3GPP2 Evdo

3GPP2 S.S0093-0 v2.
3GPP2 S.S0093-0 Version 2.0 Version Date: January 18, 2006
cdma2000 Network Performance Measurement Types
Revision: 0
COPYRIGHT NOTICE
3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partners name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partners documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.
2006 3GPP2
3GPP2 S.S0093-0 v2.0
EDITOR(s) Said Soulhi, Said.Soulhi@ericsson.com Randall J. Scheer, rjscheer@lucent.com Yao Yizhi, yzyao@motorola.com
REVISION HISTORY
Version 1.0 Version 2.0
Initial Publication Point Release Publication
Dec 11, 2003 18 Jan 2006
2006 3GPP2
3GPP2 S.S0093-0 v2.0
Table of Contents
1 2 3 4 5 6 7 7.1 7.2
7.2.1.1 7.2.1.2 7.2.1.3
Scope............................................................................................ 10 References .................................................................................... 11 Abbreviations................................................................................ 14 General......................................................................................... 18 Definitions .................................................................................... 19 Measurement definition template .................................................. 21 Measurements related to the Radio Access Network ...................... 25 Common Measurements ............................................................25 Measurements related to BTS ....................................................25
Number of available CE................................................................................................................ 25 Duration of seizures of CE............................................................................................................ 25 Number of call failures due to resource assignment failures ......................................................... 26
7.2.1 BTS system resource measurements ........................................... 25
7.3
7.3.1.1 7.3.1.2 7.3.1.3 7.3.1.4
Measurements related to BSC ....................................................27

Number of incoming hard handoffs .............................................................................................. 27 Number of successful incoming hard handoffs.............................................................................. 27 Number of soft handoff leg addition attempts ............................................................................... 27 Number of successful soft handoff leg additions ........................................................................... 28
7.3.1 BSC handoff measurements........................................................ 27
7.3.2 BSC traffic measurements related to the PS domain.................... 28

7.3.2.1 7.3.2.2 7.3.2.3 7.3.2.4 7.3.2.5 7.3.2.6 7.3.2.7 7.3.2.8 7.3.2.9 7.3.2.10 7.3.2.11 7.3.2.12 7.3.2.13 7.3.2.14 7.3.2.15 7.3.2.16 Number of attempted PS calls ...................................................................................................... 28 Number of call-drops for PS domain service.................................................................................. 29 Number of requests for forward SCH ............................................................................................ 29 Number of successful assignments for forward SCH ..................................................................... 29 Number of requests for reverse SCH............................................................................................. 30 Number of successful assignments for reverse SCH ...................................................................... 30 Traffic volume carried by Walsh Codes on SCHs for PS domain service ......................................... 30 Traffic volume carried by Walsh Codes on FCHs for PS domain service ......................................... 31 Traffic volume carried on CEs which are seized by SCHs for PS domain service............................. 32 Number of forward RLP packets ............................................................................................... 32 Number of repeated forward RLP packets ................................................................................. 32 Number of reverse RLP packets ................................................................................................ 33 Number of repeated reverse RLP packets .................................................................................. 33 Number of failed requests for PS domain service....................................................................... 33 Number of attempted PS handoffs ............................................................................................ 34 Number of successful PS handoffs............................................................................................ 35
2006 3GPP2
Page ii
3GPP2 S.S0093-0 v2.0
7.3.3 BSC system resource measurements .......................................... 35

7.3.3.1 7.3.3.2 Number of available trunk circuits ............................................................................................... 35 Duration of seizures of A-Interface circuits ................................................................................... 36
7.4
7.4.1.1 7.4.1.2 7.4.1.3 7.4.1.4 7.4.1.5 7.4.1.6
Measurements related to Sector .................................................36

Number of attempted originating calls related to the CS domain ................................................... 36 Number of attempted call assignments to the CS domain ............................................................. 37 Number of paging responses related to the CS domain ................................................................. 37 Number of dropped calls related to the CS domain ....................................................................... 37 Traffic volume including handoffs................................................................................................. 38 Traffic volume of Walsh Codes...................................................................................................... 38
7.4.1 Sector traffic measurements related to the CS domain ................ 36
7.4.2 Sector traffic measurements related to the PS domain................. 39

7.4.2.1 7.4.2.2 7.4.2.3 7.4.2.4 7.4.2.5 Number of attempted originating calls related to the PS domain ................................................... 39 Number of attempted call assignments to the PS domain.............................................................. 39 Number of successful call assignments to the PS domain ............................................................. 40 Number of paging responses related to the PS domain.................................................................. 40 Number of dropped calls related to the PS domain........................................................................ 40
7.5
7.5.1.1 7.5.1.2 7.5.1.3 7.5.1.4 7.5.1.5 7.5.1.6 7.5.1.7 7.5.1.8
Measurements related to PCF ....................................................42

Number of successful access ........................................................................................................ 42 Number of unsuccessful access.................................................................................................... 42 Forward GRE bits ........................................................................................................................ 42 Reverse GRE bits ......................................................................................................................... 43 Number of RAN discarded reverse GRE packets............................................................................ 43 Number of PDSN discarded forward GRE packets ......................................................................... 44 Number of attempted PS transitions from dormant to active ......................................................... 44 Number of successful PS transitions from dormant to active......................................................... 44
7.5.1 PCF traffic measurements........................................................... 42
8 8.1
8.1.1.1 8.1.1.2 8.1.1.3 8.1.1.4 8.1.1.5 8.1.1.6 8.1.1.7 8.1.1.8 8.1.1.9
Measurements related to the Packet Core Network ........................ 46 Common Measurements ............................................................46
Number of octets received ............................................................................................................ 46 Number of unicast packets accepted ............................................................................................ 46 Number of non-unicast packets accepted ..................................................................................... 47 Number of inbound packets discarded.......................................................................................... 47 Number of malformed packets received ........................................................................................ 47 Number of packets discarded due to unknown protocol ................................................................ 48 Number of octets sent .................................................................................................................. 48 Number of unicast packets sent ................................................................................................... 49 Number of non-unicast packets sent ............................................................................................ 49 Number of outbound packets discarded.................................................................................... 50 Number of outbound erred packets .......................................................................................... 50
8.1.1 Interfaces Group Measurements ................................................. 46
8.1.1.10 8.1.1.11
2006 3GPP2
Page iii
3GPP2 S.S0093-0 v2.0
8.1.2 IP Group Measurements ............................................................. 50

8.1.2.1 8.1.2.2 8.1.2.3 8.1.2.4 8.1.2.5 8.1.2.6 8.1.2.7 8.1.2.8 8.1.2.9 8.1.2.10 8.1.2.11 8.1.2.12 8.1.2.13 8.1.2.14 8.1.2.15 8.1.2.16 Number of input packets received ................................................................................................ 50 Number of input datagrams discarded due to errors in their IP headers ........................................ 51 Number of input datagrams discarded due to invalid address ....................................................... 51 Number of forwarded input datagrams ......................................................................................... 52 Number of input datagrams discarded due to unknown protocol................................................... 52 Number of input datagrams discarded without appropriate reasons.............................................. 52 Number of input datagrams delivered to IP user protocol .............................................................. 53 Number of output datagrams requested ....................................................................................... 53 Number of datagrams discarded due to no route .......................................................................... 54 Number of output datagrams discarded for other reasons ......................................................... 54 Number of datagrams fragmented ............................................................................................ 54 Number of datagrams for which fragmentation failed ................................................................ 55 Number of fragments created ................................................................................................... 55 Number of IP fragments received .............................................................................................. 55 Number of IP datagrams reassembled....................................................................................... 56 Number of reassembly failures ................................................................................................. 56
8.2
8.2.1.1 8.2.1.2 8.2.1.3 8.2.1.4 8.2.1.5 8.2.1.6 8.2.1.7 8.2.1.8 8.2.1.9
Measurements related to the PDSN ............................................57

Number of successful MIP registrations in PDSN .......................................................................... 57 Number of attempted MIP registrations in PDSN........................................................................... 57 Number of registrations relayed from PDSN to HA ........................................................................ 57 Number of rejected registrations by the PDSN due to unspecified reason ...................................... 58 Number of rejected registrations by the PDSN due to administrative reason.................................. 58 Number of rejected registrations by the PDSN due to insufficient resource reason......................... 59 Number of rejected registrations by the PDSN due to MN authentication failure reason................. 59 Number of rejected registrations by the PDSN due to HA authentication failure reason ................. 60 Number of rejected registrations by the PDSN due to too long registration lifetime reason ............. 60 Number of rejected registrations by the PDSN due to poorly formed requests reason ................. 60 Number of rejected registrations replies by the PDSN due to poorly formed reply reason ........... 61 Number of rejected registrations by the PDSN due to unavailable encapsulation requested reason 61 Number of rejected registrations by the PDSN due to VJ compression reason............................ 62 Number of rejected registrations by the PDSN due to unreachable HA ...................................... 62 Number of registrations replies received by the PDSN ............................................................... 63 Number of valid registrations replies relayed to the MN by the PDSN ........................................ 63
8.2.1 MIP Measurements ..................................................................... 57
8.2.1.10 8.2.1.11 8.2.1.12 8.2.1.13 8.2.1.14 8.2.1.15 8.2.1.16
8.2.2 PPP Measurements ..................................................................... 63

8.2.2.1 8.2.2.2 8.2.2.3 8.2.2.4 8.2.2.5 Total number of PPP packets sent to MNs..................................................................................... 63 Total number of errored PPP packets............................................................................................ 64 Total number of discarded PPP packets ........................................................................................ 64 Total active/dormant connection time .......................................................................................... 65 Total number of PPP packets received from all MNs ...................................................................... 65
2006 3GPP2
Page iv
3GPP2 S.S0093-0 v2.0

8.2.2.6 8.2.2.7 8.2.2.8 8.2.2.9 8.2.2.10 8.2.2.11 Total number of dropped PPP sessions ......................................................................................... 65 Total number of active PPP sessions ............................................................................................. 66 Total number of dormant PPP sessions......................................................................................... 66 Total number of PPP setup requests ............................................................................................. 67 Total number of PPP successful connections............................................................................. 67 Total number of PPP setup failures ........................................................................................... 67
8.2.3 GRE Measurements .................................................................... 68

8.2.3.1 8.2.3.2 8.2.3.3 8.2.3.4 8.2.3.5 8.2.3.6 8.2.3.7 8.2.3.8 Total number of GRE packets transmitted by the PDSN................................................................ 68 Total number of GRE packets received by the PDSN ..................................................................... 68 Total number of bytes transmitted by the PDSN ........................................................................... 69 Total number of bytes received by the PDSN................................................................................. 69 Total number of errored GRE packets........................................................................................... 69 Total number of discarded GRE packets ....................................................................................... 70 Total number of GRE packets out of sequence .............................................................................. 70 Total number of GRE packets with no existing MIP binding .......................................................... 71
8.2.4 R-P Measurements...................................................................... 71

8.2.4.1 8.2.4.2 8.2.4.3 8.2.4.4 8.2.4.5 8.2.4.6 8.2.4.7 8.2.4.8 8.2.4.9 8.2.4.10 8.2.4.11 8.2.4.12 8.2.4.13 8.2.4.14 8.2.4.15 8.2.4.16 8.2.4.17 8.2.4.18 8.2.4.19 Total number of R-P registration requests .................................................................................... 71 Total number of R-P registration requests accepted ...................................................................... 71 Total number of R-P registration requests denied ......................................................................... 72 Total number of R-P deregistration requests received.................................................................... 73 Total number of successful R-P deregistration replies ................................................................... 73 Total number of R-P release connection requests.......................................................................... 73 Total number of successful R-P release connection replies............................................................ 74 Total number of current sessions ................................................................................................. 74 Total number of active R-P sessions ............................................................................................. 75 Total number of dormant R-P sessions ..................................................................................... 75 Total number of handoff sessions ............................................................................................. 75 Total number of successful intra-PDSN handoffs ...................................................................... 76 Total number of unsuccessful inter-PDSN handoffs .................................................................. 76 Total number of unsuccessful intra-PDSN handoffs .................................................................. 76 Total number of unsuccessful inter-PDSN handoffs .................................................................. 77 Total number of simple IP sessions........................................................................................... 77 Total number of MIP sessions................................................................................................... 78 Packet session set up time (Mean) ............................................................................................ 78 Packet session set up time (Maximum) ..................................................................................... 79
8.3
8.3.1.1 8.3.1.2 8.3.1.3 8.3.1.4 8.3.1.5
Measurements related to the HA ................................................79

Number of service requests accepted by HA.................................................................................. 79 Number of service requests denied by HA ..................................................................................... 80 Number of registration requests accepted by HA........................................................................... 80 Number of registration requests accepted by HA, but not supported by the MN binding ................ 80 Number of registration requests rejected by the HA due to unknown reasons................................ 81
8.3.1 MIP Measurements ..................................................................... 79
2006 3GPP2
Page v
3GPP2 S.S0093-0 v2.0

8.3.1.6 8.3.1.7 8.3.1.8 8.3.1.9 8.3.1.10 8.3.1.11 8.3.1.12 bindings 8.3.1.13 8.3.1.14 8.3.1.15 8.3.1.16 8.3.1.17 8.3.1.18 8.3.1.19 Number of registration requests rejected by the HA due to administrative reasons ........................ 81 Number of registration requests rejected by the HA due to insufficient resources .......................... 82 Number of registration requests rejected by the HA due to authentication failure.......................... 82 Number of registration requests rejected by the HA due to FA authentication failure..................... 82 Number of registration requests rejected by the HA due to identification mismatch ................... 83 Number of registration requests rejected by the HA due to poorly formed request ..................... 83 Number of registration requests rejected by the HA due to too many simultaneous mobility 84 Number of registration requests rejected by the HA due to unknown home agent addresses...... 84 Number of ARP sent by HA on behalf of the MN ........................................................................ 85 Number of proxy ARP responses sent by HA on behalf of the MN .............................................. 85 Number of registration replies received by HA........................................................................... 85 Number of deregistration requests............................................................................................ 86 Number of registration replies sent by HA................................................................................. 86 Number of registration replies sent by the HA in response to requests to deregister .................. 87
8.4
8.4.1.1 8.4.1.2 8.4.1.3 8.4.1.4 8.4.1.5 8.4.1.6 8.4.1.7 8.4.1.8 8.4.1.9
Measurements related to the AAA ..............................................87

Number of packets received on the accounting port ...................................................................... 87 Number of packets received with unknown addresses................................................................... 87 Total packets of duplicated billing request received....................................................................... 88 Total packets of billing responses sent.......................................................................................... 88 Total of malformed packets received ............................................................................................. 89 Total packets of billing requests with illegal signature attributes................................................... 89 Total of packets dropped .............................................................................................................. 89 Total of packets received and not recorded ................................................................................... 90 Total of packets received with unknown type ................................................................................ 90
8.4.1 RADIUS Accounting Port Measurements ..................................... 87
8.4.2 RADIUS Authentication Port Measurements................................ 91

8.4.2.1 8.4.2.2 8.4.2.3 8.4.2.4 8.4.2.5 8.4.2.6 8.4.2.7 8.4.2.8 8.4.2.9 8.4.2.10 Number of packets received on the authentication port ................................................................ 91 Number of packets received with unknown address...................................................................... 91 Total packets of duplicated access request received ...................................................................... 91 Total packets of access accepted response sent ............................................................................ 92 Total packets of Access-Reject packets sent.................................................................................. 92 Total packets of Access-Challenge packets sent ............................................................................ 92 Total packets of malformed packets sent ...................................................................................... 93 Total packets of authentication requests with illegal signature attributes...................................... 93 Total packets of dropped .............................................................................................................. 94 Total packets received with unknown type................................................................................ 94
9 9.1
9.1.1.1 9.1.1.2
Measurements related to the Circuit Core Network........................ 95 Measurements related to the MSC .............................................95
Number of page requests.............................................................................................................. 95 Number of successful page requests............................................................................................. 95
9.1.1 MSC Basic Measurement ............................................................ 95
2006 3GPP2
Page vi
3GPP2 S.S0093-0 v2.0

9.1.1.3 9.1.1.4 Number of location registration requests ...................................................................................... 95 Number of successful location registrations.................................................................................. 96
9.1.2 Traffic Measurements ................................................................. 96

9.1.2.1 9.1.2.2 9.1.2.3 9.1.2.4 9.1.2.5 9.1.2.6 9.1.2.7 9.1.2.8 9.1.2.9 9.1.2.10 9.1.2.11 9.1.2.12 9.1.2.13 9.1.2.14 9.1.2.15 9.1.2.16 9.1.2.17 9.1.2.18 9.1.2.19 9.1.2.20 9.1.2.21 9.1.2.22 9.1.2.23 9.1.2.24 9.1.2.25 9.1.2.26 9.1.2.27 9.1.2.28 9.1.2.29 9.1.2.30 9.1.2.31 9.1.2.32 9.1.2.33 9.1.2.34 9.1.2.35 9.1.2.36 9.1.2.37 9.1.2.38 9.1.2.39 Number of attempted originating calls .......................................................................................... 96 Number of successful originating calls.......................................................................................... 97 Number of answered originating calls ........................................................................................... 97 Number of failed originating calls for various reasons ................................................................... 97 Number of MSC internal call attempts.......................................................................................... 98 Number of successful MSC internal calls...................................................................................... 98 Number of MSC answered internal calls ....................................................................................... 99 Number of failed internal calls...................................................................................................... 99 Number of terminating call attempts .......................................................................................... 100 Number of Successful Mobile Terminating Calls ..................................................................... 100 Number of Answered Terminating calls................................................................................... 101 Number of failed terminating calls for various reasons ............................................................ 101 Number of incoming call attempts .......................................................................................... 102 Number of successful Incoming Calls ..................................................................................... 102 Number of answered incoming calls........................................................................................ 102 Number of failed incoming calls for various reasons................................................................ 103 Number of outgoing call attempts ........................................................................................... 103 Number of successful outgoing Calls ...................................................................................... 104 Number of outgoing call answers ............................................................................................ 104 Number of failed outgoing calls for various reasons................................................................. 104 Number of transit call attempts .............................................................................................. 105 Number of successful transit Calls ......................................................................................... 105 Number of transit call answers............................................................................................... 106 Number of failed transit calls for various reasons ................................................................... 106 Number of originating outgoing call attempts.......................................................................... 107 Number of successful originating outgoing calls...................................................................... 107 Number of originating outgoing call answers........................................................................... 108 Number of failed originating outgoing calls for various reasons ............................................... 108 Number of incoming terminating call attempts ....................................................................... 109 Number of Successful Incoming Terminating Calls ................................................................. 109 Number of incoming terminating call answer .......................................................................... 109 Number of failed incoming terminating calls for various reasons ............................................. 110 Successful Traffic Volume for Mobile Originating Calls............................................................ 110 Successful traffic volume for MSC calls .................................................................................. 111 Successful Traffic Volume For Mobile Terminating Calls ......................................................... 112 Successful traffic volume for incoming calls............................................................................ 112 Successful traffic volume for outgoing calls............................................................................. 113 Successful traffic volume for transit calls................................................................................ 113 Traffic volume for successful originating outgoing calls ........................................................... 114
2006 3GPP2
Page vii
3GPP2 S.S0093-0 v2.0

9.1.2.40 9.1.2.41 9.1.2.42 Traffic Volume For Successful Incoming Terminating Calls ..................................................... 114 Occupation traffic volume of out-trunk calls ........................................................................... 115 Occupation traffic volume of incoming trunk calls .................................................................. 115
9.1.3 Handoff Measurements ............................................................. 116

9.1.3.1 9.1.3.2 9.1.3.3 9.1.3.4 Number of outgoing handoff requests ......................................................................................... 116 Number of successful outgoing handoff requests ........................................................................ 116 Number of incoming handoff requests ........................................................................................ 117 Number of successful incoming handoff requests ....................................................................... 117
9.1.4 QoS Measurements................................................................... 118

9.1.4.1 9.1.4.2 9.1.4.3 Mean time to set up call service ................................................................................................. 118 Mean call duration ..................................................................................................................... 118 Mean Trunk Seizure Duration .................................................................................................... 119
9.1.5 SMS Measurements .................................................................. 120

9.1.5.1 9.1.5.2 9.1.5.3 9.1.5.4 Number of originating Point-to-point SMS attempts .................................................................... 120 Number of successful originating Point-to-point SMS.................................................................. 120 Number of terminating Point-to-point SMS attempts................................................................... 121 Number of successful terminating Point-to-point SMS attempts.................................................. 121
9.2
9.2.1.1 9.2.1.2 9.2.1.3 9.2.1.4
Circuit End Point Subgroup Measurements .............................121

Number of outgoing call attempts............................................................................................... 122 Number of outgoing call occupations .......................................................................................... 122 Number of answers to outgoing calls .......................................................................................... 122 Total number of available out-trunks ......................................................................................... 123
9.2.1 Outgoing call measurements..................................................... 122
9.2.2 Incoming Call Measurements .................................................... 123

9.2.2.1 9.2.2.2 9.2.2.3 9.2.2.4 9.2.2.5 Number of incoming trunk call occupations................................................................................ 123 Total number of blocked out-trunks ........................................................................................... 124 Number of answers to incoming trunk calls................................................................................ 124 Total number of available incoming trunks ................................................................................. 125 Total number of blocked incoming trunks................................................................................... 125
10
Measurements Related to the Service Network ............................ 126 10.1 Measurements related to the MMS Relay/Server ......................126 10.1.1 10.1.2
10.1.2.1 10.1.2.2 10.1.2.3 10.1.2.4 10.1.2.5 10.1.2.6 10.1.2.7
Background Information on the Request Status [21]............... 128 MM1 ...................................................................................... 129
Number of Multimedia Messages submit requests received by MMS Relay/Server ................... 129 Number of Multimedia Messages submit responses sent by MMS Relay/Server....................... 130 Number of Multimedia Messages notification requests sent by MMS Relay/Server .................. 130 Number of Multimedia Messages notification responses received by MMS Relay/Server .......... 131 Number of Multimedia Messages retrieve requests received by MMS Relay/Server .................. 131 Number of Multimedia Messages retrieve responses sent by MMS Relay/Server ...................... 132 Number of Multimedia Messages acknowledgement requests received by MMS Relay/Server... 132
2006 3GPP2
Page viii
3GPP2 S.S0093-0 v2.0

10.1.2.8 10.1.2.9 10.1.2.10 10.1.2.11 10.1.2.12 Number of Multimedia Messages forward requests received by MMS Relay/Server .................. 133 Number of Multimedia Messages forward responses sent by MMS Relay/Server...................... 133 Number of Multimedia Messages delivery report requests sent by MMS Relay/Server.............. 133 Number of Multimedia Messages read reply recipient requests received by MMS Relay/Server 134 Number of Multimedia Messages read reply originator requests sent by MMS Relay/Server..... 134
10.1.3
10.1.3.1 10.1.3.2 10.1.3.3 10.1.3.4 10.1.3.5 10.1.3.6 10.1.3.7 10.1.3.8 10.1.3.9 10.1.3.10 10.1.3.11 10.1.3.12
MM4 ...................................................................................... 135

Number of Multimedia Messages forward requests received by MMS Relay/Server .................. 135 Number of Multimedia Messages forward requests sent by MMS Relay/Server ........................ 135 Number of Multimedia Messages forward responses received by MMS Relay/Server ................ 136 Number of Multimedia Messages forward responses sent by MMS Relay/Server...................... 136 Number of Multimedia Messages delivery report requests received by MMS Relay/Server........ 137 Number of Multimedia Messages delivery report requests sent by MMS Relay/Server.............. 137 Number of Multimedia Messages delivery report responses received by MMS Relay/Server ..... 137 Number of Multimedia Messages delivery report responses sent by MMS Relay/Server ........... 138 Number of Multimedia Messages read reply requests received by MMS Relay/Server .............. 138 Number of Multimedia Messages read reply requests sent by MMS Relay/Server .................... 139 Number of Multimedia Messages read reply responses received by MMS Relay/Server ............ 139 Number of Multimedia Messages read reply responses sent by MMS Relay/Server .................. 140
Annex A: 3GPP2 Service Options ................................................................. 141
2006 3GPP2
Page ix
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13
Scope
This document defines the Performance Measurement Types applicable to CDMA and cdma20001 systems. This document contains portions of material copied from 3GPP document number TS 32.403. The copyright on the 3GPP document is owned by the Organizational Partners of 3GPP (ARIB - Association of Radio Industries and Businesses, Japan; CCSA China Communications Standards Association, China; ETSI European Telecommunications Standards Institute; Committee T1, USA; TTA Telecommunications Technology Association, Korea; and TTC Telecommunication Technology Committee, Japan), which have granted license for reproduction and for use by 3GPP2 and its Organizational Partners.
cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States
2006 3GPP2
Page 10
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
References [01] 3GPP2 S.S0028-001-B "OAM&P for cdma2000 (3GPP R5 Delta Specification)"
http://www.3gpp2.org/Public_html/specs/index.cfm
[02] 3GPP2 S.S0028-003-B [03] 3GPP2 S.S0028-004-B [05] 3GPP TS 32.403
"OAM&P for cdma2000 (3GPP2 Core NRM IRP)"

"OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)" http://www.3gpp2.org/Public_html/specs/index.cfm "Performance Management (PM); Performance Measurements UMTS and Combined UMTS/GSM"; (Release 5) (Release 6)
http://www.3gpp.org/ftp/specs/latest
[06] 3GPP2 S.R0005-B
"Network Reference Model for cdma2000 Spread Spectrum Systems; Revision: B"; Version 1.0
[07] 3GPP2 S.S0028-A
"OAM&P for cdma2000 (3GPP R4 Delta Specification)"

[08] 3GPP2 S.R0037
"IP Network Architecture Model for cdma2000 Spread Spectrum Systems"; Version 3.0
[09] 3GPP TS 23.107
"Quality of Service (QoS) Concept and Architecture"; (Release 5) (Release 6)

http://www.3gpp.org/ftp/specs/latest
[10] 3GPP2 A.S0017
"Interoperability Specification (IOS) for cdma2000 Access Network Interfaces Part 7 (A10 and A11 Interfaces) "(Revision A) (Revision B) (Revision C)
[11] RFC 2006 [12] RFC 2011
"The Definitions of Managed Objects for IP Mobility Support using SMI"; Version 2 "SNMPv2 Management Information Base for the Internet Protocol using SMI"; Version 2[13] RFC 2012 "SNMPv2 Management Information Base for the Transmission Control Protocol using SMI"; Version 2 "SNMPv2 Management Information Base for the User Datagram Protocol using SMI"; Version 2 "RADIUS Authentication Client MIB" "RADIUS Authentication Server MIB" "RADIUS Accounting Server MIB"
[14] RFC 2013 [15] RFC 2618 [16] RFC 2619 [17] RFC 2621
2006 3GPP2
Page 11
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
[18] RFC 2863 [19] RFC 1213 [20] 3GPP2 S.R0064-A v1.0
"The Interfaces Group MIB" "Management Information Base for Network Management of TCP/IP-based Internets: MIB-II" "Multimedia Messaging Services (MMS) Stage 1 Requirements"; Version 1.0
[21] 3GPP2 X.S0016-200-0 v2.0 "MMS Stage 2 Functional Description"; Version 2.0
[22] 3GPP2 X.S0004-000-E [23] 3GPP2 A.S0014-A
"Introduction to TIA-41"; Version 2.0 "Interoperability Specification (IOS) for cdma2000 Access Network Interfaces Part 4 (A1, A2 and A5 Interfaces) (IOSv4.3)"
[25] 3GPP2 C.S0005-A [26] 3GPP2 C.S0017-012-A
"cdma2000 Layer 3 Signaling Revision A"

"Data Service Options for Spread Spectrum Systems: Service Options 33 and 66"
[27] 3GPP2 C.S0017-010-A
"Data Service Options for Spread Spectrum Systems: Radio Link Protocol Type 3"; Version 2.0 http://www.3gpp2.org/Public_html/specs/index.cfm "Interoperability Specification (IOS) for cdma2000 Access Network Interfaces Part 5 (A3 and A7 Interfaces)"; (Revision A) (Revision B) (Revision C) http://www.3gpp2.org/Public_html/specs/index.cfm "Interoperability Specification (IOS) for cdma2000 Access Network Interfaces Part 6 (A8 and A9 Interfaces)"; (Revision A) (Revision B) (Revision C) http://www.3gpp2.org/Public_html/specs/index.cfm "Generic Network Information Model";
[28] 3GPP2 A.S0015
[29] 3GPP2 A.S0016
[30] ITU-T Recommendation M.3100 1995 [31] 3GPP2 A.S0007-A v2.0
"Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Access Network Interfaces Revision A"; Version 2.0
[32] 3GPP2 A.S0008-0 v3.0
"Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Access Network Interfaces Revision 0"; Version 3.0
[33] ITU-T Recommendation Q.764 Signalling System No. 7 ISDN User Part Signalling Procedures, 1999
2006 3GPP2
Page 12
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
[34] ITU-T Recommendation Q.723 Specifications of Signalling System No. 7 Telephone User Part, 1988 [35] ITU-T Recommendation Q.724 Specifications of Signalling System No. 7 Telephone User Part - Signalling Procedures, 1988 [36] 3GPP2 X.S0004-540-E [37] 3GPP2 A.S0013-C MAP Operations Signaling Protocols, Version 1.0
Interoperability Specification (IOS) for cdma2000 Access Network Interfaces Part 3 Features (3G-IOS v5.0), Version 1.0
[38] 3GPP2 C.R1001-E
Administration of Parameter Value Assignments for cdma2000 Spread Spectrum Standards

[39] 3GPP2 S.S0028-001-C
"OAM&P for cdma2000 (3GPP R6 Delta Specification)"

[40] 3GPP2 S.S0028-003-C [41] 3GPP2 S.S0028-004-C
"OAM&P for cdma2000 (3GPP2 Core NRM IRP)"

"OAM&P for cdma2000 (3GPP2 Radio Access NRM IRP)" http://www.3gpp2.org/Public_html/specs/index.cfm
2006 3GPP2
Page 13
3GPP2 S.S0093-0 v2.0
Abbreviations 1X Evolution Data Only 1X Evolution Data and Voice Third Generation 3rd Generation Partnership Project 3rd Generation Partnership Project 2 Authentication, Authorization and Accounting Authentication Center Address complete message Answer signal, charge See [22] Answer Message Answer signal, no charge Association of Radio Industries and Businesses (Japan) Address Resolution Protocol Asynchronous Transfer Mode Authorization Request Breakout Gateway Control Function Border Router Base Station subsystem [see also [06]) Base Station Controller BS Management Application Part Base Transceiver Station Clear-back signal Cumulative Counter China Communications Standards Association Code Division Multiple Access Channel Element CGC Circuit-group-congestion signal Connection Management Core Network Circuit Switched Call Session Control Function Critical Vendor/Organization Specific Extension Discrete Event Registration Destination Point Code Data Ready to Send Direct Transfer Application Part Extended Simple Mail Transfer Protocol European Telecommunications Standards Institute Foreign Agent Fundamental Channel Frame Erasure Rate Goal Question Metric Generic Routing Encapsulation Global System for Mobile Communication
Page 14
1X EVDO 1X EVDV 3G 3GPP 3GPP2 AAA AC ACM ANC Anchor MSC ANM ANN ARIB ARP ATM AuthReq BGCF BR BS BSC BSMAP BTS CBK CC CCSA CDMA CE CGC CM CN CS CSCF CVSE DER DPC DRS DTAP ESMTP ETSI FA FCH FER GQM GRE GSM
2006 3GPP2
3GPP2 S.S0093-0 v2.0
HA HLR HO IAI IAM ICMP IETF IMSI IOS IP IPCP IRATHO IS ISUP ITU-T LCP MAP Mb MC MGCF MGW MIB MIME MIP MM MMS MN MRFC MRFP MS MSC MSU MTP MTP3 NAM OAM&P OAS OP OPC OSCS PCF PDE PDF PDSN PM PPP
2006 3GPP2
Home Agent Home Location Register Handoff Initial Address message with additional information Initial Address message Internet Control Message Protocol Internet Engineering Task force International Mobile Subscriber Identity Interoperability Specification Internet Protocol IP Control Protocol Inter-Radio Access Technology Handover Interface Specification ISDN User Part International Telecommunication Union - Telecommunications Standardization Sector Link Control Protocol Mobile Application Part Mega Bit Messaging Center Media Gateway Control Function Media Gateway Management Information Base Multipurpose Internet Mail Extensions Mobile Internet Protocol Mobility Management Multimedia Messaging Service Mobile Node Media Resource Function Controller Media Resource Function Processor Mobile Station Mobile Switching Centre Message Signal Units Message Transfer Part Message Transfer Part 3 Network Architecture Model Operations, Accounting, Maintenance & Provisioning OSA Application Server Organizational Partner Originating Point Code OSA Service Capability Server Packet Control Function Position Determining Entity Policy Decision Function Packet Data Serving Node Performance Management Point-to-Point Protocol
Page 15
3GPP2 S.S0093-0 v2.0
PS PS PSID PSTN QoS RADIUS RAN REG REL RF RFC RLP RP RRC RRQ SAS SCCP SCH SEC Serving MSC SGW SI SIF SIG SIO SIP SIP SLS SM SMDPP smdpp SMI SMIL SMS SMS-MO SMTP SUB Target MSC TCAP TCE TCH TCP TIA TP TRM TS TTA
2006 3GPP2
Position Server Packet Switch Private System Identifier Public Switched Telephone Network Quality of Service Remote Authentication Dial In User Service Radio Access Network Registration Release Radio Frequency Request For Comment Radio Link Protocol Radio-Packet interface (A-quater) Radio Resource Control Registration Request Session Initiation Protocol Application Server Signaling Connection Control Part Supplemental Channel Security See [22] Signaling Gateway Status Inspection Signaling Information Field Signaling Service Information Octet Session Initiation Protocol Simple IP Signaling Link Selection Session Management Message SMSDeliveryPointToPoint INVOKE Message SMSDeliveryPointToPoint RETURN RESULT Structure of Management Information Synchronized Multimedia Integration Language Short Message Service Short Message Service Mobile Originating Simple Mail Transfer Protocol Subscriber See [22] Transaction Capabilities Application Part Traffic Channel Element Traffic Channel Transmission Control Protocol Telecommunications Industry Association (North America) Termination Point Traffic Management Technical Specification Telecommunications Technology Association (Korea)
Page 16
3GPP2 S.S0093-0 v2.0
TTC TUP UA UE Um UMTS VAS VJ VLR WAP 1
Telecommunications Technology Committee (Japan) Telephone User Part User Agent User Equipment Air Interface [06] Universal Mobile Telecommunications System Value-added Services Van Jacobson header compression Visitor Location Register Wireless Application Protocol
2006 3GPP2
Page 17
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12
General
The present document describes the measurement types for CDMA and cdma2000 network. The measurement types identified in this document can be (a) defined by 3GPP2 and (b) defined by other standards bodies and re-used by 3GPP2. Measurement types defined in this document may be supported by CDMA and cdma2000 systems pending applicability and system capacity limits. Nevertheless if such measurement types are provided then definitions within this specification shall apply. Note that 3GPP2 Performance Management concepts and requirements are defined within revisions of S.S0028 ([01], [07], [39]).
2006 3GPP2
Page 18
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
Definitions
For the purposes of the document, the following terms and definitions apply: erlang The erlang is a unit of traffic density in a telecommunications system. One erlang is the equivalent of one call (including call attempts and holding time) in a specific channel for 3600 seconds in an hour. The 3600 seconds need not be, and generally are not, in a contiguous block. Forward and Reverse Throughput Forward and reverse throughput is defined as the effective data rate excluding re-transmissions. In addition for the reverse link the throughput excludes data that is impossible to decode due to high FER or other poor RF conditions. Measurement User Community This document identifies several measurement user communities that are users of the measurement types. Each measurement type should be defined to address the needs of at least one of these measurement user communities. This document identifies the following user communities. Network Operators Business Community Network Operators Maintenance Community Network Operators Traffic Engineering Community Network Operators Customer Care Community Equipment Vendors Performance Modeling Community Equipment Vendors Development Engineering Community
The measurement user communities names are a composite of the various terms used in the industry and might be subject to modification or refinement in future releases. A comprehensive description of measurement communities as well as a top-down performance measurement definition process based on the Goal Question Metric (GQM) approach are provided in Annex B of 3GPP TS 32.403 [05]. Measurement family The names of the measurement types defined in the document begin with a prefix of the measurement family name. This prefix identifies all measurement types that relate to a given functionality and its use may facilitate performance measurement administration. The list of prefix used in the document is: CE (measurements related to Channel Elements). GRE (measurements related to GRE)
Page 19
2006 3GPP2
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
HHO (measurements related to Hard Handover). HO (measurements related to Handover) IMEI (measurements related to IMEI verification). IP (measurements related to Simple IP protocol) IRATHO (measurements related to Inter-Radio Access Technology Handover) MIB (measurements from IETF) MIP (measurements related to Mobile IP protocol) MM (measurements related to Mobility Management) MMS (measurements related to Multimedia Messaging Services) PPP (measurements related to Point-to-Point Protocol) QoS (measurements related to Quality of Service) RAB (measurements related to Radio Access Bearer management). RAD (measurements related to RADIUS protocol) REG (measurements related to Registrations) RP (measurements related to R-P protocol) RRC (measurements related to Radio Resource Control) SEC (measurements related to Security) SHO (measurements related to Soft Handover). SIG (measurements related to Signaling) SIP (measurements related to Session Initiation Protocol) SM (measurements related to Session Management) SMS (measurements related to Short Messaging System) SUB (measurements related to Subscriber Management) TRM (measurements related to Traffic Management)
Vendor-specific cdma2000 measurement names shall begin with the VS prefix. In addition, it is recommend that a measurement name prefix be added to the performance measurement name (as an example, VS.HO.Reject.NoResource or VS.vendor.HO.Reject.NoResource).
2006 3GPP2
Page 20
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
Measurement definition template
The following is the template used to specify the measurement types. C.x.y. Measurement Name (clause header) This is a descriptive name of the measurement type. The measurement name shall use a string representing concatenated words without spaces. First letter for all words are capitalized. Letters of abbreviations are capitalized (e.g. PDSN). This naming rule is not applicable to measurement names from other standardization bodies (e.g. IETF). A measurement name can have one or more measurement types (e.g. the number of home subscribers (MM.NbrHomeSub) has 3 related measurement types: MM.NbrHomeSub (combined Simple IP and Mobile IP), MM.NbrHomeSub.IP for Simple IP subscribers and MM.NbrHomeSub.MIP for mobile IP subscribers. a) b) Description This contains an explanation of the measurement type. Collection Method This describes the different kinds of the measurement data captured in measurement types: CC (Cumulative Counter), are incremental counters triggered by the occurrence of the measured event; GAUGE (dynamic variable), used when data being measured can vary up or down during the period of measurement; DER (Discrete Event Registration), when data related to a particular event are captured every nth event is registered, where n can be 1 or larger; SI (Status Inspection), when a mechanism for high frequency sampling of internal counters at pre-defined rates is used. There are two allowed methods for counting DER performance measurement data. It is vendor-specific which method is used for a specific performance measurement. 1. Event Driven Collection Method: In this DER method, performance measurement data for a particular activity is put into the calculation when the event has completed. As an example, in the figure below, Activity #2 would only be used for the calculation of the performance measurement at the granularity period past the listed granularity period.
2006 3GPP2
Page 21
3GPP2 S.S0093-0 v2.0
Granularity Period
counted counted
Time
Activity #1 Start Activity #2 Start Activity #3 Start Start End Activity #4 End Counted in future granularity period End End
1 2 3 4 5 6 7 8
Figure 1. DER Collection Method #1 Event Driven Collection 2. Event and Granularity Period Driven Collection: In this DER method, performance measurement data for a particular activity is put into the calculation at each granularity period boundary (when the event has not yet completed), and when the event has completed. As an example, in the figure below, Activity #2 would be put into the calculation in three separate granularity periods.
Granularity Period
counted counted counted
Time
Activity #1 Start Activity #2 Start Activity #3 Start End Activity #4 Start End End End
Counted in earlier granularity period
Counted in future granularity period
9 10 11 12 13 14 15 16 17 18
Figure 2. DER Collection Method #2 Event and Granularity Period Driven Collection For both DER collection methods, the measurement data for individual activities, used for part of the calculation, are cleared at the beginning of the granularity period. c) Condition This specifies the condition that causes the measurement data to be updated. This can be defined by identifying protocol related trigger events for updating the value of the measurement data. If it is not possible to
2006 3GPP2
Page 22
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 h) g) f) e) d)
give a precise condition, then the conditional circumstances leading to the (value of the measurement data) update are stated. Measurement Result (measured value(s), Units) This identifies the syntax of the measurement data, e.g. an integer. Measurement Type This specifies a short form of the measurement name. Measurement result files use these to identify the measurement type. The measurement type is a sequence of items separated by dots. The items, of the sequence, are arranged from general to specific in terms of information. The first item identifies the measurement family (e.g. HO, GRE, RP). The second item identifies the name of the measurement itself. Depending on the measurement type, additional items may be present to specify sub-counters (failure causes, traffic classes, min, max, avg). In case of multiple additional items, they are separated by dot. When these sub counters are present, they must be fully described or a reference to a standard must be made.
Note that the values of a measurement type do not depend on the related collection method (CC, SI, GAUGE, DER). For instance, a gauge collected counter does not necessarily provide min, max, average values. Measurement Object Class This identifies the object class (e.g. Cell, PdsnFunction, HaFunction) where the subject measurement type is related to. The object class definition is in [02], [03], [07], [40] and [41]. Switching Technology This identifies the Switching domain(s) that this measurement type is applicable to i.e. Circuit Switched and/or Packet Switched. Generation The generation determines if it concerns a cdma2000 1X, cdma2000 1X EV-DO, cdma2000 1X EV-DV measurement or all of them. cdma2000 1X: pure cdma2000 1X measurement; it only counts cdma2000 1X events. cdma2000 1X EV-DO: pure cdma2000 1X EV-DO measurement; it only counts cdma2000 1X EV-DO events. cdma2000 1X EV-DV: pure cdma2000 1X EVDV measurement (related to usage of the Forward Packet Data Channel (PDCH)); it only counts cdma2000 1X EV-DV events.
2006 3GPP2
Page 23
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 i)
ALL: measurement applicable to cdma2000 systems, but regardless of whether the measured event occurred on the cdma2000 1X, cdma2000 1X EV-DO or cdma2000 1X EV-DV. Purpose This optional identifies the user of the measurement. It contains one or more measurement user community names (see definition of Measurement User Communities).
2006 3GPP2
Page 24
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
Measurements related to the Radio Access Network
7.1 Common Measurements To be defined in a new revision or version of this specification. 7.2 Measurements related to BTS 7.2.1 BTS system resource measurements 7.2.1.1 Number of available CE A. This measurement provides the number of available CEs, which are not broken down, including the CEs seized by traffic channels and CEs seized by overhead channels. B. GAUGE C. This measurement will be increased on transition of a CE from unavailable (can not be assigned) into available (can be assigned), decreased on transition of a CE from available (can be assigned) into unavailable (can not be assigned). D. An integer value E. CE.nbrAvailCe F. BtsFunction G. Valid for circuit switched and packet switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.2.1.2 Duration of seizures of CE A. This measurement provides the duration of seizures of CEs, including the duration during which CEs are seized by traffic channels and the duration during which CEs are seized by overhead channels (in erlang). B. DER (n=1) C. This measurement is obtained by summing the duration of seizure(s) of all CEs in this BTS. The duration of seizure(s) for each CE is calculated by accumulating the seizure time intervals between the CE is successfully assigned, and the CE is freed over a granularity period (noting that a CE is considered freed when released from traffic). The accumulator shall be re-initialized at the beginning of each granularity period. D. A value of type Real E. CE.durCeSeizure
2006 3GPP2
Page 25
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
F. BtsFunction G. Valid for circuit switched and packet switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.2.1.3 Number of call failures due to resource assignment failures A. This measurement provides the number of call failures due to resource assignment failure. This parameter indicates the total number of unsuccessful assignments for mobile subscribers due to being short of Walsh Codes, being short of power, being short of TCH, being short of transmission circuits from BTS to BSC, and all kinds of other reasons, etc. B. CC C. The BS fails to assign the resources for mobile subscribers for voice service, SMS or handoffs due to the shortage of Walsh Codes, power, CEs, transcoders or transmission links from BTS to BSC, etc. D. An integer value E. RRC.failCallsByBlock F. BtsFunction G. Valid for circuit switched and packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 26
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
7.3 Measurements related to BSC 7.3.1 BSC handoff measurements Note: the measurements defined in this section are only related to voice service. 7.3.1.1 Number of incoming hard handoffs A. This measurement provides the attempted number of incoming hard handoffs (considering both inter and intra handoffs). B. CC C. The target BS allocates radio resources for the MS, which request hard handoff into the target BS [25]. D. An integer value E. HO.attIncHardHo F. BscFunction G. Valid for circuit switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.1.2 Number of successful incoming hard handoffs A. This measurement provides the number of successful incoming hard handoffs (considering both inter and intra handoffs). B. CC C. Receipt by the target BS from MS of an Um message Handoff Completion or Extended Handoff Completion, indicating the successful incoming hard handoff [25]. D. An integer value E. HO.succIncHardHo F. BscFunction G. Valid for circuit switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.1.3 Number of soft handoff leg addition attempts A. This measurement provides the attempted number of soft handoff leg addition attempts (considering both inter and intra handoffs). B. CC
2006 3GPP2
Page 27
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. Transmission of a Um message Handoff Direction, Extended Handoff Direction, General Handoff Direction or Universal Handoff Direction from the target BS to MS, which requires MS to add the legs [25]. D. An integer value E. HO.attSoftHoAddition F. BscFunction G. Valid for circuit switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.1.4 Number of successful soft handoff leg additions A. This measurement provides the number of successful soft handoff leg additions (considering both inter and intra handoffs). B. CC C. Receipt by the target BS from MS of an Um message Handoff Completion or Extended Handoff Completion, indicating the successful soft handoff leg addition [25]. D. An integer value E. HO.succSoftHoAddition F. BscFunction G. Valid for circuit switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2 BSC traffic measurements related to the PS domain 7.3.2.1 Number of attempted PS calls A. This measurement provides the number of attempted calls for PS domain service. B. CC C. Receipt of Um message Origination by the BS from an MS [25], with Service Option set to 33 (see [38]) indicating cdma2000 high speed packet service, which excludes the attempted handoffs and the calls when the Packet Data Session State is Dormant (see also [26]). D. An integer value E. RRC.attCallsPs F. BscFunction
2006 3GPP2 Page 28
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.2 Number of call-drops for PS domain service A. This measurement provides the total number of call-drops for PS domain service due to the errors of radio, MSC or PDSN. B. CC C. On drop of the PS call due to failure of the radio, MSC or PDSN. D. An integer value E. RRC.nbrCallDropPs F. BscFunction G. Valid for packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.3 Number of requests for forward SCH A. This measurement provides the number of requests for forward SCH. B. CC C. On the attempt of the BS to assign the forward SCH. D. An integer value E. RRC.attFschAssign F. BscFunction G. Valid for packet switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.4 Number of successful assignments for forward SCH A. This measurement provides the total number of successful assignments for forward SCH, which include assignments that match the requested rate or mismatch the requested rate. B. CC C. On successful assignment of the forward SCH. D. An integer value
2006 3GPP2
Page 29
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
E. RRC.succFschAssign F. BscFunction G. Valid for packet switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.5 Number of requests for reverse SCH A. This measurement provides the number of requests for reverse SCH. B. CC C. On the attempt of assignment of the reverse SCH. D. An integer value E. RRC.attRschAssign F. BscFunction G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.6 Number of successful assignments for reverse SCH A. This measurement provides the total number of successful assignments for reverse SCH, which include assignments that match the requested rate or mismatch the requested rate. B. CC C. On successful assignment of the reverse SCH. D. An integer value E. RRC.succRschAssign F. BscFunction G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.7 Traffic volume carried by Walsh Codes on SCHs for PS domain service A. This measurement provides the traffic volume carried by Walsh Codes on SCHs for PS domain service (in erlang). E.g., if the SCH is 2X, the traffic volume of the SCH will be calculated on 2 Walsh Codes.
2006 3GPP2 Page 30
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
B. DER (n=1) C. This measurement is obtained by summing the traffic for PS service on all SCHs; The traffic on each SCH is calculated by accumulating the seizure time intervals between the SCH is successfully assigned, and the SCH is released over a granularity period, the end value of this time will be divided by the granularity period, and then be convert to the traffic volume according to the Walsh Code of the SCH. The accumulator shall be re-initialized at the beginning of each granularity period. D. A value of type Real E. RRC.trafficByWalshPsSch F. BscFunction G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.8 Traffic volume carried by Walsh Codes on FCHs for PS domain service A. This measurement provides the traffic volume carried by Walsh Codes on FCHs for PS domain service (in erlang). For example if the FCH is 8X based, then the traffic volume of the FCH will be calculated on 8 Walsh Codes. B. DER (n=1) C. This measurement is obtained by summing the traffic for PS service on all FCHs. The traffic on each FCH is calculated by accumulating the seizure time intervals between the FCH is successfully assigned, and the FCH is released over a granularity period, the end value of this time will be divided by the granularity period, and then be convert to the traffic volume according to the Walsh Code of the FCH. The accumulator shall be re-initialized at the beginning of each granularity period. D. A value of type Real E. RRC.trafficByWalshPsFch F. BscFunction G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 31
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
7.3.2.9 Traffic volume carried on CEs which are seized by SCHs for PS domain service A. This measurement provides the traffic volume carried on CEs which are seized by SCHs for PS domain service (in erlang). B. DER (n=1) C. This measurement is obtained by summing the traffic for PS service on all CEs seized by SCHs; The traffic on each CE seized by SCH is calculated by accumulating the seizure time intervals between the CE is successfully assigned, and the CE is freed over a granularity period, the end value of this time will be divided by the granularity period to be convert to the traffic volume. The accumulator shall be re-initialized at the beginning of each granularity period. D. A value of type Real E. RRC.schCeTraffic F. BscFunction G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.10 Number of forward RLP packets A. This measurement provides the total number of forward RLP packets. B. DER (n=1) C. On transmission of the forward RLP packets from the BSC (for RLP see [27]). D. An integer value E. RRC.nbrForwardRlpPkts F. BscFunction G. Valid for packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.11 Number of repeated forward RLP packets A. This measurement provides the number of repeated forward RLP packets. B. DER (n=1) C. On retransmission of the forward RLP packets from the BSC (for RLP see [27]).
2006 3GPP2 Page 32
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
D. An integer value E. RRC.nbrResendedForwardRlpPkts F. BscFunction G. Valid for packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.12 Number of reverse RLP packets A. This measurement provides the total number of reverse RLP packets. B. DER (n=1) C. On transmission of the reverse RLP packets from the BSC (for RLP see [27]). D. An integer value E. RRC.nbrReverseRlpPkts F. BscFunction G. Valid for packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.13 Number of repeated reverse RLP packets A. This measurement provides the number of repeated reverse RLP packets. B. DER (n=1) C. On retransmission of the reverse RLP packets from the BSC (for RLP see [27]). D. An integer value E. RRC.nbrResendedReverseRlpPkts F. BscFunction G. Valid for packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.14 Number of failed requests for PS domain service A. This measurement provides the number of failed requests for PS domain service due to radio resource shortage.
2006 3GPP2 Page 33
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
B. CC C. The BS fails to assign the resource for requests of PS domain service due to the shortage of TCE unit, RF link capacity, Walsh Codes, power, etc. D. An integer value E. RRC.nbrCongestionRadioPart F. BscFunction G. Valid for packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.2.15 Number of attempted PS handoffs A. This measurement provides the number of attempted incoming handoffs for PS domain service, including soft handoffs, hard handoffs and dormant handoffs. B. CC C. For inter BS hard handoffs on receipt by the BS of an A1 message Handoff Request [23] from the MSC with service option set to 33 indicating cdma2000 high speed packet service; Or, for inter BS soft handoffs, on receipt by the BS of an A7 message A7-Handoff Request [28] from another BSC for the PS domain service; Or, for inter BS dormant handoffs, on receipt by the BS of an Um message Origination [25] with the service option set to 33 indicating cdma2000 high speed packet service, and the DRS set to 0; Or, for intra BS PS domain handoffs, on transmission of an Um message Extended Handoff Direction [25], Handoff Direction [25], General Handoff Direction [25] or Universal Handoff Direction [25] message from the BS. D. An integer value E. HO.attHoPs F. BscFunction G. Valid for packet switched traffic H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 34
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
7.3.2.16 Number of successful PS handoffs A. This measurement provides the number of successful incoming handoffs for PS domain service, including soft handoffs, hard handoffs and dormant handoffs. B. CC C. For inter BS hard handoffs on transmission of an A1 message Handoff Request Acknowledge [23] indicating the successful hard handoff for PS domain service from the BS to MSC; Or, for inter BS soft handoffs, on transmission of an A7 message A7Handoff Request Acknowledge [28] indicating the successful hard handoff for PS domain service from the target BS to the source BS; Or, for inter BS dormant handoffs, on receipt by the BS of an A9Release-A8 Complete [29] message, or A9-Connect-A8 message, for the PS dormant service handoff; Or, for intra BS PS domain handoffs, on receipt by the BS of an Um message Handoff Completion [25] or Extended Handoff Completion [25] message from the BS. D. An integer value E. HO.succHoPs F. BscFunction G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.3 BSC system resource measurements 7.3.3.1 Number of available trunk circuits A. This measurement provides the number of available trunk circuits (64 Kbps time slots) of interface A, i.e. the A circuits which are not broken down. B. GAUGE C. This measurement will be increased on transition of a trunk circuit from unavailable (can not be assigned) into available (can be assigned), decreased on transition of a trunk circuit from available (can be assigned) into unavailable (can not be assigned). D. An integer value E. RRC.nbrAvailACircuits F. BscFunction
2006 3GPP2
Page 35
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
G. Valid for circuit switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.3.3.2 Duration of seizures of A-Interface circuits A. This measurement provides the time of seizures of interface A circuits (64 Kbps time slots, in seconds). B. DER (n=1) C. This measurement is obtained by summing the duration of seizure(s) of all A circuits; The duration of seizure(s) for each A circuit is gotten by accumulating the seizure time intervals between the transmission by the BSC of a BSMAP "Assignment Complete" message [23], and the receipt by the BSC of the corresponding BSMAP "Clear Command" message [23] for the circuit over a granularity period. The accumulator shall be re-initialized at the beginning of each granularity period. D. An integer value E. RRC.durACircuitsSeizure F. BscFunction G. Valid for circuit switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4 Measurements related to Sector 7.4.1 Sector traffic measurements related to the CS domain 7.4.1.1 Number of attempted originating calls related to the CS domain A. This measurement provides the number of attempted originating calls for CS domain service within the Sector. B. CC C. Receipt by the BS from MS of an Um message Origination [25], with Service Option indicating the CS domain service (for details see Annex A). D. An integer value E. RRC.attOrigCallsCs F. Sector G. Valid for circuit switched traffic. H. cdma2000 1X
2006 3GPP2 Page 36
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.1.2 Number of attempted call assignments to the CS domain A. This measurement provides the number of attempted call assignments for CS domain service within Sector. B. CC C. Receipt by the BS from MSC of a BSMAP message Assignment Request [23]. D. An integer value E. RRC.attAssignCs F. Sector G. Valid for circuit switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.1.3 Number of paging responses related to the CS domain A. This measurement provides the number of paging responses of the CS domain within the Sector. B. CC C. Receipt by the BS from MS of an Um message Page Response [25]. D. An integer value E. RRC.succPageRspsCs F. Sector G. Valid for circuit switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.1.4 Number of dropped calls related to the CS domain A. This measurement provides the total number of dropped calls for the CS domain service. This measurement can only be provided in cases where the optional Cause element is provided. B. CC C. Transmission of BSMAP message Clear Request [23] from the BS to the MSC with the cause value of the Cause element set to 00H, 01H, 07H, 0DH, 20H or 60H. D. An integer value
2006 3GPP2 Page 37
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
E. RRC.nbrRadioDropCs F. Sector G. Valid for circuit switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.1.5 Traffic volume including handoffs A. This measurement provides the traffic volume ((in erlang) carried on the traffic channels for voice service and SMS (if using TCH), including the traffic volume due to all kinds of handoff. B. DER (n=1) C. This measurement is obtained by summing the traffic on all TCHs. The traffic on each TCH is calculated by accumulating the seizure time intervals between the TCH is successfully assigned, and the TCH is released for the Voice call, SMS and CS call handoffs over a granularity period, the end value of this time will be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. RRC.trafficIncludeHoCs F. Sector G. Valid for circuit switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.1.6 Traffic volume of Walsh Codes A. This measurement provides the traffic volume carried by Walsh Codes for voice service and SMS (in erlang). B. DER (n=1) C. This measurement is obtained by summing the traffic on all Walsh Codes. The traffic on each Walsh Code is calculated by accumulating the seizure time intervals between the Walsh Code related TCH is successfully assigned, and the TCH is released over a granularity period, the end value of this time will be divided by the granularity period, and then be convert to the traffic volume according to the Walsh Code of the TCH. The accumulator shall be re-initialized at the beginning of each granularity period. D. A value of type Real
2006 3GPP2
Page 38
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
E. RRC.trafficByWalshCs F. Sector G. Valid for circuit switched traffic. H. cdma2000 1X I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.2 Sector traffic measurements related to the PS domain 7.4.2.1 Number of attempted originating calls related to the PS domain A. This measurement provides the number of attempted originating calls for PS domain service within the Sector. B. CC C. Receipt by the BS from MS of an Um message Origination, with Service Option set to 33 indicating cdma2000 high speed packet service [25]. D. An integer value E. RRC.attOrigCallsPs F. Sector G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.2.2 Number of attempted call assignments to the PS domain A. This measurement provides the number of attempted call assignments for PS domain service within Sector. B. CC C. Receipt by the BS from MSC of a BSMAP message Assignment Request [23]. D. An integer value E. RRC.attAssignPs F. Sector G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 39
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
7.4.2.3
Number of successful call assignments to the PS domain
A. This measurement provides the number of successful assignments for calls of PS domain services in the Sector. B. CC C. Transmission of BSMAP message Assignment Complete from the BS to MSC [23]. D. An integer value E. RRC.succAssignPs F. Sector G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.2.4 Number of paging responses related to the PS domain A. This measurement provides the number of paging responses of the PS domain within the Sector. B. CC C. Receipt by the BS from MS of an Um message Page Response [25]. D. An integer value E. RRC.succPageRspsPs F. Sector G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.4.2.5 Number of dropped calls related to the PS domain A. This measurement provides the total number of dropped calls call for the PS domain service. This measurement can only be provided in cases where the optional Cause element is provided. B. CC C. Transmission of BSMAP message Clear Request [23] from the BS to the MSC with the cause value of the Cause element set 00H, 01H, 07H, 0DH, 20H or 60H. D. An integer value E. RRC.nbrRadioDropPs
2006 3GPP2
Page 40
3GPP2 S.S0093-0 v2.0
1 2 3 4 5
F. Sector G. Valid for packet switched traffic. H. cdma2000 1X, cdma2000 1XEV-DV I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 41
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
7.5 Measurements related to PCF 7.5.1 PCF traffic measurements 7.5.1.1 Number of successful access A. This measurement provides the number of successful accesses for the PS domain service. B. CC C. Receipt by the PCF from PSDN of an A11 message A11-Registration Reply with the Code element set to 00H [10][31][32]. D. An integer value E. PPP.succAccessPs F. PcfFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.5.1.2 Number of unsuccessful access A. This measurement provides the number of failed requests for PS domain service due to resource shortages at the PCF. B. CC C. The PCF fails to assign the resources for the request of PS service due to the shortage of PPP capacity, PDSN volume, RP link or buffer resource, etc. D. An integer value E. PPP.nbrCongestionPcfPart F. PcfFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.5.1.3 Forward GRE bits A. This measurement provides the forward throughput including the GRE head (in kilobits, rounded up). B. DER (n=1) C. On transmission of the forward GRE packets by the PCF.
2006 3GPP2
Page 42
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
D. An integer value E. PPP.forwardThroughput F. PcfFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.5.1.4 Reverse GRE bits A. This measurement provides the reverse throughput including the GRE head (in kilobits, rounded up). B. DER (n=1) C. On receipt of the reverse GRE packets by the PCF. D. An integer value E. PPP.reverseThroughput F. PcfFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.5.1.5 Number of RAN discarded reverse GRE packets A. This measurement provides the number of the discarded reverse GRE packets from the RAN, due to Buffer Allocation Failure or Queue Overflow. B. CC C. This measurement is incremented on discarding of a reverse GRE packet by the PCF. D. An integer value E. PPP.nbrDiscardedPktsFromRan F. PcfFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 43
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
7.5.1.6
Number of PDSN discarded forward GRE packets
A. This measurement provides the number of the discarded forward GRE packets from the PSDN, due to Buffer Allocation Failure or Queue Overflow. B. CC C. This measurement is incremented on discarding of a forward GRE packet by the PCF. D. An integer value E. PPP.nbrDiscardedPktsFromPdsn F. PcfFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.5.1.7 Number of attempted PS transitions from dormant to active A. This measurement provides the number of attempted Packet Data Session Dormant to Active state transitions. B. CC C. When the Packet Data Session is dormant, PCF receives a A9 message A9-setup-A8 with the DRS bit set to 1 and the existence of A10 connection for the session activated by MS; PCF transmits a A9 message A9-BS Service Request to BS for the session activated by network [31][32]. D. An integer value E. PPP.attCallsFromDormantToActive F. PcfFunction G. Valid for packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 7.5.1.8 Number of successful PS transitions from dormant to active A. This measurement provides the number of successful setups of a Packet Data Service Instance when the Packet Data Session is Dormant. B. CC C. Transmission of A9-connect-A8 message or A9-release-A8 message from PCF to BS indicating the successful activation [31][32].
2006 3GPP2 Page 44
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8
D. An integer value E. PPP.succCallsFromDormantToActive F. PcfFunction G. Valid for packet switched traffic. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 45
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Measurements related to the Packet Core Network
8.1 Common Measurements 8.1.1 Interfaces Group Measurements 8.1.1.1 Number of octets received A. This measurement provides the number of octets received on the interface, including framing characters. It is defined in [18,19]. B. CC C. The relevant measurement is incremented when an octet is received by the interface. D. An integer value E. MIB.ifInOctets F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.1.2 Number of unicast packets accepted A. This measurement provides the number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. It is defined in [18,19]. B. CC C. The relevant measurement is incremented when a packet is delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. D. An integer value E. MIB.ifInUcastPkts F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 46
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.1.1.3
Number of non-unicast packets accepted
A. This measurement provides the number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast or broadcast address at this sub-layer. It is defined in [18,19]. B. CC C. The relevant measurement when a packet is delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast or broadcast address at this sub-layer. D. An integer value E. MIB.ifInNUcastPkts F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.1.4 Number of inbound packets discarded A. This measurement provides the number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. It is defined in [18,19]. B. CC C. The relevant measurement is incremented when an incoming packet is discarded. One possible reason for discarding such a packet could be to free up buffer space. D. An integer value E. MIB.ifInDiscards F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.1.5 Number of malformed packets received A. This measurement provides the number of inbound packets that contained errors preventing them from being deliverable to a higherlayer protocol. It is defined in [18,19]. B. CC
2006 3GPP2
Page 47
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
C. The relevant measurement is incremented when an incoming packet has an error. D. An integer value E. MIB.ifInErrors F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.1.1.6 Number of packets discarded due to unknown protocol A. This measurement provides the number of packets received via the interface, which were discarded because of an unknown or unsupported protocol. It is defined in [18,19]. B. CC C. The relevant measurement is incremented when a packet is discarded because of an unknown or unsupported protocol. D. An integer value E. MIB.ifInUnknownProtos F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.1.7 Number of octets sent A. This measurement provides the number of octets transmitted out of the interface, including framing characters. It is defined in [18,19]. B. CC C. The relevant measurement is incremented when an octet is sent by the interface. D. An integer value E. MIB.ifOutOctets F. PdsnFunction, HaFunction G. Packet Switched H. All
2006 3GPP2
Page 48
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.1.8 Number of unicast packets sent A. This measurement provides the number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. It is defined in [18,19]. B. CC C. The relevant measurement is incremented when a packet is transmitted, and which was not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. D. An integer value E. MIB.ifOutUcastPkts F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.1.9 Number of non-unicast packets sent A. This measurement provides the number of packets, that higher-level protocols requested be transmitted, and which were addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. It is defined in [18,19]. B. CC C. The relevant measurement when a packet is transmitted by this sublayer to a higher (sub-)layer, which were addressed to a multicast or broadcast address at this sub-layer. D. An integer value E. MIB.ifOutNUcastPkts F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 49
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.1.1.10 Number of outbound packets discarded A. This measurement provides the number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted. It is defined in [19]. B. CC C. The relevant measurement is incremented when an outgoing packet is discarded. One possible reason for discarding such a packet could be to free up buffer space. D. An integer value E. MIB.ifOutDiscards F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.1.11 Number of outbound erred packets A. This measurement provides the number of outbound packets that could not be transmitted because of errors. It is defined in [19]. B. CC C. The relevant measurement is incremented when an outgoing packet cant be sent due to an error. D. An integer value E. MIB.ifOutErrors F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2 IP Group Measurements 8.1.2.1 Number of input packets received A. This measurement provides the number of input datagrams received from interfaces, including those received in error. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an input datagram is received from the interface.
2006 3GPP2 Page 50
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
D. An integer value E. MIB.ipInReceives F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.2 Number of input datagrams discarded due to errors in their IP headers A. This measurement provides the number of input datagrams discarded due to errors in their IP headers. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an input datagram is discarded due to an error in the IP header, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing its IP options, etc. D. An integer value E. MIB.ipInHdrErrors F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.3 Number of input datagrams discarded due to invalid address A. This measurement provides the number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an input datagram is discarded due to an invalid address. D. An integer value E. MIB.ipInAddrErrors F. PdsnFunction, HaFunction G. Packet Switched H. All
2006 3GPP2
Page 51
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.4 Number of forwarded input datagrams A. This measurement provides the number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an input datagram is forwarded to another destination. D. An integer value E. MIB.ipForwDatagrams F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.5 Number of input datagrams discarded due to unknown protocol A. This measurement provides the number of input datagrams discarded due to unknown protocol. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an input datagram is discarded due to unknown protocol. D. An integer value E. MIB.ipInUnknownProtos F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.6 Number of input datagrams discarded without appropriate reasons A. This measurement provides the number of input datagrams discarded without appropriate reasons. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an input datagram is discarded without appropriate reasons.
2006 3GPP2 Page 52
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
D. An integer value E. MIB.ipInDiscards F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.7 Number of input datagrams delivered to IP user protocol A. This measurement provides the number of input datagrams delivered to IP user protocol successfully. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an input datagram is delivered to IP user protocol successfully. D. An integer value E. MIB.ipInDelivers F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.8 Number of output datagrams requested A. This measurement provides the number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an IP datagram, which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. D. An integer value E. MIB.ipOutRequests F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 53
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
8.1.2.9
Number of datagrams discarded due to no route
A. This measurement provides the number of datagrams that are discarded because no route is found. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when a datagram is discarded because no route is found. D. An integer value E. MIB.IpOutNoRoutes F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.10 Number of output datagrams discarded for other reasons A. This measurement provides the number of datagrams that are discarded for other reasons. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when a datagram is discarded for other reasons (e.g., for lack of buffer space). D. An integer value E. MIB.IpOutDiscards F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.11 Number of datagrams fragmented A. This measurement provides the number of successfully fragmented IP datagrams. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an IP datagram is successfully fragmented. D. An integer value E. MIB.IpFragOKs F. PdsnFunction, HaFunction
2006 3GPP2
Page 54
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.12 Number of datagrams for which fragmentation failed A. This measurement provides the number of IP datagrams that are discarded because fragmentation failure. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when a datagram is discarded because fragmentation failure. D. An integer value E. MIB.IpFragFails F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.13 Number of fragments created A. This measurement provides the number of IP datagrams fragments generated. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an IP datagram fragment is generated. D. An integer value E. MIB.ipFragCreates F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.14 Number of IP fragments received A. This measurement provides the number of IP fragments received that need to be reassembled. It is defined in [12,19]. B. CC
2006 3GPP2
Page 55
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
C. The relevant measurement is incremented when an IP fragment that needed to be reassembled is received. D. An integer value E. MIB.ipReasmReqds F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.15 Number of IP datagrams reassembled A. This measurement provides the number of successfully reassembled IP datagrams. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when an IP datagram is successfully reassembled. D. An integer value E. MIB.ipReasmOKs F. PdsnFunction, HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.1.2.16 Number of reassembly failures A. This measurement provides the number of failures detected by the IP re-assembly algorithm. It is defined in [12,19]. B. CC C. The relevant measurement is incremented when a reassembling failure is detected by the IP re-assembly algorithm (for whatever reason: time out, errors, etc). D. An integer value E. MIB.ipReasmFails F. PdsnFunction, HaFunction G. Packet Switched H. All
2006 3GPP2
Page 56
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2 Measurements related to the PDSN 8.2.1 MIP Measurements 8.2.1.1 Number of successful MIP registrations in PDSN A. This measurement provides the number of successful registrations within the PDSN during a granularity period. B. CC C. The relevant measurement is incremented on Receipt of successful MIP registration reply Message (code 0). D. An integer value E. MM.fARegReplyReceived F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.2 Number of attempted MIP registrations in PDSN A. This measurement provides the number of attempted registrations within the PDSN during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a valid Registration Request is received. D. An integer value E. MIB.faRegRequestsReceived F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.3 Number of registrations relayed from PDSN to HA A. This measurement provides the number of registrations that are relayed from PDSN to HA during the granularity period. It is defined in [11]. B. CC
2006 3GPP2 Page 57
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. The relevant measurement is incremented when a Registration Request is relayed to the HA by the PDSN. D. An integer value E. MIB.faRegRequestsRelayed F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.4 Number of rejected registrations by the PDSN due to unspecified reason A. This measurement provides the number of rejected registrations by the PDSN, due to unspecified reason, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to unspecified reason (Code 64) D. An integer value E. MIB.faReasonUnspecified F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.5 Number of rejected administrative reason registrations by the PDSN due to
A. This measurement provides the number of rejected registrations by the PDSN, because they are administratively prohibited, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to administratively prohibited reason (Code 65) D. An integer value E. MIB.faAdmProhibited F. PdsnFunction G. Packet Switched
2006 3GPP2
Page 58
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.6 Number of rejected registrations by the PDSN due to insufficient resource reason A. This measurement provides the number of rejected registrations by the PDSN, due to insufficient resource, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to insufficient resource reason (Code 66) D. An integer value E. MIB.faInsufficientResource F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.7 Number of rejected registrations by the PDSN due to MN authentication failure reason A. This measurement provides the number of rejected registrations by the PDSN, due to mobile node authentication failure, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to mobile node authentication failure reason (Code 67) D. An integer value E. MIB.faMNAuthenticationFailure F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities
2006 3GPP2
Page 59
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
8.2.1.8 Number of rejected registrations by the PDSN due to HA authentication failure reason A. This measurement provides the number of rejected registrations requests by the PDSN, due to HA authentication failure, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration reply is denied by PDSN, due to home agent failed authentication reason (Code 68) D. An integer value E. MIB.faHAAuthenticationFailure F. PdsnFunction G. Packet Switched H. ALL I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.9 Number of rejected registrations by the PDSN due to too long registration lifetime reason A. This measurement provides the number of rejected registrations by the PDSN, due to too long registration lifetime, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to Requested lifetime too long reason (Code 69) D. An integer value E. MIB.faRegLifetimeTooLong F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.10 Number of rejected registrations by the PDSN due to poorly formed requests reason A. This measurement provides the number of rejected registrations by the PDSN, due to too poorly formed requests, during the granularity period. It is defined in [11]. B. CC
2006 3GPP2 Page 60
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to Poorly formed request reason (Code 70) D. An integer value E. MIB.faPoorlyFormedRequests F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.11 Number of rejected registrations replies by the PDSN due to poorly formed reply reason A. This measurement provides the number of rejected registration replies by the PDSN, due to too poorly formed replies, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Reply is rejected by PDSN, due to Poorly formed reply reason (Code 71) D. An integer value E. MIB.faPoorlyFormedReplies F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.12 Number of rejected registrations by the PDSN due to unavailable encapsulation requested reason A. This measurement provides the number of rejected registrations by the PDSN, due to unavailable encapsulation requested, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to Requested encapsulation unavailable reason (Code 72) D. An integer value E. MIB.faEncapsulationUnavailable F. PdsnFunction
2006 3GPP2
Page 61
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.13 Number of rejected registrations by the PDSN due to VJ compression reason A. This measurement provides the number of rejected registrations by the PDSN, due to unavailable Van Jacobson header compression, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to Requested Van Jacobson header compression unavailable reason (Code 73) D. An integer value E. MIB.faVJCompressionUnavailable F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.14 Number of rejected registrations by the PDSN due to unreachable HA A. This measurement provides the number of rejected registrations by the PDSN, due to unreachable HA, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration is rejected by PDSN, due to Home agent unreachable reason (Code 8095) D. An integer value E. MIB.faHAUnreachable F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities
2006 3GPP2
Page 62
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.2.1.15 Number of registrations replies received by the PDSN A. This measurement provides the number of well-formed Registration Replies received by the PDSN, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a well-formed Registration Reply is received by PDSN. D. An integer value E. MIB.faRegRepliesReceived F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.1.16 Number of valid registrations replies relayed to the MN by the PDSN A. This measurement provides the number of valid Registration Replies relayed to the mobile node by the PDSN, during the granularity period. It is defined in [11]. B. CC C. The relevant measurement is incremented when a valid Registration Reply is relayed to the mobile node by PDSN. D. An integer value E. MIB.faRegRepliesRelayed F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.2 PPP Measurements 8.2.2.1 Total number of PPP packets sent to MNs A. This measurement provides the number of PPP packets sent to the mobile nodes during a granularity period. B. CC C. The relevant measurement is incremented on sending of a PPP data packet to the mobile node.
2006 3GPP2 Page 63
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
D. An integer value E. PPP.TxPackets F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.2.2 Total number of errored PPP packets A. This measurement provides the number of PPP packets dropped due to an error found during a granularity period B. CC C. The relevant measurement is incremented on receipt of an erred PPP data packet from the mobile node D. An integer value E. PPP.BadPackets F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities 8.2.2.3 Total number of discarded PPP packets A. This measurement provides the total number of PPP packets discarded during a granularity period B. CC C. The relevant measurement is incremented on discard of a PPP data packet received from the MN D. An integer value E. PPP.DiscardPackets F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities
2006 3GPP2
Page 64
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.2.2.4
Total active/dormant connection time
A. This measurement provides the total active/dormant connection time on traffic channel in seconds during a granularity period. B. DER (n=1) C. This measurement is obtained by accumulating active/dormant times received from the RAN in the A11 RRQ message (Airlink record stop) D. An integer value (in seconds) E. PPP.LinkStatusTime.Active PPP.LinkStatusTime.Dormant PPP.LinkStatusTime.Sum F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.2.5 Total number of PPP packets received from all MNs A. This measurement provides the number of PPP packets received from the mobile nodes during a granularity period B. CC C. The relevant measurement is incremented on receipt of a PPP data packet from the mobile node. D. An integer value E. PPP.RxPackets F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.2.6 Total number of dropped PPP sessions A. This measurement provides the number of PPP session that are cut off during a granularity period B. CC C. The relevant measurement is incremented on abnormal PPP session terminations due to the network (revocation, forced disconnect, MIP authentication failure, etc). Total active time Total dormant time Total connection time (active dormant)
2006 3GPP2
Page 65
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
D. An integer value E. PPP.SessionFailures F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities. 8.2.2.7 Total number of active PPP sessions A. This measurement provides the current number of simultaneous active PPP sessions at the end of the granularity period. B. GAUGE C. The relevant measurement is incremented on successful IPCP negotiation or successful MIP registration, and decremented upon receiving A11-Registration Request containing the all dormant indicator or successful MIP deregistration. D. An integer value E. PPP.NumActiveSessions PPP.NumActiveSessions.SIP PPP.NumActiveSessions.MIP F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.2.8 Total number of dormant PPP sessions A. This measurement provides the current number of dormant PPP sessions at the end of the granularity period. B. GAUGE C. The relevant measurement is incremented upon receiving A11Registration Request containing the all dormant indicator [10], and decremented on successful IPCP negotiation or successful MIP registration. D. An integer value E. PPP.NumDorSessions The total regardless of the service used The total of PPP sessions regardless of the service used Number of PPP sessions negotiated for Simple IP Service Number of PPP sessions negotiated for Mobile IP service
2006 3GPP2
Page 66
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
PPP.NumDorSessions.SIP Only the Simple IP service PPP.NumDorSessions.MIP Only the Mobile IP service F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.2.9 Total number of PPP setup requests A. This measurement provides the number of PPP setup requests B. CC C. The relevant measurement is incremented upon receiving LCP Config Req message. D. An integer value E. PPP.SetUpReq F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.2.10 Total number of PPP successful connections A. This measurement provides the number of PPP successful connections B. CC C. The relevant measurement is incremented when the PPP state is open. D. An integer value E. PPP.SuccConn F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.2.11 Total number of PPP setup failures A. This measurement provides the number of PPP setup failures B. CC C. The relevant measurement is incremented when the PPP setup fails.
2006 3GPP2
Page 67
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
D. An integer value E. PPP.SetUpFailures F. PdsnFunction G. Packet Switched H. All A. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.3 GRE Measurements These measurements correspond to the A10 connection (user plane) as described in [10]. 8.2.3.1 Total number of GRE packets transmitted by the PDSN A. This measurement provides the number of GRE encapsulated packets delivered to PCF for transmission. B. CC C. The relevant measurement is incremented on sending of a GRE encapsulated packet to IP for all established A10 connections. D. An integer value E. GRE.StatsTx F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.3.2 Total number of GRE packets received by the PDSN A. This measurement provides the number of GRE encapsulated packets during a granularity period received from IP (PCF). B. CC C. The relevant measurement is incremented on receipt of a GRE encapsulated packet from IP for all established A10 connections. D. An integer value E. GRE.StatsRx F. PdsnFunction G. Packet Switched H. All
2006 3GPP2
Page 68
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.3.3 Total number of bytes transmitted by the PDSN A. This measurement provides the number of bytes transmitted during a granularity period. B. CC C. The relevant measurement is incremented on sending of a data packet with the number of bytes in this data packet for all established A10 connections. D. A value of type Real E. GRE.StatsTxBytes F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.3.4 Total number of bytes received by the PDSN A. This measurement provides the number of bytes received during a granularity period. B. CC C. The relevant measurement is incremented on receipt of a data packet with the number of bytes in this data packet for all established A10 connections. D. A value of type Real E. GRE.StatsRxBytes F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities 8.2.3.5 Total number of errored GRE packets A. This measurement provides the number of packets received with errors during a granularity period. B. CC C. The relevant measurement is incremented on receipt of an errored data packet for all established A10 connections.
2006 3GPP2 Page 69
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
D. An integer value E. GRE.StatsRxErrors F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities 8.2.3.6 Total number of discarded GRE packets A. This measurement provides the total number of GRE packets discarded during a granularity period. B. CC C. The relevant measurement is incremented on discard of a GRE data packet for all established A10 connections. D. An integer value E. GRE.DiscardPackets F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities. 8.2.3.7 Total number of GRE packets out of sequence A. This measurement provides the total number of GRE packets received out of sequence during a granularity period. B. CC C. The relevant measurement is incremented on receipt of an out of sequence GRE data packet for all established A10 connections. D. An integer value E. GRE.StatsOOS F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities.
2006 3GPP2
Page 70
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.2.3.8
Total number of GRE packets with no existing MIP binding
A. This measurement provides the total number of GRE packets with no existing tunnel or no client bound to tunnel during a granularity period B. CC C. The relevant measurement is incremented on receipt of a GRE data packet with no existing MIP binding (no tunnel) D. An integer value E. GRE.StatsNoTunnel F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities. 8.2.4 R-P Measurements These measurements correspond to the A11 connection (signaling plane) as described in [10]. 8.2.4.1 Total number of R-P registration requests A. This measurement provides the total number of R-P Registration of PCF received by PDSN during a granularity period. B. CC C. The relevant measurement is incremented on receipt of an A11 registration Request message D. An integer value E. RP.AttRegistration F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.2 Total number of R-P registration requests accepted A. This measurement provides the total number of R-P Registration Requests accepted by PDSN during a granularity period. B. CC C. The relevant measurement is incremented on successful processing of an A11 registration request: PDSN sends A11 Registration Reply (accept) to PCF.
2006 3GPP2 Page 71
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
D. An integer value E. RP.RegistrationAccepted F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.3 Total number of R-P registration requests denied A. This measurement provides the number of RP registrations denied. This measurement is pegged by failure cause during a granularity period B. CC C. The relevant measurement is incremented on unsuccessful RP registration. Possible causes are Reason Unspecified, Administratively Prohibited, Insufficient Resource, FA Authentication Failure, Identification Mismatch, Poorly Formed Request, Mobile Node Failed Authentication, Unknown PDS Address, Requested Reverse Tunnel Unavailable, Reverse Tunnel is Mandatory and T bit not set, Unsupported vendor ID as defined in IS-2001-A. D. An integer value E. The measurement name has the form RP.RegDenied.Cause where Cause identifies the failure cause, and RP.RegDenied.Sum provides the sum of all the denied RP registrations. Possible cause values are:

128 (Registration Denied reason unspecified) 129 (Registration Denied administratively prohibited) 130 (Registration Denied insufficient resources) 131 (Registration Denied mobile node failed authentication) 133 (Registration Denied identification mismatch) 134 (Registration Denied poorly formed request) 136 (Registration Denied unknown PDSN address) 137 (Registration Denied requested reverse tunnel unavailable) 138 (Registration Denied reverse tunnel is mandatory and T bit not set) 140 (Registration Denied unsupported Vendor ID or unable to interpret data in the CVSE)
F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities.
2006 3GPP2 Page 72
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.2.4.4
Total number of R-P deregistration requests received
A. This measurement provides the total number of valid Registration Requests received by PDSN with a Lifetime of zero during a granularity period. B. CC C. The relevant measurement is incremented on receipt of a deregistration with a Lifetime of zero D. An integer value E. RP.DeRegistrationReceived F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.5 Total number of successful R-P deregistration replies A. This measurement provides the total number of Registration Replies accepted in response to a deregistration request during a granularity period. B. CC C. The relevant measurement is incremented on sending of an acceptation of a deregistration request D. An integer value E. RP.DeRegistrationRepliesSent F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.6 Total number of R-P release connection requests A. This measurement provides the total number of attempted R-P release connection requests originated by the PDSN during a granularity period. B. CC C. The relevant measurement is incremented when PDSN sends A11Registration Update message to PCF in order to release A10 connection. D. An integer value
2006 3GPP2
Page 73
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
E. RP.AttRelConn F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.7 Total number of successful R-P release connection replies A. This measurement provides the total number of successful R-P release connection requests originated by the PDSN during a granularity period. B. CC C. The relevant measurement is incremented when PDSN receives A11Registration Acknowledge (accept) message from PCF. D. An integer value E. RP.SuccRelConn F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.8 Total number of current sessions A. This measurement provides the current number of RP sessions in the system at the end of the granularity period. B. GAUGE C. The gauge will be incremented on successful Reply message on A11RRQ and will be decremented when an RP session is ended. D. An integer value E. RP.NumCurrentSessions F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 74
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.2.4.9
Total number of active R-P sessions
A. This measurement provides the current number of simultaneous active RP sessions at the end of the granularity period. B. GAUGE C. The relevant measurement is incremented on successful Reply message on A11-RRQ containing Airlink Start Record as a response sent to the PCF and decremented upon receiving A11-RRQ containing the all dormant indicator. D. An integer value E. RP.NumActiveSessions F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.10 Total number of dormant R-P sessions A. This measurement provides the current number of dormant R-P sessions at the end of the granularity period. B. GAUGE C. The relevant measurement is incremented upon receiving A11-RRQ containing the all dormant indicator and decremented on [10] and decremented on successful Reply message on A11-RRQ containing Airlink Start Record. D. An integer value E. RP.TotalSessions F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.11 Total number of handoff sessions A. This measurement provides the number of all handoff occurrences. B. CC C. The relevant measurement is incremented on handoff event. D. An integer value E. HO.NumHandoffSessions
2006 3GPP2 Page 75
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.12 Total number of successful intra-PDSN handoffs A. This measurement provides the total number of successful intra-PDSN handoff occurrences during a granularity period. B. CC C. The relevant measurement is incremented on successful intra-PDSN handoffs, upon receiving A11 registration request with the IMSI already available in the PDSN [10] D. An integer value E. HO.NumIntraHandoffSessions F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities. 8.2.4.13 Total number of unsuccessful inter-PDSN handoffs A. This measurement provides the total number of unsuccessful interPDSN handoff sessions during a granularity period. B. CC C. The relevant measurement is incremented on unsuccessful inter-PDSN handoffs, i.e., all registration requests with PSID information indicating that the MN is coming from a different PDSN [10]. D. An integer value E. HO.NumErrInterHandoffSessions F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities. 8.2.4.14 Total number of unsuccessful intra-PDSN handoffs A. This measurement provides the total number of unsuccessful intraPDSN handoff sessions due to PDSN during a granularity period.
2006 3GPP2 Page 76
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
B. CC C. The relevant measurement is incremented on unsuccessful intra-PDSN handoffs D. An integer value E. HO.NumErrIntraHandoffSessions F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities. 8.2.4.15 Total number of unsuccessful inter-PDSN handoffs A. This measurement provides the total number of unsuccessful interPDSN handoff sessions due to PDSN during a granularity period. B. CC C. The relevant measurement is incremented on unsuccessful inter-PDSN handoffs. D. An integer value E. HO.NumInterHandoffSessions F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities. 8.2.4.16 Total number of simple IP sessions A. This measurement provides the current number of simple IP sessions at the end of the granularity period. B. GAUGE C. The relevant measurement is incremented on successful establishment of an IP session and decremented on the end of an IP session. D. An integer value E. IP.NumSessions F. PdsnFunction G. Packet Switched H. All
2006 3GPP2
Page 77
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.17 Total number of MIP sessions A. This measurement provides the current number of mobile IP sessions at the end of the granularity period. B. GAUGE C. The relevant measurement is incremented on successful establishment of a mobile IP session and decremented on the end of a mobile IP session. D. An integer value E. MIP.NumSessions F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.2.4.18 Packet session set up time (Mean) A. This measurement provides the mean time for the packet session set up during a granularity period. B. DER (n=1) C. This measurement is obtained by accumulating the time intervals for each successful registration. The time interval starts at the receiving of an A11 registration request and ends: In Simple IP, when PPP is sending an IPCP Configure Ack. In Mobile IP, after receiving a successful registration reply from the HA. The end value of the time will then be divided by the number of successfully established registrations observed in the granularity period to give the arithmetic mean, the accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real (in milliseconds). E. IP.SetUpTimeMean MIP.SetUpTimeMean F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities.
2006 3GPP2
Page 78
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
8.2.4.19 Packet session set up time (Maximum) A. This measurement provides the maximum time for the packet session set up during a granularity period. B. GAUGE C. This measurement is obtained by monitoring the time intervals for each successful registration. The time interval starts at the receiving of an A11 registration request and ends: In Simple IP, PPP is sending an IPCP Configure Ack. In Mobile IP, after receiving a successful registration reply from the HA. The high tide mark of this time will be stored in a gauge; the gauge shall be reinitialized at the beginning of each granularity period. D. An integer value (in milliseconds) E. IP.SetUpTimeMax MIP.SetUpTimeMax F. PdsnFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Maintenance and Operator Traffic Engineering communities. 8.3 Measurements related to the HA 8.3.1 MIP Measurements 8.3.1.1 Number of service requests accepted by HA A. This measurement provides the number of service requests for the mobile node accepted by the home agent (Code 0 + Code 1). It is defined in [11]. B. CC C. The relevant measurement is incremented when a service request for the mobile node is accepted by the home agent. D. An integer value E. MIB.haServiceRequestsAccepted F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 79
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.3.1.2
Number of service requests denied by HA
A. This measurement provides the number of service requests for the mobile node denied by the home agent. It is defined in [11]. B. CC C. The relevant measurement is incremented when a service request for the mobile node is denied by the home agent (sum of all registrations denied with Code 128 through Code 159). D. An integer value E. MIB.haServiceRequestsDenied F. HaFunction G. Packet Switched H. All A. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.3 Number of registration requests accepted by HA A. This measurement provides the total number of Registration Requests accepted by home agent (Code 0). It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is accepted by the home agent. D. An integer value E. MIB.haRegistrationAccepted F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.4 Number of registration requests supported by the MN binding accepted by HA, but not
A. This measurement provides the total number of Registration Requests accepted by home agent, but not supported by the mobile node binding. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is accepted by the home agent -- simultaneous mobility bindings unsupported (Code 1).
2006 3GPP2
Page 80
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
D. An integer value E. MIB.haMultiBindingUnsupported F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.5 Number of registration requests rejected by the HA due to unknown reasons A. This measurement provides the total number of Registration Requests denied by home agent, due to unknown reason. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- reason unspecified (Code 128). D. An integer value E. MIB.haReasonUnspecified F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.6 Number of registration requests rejected by the HA due to administrative reasons A. This measurement provides the total number of Registration Requests denied by home agent due to administratively prohibited registration. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- administratively prohibited (Code 129). D. An integer value E. MIB.haAdmProhibited F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2 Page 81
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.3.1.7 Number of registration requests rejected by the HA due to insufficient resources A. This measurement provides the total number of Registration Requests denied by home agent due to insufficient resources. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- insufficient resources (Code 130). D. An integer value E. MIB.haInsufficientResource F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.8 Number of registration requests rejected by the HA due to authentication failure A. This measurement provides the total number of Registration Requests denied by home agent due to mobile node authentication failure. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- mobile node failed authentication (Code 131). D. An integer value E. MIB.haMNAuthenticationFailure F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.9 Number of registration requests rejected by the HA due to FA authentication failure A. This measurement provides the total number of Registration Requests denied by home agent due to FA authentication failure. It is defined in [11]. B. CC
2006 3GPP2
Page 82
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- foreign agent failed authentication (Code 132). D. An integer value E. MIB.haFAAuthenticationFailure F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.10 Number of registration requests rejected by the HA due to identification mismatch A. This measurement provides the total number of Registration Requests denied by home agent due to identification mismatch. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- Identification mismatch (Code 133). D. An integer value E. MIB.haIDMismatch F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.11 Number of registration requests rejected by the HA due to poorly formed request A. This measurement provides the total number of Registration Requests denied by home agent due to poorly formed request. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- poorly formed request (Code 134). D. An integer value E. MIB.haPoorlyFormedRequest F. HaFunction
2006 3GPP2
Page 83
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.12 Number of registration requests rejected by the HA due to too many simultaneous mobility bindings A. This measurement provides the total number of Registration Requests denied by home agent due to too many simultaneous mobility bindings at one time. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- too many simultaneous mobility bindings (Code 135). D. An integer value E. MIB.haTooManyBindings F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.13 Number of registration requests rejected by the HA due to unknown home agent addresses A. This measurement provides the total number of Registration Requests denied by home agent due to unknown home agent addresses. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is denied by the home agent -- unknown home agent address (Code 136). D. An integer value E. MIB.haUnknownHA F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 84
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
8.3.1.14 Number of ARP sent by HA on behalf of the MN A. This measurement provides the total number of gratuition ARPs sent by the home agent on behalf of mobile nodes. It is defined in [11]. B. CC C. The relevant measurement is incremented when a gratuition ARP is sent by the home agent on behalf of mobile node. D. An integer value E. MIB.haGratuitiousARPsSent F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.15 Number of proxy ARP responses sent by HA on behalf of the MN A. This measurement provides the total number of ARP responses sent by the home agent on behalf of mobile nodes, as the proxy ARP. It is defined in [11]. B. CC C. The relevant measurement is incremented when a proxy ARP response is sent by the home agent on behalf of mobile node. D. An integer value E. MIB.haProxyARPsSent F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.16 Number of registration replies received by HA A. This measurement provides the total number of Registration Requests received by HA. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request is received by HA. D. An integer value E. MIB.haRegRequestsReceived
2006 3GPP2
Page 85
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.17 Number of deregistration requests A. This measurement provides the total number of Registration Requests received by the home agent with a Lifetime of zero (requests to deregister). It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Request with a Lifetime of zero is received by the home agent. D. An integer value E. MIB.haDeRegRequestsReceived F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.3.1.18 Number of registration replies sent by HA A. This measurement provides the total number of Registration Replies sent by HA. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Reply is sent by the HA. D. An integer value E. MIB.haRegRepliesSent F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 86
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
8.3.1.19 Number of registration replies sent by the HA in response to requests to deregister A. This measurement provides the total number of Registration Replies sent by the home agent in response to requests to deregister. It is defined in [11]. B. CC C. The relevant measurement is incremented when a Registration Reply is sent by the home agent in response to requests to deregister. D. An integer value E. MIB.haDeRegRepliesSent F. HaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4 Measurements related to the AAA 8.4.1 RADIUS Accounting Port Measurements 8.4.1.1 Number of packets received on the accounting port A. This measurement provides the number of packets received on the accounting port [17]. B. CC C. The relevant measurement is incremented when a packet is received on the accounting port. D. An integer value E. MIB.radiusAccServTotalRequests F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.1.2 Number of packets received with unknown addresses A. This measurement provides the number of RADIUS AccountingRequest packets received from unknown addresses [17]. B. CC
2006 3GPP2
Page 87
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
C. The relevant measurement is incremented when a packet is received from unknown addresses. D. An integer value E. MIB.radiusAccServTotalInvalidRequests F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.1.3 Total packets of duplicated billing request received A. This measurement provides the number of duplicate RADIUS Accounting-Request packets received [17]. B. CC C. The relevant measurement is incremented when a duplicate RADIUS Accounting-Request packet is received. D. An integer value E. MIB.radiusAccServTotalDupRequests F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.1.4 Total packets of billing responses sent A. This measurement provides the number of RADIUS AccountingResponse packets sent [17]. B. CC C. The relevant measurement is incremented when a RADIUS AccountingResponse packet is sent. D. An integer value E. MIB.radiusAccServTotalResponses F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 88
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
8.4.1.5
Total of malformed packets received
A. This measurement provides the number of malformed RADIUS Accounting-Request packets received [17]. B. CC C. The relevant measurement is incremented when a malformed RADIUS Accounting-Request packet is received. Bad authenticators or unknown types are not included as malformed Access-Requests. D. An integer value E. MIB.radiusAccServTotalMalformedRequests F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.1.6 Total packets of billing requests with illegal signature attributes A. This measurement provides the number of RADIUS AccountingRequest packets that contained invalid Signature attributes [17]. B. CC C. The relevant measurement is incremented when a RADIUS AccountingRequest packet has invalid signature attributes. D. An integer value E. MIB.radiusAccServTotalBadAuthenticators F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.1.7 Total of packets dropped A. This measurement provides the number of incoming packets silently discarded for a reason other than malformed, bad authenticators, or unknown types [17]. B. CC C. The relevant measurement is incremented when an incoming packet is silently discarded for a reason other than malformed, bad authenticators, or unknown types. D. An integer value
2006 3GPP2
Page 89
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
E. MIB.radiusAccServTotalPacketsDropped F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.1.8 Total of packets received and not recorded A. This measurement provides the number of RADIUS AccountingRequest packets, which were received and responded to but not recorded [17]. B. CC C. The relevant measurement is incremented when a received packet is not recorded. D. An integer value E. MIB.radiusAccServTotalNoRecords F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.1.9 Total of packets received with unknown type A. This measurement provides the number of RADIUS packets of unknown types, which were received [17]. B. CC C. The relevant measurement is incremented when a received packet has an unknown type. D. An integer value E. MIB.radiusAccServTotalUnknownTypes F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 90
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
8.4.2 RADIUS Authentication Port Measurements 8.4.2.1 Number of packets received on the authentication port A. This measurement provides the number of packets received on the authentication port [16]. B. CC C. The relevant measurement is incremented when a packet is received on the authentication port. D. An integer value E. MIB.radiusAuthServTotalAccessRequests F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.2 Number of packets received with unknown address A. This measurement provides the number of RADIUS Access-Request packets received from unknown addresses [16]. B. CC C. The relevant measurement is incremented when a packet is received with unknown address. D. An integer value E. MIB.radiusAuthServTotalInvalidRequests F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.3 Total packets of duplicated access request received A. This measurement provides the number of duplicate RADIUS AccessRequest packets received [16]. B. CC C. The relevant measurement is incremented when a duplicate packet is received. D. An integer value E. MIB.radiusAuthServTotalDupAccessRequests
2006 3GPP2 Page 91
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.4 Total packets of access accepted response sent A. This measurement provides the number of RADIUS Access-Accept packets sent [16]. B. CC C. The relevant measurement is incremented when a RADIUS AccessAccept packet is sent. D. An integer value E. MIB.radiusAuthServTotalAccessAccepts F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.5 Total packets of Access-Reject packets sent A. This measurement provides the number of RADIUS Access-Reject packets sent [16]. B. CC C. The relevant measurement is incremented when a RADIUS AccessReject packet is sent. D. An integer value E. MIB.radiusAuthServTotalAccessRejects F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.6 Total packets of Access-Challenge packets sent A. This measurement provides the number of RADIUS Access-Challenge packets sent [16]. B. CC
2006 3GPP2 Page 92
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. The relevant measurement is incremented when a RADIUS AccessChallenge packet is sent. D. An integer value E. MIB.radiusAuthServTotalAccessChallenges F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.7 Total packets of malformed packets sent A. This measurement provides the number of malformed RADIUS AccessRequest packets received. [16]. B. CC C. The relevant measurement is incremented when a malformed RADIUS Access-Request packet is received. Bad authenticators and unknown types are not included as malformed Access-Requests D. An integer value E. MIB.radiusAuthServTotalMalformedAccessRequests F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.8 Total packets of authentication requests with illegal signature attributes A. This measurement provides the number of RADIUS AuthenticationRequest packets, which contained invalid Signature attributes, received [16]. B. CC C. The relevant measurement is incremented when a AuthenticationRequest packet, which contained invalid Signature attributes is received D. An integer value E. MIB.radiusAuthServTotalBadAuthenticators F. AaaFunction G. Packet Switched
2006 3GPP2
Page 93
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.9 Total packets of dropped A. This measurement provides the number of incoming packets silently discarded for some reason other than malformed, bad authenticators or unknown types [16]. B. CC C. The relevant measurement is incremented when an incoming packet, is discarded for some reason other than malformed, bad authenticators or unknown types. D. An integer value E. MIB.radiusAuthServTotalPacketsDropped F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 8.4.2.10 Total packets received with unknown type A. This measurement provides the number of RADIUS packets of unknown type, which were received [16]. B. CC C. The relevant measurement is incremented when an packet, is received with an unknown types D. An integer value E. MIB.radiusAuthServTotalUnknownTypes F. AaaFunction G. Packet Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 94
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
Measurements related to the Circuit Core Network
9.1 Measurements related to the MSC 9.1.1 MSC Basic Measurement 9.1.1.1 Number of page requests A. This measurement provides the number of page requests. B. CC C. The relevant measurement is incremented on transmission of a BSMAP message Paging Request [23] from the MSC to BSC, excluding the secondary paging requests. D. An integer value E. MM.attPageReqs F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.1.2 Number of successful page requests A. This measurement provides the number of successful page requests. B. CC C. The relevant measurement is incremented on receipt by the MSC from BSC of a DTAP message Paging Response [23], including the responses of the repeated paging requests. D. An integer value E. MM.succPageReqs F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.1.3 Number of location registration requests A. This measurement provides the number of attempted location area updating. B. CC
2006 3GPP2
Page 95
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
C. The relevant measurement is incremented on receipt by the MSC from BSC of a DTAP message Location Updating Request [23]. D. An integer value E. MM.attLuReqs F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.1.4 Number of successful location registrations A. This measurement provides the number of successful location area updating messages. B. CC C. The relevant measurement is incremented on transmission of a DTAP message Location Updating Accept [23] from the MSC to the BSC. D. An integer value E. MM.succLuReqs F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2 Traffic Measurements 9.1.2.1 Number of attempted originating calls A. This measurement provides the number of attempted originating calls in the exchange. B. CC C. The relevant measurement is incremented on receipt by the MSC from BSC of a DTAP message CM Service Request [23]. D. An integer value E. TRM.attOrigCalls F. MscFunction G. Circuit Switched H. All
2006 3GPP2
Page 96
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.2 Number of successful originating calls A. This measurement provides the number of successful originating calls in the exchange. B. CC C. This measurement is based on two different cases. For internal calls, on receipt by the MSC of a BSMAP message Assignment Complete [23] about the called party from BSC. For outgoing calls, on receipt by the MSC of an ISUP message ACM [33] or TUP message ACM [34][35] from the switching located at the PSTN or from another MSC. D. An integer value E. TRM.succOrigCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.3 Number of answered originating calls A. This measurement provides the number of answered originating calls B. CC C. This measurement is based on two different cases. For internal calls, on receipt by the MSC of a DTAP message Connect [23] about the called party from BSC. For outgoing calls, on receipt by the MSC of an ISUP message ANM [33], a TUP message ANN [34][35] or a TUP message ANC [34][35] from the switching located at the PSTN or from another MSC. D. An integer value E. TRM.ansOrigCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.4 Number of failed originating calls for various reasons A. This measurement provides the number of failed originating calls. This measurement is split into subcounters per event triggering cause.
2006 3GPP2 Page 97
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
B. CC C. This measurement provides the number of the call failures before called party answers. The following reasons apply: Subcounter 1 is BlockUnavailTrunk: calls congested for lack of available trunks; Subcounter 2 is BlockCongestion: calls congested because of exchanges internal congestion; Subcounter 3 is AbnRelease: abnormal releases or other reasons.
D. An integer value E. The measurement name has the form TRM.failOrigCalls.Cause where Cause indicates the number of the cause that triggered the originating call loss. F. MscFunction
G. Circuit Switched
H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.5 Number of MSC internal call attempts A. This measurement provides the number of attempted internal calls in the exchange. B. CC C. The relevant measurement is incremented when the MSC determines that the call is an internal call by number analysis, after receiving a DTAP message CM Service Request [23] from the BSC. D. An integer value E. TRM.attInternalCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.6 Number of successful MSC internal calls A. This measurement provides the number of successful internal calls in the exchange B. CC
2006 3GPP2
Page 98
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. This measurement is incremented on receipt by the MSC from BSC of a BSMAP message Assignment Complete [23] about the called party for internal calls. D. An integer value E. TRM.succInternalCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.7 Number of MSC answered internal calls A. This measurement provides the number of answered internal calls in the exchange. B. CC C. This measurement is incremented on receipt by the MSC from BSC of a DTAP message Connect [23] about the called party for internal calls. D. An integer value E. TRM.ansInternalCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.8 Number of failed internal calls A. This measurement provides the number of failed internal calls for every specified reason. This measurement is split into subcounters per event triggering cause. B. CC C. This measurement provides the number of failed internal calls. The following reasons apply: Subcounter 1 is BlockUnavailTrunk: calls congested for lack of available trunks; Subcounter 2 is BlockCongestion: calls congested because of exchanges internal congestion; Subcounter 3 is AbnRelease: abnormal releases or other reasons.
D. An integer value
2006 3GPP2 Page 99
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
E. The measurement name has the form TRM.failInternalCalls.Cause where Cause indicates the number of the cause that triggered the internal call loss F. MscFunction
G. Circuit Switched
H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.9 Number of terminating call attempts A. This measurement provides the number of attempted terminating calls in the exchange. B. CC C. This measurement is incremented on the transmission of a BSMAP message Paging Request [23] from the MSC to BSC excluding the repeated Paging Requests. D. An integer value E. TRM.attTermCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.10 Number of Successful Mobile Terminating Calls A. This measurement provides the number of successful mobile terminating calls in the exchange. B. CC C. This measurement is incremented on receipt by the MSC from BSC of a BSMAP message Assignment Complete [23]. D. An integer value E. TRM.succTermCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 100
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
9.1.2.11 Number of Answered Terminating calls A. This measurement provides the number of answered terminating calls in the exchange. B. CC C. This measurement is incremented on receipt by the MSC from BSC of a DTAP message Connect [23]. D. An integer value E. TRM.ansTermCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.12 Number of failed terminating calls for various reasons A. This measurement provides the number of failed terminating calls for every specified reason. This measurement is split into subcounters per event triggering cause. B. CC C. This measurement provides the number of failed terminating calls. The following reasons apply: Subcounter 1 is BlockUnavailTrunk: calls congested for lack of available trunks; Subcounter 2 is BlockCongestion: calls congested because of exchanges internal congestion; Subcounter 3 is AbnRelease: abnormal releases or other reasons.
D. An integer value E. The measurement name has the form TRM.failTermCalls.Cause where Cause indicates the number of the cause that triggered the terminating call loss F. MscFunction
G. Circuit Switched
H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 101
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
9.1.2.13 Number of incoming call attempts A. This measurement provides the number of attempted incoming calls in the exchange. B. CC C. This measurement is incremented on receipt by the MSC of an ISUP message IAM [33], a TUP IAI message [34][35] or a TUP IAM message [34][35] from the switching located at the PSTN or from another MSC. D. An integer value E. TRM.attIncCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.14 Number of successful Incoming Calls A. This measurement provides the number of successful incoming calls in the exchange. B. CC C. This measurement is incremented on the transmission of a TUP message ACM [34][35] from the MSC to originating exchange. D. An integer value E. TRM.succIncCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.15 Number of answered incoming calls A. This measurement provides the number of answered incoming calls in the exchange. B. CC C. This measurement is incremented on the transmission of an ISUP message ANM [33], a TUP message ANN [34][35], or a TUP message ANC [34][35] from the MSC to originating exchange. D. An integer value
2006 3GPP2
Page 102
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
E. TRM.ansIncCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.16 Number of failed incoming calls for various reasons A. This measurement provides the number of failed incoming calls for every specified reason. This measurement is split into subcounters per event triggering cause. B. CC C. This measurement provides the number of failed incoming calls for every specified reason. The following reasons apply: Subcounter 1 is BlockUnavailTrunk: calls congested for lack of available trunks; Subcounter 2 is BlockCongestion: calls congested because of exchanges internal congestion; Subcounter 3 is AbnRelease: abnormal releases or other reasons.
D. An integer value E. The measurement name has the form TRM.failIncCalls.Cause where Cause indicates the number of the cause that triggered the incoming call loss F. MscFunction
G. Circuit Switched
H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.17 Number of outgoing call attempts A. This measurement provides the number of attempted outgoing calls in the exchange. B. CC C. This measurement is incremented on the transmission of an ISUP message IAM [33], a TUP message IAM [34][35] or a TUP message IAI [34][35] from the MSC. D. An integer value E. TRM.attOutCalls
2006 3GPP2
Page 103
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.18 Number of successful outgoing Calls A. This measurement provides the number of successful outgoing calls in the exchange. B. CC C. This measurement is incremented on receipt by the MSC of a TUP message ACM [34][35]. D. An integer value E. TRM.succOutCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.19 Number of outgoing call answers A. This measurement provides the number of answered outgoing calls in the exchange. B. CC C. This measurement is incremented on receipt by the MSC of an ISUP message ANM [33], a TUP message ANN [34][35], or a TUP message ANC [34][35]. D. An integer value E. TRM.ansOutCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.20 Number of failed outgoing calls for various reasons A. This measurement provides the number of failed outgoing calls for every specified reason. This measurement is split into subcounters per event triggering cause.
2006 3GPP2 Page 104
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
B. CC C. This measurement provides the number of failed outgoing calls. The following reasons apply: Subcounter 1 is BlockUnavailTrunk: calls congested for lack of available trunks; Subcounter 2 is BlockCongestion: calls congested because of exchanges internal congestion; Subcounter 3 is AbnRelease: abnormal releases or other reasons.
D. An integer value E. The measurement name has the form TRM.failOutCalls.Cause where Cause indicates the number of the cause that triggered the incoming call loss F. MscFunction
G. Circuit Switched
H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.21 Number of transit call attempts A. This measurement provides the number of attempted transit calls in the exchange. B. CC C. This measurement is incremented on the transmission of an ISUP message IAM [33], a TUP message IAM [34][35] or a TUP message IAI [34][35] from the MSC to terminating exchange. D. An integer value E. TRM.attTransCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.22 Number of successful transit Calls A. This measurement provides the number of successful transit calls in the exchange. B. CC
2006 3GPP2
Page 105
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. This measurement is incremented when the MSC transfer the TUP message ACM [34][35] to the originating exchange, after receiving a TUP message ACM from the terminating exchange. D. An integer value E. TRM.succTransCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.23 Number of transit call answers A. This measurement provides the number of answered transit calls in the exchange. B. CC C. This measurement is incremented when the MSC transfers the answer message to originating exchange, after receiving the answer signal from terminating exchange. D. An integer value E. TRM.ansTransCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.24 Number of failed transit calls for various reasons A. This measurement provides the number of failed transmit calls for every specified reason. This measurement is split into subcounters per event triggering cause. B. CC C. This measurement provides the number of failed transmit calls for every specified reason. The following reasons apply: Subcounter 1 is BlockUnavailTrunk: calls congested for lack of available trunks; Subcounter 2 is BlockCongestion: calls congested because of exchanges internal congestion; Subcounter 3 is AbnRelease: abnormal releases or other reasons.
2006 3GPP2
Page 106
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
D. An integer value E. The measurement name has the form TRM.failTrans.Cause where Cause indicates the number of the cause that triggered the transit call loss. F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.25 Number of originating outgoing call attempts A. This measurement provides the number of attempted originating outgoing calls in the exchange. B. CC C. This measurement is incremented when the MSC determines the call is an outgoing call by number analysis, after receiving a DTAP message CM Service Request [23]. D. An integer value E. TRM.attOrigOutCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.26 Number of successful originating outgoing calls A. This measurement provides the number of successful originating outgoing calls in the exchange (successful seizures of originating outgoing calls). B. CC C. This measurement is incremented on receipt by the MSC from the terminating exchange of a TUP message ACM [34][35] for originating outgoing calls. D. An integer value E. TRM.succOrigOutCalls F. MscFunction G. Circuit Switched H. All
2006 3GPP2 Page 107
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.27 Number of originating outgoing call answers A. This measurement provides the number of answered originating outgoing calls in the exchange B. CC C. This measurement is incremented on receipt by the MSC from the terminating exchange of an ISUP message ANM [33], a TUP message ANN [34][35], or a TUP message ANC [34][35] for originating outgoing calls. D. An integer value E. TRM.ansOrigOutCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.28 Number of failed originating outgoing calls for various reasons A. This measurement provides the number of failed originating outgoing calls for every specified reason. This measurement is split into subcounters per event triggering cause. B. CC C. This measurement provides the number of failed originating outgoing calls. The following reasons apply: Subcounter 1 is BlockUnavailTrunk: calls congested for lack of available trunks; Subcounter 2 is BlockCongestion: calls congested because of exchanges internal congestion; Subcounter 3 is AbnRelease: abnormal releases or other reasons.
D. An integer value E. The measurement name has the form TRM.failOrigOutCalls.Cause where Cause indicates the number of the cause that triggered the originating outgoing call loss. F. MscFunction G. Circuit Switched H. All
2006 3GPP2
Page 108
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.29 Number of incoming terminating call attempts A. This measurement provides the number of attempted terminating incoming calls in the exchange. B. CC C. This measurement is incremented when the MSC determines that the call is a terminating call by number analysis, after receiving an ISUP message IAM [33], a TUP message IAM [34][35] or a TUP message IAI [34][35]. D. An integer value E. TRM.attTermIncCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.30 Number of Successful Incoming Terminating Calls A. This measurement provides the number of successful terminating incoming calls in the exchange. B. CC C. This measurement is incremented on the transmission of a TUP message ACM [34][35] from the MSC to originating exchange for terminating incoming calls. D. An integer value E. TRM.succTermIncCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.31 Number of incoming terminating call answer A. This measurement provides the number of answered terminating incoming calls in the exchange. B. CC
2006 3GPP2
Page 109
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
C. This measurement is incremented on the transmission of an ISUP message ANM, a TUP message ANN, or a TUP message ANC from the MSC to originating exchange for terminating incoming calls. D. An integer value E. TRM.ansTermIncCalls F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.32 Number of failed incoming terminating calls for various reasons A. This measurement provides the number of failed terminating incoming calls for every specified reason. This measurement is split into subcounters per event triggering cause. B. CC C. This measurement provides the number of failed terminating incoming calls for every specified reason. The following reasons apply: Subcounter1 is BlockUnavailTrunk: calls congested for lack of available trunks; Subcounter 2 is BlockCongestion: calls congested because of exchanges internal congestion; Subcounter 3 is AbnRelease: abnormal releases or other reasons.
D. An integer value E. The measurement name has the form TRM.failTermIncCalls.Cause where Cause indicates the number of the cause that triggered the incoming terminating call loss F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.33 Successful Traffic Volume for Mobile Originating Calls A. This measurement provides the traffic volume of successful originating calls (in erlang). B. DER (n=1)
2006 3GPP2
Page 110
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
C. This measurement is based on two different cases. For internal calls, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of a BSMAP message "Assignment Complete" [23] about the called party from BSC and the corresponding call clearing via the BSMAP message Clear Complete [23] during a granularity period. For outgoing calls, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of a TUP message "ACM" [34][35] from terminating exchange and the corresponding call clearing during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succOrigCallTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.34 Successful traffic volume for MSC calls A. This measurement provides the traffic volume of successful internal calls (in erlang). B. DER (n=1) C. This measurement is obtained by accumulating the time intervals for every successful internal call between the receipt by the MSC from BSC of a BSMAP message "Assignment Complete" [23] about the called party and the corresponding call clearing via the BSMAP message Clear Complete [23] during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succInternalCallTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 111
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
9.1.2.35 Successful Traffic Volume For Mobile Terminating Calls A. This measurement provides the traffic volume of successful terminating calls (in erlang). B. DER (n=1) C. This measurement is obtained by accumulating the time intervals for every successful terminating call between the receipt by the MSC from BSC of a BSMAP message "Assignment Complete" [23] about the called party and the corresponding call clearing via the BSMAP message Clear Complete [23] during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succTermCallTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.36 Successful traffic volume for incoming calls A. This measurement provides the traffic volume of successful incoming calls (in erlang). B. DER (n=1) C. This measurement is obtained by accumulating the time intervals for every successful incoming call between the transmission of a TUP message "ACM [34][35] from the MSC and the corresponding call clearing during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succIncCallTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 112
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
9.1.2.37 Successful traffic volume for outgoing calls A. This measurement provides the traffic volume of successful outgoing calls (in erlang). B. DER (n=1) C. This measurement is obtained by accumulating the time intervals for every successful outgoing call between the receipt by the MSC of a TUP message "ACM [34][35] and the corresponding call clearing during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succOutCallTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.38 Successful traffic volume for transit calls A. This measurement provides the traffic volume of successful transmit calls (in erlang). B. DER (n=1) C. This measurement is obtained by accumulating the time intervals for every successful transmit calls between transmission of an ISUP message ACM [33] or TUP message ACM [34][35] from the MSC to originating exchange after receiving the ACM message from terminating exchange and the corresponding call clearing during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succTransCallTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 113
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
9.1.2.39 Traffic volume for successful originating outgoing calls A. This measurement provides the traffic volume of successful originating outgoing calls (in erlang). B. DER (n=1) C. This measurement is obtained by accumulating the time intervals for every successful originating outgoing calls between the receipt by the MSC from terminating exchange of an ISUP message ACM [33] or TUP message "ACM" [34][35] and the corresponding call clearing during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succOrigOutCallTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.40 Traffic Volume For Successful Incoming Terminating Calls A. This measurement provides the traffic volume of successful terminating incoming calls (in erlang). B. DER (n=1) C. This measurement is obtained by accumulating the time intervals for every successful terminating incoming calls between the transmission of an ISUP message ACM [33] or TUP message "ACM [34][35] from the MSC and the corresponding call clearing during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succTermIncCallTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 114
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
9.1.2.41 Occupation traffic volume of out-trunk calls A. This measurement provides the traffic volume from the seizure of trunk circuits to the corresponding call releases (normal releases, abnormal releases) for the outgoing calls. This count is valid for one-way-out or two-way circuit end point subgroups (in erlang). B. DER (n=1) C. This measurement is based on two different cases. For circuits to BSC, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of a BSMAP message Assignment Complete [23] about the called party from BSC and the corresponding call clearing via the BSMAP message Clear Complete [23] during a granularity period. For circuits to other exchanges, the measurement is obtained by accumulating the time intervals between the transmission of an ISUP message IAM [33], a TUP message "IAM" [34][35] or a TUP message IAI [34][35] from the MSC and the corresponding backward message to indicate successful seizures of trunk circuits during a granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succOutSeizureTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.2.42 Occupation traffic volume of incoming trunk calls A. This measurement provides the traffic volume from the seizure of trunk circuits to the corresponding call releases (normal releases, abnormal releases) for the incoming calls. This count is valid for one-way-in or two-way circuit end point subgroups (in erlang). B. DER (n=1) C. This measurement is based on two different cases. For circuits to BSC, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of a BSMAP message Assignment Complete [23] about the calling party from BSC and the corresponding call clearing via the BSMAP message Clear Complete [23] during a granularity period. For circuits to other exchanges, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of an ISUP message IAM [33], a TUP message "IAM" [34][35] or a TUP message IAI [34][35] and the corresponding call clearing during a
2006 3GPP2 Page 115
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
granularity period. The end value of this time will then be divided by the granularity period to convert to the traffic volume. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. TRM.succIncSeizureTraffic F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.3 Handoff Measurements 9.1.3.1 Number of outgoing handoff requests A. This measurement provides the number of attempted outgoing handoff from the anchor MSC or serving MSC to the target MSC. B. CC C. The relevant measurement is incremented on transmission of a MAP message FACDIR2 [36] from the anchor MSC or serving MSC to the target MSC for an outgoing Handoff-Forward; or transmission of a MAP message HANDBACK2 [36] from the serving MSC to the target MSC for an outgoing Handoff-Back; or transmission of a MAP message HANDTHIRD2 [36] from the serving MSC for an outgoing Handoff-ToThird. D. An integer value E. HO.attOutHos F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.3.2 Number of successful outgoing handoff requests A. This measurement provides the number of successful outgoing handoff from the anchor MSC or serving MSC to the target MSC. B. CC C. The relevant measurement is incremented on receipt by the serving MSC of a MAP message MSONCH (MobileOnChannel) [36] for an outgoing Handoff-Forward; or receipt by the anchor MSC or serving
2006 3GPP2
Page 116
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
MSC of a MAP message FACREL (FacilitiesRelease) [36] for an outgoing Handoff-Back or Handoff-To-Third. D. An integer value E. HO.succOutHos F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.3.3 Number of incoming handoff requests A. This measurement provides the number of attempted incoming handoff from the anchor MSC or serving MSC to the target MSC. B. CC C. The relevant measurement is incremented on receipt by the target MSC of a MAP message FACDIR2 [36] for an incoming Handoff-Forward or Handoff-To-Third; or receipt by the target MSC of a MAP message HANDBACK2 [36] for an incoming Handoff-Back. D. An integer value E. HO.attIncHos F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.3.4 Number of successful incoming handoff requests A. This measurement provides the number of successful incoming handoff from the anchor MSC or serving MSC to the target MSC. B. CC C. The relevant measurement is incremented on transmission of a MAP message MSONCH (MobileOnChannel) [36] from the target MSC for an incoming Handoff-Forward; or transmission of a MAP message FACREL (FacilitiesRelease) [36] from the target MSC for an incoming Handoff-Back or Handoff-To-Third. D. An integer value E. HO.succIncHos F. MscFunction
2006 3GPP2
Page 117
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.4 QoS Measurements 9.1.4.1 Mean time to set up call service A. This measurement provides the mean time during each granularity period for call setup (in milliseconds). B. DER (n=1) C. This measurement is based on two different cases. For internal calls, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of a DTAP message "CM Service Request" (which service option value is 8000H, 0011H or 0003H, see Annex A) [23] about the calling party from BSC and the corresponding BSMAP message "Assignment Complete" [23] about the called party from BSC during a granularity period. For outgoing calls, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of a DTAP message "CM Service Request" [23] (which service option value is 8000H, 0011H or 0003H) about the calling party from BSC and the corresponding ISUP message ACM [33] or TUP message "ACM" [34][35] during a granularity period. The end value of this time will then be divided by the number of collected time intervals observed in the granularity period to give the arithmetic mean. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. QoS.meanDurOfCallSetup F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.4.2 Mean call duration A. This measurement provides the mean time during each granularity period for conversation (in seconds). B. DER (n=1) C. This measurement is based on two different cases. For internal calls, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of a DTAP message "Connect" [23] from
2006 3GPP2 Page 118
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
BSC and the transmission of the corresponding BSMAP message "Clear Command" [23] from the MSC during a granularity period. For outgoing calls, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of an ISUP message "ANM" message [33], a TUP message ANN [34][35] or a TUP message ANC [34][35] and the transmission of the corresponding BSMAP message "Clear Command [23] from the MSC during a granularity period. The end value of this time will then be divided by the number of collected time intervals observed in the granularity period to give the arithmetic mean. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. QoS.meanCallDur F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.4.3 Mean Trunk Seizure Duration A. This measurement provides the mean time during each granularity period for the seizure of trunks (in seconds). B. DER (n=1) C. This measurement is based on two different cases. For circuits to BSC, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of a BSMAP message "Assignment Complete" [23] from BSC and the transmission of the corresponding BSMAP message "Clear Command" [23] from the MSC during a granularity period. For circuits to other exchanges, the measurement is obtained by accumulating the time intervals between the receipt by the MSC of an ISUP message ACM [33] or TUP message "ACM" [34][35] and the corresponding call clearing during a granularity period. The end value of this time will then be divided by the number of collected time intervals in the granularity period to give the arithmetic mean. The accumulator shall be reinitialized at the beginning of each granularity period. D. A value of type Real E. QoS.meanDurOfTrunkSeizure F. MscFunction G. Circuit Switched H. All
2006 3GPP2 Page 119
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.5 SMS Measurements 9.1.5.1 Number of originating Point-to-point SMS attempts A. This measurement provides the number of attempted originating pointto-point SMS from MS to the MSC. B. CC C. The relevant measurement is incremented when the MSC receives a DTAP message CM Service Request [23] the Service Type of the CM Service Type element set to 0100 (i.e., Short Message Transfer) from BSC, or receives a SMS short message SMS-MO [37] from MS, including the short messages on Access Channels and Traffic Channels. D. An integer value E. SMS.attOrigP2PSms F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.5.2 Number of successful originating Point-to-point SMS A. This measurement provides the number of successful originating pointto-point SMS from MS to the MSC. B. CC C. The relevant measurement is incremented on receipt by the MSC from MC of a MAP message smdpp (SMSDeliveryPointToPoint) [36], which indicates the successful originating point-to-point SMS. D. An integer value E. SMS.succOrigP2PSms F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 120
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
9.1.5.3
Number of terminating Point-to-point SMS attempts
A. This measurement provides the number of attempted terminating point-to-point SMS from the MSC to MS. B. CC C. The relevant measurement is incremented on receipt by the MSC from MC of a MAP message SMDPP (SMSDeliveryPointToPoint) [36], which indicates the attempted terminating point-to-point SMS. D. An integer value E. SMS.attTermP2PSms F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.1.5.4 Number of successful terminating Point-to-point SMS attempts A. This measurement provides the number of successful terminating point-to-point SMS from the MSC to MS. B. CC C. The relevant measurement is incremented on the transmission of a MAP message smdpp (SMSDeliveryPointToPoint) [36] from the MSC to the MC, which indicates the successful terminating point-to-point SMS. D. An integer value E. SMS.succTermP2PSms F. MscFunction G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2 Circuit End Point Subgroup Measurements A Circuit End Point Subgroup is a set of circuit end points that directly interconnect a MSC with another network element (e.g. MSC, BSC). It is a subset of the circuit end points between the two network elements. These performance measurements may not be applicable for each type of potential network element that can interface with a MSC (as an example, not all network elements communicate via ISUP and TUP messages) (see also [30]).
2006 3GPP2
Page 121
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
9.2.1 Outgoing call measurements 9.2.1.1 Number of outgoing call attempts A. This measurement provides the number of attempted seizures of trunk circuits for outgoing calls for this circuit endpoint subgroup. This count is valid for one-way-out or two-way circuit end point subgroups. B. CC C. This measurement is incremented on the selection of route for the outgoing call in the MSC. D. An integer value E. TRM.outBids F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2.1.2 Number of outgoing call occupations A. This measurement provides the number of successful seizures of trunk circuits for outgoing calls. This count is valid for one-way-out or two-way circuit end point subgroups. B. CC C. This measurement is based on two different cases. For circuits to other exchanges, after transmitting the ISUP message IAM [33], TUP message IAM [34][35] or TUP message IAI [34][35], the MSC receives a corresponding return message that indicates successful seizures of trunk circuits. For circuits to BSC, on receipt by the MSC of a BSMAP message Assignment Complete [23] about the called party from BSC. D. An integer value E. TRM.succOutSeizures F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2.1.3 Number of answers to outgoing calls A. This measurement provides the number of answered outgoing calls. This count is valid for one-way-in or two-way circuit end point subgroups.
2006 3GPP2 Page 122
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
B. CC C. This measurement is based on two different cases. For circuits to other exchanges, on receipt by the MSC of an ISUP message ANM [33] a TUP message ANN [34][35] or a TUP message ANC [34][35]. For interface circuits to BSC, on receipt by the MSC of a DTAP message Connect [23] about the called party from BSC. D. An integer value E. TRM.ansOutSeizures F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2.1.4 Total number of available out-trunks A. This measurement provides the number of available trunk circuits for outgoing calls. This count is valid for one-way-in or two-way circuit end point subgroups. B. GAUGE C. This measurement provides the number of available trunk circuits for outgoing calls. This measurement is valid for one-way-out or two-way circuit end point subgroups. D. An integer value E. TRM.nbrOutAvailTrunks F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2.2 Incoming Call Measurements 9.2.2.1 Number of incoming trunk call occupations A. This measurement provides the number of successful seizures of trunk circuits for incoming calls. This count is valid for one-way-in or two-way circuit end point subgroups. B. CC C. This measurement is based on two different cases. For circuits to other exchanges, on receipt by the MSC of an ISUP message IAM [33], TUP message IAM [34][35] or TUP message IAI [34][35] on incoming
2006 3GPP2 Page 123
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
circuits. For circuits to BSC, on receipt by the MSC of a BSMAP message Assignment Complete [23] about the calling party from BSC. D. An integer value E. TRM.succIncSeizures F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2.2.2 Total number of blocked out-trunks A. This measurement provides the number of blocked trunk circuits for outgoing calls. This count is valid for one-way-in or two-way circuit end point subgroups. B. GAUGE C. This measurement provides the number of blocked trunk circuits for outgoing calls. This count is valid for one-way-out or two-way circuit end point subgroups. D. An integer value E. TRM.nbrOutBlockedTrunks F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2.2.3 Number of answers to incoming trunk calls A. This measurement provides the number of answered incoming calls, This count is valid for one-way-in or two-way circuit end point subgroups. B. CC C. This measurement is based on two different cases. For circuits to other exchanges, on transmitting of the ISUP message ANM [33], TUP message ANN [34][35] or TUP message ANC [34][35] from the MSC to originating exchange, For circuits to BSC, on receipt by the MSC of an ISUP message ANM, a TUP message ANN or a TUP message ANC from terminating exchange. D. An integer value E. TRM.ansIncSeizures
2006 3GPP2 Page 124
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2.2.4 Total number of available incoming trunks A. This measurement provides the number of available trunk circuits for incoming calls. This count is valid for one-way-in or two-way circuit end point subgroups. B. GAUGE C. This measurement provides the number of available trunk circuits for incoming calls. D. An integer value E. TRM.nbrIncAvailTrunks F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 9.2.2.5 Total number of blocked incoming trunks A. This measurement provides the number of blocked trunk circuits for incoming calls. This count is valid for one-way-in or two-way circuit end point subgroups. B. GAUGE C. This measurement provides the number of blocked inter-exchange trunk circuits. D. An integer value E. TRM.nbrIncBlockedTrunks F. CircuitEndPointSubGroup G. Circuit Switched H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 125
3GPP2 S.S0093-0 v2.0
1 2
10 Measurements Related to the Service Network 10.1 Measurements related to the MMS Relay/Server
MMS User Databases
HLR
MMS VAS Applications
MM6
MM5 MM7
MMS User Agent A
MM1
Relay
MMS Relay/Server
MM2
Server
MM3 Foreign MMS Relay/Server MM1 MMS User Agent B MM4 External Server #1 (e.g. E-Mail) External Server #2 (e.g. Fax) External Server #3 (e.g. UMS)
...
External Server #N
3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Figure 3. MMS Reference Architecture [21] MM1 [21]: Reference point MM1 is used to submit Multimedia Messages from MMS User Agent to MMS Relay/Server, to let the MMS User Agent pull MMs from the MMS Relay/Server, let the MMS Relay/Server push information about MMs to the MMS User Agent as part of an MM notification, and to exchange delivery reports between MMS Relay/Server and MMS User Agents. MM2 [21]: not specified yet MM3 [21]: Reference point MM3 is used by the MMS Relay/Server to send Multimedia Messages to and retrieve MMs from servers of external (legacy) messaging systems that are connected to the service provider's MMS Relay/Server. MM4 [21]: Reference point MM4 between MMS Relay/Servers belonging to different MMSEs is used to transfer messages between them. MM5 [21]: Reference point MM5 may be used to provide information to the MMS Relay/Server about the subscriber. MM6 [21]: not specified
2006 3GPP2
Page 126
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
MM7 [21]: Reference point MM7 is used to transfer MMs from MMS Relay/Server to MMS VAS applications and to transfer MMs from MMS VAS applications to MMS Relay/Server. MMS uses a number of technologies to realize the requirements of the stage 1 description [20]. As far as possible existing protocols (e.g. WAP, SMTP, ESMTP as transfer protocols; lower layers to provide push, pull, notification) and existing message formats (e.g. SMIL, MIME) shall be used for the realization of the Multimedia Messaging Service. In order to define generic measurements, 3GPP2 should specify Performance measurements based on the Reference Points (MM1 to MM7) and not specific to the protocol implemented. So whatever the implementation IP or WAP for example, the Reference Point messages are generic and so the measurements will be the same. The main interfaces involve in the MMS delivery are the interface MM1 and MM4, we can see in this diagram the exact messages involve in the delivery. Those messages can be used to define Performance Measurement on a MMS Relay/Server basis.
Originator MMS Relay/ Server Recipient MMS Relay/ Server
Originator MMS UA
Recipient MMS UA
MM1_submit. REQ MM1_submit. RES MM4_forward.REQ MM4_forward.RES MM1_notification. REQ MM1_notification. RES MM1_retrieve.REQ MM1_retrieve.RES
MM4_delivery_report.REQ MM1_delivery_ report.REQ MM4_delivery_report.RES MM4_read_reply_report.REQ MM1_read_reply_ originator.REQ MM4_read_reply_report.RES
MM1_acknowledge ment.REQ
MM1_read_reply_ recipient.REQ
18 19 20 21
Figure 4. Example Abstract Message Flow [21] The most important quality metrics for MMS are availability, accuracy and speed. This section addresses the first two, the speed will require additional
2006 3GPP2 Page 127
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
measurements based on time to deliver the multimedia messages. Availability and accuracy are a measure of the percentage of request that are successfully served and how complete the response is. The mentioned triggering points enable to define raw number of messages sent and received by the MMS Relay/Server, but is not good enough to gather service quality measurement, because those are only volume measurements. Also Response messages provide an acknowledgement mechanism for the request messages and those response messages can be positive or negative acknowledgement. This information is in the Request Status code which is contained by the Request Status field in the response messages. So in order to gather service quality measurements, a higher granularity is required for the response messages measurements: sub-counters per request status code are introduced for that purpose. This is for MM1 submission and retrieval as well as every MM4 response messages measurements. 10.1.1 Background Information on the Request Status [21] The originator MMS Relay/Server shall indicate the status of the MM1_submit.REQ in the associated MM1_submit.RES. The reason code given in the status information element of the MM1_submit.RES may be supported with an explanatory text further qualifying the status. If this text is available in the Request status text information element the MMS User Agent should bring it to the user's attention. The choice of the language used in the Request status text information element is at the discretion of the MMS service provider.
Table 1: Information elements in the MM1_submit.RES [21]
Information element Message Type Transaction ID MMS Version Request Status Request Status Text Message ID Store Status Store Status
Presence Mandatory Mandatory Mandatory Mandatory Optional
Description Identifies this message as MM1_submit.RES The identification of the MM1_submit.REQ/MM1_submit.RES pair Identifies the version of the interface supported by the MMS Relay/Server. The status of the MM submit request. Description which qualifies the status of the MM submit request
Conditional The identification of the MM if it is accepted by the originator MMS Relay/Server Conditional If the Store request was present in MM1_submit.REQ, the status of the store request. Optional The explanatory text corresponding to the Store
2006 3GPP2
Page 128
3GPP2 S.S0093-0 v2.0
Information element Text Stored Message Reference 1
Presence Status, if present.
Description
Conditional If the Store request was present in MM1_submit.REQ, the message reference to the newly stored MM.
Table 2: Example of Request Status Code
Request-StatusCode Ok Error-unspecified Error-service-denied
Meaning The corresponding request and some or all of its contents were accepted without errors. An unspecified error occurred during the processing or reception of the corresponding request. The corresponding request was rejected due to failure of authentication or authorization of the originating MMS Relay/Server. An inconsistency with the message format was detected when the corresponding request was parsed. There were no MMS address (From:, To:, Cc:, Bcc:) in its proper format or none of the addresses belong to the recipient MMS Relay/Server. This status code is obsolete The recipient MMS Relay/Server was not able to accept the corresponding request due to capacity overload. The MM content was not accepted due to size, media type, copyrights or some other reason. The recipient MMS Relay/Server does not support the corresponding request abstract message.
Error-messageformat-corrupt Error-sendingaddress-unresolved Error-message-notfound Error-networkproblem Error-content-notaccepted Error-unsupportedmessage 2 3 4 5 6 7 8 9 10.1.2 MM1
MM1 is the interface between the MMS Relay/Server and the MMS User Agent, following are the measurements: 10.1.2.1 Number of Multimedia Messages submit requests received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) submit requests received by MMS Relay/Server from MMS User Agent on the Reference point MM1.
2006 3GPP2
Page 129
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
B. CC C. On receipt of a "MM1_submit.REQ" message from MMS User Agent (see [21] for more details). D. An integer value E. MMS.MM1SubReq F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.2 Number of Multimedia Messages submit responses sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) submit responses sent by MMS Relay/Server to MMS User Agent on the Reference point MM1. The measurement is pegged by request status code. B. CC C. On transmission of a MM1_submit.RES" message to MMS User Agent. Each submit responses is added to the relevant measurement according to the request status code (see [21] for more details). D. An integer value E. The measurement name has the form MMS.MM1SubRes.Status where Status identifies the request status code. F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.3 Number of Multimedia Messages notification requests sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) notification requests sent by MMS Relay/Server to MMS User Agent on the Reference point MM1. B. CC C. On transmission of a MM1_notification.REQ" message to MMS User Agent (see [21] for more details). D. An integer value
2006 3GPP2 Page 130
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
E. MMS.MM1NotReq F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.4 Number of Multimedia Messages notification responses received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) notification responses received by MMS Relay/Server from MMS User Agent on the Reference point MM1. B. CC C. On receipt of a MM1_notification.RES" message from MMS User Agent (see [21] for more details). D. An integer value E. MMS.MM1NotRes F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.5 Number of Multimedia Messages retrieve requests received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) retrieve requests received by MMS Relay/Server from MMS User Agent on the Reference point MM1. B. CC C. On receipt of a MM1_retrieve.REQ" message from MMS User Agent (see [21] for more details). D. An integer value E. MMS.MM1RetReq F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 131
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
10.1.2.6 Number of Multimedia Messages retrieve responses sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) retrieve responses sent by MMS Relay/Server to MMS User Agent on the Reference point MM1. The measurement is pegged by request status code. B. CC C. On transmission of a MM1_retrieve.RES" message to MMS User Agent. Each retrieve responses is added to the relevant measurement according to the request status code (see [21] for more details). D. An integer value E. The measurement name has the form MMS.MM1RetRes.Status where Status identifies the request status code. F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.7 Number of Multimedia Messages received by MMS Relay/Server acknowledgement requests
A. This measurement provides the number of Multimedia Messages (MM) acknowledgement requests received by MMS Relay/Server from MMS User Agent on the Reference point MM1. B. CC C. On receipt of a MM1_acknowledgement.REQ" message from MMS User Agent (See [21] for more details). D. An integer value E. MMS.MM1AckReq F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 132
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
10.1.2.8 Number of Multimedia Messages forward requests received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) forward requests received by MMS Relay/Server from MMS User Agent on the Reference point MM1. B. CC C. On receipt of a MM1_forward.REQ" message from MMS User Agent (See [21] for more details). D. An integer value E. MMS.MM1fwdREQ F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.9 Number of Multimedia Messages forward responses sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) forward responses sent by MMS Relay/Server to MMS User Agent on the Reference point MM1. B. CC C. On transmission of a MM1_forward.RES" message to MMS User Agent (See [21] for more details). D. An integer value E. MMS.MM1FwdRes F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.10 Number of Multimedia Messages delivery report requests sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) delivery report requests sent by MMS Relay/Server to MMS User Agent on the Reference point MM1. B. CC
2006 3GPP2
Page 133
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. On transmission of a MM1_delivery_report.REQ" message to MMS User Agent (See [21] for more details). D. An integer value E. MMS.MM1RepReq F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.11 Number of Multimedia Messages read reply recipient requests received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) read reply recipient requests received by MMS Relay/Server to MMS User Agent on the Reference point MM1. B. CC C. On receipt of a MM1_read_reply_recipient.REQ" message from MMS User Agent (See [21] for more details). D. An integer value E. MMS.MM1ReadRecReq F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.2.12 Number of Multimedia Messages read reply originator requests sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) read reply originator requests sent by MMS Relay/Server to MMS User Agent on the Reference point MM1. B. CC C. On transmission of a MM1_read_reply_originator.REQ" message to MMS User Agent (See [21] for more details). D. An integer value E. MMS.MM1ReadOrigReq F. MrsFunction G. Valid for packet switching.
2006 3GPP2
Page 134
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3 MM4 MM4 is the interface between MMS Relay/Servers, following are the measurements: 10.1.3.1 Number of Multimedia Messages forward requests received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) forward requests received by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. B. CC C. On receipt of a MM4_forward.REQ" message from MMS Relay/Server (See [21] for more details). D. An integer value E. MMS.MM4FwdReqRec F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.2 Number of Multimedia Messages forward requests sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) forward requests sent by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. B. CC C. On transmission of a MM4_forward.REQ" message to MMS Relay/Server (See [21] for more details). D. An integer value E. MMS.MM4FwdReqSnt F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 135
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
10.1.3.3 Number of Multimedia Messages forward responses received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) forward responses received by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. The measurement is pegged by request status code. B. CC C. On receipt of a MM4_forward.RES" message from MMS Relay/Server. Each forward response is added to the relevant measurement according to the request status code (see [21] for more details). D. An integer value E. The measurement name has the form MMS.MM4FwdResRec.Status where Status identifies the request status code. F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.4 Number of Multimedia Messages forward responses sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) forward responses sent by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. The measurement is pegged by request status code. B. CC C. On transmission of a MM4_forward.RES" message to MMS Relay/Server. Each forward response is added to the relevant measurement according to the request status code (see [21] for more details). D. An integer value E. The measurement name has the form MMS.MM4FwdResSnt.Status where Status identifies the request status code. F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 136
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
10.1.3.5 Number of Multimedia Messages delivery report requests received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) delivery report requests received by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. B. CC C. On receipt of a MM4_ delivery_report.REQ" message from MMS Relay/Server (See [21] for more details). D. An integer value E. MMS.MM4RepReqRec F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.6 Number of Multimedia Messages delivery report requests sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) delivery report requests sent by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. B. CC C. On transmission of a MM4_ delivery_report.REQ" message to MMS Relay/Server (See [21] for more details). D. An integer value E. MMS.MM4RepReqSnt F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.7 Number of Multimedia Messages received by MMS Relay/Server delivery report responses
A. This measurement provides the number of Multimedia Messages (MM) delivery report responses received by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. The measurement is pegged by request status code. B. CC
2006 3GPP2 Page 137
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
C. On receipt of a MM4_ delivery_report.RES" message from MMS Relay/Server. Each delivery report responses is added to the relevant measurement according to the request status code (see [21] for more details). D. An integer value E. The measurement name has the form MMS.MM4RepResRec.Status where Status identifies the request status code. F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.8 Number of Multimedia Messages delivery report responses sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) delivery report responses sent by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. The measurement is pegged by request status code. B. CC C. On transmission of a MM4_delivery_report.RES" message to MMS Relay/Server. Each delivery report responses is added to the relevant measurement according to the request status code (see [21] for more details). D. An integer value E. The measurement name has the form MMS.MM4RepResSnt.Status where Status identifies the request status code. F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.9 Number of Multimedia Messages read reply requests received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) read reply requests received by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. B. CC
2006 3GPP2
Page 138
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
C. On receipt of a MM4_ read_reply.REQ" message from MMS Relay/Server (See [21] for more details). D. An integer value E. MMS.MM4ReadReqRec F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.10 Number of Multimedia Messages read reply requests sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) read reply requests sent by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. B. CC C. On transmission of a MM4_ read_reply.REQ" message to MMS Relay/Server (See [21] for more details). D. An integer value E. MMS.MM4ReadReqSnt F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.11 Number of Multimedia Messages read reply responses received by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) read reply responses received by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. The measurement is pegged by request status code. B. CC C. On receipt of a MM4_ read_reply.RES" message from MMS Relay/Server. Each read reply responses is added to the relevant measurement according to the request status code (see [21] for more details). D. An integer value
2006 3GPP2
Page 139
3GPP2 S.S0093-0 v2.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
E. The measurement name has the form MMS.MM4ReadResRec.Status where Status identifies the request status code. F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities. 10.1.3.12 Number of Multimedia Messages read reply responses sent by MMS Relay/Server A. This measurement provides the number of Multimedia Messages (MM) read reply responses sent by MMS Relay/Server from another MMS Relay/Server on the Reference point MM4. The measurement is pegged by request status code. B. CC C. On transmission of a MM4_read_reply.RES" message to MMS Relay/Server. Each read reply responses is added to the relevant measurement according to the request status code (see [21] for more details). D. An integer value E. The measurement name has the form MMS.MM4ReadResSnt.Status where Status identifies the request status code. F. MrsFunction G. Valid for packet switching. H. All I. This measurement is mainly dedicated to Operator Traffic Engineering and Operator Business communities.
2006 3GPP2
Page 140
3GPP2 S.S0093-0 v2.0
1 2 3 4
Annex A: 3GPP2 Service Options The following list providing the 3GPP2 Service Options [23], including indication on type of service (CS or PS). Service Option Value (hex) 8000H 0011H 0003H 801FH 0004H 0005H 0007H 0023H 0024H 0009H 0038H 000CH 000DH 0006H 000EH 000FH 0012H 0013H 0020H 0036H 0037H 0016H 13K speech 13K high rate voice service EVRC 13K Markov Asynchronous Data rate set 1 Group 3 Fax rate set 1 Packet Data Service: Internet or ISO Protocol Stack (Revision 0) Position Determination Service (PDS) Rate Set 1 Position Determination Service (PDS) Rate Set 2 13K loopback Selectable Mode Vocoder (SMV) Asynchronous Data rate set 2 Group 3 Fax rate set 2 SMS rate set 1 SMS rate set 2 Packet Data Service: Internet or ISO Protocol Stack (14.4 kbps) OTAPA Rate Set 1 OTAPA Rate Set 2 IS-2000 Test Data IS-2000 Markov IS-2000 Loopback High Speed Packet Data Service: Internet or ISO Protocol Stack (RS1 forward, RS1 reverse) High Speed Packet Data Service: Internet or ISO Protocol Stack (RS1 forward, RS2 reverse) Type of Service CS CS CS CS CS CS PS CS CS CS CS CS CS CS CS PS CS CS CS CS CS PS
Description
0017H
PS
2006 3GPP2
Page 141
3GPP2 S.S0093-0 v2.0
Service Option Value (hex) 0018H
Description High Speed Packet Data Service: Internet or ISO Protocol Stack (RS2 forward, RS1 reverse) High Speed Packet Data Service: Internet or ISO Protocol Stack (RS2 forward, RS2 reverse) (3G High Speed Packet Data) (ISDN Interworking Service (64 kbps)) 32 kbps Circuit Switched Video Conferencing 64 kbps Circuit Switched Video Conferencing Link-Layer Assisted Header Removal Link-Layer Assisted Robust Header Compression Wideband Speech Codec Packet Data Service: Internet or ISO Protocol Stack, Revision 1 (9.6 or 14.4 kbps) ---------
Type of Service PS
0019H 0021H 0025H 0039H 003AH 003CH 003DH 003EH 1007H 1
PS PS CS CS CS PS PS CS PS
2006 3GPP2
Page 142

3GPP2 Evdo

Uploaded by

Document Information

Original Description:

Original Title

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

3GPP2 Evdo

Uploaded by

Copyright:

Available Formats

3GPP2 S.S0093-0 v2.

3GPP2 S.S0093-0 Version 2.0 Version Date: January 18, 2006

cdma2000 Network Performance Measurement Types

3GPP2 S.S0093-0 v2.0

Version 1.0 Version 2.0

Initial Publication Point Release Publication

Dec 11, 2003 18 Jan 2006

3GPP2 S.S0093-0 v2.0

7.2.1 BTS system resource measurements ........................................... 25

Measurements related to BSC ....................................................27

7.3.1 BSC handoff measurements........................................................ 27

7.3.2 BSC traffic measurements related to the PS domain.................... 28

3GPP2 S.S0093-0 v2.0

7.3.3 BSC system resource measurements .......................................... 35

Measurements related to Sector .................................................36

7.4.1 Sector traffic measurements related to the CS domain ................ 36

7.4.2 Sector traffic measurements related to the PS domain................. 39

Measurements related to PCF ....................................................42

7.5.1 PCF traffic measurements........................................................... 42

8.1.1 Interfaces Group Measurements ................................................. 46

3GPP2 S.S0093-0 v2.0

8.1.2 IP Group Measurements ............................................................. 50

Measurements related to the PDSN ............................................57

8.2.1 MIP Measurements ..................................................................... 57

8.2.1.10 8.2.1.11 8.2.1.12 8.2.1.13 8.2.1.14 8.2.1.15 8.2.1.16

8.2.2 PPP Measurements ..................................................................... 63

3GPP2 S.S0093-0 v2.0

8.2.3 GRE Measurements .................................................................... 68

8.2.4 R-P Measurements...................................................................... 71

Measurements related to the HA ................................................79

8.3.1 MIP Measurements ..................................................................... 79

3GPP2 S.S0093-0 v2.0

Measurements related to the AAA ..............................................87

8.4.1 RADIUS Accounting Port Measurements ..................................... 87

8.4.2 RADIUS Authentication Port Measurements................................ 91

9.1.1 MSC Basic Measurement ............................................................ 95

3GPP2 S.S0093-0 v2.0

9.1.2 Traffic Measurements ................................................................. 96

3GPP2 S.S0093-0 v2.0

9.1.3 Handoff Measurements ............................................................. 116

9.1.4 QoS Measurements................................................................... 118

9.1.5 SMS Measurements .................................................................. 120

Circuit End Point Subgroup Measurements .............................121

9.2.1 Outgoing call measurements..................................................... 122

9.2.2 Incoming Call Measurements .................................................... 123

3GPP2 S.S0093-0 v2.0

MM4 ...................................................................................... 135

Annex A: 3GPP2 Service Options ................................................................. 141

3GPP2 S.S0093-0 v2.0

3GPP2 S.S0093-0 v2.0

[02] 3GPP2 S.S0028-003-B [03] 3GPP2 S.S0028-004-B [05] 3GPP TS 32.403

"OAM&P for cdma2000 (3GPP2 Core NRM IRP)"

[06] 3GPP2 S.R0005-B

[07] 3GPP2 S.S0028-A

"OAM&P for cdma2000 (3GPP R4 Delta Specification)"

[08] 3GPP2 S.R0037

[09] 3GPP TS 23.107

"Quality of Service (QoS) Concept and Architecture"; (Release 5) (Release 6)

[10] 3GPP2 A.S0017

[11] RFC 2006 [12] RFC 2011

3GPP2 S.S0093-0 v2.0

[22] 3GPP2 X.S0004-000-E [23] 3GPP2 A.S0014-A