Upload
mohammed-rafi-ahmed-shareef
View
213
Download
0
Embed Size (px)
Citation preview
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 145
Title of PresentationDate
Agilent Restricted Page 1
Drive TestingMethodology
ForPlanning QA
Troubleshootingamp Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 245
Title of PresentationDate
Agilent Restricted Page 2
Typical Engineering Groups and Activities
RF Planning
Core Design
Site Planning
RF Design
amp Planning
Implementing Changes
Databse Management
Statitics Generation
Faults Management
OMCNMC
Air InterfaceTroubleshooting
BTS Maintenance
O amp M
RF and Parametric Tuning
RF Tests
Statistics Analysis
Optimization
Benchmarking
Performance Verification
Quality Assurance
Value Added Services
Transmission
Planning
Maintenance
Switching Operations
Engineering Customer CareMarketing
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 345
Title of PresentationDate
Agilent Restricted Page 3
RF Planning and Design
RF Planning
amp Design
Marketing
Optimization
Financial ControllerProject Management
Switch Planning
Switching
RF Coverage Requirements
Capacity Coverage Requirements
RF Penentration Requirements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 445
Title of PresentationDate
Agilent Restricted Page 4
RF Planning and Design
RF Planning
amp Design
Optimization O amp MMarketing
SitePlanning
CellPlanning
FrequencyPlanning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 545
Title of PresentationDate
Agilent Restricted Page 5
Search AreaSelection
Site PhysicalQualification
Coverage
Prediction
Band
ClearanceTest
Transmission
Reject
Acquire
Action Steps Site Planning
RF Planning and Design ndash Site Planning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 645
Title of PresentationDate
Agilent Restricted Page 6
RF Design and Planning ndash Cell Planning
Antenna Parameters
-Height Tilts OmniSector Azimuth Gain Polarization etc
Cell Parameters-Power Settings
-Neighbor Planning-Handover Parameters
These are required to balance traffic loading and maintain a good QoS on cell edges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 745
Title of PresentationDate
Agilent Restricted Page 7
Test Transmission
-Test Transmitter
-High Sensitivity CW Receiver
-Time and Distance based Averaging
-Leersquos Criteria ndash AT LEAST 50 samples of RF with a RunningAverage over a distance of 40 Wavelengths (12 meters for GSM900)
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 845
Title of PresentationDate
Agilent Restricted Page 8
RF Planning and Design ndash Frequency Planning
GSM uses concept of cellsOne cell covers small part of networkNetwork has many cellsFrequency used in one cell can be usedin another cells
This is known as Frequency Re-use
F=1
F=2F=3
F=48F=59
F=610
F=7
F=1
F=2
F=3
F=48
F=59
F=610
F=7F=1
F=2F=3
F=48
F=59
F=610
F=7
F= 12345678910
Clusters
F1
F2
F3
F4
F1
F2
F3
F4
F2
F1
F2
Co-Channel ( Re-use ) Cells
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 245
Title of PresentationDate
Agilent Restricted Page 2
Typical Engineering Groups and Activities
RF Planning
Core Design
Site Planning
RF Design
amp Planning
Implementing Changes
Databse Management
Statitics Generation
Faults Management
OMCNMC
Air InterfaceTroubleshooting
BTS Maintenance
O amp M
RF and Parametric Tuning
RF Tests
Statistics Analysis
Optimization
Benchmarking
Performance Verification
Quality Assurance
Value Added Services
Transmission
Planning
Maintenance
Switching Operations
Engineering Customer CareMarketing
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 345
Title of PresentationDate
Agilent Restricted Page 3
RF Planning and Design
RF Planning
amp Design
Marketing
Optimization
Financial ControllerProject Management
Switch Planning
Switching
RF Coverage Requirements
Capacity Coverage Requirements
RF Penentration Requirements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 445
Title of PresentationDate
Agilent Restricted Page 4
RF Planning and Design
RF Planning
amp Design
Optimization O amp MMarketing
SitePlanning
CellPlanning
FrequencyPlanning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 545
Title of PresentationDate
Agilent Restricted Page 5
Search AreaSelection
Site PhysicalQualification
Coverage
Prediction
Band
ClearanceTest
Transmission
Reject
Acquire
Action Steps Site Planning
RF Planning and Design ndash Site Planning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 645
Title of PresentationDate
Agilent Restricted Page 6
RF Design and Planning ndash Cell Planning
Antenna Parameters
-Height Tilts OmniSector Azimuth Gain Polarization etc
Cell Parameters-Power Settings
-Neighbor Planning-Handover Parameters
These are required to balance traffic loading and maintain a good QoS on cell edges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 745
Title of PresentationDate
Agilent Restricted Page 7
Test Transmission
-Test Transmitter
-High Sensitivity CW Receiver
-Time and Distance based Averaging
-Leersquos Criteria ndash AT LEAST 50 samples of RF with a RunningAverage over a distance of 40 Wavelengths (12 meters for GSM900)
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 845
Title of PresentationDate
Agilent Restricted Page 8
RF Planning and Design ndash Frequency Planning
GSM uses concept of cellsOne cell covers small part of networkNetwork has many cellsFrequency used in one cell can be usedin another cells
This is known as Frequency Re-use
F=1
F=2F=3
F=48F=59
F=610
F=7
F=1
F=2
F=3
F=48
F=59
F=610
F=7F=1
F=2F=3
F=48
F=59
F=610
F=7
F= 12345678910
Clusters
F1
F2
F3
F4
F1
F2
F3
F4
F2
F1
F2
Co-Channel ( Re-use ) Cells
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 345
Title of PresentationDate
Agilent Restricted Page 3
RF Planning and Design
RF Planning
amp Design
Marketing
Optimization
Financial ControllerProject Management
Switch Planning
Switching
RF Coverage Requirements
Capacity Coverage Requirements
RF Penentration Requirements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 445
Title of PresentationDate
Agilent Restricted Page 4
RF Planning and Design
RF Planning
amp Design
Optimization O amp MMarketing
SitePlanning
CellPlanning
FrequencyPlanning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 545
Title of PresentationDate
Agilent Restricted Page 5
Search AreaSelection
Site PhysicalQualification
Coverage
Prediction
Band
ClearanceTest
Transmission
Reject
Acquire
Action Steps Site Planning
RF Planning and Design ndash Site Planning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 645
Title of PresentationDate
Agilent Restricted Page 6
RF Design and Planning ndash Cell Planning
Antenna Parameters
-Height Tilts OmniSector Azimuth Gain Polarization etc
Cell Parameters-Power Settings
-Neighbor Planning-Handover Parameters
These are required to balance traffic loading and maintain a good QoS on cell edges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 745
Title of PresentationDate
Agilent Restricted Page 7
Test Transmission
-Test Transmitter
-High Sensitivity CW Receiver
-Time and Distance based Averaging
-Leersquos Criteria ndash AT LEAST 50 samples of RF with a RunningAverage over a distance of 40 Wavelengths (12 meters for GSM900)
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 845
Title of PresentationDate
Agilent Restricted Page 8
RF Planning and Design ndash Frequency Planning
GSM uses concept of cellsOne cell covers small part of networkNetwork has many cellsFrequency used in one cell can be usedin another cells
This is known as Frequency Re-use
F=1
F=2F=3
F=48F=59
F=610
F=7
F=1
F=2
F=3
F=48
F=59
F=610
F=7F=1
F=2F=3
F=48
F=59
F=610
F=7
F= 12345678910
Clusters
F1
F2
F3
F4
F1
F2
F3
F4
F2
F1
F2
Co-Channel ( Re-use ) Cells
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 445
Title of PresentationDate
Agilent Restricted Page 4
RF Planning and Design
RF Planning
amp Design
Optimization O amp MMarketing
SitePlanning
CellPlanning
FrequencyPlanning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 545
Title of PresentationDate
Agilent Restricted Page 5
Search AreaSelection
Site PhysicalQualification
Coverage
Prediction
Band
ClearanceTest
Transmission
Reject
Acquire
Action Steps Site Planning
RF Planning and Design ndash Site Planning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 645
Title of PresentationDate
Agilent Restricted Page 6
RF Design and Planning ndash Cell Planning
Antenna Parameters
-Height Tilts OmniSector Azimuth Gain Polarization etc
Cell Parameters-Power Settings
-Neighbor Planning-Handover Parameters
These are required to balance traffic loading and maintain a good QoS on cell edges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 745
Title of PresentationDate
Agilent Restricted Page 7
Test Transmission
-Test Transmitter
-High Sensitivity CW Receiver
-Time and Distance based Averaging
-Leersquos Criteria ndash AT LEAST 50 samples of RF with a RunningAverage over a distance of 40 Wavelengths (12 meters for GSM900)
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 845
Title of PresentationDate
Agilent Restricted Page 8
RF Planning and Design ndash Frequency Planning
GSM uses concept of cellsOne cell covers small part of networkNetwork has many cellsFrequency used in one cell can be usedin another cells
This is known as Frequency Re-use
F=1
F=2F=3
F=48F=59
F=610
F=7
F=1
F=2
F=3
F=48
F=59
F=610
F=7F=1
F=2F=3
F=48
F=59
F=610
F=7
F= 12345678910
Clusters
F1
F2
F3
F4
F1
F2
F3
F4
F2
F1
F2
Co-Channel ( Re-use ) Cells
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 545
Title of PresentationDate
Agilent Restricted Page 5
Search AreaSelection
Site PhysicalQualification
Coverage
Prediction
Band
ClearanceTest
Transmission
Reject
Acquire
Action Steps Site Planning
RF Planning and Design ndash Site Planning
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 645
Title of PresentationDate
Agilent Restricted Page 6
RF Design and Planning ndash Cell Planning
Antenna Parameters
-Height Tilts OmniSector Azimuth Gain Polarization etc
Cell Parameters-Power Settings
-Neighbor Planning-Handover Parameters
These are required to balance traffic loading and maintain a good QoS on cell edges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 745
Title of PresentationDate
Agilent Restricted Page 7
Test Transmission
-Test Transmitter
-High Sensitivity CW Receiver
-Time and Distance based Averaging
-Leersquos Criteria ndash AT LEAST 50 samples of RF with a RunningAverage over a distance of 40 Wavelengths (12 meters for GSM900)
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 845
Title of PresentationDate
Agilent Restricted Page 8
RF Planning and Design ndash Frequency Planning
GSM uses concept of cellsOne cell covers small part of networkNetwork has many cellsFrequency used in one cell can be usedin another cells
This is known as Frequency Re-use
F=1
F=2F=3
F=48F=59
F=610
F=7
F=1
F=2
F=3
F=48
F=59
F=610
F=7F=1
F=2F=3
F=48
F=59
F=610
F=7
F= 12345678910
Clusters
F1
F2
F3
F4
F1
F2
F3
F4
F2
F1
F2
Co-Channel ( Re-use ) Cells
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 645
Title of PresentationDate
Agilent Restricted Page 6
RF Design and Planning ndash Cell Planning
Antenna Parameters
-Height Tilts OmniSector Azimuth Gain Polarization etc
Cell Parameters-Power Settings
-Neighbor Planning-Handover Parameters
These are required to balance traffic loading and maintain a good QoS on cell edges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 745
Title of PresentationDate
Agilent Restricted Page 7
Test Transmission
-Test Transmitter
-High Sensitivity CW Receiver
-Time and Distance based Averaging
-Leersquos Criteria ndash AT LEAST 50 samples of RF with a RunningAverage over a distance of 40 Wavelengths (12 meters for GSM900)
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 845
Title of PresentationDate
Agilent Restricted Page 8
RF Planning and Design ndash Frequency Planning
GSM uses concept of cellsOne cell covers small part of networkNetwork has many cellsFrequency used in one cell can be usedin another cells
This is known as Frequency Re-use
F=1
F=2F=3
F=48F=59
F=610
F=7
F=1
F=2
F=3
F=48
F=59
F=610
F=7F=1
F=2F=3
F=48
F=59
F=610
F=7
F= 12345678910
Clusters
F1
F2
F3
F4
F1
F2
F3
F4
F2
F1
F2
Co-Channel ( Re-use ) Cells
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 745
Title of PresentationDate
Agilent Restricted Page 7
Test Transmission
-Test Transmitter
-High Sensitivity CW Receiver
-Time and Distance based Averaging
-Leersquos Criteria ndash AT LEAST 50 samples of RF with a RunningAverage over a distance of 40 Wavelengths (12 meters for GSM900)
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 845
Title of PresentationDate
Agilent Restricted Page 8
RF Planning and Design ndash Frequency Planning
GSM uses concept of cellsOne cell covers small part of networkNetwork has many cellsFrequency used in one cell can be usedin another cells
This is known as Frequency Re-use
F=1
F=2F=3
F=48F=59
F=610
F=7
F=1
F=2
F=3
F=48
F=59
F=610
F=7F=1
F=2F=3
F=48
F=59
F=610
F=7
F= 12345678910
Clusters
F1
F2
F3
F4
F1
F2
F3
F4
F2
F1
F2
Co-Channel ( Re-use ) Cells
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 845
Title of PresentationDate
Agilent Restricted Page 8
RF Planning and Design ndash Frequency Planning
GSM uses concept of cellsOne cell covers small part of networkNetwork has many cellsFrequency used in one cell can be usedin another cells
This is known as Frequency Re-use
F=1
F=2F=3
F=48F=59
F=610
F=7
F=1
F=2
F=3
F=48
F=59
F=610
F=7F=1
F=2F=3
F=48
F=59
F=610
F=7
F= 12345678910
Clusters
F1
F2
F3
F4
F1
F2
F3
F4
F2
F1
F2
Co-Channel ( Re-use ) Cells
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 945
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1045
Title of PresentationDate
Agilent Restricted Page 10
Co - Channel interference
C Ic 9 dbInterference on a channel caused by another cellmobileusing the same frequencyCIc is the measure of co-channel interferenceGSM specifies the CIc threshold of 9dB for a service quality
of 04 BER on Type II bits9db also includes 2db implementation margin9db is decided considering the implementation of SFHWithout SFH the preferred threshold is 12 dB
CIc
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1145
Title of PresentationDate
Agilent Restricted Page 11
Co-Channel Interference
C Ic
Noise
ARFCN N ARFCN N
CausesDistant Cells due to tight frequency re-use patternsDistant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)CIc will degrade the EcNo so if Noise floor itself is high then evena high value of CIc can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1245
Title of PresentationDate
Agilent Restricted Page 12
Interference caused when wanted and unwanted GSM RFchannels co-exist
C
Ia
Adjacent Channel Interference
GSM receivers are designed for an Adjacent Channel Suppression ofminimum 18db at an offset of 200 Khz 50db at 400 Khz and 58db at 600Khz
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1345
Title of PresentationDate
Agilent Restricted Page 13
Adjacent Channel Interference
ACS = 18db amp Cc = 9dbThis means if Ia is 9db above C then with 18db ACS it equals CIc
Thresholds C Ia1 = - 9 dbC Ia2 = - 41 dbC Ia3 = - 49 db
N N+1N-1
9db
N+2N-2
41 db
49 db
N-3 N-3
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1445
Title of PresentationDate
Agilent Restricted Page 14
Adjacent Channel Interference
Causes
Adjacent ARFCNs in same cells Adjacent ARFCNs in adjacent cellsDistant Cells due to tight frequency re-use patterns
Distant Cells due to errors in frequency planningMulitpath from Distant cells( strong reflector Water)Improper Receiver filters ( low ACS )CIa will degrade the EcNo so if Noise floor itself is high then
even a low value of CIa can deteriorate quality
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1545
Title of PresentationDate
Agilent Restricted Page 15
External Interference
Interference coming on a GSM signal from an undesired sourceie neither a coadj channel cell or MS
SourcesMalfunctioning or Maladjusted Transmitters
Base station malfunction rogue mobilePaging broadcast etc
Intermodulation ProductsStrong signals in adjacent channelsHarmonics from Other Bands
CDMA GSM I t f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1645
Title of PresentationDate
Agilent Restricted Page 16
CDMA GSM Interference
824 MHz 849 MHz
869 MHz 894 MHz
890 MHz 915 MHz880
935 MHz 960 MHz925
UL UL
DL UL
bullCDMA Downlink interfering with GSM Uplink
CDMA GSM60 dbc
Minimal loss
bullOMC Stats indicates High Cell Access Failed Cell AcessPhantom RACHrsquosbullDrive Test indicates Blocked calls with return to idle after Channel Request
bullDigital Receiver can go upto ndash122 dbm noise floor level for this applicationbullAgilent Receiver becomes a Hero in China for detecting this problems in live networks
Quality Assurance
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1745
Title of PresentationDate
Agilent Restricted Page 17
Quality Assurance
Field Tests
(Drive Tests)
Customer
Care OMCNMC
QualityAssurance
Optimization
bullQuality Assurance takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1845
Title of PresentationDate
Agilent Restricted Page 18
Quality Assurance
bullConsistent Network Health MonitoringbullAuthentic Data Points to measure against KPI thresholds
bullQuality Trends by Regions and by Vendors
bullIntegration of Data from prominent sources like OMC CustomerCare Field Tests etc to generate Service Availability andPerformance Index figures
bullKPI Parameters could be split collected from different data sources
bullMost KPI Parameters need customer perception hence fieldmeasurements are essential
bullCompetitive Networks Benchmarking
bullProvide Results to Marketing Business Analysts and Optimization
k f
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 1945
Title of PresentationDate
Agilent Restricted Page 19
Network Performance Data Sources
Customer Calls OMCNMC Drive Test
bullCustomer perceptionbullRepeatabilitybullNon-Technical InfobullPhsyco Factor
bullMassive DatabullMore Statistical DatabullCell level analysisbullNon Real Time update
bullNon Geographical infobullSpecific Mobile TracingbullPerformance for All users
bullSpecific to problem routebullLimited users (148) testsbullAir interface onlybullDrill Down to Causes
bullSpot AnalysisbullCoercive TestingbullOptimization Tests
Quality Assurance Period
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2045
Title of PresentationDate
Agilent Restricted Page 20
Quality Assurance - Period
0
5
10
15
20
25
30
Daily Weekly Monthly Quarte rly Half yearly Annual
RoutineRoutine
Spurious
0
20
40
60
80
100
Major TechnicalChanges
Market Events
Quality Assurance Methodology
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2145
Title of PresentationDate
Agilent Restricted Page 21
Q y gyStep A Deciding the monitoring geography
Network(Market)
RegionCirclesStates
Cityrsquos Townrsquos Villages Connecting HwsRds
Zones Zones Groups Highways
Hot Spots RoadsStreets
Routes(Rds)
Routes(Strs)
Bye-Lanes
Performance Monitoring Measurements
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2245
Title of PresentationDate
Agilent Restricted Page 22
Performance Monitoring Measurements
VoiceVoice
StatisticalStatisticalCall Success RateCall Drop Rate
Handover Success Rate No ServicePercentage QualityPercentage Coverage
Percentage Interference
Geographical(Maps)Geographical(Maps)Speech Quality(MOS)Um Quality(Rxqual)Coverage(Rxlev)Cell Footprint(Cellid)Drop CallsBlocked Calls
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2345
Title of PresentationDate
Agilent Restricted Page 23
QA Drive Process Suggestion
-Routes should be predefined
-Test plans should be preset
-Drive Duration and Time of Day should be preplanned- Peak Traffic Hours should be used for QA tests
-Markers and Notes should be used
-Data should be preferably binned
-Use Analysis Reporter to get quick shot QA performance Report
-Thresholds should be standardized
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2445
Title of PresentationDate
Agilent Restricted Page 24
QA Drive Test Call Setup
Short Calls-Reliable CSR
-Non-Reliable Drop
Long Calls
- Non-Reliable CSR
- Reliable Drop
bullAverage User Call time should be taken ( 2mins 15 secs off)
bullCSR is more reliable on cumulative traffic basis hence focus should be more onDrop calls
bullRecommended to do Quality Drive separately or use two phones and then usecombined statistics generation
QA Dri e Basic Set p
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2545
Title of PresentationDate
Agilent Restricted Page 25
QA Drive Basic SetupSingle Phone Digital Receiver
CochannelAdjacent Chan ALink to BCH
Call Duration 120 secsIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
Blocked CallDrop CallRLTC lt 5Rxlev lt - 100 for 3 secs
RxQual gt 4 for 3 secsHandover FailureAssignment FailureBCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2645
Title of PresentationDate
Agilent Restricted Page 26
QA Drive Basic SetupTwo Phone
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Phone 2
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
QA Drive Basic Setup
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2745
Title of PresentationDate
Agilent Restricted Page 27
QA Drive Basic SetupThree Phone
Phone 3
No callIdle
Digital Receiver
CochannelAdjacent Chan ALink to BCH of Idle
Phone 1
Call Duration 60 secsIdle Time 15 secsImmediate Dial ON
Phone 2
Call Duration ContinousIdle Time 15 secsImmediate Dial ON
Do NOT dial a number which does NOT issue Alerting
Alarms and Markers
(P1) - Blocked Call(P2) - Drop Call(P1 amp P2) - RLTC lt 5(P2) - Rxlev lt - 100 for 3 secs
(P2) - RxQual gt 4 for 3 secs(P2) - Handover Failure(P1)- Assignment Failure(P1 amp P2 amp P3) - BCH ChangeCochannel CI lt 9 amp Power gt -90Adjacent CI gt -9 amp Power gt - 90
-Alarm Count provides severity points
-Helps the Post QA Action team
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2845
Title of PresentationDate
Agilent Restricted Page 28
QA Test Setup Matrix
QA Test Phone 1 Phone 2 Phone 3 Receiver
Ful l Qual ity Verification Short Cal l Long Cal l Idle
Int --gt Phone 3
BCH- Top ChDedicated Mode Full QA Short Call Long Call Int --gt Phone 2Reliability only QA Long Call Int --gt Phone 2
Accessibility only QA Short Call Int --gt Phone 1
Idle Mode only QA IdleInt --gt Phone 3
BCH-Top Ch
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 2945
Title of PresentationDate
Agilent Restricted Page 29
KPI ndash QA - TEST
Call PerformanceBlocked call RateDropped Call RateHandover Failures
CoverageRF Idle Mode Coverage (Rxlev_Full)RF Receiver Based Coverage (Top N Power)Service Coverage (CI In Idle Mode DSC )
QualityRxQual SubRxlevel SubTiming AdvanceRLTCEst InterferenceCI and CA
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3045
Title of PresentationDate
Agilent Restricted Page 30
Call Stats
Statistical DT data cannot bedirectly correlated with OMCdata
For significant statistical DTreports number of calls and drivehours should be high
Recommended to combinemultiple drives together and thengenerate Stats only module
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3145
Title of PresentationDate
Agilent Restricted Page 31
Performance KPIrsquos and Thresholds
Min Average Max Percentage Exceeding Threshold Threshold
Phone State - - - 7333 Dedicated
No Service - - - 04 No Service
Hopping - No Hop - 00 Hopping
RxLev_Full -940 -717 -490 00 lt-96 dBm
RxLev_Sub -960 -717 -490 00 lt-96 dBmRF Coverage -91 -6872 -49 000 lt-96 dBm
N1_RxLev -1090 -847 -530 92 lt-96 dBm
N2_RxLev -1080 -843 -540 77 lt-96 dBm
RxQual_Sub 00 03 70 15 gt4
RxQual Hop na na na na lt5
RxQual NonHop 00 02 70 988 lt5
Interference(Est) - - - 06 gt-80 amp gt4
FER 00 01 10 00 gt5
RLT 10 198 200 10 lt5
Tx Power 00 30 80 927 lt7
Timing Advance 00 20 630 05 gt15
Threshold used as default by AR are industry average standards
QA Tests Additional Supportive Parameters
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3245
Title of PresentationDate
Agilent Restricted Page 32
QA Tests ndash Additional Supportive ParametersbullPerformance by Cell
bullHandover Performance
Points to be Noted
-QA Tests and Results Model is very much local dependent
-Only certain industry international procedures and parameters can be usedas referenceWe donrsquot recommend the ldquoCtrl C amp Ctrl Vrdquo approach
-Localization of the QA procedures has to be done through model tuning
-This needs some significant hours of work at country level might be worthconsidering a consultant for this
Pl i V ifi i i h QA D i
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3345
Title of PresentationDate
Agilent Restricted Page 33
Planning Verification with QA Drive
-It is an incorrect norm to use Planning Tools for Post Data Analysis
-Some Planning tools support import of drive test data and also do modellingbased on this data
-There are several variants in drive test data like Power Control improperhandover parameters settings etc which can hamper this modelling
-Planning Data efficiency can be achieved through modelling the Planning Toolby using Test Transmission exercises
-Significant Variance in Planning Data vs measured data can be identified by
comparing the results
-Reverting to Planning Tool should not be a part of QA team work it is theoptimization team role to use the QA data and see where the flaw is
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3445
Title of PresentationDate
Agilent Restricted Page 34
QA Drive Best PracticesData Preservation
-Centralization of Database and Reports
- All data collected after filtering the non useful file shouldbe saved on a Server which has proper identification matrix
State
- City- Zone1- Zone n
- Jan05
- helliphellip- Dec 05
- Same Structure should be repeated for Reports also- At least 18 months of data should be preferred
- No need to preserve Troubleshooting Data only QA is enough
-Third Party Browsing Software can be developed to do Report Management ApplicationsAgilent can help with this
-A Basic Server Webbased Browsing with MYSQL Queries can be easily developed within 50KUSD We can help BSNL in identifying the Vendor and also help the feature requirements specs
QA Drive Best Practices
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3545
Title of PresentationDate
Agilent Restricted Page 35
QStandardizing Nomenclature and Terminologies
- Log files and Report names should all be standardized- Even the folder structure on local PCrsquos should be standardized
Example
CDrivetest sd5 - Log Files
CDrivetest planfiles ndash spf Plan Files
CDrivetest Reports
Logfile names should be use default Agilent names which has date and time butuse separate sub folders for location or if u desire to put some separate identify put atthe end of the file like 06-09-2004_02-56-22 PM_ GPRS Web testSD5
Whenever a correct report is generated use SAVE AS to save it in the report folder It is good
create a folder matrix in advance and standardize that country wide so if you for servermanagement it becomes easy
E l f F ld St t
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3645
Title of PresentationDate
Agilent Restricted Page 36
Example of Folder Structure
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3745
Title of PresentationDate
Agilent Restricted Page 37
Troubleshooting Network RF Problems
Troubleshooting Process Case Study
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3845
Title of PresentationDate
Agilent Restricted Page 38
g yHighHigh RxqualRxqual
Rxqual_sub gt 4
(for gt 2secs)
Rxlev lt -95 Coverage
Neigh Level Poor Yes
Interference
Identify CellBCHampNeigh BCH
amp Channel
CoverageHole
CellDragging No
Identify CellBCHamp Neigh BCH
amp Channel
InterferenceSource
Detection
Intermittent
No
No
Yes
Record Yes
Measure CI IdentifyType (coAdj)
Handoverexpected
Yes
No
Yes - Level 1- Level 2- Level 3
Troubleshooting ndash Drive Test Applications
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 3945
Title of PresentationDate
Agilent Restricted Page 39
Receiver Based Diagnosis
Receiver and Scanner are different Scanning is one of the features of a ReceiverDigital Receiver Functionalities
Interference Analysis- CoChannelAdjacent Channel
- External Interference in DLUL- Source Detection
High Speed Scanning- Flexible Configuration
- BSIC decodeSpectrum Analysis
- External Interference Detection- Cross Tech Filtering problems- UL Interference from Cordless Phones- Band Clearance
CW Measurements- Test Transmission- Indoor Planning and BSRepeater Implementations
1670
120
288
506
00
100
200
300
400
500
600
-20 to 0 0 to 9 9 to 12 12 to 15 15 to 50
Agil ent GSM Receiv er - CoChan nel CI
Digital Receiver ndash Automated Interference
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4045
Title of PresentationDate
Agilent Restricted Page 40
Analysis Example hellip
One Click Interference Management using Analysis Reporter
Example Report 1
Example Report 2
Optimization
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4145
Title of PresentationDate
Agilent Restricted Page 41
O amp M
OMCNMC
Optimization
Marketing
Field Tests(Drive Tests)
SignallingSystems
Q A
RF Design andPlanning
bullOptimization takes data from several sources
bullPrimary sources of Data are OMCNMC and Field Tests
Routine Optimization Activities
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4245
Title of PresentationDate
Agilent Restricted Page 42
bullInterference Reduction (or shift )
- Power Settings Antenna Tilts Frequency Parameters
bullCoverage Holes- Adequate Coverage to Hot Spots Indoor
bullCapacity Balancing
- Cell Configuration Power Antenna
bullFeature Implementation
- PC changes handover algorithmsCoders etc
Optimization Challenges
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4345
Title of PresentationDate
Agilent Restricted Page 43
Optimization in most cases is of two type
Overall Done over a wide geographySelected Done over a selected problem areabullFor Overall Drive Test is done over a larger area for verification
bullFor Selected Drive Test is done over the selected area whereoptimization work was done but the problems (specific to frequencyrelated) gets shifted to other areas
bullPre Optimization Drive Test Data is generally derived from QA Drive Testitself
bullPost Optimization Drive Test can also be undertaken by QA team in aselected zone
What keeps RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4445
Title of PresentationDate
Agilent Restricted Page 44
Increase Revenuesand Drive Down Costs
What keeps RF engineering and operationsmanagers up at nightbull How can I maximize the return on my test
equipment investment required to install ampmaintain my 2G25G3G networks
bull How do I quickly rollout complex next-generation data networks and ensureoptimum performance
bull How can I optimize my existing and new253G networks without limited resources
bull How do I accelerate the migration of mynetwork to a new technology
Declining capital requires ways to increase revenues reduce OpEx and improve RO
What makes a RF engineering and operations
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach
8202019 Network Operator Process
httpslidepdfcomreaderfullnetwork-operator-process 4545
Title of PresentationDate
Agilent Restricted Page 45
manager come late to workMoving from Point Engineering Solutions toSystems Thus maintaining the investmentsmade on Test Tools
Pulling out the information from Test Toolsand shattering it all over the organization
Handy Data for TodayYesterdayWeeksMonthsYears and Readyfor DATA coming Tomorrow
Independency of Skill Set and NEMdependency for Knowledge transfer
Taking a Proactive Approach rather than
Reactive Approach