Cellopt AFP 3.9 User Guide

AFP
User Guide
Version 3.9
www.actix.com
The content of this manual is provided for information only, is subject to change without notice, and should not be construed as a commitment by Actix. Actix assumes no responsibility or liability for any errors or inaccuracies that appear in this documentation. Copyright Actix 2008. All rights reserved. All trademarks are hereby acknowledged.
www.actix.com
Contents
1 WELCOME TO CELLOPT AFP ...........................................................................6
1.1 INTRODUCTION ................................................................................................ 6 1.2 MODELING...................................................................................................... 6 1.3 OPTIMIZATION ................................................................................................. 6 1.4 ANALYSIS ....................................................................................................... 6
2 GETTING STARTED WITH CELLOPT AFP ..............................................................7

2.1 INTRODUCTION ................................................................................................ 7 2.2 USER INTERFACE OVERVIEW ................................................................................. 7 2.3 APPEARANCE AND NAVIGATION .............................................................................. 8 2.4 MODELING AND OPTIMIZATION FLOW ...................................................................... 9 2.5 CONTROL PANEL ............................................................................................. 10
3 FILE MODE .............................................................................................. 12

3.1 INTRODUCTION .............................................................................................. 12 3.2 START ......................................................................................................... 12 3.3 NEW PROJECT................................................................................................ 13 3.4 OPEN PROJECT ............................................................................................... 17 3.5 IMPORT PROJECT ............................................................................................ 19 3.6 EXPORT PROJECT ............................................................................................ 20
4 IMPORT DATA .......................................................................................... 21

4.1 INTRODUCTION .............................................................................................. 21 4.2 THE IMPORT DATA TAB ..................................................................................... 21 4.2.1 The Radio Editor tab ............................................................................. 22
5 MODELING .............................................................................................. 23
5.1 INTRODUCTION .............................................................................................. 23 5.2 OVERVIEW .................................................................................................... 23 5.2.1 Detailed Project Overview ..................................................................... 24 5.2.2 Warnings............................................................................................. 26 5.3 SPECTRUM .................................................................................................... 27 5.3.1 Spectrum GSM .................................................................................. 27 5.3.2 Frequency Hopping Strategy GSM ........................................................ 28 5.3.3 MAL Editor ........................................................................................... 29 5.3.4 MAL length .......................................................................................... 30 5.3.5 Spectrum TDMA & PDC ....................................................................... 32 5.3.6 Strategy TDMA & PDC ........................................................................ 33 5.3.7 Template ............................................................................................. 34 5.3.8 Spectrum iDEN .................................................................................. 35 5.3.9 Strategy iDEN ................................................................................... 36 5.3.10 Optimize iDEN ................................................................................. 37 5.4 NETWORK..................................................................................................... 40 5.4.1 View and Edit Properties........................................................................ 40 5.4.2 Add Site .............................................................................................. 41 5.4.3 Add Sector .......................................................................................... 41 5.4.4 Add Radio............................................................................................ 43 5.4.5 Multiple Radio Adds .............................................................................. 43
www.actix.com
5.4.6 Disable Network Elements ..................................................................... 43 5.4.7 Edit Relations....................................................................................... 44 5.4.8 Alias Maps ........................................................................................... 44 5.5 LAYERS ....................................................................................................... 44 5.5.1 Modeling with the Radio Editor ............................................................... 46 5.5.2 System Categories GSM ..................................................................... 51 5.5.3 System Categories TDMA & PDC .......................................................... 52 5.5.4 System Categories iDEN ..................................................................... 53 5.6 LISTS.......................................................................................................... 53 5.6.1 Status ................................................................................................. 53 5.6.2 Manipulation ........................................................................................ 58 5.6.3 Analysis .............................................................................................. 65 5.7 PRIORITIES ................................................................................................... 67
6 FREQUENCIES .......................................................................................... 76
6.1 INTRODUCTION .............................................................................................. 76 6.2 OPTIONS...................................................................................................... 76 6.2.1 Spectrum Clearance ............................................................................. 77 6.2.2 Options - iDEN ..................................................................................... 77 6.3 ANALYZE ...................................................................................................... 77 6.3.1 Delta Report ........................................................................................ 82 6.4 OPTIMIZE ..................................................................................................... 83 6.5 RETUNE ....................................................................................................... 84
7 HSN AND MAIO....................................................................................... 88

7.1 INTRODUCTION .............................................................................................. 88 7.2 OPTIONS FOR HSN AND MAIO ........................................................................... 88 7.2.1 Lists ................................................................................................... 89 7.2.2 Synchronization ................................................................................... 89 7.2.3 HSN Options ........................................................................................ 90 7.2.4 MAIO Options ...................................................................................... 90 7.2.5 Filter................................................................................................... 90 7.3 ANALYZE ...................................................................................................... 90 7.4 OPTIMIZE ..................................................................................................... 92 7.5 RETUNE ....................................................................................................... 92
8 COLOR CODES ......................................................................................... 93

8.1 INTRODUCTION .............................................................................................. 93 8.2 COLOR CODE OPTIONS GSM ........................................................................... 94 8.2.1 Lists GSM ......................................................................................... 94 8.2.2 Rules GSM ........................................................................................ 94 8.2.3 Filter - GSM ......................................................................................... 95 8.2.4 Training Sequence Codes GSM ............................................................ 95 8.3 COLOR CODE OPTIONS TDMA & PDC ................................................................ 96 8.3.1 Lists TDMA & PDC .............................................................................. 96 8.3.2 Rules TDMA & PDC............................................................................. 97 8.3.3 Filter TDMA & PDC ............................................................................. 97 8.3.4 Color Code Grouping TDMA & PDC ....................................................... 97 8.4 COLOR CODE OPTIONS IDEN ........................................................................... 98 8.4.1 Lists iDEN ......................................................................................... 98 8.4.2 Options iDEN .................................................................................... 99 8.4.3 Filter - iDEN ......................................................................................... 99
www.actix.com
8.5 ANALYZE ...................................................................................................... 99 8.5.1 Color Code Analyze Properties GSM ................................................... 100 8.5.2 Color Code Analyze Properties TDMA & PDC ........................................ 100 8.5.3 Color Code Analyze Properties iDEN ................................................... 100 8.6 OPTIMIZE ................................................................................................... 101 8.7 RETUNE ..................................................................................................... 101
9 EXPORT PLAN ........................................................................................ 102

9.1 INTRODUCTION ............................................................................................ 102 9.2 EXPORT PLAN .............................................................................................. 102 9.2.1 Save Radio Editor ............................................................................... 104
10 INPUT AND OUTPUT FORMATS ................................................................... 105

10.1 INTRODUCTION........................................................................................... 105 10.2 CELLOPT AFP 3 FORMAT ............................................................................... 105 10.2.1 Input Data ....................................................................................... 105 10.2.2 Output Files ..................................................................................... 106 10.2.3 XML Tags......................................................................................... 106 10.3 PLANET 2.8 FORMAT .................................................................................... 117 10.4 ASSET FORMAT ......................................................................................... 118 10.5 PLAN EXPORT TO GSM OSS/BSC FORMATS ........................................................ 118 10.5.1 Nortel Supplementary Data ................................................................ 118 10.5.2 Ericsson Supplementary Data ............................................................. 119 10.5.3 Nokia Supplementary Data ................................................................ 119 10.6 ERICSSON INTERFERENCE LIST FORMAT.............................................................. 119 10.7 NOKIA INTERFERENCE LIST FORMAT .................................................................. 120 10.8 SECTOR ALIAS MAPS .................................................................................... 120
11 INSTALLATION/LICENSING AND TROUBLESHOOTING ......................................... 122

11.1 INTRODUCTION........................................................................................... 122 11.2 HARDWARE / SOFTWARE REQUIREMENTS ............................................................ 122 11.3 CELLOPT AFP INSTALLATION ........................................................................... 123 11.4 UNINSTALLING CELLOPT AFP .......................................................................... 127 11.5 CELLOPT AFP LICENSING ............................................................................... 128 11.5.1 Requesting a License ........................................................................ 128 11.5.2 Unlocking Cellopt AFP........................................................................ 129 11.5.3 License Manager Tool ........................................................................ 129 11.6 TROUBLESHOOTING ..................................................................................... 129 11.6.1 How to check if you have administrative privileges ............................... 129 11.7 SILENT INSTALL .......................................................................................... 130 11.8 CELLOPT PROJECT DATABASE .......................................................................... 130 11.9 OPTIMIZER PRIORITY.................................................................................... 130
12 INDEX ............................................................................................... 131
www.actix.com
Actix Cellopt AFP Version 3.9 User Guide
Welcome to Cellopt AFP 6
1 Welcome to Cellopt AFP

1.1 Introduction
Cellopt AFP is a powerful tool that automatically optimizes and analyzes the reuse of frequencies, color codes, frequency sets and frequency-hopping parameters. Cellopt AFP generates implementation-ready plans that do not need any further manual modifications. A guaranteed good frequency plan opens the way to better network performance, typically resulting in more satisfied subscribers, fewer dropped calls, fewer handover problems and less churn. There is a trade-off between capacity and quality: a decrease in quality allows the capacity to increase, and vice-versa. An automatic frequency-planning tool that can guarantee an improved plan would either maintain existing capacity while permitting better network quality, or would maintain quality while increasing capacity. The significant quality improvement typically made by Cellopt AFP allows for huge savings in network infrastructure investments. The potential improvement in operational performance is considerable, given the cost in time and money of skilled engineers. Any manual adjustment is wasted time, but weeks or even months could be lost to the networks in this way. At the network planning level, time saved through automated planning frees planners to work on higher value-added projects.
1.2 Modeling
Cellopt AFP includes a flexible modeler with many features to project system techniques and network-specific planning preferences. Cellopt AFP obeys a user-defined rule set to consider the desired planning preferences, or to reuse restrictions set by the operators planning strategy or other restrictions such as those applying to equipment reuse. Extensive support is provided for frequency hopping in GSM networks, as well as for planning with frequency sets in iDEN, PDC and TDMA networks.
1.3 Optimization
Cellopt AFP makes use of a proprietary iterative heuristic local-search optimization algorithm to look continually for improvements to the solution from the previous iteration, thereby guaranteeing to find high quality plans rapidly. Fast convergence is also important for performing consecutive optimizations for studies of what-if scenarios.
1.4 Analysis
Cellopt AFP has extensive support to allow the analysis of both input data as well as the optimized plans produced. Input data analysis is performed automatically in the background, and warnings are displayed if any data is missing or appears to be incorrect. Cellopt AFP provides a drill-down function to understand the data in the input lists as well as the quality of the optimized plans. This enables quick access to both summarized and detailed views of the information. Cellopt AFP also analyses the consequence of retuning any assignment, and supports making any of these retunes manually.
www.actix.com
Getting Started with Cellopt AFP 7
2 Getting Started with Cellopt AFP

2.1 Introduction
Cellopt AFP is a client-server application that uses a wizard style user interface to guide the user through the necessary steps in the modeling and optimization process. This section gives an overview of the user interface structure and how navigation is performed.
2.2 User Interface Overview

Generally, the user interface has two appearance modes:
File This mode is entered when starting the application.

In this mode, it is possible to create a new project or open an existing one. Furthermore, in this section, it is also possible to specify and load project input files and import and export projects in different formats. More details are provided in Section 3 of this User Guide.
Project This mode is entered when a project is selected and opened.

Here the network modeling is mostly performed as a first step, e.g., the available spectrum is specified and it is possible to view and undertake consistency checks on the project data. Grouping of radios with common characteristics using the category and layer concept as well as putting reuse constraints on defined groups can also be performed. Further prioritization of the optimization rules forming the desired trade-offs are also initiated here. More details are provided in Section 5 below. Moreover, the optimization process is executed and managed as a next step. Frequencies, color codes, HSN & MAIO (GSM only) resources can be optimized. It is also possible to view and analyze assignments as well as perform retunes of the resources to solve limited interference problems thereby avoiding major retunes. A number of sections are related to each of the above modes and they are described more fully later in this User Guide.
www.actix.com
2.3 Appearance and Navigation

Figure 2.1 shows the Network view of the Modeling section in Project mode. All sections available in Project mode are shown to the left in the form and the Modeling section is marked with a box to indicate the current position in the available sections. A red bullet is used to indicate that the Network view of the Modeling section is displayed. Further, the name of the project as well as project technology is shown in the upper left corner. Navigation is performed using the buttons in the bottom right of the page. The buttons are:
Back This will return to the previous section or view in the dialog sequence. It
may also return to File mode if the first section of the Project mode is currently viewed.
Next This will proceed to the next page or view in the dialog sequence. Control panel This provides a form with a variety of information and options.
Settings can be viewed and changed and help and support information can be accessed.
Hide button This will close a dialog window and show the current section or
view.
Close This can be used to close the current project or the application itself.
It is also possible to go directly to a specific section or view (in the Modeling section), by clicking its name in the section list to the left. Project name
Sections
Navigation
Figure 2.1 The Network view in the Modeling section for a GSM project. www.actix.com
2.4 Modeling and Optimization Flow

The user interface automatically guides the user through all the main steps of the modeling and optimization process using a predefined flow. Figure 2.2 shows the basic overview of the overall process by illustrating the order of sections and their associated views. Some sections may include several options and views not shown here, which are described elsewhere in this User Guide. The process starts in the File mode, where the user can create a new project, open an existing project or import/export a project. Upon completing the appropriate project selection, it will take the user to the Project mode, whereupon the user is taken through all modeling, optimization (Frequencies, HSN and MAIO and BSIC) and Export Plan sections in the order shown in Figure 2.2.
Figure 2.2 Overview of the File and Project modes with its modeling and optimization flow. The HSN and MAIO section is only available if GSM technology is chosen. BSIC is the GSM notation for color codes.
Note that some information can be displayed on the Radioplan WiNeS map. See Chapter 10 for details.
www.actix.com
2.5 Control Panel

At any time, it is possible to click the Control Panel button at the bottom of the application window to access the Control Panel (Figure 2.3), which reveals further information and options. These are: About This page displays copyright details on this product and detailed system information. Options In this page, it is possible to set the measurement system. It is also possible to activate the monitoring of user activities. When this feature is activated, a log file will be created. The file usage.txt is stored in the log folder in the installation directory on the users machine. The file includes name of project used, when it was opened and closed as well as the length of the session. Number of sites, sectors and radios in the project are recorded. From here, it is also possible to deactivate (or activate) all or some of the project warnings. There is also an option to show/hide projects created by other users, which may be useful if there are several users sharing a machine. Licensing This page displays details on the available license or licenses for this product. Logging This page contains the event log for this product. It shows all comments, warnings, errors, and messages that have been generated by the application while in use.
Figure 2.3 The Cellopt AFP Control Panel.
www.actix.com
Project Management This page contains project management options available to the user. It is possible to rename, import, copy, export and delete a project. Server / Database This section displays the server version and build number of the installed product. From here, it is possible to ping the server to check that it is active and responds. Furthermore, a status check of the Cellopt database can also be performed using the verify and if possible repair projects option. The status check may call a repair if any error is found in the database. Note that this operation may take several minutes until the process is completed depending on the size.
Support This section displays e-mail addresses, and websites from which product support can be obtained. Template Management This page contains template management options to view, import, rename, copy, export, delete and create a template from a project. A template is a repository of spectrum, project and optimization settings used in Cellopt AFP that are not network specific. For example, information about sites, sectors and radios as well as neighbors is not part of a template. The available spectrum is, however, part of a template. Priorities are also included in a template, and for this purpose, empty lists are included. The empty list may be filled with data by loading a list with the same name. Note that a template cannot be created from an open project.
Users Guide - This page allows you to open an online version of this User Guide.
www.actix.com
File mode 12
3 File mode
3.1 Introduction
This section provides a comprehensive overview of the File mode in the Cellopt AFP 3.9 client. As discussed earlier, the File mode handles the creation of projects and loading of input files. It is also possible from here to import projects from different formats as well as export to Cellopt AFP 3 format.
3.2 Start
The Start screen shown in Figure 3.1 appears after the Splash screen. Here you can select one of the following main options.
Figure 3.1 The Start page.
New Project This will create a new project. Open Existing Project This will open a project currently stored in Cellopt AFP database.
www.actix.com
File mode 13
Import Project from File This will import a project (from file in various file formats) to the Cellopt AFP database. Export Project to File This will export a project to file using the Cellopt AFP 3 file format. From the Start page, one can also select the Project Management link in the on-screen text to access other project options.
3.3 New Project

The New Project section will appear if the New project option is selected in the Start page. To create a new project, a project name and a template or project technology must be specified. See Figure 3.2.
Figure 3.2 The New Project page.
If a template is not specified, a project technology must be selected. A preview of the selected template will be shown in the bottom of the Select Template page. A template can be created in the Template Management page available through the Control Panel. Selecting Next opens the Import files section in the Project mode page, where you specify input data files that form the basis for the new project.
www.actix.com
File mode 14
The files are imported by means of a wizard, which consists of three steps, described below. 1 Select file type Here you specify the type of the file to be loaded (see Figure 3.3). Examples of file types are radio database, neighbor and interference lists. It is possible to do a quick import specifying the files (multiple) to import. Unlike the standard import, this does not give you the choice of merging with or replacing an existing list when you import a list.
Figure 3.3 The first step in the Import File Wizard.
www.actix.com
File mode 15
Select files to import Here the sources files of the desired file type are specified (see Figure 3.4).
Figure 3.4 The second step in the Import File Wizard.
Note that several files can be specified by using the Add button. It is also possible to remove a file by selecting the file and pressing Remove. For interference lists, it is possible to apply a filter function and remove relations where the co value is below or equal to the specified limit. Relations with 0 and negative co values are however always removed. A summary of the number of filtered relations are shown in the event log.
www.actix.com
File mode 16
View event log When the file or files have been loaded, a log is presented showing the status (see Figure 3.5).
Figure 3.5 The last step in the Import File Wizard, showing the import event log.
Import another will return to step 1 to load files of another type. Done will finish the file import and enter the Import files section in Project mode.
www.actix.com
File mode 17
3.4 Open Project

The Open Project section, shown in Figure 3.6, will appear if Open existing project is selected in the Start page.
Figure 3.6 The Open Project section.
A drop down list shows all of the projects currently stored in the project database. A list with the four most recently opened projects is shown on the right of the page. Any of these can be selected to open a project quickly. A preview of the selected project is also shown, which includes the following summary information: Name This is the name of the project. Template This is the project template used, if any. Technology This is the technology used in the project. Frequencies These are the frequencies included in the project.
www.actix.com
File mode 18
Color codes / NCC; BCC / Color codes; Offsets These are the available color codes included in the project. Technology-dependent notation is used. For GSM, this field is named NCC; BCC and lists available Network Color Codes (NCC) and Base Station Color Codes (semicolon separated). For iDEN, this field is named Color codes; Offsets and lists available are color codes and color code offsets (semicolon separated). For TDMA and PDC, generic color codes are listed.
User-defined MAL Number of Mobile Allocation Lists defined by the user that are available in the project. (Only present for GSM.) Sites Number of sites in the project. Sectors Number of sectors in the project. Radios Number of radios in the project. Lists The available lists and input files in the project. Layers The user-defined categories and layers included in the project. Selecting Open will open the selected project and enter the Modeling section in the Project mode.
www.actix.com
File mode 19
3.5 Import Project

The Import Project section, shown in Figure 3.7, will appear if Import project is selected from the Start page. Here the name and format of the project to import into the project database as well as the source project file must be specified. If the box beside the project name is ticked, the specified project name will be used; otherwise, AFP will use the project name specified in the project file. Cellopt AFP 3 and Cellopt AFP 2 are currently supported. Note that a Cellopt AFP 2 project may have source files in other formats, such as Planet 2.8 or ASSET. Selecting Import will import the project and enter the Modeling section in the Project mode.
Figure 3.7 The Import Project section, where it is possible to import a project into the project database from Cellopt AFP 2 or 3 file format.
For an interference list, it is possible to apply a filter function and remove relations where the co value is below or equal to the specified limit. Relations with 0 and negative co values are however always removed. A summary of the number of filtered relations are shown in the event log.
www.actix.com
File mode 20
3.6 Export Project

The Export Project section, shown in Figure 3.8, will appear if Export Project is selected from the Start page. Here it is possible to export a project stored in the project database to Cellopt AFP 3 file format. The project to export is chosen from a drop down list. A summary of the project will be shown when a project has been selected. Selecting Export will export the selected project to file and return to the Start page again.
Figure 3.8 The Export Project section: export a project to file in Cellopt AFP 3 format.
www.actix.com
Import Data 21
4 Import Data
4.1 Introduction
This section provides an overview of the Import Data section when in Project mode. Here the external files forming the project are shown. It is also possible to import additional files from here.
4.2 The Import Data tab

This section is always entered when a new project is created and it shows an overview of the files imported into the current project. The overview includes file name, file size and source format. It is also possible to load additional files using the Import button and view the supported file formats. Figure 4.1 shows an example overview.
Figure 4.1 The Import Data section, where an overview of the loaded project files is shown. Furthermore, it is possible to import additional files from here.
Clicking on the Import button displays the Import File Wizard, described on page 13.
www.actix.com
Import Data 22
4.2.1 The Radio Editor tab

The Radio Editor is used for modeling purposes (for example by changing categories and layers, viewing assignments and other radio properties), and also for selecting radios to be optimized (that is, assigned spectrum resources). The Radio Editor tab is accessible from the top in all pages in Project mode. There are two tabs: one for the current page and one for the Radio Editor (see Figure 4.2). The Radio Editor shows one row for each radio in the project, with the columns representing different radio properties.
Figure 4.2 The Radio Editor tab.
More details about the contents of the Radio Editor can be found in the Modeling chapter, Layers section of this User Guide on page 46.
www.actix.com
Modeling 23
5 Modeling
5.1 Introduction
In the Modeling section, the project modeling is performed. There are several views in this section described below. Modeling includes e.g. setting available spectrum and to view and make consistency checks on the project data. Grouping of radios with common characteristics using the category and layer concept as well as put different requirements on defined groups can also be performed. Further, reuse priorities can be defined and weighted to form a desired trade-off order for the optimizer.
5.2 Overview
The Overview view shown in Figure 5.1 is the first page in the Modeling section, which provides an overview of the selected project. This view is always entered when an existing project is opened.
Figure 5.1 The Project Overview page. Potential errors in the project are indicated by a warning sign.
www.actix.com
Modeling 24
The project overview includes general information: Name This is the name of the project. The name can be changed by clicking the link. Technology This is the technology used in the project. The technology can be changed by clicking the link. Description This is field includes a short description of the project. The description can be changed by clicking the link. The project overview further includes the following properties: Based on template This is the project template used. Frequencies These are the available frequencies included in the project. Color codes / NCC; BCC / Color code; Offsets These are the available color codes included in the project. Technology dependent notation is used. For GSM, this field is named NCC; BCC and lists available Network Color Codes (NCC) and Base Station Color Codes (semicolon separated). For iDEN, this field is named Color codes; Offsets and list available color codes and color code offsets (semicolon separated). For TDMA and PDC, generic color codes are listed. User-defined MAL Number of user-defined Mobile Allocation Lists defined by the user available in the project. (Only present for GSM.) Sites Number of sites in the project. Sectors Number of sectors in the project. Radios Number of radios in the project. Lists The available lists and input files in the project. Layers The user-defined categories and layers included in the project.
5.2.1 Detailed Project Overview

Appearing in the text near the top of the page, this link launches a detailed project overview, which includes several headings: General This heading includes general data such as project name, template, technology, when the project was created and description. Spectrum This heading includes spectrum data such as available and assigned frequencies and color codes. Frequency hopping (GSM) and set strategy (iDEN, TDMA and PDC) is also listed here. More information about specific details can be found in the Spectrum section on page 27. Network This heading includes network data such as number of sites, sectors and radios. It also lists number of sites, sectors and radios that have been added (compared to the source radio database file). See page 40 for details. Categories and Layers This heading lists user-defined categories and layers as well as some system categories (see the Layers section on page 44 for specific details). Spectrum rules associated to layers may also be listed. Finally, number of radios assigned to each layer is also displayed.
www.actix.com
Modeling 25
Lists This heading shows the defined spectrum, co-located, neighbor, interference and other lists in the project. Status and origin for each list is also showed. More information about specific details can be found in the Lists section on page 53. Priorities This heading shows all defined priorities in the project. For each priority, class and weight are listed as well as if any scaling or threshold option is used. More information about specific details can be found in the Priorities section on page 67. Plans This heading lists the defined plans in the project. Files This heading lists the name, size and source format of imported project files. Warnings This heading lists the current available project warnings. See below for more details. At the top there are options to save and print the overview. Figure 5.2 shows an example of a detailed overview.
Figure 5.2 The detailed project overview page showing more information about the loaded project.
www.actix.com
Modeling 26
5.2.2 Warnings
A linked warning sign will appear to the right in the Overview section (see Figure 5.1) if some information or data is missing. Details of the warning will be shown by the link. Cellopt AFP will identify and present a warning if: No system technology is associated with the project There are no available frequencies There are no available color codes A list is empty A list does not fulfill its list criterion, see Lists section for more details A layer has no assigned radios, see Layers section for more details The network has no sites No sites have latitude/longitude information A site has no latitude/longitude information A sector has no radios No sectors have served traffic information A sector has no served traffic information A sector has more than one donor sector A sector has no control radio No radios have frequency assignments A radio has no frequency assigned A QUAD/WiDEN has more than four radios (iDEN specific), see Layers section for more details A QUAD/WiDEN has only one radio (iDEN specific), see Layers section for more details A combiner has too many radios, see Layers section for more details There is no spectrum list available (iDEN specific) There is no interference list available There is no neighbor list available A priority has a too large weight value.
www.actix.com
Modeling 27
5.3 Spectrum
This view is used for defining spectrum resources such as frequencies and color codes. A warning will appear if any resource is missing. In addition, some technology dependent planning strategy options may be set here.
5.3.1 Spectrum GSM

Figure 5.3 shows the Spectrum page for a GSM project.
Figure 5.3 The GSM Spectrum view with Frequency Hopping options.
This page allows available frequencies and Network Color Codes (NCC) to be specified. The Base Station Color Codes (BCC) are fixed 0-7. Further details about GSM color code options can be found in the section on color code optimization. It is possible to import available frequencies from an ASCII file. The format of the file is the same as used in the client dialog and it may use the same range tokens. In addition, the following Frequency Hopping options can also be specified: Strategy Global frequency hopping planning strategy is specified. MAL editor Mobile Allocation Lists (MAL) for synthesizer hopping radios can be created and edited manually. MAL length Options used by Cellopt AFP to determine the MAL length for synthesizer hopping radios are specified. For synthesizer frequency hopping radios, Cellopt AFP supports two operation modes: user-defined and customized MAL. Customized MAL is the default mode and means that Cellopt AFP generates the MAL to each radio automatically. User-defined MAL is used when
www.actix.com
Modeling 28
a number of predefined MAL are available and Cellopt AFP assigns radios MAL from the given set. The user-defined MAL mode is activated from the MAL editor where the MAL are created.
5.3.2 Frequency Hopping Strategy GSM

The Frequency Hopping Strategy option for GSM allows the user to select a global frequency hopping strategy to be used by default throughout the network. You can also change this on the Frequencies page, or select a specific hopping strategy using the Layers option in the Radio Editor.
Figure 5.4 The Frequency Hopping Strategy dialog in the GSM Spectrum view.
Figure 5.4 shows the dialog where you can select a frequency hopping strategy to include: No hopping All radios in the network will be nonhopping. Baseband All radios in the network will perform baseband frequency hopping. Synthesized, one MAL per sector All radios in the network will be synthesized frequency hopping with a unique MAL per sector. A question to set control radios to non-hopping will appear.
www.actix.com
Modeling 29
Synthesized, one MAL per site All radios in the network will be synthesized frequency hopping with a unique MAL per site shared by all sectors at the site. Sectors at sites must be synchronized to make use of this option. A question to set control radios to non-hopping will appear.
5.3.3 MAL Editor

The MAL editor option (shown in Figure 5.3) will launch the editor and, where applicable, allow mobile allocation lists to be defined and edited. Furthermore, the option to use userdefined MAL is set here as shown in Figure 5.5. Note that the MAL editor will only appear if the option to use user-defined MAL for the optimization is selected. The number of MAL to define is specified in the page. Adding and changing frequencies to a MAL is simply done by selecting, or clicking, the frequency. A fill (adds all frequencies to the MAL) and clear (remove all frequencies from the MAL) functions are available in the MAL header as well as a delete MAL option. In the header, the number of radios that are assigned the MAL is listed.
Figure 5.5 The MAL editor, where you can define and edit MAL as well as specify a user-defined MAL for optimization.
www.actix.com
Modeling 30
5.3.4 MAL length

The MAL length option accesses the options that the optimizer will use in order to determine the length of an individual MAL to be allocated to the group of radios sharing an MAL. The settings will be effective for both user-defined and customized MAL optimizations. The length will set a minimum requirement for user-defined MAL (i.e. a longer MAL may be used), but a strict requirement for customized MAL (i.e. only an MAL with the exact length will be used). The MAL options can be applied globally or per category and layer. Each layer can have it own settings and this is represented by one entry in the MAL length options table, see Figure 5.6. More details about layers are found in the Layers section below.
Figure 5.6 The table with global or layer specific MAL length options.
The MAL length settings are shown in Figure 5.7 and the options are: Min length The minimum length of the MAL to be generated, i.e., the smallest MAL to be generated. Multiple of The common denominator length of the MAL to be generated, e.g., specifying 4 will generate MAL with length 4, 8, 12 etc. This can be used to avoid interference between sectors at a site that are synchronized and still use different MAL per sector. Max length The maximum length of the MAL to be generated, i.e., the largest MAL to be generated. Max fractional load The maximum utilization of the MAL that is desired, measured in terms of relative number of radios per frequencies. For example, specifying 50% will make sure that there are always twice as many frequencies or more in the MAL as there are number of radios allocated to the MAL. Together with
www.actix.com
Modeling 31
Min length and the actual number of radios in the hopping group, this sets a minimum length of the MAL. The maximum value of the three properties is used as the minimum value in a sector. The value used for a particular radio would be the worst-case value from the global settings and the settings from the layer the radio is on. In detail, the maximum of the specified min lengths and common lengths will be used and the minimum of the max lengths and fractional loads.
Figure 5.7 The MAL length options used by the Cellopt AFP optimizer to determine the length of individual MAL.
www.actix.com
Modeling 32
5.3.5 Spectrum TDMA & PDC

Figure 5.8 below shows the Spectrum options for a TDMA project (PDC will have the same appearance). Frequencies and generic color codes may be specified here. It is possible to import available frequencies from an ASCII file. The format of the file is the same as used in the client dialog and it may use the same range tokens. Furthermore, some additional Set Planning options can be specified, namely: Strategy Here the Global set planning strategy is specified. Template Here the frequency sets are defined and edited.
Figure 5.8 The TDMA Spectrum view with Set planning options.
www.actix.com
Modeling 33
5.3.6 Strategy TDMA & PDC

The Strategy option for TDMA and PDC (shown in Figure 5.8 above) allows the user to select a global set planning strategy to be used throughout the network. It is however possible to change this locally in the Radio Editor. Figure 5.9 illustrates the available options for selecting the frequency set planning strategy. These include: Sets only Radios of a sector will be assigned frequencies from sets only. Sets are added until the demand is reached. One set and subsets Radios of a sector will be assigned frequencies from one set and subsets if required. Subsets are added until the demand is reached. One set and adhoc Radios of a sector will be assigned frequencies from one set and additional individual frequencies are added if required. Adhoc Radios of a sector will be assigned frequencies from individual frequencies only.
Figure 5.9 The Set Strategy options dialog in the TDMA Spectrum page.
There are also some additional options used to further specify planning preferences if any planning strategy using sets is selected: Random assignment of frequencies from sets This option is effective when sets only and one set and subsets are selected above. It will randomly select frequencies from a set or subset when the sector demand requires that part of a set or a subset is additionally assigned. If disabled, frequencies will be selected in order instead (from top to bottom in set template). Use primary control frequencies for additional sets/subsets This option is only effective when sets only and one set and subsets are selected above. It will allow control frequencies (the first frequency in a set) to be reused for traffic
www.actix.com
Modeling 34
radios as well when additional sets or subsets are assigned to meet the demand in sectors. When disabled, control frequencies will only be assigned to control radios (i.e., first radio in sectors). Use sets where all frequencies are available to a sector See the iDEN spectrum section on page 36 for information on this option. Note that Cellopt AFP always considers frequency sets to be fully utilized (i.e. all frequencies in a set are active and generating interference) in the set optimization. The actual frequency assignments to radios are performed after the optimization has finished.
5.3.7 Template
The Template option (shown in Figure 5.8) will launch the Set Template page, where the frequency sets can be viewed and edited (see Figure 5.10).
Figure 5.10 The Set Template page, where frequency sets can be viewed and edited.
The number of frequency sets and maximum number of frequencies per set are specified in the bottom-right of the page. There is also possible to specify the number of subsets in each set via the Subsets button. The subset numbering is shown in the left-most column in the table. In general, frequencies may be added or changed by clicking the table cells. Further, it is possible to mark a frequency as primary control frequency by ctrl-clicking (hold Ctrl key while clicking) or alternative control frequency by alt-clicking (hold Alt key while clicking) the selected frequency. The cell background color will change and a darker color is used for the primary control frequency than for the alternative control frequency. It is possible to have maximum one primary control frequency per set and it is always shown at the top of a set. The control frequencies are only effective when set planning is used. It is possible to assign the control frequencies to control radios only. To assign the control frequencies to other radios as well, the option use primary control frequencies for additional sets/subsets (see Strategy TDMA & PDC above) must be activated.
www.actix.com
Modeling 35
5.3.8 Spectrum iDEN

Figure 5.11 below shows the Spectrum page for an iDEN project.
Figure 5.11 The iDEN Spectrum page, where spectrum can be specified and set planning strategy along with frequency set optimization can be accessed.
Available frequencies and band map frequencies (to be used for control radios) are specified as well as color code offsets to be used. A control radio will only be assigned one of the available band map frequencies. Non-control radios may use any of the available frequencies. If no band map frequencies are specified, all available frequencies will be considered for control radios. In the band map frequency dialog, it is also possible to set maximum number of band map frequencies that may be used in a QUAD/WiDEN radio. Possible values are 0 to 4. Four means that up to four control frequencies may be assigned to a QUAD/WiDEN, i.e. 0-4 are allowed. Further, it is possible to import available and control frequencies from an ASCII file. The format of the file is the same as used in the client dialog and it may use the same range tokens. The color code offsets may be in the 0-5 range. The ordinary color codes are fixed 0-15. Furthermore, the following options can be specified: Strategy Here Global set planning strategy is specified. Template Here the frequency sets can be defined and edited. The set template is identical to the one used for TDMA and PDC, see previous section. Optimize - The set template can be generated automatically by Cellopt AFP. This task is managed here.
www.actix.com
Modeling 36
5.3.9 Strategy iDEN

The global set planning strategy option (accessed using the Strategy button in Figure 5.11) is identical to those used for TDMA and PDC, see previous section.
Figure 5.12 The Set Strategy options dialog in the iDEN Spectrum page.
There are, however, also some iDEN specific options here (see Figure 5.12): Use sets where all frequencies are available to a sector This option will only assign sets where all frequencies are available (i.e. not forbidden) to sectors. Thus, sets that have any frequencies forbidden to a sector will be disregarded. If this option is disabled, sets may be considered that have some frequencies forbidden to a sector. The result is that the forbidden frequencies are just not assigned, and an additional set may be assigned if needed. Plan QUAD adhoc Assigns individual frequencies (i.e. ad hoc) for QUAD/WiDEN radios. Note that a QUAD/WiDEN radio can be assign more than one control frequency if assign ad hoc frequencies by changing an option in the Control Panel (see the section on the Control Panel). QUAD/WiDEN radios are specified in the Layers section. Plan one QUAD with sets and then adhoc Assigns the first QUAD/WiDEN in each sector from sets. The additional QUAD/WiDEN radios in sector with more then one QUAD/WiDEN will be planned with individual frequencies, i.e. ad hoc. Plan QUAD with sets Assigns QUAD/WiDEN radios from sets or subsets.
www.actix.com
Modeling 37
5.3.10 Optimize iDEN

Optimize launches the page where the set template can be automatically generated by Cellopt AFP. A completely new set template will be created from this operation. The operation will create a set template for radios configured to be planned with sets. If there are radios configured to be planned with adhoc frequencies, or the global set strategy is one set and adhoc, the optimizer will try to maximize and balance the reuse of the set and adhoc radios (see the two columns in the progress table below). Note that in the latter case, the number of adhoc radios will depend on the set size. Figure 5.13 displays the set template optimization page:
Figure 5.13 The Frequency Set Optimization for iDEN.
Balance reuse means that the optimizer will try to find a template so that the set and adhoc reuse are as small and close to each other (balanced) as possible. This is the default optimization goal. To optimize only the set template with respect to the radios configured to be planned with sets, only enable the minimize set reuse option (see the modeling options below). The optimized set template will include frequency assignments that fit QUAD/WiDEN radios if any QUAD/WiDEN radio is defined in the project (see Layers section) or if specified by the user (see the options shown below). Cellopt will only consider sectors that are selected in the Radio Editor (a sector is selected if at least one of its radio is selected) for the optimization. In addition, the optimizer will consider frequencies forbidden per sector or in a layer. As previously mentioned, Cellopt will also consider the set strategy either set globally or on a per-radio basis, as well as the band map and QUAD/WiDEN planning options set in
www.actix.com
Modeling 38
Spectrum. Note that the produced set template will have the same set length (number of frequencies) in all sets. In the same view, it is possible to Start and Stop the set optimization as well as view the optimization progress in a table. The optimized sets can also be viewed in the Template editor. Note that the choice to use the optimized template is made in the template editor. The optimization progress table reports the following: Sets Number of sets currently being optimized (i.e., created). Sets reuse Number of set radios divided by the number of set frequencies (Freqs in set). Adhoc reuse Number of adhoc radios divided by the number of adhoc frequencies (Freqs for adhoc). Freqs in set Number of frequencies in the set template. Freqs for adhoc Number of frequencies available for adhoc radios. Elapsed Total elapsed time. Elapsed Difference of elapsed time compared to previous plan. Clock Current time. Index Count of solutions. At the top in the progress table, there are buttons to Save, Print and Clear the table as well as Start and Stop the set optimization. To display the available optimization options (as shown in Figure 5.14), click on the Modeling button: Number of sets The range of the number of sets, specified using a min and max value, used by Cellopt AFP in the search for the best solution. The optimized number of sets will be in this range. If only one value is specified (min or max), the solution will have this number of sets. Frequency separation in set The desired frequency separation within a set. This is specified using a min and max separation. Band map frequencies per set The desired number of control frequencies to be assigned to a set. Note that this is a strict requirement. Min availability per frequency The option will make it possible to only include frequencies that have availability (over sectors) larger than the specified percentage value. For example, 100 mean that the only frequencies that can be used in all sectors are considered in the optimization. Similarly, 0 means that all available frequencies may be used. In general, a high value may be too restricting on the set of the available frequencies to produce a usable template. There could be sectors that have no available set frequencies. Some experimentation may be required to find an optimum value for the network.
www.actix.com
Modeling 39
Figure 5.14 The Options for Set Template Optimization for iDEN.
Frequencies per set - Specify the exact number of frequencies per set that the optimizer should assign. Minimize set reuse only Check this box to minimize only the set reuse factor. This setting will not balance reuse between set and adhoc radios. Reuse ratio of sets to adhoc Specify the desired relative reuse ratio between sets and adhoc. A value 1 would try to give the same reuse for sets and adhoc radios. This setting is effective only if reuse balance is used. Number of Quads per set Specify the number of QUAD assignments that should be included in each set in the set template. Possible values are 0 (no), 1-2, or any. Any means that some sets will have QUAD, depending on the QUAD demand in the network. Specifying 0-2 are strict requirements. Quad length Specify the length of the QUAD assignments in the set template. Two to four frequencies per QUAD assignment may be selected. Quad start position in set Specify the position of the QUAD assignment (up to four adjacent frequencies). The first frequency of a set will always be a control frequency.
www.actix.com
Modeling 40
5.4 Network
In the Network view shown below in Figure 5.15, you can view properties of the network elements (i.e. sites, sectors and radios) in a tree view. It is further possible to add, edit and disable sites, sectors and radios. The properties of sites, sectors and radios may also be changed if desired. It is also possible to edit interference, neighbor and other lists. In detail, sector relations can be added and removed in the available lists. Note that plan exports may not be imported properly with some planning tools when new sites, sectors and radios have been added to the network.
Figure 5.15 The Network page.
5.4.1 View and Edit Properties

The top right of the page (see Figure 5.15) summarizes the number of sites, sectors and radios present in the network. Cellopt AFP will also warn for a number of potential errors and present a clickable warning sign (one for each warning). Warnings are listed on page 26. In the network-tree, it is possible to expand sites to view their respective sectors. Similarly, radios of a given sector can also be displayed by expanding the associated sector. The properties of sites, sectors and radios are displayed in a properties window to the right if one element is selected in the network-tree. It is further possible to edit the properties by pressing the icon (present in the properties window) or right clicking the site, sector or radio name in the network-tree. If some important data is missing for any element, a small warning sign ( ) is shown beside the site, sector or radio icon. Further, a Search function is also available to find a specific site, sector or radio.
www.actix.com
Modeling 41
5.4.2 Add Site

A site can be added to the network by pressing the Add site button (see Figure 5.15). It is then possible to specify the site name as well as its latitude and longitude data in a dialog.
5.4.3 Add Sector

A new sector can be added to a site in the network by clicking the icon in the properties table (or by right clicking the site name in the network-tree) when a site is selected in the network-tree.
Figure 5.16 Add Sector Wizard step 4, specifies neighbors to the new sector.
www.actix.com
Modeling 42
A wizard is then launched: Sector name and properties Here the name and the properties of the new sector may be specified. Undesired & forbidden frequencies and forbidden color codes Here undesired and forbidden frequencies for the new sector may be specified. Forbidden color codes (BSIC for GSM) may also be specified if desired. See the section on Priorities for detailed information about spectrum rules. Neighbor relations Here the sectors that are expected to be neighbors to the new sector are specified, see Figure 5.16. It is possible to add the new neighbor relations to an existing neighbor list or create a new list (use Create button to create the new list). Neighbor relations are symmetric by default, i.e. handover is assumed to be performed both to and from the new sector and the selected neighbor. It is possible to make a relation a one-way handover relation by changing it to an asymmetric relation, i.e. handover is then assumed to be performed from the new sector to the specified neighbor only, by selecting the relations and clicking Symmetry.
Figure 5.17 The Add Sector Wizard step 5, specifying interference weights for each neighbor used in the interference relation calculation.
www.actix.com
Modeling 43
Interference relations Cellopt AFP derives estimated interference relations from the interference relations of the specified neighbors. The new sector is assumed to be receiving interference by the same sectors as its neighbors and, in the same way, is assumed to be interfering with the same sectors as its neighbors. Cellopt AFP further calculates the interference values (the priority if co- or adjacent frequencies are reused; see the section on Priorities for more information) for each relation. The user may set an importance weight for each neighbor in both interfered and interfering direction to make the interference relations of a certain neighbor to be more important than the others (see Figure 5.17). Equal weights for all neighbors will mean that the new sector will use an interference value for a relation that is the average of the neighbor interference values to/from the same sector. You can add the new relations to an existing interference list or create a new list (use Create button to create the new list). If a new list is created, the source interference list may be selected to the right in the dialog; that is, you may select to include relations from certain lists only (not shown in Figure 5.17). If the new relations are added to an existing list, the source relations are taken from the same list. Summary The last view in the add sector wizard will show a summary of the new sector and its relations. It is possible to return and change any selection. Note that lists generated from other lists, e.g. distance and 2nd order neighbor lists are not updated. See the section on Lists for detailed information about list manipulation.
5.4.4 Add Radio

A new radio can be added to a sector in the network by pressing the icon in the properties table (or by right clicking the sector name in the network-tree) when a sector is selected in the network-tree. It is then possible to specify the radio name as well as some layer settings. The user may specify it the radio is a control radio and copy layer settings from other radios of the same sector. See the section on Layers for detailed information. Note that Edit Radio ( ) should be used in order to change specific layer assignments of a radio.
5.4.5 Multiple Radio Adds

Multiple radios can be added to multiple sectors in one step, by pressing the icon. A mini wizard lets the user specify which sectors are to have new radios, and the number of radios to add to each sector. Note that it is not possible to add control radios using this wizard.
5.4.6 Disable Network Elements

It is possible to disable network elements (a site, sector or radio) by pressing the icon in the properties table (or by right clicking the network element name in the network-tree) when it is selected in the network-tree. A disabled network element will not be considered by Cellopt in the analysis and optimization. There is a button under the network tree to select whether disabled elements should be shown in network-tree. You can also disable multiple radios from the Radio Editor by using the assign selected radios to layer option. The Disabled category exists for this purpose. There is also an option to bulk-enable network elements from the warning dialog for disabled network elements presented in the Network section.
www.actix.com
Modeling 44
5.4.7 Edit Relations

It is possible to edit relations of sector or by right clicking the sector in the network-tree when it is selected in the network-tree. Spectrum, neighbor and other relations of a sector may be edited. It is also possible create in a new list under this menu. Spectrum relations Here the desired undesired and forbidden frequencies for the selected sector may be viewed and edited as well as forbidden color codes. Neighbor relations Here the defined neighbor relations for the selected sector may be viewed and edited per available neighbor list. It is possible change symmetry (i.e. if it is one or two way handover relation) of a neighbor relation by selecting the neighbor and pressing Symmetry button. Interference relations Here the defined interference relations for the selected sector may be viewed and edited per available interference list. It is possible to disable interference relations or enable a previously disabled one. The interference values, i.e. the Co and Adj interference values, may however not be changed. The three right columns list the sum of Co and Adj interference values if the selected sector and the interfering/interfered sector are reusing frequencies. This list can thus be used for identifying the potential worst interference relation. Other relations Here the defined other relations for the selected sector may be viewed and edited per available other list. This is similar to edit neighbor relations above. This option can be used to manage exception lists directly in Cellopt AFP. Create new list Here it is possible to create a new neighbor or other list and include new relations for the selected sector.
5.4.8 Alias Maps

You can specify alternative sector names (identities). The alias sector name is used to model the situation where different data sourcessuch as switch and performance measurement toolsmay use a different cell id. By specifying the sector aliases, there is no need to change the sector names in the data source files, and so you can load data directly into Cellopt. In the Network section, it is possible to define, view and edit the sector aliases. You can also create the alias map in a file, and import that file into Cellopt. More details about the alias loader can be found in the Input and Output format section, on page 120.
5.5 Layers
The category and layers concept is the flexible modeling means used in Cellopt AFP to group radios with similar characteristics. A category is owner of one or several layers. For example, a category could be called Radio Type with two defined layers: Control and Traffic. This category could be used to distinguish between the radios carrying control and traffic channels in the optimization prioritization process, i.e., different reuse restrictions can be set per layer. Note that a radio can only be assigned one layer of a category. The management of both category and layers are performed in the Layers section.
www.actix.com
Modeling 45
Further, assignments of layers as well as spectrum resources are shown in the Radio Editor shown in the top of each view in the Modeling section (see Figure 5.18).
Figure 5.18 The Layers section, for creating and managing categories and layers.
Options to Add category, Add layer, Edit, Rename and Delete a category or layer are available to the user here. A category is created by specifying a suitable name in the Add category dialog. When a category has been created, a created by selecting wizard will be started to add a layer to the category. Alternatively, a layer can be added by selecting a category (the layer owner) and pressing the Add layer button.
www.actix.com
Modeling 46
The Add layer dialog shown in Figure 5.19, requires the name of layer to be specified and provides additional options to specify undesired and forbidden frequencies, frequency sets (TDMA, PDC and IDEN only) and MAL (GSM only). Forbidden color codes are specified in TDMA and PDC. For GSM, forbidden BSIC (NCC/BCC pair) may be specified. Similarly for iDEN, it is possible to specify some forbidden color codes. Links to view and import available frequencies and color codes are present in the form. The Edit layer option takes the user to the same dialog.
Figure 5.19 The Add Layer dialog for GSM.
Frequencies defined as undesired will be associated a cost and penalized by the optimizer if assigned to any radio in the defined layer. It is possible to limit the available resource spectrum in the layer by defining the resource as forbidden. More details can be found in the Priorities section. Categories and layers are also used to model combiners in TDMA, PDC and iDEN. It is possible to specify maximum number of radios per combiner via the Combiners button in the bottom right of the page (not shown in Figure 5.18). This information is used for consistency checks performed by Cellopt AFP.
5.5.1 Modeling with the Radio Editor

The Radio Editor tab (see e.g. Figure 5.20) at the top of each Modeling page is used for modeling tasks, i.e. assigning radios to layers and changing radio properties as well as viewing assignments. Configured as a table, the Editor provides a row for each radio with columns describing the user-defined categories and additional system categories (i.e., predefined categories that are technology specific). The system categories are described in more detail in below.
www.actix.com
Modeling 47
There are also some further columns, which are independent of technology, including: Site Name of site. Sector Name of sector. Azimuth the direction in degrees of the centreline of the main sector beam pattern. Beamwidth the width in degrees of the main sector beam pattern. Tilt the vertical angle from the horizontal that the sectors antenna has been adjusted by.
Figure 5.20 The Radio Editor, where radios are assigned to layers and system categories can be changed.
Height Antenna type Latitude
www.actix.com
Modeling 48
Longitude Radio Radio number in the sector. Frequency Recently assigned (i.e., optimized) frequency. Color code Recently assigned (i.e., optimized) color code. This field is not presented for GSM. Old frequency Previously assigned frequency (defined in the input data). It is possible to edit this category from the Radio Editor. Old color code Previously assigned color code (defined in the input data). This field is not presented for GSM. Donor sector Name of donor sector if the sector is a repeating sector. Note that a repeating sector should have the same number of radios as the donor sector. Control radio Control radio indicator, i.e., if the radio carries control channels. Position Position of radio within sector (1st, 2nd etc.). #radio Number of radios in sector. Traffic Traffic served by sector. Area Serving area of sector.
Note that the frequency columns can include frequencies, MAL or set numbers depending on the chosen technology or planning strategy. If MAL or sets are used, the individual frequencies are listed as well. Furthermore, the color code columns use a technology-specific notation in some cases. For iDEN, the color code column includes a color code/color code offset pair. GSM projects have also a different appearance; see below. An additional category will appear if a Cellopt AFP 2 project using the fixed/free concept is imported: CellOptIIFree Indicates radios that were flagged as free to plan in Cellopt AFP 2. This can be used to select which radios Cellopt AFP 3 will work with. An autofilter in each column header can be used to select radios to apply changes in the table. Consecutive selections from different columns can be made. The first two options allow you to sort the column in ascending or descending order. Note that numbers will be sorted in an alphabetic rather than numeric order (i.e. 1, 10, 2 rather than 1, 2, 10).
www.actix.com
Modeling 49
Figure 5.21 The column autofilter.
You can filter by checking boxes for individual items, or use the Select All box to check each one, or use the Invert Selection option which switches whether each box is checked or unchecked. The Custom option displays this dialog (Figure 5.22):
Figure 5.22 The Custom column filter.
www.actix.com
Modeling 50
You can use the first drop-down menu to select an expression, then enter the value to be operated on. Alternatively, check the Use regular expressions box (Figure 5.23) and enter your own criteria (for example, using wildcards * and ?, and operators >, <, +, _ etc.). The Internet contains many definitions of regular expressions.
Figure 5.23 Using regular expressions in the column autofilter.
In the Radio Editor table toolbar, there are options to: Save the table to file in TAB delimited, html or PDF formats. It is possible to save the entire or only the selection of the report. Only a subset of the columns in the radio editor will be included when saving the table to a file in PDF format. All columns are however included when saving to html or TAB format. Store frequency plan saves the current assignments of frequencies, color codes and HSN & MAIO (GSM) as a plan with a selected name. This can be used to save a plan and compare it at a later stage. Export to Excel - opens the table as a file within Microsoft Excel, with the name radio_editor.xls (subsequent files are opened as radio_editor2.xls, etc.). Refresh the Radio Editor updates the Radio Editor display. Show or hide columns choose which columns to show or hide in the Radio Editor, as shown in Figure 5.24. Check or uncheck the possible columns, then click OK to apply. Select all radios selects all radios in the table. Extend selection to related radios - used to select additional radios relating to a first selection of radios (presented in the table). It is possible to select radios that are for example, interfering with, or neighbors to, the first selection. The result as well as the first selection is stored in a category Selection using a layer In selection. It is possible to make consecutive selections, and all selections will be stored in the category using the same layer. Select by file - Import a selection of radios specified in a text file including sites, sectors and possibly radios (TAB delimited) or frequency numbers. There should be one site, sector, radio/frequency per row in the file. Format: <site name><tab><sector name><tab><radio name/frequency number>. Also, the user then selects the category and layer (both user-defined and system categories may be chosen) to be assigned to the radios defined by the file.
www.actix.com
Modeling 51
Store selection as new category creates a new category and the selected radios are assigned to layer In selection. Assign selected radios to layer - this is the means used to assign selected radios to a certain layer. It includes a category and layer selector.
Figure 5.24 Selecting which Radio Editor columns to display.
5.5.2 System Categories GSM

Some additional columns will appear in the Radio Editor if GSM projects are used. The GSM system categories are: BSIC Recently assigned Base Station Identity Code (BSIC) including a NCC/BCC pair (defined in the input data). Old BSIC Previously assigned Base Station Identity Code (BSIC) including a NCC/BCC pair (defined in the input data). HSN Recently assigned (i.e., optimized) hopping sequence number. MAIO Recently assigned (i.e., optimized) mobile allocation index offset. Old HSN Previously assigned hopping sequence number (defined in the input data). Old MAIO Previously assigned mobile allocation index offset (defined in the input data). MAL length Length of MAL assigned to this radio. BSC type Base station controller and radio equipment supplier of this radio. Possible layers of this category are Ericsson, Nokia, Nortel or Unassigned. All radios of a sector should be assigned to the same layer, i.e. only one supplier per sector. This information is used for creating plan exports in vendor specific switch (OSS/BSC) formats. Supplementary data is required to complete the formats and this category is only present if this data is available in the project. More details about the supplementary data can be found in the section about Input and Output Formats below.
www.actix.com
Modeling 52
Hopping Strategy Frequency hopping strategy used for this radio. The following values are accepted: Default, Non hopping, Baseband hopping, Synth sector or Synth site. Default is used to derive the frequency hopping strategy for this radio from the global specification, set in the Spectrum section, as discussed in the section above. Non hopping should be used for non-hopping configurations. Baseband hopping should similarly be used for baseband hopping radios. For synthesizer hopping radios, two strategies are available: Synth sector and Synth site where the latter assumes site synchronization, i.e., sectors at a site are synchronized. It is possible to have several groups of baseband and synthesizer hopping radios per sector (or site). Radios of the same group should be assigned the same number of the selected hopping mode (e.g. Synth sector). Sync group Indicates the synthesizer hopping radio grouping identified by the HSN and MAIO sync group optimizer. Radios marked as Not allowed may not be synchronized. As mentioned, there is an option to specify the frequency hopping strategy on a global level in the Spectrum section. The Hopping Strategy system category can be used to specify the frequency hopping strategy at the radio level. This is useful when there is a mix of hopping strategy in a network and the default option cannot be used.
5.5.3 System Categories TDMA & PDC

For TDMA and PDC, additional system category columns appear in the Radio Editor: Combiner Indicates if a combiner is connected to this radio. The Default value is unassigned. A value of Combiner17 denotes that the radio is connected to combiner number 1 to 7. The maximum number of radios per combiner is specified in the Layers definition view. If set planning is used, you can use this category to split a sector into several groups, in order to assign more than one set to a sector. Then one set will be assigned to the group of radios assigned to the first combiner, a second set to the second combiner, and so on. Set Strategy Set planning strategy used for this radio, where Default, Sets only, One set and subsets, One set and adhoc or Ad hoc values can be entered. Default being the default setting is used to derive the set planning strategy for this radio from the global specification, set in the Spectrum section discussed in the previous section. Sets only is selected if assignment from sets is desired. In the same way, One set and subsets should be used to assign frequencies from sets and subsets if more than one set is required in a sector. One set and adhoc is used to assign individual frequencies to radios in a sector where the assigned set cannot fulfill the demand. Ad hoc should be selected for radios when assignment with individual frequencies only is desired (i.e. no sets). As mentioned, there is an option to specify set planning strategy on a global level in the Spectrum section. The Set Strategy system category can also be used to specify set
www.actix.com
Modeling 53
planning strategy at the radio level. This is useful when the default option cannot be used because there is a mix of set and ad-hoc planning in a network.
5.5.4 System Categories iDEN

The system categories for iDEN are identical to those of TDMA and PDC, with the exception of that the Set Strategy category is somewhat different and there is one iDEN specific one, namely: Set Strategy Set planning strategy used for this radio or if this radio is part of a QUAD or WiDEN radio. Default, Sets only, One set and subsets, One set and adhoc or Ad hoc values can be entered similar to TDMA. Additional possible values are QUAD-1st...8th that denote that a radio is connected to QUAD number 1 to 8. Similarly, WiDEN-1st8th can be used to identify WiDEN radios. There must be two to four radios connected to a QUAD/WiDEN. The planning strategy for QUAD/WiDEN radios is set in the Spectrum section (the default is adhoc). WiDEN radios are currently planned as QUAD radios, i.e. Cellopt assigns up to four adjacent frequencies to a WiDEN. MCRB-1st-8th can be used to identify radios that are grouped in an MCRB. Each MCRB group may contain from one to six radios, and the assigned frequencies must have a separation of (at most) 1.25 Mhz, equivalent to a 50-frequency difference. The radios within an MCRB are always planned as adhoc. MCRBs may contain a mixture of control and non-control radios, but the radios must have identical priorities. So if a layer is assigned to an MCRB radio and there is a priority that is specific to that layer, then the layer must be assigned to all radios in the MCRB. Intermod This category is used for grouping/marking radios in sectors that are to be assigned adjacent frequencies or tightly packed frequencies. Tightly packed assignments will minimize the impact of intermodulation products in the system. Radios should be marked as Adjacent if this is desired. Adjacent is not a strict requirement, there may be holes in the spectrum assigned to a sector due to e.g. forbidden frequencies. Note that Set Strategy will not be considered for adjacent radios, only QUAD/WiDEN.
5.6 Lists
In the Lists section, you can analyze, manage and view the status of the lists in the project. Cellopt AFP uses lists containing optimization rules in the optimization process to model the planning preferences. These views are available: Status The status of each list is shown. Manipulation Provides options to perform list manipulation actions. Analyze Provides options to view the actual list content.
5.6.1 Status
Figure 5.25 shows the status view of the lists loaded into the project. The view shows if any sector-to-sector relations defined in the lists violates a user-defined threshold. The loaded lists are grouped into these types: Spectrum lists Lists that include forbidden or undesired rules. A forbidden rule is used to limit the possible assignments of frequencies and / or color codes to a radio and it is a strict requirement. An undesired rule is a softer version of the forbidden rule, by which Cellopt AFP will penalize against making certain assignments of frequencies that are undesired.
www.actix.com
Modeling 54
Neighbor lists Lists that define neighbors to sectors. Used to impose requirements on sector neighbors to allow handover to work properly. Interference lists Lists that specify how much traffic or area would be affected if two sectors re-used co or adjacent frequencies. The interference lists are often generated by Cellopt MDA or an external planning tool. This is often referred to as an interference or permission matrix. Other lists Lists that are not part of the above categories, e.g., exception, 2nd order neighbor and distance lists. See also the section on List Manipulation below.
Figure 5.25 The List Status view, showing the status of the projects loaded lists.
The status is indicated using style and color-coding. Three status levels are defined: Red The list has no relations, i.e., it is empty. The list name is shown with bold style if reported with this status. Yellow The list violates the list status criteria in at least one sector. The list name is shown with italic style if reported with this status. Green The list is valid and correct, i.e., it fulfils the list status criteria in all sectors. The list name is shown with normal style if reported with this status. For Yellow lists, it is further possible to view the sectors violating the list status criteria by clicking the list name. Hovering the cursor over a list name displays a tool tip showing information about that list for example, if it was copied and from which list, and if it was normalized, the normalization factor that was used.
www.actix.com
Modeling 55
Right-clicking on a list name displays a pop-up menu of available functions. See section 5.6.2 Manipulation on page 58 for more information. Note that the Join Lists function is not avaialble from the menu. For Neighbor, Interference and Other lists, there are two addional options that do not appear in the Manipulation section: Change Type This allows you to select a new type for the selected list. For interference lists you can additionally specify whether the list is based on measured data. See Figure 5.26.
Figure 5.26 The Change List Type option
Properties This shows the lists origin (and, if the list was normalized, the normalization factor used). A button displays the lists Status (and, if a neighbor list, a button to Check Asymmetry). See Figure 5.28.
www.actix.com
Modeling 56
Selecting the Criteria button will launch a view where the list status criteria can be edited, as show in Figure 5.27.
Figure 5.27 The List Status Criteria dialog: edit and change the criteria per list type.
Criteria are set per list type and a category and layer filter can further be applied if desired. This means that the criteria are effective on radios defined by the category and layer only. Sectors with no radios can also be removed in the status reporting.
www.actix.com
Modeling 57
Selecting the Symmetry button (see Figure 5.28) will launch a view where the asymmetric handover relations can be viewed per neighbor list. A handover relation between a sector A and B is considered asymmetric if sector A is defined as a neighbor of sector B but not vice versa, i.e. sector B is not a neighbor of sector A. There is also an option to add (create) the missing relations, to make the neighbor relations symmetric.
Figure 5.28 Asymmetric Relations table.
www.actix.com
Modeling 58
5.6.2 Manipulation
List management can be performed in the Manipulation view (Figure 5.29 below). Copy, Join, Rename, Delete, Modify Spectrum List, Export and Normalize list functions can be performed on the lists. It is possible to export a list to file in Cellopt AFP 3 (XML) and 2 formats as well as HTML, TAB and Comma delimited formats. In addition, it is also possible to create new lists under List Generation: Create Distance List, Create Second Order Neighbor List and Create Site Neighbor List.
Figure 5.29 The Lists Manipulation view, where lists management can be performed. It is also possible to create new lists.
5.6.2.1
Copy List
The Copy List button is used to create a new list from an existing list.
www.actix.com
Modeling 59
5.6.2.2
Join Lists
The Join Lists button is used to combine lists. Select two or more lists and specify the Join type and the Statistics operation to be used for the join operation, as seen in Figure 5.30.
Figure 5.30 The Join Lists dialog.
The following operations are possible: No statistics This results in a list with no interference values. Sum This results in a list with the sum of the interference values from the source lists per relation. Max This results in a list with the maximum of the interference values from the source lists per relation. Average This results in a list with the average of the interference values from the source lists per relation. Product This results in a list with the product of the interference values from the source lists per relation. Preferred In the join, if the same relation exists in more than one list, the join will take the statistics from the top-most selected list in the Lists window (see Figure 5.30). You can use the arrow buttons to alter this order. Range This results in a list with the absolute (positive) difference of the interference values from the source lists per relation. A large value indicates a large difference between the selected lists.
www.actix.com
Modeling 60
Furthermore, the type of join must be selected. These join types are available: Union The resulting list contains relations that were in either or all source lists. Intersection The resulting list contains only relations that were in all source lists. Difference The resulting list has only those relations from the source list that are not in any other source list.
5.6.2.3
Modify Spectrum List
The Modify Spectrum List button is used to modify particular frequencies or ranges of frequencies that are forbidden or undesired, as seen in Figure 5.31 below. Use Choose spectrum list to specify whether you wish to remove frequencies from the Forbidden Frequencies list, the Undesired Frequencies list, or another specified spectrum list. You can then enter frequency numbers individually, separated by commas, or as inclusive ranges, specified by a hyphen. So for example, you might type: 1-5, 8, 10 to specify the frequencies 1 to 5, 8 and 10 to be removed from the selected spectrum list. You can also modify all sectors of the selected list, or the sectors as defined by a category and layer. A sector is selected if at least one of its radios is selected.
Figure 5.31 The Modify Spectrum List dialog, used to specify the removal of frequencies from the forbidden and undesired frequencies lists.
www.actix.com
Modeling 61
5.6.2.4
Export Lists
The Export List button is used to write a list to file. It is possible to export spectrum, neighbor and interference lists to file. The following export formats may be used: Cellopt 2, Cellopt 3, TAB and CSV (comma separated). Spectrum lists may only be exported in Cellopt 2 and TAB formats.
5.6.2.5
Normalize List
The Normalize List button is used to normalize interference lists (lists with co and adj values). You can normalize the original list (i.e. overwrite the co and adj values) or create a new list. Select both the list to be normalized as well as the normalize option. Three options can be used stand-alone or together (see Figure 5.32):
Figure 5.32 The Normalize List dialog, used where interference lists are normalized. Several normalize operations may be selected.
Per sector This option is used to normalize a list on a sector level so that the sum of sum of all co interfering relations for each sector is equal to 1 after the normalization. For each sector, each interfered relation is scaled with the sum of the co interference from all interfering sectors for the target sector. This option can be used to normalize list with handover counts so that low traffic sectors will have equal priority as high traffic sector with many counts. Based on other list The option normalizes the selected list based on another interference list to be selected. The result is that the normalized list will have the same average co interference as the selected list. Each relation is scaled by the
www.actix.com
Modeling 62
ratio average (co interference of another list)/average (co interference of list to be normalized). To max value This option normalizes the selected list so that it will have a new maximum co value (that is selected by the user). Each relation is scaled by the ratio value inserted/max (co interference of list to be normalized).
5.6.2.6
Create Distance List
This option will create a distance list and requires that the longitude and latitude coordinates of the sites are available.
Figure 5.33 The Distance List Wizard. Options to use as basis for the distance list are specified here.
Cellopt AFP will request the spatial coordinates of the sites if they are not present. It is possible to create a distance list even if all sites are not positioned (they are just not included). The distance list contains distance-based rules, for example, that sectors close to each other may be given a high priority if reusing frequencies or color codes while a lower priority is afforded for sectors with a large distance separation. Typically, the distances (of interest) are only to be calculated for sectors that reuse the same frequencies. Note that if this is the case, the distance list must be generated each time the frequency plan is changed. Figure 5.33 shows the Create Distance List dialog. The following options can be specified: Selection Select all sectors or define a category and layer filter. It is possible to base the distance list on sites defined by radios in a specific category and layer only.
www.actix.com
Modeling 63
Max distance The maximum distance that are given a priority value. Distances larger than this are not given any priority. It is possible to disable max distance to calculate the distance list independent of the sector-to-sector distance, i.e. for all sector-pairs. Separation The maximum frequency separation to consider in the distance list generation. It is possible to only consider sectors that are reusing frequencies in the distance list (Co is then selected). The current plan is considered. Selecting Adj-1 will consider both co- and first-order adjacent frequencies, and so on. You can disable separation to calculate the distance list independent of the frequency plan (thus between all sectors). Scale with number of radios within separation This option will scale the priority values if there are multiple radios having frequency reuse (within a separation) between two sectors. Separation must have been specified to be effective. For example, if this option is enabled, and if the Co priority between two sectors is 1000 and there are two radios within the desired separation, a Co priority of 2000 will be used. Co max The maximum priority that will be given to a relation in the list. Co function The function of the distance used to derive the co frequency or color code priority value. These functions are available: Absolute value is a step function where sectors closer than the maximum distance are given the maximum importance (others are given no priority). Linear drop-off implies that the priority function is an inverse linear function of the distance. Quadratic, Cubic and Quadruple drop-off are used to specify that the function is inversely proportional to the power of 2, 3 and 4 of the distance respectively.
Checking the and box allows a further co function to be defined, allowing you to use different functions for different range bands. The co value is calculated as follows: co0 is the co value and d0 is the distance at the start of the distance segment. The co0 value for a given segment is calculated from the formula for the previous segment.
co
d d0 co0 1 d max
dropoff
In the first segment, co0 = comax and d0 = 0. Adjacent function The function of the distance used to derive the adjacent frequency priority value. The same functions described above are available. Adjacent scaling The calculated adjacent priority is multiplied by this percentage value. The default values are 0% for iDEN and 100% for non-iDEN.
www.actix.com
Modeling 64
5.6.2.7
Create Second Order Neighbor List
This option will create a 2nd order neighbor list and requires that a neighbor list is loaded. A 2nd order neighbor list includes relations between sectors and the neighbors to the neighbors of the sectors (see Figure 5.34).
Neighbors Neighbors
Second order neighbors
Figure 5.34 An example of a second-order neighbor relation between two sectors.
If a 2nd order neighbor to a sector is also defined as handover neighbor, it is not included in the list. When the list is created, it is requested to specify the priority that should be associated to the list (see the Priorities section on page 67 for more details).
5.6.2.8
Create Site Neighbor List
This option will create a site neighbor list and requires that a neighbor list is loaded. A site neighbor list includes relations between sectors and all other sectors of the same sites as the neighbors of the sectors (see Figure 5.35). If a sector on the same site as the neighbor to a sector is also defined as handover neighbor, it is however excluded in the list. When the list is created, it is requested to specify the priority that should be associated to the list (see the Priorities section on page 67 for more details).
Site neighbors
Co sited
Neighbors
Figure 5.35 An example of a site neighbor relation between two sectors.
www.actix.com
Modeling 65
5.6.3 Analysis
The Analysis view allows the actual list content to be displayed as a report. The report can be shown in two ways: on the screen in a table. You then have the option of viewing a Detailed Report for one or more rows in the table. output to a tab-delimited text file. This can then be examined in detail in Microsoft Excel. Use this for very large reports which can be difficult to view on screen. You can create interactive summaries using a pivot function. The data from the lists are presented by means of subtotals defined by the pivot function. The subtotal columns presented in the table are selected by the pivot. You are still able to view the raw content of each file. Figure 5.36 shows the Analysis view with the pivot field selector. Note that you can select multiple fields by checking the and box next to each Field.
Figure 5.36 The Analysis Lists view with the pivot field selector.
The following properties can be used as a pivot: List Used to report per list. Site/SiteR Used to report per site (serving/interfering). Sector/SectorR Reports per sector (serving/interfering). Radio/RadioR Reports per radio (serving/interfering). System category/System categoryR Report per system category (serving/interfering). The system category is Hopping Strategy for GSM and Set Strategy for TDMA, iDEN or PDC (see Layers above). Control radio/Control radioR Report per control radio (serving/interfering). Donor sector/Donor sectorR Report per donor sector (serving/interfering).
www.actix.com
Modeling 66
Defined categories/Defined categoriesR Report per category defined by the user (serving/interfering). All defined ones are present. If you have a Cellopt MDA license, you can also use the Interference Analysis options: Analyze Interference List Click this link to open the MDA Interference List Analysis Summary page. See the Cellopt MDA User Guide: Interference List Analysis section for more information. Compare Interference List Click this link to open the MDA Interference List Comparison Summary page. See the Cellopt MDA User Guide: List Comparison section for more information. Analyze Neighbors Click this link to open the MDA Neighbor Analysis Status page. See the Cellopt MDA User Guide: Neighbor Analysis section for more information. Depending on the analysis selected, it may be several minutes until the process is completed if the files are large. The list analysis report will be presented in a table which includes four properties apart from the pivot fields. These include: Count This represents the number of relations in the selected pivot. Co Int This represents the sum of the co frequency interference values in the selected pivot. Adj Int This represents the sum of the adjacent frequency interference values in the selected pivot. An example is shown in Figure 5.37, where the List function has been used as pivot (that is, the subtotal per list is desired).
Figure 5.37 The List Analysis table, where the List entry has been used a pivot.
www.actix.com
Modeling 67
The number of relations, sum of interference and maximum separation is reported per list for each case. Selecting one or several rows in the summary table and then clicking on Detailed Report will show the raw data; that is, the actual list content for the selection. This will be presented in a new table view.
5.7 Priorities
The planning rules defined by the user are required by Cellopt AFP optimizer to consider desired planning preferences or reuse restrictions set by the operators planning strategy as well as other restrictions such as equipment limitations (for example, combiner spacing, and so on). A number of different rules can be defined in Cellopt AFP. In the Priorities section shown in Figure 5.38, these rules are set up and managed.
Figure 5.38 - The Priorities view.
The order of prioritization between the defined rules is also defined here. To the right of the Priorities view, the available lists are shown, grouped using the following types: Spectrum Lists Co Located lists Interference Lists Neighbor Lists Other Lists
www.actix.com
Actix Radioplan AFP Version 3.9 User Guide
Modeling 68
5.7.1.1
Spectrum Lists
Four types of rules are part of the spectrum list category: Forbidden A forbidden rule is used to limit the possible assignments of frequencies or color codes to a radio. This is a strict requirement and the optimizer will always fulfill this requirement. This rule can be used, for example, to achieve a band split scenario where some radios may be assigned frequencies in a certain spectrum part. Control radios are sometimes allocated a dedicated part of the spectrum band that may not be used by the traffic radios. Thus, the traffic radios may be forbidden to use the control radio spectrum. This rule is only available if forbidden frequencies or color codes are defined. Undesired An undesired rule is a softer version of the forbidden rule, by which Cellopt AFP will penalize against making certain assignments of frequencies that are undesired but not necessarily strict. For example, the undesired rule may project a preferred band split for control and traffic radios in problem areas where it may be accepted that the band split is violated to fulfill the capacity requirements. It may also be used at country borders where operators have agreed to limit the assignment of certain frequencies as much as possible but not in the strictest sense. For example, it is undesired that Operator A uses some frequencies mostly used by Operator B to minimize interference over the border. However, Operator A may use the undesired frequencies if no other better can be found. Desired A desired rule is used to ensure predefined assignments are kept. However, it allows Cellopt AFP to reassign a radio if an improvement can be found which is better than the level defined by the desired rule. For example, the desired rule may be used at the borders of retune areas, where it is desired that the sectors bordering on the retune areas not be changed if no major improvement can be found. Spare A spare rule is used to allow radios to remain unassigned if the sum of the incurred violations (for a radio) is larger than a specified value. It however allows Cellopt AFP to assign a radio if the interference (priority) increase by assigning a radio is below the level defined by the spare rule. This rule may be used to plan a network for additional (spare) radios to cope with an expected traffic growth if the interference is below a limit. Note that the spare rule can only be associated to radios that are configured as non-hopping/baseband hopping (GSM) or adhoc (TDMA, PDC and iDEN).
5.7.1.2
Co Located Lists
Co Located rules are used to define separation requirements between radio pairs that are co-located. Three types of rules are central to the co located list category, namely: Co Combiner The Co Combiner rule is used to specify separation requirements between two radios of the same combiner in a sector. This can be used to fulfill required combiner spacing. The radios that are combined together are specified in the Layers section using the Combiner category. This rule is only available for TDMA, PDC and iDEN technologies. Co Sector The Co Sector rule is used to specify separation requirements between two radios of the same sector or between combiners of the same sector. This can for example be used to avoid co, adjacent or higher order adjacent frequencies being assigned to the same sector. Co Site The Co Site rule is used to specify separation requirements between two radios of the same site (independent of sector). This can for example be used if
www.actix.com
Modeling 69
the operator wants to avoid having co, adjacent or higher order adjacent frequencies within sites. The Co Located lists are internal lists created by Cellopt AFP and cannot be loaded into a project. The Co Combiner list is created by the special category Combiner that allows the grouping of radios into combiners. See the Layers section.
5.7.1.3
Neighbor Lists
The neighbor list includes the neighbor relations in the network. A neighbor rule is used to impose restrictions between sectors that are defined as handover neighbors. For example, an operator may want to protect neighbor relations to make sure that the handover works properly. It is also possible to specify that co and adjacent frequencies may not be used at two neighbors.
5.7.1.4
Interference Lists
The Interference lists specify how much traffic or area would be affected (i.e., interfered) if two sectors reuse co or adjacent frequencies. The interference lists are often generated by Cellopt MDA or an external planning tool. The latter often refers to the list as an interference or permission matrix. The interference lists are often generated with the assumption that the interference is constant and at full power. An interference rule is used to consider the interference due to radio propagation between sectors in the network. An interference list is hence always required to minimize the radio interference.
5.7.1.5
Other Lists
The other lists category includes rules that are not part of those defined above. Examples of these rules include: Exception An exception rule contains separation requirements between sector pairs. It can be used for including planners local knowledge about reuse restrictions between sector pairs. Distance This is a kind of interference rule. The difference is that the sector relations describe priorities based on distance between sector pairs, instead of actual interference. See Lists for more details. 2nd order neighbor This is also an interference rule. It includes only interference relations between sectors and the neighbors to the neighbors of the sectors (2nd order neighbors). Site neighbors This is also an interference rule. It includes only interference relations between sectors and all sectors of the same sites as the neighbors of the sectors.
5.7.1.6
Prioritization Structure
The rule prioritization order is presented as a table to the left of this page, as shown in Figure 5.37. The prioritization is structured as three classes, namely: Strict Rules of this class are strict and should be used for rules that are supposed not to be violated at all. Forbidden rules can only be strict. Strict has the highest priority. Red color-coding is used for this class. Important Rules of this class are to be considered as important, but may be violated by Cellopt AFP. Important has lower priority than strict. Yellow colorcoding is used for this class.
www.actix.com
Modeling 70
Interference Rules of this class are to be considered tradable by Cellopt AFP. Interference lists are typical of this category and Interference has the lowest priority. Green color-coding is used for this class. A rule must be assigned to one priority class. Rules part of the Important and Interference classes are further differentiated using an additional weight factor. No weights are used for Strict rules. The prioritization table includes columns detailing list name, category and layer, separation, priority (class and weight) and advanced settings. An interference list is always marked with a sign. For interference lists, the column with advanced settings may include an S, T or FH. This indicates that the scaling, threshold or frequency hopping options respectively differ from the default values for a particular list. More details on these options are found in sections below. It is further possible to sort the table with respect to list name, separation and priority by clicking on the heading. A rule may be deleted by right clicking the name of the rule. The relative importance between the classes may be changed by selecting Classes, as shown in Figure 5.39. Upon selection the following dialog will appear:
Figure 5.39 The Classes dialog, where the relative importance between the priority classes are set.
The relative importance between Strict and Important as well as between Important and Interference is set in this dialog. These values should not be changed frequently. Instead, the class and weight of rules should be changed during the planning process to find a trade off according to the desired planning preferences. The (classes) settings will determine the final priority (weighted priority) that will be seen by the optimizer, i.e. after weighting and scaling etc. The defaults in Figure 5.38 imply that an important rule with weight 1 (the multiplier) has 10000 higher priority than an interference rule. Further, a strict rule will be 10000 0000 more important than an interference rule. The default may also imply that an interference rule could be considered
www.actix.com
Modeling 71
as an important rule if the value in the interference list exceeds 10000 after weighting and scaling. The maximum priority considered by the optimizer corresponds to the strict level, i.e. red class * yellow class (10000*10000 in the example above). A priority can never exceed this value. Note, if a Cellopt AFP 2 project is imported, the defined planning rules and associated penalties will automatically be translated into corresponding priority classes and weights using the default class settings.
5.7.1.7
Add Priority
A rule will be added by selecting the list name that appears in the list to the right.
Figure 5.40 The Add Priority dialog for GSM projects, where separation, class and weight can be specified to form a rule.
The following must be specified (see Figure 5.40): Separation That applies to the rule. Separation is expressed as: Co (co frequency), Adj-1 (first order adjacent frequency), Adj-2 (second order adjacent frequency) etc. Higher order than Adj-1 is only possible for Co located and neighbor lists. The rule may also be effective on smaller separations than the defined one if no such rule exists (for the same list). For example, a neighbor Adj1 rule will be applied for neighbor Co with the same class and weight if no such rule is defined. If a different class and weight are required for e.g. Co and Adj-1 of a list, two rules must be defined. Priority Priority of rule in terms of class and weight (Important and Interference only). Co located lists with Adj-2 separation or higher can only be
www.actix.com
Modeling 72
set to Strict or Important. An interference list can, in its turn, only be set to class Interference. Note, the weight applies to interfered direction only, i.e., when a radio is interfered. A weight factor that applies to the interfering direction only (i.e., when a radio is interfering) can be set for interference lists under Scaling and Thresholds. These options are discussed below. A rule can also be defined that applies to radios of a category and layer. The layer to apply the rule to is selected by expanding the categories and layer list (marked with a symbol left of the list name). An additional option is available in the Add Priority dialog, namely: Only applicable when interfering and interfered This option is used to make the rule effective between radios of the same layer only. It is not applied if radios of the selected layer are interfered by radios of another layer (the latter is achieved by not selecting this option). The category and layer name will appear in a column of the prioritization list for the rule (see Figure 5.37). Note, if a radio is applied multiple weights on different layers, the product of the weights will be used for the radio. Further, there can at the most be two rules per list, category and layer combination.
5.7.1.8
Scaling and Thresholds
If a rule based on an interference list is created, it is possible to specify some advanced properties, as specified in Figure 5.41.
Figure 5.41 Scaling and Threshold properties that can be specified for interference lists.
www.actix.com
Modeling 73
The advanced properties consist of scaling options: Divide by number of radios This option is the default and it will distribute the interference of a sector to each radio uniformly. For example, if a sector with 4 radios is interfered with 2 Erlang (interfered traffic given from the interference list) from another sector, each radio will get 0.5 Erlang of interference. This option is effective for a radio if it is on on list level and all layers to which the radio belongs. Further, it is possible to protect radios of a sector by turning this option off on a layer level (the radios are part of this layer). In this case, the radios in the layer would get 2 Erlang interference each using the above example. This can be used for control radio protection. Relative amount of traffic This option implies that some radios, defined by a layer, carry relatively more traffic than the other radios of the sector, and therefore should get more protection. The relative protection value must therefore be specified. This option should be used to project a preferential channel assignment scheme. It can only be set on a layer and the Divide by number of radios option must also be applied on the list level for this option to be effective. If a radio has this option set for several of its layers, the product of the relative values will be used. Relative amount of interference This option implies that some radios, defined by a layer, experience relatively more interference than the other radios of the sector. The value of relative interference must be specified. This option should be to project an overlaid/underlaid subcells feature. It can only be set on a layer and the Divide by number of radios option must also be applied on the list level for this option to be effective. If a radio has this option set for several of its layers, the product of the relative values will be used. Multiply with traffic (not shown in Figure 5.41) This option is for converting an interference list with relations expressed in percentage interfered traffic or area to interfered traffic in Erlang. This is achieved by multiplying each relation with its sectors served traffic. Cellopt AFP will warn if no sector traffic is available. Sectors with no traffic will be multiplied with zero. This option appears only on list level, i.e. it can not be set on a layer. Multiply with weight when <Layer> radios are interfering This option will change the interference in the interfering direction (i.e., from one sector to another sector) by the specified value. The interfered direction is unchanged. If a radio has this option set for several of its layers, the product of the weights will be used. The threshold options are: Threshold This box, when checked, will impose an additional priority weighting if the weighted interference (scaled) exceeds or is equal to the specified threshold level. If a radio is assigned multiple thresholds on different layers, all individual thresholds will be applied. Absolute The threshold value. The unit of the threshold is the same as used in the list. Class The priority class (strict/important/interference). Weight The additional weighting factor to be imposed.
www.actix.com
Modeling 74
5.7.1.9
Frequency Hopping GSM
Some additional options are available for an interference list when a GSM project is used. A number of radio network features that may be used in GSM can be projected by means of scaling, as shown in Figure 5.42. Note that these options (expect traffic load per sector) are only applied on radios with baseband or synthesizer hopping. Non-hopping and control radios are unaffected.
Figure 5.42 The Frequency Hopping options that can be specified for interference lists in a GSM project.
The options include: Traffic load per sector This option is used to consider the interference probability from a sector instead of 100% activity. The average interference probability depends on the sector served traffic and number of radios in the sector. Sector traffic values are required for this option. However, a global value (dB or %) is specified in the form, to be used in sectors that are missing traffic values. If a radio has this option set for several of its layers, the minimum gain value will be used. Note that this option is effective for non-hopping radios as well. DTX This option is used to model the interference reduction that will appear if discontinuous transmission is used. The voice activity must be specified in terms of dB or %. If a radio has this option set for several of its layers, the minimum gain value will be used. DPC This option is used to model the interference reduction that will appear if dynamic power control is used in the base station. The power control gain is measured at the cell border and it can be specified in terms of dB or %. If a radio has this option set for several of its layers, the minimum gain value will be used.
www.actix.com
Modeling 75
Frequency diversity gain This option is used to enable the fast fading diversity gain present for slow moving mobiles when frequency hopping is used. It will make the GSM receiver more resistant to interference and improve the sensitivity. The diversity gain is dependent on the number of hopping frequencies. It is specified in dB and the column to the right shows the resulting scaling value in %. Linear interpolation is used for hopping lengths between two specified values. There can only be one setting per list. AMR (not shown in Figure 5.42) This option is used to model the gain achieved when Adaptive Multi Rate (AMR) vocoders are used in the network. The gain with AMR over the conventional vocoder must be specified in terms of dB or %. In addition, the population of AMR mobiles must be specified in %. There can only be one setting per list.
www.actix.com
Frequencies 76
6 Frequencies
6.1 Introduction
This section provides a comprehensive overview of the Frequencies section. The Optimize section is where frequency plans are optimized and analyzed. An interactive retune report is available to view implications from possible reassignments, as well as for performing actual frequency retunes. The views are: Analyze Analysis of a frequency plan can be performed in this view. Optimize The frequency optimization is managed in this view. Retune Frequency retunes can be performed in this view.
Note that for iDEN projects, Cellopt AFP supports the frequency numbering scheme where the 800 MHz band uses numbers 1-720 and 2001-2720. Co and adjacent frequency interference between non co- or adjacent frequency numbers are detected for example between frequency numbers 1 and 2002.
6.2 Options
The first view in this section is the (optimization) Options for Frequencies view.
Figure 6.1 The Options for Frequencies view. For iDEN, an additional option Consider color code reuse is available.
www.actix.com
Frequencies 77
The following optimization properties may be specified: Priorities The Lists (or rules) to consider in the frequency optimization are selected here. Priorities defined from a list are enabled by selecting the list. By disabling a list, it is possible to disregard priorities without deleting the rules here. Co Sector rules are automatically enabled and cannot be disabled here. Note that rules are created and managed in the Priorities section. A link to the Priorities section is available under See Also. Options Here the global planning strategy (hopping for GSM or set strategy for TDMA, PDC or iDEN) is displayed. It is possible to change the strategy by pressing the link or return to the Spectrum section. Filter Here it is possible to apply a filtering function on interference lists. Relations where the co value is below or equal to the specified value is not considered by the optimizer in the analysis and optimization. This filtering is only a temporary filtering applied on analysis and optimization if enabled.
6.2.1 Spectrum Clearance

Support for clearing the spectrum (removing frequencies from the network) is presented here as well. The technique is to define temporary forbidden frequency rules for the frequencies to be removed. Part of this process is also to create a desired rule that is used for striving to keep the existing frequency assignments for the selected radios assigned to frequencies that are not to be cleared. To simplify this work, a three-step wizard is available: Forbidden frequencies Here the frequencies to be removed are specified, as well as the categories and layers of the radios to which the forbidden rule should apply. The forbidden frequencies are retrieved and filled in from the selected category and layer. Priority for selected radios Here you specify the Priority (class and weight) of the desired rule used for striving to keep the frequencies of the selected radios not subject to clearance. Ready to optimize Here, it is possible to start the frequency optimization. Note that the desired priority created in step 2 is effective only if the optimization is started from here. It will not appear in the lists under Priorities. The forbidden priorities will, however, remain.
6.2.2 Options - iDEN

For iDEN projects, an additional option is available: Consider color code reuse This option allows considering both co-frequency and co-color code reuse (not the color code offset reuse) from unselected/fixed radios during the frequency optimization. The priority to achieve this is given by the scaling factor. Interference relations from fixed radios with co-frequency and co-color code are scaled with the applied factor. This feature makes it possible to avoid color code re-planning after a frequency optimization.
6.3 Analyze
A frequency plan can be examined in more detail from the Analyze view. It is possible to view frequency assignments, violated rules as well as interfering sectors or radios. The analysis report can be shown in two ways:
www.actix.com
Frequencies 78
on the screen in a table. You then have the option of viewing a Detailed Report for one or more rows in the table. output to a tab-delimited text file. This can then be examined in detail in Microsoft Excel. Use this for very large reports which can be difficult to view on screen. Before the Analyze report is generated, the radios to analyze should be selected in the Radio Editor in the top of the view. In a similar way to the List Analyze function discussed on page 65, it is possible to create interactive summaries using a pivot function. The frequency plan data is presented by means of subtotals that are defined by the pivot function. The subtotal columns presented in the table are selected by the pivot. Figure 6.2 shows the Analyze view with a plan selector and the pivot field selector. First, a plan to be analyzed must be selected in the Plan selector which includes several plans. Current denotes the currently optimized frequency plan, i.e. frequencies in Frequency column in the Radio Editor. Old denoted the frequencies in the Old frequency column (the plan included in the loaded radio database). The plan selector may also include plans saved under names using the option in the Radio Editor. There is also a Compare with plan selector used for comparing plans; see the section about Delta reports on page 82.
Figure 6.2 The Analyze Frequencies view with the pivot function selector used to examine a frequency plan in more detail.
Rather than defining all the fields in the analysis, you may want to use a previously saved configuration. All such configurations are listed in a box to the right simply click the required configuration once to populate the fields, or double-click to perform the analysis directly. To delete an existing configuration, right click on the configuration name and select the Delete option. Once you have defined the fields that you want to use, you can
www.actix.com
Frequencies 79
click on Save current configuration to store the configuration for future use with the current project. Now select the pivot. Note that you can select multiple fields by checking the and box after each Field, and that you can also check a box to include all user-defined layers in the detailed reports. These properties can be used in pivot mode: List Used to report per list. Site/SiteR Used to report per site (serving/interfering). Sector/SectorR Used to report per sector (serving/interfering). Radio/RadioR Used to report per radio (serving/interfering). Old frequency/Old frequencyR Used to report per original frequency, MAL or frequency set (serving/interfering). Frequency/FrequencyR Used to report per optimized frequency, MAL or frequency set (serving/interfering). Position/Position R Used to report per position of radio in sector (serving/interfering). System categories/System categoriesR Used to report per system categories (serving/interfering). For GSM, the system category Hopping Strategy is available. For TDMA, iDEN or PDC, Set Strategy and Combiner will be available (see Layers above). Defined categories/Defined categoriesR Used to report per category defined by the user (serving/interfering). All defined are present. The analysis report will be presented in a Summary table and it will include these analyze properties: Count This represents the number of violations in the selected pivot. Priority This represents the weighted sum of all priorities from the violated rules in the selected pivot. Imp Co This represents the weighted sum of the priorities from the violated Important co frequency rules in the selected pivot. Imp Adj This represents the weighted sum of the priorities from the violated Important first order adjacent frequency rules in the selected pivot. Imp Adj+ This represents the weighted sum of the priorities from the violated Important second order and higher adjacent frequency rules in the selected pivot. Int Co This represents the weighted sum of the priorities from the violated Interference co frequency rules in the selected pivot. Int Adj This represents the weighted sum of the priorities from the violated Interference adjacent frequency rules in the selected pivot.
www.actix.com
Frequencies 80
An example is shown in Figure 6.3 where the List option has been used as the pivot (i.e., the subtotal per list is desired). The number of violated rules, sum of importance and interference are reported per list in this case.
Figure 6.3 The Analyze Frequencies table, where the List entry has been used as a pivot.
It is possible to sort rows with respect to certain columns by double-clicking the column header. Furthermore, selecting one row in the summary table and then choosing Details will show all violated rules (i.e., one per row), as seen in Figure 6.4. The following analyze properties will be shown: Priority This represents the weighted priority of the violation. List This represents the name of the violated list. Site This represents the id of the site that is serving (target). Sector This represents the id of the sector that is serving (target). Radio This represents the id of the radio that is serving (target). Frequency This represents the frequency, MAL or frequency set assigned to the serving radio above. SiteR This represents the id of the site that is interfering. SectorR This represents the id of the sector that is interfering.
www.actix.com
Frequencies 81
Figure 6.4 The Detailed Report view, where the properties are shown per radio.
RadioR This represents the id of the radio that is interfering. FrequencyR This represents the frequency, MAL or frequency set assigned to the interfering radio above. Imp Co This represents the weighted co frequency priority from an Important rule if any. Imp Adj This represents the weighted first and higher order adjacent frequency priority from an Important rule if any. Int Co This represents the weighted co frequency priority from an Interference rule if any. Int Adj This represents the weighted first order adjacent frequency priority from an Interference rule if any. It is possible to enter the summary view again, by choosing Summary. The table contents may also be saved, exported to Excel or printed. Note that Cellopt AFP always considers frequency sets to be fully utilized (all frequencies in a set are active and generating interference) during the set optimization. The actual frequency assignments to radios are performed after the optimization has finished. As a result, the total priority shown in the Optimization Progress and in the analysis report may differ. The analysis report shows the priority for the actual assignments. Cellopt will consider and report adjacent frequency violations that occur between nonadjacent frequency numbers in the E-GSM 900 and R-GSM 900 band, e.g., between
www.actix.com
Frequencies 82
frequency numbers 0 and 1023, as well as in the AMPS/IS-136 (TDMA) A and A bands, in this case e.g. between frequency numbers 1 and 1023. For iDEN projects, Cellopt AFP supports the frequency numbering scheme where the 800MHz band uses numbers 1-720 and 2001-2720. Co and adjacent frequency interference between non co- or adjacent frequency numbers are detected, for example between frequency numbers 1 and 2002.
6.3.1 Delta Report

It is possible to compare two plans by using a delta report. Plans can be created using a Save Plan option in the Radio Editor header; see the section on Layers on page 44 for more information. The delta report shows the difference (a subtraction) between the first plan, selected in the Plan selector, and the second plan, selected in the Compare with selector (available by pressing the More button in Figure 6.2). The delta report can be generated in a number of ways using the pivot selector, similar to the analysis report. An example is shown in Figure 6.5 where per List is the selected pivot. A negative value means that the priority or number of counts has decreased for the second plan compared to the first plan. In the same way, a positive value means that the first plan has a higher value in a given cell of the report. You can also display a detailed delta report similar to the detailed report. In this case, the frequency columns include the assignments of both plans.
Figure 6.5 The Delta report, where frequency plans can be compared in terms of number of violations and priorities.
www.actix.com
Frequencies 83
6.4 Optimize
Frequency optimization is performed in this view, see Figure 6.6. The radios to be assigned frequencies (i.e., to be optimized) are selected in the Radio Editor at the top of the page using autofilter functions. The optimizer will assign frequencies only to the selected radios. The unselected radios will be unchanged but their assignments will be considered by the optimizer, i.e., interference from the unselected radios will be taken into account. The optimization is controlled via the Start and Stop buttons; there is a progress table to the left. The progress is expressed using the following columns: Class The class of rule with highest priority currently violated in the optimized plan. Imp class means that at least one Important rule is violated in the plan etc. Int means only Interference rules are violated.
Figure 6.6 The Optimize Frequencies view, where the frequency optimization is started or stopped and the optimization progress can be viewed.
Importance The weighted sum of the violated Important rules in the optimized plan. Importance The Importance delta compared to the previous plan. Interference The weighted sum of the violated Interference rules in the optimized plan. Interference The Interference delta compared to the previous plan. Assigned The count of reassigned frequencies. Assigned The delta between reassigned frequencies compared to the previous plan. Elapsed The total elapsed time.
www.actix.com
Frequencies 84
Elapsed The elapsed time difference compared to the previous plan. Clock The current time. Index The count of generated plans. The optimization progress can alternatively be shown by means of a graph. There is a button in the top of the table to switch to graph mode. In the table, there are also options to save, print and clear the table as well as start and stop the optimization; for example, see Figure 6.6. The optimized plan can be viewed in the Radio Editor when the optimization is stopped.
6.5 Retune
In the Retune Frequencies view shown in Figure 6.7, one can generate reports showing the implications of possible frequency reassignments.
Figure 6.7 The Retune Frequencies view.
From this view it is also possible to perform a manual retune, i.e., change frequency assignments for radios. Before the Retune report is generated, the radios to study should be selected in the Radio Editor (Figure 6.7). Note that it may be several minutes until the process is completed, depending on the size of the selection and number of available frequencies. Note also that if the radio selection is changed, the Retune report must be regenerated.
www.actix.com
Frequencies 85
The Retune report is available in two report views, namely Priority and Best Choice. The buttons P, BC in the report header can be used to switch between the two reports. It is possible to hide the four summary columns by pressing the arrow in the report header. Priority This shows the (weighted) priority for all available frequencies per radio. The priority value for a given frequency represents the incurred priority if a radio is reassigned to this frequency. The available frequencies are listed as columns with the priority values in the rows below, as shown in Figure 6.8.
Figure 6.8 The Priorities view of the Retune report showing the priority per available frequency for each radio. Click the BC at the top to move to the Best Choice view.
The current frequency assigned to each radio is highlighted in the table. The priority value for each available frequency is also color-coded (yellow or green) to show the class of the worst violated rule. Note that the radios of a sector that have the same layer settings are grouped into the same row. Further, forbidden frequencies are indicated with blanks in the report. Frequencies that will break a strict rule (except forbidden) if reassigned are indicated with a red X.
www.actix.com
Frequencies 86
Best Choice This shows the available frequencies sorted in best choice in increasing priority order per radio (Figure 6.9). The current frequency assigned to each radio is also highlighted. Frequency numbers are colored red, yellow or green to show the class of the worst violated rule if reassigned to this frequency.
Figure 6.9 The Best Choice view of the Retune report showing the best frequencies for each radio in order. Click the P at the top to move to the Priorities view.
A manual retune can be performed in both views in two steps. First, unassign the frequency to be changed by double-clicking that frequency (i.e. the cell in the table). Next, assign the new frequency by double-clicking it. Press the Retune button to complete the retune operation; Cellopt AFP will then update the report views accordingly. Two columns help identify obvious improvements (for non-optimal plans): Potential This column reports the priority difference that can be achieved with a single retune. More exactly, the difference is the priority delta between the worst assignment and the best reassignment for this radio or group of radios. An optimal assignment (i.e. no improvement or potential) has a blank in this column. Retune Shows the recommended frequency reassignment (listed as before to after) for achieving the priority improvement reported in the Potential column for this radio or group of radios. To perform a retune, double-click a cell. If user-defined MAL are optimized in a GSM project, MAL, not frequencies, are listed in the retune report. A complete MAL must be retuned, not individual frequencies of the MAL. If frequency sets are used for assignment (TDMA, PDC or iDEN), you can change individual frequencies in sectors. iDEN QUAD/WiDEN radios will have a slightly different appearance, since they may be assigned up to four adjacent frequencies. A Q/W is treated as a group of radios where the assigned frequencies are shown with a gray background in the Priority view. The priority value for a particular frequency refers to the impact of being assigned to the range of frequencies starting at this particular frequency. For example, for a Q/W assigned three frequencies, the frequency 5 column indicates the priority if the Q/W is assigned to frequencies 5, 6 and 7. In the Best Choice view, only the first frequency in the range is highlighted. A Q/W may be unassigned by clicking any of the highlighted frequencies. A Q/W is assigned by clicking on the first frequency in the range.
www.actix.com
Frequencies 87
MCRB groups are indicated by an "M" in the Demand column before the number of radios. A 6-radio MCRB will be indicated as "M6". MCRBs may cover more than one row of the retune report when different rules apply to different radios. This will typically be because one radio is a control radio. This will be indicated by row numbers in brackets in the Demand column. For example, the control radio may be indicated as "M1(1)" on the first row, with 5 non-control radios indicated as "M5(2)" on the second row. The Retune column for an MCRB suggests a complete set of replacement frequencies that satisfy the separation requirement. The old frequencies are not shown in the Retune column for MCRBs. If an MCRB is split between more than one row, the Retune column will suggest an assignment in each row within the same 50-frequency range. Clicking on the Retune column in any row will perform the retune for that row and for other rows of the same MCRB.
www.actix.com
HSN and MAIO 88
7 HSN and MAIO

7.1 Introduction
The section is only available for GSM projects. Here, the Hopping Sequence Number (HSN) and Mobile Allocation Index Offset (MAIO) optimization can be performed if a frequency plan or Mobile Allocation List (MAL) plan is available. HSN and MAIO are only allocated to frequency hopping radios in GSM systems. Cellopt AFP will always use HSN from 1-63 for the assignment. For HSN and MAIO optimization, three views are available, as shown in Figure 7.1, namely: Analyze HSN and MAIO plan analysis can be performed in this view. Optimize The HSN and MAIO optimization are managed in this view. Retune The HSN and MAIO retunes can be performed in this view.
Figure 7.1 The Options for HSN and MAIO optimization view.
7.2 Options for HSN and MAIO

The first view in this section shows the HSN and MAIO options seen in Figure 7.1. The following HSN optimization properties may be specified: Lists The Lists (or rules) to consider in the HSN optimization, i.e., optimization priorities are derived from the specified lists as discussed below. Synchronization Click the Optimize Sync Groups to optimize the sync group assignments. HSN Options Three options may be selected to achieve a desired HSN planning strategy.
www.actix.com
HSN and MAIO 89
MAIO Options Allows regular MAIO steps in sectors for consistency with Nokia methodology. Filter Applies a filtering function on interference lists.
7.2.1 Lists
The lists that define the optimization priorities must be selected. Neighbor, Interference and Other Lists loaded into the project may be chosen as well as Co-located lists (i.e., CoSite and Co-Sector), if any such rule is defined. Note that rules are created and managed in the Priorities section. The Co part of a list will be applied since the optimization only considers co frequency reuse and not any adjacent frequency reuse. For the MAIO optimization, Co-located rules will only be considered if they are of a strict priority class. Cellopt AFP always avoids co-MAIO within hopping groups even when not stated explicitly.
7.2.2 Synchronization
Figure 7.2 The HSN and MAIO Optimize Sync Groups view.
It is possible to identify synthesizer-hopping groups that may be synchronized and planned within the same HSN to avoid interference between the synchronized hopping groups (similar to site synchronization). It uses the selected lists and priorities from the frequency optimization as inputs. The result of the hopping radio grouping is written in a new system category, Sync group. Click Optimize Sync Groups to optimize the sync group assignments. Sync groups are only used if inter-site is selected from the HSN Options.
www.actix.com
HSN and MAIO 90
7.2.3 HSN Options

A HSN planning strategy must be selected and the following HSN planning strategies are available: Assign HSN for hopping groups The HSN is assigned per hopping group (i.e., group of radios sharing hopping frequencies). Synchronize hopping per site if possible If possible (without reusing a MAIO), HSN is assigned per site, with the same HSN assigned to all hopping groups in the site. At sites where this is not possible, HSN will be planned per hopping group. Radios assigned to layer Synth sector (of category Strategy) will be synchronized at sites, if possible. Synchronize hopping per site The HSN is strictly assigned per site and one MAIO will be reused within the site if there are more radios than number of hopping frequencies for the site (i.e., lack of MAIO). The MAIO is reused between the sectors with the least traffic. Note that this does not affect non-hopping or baseband radios. Synchronize hopping inter-site if possible If possible (without reusing a MAIO), the same HSN is assigned to all synthesizer hopping groups. Synchronize hopping inter-site The same HSN is assigned to all synthesizer hopping groups.
7.2.4 MAIO Options

Regular MAIO steps (Nokia) For consistency with Nokia methodology, this allows regular MAIO steps in sectors (for example 0, 2, 4, etc.). Irregular MAIO steps in a sector (e.g. 1, 3, 4) will not be allowed if this option is enabled.
7.2.5 Filter
Filter Here it is possible to apply a filtering function on interference lists. Relations where the co value is below or equal to the specified value is not considered by the optimizer in the analysis and optimization. This filtering is only a temporary filtering applied on analysis and optimization if enabled.
7.3 Analyze
Similar to the Analyze Frequencies option, a HSN and MAIO plan can be examined in more detail by using a pivot table as its view. The radios to be analyzed are selected in the Radio Editor. More details about the use of the pivot and analyze report features can be found in the Analyze Frequencies section on page 77. The pivot function for HSN and MAIO analysis is the same as the one used for Analyze Frequencies except that there are some additional fields: Old HSN Used to report per original HSN (serving). Old MAIO Used to report per original MAIO (serving). HSN/HSNR Used to report per optimized HSN (serving/interfering). MAIO/MAIOR Used to report per optimized MAIO (serving/interfering).
www.actix.com
HSN and MAIO 91
The analysis report will be presented in a table and it will include the analyze properties below: Count This represents the number of violations in the selected pivot. Priority This represents the weighted sum of all priorities from the violated rules in the selected pivot. HSN Imp This represents the weighted priority sum from the violated Important co-HSN rules (i.e., when it is co-HSN and co-frequency simultaneously) in the selected pivot. HSN Int This represents the weighted priority sum from the violated Interference co-HSN rules (i.e., when it is co-HSN and co-frequency simultaneously) in the selected pivot. # MAIO Co This represents the number of assignments in the pivot with co-HSN and co-MAIO. # MAIO Adj This represents the number of assignments in the pivot with coHSN and adjacent-MAIO. Details will show all violated rules, one per row of the selected summary row. The detailed analysis properties are the same as used in the detailed frequency analysis view, except that the frequency specific fields are excluded and some new ones are added. The HSN specific properties are: HSN This represents the HSN assigned to the serving radio. MAIO This represents the MAIO assigned to the serving radio. HSNR This represents HSN assigned to the interfering radio. MAIOR This represents the MAIO assigned to the interfering radio. HSN Imp This represents the weighted priority from a violated Important coHSN rule (i.e., when it is co-HSN and co-frequency simultaneously) if any. HSN Int This represents the weighted priority from a violated Interference co HSN rule (i.e., when it is co-HSN and co-frequency simultaneously) if any. # MAIO Co This represents the number of assignments with co-HSN and coMAIO. # MAIO Adj This represents the number of assignments with co-HSN and adjacent-MAIO.
www.actix.com
HSN and MAIO 92
7.4 Optimize
The HSN and MAIO optimization is performed and managed in this view (see Figure 7.3).
Figure 7.3 The Optimize HSN and MAIO view.
The radios to be assigned HSN and MAIO (i.e., optimized) are selected in the Radio Editor. The optimization progress is identical to that described for frequencies above.
7.5 Retune
Similar to Retune Frequencies, an interactive retune report for HSN assignments is available in this view. The function is the same as in Retune Frequencies except that HSN are shown instead of the frequencies. The implications of HSN reassignments are shown and HSN retunes may be performed similarly. More details about the retune report features can be found under Retune Frequencies on page 84.
www.actix.com
Color Codes 93
8 Color Codes
8.1 Introduction
In this section, color codes are assigned to radios. Optimizing color codes requires that frequencies have been assigned to the selected radios. In general, color codes are used by receivers to distinguish between separate serving traffic channels and co-traffic channels, i.e., frequency reuse cases. The color code properties differ between system technologies and appearance of this section is highly dependent on the chosen technology. For example, color codes are referred to as BSIC, NCC, BCC and TSC in GSM. Similar to Frequencies, three views are available, as shown in Figure 8.1: Optimize Color code optimization is managed in this view. Analyze Analysis of a color code plan can be performed in this view. Retune Color code retunes can be performed in this view.
Figure 8.1 The GSM color code optimization options.
www.actix.com
Color Codes 94
8.2 Color Code Options GSM

In GSM, Base Station Identity Codes (BSIC) and Training Sequence Codes (TSC) are assigned to radios. The BSIC is associated to control radios only and it consists of a Network Color Code (NCC) and a Base station Color Code (BCC). Cellopt AFP will optimize both BSIC and TSC to selected radios if desired. It is possible to allocate one BSIC and one TSC per sector. Available BCC and TSC are always 0-7 respectively and available NCC is specified in the Spectrum (Project) section discussed previously. The following GSM color-code optimization properties, shown in Figure 8.1 may be specified (more details are found below): Lists The Lists (or rules) to consider in the color code optimization are specified here. Rules Two options are set to achieve a desired color code planning strategy. Training sequence codes TSC reuse options are set here.
8.2.1 Lists GSM

Lists (or rules) to consider in the color code optimization, i.e., optimization priorities are derived from the specified lists., are selected here Neighbor, Interference and other Lists loaded into the project may be chosen as well as Co-located lists (i.e., Co-Site and CoSector) if any such rule is defined. The Co part of a list will be applied since the optimization considers only co frequency reuse and not any adjacent frequency reuse. Lists to be used to derive color code reuse priorities are selected under the Priorities column. Lists to be used as neighbor definitions (for Server and interferer option below) are selected under the Neighbors column.
8.2.2 Rules GSM

There are two options to set a desired color code planning strategy, namely: Server and interferer This option is used to give preference for avoiding the same BSIC, BCC or TSC on co-frequencies, i.e., reuse of BSIC, BCC or TSC, between a server and interferer. Neighbor and interferer This option is used to give higher priority for avoiding the same BSIC on a neighbor to a serving sector and interfering sectors to the same server. This will improve handover performance since it is easier for the system to distinguish between a handover candidate and an interferer to the same sector that may cause a handover failure if selected. A neighbor list must be specified for this feature to be active. A preference value is specified for each alternative indicating the respective importance. The same value for both options means equal importance and zero means no importance (i.e., it is not considered at all). It is also possible to consider only co frequency reuse or both co and first order adjacent frequency reuse when optimizing the BSIC. The latter option will result in an incurred priority if two radios are assigned adjacent frequencies and co BSIC (if an adjacent priority is defined between the sector pair).
www.actix.com
Color Codes 95
8.2.3 Filter - GSM

An interference list filer function is also available: Filter This applies a filtering function on interference lists. Relations where the co value is below or equal to the specified value is not considered by the optimizer in the analysis and optimization. This filtering is only a temporary filtering applied on analysis and optimization if enabled.
8.2.4 Training Sequence Codes GSM

There are two options to manage the planning of TSC, namely: Co-BSIC over co-TSC This is used to give higher priority to consider co-BSIC, i.e., co-NCC and co-BCC simultaneously, rather than co-BCC only on cofrequencies. BSIC is used for handover purposes and the TSC is used by the GSM receiver for correcting bit errors introduced by the radio environment. It is thus possible to set preferences for BSIC over TSC. Specifying the value one means equal importance (zero is not allowed here). Use another TSC than BSIC This is used when you want to assign two TSC per sector. A category with at least two layers must be specified. The sector radios in the layer (or layers) excluding the control channel are assigned a separate TSC. The sector radios part of the layer that includes the control radio will be assigned the TSC defined by BSIC. For example, choosing the category Radio Type having two layers, BCCH and TCH, will result in that TCH radios may get a different TSC than the one defined by the BSIC (that will be used for the BCCH radio). Note: the BCC is always used as TSC on common control channels.
Ignore co-TSC between synchronized radios This is used to reflect that no TSC (co-sequence) interference will occur between synchronized radios.
www.actix.com
Color Codes 96
8.3 Color Code Options TDMA & PDC

In TDMA and PDC mode, color code is the notation used and one color code is associated to each radio. The following TDMA and PDC color-code optimization properties (see Figure 8.2) may be specified: Lists The Lists (or rules) to consider in the color code optimization are specified here. Rules Two options are set to achieve a desired color code planning strategy. Filter Allows you to disable relations with low co values. Color code grouping Here options are set to control the assignment of color codes per sector.
8.3.1 Lists TDMA & PDC

Lists (or rules) to consider in the color code optimization that is, optimization priorities are derived from the specified lists are selected here. Neighbor, Interference and other Lists loaded into the project may be chosen as well as possibly Co-located lists (Co-Site and Co-Sector) if any such rule is defined. This is similar to the Lists selection for GSM above.
Figure 8.2 The TDMA and PDC color-code optimization options.
www.actix.com
Color Codes 97
8.3.2 Rules TDMA & PDC

There are two options to set a desired planning strategy: Server and interferer This option is used to give preference for avoiding the same color code on co-frequencies, i.e., reuse of color code, between a server and interferer. Neighbor and interferer This option is used to give higher priority for avoiding the same color code on a neighbor to a serving sector and interfering sectors to the same server. A neighbor list must be specified for this feature to be active. A preference value is specified for each alternative indicating the importance. The same value for both options means equal importance and zero means no importance (it is not considered). It is also possible to consider only co-frequency reuse or both co- and first-order adjacent frequency re-use when optimizing the color codes. The latter option will result in an incurred priority if two radios are assigned adjacent frequencies and co color code (if an adjacent priority is defined between the sector pair).
8.3.3 Filter TDMA & PDC

An interference list filer function is also available: Filter Here it is possible to apply a filtering function on interference lists. Relations where the co value is below or equal to the specified value is not considered by the optimizer in the analysis and optimization. This filtering is only a temporary filtering applied on analysis and optimization if enabled.
8.3.4 Color Code Grouping TDMA & PDC

This option allows you detailed control over how the color codes should be assigned per sector. A selector Plan color codes per is available and it includes two predefined fields, Sector and Radio, as well as any user-defined categories. Sector is used to assign a single color code per sector (assigned to all radios in the sector). Sector should typically be used for a pure IS-136 digital network. Radio is used to be able to plan color code per radio in sectors, i.e. each radio may be assigned a unique color code. This is typically used for a pure analogue AMPS network. If a user-defined category is selected, its Layers will define groups that share color code per sector. For example, a category with three layers will assign three groups of color codes per sector, where all radios in each layer share the same color code that is, three different color codes per sector are assigned. If a category is selected, you can also assign color codes per radios for layers of the selected category by using the Assign color codes per radio for option and selecting one or more layers (hold down the Ctrl key and click on an option to deselect a layer).
www.actix.com
Color Codes 98
8.4 Color Code Options iDEN

In iDEN, two color code entities, referred to as color code offsets and color codes, are assigned to radios. One of each is associated with each sector. The color codes are considered for all radios while the color code offsets are considered for control radios only. The following iDEN color-code optimization properties may be specified (see Figure 8.3): Lists The Lists (or rules) to consider in the color code optimization are specified here. Options Two options are set to achieve a desired color code planning strategy. Filter Allows you to disable relations with low co values.
Figure 8.3 The iDEN color code optimization options.
8.4.1 Lists iDEN

Lists (or rules) to consider in the color code optimization; that is, optimization priorities are derived from the specified lists. Interference and other Lists loaded into the project may be chosen as well as possibly Co-located lists (Co-Site and Co-Sector) if any such rule is defined. Lists to be used to derive color code reuse priorities are selected under the Priorities column.
www.actix.com
Color Codes 99
8.4.2 Options iDEN

There are two color code options: Co-color code and offset over co-color code This is used to give higher priority to consider co-color code (DCC) and co-color code offset (PCCH) simultaneously rather than co-color code only. Specifying the value 1 (one) means equal importance. Specifying values smaller than 1 indicates lower importance. This factor scaling may be specified between control radios and other radios. Other radios means that at least one of the serving or interfering radios is a non-control radio. So it is possible to associate the color code offset (PCCH) to either the control radio only or to all radios. Use priorities defined by adjacent column in permissions matrix Cellopt AFP will use the interference values from the adjacent column in the interference matrix as the color-code interference values, if enabled. Optimize color code offsets only This option is used if it desired to optimize the color code offsets only. The color codes will then be unchanged, i.e. fixed.
8.4.3 Filter - iDEN

A function is also available to filter interference lists: Filter Here it is possible to apply a filtering function on interference lists. Relations where the co value is below or equal to the specified value is not considered by the optimizer in the analysis and optimization. This filtering is only a temporary filtering applied on analysis and optimization if enabled.
8.5 Analyze
Similar to Analyze Frequencies, in this view a color code plan can be examined in more detail using a pivot table. More details about the use of the pivot and analyze report features can be found in the Analyze (Frequencies) section on page 77. The pivot function for color code analysis is the same as the one used for Analyze Frequencies, except the Old frequency field is excluded. In addition, the function includes: Old color code Used to report per original color code/BSIC (serving). Old BSIC Used to report per original BSIC (serving). For GSM projects only. Color code/Color codeR Used to report per optimized color code (serving/interfering). BSIC/BSICR Used to report per optimized BSIC (serving/interfering). For GSM projects only. Sector via Used to report sectors that have a neighbor with an interferer reusing color code (both have the same color code or BSIC). This field in not used in iDEN. Note, a GSM BSIC is specified as a NCC/BCC (TSC) pair. For iDEN, a color code includes similarly a color code/color code offset pair. The Summary analysis report will be presented in a table and it will include the analyze properties below (apart from the selected pivot fields): Count This represents the number of violations in the selected pivot.
www.actix.com
Color Codes 100
Priority This represents the weighted sum of all priorities from the violated rules in the selected pivot. There are some additional analyze properties that are technology specific; see below.
8.5.1 Color Code Analyze Properties GSM

Imp BSIC This represents the weighted sum of the priorities from the violated Important co-BSIC rules (when it is simultaneously co-BSIC and co-frequency) in the selected pivot. Imp TSC This represents the weighted sum of the priorities from the violated Important co-TSC rules (when it is simultaneously co-TSC and co-frequency) in the selected pivot. Int BSIC This represents the weighted priority sum of the priorities from the violated Interference co-BSIC rules in the selected pivot. Int TSC This represents the weighted priority sum of the priorities from the violated Interference co-TSC rules in the selected pivot. If both co-BSIC and co-TSC violations occur between a sector pair, the incurred priority is reported in the co-BSIC column only. For example, the Int BSIC column will include interference priority from both the co-BSIC and co-TSC violations.
8.5.2 Color Code Analyze Properties TDMA & PDC

Imp Co-CC This represents the weighted sum of the priorities from the violated Important co-color code rules (when it is co-color code and co-frequency simultaneously) in the selected pivot. Int Co-CC This represents the weighted priority sum of the priorities from the violated Interference co-color code rules in the selected pivot.
8.5.3 Color Code Analyze Properties iDEN

Imp CC&CCO This represents the weighted sum of the priorities from the violated Important co-color code and color code offset rules (when it is simultaneously co-color code, co-color code offset and co-frequency) in the selected pivot. Imp CC This represents the weighted sum of the priorities from the violated Important co-color code rules (when it is simultaneously co-color code and cofrequency) in the selected pivot. Int CC&CCO This represents the weighted priority sum of the priorities from the violated Interference co-color code and color code offset rules in the selected pivot. Int CC This represents the weighted priority sum of the priorities from the violated Interference co-color code rules in the selected pivot. Details will show all violated rules (one per row) of the selected summary row. The detailed analyze properties are the same as in the detailed frequency analysis view. In addition, the following ones are added: Color code This represents the color code assigned to the serving radio.
www.actix.com
Color Codes 101
BSIC This represents the BSIC assigned to the serving radio. For GSM projects only. Color codeR This represents the color code assigned to the interfering radio. BSICR This represents the BSIC assigned to the interfering radio. For GSM projects only. The violations of the color code assignments are reported using the same technologyspecific analyze properties, as defined above.
8.6 Optimize
The color code optimization is performed and managed in this view, and is similar to Optimize Frequencies (see the previous section). Figure 8.4 shows the an example of the Optimize view. The radios to be assigned color codes (that is, to be optimized) are selected in the Radio Editor similarly. The optimization progress is also identical to the Optimize Frequencies progress.
Figure 8.4 The color code optimization view for GSM BSIC.
8.7 Retune
Similar to Retune Frequencies, an interactive retune report for color code assignments is available in this view. The function is the same as in Retune Frequencies, except that color codes are shown instead of frequencies. The implication of color code reassignments are shown, and color code retunes may be performed. More details about the retune report features can be found under Retune Frequencies.
www.actix.com
Export Plan 102
9 Export Plan
9.1 Introduction
This section is used for exporting optimized plans (frequencies, HSN & MAIO and color code plans) to different formats. You can also save the contents of the radio editor to file (see page 104).
9.2 Export Plan

This is the last section in the Project mode, and is shown in Figure 9.1 below. The purpose is to export frequency, HSN and MAIO, and color code plans to a file. Options to export, delete or create a plan are available here.
Figure 9.1 The Export Plan view, where frequency, HSN & MAIO and color code plans may be exported to file.
www.actix.com
Export Plan 103
To export, you need to specify the plan as well as the file name and format. Drop-down list boxes display lists of the available plans and the supported file formats. Cellopt AFP 3, Cellopt AFP 2, Planet 2.8 and ASSET XML are supported. Ericsson, Nokia and Nortel BSC/OSS formats may also be available if the supplementary data required to complete these formats is available. Depending on the format, there may be a check-box for including disabled sites, sectors and radios in the export; see the Network section above for more details. Also, for iDEN projects it is possible to include color code offsets in the export if Cellopt AFP 2 format is selected. The iDEN Cellopt AFP 2 export only includes the color codes by default. There is also a check box to export only those sectors or radios (depending on the selected export format) selected in the Radio Editor. An extended color code has been added to the plan export when the Cellopt AFP 2 format is selected for iDEN. The extended color code is exported together with the color code (DCC) and color code offset (PCCH), and it is always set to the same value as the color code offset (PCCH) of a sector. In the export, a dot is used to separate the color codes in the color code field. So, for example, 1.0 becomes 1.0.0. For Cellopt 2 format, it is also possible to export the Optimi Wizard category and layers if desired. A separate file will be created with the text _CatsLayers added to the selected file name. The layers of categories W:Technology and W:Channel Type are included in the export, as well as the QUAD/WiDEN layers of the system category Set Strategy (TDMA and iDEN technologies only). The file formats are described in the Input and Outputs chapter of this User Guide (see page 105).
www.actix.com
Export Plan 104
9.2.1 Save Radio Editor

Note that the link at the bottom of the Export Plan page displays the Save Radio Editor page (Figure 9.2), which allows you to save the contents of the radio editor to file of type: PDF, tab-delimited text, or HTML format.
Figure 9.2 The Save Radio Editor page.
www.actix.com
Input and Output Formats 105
10 Input and Output Formats

10.1 Introduction
This section gives an overview of the Cellopt AFP input and output formats. In general, several file formats are supported in Cellopt AFP and they are: Cellopt AFP 3 Cellopt AFP 2 Planet 2.8 ASSET Nokia interference matrix Ericsson interference matrix Explicit details on the Planet and ASSET formats can be found in their respective User Guides. A document describing the Cellopt AFP 2 format comes with the installation and it can be found in the doc folder under the installation folder on the users machine. The Cellopt AFP 3 format is described in more detail below.
10.2 Cellopt AFP 3 Format

Cellopt AFP 3 is an extensive mark-up language (XML) based format. XML makes use of tags (i.e., words bracketed by '<' and '>') to delimit data. Furthermore, attributes (of the form name="value") are used to describe and provide additional information about data elements. It is a text-based format and it can be viewed within a text editor or an XML enabled browser.
10.2.1 Input Data

A number of data are generally required to build a project. The following external data sources are generally needed: Radio database This contains information on all the sites, sectors and radios in the network to be considered. It contains, for example, sector names, which site the sector is on, numbers of radios required and existing frequencies, HSN and MAIO and color codes allocated. The radio database is stored under XML tag <network> using tags <site> and <sector>, <radio>, <frequency>, <colorcode>, <frequencygroup>, <frequencygroupentry>, <plans>, <plan>, <groupplanentry>, and <frequencyplanentry>. Spectrum lists A list of sectors and their undesired or forbidden frequencies and color codes. Undesired or forbidden frequencies and color codes are stored per sector in XML tag <sector>,<undesired_frequency>, <forbidden_frequency>, <undesired_group>, <forbidden_group> and <forbidden_colorcode>. Neighbor lists A list of the neighbor relations in the network. A neighbor list is also described by XML tag <list> including <rel>, see below for more details. Note that for a list to be defined completely, each site and sector must have been described by tags <site> and <sector> as well. Interference lists A list specifying how much traffic or area will be interfered if two radios in two particular sectors are allocated to the same or adjacent
www.actix.com
frequencies. An interference list is also described by XML tag <list> including <rel>. Note, for a list to be defined completely, each site and sector must have been described by tags <site> and <sector>. Other lists Exception, 2nd order neighbor, site neighbor and distance lists are included in this category. The exception list is a list of the exceptions in the network, e.g., separation requirements for different sector relations. 2 nd order neighbor, site neighbor and distance lists are similar to Interference lists and contain interference relations between sector pairs based on different properties. Other lists are also described by tag XML <list> including <rel>. Note, for a list to be defined completely, each site and sector must have been described by tags <site> and <sector>.
10.2.2 Output Files

Cellopt AFP 3 may generate several outputs. The following output types may be exported to file: Project A file container of an exported project. A project is described by XML tag <cellopt_afp> or <project>. Template A file that contains all Cellopt AFP 3 project settings. The settings could be, for example, optimization options and export format used. Apart from frequency and color code spectrum, network specific data (e.g., such as lists and rules associated with them) are not included in a template. A template is described by XML tag <cellopt_afp>. Plan A file that includes frequency and color code assignments for all radios in the network. The network is described by tag <network> and spectrum is described by tag <spectrum>. The actual assignments are stored in tag <plan>. Altogether, a number of tags are required to describe a plan. The attributes of the tags described above are detailed below.
10.2.3 XML Tags

A Cellopt AFP 3 project is described using a number of XML tags and attributes, in the tables below. Attributes in italic are optional. In the description field of tags and attributes, the following legend is used: Token [i] [s] [f] [d] [it] [st] [ft] [dt] Type Integer String Floating precision Double precision Integer given as PCDATA String given as PCDATA Float given as PCDATA Double given as PCDATA
Furthermore, a range format consists of comma separated range tokens. The range tokens can consist of a single integer or a range of integers separated by a - character. For example, 1,3-4,7-12 expands to the integers 1,3,4,7,8,9,10,11,12 respectively.
www.actix.com
10.2.3.1
<cellopt_afp>
<cellopt_afp> is the root node and the container of a Cellopt AFP project and of the selection of radios to be optimized. Attribute Type Description Type of export. The accepted values are: PLAN, TEMPLATE, LIST or MODEL. [s]
Tag <model> <selection>
Multiplicity 1 0..1
Description Cellopt AFP project. Selection of sites, sectors and radios to be optimized.
10.2.3.2
Attribute id name
Tag <network> <spectrum> <plans> <categories> <rules>
<Model>
Description Project id. [i] Project name. [s]
Multiplicity 1 1 1 0..1 1 0..1 Description Network contained within the project. The spectrums defined in this project. Frequency plans. Category and layer roots. Planning rules. Project settings.
<Model> is the project container.
<model_settings>
10.2.3.3
Tag
<selection>
Multiplicity 0.. * 0.. * 0.. * Description Radios of site selected. Radios of sector selected. Individual radios selected.
<selection> contains the radios selected to be assigned a resource, i.e., to be optimized.
<selected_site> <selected_sector> <selected_radio>
10.2.3.4
Attribute id
<selected_site>
Description Site id, unique within the project. This id is the same as inside the <network> tag, when defining a site. [i]
<selected_site> represents a selection of all radios belonging to a specific site.
www.actix.com
10.2.3.5
Attribute id
<selected_sector>
Description Sector id, unique within the project. This id is the same as inside the <network> tag, when defining a sector. [i]
<selected_sector> represents a selection of all radios belonging to a specific sector.
10.2.3.6
Attribute id
<selected_radio>
Description Radio id, unique within the project. This id is the same as inside the <network> tag, when defining a radio. [i]
<selected_radio> represents a selection of a specific radio.
10.2.3.7
Tag <site> <list>
<network>
Multiplicity 0..* 0..* 0..* Description Sites in the network. Lists. Sector alias maps
<network> is the root node of a Cellopt AFP network.
<sector_alias_maps>
10.2.3.8
Attribute id name latitude longitude disabled
<site>
Description Site id, unique within the project. [i] Site name. [s] Sites latitude in decimal degrees. [d] Sites longitude in decimal degrees. [d] Specifies if the site is disabled or not. no or yes. [s]
<site> represents a site in the network.
Tag <layer_id> <sector>
Multiplicity 0..* 0..*
Description Id of layers related to this site. The attribute id is the id of the layer referred to. Sectors within this site.
10.2.3.9
Attribute id name azimuth
<sector>
Description Sector id, unique within the project. [i] Sector name. [s] Sectors azimuth. If a sector does not have an azimuth value, a default value is used instead. [f]
www.actix.com
<sector> represents a sector in the network.
Attribute height tilt beamwidth antennatype servedtraffic servedarea donor_id
Description Sectors height. [f] Sectors tilt. [f] Sectors beam width. Cellopt MDA only. [f] Description of sectors antenna type. [s] Sectors served traffic. [f] Sectors served area. [f] The ID of the donor sector (sector_id). When specifying another sector as a donor sector, all radio information will be ignored (because of repeater characteristics). [i] Specifies if the sector is disabled or not. no or yes. [s]
disabled
Tag <layer_id> <undesired_frequency>
Multiplicity 0..* 0..*
Description ID of layers related to this sector. The attribute id is the id of the layer referred to. Undesired frequencies for this sector. The attribute id is the id of the frequency referred to. Undesired frequency group for this sector. The attribute id is the id of the frequency group referred to. Forbidden frequencies for this sector. The attribute id is the id of the frequency referred to. Forbidden color codes for this sector. The attribute id is the id of the color code referred to. For GSM, these are BSIC. For iDEN, these are color codes (not color code offsets) Forbidden frequency group for this sector. The attribute id is the id of the frequency group referred to. Radios on this sector.
<undesired_group>
0..*
<forbidden_frequency>
0..*
<forbidden_colorcode>
0..*
<forbidden_group>
0..*
<radio>
0..*
10.2.3.10
Attribute id name pos control_id
<radio>
Description Radio id, unique within the project. [i] Radio name, unique within the sector. [s] Radio position within this sector. [i] no = no control, yes = primary control. [s]
<radio> represents a radio in the network.
www.actix.com
Attribute group
Description The type of radio group that this radio belongs to. The accepted values are: GLOBAL, ADHOC, BASEBAND, SYNTH_SECTOR_1, SYNTH_SECTOR_2, SYNTH_SECTOR_3, SYNTH_SECTOR_4, SYNTH_SITE_1, SYNTH_SITE_2, SYNTH_SITE_3, SYNTH_SITE_4, SETS_ONLY, SETS_AND_SUBSETS, SETS_AND_INDIVIDUAL, QUAD_1, WiDEN_1, QUAD_2, WiDEN_2, etc. up to QUAD_8/WiDEN_8 and MCRB_1 up to MRCB_8. [s] Specifies if the radio is disabled or not. no or yes. [s] Specifies if the radio is selected or not (only included for plan exports). no or yes. [s] Specified if the radio should be assigned adjacent frequencies. ADJACENT. [s]
disabled selected intermod
Tag <layer_id>
Multiplicity 0..*
Description Id of layers related to this radio. The attribute id is the id of the layer referred to.
10.2.3.11
Attribute id name type
<list>
Description List id, unique within the project. [i] Lists name. [s] Type of list. Valid values are NEIGHBOR, INTERFERENCE, and OTHER. [s]
<list> represents a sector relation list used by the optimizer.
Tag <rel>
Multiplicity 0..*
Description Sector-sector relations.
10.2.3.12
Attribute s1 s2 co adj
<rel>
Description Id of sector 1 (interfered). [i] Id of sector 2 (interfering). [i] Optional, only for interference lists, co interference value. A dot is used to separate decimal values. [f] Optional, only for interference lists, adjacent interference value. A dot is used to separate decimal values [f]
<rel> represents a sector to sector relation.
www.actix.com
10.2.3.13
<spectrum>
<spectrum> represents the frequency and color code spectrum. There can be multiple spectrum tags within a project, each representing a different technology. Attribute id technology Description Spectrum id, unique within the project. It is optional in projects with only one spectrum. [i] Technology associated with this spectrum. This is always optional, as it might not be known at all times. Allowed values are GSM, IDEN, TDMA, PDC and GENERIC. [s]
Tag <frequency> <frequency_range> <colorcode> <colorcode_range> <frequencygroup>
Multiplicity 0..* 0..* 0..* 0..* 0..*
Description Available frequencies. [it] Available frequencies expressed in the range format. [st] Available color code. [i] Available color codes expressed in the range format. [st] Frequency groups in the set template.
10.2.3.14
<frequency>
<frequency> defines a specific individual frequency within the spectrum. All frequencies are expressed as channel numbers. Attribute id available Description Frequency value, unique for all frequencies within a spectrum. This value expresses frequencies as channel numbers. [i] This attribute marks if this frequency is a frequency available for the optimization. No value is associated to this attribute, just . This attribute marks if this frequency is a control frequency (iDEN only). No value is associated to this attribute, just .
control
10.2.3.15
<colorcode>
<colorcode> defines a specific individual color code within the spectrum. The nature of these data types depends a lot on the technology used. In GSM, they represent BSIC values (a combination of NCC and BCC). In TDMA and PDC, the color code value is a generic color code. In iDEN, Color Code Offsets (CCO) and Color Codes (CC) are specified. The color code value is then CCO*100+CC. The value specified by the id attribute is in the native format appropriate for the technology. Attribute id Description Color code value, unique for all color codes within a spectrum. [i]
www.actix.com
10.2.3.16
Attribute id
<frequencygroup>
Description Frequency group id, unique within the spectrum. This does not need to be unique against ordinary frequencies. For example, frequency 1 and group 1 can both exist in the same spectrum, but MAL1 cannot co-exist with Set1, as they are both groups. [i] Type of frequency group. MAL, CMAL or SET. [s] Multiplicity 0..* Description Frequencies in this group.
<frequencygroup> represents a frequency group within the spectrum.
type Tag <frequencygroupentry>
10.2.3.17
Attribute freq pos type
<frequencygroupentry>
Description Frequency as declared in spectrum [i] The position of the frequency within this group [i] Frequencys role in this group. CONTROL or ALTERNATIVE_CONTROL [s]
<frequencygroupentry> represents a frequency and its role in the frequency group.
10.2.3.18
Tag <plan>
<plans>
Multiplicity 0..* Description Plans in the system.
Under <plans>, all frequency plans in the system are stored.
10.2.3.19
Attribute id name type
<plan>
Description Plan id, unique within the project. [i] Plan name. [s] Plans role in this project. ORIGINAL, CURRENT or MDA. [s] Multiplicity 0..* 0..* Description Single frequency assignments in this plan. Frequency group assignments in this plan.
<plan> represents a frequency plan within the project.
Tag <frequencyplanentry> <groupplanentry>
www.actix.com
10.2.3.20
Attribute group_id colorcode hsn sync Tag <radio_id>
<groupplanentry>
Description Frequency group id. [i] Color code value. [i] HSN value. [i] Sync group identifier. [i] Multiplicity 1..* Description Radio id of radios that have the same frequency group assignment. The attribute id is the id of the radio referred to. [i].The optional attribute maio specifies the maio setting for this radio. [i]
<groupentry> represents a frequency group assignment to a number of radios.
10.2.3.21
Attribute radio_id frequency group_id color code hsn maio Sync
<frequencyplanentry>
Description Id of radio that has the frequency assignment. [i] Id of assigned frequency. [i] Frequency group id. [i] Color code value. [i] HSN value. [i] MAIO value. [i] Sync group identifier. [i]
<frequencyplanentry> represents a frequency assignment to a single radio.
10.2.3.22
Tag <category>
<categories>
Multiplicity 0..* Description Categories in the system.
Under <categories>, all categories in the system are stored.
10.2.3.23
Attribute id name Tag <layer>
<category>
Description Category id, unique within the network. [i] Category name. [s] Multiplicity 0* Description Layers within this category.
<category> represents a category in the network.
www.actix.com
10.2.3.24
Attribute id name Tag
<layer>
Description Layer id, unique within the network. [i] Layer name. [s] Multiplicity 0..* Description Undesired frequencies for this layer. The attribute id is the id of the frequency referred to. Forbidden frequencies for this layer. The attribute id is the id of the frequency referred to. Forbidden color codes for this layer. The attribute id is the id of the color code referred to. Undesired frequency group for this layer. The attribute id is the id of the frequency group referred to. Forbidden frequency group for this layer. The attribute id is the id of the frequency group referred to.
<layer> represents a layer in the network.
<undesired_frequency>
<forbidden_frequency>
0..*
<forbidden_colorcode>
0..*
<undesired_group>
0..*
<forbidden_group>
0..*
10.2.3.25
Attribute
<rules>
Description The classes value for strict priorities compared with important priorities. [i] The classes value for important priorities compared with interference priorities. [i]
Under <rules>, all planning rules in the system are stored.
red_over_yellow yellow_over_green
10.2.3.26
Attribute id list_id layer_id
<rule>
Description Rule id, unique within the project. [i] Id of list that this rule applies to. [i] Id of layer that this rule applies to. If the rule is being defined on the list level, then this attribute is left out. [i] Apply rule when layer is both interfered and interfering. Valid values are yes and no. Only for rules on the category/layer level. Common for all rules with the same list/category/layer combination. [s] The separation. Values are 0, 1, 2, [i]
<rule> represents a rule in the network.
apply_interfered_interfering
separation
www.actix.com
Attribute priority weight Tag <advanced_rule_properties>
Description The priority of the rule. Valid values are red, yellow, and green. [s] The weight of the rule. Must be a non-negative float. [f] Multiplicity 01 Description Properties that only apply to interference lists.
10.2.3.27
Tag <scaling> <thresholds>
<advanced_rule_properties>
Multiplicity 1 0..1 0..1 Description Container element for the scaling properties. Container element for the threshold property. Container element for the frequency hopping properties. Only include this section if using frequency hopping. Common for all rules with the same list / category / layer combination.
<advanced_rule_properties> represents the rule settings for an interference list.
<frequency_hopping>
10.2.3.28
Attribute
<scaling>
Description Normalized by number of radios in the interfered sector. Common for all rules with the same list / category / layer combination. [s] Multiply with the traffic in the interfered sector. Accepted values: yes or no. Common for all rules with the same list / category / layer combination. [s] Weight if radios from this layer are interfering. [f] Relative amount of traffic a radio from this layer carries in the interfered sector. Common for all rules with the same list / category / layer combination. [f] Relative amount of interference a radio from this layer experiences in the interfered sector. Common for all rules with the same list / category / layer combination. [f]
<scaling> represents the rule settings for the scaling.
normalize_number_radios
multiply_sector_traffic
interfering_weight relative_traffic
relative_interference
10.2.3.29
Attribute absolute
<threshold>
Description The absolute threshold. The attribute active can be yes or no. [f]
<threshold> represents the rule settings for the thresholds.
www.actix.com
Attribute priority weight
Description The priority used. The value is red, yellow, or green. [f] The weight of the threshold rule. [f]
10.2.3.30
Attribute traffic_load dtx dpc amr
<frequency_hopping>
Description Traffic load per sector. The value is given as a percentage value. [f] DTX voice activity. The value is given as a percentage value. [f] Downlink power control gain at cell border. The value is given as a percentage value. [f] AMR. The value is the value of this element The value is given as a percentage value [f] Percentage subscribers. Must be present if the attribute amr is present. [f]
<frequency_hopping> represents the rule settings for the frequency hopping.
amr_subscribers
10.2.3.31
Attribute technology
<Model settings_settings>
Description Technology of project. Recognized technologies are: GENERIC, GSM, TDMA, IDEN and PDC. [s] Multiplicity 0..* 0..1 Description MAL settings for this project. GSM specific. Frequency hopping gains.
<model_settings> represents project specific settings.
Tag <mal_setting> <frequency_hopping_gains>
10.2.3.32
Attribute layer_id min_length max_length
<mal_setting>
Description Layer id that this particular setting applies to. If left out, the settings apply to global level. [i] Minimum MAL length. [i] Maximum MAL length. [i] Common denominator of the resulting calculated MAL. [i] Percentage value of the preferred fractional load. [i]
<mal_setting> specifies the lengths of the legal MAL in different parts of the network.
common_length fractional_load
www.actix.com
10.2.3.33
<frequency_hopping_gains>
<frequency_hopping_gains> specifies the interference reduction expressed as scaling values. Attribute gain_2 Description Scaling value that should be applied to interfered side of relations that hop over two frequencies. [i] Scaling value that should be applied to interfered side of relations that hop over four frequencies. [i] Scaling value that should be applied to interfered side of relations that hop over eight frequencies. [i] Scaling value that should be applied to interfered side of relations that hop over 16 frequencies. [i] Scaling value that should be applied to interfered side of relations that hop over 32 frequencies. [i]
gain_4
gain_8
gain_16
gain_32
10.2.3.34
Tag <alias_maps>
<sector_alias_maps>
Multiplicity 0..* Description Alias map for this project.
<sector_alias_maps> stores the sector alias maps.
10.2.3.35
Attribute id name Tag <alias>
<alias_map>
Description Id of alias map, unique within the project. [i] Name of alias map. [s] Multiplicity 0..* Description Sector aliases for this alias map.
<alias_map> represents a sector alias map.
10.2.3.36
Attribute Sector_id name
<alias>
Description Sector id. [i] Sector alias name (alternative name). [s]
<alias> represents a sector alias (i.e. alternative name for a sector).
10.3 Planet 2.8 Format

Cellopt AFP supports import from Planet format, up to version 2.8. The required information about the network, i.e., radio database (e.g., sector names, numbers of radios required and existing frequencies allocated), are extracted from the Planet carrier and site files. Note; these files include some information that are not imported or stored in the
www.actix.com
Cellopt AFP database. Cellopt AFP imports only the required properties. It is also possible to import Planet exceptions, interference and neighbor files (i.e., lists) as well as export optimized plans to a carrier file. More information about the Planet 2.8 format can be found in the Planet 2.8 User and Technical Reference Guides.
10.4 ASSET Format

The ASSET v4.2, v5.0, v5.1, v5.2 and v6.0 XML formats are supported. The following files may be loaded into Cellopt AFP (note that the files must be loaded in the below order): Cell-Site-List GSM-Cell-List Carriers-List Car-Layer-List Asset AIT (interference table) Property Site, sector, radio and layer information as well as parameter assignments are imported. Note that Cellopt AFP does not read all information in the above files, only data useful for Cellopt is imported. The order of load is important. The neighbor data must be loaded site and sector data. Note that the ASSET interference table loader assumes that the sector name is only a single character and _ character used to separate site and sector name is not included in the site name. If Overlaid/Underlaid layers are defined in the interference table, separate lists will be created (for each layer respectively). Frequency, HSN & MAIO and BSIC assignments may also be exported from the Export section to a GSM-CELL-LIST file for importing back into ASSET. The User must choose the appropriate export format, either 4.2, 5.0, 5.1, 5.2 or 6.0.
10.5 Plan Export to GSM OSS/BSC Formats

In GSM projects, it is possible export plans to Ericsson, Nortel or Nokia OSS/BSC formats. The supplier of the radios (and sectors) in the network are identified using the BSC type category, see Layers section. To complete the OSS/BSC formats, supplementary data must be available in the project. In general, the supplementary data includes a mapping between the sector (cell) identity used in the OSS/BSC and name used in Cellopt. The format of the files including the supplementary data is tab-separated columns where the first column consists of a command which is the name of supplier and the OSS/BSC version information. The next two columns are the site name and the sector name used in Cellopt AFP 3. Any additional columns are specific for each supplier, see below. Note that the supplementary data is not included in a project export and must thus be reloaded when the project is imported. For Ericsson, the generated export fulfils CNA interface format for GSM OSS R9.1. For Nokia, the generated export fulfils the XML format for Nokia CM Plan Manager RAM 2.0.
10.5.1 Nortel Supplementary Data

Syntax: Nortel<tab><site><tab><sector><tab><omc><tab><id><tab><lac><tab><mcc><tab ><mnc><tab><bsc> Example:
www.actix.com
Nortel bsc1
CentralStation
North
omc1
111
11000
206
10
Note, a separate fplan-configuration file will be created for each BSC. The name of the file is given by both the OMC and the BSC.
10.5.2 Ericsson Supplementary Data

Syntax: EricssonGSMOSSR9.1<tab><site><tab><sector><tab><nw><tab><msc><tab><bsc><t ab><cell> Example: EricssonGSMOSSR9.1 CentralStation North nw1 msc7 b9 910
10.5.3 Nokia Supplementary Data

Syntax: NokiaRAMCM2.0<tab><site><tab><sector><tab><bsc><tab><bcf><tab><bts><tab>< version><tab><btsid><tab><trx><tab><trxids> Where the <trx> syntax is as follows: <trx><space><trx><space><trx> Where the <trxids> syntax is as follows: <trxid><space><trxid><space><trxid> Example: NokiaRAMCM2.0 CentralStation North btsid1 trx1 trx2 trx3 trx4 trx5 trx6 trxid5 trxid6 bsc1 bcf1 bts1 version1 trxid1 trxid2 trxid3 trxid4
Note that, an assumption is that the position for the given trx IDs matches the position for the trx presented in the bts. i.e. TRX1 with position 1 under the BTS would be trx1 and trxid1, the second radio in the BTS would be trx2 and trxid2 etc. All separated with space. For Nokia also information about the used MAL identities per BSC is required. The format shown below is used to load this information. Syntax: NokiaMALIDs<tab><bsc><tab><malids><tab><malINTids> Where the <malids> syntax is as follows: <malid><space><malid><space><malid> Where the <malINTids> syntax is as follows: <malINTid><space><malINTid><space><malINTid> Example: NokiaMALIDs malINTid 7 bsc1 malid1 malid2 malid7 malINTid 1 malINTid 2
The Nokia MAL information must be loaded after the sector information described by NokiaRAMCM2.0 shown above.
10.6 Ericsson Interference List Format

Cellopt supports the import of the Ericsson OSS generated interference lists (R8 FAS/FOX feature) in GSM projects. The Ericsson Supplementary data, described above, may be required to map the OSS sector identity to Cellopt sector names (if they are different). The imported list will include the percentage counts that violate the co and adjacent frequency
www.actix.com
interference thresholds, i.e. the ICDM-C and ICDM-A values. The Multiply with traffic scaling option should be applied to convert the interference list unit to interfered traffic in e.g. Erlang, see Priorities section above.
10.7 Nokia Interference List Format

Cellopt supports the import of the interference lists described in the Nokia OSS 3.1 XML format in GSM projects. The Nokia Supplementary data, described above, is required to map the OSS sector identity to Cellopt sector names. The imported list will include the downlink carrier over interference probability in percentage for co and adjacent relations, i.e. the coDLCIP and adjDLCIP values. The Multiply with traffic scaling option should be applied to convert the interference list unit to interfered traffic in e.g. Erlang, see Priorities section above. Cellopt will create one interference list per radio layer (BCCH, REGULAR or SUPER) if data for the layer is available in the source file.
10.8 Sector Alias Maps

Multiple sector names are supported to simplify importing data from different sources such as OSS and other performance tool applications. A sector alias map file (TAB separated file) can be created and loaded into Cellopt AFP. This map creates a relation between the AFP sector name and the sector alias for a data source. The sector alias name may include TAB characters. Up to three different alias names per sector may be available. The alias map file format syntax is: Alias_name<tab><Site><tab><sector><tab><cell name> The file must start with a header CELLOPT SECTOR MAP. Example: CELLOPT SECTOR MAP OSS Downtown2 A 20310
In the above example, sector Downtown2-A has an alias 20310 (the alternative sector name) for an OSS application. The aliases for a sector may be viewed and edited from the tree in the Network section. In addition, a new alias can be created directly from the client. Note that the aliases are included in a project export. The sector aliases are best used to import data such as neighbor, exception, interference and handover statistics lists. A simple text format is included to support this process. It is simply a TAB separated file that describes sector relations. Serving sector alias<tab><Interfering sector alias><tab><Co interference><tab><Adjacent interference> The file must start with a header CELLOPT ALIAS LIST, and the second row should include the list name. The Co and Adjacent interference columns are optional and may be left out. Here is an example of a neighbor list alias: CELLOPT ALIAS LIST HANDOVER Cell19 Cell102 In the above example, the neighbor list HANDOVER contains a neighbor relation between Cell19 and Cell102 (Cell102 is a neighbor to Cell19). Here is an example of an interference list alias: CELLOPT ALIAS LIST IM 20238 20239 0.09
0.02
www.actix.com
In the above example, the interference list IM contains a relation where sector 20238 is interfered by sector 20239. Co interference is 0.09, and adjacent interference is 0.02.
www.actix.com
Installation/Licensing and Troubleshooting 122
11 Installation/Licensing and Troubleshooting

11.1 Introduction
This section describes the hardware requirements, needed third party packages, the contents of the CD, the two minutes install of the software, the licensing and some trouble shooting. Note that if you are using Radioplan to provide the map functionality, Radioplan must be installed before you install Cellopt AFP. Ensure that your Radioplan license includes the AFP map module.
11.2 Hardware / Software Requirements

These are the minimum Windows hardware requirements for Cellopt AFP: 400 MHz PC 512 MB RAM 500 MB hard disk space Cellopt AFP will run on the following platforms: Windows 2000, with Service Pack 2 or above Download it from; http://www.microsoft.com/downloads/details.aspx?FamilyID=687646b3fdd7-4c6b-b1a9-8441ef2157d4&DisplayLang=en MSI Installation service package Download it from; http://www.microsoft.com/downloads/details.aspx?FamilyID=4b6140f92d36-4977-8fa1-6f8a0f5dca8f&DisplayLang=en Internet Explorer v5.5 or above Download v6 SP1 from: http://www.microsoft.com/downloads/details.aspx?FamilyID=1e1550cb5e5d-48f5-b02b-20b602228de6&DisplayLang=en
Windows XP Professional Windows XP comes with all the required packages, except for the packages below. In addition to this, the following packages are needed for all the platforms above: Microsoft XML (MSXML v6 SP1) Download MS XML v6 SP1 from; http://www.microsoft.com/downloads/details.aspx?FamilyID=d21c292c-368b4ce1-9dab-3e9827b70604&displaylang=en Microsoft Office Web Components (v11, v10 or v9) Version 9 is typically installed on machines with Microsoft Office 2000, or can be installed from the MS Office 2000 distribution CD. Version 10 is typically installed with the Microsoft Office XP, or can be installed from the MS Office XP distribution
www.actix.com
CD. If neither MS Office 2000 nor XP is installed, then Office Web Components v10 can be downloaded from: http://www.microsoft.com/downloads/details.aspx?FamilyID=982b0359-0a86-4fb2a7ee-5f3a499515dd&DisplayLang=en Windows XP Home Edition is not supported.
11.3 Cellopt AFP Installation

The Windows installation is typically a seven-step installation, and if all the required software packages above have been installed already then the installation should take about two minutes or so. Note that the user does not have to uninstall any previous Cellopt AFP installation that might reside on the machine. However, administrative privileges are needed to perform the installation (details of how to achieve this are shown below). During the installation, a database configuration file is edited, and this action may present a warning from programs like Norton AntiVirus, see e.g. Figure 11.1. For a successful installation, the action must be permitted.
Figure 11.1 This specific warning may be shown during the installation if Norton AntiVirus is available. To successfully install, you must allow the script to execute.
www.actix.com
The installation steps are: The main dialog which is the first screen in the installation procedure (see Figure 11.2).
Figure 11.2 The main dialog.
The License Agreement dialog. Please read the agreement before continuing (Figure 11.3).
Figure 11.3 The End User License Agreement dialog.
www.actix.com
The missing third party products dialog, where it is possible to install additional required software products (Figure 11.4).
Figure 11.4 The Install 3rd Party Products dialog.
The Choose installation folder dialog, where the user may select the folder in which to install Cellopt AFP (Figure 11.5).
Figure 11.5 The Choose installation folder dialog.
www.actix.com
The Ready to install dialog, where the user starts the installation (Figure 11.6).
Figure 11.6 The Ready to install dialog.
The Installing files progress view showing the progress of the installation using a bar (Figure 11.7).
Figure 11.7 The Installing dialog.
www.actix.com
The Installation Complete dialog, which is the last screen in the installation process (Figure 11.8).
Figure 11.8 The Installation Complete dialog.
11.4 Uninstalling Cellopt AFP

The Windows uninstaller for Cellopt AFP can be found under Add / Remove Programs in the Control Panel. The uninstaller will only remove the files installed by the Cellopt AFP installer. Note that the uninstaller will remove the project database and projects in the database will thus be lost. To save projects, export the projects to file before starting the uninstaller; see Export Project on page 19 for more information.
www.actix.com
11.5 Cellopt AFP Licensing

11.5.1 Requesting a License
It is possible to obtain a key by completing the information requested in the Cellopt AFP License Request (accessed from the splash screen by clicking the Next button); see Figure 11.9.
Figure 11.9 Appearance of Cellopt AFP License Request.
Once the requested information has been entered, click on the Request button to create an e-mail with the license request. A question to confirm this action will appear before generating the e-mail (Figure 11.10).
www.actix.com
Figure 11.10 E-mail connection confirmation dialog
Pressing Yes on the confirmation dialog will launch the default e-mail application and automatically create and send an e-mail with the information required to create the unlock key. In the e-mail created and sent, a file is attached that contains the information about the users computer that is required to generate the unlock key. Please do not delete this file. Note that if Cellopt AFP is installed on a laptop where the internet connection might vary from time to time - e.g. Ethernet at your desk, 802.11b at home, etc, it is required to request one unlock key for each configuration.
11.5.2 Unlocking Cellopt AFP

Once an unlock key has been requested and the license has been verified by Actix, a file containing the unlock key will be sent to the user. When the user receives the unlock-key e-mail, the user should: Save the attached key file to the user machines hard drive. Start Cellopt AFP. Drag and drop the key file onto anywhere in the Cellopt AFP window, or alternatively, click on the Load key button (see Figure 11.9) to open a file browser to navigate and select the unlock key file. If the key is valid, the word Unlicensed will be removed from the Cellopt AFP title bar. If the key is not recognized as valid, a message stating that fact will be presented.
11.5.3 License Manager Tool

A license administration tool is available from the program menu. It can be used to view a license report (e.g. used for trouble shooting), request a new license and install or delete a license key.
11.6 Troubleshooting
11.6.1 How to check if you have administrative privileges
11.6.1.1 Microsoft Windows 2000
Click the Start button > Programs > Administrative Tools > Computer Management: Expand Local users and groups node. Open users folder. Find your login name and double click on it.
www.actix.com
Look in the members of tab. If the group called Administrators is shown, then you have administrative rights and can install Cellopt AFP 3.9.
11.6.1.2
Microsoft Windows XP
Click the Start button > Control Panel. Double click on User accounts. On the Users tab, under Users for this computer, click the user account name, and then click Properties. On the Group Membership tab, check to see if the other button is selected and administrators is currently showing in the drop-down box. If this is true, then the user will be an administrator and can install Cellopt AFP 3.9.
11.7 Silent Install

It is possible to install the package in a silent mode, i.e. without a user interface, if desired. To launch the silent install, do the following in a console (CMD): msiexec /q /I CellOptAFPInstaller.msi and to uninstall: msiexec /q /x CellOptAFPInstaller.msi
11.8 Cellopt Project Database

The Cellopt AFP projects are stored in a database and for secure database operation, it is strongly recommended that there is twice as much free space on the hard disk compared to the size of the largest project. Each project is stored as a separate folder in the data folder of the db directory. This is usually found in C:\Program Files\ComOpt\Cellopt AFP\3.9\db\data\, if the default installation folder was selected. The database temporarily uses a large amount of disk space during its operation, and if there is no or little disk space left, this can result in the database becoming corrupt. If there is less than 300 MB of free space, a warning is displayed when importing any file. This threshold value can be changed by editing the settings.xml file; see below for details. Note that the performance of the database will decrease with the size of the database. It is strongly recommended to regularly perform verify and if possible repair the database by using the option under the Cellopt AFP control panel to trim the database. See the section about the control panel for details.
11.9 Optimizer Priority

It is possible to run the Cellopt AFP optimizer with a lower priority compared to the client and server processes. The default operation is to have the same priority (normal) for all processes. This can however be changed for the optimizer process by editing the settings.xml file found in the conf folder under the installation folder. This is usually found in C:\Program Files\ComOpt\Cellopt AFP\3.9\conf, if the default installation folder was selected. Change value normal to low in the line: <jvmarg line="-Doptimizer.priority=normal"/>.
www.actix.com
Index 131
12 Index
<
<advanced_rule_properties>, 115 <categories>, 113 <category>, 113 <cellopt_afp>, 107 <colorcode>, 111 <frequency_hopping_gains>, 117 <frequency_hopping>, 116 <frequency>, 111 <frequencygroup>, 112 <frequencygroupentry>, 112 <frequencyplanentry>, 113 <groupentry>, 113 <layer>, 114 <list>, 110 <mal_setting>, 116 <model_settings>, 116, 117 <Model>, 107 <network>, 108 <plan>, 112 <plans>, 112 <radio>, 109 <rel>, 110 <rule>, 114 <rules>, 114 <scaling>, 115 <sector>, 108 <selected_radio>, 108 <selected_sector>, 108 <selected_site>, 107 <selection>, 107 <site>, 108 <spectrum>, 111 <threshold>, 115 asymmetric handover relations, viewing, 57 autofilter, 48
B
Best Choice view, 86 BSIC color codes section Optimize, 101
C
change frequency assignments for radios, 84 Classes dialog, 70 Clear Spectrum List dialog, 60 clearing the spectrum, 77 Color Codes section Analyze, 99 Optimize, 101 Retune, 101 color codes, optimizing, 93 Control Panel, 10 copying a template, 11 Create Distance List dialog, 62 Create Second Order Neighbor List, 64 Create Site Neighbor List, 64 creating a new project, 13 creating a template from a project, 11 creating new lists, 58 creating plans, 82
D
deleting a template, 11 deleting rules, 70 delta report, 82 detailed project overview, 24 Detailed Report view, 81 disabling network elements, 43 distance list generation, 63 Distance List Wizard, 62 diversity gain, 75 DPC, 74 DTX, 74
A
About, 10 Adaptive Multi Rate, 75 Add MAL Length Rule, 31 Add Priority dialog, 71 Add Sector Wizard, 42 adding radios to a sector, 43 adding sectors to the network, 41 adding sites to the network, 41 AMR, 75 Analysis Lists view, 65 analysis report, 79 Analysis view, 65 Analyze Frequencies table, 80 Analyze view, 77 ASSET format, 118 assigning radios to layers, 51
E
editing the relations of sector, 44 Ericsson interference list, 119 Ericsson OSS/BSC formats, 118 event log, viewing the, 16 Export Plan view, 102 Export Project section, 20 Export Project to File, 13 exporting a template, 11 exporting to Excel, 50
www.actix.com
Index 132
F
fast fading diversity gain, 75 File mode, 7, 12 final priority, 70 forbidden frequencies, 77 Frequencies section, 76 Analyze, 77 Optimize, 83 Retune, 84 frequency diversity gain, 75 Frequency Hopping options, 74 frequency optimization, 83 frequency plan, storing, 50
list status color codes, 54 List Status Criteria dialog, 56 list status criteria, editing, 56 List Status view, 54 Lists Manipulation view, 58 lists, creating new, 58 Lists, managing, 58 log file, 10 Logging - displaying the AFP event log, 10
M
MAIO, 88 MAL editor, 29 MAL length, 30 Manipulation view, 58 manual retune, 86 Mobile Allocation Index Offset, 88 Mobile Allocation Lists editor, 29 Modeling detailed project overview, 24 Priorities, 67 modeling and optimization flow, 9 Modeling section, 18, 19 Layers, 44 Lists, 53 Network, 40 Project Overview, 23 Spectrum, 27 monitoring user activities, 10 multiply with traffic, 73 multiply with weight, 73
G
generating a Retune report, 84 generating lists, 58 global set planning strategy, selecting, 33 grouping radios with similar characteristics, 44 GSM color code options, 94 GSM system categories, 51
H
hide projects, 10 hiding columns, 50 hopping radio groupings, 89 Hopping Sequence Number, 88 hopping strategy, 52 HSN, 88 HSN and MAIO section Analyze, 90 Optimize, 92 Retune, 92 HSN planning strategies, 90
N
navigation buttons, 8 neighbor lists, 54 Network view, 40 new lists, creating, 58 New Project, 12 New Project section, 13 Nokia interference list format, 120 Nokia OSS/BSC formats, 118 Normalize List dialog, 61 Nortel OSS/BSC formats, 118
I
iDEN color code options, 98 Import Data section, 21 Import File Wizard, 14 Import Project from File, 13 Import Project section, 19 important rules class, 69 importing a template, 11 input formats, 105 interference lists, 54 interference rules class, 70
O
Open Existing Project, 12 Open Project section, 17 Optimize Frequencies view, 83 Optimize Sync Groups view, 89 optimizing color codes, 93 Options, 10 Options for Frequencies view, 76 Options for HSN and MAIO optimization view, 88 OSS/BSC formats, 118 other lists, 54 output formats, 105
J
Join Lists dialog, 59
L
Licensing information, 10 list analysis report, 66 List Analysis table, 66 list functions, 58 List Generation, 58
www.actix.com
Index 133
P
pivot field selector, 65 pivot function, 78 Planet 2.8 format, 117 Priorities view, 67, 85 prioritization structure, 69 prioritization table, 70 Project Management, 11 link, 13 Project mode, 7, 18, 19, 21 project warnings, activating and deactivating, 10 projects, showing/hiding, 10
Q
QUAD/WiDEN radios, 86 quick import, 14
R
radio database, 15 Radio Editor, 22, 46, 78 additional GSM columns, 51 additional iDEN columns, 53 additional TDMA and PDC columns, 52 Radio Editor data, saving, 104 related radios, selecting, 50 relative amount of interference, 73 relative amount of traffic, 73 relative importance between rules classes, changing, 70 renaming a template, 11 Retune Frequencies view, 84 rule prioritization order, 69
setting the measurement system, 10 show projects, 10 showing columns, 50 Site Neighbor List, creating, 64 source files, specifying, 15 source radio database file, 24 Spectrum page for a GSM project, 27 page for a TDMA or PDC project, 32 Set Template, 34 spectrum clearance, 77 spectrum lists, 53 Start screen, 12 starting AFP, 9 storing radios as a new category, 51 storing the frequency plan, 50 strict rules class, 69 Support, 11 synchronized hopping groups, 89
T
TDMA and PDC color code options, 96 Template editor, 38 Template Management, 11 The Priorities view, 67 traffic load per sector, 74 training sequence codes, 95
U
usage.txt log file, 10 user activities, monitoring, 10
V
viewing a template, 11 viewing network properties, 40 vocoder, 75
S
Save Radio Editor page, 104 saving the radio editor table, 50 Scaling and Threshold properties, 72 Second Order Neighbor List, creating, 64 selecting all radios, 50 selecting radios by file, 50 selecting related radios, 50 Server / Database, 11 Set Template Optimization, 38
W
warnings, 26 weighted priority, 70
X
XML tags, 106 XML-based format, 105
www.actix.com
Index 134
www.actix.com

Cellopt AFP 3.9 User Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cellopt AFP 3.9 User Guide

Uploaded by

Copyright:

Available Formats

AFP

2 GETTING STARTED WITH CELLOPT AFP ..............................................................7

3 FILE MODE .............................................................................................. 12

4 IMPORT DATA .......................................................................................... 21

7 HSN AND MAIO....................................................................................... 88

8 COLOR CODES ......................................................................................... 93

9 EXPORT PLAN ........................................................................................ 102

10 INPUT AND OUTPUT FORMATS ................................................................... 105

11 INSTALLATION/LICENSING AND TROUBLESHOOTING ......................................... 122

12 INDEX ............................................................................................... 131

Actix Cellopt AFP Version 3.9 User Guide

Welcome to Cellopt AFP 6

1 Welcome to Cellopt AFP

Actix Cellopt AFP Version 3.9 User Guide

Getting Started with Cellopt AFP 7

2 Getting Started with Cellopt AFP

2.2 User Interface Overview

File This mode is entered when starting the application.

Project This mode is entered when a project is selected and opened.

Actix Cellopt AFP Version 3.9 User Guide

Getting Started with Cellopt AFP 8

2.3 Appearance and Navigation

Actix Cellopt AFP Version 3.9 User Guide

Getting Started with Cellopt AFP 9

2.4 Modeling and Optimization Flow

Actix Cellopt AFP Version 3.9 User Guide

Getting Started with Cellopt AFP 10

2.5 Control Panel

Figure 2.3 The Cellopt AFP Control Panel.

Actix Cellopt AFP Version 3.9 User Guide

Getting Started with Cellopt AFP 11

Actix Cellopt AFP Version 3.9 User Guide

Figure 3.1 The Start page.

Actix Cellopt AFP Version 3.9 User Guide

3.3 New Project

Figure 3.2 The New Project page.

Actix Cellopt AFP Version 3.9 User Guide

Figure 3.3 The first step in the Import File Wizard.

Actix Cellopt AFP Version 3.9 User Guide

Figure 3.4 The second step in the Import File Wizard.

Actix Cellopt AFP Version 3.9 User Guide

Actix Cellopt AFP Version 3.9 User Guide

3.4 Open Project

Figure 3.6 The Open Project section.

Actix Cellopt AFP Version 3.9 User Guide

Actix Cellopt AFP Version 3.9 User Guide

3.5 Import Project

Actix Cellopt AFP Version 3.9 User Guide

3.6 Export Project

Actix Cellopt AFP Version 3.9 User Guide

4.2 The Import Data tab

Actix Cellopt AFP Version 3.9 User Guide

4.2.1 The Radio Editor tab

Figure 4.2 The Radio Editor tab.

Actix Cellopt AFP Version 3.9 User Guide

Actix Cellopt AFP Version 3.9 User Guide

5.2.1 Detailed Project Overview

Actix Cellopt AFP Version 3.9 User Guide

Actix Cellopt AFP Version 3.9 User Guide

Actix Cellopt AFP Version 3.9 User Guide

5.3.1 Spectrum GSM

Actix Cellopt AFP Version 3.9 User Guide

5.3.2 Frequency Hopping Strategy GSM