SlideShare une entreprise Scribd logo
1  sur  20
Performance Metrics Overview
2
Performance Data
> There are 3 main sources of performance data in Nortel’s CDMA
equipment
• MTX
• BSS (BSC + BTS)
• PDSN
> Each of these are unique and comes under different format and
performance data are configured, collected, stored, and
retrieved separately on each system
> The focus for RF engineering is on the MTX and BSS side
3
Performance Data - Overview
> BSS data can provide
• XCEM usage – Per sector Traffic/Erlang
• Paging/Access performance (normal + border repage)
• Handover performance
• Power measurement (Tx/Rx)
• Data performance
> MTX data can provide
• Performance (call setup and drop call)
• Total call attempt (new and hard handoff)
• SMS statistics
• MCTA
• Authentication
• Trunk utilisation
4
 BSC – timestamp
 CPDSSubsystem – timestamp
 CSVSSubsystem – timestamp
 MCBTSSubsystem – timestamp
 CompactMCBTSSubsystem – timestamp
 SBSCSubsystem – timestamp
where timestamp is yyyymmddhhmmss
BSS Performance OM File Naming Conventions
5
BSS Data Format
> File will commence with date/timestamp
> Data line format is
|DT|Seq|Value|
Where:
DT = Data Type (5 = 16 bit word, 7 = 32 bit word)
Seq = Sequence Number
Value = Value for this half hour
6
BTS Performance Data
> The MO’s of interest for Radio engineers are :
• AdvancedFA MO,
• PowerManagement MO, and
• AdvancedSector MO.
> Every half-hour, all BTSs report the following information:
• Handoff state information
• Transmit power information
• Received power information
• Call/Handoff blocking reasons
> From these, can also deduce:
• Total carried traffic
• Available RF capacity
• Transmitter faults
• Receiver faults
7
AdvancedFA MO
Contain Carrier specific information mainly Channel element
availability and usage
 NumOfTCAvailable
Total number of channel elements available for traffic across all
channel cards after overhead channels have been subtracted
 TCEUtilMaximum
The peak number of channel elements in use simultaneously
during this half hour
8
#LOGNUM|2|OPERATIONAL
|O%:CCLN-1-CBS1:CELLS-1-CELLS1:MCBTS-1-MC800BTS136:MCBTSSUBSYSTEM-1-
MCBTSSUBSYSTEM1:ROOT-1-ROOT1:BTSCALLPROCESSING-1-
BTSCALLPROCESSING1:ADVANCEDFA-1-ADVANCEDFA1
|33.2.0.150.1.1|33.2.0.150.1.1|0x3|0|0|1
|0|14
|5|23|43
|5|24|3
|7|72|250
|7|74|0
|7|75|0
|7|76|1
|7|77|124
|7|79|0
|7|80|0
|7|81|1
|7|88|1
|7|89|1
|7|90|1
|7|91|0
#END
Peak simultaneous CCEM in use, if deployed
Reverse direction XCEM OMs
Total available CCEM, if deployed
Forward direction XCEM OMs
Actual simultaneous XCEM resources used
AdvancedFA MO
9
Advanced Sector MO
Contain :
• Origination/Termination/Soft Handoff Blocking Reasons/Counts
• Non-blocked Origination/Termination/Soft Handoff Counts
• Digital Power Averages
• Paging and Access channel utilisation
• Walsh Code utilisation
Units for Power usage is Digital gain squared
Where digital gain of a particular channel element is a value from 0 to 254
representing the voltage at the output of the element
Example Uses:
Calculate percentages of blocks due to different reasons
In conjunction with AdvancedFA MO data, estimate available forward
air link capacity
10
Advanced Sector MO: Example Log
#LOGNUM|9655
|O%:CCLN-1-C
ROOT1:BTSCAL
ADVANCEDSECT
|706.2.0.158
|5|59|0
|5|60|0
|5|61|0
|5|62|0
|5|63|0
|5|64|0
|5|65|0
|5|66|0
|5|67|0
|5|68|0
#END
11
Power Information
 MO Name: PowerManagement
 Allow engineers to determine whether sector went into software power
limiting
 Information include
RF Transmit Power Information
RF Received Power Information
Both Max and Average are captured
 In conjunction with AdvancedFA MO data, estimate available forward
and reverse air-link capacity on a per sector carrier level (CE + RF)
 Units:
 Receive power is 16*dBfW
 conversion to dBm = (value/16) – 120
 Transmit power is 16*dBm
 Conversion to dBm = (value/16)
12
PowerManagement MO
#LOGNUM|96
|O%:CCLN-1
ROOT1:BTSC
ADVANCEDSE
|710.2.0.1
|5|62|133
|5|63|131
|5|59|548
|5|64|240
|5|65|237
|5|60|556
|5|67|0
#END
13
MTX Performance Data
> 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 would include such things are MTX
memory and link utilizations, VLR and HLR transactions
> MTX specifically for CDMA-related events and normally
labelled as CAUxxx
14
How to read an MTX OM table
15
Voice Metric for a 30 minute collection period
Call Attempts = Summed across all sector - carriers
CAUCPSCT. (CAUPGRES + CAUOATTS + CAUHATTS)
+ CAUSCT3V. (CAUPGRES + CAUOATTS + CAUHATTS)
+ CAUSCT2.(WPSRETRY + WPSTRTRY) +
CAUST3V2.(WPSRETRY + WPSTRTRY) –
CAUXTFRQ.(MCTPRSO + MCTPRST) –
CAUXTF3V.(MCTPRSO + MCTPRST)
Data Metric for a 30 minute collection period
Data Call Attempts = Summed across all sector - carriers
CAUSCT3D. (CAUPGRES + CAUOATTS + CAUHATTS) –
CAUXTF3D.(MCTPRSO + MCTPRST)
MTX Performance Data
16
Drop Call Rate all scenarios across all sector - carriers
(Σ (CAUDROPR + CAUDROPN) for all sectors/ Σ (CAUOSUCC +
CAUTSUCC + CAUHSUCC) for all sectors) x 100
RF only Drop Call Rate across all sector
( Σ CAUDROPR for all sectors / Σ (CAUOSUCC + CAUTSUCC +
CAUHSUCC) for all sectors) x 100
Network only Drop Call Rate across all sector which include issues
such as “RLM locked, TCE locked, Trunk problem or a Selector
problem
( Σ CAUDROPN for all sectors / Σ (CAUOSUCC + CAUTSUCC +
CAUHSUCC) for all sectors) x 100
MTX Drop Call Rate
17
Successful call attempt across all sector - carriers
(CAUOSUCC + CAUTSUCC + CAUHSUCC) for all sectors
Unsuccessful Call Attempt across all sector
(CAUOBLKS + CAUTBLKS + CAUHBLKS + CAUORLS + CAUTRLS + CAUHRLS +
CAUORODR + CAUERLFL + CAUHRLFL + MISCFLT + NORFSEFL + NRFSEFHH +
NWKFLBS - (WQTOUT + WQOVFL + WINVALDQ) for all sectors- MCTPRSO - MCTPRST
+ MCTPRRO + MCTPRRT for all frequencies for all sectors
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
> NORFS - Non-RF resource failure during origination or termination, NRFSEFHH Non-RF
resource failure during Hard Handoff
> MCTPRST- MCTa Paging channel Redirection Successful for call Termination. Pegged,
along with MCTPGRES and CAUPGRES, when the mobile re-send a page response after
the mobile was redirected to the alternate band.
> WQTOUT - WPS Queue failure due to queue TimeOUT, Wireless Priority Service
Operational Measurements, Winvaldq - WPS total INVALiD originations while Queued.
> NWKFLBS - NetWork rp session FaiLure Before Service connect completion is pegged
when RP session setup failures for packet data calls before service connect completion
> MISCFLT - MISCellaneous Faults
MTX Access Failure Rate
18
Call Attempt Formulas
Traffic Type Call Attempt Formula
Packet Data = CAUSCT3D.(CAUPGRES + CAUOATTS + CAUHATTS)
Total SMS
= CAUDATSC.(SMOCSRAC + SMOATTAC + SMOATBTC +
SMSPGRES + SMSPRRES + SMSDVCAT)
SMS Over Traffic Channel = CAUDATSC.(SMOCSRAC + SMSORATS)
Total Voice (2G + 3G)
= CAUCPSCT.(CAUPGRES + CAUOATTS + CAUHATTS) +
CAUSCT3V.(CAUPGRES + CAUOATTS + CAUHATTS) -
CAUXTFRQ.(MCTPRSO + MCTPRST) -
CAUXTF3V.(MCTPRSO + MCTPRST) +
CAUSCT2.WPSRETRY + CAUST3V2.WPSRETRY
The MCTPRSO and MCTPRST OMs are subtracted in the above formula to account
for the origination or termination attempts that get redirected by MCTA to the alternate
CDMA band resulting in MCTORIGS or MCTPGRES OM being pegged twice in those
events – not really applicable for Bakrie
19
SMS Attempts Calculation
Termination - Over Busy Traffic Channel
= 100 * CAUDATSC.SMSDVCAT / CAUDATSC.(SMSPGRES
+ SMSPRRES + SMSDVCAT)
Termination - Over Idle Traffic Channel
= 100 * CAUDATSC.SMSORATS / CAUDATSC.(SMSPGRES
+ SMSPRRES + SMSDVCAT)
Origination - Over Idle Traffic Channel
= 100 * CAUDATSC.SMOCSRAC /
CAUDATSC.(SMOATTAC + SMOCSRAC + SMOATBTC)
Termination - Over Paging Channel
= 100 * CAUDATSC.SMSTATPG / CAUDATSC.(SMSPGRES
+ SMSPRRES + SMSDVCAT)
Origination - Over Access Channel
= 100 * CAUDATSC.SMOATTAC / CAUDATSC.(SMOATTAC
+ SMOCSRAC + SMOATBTC)
Origination - Over Busy Traffic Channel
= 100 * CAUDATSC.SMOATBTC / CAUDATSC.(SMOATTAC
+ SMOCSRAC + SMOATBTC)
Metric Formula
20
SMS Origination and Termination
Failure Metrics
Metric Formula
Origination - Access Channel Failure Rate = 100 * CAUDATSC.SMOFAIAC / CAUDATSC.SMOATTAC
Origination - Radio Link Setup Failure Rate - Traffic Channel = 100 * CAUDATSC.SMOCSFTC / CAUDATSC.SMOCSRAC
Origination - Idle Traffic Channel Delivery Failure Rate = 100 * CAUDATSC.SMOFAITC / CAUDATSC.SMOATITC
Origination - Data Burst Failure Rate = 100 * CAUDATSY.SMODBRTO / CAUDATSC.SMOCSSTC
Origination - Idle Mobile Failure Rate
= 100 * (CAUDATSC.SMOFAIAC + CAUDATSC.SMOCSFTC +
CAUDATSC.SMSORCFL + CAUDATSC.SMOFAITC +
CAUDATSY.SMODBRTO) / (CAUDATSC.SMOATTAC +
CAUDATSC.SMOCSRAC)
Origination - In-Call Mobile Failure Rate = 100 * CAUDATSC.SMOFABTC / CAUDATSC.SMOATBTC
Termination - Paging Channel Failure Rate = 100 * CAUDATSC.SMSTFLPG / CAUDATSC.SMSTATPG
Termination - Radio Link Setup Failure Rate - Traffic Channel = 100 * CAUDATSC.SMSTMCFL / CAUDATSC.SMSORATS
Termination - In-Call Mobile Failure Rate = 100 * CAUDATSC.SMSDVCFL / CAUDATSC.SMSDVCAT
Termination - Idle Traffic Channel Delivery Failure Rate = 100 * CAUDATSC.SMSTFLTC / CAUDATS2.SMSTATTC
Termination - Idle Mobile Failure Rate
= 100 * (CAUDATSC.SMSTFLPG + CAUDATSC.SMSTMCFL +
CAUDATSC.SMSTFLTC) / (CAUDATSC.SMSPGRES +
CAUDATSC.SMSPRRES)
OM definitions and Metric can be found in NTP 411-2133-525

Contenu connexe

Similaire à Performance Metrics Overview

Fullgsm overviewmodified-111004024904-phpapp01
Fullgsm overviewmodified-111004024904-phpapp01Fullgsm overviewmodified-111004024904-phpapp01
Fullgsm overviewmodified-111004024904-phpapp01
Ram Prasath
 
Bsspar1 s14 chapter 02_radio_resource_administration_v1.1
Bsspar1 s14 chapter 02_radio_resource_administration_v1.1Bsspar1 s14 chapter 02_radio_resource_administration_v1.1
Bsspar1 s14 chapter 02_radio_resource_administration_v1.1
Simon Aja
 
L2 MAC LTE PROCEDURES revC
L2 MAC LTE PROCEDURES revCL2 MAC LTE PROCEDURES revC
L2 MAC LTE PROCEDURES revC
Vincent Daumont
 
6 Weeks Industrial Training In Telecom In Chandigarh
6 Weeks Industrial Training In Telecom In Chandigarh6 Weeks Industrial Training In Telecom In Chandigarh
6 Weeks Industrial Training In Telecom In Chandigarh
Arcadian Learning
 

Similaire à Performance Metrics Overview (20)

Gsm Cell Planning And Optimization
Gsm Cell Planning And OptimizationGsm Cell Planning And Optimization
Gsm Cell Planning And Optimization
 
CDMA BSC 6600
CDMA BSC 6600CDMA BSC 6600
CDMA BSC 6600
 
BASIC GSM
BASIC GSMBASIC GSM
BASIC GSM
 
GSM FRAME STRUCTURE.pptx
GSM FRAME STRUCTURE.pptxGSM FRAME STRUCTURE.pptx
GSM FRAME STRUCTURE.pptx
 
Parameters for drive test
Parameters for drive testParameters for drive test
Parameters for drive test
 
Ttsl orissa-egprs-download-throughput-improved-new
Ttsl orissa-egprs-download-throughput-improved-newTtsl orissa-egprs-download-throughput-improved-new
Ttsl orissa-egprs-download-throughput-improved-new
 
Signalling in EPC/LTE
Signalling in EPC/LTESignalling in EPC/LTE
Signalling in EPC/LTE
 
Fullgsm overviewmodified-111004024904-phpapp01
Fullgsm overviewmodified-111004024904-phpapp01Fullgsm overviewmodified-111004024904-phpapp01
Fullgsm overviewmodified-111004024904-phpapp01
 
Bsspar1 s14 chapter 02_radio_resource_administration_v1.1
Bsspar1 s14 chapter 02_radio_resource_administration_v1.1Bsspar1 s14 chapter 02_radio_resource_administration_v1.1
Bsspar1 s14 chapter 02_radio_resource_administration_v1.1
 
L2 MAC LTE PROCEDURES revC
L2 MAC LTE PROCEDURES revCL2 MAC LTE PROCEDURES revC
L2 MAC LTE PROCEDURES revC
 
39540950 gsm-ion-course-130814024028-phpapp01
39540950 gsm-ion-course-130814024028-phpapp0139540950 gsm-ion-course-130814024028-phpapp01
39540950 gsm-ion-course-130814024028-phpapp01
 
UMTS OVERVIEW
UMTS OVERVIEWUMTS OVERVIEW
UMTS OVERVIEW
 
ZTE (3GPP Specification Evolution).ppt
ZTE (3GPP Specification Evolution).pptZTE (3GPP Specification Evolution).ppt
ZTE (3GPP Specification Evolution).ppt
 
Hsdpa analysis
Hsdpa analysisHsdpa analysis
Hsdpa analysis
 
6 Weeks Industrial Training In Telecom In Chandigarh
6 Weeks Industrial Training In Telecom In Chandigarh6 Weeks Industrial Training In Telecom In Chandigarh
6 Weeks Industrial Training In Telecom In Chandigarh
 
Sanjay
SanjaySanjay
Sanjay
 
Channelconfih s9
Channelconfih s9Channelconfih s9
Channelconfih s9
 
Full gsm overview (modified)
Full gsm overview  (modified)Full gsm overview  (modified)
Full gsm overview (modified)
 
Ch3 air interface
Ch3 air interfaceCh3 air interface
Ch3 air interface
 
4G-Fourth Generation Mobile Communication System
4G-Fourth Generation Mobile Communication System4G-Fourth Generation Mobile Communication System
4G-Fourth Generation Mobile Communication System
 

Dernier

Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
WSO2
 

Dernier (20)

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
 
Understanding the FAA Part 107 License ..
Understanding the FAA Part 107 License ..Understanding the FAA Part 107 License ..
Understanding the FAA Part 107 License ..
 
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ..."I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
 
Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)
 
MINDCTI Revenue Release Quarter One 2024
MINDCTI Revenue Release Quarter One 2024MINDCTI Revenue Release Quarter One 2024
MINDCTI Revenue Release Quarter One 2024
 
WSO2's API Vision: Unifying Control, Empowering Developers
WSO2's API Vision: Unifying Control, Empowering DevelopersWSO2's API Vision: Unifying Control, Empowering Developers
WSO2's API Vision: Unifying Control, Empowering Developers
 
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
 
CNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In PakistanCNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In Pakistan
 
ICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesICT role in 21st century education and its challenges
ICT role in 21st century education and its challenges
 
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWEREMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
 
Six Myths about Ontologies: The Basics of Formal Ontology
Six Myths about Ontologies: The Basics of Formal OntologySix Myths about Ontologies: The Basics of Formal Ontology
Six Myths about Ontologies: The Basics of Formal Ontology
 
Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...
 
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...
 
Vector Search -An Introduction in Oracle Database 23ai.pptx
Vector Search -An Introduction in Oracle Database 23ai.pptxVector Search -An Introduction in Oracle Database 23ai.pptx
Vector Search -An Introduction in Oracle Database 23ai.pptx
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor Presentation
 
Spring Boot vs Quarkus the ultimate battle - DevoxxUK
Spring Boot vs Quarkus the ultimate battle - DevoxxUKSpring Boot vs Quarkus the ultimate battle - DevoxxUK
Spring Boot vs Quarkus the ultimate battle - DevoxxUK
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
 
FWD Group - Insurer Innovation Award 2024
FWD Group - Insurer Innovation Award 2024FWD Group - Insurer Innovation Award 2024
FWD Group - Insurer Innovation Award 2024
 
presentation ICT roal in 21st century education
presentation ICT roal in 21st century educationpresentation ICT roal in 21st century education
presentation ICT roal in 21st century education
 
Artificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : UncertaintyArtificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : Uncertainty
 

Performance Metrics Overview

  • 2. 2 Performance Data > There are 3 main sources of performance data in Nortel’s CDMA equipment • MTX • BSS (BSC + BTS) • PDSN > Each of these are unique and comes under different format and performance data are configured, collected, stored, and retrieved separately on each system > The focus for RF engineering is on the MTX and BSS side
  • 3. 3 Performance Data - Overview > BSS data can provide • XCEM usage – Per sector Traffic/Erlang • Paging/Access performance (normal + border repage) • Handover performance • Power measurement (Tx/Rx) • Data performance > MTX data can provide • Performance (call setup and drop call) • Total call attempt (new and hard handoff) • SMS statistics • MCTA • Authentication • Trunk utilisation
  • 4. 4  BSC – timestamp  CPDSSubsystem – timestamp  CSVSSubsystem – timestamp  MCBTSSubsystem – timestamp  CompactMCBTSSubsystem – timestamp  SBSCSubsystem – timestamp where timestamp is yyyymmddhhmmss BSS Performance OM File Naming Conventions
  • 5. 5 BSS Data Format > File will commence with date/timestamp > Data line format is |DT|Seq|Value| Where: DT = Data Type (5 = 16 bit word, 7 = 32 bit word) Seq = Sequence Number Value = Value for this half hour
  • 6. 6 BTS Performance Data > The MO’s of interest for Radio engineers are : • AdvancedFA MO, • PowerManagement MO, and • AdvancedSector MO. > Every half-hour, all BTSs report the following information: • Handoff state information • Transmit power information • Received power information • Call/Handoff blocking reasons > From these, can also deduce: • Total carried traffic • Available RF capacity • Transmitter faults • Receiver faults
  • 7. 7 AdvancedFA MO Contain Carrier specific information mainly Channel element availability and usage  NumOfTCAvailable Total number of channel elements available for traffic across all channel cards after overhead channels have been subtracted  TCEUtilMaximum The peak number of channel elements in use simultaneously during this half hour
  • 9. 9 Advanced Sector MO Contain : • Origination/Termination/Soft Handoff Blocking Reasons/Counts • Non-blocked Origination/Termination/Soft Handoff Counts • Digital Power Averages • Paging and Access channel utilisation • Walsh Code utilisation Units for Power usage is Digital gain squared Where digital gain of a particular channel element is a value from 0 to 254 representing the voltage at the output of the element Example Uses: Calculate percentages of blocks due to different reasons In conjunction with AdvancedFA MO data, estimate available forward air link capacity
  • 10. 10 Advanced Sector MO: Example Log #LOGNUM|9655 |O%:CCLN-1-C ROOT1:BTSCAL ADVANCEDSECT |706.2.0.158 |5|59|0 |5|60|0 |5|61|0 |5|62|0 |5|63|0 |5|64|0 |5|65|0 |5|66|0 |5|67|0 |5|68|0 #END
  • 11. 11 Power Information  MO Name: PowerManagement  Allow engineers to determine whether sector went into software power limiting  Information include RF Transmit Power Information RF Received Power Information Both Max and Average are captured  In conjunction with AdvancedFA MO data, estimate available forward and reverse air-link capacity on a per sector carrier level (CE + RF)  Units:  Receive power is 16*dBfW  conversion to dBm = (value/16) – 120  Transmit power is 16*dBm  Conversion to dBm = (value/16)
  • 13. 13 MTX Performance Data > 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 would include such things are MTX memory and link utilizations, VLR and HLR transactions > MTX specifically for CDMA-related events and normally labelled as CAUxxx
  • 14. 14 How to read an MTX OM table
  • 15. 15 Voice Metric for a 30 minute collection period Call Attempts = Summed across all sector - carriers CAUCPSCT. (CAUPGRES + CAUOATTS + CAUHATTS) + CAUSCT3V. (CAUPGRES + CAUOATTS + CAUHATTS) + CAUSCT2.(WPSRETRY + WPSTRTRY) + CAUST3V2.(WPSRETRY + WPSTRTRY) – CAUXTFRQ.(MCTPRSO + MCTPRST) – CAUXTF3V.(MCTPRSO + MCTPRST) Data Metric for a 30 minute collection period Data Call Attempts = Summed across all sector - carriers CAUSCT3D. (CAUPGRES + CAUOATTS + CAUHATTS) – CAUXTF3D.(MCTPRSO + MCTPRST) MTX Performance Data
  • 16. 16 Drop Call Rate all scenarios across all sector - carriers (Σ (CAUDROPR + CAUDROPN) for all sectors/ Σ (CAUOSUCC + CAUTSUCC + CAUHSUCC) for all sectors) x 100 RF only Drop Call Rate across all sector ( Σ CAUDROPR for all sectors / Σ (CAUOSUCC + CAUTSUCC + CAUHSUCC) for all sectors) x 100 Network only Drop Call Rate across all sector which include issues such as “RLM locked, TCE locked, Trunk problem or a Selector problem ( Σ CAUDROPN for all sectors / Σ (CAUOSUCC + CAUTSUCC + CAUHSUCC) for all sectors) x 100 MTX Drop Call Rate
  • 17. 17 Successful call attempt across all sector - carriers (CAUOSUCC + CAUTSUCC + CAUHSUCC) for all sectors Unsuccessful Call Attempt across all sector (CAUOBLKS + CAUTBLKS + CAUHBLKS + CAUORLS + CAUTRLS + CAUHRLS + CAUORODR + CAUERLFL + CAUHRLFL + MISCFLT + NORFSEFL + NRFSEFHH + NWKFLBS - (WQTOUT + WQOVFL + WINVALDQ) for all sectors- MCTPRSO - MCTPRST + MCTPRRO + MCTPRRT for all frequencies for all sectors 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 > NORFS - Non-RF resource failure during origination or termination, NRFSEFHH Non-RF resource failure during Hard Handoff > MCTPRST- MCTa Paging channel Redirection Successful for call Termination. Pegged, along with MCTPGRES and CAUPGRES, when the mobile re-send a page response after the mobile was redirected to the alternate band. > WQTOUT - WPS Queue failure due to queue TimeOUT, Wireless Priority Service Operational Measurements, Winvaldq - WPS total INVALiD originations while Queued. > NWKFLBS - NetWork rp session FaiLure Before Service connect completion is pegged when RP session setup failures for packet data calls before service connect completion > MISCFLT - MISCellaneous Faults MTX Access Failure Rate
  • 18. 18 Call Attempt Formulas Traffic Type Call Attempt Formula Packet Data = CAUSCT3D.(CAUPGRES + CAUOATTS + CAUHATTS) Total SMS = CAUDATSC.(SMOCSRAC + SMOATTAC + SMOATBTC + SMSPGRES + SMSPRRES + SMSDVCAT) SMS Over Traffic Channel = CAUDATSC.(SMOCSRAC + SMSORATS) Total Voice (2G + 3G) = CAUCPSCT.(CAUPGRES + CAUOATTS + CAUHATTS) + CAUSCT3V.(CAUPGRES + CAUOATTS + CAUHATTS) - CAUXTFRQ.(MCTPRSO + MCTPRST) - CAUXTF3V.(MCTPRSO + MCTPRST) + CAUSCT2.WPSRETRY + CAUST3V2.WPSRETRY The MCTPRSO and MCTPRST OMs are subtracted in the above formula to account for the origination or termination attempts that get redirected by MCTA to the alternate CDMA band resulting in MCTORIGS or MCTPGRES OM being pegged twice in those events – not really applicable for Bakrie
  • 19. 19 SMS Attempts Calculation Termination - Over Busy Traffic Channel = 100 * CAUDATSC.SMSDVCAT / CAUDATSC.(SMSPGRES + SMSPRRES + SMSDVCAT) Termination - Over Idle Traffic Channel = 100 * CAUDATSC.SMSORATS / CAUDATSC.(SMSPGRES + SMSPRRES + SMSDVCAT) Origination - Over Idle Traffic Channel = 100 * CAUDATSC.SMOCSRAC / CAUDATSC.(SMOATTAC + SMOCSRAC + SMOATBTC) Termination - Over Paging Channel = 100 * CAUDATSC.SMSTATPG / CAUDATSC.(SMSPGRES + SMSPRRES + SMSDVCAT) Origination - Over Access Channel = 100 * CAUDATSC.SMOATTAC / CAUDATSC.(SMOATTAC + SMOCSRAC + SMOATBTC) Origination - Over Busy Traffic Channel = 100 * CAUDATSC.SMOATBTC / CAUDATSC.(SMOATTAC + SMOCSRAC + SMOATBTC) Metric Formula
  • 20. 20 SMS Origination and Termination Failure Metrics Metric Formula Origination - Access Channel Failure Rate = 100 * CAUDATSC.SMOFAIAC / CAUDATSC.SMOATTAC Origination - Radio Link Setup Failure Rate - Traffic Channel = 100 * CAUDATSC.SMOCSFTC / CAUDATSC.SMOCSRAC Origination - Idle Traffic Channel Delivery Failure Rate = 100 * CAUDATSC.SMOFAITC / CAUDATSC.SMOATITC Origination - Data Burst Failure Rate = 100 * CAUDATSY.SMODBRTO / CAUDATSC.SMOCSSTC Origination - Idle Mobile Failure Rate = 100 * (CAUDATSC.SMOFAIAC + CAUDATSC.SMOCSFTC + CAUDATSC.SMSORCFL + CAUDATSC.SMOFAITC + CAUDATSY.SMODBRTO) / (CAUDATSC.SMOATTAC + CAUDATSC.SMOCSRAC) Origination - In-Call Mobile Failure Rate = 100 * CAUDATSC.SMOFABTC / CAUDATSC.SMOATBTC Termination - Paging Channel Failure Rate = 100 * CAUDATSC.SMSTFLPG / CAUDATSC.SMSTATPG Termination - Radio Link Setup Failure Rate - Traffic Channel = 100 * CAUDATSC.SMSTMCFL / CAUDATSC.SMSORATS Termination - In-Call Mobile Failure Rate = 100 * CAUDATSC.SMSDVCFL / CAUDATSC.SMSDVCAT Termination - Idle Traffic Channel Delivery Failure Rate = 100 * CAUDATSC.SMSTFLTC / CAUDATS2.SMSTATTC Termination - Idle Mobile Failure Rate = 100 * (CAUDATSC.SMSTFLPG + CAUDATSC.SMSTMCFL + CAUDATSC.SMSTFLTC) / (CAUDATSC.SMSPGRES + CAUDATSC.SMSPRRES) OM definitions and Metric can be found in NTP 411-2133-525