Cluster Acceptance Criteria

KPI No KPIs
URBAN SUBURBAN RURAL

4G KPI-1 MO/MT CSFB Call Setup Success Rate (CSSR) > 99.2% > 99.0% > 98.8%

<=6 sec <=7 sec <=8 sec

4G KPI-2 MO/MT CSFB to 3G Call Set Up Time (s)

With Fast
Return With Fast Return With Fast Return
Feature <= Feature <= 3sec. Feature <= 4sec.
2sec.
Time to return to 4G network after CSFB call
4G KPI-3 release in 2G network
Without Fast
Return <= 25 Without Fast Return Without Fast Return
<= 28 sec <= 30 sec
sec

With Fast
Return With Fast Return With Fast Return
Feature <= Feature <= 3sec. Feature <= 4sec.
Time to return to 4G network after CSFB call 2sec.
4G KPI-4 release in 3G network Without Fast
Return <= 10 Without Fast Return Without Fast Return
<= 11 sec <= 12 sec
sec

10MHz > 10MHz > 30Mbps 10MHz > 30Mbps

30Mbps

CA (2x10MHz) CA (2x10MHz) - 50 CA (2x10MHz) - 50

- 50 Mbps Mbps Mbps

4G KPI-5 DL Throughput
CA
(10+15MHz) - CA (10+15MHz) - 65 CA (10+15MHz) - 65
Mbps Mbps
65 Mbps

CA
(10+10+15MH CA (10+10+15MHz) - CA (10+10+15MHz) -
85 Mbps 85 Mbps
z) - 85 Mbps
 10MHz >
4G KPI-6 UL Throughput 10MHz > 10Mbps 10MHz > 10Mbps
10Mbps

Part1 35 35 35

Latency (ms) -
4G KPI-7 Median

Part2 45 50 50

<=1 <=1 <=1

4G KPI-8 VOLTE - Call Setup Time (s)

4G KPI-9 VOLTE Drop Rate % <0.5 <0.8 <1.2

VOLTE Accessibility
4G KPI -10 Start trigger: INVITE sent by MO 99.0% 98.8% 98.5%
•End trigger: Ringing received by MO

4G KPI-11 MOS Speech Quality 3.75 3.70 3.65

Only for
4G KPI-12 Voice Call Speech Quality Non-Sustainability [%] Only for reporting Only for reporting
reporting

Codec MOS Only for

4G KPI-13 Only for reporting Only for reporting
Reporting reporting
 Criteria Comments and Exclusions

LTE CSFB: EMM Extended

Service Request Failures related to 2G/3G and UE
End trigger: Alerting (B- problems shall be excluded.
Party is ringing)

LTE CSFB: EMM Extended Paging cycle latency of LTE network

Service Request
End trigger: Alerting (B- will not be more than 1.28 second
Over delays due to backhaul and
Party is ringing) core network problems shall be
excluded

Start Trigger:
Last 3G RRC
Messeage / Last 2G RR
Message
Stop Trigger:
LTE: First RRC
message

PS data cycle is composed

of HTTP 3 MB DL and
HTTP 1 MB UL as well as
HTTP 10s Stress test
[400MB] for UL and DL

- Vendor is supposed to
suggest HTTP DL file size if
the CE test file dimension
(3MB) is too small to allow
massive activation of CA Stress test file size might be
increased in case of need.
• Refers to the average
data throughput calculated
on sequence basis and
without retransmissions
• Only successful
sequences are taken into
account (for failed
sequences in the transfer
phase no Mean Data Rate
will be calculated)
PS data cycle is composed
of HTTP 3 MB DL and
HTTP 1 MB UL as well as
HTTP 10s Stress test
[400MB] for UL and DL
Refers to the average data
throughput calculated on
sequence basis and
without retransmissions
• Only successful
sequences are taken into
account (for failed
sequences in the transfer
phase no Mean Data Rate
will be calculated)

Time between:
Client sends ICMP echo
request
Client receives ICMP echo
reply Part1 and Part2 clusters will be
provided by VGC according to the
The recommended actual transmisson performance
number of measurements
Service
per IPNon-Accessibility:
host is ≥ 100
Start trigger: INVITE
sent by MO
End trigger: Ringing
received by MO
Service Access Time:
Start trigger: INVITE
sent by MO
End trigger: Ringing Over delays due to backhaul and
received by MO core network problems shall be
Cut-off Call Ratio and Call excluded
Duration
Start trigger: 200 OK
(INVITE) sent by MO /
received by MT
End trigger: BYE
sent/received by MO or
MT
Service
The VOLTE Access<-> Time
VOLTEB
Start trigger:
scenarios replacesUserthe
presses the dialspeech
narrow-band button
sample End trigger:
with a superRinging
wide-
bandreceived
one inby MO to
order
assess “HD voice”. In this
case,
WB Speechthe speech
Quality quality
Non
assessment
Sustainability shall
[%]be
performed
– A “FALSE” using P.OLQA
Call/not
wide-band
Sustainable(ITU is a Rec.P.863).
call where
The speech sample
2 consecutive voiceis 23.85 HD voice codec can be used
super-wideband
samples MOS English is < 1.6 @
(Polqa 14wideband
KHz
reference)
Call window
–• 2 consecutive samples,
onoCall setupthe
matter time:
direction
20s (timeout)
(DL-UL / UL-DL) OR
–•o Call duration: samples
2 consecutive
120s
in the same direction (DL-
o Call DLwindow:
/ UL-UL)
– OR 5 or180s more voice
samples MOS < 1.6
– Sustainability to be
calculated as: FALSE /
(TRUECodec based MOS
+ FALSE)* 100 [%]
– reporting
Drop Callsisnot suggested
included
in the KPI calculation
– Denominator: completed
calls
 Requirement for Scenarios Formula
Stat. on UE side:
1）Success Rate = Number of Success / Number of
Attempt ×100%
Definition : UE sents extend service request in LTE cell,
number of attempt is incremented by 1;
UE sends/receives Alerting in WCDMA cell, number of
success is incremented by 1;
Stat. on UE side:
1）Success Rate = Number of Success / Number of
Attempt ×100%
Definition : UE sents extend service request in LTE cell,
number of attempt is incremented by 1;
UE sends/receives Alerting in GERAN cell, number of
success is incremented by 1;

1)Use R9 Redirection
2)Location updated should be excluded
3）WCDMA Call Setup Latency condition:
MTM(3G-3G)<4s(DT),the time longer than 4s should be subtracted.
4)HSS and HLR should be Converged.
Measuredin UE side:
From:UE sends Extend Sevice Request message in LTE
To:UE receives ALERTING message in WCDMA

1)The quantity neighbor should less than 20.If the total neighbor is
more than 20, our proposal is 36s(urban).
2)Even the reselection from 2G to 4G, because the neighbor includs (4G)RRC connection request-(2G)channel release
3G+4G, suggest to keep the above condition 1)

(4G)RRC connection request-(3G)RRCconnection Release

1）CFI adaptation and Initial CFI=1

2）UE should work with multithreading for downloading;
3）DL throughtput and UL throughput should be tested independently;
4)Intra eNB CA
5)Under the condition of Planning and actual average SINR should
>=17dB,can met the DL target.
6)If the SINR<17dB and >=13dB, the proposal should be
DL(10Mbandwidth)
25Mbps.,CA(10M+10M)41.7Mbps,CA(10M+15M)54.2Mbps,CA(10M+10
M+15M)70.8Mbps
7)If the SINR < 13dB, the proposal is DL(10Mbandwidth)
21Mpbs,CA(10M+10M)37.8Mbps,CA(10M+15M)46.8Mbps,CA(10M+10
M+15M)62.05Mbps
8) Samples with SINR<3 dB or RSRP<-100 dBm shall excluded from
average throughput calculation
9) After 1st of April, throughput targets will be modified based on
drivetest hours' average PRB utilisation,
if PRB utilisation is <= 5% , targets will be decreased 5%
if PRB utilisation is > 5% and <=10%, targets will be decreased 12%
if PRB utilisation is > 10% and <=15%, targets will be decreased 20%
if PRB utilisation is > 15%, targets will be decreased based on the
utilisation value(U), degradation will be 22+2*(U-15)
After 1st of April, throughput targets will be modified based on drivetest
hours' average PRB utilisation,
if PRB utilisation is <= 5% , targets will be decreased 5%
if PRB utilisation is > 5% and <=10%, targets will be decreased 12%
if PRB utilisation is > 10% and <=15%, targets will be decreased 20%
if PRB utilisation is > 15%, targets will be decreased based on the
utilisation value(U), degradation will be 22+2*(U-15)

1) Number of service drop / Number of total service

connection x 100%;
2) Number of total service connection: number of times
a UE receives an Alerting while Service request or the
1)under the active state ping 32byte with pre-schduling. number of times a UE entering normal user-plane data
2)the transmission latency(eNB to Ping server) should be less than transmission state after it receives
5ms,If the latency is over 5ms and this KPI test result can not meet the RRCConnectionReconfiguration (containing drb-
target, suggest to subtract the latency part which is more than 3ms from ToAddModList or drb-ToAddModifyList) and responds
the test result with RRCConnectionReconfigurationComplete.
3)Configured by HW baseline parameter value (such as UL pre- 3) Number of service drop: Based on the Uu signaling
scheduling switch is ON,and DRX switch is OFF); messages recorded on the UE side, if the signaling
4)Connect server with PGW directly; messages meet any of the following two scenarios during
5)If the the transmission latency(eNB to Ping server) can be less than a call (the UE is in the connected mode), the number of
5ms, the result can be 35ms. service drops is incremented by one:
6) Or we test the latency from the UE to eNB, the one way latency can Scenario A: There are release messages over the Uu
less than 15ms. interface but without
from sending reasons.to
"PING Request" Therefore,
receivingNAS signaling
"PING Reply"
active state to active state; messages must also be considered to determine whether
1）the transmission latency (eNB to IMS) should be less than a release is normal or not. Basic rule for judgement: If UE
5ms,If the latency is over 5ms and this KPI test result can not receives an RRC Connection
Measured in Release on air interface but
UE side:
meet the target, the time longer than 5ms should be there is noFrom
NASA:UE
message
sendindicating
SIP INVITEDRB release, we can
message
subtracted. determine that this
To B:UE receives SIPis 180
an abnormal release.
Ringing message
2)One iFC triggering for all service Scenario B: A UE in a service
Formula:B-Aprocess migrates from the
(LTE UE->LTE UE) connected mode to the idle mode without receiving an
RRC Connection Release.
Note: If an RRC connection reestablishment is trigged on
the UE side and the reestablishment is successful, the
1) all clusters are urban. service drop is not counted.
(OC: mobile, OT: mobile)
1) Oringinal Call Setup Success Rate = number of OC
setup success / number of total OC setup attempt x 100%
2) Number of total OC setup attempt is number of SIP
INVITE
3) Number of OC setup success is number of SIP 180
Ringing message

1）Testing tools and voice sample selected can reach peak MOS to 4.2;
2）Packet Loss Rate of core is less than 0.001%.
 1

2
3
4
5
6
7
8

10

11

12
13
14
15
16

17

18

Definition of URBAN
Definition of SUBURBAN
Definition of RURAL
For E2E KPIs, the samples that do not meet; GSMRxlevel >=-90dBm , UMTS:RSCP≥-95dBm or EcNo>-16, LTE: RSRP>-100dBm or SINR>
will be excluded. SGC may suggest routes for the clusters, VGC has the right to give the final decision.

KPI fluctuation due to engineering implementation should be excluded(such as network upgrade/capacity expansion/network restruct

If the bad KPI is caused by a worst cell has poor coverage, SGC and VGC will discuss case by case.
KPI abnormality caused by network congestion should be excluded;
KPI abnormality caused by non-SGC's equipment should be excluded(such as MME/transmission /UE/BTS/NODEB).2G/3G performance
be provided in case of need
Number of samples for the cluster PM KPIs should be more than 5,000;(all monitoring period total)
Network problems arising due to implementation delays from VGC
KPI degradations due to external limitations such as the Transmission Links(not more than 5ms). Readiness of FTTS will be checked in c
need.
Considering the new market policy issued by ‘operator’ (example: free call, etc.) and cause burst traffic happened which affect the curr
network performance seriously, VGC should inform SGC in advance and negotiate the optimization KPI baseline together or VGC should
SGC hardware/software expansion proposal for network performance guarantee.
External interference problems caused by other systems or sources which happen at frequent / repetitive intervals.
Performance degradation for a new geographical area, where it is proved that a new site(s) is needed, will be excluded from the KPI
measurements / reports. However SGC will put all optimization efforts in reducing the impact due to traffic from such areas on perform
network level
KPI decrease caused by co-frequency or adjacent-frequency interference brought by re-farming requested by Customer other than 10/
for GSM900
Planned downtime and activities (e.g. software upgrades) that have an impact on SLA and/or KPI performance.
KPI degradations due to the traffic model/coverage area change which exceeds System Planning capacity.
Change Requests made by Operator which have a direct impact on KPI performance measurement
Natural disasters or emergency situations announced by the government.
Major or special events (National and Religious Days, Meeting etc.) of which general traffic trend are affected such that the NW is subje
traffic demand. However as per the scope, SGC would implement necessary changes in the network and optimize to the best capacity f
event, if pre-informed.

Failures as results of any external factors (such as Force Majeure, problems related to Non-SGC scope, vandalism, extreme bad weathe
be presented to VGC with valid proofs. SGC will do their best in investigating such issues so as to reduce the impact.

On the cell edge RSRP value is greater than -87dBm

On the cell edge RSRP value is greater than -95dBm
On the cell edge RSRP value is greater than -100 dBm
Appendix A_VGC-KPI A1 E2E KPIs 6a
"Minimum 100 samples for each service" is changed to "Minimum 100 samples for each service regarding cluster end to end K