70571738-411-2133-525-06-12

8/13/2019 70571738-411-2133-525-06-12

1/950

8/13/2019 70571738-411-2133-525-06-12

2/950

Whats inside...CDMA-LTX performance

OTAPA perform anceCall fl ow diagrams wit h OMsMSC OM description sBSC OM descripti onsBTS OM descriptio ns

8/13/2019 70571738-411-2133-525-06-12

3/950

CDMA

Operational Measurements Reference System Performance Metrics

Document number: 411-2133-525Product release: NBSS15.0Document version: Standard 06.12Date: April 2008

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright 2008 Nortel Networks

All Rights Reserved.

Originated in the United States of America

This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectualproperty rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by NortelNetworks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied,produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components asprogress in engineering and manufacturing may warrant.

* Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks.

8/13/2019 70571738-411-2133-525-06-12

4/950

ivNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

8/13/2019 70571738-411-2133-525-06-12

5/950

vNortel Networks Copyright 2008 Nortel Networks

CDMA System Performance System Performance Metrics NBSS15.0

Contents 1

About this document 3-xviiPurpose 3-xvii

Audience 3-xviiiScope of document 3-xviii

Organization 3-xviiiRelated documents 3-xixIndication of hypertext links 3-xx

New in this release 4-xxiFeatures 4-xxiOther changes 4-xxi

CDMA OM design overview 1-1OM philosophy 1-1

MTX OM philosophy 1-1CDMA access system OM philosophy 1-2

MTX OM consolidation 1-4CDMA access system OM consolidation 1-5OM metrics overview 1-8OM validation overview 1-9

Call setup performance 2-1List of OMs 2-1Call setup failure before resources are allocated (blocked calls) 2-9

Goal 2-10Formula usage 2-10Total calls attempted 2-12Call types 2-13

Overall call setup failures (call blocking rate) 2-14Call setup failures (blocks) due to lack of EBSC/BSC resources 2-14Call setup failures due to BSC/EBSC processing errors 2-15Call setup failures (blocks) due to BTS physical resources 2-16Call setup failures (blocks) due to BTS time-outs 2-163G packet data call setup failures (blocks) 2-17Screened calls 2-17Screened calls for 3G packet data calls due to mobile service inactive indication

8/13/2019 70571738-411-2133-525-06-12

6/950

vi ContentsNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

during network initiated dormant to active transition 2-18Call setup failures due to RF failures 2-18

Goal 2-19Formulas 2-19

Voice call failures during setup due to non-RF resource failures 2-20Formulas 2-21Miscellaneous packet data call failures 2-21

Additional formulas 2-22Voice call setup performance metrics on a per platform basis- (EBSC andBSC) 2-22MEID related metrics 2-23VPAD (voice preemption of active data) voice call setup performance - systemlevel 2-25Global emergency call metrics 2-26Silent retry 2-273G packet data 2-27Closed R-P metrics 2-28OpenRP Metrics 2-30

Validation 2-32For all call types together or 2G-only systems 2-32Silent retry OMs validation 2-33Blocking OMs validation 2-33Validation for voice call setup performance OMs (per platform basis) 2-34Validation for MEID OMs 2-35Validation for 3G packet data OMs 2-35Validation of VPAD OMs 2-35

Additional validation of HHO OMs 2-35Validation of close RP OMs 2-36Validation of open RP OMs 2-36Validation for PCU manager OMs 2-36

Recommendations 2-371xRTT packet data performance 3-1List of OMs 3-1Goals 3-8Formulas 3-8

SCH burst setup 3-8SCH radio link setup 3-26

Additional information 3-41Validation 3-43

Validation of forward burst setup OMs 3-44Validation of reverse burst setup OMs 3-46Validation of F-SCH primary link setup OMs 3-47Validation of F-SCH handoff link setup OMs 3-47

3-48Validation of R-SCH primary link setup OMs 3-48Validation of R-SCH handoff link setup OMs 3-49Validation of SCHDrop OMs 3-49

RLP throughput performance 4-1

8/13/2019 70571738-411-2133-525-06-12

7/950

Contents vi iNortel Networks Copyright 2008 Nortel Networks


List of OMs 4-1RLP throughput performance metrics 4-2

Aggregate sector throughput (per EBID basis) 4-3Per channel aggregate sector throughput (per EBID basis) 4-4Per channel contribution to the overall aggregate sector throughput (per EBIDbasis) 4-6

Average mobile user throughput (per cluster/system basis for all givencarriers) 4-8Per channel throughput (per EBID basis) 4-10Per channel utilization (per EBID basis) 4-13Per channel data-retransmission percentage (per EBID basis) 4-15

Average physical layer data rate while bursting 4-17Maximum bearer data throughput 4-17Supporting metrics for 3G data throughput performance 4-18

Validation formulas 4-19

Access robustness package performance 5-1Goal 5-1List of OMs 5-1CDMA access robustness package performance 5-2

CASHO failures per sector 5-2CASHO releases per sector 5-2

ACCHO failures per sector 5-2 ACCHO releases per sector 5-2

Validation 5-2Validation of CASHO OMs 5-2Validation of ACCHO OMs 5-2

Dropped call performance 6-1Goals for dropped call performance 6-2

List of OMs 6-2Overall dropped call rate 6-2RF related dropped call rate 6-3Network related dropped call rate 6-3

Additional formulas 6-3Recommendations 6-4

Handoff performance 7-1List of OMs 7-2Soft and softer handoff performance 7-3

Goal 7-4Formula 7-4Recommendations 7-4

Sector based hard handoff performance 7-5Goal 7-5Formula 7-5Validation 7-7

Route based hard handoff performance 7-8Goal 7-8Formulas 7-8

8/13/2019 70571738-411-2133-525-06-12

8/950

viii ContentsNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

Validation 7-8Trigger type based hard handoff performance 7-8

Goal 7-9Formulas 7-9Validation 7-13Recommendation 7-14

Intelligent voice service negotiations performance 8-1Goal 8-2List of OMs 8-2Formulas 8-3

Service redirection performance 8-3Successful call setup based on mobile requested service option 8-6Validation 8-8Recommendations 8-8Query performance 8-10

BTS performance 9-1List of OMs 9-1Resource blocking and voice call downgrades 9-8

Origination and termination blocking 9-9Soft handoff blocking 9-103G to 2G voice calls downgrade rate 9-11

Handoff sectors/beams per user 9-11FSCH queuing 9-14SCH link data rate downgrades 9-17

Percentage of SCH data rate downgrades per EBID 9-17Distribution of SCH downgrades by specific downgrade reason 9-18Distribution of SCH downgrades by specific FSCH downgrade scenario 9-19

Walsh code usage distribution 9-20

Lower bound of average number of walsh codes in simultaneous use 9-21Upper bound of average number of walsh codes in simultaneous use 9-22

Physical resource utilization metrics 9-22Peak percentage of physical resources used for 2G FCH 9-22Peak percentage of physical resources used for 3G FCH 9-22Peak percentage of forward physical resources used for SCH 9-22Peak percentage of reverse physical resources used for SCH 9-22Peak percentage of forward physical resources used 9-22Peak percentage of reverse physical resources used 9-22Peak percentage of voice resources used on the forward FCH 9-23Peak percentage of data resources used on the forward FCH 9-23

Forward transmit power utilization 9-23Lower bound of average occupancy range 9-24Upper bound of average occupancy range 9-24Percentage of time forward transmit power is in an occupancy range 9-24

Forward common channel utilization 9-24Paging channel utilization 9-24Forward common control channel utilization 9-25

Reverse common channel utilization 9-26 Access channel utilization 9-26

8/13/2019 70571738-411-2133-525-06-12

9/950

Contents ixNortel Networks Copyright 2008 Nortel Networks


Enhanced access channel utilization 9-27Reverse common channel message received by type 9-28

Access channel message received by type 9-28Enhanced access channel metrics 9-31

Forward common channel message drop rate 9-31Paging channel message drop rate 9-31FCCCH channel message drop rate 9-32

Forward common channel messages sent by type 9-33Paging channel messages sent by type 9-33FCCCH channel messages sent by type 9-34

MFRM-3 9-34Metro Cell validation formulas 9-36

Paging performance 10-1Goal 10-1List of OMs 10-2

10-5CDMA call delivery performance metrics 10-5

Overall call delivery performance of a system without BCP activated 10-5Time distribution of page responses 10-8Delayed page response rate 10-8Overall call delivery performance of an anchor system with BCP activated 10-9

CDMA intersystem paging performance metrics 10-11Overall intersystem paging performance of an anchor system (all border routes ofall anchor sectors) 10-12Intersystem paging performance of an anchor sector (all border routes of theanchor sector) 10-13Intersystem paging performance of a border route (of an anchor sector) 10-14

CDMA IZP zone performance metrics 10-15Zone performance for voice, CSD, and packet data calls 10-16

Delayed page response rate 10-19Zone performance for SMS calls 10-20Zone performance for MWI 10-2210-24

MWI delivery performance 10-24Voice preemption of active data feature paging performance 10-28

Overall paging failures for VPAD feature 10-28Overall paging successes for VPAD feature 10-28

AMPS formulas 10-28 AMPS repaging formula 10-28

Validation 10-29CDMA call delivery performance OM validations 10-29CDMA intersystem paging performance OM validations 10-29CDMA zone performance OM validations (for a single zone) 10-30VPAD OMs 10-31MWI OMs 10-32

Recommendations 10-32CDMA paging 10-32Zone paging 10-32

8/13/2019 70571738-411-2133-525-06-12

10/950

x ContentsNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

Border paging performance 11-1Goal 11-1List of OMs 11-1

11-3CDMA intersystem paging performance metrics 11-3

Overall intersystem paging performance of a border system (all anchorroutes) 11-4Intersystem paging performance of an anchor route 11-5

CDMA BCP zone performance metrics 11-6Zone performance for voice, CSD, and packet data calls 11-6Zone performance for SMS calls 11-10Success rate of SMS delivery in the border system 11-1011-10

Validation 11-10CDMA border cell paging performance OM validations 11-10CDMA zone performance OM validations (for a single BCP zone) 11-11SMS Delivery 11-1211-12

Recommendations 11-12CDMA paging 11-12

Data burst message delivery performance 12-1List of OMs 12-2Idle mode SMS 12-4

Goal 12-5Formula 12-5Validation 12-8

In call SMS 12-9Goal 12-9

Formula 12-9Validation 12-10

CAU-CM SMS origination delivery 12-10Goal 12-10Formula 12-10Validation 12-10

Message length histogram metrics 12-10Formula 12-10Distribution of DDS messages across channels 12-11Distribution of DDS messages according to size on a per channel basis 12-12Upper bound of the average message length on per channel basis 12-13

Mobile-initiated R-SDB 12-13R-SDB size histogram metrics 12-13Mobile-initiated SDB delivery success rate at the PCU-M 12-15Mobile-initiated SDB delivery success rate at the PCU 12-15Percentage of R-SDBs received on the R-EACH 12-16Validation 12-16

Location services performance 13-1Goal 13-1

8/13/2019 70571738-411-2133-525-06-12

11/950

Contents xiNortel Networks Copyright 2008 Nortel Networks


List of OMs 13-1LCS paging performance 13-2LCS call setup performance 13-3Miscellaneous information 13-4

Recommendations 13-5Notes 13-5

MCTA performance 14-1List of OMs 14-1MCTA call setup failures 14-3

Goal 14-4Formula 14-4Total number of call setups attempted 14-4Call types 14-5MCTA frequency selection failures 14-6MCTA resource allocation failures before CDA is executed 14-6Reason codes for MCTA frequency resource allocation failures 14-7MCTA call setup failures 14-8

14-9Non MCTA frequency resource allocation failures (per frequency) 14-9Retain loading related metrics 14-9Paging channel redirection related metrics 14-10MCTA RF access failure (per frequency) 14-10MCTA RF related dropped call rate (per frequency) 14-12

Validation 14-12Originations, terminations, and handoffs 14-12Miscellaneous 14-12

Recommendations 14-13

Authentication performance 15-1 Authentication air-interface performance 15-1

Goal 15-2List of OMs 15-2Formulas 15-2Validation 15-3Recommendations 15-4

Call resource allocation and management 16-1List of OMs 16-1

16-9BSC/EBSC resource management 16-9

RMU resource management 16-9RMU resource allocation performance 16-11Resource utilization metrics 16-13NRM resource allocation performance 16-18SBSRM resource allocation performance 16-26PCU change rate for dormant to active requests 16-27PCU allocation performance for dormant handoff requests 16-29

Resource allocation metrics during CNFP overload 16-3116-32

8/13/2019 70571738-411-2133-525-06-12

12/950

xi i ContentsNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

Effects of CSRM / SBSRM overload on platform selection mechanism 16-32Resource allocation failures at CSRM and SBSRM (due to overloadcondition) 16-33

Resource allocation performance for connection type 16-34Resource allocation failures for a connection type (due to lack of resources) 16-34Resource allocation failures for a connection type (due to processing errors) 16-34Resource availability rate for a connection type 16-35

Additional formula 16-35Resource unavailability rate for a connection type 16-35Resource re-direction rate 16-36Distribution rate of resource allocation per connection type 16-37Resource allocation failure rate per connection type 16-37Distribution ratio for TrFO Vs. NonTrFO calls at TrFO capable PVG cards 16-37Distribution ratio for EVRC Vs. Non-EVRC calls at non-TrFO PVG cards 16-38

EVRC-B related Metrics 16-38EVRC-B Mode distribution Metrics (event based) 16-39EVRC-B Mode distribution Metrics (time-based) 16-40

Primary sector capacity metrics 16-40 Approximate carried load per BSC for non-packet data 16-41 Approximate carried load per BSC for packet data 16-41 Approximate carried load per sector 16-42 Approximate carried load per carrier-sector 16-42Load contribution per service option on BSC 16-43

Eighth rate gating formulas 16-44Gating request rates 16-44Gating request granted rate 16-45Gating request denied rate 16-45Gating-enabled handoff percentage 16-46

Gating deactivation rate 16-46Gating usage 16-47Validation 16-47

Service option validation formulas 16-47Resource utilization validation formula 16-48

16-48Resource allocation validation formula 16-48NRM resource allocation validation formula 16-49SBSRM resource allocation validation formula 16-50CSRM resource allocation validation formula 16-50

16-50Dormant-to-active - PCU change validation formula 16-50Dormant handoff - PCU allocation validation formula 16-51

Resource allocation for connection types validation formula 16-51Eighth rate gating validation formula 16-53

RF performance 17-1List of OMs 17-1Reference sector FER metrics 17-2

FCH formula 17-2

8/13/2019 70571738-411-2133-525-06-12

13/950

Contents xiiiNortel Networks Copyright 2008 Nortel Networks


SCH formula 17-4Recommendations 17-5

CDMA-LTX performance 18-1Pegging methods 18-1List of OMs 18-2Call setup performance 18-4

Call setup failure before resources are allocated 18-4Goal 18-4Formula 18-5Validation 18-9Recommendations 18-11

Access failures 18-13Dropped call performance 18-13

Goal 18-14Formula 18-14Validation 18-15Recommendations 18-15

Paging performance 18-15Goal 18-15Formula 18-15Limitations 18-17

MCTA performance 18-17Goal 18-17Formula 18-17

V5.2 protocol adaptor performance 18-24Circuit switched data performance 18-25

Goal 18-25Formula 18-25

OTAPA performance 19-1Goal 19-1List of OMs 19-1Formulas 19-2

Validation 19-2

Call flow diagrams with OMs 20-12G/3G voice call setup flow diagram with OMs 20-2 Voice call setup flow diagram with OMs- CSVS and SBS subsystems 20-9Call setup flow diagram using BAM channels 20-16MEID- Registration, origination/termination call flow with OMs 20-192G/3G voice/data soft handoff (intra-BSC) flow diagram with OMs 20-30Hard handoff flow diagram with OMs 20-33Hard handoff (intra-MSC) 20-34

Access robustness package: call flow with OM register pegs 20-35IVSN flow diagram with OMs 20-37Intelligent zone paging flow diagram with OMs 20-45SMS termination over paging channel 20-45SMS termination over traffic channel 20-47In-call SMS termination 20-48

8/13/2019 70571738-411-2133-525-06-12

14/950

xi v ContentsNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

SMS origination over access channel 20-49SMS origination over traffic channel 20-50In-call SMS origination 20-51VPAD call flow 20-52VPAD call flow with OM pegs 20-53Border cell paging and call setup 20-54

Successful paging and call setup in border system 20-54Successful paging for SMS and SMS delivery in border system 20-56

Inter-system hard handoff 20-60Target system 20-60

MSC OM descript ions 21-1MSC operational measurements 21-1

BSC OM descriptions 22-1BSC operational measurements 22-1CDMA-LTX operational measurements 22-167

BTS OM descript ions 23-1Metro Cell BTS operational measurements 23-2
http://-/?-

8/13/2019 70571738-411-2133-525-06-12

15/950

Front xvNortel Networks Copyright 2008 Nortel Networks


Table 13-1Location services performance OMs 13-1

Table 14-1MCTA performance OMs 14-1

Table 22-1List of BSC OMsSCH burst setup OM group 22-5

Table 22-2 List of BSC OMsPlatform Selection OM group 22-121Table 22-3

List of BSC OMsDHO call resource request processing OMgroup 22-135

Table 22-4 List of BSC OMs OM group 22-150

8/13/2019 70571738-411-2133-525-06-12

16/950

xvi FrontNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

8/13/2019 70571738-411-2133-525-06-12

17/950

xviiNortel Networks Copyright 2008 Nortel Networks


About this document 1Purpose 1

This document is written to assist the service provider in determining andtracking the performance of the Nortel CDMA System. Various formulas are

provided for ascertaining system performance. In some cases the documentalso provides recommendations on the course of action to take. Some

performance measurements are kept simply for establishing norms for system performance so that the service provider may monitor changes in operation(for instance, resource utilization, and call traffic patterns) that are dependenton the number of subscribers/users of the system, rather than a parameterdirectly under the control of the system.

It is also important to note that the performance metrics listed in thisdocument should be evaluated over several OM reporting cycles. This is dueto the fact that the number of established calls may fluctuate over time. Thesame fluctuation could be seen in various other OM registers that trackseveral call-related events. These fluctuations would cause the metrics to varysignificantly from one reporting period to the other.

The focus of this document is to provide its customers with a high levelunderstanding of the CDMA related OMs available and how to measure thevarious types of system performance with those OMs.

Note: The performance measurements presented in this document aremeant to track the CDMA system performance rather than specific callmodels.

The example performance metric goals listed in this document are high levelobjectives for the service provider and depend on the planned RF/Networkrequirements. If required, similar metric goals can be created for othermetrics listed in this document. Also, the listed metric goals can be changedfrom system to system. In general, the metrics listed in this document should

be monitored against the metric goals, and if the success rate goes down (orthe failure rate goes up), further investigation is usually required and should

be done.

8/13/2019 70571738-411-2133-525-06-12

18/950

xviii About this documentNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

Audience 1The audience for this document is Nortel designers, testers, Nortel customers,field support and VO, system engineering groups, and RF engineering. Itassumes the reader has a good understanding of the DMS-MTX CDMA

software and hardware architecture and CDMA RF technology.

Scope of document 1This document covers Operational Measurements related to CDMA SystemPerformance. The CDMA Operational Measurements (OMs) are comprisedof OMs from the DMS-MTX and the CDMA Access Subsystems (whichincludes BSC and/or EBSC and BTSs). This document does not cover BSC/EBSC and BTS non-application OMs such as for ACN/BCN Transport andOverload Characterization.

This document is written within the context of the Nortel CDMA NBSSSystem. Hence, we refer to OMs that peg for NOIS only (with the exceptionof some CM OMs that peg for IOS).

This document is not intended to correct or document existing performancemeasurements that are not being added by or are not of primary concern to theCDMA system.This document is not intended to provide the proceduresnecessary for collecting the MSC, BSC or BTS OM data. Please refer to NTP

NN20000-104 and NTP # 411-2131-814 for OM collection procedures.

Open A is not discussed in this document. MDM OMs are not discussed inthis document. Refer to NTP # 241-6001-031 Preside Multiservice DataManager Performance Management User Guide.

Organization 1The document is organized by performance area. Chapter 2 through Chapter18 describe the CDMA specific product metrics. Each of these chaptersspecifies a few example metric goals, list of applicable operationalmeasurements (OMs) used to calculate the metric, formulas for calculatingthe metric, and a section that recommends changes to the configurable

parameters of the MTX-CDMA system or other potential actions to addressidentified performance issues. For a better understanding and interpretation ofthe metrics provided in this NTP; it is essential to refer to the explanation ofthe operational measurements (OMs) provided in the OM Descriptionschapters (Chapters 21, 22 and 23).

The following is a list of chapters and performance areas that are discussed inthis document: Chapter 1, CDMA OM design overview

Chapter 2, Call setup performance

8/13/2019 70571738-411-2133-525-06-12

19/950

About this document xixNortel Networks Copyright 2008 Nortel Networks


Chapter 3, 1xRTT packet data performance

Chapter 4, RLP throughput performance

Chapter 5, Access robustness package performance

Chapter 6, Dropped call performance Chapter 7, Handoff performance

Chapter 8, Intelligent voice service negotiations performance

Chapter 9, BTS performance

Chapter 10, Paging performance

Chapter 11, Border paging performance

Chapter 12, Data burst message delivery performance

Chapter 13, Location services performance

Chapter 14, MCTA performance Chapter 15, Authentication performance

Chapter 16, Call resource allocation and management

Chapter 17, RF performance

Chapter 18, CDMA-LTX performance

Chapter 20, Call flow diagrams with OMs - provides call setup andhandoff scenario flow charts with key OMs from related OM group forthe majority of the OMs discussed in this document.

Chapter 21, MSC OM descriptions - contains a list of all the MSC OMs

referenced in this document organized by OM group. Chapter 22, BSC OM descriptions - contains a list of all the BSC OMs

referenced in this document organized by OM group.

Chapter 23, BTS OM descriptions - contains a list of all the BTS OMsreferenced in this document organized by MO.

Related documents 1 NTP # 411-2133-526: Nortel CDMA Performance Management --

Operational Guidelines. Please refer to the System Parameters section forall the Parameters mentioned in this Guide .

NTP # 411-2131-814: DMS-MTX Operational Measurements Reference

Manual NTP # 241-6001-031: Preside Multiservice Data Manager Performance

Management User Guide

NTP # 411-2133-802: Packet Data Serving Node Customer InformationGuide .

8/13/2019 70571738-411-2133-525-06-12

20/950

8/13/2019 70571738-411-2133-525-06-12

21/950

1-xxiNortel Networks Copyright 2008 Nortel Networks


New in this release 1The following sections detail whats new in Nortel CDMA Operational

Measurements Reference -- System Performance Metrics ( NTP 411-2133-525) for NBSS 15.0 / MTX15.

Features on page 1-xxi

Other changes on page 1-xxiFeatures 1

This document contains no feature update for this release.

Other changes 1See the following section for information about changes that are not featurerelated:

Updated the section Network-initiated dormant-to-active transition failurerate (page -27)

Updated the table Call setup performance OMs (page -2)

Updated the table MSC operational measurements (page -1)

8/13/2019 70571738-411-2133-525-06-12

22/950

1-xxii New in this releaseNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

8/13/2019 70571738-411-2133-525-06-12

23/950

1-1Nortel Networks Copyright 2008 Nortel Networks


CDMA OM design overview 1OM philosophy 1

The CDMA operational measurements (OMs) consist of OMs from the DMS-MTX (digital multiplexing switch - mobile telephone exchange) system,including the CAU, CM and other subsystems, and the CDMA access system,including the BSC, EBSC, and BTS subsystems. OMs are configured,

collected, stored, and retrieved separately on each system.

MTX OM philosophyThe DMS-MTX OMs are collected individually by each subsystem (CAU,RMU, and CM) and are periodically sent to the CM for collection. MTX OMsare organized and reported on a per-system, per-sector, or per-carrier-sector

basis. MTX OMs are divided into two categories: non-CDMA specific OMsand CDMA specific OMs.

Non-CDMA-specif ic OMsThe non-CDMA-specific OMs consist of the OMs common to CDMA,TDMA, and AMPS technologies. Most of these common OMs are related tocall processing. However, on systems that are configured for CDMA only,these OMs reflect CDMA related events only.

For more information about non-CDMA-specific MTX OMs, see CDMA/ TDMA Operational Measurements Reference Manual ( NTP 411-2131-814).

CDMA-specific OMsMany OMs have been added to the MTX specifically for CDMA-relatedevents. For example, all OMs pegged by the CAU and RMU are CDMA-specific. The majority of these CDMA-specific groups are identified by OMgroup names beginning with CAU, RMU, or CDMA.

For more information about CDMA-specific OMs, see MSC OM descriptions(page 21-1) , BSC OM descriptions (page 22-1) , and BTS OM descriptions(page 23-1) .

8/13/2019 70571738-411-2133-525-06-12

24/950

1-2 CDMA OM design overviewNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

Extension registersThe standard OM registers hold a range of values from 0 to 65 535. When thecount in a register exceeds its design limit of 65 535, its extension register (ifmade available) increases by 1 while the basic register clears. Therefore, anactual event count of 65 536 would show a count of 1 in the extension registerand 0 in the basic register. When the actual event count reaches 131 072, theextension register would increase again and show a count of 2, and the basicregister would clear again and show a count of 0. Since the features and

behavior of extension registers are essentially the same as the registers thatthey extend, detailed explanations of individual extension registers areunnecessary. For example, the extension register for the OM PGRESP1 isPGRESP1X.

CDMA access system OM philosophyThe CDMA access system consists of the EBSC/BSC, and the BTS (basestation transceiver subsystem). From an OM perspective, the EBSC consists

of CPDS (CDMA packet data subsystem), CSVS (CDMA selection andvocoding subsystem), and BSC/SBS (selector bank subsystem).

CDMA access system OMs are collected individually by each subsystem andare periodically sent to either the BSSM (base station subsystem manager) orthe C-EMS (CDMA element management subsystem). The BSC(SBS) andBTS OMs are sent to the BSSM as QMIP event report messages. Uponreceiving these messages, the BSSM stores them in its OM binary file that iscurrently open. These OMs appear mixed in the BSSM OM binary file.

The EBSC OMs (CSVS and CPDS) are uploaded as binary files to the C-EMS. 2pVS OMs are handled by the MDP (an MDM component).

C-EMSC-EMS is an OA&M platform that was introduced in NBSS 12.1. It managesthe OM configurations for the CSVS, CPDS, and SBS subsystems. The C-EMS co-resides and interacts with the existing BSSM. Starting in 14.0 releasethe BSSM should only be deployed with the C-EMS.

OM pegging typesEach OM can only have one pegging type. The pegging type describes onwhat basis a particular OM is collected. It also provides a reference and acontext for each OM.

The following pegging types are supported:

node-based: this type of OM is pegged on a per card basis

EBID-based: this type of OM is pegged on a per carrier-sector basis

IP-based: this type of OM is pegged on a per IP Address basis

8/13/2019 70571738-411-2133-525-06-12

25/950

CDMA OM design overview 1-3Nortel Networks Copyright 2008 Nortel Networks


service group-based: this type of OM is pegged on a per service group basis. Service groups are a collection of the following service types:

voice: EVRC (8Kbps), high rate voice service (13Kbps), basic 13K,and CSD service types

packet data: packet data service type

Other: OTAPA (RS1-9.6Kbps), SMS (RS1-9.6Kbps), location basedservices (RS1-9.6Kbps), Markov (9.6Kbps), Markov(14.4Kbps), MSloopback (8Kbps), and MS loopback (13Kbps) service types

service type-based: this type of OM is pegged on a per service type basis.All the service types are listed above.

resource type-based: this type of OM is pegged on a per resource type basis. Supported resource types are as follows:

CIC (circuit identification code), ebscSduVoiceAndOther,ebscSduPacketDataAndOther, ebscCct, ebscPkt, ebscTrfo, bscCct,and bscPkt

connection type-based: this type of OM is pegged on a connection type basis. Supported connections are as follows:

trfo, cct, pkt, and unspecified

multi-ID type-based: this type of OM is pegged on a multi-ID basis. Thisincludes the following pegging types: service type, service group, EBID,IP, resource type and RC

OM groupsAs of NBSS 12.0, OM groups are defined for all of the BSC and EBSC OMs.An OM group is a collection of OMs that logically, functionally, and

physically (for example, ESEL cards) relate to one another. Each OM groupis assigned an identifier (the group ID). All BSC and EBSC OMs, includingthose that existed prior to NBSS 12.0, are assigned to OM groups. All BSCand EBSC OMs are classified into these groups.

Each OM group can contain OMs of only one pegging type. In NBSS 12.0,BSC and EBSC OMs were given new sequence numbers.

OM configuration toolAs of NBSS 12.0, the service provider has the capability to turn the peggingof OMs in each group on or off on a per OM group or per OM basis. This

continues in NBSS 12.1 and in subsequent releases with the introduction ofthe C-EMS. The BSSM and the C-EMS provide the user with an interfacethat is used to inform the system of the users selection.

As of NBSS 14.0, the BSSM tool is no longer available. In NBSS 13.0, theOM management tool on the BSSM controls SBS OMs when the C-EMS isnot installed. The BSSM OM management tool is disabled when the C-EMS

8/13/2019 70571738-411-2133-525-06-12

26/950


411-2133-525 Standard 06.12 April 2008

is installed. The BSSM OM management tools provides system-wide controlof SBS OMs (not on a card-level basis).

When the C-EMS is installed, the BSSM OM management tool is disabledand the C-EMS OM configuration tool controls CSVS, CPDS, and SBS OMs.The C-EMS provides the ability to enable or disable OM reporting on a per-card basis for CSVS and CPDS only (for example, an individual DSFP cardcan be prevented from uploading its OM file.) The C-EMS OM configurationtool contains a superset of all configurable CSVS, CPDS, and SBS OMs(which are not visually segregated by SBS, CSVS, or CPDS type). Therefore,turning an OM on or off affects that OM on both platforms.

Turning performance-related OMs or OM groups on or off through the C-EMS OM configuration tool will affect those OM collections on CSVS,CPDS, and SBS. In addition, the C-EMS will not be aware of any manualconfiguration changes made to the SBS OMs or OM groups through the

BSSM system configuration MO.

The service provider must be aware that turning off performance-related OMsor OM groups may affect the ability of the provider to use some or all of themetrics described within this document.

For more information about C-EMS functionality, see Nortel CDMA C-EMSFault Management (NN20000-144).

BTS OMs are always collected at the subsystem level, but the reporting (forexample, uploading) may be enabled or disabled on a per-subsystem basisfrom the BSSM.

For more information about OM management and configuration, see NortelCDMA BSS Manager Fault Management -- Log Report Generation (NN20000-104).

CDMA OMs are collected and stored separately on the DMS-MTX and theBSCandEBSC and the BTS. These systems may or may not consolidate theOMs from multiple nodes as described below.

MTX OM consolidationBecause of the distributed architecture of the DMS-MTX, any CAU

provisioned for the single CDMA access system can process calls from any ofthe CDMA cells in that BSC system. Therefore, OMs are collected atindividual nodes, such as CAU and RMU, across multiple LPPs.

With the introduction of the MTX multi-BSC support feature, the NOIS CSS(CDMA signaling subsystem) is enhanced to support more BSCs (themaximum number is increased from 2 to 16) per MTX. As a result themaximum number of cell-sector-frequency supported per NOIS BSC is 4500

8/13/2019 70571738-411-2133-525-06-12

27/950



and the maximum number of cell-sector-frequency supported on the MTX is9000.

Depending on the provisioning of parameter OMXFR in table OFCENG, theCM will transfer the values of the OMs from the active to the holdingregisters every 15 or 30 minutes and upload the OMs from the CAUs andRMUs. Note that parameter OMHISTORYON is disabled.

For sector-based OMs, a software entity at the LPP combines andconsolidates the OMs from all CAUs on that LPP into a single sector-basedOM for that entire LPP. For example, if CAU108 receives 5 originations fromsector 13X and CAU109 receives 7 originations from sector 13X, there is oneorigination OM on the LPP for sector 13X, and its value is 12. These sector-

based OMs gathered at each individual LPP are uploaded to the CM. The CMcombines and consolidates all of the individual LPP OMs into a single sector-

based OM.

For carrier-sector based OMs, they are similarly consolidated and uploaded asdescribed for the sector-based OMs.

For node-based OMs, the OMs are uploaded directly to the CM withoutconsolidation.

In MTX 14.0 and NBSS 14.0, the OM framework is modified so that the NOIS LPP OM uploading is initiated each period according to the OFCENGOMXFR setting. This eliminates the two minute skew between the NOIS LPPand the CM OMs. A four minute delay is introduced before starting thesubsequent accumulation, recording, reporting, and printing for all MTX

OMs, including IOS and CM OMs. This delay is required to ensure that all NOIS LPP OMs are uploaded to the CM holding registers before processing.The NOIS LPP OMs are uploaded directly into the CM holding registersduring the four minute OM upload period (and not to the CM activeregisters). Any late NOIS LPP OMs received by the CM are placed in the CMactive registers and used during the next OMXFR cycle.

CDMA access system OM consol idationOM consolidation on the CDMA access subsystem is performed by theBSSM and the C-EMS OM parser tool. The OM parser is responsible for

parsing each new OM binary file. For OMs tracked on per node basis, the OM parser reports separately for each node. BSC nodes use ESEL and PCU cards.EBSC nodes use ACPs, CACs for DSFP cards, PCUs, and CACs for PCUFPcards. For non-node-based OMs, the OM parser consolidates (for example,sums) the OMs from the multiple nodes.

For non-node-based OMs, such as per EBID OMs (extended base ID), theOMs of the individual network elements that relate to that particular EBIDare added together to provide a network-wide representation for those OMs.

8/13/2019 70571738-411-2133-525-06-12

28/950


411-2133-525 Standard 06.12 April 2008

For example, the FSCHLinkSetupAttempts_2X OM is an EBID-based OMthat exists on both ESEL and DSFP cards. Since the ESEL and DSFP cardsare pooled system resources, the OM value of FSCHLinkSetupAttempts_2Xfor a particular EBID may have contributions from more than one ESEL orDSFP card during any given collection period. Therefore, the OM value forFSCHLinkSetupAttempts_2X for a particular EBID is a sum of pegs at allESEL and DSFP cards. Similarly, the per-IP-based OMs that are pegged atthe PCU and the PCUFP cards are also summed up for a particular IP addressand a single value is provided in the OM report. This functionality is thedefault behavior of the OM parser. The OM parser can also be run in non-accumulation mode as described below.

The specifics of OM uploading, processing, and file location are slightlydifferent depending on whether the subsystem is part of the EBSC, BSC, orBTS platform as described below.

EBSC-specific OM upload processFor C-EMS managed subsystems such as CPDS, the collection agents (forexample, the DSFP card for ACPs) are responsible for pegging and collectingOMs. Every 30 minutes, these binary files are transferred to the C-EMS usingFTP and placed in the C-EMS /opt/cems/log/OMBinary directory. The binaryfiles have a format similar to SBS binary files.

The EBSC OMs are collected over 30 minute intervals starting and ending onthe hour or half hour (for example, 16:00:00 or 16:30:00) and then uploadedto the C-EMS.

BSC-specific OM upload processFor the BSC subsystem, the OMs are pegged, collected, and sent to the BSSMthrough an event trigger. As of NBSS 12.0, the BSC (SBS) OM uploadsystem is enhanced so that the OM data is directly uploaded from thesubsystems (ESEL, PCU) to the BSSM. The uploaded event report is saved in

binary format on the BSSM in the /opt/bsm/log/OMBinary directory.

The BSC OMs are collected over 30 minute intervals starting and ending onthe hour or half hour (for example, 16:00:00 or 16:30:00) and subsequentlyuploaded to the BSSM.

BTS-specific OM upload process

For the BTS subsystem, the OMs are pegged, collected, and sent to the BSSMthrough an event trigger. The uploaded event report is saved in binary formaton the BSSM in the /opt/bsm/log/OMBinary directory. The OMs pegged atthe BTS cannot distinguish between events related to calls set up on the SBSor CDPS.

8/13/2019 70571738-411-2133-525-06-12

29/950



The BTS OMs are collected over 30 minute intervals starting and ending onthe hour or half hour (for example, 16:00:00 or 16:30:00) and subsequentlyuploaded to the BSSM.

OM parsingIn the case of deployment with C-EMS and BSSM, the default behavior of theOM parser is to process the binary files under both the /opt/cems/log/OMBinary and /opt/bsm/log/OMBinary directories. The output files from theOM parser are raw ASCII text files.

C-EMS provides the capability to configure the OM parsing time (forexample, when the OM parser is run to generate the ASCII files).

The OM parser can be run in different modes. Two of these modes arediscussed below. For more information about running the OM parser, see

Nortel CDMA C-EMS Fault Management (NN20000-144) .

OM parser accumulation mode (default)

When the OM parser runs under the default mode, it generates the followingfiles:

CPDS-, which contains the node-based CPDS OMs listedfor each ACP, CAC, and PCU

CSVS-, which contains the node-based CSVS OMs listedfor each ACP, CAC, and PCU

Resource Management-, which contains the node-based

resource management OMs for the NRM, CSRM, SDRM, and SBSRM SBSCSubsystem-, which contains the node-based SBS OMs

listed for each ESEL and PCU.

MCBTSSubsystem-, which contains the node-based BTSOMs listed by BTS MO (for example, the BTSCallProcessing MO andthe AdvancedFA MO).

BSC-, which contains the non-node-based consolidated (forexample, summed) OMs such as EBID, Multi-ID, and IP-based OMsfrom both BSC and EBSC nodes. For example, per carrier-sector OMsthat peg for a given carrier sector on both the CSVS, CPDS, and SBS will

result in one single summed up value for those particular OMs.The node based CPDS/CSVS/resource management- files arestored in the /opt/cems/log directory while the SBSCSubsystem-, MCBTSSubsystem-, and BSC- filesare stored in the /opt/bsm/log directory.

8/13/2019 70571738-411-2133-525-06-12

30/950


411-2133-525 Standard 06.12 April 2008

OM parser no accumulation mode

The OM parser can also be run manually with a non-accumulation option. Byspecifying this option, the OM parser will not accumulate (for example, add)any EBID and IP OM values together. Instead, it will print out the OM valuesexactly as they were found in the binary files. Therefore, all OMs will bedisplayed only on a per-node and per-card basis.

When the OM parser runs under this mode, it generates the following files: CPDS- and CSVS-, which contains the node-

based, IP-based, and EBID-based CPDS and CSVS OMs listed for eachACP, CAC, and PCU

Resource Management-, which contains OMs at the CNFP

SBSCSubsystem-, which contains the node-based, IP-based,and EBID-based BSC OMs listed for each ESEL and PCU

MCBTSSubsystem-, which contains the node-based BTSOMs listed by the BTS MO (for example, the BTSCallProcessing MOand the AdvancedFA MO)

When the OM parser is run with the non-accumulation option, the node,interface and some multi-ID-based OMs for CSVS, CPDS, and SBS are nolonger summed up. Instead, these OMs for CSVS and CPDS are included inthe CSVS/CPDS- file on a per-node basis along with the node-

based OMs. Similarly, these SBS OMs are included in the SBSCSubsystem- file along with the node-based OMs.

OM metrics overview 1The OMs collected by the DMS-MTX, BSC, EBSC, and BTS make it possible to define and implement performance-related metrics. Thisdocument contains informaiton about metrics that help customers monitorand improve the performance of their wireless systems.

These metrics are useful because: measurements are pieces of data reporting a value that concerns a

particular function or event

metrics are pieces of information, derived from one or moremeasurements, providing a view of system performance

useful metrics have a specific purpose that relate to customer need and are benchmarked to establish norms.

metrics are used for preventative actions rather than for debugging oranalysis after-the-fact or for the measurement of abnormal events.

8/13/2019 70571738-411-2133-525-06-12

31/950



if possible, metrics have a mechanism (formula) in place to guaranteetheir validity (for example, total number of packets received = totaldropped packets + total long packets + total short packets)

OM validation overview 1Where possible, formulas are provided at the end of each major section orchapter to allow the validation of related OMs. The basic formula used is:

Attempts = Successes + Non-Successes

Validation formulas provide confidence that the system is capturing eventscorrectly.

Since OMs are collected during specific intervals, it is possible for relatedOMs to span one or more OM collection periods. This may cause a slightdiscrepancy in any of the validation formulas described in this document. For

example, an attempt OM for a particular event may be captured at the end ofone OM period while the success or non-success of that same event may becaptured at the beginning of the next OM period. Therefore it isrecommended that, where possible, the validation formulas be used with OMscollected over a 24 hour period in order to minimize the effect of thesediscrepancies.

8/13/2019 70571738-411-2133-525-06-12

32/950


411-2133-525 Standard 06.12 April 2008

8/13/2019 70571738-411-2133-525-06-12

33/950

2-1Nortel Networks Copyright 2008 Nortel Networks


Call setup performance 2Call setup performance reflects how well the system is accepting originations,terminations, and hard handoff attempts from other CDMA cells.

There are three different stages when a call may fail:1. Before the resources are allocated (blocked Calls). This can occur during

the setup of a new origination, termination, or hard handoff target, orduring a resource allocation attempt for a queued WPS (wireless priorityservice (WPS) call.

2. When the mobile is moving from the common channel to the trafficchannel (access failures)

3. After the mobile is on the traffic channel.

Basically, the subscriber does not perceive the difference between the call(origination) failing due to no resources or due to poor RF performance.However, to the service provider, they are two separate problems: one

problem of improper provisioning and the other problem of RF engineeringor possible problems with the subscribers mobile unit.

For more information about item 1, see Call setup failure before resources areallocated (blocked calls) (page 2-10) .

For more information about item 2, where the base station is unable to receivetraffic from the mobile on the reverse traffic link, see Call setup failures dueto RF failures (page 2-18) .

For more information about item 3, see Dropped call performance (page 6-1) .

This chapter contains 3G packet data call setup metrics. For packet data calls,the call may set up successfully but the bursts may still fail. The metrics forthe packet data scenarios, including SCH burst setups, are listed in 1xRTT

packet data performance (page 3-1) .

List o f OMs 2The following list contains the MSC, BSC, and BTS OMs that are relevant tothis chapter.

8/13/2019 70571738-411-2133-525-06-12

34/950

8/13/2019 70571738-411-2133-525-06-12

35/950

Call setup performance 2-3Nortel Networks Copyright 2008 Nortel Networks


CAUST3D2 OM group

CAURELSI PDSEFLDS PDSEFLAS

EBPBCPOM OM group

ESBSRASU ECSVRASU ESBESWFL ECSESWFL

ESBNRSFL ECSNRSFL ESBERLFL ECSERLFL

ESBSCSS ECSVCSS

BAMCPSCT OM group

BAMOATTS BAMOSUCC BAMPGRES BAMTSUCC

BAMERLFL BAMEDLOT BAMWPSRT MCPCOBAM

MCPCTBAM

CAUCPSYS OM group

CAUORIGS CAUREGNS CAUHOSRC CAUHOTRG

CAUCNICV CAUCNITR CAUTMWNA CAUTMWNC

CAUTMWNR CAUFLASH CAUMRLS CAULRLS

CAUCPFRQ OM group

MCTORIGS MCTOATTS MCTOSUCC MCTPGRES

MCTTATTS MCTTSUCC MCTHCATT MCTHATTS

MCTHSUCC MCTHRLFL MCTERSFL MCTNOTCE

MCTNOWCD MCTNOFOF MCTFWCAP MCTBTSBK

MCTERLFL MCTAREQT MCTAREQN MCTARQFN

MCTDROPR

CAUFRQ3V OM group

Call setup perfo rmance OMs

8/13/2019 70571738-411-2133-525-06-12

36/950

2-4 Call setup performanceNortel Networks Copyright 2008 Nortel Networks

411-2133-525 Standard 06.12 April 2008

This OM group has the same OM registers as the CAUCPFRQ OM group as listed above.

CAUFRQ3D OM group

This OM group has the same OM registers as the CAUCPFRQ OM group as listed above.

BAMCPFRQ OM group

BAMSCSAT BAMSCSFL BAMSBSAT BAMSBSFL

CAUXTFRQ OM group

NMCTATTS NMCTBLKS MCTPRRO MCTPRRT

MCTPRST MCTPRSO MPRBLKS MPRSUCC

MPRFL MRETATTS MRETHATT MRETBLKS

MRETHBLK MRETSUCC MRETHSUC MRETFL

MRETHFL

CAUXTF3V OM group

This OM group has the same OM registers as the CAUXTFRQ OM group listed above.

CAUXTF3D OM group

This OM group has the same OM registers as the CAUXTFRQ OM group listed above.

BSCRM OM group

RMUIATOV RMUIANRV RMUIOENV RMURARV

RMURATOV RMURANRV RMURAOEV RMUIATOD

RMUIANRD RMUIOEND RMURARD RMURATOD

RMURANRD RMURAOED


8/13/2019 70571738-411-2133-525-06-12

37/950



BSCRM2 OM group

RMUIRDS RMUINRDS RMUITODS RMUIOEDS

RMURRDS RMURNRDS RMURTODS RMUROEDS

EBSCRM OM group

NRMARV NRMANRV NRMOEV NRMATOV

NRMOLRV NRMSTOV NRMARPD NRMANRPD

NRMOEPD NRMOLRPD NRMSTOPD NRMARDS

NRMANRDS NRMAOEDS NRMATODS NRMOLRDS

NRMSTODS

CAUMISC OM group

CAUUNSO RMUUNSO NRMUNSO FLEVR13K

CDMAIVSN OM group

ONILDNY ODENYCAU ODENYCM TDENYCAU

CDMAPDOM OM group

MIDTOAAT MIDTOASU MIDTOAFL NIDTOAAT

NIDTOASU NIDTOAFL NULTOAAT NULTOASU

NULTOAFL MIDTOAAX MIDTOASX NIFLNVLR

NIFLMINA NIFLPGTM NIFLPGNG NIFLVCLL

NIFLSRSP NIFLCLFL NIFLMRLS NIFLAMPS

MSREGNOT MIDTOAFX NIDTOAAX NIDTOASX

NIDTOAFX NULTOAAX NULTOASX NULTOAFX

NIFLNSOP


8/13/2019 70571738-411-2133-525-06-12

38/950


411-2133-525 Standard 06.12 April 2008

CDSNMQRY OM group

FLTCEVR FLTCI13K FLTCB13K 3GFLTEV

3GFLI13K 3GFLB13K

MTXPDSCT OM group

NWKFLBS NWKFLAS NARLPFL DARLPFL

AHRLPFL

MTXPDSYS OM group

NARPFLBS DARPFLBS AHRPFLBS NARPFLAS

DARPFLAS AHRPFLAS DHORPFL

MTXSYS1 OM group

CDMAPRS1 CDMAPRS2 TDENYCM

MTXSYS2 OM group

GECRCVD GECATTS GECSUCC MEIDQRCC

MEIDQSCC MEIDQRTC MEIDQSTC MEIDATTS

ESNATTS

OMMTX OM group

MBORIGS

OMMTXSYS OM group

TWCSTART

OMMTX2 OM group


8/13/2019 70571738-411-2133-525-06-12

39/950



VPADIC

OMMTX3 OM group

SRTDBORG SRTDBO2G SRTDBO3V SRTDBO3D

SLNTRTAF SLNTRT2G SLNTRT3V SLNTRT3D

OMMTXSY2 OM group

VPADATT VPADSUC VPADFL

TRMTRS OM group

TRSGNCT

WPSOM1 OM group

WQTOUT WQOVFL WINVALDQ

BSC OMs

RLP Setup OM group

RLPSetupAttempts RLPSetupSuccesses RLPSetupFailures

Packet Session Signaling OM group

TotalSessionSetupInitialAttempts

TotalSessionSetupReconnectAttempts

TotalSessionSetupSuccess TotalSessionSetupFailur es

TotalInitialRPSessionSetupFailures

TotalRPSessionHandoffFailures

TotalReleasesBeforeInitialSessionSetup

TotalReleasesBeforeHandoffSessionSetup

Packet Session Data OM group


8/13/2019 70571738-411-2133-525-06-12

40/950

8/13/2019 70571738-411-2133-525-06-12

41/950



PCU Manager OM group

DormantToActiveHandoffs DormantHandoffRequests PCU_AllocRequests PCU_AllocFailures

PCU_AllocSuccessful IMSI_TableFull

RP Session L2TP OM group

ReliablePacketSentSuccess ReliablePacketReTransmitted

ReliablePacketReceived NumberOfTunnelFailures

TotalUnreliableBytesTransmitted

TotalUnreliableBytesReceived

RP_SessionSetupAttempts RP_SessionSetupSuccesses

RP_SessionSetupRejectReasonGenErr

RP_SessionSetupRejectReasonNoCarrier

RP_SessionSetupRejectReasonAdminReason

RP_SessionSetupRejectReasonNoTempRsrcs

RP_SessionSetupRejectReasonNoPermRsrcs

RP_SessionSetupRejectReasonSysOverload

RP_SessionSetupRejectReasonOther

RP_SessionSetupRejectReasonNoPDSNRsp

BTS OMs

Advanced Sector MO

FchOriginationNonBlocking3GDowngrade2G

FchOriginationNonBlocking3GDowngrade2GNoAcn

FchOriginationNonBlocking3GDowngrade2GNoBcn

BlockedFchOriginations2G[6]: CFDS RadioConfig State

BlockedFchOriginations3GVoice[6]: CFDS RadioConfig State

BlockedFchOriginations3GData[6]: CFDS RadioConfig State


8/13/2019 70571738-411-2133-525-06-12

42/950


411-2133-525 Standard 06.12 April 2008

Call setup failure before resources are allocated (blocked calls) 2Call setup failures before resources are allocated are network-related call setupfailures and can be classified as follows:1. Screened calls (call setup interrupted for reasons such as un-authenticated

mobile, mobile-initiated release, land-side release, and denials due tounsupported Service Options)

2. Call setup failure due to lack of physical resources

3. Call setup failure due to time-outs and software faults

Network resources are defined as the following switching resources involvedin the call: terrestrial trunks (SBS to DTC trunks)

SBS selector elements

BTS traffic channel elements.

non-availability of excess RF capacity.

non-availability of Walsh codes

PDSN

PCU

Goal Less than x% of all originations attempted failed due to resource

shortages.

Less than y% of all terminations attempted failed due to resourceshortages.

Less than z% of all hard handoffs attempted to CDMA cells are failed dueto resource shortages.

The variables above ( x, y, and z) are defined in accordance with the service providers planned grade of service. It is improper to provision the system(for example, x + y + z) for 2% blocking and then set the goal for anythingother than 2%.

Formula usageThe Boolean field OM3G in table CDMAPART is an indicator of whether theOMs for 3G voice calls and 3G data calls are to be kept separate from theOMs for 2G calls. The OM groups CAUSCT3V, CAUSCT3D, CAUFRQ3V,CAUFRQ3D, CAUXTF3V, CAUXTF3D maintain 3G voice and 3G dataOM counts for a particular sector only if OM3G is set to Y. If a particularsector is 3G-capable but OM3G is set to N, the 3G voice and 3G data OMcounts are combined with the 2G OMs in the CAUCPSCT, CAUCPFRQ andCAUXTFRQ OM groups.

8/13/2019 70571738-411-2133-525-06-12

43/950



Impact of OM3G Boolean on OM registers i n certain OM groups

OM3G

Boolean

Impact on

CAUCPSCT,CAUCPFRQ, andCAUXTFRQ OMgroups

Impact on

CAUSCT3V,CAUFRQ3V, andCAUXTF3V OMgroups

Impact on

CAUSCT3D,CAUFRQ3D, andCAUXTF3D OMgroups

Y The registers in theseOM groups get peggedonly for events relatedto 2G voice and CSDcalls

The registers in theseOM groups get peggedonly for events relatedto 3G voice and CSDcalls

The registers in theseOM groups get peggedonly for events relatedto 3G data calls

N The registers in theseOM groups get pegged

for all call-relatedevents (3G voice &CSD, 3G data, and 2Gvoice and CSD calls)

The registers in theseOM groups do not get

pegged. The related 3Gvoice and CSD call-specific events will becaptured inCAUCPSCT,CAUCPFRQ, andCAUXTFRQ OMgroups along with 3Gdata and 2Gcall-related events.

The registers in theseOM groups do not get

pegged. The related 3Gdata call-specificevents will be capturedin CAUCPSCT,CAUCPFRQ, andCAUXTFRQ OMgroups along with 3Gvoice and 2Gcall-related events.

Impact of OM3G Boolean on OM registers in t he new OM groups

OM3G

Boolean

Impact on

CAUSCT2 OMgroup

Impact on

CAUST3V2 OMgroup

Impact on

CAUST3D2 OMgroup

Y The registers in thisOM group get peggedonly fr events related to2G voice and CSDcalls

The registers in thisOM group get peggedonly for events relatedto 3G voice and CSDcalls

The registers in thisOM group get peggedonly for events relatedto 3G packet data calls

N The registers in thisOM group get peggedfor 2G, 3G voice, andCSD related calls.

The 3G packet dataOMs do not haveregisters that can be

pegged here.

The registers in thisOM group do not get

pegged. The 3G voiceand CSD call relatedevents will be capturedin CAUSCT2 OMgroup.

The registers in thisOM group do not get

pegged.

8/13/2019 70571738-411-2133-525-06-12

44/950


411-2133-525 Standard 06.12 April 2008

The attempts in the following sections refer to those calls that the system isaware of and attempts to setup resources for. For example, the system is notaware of origination call attempts that exhaust the access probes since theorigination message is lost and, therefore, is not received by the BTS.

Similarly, the system does not count termination call attempts if the pagetimed out without receiving a response, since the system does not attempt toset up resources. Attempts to allocate resources for WPS calls that are queuedare considered a call setup attempt, since the origination for the call originallyresulted in a block (the call is then queued). WPS calls can be either 2G or 3Gvoice only.

Total calls attempted The following formula will be used (and will be referred to) throughout thechapter.

Total calls attempted =

(CAUOATTS + CAUPGRES + CAUHATTS + WPSRETRY +WPSTRTRY ) for all sectors - (MCTPRSO + MCTPRST) for allfrequencies for all MCTA sectors +/-FchOriginationNonBlocking3GDowngrade2G +/-FchOriginationNonBlocking3GDowngrade2GNoAcn +/-FchOriginationNonBlocking3GDowngrade2GNoBcn for all sectors.

The MCTPRSO and MCTPRST OMs are subtracted in the above formulaaccounting for the origination or termination attempts that get redirected byMCTA to the alternate CDMA band resulting in CAUOATTS or CAUPGRES OM being pegged twice in those events. It is also important to note that theabove formula evaluates the metric on a per system wide basis. However,when the metric is to be evaluated on a per sector basis, the MCTPRSO andMCTPRST OMs in the above formula are replaced with MCTPRRO andMCTPRRT OMs respectively.

The FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn BTSOMs are pegged when the BTS runs out of XCEM resources but still hasCEM resources and all other needed resources to be set up for the call as a 2Gvoice call rather than a 3G voice call as requested by the mobile. These BTSOMs are included in the above metric as well as other metrics later on in thischapter for the following reason: When a mobile attempts to make a 3G voicecall, the attempt is pegged in CAUSCT3V OM group, but if the call isdowngraded to 2G as described above, then the subsequent events for that call(i.e. success or access failure,...etc.) are pegged in CAUCPSCT OM group.Therefore, when evaluating certain metrics on a per call type basis (i.e. 2Gversus 3G voice), the BTS OMsFchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn are addedto the 2G attempts and subtracted from the 3G attempts as stated below.

8/13/2019 70571738-411-2133-525-06-12

45/950



The WPSRETRY and WPSTRTRY OMs only apply to voice and circuitswitched data calls. There is no WPS service for packet data calls. For packetdata only metrics, do not include these two OMs in the Total CallsAttempted term.

Call typesThe following sections will be referred to throughout the chapter in order toevaluate the metrics based on call types (2G Voice, 3G Voice, Voice Calls,PD Calls and For all Call types together)

For 2G voice callsFor 2G calls, use the OMs from the OM groups CAUCPSCT, CAUSCT2 andCAUXTFRQ in the formula and add the value of the BTS OMsFchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in theformula.

For non-3G enabled systems, the BTS OMsFchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in theabove formula are not applicable and are not pegged.

For 3G voice callsFor 3G Voice calls, use the OMs from OM groups CAUSCT3V, CAUST3V2and CAUXTF3V in the formula and subtract the value of the BTS OMsFchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in theformula.

For voice calls

For Voice calls use the OMs from OM groups CAUCPSCT, CAUSCT2,CAUSCT3V, CAUST3V2 (and from OM groups CAUXTFRQ,CAUXTF3V, CAUXTF3D) in the formula, but the BTS OMsFchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in theformula are not applicable since the value is already included in the otherOMs.

For 3G packet data callsFor 3G Packet Data calls, use the OMs from OM groups CAUSCT3D,CAUST3D2 and CAUXTF3D in the formula, but the BTS OMsFchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in the above formula are not applicable for packet data calls .

For all call typesFor all call types together, use the sum of the OMs from OM groupsCAUCPSCT, CAUSCT2, CAUSCT3V, CAUST3V2, CAUSCT3D andCAUST3D2 (and from OM groups CAUXTFRQ, CAUXTF3V,CAUXTF3D) in the formula, but the BTS OMs

8/13/2019 70571738-411-2133-525-06-12

46/950


411-2133-525 Standard 06.12 April 2008

FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in the formula are notapplicable since the value is already included in the other OMs.

Overall call setup failures (call blocking r ate) 2

(CAUOBLKS + CAUTBLKS + CAUHBLKS) all sectors / Totalcalls attempted x 100

For more information about how to use the above metric based on call type(2G Voice, 3G Voice or 3G Packet data calls), see Call types (page -13)

Call setup failures (blocks) due to lack of EBSC/BSC resourcesThis metric indicates the shortage of the resources for Voice, Packet Data andData Delivery Services (SMS, OTAPA, LCS). This metric indicates thatresources are not available for the call during resource allocation request

phase. This situation may be improved by provisioning BSC/EBSC additionalresources.

System where NRM is resource manager

Voice call setup failures (blocks)( NRMANRV for all CAUs / Total calls attempted )x 100

Packet data call setup failures (blocks)( NRMANRPD for all CAUs / Total calls attempted )x 100

Data delivery services (SMS, OTAPA, LCS) call setup failures (blocks)( NRMANRDS for all CAUs / NRMARDS for all CAUs) x 100

All (voice and packet data) call setup failures (blocks)( (NRMANRV + NRMANRPD) for all CAUs / Total callsattempted ) x 100

Failures combined for Voice, Packet data and Data Delivery services togethercan also be derived.

System where RMU is resource manager

Voice call setup failures (blocks)( (RMURANRV + RMUIANRV - RMURARV) for all CAUs /Total calls attempted ) x 100

Packet data call setup failures (blocks)( (RMURANRD + RMUIANRD - RMURARD) for all CAUs /Total calls attempted ) x 100

Data delivery services (SMS, OTAPA, LCS) call setup failures (blocks)( (RMURNRDS + RMUINRDS - RMURRDS) for all CAUs / RMUIRDS for all CAUs) x 100

8/13/2019 70571738-411-2133-525-06-12

47/950



All (voice and packet data) call setup failures (blocks)( (RMURANRV + RMUIANRV - RMURARV + RMURANRD +RMUIANRD - RMURARD) for all CAUs / Total calls attempted ) x100


Call s etup failures due to BSC/EBSC processing errorsThis metric is useful in determining the blocks due to certain processingerrors such as time outs or internal errors occurring during the resourceallocation phase. Blocking of calls due to such error conditions is typicallyrare and is not due to shortage of resources.

System where NRM is resource manager

Voice call setup failures( (NRMATOV + NRMOEV + NRMOLRV + NRMSTOV ) for allCAUs + CAUESWFL for all sectors / Total calls attempted ) x 100

Packet data call setup failures( (NRMATOPD + NRMOEPD + NRMOLRPD + NRMSTOPD ) forall CAUs + CAUESWFL for all sectors / Total calls attempted ) x 100

Data delivery services (SMS, OTAPA, LCS) call setup failures( (NRMATODS + NRMOEDS + NRMOLRDS + NRMSTODS ) forall CAUs / NRMARDS for all CAUs) x 100

All (voice and packet data) call setup failures

( (NRMATOV + NRMOEV + NRMOLRV + NRMSTOV +NRMATOPD + NRMOEPD + NRMOLRPD + NRMSTOPD ) for allCAUs + CAUESWFL for all sectors / Total calls attempted ) x100


System where RMU is resource manager

Voice call setup failures( (RMUIATOV + RMURATOV + RMUIOENV + RMURAOEV )for all CAUs + CAUESWFL for all sectors / Total calls attempted ) x100

Packet data call setup failures( (RMUIATOD + RMURATOD + RMUIOEND + RMURAOED )for all CAUs + CAUESWFL for all sectors / Total calls attempted ) x100

8/13/2019 70571738-411-2133-525-06-12

48/950

8/13/2019 70571738-411-2133-525-06-12

49/950



For more information about how to use the above metrics based on call type(2G Voice, 3G Voice or 3G Packet data calls), see Call types (page -13) . Usethe appropriate BlockedFchOriginations*[6] OM based on the call type (2GVoice, 3G Voice or 3G Packet data calls).

3G packet data call setup failures (blocks)3G Packet Data Call setup failures (blocks) due to RP session setup failuresduring null to active transition of a packet data call before service connectcompletion can be expressed as:

( NARPFLBS for all sectors ) / ( CAUOATTS for all sectors -MIDTOAAT - MCTPRSO for all frequencies for all MCTA sectors))x100

3G Packet Data Call setup failures (blocks) due to RP session setup failuresduring dormant to active transition of a packet data call before service

connect completion can be expressed as:( DARPFLBS for all sectors ) / (MIDTOAAT + NIDTOAAT ) x100

3G Packet Data Call setup failures (blocks) due to RP session setup failuresduring active handoff of a packet data call before service connect completioncan be expressed as:

( AHRPFLBS for all sectors ) / ( CAUHATTS for all sectors) x100In the above formula use the sum of each CAU* OMs from the CAUSCT3D ,CAUXTF3D and CDMAPDOM OM groups. The MCTPRSO OM issubtracted in the above formula to account for the origination attempts that

are redirected by MCTA to the alternate CDMA band resulting inCAUOATTS being pegged twice in this event. It is also important to notethat the above formula evaluates the metric on a per system wide basis.However, when the metric is to be evaluated on a per sector basis,MCTPRSO in the above formula is replaced with MCTPRRO .

Screened callsFor voice calls

((CAUORLS + CAUTRLS + CAUHRLS + CAUORODR +MISCFLT) all sectors - (WQTOUT + WQOVFL + WINVALDQ) /Total calls attempted ) x 100

For more information about the OM groups to use in the above formula,see For voice calls (page -13) .

For packet data calls((CAUORLS + CAUTRLS + CAUHRLS + CAUORODR) all sectors

/ (CAUOATTS + CAUPGRES + CAUHATTS) for all sectors-(MCTPRSO + MCTPRST) for all frequencies for all MCTA sectors))x100

8/13/2019 70571738-411-2133-525-06-12

50/950

8/13/2019 70571738-411-2133-525-06-12

51/950



This section also provides the following per-frequency RF access failuremetrics for FCCCH channel:

Origination and Termination RF access failures for same band selected

Origination and Termination RF access failures for same frequencyselected

Goal Less than x% of all originations and terminations attempted failed due to

RF Access Failure.

Less than y% of all hard handoffs attempted to CDMA cells are failed dueto RF Access Failure.

FormulasFollowing are the per sector RF access failure metrics:

Overall RF access failuresThis metric provides the combined RF access failure for originations &terminations on the common channels and Hard Handoffs.

( (CAUERLFL + CAUHRLFL) for all sectors / Total callsattempted ) x 100

Origination and termination RF access failure on commonchannels

( CAUERLFL for all sectors / (CAUOATTS + CAUPGRES +WPSRETRY + WPSTRTRY) for all sectors- (MCTPRSO +MCTPRST) for all frequencies for all MCTA sectors) x 100

Hard handoff (HHO) RF access failure( CAUHRLFL for all sectors / CAUHATTS for all sectors) x 100

The above formula evaluates the metric on a per system wide basis. However,when the metric is to be evaluated on a per sector basis, the CAUHATTSOM in the above formula is replaced with the CAUHINIT OM.

For more information about how to use the above metrics based on call type(2G Voice, 3G Voice or 3G Packet data calls), see Call types (page -13) .

The RF access failures on FCCCH channel can be compared with the RFaccess failures on the paging channel to assess the performance of FCCCHchannel in comparison with the paging channel.

Origination and termination RF access failure on FCCCH channelSince BAM OMs peg for all 2G, 3GVoice and 3GData calls combined, themetric below provides the combined RF access failure for all calls on theFCCCH channel.

8/13/2019 70571738-411-2133-525-06-12

52/950


411-2133-525 Standard 06.12 April 2008

BAMERLFL for all sectors / ((BAMOATTS + BAMPGRES +BAMWPSRT )for all sectors - ( MCPCOBAM + MCPCTBAM )) for allfrequencies for all MCTA sectors) x 100

Origination and t ermination RF access failure on paging channel

(CAUERLFL - BAMERLFL ) for all sectors / ((CAUOATTS +CAUPGRES + WPSRETRY + WPSTRTRY - BAMOATTS -BAMPGRES - BAMWPSRT ) for all sectors - ( MCTPRSO +MCTPRST - MCPCOBAM - MCPCTBAM )) for all frequencies for allMCTA sectors) x 100

All CAU* OMs, WPSRETRY, WPSTRTRY and MCT* OMs in the aboveformula for paging channel represent the summation of all correspondingOMs from 2G voice, 3G voice and 3G data OM groups. This is because theBAM channel OMs peg for all call types combined.

If MCTA feature is turned on, the resources for a call may be set up on the

same frequency, a different frequency on the same band or a differentfrequency on a different band. Following metrics provide the per frequencyRF access failures for FCCCH channel. These metrics should not becompared to the per frequency RF access failures presented in the MCTAchapter since the pegging behavior of these OMs is different.

Origination and termination RF access failure for same bandselectedThis metric provides the breakdown of the sector wide RF Access failure rateon the FCCCH channel on a per frequency basis. This metric is useful in

pointing to a particular frequency issue rather than a sector wide issue.

(BAMSBSFL / BAMSBSAT ) for a given frequency x 100Origination and termination RF access failure for same frequencyselectedThis metric provides the RF access failure rate for calls that originated on afrequency and were set up on the same frequency. If the number of carrierredirections are low, then the metric below can be used to derive and comparethe RF access failure rate on paging channel with the RF access failure rate ofFCCCH channel.

(BAMSCSFL / BAMSCSAT ) for a given frequency x 100

Voice call failu res during setup due to non-RF resource failures 2

Call failures during setup due to non-RF resource failures are classified asfollows:1. Non-RF resource failure during origination/termination

2. Non-RF resource failure during Hard Handoff.

8/13/2019 70571738-411-2133-525-06-12

53/950



FormulasOverall RF access failures

( (NORFSEFL + NRFSEFHH) for all sectors / Total callsattempted ) x 100

Origination and termination RF access failure

( NORFSEFL for all sectors / (CAUOATTS + CAUPGRES +WPSRETRY + WPSTRTRY) for all sectors- (MCTPRSO +MCTPRST) for all freq;MCTA sectors) x 100

Hard handoff (HHO) RF access failure

( NRFSEFHH for all sectors / CAUHATTS for all sectors) x 100The above formula evaluates the metric on a per system wide basis. However,when the metric is to be evaluated on a per sector basis, the CAUHATTSOM in the above formula is replaced with the CAUHINIT OM.

For more information about how to use the above metrics based on call type(2G Voice or 3G Voice), see Call types (page -13) .

Miscellaneous packet data call failuresFor packet data call setup during origination, BSC resources are setup firstfollowed by BTS resources and then R-P session is setup between PCU andPDSN. Mobile could successfully arrive on the traffic channel but the R-Psession setup could fail due to lack of PDSN resources. This failure maybereported at the CAU by the BSC/PCU after CAUOSUCC OM is peggedresulting in a call failure. For null-to-active scenario NARPFLAS OM gets

pegged. The OMs captures RLP failures between mobile and PCU are pegged

after RP session is setup.

3G packet data call failures (after call setup) due to RP sessionfailures during null t o active transition of a packet data call

( NARPFLAS for all sectors) / CAUOATTS for all sectors -MIDTOAAT - MCTPRSO for all frequencies for all MCTA sectors)x100

3G packet data call failures (after call setup) due to RP sessionfailures during dormant to active transit ion of a packet data call

( DARPFLAS for all sectors) / (MIDTOAAT + NIDTOAAT ) x100

3G packet data call failures (after call setup) due to RP sessionfailures dur ing active handoff of a packet data call

( AHRPFLAS for all sectors) / ( CAUHATTS for all sectors) x100In the above formula use the sum of each CAU* OMs from the CAUSCT3D ,CAUXTF3D and CDMAPDOM OM groups. The MCTPRSO OM issubtracted in the above formula to account for the origination attempt that is

8/13/2019 70571738-411-2133-525-06-12

54/950


411-2133-525 Standard 06.12 April 2008

redirected by MCTA to the alternate CDMA band resulting in CAUOATTS being pegged twice in that event. It is also important to note that the aboveformula evaluates the metric on a per system wide basis. However, when themetric is to be evaluated on a per sector basis, MCTPRSO in the aboveformula is replaced with MCTPRRO .

3G packet data call failures (after call setup) due to RLP failuresduring null t o active transition of a packet data call

NARLPFL / ( CAUOATTS for all sectors - MIDTOAAT - MCTPRSO for all frequencies for all MCTA sectors) x100

3G packet data call failures (after call setup) due to RLP failuresduring dormant to active transition of a packet data call

DARLPFL / (MIDTOAAT + NIDTOAAT ) x1003G packet data call failures (after call setup) due to RLP failuresduring active handoff of a packet data call

AHRLPFL / ( CAUHATTS for all sectors) x100

Addit ional formulas 2Voice call setup performance metrics on a per platform basis- (EBSC andBSC)

These metric formulas measure the call setup failures and successes afterresources have been successfully allocated on the EBSC (CSVS) and BSC(SBS) platforms. Call setup failures due to network related and RF relatedfailures can be measured using these metrics.

It is important to note that these metrics are only valid when NRM is thecentral resource manager in the system.

Call setup failures due to network related failures

Network related failures are

Failures due to processing errors during communication between CAUand the selector element after successful resource allocation and beforethe radio link setup phase.

Failures due to processing errors at the selector element duringcommunication between CAU and EBSC after successful radio link setupand before successful call setup.

Percentage of call setup failures due to processing errorsCall failures due to processing errors include CAU time-outs, softwarefailures and resource mismatches at the selector element. Resource

8/13/2019 70571738-411-2133-525-06-12

55/950



availability status mismatch means that a resource is reserved for allocation by the NRM but is unavailable during CAU call setup request.

on CSVS

( ECSESWFL for all CAUs / ECSVRASU for all CAUs) x 100on SBS

( ESBESWFL for all CAUs / ESBSRASU for all CAUs) x 100Percentage of call setup failures due to non-RF failures

Non-RF failures include internal failures at the BSC like DSP initializationfailures etc.

on CSVS( ECSNRSFL for all CAUs / ECSVRASU for all CAUs) x 100

on SBS

( ESBNRSFL for all CAUs / ESBSRASU for all CAUs) x 100Call setup failures due to RF related failures

on CSVS( ECSERLFL for all CAUs / ECSVRASU for all CAUs) x 100

on SBS( ESBERLFL for all CAUs / ESBSRASU for all CAUs) x 100

Call setup successes

on CSVS( ECSVCSS for all CAUs / Total calls attempted ) x 100

on SBS( ESBSCSS for all CAUs / Total calls attempted ) x 100

MEID related metrics

The following metrics at the MTX measure the penetration of MEID andESN mobiles. They also track the number of MEID mobiles that do notrespond to the status request message from the CAU to retrieve the MEIDvalue. An MTXT139 log has been introduced at the MTX to track non-complaint mobiles i.e., mobiles that send an SCM bit 4 = 1 and ESN field =true ESN and SCM bit 4 = 0, ESN field = pESN.

Query to retrieve the MEID value of the mobile could fail due to the channelconditions, RF conditions or the mobile being unable to send the MEID in thestatus response message. To determine the root cause of the query failure, oneshould look at the Call Detail Records (CDRs) at the MTX to determine ifthis failure is related to mobiles that belong to particular manufacturer type.

8/13/2019 70571738-411-2133-525-06-12

56/950


411-2133-525 Standard 06.12 April 2008

It is also important to note that there are no separate OMs for query failures asthere no associated timers (no retries as a result) to track the query response.

Percentage of calls made by MEID mobiles

((MEIDATTS + MEIDATT2 * 65536) / Total calls attempted ) x 100

Percentage of calls made by ESN mobiles

((ESNATTS + ESNATT2 * 65536) / Total calls attempted ) x 100

Percentage of MEID query failures on the common channel

((MEIDQRCC - MEIDQSCC ) / MEIDQRCC ) x 100

Percentage of MEID query failures on the traffic channel

((MEIDQRTC - MEIDQSTC ) / MEIDQRTC ) x 100

The following metrics at the BSC measure the PLCM type (pESN, MEID,BS-Assigned) performance by tracking the PLCM collisions whenever thereis a call setup failure or a call drop due to RF related reasons. The existingCall Summary Log has been modified to include the PLCM EBID collision

bit map field, the PLCM type and the SCM. This will allow the customer totrack the carrier-sector information in event of PLCM collision.

These metrics help re-evaluate the choice of the PLCM type chosen for callsetup in the SelectorSubsystemMO;PlcmTypeConfig. Optimal selection of aPLCM type will help reduce the call setup failures and call drops due toPLCM collisions. For more information, see Nortel CDMA Performance

Management -- Operational Guidelines (411-2133-526).

For example, if ESN_Preferred is the chosen PLCM type at the BSC and ifthere are call failures (RF related) due to pESN collisions, changing thechoice of PLCM type to Allow_BS_Assigned or BS_Assigned_Preferredcould lower the call failures.

Percentage of call setup failures in the event of pESN PLCMcollisions(PLCM_CallSetupFailuresPseudoESN /PLCM_CallSetupAttemptsPsuedoESN ) x 100

Percentage of call setup failures in the event of MEID PLCMcollisions(PLCM_CallSetupFailuresMEID / PLCM_CallSetupAttemptsMEID) x100

8/13/2019 70571738-411-2133-525-06-12

57/950



Percentage of call setup failures in the event of BS-assignedPLCM collisions(PLCM_CallSetupFailuresBS_Assigned /PLCM_CallSetupAttemptsBS_Assigned) x 100

Percentage of call drops in the event of pESN PLCM collisions(PLCM_CallDropsPseudoESN / PLCM_CallSetupSuccessesPsuedoESN)x 100

Percentage of call drops in the event o f MEID PLCM collisions(PLCM_CallDropsMEID / PLCM_CallSetupSuccessesMEID ) x 100

Percentage of call drops in the event of BS-assigned PLCMcollisions(PLCM_CallDropsBS_Assigned /PLCM_CallSetupSuccessesBS_Assigned) x 100

Addi tional metrics

Percentage of RF setup failures in the event of PLCM collisions(PLCM_CallSetupFailuresPseudoESN +PLCM_CallSetupFailuresMEID +PLCM_CallSetupFailuresBS_Assigned) / (CAUERLFL + CAUHRFL)for all sectors) x 100

Percentage of RF setup failures (in the event of non col lision)when pESN is selected((PLCM_CallSetupAttemptsPsuedoESN-(PLCM_CallSetupFailuresPseudoESN +PLCM_CallSetupSuccessesPsuedoESN) /PLCM_CallSetupAttemptsPsuedoESN ) x 100

The above metric tracks RF setup failures when there are no pESN collisions.This metric can be used to compare with the overall RF failure metric at theMTX (values should fairly stay the same). This will ensure that a particularPLCM type will have no impact on the RF part of the call setup (need tocompare with metrics for other PLCM types). Similar metrics can be obtainedfor other PLCM types (MEID, BS_Assigned)

VPAD (voice preemption of active data) voice call setup performance -

system levelThe following formulas are related to the preemption of active packet datasessions by incoming voice calls due to the VPAD feature:

Overall active packet data call preemption due to VPAD featurePercentage of active packet data calls preempted by incoming voice callrequests due to the VPAD feature is expressed as

8/13/2019 70571738-411-2133-525-06-12

58/950


411-2133-525 Standard 06.12 April 2008

( VPADIC for all sectors / (CAUOSUCC + CAUTSUCC +CAUHSUCC) for all sectors) x 100

The CAU* OMs in the above formula are from OM group CAUSCT3D .Theabove metric may also be applied on a per cluster or per BSC basis.

Overall voice call setup failures related to VPAD featurePercentage of incoming voice setup requests that failed (for any reason, afterthe CM received a page response) during call setup is expressed as

(VPADFL / VPADATT ) x100

Global emergency call metricsWhen considering the GEC metrics that follow, it is important to rememberthat a GEC call is treated the same way as an ordinary mobile origination or3WC with the exception of digits translation. The MTX-CM must receive the

Origination or Flash with Information message in order for GEC digittranslation to take place.

GEC mobile user feature activationPercentage of GEC calls received by the CM is expressed by the following:

(GECRCVD / (MBORIGS + TWCSTART)) x 100Please refer to NTP 411-2131-814 for a description of OMMTX.MBORIGS and OMMTXSYS.TWCSTART .

GEC feature usagePercentage of received GEC calls that use the translation to the emergencyservices number datafilled in MTX_GLOBAL_EMERGENCY_DIGITS isexpressed by the following:

(GECATTS / GECRCVD) x 100If there are no digits datafilled in MTX_GLOBAL_EMERGENCY_DIGITS,then the value of this metric will be 0%. If digits are datafilled, it is expectedthat this metric should be 100%. If it is not, this indicates a translations orrouting issue.

GEC success ratePercentage of successful GEC calls is expressed by the following:

(GECSUCC / GECATTS) x 100The success rate of the GEC is dependent upon many different factors, not theleast of which is that the number datafilled in Table OFCVAR may or maynot be correct; there is no check made by the MTX that the number datafille

70571738-411-2133-525-06-12

Documents