1

% Core Packet Switched Network PDP

context load
Contact MorpheusSupport@orange.ch if you have questions about this
metric.

Status

Status : Proposed

Justification : Packet Core Capacity KPI - presents number of active Packet Core Sessions at
measurement time Valuable to present current usage of GGSN license

Ownership : Denis Gros-Jean + 33 1 57 36 17 27

Definition

Definition : Number of PDP contexts at BH (all GGSNs) / GGSNs PDP contexts available Capacity -
End of Period

Frequency : Monthly

Units : %

Data Source : SGSNs and GGSNs Measurements (both sources should be used and reported for
comparison reasons);alternatively signalling probes

Calculation Rule : Sum of Number of PdP contexts at BH of the end period for all types of packet
access and interfaces taken from all SGSNs or GGSN in the given Packet Network divided by the total
capacity of pdp contexts of the packet network * 100

Morpheus code:

Vendor Formulas

NSN:

For NSN counters which could be used for calculation of PDP load
are present in SGSN and GGSN
SGSN SG6:
[ PEAK PDP CONTEX (GB+IU) / SW PDP
license ] * 100 where i=number of SGSNs
GGSN FI3:
[ pdpContextsActive / SW PDP license ] *
100 where i=number of GGSNs
 2

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

PS6 and PS7. In both versions, there is SGSN and GGSN counter which could
be used for PDP load calculation. However, these two KPIs should be
compared to confirm their precision:
SGSN PS6 & PS7:
[ {Gb mode max users with act PDP context
+ Iu mode max users with active PDP context} / SW PDP license ] * 100
where i=number of SGSNs
GGSN PS6 & PS7:
[ Maximum PDP contexts / SW PDP license ] *
100 where i=number of GGSNs

Ericsson:

SGSN2008B :
(NbrActPdpContext.G + NbrActPdpContext.U) / SW PDP
Licence *100
GGSN R4-M20 and 2009A-M120:
ggsnNbrOfActivePdpContexts / SW PDP Licence * 100

Other Information

Notes:

- Even if it is a calculation for the whole network, it is important

that for each SGSN and GGSN, th target value is approx. < 70%
- for NSN SGSN "peak pdp contex (Gb+Iu)" is the counter no 4055
- for NSN GGSN "pdpContestsActive" is the counter id PDP005
- for Huawei GGSN PS6 "Maximum simultaneously activated PDP contexts"
and for PS7 "Maximum PDP contexts" - in both cases it is counter id
1.1.17
- for Huawei SGSN PS6 & PS7 counters are "Gb mode max users with act
PDP context" - counter id 8.5.3 and "Iu mode max users with active PDP
context" - counter id 9.7.6

Typical Values:

Frequently Asked Questions:

 3

% Core Packet Switched SAU load

Contact MorpheusSupport@orange.ch if you have questions about this
metric.

Status

Status : Proposed

Justification : Packet Core Capacity KPI - presents number of users (subscribers) currently attached
to MCO Packet Network Valuable to present number of subscriber having the access to MCO Packet
Core Network at time of measurement Dimensioning and licensing KPI for Packet Core NE such as
SGSNs

Ownership : Denis Gros-Jean + 33 1 57 36 17 27

Definition

Definition : Number of Number of Simultaneously Attached Users at BH (all SGSNs) / SGSNs SAU
available Capacity - End of Period

Frequency :Monthly

Units : %

Data Source : SGSN Measurements; alternatively signalling probes

Calculation Rule : Sum of Number of simultaneously Attached Users at BH of the end period for all
types of packet access and interfaces taken from all SGSNs in the given Packet Network divided by
the total capacity of SAU of the packet network * 100

Morpheus code:

Vendor Formulas

NSN:

SGSN SG6:
[ PEAK ATTACH USERS (GB+IU) / SW SAU License ]
* 100 where i=number of SGSNs
 4

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

PS6 and PS7. In both versions, there is SGSN counter which could be used
for calculation:
SGSN PS6 & PS7:
[ {Gb mode max attached users + Iu mode max
attached users} / SW SAU License ] * 100 where i=number of SGSNs

Ericsson:

SGSN2008B:
(NbrActAttachedSub.G + NbrActAttachedSub.U) / SW SAU Licence
* 100

Other Information

Notes:

- even if it is a calculation for the whole network, it is important

that for each SGSN, the target value is approx. < 70%
- For NSN SGSN the counter for peak attach users (Gb + Iu) is counter
no 4047
- for Huawei SGSN PS6 and PS7 it is "Gb mode max attached users" -
counter id 6.7.9 and "Iu mode max attached users" - counter id 7.8.7

Typical Values:

Max Core Packet-Switched Network SAU

Load
Contact MorpheusSupport@orange.ch if you have questions about this
metric.

Status

Status : Proposed

Justification : Packet Core Capacity KPI - presents number of users (subscribers) currently attached
 5

to MCO Packet Network Valuable to present number of subscriber having the access to MCO Packet
Core Network at time of measurement Dimensioning and licensing KPI for Packet Core NE such as
SGSNs

Ownership : denis.grosjean@orange-ftgroup.com Denis Gros-Jean + 33 1 57 36 17 27

Definition

Definition : [Maximum] Number of Simultaneously Attached Users in the measurement period for all
types of packet access (e.g. 2G, 3G) and interfaces (e.g. Gb, Iu)

Frequency : Monthly

Units : Number

Data Source : SGSN Measurements; alternatively signalling probes

Calculation Rule : Sum of [Maximum] Number of simultaneously Attached Users in measurement

period for all types of packet access and interfaces taken from all SGSNs in the given Packet Network

Morpheus code:

Vendor Formulas

NSN:

SGSN SG6:
PEAK ATTACH USERS (GB+IU) where i=number of
SGSNs

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

PS6 and PS7. In both versions, there is SGSN counter which could be used
for calculation:
SGSN PS6 & PS7:
{Gb mode max attached users + Iu mode max
attached users} where i=number of SGSNs

Ericsson:

SGSN2008B:
(NbrActAttachedSub.G + NbrActAttachedSub.U)
 6

Other Information

Notes:

- for NSN SGSN it is peak attach users (Gb + Iu) , counter no 4047
- for Huawei SGSN PS6 and PS7 it is "Gb mode max attached users" -
counter id 6.7.9 and "Iu mode max attached users" - counter id 7.8.7
- for Ericsson there is no counter Max on the SGSN, the used formula
is the same than SAU load

Typical Values:

Max Core Packet-Switched Network PDP

Load
Contact MorpheusSupport@orange.ch if you have questions about this
metric.

Status

Status : Proposed

Justification : Packet Core Capacity KPI - presents number of active Packet Core Sessions at
measurement time Valuable to present current usage of Packet Services Dimensioning and licensing
KPI for Packet Core NE such as SGSNs, GGSNs

Ownership : denis.grosjean@orange-ftgroup.com Denis Gros-Jean + 33 1 57 36 17 27

Definition

Definition : [Maximum] Number of PDP Contexts in the measurement period for all types of packet
access (e.g. 2G, 3G) and interfaces (e.g. Gb, Iu)

Frequency : Monthly

Units : Number

Data Source : SGSN Measurements; alternatively signalling probes

Calculation Rule : SGSNs and GGSNs Measurements (both sources should be used and reported for
 7

comparison reasons);alternatively signalling probes

Morpheus code:

Vendor Formulas

NSN:

For NSN counters which could be used for calculation of PDP Peak
rate are present in SGSN and GGSN.
SGSN SG6:
PEAK PDP CONTEX (GB+IU) where i=number of
SGSNs
GGSN FI3:
pdpContextsActive where
i=number of GGSNs

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

PS6 and PS7. In both versions, there is SGSN and GGSN counter which could
be used for PDP peak load calculation. However, these two KPIs should be
compared to confirm their precision:
SGSN PS6 & PS7:
{Gb mode max users with act PDP context +
Iu mode max users with active PDP context} where
i=number of SGSNs
GGSN PS6 & PS7:
Maximum PDP contexts where
i=number of GGSNs

Ericsson:

SGSN2008B:
NbrActPdpContext.G + NbrActPdpContext.U
GGSN R4-M20 and 2009A-M120:
ggsnNbrOfActivePdpContexts

Other Information

Notes:
 8

- for NSN SGSN "peak pdp contex (Gb+Iu)" is the counter no 4055
- for NSN GGSN "pdpContestsActive" is the counter id PDP005
- for Huawei GGSN PS6 "Maximum simultaneously activated PDP contexts"
and for PS7 "Maximum PDP contexts" - in both cases it is counter id
1.1.17
- for Huawei SGSN PS6 & PS7 counters are "Gb mode max users with act
PDP context" - counter id 8.5.3 and "Iu mode max users with active PDP
context" - counter id 9.7.6
- for Ericsson there is no Load max counters on the SGSN and GGSN.
This value should be picked at during the busy hours.

Max Throughput in BH
Contact MorpheusSupport@orange.ch if you have questions about this
metric.

Status

Status : Proposed

Justification : Packet Core KPI Used for dimensioning in Packet Core Networks Useful for growth
analysys and trends observation in MCO Packet Networks

Ownership : denis.grosjean@orange-ftgroup.com Denis Gros-Jean + 33 1 57 36 17 27

Definition

Definition : Amount of Uplink Bytes and Downlink Bytes send per second in MCO Packet Network.
Measured in BH

Frequency : Monthly

Units : Megabits per second

Data Source : SGSNs or GGSNs; alternatively signalling probes

Calculation Rule : Sum of Uplink and Downlink Bytes send by given type of network elements in MCO
Network (SGSNs or GGSNs) divided by time of measurement given in seconds. Measures taken for
BH on daily basis.

Morpheus code:

Vendor Formulas
 9

NSN:

Measures could be taken from both SGSN and GGSN level.

SGSN SG6:
Sum (GTP_DATA_IN_BYTES_SENT_IN_UL + GTP_DATA_IN_BYTES_SENT_IN_DL
) / Measurement time [s]
GGSN FI3:
Sum (GTPSTATINBYTES + GTPSTATOUTBYTES) /Measurement time [s]

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

PS6 and PS7. In both versions there are many SGSN and GGSN different
counters which could be used for such calculation - depending on MCO
needs. Some examples below:
SGSN PS6 & PS7:
Sum (GTP kbytes sent to GGSN + GTP kbytes received from GGSN) /
Measurement time [s]
GGSN PS6 & PS7:
Sum (Gn uplink traffic in MB + Gn downlink traffic in MB) /
Measurement time [s]

Ericsson:

SGSN2008B:
Sum (OutOctets.GN + InOctets.GN ) / 300 s

Other Information

Notes:

- For SGSN level, Measurements taken from Gn (GTP)

- for GGSN level, either from Gn (GTP) or Gi (pure user traffic, no
tunneling)
- for NSN SGSN it is "GTP DATA IN BYTES SENT IN UL" - counter id 3002
and "GTP DATA IN BYTES SENT IN DL" - counter id 3003
- for NSN GGSN it is "Bytes in GTP Packets Sent" - GTP005 and "Bytes
in GTP Packets Received" - GTP004
- for Huawei SGSN it could be for example "GTP kbytes sent to GGSN" -
counter id 4.4.7 and "GTP kbytes received from GGSN" - counter id 4.4.9
- for Huawei GGSN it could be for example "Gn uplink traffic in
packets" - counter id 2.1.9 and "Gn downlink traffic in MB" - counter id
 10

2.1.11
- for Ericsson these counters are pointed in the SGSN, it is
important to specify the Gn interface name

Core Packet-Switched Monthly data

volume
Contact MorpheusSupport@orange.ch if you have questions about this
metric.

Status

Status : Proposed

Justification : Packet Core KPI Useful for growth analysys and trends observation in MCO Packet
Networks

Ownership : denis.grosjean@orange-ftgroup.com Denis Gros-Jean + 33 1 57 36 17 27

Definition

Definition : Amount of Uplink Bytes and Downlink Bytes sent in MCO Network for given month.

Frequency : Monthly

Units : Megabits

Data Source : SGSNs or GGSNs; alternatively signalling probes

Calculation Rule : Sum of Uplink and Downlink Bytes send by given type of network elements in MCO
Network (SGSNs or GGSNs). Calculated on daily basis, aggregated to Monthly level.

Morpheus code:

Vendor Formulas

NSN:

Measures could be taken from both SGSN and GGSN level.

SGSN SG6:
Sum (GTP_DATA_IN_BYTES_SENT_IN_UL
 11

+GTP_DATA_IN_BYTES_SENT_IN_DL )
GGSN FI3:
Sum (GTPSTATINBYTES + GTPSTATOUTBYTES)

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

PS6 and PS7. In both versions there are many SGSN and GGSN different
counters which could be used for such calculation - depending on MCO
needs. Some examples below:
SGSN PS6 & PS7:
Sum (GTP kbytes sent to GGSN + GTP kbytes received from GGSN)
GGSN PS6 & PS7:
Sum (Gn uplink traffic in MB + Gn downlink traffic in MB)

Ericsson:

SGSN2008B :
Sum (OutOctets.GN + InOctets.GN)

Other Information

Notes:

- For SGSN level, Measurements taken from Gn (GTP)

- for GGSN level, either from Gn (GTP) or Gi (pure user traffic, no
tunnelling)
- for NSN SGSN it is "GTP DATA IN BYTES SENT IN UL" - counter id 3002
and "GTP DATA IN BYTES SENT IN DL" - counter id 3003
- for NSN GGSN it is "Bytes in GTP Packets Sent" - GTP005 and "Bytes
in GTP Packets Received" - GTP004
- for Huawei SGSN it could be for example "GTP kbytes sent to GGSN" -
counter id 4.4.7 and "GTP kbytes received from GGSN" - counter id 4.4.9
- for Huawei GGSN it could be for example "Gn uplink traffic in
packets" - counter id 2.1.9 and "Gn downlink traffic in MB" - counter id
2.1.11
- for Ericsson these counters are pointed in the SGSN, it is
important to specify the Gn interface name
 12

Core Packet-Switched Monthly data

volume
Contact MorpheusSupport@orange.ch if you have questions about this
metric.

Status

Status : Proposed

Justification : Packet Core KPI Useful for growth analysys and trends observation in MCO Packet
Networks

Ownership : denis.grosjean@orange-ftgroup.com Denis Gros-Jean + 33 1 57 36 17 27

Definition

Definition : Amount of Uplink Bytes and Downlink Bytes sent in MCO Network for given month.

Frequency : Monthly

Units : Megabits

Data Source : SGSNs or GGSNs; alternatively signalling probes

Calculation Rule : Sum of Uplink and Downlink Bytes send by given type of network elements in MCO
Network (SGSNs or GGSNs). Calculated on daily basis, aggregated to Monthly level.

Morpheus code:

Vendor Formulas

NSN:

Measures could be taken from both SGSN and GGSN level.

SGSN SG6:
Sum (GTP_DATA_IN_BYTES_SENT_IN_UL
+GTP_DATA_IN_BYTES_SENT_IN_DL )
GGSN FI3:
Sum (GTPSTATINBYTES + GTPSTATOUTBYTES)

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

 13

PS6 and PS7. In both versions there are many SGSN and GGSN different
counters which could be used for such calculation - depending on MCO
needs. Some examples below:
SGSN PS6 & PS7:
Sum (GTP kbytes sent to GGSN + GTP kbytes received from GGSN)
GGSN PS6 & PS7:
Sum (Gn uplink traffic in MB + Gn downlink traffic in MB)

Ericsson:

SGSN2008B :
Sum (OutOctets.GN + InOctets.GN)

Other Information

Notes:

- For SGSN level, Measurements taken from Gn (GTP)

- for GGSN level, either from Gn (GTP) or Gi (pure user traffic, no
tunnelling)
- for NSN SGSN it is "GTP DATA IN BYTES SENT IN UL" - counter id 3002
and "GTP DATA IN BYTES SENT IN DL" - counter id 3003
- for NSN GGSN it is "Bytes in GTP Packets Sent" - GTP005 and "Bytes
in GTP Packets Received" - GTP004
- for Huawei SGSN it could be for example "GTP kbytes sent to GGSN" -
counter id 4.4.7 and "GTP kbytes received from GGSN" - counter id 4.4.9
- for Huawei GGSN it could be for example "Gn uplink traffic in
packets" - counter id 2.1.9 and "Gn downlink traffic in MB" - counter id
2.1.11
- for Ericsson these counters are pointed in the SGSN, it is
important to specify the Gn interface name

(2G/3G) GPRS Attached Success rate

Contact MorpheusSupport@orange.ch if you have questions about this
metric.

Status
 14

Status : Proposed

Justification : Packet Core KQI - presents Attach Procedures Ratio for given Packet core technology
(2G-Gb or 3G-Iu) Useful in monitoring MCO Packet Core Network quality (in light of the general
subscriber's ability to access the MCO Network) Gives an indication about the accessibility of the
network from mobility perspective Requires to define "successful rejection cause group" (reject cause
codes which are not due to Network reasons)

Ownership : Denis Gros-Jean + 33 1 57 36 17 27

Definition

Definition : Sum of Successful Attach Procedures (for given access technology: 2G or 3G) and
Rejected Attach Procedures (failed due to Subscriber reasons) divided by overall number of Attach
Request attempts

Frequency :Monthly

Units : Megabits

Data Source : SGSNs or GGSNs; alternatively signalling probes

Calculation Rule : Sum of Successful Attach Procedures (for given access technology: 2G or 3G) and
Rejected Attach Procedures (failed due to Subscriber reasons), divided by overall number of Attach
Request attempts. Achieved figure multiplied by 100 to get % results Allowed (normal) rejection cause
values are #7, #8, #13, #14, #15. For more information, see 3GPP TS 24.008 Mobile radio interface
Layer 3 specification; Core network protocols; Stage 3.

Morpheus code:

Vendor Formulas

NSN:

SGSN SG6:
Different formula for 2G and 3G. Related also to installed CD
level, here e.g. for CD6 (used by OPL):
2G:

sum( SUCC_GPRS_ATTACH
+FAIL_GPRS_ATTACH_DUE_TO_GPRS_SERVICES_NOT_ALLOWED +
FAIL_GPRS_ATTACH_DUE_TO_GPRS_SERVICES_AND_NON-
GPRS_SERVICES_NOT_ALLOWED +
FAIL_GPRS_ATTACH_DUE_TO_GPRS_SERVICES_NOT_ALLOWED_IN_THIS_PLMN +
FAIL_GPRS_ATTACH_DUE_TO_ROAMING_NOT_ALLOWED_IN_THIS_LOCATION_AREA +
 15

FAIL_GPRS_ATTACH_DUE_TO_NO_SUITABLE_CELLS_IN_LOCATION_AREA)/
sum(SUCC_GPRS_ATTACH + FAIL_GPRS_ATTACH_GEN)

3G:

sum( IU_SUCC_GPRS_ATTACH + IU_SUCC_COMBINED_ATTACH +

IU_FAIL_GPRS_ATTACH_7 + IU_FAIL_GPRS_ATTACH_8 + IU_FAIL_GPRS_ATTACH_13 +
IU_FAIL_GPRS_ATTACH_14+IU_FAIL_GPRS_ATTACH_15 +
IU_FAIL_COMB_ATTACH_7+IU_FAIL_COMB_ATTACH_8 + IU_FAIL_COMB_ATTACH_13 +
IU_FAIL_COMB_ATTACH_14 + IU_FAIL_COMB_ATTACH_15) / sum (IU_SUCC_GPRS_ATTACH)
+ IU_FAIL_GPRS_ATTACH+IU_SUCC_COMBINED_ATTACH + IU_FAIL_COMB_ATTACH_IN_PS
+

IU_SUCC_COMB_ATTACH_ONLY_IN_PS +
IU_FAIL_GPRS_ATTACH_22,+IU_FAIL_COMB_ATTACH_22)

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

PS6 and PS7. there are different formulas for 2G and 3G:
SGSN PS6 & PS7:
2G:
Exact formula to be constructed from Gb measures described
in section 6.2 of "31350368-sgsn9810 performance metrics reference-
(v800r007_02).pdf" document being a part of PS6 and PS7 documentation.
Formula should have been constructed from both normal and combined attach
measurements. "normal" rejection cause codes to be used in numerator
listed in "calculation rule" above. KPI calcullation proposal (needs to
be operationally verifed):

[ 6.2.2 Gb mode GPRS attach accept + 6.2.14 Gb mode combined attach accept + 6.2.4 Gb mode
GPRS attach reject(GPRS not allowed in PLMN) + 6.2.5 Gb mode GPRS attach reject(No suitable
Cells in LA) + 6.2.7 Gb mode attach reject(roaming not allowed in LA) + 6.2.9 Gb mode attach
reject(GPRS service not allowed) + 6.2.16 Gb mode combined attach reject(GPRS not allowed in
PLMN) + 6.2.17 Gb mode combined attach reject(No suitable Cells in LA) + 6.2.19 Gb mode
combined attach reject(roaming not allowed in LA) + 6.2.21 Gb mode combined attach
reject(GPRS service not allowed) ] / ( 6.2.1 Gb mode GPRS attach request + 6.2.13 Gb mode
combined attach request )

3G:
 16

Exact formula to be constructed from Iu measures described in section 7.2

of "31350368-sgsn9810 performance metrics reference-(v800r007_02).pdf"
document being a part of PS6 and PS7 documentation. Formula should have
been constructed from both normal and combined attach measurements.
"normal" rejection cause codes to be used in numerator listed in
"calculation rule" above. KPI calcullation proposal (needs to be
operationally verifed):

[ 7.2.2 Iu mode GPRS attach success + 7.2.13 Iu mode combined attach accept + 7.2.6 Iu mode
attach reject(GPRS service not allowed) + 7.2.10 Iu mode GPRS attach reject(Gprs not allowed in
PLMN) + 7.2.11 Iu mode GPRS attach reject(no suitable cell in LA) + 7.2.17 Iu mode combined
attach reject(GPRS service not allowed) + 7.2.21 Iu mode combined attach reject(Gprs not allowed
in PLMN) + 7.2.22 Iu mode combined attach reject(no suitable cell in LA) ] / ( 7.2.1 Iu mode GPRS
attach request + 7.2.12 Iu mode combined attach request )

Ericsson:

For 2G:
100 * (SuccGprsAttach.G + UnsuccAttachCC7.G + UnsuccAttachCC8.G +
UnsuccAttachCC13.G + UnsuccAttachCC14.G + UnsuccAttachCC15.G) /
(AttGprsAttach.G)
For 3G:
100 * (SuccGprsAttach.U + UnsuccAttachCC7.U + UnsuccAttachCC8.U +
UnsuccAttachCC13.U + UnsuccAttachCC14.U + UnsuccAttachCC15.U) /
(AttGprsAttach.U)

Other Information

Notes:

- It is recommended to calculate this KPI separately fro 2G and 3G

access types
- Combined Attach Procedures are also part of this calculation

(2G/3G) PDP Context Activation Success

Rate
Contact MorpheusSupport@orange.ch if you have questions about this
metric.
 17

Status

Status : Proposed

Justification : Packet Core KQI - presents PDP Context Activation Procedures Ratio (if possible to
distinguish: for given Packet Core technology, 2G-Gb or 3G-Iu) Useful in monitoring MCO Packet Core
Network quality (in light of the general subscriber's ability to access the Packet Core Services) Gives
an indication on the accessibility of the network in relation to establishment of data sessions Requires
to define "successful rejection cause group" (reject cause codes which are not due to Network reasons
but to Subscriber errors or attempts to not provisioned service)

Ownership : Denis Gros-Jean denis.grosjean@orange-ftgroup.com + 33 1 57 36 17 27

Definition

Definition : Sum of Successful PDP_Context Activation Procedures (for given access technology: 2G
or 3G) and Rejected PDP_Context Activation Procedures (failed due to Subscriber reasons or lack of
provisioned service) divided by overall number of PDP_Context Activation Request attempts

Frequency : Monthly

Units : %

Data Source : SGSN Measurements; alternatively signalling probes; alternatively GGSN

Measurements

Calculation Rule : Sum of Successful PDP_Context Activation Procedures (for given access
technology: 2G or 3G) and Rejected PDP_Context Activation Procedures (failed due to Subscriber
reasons or lack of provisioned service) divided by overall number of PDP_Context Activation Request
attempts. Multiplied by 100 to get % values Allowed (normal) rejection cause values are: #27, #28, #29,
#32, #33,. For more information, see 3GPP TS 24.008 Mobile radio interface Layer 3 specification;
Core network protocols; Stage 3.

Morpheus code:

Vendor Formulas

NSN:

KPI calculated on SGSN level. Could be also calculated on GGSN level

for comparison, hovewer SGSN is wider source of information since
verifies also subscriber subscription in HLR.
SGSN SG6:
Different formula for 2G and 3G. Here, e.g. for CD6 (used by
OPL):
2G:
 18

Sum(SUCC_MO_PDP_CONTEXT_ACT +
FAIL_MO_PDP_ACT_DUE_TO_AUTHENTICATION_FAILED

+ FAIL_MO_PDP_ACT_DUE_TO_MISSING_OR_UNKNOWN_APN +
FAIL_MO_PDP_ACT_DUE_TO_UNKNOWN_PDP_ADDRESS_OR_PDP_TYPE
+ FAIL_MO_PDP_ACT_DUE_TO_SERVICE_OPTION_NOT_SUPPORTED +
FAIL_MO_PDP_ACT_DUE_TO_REQUESTED_SERVICE_OPTION_NOT_SUBSCRIBED +
MO_SEC_PDP_ACTIVATION_SUCC +
FAIL_MO_SECONDARY_PDP_ACT_DUE_TO_SERVICE_OPTION_NOT_SUPPORTED +
FAIL_MO_SECONDARY_PDP_ACT_DUE_TO_REQUESTED_SERVICE_OPTION_NOT_SUBSCRIBED
+ FAIL_MO_SECONDARY_PDP_ACT_DUE_TO_UNKNOWN_PDP_CONTEXT) / sum
(MO_SEC_PDP_ACTIVATION_SUCC + SUCC_MO_PDP_CONTEXT_ACT +
FAIL_MO_PDP_CONT_ACT_GEN + FAIL_MO_SEC_PDP_CONT_ACT_GEN)

3G:

Sum (IU_SUCC_MO_PDP_CON_ACT + IU_MO_SEC_PDP_ACTIVATION_SUCC +

IU_FAIL_MO_PDP_ACT_27 + IU_FAIL_MO_PDP_ACT_28 + IU_FAIL_MO_PDP_ACT_29 +
IU_FAIL_MO_PDP_ACT_32 + IU_FAIL_MO_PDP_ACT_33 + IU_FAIL_SEC_MO_PDP_ACT_32 +
IU_FAIL_SEC_MO_PDP_ACT_33) / Sum (IU_FAIL_MO_PDP_CON_ACT +
IU_MO_SEC_PDP_ACT_FAILED + IU_SUCC_MO_PDP_CON_ACT +
IU_MO_SEC_PDP_ACTIVATION_SUCC)

Huawei:

For Huawei there are two SW releases currently used by Affiliates -

PS6 and PS7. there are different formulas for 2G and 3G:
SGSN PS6 & PS7:
2G:
Exact formula to be constructed from Gb measures described
in section 8.1 of "00413616-Performance Metrics
Reference(V800R009_04).pdf" document being a part of PS6 and PS7
documentation. Formula should have been constructed from both primary and
secondary PDP context activations. "normal" rejection cause codes to be
used in numerator listed in "calculation rule" above. KPI calculation
proposal (needs to be operationally verifed):

[8.1.2 Gb mode MS init PDP context act success + 8.1.12 Gb mode PDP context act fail(missing or
unknown APN) + 8.1.13 Gb mode PDP context act fail(unknown PDP addr or PDP type) + 8.1.14
Gb mode PDP context act fail(user authentication fail) + 8.1.15 Gb mode PDP context act
fail(service unsupported) + 8.1.16 Gb mode PDP context act fail(service unsubscribed) ] / 8.1.1 Gb
mode MS init PDP context act
 19

3G:
Exact formula to be constructed from Iu measures described
in section 9.1 of "00413616-Performance Metrics
Reference(V800R009_04).pdf" document being a part of PS6 and PS7
documentation. Formula should have been constructed from both both
primary and secondary PDP context activations. "normal" rejection cause
codes to be used in numerator listed in "calculation rule" above. KPI
calcullation proposal (needs to be operationally verifed):

[9.1.2 Iu mode MS init PDP context act success + 9.1.14 Iu mode MS init PDP context sec act
success + 9.1.16 Iu mode PDP context act fail(missing or unknown APN) + 9.1.17 Iu mode PDP
context act fail(unknown PDP addr or type) + 9.1.18 Iu mode PDP context act fail(user
authentication fail) + 9.1.19 Iu mode PDP context act fail(service not supported) + 9.1.20 Iu mode
PDP context act fail(service unsubscribed) ] / 9.1.1 Iu mode MS init PDP context act

Ericsson:

SGSN2008B
2G :
100 * (SuccActPdpContext.G + UnsuccActPdpContextCC27_28.G +
UnsuccActPdpContextCC29.G + UnsuccActPdpContextCC32_33.G) /
AttActPdpContext.G
3G :
100 * (SuccActPdpContext.U + UnsuccActPdpContextCC27_28.U +
UnsuccActPdpContextCC29.U + UnsuccActPdpContextCC32_33.U) /
AttActPdpContext.U

Other Information

Notes:

- It is recommended to calculate this KPI separately fro 2G and 3G access types - Secondary PDP
contexts are also part of this calculation