7/28/2019 3GPP2 EVDO
1/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2
3GPP2 S.S0093-0
Version 2.0
Version Date: January 18, 2006
cdma2000 Network PerformanceMeasurement 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
[email protected]. Requests to reproduce individual Organizational Partners
documents should be directed to that Organizational Partner. See www.3gpp2.org for more
information.
7/28/2019 3GPP2 EVDO
2/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2
EDITOR(s)
Said Soulhi, [email protected]
Randall J. Scheer, [email protected]
Yao Yizhi,[email protected]
REVISION HISTORY
Version 1.0 Initial Publication Dec 11, 2003
Version 2.0 Point Release Publication 18 Jan 2006
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]7/28/2019 3GPP2 EVDO
3/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page ii
Table of Contents
1 Scope............................................................................................ 10
2 References .................................................................................... 11
3 Abbreviations................................................................................ 14
4 General......................................................................................... 18
5 Definitions.................................................................................... 19
6 Measurement definition template.................................................. 21
7 Measurements related to the Radio Access Network ...................... 25
7.1 Common Measurements ............................................................25
7.2 Measurements related to BTS ....................................................25
7.2.1 BTS system resource measurements........................................... 25
7.2.1.1 Number of available CE................................................................................................................257.2.1.2 Duration of seizures of CE............................................................................................................25
7.2.1.3 Number of call failures due to resource assignment failures .........................................................26
7.3 Measurements related to BSC....................................................27
7.3.1 BSC handoff measurements........................................................ 27
7.3.1.1 Number of incoming hard handoffs ..............................................................................................27
7.3.1.2 Number of successful incoming hard handoffs..............................................................................27
7.3.1.3 Number of soft handoff leg addition attempts ...............................................................................27
7.3.1.4 Number of successful soft handoff leg additions ........................................................................... 28
7.3.2 BSC traffic measurements related to the PS domain.................... 287.3.2.1 Number of attempted PS calls ......................................................................................................28
7.3.2.2 Number of call-drops for PS domain service.................................................................................. 29
7.3.2.3 Number of requests for forward SCH............................................................................................ 29
7.3.2.4 Number of successful assignments for forward SCH .....................................................................29
7.3.2.5 Number of requests for reverse SCH.............................................................................................30
7.3.2.6 Number of successful assignments for reverse SCH......................................................................30
7.3.2.7 Traffic volume carried by Walsh Codes on SCHs for PS domain service .........................................30
7.3.2.8 Traffic volume carried by Walsh Codes on FCHs for PS domain service .........................................31
7.3.2.9 Traffic volume carried on CEs which are seized by SCHs for PS domain service.............................32
7.3.2.10 Number of forward RLP packets ...............................................................................................32
7.3.2.11 Number of repeated forward RLP packets .................................................................................32
7.3.2.12 Number of reverse RLP packets ................................................................................................ 33
7.3.2.13 Number of repeated reverse RLP packets .................................................................................. 33
7.3.2.14 Number of failed requests for PS domain service....................................................... ................33
7.3.2.15 Number of attempted PS handoffs ............................................................................................ 34
7.3.2.16 Number of successful PS handoffs............................................................................................ 35
7/28/2019 3GPP2 EVDO
4/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page iii
7.3.3 BSC system resource measurements .......................................... 35
7.3.3.1 Number of available trunk circuits ...............................................................................................35
7.3.3.2 Duration of seizures of A-Interface circuits.......................... .........................................................36
7.4 Measurements related to Sector .................................................36
7.4.1 Sector traffic measurements related to the CS domain ................ 36
7.4.1.1 Number of attempted originating calls related to the CS domain ...................................................367.4.1.2 Number of attempted call assignments to the CS domain .............................................................37
7.4.1.3 Number of paging responses related to the CS domain .................................................................37
7.4.1.4 Number of dropped calls related to the CS domain .......................................................................37
7.4.1.5 Traffic volume including handoffs................................................................................................. 38
7.4.1.6 Traffic volume of Walsh Codes......................................................................................................38
7.4.2 Sector traffic measurements related to the PS domain................. 39
7.4.2.1 Number of attempted originating calls related to the PS domain ...................................................39
7.4.2.2 Number of attempted call assignments to the PS domain..............................................................39
7.4.2.3 Number of successful call assignments to the PS domain .............................................................40
7.4.2.4 Number of paging responses related to the PS domain..................................................................40
7.4.2.5 Number of dropped calls related to the PS domain........................................................................ 40
7.5 Measurements related to PCF ....................................................42
7.5.1 PCF traffic measurements........................................................... 42
7.5.1.1 Number of successful access........................................................................................................ 42
7.5.1.2 Number of unsuccessful access.................................................................................................... 42
7.5.1.3 Forward GRE bits ........................................................................................................................42
7.5.1.4 Reverse GRE bits .........................................................................................................................43
7.5.1.5 Number of RAN discarded reverse GRE packets............................................................................ 43
7.5.1.6 Number of PDSN discarded forward GRE packets .........................................................................447.5.1.7 Number of attempted PS transitions from dormant to active .........................................................44
7.5.1.8 Number of successful PS transitions from dormant to active......................................................... 44
8 Measurements related to the Packet Core Network........................ 46
8.1 Common Measurements ............................................................46
8.1.1 Interfaces Group Measurements ................................................. 46
8.1.1.1 Number of octets received ............................................................................................................46
8.1.1.2 Number of unicast packets accepted ............................................................................................ 46
8.1.1.3 Number of non-unicast packets accepted .....................................................................................47
8.1.1.4 Number of inbound packets discarded..........................................................................................478.1.1.5 Number of malformed packets received ........................................................................................47
8.1.1.6 Number of packets discarded due to unknown protocol ................................................................ 48
8.1.1.7 Number of octets sent ..................................................................................................................48
8.1.1.8 Number of unicast packets sent ...................................................................................................49
8.1.1.9 Number of non-unicast packets sent ............................................................................................49
8.1.1.10 Number of outbound packets discarded.................................................................................... 50
8.1.1.11 Number of outbound erred packets .......................................................................................... 50
7/28/2019 3GPP2 EVDO
5/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page iv
8.1.2 IP Group Measurements ............................................................. 50
8.1.2.1 Number of input packets received ................................................................................................50
8.1.2.2 Number of input datagrams discarded due to errors in their IP headers........................................ 51
8.1.2.3 Number of input datagrams discarded due to invalid address .......................................................51
8.1.2.4 Number of forwarded input datagrams.........................................................................................52
8.1.2.5 Number of input datagrams discarded due to unknown protocol...................................................52
8.1.2.6 Number of input datagrams discarded without appropriate reasons.............................................. 52
8.1.2.7 Number of input datagrams delivered to IP user protocol........ ......................................................53
8.1.2.8 Number of output datagrams requested ....................................................................................... 53
8.1.2.9 Number of datagrams discarded due to no route .......................................................................... 54
8.1.2.10 Number of output datagrams discarded for other reasons .........................................................54
8.1.2.11 Number of datagrams fragmented ............................................................................................ 54
8.1.2.12 Number of datagrams for which fragmentation failed................................................................ 55
8.1.2.13 Number of fragments created ................................................................................................... 55
8.1.2.14 Number of IP fragments received........... ...................................................................................55
8.1.2.15 Number of IP datagrams reassembled....................................................................................... 568.1.2.16 Number of reassembly failures .................................................................................................56
8.2 Measurements related to the PDSN............................................57
8.2.1 MIP Measurements ..................................................................... 57
8.2.1.1 Number of successful MIP registrations in PDSN..........................................................................57
8.2.1.2 Number of attempted MIP registrations in PDSN...........................................................................57
8.2.1.3 Number of registrations relayed from PDSN to HA ........................................................................57
8.2.1.4 Number of rejected registrations by the PDSN due to unspecified reason ......................................58
8.2.1.5 Number of rejected registrations by the PDSN due to administrative reason.............................. ....58
8.2.1.6 Number of rejected registrations by the PDSN due to insufficient resource reason.........................59
8.2.1.7 Number of rejected registrations by the PDSN due to MN authentication failure reason.................59
8.2.1.8 Number of rejected registrations by the PDSN due to HA authentication failure reason.................60
8.2.1.9 Number of rejected registrations by the PDSN due to too long registration lifetime reason............. 60
8.2.1.10 Number of rejected registrations by the PDSN due to poorly formed requests reason................. 60
8.2.1.11 Number of rejected registrations replies by the PDSN due to poorly formed reply reason ...........61
8.2.1.12 Number of rejected registrations by the PDSN due to unavailable encapsulation requested reason61
8.2.1.13 Number of rejected registrations by the PDSN due to VJ compression reason............................ 62
8.2.1.14 Number of rejected registrations by the PDSN due to unreachable HA ......................................62
8.2.1.15 Number of registrations replies received by the PDSN ...............................................................63
8.2.1.16 Number of valid registrations replies relayed to the MN by the PDSN ........................................63
8.2.2 PPP Measurements ..................................................................... 63
8.2.2.1 Total number of PPP packets sent to MNs..................................................................................... 63
8.2.2.2 Total number of errored PPP packets ............................................................................................64
8.2.2.3 Total number of discarded PPP packets ........................................................................................64
8.2.2.4 Total active/dormant connection time .......................................................................................... 65
8.2.2.5 Total number of PPP packets received from all MNs ......................................................................65
7/28/2019 3GPP2 EVDO
6/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page v
8.2.2.6 Total number of dropped PPP sessions .........................................................................................65
8.2.2.7 Total number of active PPP sessions............................................................................................. 66
8.2.2.8 Total number of dormant PPP sessions......................................................................................... 66
8.2.2.9 Total number of PPP setup requests .............................................................................................67
8.2.2.10 Total number of PPP successful connections............................................................................. 67
8.2.2.11 Total number of PPP setup failures........................................................................................... 67
8.2.3 GRE Measurements .................................................................... 68
8.2.3.1 Total number of GRE packets transmitted by the PDSN................................................................68
8.2.3.2 Total number of GRE packets received by the PDSN ..................................................................... 68
8.2.3.3 Total number of bytes transmitted by the PDSN ........................................................................... 69
8.2.3.4 Total number of bytes received by the PDSN.................................................................................69
8.2.3.5 Total number of errored GRE packets...........................................................................................69
8.2.3.6 Total number of discarded GRE packets ....................................................................................... 70
8.2.3.7 Total number of GRE packets out of sequence.............................................................................. 70
8.2.3.8 Total number of GRE packets with no existing MIP binding ..........................................................71
8.2.4 R-P Measurements...................................................................... 718.2.4.1 Total number of R-P registration requests .................................................................................... 71
8.2.4.2 Total number of R-P registration requests accepted ......................................................................71
8.2.4.3 Total number of R-P registration requests denied .........................................................................72
8.2.4.4 Total number of R-P deregistration requests received....................................................................73
8.2.4.5 Total number of successful R-P deregistration replies ...................................................................73
8.2.4.6 Total number of R-P release connection requests..........................................................................73
8.2.4.7 Total number of successful R-P release connection replies............................................................ 74
8.2.4.8 Total number of current sessions .................................................................................................74
8.2.4.9 Total number of active R-P sessions .............................................................................................75
8.2.4.10 Total number of dormant R-P sessions .....................................................................................75
8.2.4.11 Total number of handoff sessions.............................................................................................75
8.2.4.12 Total number of successful intra-PDSN handoffs ......................................................................76
8.2.4.13 Total number of unsuccessful inter-PDSN handoffs ..................................................................76
8.2.4.14 Total number of unsuccessful intra-PDSN handoffs ..................................................................76
8.2.4.15 Total number of unsuccessful inter-PDSN handoffs ..................................................................77
8.2.4.16 Total number of simple IP sessions...........................................................................................77
8.2.4.17 Total number of MIP sessions................................................................................................... 78
8.2.4.18 Packet session set up time (Mean) ............................................................................................78
8.2.4.19 Packet session set up time (Maximum) ..................................................................................... 798.3 Measurements related to the HA ................................................79
8.3.1 MIP Measurements ..................................................................... 79
8.3.1.1 Number of service requests accepted by HA..................................................................................79
8.3.1.2 Number of service requests denied by HA..................................................................................... 80
8.3.1.3 Number of registration requests accepted by HA...........................................................................80
8.3.1.4 Number of registration requests accepted by HA, but not supported by the MN binding ................80
8.3.1.5 Number of registration requests rejected by the HA due to unknown reasons................................81
7/28/2019 3GPP2 EVDO
7/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page vi
8.3.1.6 Number of registration requests rejected by the HA due to administrative reasons........................81
8.3.1.7 Number of registration requests rejected by the HA due to insufficient resources.......................... 82
8.3.1.8 Number of registration requests rejected by the HA due to authentication failure..........................82
8.3.1.9 Number of registration requests rejected by the HA due to FA authentication failure.....................82
8.3.1.10 Number of registration requests rejected by the HA due to identification mismatch................... 83
8.3.1.11 Number of registration requests rejected by the HA due to poorly formed request .....................83
8.3.1.12 Number of registration requests rejected by the HA due to too many simultaneous mobilitybindings 84
8.3.1.13 Number of registration requests rejected by the HA due to unknown home agent addresses......84
8.3.1.14 Number of ARP sent by HA on behalf of the MN........................................................................85
8.3.1.15 Number of proxy ARP responses sent by HA on behalf of the MN ..............................................85
8.3.1.16 Number of registration replies received by HA...........................................................................85
8.3.1.17 Number of deregistration requests............................................................................................86
8.3.1.18 Number of registration replies sent by HA.................................................................................86
8.3.1.19 Number of registration replies sent by the HA in response to requests to deregister ..................87
8.4 Measurements related to the AAA ..............................................87
8.4.1 RADIUS Accounting Port Measurements ..................................... 87
8.4.1.1 Number of packets received on the accounting port ......................................................................87
8.4.1.2 Number of packets received with unknown addresses...................................................................87
8.4.1.3 Total packets of duplicated billing request received....................................................................... 88
8.4.1.4 Total packets of billing responses sent.......................................................................................... 88
8.4.1.5 Total of malformed packets received............................................................................ .................89
8.4.1.6 Total packets of billing requests with illegal signature attributes................................................... 89
8.4.1.7 Total of packets dropped ..............................................................................................................89
8.4.1.8 Total of packets received and not recorded ...................................................................................90
8.4.1.9 Total of packets received with unknown type................................................................................ 908.4.2 RADIUS Authentication Port Measurements................................ 91
8.4.2.1 Number of packets received on the authentication port ................................................................91
8.4.2.2 Number of packets received with unknown address..................................................... .................91
8.4.2.3 Total packets of duplicated access request received ......................................................................91
8.4.2.4 Total packets of access accepted response sent ............................................................................ 92
8.4.2.5 Total packets of Access-Reject packets sent............... ...................................................................92
8.4.2.6 Total packets of Access-Challenge packets sent ............................................................................ 92
8.4.2.7 Total packets of malformed packets sent ......................................................................................93
8.4.2.8 Total packets of authentication requests with illegal signature attributes...................................... 93
8.4.2.9 Total packets of dropped ..............................................................................................................94
8.4.2.10 Total packets received with unknown type................................................................................ 94
9 Measurements related to the Circuit Core Network........................ 95
9.1 Measurements related to the MSC .............................................95
9.1.1 MSC Basic Measurement ............................................................ 95
9.1.1.1 Number of page requests..............................................................................................................95
9.1.1.2 Number of successful page requests.............................................................................................95
7/28/2019 3GPP2 EVDO
8/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page vii
9.1.1.3 Number of location registration requests ......................................................................................95
9.1.1.4 Number of successful location registrations.................................................................................. 96
9.1.2 Traffic Measurements ................................................................. 96
9.1.2.1 Number of attempted originating calls ..........................................................................................96
9.1.2.2 Number of successful originating calls..........................................................................................97
9.1.2.3 Number of answered originating calls ...........................................................................................97
9.1.2.4 Number of failed originating calls for various reasons ................................................................... 97
9.1.2.5 Number of MSC internal call attempts.......................................................................................... 98
9.1.2.6 Number of successful MSC internal calls......................................................................................98
9.1.2.7 Number of MSC answered internal calls .......................................................................................99
9.1.2.8 Number of failed internal calls......................................................................................................99
9.1.2.9 Number of terminating call attempts.......................................................................................... 100
9.1.2.10 Number of Successful Mobile Terminating Calls ..................................................................... 100
9.1.2.11 Number of Answered Terminating calls................................................................................... 101
9.1.2.12 Number of failed terminating calls for various reasons............................................................ 101
9.1.2.13 Number of incoming call attempts .......................................................................................... 1029.1.2.14 Number of successful Incoming Calls ..................................................................................... 102
9.1.2.15 Number of answered incoming calls........................................................................................102
9.1.2.16 Number of failed incoming calls for various reasons................................................................ 103
9.1.2.17 Number of outgoing call attempts ........................................................................................... 103
9.1.2.18 Number of successful outgoing Calls ...................................................................................... 104
9.1.2.19 Number of outgoing call answers............................................................................................ 104
9.1.2.20 Number of failed outgoing calls for various reasons................................................................. 104
9.1.2.21 Number of transit call attempts.............................................................................................. 105
9.1.2.22 Number of successful transit Calls ......................................................................................... 105
9.1.2.23 Number of transit call answers............................................................................................... 106
9.1.2.24 Number of failed transit calls for various reasons ................................................................... 106
9.1.2.25 Number of originating outgoing call attempts.......................................................................... 107
9.1.2.26 Number of successful originating outgoing calls...................................................................... 107
9.1.2.27 Number of originating outgoing call answers...........................................................................108
9.1.2.28 Number of failed originating outgoing calls for various reasons ............................................... 108
9.1.2.29 Number of incoming terminating call attempts ....................................................................... 109
9.1.2.30 Number of Successful Incoming Terminating Calls ................................................................. 109
9.1.2.31 Number of incoming terminating call answer................ .......................................................... 109
9.1.2.32 Number of failed incoming terminating calls for various reasons............................................. 110
9.1.2.33 Successful Traffic Volume for Mobile Originating Calls............................................................ 110
9.1.2.34 Successful traffic volume for MSC calls .................................................................................. 111
9.1.2.35 Successful Traffic Volume For Mobile Terminating Calls ......................................................... 112
9.1.2.36 Successful traffic volume for incoming calls............................................................. ............... 112
9.1.2.37 Successful traffic volume for outgoing calls.............................................................................113
9.1.2.38 Successful traffic volume for transit calls................................................................................113
9.1.2.39 Traffic volume for successful originating outgoing calls ........................................................... 114
7/28/2019 3GPP2 EVDO
9/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page viii
9.1.2.40 Traffic Volume For Successful Incoming Terminating Calls ..................................................... 114
9.1.2.41 Occupation traffic volume of out-trunk calls ........................................................................... 115
9.1.2.42 Occupation traffic volume of incoming trunk calls .................................................................. 115
9.1.3 Handoff Measurements............................................................. 116
9.1.3.1 Number of outgoing handoff requests ......................................................................................... 116
9.1.3.2 Number of successful outgoing handoff requests ........................................................................ 116
9.1.3.3 Number of incoming handoff requests ........................................................................................ 117
9.1.3.4 Number of successful incoming handoff requests ....................................................................... 117
9.1.4 QoS Measurements................................................................... 118
9.1.4.1 Mean time to set up call service ................................................................................................. 118
9.1.4.2 Mean call duration..................................................................................................................... 118
9.1.4.3 Mean Trunk Seizure Duration.................................................... ................................................119
9.1.5 SMS Measurements .................................................................. 120
9.1.5.1 Number of originating Point-to-point SMS attempts................................................................ ....120
9.1.5.2 Number of successful originating Point-to-point SMS..................................................................120
9.1.5.3 Number of terminating Point-to-point SMS attempts...................................................................121
9.1.5.4 Number of successful terminating Point-to-point SMS attempts.................................................. 121
9.2 Circuit End Point Subgroup Measurements .............................121
9.2.1 Outgoing call measurements..................................................... 122
9.2.1.1 Number of outgoing call attempts............................................................................................... 122
9.2.1.2 Number of outgoing call occupations.......................................................................................... 122
9.2.1.3 Number of answers to outgoing calls .......................................................................................... 122
9.2.1.4 Total number of available out-trunks ......................................................................................... 123
9.2.2 Incoming Call Measurements.................................................... 123
9.2.2.1 Number of incoming trunk call occupations................................................................................ 123
9.2.2.2 Total number of blocked out-trunks........................................................................................... 124
9.2.2.3 Number of answers to incoming trunk calls................................................................................ 124
9.2.2.4 Total number of available incoming trunks..................... ............................................................ 125
9.2.2.5 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 Background Information on the Request Status [21]............... 128
10.1.2 MM1 ...................................................................................... 129
10.1.2.1 Number of Multimedia Messages submit requests received by MMS Relay/Server...................129
10.1.2.2 Number of Multimedia Messages submit responses sent by MMS Relay/Server....................... 130
10.1.2.3 Number of Multimedia Messages notification requests sent by MMS Relay/Server ..................130
10.1.2.4 Number of Multimedia Messages notification responses received by MMS Relay/Server ..........131
10.1.2.5 Number of Multimedia Messages retrieve requests received by MMS Relay/Server ..................131
10.1.2.6 Number of Multimedia Messages retrieve responses sent by MMS Relay/Server......................132
10.1.2.7 Number of Multimedia Messages acknowledgement requests received by MMS Relay/Server...132
7/28/2019 3GPP2 EVDO
10/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page ix
10.1.2.8 Number of Multimedia Messages forward requests received by MMS Relay/Server ..................133
10.1.2.9 Number of Multimedia Messages forward responses sent by MMS Relay/Server...................... 133
10.1.2.10 Number of Multimedia Messages delivery report requests sent by MMS Relay/Server.............. 133
10.1.2.11 Number of Multimedia Messages read reply recipient requests received by MMS Relay/Server 134
10.1.2.12 Number of Multimedia Messages read reply originator requests sent by MMS Relay/Server..... 134
10.1.3 MM4 ...................................................................................... 135
10.1.3.1 Number of Multimedia Messages forward requests received by MMS Relay/Server ..................135
10.1.3.2 Number of Multimedia Messages forward requests sent by MMS Relay/Server........................135
10.1.3.3 Number of Multimedia Messages forward responses received by MMS Relay/Server................ 136
10.1.3.4 Number of Multimedia Messages forward responses sent by MMS Relay/Server...................... 136
10.1.3.5 Number of Multimedia Messages delivery report requests received by MMS Relay/Server........ 137
10.1.3.6 Number of Multimedia Messages delivery report requests sent by MMS Relay/Server.............. 137
10.1.3.7 Number of Multimedia Messages delivery report responses received by MMS Relay/Server ..... 137
10.1.3.8 Number of Multimedia Messages delivery report responses sent by MMS Relay/Server ...........138
10.1.3.9 Number of Multimedia Messages read reply requests received by MMS Relay/Server ..............138
10.1.3.10 Number of Multimedia Messages read reply requests sent by MMS Relay/Server ....................13910.1.3.11 Number of Multimedia Messages read reply responses received by MMS Relay/Server ............139
10.1.3.12 Number of Multimedia Messages read reply responses sent by MMS Relay/Server ..................140
Annex A: 3GPP2 Service Options................................................................. 141
7/28/2019 3GPP2 EVDO
11/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 10
1 Scope1
This document defines the Performance Measurement Types applicable to CDMA2
and cdma20001 systems.3
4
This document contains portions of material copied from 3GPP document number5TS 32.403. The copyright on the 3GPP document is owned by the Organizational6
Partners of 3GPP (ARIB - Association of Radio Industries and Businesses, Japan;7
CCSA China Communications Standards Association, China; ETSI European8
Telecommunications Standards Institute; Committee T1, USA; TTA -9
Telecommunications Technology Association, Korea; and TTC Telecommunication10
Technology Committee, Japan), which have granted license for reproduction and for11
use by 3GPP2 and its Organizational Partners.1213
1 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
7/28/2019 3GPP2 EVDO
12/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 11
2 References1
[01] 3GPP2 S.S0028-001-B "OAM&P for cdma2000 (3GPP R5 Delta2
Specification)"3http://www.3gpp2.org/Public_html/specs/index.cfm4
[02] 3GPP2 S.S0028-003-B "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"5http://www.3gpp2.org/Public_html/specs/index.cfm6
[03] 3GPP2 S.S0028-004-B "OAM&P for cdma2000 (3GPP2 Radio Access7
NRM IRP)" http://www.3gpp2.org/Public_html/specs/index.cfm8
[05] 3GPP TS 32.403 "Performance Management (PM); Performance9
Measurements UMTS and Combined10
UMTS/GSM"; (Release 5) (Release 6)11http://www.3gpp.org/ftp/specs/latest12
[06] 3GPP2 S.R0005-B "Network Reference Model for cdma2000 Spread13
Spectrum Systems; Revision: B"; Version 1.014http://www.3gpp2.org/Public_html/specs/index.cfm15
[07] 3GPP2 S.S0028-A "OAM&P for cdma2000 (3GPP R4 Delta16
Specification)"17http://www.3gpp2.org/Public_html/specs/index.cfm18
[08] 3GPP2 S.R0037 "IP Network Architecture Model for cdma200019
Spread Spectrum Systems"; Version 3.020http://www.3gpp2.org/Public_html/specs/index.cfm21
[09] 3GPP TS 23.107 "Quality of Service (QoS) Concept and22
Architecture"; (Release 5) (Release 6)23http://www.3gpp.org/ftp/specs/latest24
[10] 3GPP2 A.S0017 "Interoperability Specification (IOS) for25
cdma2000 Access Network Interfaces Part 726(A10 and A11 Interfaces) "(Revision A) (Revision27
B) (Revision C)28http://www.3gpp2.org/Public_html/specs/index.cfm29
[11] RFC 2006 "The Definitions of Managed Objects for IP30
Mobility Support using SMI"; Version 231
[12] RFC 2011 "SNMPv2 Management Information Base for the32
Internet Protocol using SMI"; Version 2[13] RFC33
2012 "SNMPv2 Management Information34
Base for the Transmission Control Protocol35
using SMI"; Version 236
[14] RFC 2013 "SNMPv2 Management Information Base for the37
User Datagram Protocol using SMI"; Version 238
[15] RFC 2618 "RADIUS Authentication Client MIB"39
[16] RFC 2619 "RADIUS Authentication Server MIB"40
[17] RFC 2621 "RADIUS Accounting Server MIB"41
http://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp.org/ftp/specs/latesthttp://www.3gpp.org/ftp/specs/latesthttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp.org/ftp/specs/latesthttp://www.3gpp.org/ftp/specs/latesthttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp.org/ftp/specs/latestftp://ftp.3gpp.org//Specs/2001-09/R1999/32_series/32104-340.ziphttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp.org/ftp/specs/latestftp://ftp.3gpp.org//Specs/2001-09/R1999/32_series/32104-340.ziphttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfm7/28/2019 3GPP2 EVDO
13/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 12
[18] RFC 2863 "The Interfaces Group MIB"1
[19] RFC 1213 "Management Information Base for Network2
Management of TCP/IP-based Internets: MIB-II"3
[20] 3GPP2 S.R0064-A v1.0 "Multimedia Messaging Services (MMS) Stage 14
Requirements"; Version 1.05http://www.3gpp2.org/Public_html/specs/index.cfm
6[21] 3GPP2 X.S0016-200-0 v2.0 "MMS Stage 2 Functional Description";7
Version 2.08http://www.3gpp2.org/Public_html/specs/index.cfm9
[22] 3GPP2 X.S0004-000-E "Introduction to TIA-41"; Version 2.010http://www.3gpp2.org/Public_html/specs/index.cfm11
[23] 3GPP2 A.S0014-A "Interoperability Specification (IOS) for12
cdma2000 Access Network Interfaces Part 413
(A1, A2 and A5 Interfaces) (IOSv4.3)"14http://www.3gpp2.org/Public_html/specs/index.cfm15
[25] 3GPP2 C.S0005-A "cdma2000 Layer 3 Signaling Revision A"16 http://www.3gpp2.org/Public_html/specs/index.cfm17
[26] 3GPP2 C.S0017-012-A "Data Service Options for Spread Spectrum18
Systems: Service Options 33 and 66"19http://www.3gpp2.org/Public_html/specs/index.cfm20
[27] 3GPP2 C.S0017-010-A "Data Service Options for Spread Spectrum21
Systems: Radio Link Protocol Type 3"; Version22
2.0 http://www.3gpp2.org/Public_html/specs/index.cfm23
[28] 3GPP2 A.S0015 "Interoperability Specification (IOS) for24
cdma2000 Access Network Interfaces Part 525
(A3 and A7 Interfaces)"; (Revision A) (Revision B)26 (Revision C) http://www.3gpp2.org/Public_html/specs/index.cfm27
[29] 3GPP2 A.S0016 "Interoperability Specification (IOS) for28
cdma2000 Access Network Interfaces Part 629
(A8 and A9 Interfaces)"; (Revision A) (Revision B)30
(Revision C) http://www.3gpp2.org/Public_html/specs/index.cfm31
[30] ITU-T Recommendation M.3100 "Generic Network Information Model";32
199533
[31] 3GPP2 A.S0007-A v2.0 "Interoperability Specification (IOS) for High Rate34
Packet Data (HRPD) Access Network Interfaces 35
Revision A"; Version 2.036http://www.3gpp2.org/Public_html/specs/index.cfm37
[32] 3GPP2 A.S0008-0 v3.0 "Interoperability Specification (IOS) for High Rate38
Packet Data (HRPD) Access Network Interfaces39
Revision 0"; Version 3.040http://www.3gpp2.org/Public_html/specs/index.cfm41
[33] ITU-T Recommendation Q.764 Signalling System No. 7 ISDN User Part42
Signalling Procedures, 199943
http://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfm7/28/2019 3GPP2 EVDO
14/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 13
[34] ITU-T Recommendation Q.723 Specifications of Signalling System No. 7 1
Telephone User Part, 19882
[35] ITU-T Recommendation Q.724 Specifications of Signalling System No. 7 3
Telephone User Part - Signalling Procedures,4
19885
[36] 3GPP2 X.S0004-540-E MAP Operations Signaling Protocols, Version 1.06 http://www.3gpp2.org/Public_html/specs/index.cfm7
[37] 3GPP2 A.S0013-C Interoperability Specification (IOS) for cdma20008
Access Network Interfaces Part 3 Features9
(3G-IOS v5.0), Version 1.010http://www.3gpp2.org/Public_html/specs/index.cfm11
[38] 3GPP2 C.R1001-E Administration of Parameter Value Assignments12
for cdma2000 Spread Spectrum Standards13http://www.3gpp2.org/Public_html/specs/index.cfm14
[39] 3GPP2 S.S0028-001-C "OAM&P for cdma2000 (3GPP R6 Delta15
Specification)"16http://www.3gpp2.org/Public_html/specs/index.cfm17
[40] 3GPP2 S.S0028-003-C "OAM&P for cdma2000 (3GPP2 Core NRM IRP)"18http://www.3gpp2.org/Public_html/specs/index.cfm19
[41] 3GPP2 S.S0028-004-C "OAM&P for cdma2000 (3GPP2 Radio Access20
NRM IRP)" http://www.3gpp2.org/Public_html/specs/index.cfm21
http://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfmhttp://www.3gpp2.org/Public_html/specs/index.cfm7/28/2019 3GPP2 EVDO
15/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 14
3 Abbreviations1
1X EVDO 1X Evolution Data Only
1X EVDV 1X Evolution Data and Voice
3G Third Generation
3GPP 3rd Generation Partnership Project
3GPP2 3rd
Generation Partnership Project 2AAA Authentication, Authorization and Accounting
AC Authentication Center
ACM Address complete message
ANC Answer signal, charge
Anchor MSC See [22]
ANM Answer Message
ANN Answer signal, no charge
ARIB Association of Radio Industries and Businesses (Japan)
ARP Address Resolution Protocol
ATM Asynchronous Transfer Mode
AuthReq Authorization RequestBGCF Breakout Gateway Control Function
BR Border Router
BS Base Station subsystem [see also [06])
BSC Base Station Controller
BSMAP BS Management Application Part
BTS Base Transceiver Station
CBK Clear-back signal
CC Cumulative Counter
CCSA China Communications Standards Association
CDMA Code Division Multiple Access
CE Channel Element
CGC CGC Circuit-group-congestion signal
CM Connection Management
CN Core Network
CS Circuit Switched
CSCF Call Session Control Function
CVSE Critical Vendor/Organization Specific Extension
DER Discrete Event Registration
DPC Destination Point Code
DRS Data Ready to Send
DTAP Direct Transfer Application PartESMTP Extended Simple Mail Transfer Protocol
ETSI European Telecommunications Standards Institute
FA Foreign Agent
FCH Fundamental Channel
FER Frame Erasure Rate
GQM Goal Question Metric
GRE Generic Routing Encapsulation
GSM Global System for Mobile Communication
7/28/2019 3GPP2 EVDO
16/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 15
HA Home Agent
HLR Home Location Register
HO Handoff
IAI Initial Address message with additional information
IAM Initial Address message
ICMP Internet Control Message Protocol
IETF Internet Engineering Task forceIMSI International Mobile Subscriber Identity
IOS Interoperability Specification
IP Internet Protocol
IPCP IP Control Protocol
IRATHO Inter-Radio Access Technology Handover
IS Interface Specification
ISUP ISDN User Part
ITU-T International Telecommunication Union - Telecommunications
Standardization Sector
LCP Link Control Protocol
MAP Mobile Application PartMb Mega Bit
MC Messaging Center
MGCF Media Gateway Control Function
MGW Media Gateway
MIB Management Information Base
MIME Multipurpose Internet Mail Extensions
MIP Mobile Internet Protocol
MM Mobility Management
MMS Multimedia Messaging Service
MN Mobile NodeMRFC Media Resource Function Controller
MRFP Media Resource Function Processor
MS Mobile Station
MSC Mobile Switching Centre
MSU Message Signal Units
MTP Message Transfer Part
MTP3 Message Transfer Part 3
NAM Network Architecture Model
OAM&P Operations, Accounting, Maintenance & Provisioning
OAS OSA Application Server
OP Organizational PartnerOPC Originating Point Code
OSCS OSA Service Capability Server
PCF Packet Control Function
PDE Position Determining Entity
PDF Policy Decision Function
PDSN Packet Data Serving Node
PM Performance Management
PPP Point-to-Point Protocol
7/28/2019 3GPP2 EVDO
17/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 16
PS Position Server
PS Packet Switch
PSID Private System Identifier
PSTN Public Switched Telephone Network
QoS Quality of Service
RADIUS Remote Authentication Dial In User Service
RAN Radio Access NetworkREG Registration
REL Release
RF Radio Frequency
RFC Request For Comment
RLP Radio Link Protocol
RP Radio-Packet interface (A-quater)
RRC Radio Resource Control
RRQ Registration Request
SAS Session Initiation Protocol Application Server
SCCP Signaling Connection Control Part
SCH Supplemental ChannelSEC Security
Serving MSC See [22]
SGW Signaling Gateway
SI Status Inspection
SIF Signaling Information Field
SIG Signaling
SIO Service Information Octet
SIP Session Initiation Protocol
SIP Simple IP
SLS Signaling Link SelectionSM Session Management
SMDPP Message SMSDeliveryPointToPoint INVOKE
smdpp Message SMSDeliveryPointToPoint RETURN RESULT
SMI Structure of Management Information
SMIL Synchronized Multimedia Integration Language
SMS Short Message Service
SMS-MO Short Message Service Mobile Originating
SMTP Simple Mail Transfer Protocol
SUB Subscriber
Target MSC See [22]
TCAP Transaction Capabilities Application PartTCE Traffic Channel Element
TCH Traffic Channel
TCP Transmission Control Protocol
TIA Telecommunications Industry Association (North America)
TP Termination Point
TRM Traffic Management
TS Technical Specification
TTA Telecommunications Technology Association (Korea)
7/28/2019 3GPP2 EVDO
18/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 17
TTC Telecommunications Technology Committee (Japan)
TUP Telephone User Part
UA User Agent
UE User Equipment
Um Air Interface [06]
UMTS Universal Mobile Telecommunications System
VAS Value-added ServicesVJ Van Jacobson header compression
VLR Visitor Location Register
WAP Wireless Application Protocol
1
7/28/2019 3GPP2 EVDO
19/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 18
4 General1
The present document describes the measurement types for CDMA and2
cdma2000 network.3
The measurement types identified in this document can be (a) defined by 3GPP24
and (b) defined by other standards bodies and re-used by 3GPP2.5Measurement types defined in this document may be supported by CDMA and6
cdma2000 systems pending applicability and system capacity limits.7
Nevertheless if such measurement types are provided then definitions within this8
specification shall apply.9
Note that 3GPP2 Performance Management concepts and requirements are10
defined within revisions of S.S0028 ([01], [07], [39]).1112
7/28/2019 3GPP2 EVDO
20/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 19
5 Definitions1
For the purposes of the document, the following terms and definitions apply:2
erlang3
The erlang is a unit of traffic density in a telecommunications system. One4
erlang is the equivalent of one call (including call attempts and holding time) in a5specific channel for 3600 seconds in an hour. The 3600 seconds need not be,6
and generally are not, in a contiguous block.7
Forward and Reverse Throughput8
Forward and reverse throughput is defined as the effective data rate excluding9
re-transmissions. In addition for the reverse link the throughput excludes data10
that is impossible to decode due to high FER or other poor RF conditions.11
Measurement User Community12
This document identifies several measurement user communities that are users13
of the measurement types. Each measurement type should be defined to14address the needs of at least one of these measurement user communities.15
This document identifies the following user communities.16
Network Operators Business Community17
Network Operators Maintenance Community18
Network Operators Traffic Engineering Community19
Network Operators Customer Care Community20
Equipment Vendors Performance Modeling Community21
Equipment Vendors Development Engineering Community22
The measurement user communities names are a composite of the various23
terms used in the industry and might be subject to modification or refinement in24
future releases. A comprehensive description of measurement communities as25
well as a top-down performance measurement definition process based on the26
Goal Question Metric (GQM) approach are provided in Annex B of 3GPP TS27
32.403 [05].28
Measurement family29
The names of the measurement types defined in the document begin with a30
prefix of the measurement family name. This prefix identifies all measurement31types that relate to a given functionality and its use may facilitate performance32
measurement administration.33
The list of prefix used in the document is:34
35
CE (measurements related to Channel Elements).36
GRE (measurements related to GRE)37
7/28/2019 3GPP2 EVDO
21/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 20
HHO (measurements related to Hard Handover).1
HO (measurements related to Handover)2
IMEI (measurements related to IMEI verification).3
IP (measurements related to Simple IP protocol)4
IRATHO (measurements related to Inter-Radio Access Technology5Handover)6
MIB (measurements from IETF)7
MIP (measurements related to Mobile IP protocol)8
MM (measurements related to Mobility Management)9
MMS (measurements related to Multimedia Messaging Services)10
PPP (measurements related to Point-to-Point Protocol)11
QoS (measurements related to Quality of Service)12
RAB (measurements related to Radio Access Bearer management).13
RAD (measurements related to RADIUS protocol)14
REG (measurements related to Registrations)15
RP (measurements related to R-P protocol)16
RRC (measurements related to Radio Resource Control)17
SEC (measurements related to Security)18
SHO (measurements related to Soft Handover).19
SIG (measurements related to Signaling)20 SIP (measurements related to Session Initiation Protocol)21
SM (measurements related to Session Management)22
SMS (measurements related to Short Messaging System)23
SUB (measurements related to Subscriber Management)24
TRM (measurements related to Traffic Management)25
Vendor-specific cdma2000 measurement names shall begin with the VS prefix.26
In addition, it is recommend that a measurement name prefix be added to the27
performance measurement name (as an example, VS.HO.Reject.NoResource or28VS.vendor.HO.Reject.NoResource).29
30
7/28/2019 3GPP2 EVDO
22/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 21
6 Measurement definition template1
The following is the template used to specify the measurement types.2
C.x.y. Measurement Name (clause header)3
This is a descriptive name of the measurement type.4
The measurement name shall use a string representing concatenated5
words without spaces. First letter for all words are capitalized. Letters of6
abbreviations are capitalized (e.g. PDSN). This naming rule is not7
applicable to measurement names from other standardization bodies (e.g.8
IETF).9
A measurement name can have one or more measurement types (e.g. the10
number of home subscribers (MM.NbrHomeSub) has 3 related11
measurement types: MM.NbrHomeSub (combined Simple IP and Mobile12
IP), MM.NbrHomeSub.IP for Simple IP subscribers and13
MM.NbrHomeSub.MIP for mobile IP subscribers.14
a) Description15
This contains an explanation of the measurement type.16
b) Collection Method17
This describes the different kinds of the measurement data captured in18
measurement types:19
CC (Cumulative Counter), are incremental counters triggered by the20occurrence of the measured event;21
GAUGE (dynamic variable), used when data being measured can vary22
up or down during the period of measurement;23
DER (Discrete Event Registration), when data related to a particular24event are captured every nth event is registered, where n can be 1 or25
larger;26
SI (Status Inspection), when a mechanism for high frequency sampling27of internal counters at pre-defined rates is used.28
There are two allowed methods for counting DER performance29
measurement data. It is vendor-specific which method is used for a30
specific performance measurement.31
32
1. Event Driven Collection Method: In this DER method, performance33
measurement data for a particular activity is put into the calculation34
when the event has completed. As an example, in the figure below,35
Activity #2 would only be used for the calculation of the performance36
measurement at the granularity period past the listed granularity37
period.38
7/28/2019 3GPP2 EVDO
23/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 22
Granularity PeriodTime
Start End
End
End
End
Start
Start
Start
Activity #1
Activity #2
Activity #3
Activity #4
counted counted
Counted in future
granularity period
1
Figure 1. DER Collection Method #1 Event Driven Collection2
2. Event and Granularity Period Driven Collection: In this DER method,3
performance measurement data for a particular activity is put into the4
calculation at each granularity period boundary (when the event has5
not yet completed), and when the event has completed. As an example,6in the figure below, Activity #2 would be put into the calculation in7
three separate granularity periods.8
Counted in future
granularity period
Granularity PeriodTime
counted
Start End
Activity #1
EndStart
Activity #2
counted
End
counted
Start
Activity #3
EndStart
Activity #4Counted in earlier
granularity period
9
Figure 2. DER Collection Method #2 Event and Granularity Period Driven10Collection11
For both DER collection methods, the measurement data for individual12
activities, used for part of the calculation, are cleared at the beginning of13
the granularity period.14
c) Condition15
This specifies the condition that causes the measurement data to be16
updated. This can be defined by identifying protocol related trigger events17
for updating the value of the measurement data. If it is not possible to18
7/28/2019 3GPP2 EVDO
24/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 23
give a precise condition, then the conditional circumstances leading to the1
(value of the measurement data) update are stated.2
d) Measurement Result (measured value(s), Units)3
This identifies the syntax of the measurement data, e.g. an integer.4
e) Measurement Type5
This specifies a short form of the measurement name. Measurement6
result files use these to identify the measurement type.7
The measurement type is a sequence of items separated by dots. The8
items, of the sequence, are arranged from general to specific in terms of9
information.10
The first item identifies the measurement family (e.g. HO, GRE, RP).11
The second item identifies the name of the measurement itself.12
Depending on the measurement type, additional items may be present13
to specify sub-counters (failure causes, traffic classes, min, max, avg).14 In case of multiple additional items, they are separated by dot. When15
these sub counters are present, they must be fully described or a16
reference to a standard must be made.17
Note that the values of a measurement type do not depend on the related18
collection method (CC, SI, GAUGE, DER). For instance, a gauge collected19
counter does not necessarily provide min, max, average values.20
f) Measurement Object Class21
This identifies the object class (e.g. Cell, PdsnFunction, HaFunction) where22
the subject measurement type is related to. The object class definition is in23
[02], [03], [07], [40] and [41].24
g) Switching Technology25
This identifies the Switching domain(s) that this measurement type is26
applicable to i.e. Circuit Switched and/or Packet Switched.27
h) Generation28
The generation determines if it concerns a cdma2000 1X, cdma2000 1X29
EV-DO, cdma2000 1X EV-DV measurement or all of them.30
cdma2000 1X: pure cdma2000 1X measurement; it only counts31
cdma2000 1X events.32 cdma2000 1X EV-DO: pure cdma2000 1X EV-DO measurement; it only33
counts cdma2000 1X EV-DO events.34
cdma2000 1X EV-DV: pure cdma2000 1X EVDV measurement (related35
to usage of the Forward Packet Data Channel (PDCH)); it only counts36
cdma2000 1X EV-DV events.37
7/28/2019 3GPP2 EVDO
25/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 24
ALL: measurement applicable to cdma2000 systems, but regardless of1
whether the measured event occurred on the cdma2000 1X, cdma20002
1X EV-DO or cdma2000 1X EV-DV.3
i) Purpose4
This optional identifies the user of the measurement. It contains one or5
more measurement user community names (see definition of Measurement6User Communities).7
8
7/28/2019 3GPP2 EVDO
26/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 25
7 Measurements related to the Radio Access Network1
7.1 Common Measurements2
To be defined in a new revision or version of this specification.3
7.2 Measurements related to BTS4
7.2.1 BTS system resource measurements5
7.2.1.1 Number of available CE6
A. This measurement provides the number of available CEs, which are not7
broken down, including the CEs seized by traffic channels and CEs8
seized by overhead channels.9
B. GAUGE10
C. This measurement will be increased on transition of a CE from11
unavailable (can not be assigned) into available (can be assigned),12decreased on transition of a CE from available (can be assigned) into13
unavailable (can not be assigned).14
D. An integer value15
E. CE.nbrAvailCe16
F. BtsFunction17
G. Valid for circuit switched and packet switched traffic.18
H. cdma2000 1X19
I. This measurement is mainly dedicated to Operator Traffic Engineering20and Operator Business communities.21
7.2.1.2 Duration of seizures of CE22
A. This measurement provides the duration of seizures of CEs, including23
the duration during which CEs are seized by traffic channels and the24
duration during which CEs are seized by overhead channels (in erlang).25
B. DER (n=1)26
C. This measurement is obtained by summing the duration of seizure(s) of27
all CEs in this BTS. The duration of seizure(s) for each CE is calculated28
by accumulating the seizure time intervals between the CE is29successfully assigned, and the CE is freed over a granularity period30
(noting that a CE is considered freed when released from traffic). The31
accumulator shall be re-initialized at the beginning of each granularity32
period.33
D. A value of type Real34
E. CE.durCeSeizure35
7/28/2019 3GPP2 EVDO
27/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 26
F. BtsFunction1
G. Valid for circuit switched and packet switched traffic.2
H. cdma2000 1X3
I. This measurement is mainly dedicated to Operator Traffic Engineering4
and Operator Business communities.5
7.2.1.3 Number of call failures due to resource assignment failures6
A. This measurement provides the number of call failures due to resource7
assignment failure. This parameter indicates the total number of8
unsuccessful assignments for mobile subscribers due to being short of9
Walsh Codes, being short of power, being short of TCH, being short of10
transmission circuits from BTS to BSC, and all kinds of other reasons,11
etc.12
B. CC13
C. The BS fails to assign the resources for mobile subscribers for voice14
service, SMS or handoffs due to the shortage of Walsh Codes, power,15
CEs, transcoders or transmission links from BTS to BSC, etc.16
D. An integer value17
E. RRC.failCallsByBlock18
F. BtsFunction19
G. Valid for circuit switched and packet switched traffic.20
H. All21
I. This measurement is mainly dedicated to Operator Traffic Engineering22
and Operator Business communities.23
7/28/2019 3GPP2 EVDO
28/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 27
7.3 Measurements related to BSC1
7.3.1 BSC handoff measurements2
Note: the measurements defined in this section are only related to voice service.3
7.3.1.1 Number of incoming hard handoffs4A. This measurement provides the attempted number of incoming hard5
handoffs (considering both inter and intra handoffs).6
B. CC7
C. The target BS allocates radio resources for the MS, which request hard8
handoff into the target BS [25].9
D. An integer value10
E. HO.attIncHardHo11
F. BscFunction12G. Valid for circuit switched traffic.13
H. cdma2000 1X, cdma2000 1XEV-DV14
I. This measurement is mainly dedicated to Operator Traffic Engineering15
and Operator Business communities.16
7.3.1.2 Number of successful incoming hard handoffs17
A. This measurement provides the number of successful incoming hard18
handoffs (considering both inter and intra handoffs).19
B. CC20C. Receipt by the target BS from MS of an Um message Handoff21
Completion or Extended Handoff Completion, indicating the22
successful incoming hard handoff [25].23
D. An integer value24
E. HO.succIncHardHo25
F. BscFunction26
G. Valid for circuit switched traffic.27
H. cdma2000 1X, cdma2000 1XEV-DV28
I. This measurement is mainly dedicated to Operator Traffic Engineering29
and Operator Business communities.30
7.3.1.3 Number of soft handoff leg addition attempts31
A. This measurement provides the attempted number of soft handoff leg32
addition attempts (considering both inter and intra handoffs).33
B. CC34
7/28/2019 3GPP2 EVDO
29/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 28
C. Transmission of a Um message Handoff Direction, Extended Handoff1
Direction, General Handoff Direction or Universal Handoff Direction2
from the target BS to MS, which requires MS to add the legs [25].3
D. An integer value4
E. HO.attSoftHoAddition5
F. BscFunction6
G. Valid for circuit switched traffic.7
H. cdma2000 1X, cdma2000 1XEV-DV8
I. This measurement is mainly dedicated to Operator Traffic Engineering9
and Operator Business communities.10
7.3.1.4 Number of successful soft handoff leg additions11
A. This measurement provides the number of successful soft handoff leg12
additions (considering both inter and intra handoffs).13
B. CC14
C. Receipt by the target BS from MS of an Um message Handoff15
Completion or Extended Handoff Completion, indicating the16
successful soft handoff leg addition [25].17
D. An integer value18
E. HO.succSoftHoAddition19
F. BscFunction20
G. Valid for circuit switched traffic.21
H. cdma2000 1X, cdma2000 1XEV-DV22
I. This measurement is mainly dedicated to Operator Traffic Engineering23
and Operator Business communities.24
7.3.2 BSC traffic measurements related to the PS domain25
7.3.2.1 Number of attempted PS calls26
A. This measurement provides the number of attempted calls for PS27
domain service.28
B. CC29
C. Receipt of Um message Origination by the BS from an MS [25], with30
Service Option set to 33 (see [38]) indicating cdma2000 high speed31
packet service, which excludes the attempted handoffs and the calls32
when the Packet Data Session State is Dormant (see also [26]).33
D. An integer value34
E. RRC.attCallsPs35
F. BscFunction36
7/28/2019 3GPP2 EVDO
30/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 29
G. Valid for packet switched traffic.1
H. cdma2000 1X, cdma2000 1XEV-DV2
I. This measurement is mainly dedicated to Operator Traffic Engineering3
and Operator Business communities.4
7.3.2.2 Number of call-drops for PS domain service5
A. This measurement provides the total number of call-drops for PS6
domain service due to the errors of radio, MSC or PDSN.7
B. CC8
C. On drop of the PS call due to failure of the radio, MSC or PDSN.9
D. An integer value10
E. RRC.nbrCallDropPs11
F. BscFunction12
G. Valid for packet switched traffic.13H. All14
I. This measurement is mainly dedicated to Operator Traffic Engineering15
and Operator Business communities.16
7.3.2.3 Number of requests for forward SCH17
A. This measurement provides the number of requests for forward SCH.18
B. CC19
C. On the attempt of the BS to assign the forward SCH.20
D. An integer value21
E. RRC.attFschAssign22
F. BscFunction23
G. Valid for packet switched traffic.24
H. cdma2000 1X25
I. This measurement is mainly dedicated to Operator Traffic Engineering26
and Operator Business communities.27
7.3.2.4 Number of successful assignments for forward SCH28
A. This measurement provides the total number of successful assignments29
for forward SCH, which include assignments that match the requested30
rate or mismatch the requested rate.31
B. CC32
C. On successful assignment of the forward SCH.33
D. An integer value34
7/28/2019 3GPP2 EVDO
31/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 30
E. RRC.succFschAssign1
F. BscFunction2
G. Valid for packet switched traffic.3
H. cdma2000 1X4
I. This measurement is mainly dedicated to Operator Traffic Engineering5 and Operator Business communities.6
7.3.2.5 Number of requests for reverse SCH7
A. This measurement provides the number of requests for reverse SCH.8
B. CC9
C. On the attempt of assignment of the reverse SCH.10
D. An integer value11
E. RRC.attRschAssign12
F. BscFunction13
G. Valid for packet switched traffic.14
H. cdma2000 1X, cdma2000 1XEV-DV15
I. This measurement is mainly dedicated to Operator Traffic Engineering16
and Operator Business communities.17
7.3.2.6 Number of successful assignments for reverse SCH18
A. This measurement provides the total number of successful assignments19
for reverse SCH, which include assignments that match the requested20
rate or mismatch the requested rate.21B. CC22
C. On successful assignment of the reverse SCH.23
D. An integer value24
E. RRC.succRschAssign25
F. BscFunction26
G. Valid for packet switched traffic.27
H. cdma2000 1X, cdma2000 1XEV-DV28
I. This measurement is mainly dedicated to Operator Traffic Engineering29
and Operator Business communities.30
7.3.2.7 Traffic volume carried by Walsh Codes on SCHs for PS domain31service32
A. This measurement provides the traffic volume carried by Walsh Codes33
on SCHs for PS domain service (in erlang). E.g., if the SCH is 2X, the34
traffic volume of the SCH will be calculated on 2 Walsh Codes.35
7/28/2019 3GPP2 EVDO
32/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 31
B. DER (n=1)1
C. This measurement is obtained by summing the traffic for PS service on2
all SCHs; The traffic on each SCH is calculated by accumulating the3
seizure time intervals between the SCH is successfully assigned, and4
the SCH is released over a granularity period, the end value of this time5
will be divided by the granularity period, and then be convert to the6
traffic volume according to the Walsh Code of the SCH. The7
accumulator shall be re-initialized at the beginning of each granularity8
period.9
D. A value of type Real10
E. RRC.trafficByWalshPsSch11
F. BscFunction12
G. Valid for packet switched traffic.13
H. cdma2000 1X, cdma2000 1XEV-DV14
I. This measurement is mainly dedicated to Operator Traffic Engineering15and Operator Business communities.16
7.3.2.8 Traffic volume carried by Walsh Codes on FCHs for PS domain17service18
A. This measurement provides the traffic volume carried by Walsh Codes19
on FCHs for PS domain service (in erlang). For example if the FCH is 8X20
based, then the traffic volume of the FCH will be calculated on 8 Walsh21
Codes.22
B. DER (n=1)23
C. This measurement is obtained by summing the traffic for PS service on24
all FCHs. The traffic on each FCH is calculated by accumulating the25
seizure time intervals between the FCH is successfully assigned, and26
the FCH is released over a granularity period, the end value of this time27
will be divided by the granularity period, and then be convert to the28
traffic volume according to the Walsh Code of the FCH. The29
accumulator shall be re-initialized at the beginning of each granularity30
period.31
D. A value of type Real32
E. RRC.trafficByWalshPsFch33F. BscFunction34
G. Valid for packet switched traffic.35
H. cdma2000 1X, cdma2000 1XEV-DV36
I. This measurement is mainly dedicated to Operator Traffic Engineering37
and Operator Business communities.38
7/28/2019 3GPP2 EVDO
33/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 32
7.3.2.9 Traffic volume carried on CEs which are seized by SCHs for PS1domain service2
A. This measurement provides the traffic volume carried on CEs which are3
seized by SCHs for PS domain service (in erlang).4
B. DER (n=1)5
C. This measurement is obtained by summing the traffic for PS service on6all CEs seized by SCHs; The traffic on each CE seized by SCH is7
calculated by accumulating the seizure time intervals between the CE is8
successfully assigned, and the CE is freed over a granularity period, the9
end value of this time will be divided by the granularity period to be10
convert to the traffic volume. The accumulator shall be re-initialized at11
the beginning of each granularity period.12
D. A value of type Real13
E. RRC.schCeTraffic14
F. BscFunction15G. Valid for packet switched traffic.16
H. cdma2000 1X, cdma2000 1XEV-DV17
I. This measurement is mainly dedicated to Operator Traffic Engineering18
and Operator Business communities.19
7.3.2.10 Number of forward RLP packets20
A. This measurement provides the total number of forward RLP packets.21
B. DER (n=1)22
C. On transmission of the forward RLP packets from the BSC (for RLP see23[27]).24
D. An integer value25
E. RRC.nbrForwardRlpPkts26
F. BscFunction27
G. Valid for packet switched traffic.28
H. All29
I. This measurement is mainly dedicated to Operator Traffic Engineering30
and Operator Business communities.31
7.3.2.11 Number of repeated forward RLP packets32
A. This measurement provides the number of repeated forward RLP33
packets.34
B. DER (n=1)35
C. On retransmission of the forward RLP packets from the BSC (for RLP36
see [27]).37
7/28/2019 3GPP2 EVDO
34/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 33
D. An integer value1
E. RRC.nbrResendedForwardRlpPkts2
F. BscFunction3
G. Valid for packet switched traffic.4
H. All5I. This measurement is mainly dedicated to Operator Traffic Engineering6
and Operator Business communities.7
7.3.2.12 Number of reverse RLP packets8
A. This measurement provides the total number of reverse RLP packets.9
B. DER (n=1)10
C. On transmission of the reverse RLP packets from the BSC (for RLP see11
[27]).12
D. An integer value13E. RRC.nbrReverseRlpPkts14
F. BscFunction15
G. Valid for packet switched traffic.16
H. All17
I. This measurement is mainly dedicated to Operator Traffic Engineering18
and Operator Business communities.19
7.3.2.13 Number of repeated reverse RLP packets20
A. This measurement provides the number of repeated reverse RLP21packets.22
B. DER (n=1)23
C. On retransmission of the reverse RLP packets from the BSC (for RLP24
see [27]).25
D. An integer value26
E. RRC.nbrResendedReverseRlpPkts27
F. BscFunction28
G. Valid for packet switched traffic.29
H. All30
I. This measurement is mainly dedicated to Operator Traffic Engineering31
and Operator Business communities.32
7.3.2.14 Number of failed requests for PS domain service33
A. This measurement provides the number of failed requests for PS34
domain service due to radio resource shortage.35
7/28/2019 3GPP2 EVDO
35/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 34
B. CC1
C. The BS fails to assign the resource for requests of PS domain service2
due to the shortage of TCE unit, RF link capacity, Walsh Codes, power,3
etc.4
D. An integer value5
E. RRC.nbrCongestionRadioPart6
F. BscFunction7
G. Valid for packet switched traffic.8
H. All9
I. This measurement is mainly dedicated to Operator Traffic Engineering10
and Operator Business communities.11
7.3.2.15 Number of attempted PS handoffs12
A. This measurement provides the number of attempted incoming13
handoffs for PS domain service, including soft handoffs, hard handoffs14and dormant handoffs.15
B. CC16
C. For inter BS hard handoffs on receipt by the BS of an A1 message17
Handoff Request [23] from the MSC with service option set to 3318
indicating cdma2000 high speed packet service;19
Or, for inter BS soft handoffs, on receipt by the BS of an A7 message20
A7-Handoff Request [28] from another BSC for the PS domain service;21
Or, for inter BS dormant handoffs, on receipt by the BS of an Um22
message Origination [25] with the service option set to 3323indicating cdma2000 high speed packet service, and the DRS set to24
0;25
Or, for intra BS PS domain handoffs, on transmission of an Um26
message Extended Handoff Direction [25], Handoff Direction [25],27
General Handoff Direction [25] or Universal Handoff Direction [25]28
message from the BS.29
D. An integer value30
E. HO.attHoPs31
F. BscFunction32
G. Valid for packet switched traffic33
H. cdma2000 1X, cdma2000 1XEV-DV34
I. This measurement is mainly dedicated to Operator Traffic Engineering35
and Operator Business communities.36
7/28/2019 3GPP2 EVDO
36/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 35
7.3.2.16 Number of successful PS handoffs1
A. This measurement provides the number of successful incoming2
handoffs for PS domain service, including soft handoffs, hard handoffs3
and dormant handoffs.4
B. CC5
C. For inter BS hard handoffs on transmission of an A1 message Handoff6Request Acknowledge [23] indicating the successful hard handoff for7
PS domain service from the BS to MSC;8
Or, for inter BS soft handoffs, on transmission of an A7 message A7-9
Handoff Request Acknowledge [28] indicating the successful hard10
handoff for PS domain service from the target BS to the source BS;11
Or, for inter BS dormant handoffs, on receipt by the BS of an A9-12
Release-A8 Complete [29] message, or A9-Connect-A8 message, for13
the PS dormant service handoff;14
Or, for intra BS PS domain handoffs, on receipt by the BS of an Um15message Handoff Completion [25] or Extended Handoff Completion16
[25] message from the BS.17
D. An integer value18
E. HO.succHoPs19
F. BscFunction20
G. Valid for packet switched traffic.21
H. cdma2000 1X, cdma2000 1XEV-DV22
I. This measurement is mainly dedicated to Operator Traffic Engineering23 and Operator Business communities.24
7.3.3 BSC system resource measurements25
7.3.3.1 Number of available trunk circuits26
A. This measurement provides the number of available trunk circuits (6427
Kbps time slots) of interface A, i.e. the A circuits which are not broken28
down.29
B. GAUGE30
C. This measurement will be increased on transition of a trunk circuit31
from unavailable (can not be assigned) into available (can be assigned),32
decreased on transition of a trunk circuit from available (can be33
assigned) into unavailable (can not be assigned).34
D. An integer value35
E. RRC.nbrAvailACircuits36
F. BscFunction37
7/28/2019 3GPP2 EVDO
37/143
3GPP2 S.S0093-0 v2.0
2006 3GPP2 Page 36
G. Valid for circuit switched traffic.1
H. cdma2000 1X2
I. This measurement is mainly dedicated to Operator Traffic Engineering3
and Operator Business communities.4
7.3.3.2 Duration of seizures of A-Interface circuits5
A. This measurement provides the time of seizures of interface A circuits6
(64 Kbps time slots, in seconds).7
B. DER (n=1)8
C. This measurement is o