Plan Checker3Gv6

Plan_Checker3Gv6.mbx

By: Dayanti PratiwiFirst Version Released: Plan_Checker1.0.mbx on 1st July 1999

Was developed under:• Windows XP• MapInfo/MapBasic 7

1 © 2006 Nokia Plan_Checker3Gv6.ppt / 2006-06-26 / DP

Necessary Header/Column for BTS Table

• BTS_NAME• BSC_RNC_ID• LAC• CI• X: Longitude• Y: Latitude• NUM_SECT:

• #of sector 1 for single cell; > 1 for quasi antennas• AZM1 to AZM4 (azimuth)

• -2 for indoor (small square)• -1 for omni antenna (circle)• If single cell just use AZM1 and others put 0

• CELL_TYPE: Macro, Micro, Indoor• CELL_SYST: DCS, GSM, WCDMA• NCC• BCC• BCCH_3GFREQ1: put 0 if not use• TCH1_3GSC1: put 0 if not use• TCH2_3GFREQ2: put 0 if not use• TCH3_3GSC2: put 0 if not use• TCH4_3GFREQ3: put 0 if not use• TCH5_3GSC3: put 0 if not use• TCH6_3GFREQ4: put 0 if not use• TCH7_3GSC4: put 0 if not use• SIZE (optional): in meter


• NOTE:⇒Minimal columns use for drawing are:

⇒X, Y, NUM_SECT, AZM1 to AZM4, CELL_TYPE, CELL_SYST, SIZE (optional)⇒ if you only want to draw the cell without checking, usually during nominal plan

BTS Table


• There will be 2 options for HO Table Used:• Option1 HOTable: Use (SOURCE_NAME) vs (TARGET_NAME) Reference

⇒Will link the related BTS_NAME only⇒Necessary header/column for HO Table: SOURCE_NAME, TARGET_NAME

Necessary Header/Column for HO Table

• Option2 HOTable: Use (BSC_RNC_ID & SOURCE_CI) vs (TARGET_LAC & TARGET_CI) Reference⇒The CI can not unique network-wide if the number already exceed 65535⇒Necessary header/column for HO Table: BSC_RNC_ID, SOURCE_CI, TARGET_LAC, TARGET_CI


Tips & Tricks


• Better use .txt format for the input data (BTStable, HOtable)• The yellow header in previous page are the MUST columns• The columns place are flexible, example; you can put BTS_NAME at 1st; 2nd; or even at last

position• The columns number are flexible, you can add any columns for additional info• BCCH_3GFREQ1; TCH1_3GSC1; TCH2_3GFREQ2; TCH3_3GSC2; TCH4_3GFREQ3; TCH5_3GSC3;

TCH6_3GFREQ4; TCH7_3GSC4 • Are common columns between 2G and 3G data• If 2G then fill with the 2G-frequency (BCCH, TCH1, TCH2 ... TCH7)• If 3G then fill with the 3G-frequency (3GFREQ1 … 3GFREQ4) and 3G-Scrambling Code (3GSC1 …

3GSC4)• BSC_RNC_ID also common column between 2G and 3G data

• If 2G then fill with the 2G-BSC_ID• If 3G then fill with the 3G-RNC_ID

• We can use PlanEdit database for reference • We can export ADJACENT_CELL object from .mdb PlanEdit to create the HOtable• We can export BTS object from .mdb PlanEdit as reference for BTStable

Tips & Tricks


• No need to create specific directory nor specific table name• Use decimal degree format for X & Y column• Three different style of drawing the btstable for your presentation purposes• Below columns must have value (= 0) if you want to do the HO checking and neighbors

audit using Option2 HOTable, coz the data will be used as reference• BTS Table (BSC_RNC_ID; CI; LAC) & HO Table (BSC_RNC_ID; SOURCE_CI; TARGET_LAC; TARGET_CI)

• Neighbor audit menu• Delete/Create HO, the list of deleted/created relation will be recorded in tabnameAudit.TAB

• Checking the existing 2G-NCC;2G-BCC;2G-Frequency;3G-Scrambling Code used in defined radius

• Toolbar application make the checking much faster and easier• Mapping the KPI from different table and create the thematic on the map

• Use BTS_NAME column header in KPI table to link with BTS_NAME in BTStable• Connect the measurement data with related cell using Line Connection

• Use CI (as integer) column header in measurement table to link with CI (as Integer) in BTStable

Note: Please exit the tools and run again if you found problem cannot draw the btstable when you re-created directly, this is related with memory management from MapInfo7, I still have no idea how to fix it yet.


Creating Reference BTS Table


Flexible for any data type (txt/xls/mdb)The simplest one is .txt format, minimize your mistakes if you forgot to put 0 value when no data


Arrow style

Clover1 style⇒The DCS; GSM; WCDMA data keep maintain in one table

Micro Indoor

Macro GSM

Macro DCS

Clover2 style⇒The DCS; GSM; WCDMA data will be split into three different table

Clover1 style using user defined from column SIZE value

SIZE = 100 m

Size = 300 m

Macro WCDMA


Display Checker Toolbar


Open BTS Table as Reference


You need to open the btstable first before continue with the checker menus

Checker Toolbar


Clear Search PointerSearch Cell Location

Toggle to Activate Frequency Checker Toggle to Activate Scrambling Code Checker

New Freq or SC

Previous Freq or SCNext Freq or SC

Check co-3GFREQ SC SetToggle to Activate BSIC or SC Group Checker

Check co-BSIC_BCCHCheck co-BSIC only

Clear Radius ObjectChecking in Radius

Toggle to Activate Handover Checker

Search Source Cell Packing HO Table

Display Incoming NeighborsDisplay Outgoing Neighbors

Delete Both-way NeighborsCreate Both-way Neighbors

Delete One-way NeighborsCreate One-way Neighbors

Export Audit Neighbors

Search Cell Location (can be applied in any checker windows)


To Clear Search Pointer on Map


2G Frequency OR 3G Scrambling Code Checker(will be applied in 2G Frequency OR 3G Scrambling Code checker window)

The check reference is 2G-FreqGSM ch-55



By clicking the Next Freq or SCbutton, the check reference willincrease one by one, in this samplebecome 2G-Freq GSM ch-56



By clicking the Previous Freq or SCbutton, the check reference willdecrease one by one, in this sampleback to 2G-Freq GSM ch-55



The check reference is 3G-SC 10



By clicking the Next Freq or SCbutton, the check reference willincrease one by one, in this samplebecome 3G-Scrambling Code 11



By clicking the Previous Freq or SCbutton, the check reference willdecrease one by one, in this sampleback to 3G-Scrambling Code 10


2G BSIC OR 3G Code Group Checker(will be applied in 2G BSIC OR 3G Code Group checker window)

The check reference is 2G cells which is used NCC=1; BCC=5 both in GSM & DCS layer



The check reference is 2G cells which is used NCC=1; BCC=5; BCCH=51



The check reference is 3G cells which is used Freq=10563; SC=289


Check In Radius (can be applied in any checker windows)

select

To Clear Radius Object on Map


Handover Checker(will be applied in 2G AND 3G Handover checker window)

When activate for the first time,Automatically will display the “Properties of HO Table Used” and“Open File” dialog to select the HO Table reference


If using Option1 HOTable





If using “Select New Source” buttonthen always display outgoing HOas the result

In message window we can see the info number of adjacent cells; and also the distance with each neighbor



We also can get the same result byselect directly the sector object to display the outgoing neighbors

select



By select directly the sector object we can display the incoming neighbors as well

select



We can select directly the sectorobject during the checking mode to display the next handover checking

select



select

select

select

select

Create both-way neighbors

Outgoing HO

We can use multiple select to add new neighbors

Incoming HO



select

select

select

select

Create one-way neighbors

Outgoing HO

We can use multiple select to add new neighbors

Incoming HO


Handover Checker(will be applied in 2G AND 3G Handover checker window) Delete both-way

neighbors

selectOutgoing HO

We can use multiple select to delete existing neighbors

Incoming HO


Handover Checker(will be applied in 2G AND 3G Handover checker window) Delete one-way

neighbors

selectOutgoing HO

We can use multiple select to delete existing neighbors

Incoming HO





Your delete/create list result will be saved in the new tableAudit.TAB in the same directory with your other data

If you export the Audit Result will be saved as tabnameAuditExp.txtYou can check the file on Explorer



When you delete the adjacency from the HO list there will be blank rows in the HO table, you can “Packing” the HO table to clean up the blank rows after you finished the neighbor audit


Arrange Window Checker(will display two selected windows side by side)


KPI Checker(will open new KPI checker window)

Open KPI tableYou can use any data and no need to create specific table/columns name

Column from KPI table that you want to display will be inserted temporarily into BTS table

If you want to modify the previous threshold and redraw the result


Line Connection(will open new Line Connection BTS vs Measurement Data window)

You can use any measurement data (NEMO; TOM ; TEMS ; Agilent; etc) as long as you have CI column with integer type in your measurement_data .TAB tableThe export from TEMS usually the CI in character format, need tochange to be integer from Table=>Maintenance=>Table Structure

The result will be saved in measnameLine.TAB in the same directory and the original point measurement data still exist

Need to make point the measurement data and save as in MapInfo format before use this menuThe reason of “Save As” to make the object become editable, if not the raw data still keep in .txt (sample)To be NOTED; you have to prepare the btstable with the same CI status when the drivetest was conducted

Sample Exercise

• Together with the Plan_Checker3Gv6.zip we attached the sample dummy network adopt from worldcap.TAB in MapInfo

• The btstable created from worldcap_bts.txt using “Clover1” + “From SIZE Column” drawing mode

• The HOtable was created for co-site in the same band only, you can playing around to add/delete the neighbors

• You can open KPI table directly in .txt format; the data will be mapping into current BTStable

• Try to visualize the DCR with ranges• Red 5 … 10• Yellow 1 … 5• Green 0 … 1

• Try mapping another KPI (HO_Failure & HO_Success)• Sorry; I can not create dummy data for line connection, or maybe any of you

would like to do drivetest around the world ☺


Have a nice day☺

Note: we are using dummy data for the samplehope useful for everybody


Documents

Plan Checker3Gv6