ETHIOTELECOM REQUIREMENTS

Ethio
Ethio Telecom telecomrequir
Brief description,
Name requirements (20 ements (10
details
MHz Bandwidth) MHz
Bandwidth)
In case bandwidth used is inferior to 10MHz: throughput requirements without UE_AMBR will
be based on 10 MHz requirements and divided proportionnaly with frequency bandwidth, other
LTE/EPC REQUIREMENTS
VOICE
Voice call successfully established and
maintainted during 2 minutes with good
MOC - MTC - MTM (LTE/LTE)
quality
CSFB case: LTE/EPC->3G 98% 98%
MOC (Mobile Originated
Call)
4s 4s

MOC (Mobile Originated

Call)
4s 4s

MTC (Mobile Terminated

Call) 4s 4s

Voice call establishment time

CSFB case: LTE/EPC->3G MTC (Mobile Terminated
Call) 4s 4s

MTM (Mobile on LTE To

Mobile on LTE)
7s 7s

MTM (Mobile on LTE To

Mobile on LTE) 7s 7s

Voice call successfully established and

maintainted during 2 minutes with good
MOC - MTM (LTE/LTE)
quality
CSFB case: LTE/EPC->2G 98% 98%
MOC (Mobile Originated
Call) 5s 5s
MOC (Mobile Originated
Call)
5s 5s
Voice call establishment time
CSFB case: LTE/EPC->2G MTM (Mobile on LTE To
Mobile on LTE) 8s 8s

MTM (Mobile on LTE To

Mobile on LTE) 8s 8s

Voice call successfully established and

maintainted during 2 minutes with good
MOC - MTC - MTM (LTE/LTE)
quality
VoIP over IMS over LTE 98% 98%

MOC (Mobile Originated

Call) 4s 4s

Voice call establishment time MTC (Mobile Terminated

VoIP over IMS over LTE Call) 4s 4s

MTM (Mobile on LTE To

Mobile on LTE)
7s 7s
 4.3 4.3
Voice quality, MOS, AMR-WB
MTM (Mobile To Mobile)
VoIP over IMS over LTE

4.3 4.3

Voice quality, MOS, AMR-NB

VoIP over IMS over LTE
MTM (Mobile To Mobile) 3.5 3.5

Voice quality, MOS, AMR-NB MTC (Mobile Terminated

VoIP over IMS over LTE Call) 3.2 3.2

150 ms 150 ms
Mouth to Ear delay MTM (LTE/LTE)
VoIP over IMS over LTE

150 ms 150 ms

200 ms 200 ms
Mouth to Ear delay MTM (LTE/3G)
VoIP over IMS over LTE

200 ms 200 ms

SMS

MTM (LTE->LTE, 3G->LTE,

SMS successfully sent and received with
2G->LTE,
acceptable delay (<10s)
LTE->3G, LTE->2G)
98% 98%

DATA
Technical KPIs - good radio
Attach success rate 98% 98%
Attach time All technos 800 ms 800 ms
Ping success rate 98% 98%

IDLE (0 bytes) 120 ms 120 ms

IDLE (1460 bytes) 130 ms 130 ms

Round Trip Time
ACTIVE, NON SCHEDULED
(0 bytes) 30 ms 30 ms
ACTIVE, NON SCHEDULED
(1460 bytes) 40 ms 40 ms
ACTIVE, PRESCHEDULED (0
bytes) 15 ms 15 ms
ACTIVE, PRESCHEDULED
(1460 bytes) 25 ms 25 ms
Data transfer success rate 98% 98%
 cat3 90 Mbps 60Mbps
HTTP Throughput DL - Cat 3 cat3 - with one UE_AMBR <
30 Mbps UE_AMBR UE_AMBR
cat3 40 Mbps 20 Mbps
HTTP Throughput UL - cat 3 cat3 - with one UE_AMBR <
20 Mbps UE_AMBR UE_AMBR
HTTP Throughput DL - cat 4 cat4 120 Mbps 60 Mbps

HTTP Throughput DL - cat5 cat5 240 Mbps 120 Mbps

Multi users throughput DL

(4 users)
cat3 120 Mbps 60 Mbps

Technical KPIs - degraded radio

Data transfer success rate 98% 98%
80 Mbps 40 Mbps

RSSNR=20dB
80 Mbps 40 Mbps
HTTP Throughput DL - Degraded radio - Cat
3

RSSNR=15dB 40 Mbps 20 Mbps

RSSNR=10dB 30 Mbps 15 Mbps
RSSNR=5dB 20 Mbps 10 Mbps
RSSNR= -5dB 3 Mbps 1,5 Mbps
uplink pathloss = 100dB 40 Mbps 20 Mbps
uplink pathloss = 110dB 25 Mbps 12 Mbps
uplink pathloss = 120dB 10 Mbps 5 Mbps
uplink pathloss = 130dB 2 Mbps 1 Mbps
HTTP Throughput UL - Degraded radio - Cat3

uplink pathloss = 140dB 500 kbps 200 kbps

User oriented KPIs

Web page download success rate 98% 98%
Web page download time cat3 1s 1s
Data transfer success rate 98% 98%
Cat 3 38 Mbps 20 Mbps
Handover success rate 98% 98%

Interruption time
HTTP Throughput DL in mobility 100 ms 100 ms

Interruption time before

reaching nominal value 1s 1s
 Cat 3 UE_AMBR 10 Mbps 8 Mbps 8 Mbps
Handover success rate 98% 98%

HTTP Throughput DL in mobility UE_AMBR 10 Interruption time

Mbps
100 ms 100 ms

Interruption time before

reaching nominal value 1s 1s

Cat 3 20 Mbps 10 Mbps

Handover success rate 98% 98%

Interruption time
HTTP Throughput UL in mobility

100ms 100ms

Interruption time before

reaching nominal value 1s 1s

Cat 3 UE_AMBR 10 Mbps 8 Mbps 8 Mbps

Handover success rate 98% 98%

Interruption time
HTTP Throughput UL in mobility UE_AMBR 10
Mbps

100ms 100ms

Interruption time before

reaching nominal value
1s 1s

1 MS Streaming
with perfect audio/video
quality (no RTP packet loss)
98% 98%

Handover success rate 98% 98%

Streaming
Dedicated bearer activation
time
400 ms 400 ms

Interruption time
150 ms 150 ms

MULTISESSION MODE
Voice call successfully established and
maintainted during 2 minutes with good
quality while downlink transfer is MTM
running
CSFB case: LTE->3G, VoIP over IMS 98% 98%
Voice call establishment time while
downlink transfer is running MTM 8s 8s
CSFB case: LTE->3G,VoIP over IMS

LEGEND
 Compliancy of supplier
FC Fully Compliant
PC Partialy Compliant
NC Not Compliant
 VALID IN: End user SUPPLIER COMMITMENTS
LAB FIELD KPIs
Monitoring:
Cell center
Huawei Comments Agreement with TEP
Degraded

Cell edge
List of
Drive counters/ 20140920 2014/07/16
Ideal

metrics/ind
icators:

X X
X

X There is no landline telephone in the lab.

There is a switch for CSFB in 2G

not acceptable
which is not opened now.
X X
X

X There is a switch for CSFB in 2G

not acceptable
which is not opened now.
X

X
There is no IMS in the network,
Huawei recommends to test when Accepted
X X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X X IMS is available
 There is no IMS in the network,
Huawei recommends to test when Accepted
X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X IMS is available

There is no IMS in the network,

Huawei recommends to test when Accepted
X IMS is available

The delay time can not be

evaluated by Actix, so we need to
use Mobile Partner to test.
X X

X X
X X
X X

X X
X X NEMO does not support 0 Bytes
Ping,
not acceptable
X X We could use Hrping instead for
test.
X X

X X

X X
X X
X X

X X
X X

X X
X X

No cat5 commercial terminal until

now.

X X

X X

X X
X

X
X X
X X
X X
X X
X X
X X Nemo can't support this function to
observe pathloss directly.
X X
We could observe RSCP instead
X X of pathloss. The relation is:
not acceptable
pathloss = Cell Pdsch Power –
RSRP.
It's impossible to find the point near
130 and 140dB in outdoor test.
X X

X X
X X
X
X
X
Nemo doesn't support this test.
We could use other tools like
X Network Monitor for test.
Nemo doesn't support this test.
We could use other tools like
not acceptable
Network Monitor and LMT Cell
X Performance Monitoring for test.
 X
X
Nemo doesn't support this test.
We could use other tools like
X Network Monitor for test.
Nemo doesn't support this test.
We could use other tools like not acceptable
X Network Monitor for test.
X
X

Nemo doesn't support this test.

We could use other tools like
Network Monitor for test.
X
Nemo doesn't support this test.
We could use other tools like
not acceptable
Network Monitor and LMT Cell
X Performance Monitoring for test.
X
X

Nemo doesn't support this test.

We could use other tools like
Network Monitor for test.
X
Nemo doesn't support this test.
We could use other tools like
not acceptable
Network Monitor and LMT Cell
X Performance Monitoring for test.
Nemo doesn't support this test.
We could use other tools like
X Network Monitor for test.
X
Nemo doesn't support this test.
We could use other tools like
X Network Monitor for test.
Nemo doesn't support this test.
We could use other tools like
X Network Monitor for test.

There is no IMS in the network,

Huawei recommends to test when Accepted
IMS is available
X X
There is no IMS in the network,
Huawei recommends to test when Accepted
X X IMS is available
COMMITMENTS
Release
considered
for first Comment or
Complianc Value
complianc additional
y (if PC)
e (Release information
N if not
specified)

FC
FC

Huawei commits 5.5s

in DT scenario. CQT
NC 5.5s can meet 4s.

FC

Huawei commits 5.5s

in DT scenario. CQT
NC 5.5s can meet 4s.

FC

Huawei commits 9s in
DT scenario. CQT can
NC 9s meet 7s.

FC
FC

Huawei commits 8.2s

NC 8.2s in DT scenario.

FC

Huawei commits 12s

NC 12s in DT scenario.

FC

FC

FC

FC
FC

FC

FC

FC

FC

FC

FC

FC

FC

FC
FC
FC

FC
FC

FC

FC

FC

FC

FC
FC

FC
FC

FC
FC

No cat5 commercial
terminal until now.
Huawei commits to
FC test when applicable.

FC

FC
FC

Huawei commits
60Mbps for 20 MHz of
bandwidth in Cell
edge scenario.
60 Huawei commits
Mbps@20MHz 30Mbps for 10 MHz of
30 bandwidth in Cell
NC Mbps@10MHz edge scenario.
FC
FC
FC
FC
FC
FC
FC
FC

100 Huawei commits

kbps@20MHz 100kbps in LAB-
100 Degraded and Cell
NC kbps@10MHz edge scenario.

FC
FC
FC
FC
FC

FC

FC
FC
FC

FC

FC
FC
FC

Huawei commits
140ms in Drive Test
scenario. Only can
NC 140 ms meet in LAB to 100ms.

FC
FC
FC

Huawei commits
140ms in Drive Test
scenario. Only can
NC 140 ms meet in LAB to 100ms.

FC

FC
FC

FC

FC

FC

FC
 paragraph title to be considered in
the word document

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice quality

Voice quality

Voice quality

Mouth to ear

Mouth to ear

SMS KPIs: SMS successful reception

Attach
Attach
PING

PING
PING

PING

PING

PING

PING
HTTP throughput: File transfer
HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

Multi users throughput

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer

HTTP throughput: File transfer

Web browsing
Web browsing
Intrasystem mobility during data transfer
Intrasystem mobility during data transfer
Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer
Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer
Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer
Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Streaming
Streaming

Streaming

Streaming

Multisession mode: Voice call while a data transfer is runnin

Multisession mode: Voice call while a data transfer is runnin

 ETHIOTELECOM REQUIREMENTS

Ethio Telecom
Name Brief description, details requirements
(all bandwidth)

LTE/EPC-3G REQUIREMENTS
VOICE

Intersystem handover success rate with

from LTE to 3G
SRVCC

98%

300 ms

Intersystem handover interruption time

from LTE to 3G
with SRVCC

300 ms

DATA
from LTE to 3G
Intersystem handover success rate 98%
HTTP Transfer
from 3G to LTE
98%

500 ms
from LTE to 3G - downlink

500 ms

500 ms
Intersystem interruption time
HTTP Transfer from LTE to 3G - uplink

503 ms

from 3G to LTE - downlink

500 ms

from 3G to LTE - uplink

500 ms
Intersystem handover success rate from LTE to 3G 98%
Video streaming
from 3G to LTE
98%
500 ms
from LTE to 3G
Intersystem interruption time 500 ms
Video streaming
Intersystem interruption time
Video streaming
from 3G to LTE
500 ms

Intersystem cell reselection with

redirection success rate from LTE to 3G
HTTP Download
98%
Intersystem cell reselection with 5s
redirection interruption time from LTE to 3G - downlink
HTTP Download 5s

LTE/EPC-2G REQUIREMENTS
VOICE

Intersystem handover success rate with

from LTE to 2G
SRVCC

98%

Intersystem handover interruption time

from LTE to 2G
with SRVCC

300 ms

DATA
Intersystem cell reselection with
redirection success rate from LTE to 2G
HTTP Download 98%

LEGEND
Compliancy of supplier
FC Fully Compliant
PC Partialy Compliant
NC Not Compliant
 VALID IN:
LAB FIELD
End user KPIs
Cell center

Huawei Comments
Degraded

Cell edge Monitoring: Compliancy

Drive List of counters/ in Release N. 20140920
Ideal

metrics/indicators:

Vendor shall commit the test at no cost to ethio

X X
telecom when the IMS ready and fully meet the
KPI as per the agreement ( HQ official
commitment letter) And This KPI hasn't impact
on PAC
FC

Vendor shall commit the test at no cost to ethio

telecom when the IMS ready and fully meet the
KPI as per the agreement ( HQ official
commitment letter) And This KPI hasn't impact
on PAC
X FC

Vendor shall commit the test at no cost to ethio

telecom when the IMS ready and fully meet the
KPI as per the agreement ( HQ official
commitment letter) And This KPI hasn't impact
on PAC
X NC

X X FC
The HO switch is not opened from 3G to LTE,
X X FC Now there is no Licence for this switch.
Nemo doesn't support this test.
We could use other tools like Network Monitor for
X FC test.
Nemo doesn't support this test.
We could use other tools like Network Monitor for
X FC test.
Nemo doesn't support this test.
We could use other tools like Network Monitor for
X FC test.
Nemo doesn't support this test.
We could use other tools like Network Monitor for
X FC test.
The HO switch is not opened from 3G to LTE,
X X FC Now there is no Licence for this switch.
The HO switch is not opened from 3G to LTE,
X X FC Now there is no Licence for this switch.
X X FC
The HO switch is not opened from 3G to LTE,
X X FC Now there is no Licence for this switch.
Nemo doesn't support this test.
X FC We could use other tools like Network Monitor for
X FC test.
 The HO switch is not opened from 3G to LTE,
X X FC Now there is no Licence for this switch.

Nemo doesn't support this test.

X X FC We could use other tools like Network Monitor for
test.
X FC
X FC

Vendor shall commit the test at no cost to ethio

telecom when the IMS ready and fully meet the
KPI as per the agreement ( HQ official
commitment letter) And This KPI hasn't impact
on PAC
X X FC

Vendor shall commit the test at no cost to ethio

telecom when the IMS ready and fully meet the
KPI as per the agreement ( HQ official
commitment letter) And This KPI hasn't impact
on PAC
X X FC

Nemo doesn't support this test.

We could use other tools like Network Monitor for
X X FC test.
 SUPPLIER COMMITMENTS
Value in
Value in Release Compliancy
Agreement with TEP Release
N in Release
2014/07/16 N+1
(if PC) N+1.
(if PC)

Accepted

Accepted

Accepted

600 ms
Accepted

Accepted
 Comment or additional information

Huawei commits ESRVCC 600ms in DT scenario.

Reselection Succesful Rate

Attach Time

Attach Time

Reselection Succesful Rate

Attach Time

Currently there is no Commercial terminal support SRVCC

handover from LTE to GSM.
Huawei commits to test when applicable.

Currently there is no Commercial terminal support SRVCC

handover from LTE to GSM.
Huawei commits to test when applicable.
paragraph title to be considered in the word
document

Intersystem voice mobility

Intersystem voice mobility

Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer

Intersystem handover mobility during streaming
Intersystem handover mobility during streaming
Intersystem handover mobility during streaming
Intersystem handover mobility during streaming

Intersystem cell-reselection during data transfer

Intersystem cell-reselection during data transfer

Intersystem voice mobility

Intersystem voice mobility

Intersystem cell-reselection during data transfer

 ETHIOTELECOM REQUIREMENTS VALID IN:
Ethio LAB
Ethio Telecom telecomrequir
Brief description,
Name requirements (20 ements (10
details
MHz Bandwidth) MHz

Ideal
Bandwidth)
In case bandwidth used is inferior to 10MHz: throughput requirements without UE_AMBR will
be based on 10 MHz requirements and divided proportionnaly with frequency bandwidth, other
LTE/EPC REQUIREMENTS
VOICE
Author:
作为新增指标的备选
Voice call successfully established and
按98%承诺，加3G电
maintainted during 2 minutes with good
MOC - MTC - MTM (LTE/LTE) 要求（参考基线确认
quality
。
CSFB case: LTE/EPC->3G
98% 98% X
新增CDR<1%

MOC (Mobile Originated

Call) 4s 4s
X

MOC (Mobile Originated

Call)
4s 4s

MTC (Mobile Terminated

Call)
4s 4s
X
Voice call establishment time
CSFB case: LTE/EPC->3G
MTC (Mobile Terminated
Call) 4s 4s

MTM (Mobile on LTE To

Mobile on LTE)
7s 7s
X

MTM (Mobile on LTE To

Mobile on LTE) 7s 7s

Voice call successfully established and

maintainted during 2 minutes with good
MOC - MTM (LTE/LTE)
quality
CSFB case: LTE/EPC->2G
98% 98% X

MOC (Mobile Originated

Call) 5s 5s
X

MOC (Mobile Originated

Call) 5s 5s
Voice call establishment time
CSFB case: LTE/EPC->2G
MTM (Mobile on LTE To
Mobile on LTE)
8s 8s
X
Voice call establishment time
CSFB case: LTE/EPC->2G

MTM (Mobile on LTE To

Mobile on LTE) 8s 8s

Voice call successfully established and

maintainted during 2 minutes with good
MOC - MTC - MTM (LTE/LTE)
quality
VoIP over IMS over LTE 98% 98% X
MOC (Mobile Originated
Call)
4s 4s X
MTC (Mobile Terminated
Voice call establishment time
Call) 4s 4s X
VoIP over IMS over LTE
MTM (Mobile on LTE To
Mobile on LTE) 7s 7s X
Voice quality, MOS, AMR-WB 4.3 4.3 X
MTM (Mobile To Mobile)
VoIP over IMS over LTE 4.3 4.3
Voice quality, MOS, AMR-NB
VoIP over IMS over LTE
MTM (Mobile To Mobile) 3.5 3.5 X
Voice quality, MOS, AMR-NB MTC (Mobile Terminated
VoIP over IMS over LTE Call)
3.2 3.2 X
Mouth to Ear delay MTM (LTE/LTE) 150 ms 150 ms X
VoIP over IMS over LTE 150 ms 150 ms
Mouth to Ear delay MTM (LTE/3G) 200 ms 200 ms X
VoIP over IMS over LTE 200 ms 200 ms

SMS Author:
RRC成功率>98.5%，
eRAB成功率>99%
MTM (LTE->LTE, 3G->LTE,
SMS successfully sent and received with
2G->LTE,
acceptable delay (<10s)
LTE->3G, LTE->2G)
98% 98% X

DATA
Technical KPIs - good radio

Attach success rate

98% 98% X

Attach time All technos 800 ms 800 ms

X

Ping success rate

98% 98% X
IDLE (0 bytes) 120 ms 120 ms X
IDLE (1460 bytes) 130 ms 130 ms X
ACTIVE, NON SCHEDULED
(0 bytes) 30 ms 30 ms X
Round Trip Time ACTIVE, NON SCHEDULED
(1460 bytes) 40 ms 40 ms X
ACTIVE, PRESCHEDULED (0
bytes) 15 ms 15 ms X
ACTIVE, PRESCHEDULED
(1460 bytes)
25 ms 25 ms X
Data transfer success rate 98% 98%
X
cat3 90 Mbps 60Mbps X
HTTP Throughput DL - Cat 3 cat3 - with one UE_AMBR <
30 Mbps UE_AMBR UE_AMBR X
cat3 40 Mbps 20 Mbps X
HTTP Throughput UL - cat 3 cat3 - with one UE_AMBR <
20 Mbps UE_AMBR UE_AMBR X
HTTP Throughput DL - cat 4 cat4 120 Mbps 60 Mbps X

HTTP Throughput DL - cat5 cat5 240 Mbps 120 Mbps

X
Multi users throughput DL
(4 users)
cat3 120 Mbps 60 Mbps X
Technical KPIs - degraded radio

Data transfer success rate 98% 98%

80 Mbps 40 Mbps

RSSNR=20dB
80 Mbps 40 Mbps
HTTP Throughput DL - Degraded radio - Cat
3

RSSNR=15dB 40 Mbps 20 Mbps

RSSNR=10dB 30 Mbps 15 Mbps
RSSNR=5dB 20 Mbps 10 Mbps
RSSNR= -5dB 3 Mbps 1,5 Mbps
uplink pathloss = 100dB 40 Mbps 20 Mbps
uplink pathloss = 110dB 25 Mbps 12 Mbps
uplink pathloss = 120dB 10 Mbps 5 Mbps
uplink pathloss = 130dB 2 Mbps 1 Mbps
HTTP Throughput UL - Degraded radio - Cat3

uplink pathloss = 140dB 500 kbps 200 kbps

User oriented KPIs

Web page download success rate 98% 98%

X
Web page download time cat3 1s 1s

Data transfer success rate

Author:
98% 98%
改为FTP, 34Mbps
Cat 3 38 Mbps 20 Mbps

Handover success rate 98% 98%

HTTP Throughput DL in mobility

Interruption time

100 ms 100 ms

Interruption time before

reaching nominal value 1s 1s

Cat 3 UE_AMBR 10 Mbps 8 Mbps 8 Mbps

Handover success rate 98% 98%

HTTP Throughput DL in mobility UE_AMBR 10

Mbps
Interruption time

100 ms 100 ms
 Interruption time before
reaching nominal value 1s 1s

Author:
FTP, 18Mbps
Cat 3 20 Mbps 10 Mbps

Handover success rate 98% 98%

HTTP Throughput UL in mobility

Interruption time

100ms 100ms

Interruption time before

reaching nominal value 1s 1s

Cat 3 UE_AMBR 10 Mbps 8 Mbps 8 Mbps

Handover success rate 98% 98%

HTTP Throughput UL in mobility UE_AMBR 10

Mbps
Interruption time

100ms 100ms
 Interruption time before
reaching nominal value 1s 1s

1 MS Streaming
with perfect audio/video
quality (no RTP packet loss) 98% 98%

Handover success rate 98% 98%

Streaming

Dedicated bearer activation

time

400 ms 400 ms

Interruption time

150 ms 150 ms

MULTISESSION MODE
Voice call successfully established and
maintainted during 2 minutes with good
quality while downlink transfer is MTM
running
CSFB case: LTE->3G, VoIP over IMS 98% 98% X
Voice call establishment time while
downlink transfer is running MTM 8s 8s
CSFB case: LTE->3G,VoIP over IMS X

LEGEND
Compliancy of supplier
FC Fully Compliant
PC Partialy Compliant
NC Not Compliant
 VALID IN: SUPPLIER COMMIT
LAB FIELD
Release considered
Cell center

for first compliance Complianc Value

Degraded

Cell edge

KPI formula
(Release N if not y (if PC)
Drive

specified)

Author:
作为新增指标的备选，
按98%承诺，加3G电平
要求（参考基线确认） The success rate is evaluated that the
。 times of "CC Alerting" compare to the
times of "Extended Service Request" and
X "Paging with CS Domain indicator" FC
新增CDR<1%

Between "Extended Service Request" in

LTE/EPC and “CC Alerting” in 3G/2G, for CC Alerting - EMM Extended
MOC and MTM calls (calling part) Service Request FC

Between "Extended Service Request" in

LTE/EPC and “CC Alerting” in 3G/2G, for
X MOC and MTM calls (calling part) NC 5.5s
Between first “Paging with CS Domain
indicator” in LTE/EPC and “CC Alerting” in
3G/2G for MTC calls FC

Between first “Paging with CS Domain

indicator” in LTE/EPC and “CC Alerting” in
X 3G/2G for MTC calls NC 5.5s

Between "Extended Service Request" in

LTE/EPC and “CC Alerting” in 3G/2G, for
MOC and MTM calls (calling part) FC

Between "Extended Service Request" in

LTE/EPC and “CC Alerting” in 3G/2G, for
X MOC and MTM calls (calling part) NC 9s

The success rate is evaluated that the

times of "CC Alerting" compare to the
times of "Extended Service Request" and
X "Paging with CS Domain indicator" FC

Between "Extended Service Request" in

LTE/EPC and “CC Alerting” in 3G/2G, for
MOC and MTM calls (calling part) FC

Between "Extended Service Request" in

LTE/EPC and “CC Alerting” in 3G/2G, for
X MOC and MTM calls (calling part) NC 8.2s

Between "Extended Service Request" in

LTE/EPC and “CC Alerting” in 3G/2G, for
MOC and MTM calls (calling part) FC
 Between "Extended Service Request" in
LTE/EPC and “CC Alerting” in 3G/2G, for
X MOC and MTM calls (calling part) NC 12s

X FC
X FC

X FC

X FC
FC
X FC

X FC

X FC
FC
X FC
FC
X FC

The delay time is evaluated that the

received time minus the send time in the
X Mobile partner. FC

The success rate is evaluated that the

times of "EMM Attach Complete" compare
to the times of "UL_CCCH
X RRCConnectionRequest". FC

The Attach time is evaluated that the time

of "EMM Attach Complete" minus the time
X of "UL_CCCH RRCConnectionRequest"
EMM Attach Complete - UL_CCCH RRCConnectionRequest
FC

The success rate is evaluated that the

times of received response compare to the
X times of sent data. FC
X FC
X FC

X FC

X FC

The delay between 2 consecutive PINGs FC

X
has to be adapted in order to enable
expected state changes defined in master FC
X Excel document.
 the success rate is evaluated that the times
of success complare to the times of
X transfer FC
X FC

X FC
X FC

X FC
X FC
The speed of application layer or PDCP
layer

X FC

X FC

the success rate is evaluated that the times

of success complare to the times of
X X transfer FC
X FC

60
Mbps@20MHz
30
X NC Mbps@10MHz
X X FC
The speed of application layer or PDCP
X X layer FC
X X FC
X X FC
X X FC
X X FC
X X FC
X X FC

100
kbps@20MHz
100
X X NC kbps@10MHz

The success rate is evaluated that the

times of success complare to the times of
X opening FC
 • Web page download times are calculated
with Network Monitor on laptop between
the DNS resolution of the page name and
the last TCP ACK of the last object of the
downloaded page. If no DNS resolution is
needed, then the first “TCP SYN” is
X considered. FC

the success rate is evaluated that the times

of success complare to the times of
X transfer FC
The speed of application layer or PDCP
X layer FC
The success rate is evaluated that
Intra-frequency Handover Out
Success
Rate=(L.HHO.IntraeNB.IntraFreq.Exec
SuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccO
ut)/(L.HHO.IntraeNB.IntraFreq.ExecAtt
Out +
L.HHO.IntereNB.IntraFreq.ExecAttOut
X ) FC

This interruption time is measured at

application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and first TCP packet
received by the mobile on target cell. This
will be a full TCP frame (user plan) for
downlink transfer, and TCP ACK for uplink
X transfer. FC

This interruption time is measured at

application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and the first TCP
packet received by the mobile on target
cell when the throughput is back to the
value it was on the initial cell before the
X handover. FC
The speed of application layer or PDCP
X layer FC
The success rate is evaluated that
Intra-frequency Handover Out
Success
Rate=(L.HHO.IntraeNB.IntraFreq.Exec
SuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccO
ut)/(L.HHO.IntraeNB.IntraFreq.ExecAtt
Out +
L.HHO.IntereNB.IntraFreq.ExecAttOut
X ) FC

This interruption time is measured at

application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and first TCP packet
received by the mobile on target cell. This
will be a full TCP frame (user plan) for
downlink transfer, and TCP ACK for uplink
X transfer. FC
 This interruption time is measured at
application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and the first TCP
packet received by the mobile on target
cell when the throughput is back to the
value it was on the initial cell before the
X handover. FC
The speed of application layer or PDCP
X layer FC
The success rate is evaluated that
Intra-frequency Handover Out
Success
Rate=(L.HHO.IntraeNB.IntraFreq.Exec
SuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccO
ut)/(L.HHO.IntraeNB.IntraFreq.ExecAtt
Out +
L.HHO.IntereNB.IntraFreq.ExecAttOut
X ) FC

This interruption time is measured at

application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and first TCP packet
received by the mobile on target cell. This
will be a full TCP frame (user plan) for
downlink transfer, and TCP ACK for uplink
X transfer. NC 140 ms

This interruption time is measured at

application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and the first TCP
packet received by the mobile on target
cell when the throughput is back to the
value it was on the initial cell before the
X handover. FC
The speed of application layer or PDCP
X layer FC
The success rate is evaluated that
Intra-frequency Handover Out
Success
Rate=(L.HHO.IntraeNB.IntraFreq.Exec
SuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccO
ut)/(L.HHO.IntraeNB.IntraFreq.ExecAtt
Out +
L.HHO.IntereNB.IntraFreq.ExecAttOut
X ) FC

This interruption time is measured at

application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and first TCP packet
received by the mobile on target cell. This
will be a full TCP frame (user plan) for
downlink transfer, and TCP ACK for uplink
X transfer. NC 140 ms
 This interruption time is measured at
application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and the first TCP
packet received by the mobile on target
cell when the throughput is back to the
value it was on the initial cell before the
X handover. FC

• The IP packet lost are measured thanks

to IP sniffer on client (by analyzing RTCP
reports which gives the packets lost
X experienced by the client) FC
The success rate is evaluated that
Intra-frequency Handover Out
Success
Rate=(L.HHO.IntraeNB.IntraFreq.Exec
SuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccO
ut)/(L.HHO.IntraeNB.IntraFreq.ExecAtt
Out +
L.HHO.IntereNB.IntraFreq.ExecAttOut
X ) FC

• The dedicated bearer activation time is

measured on the IP mobile traces (radio
and IP) between the last “RTSP 200”
packet (ending the session initialization)
and the first RTP packet on the dedicated
X bearer. FC

This interruption time is measured at

application level with Network Monitor
between last TCP packet received by the
mobile on initial cell and first TCP packet
received by the mobile on target cell. This
will be a full TCP frame (user plan) for
downlink transfer, and TCP ACK for uplink
X transfer. FC

X FC

X FC
SUPPLIER COMMITMENTS
Next Next
release, release,
Compliancy Value in next Compliancy Value in next Comment or
considere considered
in next release in next release additional
d for for
release. (if PC) release. (if PC) information
improvem improveme
ent nt

Huawei commits 5.5s

in DT scenario. CQT
can meet 4s.

Huawei commits 5.5s

in DT scenario. CQT
can meet 4s.

Huawei commits 9s in
DT scenario. CQT can
meet 7s.

Huawei commits 8.2s

in DT scenario.
Huawei commits 12s
in DT scenario.

Excluding the reason

caused by third part
equipment
No cat5 commercial
terminal until now.
Huawei commits to
test when applicable.

Huawei commits
60Mbps for 20 MHz of
bandwidth in Cell
edge scenario.
Huawei commits
30Mbps for 10 MHz of
bandwidth in Cell
edge scenario.

Huawei commits
100kbps in LAB-
Degraded and Cell
edge scenario.
Huawei commits
140ms in Drive Test
scenario. Only can
meet in LAB to 100ms.

Huawei commits
140ms in Drive Test
scenario. Only can
meet in LAB to 100ms.
 paragraph title to be considered in
the word document

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice call establishment

Voice quality

Voice quality

Voice quality
Mouth to ear

Mouth to ear

SMS KPIs: SMS successful reception

Attach

Attach

PING
PING
PING

PING

PING

PING

PING
HTTP throughput: File transfer
HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

Multi users throughput

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer

HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer
HTTP throughput: File transfer

HTTP throughput: File transfer

Web browsing
Web browsing

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Intrasystem mobility during data transfer

Streaming

Streaming

Streaming

Streaming

Multisession mode: Voice call while a data transfer is runnin

Multisession mode: Voice call while a data transfer is runnin

 ETHIOTELECOM REQUIREMENTS VALID IN:
LAB
Ethio Telecom

Degraded
Name Brief description, details requirements
(all bandwidth)

Ideal
LTE/EPC-3G REQUIREMENTS
VOICE
Intersystem handover success rate with
from LTE to 3G
SRVCC 98% X
Intersystem handover interruption time 300 ms X
from LTE to 3G
with SRVCC 300 ms

DATA

Intersystem handover success rate from LTE to 3G

HTTP Transfer
98% X
from 3G to LTE 98% X
500 ms X
from LTE to 3G - downlink
500 ms
500 ms X
from LTE to 3G - uplink
Intersystem interruption time 503 ms
HTTP Transfer
from 3G to LTE - downlink
500 ms X
from 3G to LTE - uplink
500 ms X
Intersystem handover success rate from LTE to 3G 98% X
Video streaming
from 3G to LTE
98% X

500 ms
from LTE to 3G
Intersystem interruption time
Video streaming X
500 ms

from 3G to LTE
500 ms X

Intersystem cell reselection with

redirection success rate from LTE to 3G
HTTP Download
98% X
Intersystem cell reselection with
redirection interruption time from LTE to 3G - downlink 5s X
HTTP Download
5s

LTE/EPC-2G REQUIREMENTS
VOICE

Intersystem handover success rate with

from LTE to 2G
SRVCC
98% X
Intersystem handover interruption time
from LTE to 2G
with SRVCC
300 ms X

DATA

Intersystem cell reselection with

redirection success rate from LTE to 2G
HTTP Download
98% X

LEGEND
Compliancy of supplier
FC Fully Compliant
PC Partialy Compliant
NC Not Compliant
VALID IN: SUPPLIER COMMITMENTS
FIELD
Value in Release Compliancy
Cell center

Compliancy
Cell edge

KPI formula N in Release

in Release N.
(if PC) N+1.
Drive

X FC
FC
X NC 600 ms

HO success rate = UL-DCCH

HandoverToUTRANComplete /
X HandoverToUTRANCommand * 100% FC
X FC
will be a full TCP frame (user plan) for
downlink transfer, and TCP ACK for uplink FC
X transfer. FC
will be a full TCP frame (user plan) for
downlink transfer, and TCP ACK for uplink FC
X transfer. FC

X FC

X success rate = UL-DCCH FC

HandoverToUTRANComplete /
X HandoverToUTRANCommand * 100% FC
X FC

This interruption time is measured at

application level with Network Monitor
between last UDP packet received by the
mobile on initial layer and first UDP packet FC
X received by the mobile on target layer. FC

X FC
This interruption time is measured at
The successlevel
application ratewith
is evaluated
Network that the
Monitor
count L.IRATHO.E2W.ExecSuccOut
between last TCP packet received by the
compare
mobile onto L.IRATHO.E2W.ExecAttOut
initial in
layer and first TCP packet
X received by the mobileM2000.on target layer. This FC
will be a full TCP frame (user plan) for
downlink transfer. FC
X FC
X FC

X FC

The success rate is evaluated that the

count L.IRATHO.E2W.ExecSuccOut
compare to L.IRATHO.E2W.ExecAttOut in
X M2000. FC
COMMITMENTS
Value in
Release
Comment or additional information
N+1
(if PC)

Huawei commits ESRVCC 600ms in DT scenario.

The HO switch is not opened from 3G to LTE, Now there

is no Licence for this switch.

The HO switch is not opened from 3G to LTE, Now there

is no Licence for this switch.
The HO switch is not opened from 3G to LTE, Now there
is no Licence for this switch.

The HO switch is not opened from 3G to LTE, Now there

is no Licence for this switch.

The HO switch is not opened from 3G to LTE, Now there

is no Licence for this switch.
Currently there is no Commercial terminal support SRVCC
handover from LTE to GSM.
Huawei commits to test when applicable.
Currently there is no Commercial terminal support SRVCC
handover from LTE to GSM.
Huawei commits to test when applicable.
paragraph title to be considered in the word
document

Intersystem voice mobility

Intersystem voice mobility

Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer
Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer

Intersystem handover mobility during data transfer

Intersystem handover mobility during streaming
Intersystem handover mobility during streaming

Intersystem handover mobility during streaming

Intersystem handover mobility during streaming

Intersystem cell-reselection during data transfer

Intersystem cell-reselection during data transfer

Intersystem voice mobility

Intersystem voice mobility

Intersystem cell-reselection during data transfer

 ETHIOTELECOM REQUIREMENTS VALID IN:
LAB
Brief description,

Degraded
Name requirements
details

Ideal
2G REQUIREMENTS
CIRCUIT MODE

Voice call successfully established and

KPI maintainted during 2 minutes with good MOC - MTC - MTM
Every quality
15 min 98% X

MOC (Mobile Originated

Call)
4s
X
Voice call establishment time
MTC (Mobile Terminated
Call) 4s
X
MTM (Mobile To Mobile) 7s X

PACKET MODE
Technical KPIs

Attach success rate

98% X

Attach time All technos 2,5s

X

PDP context activation success rate

KPI 98% X

Every PDP context activation time All technos 1,5s

15 min KPI X
Ping success rate 98% X

EDGE - PING 0s, 0 Bytes 250 ms

Round Trip Time X
EDGE - PING 0s, 1460
Bytes 350 ms

Data transfer success rate 98%

X
HTTP Throughput UL/DL EDGE 50 kbps/TS
X

User oriented KPIs

Web page download success rate 98% X
 Web page download time EDGE 20s

Data transfer success rate 98%

Every KPI HTTP Throughput DL EDGE 130kbps

15 min KPI HTTP Throughput UL EDGE 70kbps
Cell reselection success rate 98%

Interruption time EDGE, Intra RA 1,5s

LEGEND
Compliancy of supplier
FC Fully Compliant
PC Partialy Compliant
NC Not Compliant
VALID IN: SUPPLIER COMMIT
FIELD
Cell center

Compliancy in Release
Cell edge

N.
Drive

X X FC

X X FC

X X FC
X X FC

X FC

X FC

X FC

X FC
X FC

X FC

FC

X FC

X FC

X FC
X FC

X FC
X FC
X FC
X FC

X FC
 SUPPLIER COMMITMENTS

Agreement with Value in

Huawei Comments Release
TEP
20140920 N
2014/07/16 (if PC)

NEMO does not support the KPI generation, we could use Actix
Accepted

NEMO does not support the KPI generation, we could use Actix
2014/9/20 no fix-line phone is available in Lab Accepted
NEMO does not support the KPI generation, we could use Actix Accepted

NEMO does not support 0 Bytes Ping

2014/9/20：We could use PROBE or Windows CMD or NEMO
handy instead for test. Not acceptable.

NEMO does not support the test scenario Not acceptable.

NEMO does not support the test scenario
2014/9/20: We could use other tools like Network Monitor
for test.
Not acceptable.

NEMO does not support the test scenario Not acceptable.

NEMO does not support the test scenario

2014/9/20: We could use other tools like Network Monitor
for test.
Not acceptable.
 Value in
Compliancy in Release Release Comment or additional
N+1. N+1 information
(if PC)
 ETHIOTELECOM REQUIREMENTS VALID IN:
LAB FIELD

Cell center
Brief description,

Degraded
Name requirements
details

Ideal
2G REQUIREMENTS
CIRCUIT MODE

Voice call successfully established and

KPI maintainted during 2 minutes with good MOC - MTC - MTM
Every quality
15 min 98% X X

MOC (Mobile Originated

Call) 4s
X X
Voice call establishment time
MTC (Mobile Terminated
Call)
4s
X X
MTM (Mobile To Mobile) 7s X X

PACKET MODE
Technical KPIs

Attach success rate

98% X X

Attach time All technos 2,5s

X X

PDP context activation success rate

KPI 98% X X

Every PDP context activation time All technos 1,5s

15 min KPI X X
Ping success rate 98% X X

EDGE - PING 0s, 0 Bytes 250 ms

Round Trip Time X X
EDGE - PING 0s, 1460
Bytes 350 ms

Data transfer success rate 98%

X X
HTTP Throughput UL/DL EDGE 50 kbps/TS
X X
 User oriented KPIs
Web page download success rate 98% X X

Web page download time EDGE 20s

X X

Data transfer success rate 98%

Every KPI HTTP Throughput DL EDGE 130kbps

15 min KPI HTTP Throughput UL EDGE 70kbps
Cell reselection success rate 98%

Interruption time EDGE, Intra RA 1,5s

LEGEND
Compliancy of supplier
FC Fully Compliant
PC Partialy Compliant
NC Not Compliant
VALID IN: SUPPLIER COMMITMENTS
FIELD
Compli
ancy in
Cell edge

Actix Formula
Releas
Drive

e N.

(1-
NemoEvent_AbnormalCallDisconnect_CAD
/NemoEvent_OutgoingCallSetupSuccess_C
X FC AC)*CallSetupSuccessRate

GSM_Call_Setup_Time(Mean)
X FC

GSM_Call_Setup_Time(Mean)
X FC
X FC GSM_Call_Setup_Time(Mean)

NemoEvent_GPRS_AttachConnected_GAC
/NemoEvent_GPRS_AttachAttempt_GAA
FC
Time of
NemoEvent_GPRS_AttachConnected_GAC
FC -NemoEvent_GPRS_AttachAttempt_GAA
(NemoEvent_GPRS_PDPContext_Activation
Attempt_PAA-
NemoEvent_GPRS_PDPContext_ActivationF
ailed_PAF)/NemoEvent_GPRS_PDPContext_
ActivationAttempt_PAA
FC

①GPRS_SM_PDP_Context_Time
FC
FC Success Times/Attempt Times

Ping Statistics-Ping_RTT-Mean
FC

FC Ping Statistics-Ping_RTT-Mean
Data transfer completed (DCOMP)/ Data
transfer request
FC
Application Throughput uplink
FC -Average
 FC Success Times/Attempt Times
Average(File transfer download time)
:The page download time is measured
with Wireshark between the first SYN
packet that MS send to HTTP server and
the last ACK packet that MS send to
FC HTTP server
Data transfer completed (DCOMP)/ Data
transfer request
X FC
X FC Application Throughput uplink -Average
X FC Application Throughput uplink -Average
X FC Success Times/Attempt Times

This interruption time is measured at

application level with Wireshark
between last TCP packet received by
the mobile on initial cell and first
TCP packet received by the mobile on
target cell
X FC
 ETHIOTELECOM REQUIREMENTS

Name Brief description, details

3G REQUIREMENTS
CIRCUIT MODE

Voice call successfully

established and maintainted
MOC - MTC - MTM
during 2 minutes with good
Every quality
15 min KPI

MOC (Mobile Originated

Call)

Voice call establishment time MTC (Mobile

Terminated Call)

MTM (Mobile To Mobile)

PACKET MODE
Technical KPIs - good radio
Attach success rate

Attach time All technos

PDP context activation

KPI success rate

PDP context activation time All technos

Every
15 min KPI

Ping success rate

R99, CELL_DCH (0
bytes)

R99, CELL_DCH (1460

bytes)
 R99, CELL_FACH (1460
bytes)

HSDPA, CELL_DCH (0
bytes)

HSDPA, CELL_DCH (1460

bytes)
HSDPA, CELL_FACH
(1460 bytes)
Round Trip Time

HSUPA 10ms, CELL_DCH

(0 bytes)

HSUPA 10ms, CELL_DCH

(1460 bytes)
HSUPA 10ms,
CELL_FACH (1460 bytes)

HSUPA 2ms, CELL_DCH

(0 bytes)

HSUPA 2ms, CELL_DCH

(1460 bytes)
HSUPA 2ms, CELL_FACH
(1460 bytes)
Data transfer success rate

R99

cat12

cat6

cat8

cat9
 cat10

cat13 & 17 with 64QAM

cat14 & 18 with 64QAM

cat15 & 17 with MIMO

HTTP Throughput DL
cat16 & 18 with MIMO

cat13 & 17 with 64QAM

cat14 & 18 with 64QAM

Every
15 min KPI

cat15 & 17 with MIMO

cat16 & 18 with MIMO

cat 24 - Dual Carrier

(wo 64QAM)

cat 24 - Dual Carrier

(with 64QAM)
 cat 24 - Dual Carrier
(with 64QAM)

R99

cat3

cat5

HTTP Throughput UL
cat6

cat7 with 16QAM

cat7 with 16QAM

cat12

cat6

cat8

cat9

cat10

cat13 & 17 with 64QAM

Cell Capacity DL
Cell Capacity DL
cat14 & 18 with 64QAM

cat15 & 17 with MIMO

cat16 & 18 with MIMO

cat13 & 17 with 64QAM

cat14 & 18 with 64QAM

cat15 & 17 with MIMO

cat16 & 18 with MIMO

cat3

cat5

Cell Capacity UL cat6

cat7 with 16QAM

cat7 with 16QAM

Technical KPIs - degraded radio

Data transfer success rate

 CQI = 9

CQI = 10

CQI = 11

HTTP Throughput DL -
CQI = 12
HSDPA

CQI = 13

CQI = 14

CQI = 15

uplink pathloss = 115dB

uplink pathloss = 117dB

uplink pathloss = 119dB

uplink pathloss = 121dB

uplink pathloss = 123dB

HTTP Throughput UL -
uplink pathloss = 125dB
HSUPA cat3

uplink pathloss = 127dB

uplink pathloss = 129dB

uplink pathloss = 131dB

uplink pathloss = 133dB

uplink pathloss = 135dB

uplink pathloss = 115dB

Every
15 min KPI
 uplink pathloss = 117dB
Every
15 min KPI
uplink pathloss = 119dB

uplink pathloss = 121dB

uplink pathloss = 123dB

HTTP Throughput UL -
uplink pathloss = 125dB
HSUPA cat5

uplink pathloss = 127dB

uplink pathloss = 129dB

uplink pathloss = 131dB

uplink pathloss = 133dB

uplink pathloss = 135dB

uplink pathloss = 115dB

uplink pathloss = 117dB

uplink pathloss = 119dB

uplink pathloss = 121dB

uplink pathloss = 123dB

HTTP Throughput UL -
uplink pathloss = 125dB
HSUPA cat6

uplink pathloss = 127dB

uplink pathloss = 129dB

uplink pathloss = 131dB

 uplink pathloss = 133dB

uplink pathloss = 135dB

User oriented KPIs

Web page download success

rate

R99 DL 384

Web page download time

HSDPA

HSUPA

Data transfer success rate

HTTP Throughput DL HSDPA cat8 or better

cat 24 - Dual Carrier

KPI HTTP Throughput DL
(with 64QAM)

Every HTTP Throughput UL HSUPA cat3 or better

15 min
 Handover success rate

Interruption time Any config

Data transfer success

rate

HTTP Throughput DL

HTTP Throughput UL

Web page download

success rate
Every Realistic load - 60 users at
KPI
15 min the same time

Web page download

time

Streaming session
established, 2 minutes
with correct audio/video
quality

Streaming session
establishment time

MULTISESSION MODE
Voice call successfully
established and maintainted
during 2 minutes with good MTM
quality while downlink
transfer is running
Voice call establishment time
while downlink transfer is MTM (Mobile To Mobile)
running

Web page download success

rate while voice call is
running

R99 DL 384

Web page download time

while voice call is running

HSDPA
 HSUPA

LEGEND
Compliancy of supplier
FC Fully Compliant
PC Partialy Compliant
NC Not Compliant
 VALID IN:
LAB FIELD UE Num
Tester Num

Cell center
HW New Comment

Degraded

Cell edge
requirements
（2014/9/20）

Drive
Ideal

98% X X X

4s
X X X 2 2

4s
X X X 2 2

7s
X X X 2 2

98% X X

1,5s

X X

98% X X

2s

X X

98% X X
Nemo outdoor can't supprt 0 byte
ping function.
150 ms 2014/9/20：We could use PROBE,
Windows CMD or NEMO handy
X X 1 1 instead.

250ms
X X
 1100 ms
X X
Nemo outdoor can't supprt 0 byte
ping function.
80 ms 2014/9/20：We could use PROBE,
Windows CMD or NEMO handy
X X 1 1 instead.

150 ms
X X

1000 ms
X X
Nemo outdoor can't supprt 0 byte
ping function.
60 ms 2014/9/20：We could use PROBE,
Windows CMD or NEMO handy
X X 1 1 instead.

100 ms
X X

950 ms
X X
Nemo outdoor can't supprt 0 byte
ping function.
50 ms 2014/9/20：We could use PROBE,
Windows CMD or NEMO handy
X X instead.

80 ms
X X

950 ms
X X
0.98 X X
90% of Radio
Bearer
X X X 2 2

1,5 Mbps
X X 1 1

3 Mbps
X X 1
It need all resources of a cell for test
UE to get so high throughput, and it
is very hard to find a good point just
6 Mbps like LAB to test in field, so we
suggest to test in LAB. FT test only
in LAB also.
X X 1
It need all resources of a cell for test
UE to get so high throughput, and it
is very hard to find a good point just
8 Mbps like LAB to test in field, so we
suggest to test in LAB. FT test only
in LAB also.
X X 1
 It need all resources of a cell for test
UE to get so high throughput, and it
is very hard to find a good point just
10 Mbps like LAB to test in field, so we
suggest to test in LAB. Note: FT test
only in LAB also.
X X 1

12 Mbps Not test

X
ET did not buy MIMO licnese and
can't support MIMO function,
14 Mbps
Huawei commits to test when
X 1
applicable.
ET did not buy MIMO licnese and
can't support MIMO function,
17 Mbps
Huawei commits to test when
X applicable.
ET did not buy MIMO licnese and
can't support MIMO function,
20 Mbps
Huawei commits to test when
X
applicable.
15 Mbps Not test
X
1.ET did not buy MIMO licnese and
can't support MIMO function,
Huawei commits to test when
applicable.
18 Mbps 2.Can't find commecial UE of cat18
for test. Note: FT also not test this
case.
Huawei commits to test when
X 1 applicable.

ET did not buy MIMO licnese and

can't support MIMO function,
20 Mbps
Huawei commits to test when
applicable.
X
ET did not buy MIMO licnese and
can't support MIMO function,
24 Mbps
Huawei commits to test when
X
applicable.
Due to the TCP slow start,If we
download file which size is 100
20 Mbps Mbytes,Can't achieve the comment
value.So we suggest to download
file which size is more than 100
X 1 Mbytes,for example 200Mbytes.
Due to the TCP slow start,If we
download file which size is 100
28 Mbps Mbytes,Can't achieve the comment
value.So we suggest to download
file which size is more than 100
X 1 Mbytes,for example 300Mbytes.
 Due to the TCP slow start,If we
download file which size is 100
36 Mbps Mbytes,Can't achieve the comment
value.So we suggest to download
file which size is more than 100
X 1 Mbytes,for example 300Mbytes.

90% of Radio
Bearer
X X X 2 2

1,2 Mbps
X X 1

1,6 Mbps X X 1

4,5 Mbps X X 1
Can't find commecial UE of this cat
for test. Note: FT also not test this
8 Mbps case.
Huawei commits to test when
X applicable.
Can't find commecial UE of this cat
for test. Note: FT also not test this
10 Mbps case.
Huawei commits to test when
X applicable.

4 Mbps
X X 4 4
It need all resources of a cell for test
UE to get so high throughput, and it
is very hard to find a good point just
8 Mbps
like LAB to test in field, so we
suggest to test in LAB. FT test only
X X 4 in LAB also.
It need all resources of a cell for test
UE to get so high throughput, and it
is very hard to find a good point just
8 Mbps like LAB to test in field, so we
suggest to test in LAB. FT test only
in LAB also.
X X 4
It need all resources of a cell for test
UE to get so high throughput, and it
is very hard to find a good point just
8 Mbps
like LAB to test in field, so we
suggest to test in LAB. FT test only
X X 4 in LAB also.
It need all resources of a cell for test
UE to get so high throughput, and it
is very hard to find a good point just
10 Mbps
like LAB to test in field, so we
suggest to test in LAB. FT test only
X X 4 in LAB also.

12 Mbps Not test

X
 1.ET did not buy MIMO licnese and
can't support MIMO function,
Huawei commits to test when
applicable.
14 Mbps 2.Can't find commecial UE of cat18
X 4 for test. Note: FT also not test this
case.
Huawei commits
ET did not to test
buy MIMO whenand
licnese
applicable.
can't support MIMO function,
17 Mbps
Huawei commits to test when
applicable.
X
1.ET did not buy MIMO licnese and
20 Mbps can't support MIMO function,
Huawei commits to test when
X applicable.

15 Mbps Not test

X
ET did not buy MIMO licnese and
can't support MIMO function,
18 Mbps
Huawei commits to test when
X 4
applicable.

ET did not buy MIMO licnese and

can't support MIMO function,
20 Mbps
Huawei commits to test when
applicable.
X
1.ET did not buy MIMO licnese and
24 Mbps can't support MIMO function,
Huawei commits to test when
X applicable.

4,5 Mbps

X X 4 4

4,5 Mbps
X X 4

4,5 Mbps
X X 4
Can't find commecial UE of this cat
8 Mbps for test. Note: FT also not test this
case.
X
Can't find commecial UE of this cat
10 Mbps for test. Note: FT also not test this
case.
X

98%

X X 1 1
550 kbps
X X

650 kbps
1.Note that there will be only one
X X
test (20 samples) in edge conditions
and the CQI will be traced for each
700 kbps download. The result should be
X X inline with the associated CQI target
2.Because we can't find a point
800 kbps where CQI near 9 or 10, even in the
X X LAB, so we suggest to test CQI
between 12 and 15. For example, if
900 kbps the average CQI is 12<= CQI < 13,
X X then the throughput must bigger
than 800kbps.
950 kbps
X X

1050 kbps
X X

1200 kbps
X

1200 kbps
X

1200 kbps
X

1200 kbps
X 2014/9/20：
1.It's very difficulty to control the
1200 kbps interval of the pathloss as 2DB in
X LAB and field.So we suggest to test
for the interval of the pathloss as
10DB.
1200 kbps
2. NEMO can't suport check
X
pathloss. We could observe RSCP
instead of pathloss. The relation is:
1200 kbps pathloss = Cell Pcpich Power –
X RSCP. And test the average
pathloss.
1200 kbps
X

1200 kbps
X

1000 kbps
X

800 kbps
X

1600 kbps
X
1600 kbps
X

1600 kbps
X

1600 kbps
X 2014/9/20：
1.It's very difficulty to control the
1600 kbps interval of the pathloss as 2DB in
X LAB and field.So we suggest to test
for the interval of the pathloss as
10dB.
1600 kbps
2. NEMO can't suport check
X
pathloss. We could observe RSCP
instead of pathloss. The relation is:
1600 kbps pathloss = Cell Pcpich Power –
X RSCP. And test the average
pathloss.
1600 kbps
X

1600 kbps
X

1200 kbps
X

800 kbps
X

4500 kbps
X

4500 kbps
X

4500 kbps
X

4500 kbps
X 2014/9/20：
1.It's very difficulty to control the
4500 kbps interval of the pathloss as 2DB in
X LAB and field.So we suggest to test
for the interval of the pathloss as
10dB.
4500 kbps
2. NEMO can't suport check
X
pathloss. We could observe RSCP
instead of pathloss. The relation is:
4000 kbps pathloss = Cell Pcpich Power –
X RSCP. And test the average
pathloss.
3200 kbps
X

2200 kbps
X
1200 kbps
X

800 kbps
X

98%

X X
Nemo can't support this function to
measure downloading time.
2014/9/20: We could use other tools
like Network Monitor for test.

15s

X X 1 1
Nemo can't support this function to
measure downloading time.
5s
2014/9/20: We could use other tools
X X 1 like Network Monitor for test.
Nemo can't support this function to
4s measure downloading time.
X X 1 2014/9/20: We could use other tools
like Network Monitor or Network
98% Monitor for test.
X

2 Mbps
X 1 3
Due to the TCP slow start,If we
download file which size is 100
Mbytes,Can't achieve the comment
4 Mbps value.So we suggest to download
file which size is more than 100
X 1 Mbytes,for example 300Mbytes.

1 Mbps
X 1
 Nemo can't support this function to
measure downloading time.
98% 2014/9/20: We could use other tools
like Network Monitor for test.
X
Nemo can't support this function to
measure downloading time.
2014/9/20: We could use other tools
like Network Monitor for test.

1s X 1

It is 4 users at the same time for

test, not 60 users, please refer
<Appendix C13 E2E KPI
Definition.docx>.
98% X
Note:FT also only test 4 users for
this case.
2 Mbps 2014/9/20:Test 4 users will be ok.
X 1 4

1 Mbps X 1

Nemo can't support this function to

measure downloading time.
2014/9/20: We could use other tools
98% X like Network Monitor for test.

8s X 1

There is no streaming service by

now in worldwide, and there is no
streaming service in current ET
network now,actually all the
98% X 1
video/audio we watch on web are
interactive services.Nemo can't
support this function to measure
audio/video quality and streaming
session establishment time.

12s X

98% X X 2 2
7s

X X
Nemo can't support this function to
measure downloading time.
2014/9/20: We could use other tools
98% like Network Monitor for test.

X X
Nemo can't support this function to
measure downloading time.
2014/9/20: We could use other tools
like Network Monitor for test.

15s

X X 1
Nemo can't support this function to
measure downloading time.
2014/9/20: We could use other tools
like Network Monitor for test.

5s

X X 1
 Nemo can't support this function to
measure downloading time.
2014/9/20: We could use other tools
like Network Monitor for test.

4s

X X 1
 Agreement with TEP
Actix Formula
KPI formula

2014/09/25：In ET ,with good

quality is means MOS score
>=3.2;HUAWEI should review Success
to test MOS score,because this Times/Attempt
is not find in the contract ,and Between
Times "RRC
FT did not test also; Connection
2014/07/24：during 2 minutes Request" in 3G
2014/10/03：ET
with good qualityagreed
meanswiththe or “Channel
MOC can usecall
two phones 118.
2 minutes Uu_TimeBetweenRRC_REQandCallStar request” in 2G
2014/09/25：In
without drop t
ET ,with good and “CC
quality is means MOS score Alerting", for
>=3.2;HUAWEI should
2014/10/03：ET agreedreview
with Between
MOC and first
MTM
Between first “Paging” and “CC Between
“Paging” "RRC
and
calls (calling
to test
MTC can MOSusescore,because
fixed line. this
Alerting” for MTC calls. Connection
“CC Alerting”
part).
is not find in theET
2014/09/25：In contract ,and
,with good
Request" in 3G
for MTC calls.
FT did not
quality test also;
is means MOS score
2014/09/25：In ET ,with good or “Channel
2014/07/24：during
>=3.2;HUAWEI should 2 minutes
review
quality is means MOS Uu_TimeBetweenRRC_REQandCallStar request” in 2G
score
with good quality means
to test MOS score,because thethis
>=3.2;HUAWEI t and “CC
two
is phones
not theshould
find incall 2contract
minutesreview
,and
to test MOS score,because this Alerting", for
without
FT did notdrop
test also;
is not find in the contract ,and MOC and MTM
2014/07/24：during 2 minutes
FT did not quality
test also; calls
The (calling
with good means the
2014/07/24：during 2 minutes part).
corresponding
two phones call 2 minutes
with good
without drop quality means the connection
two phones call 2 minutes (NemoEvent_GPRS_AttachConnected_GAC /NemoEvent_
times are
without drop
2014/09/25：Partly Accept. ET measured from
agree with test R99 , HSPA+ The corresponding connection times mobile traces
,HSUPA , HSDPA . The cat of are measured from mobile traces between first
HSUPA is cat6.The cat of HSDPA between first "RRC Connection "RRC
is cat10.The cat of HSPA+ is Request" [3G] or “Channel request” Connection
cat14. [2G] and first “Attach Complete”. The
Request" [3G]
corresponding
or “Channel
activation
request” [2G]
times are
and first
PDP Activation Complete/PDP Activationmeasured
Request from
“Attach
2014/09/25：Partly Accept. ET RNC ue_trace
Complete”.
agree with test R99 , HSPA+ between first
,HSUPA , HSDPA . The cat of "RRC
HSUPA is cat6.The cat of HSDPA Average(PDP context activation time) Connection
is cat10.The cat of HSPA+ is Request" [3G /
cat14. HsxPA] or
“Channel
Success Times/Attempt Times request” [2G]
and “PDP
accept”
2014/10/03：ET agree with test messages.
by windows CMD and trace log
by NEMO when ping 0B. Ping_RTT

Ping_RTT
2014/09/25：The interval for
the two test PING should check , just
with ET;
2014/10/03：ET agree with test
by windows CMD and trace log
by NEMO when ping 0B. Ping_RTT

Ping_RTT

2014/09/25：The interval for

the two test PING should check Ping_RTT
with ET;
2014/10/03：ET agree with test
by windows CMD and trace log
by NEMO when ping 0B. Ping_RTT

Ping_RTT

2014/09/25：The interval for

the two test PING should check Ping_RTT
with ET;
2014/10/03：ET agree with test
by windows CMD and trace log
by NEMO when ping 0B. Ping_RTT

Ping_RTT

2014/09/25：The interval for

the two test PING should check Ping_RTT
with ET;

Accepted Average( App_Throughput_DL )

Test will be done in Midnight for

Average( App_Throughput_DL )
Cell Center Test.

Test will be done in Midnight for

Average( App_Throughput_DL )
Cell Center Test.

2014/09/25:Suggest to discuss
next time;
Average( App_Throughput_DL )
Test will be done in Midnight for
Cell Center Test.

2014/09/25:Suggest to discuss
next time;
Average( App_Throughput_DL )
Test will be done in Midnight for
Cell Center Test.
2014/09/25:Suggest to discuss
next time;
Average( App_Throughput_DL )
Test will be done in Midnight for
Cell Center Test.

2014/10/02:ET need check

those UE

Accepted Average( App_Throughput_DL )

Accepted

Accepted

2014/10/02:ET need check

those UE

2014/10/02:ET need check

Average( App_Throughput_DL )
cat18 UE

Accepted

Accepted

Average( App_Throughput_DL )

2014/09/25:Accepted

Average( App_Throughput_DL )

2014/09/25:Accepted
 Average( App_Throughput_DL )

2014/09/25:Accepted
2014/10/01: ET agreed with
test only for 384(Kbit/s).90% of
Average( App_Throughput_UL )
Radio Bearer means
384(Kbit/s)*90%=345(Kbit/s).

Test will be done in Midnight for

Average( App_Throughput_UL )
Cell Center Test.

Average( App_Throughput_UL )

Average( App_Throughput_UL )

2014/09/25: ET will check and

answer tomorrow

2014/09/25: ET will check and

answer tomorrow

Not acceptable for UE Issue.

Test will be done in Midnight for SUM(Average( App_Throughput_DL ))
Cell Center Test.

Not acceptable for UE Issue.

Test will be done in Midnight for SUM(Average( App_Throughput_DL ))
Cell Center Test.

Not acceptable for UE Issue.

SUM(Average( App_Throughput_DL ))
Test will be done in Midnight for
Cell Center Test.

Not acceptable for UE Issue.

Test will be done in Midnight for SUM(Average( App_Throughput_DL ))
Cell Center Test.

Not acceptable for UE Issue.

Test will be done in Midnight for SUM(Average( App_Throughput_DL ))
Cell Center Test.

Accepted
2014/10/02:ET need check
SUM(Average( App_Throughput_DL ))
cat18 UE

Accepted

Accepted SUM(Average( App_Throughput_DL ))

Accepted

SUM(Average( App_Throughput_DL ))
Accepted

Accepted

Accepted SUM(Average( App_Throughput_DL ))

Test will be done in Midnight for

SUM(Average( App_Throughput_DL ))
Cell Center Test.

SUM(Average( App_Throughput_DL ))

SUM(Average( App_Throughput_DL ))

2014/10/02:ET need check this

UE
2014/09/25: ET will check and
answer tomorrow
2014/10/02:ET need check this
UE
2014/09/25: ET will check and
answer tomorrow

1-[Count(Nemo_Data_Transfer_Status!
=1)/Count(NemoEvent_DataTransferR
equest_DREQ)]
and cat24 for test.
2014/10/01: Average( Physical_Throughput_DL )
1.ET agreed with the test
method: We test (20 samples)
in edge conditions for a CAT.
Average( Physical_Throughput_DL )
For each samples we count the
average CQI and the average
throughput ,the average
throughput should achieve the Average( Physical_Throughput_DL )
requirements for the average
CQI . At the end ,we count the
the average CQI and the Average( Physical_Throughput_DL )
average throughput for 20
sample's results. The average
throughput for 20 sample's Average( Physical_Throughput_DL )
results must achieve the
requirements for the average
CQI for the 20 sample's also.
Average( Physical_Throughput_DL )
For example, if the average CQI
is 12<= CQI < 13, then the
throughput must bigger than
800kbps. Average( Physical_Throughput_DL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

2014/10/02:ET persist test all.If Average( App_Throughput_UL )

can't control the interval for
2db,can discuss that time.
2014/10/01:The interval of Average( App_Throughput_UL )
pathloss need discuss tomorrow
2014/09/25: ET will check and
answer tomorrow Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )
 Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

2014/10/02:ET persist test all.If Average( App_Throughput_UL )

can't control the interval for
2db,can discuss that time.
2014/10/01:The interval of Average( App_Throughput_UL )
pathloss need discuss tomorrow
2014/09/25: ET will check and
answer tomorrow Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )

2014/10/02:ET persist test all.If Average( App_Throughput_UL )

can't control the interval for
2db,can discuss that time.
2014/10/01:The interval of Average( App_Throughput_UL )
pathloss need discuss tomorrow
2014/09/25: ET will check and
answer tomorrow Average( App_Throughput_UL )

Average( App_Throughput_UL )

Average( App_Throughput_UL )
 Average( App_Throughput_UL )

Average( App_Throughput_UL )

The percentage
of web page
downloaded
successfully at
Success Times/Attempt Times
the first
attempt is
2014/09/25:Accepted evaluated by
2014/09/25:Accepted the
Web test
pageleader.
download times
are calculated
with Network
Monitor on
laptop between
the DNS
resolution of
the page name
and the last
Average(File transfer download time)
TCP ACK of the
last object of
the
Web page
downloaded
download times
page. If no DNS
are calculated
resolution is
with Network
needed,
Web page then
Monitor on
the first “TCP
download times
laptop between
SYN”
are is
calculated
the DNS
considered.
with Network
resolution of
Monitor
the pageon name
laptop
and thebetween
last
2014/10/02:ET Accepted we ue
Average(File transfer download time) the DNS
cat10 TCP ACK of the
resolution
last object of of
2014/09/25:Accepted
2014/10/02:ET Accepted we ue the
the page name
cat6 and the last
Average(File transfer download time) downloaded
2014/09/25:Accepted TCP
page. ACK
If noof DNS
the
last object of
1-[Count(Nemo_Data_Transfer_Status! resolution
the
is
needed,
=1)/Count(NemoEvent_DataTransferR downloaded then
equest_DREQ)] the first “TCP
page.
SYN” isIf no DNS
resolution
considered. is
Average( App_Throughput_DL ) needed, then
2014/10/02:ET Accepted we ue c the first “TCP
SYN” is
considered.

Average( App_Throughput_DL )

2014/09/25:Accepted

Average( App_Throughput_DL )
2014/10/02:ET Accepted we ue c
 interruption
time is
evaluated by
the test leader.
This
2014/09/25:Accepted. we can interruption
The percentage
choose only one configuration time is
of handover
for test; Success Times/Attempt Times measured
success rate at is
application
evaluated by
This interruption time is measured at level with
the test leader.
2014/10/04:ET agreed with the application level with Network Monitor Network
count method:first find the HO between last TCP packet received by Monitor
Command time , the time the mobile on initial cell and first TCP between last
nearby HO Command time in packet received by the mobile on TCP packet
the Network Monitor log is the target cell. This will be a full TCP received by the
handover time range, Then frame (user plan) for downlink mobile on
count the tinerruption time as transfer, and TCP ACK for uplink initial cell and
the contract . transfer. first TCP packet
2014/09/25:Accepted. we can received by the
choose only one configuration 1-[Count(Nemo_Data_Transfer_Status! mobile on
for test; =1)/Count(NemoEvent_DataTransferR target cell. This
equest_DREQ)] will be a full
TCP frame
(user plan) for
downlink
2014/10/02:ET agree with test transfer, and
Average( App_Throughput_DL )
for cat14 TCP ACK for
uplink transfer.
2014/10/02:ET agree with test
Average( App_Throughput_UL )
for cat6
The percentage
Web page
of web page
download times
downloaded
are calculated
successfully at
Success Times/Attempt Times with Network
the first
Monitor on
attempt is
laptop between
evaluated by
2014/09/25:Accepted the DNS
the test leader.
resolution of
the page name
and the last
Average(File transfer download time)
TCP ACK of the
The percentage
last object of
of
thestreaming
session
downloaded
The streaming
established,
page. If no DNS2
session
minutes with
Success Times/Attempt Times resolution
establishment is
2014/09/25: Accepted.we correct
needed, then
should chose the streaming duration
audio/video is
the first “TCP
calculated
service vidio and check with ET. quality
SYN” is is from
The streaming session manually
evaluated by
considered.
the
establishment duration is the mobile with
test leader.
a stopwatch.
calculated manually from the
mobile with a stopwatch,this The duration is
can supervise for ET engineer. Time evaluate by Stop Watch considered
between the
sending of the
request and
the correct
display of the
first image of
the video on
the mobile
screen.

(NemoEvent_OutgoingCallSetupSuccess_CAC)/( NemoEv
 Between RRC
request in
"Initial Direct
Time of Alerting - Time of RRC request Transfer" Msg
in Initial Direct Transfer Msg and “CC
Alerting", for
MTM calls
(calling part).
The percentage
of web page
downloaded
successfully at
Success Times/Attempt Times
the first
attempt is
evaluated by
2014/09/25:Accepted the test leader.
2014/09/25:Accepted Web page
download times
are calculated
with Network
Monitor on
laptop between
the DNS
resolution of
the page name
and the last
Average(File transfer download time)
TCP ACK of the
last object of
the
downloaded
page. If no DNS
resolution is
needed, then
the first “TCP
SYN” is
considered.
Web page
download times
are calculated
with Network
Monitor on
laptop between
the DNS
resolution of
the page name
and the last
Average(File transfer download time)
TCP ACK of the
last object of
the
downloaded
page. If no DNS
resolution is
needed, then
2014/10/02:ET Accepted we ue the first “TCP
cat10 SYN” is
2014/09/25:Accepted considered.
 Web page
download times
are calculated
with Network
Monitor on
laptop between
the DNS
resolution of
the page name
and the last
Average(File transfer download time)
TCP ACK of the
last object of
2014/10/02:ET Accepted we ue the
cat6 downloaded
2014/09/25:Accepted page. If no DNS
resolution is
needed, then
the first “TCP
SYN” is
considered.
 SUPPLIER COMMITMENTS

Value in
Value in Compliancy
Compliancy in Release Comment or additional
Release N in Release
Release N. N+1 information
(if PC) N+1.
(if PC)

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC
FC

FC

FC

FC

FC

FC

FC

FC

FC

FC
FC

FC

FC

FC

FC

FC
FC
Currently there is no Cat
13&17 commercial
terminal.
Huawei commits to test
FC when applicable.

FC
Currently there is no Cat
15&17 commercial
terminal.
Huawei commits to test
FC when applicable.

Currently there is no Cat

FC 13&17 commercial
terminal.
Huawei commits to test
FC when applicable.

FC

Currently there is no Cat

15&17 commercial
terminal.
Huawei commits to test
FC when applicable.

FC

FC

FC
FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

Currently there is no Cat

13&17 commercial
terminal.
Huawei commits to test
FC when applicable.
FC

Currently there is no Cat

15&17 commercial
terminal.
Huawei commits to test
FC when applicable.

FC

Currently there is no Cat

13&17 commercial
terminal.
Huawei commits to test
FC when applicable.

FC

Currently there is no Cat

15&17 commercial
terminal.
Huawei commits to test
FC when applicable.

FC

Huawei commits 3Mbps

in LAB-Ideal and Cell
NC 3 Mbps center scenario.

FC

FC

Huawei commits 6Mbps

NC 6 Mbps in Cell center scenario.

Huawei commits 6Mbps

NC 6 Mbps in LAB-Ideal scenario.

FC
FC Physical layer throughput.

FC Physical layer throughput.

FC Physical layer throughput.

FC Physical layer throughput.

FC Physical layer throughput.

FC Physical layer throughput.

FC Physical layer throughput.

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC
FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC

FC
FC

FC

FC

FC

FC

FC

FC

FC

FC

FC
FC

FC

FC

FC

FC

FC

FC

FC

FC

FC
FC

FC

FC

FC
FC
 ETHIOTELECOM
REQUIREMENTS

Name
Brief description, details
3G-2G REQUIREMENTS
CIRCUIT MODE

Intersystem
handover
success rate from 3G to 2G
Every
KPI
15 min
Intersystem
handover from 2G to 3G
interruption
time from 3G to 2G

from 2G to 3G
PACKET MODE

Intersystem cell
reselection
success rate from 3G to 2G

from 2G to 3G
Intersystem
interruption from 3G to 2G -
time downlink
from 3G to 2G - uplink
from 2G to 3G -
downlink

from 2G to 3G - uplink
LEGEND
Compliancy of supplier
FC Fully Compliant
PC Partialy Compliant
NC Not Compliant
 VALID IN:

LAB FIELD

requirements

Cell center
Degraded

Cell edge

Drive
Ideal

0.98 X X

0.98 X X

250 ms X X

300 ms X X
 0.98 X X

0.98 X X

20 s X X
20 s X X

20 s X X

20 s X X
Actix does not
support the test
scenario.
Huawei Comments
2014/9/20:
20140920 We

could count the

intersystem
handover
interruption
time by NEMO
log. The
interruption
time is
measured from
mobile traces,
between “HO
Command” and
“HO Complete”
2014/9/20: Not
messages.
open in the
field,so can't
test in the field;
but should test
in the lab;
NEMO does not
NEMO
supportdoes not
the test
support
scenario. the test
NEMO
NEMO
scenario.does
does not
not
2014/9/20:
support the We
test
support
2014/9/20:
could usethe test
We
other
scenario.
scenario.
could use other
tools like
2014/9/20: We
2014/9/20:
tools
Networklike We
could
could
Network use
use other
other
Monitor
tools like for
tools
Monitor
test. like for
Network
Network
test.
2014/9/20:
Monitor for Not
Monitor
open for
in the
test.
test.
field,so
2014/9/20:can'tNot
test
openininthe
thefield;
but should
field,so test
can't
in the
test inlab;
the field;
but should test
in the lab;
 Agreement with TEP

2014/09/25:ET Accepted:1.We could count the inter

interruption time by NEMO log. The interruption tim
from mobile traces, between “HO Command” and “
messages.
2014/09/25:ET Accepted:1.We could count the inter
2.we can't test
interruption from
time by 2G to 3G
NEMO in The
log. FIELD.
interruption tim
from mobile traces, between “HO Command” and “
messages.
2.we can't test from 2G to 3G in FIELD.
2014/09/25:Accepted
2014/10/04:ET agreed with the count method:first fi
2014/09/25:ET
Command timeAccepted
, the timewenearby
can'tHO
testCommand
from 2G to
tim3G
2014/10/04:ET
Monitor log is theagreed with the
handover timecount
range,method:first
Then countfi
Command
time as the time ,
contractthe time nearby HO Command
.2014/09/25:Accepted.
2014/10/04:ET agreed with the count method:first fiwe tim
can
Monitor logtime
configuration
Command isfor
the handover
test;
, the time range,
time nearby Then count
HO Command tim
time as
Monitor the contract
log is the .2014/09/25:Accepted.
handover timecount
range, we can
Then countfi
2014/10/04:ET
configuration agreed
for test; with the method:first
time as thetime
Command contract
, the .2014/09/25:Accepted.
time nearby HO Command we can
tim
configuration
Monitor log isforthetest;
handover time range, Then count
2014/09/25:ET Accepted
time as the contract we can't test from 2G
.2014/09/25:Accepted. we to
can3G
configuration for test;
2014/09/25:ET Accepted we can't test from 2G to 3G
 SUPPLIER COMMITMENTS

Value in Value in
Comment or
Compliancy in Release Release Compliancy in Release Release
additional
N. N N+1. N+1
information
(if PC) (if PC)

FC

FC

FC

FC
FC

FC

FC

FC

FC

FC