411-2133-525_06.12

411-2133-525CDMA

Operational Measurements Reference System Performance MetricsNBSS15.0 Standard 06.12 April 2008

Whats inside...CDMA OM design overview Call setup performance 1xRTT packet data performance RLP throughput performance Access robustness package performance Dropped call performance Handoff performance Intelligent voice service negotiations performance BTS performance Paging performance Border paging performance Data burst message delivery performance Location services performance MCTA performance Authentication performance Call resource allocation and management RF performance

Whats inside...CDMA-LTX performance OTAPA performance Call flow diagrams with OMs MSC OM descriptions BSC OM descriptions BTS OM descriptions

CDMA

Operational Measurements Reference System Performance MetricsDocument number: 411-2133-525 Product release: NBSS15.0 Document version: Standard 06.12 Date: April 2008

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright 2008 Nortel Networks All Rights Reserved. Originated in the United States of AmericaThis document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel Networks, 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 as progress in engineering and manufacturing may warrant. * Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks.

iv Nortel Networks

Copyright 2008 Nortel Networks

411-2133-525

Standard

06.12

April 2008

Nortel Networks

v Copyright 2008 Nortel Networks

ContentsAbout this documentPurpose 3-xvii Audience 3-xviii Scope of document 3-xviii Organization 3-xviii Related documents 3-xix Indication of hypertext links 3-xx

13-xvii

New in this releaseFeatures 4-xxi Other changes 4-xxi

4-xxi

CDMA OM design overviewOM philosophy 1-1 MTX OM philosophy 1-1 CDMA access system OM philosophy 1-2 MTX OM consolidation 1-4 CDMA access system OM consolidation 1-5 OM metrics overview 1-8 OM validation overview 1-9

1-1

Call setup performance

2-1

List of OMs 2-1 Call setup failure before resources are allocated (blocked calls) 2-9 Goal 2-10 Formula usage 2-10 Total calls attempted 2-12 Call types 2-13 Overall call setup failures (call blocking rate) 2-14 Call setup failures (blocks) due to lack of EBSC/BSC resources 2-14 Call setup failures due to BSC/EBSC processing errors 2-15 Call setup failures (blocks) due to BTS physical resources 2-16 Call setup failures (blocks) due to BTS time-outs 2-16 3G packet data call setup failures (blocks) 2-17 Screened calls 2-17 Screened calls for 3G packet data calls due to mobile service inactive indication

CDMA

System Performance System Performance Metrics

NBSS15.0

vi Contents Nortel Networks

Copyright 2008 Nortel Networks during network initiated dormant to active transition 2-18 Call setup failures due to RF failures 2-18 Goal 2-19 Formulas 2-19 Voice call failures during setup due to non-RF resource failures 2-20 Formulas 2-21 Miscellaneous packet data call failures 2-21 Additional formulas 2-22 Voice call setup performance metrics on a per platform basis- (EBSC and BSC) 2-22 MEID related metrics 2-23 VPAD (voice preemption of active data) voice call setup performance - system level 2-25 Global emergency call metrics 2-26 Silent retry 2-27 3G packet data 2-27 Closed R-P metrics 2-28 OpenRP Metrics 2-30 Validation 2-32 For all call types together or 2G-only systems 2-32 Silent retry OMs validation 2-33 Blocking OMs validation 2-33 Validation for voice call setup performance OMs (per platform basis) 2-34 Validation for MEID OMs 2-35 Validation for 3G packet data OMs 2-35 Validation of VPAD OMs 2-35 Additional validation of HHO OMs 2-35 Validation of close RP OMs 2-36 Validation of open RP OMs 2-36 Validation for PCU manager OMs 2-36 Recommendations 2-37

1xRTT packet data performanceList of OMs 3-1 Goals 3-8 Formulas 3-8 SCH burst setup 3-8 SCH radio link setup 3-26 Additional information 3-41 Validation 3-43 Validation of forward burst setup OMs 3-44 Validation of reverse burst setup OMs 3-46 Validation of F-SCH primary link setup OMs Validation of F-SCH handoff link setup OMs 3-48 Validation of R-SCH primary link setup OMs Validation of R-SCH handoff link setup OMs Validation of SCHDrop OMs 3-49

3-1

3-47 3-47 3-48 3-49

RLP throughput performance411-2133-525 Standard 06.12 April 2008

4-1

Nortel Networks

Contents vii Copyright 2008 Nortel Networks List of OMs 4-1 RLP throughput performance metrics 4-2 Aggregate sector throughput (per EBID basis) 4-3 Per channel aggregate sector throughput (per EBID basis) 4-4 Per channel contribution to the overall aggregate sector throughput (per EBID basis) 4-6 Average mobile user throughput (per cluster/system basis for all given carriers) 4-8 Per channel throughput (per EBID basis) 4-10 Per channel utilization (per EBID basis) 4-13 Per channel data-retransmission percentage (per EBID basis) 4-15 Average physical layer data rate while bursting 4-17 Maximum bearer data throughput 4-17 Supporting metrics for 3G data throughput performance 4-18 Validation formulas 4-19

Access robustness package performanceGoal 5-1 List of OMs 5-1 CDMA access robustness package performance CASHO failures per sector 5-2 CASHO releases per sector 5-2 ACCHO failures per sector 5-2 ACCHO releases per sector 5-2 Validation 5-2 Validation of CASHO OMs 5-2 Validation of ACCHO OMs 5-2 5-2

5-1

Dropped call performanceGoals for dropped call performance 6-2 List of OMs 6-2 Overall dropped call rate 6-2 RF related dropped call rate 6-3 Network related dropped call rate 6-3 Additional formulas 6-3 Recommendations 6-4

6-1

Handoff performanceList of OMs 7-2 Soft and softer handoff performance 7-3 Goal 7-4 Formula 7-4 Recommendations 7-4 Sector based hard handoff performance 7-5 Goal 7-5 Formula 7-5 Validation 7-7 Route based hard handoff performance 7-8 Goal 7-8 Formulas 7-8

7-1

CDMA


NBSS15.0

viii Contents Nortel Networks Validation 7-8 Trigger type based hard handoff performance Goal 7-9 Formulas 7-9 Validation 7-13 Recommendation 7-14


7-8

Intelligent voice service negotiations performanceGoal 8-2 List of OMs 8-2 Formulas 8-3 Service redirection performance 8-3 Successful call setup based on mobile requested service option Validation 8-8 Recommendations 8-8 Query performance 8-10

8-1

8-6

BTS performance

9-1

List of OMs 9-1 Resource blocking and voice call downgrades 9-8 Origination and termination blocking 9-9 Soft handoff blocking 9-10 3G to 2G voice calls downgrade rate 9-11 Handoff sectors/beams per user 9-11 FSCH queuing 9-14 SCH link data rate downgrades 9-17 Percentage of SCH data rate downgrades per EBID 9-17 Distribution of SCH downgrades by specific downgrade reason 9-18 Distribution 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-21 Upper bound of average number of walsh codes in simultaneous use 9-22 Physical resource utilization metrics 9-22 Peak percentage of physical resources used for 2G FCH 9-22 Peak percentage of physical resources used for 3G FCH 9-22 Peak percentage of forward physical resources used for SCH 9-22 Peak percentage of reverse physical resources used for SCH 9-22 Peak percentage of forward physical resources used 9-22 Peak percentage of reverse physical resources used 9-22 Peak percentage of voice resources used on the forward FCH 9-23 Peak percentage of data resources used on the forward FCH 9-23 Forward transmit power utilization 9-23 Lower bound of average occupancy range 9-24 Upper bound of average occupancy range 9-24 Percentage of time forward transmit power is in an occupancy range 9-24 Forward common channel utilization 9-24 Paging channel utilization 9-24 Forward common control channel utilization 9-25 Reverse common channel utilization 9-26 Access channel utilization 9-26

411-2133-525

Standard

06.12

April 2008

Nortel Networks

Contents ix Copyright 2008 Nortel Networks Enhanced access channel utilization 9-27 Reverse common channel message received by type 9-28 Access channel message received by type 9-28 Enhanced access channel metrics 9-31 Forward common channel message drop rate 9-31 Paging channel message drop rate 9-31 FCCCH channel message drop rate 9-32 Forward common channel messages sent by type 9-33 Paging channel messages sent by type 9-33 FCCCH channel messages sent by type 9-34 MFRM-3 9-34 Metro Cell validation formulas 9-36

Paging performance

10-1

Goal 10-1 List of OMs 10-2 10-5 CDMA call delivery performance metrics 10-5 Overall call delivery performance of a system without BCP activated 10-5 Time distribution of page responses 10-8 Delayed page response rate 10-8 Overall call delivery performance of an anchor system with BCP activated 10-9 CDMA intersystem paging performance metrics 10-11 Overall intersystem paging performance of an anchor system (all border routes of all anchor sectors) 10-12 Intersystem paging performance of an anchor sector (all border routes of the anchor sector) 10-13 Intersystem paging performance of a border route (of an anchor sector) 10-14 CDMA IZP zone performance metrics 10-15 Zone performance for voice, CSD, and packet data calls 10-16 Delayed page response rate 10-19 Zone performance for SMS calls 10-20 Zone performance for MWI 10-22 10-24 MWI delivery performance 10-24 Voice preemption of active data feature paging performance 10-28 Overall paging failures for VPAD feature 10-28 Overall paging successes for VPAD feature 10-28 AMPS formulas 10-28 AMPS repaging formula 10-28 Validation 10-29 CDMA call delivery performance OM validations 10-29 CDMA intersystem paging performance OM validations 10-29 CDMA zone performance OM validations (for a single zone) 10-30 VPAD OMs 10-31 MWI OMs 10-32 Recommendations 10-32 CDMA paging 10-32 Zone paging 10-32

CDMA


NBSS15.0

x Contents Nortel Networks


Border paging performanceGoal 11-1 List of OMs 11-1 11-3 CDMA intersystem paging performance metrics 11-3 Overall intersystem paging performance of a border system (all anchor routes) 11-4 Intersystem paging performance of an anchor route 11-5 CDMA BCP zone performance metrics 11-6 Zone performance for voice, CSD, and packet data calls 11-6 Zone performance for SMS calls 11-10 Success rate of SMS delivery in the border system 11-10 11-10 Validation 11-10 CDMA border cell paging performance OM validations 11-10 CDMA zone performance OM validations (for a single BCP zone) 11-11 SMS Delivery 11-12 11-12 Recommendations 11-12 CDMA paging 11-12

11-1

Data burst message delivery performance

12-1

List of OMs 12-2 Idle mode SMS 12-4 Goal 12-5 Formula 12-5 Validation 12-8 In call SMS 12-9 Goal 12-9 Formula 12-9 Validation 12-10 CAU-CM SMS origination delivery 12-10 Goal 12-10 Formula 12-10 Validation 12-10 Message length histogram metrics 12-10 Formula 12-10 Distribution of DDS messages across channels 12-11 Distribution of DDS messages according to size on a per channel basis 12-12 Upper bound of the average message length on per channel basis 12-13 Mobile-initiated R-SDB 12-13 R-SDB size histogram metrics 12-13 Mobile-initiated SDB delivery success rate at the PCU-M 12-15 Mobile-initiated SDB delivery success rate at the PCU 12-15 Percentage of R-SDBs received on the R-EACH 12-16 Validation 12-16

Location services performanceGoal 13-1

13-1

411-2133-525

Standard

06.12

April 2008

Nortel Networks List of OMs 13-1 LCS paging performance 13-2 LCS call setup performance 13-3 Miscellaneous information 13-4 Recommendations 13-5 Notes 13-5

Contents xi Copyright 2008 Nortel Networks

MCTA performanceList of OMs 14-1 MCTA call setup failures 14-3 Goal 14-4 Formula 14-4 Total number of call setups attempted 14-4 Call types 14-5 MCTA frequency selection failures 14-6 MCTA resource allocation failures before CDA is executed 14-6 Reason codes for MCTA frequency resource allocation failures 14-7 MCTA call setup failures 14-8 14-9 Non MCTA frequency resource allocation failures (per frequency) 14-9 Retain loading related metrics 14-9 Paging channel redirection related metrics 14-10 MCTA RF access failure (per frequency) 14-10 MCTA RF related dropped call rate (per frequency) 14-12 Validation 14-12 Originations, terminations, and handoffs 14-12 Miscellaneous 14-12 Recommendations 14-13

14-1

Authentication performanceAuthentication air-interface performance Goal 15-2 List of OMs 15-2 Formulas 15-2 Validation 15-3 Recommendations 15-4 15-1

15-1

Call resource allocation and managementList of OMs 16-1 16-9 BSC/EBSC resource management 16-9 RMU resource management 16-9 RMU resource allocation performance 16-11 Resource utilization metrics 16-13 NRM resource allocation performance 16-18 SBSRM resource allocation performance 16-26 PCU change rate for dormant to active requests 16-27 PCU allocation performance for dormant handoff requests Resource allocation metrics during CNFP overload 16-31 16-32

16-1

16-29

CDMA


NBSS15.0

xii Contents Nortel Networks

Copyright 2008 Nortel Networks Effects of CSRM / SBSRM overload on platform selection mechanism 16-32 Resource allocation failures at CSRM and SBSRM (due to overload condition) 16-33 Resource allocation performance for connection type 16-34 Resource allocation failures for a connection type (due to lack of resources) 1634 Resource allocation failures for a connection type (due to processing errors) 1634 Resource availability rate for a connection type 16-35 Additional formula 16-35 Resource unavailability rate for a connection type 16-35 Resource re-direction rate 16-36 Distribution rate of resource allocation per connection type 16-37 Resource allocation failure rate per connection type 16-37 Distribution ratio for TrFO Vs. NonTrFO calls at TrFO capable PVG cards 16-37 Distribution ratio for EVRC Vs. Non-EVRC calls at non-TrFO PVG cards 16-38 EVRC-B related Metrics 16-38 EVRC-B Mode distribution Metrics (event based) 16-39 EVRC-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-42 Load contribution per service option on BSC 16-43 Eighth rate gating formulas 16-44 Gating request rates 16-44 Gating request granted rate 16-45 Gating request denied rate 16-45 Gating-enabled handoff percentage 16-46 Gating deactivation rate 16-46 Gating usage 16-47 Validation 16-47 Service option validation formulas 16-47 Resource utilization validation formula 16-48 16-48 Resource allocation validation formula 16-48 NRM resource allocation validation formula 16-49 SBSRM resource allocation validation formula 16-50 CSRM resource allocation validation formula 16-50 16-50 Dormant-to-active - PCU change validation formula 16-50 Dormant handoff - PCU allocation validation formula 16-51 Resource allocation for connection types validation formula 16-51 Eighth rate gating validation formula 16-53

RF performanceList of OMs 17-1 Reference sector FER metrics FCH formula 17-2 17-2

17-1

411-2133-525

Standard

06.12

April 2008

Nortel Networks SCH formula 17-4 Recommendations 17-5

Contents xiii Copyright 2008 Nortel Networks

CDMA-LTX performancePegging methods 18-1 List of OMs 18-2 Call setup performance 18-4 Call setup failure before resources are allocated Goal 18-4 Formula 18-5 Validation 18-9 Recommendations 18-11 Access failures 18-13 Dropped call performance 18-13 Goal 18-14 Formula 18-14 Validation 18-15 Recommendations 18-15 Paging performance 18-15 Goal 18-15 Formula 18-15 Limitations 18-17 MCTA performance 18-17 Goal 18-17 Formula 18-17 V5.2 protocol adaptor performance 18-24 Circuit switched data performance 18-25 Goal 18-25 Formula 18-25

18-1

18-4

OTAPA performanceGoal 19-1 List of OMs 19-1 Formulas 19-2 Validation 19-2

19-1

Call flow diagrams with OMs2G/3G voice call setup flow diagram with OMs 20-2 Voice call setup flow diagram with OMs- CSVS and SBS subsystems 20-9 Call setup flow diagram using BAM channels 20-16 MEID- Registration, origination/termination call flow with OMs 20-19 2G/3G voice/data soft handoff (intra-BSC) flow diagram with OMs 20-30 Hard handoff flow diagram with OMs 20-33 Hard handoff (intra-MSC) 20-34 Access robustness package: call flow with OM register pegs 20-35 IVSN flow diagram with OMs 20-37 Intelligent zone paging flow diagram with OMs 20-45 SMS termination over paging channel 20-45 SMS termination over traffic channel 20-47 In-call SMS termination 20-48

20-1

CDMA


NBSS15.0

xiv Contents Nortel Networks

Copyright 2008 Nortel Networks SMS origination over access channel 20-49 SMS origination over traffic channel 20-50 In-call SMS origination 20-51 VPAD call flow 20-52 VPAD call flow with OM pegs 20-53 Border cell paging and call setup 20-54 Successful paging and call setup in border system 20-54 Successful paging for SMS and SMS delivery in border system Inter-system hard handoff 20-60 Target system 20-60

20-56

MSC OM descriptionsMSC operational measurements 21-1

21-1 22-1

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

BTS OM descriptionsMetro Cell BTS operational measurements 23-2

23-1

411-2133-525

Standard

06.12

April 2008

Nortel Networks Table 13-1

Front xv Copyright 2008 Nortel Networks

Location services performance OMs Table 14-1 MCTA performance OMs Table 22-1 Table 22-2 Table 22-3 14-1

13-1

List of BSC OMsSCH burst setup OM group 22-5 List of BSC OMsPlatform Selection OM group 22-121 List of BSC OMsDHO call resource request processing OM group 22-135 List of BSC OMs OM group 22-150

Table 22-4

CDMA


NBSS15.0

xvi Front Nortel Networks


411-2133-525

Standard

06.12

April 2008

Nortel Networks

xvii Copyright 2008 Nortel Networks

About this documentPurpose

11

This document is written to assist the service provider in determining and tracking the performance of the Nortel CDMA System. Various formulas are provided for ascertaining system performance. In some cases the document also 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 dependent on the number of subscribers/users of the system, rather than a parameter directly under the control of the system. It is also important to note that the performance metrics listed in this document should be evaluated over several OM reporting cycles. This is due to the fact that the number of established calls may fluctuate over time. The same fluctuation could be seen in various other OM registers that track several call-related events. These fluctuations would cause the metrics to vary significantly from one reporting period to the other. The focus of this document is to provide its customers with a high level understanding of the CDMA related OMs available and how to measure the various types of system performance with those OMs. Note: The performance measurements presented in this document are meant to track the CDMA system performance rather than specific call models. The example performance metric goals listed in this document are high level objectives for the service provider and depend on the planned RF/Network requirements. If required, similar metric goals can be created for other metrics listed in this document. Also, the listed metric goals can be changed from 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 (or the failure rate goes up), further investigation is usually required and should be done.

CDMA


NBSS15.0

xviii About this document Nortel Networks


Audience

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

Scope of document

1

This document covers Operational Measurements related to CDMA System Performance. The CDMA Operational Measurements (OMs) are comprised of OMs from the DMS-MTX and the CDMA Access Subsystems (which includes BSC and/or EBSC and BTSs). This document does not cover BSC/ EBSC and BTS non-application OMs such as for ACN/BCN Transport and Overload Characterization. This document is written within the context of the Nortel CDMA NBSS System. Hence, we refer to OMs that peg for NOIS only (with the exception of some CM OMs that peg for IOS). This document is not intended to correct or document existing performance measurements that are not being added by or are not of primary concern to the CDMA system.This document is not intended to provide the procedures necessary 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 in this document. Refer to NTP # 241-6001-031 Preside Multiservice Data Manager Performance Management User Guide.

Organization

1

The document is organized by performance area. Chapter 2 through Chapter 18 describe the CDMA specific product metrics. Each of these chapters specifies a few example metric goals, list of applicable operational measurements (OMs) used to calculate the metric, formulas for calculating the metric, and a section that recommends changes to the configurable parameters of the MTX-CDMA system or other potential actions to address identified performance issues. For a better understanding and interpretation of the metrics provided in this NTP; it is essential to refer to the explanation of the operational measurements (OMs) provided in the OM Descriptions chapters (Chapters 21, 22 and 23). The following is a list of chapters and performance areas that are discussed in this document: Chapter 1, CDMA OM design overview Chapter 2, Call setup performance

411-2133-525

Standard

06.12

April 2008

Nortel Networks

About this document xix 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 and handoff scenario flow charts with key OMs from related OM group for the 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 OMs referenced 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 for all 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 Information Guide.

CDMA


NBSS15.0

xx About this document Nortel Networks


NTP # NN20000-104: Nortel CDMA BSS Manager Fault Management -Log Report Generation. NTP # NN20000-144: Nortel CDMA C-EMS Fault Management. This document contains procedures for handling OMs in the C-EMS and a detailed description of OM Parser and OM Log Filter.

Indication of hypertext linksHypertext links in this document are indicated in blue. If viewing a PDF version of this document, click on the blue text to jump to the associated section or page.

1

411-2133-525

Standard

06.12

April 2008

Nortel Networks

1-xxi Copyright 2008 Nortel Networks

New in this release

1

The following sections detail whats new in Nortel CDMA Operational Measurements Reference -- System Performance Metrics (NTP 411-2133525) for NBSS 15.0 / MTX15. Features on page 1-xxi Other changes on page 1-xxi

FeaturesThis document contains no feature update for this release.

1

Other changesSee the following section for information about changes that are not feature related:

1

Updated the section Network-initiated dormant-to-active transition failure rate (page -27) Updated the table Call setup performance OMs (page -2) Updated the table MSC operational measurements (page -1)

CDMA


NBSS15.0

1-xxii New in this release Nortel Networks


411-2133-525

Standard

06.12

April 2008

Nortel Networks

1-1 Copyright 2008 Nortel Networks

CDMA OM design overviewOM philosophy

11

The CDMA operational measurements (OMs) consist of OMs from the DMSMTX (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 philosophy The DMS-MTX OMs are collected individually by each subsystem (CAU, RMU, and CM) and are periodically sent to the CM for collection. MTX OMs are organized and reported on a per-system, per-sector, or per-carrier-sector basis. MTX OMs are divided into two categories: non-CDMA specific OMs and CDMA specific OMs. Non-CDMA-specific OMs The non-CDMA-specific OMs consist of the OMs common to CDMA, TDMA, and AMPS technologies. Most of these common OMs are related to call 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 OMs Many OMs have been added to the MTX specifically for CDMA-related events. For example, all OMs pegged by the CAU and RMU are CDMAspecific. The majority of these CDMA-specific groups are identified by OM group 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).

CDMA


NBSS15.0

1-2 CDMA OM design overview Nortel Networks


Extension registers The standard OM registers hold a range of values from 0 to 65 535. When the count in a register exceeds its design limit of 65 535, its extension register (if made available) increases by 1 while the basic register clears. Therefore, an actual event count of 65 536 would show a count of 1 in the extension register and 0 in the basic register. When the actual event count reaches 131 072, the extension register would increase again and show a count of 2, and the basic register would clear again and show a count of 0. Since the features and behavior of extension registers are essentially the same as the registers that they extend, detailed explanations of individual extension registers are unnecessary. For example, the extension register for the OM PGRESP1 is PGRESP1X. CDMA access system OM philosophy The CDMA access system consists of the EBSC/BSC, and the BTS (base station transceiver subsystem). From an OM perspective, the EBSC consists of CPDS (CDMA packet data subsystem), CSVS (CDMA selection and vocoding subsystem), and BSC/SBS (selector bank subsystem). CDMA access system OMs are collected individually by each subsystem and are periodically sent to either the BSSM (base station subsystem manager) or the C-EMS (CDMA element management subsystem). The BSC(SBS) and BTS OMs are sent to the BSSM as QMIP event report messages. Upon receiving these messages, the BSSM stores them in its OM binary file that is currently open. These OMs appear mixed in the BSSM OM binary file. The EBSC OMs (CSVS and CPDS) are uploaded as binary files to the CEMS. 2pVS OMs are handled by the MDP (an MDM component). C-EMS C-EMS is an OA&M platform that was introduced in NBSS 12.1. It manages the OM configurations for the CSVS, CPDS, and SBS subsystems. The CEMS co-resides and interacts with the existing BSSM. Starting in 14.0 release the BSSM should only be deployed with the C-EMS. OM pegging types Each OM can only have one pegging type. The pegging type describes on what basis a particular OM is collected. It also provides a reference and a context 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

411-2133-525

Standard

06.12

April 2008

Nortel Networks

CDMA OM design overview 1-3 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 based services (RS1-9.6Kbps), Markov (9.6Kbps), Markov(14.4Kbps), MS loopback (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. This includes the following pegging types: service type, service group, EBID, IP, resource type and RC

OM groups As 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 group is assigned an identifier (the group ID). All BSC and EBSC OMs, including those that existed prior to NBSS 12.0, are assigned to OM groups. All BSC and 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 tool As of NBSS 12.0, the service provider has the capability to turn the pegging of 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 of the C-EMS. The BSSM and the C-EMS provide the user with an interface that 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, the OM management tool on the BSSM controls SBS OMs when the C-EMS is not installed. The BSSM OM management tool is disabled when the C-EMSCDMA System Performance System Performance Metrics NBSS15.0



is installed. The BSSM OM management tools provides system-wide control of SBS OMs (not on a card-level basis). When the C-EMS is installed, the BSSM OM management tool is disabled and 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 percard basis for CSVS and CPDS only (for example, an individual DSFP card can be prevented from uploading its OM file.) The C-EMS OM configuration tool 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 CEMS OM configuration tool will affect those OM collections on CSVS, CPDS, and SBS. In addition, the C-EMS will not be aware of any manual configuration 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 OMs or OM groups may affect the ability of the provider to use some or all of the metrics described within this document. For more information about C-EMS functionality, see Nortel CDMA C-EMS Fault Management (NN20000-144). BTS OMs are always collected at the subsystem level, but the reporting (for example, uploading) may be enabled or disabled on a per-subsystem basis from the BSSM. For more information about OM management and configuration, see Nortel CDMA BSS Manager Fault Management -- Log Report Generation (NN20000-104). CDMA OMs are collected and stored separately on the DMS-MTX and the BSCandEBSC and the BTS. These systems may or may not consolidate the OMs from multiple nodes as described below. MTX OM consolidation Because of the distributed architecture of the DMS-MTX, any CAU provisioned for the single CDMA access system can process calls from any of the CDMA cells in that BSC system. Therefore, OMs are collected at individual 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 (the maximum number is increased from 2 to 16) per MTX. As a result the maximum number of cell-sector-frequency supported per NOIS BSC is 4500411-2133-525 Standard 06.12 April 2008

Nortel Networks


and the maximum number of cell-sector-frequency supported on the MTX is 9000. Depending on the provisioning of parameter OMXFR in table OFCENG, the CM will transfer the values of the OMs from the active to the holding registers every 15 or 30 minutes and upload the OMs from the CAUs and RMUs. Note that parameter OMHISTORYON is disabled. For sector-based OMs, a software entity at the LPP combines and consolidates the OMs from all CAUs on that LPP into a single sector-based OM for that entire LPP. For example, if CAU108 receives 5 originations from sector 13X and CAU109 receives 7 originations from sector 13X, there is one origination OM on the LPP for sector 13X, and its value is 12. These sectorbased OMs gathered at each individual LPP are uploaded to the CM. The CM combines and consolidates all of the individual LPP OMs into a single sectorbased OM. For carrier-sector based OMs, they are similarly consolidated and uploaded as described for the sector-based OMs. For node-based OMs, the OMs are uploaded directly to the CM without consolidation. 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 OFCENG OMXFR setting. This eliminates the two minute skew between the NOIS LPP and the CM OMs. A four minute delay is introduced before starting the subsequent 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 registers during the four minute OM upload period (and not to the CM active registers). Any late NOIS LPP OMs received by the CM are placed in the CM active registers and used during the next OMXFR cycle. CDMA access system OM consolidation OM consolidation on the CDMA access subsystem is performed by the BSSM 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 PCUFP cards. 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), the OMs of the individual network elements that relate to that particular EBID are added together to provide a network-wide representation for those OMs.CDMA System Performance System Performance Metrics NBSS15.0



For example, the FSCHLinkSetupAttempts_2X OM is an EBID-based OM that exists on both ESEL and DSFP cards. Since the ESEL and DSFP cards are pooled system resources, the OM value of FSCHLinkSetupAttempts_2X for a particular EBID may have contributions from more than one ESEL or DSFP card during any given collection period. Therefore, the OM value for FSCHLinkSetupAttempts_2X for a particular EBID is a sum of pegs at all ESEL and DSFP cards. Similarly, the per-IP-based OMs that are pegged at the PCU and the PCUFP cards are also summed up for a particular IP address and a single value is provided in the OM report. This functionality is the default behavior of the OM parser. The OM parser can also be run in nonaccumulation mode as described below. The specifics of OM uploading, processing, and file location are slightly different depending on whether the subsystem is part of the EBSC, BSC, or BTS platform as described below. EBSC-specific OM upload process For C-EMS managed subsystems such as CPDS, the collection agents (for example, the DSFP card for ACPs) are responsible for pegging and collecting OMs. Every 30 minutes, these binary files are transferred to the C-EMS using FTP and placed in the C-EMS /opt/cems/log/OMBinary directory. The binary files have a format similar to SBS binary files. The EBSC OMs are collected over 30 minute intervals starting and ending on the hour or half hour (for example, 16:00:00 or 16:30:00) and then uploaded to the C-EMS. BSC-specific OM upload process For the BSC subsystem, the OMs are pegged, collected, and sent to the BSSM through an event trigger. As of NBSS 12.0, the BSC (SBS) OM upload system is enhanced so that the OM data is directly uploaded from the subsystems (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 on the hour or half hour (for example, 16:00:00 or 16:30:00) and subsequently uploaded to the BSSM. BTS-specific OM upload process For the BTS subsystem, the OMs are pegged, collected, and sent to the BSSM through an event trigger. The uploaded event report is saved in binary format on the BSSM in the /opt/bsm/log/OMBinary directory. The OMs pegged at the BTS cannot distinguish between events related to calls set up on the SBS or CDPS.

411-2133-525

Standard

06.12

April 2008

Nortel Networks


The BTS OMs are collected over 30 minute intervals starting and ending on the hour or half hour (for example, 16:00:00 or 16:30:00) and subsequently uploaded to the BSSM. OM parsing In the case of deployment with C-EMS and BSSM, the default behavior of the OM parser is to process the binary files under both the /opt/cems/log/ OMBinary and /opt/bsm/log/OMBinary directories. The output files from the OM parser are raw ASCII text files. C-EMS provides the capability to configure the OM parsing time (for example, when the OM parser is run to generate the ASCII files). The OM parser can be run in different modes. Two of these modes are discussed 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 following files: CPDS-, which contains the node-based CPDS OMs listed for each ACP, CAC, and PCU CSVS-, which contains the node-based CSVS OMs listed for 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 BTS OMs listed by BTS MO (for example, the BTSCallProcessing MO and the AdvancedFA MO). BSC-, which contains the non-node-based consolidated (for example, summed) OMs such as EBID, Multi-ID, and IP-based OMs from both BSC and EBSC nodes. For example, per carrier-sector OMs that 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 are stored in the /opt/cems/log directory while the SBSCSubsystem, MCBTSSubsystem-, and BSC- files are stored in the /opt/bsm/log directory.

CDMA


NBSS15.0



OM parser no accumulation mode The OM parser can also be run manually with a non-accumulation option. By specifying 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 values exactly as they were found in the binary files. Therefore, all OMs will be displayed 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 nodebased, IP-based, and EBID-based CPDS and CSVS OMs listed for each ACP, 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 BTS OMs listed by the BTS MO (for example, the BTSCallProcessing MO and 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 no longer summed up. Instead, these OMs for CSVS and CPDS are included in the CSVS/CPDS- file on a per-node basis along with the nodebased OMs. Similarly, these SBS OMs are included in the SBSCSubsystem file along with the node-based OMs.

OM metrics overviewThe OMs collected by the DMS-MTX, BSC, EBSC, and BTS make it possible to define and implement performance-related metrics. This document contains informaiton about metrics that help customers monitor and 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 more measurements, providing a view of system performance

1

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 or analysis after-the-fact or for the measurement of abnormal events.

411-2133-525

Standard

06.12

April 2008

Nortel Networks


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

OM validation overviewWhere possible, formulas are provided at the end of each major section or chapter 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 events correctly.

1

Since OMs are collected during specific intervals, it is possible for related OMs to span one or more OM collection periods. This may cause a slight discrepancy 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 of one OM period while the success or non-success of that same event may be captured at the beginning of the next OM period. Therefore it is recommended that, where possible, the validation formulas be used with OMs collected over a 24 hour period in order to minimize the effect of these discrepancies.

CDMA


NBSS15.0



411-2133-525

Standard

06.12

April 2008

Nortel Networks

2-1 Copyright 2008 Nortel Networks

Call setup performance

2

Call 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, or during a resource allocation attempt for a queued WPS (wireless priority service (WPS) call. 2. When the mobile is moving from the common channel to the traffic channel (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 engineering or possible problems with the subscribers mobile unit. For more information about item 1, see Call setup failure before resources are allocated (blocked calls) (page 2-10). For more information about item 2, where the base station is unable to receive traffic from the mobile on the reverse traffic link, see Call setup failures due to 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 for the packet data scenarios, including SCH burst setups, are listed in 1xRTT packet data performance (page 3-1).

List of OMs

2The following list contains the MSC, BSC, and BTS OMs that are relevant to this chapter.CDMA System Performance System Performance Metrics NBSS15.0

2-2 Call setup performance Nortel Networks


For more information about detailed OM descriptions, see MSC operational measurements (page 21-1), BSC OM descriptions (page 22-1), and Metro Cell BTS operational measurements (page 23-2).Call setup performance OMs

MSC OMsCAUCPSCT OM group CAUPGRES CAUTRLS CAUORODR SLTPGRES CAUHRLS CAUESWFL CAUFWCAP MCTALLFU CAUTSUCC CAUOATTS CAUORLS CAUHATTS CAUHRLFL CAUNOTCE SCTBTSBK MCTALLTO CAUTBLKS CAUOSUCC CAUERSFL CAUHBLKS CAUDROPR CAUNOWCD MCTAHRQF MCTAMIXF CAUEDLOT CAUOBLKS CAUERLFL CAUHSUCC CAUDROPN CAUNOFOF MCTAREQF CAUHINIT

CAUSCT2 OM group NORFSEFL WPSTRTRY NRFSEFHH MISCFLT WPSRETRY

CAUSCT3V OM group This OM group has the same OM registers as the CAUCPSCT OM group listed above.

CAUST3V2 OM group This OM group has the same OM registers as the CAUSCT2 OM group listed above

CAUSCT3D OM group This OM group has the same OM registers as the CAUCPSCT OM group listed above.

411-2133-525

Standard

06.12

April 2008

Nortel Networks Call setup performance OMs CAUST3D2 OM group CAURELSI PDSEFLDS PDSEFLAS

Call setup performance 2-3 Copyright 2008 Nortel Networks

EBPBCPOM OM group ESBSRASU ESBNRSFL ESBSCSS ECSVRASU ECSNRSFL ECSVCSS ESBESWFL ESBERLFL ECSESWFL ECSERLFL

BAMCPSCT OM group BAMOATTS BAMERLFL MCPCTBAM BAMOSUCC BAMEDLOT BAMPGRES BAMWPSRT BAMTSUCC MCPCOBAM

CAUCPSYS OM group CAUORIGS CAUCNICV CAUTMWNR CAUREGNS CAUCNITR CAUFLASH CAUHOSRC CAUTMWNA CAUMRLS CAUHOTRG CAUTMWNC CAULRLS

CAUCPFRQ OM group MCTORIGS MCTTATTS MCTHSUCC MCTNOWCD MCTERLFL MCTDROPR MCTOATTS MCTTSUCC MCTHRLFL MCTNOFOF MCTAREQT MCTOSUCC MCTHCATT MCTERSFL MCTFWCAP MCTAREQN MCTPGRES MCTHATTS MCTNOTCE MCTBTSBK MCTARQFN

CAUFRQ3V OM group

CDMA


NBSS15.0

2-4 Call setup performance Nortel Networks Call setup performance OMs


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 MCTPRST MPRFL MRETHBLK MRETHFL NMCTBLKS MCTPRSO MRETATTS MRETSUCC MCTPRRO MPRBLKS MRETHATT MRETHSUC MCTPRRT MPRSUCC MRETBLKS MRETFL

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 RMURATOV RMUIANRD RMURANRD RMUIANRV RMURANRV RMUIOEND RMURAOED RMUIOENV RMURAOEV RMURARD RMURARV RMUIATOD RMURATOD

411-2133-525

Standard

06.12

April 2008

Nortel Networks Call setup performance OMs BSCRM2 OM group RMUIRDS RMURRDS RMUINRDS RMURNRDS RMUITODS RMURTODS


RMUIOEDS RMUROEDS

EBSCRM OM group NRMARV NRMOLRV NRMOEPD NRMANRDS NRMSTODS NRMANRV NRMSTOV NRMOLRPD NRMAOEDS NRMOEV NRMARPD NRMSTOPD NRMATODS NRMATOV NRMANRPD NRMARDS NRMOLRDS

CAUMISC OM group CAUUNSO RMUUNSO NRMUNSO FLEVR13K

CDMAIVSN OM group ONILDNY ODENYCAU ODENYCM TDENYCAU

CDMAPDOM OM group MIDTOAAT NIDTOASU NULTOAFL NIFLMINA NIFLSRSP MSREGNOT NIDTOAFX NIFLNSOP MIDTOASU NIDTOAFL MIDTOAAX NIFLPGTM NIFLCLFL MIDTOAFX NULTOAAX MIDTOAFL NULTOAAT MIDTOASX NIFLPGNG NIFLMRLS NIDTOAAX NULTOASX NIDTOAAT NULTOASU NIFLNVLR NIFLVCLL NIFLAMPS NIDTOASX NULTOAFX

CDMA


NBSS15.0

2-6 Call setup performance Nortel Networks Call setup performance OMs CDSNMQRY OM group FLTCEVR 3GFLI13K FLTCI13K 3GFLB13K FLTCB13K


3GFLTEV

MTXPDSCT OM group NWKFLBS AHRLPFL NWKFLAS NARLPFL DARLPFL

MTXPDSYS OM group NARPFLBS DARPFLAS DARPFLBS AHRPFLAS AHRPFLBS DHORPFL NARPFLAS

MTXSYS1 OM group CDMAPRS1 CDMAPRS2 TDENYCM

MTXSYS2 OM group GECRCVD MEIDQSCC ESNATTS GECATTS MEIDQRTC GECSUCC MEIDQSTC MEIDQRCC MEIDATTS

OMMTX OM group MBORIGS

OMMTXSYS OM group TWCSTART

OMMTX2 OM group

411-2133-525

Standard

06.12

April 2008

Nortel Networks Call setup performance OMs VPADIC


OMMTX3 OM group SRTDBORG SLNTRTAF SRTDBO2G SLNTRT2G SRTDBO3V SLNTRT3V SRTDBO3D SLNTRT3D

OMMTXSY2 OM group VPADATT VPADSUC VPADFL

TRMTRS OM group TRSGNCT

WPSOM1 OM group WQTOUT WQOVFL WINVALDQ

BSC OMsRLP Setup OM group RLPSetupAttempts RLPSetupSuccesses RLPSetupFailures

Packet Session Signaling OM group TotalSessionSetupInitialAtt empts TotalInitialRPSessionSetup Failures TotalSessionSetupReconn TotalSessionSetupSuccess TotalSessionSetupFailur ectAttempts es TotalRPSessionHandoffFa TotalReleasesBeforeInitial TotalReleasesBeforeHan ilures SessionSetup doffSessionSetup

Packet Session Data OM group

CDMA


NBSS15.0

2-8 Call setup performance Nortel Networks Call setup performance OMs TotalFwdPacketsDropped TotalRevPacketsDropped


DCRBufferOverflows

DCRNumOfStopTransm itMsgsSent PeakNumberOfAttached ActiveUsers SessionTransitionsQueu ed

RRBufferOverflows

PeakNumberOfAttachedD AttachedActiveUsers ormantUsers NumberOfDormantCallsG EnteredSessionTransition oingActive ThrottleMode

AttachedDormantUsers

ExitedSessionTransitionThr TotalDormantBufferLimit ottleMode Overflows

RP Session Signaling OM group TotalInitialRP_SessionSetu pAttempts TotalInitialRP_SessionSet TotalInitialRP_SessionSet TotalInitialRP_SessionS upSuccesses upRejectReasonOther etupRejectReasonIdMis match

TotalInitialRP_SessionSetu TotalInitialRP_SessionSet TotalInitialRP_SessionSet TotalRP_SessionHandof pRejectReasonInsufficientR upRejectReasonMobileAu upFailuresReasonPDSN_ fAttempts NotResponding esources thFailure

TotalRP_SessionHandoffSu TotalRP_SessionHandoff ccesses RejectReasonOther

TotalRP_SessionHandoff RejectReasonIdMismatch

TotalRP_SessionHandof fRejectReasonInsufficie ntResources

TotalRP_SessionHandoffRe TotalRP_SessionHandoffF PCU_InitiatedSessionRele PCU_InitiatedSessionRe jectReasonMobileAuthFailu ailuresReasonPDSN_Not asePacketSessionDisconne leasePacketSessionDrop re Responding ct PCU_InitiatedSessionReleas PCU_InitiatedSessionRele TotalRegistrationRequest ePDSN_Reject aseOther MsgSent TotalRegistrationRequestRe TotalRegistrationRequest jectReasonOther RejectReasonIdMismatch TotalRegistrationReques tRetries

TotalRegistrationRequest TotalRegistrationReques RejectReasonInsufficientR tRejectReasonMobileAu esources thFailure

TotalRegistrationRequestRe TotalSignallingMsgReceiv jectReasonPDSN_NotRespo ed nding

RP Session Data OM group RPTotalOutofSequencePack RPTotalUnreliableBytesTr RPTotalUnreliableBytesR etsReceived ansmitted eceived

411-2133-525

Standard

06.12

April 2008

Nortel Networks Call setup performance OMs


PCU Manager OM group DormantToActiveHandoffs PCU_AllocSuccessful DormantHandoffRequests PCU_AllocRequests IMSI_TableFull PCU_AllocFailures

RP Session L2TP OM group ReliablePacketSentSuccess ReliablePacketReTransmit ReliablePacketReceived ted NumberOfTunnelFailure s

TotalUnreliableBytesTrans mitted

TotalUnreliableBytesRece RP_SessionSetupAttempts RP_SessionSetupSucces ived ses

RP_SessionSetupRejectRea RP_SessionSetupRejectRe RP_SessionSetupRejectRe RP_SessionSetupReject sonGenErr asonNoCarrier asonAdminReason ReasonNoTempRsrcs

RP_SessionSetupRejectRea RP_SessionSetupRejectRe RP_SessionSetupRejectRe RP_SessionSetupReject sonNoPermRsrcs asonSysOverload asonOther ReasonNoPDSNRsp

BTS OMsAdvanced Sector MO FchOriginationNonBlocking FchOriginationNonBlocki FchOriginationNonBlocki BlockedFchOriginations 3GDowngrade2G ng3GDowngrade2GNoAc ng3GDowngrade2GNoBc 2G[6]: CFDS Radio n n Config State BlockedFchOriginations3G Voice[6]: CFDS Radio Config State BlockedFchOriginations3 GData[6]: CFDS Radio Config State

CDMA


NBSS15.0



Call setup failure before resources are allocated (blocked calls)

2

Call setup failures before resources are allocated are network-related call setup failures 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 to unsupported 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 involved in the call: terrestrial trunks (SBS to DTC trunks) Goal Less than x% of all originations attempted failed due to resource shortages. Less than y% of all terminations attempted failed due to resource shortages. Less than z% of all hard handoffs attempted to CDMA cells are failed due to resource shortages. SBS selector elements BTS traffic channel elements. non-availability of excess RF capacity. non-availability of Walsh codes PDSN PCU

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 anything other than 2%. Formula usage The Boolean field OM3G in table CDMAPART is an indicator of whether the OMs for 3G voice calls and 3G data calls are to be kept separate from the OMs for 2G calls. The OM groups CAUSCT3V, CAUSCT3D, CAUFRQ3V, CAUFRQ3D, CAUXTF3V, CAUXTF3D maintain 3G voice and 3G data OM counts for a particular sector only if OM3G is set to Y. If a particular sector is 3G-capable but OM3G is set to N, the 3G voice and 3G data OM counts are combined with the 2G OMs in the CAUCPSCT, CAUCPFRQ and CAUXTFRQ OM groups.

411-2133-525

Standard

06.12

April 2008

Nortel Networks


Impact of OM3G Boolean on OM registers in certain OM groups

OM3G Impact on Boolean CAUCPSCT, CAUCPFRQ, and CAUXTFRQ OM groupsY The registers in these OM groups get pegged only for events related to 2G voice and CSD calls The registers in these OM groups get pegged for all call-related events (3G voice & CSD, 3G data, and 2G voice and CSD calls)

Impact on CAUSCT3V, CAUFRQ3V, and CAUXTF3V OM groupsThe registers in these OM groups get pegged only for events related to 3G voice and CSD calls The registers in these OM groups do not get pegged. The related 3G voice and CSD callspecific events will be captured in CAUCPSCT, CAUCPFRQ, and CAUXTFRQ OM groups along with 3G data and 2G call-related events.

Impact on CAUSCT3D, CAUFRQ3D, and CAUXTF3D OM groupsThe registers in these OM groups get pegged only for events related to 3G data calls The registers in these OM groups do not get pegged. The related 3G data call-specific events will be captured in CAUCPSCT, CAUCPFRQ, and CAUXTFRQ OM groups along with 3G voice and 2G call-related events.

N

Impact of OM3G Boolean on OM registers in the new OM groups

OM3G Impact on Boolean CAUSCT2 OM groupY The registers in this OM group get pegged only fr events related to 2G voice and CSD calls The registers in this OM group get pegged for 2G, 3G voice, and CSD related calls. The 3G packet data OMs do not have registers that can be pegged here.

Impact on CAUST3V2 OM groupThe registers in this OM group get pegged only for events related to 3G voice and CSD calls The registers in this OM group do not get pegged. The 3G voice and CSD call related events will be captured in CAUSCT2 OM group.

Impact on CAUST3D2 OM groupThe registers in this OM group get pegged only for events related to 3G packet data calls The registers in this OM group do not get pegged.

N

CDMA


NBSS15.0



The attempts in the following sections refer to those calls that the system is aware of and attempts to setup resources for. For example, the system is not aware of origination call attempts that exhaust the access probes since the origination message is lost and, therefore, is not received by the BTS. Similarly, the system does not count termination call attempts if the page timed out without receiving a response, since the system does not attempt to set up resources. Attempts to allocate resources for WPS calls that are queued are considered a call setup attempt, since the origination for the call originally resulted in a block (the call is then queued). WPS calls can be either 2G or 3G voice only. Total calls attempted The following formula will be used (and will be referred to) throughout the chapter. Total calls attempted = (CAUOATTS + CAUPGRES + CAUHATTS + WPSRETRY + WPSTRTRY) for all sectors - (MCTPRSO + MCTPRST) for all frequencies for all MCTA sectors +/FchOriginationNonBlocking3GDowngrade2G +/FchOriginationNonBlocking3GDowngrade2GNoAcn +/FchOriginationNonBlocking3GDowngrade2GNoBcn for all sectors. The MCTPRSO and MCTPRST OMs are subtracted in the above formula accounting for the origination or termination attempts that get redirected by MCTA to the alternate CDMA band resulting in CAUOATTS or CAUPGRES OM being pegged twice in those events. It is also important to note that 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 MCTPRSO and MCTPRST OMs in the above formula are replaced with MCTPRRO and MCTPRRT OMs respectively. The FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn BTS OMs are pegged when the BTS runs out of XCEM resources but still has CEM resources and all other needed resources to be set up for the call as a 2G voice call rather than a 3G voice call as requested by the mobile. These BTS OMs are included in the above metric as well as other metrics later on in this chapter for the following reason: When a mobile attempts to make a 3G voice call, the attempt is pegged in CAUSCT3V OM group, but if the call is downgraded 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. 2G versus 3G voice), the BTS OMs FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn are added to the 2G attempts and subtracted from the 3G attempts as stated below.

411-2133-525

Standard

06.12

April 2008

Nortel Networks


The WPSRETRY and WPSTRTRY OMs only apply to voice and circuit switched data calls. There is no WPS service for packet data calls. For packet data only metrics, do not include these two OMs in the Total Calls Attempted term. Call types The following sections will be referred to throughout the chapter in order to evaluate the metrics based on call types (2G Voice, 3G Voice, Voice Calls, PD Calls and For all Call types together) For 2G voice calls For 2G calls, use the OMs from the OM groups CAUCPSCT, CAUSCT2 and CAUXTFRQ in the formula and add the value of the BTS OMs FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in the formula. For non-3G enabled systems, the BTS OMs FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in the above formula are not applicable and are not pegged. For 3G voice calls For 3G Voice calls, use the OMs from OM groups CAUSCT3V, CAUST3V2 and CAUXTF3V in the formula and subtract the value of the BTS OMs FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in the formula. 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 OMs FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in the formula are not applicable since the value is already included in the other OMs. For 3G packet data calls For 3G Packet Data calls, use the OMs from OM groups CAUSCT3D, CAUST3D2 and CAUXTF3D in the formula, but the BTS OMs FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in the above formula are not applicable for packet data calls. For all call types For all call types together, use the sum of the OMs from OM groups CAUCPSCT, CAUSCT2, CAUSCT3V, CAUST3V2, CAUSCT3D and CAUST3D2 (and from OM groups CAUXTFRQ, CAUXTF3V, CAUXTF3D) in the formula, but the BTS OMs

CDMA


NBSS15.0



FchOriginationNonBlocking3GDowngrade2G/NoAcn/NoBcn in

the formula are not applicable since the value is already included in the other OMs.

Overall call setup failures (call blocking rate) (CAUOBLKS + CAUTBLKS + CAUHBLKS) all sectors / Total calls 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)

2

Call setup failures (blocks) due to lack of EBSC/BSC resources This metric indicates the shortage of the resources for Voice, Packet Data and Data Delivery Services (SMS, OTAPA, LCS). This metric indicates that resources are not available for the call during resource allocation request phase. This situation may be improved by provisioning BSC/EBSC additional resources. 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 calls attempted) x 100 Failures combined for Voice, Packet data and Data Delivery services together can 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 100411-2133-525 Standard 06.12 April 2008

Nortel Networks


All (voice and packet data) call setup failures (blocks) ( (RMURANRV + RMUIANRV - RMURARV + RMURANRD + RMUIANRD - RMURARD) for all CAUs / Total calls attempted) x 100 Failures combined for Voice, Packet data and Data Delivery services together can also be derived. Call setup failures due to BSC/EBSC processing errors This metric is useful in determining the blocks due to certain processing errors such as time outs or internal errors occurring during the resource allocation phase. Blocking of calls due to such error conditions is typically rare and is not due to shortage of resources. System where NRM is resource manager Voice call setup failures ( (NRMATOV + NRMOEV + NRMOLRV + NRMSTOV) for all CAUs + CAUESWFL for all sectors / Total calls attempted) x 100 Packet data call setup failures ( (NRMATOPD + NRMOEPD + NRMOLRPD + NRMSTOPD) for all CAUs + CAUESWFL for all sectors / Total calls attempted) x 100 Data delivery services (SMS, OTAPA, LCS) call setup failures ( (NRMATODS + NRMOEDS + NRMOLRDS + NRMSTODS) for all CAUs / NRMARDS for all CAUs) x 100 All (voice and packet data) call setup failures ( (NRMATOV + NRMOEV + NRMOLRV + NRMSTOV + NRMATOPD + NRMOEPD + NRMOLRPD + NRMSTOPD) for all CAUs + CAUESWFL for all sectors / Total calls attempted) x100 Failures combined for Voice, Packet data and Data Delivery services together can also be derived.

System where RMU is resource manager Voice call setup failures ( (RMUIATOV + RMURATOV + RMUIOENV + RMURAOEV) for all CAUs + CAUESWFL for all sectors / Total calls attempted) x 100 Packet data call setup failures ( (RMUIATOD + RMURATOD + RMUIOEND + RMURAOED) for all CAUs + CAUESWFL for all sectors / Total calls attempted) x 100CDMA System Performance System Performance Metrics NBSS15.0



Data delivery service (SMS, OTAPA, LCS) call setup failures ( (RMUITODS + RMURTODS + RMUIOEDS + RMUROEDS) for all CAUs / RMUIRDS for all CAUs) x 100 All (voice and packet data) call setup failures ( (RMUIATOV + RMURATOV + RMUIOENV + RMURAOEV + RMUIATOD + RMURATOD + RMUIOEND + RMURAOED) for all CAUs + CAUESWFL for all sectors / Total calls attempted) x 100 Failures combined for Voice, Packet data and Data Delivery services together can also be derived. Call setup failures (blocks) due to BTS physical resources These metrics determine the shortage of BTS physical resources. High values of these metrics should be addressed by provisioning additional BTS resources. Call setup failures (blocks) due to all BTS related blocks ( CAUERSFL all sectors / Total calls attempted) x 100 Call setup failures (blocks) due to lack of BTS channel elements ( CAUNOTCE all sectors / Total calls attempted) x 100 Call setup failures (blocks) due to lack of Walsh codes ( CAUNOWCD all sectors / Total calls attempted) x 100 Call setup failures (blocks) due to lack of forward capacity ( CAUFWCAP all sectors / Total calls attempted) x 100 Call setup failures (blocks) due to no frame offset availability ( CAUNOFOF all sectors / Total calls attempted) x 100 Call setup failures (blocks) due to miscellaneous BTS failure reasons ( SCTBTSBK all sectors / Total calls attempted) x 100 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). Call setup failures (blocks) due to BTS time-outs ( (CAUERSFL - CAUNOTCE - CAUNOWCD - CAUFWCAP CAUNOFOF - SCTBTSBK - BlockedFchOriginations*[6] MCTAREQF - MCTAHRQF + MCTALLTO) all sectors / Total calls attempted) x 100

411-2133-525

Standard

06.12

April 2008

Nortel Networks


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). Use the appropriate BlockedFchOriginations*[6] OM based on the call type (2G Voice, 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 failures during null to active transition of a packet data call before service connect completion 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 failures during 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 failures during active handoff of a packet data call before service connect completion can be expressed as: ( AHRPFLBS for all sectors) / ( CAUHATTS for all sectors) x100 In the above formula use the sum of each CAU* OMs from the CAUSCT3D, CAUXTF3D and CDMAPDOM OM groups. The MCTPRSO OM is subtracted in the above formula to account for the origination attempts that are redirected by MCTA to the alternate CDMA band resulting in CAUOATTS being pegged twice in this event. It is also important to note that 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 calls For 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)) x100CDMA System Performance System Performance Metrics NBSS15.0



For more information about the OM groups to use in the above formula, see For 3G packet data calls (page -13). Screened calls for 3G packet data calls due to mobile service inactive indication during network initiated dormant to active transition ( CAURELSI all sectors / CAUPGRES all sectors - MCTPRST all freq, all MCTA sectors) x 100 For network initiated dormant calls in the denominator, use the sum of OMs from OM groups CAUSCT3D and from OM groups CAUXTF3D. The MCTPRST OM is subtracted in the above formula accounting for the termination attempt that gets redirected by MCTA to the alternate CDMA band resulting in CAUPGRES OM being pegged twice in that event. It is also important to note that 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 MCTPRST OM in the above formula are replaced with MCTPRRT OM. High value of this CAURELSI OM may result in high values of the Screened calls for All Call Types Together metric, so operators should subtract this (CAURELSI OM) value from the screened calls metric to get screened calls metric due to other failure reasons.

Call setup failures due to RF failuresCall failures during setup are usually RF-related call setup failures and are classified as follows: 1. RF Access failure during origination/termination

2

RF Access failures are the call setup failures that occur when the mobile is moving from the common channel (paging or FCCCH) to the traffic channel during origination or termination (i.e. the base station is unable to receive traffic from the mobile on the reverse traffic link). 2. RF Hard Handoff failure Hard Handoff failure are the failures that occur when a mobile does not arrive on the traffic channel set up on the sector in the target system due to RF coverage issues. This section provides the following per-sector RF related failure metrics: Overall RF access failures Origination and Termination RF access failures on common channels Hard Handoff RF access failures Origination and Termination RF access failures on FCCCH channel Origination and Termination RF access failure on paging channel

411-2133-525

Standard

06.12

April 2008

Nortel Networks


This section also provides the following per-frequency RF access failure metrics for FCCCH channel: 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 due to RF Access Failure. Origination and Termination RF access failures for same band selected Origination and Termination RF access failures for same frequency selected

Formulas Following are the per sector RF access failure metrics: Overall RF access failures This metric provides the combined RF access failure for originations & terminations on the common channels and Hard Handoffs. ( (CAUERLFL + CAUHRLFL) for all sectors / Total calls attempted) x 100 Origination and termination RF access failure on common channels ( 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 CAUHATTS OM 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 RF access failures on the paging channel to assess the performance of FCCCH channel in comparison with the paging channel. Origination and termination RF access failure on FCCCH channel Since BAM OMs peg for all 2G, 3GVoice and 3GData calls combined, the metric below provides the combined RF access failure for all calls on the FCCCH channel.

CDMA


NBSS15.0



BAMERLFL for all sectors / ((BAMOATTS + BAMPGRES + BAMWPSRT)for all sectors - (MCPCOBAM + MCPCTBAM)) for all frequencies for all MCTA sectors) x 100 Origination and termination 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 all MCTA sectors) x 100 All CAU* OMs, WPSRETRY, WPSTRTRY and MCT* OMs in the above formula for paging channel represent the summation of all corresponding OMs from 2G voice, 3G voice and 3G data OM groups. This is because the BAM 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 different frequency on a different band. Following metrics provide the per frequency RF access failures for FCCCH channel. These metrics should not be compared to the per frequency RF access failures presented in the MCTA chapter since the pegging behavior of these OMs is different. Origination and termination RF access failure for same band selected This metric provides the breakdown of the sector wide RF Access failure rate on 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 100 Origination and termination RF access failure for same frequency selected This metric provides the RF access failure rate for calls that originated on a frequency and were set up on the same frequency. If the number of carrier redirections are low, then the metric below can be used to derive and compare the RF access failure rate on paging channel with the RF access failure rate of FCCCH channel. (BAMSCSFL / BAMSCSAT) for a given frequency x 100

Voice call failures during setup due to non-RF resource failuresCall failures during setup due to non-RF resource failures are classified as follows: 1. Non-RF resource failure during origination/termination 2. Non-RF resource failure during Hard Handoff.

2

411-2133-525

Standard

06.12

April 2008

Nortel Networks


Formulas Overall RF access failures ( (NORFSEFL + NRFSEFHH) for all sectors / Total calls attempted) 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 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 CAUHATTS OM 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 failures For packet data call setup during origination, BSC resources are setup first followed by BTS resources and then R-P session is setup between PCU and PDSN. Mobile could successfully arrive on the traffic channel but the R-P session setup could fail due to lack of PDSN resources. This failure maybe reported at the CAU by the BSC/PCU after CAUOSUCC OM is pegged resulting 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 session failures during null to 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 session failures during dormant to active transition of a packet data call ( DARPFLAS for all sectors) / (MIDTOAAT + NIDTOAAT) x100 3G packet data call failures (after call setup) due to RP session failures during active handoff of a packet data call ( AHRPFLAS for all sectors) / ( CAUHATTS for all sectors) x100 In the above formula use the sum of each CAU* OMs from the CAUSCT3D, CAUXTF3D and CDMAPDOM OM groups. The MCTPRSO OM is subtracted in the above formula to account for the origination attempt that isCDMA System Performance System Performance Metrics NBSS15.0



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 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. 3G packet data call failures (after call setup) due to RLP failures during null to 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 failures during dormant to active transition of a packet data call DARLPFL / (MIDTOAAT + NIDTOAAT) x100 3G packet data call failures (after call setup) due to RLP failures during active handoff of a packet data call AHRLPFL / ( CAUHATTS for all sectors) x100

Additional formulas

2

Voice call setup performance metrics on a per platform basis- (EBSC and BSC) These metric formulas measure the call setup failures and successes after resources have been successfully allocated on the EBSC (CSVS) and BSC (SBS) platforms. Call setup failures due to network related and RF related failures can be measured using these metrics. It is important to note that these metrics are only valid when NRM is the central 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 CAU and the selector element after successful resource allocation and before the radio link setup phase. Failures due to processing errors at the selector element during communication between CAU and EBSC after successful radio link setup and before successful call setup.

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

411-2133-525

Standard

06.12

April 2008

Nortel Networks


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 100 on SBS ( ESBESWFL for all CAUs / ESBSRASU for all CAUs) x 100 Percentage of call setup failures due to non-RF failures Non-RF failures include internal failures at the BSC like DSP initialization failures etc. on CSVS ( ECSNRSFL for all CAUs / ECSVRASU for all CAUs) x 100 on SBS ( ESBNRSFL for all CAUs / ESBSRASU for all CAUs) x 100 Call 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 and ESN mobiles. They also track the number of MEID mobiles that do not respond to the status request message from the CAU to retrieve the MEID value. An MTXT139 log has been introduced at the MTX to track noncomplaint 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 channel conditions, RF conditions or the mobile being unable to send the MEID in the status response message. To determine the root cause of the query failure, one should look at the Call Detail Records (CDRs) at the MTX to determine if this failure is related to mobiles that belong to particular manufacturer type.

CDMA


NBSS15.0



It is also important to note that there are no separate OMs for query failures as there 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 there is a call setup failure or a call drop due to RF related reasons. The existing Call 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 to track the carrier-sector information in event of PLCM collision. These metrics help re-evaluate the choice of the PLCM type chosen for call setup in the SelectorSubsystemMO;PlcmTypeConfig. Optimal selection of a PLCM type will help reduce the call setup failures and call drops due to PLCM 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 if there are call failures (RF related) due to pESN collisions, changing the choice of PLCM type to Allow_BS_Assigned or BS_Assigned_Preferred could lower the call failures. Percentage of call setup failures in the event of pESN PLCM collisions (PLCM_CallSetupFailuresPseudoESN / PLCM_CallSetupAttemptsPsuedoESN ) x 100 Percentage of call setup failures in the event of MEID PLCM collisions (PLCM_CallSetupFailuresMEID / PLCM_CallSetupAttemptsMEID) x 100

411-2133-525

Standard

06.12

April 2008

Nortel Networks


Percentage of call setup failures in the event of BS-assigned PLCM 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 of MEID PLCM collisions (PLCM_CallDropsMEID / PLCM_CallSetupSuccessesMEID ) x 100 Percentage of call drops in the event of BS-assigned PLCM collisions (PLCM_CallDropsBS_Assigned / PLCM_CallSetupSuccessesBS_Assigned) x 100 Additional 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

Date post:	21-Feb-2015
Category:	Documents
Upload:	daniel-chapman
View:	354 times
Download:	33 times

411-2133-525_06.12

Documents