KQI/KPI

1 Overall Temporary Block Flow Success Rate (%)

2 Temporary Block Flow (TBF) Uplink Success Rate (%)

3 Temporary Block Flow (TBF) Downlink Success Rate (%)

4 Temporary Block Flow Drop Rate (%)

5 PDCH Allocation Success Rate (%)

6 PDCH Occupancy (%)

7 RLC Uplink Data Volume (Kbits) - GPRS

8 RLC Uplink Data Volume (Kbits) - E-GPRS

9 RLC Downlink Data Volume (Kbits) - GPRS

10 RLC Downlink Data Volume (Kbits) -E- GPRS

11 Average DL GPRS Throughput (Kbits/s)

12 Average UL GPRS Throughput (Kbits/s)

13 Average DL EDGE Throughput (Kbits/s)

14 Average UL EDGE Throughput (Kbits/s)

15 GPRS Max Active Users

16 E - GPRS Max Active Users

17 GPRS Avg Active Users

18 E - GPRS Avg Active Users

19 GPRS Max Attached Users

20 E - GPRS Max Attached Users

21 GPRS Avg Attached Users

22 E - GPRS Avg Attached Users

23 TBF Blocking Rate (%)

 SQM Definition
Overall TBF SR = (TBF Uplink Successes + TBF Downlink Successes) / (TBF Uplink
Attempts + TBF Downlink Attempts)

1) For TBF Uplink Successes and Attempts, refer to Temporary Block Flow (TBF)
Uplink Success Rate (%).
2) For TBF Downlink Successes and Attempts, refer to Temporary Block Flow (TBF)
Downlink Success Rate (%).

Uplink TBF SR = TBF Uplink Successes / TBF Uplink Attempts

1) TBF Uplink Attempts should use Requests, not Allocations. Includes Preparation
failures.

Downlink TBF SR = TBF Downlink Successes / TBF Downlink Attempts

1) TBF Downlink Attempts should use Requests, not Allocations. Includes Preparation
failures.

TBF DR = (TBF Abnormal Drops) / (TBF Abnormal Drops + TBF Normal Drops)

1) Includes drops for Uplink and Downlink.

2) Should include all available failure causes
3) Abnormal and Normal Drops should add Incoming Handovers
4) Abnormal and Normal Drops should substract Outgoing Handovers
5) Mapping required in counter form

PDCH Allocation SR = PDCH Successes / PDCH Attempts

1) PDCH Attempts should use Requests, not Allocations. Include Preparation failures.

PDCH Occupancy SR = PDCH Occupied / PDCH Available

1) PDCH Available should map to total PDCH capacity for the cell
2) PDCH Occupied should include allocated PDCHs for the measurement interval
only
Data Volume for GERAN Uplink in Kbits

1) Should contain GPRS data

2) Should include Uplink data only.
3) Should be measured at RLC Level
4) Should contain payload data only.
5) Does not fulfil (3). Measured at LLC, not RLC.
6) Confirmation on Unit Required.
7) Should include acknowledged and unacknowledged traffic.

Data Volume for GERAN Uplink in Kbits

1) Should contain E-GPRS data

2) Should include Uplink data only.
3) Should be measured at RLC Level
4) Should contain payload data only.
5) Does not fulfil (3). Measured at LLC, not RLC.
6) Confirmation on Unit Required.

Data Volume for GERAN Downlink in Kbits

1) Should contain GPRS

2) Should include Downlink data only.
3) Should be measured at RLC Level
4) Should contain payload data only.
5) Does not fulfil (3). Measured at LLC, not RLC.
6) Confirmation on Unit Required.
7) Should include acknowledged and unacknowledged traffic.

Data Volume for GERAN Downlink in Kbits

1) Should contain E-GPRS

2) Should include Downlink data only.
3) Should be measured at RLC Level
4) Should contain payload data only.
5) Does not fulfil (3). Measured at LLC, not RLC.
6) Confirmation on Unit Required.
Throughput for GPRS Download (Kbits/s) = [RLC Downlink Data Volume (Kbits) -
GPRS] / [Transfer Time]

1) Should contain GPRS throughput at cell level.

2) Should include Downlink data only.
3) Transfer Time should ONLY include the time spent in Active State during which
data was transferred
4) Transfer Time should NOT include time spent in Idle or Standby state.
5) Transfer Time should NOT include time in Active State while waiting for packet
paging.
6) Mapping required in counter form
7) Confirmation on Unit Required
8) Should include acknowledged and unacknowledged traffic

Throughput for GPRS Upload in Kbits/s = [RLC Uplink Data Volume (Kbits) - GPRS] /
[Transfer Time]

1) Should contain GPRS throughput at cell level.

2) Should include Uplink data only.
3) Transfer Time should ONLY include the time spent in Active State during which
data was transferred
4) Transfer Time should NOT include time spent in Idle or Standby state.
5) Transfer Time should NOT include time in Active State while waiting for packet
paging.
6) Mapping required in counter form
7) Confirmation on Unit Required
8) Should include acknowledged and unacknowledged traffic

Throughput for E-GPRS Download in Kbits/s = [RLC Downlink Data Volume (Kbits) -
E - GPRS] / [Transfer Time]

1) Should contain E-GPRS throughput at cell level.

2) Should include Downlink data only.
3) Transfer Time should ONLY include the time spent in Active State during which
data was transferred
4) Transfer Time should NOT include time spent in Idle or Standby state.
5) Transfer Time should NOT include time in Active State while waiting for packet
paging.
6) Mapping required in counter form
7) Confirmation on Unit Required
8) Should include acknowledged and unacknowledged traffic
Throughput for E-GPRS Upload in Kbits/s = [RLC Uplink Data Volume (Kbits) - E -
GPRS] / [Transfer Time]

1) Should contain E-GPRS throughput at cell level.

2) Should include Uplink data only.
3) Transfer Time should ONLY include the time spent in Active State during which
data was transferred
4) Transfer Time should NOT include time spent in Idle or Standby state.
5) Transfer Time should NOT include time in Active State while waiting for packet
paging.
6) Mapping required in counter form
7) Confirmation on Unit Required

Number of Active Max Users for GPRS

1) Count of Active users for E-GPRS data service

2) Should include downlink and uplink users
3) Should ONLY include maximum number of users in Active State for one hour.

Number of Active Users for E - GPRS

1) Count of Active users for E-GPRS data service

2) Should include downlink and uplink users
3) Should ONLY include maximum number of users in Active State for one hour.

Number of Active Max Users for GPRS

1) Count of Active users for E-GPRS data service

2) Should include downlink and uplink users
3) Should ONLY include average number of users in Active State for one hour.
4) Mapping required in counter form

Number of Active Users for E - GPRS

1) Count of Active users for E-GPRS data service

2) Should include downlink and uplink users
3) Should ONLY include average number of users in Active State for one hour.

Number of Active Max Users for GPRS

1) Count of Active users for E-GPRS data service

2) Should include downlink and uplink users
3) Should ONLY include maximum number of users in Active, Standby, and Idle State
for one hour.
4) Mapping required in counter form
Number of Active Users for E - GPRS

1) Count of Active users for E-GPRS data service

2) Should include downlink and uplink users
3) Should ONLY include maximum number of users in Active, Standby, and Idle State
for one hour.

Number of Active Max Users for GPRS

1) Count of Active users for E-GPRS data service

2) Should include downlink and uplink users
3) Should ONLY include average number of users in Active, Standby, and Idle State for
one hour.

Number of Active Users for E - GPRS

1) Count of Active users for E-GPRS data service

2) Should include downlink and uplink users
3) Should ONLY include average number of users in Active, Standby, and Idle State for
one hour.
TBF BR = TBF Blocks / TBF Attempt

1) TBF Attempt should be the same for TBF Blocking Rate and TBF Success
Rate.
2) TBF Blocks and TBF Attempt should NOT include Handovers
 ALU Formula - Counter base ALU Formula - Indicator base
[Customized as per SQM Definition] [Customized as per SQM Definition]
(( P30a + P30b + P30c + P508))+( P90a +
P90b + P90c + P90d + P90e + P90f +
P506 ))/((P62a + P62b +P62c - P438c + (TBF Uplink Successes + TBF Downlink
P507 )+(P91a + P91b + P91c + P91d + P91e Successes) / (TBF Uplink Attempts + TBF
+ P91f + P505)) Downlink Attempts)

( P30a + P30b + P30c + P508)/(P62a + P62b

+P62c - P438c + P507)
GPRS_UL_TBF_success / GPRS_UL_TBF_reques
t

( P90a + P90b + P90c + P90d + P90e + P90f

+ P506)/(P91a + P91b + P91c + P91d +
P91e + P91f + P505)

GPRS_DL_TBF_success / GPRS_DL_TBF_reques
t

(((P90a + P90b + P90c + P90d + P90e +

P90f + P506)-((P146)+(P98c)+(( P434b )+
(P434d))+NZ((P509)))-( P9 ))+((P30a +
P30b + P30c + P508)-(P22 )-((P147 )+( P98d GPRS_TBF_drop / GPRS_TBF_success =
)+(( P434a )+( P434c ))+NZ(( P510)))))/
(( P30a + P30b + P30c + P508 )+( P90a +
P90b + P90c + P90d + P90e + P90f +
P506 ))
Not Found

Not Found
(P44a+P44b)*8/1000

(GPRS_UL_LLC_bytes_GPRS_ack_mode +GPRS
_UL_LLC_bytes_GPRS_unack_mode)*8/1000

(P44c+P44d)*8/1000

(GPRS_UL_LLC_bytes_EGPRS_ack_mode+GPR
S_UL_LLC_bytes_EGPRS_unack_mode)*8/1000

(P43a+P43b)*8/1000

(GPRS_DL_LLC_bytes_GPRS_ack_mode+GPRS
_DL_LLC_bytes_GPRS_unack_mode)*8/1000

(P43c+P43d)*8/1000

(GPRS_DL_LLC_bytes_EGPRS_ack_mode+GPR
S_DL_LLC_bytes_EGPRS_unack_mode)*8/1000
Average DL GPRS Throughput (Kbits/s) =
((P43a+P43b)/(P52a+P52b))*8/1000

Average DL GPRS Throughput (Kbits/s) =

((GPRS_DL_LLC_bytes_GPRS_ack_mode+GPRS
_DL_LLC_bytes_GPRS_unack_mode)/
(GPRS_DL_active_connection_GPRS_ack_time+
GPRS_DL_active_connection_GPRS_nack_time)
)*8/1000

Average UL GPRS Throughput (Kbits/s) =

((P44a+P44b)/(P129a+P129b))*8/1000

Average UL GPRS Throughput (Kbits/s) =

((GPRS_UL_LLC_bytes_GPRS_ack_mode +GPR
S_UL_LLC_bytes_GPRS_unack_mode)/
(GPRS_UL_active_connection_GPRS_ack_time+
GPRS_UL_active_connection_GPRS_nack_time)
)*8/1000

Average DL EDGE Throughput (Kbits/s) =

((P43c+P43d)/(P52c + P52d))*8/1000

Average DL EDGE Throughput (Kbits/s) =

((GPRS_DL_LLC_bytes_EGPRS_ack_mode+GPR
S_DL_LLC_bytes_EGPRS_unack_mode)/
(GPRS_DL_active_connection_EGPRS_ack_time
+
GPRS_DL_active_connection_EGPRS_nack_time
))*8/1000
Average UL EDGE Throughput (Kbits/s) =
(P44c+P44d)/(P129c+P129d)*8/1000

Average UL EDGE Throughput (Kbits/s) =

(GPRS_UL_LLC_bytes_EGPRS_ack_mode+GPR
S_UL_LLC_bytes_EGPRS_unack_mode)/
(GPRS_UL_active_connection_EGPRS_ack_time
+GPRS_UL_active_connection_EGPRS_nack_ti
me)*8/1000

Not Found

Not Found

(( P30a + P30b + P30c + P508 )+

( P90a + P90b + P90c + P90d + P90e + P90f
+ P506 ))/( P413 )
GPRS_TBF_success / GPRS_sessions

Not Found

(( P419 )+( P420 ))/( P413)

(GPRS_DL_biased_transfer_time + GPRS_UL_biased
_transfer_time )/ GPRS_sessions
Not Found

Not Found

Not Found

((( P105d )+( P105f ))+( P27 )+( P105h )

+( P105j )+( P105l)+( P204 )
+NZ(( P512 )))+((( P105c )+( P105e ))+
( P14 )+(
GPRS_TBF_estab_cong / GPRS_TBF_request
P105g )+NZ(( P105i ))+NZ(( P105k ))
+NZ(( P203 ))+NZ(( P511 ))))/
((P62a + P62b + P62c - P438c + P507)+
( P91a + P91b + P91c + P91d + P91e + P91f
+ P505 ))
 Matching with ALU Indicator used in SQM Indicator Name
Daily QoS Daily QoS on NPO

Not in Daily QoS GPRS_TBF_success_rat No change in System

Rep. e indicator

GPRS_UL_TBF_success No change in System

YES _rate indicator

GPRS_DL_TBF_success No change in System

YES _rate indicator

Not in Daily QoS GPRS_TBF_drop_rate No change in System

Rep. indicator

Not in Daily QoS

Rep.

Not in Daily QoS

Rep.
 _GPRS_UL_LLC_byte
No GPRS_UL_LLC_bytes s_SQM

Not in Daily QoS _EGPRS_UL_LLC_byt

Rep. es_SQM

_GPRS_DL_LLC_byte
No GPRS_DL_LLC_bytes s_SQM

Not in Daily QoS _EGPRS_DL_LLC_byt

Rep. es_SQM
 _GPRS_DL_useful_th
Not in Daily QoS roughput_radio_GPR
Rep. S_TBF_avg_SQM

_GPRS_UL_useful_th
Not in Daily QoS roughput_radio_GPR
Rep. S_TBF_avg_SQM

GPRS_DL_useful_throu _GPRS_DL_useful_th
No ghput_radio_EGPRS_TB roughput_radio_EGP
F_avg RS_TBF_avg_SQM
 GPRS_UL_useful_throu _GPRS_UL_useful_th
NO ghput_radio_EGPRS_TB roughput_radio_EGP
F_av RS_TBF_avg_SQM

Not in Daily QoS

Rep.

Not in Daily QoS

Rep.

Not in Daily QoS GPRS_TBF_per_session No change in System

Rep. _avg indicator

Not in Daily QoS

Rep.

Not in Daily QoS GPRS_sessions_duratio No change in System

Rep. n_max_avg indicator
Not in Daily QoS
Rep.

Not in Daily QoS

Rep.

Not in Daily QoS

Rep.

Not in Daily QoS GPRS_TBF_estab_cong No change in System

Rep. _rate indicator
 REMARKS Mobily Feedback

* Need to check with ALU-QoS-Spport team if we can provide alternate

and/or customized formula.

* Need to check with ALU-QoS-Spport team if we can provide alternate

and/or customized formula.
* There is no loss of data between LLC and RLC where the
proposed LLC counters are trigger, the RLC bytes are correctly
measured.
The GMM/SM traffic is included in these counters.

* There is no loss of data between LLC and RLC where the

proposed LLC counters are trigger, the RLC bytes are correctly
measured.
The GMM/SM traffic is included in these counters.

* There is no loss of data between LLC and RLC where the

proposed LLC counters are trigger, the RLC bytes are correctly
measured.
The GMM/SM traffic is included in these counters.

* There is no loss of data between LLC and RLC where the

proposed LLC counters are trigger, the RLC bytes are correctly
measured.
The GMM/SM traffic is included in these counters.
* It is also including signaling packet.
* P52a+P52b could not be accurate for hourly consolidation.

* It is also including signaling packet.

* P52a+P52b could not be accurate for hourly consolidation.
* Notice that, an active UL TBF connection is an UL TBF not in
extended mode.

* It is also including signaling packet.

* P52a+P52b could not be accurate for hourly consolidation.
* It is also including signaling packet.
* P52a+P52b could not be accurate for hourly consolidation.
* Notice that, an active UL TBF connection is an UL TBF not in
extended mode.

* Need to check with ALU-QoS-Spport team if we can provide alternate

and/or customized formula.
* Current suggestions are to use P413 GPRS_sessions, but this counter
measures number of sessions (Not Users) and including both of GPRS & Held by NPM-RAN team, not to
E-GPRS (Not only GPRS), which is not matching with the requested be sent until a further notice.
definition.

* Need to check with ALU-QoS-Spport team if we can provide alternate

and/or customized formula.
* Current suggestions are to use P413 GPRS_sessions, but this counter
measures number of sessions (Not Users) and including both of GPRS & Held by NPM-RAN team, not to
E-GPRS (Not only E-GPRS), which is not matching with the requested be sent until a further notice.
definition.

* Need to be verified/validated with ALU-QoS-Spport team. As this is a

customized formula by ALU-PERF local team.
* Notice that, the provided formula has:
1) Mapping is of the form (TBF Successfully Established / Number of
GPRS Sessions). Held by NPM-RAN team, not to
2) Above mapping results in TBFs/Session. be sent until a further notice.
* Suggest P413 only.

* Need to check with ALU-QoS-Spport team if we can provide alternate

and/or customized formula.
Held by NPM-RAN team, not to
be sent until a further notice.

* Need to be verified/validated with ALU-QoS-Spport team. As this is a

customized formula by ALU-PERF local team.
* Notice that, the provided formula has:
1) Mapping is of the form (Cumulated Active Time / Number of GPRS
Sessions)
2) Above mapping results in Time/Session
* This KPI requires a counter that takes measurements periodically Held by NPM-RAN team, not to
during an hour (e.g. every 30 secs) and records the highest Session be sent until a further notice.
Count measured during the hour for one of the 30 second windows.
* Need to check with ALU-QoS-Spport team if we can provide alternate
and/or customized formula.
Held by NPM-RAN team, not to
be sent until a further notice.

* Need to check with ALU-QoS-Spport team if we can provide alternate

and/or customized formula.
Held by NPM-RAN team, not to
be sent until a further notice.

* Need to check with ALU-QoS-Spport team if we can provide alternate

and/or customized formula.
Held by NPM-RAN team, not to
be sent until a further notice.
 < Alternative Proposal / Plan-B > Alternative Proposal Clarification
Provided by ALU-PERF or TSCc

* No counter exists for PDCH requests,

preparation failures or number of success.
* ALU counter focus is for TBF. The only
reference to count number of PDCH success is
on counters P160, P161, P162, P163, P165
which count for DL/UL TBF Success dividing by
the number of PDCH used. P160 counts
“Number
* The number of DLofTBF establishment
PDCH that can berequests
used on (1a
slot allocated)
cell, which areis satisfied
i.e. PDCH capacity all TS onat oncewith
a TRX by
the initial allocation.”,
TRXPrefmark P161that
= 0, meaning is P160
it’s afor UL,
dynamic
P162
number since a TS can be used as TCH &P163 is
is for DL when 2 or 3 TS are used,
P162
PDCH.for UL andnoP165
There´s is fortoDLget
counter when
PDCH 4 or 5 TS
are used. number and also TRXPrefmark is not
available
For requests
tracked there’s
on NPO, no TS that
meaning division.
on NPO we
cannot calculate the number of available PDCH
TS.
* Another point that does not allows us to
estimate the number of available PDCH is the
fact that all TS can be used as TCH,
independently of TRXPrefmark. If you have
several group of PDCH allocated contiguously
it can happen for a TCH to be allocated in the
middle and we cannot predict for sure if this
TCH was allocated on a PS zone.
* Currently ALU implements the following
indicators for PDCH occupancy, but it’s based
on cumulated TIME rather than number of

GPRS_UL_LLC_bytes = P44
* An alternate and/or customized formula but not
mtached with the requested definition.
* Notice that, the provided formula (p44) has:
1) Measured in Bits
2) Measured at LLC layer (Not RLC). Notice that all
other vendors are measuring at RLC.
3) Includes acknowledged and unacknowledged traffic
* Current suggestions are to use (p350b)
GPRS_UL_RLC_block_PDTCH, but this counter
measures number of data blocks (Not Bytes), which is
not matching with the requested definition.

* An alternate and/or customized formula but not

mtached with the requested definition.
* Current suggestions are to use (p44c)
GPRS_UL_LLC_bytes_EGPRS_ack_mode = GPRS_UL_LLC_bytes_EGPRS_ack_mode, but this
counter measures at LLC layer (Not RLC), which is not
p44c matching with the requested definition.

*An alternate and/or customized formula but not

GPRS_DL_LLC_bytes = P43
mtached with the requested definition.
* Notice that, the provided formula (p43) has:
1) Measured in Bits
2) Measured at LLC layer (Not RLC). Notice that all
other vendors are measuring at RLC.
3) Includes acknowledged and unacknowledged traffic
* Current suggestions are to use (P350a)
GPRS_DL_RLC_block_PDTCH(GTRPDDN), but this
counter measures number of data blocks (Not Bytes),
which is not matching with the requested definition.

*An alternate and/or customized formula but not

mtached with the requested definition.
* Current suggestions are to use (p43c)
GPRS_DL_LLC_bytes_EGPRS_ack_mode, but this
GPRS_DL_LLC_bytes_EGPRS_ack_mode = counter measures at LLC layer (Not RLC), which is not
p43c matching with the requested definition.
1st proposal: 1st proposal:
GPRS_DL_useful_throughput_radio_GPRS_TBF * Notice that, the provided formula has:
_avg = 1) Mapping is in Kbits/s
GPRS_DL_useful_bits_CSx_ack / 2) Measured at RLC layer.
( GPRS_DL_active_connection_GPRS_ack_time 3) Including ONLY ACK traffic (While it is requested
*1000) = to include both ACK & NACK).
((P55a)*160+( P55b )*240+( P55c )*288+ *
( P55d )*400)/((P52a )*1000) This indicator could not be accurate for hourly con
2nd proposal: solidation.
( ( (P532b_1)*((((GPRS_LLC_THROUGHPUT_TH 2nd proposal:
R_1))-1)/2))+ * These counters are at LLC level but as explained
( (P532b_2)*((GPRS_LLC_THROUGHPUT_THR_ before within the Traffic vloume counters, there is
1)+(((GPRS_LLC_THROUGHPUT_THR_2)-1- no loss of data between LLC and RLC, meaning
(GPRS_LLC_THROUGHPUT_THR_1))/2) ))+ that the payload(data) is the same. P53yb_x are
( (P532b_3)*((GPRS_LLC_THROUGHPUT_THR_ taken only for data packets, i.e. without signaling.
2)+(((GPRS_LLC_THROUGHPUT_THR_3)-1- * To include only data packets, this is the most
(GPRS_LLC_THROUGHPUT_THR_2))/2) ))+ approximate formula.
( (P532b_4)*((GPRS_LLC_THROUGHPUT_THR_ * It is not accurate on hourly level.
3)+(((GPRS_LLC_THROUGHPUT_THR_4)-1-
1st proposal:
(GPRS_LLC_THROUGHPUT_THR_3))/2) ))+ 1st proposal:
GPRS_UL_useful_throughput_radio_GPRS_TBF
( (P532b_5)*((GPRS_LLC_THROUGHPUT_THR_ * Notice that, the provided formula has:
_avg =
4)+(((GPRS_LLC_THROUGHPUT_THR_5)-1- 1) Mapping is in Kbits/s
GPRS_UL_useful_bits_CSx_ack
(GPRS_LLC_THROUGHPUT_THR_4))/2) ))+ / 2) Measured at RLC layer.
(( GPRS_UL_active_connection_GPRS_ack_time
(P532b_6)*((GPRS_LLC_THROUGHPUT_THR_ 3) Including ONLY ACK traffic (While it is requested
*1000) =
5)+(((GPRS_LLC_THROUGHPUT_THR_6)-1- to include both ACK & NACK).
(( P57a )*160+( P57b
(GPRS_LLC_THROUGHPUT_THR_5))/2) ))+)*240+( P57c )*288+ *
(( (P532b_7)*((GPRS_LLC_THROUGHPUT_THR_
P57d )*400)/(( P129a )*1000) This indicator could not be accurate for hourly con
2nd proposal:
6)+(((GPRS_LLC_THROUGHPUT_THR_7)-1- solidation.
((GPRS_LLC_THROUGHPUT_THR_6))/2)
( (P532a_1)*((((GPRS_LLC_THROUGHPUT_TH ))+ 2nd proposal:
R_1))-1)/2))+
( (P532b_8)*((GPRS_LLC_THROUGHPUT_THR_ * These counters are at LLC level but as explained
(7)+(((GPRS_LLC_THROUGHPUT_THR_8)-1-
(P532a_2)*((GPRS_LLC_THROUGHPUT_THR_ before within the Traffic vloume counters, there is
1)+(((GPRS_LLC_THROUGHPUT_THR_2)-1-
(GPRS_LLC_THROUGHPUT_THR_7))/2) ))+ no loss of data between LLC and RLC, meaning
(GPRS_LLC_THROUGHPUT_THR_1))/2)
( (P532b_9)*((GPRS_LLC_THROUGHPUT_THR_ ))+ that the payload(data) is the same. P53ya_x are
(8)+(((GPRS_LLC_THROUGHPUT_THR_9)-1-
(P532a_3)*((GPRS_LLC_THROUGHPUT_THR_ taken only for data packets, i.e. without signaling.
2)+(((GPRS_LLC_THROUGHPUT_THR_3)-1-
(GPRS_LLC_THROUGHPUT_THR_8))/2) ))+ * To include only data packets, this is the most
(GPRS_LLC_THROUGHPUT_THR_2))/2)
( (P532b_10)*((GPRS_LLC_THROUGHPUT_THR approximate formula.
))+
(_9)+(((GPRS_LLC_THROUGHPUT_THR_10)-1-
(P532a_4)*((GPRS_LLC_THROUGHPUT_THR_ * It is not accurate on hourly level.
3)+(((GPRS_LLC_THROUGHPUT_THR_4)-1-
(GPRS_LLC_THROUGHPUT_THR_9))/2) )))
1st proposal:
(GPRS_LLC_THROUGHPUT_THR_3))/2) ))+ 1st proposal:
GPRS_DL_useful_throughput_radio_EGPRS_TB
( (P532a_5)*((GPRS_LLC_THROUGHPUT_THR_ * Notice that, the provided formula has:
F_avg =
4)+(((GPRS_LLC_THROUGHPUT_THR_5)-1- 1) Mapping is in Kbits/s
GPRS_DL_useful_bits_MCSx_ack
(GPRS_LLC_THROUGHPUT_THR_4))/2) ))+ / 2) Measured at RLC layer.
(( GPRS_DL_active_connection_EGPRS_ack_tim
(P532a_6)*((GPRS_LLC_THROUGHPUT_THR_ 3) Including ONLY ACK traffic (While it is requested
e5)+(((GPRS_LLC_THROUGHPUT_THR_6)-1-
*1000) = to include both ACK & NACK).
((( P55e )*176+( P55f )*224+( P55g )*296+
(GPRS_LLC_THROUGHPUT_THR_5))/2) ))+ *
(( P55h
(P532a_7)*((GPRS_LLC_THROUGHPUT_THR_ This indicator could not be accurate for hourly con
)*352)+(( P55i )*448+( P55j )*592+
(P55k )*448+( P55l )*544+( P55m)*592))/
6)+(((GPRS_LLC_THROUGHPUT_THR_7)-1- solidation.
((P52c )*1000)
(GPRS_LLC_THROUGHPUT_THR_6))/2) ))+ 2nd proposal:
2nd proposal:
( (P532a_8)*((GPRS_LLC_THROUGHPUT_THR_ * These counters are at LLC level but as explained
(7)+(((GPRS_LLC_THROUGHPUT_THR_8)-1-
( (P531b_1)*((((EGPRS_LLC_THROUGHPUT_T before within the Traffic vloume counters, there is
HR_1))-1)/2))+
(GPRS_LLC_THROUGHPUT_THR_7))/2) ))+ no loss of data between LLC and RLC, meaning
(( (P532a_9)*((GPRS_LLC_THROUGHPUT_THR_
(P531b_2)*((EGPRS_LLC_THROUGHPUT_THR that the payload(data) is the same. P53yb_x are
_1)+(((EGPRS_LLC_THROUGHPUT_THR_2)-1-
8)+(((GPRS_LLC_THROUGHPUT_THR_9)-1- taken only for data packets, i.e. without signaling.
(EGPRS_LLC_THROUGHPUT_THR_1))/2)
(GPRS_LLC_THROUGHPUT_THR_8))/2) ))+ ))+ * To include only data packets, this is the most
(( (P531b_3)*((EGPRS_LLC_THROUGHPUT_THR
(P532a_10)*((GPRS_LLC_THROUGHPUT_THR approximate formula.
_2)+(((EGPRS_LLC_THROUGHPUT_THR_3)-1-
_9)+(((GPRS_LLC_THROUGHPUT_THR_10)-1- * It is not accurate on hourly level.
(EGPRS_LLC_THROUGHPUT_THR_2))/2)
(GPRS_LLC_THROUGHPUT_THR_9))/2) )))))+
( (P531b_4)*((EGPRS_LLC_THROUGHPUT_THR
_3)+(((EGPRS_LLC_THROUGHPUT_THR_4)-1-
(EGPRS_LLC_THROUGHPUT_THR_3))/2) ))+
( (P531b_5)*((EGPRS_LLC_THROUGHPUT_THR
_4)+(((EGPRS_LLC_THROUGHPUT_THR_5)-1-
(EGPRS_LLC_THROUGHPUT_THR_4))/2) ))+
( (P531b_6)*((EGPRS_LLC_THROUGHPUT_THR
_5)+(((EGPRS_LLC_THROUGHPUT_THR_6)-1-
(EGPRS_LLC_THROUGHPUT_THR_5))/2) ))+
( (P531b_7)*((EGPRS_LLC_THROUGHPUT_THR
1st proposal: 1st proposal:
GPRS_UL_useful_throughput_radio_EGPRS_TB * Notice that, the provided formula has:
F_avg = 1) Mapping is in Kbits/s
GPRS_UL_useful_bits_MCSx_ack / 2) Measured at RLC layer.
( GPRS_UL_active_connection_EGPRS_ack_tim 3) Including ONLY ACK traffic (While it is requested
e *1000) = to include both ACK & NACK).
(((P57e )*176+(P57f)*224+( P57g )*296+ *
(P57h)*352)+((P57i)*448+(P57j )*592+ This indicator could not be accurate for hourly con
( P57k )*448+(P57l )*544+( P57m)*592))/ solidation.
((P129c)*1000) 2nd proposal:
2nd proposal: * These counters are at LLC level but as explained
( ( (P531a_1)*((((EGPRS_LLC_THROUGHPUT_T before within the Traffic vloume counters, there is
HR_1))-1)/2))+ no loss of data between LLC and RLC, meaning
( (P531a_2)*((EGPRS_LLC_THROUGHPUT_THR that the payload(data) is the same. P53ya_x are
_1)+(((EGPRS_LLC_THROUGHPUT_THR_2)-1- taken only for data packets, i.e. without signaling.
(EGPRS_LLC_THROUGHPUT_THR_1))/2) ))+ * To include only data packets, this is the most
( (P531a_3)*((EGPRS_LLC_THROUGHPUT_THR approximate formula.
_2)+(((EGPRS_LLC_THROUGHPUT_THR_3)-1- * It is not accurate on hourly level.
(EGPRS_LLC_THROUGHPUT_THR_2))/2) ))+
No counter exists to distinguish idle state for * ALU 2G counters do not track number of users,
( (P531a_4)*((EGPRS_LLC_THROUGHPUT_THR
GPRS.
_3)+(((EGPRS_LLC_THROUGHPUT_THR_4)-1- but rather number of sessions, TBF and MS
(EGPRS_LLC_THROUGHPUT_THR_3))/2) ))+ context. In one granularity period, one user can
( (P531a_5)*((EGPRS_LLC_THROUGHPUT_THR have several sessions, for each session several MS
_4)+(((EGPRS_LLC_THROUGHPUT_THR_5)-1- context can be established and inside each MS
(EGPRS_LLC_THROUGHPUT_THR_4))/2) ))+ context several DL/UL TBF can be triggered.
( (P531a_6)*((EGPRS_LLC_THROUGHPUT_THR * For this indicator I suggest number of TBF since
_5)+(((EGPRS_LLC_THROUGHPUT_THR_6)-1- it's
GPRS_DL_EGPRS_TBF_request+GPRS_UL_EGP the2Gonly
*distinguished.
ALU indicator
counters doon notwhich idle
track we stateof
number can be
users,
(EGPRS_LLC_THROUGHPUT_THR_5))/2) ))+ For ALU counter have MS(PDP)
RS_TBF_request- but rather number of sessions, TBF and MS
(P531a_7)*((EGPRS_LLC_THROUGHPUT_THR context
(GPRS_DL_TBF_MS_idle_EGPRS_request- context. and
In TBF.granularity
one 1 user canperiod,
have several
one MScan
user
context several sessions, for each session severalthan
_6)+(((EGPRS_LLC_THROUGHPUT_THR_7)-1- and each MS context can have more
GPRS_UL_TBF_MS_idle_EGPRS_request = have MS
(EGPRS_LLC_THROUGHPUT_THR_6))/2) ))+ 1 TBF.
P91h + P91i + P505a + P62e + P507a context can be established and inside each MS
( (P531a_8)*((EGPRS_LLC_THROUGHPUT_THR *context On ALU there'sDL/UL
several no Active state
TBF can bedefinition,
triggered. only
_7)+(((EGPRS_LLC_THROUGHPUT_THR_8)-1- Ready *and state which
ForPTM(Packect includes
this indicatorTransfer
I suggest PIM(Packet
number Idle
of TBF mode)
since
(EGPRS_LLC_THROUGHPUT_THR_7))/2) ))+ mode). Then there's
it's the only indicator on which idle state can be
No difference for the below indicators, ALU
( (P531a_9)*((EGPRS_LLC_THROUGHPUT_THR *Idle
ALUstate
2G counters
and Standby
do notstate.
track
ALU number
countersof do
users,
not
distinguished. For ALU counter we have MS(PDP)
does not implement peak values for MS distinguish
but rather number
Standby of
state,
_8)+(((EGPRS_LLC_THROUGHPUT_THR_9)-1- context and TBF. 1 user can have several MSsessions,
only if
TBF
it'sand
on Idle
MS state
context when GPRS/EGPRS type are taken
(EGPRS_LLC_THROUGHPUT_THR_8))/2) ))+into context.
or not inand
In
Idle.
one granularity period, one more
user can
context each MS context can have than
account.
( (P531a_10)*((EGPRS_LLC_THROUGHPUT_TH 1 TBF. have several sessions, for each session several MS
context can be established
R_9)+(((EGPRS_LLC_THROUGHPUT_THR_10)- * On ALU there's no Active state definition, only and inside each MS
1-(EGPRS_LLC_THROUGHPUT_THR_9))/2) ))+ context several
Ready state DL/UL
which TBF can
includes be triggered.
PIM(Packet Idle mode)
( (P531a_11)*((EGPRS_LLC_THROUGHPUT_TH and PTM(Packect Transfer mode). Then there's
R_10)+(((EGPRS_LLC_THROUGHPUT_THR_11)- Idle state and Standby state. ALU counters do not
1-(EGPRS_LLC_THROUGHPUT_THR_10))/2)
No difference for the below indicators, ALU ))) *distinguish Standbydo
ALU 2G counters state,
not only
trackifnumber
it's on Idle state
of users,
does not implement peak values for MS or not
but in Idle.
rather number of sessions, TBF and MS
context when GPRS/EGPRS type are taken into context. In one granularity period, one user can
account. have several sessions, for each session several MS
context can be established and inside each MS
context several DL/UL TBF can be triggered.
The below indicators get all MS context * ALU 2G counters do not track number of users,
created for GPRS: GPRS_DL_LLC_MS_Context + but rather number of sessions, TBF and MS
GPRS_UL_LLC_MS_Context = context. In one granularity period, one user can
(P532b_1+P532b_2+P532b_3+P532b_4+P532 have several sessions, for each session several MS
b_5+P532b_6+P532b_7+P532b_8+P532b_9+P context can be established and inside each MS
532b_10, context several DL/UL TBF can be triggered.
old:P532b_1+P532b_2+P532b_3+P532b_4+P5 * Based on MS context. 1 user can have multiple
32b_5+P532b_6+P532b_7+P532b_8+P532b_9 MS context.
+P532b_10, * For 30 second counter, the granularity has to be
past:P532b_1+P532b_2+P532b_3+P532b_4+P activated at the OMC.
532b_5+P532b_6+P532b_7+P532b_8+P532b_
9+P532b_10) +
(P532a_1+P532a_2+P532a_3+P532a_4+P532a
_5+P532a_6+P532a_7+P532a_8+P532a_9+P5
32a_10,
old:P532a_1+P532a_2+P532a_3+P532a_4+P5
32a_5+P532a_6+P532a_7+P532a_8+P532a_9
+P532a_10,
past:P532a_1+P532a_2+P532a_3+P532a_4+P
The below indicators get all MS context
created for E-GPRS:
EGPRS_DL_LLC_MS_Context +
EGPRS_UL_LLC_MS_Context =
(P531b_1+P531b_2+P531b_3+P531b_4+P531
b_5+P531b_6+P531b_7+P531b_8+P531b_9+P
Same as for the above (E)GPRS Avg Active
531b_10+P531b_11,
Users
old:P531b_1+P531b_2+P531b_3+P531b_4+P5
31b_5+P531b_6+P531b_7+P531b_8+P531b_9
+P531b_10+P531b_11,
past:P531b_1+P531b_2+P531b_3+P531b_4+P
531b_5+P531b_6+P531b_7+P531b_8+P531b_
9+P531b_10+P531b_11)+
Same as for the above (E)GPRS Avg Active
(P531a_1+P531a_2+P531a_3+P531a_4+P531a
Users
_5+P531a_6+P531a_7+P531a_8+P531a_9+P5
31a_10+P531a_11,
old:P531a_1+P531a_2+P531a_3+P531a_4+P5
31a_5+P531a_6+P531a_7+P531a_8+P531a_9
+P531a_10+P531a_11,
past:P531a_1+P531a_2+P531a_3+P531a_4+P
531a_5+P531a_6+P531a_7+P531a_8+P531a_
9+P531a_10+P531a_11)
* ALU 2G counters do not track number of users,
but rather number of sessions, TBF and MS
context. In one granularity period, one user can
have several sessions, for each session several MS
context can be established and inside each MS
context several DL/UL TBF can be triggered.
* ALU
Based2Gon
counters do not
MS context. trackcan
1 user number of users,
have multiple
but rather
MS context. number of sessions, TBF and MS
context.
* For 30 In one granularity
second counter, theperiod, one user
granularity has can
to be
have several
activated sessions,
at the OMC. for each session several MS
context can be established and inside each MS
context several DL/UL TBF can be triggered.
* ALU 2G counters do not track number of users,
but rather number of sessions, TBF and MS
context. In one granularity period, one user can
have several sessions, for each session several MS
context can be established and inside each MS
context several DL/UL TBF can be triggered.
 KQI/KPI

1 PS RRC Establishment Success Rate (%)

2 PS R99 RAB Establishment Success Rate (%)

3 PS R99 Connection Setup Success Rate (%)

4 PS HSUPA RAB Establishment Success Rate (%)

5 PS HSDPA RAB Establishment Success Rate (%)

6 RRC Drop Rate (%)

7 PS R99 RAB Drop Rate (%)

8 PS HSUPA RAB Drop Rate (%)

9 PS HSDPA RAB Drop Rate (%)

10 PS Outgoing IRAT Handover Success Rate (%)

11 PS Outgoing Handover Success Rate (%)

12 PS R99 DL Throughput (Kbits/s)

14 PS R99 UL Throughput (Kbits/s)

13 PS HSDPA Throughput (Kbits/s)

15 PS HSUPA Throughput (Kbits/s)

16 PS HSDPA Data Volume (Kbits)

17 PS HSUPA Data Volume (Kbits)

18 PS R99 DL Data Volume (Kbits)

19 PS R99 UL Data Volume (Kbits)

20 PS R99 Max Active Users (Count)

21 PS R99 Avg Active Users (Count)

22 PS R99 Max Attached Users (Count)

23 PS R99 Avg Attached Users (Count)

24 PS HSUPA Max Active Users (Count)

25 PS HSUPA Avg Active Users (Count)

26 PS HSUPA Max Attached Users (Count)

27 PS HSUPA Avg Attached Users (Count)

28 PS HSDPA Max Active Users (Count)

29 PS HSDPA Avg Active Users (Count)

30 PS HSDPA Max Attached Users (Count)

31 PS HSDPA Avg Attached Users (Count)

32 RAB Blocking Rate PS (%)

33 PS Global RAB Drop Rate (%)
 SQM Definition
RRC SR = RRC Successes / RRC Attempts

1) RRC Successes and RRC Attempts include originating and terminating PS Traffic
only
2) RRC Successes and RRC Attempts are the same in RRC Success Rate and CSSR
3) RRC Successes and RRC Attempts should NOT include Repeat Attempts
4) RRC Successes and RRC Attempts should NOT include Location Updates
5) Should not include High Priority Signalling

RAB Background SR = [RAB Background Successes + RAB Interactive Successes

+ RAB Streaming Successes] / [RAB Background Attempts + RAB Interactive
Attempts + RAB Streaming Attempts]

1) RAB Successes and RAB Attempts include PS Background, Interactive, and

Streaming.
2) RAB Successes and RAB Attempts are the same in RAB Success Rate and CSSR
3) RAB Successes and RAB Attempts should NOT include Repeat Attempts

CSSR = [RRC Successes / RRC Attempts] * [ [RAB Background Successes + RAB

Interactive Successes + RAB Streaming Successes] / [RAB Background Attempts
+ RAB Interactive Attempts + RAB Streaming Attempts]]

1) For RRC Successes and Attempts, refer to definition of PS RRC Establishment

Success Rate (%)
2) For RAB Successes and Attempts, refer to definition of PS R99 RAB
Establishment Success Rate (%)

RAB HSUPA SR = RAB HSUPA Successes / RAB HSUPA Attempts

1) RAB HSUPA Successes and RAB HSUPA Attempts include HSUPA only.
2) RAB HSUPA Successes and RAB HSUPA Attempts should NOT include Repeat
Attempts

RAB HSDPA SR = RAB HSDPA Successes / RAB HSDPA Attempts

1) RAB HSDPA Successes and RAB HSDPA Attempts include HSDPA only.
2) RAB HSDPA Successes and RAB HSDPA Attempts should NOT include Repeat
Attempts
RRC DR = RRC Abnormal Drops / (RRC Abnormal Drops + RRC Normal Drops)

1) RRC Drops should contain all available failure causes

RAB DR = RAB Abnormal Drops / ( RAB Abnormal Drops + RAB Normal Drops)

1) RAB Drops should contain all available failure causes

2) Abnormal Drops should add Incoming Handovers
3) Abnormal Drops should remove Outgoing Handovers
4) Normal Releases are defined as follows:
Release due to User Inactivity - a) This measurement provides the number of
times when the UE is removed from transport channel due to user inactivity
Core Network Initiated Release - This measurement provides the number of
times when the UE is removed from transport channel due to a release initiated
by the Core Network
Switch to PCH - Release due to successful channel switches from Cell FACH to
URA PCH in the serving cell
Serving Cell Change - Release due to successfully performed serving cell changes

HSUPA DR = HSUPA Abnormal Drops / (HSUPA Abnormal Drops + HSUPA

Normal Drops)

1) HSUPA Drops should include all available failure causes

2) Abnormal Drops should add Incoming Handovers
3) Abnormal Drops should remove Outgoing Handovers
4) Normal Releases are defined as follows:
Release due to User Inactivity - a) This measurement provides the number of
times when the UE is removed from E-DCH transport channel due to user
inactivity
Core Network Initiated Release - This measurement provides the number of
times when the UE is removed from E-DCH transport channel due to a release
initiated by the Core Network
Switch to DCH/RACH - Release due to successful channel switches from HS-DSCH
to DCH or FACH in the serving E-DCH cell
E-DCH Serving Cell Change - Release due to successfully performed serving E-
DSCH cell changes.
HSDPA DR = HSDPA Abnormal Drops / (HSDPA Abnormal Drops + HSDPA
Normal Drops)

1) HSDPA Drops should include all available failure causes

2) Abnormal Drops should add Incoming Handovers
3) Abnormal Drops should remove Outgoing Handovers
4) Normal Releases are defined as follows:
Release due to User Inactivity - a) This measurement provides the number of
times when the UE is removed from HS-DSCH transport channel due to user
inactivity
Core Network Initiated Release - This measurement provides the number of
times when the UE is removed from HS-DSCH transport channel due to a release
initiated by the Core Network
Switch to DCH/FACH - Release due to successful channel switches from E-DSCH
to DCH or RACH in the serving E-DSCH cell
HS-DCH Serving Cell Change - Release due to successfully performed serving HS-
DSCH cell changes.

PS IRAT SR = PS IRAT Successes / PS IRAT Attempts

1) PS IRAT Successes and PS IRAT Attempts should include PS Background and

Interactive only.
2) PS IRAT Succcesses and PS IRAT Attempts should include 3G to 2G Handover
only.

PS Handover SR = Handover Successes / Handover Attempts

1) Handover Successes and Handover Attempts should include PS Background

and PS Interactive only.
2) Handover Successes and Handover Attempts should include Outgoing
handovers only
UTRAN Download R99 Throughput in Kbits/s = [PS R99 DL Data Volume
(Kbits)] / [Transfer Time]

1) Should contain Download data only at cell level.

3) Should include R99 data only.
3) Should NOT include HSDPA
3) Transfer Time should ONLY include the time spent in Active State during which
data was transferred
4) Transfer Time should NOT include time spent in Idle or Standby state.
5) Transfer Time should NOT include time in Active State while waiting for packet
paging.
6) Mobily uses 1000 instead of 1024
7) (VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsIb64 /
VS_DlAsConfIdAvgNbrEstablished_DlAsCnfPsIB64_Cum) is not used.
Confirmation required.
8) Confirmation on Unit Required.

UTRAN Upload R99 Throughput in Kbits/s = [PS R99 UL Data Volume (Kbits)] /
[Transfer Time]

1) Should contain Upload data only at cell level.

3) Should include R99 data only.
3) Should NOT include HSDPA
3) Transfer Time should ONLY include the time spent in Active State during which
data was transferred
4) Transfer Time should NOT include time spent in Idle or Standby state.
5) Transfer Time should NOT include time in Active State while waiting for packet
paging.
6) Mobily uses 1000 instead of 1024
7) (VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsIb256 /
VS_UlAsConfIdAvgNbrEstablished_UlAsCnfPsIB256_Cum) is not used.
Confirmation required.
8) Confirmation on Unit Required.

HSDPA Throughput in Kbits/s = [PS HSDPA Data Volume (Kbits)] / [Transfer

Time]

1) Should contain Download data only at cell level.

3) Should NOT include R99 data.
3) Should include HSDPA only
3) Transfer Time should ONLY include the time spent in Active State during which
data was transferred
4) Transfer Time should NOT include time spent in Idle or Standby state.
5) Transfer Time should NOT include time in Active State while waiting for packet
paging.
6) Confirmation on Unit Required
7) Cell weighting should not be included
HSUPA Throughput in Kbits/s = [PS HSUPA Data Volume (Kbits)] / [Transfer
Time]

1) Should contain Download data only at cell level.

3) Should NOT include R99 data.
3) Should include HSUPA only
3) Transfer Time should ONLY include the time spent in Active State during which
data was transferred
4) Transfer Time should NOT include time spent in Idle or Standby state.
5) Transfer Time should NOT include time in Active State while waiting for packet
paging.
6) Confirmation on Unit Required
7) Cell weighting should not be included

HSDPA Data in Kbits

1) Should contain Download data only.

3) Should NOT include R99 data.
3) Should include HSDPA only
4) Should contain payload data only
5) Should NOT include Soft Handover Overhead
7) Does not match the HSDPA Data Volume used in HSDPA throughput
8) TrafficDLSDUPayloadInKbyte_Traffic017_C_HSDPA is not a counter
9) Confirmation on Unit Required
10) Confirmation on Layer required
11) Confirmation required that this mapping is Best Cell

HSUPA Data in Kbits

1) Should contain Upload data only.

3) Should NOT include R99 data.
3) Should include HSUPA only
4) Should contain payload data only
5) Should NOT include Soft Handover Overhead
6) Does not match the HSUPA Data Volume used in HSUPA throughput
7) Confirmation on Unit Required
8) Confirmation on Layer required
9) Confirm that this mapping is Best Cell.
10) Confirmation required that this mapping is Best Cell

UTRAN Download R99 Data in Kbits

1) Should contain Download data only.

3) Should include R99 data only.
3) Should NOT include HSDPA
4) Should contain payload data only
5) Should NOT include Soft Handover Overhead
6) Does not match the Download R99 Data Volume used in Download R99
throughput
7) Confirmation on Unit Required
8) Confirmation on Layer required
9) Confirm that this mapping is Best Cell.
UTRAN Upload R99 Data in Kbits

1) Should contain Upload data only.

3) Should include R99 data only.
3) Should NOT include HSUPA
4) Should contain payload data only
5) Should NOT include Soft Handover Overhead
6) Does not match the Upload R99 Data Volume used in Upload R99 throughput
7) Confirmation on Unit Required
8) Confirmation on Layer required
9) Confirm that this mapping is Best Cell.

Count of R99 Active Users

1) Should include users on Upload and download links

2) Should NOT include HSUPA or HSDPA users
3) Should ONLY include maximum number of users in Active State for one hour.

Count of R99 Active Users

1) Should include users on Upload and download links

2) Should NOT include HSUPA or HSDPA users
3) Should ONLY include Average number of users in Active State for one hour.

Count of R99 Active Users

1) Should include users on Upload and download links

2) Should NOT include HSUPA or HSDPA users
3) Should ONLY include maximum number of users in Active, Standby, and Idle
State for one hour.

Count of R99 Active Users

1) Should include users on Upload and download links

2) Should NOT include HSUPA or HSDPA users
3) Should ONLY include maximum number of users in Active, Standby, and Idle
State for one hour.

Count of HSUPA Active Users

1) Should include users on Upload High Speed links

2) Should NOT include R99 users
3) Should ONLY include maximum number of users in Active State for one hour.

Count of HSUPA Active Users

1) Should include users on Upload High Speed links

2) Should NOT include R99 users
3) Should ONLY include average number of users in Active State for one hour.
Count of HSUPA Active Users

1) Should include users on Upload High Speed links

2) Should NOT include R99 users
3) Should ONLY include maximum number of users in Active, Standby, and Idle
State for one hour.

Count of HSUPA Active Users

1) Should include users on Upload High Speed links

2) Should NOT include R99 users
3) Should ONLY include average number of users in Active, Standby, and Idle
State for one hour.

Count of HSDPA Active Users

1) Should include users on download high speed links

2) Should NOT include R99 users
3) Should ONLY include maximum number of users in Active State for one hour.

Count of HSDPA Active Users

1) Should include users on download high speed links

2) Should NOT include R99 users
3) Should ONLY include average number of users in Active State for one hour.

Count of HSDPA Active Users

1) Should include users on download high speed links

2) Should NOT include R99 users
3) Should ONLY include maximum number of users in Active, Standby, and Idle
State for one hour.

Count of HSDPA Active Users

1) Should include users on download high speed links

2) Should NOT include R99 users
3) Should ONLY include average number of users in Active, Standby, and Idle
State for one hour.

RAB BR = RAB Blocks / RAB Attempts

1) RAB Blocks should ONLY include failures caused by Congestion

2) RAB Attempts should be the same in RAB Blocking Rate and RAB
Success Rate
3) RAB Blocks and RAB Attempts should ONLY contain PS traffic
4) Confirm that RABEstablishmentAttempts_RAB036_C_Ps is equal to
RAB.AttEstab.PS.Sum
5) Confirmation required on traffic type.
RAB Global DR = Global RAB Abnormal Drops / ( Global RAB Abnormal
Drops + Global RAB Normal Drops)

1) RAB Drops should contain all available failure causes

2) Abnormal Drops should add Incoming Handovers
3) Abnormal Drops should remove Outgoing Handovers
4) Normal Releases are defined as follows:
Release due to User Inactivity - a) This measurement provides the
number of times when the UE is removed from transport channel due
to user inactivity
Core Network Initiated Release - This measurement provides the
number of times when the UE is removed from transport channel due
to a release initiated by the Core Network
5) Should include PCH feature
 ALU Formula -Counter base Matching with ALU Indicator used in
[Customized as per SQM Definition] Daily QoS Daily QoS
((((RRC_SuccConnEstab_OrigStrmCall)+
(RRC_SuccConnEstab_TermStrmCall))+
((RRC_SuccConnEstab_OrigIntactCall)+
(RRC_SuccConnEstab_TermIntactCall))+
((RRC_SuccConnEstab_OrigBgrdCall)+ RRCConnectionSuccess
(RRC_SuccConnEstab_TermBgrdCall))+ No RateExcRep_RRC021_C
((RRC_SuccConnEstab_OrigSubscCall))))/ R_Ps
(((VS_RRC_AttConnEstab_LastperProc_OrigStrmCall+VS_RRC_AttCo
nnEstab_LastperProc_TermStrmCall)+
(VS_RRC_AttConnEstab_LastperProc_OrigIntactCall+VS_RRC_AttCo
nnEstab_LastperProc_TermIntactCall)+
(VS_RRC_AttConnEstab_LastperProc_OrigBgrdCall+VS_RRC_AttCon
RABEstabSuccessRatePS_DCH_RAB031_C =

RAB_SuccEstab_PS_TrChn_DCH_DCH/
(RAB_AttEstab_PS_TrChn_DCH_DCH+RAB_AttEstab_PS_DCH_HSD
SCH_Conf_DCH_DCH+RAB_AttEstab_PS_EDCH_HSDSCH_Conf_DC Not in Daily
N/A
H_DCH+RAB_AttEstab_PS_EDCH_HSDSCH_Conf_DCH_HSDSCH_Co QoS Rep.
nf_DCH_DCH)

[((RRC_SuccConnEstab_OrigStrmCal)+
(RRC_SuccConnEstab_TermStrmCall)+
(RRC_SuccConnEstab_OrigIntactCall)+
(RRC_SuccConnEstab_TermIntactCall)+
(RRC_SuccConnEstab_OrigBgrdCall)+
(RRC_SuccConnEstab_TermBgrdCall)+
(RRC_SuccConnEstab_OrigSubscCall))/ Not in Daily
((VS_RRC_AttConnEstab_LastperProc_OrigStrmCall+VS_RRC_AttCo N/A
QoS Rep.
nnEstab_LastperProc_TermStrmCall)+
(VS_RRC_AttConnEstab_LastperProc_OrigIntactCall+VS_RRC_AttCo
nnEstab_LastperProc_TermIntactCall)+
(VS_RRC_AttConnEstab_LastperProc_OrigBgrdCall+VS_RRC_AttCon
nEstab_LastperProc_TermBgrdCall)+
(VS_RRC_AttConnEstab_LastperProc_OrigSubscCallsc))]*[(RAB_Suc
cEstab_PS_TrChn_DCH_DCH/
RAB_SuccEstab_PS_TrChn_EDCH_HSDSCH/RAB_AttEstab_PS_TrCh
(RAB_AttEstab_PS_TrChn_DCH_DCH+RAB_AttEstab_PS_DCH_HSD
n_EDCH_HSDSCH
SCH_Conf_DCH_DCH+RAB_AttEstab_PS_EDCH_HSDSCH_Conf_DC
RABEstabSuccessRateP
H_DCH+RAB_AttEstab_PS_EDCH_HSDSCH_Conf_DCH_HSDSCH_Co YES S_EDCH_RAB029_CR
nf_DCH_DCH)]

(( RAB_SuccEstab_PS_TrChn_DCH_HSDSCH +
RAB_SuccEstab_PS_TrChn_EDCH_HSDSCH )/(
RAB_AttEstab_PS_TrChn_DCH_HSDSCH + YES _HSDPA_RAB_EST
RAB_AttEstab_PS_TrChn_EDCH_HSDSCH ))
Not Found

Not in Daily N/A

QoS Rep.

IuAbnormalReleaseRequest_IU008_C_Ps /
( RadioBearerReleaseSuccess_RB030_C_Ps + IuReleaseWithRAB_IU
017_C_Ps )

Not in Daily N/A

QoS Rep.

(VS_IuAbnRelReqPsPerULRb_EDCH)/
(RAB_SuccEstab_PS_TrChn_EDCH_HSDSCH)

_Mobily_HSUPA_DropR
YES ate
((VS_RAB_Drop_PS_CellDCH_EDCH_HSDSCH)+
(VS_RAB_Drop_PS_CellDCH_DCH_HSDSCH)+
(VS_RAB_Drop_PS_Cause_DL_RLF_HSDSCH))/
((RAB_SuccEstab_PS_TrChn_DCH_HSDSCH)+
(RAB_SuccEstab_PS_TrChn_EDCH_HSDSCH)+
(VS_RAB_SuccEstab_PS_ReqNotGranted_EDCH_HSDSCH_GrantedD
CH_HSDSCH))

_Mobily_Calldrop_HSD
YES PA_cell

(IRATHO_SuccOutPS_RescuePs+IRATHO_SuccOutPS_ServicePs+IR
ATHO_SuccOutPS_NoRsrcPs)/
(VS_RrcCellChgOrderUtranCmdTrigEcNo+VS_RrcCellChgOrderUtran _Mobily_3G2G_HHO_P
YES S_Success_Rate_2
CmdTrigRscp+VS_RrcCellChgOrderUtranCmdTrigRncCell_ServicePs
+VS_RrcCellChgOrderUtranCmdTrigRncCell_NoRsrcAvailCacFailure+
VS_RrcCellChangeFromUtranTrigByUeTxPowerMax)
(VS_IuReleaseCommandPs_Succ3G3GReloc+VS_IuReleaseComman
dPsNRnc_Succ3G3GReloc)/(
VS_IuRelocationCommands_3Gto3GPs+VS_IuRelocationCommands Not in Daily N/A
_3Gto3GPsUeNotInv) QoS Rep.
(1.000*80( VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPs
Str128 + VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsStr
256 + VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsStr38
4 + VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsStrOther
+ VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsIb8 + VS
_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsIb16 + VS_De
dicatedDownlinkKbytesRlcReferenceCell_DlRabPsIb32 + VS_Dedicat
edDownlinkKbytesRlcReferenceCell_DlRabPsIb64 + VS_DedicatedDo
wnlinkKbytesRlcReferenceCell_DlRabPsIb128 + VS_DedicatedDownl
inkKbytesRlcReferenceCell_DlRabPsIb256 + VS_DedicatedDownlink Not in Daily N/A
KbytesRlcReferenceCell_DlRabPsIb384))/ QoS Rep.
(VS_DlAsConfIdAvgNbrEstablished_DlAsCnfPsStr16_Cum+VS_DlAsC
onfIdAvgNbrEstablished_DlAsCnfPsStr64_Cum+VS_DlAsConfIdAvgN
brEstablished_DlAsCnfPsStr128_Cum+VS_DlAsConfIdAvgNbrEstablis
hed_DlAsCnfPsStr256_Cum+VS_DlAsConfIdAvgNbrEstablished_DlAs
CnfPsStr384_Cum+VS_DlAsConfIdAvgNbrEstablished_DlAsCnfPsIB8
_Cum+VS_DlAsConfIdAvgNbrEstablished_DlAsCnfPsIB16_Cum+VS_
DlAsConfIdAvgNbrEstablished_DlAsCnfPsIB32_Cum+VS_DlAsConfId
AvgNbrEstablished_DlAsCnfPsIB64_Cum+VS_DlAsConfIdAvgNbrEsta
blished_DlAsCnfPsIB128_Cum+VS_DlAsConfIdAvgNbrEstablished_Dl
(1.000*80(VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsIb12
8+VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsIb16+VS_De
dicatedUplinkKbytesRlcReferenceCell_UlRabPsIb32+VS_DedicatedU
plinkKbytesRlcReferenceCell_UlRabPsIb384+VS_DedicatedUplinkKb
ytesRlcReferenceCell_UlRabPsIb64+VS_DedicatedUplinkKbytesRlcR
eferenceCell_UlRabPsIb8+VS_DedicatedUplinkKbytesRlcReferenceC
ell_UlRabPsStr16+VS_DedicatedUplinkKbytesRlcReferenceCell_UlRa
bPsStr64+VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsStrOt
her))/ Not in Daily
N/A
(VS_UlAsConfIdAvgNbrEstablished_UlAsCnfPsIB128_Cum+VS_UlAs QoS Rep.
ConfIdAvgNbrEstablished_UlAsCnfPsIB16_Cum+VS_UlAsConfIdAvg
NbrEstablished_UlAsCnfPsIB32_Cum+VS_UlAsConfIdAvgNbrEstablis
hed_UlAsCnfPsIB384_Cum+VS_UlAsConfIdAvgNbrEstablished_UlAs
CnfPsIB64_Cum+VS_UlAsConfIdAvgNbrEstablished_UlAsCnfPsIB8_C
um+VS_UlAsConfIdAvgNbrEstablished_UlAsCnfPsStr128_Cum+VS_
UlAsConfIdAvgNbrEstablished_UlAsCnfPsStr16_Cum+VS_UlAsConfI
dAvgNbrEstablished_UlAsCnfPsStr32_Cum+VS_UlAsConfIdAvgNbrEs
tablished_UlAsCnfPsStr64_Cum)
(((VS_HsdpaTxDataBitsMAChs_Cum)*500)/
(VS_HsdpaTTIsUsed))/1000

_Mobily_Average_cell_
YES throughput_Mbps
(500*(VS_eDCHdataBitSentToRNC_Cum)/
(VS_eDCHdataBitRec_NbEvt))/1000

_Mobily_eDCH_Averag
YES e_Cell_throughput

(VS_DedicatedDownlinkKbytesRlcActiveCells_DlRabHsdpa+VS_Dedi
catedDownlinkKbytesRlcActiveCells_DlRabPsStrHsdpa+VS_Dedicate
dDownlinkKbytesRlcActiveCells_DlRabPsIbQChatHspa)

_Mobily_HSDPA_Traffic
YES _Gbyte

(VS_DedicatedUplinkKbytesRlcActiveCells_UlRabHsupa+VS_Dedicat
edUplinkKbytesRlcActiveCells_UlRabPsStrHsupa+VS_DedicatedUplin
kKbytesRlcActiveCells_UlRabPsIbQChatHspa)

_Mobily_HSUPA_Traffic
YES _GB

( VS_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsStr128 + V
S_DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsStr256 + VS_
DedicatedDownlinkKbytesRlcReferenceCell_DlRabPsStr384 + VS_De
dicatedDownlinkKbytesRlcReferenceCell_DlRabPsStrOther + VS_Ded
icatedDownlinkKbytesRlcReferenceCell_DlRabPsIb8 + VS_Dedicated
DownlinkKbytesRlcReferenceCell_DlRabPsIb16 + VS_DedicatedDow Not in Daily N/A
nlinkKbytesRlcReferenceCell_DlRabPsIb32 + VS_DedicatedDownlink QoS Rep.
KbytesRlcReferenceCell_DlRabPsIb64 + VS_DedicatedDownlinkKbyt
esRlcReferenceCell_DlRabPsIb128 + VS_DedicatedDownlinkKbytesR
lcReferenceCell_DlRabPsIb256 + VS_DedicatedDownlinkKbytesRlcR
eferenceCell_DlRabPsIb384)
VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsIb128+VS_Dedi
catedUplinkKbytesRlcReferenceCell_UlRabPsIb16+VS_DedicatedUpli
nkKbytesRlcReferenceCell_UlRabPsIb32+VS_DedicatedUplinkKbytes
RlcReferenceCell_UlRabPsIb384+VS_DedicatedUplinkKbytesRlcRefer
enceCell_UlRabPsIb64+VS_DedicatedUplinkKbytesRlcReferenceCell_
UlRabPsIb8+VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsSt Not in Daily N/A
r16+VS_DedicatedUplinkKbytesRlcReferenceCell_UlRabPsStr64+VS_ QoS Rep.
DedicatedUplinkKbytesRlcReferenceCell_UlRabPsStrOther

Not Found

Not in Daily N/A

QoS Rep.

VS_RadioBearerSetupSuccess_TgtCallOther + VS_RadioBearerSetup
Success_TgtCallPsStrLt64 + VS_RadioBearerSetupSuccess_TgtCallPs
Str64 + VS_RadioBearerSetupSuccess_TgtCallPsStr128 + VS_Radio
BearerSetupSuccess_TgtCallPsStr256 + VS_RadioBearerSetupSucce
Not in Daily
ss_TgtCallPsStr384 + VS_RadioBearerSetupSuccess_TgtCallPsIbLt64 N/A
+ VS_RadioBearerSetupSuccess_TgtCallPsIb64 + VS_RadioBearerS
QoS Rep.
etupSuccess_TgtCallPsIb128 + VS_RadioBearerSetupSuccess_TgtCa
llPsIb256 + VS_RadioBearerSetupSuccess_TgtCallPsIb384

Not Found

Not in Daily
N/A
QoS Rep.

Not Found

Not in Daily
N/A
QoS Rep.

VS_eDCHactiveUsers_2ms_users_Max+VS_eDCHactiveUsers_10ms
_users_Max
Not in Daily
N/A
QoS Rep.

( VS_eDCHactiveUsers_2ms_users_Cum + VS_eDCHactiveUsers_10
ms_users_Cum )/
( VS_eDCHactiveUsers_2ms_users_NbEvt + VS_eDCHactiveUsers_1 _Mobily_eDCH_Active_
Yes users
0ms_users_NbEvt )
Not Found

Not in Daily N/A

QoS Rep.

Not Found

Not in Daily N/A

QoS Rep.

VS_HsdpaUsersCapacity_HSXPA_MaxUsed/VS_HsdpaUsersCapacity_
HSXPA_NbEvt
Not in Daily N/A
QoS Rep.

VS_HsdpaUsersCapacity_HSXPA_CumUsed/VS_HsdpaUsersCapacity
_HSXPA_NbEvt
Not in Daily N/A
QoS Rep.

Not Found

Not in Daily N/A

QoS Rep.

Not Found

Not in Daily N/A

QoS Rep.

( RAB_FailEstab_PS_DLPwr + RAB_FailEstab_PS_CodeStarv + RAB_

FailEstab_PS_RLFailNodeBResource + RAB_FailEstab_PS_LackTrans
pRsrc )/ RABEstablishmentAttempts_RAB036_C_Ps
_Mobily_RAB_BlockR
Yes ate_PS_RC
(((VS_RAB_Drop_PS_CellDCH_RelProc_IuRelReq+VS_RAB_Drop_PS
_CellDCH_RelProc_RABRelReq+VS_RAB_Drop_PS_CellDCH_RelProc
_Reset)+(VS_RAB_Drop_PS_CellFACH)+
(VS_RAB_Drop_CN_Init_PS_CellDCH_DCH_DCH+VS_RAB_Drop_CN
_Init_PS_CellDCH_DCH_HSDSCH+VS_RAB_Drop_CN_Init_PS_CellD
CH_EDCH_HSDSCH)+(VS_RAB_Drop_CN_Init_PS_CellFACH))/
(((VS_RAB_Drop_CN_Init_PS_CellDCH_DCH_DCH+VS_RAB_Drop_C
N_Init_PS_CellDCH_DCH_HSDSCH+VS_RAB_Drop_CN_Init_PS_Cell Yes _RABDropRate_PS
DCH_EDCH_HSDSCH)+(VS_RAB_Drop_PS_CellFACH)+
(VS_RAB_Drop_CN_Init_PS_CellDCH_DCH_DCH+VS_RAB_Drop_CN
_Init_PS_CellDCH_DCH_HSDSCH+VS_RAB_Drop_CN_Init_PS_CellD
CH_EDCH_HSDSCH)+(VS_RAB_Drop_CN_Init_PS_CellFACH))+
((VS_RabNormalRelPerGrantedRabTypeRefCell_GrantedRabPsHighR
ateBgnd)+
(VS_RabNormalRelPerGrantedRabTypeRefCell_GrantedRabPsHighRa
teInter)+
(VS_RabNormalRelPerGrantedRabTypeRefCell_GrantedRabPsLowRat
eBgnd)+
(VS_RabNormalRelPerGrantedRabTypeRefCell_GrantedRabPsLowRat
eInter)+
(VS_RabNormalRelPerGrantedRabTypeRefCell_GrantedRabPsStrHiR
ateStr)+
(VS_RabNormalRelPerGrantedRabTypeRefCell_GrantedRabPsStrLow
RateStr))))
SQM Indicator Name REMARKS
on NPO

RRCConnectionSucce
ssRateExcRep_RRC02
1_CR_Ps_SQM

No change in System
indicator

PS_CSSR_R99_SQM

No change in System
indicator

No change in System
indicator
 * Need to check with ALU-QoS-Spport team if we can provide
alternate and/or customized formula.

* Does not fulfil (4); We already provided the Abnormal Releases

counters, but we did not found a counters for R99 RAB Normal
Releases.
* Abnormal Releases = VS_RAB_Drop_PS_CellDCH_DCH_DCH
* Current suggestions are to use RAB success instead but this does
not align with the definition.
* Another suggestion was
CallDropRate_IU022_C_Ps= IuAbnormalReleaseRequest_IU008_C_
Ps /
CallDropRate_IU022 ( RadioBearerReleaseSuccess_RB030_C_Ps + IuReleaseWithRAB_I
_C_Ps U017_C_Ps ), (which is the one used now) but this was also not
align with the definition.

* Need to check with ALU-QoS-Spport team if we can provide

alternate and/or customized formula.
* Does not fulfil (4); We already provided the Abnormal Releases
counters, but we did not found a counters for HSUPA RAB Normal
Releases.
* Abnormal Releases = VS_IuAbnRelReqPsPerULRb_EDCH
* Current suggestions are to use RAB success instead but this does
not align with the definition, where as for Total release this
"RAB_SuccEstab_PS_TrChn_EDCH_HSDSCH" counter available
which does not satisfies Point no.(2), this means
No change in System this counter does not take into account RAB successfully establishe
indicator d for incoming relocations.
* Current used formula within our Daily QoS Report:
_Mobily_HSUPA_DropRate =
IuAbnormalReleaseRequest_IU008_C_HSUPA/TotalNumberPsCalls
_Traffic041_CR_Edch
 * Need to check with ALU-QoS-Spport team if we can provide
alternate and/or customized formula.
* Does not fulfil (4); We already provided the Abnormal Releases
counters, but we did not found a counters for HSDPA RAB Normal
Releases.
* Abnormal Releases =
IuAbnormalReleaseRequest_IU008_R_HSDPA=
((VS_RAB_Drop_PS_CellDCH_EDCH_HSDSCH)+
(VS_RAB_Drop_PS_CellDCH_DCH_HSDSCH)+
(VS_RAB_Drop_PS_Cause_DL_RLF_HSDSCH)).
* Current suggestions are to use RAB success instead but this does
not align with the definition where as the Total release this
TotalNumberPsCalls_Traffic041_C_Hsdpa indicator available which
does not satisfies Point no.(2) that means
No change in System this indicator does not take into account RAB successfully establish
indicator ed for incoming relocations.
* Current used formula within our Daily QoS Report:
_Mobily_Calldrop_HSDPA_cell =
(PsRabDroppedInCellDCH_RAB035_CR_Utran_EdchHsdsch+PsRab
DroppedInCellDCH_RAB035_C_Utran_DchHsdsch+VS_RAB_Drop_
PS_Cause_DL_RLF_HSDSCH)/
(RAB_SuccEstab_PS_TrChn_DCH_HSDSCH+RAB_SuccEstab_PS_TrC
hn_EDCH_HSDSCH+VS_RAB_SuccEstab_PS_ReqNotGranted_EDCH
_HSDSCH_GrantedDCH_HSDSCH).

No change in System
indicator

Outgoing3G3GHHO
ExecutionSuccessR
ate_HO3G3G009_R
_Ps
 * Need to be verified/validated with ALU-QoS-Spport team. As this
is a customized formula by ALU-PERF local team
* No direct indicator available for PS-DL-R99 throughput.
* Indicators availble for throughput for different
services(PS384,256,128,64) using this different services
throughput.
* Notice that, the provided formula has:
1) Mapping is in Kbytes.
2) Measured at RLC Layer.
3) Best Cell.
Need to create
Customized indicator

* Need to be verified/validated with ALU-QoS-Spport team. As this

is a customized formula by ALU-PERF local team
* No direct indicator available for PS-UL-RR9 throughput.
* Indicators availble for throughput for different
services(PS384,256,128,64) using this different services
throughput.
* Notice that, the provided formula has:
1) Mapping is in Kbytes
2) Measured at RLC Layer
3) Best Cell
Need to create 4) Mobily uses 1000 instead of 1024
Customized indicator

* Need to verify below suggestion with the ALU-QoS-Support

team, in order to provide the Throughput formula on RLC layer as
per the Traffic formula; Shall we use below formula:
(Traffic_indicator_used_in_row20)/(VS_HsdpaTTIsUsed*2* 0.001)
* Notice that, the provided formula has:
1) Mapping is in Mbps.
2) Measured at MAC layer (Not RLC).
No change in System
indicator
 * Need to verify below suggestion with the ALU-QoS-Support
team, in order to provide the Throughput formula on RLC layer as
per the Traffic formula; Shall we use below formula:
(Traffic_indicator_used_in_row21)/(VS_HsdpaTTIsUsed*2* 0.001)
* In Addition, the suggested formula inlcude only the TTI-2ms,
How can we include also TTI=10ms?
* Notice that, the provided formula has:
No change in System 1) Mapping is in Mbps.
indicator 2) Measured at MAC layer (Not RLC).

* For Point no. (1), HSDPA data volume used in HSDPA throughput
KPI is excluding re-transmission and at MAC layer.
* Notice that, the provided formula has:
1) Mapping is in KBytes
2) Measured at RLC layer
3) Best Cell

No change in System
indicator

* For Point no. (1), HSUPA data volume used in HSUPA throughput
KPI is excluding re-transmission and at MAC layer.
* Notice that, the provided formula has:
1) Mapping is in KBytes
2) Measured at RLC layer
3) Best Cell
No change in System
indicator

* Need to be verified/validated with ALU-QoS-Spport team. As this

is a customized formula by ALU-PERF local team
* No direct indicator available for PS-DL-RR9 data volume.
* Notice that, the provided formula has:
1) Mapping is in Kbytes
2) Measured at RLC Layer
_Mobily_DL_Traffic_ 3) Mapping is Best Cell
PS_R99_SQM
 * Need to be verified/validated with ALU-QoS-Spport team. As this
is a customized formula by ALU-PERF local team
* No direct indicator available for PS-UL-RR9 data volume.
* Notice that, the provided formula has:
1) Mapping is in Kbytes
2) Measured at RLC Layer
_Mobily_UL_Traffic_ 3) Mapping is Best Cell
PS_R99_SQM

* Need to check with ALU-QoS-Spport team if we can provide

alternate and/or customized formula.

_R99_users

* Need to check with ALU-QoS-Spport team if we can provide

alternate and/or customized formula.
* May be available at SGSN

* Need to check with ALU-QoS-Spport team if we can provide

alternate and/or customized formula.
* May be available at SGSN.

HSUPA_users_Max

No change in System
indicator
 * Need to check with ALU-QoS-Spport team if we can provide
alternate and/or customized formula.
* May be available at SGSN.

* Need to check with ALU-QoS-Spport team if we can provide

alternate and/or customized formula.
* May be available at SGSN.

Mobily_Max_HSDPA
_Users

_Mobily_Average_HS
DPA_Users

* Need to check with ALU-QoS-Spport team if we can provide

alternate and/or customized formula.
* May be available at SGSN.

* Need to check with ALU-QoS-Spport team if we can provide

alternate and/or customized formula.
* May be available at SGSN.

* Notice that, the provided formula has:

1) All PS attempts are included.
2) Both R99 & HS traffic types are included.

No change in System
indicator
 * Refering to Point No.5, PCH feature is not activated for the
moment, it is also not included within the provided formula; Need
to check with ALU-QoS-Spport team to be included.
* Newly added on 09-Dec-2013.

No change in System
indicator
Mobily Feedback < Alternative Proposal / Plan-B >
Provided by ALU-PERF or TSCc

Proposal by OPT team:

_Mobily_CSSR_PS_R99Only(Mobily_CSSR_PS_
R99) (%)
=
RRCConnectionSuccessRateExcRep_RRC021_C
R_Ps *
RABEstabSuccessRatePS_DCH_RAB031_C
 *No Separate screenings for Normal and
Abnormal releases
*Total RRC Drops for CS and PS
Held by NPM-RAN team, not to *Proposed Indicator : URB017_CR =
be sent until a further notice. (VS_RRC_AttConnRel_CS_Drop_CallSetup+VS_
RRC_AttConnRel_PS_Drop_CallSetup)/
(RRCConnectionSuccess_RRC001_C_Cs+RRCCo
nnectionSuccessPsServices_RRC026_CR)

*No matching indicator

*Another Proposed formula for R99 RAB DR
used by ALU: RABDropRatePSDch_RAB025_R
=
(PsRabDroppedInCellDCH_RAB035_R_Utran_D
chDch+PsRabDroppedInCellDCH_RAB035_R_C
ore_DchDch)/TotalNumberOfCalls_Traffic040_
R_Ps
Note that this formula counts the core drops
as abnormal drop, while SQM requirs to count
it as normal drop.

*No matching indicator

*Another Proposed formula for HSUPA RAB
DR used by ALU:
RABDropRatePSEdch_RAB023_R =
(PsRabDroppedInCellDCH_RAB035_CR_Utran_
EdchHsdsch+PsRabDroppedInCellDCH_RAB035
_CR_Core_EdchHsdsch)/TotalNumberOfCalls_T
raffic040_R_Ps
Note that this formula counts the core drops
as abnormal drop, while SQM requirs to count
it as normal drop.
 *No matching indicator
*Another Proposed formula for R99 RAB DR
used by ALU:
RABDropRatePSHsdpa_RAB024_R =
(PsRabDroppedInCellDCH_RAB035_R_Utran_D
chHsdsch+PsRabDroppedInCellDCH_RAB035_
CR_Utran_EdchHsdsch+PsRabDroppedInCellD
CH_RAB035_R_Core_DchHsdsch+PsRabDropp
edInCellDCH_RAB035_CR_Core_EdchHsdsch)/
TotalNumberOfCalls_Traffic040_R_Ps
Note that this formula counts the core drops
as abnormal drop, while SQM requirs to count
it as normal drop.

Held by NPM-RAN team, not to

be sent until a further notice.
Held by NPM-RAN team, not to
be sent until a further notice.

Held by NPM-RAN team, not to

be sent until a further notice.
Held by NPM-RAN team, not to Not available
be sent until a further notice.

Held by NPM-RAN team, not to

be sent until a further notice.

Held by NPM-RAN team, not to Not available

be sent until a further notice.

Held by NPM-RAN team, not to Not available

be sent until a further notice.

Held by NPM-RAN team, not to

be sent until a further notice.

Held by NPM-RAN team, not to

be sent until a further notice.
Held by NPM-RAN team, not to Proposed Formula (NodeB level, not available
on cell level):
be sent until a further notice. VS_eDCHUsersCapacity_HSXPA_MaxUsed

Proposed Formula (NodeB level, not available

Held by NPM-RAN team, not to on cell level):
be sent until a further notice. VS_eDCHUsersCapacity_HSXPA_CumUsed/VS_
eDCHUsersCapacity_HSXPA_NbEvt

Held by NPM-RAN team, not to

be sent until a further notice.

Held by NPM-RAN team, not to

be sent until a further notice.

Held by NPM-RAN team, not to Proposed Formula (NodeB level, not available
on cell level):
be sent until a further notice. VS_HsdpaUsersCapacity_HSXPA_MaxUsed

Proposed Formula (NodeB level, not available

Held by NPM-RAN team, not to on cell level):
be sent until a further notice. (VS_HsdpaUsersCapacity_HSXPA_CumUsed/VS
_HsdpaUsersCapacity_HSXPA_NbEvt)
 KQI/KPI

1 PDP Context Activation Success Rate (%)

2 Overall PDP Deactivation Success Rate (%)

3 MS Initiated PDP Deactivation Success Rate (%)

4 Nw Initiated PDP Deactivation Success Rate (%)

5 GGSN initiated PDP Cut-Off Ratio (%)

6 UL Packet Drop Rate (%)

7 DL Packet Drop Rate (%)

8 DL Data Volume (Gn)

9 UL Data Volume (Gn)

10 Upload Data Volume (Gi)

11 Download Data Volume (Gi)

12 DHCP Address Allocation SR

13 Consumption of IP pool

14 Number of Active Session PDP Background

15 Number of Active Sessions PDP Interactive

 SQM Definition

PDP Activation SR = PDP Successes / PDP Attempts

1) PDP Successes and PDP Attempts should include all PDPs activated at the GGSN
2) PDP Successes and PDP Attempts should include all traffic classes
3) PDP Activation GERAN Successes and PDP Activation UTRAN Successes should ADD the following failure types:
a) Unknown or missing Access Point Name or Unknown PDP address or PDP Type
Number of unsuccessful primary PDP context activation procedures due to cause code 27 (Unknown or missing access point name), and cause code 28 (Unk
address or PDP type). This is incremented when the SGSN interrogates the Domain Name System (DNS) resolver and there is a failure-name error or if Acce
Name (APN) (SGSN) is not defined or if requested PDP type not sent by MS - error.
b) User Authentication Failed
Number of unsuccessful primary PDP context activation procedures due to cause code 29 (User Authentication Failed). The counter is iConfigurationemente
request is rejected by the GGSN (Remote Authentication Dial-In User Service (RADIUS)).
c) Service Option not supported or Requested Server option not subscribed
Number of unsuccessful primary PDP context activation procedures due to cause code 32 (Service option not supported), and cause code 33 (Requested Se
not subscribed). The counter is iConfigurationemented if the PDP Type is not supported or Network Services Access Point Identifier (NSAPI) Reserved or if th
denied in the SGSN due to subscriber data restriction.

Overall PDP Deactivation SR = (MS PDP Deactivate Successes + Network PDP Deactivate Successes) / (MS PDP Deactivate Attempts + Network PDP Deac
Attempts)

1) For MS Deactivations, refer to MS Initiated PDP Deactivation Success Rate (%)

2) For Network Deactivations, refer to Nw Initiated PDP Deactivation Success Rate (%)

Overall PDP Deactivation SR = (MS PDP Deactivate Successes) / (MS PDP Deactivate Attempts)

1) All Attempts should be measured at initial request

2) All Success and Attempts should include all traffic classes

Overall PDP Deactivation SR = (Network PDP Deactivate Successes) / (Network PDP Deactivate Attempts)

1) All Attempts should be measured at initial request

2) All Success and Attempts should include all traffic classes
3) Network PDP Deactivate Successes and Network PDP Deactivate Attempts should include GGSN initiated attempts and successes only.

GGSN Initiated Cut-Off Ratio = (Network PDP Deactivate Attempts) / (MS PDP Deactivate Attempts + Network PDP Deactivate Attempts)

1) For MS Deactivations, refer to MS Initiated PDP Deactivation Success Rate (%)

2) For Network Deactivations, refer to Nw Initiated PDP Deactivation Success Rate (%)

Upload Packet DR = (Packets Received on Gn - Packets Sent on Gi) / Packets Revceived on Gn

1) Packets Reviced on Gn measures the packets coming into the GGSN from the SGSN
Download Packet DR = (Packets Received on Gi - Packets Sent on Gn) / Packets Revceived on Gi
1) Packets Reviced on Gi measures the packets coming into the GGSN from out of the network

Download Data on Gn interface in Kbits

1) Should contain Download data only.

2) Measures the data travelling IN to the network from the GGSN
3) Should contain payload data only

Upload Data on Gn interface in Kbits

1) Should contain Upload data only.

2) Measures the data travelling IN to the GGSN from the network
3) Should contain payload data only

Data on Gi interface in Kbits

1) Should contain Upload data.

2) Measures the data travelling OUT of the GGSN on the Gi interface
3) Should contain payload data only
Data on Gi interface in Kbits

1) Should contain Download data.

2) Measures the data travelling IN to the GGSN on the Gi interface
3) Should contain payload data only

DHCP Allocation SR = DHCP Successes / DHCP Attempts

1) DHCP Attempts should include initial request.

IP Pool Consumption = IP Pool Occupied / IP Pool Available

1) IP Pool Available should measure total capacity of GGSN

2) IP Pool Occupied should measure IP currently active

Count of active PDP Background

1) Should not contain any other traffic class, except background

Count of active PDP Interactive

1) Should not contain any other traffic class, except interactive

 KQI/KPI

1 Overall Attach Success Rate (%)

2 Attach Success Rate for GERAN (%)

3 Attach Success Rate for UTRAN (%)

4 MS Initiated Detach Success Rate for GERAN (%)

5 MS Initiated Detach Success Rate for UTRAN (%)

6 Nw Initiated Detach Success Rate for GERAN (%)

7 Nw Initiated Detach Success Rate for UTRAN (%)

8 Overalll PDP Context Activation Success Rate (%)

9 PDP Context Activation Success Rate for GERAN (%)

10 PDP Context Activation Success Rate for UTRAN (%)

Nw Initiated PDP Modification Success Rate for GERAN

11
(%)

Nw Initiated PDP Modification Success Rate for UTRAN

12 (%)

MS Initiated PDP Modification Success Rate for GERAN

13
(%)

MS Initiated PDP Modification Success Rate for UTRAN

14
(%)

15 Nw Initiated PS RAB Release Rate (%)

16 MS Initiated PS RAB Release Rate (%)

17 DL Packet Discard Rate Background (%)

18 DL Packet Discard Rate for Interactive (%)

19 Overall PS Paging Success Rate (%)

20 PS Paging Success Rate for GERAN (%)

21 PS Paging Success Rate for UTRAN (%)

22 Periodic RAU Success Rate for GERAN (%)

23 Periodic RAU Success Rate for UTRAN (%)

24 Overall Combined RAU/LAU Success Rate (%)

25 Combined RAU/LAU Success Rate for GERAN (%)

26 Combined RAU/LAU SR Success Rate for UTRAN (%)

27 Inter SGSN RAU Success Rate for GERAN (%)

28 Inter SGSN RAU Success Rate for UTRAN (%)

29 Intra SGSN RAU Success Rate for GERAN (%)

30 Intra SGSN RAU Success Rate for UTRAN (%)

31 SGSN Authentication Success Rate (%)

32 DNS Query Success Rate (%)

33 PS RAB Establishment Success Rate (%)

34 IuPS Traffic (Kbits)

35 Gb Traffic (Kbits)

36 Gp Traffic (Kbits)

37 2G Attached Max Subscribers (Count)

38 2G PDP Activated Max Subscribers (Count)

39 2G Attached Avg Subscribers (Count)

40 2G PDP Activated Avg Subscribers (Count)

41 3G Attached Max Subscribers (Count)

42 3G PDP Activated Max Subscribers (Count)

43 3G Attached Avg Subscribers (Count)

44 3G PDP Activated Avg Subscribers (Count)

45 HSDPA PDP Activated Max Subscribers (Count)

46 HSUPA PDP Activated Max Subscribers (Count)

47 HSDPA PDP Activated Avg Subscribers (Count)

48 HSUPA PDP Activated Avg Subscribers (Count)

 SQM Definition

Attach SR = (Attach GERAN Successes + Attach UTRAN Successes) / (Attach GERAN Attempts + Attach UTRAN Attempts)

1) For Attach GERAN Succeses and Attempts, refer to Attach Success Rate for GERAN (%)
2) For Attach UTRAN Succeses and Attempts, refer to Attach Success Rate for UTRAN (%)

Attach GERAN SR = (Attach GERAN Successes) / (Attach GERAN Attempts)

1) Attach GERAN Attempts should use initial requests

2) Attach GERAN Successes should ADD the following failure types:
a) GPRS Not Allowed
The number of unsuccessful MM attach procedures which return cause code 7 - GPRS services not allowed.
b) GPRS Non GPRS Not Allowed
The number of unsuccessful MM attach procedures which return cause code 8 – GPRS and non-GPRS services not allowed.
c) PLMN Not Allowed
The number of unsuccessful MM attach procedures which return cause code 11 – PLMN not allowed.
d) Not Allowed in Location Area
The number of unsuccessful MM attach procedures which return cause code 12 – not allowed in this location area.
e) Not Allowed in PLMN
The number of unsuccessful MM attach procedures which return cause code 14 – GPRS services not allowed in this PLMN.
f) No suitable cell
The number of unsuccessful MM attach procedures which return cause code 15 – No suitable cells in location area.
3) Attach GERAN Success and Attach GERAN Attempts should include GERAN measurements only.

Attach UTRAN SR = (Attach UTRAN Successes) / (Attach UTRAN Attempts)

1) Attach UTRAN Attempts should use initial requests

2) Attach GERAN Successes should ADD the following failure types:
a) GPRS Not Allowed
The number of unsuccessful MM attach procedures which return cause code 7 - GPRS services not allowed.
b) GPRS Non GPRS Not Allowed
The number of unsuccessful MM attach procedures which return cause code 8 – GPRS and non-GPRS services not allowed.
c) PLMN Not Allowed
The number of unsuccessful MM attach procedures which return cause code 11 – PLMN not allowed.
d) Not Allowed in Location Area
The number of unsuccessful MM attach procedures which return cause code 12 – not allowed in this location area.
e) Not Allowed in PLMN
The number of unsuccessful MM attach procedures which return cause code 14 – GPRS services not allowed in this PLMN.
f) No suitable cell
The number of unsuccessful MM attach procedures which return cause code 15 – No suitable cells in location area.
3) Attach UTRAN Success and Attach UTRAN Attempts should include UTRAN measurements only.

MS Initiated Detach GERAN SR = MS Initiated Detach GERAN Successes / MS Initiated Detach GERAN Attempts

1) MS Initiated Detach GERAN Attempts should include initial requests

MS Initiated Detach UTRAN SR = MS Initiated Detach UTRAN Successes / MS Initiated Detach UTRAN Attempts

1) MS Initiated Detach UTRAN Attempts should include initial requests

Network Initiated Detach GERAN SR = Network Initiated Detach GERAN Successes / Network Initiated Detach GERAN Attempts

1) Network Initiated Detach GERAN Attempts should include initial requests

Network Initiated Detach UTRAN SR = Network Initiated Detach UTRAN Successes / Network Initiated Detach UTRAN Attempts

1) Network Initiated Detach UTRAN Attempts should include initial requests

PDP Activation SR = (PDP Activation GERAN Successes + PDP Activation UTRAN Successes) / (PDP Activation GERAN Attempts + PDP Activation UTRAN A

1) For PDP Activation GERAN Attempts and Successes, refer to PDP Context Activation Success Rate for GERAN (%)
2) For PDP Activation UTRAN Attempts and Successes, refer to PDP Context Activation Success Rate for UTRAN (%)

PDP Activation GERAN SR = (PDP Activation GERAN Successes) / (PDP Activation GERAN Attempts)

1) PDP Activation GERAN Attempts should use initial requests

2) PDP Activation GERAN Successes should ADD the following failure types:
a) Unknown or missing Access Point Name or Unknown PDP address or PDP Type
Number of unsuccessful primary PDP context activation procedures due to cause code 27 (Unknown or missing access point name), and cause code 28 (Unk
This is incremented when the SGSN interrogates the Domain Name System (DNS) resolver and there is a failure-name error or if Access Point Name (APN) (S
PDP type not sent by MS - error.
b) User Authentication Failed
Number of unsuccessful primary PDP context activation procedures due to cause code 29 (User Authentication Failed). The counter is iConfigurationemente
GGSN (Remote Authentication Dial-In User Service (RADIUS)).
c) Service Option not supported or Requested Server option not subscribed
Number of unsuccessful primary PDP context activation procedures due to cause code 32 (Service option not supported), and cause code 33 (Requested Se
counter is iConfigurationemented if the PDP Type is not supported or Network Services Access Point Identifier (NSAPI) Reserved or if the request is denied i
restriction.
3) PDP Activation GERAN Success and PDP Activation GERAN Attempts should include GERAN measurements only.

PDP Activation UTRAN SR = (PDP Activation UTRAN Successes) / (PDP Activation UTRAN Attempts)

1) PDP Activation UTRAN Attempts should use initial requests

2) PDP Activation UTRAN Successes should ADD the following failure types:
a) Unknown or missing Access Point Name or Unknown PDP address or PDP Type
Number of unsuccessful primary PDP context activation procedures due to cause code 27 (Unknown or missing access point name), and cause code 28 (Unk
This is incremented when the SGSN interrogates the Domain Name System (DNS) resolver and there is a failure-name error or if Access Point Name (APN) (S
PDP type not sent by MS - error.
b) User Authentication Failed
Number of unsuccessful primary PDP context activation procedures due to cause code 29 (User Authentication Failed). The counter is iConfigurationemente
GGSN (Remote Authentication Dial-In User Service (RADIUS)).
c) Service Option not supported or Requested Server option not subscribed
Number of unsuccessful primary PDP context activation procedures due to cause code 32 (Service option not supported), and cause code 33 (Requested Se
counter is iConfigurationemented if the PDP Type is not supported or Network Services Access Point Identifier (NSAPI) Reserved or if the request is denied i
restriction.
3) PDP Activation UTRAN Success and PDP Activation UTRAN Attempts should include UTRAN measurements only.

Network Initiated PDP Modification GERAN SR = Network Initiated PDP Modification GERAN Successes / Network Initiated PDP Modification GERAN Att

1) Network Initiated PDP Modification GERAN Attempts should include initial requests

Network Initiated PDP Modification UTRAN SR = Network Initiated PDP Modification UTRAN Successes / Network Initiated PDP Modification UTRAN Att

1) Network Initiated PDP Modification UTRAN Attempts should include initial requests

MS Initiated PDP Modification GERAN SR = MS Initiated PDP Modification GERAN Successes / MS Initiated PDP Modification GERAN Attempts

1) MS Initiated PDP Modification GERAN Attempts should include initial requests

MS Initiated PDP Modification UTRAN SR = MS Initiated PDP Modification UTRAN Successes / MS Initiated PDP Modification UTRAN Attempts

1) MS Initiated PDP Modification UTRAN Attempts should include initial requests

Network Initiated PS RAB Release Rate = Network Initiated RAB Release Attempts / (MS Initiated RAB Release Attempts + Network Initiated RAB Release

1) RAB Release attempts should inculde all available failure causes

MS Initiated PS RAB Release Rate = MS Initiated RAB Release Attempts / (MS Initiated RAB Release Attempts + Network Initiated RAB Release Attempts)

1) RAB Release attempts should inculde all available failure causes

Download Packet Background Discard Rate = (Background Packets Received on Gn - (Background Packets Sent on IuPS + Background Packets Sent on Gb
Gn)
1) Packets Received on Gn should measure packets received from the GGSN

Download Packet Background Discard Rate = (Interactive Packets Received on Gn - (Interactive Packets Sent on IuPS + Interactive Packets Sent on Gb)) /
1) Packets Received on Gn should measure packets received from the GGSN

PS Paging SR = (PS Paging GERAN Success + PS Paging UTRAN Success) / (PS Paging GERAN Attempts + PS Paging UTRAN Attempts)

1) For PS Paging GERAN Successes and Attempts, refer to PS Paging Success Rate for GERAN (%)
2) For PS Paging UTRAN Successes and Attempts, refer to PS Paging Success Rate for UTRAN (%)

PS Paging GERAN SR = PS Paging GERAN Success / PS Paging GERAN Attempts

1) PS Paging GERAN Attempts should include initial request

2) PS Paging GERAN Attempts should include first attempts only
3) PS Paging GERAN Successes should include first and second responses

PS Paging UTRAN SR = PS Paging UTRAN Success / PS Paging UTRAN Attempts

1) PS Paging UTRAN Attempts should include initial request

2) PS Paging UTRAN Attempts should include first attempts only
3) PS Paging UTRAN Successes should include first and second responses

Periodic RAU GERAN SR = Periodic RAU GERAN Success / Periodic RAU GERAN Attempts

1) Periodic RAU GERAN Attempts should include initial request

2) Periodic RAU GERAN Attempts and Periodic RAU GERAN Successes should only include Periodic RAU
Periodic RAU UTRAN SR = Periodic RAU UTRAN Success / Periodic RAU UTRAN Attempts

1) Periodic RAU UTRAN Attempts should include initial request

2) Periodic RAU UTRAN Attempts and Periodic RAU UTRAN Successes should only include Periodic RAU
Combined RAU/LAU SR = (RAU/LAU GERAN Successes + RAU/LAU UTRAN Successes) / (RAU/LAU GERAN Attempts + RAU/LAU UTRAN Attempts)

1) RAU/LAU GERAN Attempts and RAU/LAU UTRAN Attempts should include initial request

Combined GERAN RAU/LAU SR = (RAU/LAU GERAN Successes) / (RAU/LAU GERAN Attempts)

1) RAU/LAU GERAN Attempts should include initial request

Combined UTRAN RAU/LAU SR = (RAU/LAU UTRAN Successes) / (RAU/LAU UTRAN Attempts)

1) RAU/LAU UTRAN Attempts should include initial request

Inter SGSN RAU GERAN SR = Inter SGSN RAU GERAN Successes / Inter SGSN RAU UTRAN Attempts

1) Inter SGSN RAU UTRAN Attempts should include initial request

2) Inter SGSN RAU UTRAN Attempts and Inter SGSN RAU UTRAN Successes should include GERAN measurements only.

Inter SGSN RAU UTRAN SR = Inter SGSN RAU UTRAN Successes / Inter SGSN RAU UTRAN Attempts

1) Inter SGSN RAU UTRAN Attempts should include initial request

2) Inter SGSN RAU UTRAN Attempts and Inter SGSN RAU UTRAN Successes should include UTRAN measurements only.

Intra SGSN RAU GERAN SR = Intra SGSN RAU GERAN Successes / Intra SGSN RAU UTRAN Attempts

1) Intra SGSN RAU UTRAN Attempts should include initial request

2) Intra SGSN RAU UTRAN Attempts and Intra SGSN RAU UTRAN Successes should include GERAN measurements only.

Intra SGSN RAU UTRAN SR = Intra SGSN RAU UTRAN Successes / Intra SGSN RAU UTRAN Attempts

1) Intra SGSN RAU UTRAN Attempts should include initial request

2) Intra SGSN RAU UTRAN Attempts and Intra SGSN RAU UTRAN Successes should include UTRAN measurements only.

SGSN Authentication SR = SGSN Authentication Successes / SGSN Authentication Attempts

1) SGSN Authentication Attempts should include initial requests

DNS Query SR = DNS Success / DNS Attempts

1) Attempts should include initial request

RAB Background (SGSN) SR = (RAB Background (SGSN) Successes + RAB Interactive (SGSN) Successes + RAB Streaming (SGSN) Successes) / (RAB Backgro
Interactive (SGSN) Attempts + RAB Streaming (SGSN) Attempts)

1) SGSN RAB Successes and SGSN RAB Attempts include PS Background, Interactive, and Stremaing
2) SGSN RAB Successes and SGSN RAB Attempts are the same in RAB Success Rate and CSSR
3) SGSN RAB Successes and SGSN RAB Attempts should NOT include Repeat Attempts
4) SGSN RAB Successes and SGSN RAB Attempts are measured at the SGSN

Data on IuPS interface in Kbits

1) Should include download and upload data

2) Should include R99, HSUPA, and HSDPA data
3) Should contain payload data only

Data on Gb interface in Kbits

1) Should include download and upload data

2) Should include GERAN data only
3) Should contain payload data only

Data on Gp interface in Kbits

1) Should include download and upload data

2) Should contain payload data only

Count of attached Subscribers on GERAN network

1) Should include downlink and uplink users

2) Should include users of GPRS and E-GPRS data
3) Should report maximum users in Active, Standy, and Idle State for one hour

Count of PDP Activated Subscribers on GERAN network

1) Should include downlink and uplink users

2) Should include users of GPRS and E-GPRS data
3) Should report maximum users in Active State with an Active PDP Context for one hour

Count of attached Subscribers on GERAN network

1) Should include downlink and uplink users

2) Should include users of GPRS and E-GPRS data
3) Should report average users in Active, Standy, and Idle State for one hour

Count of PDP Activated Subscribers on GERAN network

1) Should include downlink and uplink users

2) Should include users of GPRS and E-GPRS data
3) Should report average users in Active State with an Active PDP Context for one hour

Count of attached Subscribers on UTRAN network

1) Should include downlink and uplink users

2) Should include R99, HSUPA, and HSDPA users
3) Should report maximum users in Active, Standy, and Idle State for one hour

Count of PDP Activated Subscribers on UTRAN network

1) Should include downlink and uplink users

2) Should include R99, HSUPA, and HSDPA users
3) Should report maximum users in Active State with an Active PDP Context for one hour
Count of attached Subscribers on UTRAN network

1) Should include downlink and uplink users

2) Should include R99, HSUPA, and HSDPA users
3) Should report average users in Active, Standy, and Idle State for one hour

Count of PDP Activated Subscribers on UTRAN network

1) Should include downlink and uplink users

2) Should include R99, HSUPA, and HSDPA users
3) Should report average users in Active State with an Active PDP Context for one hour

Count of HSDPA users

1) Should NOT include users of R99 Download and HSUPA data

3) Should report maximum users in Active State with an Active PDP Context for one hour

Count of HSUPA users

1) Should NOT include users of R99 Upload and HSDPA data

3) Should report maximum users in Active State with an Active PDP Context for one hour

Count of PDP Activated HSDPA users

1) Should NOT include users of R99 Download and HSUPA data

3) Should report average users in Active State with an Active PDP Context for one hour

Count of PDP Activated HSUPA users

1) Should NOT include users of R99 Upload and HSDPA data

3) Should report average users in Active State with an Active PDP Context for one hour