Powered by www.agileto.com MOBILE RADIO NETWORK OPTIMIZATION POST-Swap C07 DT Analysis 2G
Powered by www.agileto.com
MOBILE RADIO
NETWORK OPTIMIZATION
POST-Swap C07 DT Analysis 2G
Powered by www.agileto.com
Agenda
• Introduction: Context, Inputs and Deliverables
• Geo-spatial representation of the Network/Cluster
• Cluster Audit & Sanity Check (RF main param + Neighbors)
• Automatic best Neighboring evaluation (missing detected)
• Drive Test (DT) Analysis and Recommendations
2
Powered by www.agileto.com
Inputs and deliverable Inputs: • Geodatabase of network encompassing the cluster under study:
Site Coordinates in WGS 84 in CSV or tabular format Antenna configurations per technology (2G) : height, azimuth, tilt (mech + elec)…
• BSC dump of the 2G cluster: Ericsson 2G *.log dump OSS file(s) on 01.11.2017
• Drive test log files (POST-Swap) on period time from 27.10.2017 to 28.10.2017 (Scanner 2G)
Outputs: • GIS representation of the 2G clusters in MapInfo & Google Earth formats
• Cluster Audit & Sanity check (main RF parameters + neighbors)
• Automatic best neighboring evaluation (based only on Cells positions Lat/Long + azimuths)
• Drive Test route and analysis presentations in MapInfo & Google Earth formats
• Recommendations: • Neighbors proposals (missing + detected) • Over-shooters detections • Polluted areas (Investigations) • Cells Coverage efficiency • Wrong BCCH planning and optimization • Automatic Cross Sectors/Feeders detections
3
Powered by www.agileto.com
Agenda
4
• Introduction: Context, Inputs and Deliverables
• Geo-spatial representation of the Network/Cluster
• Cluster Audit & Sanity Check (RF main param + Neighbors)
• Automatic best Neighboring evaluation (missing detected)
• Drive Test (DT) Analysis and Recommendations
Powered by www.agileto.com
Geographical cluster distribution
5
Cluster 07 General Overview
Powered by www.agileto.com
Geographical cluster distribution
Cells/Sites distribution of the DT cluster under the study:
Nbr of 2G sites: 22 Nbr of cells per band:
• 2G-900 = 60 • 2G-1800 = 6
Colors Legend: 2G Layers: 900, 1800
6
Powered by www.agileto.com
Agenda
• Introduction: Context, Inputs and Deliverables
• Geo-spatial representation of the Network/Cluster
• Cluster Audit & Sanity Check (RF main param + Neighbors)
• Automatic best Neighboring evaluation (missing detected)
• Drive Test (DT) Analysis and Recommendations
7
Powered by www.agileto.com
Cluster Audit & Sanity check (summary) Below is presented a sample concerning the first cells from the Audit & Sanity check summary analysis for the cluster under investigation. The main RF parameters analysis and the related summary neighbors are presented accordingly. The entire table is attached to this report.
8
Powered by www.agileto.com
Cluster Audit & Sanity check (2G2G neighbors) Below is presented a sample concerning the first 2G2G neighbors (Source-Target) extracted from the Audit & Sanity check analysis for the cluster under investigation. The main related summary neighbors are presented accordingly. The entire table is attached to this report.
9
Powered by www.agileto.com
Agenda
• Introduction: Context, Inputs and Deliverables
• Geo-spatial representation of the Network/Cluster
• Cluster Audit & Sanity Check (RF main param + Neighbors)
• Automatic best Neighboring evaluation (missing detected)
• Drive Test (DT) Analysis and Recommendations
10
Powered by www.agileto.com
Automatic best Neighboring evaluation Agileto dedicated module (M3.4) provides the optimum neighbors generation based only on the Cells positions (Latitude and Longitude) + their antennas orientations (Azimuths) together with the Source Coverage + Target Distance (see below).
11
Evaluating the cluster average Inter-Cells distance ~ 3Km, the following inputs were used:
Source Cell Coverage Distance:
4Km
Target Cell (Neighbor) Distance (maximum):
8Km
By using as reference the existing 2G2G neighbors declarations extracted from the OMC 2G export snapshot file, the missing neighbors detected by this method will be presented in tabular format and Google Earth representation on this section.
Powered by www.agileto.com
Below is presented a sample representing the first missing 2G2G neighbors (Source-Target) detected by Agileto module M3.4 for the cluster under investigation. The entire table containing a number of 72 missing neighbors detected (2G2G) is attached to this report.
12
Automatic best Neighboring evaluation (missing)
Powered by www.agileto.com
Example of the 2G2G Neighbors presenting the existing neighbors declarations + the missing detected by Agileto module M3.4 (and mapped on Google Earth by M3.2)
Source Cell: QDH0042
On this example there are detected three (3) missing neighbors which are presented on the right side with red lines. Obs. The full representation in GE of all the 2G2G neighbors including the already existing neighbors + the missing detected (red lines) are attached to this report.
13
Automatic best Neighboring evaluation
Powered by www.agileto.com
Agenda
• Introduction: Context, Inputs and Deliverables
• Geo-spatial representation of the Network/Cluster
• Cluster Audit & Sanity Check (RF main param + Neighbors)
• Automatic best Neighboring evaluation (missing detected)
• Drive Test (DT) Analysis and Recommendations
14
Powered by www.agileto.com
Drive test cluster
presentation
DT Route
DT Best Server
Pollution areas
Coverage Efficiency
Over shooter
Cells
BCCH Audit &
Optimization
Missing Neighbors
(2G-2G)
Cross feeder
detection
Drive Test analysis
15
Powered by www.agileto.com
Drive test Summary Project: TRIAL_COMIT Input Drive Test File: Post-Swap-C07_Scan2G.txt DRIVE TEST SUMMARY: Agileto => www.agileto.com © 2017 All rights reserved ([email protected]) [M4.1|V5.24] => Network Optimisation based on Drive Tests (*.txt/*.csv) User Login: Agileto| Run Time: 15Nov2017 04:31:06-04:31:21 [15sec] Input Drive Test measurement file: D:\Agileto\TRIAL_COMIT\Drive_Tests\DT_Measurements\Post-Swap-Cluster07-Laptop2_20171028\export\Final\Post-Swap-C07_Scan2G.txt Input OMC Snapshot file: D:\Agileto\TRIAL_COMIT\OMC_Snapshots\01-11-2017\2G\BSCs_01Nov\B1351E_111.log+B1351E_211.log+B357E_111.log Input Agileto database reference file: D:\Agileto\TRIAL_COMIT\MobileNW_Config\MobileNW_Config.xls Drive Test post-processing -> Option Selected: 2G -> 2G [Intra2G-2G)] Source Technology: 2G, [GSM] layer Target Technology: 2G, [GSM] layer Source: Nr of BestServers = 33 Target: Nr of BestServers = 33 GSM RSSI Min [dBm]: -100 Active Set (RSSI) Range (delta BestServer) for valid 'Best Servers' [dB]: 3 Monitoring Set (RSSI) Range (delta BestServer) for valid Scanner measurements [dB]: 8 Minimum Neighbors Imposed Weight [%]: 2 Spatial binning operated: YES, -> bin size [m]: 10 Output Drive Test Network Optimisation file: D:\Agileto\TRIAL_COMIT\Drive_Tests\DT_Optimisation\Bin10m_Post-Swap-C07_Scan2G-2G2G_GSM-GSM\Bin10m_Post-Swap-C07_Scan2G-2G2G_GSM-GSM_DT-NWOptim.xls 1) Total number of INPUT lines detected into DRIVE TEST measurements file: 61145, Drive Test => 16H 59min, [100%] 2) Total number of MOBILITY Drive Test measurements: 58856, Drive Test => 16H 21min, [96.26%] 3) Total number of STATIC [No Mobility detected] Drive Test measurements: 1941, Drive Test => 0H 32min, [3.17%] 4) Total number of INVALID GPS (Lat/Lon) lines: 0, Drive Test => 0H 0min, [0.00%] 5) Total number of INVALID DRIVE TEST SOURCE measurements: 348, Drive Test => 0H 6min, [0.57%] 6) Total number of INVALID DRIVE TEST TARGET measurements: 0, Drive Test => 0H 0min, [0.00%] Total number of points resulted after spatial binning aggregation: 12321 (bin size[m]=10)
Powered by www.agileto.com
Route of the 2G DT cluster
Drive test route related to the 2G cluster (layers: 900 + 1800):
The DT covers ~ 123 km (without
counting repetitive routes)
Total aggregated points of the DRIVE TEST detected into the measurements file: 100% • Total number of MOBILITY
Drive Test measurements: 96.26%
• Total number of STATIC [No Mobility detected] Drive Test measurements: 3.17%
17
Powered by www.agileto.com
Best server RSSI along the 2G DT cluster
Percentage distribution of RSSI (TOP1 = Best server) 88.9 % of the DT route
RSSI ≥ -70 dBm Deep Indoor, good coverage
7.4 % of the DT route
-80 dBm ≤ RSSI < -70 dBm Indoor acceptable coverage
2.1 % of the DT route
-90 dBm ≤ RSSI < -80 dBm Outdoor poor coverage,
1.5 % of the DT route
RSSI < -90 dBm Bad coverage,
19
Powered by www.agileto.com
Best server RSSI along the 2G DT cluster
The worst coverage areas: 3.6 % DT route
RSSI < -80 dBm
20
Powered by www.agileto.com
Cluster DT analysis: Pollution (2G)
Similar with the 3G technology, Agileto tool is using the terminology of the Active Set size for the 2G technology too, as following:
Active Set size means the number of the 2G cells (detected on each drive test measurement point) -
(2G cells are unique identified by Agileto in relation with the NW 2G cells database, the BCCH (BSIC) and the Lat/Long of the drive test measurement point)
- which are falling within the specified range (called Active Set range, usually 3dB) against the best server (which is in reality the single 2G active radio link).
Definition:
Polluted area = area where the number of the 2G cells detected on each measurement point within user specified range - (this range is provided as input to Agileto tool as Active Set range, usually 3dB) - against the best server exceeds a certain value called Active Set size (usually 3 cells).
22
Powered by www.agileto.com
Percentage distribution of Active Set (AS) size along the DT route: 88.1 %
AS ≤ 2 No polluted area
6.0 % AS = 3
Medium polluted area
5.8 % AS ≥ 4
Polluted area
Cluster DT analysis: Pollution
23
Powered by www.agileto.com
Geographically distribution of the points representing the Polluted areas:
5.8 %
AS ≥ 4 Polluted areas
Cluster DT analysis: Pollution
24
Powered by www.agileto.com
Cluster DT analysis: Pollution
25
Pt_nr = 6708 Time_Stamp = 10:40:18.504 ActiveSet_Size = 6 MaxLink_Dist=45.0Km 1) QDH0021/6/-59.0/34.0 2) QDH0022/4/-60.0/35.0 3) QBL0023/27/-61.0/-1.0 4) QMC0303/33/-62.0/-1.0 5) QMC0233/30/-62.0/-1.0 6) QBL0041/34/-62.0/-1.0 Best server (Active link) TOP X (Existing Neighbors) TOP X (Missing Neighbors/Polluters)
Example of pollution Area: (Detailed overview) Active Set Size = 6 (6 cells are detected within 3dB against the best server)
Powered by www.agileto.com
Pt_nr = 6708 Time_Stamp = 10:40:18.504 ActiveSet_Size = 6 MaxLink_Dist=45.0Km 1) QDH0021/6/-59.0/34.0 2) QDH0022/4/-60.0/35.0 3) QBL0023/27/-61.0/-1.0 4) QMC0303/33/-62.0/-1.0 5) QMC0233/30/-62.0/-1.0 6) QBL0041/34/-62.0/-1.0 The pollution is generated by cells outside the cluster placed on high altitude like it may be seen for one case (QMC0233) on the path profile presented on the right side.
Cluster DT analysis: Pollution
26
Example of pollution Area: (General overview) Active Set Size = 6 (6 cells are detected within 3dB against the best server)
Powered by www.agileto.com
Cluster DT analysis: Pollution
27
Case of pollution Area: Cell: QMC0233 Although this cell is outside of the cluster area (~45Km) it has an important coverage inside the cluster area due to its dominant position (altitude =40m comparing with cluster altitude =2m) On the right side it is presented the coverage limits of this cell inside the cluster and the color lines present even the points/cases where this cell was detected as Top1 ! It is suggested to apply more tilt on its antennae from the actual values: H_Antenna = 39m El_Tilt = 2, Mec_Tilt = 0 Suggested new tilts: El_Tilt = 5.5, Mec_Tilt = 0
Powered by www.agileto.com
Cluster DT analysis: Pollution
28
Case of pollution Area: Cell: QBL00233 Although this cell is outside of the cluster area (~25Km) it has an important coverage inside the cluster area due to its dominant position (altitude =275m comparing with cluster altitude =20m) On the right side it is presented the coverage limits of this cell inside the cluster and the color lines present even the points/cases where this cell was detected as Top1 ! It is suggested to apply more tilt on its antennae from the actual values: H_Antenna = 39m El_Tilt = 3, Mec_Tilt = 0 Suggested new tilts: El_Tilt = 5, Mec_Tilt = 0
Powered by www.agileto.com
Cluster DT analysis: Pollution
29
Case of pollution Area: Cell: QMC0303 Although this cell is outside of the cluster area (~56Km) it has an important coverage inside the cluster area due to its dominant position (altitude =44m comparing with cluster altitude =2m) On the right side it is presented the coverage limits of this cell inside the cluster and the color lines present even the points/cases where this cell was detected as Top1 ! It is suggested to apply more tilt on its antennae from the actual values: H_Antenna = 46m El_Tilt = 6, Mec_Tilt = 4 Suggested new tilts: El_Tilt = 6, Mec_Tilt = 5
Powered by www.agileto.com
Cluster DT analysis: Pollution
30
Case of pollution Area: Cell: QBL0041 (similar approach should be taken for the other co-site cells QBL0042 respective QBL0043)
Although this cell is outside of the cluster area (~27Km) it has an important coverage inside the cluster area due to its dominant position (altitude =250m comparing with cluster altitude =20m)
On the right side it is presented the coverage limits of this cell inside the cluster and the color lines present even the points/cases where this cell was detected as Top1 !
It is suggested to apply more tilt on its antennae from the actual values: H_Antenna = 39m El_Tilt = 2, Mec_Tilt = 2
Suggested new tilts: El_Tilt = 4, Mec_Tilt = 2
Powered by www.agileto.com
Coverage area vs Coverage efficiency Coverage efficiency of one cell is an Agileto concept
presenting the ratio between the specific coverage area of one cell (seen as Top1 – TopX) and its full (total) coverage area where the cell has been detected during the drive test.
According with the cell position related to the best cell (Top1), there are mainly two interesting coverage areas efficiency, as following: • 1) Coverage Top1 efficiency • 2) Coverage ASet (Active Set) efficiency
The values of the coverage areas efficiency may
provide a good indication if a cell is a polluter or has a lack of coverage – see some examples on the right side for several cells.
The line in purple background (right side) is detailed into the next slide as an example.
Google Earth cells coverage areas representations and the related spreadsheet containing all the cells belonging to the cluster are attached for further investigation.
32
Powered by www.agileto.com
Coverage areas: Top1/ASet/Full:
(for the selected cell 3G-DHA008M13-QNH)
Area where the cell is detected as the best server (Top1) (green border): Top1 Cvg area = 5.6 km²
Area where the cell is detected into Active Set range of 3dB (blue border): ASet Cvg area = 10.4 km²
Area where the cell is detected in Full Coverage (red border): Full Cvg area = 29.9 km²
Coverage Efficiency: Top1/ASet:
Definition: Cvg Efficiency [Top1 or ASet] = [Top1 or Aset] Cvg Area / Full Cvg Area
Coverage efficiency [Top1] = 18.67% ( 5.6 / 29.9 )
Coverage efficiency [ASet] = 34.84% ( 10.4 / 29.9 )
33
Coverage area vs Coverage efficiency
Top1 ASet Full
Powered by www.agileto.com
Cluster DT analysis: Over-shooters Top Nr. of Worst overshooters (≥ 21 affected cells/overshooter): 11
35
Top
11
wo
rst
ove
rsh
oo
ters
OS
Number
Nr of Cells
Affected
per OS
OS LAC
(Overshooter)
OS
LocalCID
Overshooter
CellNameOS BCCH
Region
Overshooter
1 28 13511 10202 QBL0042 37 Cluster_QNH_08
2 26 13511 13023 QMC0513 25 Cluster_QNH_12
3 24 13511 10613 QMC0233 30 Cluster_QNH_10
4 24 13511 10023 QMC0253 35 Cluster_QNH_10
5 23 13511 12682 QMC0342 24 Cluster_QNH_11
6 22 13511 10251 QBL0021 32 Cluster_QNH_08
7 22 13511 10263 QMC0283 26 Cluster_QNH_10
8 22 13511 10261 QMC0281 28 Cluster_QNH_10
9 22 13511 12252 QMC0132 31 Cluster_QNH_12
10 21 13511 10201 QBL0041 34 Cluster_QNH_08
11 21 13511 10013 QHH0203 36 Cluster_QNH_10
12 18 13511 10363 QMC0303 33 Cluster_QNH_10
13 17 13511 10203 QBL0043 29 Cluster_QNH_08
14 17 13511 12343 QMC0203 38 Cluster_QNH_11
15 14 13511 10253 QBL0023 27 Cluster_QNH_08
16 13 13511 10011 QHH0201 41 Cluster_QNH_10
17 11 13511 10801 QDH0121 10 Cluster_QNH_07
18 10 13511 12521 QDH0091 12 Cluster_QNH_07
19 10 13511 12673 QTY0093 9 Cluster_QNH_07
20 10 13511 10012 QHH0202 39 Cluster_QNH_10
21 10 13511 12591 QMC0291 30 Cluster_QNH_11
22 10 13511 12903 QTY0103 7 Cluster_QNH_07
The table on the right side presents the Overshooters (OS) cells automatically detected by Agileto tool during the drive test post-processing and analysis of the input data. This table is sorted in descending order from the worst overshooter cell - based on the number of affected/ polluted cells - to the last important detected. The full table containing all the details concerning all the overshooters cells detected during the drive test together with their representation in Google Earth are provided as attachments to this report. This section will present screenshots with detailed representation of the affected cells for the first worst Top 5 overshooters detected. The other overshooters detected may be investigated - case by case - on Google Earth by using the full Google Earth package (files) provided for multiple topics (Top1/Full coverage, Coverage areas, Overshooters, etc) in order to classify if further actions are required. Notice: You may remark that in many cases the Overshooter cells detected may represent the same cells detected on “Pollution” section and this is the confirmation (double check) of the right analysis performed.
Powered by www.agileto.com
Cluster DT analysis: Over-shooters Top Nr. of Worst overshooters (≥ 21 affected cells/overshooter): 11
36
Nr of OS
(Overshooters)
Nr of Cells
Affected
per OS
1 28
1 26
2 24
1 23
4 22
2 21
1 18
2 17
1 14
1 13
1 11
5 10
2 9
2 8
5 7
7 6
11 5
9 4
13 3
18 2
20 1
Top 11 worst overshooters
Top
11
o
vers
ho
ote
rs
Powered by www.agileto.com
Over-shooter cell: QBL0042 (automatically detected by Agileto)
• Nr. of affected cells: 28
The green lines are links between the overshooter cell and all its affected cells. At the edge of each line is presented the order of the affected cell per overshooter based on the number of occurrences detected during the drive test -> Ex: 22[2].
Top worst overshooters Cells
QBL0042 Cell Code = G13511.10202_2 BCCH = 37 GSM Band = GSM900 Cell_Id = 10202 Sector_ID = 2 Azimuth = 50 Antennas = Ant_Height = 39 El_Tilt = 5 Mec_Tilt = 2 BCC = 4 NCC = 3 LAC = 13511
37
Powered by www.agileto.com
Over-shooter cell: QMC0513 (automatically detected by Agileto)
• Nr. of affected cells: 26
The green lines are links between the overshooter cell and all its affected cells. At the edge of each line is presented the order of the affected cell per overshooter based on the number of occurrences detected during the drive test.
Top worst overshooters Cells
QMC0513 Cell Code = G13511.13023_3 BCCH = 25 GSM Band = GSM900 Cell_Id = 13023 Sector_ID = 3 Azimuth = 250 Antennas = Ant_Height = 33 El_Tilt = 6 Mec_Tilt = 0 BCC = 0 NCC = 6 LAC = 13511
38
Powered by www.agileto.com
Over-shooter cell: QMC0233 (automatically detected by Agileto)
• Nr. of affected cells: 24
The green lines are links between the overshooter cell and all its affected cells. At the edge of each line is presented the order of the affected cell per overshooter based on the number of occurrences detected during the drive test.
Top worst overshooters Cells
QMC0233 Cell Code = G13511.10613_3 BCCH = 30 GSM Band = GSM900 Cell_Id = 10613 Sector_ID = 3 Azimuth = 220 Antennas = Ant_Height = 39 El_Tilt = 2 Mec_Tilt = 0 BCC = 7 NCC = 7 LAC = 13511
39
Powered by www.agileto.com
Over-shooter cell: QMC0253 (automatically detected by Agileto)
• Nr. of affected cells: 24
The green lines are links between the overshooter cell and all its affected cells. At the edge of each line is presented the order of the affected cell per overshooter based on the number of occurrences detected during the drive test.
Top worst overshooters Cells
QMC0253 Cell Code = G13511.10023_3 BCCH = 35 GSM Band = GSM900 Cell_Id = 10023 Sector_ID = 3 Azimuth = 220 Antennas = Ant_Height = 42 El_Tilt = 2 Mec_Tilt = 0 BCC = 6 NCC = 0 LAC = 13511
40
Powered by www.agileto.com
Over-shooter cell: QMC0342 (automatically detected by Agileto)
• Nr. of affected cells: 23
The green lines are links between the overshooter cell and all its affected cells. At the edge of each line is presented the order of the affected cell per overshooter based on the number of occurrences detected during the drive test.
Top worst overshooters Cells
QMC0342 Cell Code = G13511.12682_2 BCCH = 24 GSM Band = GSM900 Cell_Id = 12682 Sector_ID = 2 Azimuth = 150 Antennas = Ant_Height = 28 El_Tilt = 6 Mec_Tilt = 0 BCC = 1 NCC = 3 LAC = 13511
41
Powered by www.agileto.com
Missing Neighbors 2G-2G Neighbors audit and optimization analysis has been performed based on the Drive Test input data and the results have been compared with the neighbors declarations detected into OMC/OSS snapshot/dump files. The complete neighbor results (Detected/Missing/Not Detected) provided by Agileto tool after post-processing the drive test input data are provided as attachment to this report. There are provided as well the Google Earth files containing the neighbors representation where the neighbors results from the tabular format may be visualized in Google Earth environment for supplementary checking if desired. Supplementary, the simulation movie along the drive test route representing the radio links between each drive test measurement point and all the Cells from ASet is provided (where the missing neighbors are provided with red colors) an it may run in Google Earth (GE) environment as so called “Tour”. If desired, this movie may be accessed in GE and used like an ordinary movie with Play/Pause/FastForward, etc in order to arrive quickly and investigate the desired area around a specific timestamp.
Powered by www.agileto.com
Missing Neighbors detection (automatic)
An example of the 2G-2G neighbors case proposal, detected & generated by Agileto is displayed on the right side, as following:
Missing neighbors (# 7)
Detected (Maintained) neighbors (# 6)
Detected (LI = Low Importance) (# 2)
Missing LI (Low Importance) (#7)
Not Detected neighbors (# 18) Obs. The optimization results have considered the minimum ‘weight’ related to the Nr. of occurrences Source-Target as to be > 2%. All cases which do not meet the ‘weight’ criteria are provided with ‘negative’ priority which means NO neighbor proposition.
43
Powered by www.agileto.com
2G-2G (automatic) Neighbors optimization Example of the 2G-2G Neighbors Optimisation generated by Agileto: The missing neighbors relations are presented with red lines The maintained neighbors relations are presented with blue lines. The pink lines are presenting the existing neighbors declarations which are NOT meeting the weight criteria (2%). The green lines are presenting potential new neighbors declarations but which do not meet the minimum weight criteria (2% on our case). Obs. Each neighbor line is presenting at the edge the priority proposal and the relative contribution [%] detected during the drive test. Cell: QDH0073 =>
NB_Proposals: 20 NB_Maintained: 7 NB_Missing: 13 NB_Declared_LI: 8 NB_Missing_LI: 13 NB_Not Detected: 14
44
Powered by www.agileto.com
2G-2G (automatic) Neighbors optimization Example of the 2G-2G Neighbors Optimisation generated by Agileto: Cell: QDH0073 => Global overview: Until all the cells detected as Overshooters will be regulated (more downtilt on their antennas) it is reccomended to add them as neighbors cells (reciprocally) in order to avoid drops which may occur when the mobile originates the call on the overshooter then it moves out of its coverage area on a local cell.
Reciprocally, when the mobile originate on the local cell it should be able to HO to the far cell in order to avoid drops due to low S/N signal RF ratio which may lead finally to drop call.
(Table containing all Missing NB is attached)
NB_Proposals: 20 NB_Maintained: 7 NB_Missing: 13 NB_Declared_LI: 8 NB_Missing_LI: 13 NB_Not Detected: 14
45
Powered by www.agileto.com
BCCH Audit & Optimization + wrong BCCH allocation detected
Powered by www.agileto.com
BCCH Optimization proposal provided by Agileto
Agileto dedicated module (M2.3) provides the optimum change value for the wrong BCCHs cases detected during the drive test analysis by providing as input just the Cell Name for the desired 2G Cell which need to change its BCCH.
47
On this section will be presented the cases automatically detected by Agileto as the ‘Wrong BCCH allocation’ during the drive test analysis and there will be provided the new BCCHs proposals in order to avoid important interference.
Powered by www.agileto.com
BCCH Audit provided by Agileto On the right side it is presented a screenshot of the general BCCH audit table over the entire 2G network generated by Agileto tool (M2.3) concerning the cells belonging the cluster under investigation. The table has been filtered for the most critical cases detected with a limited set co-channel distance up to 5km.
(The entire table is attached to this report)
The yellow columns display the cells with the minimum repeated distance of the BCCH co-channel.
The green and blue columns show the Adjacent channel inferior and Adjacent channel superior with their minimum repeated distance.
The cells with red color are few examples which are detected (as well) and presented into this section after the drive tests BCCH wrong planning analysis investigation.
48
Powered by www.agileto.com
BCCH wrong planning detection optimized by Agileto On the right side there are presented the cells detected during the drive test analysis with the ‘Wrong BCCH planning allocation’ meaning that two different cells which share the same BCCH may be declared as neighbors to a specific source cell (and therefore a conflict may occur). Some suggestive cases from those displayed on the right side are presented in Google Earth environment (furthermore on this section) where the cells detected in conflict by sharing the same BCCH are linked together with a red line while each one is linked by the source cell with a yellow line. The full table presented on the right side (*.xls) together with the Google Earth package presenting the “WrongPlanBCCH” detected during the drive test are attached to this report for future investigation. On the right side there are presented the BCCH changes proposals for the selected cells (detected to have BCCH in conflict) after using Agileto module M2.3 by getting optimum BCCH values. => Total = 38 BCCHs changes.
49
Cells sharing same BCCH Cells BCCHs to be changed
Case Number Common
BCCH Cell 1 Cell 2 Cell 3
Cell Change_1
New BCCH_1 Cell Change_2
New BCCH_2
1 6 QDH0021 QDH0093 QTY0122 QDH0093 19 QTY0122 17
2 11 QTY0052 QDH0102 QDH0102 20
3 9 QDH0082 QDH0053 QDH0071 QDH0053 21 QDH0071 18
4 5 QDH0052 QDH0113 QDH0113 31
5 4 QDH0073 QDH0022 QTY0051 QDH0022 0 QTY0051 22
6 4 QTY0051 QDH0081 QDH0041 QDH0081 23 QDH0041 25
7 2 QDH0061 QDH0111 QDH0111 24
8 10 QDH0032 QDH0121 QDH0062 QDH0121 33 QDH0062 28
9 7 QDH0103 QDH0072 QDH0083 QDH0072 30 QDH0083 40
10 3 QDH0101 QDH0092 QDH0092 17
11 12 QDH0051 QDH0091 QDH0063 QDH0091 42 QDH0063 20
12 6 QTY0092 QTY0073 QTY0073 16
13 5 QTY0241 QDH0012 QDH0012 38 QTY0241 35
14 3 QDH0101 QDH0013 QDH0013 15
15 10 QDH0032 QTY0102 QTY0102 23
16 512 QTY0145 QHH0014 QHH0014 513
17 7 QDH0103 QTY0103 QTY0062 QTY0103 26 QTY0062 36
18 8 QTY0053 QTY0243 QTY0243 41
19 6 QDH0021 QDH0031 QDH0031 34 QDH0021 14
20 11 QTY0052 QTY0242 QTY0242 13
21 4 QDH0073 QTY0091 QTY0101 QTY0091 0 QTY0101 36
22 2 QDH0033 QTY0121 QTY0121 42 QDH0033 29
23 12 QDH0051 QTY0123 QTY0151 QTY0123 19 QTY0151 33
24 9 QTY0093 QTY0071 QTY0061 QTY0071 39 QTY0061 27
Powered by www.agileto.com
wrong BCCH allocation detection
50
Case of wrong BCCH detected:
BCCH = 6 Two cells are sharing the same BCCH: Cell 1: QDH0093 Cell 2: QDH0021 Due to the negative impact on the network performance it is recommended to change the BCCH for one cell in order to avoid possible interference which may degrade important KPIs like CSSR and/or CDR. Based on Agileto module M2.3 we get the optimum new BCCH value: Cell change: QDH0093 New BCCH: 19
Powered by www.agileto.com
wrong BCCH allocation detection
51
Case of wrong BCCH detected:
BCCH = 5 Two cells are sharing the same BCCH: Cell 1: QDH0052 Cell 2: QDH0113 Due to the negative impact on the network performance it is recommended to change the BCCH for one cell in order to avoid possible interference which may degrade important KPIs like CSSR and/or CDR. Based on Agileto module M2.3 we get the optimum new BCCH value: Cell change: QDH0113 New BCCH: 31
Powered by www.agileto.com
wrong BCCH allocation detection
52
Case of wrong BCCH detected:
BCCH = 9 Two cells are sharing the same BCCH: Cell 1: QDH0082 Cell 2: QDH0053 Due to the negative impact on the network performance it is recommended to change the BCCH for one cell in order to avoid possible interference which may degrade important KPIs like CSSR and/or CDR. Based on Agileto module M2.3 we get the optimum new BCCH value: Cell change: QDH0053 New BCCH: 21
Powered by www.agileto.com
wrong BCCH allocation detection
53
Case of wrong BCCH detected:
BCCH = 4 Two cells are sharing the same BCCH: Cell 1: QTY0051 Cell 2: QDH0081 Due to the negative impact on the network performance it is recommended to change the BCCH for one cell in order to avoid possible interference which may degrade important KPIs like CSSR and/or CDR. Based on Agileto module M2.3 we get the optimum new BCCH value: Cell change: QDH0081 New BCCH: 23
Powered by www.agileto.com
wrong BCCH allocation detection
54
Case of wrong BCCH detected:
BCCH = 4 Two cells are sharing the same BCCH: Cell 1: QDH0073 Cell 2: QDH0081 Due to the negative impact on the network performance it is recommended to change the BCCH for one cell in order to avoid possible interference which may degrade important KPIs like CSSR and/or CDR. Based on Agileto module M2.3 we get the optimum new BCCH value: Cell change: QDH0081 New BCCH: 23
Powered by www.agileto.com
Automatic cross feeders detection After processing the drive test (DT) input data Agileto tool provides automatically analysis regarding the cross sectors/feeders detection based on the following elements: • Cells geographically position (Lat/Long); • Cells antennae’s azimuth; • DT Measurement point positions (Lat/Long) where the
cells has been detected.
Based on automatically analysis there are detected how many points [%] are detected inside the antennae’s beamwidth (Good) and how many points are detected outside (Bad). If the nr. of ‘Bad’ points is greater than the nr. of ‘Good’ points it is flagged like having a Cross Sector (TRUE). This analysis is performed for two cases representing the situations where the cell was detected in Full coverage and the situations where the cell was detected as Top1. On the right side it is presented this output table concerning the ‘CrossSector’ analysis where it was emphasized with red color one case where the sectors 1/2/3 have been swapped like 3/1/2 (this double check may be seen into the next page presenting the full coverage points for each sector).
56
Cell_Name LAC|Cell_ID AzimuthCvg All
Pts
Cvg
PtsGood
[%]
Cvg
PtsBad
[%]
CrossSect
or CvgAllTop1 Pts
Top1
PtsGood
[%]
Top
PtsBad
[%]
CrossSect
or Top1
QDH0011 13511|10031 0 29 0 100 TRUE 0 FALSE
QDH0012 13511|10032 100 202 39.11 60.89 TRUE 111 23.42 76.58 TRUE
QDH0041 13511|10481 30 475 45.89 54.11 TRUE 127 94.49 5.51 FALSE
QDH0062 13511|12762 150 230 9.13 90.87 TRUE 31 54.84 45.16 FALSE
QDH0063 13511|12763 240 315 22.22 77.78 TRUE 9 55.56 44.44 FALSE
QDH0072 13511|12892 150 90 14.44 85.56 TRUE 15 73.33 26.67 FALSE
QDH0121 13511|10801 330 185 44.86 55.14 TRUE 0 FALSE
QDH0122 13511|10802 130 18 0 100 TRUE 0 FALSE
QHH0014 13511|60771 300 180 33.33 66.67 TRUE 29 72.41 27.59 FALSE
QTY0061 13511|10051 70 194 0 100 TRUE 4 0 100 TRUE
QTY0091 13511|12671 80 150 3.33 96.67 TRUE 99 0 100 TRUE
QTY0092 13511|12672 160 580 38.28 61.72 TRUE 118 13.56 86.44 TRUE
QTY0093 13511|12673 290 445 4.04 95.96 TRUE 9 33.33 66.67 TRUE
QTY0103 13511|12903 270 187 11.23 88.77 TRUE 2 0 100 TRUE
QTY0122 13511|10882 80 1012 34.49 65.51 TRUE 285 45.61 54.39 TRUE
QTY0123 13511|10883 270 1281 44.26 55.74 TRUE 190 85.79 14.21 FALSE
QTY0182 13511|12472 150 479 10.86 89.14 TRUE 39 97.44 2.56 FALSE
Powered by www.agileto.com
Automatic cross feeders detection
Sector 3 (QTY0093)
57
Sector 1 (QTY0091)
Sector 2 (QTY0092)
Powered by www.agileto.com
Thank you
Agileto www.agileto.com
Agileto
What kind of services are we providing currently ?
• Network Optimization services (including roll-out or/and swap) for any mobile
networks (2G/3G/4G) from small clusters to large (BSCs/RNCs/TACs) areas;
• Benchmark analysis on multiple drive test metrics/networks;
• Enhanced Agileto PRO Edition license(s) for your own usage;
We are providing for FREE our services as POC (Proof Of Concept) for all our new clients so do not hesitate to contact us Today !
Agileto
Contact details:
Sales: [email protected]
Support: [email protected]
Web site: www.agileto.com