SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.

2001 Company

1 (21) Confidential v.0.7

2G-SGSN KPIS Company Confidential Owner: Status: Vesa Ol. Heikkil Draft

Change History Issue v.0.1 v.0.2 v.0.3 v.0.4 v.0.5 v.0.6 v.0.7 Date Comments

22.12.2000 First draft 23.01.2001 KPIs s_26 - s_33 added 02.02.2001 KPI s_26 content changed, KPIs s_34 s_35 added 20.03.2001 KPIs s_36 - s_ 42 added 07.05.2001 Counter descriptions removed 06.06.2001 KPIs s_43 - s_48 added 18.09.2001 KPIs s_28b , s_29b and s_30b added, s_35 and s_46 corrected

Approved by

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

2 (21) Confidential v.0.7

TABLE OF CONTENTS
2G-SGSN KPIS.................................................................................................................................... 1 1. INTRODUCTION.............................................................................................................................. 4 2. 2G-SGSN KPIs................................................................................................................................. 4 2.1 Quality of Service KPIs................................................................................................................ 4 2.1.1 Attach attempts failure ratio, SG1 (s_1)................................................................................4 2.1.2 GPRS attach attempts failure ratio, SG1 (s_2).....................................................................4 2.1.3 Combined GPRS/IMSI attach attempts failure ratio, SG1 (s_3)...........................................5 2.1.4 IMSI attach attempts failure ratio, SG1 (s_4)........................................................................5 2.1.5 Failure ratio of GPRS and combined GPRS/IMSI attach attempts, SG1 (s_31)...................5 2.1.6 MO PDP context activations failure ratio, SG1 (s_5)............................................................6 2.1.7 MO PDP context deactivations failure ratio, SG1 (s_6)........................................................6 2.1.8 Failure ratio of MO and NWR PDP context activation attempts, SG1 (s_32)........................6 2.1.9 Ratio of discarded DL GTP packets, SG1 (s_7)...................................................................7 2.1.10 RA update failure ratio in PAPU, SG1 (s_12).....................................................................7 2.1.11 Failure ratio of RA updates, (s_30).....................................................................................7 2.1.12 Failure ratio of RA updates, SG1 (s_30b)...........................................................................8 2.1.13 Discarded CDR ratio, SG1 (s_13)......................................................................................9 2.1.14 Resent CDR ratio, SG1 (s_14)...........................................................................................9 2.1.15 NS-VC CIR overflow ratio, SG1 (s_15)...............................................................................9 2.1.16 MS-BVC overflow ratio, SG1 (s_16).................................................................................10 2.1.17 Average BSSGP buffer utilization ratio, SG1 (s_21).........................................................10 2.1.18 VJHC compression ratio, SG1 (s_24)...............................................................................10 2.1.19 V42bis compression ratio, SG1 (s_25).............................................................................11 2.1.20 Failure ratio of MO and MT short message delivery attemps, SG1 (s_33).......................11 2.1.21 Average load rate of the object unit processor, SG1 (s_26).............................................11 2.1.22 Failure ratio of BSSGP MS-BVC flow control passed data, SG1 (s_42)...........................12 2.2 Traffic KPIs............................................................................................................................... 12 2.2.1 Number of intra PAPU RA updates, SG1 (s_8)..................................................................12 2.2.2 Number of inter PAPU RA updates, SG1 (s_9)..................................................................12 2.2.3 Number of inter SGSN RA updates, SG1 (s_10)................................................................13 2.2.4 Number of periodic RA updates, SG1 (s_11).....................................................................13 2.2.5 Successful RA updates, (s_28)..........................................................................................13 2.2.6 Successful RA updates, SG1 (s_28b)................................................................................14 2.2.7 Number of intra PAPU RA updates, (s_29)........................................................................14 2.2.8 Failed RA updates, SG1 (s_29b)........................................................................................15 2.2.9 GTP packets sent in UL direction, SG1 (s_17)...................................................................15 2.2.10 GTP packets sent in DL direction, SG1 (s_18).................................................................15

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

3 (21) Confidential v.0.7

2.2.11 GTP data in Kbytes sent in UL, SG1 (s_19).....................................................................16 2.2.12 GTP data in Kbytes sent in DL, SG1 (s_20).....................................................................16 2.2.13 Discarded DL Kbytes in BSSGP , SG1 (s_27)..................................................................16 2.2.14 Average PDP context duration, SG1 (s_22).....................................................................16 2.2.15 Average amount of attached subscibers per PAPU, SG1 (s_23)......................................17 2.2.16 Average cell count per PAPU, SG1 (s_34).......................................................................17 2.2.17 Number of successful pagings, SG1 (s_35).....................................................................17 2.2.18 Number of successful GPRS and combined GPRS/IMSI attaches, SG1 (s_36)...............18 2.2.19 Number of failed GPRS, combined GPRS/IMSI and undefined attach attempts, SG1 (s_37) .................................................................................................................................................... 18 2.2.20 Number of successful MO and NWR context activations, SG1 (s_38).............................18 2.2.21 Number of failed MO and NWR context activation attempts, SG1 (s_39).........................19 2.2.22 Number of successfully delivered MO and MT short messages, SG1 (s_40)...................19 2.2.23 Number of failed MO and MT short message delivery attempts, SG1 (s_41)...................19 2.2.24 Discarded DL Kbytes in BSSGP due to buffer overflow, SG1 (s_43)...............................20 2.2.25 Discarded DL Kbytes in BSSGP due to max data amount exceeded, SG1 (s_44)...........20 2.2.26 Maximum NS-VC passed DL data in Kbytes, SG1 (s_45)................................................20 2.2.27 Average NS-VC discarded DL data due to CIR overflow in Kbytes, SG1 (s_46)..............20 2.2.28 BSSGP MS-BVC flow control passed data in Kbytes, SG1 (s_47)...................................21 2.2.29 BSSGP MS-BVC flow control discarded data in Kbytes, SG1 (s_48)...............................21 2.2.17 Number of successful RA pagings (s_35)......................................................................................... 2.2.18 Number of successful GPRS and combined GPRS/IMSI attaches (s_36)................................................. 2.2.19 Number of failed GPRS, combined GPRS/IMSI and undefined attach attempts (s_37)................................ 2.2.20 Number of successful MO and NWR PDP context activations (s_38)..................................................... 2.2.21 Number of failed MO and NWR PDP context activation attempts (s_39)................................................. 2.2.22 Number of successfully delivered MO and MT short messages (s_40)..................................................... 2.2.23 Number of failed MO and MT short message delivery attempts (s_41).................................................... 2.2.24 Discarded DL Kbytes in BSSGP due to buffer overflow (s_43)............................................................. 2.2.25 Discarded DL Kbytes in BSSGP due to max data amount exceeded (s_44).............................................. 2.2.26 Maximum NS-VC passed DL data in Kbytes (s_45)........................................................................... 2.2.27 Average NS-VC discarded DL data due to CIR overflow in Kbytes (s_46).............................................. 2.2.28 BSSGP MS-BVC flow control passed data in Kbytes (s_47)................................................................ 2.2.29 BSSGP MS-BVC flow control discarded data in Kbytes (s_48)............................................................

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

4 (21) Confidential v.0.7

1.

INTRODUCTION
The purpose of this document is to introduce some formulas to be used as Key Performance Indicators (KPIs) with 2G-SGSN statistics measurement counters. Part of this document is taken from GPRS KPIs document owned by Inka Martti and Jani-Pekka Virtanen. This document is a working document for internal use.

2. 2.1
2.1.1

2G-SGSN KPIS Quality of Service KPIs

Attach attempts failure ratio, SG1 (s_1) This KPI gives a failure ratio for different type of attempts

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Fail_GPRS_attach + Fail_combined_attach + Fail_IMSI_attach) ------------------------------------------------------------------------------------- * 100 % Sum(Succ_GPRS_attach + Fail_GPRS_attach + Succ_combined_attach + Fail_combined_attach + Succ_IMSI_attach + Fail_IMSI_attach) Counters from table(s): p_ sgsn_ mobility_ management

2.1.2 Use:

GPRS attach attempts failure ratio, SG1 (s_2) This KPI gives a failure ratio for GPRS attach attempts and should be used mainly for trouble shootin purposes.

Experiences on use: Known problems: Open questions: PM Class: Formula:

Sum(Fail_GPRS_attach)

All used counters from GPRS Mobility Management Measurement

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

5 (21) Confidential v.0.7

---------------------------------------- * 100 % Sum(Succ_GPRS_attach + Fail_GPRS_attach) Counters from table(s): p_ sgsn_ mobility_ management

2.1.3 Use:

Combined GPRS/IMSI attach attempts failure ratio, SG1 (s_3) This KPI gives a failure ratio for combined GPRS/IMSI attach attempts and should be used mainly for trouble shootin purposes.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Fail_combined_attach) ------------------------------------------------ * 100 % Sum(Succ_combined_attach + Fail_combined_attach) Counters from table(s): p_ sgsn_ mobility_ management

2.1.4 Use:

IMSI attach attempts failure ratio, SG1 (s_4) This KPI gives a failure ratio for IMSI attach attempts and should be used mainly for trouble shootin purposes.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Fail_IMSI_attach) ----------------------------------------- * 100 % Sum(Succ_IMSI_attach + Fail_IMSI_attach) Counters from table(s): p_ sgsn_ mobility_ management

2.1.5 Use:

Failure ratio of GPRS and combined GPRS/IMSI attach attempts, SG1 (s_31) This KPI gives a failure rato for GPRS and combined GPRS/IMSI attach attempts and should be used mainly for trouble shootin purposes.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Fail_GPRS_attach + Fail_combined_attach + General_undef_attach_failure)

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

6 (21) Confidential v.0.7

----------------------------------------------------------------------------------------------- * 100 % Sum(Succ_GPRS_attach + Fail_GPRS_attach + Succ_combined_attach + Fail_combined_attach + General_undef_attach_failure) Counters from table(s): p_ sgsn_ mobility_ management

2.1.6 Use:

MO PDP context activations failure ratio, SG1 (s_5) This KPI gives a failure ratio for mobile originated PDP context activations. The Packet Data Protocol (PDP) context functions are network level functions that are used to bind a MS to various PDP addresses. After use these functions are used to unbind the MS from these addresses. When a MS is attached to the network, it has to activate all the addresses it wants to use for data traffic with the external networks.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Session Management Measurement

Sum(Fail_MO_PDP_context_act) ----------------------------------------------------- * 100 % Sum(Succ_MO_PDP_context_act + Fail_MO_PDP_context_act) Counters from table(s): p_ sgsn_ session_ management

2.1.7 Use:

MO PDP context deactivations failure ratio, SG1 (s_6) Activated PDP addresses have to be deactivated after the subscriber has finished using them. This KPI gives a failure ratio for mobile originated PDP context deactivations.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Session Management Measurement

Sum(Fail_MO_PDP_context_deact) --------------------------------------------------------- * 100 % Sum(Succ_MO_PDP_context_deact + Fail_MO_PDP_context_deact) Counters from table(s): p_ sgsn_ session_ management

2.1.8 Use:

Failure ratio of MO and NWR PDP context activation attempts, SG1 (s_32) This KPI gives a failure ratio for mobile originated and network requested PDP context activations.

Experiences on use:

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

7 (21) Confidential v.0.7

Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Session Management Measurement

Sum(Fail_MO_PDP_context_act + Fail_NWR_PDP_context_act) ----------------------------------------------------------------- * 100 % Sum(Succ_MO_PDP_context_act + Fail_MO_PDP_context_act + Succ_MO_PDP_context_act + Fail_MO_PDP_context_act) Counters from table(s): p_ sgsn_ session_ management

2.1.9 Use:

Ratio of discarded DL GTP packets, SG1 (s_7) The GPRS Tunneling Protocol (GTP) is used to tunnel the data and signalling between SGSN and GGSN. This KPI shows how many per cent of the sent downlink GTP packets are discarded. GTP may discard only downlink packets. The main reason for discarding is that GTP's buffer is temporarily full of packets sent with reliability class 2 (acknowledged LLC mode).

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement

Sum(Discarded_GTP_packets) ------------------------------------ * 100 % Sum(GTP_packets_sent_in_DL) Counters from table(s): p_ sgsn_ data

2.1.10

RA update failure ratio in PAPU, SG1 (s_12) This KPI gives an overall failure ratio of RA updates.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Fail_intra_PAPU_RA_updat + Fail_inter_PAPU_RA_updat + Fail_outg_intra_PAPU_RA_updat) -------------------------------------------------------------------------------------------------- * 100 % Sum(Succ_intra_PAPU_RA_updat + Fail_intra_PAPU_RA_updat + Succ_inter_PAPU_RA_updat + Fail_inter_PAPU_RA_updat + Succ_outg_inter_PAPU_RA_updat + Fail_outg_inter_PAPU_RA_updat) Counters from table(s): p_ sgsn_ mobility_ management

2.1.11

Failure ratio of RA updates, (s_30)

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

8 (21) Confidential v.0.7

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. This KPIs gives the ratio of failed RA updates.

All used counters from GPRS Mobility Management Measurement

Sum(Fail_intra_PAPU_RA_updat + Fail_intra_PAPU_RA_LA_updat + Fail_intra_PAPU_RA_updat_IMSI + Fail_inter_PAPU_RA_updat + Fail_inter_PAPU_RA_LA_updat + Fail_inter_PAPU_RA_updat_IMSI + Fail_inter_SGSN_RA_updat + Fail_inter_SGSN_RA_LA_updat + Fail_inter_SGSN_RA_updat_IMSI + Fail_periodical_RA_updat + Fail_periodic_RA_LA_updat + Fail_outg_inter_PAPU_RA_updat + Fail_outg_inter_SGSN_RA_updat + General_undef_ra_updat_failure) -------------------------------------------------------------------------------------------------- * 100 % Sum(Succ_intra_PAPU_RA_updat + Succ_intra_PAPU_RA_LA_updat + Succ_intra_PAPU_RA_updat_IMSI + Succ_inter_PAPU_RA_updat + Succ_inter_PAPU_RA_LA_updat + Succ_inter_PAPU_RA_updat_IMSI + Succ_inter_SGSN_RA_updat + Succ_inter_SGSN_RA_LA_updat + Succ_inter_SGSN_RA_updat_IMSI + Succ_periodical_RA_updat + Succ_periodic_RA_LA_updat + Succ_outg_inter_PAPU_RA_updat + Succ_outg_inter_SGSN_RA_updat + Fail_intra_PAPU_RA_updat + Fail_intra_PAPU_RA_LA_updat + Fail_intra_PAPU_RA_updat_IMSI + Fail_inter_PAPU_RA_updat + Fail_inter_PAPU_RA_LA_updat + Fail_inter_PAPU_RA_updat_IMSI + Fail_inter_SGSN_RA_updat + Fail_inter_SGSN_RA_LA_updat + Fail_inter_SGSN_RA_updat_IMSI + Fail_periodical_RA_updat + Fail_periodic_RA_LA_updat + Fail_outg_inter_PAPU_RA_updat + Fail_outg_inter_SGSN_RA_updat + General_undef_ra_updat_failure) Counters from table(s): p_ sgsn_ mobility_ management

2.1.12 Use:

Failure ratio of RA updates, SG1 (s_30b) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. This KPIs gives the ratio of failed RA updates. Counters 1029, 1030, 1031 and 1032 are not supported in SG1 or SG2. They are not included in the formula s_30b.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Fail_intra_PAPU_RA_updat + Fail_intra_PAPU_RA_LA_updat + Fail_intra_PAPU_RA_updat_IMSI + Fail_inter_PAPU_RA_updat + Fail_inter_PAPU_RA_LA_updat + Fail_inter_PAPU_RA_updat_IMSI + Fail_inter_SGSN_RA_updat + Fail_inter_SGSN_RA_LA_updat + Fail_inter_SGSN_RA_updat_IMSI + Fail_periodical_RA_updat + Fail_periodic_RA_LA_updat + General_undef_ra_updat_failure) -------------------------------------------------------------------------------------------------- * 100 % Sum(Succ_intra_PAPU_RA_updat + Succ_intra_PAPU_RA_LA_updat + Succ_intra_PAPU_RA_updat_IMSI + Succ_inter_PAPU_RA_updat + Succ_inter_PAPU_RA_LA_updat + Succ_inter_PAPU_RA_updat_IMSI + Succ_inter_SGSN_RA_updat + Succ_inter_SGSN_RA_LA_updat + Succ_inter_SGSN_RA_updat_IMSI + Succ_periodical_RA_updat + Succ_periodic_RA_LA_updat + Fail_intra_PAPU_RA_updat + Fail_intra_PAPU_RA_LA_updat + Fail_intra_PAPU_RA_updat_IMSI + Fail_inter_PAPU_RA_updat + Fail_inter_PAPU_RA_LA_updat + Fail_inter_PAPU_RA_updat_IMSI

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

9 (21) Confidential v.0.7

+ Fail_inter_SGSN_RA_updat + Fail_inter_SGSN_RA_LA_updat + Fail_inter_SGSN_RA_updat_IMSI + Fail_periodical_RA_updat + Fail_periodic_RA_LA_updat + General_undef_ra_updat_failure) Counters from table(s): p_ sgsn_ mobility_ management

2.1.13

Discarded CDR ratio, SG1 (s_13) This KPI gives an overall ratio of discarded CDRs.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from CDR Measurement:

Sum(Discarded_S-CDRs_due_overflow + Discarded_M-CDRs_due_overflow + Discarded_SMO-CDRs_due_overflow + Discarded_SMT-CDRs_due_overflow + Discarded_S-CDRs_due_other + Discarded_M-CDRs_due_other + Discarded_SMO-CDRs_due_other + Discarded_SMT-CDRs_due_other) ---------------------------------------------------------------------------------------- * 100 % Sum(Received_S-CDRs + Received_M-CDRs + Received_SMO-CDRs + Received_SMT-CDRs) Counters from table(s): p_ sgsn_ cdr

2.1.14

Resent CDR ratio, SG1 (s_14) This KPI gives an overall ratio of resent CDRs.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from CDR Measurement:

Sum(Resent_S-CDRs + Resent_M-CDRs + Resent_SMO-CDRs + Resent_SMT-CDRs) --------------------------------------------------------------------------------------- * 100 % Sum(received_S-CDRs + Received_M-CDRs + Received_SMO-CDRs + Received_SMT-CDRs) Counters from table(s): p_ sgsn_ cdr

2.1.15

NS-VC CIR overflow ratio, SG1 (s_15) This KPI gives an overall ratio for data buffered due to FR. High values with this KPI indicate capacity problems i.e. the size of the Gb link might not be correct.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(NSVC_disc_data_cir_overflow)

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

10 (21) Confidential v.0.7

------------------------------------- --------------------- * 100 % Sum(NSVC_disc_data_cir_overflow + NSVC_passed_data_in_bytes) Counters from table(s): p_sgsn_data

2.1.16

MS-BVC overflow ratio, SG1 (s_16) This KPI gives an overall ratio for data buffered due to flow control. High values with this KPI indicate capacity problems i.e. the size of the cell might not be correct.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Cell Data Measurement:

Sum(Discarded_data_by_BSSGP) ------------------------------------- ------------------ * 100 % Sum(Discarded_data_by_BSSGP + BSSGP_passed_data_in_bytes) Counters from table(s): p_ sgsn_ cell_ data

2.1.17

Average BSSGP buffer utilization ratio, SG1 (s_21) This KPI shows average BSSGP buffer utilization ratio. High values with this KPI indicate capacity problems. Only downlink data is stored to buffer.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(Ave_BSSGP_buff_util_sum) -------------------------------------Sum(Ave_BSSGP_buff_util_den) Counters from table(s): p_ sgsn_ data

2.1.18

VJHC compression ratio, SG1 (s_24) This KPI shows the efficiency of Van Jacobssen Header Compression.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(Bytes_out_of_VJHC_compression) -------------------------------------------- * 100 % Sum(Bytes_in_for_VJHC_compression) Counters from table(s):

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

11 (21) Confidential v.0.7

p_ sgsn_ data

2.1.19

V42bis compression ratio, SG1 (s_25) This KPI shows the efficiency of V42bis compression.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(Bytes_out_of_V42bis_compression) ---------------------------------------------- * 100 % Sum(Bytes_in_for_V42bis_compression) Counters from table(s): p_ sgsn_ data

2.1.20

Failure ratio of MO and MT short message delivery attemps, SG1 (s_33) This KPI tells the ratio of failed MO and MT short message delivery attemps.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from SMS Measurement:

Sum(Failed_MO_SMS_deliveries + Failed_MT_SMS_deliveries) ---------------------------------------------------------------------- * 100 % Sum(Successfully_sent_MO_SMS + Failed_MO_SMS_deliveries + Successfully_received_MT_SMS + Failed_MT_SMS_deliveries) Counters from table(s): p_ sgsn_ sms

2.1.21

Average load rate of the object unit processor, SG1 (s_26) This KPI shows average load rate of the object unit processor.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Load Measurement:

Sum(Ave_load_rate_sum) -------------------------------Sum(Ave_load_rate_den) Counters from table(s): p_ sgsn_ load

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

12 (21) Confidential v.0.7

2.1.22

Failure ratio of BSSGP MS-BVC flow control passed data, SG1 (s_42) This KPI tells the failure ratio of BSSGP MS-BVC flow control passed data.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Cell Data Measurement:

Sum(Discarded_data_by_BSSGP) ------------------------------------------------ * 100 % Sum(BSSGP_passed_data + Discarded_data_by_BSSGP) Counters from table(s): p_ sgsn_ cell_ data

2.2
2.2.1 Use:

Traffic KPIs
Number of intra PAPU RA updates, SG1 (s_8) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. KPIs ( s_8) (s_12) give the number of different type of RA updates.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Succ_intra_PAPU_RA_updat + Fail_intra_PAPU_RA_updat + Succ_intra_PAPU_RA_LA_updat + Fail_intra_PAPU_RA_LA_updat + Succ_intra_PAPU_RA_updat_IMSI + Fail_intra_PAPU_RA_updat_IMSI) Counters from table(s): p_ sgsn_ mobility_ management

2.2.2 Use:

Number of inter PAPU RA updates, SG1 (s_9) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. KPIs ( s_8) (s_12) give the number of different type of RA updates.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

13 (21) Confidential v.0.7

Sum(Succ_inter_PAPU_RA_updat + Fail_inter_PAPU_RA_updat + Succ_inter_PAPU_RA_LA_updat + Fail_inter_PAPU_RA_LA_updat + Succ_inter_PAPU_RA_updat_IMSI + Fail_inter_PAPU_RA_updat_IMSI) Counters from table(s): p_ sgsn_ mobility_ management

2.2.3 Use:

Number of inter SGSN RA updates, SG1 (s_10) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. KPIs ( s_8) (s_12) give the number of different type of RA updates.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Succ_inter_SGSN_RA_updat + Fail_inter_SGSN_RA_updat + Succ_inter_SGSN_RA_LA_updat + Fail_inter_SGSN_RA_LA_updat + Succ_inter_SGSN_RA_updat_IMSI + Fail_inter_SGSN_RA_updat_IMSI) Counters from table(s): p_ sgsn_ mobility_ management

2.2.4 Use:

Number of periodic RA updates, SG1 (s_11) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. KPIs ( s_8) (s_12) give the number of different type of RA updates.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Succ_periodic_RA_updat + Fail_periodic_RA_updat + Succ_periodic_RA_LA_updat + Fail_periodic_RA_LA_updat) Counters from table(s): p_ sgsn_ mobility_ management

2.2.5 Use:

Successful RA updates, (s_28) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. This KPIs gives the number of successful RA updates.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

14 (21) Confidential v.0.7

Sum(Succ_intra_PAPU_RA_updat + Succ_intra_PAPU_RA_LA_updat + Succ_intra_PAPU_RA_updat_IMSI + Succ_inter_PAPU_RA_updat + Succ_inter_PAPU_RA_LA_updat + Succ_inter_PAPU_RA_updat_IMSI + Succ_inter_SGSN_RA_updat + Succ_inter_SGSN_RA_LA_updat + Succ_inter_SGSN_RA_updat_IMSI + Succ_periodical_RA_updat + Succ_periodic_RA_LA_updat + Succ_outg_inter_PAPU_RA_updat + Succ_outg_inter_SGSN_RA_updat) Counters from table(s): p_ sgsn_ mobility_ management

2.2.6 Use:

Successful RA updates, SG1 (s_28b) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. This KPIs gives the number of successful RA updates. Counters 1029 and 1031 are not supported in SG1 or SG2. They are not included in the formula s_28b.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Succ_intra_PAPU_RA_updat + Succ_intra_PAPU_RA_LA_updat + Succ_intra_PAPU_RA_updat_IMSI + Succ_inter_PAPU_RA_updat + Succ_inter_PAPU_RA_LA_updat + Succ_inter_PAPU_RA_updat_IMSI + Succ_inter_SGSN_RA_updat + Succ_inter_SGSN_RA_LA_updat + Succ_inter_SGSN_RA_updat_IMSI + Succ_periodical_RA_updat + Succ_periodic_RA_LA_updat) Counters from table(s): p_ sgsn_ mobility_ management

2.2.7 Use:

Number of intra PAPU RA updates, (s_29) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. This KPIs gives the number of failed RA updates.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Fail_intra_PAPU_RA_updat + Fail_intra_PAPU_RA_LA_updat + Fail_intra_PAPU_RA_updat_IMSI + Fail_inter_PAPU_RA_updat + Fail_inter_PAPU_RA_LA_updat + Fail_inter_PAPU_RA_updat_IMSI + Fail_inter_SGSN_RA_updat + Fail_inter_SGSN_RA_LA_updat + Fail_inter_SGSN_RA_updat_IMSI + Fail_periodical_RA_updat + Fail_periodic_RA_LA_updat + Fail_outg_inter_PAPU_RA_updat + Fail_outg_inter_SGSN_RA_updat + General_undef_ra_updat_failure) Counters from table(s): p_ sgsn_ mobility_ management

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

15 (21) Confidential v.0.7

2.2.8 Use:

Failed RA updates, SG1 (s_29b) A Routing Area (RA) is a subset of one Location Area (LA). RA cannot span more than one LA. A RA is served by only one SGSN. This KPIs gives the number of failed RA updates. Counters 1030 and 1032 are not supported in SG1 or SG2. They are not included in the formula s_29b.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from GPRS Mobility Management Measurement

Sum(Fail_intra_PAPU_RA_updat + Fail_intra_PAPU_RA_LA_updat + Fail_intra_PAPU_RA_updat_IMSI + Fail_inter_PAPU_RA_updat + Fail_inter_PAPU_RA_LA_updat + Fail_inter_PAPU_RA_updat_IMSI + Fail_inter_SGSN_RA_updat + Fail_inter_SGSN_RA_LA_updat + Fail_inter_SGSN_RA_updat_IMSI + Fail_periodical_RA_updat + Fail_periodic_RA_LA_updat + General_undef_ra_updat_failure) Counters from table(s): p_ sgsn_ mobility_ management

2.2.9 Use:

GTP packets sent in UL direction, SG1 (s_17) This KPI can be used together with the KPI called Ratio of discarded GTP packets (s_7) in the same report. It is probably better to use bytes than the number of packets to find out the amount of traffic in the network. The reason for this is that the size of packets can vary. This counter will not give the right picture of the amount of traffic in the network.

Experiences on use: Known problems: Open questions: PM Class: Formula:

This counter is from Data Measurement:

Sum(GTP_packets_sent_in_UL) Counters from table(s): p_ sgsn_ data

2.2.10 Use:

GTP packets sent in DL direction, SG1 (s_18) This KPI can be used together with the KPI called Ratio of discarded GTP packets (s_7) in the same report. It is probably better to use bytes than the number of packets to find out the amount of traffic in the network. The reason for this is that the size of packets can vary. This counter will not give the right picture of the amount of traffic in the network. This counter is from Data Measurement:

Experiences on use: Known problems: Open questions: PM Class: Formula:

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

16 (21) Confidential v.0.7

GTP_packets_sent_in_DL Counters from table(s): p_ sgsn_ data

2.2.11

GTP data in Kbytes sent in UL, SG1 (s_19)

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

This counter is from Data Measurement:

Sum(GTP_data_in_bytes_sent_in_UL)/1000 Counters from table(s): p_ sgsn_ data

2.2.12

GTP data in Kbytes sent in DL, SG1 (s_20)

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

This counter is from Data Measurement:

Sum(GTP_data_in_bytes_sent_in_DL)/1000 Counters from table(s): p_ sgsn_ data

2.2.13 Use:

Discarded DL Kbytes in BSSGP , SG1 (s_27) This KPI tells the sum of discarded DL Kbytes in BSSGP due to buffer overflow and due to maximum data amount exceeded.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(BSSGP_lost_data_due_buffer + BSSGP_lost_data_due_amount)/1000 Counters from table(s): p_ sgsn_ data

2.2.14

Average PDP context duration, SG1 (s_22)

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

17 (21) Confidential v.0.7

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

This KPI gives average duration of PDP context.

All used counters from User Measurement:

Sum(Ave_PDP_context_duration_sum) ------------------------------------------Sum(Ave_PDP_context_duration_den) Counters from table(s): p_ sgsn_ user

2.2.15 Use:

Average amount of attached subscibers per PAPU, SG1 (s_23) This KPI shows average amount of attached subscribers per PAPU (Packet Processing Unit).

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(Ave_attach_subscr_per_PAPU_sum) --------------------------------------------Sum(Ave_attach_subscr_per_PAPU_den) Counters from table(s): p_ sgsn_ data

2.2.16

Average cell count per PAPU, SG1 (s_34) This KPI shows average cell count per PAPU (Packet Processing Unit).

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(Ave_cell_count_per_PAPU_sum) -----------------------------------------Sum(Ave_cell_count_per_PAPU_den) Counters from table(s): p_ sgsn_ data

2.2.17

Number of successful pagings, SG1 (s_35) This KPI tells the number of successful pagings.

Use: Experiences on use:

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

18 (21) Confidential v.0.7

Known problems: Open questions: PM Class: Formula:

All used counters from Paging Measurement:

Sum(RA_level_pagings + SGSN_level_pagings) Counters from table(s): p_ sgsn_ paging

2.2.18 Use:

Number of successful GPRS and combined GPRS/IMSI attaches, SG1 (s_36) This KPI tells the number of successful GPRS and combined GPRS/IMSI attaches.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Mobility Management Measurement:

Sum(Succ_GPRS_attach + Succ_combined_attach) Counters from table(s): p_ sgsn_ mobility_ management

2.2.19 (s_37) Use:

Number of failed GPRS, combined GPRS/IMSI and undefined attach attempts, SG1 This KPI tells the number of failed GPRS, combined GPRS/IMSI and undefined attach attempts.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Mobility Management Measurement:

Sum(Fail_GPRS_attach + Fail_combined_attach + General_undef_attach_failure) Counters from table(s): p_ sgsn_ mobility_ management

2.2.20

Number of successful MO and NWR context activations, SG1 (s_38) This KPI tells the number of successful MO and NWR context activations.

Use: Experiences on use: Known problems: Open questions: PM Class:

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

19 (21) Confidential v.0.7

Formula:

All used counters from Session Management Measurement:

Sum(Succ_MO_PDP_context_act + Succ_NWR_PDP_context_act) Counters from table(s): p_ sgsn_ session_ management

2.2.21

Number of failed MO and NWR context activation attempts, SG1 (s_39) This KPI tells the number of failed MO and NWR context activation attempts.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Session Management Measurement:

Sum(Fail_MO_PDP_context_act + Fail_NWR_PDP_context_act) Counters from table(s): p_ sgsn_ session_ management

2.2.22

Number of successfully delivered MO and MT short messages, SG1 (s_40) This KPI tells the number of successfully delivered MO and MT short messages.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from SMS Measurement:

Sum(Successfully_sent_MO_SMS + Successfully_received_MT_SMS) Counters from table(s): p_ sgsn_ sms

2.2.23

Number of failed MO and MT short message delivery attempts, SG1 (s_41) This KPI tells the number of failed MO and MT short message delivery attempts.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from SMS Measurement:

Sum(Failed_MO_SMS_deliveries + Failed_MT_SMS_deliveries) Counters from table(s): p_ sgsn_ sms

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

20 (21) Confidential v.0.7

2.2.24

Discarded DL Kbytes in BSSGP due to buffer overflow, SG1 (s_43) This KPI tells the sum of discarded DL Kbytes in BSSGP due to buffer overflow.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(BSSGP_lost_data_due_buffer)/1000 Counters from table(s): p_ sgsn_ data

2.2.25 Use:

Discarded DL Kbytes in BSSGP due to max data amount exceeded, SG1 (s_44) This KPI tells the sum of discarded DL Kbytes in BSSGP due to maximum data amount exceeded.

Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Sum(BSSGP_lost_data_due_amount)/1000 Counters from table(s): p_ sgsn_ data

2.2.26

Maximum NS-VC passed DL data in Kbytes, SG1 (s_45) This KPI tells the maximum amount of NS-VC passed DL data in Kbytes.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Data Measurement:

Max(NSVC_passed_data_in_bytes)/1000 Counters from table(s): p_ sgsn_ data

2.2.27 Use:

Average NS-VC discarded DL data due to CIR overflow in Kbytes, SG1 (s_46) This KPI tells the average amount of NS-VC discarded DL data due to CIR overflow in Kbytes.

Experiences on use: Known problems:

SPECIFICATION OSS/Tampere PCH/Content Creation Vesa Ol. Heikkil 18.09.2001 Company

21 (21) Confidential v.0.7

Open questions: PM Class: Formula:

All used counters from Data Measurement:

Avg(NSVC_disc_data_cir_overflow)/1000 Counters from table(s): p_ sgsn_ data

2.2.28

BSSGP MS-BVC flow control passed data in Kbytes, SG1 (s_47) This KPI tells the amount of MS-BVC passed data in Kbytes.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Cell Data Measurement:

Sum(BSSGP_passed_data_in_bytes)/1000 Counters from table(s): p_ sgsn_ cell_ data

2.2.29

BSSGP MS-BVC flow control discarded data in Kbytes, SG1 (s_48) This KPI tells the amount of MS-BVC discarded data in Kbytes.

Use: Experiences on use: Known problems: Open questions: PM Class: Formula:

All used counters from Cell Data Measurement:

Sum(Discarded_data_by_BSSGP)/1000 Counters from table(s): p_ sgsn_ cell_ data