The document discusses optimization of the top 10 worst performing cells in a network. It covers analyzing dropped call statistics to identify problem cells, investigating reasons for dropped calls, and making configuration changes or troubleshooting issues to improve network performance. The objectives are to monitor network performance, improve it, and meet key performance indicators by focusing on optimizing the cells with the highest dropped call rates.
The document discusses key performance indicators (KPIs) for cellular networks and provides relationships between network components and their capacities. It also analyzes reasons for call blocking, dropping, and failures during call setup and solutions to address them, including parameter tuning, hardware checks, interference mitigation, and useful reports.
Channel failure rate above defined thresholdaabaap
The document discusses troubleshooting channel failure rate alarms on 2G NSN networks. It provides details on what the alarm means, including supplementary information fields to identify the faulty channel. It recommends finding the cause of alarms by checking channel release messages and restoring channels by locking and unlocking them. Parameters affecting the alarm are listed, and it is noted the alarm will automatically cancel after the measurement period if the situation is resolved without actions. Responses suggest checking the Abis allocation between BTS and BSC, performing hardware replacements, and conducting a sector reset as initial steps to resolve the issue.
This document discusses key performance indicators (KPIs) for monitoring a GSM network and reasons for and solutions to common issues. It provides relationships between network elements, defines terms like SD blocking and dropping, TCH blocking and assignment, and TCH dropping. Causes of and fixes for these issues are outlined, such as adjusting parameters, adding TRXs, improving hardware, and tuning neighbors. Reports for analyzing each issue are also listed.
This document discusses key performance indicators (KPIs) for mobile network analysis. It provides information on relationships between network elements, reasons for poor KPI values like service drop blocking and dropping, and potential solutions. KPIs to monitor include service drop blocking, service drop, traffic channel blocking, traffic channel assignment, traffic channel drop, and handover success rate. Causes of issues include hardware problems, interference, parameter misconfiguration, and overlapping coverage. Solutions involve checking configurations, drive testing, adding resources, retuning parameters, and resolving hardware faults.
The document discusses key performance indicators (KPIs) for monitoring a GSM network, including reasons for and solutions to issues like SD blocking, SD drop, TCH blocking, TCH assignment failure, and TCH drop. It provides technical details on the relationships between network elements like BSCs, BTSs, TRXs, and timeslots. It also lists common causes of the issues like hardware faults, interference, parameter misconfiguration, and outlines steps to troubleshoot and resolve problems.
Nokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentationmohammed khairy
This document discusses key performance indicators (KPIs) for monitoring a GSM network and reasons for and solutions to common issues. It provides relationships between different network elements and describes concepts like SD blocking, SD drop, TCH blocking, TCH assignment, TCH drop, and handover success rate (HOSR). For each KPI, it outlines potential causes for degradation and recommendations to address hardware faults, interference, parameter misconfiguration, and other problems.
This document provides guidelines for analyzing problems in a mobile network. It presents decision trees and flowcharts to help troubleshoot issues related to call setup success rate, SDCCH assignment, SDCCH congestion, TCH call drop, TCH seizure failure rate, TCH blocking rate, abnormal traffic patterns, idle interference, outgoing handover failure rate, and incoming handover failure rate. Potential causes are identified at each step to direct further investigation and resolution of issues.
1. The document analyzes key performance indicators related to SDCCH establishment success rates in an AFC radio network, which have been observed to be low at 89%.
2. A main cause identified for the low SDCCH establishment is timer T3101 expiration after sending Immediate Assignment messages, indicating 11% failure due to no response from mobile stations. This could be due to "phantom" random access bursts or abnormal mobile station behavior.
3. Other potential contributing factors discussed include periodic registration interval being too short, location area border cells, cell broadcast usage, and low signal strength, but clear relationships between these and SDCCH establishment success rates were not found based on the investigation. The document outlines further
The document discusses key performance indicators (KPIs) for cellular networks and provides relationships between network components and their capacities. It also analyzes reasons for call blocking, dropping, and failures during call setup and solutions to address them, including parameter tuning, hardware checks, interference mitigation, and useful reports.
Channel failure rate above defined thresholdaabaap
The document discusses troubleshooting channel failure rate alarms on 2G NSN networks. It provides details on what the alarm means, including supplementary information fields to identify the faulty channel. It recommends finding the cause of alarms by checking channel release messages and restoring channels by locking and unlocking them. Parameters affecting the alarm are listed, and it is noted the alarm will automatically cancel after the measurement period if the situation is resolved without actions. Responses suggest checking the Abis allocation between BTS and BSC, performing hardware replacements, and conducting a sector reset as initial steps to resolve the issue.
This document discusses key performance indicators (KPIs) for monitoring a GSM network and reasons for and solutions to common issues. It provides relationships between network elements, defines terms like SD blocking and dropping, TCH blocking and assignment, and TCH dropping. Causes of and fixes for these issues are outlined, such as adjusting parameters, adding TRXs, improving hardware, and tuning neighbors. Reports for analyzing each issue are also listed.
This document discusses key performance indicators (KPIs) for mobile network analysis. It provides information on relationships between network elements, reasons for poor KPI values like service drop blocking and dropping, and potential solutions. KPIs to monitor include service drop blocking, service drop, traffic channel blocking, traffic channel assignment, traffic channel drop, and handover success rate. Causes of issues include hardware problems, interference, parameter misconfiguration, and overlapping coverage. Solutions involve checking configurations, drive testing, adding resources, retuning parameters, and resolving hardware faults.
The document discusses key performance indicators (KPIs) for monitoring a GSM network, including reasons for and solutions to issues like SD blocking, SD drop, TCH blocking, TCH assignment failure, and TCH drop. It provides technical details on the relationships between network elements like BSCs, BTSs, TRXs, and timeslots. It also lists common causes of the issues like hardware faults, interference, parameter misconfiguration, and outlines steps to troubleshoot and resolve problems.
Nokia gsm-kpi-analysis-based-on-daily-monitoring-basis-presentationmohammed khairy
This document discusses key performance indicators (KPIs) for monitoring a GSM network and reasons for and solutions to common issues. It provides relationships between different network elements and describes concepts like SD blocking, SD drop, TCH blocking, TCH assignment, TCH drop, and handover success rate (HOSR). For each KPI, it outlines potential causes for degradation and recommendations to address hardware faults, interference, parameter misconfiguration, and other problems.
This document provides guidelines for analyzing problems in a mobile network. It presents decision trees and flowcharts to help troubleshoot issues related to call setup success rate, SDCCH assignment, SDCCH congestion, TCH call drop, TCH seizure failure rate, TCH blocking rate, abnormal traffic patterns, idle interference, outgoing handover failure rate, and incoming handover failure rate. Potential causes are identified at each step to direct further investigation and resolution of issues.
1. The document analyzes key performance indicators related to SDCCH establishment success rates in an AFC radio network, which have been observed to be low at 89%.
2. A main cause identified for the low SDCCH establishment is timer T3101 expiration after sending Immediate Assignment messages, indicating 11% failure due to no response from mobile stations. This could be due to "phantom" random access bursts or abnormal mobile station behavior.
3. Other potential contributing factors discussed include periodic registration interval being too short, location area border cells, cell broadcast usage, and low signal strength, but clear relationships between these and SDCCH establishment success rates were not found based on the investigation. The document outlines further
This document discusses key performance indicators (KPIs) related to a mobile network. It provides information on the relationships between different network elements like BSCs, BTSs, TRXs. It defines terms like SD blocking, SD drop, TCH blocking, TCH assignment, TCH drop and reasons they may occur. Solutions for reducing each issue are provided like changing parameters, adding hardware, improving coverage. Reports for analyzing each problem are listed.
This document provides guidance on tuning parameters to slow down inter-RAT cell reselections in UMTS networks. It discusses the Treselection timer, hysteresis between 3G and 2G cell reselections, and PRACH power ramping parameters. Recommended values for these parameters are given to reduce unnecessary reselections while maintaining call setup success rates. Key performance indicators for analyzing the impact of parameter changes on reselection rates and call performance are also identified.
This document discusses using signal strength and path loss data from 208 reports and OSS to identify hardware faults in cells. Case studies show how comparing path loss between transmit-receive channels within sectors can expose problems like loose cables or connectors. For example, much higher path losses (>20 dB difference) for some channels in a sector indicate a combiner issue. Differences only in uplink path loss between channels suggest a receiver cable problem. The document recommends using pivot tables to flag cells with over 10 dB variation in downlink or uplink path losses between channels for further 208 report analysis to identify worst performing cells needing attention.
This document describes the process of optimizing GSM900/1800 mobile networks. Key metrics are monitored daily, weekly, and monthly to check network health using a tool called Optima. Daily counters include call setup success rate, dropped calls, handover failures, and congestion. Issues like low call success rates could be due to problems like SDCCH congestion, phantom RACHs, CM service rejects, or TCH failures. Weekly and monthly statistics provide further insight into trends, retention, accessibility, load, and overall performance. Reports evaluate capacity and optimization progress.
This document discusses key performance indicators (KPIs) for a mobile network and reasons for and solutions to common issues. It provides relationships between different network elements and defines KPIs like SD blocking, SD drop, TCH blocking, TCH assignment, and TCH drop. For each KPI, it describes what causes poor performance, such as hardware faults, interference, parameter issues, and provides potential solutions like adding channels, improving coverage, adjusting timers and thresholds. Reports to analyze specific problems are also listed.
The document provides an overview and analysis flow for optimizing the performance of a mobile network. It discusses various problems that can occur like low availability of control channels, congestion on signaling and traffic channels, and high drop call rates. For each problem, it lists probable causes and recommends actions to identify the issue and solutions to resolve it, such as adjusting configuration parameters, adding network capacity, or improving frequency planning. MML commands are also provided to check device logs, resources, and performance statistics for troubleshooting purposes.
This document provides solutions for code congestion in mobile networks. It recommends checking certain counters to detect code congestion and expanding to two carriers if congestion is severe in a single carrier cell. The document also recommends using a Load-based Dynamic Rate (LDR) algorithm to solve code congestion. It provides the specific MML configuration to switch on LDR and set the LDR actions, and lists counters that can be monitored to check the effect of the LDR actions.
This document discusses radio resource optimization parameters in GSM networks. It covers topics like idle parameter optimization, power control, handover control, radio resource administration, measurement processing, signaling channel mapping, traffic channel mapping, paging parameters, access grant channel parameters, frequency reuse, and frequency hopping techniques. Diagrams and examples are provided to illustrate concepts like TDMA frame structure, logical and physical channel organization, and capacity calculations.
This document outlines processes for optimizing key performance indicators (KPIs) in a cellular network, including SDCCH assignment success rate, SDCCH drop rate, RACH success rate, TCH assignment success rate, Rx quality, handover success rate (HOSR), and TCH drop rate. For each KPI, it defines the measurement, identifies potential causes of poor performance, and provides steps to analyze detailed reports, check for issues like configuration errors or RF problems, and refine the network configuration to improve the KPI.
This document discusses various causes and troubleshooting steps related to 2G call drops and unsuccessful handovers. It addresses issues like low signal strength, interference, incorrect parameter settings, transmission faults, hardware faults, and more. The key performance indicators of TCH Drop Rate and Handover Failure Rate are defined. Causes of dropped calls on traffic channels include excessive timing advance, low signal strength, poor quality, sudden loss of connection, and other factors. Investigation steps provided include checking error logs, parameters, neighboring cell definitions, transmission quality, antenna installation, and more.
This document summarizes various LTE KPIs and performance metrics related to random access, RRC connection establishment, ERAB establishment, and issues that may impact them. It provides potential causes for high values or failures in these metrics as well as recommended actions to investigate like checking RF parameters, capacity, licenses, alarms, configuration, and optimizing physical antenna settings.
There are several ways to improve TBF Drop rates mentioned in the document:
1. Check frequency usage and retransmission rates to identify potential frequency issues and improve carrier to interference ratios to reduce interference.
2. Use the transmitter with the best broadcast control channel for packet data channels.
3. Ensure GPRS link adaptation is enabled and limit coding schemes to the more robust MCS7 if frequency changes don't help.
4. Reduce the number of users per packet data channel and check packet control unit congestion and utilization.
This document provides parameters for radio network configuration in a Nokia wireless network. It contains over 100 parameters organized in sections for the BSC, BCF, BTS, adjacent cells, and other settings. The parameters define thresholds, timers, and options that control functions like call handling, congestion management, handover processing, and radio resource allocation. The document is intended only for Nokia customers and subject to change without notice.
This document discusses possible reasons for SDCCH drops due to "Other Reasons" and provides steps to analyze and address the issue. It lists hardware faults, parameter definition issues, DIP status problems, frequency interference, C7 link stability, and improper MSC parameter definition as potential causes. The document advises checking logs, parameters, DIP quality, interference levels, C7 link commands, and MSC settings related to call setup, paging, location updating, authentication, ciphering, and SMS when analyzing SDCCH drops.
This document provides an overview of analyzing and troubleshooting SDCCH drop rate issues. It describes the SDCCH channel and how it is used, defines the KPI formula for calculating SDCCH drop rate, lists the counters involved in the KPI, and presents a flow chart of the SDCCH assignment process. Tools that can be used for the analysis are also identified, including Business Objects, MCOM, ZXG10 OMCR, and TEMS Investigation.
3 g huawei ran resource monitoring and management recommendedMery Koto
The document discusses monitoring resources in a Huawei WCDMA network to avoid congestion and blockages. It describes monitoring resources at the NodeB and cell levels like CE cards, licenses, OVSF codes, power levels, and Iub bandwidth. Counters are presented to monitor traffic, KPIs, resource usage, and rejections due to congestion. The resource consumption of different services is also analyzed to understand network characteristics and identify if resources are sufficient for desired services.
Day1 slot3 br radio configuration assessment and bss radio configurationv0.4fdr1975
The document discusses radio configuration assessment and planning for both a Broadband Radio (BR) system and a Base Station Subsystem (BSS). It provides examples of configuration settings for signaling allocation, traffic channel allocation, and packet switched capacity for a cell with either 8 or 10 TRXs. Key parameters for both the BR and BSS configurations are also defined.
The document describes parameter handling for Nokia's BSC/TCSM base station controller. It contains over 20 commands for modifying parameters related to general BSC configuration, radio network supervision, quality of service, GPRS, and background data activation. The commands allow operators to control functions like priority levels, dynamic frequency allocation, network monitoring thresholds, and more. Release notes describe changes between documentation issues, such as new parameters and updated output formats.
Bsspar1 s14 chapter 02_radio_resource_administration_v1.1Simon Aja
1. The document discusses intellectual property rights for Nokia Siemens Networks training materials, stating that Nokia Siemens Networks owns exclusive copyright and that individuals can only use materials for personal development and cannot pass them on without permission.
2. It then provides an overview of TDMA frame structures, logical and physical channels, and their mapping and parameters.
3. The document describes concepts like base station identity codes, training sequence codes, frequency reuse, and frequency hopping parameters.
How to perform trouble shooting based on countersAbdul Muin
This document provides guidance on troubleshooting radio network issues based on counter analysis. It discusses various counters related to RRC connection setup, access, and active phases. For each failure cause, it describes steps like checking alarm history, measurements, parameters, and traffic tables to identify potential root causes such as coverage issues, configuration mistakes, or hardware problems. The document uses examples and case studies to illustrate how to methodically analyze counters and narrow down issues.
This document discusses optimization of radio parameters in WCDMA networks. It describes the process of parameter optimization including collecting configuration, signaling, drive test and statistics data. It then lists common radio parameter optimization cases such as coverage, handover, call drop rates, access control and signal quality. Specific cases covered in more detail include increasing PCPICH power to improve coverage, increasing the maximum DL power of AMR to reduce call drops, increasing FACH power to improve RRC setup success rates, and optimizing the T300 timer to further improve RRC success rates.
This document discusses key performance indicators (KPIs) related to a mobile network. It provides information on the relationships between different network elements like BSCs, BTSs, TRXs. It defines terms like SD blocking, SD drop, TCH blocking, TCH assignment, TCH drop and reasons they may occur. Solutions for reducing each issue are provided like changing parameters, adding hardware, improving coverage. Reports for analyzing each problem are listed.
This document provides guidance on tuning parameters to slow down inter-RAT cell reselections in UMTS networks. It discusses the Treselection timer, hysteresis between 3G and 2G cell reselections, and PRACH power ramping parameters. Recommended values for these parameters are given to reduce unnecessary reselections while maintaining call setup success rates. Key performance indicators for analyzing the impact of parameter changes on reselection rates and call performance are also identified.
This document discusses using signal strength and path loss data from 208 reports and OSS to identify hardware faults in cells. Case studies show how comparing path loss between transmit-receive channels within sectors can expose problems like loose cables or connectors. For example, much higher path losses (>20 dB difference) for some channels in a sector indicate a combiner issue. Differences only in uplink path loss between channels suggest a receiver cable problem. The document recommends using pivot tables to flag cells with over 10 dB variation in downlink or uplink path losses between channels for further 208 report analysis to identify worst performing cells needing attention.
This document describes the process of optimizing GSM900/1800 mobile networks. Key metrics are monitored daily, weekly, and monthly to check network health using a tool called Optima. Daily counters include call setup success rate, dropped calls, handover failures, and congestion. Issues like low call success rates could be due to problems like SDCCH congestion, phantom RACHs, CM service rejects, or TCH failures. Weekly and monthly statistics provide further insight into trends, retention, accessibility, load, and overall performance. Reports evaluate capacity and optimization progress.
This document discusses key performance indicators (KPIs) for a mobile network and reasons for and solutions to common issues. It provides relationships between different network elements and defines KPIs like SD blocking, SD drop, TCH blocking, TCH assignment, and TCH drop. For each KPI, it describes what causes poor performance, such as hardware faults, interference, parameter issues, and provides potential solutions like adding channels, improving coverage, adjusting timers and thresholds. Reports to analyze specific problems are also listed.
The document provides an overview and analysis flow for optimizing the performance of a mobile network. It discusses various problems that can occur like low availability of control channels, congestion on signaling and traffic channels, and high drop call rates. For each problem, it lists probable causes and recommends actions to identify the issue and solutions to resolve it, such as adjusting configuration parameters, adding network capacity, or improving frequency planning. MML commands are also provided to check device logs, resources, and performance statistics for troubleshooting purposes.
This document provides solutions for code congestion in mobile networks. It recommends checking certain counters to detect code congestion and expanding to two carriers if congestion is severe in a single carrier cell. The document also recommends using a Load-based Dynamic Rate (LDR) algorithm to solve code congestion. It provides the specific MML configuration to switch on LDR and set the LDR actions, and lists counters that can be monitored to check the effect of the LDR actions.
This document discusses radio resource optimization parameters in GSM networks. It covers topics like idle parameter optimization, power control, handover control, radio resource administration, measurement processing, signaling channel mapping, traffic channel mapping, paging parameters, access grant channel parameters, frequency reuse, and frequency hopping techniques. Diagrams and examples are provided to illustrate concepts like TDMA frame structure, logical and physical channel organization, and capacity calculations.
This document outlines processes for optimizing key performance indicators (KPIs) in a cellular network, including SDCCH assignment success rate, SDCCH drop rate, RACH success rate, TCH assignment success rate, Rx quality, handover success rate (HOSR), and TCH drop rate. For each KPI, it defines the measurement, identifies potential causes of poor performance, and provides steps to analyze detailed reports, check for issues like configuration errors or RF problems, and refine the network configuration to improve the KPI.
This document discusses various causes and troubleshooting steps related to 2G call drops and unsuccessful handovers. It addresses issues like low signal strength, interference, incorrect parameter settings, transmission faults, hardware faults, and more. The key performance indicators of TCH Drop Rate and Handover Failure Rate are defined. Causes of dropped calls on traffic channels include excessive timing advance, low signal strength, poor quality, sudden loss of connection, and other factors. Investigation steps provided include checking error logs, parameters, neighboring cell definitions, transmission quality, antenna installation, and more.
This document summarizes various LTE KPIs and performance metrics related to random access, RRC connection establishment, ERAB establishment, and issues that may impact them. It provides potential causes for high values or failures in these metrics as well as recommended actions to investigate like checking RF parameters, capacity, licenses, alarms, configuration, and optimizing physical antenna settings.
There are several ways to improve TBF Drop rates mentioned in the document:
1. Check frequency usage and retransmission rates to identify potential frequency issues and improve carrier to interference ratios to reduce interference.
2. Use the transmitter with the best broadcast control channel for packet data channels.
3. Ensure GPRS link adaptation is enabled and limit coding schemes to the more robust MCS7 if frequency changes don't help.
4. Reduce the number of users per packet data channel and check packet control unit congestion and utilization.
This document provides parameters for radio network configuration in a Nokia wireless network. It contains over 100 parameters organized in sections for the BSC, BCF, BTS, adjacent cells, and other settings. The parameters define thresholds, timers, and options that control functions like call handling, congestion management, handover processing, and radio resource allocation. The document is intended only for Nokia customers and subject to change without notice.
This document discusses possible reasons for SDCCH drops due to "Other Reasons" and provides steps to analyze and address the issue. It lists hardware faults, parameter definition issues, DIP status problems, frequency interference, C7 link stability, and improper MSC parameter definition as potential causes. The document advises checking logs, parameters, DIP quality, interference levels, C7 link commands, and MSC settings related to call setup, paging, location updating, authentication, ciphering, and SMS when analyzing SDCCH drops.
This document provides an overview of analyzing and troubleshooting SDCCH drop rate issues. It describes the SDCCH channel and how it is used, defines the KPI formula for calculating SDCCH drop rate, lists the counters involved in the KPI, and presents a flow chart of the SDCCH assignment process. Tools that can be used for the analysis are also identified, including Business Objects, MCOM, ZXG10 OMCR, and TEMS Investigation.
3 g huawei ran resource monitoring and management recommendedMery Koto
The document discusses monitoring resources in a Huawei WCDMA network to avoid congestion and blockages. It describes monitoring resources at the NodeB and cell levels like CE cards, licenses, OVSF codes, power levels, and Iub bandwidth. Counters are presented to monitor traffic, KPIs, resource usage, and rejections due to congestion. The resource consumption of different services is also analyzed to understand network characteristics and identify if resources are sufficient for desired services.
Day1 slot3 br radio configuration assessment and bss radio configurationv0.4fdr1975
The document discusses radio configuration assessment and planning for both a Broadband Radio (BR) system and a Base Station Subsystem (BSS). It provides examples of configuration settings for signaling allocation, traffic channel allocation, and packet switched capacity for a cell with either 8 or 10 TRXs. Key parameters for both the BR and BSS configurations are also defined.
The document describes parameter handling for Nokia's BSC/TCSM base station controller. It contains over 20 commands for modifying parameters related to general BSC configuration, radio network supervision, quality of service, GPRS, and background data activation. The commands allow operators to control functions like priority levels, dynamic frequency allocation, network monitoring thresholds, and more. Release notes describe changes between documentation issues, such as new parameters and updated output formats.
Bsspar1 s14 chapter 02_radio_resource_administration_v1.1Simon Aja
1. The document discusses intellectual property rights for Nokia Siemens Networks training materials, stating that Nokia Siemens Networks owns exclusive copyright and that individuals can only use materials for personal development and cannot pass them on without permission.
2. It then provides an overview of TDMA frame structures, logical and physical channels, and their mapping and parameters.
3. The document describes concepts like base station identity codes, training sequence codes, frequency reuse, and frequency hopping parameters.
How to perform trouble shooting based on countersAbdul Muin
This document provides guidance on troubleshooting radio network issues based on counter analysis. It discusses various counters related to RRC connection setup, access, and active phases. For each failure cause, it describes steps like checking alarm history, measurements, parameters, and traffic tables to identify potential root causes such as coverage issues, configuration mistakes, or hardware problems. The document uses examples and case studies to illustrate how to methodically analyze counters and narrow down issues.
This document discusses optimization of radio parameters in WCDMA networks. It describes the process of parameter optimization including collecting configuration, signaling, drive test and statistics data. It then lists common radio parameter optimization cases such as coverage, handover, call drop rates, access control and signal quality. Specific cases covered in more detail include increasing PCPICH power to improve coverage, increasing the maximum DL power of AMR to reduce call drops, increasing FACH power to improve RRC setup success rates, and optimizing the T300 timer to further improve RRC success rates.
The Monthly Journal of the American Hackerzubeditufail
This document provides an overview of office parameters for a Nortel DMS-100 telephone switch. It describes how the parameters are initially set and can be adjusted over time based on monitoring actual usage compared to settings. It recommends collecting operational measurement data and DMSMON reports to analyze peak usage and determine if parameter adjustments are needed.
This document discusses the Transaction Processing Performance Council (TPC) benchmarks. It provides a history of the TPC and describes some of its early benchmarks including TPC-A, TPC-B, and TPC-C. TPC-C is described as a moderately complex and more representative online transaction processing (OLTP) benchmark that models the business of a wholesale supplier managing orders. Key aspects of TPC-C such as its five transaction types, database schema, workload, and rules of compliance are summarized.
This document discusses troubleshooting of OptiX RTN 600 equipment. It covers objectives of troubleshooting preparation, ideas and methods, and examples of classified troubleshooting situations. Common troubleshooting methods discussed include alarm and performance analysis, loopback, replacement, configuration data analysis, configuration modification, using testing instruments, and experience-based rules of thumb. Typical troubleshooting sequences are also presented, beginning with excluding external issues and locating faults to a single network element or board. Finally, examples of traffic interruptions, wrong configurations, and bit errors are analyzed.
The agenda outlines a day of presentations and networking for National Semiconductor Corporation. It includes welcome remarks by Gil Amelio, President and CEO of National Semiconductor, followed by presentations on semiconductor forecasts, personal computers, computer storage, wireless communications, and office automation. Breakout sessions are scheduled for networking and Q&A. The event aims to provide National Semiconductor with a strategic review of key high technology markets.
The document discusses the machine cycles and timing of the 8085 microprocessor. It describes that each instruction of the 8085 is divided into machine cycles and each machine cycle is divided into clock cycles called T-states. The 5 basic machine cycles of the 8085 are listed as opcode fetch cycle, memory write cycle, I/O read cycle, memory read cycle, and I/O write cycle. The timing and status of signals like ALE, RD, WR, and IO/M during each machine cycle are explained.
The document provides information about a digital logic design course including the instructor's contact details, course objectives, textbooks, and summaries of key concepts in digital electronics such as binary digits, logic levels, digital waveforms, timing diagrams, basic logic functions, common digital systems and components, and integrated circuits.
The document provides information about a digital logic design course including the instructor's contact details, course objectives, textbooks, and summaries of key concepts in digital electronics such as binary digits, logic levels, digital waveforms, timing diagrams, basic logic functions, common digital systems and components, and integrated circuits.
The document discusses network integration considerations for Hadoop data centers. It addresses traffic types, job patterns, network attributes, architecture, availability, capacity, flexibility, management and visibility. It provides examples of buffer usage on switches and recommendations for dual 1GbE or 10GbE NIC configuration for Hadoop servers.
This document discusses how additive manufacturing (3D printing) could positively influence Thales' after-sales service. It first outlines why AM may be suitable for Thales, such as producing low volumes of complex parts with varying demand. The document then analyzes data on critical and general spare parts lists to identify parts that score high based on criteria like lead time, price and size. Preliminary conclusions suggest AM possibilities for injection molded casings and parts with long lead times and high impact. Questions remain around fully utilizing AM's potential and how it could improve Thales' after-sales service.
The document provides an overview of a 3-part training session on Unix/Linux performance and capacity management. It introduces the presenters, Adrian Cockcroft and Bob Sneed, and outlines the topics to be covered in each session. Session 1 will cover key definitions and concepts in capacity planning as well as important laws like Little's Law, Amdahl's Law, and Moore's Law. It will also discuss workload characterization and the importance of understanding application workloads.
The document provides processes for optimizing various key performance indicators (KPIs) related to GSM network performance. It describes processes for optimizing the SDCCH assignment success rate, SDCCH drop rate, RACH success rate, TCH assignment success rate, Rx quality, handover success rate, and TCH drop rate. The processes involve identifying poorly performing cells, analyzing detailed reports, checking for issues like configuration errors, hardware faults, RF interference, and making appropriate fixes such as parameter tuning and physical network optimizations.
The document discusses project scheduling techniques PERT and CPM. It provides an overview of PERT which was developed for projects with uncertain activity times, and CPM which was developed for projects with known activity times. The document then discusses how project networks are constructed and how critical paths are determined. It provides an example of applying PERT/CPM to the project of building a parade float, determining the critical path and project duration.
The document discusses digital logic design concepts including adaptive logic modules, logic array blocks, lookup tables, and timing analysis reports. It provides definitions and descriptions of these basic building blocks used in FPGAs. It also outlines the steps to generate and interpret timing analysis reports, identify timing violations, and apply clock constraints to solve violations by specifying a restricted maximum frequency of 500MHz.
Javier Garcia - Verdugo Sanchez - Six Sigma Training - W2 Non Normal DataJ. García - Verdugo
This document discusses evaluating and transforming non-normal distributed data sets to normal distributions. It describes the Box-Cox and Johnson transformations which can be used to normalize data. The Box-Cox tries to directly transform data while Johnson "distorts" a normal distribution to model the data distribution. The document provides examples applying the Johnson transformation to uniform and non-normal data sets. Graphical analyses show the transformations successfully produce normal distributions for analysis and process capability evaluations.
David Chase, Reducing Energy ConsumptionDavid Chase
1) The document discusses reducing energy consumption at Medtronic's Tempe campus facilities by analyzing the electricity usage of recirculation fans in Building 4.
2) Data was collected on the fans' energy use at different speeds and it was found that the fans could operate at 15Hz without impacting air quality standards, saving an estimated $23,000 per year.
3) A plan is proposed to lower the fans to 15Hz continuously, which would pay for itself within 12 weeks and could be expanded to other buildings.
The document provides an overview of the Telehouse Center site in New York City. It describes the facility's key features including 24/7 security, redundant power and cooling systems, telecom providers, and colocation space. The tour highlights security measures, loading docks, customer support areas, electrical infrastructure, and fire suppression systems designed to provide reliable operations for colocated IT equipment.
1. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TOP 10 WORST CELLSTOP 10 WORST CELLS
OPTIMIZATIONOPTIMIZATION
2. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
AGENDA
• Basic Idea of TOP 10 Optimization
• Introduction to statistics
• Configuration
• SDCCH and TCH drop Analysis
• Congestion Analysis
3. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Objective
THREE MAIN OBJECTIVES
• To keep track of the Network Performance
• To improve the Network Performance
• To achieve KPI purpose
4. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
GOAL
• To spread knowledge of how to optimize a
GSM network with help from statistics
• Share experience from other projects
5. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
BASIC IDEA TOP 10 OPTIMIZING
KPI
Top 10 optimizing
Procedures
TCH/SDCCH
DROP
Hand-overCongestion Random
Access
Paging (MSC)
6. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TOP 10 Optimization
KPI - Key performance indicator
1) Paging
2) TCH Drop Rate
3) SDCCH Drop
4) Congestion
5) Service denied
6) Random Access
7. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
BASIC IDEA
• Improve the worst 10 performing cells
Improving the worst 10 cells will give the biggest
improvement on BSC and Network level
As many subscriber as possible will benefit from a
better network.
The 10 worst cells will be different depending on what
is decided to optimize.
TOP 10 Optimization
8. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Resources
• Optimization per BSC, 1 region with 3-4 BSC per team
Team: 3 optimizer and 1 Cell-planner with support from
a pool of Filed Maintenance personnel and one expert.
• Location?
From a technical perspective preferably in regions with
local knowledge.
From an organizational perspective, Mexico City
TOP 10 Optimization
Decision need to be taken by management.
9. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Resources
First and second BSC, one owner / BSC
TOP 10 Optimization
BSC 1
BSC 2
TEAM A
1 optimizer
1 cell-planner
TEAM B
1 optimizer
1 cell-planner
10. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Analyzing statistical data
NWS
DATABASE
GSM NETWORK
WEB I
REPORTS
ANALYZE
• LOCATE PROBLEM
• SUGGESTIONS FOR
IMPORVMENT
• Change
request
• Trouble
report
11. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
WEB
NWS ANALYSER
Business Objects
STS DATA FILEOMS DATA FILES
TCP/IP
X25
AXE
1st Open Interface
Raw Interface
2nd Open Interface
- SQL Interfaces for other
applications or systems.
- Release Independent
Interfaces, e.g. GSM 12.04
PSA
LOADING
FM
External eventsBSDCSD
SDM
SDM FILE X FILE
External systems
SGwSMIA
X formatSDM format
STS Y DataOMS - Parsers
- Formatters
12. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
TOOLS
NWS
• Based on Business objects
• Possibility to create different reports and graphs.
• Direct access to SDM database where STS date are stored.
• Today SDM database is on Telcel LAN.
13. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
TOOLS
WEB I
• Tool to look at NWS reports bye using WEB browser
• No possibility to create different reports and graphs, only
look at predefined reports ant graphs.
• Possibility to down load data to excel
• Possibility change time period for statistic data
• No sort and filter in WEB I
14. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
• With statistics, performance of the network can be
measured
DROPPED CALLS
0,00
20,00
40,00
60,00
80,00
100,00
120,00
00151
00153
00182
00231
00233
00242
00351
00353
00402
00411CELL NAME
Nr.Dropp
0,00
1,00
2,00
3,00
4,00
5,00
6,00
Droperate
TFNDROP
T_DR-S
15. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
• With statistics problem-cells can easily be
identified.
DROPPED CALLS
0,00
20,00
40,00
60,00
80,00
100,00
120,00
00151
00152
00153
00181
00182
00183
00231
00411
00233
00241
00242
00351
00353
00403
CELL NAME
Nr.Dropp
TFNDROP
16. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Data Reliability
• 24 Hours Statistic data must complete or at least 95% of
Statistic data must be used in Analyzing process.
• Lack of complete Statistic data can lead to wrong
analysis result.
• In case of losing statistics data at night, we might still
analyze the data. But if we lost statistics data during day
time, we should reject the data for analysis process.
Introduction to statistics.
17. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
Statistics are built up from counters that steps for different events,
counters are put into formulas.
Example - Counter
TFNDROP - Steps when a call is dropped
TFNDROPSUB - Steps when a call is dropped in OL subcell
Example - Formulas
TCH DROP RATE TFNDROP + TFNDROPSUB * 100 [%]
TFCASSALL + TFCASSALLSUB
18. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
Formula name
• The formula name is build of short abbreviations.
• IN WEB I the formula is describes with a short sentence.
Example
Formula: S_DR_BQ_OU
SDCCH DROP BAD QUALITY OVERLAID/UNDERLAID
19. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
Formula name
Formula:
S_DR_BQ_OU
Description:
Dropped SDCCH Connections due to Bad quality of Total
Number of Dropped SDCCH Connections
WEB I Description:
SDCCH Drop Reason, BQ %
20. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
Formula name
• Naming conversion
Name given in Webi STS formula
name
Description
TCH Drop, BQ % OU U.link TF_DRBQULOU
Dropped TCH/F Connection at Bad Quality uplink of Total Number of Dropped
TCH/F Connections
TCH Drop, BQ % OU D.link TF_DRBQDLOU
Dropped TCH/F Connection at Bad Quality downlink of Total Number of
Dropped TCH/F Connections
TCH Drop, BQ % OU B.link TF_DRBQBLOU
Dropped TCH/F Connection at Bad Quality both links of Total Number of
Dropped TCH/F Connections
TCH Drop, Sudden % OU TF_DR_SUDOU
Suddenly lost TCH/F Connections of Total Number of Dropped TCH/F
Connections
21. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Introduction to statistics.
Ericsson provide many counters and standard formulas.
References
STS_formulas_PA10 - Formulas that will be used in Telcel project
NWSnamedefinitions - Conversion between formula name,
description and WEB I description.
R8 STS Formula - Standard Ericsson formula document
22. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
CONFIGURATION OL/UL - SUBCEL
Mexico Telcel
TCH
Frequencies
OL = HOP 1/1 over 6 -12 f
UL = NO HOP, 12-18 BCCH f
f
BCCH
TCH CHG1
CHG0
HOP
1/1
BCCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
UL
OL
SDCCH8SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
23. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
CONFIGURATION TCH DROP
OL / UL STATISTICS
• Possible to get separate statistic for UL/OL Subell.
• Possibility to limit a suspected interference problem to
UL or OL frequency band.
• CHALLOC set to 1, CHAP set to 5, most traffic on UL
Subcel.
24. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Preparation and Tools
• NWS WEB intelligent reports with correct formulas.
• There are standard report created for each statistics
analysis purpose.
• General Statistic daily and hourly reports for 24
hours statistic data per BSC. (All formulas needed
according to STS useful document TIM/TND-2001:
0023)
25. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
Preparation and Tools
• Maps with cell positions and antenna directions.
Use TCP or MapInfo. The map should show antenna
directions and BCCH, BISC.
• OSS
RNO and CNA.
In case of no access to OSS, dump file for each BSC
needed. (All parameters related, All neighbors
relation)
26. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TOP 10 DROPPED CALL
27. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH and SDCCH DROP
TCH - Traffic channel
SDCCH - Stand Alone Dedicated Control Channel
• Improvement on TCH drop will lead to improvement on
SDCCH drop
• Recommendation is to start with TCH drop
• The worst drop from a subscriber point of view is TCH
drop.
28. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP
Definition
• TCH Drop is an abnormal disconnection
Affects
• Subscribers will drop the call in conversation state
Objective
• Minimize dropped calls and thereby improve
retainability performance
29. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TOP 10 Optimization - Dropped call
Different way to measure:
• TF_DR_TOTOU = Total number of Dropped TCH/F
Connections in UL and OL subcell
• TF_DR-S_OU [%]=Dropped TCH/F Connections of
Total Number of TCH/F
Connections
• TF_DR_ERLMOU=Erlang Minutes per Dropped TCH/F
Connection
32. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP - WORK FLOW
UL SUBCEL
DROP REASSONS
OL UL
Yes
No
OUTPUT
REPORT
IS A CHANGE
REQUEST
NESSECARY?
ISSUE CR IN
REMEDY
ANALYSEANALYSEANALYSEANALYSEANALYSE
HIGH TA LOW SS
BAD
QUALITY
SUDDEN
LOST
OTHER
IDLE MESSUERMENT&
HANDOVER
REPORT
MRR, FAS, NCS,
MapInfo
What drop
reason have
higest %
drop?
What drop
reason have
higest %
drop?
OL SUBCEL DROP
REASSONS
Which subcel
OL or UL
have most
drops?
Dropped call
report
STS REPORTS
TOOS & STS REPORTS
1) SORT
& FILTER
PRE DEFINED
REPORT
TOP10 Droped
Calls
STS DATA
GSM
NETWORK
33. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP - Find the worst cells
Sorting process
• TF_DR_TOTOU, Descending
• Exclude drops with TF_DR-S_OU < 1,5% (Limit could
change)
• Cells with low drop rate in [%] can be hard to do
anything about.
• Some drops are normal.
34. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP - Find the worst cells
Sorting process
• What subcel have most number of drops?
• Overlaid subcel (OL)
• Underlaid subcel (UL)
BCCH
TCH CHG1
CHG0
HOP
1/1
BCCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
UL
OL
SDCCH8
TCH
35. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Priority In following order:
• Drop due to TA
• Drop due to Signal Strength UL/DL or Both
• Drop due to Bad Quality UL/DL or Both
• Drop due to Sudden lost
• Drop due to Other reason
Understanding of how
a dropped call will be
categorized
36. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Measurements and Filtering
• Not only one measurement report is used to determine
type of urgency condition.
• An average is made up of the last 6 measurements
reports ( number of measurement reports that will be
used can be set with parameters).
• Parameters
SS -- SSLENSI,SSLENSD
QL -- QLENSI,QLENSID
37. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Parameters- Drop due to TA
MAXTA = Maximum timing advance a MS can use in a cell
If the measured and averaged timing advance value for an
ongoing call is equal or greater than MAXTA, the call is released.
Recommended value = 63
TALIM = Determines the maximum timing advance that the MS
is recommended to use in the cell.
If the measured and averaged timing advance value for an
ongoing call is equal or greater than TALIM the cell must be
abandoned urgently
Recommended value = 61
38. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Parameters- Drop due to SS
LOWSSDL= Low signal strength limit for urgency
condition, downlink.
Recommended value =104dBm
LOWSSUL= Low signal strength limit for urgency
condition, uplink.
Recommended value =104dBm
39. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Drop due to SS
SS
SS DL SS UL SS BOTH
=
TF_DRSSDLOU
20%
=
TF_DRSSULOU
10%
=
TF_DRSSBLOU
10%
= TF_DRSS_OU 40%
40. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Parameters- Drop due to Bad Quality
BADQDL= Bad quality limit for urgency condition, downlink
Recommended value =55dtqu
BADQUL= Bad quality limit for urgency condition, uplink.
Recommended value =55dtqu
55dtqu = 5.5 RxQual
41. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Drop due to BQ
BQ
BQ DL BQ UL BQ BOTH
=
TF_DRBQDLOU
20%
=
TF_DRBQULOU
10%
=
TF_DRBQBLOU
20%
= TF_DRBQ_OU 50%
42. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Parameters- Drop due to Sudden lost
Sudden loss of connection is valid if none of the first three types
of urgency state are indicated (that is excessive TA, low signal
strength or bad quality) and the locating procedure indicates
missing measurement results from the MS.
TFSUDLOS is stepped according to above conditions
43. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Parameters - Drop due to Other
If a connection is dropped and there in no abnormal conditions and
no indications that measurements reports are missing.
Drops due to Other = All drops - drops due to TA,SS,QL,SUD
TF_DR_OTHOU=
TFNDROP + TFNDROPSUB - (TFDISSDL + TFDISSDLSUB + TFDISSUL + TFDISSULSUB +
TFDISSBL + TFDISSBLSUB + TFDISQADL + TFDISQADLSUB + TFDISQAUL + TFDISQAULSUB
+ TFDISQABL + TFDISQABLSUB + TFDISTA + TFSUDLOS + TFSUDLOSSUB) * 100 [%]
TFNDROP + TFNDROPSUB
44. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication - Drop due to TA
Ex1.
• Subscriber is far away from serving cell
• Possible missing neighbor
• If necessary plan for new site.
MS
35 KM
New site?
Missing Neighbor?
45. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication - Drop due to TA
Ex2.
• Subscriber is far away from serving cell
• Possible Dragon site
MS
35 KM
Down-tilt, lower antenna or change antenna type
46. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication - Drop due to SS
• Missing neighbor
• Missing site (planned but not built)
• Lack of indoor coverage
• Site location
• Installation problem
Shopping mall
with many
subscribers Low
indoor SS.
Missing
Neighbor
Missing
SITE
47. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication - Drop due to SS
• If many drops on UPLINK due to SS:
Could indicate installation problems such as lose feeders
hidden antennas.
• If many drops on DOWNLINK due to SS:
Could indicate wrong output power or lack of indoor
coverage.
48. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication- Drop due to Bad Quality
• Interference, Co- or adjacent Interference
Change frequency
MS
BCCH 590
BCCH 590
49. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication- Drop due to Bad Quality
• Interference - Co- or adjacent Interference
Down-tilt interferrer
BCCH 590
BCCH 590
High site
50. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication- Drop due to Bad Quality
• UPLINK Interference - Check Idle Channel measurement
Change frequency or find source of interferrer
• How are the ICM over time? Regularly or from time to time?
• Parameters
LIMIT1=4
LIMIT2=8
LIMIT3=15
LIMIT4= 25
Interferance band Interferance level Messured Rxlev
1 I <=-106dBm 0 to 4
2 -106dBm<I<=-102dBm 5 to 8
3 -102dBm<I<=-95dBm 9 to 15
4 -95dBm<I<=-85dBm 16 to 25
5 -85dBm<I 26 to 63
51. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication- Drop due to Bad Quality
• UPLINK Interference - Check Idle Channel measurement
Cellname ICH1 ICH2 ICH3 ICH4 ICH5
DF9999 0 0 10 30 60
DF5555 90 10 0 0 0
DF4444 100 0 0 0 0
This means that 10% of the time the measured
interference on idle TCH has SS according to
ICH BAND 2 -106dBm<I<=-102dBm
52. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication- Drop due to Sudden lost
• Measurement reports from MS is missing.
• Last report had good RxQual and Rxlev.
Rapid decrease of signal strength
Hand-over lost
Battery pulled out by subscriber
TUNNEL
MS
53. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP REASON
Problem indication - Drop due to Other
• Since there is no urgent conditions but the call is still
dropped its hard to find the reason.
• Request NOM to Check for BTS error log
• Generally
• NOT a radio related problem
• Transmission problems
• TRU hardware problems
• Wrong definitions of cell in MSC & BSC
• Wrong LAC definition in MSC
54. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
TCH DROP Investigation report in NWS
BASIC IDEA
• Easy overview of problem cells
• Pre defined reports
Top 10 DROP CALL
TCH DROP
SDCCH DROP
ICH Measurement
Handover performance
All STS data hourly
55. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP
Definition
• SDCCH Drop is an abnormal disconnection of SDCCH
Affects
• Subscribers will not able to set up a call. The
subscriber will try again,
• A radio link time-out on the SDCCH will occupy an
SDCCH sub-channel for (RLINKUP+RLINKT)/2 second
and increase the risk for SDCCH congestion
Objective
• Minimize dropped calls and thereby improve
retainability & accessibility performance
56. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP
Counter: CNDROP
CNDROP steps for following cases:
• Error indication and Channel release, abnormal release.
– Low SS, high BER
• Radio link time out.
– Low SS, high interference
• No assignment command
– Congestion or No measurement report received
• Unsuccessful assignment command
– Low SS high interference
57. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP
• SDCCH IN UNDERLAID CELL
TCH• Interference problem on SDCCH can be limited to
BCCH FREQ
BCCH
TCH CHG1
CHG0
HOP
1/1
BCCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
TCH
UL
OL
SDCCH8SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
SDCCH
58. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP
Formula:
S_DRCNTCOU = Dropped SDCCH Connections of Total Number of
SDCCH Connections when no TCH congestion
CNDROP - CNRELCONG * 100 [%]
CMSESTAB
59. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP - Find the worst cells
Sorting process
• S_DR_TOT-C, Descending
• Exclude drops with S_DRCNTCOU < 1,5% (Limit could
change)
• Cells with low drop rate [%] can be hard to do anything
about.
• Some drops are normal.
60. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP REASON
Priority In following order:
• Drop due to TA
• Drop due to Signal Strength
• Drop due to Bad Quality
• Drop due to Other reason
61. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP REASON
Problem indication - Drop due to TA
• Subscriber is far away from serving cell
• Possible missing neighbor
• If necessary plan for new site.
MS
35 KM
New site?
62. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP REASON
Problem indication - Drop due to SS
• MS Battery run out
• Missing site (planned but not built)
• Lack of indoor coverage
• Site location
• Installation problem Shopping mall
with many
subscribers Low
indoor SS.
Missing
Neighbor
Missing
SITE
63. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP REASON
Problem indication- Drop due to Bad Quality
• Interference - Co- or adjacent Interference
• Change frequency
MS
BCCH 590
BCCH 590
64. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP REASON
Problem indication- Drop due to Bad Quality
• Interference - Co- or adjacent Interference
Down-tilt interferrer
BCCH 590
BCCH 590
High site
65. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
SDCCH DROP REASON
Problem indication - Drop due to Other
• Since there is no urgent conations but the call is still
dropped its hard to find the reason.
• Generally drops due to other reasons indicate a non RF
problem.
• Transmission problems
• TRU hardware problems
• Wrong definitions of call in MSC BSC
• Wrong LAC definition in MSC
66. Nov. 2001 Henrik Centerham ERA/GG/NI TIM/NPOC/O
THANKS FOR YOUR ATTENTION