SJ-20150919164026-011-ZXUN iEPC (V1.15.10) Integrated Evolved Packet Core Performance Counter Reference

ZXUN iEPC
Integrated Evolved Packet Core

Performance Counter Reference
Version: V1.15.10
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: [email protected]
LEGAL INFORMATION
Copyright © 2015 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2015-10-30 First Edition
Serial Number: SJ-20150919164026-011
Publishing Date: 2015-10-30 (R1.0)
SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

Contents
Chapter 1 Introduction to the Performance Measurement ..................... 1-1
1.1 Relationship Between the Performance Counters and the System Performance ..... 1-1
1.2 Introduction to the Format of the Performance Counters ....................................... 1-2
Chapter 2 MME Measurement ................................................................... 2-1

2.1 MME ESM Measurement .................................................................................... 2-1
2.1.1 Mean Number of Dedicated Bearers in Active State.................................... 2-1
2.1.2 Max Number of Dedicated Bearers in Active State...................................... 2-2
2.1.3 Times of Dedicated Bearer Activation Requested ....................................... 2-2
2.1.4 Times of Successful Dedicated Bearer Activation ....................................... 2-3
2.1.5 Times of Failed Dedicated Bearer Activation .............................................. 2-4
2.1.6 Times of Dedicated Bearer Deactivation Requested ................................... 2-5
2.1.7 Times of Successful Dedicated Bearer Deactivation Requested .................. 2-6
2.1.8 Times of Bearer Modify Requested............................................................ 2-7
2.1.9 Times of Successful Bearer Update Requested.......................................... 2-8
2.1.10 Times of Failed Bearer Update Requested ............................................... 2-9
2.1.11 Total Time of Dedicated Bearer Activation Procedure (ms) ..................... 2-10
2.1.12 Total Time of Default Bearer Activation Procedure (ms)............................2-11
2.1.13 Times of PDN Connection Request........................................................ 2-12
2.1.14 Times of Successful PDN Connection ................................................... 2-13
2.1.15 Times of PDN Connection Failure.......................................................... 2-13
2.1.16 Times of Default Bearer Deactivation Requested .................................... 2-14
2.1.17 Times of Successful Default Bearer Deactivation .................................... 2-15
2.1.18 Times of PDN Disconnect Request ........................................................ 2-15
2.1.19 Times of Successful PDN Disconnect .................................................... 2-15
2.1.20 Times of PDN Disconnect Failure .......................................................... 2-16
2.1.21 Times of UE Requested Bearer Resource Allocation............................... 2-16
2.1.22 Times of Successful UE Requested Bearer Resource Allocation ............. 2-17
2.1.23 Times of Failed UE Requested Bearer Resource Allocation..................... 2-17
2.1.24 Times of UE Requested Bearer Resource Modification ........................... 2-17
2.1.25 Times of Successful UE Requested Bearer Resource Modification .......... 2-18
2.1.26 Times of Failed UE Requested Bearer Resource Modification ................. 2-18
2.2 MME User Measurement .................................................................................. 2-19
2.2.1 Mean Number of Subscribers in ECM-IDLE State..................................... 2-19

2.2.2 Max Number of Subscribers in ECM-IDLE State....................................... 2-19
2.2.3 Mean Number of Subscribers in ECM-CONNECTED State ....................... 2-20
2.2.4 Max Number of Subscribers in ECM-CONNECTED State ......................... 2-20
2.2.5 Mean Number of EPS Attach subscribers ................................................ 2-21
2.2.6 Max Number of EPS Attach subscribers .................................................. 2-21
2.2.7 Mean number of default bearers in active state ........................................ 2-21
2.2.8 Max number of default bearers in active state .......................................... 2-22
2.2.9 Mean number of GBR bearers in active state ........................................... 2-22
2.2.10 Max number of GBR bearers in active state ........................................... 2-23
2.2.11 Mean number of non-GBR bearers in active state ................................... 2-23
2.2.12 Max number of non-GBR bearers in active state..................................... 2-23
2.2.13 Number of MME Requested Default Bearers .......................................... 2-24
2.2.14 Number of Successful MME Requested Default Bearers......................... 2-24
2.2.15 Number of MME Requested Dedicated Bearers ..................................... 2-25
2.2.16 Number of Successful MME Requested Dedicated Bearers .................... 2-25
2.2.17 Mean Number of Member Subscribers in Closed CSG Cell ..................... 2-25
2.2.18 Max Number of Member Subscribers in Closed CSG Cell ....................... 2-26
2.2.19 Mean Number of Member Subscribers in Hybrid CSG Cell ...................... 2-26
2.2.20 Max Number of Member Subscribers in Hybrid CSG Cell ........................ 2-27
2.2.21 Mean Number of Common Subscribers in Hybrid CSG Cell..................... 2-27
2.2.22 Max Number of Common Subscribers in Hybrid CSG Cell....................... 2-28
2.2.23 Number of CSG Subscribers ................................................................. 2-28
2.3 MME Handover Measurement........................................................................... 2-29
2.3.1 Times of Intra E-UTRAN Handover Request Without MME Change
Based S1 Interface ............................................................................... 2-29
2.3.2 Times of Successful Intra E-UTRAN Handover Without MME Change
Based S1 Interface ............................................................................... 2-29
2.3.3 Times of Intra E-UTRAN Handover Failure Without MME Change Based
S1 Interface .......................................................................................... 2-30
2.3.4 Times of Intra E-UTRAN Path Switch Request Based X2 Interface ............ 2-31
2.3.5 Times of Successful Intra E-UTRAN Path Switch Based X2 Interface ........ 2-32
2.3.6 Times of Intra E-UTRAN Path Switch Failure Based X2 Interface .............. 2-33
2.3.7 Times of Intra E-UTRAN Handover Failure without MME Change based
S1 interface for internal cause................................................................ 2-34
2.3.8 Times of Intra E-UTRAN Path Switch Failure based X2 interface for
internal cause ....................................................................................... 2-34
2.4 MME EMM Common Procedure Measurement................................................... 2-35
2.4.1 Times of EMM INFORMATION Message Sent by MME ............................ 2-35
II

2.4.2 Times of EMM Status Received............................................................... 2-35
2.4.3 Times of Sending EMM Status ................................................................ 2-36
2.4.4 Times of Identity Request ....................................................................... 2-36
2.4.5 Times of success for Identity procedure ................................................... 2-36
2.4.6 Times of Reallocation Request ................................................................ 2-37
2.4.7 Times of success for Reallocation procedure ........................................... 2-37
2.4.8 Times of Authentication Request ............................................................. 2-38
2.4.9 Times of success for Authentication procedure......................................... 2-38
2.4.10 Times of UE Authentication failure ......................................................... 2-38
2.4.11 Times of NW Authentication Failure ....................................................... 2-39
2.4.12 Times of Security Mode Request ........................................................... 2-39
2.4.13 Times of success for Security Mode procedure....................................... 2-40
2.4.14 Times of UE Authentication failure(MAC failure) ..................................... 2-40
2.4.15 Times of UE Authentication failure(Synch failure).................................... 2-41
2.4.16 Times of UE Authentication failure(Non-EPS authentication
unacceptable) ....................................................................................... 2-41
2.5 S1AP Measurement ......................................................................................... 2-42
2.5.1 Times of Receiving Management Message .............................................. 2-42
2.5.2 Times of Discarding Management Message ............................................. 2-42
2.5.3 Times of Sending Management Message ................................................ 2-42
2.5.4 Times of Initial UE Message.................................................................... 2-43
2.5.5 Times of Discarding Initial UE Message ................................................... 2-43
2.5.6 Times of UPLINK NAS TRANSPORT Message ........................................ 2-43
2.5.7 Times of Discarding UPLINK NAS TRANSPORT Message ....................... 2-44
2.5.8 Times of DOWNLINK NAS TRANSPORT Message .................................. 2-44
2.5.9 Times of Sending Initial Context Setup Request Message......................... 2-45
2.5.10 Times of Receiving Initial Context Setup Response Message .................. 2-45
2.5.11 Times of Sending E-RAB SETUP REQUEST Message ........................... 2-45
2.5.12 Times of Receiving E-RAB SETUP RESPONSE Message ...................... 2-46
2.5.13 Times of Receiving Other Message ....................................................... 2-46
2.5.14 Times of Discarding Other Message ...................................................... 2-47
2.5.15 Times of Sending Other Message.......................................................... 2-47
2.5.16 Times of Receiving UE CONTEXT RELEASE REQUEST Message ......... 2-47
2.5.17 Times of Sending UE CONTEXT RELEASE COMMAND Message.......... 2-48
2.5.18 Times of Receiving UE CONTEXT RELEASE COMPLETE Message....... 2-48
2.6 Paging Measurement of MME ........................................................................... 2-49
2.6.1 Times of E-UTRAN Paging ..................................................................... 2-49
2.6.2 Times of Success for E-UTRAN Paging ................................................... 2-49
III

2.7 MME ESM Failure Measurement per NE ........................................................... 2-50
2.7.1 Times of PDN Connection Failure (UE Trigger) ........................................ 2-50
2.7.2 Times of PDN Connection Failure (GW Trigger) ....................................... 2-51
2.7.3 Times of PDN Connection Failure (MME Trigger) ..................................... 2-51
2.7.4 Times of Default Bearer Activation Failure (UE Trigger) ............................ 2-52
2.7.5 Times of Default Bearer Activation Failure (eNodeB Trigger) ..................... 2-52
2.7.6 Times of Default Bearer Activation Failure (MME Trigger) ......................... 2-53
2.7.7 Times of Default Bearer Activation Failure (GW Trigger) ........................... 2-53
2.7.8 Times of Dedicated Bearer Activation Failure (UE Trigger) ........................ 2-54
2.7.9 Times of Dedicated Bearer Activation Failure (eNodeB Trigger)................. 2-54
2.7.10 Times of Bearer Modification Failure (UE Trigger)................................... 2-55
2.7.11 Times of Bearer Modification Failure (eNodeB Trigger)............................ 2-55
2.7.12 Times of Failed UE Requested Bearer Resource Allocation(UE
Trigger) ................................................................................................ 2-56
2.7.13 Times of Failed UE Requested Bearer Resource Allocation (MME
Trigger) ................................................................................................ 2-56
2.7.14 Times of Failed UE Requested Bearer Resource Allocation (GW
Trigger) ................................................................................................ 2-57
2.7.15 Times of Failed UE Requested Bearer Resource Modification (UE
Trigger) ................................................................................................ 2-58
2.7.16 Times of Failed UE Requested Bearer Resource Modification (MME
Trigger) ................................................................................................ 2-58
2.7.17 Times of Failed UE Requested Bearer Resource Modification (GW
Trigger) ................................................................................................ 2-59
2.8 MME EMM Basic Procedure Measurement ........................................................ 2-59
2.8.1 Times of EPS Attach Request ................................................................. 2-59
2.8.2 Times of Success for EPS Attach Procedure ............................................ 2-60
2.8.3 Times of Intra-MME TAU Attempt (SGW not Change) ............................... 2-60
2.8.4 Times of Intra-MME TAU Success (SGW not Change).............................. 2-60
2.8.5 Times of Intra-MME TAU Attempt (SGW Change)..................................... 2-61
2.8.6 Times of Intra-MME TAU Success (SGW Change) ................................... 2-61
2.8.7 Times of EPS Detach Request from UE ................................................... 2-62
2.8.8 Times of Success for EPS Detach Procedure from UE.............................. 2-62
2.8.9 Times of EPS Detach Request from MME................................................ 2-62
2.8.10 Times of Success for EPS Detach Procedure from MME......................... 2-63
2.8.11 Times of Detach Request from HSS....................................................... 2-63
2.8.12 Times of Successful Detach Procedure from HSS .................................. 2-64
2.8.13 Times of Service Request ..................................................................... 2-64
IV

2.8.14 Times of Success for Service Request Procedure................................... 2-64
2.8.15 Duration of EPS Attach Procedure (ms) ................................................. 2-65
2.8.16 Times of Attach Request From Closed CSG Cell .................................... 2-65
2.8.17 Times of Attach Request From Hybrid CSG Cell..................................... 2-65
2.8.18 Times of Success for Attach Procedure From Closed CSG Cell............... 2-66
2.8.19 Times of Success for Attach Procedure From Hybrid CSG Cell................ 2-66
2.8.20 Times of TAU Attempt From Closed CSG Cell ........................................ 2-67
2.8.21 Times of TAU Success From Closed CSG Cell ....................................... 2-67
2.8.22 Times of TAU Attempt From Hybrid CSG Cell......................................... 2-68
2.8.23 Times of TAU Success From Hybrid CSG Cell........................................ 2-68
2.8.24 Times of Service Request From Closed CSG Cell .................................. 2-68
2.8.25 Times of Success for Service Request Procedure From Closed CSG
Cell ...................................................................................................... 2-69
2.8.26 Times of Service Request From Hybrid CSG Cell ................................... 2-69
2.8.27 Times of Success for Service Request Procedure From Hybrid CSG
Cell ...................................................................................................... 2-70
2.9 MME EMM Procedure Failure based on NE Measurement.................................. 2-70
2.9.1 Times of EPS Attach Failure (UE Trigger) ................................................ 2-70
2.9.2 Times of EPS Attach Failure (MME Trigger) ............................................. 2-71
2.9.3 Times of EPS Attach Failure (GW Trigger) ............................................... 2-71
2.9.4 Times of EPS Attach Failure (HSS Trigger) .............................................. 2-72
2.9.5 Times of EPS Attach Failure (EIR Trigger) ............................................... 2-72
2.9.6 Times of Intra-MME TAU Failure with SGW not Change (UE Trigger) ........ 2-73
2.9.7 Times of Intra-MME TAU Failure with SGW not Change (MME Trigger) ..... 2-73
2.9.8 Times of Intra-MME TAU Failure with SGW not Change (GW Trigger) ....... 2-74
2.9.9 Times of Intra-MME TAU Failure with SGW not Change (HSS Trigger) ...... 2-74
2.9.10 Times of Service Request Failure (UE Trigger) ....................................... 2-75
2.9.11 Times of Service Request Failure (MME Trigger) .................................... 2-75
2.10 MME S1 Overload-Control Measurement ......................................................... 2-76
2.10.1 Number of Rejected S1 Attach Request messages for overload-control ..... 2-76
2.10.2 Number of Discarded S1 Attach Request messages for
overload-control .................................................................................... 2-76
2.10.3 Number of Rejected S1 Service Request messages for
2.10.4 Number of Discarded S1 Service Request messages for
2.10.5 Number of Rejected S1 TAU Request messages for overload-control ...... 2-77
2.10.6 Number of Discarded S1 TAU Request messages for overload-control ..... 2-78

2.10.7 Number of Rejected S1 HO Request messages for overload-control........ 2-78
2.10.8 Number of Discarded S1 HO Request messages for overload-control...... 2-79
2.10.9 Number of Rejected S1 PDN Connectivity Request messages for
2.10.10 Number of Discarded S1 PDN Connectivity Request messages for
2.10.11 Number of Rejected S1 Bearer Resource Modify Request messages
for overload-control ............................................................................... 2-80
2.10.12 Number of Discarded S1 Bearer Resource Modify Request messages
for overload-control ............................................................................... 2-80
2.10.13 Number of Discarded S1 paging messages for overload-control ............ 2-81
2.10.14 Number of Discarded S1 downlink Bearer Modify messages for
2.10.15 Number of Rejected S1 Bearer Resource Allocation Request
messages for overload-control ............................................................... 2-82
2.10.16 Number of Discarded S1 Bearer Resource Allocation Request
messages for overload-control ............................................................... 2-82
2.11 MME TAU Failure based on Failure Cause Measurement.................................. 2-83
2.11.1 Times of Intra-MME TAU with SGW not Change Failure (IMSI unknown
in HSS) ................................................................................................ 2-83
2.11.2 Times of Intra-MME TAU with SGW not Change Failure (Illegal UE)......... 2-83
2.11.3 Times of Intra-MME TAU with SGW not Change Failure (Illegal ME) ........ 2-84
2.11.4 Times of Intra-MME TAU with SGW not Change Failure (EPS services
not allowed) .......................................................................................... 2-84
and non-EPS services not allowed) ........................................................ 2-85
2.11.6 Times of Intra-MME TAU with SGW not Change Failure (UE identity
cannot be derived by the network).......................................................... 2-85
2.11.7 Times of Intra-MME TAU with SGW not Change Failure (Implicitly
detached) ............................................................................................. 2-86
2.11.8 Times of Intra-MME TAU with SGW not Change Failure (PLMN not
allowed) ............................................................................................... 2-86
2.11.9 Times of Intra-MME TAU with SGW not Change Failure (Tracking area
not allowed) .......................................................................................... 2-86
2.11.10 Times of Intra-MME TAU with SGW not Change Failure (Roaming not
allowed in this tracking area).................................................................. 2-87
not allowed in this PLMN) ...................................................................... 2-87
2.11.12 Times of Intra-MME TAU with SGW not Change Failure (No suitable
cells in tracking area) ............................................................................ 2-88
VI

2.11.13 Times of Intra-MME TAU with SGW not Change Failure (MSC
temporarily not reachable) ..................................................................... 2-88
2.11.14 Times of Intra-MME TAU Failure with SGW not Change (Network
failure).................................................................................................. 2-89
2.11.15 Times of Intra-MME TAU with SGW not Change Failure (CS domain
not available) ........................................................................................ 2-89
2.11.16 Times of Intra-MME TAU with SGW not Change Failure (ESM failure) ..... 2-90
2.11.17 Times of Intra-MME TAU with SGW not Change Failure (Congestion) ..... 2-90
2.11.18 Times of Intra-MME TAU with SGW not Change Failure (Not authorized
for this CSG)......................................................................................... 2-90
2.11.19 Times of Intra-MME TAU with SGW not Change Failure (No EPS
bearer context activated) ....................................................................... 2-91
2.11.20 Times of Intra-MME TAU with SGW not Change Failure (invalid
mandatory information element error)..................................................... 2-91
2.11.21 Times of Intra-MME TAU with SGW not Change Failure (Message type
non-existent or not implemented) ........................................................... 2-92
2.11.22 Times of Intra-MME TAU with SGW not Change Failure (information
element non-existent or not implemented) .............................................. 2-92
2.11.23 Times of Intra-MME TAU with SGW not Change Failure (conditional IE
error).................................................................................................... 2-93
2.11.24 Times of Intra-MME TAU with SGW not Change Failure (protocol error,
unspecified) .......................................................................................... 2-93
2.11.25 Times of Intra-MME TAU with SGW not Change Failure (Other
causes) ................................................................................................ 2-94
2.12 MME Service Request Failure based on Failure Cause Measurement ............... 2-94
2.12.1 Times of Service Request failure (Illegal UE).......................................... 2-94
2.12.2 Times of Service Request failure (Illegal ME) ......................................... 2-95
2.12.3 Times of Service Request failure (EPS services not allowed) .................. 2-95
2.12.4 Times of Service Request failure (EPS services and non-EPS services
not allowed) .......................................................................................... 2-95
2.12.5 Times of Service Request failure (UE identity cannot be derived by the
network) ............................................................................................... 2-96
2.12.6 Times of Service Request failure (Implicit detached) ............................... 2-96
2.12.7 Times of Service Request failure (PLMN not allowed) ............................. 2-97
2.12.8 Times of Service Request failure (Tracking Area not allowed).................. 2-97
2.12.9 Times of Service Request failure (Roaming not allowed in this tracking
area) .................................................................................................... 2-97
2.12.10 Times of Service Request failure (EPS services not allowed in this
PLMN) ................................................................................................. 2-98
2.12.11 Times of Service Request failure (No Suitable Cells In tracking area) ..... 2-98
VII

2.12.12 Times of Service Request failure (Network failure) ................................ 2-99
2.12.13 Times of Service Request failure (CS domain not available) .................. 2-99
2.12.14 Times of Service Request failure (Congestion) ....................................2-100
2.12.15 Times of Service Request failure (Not authorized for this CSG) ............2-100
2.12.16 Times of Service Request failure (CS domain temporarily not
available).............................................................................................2-100
2.12.17 Times of Service Request failure (Invalid mandatory information)..........2-101
2.12.18 Times of Service Request failure (Message type non-existent or not
implemented).......................................................................................2-101
2.12.19 Times of Service Request failure (Information element non-existent or
not implemented) .................................................................................2-102
2.12.20 Times of Service Request failure (Conditional IE error).........................2-102
2.12.21 Times of Service Request failure (Protocol error,unspecified) ...............2-103
2.12.22 Times of Service Request failure (Unknown cause)..............................2-103
2.13 MME EMM Messages Abnormal Measurement ...............................................2-103
2.13.1 Times of Receiving Attach Request of Procedure Conflict ......................2-103
2.13.2 Times of Illegal Receiving UNT Attach Request .....................................2-104
2.13.3 Times of Failed Attach Request of S1 Release ......................................2-104
2.13.4 Times of Receiving Resend Attach Request ..........................................2-105
2.13.5 Times of Receiving TAU Request of Procedure Conflict .........................2-105
2.13.6 Times of Failed TAU Request of S1 Release .........................................2-105
2.13.7 Times of Receiving Resend TAU Request .............................................2-106
2.13.8 Times of Receiving Service Request of Procedure Conflict.....................2-106
2.13.9 Times of Receiving Illegal UNT Service Request ...................................2-107
2.13.10 Times of Failed Service Request of S1 Release...................................2-107
2.13.11 Times of Receiving Resend Service Request.......................................2-107
2.14 MME dedicated bearer activation Failure based on Failure Cause
Measurement ................................................................................................2-108
2.14.1 Times of failed dedicated bearer activation (Insufficient resources) .........2-108
2.14.2 Times of failed dedicated bearer activation (Request rejected,
unspecified) .........................................................................................2-108
2.14.3 Times of failed dedicated bearer activation (Semantic error in the TFT
operation)............................................................................................2-109
2.14.4 Times of failed dedicated bearer activation (Syntactical error in the TFT
operation)............................................................................................2-109
2.14.5 Times of failed dedicated bearer activation (Invalid EPS bearer
identity) ............................................................................................... 2-110
2.14.6 Times of failed dedicated bearer activation (Semantic errors in packet
filter (s))............................................................................................... 2-110
VIII

2.14.7 Times of failed dedicated bearer activation (Syntactical errors in packet
filter (s))............................................................................................... 2-111
2.14.8 Times of failed dedicated bearer activation (Semantically incorrect
message) ............................................................................................ 2-111
2.14.9 Times of failed dedicated bearer activation (Invalid mandatory
information) ......................................................................................... 2-112
2.14.10 Times of failed dedicated bearer activation (Message type non-existent
or not implemented) ............................................................................. 2-112
2.14.11 Times of failed dedicated bearer activation (Message type not
compatible with the protocol state) ........................................................ 2-113
2.14.12 Times of failed dedicated bearer activation (Information element
non-existent or not implemented) .......................................................... 2-113
2.14.13 Times of failed dedicated bearer activation (Conditional IE error) .......... 2-114
2.14.14 Times of failed dedicated bearer activation (Message not compatible
with the protocol state) ......................................................................... 2-114
2.14.15 Times of failed dedicated bearer activation (Protocol error,
unspecified) ......................................................................................... 2-115
2.14.16 Times of failed dedicated bearer activation (PTI already in use) ............ 2-115
2.14.17 Times of failed dedicated bearer activation (EPS QoS not accepted) ...... 2-116
2.14.18 Times of failed dedicated bearer activation (Reactivation requested) ...... 2-116
2.14.19 Times of failed dedicated bearer activation (EPS bearer context
without TFT already activated) .............................................................. 2-117
2.14.20 Times of failed dedicated bearer activation (PTI mismatch) .................. 2-117
2.14.21 Times of failed dedicated bearer activation (Collision with network
initiated request) .................................................................................. 2-118
2.14.22 Times of failed dedicated bearer activation (Invalid PTI value) .............. 2-118
2.14.23 Times of failed dedicated bearer activation (Other causes) ................... 2-119
2.15 MME bearer modification Failure based on Failure Cause Measurement .......... 2-119
2.15.1 Times of failed bearer modification (Insufficient resources) ..................... 2-119
2.15.2 Times of failed bearer modification (Semantic error in the TFT
operation)............................................................................................2-120
2.15.3 Times of failed bearer modification (Syntactical error in the TFT
operation)............................................................................................2-120
2.15.4 Times of failed bearer modification (Invalid EPS bearer identity) .............2-121
2.15.5 Times of failed bearer modification (Semantic errors in packet filter
(s))......................................................................................................2-121
2.15.6 Times of failed bearer modification (Syntactical errors in packet filter
(s))......................................................................................................2-122
2.15.7 Times of failed bearer modification (EPS bearer context without TFT
already activated).................................................................................2-122
IX

2.15.8 Times of failed bearer modification (Semantically incorrect message) ......2-123
2.15.9 Times of failed bearer modification (Invalid mandatory information).........2-123
2.15.10 Times of failed bearer modification (Message type non-existent or not
implemented).......................................................................................2-124
2.15.11 Times of failed bearer modification (Message type not compatible with
the protocol state) ................................................................................2-124
2.15.12 Times of failed bearer modification (Information element non-existent
or not implemented) .............................................................................2-125
2.15.13 Times of failed bearer modification (Conditional IE error)......................2-125
2.15.14 Times of failed bearer modification (Message not compatible with the
protocol state)......................................................................................2-125
2.15.15 Times of failed bearer modification (Protocol error, unspecified)............2-126
2.15.16 Times of failed bearer modification (PTI already in use)........................2-126
2.15.17 Times of failed bearer modification (Request rejected, unspecified).......2-127
2.15.18 Times of failed bearer modification (EPS QoS not accepted) ................2-127
2.15.19 Times of failed bearer modification (Reactivation requested) ................2-128
2.15.20 Times of failed bearer modification (PTI mismatch) ..............................2-128
2.15.21 Times of failed bearer modification (Collision with network initiated
request)...............................................................................................2-129
2.15.22 Times of failed bearer modification (Invalid PTI value)..........................2-129
2.15.23 Times of failed bearer modification (Other causes)...............................2-129
2.16 MME Attach Failure based on Failure Cause Measurement .............................2-130
2.16.1 Times of EPS Attach failure (Illegal UE) ................................................2-130
2.16.2 Times of EPS Attach failure (Illegal ME) ................................................2-130
2.16.3 Times of EPS Attach failure (EPS services not allowed) .........................2-131
2.16.4 Times of EPS Attach failure (EPS services and non-EPS services not
allowed) ..............................................................................................2-131
2.16.5 Times of EPS Attach failure (PLMN not allowed) ...................................2-132
2.16.6 Times of EPS Attach failure (Tracking Area not allowed) ........................2-132
2.16.7 Times of EPS Attach failure (Roaming not allowed in this tracking
area) ...................................................................................................2-132
2.16.8 Times of EPS Attach failure (EPS services not allowed in this PLMN) ......2-133
2.16.9 Times of EPS Attach failure (No Suitable Cells In tracking area) .............2-133
2.16.10 Times of EPS Attach failure (Network failure) ......................................2-134
2.16.11 Times of EPS Attach failure (ESM failure)............................................2-134
2.16.12 Times of EPS Attach failure (ESM failure for User Reason) ..................2-135
2.16.13 Times of EPS Attach failure (Congestion)............................................2-135
2.16.14 Times of EPS Attach failure (Not authorized for this CSG) ....................2-135
2.16.15 Times of EPS Attach failure (Invalid mandatory information) .................2-136

2.16.16 Times of EPS Attach failure (Message type non-existent or not
implemented).......................................................................................2-136
2.16.17 Times of EPS Attach failure (Information element non-existent or not
implemented).......................................................................................2-137
2.16.18 Times of EPS Attach failure (Conditional IE error) ................................2-137
2.16.19 Times of EPS Attach failure (Protocol error, unspecified) ......................2-137
2.16.20 Times of EPS Attach failure (Other causes).........................................2-138
2.17 MME Periodic TAU Measurement ...................................................................2-138
2.17.1 Times of Attempt .................................................................................2-138
2.17.2 Times of success.................................................................................2-139
2.17.3 Times of IMSI unknown in HSS ............................................................2-139
2.17.4 Times of Illegal UE ..............................................................................2-140
2.17.5 Times of Illegal ME ..............................................................................2-140
2.17.6 Times of EPS services not allowed .......................................................2-140
2.17.7 Times of EPS services and non-EPS services not allowed .....................2-141
2.17.8 Times of UE identity cannot be derived by the network...........................2-141
2.17.9 Times of Implicitly detached .................................................................2-142
2.17.10 Times of PLMN not allowed................................................................2-142
2.17.11 Times of Tracking area not allowed .....................................................2-143
2.17.12 Times of Roaming not allowed in this tracking area ..............................2-143
2.17.13 Times of EPS services not allowed in this PLMN .................................2-144
2.17.14 Times of No suitable cells in tracking area ...........................................2-144
2.17.15 Times of MSC temporarily not reachable .............................................2-144
2.17.16 Times of Network failure.....................................................................2-145
2.17.17 Times of CS domain not available.......................................................2-145
2.17.18 Times of ESM failure..........................................................................2-146
2.17.19 Times of Congestion ..........................................................................2-146
2.17.20 Times of Not authorized for this CSG ..................................................2-147
2.17.21 Times of No EPS bearer context activated ..........................................2-147
2.17.22 Times of invalid mandatory information element error...........................2-148
2.17.23 Times of Message type non-existent or not implemented......................2-148
2.17.24 Times of information element non-existent or not implemented .............2-148
2.17.25 Times of conditional IE error ...............................................................2-149
2.17.26 Times of protocol error, unspecified ....................................................2-149
2.17.27 Times of Other causes .......................................................................2-150
Chapter 3 MME Track Measurement ......................................................... 3-1

3.1 Subscriber Measurement of MME TA................................................................... 3-1
3.1.1 Mean number of Attach Subscribers per TA ............................................... 3-1
XI

3.1.2 Max number of Attach Subscribers per TA ................................................. 3-2
3.1.3 Number of Subscribers in ECM-IDLE State per TA ..................................... 3-2
3.1.4 Max Number of Subscribers in ECM-IDLE State per TA .............................. 3-3
3.1.5 Number of Subscribers in ECM-CONNECT State per TA ............................ 3-3
3.1.6 Max Number of Subscribers in ECM-CONNECT State per TA ..................... 3-4
3.2 TA Update Measurement of MME TA................................................................... 3-4
3.2.1 Times of TAU Attempt Without SGW Change per TA .................................. 3-4
3.2.2 Times of TAU Success Without SGW Change per TA ................................. 3-5
3.2.3 Times of TAU Without SGW Change Failure per TA (Illegal UE) .................. 3-6
3.2.4 Times of TAU Without SGW Change Failure per TA (Illegal ME).................. 3-7
3.2.5 Times of TAU Without SGW Change Failure per TA (EPS services not
allowed) ................................................................................................. 3-8
3.2.6 Times of TAU Without SGW Change Failure per TA (EPS services and
non-EPS services not allowed) ................................................................ 3-9
3.2.7 Times of TAU Without SGW Change Failure per TA (UE identity cannot
be derived by the network)..................................................................... 3-10
3.2.8 Times of TAU Without SGW Change Failure per TA (Implicitly detached) ......3-11
3.2.9 Times of TAU Without SGW Change Failure per TA (PLMN not allowed) ..... 3-12
3.2.10 Times of TAU Without SGW Change Failure per TA (Tracking area not
allowed) ............................................................................................... 3-13
3.2.11 Times of TAU Without SGW Change Failure per TA (Roaming not
allowed in this tracking area).................................................................. 3-14
3.2.12 Times of TAU Without SGW Change Failure per TA (EPS services not
allowed in this PLMN)............................................................................ 3-15
3.2.13 Times of TAU Without SGW Change Failure per TA (No suitable cells in
tracking area) ....................................................................................... 3-16
3.2.14 Times of TAU Without SGW Change Failure per TA (Not authorized for
this CSG) ............................................................................................. 3-17
3.2.15 Times of TAU Without SGW Change Failure per TA (No EPS bearer
context activated).................................................................................. 3-18
3.2.16 Times of TAU Without SGW Change Failure per TA (invalid mandatory
information element error) ..................................................................... 3-19
3.2.17 Times of TAU Without SGW Change Failure per TA (information
element non-existent or not implemented) .............................................. 3-20
3.2.18 Times of TAU Without SGW Change Failure per TA (conditional IE
error).................................................................................................... 3-21
3.2.19 Times of TAU Without SGW Change Failure per TA (protocol error)......... 3-22
3.2.20 Times of TAU Failure Without SGW Change per TA (Network Failure) ..... 3-23
3.2.21 Times of Receiving Repeat TAU Request Message ................................ 3-24
XII

3.2.22 Times of TAU Without SGW Change Failure per TA (IMSI Unknown in
HSS) .................................................................................................... 3-24
3.2.23 Times of TAU Without SGW Change Failure per TA (MSC Temporarily
not Reachable) ..................................................................................... 3-25
3.2.24 Times of TAU Without SGW Change Failure per TA (CS domain not
available).............................................................................................. 3-26
3.2.25 Times of TAU Without SGW Change Failure per TA (ESM Failure) .......... 3-27
3.2.26 Times of TAU Without SGW Change Failure per TA (Congestion)............ 3-28
3.2.27 Times of TAU Without SGW Change Failure per TA (Message Type
Non-Existent or not Implemented) .......................................................... 3-29
3.2.28 Times of TAU Failure without SGW Change per TA (Network failure for
UE or radio reason)............................................................................... 3-30
3.2.29 Times of TAU Attempt Intra-MME With SGW unchanged per TA.............. 3-31
3.2.30 Times of TAU Success Intra-MME With SGW unchanged per TA............. 3-31
3.3 Attach Measurement of MME TA ....................................................................... 3-32
3.3.1 Times of Attach Request from UE per TA ................................................. 3-32
3.3.2 Times of Success for Attach Procedure from UE per TA............................ 3-33
3.3.3 Times of EPS Attach Failure per TA (Illegal UE) ....................................... 3-34
3.3.4 Times of EPS Attach Failure per TA (Illegal ME) ....................................... 3-35
3.3.5 Times of EPS Attach Failure per TA (EPS services not allowed) ................ 3-36
3.3.6 Times of EPS Attach Failure per TA (EPS services and non-EPS services
not allowed) .......................................................................................... 3-37
3.3.7 Times of EPS Attach Failure per TA (PLMN not allowed) .......................... 3-38
3.3.8 Times of EPS Attach Failure per TA (Tracking Area not allowed) ............... 3-39
3.3.9 Times of EPS Attach Failure per TA (Roaming not allowed in this tracking
area) .................................................................................................... 3-40
3.3.10 Times of EPS Attach Failure per TA (EPS services not allowed in this
PLMN) ................................................................................................. 3-41
3.3.11 Times of EPS Attach Failure per TA (No Suitable Cells In tracking
area) .................................................................................................... 3-42
3.3.12 Times of EPS Attach Failure per TA (ESM failure) .................................. 3-43
3.3.13 Times of EPS Attach Failure per TA (Not authorized for this CSG) ........... 3-44
3.3.14 Times of EPS Attach Failure per TA (Invalid mandatory information) ........ 3-45
3.3.15 Times of EPS Attach Failure per TA (Information element non-existent
or not implemented) .............................................................................. 3-46
3.3.16 Times of EPS Attach Failure per TA (Conditional IE error) ....................... 3-47
3.3.17 Times of EPS Attach Failure per TA (Protocol error) ............................... 3-48
3.3.18 Times of EPS Attach Failure per TA (Network Failure) ............................ 3-49
3.3.19 Times of EPS Attach Failure per TA (ESM Failure for User Reason) ........ 3-50
XIII

3.3.20 Times of Attach produce per TA (ms) ..................................................... 3-51
3.3.21 Times of Receiving Attach Request of Procedure Conflict ....................... 3-52
3.3.22 Times of Receiving UNT Attach Request of App Resource Fail................ 3-52
3.3.23 Times of EPS Attach Failure per TA (IMSI Unknown in HSS)................... 3-53
3.3.24 Times of EPS Attach Failure per TA (UE Identity Cannot be Derived by
the Network) ......................................................................................... 3-54
3.3.25 Times of EPS Attach Failure per TA (MSC Temporarily not Reachable) ..... 3-54
3.3.26 Times of EPS Attach Failure per TA (CS Domain not Available)............... 3-55
3.3.27 Times of EPS Attach Failure per TA (Congestion)................................... 3-56
3.3.28 Times of EPS Attach Failure per TA (Message Type Non-Existent or not
Implemented) ....................................................................................... 3-57
3.3.29 Times of EPS Attach Failure per TA (Network Failure for UE or Radio
Reason) ............................................................................................... 3-58
3.4 Paging Measurement of MME TA ...................................................................... 3-59
3.4.1 Times of E-UTRAN Paging per TA........................................................... 3-59
3.4.2 Times of Success for E-UTRAN Paging per TA ........................................ 3-59
3.5 Detach Measurement of MME TA ...................................................................... 3-60
3.5.1 Times of EPS Detach Request from UE per TA ........................................ 3-60
3.5.2 Times of Success for EPS Detach Procedure from UE per TA ................... 3-61
3.5.3 Times of EPS Detach Request from MME per TA ..................................... 3-62
3.5.4 Times of Success for EPS Detach Procedure from MME per TA................ 3-63
3.5.5 Times of EPS Detach Request from HSS per TA ...................................... 3-64
3.5.6 Times of Success for EPS Detach Procedure from HSS per TA................. 3-65
3.5.7 Times of Receiving repeat Detach Request message ............................... 3-66
3.5.8 Times of Sending repeat Detach Request message.................................. 3-66
3.6 Service Request Measurement of MME TA ........................................................ 3-67
3.6.1 Times of Receiving repeat Service Request message............................... 3-67
3.6.2 Times of Service Request ....................................................................... 3-67
3.6.3 Successful Times of service request ........................................................ 3-68
Chapter 4 MME Interface Measurement ................................................... 4-1

4.1 MME S1 Interface Measurement ......................................................................... 4-1
4.1.1 Numbers of IP Packet MME S1 Interface Received .................................... 4-1
4.1.2 Numbers of IP Packet MME S1 Interface Sent ........................................... 4-1
4.1.3 Bytes of IP Packet MME S1 Interface Received(Byte)................................. 4-2
4.1.4 Bytes of IP Packet MME S1 Interface Sent(Byte)........................................ 4-2
Chapter 5 SAE-GW Measurement ............................................................. 5-1

5.1 S1u Port Flow Measurement ............................................................................... 5-1
XIV

5.1.1 Number of Data Packets Received from S1u Interface................................ 5-1
5.1.2 Number of Data Bytes Received from S1u Interface (Byte) ......................... 5-1
5.1.3 Number of Data Packets Sent to S1u Interface........................................... 5-2
5.1.4 Number of Data Bytes Sent to S1u Interface (Byte) .................................... 5-2
5.1.5 Peak Rate of Data Packets Received from S1u Interface (pps) ................... 5-3
5.1.6 Peak Rate of Data Bytes Received from S1u Interface(KB/s) ...................... 5-3
5.1.7 Peak Rate of Data Packets Sent to S1u Interface (pps) .............................. 5-4
5.1.8 Peak Rate of Data Bytes Sent to S1u Interface (KB/s) ................................ 5-4
5.2 SGi Port Flow Measurement ............................................................................... 5-4
5.2.1 Number of Data Packets Sent to SGi Interface ........................................... 5-4
5.2.2 Number of Uplink Data Bytes Sent to SGi Interface (Byte) .......................... 5-5
5.2.3 Number of Data Packets Received from SGi Interface ................................ 5-5
5.2.4 Number of Data Bytes Received from SGi Interface (Byte).......................... 5-6
5.2.5 Peak Rate of Data Packets Sent to SGi Interface (pps)............................... 5-6
5.2.6 Peak Rate of Data Bytes Sent to SGi Interface(KB/s) ................................. 5-6
5.2.7 Peak Rate of Data Packets Received from SGi Interface (pps).................... 5-7
5.2.8 Peak Rate of Data Bytes Received from SGi Interface (KB/s)...................... 5-7
Glossary .......................................................................................................... I
XV

This page intentionally left blank.
XVI

Chapter 1
Introduction to the
Performance Measurement
Table of Contents
Relationship Between the Performance Counters and the System Performance ........1-1
Introduction to the Format of the Performance Counters.............................................1-2
1.1 Relationship Between the Performance Counters

and the System Performance
Description
Performance counters are the data reflecting the operational status of the system, and
they reflect the performance of a module in the ZXUN iEPC front-end subsystem over a
period of time. By measuring the system performance, you can know the performance
status of the system. The operators can measure the performance indices periodically to
know the operational status of the system, and locate and solve problems by using the
performance measurement data. The system performance reflects the operational status
of the system, while the performance measurement measures the performance indices of
the system, and it furthermore analyzes the operational status of the network, providing
basics and verification methods for the network optimization.
Relationship
The performance measurement functional module is used to calculate and analyze
the performance counters of the front-end subsystem. The performance measurement
functional module collects the service performance of the front-end subsystem and the
operational performance of boards of the ZXUN iEPC. The performance measurement
provides the data of performance counters. Data analysis is required to get the operational
status of the system from the data of performance counters.
1-1

ZXUN iEPC Performance Counter Reference
1.2 Introduction to the Format of the Performance

Counters
Description
The description format of each performance counter in this manual is consistent, including
the following formats:
l Counter ID
l Description
l Triggers
l Collection method
Counter ID
The counter ID is composed of a "C" and this counter calculates the numbers, which is a
unique identifier of the counter.
Description
Description of the performance counters.
Triggers
The measurement triggering point describes the triggering process of a performance
counter.
Collection Method
Collection methods of the performance counters are described in Table 1-1.
Table 1-1 Collection Method
Value Name Description
CC Accumulation It traces the accumulated changes of an event in the collection granularity

Counter (such as PDP activation), and the value of the counter generally is
incremented in an unidirectional way.
TA Time Average It samples the value of continuously changing even data every 10
Counter seconds, and calculates and reports the average value of all 10 - second
data when the collection granularity ends.
1-2

Chapter 1 Introduction to the Performance Measurement
Value Name Description
Max Maximum It generally obtains the event data every 10 seconds (the data may be the
Value Counter sampling value of the continuous event data, or may be the variation of
the data over 10 seconds), and only the maximum result is saved in the
counter. In addition, data reported by this counter is the maximum value
of a module or a unit over the collection granularity period. Data of each
module or unit is independent, therefore, it is meaningless to combine
them by module, and they cannot be provided to the background as the
original data for calculating the peak KPI of the NE.
Peak Peak Value It calculates the peak data of an event in the whole NE using the peak
Counter value algorithm, and the results of this counter are gathered and displayed
on the OMP.
1-3

1-4

Chapter 2
MME Measurement
Table of Contents
MME ESM Measurement ...........................................................................................2-1
MME User Measurement..........................................................................................2-19
MME Handover Measurement..................................................................................2-29
MME EMM Common Procedure Measurement.........................................................2-35
S1AP Measurement .................................................................................................2-42
Paging Measurement of MME ..................................................................................2-49
MME ESM Failure Measurement per NE ..................................................................2-50
MME EMM Basic Procedure Measurement ..............................................................2-59
MME EMM Procedure Failure based on NE Measurement.......................................2-70
MME S1 Overload-Control Measurement .................................................................2-76
MME TAU Failure based on Failure Cause Measurement ........................................2-83
MME Service Request Failure based on Failure Cause Measurement......................2-94
MME EMM Messages Abnormal Measurement ......................................................2-103
MME dedicated bearer activation Failure based on Failure Cause Measurement ...2-108
MME bearer modification Failure based on Failure Cause Measurement ............... 2-119
MME Attach Failure based on Failure Cause Measurement ...................................2-130
MME Periodic TAU Measurement...........................................................................2-138
2.1 MME ESM Measurement

2.1.1 Mean Number of Dedicated Bearers in Active State
Counter ID
C420010001
Description
This counter counts the average number of the special bearers in the activated status.
Triggers
When the status of the special bearer is set as the activated status, the counter is
incremented by one. When the service invokes the DB interface to create the bearer
context (for a Combo office, the bearer type is the MME bearer when the bearer/PDP
context is created), if the DB determines the created type as special bearer, the counter
is incremented by one; when the service invokes the DB interface to delete the bearer
2-1

context (for a Combo office, the bearer type is the MME bearer when the bearer/PDP
context is created), if the DB determines the created type as the special bearer, the
counter is decremented by one.
Collection Method
TA
2.1.2 Max Number of Dedicated Bearers in Active State

Counter ID
C420010002
Description
This counter counts the maximum number of the special bearers in the activated status.
Triggers
After the status of the special bearer is set to activated, if the current number is equal to
the last maximum value, this counter is incremented by one. When the service invokes
the DB interface to create the bearer context (for a Combo office, the bearer type is the
MME bearer when the bearer/PDP context is created), if the DB determines the created
type as special bearer, the counter is incremented by one; when the service invokes the
DB interface to delete the bearer context (for a Combo office, the bearer type is the MME
bearer when the bearer/PDP context is created), if the DB determines the created type as
the special bearer, the counter is decremented by one.
Collection Method
Max
2.1.3 Times of Dedicated Bearer Activation Requested

Counter ID
C420010003
Description
This counter counts the times of activation requests of the special bearer.
Triggers
The calculation is made after the MME sends the Activete Dedicated EPS Bearer Context
Request message to the UE, and the flow succeeds or fails, as shown in the following
figure. A indicates the triggering position of this measurement item in the flow.
2-2

Chapter 2 MME Measurement
Collection Method
CC
2.1.4 Times of Successful Dedicated Bearer Activation

Counter ID
C420010004
Description
This counter counts the times of successful activation of the special bearers
Triggers
The MME receives the Activete Dedicated EPS Bearer Context Accept message sent
from the UE, as shown in the following figure. A indicates the triggering position of this
measurement item in the flow.
2-3

Collection Method
CC
2.1.5 Times of Failed Dedicated Bearer Activation

Counter ID
C420010005
Description
This counter counts the times of failed activation of the special bearers.
Triggers
The MME receives the Activete Dedicated EPS Bearer Context Reject message sent
from the UE, as shown in the following figure. A indicates the triggering position of this
2-4

Collection Method
CC
2.1.6 Times of Dedicated Bearer Deactivation Requested

Counter ID
C420010006
Description
This counter counts the times that the MME sends the Deactivate EPS Bearer Context
Request messages to the UE.
Triggers
After the MME sent the Deactivate EPS Bearer Context Request message to the UE,
the flow succeeded or no response message was received till time-out, as shown in the
following figure. A indicates the triggering position of this measurement item in the flow.
2-5

Collection Method
CC
2.1.7 Times of Successful Dedicated Bearer Deactivation

Requested
Counter ID
C420010007
Description
After the MME sends the Deactivate EPS Bearer Context Request message to the UE, this
counter calculates the times that the MME receives the Deactivate EPS Bearer Context
Accept messages sent from the UE.
Triggers
The UE returns the Deactivate EPS Bearer Context Accept message to the MME, as shown
in the following figure. A indicates the triggering position of this measurement item in the
flow.
2-6

Collection Method
CC
2.1.8 Times of Bearer Modify Requested

Counter ID
C420010008
Description
This counter counts the times of attempt times that the MME sends the Modify EPS Bearer
Context Request messages to the UE.
Triggers
The calculation is made after the MME sent the Modify EPS Bearer Context Request
message to the UE, and the flow succeeds or fails, as shown in the following figure. A
indicates the triggering position of this measurement item in the flow.
2-7

Collection Method
CC
2.1.9 Times of Successful Bearer Update Requested

Counter ID
C420010009
Description
This counter counts the times that the MME receives the Modify EPS Bearer Context
Accept messages sent from the UE
Triggers
The calculation is made when the MME receives the Modify EPS Bearer Context Accept
message sent from the UE, as shown in the following figure. A indicates the triggering
position of this measurement item in the flow.
2-8

Collection Method
CC
2.1.10 Times of Failed Bearer Update Requested

Counter ID
C420010010
Description
This counter counts the times of times that the MME receives the Modify EPS Bearer
Context Reject messages sent from the UE
Triggers
The calculation is made when the MME receives the Modify EPS Bearer Context Reject
message sent from the UE, as shown in the following figure. A indicates the triggering
2-9

Collection Method
CC
2.1.11 Total Time of Dedicated Bearer Activation Procedure (ms)

Counter ID
C420010011
Description
This counter counts the time period from when SGW receives the Create Bearer Request
messages to when MME responds with the Create Bearer Response messages to SGW
within a measurement period.
Triggers
The counter starts counting the period at point A1 when MME receives the Create Bearer
Request message and ends counting at point A2 when MME returns the Create Bearer
Response message.
The difference between the end time and the start time is the time interval for establishing
the dedicated bearer.
2-10

Collection Method
CC
2.1.12 Total Time of Default Bearer Activation Procedure (ms)

Counter ID
C420010012
Description
This counter counts the interval, within a measurement period, from when UE receives the
Attach Request or PDN Connection Request messages from UE to when MME receives
the Modify Bearer Response messages from SGW.
Triggers
The counter starts counting the period at point A1 when MME receives the Attach
Request/PDN Connection Request message and ends counting at point A2 when MME
receives the Modify Bearer Response message from SGW.
The difference between the end time and the start time is the time interval for establishing
the default bearer.
2-11

Collection Method
CC
2.1.13 Times of PDN Connection Request

Counter ID
C420010013
Description
This counter counts the times of the PDN connection requests within a measurement
period.
Triggers
The counter counts when MME receives an Attach Request or PDN Connection Request
message from UE and the flow succeeds or fails. "A" as shown in the following figure
indicates the location where the measurement item is triggered in the flow.
2-12

Collection Method
CC
2.1.14 Times of Successful PDN Connection

Counter ID
C420010014
Description
This counter counts the times that PDN connection succeeds within a measurement period.
Triggers
The counter counts when MME receives a Modify Bearer Response message from SGW
in which the Cause value is Accept. "A" as shown in the following figure indicates the
location where the measurement item is triggered in the flow.
Collection Method
CC
2.1.15 Times of PDN Connection Failure

Counter ID
C420010015
Description
This counter counts the times that PDN connection fails within a measurement period.
2-13

Triggers
The counter counts when MME sends to UE an Attach Reject or PDN Connection
Reject message. "A" as shown in the following figure indicates the location where the
measurement item is triggered in the flow.
Collection Method
CC
2.1.16 Times of Default Bearer Deactivation Requested

Counter ID
C420010020
Description
This counter counts the times that MME sends a DEACTIVATE EPS BEARER CONTEXT
REQUEST message to UE.
Triggers
This counter is incremented by one when the default carrier deactivation flow is complete
or timeout occurs before a response is received, after ESM sends a DEACTIVATE EPS
BEARER CONTEXT REQUEST message to UE.
Collection Method
CC
2-14

2.1.17 Times of Successful Default Bearer Deactivation

Counter ID
C420010021
Description
This counter counts the times that MME sends a DEACTIVATE EPS BEARER CONTEXT
REQUEST message to UE and receives a DEACTIVATE EPS BEARER CONTEXT
ACCEPT message.
Triggers
This counter is incremented by one when ESM sends a DEACTIVATE EPS BEARER
CONTEXT REQUEST message to UE and the default carrier deactivation flow is complete.
Collection Method
CC
2.1.18 Times of PDN Disconnect Request

Counter ID
C420010022
Description
This counter counts the times of PDN disconnection requests.
Triggers
When the disconnection flow succeeds or fails after ESM receives PDN Disconnect
Request from UE.
Collection Method
CC
2.1.19 Times of Successful PDN Disconnect

Counter ID
C420010023
Description
This counter counts the times that PDN disconnection succeeds.
2-15

Triggers
This counter is incremented by one when ESM sends Deactive EPS Bearer Context
Request to UE.
Collection Method
CC
2.1.20 Times of PDN Disconnect Failure

Counter ID
C420010024
Description
This counter counts the times that PDN disconnection fails.
Triggers
This counter is incremented by one when ESM sends PDN Disconnect Reject to UE.
Collection Method
CC
2.1.21 Times of UE Requested Bearer Resource Allocation

Counter ID
C420010025
Description
This counter counts the times that UE requests to allocate bearer resources.
Triggers
This counter is incremented by one when the flow succeeds or fails after ESM receives
Bearer Resource Allocation Request from UE.
Collection Method
CC
2-16

2.1.22 Times of Successful UE Requested Bearer Resource

Allocation
Counter ID
C420010026
Description
This counter counts the times that UE succeeds in requesting bearer resource allocation.
Triggers
This counter is incremented by one after ESM sends Active Dedicated EPS Bearer Context
Request or Modify EPS Bearer Context Request to UE.
Collection Method
CC
2.1.23 Times of Failed UE Requested Bearer Resource Allocation

Counter ID
C420010027
Description
This counter counts the times that UE fails to request bearer resource allocation.
Triggers
This counter is incremented by one when ESM sends Bearer Resource Allocation Reject
to UE.
Collection Method
CC
2.1.24 Times of UE Requested Bearer Resource Modification

Counter ID
C420010028
Description
This counter counts the times that UE requests to allocate bearer resources.
2-17

Triggers
This counter is incremented by one when the flow succeeds or fails after ESM receives
Bearer Resource Modification Request from UE.
Collection Method
CC
2.1.25 Times of Successful UE Requested Bearer Resource

Modification
Counter ID
C420010029
Description
This counter counts the times that UE succeeds in requesting bearer resource modification.
Triggers
This counter is incremented by one after ESM sends Active Dedicated EPS Bearer Context
Request, Modify EPS Bearer Context Request, or Deactive EPS Bearer Context Request
to UE.
Collection Method
CC
2.1.26 Times of Failed UE Requested Bearer Resource Modification

Counter ID
C420010030
Description
This counter counts the times that UE fails to request bearer resource modification.
Triggers
This counter is incremented by one when ESM sends Bearer Resource Modification Reject
to UE.
Collection Method
CC
2-18

2.2 MME User Measurement

2.2.1 Mean Number of Subscribers in ECM-IDLE State
Counter ID
C420020002
Description
This counter counts the average number of the subscribers in the ECM-IDLE status.
Triggers
There is no NAS signaling between the UE and the network side; after the subscriber
status is set as the ECM-IDLE, the counter is incremented by one.
When the service invokes the DB interface to create, delete, and modify the MME context,
DB determines whether it becomes the ECM-IDLE status from other status: If so, the
counter is incremented by one; and the DB determines whether it becomes other status
from the ECM-IDLE status: If so, the counter is decremented by one.
Collection Method
TA
2.2.2 Max Number of Subscribers in ECM-IDLE State

Counter ID
C420020003
Description
This counter counts the maximum number of subscribers in the ECM-IDLE status.
Triggers
After the NAS signaling connection between the UE and the network side is deleted and
the subscriber status is set to ECM-IDLE, if the current number equals to the last maximum
value, the counter is incremented by one.
DB determines whether it becomes the ECM-IDLE status from other status: If so, the
counter is incremented by one; and the DB determines whether it becomes other status
from the ECM-IDLE status: If so, the counter is decremented by one.
Collection Method
Max
2-19

2.2.3 Mean Number of Subscribers in ECM-CONNECTED State

Counter ID
C420020004
Description
This counter counts the average number of the subscribers in the ECM-CONNECTED
status.
Triggers
DB determines whether it becomes the ECM-CONNECTED status from other status: If
so, the counter is incremented by one; and the DB determines whether it becomes other
status from the ECM-CONNECTED status: If so, the counter is decremented by one.
Collection Method
TA
2.2.4 Max Number of Subscribers in ECM-CONNECTED State

Counter ID
C420020005
Description
This counter counts the maximum number of the subscribers in the ECM-CONNECTED
status.
Triggers
After the NAS signaling connection between the UE and the network side is established
and the subscriber status is set to ECM-CONNECTED, if the current number is equal to
the last maximum value, the counter is incremented by one.
DB determines whether it becomes the ECM-CONNECTED status from other status: If
so, the counter is incremented by one; and the DB determines whether it becomes other
status from the ECM-CONNECTED status: If so, the counter is decremented by one.
Collection Method
Max
2-20

2.2.5 Mean Number of EPS Attach subscribers

Counter ID
C420020006
Description
This counter counts the average number of attachment subscribers.
Triggers
l This counter is incremented by one when a new subscriber attaches.
l This counter is incremented by one when TA update succeeds.
l This counter decrements when an old subscriber detaches.
l This counter decrements when an old subscriber fails to attach.
l This counter decrements when an old subscriber TA update fails.
Collection Method
TA
2.2.6 Max Number of EPS Attach subscribers

Counter ID
C420020007
Description
This counter counts the maximum number of attachment subscribers.
Triggers
l This counter is incremented by one when a new subscriber attaches and exceeds the
maximum value of last time.
l This counter is incremented by one when TA update succeeds and exceeds the
maximum value of last time.
Collection Method
MAX
2.2.7 Mean number of default bearers in active state

Counter ID
C420020008
2-21

Description
This counter counts the average number of default bearers in activated status.
Triggers
This counter is incremented when the status of a default bearer is set as activated status.
Collection Method
TA
2.2.8 Max number of default bearers in active state

Counter ID
C420020009
Description
This counter counts the maximum number of default bearers in activated status.
Triggers
This counter is incremented when the status of a default bearer is set as activated status,
and current number equals to maximum number of last time.
Collection Method
MAX
2.2.9 Mean number of GBR bearers in active state

Counter ID
C420020010
Description
This counter counts the average number of GBR bearers in activated status.
Triggers
This counter is incremented after the GBR bearer status is set as activated status.
Collection Method
TA
2-22

2.2.10 Max number of GBR bearers in active state

Counter ID
C420020011
Description
This counter counts the maximum number of GBR bearers in activated status.
Triggers
This counter is incremented when the status of a GBR bearer is set to activated, and the
current number is equal to the previous maximum number.
Collection Method
MAX
2.2.11 Mean number of non-GBR bearers in active state

Counter ID
C420020012
Description
This counter counts the average number of non-GBR beaters in activated status.
Triggers
This counter is incremented when the status of a Non-GBR bearer is set as activated
status.
Collection Method
TA
2.2.12 Max number of non-GBR bearers in active state

Counter ID
C420020013
Description
This counter counts the maximum number of non-GBR bearers in activated status.
2-23

Triggers
This counter is incremented when the status of a Non-GBR bearer is set as activated
status, and current number is equal to the previous maximum number.
Collection Method
MAX
2.2.13 Number of MME Requested Default Bearers

Counter ID
C420020014
Description
This counter counts the number of default bearers that the MME requests to establish.
Triggers
The MME sends a Create Session Request message to the SGW, containing a default
bearer establishment request. This counter is incremented by one when a response is
received from the SGW or when the MME fails.
Collection Method
CC
2.2.14 Number of Successful MME Requested Default Bearers

Counter ID
C420020015
Description
This counter counts the number of default bearers established by the MME successfully.
Triggers
This counter is incremented by one when the MME receives a Create Session Response
message from the SGW, containing default bearer establishment success information and
the cause value "Request Accepted".
Collection Method
CC
2-24

2.2.15 Number of MME Requested Dedicated Bearers

Counter ID
C420020016
Description
This counter counts the number of dedicated bearers that the MME requests to establish.
Triggers
The MME sends a Create Session Request message to the SGW, containing a dedicated
bearer establishment request. This counter is incremented by one when a response is
received from the SGW or when the MME fails.
Collection Method
CC
2.2.16 Number of Successful MME Requested Dedicated Bearers

Counter ID
C420020017
Description
This counter counts the number of dedicated bearers established by the MME successfully.
Triggers
This counter is incremented by one when the MME receives a Create Session Response
message from the SGW, containing dedicated bearer establishment success information
and the cause value "Request Accepted".
Collection Method
CC
2.2.17 Mean Number of Member Subscribers in Closed CSG Cell

Counter ID
C420020022
Description
This counter counts the average number of member subscribers in a closed CSG cell.
2-25

Triggers
This counter is incremented by one when:
l A member subscriber in the closed CSG cell successfully attaches.
l The tracking area of a member subscriber is updated for the first time.
l A member subscriber is switched over to the local CSG.
Collection Method
TA
2.2.18 Max Number of Member Subscribers in Closed CSG Cell

Counter ID
C420020023
Description
This counter counts the maximum number of member subscribers in a closed CSG cell.
Triggers
This counter counts the maximum number of member subscribers in a closed CSG cell
Collection Method
Max
2.2.19 Mean Number of Member Subscribers in Hybrid CSG Cell

Counter ID
C420020024
Description
This counter counts the average number of member subscribers in a hybrid CSG cell.
Triggers
l A member subscriber in a hybrid CSG cell successfully attaches.

l The tracking area of a member is updated for the first time.
l A member subscriber is switched over to this CSG.
2-26

Note:
Non-member subscribers are not counted.
Collection Method
TA
2.2.20 Max Number of Member Subscribers in Hybrid CSG Cell

Counter ID
C420020025
Description
This counter counts the maximum number of member subscribers in a hybrid CSG cell.
Triggers
This counter counts the maximum number of member subscribers in a hybrid CSG cell
Collection Method
Max
2.2.21 Mean Number of Common Subscribers in Hybrid CSG Cell

Counter ID
C420020026
Description
This counter counts the average number of common subscribers in a hybrid CSG cell.
Triggers
l A common subscriber in a hybrid CSG cell successfully attaches.

l The tracking area of a common subscriber is updated for the first time.
l A common subscriber is switched over to this CSG.
2-27

Note:
Non-common subscribers are not counted.
Collection Method
TA
2.2.22 Max Number of Common Subscribers in Hybrid CSG Cell

Counter ID
C420020027
Description
This counter counts the maximum number of common subscribers in a hybrid CSG cell.
Triggers
This counter counts the maximum number of common subscribers in a hybrid CSG cell
Collection Method
Max
2.2.23 Number of CSG Subscribers

Counter ID
C420020028
Description
This counter counts the number of subscribed CSG subscribers.
Triggers
This counter is incremented by one when a CSG subscription message is received.
Collection Method
CC
2-28

2.3 MME Handover Measurement

2.3.1 Times of Intra E-UTRAN Handover Request Without MME
Change Based S1 Interface
Counter ID
C420030013
Description
This counter counts the times of handover requests with MME unchanged internal
E-UTRAN based on the S1 interface.
Triggers
The counter counts after Source eNodeB sends a Handover Reqired message to MME
and the handover flow is successful or fails. "A" as shown in the following figure indicates
the location where the measurement item is triggered in the flow.
Collection Method
CC
2.3.2 Times of Successful Intra E-UTRAN Handover Without MME

Counter ID
C420030014
Description
This counter counts the times of handover successes with MME unchanged internal
E-UTRAN based on the S1 interface.
2-29

Triggers
The counter counts after Target eNodeB sends a Handover Notify message to MME. "A"
as shown in the following figure indicates the location where the measurement item is
triggered in the flow.
Collection Method
CC
2.3.3 Times of Intra E-UTRAN Handover Failure Without MME

Counter ID
C420030015
Description
This counter counts the times of handover failures with MME unchanged internal E-UTRAN
based on the S1 interface.
Triggers
The counter counts after MME sends a Handover Preparation Failure message to Source
eNodeB. "A" as shown in the following figure indicates the location where the measurement
item is triggered in the flow.
2-30

Collection Method
CC
2.3.4 Times of Intra E-UTRAN Path Switch Request Based X2

Interface
Counter ID
C420030016
Description
This counter counts the times that the intra-E-UTRAN path handover based on the X2
interface within a measurement period.
Triggers
The counter counts after Target eNodeB sends a Path Switch Request message to MME
and the handover flow is successful (at point A1) or fails (at point A2). "A1" and "A2" as
shown in the following figure indicate the location where the measurement item is triggered
in the flow.
2-31

Collection Method
CC
2.3.5 Times of Successful Intra E-UTRAN Path Switch Based X2

Interface
Counter ID
C420030017
Description
interface succeeds.
Triggers
The counter counts after MME sends Path Switch Request Ack to Target eNodeB. "A"
2-32

Collection Method
CC
2.3.6 Times of Intra E-UTRAN Path Switch Failure Based X2

Interface
Counter ID
C420030018
Description
interface fails within a measurement period.
Triggers
The counter counts after MME sends Path Switch Request Failure to Target eNodeB. "A"
2-33

Collection Method
CC
2.3.7 Times of Intra E-UTRAN Handover Failure without MME

Change based S1 interface for internal cause
Counter ID
C420030021
Description
This counter counts the number of times of intra–E-UTRAN handover failure without MME
change based on S1 interface because of internal reasons.
Triggers
This counter is incremented when handover flow fails because of internal reasons during
HO, such as internal resource unavailability and DB reading & writing abnormality.
Collection Method
CC
2.3.8 Times of Intra E-UTRAN Path Switch Failure based X2

interface for internal cause
Counter ID
C420030022
2-34

Description
This counter counts the number of times of intra–E-UTRAN path switch failure based on
X2 interface because of internal reasons.
Triggers
This counter is incremented when handover flow fails because of internal reasons during
HO, such as internal resource unavailability, DB reading & writing abnormality.
Collection Method
CC
2.4 MME EMM Common Procedure Measurement

2.4.1 Times of EMM INFORMATION Message Sent by MME
Counter ID
C420140001
Description
This counter counts the times that MME sends EMM INFORMATION message.
Triggers
This counter is incremented by one when MME sends an EMM INFORMATION message.
Collection Method
CC
2.4.2 Times of EMM Status Received

Counter ID
C420140002
Description
This counter counts the number of times that the MME receives an EMM Status message.
Triggers
This counter is incremented when the MME receives an EMM Status message.
2-35

Collection Method
CC
2.4.3 Times of Sending EMM Status

Counter ID
C420140003
Description
This counter counts the number of times that the MME sends an EMM Status messages.
Triggers
This counter is incremented when the MME sends an EMM Status message.
Collection Method
CC
2.4.4 Times of Identity Request

Counter ID
C420140004
Description
This counter counts the number of times that the MME sends an Identity requests.
Triggers
l This counter is incremented by one when the MME sends an Identity request and the
Identity processing succeeds.
l This counter is incremented by one when the MME sends an Identity request and the
Identity processing fails.
Collection Method
CC
2.4.5 Times of success for Identity procedure

Counter ID
C420140005
2-36

Description
This counter counts the number of times of MME successfully sending Identity requests.
Triggers
This counter is incremented when the MME receives an Identity Response message.
Collection Method
CC
2.4.6 Times of Reallocation Request

Counter ID
C420140006
Description
This counter counts the number of times of MME originating GUTI reallocation requests.
Triggers
l This counter is incremented by one when the MME originates GUTI reallocation flow
and reallocation processing succeeds.
l This counter is incremented by one when the MME originates GUTI reallocation flow
and reallocation processing fails.
Collection Method
CC
2.4.7 Times of success for Reallocation procedure

Counter ID
C420140007
Description
This counter counts the number of times of MME successfully originating GUTI reallocation
requests.
Triggers
This counter is incremented when the MME receives a GUTI Reallocation complete
message.
2-37

Collection Method
CC
2.4.8 Times of Authentication Request

Counter ID
C420140008
Description
This counter counts the number of times of MME originating authentication requests.
Triggers
This counter is incremented when the MME originates an authentication request and the
authentication processing succeeds or fails.
Collection Method
CC
2.4.9 Times of success for Authentication procedure

Counter ID
C420140009
Description
This counter counts the number of times of MME successfully originating authentications.
Triggers
This counter is incremented when the MME receives an authentication response
authentication succeeds.
Collection Method
CC
2.4.10 Times of UE Authentication failure

Counter ID
C420140010
2-38

Description
This counter counts the number of times of failed UE authentications originated by MME.
Triggers
This counter is incremented when the MME receives an authentication failure message.
Note:
If it is the failure caused by MAC Failure, the authentication flow re-originated
after obtaining IMSI is considered as the calculation of another authentication
request/success/failure.
Collection Method
CC
2.4.11 Times of NW Authentication Failure

Counter ID
C420140011
Description
This counter counts the number of times of failed network authentication originated by
MME.
Triggers
The counter is incremented by one when the MME receives a response to the UE
authentication and the RES does not match the request.
Collection Method
CC
2.4.12 Times of Security Mode Request

Counter ID
C420140012
Description
This counter counts the number of times of MME originating security mode requests.
2-39

Triggers
l This counter is incremented by one when the MME sends a security mode request
and the security mode processing succeeds.
l This counter is incremented by one when the MME sends a security mode request
and the security mode processing fails.
Collection Method
CC
2.4.13 Times of success for Security Mode procedure

Counter ID
C420140013
Description
This counter counts the number of times of successful security mode originated by MME.
Triggers
This counter is incremented when the MME receives a Security mode complete message.
Collection Method
CC
2.4.14 Times of UE Authentication failure(MAC failure)

Counter ID
C420140014
Description
This counter counts the number of times of failed authentication due to an MAC error.
Triggers
This counter is incremented by one when the MME receives an Authentication Failure
message from the UE, and the cause value in the message is "MAC Failure (20)".
Collection Method
CC
2-40

2.4.15 Times of UE Authentication failure(Synch failure)

Counter ID
C420140015
Description
This counter counts the number of times of failed authentication due to a synchronization
failure.
Triggers
message from the UE, and the cause value in the message is "Synch Failure (21)".
Collection Method
CC
2.4.16 Times of UE Authentication failure(Non-EPS authentication

unacceptable)
Counter ID
C420140016
Description
This counter counts the number of times of failed authentication due to non-EPS
authentication.
Triggers
message from the UE, and the cause value in the message is "Non-EPS authentication
unacceptable (26)".
Collection Method
CC
2-41

2.5 S1AP Measurement

2.5.1 Times of Receiving Management Message
Counter ID
C420170001
Description
This counter counts the number of times that S1AP receives a management message.
Triggers
This counter is incremented by one when S1AP receives a management message.
Collection Method
CC
2.5.2 Times of Discarding Management Message

Counter ID
C420170002
Description
This counter counts the number of times that S1AP discards a management message.
Triggers
This counter is incremented by one when S1AP discards a management message.
Collection Method
CC
2.5.3 Times of Sending Management Message

Counter ID
C420170003
Description
This counter counts the number of times that S1AP sends a management message.
2-42

Triggers
This counter is incremented by one when S1AP sends a management message.
Collection Method
CC
2.5.4 Times of Initial UE Message

Counter ID
C420170004
Description
This counter counts the number of times that S1AP receives an Initial UE message.
Triggers
This counter is incremented by one when S1AP receives an Initial UE message.
Collection Method
CC
2.5.5 Times of Discarding Initial UE Message

Counter ID
C420170005
Description
This counter counts the number of times that S1AP discards an Initial UE message.
Triggers
This counter is incremented by one when S1AP discards an Initial UE message.
Collection Method
CC
2.5.6 Times of UPLINK NAS TRANSPORT Message

Counter ID
C420170006
2-43

Description
This counter counts the number of times that S1AP receives an UPLINK NAS
TRANSPORT message.
Triggers
This counter is incremented by one when S1AP receives an UPLINK NAS TRANSPORT
message.
Collection Method
CC
2.5.7 Times of Discarding UPLINK NAS TRANSPORT Message

Counter ID
C420170007
Description
This counter counts the number of times that S1AP discards an UPLINK NAS
TRANSPORT message.
Triggers
This counter is incremented by one when S1AP discards an UPLINK NAS TRANSPORT
message.
Collection Method
CC
2.5.8 Times of DOWNLINK NAS TRANSPORT Message

Counter ID
C420170008
Description
This counter counts the number of times that S1AP sends an UPLINK NAS TRANSPORT
message.
Triggers
This counter is incremented by one when S1AP sends an UPLINK NAS TRANSPORT
message.
2-44

Collection Method
CC
2.5.9 Times of Sending Initial Context Setup Request Message

Counter ID
C420170009
Description
This counter counts the number of times that S1AP sends an Initial Context Setup Request
message.
Triggers
This counter is incremented by one when S1AP sends an Initial Context Setup Request
message.
Collection Method
CC
2.5.10 Times of Receiving Initial Context Setup Response Message

Counter ID
C420170010
Description
This counter counts the number of times that S1AP receives an Initial Context Setup
Response message.
Triggers
This counter is incremented by one when S1AP receives an Initial Context Setup Response
message.
Collection Method
CC
2.5.11 Times of Sending E-RAB SETUP REQUEST Message

Counter ID
C420170011
2-45

Description
This counter counts the number of times that S1AP sends an E-RAB SETUP REQUEST
message.
Triggers
This counter is incremented by one when S1AP sends an E-RAB SETUP REQUEST
message.
Collection Method
CC
2.5.12 Times of Receiving E-RAB SETUP RESPONSE Message

Counter ID
C420170012
Description
This counter counts the number of times that S1AP receives an E-RAB SETUP
RESPONSE message.
Triggers
This counter is incremented by one when S1AP receives an E-RAB SETUP RESPONSE
message.
Collection Method
CC
2.5.13 Times of Receiving Other Message

Counter ID
C420170013
Description
This counter counts the number of times that S1AP receives a message.
Triggers
This counter is incremented by one when S1AP receives a message.
Collection Method
CC
2-46

2.5.14 Times of Discarding Other Message

Counter ID
C420170014
Description
This counter counts the number of times that S1AP discards a message.
Triggers
This counter is incremented by one when S1AP discards a message.
Collection Method
CC
2.5.15 Times of Sending Other Message

Counter ID
C420170015
Description
This counter counts the number of times that S1AP sends a message.
Triggers
This counter is incremented by one when S1AP sends a message.
Collection Method
CC
2.5.16 Times of Receiving UE CONTEXT RELEASE REQUEST

Message
Counter ID
C420170016
Description
This counter counts the number of times that S1AP receives a UE CONTEXT RELEASE
REQUEST message.
2-47

Triggers
This counter is incremented by one when S1AP receives a UE CONTEXT RELEASE
REQUEST message.
Collection Method
CC
2.5.17 Times of Sending UE CONTEXT RELEASE COMMAND

Message
Counter ID
C420170017
Description
This counter counts the number of times that S1AP sends a UE CONTEXT RELEASE
COMMAND message.
Triggers
This counter is incremented by one when S1AP sends a UE CONTEXT RELEASE
COMMAND message.
Collection Method
CC
2.5.18 Times of Receiving UE CONTEXT RELEASE COMPLETE

Message
Counter ID
C420170018
Description
This counter counts the number of times that S1AP receives a UE CONTEXT RELEASE
COMPLETE message.
Triggers
This counter is incremented by one when S1AP receives a UE CONTEXT RELEASE
COMPLETE message.
2-48

Collection Method
CC
2.6 Paging Measurement of MME

2.6.1 Times of E-UTRAN Paging
Counter ID
C420260001
Description
This counter counts the number of times that the MME originates the E-UTRAN packet
paging.
Triggers
As shown in the following figure, when the MME sends the Paging message to the UE,
calculate the This counter counts the number of times of paging at point A.
Collection Method
CC
2.6.2 Times of Success for E-UTRAN Paging

Counter ID
C420260002
2-49

Description
This counter counts the number of times of successfully receiving the responses from the
UE after the MME originates the E-UTRAN packet paging.
Triggers
As shown in the following figure, when the MME receives the service request message
sent by the UE, and the Service Type = Paging Response, the calculation is made at point
A.
Collection Method
CC
2.7 MME ESM Failure Measurement per NE

2.7.1 Times of PDN Connection Failure (UE Trigger)
Counter ID
C420280001
Description
This counter counts the number of times that PDN connection fails due to UE causes.
Triggers
This counter is incremented by one if MME sends PDN Connectivity Reject to UE due to
UE causes.
The failure causes in the Reject message are other causes except for:
2-50

l Insufficient resources.
l Request rejected by SGW/PGW.
l Network failure
Collection Method
CC
2.7.2 Times of PDN Connection Failure (GW Trigger)

Counter ID
C420280002
Description
This counter counts the number of times that PDN connection fails due to GW causes.
Triggers
GW causes.
The failure causes in the Reject message maybe:
l Insufficient resources
l Request rejected by SGW/PGW.
l Network failure, due to SGW/PGW.
Collection Method
CC
2.7.3 Times of PDN Connection Failure (MME Trigger)

Counter ID
C420280003
Description
This counter counts the number of times that PDN connection fails due to MME causes.
Triggers
causes inside MME.
The failure cause in the Reject message maybe:
l Insufficient resources
2-51

l Network failure, due to MME.
Collection Method
CC
2.7.4 Times of Default Bearer Activation Failure (UE Trigger)

Counter ID
C420280004
Description
This counter counts the number of times that the default bearer fails to be activated due
to UE causes.
Triggers
This counter is incremented by one when the default bearer fails to be activated due to UE.
The failure of default bearer activation is counted as a failure due to UE if MME sends an
Activate EPS bearer context request message to UE because of the following:
l MME receibes the Activate default EPS bearer context reject message from UE.
l Timeout occurs and MME fails to receive the response to the default bearer activation
request from UE.
Collection Method
CC
2.7.5 Times of Default Bearer Activation Failure (eNodeB Trigger)

Counter ID
C420280005
Description
This counter counts the number of times that the dedicated bearer fails to be activated due
to eNodeB causes.
Triggers
This counter is incremented by one when the default bearer fails to be activated due to
eNodeB.
The failure is counted as a failure due to eNodeB when MME sends an initial context setup
request/E-RAB setup request message to eNodeB, during activating the default bearer,
due to the following causes:
2-52

l MME receives the initial context setup failure message from eNodeB.
l MME receives the initial context setup response message from eNodeB, which indi-
cates that the E-RAB corresponding to the default bearer is failed to be set up.
l MME receives the E-RAB setup response message from eNodeB, which indicates
that the E-RAB corresponding to the default bearer is failed to be set up.
l Timeout occurs and MME does not receive a response from eNodeB.
Collection Method
CC
2.7.6 Times of Default Bearer Activation Failure (MME Trigger)

Counter ID
C420280006
Description
to causes inside MME.
Triggers
This counter is incremented by one when the defaut bearer activation fails due to causes
inside MME, after MME sends an Activate EPS bearer context request message to UE
and before SGW returns a Modify Bearer Response message.
Collection Method
CC
2.7.7 Times of Default Bearer Activation Failure (GW Trigger)

Counter ID
C420280007
Description
to SGW/PGW causes.
Triggers
This counter is incremented by one when the default bearer fails to be activated due to
SGW/PGW.
2-53

The failure is counted as a failure due to GW when a Modify Bearer Request message is
sent to SGW, during activating the default bearer, due to the following causes:
l MME receives the Modify Bearer Response message from SGW, with the cause value
being not request accepted.
l Timeout occurs and MME does not receive the response from SGW/PGW.
Collection Method
CC
2.7.8 Times of Dedicated Bearer Activation Failure (UE Trigger)

Counter ID
C420280008
Description
to UE causes.
Triggers
This counter is incremented by one when the dedicated bearer fails to be activated due to
UE.
The failure of dedicated bearer activation is counted as a failure due to UE if MME sends the
Activate dedicated EPS bearer context request message to UE because of the following:
l MME receives the Activate dedicated EPS bearer context reject message from UE.
l Timeout occurs and MME fails to receive the response to the dedication bearer
activation request.
Collection Method
CC
2.7.9 Times of Dedicated Bearer Activation Failure (eNodeB Trigger)

Counter ID
C420280009
Description
to eNodeB causes.
2-54

Triggers
This counter is incremented by one when the dedicated bearer fails to be activated due to
eNodeB.
The failure is counted as a failure due to eNodeB when MME sends an E-RAB setup
request message to eNodeB, during activating the dedicated bearer, due to the following
causes:
l MME receives the E-RAB setup response message from eNodeB, which indicates
that the E-RAB corresponding to the dedicated bearer is failed to be set up.
l Timeout occurs and MME does not receive the response from eNodeB.
Collection Method
CC
2.7.10 Times of Bearer Modification Failure (UE Trigger)

Counter ID
C420280010
Description
This counter counts the number of times that bearer modification fails due to UE.
Triggers
This counter is incremented by one when bearer modification fails due to UE.
The failure of dedicated bearer activation is counted as a failure due to UE if MME sends
the Modify EPS bearer context request message to UE because of the following:
l MME receives the Activate dedicated EPS bearer context reject message from UE.
l Timeout occurs and MME does not receive the response from UE.
Collection Method
CC
2.7.11 Times of Bearer Modification Failure (eNodeB Trigger)

Counter ID
C420280011
Description
This counter counts the number of times that bearer modification fails due to eNodeB.
2-55

Triggers
This counter is incremented by one when bearer modification fails due to eNodeB.
The failure is counted as a failure due to the eNodeB when the MME sends an E-RAB
modify request message to the eNodeB when a bearer fails to be modified due to the
following causes:
l The MME receives the E-RAB modify response message from the eNodeB, which
indicates that the modification of the E-RAB corresponding to the dedicated bearer
fails.
l A timeout occurs and the MME does not receive a response from the eNodeB.
Collection Method
CC
2.7.12 Times of Failed UE Requested Bearer Resource

Allocation(UE Trigger)
Counter ID
C420280012
Description
This counter counts the number of times that UE fails to request bearer resources allocation
due to UE causes.
Triggers
This counter is incremented by one if MME sends Bearer Resource Allocation Reject to
UE due to UE causes.
l Request rejected by SGW or PGW.
l Network failure.
Collection Method
CC

(MME Trigger)
Counter ID
C420280013
2-56

Description
due to causes inside MME.
Triggers
UE due to causes inside MME.
The failure cause in the Reject message may be due to the following:
l Network failure, due to MME itself.
Collection Method
CC

(GW Trigger)
Counter ID
C420280014
Description
due to SGW or PGW causes.
Triggers
UE due to SGW or PGW causes.
The failure causes in the Reject message may be due to the following:
l Network failure, due to SGW or PGW.
Collection Method
CC
2-57


(UE Trigger)
Counter ID
C420280015
Description
This counter counts the number of times that UE fails to request bearer resources
modification due to UE causes.
Triggers
This counter is incremented by one if MME sends Bearer Resource Modification Reject to
l Network failure.
Collection Method
CC

(MME Trigger)
Counter ID
C420280016
Description
modification due to causes inside MME.
Triggers
UE due to causes inside MME.
The failure cause in the Reject message may be due to the following:
l Network failure, due to MME itself.
2-58

Collection Method
CC

(GW Trigger)
Counter ID
C420280017
Description
modification due to SGW or PGW.
Triggers
UE due to SGW or PGW.
The failure causes in the Reject message may be due to the following:
l Network failure, due to SGW/PGW.
Collection Method
CC
2.8 MME EMM Basic Procedure Measurement

2.8.1 Times of EPS Attach Request
Counter ID
C420290001
Description
This counter counts the number of requests for attach of the EPS attach type.
Triggers
When MME succeeds or fails in processing a received Attach Request with EPS attach
type IE being EPS attach.
2-59

Collection Method
CC
2.8.2 Times of Success for EPS Attach Procedure

Counter ID
C420290002
Description
This counter counts the number of times that an attach of the EPS attach type succeeds.
Triggers
When EMM receives an Attach Accept message from UE during the attach flow of the EPS
attach type.
Collection Method
CC
2.8.3 Times of Intra-MME TAU Attempt (SGW not Change)

Counter ID
C420290005
Description
This counter counts the times of trace area update requests with MME and SGW
unchanged.
Triggers
This counter is incremented by one when the TAU flow succeeds or fails after EMM
receives a TAU Request message (with both MME and SGW unchanged) from UE.
Collection Method
CC
2.8.4 Times of Intra-MME TAU Success (SGW not Change)

Counter ID
C420290006
2-60

Description
This counter counts the times that the trace area successfully updates with MME and SGW
unchanged.
Triggers
This counter is incremented by one when EMM receives a TA Update Accept message
from UE during the TAU flow with both MME and SGW unchanged.
Collection Method
CC
2.8.5 Times of Intra-MME TAU Attempt (SGW Change)

Counter ID
C420290007
Description
This counter counts the times of trace area update requests with MME unchanged and
SGW changed.
Triggers
This counter is incremented by one when the TAU flow succeeds or fails after EMM
receives a TAU Request message (with MME unchanged and SGW changed) from UE.
Collection Method
CC
2.8.6 Times of Intra-MME TAU Success (SGW Change)

Counter ID
C420290008
Description
This counter counts the times of times that the trace area successfully updates with MME
and SGW changed.
Triggers
This counter is incremented by one when EMM receives a TA Update Accept message
from UE during the TAU flow with both MME and SGW changed.
2-61

Collection Method
CC
2.8.7 Times of EPS Detach Request from UE

Counter ID
C420290013
Description
This counter counts the number of times that EPS detach is originated by UE.
Triggers
This counter is incremented by one if the detach flow succeeds or fails after EMM receives
a Detach Request message (with Detach type IE being EPS detach) from UE.
Collection Method
CC
2.8.8 Times of Success for EPS Detach Procedure from UE

Counter ID
C420290014
Description
This counter counts the number of times that EPS detach originated by UE succeeds.
Triggers
This counter is incremented by one after EMM receives a Detach Request message (with
Detach type IE being EPS detach) from UE and returns Detach Accept to UE upon poweron
or receives Detach Request upon poweroff.
Collection Method
CC
2.8.9 Times of EPS Detach Request from MME

Counter ID
C420290019
2-62

Description
This counter counts the number of detach requests originated by MME.
Triggers
This counter is incremented by one if the detach flow succeeds or fails after MME sends
Detach Request to UE with reattach needed or unneeded after detach.
Collection Method
CC
2.8.10 Times of Success for EPS Detach Procedure from MME

Counter ID
C420290020
Description
This counter calculates the number of successful detaches originated by MME.
Triggers
When EMM receives Detach Accept returned by UE if reattach is needed or unneeded
after detach.
Collection Method
CC
2.8.11 Times of Detach Request from HSS

Counter ID
C420290023
Description
This counter counts the number of detach requests originated by HSS.
Triggers
When the detach flow succeeds or fails after EMM sends Detach Request to UE
responding to the trigger by HSS.
Collection Method
CC
2-63

2.8.12 Times of Successful Detach Procedure from HSS

Counter ID
C420290024
Description
This counter calculates the times of successful detaches originated by HSS.
Triggers
When EMM receives Detach Accept from UE.
Collection Method
CC
2.8.13 Times of Service Request

Counter ID
C420290025
Description
This counter counts the times that a terminal originates a service request.
Triggers
This counter is incremented by one after EMM receives a Service Request message and
processes the request (successful or failed).
Collection Method
CC
2.8.14 Times of Success for Service Request Procedure

Counter ID
C420290026
Description
This counter counts the times that a terminal successfully originates a service request.
Triggers
This counter is incremented by one when S1AP:Initial Context Setup Request is sent.
2-64

Collection Method
CC
2.8.15 Duration of EPS Attach Procedure (ms)

Counter ID
C420290027
Description
This counter counts the duration for EPS user attach.
Triggers
Time period from the time when a UE receives an attach request message of the EPS
attache type (ATTACH REQUEST) to the time when the MME returns an attach success
message (ATTACH ACCEPT) within a measurement period (unit: mm).
Collection Method
CC
2.8.16 Times of Attach Request From Closed CSG Cell

Counter ID
C420290033
Description
This counter counts the number of Attach Request messages received from a closed CSG
cell.
Triggers
This counter is incremented by one when attachment succeeds or fails after the MME
receives an Attach Request message for a subscriber to attach from a closed CSG cell.
Collection Method
CC
2.8.17 Times of Attach Request From Hybrid CSG Cell

Counter ID
C420290034
2-65

Description
This counter counts the number of Attach Request messages received from a hybrid CSG
cell.
Triggers
This counter is incremented by one when attachment succeeds or fails after the MME
receives an Attach Request message for a subscriber to attach from a hybrid CSG cell.
Collection Method
CC
2.8.18 Times of Success for Attach Procedure From Closed CSG

Cell
Counter ID
C420290035
Description
This counter counts the number of times that a subscriber successfully attaches in a closed
CSG cell.
Triggers
This counter is incremented by one after the eNodeB sends an Attach Accept message to
a UE attaching from a closed CSG cell.
Collection Method
CC
2.8.19 Times of Success for Attach Procedure From Hybrid CSG

Cell
Counter ID
C420290036
Description
This counter counts the number of times that a subscriber successfully attaches in a hybrid
CSG cell.
2-66

Triggers
This counter is incremented by one after the eNodeB sends an Attach Accept message to
a UE attaching from a hybrid CSG cell.
Collection Method
CC
2.8.20 Times of TAU Attempt From Closed CSG Cell

Counter ID
C420290037
Description
This counter counts the number of received tracking-area update requests from a closed
CSG cell.
Triggers
This counter is incremented by one when a tracking area update flow succeeds or fails
after the EMM receives a TAU Request sent by a UE from a closed CSG cell.
Collection Method
CC
2.8.21 Times of TAU Success From Closed CSG Cell

Counter ID
C420290038
Description
This counter counts the number of times that a tracking area successfully updates in a
closed CSG cell.
Triggers
This counter is incremented by one after the eNodeB sends a TA Update Accept message
to a UE in a closed CSG cell.
Collection Method
CC
2-67

2.8.22 Times of TAU Attempt From Hybrid CSG Cell

Counter ID
C420290039
Description
This counter counts the number of received tracking-area update requests from a hybrid
CSG cell.
Triggers
This counter is incremented by one when a tracking area update flow succeeds or fails
after the EMM receives a TAU Request sent by a UE from a hybrid CSG cell.
Collection Method
CC
2.8.23 Times of TAU Success From Hybrid CSG Cell

Counter ID
C420290040
Description
This counter counts the number of times that a tracking area successfully updates in a
hybrid CSG cell.
Triggers
This counter is incremented by one after the eNodeB sends a TA Update Accept message
to a UE in a hybrid CSG cell.
Collection Method
CC
2.8.24 Times of Service Request From Closed CSG Cell

Counter ID
C420290041
Description
This counter counts the number of service requests initiated by a subscriber in a closed
CSG cell.
2-68

Triggers
This counter is incremented by one when a service request is handled successfully or
unsuccessfully after the EMM receives a Service Request message from a subscriber in
a closed CSG cell.
Collection Method
CC
2.8.25 Times of Success for Service Request Procedure From

Closed CSG Cell
Counter ID
C420290042
Description
This counter counts the number of service requests successfully initiated by a subscriber
in a closed CSG cell.
Triggers
This counter is incremented by one when a UE in a closed CSG cell sends an Initial Context
Setup Request to the eNodB.
Collection Method
CC
2.8.26 Times of Service Request From Hybrid CSG Cell

Counter ID
C420290043
Description
This counter counts the number of service requests initiated by a UE in a hybrid CSG cell.
Triggers
This counter is incremented by one when a service request is handled successfully or
unsuccessfully after the EMM receives a Service Request message from a UE in a hybrid
CSG cell.
Collection Method
CC
2-69

2.8.27 Times of Success for Service Request Procedure From

Hybrid CSG Cell
Counter ID
C420290044
Description
This counter counts the number of service requests successfully initiated by a UE in a
hybrid CSG cell.
Triggers
This counter is incremented by one when a UE in a hybrid CSG cell sends an Initial Context
Setup Request to the eNodB.
Collection Method
CC
2.9 MME EMM Procedure Failure based on NE

Measurement
2.9.1 Times of EPS Attach Failure (UE Trigger)
Counter ID
C420300001
Description
This counter counts the times that EPS fails to attach (due to UE causes).
Triggers
During the attach flow of the EPS attach type, EMM sends an Attach reject message to
The causes for Attach reject include the failures except network failures and ESM failures
(excluding ESM failures due to subscribers).
Collection Method
CC
2-70

2.9.2 Times of EPS Attach Failure (MME Trigger)

Counter ID
C420300002
Description
This counter counts the times that EPS fails to attach (due to MME causes).
Triggers
During the attach flow of the EPS attach type, EMM sends an Attach reject message to UE
because of failures inside MME, for example, resources cannot be obtained or resources
are abnormal.
The causes for Attach reject include network failure, ESM failure or conflict due to MME.
The causes corresponding to the ESM are as follows:
l Network failure.
l Resources are insufficient.
Collection Method
CC
2.9.3 Times of EPS Attach Failure (GW Trigger)

Counter ID
C420300003
Description
This counter counts the times that EPS fails to attach (due to GW causes).
Triggers
UE because the gateway returns failure messages or returns no responses.
The cause for Attach reject is ESM failure and this failure is caused due to the MME.
The corresponding causes are as follows:
l Network failure.
l Resources are insufficient.
l SGW/PGW denies the request.
Collection Method
CC
2-71

2.9.4 Times of EPS Attach Failure (HSS Trigger)

Counter ID
C420300004
Description
This counter counts the times that EPS fails to attach (due to HSS causes).
Triggers
UE because HSS returns failure messages or returns no responses. The corresponding
Attach reject cause is network failure.
Note:
Failures related to HSS subscription information are counted as UE failures.
Collection Method
CC
2.9.5 Times of EPS Attach Failure (EIR Trigger)

Counter ID
C420300005
Description
This counter counts the times that EPS fails to attach (due to EIR causes).
Triggers
UE because EIR does not respond.
Note:
Failures because EIR determines the equipment as invalid are counted as UE failures.
2-72

Collection Method
CC
2.9.6 Times of Intra-MME TAU Failure with SGW not Change (UE
Trigger)
Counter ID
C420300011
Description
This counter calculates the times that TAU with intra-office SGW unchanged fails (due to
UE).
Triggers
During the TAU flow with intra-office SGW unchanged, EMM sends TAU reject to UE due
to UE causes, including:
l UE rejects.
l UE has no response.
l Subscription
The causes for TAU reject include the failures except network failures and ESM failures
Collection Method
CC
2.9.7 Times of Intra-MME TAU Failure with SGW not Change (MME
Trigger)
Counter ID
C420300012
Description
MME).
Triggers
During the TAU flow with intra-office SGW unchanged, EMM sends a TAU reject message
to UE because of failures inside MME, for example, resources cannot be obtained or
resources are abnormal.
2-73

The causes for TAU reject may be network failure, conflicts or ESM failure due to MME.
Collection Method
CC
2.9.8 Times of Intra-MME TAU Failure with SGW not Change (GW
Trigger)
Counter ID
C420300013
Description
GW).
Triggers
During the TAU flow with intra-office SGW unchanged, EMM sends TAU reject to UE
because the gateway returns a failure message or no response.
The causes for TAU reject may be network failure or ESM failure due to GW.
Collection Method
CC
2.9.9 Times of Intra-MME TAU Failure with SGW not Change (HSS
Trigger)
Counter ID
C420300014
Description
This counter counts the times that TAU with intra-office SGW unchanged fails (due to HSS).
Triggers
During the TAU flow with intra-office SGW unchanged, EMM sends TAU reject to UE
because HSS returns a failure message or no response.
The cause for TAU reject may be network failure due to HSS.
Collection Method
CC
2-74

2.9.10 Times of Service Request Failure (UE Trigger)

Counter ID
C420300029
Description
This counter calculates the times that a service request fails due to UE.
Triggers
During the service request flow, EMM sends a service reject message to UE due to UE
causes including:
l UE rejects.
l UE has no response.
l Subscription
The causes for service reject include the failures except network failures and ESM failures
Collection Method
CC
2.9.11 Times of Service Request Failure (MME Trigger)

Counter ID
C420300030
Description
This counter calculates the times that a service request fails due to MME.
Triggers
During the service request flow, EMM sends a service request reject message to UE
because of failures inside MME, for example, resources cannot be obtained or resources
are abnormal.
The service reject causes may be network failure, conflict, or ESM failure due to MME.
Collection Method
CC
2-75

2.10 MME S1 Overload-Control Measurement

2.10.1 Number of Rejected S1 Attach Request messages for
overload-control
Counter ID
C420310001
Description
This counter counts the number of attachment request rejected because of load control in
MME.
Triggers
This counter is incremented when the MME rejects an attachment request because of load
control after it receives this attachment request.
Collection Method
CC
2.10.2 Number of Discarded S1 Attach Request messages for

overload-control
Counter ID
C420310002
Description
This counter counts the number of attachment request discarded because of load control
in MME.
Triggers
This counter is incremented when the MME discards an attachment request because of
load control after it receives this attachment request.
Collection Method
CC
2-76

2.10.3 Number of Rejected S1 Service Request messages for

overload-control
Counter ID
C420310003
Description
This counter counts the number of service request rejected because load control in MME.
Triggers
This counter is incremented when the MME rejects a service request because of load
control after it receives this service request.
Collection Method
CC
2.10.4 Number of Discarded S1 Service Request messages for

overload-control
Counter ID
C420310004
Description
This counter counts the number of service request discarded by load control in MME.
Triggers
This counter is incremented when the MME discards a service request because of load
control after it receives this service request.
Collection Method
CC
2.10.5 Number of Rejected S1 TAU Request messages for

overload-control
Counter ID
C420310005
2-77

Description
This counter counts the number of TAU request rejected because of load control in MME.
Triggers
This counter is incremented when the MME rejects a TAU request because of load control
after it receives this TAU request.
Collection Method
CC
2.10.6 Number of Discarded S1 TAU Request messages for

overload-control
Counter ID
C420310006
Description
This counter counts the number of TAU request discarded because of load control in MME.
Triggers
This counter is incremented when the MME discards a TAU request because of load control
after it receives this TAU request.
Collection Method
CC
2.10.7 Number of Rejected S1 HO Request messages for

overload-control
Counter ID
C420310007
Description
This counter calculates the number of HO request rejected because of load control in MME.
Triggers
This counter increments when the MME rejects an HO request because of load control
after it receives an HO request.
2-78

Collection Method
CC
2.10.8 Number of Discarded S1 HO Request messages for

overload-control
Counter ID
C420310008
Description
This counter calculates the number of HO request discarded because of load control in
MME.
Triggers
This counter increments when the MME discards an HO request because of load control
after it receives this HO request.
Collection Method
CC
2.10.9 Number of Rejected S1 PDN Connectivity Request messages

for overload-control
Counter ID
C420310009
Description
This counter counts the number of PDN connectivity request rejected because of load
control in MME.
Triggers
This counter is incremented when the MME rejects a PDN connectivity request because
of load control after it receives this PDN connectivity request.
Collection Method
CC
2-79

2.10.10 Number of Discarded S1 PDN Connectivity Request

messages for overload-control
Counter ID
C420310010
Description
This counter counts the number of PDN connectivity request discarded because of load
control in MME.
Triggers
This counter is incremented when the MME discards a PDN connectivity request because
of load control after it receives this PDN connectivity request.
Collection Method
CC
2.10.11 Number of Rejected S1 Bearer Resource Modify Request

Counter ID
C420310011
Description
This counter counts the number of bearer resource modifying request rejected because of
load control in MME.
Triggers
This counter is incremented when the MME rejects a bearer resource modifying request
because of load control after it receives this bearer resource modifying request.
Collection Method
CC
2.10.12 Number of Discarded S1 Bearer Resource Modify Request

Counter ID
C420310012
2-80

Description
This counter counts the number of bearer resource modifying request discarded because
of load control in MME.
Triggers
This counter is incremented when the MME discards a bearer resource modifying request
because of load control after it receives this bearer resource modifying request.
Collection Method
CC
2.10.13 Number of Discarded S1 paging messages for

overload-control
Counter ID
C420310013
Description
This counter counts the number of paging messages discarded because of load control in
MME.
Triggers
This counter is incremented when the MME discards a paging request because of load
control after it receives this message.
Collection Method
CC
2.10.14 Number of Discarded S1 downlink Bearer Modify messages

for overload-control
Counter ID
C420310014
Description
This counter calculates the number of downlink bearer modifying messages discarded
because of load control in MME.
2-81

Triggers
This counter increments when the MME discards a downlink bearer modifying request
because of load control after it receives this request.
Collection Method
CC
2.10.15 Number of Rejected S1 Bearer Resource Allocation

Request messages for overload-control
Counter ID
C420310015
Description
This counter counts the number of rejected Bearer Resource Allocation Request messages
received by the MME from the Enodeb due to overload control.
Triggers
This counter is incremented by one when a Bearer Resource Allocation Request message
received from the MME to the EnodeB is rejected due to overload control.
Collection Method
CC
2.10.16 Number of Discarded S1 Bearer Resource Allocation

Request messages for overload-control
Counter ID
C420310016
Description
This counter counts the number of discarded Bearer Resource Allocation Request
messages received by the MME from the Enodeb due to overload control.
Triggers
This counter is incremented by one when a Bearer Resource Allocation Request message
received from the MME to the EnodeB is discarded due to overload control.
2-82

Collection Method
CC
2.11 MME TAU Failure based on Failure Cause

Measurement
2.11.1 Times of Intra-MME TAU with SGW not Change Failure (IMSI
unknown in HSS)
Counter ID
C420340001
Description
Times of Intra-MME TAU with SGW not Change Failure (IMSI unknown in HSS)
Triggers
This counter is incremented by one when the EMM sends a TAU rejection message (with
the failure cause being "IMSI unknown in HSS") to the UE in the TAU flow with unchanged
intra-office SGW.
Collection Method
CC
2.11.2 Times of Intra-MME TAU with SGW not Change Failure

(Illegal UE)
Counter ID
C420340002
Description
Times of Intra-MME TAU with SGW not Change Failure (Illegal UE)
Triggers
the failure cause being "Illegal UE") to the UE in the TAU flow with unchanged intra-office
SGW.
2-83

Collection Method
CC

(Illegal ME)
Counter ID
C420340003
Description
Times of Intra-MME TAU with SGW not Change Failure (Illegal ME)
Triggers
the failure cause being "Illegal ME") to the UE in the TAU flow with unchanged intra-office
SGW.
Collection Method
CC
2.11.4 Times of Intra-MME TAU with SGW not Change Failure (EPS
services not allowed)
Counter ID
C420340004
Description
Times of Intra-MME TAU with SGW not Change Failure (EPS services not allowed)
Triggers
This counter is incremented by one when the EMM sends a TAU rejection message
(with the failure cause being "EPS services not allowed") to the UE in the TAU flow with
unchanged intra-office SGW.
Collection Method
CC
2-84

2.11.5 Times of Intra-MME TAU with SGW not Change Failure (EPS
services and non-EPS services not allowed)
Counter ID
C420340005
Description
Times of Intra-MME TAU with SGW not Change Failure (EPS services and non-EPS
Triggers
the failure cause being "EPS services and non-EPS services not allowed") to the UE in
the TAU flow with unchanged intra-office SGW.
Collection Method
CC
2.11.6 Times of Intra-MME TAU with SGW not Change Failure (UE
identity cannot be derived by the network)
Counter ID
C420340006
Description
Times of Intra-MME TAU with SGW not Change Failure (UE identity cannot be derived by
the network)
Triggers
the failure cause being "UE identity cannot be derived by the network") to the UE in the
TAU flow with unchanged intra-office SGW.
Collection Method
CC
2-85


(Implicitly detached)
Counter ID
C420340007
Description
Times of Intra-MME TAU with SGW not Change Failure (Implicitly detached)
Triggers
the failure cause being "Implicitly detached") to the UE in the TAU flow with unchanged
intra-office SGW.
Collection Method
CC

(PLMN not allowed)
Counter ID
C420340008
Description
Times of Intra-MME TAU with SGW not Change Failure (PLMN not allowed)
Triggers
the failure cause being "PLMN not allowed") to the UE in the TAU flow with unchanged
intra-office SGW.
Collection Method
CC

(Tracking area not allowed)
Counter ID
C420340009
2-86

Description
Times of Intra-MME TAU with SGW not Change Failure (Tracking area not allowed)
Triggers
(with the failure cause being "Tracking area not allowed") to the UE in the TAU flow with
Collection Method
CC

(Roaming not allowed in this tracking area)
Counter ID
C420340010
Description
Times of Intra-MME TAU with SGW not Change Failure (Roaming not allowed in this
tracking area)
Triggers
the failure cause being "Roaming not allowed in this tracking area") to the UE in the TAU
flow with unchanged intra-office SGW.
Collection Method
CC

(EPS services not allowed in this PLMN)
Counter ID
C420340011
Description
Times of Intra-MME TAU with SGW not Change Failure (EPS services not allowed in this
PLMN)
2-87

Triggers
the failure cause being "EPS services not allowed in this PLMN") to the UE in the TAU flow
with unchanged intra-office SGW.
Collection Method
CC
2.11.12 Times of Intra-MME TAU with SGW not Change Failure (No
suitable cells in tracking area)
Counter ID
C420340012
Description
Times of Intra-MME TAU with SGW not Change Failure (No suitable cells in tracking area)
Triggers
the failure cause being "No suitable cells in tracking area") to the UE in the TAU flow with
Collection Method
CC

(MSC temporarily not reachable)
Counter ID
C420340013
Description
Times of Intra-MME TAU with SGW not Change Failure (MSC temporarily not reachable)
Triggers
the failure cause being "MSC temporarily not reachable") to the UE in the TAU flow with
2-88

Collection Method
CC
2.11.14 Times of Intra-MME TAU Failure with SGW not Change

(Network failure)
Counter ID
C420340014
Description
Times of Intra-MME TAU Failure with SGW not Change (Network failure)
Triggers
(with the failure cause being "Network failure") to the UE in the TAU flow with unchanged
intra-office SGW.
Collection Method
CC
2.11.15 Times of Intra-MME TAU with SGW not Change Failure (CS
domain not available)
Counter ID
C420340015
Description
Times of Intra-MME TAU with SGW not Change Failure (CS domain not available)
Triggers
(with the failure cause being "CS domain not available") to the UE in the TAU flow with
Collection Method
CC
2-89


(ESM failure)
Counter ID
C420340016
Description
Times of Intra-MME TAU with SGW not Change Failure (ESM failure)
Triggers
the failure cause being "ESM failure") to the UE in the TAU flow with unchanged intra-office
SGW.
Collection Method
CC

(Congestion)
Counter ID
C420340017
Description
Times of Intra-MME TAU with SGW not Change Failure (Congestion)
Triggers
the failure cause being "Congestion") to the UE in the TAU flow with unchanged intra-office
SGW.
Collection Method
CC
2.11.18 Times of Intra-MME TAU with SGW not Change Failure (Not
authorized for this CSG)
Counter ID
C420340018
2-90

Description
Times of Intra-MME TAU with SGW not Change Failure (Not authorized for this CSG)
Triggers
the failure cause being "Not authorized for this CSG") to the UE in the TAU flow with
Collection Method
CC
2.11.19 Times of Intra-MME TAU with SGW not Change Failure (No
EPS bearer context activated)
Counter ID
C420340019
Description
Times of Intra-MME TAU with SGW not Change Failure (No EPS bearer context activated)
Triggers
the failure cause being "No EPS bearer context activated") to the UE in the TAU flow with
Collection Method
CC

(invalid mandatory information element error)
Counter ID
C420340020
Description
Times of Intra-MME TAU with SGW not Change Failure (invalid mandatory information
element error)
2-91

Triggers
the failure cause being "invalid mandatory information element error") to the UE in the TAU
flow with unchanged intra-office SGW.
Collection Method
CC

(Message type non-existent or not implemented)
Counter ID
C420340021
Description
Times of Intra-MME TAU with SGW not Change Failure (Message type non-existent or not
implemented)
Triggers
the failure cause being "Message type non-existent or not implemented") to the UE in the
Collection Method
CC

(information element non-existent or not implemented)
Counter ID
C420340022
Description
Times of Intra-MME TAU with SGW not Change Failure (information element non-existent
or not implemented)
Triggers
the failure cause being "information element non-existent or not implemented") to the UE
in the TAU flow with unchanged intra-office SGW.
2-92

Collection Method
CC

(conditional IE error)
Counter ID
C420340023
Description
Times of Intra-MME TAU with SGW not Change Failure (conditional IE error)
Triggers
the failure cause being "conditional IE error") to the UE in the TAU flow with unchanged
intra-office SGW.
Collection Method
CC

(protocol error, unspecified)
Counter ID
C420340024
Description
Times of Intra-MME TAU with SGW not Change Failure (protocol error, unspecified
Triggers
(with the failure cause being "protocol error, unspecified") to the UE in the TAU flow with
Collection Method
CC
2-93


(Other causes)
Counter ID
C420340025
Description
Times of Intra-MME TAU with SGW not Change Failure (Other causes)
Triggers
a failure cause in other measurement items of this measurement type) to the UE in the
Collection Method
CC
2.12 MME Service Request Failure based on Failure

Cause Measurement
2.12.1 Times of Service Request failure (Illegal UE)
Counter ID
C420350001
Description
Times of Service Request failure (Illegal UE)
Triggers
This counter is incremented by one when the EMM sends a service request rejection
message (with the failure cause being "Illegal UE") to the UE in the service request flow.
Collection Method
CC
2-94

2.12.2 Times of Service Request failure (Illegal ME)

Counter ID
C420350002
Description
Times of Service Request failure (Illegal ME)
Triggers
message (with the failure cause being "Illegal ME") to the UE in the service request flow.
Collection Method
CC
2.12.3 Times of Service Request failure (EPS services not allowed)

Counter ID
C420350003
Description
Times of Service Request failure (EPS services not allowed)
Triggers
message (with the failure cause being "EPS services not allowed") to the UE in the service
request flow.
Collection Method
CC
2.12.4 Times of Service Request failure (EPS services and non-EPS

Counter ID
C420350004
Description
Times of Service Request failure (EPS services and non-EPS services not allowed)
2-95

Triggers
message (with the failure cause being "EPS services and non-EPS services not allowed")
to the UE in the service request flow.
Collection Method
CC
2.12.5 Times of Service Request failure (UE identity cannot be

derived by the network)
Counter ID
C420350005
Description
Times of Service Request failure (UE identity cannot be derived by the network)
Triggers
message (with the failure cause being "UE identity cannot be derived by the network")
Collection Method
CC
2.12.6 Times of Service Request failure (Implicit detached)

Counter ID
C420350006
Description
Times of Service Request failure (Implicit detached)
Triggers
message (with the failure cause being "Implicit detached") to the UE in the service request
flow.
Collection Method
CC
2-96

2.12.7 Times of Service Request failure (PLMN not allowed)

Counter ID
C420350007
Description
Times of Service Request failure (PLMN not allowed)
Triggers
message (with the failure cause being "PLMN not allowed") to the UE in the service request
flow.
Collection Method
CC
2.12.8 Times of Service Request failure (Tracking Area not allowed)

Counter ID
C420350008
Description
Times of Service Request failure (Tracking Area not allowed)
Triggers
message (with the failure cause being "Tracking Area not allowed") to the UE in the service
request flow.
Collection Method
CC
2.12.9 Times of Service Request failure (Roaming not allowed in

this tracking area)
Counter ID
C420350009
2-97

Description
Times of Service Request failure (Roaming not allowed in this tracking area)
Triggers
message (with the failure cause being "Roaming not allowed in this tracking area") to the
UE in the service request flow.
Collection Method
CC
2.12.10 Times of Service Request failure (EPS services not allowed

in this PLMN)
Counter ID
C420350010
Description
Times of Service Request failure (EPS services not allowed in this PLMN)
Triggers
message (with the failure cause being "EPS services not allowed in this PLMN") to the
UE in the service request flow.
Collection Method
CC
2.12.11 Times of Service Request failure (No Suitable Cells In

tracking area)
Counter ID
C420350011
Description
Times of Service Request failure (No Suitable Cells In tracking area)
2-98

Triggers
message (with the failure cause being "No Suitable Cells In tracking area") to the UE in
the service request flow.
Collection Method
CC
2.12.12 Times of Service Request failure (Network failure)

Counter ID
C420350012
Description
Times of Service Request failure (Network failure)
Triggers
message (with the failure cause being "Network failure") to the UE in the service request
flow.
Collection Method
CC
2.12.13 Times of Service Request failure (CS domain not available)

Counter ID
C420350013
Description
Times of Service Request failure (CS domain not available)
Triggers
message (with the failure cause being "CS domain not available") to the UE in the service
request flow.
Collection Method
CC
2-99

2.12.14 Times of Service Request failure (Congestion)

Counter ID
C420350014
Description
Times of Service Request failure (Congestion)
Triggers
message (with the failure cause being "Congestion") to the UE in the service request flow.
Collection Method
CC
2.12.15 Times of Service Request failure (Not authorized for this

CSG)
Counter ID
C420350015
Description
Times of Service Request failure (Not authorized for this CSG)
Triggers
message (with the failure cause being "Not authorized for this CSG") to the UE in the
service request flow.
Collection Method
CC
2.12.16 Times of Service Request failure (CS domain temporarily

not available)
Counter ID
C420350016
2-100

Description
Times of Service Request failure (CS domain temporarily not available)
Triggers
message (with the failure cause being "CS domain temporarily not available") to the UE in
the service request flow.
Collection Method
CC
2.12.17 Times of Service Request failure (Invalid mandatory

information)
Counter ID
C420350017
Description
Times of Service Request failure (Invalid mandatory information)
Triggers
message (with the failure cause being "Invalid mandatory information") to the UE in the
service request flow.
Collection Method
CC
2.12.18 Times of Service Request failure (Message type

non-existent or not implemented)
Counter ID
C420350018
Description
Times of Service Request failure (Message type non-existent or not implemented)
2-101

Triggers
message (with the failure cause being "Message type non-existent or not implemented")
Collection Method
CC
2.12.19 Times of Service Request failure (Information element

Counter ID
C420350019
Description
Times of Service Request failure (Information element non-existent or not implemented)
Triggers
message (with the failure cause being "Information element non-existent or not
implemented") to the UE in the service request flow.
Collection Method
CC
2.12.20 Times of Service Request failure (Conditional IE error)

Counter ID
C420350020
Description
Times of Service Request failure (Conditional IE error)
Triggers
message (with the failure cause being "Conditional IE error") to the UE in the service
request flow.
Collection Method
CC
2-102

2.12.21 Times of Service Request failure (Protocol error,unspecified)

Counter ID
C420350021
Description
Times of Service Request failure (Protocol error,unspecified)
Triggers
message (with the failure cause being "Protocol error, unspecified") to the UE in the service
request flow.
Collection Method
CC
2.12.22 Times of Service Request failure (Unknown cause)

Counter ID
C420350022
Description
Times of Service Request failure (Unknown cause)
Triggers
message (with a failure cause of other measurement items in this measurement type)
Collection Method
CC
2.13 MME EMM Messages Abnormal Measurement

2.13.1 Times of Receiving Attach Request of Procedure Conflict
Counter ID
C420360001
2-103

Description
Times of Receiving Attach Request of Procedure Conflict
Triggers
This counter is incremented by one when an Attach request is received but is then
discarded due to procedure conflict, or when an ongoing Attach flow is terminated
because other messages are received.
Collection Method
CC
2.13.2 Times of Illegal Receiving UNT Attach Request

Counter ID
C420360002
Description
Times of Illegal Receiving UNT Attach Request
Triggers
This counter is incremented by one when a UNT Attach request messages is discarded.
Collection Method
CC
2.13.3 Times of Failed Attach Request of S1 Release

Counter ID
C420360003
Description
Times of Failed Attach Request of S1 Release
Triggers
This counter is incremented by one when the attachment flow is terminated abnormally
due to S1 release.
Collection Method
CC
2-104

2.13.4 Times of Receiving Resend Attach Request

Counter ID
C420360004
Description
Times of Receiving Resend Attach Request
Triggers
This counter is incremented by one when a resent Attach request is received.
Collection Method
CC
2.13.5 Times of Receiving TAU Request of Procedure Conflict

Counter ID
C420360005
Description
Times of Receiving TAU Request of Procedure Conflict
Triggers
This counter is incremented by one when a TAU request is received but is then discarded
due to procedure conflict, or when an ongoing TAU flow is terminated because other
messages are received.
Collection Method
CC
2.13.6 Times of Failed TAU Request of S1 Release

Counter ID
C420360006
Description
Times of Failed TAU Request of S1 Release
2-105

Triggers
This counter is incremented by one when the TAU flow is terminated abnormally due to S1
release.
Collection Method
CC
2.13.7 Times of Receiving Resend TAU Request

Counter ID
C420360007
Description
Times of Receiving Resend TAU Request
Triggers
This counter is incremented by one when a resent TAU request is received.
Collection Method
CC
2.13.8 Times of Receiving Service Request of Procedure Conflict

Counter ID
C420360008
Description
Times of Receiving Service Request of Procedure Conflict
Triggers
This counter is incremented by one when a service request is received but is then discarded
due to procedure conflict, or when an ongoing service flow is terminated because other
messages are received.
Collection Method
CC
2-106

2.13.9 Times of Receiving Illegal UNT Service Request

Counter ID
C420360009
Description
Times of Receiving Illegal UNT Service Request
Triggers
This counter is incremented by one when a UNT service request message is discarded.
Collection Method
CC
2.13.10 Times of Failed Service Request of S1 Release

Counter ID
C420360010
Description
Times of Failed Service Request of S1 Release
Triggers
This counter is incremented by one when the service request flow is terminated abnormally
due to S1 release.
Collection Method
CC
2.13.11 Times of Receiving Resend Service Request

Counter ID
C420360011
Description
Times of Receiving Resend Service Request
Triggers
This counter is incremented by one when a resent service request is received.
2-107

Collection Method
CC
2.14 MME dedicated bearer activation Failure based on

Failure Cause Measurement
2.14.1 Times of failed dedicated bearer activation (Insufficient
resources)
Counter ID
C420370001
Description
This counter counts the number of dedicated bearer activation failures due to insufficient
resources.
Triggers
This counter is incremented by one when the MME receives an ACTIVATE DEDICATED
EPS BEARER CONTEXT REJECT message from the UE with the failure cause being
"Insufficient resources".
Collection Method
CC
2.14.2 Times of failed dedicated bearer activation (Request

rejected, unspecified)
Counter ID
C420370002
Description
This counter counts the number of dedicated bearer activation failures due to unspecified
request rejections.
Triggers
2-108

"Request rejected, unspecified".
Collection Method
CC
2.14.3 Times of failed dedicated bearer activation (Semantic error

in the TFT operation)
Counter ID
C420370003
Description
This counter counts the number of dedicated bearer activation failures due to TFT semantic
errors.
Triggers
"Semantic error in the TFT operation".
Collection Method
CC
2.14.4 Times of failed dedicated bearer activation (Syntactical error

in the TFT operation)
Counter ID
C420370004
Description
This counter counts the number of dedicated bearer activation failures due to TFT
syntactical errors.
Triggers
"Syntactical error in the TFT operation".
2-109

Collection Method
CC
2.14.5 Times of failed dedicated bearer activation (Invalid EPS

bearer identity)
Counter ID
C420370005
Description
This counter counts the number of dedicated bearer activation failures because the EPS
bearer identity is invalid.
Triggers
"Invalid EPS bearer identity".
Collection Method
CC
2.14.6 Times of failed dedicated bearer activation (Semantic errors

in packet filter (s))
Counter ID
C420370006
Description
This counter counts the number of dedicated bearer activation failures due to semantic
errors in packet filter(s).
Triggers
"Semantic errors in packet filter(s)".
Collection Method
CC
2-110

2.14.7 Times of failed dedicated bearer activation (Syntactical

errors in packet filter (s))
Counter ID
C420370007
Description
This counter counts the number of dedicated bearer activation failures due to syntactical
errors in packet filter(s).
Triggers
"Syntactical errors in packet filter(s)".
Collection Method
CC
2.14.8 Times of failed dedicated bearer activation (Semantically

incorrect message)
Counter ID
C420370008
Description
This counter counts the number of dedicated bearer activation failures due to semantic
message errors.
Triggers
"Semantically incorrect message".
Collection Method
CC
2-111

2.14.9 Times of failed dedicated bearer activation (Invalid

mandatory information)
Counter ID
C420370009
Description
This counter counts the number of dedicated bearer activation failures because the
mandatory information is invalid.
Triggers
"Invalid mandatory information".
Collection Method
CC
2.14.10 Times of failed dedicated bearer activation (Message type

Counter ID
C420370010
Description
message type does not exist or is not implemented.
Triggers
"Message type non-existent or not implemented".
Collection Method
CC
2-112

2.14.11 Times of failed dedicated bearer activation (Message type

not compatible with the protocol state)
Counter ID
C420370011
Description
message type is not compatible with the protocol state.
Triggers
"Message type not compatible with the protocol state".
Collection Method
CC
2.14.12 Times of failed dedicated bearer activation (Information

element non-existent or not implemented)
Counter ID
C420370012
Description
information element does not exist or is not implemented.
Triggers
"Information element non-existent or not implemented".
Collection Method
CC
2-113

2.14.13 Times of failed dedicated bearer activation (Conditional IE

error)
Counter ID
C420370013
Description
This counter counts the number of dedicated bearer activation failures due to conditional
IE errors.
Triggers
"Conditional IE error".
Collection Method
CC
2.14.14 Times of failed dedicated bearer activation (Message not

compatible with the protocol state)
Counter ID
C420370014
Description
message is not compatible with the protocol state.
Triggers
"Message not compatible with the protocol state".
Collection Method
CC
2-114

2.14.15 Times of failed dedicated bearer activation (Protocol error,

unspecified)
Counter ID
C420370015
Description
This counter counts the number of dedicated bearer activation failures due to unspecified
protocol errors.
Triggers
"Protocol error, unspecified".
Collection Method
CC
2.14.16 Times of failed dedicated bearer activation (PTI already

in use)
Counter ID
C420370016
Description
This counter counts the number of dedicated bearer activation failures because the PTI is
already in use.
Triggers
EPS BEARER CONTEXT REJECT message from the UE with the failure cause being "PTI
already in use".
Collection Method
CC
2-115

2.14.17 Times of failed dedicated bearer activation (EPS QoS not

accepted)
Counter ID
C420370017
Description
This counter counts the number of dedicated bearer activation failures because the EPS
QoS is not accepted.
Triggers
"EPS QoS not accepted".
Collection Method
CC
2.14.18 Times of failed dedicated bearer activation (Reactivation

requested)
Counter ID
C420370018
Description
This counter counts the number of dedicated bearer activation failures due to reactivation
requests.
Triggers
"Reactivation requested".
Collection Method
CC
2-116

2.14.19 Times of failed dedicated bearer activation (EPS bearer

context without TFT already activated)
Counter ID
C420370019
Description
This counter counts the number of dedicated bearer activation failures because a bearer
context without TFT already exists.
Triggers
"EPS bearer context without TFT already activated".
Collection Method
CC
2.14.20 Times of failed dedicated bearer activation (PTI mismatch)

Counter ID
C420370020
Description
This counter counts the number of dedicated bearer activation failures due to PTI
mismatch.
Triggers
EPS BEARER CONTEXT REJECT message from the UE with the failure cause being "PTI
mismatch".
Collection Method
CC
2-117

2.14.21 Times of failed dedicated bearer activation (Collision with

network initiated request)
Counter ID
C420370021
Description
This counter counts the number of dedicated bearer activation failures due to an conflict
with the network-initiated request.
Triggers
"Collision with network initiated request".
Collection Method
CC
2.14.22 Times of failed dedicated bearer activation (Invalid PTI

value)
Counter ID
C420370022
Description
This counter counts the number of dedicated bearer activation failures because the PTI is
invalid.
Triggers
"Invalid PTI value".
Collection Method
CC
2-118

2.14.23 Times of failed dedicated bearer activation (Other causes)

Counter ID
C420370023
Description
This counter counts the number of dedicated bearer activation failures due to other causes.
Triggers
EPS BEARER CONTEXT REJECT message from the UE with a failure cause of other
measurement items in this measurement type.
Collection Method
CC
2.15 MME bearer modification Failure based on Failure

Cause Measurement
2.15.1 Times of failed bearer modification (Insufficient resources)
Counter ID
C420380001
Description
This counter counts the number of bearer modification failures due to insufficient
resources.
Triggers
This counter is incremented by one when the MME receives a MODIFY EPS BEARER
CONTEXT REJECT message from the UE with the failure cause being "Insufficient
resources".
Collection Method
CC
2-119

2.15.2 Times of failed bearer modification (Semantic error in the

TFT operation)
Counter ID
C420380002
Description
This counter counts the number of bearer modification failures due to TFT semantic errors.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Semantic error in
the TFT operation".
Collection Method
CC
2.15.3 Times of failed bearer modification (Syntactical error in the

TFT operation)
Counter ID
C420380003
Description
This counter counts the number of bearer modification failures due to TFT syntactical
errors.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Syntactical error
in the TFT operation".
Collection Method
CC
2-120

2.15.4 Times of failed bearer modification (Invalid EPS bearer

identity)
Counter ID
C420380004
Description
This counter counts the number of bearer modification failures because the EPS bearer
identity is invalid.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Invalid EPS bearer
identity".
Collection Method
CC
2.15.5 Times of failed bearer modification (Semantic errors in

packet filter (s))
Counter ID
C420380005
Description
This counter counts the number of bearer modification failures due to semantic errors in
packet filter(s).
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Semantic errors
in packet filter(s)".
Collection Method
CC
2-121

2.15.6 Times of failed bearer modification (Syntactical errors in

packet filter (s))
Counter ID
C420380006
Description
This counter counts the number of bearer modification failures due to syntactical errors in
packet filter(s).
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Syntactical errors
in packet filter(s)".
Collection Method
CC
2.15.7 Times of failed bearer modification (EPS bearer context

without TFT already activated)
Counter ID
C420380007
Description
This counter counts the number of bearer modification failures because a bearer context
without TFT already exists.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "EPS bearer
context without TFT already activated".
Collection Method
CC
2-122

2.15.8 Times of failed bearer modification (Semantically incorrect

message)
Counter ID
C420380008
Description
This counter counts the number of bearer modification failures because the semantic
meaning of the message is incorrect.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Semantically
incorrect message".
Collection Method
CC
2.15.9 Times of failed bearer modification (Invalid mandatory

information)
Counter ID
C420380009
Description
This counter counts the number of bearer modification failures because the mandatory
information is incorrect.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Invalid mandatory
information".
Collection Method
CC
2-123

2.15.10 Times of failed bearer modification (Message type

Counter ID
C420380010
Description
This counter counts the number of bearer modification failures because the message type
does not exist or is not implemented.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Message type
non-existent or not implemented".
Collection Method
CC
2.15.11 Times of failed bearer modification (Message type not

Counter ID
C420380011
Description
This counter counts the number of bearer modification failures because the message type
is not compatible with the protocol state.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Message type not
compatible with the protocol state".
Collection Method
CC
2-124

2.15.12 Times of failed bearer modification (Information element

Counter ID
C420380012
Description
This counter counts the number of bearer modification failures because the information
element does not exist or is not implemented.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Information
element non-existent or not implemented".
Collection Method
CC
2.15.13 Times of failed bearer modification (Conditional IE error)

Counter ID
C420380013
Description
This counter counts the number of bearer modification failures due to conditional IE errors.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Conditional IE
error".
Collection Method
CC
2.15.14 Times of failed bearer modification (Message not

Counter ID
C420380014
2-125

Description
This counter counts the number of bearer modification failures because the message is
not compatible with the protocol state.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Message not
compatible with the protocol state".
Collection Method
CC
2.15.15 Times of failed bearer modification (Protocol error,

unspecified)
Counter ID
C420380015
Description
This counter counts the number of bearer modification failures due to unspecified protocol
errors.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Protocol error,
unspecified".
Collection Method
CC
2.15.16 Times of failed bearer modification (PTI already in use)

Counter ID
C420380017
Description
This counter counts the number of bearer modification failures because the PTI is already
in use.
2-126

Triggers
CONTEXT REJECT message from the UE with the failure cause being "PTI already in
use".
Collection Method
CC
2.15.17 Times of failed bearer modification (Request rejected,

unspecified)
Counter ID
C420380016
Description
This counter counts the number of bearer modification failures due to unspecified request
rejections.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Request rejected,
unspecified".
Collection Method
CC
2.15.18 Times of failed bearer modification (EPS QoS not accepted)

Counter ID
C420380018
Description
This counter counts the number of bearer modification failures because the EPS QoS is
not accepted.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "EPS QoS not
accepted".
2-127

Collection Method
CC
2.15.19 Times of failed bearer modification (Reactivation requested)

Counter ID
C420380019
Description
This counter counts the number of bearer modification failures due to reactivation request.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Reactivation
requested".
Collection Method
CC
2.15.20 Times of failed bearer modification (PTI mismatch)

Counter ID
C420380020
Description
This counter counts the number of bearer modification failures due to PTI mismatch.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "PTI mismatch".
Collection Method
CC
2-128

2.15.21 Times of failed bearer modification (Collision with network

initiated request)
Counter ID
C420380021
Description
This counter counts the number of bearer modification failures because the request
conflicts with a network-initiated request.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Collision with
network initiated request".
Collection Method
CC
2.15.22 Times of failed bearer modification (Invalid PTI value)

Counter ID
C420380022
Description
This counter counts the number of bearer modification failures because the PTI is invalid.
Triggers
CONTEXT REJECT message from the UE with the failure cause being "Invalid PTI value".
Collection Method
CC
2.15.23 Times of failed bearer modification (Other causes)

Counter ID
C420380023
2-129

Description
This counter counts the number of bearer modification failures due to other causes.
Triggers
CONTEXT REJECT message from the UE with a failure cause of other measurement
items in this measurement type.
Collection Method
CC
2.16 MME Attach Failure based on Failure Cause

Measurement
2.16.1 Times of EPS Attach failure (Illegal UE)
Counter ID
C420390001
Description
Times of EPS Attach failure (Illegal UE)
Triggers
This counter is incremented by one when the EMM sends an EPS attachment rejection
message (with the failure cause being "Illegal UE") to the UE in the EPS attachment flow.
Collection Method
CC
2.16.2 Times of EPS Attach failure (Illegal ME)

Counter ID
C420390002
Description
Times of EPS Attach failure (Illegal ME)
2-130

Triggers
message (with the failure cause being "Illegal ME") to the UE in the EPS attachment flow.
Collection Method
CC
2.16.3 Times of EPS Attach failure (EPS services not allowed)

Counter ID
C420390003
Description
Times of EPS Attach failure (EPS services not allowed)
Triggers
message (with the failure cause being "EPS services not allowed") to the UE in the EPS
attachment flow.
Collection Method
CC
2.16.4 Times of EPS Attach failure (EPS services and non-EPS

Counter ID
C420390004
Description
Times of EPS Attach failure (EPS services and non-EPS services not allowed)
Triggers
message (with the failure cause being "EPS services and non-EPS services not allowed")
to the UE in the EPS attachment flow.
Collection Method
CC
2-131

2.16.5 Times of EPS Attach failure (PLMN not allowed)

Counter ID
C420390005
Description
Times of EPS Attach failure (PLMN not allowed)
Triggers
message (with the failure cause being "PLMN not allowed") to the UE in the EPS
attachment flow.
Collection Method
CC
2.16.6 Times of EPS Attach failure (Tracking Area not allowed)

Counter ID
C420390006
Description
Times of EPS Attach failure (Tracking Area not allowed)
Triggers
message (with the failure cause being "Tracking Area not allowed") to the UE in the EPS
attachment flow.
Collection Method
CC
2.16.7 Times of EPS Attach failure (Roaming not allowed in this

tracking area)
Counter ID
C420390007
2-132

Description
Times of EPS Attach failure (Roaming not allowed in this tracking area)
Triggers
message (with the failure cause being "Roaming not allowed in this tracking area") to the
UE in the EPS attachment flow.
Collection Method
CC
2.16.8 Times of EPS Attach failure (EPS services not allowed in

this PLMN)
Counter ID
C420390008
Description
Times of EPS Attach failure (EPS services not allowed in this PLMN)
Triggers
message (with the failure cause being "EPS services not allowed in this PLMN") to the UE
in the EPS attachment flow.
Collection Method
CC
2.16.9 Times of EPS Attach failure (No Suitable Cells In tracking

area)
Counter ID
C420390009
Description
Times of EPS Attach failure (No Suitable Cells In tracking area)
2-133

Triggers
message (with the failure cause being "No Suitable Cells In tracking area") to the UE in
the EPS attachment flow.
Collection Method
CC
2.16.10 Times of EPS Attach failure (Network failure)

Counter ID
C420390010
Description
Times of EPS Attach failure (Network failure)
Triggers
message (with the failure cause being "Network failure") to the UE in the EPS attachment
flow.
Collection Method
CC
2.16.11 Times of EPS Attach failure (ESM failure)

Counter ID
C420390011
Description
Times of EPS Attach failure (ESM failure)
Triggers
message (with the failure cause being "ESM failure") to the UE in the EPS attachment flow.
Collection Method
CC
2-134

2.16.12 Times of EPS Attach failure (ESM failure for User Reason)
Counter ID
C420390012
Description
Times of EPS Attach failure (ESM failure for User Reason)
Triggers
message (with the failure cause being "ESM failure for User Reason") to the UE in the
EPS attachment flow.
Collection Method
CC
2.16.13 Times of EPS Attach failure (Congestion)

Counter ID
C420390013
Description
Times of EPS Attach failure (Congestion)
Triggers
message (with the failure cause being "Congestion") to the UE in the EPS attachment flow.
Collection Method
CC
2.16.14 Times of EPS Attach failure (Not authorized for this CSG)
Counter ID
C420390014
Description
Times of EPS Attach failure (Not authorized for this CSG)
2-135

Triggers
message (with the failure cause being "Not authorized for this CSG") to the UE in the EPS
attachment flow.
Collection Method
CC
2.16.15 Times of EPS Attach failure (Invalid mandatory information)

Counter ID
C420390015
Description
Times of EPS Attach failure (Invalid mandatory information)
Triggers
message (with the failure cause being "Invalid mandatory information") to the UE in the
EPS attachment flow.
Collection Method
CC
2.16.16 Times of EPS Attach failure (Message type non-existent or

not implemented)
Counter ID
C420390016
Description
Times of EPS Attach failure (Message type non-existent or not implemented)
Triggers
message (with the failure cause being "Message type non-existent or not implemented")
to the UE in the EPS attachment flow.
Collection Method
CC
2-136

2.16.17 Times of EPS Attach failure (Information element

Counter ID
C420390017
Description
Times of EPS Attach failure (Information element non-existent or not implemented)
Triggers
message (with the failure cause being "Information element non-existent or not
implemented") to the UE in the EPS attachment flow.
Collection Method
CC
2.16.18 Times of EPS Attach failure (Conditional IE error)

Counter ID
C420390018
Description
Times of EPS Attach failure (Conditional IE error)
Triggers
message (with the failure cause being "Conditional IE error") to the UE in the EPS
attachment flow.
Collection Method
CC
2.16.19 Times of EPS Attach failure (Protocol error, unspecified)

Counter ID
C420390019
2-137

Description
Times of EPS Attach failure (Protocol error, unspecified)
Triggers
message (with the failure cause being "Protocol error, unspecified") to the UE in the EPS
attachment flow.
Collection Method
CC
2.16.20 Times of EPS Attach failure (Other causes)

Counter ID
C420390020
Description
Times of EPS Attach failure (Other causes)
Triggers
message (with the failure cause of other measurement items in this measurement type) to
the UE in the EPS attachment flow.
Collection Method
CC
2.17 MME Periodic TAU Measurement

2.17.1 Times of Attempt
Counter ID
C420440001
Description
This counter counts the number of times that a periodic TAU request is originated.
2-138

Triggers
This counter is incremented by one when the MME receives a periodic TAU Request
message from the UE, and processes the request (successfully or unsuccessfully).
Collection Method
CC
2.17.2 Times of success

Counter ID
C420440002
Description
This counter counts the number of times that a periodic TAU request is accepted.
Triggers
This counter is incremented by one when the MME receives a periodic TAU Request
message from the UE and returns a TA Update Accept message to the UE.
Collection Method
CC
2.17.3 Times of IMSI unknown in HSS

Counter ID
C420440003
Description
This counter counts the number of times that a periodic TAU request is rejected because
the IMSI does not exist in the HSS.
Triggers
This counter is incremented by one when the MME receives a periodic TAU request
message from the UE and returns a TA Update Reject message to the UE, with the cause
being "IMSI unknown in HSS".
Collection Method
CC
2-139

2.17.4 Times of Illegal UE

Counter ID
C420440004
Description
the UE is illegal.
Triggers
being "Illegal UE".
Collection Method
CC
2.17.5 Times of Illegal ME

Counter ID
C420440005
Description
the ME is illegal.
Triggers
being "Illegal ME".
Collection Method
CC
2.17.6 Times of EPS services not allowed

Counter ID
C420440006
2-140

Description
EPS services are not allowed.
Triggers
being "EPS services not allowed".
Collection Method
CC
2.17.7 Times of EPS services and non-EPS services not allowed

Counter ID
C420440007
Description
EPS and non-EPS services are not allowed.
Triggers
being "EPS services and non-EPS services not allowed".
Collection Method
CC
2.17.8 Times of UE identity cannot be derived by the network

Counter ID
C420440008
Description
the UE ID cannot be found on the network side.
2-141

Triggers
being "UE identity cannot be derived by the network".
Collection Method
CC
2.17.9 Times of Implicitly detached

Counter ID
C420440009
Description
a subscriber is implicitly detached.
Triggers
being "Implicitly detached".
Collection Method
CC
2.17.10 Times of PLMN not allowed

Counter ID
C420440010
Description
the PLMN is not allowed.
Triggers
being "PLMN not allowed".
2-142

Collection Method
CC
2.17.11 Times of Tracking area not allowed

Counter ID
C420440011
Description
the tracking area is not allowed.
Triggers
being "Tracking Area not allowed".
Collection Method
CC
2.17.12 Times of Roaming not allowed in this tracking area

Counter ID
C420440012
Description
roaming is not allowed in the tracking area.
Triggers
being "Roaming not allowed in this tracking area".
Collection Method
CC
2-143

2.17.13 Times of EPS services not allowed in this PLMN

Counter ID
C420440013
Description
EPS services are not allowed in the PLMN.
Triggers
being "EPS services not allowed in this PLMN".
Collection Method
CC
2.17.14 Times of No suitable cells in tracking area

Counter ID
C420440014
Description
no suitable cells are in the tracking area.
Triggers
being "No suitable cells in tracking area".
Collection Method
CC
2.17.15 Times of MSC temporarily not reachable

Counter ID
C420440015
2-144

Description
the MSC is temporarily not reachable.
Triggers
being "MSC temporarily not reachable".
Collection Method
CC
2.17.16 Times of Network failure

Counter ID
C420440016
Description
a network failure occurs.
Triggers
being "Network failure".
Collection Method
CC
2.17.17 Times of CS domain not available

Counter ID
C420440017
Description
the CS domain is not available.
2-145

Triggers
being "CS domain not available".
Collection Method
CC
2.17.18 Times of ESM failure

Counter ID
C420440018
Description
an ESM failure occurs.
Triggers
being "ESM failure".
Collection Method
CC
2.17.19 Times of Congestion

Counter ID
C420440019
Description
congestion occurs.
Triggers
being "Congestion".
2-146

Collection Method
CC
2.17.20 Times of Not authorized for this CSG

Counter ID
C420440020
Description
the CSG is not authorized.
Triggers
being "Not authorized for this CSG".
Collection Method
CC
2.17.21 Times of No EPS bearer context activated

Counter ID
C420440021
Description
no activated EPS bearer context exits.
Triggers
being "No EPS bearer context activated".
Collection Method
CC
2-147

2.17.22 Times of invalid mandatory information element error

Counter ID
C420440022
Description
a mandatory field is invalid.
Triggers
being "Invalid mandatory information element error".
Collection Method
CC
2.17.23 Times of Message type non-existent or not implemented

Counter ID
C420440023
Description
the message type does not exist or is not implemented.
Triggers
being "Message type non-existent or not implemented".
Collection Method
CC
2.17.24 Times of information element non-existent or not

implemented
Counter ID
C420440024
2-148

Description
the information element does not exist or is not implemented.
Triggers
being "Information element non-existent or not implemented".
Collection Method
CC
2.17.25 Times of conditional IE error

Counter ID
C420440025
Description
a conditional IE error exists.
Triggers
being "Conditional IE error".
Collection Method
CC
2.17.26 Times of protocol error, unspecified

Counter ID
C420440026
Description
a protocol error exists.
2-149

Triggers
being "Protocol error, unspecified".
Collection Method
CC
2.17.27 Times of Other causes

Counter ID
C420440027
Description
of other reasons.
Triggers
being different from the causes of other counters of this measurement type.
Collection Method
CC
2-150

Chapter 3
MME Track Measurement
Table of Contents
Subscriber Measurement of MME TA .........................................................................3-1
TA Update Measurement of MME TA .........................................................................3-4
Attach Measurement of MME TA ..............................................................................3-32
Paging Measurement of MME TA .............................................................................3-59
Detach Measurement of MME TA.............................................................................3-60
Service Request Measurement of MME TA ..............................................................3-67
3.1 Subscriber Measurement of MME TA

3.1.1 Mean number of Attach Subscribers per TA
Counter ID
C420060003
Description
This counter counts the average number of the attached subscribers in each TA.
Triggers
The new subscriber attaches in the local TA, or the TA is successfully updated, the counter
is incremented by one; the old subscriber of the local TA detaches, or the attachment or
the route update fails, the counter is decremented by one.
When the service invokes the DB interface to modify the TA of the subscriber, the DB
collects the calculation according to different TAs. This counter is incremented by one if
the subscriber becomes belonging to this TA from not belonging to it (including creating TA
during the attachment); the counter is decremented by one if the subscriber becomes not
belonging to this TA from belonging to it (including deleting TA during the detachment).
Collection Method
TA
3-1

3.1.2 Max number of Attach Subscribers per TA

Counter ID
C420060004
Description
This counter counts the maximum number of subscribers attached in each TA.
Triggers
This counter is incremented by one if the new subscriber attaches in this TA, or the TA is
successfully updated and exceeds the last maximum value.
When the service invokes the DB interface to modify the TA of the subscriber, the DB
collects the calculation according to different TAs. This counter is incremented by one if
the subscriber becomes belonging to this TA from not belonging to it (including creating TA
during the attachment); the counter is decremented by one if the subscriber becomes not
belonging to this TA from belonging to it (including deleting TA during the detachment).
Collection Method
Max
3.1.3 Number of Subscribers in ECM-IDLE State per TA

Counter ID
C420060005
Description
This counter counts the number of subscribers in ECM-IDLE state per tracking area within
a measurement period.
Triggers
l This counter is incremented by one when a subscriber is set in ECM-IDLE state.
This counter decreases by one when a subscriber is deleted or changes from the
ECM-IDLE state to other state.
l The number of subscribers is counted based on changes in tracking areas when the
tracking area of a subscriber is modified. This counter is incremented by one when a
subscriber becomes to belong to this tracking area (including when a tracking area is
created during attachment). This counter decreases by one when a subscriber does
not belong to this tracking area (including when the tracking area is deleted during
detachment).
3-2

Chapter 3 MME Track Measurement
Collection Method
CC
3.1.4 Max Number of Subscribers in ECM-IDLE State per TA

Counter ID
C420060006
Description
This counter counts the maximum number of subscribers in ECM-IDLE state per tracking
area.
Triggers
This counter performs the add operation on the number of subscribers in ECM-IDLE state
per tracking area. When the number of subscribers in ECM-IDLE state is greater than the
maximum number of subscribers in ECM-IDLE state, the maximum number of subscribers
is equal to the number of subscribers.
Collection Method
CC
3.1.5 Number of Subscribers in ECM-CONNECT State per TA

Counter ID
C420060007
Description
This counter counts the number of subscribers in ECM-CONNECT state per tracking area
Triggers
l This counter is incremented by one when a subscriber is set to be in ECM-CONNECT
state. This counter decreases by one when a subscriber is deleted or changes from
the ECM-CONNECT state to other state.
l The number of subscribers is counted based on changes in tracking areas when the
tracking area of a subscriber is modified. This counter is incremented by one when a
subscriber becomes to belong to this tracking area. This counter decreases by one
when a subscriber does not belong to this tracking area (including when the tracking
area is deleted during detachment).
3-3

Collection Method
CC
3.1.6 Max Number of Subscribers in ECM-CONNECT State per TA

Counter ID
C420060008
Description
This counter counts the maximum number of subscribers in ECM-CONNECT state per
tracking area.
Triggers
This counter performs the add operation on the number of subscribers in ECM-CONNECT
state per tracking area. When the number of subscribers in ECM-CONNECT state is
greater than the maximum number of subscribers in ECM-CONNECT state, the maximum
number of subscribers is equal to the number of subscribers.
Collection Method
CC
3.2 TA Update Measurement of MME TA

3.2.1 Times of TAU Attempt Without SGW Change per TA
Counter ID
C420070022
Description
This counter counts the times of TAU requests with the SGW unchanged in each TA.
Triggers
The calculation is made after the MME receives the TA Update Request message
originated by the UE, wherein the SGW is unchanged, and the TAU processing succeeds
or fails, as shown in the following figures. A indicates the triggering position of this
3-4

Collection Method
CC
3.2.2 Times of TAU Success Without SGW Change per TA

Counter ID
C420070023
Description
This counter counts the times of successful TAU with the SGW unchanged in each TA.
3-5

Triggers
During the TAU with the SGW unchanged, the MME sends the TA Update Accept message
to the UE, as shown in the following figure. A indicates the triggering position of this
measurement item.
Collection Method
CC
3.2.3 Times of TAU Without SGW Change Failure per TA (Illegal UE)
Counter ID
C420070024
Description
This counter counts the number of failed TAU with the SGW unchanged in each TA, which
is caused by the illegal UE.
Triggers
During the TAU with the SGW unchanged, the MME sends the TA Update Reject message
to the UE, with the reject reason as Illegal UE, as shown in the following figure. A indicates
the triggering position of this measurement item in the flow.
3-6

Collection Method
CC
3.2.4 Times of TAU Without SGW Change Failure per TA (Illegal ME)
Counter ID
C420070025
Description
This counter counts the times of failed TAU with the SGW unchanged in each TA, which
is caused by the illegal ME.
Triggers
to the UE, with the reject reason as Illegal ME, as shown in the following figure. A indicates
3-7

Collection Method
CC
3.2.5 Times of TAU Without SGW Change Failure per TA (EPS

Counter ID
C420070026
Description
is caused by that the EPS service is not allowed.
Triggers
to the UE, with the reject reason as EPS services not allowed, as shown in the following
3-8

Collection Method
CC

services and non-EPS services not allowed)
Counter ID
C420070027
Description
is caused by that the EPS service and the non-EPS service are not allowed.
Triggers
to the UE, with the reject reason as EPS services and non-EPS services not allowed,
as shown in the following figure. A indicates the triggering position of this measurement
item in the flow.
3-9

Collection Method
CC
3.2.7 Times of TAU Without SGW Change Failure per TA (UE

identity cannot be derived by the network)
Counter ID
C420070028
Description
is caused by that the network side cannot obtain the UE identity.
Triggers
to the UE, with the reject reason as UE identity cannot be derived by the network, as
shown in the following figure. A indicates the triggering position of this measurement item
in the flow.
3-10

Collection Method
CC
3.2.8 Times of TAU Without SGW Change Failure per TA (Implicitly

detached)
Counter ID
C420070029
Description
is caused by implicitly detached.
Triggers
to the UE, with the reject reason as Implicitly detached, as shown in the following figure.
A indicates the triggering position of this measurement item in the flow.
3-11

Collection Method
CC
3.2.9 Times of TAU Without SGW Change Failure per TA (PLMN

not allowed)
Counter ID
C420070030
Description
is caused by that the PLMN is not allowed.
Triggers
to the UE, with the reject reason as PLMN not allowed, as shown in the following figure.
3-12

Collection Method
CC
3.2.10 Times of TAU Without SGW Change Failure per TA (Tracking

area not allowed)
Counter ID
C420070031
Description
is caused by that the TA is not allowed.
Triggers
to the UE, with the reject reason as Tracking area not allowed, as shown in the following
3-13

Collection Method
CC
3.2.11 Times of TAU Without SGW Change Failure per TA (Roaming

not allowed in this tracking area)
Counter ID
C420070032
Description
is caused by that the TA does not allow roaming.
Triggers
to the UE, with the reject reason as Roaming not allowed in this tracking area, as shown
flow.
3-14

Collection Method
CC

services not allowed in this PLMN)
Counter ID
C420070033
Description
is caused by that the PLMN does not allow the EPS service.
Triggers
to the UE, with the reject reason as EPS services not allowed in this PLMN, as shown
flow.
3-15

Collection Method
CC
3.2.13 Times of TAU Without SGW Change Failure per TA (No

suitable cells in tracking area)
Counter ID
C420070034
Description
is caused by that there is no suitable cell in this TA.
Triggers
to the UE, with the reject reason as No suitable cells in tracking area, as shown in the
3-16

Collection Method
CC
3.2.14 Times of TAU Without SGW Change Failure per TA (Not

authorized for this CSG)
Counter ID
C420070035
Description
is caused by that the CSG is not authorized.
Triggers
to the UE, with the reject reason as Not authorized for this CSG, as shown in the following
3-17

Collection Method
CC
3.2.15 Times of TAU Without SGW Change Failure per TA (No EPS
bearer context activated)
Counter ID
C420070036
Description
is caused by that there is no activated EPS bearer context.
Triggers
to the UE, with the reject reason as No EPS bearer context activated, as shown in the
3-18

Collection Method
CC
3.2.16 Times of TAU Without SGW Change Failure per TA (invalid

mandatory information element error)
Counter ID
C420070037
Description
is caused by that the mandatory field is invalid.
Triggers
to the UE, with the reject reason as invalid mandatory information element error, as
in the flow.
3-19

Collection Method
CC
3.2.17 Times of TAU Without SGW Change Failure per TA

(information element non-existent or not implemented)
Counter ID
C420070038
Description
is caused by that the information element does not exist or is not applied.
Triggers
During the TAU with the SGW unchanged, the MME sends the TA Update Reject
message to the UE, with the reject reason as information element non-existent or not
implemented, as shown in the following figure. A indicates the triggering position of this
3-20

Collection Method
CC

(conditional IE error)
Counter ID
C420070039
Description
is caused by conditional IE error.
Triggers
to the UE, with the reject reason as conditional IE error, as shown in the following figure.
3-21

Collection Method
CC
3.2.19 Times of TAU Without SGW Change Failure per TA (protocol

error)
Counter ID
C420070040
Description
This counter counts the number of failed TAU with the SGW unchanged in each TA, which
is caused by protocol error.
Triggers
to the UE, with the reject reason as protocol error, unspecified., as shown in the following
3-22

Collection Method
CC
3.2.20 Times of TAU Failure Without SGW Change per TA (Network

Failure)
Counter ID
C420070041
Description
This counter counts the times of TAU Failures with SGW unchanged per TA (Network
Failure) within a measurement period.
Triggers
The counter counts, during the TAU process with SGW unchanged, if MME sends to UE
a TAU Reject message including the reject cause Network failure. "A" as shown in the
following figure indicates the location where the measurement item is triggered in the flow.
3-23

Collection Method
CC
3.2.21 Times of Receiving Repeat TAU Request Message

Counter ID
C420070043
Description
This counter counts the number of times that a received TAU request is resent.
Triggers
After sending a TAU Accept, the MME receives a TAU request when waiting for a TAU
Complete message, and will send a TAU Accept again. In this case, this counter is
incremented by one.
Collection Method
CC
3.2.22 Times of TAU Without SGW Change Failure per TA (IMSI

Unknown in HSS)
Counter ID
C420070052
3-24

Description
is caused by the IMSI unknown in HSS.
Triggers
to the UE, with the reject reason as IMSI unknown in HSS, as shown in the following
Collection Method
CC
3.2.23 Times of TAU Without SGW Change Failure per TA (MSC

Temporarily not Reachable)
Counter ID
C420070053
Description
is caused by the MSC temporarily not reachable.
Triggers
to the UE, with the reject reason as MSC temporarily not reachable, as shown in the
3-25

Collection Method
CC
3.2.24 Times of TAU Without SGW Change Failure per TA (CS

domain not available)
Counter ID
C420070054
Description
is caused by CS domain not available.
Triggers
to the UE, with the reject reason as CS domain not available, as shown in the following
3-26

Collection Method
CC
3.2.25 Times of TAU Without SGW Change Failure per TA (ESM

Failure)
Counter ID
C420070055
Description
is caused by the ESM failure.
Triggers
to the UE, with the reject reason as ESM failure, as shown in the following figure. A
3-27

Collection Method
CC

(Congestion)
Counter ID
C420070056
Description
is caused by congestion.
Triggers
to the UE, with the reject reason as Congestion, as shown in the following figure. A
3-28

Collection Method
CC
3.2.27 Times of TAU Without SGW Change Failure per TA (Message

Type Non-Existent or not Implemented)
Counter ID
C420070057
Description
is caused by message type non-existent or not implemented.
Triggers
to the UE, with the reject reason as Message type non-existent or not implemented, as
in the flow.
3-29

Collection Method
CC
3.2.28 Times of TAU Failure without SGW Change per TA (Network

failure for UE or radio reason)
Counter ID
C420070062
Description
Times of TAU Failure without SGW Change per TA (Network failure for UE or radio reason)
Triggers
In the TAU process that the SGW is not changed, the counter is incremented by one when
the MME sends TA update reject messages to the UE. This failure is triggered by terminal or
wireless reasons, including no response to the authentication, no response to the security
mode, or the security mode rejection.
Collection Method
CC
3-30

3.2.29 Times of TAU Attempt Intra-MME With SGW unchanged per

TA
Counter ID
C420070070
Description
Times of TAU Attempt Intra-MME With SGW unchanged per TA.
Triggers
This counter is incremented by one when the MME receives a TAU request message (TA
Update Request) from the UE, in which neither the MME nor the SGW is not changed, no
matter the TAU processing is successful or not (including the TAU from the SGSN to the
MME).
Collection Method
CC
3.2.30 Times of TAU Success Intra-MME With SGW unchanged per

TA
Counter ID
C420070071
Description
Times of TAU Success Intra-MME With SGW unchanged per TA.
Triggers
This counter is incremented by one when the MME sends a TAU Accept message (TA
Update Accept) to the UE in the TAU flow with unchanged MME and SGW.
Collection Method
CC
3-31

3.3 Attach Measurement of MME TA

3.3.1 Times of Attach Request from UE per TA
Counter ID
C420080003
Description
This counter counts the times that the S1 interface of the MME receives the Attach Request
messages.
Triggers
As shown in the following figures, the calculation is made when the MME receives the
Attach Request message, and the attachment succeeds or fails. The calculation is made
at point A.
3-32

Collection Method
CC
3.3.2 Times of Success for Attach Procedure from UE per TA

Counter ID
C420080004
Description
This counter counts the times that the S1 interface of the MME receives the Attach
complete messages.
Triggers
As shown in the following figure, when the MME receives the Attach complete message,
the calculation is made at point A.
3-33

Collection Method
CC
3.3.3 Times of EPS Attach Failure per TA (Illegal UE)

Counter ID
C420080005
Description
This counter counts the times of failed EPS attachment in each TA, which is caused by the
Illegal UE.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as Illegal UE,
as shown in the following figure. A indicates the triggering position of this measurement
item in the flow.
3-34

Collection Method
CC
3.3.4 Times of EPS Attach Failure per TA (Illegal ME)

Counter ID
C420080006
Description
Illegal ME.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as
Illegal ME, as shown in the following figure. A indicates the triggering position of this
3-35

Collection Method
CC
3.3.5 Times of EPS Attach Failure per TA (EPS services not allowed)
Counter ID
C420080007
Description
This counter counts the times of failed EPS attachment in each TA, which is caused by
that the EPS service is not allowed.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as EPS
services not allowed, as shown in the following figure. A indicates the triggering position
of this measurement item in the flow.
3-36

Collection Method
CC
3.3.6 Times of EPS Attach Failure per TA (EPS services and

non-EPS services not allowed)
Counter ID
C420080008
Description
that the EPS service and the non-EPS service are not allowed.
Triggers
services and non-EPS services not allowed, as shown in the following figure. A
3-37

Collection Method
CC
3.3.7 Times of EPS Attach Failure per TA (PLMN not allowed)

Counter ID
C420080009
Description
that the PLMN is not allowed.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as PLMN
not allowed, as shown in the following figure. A indicates the triggering position of this
3-38

Collection Method
CC
3.3.8 Times of EPS Attach Failure per TA (Tracking Area not

allowed)
Counter ID
C420080010
Description
that the TA is not allowed.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as Tracking
Area not allowed, as shown in the following figure. A indicates the triggering position of
this measurement item in the flow.
3-39

Collection Method
CC
3.3.9 Times of EPS Attach Failure per TA (Roaming not allowed in

this tracking area)
Counter ID
C420080011
Description
that the TA does not allow roaming.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as Roaming
not allowed in this tracking area, as shown in the following figure. A indicates the
triggering position of this measurement item in the flow.
3-40

Collection Method
CC
3.3.10 Times of EPS Attach Failure per TA (EPS services not

allowed in this PLMN)
Counter ID
C420080012
Description
that the PLMN does not allow the EPS service.
Triggers
services not allowed in this PLMN, as shown in the following figure. A indicates the
3-41

Collection Method
CC
3.3.11 Times of EPS Attach Failure per TA (No Suitable Cells In

tracking area)
Counter ID
C420080013
Description
that there is no suitable cell in this TA.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as No
Suitable Cells In tracking area, as shown in the following figure. A indicates the triggering
3-42

Collection Method
CC
3.3.12 Times of EPS Attach Failure per TA (ESM failure)

Counter ID
C420080014
Description
ESM failure.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as ESM
failure, as shown in the following figure. A indicates the triggering position of this
3-43

Collection Method
CC
3.3.13 Times of EPS Attach Failure per TA (Not authorized for this
CSG)
Counter ID
C420080015
Description
that the CSG is not authorized.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as Not
authorized for this CSG, as shown in the following figure. A indicates the triggering
3-44

Collection Method
CC
3.3.14 Times of EPS Attach Failure per TA (Invalid mandatory

information)
Counter ID
C420080016
Description
that the mandatory field is invalid.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as Invalid
mandatory information, as shown in the following figure. A indicates the triggering
3-45

Collection Method
CC
3.3.15 Times of EPS Attach Failure per TA (Information element

Counter ID
C420080017
Description
that the information element does not exist or is not applied.
Triggers
Information element non-existent or not implemented, as shown in the following
3-46

Collection Method
CC
3.3.16 Times of EPS Attach Failure per TA (Conditional IE error)

Counter ID
C420080018
Description
conditional IE error.
Triggers
Conditional IE error, as shown in the following figure. A indicates the triggering position
3-47

Collection Method
CC
3.3.17 Times of EPS Attach Failure per TA (Protocol error)

Counter ID
C420080019
Description
protocol error.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as Protocol
error, unspecified, as shown in the following figure. A indicates the triggering position of
3-48

Collection Method
CC
3.3.18 Times of EPS Attach Failure per TA (Network Failure)

Counter ID
C420080020
Description
This counter counts the times that EPS attach fails per TA (network failure) within a
measurement period.
Triggers
The counter counts when MME sends to UE an Attach Reject message, in which the failure
cause is Network failure. "A" as shown in the following figure indicates the location where
the measurement item is triggered in the flow.
3-49

Collection Method
CC
3.3.19 Times of EPS Attach Failure per TA (ESM Failure for User
Reason)
Counter ID
C420080021
Description
This counter counts the times that EPS attach fails per TA (ESM Failure due to user causes)
Triggers
The counter counts after MME sends to UE an Attach Reject message, in which the failure
cause value is ESM failure for User Reason (that is, the value of EMM cause is ESM
failure, ESM cause is Insufficient resources, Request rejected by Serving GW or PDN
GW, or Network failure). "A" as shown in the following figure indicates the location where
the measurement item is triggered in the flow.
3-50

Collection Method
CC
3.3.20 Times of Attach produce per TA (ms)

Counter ID
C420080022
Description
This counter counts the time interval from that the UE receives the Attach Request
message to that the MME dispatches the Attach Accept message in the measurement
period (Unit:ms).
Triggers
As shown in the following figure, when the MME receives the Attach Request message,
the point A1 is considered as the start time; when the MME dispatches the Attach Accept
message, the point A2 is considered as the end time. The difference between the end time
and the start time is the time interval for establishing the attachment.
3-51

Collection Method
CC
3.3.21 Times of Receiving Attach Request of Procedure Conflict

Counter ID
C420080024
Description
This counter counts the number of times that the MME receives attach request of procedure
conflict.
Triggers
The value of this counter increases by one when the MME discards a received attach
request message for procedure conflict, or the attach procedure be terminated due to the
MME receives other message when the Attach flow is in process.
Collection Method
CC
3.3.22 Times of Receiving UNT Attach Request of App Resource

Fail
Counter ID
C420080025
3-52

Description
This counter counts the number of times that the MME receive UNT attach request for
applying resource fail when MME sent direct.
Triggers
The value of this counter increases by one when the MME discards a received attach
request message for applying resource fail.
Collection Method
CC
3.3.23 Times of EPS Attach Failure per TA (IMSI Unknown in HSS)

Counter ID
C420080026
Description
IMSI unknown in HSS.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as IMSI
unknown in HSS, as shown in the following figure. A indicates the triggering position of
Collection Method
CC
3-53

3.3.24 Times of EPS Attach Failure per TA (UE Identity Cannot be

Derived by the Network)
Counter ID
C420080027
Description
UE identity cannot be derived by the network.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as UE
identity cannot be derived by the network, as shown in the following figure. A indicates
Collection Method
CC
3.3.25 Times of EPS Attach Failure per TA (MSC Temporarily not

Reachable)
Counter ID
C420080028
3-54

Description
MSC temporarily not reachable.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as MSC
temporarily not reachable, as shown in the following figure. A indicates the triggering
Collection Method
CC
3.3.26 Times of EPS Attach Failure per TA (CS Domain not

Available)
Counter ID
C420080029
Description
This counter counts the times of failed EPS attachment in each TA, which is caused by CS
domain not available.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as CS
domain not available, as shown in the following figure. A indicates the triggering position
3-55

Collection Method
CC
3.3.27 Times of EPS Attach Failure per TA (Congestion)

Counter ID
C420080030
Description
congestion.
Triggers
Congestion, as shown in the following figure. A indicates the triggering position of this
3-56

Collection Method
CC
3.3.28 Times of EPS Attach Failure per TA (Message Type

Non-Existent or not Implemented)
Counter ID
C420080031
Description
message type non-existent or not implemented.
Triggers
The MME sends the Attach Reject message to the UE, with the failure reason as Message
type non-existent or not implemented, as shown in the following figure. A indicates the
3-57

Collection Method
CC
3.3.29 Times of EPS Attach Failure per TA (Network Failure for UE

or Radio Reason)
Counter ID
C420080036
Description
This counter counts the number of EPS attachment failures in each TA, which is caused
by the network failure for UE or Radio reasons.
Triggers
The counter is incremented by one when the MME sends an Attach Reject message to
the UE. This failure is triggered by a UE or radio problem, including no response to the
authentication, no response to security mode or the security mode rejection.
Collection Method
CC
3-58

3.4 Paging Measurement of MME TA

3.4.1 Times of E-UTRAN Paging per TA
Counter ID
C420090003
Description
This counter counts the number of times that the MME originates the E-UTRAN packet
paging in each TA.
Triggers
As shown in the following figure, when the MME sends the Paging message to the UE,
calculate the This counter counts the number of times of paging at point A in each TA.
Collection Method
CC
3.4.2 Times of Success for E-UTRAN Paging per TA

Counter ID
C420090004
Description
This counter counts the number of times of successfully receiving the responses from the
UE after the MME originates the E-UTRAN packet paging in each TA.
3-59

Triggers
As shown in the following figure, when the MME receives the service request message
sent by the UE, and the Service Type = Paging Response, the calculation is made at point
A.
Collection Method
CC
3.5 Detach Measurement of MME TA

3.5.1 Times of EPS Detach Request from UE per TA
Counter ID
C420110003
Description
This counter calculates the times that the S1 interface of the MME receives the Detach
Request messages.
Triggers
As shown in the following figure, the calculation is made when the MME receives the
Detach Request message with the Detach type IE as EPS detach, and the detachment
succeeds or fails. The calculation is made at point A.
3-60

Collection Method
CC
3.5.2 Times of Success for EPS Detach Procedure from UE per TA

Counter ID
C420110004
Description
This counter calculates the times that the S1 interface of the MME sends the Detach Accept
messages.
Triggers
As shown in the following figure, the calculation is made when the MME sends the Detach
Accept message at point A.
3-61

Collection Method
CC
3.5.3 Times of EPS Detach Request from MME per TA

Counter ID
C420110005
Description
This counter calculates the times that the S1 interface of the MME sends the Detach
Request messages.
Triggers
As shown in the following figure, the calculation is made after the MME sends the Detach
Request message, and the detachment succeeds or fails. The calculation is made at point
A.
3-62

Collection Method
CC
3.5.4 Times of Success for EPS Detach Procedure from MME per TA
Counter ID
C420110006
Description
This counter calculates the times that the S1 interface of the MME receives the Detach
Accept messages.
Triggers
As shown in the following figure, when the MME receives the Detach Accept message, the
calculation is made at point A.
3-63

Collection Method
CC
3.5.5 Times of EPS Detach Request from HSS per TA

Counter ID
C420110007
Description
This counter counts the times that the s6a interface of the MME receives the Cancel
Location Request messages.
Triggers
As shown in the following figure, the calculation is made after the MME receives the Cancel
Location Request message, and the detachment succeeds or fails. The calculation is
made at point A.
3-64

Collection Method
CC
3.5.6 Times of Success for EPS Detach Procedure from HSS per TA
Counter ID
C420110008
Description
This counter calculates the times that the s6a interface of the MME sends the Cancel
Location Answer messages.
Triggers
As shown in the following figure, the calculation is made when the MME sends the Cancel
Location Answer message at Point A.
3-65

Collection Method
CC
3.5.7 Times of Receiving repeat Detach Request message

Counter ID
C420110009
Description
This counter counts the number of times that detach messages are resent.
Triggers
This counter is incremented by one when a detach request message is received during
the detaching process.
Collection Method
CC
3.5.8 Times of Sending repeat Detach Request message

Counter ID
C420110010
Description
This counter counts the number of times that detach messages are resent.
3-66

Triggers
This counter is incremented by one when a detach request message is resent after it is
sent without getting a response.
Collection Method
CC
3.6 Service Request Measurement of MME TA

3.6.1 Times of Receiving repeat Service Request message
Counter ID
C420200003
Description
This counter counts the number of resent service request messages.
Triggers
This counter is incremented by one when a resent service request message is received
during the service request process.
Collection Method
CC
3.6.2 Times of Service Request

Counter ID
C420200004
Description
This counter counts the number of times that terminals in each trace area originate a
service request.
Triggers
This counter is incremented by one after EMM receives a Service Request message and
processes the request (successful or failed).
Collection Method
CC
3-67

3.6.3 Successful Times of service request

Counter ID
C420200005
Description
This counter counts the number of times that terminals in each trace area successfully
originate a service request.
Triggers
This counter is incremented by one when S1AP:Initial Context Setup Request is sent.
Collection Method
CC
3-68

Chapter 4
MME Interface Measurement
Table of Contents
MME S1 Interface Measurement ................................................................................4-1
4.1 MME S1 Interface Measurement

4.1.1 Numbers of IP Packet MME S1 Interface Received
Counter ID
C420120001(EMS)
Description
This counter counts the number of IP packets received by the MME S1 interface.
Triggers
This counter is incremented by one when the MME S1 interfaces receives an IP packet.
Collection Method
CC
4.1.2 Numbers of IP Packet MME S1 Interface Sent

Counter ID
C420120002(EMS)
Description
This counter counts the number of IP packets sent by the MME S1 interface.
Triggers
This counter is incremented by one when the MME S1 interface sends an IP packet.
Collection Method
CC
4-1

4.1.3 Bytes of IP Packet MME S1 Interface Received(Byte)

Counter ID
C420120003(EMS)
Description
This counter counts the number of bytes received from the IP layer by the MME S1
interface.
Triggers
This counter is incremented by one when the MME S1 interface receives an IP packet.
Collection Method
CC
4.1.4 Bytes of IP Packet MME S1 Interface Sent(Byte)

Counter ID
C420120004(EMS)
Description
This counter counts the number of IP packets sent by the MME S1 interface.
Triggers
This counter is incremented by one when the MME S1 interface sends an IP packet.
Collection Method
CC
4-2

Chapter 5
SAE-GW Measurement
Table of Contents
S1u Port Flow Measurement ......................................................................................5-1
SGi Port Flow Measurement.......................................................................................5-4
5.1 S1u Port Flow Measurement

5.1.1 Number of Data Packets Received from S1u Interface
Counter ID
C430010001
Description
l This counter counts only the received GTP packets with a message type of 0xF in the
GTP header being 0xFF.
l On the USUP-GW board, this counter counts the number of GTP packets after IP
fragments are reassembled in tunnels.
Triggers
This counter is incremented by one when the USUP-GW board receives a GTP packet
from the S1u interface.
Collection Method
CC
5.1.2 Number of Data Bytes Received from S1u Interface (Byte)

Counter ID
C430010002
Description
l This counter counts only the received GTP packets with a message type of 0xF in the
GTP header being 0xFF.
5-1

l On the USUP-GW board, this counter counts the number of bytes of GTP packets
after IP fragments are reassembled in tunnels.
Triggers
This counter counts the number of bytes when the USUP-GW board receives a GTP packet
from the S1u interface.
Collection Method
CC
5.1.3 Number of Data Packets Sent to S1u Interface

Counter ID
C430010003
Description
l This counter counts only the sent GTP packets with a message type of 0xF in the GTP
header being 0xFF.
l On the USUP-GW board, this counter counts the number of GTP packets after IP
fragments are reassembled in tunnels.
Triggers
This counter is incremented by one when the USUP-GW board sends a GTP packet to the
S1u interface.
Collection Method
CC
5.1.4 Number of Data Bytes Sent to S1u Interface (Byte)

Counter ID
C430010004
Description
l This counter counts only the sent GTP packets with a message type of 0xF in the GTP
header being 0xFF.
l On the USUP-GW board, this counter counts the number of bytes of GTP packets
after IP fragments are reassembled in tunnels.
5-2

Chapter 5 SAE-GW Measurement
Triggers
This counter counts the number of bytes when the USUP-GW board sends a GTP packet
to the S1u interface.
Collection Method
CC
5.1.5 Peak Rate of Data Packets Received from S1u Interface (pps)
Counter ID
C430010005
Description
This counter counts the peak rate of packets received from the S1u interface.
Triggers
This counter counts the peak rate of packets when the ZXUN iEPC receives packets from
the S1u interface.
Collection Method
Peak
5.1.6 Peak Rate of Data Bytes Received from S1u Interface(KB/s)

Counter ID
C430010006
Description
This counter counts the peak rate of packet bytes received from the S1u interface.
Triggers
This counter counts the peak rate of bytes when the ZXUN iEPC receives packets from
the S1u interface.
Collection Method
Peak
5-3

5.1.7 Peak Rate of Data Packets Sent to S1u Interface (pps)

Counter ID
C430010007
Description
This counter counts the peak rate of packets sent to the S1u interface.
Triggers
This counter counts the peak rate when the ZXUN iEPC sends packets to the S1u interface.
Collection Method
Peak
5.1.8 Peak Rate of Data Bytes Sent to S1u Interface (KB/s)

Counter ID
C430010008
Description
This counter counts the peak rate of packet bytes sent to the S1u interface.
Triggers
This counter counts the peak rate of packet bytes when the ZXUN iEPC sends packets to
the S1u interface.
Collection Method
Peak
5.2 SGi Port Flow Measurement

5.2.1 Number of Data Packets Sent to SGi Interface
Counter ID
C430020001
Description
On the USUP-GW board, this counter counts the number of IP packets before IP
fragmentation.
5-4

Triggers
This counter is incremented by one when the USUP-GW board sends an IP packet to the
SGi interface.
Collection Method
CC
5.2.2 Number of Uplink Data Bytes Sent to SGi Interface (Byte)

Counter ID
C430020002
Description
On the USUP-GW board, this counter counts the number of IP packet bytes before IP
fragmentation.
Triggers
This counter counts the number of bytes when the USUP-GW board sends an IP packet
to the SGi interface.
Collection Method
CC
5.2.3 Number of Data Packets Received from SGi Interface

Counter ID
C430020003
Description
On the USUP-GW board, this counter counts the number of packets received after IP
fragmentation.
Triggers
This counter is incremented by one when the USUP-GW board receives a packet and finds
the context in the packet.
Collection Method
CC
5-5

5.2.4 Number of Data Bytes Received from SGi Interface (Byte)

Counter ID
C430020004
Description
On the USUP-GW board, this counter counts the number of packet bytes received after
IP fragmentation.
Triggers
This counter counts the number of packet bytes when the USUP-GW board receives
packets and finds the context in them.
Collection Method
CC
5.2.5 Peak Rate of Data Packets Sent to SGi Interface (pps)

Counter ID
C430020005
Description
This counter counts the peak rate of packets sent to the SGi interface.
Triggers
This counter counts the peak rate when the ZXUN iEPC sends packets to the SGi interface.
Collection Method
Peak
5.2.6 Peak Rate of Data Bytes Sent to SGi Interface(KB/s)

Counter ID
C430020006
Description
This counter counts the peak rate of packet bytes sent to the SGi interface.
5-6

Triggers
This counter counts the peak rate of packet bytes when the ZXUN iEPC sends packets to
the SGi interface.
Collection Method
Peak
5.2.7 Peak Rate of Data Packets Received from SGi Interface (pps)
Counter ID
C430020007
Description
This counter counts the peak rate of packets received from SGi interface.
Triggers
This counter counts the peak rate of packets when the ZXUN iEPC receives packets from
the SGi interface.
Collection Method
Peak
5.2.8 Peak Rate of Data Bytes Received from SGi Interface (KB/s)
Counter ID
C430020008
Description
This counter counts the peak rate of packet bytes received from the SGi interface.
Triggers
This counter counts the peak rate of packet bytes when the ZXUN iEPC receives packets
from the SGi interface.
Collection Method
Peak
5-7

5-8

Glossary
MME
- Mobility Management Entity
NAS
- Network Access Server
PDN
- Packet Data Network
SGW
- Serving Gateway
UE
- User Equipment

SJ-20150919164026-011-ZXUN iEPC (V1.15.10) Integrated Evolved Packet Core Performance Counter Reference

Uploaded by

Copyright:

Available Formats

SJ-20150919164026-011-ZXUN iEPC (V1.15.10) Integrated Evolved Packet Core Performance Counter Reference

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20150919164026-011-ZXUN iEPC (V1.15.10) Integrated Evolved Packet Core Performance Counter Reference

Uploaded by

Copyright:

Available Formats

ZXUN iEPC

Integrated Evolved Packet Core

Revision No. Revision Date Revision Reason

R1.0 2015-10-30 First Edition

Serial Number: SJ-20150919164026-011

Publishing Date: 2015-10-30 (R1.0)

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

Chapter 2 MME Measurement ................................................................... 2-1

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

Chapter 3 MME Track Measurement ......................................................... 3-1

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

Chapter 4 MME Interface Measurement ................................................... 4-1

Chapter 5 SAE-GW Measurement ............................................................. 5-1

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

1.1 Relationship Between the Performance Counters

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

1.2 Introduction to the Format of the Performance

Table 1-1 Collection Method

Value Name Description

CC Accumulation It traces the accumulated changes of an event in the collection granularity

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

Value Name Description

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1 MME ESM Measurement

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.2 Max Number of Dedicated Bearers in Active State

2.1.3 Times of Dedicated Bearer Activation Requested

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.4 Times of Successful Dedicated Bearer Activation

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.5 Times of Failed Dedicated Bearer Activation

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.6 Times of Dedicated Bearer Deactivation Requested

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.7 Times of Successful Dedicated Bearer Deactivation

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.8 Times of Bearer Modify Requested

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.9 Times of Successful Bearer Update Requested

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.10 Times of Failed Bearer Update Requested

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.11 Total Time of Dedicated Bearer Activation Procedure (ms)

SJ-20150919164026-011|2015-10-30 (R1.0) ZTE Proprietary and Confidential

2.1.12 Total Time of Default Bearer Activation Procedure (ms)