32.406 pm core network (cn) packet switched (ps) domain.doc

3GPP TS 32.406

3GPP TS 32.406 V11.3.0 (2012-03)Technical Specification

3rd Generation Partnership Project;

Technical Specification Group Services and System Aspects;Telecommunication management;Performance Management (PM);Performance measurements;Core Network (CN) Packet Switched (PS) domain

(Release 11)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.

Keywords

GSM, UMTS, management, performance3GPP

Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis

Valbonne - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet

http://www.3gpp.org

Copyright Notification

No part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.

2012, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).

All rights reserved.

UMTS is a Trade Mark of ETSI registered for the benefit of its members

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners

GSM and the GSM logo are registered and owned by the GSM Association

Contents

10Foreword

Introduction101Scope122References123Measurement family and abbreviations133.1Measurement family133.2Abbreviations144Measurements related to the SGSN164.1Mobility Management164.1.1GPRS attach procedures164.1.1.1Attempted GPRS attach procedures164.1.1.2Successful GPRS attach procedures164.1.1.3Failed GPRS attach procedures174.1.1.4Aborted GPRS attach procedures174.1.2Intra-SGSN Routing Area update procedures174.1.2.1Attempted intra-SGSN Routing Area update procedures174.1.2.2Successful intra-SGSN Routing Area update procedures184.1.2.3Failed intra-SGSN Routing Area update procedures184.1.3GPRS detach procedures initiated by MS194.1.3.1Attempted GPRS detach procedures initiated by MS194.1.4GPRS detach procedures initiated by SGSN194.1.4.1Attempted GPRS detach procedures initiated by SGSN194.1.4.2Successful GPRS detach procedures initiated by SGSN204.1.5Inter-SGSN Routing Area update procedures204.1.5.1Attempted inter-SGSN Routing Area update procedures204.1.5.2Successful inter-SGSN Routing Area update procedures204.1.5.3Failed inter-SGSN Routing Area update procedures214.1.6GPRS attach procedures with IMSI already attached214.1.6.1Attempted GPRS attach procedures with IMSI already attached214.1.6.2Successful GPRS attach procedures with IMSI already attached224.1.6.3Failed GPRS attach procedures with IMSI already attached224.1.6.4Aborted GPRS attach procedures with IMSI already attached234.1.7IMSI detach procedures initiated by MS234.1.7.1Attempted IMSI detach procedures initiated by MS234.1.8Combined GPRS/IMSI attach procedures244.1.8.1Attempted combined GPRS/IMSI attach procedures244.1.8.2Successful combined GPRS/IMSI attach procedures244.1.8.3Failed combined GPRS/IMSI attach procedures254.1.8.4Aborted combined GPRS/IMSI attach procedures254.1.9Combined GPRS/IMSI detach procedures initiated by MS264.1.9.1Attempted combined GPRS/IMSI detach procedures initiated by MS264.1.10Combined RA/LA intra-SGSN Routing Area update procedures264.1.10.1Attempted combined RA/LA intra-SGSN Routing Area update procedures264.1.10.2Successful combined RA/LA intra-SGSN Routing Area update procedures264.1.10.3Failed combined RA/LA intra-SGSN Routing Area update procedures274.1.11"Combined RA/LA with IMSI Attach" intra-SGSN Routing Area update procedures274.1.11.1Attempted "combined RA/LA with IMSI Attach" intra-SGSN Routing Area update procedures274.1.11.2Failed "combined RA/LA with IMSI Attach" intra-SGSN Routing Area update procedures284.1.12Combined RA/LA inter-SGSN Routing Area update procedures284.1.12.1Attempted combined RA/LA inter-SGSN Routing Area update procedures284.1.12.2Successful combined RA/LA inter-SGSN Routing Area update procedures294.1.12.3Failed combined RA/LA inter-SGSN Routing Area update procedures294.1.13"Combined RA/LA with IMSI Attach" inter-SGSN Routing Area update procedures304.1.13.1Attempted "combined RA/LA with IMSI Attach" inter-SGSN Routing Area update procedures304.1.13.2Failed "combined RA/LA with IMSI Attach" inter-SGSN Routing Area update procedures304.1.14Number of received invalid P-TMSI's during detach314.1.15GSM PS paging procedures314.1.15.1Attempted GSM PS paging procedures314.1.15.2Successful GSM PS paging procedures314.1.15.3Failed GSM PS paging procedures324.1.16UMTS PS paging procedures324.1.16.1Attempted UMTS PS paging procedures324.1.16.2Successful UMTS PS paging procedures324.1.16.3Failed UMTS PS paging procedures334.1.17PS paging procedures with unknown access type334.1.17.1Attempted PS paging procedures with unknown access type334.1.18Number of PS paging message sends from 2G-SGSN to the MS334.1.19Number of PS paging message sends from 3G-SGSN to the MS344.1.20GSM subscribers state344.1.20.1Subscribers in STANDBY state344.1.20.1.1Number of subscribers in STANDBY state344.1.20.1.2Mean number of subscribers in STANDBY state344.1.20.1.3Max number of subscribers in STANDBY state344.1.20.2Subscribers in READY state354.1.20.2.1Number of subscribers in READY state354.1.20.2.2Mean number of subscribers in READY state354.1.20.2.3Max number of subscribers in READY state354.1.21UMTS subscribers state364.1.21.1Subscribers in PMM-IDLE state364.1.21.1.1Number of subscribers in PMM-IDLE state364.1.21.1.2Mean number of subscribers in PMM-IDLE state364.1.21.1.3Max number of subscribers in PMM-IDLE state364.1.21.2Subscribers in PMM-CONNECTED state374.1.21.2.1Number of subscribers in PMM-CONNECTED state374.1.21.2.2Mean number of subscribers in PMM-CONNECTED state374.1.21.2.3Max number of subscribers in PMM-CONNECTED state374.1.22Attached subscribers374.1.22.1Number of attached subscribers374.1.22.2Mean number of attached subscribers384.1.22.3Max number of attached subscribers384.1.23Home subscribers394.1.23.1Number of home subscribers394.1.23.2Mean number of home subscribers394.1.23.3Max number of home subscribers404.1.24Visiting national subscribers404.1.24.1Number of visiting national subscribers404.1.24.2Mean number of visiting national subscribers404.1.24.3Max number of visiting national subscribers414.1.25Visiting foreign subscribers414.1.25.1Number of visiting foreign subscribers414.1.25.2Mean number of visiting foreign subscribers424.1.25.3Max number of visiting foreign subscribers424.1.26Void434.1.27Void434.1.28Void434.1.29Void434.1.30CAMEL subscribers434.1.30.1Number of CAMEL subscribers434.1.30.2Mean Number of CAMEL subscribers434.1.30.3Max number of CAMEL subscribers444.1.31Void444.1.32InsertSubscriberData requests received from a HLR during GPRS Update Location procedure444.1.32.1Attempted InsertSubscriberData requests received from a HLR during GPRS Update Location procedure444.1.33GPRS Update Locations sent to the HLR444.1.33.1Attempted GPRS Update Locations sent to the HLR444.1.33.2Successful GPRS Update Locations returned from the HLR454.1.34CancelLocation requests received from an HLR-operator, in case of a HLR-initiated Detach454.1.34.1Attempted CancelLocation requests received from an HLR-operator, in case of a HLR-initiated Detach454.1.35CancelLocation requests received from a HLR due to a SGSN-change (previous SGSN)454.1.35.1Attempted CancelLocation requests received from a HLR due to a SGSN-change (previous SGSN)454.1.36Reset requests received from a HLR due to an HLR restart, indicating that a failure occurred464.1.36.1Attempted Reset requests received from a HLR due to an HLR restart, indicating that a failure occurred464.1.37Periodic Routing Area update procedures464.1.37.1Attempted periodic Routing Area update procedures464.1.37.2Successful periodic Routing Area update procedures464.1.37.3Failed Periodic Routing Area update procedures474.1.38Number of implicit detach procedure474.2Subscriber Management484.2.1Insert Subscriber Data requests received from a HLR due to an HLR-operator intervention484.2.1.1Attempted Insert Subscriber Data requests received from a HLR due to an HLR-operator intervention484.2.2Delete Subscriber Data requests received from a HLR due to an HLR-operator intervention484.2.2.1Attempted Delete Subscriber Data requests received from a HLR due to an HLR-operator intervention484.3SRNS Relocation494.3.1Intra 3G-SGSN SRNS Relocations494.3.1.1Attempted intra 3G-SGSN SRNS Relocations494.3.1.2Successful intra 3G-SGSN SRNS Relocations494.3.1.3Failed intra 3G-SGSN SRNS Relocations, due to internal reasons494.3.1.4Failed intra 3G-SGSN SRNS Relocations, due to external reasons504.3.2Inter 3G-SGSN SRNS Relocations504.3.2.1Attempted inter 3G-SGSN SRNS Relocations, counted in the old 3GSGSN504.3.2.2Successful inter 3G-SGSN SRNS Relocations, counted in the old 3GSGSN504.3.2.3Failed inter 3G-SGSN SRNS Relocations, due to internal reasons, counted in the old 3GSGSN514.3.2.4Failed inter 3G-SGSN SRNS Relocations, due to external reasons, counted in the old 3GSGSN514.3.3Inter 3G-SGSN SRNS Relocations, counted in the new 3G-SGSN514.3.3.1Attempted inter 3G-SGSN SRNS Relocations, counted in the new 3G-SGSN514.3.3.2Successful Inter 3G-SGSN SRNS Relocations, counted in the new 3G-SGSN524.4Security524.4.1P-TMSI reallocation procedures524.4.1.1Attempted P-TMSI reallocation procedures524.4.1.2Successful P-TMSI reallocation procedures524.4.2Identity Request procedures initiated by this SGSN534.4.2.1Attempted Identity Request procedures initiated by this SGSN534.4.2.2Successful completed Identity Request procedures initiated by this SGSN534.4.3Identification information requests sent to a partner (previous) SGSN for subscribers registering afresh in this SGSN544.4.3.1Attempted identification information requests sent to a partner (previous) SGSN for subscribers registering afresh in this SGSN544.4.3.2Successful replied identification information requests that were sent to a partner (previous) SGSN544.4.4Attempted Identity Requests sent to the MS554.4.4.1Attempted Identity Requests sent to the MS554.4.4.2Successful replied Identity Requests from the MS554.4.5Authentication procedures that are started within this SGSN area for a subscriber using a SIM554.4.5.1Attempted authentication procedures that are started within this SGSN area for a subscriber using a SIM554.4.5.2Successful authentication procedures within this SGSN area, for a subscriber using a SIM564.4.6Authentication procedures that are started within this SGSN area for a subscriber using a USIM564.4.6.1Attempted authentication procedures that are started within this SGSN area for a subscriber using a USIM564.4.6.2Successful authentication procedures within this SGSN area, for a subscriber using a USIM574.4.6.3Received ciphering and Authentication failures within this SGSN area574.4.7Identification information requests that were received from a partner (new) SGSN for subscribers de-registering from this SGSN584.4.7.1Attempted identification information requests that were received from a partner (new) SGSN for subscribers de-registering from this SGSN584.4.7.2Successfully replied identification information requests that were received from a partner (new) SGSN584.4.8SGSN context requests sent to a partner (previous) SGSN for subscribers registering afresh in this SGSN594.4.8.1Attempted SGSN context requests sent to a partner (previous) SGSN for subscribers registering afresh in this SGSN594.4.8.2Successfully replied SGSN context requests that were sent to a partner (previous) SGSN594.4.9SGSN context requests received from a partner (new) SGSN for a subscriber de-registering from this SGSN604.4.9.1Attempted SGSN context requests received from a partner (new) SGSN for a subscriber de-registering from this SGSN604.4.9.2Successfully replied SGSN context requests received from a partner (new) SGSN604.4.10Number of P-TMSI - IMSI correlation failures (User Identity Confidentiality (TS 23.060 [2]))604.4.11Security mode control procedures started by the SGSN614.4.11.1Attempted security mode control procedures started by the SGSN614.4.11.2Successful security mode procedures614.4.12Ciphering procedures started by the SGSN614.4.12.1Attempted GSM ciphering procedures started by the SGSN614.4.12.2Successful GSM ciphering procedures started by the SGSN624.4.12.3Attempted UMTS ciphering procedures started by the SGSN624.4.12.4Successful UMTS ciphering procedures started by the SGSN624.4.13MAP V1 requests for authentication sets634.4.13.1Attempted MAP V1 requests for authentication sets, sent to the HLR by SGSN634.4.13.2Successful MAP V1 requests for authentication sets that were sent to the HLR634.4.13.3Number of empty responses to the MAP V1 request for authentication sets that were sent to the HLR634.4.14MAP V3 requests for Authentication sets644.4.14.1Attempted MAP V3 requests for Authentication sets sent to the HLR by SGSN644.4.14.2Successful MAP V3 requests for authentication sets that were sent to the HLR644.4.14.3Number of empty responses to the MAP V3 request for authentication sets that were sent to the HLR644.5Void654.6Session Management654.6.1PDP context activation procedures initiated by MS654.6.1.1Attempted PDP context activation procedures initiated by MS654.6.1.2Successful PDP context activation procedures initiated by MS654.6.1.3Failed PDP context activation procedures initiated by MS654.6.2dynamic PDP context activation procedures initiated by MS664.6.2.1Attempted dynamic PDP context activation procedures initiated by MS664.6.2.2Successful dynamic PDP context activation procedures initiated by MS664.6.3Mean number of activated PDP contexts674.6.4PDP context deactivation procedures initiated by the MS674.6.4.1Attempted PDP context deactivation procedures initiated by the MS674.6.4.2Successful PDP context deactivation procedures initiated by the MS684.6.5Number of active PDP context684.6.6Subscribers with activated PDP context684.6.6.1Number of subscribers with activated PDP context684.6.6.2Mean number of subscribers with activated PDP context694.6.6.3Max number of subscribers with activated PDP context694.6.6.4Mean number of subscribers with activated PDP context and direct tunnel704.6.6.5Max number of subscribers with activated PDP context and direct tunnel704.6.7Void704.6.8PDP context deactivation procedures initiated by the GGSN704.6.8.1Attempted PDP context deactivation procedures initiated by the GGSN704.6.8.2Successful PDP context deactivation procedures initiated by the GGSN714.6.9PDP context deactivation procedures initiated by the SGSN714.6.9.1Attempted PDP context deactivation procedures initiated by the SGSN714.6.9.2Successful PDP context deactivations initiated by the SGSN714.6.9.3Abnormal PDP context Deactivation procedures724.6.10SGSN-Initiated PDP context update procedures724.6.10.1Attempted SGSN-Initiated PDP context update procedures724.6.10.2Successful SGSN-Initiated PDP context update procedures734.6.10.3Attempted SGSN-Initiated PDP context update procedures with direct tunnel734.6.10.4Successful SGSN-Initiated PDP context update procedures with direct tunnel734.6.11GGSN-Initiated PDP context update procedures744.6.11.1Attempted GGSN-Initiated PDP context update procedures744.6.11.2Successful GGSN-Initiated PDP context update procedures744.6.12SGSN-Initiated PDP context modifications procedures754.6.12.1Attempted SGSN-Initiated PDP context modifications procedures754.6.12.2Successfully SGSN-Initiated PDP context modifications procedures754.6.13MS-Initiated PDP context modifications procedures754.6.13.1Attempted MS-Initiated PDP context modifications procedures754.6.13.2Successfully MS-Initiated PDP context modifications procedures764.6.14Secondary PDP context activation procedures764.6.14.1Attempted Secondary PDP context activation procedures764.6.14.2Successful Secondary PDP context activations774.6.15PDP context activation procedures initiated by Network774.6.15.1Attempted PDP context activation procedures initiated by Network774.6.15.2Successful PDP context activation procedures initiated by Network774.6.15.3Failed PDP context activation procedures initiated by Network784.6.16PDP Context set-up time, initiated by MS (Mean)784.6.17PDP Context set-up time, initiated by MS (Max)794.6.18PDP Context set-up time, initiated by Network (Mean)794.6.19PDP Context set-up time, initiated by Network (Max)804.6.20 Service Request related measurement804.6.20.1Attempted Service Request procedures804.6.20.2Successful Service Request procedures804.6.20.3Failed Service Request procedures814.6.21Mean number of activated PDP contexts with direct tunnel related measurements814.7CAMEL Measurements824.7.1CAMEL dialogues824.7.1.1Attempted CAMEL dialogues824.7.1.2Failed CAMEL dialogues, aborted locally by gprsSSF824.7.1.3Failed CAMEL dialogues, error or reject from gsmSCF824.8UMTS-GSM Intersystem Change834.8.1Intra SGSN inter system changes from UMTS to GSM834.8.1.1Attempted intra SGSN inter system changes from UMTS to GSM834.8.1.2Successful intra SGSN inter system changes from UMTS to GSM834.8.1.3Failed intra SGSN inter system changes UMTS to GSM RAU, due to internal reasons834.8.1.4Failed intra SGSN inter system changes UMTS to GSM RAU, due to external reasons844.8.2Intra SGSN inter system changes from GSM to UMTS844.8.2.1Attempted intra SGSN inter system changes from GSM to UMTS844.8.2.2Successful intra SGSN inter system changes from GSM to UMTS844.8.2.3Failed intra SGSN inter system changes GSM to UMTS RAU, due to internal reasons854.8.2.4Failed intra SGSN inter system changes GSM to UMTS RAU, due to external reasons854.9UMTS GTP Measurements854.9.1GTP-U Iu854.9.1.1Number of outgoing GTP data packets on the Iu interface854.9.1.2Number of incoming GTP data packets on the Iu interface864.9.1.3Number of octets of outgoing GTP data packets on the Iu interface864.9.1.4Number of octets of incoming GTP data packets on the Iu interface864.9.2GTP Gn874.9.2.1Number of outgoing GTP data packets on the Gn interface, from SGSN to GGSN874.9.2.2Number of incoming GTP data packets on the Gn interface, from GGSN to SGSN874.9.2.3Number of octets of outgoing GTP data packets on the Gn interface, from SGSN to GGSN874.9.2.4Number of octets of incoming GTP data packets on the Gn interface, from GGSN to SGSN884.9.2.5Number of outgoing GTP signalling packets on the Gn interface, from SGSN to GGSN884.9.2.6Number of incoming GTP signalling packets on the Gn interface, from GGSN to SGSN894.9.2.7Number of octets of outgoing GTP signalling packets on the Gn interface, from SGSN to GGSN894.9.2.8Number of octets of incoming GTP signalling packets on the Gn interface, from GGSN to SGSN894.9.2.9Number of outgoing GTP data packets on the Gn interface, from SGSN to SGSN904.9.2.10Number of incoming GTP data packets on the Gn interface, from SGSN to SGSN904.9.2.11Number of octets of outgoing GTP data packets on the Gn interface, from SGSN to SGSN914.9.2.12Number of octets of incoming GTP data packets on the Gn interface, from SGSN to SGSN914.9.2.13Number of outgoing GTP signalling packets on the Gn interface, from SGSN to SGSN914.9.2.14Number of incoming GTP signalling packets on the Gn interface, from SGSN to SGSN924.9.2.15Number of octets of outgoing GTP signalling packets on the Gn interface, from SGSN to SGSN924.9.2.16Number of octets of incoming GTP signalling packets on the Gn interface, from SGSN to SGSN934.10UMTS Bearer Service934.10.1UMTS Bearer Service CS time to register (Mean)934.10.2UMTS Bearer Service CS time to register (Max)934.10.3UMTS Bearer Service PS time to register (Mean)944.10.4UMTS Bearer Service PS time to register (Max)944.10.5UMTS Bearer Service time to establish Communications Management (CM) radio access connectivity (Mean)944.10.6UMTS Bearer Service time to establish Communications Management (CM) radio access connectivity (Max)954.11LLC frames954.11.1Number of LLC frames sent954.11.2Number of LLC frames received954.11.3Number of erroneous LLC frames received964.11.4Number of LLC frames retransmitted964.12SNDCP N-PDUs964.12.1Number of SNDCP N-PDUs sent964.12.2Number of SNDCP N-PDU octets sent974.12.3Number of SNDCP N-PDUs received974.12.4Number of SNDCP N-PDU octets received974.13IMEI checking procedure974.13.1Number of check IMEI requests974.13.2Number of check IMEI white list responses984.13.3Number of check IMEI grey list responses984.13.4Number of check IMEI black list responses984.13.5Number of check IMEI unknown equipment responses994.14DNS994.14.1Attempted DNS Query Procedures994.14.2Successful DNS Query Procedures1005Measurements related to the GGSN1005.1Session Management1005.1.1Session establishments1005.1.1.1Attempted session establishments1015.1.1.2Successful session establishments1025.1.1.3Failed session establishments1025.1.2Network-initiated session establishments1035.1.2.1Number of routing information requests for network-initiated session establishment attempts1035.1.2.2Number of routing information successful responses for networkinitiated session establishment attempts1045.1.2.3Attempted Network-initiated session establishments1045.1.2.3.1Attempted Network-initiated session establishments1045.1.2.3.2Failed Network-initiated session establishments - failures occurred before sending PDP context activation request to the MS1045.1.2.3.3Failed Network-initiated session establishments - failures occurred after sending PDP context activation request to the MS1055.1.3Subscribers with activated PDP context1055.1.3.1Number of subscribers with activated PDP context1055.1.3.2Mean number of subscribers with activated PDP context1065.1.3.3Max number of subscribers with activated PDP context1065.1.4Session conclusions1065.1.4.1MS & SGSN-initiated session conclusions1075.1.4.1.1Attempted MS & SGSN-initiated session conclusions1075.1.4.1.2Successful MS & SGSN-initiated session conclusions1085.1.4.2GGSN-initiated session conclusions1085.1.4.2.1Attempted GGSN-initiated session conclusions1085.1.4.2.2Successful GGSN-initiated session conclusions1085.2Per APN measurements1095.2.1Session establishments1095.2.1.1Session establishments, per APN1105.2.1.1.1Attempted session establishments, per APN1105.2.1.1.2Successfully established sessions, per APN1115.2.1.2Session establishments with dynamic PDP address allocation required, per APN1115.2.1.2.1Attempted session establishments with dynamic PDP address allocation required, per APN1115.2.1.2.2Successfully established sessions with dynamic PDP address allocation required, per APN1115.2.1.3Session establishments with user authentication required, per APN1125.2.1.3.1Attempted session establishments with user authentication required, per APN1125.2.1.3.2Failed session establishments due to user authentication failure, per APN1125.2.2Active sessions1135.2.2.1Number of simultaneous active sessions, per APN1135.2.2.2Peak number of simultaneous active sessions, per APN1135.2.2.3MS & SGSN-initiated session modifications, per APN1145.2.2.3.1Attempted MS & SGSN-initiated session modifications, per APN1145.2.2.3.2Successfully performed MS & SGSN-initiated session modifications, per APN1145.2.3Session conclusions1145.2.3.1MS-initiated session conclusions, per APN1145.2.3.1.1Attempted MS-initiated session conclusions, per APN1145.2.3.1.2Successful MS-initiated session conclusions, per APN1155.2.3.2GGSN-initiated session conclusions, per APN1155.2.3.2.1Attempted GGSN-initiated session conclusions, per APN1155.2.3.2.2Successful GGSN-initiated session conclusions, per APN1155.3GTP measurements1165.3.1Number of incoming GTP data packets on the Gn interface1165.3.2Number of outgoing GTP data packets on the Gn interface1165.3.3Number of discarded GTP data packets1175.3.4Number of octets of incoming GTP data packets on the Gn interface1175.3.5Number of octets of outgoing GTP data packets on the Gn interface1185.3.6Number of incoming GTP signalling packets on the Gn interface1185.3.7Number of outgoing GTP signalling packets on the Gn interface1195.3.8Number of discarded GTP signalling packets1195.3.9Number of octets of incoming GTP signalling packets on the Gn interface1195.3.10Number of octets of outgoing GTP signalling packets on the Gn interface1205.3.11Number of GTP tunnels on the Gn interface1205.3.12Number of GTP tunnels created on the Gn interface1215.4GTP' measurements1215.4.1Attempted CDR information transfers1225.4.2Successful CDR information transfers1225.4.3Failed CDR information transfers1235.5IP measurements1235.5.1Number of incoming IP data packets on the Gi interface1245.5.2Number of outgoing IP data packets on the Gi interface1255.5.3Number of IP data packets discarded due to node congestion1255.5.4Number of octets of incoming IP data packets on the Gi interface1255.5.5Number of octets of outgoing IP data packets on the Gi interface1265.6AAA Authentication measurements1265.6.1Attempted Authentication Procedures, per APN1275.6.2Successful Authentication Procedures, per APN127Annex A (informative):Use cases for performance measurements128A.1Use case of implicit detach related measurements128A.2Use case of service request related measurements128A.3Use case of Mean number of activated PDP contexts with direct tunnel related measurements128A.4Use case of direct tunnel related measurements128Annex B (informative):Change history129

Foreword

This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

xthe first digit:

1presented to TSG for information;

2presented to TSG for approval;

3or greater indicates TSG approved document under change control.

ythe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.

zthe third digit is incremented when editorial only changes have been incorporated in the document.

Introduction

The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:

32.401Performance Management (PM); Concept and requirements

52.402Performance Management (PM); Performance measurements GSM

32.404Performance Management (PM); Performance measurements - Definitions and template

32.405Performance Management (PM); Performance measurements Universal Terrestrial Radio Access Network (UTRAN)

32.406Performance Management (PM); Performance measurements Core Network (CN) Packet Switched (PS) domain32.407Performance Management (PM); Performance measurements Core Network (CN) Circuit Switched (CS) domain32.408Performance Management (PM); Performance measurements Teleservice

32.409Performance Management (PM); Performance measurements IP Multimedia Subsystem (IMS)

The present document is part of a set of specifications, which describe the requirements and information model necessary for the standardised Operation, Administration and Maintenance (OA&M) of a multi-vendor 3G-system.

During the lifetime of a 3G network, its logical and physical configuration will undergo changes of varying degrees and frequencies in order to optimise the utilisation of the network resources. These changes will be executed through network configuration management activities and/or network engineering, see TS32.600 [3].

Many of the activities involved in the daily operation and future network planning of a 3G network require data on which to base decisions. This data refers to the load carried by the network and the grade of service offered. In order to produce this data performance measurements are executed in the NEs, which comprise the network. The data can then be transferred to an external system, e.g. an Operations System (OS) in TMN terminology, for further evaluation. The purpose of the present document is to describe the mechanisms involved in the collection of the data and the definition of the data itself.

Annex B of TS 32.404 helps in the definition of new performance measurements that can be submitted to 3GPP for potential adoption and inclusion in the present document. Annex B of TS 32.404 discusses a top-down performance measurement definition methodology that focuses on how the end-user of performance measurements can use the measurements.1Scope

The present document describes the measurements for UMTS and combined UMTS/GSM.

TS 32.401 [1] describes Performance Management concepts and requirements.

The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.

Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to manufacturer's documentation.

Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.

The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.

The structure of the present document is as follows:

-Header 1: Network Element (e.g. RNC related measurements);

-Header 2: Measurement function (e.g. soft handover measurements);

-Header 3: Measurements.

2References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication and/or edition number or version number) or nonspecific.

For a specific reference, subsequent revisions do not apply.

For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements".[2]3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".[3]3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".

[4]3GPP TS 29.002: "Mobile Application Part (MAP) specification".[5]3GPPTS25.413: "UTRAN Iu Interface RANAP signalling".

[6]3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".[7]Void.[8]3GPPTS23.107: "Quality of Service (QoS) concept and architecture".

[9]3GPP TS 23.003: "Numbering, Addressing and Identification".[10]3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".[11]3GPP TS 44.064: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification".[12]3GPP TS 44.065: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP)".[13]IETF RFC 1034: "DOMAIN NAMES - CONCEPTS AND FACILITIES".[14]IETF RFC 1035: "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION".[15]3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage3".

[16]GSM 08.18: "Digital cellular telecommunication system (Phase2); General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)".

[17]IETF RFC 2903: "Generic AAA Architecture".[18]IETF RFC 2138: "Remote Authentication Dial In User Service (RADIUS) ".

3Measurement family and abbreviations

3.1Measurement familyThe measurement names defined in the present document are all beginning with a prefix containing the measurement family name (e.g. MM.AttGprsAttach). This family name identifies all measurements which relate to a given functionality and it may be used for measurement administration (see TS 32.401 [1]).

The list of families currently used in the present document is as follows:

-AAA (measurements related to AAA)

-CAM (measurements related to CAMEL)

-DNS (measurements related to DNS)

-GTP (measurements related to GTP)

-IMEI (measurements related to IMEI verification)

-ISYSC (measurements related to GSM/UMTS Intersystem changes)

-LLC (measurements related to Logical Link Control)

-MM (measurements related to Mobility Management)

-RELOC (measurements related to SRNS Relocation)

-RRC (measurements related to Radio Resource Control)

-SEC (measurements related to Security)

-SIG (measurements related to Signalling)

-SM (measurements related to Session Management)

-SNDCP (measurements related to Sub-Network Dependent Convergence Protocol)

-SUB (measurements related to Subscriber Management)

-UBS (measurements related to UMTS Bearer Service)

3.2Abbreviations

For the purposes of the present document, the following abbreviations apply:

3G3rd Generation

3GPP3G Partnership Project

ASN.1Abstract Syntax Notation 1

BERBasic Encoding Rules

CNCore Network

DTDDocument Type Definition

DTIDirect Tunnel IndicatorEGQMEnhanced Goal, Question, Metric

EM(Network) Element Manager

FTAMFile Transfer Access and Management

FTPFile Transfer Protocol

GQM

Goal, Question, Metric

IEEEInstitute of Electrical and Electronics EngineersItfInterface

ITU-TInternational Telecommunication Union - Telecommunications Standardisation Sector

MSCMobile services Switching Centre

NENetwork Element

NMNetwork Manager

OA&MOperation, Administration and Maintenance

OSOperations System (EM, NM)

OSIOpen Systems Interconnection

PMPerformance Management

QoSQuality of Service

RNCRadio Network Controller

TFTPTrivial FTP

UMTSUniversal Mobile Telecommunications System

UTRANUniversal Terrestrial Radio Access Network

You can find below a list of abbreviations used within the measurement types for field E of the measurement template (see subclause 3.3).

AssnAssign(ment,ed)

AttAttempt(s,ed)

AuthAuthentication

BgrdBackground

CallCall

ChgChange

ConnConnection

CombiCombined

CSCircuit switched

CtrlControlled

ConvConversational

DelDeletion

DropDrop(ped)

EstabEstablish (ed,ment)

FailFail(ed, ure)

FDDFrequency Division DuplexHOHandover

IncIncoming

IntactInteractive

InterInter

IntraIntra

InvolInvolve(d)

MaxMaximum

MMMobility Management

NatNational

NetwNetwork

NodeBNodeB

OctOctet(s)

OutOutgoing

PktPacket(s)

PrepPreparation

ProcProcedure

PSPacket switched

RATRadio Access Technology

ReEstabRe-establish (ed,ment)

RelReleased

RelocRelocation

ReqRequest(s,ed)

ResResource

RLRadio Link

RNCRNC

RRCRadio Resource Control

RTWPReceived Total Wideband Power

SetupSetup

SGSNSGSN

SigSignalling

StrmStreaming

SubSubscriber

SuccSuccess(es,ful)

TCPTransmitted Carrier Power

UEUser Equipment

UTRANUTRAN

4Measurements related to the SGSN

4.1Mobility Management

4.1.1GPRS attach procedures

The four measurements defined in the clause 4.1.1 are subject to the "3 out of 4 approach".

NOTE:Number of Attempted GPRS attach procedures = Number of Successful GPRS attach procedures + Total Number of Failed GPRS attach procedures + Aborted GPRS attach procedures.

4.1.1.1Attempted GPRS attach procedures

a) This measurement provides the number of attempted GPRS attach procedures initiated within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of "ATTACH REQUEST" message with "Attach type" information element indicating "GPRS attach" from the MS (TS 24.008 [15]).

d) A single integer value per measurement type defined in e).

e) MM.AttGprsAttach:

-MM.AttGprsAttachCombined (don't care);

-MM.AttGprsAttach.GGSM;

-MM.AttGprsAttach.UUMTS.

f) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.

g) Valid for packet switching.

h) GSM/UMTS.

4.1.1.2Successful GPRS attach procedures

a) This measurement provides the number of successfully performed GPRS attach procedures within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Transmission of a "ATTACH ACCEPT" message to the MS, in response to a "ATTACH REQUEST" message with the "Attach type" information element indicating "GPRS attach". If the "ATTACH ACCEPT" message is caused by a retransmission, this will not cause the counter to be increased. (TS 24.008 [15]).


e) MM.SuccGprsAttach:

-MM.SuccGprsAttachCombined (don't care);

-MM.SuccGprsAttach.GGSM;

-MM.SuccGprsAttach.UUMTS.



h) GSM/UMTS.

4.1.1.3Failed GPRS attach procedures

a) This measurement provides the number of failed GPRS attach procedures. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CCc) Transmission by the SGSN of the ATTACH REJECT message to the MS, in response to a "ATTACH REQUEST" message with the "Attach type" information element indicating "GPRS attach", the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS24.008[15].The sum of all supported per cause measurements shall be equal to the total number of failed GPRS attach procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.e) MM. FailedGprsAttach.Cause:-MM. FailedGprsAttach.CauseCombined (don't care);

-MM. FailedGprsAttach.Cause.GGSM;

-MM. FailedGprsAttach.Cause.UUMTS;

where Cause identifies the reject cause.f) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.g) Valid for packet switchingh) GSM/UMTS

4.1.1.4Aborted GPRS attach procedures

a) This measurement provides the number of aborted GPRS attach procedures. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CCc) Abortion of a GPRS attach procedure, or a "ATTACH REQUEST" message with "Attach type" information element indicating "GPRS attach" would not be treated (TS 24.008 [15]).d) A single integer value per measurement type defined in e).e) MM.AbortedGprsAttach:

-MM. AbortedGprsAttachCombined (don't care);

-MM. AbortedGprsAttach.GGSM;

-MM. AbortedGprsAttach.UUMTS.

f) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.g) Valid for packet switchingh) GSM/UMTS4.1.2Intra-SGSN Routing Area update procedures4.1.2.1Attempted intra-SGSN Routing Area update procedures

a) This measurement provides the number of attempted intra-SGSN Routing Area Update procedures initiated within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of a "ROUTING AREA UPDATE REQUEST" message from the MS, where the old RA and the new RA are served by this SGSN (TS 24.008 [15]).


e) MM.AttIntraSgsnRaUpdate:

-MM.AttIntraSgsnRaUpdateCombined (don't care);

-MM.AttIntraSgsnRaUpdate.GGSM;

-MM.AttIntraSgsnRaUpdate.UUMTS.



h) GSM/UMTS.

4.1.2.2Successful intra-SGSN Routing Area update procedures

a) This measurement provides the number of successfully performed intra-SGSN Routing Area Update procedures initiated in this SGSN.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Transmission of "ROUTING AREA UPDATE ACCEPT" message to the MS (TS 24.008 [15]).

d) A single integer value.

e) MM.SuccIntraSgsnRaUpdate:

-MM.SuccIntraSgsnRaUpdateCombined (don't care);

-MM.SuccIntraSgsnRaUpdate.GGSM;

-MM.SuccIntraSgsnRaUpdate.UUMTS.



h) GSM/UMTS.

4.1.2.3Failed intra-SGSN Routing Area update procedures

a) This measurement provides the number of failed GPRS intra-SGSN Routing Area Update procedures initiated in this SGSN. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CCc) Transmission by the SGSN of the ROUTING AREA UPDATE REJECT message to the MS, in response to a " ROUTING AREA UPDATE REQUEST" (Intra-Sgsn) message, the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS24.008[15].The sum of all supported per cause measurements shall be equal to the total number of failed GPRS routing area update procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.e) MM. FailIntraSgsnRaUpdate.Cause:f) -MM. FailIntraSgsnRaUpdate.CauseCombined (don't care);

g) -MM. FailIntraSgsnRaUpdate.Cause.GGSM;

h) -MM. FailIntraSgsnRaUpdate.Cause.UUMTS;

i) where Cause identifies the reject cause.j) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.

k) Valid for packet switching.

l) GSM/UMTS.

4.1.3GPRS detach procedures initiated by MS4.1.3.1Attempted GPRS detach procedures initiated by MS

a) This measurement provides the number of MS initiated GPRS detach procedures within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of a "DETACH REQUEST" message from the MS indicating a GPRS detach (TS 24.008 [15]).


e) MM.AttGprsDetachMs:

-MM.AttGprsDetachMsCombined (don't care);

-MM.AttGprsDetachMs.GGSM;

-MM.AttGprsDetachMs.UUMTS.



h) GSM/UMTS.

4.1.4GPRS detach procedures initiated by SGSN4.1.4.1Attempted GPRS detach procedures initiated by SGSN

a) This measurement provides the number of attempted GPRS detach procedures initiated by SGSN.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Transmission of a "DETACH REQUEST" message to the MS (TS 24.008 [15]).


e) MM.AttGprsDetachSgsn:

-MM.AttGprsDetachSgsnCombined (don't care);

-MM.AttGprsDetachSgsn.GGSM;

-MM.AttGprsDetachSgsn.UUMTS.



h) GSM/UMTS.

4.1.4.2Successful GPRS detach procedures initiated by SGSN

a) This measurement provides the number of successfully completed GPRS detach procedures SGSN-initiated within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of "DETACH ACCEPT" message from the MS (TS 24.008 [15]).


e) MM.SuccGprsDetachSgsn:

-MM.SuccGprsDetachSgsnCombined (don't care);

-MM.SuccGprsDetachSgsn.GGSM;

-MM.SuccGprsDetachSgsn.UUMTS.



h) GSM/UMTS

4.1.5Inter-SGSN Routing Area update procedures4.1.5.1Attempted inter-SGSN Routing Area update procedures

a) This measurement provides the number of attempted inter-SGSN Routing Area Update procedures initiated in this SGSN.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of an "ROUTING AREA UPDATE REQUEST" message from the MS where the old RA is served by another SGSNs (TS 24.008 [15]).


e) MM.AttInterSgsnRaUpdate:

-MM.AttInterSgsnRaUpdateCombined (don't care);

-MM.AttInterSgsnRaUpdate.GGSM;

-MM.AttInterSgsnRaUpdate.UUMTS.



h) GSM/UMTS.

4.1.5.2Successful inter-SGSN Routing Area update procedures

a) This measurement provides the number of successfully completed inter-SGSN Routing Area Update procedures in this SGSN.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Transmission of a "ROUTING AREA UPDATE ACCEPT" message to the MS (TS 24.008 [15]).


e) MM.SuccInterSgsnRaUpdate:

-MM.SuccInterSgsnRaUpdateCombined (don't care);

-MM.SuccInterSgsnRaUpdate.GGSM;

-MM.SuccInterSgsnRaUpdate.UUMTS.



h) GSM/UMTS.

4.1.5.3Failed inter-SGSN Routing Area update procedures

a) This measurement provides the number of failed GPRS inter-SGSN Routing Area Update procedures initiated in this SGSN. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CCc) Transmission by the SGSN of the ROUTING AREA UPDATE REJECT message to the MS, in response to a " ROUTING AREA UPDATE REQUEST" (Inter-Sgsn) message, the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS24.008[15].The sum of all supported per cause measurements shall be equal to the total number of failed GPRS routing area update procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.e) MM. FailInterSgsnRaUpdate.Cause:f) -MM. FailInterSgsnRaUpdate.CauseCombined (don't care);

g) -MM. FailInterSgsnRaUpdate.Cause.GGSM;

h) -MM. FailInterSgsnRaUpdate.Cause.UUMTS;

i) where Cause identifies the reject cause.j) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.k) Valid for packet switchingl) GSM/UMTS4.1.6GPRS attach procedures with IMSI already attached


NOTE:Number of Attempted GPRS attach procedures with IMSI already attached = Number of Successful GPRS attach procedures with IMSI already attached + Total Number of Failed GPRS attach procedures with IMSI already attached + Aborted GPRS attach procedures with IMSI already attached.

4.1.6.1Attempted GPRS attach procedures with IMSI already attached

a) This measurement provides the number of attempted GPRS attach procedures, while IMSI is already attached. The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of "ATTACH REQUEST" Message with "Attach type" information element indicating "GPRS attach while IMSI attached" from the MS (TS24.008 [15]).


e) MM.AttGprsAttachImsiAttached:

-MM.AttGprsAttachImsiAttachedCombined (don't care);

-MM.AttGprsAttachImsiAttached.GGSM;

-MM.AttGprsAttachImsiAttached.UUMTS.



h) GSM/UMTS.

4.1.6.2Successful GPRS attach procedures with IMSI already attached

a) This measurement provides the number of successfully performed GPRS attach procedures with IMSI already attached within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Transmission of a "ATTACH ACCEPT" message to the MS, in response to a "ATTACH REQUEST" message with the "Attach type" information element indicating "GPRS attach while IMSI attached". If the "ATTACH ACCEPT" message is caused by a retransmission, this will not cause the counter to be increased. (TS24.008 [15]).


e) MM.SuccGprsAttachImsiAttached:

-MM.SuccGprsAttachImsiAttachedCombined (don't care);

-MM.SuccGprsAttachImsiAttached.GGSM;

-MM.SuccGprsAttachImsiAttached.UUMTS.



h) GSM/UMTS.

4.1.6.3Failed GPRS attach procedures with IMSI already attached

a) This measurement provides the number of failed GPRS attach procedures with IMSI already attached. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CC

c) Transmission by the SGSN of the ATTACH REJECT message to the MS, in response to a "ATTACH REQUEST" message with the "Attach type" information element indicating "GPRS attach while IMSI attached", the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS 24.008 [15]. The sum of all supported per cause measurements shall be equal to the total number of failed GPRS attach procedures with IMSI already attached. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.

e) MM. FailedGprsAttachImsiAttached.Cause:-MM. FailedGprsAttachImsiAttached.CauseCombined (don't care);

-MM. FailedGprsAttachImsiAttached.Cause.GGSM;

-MM. FailedGprsAttachImsiAttached.Cause.UUMTS;

where Cause identifies the reject cause.f) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.g) Valid for packet switching.h) GSM/UMTS.4.1.6.4Aborted GPRS attach procedures with IMSI already attached

a) This measurement provides the number of aborted GPRS attach procedures with IMSI already attached. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CC.c) Abortion of a GPRS attach procedure with IMSI already attached, or a "ATTACH REQUEST" message with "Attach type" information element indicating "GPRS attach while IMSI attached" would not be treated (TS24.008 [15]).d) A single integer value per measurement type defined in e).e) MM.AbortedGprsAttachImsiAttached:

-MM. AbortedGprsAttachImsiAttachedCombined (don't care);

-MM. AbortedGprsAttachImsiAttached.GGSM;

-MM. AbortedGprsAttachImsiAttached.UUMTS.

f) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.g) Valid for packet switching.h) GSM/UMTS.4.1.7IMSI detach procedures initiated by MS4.1.7.1Attempted IMSI detach procedures initiated by MS

a) This measurement provides the number of attempted IMSI detach procedures MS-initiated within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of a "DETACH REQUEST" message from the MS, indicating a IMSI detach (TS 24.008 [15]).


e) MM.AttImsiDetachMs:

-MM.AttImsiDetachMsCombined (don't care);

-MM.AttImsiDetachMs.GGSM;

-MM.AttImsiDetachMs.UUMTS.



h) GSM/UMTS.

4.1.8Combined GPRS/IMSI attach procedures


NOTE:Number of Attempted combined GPRS/IMSI attach procedures = Number of Successful combined GPRS/IMSI attach procedures + Total Number of Failed combined GPRS/IMSI attach procedures + Aborted combined GPRS/IMSI attach procedures.

4.1.8.1Attempted combined GPRS/IMSI attach procedures

a) This measurement provides the number of attempts of combined GPRS/IMSI attach procedures initiated within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of a "ATTACH REQUEST" message with "Attach type" information element indicating "Combined GPRS/IMSI attach" from the MS (TS 24.008 [15]).

d) A single integer value per measurement type defined in e) .

e) MM.AttCombiAttach:

-MM.AttCombiAttachCombined (don't care);

-MM.AttCombiAttach.GGSM;

-MM.AttCombiAttach.UUMTS.



h) GSM/UMTS.

4.1.8.2Successful combined GPRS/IMSI attach procedures

a) This measurement provides the number of successfully performed combined GPRS/IMSI attach procedures within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Transmission of a "ATTACH ACCEPT" message to the MS, in response to a "ATTACH REQUEST" message with the "Attach type" information element indicating "Combined GPRS/IMSI attach". If the "ATTACH ACCEPT" message is caused by a retransmission, this will not cause the counter to be increased. (TS24.008 [15]).


e) MM.SuccCombiAttach:

-MM.SuccCombiAttachCombined (don't care);

-MM.SuccCombiAttach.GGSM;

-MM.SuccCombiAttach.UUMTS.



h) GSM/UMTS.

4.1.8.3Failed combined GPRS/IMSI attach procedures

a) This measurement provides the number of failed combined GPRS/IMSI attach procedures. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CC

c) Transmission by the SGSN of the ATTACH REJECT message to the MS, in response to a "ATTACH REQUEST" message with the "Attach type" information element indicating "Combined GPRS/IMSI attach", the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS 24.008 [15]. The sum of all supported per cause measurements shall be equal to the total number of failed combined GPRS/IMSI attach procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.

d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.

e) MM. FailedCombiAttach.Cause:-MM. FailedCombiAttach.CauseCombined (don't care);

-MM. FailedCombiAttach.Cause.GGSM;

-MM. FailedCombiAttach.Cause.UUMTS;

where Cause identifies the reject cause.f) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.g) Valid for packet switching.h) GSM/UMTS.4.1.8.4Aborted combined GPRS/IMSI attach procedures

a) This measurement provides the number of aborted combined GPRS/IMSI attach procedures. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CC.c) Abortion of a combined GPRS/IMSI attach procedure, or a "ATTACH REQUEST" message with "Attach type" information element indicating "Combined GPRS/IMSI attach" would not be treated (TS 24.008 [15]).d) A single integer value per measurement type defined in e).e) MM.AbortedCombiAttach:

-MM. AbortedCombiAttachCombined (don't care);

-MM. AbortedCombiAttach.GGSM;

-MM. AbortedCombiAttach.UUMTS.

f) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.g) Valid for packet switching.h) GSM/UMTS.4.1.9Combined GPRS/IMSI detach procedures initiated by MS4.1.9.1Attempted combined GPRS/IMSI detach procedures initiated by MS

a) This measurement provides the number of attempted Combined GPRS/IMSI detach procedures MS-initiated within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of "DETACH REQUEST" message from the MS, indicating a Combined GPRS/IMSI detach (TS24.008 [15]).


e) MM.AttCombiDetachMs:

-MM.AttCombiDetachMsCombined (don't care);

-MM.AttCombiDetachMs.GGSM;

-MM.AttCombiDetachMs.UUMTS.



h) GSM/UMTS.

4.1.10Combined RA/LA intra-SGSN Routing Area update procedures4.1.10.1Attempted combined RA/LA intra-SGSN Routing Area update procedures

a) This measurement provides the number of combined RA/LA updates (intra-SGSN) procedures initiated in this SGSN. These are counted as attempts.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of "Routing Area Update REQUEST" message from the MS, indicating a combined RA/LA update (TS24.008 [15]).


e) MM.AttCombiIntraSgsnRaUpdate:

-MM.AttCombiIntraSgsnRaUpdateCombined (don't care);

-MM.AttCombiIntraSgsnRaUpdate.GGSM;

-MM.AttCombiIntraSgsnRaUpdate.UUMTS.



h) GSM/UMTS.

4.1.10.2Successful combined RA/LA intra-SGSN Routing Area update procedures

a) This measurement provides the number of success-fully performed combined RA/LA updates (intra-SGSN) procedures initiated in this SGSN.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Transmission of "Routing Area Update ACCEPT" message to the MS (TS 24.008 [15]).


e) MM.SuccCombiIntraSgsnRaUpdate:

-MM.SuccCombiIntraSgsnRaUpdateCombined (don't care);

-MM.SuccCombiIntraSgsnRaUpdate.GGSM;

-MM.SuccCombiIntraSgsnRaUpdate.UUMTS.



h) GSM/UMTS.

4.1.10.3Failed combined RA/LA intra-SGSN Routing Area update procedures

a) This measurement provides the number of failed GPRS combined RA/LA intra-SGSN Routing Area Update procedures initiated in this SGSN. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CCc) Transmission by the SGSN of the ROUTING AREA UPDATE REJECT message to the MS, in response to a " ROUTING AREA UPDATE REQUEST" (combined RA/LA Intra-Sgsn) message, the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS24.008[15].The sum of all supported per cause measurements shall be equal to the total number of failed GPRS routing area update procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.e) MM. FailCombiIntraSgsnRaUpdate.Cause:f) -MM. FailedCombiIntraSgsnRaUpdate.CauseCombined (don't care);

g) -MM. FailedCombiIntraSgsnRaUpdate.Cause.GGSM;

h) -MM. FailedCombiIntraSgsnRaUpdate.Cause.UUMTS;

i) where Cause identifies the reject cause.j) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.k) Valid for packet switchingl) GSM/UMTS4.1.11"Combined RA/LA with IMSI Attach" intra-SGSN Routing Area update procedures4.1.11.1Attempted "combined RA/LA with IMSI Attach" intra-SGSN Routing Area update procedures

a) This measurement provides the number of combined RA/LA updates with IMSI attach (intra-SGSN) procedures initiated in this SGSN. These are counted as attempts.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of "Routing Area Update REQUEST" message from the MS, indicating a combined RA/LA update with IMSI attach (TS 24.008 [15]).


e) MM.AttImsiCombiIntraSgsnRAUpdate:

-MM.AttImsiCombiIntraSgsnRAUpdateCombined (don't care);

-MM.AttImsiCombiIntraSgsnRAUpdate.GGSM;

-MM.AttImsiCombiIntraSgsnRAUpdate.UUMTS.



h) GSM/UMTS.

4.1.11.2Failed "combined RA/LA with IMSI Attach" intra-SGSN Routing Area update procedures

a) This measurement provides the number of failed GPRS "combined RA/LA with IMSI Attach" intra-SGSN Routing Area Update procedures initiated in this SGSN. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CCc) Transmission by the SGSN of the ROUTING AREA UPDATE REJECT message to the MS, in response to a " ROUTING AREA UPDATE REQUEST" ("combined RA/LA with IMSI Attach" Intra-Sgsn) message, the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS24.008[15].The sum of all supported per cause measurements shall be equal to the total number of failed GPRS routing area update procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.e) MM. FailImsiCombiIntraSgsnRAUpdate.Cause:f) -MM. FailImsiCombiIntraSgsnRAUpdate.CauseCombined (don't care);

g) -MM. FailImsiCombiIntraSgsnRAUpdate.Cause.GGSM;

h) -MM. FailImsiCombiIntraSgsnRAUpdate.Cause.UUMTS;

i) where Cause identifies the reject cause.j) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.k) Valid for packet switchingl) GSM/UMTS4.1.12Combined RA/LA inter-SGSN Routing Area update procedures4.1.12.1Attempted combined RA/LA inter-SGSN Routing Area update procedures

a) This measurement provides the number of combined RA/LA updates (inter-SGSN) procedures initiated in this SGSN. These are counted as attempts.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of "Routing Area Update REQUEST" message from the MS, indicating a combined RA/LA update (TS24.008 [15]).


e) MM.AttCombiInterSgsnRaUpdate:

-MM.AttCombiInterSgsnRaUpdateCombined (don't care);

-MM.AttCombiInterSgsnRaUpdate.GGSM;

-MM.AttCombiInterSgsnRaUpdate.UUMTS.



h) GSM/UMTS.

4.1.12.2Successful combined RA/LA inter-SGSN Routing Area update procedures

a) This measurement provides the number of success-fully performed combined RA/LA updates (inter-SGSN) procedures initiated in this SGSN.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Transmission of "Routing Area Update ACCEPT" message to the MS (TS 24.008 [15]).


e) MM.SuccCombiInterSgsnRaUpdate:

-MM.SuccCombiInterSgsnRaUpdateCombined (don't care);

-MM.SuccCombiInterSgsnRaUpdate.GGSM;

-MM.SuccCombiInterSgsnRaUpdate.UUMTS.



h) GSM/UMTS.

4.1.12.3Failed combined RA/LA inter-SGSN Routing Area update procedures

a) This measurement provides the number of failed GPRS combined RA/LA inter-SGSN Routing Area Update procedures initiated in this SGSN. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CCc) Transmission by the SGSN of the ROUTING AREA UPDATE REJECT message to the MS, in response to a " ROUTING AREA UPDATE REQUEST" (combined RA/LA Inter-Sgsn) message, the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS24.008[15].The sum of all supported per cause measurements shall be equal to the total number of failed GPRS routing area update procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.e) MM. FailCombiInterSgsnRaUpdate.Cause:f) -MM. FailedCombiInterSgsnRaUpdate.CauseCombined (don't care);

g) -MM. FailedCombiInterSgsnRaUpdate.Cause.GGSM;

h) -MM. FailedCombiInterSgsnRaUpdate.Cause.UUMTS;

i) where Cause identifies the reject cause.j) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.k) Valid for packet switchingl) GSM/UMTS4.1.13"Combined RA/LA with IMSI Attach" inter-SGSN Routing Area update procedures4.1.13.1Attempted "combined RA/LA with IMSI Attach" inter-SGSN Routing Area update procedures

a) This measurement provides the number of combined RA/LA updates with IMSI attach (inter-SGSN) procedures initiated in this SGSN. These are counted as attempts:The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of "Routing Area Update REQUEST" message from the MS, indicating a combined RA/LA update with IMSI attach.E52.


e) MM.AttImsiCombiInterSgsnRAUpdate:

-MM.AttImsiCombiInterSgsnRAUpdateCombined (don't care);

-MM.AttImsiCombiInterSgsnRAUpdate.GGSM;

-MM.AttImsiCombiInterSgsnRAUpdate.UUMTS.



h) GSM/UMTS.

4.1.13.2Failed "combined RA/LA with IMSI Attach" inter-SGSN Routing Area update procedures

a) This measurement provides the number of failed GPRS "combined RA/LA with IMSI Attach" inter-SGSN Routing Area Update procedures initiated in this SGSN. The measurement is split into subcounters per the reject cause. The three measurements defined in e) are subject to the "2 out of 3 approach".

b) CCc) Transmission by the SGSN of the ROUTING AREA UPDATE REJECT message to the MS, in response to a " ROUTING AREA UPDATE REQUEST" ("combined RA/LA with IMSI Attach" Intra-Sgsn) message, the relevant measurement is incremented according to the reject cause. Possible reject causes are defined within TS24.008[15].The sum of all supported per cause measurements shall be equal to the total number of failed GPRS routing area update procedures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first.d) Each measurement (as defined in e) is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix.e) MM. FailImsiCombiInterSgsnRAUpdate.Cause:-MM. FailImsiCombiInterSgsnRAUpdate.CauseCombined (don't care);

-MM. FailImsiCombiInterSgsnRAUpdate.Cause.GGSM;

-MM. FailImsiCombiInterSgsnRAUpdate.Cause.UUMTS;

where Cause identifies the reject cause.f) RA, specified by a concatenation of the MCC, MNC, LAC and the RAC.g) Valid for packet switchingh) GSM/UMTS4.1.14Number of received invalid P-TMSI's during detach

a) This measurement provides the number of received invalid P-TMSI's during detach. The three measurement types defined in e) are subject to the "2 out of 3 approach".b) CC.

c) Receipt of an "DETACH_REQUEST" with invalid P-TMSI (TS 24.008 [15]).


e) MM.NbrPTMSIDetachFail:

-MM.NbrPTMSIDetachFailCombined (don't care);

-MM.NbrPTMSIDetachFail.GGSM;

-MM.NbrPTMSIDetachFail.UUMTS.



h) GSM/UMTS.

4.1.15GSM PS paging proceduresThe three measurement types defined in clauses 4.1.15.n are subject to the "2 out of 3 approach".

4.1.15.1Attempted GSM PS paging procedures

a) This measurement provides the number of attempted PS paging procedures initiated at the SGSN over the Gb interface. The initial paging procedures as well as the repeated paging procedures are counted.b) CC.

c) Incremented when a GSM PS paging procedure is started, i.e. at the transmission of the first BSSGP Paging Request (GSM 08.18 [16]) from the SGSN to the MS.


e) MM.AttPsPagingProcGb.



h) GSM.

4.1.15.2Successful GSM PS paging procedures

a) This measurement provides the number of successful PS paging procedures initiated at the SGSN over the Gb interface. The initial paging procedures as well as the repeated paging procedures are counted.b) CC.

c) Incremented when an uplink_trigger (any LLC frame) is received by the SGSN from the MS (over the Gb interface) as response to a GSM PS paging procedure (TS 23.060 [2]) or during intersystem change UMTS -> GSM.


e) MM.SuccPsPagingProcGb.



h) GSM.

4.1.15.3Failed GSM PS paging procedures

a) This measurement provides the number of failed PS paging procedures initiated at the SGSN over the Gb interface, i.e. PS paging procedures that time out. The initial paging procedures as well as the repeated paging procedures are counted.b) CC.

c) Incremented when a GSM PS paging procedure times out.


e) MM.FailPsPagingProcGb.



h) GSM.

4.1.16UMTS PS paging proceduresThe three measurement types defined in clauses 4.1.16.n are subject to the "2 out of 3 approach".

4.1.16.1Attempted UMTS PS paging procedures

a) This measurement provides the number of attempted PS paging procedures initiated at the SGSN over the Iu interface. The initial paging procedures as well as the repeated paging procedures are counted.b) CC.

c) Incremented when a UMTS PS paging procedure is started i.e. at the transmission of the first "Paging" message (TS25.413[5]) from the SGSN to the MS.


e) MM.AttPsPagingProcIu.



h) UMTS.

4.1.16.2Successful UMTS PS paging procedures

a) This measurement provides the number of successful PS paging procedures initiated at the SGSN over the Iu interface. The initial paging procedures as well as the repeated paging procedures are counted.b) CC.

c) Incremented when a paging_response is received by the SGSN from the MS (over the Iu interface) as response to a UMTS PS paging procedure (Receipt of "Service Request" message with Service Type = Paging Response from the MS (TS 24.008 [15])) or during intersystem change GSM -> UMTS.


e) MM.SuccPsPagingProcIu.



h) UMTS.

4.1.16.3Failed UMTS PS paging procedures

a) This measurement provides the number of failed PS paging procedures initiated at the SGSN over the Iu interface, i.e. PS paging procedures that time out. The initial paging procedures as well as the repeated paging procedures are counted.b) CC.

c) Incremented when a UMTS PS paging procedure times out.


e) MM.FailPsPagingProcIu.



h) UMTS.

4.1.17PS paging procedures with unknown access type4.1.17.1Attempted PS paging procedures with unknown access type

a) This measurement provides the number of attempted PS paging procedures initiated at the SGSN with access type unknown. In this case the paging will be done both over the Gb and the Iu interface. The initial paging procedures as well as the repeated paging procedures are counted.b) CC.

c) Incremented when a paging procedure is started for which MM doesn't know the access type i.e. at the transmission of the first BSSGP Paging Request (GSM 08.18 [16]) and/or "Paging" message (TS 25.413[5]) from the SGSN to the MS.


e) MM.AttPsPagingProcGbIu.



h) Combined.

4.1.18Number of PS paging message sends from 2G-SGSN to the MS

a) This measurement provides the Number of PS paging message sends from 2G-SGSN to the MS.

b) CC.

c) Transmission of "GMM-PAGING.req" (GSM 08.18 [16]) from the SGSN to the MS. Each paging message will be counted separately, addressed to all BSS in this certain RA.


e) MM.NbrPsPagingMesGb.



h) GSM.

4.1.19Number of PS paging message sends from 3G-SGSN to the MS

a) This measurement provides the Number of PS paging message sends from 3G-SGSN to the MS.

b) CC.

c) Transmission of "Paging" message (CN Domain Indicator = PS Domain) from the SGSN to the MS (TS25.413[5]). Each paging message will be counted separately, addressed to all RNC in this certain RA.


e) MM.NbrPsPagingMesIu.



h) UMTS.

4.1.20GSM subscribers state

4.1.20.1Subscribers in STANDBY state

4.1.20.1.1Number of subscribers in STANDBY state

a) This measurement provides the number of subscribers in STANDBY state.

b) GAUGE.

c) Incremented at transition of a subscriber registered in the SGSN into STANDBY state, decremented at transition of a subscriber registered in the SGSN out from STANDBY state.


e) MM.NbrSubStandby.

f) SgsnFunction.


h) GSM.

4.1.20.1.2Mean number of subscribers in STANDBY state

a) This measurement provides the mean number of subscribers in STANDBY state.b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of subscribers in STANDBY state and then taking the arithmetic mean.


e) MM.MeanNbrSubStandby.

f) SgsnFunction.


h) GSM.

4.1.20.1.3Max number of subscribers in STANDBY state

a) This measurement provides the maximum number of subscribers in STANDBY state.b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of subscribers in STANDBY state and then taking the maximum.


e) MM.MaxNbrSubStandby.

f) SgsnFunction.


h) GSM.

4.1.20.2Subscribers in READY state

4.1.20.2.1Number of subscribers in READY state

a) This measurement provides the number of subscribers in READY state.

b) GAUGE.

c) Incremented at transition of a subscriber registered in the SGSN into READY state, decremented at transition of a subscriber registered in the SGSN out from READY state.


e) MM.NbrSubReadyf) SgsnFunction.


h) GSM.

4.1.20.2.2Mean number of subscribers in READY state

a) This measurement provides the mean number of subscribers in READY state.b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of subscribers in READY state and then taking the arithmetic mean.


e) MM.MeanNbrSubReady.

f) SgsnFunction.


h) GSM.

4.1.20.2.3Max number of subscribers in READY state

a) This measurement provides the maximum number of subscribers in READY state.b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of subscribers in READY state and then taking the maximum.


e) MM.MaxNbrSubReady.

f) SgsnFunction.


h) GSM.

4.1.21UMTS subscribers state

4.1.21.1Subscribers in PMM-IDLE state

4.1.21.1.1Number of subscribers in PMM-IDLE state

a) This measurement provides the number of subscribers in PMM-IDLE state.

b) GAUGE.

c) Incremented at PS Signalling Connection Release (Iu Release), decremented at PS Detach or PS Signalling Connection Establish (Service Request).


e) MM.NbrSubPmmIdle.

f) SgsnFunction.


h) UMTS.

4.1.21.1.2Mean number of subscribers in PMM-IDLE state

a) This measurement provides the mean number of subscribers in PMM-IDLE state.b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of subscribers in PMM-IDLE state and then taking the arithmetic mean.


e) MM.MeanNbrSubPmmIdle.

f) SgsnFunction.


h) UMTS.

4.1.21.1.3Max number of subscribers in PMM-IDLE state

a) This measurement provides the maximum number of subscribers in PMM-IDLE state.b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of subscribers in PMM-IDLE state and then taking the maximum.


e) MM.MaxNbrSubPmmIdle.

f) SgsnFunction.


h) UMTS.

4.1.21.2Subscribers in PMM-CONNECTED state

4.1.21.2.1Number of subscribers in PMM-CONNECTED state

a) This measurement provides the number of subscribers in PMM-CONNECTED state.

b) GAUGE.

c) Decremented at PS Signalling Connection Release (Iu Release), Detach, PS Attach Reject or RAU Reject, incremented at PS Attach or PS Signalling Connection Establish (Service Request).


e) MM.NbrSubPmmConnected

f) SgsnFunction.


h) UMTS.

4.1.21.2.2Mean number of subscribers in PMM-CONNECTED state

a) This measurement provides the mean number of subscribers in PMM-CONNECTED state.b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of subscribers in PMMCONNECTED state and then taking the arithmetic mean.


e) MM.MeanNbrSubPmmConnected.

f) SgsnFunction.


h) UMTS.

4.1.21.2.3Max number of subscribers in PMM-CONNECTED state

a) This measurement provides the maximum number of subscribers in PMM-CONNECTED state.b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of subscribers in PMMCONNECTED state and then taking the maximum.


e) MM.MaxNbrSubPmmConnected.

f) SgsnFunction.


h) UMTS.

4.1.22Attached subscribers

4.1.22.1Number of attached subscribers

a) This measurement provides the number of attached subscribers within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) GAUGE.

c) Incremented when a subscriber enters the GMM_REGISTERED state in the SGSN Location Register, and decremented when a subscriber leaves the GMM_REGISTERED state.

NOTE:The GMM state machine in the SGSN Location Register is described in TS 24.008 [15], clause 4.1.3.3 (Figure 4.1c/3GPP TS 24.008 [15]: GMM main states on the network side).


e) MM.NbrActAttachedSub:

-MM.NbrActAttachedSubCombined (don't care);

-MM.NbrActAttachedSub.GGSM;

-MM.NbrActAttachedSub.UUMTS.

f) SgsnFunction RoutingArea.


h) GSM/UMTS.

4.1.22.2Mean number of attached subscribers

a) This measurement provides the mean number of attached subscribers within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of attached subscribers and then taking the arithmetic mean.


e) MM.MeanNbrAttachedSub:

-MM.MeanNbrAttachedSubCombined (don't care);

-MM.MeanNbrAttachedSub.GGSM;

-MM.MeanNbrAttachedSub.UUMTS.

f) SgsnFunction. RoutingAreag) Valid for packet switching.

h) GSM/UMTS.

4.1.22.3Max number of attached subscribers

i) This measurement provides the maximum number of attached subscribers within this SGSN area.The three measurement types defined in e) are subject to the "2 out of 3 approach".j) SI.

k) This measurement is obtained by sampling at a pre-defined interval the number of attached subscribers and then taking the maximum.

l) A single integer value per measurement type defined in e).

m) MM.MaxNbrAttachedSub:

-MM.MaxNbrAttachedSubCombined (don't care);

-MM.MaxNbrAttachedSub.GGSM;

-MM.MaxNbrAttachedSub.UUMTS.

n) SgsnFunction. RoutingAreao) Valid for packet switching.

p) GSM/UMTS.4.1.23Home subscribers

4.1.23.1Number of home subscribers

a) This measurement provides the number of GPRS home subscribers located in the SGSN location register. The GPRS MM state of this subscriber is GMM_REGISTERED or GMM_DEREGISTERED. Only GPRS subscribers that are homed in the same GPRS network are considered.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) GAUGE.

c) Incremented by one when GPRS home subscriber is successfully registered in the SGSN location registered and decremented by one when GPRS home subscriber is successfully deregistered out of the SGSN location register (TS24.008 [15]).


e) MM.NbrHomeSub:

-MM.NbrHomeSubCombined (don't care);

-MM.NbrHomeSub.GGSM;

-MM.NbrHomeSub.UUMTS.

f) SgsnFunction.


h) GSM/UMTS.

4.1.23.2Mean number of home subscribers

a) This measurement provides the mean number of GPRS home subscribers located in the SGSN location register.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of GPRS home subscribers located in the SGSN location register and then taking the arithmetic mean.


e) MM.MeanNbrHomeSub:

-MM.MeanNbrHomeSubCombined (don't care);

-MM.MeanNbrHomeSub.GGSM;

-MM.MeanNbrHomeSub.UUMTS.

f) SgsnFunction.


h) GSM/UMTS.

4.1.23.3Max number of home subscribers

a) This measurement provides the maximum number of GPRS home subscribers located in the SGSN location register.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of GPRS home subscribers located in the SGSN location register and then taking the maximum.


e) MM.MaxNbrHomeSub:

-MM.MaxNbrHomeSubCombined (don't care);

-MM.MaxNbrHomeSub.GGSM;

-MM.MaxNbrHomeSub.UUMTS.

f) SgsnFunction.


h) GSM/UMTS.

4.1.24Visiting national subscribers

4.1.24.1Number of visiting national subscribers

a) This measurement provides the number of visiting national GPRS subscribers located in the SGSN location register. The GPRS MM state of this subscriber is GMM_REGISTERED or GMM_DEREGISTERED. Only GPRS subscribers that are homed in a partner GPRS network of the same country are considered.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) GAUGE.

c) This measurement provides the number of visiting national GPRS subscribers located in the SGSN location register. The GPRS MM state of this subscriber is GMM_REGISTERED or GMM_DEREGISTERED. Only GPRS subscribers that are homed in a partner GPRS network of the same country are considered.


e) MM.NbrVisitingNatSub:

-MM.NbrVisitingNatSubCombined (don't care);

-MM.NbrVisitingNatSub.GGSM;

-MM.NbrVisitingNatSub.UUMTS.

f) SgsnFunction.


h) GSM/UMTS.

4.1.24.2Mean number of visiting national subscribers

a) This measurement provides the mean number of visiting national GPRS subscribers located in the SGSN location register.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of visiting national GPRS subscribers located in the SGSN location register and then taking the arithmetic mean.


e) MM.MeanNbrVisitingNatSub:

-MM.MeanNbrVisitingNatSubCombined (don't care);

-MM.MeanNbrVisitingNatSub.GGSM;

-MM.MeanNbrVisitingNatSub.UUMTS.

f) SgsnFunction.


h) GSM/UMTS.

4.1.24.3Max number of visiting national subscribers

a) This measurement provides the maximum number of visiting national GPRS subscribers located in the SGSN location register.The three measurement types defined in e) are subject to the "2 out of 3 approach".b) SI.

c) This measurement is obtained by sampling at a pre-defined interval the number of visiting national GPRS subscribers located in the SGSN location register and then taking the maximum.

d) A single integer value per measure

32.406 pm core network (cn) packet switched (ps) domain.doc

Documents