Actix Cellrefs

8/13/2019 Actix Cellrefs

1/24

equired CellRefs Fields

This topic provides a summary of the fields that mustbe present in the CellRefs file for Analyzer to workcorrectly. There are some fields that are always required and others that are required for specific technologiesand solutions.

equired Fields: All Technologies and Solutions

te-Level Fields

ector-Level Fields

dditional Fields by Technology

ector-Level Fields

GSM

In This Topic See Also

All Technologies and SolutionsAdditional Fields by TechnologyAdditional Fields Used by Veritune

CellRefs Fields: CDMACellRefs Fields: EVDOCellRefs Fields: GSMCellRefs Fields: UMTS TDD (UTDD)

CellRefs Fields: WCDMA

Field Description

Si t eI D The ID of the site (base station).Lat i tude The site's latitude expressed as a decimal number representing the degrees in the WGS 84

projection system.

Longi t ude The site's longitude expressed as a decimal number representing the degrees in the WGS 84projection system.

Field Description

TECHNOLOGY_Si t eI DFor Cel l The ID of the site to which the sector belongs.Sect or_I D The ID of the cell or sector within the site.Azi mut h The sector's azimuth angle relative to true North, expressed in degrees. If

this field is missing or does not contain a sensible value, the sector will beshown pointing due North on the map.

Beamwi dt h The sector's beam width angle expressed in degrees. Used to control thesize of the sector wedges on the map. If this field is missing or does not

contain a sensible value, the sector will be shown on the map as a narrow

line rather than a wedge.

Field Description

BCCH The base station control channel.CI The cell identity code.BSI C The base station identity code.

MCC The mobile country code. This is an optional field. However, in some networks the CI isnot sufficient to uniquely identify each cell. In these circumstances, the MCC isrequired for the full cell global identity (CGI, which consists of the MCC, MNC, LAC, andCI) that is necessary for the correct identification of each cell.

MNC The mobile network code. This is an optional field. However, if the CI is not sufficientto uniquely identify each cell, the MNC is required (along with the MCC and LAC) forthe full CGI.

LAC The location area code. This is an optional field. However, if the CI is not sufficient touniquely identify each cell, the LAC is required (along with the MCC and MNC) for thefull CGI.

TCHLi st A list of traffic channels. This is required for the TCH Co/adjacent Channel feature in

Spotlight and the GSM Cell Plan Viewer.NBorCI A list of neighbor cell IDs. This is required for the Neighbor List Analysis in Spotlightand the GSM Cell Plan Viewer.

adj acent Channel This field is required by the GSM Cell Plan Viewer in versions of Analyzer earlier thanSpotlight. It is a special internal field that must be present as the last field for the GSMcell network element in the .iniconfiguration file. However, the cellrefs file does notneed to store data for this field, because it is populated by the GSM Cell Plan Viewer.This field is not required from the introduction of Spotlight onwards.


2/24


3/24

echnology-Specific Information

CellRefs Fields: CDMA

CellRefs Fields: EVDOCellRefs Fields: GSM

CellRefs Fields: UMTS TDD (UTDD)CellRefs Fields: WCDMA

ee Also

Structure of the CellRefs FileCellRefs PreferencesVeritune PreferencesAdding New Fields to the CellRefs FileLines to CellsCellRefs HistoryCellRefs Limits

Send feedback on this topic

If this field is absent, all frequencies are assumed. Integer.

EI RP This optional field stores outward power of the sector in dBm. Ifthis field is present, Veritune adjusts it when you enter a value inthe Relative Power box. If this field is not present, Verituneadjusts the measured power value instead.

CDMA CDMA_Fr eq This optional field indicates the frequency in MHz in multi-frequency network configurations where PN varies with frequency.If this field is absent, all frequencies are assumed. Integer.

EI RP This optional field stores outward power of the sector in dBm. Ifthis field is present, Veritune adjusts it when you enter a value inthe Relative Power box. If this field is not present, Veritune

adjusts the measured power value instead.PctPi l ot Percentage of power allocated to pilot channel. Integer.PctTraf f i c Percentage of power allocated to traffic channels. Integer.Pct Pagi ng Percentage of power allocated to paging channel. Integer.Pct Sync Percentage of power allocated to synchronization channels.

Integer.


4/24

tructure of the CellRefs File

ontents

IntroductionThe DefNetworkData.inifileThe CellRefs file

ntroduction

Network configuration information (such as the names, IDs, and locations of the cell sites, etc.) is stored in atext file that is called the CellRefs file. This topic provides information about the structure of this file and the

configuration file (called DefNetworkData.ini), which defines its structure and format. You set the location ofthe CellRefs file in the Preferences dialog box. See CellRefs Preferencesfor more information.

The cellrefs file is a text file that stores information about actual physical network elements. The first line of thefile must be as follows:

#Net workData - dat af i l e

Each subsequent line in the file stores information about an individual network element (such as a cell or site).The information that is stored for each network element must correspond to the definition specified for thattype of network element in the DefNetworkData.inifile.

heD e f N e t w o r k D a t a . i n i

fileThe DefNetworkData.inifile is a configuration file that defines the structure and format of the information in theCellRefs files. The default DefNetworkData.inifile is located in the Program Files\Actix\Analyzer\Binfolder.However, you can override the default file with a custom onefor example, if you want to store additional data

about the network elements. This is done by creating a custom configuration file with the same name as thecellrefs file but with an .inifilename extension and placing it in the same folder as the cellrefs file. (Forexample, if the cellrefs file is called cellrefs.txt, the custom configuration file must be called cellrefs.ini.) Notethat the default configuration file is totally ignored when a custom configuration file is present.

The DefNetworkData.inifile contains two key sections[ Net work El ement s] and [F i el ds] and one or more

additional sections defining the root object in the hierarchy of net elements for a technology. The defaultDefNetworkData.inifile contains one of these elements, [ GSM_MSC] .

[Network Elements]. This section defines the different types of network element and the fields that arestored for each one using the Network_Element_Name=Field1 Field2 Field3. . . syntax. For example:

[ Network El ement s]CDMA_Si t e=Si t e_Name Si t eI D Lat i t ude Longi t udeCDMA_Cel l =CDMA_SiteIDForCell Sect or_I D Azi muth Beamwi dth EI RP PN MCC SI D NI D BI D Pct Pi l ot Pct TrafGSM_MSC=I D MSCNameGSM_BSC=I D MSCI D BSCNameGSM_Si t e=Si t e_Name Si t eI D Lat i t ude Longi t udeGSM_Cel l =GSM_Si t eI DFor Cel l Sect or _I D Azi mut h Beamwi dt h EI RP BCCH MCC MNC LAC CI BSI C BSCI D Face_

[Fields]. This section defines the properties of each field, including:

The format group(such as string, integer, degrees, or percentage) to be used for the data in the field.Format groups specify the data type and control how the information is formatted (for example, when it isdisplayed in the Map view). The format group can also be used to define valid values to be used to validatethe data when it is imported.

Whether the field is Required(must be present) or Key(must be present and unique).

Whether the field is an array field, which means that the field can contain a variable-length list of values(such as a neighbor list). These fields are specified using the arraykeyword, as shown for theCDMANeighborListfield below.

If the field maps one network element to another, the related field is defined using theRef:NetworkElement:Field:RelationTypeToOther#RelationToMesyntax. RelationTypeToOtherspecifies

the relationship between the network element and the linked object (typical examples are Parent andCellSite). RelationToMespecifies the reverse relationship (for example, Child and Cell).

In the snippet from the [ Network El ement s] section shown above, the CDMA_SiteIDForCellfield has been

highlighted. Below is a snippet from the [ Fi el ds] section, in which the same field has been highlighted. Notice

that the Refkeyword has been used to specify that this field is linked to the SiteIDfield in the CDMA_Site


5/24

network element.

[ Fi el ds]Test =ar r ay: i nt egerGSM_Si t eI DFor Cel l =Ref : GSM_Si t e: Si t eI D: Cel l Si t e#Cel l : keyCDMA_SiteIDForCell=Ref : CDMA_Si t e: Si t eI D: Cel l Si t e#Cel l : keyCDMA1xEVDO_Si t eI DFor Cel l =Ref : CDMA1xEVDO_Si t e: Si t eI D: Cel l Si t e#Cel l : keyS136_Si t eI DFor Cel l =Ref : I S- 54/ I S- 136_Si t e: Si t eI D: Cel l Si t e#Cel l : key

AMPS_Si t eI DFor Cel l =Ref : AMPS_Si t e: Si t eI D: Cel l Si t e#Cel l : keyDEN_Si t eI DFor Cel l =Ref : I DEN_Si t e: Si t eI D: Cel l Si t e#Cel l : key

TETRA_Si t eI DFor Cel l =Ref : TETRA_Si t e: Si t eI D: Cel l Si t e#Cel l : keyWCDMA_Si t eI DFor Cel l =Ref : WCDMA_Si t e: Si t eI D: Cel l Si t e#Cel l : key

MSCI D=Ref : GSM_MSC: I D: Parent #Chi l dBSCI D=Ref : GSM_BSC: I D: Parent #Chi l dSi t e_Name=Si t eSi t eI D=st r i ng: keyLat i t ude=Degr ees: r equi r edLongi t ude=Degr ees: r equi r ed

CDMANei ghbor Li st =arr ay: i nt eger

[GSM_MSC]. This section specifies that the GSM_MSCnetwork element is the root element in the hierarchy of

GSM network elements. Custom configuration files might contain an equivalent section for other technologies.

[ GSM_MSC]RootObj ect =yes

Entire default DefNetworkData.inifile

he CellRefs file

The cellrefs file is a tab-delimited text file that stores information about actual physical network elements. Withthe exception of the first line, each line in the file stores information about an individual network element (such

as a cell or site). The information that is stored for each network element must correspond to the definitionspecified for that type of network element in the DefNetworkData.inifile (which is described above). Thismeans that if a field is not used, an additional tab must be entered to retain the mapping of the subsequentfields. (However, this is not necessary for unused fields at the end of the line.)

Here is a snippet of a cellrefs file:

#Net workData - dat af i l eGSM_Cel l S_1 A 0 92 45 592 0 0 5004 40121 52GSM_Cel l S_1 B 130 92 45 599 0 0 5004 40122 52GSM_Cel l S_1 C 240 92 45 606 0 0 5004 40123 52

GSM_Si t e 91MOO1 91MOO 99. 94108333 99. 790222222GSM_Si t e 91MLL1 91MLL 99. 99913889 99. 803555556GSM_Si t e 91GTZ1 91GTZ 99. 02313889 99. 699555556

If we refer to the definition of the GSM_Sitenetwork element in the DefNetworkData.inifile above, we can see

that it is defined as GSM_Si t e=Si t e_Name Si t eI D Lat i t ude Longi t ude. This means that the information

shown for each GSM_Sitein the cellrefs file represents the site name, site ID, latitude, and longitude, in thatorder.

This Section

About the CellRefs Section

Required CellRefs FieldsAdding New Fields to the CellRefs File

Lines to Cells AlgorithmsCellRefs HistoryCellRefs Limits


6/24


CellRefs Fields: CDMACellRefs Fields: EVDOCellRefs Fields: GSMCellRefs Fields: UMTS TDD (UTDD)CellRefs Fields: WCDMA

elated Topics

CellRefs Preferences

Map Projections



7/24

ellRefs Preferences

The CellRefssettings in the Preferences dialogprovide configuration options for the CellRefs file, which storesnformation about the physical network.

IntroductionCellRefs preferencesUsing the manual import feature to create an import templateCellRefs fieldsImport file specificationData validation

ntroduction

When you first install the software, it is configured with an empty CellRefs file (called cellrefs.txt) located in theBin\CellRefsfolder within the user data area.

CellRefs files must have a specific format (which is described in Structure of the CellRefs File) and must containspecific fields. The fields that are required depend on the technology and solution you are using and aredescribed in Required CellRefs Fields.

If you already have an appropriately formatted CellRefs file containing your network data, you can simplychange the CellRefs File Locationin the Preferences dialog to the name and location of your file. Otherwise,you need to import your network data and save it as a CellRefs file.

Network data can come from a wide range of databases and systems, such as planning tools. Generally theseprovide a mechanism for exporting the data in a delimited text format that is suitable for import. You can

configure the software so that it automatically imports the network data again whenever it has changed.Alternatively you can import new network data manually when necessary or make small modifications in theNetwork Explorer.

Note: Currently only one CellRefs file can be used at a time.

ellRefs preferences

If you change the CellRefs file and the new file relates to the same technology (or combination of technologies)

that you were using before, you no do not need to restart the application in order for the changes to takeeffect. But if you change the CellRefs file afterloading log files, you may see some unexpected resultsfor

example, when you use the Lines to Cells feature on the map with those log files. Therefore, after changing theCellRefs file, you should generally close any log files that you loaded earlier, and if necessary, reload them.However, you must restart the application if you change a new CellRefs file that relates to a differenttechnology or combination of technologies.

File Location. Specifies the name and location of the current CellRefs file. This can either be an existing validCellRefs file or a blank text file that starts with the following line and into which you will import your networkconfiguration data:


8/24


9/24


10/24

Enter a name for the template.

Notice that the first page of the wizard has options for entering the field delimiter, the separators used forlists and decimal numbers, whether the first row contains headers, the latitude and longitude format andthe coordinate systemthat is used to record the locations. In this example we do not need to change any ofthese options because the defaults are suitable for use with our example file.

The lower part of the page provides a preview of the data, showing the column names and the values theycontain. If your text file uses a different delimiter, you need to specify the correct delimiter in the upperpart of the page, in order for the data preview to be displayed correctly.

Click Next, to move to the second page of the wizard, which you use to associate the columns in the textfile with the CellRefs fields.


11/24


12/24

Notice that although our import file contains an EIRPcolumn, it does not contain valid data, so we haveselected Ignorefor this column and entered a default value of zero. This means that this field will be set to

zero for every row. For more information about the various types of fields and how to add new fields, seeCellRefs fieldsbelow.

When you have finished, click Finish.

This imports the data using our new template and saves the template in the Bin\CellRefs\Tempatesfolderwithin the user data area. This means that the template will automatically appear in the list of templates forboth automatic and manual imports.

The network data is validated as it is imported and details of any errors are written to a log file. If any errors

occur, you need to open the log file and use the information it contains to track down the errors and correctthem, before attempting to import the data again. For more information. see Data validationbelow.

If the import is successful, the details are displayed in the Network Explorer. When you are satisfied that thedetails are correct, click the Savebutton (circled in red below) to save the details in the CellRefs file specifiedn the Preferences dialog.

ellRefs fields

This section provides information about setting the fields on the second page of the wizard.

Icons. These are used in the import wizard to indicate the various types of fields as shown in the followingtable.

Defaults. If you enter a default value for a field that is linked to a column, the default value is used whenthere is a gap in the input data. If you enter a default for a field that is set to Ignore, the default value is used

for every row.

CellRefs fields. The CellRefs fields are defined in the configuration file, as described in Structure of theCellRefs File. Detailed information is available about the standard CellRefs fields for the following technologies:

CDMA

EVDO

SiteID Site ID

Latitude Lat

Longitude Long

Icon Type Description

Key The field must be linked to an import data column in which the value in every row isunique. You cannot set key fields to Ignore.

Required You need to link this field with a column, in order for it to work properly. Although you

can create a template that ignores a required field, an error will be logged and somefeatures may not work correctly. For example, if you ignore the Beamwidthfield and donot enter a sensible default, cells will be shown on the map as narrow lines rather thanwedges.

Optional The field can be ignored safely.


13/24

GSM

UMTS TDD (UTDD)

WCDMA

For other technologies, see Required CellRefs Fields.

Adding new fields. Sometimes you may find that your network data contains items that are not defined as

fields in the configuration file. When this happens you can define new fields. See Adding New Fields to theCellRefs Filefor more information. However, note that this can adversely affect performance. See CellRefs

Limitsfor more information.

mport file specificationThe network data input file should be a tab-, space- or comma-separated file with one row of data per cell. Aheading row is optional. Latitude and longitude may be represented in any of the supported coordinatesystems.

The following table shows the minimum fields that are required for the various technologies.

Note there are some additional optional fields and others that are required for Veritune and some other Actix

solutions, see Required CellRefs Fields.

Some fields contain a list (also called an array) of values. Common examples are the Col or_Codesandoptional CDMA neighbor list fields. If you want to import values into these fields, they must be in a singlecolumn in the import file, with the individual values separated using a different character from that used forseparating the columns. Then you need to specify the separator being used on the first page of the importwizard. For example, if the main items are separated using the tab character, you could separate the neighborist values using commas.

ata validation

The network data is validated as it is imported. This helps to ensure that the software works correctly. Thevalidity checks include:

Validating the fields against their definition in the configuration file.

Validating the values against the data type (integer, string, etc.) specified in the configuration file.

Checking that values are within an appropriate rangefor example, the Mobile Network Code should

represent a real network. Valid values are defined in the format groupspecified for the field in theconfiguration file.

For information about the configuration file, see Structure of the CellRefs File.

If any errors occur, details are written to a log file called ImportErrors.login the Bin\CellRefsfolder within the

user data area. Typically this is:

C:\Documents and Settings\All Users\Application Data\Actix\Analyzer\Bin\Cellrefs\ImportErrors.log

To view the error log:

Open the file in Notepad.

Here is an example:

Act i x Anal yzer Cel l Ref s I mpor t ermpor t Fi l e: C: \ Test Dat a\ GSM\ Cel l r ef s\ Exampl eCel l Ref sI mpor t . t xt

Technology Columns

All Si t eI DLat i t udeLongi t udeSect or _I DAzi muth

Beamwi dt hGSM BCCH

CIBSI C

CDMA/EV-DO PN

UMTS SC

IS 136/IS 54 Col or_Codes

iDEN CCCHCol or_Codes


14/24

mport Templ at e: DemoTempl at eTi me of t empl at e Def i ni t i on: 27/ 06/ 1426 14: 09: 49

mpor t Er r or s.Li ne 2 : GSM_Cel l : Fi el d EI RP. Fai l ur e to conver t val ue "0 Not i n use" t o type an i nt eger .Li ne 3 : GSM_Cel l : Fi el d EI RP. Fai l ur e to conver t val ue "0 Not i n use" t o type an i nt eger .Li ne 4 : GSM_Cel l : Fi el d EI RP. Fai l ur e to conver t val ue "0 Not i n use" t o type an i nt eger .Li ne 5 : GSM_Cel l : Fi el d EI RP. Fai l ur e to conver t val ue "0 Not i n use" t o type an i nt eger .Li ne 6 : GSM_Cel l : Fi el d EI RP. Fai l ur e to conver t val ue "0 Not i n use" t o type an i nt eger .Li ne 7 : GSM_Cel l : Fi el d EI RP. Fai l ur e to conver t val ue "0 Not i n use" t o type an i nt eger .

elated Topics

PreferencesStructure of the CellRefs File

Required CellRefs FieldsAdding New Fields to the CellRefs FileCellRefs HistoryCellRefs Limits


CellRefs Fields: CDMACellRefs Fields: EVDOCellRefs Fields: GSMCellRefs Fields: UMTS TDD (UTDD)




15/24

ellRefs Fields: CDMA

In Analyzer, network configuration information is stored in a text file called the CellRefs file. This topicprovides information about the standard fields that are used in the CellRefs file for CDMA. The structure of theCellRefs file is defined in the CellRefs configuration file (DefNetworkData.ini). This topic provides informationabout all of the CDMA fields that are defined in the default configuration file, plus an additional field that canoptionally be added for use by Spotlight. This field is marked with an asterisk (*) and needs to be manually

added as described in Adding New Fields to the CellRefs File.

See CellRefs Preferencesfor an introduction to the CellRefs file and information about setting it and importingdata into it.

DMA site fields

DMA sector fields

Field Required? Description

SiteID Always The ID of the site (base station).

Site_Name No A text description, which can optionally be displayed on the map.

Latitude Always The site's latitude expressed as a decimal number representing the degrees in theWGS 84 projection system.

Longitude Always The site's longitude expressed as a decimal number representing the degrees inthe WGS 84 projection system.


CDMA_SiteIDForCell Always The ID of the site to which the sector belongs.

Sector_ID Always The ID of the cell or sector within the site.

Azimuth Always The sector's azimuth angle relative to true North, expressed in degrees.Used to orient the sector wedges on the map. If this field is missing ordoes not contain a sensible value, the sector will be shown pointing dueNorth on the map.

Beamwidth Always The sector's beam width angle expressed in degrees. Used to control the

size of the sector wedges on the map. If this field is missing or does notcontain a sensible value, the sectors will be shown on the map asnarrow lines rather than wedges.

EIRP No This optional field can be used to store the outward power of the sector

in dBm. If this is present, it is used by Veritune, which adjusts it whenyou enter a value in the Relative Power box. If this field is not present,

Veritune adjusts the measured power value instead.

PN Always The sector's pseudo noise code.

MCC No The mobile country code.

SID No The system identity code.

NID No The network identity code.

BID No The broadcast identity code.

PctPilot Veritune The percentage of power allocated to the pilot channel. Integer.

Required for Veritune.

PctTraffic Veritune The percentage of power allocated to the traffic channels. Integer.

Required for Veritune.

PctPaging Veritune The percentage of power allocated to the paging channel. Integer.Required for Veritune.

PctSync Veritune The percentage of power allocated to synchronization of channels.

Integer. Required for Veritune.

SRCH_WIN_A CDMAToolkit

The size of the search window in the active pilot set. Integer. Requiredfor Search Window Optimization in CDMA Toolkit.

SRCH_WIN_N CDMA

Toolkit

The size of the search window in the neighbor pilot set. Integer.

Required for Search Window Optimization in CDMA Toolkit.CDMANeighborList Neighbor

List Analysis

This is an array field that is required by the CDMA missing neighbor

analysis to store the PN codes of the neighbors. Although this field mustbe present, it does not need to store data, because the analysis willautomatically suggest neighbors. If this field does store data, theanalysis will suggest cells for removal when they do not meet thedefined criteria.

Face_Display No An integer value.


16/24


CellRefs Fields: EVDOCellRefs Fields: GSMCellRefs Fields: UMTS TDD (UTDD)


elated Topics

CellRefs PreferencesStructure of the CellRefs FileRequired CellRefs FieldsAdding New Fields to the CellRefs FileLines to CellsCellRefs Limits


Azimuth_Display No A value in degrees.

Phase_Display No An integer value.

LayerType No This field can be used to enter a text to group sectors on some user-

defined criteria. Typical examples are purpose (microcell, macrocell,underlay, overlay) and status (Planned, Built, Integrated). When data is

displayed on the map, sectors are placed in separate layers according tothe value in this field. This means that you can use the Layer Control

dialog to hide sectors that have a particular status, for example.

Height Veritune Height in meters of the antenna above ground level. Required for

Veritune. Optional for Spotlight.

Tilt Veritune The mechanical tilt of the antenna measured in degrees. This is positivefor downtilt and negative for uptilt. Required for Veritune.

Antenna_key Veritune A unique identifier for the antenna mask in use on the site. The antenna

mask identifies a specific electrical downtilt configuration for a particularantenna type. This key must correspond to a key in the antenna pattern

database. Required for Veritune. Optional for Spotlight.

CDMA_Freq No This optional field indicates the frequency in MHz in multi-frequencynetwork configurations where PN varies with frequency. If this field isabsent, all frequencies are assumed. Integer. Used by Veritune.

Channel No The channel number of the RF carrier frequency. Integer.

Max_ServerDist* No This can be used to specify a threshold that indicates the maximum

distance in meters that the sector should serve. Spotlight considerssamples beyond this distance to be overshooting. If this is not present inthe CellRefs file, Spotlight uses the general SL_Overspill_Dist_Thresholduser-defined thresholdinstead.

*Indicates that this field must be added to the configuration file manually as described in Adding New Fields

to the CellRefs File.


17/24

ellRefs Fields: EVDO

In Analyzer, network configuration information is stored in a text file called the CellRefs file. This topicprovides information about the standard fields that are used in the CellRefs file for EVDO. The structure of theCellRefs file is defined in the CellRefs configuration file (DefNetworkData.ini). This topic provides informationabout all of the CDMA fields that are defined in the default configuration file, plus an additional field that canoptionally be added for use by Spotlight. This field is marked with an asterisk (*) and needs to be manually

added as described in Adding New Fields to the CellRefs File.


VDO site fields

VDO sector fields







CDMA1xEVDO_SiteIDForCell Always The ID of the site to which the sector belongs.


Azimuth Always The sector's azimuth angle relative to true North, expressed indegrees. Used to orient the sector wedges on the map. If thisfield is missing or does not contain a sensible value, the sectorwill be shown pointing due North on the map.

Beamwidth Always The sector's beam width angle expressed in degrees. Used to

control the size of the sector wedges on the map. If this field ismissing or does not contain a sensible value, the sector will beshown on the map as a narrow line rather than a wedge.

EIRP No This optional field can be used to store the outward power of the

sector in dBm. If this is present, it is used by Veritune, whichadjusts it when you enter a value in the Relative Power box. If

this field is not present, Veritune adjusts the measured powervalue instead.

PN Always The sector's pseudo noise code.


SID No The system identity code.

NID No The network identity code.

BID No The broadcast identity code.

SRCH_WIN_A CDMAToolkit

The size of the search window in the active pilot set. Integer.Required for Search Window Optimization in CDMA Toolkit.

SRCH_WIN_N CDMAToolkit

The size of the search window in the neighbor pilot set. Integer.Required for Search Window Optimization in CDMA Toolkit.

CDMANeighborList NeighborList Analysis

This is an array field that is required by the CDMA missingneighbor analysis to store the PN codes of the neighbors.Although this field must be present, it does not need to storedata, because the analysis will automatically suggest neighbors.

If this field does store data, the analysis will suggest cells forremoval when they do not meet the defined criteria.



Phase_Display No An integer value.

SubnetMask No The subnet identifier that corresponds to the sector. Integer.

Color_Code No The color code that corresponds to the sector. Integer.

LayerType No This field can be used to enter a text to group sectors on someuser-defined criteria. Typical examples are purpose (microcell,


18/24


CellRefs Fields: CDMACellRefs Fields: GSMCellRefs Fields: UMTS TDD (UTDD)CellRefs Fields: WCDMA

elated Topics

CellRefs PreferencesStructure of the CellRefs FileRequired CellRefs FieldsAdding New Fields to the CellRefs FileLines to Cells

CellRefs Limits


macrocell, underlay, overlay) and status (Planned, Built,Integrated). When data is displayed on the map, sectors areplaced in separate layers according to the value in this field. This

means that you can use the Layer Control dialog to hide sectorsthat have a particular status, for example.

Height Veritune Height in meters of the antenna above ground level. Required forVeritune. Optional for Spotlight.

Tilt Veritune The mechanical tilt of the antenna measured in degrees. This ispositive for downtilt and negative for uptilt. Required forVeritune.

Antenna_key Veritune A unique identifier for the antenna mask in use on the site. The

antenna mask identifies a specific electrical downtilt configurationfor a particular antenna type. This key must correspond to a key

in the antenna pattern database. Required for Veritune. Optionalfor Spotlight.

CDMA_Freq No Indicates the frequency in MHz in multi-frequency networkconfigurations where PN varies with frequency. If this field is

absent, all frequencies are assumed. Integer. Used by Veritune.

Channel No The channel number of the RF carrier frequency. Integer.

Max_ServerDist* No This can be used to specify a threshold that indicates the

maximum distance in meters that the sector should serve.

Spotlight considers samples beyond this distance to be

overshooting. If this is not present in the CellRefs file, Spotlightuses the general SL_Overspill_Dist_Thresholduser-definedthresholdinstead.

*Indicates that this field must be added to the configuration file manually as described in Adding New Fieldsto the CellRefs File.


19/24

ellRefs Fields: GSM

In Analyzer, network configuration information is stored in a text file called the CellRefs file. This topicprovides information about the standard fields that are used in the CellRefs file for GSM. The structure of theCellRefs file is defined in the CellRefs configuration file (DefNetworkData.ini). This topic provides informationabout all of the CDMA fields that are defined in the default configuration file, plus some additional fields thatcan optionally be added for use by Spotlight and the GSM Cellplan Viewe. These fields are marked with an

asterisk (*) and need to be manually added as described in Adding New Fields to the CellRefs File.


The default CellRefs configuration can handle four levels of network infrastructure:MSC. This corresponds to the Mobile services Switching Center. It is an optional level. However, it becomesmandatory if the BSCID field is filled in at the sector level.

BSC. This corresponds to the Base Station Controller. It is an optional level. However, it becomesmandatory if the BSCID field is filled in at the sector level.

Site. This is mandatory and describes the ID and location of the site.

Sector. This is also mandatory and describes sector-specific data such as Azimuth, Beamwidth, BCCH, CI,and BSIC. If the optional BSCID field is filled in, there must be a corresponding BSC row describing the BSCID and MSC ID.

The main advantage of including the BSC and MSC definitions is that they can be used in the map legend,

allowing cells to be color-coded according to their BSC.

SM MSC fields

SM BSC fields

SM site fields

SM sector fields


ID Only if the BSCIDfield is filled in at the sector level. The ID of the MSC.

MSCName No A text description.


ID Only if the BSCIDfield is filled in at the sector level. The ID of the BSC.

MSCID Only if the BSCIDfield is filled in at the sector level. The ID of the MSC to which the BSC belongs.BSCName No A text description.


SiteID Yes The ID of the site (base station).


Latitude Yes The site's latitude expressed as a decimal number representing the degrees in theWGS 84 projection system.

Longitude Yes The site's longitude expressed as a decimal number representing the degrees in the

WGS 84 projection system.


GSM_SiteIDForCell Always The ID of the site to which the sector belongs.


Azimuth Always The sector's azimuth angle relative to true North, expressed indegrees. Used to orient the sector wedges on the map. If this field ismissing or does not contain a sensible value, the sector will be shownpointing due North on the map.

BeamwidthAlways The sector's beam width angle expressed in degrees. Used to controlthe size of the sector wedges on the map. If this field is missing or

does not contain a sensible value, the sector will be shown on the mapas a narrow line rather than a wedge.

EIRP No This optional field can be used to store the outward power of the sectorin dBm. This is used as follows: Verituneadjusts the value in this field (if it is present) when you

enter a value in the Relative Power box. If this field is not present,


20/24

Veritune adjusts the measured power value instead.

When this is present for a sector, Spotlightuses it instead of thegeneral SL_GSM_EIRP_Thresholduser-defined threshold.

BCCH Always The base station control channel. This field must be present for thelines to neighboring cells feature to work correctly on the map.

MCC Sometimes The mobile country code. This is an optional field. However, in somenetworks the CI is not sufficient to uniquely identify each cell. In these

circumstances, the MCC is required for the full cell global identity (CGI,which consists of the MCC, MNC, LAC, and CI) that is necessary for thecorrect identification of each cell.

MNC Sometimes The mobile network code. This is an optional field. However, if the CI is

not sufficient to uniquely identify each cell, the MNC is required (alongwith the MCC and LAC) for the full CGI.

LAC Sometimes The location area code. This is an optional field. However, if the CI isnot sufficient to uniquely identify each cell, the LAC is required (along

with the MCC and MNC) for the full CGI.

CI Always The cell identity code. This field must be present for the lines to servingcells feature to work correctly on the map.

BSIC Always The base station identity code. This field must be present for the lines

to neighboring cells feature to work correctly on the map.

BSCID No ID of the base station controller. If this is filled in, the BSC and MSClevelsbecome mandatory and a BSC row with the same ID must exist.

GSMNeighborList GSM 2GMissingNeighborsAnalysis

This is an array field that is required only by the 2G missing neighboranalysis to store the cell identity (CI) codes of the neighbors. Note thatthese must match CI codes of GSM sector elements within the CellRefsfile.

Although this field must be present, it does not need to store data,because the 2G missing neighbor analysis will automatically suggest

neighbors. If this field does store data, the analysis will suggest cellsfor removal when they do not meet the defined criteria.



Phase_Display No An integer value.RAC No The routing area code.

LayerType No This field can be used to enter a text to group sectors on some user-

defined criteria. Typical examples are bands (900 MHz, 1800 MHz,1900 MHz), purpose (microcell, macrocell, underlay, overlay) and

status (Planned, Built, Integrated). When data is displayed on the map,sectors are placed in separate layers according to the value in thisfield. This means that you can use the Layer Control dialog to hidesectors that have a particular status, for example.


Tilt Veritune The mechanical tilt of the antenna measured in degrees. This is positivefor downtilt and negative for uptilt. Required for Veritune.

Antenna_key Veritune A unique identifier for the antenna mask in use on the site. Theantenna mask identifies a specific electrical downtilt configuration for aparticular antenna type. This is required for Verituneand mustcorrespond to a key in the antenna pattern database. Optional forSpotlight.

TCHList Cell

Visualization

A list of traffic channels. This is required for the TCH Co/adjacent

Channel feature in Spotlight and the GSM Cell Plan Viewer.

NBorCI* Neighbor List

AnalysisA list of neighbor cell IDs. This is required for the Neighbor List Analysisin Spotlightand the GSM Cell Plan Viewer.

BTS_Sens* No This can be used to specify the BTS receiver sensitivity threshold forindividual sectors. If present, this is used in the SpotlightULDLpathloss difference calculation instead of the generalSL_GSM_BTS_Sens_Thresholduser-defined threshold.

Ant_Gain* No This can be used to specify the antenna gain threshold in dB for

individual sectors. If present, this is used in the SpotlightULDLpathloss difference calculation instead of the generalSL_GSM_Ant_Gain_Thresholduser-defined threshold.


21/24



CellRefs Fields: EVDOCellRefs Fields: UMTS TDD (UTDD)


elated Topics

CellRefs Preferences

Structure of the CellRefs FileRequired CellRefs FieldsAdding New Fields to the CellRefs FileLines to CellsCellRefs Limits



distance in meters that the sector should serve. Spotlight considerssamples beyond that distance as overshooting. If present, this is not

present in the CellRefs file, Spotlight uses the generalSL_Overspill_Dist_Thresholduser-defined threshold.

adjacentChannel No This field is required by the GSM Cell Plan Viewer in versions ofAnalyzer earlier than Spotlight. It is a special internal field that must bepresent as the last field for the GSM cell network element in the .iniconfiguration file. However, the cellrefs file does not need to store data

for this field, because it is populated by the GSM Cell Plan Viewer. Thisfield is not required from the introduction of Spotlight onwards.



22/24

ellRefs Fields: UMTS TDD (UTDD)

In Analyzer, network configuration information is stored in a text file is called the CellRefs file. This topicprovides information about the standard fields that are used in the CellRefs file for UMTS TDD (sometimesreferred to as UTDD). The structure of the CellRefs file is defined in the CellRefs configuration file(DefNetworkData.ini). This topic provides information about all of the CDMA fields that are defined in thedefault configuration file.


UMTS-TDD is a mobile data network standard built upon the UMTS 3G cellular mobile phone standard, using

a TD-CDMA air interface and Time Division Duplexing to duplex spectrum between the up-link and down-link. While a full mobile UMTS implementation, it is mainly used to provide Internet access in circumstancessimilar to those where WiMAX might be used. UMTS-TDD is not directly compatible with UMTS: a devicedesigned to use one standard cannot, unless specifically designed to, work on the other, because of thedifference in air interface technologies and frequencies used.

TDD site fields

TDD sector fields


CellRefs Fields: CDMACellRefs Fields: EVDOCellRefs Fields: GSM


elated Topics

CellRefs PreferencesStructure of the CellRefs File

Required CellRefs FieldsAdding New Fields to the CellRefs FileLines to CellsCellRefs Limits





Latitude Always The site's latitude expressed as a decimal number representing the degrees in the

WGS 84 projection system.Longitude Always The site's longitude expressed as a decimal number representing the degrees in

the WGS 84 projection system.


UTDD_SiteIDForCell Always The ID of the site to which the sector belongs.


Azimuth Always The sector's azimuth angle relative to true North, expressed in degrees.Used to orient the sector wedges on the map. If this field is missing or

does not contain a sensible value, the sector will be shown pointing dueNorth on the map.

Beamwidth Always The sector's beam width angle expressed in degrees. Used to control the

size of the sector wedges on the map. If this field is missing or does notcontain a sensible value, the sector will be shown on the map as a narrowline rather than a wedge.

EIRP No This optional field can be used to store the outward power of the sector in

dBm.

Toffset Always The time offset for the sector.


MNC No The mobile network code.

LAC No The location area code.

UTDD_CI No The UMTS TDD cell identity code.

UARFCN Always The UTRA absolute radio frequency channel number.


23/24

ellRefs Fields: WCDMA

In Analyzer, network configuration information is stored in a text file called the CellRefs file. This topicprovides information about the standard fields that are used in the CellRefs file for WCDMA (UMTS). Thestructure of the CellRefs file is defined in the CellRefs configuration file (DefNetworkData.ini). This topicprovides information about all of the CDMA fields that are defined in the default configuration file, plus someadditional fields that can optionally be added for use by Spotlight. These fields are marked with an asterisk (*)

and need to be manually added as described in Adding New Fields to the CellRefs File.


CDMA site fields

CDMA sector fields






Vendor No The name of the software vendor.

RNC No The name of the RNC.

Software No The version of the software.


WCDMA_SiteIDForCell Always The ID of the site to which the sector belongs.


Azimuth Always The sector's azimuth angle relative to true North, expressed indegrees. Used to orient the sector wedges on the map. If this field is

missing or does not contain a sensible value, the sector will be shownpointing due North on the map.

Beamwidth Always The sector's beam width angle expressed in degrees. Used to controlthe size of the sector wedges on the map. If this field is missing ordoes not contain a sensible value, the sector will be shown on the mapas a narrow line rather than a wedge.

EIRP No This optional field can be used to store the outward power of thesector in dBm. This is used as follows: Verituneadjusts the value in this field (if it is present) when you

enter a value in the Relative Power box. If this field is not present,Veritune adjusts the measured power value instead.

When this is present for a sector, Spotlightuses it instead of the

general SL_EIRP_Thresholduser-defined threshold.

SC Always The sector's scrambling code.MCC No The mobile country code.

MNC No The mobile network code.

LAC No The location area code.

WCDMA_CI No The WCDMA cell identity code.

WCDMANeighborList Neighbor

List Analysis

This is an array field that is required by the 3G missing neighbor

analysis to store the scrambling (SC) codes of the 3G neighbors.Although this field must be present, it does not need to store data,because the 3G missing neighbor analysis will automatically suggestneighbors. If this field does store data, the analysis will suggest cellsfor removal when they do not meet the defined criteria.

GSM_BSIC No The GSM base station identity code.

LayerType No This field can be used to enter a text to group sectors on some user-defined criteria. Typical examples are whether HSDPA is enabled,purpose (microcell, macrocell, underlay, overlay) and status (Planned,Built, Integrated). When data is displayed on the map, sectors are

placed in separate layers according to the value in this field. Thismeans that you can use the Layer Control dialog to hide sectors that


24/24



CellRefs Fields: EVDOCellRefs Fields: GSMCellRefs Fields: UMTS TDD (UTDD)

elated Topics

CellRefs PreferencesStructure of the CellRefs FileRequired CellRefs Fields

Adding New Fields to the CellRefs FileLines to CellsCellRefs Limits


have a particular status, for example.

GSMNeighborList 3G-2GNeighborList Analysis

This is an array field that is required only by the 3G-2G missingneighbor analysis to store the cell identity (CI) codes of the 2Gneighbors. Note that these must match CI codes of GSM sectorelements within the CellRefs file.

Although this field must be present, it does not need to store data,

because the 3G-2G missing neighbor analysis will automaticallysuggest neighbors. If this field does store data, the analysis willsuggest cells for removal when they do not meet the defined criteria.

UARFCN Always The UTRA absolute radio frequency channel number.


Tilt Veritune The mechanical tilt of the antenna measured in degrees. This ispositive for downtilt and negative for uptilt. Required for Veritune.

Antenna_key Veritune A unique identifier for the antenna mask in use on the site. Theantenna mask identifies a specific electrical downtilt configuration for aparticular antenna type. This key must correspond to a key in theantenna pattern database. Required for Veritune. Optional for

Spotlight.

PA_Power Veritune The maximum PA output power in dBm. Integer. Required forVeritune.

Pilot_Power Veritune The CPICH power in dBm. Integer. Required for Veritune.Sync_Power Veritune The combined P-SCH and S_SCH power in dBm. Integer. Required for

Veritune.

Other_Common_Powers Veritune The combined power for other common downlink channels in dBm.Integer. Required for Veritune.

LayerSize No An integer between 1 and 5 that indicates the size of the wedges onthe map relative to GSM sector wedges.

BTS_Sens* No This can be used to specify the BTS receiver sensitivity threshold for

individual sectors. If present, this is used in the SpotlightULDLpathloss difference calculation instead of the generalSL_BTS_Sens_Thresholduser-defined threshold.

Ant_Gain* No This can be used to specify the antenna gain threshold in dB forindividual sectors. If present, this is used in the SpotlightULDLpathloss difference calculation instead of the generalSL_Ant_Gain_Thresholduser-defined threshold.


distance in meters that the sector should serve. Spotlight considerssamples beyond this distance to be overshooting. If this is not presentin the CellRefs file, Spotlight uses the generalSL_Overspill_Dist_Thresholduser-defined thresholdinstead.


Actix Cellrefs

Documents

Transcript of Actix Cellrefs