TEMS™ CellPlanner 8.

1
Release Note

© Ascom (2009)

Date: 25 June 2009

Document: LZT 108 9841 R2C

© Ascom (2009) All rights reserved. TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.

Contents
1
1.1 1.2

About the 8.1 Release ............................................... 7
TEMS Technical Support web pages...........................................7 Major changes in the 8.1 release.................................................7

2 3
3.1 3.2

TEMS CellPlanner 8.1.2 upgrade matrix .................. 8 Hardware and Software Requirements.................... 9
Minimum requirements ................................................................9 Recommended configuration .....................................................10

4
4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12

New Features in TEMS CellPlanner Release 8.1... 11
LTE – New module in TEMS CellPlanner ..................................11 Evolved HSDPA.........................................................................11 EUL, 5.76 Mbps .........................................................................11 TEMS Investigation 9.1 Interface...............................................12 Demographic Maps and Demographic Reports.........................12 Partial Publish and Refresh .......................................................12 TEMS CellPlanner Server JBoss Integration .............................13 Automatic Queue Evaluator .......................................................13 Enhanced GSM Best Server Coverage Report .........................13 Support Button ...........................................................................14 Repeaters Import and Export.....................................................14 Filter improvements ...................................................................14

5
5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8
© Ascom (2009)

Improvements and changes in release 8.1.0......... 15
New import wizard for map data ................................................15 Display performance of internal vector format (MRV) improved ....................................................................................15 Vector data rasterization improvements ....................................15 Performance improvement for creating project in TEMS CellPlanner server database .....................................................15 Prune DB and Update Statistics functions removed from admin tool ..................................................................................15 Changed default value for WiMAX carrier distance ...................16 Donor cell is no longer assigned automatically when adding radio repeater in project .................................................16 Changed terminology.................................................................16
Document: LZT 108 9841 R2C 2(47)

5.9 5.10 5.11

TEMSlog.xml file removed .........................................................16 New WCDMA demo project .......................................................16 Concurrency Protection .............................................................16

6
6.1 6.2 6.3

Improvements and changes in release 8.1.1......... 18
Support for LTE and TI 9.1 measurements................................18 Support for LTE repeaters .........................................................18 The property panel for height or obstacle maps with threshold renderer has been improved ......................................18

7
7.1 7.2 7.3 7.4 7.5

Improvements and changes in release 8.1.2......... 19
Text export of LSA Polygons .....................................................19 Possibility to change the format of the polygon positions when exporting LSA polygons ...................................................19 Area limit function for LTE DL traffic analysis ............................19 Increased number of decimals in screen statistics report ..........19 Possibility to allocate licenses, on a license server, to a limited group of users ................................................................19

8
8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 8.12 8.13 8.14

Corrections in release 8.1.0 .................................... 20
Area calculation in GSM Coverage Report was sometimes incorrect .....................................................................................20 GSM Interference Report was incorrect.....................................20 The AFP sometimes crashed on Vista.......................................20 The AFP assigned also TCH frequencies even if only BCCH should have been planned..............................................20 The AFP report wrongly reported fixed channel groups for HSN ...........................................................................................20 Global editing of HCS band was not possible............................21 Handover Cursor was missing in GSM ......................................21 Error message when opening OSS-RC GSM Export ................21 Calculation of noise figure for WCDMA cells with radio repeaters was incorrect .............................................................21 Simulation results not updated when re-running WCDMA analysis ......................................................................................21 UL load from best server plot was always 0 after noniterative WCDMA analysis .........................................................21 "Hanging" progress bar during OSS-RC WCDMA Import..........21 OSS-RC WCDMA import sometimes imported more data than the user had selected ........................................................22 Co-sited WCDMA and GSM RBSs displayed under both networks in OSS-RC WCDMA Import comparison window .......22
Document: LZT 108 9841 R2C

© Ascom (2009)

3(47)

8.15 8.16 8.17 8.18 8.19 8.20 8.21 8.22 8.23 8.24 8.25 8.26 8.27 8.28 8.29 8.30 8.31 8.32 8.33 8.34 8.35 8.36 8.37 8.38 8.39 8.40 8.41 8.42 8.43

Cells text file import dialog had contradictory behavior..............22 Cell text import failed to update antenna attributes....................22 Model tuning changed land use correction factors despite no matching samples .................................................................23 AMI failed for partially configured cells ......................................23 XML measurement file did not support non-USASCII characters ..................................................................................23 User interface in Model tuning dialog was misleading ...............23 Pathloss calculation difference for GeoBox data .......................23 Screen statistics for lookup plots sometimes gave incorrect result ..........................................................................................23 Undefined value and 0 mixed up in Screen statistics ................24 Problem with legend in survey files plot in Model tuning when selecting Multi-color..........................................................24 6.25. User specific result calculation directory was lost.............24 Drag and drop in explorers could cause inconsistencies...........24 Site symbols in the network layer became too large..................24 Attribute filter error .....................................................................24 Bin query was affected by filter ..................................................24 User was allowed to create Custom Attributes with empty and/or duplicate names .............................................................25 Flag values in Custom attributes editor were unsorted..............25 Custom attribute map layer could not be exported to vector format.........................................................................................25 Problem when exporting certain type of plots to vector format.........................................................................................25 Zooming was very slow on Vista................................................25 Vector map objects were occasionally invisible in some zoom levels ................................................................................25 Brightness for image exchanged with saturation .......................26 Occasional TEMS CellPlanner crashed when corrupt TABfiles were present.......................................................................26 Conversion of Swiss coordinate system incorrect with the pre-process raster tool if changing coordinate system ..............26 TEMS CellPlanner froze, when checking details on PlaNet map data ....................................................................................26 Google Earth export was not fully functional for all options .......26 Conversion of building data from MapInfo (MIF/MID) did not always work .........................................................................26 Warning messages were missing when importing project XML containing existing coordinate system...............................26 Import of data base project failed when user permissions were included.............................................................................27

© Ascom (2009)

Document: LZT 108 9841 R2C

4(47)

...31 Not possible to run LSA without running iterative analysis ................52 8..................................30 LTE UL total bitrate plot not always selectable in the Result plots window ..........30 10 10........3 9...47 8....44 8.....31 © Ascom (2009) Document: LZT 108 9841 R2C 5(47) ....2 9......................31 User documentation updated..............................28 Default settings for user permissions updated.....................................................48 8..................................................27 Unable to export project to xml from the Server Admin Tool .....................................................1...... 30 The calculation of UL loss for radio repeater in WCDMA analysis was incorrect......28 Incorrectly displayed warning messages when exiting TEMS CellPlanner ......................45 8........46 8.1 9..........8........2 10.................28 Unnecessary information was shown in the Component version info window in 64-bit environment ...........27 Server export and import disregarded “Sites modifiable”........... 31 800 MB limit removed from W2003 server installation...........53 8.........3 10........................27 Consistency check missing for TEMS CellPlanner Server import ...........................28 Server logout caused exception...................................1 ....................................1.......................................................54 8....1 10......................................30 Antenna branches in GSM OL cell template were ignored ......................30 Performance problem when loading large project from the database ...........27 Slow performance when comparing workspaces in TEMS CellPlanner server .....28 Sporadic error messages after closing a project....50 8........5 Corrections in release 8................4 9....................28 Errors in client log when going off-line using project area .......31 The UL noise rise from EUL/HSUPA did not correspond to the UL loading from best server plot ..................................................5 Corrections in release 8...........................................................49 8...........................51 8..4 10...55 Information on supported XML file versions was missing in TEMS CellPlanner server import ..31 Error in LTE DL interference analysis .....2 ......................................................................................29 9 9.........30 LTE manual was not visible .......................................................27 Error when trying to store an offline project that had been deleted in the database ..............

.. 39 Appendix I.......................... 38 Contact information.......................... 41 Additions and clarifications to different parts of the TEMS CellPlanner 8.........47 2 2........1 User documentation .....11 12 13 Known bugs and limitations in release 8.. on a license server...............................................45 Bulk CM bug in OSS-RC R4 affecting import of Feeder cables ...................... to a limited group of users .....2 ............1 User documentation ................................................45 Rules for OSS-RC WCDMA Import into an existing TEMS CellPlanner project .....43 TEMS CellPlanner supports single-byte character sets........................2 2................44 The permissions system is enforced when you make changes that affect other people i........ 40 1 Correction to the Common Features User's Guide.......................................4 2................................................................................................44 Interpretation of ground height............................................................. 33 TEMS CellPlanner product packages ........................... 43 How to allocate licenses......1 2....................5 2.......................................................................................e.....6 2........................................................................... you publish your changes to the main project......7 © Ascom (2009) Document: LZT 108 9841 R2C 6(47) . 40 Addendum Additions to the TEMS CellPlanner 8.........1.............3 2.......43 What could happen if a user takes long time to resolve conflicts in the TEMS CellPlanner Server environment? ....

Tech Support. TEMS CellPlanner provides full support for voice and data services in LTE. For information about previous releases. planning.1 TEMS Technical Support web pages Please visit our Support web site. GSM. and optimizing 2G. since accuracy reduces the number of sites and increases capacity in the network.1 Technical Product Description. Ascom understands this concern and has focused on developing algorithms that generate accurate and proven results. 1. from early planning to the most complex optimization. 2. FAQs and downloads of patch releases. 3G and LTE networks. TEMS CellPlanner can be used in all phases of a radio network’s life cycle. A key concern for the experienced RF network planner is the accuracy of the network design. TEMS CellPlanner provides superior planning and optimization capabilities to save time and money during network deployment.com/tems.5G.1 Release TEMS CellPlanner is an advanced tool for designing.1 release LTE – new module in TEMS CellPlanner Evolved HSDPA support True HSUPA/EUL support TEMS Investigation 8. Developed by Ascom. For more information about TEMS CellPlanner.1 About the 8. please see TEMS CellPlanner 8.1 interface Demographic maps and reports Partial publish and refresh TEMS CellPlanner server JBoss® integration Automatic queue evaluator Enhanced GSM best server coverage report Support button Enhanced performance display for vector data Repeaters export/import Filter improvements © Ascom (2009) Document: LZT 108 9841 R2C 7(47) . WCDMA. and WiMAX and meets the needs of today’s complex radio networks.ascom. for the latest technical information. 1. please refer to the corresponding Release Notes. It features open interfaces and a flexible architecture. www.2 • • • • • • • • • • • • • Major changes in the 8.

© Ascom (2009) Document: LZT 108 9841 R2C 8(47) . TEMS CellPlanner Universal 6. Note: Simplified information model in 7.x New license file needed. Please contact TEMS Sales. TEMS CellPlanner 7. Existing license file can be used. Projects must be exported with the TEMS CellPlanner XML export and imported in TEMS CellPlanner 8.0.1.0.x Existing license file can be used. Please contact TEMS Sales.1. INSTALLED PRODUCTS TEMS CellPlanner 8.2.x and 6.2 TEMS CellPlanner 8.x TEMS CellPlanner 8. Projects must be exported with the TEMS CellPlanner Universal XML export and imported in TEMS CellPlanner 8.2 upgrade matrix LICENSING MIGRATION OF PROJECTS The table below indicates if new licenses are needed and if planning data must be migrated when upgrading to TEMS CellPlanner 8. some attributes from earlier releases are not migrated by the XML export and import.0 and 6.1.1.1. please contact TEMS Support for further information. Please contact TEMS Sales.2.1.1. Please contact TEMS Support.0i New license file needed.x New license file needed.1. In this case.1. Please contact TEMS Support Earlier releases of TEMS CellPlanner Other cell-planning tools Please contact TEMS Sales. TEMS CellPlanner Universal 6.0 and later releases. Projects must be exported with the TEMS CellPlanner XML export and imported in TEMS CellPlanner 8. Please contact TEMS Support.3. Projects stored in a TEMS CellPlanner database can also be migrated by using the “Server Export”. Note: Scenarios are not supported in releases after 6. No actions needed. Projects must be exported with the TEMS CellPlanner Universal XML export and imported in TEMS CellPlanner 8.

up to 500 sites O/S: Windows® XP Professional or Windows® 2003 Server x86 (32bit) Processor: Pentium III 1. up to 500 sites OS: Windows® XP Professional Processor: Pentium III 1.5GHz or higher processor Memory: 1 GB of RAM or higher Server PC: Medium projects.3 Hardware and Software Requirements The following are minimum and recommended configurations for TEMS CellPlanner 8. 3. 500 .3000 sites OS: Windows® XP Professional Processor: Pentium IV 2. 500 .1.5 GHz Memory: 2 GB of RAM Database: Oracle 11g © Ascom (2009) Document: LZT 108 9841 R2C 9(47) .4 GHz Memory: 512 MB of RAM Database: Oracle 11g Client or standalone PC: Medium projects.1 Minimum requirements Client or standalone PC: Small projects.3000 sites OS: Windows® XP Professional or Windows® 2003 Server x86 (32bit) Processor: Pentium IV 2.4 GHz Memory: 512 MB of RAM Server PC: Small projects.

000 – 3. more than 3.000 sites OS: Windows® XP Professional x86/x64 (32 or 64 bit) or Windows® Vista Enterprise/Ultimate/Business x86/x64 (32 or 64 bit) Processor: Intel Core 2 Duo or similar processor Memory: 2 GB of RAM Server PC: Small projects.000 sites or less than 5 users OS: Windows® 2003 Server x86/x64 (32 or 64bit) Processor: Intel XEON or similar processor Memory: 2 GB of RAM Database: Oracle 11g Server PC: Medium projects. more than 5.000 sites or more than 10 users OS: Windows® 2003 Server x64 (64bit) Processor: Intel XEON or similar processor Memory: 8 GB of RAM © Ascom (2009) Document: LZT 108 9841 R2C 10(47) .3. 1.2 Recommended configuration Client or standalone PC: Large projects. less than 1.000 sites or 5 .10 users OS: Windows® 2003 Server x64 (64bit) Processor: Intel XEON or similar processor Memory: 4 GB of RAM Database: Oracle 11g Server PC: Large projects.

cells. TEMS CellPlanner contains a default set of mapping curves that support different channel models and user velocities. the new worldwide standard for mobile broadband. Support for MIMO. Interference and Traffic analysis.1.1 New Features in TEMS CellPlanner Release 8. The tool also provides a flexible LTE frequency band editor which allows the user to define any LTE frequency band and carrier desired.76 Mbps TEMS CellPlanner supports EUL. the user can select an uplink and a downlink mapping curve from C/(I+N) to data rate.4 4. TEMS CellPlanner also supports LTE neighbors display and intratechnology LTE neighbor relations. including the features 64QAM and MIMO. and TMAs. as well as different antenna configurations and transmission modes for the downlink. has been introduced. This feature will double the data rate in P7. The maximum throughput for EUL is now 5. The implementation covers the functionality in WCDMA RAN P7. For every LTE terminal type. MIMO is a technique where two transmitter antennas and two receiver antennas are used to transfer different bit streams on the same frequency. using a pseudo-random distribution to spread the terminals over the map for each trial.1. and the throughput can be up to 28 Mbps. 4. Tx Diversity and SIMO is offered. TEMS CellPlanner also brings support for 10 and 2ms TTI. The outputs of the analysis are quality and data rate plots and reports. feeder cables.2 Evolved HSDPA Evolved HSDPA. © Ascom (2009) Document: LZT 108 9841 R2C 11(47) .3 EUL. The 64QAM modulation technique leads to higher data rates. 4. as well as uplink analysis.1 LTE – New module in TEMS CellPlanner The newest module in TEMS CellPlanner supports LTE. TEMS CellPlanner offers the possibility to model LTE networks containing eNodeBs (LTE RBSs) with sectors. the maximum number of codes are now 4. The uplink analysis contains a Monte Carlo engine that performs several random trials.76 Mbps following the WCDMA RAN P6 and P7 system properties. reaching up to 21 Mbps in P7. 5. The LTE analysis functions in TEMS CellPlanner comprise downlink Best Server. antenna branches. TEMS CellPlanner also brings new coverage probability plots for data rates up to 28 Mbps. Support for LTE repeaters will be available in release 8. antennas.

1. The new choice of the map (land use or demographic) is added to the existing coverage report. It is possible to create a report for GSM best server using a demographic map defined in the project. where the demographic map can be chosen instead of the land use format.6 Partial Publish and Refresh The TEMS CellPlanner server now supports the ability to select which changes to publish when publishing changes from the private workspace to the main workspace. The existing WCDMA Pilot report is extended with a map choice. Demographics maps (or demographic data) refer to a selected population characteristic as used for governmental purposes. In TEMS CellPlanner 8.1. 4. marketing.5 Demographic Maps and Demographic Reports Demographic maps are introduced in TEMS CellPlanner 8. the possibility to select which changes to refresh from the main workspace to the private workspace is now included. Sites with relationship to the selected sites will automatically be selected as well. At the same time.1 Interface TEMS CellPlanner has a natural interface with TEMS investigation.4. When the demographic map is chosen the new demographic report for the Pilot is created. © Ascom (2009) Document: LZT 108 9841 R2C 12(47) .1 demographic data can be: • • Displayed as a map layer thus allowing visual analyses Used to create coverage reports TEMS CellPlanner 8. These selections are made at the site level. Each demographic category has its own report sheet. 4. Each demographic category has its own report sheet for best server cells. or opinion research.4 TEMS Investigation 9. allowing the user to import log files from TEMS Investigation 9.1 also has support for importing demographic data from various sources to the TEMS CellPlanner internal format.

called the Automatic Queue Evaluator. The server’s logging system allows detailed customization of what and how logging information is handled and stored. where resources are limited. When enabled. The evaluator optimizes the number of concurrent operations with current load on the TEMS CellPlanner server.4.9 Enhanced GSM Best Server Coverage Report The report for GSM best server coverage has a new layout and the cell information is presented on its own sheet. No queue evaluator is enabled by default because most installations don't need any queue management. save.8 Automatic Queue Evaluator TEMS CellPlanner 8. © Ascom (2009) Document: LZT 108 9841 R2C 13(47) . This means that the TEMS CellPlanner server can be deployed. run and managed in the same way as many other modern enterprise services are managed today.1 introduces a new version of queue handling for user operations (load. this version of queue handling adapts to changes in resource allocation and projects size. 4. 4. For some installations. The server can be remotely managed and monitored using the JMX (Java Management Extensions). In this case please contact the TEMS support for guidelines on how to enable and configure the queue systems. which enables the system administrator to set system parameters and check the health of the server using off-the-shelf management tools or the integrated JMX console. the queue system can be used to avoid overloading the TEMS CellPlanner server. refresh etc. This enables integration of the TEMS CellPlanner server into a data center solution. publish.). The manual Queue evaluator (also called FIFO Queue evaluator) is the other available version where the users can manually set the maximum number of concurrent operations in the TEMS CellPlanner server.1 server has been integrated with the JBoss application server. within the configured safety limits.7 TEMS CellPlanner Server JBoss Integration The TEMS CellPlanner 8.

12 Filter improvements Area and group filter The area and group filters have been extended. The areas or other filters can then be further grouped into several hierarchical levels where "AND" and "OR" operators can be applied between the groups (several areas can be combined into union areas and/or intercept areas). this new function can also collect and compress project files and log files automatically. at a location specified by the user. buttons. thus defining the desirable range where the sites within that range will be inside the filter. and control keys are now available for dealing with filters. 4. The user can manually fill in a position and radius to be searched. Latitude and Longitude Position attributes are now supported and can be included in the filter. Attribute filter It is now possible to select case-sensitive or non-case sensitive searches when searching text attributes.4. Clicking on the support button produces a number of readable text files. or get the position directly from the map by clicking on the map window. 4. New options make it possible to select several areas or other filters to be included in a group filter.11 Repeaters Import and Export The Cell Text Import and Export functions have been extended to include Radio repeaters. popup menus. with settings and environment information.10 Support Button The new support button provides the customer with a flexible and convenient way to provide information to the support team about many aspects and settings of TEMS CellPlanner. © Ascom (2009) Document: LZT 108 9841 R2C 14(47) . Import/export filters from Excel The Excel file format is now supported for import and export of site and cell filters. These files are then sent to a designated support mail address given by the support member. Usability improvements such as drag and drop functionality. If desired. The customer will also be able to add a detailed problem description and any other information that may be helpful for the support team. Several of these filters can be included in an Excel document with a sheet for each filter.

4 Performance improvement for creating project in TEMS CellPlanner server database The creation of a project in TEMS CellPlanner server data base now takes considerably shorter time than in previous releases.2 Display performance of internal vector format (MRV) improved Display performance of internal vector format. The 'Update Statistics' function is available in Oracle and can be executed by the Oracle administrator. The ‘Prune DB’ function was intended to remove all unused objects from the database. MRV. 5. 5.1. 5. This avoids some minor anomalies for example when importing building data in vector formats. The wizard is straight-forward and easy-to-use.1 Improvements and changes in release 8. The Import wizard guides the user to convert different map data formats to internal formats used by TEMS CellPlanner. © Ascom (2009) Document: LZT 108 9841 R2C 15(47) .5 Prune DB and Update Statistics functions removed from admin tool The utility functions 'Prune DB' and 'Update statistics' have been removed from the admin tool.0 New import wizard for map data The old map import tool (File->Map data->Import/Transformations) has been replaced by an import wizard (File->Map data->Import wizard). 5. has been substantially improved.5 5. Unused data is cleaned up automatically during a migration to a new version of TEMS CellPlanner and therefore the 'Prune DB' is not needed.3 Vector data rasterization improvements The algorithm for rasterizing vector data when importing has been improved for better precision.

and potentially corrupting it. 5. If a client is trying to open a project file currently in use by another client. in order to confirm to 3GPP standard names. Server name. In earlier releases different names (Server. Description) were used for the same parameter in the different windows displayed at login to TEMS CellPlanner Server.9 TEMSlog. 5. 5.25 MHz to 3. 5.10 New WCDMA demo project The WCDMA demo project has been updated.n81) is now locked by the TEMS CellPlanner client when opened in order to prevent other TEMS CellPlanner clients from updating it simultaneously. which matches the default bandwidth. All of these names are now renamed to "Server nickname".5 MHz. "Carrier number" has been renamed to "ARFCN" in GSM windows and to "UARFCN" in WCDMA windows.11 Concurrency Protection Project File Concurrency Protection The project file (. Now the donor cell has to be assigned manually by the user. 5.5.6 Changed default value for WiMAX carrier distance The carrier separation for the default WiMAX frequency band has been increased from 0.7 Donor cell is no longer assigned automatically when adding radio repeater in project The donor cell is no longer assigned automatically when adding a radio repeater in the project.8 Changed terminology The term "reference system" has been changed to "coordinate system" in the TEMS CellPlanner user interface. The plain text variant fulfills the purpose.xml file removed The XML variant of the log file was considered superfluous and is no longer generated. the second client will be notified. © Ascom (2009) Document: LZT 108 9841 R2C 16(47) .

and potentially corrupting it. If a client is trying to open an AMI database currently in use by another client. © Ascom (2009) Document: LZT 108 9841 R2C 17(47) . the second client will be notified.AMI Database Concurrency Protection The Automatic Measurement Integration database file is now locked by the TEMS CellPlanner client using it in order to prevent other TEMS CellPlanner clients from reading or updating it simultaneously.

6.1 are supported as well.1.1 Improvements and changes in release 8. 6.4 and TEMS Automatic 7.1.6 6. Log files from TEMS Pocket 6. Checkbox for transparency above Text field for input of the value above which values are displayed transparent Checkbox for whether this value should be fetched automatically from the threshold table or manually input.1. If the desired legend behaviour should appear all four checkboxes should be selected. The following types of measurements can be imported: • • • GSM: UE mode.1 measurements TEMS CellPlanner 8. © Ascom (2009) Document: LZT 108 9841 R2C 18(47) . CPICH scan (UE or dedicated scanner) LTE: scanner mode (dedicated scanner only) Log files from TEMS Pocket and TEMS Automatic are imported through the same procedure as log files from TEMS Investigation.2 Support for LTE repeaters LTE radio repeaters are now supported.3 The property panel for height or obstacle maps with threshold renderer has been improved In the property panel for threshold renderer there is now the following additional input fields: • • • • • • Checkbox for transparency below Text field for input of the value below which values are displayed transparent Checkbox for whether this value should be fetched automatically from the threshold table or manually input. CW scan (UE or dedicated scanner) WCDMA: UE mode.1 supports TEMS Investigation versions up to 9.1 Support for LTE and TI 9.

chapter 2 Additions and clarifications to different parts of the TEMS CellPlanner 8. 7.4 Increased number of decimals in screen statistics report The number of decimals in the screen statistics report has been increased from two to five.2 Possibility to change the format of the polygon positions when exporting LSA polygons It is now possible to select output coordinate format for LSA polygons in the cell text and generic text exports.1 Improvements and changes in release 8. latitude.1.1 User documentation. Max 15 vertices per polygon are exported. due to their coverage area extending beyond the cluster being analyzed. longitude or longitude. There is an option of selecting coordinate system. 7. © Ascom (2009) Document: LZT 108 9841 R2C 19(47) . on a license server. 7.3 Area limit function for LTE DL traffic analysis The LTE downlink traffic analysis has been extended with a possibility to limit the traffic to a user-specified polygon. on a license server.2 Text export of LSA Polygons The possibility to export LSA Polygons in tab separated text format has been added. This can be used to avoid overestimated traffic load on border cells. latitude.5 Possibility to allocate licenses. to a limited group of users It is possible to allocate licenses. 7.7 7. A description of how to do this is found in this document Appendix 1. to a limited group of users. coordinate format and the order of the coordinates within a point.

5 The AFP report wrongly reported fixed channel groups for HSN In the AFP report. this has been fixed: under the policy "Keep". However.1. the areas specified for the interference categories in the GSM Interference Report were half the correct value. however.0 and is now corrected.3 The AFP sometimes crashed on Vista In some rare cases. the report would indicate two square kilometers below twelve dB C/I. the AFP crashed on Windows Vista systems. the report gives correct area figures.0 used to assign a frequency even under the "Keep" policy.1 Corrections in release 8. if four square kilometers were below twelve dB C/I. 8.8 8. was correct. 8.0 release.1.4 The AFP assigned also TCH frequencies even if only BCCH should have been planned In the AFP. For TRXs with this policy. For example. the AFP should not change existing frequency allocations. An error has been found in the GSM coverage report. 8.1. in the special case where a TRX does not have a current carrier assignment. and it was superfluous to have both policies available. the AFP in release 8.0 Area calculation in GSM Coverage Report was sometimes incorrect This chapter includes corrections made in the 8.2 GSM Interference Report was incorrect In previous TEMS CellPlanner versions. one of the available planning policies is "Keep". The area calculation has been updated. The total area. the policy "Keep" had the same effects as the policy "Plan unallocated". In TEMS CellPlanner 8. The report was always created for the first area in the list of available areas regardless of selection. In some cases. the calculated area for cells was incorrect.1. Therefore. This error was introduced in release 8. In TEMS CellPlanner 8. carrierless TRXs stay carrierless. © Ascom (2009) Document: LZT 108 9841 R2C 20(47) . This has been corrected. 8. the HSN number is replaced by a '-' when the channel group is non-hopping.

8 Error message when opening OSS-RC GSM Export If the coordinate reference system used during the last OSS-RC GSM Export had been modified (removed or its name changed). This problem is now fixed. This is now corrected. the progress bar reached 100% much too early. 8. making it possible to use plots such as number of connected/blocked users and UL / DL load plots.6 Global editing of HCS band was not possible Now it is possible to select HCS band for global editing. the plots displayed in the map window were sometimes not updated correctly. and the export worked anyway. the old cell statistics was deleted (output from previously run MonteCarlo analysis). long before the import was actually finished. The error was harmless. 8. This problem has been corrected.11 UL load from best server plot was always 0 after non-iterative WCDMA analysis In non-iterative mode in WCDMA analysis.8. 8. so the progress bar reaches 100% when the import is actually finished. 8.10 Simulation results not updated when re-running WCDMA analysis When re-running the WCDMA analysis.7 Handover Cursor was missing in GSM The handover cursor button in left toolbar was missing in installations with only GSM license. For most configurations the donor cell's noise figure was underestimated in earlier releases. © Ascom (2009) Document: LZT 108 9841 R2C 21(47) . 8.9 Calculation of noise figure for WCDMA cells with radio repeaters was incorrect The noise figure calculation for UL in Utran cells with radio repeater(s) has been corrected. an error message appeared in the log when opening the OSS-RC GSM Export window. Now the cell statistics is maintained. 8. The unnecessary error message has now been removed from the log.12 "Hanging" progress bar during OSS-RC WCDMA Import When using a large import file and/or a large project during OSS-RC WCDMA Import.

it is sometimes necessary to import even cells that the user has not selected.16 Cell text import failed to update antenna attributes Cell text import failed to update antenna attributes (antenna type. this rule was taken too far and even neighbors of neighbors. which meant that sometimes a lot more objects were imported than the user had originally selected. In the previous release. electrical tilt) in case the antenna already existed. 8. etc. update existing cells only" and "Prompt before overwriting" boxes are selected in the "Cell text file import" dialog. position. then the OSSRC WCDMA Import comparison window displayed both RBSs and antenna equipment under both the GSM and the WCDMA networks. so the WCDMA RBS and its antenna equipment is now only displayed under the WCDMA network and the GSM RBS and its antenna equipment is only displayed under the GSM network. the “Overwrite cells” prompt is now only displayed for the cells that are to be modified. were included.13 OSS-RC WCDMA import sometimes imported more data than the user had selected The OSS-RC WCDMA Import comparison window allows the user to select which new or modified objects to import from OSS-RC into the TEMS CellPlanner project. mechanical tilt. height AGL. but not any second. ground height. 8. in case a selected cell has neighbors among the unselected cells.or higher-degree neighbors. This problem has been solved.15 Cells text file import dialog had contradictory behavior When the "Do not create cells. This problem is now fixed.14 Co-sited WCDMA and GSM RBSs displayed under both networks in OSS-RC WCDMA Import comparison window If a WCDMA and a GSM RBS were placed on the same site. Because of neighbor relations. the “Overwrite cells” prompt was still displayed for the cells that were not going to be created. so that only the immediate neighbors of the selected cells are imported.8. © Ascom (2009) Document: LZT 108 9841 R2C 22(47) . beam direction. This has been corrected. 8. This is corrected. and their neighbors.

This problem has been corrected.8. it looked like the Coordinate system was selectable for XML measurement survey files. 8. a clearly visible but non-significant difference could be observed in the pathloss results when using GeoBox raster data compared to when using MRR raster data.17 Model tuning changed land use correction factors despite no matching samples Propagation model auto tuning sometimes modified clutter codes for which there were no measurements.22 Screen statistics for lookup plots sometimes gave incorrect result If an element name in the legend for a lookup plot contained a number. This has been corrected. 8. 8. 8. It is recommended to use MRR format for performance reasons. This reflects the actual behavior. © Ascom (2009) Document: LZT 108 9841 R2C 23(47) . This has been corrected and the file is now supporting UTF-8 as indicated in the XML header.20 User interface in Model tuning dialog was misleading In the Model tuning dialog. Correction factors for clutter codes with no matching measurements now remains untouched after auto tuning. The Coordinate reference system panel is now grayed out and fixed to WGS84 for XML survey files.18 AMI failed for partially configured cells If a cell without propagation model existed on a position/height/frequency where measurements existed.21 Pathloss calculation difference for GeoBox data When calculating pathloss using a lower resolution than the original resolution. This has been corrected. The pathloss calculation based on GeoBox data is now aligned with the pathloss result from the standard format MRR.19 XML measurement file did not support nonUSASCII characters The XML measurement file. did not support international characters. AMI crashed and could not be used until the cell had been assigned a propagation model. 8. statistics was calculated incorrectly. created when pressing Save for a measurement file in the Model tuning dialog.

29 Bin query was affected by filter The map window filter is now not applied to Bin Query anymore.23 Undefined value and 0 mixed up in Screen statistics The function Screen statistics gave strange results for some plots since undefined value and value 0 were added together.25 6.27 Site symbols in the network layer became too large Site symbols in the network layer became too large on standing screens (larger height than width). the inconsistency errors were reported. User specific result calculation directory was lost When changing the project name the calculation result directory setting was lost and had to be defined again. 8. This is now corrected. some drag and drop operations could cause that inconsistent data was stored in the database. This problem has been corrected.28 Attribute filter error TEMS CellPlanner displayed an error message when an attribute filter was defined using the Position attribute. This bug has been corrected.8. enabling cell names outside filter to be displayed in bin query. This has now been corrected. This has been corrected.26 Drag and drop in explorers could cause inconsistencies Due to a bug in the drag and drop functionality in explorers. A position filter with no area will block everything when "inside" option is selected and pass everything when "outside" option is selected. 8. When opening the stored project. 8. © Ascom (2009) Document: LZT 108 9841 R2C 24(47) .24 Problem with legend in survey files plot in Model tuning when selecting Multi-color The appearance and behavior of the legend has been corrected for this case. 8. but without selecting any area.25. 8. 8.

8. © Ascom (2009) Document: LZT 108 9841 R2C 25(47) . 8. such as very slow zooming under Windows Vista. but generally not recommended. the graphics performance feature DirectDraw was enabled or disabled depending on the installed graphics hardware. to activate DirectDraw manually using the Application Preferences tool. The reason for this was that the “Transparent above” and “Transparent below” limits were not taken into account by the export. composite coverage) to a vector format (e.8. 8. A limitation exists in this feature and is described in the chapter Known bugs and limitations. This problem has now been fixed. while causing rather serious problems on some systems. 8.30 User was allowed to create Custom Attributes with empty and/or duplicate names It is no longer allowed to create a Custom Attribute without a name. A unique name must always be specified when creating a new Custom Attribute in the System Explorer.34 Zooming was very slow on Vista In previous TEMS CellPlanner releases. sometimes produced a result that looked different from the original plot. The reason is that it has relatively minor performance effects.31 Flag values in Custom attributes editor were unsorted Flags are now sorted in lexical order when applying changes in custom attribute editor (System explorer).35 Vector map objects were occasionally invisible in some zoom levels The problem could be observed while panning in the overview map window using the supplied world map.g. This problem has been fixed.g. It is now disabled by default.32 Custom attribute map layer could not be exported to vector format Enabled possibility to export the Custom attribute map layer also to vector file formats. Previously only image file formats were supported. nor is it allowed to have two Custom Attributes with the same name. which made the resulting plot appear larger (cover more area) than the original plot. 8. MapInfo). It is possible.33 Problem when exporting certain type of plots to vector format Exporting certain type of plots (e.

36 Brightness for image exchanged with saturation Brightness and saturation is now working properly with image maps.37 Occasional TEMS CellPlanner crashed when corrupt TAB-files were present If the user selected a map and there were corrupt or incomplete TAB files (MapInfo) in the directories where TEMS CellPlanner was searching for map data.38 Conversion of Swiss coordinate system incorrect with the pre-process raster tool if changing coordinate system A problem with incorrect map data conversion (boundary and re-projection problem) which occurred when importing map data from Swiss coordinate system to another coordinate system has been solved. 8. This is now corrected.41 Conversion of building data from MapInfo (MIF/MID) did not always work All buildings from the MapInfo (MIF/MID) source data will now be converted into the internal MRR format.39 TEMS CellPlanner froze.40 Google Earth export was not fully functional for all options When exporting areas to Google Earth using the Entire layer area or Visible map area option. 8. when checking details on PlaNet map data A problem has been fixed causing TEMS CellPlanner to freeze when trying to check detailed information regarding PlaNet elevation and clutter map layers. 8. 8.42 Warning messages were missing when importing project XML containing existing coordinate system When you import a project with a coordinate system that already exists in EriMap but with a different name. 8. the area polygons were shifted. a message is displayed saying that the existing coordinate system will be used.8. 8. © Ascom (2009) Document: LZT 108 9841 R2C 26(47) . This problem has been fixed. TEMS CellPlanner could crash without notice.

8. This performance problem has been solved.46 Server export and import disregarded “Sites modifiable” The global permission flag “Sites modifiable” was not included in the Server XML export and import. 8. 8. This is now corrected.45 Consistency check missing for TEMS CellPlanner Server import The same consistency check that is used when creating projects in the client is now performed for the server import.48 Slow performance when comparing workspaces in TEMS CellPlanner server Comparing two workspaces could in some cases result in very bad performance.47 Unable to export project to xml from the Server Admin Tool A problem with exporting XML project files. the consistency check reported 'core consistency' problems. 8. This problem was only present in TEMS CellPlanner 8. informing about the currently supported XML versions.0. using the Server Admin Tool has been solved.2.0. This problem is now fixed so the TEMS CellPlanner client now imports xml projects exported by the server correctly. This happened if a lot of data was deleted or added in the private workspace compared to the main workspace.8.1 and 8.44 Information on supported XML file versions was missing in TEMS CellPlanner server import There is now a Supported version panel that is used in both the client and server import.43 Import of data base project failed when user permissions were included After importing a project xml file in the client generated by the server export function in the admin tool. 8. © Ascom (2009) Document: LZT 108 9841 R2C 27(47) .

53 Server logout caused exception In previous releases. This happened more often with large projects. a warning message appeared incorrectly. This has now been fixed.8. unnecessary and there was no problem with the project. TEMS CellPlanner asked if user wanted to save or store the project even if it was not modified when logging out from TEMS CellPlanner server. sometimes quite many of them.52 Sporadic error messages after closing a project Unexpected error messages were sometimes shown when closing a project or loading a project when another project had previously been loaded. They were. This problem has now been corrected. after logging out from the server. 8. so no message appears if the logout and exit has been performed correctly.50 Default settings for user permissions updated The default setting has been changed so that only groups with administrator permission get the 'delete projects' as default. there may have been error messages generated in the TEMS CellPlanner client log. so the user is presented with a proper information message that the database project has been deleted.54 Incorrectly displayed warning messages when exiting TEMS CellPlanner In some cases when a user tried to exit from TEMS CellPlanner. 8. an internal error message was displayed.49 Error when trying to store an offline project that had been deleted in the database If the user tried to store an offline project back to the database and the project had been deleted in the database. 8. even if the project was already closed. These unnecessary error messages have been removed now.51 Errors in client log when going off-line using project area When saving a workspace offline and a project area is defined that does not contain all sites in a project. however. This has now been fixed. 8. This has now been corrected so that TEMS CellPlanner only ask if the project is actually modified. © Ascom (2009) Document: LZT 108 9841 R2C 28(47) . The message asked if the user wanted to save the project named 'NULL'. 8.

© Ascom (2009) Document: LZT 108 9841 R2C 29(47) .55 Unnecessary information was shown in the Component version info window in 64-bit environment When running in a 64-bit environment.8.dll) was erroneously included in the Component version info window. This file is not used by TEMS CellPlanner when running in 64-bit environment and has now been removed from the Component version info in the 64-bit version. one file (FileInfoJni.

the plot is now available for every traffic case. The attenuation of the pickup antenna was used instead of the attenuation of the service antenna. the corresponding LTE UL total bitrate plots was only available for one of the traffic cases.4 Performance problem when loading large project from the database In some cases it could take a long time to load large projects from the database.1.1 The calculation of UL loss for radio repeater in WCDMA analysis was incorrect This chapter includes corrections made in the 8.1.1 Corrections in release 8.9 9. © Ascom (2009) Document: LZT 108 9841 R2C 30(47) . 9. This has now been corrected. 9.1. The calculation of RX attenuation for a radio repeater's service antenna was incorrect in the WCDMA analysis.3 LTE manual was not visible The LTE manual was not available from the Help menu in TEMS CellPlanner or from the Start button. This has been corrected.5 LTE UL total bitrate plot not always selectable in the Result plots window When using LTE UL analysis with two or more traffic cases. This has now been corrected. 9. This occurred when the project contained large site or cell filters.1. This has been corrected in TEMS CellPlanner 8. This problem has now been solved. the antenna branches of the OL cell were not created.2 Antenna branches in GSM OL cell template were ignored When a multiband OL/UL GSM cell was created from a cell template. 9.1 release.

1. section "Environment Variables in Citrix Environment".2 800 MB limit removed from W2003 server installation This chapter includes corrections made in the 8. This limit is now raised to 1200 MB. This has been corrected by adjusting the data rate mapping tables. This has now been corrected. 10.5 • User documentation updated The manuals have been updated. The value was only from the last trial and not a mean of all run trials. In earlier releases an 800 MB primary memory allocation limit had to be enforced on the 32 bit Windows 2003 server operative system. has now been corrected to show the correct target folder.1.10 10. with among others the following: LTE data rate mappings incorrect The LTE User's Guide did not correctly show the supported antenna configurations and UE speed for all channel models.4 Not possible to run LSA without running iterative analysis Previously the LSA algorithm could only be used if Monte Carlo and plots were selected in WCDMA analysis. This change also affects the EUL SIR plot and EUL data rate plot since same power value of was used in those calculations. Document: LZT 108 9841 R2C 31(47) • © Ascom (2009) . 10.3 Error in LTE DL interference analysis There was an error in the interference analysis which gave more impact to terminal Rx loss values than intended. The Installation Guide.0 the default target folder for Citrix users was changed. This has now been corrected. The Installation Guide showed wrong folder for Citrix users In TEMS CellPlanner 8.2 The UL noise rise from EUL/HSUPA did not correspond to the UL loading from best server plot In WCDMA analysis. 10. 10.1. the EUL noise rise plot sometimes showed a different value from the noise rise value used in UL load plot found within WCDMA analysis best server plots.1 Corrections in release 8.2 release. but the Installation Guide was not updated accordingly. It is now possible to run the LSA algorithm without running iterative analysis. The reason for this was an incorrect value of total received power in the EUL noise rise calculation.

• • © Ascom (2009) Document: LZT 108 9841 R2C 32(47) . The chapter has been corrected from 3. and that the Eb/Io value also depends on the frequency band and the service type. Scale factor unit description corrected The scale factor units were incorrectly described in chapter "Traffic Modeling" in the Common Features Technical Reference Manual. in a new section named "Modeling Multi-RABs". and an example of calculating subscriber density has been added.3 and onwards. A brief explanation has now been added to the WCDMA User's Guide.• How to model Multi-RABs was not explained The modeling of multi-RABs. Eb/Io and ASE parameter dependencies have been clarified in manuals The WCDMA User's Guide and the WCDMA Technical Reference Manual now explain that appropriate values for Eb/Io and ASE depend on the system release version. or combined bearers. was not described in the WCDMA manuals.

The memory problem occurs only if the CPLM was created for the whole network without the filter.2 Database migration Database users must read the Database migration chapter in the Installation guide before starting the new installation to avoid loosing data. • Out of memory during WCDMA analysis When running WCDMA analysis on a very large network (more than 10 000 cells).0. This is needed in order for the AMI plots to align with pathloss plots.11 • Known bugs and limitations in release 8. Workaround: Re-run CPLM analysis with a smaller number of cells using the same filter as for the WCDMA analysis. Workaround: The CPLM parameters "Max delta pathloss" and "Max number of cells" should be increased. The reason is that CPLM discards cells with high pathloss relative to the cell with the least pathloss. since they are all threshold plots. the coverage plot for a particular frequency has holes around sites not using that frequency.1 or 8.2. The database server export from the. • AMI plots showing measurements not aligned with actual measurements AMI plots displaying locations for measurements are deliberately displaced by half a bin. This limitation leads to that it is not possible to create screen statistics for Custom attribute plots. If you are going to migrate from any of those versions please contact TEMS support for further instructions. • Drag and drop of radio repeaters for GSM and WCDMA Drag and drop of sites containing radio repeaters for GSM and WCDMA will cause errors in Project consistency check. the WCDMA analysis could crash with an “Out of memory” error even when a filter is applied. • Screen statistics for threshold plots disabled Screen statistics has been disabled for threshold plots due to vastly erroneous result. Workaround: Avoid using drag and drop of sites with repeaters.0. User Administration tool does not work properly when exporting from TEMS CellPlanner 8. © Ascom (2009) Document: LZT 108 9841 R2C 33(47) . • Coverage holes close to sites in multi-carrier WCDMA networks In multi-carrier WCDMA networks.1. which limits the number of cells included in the WCDMA analysis.

Importing a large OSS-RC file into a new (empty) project does not require as much memory as if both the import file and the target project are relatively large and it can be sufficient with the 32-bit version of TEMS CellPlanner.• Out of memory during OSS-RC WCDMA Import In 32-bit version of TEMS CellPlanner. the OSS-RC WCDMA import may run out of memory. the Preprocess vector data window cannot be opened again. pixels with code 255 in the PlaNet backdrop are incorrectly converted to transparent in TEMS CellPlanner. Workaround: Import PlaNet backdrop data as file through the Import wizard instead. This error is harmless and does not affect any TEMS CellPlanner functionality. Possible workarounds: • • • Run Import to neighbor list one more time. the solution is to run TEMS CellPlanner on a 64-bit operating system with sufficient amount of memory. Workaround: Restart TEMS CellPlanner. which is seen as a high negative value. © Ascom (2009) Document: LZT 108 9841 R2C 34(47) . • Error in log after using Import to neighbor list In some cases. • WiMAX utilization % values are not correct Using a traffic demand mix with extremely high traffic density and/or scale factor values can result in overflow in the utilization for a cell. after using If Analysis->Neighbor list->Import to neighbor list. if both the import file and the target project are relatively large (a couple of thousand sites each). • Preprocess vector data window cannot be opened a second time After preprocessing PLANET vector data to MRV. an error appears in the Log saying “Error when saving metadata”. Erroneous pixels in preprocessed Planet backdrop images When importing PlaNet backdrop data to internal TEMS CellPlanner format (MRR) through the Preprocess raster data function. start the Application Preferences utility and make sure that “Max Memory Allocation” for the Client Application is set to the maximum possible (1200 MB for 32-bit TEMS CellPlanner). Note that TEMS CellPlanner must be restarted for the change to take effect! If the OSS-RC WCDMA import still runs out of memory. Workaround: Before running OSS-RC WCDMA import. OR Run Analysis->Neighbor list->Generate neighbor list before running Import to neighbor list.

In some systems it always works the first time. MapInfo) the error message “Export Error…. sometimes produce a result that looks different from the original plot.• Occasional error when exporting Network layer as vector file When exporting the network layer as a vector file (e.Cannot create exporter” may appear occasionally. pan. the correct symbol will be displayed for the site. In this case the indication is incorrect for the newly created site. This happens when there is coverage holes present in the plot in TEMS CellPlanner. • Partial publish fails when interfered by another user If one user has modified an object. zoom.g. Workaround: The first user has to restart the partial publish. • Newly created sites marked as non-modifiable in site explorer If you create a new site and store the project on the CellPlanner server with permissions activated.g. Workaround: Retry the export.g. you may get a red cross symbol in the site explorer. Workaround: Do not zoom or pan in the map window while a print operation is in progress. The system is working correctly and after publish. Workaround: Wait for the print preview to draw completely before doing operations on the map windows (clicking in it. indicating that the user is not allowed to modify a site. display plot etc). © Ascom (2009) Document: LZT 108 9841 R2C 35(47) . composite coverage) to a vector format (e. the partial publish for the first user will fail with a "NullPointerException". • Print preview window occasionally distorted The print preview window can be drawn incorrectly when drawing in the normal map window interferes. Export of coverage holes in the plots to vector format is currently not supported and the holes will not be present in the exported plot. This will be fixed in a future release of TEMS CellPlanner. in some systems always the second time and on some system you must retry a number of times before it finally succeeds. MapInfo). another user has deleted the same object and both of them are doing a partial publish at the same time. • Problem exporting certain type of plots to vector format Exporting certain type of plots (e. • TEMS CellPlanner occasionally hangs while printing map TEMS CellPlanner may stop responding if printing a map while at the same time zooming or panning in the map window.

and the fraction of the time while this is the case is reported as the Activity factor. This script is normally used to merge several antenna types with one electrical tilt lobe each into one antenna type with multiple electrical tilt lobes. The channel is switched on only when there is data to transmit. which are visible through the current project filter. • Change of project filter may cause problem A consistency check is now performed behind the scenes when saving to the database. • WCDMA Statistics is only counted for best-serving cell Statistics only counts admitted users and blocking reason on a cell for those users having cell as best cell. • HS-DSCH power in the statistics report is not correct in spite of low/high traffic demand mix The HS-DSCH power shown in the HSPA statistics report is the power transmitted while the HSDPA channel is switched on. The script will be corrected in a drop release. Hence. This can give inconsistency between connected and blocked users in statistics. to calculate the average power (in W) used by the HS-DSCH.1. If the project filter is changed without first saving done changes to the database. this check only applies to objects. • OSS-RC import sometimes finds too many differences when comparing import file and the TEMS CellPlanner project The comparison between objects in the Compare Workspaces and OSSRC import can sometimes report differences between objects because of precision differences in floating point attributes like power setting for channels. © Ascom (2009) Document: LZT 108 9841 R2C 36(47) . • WCDMA Analysis: The number of blocked multi-rate users can be too high in some cases The number of blocked multi-rate users can be too high if the number of multirate users is higher than the admission SF threshold for lowest bit rate. However. inconsistency might go undetected and possibly causing problems in the server later.• Script antenna_type_util does not work The J-Python script antenna_type_util. while congestion control. in some cases. Workaround: Avoid changing the project filter while having unsaved changes. Workaround: Set a higher SF threshold for SF used in lowest bit rate for multirate bearers. This means that too many decimal digits are considered when comparing these kinds of values this will be addressed in a future release.py does not work in TEMS CellPlanner 8. apply blocking for users in handover also. you must multiply the reported HS-DSCH power (converted to W) by the Activity factor.

E. regardless of the chosen Carrier mapping. This works properly the first time the option is selected for a project. 6 resource blocks corresponds to a Carrier bandwidth of 1. change to another Carrier mapping and then switch back to the preferred Carrier mapping.• Option "Sites modifiable" not reliable In the TEMS CellPlanner administration window. © Ascom (2009) Document: LZT 108 9841 R2C 37(47) . the initial value for the Carrier bandwidth is 5 MHz. Selecting this option should automatically enable the modify/delete sites permissions on all sites for that project. • Missing initial correlation between Number of resource blocks and Carrier bandwidth When adding an LTE frequency band. Workaround: To get the correct Carrier bandwidth. There is a correlation between the number of resource blocks (in Carrier mapping) and the Carrier bandwidth. the modify/delete site permissions are not correctly updated.g. In this case the Carrier bandwidth will be updated automatically.25 MHz. based on the chosen Carrier mapping. but if clearing it and selecting it again. there is a project option named "Sites modifiable".

Optional modules and Optimization modules. Base module: • • Single user license Floating network license Technology modules: • • • • GSM WCDMA LTE WiMAX Optional modules: • HSPA for WCDMA Optimization modules: • • • AFP . Combine the Base module with Technology.12 TEMS CellPlanner product packages The TEMS CellPlanner product consists of different modules to meet different customers’ needs.Automatic Frequency Planning ACP – Automatic Cell Planning AMI & ASMT – Automatic Measurement Integrator & Automatic Sector Model Tuning A standard TEMS CellPlanner product package consists of the following: • • • • TEMS CellPlanner installation CD Installation Note and Installation Guide Demonstration Project and demonstration Map data Release Note © Ascom (2009) Document: LZT 108 9841 R2C 38(47) .

com You will also find the latest technical information.13 Contact information Please visit our web site at www.ascom. FAQs and downloads of patch release on the Technical Support web pages at our web site. © Ascom (2009) Document: LZT 108 9841 R2C 39(47) . To receive product updates and patch release information. sign up for the TEMS Subscription Service at TEMS web site.

Appendix I Addendum Additions to the TEMS CellPlanner 8.1 User documentation © Ascom (2009) Document: LZT 108 9841 R2C 40(47) .

and RBS explorers to apply filters to limit the scope of operations.2 Figure 2a. (The Selection is a selection of sites or cells from the map display). use instead the procedure Apply Filters in Explorers. create and delete filters from this panel.2). and created. Site. © Ascom (2009) Document: LZT 108 9841 R2C 41(47) .1.0 Figure 2b.0 will include possibilities to edit. there are options to filter on a Selection or a Filter in explorers and analysis windows. Layout in explorers and analysis windows In 8.0 Filter functionality In 9. Filter option in Selection & filters panel in TEMS CellPlanner 9. edited and deleted from the Filter option. view. Selection panel in TEMS CellPlanner 8.2 this is not possible. Limiting the view to a specific set of network elements makes it easier to locate. (This procedure has been removed from the manual delivered with 8.2 documentation and implementation is described below.2. The following procedures in the manual are not yet usable in 8. enclosed below. filters can be created and edited from the Selection option. Figures 1-3 show the different layouts. and 9. In 8.1.1.1 Correction to the Common Features User's Guide Chapter Using Filters to Manage Network Planning in the Common Features User's Guide is updated for functionality delivered in a later release.1. 9. The layout is though somewhat different.1. Apply Filters in Explorers Use the Network.2: • • • Create Filter from Explorers or Analysis Windows Remove Selection from Explorer or Analysis Window Delete Filter from Explorer or Analysis Window In 8. Figure 1.1. The main discrepancies between the 8.0.0.0. and change them. Selection option in Selection & filters panel in TEMS CellPlanner 9.2 as well as 9.1.

Click Up or Down to move the filter in the Applied list. When the list of applied filters is complete and sorted. Select additional filters as desired. The filter is moved to the Applied list. An object must pass all selected filters to be included in a selection. as shown in the following example: 3. Select a filter from the list and click Add. click OK to apply the filters to the view in the Network explorer.Procedure Follow these steps to apply a filter to an explorer. The filters are processed sequentially. Select Utilities Network explorer. 4. This example uses the Network explorer: 1. To the right of the Filter field. 5. click to display the Apply filter window. using an AND operation between each filter. 2. © Ascom (2009) Document: LZT 108 9841 R2C 42(47) .

4.e. Restart the service SentinelLM (right-click and order this) Start the WlmAdmin. 3 licenses should be reserved These 4 users. 8. user4 At the license server. TEMS CellPlanner does not fully support multi-byte character sets. user3. should be able to use the 3 licenses 3. open the SentinelLM service.2.TCP_LI_2:OUR_GROUP:3:user1 user2 user3 user4 5. on a license server. check the license INTERNAL version TCP_LI_2.2 Additions and clarifications to different parts of the TEMS CellPlanner 8. in W2000 via Programs-Administrative Tools-Services in Vista via Control Panel-Administrative Tools-Services 2. Check where the service was installed. (rightClickproperties). © Ascom (2009) Document: LZT 108 9841 R2C 43(47) .1 Suppose you have: • • 1. In the Services panel. 3 licenses of INTERNAL. and no other. activate the Services panel. from the bin folder in TCP Choose the license server machine In WlmAdmin. 2.exe program. i.1 User documentation How to allocate licenses. 6. "Path to executable" Go to this directory Create a file. to a limited group of users 2.2 TEMS CellPlanner supports single-byte character sets. with following content: # Created By SentinelLM Group Manager ::: 7.0 INTERNAL. version TCP_LI_2 4 users called user1. called lsreserv. user2.0 ::: 1. 7.

User A can only select to publish his/her private workspace value. with a scenario of two users updating the same parameter in the database: 1. To minimize the risk for lost updates minimize the time spent deciding on conflicts. The conflict is displayed in the Resolve Conflicts window. User A publishes his/her change. or explicitly set the antenna height to the correct value in the Antenna branch editor. 2.3 What could happen if a user takes long time to resolve conflicts in the TEMS CellPlanner Server environment? First a short description of this situation.4 Interpretation of ground height The ground height of an antenna branch is typically set to zero. or accept the value in the database (which he/she thinks is X. 3.e. user A has set a new value of the object in his/her private workspace and now publishes the change. In the meanwhile. It is always safe to cancel the publish i. but for some reason he/she waits with the decision. which means that the effective antenna height may be different in different resolutions. In such cases. When a coarse pathloss resolution is used in hilly terrain. Here user B shall take a decision to publish his/her value or accept the one published by user A. User B now publishes his/her change. restart the conflict resolution with the latest changes. 2. 4.2. the elevation map is re-sampled to the same resolution used in the pathloss calculation. it is recommended to either use the full map resolution when running pathloss. this may give a large difference in effective antenna height. The database is updated with the new value (for example X). © Ascom (2009) Document: LZT 108 9841 R2C 44(47) . User A is now ready to take a decision about the conflict in the still open Resolve Conflicts window. but in reality it is Y). As TEMS CellPlanner does not support updating the window with changes done after the first conflict was presented. user A does not see that the object in the database has changed to value Y. However. which implies that the pathloss algorithm uses the height specified by the elevation map at the geographical position of the antenna. Since Publish is performed on the stored data in your private workspace and the stored data in the main projects nothing will be lost if you cancel Publish. The database is updated with the new value (Y). 5. Users A and B both change the same object in their private workspaces.

etc.e. The situation is a bit more complicated if you are using OSS-RC WCDMA Import to update an existing TEMS CellPlanner project that has not been created with OSS-RC Import. the publishing fails. your project must comply with the rules listed below. Not following the rules below may result in creation of duplicate objects in the project. When you publish changes the permissions are checked to make sure that you only change things that you are allowed to change.If not present. which makes it more difficult for the OSS-RC WCDMA Import function to figure out which TEMS CellPlanner object corresponds to a certain OSS-RC object. In this case the objects in the project don't have any OSS-RC ids. This is allowed in order to be able to make changes that you never intend to publish.) are guaranteed to have the correct OSS-RC ids from the beginning and subsequent OSS-RC exports and imports will work smoothly. it must have the same name as the root Subnetwork in OSS-RC. yet.5 The permissions system is enforced when you make changes that affect other people i. Optionally the name may be prefixed with the Subnetwork name prefix from Project settings->Object names. cells. 2.If present in the project. Sectors. You can use the partial publish to publish a part of the project and partial refresh to refresh a part of the project. the Subnetwork will be created by the Import. RBSs.6 Rules for OSS-RC WCDMA Import into an existing TEMS CellPlanner project The easiest way to use OSS-RC WCDMA Import is to start a new project from scratch and import the entire network from OSS-RC. Rules to follow when performing first time OSS-RC WCDMA Import into an existing WCDMA project: Subnetwork (Optional) . or the OSS-RC objects being mapped to the wrong TEMS CellPlanner objects. In that way all objects in the projects (Subnetwork. you publish your changes to the main project You are allowed to change your private workspace regardless of permission. . Rnc (Optional) © Ascom (2009) Document: LZT 108 9841 R2C 45(47) .2. RNCs. a change requiring special permissions blocks the entire publishing if the user does not have these permissions. As all permission violations must be resolved before a change in the project can be published. When a user tries to publish a change in conflict with the user’s permissions in the project. In order for the import to succeed.

since TEMS CellPlanner does not model antenna diversity."2". .. (2) Using RBS name+letter suffix: For this to work. Sector->AntennaBranch->Antenna>beamDirection must be the same as the beamDirection of the corresponding Sector in OSS-RC. which consists of AntennaBranch prefix (from Project settings) + Sector name. . it must have the same name as the corresponding RNC in OSS-RC. The alternatives are tested in the order below... then the relevant one should be given the default name.e. if that fails. Sector There are three alternative ways to match Sectors. and the corresponding Sectors in TEMS CellPlanner must be called RBS_nameA. the localCellId in TEMS CellPlanner must be set to the same value as the localCellId of the corresponding UtranCell and RbsLocalCell in OSS-RC. the beamDirection of each Sector must be unique within the Rbs. AntennaBranch Only one AntennaBranch per Sector is imported from OSS-RC: the "A" branch. UtranCell There are two alternative ways to match UtranCells."3". Optionally the name may be prefixed with the Rbs name prefix from Project settings->Object names. Therefore. the Rnc will be created by the Import. (2) Using localCellId: For this to work.If not present. (3) Using any name: Each Sector in TEMS CellPlanner must have the same name as the corresponding Sector in OSS-RC. i. try (2). Optionally the name may be prefixed with the Rnc name prefix from Project settings->Object names.. the Sectors in OSS-RC must be named "1". Rbs The RBS objects must have the same name as the corresponding RBS in OSS-RC. i.e. and the UtranCell on carrier 2 must be called Sector_name2 in the TEMS CellPlanner project. we try (2). RBS_nameC. RBS_nameB.. NOTE: The UtranCell names and RbsLocalCell names from OSS-RC are not used for matching. if that fails try (3). it is recommended to have only one AntennaBranch per Sector alsoin the TEMS CellPlanner project. they are only stored as Custom Attributes.. The alternatives are tested in the order below. we try (1) first.If present in the project. (1) Using Sector name+carrier number: For this to work.. Furthermore. © Ascom (2009) Document: LZT 108 9841 R2C 46(47) . (1) Using azimuth: For this to work. if that fails. try (1) first. If a Sector has more than one AntennaBranch nevertheless. the UtranCell on carrier 1 must be called Sector_name1.

since the FeederCables are listed on RBS level. As a work-around. To avoid this problem. NOTE that this problem only exists in OSS-RC R4. This means that when importing a Bulk CM file from OSS-RC R4.2 and higher versions. Getting the wrong Feeder cable for an AntennaBranch may result in getting incorrect "Override attenuation" values for the AntennaBranch. the OSS-RC WCDMA Import makes an assumption that the feeder cables are listed in the same order as the AntennaBranches in the Bulk CM file. however.2. you can unselect the "Feeder cable attenuations" parameter when importing from OSS-RC. (See File->Import->OSS-RC WCDMA->Antenna equipment tab). we cannot know for certain which AntennaBranch each FeederCable belongs to. This usually works. The bug is fixed in OSSRC R5. © Ascom (2009) Document: LZT 108 9841 R2C 47(47) . there is no guarantee.7 Bulk CM bug in OSS-RC R4 affecting import of Feeder cables There is a known bug in OSS-RC R4 regarding the Bulk CM interface: the AntennaBranch reference attribute of Feeder cable is missing from the Bulk CM file.