Professional Documents
Culture Documents
Cellopt AFP 3.9 User Guide
Cellopt AFP 3.9 User Guide
Cellopt AFP 3.9 User Guide
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
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
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
www.actix.com
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
www.actix.com
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
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
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.
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.
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.
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).
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
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
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
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.
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
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.
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.
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.
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.
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
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
Figure 5.8 The TDMA Spectrum view with Set planning options.
www.actix.com
Modeling 33
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
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
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
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.
Modeling 41
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.
www.actix.com
Modeling 44
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.
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.
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.
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
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):
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.
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.
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.
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.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.
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.
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.
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
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
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
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
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
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
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.
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
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
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
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.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.
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.
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
Figure 7.1 The Options for HSN and MAIO optimization view.
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
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
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
7.4 Optimize
The HSN and MAIO optimization is performed and managed in this view (see Figure 7.3).
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.
www.actix.com
Color Codes 94
www.actix.com
Color Codes 95
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
www.actix.com
Color Codes 97
www.actix.com
Color Codes 98
www.actix.com
Color Codes 99
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
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.
www.actix.com
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
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).
Figure 9.1 The Export Plan view, where frequency, HSN & MAIO and color code plans may be exported to file.
www.actix.com
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
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>.
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]
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_settings>
10.2.3.3
Tag
<selection>
Multiplicity 0.. * 0.. * 0.. * Description Radios of site selected. Radios of sector selected. Individual radios selected.
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]
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]
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]
10.2.3.7
Tag <site> <list>
<network>
Multiplicity 0..* 0..* 0..* Description Sites in the network. Lists. Sector alias maps
<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]
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
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
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]
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]
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]
Tag <rel>
Multiplicity 0..*
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]
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]
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.
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]
10.2.3.18
Tag <plan>
<plans>
Multiplicity 0..* Description Plans in the system.
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.
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]
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]
10.2.3.22
Tag <category>
<categories>
Multiplicity 0..* Description Categories in the system.
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.
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.
<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]
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]
apply_interfered_interfering
separation
www.actix.com
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.
<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]
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]
www.actix.com
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]
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.
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.
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.
10.2.3.36
Attribute Sector_id name
<alias>
Description Sector id. [i] Sector alias name (alternative name). [s]
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.
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.
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.
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.
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
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.
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).
The License Agreement dialog. Please read the agreement before continuing (Figure 11.3).
www.actix.com
The missing third party products dialog, where it is possible to install additional required software products (Figure 11.4).
The Choose installation folder dialog, where the user may select the folder in which to install Cellopt AFP (Figure 11.5).
www.actix.com
The Ready to install dialog, where the user starts the installation (Figure 11.6).
The Installing files progress view showing the progress of the installation using a bar (Figure 11.7).
www.actix.com
The Installation Complete dialog, which is the last screen in the installation process (Figure 11.8).
www.actix.com
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
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.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.
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