tems visualization 8 enterprise help client

i

TEMS Visualization 8.0 Enterprise Client User’s Manual

ii

Copyright This manual is provided by Ascom without any kind of warranty. Improvements and changes in this description due to typographical errors or inaccuracies in current information, or improvements to programs and/or equipment may be made by Ascom at any time without notice. These changes will, however, be incorporated into new editions of this manual. No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of the copyrighted owner, Ascom.

TEMS is a trademark owned by Ascom. All other trademarks are the property of their respective holders. © 2011 Ascom. All rights reserved. Publication number: NT11-2026

iii

Software License Agreement Ascom Network Testing AB, reg. no. 556759-2521, 932 83 Ursviken, Sweden ("Licensor") licenses the accompanying software (hereinafter “Software”) to you only upon the condition that you accept all of the terms and conditions in this Software License Agreement ("SLA"). Please read the terms and conditions carefully before installing and using the Software. 1.0 DEFINITIONS "Confidential Information" means any information of a proprietary or confidential nature disclosed or otherwise provided to you by Licensor in connection with the Software. "Licensee" or "you," means the corporate entity licensing the Software under the terms of this SLA. "Materials" means the documentation, modifications, subsequent versions, diagnostic software, prior versions support materials, and manuals provided by Licensor with or for use in conjunction with the Software with which it was delivered. "Software" means Program and Third-Party Software, along with each and every one of its components, including but not limited to Materials, Confidential Information, and other materials delivered to Licensee herein. "Program" means the proprietary software of Licensor. “Third-Party Software” means all software (including its accompanying Materials) delivered to Licensee herein, which is not a Program. “Trial Period” means the trial period for a Trial Version to be agreed separately. “Trial Version” means Software indicated by Licensor as a trial version. 2.0 LICENSE 2.1 Scope: Licensor hereby grants Licensee a non-exclusive, non-transferable license

(without the right to sub-license or assign) for the following purposes: a. To use the Software solely for the purpose of plan, design, rollout, verify,

optimize, troubleshoot and/or analyze communication networks and for no other purpose. This license is provided by Licensor to the Licensee only, and is expressly limited to use by the Licensee, its employees, and agents using it

iv

on Licensee's behalf, provided that such employees and agents comply with the terms of this SLA. Licensee assumes full responsibility and liability for compliance with all of the terms and conditions of this SLA by its employees and agents.

b. Licensor may license the Software in the following ways: single user license or concurrent user license. The specific license applicable to this SLA is agreed separately. Depending upon the type of license agreed, one or more of the following terms (1-2) shall apply. Should no agreement exist on the type of license including the number of users, the license is for one single user only: 1. If the agreed license is for a specified number of single users, you may

copy the Software into the local memory or storage device of the number of computers agreed upon separately and actually paid for by you.

2. If the agreed license is for concurrent users, you may copy the Software into the local memory or storage device accessible by the number of concurrent users agreed upon separately and the actual payment for concurrent use made to Licensor. If more users have access to the local memory or storage device where the Software will be stored, Licensee agrees to limit the number of concurrent users to that agreed upon separately.

c. If Licensor has made available to Licensee information reasonably necessary to achieve interoperability of the Software with other operating systems and/or platforms, Licensee further agrees that the provision of such information shall not act to expand the foregoing license, either directly or by implication, nor shall it provide any exception to the Limitations on Use enumerated in Section 2.2, below.

d. For Trial Versions of the Software the Licensee hereby agrees to that, at the end of the Trial Period, all copies of all of the Materials, Programs, Confidential Information and Third-Party Software included are no longer being used by Licensee and are either removed from the Licensee’s computer system or are otherwise made unusable after the end of the Trial Period.

e. No other right is granted by this SLA, either expressly, by implication, or otherwise.

2.2 Limitations on Use. In addition to all other limitations in this section and this SLA,

you expressly agree that you shall not: a. Make any copies of the Software or any component of the Software, other

than those specifically authorized in Section 2.1 of this SLA (if your CD ROM becomes damaged and additional copies are necessary, please contact Licensor);

b. Modify the Software in any way;

v

c. Reverse engineer, decompile, disassemble, or reverse assemble the Software or any of its components to the extent Licensor can prohibit such acts by law;

d. Remove any Licensor (or Third-Party Software) copyright, trademark, or other proprietary notices from the Software or any Third-Party Software included with it;

e. Create derivative works or other versions of the Software; f. Distribute or otherwise make available the Software, any component of the

Software or any Materials provided with the Software, directly or indirectly, for any use by any other person or entity;

g. Transfer the Software or any part of the Software, including the Materials, except as expressly authorized in writing by Licensor;

h. Modify or render inoperable any hardware or software key, or other encryption device or code required to use the Software;

i. Modify or render inoperable any license management software included with the Software;

j. Assign any part or all of Licensee's rights under this SLA.

2.3 Ownership: a. Licensee acknowledges that the Software includes proprietary information

which is protected by copyright and other intellectual property laws and international treaties.

b. Licensee acknowledges that the Software is an unpublished work which contains valuable trade secrets and other confidential and proprietary information of Licensor, that Licensor derives independent economic benefits from its ownership and use of the Software, and that Licensor maintains the Software in confidence and uses reasonable precautions to protect the Software from unauthorized use or disclosure. Licensor's trade secrets and confidential information include but are not limited to: (1) the development status of the Software; (2) the functionality of the Software; (3) the appearance, content, and flow of the Software's screens; (4) the method and pattern of user interaction with the Software; and (5) the content of the Materials provided with the Software.

c. Licensor retains all title and ownership rights in the Software and its components, and all of the updates, documentation, changes, modifications, subsequent versions, diagnostic software, support materials, manuals, and other Materials, all of which contain Licensor proprietary or confidential information. The Software, the Materials, and any Licensor proprietary rights pertaining thereto (including all patents, trademarks, trade secrets, and service marks), remain the exclusive property of Licensor and no title is granted to you in conjunction with this SLA.

d. Licensee agrees that no title or other ownership right (except the explicit license granted herein) to the Software (including but not limited to the components of the Software, any intellectual property rights in the Software

vi

or its components, or copies of the Software or any components of the Software) is transferred by this SLA.

2.4 Licensee's Additional Obligations:

a. Licensee agrees to properly secure the Software and all other aspects of the Software and agrees not to use the Software in any manner inconsistent with this SLA, including, but not limited to, making the Software available to third parties without Licensor's prior written consent.

b. Licensee agrees to hold the Software, including but not limited to, the Materials, in trust and confidence for Licensor during the term of this SLA and thereafter for a period of five years, and consents to the subsequent destruction or return of the material at Licensor's option, after expiration of the license.

c. Licensee agrees that it maintains or will maintain adequate internal procedures, including appropriate binding agreements with its employees and agents, to protect Licensor's proprietary information in a reasonable manner, but with no less degree of care than Licensee uses to protect its own confidential or proprietary information.

2.5 Limitations to Confidentiality Obligations. Licensee shall have no obligation under

Section 2.4 of this SLA as to information in the Software that Licensee can prove through independent evidence: a. was known to Licensee at the time of disclosure by Licensor, and for which

Licensee is under no duty of confidentiality to Licensor or any third party; b. is independently developed by Licensee, provided Licensee can show by

documentary evidence that such development was accomplished by Licensee or on Licensee's behalf without the use of or reference to Confidential Information supplied to Licensee by Licensor;

c. becomes rightfully known to Licensee from a source other than Licensor, which source is without a confidentiality restriction on disclosure or use; or

d. is or becomes part of the public domain through no wrongful act of Licensee or another person or entity.

2.6 Disclosure Pursuant to Order of Court. If Licensee is ordered by a judicial or

governmental body to disclose Licensor's Confidential Information, such disclosure may occur only if Licensee gives Licensor at least ten (10) days' written notice prior to such disclosure (or any longer period reasonably necessary to allow Licensor to act under the circumstances) so Licensor may either (1) contest the order or (2) obtain a protective order or writ preventing disclosure pursuant to such order.

2.7 Third-Party Software. The Software include Third-Party Software consisting of

Microsoft SQL Server 2008 Enterprise Edition which is licensed by Microsoft Corporation and is subject to individual terms and conditions which are attached to this SLA as Appendix A. Please review any such agreement carefully before

vii

installing and using the Software. If the provisions of any Third-Party Software license agreement conflicts with the provisions of this SLA, the provisions of this SLA shall have precedence if more restrictive towards Licensee.

3.0 LIMITATION OF LIABILITY 3.1 General Disclaimer. UNLESS OTHERWISE EXPLICITLY AGREED IN WRITING

BETWEEN LICENSOR OR AUTHORIZED LICENSOR RESELLER AND LICENSEE, WITH REGARDS TO THE SOFTWARE, LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND/OR CONDITIONS, EXPRESSED OR IMPLIED, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTY OF MERCHANTABILITY, ANY IMPLIED WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE, ANY IMPLIED WARRANTY OF, AND ANY IMPLIED WARRANTY ARISING OUT OF, THE COURSE OF DEALING BETWEEN LICENSEE AND LICENSOR, CUSTOM, OR USAGE OF THE TRADE.

3.2 Limitation of Liability. IN NO EVENT WILL LICENSOR BE LIABLE HEREUNDER

TO LICENSEE OR ANY OTHER PERSON OR ENTITY FOR ANY CLAIM, LOSS, OR DAMAGE OF ANY KIND ARISING OUT OF THE PERFORMANCE OF THIS SLA OR ARISING OUT OF OR IN CONNECTION WITH (1) THE DEFICIENCY OR INADEQUACY OF THE SOFTWARE FOR ANY PURPOSE WHETHER OR NOT KNOWN OR DISCLOSED TO LICENSEE; (2) THE USE OR PERFORMANCE OF THE SOFTWARE OR OF ANY FILES, DATA, OR COMPUTER SYSTEMS RELATING THERETO OR USED IN CONNECTION THEREWITH; (3) ANY INTERRUPTION OR LOSS OF SERVICE OR USE OF THE SOFTWARE; (4) ANY ERROR; OR (5) ANY LOSS OF PROFITS, SALES, BUSINESS, DATA, OR OTHER DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL LOSS OR DAMAGE OF ANY KIND OR NATURE RESULTING FROM THE FOREGOING, AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE.

IN NO EVENT SHALL LICENSOR'S LIABILITY TO LICENSEE HEREUNDER

EXCEED THE LICENSE FEES ACTUALLY PAID BY LICENSEE FOR THE LICENSES PROVIDED HEREUNDER, WHETHER SUCH LIABILITY IS ASSERTED ON THE BASIS OF CONTRACT, TORT (INCLUDING NEGLIGENCE, PRODUCT LIABILITY, AND STRICT LIABILITY), OR OTHERWISE, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

3.3 No Warranty or Representations as to Intellectual Property Rights of Third

Parties. LICENSOR EXPRESSLY DISCLAIMS ANY WARRANTY OF NON-INFRINGEMENT OF ANY PATENT, TRADEMARK, COPYRIGHT, OR OTHER INTELLECTUAL PROPERTY OF ANY THIRD PARTY.

viii

4.0 MISCELLANEOUS 4.1 Independent Parties. The parties to this SLA are independent entities. Nothing in

this SLA shall be construed as creating a joint venture, partnership, agency, or employment relationship between Licensor and Licensee, its employees, or agents.

4.2 Export Controls. In the event that the provision of the Software or any part

thereof is prohibited by export control laws or regulations, then: (i) Licensor shall have no obligation whatsoever to deliver the Software or any part thereof to Licensee; (ii) Licensor shall have no liability to Licensee or any third party for its failure to deliver the Software or any part thereof to Licensee; and (iii) in the event Licensee has paid any amount to Licensor, that amount shall, at Licensor's option, either be refunded or credited against any outstanding amounts due from Licensee.

4.3 Severability/Unenforceable Provisions. In the event that any provision of this SLA

is found by a court of competent jurisdiction to be unenforceable, invalid, or illegal in any respect, the remaining provisions of this SLA shall be enforceable to the maximum extent possible.

4.4 Headings. The section headings used in this SLA are intended for reference

purposes only, and shall not affect the interpretation or construction of any provision of this SLA.

4.5 Consent to Use of Non-Personal Data. The Licensee agrees that the Licensor and

its subsidiaries may collect and use technical and related information, including but not limited to information about your hardware, system and software, and peripherals, that is gathered periodically to facilitate the provision of software updates, Software support and other services to Licensee (if any) related to the Software, and to verify compliance with this SLA. Licensor may use this information, as long as it is in a form that does not personally identify you, to improve Softwares of Licensor or to provide services or technologies to Licensee.

4.6 Force Majeure. Neither party shall be responsible for any delay or failure to

perform obligations specified in this SLA due to causes beyond the party's reasonable control, including but not limited to strikes, civil disturbances, embargoes, parts shortages, manufacturing difficulties, riots, wars, fires, acts of God, and acts in compliance with any applicable law, regulation, or order (whether valid or invalid) of any governmental authority.

4.7 Complete Agreement. This SLA represents the sole and exclusive SLA between

the parties, and supersedes and cancels any previous agreement, whether written or oral, between the parties with respect to the subject matter of this SLA. Neither

ix

party shall be bound by any term, provision, condition, definition, guarantee, or representation other than those set forth herein.

4.8 Waiver. The failure of either party to enforce any section or part of this SLA, or

any right under this SLA, shall not be construed as a waiver of such provision or right to subsequently enforce that or any other provision of this SLA.

4.9 Assignment. Licensee may not assign either this SLA (in whole or part) or any of

the rights or obligations arising from it without the express, written consent of Licensor. Any attempted assignment shall be null and void. Licensor may assign this SLA in whole or part, including any specific rights or obligations of Licensor hereunder.

4.10 Applicable Law/Obligation and consent to Jurisdiction. The parties agree that this

SLA is governed by the laws of Sweden excluding its principles of conflict of laws. All disputes between the parties arising out of or in connection with this SLA shall be finally settled under the Rules of Arbitration of the International Chamber of Commerce, in Stockholm, Sweden, by one or more arbitrators appointed in accordance with the said Rules and the proceedings shall be conducted in the English language. The parties undertake and agree that all arbitral proceedings conducted under this article shall be kept strictly confidential, and all information, documentation, materials in whatever form disclosed in the in the course of such arbitral proceeding shall be used solely for the purpose of those proceedings. All arbitral awards may if necessary be enforced by any court having jurisdiction in the same manner as a judgment in such court.

TEMS Visualization 8.0 Enterprise Client

xi

Appendix A (For ISV Royalty Program Only) Microsoft® SQL Server™ 2008 Enterprise Edition Server Licenses: 1 User Client Access Licenses: 0 Device Client Access Licenses: 1 These license terms are an agreement between the licensor of the software application or suite of applications with which you acquired the Microsoft software (“Licensor”) and you. Please read them. They apply to the software named above, which includes the media on which you received it, if any. The terms also apply to any Microsoft

• updates, • supplements, and • Internet-based services

for this software, unless other terms accompany those items. If so, those terms apply. Microsoft Corporation or one of its affiliates (collectively, “Microsoft”) has licensed the software to Licensor. BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE. INSTEAD, RETURN IT TO THE PLACE OF PURCHASE FOR A REFUND OR CREDIT. These terms supersede any electronic terms which may be contained within the software. If any of the terms contained within the software conflict with these terms, these terms will control. IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE RIGHTS BELOW FOR EACH SOFTWARE LICENSE YOU ACQUIRE. 1. OVERVIEW.

a. Software. The software includes • server software; and • additional software that may only be used with the server software

directly, or indirectly through other additional software. b. License Model. The software is licensed based on

• the number of instances of server software that you run; and • the number of devices and users that access instances of server

software. c. Licensing Terminology.

• Instance. You create an “instance” of software by executing the software’s setup or install procedure. You also create an instance of software by duplicating an existing instance. References to software in this agreement include “instances” of the software.

xii

• Run an Instance. You “run an instance” of software by loading it into memory and executing one or more of its instructions. Once running, an instance is considered to be running (whether or not its instructions continue to execute) until it is removed from memory.

• Operating System Environment. An “operating system environment” is: − all or part of an operating system instance, or all or part of a

virtual (or otherwise emulated) operating system instance which enables separate machine identity (primary computer name or similar unique identifier) or separate administrative rights, and

− instances of applications, if any, configured to run on the operating system instance or parts identified above.

There are two types of operating system environments, physical and virtual. A physical operating system environment is configured to run directly on a physical hardware system. The operating system instance used to run hardware virtualization software (e.g. Microsoft Virtual Server or similar technologies) or to provide hardware virtualization services (e.g. Microsoft virtualization technology or similar technologies) is considered part of the physical operating system environment. A virtual operating system environment is configured to run on a virtual (or otherwise emulated) hardware system. A physical hardware system can have either or both of the following: • one physical operating system environment • one or more virtual operating system environments.

2. USE RIGHTS. Server. A “server” is a physical hardware system capable of running server software. A hardware partition or blade is considered to be a separate physical hardware system. Assigning a License. To “assign a license” means simply to designate that license to one device or user. a. Assigning the License to the Server.

i. Before you run any instance of the server software under a software license, you must assign that license to one of your servers. That server is the licensed server for that particular license. You may assign other software licenses to the same server, but you may not assign the same license to more than one server. A hardware partition or blade is considered to be a separate server.

ii. You may reassign a software license, but not within 90 days of the last assignment. You may reassign a software license sooner if you retire the licensed server due to permanent hardware failure. If you reassign a license, the server to which you reassign the license becomes the new licensed server for that license.


xiii

b. Running Instances of the Server Software. You may run any number of instances of the server software in one physical or virtual operating system environment on the licensed server at a time.

c. Running Instances of the Additional Software. You may run or otherwise use any number of instances of additional software listed below in physical or virtual operating system environments on any number of devices solely to support your use of the integrated software turnkey application or suite of applications (the “Unified Solution”) delivered by or on behalf of the Licensor. You may use additional software only with the server software directly or indirectly through other additional software. • Business Intelligence Development Studio • Client Tools Backward Compatibility • Client Tools Connectivity • Client Tools Software Development Kit • Management Studio • Microsoft Sync Framework • SQL Server 2008 Books Online

d. Creating and Storing Instances on Your Servers or Storage Media. You have the additional rights below for each software license you acquire. • You may create any number of instances of the server software and

additional software. • You may store instances of the server software and additional software

on any of your servers or storage media. • You may create and store instances of the server software and

additional software solely to exercise your right to run instances of the server software under any of your software licenses as described (e.g., you may not distribute instances to third parties).

e. Included Microsoft Programs. The software contains other Microsoft programs. The license terms with those programs apply to your use of them.

3. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS.

a. Client Access Licenses (CALs). i. You must acquire and assign a SQL Server 2008 CAL to each device or

user that accesses your instances of the server software directly or indirectly. A hardware partition or blade is considered to be a separate device. • You may not access instances of the server software under

Workgroup Edition CALs. • You may use your Windows Small Business Server (“SBS”) 2008

CAL Suite for Premium Users or Devices instead of SQL Server 2008 CALs to access your instances of the server software within an SBS 2008 domain.

• You may use your Windows Essential Business Server (“EBS”) 2008 CAL Suite for Premium Users or Devices instead of SQL Server

xiv

2008 CALs to access your instances of the server software within an EBS domain.

• You do not need CALs for any of your servers licensed to run instances of the server software.

• You do not need CALs for up to two devices or users to access your instances of the server software only to administer those instances.

• Your CALs permit access to your instances of earlier versions, but not later versions, of the server software. If you are accessing instances of an earlier version, you may also use CALs corresponding to that version.

ii. Types of CALs. There are two types of CALs: one for devices and one for users. Each device CAL permits one device, used by any user, to access instances of the server software on your licensed servers. Each user CAL permits one user, using any device, to access instances of the server software on your licensed servers. You may use a combination of device and user CALs.

iii. Reassignment of CALs. You may • permanently reassign your device CAL from one device to

another, or your user CAL from one user to another; or • temporarily reassign your device CAL to a loaner device while the

first device is out of service, or your user CAL to a temporary worker while the user is absent.

b. Runtime-Restricted Use Software. The software is “Runtime-Restricted Use” software; as such, it may only be used in conjunction with the Unified Solution. The software may not be used either i. to develop any new software applications, ii. in conjunction with any software applications, databases or tables

other than those contained in the unified solution, and/or iii. as a standalone software application. The foregoing provision, however, does not prohibit you from using a

tool to run queries or reports from existing tables. A CAL permits you to access instances of only the Runtime-Restricted User version of the server software licensed and delivered to you as part of the Unified Solution, in accordance with the other terms of the agreement.

c. Maximum Instances. The software or your hardware may limit the number of instances of the server software that can run in physical or virtual operating system environments on the server.

d. Multiplexing. Hardware or software you use to • pool connections, • reroute information, and • reduce the number of devices or users that directly access or use the

software, or • reduce the number of devices or users the software directly manages.


xv

• (sometimes referred to as “multiplexing” or “pooling”), does not reduce the number of licenses of any type that you need.

e. No Separation of Server Software. You may not separate the server software for use in more than one operating system environment under a single license, unless expressly permitted. This applies even if the operating system environments are on the same physical hardware system.

f. Fail-over Server. For any operating system environment in which you run instances of the server software, you may run up to the same number of passive fail-over instances in a separate operating system environment for temporary support. You may run the passive fail-over instances on a server other than the licensed server.

4. INTERNET-BASED SERVICES. Microsoft provides Internet-based services with the

software. It may change or cancel them at any time. 5. .NET FRAMEWORK AND POWERSHELL SOFTWARE. The software contains

Microsoft .NET Framework and PowerShell software. These software components are part of Windows.

6. BENCHMARK TESTING. You must obtain Microsoft's prior written approval to

disclose to a third party the results of any benchmark test of the software. However, this does not apply to the Windows components. For Microsoft .NET Framework see below.

7. MICROSOFT .NET FRAMEWORK. The software includes one or more components

of the .NET Framework (“.NET Components”). You may conduct internal benchmark testing of those components. You may disclose the results of any benchmark test of those components, provided that you comply with the conditions set forth at http://go.microsoft.com/ fwlink/?LinkID=66406. Notwithstanding any other agreement you may have with Microsoft, if you disclose such benchmark test results, Microsoft shall have the right to disclose the results of benchmark tests it conducts of your products that compete with the applicable .NET Component, provided it complies with the same conditions set forth at http://go.microsoft.com/fwlink/?LinkID=66406.

8. SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives

you some rights to use the software. Licensor and Microsoft reserve all other rights. Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. For more information, see www.microsoft.com/licensing/userights. You may not

• work around any technical limitations in the software;

http://go.microsoft.com/fwlink/?LinkID=66406�

http://www.microsoft.com/licensing/userights�

xvi

• reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;

• make more copies of the software than specified in this agreement or allowed by applicable law, despite this limitation;

• publish the software for others to copy; • rent, lease or lend the software; or • use the software for commercial software hosting services.

Rights to access the software on any device do not give you any right to implement Microsoft patents or other Microsoft intellectual property in software or devices that access that device.

9. BACKUP COPY. You may make one backup copy of the software media. You may

use it only to create instances of the software. 10. DOCUMENTATION. Any person that has valid access to your computer or internal

network may copy and use the documentation for your internal, reference purposes.

11. NOT FOR RESALE SOFTWARE. You may not sell software marked as “NFR” or “Not

for Resale.” 12. ACADEMIC EDITION SOFTWARE. You must be a “Qualified Educational User” to

use software marked as “Academic Edition” or “AE.” If you do not know whether you are a Qualified Educational User, visit www.microsoft.com/ education

or contact the Microsoft affiliate serving your country.

13. TRANSFER TO ANOTHER DEVICE. You may uninstall the software and install it on another device for your use solely as part of the Unified Solution. You may not do so to share this license between devices to reduce the number of licenses you need.

14. TRANSFER TO A THIRD PARTY. The first user of the software may transfer it, this

agreement, and CALs, directly to another end user as part of a transfer of the Unified Solution delivered to you by or on behalf of the Licensor solely as part of the Unified Solution. Before the transfer, that end user must agree that this agreement applies to the transfer and use of the software. The first user may not retain any instances of the software unless that user also retains another license for the software.

15. EXPORT RESTRICTIONS. The software is subject to United States export laws and

regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see www.microsoft.com/exporting.

http://www.microsoft.com/�

http://www.microsoft.com/exporting�


xvii

16. ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates,

and Internet-based services that you use, are the entire agreement for the software.

17. LEGAL EFFECT. This agreement describes certain legal rights. You may have other

rights under the laws of your state or country. You may also have rights with respect to the Licensor from whom you acquired the software. This agreement does not change your rights under the laws of your state or country if the laws of your state or country do not permit it to do so.

18. NOT FAULT TOLERANT. THE SOFTWARE IS NOT FAULT TOLERANT. LICENSOR

HAS INDEPENDENTLY DETERMINED HOW TO USE THE SOFTWARE IN THE INTEGRATED SOFTWARE APPLICATION OR SUITE OF APPLICATIONS THAT IT IS LICENSING TO YOU, AND MICROSOFT HAS RELIED ON LICENSOR TO CONDUCT SUFFICIENT TESTING TO DETERMINE THAT THE SOFTWARE IS SUITABLE FOR SUCH USE.

19. NO WARRANTIES BY MICROSOFT. YOU AGREE THAT IF YOU HAVE RECEIVED

ANY WARRANTIES WITH REGARD TO EITHER (A) THE SOFTWARE, OR (B) THE SOFTWARE APPLICATION OR SUITE OF APPLICATIONS WITH WHICH YOU ACQUIRED THE SOFTWARE, THEN THOSE WARRANTIES ARE PROVIDED SOLELY BY THE LICENSOR AND DO NOT ORIGINATE FROM, AND ARE NOT BINDING ON, MICROSOFT.

20. NO LIABILITY OF MICROSOFT FOR CERTAIN DAMAGES. TO THE MAXIMUM

EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT SHALL HAVE NO LIABILITY FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL OR INCIDENTAL DAMAGES ARISING FROM OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE SOFTWARE OR THE SOFTWARE APPLICATION OR SUITE OF APPLICATIONS WITH WHICH YOU ACQUIRED THE SOFTWARE, INCLUDING WITHOUT LIMITATION, PENALTIES IMPOSED BY GOVERNMENT. THIS LIMITATION WILL APPLY EVEN IF ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE. IN NO EVENT SHALL MICROSOFT BE LIABLE FOR ANY AMOUNT IN EXCESS OF TWO HUNDRED FIFTY U.S. DOLLARS (US$250.00).

Microsoft and SQL Server are registered trademarks of Microsoft Corporation in the United States and/or other countries.


Contents • xix

Contents

1 Introduction ............................................................................. 1 1.1 System Overview ................................................................................... 1 1.2 Bridging the Optimization Gap ....................................................... 2 1.3 What's New in This Release .............................................................. 3 1.4 Key Concepts .......................................................................................... 4 1.5 OSS Overview.......................................................................................... 5

1.5.1 WCDMA GPEH ..................................................................... 5 1.5.2 LTE CELL TRACE ....................................................................... 5 1.5.3 CELL CONFIGURATION FILES .................................................... 6

1.6 Installation, Help and Support ......................................................... 6

2 Navigating the TEMS Visualization Enterprise Client UI ............................................................................................... 7 2.1 Application Button & Quick Access Toolbar ............................. 8 2.2 Home Tab ................................................................................................. 9 2.3 Workspace Tab ....................................................................................... 9 2.4 Window Tab ......................................................................................... 11 2.5 Tools Tab − Cell Data Status Monitor ........................................ 11 2.6 Help Buttons......................................................................................... 13

2.6.1 LICENSE INFORMATION ......................................................... 13 2.6.2 ABOUT .................................................................................... 14 2.6.3 HELP ........................................................................................ 14

2.7 Status Bar ............................................................................................... 14 2.8 Data View Management .................................................................. 15

2.8.1 DISPLAY CONTROL ................................................................ 15 2.8.2 WINDOW MANAGER ............................................................. 15 2.8.3 VIEW DOCKING ...................................................................... 16 2.8.4 VIEW BUTTONS ...................................................................... 17

2.9 Chart Zoom ........................................................................................... 18 2.10 Working with Tables ......................................................................... 19 2.11 Workflow ................................................................................................ 21

3 Starting the System .............................................................. 23

xx

4 Data Views .............................................................................. 25 4.1 List of Views .......................................................................................... 25 4.2 Data Scope ............................................................................................ 28

4.2.1 MAP VIEW .............................................................................. 29 4.2.2 MAP THEMES ......................................................................... 30 4.2.3 MAP TOOLBAR ....................................................................... 34 4.2.4 MAP RIGHT-CLICK OPTIONS ................................................ 41

4.3 Overview Statistics View .................................................................. 48 4.4 Cell KPI View ......................................................................................... 49 4.5 Cluster KPI View .................................................................................. 53 4.6 Cell Capacity Analysis View ............................................................ 54 4.7 RF Diagnostics (MRR-W) View ...................................................... 55 4.8 Subscriber KPI View ........................................................................... 57 4.9 Subscriber Group KPI View ............................................................ 61 4.10 Phone Model KPI View ..................................................................... 63 4.11 Dropped Calls Analyzer ................................................................... 66 4.12 Call Search ............................................................................................. 68 4.13 Exception Analysis.............................................................................. 69

4.13.1 TEMS VISUALIZATION EVENT SUMMARY ........................... 69 4.13.2 GPEH / LTE CELL TRACE MESSAGES SUMMARY .............. 70 4.13.3 NAS MESSAGES SUMMARY ................................................. 71

4.14 Histogram View ................................................................................... 72 4.15 Coverage Area Optimization ......................................................... 74

4.15.1 OVERSHOOTING CELLS PART................................................ 74 4.15.2 PILOT POLLUTION COVERAGE – THRESHOLD BASED ......... 76 4.15.3 PILOT POLLUTION – SOHO BASED .................................... 77

4.16 Neighbor Optimization .................................................................... 78 4.16.1 EXISTING NEIGHBOR USAGE – INTRA-FREQUENCY ............ 80 4.16.2 MISSING NEIGHBORS – INTRA-FREQUENCY ....................... 80 4.16.3 EXISTING NEIGHBOR USAGE – INTER-FREQUENCY ............ 81 4.16.4 CANDIDATE NEIGHBORS – INTER-FREQUENCY ................... 81

4.17 Neighbor Change Request ............................................................. 82 4.18 User Defined Query ........................................................................... 86 4.19 Call Analysis .......................................................................................... 91 4.20 Chart Views ........................................................................................... 93

4.20.1 RF DISTRIBUTION CHART ..................................................... 94 4.20.2 RF SCATTER CHART ............................................................... 95 4.20.3 CAPACITY CHART ................................................................... 96 4.20.4 MEASUREMENT CHART ......................................................... 97


Contents • xxi

5 WCDMA Feature Description: Neighbor Optimization ... 99 5.1 Prerequisites ......................................................................................... 99 5.2 Intra-frequency Neighbor Optimization ................................ 100

5.2.1 GENERAL ............................................................................... 100 5.2.2 CALCULATION OF EXISTING NEIGHBOR USAGE ................ 100 5.2.3 MISSING NEIGHBORS .......................................................... 100 5.2.4 VIEW DESCRIPTIONS ............................................................ 101

5.3 Inter-frequency Neighbor Optimization ................................ 103 5.3.1 TECHNICAL DESCRIPTION .................................................... 103 5.3.2 VIEW DESCRIPTIONS ............................................................ 104

6 WCDMA Feature Description: Coverage Area Optimization ....................................................................... 107 6.1 Overshooting Cells .......................................................................... 107

6.1.1 PREREQUISITES ..................................................................... 107 6.1.2 TECHNICAL DESCRIPTION .................................................... 108 6.1.3 VIEW DESCRIPTIONS ............................................................ 111

6.2 Pilot Pollution - Threshold Based .............................................. 112 6.2.1 PREREQUISITES ..................................................................... 112 6.2.2 TECHNICAL DESCRIPTION .................................................... 112 6.2.3 VIEW DESCRIPTIONS ............................................................ 114

6.3 Pilot Pollution - SOHO Based ...................................................... 116 6.3.1 PREREQUISITES ..................................................................... 116 6.3.2 TECHNICAL DESCRIPTION .................................................... 116 6.3.3 VIEW DESCRIPTION .............................................................. 117

7 WCDMA Feature Description: RF Diagnostics ............... 119 7.1 Prerequisites ....................................................................................... 119 7.2 Technical Description ..................................................................... 120

7.2.1 RF ISSUE EVALUATION ........................................................ 121 7.2.2 POSSIBLE CAUSE: OVERSHOOTING CELL ........................... 122 7.2.3 POSSIBLE CAUSE: MISSING IFHO/IRAT .......................... 122 7.2.4 POSSIBLE CAUSE: PILOT POLLUTION - THRESHOLD

BASED ................................................................................... 123 7.2.5 POSSIBLE CAUSE: SOHO BLOCK ....................................... 124 7.2.6 POSSIBLE CAUSE: SOHO FAILURE .................................... 124 7.2.7 POSSIBLE CAUSE: UNMONITORED SOHO NEIGHBOR .... 125 7.2.8 POSSIBLE CAUSE: MISSING SOHO NEIGHBOR ................ 125 7.2.9 POSSIBLE CAUSE: UL PATH LOSSES ................................... 126

xxii

7.3 View Descriptions ............................................................................. 127 7.3.1 OUT OF COVERAGE.............................................................. 127 7.3.2 HIGH DL INTERFERENCE ..................................................... 127 7.3.3 HIGH UL INTERFERENCE ..................................................... 128 7.3.4 UL/DL IMBALANCE ............................................................. 129

8 WCDMA Feature Description: Cell Capacity Analysis ... 131 8.1 Prerequisites ....................................................................................... 131 8.2 Technical Description ..................................................................... 131 8.3 View Descriptions ............................................................................. 132

8.3.1 DOWNLINK RESOURCE USAGE ........................................... 132 8.3.2 UPLINK RESOURCE USAGE .................................................. 133

9 WCDMA Feature Description: KPI Views ........................ 135 9.1 Prerequisites ....................................................................................... 135 9.2 Technical Description ..................................................................... 135 9.3 View Descriptions ............................................................................. 136

9.3.1 ACCESSIBILITY ....................................................................... 136 9.3.2 RETAINABILITY ...................................................................... 137 9.3.3 MOBILITY .............................................................................. 138 9.3.4 DATA INTEGRITY .................................................................. 139

10 LTE Feature Description: KPI Views ................................. 141 10.1 Prerequisites ....................................................................................... 141 10.2 Technical Description ..................................................................... 141 10.3 View Descriptions ............................................................................. 142

10.3.1 ACCESSIBILITY ....................................................................... 142 10.3.2 RETAINABILITY ...................................................................... 142 10.3.3 MOBILITY .............................................................................. 143 10.3.4 DATA INTEGRITY .................................................................. 143

Appendix A. MapInfo MapXtreme® Layer Control ................... 145 Introduction ........................................................................................................... 145 Setting the Map Window................................................................................. 145

VIEW TAB ............................................................................................... 146 EDITING TAB............................................................................................ 147 TOOLS TAB .............................................................................................. 149 EXTENTS TAB ........................................................................................... 150


Contents • xxiii

COORDINATE SYSTEM TAB .................................................................... 150 Inserting Layers .................................................................................................... 151

OPTIONS TAB .......................................................................................... 151 EXTENTS TAB ........................................................................................... 152 INFORMATION TAB ................................................................................. 153

Inserting Layers to be Labeled ...................................................................... 154 VISIBILITY TAB ......................................................................................... 154 AUTOLABEL TAB ..................................................................................... 155 STYLE TAB ............................................................................................... 156 TEXT TAB ............................................................................................... 157 POSITION TAB ......................................................................................... 158 RULES TAB ............................................................................................... 159

Editing Layers and Labels ................................................................................ 160 Adding a Theme to Layers or Labels .......................................................... 160 Adding Style Overrides to Layers ................................................................. 161 Opening Tables .................................................................................................... 162

Glossary of Terms ............................................................................ 163

Index .............................................................................................. 167


Introduction • 1

1 Introduction TEMS Visualization Enterprise is an automated client-server system for performance optimization and problem troubleshooting of wireless cellular networks. It retrieves and analyzes event data collected by the networks for two main purposes:

• Automatic diagnosis of network issues that have a negative impact on network performance or user experience

• Creation and geographic presentation of information to support optimization decisions (for example, to assist in defining neighbor relations and optimizing cell coverage areas)

1.1 System Overview

The TEMS Visualization Enterprise Server is the heart of the TEMS Visualization Enterprise system. The Server automatically retrieves and analyzes Ericsson OSS log files. The analysis results are stored in an internal database. Only administrators may interact with the Server and configure operational settings.

The TEMS Visualization Enterprise Client is the front end of the system. Multiple Clients may be connected to the Server at the same time. Via the Clients, regular users may access the analysis results stored in the database in order to view information, troubleshoot, configure, and optimize the network.

This user’s manual is written for the TEMS Visualization Enterprise Client user.

2

1.2 Bridging the Optimization Gap Performance management tools show cells that are having problems statistically, but the exact causes of the problems, or the locations of the problems within the cell, are usually not provided. Drive test tools, on the other hand, are specifically designed to reveal the causes and locations of problems, but can only capture this critical data if the problems are more or less constant, and can only capture the data when a drive test happens to be made.

TEMS Visualization Enterprise bridges this gap by offering both the breadth of traditional performance management solutions and the depth of drive test tools. TEMS Visualization processes event-based OSS data all the way down to the individual call level. This ability to look at real individual call data from the infrastructure side complements both the big picture provided by performance management systems and the thin slicing of traditional drive testing. TEMS Visualization analyzes data sets with amounts of data large enough for statistical accuracy while offering detailed drill-down to facilitate precise problem localization.

High volume /Great detail

Low volume /Great detail

Stats

Drive

High volume /Little detail


Introduction • 3

1.3 What's New in This Release TEMS Visualization 8.0 Enterprise enhancements include the following:

• Ericsson WCDMA GPEH Module

− Support for Ericsson W11A release

− Phone Model KPIs – find and analyze worst performing phone models

− Dropped Call Analyzer – identify common factors behind dropped calls

− Cluster based analysis – import or define geographic cell clusters and troubleshoot performance per cluster

− Geo-located maps – plot and analyze maps of dropped calls and pilot pollution for a selected geographic area, subscribers as virtual drive tests

− Sequence Delay Histogram – analyze delays in message signaling

− Call Search – find calls based on specific search criteria

− NAS message decoding – investigate signaling between UE and core

− Scanner ID filter – ensure only messages for the TEMS Visualization profile on the OSS-RC are processed

• Ericsson LTE Cell Trace Module

− RF Charts – analyze RF and throughput performance per cell

4

1.4 Key Concepts

Automated Data Retrieval

TEMS Visualization Enterprise can be configured to automatically and continually retrieve Ericsson OSS log files at scheduled intervals from a secure FTP server. With this feature, users will have the latest available data from the network, without needing to download it manually.

Automated Data Processing

TEMS Visualization Enterprise automatically decodes and analyzes the retrieved Ericsson OSS data and makes the latest information directly available for all users in almost real time.

The raw data from the decoded log files and the analysis results are stored in separate databases. This separation of raw and analyzed data means that analysis results can be based on large data sets, leading to more accurate problem diagnostics and better optimization decisions.

Central Data Storage

TEMS Visualization Enterprise stores all information in a central database, making information available for all users. With this feature, all users are guaranteed to have access to the same information. There is no risk of basing incorrect decisions on local, out-of-date log files.

Automated Network Diagnosis

TEMS Visualization Enterprise automatically finds network problems, highlights them, and indicates possible causes. With this feature, users will be able to quickly find out what problems they have in their networks without spending time manually analyzing the collected data.

Optimization Decision Support

TEMS Visualization Enterprise provides optimization support in two areas:

• Neighbor Optimization. Statistics are presented in tables and on the map to support the engineers when deciding which neighbors to add or remove to ensure the best possible performance in a network area.

• Coverage Area Optimization. Statistics are presented in tables and on the map to help engineers decide when cell coverage extends too far, thus creating areas of high interference and non-dominance.


Introduction • 5

1.5 OSS Overview TEMS Visualization Enterprise works with data gathered by the optional event-based data collection features found in the Ericsson WCDMA and LTE systems. In WCDMA, this function is known as General Performance Event Handling (GPEH). In LTE, it is known at CellTrace.

TEMS Visualization Enterprise supports Ericsson WCDMA system releases P6 to W10B, and Ericsson LTE system releases L10A, L10B, and L11A.

1.5.1 WCDMA GPEH For Ericsson WCDMA, the application for recording event data on an area of cells is known as GPEH.

The GPEH application in OSS-RC enables the collection, retrieval, and storage of event data collected from network elements in WCDMA RAN. The files are generated from the network elements (i.e., RNC) and are collected together in the OSS-RC file storage.

GPEH collects both internal RNC event data, which gives very detailed RNC internal information that is not possible to collect using protocol analyzers and external event data from protocol groups such as RRC (Uu interface), RAN (Iu interface), RNSAP (Iur interface), and NBAP (Iub interface).

In OSS-RC, the collected event Result Output Period (ROP) files are stored in local file storage, enabling easy FTP retrieval from OSS-RC to TEMS Visualization for post-processing into the databases.

1.5.2 LTE Cell Trace For Ericsson LTE, the application for recording event data on an area of cells is called CellTrace.

The CellTrace application enables the collection, retrieval, and storage of event data. The files are generated in the eNodeB and are collected together in the OSS-RC file storage.

CellTrace can collect 3GPP defined “external” messages on all interfaces to/from the eNodeB. For example all RRC protocol messages exchanged between the eNodeB and UE on the Uu interface can be recorded. Also, all communication with the evolved packet core (on the S1 interfaces) and other eNodeB (on the X2 interfaces) can be recorded.

In OSS-RC, the collected event Result Output Period (ROP) files are stored in local file storage, enabling easy FTP retrieval from OSS-RC to TEMS Visualization for post-processing into the databases

6

1.5.3 Cell Configuration Files Cell configuration files are used by TEMS Visualization to get information about the parameter settings and other network configuration information stored in the OSS-RC.

Only selected parameters are used by TEMS Visualization. A reference file can be used when information such as the site position, antenna beamwidth, and antenna direction is not available from the OSS-RC.

1.6 Installation, Help and Support The System Setup document describes the prerequisites and steps necessary to successfully install and run TEMS Visualization 8.0 Enterprise Client.

For product support, contact information, and further information about TEMS products, please visit Ascom Network Testing on the web at:

www.ascom.com/networktesting

http://www.ascom.com/networktesting�


Navigating the UI • 7

2 Navigating the TEMS Visualization Enterprise Client UI

To launch TEMS Visualization Enterprise Client, browse to Start | All Programs | Ascom | TEMS Products | TEMS Visualization 8.0 Enterprise and select TEMS Visualization 8.0 Enterprise Client.

Note: In order to launch the TEMS Visualization Enterprise Client, the HASP USB hardware license key must be connected to the TEMS Visualization Enterprise Server.

The TEMS Visualization Enterprise 8.0 Client features a user interface that incorporates Microsoft® Office 2007 style ribbons, navigation panes, tabbed windows, tool tips, and on-line help. Each ribbon is divided into logical ribbon groups. The screen capture below illustrates a typical user session.

8

2.1 Application Button & Quick Access Toolbar

Pull down the Application Button for immediate access to the following:

Connect to TEMS Visualization Enterprise Server. Launches the Connect to TEMS Visualization Enterprise Server window. For more information, see Starting the System.

Load Workspace. Opens the Load Workspace dialog. For more information, see the description of the functions on the Workspace tab.

Save Workspace As. Opens the Save Workspace window. For more information, see the description of the functions on the Workspace tab.

The Export function applies to the currently highlighted application window. It enables the user to store the window’s content as an XML or image (BMP, GIF, or JPG) file, depending on its content. Note that the Export feature automatically selects the type of export available for a window. Not all views support the Export feature.

Page Setup. Opens the Page Setup dialog, where paper size, document orientation, and margins can be set.

Print Preview. Opens the Print Preview dialog, where you can adjust the zoom or layout of image before it is printed.

The Print function applies to the currently highlighted application window. It enables the user to print the content of the window via the standard Print dialog.

Exit. Closes the TEMS Visualization Enterprise application.

The Quick Access toolbar, whose default location is at the top left above the ribbons, also provides easy access to commonly-used functions.

Connect to TEMS Visualization Enterprise Server. Launches the Connect to TEMS Visualization Enterprise Server window. For more information, see Starting the System.

Save Workspace As. Opens the Save Workspace window. For more information, see the description of the functions on the Workspace tab.



The Export function applies to the currently highlighted application window. It enables the user to store the window’s content as an XML or image (BMP, GIF, or JPG) file, depending on its content. Note that the Export feature automatically selects the type of export available for a window. Not all views support the Export feature.

The Window Manager provides a quick and efficient way of managing the many views. See the description of the Window Manager for more information.

The down arrow menu at the right of the Quick Access toolbar offers the options to display the toolbar either above or below the ribbons, and to minimize the ribbons.

2.2 Home Tab

The Home tab provides access to the most frequently used TEMS Visualization Enterprise Client functions.

Defining the Data Scope is the starting point for a TEMS Visualization session. The tools in this ribbon group define the set of data to be retrieved. For more information, see page 28.

The Home tab also provides access to the Map, the Overview Statistics, and each data view (the exact items listed will differ depending on whether a WCDMA or LTE project is selected). Detailed descriptions of each view are provided later in this user’s manual.

2.3 Workspace Tab

When TEMS Visualization Enterprise Client is closed, the layout, including the scope selected and views displayed, will automatically be saved to a workspace called “Auto Saved.” The next time the Client is launched, all windows will reopen and display as they were when the previous session ended, enabling users to continue working where they left off when they closed the application. Additionally, users can save and name their own workspaces.

The workspace currently being used is always named in the title bar, as well as in the Workspace Selection dropdown menu. The dropdown menu lists all previously-saved workspaces.

10

Load Workspace. To load a previously-saved workspace, click the Load Workspace button. The Load Workspace dialog will be displayed. The currently-loaded workspace will be listed at the top of the dialog. Select the desired workspace and click Load.

Save Workspace As. The Save Workspace dialog is similar to the Load Workspace dialog. To save a workspace under a new name, enter the new name in the Workspace Name field. The default location works well for most users, but if you would like to change the default workspace folder, click on the Browse button and select the one you want. Click Save to complete the operation.

Right-Click Menu. Options to copy, delete, or rename a workspace are available from the right-click menu on both the Load Workspace and Save Workspace dialogs. Simply select any listed workspace, right-click, and select the desired option from the right-click menu. (If a workspace is currently open, it cannot be deleted or renamed.)



Load New UI Style. TEMS Visualization Enterprise Client offers several different styles, which are sets of formatting choices that affect the color of the user interface. The default is called tv80.isl, but the user can choose other pre-defined options from the Styles dropdown menu.

If you have access to additional styles that you would like to use, click the Load New UI Style button, and navigate to the desired Infragistics Style Library.

2.4 Window Tab

The Window tab provides access to tasks related to managing the data views.

2.5 Tools Tab − Cell Data Status Monitor

The Tools tab provides access to a tool called the Cell Data Status Monitor. This monitor provides server side information about how well the cell configuration file and the reference cell file match for a specific project. A poor match between the files will negatively affect the server’s analysis and processing capabilities, which may result in information not being available on the client side.

12

The Cell Data Status fields are described below.

Bulk CM Cells Count. This field lists the number of cells in the selected cell configuration file saved to the database. All cells are saved, regardless of whether a match has been made with the reference data.

Reference Cells Count. This field lists the number of cells in the selected reference cell file.

Matching Cells Count. This field lists the number of matching cells, according to the cell matching settings, between the cell configuration file and the reference cell file. If the Matching Cell Count is greater than the Reference Cell Count, check the matching criteria for duplicates. (For example, is the same cell name used in more than one RNC?)

No Lat/Lon Cells Count. This field lists the number of cells that are, after matching, saved to the database without valid positioning information.

No Antenna Beamwidth Cells Count. This field lists the number of cells that are, after matching, saved to the database without valid antenna orientation information.

No Antenna Orientation Cells Count. This field lists the number of cells that are, after matching, saved to the database without valid antenna orientation information.

Note: As part of the matching process, the “assign blank values” option can be used to ensure that values for Lat/Lon and Antenna Orientation only come from the reference cell file and never from the cell configuration file.



2.6 Help Buttons Three buttons at the upper right of the user interface provide access to the TEMS Visualization Enterprise Client license information, the About box, and help files.

2.6.1 License Information The License Information dialog lists the features that have been licensed for

use with the TEMS Visualization Enterprise installation, along with related expiration information. TEMS Visualization Enterprise 8.0 supports two feature types: Ericsson WCDMA GPEH and Ericsson LTE Cell Trace.

Key ID. This field shows the unique hardware identifier of the attached USB HASP key, in both decimal and hexadecimal formats.

IP Address. This field shows the IP address of the computer to which the key is attached. If this computer is the local host, the IP address shown will always be the 127.0.0.1 (loopback) address.

Host Name. This field lists the name of the local host.

# of Licenses. This field lists the number of feature licenses authorized for this key.

Expiration Date. This field lists the expiration date of the licenses.

14

2.6.2 About The About box lists software build and product version information. The box

also includes the Tech Support button, which provides quick access to the Ascom Network Testing web site, and the System Info button, which launches a standard Microsoft utility that displays system configuration information.

2.6.3 Help The Help button provides access to the TEMS Visualization Enterprise on-

line help and a PDF copy of the user’s manual.

2.7 Status Bar The status bar at the lower edge of the user interface shows the names of the user, the server, and the database, along with the authentication method.



2.8 Data View Management The View Manager tasks are accessed from the Window tab.

2.8.1 Display Control

Pin All. The Pin All option pins all unpinned windows to the canvas and disables the auto-hiding feature. Note that floating windows remain unaffected by Pin All.

Unpin All. The Unpin All option makes all windows become auto-hiding sliding windows. When not under the mouse cursor, the windows will automatically slide (hide) into a small tab on the application frame. To view a specific window again, move the mouse cursor over that window’s tab and it will slide out. Note that floating windows remain unaffected by Unpin All.

Show All. The Show All option reopens all closed (hidden) windows.

2.8.2 Window Manager

The Window Manager dialog provides a quick and efficient way of managing the many views. Multiple views can be selected by holding down the left mouse button in the list box and then dragging the mouse cursor over the screen.

16

The Name column displays the icon and name of a currently open view. Note that the view may be open but not visible (it may be closed/hidden).

The Description column shows the first line of the view description tooltip. Moving the mouse cursor over a line in the Description column will show the whole tooltip. The tooltip displays information about the current project, the number of ROPs in the view scope, and the time it took to fetch the current view data. Note that the various charts do not have tooltips.

Show. The Show button reopens closed/hidden windows. When a window is closed, data previously displayed in the window is still intact. No database query has to be made to repopulate it.

Unpin. The Unpin button makes windows become auto-hiding sliding windows. When not under the mouse cursor, the windows will automatically slide (hide) into a small tab on the application frame. To view a specific window again, move the mouse cursor over that window’s tab and it will slide out.

Dispose. The Dispose button completely removes windows from memory, along with all the data that was displayed in them. When a disposed window is reopened, a database query must fetch the data again.

2.8.3 View Docking Views in TEMS Visualization Enterprise are either in a floating state or in a docked state. When a window’s title bar is grabbed, docking points are displayed. By moving the window to one of these docking points and releasing the window, the window ”docks” at the specified location.

To undock a docked window, double-click on the window’s title bar. Note that the window must be in the pinned docking state to undock.

Holding down the Control key while moving a data view will hide the docking indicator and enable the user to freely move the window without accidentally docking it into another frame.



2.8.4 View Buttons All views in TEMS Visualization Enterprise offer useful window management features accessible through a set of buttons located within the view itself. Not all windows offer the full range of windows management features.

The View Data Scope Information dropdown displays information about the current scope such as the project name, selected ROPs, and query times. This feature is particularly useful when multiple locked windows with different scopes are being displayed at the same time.

The Close button closes the window but keeps it in memory. Hence the window can be opened again from the toolbar with all content intact. This makes it possible to close windows that are fetching data from the database and open them at a later time when the data has been retrieved. To clear content and dispose the window, use the dispose feature in the Window Manager.

Clicking the Refresh button reloads the selected ROPs without displaying any additional information. This is useful when a new project is loaded and the default scope has changed.

The Overview Statistics view and the Map view are automatically updated when the scope changes. All other (unlocked) views will be cleared of data. One way to repopulate the windows with data is to click the Refresh button.

By default, every new window is unlocked. This means that when the scope changes, the window will be cleared. To keep the current data in a window, the window can be locked. When the window is locked the data will remain even though scope changes. This allows comparison of data between multiple windows of the same type but with different content in each one. Once a window is locked it cannot be unlocked or refreshed.

Many windows contain sub-sections that can be minimized to increase the viewing space of other parts of the window. Selecting the feature again restores the sub-section to its original size.

Docked windows are either in pinned or in auto-hide mode. When a floating window is docked it always ends up in pinned mode. Pinned windows may not be moved from their location without becoming floating windows. By un-pinning or setting the window in an auto-hide state, the window will slide into the TEMS Visualization application frame when the mouse cursor clicks outside the unpinned window. Once the window is hidden, a tab on the application frame with the window name will appear. Clicking on this tab will restore and display the hidden window.

18

2.9 Chart Zoom To zoom in on a chart section, click at the start of the section and, while holding down the left mouse button, move the mouse cursor to the end of that section.

When the mouse button is released, the chart will zoom in on the new specified area.

To zoom back out, click the circle button on the scrollbar.



2.10 Working with Tables Many of the data views within TEMS Visualization Enterprise present data in the form of tables (grids). The “Row Count” line at the top of each table lists the number of rows in that table.

The contents of tables can be filtered according to their column values. Additionally, column summaries such as count, average, and standard deviation can be displayed.

Column filters can be added in one of two ways.

1. The simplest way is to right-click on a cell in the column and select the Filter By Selection option from the right-click menu. This will filter out all rows whose column value does not match the content of the selected cell.

2. The other way is to specify the filter properties in detail for the selected column by using the filter input located just under the column heading. The filter input allows specification of the filter operator (less than, greater than, equal to, etc.) and the filter value.

Alphanumeric Filters Mathematical Filters

Clears all filter criteria

Starts with

Contains

Ends with

Does not start with

Does not contain

Does not end with Does not match

Not like

= Equals ≠ Does not equal < Less than > Greater than ≥ Greater than or equal to

To remove a specific column filter, click the Clear button in the filter input or right-click on a cell in the column and select Remove Filter from the right-click menu.

20

To remove all column filters, click the Clear All button to the very left in the filter input row or right-click on a cell in the column and select Remove All Filters from the right-click menu.

To add a summary section for a column, click on the sigma symbol in the column heading. This will open the Select Summaries dialog. From this dialog, check the boxes for all the summaries to be added.

• For Average, null values are interpreted as 0 and taken into account.

• For Count, null values are also taken into account.

• For Minimum, null values are ignored.

To see summaries for values other than null, create a column filter to show only non-blank values.

To remove a summary for a column, click the sigma symbol in the column heading and uncheck the summary to be removed.

To remove all column summaries, highlight a cell, right–click, and select Remove All Summaries from the right-click menu.



An often-used feature when working with tables is the Copy Cell Value option. This option, available on many of the right-click menus throughout TEMS Visualization Enterprise, copies the name of the selected cell to the clipboard. It can then be pasted into the Search Text fields on views such as the Map.

And finally, the Export feature allows a table to be exported to the location of the user’s choice in the form of an Excel file.

2.11 Workflow To fully utilize the features in TEMS Visualization Enterprise Client, one should have a good understanding of the built-in information workflow.

The following figures illustrate the intended workflow. In the diagrams on the following page, a feature represented by an orange box must be explicitly populated by another feature. Solid arrows or notes indicate the populating feature.

22

WCDMA GPEH Workflow:

Selecting a cell in these view tables triggers a synchronization update in the other view tables,

highlighting the same cell in all windows

Additionally, each view offers further drilldown to Call Analysis

Connect to Server

Map View

RF Distribution Chart RF Scatter Chart

Capacity Chart

Subscriber KPI,

Subscriber Group KPI

RFDiagnostics

Coverage Area Optimization

ExceptionAnalysis

Measurement Chart

Overview Statistics

Pie Chart

Call AnalysisCall Analysis

Neighbor Optimization

Populated from Map or any other view where cell can be selected

All cells involved in scope shown on map

Map can be populated with themes from cell based statistics and

other data from many different views

Cell clusters can be created and managed

using the Cluster Manager tool

Cell KPI,Cluster KPI

Select Scope

Phone Model KPI

Dropped Call Analyzer

Histogram

Call Search

Time ChartCluster Manager

Cell Capacity Analysis

Neighbor Change Request

Geo-locate selected dropped calls on map

Follow best server changes for selected call on map

LTE Workflow:

Selecting a cell in these view tables triggers a synchronization update in the other view tables,

highlighting the same cell in all windows

Additionally, each view offers further drilldown to Call Analysis

Connect to Server

Map View

RF Distribution Chart RF Scatter Chart

ExceptionAnalysis

Measurement Chart

Call AnalysisCall Analysis

Populated from Map or any other view where cell can be selected

All cells involved in scope shown on map

Map can be populated with themes from cell based statistics and other data from

many different views

Cell clusters can be created and managed using the Cluster Manager tool

Cell KPI,Cluster KPI

Select Scope

Time ChartCluster Manager


Starting the System • 23

3 Starting the System To launch TEMS Visualization Enterprise Client, browse to:

Start | All Programs | Ascom | TEMS Products | TEMS Visualization 8.0 Enterprise and select TEMS Visualization 8.0 Enterprise Client.

Note: In order to launch the TEMS Visualization Enterprise Client, the HASP USB hardware license key must be connected to the TEMS Visualization Enterprise Server.

The first time TEMS Visualization Enterprise Client is launched, the Connect to Server dialog is displayed. The user credentials entered in the server connect dialog will determine projects and data available for access on the Client.

Server Name. Enter the computer name (the name of the local host) or IP address where the TEMS Visualization 8.0 Enterprise Server is installed. If several instances of SQL Server 2008 are installed, then the instance that should be used must be specified (e.g., “ComputerName or IP Address\ MySQLServer2008EntInstance”).

Port. Specify the port to use for communication with the server. If the field is left blank, the default SQL Server port of 1433 will be used.

Authentication. Specify the authentication, which depends on how this user was created in the SQL Server.

User Name. Specify the username, which depends on how this user was created in the SQL Server.

Password. Specify the password, which depends on how this user was created in the SQL Server.

Once the server connection has been entered and a connection established, TEMS Visualization 8.0 Enterprise Client will remember the settings for future sessions. In case the server information changes, the Connect to Server dialog can be found under the File menu in the application main menu.


Data Views • 25

4 Data Views Data views are a set of linked or synchronized TEMS Visualization windows that allow user interaction to help understand and solve common network optimization problems and scenarios.

4.1 List of Views The following table lists the TEMS Visualization data views with a brief description of each. References to full descriptions are provided.

Name Description

Map

The Map view provides a geographical presentation of network optimization related data. Many TEMS Visualization Enterprise views are synchronized with the Map view and a selection change in any of those views will cause the Map to update accordingly.

Overview

The Overview Statistics view gives a quick statistical glance of the data retrieved for the selected scope.

Cell Analysis

The Cell KPI view allows the user to see cell specific KPIs, and can be further subdivided by Service type. The Worst Cells section allows charts to be plotted of the cells that are most affected by performance issues. The individual sections for accessibility, retainability, mobility, and data integrity allow related KPI statistics for all cells in the project area to be viewed. When a specific cell is selected, the associated chart shows the variation of the KPIs related to that cell over time.

Available for WCDMA projects only, the Cluster KPI view provides cell KPI data at a group level.

Available for WCDMA projects only, the Cell Capacity Analysis view shows all cells affected by network issues identified by TEMS Visualization Enterprise as cell capacity issues.

Available for WCDMA projects only, the RF Diagnostics (MRR-W) view shows the worst affected cells for each network issue identified by TEMS Visualization Enterprise in the selected scope.

26

Name Description

Subscriber Analysis

Available for WCDMA projects only, the Subscriber KPI view allows the user to see subscriber-specific KPIs, and can be further subdivided by Service type. The Worst Subscribers section allows plotting of the IMSIs that are most affected by performance issues. The individual sections for accessibility, retainability, mobility, and data integrity allow related KPI statistics for all subscribers in the project area to be viewed. When a specific subscriber is selected, the associated chart shows the variation of the KPIs related to that subscriber over time.

Available for WCDMA projects only, the Subscriber Group KPI view provides Subscriber KPI data at a group level. (Since the user is selecting a subscriber rather than a cell, the two Subscriber KPI views are not synchronized with the other views.)

Phone Model Analysis

The Phone Model KPI view allows the user to see phone model specific KPIs. Drill-down to the device level is available, exposing data such as the worst performing cell, ROP, subscriber, and bin.

Call Search

The Call Search feature allows the user to specify several search criteria and then send all calls that meet those criteria to the Call List for further analysis.

Event Investigation

The Exception Analysis view provides an overview of all messages that occurred in the selected scope as well as TEMS Visualization events that were generated during parsing.

The Histogram view displays the elapsed time between two selected messages within the selected scope.

Optimization

Available for WCDMA projects only, the Coverage Area Optimization view has three parts. • The Overshooting Distance part provides information about

overshooting cells. • The Pilot Pollution - Threshold Based part identifies cells with RSCP

or Ec/No within user-defined thresholds and then geo-locates these areas of pilot pollution on the map.

• The Pilot Pollution - SOHO Based part identifies soft handover replacement events on active sets by potential polluters.


Data Views • 27

Name Description

Available for WCDMA projects only, the Neighbor Optimization view shows information about Intra-freq (existing neighbor usage and missing neighbors) and Inter-freq (existing neighbor usage and candidates).

Available for WCDMA projects only, the Neighbor Change Request view lists cell relations selected for modification through an Add Mutual Neighbor, Delete Mutual Neighbor, or Modify Neighbor action, initiated from Neighbor Optimization.

User-defined

Available for WCDMA projects only, the User Defined Query feature offers the user the ability to create and use custom database queries.

Other Views

The Call Analysis view allows message level analysis related to a user specified event.

The closely-associated Measurement chart shows call level details such as IEs and events plotted on a time axis.

Chart Views

The following chart views can be initiated from the Map or any of the other views where a cell can be selected for further analysis:

The RF Distribution Chart shows the distribution of RF IEs for a selected cell.

The RF Scatter Chart shows the relative distribution of RF IEs for a selected cell.

The Capacity Chart shows capacity related RF IEs on an ROP basis.

28

4.2 Data Scope The starting point for a TEMS Visualization session is definition of the set of data to be retrieved. This definition is called the “scope,” and it includes the project, the area, and time filters, all of which are selected from dropdown menus on the toolbar. Once the data scope has been defined, the application will connect to that data set the next time it is opened.

To define the scope for the project, do the following:

1. Select the project from the Project dropdown.

2. Select the RNC or LTE cell group from the Area dropdown menu.

3. Specify the dates for which data is to be retrieved.

Pull down the date menu, which will display a calendar control.

Days with data will be highlighted for easy identification.

Days with no data will be disabled or grayed out and cannot be selected. The 00:00 and 23:59 sliders filter what ROPs to show in the ROP list box based on start and end time.

4. Select individual ROPs by checking the ROP checkboxes. To quickly select all ROPs, check the checkbox in the ROP column heading.

5. Once the scope is defined, click the Fetch Data button to launch a query to obtain the data from the TEMS Visualization Enterprise Server. The first view to open will be the Map view.

Depending on the TEMS Visualization Enterprise Server data retention settings, all types of data may not always be available. The Calculated Data and Decoded Data columns in the ROP list box indicate the availability of those data types. Calculated data comes from the Analysis Database, and all analysis features with statistics will be affected if this data is missing. Decoded data (also known as message data) comes from the Primary Database, and charts graphs and detailed call-by-call investigation will be affected if this data is missing.


Data Views • 29

4.2.1 Map View

The Map view geographically displays information on top of a map background. TEMS Visualization Enterprise utilizes MapInfo MapXtreme® as the map engine, so any MapInfo compatible map (GST, MWS, TAB) can be used. TEMS Visualization Enterprise also comes with a basic world map that is displayed by default when the Map is opened for the first time.

The data views in TEMS Visualization Enterprise Client are synchronized with each other, meaning that when a cell is selected in a data view, the map will be updated accordingly. However, selecting a cell in the Map itself will not cause the other views to synchronize with that selection. The Subscriber KPI views are not synchronized with the Map, since subscribers, not cells, are selected from the Subscriber KPI views.

The Map features a dynamic multi-carrier display that automatically color codes cells to provide an easy visual separation of multiple carriers. When a cell is selected that has more than one carrier, a small window will pop up to list the available selections.

Cell Settings, accessed from the Map toolbar, offers further customization.

30

4.2.2 Map Themes The detail shown on the Map is determined by the selected Map theme. The theme type – Cell KPIs, Coverage, or Bin Plots – is selected from the Themes section in the upper right corner. Each theme type offers a different set of themes that affect the coloring of cells, cell coverage areas, and bins on the map. A legend describes the color coding.

Theme colors and ranges can be changed with the Themes Settings tool on the Map toolbar. (Themes based on the Count cannot be changed.)

Cell KPI Themes

Cell KPI themes are grouped into feature sections. The sections are loaded based on availability of data in the selected scope. For example, if the selected scope does not contain RF Issues: Out of Coverage data, then that theme section will not be available.

To select a cell-based theme section, browse to the Cell KPIs tab and choose from the dropdown menu.

Clicking on a certain theme displays that theme on the map and colors the theme selection in blue. Click the theme again to toggle off the display.

Only one theme can be displayed on the map at a time.

The cell KPI theme set differs for WCDMA and LTE projects, as described in the following lists.

WCDMA Project Cell KPI Themes

Feature Themes RF Issues: Out of Coverage

Calls Evaluated % Out of Coverage Affected Calls Out of Coverage Affected Calls % Missing IFHO/IRAT % Overshooting Cell

RF Issues: High DL Interference

Calls Evaluated % High DL Interference Affected Calls High DL Interference Affected Calls % Pilot Pollution Threshold Based % Overshooting Cell % Missing SOHO Neighbor % SOHO Block % SOHO Failure % Unmonitored SOHO Neighbor


Data Views • 31

Feature Themes RF Issues: High UL Interference

Calls Evaluated % High UL Interference Affected Calls High UL Interference Affected Calls

RF Issues: UL/DL Imbalance

Calls Evaluated % UL/DL Imbalance Affected Calls UL/DL Imbalance Affected Calls % UL Path Losses % Overshooting Cell

Capacity Issues: DL Resource Consumption

ROPs Evaluated Max DL Power (dBm) Peak Non-HS DL Power Consumption (%) DL Channel Element Capacity Peak DL Channel Element Consumption (%) Max HSDPA Users Max HSDPA Users (%)

Capacity Issues: UL Resource Consumption

ROPs Evaluated UL Interference Peak (dBm) UL Channel Element Capacity UL Channel Element Peak (%) Max EUL Served Users EUL Served Users Peak (%)

Coverage Area Optimization

ROPs Evaluated Overshooting distance (km) % Overshooting Call Establishments Overshooting Call Establishments Calls Established % Poor Ec/No Calls Established Poor Ec/No Calls Established

Cell KPI Accessibility Blocked Calls Call Attempts RRC Connection Attempts RRC Connection Blocks Initial RAB Establishment Attempts Initial RAB Establishment Blocks % Blocked Calls % RRC Connection Blocks % Initial RAB Establishment Blocks

Cell KPI Retainability Dropped Calls Normal End Calls % Dropped Calls Service Minutes Minutes Per Drop

32

Feature Themes Intra-freq HO Neighbor Optimization

SOHO Count Missing Neighbor Events Polluter Events

Inter-freq Neighbor Optimization

IFHO Attempts Candidate Events

LTE Project Cell KPI Themes Feature Themes Cell KPI Accessibility Connection Attempts

Blocked Connections % of Blocked Connections Default Bearer Setup Attempt Default Bearer Setup Failure % of Default Bearer Setup Failure Dedicated Bearer Setup Attempt Dedicated Bearer Setup Failure % of Dedicated Bearer Setup Failure

Cell KPI Retainability Normal UE Release Abnormal UE Release % of Abnormal UE Release Normal Bearer Release Abnormal Bearer Release % of Abnormal Bearer Release

Cell KPI Mobility X2 Handover Success X2 Handover Failure % of X2 Handover Failure S1 Handover Success S1 Handover Failure % of S1 Handover Failure

Coverage Themes – Available for WCDMA projects only

The coverage area optimization feature must be initiated and data for the overshooting cells must be available in order for coverage themes to be available. The NBAP RADIO LINK SETUP REQUEST message is needed for the feature to operate correctly.

To initiate the coverage area feature, launch the Coverage Area Optimization view or select a cell on the Map and then select Show Overshooting Cell Coverage from the right-click menu. To select a coverage theme, browse to the Coverage tab and select one of the following: Call Establishments, Average Ec/No, or % Call Establishments.


Data Views • 33

Bin Plots Themes – Available for WCDMA projects only

The selection of bin plot themes depends on the feature in use. For example, when using the Geo-Locate Dropped Calls feature, only one theme is available: Dropped Calls. When using the Geo-Locate Pilot Pollution feature, four themes are available: % Cell Involvements, Pilot Pollution Threshold Based Events, Average Ec/No, and Average RSCP. Selecting one of these themes color-codes the bins as described in the legend.

Bin size is selected via the Thresholds button. Click the Thresholds button to display the following grid. Click in the Min column and change the bin size as desired.

Currently, data must be reloaded when the bin size is changed. For example, assume the bin size is 100x100 meters and geo-located dropped calls are displayed on the map. If the bin size is then changed to 200x200 meters, the Geo-locate Drop Calls query must be executed again for the selected cell in order for the changes to be reflected on the map.

Legends & Layers

Legends Map Layers

When themes are being displayed, the Legends section provides information on theme names, color codes, and ranges. For cell KPI themes, the number within parentheses indicates the number of cells in each range. For coverage themes, the number within parentheses indicates the number of distance bands in each range. For bin plot themes, the number within parentheses indicates the number of bins in each range.

34

The Map Layers section lists the currently open layers. Each layer’s position on the map can be rearranged by dragging-and-dropping that layer to a different position. The checkboxes control whether each layer is enabled or disabled. Right-click on a layer to zoom to that layer on the map or to clear that layer.

4.2.3 Map Toolbar The Map toolbar provides easy access to functions needed to manipulate the map and the objects placed on the map. The toolbar’s buttons are described, from left to right, in the following sections.

4.2.3.1 Load Map File

The Load Map File feature allows the user to load MapInfo map files (GST, MWS, TAB) for display as background maps in the Map view. To unload or remove map files, use the Layer Control dialog.

4.2.3.2 Select

The Select feature puts the mouse cursor in Select mode while in the Map view. This enables the user to left-click on a single object on the map and obtain additional information about that object. These details will be displayed in the Details section.

Note: When the user right-clicks on a selected cell in the Map, a menu will appear with several options. See Right-Click Options, on page 41.

Sample Details sections are shown below.

WCDMA LTE


Data Views • 35

4.2.3.3 Draw Polygon

The Draw Polygon tool is used to create polygons and cell clusters. To begin, click the tool and then draw a boundary around the area or cells of interest. Click once each time you need to add a point to the polygon; double-click on the last point of the polygon to complete it.

An analysis menu will pop up with the following options:

• Geo-locate Pilot Pollution Threshold Based in Polygon for UARFCN. Choose this option, first selecting the carrier of interest, to plot the map with bins showing Pilot Pollution Threshold Based events. The contribution to the pilot pollution events in the bins could come from cells located both within and outside of the boundaries of the polygon.

• Geo-locate Dropped Calls in Polygon. Choose this option to plot the map showing bins where Dropped Calls occurred within the polygon. The cells where the calls were dropped could be located both within and outside of the boundaries of the polygon.

• Add to Cluster Manager. Choose this option to add the cells located within the polygon as a cluster to the Cluster Manager. Then, click Save All in the Cluster Manager to save the cluster to the database. After it has been saved, you can open the Cluster KPI view to analyze the KPIs for the cluster. (If the Cluster KPI view was already open, then click the Reload button in the Cluster Manager to get the KPIs for this newly created cluster.

The following two right-click options become available after the cluster is saved:

• Geo-locate Pilot Pollution Threshold Based for Cell Cluster for UARFCN. Choose this option, first selecting the carrier of interest, to plot the map with bins showing Pilot Pollution Threshold Based events. The contribution to the pilot pollution events in the bins could only come from cells located within the boundaries of the polygon.

• Geo-locate Dropped Calls for Cell Cluster. Choose this option to plot the map with bins showing Dropped Calls. The cells that dropped the calls in the bins could only be located within the boundaries of the polygon.

4.2.3.4 Zoom In

The Zoom In feature puts the mouse cursor in Zoom In mode. This allows the user to zoom in on the map either by clicking on the map itself or by clicking and, while holding down the mouse button and moving the mouse cursor, creating a rectangular area. When the mouse button is released the map will zoom in to fit the rectangular area in the Map. Zooming can also be done by scrolling the mouse wheel.

36

4.2.3.5 Zoom Out

The Zoom Out feature puts the mouse cursor in Zoom Out mode. This allows the user to zoom out on the map by clicking on it. Zoom Out will center on the map location where the user clicked. Zooming can also be done by scrolling the mouse wheel.

4.2.3.6 Pan

The Pan feature puts the mouse cursor in Pan mode. In Pan mode, the user grabs the map by left-clicking and holds the mouse button down while moving the mouse around as needed. When the mouse button is released, the grab will release and the map will keep its focus.

4.2.3.7 Distance The Distance feature puts the mouse cursor in Distance mode. Distance

mode allows the user to measure distances between objects/locations on the map. To start measuring, left-click once on a location on the Map. Move the mouse cursor to a new location and double-click to release and view the distance between the two locations. Double-clicking will also reset the measurement feature and allow the user to make another measurement. To measure the distance between multiple points on the map, click once to start the measurement and click once for every point to include in the measurement. Double-click to finish the measurement and view the result.

4.2.3.8 Layer Control

The Layer Control button opens the MapInfo MapXtreme® Layer Control window. From this window, the user can change the layers and themes that are presented in the map, the order of the layers, and with what visual preferences they are presented. For detailed information about MapInfo MapXtreme® Layer Control, see Appendix A.

4.2.3.9 Manage Clusters

The Manage Clusters button opens the Cluster Manager. (The Cluster Manager is also opened when Add to Cluster Manager is selected from the Draw Polygon tool menu.)

The Cluster Manager has two grids. The upper grid lists the clusters that have been defined. The lower grid lists the cells included in the cluster selected in the top grid. The right-click menu for the top grid offers the following options in addition to the standard filter, copy, and export actions:


Data Views • 37

• Save all Clusters to Database. Note that it is not necessary to save a cluster before performing analysis – simply click on a cluster boundary to access the analysis option menu.

• Show all Clusters on Map. This option shows all cluster boundaries on the map.

• Hide Clusters from Map. This option hides the cluster boundaries.

• Delete Selected Cluster(s). This option deletes the selected cluster(s) from the database.

• Zoom Map to Cluster. This option zooms the map to the selected cluster.

The example below shows three clusters. Clusters 1 and 2 have already been renamed and saved to the database. The third cluster has just been defined – its state of “ADD” indicates it has not yet been saved to the database.

The Cluster Manager includes an import option. To use it, pull down the Import Clusters menu. Any MapInfo tab files that have been loaded previously (see Load Map File) will be listed here.

38

4.2.3.10 Cell Settings

The Cell Settings feature displays the Cell Display Preferences window. From this window, the user can configure how cell sites are displayed on the map.

WCDMA LTE

The Cell Site Radius slider controls the radius of the pie chart piece used to represent cell sectors on the map.

Display filters are automatically created for the UARFCN values (for WCDMA) or EARFCN values (for LTE) detected in the Cell Configuration Data. The Display Filters table allows the user to specify:

• % Radius. The relative size of sectors with that channel number (compared to the Cell Site Radius).

• Offset. A sector drawing offset (in meters) from the center point of the site.

• Color. The color to use for each UARFCN.

4.2.3.11 Theme Settings

The Theme Settings feature opens the Themes Display Preferences window. From this window, the user can change how the pre-defined TEMS Visualization themes are displayed (i.e., the number of ranges in a theme, the range boundaries, and the colors of each range). Note: Themes based on count are not available for modification.


Data Views • 39

4.2.3.12 SC Collision Report

Available for WCDMA projects only, the SC Collision Report feature analyzes the scrambling code allocation and determines whether identical scrambling codes are used within a user-specified search radius around each cell in the cell configuration file or the reference cell file. The SC Collision distance field allows the user to specify the search radius (in kilometers). The SC Collision Report button starts the analysis and then presents the results both on the Map and in a table.

A table will be presented that shows cell name, cell ID, UARFCN, and scrambling code for each cell in the cell pair. The pair currently selected in the table will be highlighted on the map with a red line. A gray line will be drawn to connect each pair of cells within the defined search radius that have the same scrambling code.

The table can be exported to an Excel file.

40

4.2.3.13 Search

The Search button opens the Search Parameters dialog, which allows the user to locate all cells matching a specific parameter and value. The Name menu lists the parameters available for searching, and the Value menu lists any fixed values for the selected parameter. Enter the name and value and press OK. The map will be redrawn, highlighting all cells that meet the search criteria. Note that it may be helpful to use the Zoom to Layer feature to quickly locate the selected cells. (Go to Legends & Layers, right-click on the Cells entry, and click Zoom to Layer.)

4.2.3.14 Clear Themes

The Clear Themes button clears all the themes created on the Map view. To clear custom-made themes, use the Layer Control dialog.


Data Views • 41

4.2.4 Map Right-Click Options When the user clicks on a cell on the Map using the Select tool and then right-clicks, a menu will appear with the options described in the following sections.

4.2.4.1 Show All Defined Neighbors This option highlights all the defined neighbors of the currently selected cell.

In the above example:

• Magenta-colored cells are defined intra-freq neighbors of the selected cell.

• Red-colored cells are inter-freq neighbors.

• The selected cell is outlined in green.

4.2.4.2 Show Inter-Freq Defined Neighbors Available for WCDMA projects only, this option highlights all the defined inter-freq neighbors (colored in red) of the currently selected cell.

4.2.4.3 Show Intra-Freq Existing Neighbors Available for WCDMA projects only, this option highlights all the defined intra-freq neighbors of the currently selected cell. The cell bordered in blue is the selected cell whose existing neighbor relation is indicated by a line ending in a square. The color of the square is based on SOHO Count (occurrences), as described in the legend.

42

4.2.4.4 Show Missing Neighbors Available for WCDMA projects only, this option highlights the missing neighbors of the currently selected cell. The cell bordered in blue is the selected cell whose missing neighbor relation is indicated by a line ending with a circle. The color of the circle is based on MN Events, as described in the legend.


Data Views • 43

4.2.4.5 Show Inter-Freq Existing Neighbors Available for WCDMA projects only, this option highlights the defined inter-freq neighbors of the currently selected cell. The cell bordered in blue is the selected cell whose missing neighbor relation is indicated by a black line ending with a square. The color of the square is based on IFHO Attempt occurrences.

4.2.4.6 Show Candidate Neighbors Available for WCDMA projects only, this option highlights all the candidate neighbors of the currently selected cell. The cell bordered in blue is the selected cell whose candidate relation is indicated by a line ending with a circle. The color of the circle is based on Total IFHO Success from Best Server occurrences.

Additionally, a maroon-colored arrowed line points to the selected cell’s intermediate inter-freq neighbor, and a lime-colored arrowed line points to the candidate.

44

4.2.4.7 Show All Cells With Same SC Available only for WCDMA projects, this option draws a green dotted line from the currently selected cell to any other cells on the map that share the same scrambling code.

4.2.4.8 Show All Cells With Same PCI Available only for LTE projects, this option draws a green dotted line from the currently selected cell to any other cells on the map that share the same PCI.

4.2.4.9 Show All Cells With Same UARFCN and SC Available only for WCDMA projects, this option draws a green dotted line from the currently selected cell to any other cells on the map that share both the same scrambling code and the same UARFCN.

4.2.4.10 Show Overshooting Cell Coverage Available only for WCDMA projects, this option shows the cell coverage. The color code for the coverage bands is defined in the legend. For more information, see the description of the Coverage Area Optimization feature.


Data Views • 45

4.2.4.11 Geo-Locate Pilot Pollution - Threshold Based Available only for WCDMA projects, this option shows threshold-based pilot pollution events. The color code for the event bins is defined in the legend. This feature is often accessed via the right-click menu on the Pilot Pollution Threshold Based tab of the Coverage Area Optimization view.

The cell of interest will be highlighted on the map with a thick blue border. The map will be populated with color-coded bins where threshold-based Pilot Pollution events occurred. The color code is explained in the Legend.

When a bin is selected, lines will be drawn to connect the bin to all the cells that contributed to the Pilot Pollution events above a user defined threshold. The table in

46

the Bin Details section will be updated to show the cell name, the count and percentage of event involvements, the average Ec/No and RSCP for each cell involved with pilot pollution, and the distance from the cell to the selected bin.

For more information, see the description of the Coverage Area Optimization feature.

4.2.4.12 Geo-Locate Dropped Calls Available only for WCDMA projects, when this option is selected, TEMS Visualization will attempt to geo-locate all dropped calls for the selected cell (within the current scope). (Note that it may be helpful to zoom out when using this feature.) This feature is often accessed via the right-click menu on the Retainability tab of the Cell KPI, Subscriber KPI, and Phone Model KPI views.

Upon completion, a Dropped Calls Information dialog box will be displayed that lists the name of the selected cell, IMSI (subscriber), or phone make and model (or IMEI-TAC), the total number of dropped call events in that cell (or for that IMSI or phone model), and the number of dropped calls that were geo-located.

After pressing OK on the dialog, bins will be displayed on the map for each of the dropped calls that could be geo-located. The bins will be color-coded according to the number of dropped calls that occurred in them.

When a bin is selected, all the calls contributing to that bin are sent to the mini call list on the map. After a call is selected in the mini call list, lines will be drawn to the terminating cell and active set. The originating cell will be colored green. The terminating cell will be indicated by a red square. Cells marked with a yellow square were in the Active Set at the time the drop occurred.


Data Views • 47

The table in the Bin Details section will be updated to show the subscriber’s IMSI, the start and end time for the call, the call duration, the names of the originating and terminating cells, their scrambling codes, the starting and ending Service, and the release cause. If more than one dropped call occurred in the selected bin, more than one line will be displayed in the table. Also, if the Call Analysis window is open and the user selects a call in the mini call list, then the same call will be selected in the Call Analysis view.

4.2.4.13 Show RF Distribution Chart This option opens the RF Distribution Chart for the selected cell.

4.2.4.14 Show RF Scatter Chart This option opens the RF Scatter Chart for the selected cell.

4.2.4.15 Show Capacity Chart This option opens the Capacity Chart for the selected cell.

48

4.3 Overview Statistics View

Available only for WCDMA projects, the Overview Statistics view gives a quick look at the data retrieved for the selected scope. All data is retrieved from the analysis database.

The table at the top of the Overview Statistics view lists statistics per ROP. The table at the lower left and the pie chart provide more details for the ROP selected in the top table.

In the top table, each column corresponds to the count of a GPEH event or the count of a TEMS Visualization generated event (such as a dropped or blocked call). The counts are calculated for the event data recorded within the selected scope (RNC and time period). A pink-colored row at the bottom of the table displays the sum of the selected ROP statistics. Right-clicking on a highlighted cell in the table opens a menu of standard filter, copy, and export actions.

The pie chart offers further drill-down to Call Analysis. Clicking on a pie piece brings up the Call Analysis view, updated with all calls contributing to that statistic.


Data Views • 49

4.4 Cell KPI View

The Cell KPI view allows the user to see cell-specific KPIs that can be further subdivided by Service type. The Worst Cells section allows charts to be plotted of the cells that are most affected by performance issues. The individual sections for accessibility, retainability, mobility, and data integrity allow related KPI statistics for all cells in the project area to be viewed. When a specific cell is selected, the associated chart shows the variation of the KPIs related to that cell over time.

Worst Cells tab

The Worst Cells tab shows a chart of the 10 worst performing cells given the selection criteria. Simply drag-and-drop a KPI from the list on the left onto a chart to plot a graph. Up to four charts can be graphed at a time.

Generally, one KPI is plotted per chart at a time, with the exception that, when available, a line graph of rate KPIs is automatically overlaid onto a bar chart showing the count of that KPI.

Observe the labels on the vertical axes, as two cases are possible. For example, when a count KPI such as Blocked Calls is dropped on the chart, the count will be graphed on the left axis and the rate will be graphed on the right axis. Conversely, when Blocked

50

Calls Rate (%) is dropped on the chart, the rate will be graphed on the left axis and the count will be graphed on the right axis.

The columns in the chart are sorted in descending or ascending order depending on the type of KPI displayed on the left axis. The user can mouse over a column in the graph to see the content delineated by Service, which is further described by the legend beneath the graph.

• For WCDMA projects, the color coding of the bars on the chart indicates the Service, which can be filtered from the checklist in the Service dropdown menu.

• For LTE projects, the color coding of the bars on the chart indicate the QCI.

To access this checklist, click as shown here. When selecting KPIs within the same group, the Service settings will stay intact; when switching to a different group, the Service settings will reset. Before a KPI is dragged onto a chart, the Service dropdown menu will not be populated.

Accessibility, Retainability, Mobility, and Data Integrity tabs


Data Views • 51

The format of the Accessibility, Retainability, Mobility, and Data Integrity tabs is the same. Each has a table showing all cells in the project area, a Time Chart section, and a Time Grid section.

Table

The table at the top of the view lists all cells in the selected project area. Column filters can be used to focus on the desired data. Selecting a cell in this table triggers a synchronization update in the other synchronized views and in the Map view, highlighting the same cell in all views.

Right-clicking on a highlighted cell in the table opens a menu with a set of standard filter, copy, and export actions, along with the options to send the data to the chart for trend analysis, or to plot cell related IEs on the Distribution, Scatter, or Capacity Charts for further analysis.

Additional options are specific to the type of KPI:

KPI Type WCDMA LTE

Accessibility Blocked Calls, RRC Connection Blocked Calls, Initial RAB Establishment Blocked Calls can be sent to the Call List

Blocked Connections, Default Bearer Setup Failure, Dedicated Bearer Setup Failure can be sent to the Call List

Retainability Dropped Calls, All End Calls can be sent to the Call List. Additionally, Dropped Calls can be geo-located on the map.

Abnormal UE Release, Abnormal Bearer Release can be sent to the Call List

Mobility SOHO failure, IFHO failure, IRAT HO failure, IRAT CC failure, and HS Cell Change failure calls can be sent to the Call List

X2 Handover Failures and S1 Handover Failures can be sent to the Call List

Data Integrity HS data calls, EUL data calls and channel switch failures can be sent to the Call List

N/A

Time Chart

On the Time Chart section, the KPIs list indicates what KPIs are available for graphing. The parameters listed differ depending on whether the Accessibility, Retainability, Mobility, or Data Integrity tab is selected.

The chart, which shows KPI instances over time, is useful for trend analysis. It can be populated from the right-click menu in the table at the top of the window or by dragging-and-dropping the desired parameter from the list of KPIs on the left onto

52

the chart area. The data can be further filtered according to Service by checking the boxes in the list on the left. Up to three charts can be graphed at a time.

Time Grid

The Time Grid lists all ROPs in the project area. Column filters can be used to focus on the desired data. The right-click menu offers the option to send affected calls to the Call List for further analysis, along with the standard set of filter, copy, and export actions.


Data Views • 53

4.5 Cluster KPI View

The Cluster KPI view provides cell KPI data at a group level. Cell groups, or “clusters,” are created on the map by using the Draw Polygon tool. Only clusters that were created and then saved to the database will be listed on the Cluster KPI View. See the descriptions of the Draw Polygon tool and the Manage Clusters feature for more information.

In the Cluster KPI view, the top grid lists the cell clusters, with summary statistics. When a cluster is selected in the top grid, accessibility, retainability, mobility, or data integrity statistics for the cells comprising the selected cluster will be listed in the lower grid. The statistics can be further filtered by Service.

54

4.6 Cell Capacity Analysis View

Available only for WCDMA projects, the Cell Capacity Analysis view shows all cells affected by network issues identified by TEMS Visualization Enterprise as cell capacity issues.

Selecting a cell in the table triggers a synchronization update in the other synchronized data views and the Map, highlighting the same cell in all views.

The following types of cell capacity issues can be identified by TEMS Visualization Enterprise:

• DL Resource Usage

• UL Resource Usage

The table lists the cells that are experiencing the issue highlighted in the Capacity Issues list. Columns color-coded in green are issue-related. The data in these columns help identify the seriousness of the issue. Columns without a highlight color are cause-related. They provide information about the possible cause or causes for the specific issue.

Right-clicking on a highlighted cell in the table opens a menu with a set of standard filter, copy, and export actions, including the options to plot cell related IEs on the Distribution, Scatter, or Capacity Charts for further analysis.


Data Views • 55

4.7 RF Diagnostics (MRR-W) View

Available only for WCDMA projects, the RF Diagnostics (MRR-W) view shows all cells affected by network issues identified by TEMS Visualization Enterprise as RF issues.

Selecting a cell in the table triggers a synchronization update in the other synchronized data views and the Map, highlighting the same cell in all views.

The following types of RF Issues can be identified by TEMS Visualization Enterprise:

• Out of Coverage

• High DL Interference

• High UL Interference

• UL/DL Imbalance

The table lists the cells that are experiencing the issue highlighted in the Network Issues list. Columns color-coded in green are issue-related. The data in these columns help identify the seriousness of the issue. Columns without a highlight color are cause-related. They provide information about the possible cause or causes for the specific issue.

56

A details section is displayed under the issue table. This section contains a KPI list with information relevant to the specific issue. If a possible cause is measurement-based, the KPI list will be updated when that cause is highlighted.

Right-clicking on a highlighted cell in the table opens a menu with a set of standard filter, copy, and export actions, including the options to plot cell related IEs on the Distribution, Scatter, or Capacity Charts for further analysis. Additionally, the right-click menu provides an option to send all affected calls to the Call List.


Data Views • 57

4.8 Subscriber KPI View

Available only for WCDMA projects, the Subscriber KPI view allows the user to see subscriber-specific KPIs that can be further subdivided by Service type. The Worst Subscribers section allows charts to be plotted of the IMSIs that are most affected by performance issues. The individual sections for accessibility, retainability, mobility, and data integrity allow related KPI statistics for all subscribers in the project area to be viewed. When a specific subscriber is selected, the associated chart shows the variation of the KPIs related to that subscriber over time.

Worst Subscribers tab

The Worst Subscribers tab shows a chart of the 10 worst performing subscribers given the selection criteria. Simply drag-and-drop a KPI from the list on the left onto a chart to plot a graph. Up to four charts can be graphed at a time.


Observe the labels on the vertical axes, as two cases are possible. For example, when a count KPI such as Blocked Calls is dropped on the chart, the count will be graphed on the left axis and the rate will be graphed on the right axis. Conversely, when Blocked

58

Calls Rate (%) is dropped on the chart, the rate will be graphed on the left axis and the count will be graphed on the right axis.


The color coding of the bars on the chart indicates the Service, which can be filtered from the checklist in the Service dropdown menu. To access this checklist, click as shown here.

When selecting KPIs within the same group, the Service settings will stay intact; when switching to a different group, the Service settings will reset. Before a KPI is dragged onto a chart, the Service dropdown menu will not be populated.


The format of the Accessibility, Retainability, Mobility, and Data Integrity tabs is the same. Each has a table showing all subscribers in the project area, a Time Chart section, and a Time Grid section.


Data Views • 59

Table

The table at the top of the view lists all subscribers in the selected project area. Column filters can be used to focus on the desired data.

Right-clicking on a highlighted IMSI in the table opens a menu with a set of standard filter, copy, and export actions, along with the options to send the data to the chart for trend analysis, or to plot subscriber related IEs on the Distribution, Scatter, or Capacity Charts for further analysis.

KPI Type WCDMA

Accessibility Blocked Calls, RRC Connection Blocked Calls, Initial RAB Establishment Blocked Calls can be sent to the Call List

Retainability Dropped Calls, All End Calls can be sent to the Call List. Additionally, Dropped Calls can be geo-located on the map.

Mobility SOHO failure, IFHO failure, IRAT HO failure, IRAT CC failure, and HS Cell Change failure calls can be sent to the Call List

Data Integrity HS data calls, EUL data calls, and channel switch failures can be sent to the Call List

Time Chart

On the Time Chart section, the KPIs list indicates what KPIs are available for graphing. The parameters differ depending on whether the Accessibility, Retainability, Mobility, or Data Integrity tab is selected.

The chart, which shows KPI instances over time, is useful for trend analysis. It can be populated from the right-click menu in the table at the top of the window or by dragging-and-dropping the desired parameter from the list of KPIs on the left onto the chart area. The data can be further filtered according to Service by checking the boxes in the list on the left. Up to three charts can be graphed at a time.

Time Grid



Data Views • 61

4.9 Subscriber Group KPI View

Available only for WCDMA projects, the Subscriber Group KPI view provides Subscriber KPI data at a group level. Subscriber groups can be created in one of several ways – by manually entering the subscriber numbers, by importing subscriber numbers from a database, or by importing an Excel list with the required data.

In the Subscriber Group KPI view, the top table lists all defined subscriber groups, with summary statistics. When a group is selected in the top table, the subscribers comprising that group will be listed in the table in the lower table.

62

To create a new group, do the following:

1. Click the Edit IMSI Groups icon. The Select IMSI Group window will open. Click the New button.

2. The IMSI Group window will open. Enter a name for the group.

3. If you know the IMSI numbers to be included in the group, you may type them in the Source IMSI List. However, if the new group has more than a very few members, it is easier to load the numbers from a database or from a file. For example, click the Load from DB button. At the IMSI Filter window, enter the desired filter (e.g., 505*) and press OK. The window will be populated with all IMSIs in the database matching that filter. Select the desired IMSIs and click the => button to move them to the Target IMSI List

4. Click the Save button. After closing the IMSI Group window, the new group will be listed in the Select IMSI Group window.

5. Close the Select IMSI Group window. The new group will be listed on the Subscriber Group KPI view. Select the new group, and the view will be populated with data for that group.


Data Views • 63

4.10 Phone Model KPI View

Available only for WCDMA projects, the Phone Model KPI view allows the user to see phone model specific KPI values that can be further subdivided by Service type. Since grouping by phone model doesn’t always distinguish individual revisions, the option to group by IMEI-TAC allows more refined analysis.

The Worst Phone Models section allows charts to be plotted of the phone models that are most affected by performance issues. The individual sections for accessibility, retainability, mobility, and data integrity allow related KPI statistics for all phone models in the project area to be viewed. When a specific phone model is selected, the associated chart shows the variation of the KPIs related to that phone over time.

Worst Phone Models tab

The Worst Phone Models tab shows a chart of the 10 worst performing phones given the selection criteria. Simply drag-and-drop a KPI from the list on the left onto a chart to plot a graph. Up to three charts can be graphed at a time.


Observe the labels on the vertical axes, as two cases are possible. For example, when a count KPI such as Blocked Calls is dropped on the chart, the count will be graphed on

64

the left axis and the rate will be graphed on the right axis. Conversely, when Blocked Calls Rate (%) is dropped on the chart, the rate will be graphed on the left axis and the count will be graphed on the right axis.


The color coding of the bars on the chart indicates the Service, which can be filtered from the checklist in the Service dropdown menu.

To access this checklist, click as shown here. When selecting KPIs within the same group, the Service settings will stay intact; when switching to a different group, the Service settings will reset. Before a KPI is dragged onto a chart, the Service dropdown menu will not be populated.


The format of the Accessibility, Retainability, Mobility, and Data Integrity tabs is the same. Each has a table, a Time Chart section, and a Time Grid section.


Data Views • 65

Table

The table at the top of the view lists all phone models in the selected project area. Column filters can be used to focus on the desired data. Right-clicking on a highlighted cell in the table opens a menu with a set of standard filter, copy, and export actions, along with the options to send the data to the Call List for further analysis.

Time Chart

On the Time Chart, the KPIs list indicates what KPIs are available for graphing. The parameters listed differ depending on whether the Accessibility, Retainability, Mobility, or Data Integrity tab is selected.

The chart, which shows KPI instances over time, is useful for trend analysis. It can be populated from the right-click menu in the table at the top of the window or by dragging-and-dropping the desired parameter from the list of KPIs on the left onto the chart area. The data can be further filtered according to Service by checking the boxes in the list on the left. Up to three charts can be graphed at a time.

Time Grid


66

4.11 Dropped Calls Analyzer When the Dropped Calls KPI is displayed on the “Worst Cells” chart in the Cell KPI view or the Phone Model KPI view, further drill-down is available by clicking on the link at the base of each column in the chart.

A called Dropped Calls Analyzer will be displayed showing statistics for the dropped calls for that phone model, IMEI-TAC, or cell.

All the dropped calls are analyzed in terms of six orthogonal components: 1. Cell (for drill-down from Phone Model KPI) or

Phone Model (for drill-down from Cell KPI) or IMEI-TAC (for drill-down from Cell KPI)

2. Time (15-minute periods) 3. RAB Type 4. Drop Reason 5. Subscriber 6. Location (1km X 1km areas)

The three worst contributors in each component are identified and all others are listed as a group. This makes it easy to see if all the dropped calls can be attributed to one component. In the example shown below, it can quickly be seen that nearly all dropped calls come from one subscriber.


Data Views • 67

Select and then right-click on one of the “top three” worst contributors of any of the bars to access the options to send the call to the Call List for further analysis or to geo-locate the dropped calls. When the geo-locate option is selected, an information dialog will display statistics for the total number of dropped calls and how many of them were successfully geo-located.

After selecting the geo-locate option, the bins holding the dropped calls will be displayed on the map. The Legend will identify the color-coding for the various parameters.

68

4.12 Call Search

The Call Search feature allows the user to select several search criteria and then send all calls that meet those criteria to the Call List for further analysis.

The user can select one or more search criteria. A logical OR operation is applied to selected values within one search criteria category, and a logical AND operation is applied to different search criteria categories. The following search criteria categories are available:

• Originating Cells

• Terminating Cells

• IMSI

• IMEI-TAC

• End RAB

• End Event

• End Time Period

After choosing the criteria of interest, which will be listed in the Selected Criteria window, click Search. The Call Analysis view will open to list any calls found that meet the selected criteria.


Data Views • 69

4.13 Exception Analysis

The Exception Analysis view offers three sets of data: a summary of all events generated by TEMS Visualization Enterprise, a summary of GPEH or LTE Cell Trace messages, and (for WCDMA only) a summary of NAS messages.

4.13.1 TEMS Visualization Event Summary WCDMA (sample data only):

LTE (sample data only):

The TEMS Visualization Event Summary section offers drill-down to the individual call level. To use this feature, right-click on the event of interest and select Send to Call List. This will open the Call Analysis view, which will be updated with all calls contributing to that event.

70

4.13.2 GPEH / LTE Cell Trace Messages Summary WCDMA:

LTE:

The Messages Summary section also offers drill-down to the individual call level via a right-click menu. More details are available for messages displayed in bold text. When a bolded message is selected, exception types relevant to that message that are available for drill-down will be listed at the lower left of the view. When one of those exception types is selected, the table at the lower right will be updated with specific information about that exception type for the message in the message list.

Note that only messages associated with individual calls are presented in the Message Summary. Optional messages are not included.


Data Views • 71

4.13.3 NAS Messages Summary Available only for WCDMA

The NAS Messages Summary provides statistics and information for messages exchanged between the phone and the core network. Drill-down to the individual call level is available via a right-click menu.

When an NAS message is selected, exception types relevant to that message that are available for drill-down will be listed at the lower left of the view. When one of those exception types is selected, the table at the lower right will be updated with specific information about that exception type for the message in the message list.

72

4.14 Histogram View

The Histogram view displays the elapsed time between two selected messages within the selected scope. Each bar represents the count of how many message pairs occurred within the time interval indicated on the x axis. The red wavy lines toward the top of the histogram represent breaks in the y axis scale.

The top of the Histogram view contains controls used to generate the histogram. When all settings are made as desired, click the Show Histogram button.

• Calls From: Before analysis starts, Entire Scope is the only option. This creates the histogram from all of the calls in the project scope. If the histogram was accessed from another view, such as Call Analysis, a smaller selection would be available.

• Bin Resolution: The Bin Resolution spin control allows you to set the time interval for each bin, in milliseconds.

• From/To: Select the two messages for analysis.


Data Views • 73

To zoom in, click-and-drag the mouse pointer across the intervals on which you want to zoom in. Release the mouse. To zoom out, click the zoom out icon on the left side of the scroll bars. The histogram will zoom out to display the full elapsed time in the Histogram view.

You can send calls plotted in the Histogram view to the Call List by right-clicking on a bar in the view and selecting Send to Call List from the shortcut menu.

74

4.15 Coverage Area Optimization

Available only for WCDMA projects, the three tabs on the Coverage Area Optimization view provide information about overshooting cells, threshold-based pilot pollution events, and SOHO-based pilot pollution events in the selected scope.

4.15.1 Overshooting Cells Part The Overshooting Cells part of the Coverage Area Optimization view helps identify overshooting cells that may be causing areas of pilot pollution and non-dominance. An overshooting call is a call whose establishment distance is greater than the overshooting cell distance (calculated by using the overshooting cell distance multiplier, specified in the analysis thresholds, and the distance to the closest neighbor of the selected cell).

The top table lists all cells in the selected project area. The columns contain parameters relevant to coverage area optimization, and column filters can be used to focus on the desired data.

The table at the lower left contains information about the distance bands for the cell selected in the top table. The coverage area of each cell is broken down into separate distance bands (multiples of the chip distance, which is 78m). Each distance band is 234m (3*78) wide, up until 4680m, after which each distance band is 1170M (15*78) wide. Currently, the last distance band ends at 30km (30,000m).


Data Views • 75

Within the coverage area of the selected cell, the chart graphs two IEs: Call Count and Average Ec/No at call establishment.

Right-clicking on a highlighted cell in the table opens a menu with a set of standard filter, copy, and export actions, including the options to plot cell related IEs on the Distribution, Scatter, or Capacity Charts for further analysis. The right-click menu also provides the options to send all calls served by the selected cell, all overshooting calls, or all calls with poor signal strength to the Call List for further analysis.

Selecting a cell in the top table triggers a synchronization event in other synchronized views and the Map, highlighting the same cell in all views. The map will graphically show the coverage area of the cell, color-coded according to the user-selected theme. (The theme can be turned on or off by clicking the theme name in the Themes section of the Map.) Selecting a distance band in the lower left table will also trigger a synchronization event in the Map, highlighting the selected band.

76

4.15.2 Pilot Pollution Coverage – Threshold Based Available only for WCDMA projects, the Pilot Pollution parts of the Coverage Area Optimization view allow users to identify cells that are involved in two types of pilot pollution: threshold-based (areas of which can be geo-located on the map) and SOHO-based.

During the analysis performed by TEMS Visualization Enterprise, all cells reported in the measurement reports sent by the UE are examined. If more than a certain number of cells with RSCP or Ec/No within a certain threshold of the best server’s RSCP or Ec/No are detected, then a Pilot Pollution – Threshold Based event is triggered. (The user defines the number of cells and the RSCP and Ec/No thresholds.)

The Pilot Pollution – Threshold Based tab shows a chart of the 10 worst-performing cells for the selected KPI. The KPIs available for plotting are listed at the left.

The following KPIs are count values; only one KPI of that type can be plotted on a chart at a time: PP Threshold Based Events, Calls Affected PP Threshold Based, Calls Affected PP Threshold Based with IMSI, and IMSI Affected PP Threshold Based. The remaining KPIs are calculation values. When one of these is dragged onto a chart, the right vertical axis will automatically be populated with PP Threshold Based Events, and the left vertical axis will track the requested KPI. The chart is always sorted in descending order according to the value of the KPI identified on the left.


Data Views • 77

The table beneath the chart lists all cells with Pilot Pollution – Threshold Based events. Right-clicking on a highlighted cell in the table opens a menu with a set of standard filter, copy, and export actions, along with the options to plot cell related IEs on the Distribution, Scatter, or Capacity Charts for further analysis. The right-click menu also provides the options to send all affected calls to the Call List and to geo-locate Pilot Pollution – Threshold Based events on the map.

To use the Geo-Locate Pilot Pollution Threshold Based feature, right-click on the cell of interest and select the feature from the right-click menu. Then, open the Map view.

4.15.3 Pilot Pollution – SOHO Based A Pilot Pollution – SOHO Based event is triggered when the analysis detects soft handover replacement events on active sets by potential polluters (cells). Typically, the active set has a size of three cells, so an occurrence of a soft handover replacement means at least four cells are in the area, causing pilot pollution.

The table displayed on the Pilot Pollution SOHO Based tab shows statistics about polluter cells. This table helps identify cells that may need to be tuned in order to lower interference. A pink-colored row at the bottom of the table displays reciprocal cell information (reverse cell relationship information).

Right-clicking on a highlighted cell (best server) in the table opens a menu with a set of standard filter, copy, and export actions, along with the option to send the affected calls to the Call List for further analysis.

78

4.16 Neighbor Optimization

Available only for WCDMA projects, the Neighbor Optimization view shows intra-frequency information about existing neighbor usage and missing neighbors, and inter-frequency information about existing neighbor usage and candidates. It also provides a means to create neighbor relation change requests for direct input to Ericsson OSS systems.

The Existing Neighbor Usage tables, Missing Neighbors table, and Candidate Neighbors table are all synchronized, which means that when a cell is selected in one table, the other tables will automatically update according to that cell selection, highlighting the same cell in each.

When selecting a row in any of the tables, a pink-colored row may appear at the bottom of the table, depending on data availability. This row shows reciprocal cell information (reverse cell relationship information).

Intra-Frequency tab:


Data Views • 79

Inter-Frequency tab

As with other synchronized data views, the selected cell will be highlighted in the Map view. Additionally, a count of trigger events will be displayed on the map in the form of color-coded symbols attached to pie slices that represent neighbor cells.

80

The symbols displayed in front of the cells depend on the originating table. For example, if the synchronization was initiated by selecting a cell in the Missing Neighbor table, the trigger event displayed in the map will be missing neighbor events. The Existing Neighbor Usage table will trigger a display of SOHO counts. (The Candidate Usage table is not synchronized with the map.)

Symbols represent the event type and color codes represent the number of occurrences of that event type. The same color code range is used for all event types.

4.16.1 Existing Neighbor Usage – Intra-Frequency The Intra-Freq Existing Neighbor Usage table shows neighbor relation statistics for cells that have acted as serving cells during recorded calls. This table helps identify valuable intra-frequency neighbor cell relations (what cells to keep in the defined neighbor cells list), as well as relations that are not as valuable (possible candidates to remove from the defined neighbor cells list).

Right-clicking on a row (best server) in the table shows a menu with options for adding a neighbor, modifying a neighbor, or deleting mutual neighbors. For more information about making a change request, see the Neighbor Change Request section.

4.16.2 Missing Neighbors – Intra-Frequency The Intra-Freq Missing Neighbors table shows statistical data for how calls are affected by cells not defined as neighbors. This table helps identify cells that should be in the defined neighbor list.

Right-clicking on a row (best server) in the table shows a menu with options to send affected calls or missing neighbor dropped calls to the Call List for more in-depth analysis.

The option to add mutual neighbors is also available from the right-click menu. For more information about making a change request, see the Neighbor Change Request section.


Data Views • 81

4.16.3 Existing Neighbor Usage – Inter-Frequency The Inter-Freq Existing Neighbor Usage table shows neighbor relation statistics for cells that have acted as serving cells during recorded calls. This table helps identify valuable inter-frequency neighbor cell relations (what cells to keep in the defined neighbor cells list), as well as relations that are not as valuable (possible candidates to remove from the defined neighbor cells list).

Right-clicking on a row (best server) in the table shows a menu with options to send IFHO lost calls to the Call List for more in-depth analysis.

Options to add a single neighbor or mutual neighbors, to modify a neighbor, or to delete a single neighbor or mutual neighbors are also available from the right-click menu. For more information about making a change request, see the Neighbor Change Request section.

4.16.4 Candidate Neighbors – Inter-Frequency The Inter-Freq Candidate Neighbors table shows a list of candidate IFHO neighbor cells. These are cells that the UE attempted to add to the active set shortly (5 seconds) after a successful IFHO execution from the best server to a different (intermediate) cell. This table helps identify inter-frequency cells that were not defined as neighbors to the Best Server or that were neighbors with a low selection priority.

Right-clicking on a row (best server) in the table shows a menu with the option to send calls with candidate events to the Call List for more in-depth analysis.

Options to add a single neighbor or mutual neighbors, to modify a neighbor, or to delete a single neighbor or mutual neighbors are also available from the right-click menu. For more information about making a change request, see the Neighbor Change Request section.

82

4.17 Neighbor Change Request

Available only for WCDMA projects, the Neighbor Change Request view allows the user to create a list of Create, Delete, and Update requests for modifications to cell neighbor relations. The list can be exported to an Excel file for reporting purposes, or to an XML file for direct import to Ericsson’s OSS.

Alternatively, the Neighbor Change Request feature can be accessed via the right-click menu on the Neighbor Optimization view. The list of Servers at the left will automatically be populated and the OSS Action column will already indicate any requested changes if the change request originated from the Neighbor Optimization view.

To add a specific server, click the Add Server button (or right-click anywhere in the Server Information list box and select Add Server from the right-click menu).

The Add Cells From Cell Data dialog will appear, listing all the cells in the project scope. This list can be filtered by scrambling code and/or by UARFCN. Select the server of interest and click Add (alternatively, double-click on the selected server to add it).


Data Views • 83

Once the Neighbor Change Request table has been populated, the three fields at the top of the window are:

• Cell. The selected server.

• Total Existing. A count of the initially defined neighbors of the selected server, both intra and inter-frequency.

• Total Planned. A count of the planned changes to neighbor relations for the selected server, both intra and inter-frequency.

The top table lists the currently defined intra-frequency neighbors, together with their selection priorities for the selected server. If changes are made (new intra-frequency neighbors are added, the existing selection priority is changed, or a neighbor is deleted) those will also be identified here. Intra-frequency neighbors must have the same UARFCN as the selected server. The maximum number of neighbor relations for intra-frequency neighbors is 31.

The bottom table lists the currently defined inter-frequency neighbors, together with their selection priorities for the selected server. If changes are made (new inter-frequency neighbors are added, the existing selection priority is changed, or a neighbor is deleted) those will also be identified here. Inter-frequency neighbors must have UARFCNs that differ from one of the selected servers. The maximum number of neighbor relations for inter-frequency neighbors is 32.

The tables identify each neighbor’s cell name, UARFCN, scrambling code, requested OSS action (MODIFY, ADD, or DELETE), existing selection priority, and planned selection priority. The Existing Mutuality checkboxes indicate whether the selected server is a defined neighbor of each of its neighbor cells. Check or uncheck the Planned Mutuality boxes to indicate whether the cell is desired as a defined mutual neighbor.

The tables are sorted in order of Planned Selection Priority. To change the selection priority, click in the Planned Selection Priority field and type the desired priority

84

number. Click Return, and note that the OSS Action field will be updated with an action to MODIFY that cell relation.

Modifications can also be requested via a right-click menu, as described in the following paragraphs.

Add Mutual Neighbors. This option opens the Add Neighbors dialog, from which a new neighbor from the cell configuration can be selected and added. The modification will be marked as an ADD in the OSS Action column, and the selection priority assigned will be the first available in numeric sequence.

The filtering options limit the choices to cells that have a specific scrambling code or UARFCN.

When a cell is selected, a flag will indicate whether a relation already exists between the server (whose name is on the title bar) and the selected cell.

Delete Mutual Neighbors. This option marks the selected neighbor with a DELETE in the OSS Action column.

Note that if a neighbor is added for a given server (the OSS Action column indicates ADD), and then that neighbor relation is deleted, the entire line containing all information about that neighbor will be deleted from the table.

The action buttons at the top right of the window are as follows:

• Clear All. This option removes all previously added servers from the Neighbor Change Request view. Note: A single server can be deleted by right-clicking on the server and selecting Delete Server from the right-click menu.


Data Views • 85

• Export to Excel. This option creates a single Excel spreadsheet summarizing the requested changes. The spreadsheet includes a separate tab for each server. This spreadsheet can be used for reporting purposes.

• Export to Bulk CM. This option creates a separate XML file for each type of command (Create, Delete, or Update). These lists of commands can be loaded into Ericsson’s OSS. Note: To export only the changes made to a single server’s neighbor relations, select that server in the list at the left of the window, right-click, and select Export to Bulk CM from the right-click menu.

Destination Path. This field specifies where the file will be saved.

Prefix text field value and Append Timestamp checkbox. These optional settings make it easier to distinguish between multiple export files.

Ericsson Specific Attributes. The default value is 6.2.

Please consult the Ericsson OSS documentation for additional information. According to the "Bulk Interface Schema Description" document in the OSS-RC library:

"The current version number can be determined by checking the names of the BCG schema files or the network element map files delivered with this product for example EricssonSpecificAttributes.6.0.xsd, or EricssonSpecific Attributes.6.0.RBS_ NODE_MODEL J.5.16.G.4.1.xml.”

File Format Version. The default is 32.615 V4.5 (the file format is based on 3GPP TS 32.615 V4.5 and is unlikely to change).

86

4.18 User Defined Query

For WCDMA projects, TEMS Visualization offers the user the ability to create custom queries of the data in the primary database. Additionally, as an option, the search can be linked with the analysis database. Any previously-defined queries are listed in the query list, and a detailed description of the selected query, as it will be executed, is displayed in the lower part of the User Defined Query window.

A query is made of one message type at a time. The output can include all the IEs included or associated with that message, or the output can include only the IEs selected by the user.

New queries can be created, and existing queries can be edited, copied, or deleted.

While queries can be created and edited without defining the project scope, the scope must be selected prior to actually retrieving the data. Clicking the Fetch Data button launches the search for records within the first ROP of the defined scope that matches the defined criteria.

The results are presented in a table. The table rows show the values of the requested IEs at each timestamp. The table columns reflect each Expression designed in the


Data Views • 87

query. Standard TEMS Visualization Enterprise table features are available for filtering, copying, and exporting the table data.

Creating a new query involves three steps: providing general information such as query name and data source, selecting the message and IEs to be searched during the query, and designing conditions to be used during the query.

To create a new query, click New, which will open the Design New Query window. Then, do the following:

1. General Information. Enter a unique name for the query, and select the data source and version. Currently, GPEH is the only data source. The version can be any version supported by the user’s network. Press Next to continue.

2. Message and IEs selection. This section helps the user to decide what columns to show in the resultant output. Several groups of message protocols will be listed in the Message and IE Selection window, each of which can be expanded to show the messages within each group. Additionally, the search feature can be used to locate messages. (In the example shown below, a search for the word “release” located several messages, of which INTERNAL_SYSTEM_RELEASE is the desired message.)

Drag-and-drop or use the arrow button to copy the message to the Output IEs list box. By default, all of the IEs in the message will be included in the output results. The resultant output columns can be narrowed by unchecking the Output IEs box and then checking the individual IEs for inclusion.

The primary database will be searched for the IEs listed in the Output IEs list box. Optionally, associated IEs in the analysis database can be linked into the search. To include associated IEs in the resultant output, check the Output Associated IEs box, or check individual boxes, as shown below.

Press Next to continue.

88

3. Expression Designer. This section helps the user to narrow the search. The query requires search conditions, which are termed “Expressions.” Any previously-created Expressions will be listed in the Expression List. Expressions can be created, edited, or deleted from this window. After creating the desired Expression, click Finish to return to the main window, where the query can be launched.

The hierarchy of an Expression List is as follows:

− An Expression List can contain multiple Expressions. One column per Expression will be contained in the output, indicating whether the Expression was true or false. When a query contains multiple Expressions, only the OR condition will be applied between the Expressions.


Data Views • 89

− An Expression can contain multiple Condition Groups. Both AND and OR conditions can be used between two Condition Groups.

− A Condition Group can contain multiple Conditions. Both AND and OR conditions can be used between two Conditions.

− A Condition is the smallest unit that can perform a conditional operation on a selected IE.

Creating an Expression

To create a new Expression, click New. This will open a window where the Expression can be designed. Enter a unique name and an optional description. Click the Add Condition Group button . Use the dropdown box to select an IE to be used in the Condition, and then define the logic for evaluating that IE.

To add another Condition to a Condition Group, click . Select AND/OR operators between the Conditions in the Condition Group.

To add another Condition Group to the Expression, click . Select AND/OR operators between the Condition Groups.

Save the Expression. It will be now be available in the Expression List. Click Finish from the Expression Designer window to save the query.

90

Executing the Query

From the main User Defined Query window, select the query, and click Fetch Data. If the project scope has not yet been defined, a prompt to select the data scope from the scope selection toolbar will appear.

After Fetch Data is clicked, the User Defined Query Output view will appear. The table on the view will be populated with data from the first ROP available.

The Fetch tab allows the user to select a different ROP. Clicking Fetch Data again looks at that ROP for data matching the query.

The Info tab displays the query code.

The table rows show the values of the requested IEs at each timestamp. The table columns reflect selections made during query design.


Data Views • 91

4.19 Call Analysis The Call Analysis view allows message level analysis related to a user specified

event. The closely-associated Measurement chart shows call level details such as IEs and events plotted on a time axis.

The Call Analysis view is populated from a right-click option on several of the other views: Overview Statistics, Cell KPI, Cluster KPI, Subscriber KPI, Subscriber Group KPI, Exception Analysis, RF Diagnostics, Coverage Area Optimization, and Neighbor Optimization.

The table at the top of the Call Analysis view is the Call List. This table displays all calls contributing to the specific issue.

The table at the lower left of the view is the Call Messages list. This table displays the message list for the call selected in the top table. The list box to the right of the call messages shows details about the selected message.

Note that after Primary Data is removed (due to the retention policy), the Call Message list and the Message Details will not be available.

Note also that only messages highlighted in blue on the Call Messages list will update the Message Details section. When a call message is selected in the Call Message list, the best server for that message will be highlighted in blue on the Map.

92

If the desired call messages are not displayed in bold blue, it could be because they were not selected during project creation in the System Manager. In the TEMS Visualization Enterprise Server UI, in the Project Data Source Filter window, be sure the External Message Content checkboxes are checked for the desired messages.


Data Views • 93

4.20 Chart Views TEMS Visualization Enterprise offers several chart views.

The following three chart views can be accessed from the Map or from one of the other views where a cell can be selected for further analysis (such as Coverage Area Optimization, RF Diagnostics, and Cell KPI):

• RF Distribution Chart

• RF Scatter Chart

• Capacity Chart

An additional chart view, the Measurement Chart, is tightly coupled to the selected call in the Call Analysis view, and can only be accessed from that view.

Each of the chart views is populated in a similar manner. The IEs section on the left lists the Information Elements available for plotting. Simply drag-and-drop one or more IEs from the list onto a chart to display it.

The Chart Area slider allows the user to specify the number of charts to be displayed in the charting area. The minimum is one chart. The maximum is four (or three for time-synchronized charts).

The brush icon in the upper right corner of the chart clears all series from the charts, and the brush icons below an individual chart clear specific IE series from that chart.

The series checkbox specifies whether an IE is hidden or visible.

Note that a chart view will only contain information if it has been launched from the Map or from one of the other views. If a chart has been closed (hidden) after being launched, and then reopened from the Window Manager, the content will be restored.

The chart views are illustrated and further described in the following sections.

94

4.20.1 RF Distribution Chart

Drag-and-drop an IE from the list onto an RF Distribution Chart to display it.


Data Views • 95

4.20.2 RF Scatter Chart

Drag-and-drop the IE pair that will make up the X and Y axis onto the RF Scatter Chart to display the graph. Dropping an IE onto a previously configured chart will reset it with the current element as the X-axis. To display the graph, a second IE, the Y-axis, must be dropped onto the chart.

96

4.20.3 Capacity Chart Two types of charts are available in the Capacity Chart view. Each chart type offers different IEs for analysis.

• ROP Chart. Use the ROP Chart to view 95th percentile or maximum values during each 15-minute ROP.

• Line Chart. Use the Line Chart to view detailed variations in resource usage during a selected ROP.

Simply drag-and-drop one or more IEs from the list onto a Capacity Chart to display it. (This chart is available only for WCDMA projects.)

Selecting (clicking) an ROP on the bar chart will automatically drill-down to the line chart tab with the time period set to the selected ROP. Alternatively, the ROP for the Line Chart can be selected from a drop-down menu.


Data Views • 97

4.20.4 Measurement Chart To access the Measurement Chart, select the call of interest on the Call Analysis view, right-click, and select Show Measurement Chart from the right-click menu.

Simply drag-and-drop one or more IEs from the list onto a Measurement Chart to display it.

The Event Selection allows the user to add event information to the graph’s x-axis as icons symbolizing the event and lines indicating when the event occurred in time. Only the available events in a cell are listed in this section. The icons are defined in the Event Selection list.

Call End

Compressed Mode End

Soft Handover Addition Success, Soft Handover Deletion Success, Soft Handover Replacement Success

Channel Switch Success

The Details section shows information about the current active set IEs. It is a snapshot in time. The section is updated when the user selects a point by clicking on the graph for one of the plotted IEs.


WCDMA – Neighbor Optimization Feature • 99

5 WCDMA Feature Description: Neighbor Optimization

In WCDMA, an accurate neighbor plan is crucial for network performance. If a Missing Neighbor is too strong, the system will drop the call. If there are too many defined neighbors, there is a greater risk that the most important neighbors are not being measured due to lack of time. This makes optimizing the neighbor plan one of the most important tasks for a WCDMA optimization engineer.

The Neighbor Optimization feature makes it possible to easily verify the neighbor plan and find both intra-frequency and inter-frequency Missing Neighbors and non-utilized Existing Neighbors in a WCDMA network.

5.1 Prerequisites Correct setup of GPEH recordings. The GPEH messages required for basic call analysis plus the following messages must have been included in the GPEH recording.

• INTERNAL_SOHO_DS_MISSING_NEIGHBOR

• INTERNAL_SOHO_DS_UNMOITORED_NEIGHBOR

• INTERNAL_SOHO_EXECUTION

• INTERNAL_IFHO_EXECUTION

• INTERNAL_IFHO_EXECUTION_ACTIVE

Also, the OSS-RC parameter GPEHDataLevel must be set to All_Data. For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual.

Successful import of Cell Configuration Data. The calculations for the Neighbor Optimization feature require correct site coordinates be supplied – either in the cell configuration file from the Ericsson OSS-RC or in a reference cell file. Other parameters required from the cell configuration file include the defined neighbors and Selection Priority. For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual.

Correct Analysis Threshold settings. The Virtual Release Connection Offset analysis thresholds are used by the Neighbor Optimization feature. For details on how to set these parameters, see the TEMS Visualization Enterprise Server user’s manual.

100

5.2 Intra-frequency Neighbor Optimization

5.2.1 General The statistics calculated and presented in the Existing Neighbor Usage and Missing Neighbor sections help the user optimize intra-frequency Neighbor Relation definitions and their assigned Selection Priorities. Desired changes can then be sent to the Change Request section for export to the OSS.

Cells that generate Missing Neighbor events may be providing coverage in unwanted areas – and instead of adding neighbor relations, additional down-tilts or power adjustments should be applied. The Coverage Area Optimization feature can be used to determine whether cells are providing coverage in unwanted areas.

Many statistics are provided that are normalized per call. These are important because they can highlight whether the problems are real network issues (many events from many calls) or problems that only affect a single subscriber (many events from few calls).

5.2.2 Calculation of Existing Neighbor Usage The Existing Neighbor section provides detailed statistics based on soft handover evaluations and executions.

The SOHO 1 to 2 Cell statistics show the number of Soft Handover additions where only the best server existed in the Active Set and the neighbor cell was added as the second cell. Use these to help determine when a neighbor relation can be removed without major impact.

Statistics are also given on Unmonitored Neighbor events. These are generated when a soft handover addition or replacement is proposed and the trigger cell is not included in the Monitored Set but is an already defined neighbor. Use these to help determine if the correct Selection Priority has been set.

5.2.3 Missing Neighbors The Missing Neighbors section provides detailed statistics that are based on Missing Neighbor events. These events are generated when a soft handover addition or replacement is proposed and the trigger cell is not included in the Monitored Set and is not a defined neighbor.

Use the Virtual Release Conn Offset dB analysis threshold to better analyze Missing Neighbors. The number of virtual dropped calls per best server are calculated based on a higher than actual setting of the releaseConnOffset parameter. This allows the severity of Missing Neighbors to be assessed more accurately, and a parameter change can be evaluated before being implemented.



This version of TEMS Visualization Enterprise implements no “Guard Time” that would avoid counting more than one Missing Neighbor event within a short time period. All Missing Neighbor events are counted.

5.2.4 View Descriptions

5.2.4.1 Existing Neighbor Usage Column Name Description Best Server The Best Server in the active set at the time of the

event.

Defined Neighbor Count Count of the defined neighbors.

Neighbor The neighbor cell that triggered the event.

Defined Neighbor True or False. False means that the neighbor cell was not a defined neighbor – the Soft Handovers were made through the second, third, or fourth cell in the Active Set that did have this cell as a neighbor.

Selection Priority Selection Priority from the cell configuration file.

SOHO Count Number of Soft Handover additions or replacement events where the neighbor cell was added to the Active Set.

SOHO 1 to 2 Cell Number of Soft Handover additions where only the Best Server existed in the Active Set and the neighbor cell was added as the second cell.

% SOHO 1 to 2 Cell Percentage of all Soft Handover additions and replacements that were SOHO 1 to 2 cell.

Calls Served Calls Served by the Best Server during the selected scope.

UMN Events Number of Unmonitored Neighbor events. A Soft Handover was proposed to the defined neighbor, but it was reported in the Detected Set, not in the Monitored Set.

Calls Affected UMN Number of served calls that were affected by one or more Unmonitored Neighbor events.

% Calls Affected UMN Percentage of served calls that were affected by one or more Unmonitored Neighbor events.

Avg UMN Events Per Call Average Unmonitored Neighbor events per served call.

Avg UMN RSCP (dBm) Average measured RSCP of the neighbor cell when Unmonitored Neighbor was triggered.

102

Column Name Description Avg UMN Ec/No (dB) Average measured Ec/No of the neighbor cell when

Unmonitored Neighbor was triggered.

Distance (km) Distance to the neighbor cell, in kilometers.

5.2.4.2 Missing Neighbors Column Name Description Best Server The Best Server in the Active Set at the time of the

event.

Missing Neighbor Count Count of the number of Missing Neighbor cells reported against this Best Server.

Missing Neighbor The Missing Neighbor cell that triggered the event.

Missing Neighbor SC The Scrambling Code of the Missing Neighbor.

Best Server UARFCN Also the UARFCN of the Missing Neighbor cell since Missing Neighbors are only measured and reported within the same frequency.

Calls Served Calls Served by the Best Server during the selected scope.

MN Events Number of Missing Neighbor events reported against this Best Server when the Missing Neighbor cell was the trigger cell.

Calls Affected MN Number of served calls affected by one or more Missing Neighbor events.

% Calls Affected MN 100 * ( Calls Affected MN / Calls Served)

MN Calls with IMSI Number of calls with IMSI information. Compare with the Calls Affected MN column. For the remaining calls, the IMSI was not available.

IMSIs Affected MN Number of unique IMSIs that generated Missing Neighbor events. If many different IMSI contribute with Missing Neighbor events, it can be determined that this is a real issue.

Avg MN Events Per Call Average number of events per served call for this Missing Neighbor.

MN Release Events Number of Missing Neighbor events with action “Release”. For the Best Server when the Missing Neighbor was the trigger cell.



Column Name Description MN Release Affected Calls Number of served calls affected by a Missing

Neighbor event with action “Release”. For the Best Server when the Missing Neighbor was the trigger cell. Stepped maximum once per call.

% MN Release Affected Calls 100 * ( MN Release Affected Calls / Calls Served)

Avg RSCP MN Release (dBm) Average RSCP for the Missing Neighbor cell in MN Release Events.

Avg Ec/No MN Release (dBm) Average Ec/No for the Missing Neighbor cell in MN Release Events.

Calls Virtual RelCon Threshold Exceeded

Number of calls where the Virtual ReleaseConnOffset Threshold was exceeded for the Missing Neighbor. Stepped maximum once per call.

MN NoAction Events Number of Missing Neighbor events with “No Action” – Release Connection Offset NOT exceeded.

Avg MN RSCP NoAction (dBm)

Average RSCP of the Missing Neighbor cell when it did NOT result in a dropped call.

Avg MN Ec/No NoAction (dB) Average Ec/No of the Missing Neighbor cell when it did NOT result in a dropped call.

Distance (km) Distance between the Missing Neighbor cell and the Best Server.

Mutually Missing Neighbor True or False. True means that the Best Server / Missing Neighbor relationship also exists reciprocally.

5.3 Inter-frequency Neighbor Optimization

5.3.1 Technical Description

5.3.1.1 General The statistics calculated and presented in the Existing Neighbor Usage and Candidate Neighbor sections help the user optimize inter-frequency Neighbor Relation definitions and their assigned Selection Priorities. Desired changes can then be sent to the Change Request section for export to the OSS.

Many statistics are provided that are normalized per call. These are important because they can highlight whether the problems are real network issues (many events from many calls) or problems that only affect a single subscriber (many events from few calls).

104

5.3.1.2 Calculation of Existing Neighbor Usage The Existing Neighbor section provides detailed statistics based on IFHO handover executions. These show the usage and performance of already defined IFHO relations.

There may also be statistics for IFHO neighbors which are not defined to the Best Server. In this case the IFHO were made through the second, third, or fourth cell in the Active Set that did have this cell as an IFHO neighbor. Can also be a good indicator of Missing IFHO Neighbor.

5.3.1.3 Candidate Neighbors The Candidate Neighbors section provides detailed statistics on soft handover addition events that occurs a short time (currently fixed to 5 seconds) after a successful IFHO attempt to another cell. This enables identification of missing IFHO relations and defined IFHO relations that may have too low selection priority.

• Best Server – Best Server at time of successful IFHO attempt

• Intermediate cell – target of the successful IFHO attempt

• Candidate cell – cell that is added by soft handover a short time after the successful IFHO attempt

Filter on “Defined IFHO Neighbors” = False to identify true missing IFHO Neighbors.


5.3.2.1 Existing Neighbor Usage Column Name Description Best Server The Best Server in the active set at the time of the

event.

Best Server UARFCN The UARFCN of the Best Server in the active set at the time of the event.

Defined IFHO Neighbors Count of the defined IFHO neighbors according to the cell configuration file.

IFHO Neighbor If IFHO succeeded, this cell is the best server from the INTERNAL_IFHO_EXECUTION_ACTIVE.

IFHO Neighbor UARFCN The UARFCN of the IFHO neighbor.

Defined Neighbor True or False. False means that the neighbor cell was not a defined IFHO neighbor to the Best Server – the IFHO were made through the second, third, or fourth cell in the Active Set that did have this cell as an IFHO neighbor - can also be a good indicator of Missing IFHO Neighbor.



Column Name Description Selection Priority Selection Priority from the cell configuration file.

IFHO Attempts The number of IFHOs between this cell pair.

Calls With IFHO Attempts The number of calls with IFHO events between this cell pair.

IFHO Attempts Calls with IMSI The number of calls with IFHO events between this cell pair, where IMSI was available.

IMSIs with IFHO Attempts The number of IMSIs with IFHO events between this cell pair.

Avg Nbr Ec/No (dB) The average Ec/No of the Inter-freq neighbor (taken from INTERNAL_IFHO_EXECUTION_ACTIVE).

Avg Nbr RSCP (dBm) The average RSCP of the Inter-freq neighbor (taken from INTERNAL_IFHO_EXECUTION_ACTIVE).

% IFHO Success Percentage of IFHO Successes.

% IFHO Other Percentage of all other IFHO that are not Success, Reversion, or Lost.

% IFHO Reversions Percentage of IFHO Reversions.

% IFHO Lost Percentage of lost IFHO.

Distance (km) Distance to the neighbor cell, in kilometers.

5.3.2.2 Candidate Neighbors Column Name Description Best Server The Best Server at the time of the event.

Best Server UARFCN The UARFCN of the Best Server in the active set at the time of the event.

Candidate Neighbor The Candidate IFHO Neighbor cell is a cell that the UE tried to add to the active set a short time (within 5 seconds or other user-defined threshold) after a successful IFHO execution from the Best Server to a different cell. The Candidate cell was not measured for the original IFHO either because it was a defined neighbor but the Selection Priority was too low, or because it was not defined as neighbor.

IFHO Candidate Neighbor UARFCN

The UARFCN of the IFHO candidate neighbor.

106

Column Name Description Defined Neighbor True or False. False means that the neighbor cell was

not a defined neighbor – the Soft Handovers were made through the second, third, or fourth cell in the Active Set that did have this cell as a neighbor.

Selection Priority Selection Priority from the cell configuration file.

Total IFHO Success from Best Server

Total IFHO Successes from the Best Server cell. This value will be the same for all rows with candidate cells.

% Candidate Event Percentage of IFHO Successes from the Best Server that are followed (within 5 seconds or other user-defined threshold) by a SOHO addition event to the Candidate IFHO Neighbor.

Candidate Event Number of IFHO Successes from the Best Server that are followed (within 5 seconds or other user-defined threshold) by a SOHO addition event to the Candidate IFHO Neighbor.

Calls with Candidate Event The number of calls with IFHO Successes from the Best Server that are followed (within 5 seconds or other user-defined threshold) by a SOHO addition event to the Candidate IFHO Neighbor.

Calls with Candidate Event and IMSI

The number of calls with IFHO Successes from the Best Server that are followed (within 5 seconds or other user-defined threshold) by a SOHO addition event to the Candidate IFHO Neighbor where the IMSI was available.

IMSIs with Candidate Event The number of IMSIs with IFHO Executions Successes from Best Server which are followed (within 5 seconds or user defined threshold) by a SOHO addition event to the Candidate IFHO Neighbor

Avg Delta Ec/No (dB) RSCP for Candidate cell – RSCP for actual IFHO cell. Both measurements are taken from the SOHO Evaluation event.

Avg Delta RSCP (dBm) Ec/No for Candidate cell – Ec/No for actual IFHO cell. Both measurements are taken from the SOHO Evaluation event.

Intermediate Cells A list of cells that the Best Server performed successful IFHO to before the Soft Handover attempt to add the Candidate Neighbor to the active set.


WCDMA – Coverage Area Optimization Feature • 107

6 WCDMA Feature Description: Coverage Area Optimization

This feature applies only to WCDMA projects.

One of the central WCDMA network optimization activities is to ensure that cells provide the necessary coverage, but not any unnecessary coverage.

Cells that provide coverage at unintended locations can cause pilot pollution (weak overshooting cells) or lack of dominance by the proper serving sector (strong overshooting cells). Such unwanted coverage creates a loss of capacity due to overshooting interference energy and can also increase the probability of dropped calls and consume extra backhaul resources by increasing the number of soft handoffs.

The Coverage Area Optimization feature is designed to allow areas of unnecessary coverage to be quickly and easily identified. Re-tuning decisions, such as down-tilt changes, can then be made based upon analysis of statistical signal strength and location of call originations versus other cells.

The Coverage Area Optimization feature has three sections:

• The Overshooting Cells section highlights call originations on a selected cell that should belong to another cell's coverage area.

• The Pilot Pollution – Threshold Based section shows areas where a large number of cells are providing coverage in the same geographical area. These areas are geo-located on the map.

• The Pilot Pollution – SOHO Based section shows soft handover replacement events on active sets by potential polluters.

6.1 Overshooting Cells

6.1.1 Prerequisites Correct setup of GPEH recordings. The GPEH messages required for basic call analysis plus NBAP_RADIO_LINK_SETUP_REQUEST and RRC_CONNECTION_REQUEST must have been included in the GPEH recording. Also, the OSS-RC parameter GPEHDataLevel must be set to All Data. For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual.

Successful import of Cell Configuration Data. The calculations for the Coverage Area Optimization feature require correct site coordinates, antenna directions, and beamwidths to be supplied – either in the cell configuration file from the OSS-RC or in a reference cell file. For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual.

108

Correct Analysis Threshold settings. The Overshooting Cell Distance Multiplier and Poor Ec/No Threshold analysis thresholds are used by the Coverage Area Optimization feature. For details on how to set these parameters, see the TEMS Visualization Enterprise Server user’s manual.


6.1.2.1 Calculation of Overshooting Cell Distance The calculation of Overshooting Cell Distance is performed whenever cell configuration data is imported into a project. For a “one-time” project, this is done when the project is created. For a “continuous” project, the values for each cell will be updated, if changed, whenever a new cell configuration file or reference cell data file is imported.

Two steps are performed in this calculation.

First, the distance to the closest neighbor site is calculated. The figure on the following page illustrates how this is done. Basically, for Omni cells, the distance to the next closest site in any direction is taken. For Sector cells, the distance to the next closest site within the antenna beamwidth is taken.

Second, the Overshooting Cell Distance is calculated by multiplying the Closest Neighbor Site Distance by the Overshooting Cell Distance Multiplier analysis threshold. This is performed when the data processing for Coverage Area Analysis is run on the server and the resulting value is stored for each cell.

110

6.1.2.2 Calculation of Statistics When the data processing for Call Analysis is run on the Server, each call establishment is analyzed and the following information is extracted and stored:

• Call setup distance from the Propagation Delay contained in NBAP_RADIO_LINK_SETUP

• Establishment Cause from RRC_CONNECTION_REQUEST

• Ec/No from RRC_CONNECTION_REQUEST

The Propagation Delay is normally only provided in the NBAP_RADIO_LINK_SETUP message at call start on the PRACH, and not at other times.

Calls with the Establishment Causes listed below are filtered out completely (they are NOT included in any statistics). This is because these call establishments are generated by the network, not by the subscriber.

• interRAT-CellReselection,

• registration

• detach

Each subscriber-generated call is evaluated to determine if it was established further from the site than the Overshooting Cell Distance. If so, it is classified as an overshooting call establishment. Each subscriber-generated call is also evaluated against the Ec/No Poor Threshold analysis threshold.

The distance from the site is broken down into a number of bands. For each of these distance bands, the total number of subscriber-generated call establishments, the total number of overshooting call establishments, and the average Ec/No are calculated. The highest possible resolution of 234 meters (the Propagation Delay is reported in units of 3 chips) is used for the coverage distance bands close to the site.

The last distance band includes all calls established further than 30 km (18.6 miles) from the site.




6.1.3.1 Main Grid for All Cells Column Name Description Cell The involved cell.

Overshooting Distance (km)

The Overshooting Cell Distance for the cell. Calculated when the cell configuration file and/or reference cell file data are processed

% Overshooting Call Establishments

The overall percentage of subscriber-generated call establishments that were established farther from the cell than the Overshooting Cell Distance

Overshooting Call Establishments

The total number of subscriber-generated call establishments that were established farther from the cell than the Overshooting Cell Distance

Calls Established The total number of subscriber-generated call establishments in the coverage distance band

% Poor Ec/No Calls Established

Percentage of calls where Ec/No is less than the Ec/No Poor Threshold analysis threshold at call establishment. The threshold is specified on the server side when creating or editing the project

Poor Ec/No Calls Established

Number of calls where Ec/No is less than the Ec/No Poor Threshold analysis threshold at call establishment. The threshold is specified on the server side when creating or editing the project

6.1.3.2 Details Grid for Selected Cell Column Name Description Distance Band Inner (m)

The inner distance from the cell of the coverage band, in meters

Distance Band Outer (m)

The outer distance from the cell of the coverage band, in meters

Call Establishments

The total number of subscriber-generated call establishments in the coverage distance band

Average Ec/No (dB)

The average Ec/No for subscriber-generated call establishments in the coverage distance band

% Call Establishments

The percentage of subscriber-generated call establishments in this coverage distance band compared with the total for the whole cell

6.1.3.3 Chart for Selected Cell The chart shows the same information as the details grid for the selected cell.

112

6.2 Pilot Pollution - Threshold Based This feature applies only to WCDMA projects.

6.2.1 Prerequisites Correct setup of GPEH recordings. The GPEH messages required for basic call analysis plus RRC_MEASUREMENT_REPORT must have been included in the GPEH recording. Also, the OSS-RC parameter GPEHDataLevel must be set to All Data. For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual.

Cell Configuration Data. The geo-location calculations for the Pilot Pollution feature require correct site coordinates and antenna directions to be supplied – either in the cell configuration file from the OSS-RC or in a reference cell file. For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual.

Correct Analysis Threshold settings. Before execution, the project must be set up with the desired settings for the Analysis Thresholds for Pilot Pollution – Threshold Based. For details on how to set these parameters, see the TEMS Visualization Enterprise Server user’s manual.

Project Execution. When the project is executed, the correct “Analysis Execution” options must be selected to ensure the Pilot Pollution – Threshold Based events are generated and geo-located (if required).


6.2.2.1 Creation of Pilot Pollution - Threshold Based Events When the data processing for Pilot Pollution - Threshold Based is run on the Server, each Measurement Report for Soft Handover (for addition, deletion, or replacement) is analyzed. A Pilot Pollution – Threshold Based event is generated when too many cells are reported as covering in the same area.

The criteria for the generation of this event are defined by the Analysis Thresholds set at project creation:

• Pilot Pollution – Threshold Based Type – use Ec/No or RSCP for the evaluation

• Pilot Pollution – Threshold Based dB Delta – dB range (Ec/No or RSCP) from the Best Server

• Pilot Pollution – Threshold Based Number of Cells – within the dB Delta

For example, assume the following settings:



• Pilot Pollution – Threshold Based Type = Ec/No

• Pilot Pollution – Threshold Based dB Delta = 5 dB

• Pilot Pollution - Threshold Based Number of Cells = 4

With these settings a Pilot Pollution – Threshold Based event will be generated if four or more cells are within 5 dB of the Best Server Ec/No (the four or more cell count includes the Best Server). All cells within 5dB of the Best Server will be considered to be involved in the Pilot Pollution.

This event needs to be generated from RRC Measurement Reports since the internal Soft Handover events only contain information on the cells in the Active Set.

6.2.2.2 Geo-location of Pilot Pollution Threshold Based Events This option is selected at the time of project execution. The events are geo-located based on an OTDOA algorithm that utilizes the information from the Measurement Reports.

For data generation, each Pilot Pollution – Threshold Based event is assigned to a 50m x 50m geographical bin. The display of the bins can be set on the client to be any multiple of 50m x 50m.

6.2.2.3 Creation of Pilot Pollution Threshold Based Statistics Statistics are calculated for Pilot Pollution Threshold Based events. These events are based on all Measurement Reports for Soft Handover additions, deletions, replacements, or changes of best cell. They are aggregated values per cell. Statistics presented are for cell “involvement” in Pilot Pollution.

Cell involvement means any cell that was within the user-defined dB delta of the best server when Pilot Pollution occurred. The involved cell could be the best server at that time, it could be a cell in the active set, or it could just be any other cell with a measured Ec/No (or RSCP) close to the strongest cell. For example, if there must be four or more cells within 5 dB to trigger Pilot Pollution, then there could be four, five, six, seven, or even more cells within the 5 dB range – or involved in Pilot Pollution – when each event is generated.

114


6.2.3.1 Chart for Worst Cells The chart can be populated with any statistic from the Main Grid. The “worst” 10 cells are shown.

6.2.3.2 Main Grid for All Cells Column Name Description Cell The cell involved in the PP Threshold Based event.

PP Threshold Based Events

The number of Threshold Based Pilot Pollution events where this cell was involved.

Calls Affected PP Threshold Based

The number of calls affected by Threshold Based Pilot Pollution events where this cell was involved.

Calls Affected PP Threshold Based with IMSI

The number of calls affected by Threshold Based Pilot Pollution events where this cell was involved. and the IMSI was available in those calls.

IMSI Affected PP Threshold Based

Number of unique IMSIs for which Pilot Pollution – Threshold Based events occurred where this cell was involved. Helps to determine if this is a real network issue or only a problem for a limited number of subscribers.

Avg Cells in PP Threshold Based Events

When a Pilot Pollution – Threshold Based event occurs, the number of cells measured within the dB range of the Best Server is counted and the average for all events is calculated. The average will always be equal to or larger than the Analysis Threshold setting “Pilot Pollution – Threshold Based Number of Cells.”

Total Cells in All PP Threshold Based Events

Total cells involved in all Pilot Pollution – Threshold Based events with this cell.

Avg RSCP at PP Threshold Based (dBm)

Average RSCP for this cell over the Pilot Pollution Threshold Based events with which this cell was involved.

Avg Ec/No at PP Threshold Based (dB)

Average Ec/No for this cell over the Pilot Pollution Threshold Based events with which this cell was involved.



6.2.3.3 Details Grid for Selected Bin Column Name Description Cell The cell involved in the PP Threshold Based event.

PP Threshold Based Event Involvement

Number of PP Threshold Based events within this bin with which this cell was involved.

% PP Threshold Based Event Involvement

The percentage of PP Threshold Based ED event involvement of this cell in the selected bin. Calculated as: (PP Threshold Based Event Involvement / Total PP Threshold Based Events in the selected bin) * 100

Avg Ec/No for Cell in PP Threshold Based Events (dB)

Average Ec/No for this cell over the Pilot Pollution Threshold Based events with which this cell was involved.

Avg RSCP for Cell in PP Threshold Based Events (dBm)

Average RSCP for this cell over the Pilot Pollution Threshold Based events with which this cell was involved.

Distance (km) The distance from the selected bin to the cell involved in PP-THR.

116

6.3 Pilot Pollution - SOHO Based This feature applies only to WCDMA projects.

6.3.1 Prerequisites Correct setup of GPEH recordings. The GPEH messages required for basic call analysis plus the following messages must have been included in the GPEH recording.

• INTERNAL_SOHO_EXECUTION

For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual.

Project Execution. When the project is executed, the correct “Analysis Execution” options must be selected to ensure the Pilot Pollution – SOHO Based events are generated.


6.3.2.1 Creation of Pilot Pollution - SOHO Based Events The Pilot Pollution - SOHO Based analysis detects soft handover replacement events on active sets by potential polluters (cells). This means that when a soft handover replacement occurs then there are at least 4 cells in the same area.

The replacing cell that has triggered a replacement event is considered a polluter. The best server of the active set is considered the polluted server.

Depending on the severity of the pilot pollution a soft handover replacement attempt can have a successful or failed outcome. In the worst case scenario, a failed attempt can lead to the connection release or drop of call.

6.3.2.2 Creation of Pilot Pollution – SOHO Based Statistics Statistics are calculated for Pilot Pollution - SOHO Based events. These events are based on all Soft Handover replacements. They are aggregated values per cell.

An example of how the statistics are incremented is given below.

Example of soft handover replacement:

• Active Set before Soft Handover Replacement: Cell A, Cell B, Cell C.

• Active Set after Soft Handover Replacement: Cell A, Cell B, Cell D.



Result of example:

Best Server Potential Polluter Pilot Pollution Events Cell A Cell D +1

Note that in this version of TEMS Visualization Enterprise there is no “Pilot Pollution” timer with the aim of only counting repeated replacements. All Soft Handover Replacement events are counted.

6.3.3 View Description

6.3.3.1 Main Grid for All Cells Column Name Description Best Server Name of the polluted cell, or best server at the time the pilot

pollution event was detected.

Potential Polluter Count

Number of potential polluter cells.

Potential Polluter Name of the polluter cell.

Calls Served Number of calls served by this cell.

PP Events Number of pilot pollution events detected for the same polluted and polluter cells.

Calls Affected PP Number of calls affected by SOHO-based pilot pollution.

% Calls Affected PP

Percentage of the calls served by this cell affected by pilot pollution.

Avg PP Events Per Call

Average number of PP events per call.

Avg Polluter RSCP (dBm)

Average RSCP of the polluter cell, calculated for each time it was detected for the given polluter cell.

Avg Polluter Ec/No (dB)

Average Ec/No of the polluted cell, calculated for each time it was detected for the given polluter cell.

Distance (km) Distance between the best server (polluted cell) and the potential polluter cell.


WCDMA – RF Diagnostics Feature • 119

7 WCDMA Feature Description: RF Diagnostics


The RF Diagnostics feature automatically identifies RF issues that are affecting cell performance and then gives possible causes for those issues. The right actions can then be taken to fix poorly performing cells.

The feature is normally used to troubleshoot poor performance in one or more cells in an area of the network. Neighbor cells should be included in the recordings to get a full picture of reasons for possible performance degradation.

7.1 Prerequisites Simultaneous GPEH and W-MRR recordings performed correctly. See the TEMS Visualization Enterprise Server user’s manual for more details on how to:

• Set up simultaneous GPEH and MRR-W recordings.

• Select the GPEH messages that must be included in the recording for basic call analysis and this feature.

• Set the OSS-RC parameter GPEHDataLevel to All_Data.

Note that if the RRC_MEASUREMENT_REPORT event is included in the GPEH profile, then the periodic events are automatically captured in the GPEH recording. There is no need to load any separate data or results file from MRR-W.

Successful import of Cell Configuration Data. The calculations for the RF Diagnostics feature require some parameters from the cell configuration file. A valid cell configuration file from the OSS-RC must have been loaded into the configuration database.

Desired Analysis Threshold settings. A number of Analysis Threshold parameters are associated with the RF Diagnostics feature, as described in the following sections. For details on how to configure these settings, see the TEMS Visualization Enterprise Server user’s manual.

120

7.2 Technical Description RF Issues

Periodic measurements of the radio environment can be reported by UEs in all areas where a cell is serving, not just at handover events. These are activated using the MRR-W feature in the Ericsson OSS-RC, and are captured as RRC_MEASUREMENT_REPORT events in the GPEH recordings.

The RF Diagnostics feature analyzes these periodic measurements to automatically detect calls where a potential RF Issue occurred.

Possible Causes

Whenever an RF Issue is detected during a call, then a number of different Possible Causes are evaluated. Some of these Possible Causes are based on additional measurements of radio conditions, while other Possible Causes are based on events such as missing or failed handovers.

Calculation and presentation of results

When an RF Issue is detected, the call is marked as ”affected.” The RF Issue is counted as an affected call against the cell that was Best Server at that time.

The same RF Issue may occur repeatedly during a call on the same Best Server, but each RF Issue can only be counted once per call and per cell. However, if the Best Server changes and the same RF Issue occurs again, then the call may be counted against this new Best Server.

For each cell, the total counts and percentages of calls affected by each RF Issue are calculated and presented. The percentages of these affected calls where a Possible Cause was found are also calculated and presented. Note that Possible Causes are only evaluated at the same time as detection of a “parent” RF Issue.

Summing the percentages of affected calls where a Possible Cause was detected may not add up to 100%. This is because each occurrence of an RF Issue may have more than one Possible Cause – or the same RF Issue may occur several times in the same call with different Possible Causes.

Filter

Calls with the Establishment Causes listed below are filtered out (they are NOT included in any statistics). This is because issues affecting these network generated calls do not have the same impact on subscriber perceived quality.

• interRAT-CellReselection, • registration • detach



7.2.1 RF Issue Evaluation The table below gives an overview of how RF Issues are evaluated.

RSCP Ec/No UeTxPwr UL Interference

Out of Coverage Poor Poor Not required Not required

High DL Interference

Acceptable, Good

Poor Not required Not required

High UL Interference Not required Not required High High

UL/DL imbalance Good Not required High Low

Analysis Thresholds

RSCP Acceptable Threshold, RSCP Poor Threshold

Ec/No Poor Threshold

UeTxPwr High Threshold

UL Interference High RF

Threshold

RSCP, Ec/No. Measured and reported together by the UE in an RRC_MEASUREMENT_ REPORT. Values are taken from periodic measurements and from measurements for handovers.

UeTxPower. Measured by the UE and reported in an RRC_MEASUREMENT_REPORT. Values are only available and taken from periodic measurements.

UL Interference. Measured in NodeB. Values are taken from the periodic INTERNAL_ SYSTEM_UTILIZATION event. This is reported for each cell every 2 seconds.

The Measurement Valid Timer analysis threshold specifies how long a measurement is considered valid for use in evaluations of RF Issues and Possible Causes. This is needed because each of the measurements listed above occur in separate GPEH events.

RF Issue IE

122

7.2.2 Possible Cause: Overshooting Cell Description:

Shows when calls are being set up too far from the site.

Possible Cause for:

Out of Coverage, High DL Interference, UL/DL Imbalance

Evaluated:

When the parent RF Issue occurs during the start of the call then, as long as the call has the first cell as Best Server, the Overshooting Cell Possible Cause is evaluated.

Inputs:

• Call setup distance. From Propagation Delay contained in NBAP_RADIO_ LINK_SETUP. Value stored for each Call Setup.

• Overshooting Cell Distance. Calculated by multiplying the Distance to Nearest Neighbor Site by the Overshooting Cell Distance Multiplier analysis threshold. Calculated at analysis time. Value stored for each cell at analysis start.

Distance to Nearest Neighbor Site is calculated when the cell configuration file is imported and stored in the database together with other cell data.

Possible Cause IF:

Call setup distance ≥ Overshooting Cell Distance

7.2.3 Possible Cause: Missing IFHO/IRAT Description:

Detects when compressed mode was started but no IFHO or IRAT handover was attempted within a certain period of time. This shows when the UE needed to make an IFHO or IRAT handover but no suitable candidate cell was available – and the call then goes Out of Coverage.

Possible Cause for:

Out of Coverage

Evaluated:

Whenever an INTERNAL_CMODE_ACTIVATE event is received, signaling the start of compressed mode.



Inputs:

• To signal start of compressed mode: INTERNAL_CMODE_ACTIVATIE

• To signal measurement made on suitable candidate or end of compressed mode: INTERNAL_IFHO_EVALUATION OR INTERNAL_IRAT_HO_CC_ EVALUATION OR RRC_MEASUREMENT_REPORT for e3a or e2b OR INTERNAL_CMODE_DEACTIVATE.

• Missing IFHO/IRAT Handover Time analysis threshold

• Condition Valid Long Timer analysis threshold

Possible Cause IF:

Missing IFHO/IRAT Handover Time expires without compressed mode deactivation or an IFHO/IRAT evaluation and then Out of Coverage is detected within Condition Valid Long Timer.

7.2.4 Possible Cause: Pilot Pollution - Threshold Based Description:

The number of cells reported within a certain dB value of the Best Server at SOHO is evaluated. This shows when there is coverage from many different cells at around the same signal level.

Possible Cause for:


Evaluated:

When the parent RF Issue occurs, then all soft handover additions or replacements are evaluated during the Condition Valid Long Timer analysis threshold.

Inputs:

• RSCP or Ec/No from RRC_MEASUREMENT_REPORT. Value taken for each measured cell in SOHO addition or replacement.

• Pilot Pollution Threshold Based dB Delta analysis threshold. If the difference between the Best Server and the measured cell is less than this value in dB, then is considered an Overlapping Cell. (The Pilot Pollution Threshold Based type analysis threshold controls whether Ec/No or RSCP is used.)

• Number of Overlapping Cells. Total number of overlapping cells in the Measurement Report for the SOHO addition or replacement.

Possible Cause IF:

The Number of Overlapping Cells is ≥ the Pilot Pollution Threshold Based Number of Cells analysis threshold for one of the evaluated SOHO additions or replacements.

124

7.2.5 Possible Cause: SOHO Block Description:

Detects when a soft handover was required but could not be executed because of Admission Control congestion in the target cell – and then the call goes into High DL Interference. This is a delayed handover causing downlink interference problems.

Possible Cause for:


Evaluated:

Whenever an INTERNAL_SYSTEM_BLOCK message is received during the call.

Inputs:

• INTERNAL_SYSTEM_BLOCK message


Possible Cause IF:

Any INTERNAL_SYSTEM_BLOCK message with EVENT_PARAM_REQUESTED_ SETUP_CLASS=0 (for SOHO) occurs for the call and High DL Interference is detected within Condition Valid Long Timer.

7.2.6 Possible Cause: SOHO Failure Description:

Detects when a soft handover was required and executed but resulted in a failure – after which the call goes into High DL Interference.

Possible Cause for:


Evaluated:

Whenever an INTERNAL_SOFT_HANDOVER_EXECUTION message is received during the call.

Inputs:

• INTERNAL_SOFT_HANDOVER_EXECUTION message


Possible Cause IF:

Any INTERNAL_SOFT_HANDOVER message occurs during the call with EVENT_PARAM_ RESULT <> EVENT_VALUE_SUCCESS (indicating a SOHO failure) and High DL Interference is detected within Condition Valid Long Timer.



7.2.7 Possible Cause: Unmonitored SOHO Neighbor Description:

Detects when an Unmonitored Neighbor occurs (soft handover is proposed to a cell in the detected set that is already defined as a neighbor) – and this coincides with High DL Interference. It may have been possible for the UE to hand over to the Unmonitored Neighbor cell earlier – and avoid the High DL Interference – if it had been in the monitored set.

Possible Cause for:


Evaluated:

Whenever an INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR message is received during the call.

Inputs: • INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOUR message • Condition Valid Long Timer analysis threshold

7.2.8 Possible Cause: Missing SOHO Neighbor Description:

Detects when a Missing Neighbor is reported by the UE (for event 1a or event 1c, where the triggering cell is not included in Neighbor Set) – and this coincides with High DL Interference. It may have been possible for the UE to handover to the Missing Neighbor cell – and avoid the High DL Interference – if it had been in the neighbor list. Or else the Missing Neighbor cell is providing unintended coverage and should be down-tilted.

Possible Cause for:


Evaluated:

Whenever an INTERNAL_SOHO_DS_MISSING_NEIGHBOR message is received during the call.

Inputs: • INTERNAL_SOHO_DS_MISSING_NEIGHBOR message • Condition Valid Long Timer analysis threshold

Possible Cause IF:

INTERNAL_SOHO_DS_MISSING_NEIGHBOR message occurs at the same time as High DL Interference – within Condition Valid Long Timer.

126

Possible Cause IF:

INTERNAL_SOHO_DS_UNMONITORED_NEIGHBOR message occurs at the same time as High DL Interference – within Condition Valid Long Timer.

7.2.9 Possible Cause: UL Path Losses Description:

Indicates when the power used by the UE exceeds what was expected (given the DL path loss, noise rise, and RBS sensitivity) by a significant margin. This indicates losses on the UL Path – and a potential cause for UL/DL imbalance.

Possible Cause for:

UL/DL imbalance

Evaluated:

When all required measurements (RSCP, UeTXPower, UL Interference) are valid.

Inputs:

• RSCP and UeTxPower from periodic RRC_MEASUREMENT_REPORT for MRR-W

• UL Interference from periodic INTERNAL_SYSTEM_UTILIZATION message

• CPICH Power from the cell configuration file (the CPICH Power Fallback analysis threshold is used if the information is not available from the cell configuration file)

• RBS Sensitivity analysis threshold

• UL Path Loss UL/DL dB Delta analysis threshold

• Condition Valid Short Timer analysis threshold

Possible Cause IF:

UeTxPower – (DL Pathloss + Noise Rise + RBS Sensitivity) ≥ UL Path Loss UL/DL dB Delta occurs at the same time as UL/DL imbalance – within Condition Valid Short Timer, where:

• DL Pathloss = (CPICH_POWER – CPICH RSCP)

• Noise Rise = UL Interference + 106 dBm



7.3 View Descriptions

7.3.1 Out of Coverage Column Name Description Cell Cell name.

Calls Evaluated The total number of calls that were evaluated for Out of Coverage when this cell was Best Server. These are subscriber-generated calls where Ec/No and RSCP samples were available from measurements reported by the UE, either for handover or for periodic measurements activated using MRR-W.

% Out of Coverage Affected Calls

The percentage of calls evaluated that were affected by an Out of Coverage RF Issue

Out of Coverage Affected Calls

The number of calls evaluated that were affected by an Out of Coverage RF Issue

% Missing IFHO/IRAT Percentage of Out of Coverage Affected Calls where a Possible Cause of Missing IFHO/IRAT was detected

% Overshooting Cell Percentage of Out of Coverage Affected Calls where a Possible Cause of Overshooting Cell was detected

7.3.2 High DL Interference Column Name Description Cell Cell name.

Calls Evaluated The total number of calls that were evaluated for High DL Interference when this cell was Best Server. These are subscriber-generated calls where Ec/No and RSCP samples were available from measurements reported by the UE, either for handover or for periodic measurements activated using MRR-W.

% High DL Interference Affected Calls

The percentage of calls evaluated that were affected by a High DL Interference RF Issue

High DL Interference Affected Calls

The number calls evaluated that were affected by a High DL Interference RF Issue

% Pilot Pollution Threshold Based

Percentage of High DL Interference Affected Calls where a Possible Cause of Pilot Pollution – Threshold Based was detected

128

Column Name Description % Overshooting Cell Percentage of High DL Interference Affected Calls where a

Possible Cause of Overshooting Cell was detected at the call start

% Missing SOHO Neighbor

Percentage of High DL Interference Affected Calls where a Possible Cause of Missing SOHO Neighbor Failure was detected

% SOHO Block Percentage of High DL Interference Affected Calls where a Possible Cause of Admission Control Block delaying a Soft Handover was detected

% SOHO Failure Percentage of High DL Interference Affected Calls where a Possible Cause of Soft Handover Failure was detected

% Unmonitored SOHO Neighbor

Percentage of High DL Interference Affected Calls where a Possible Cause of Unmonitored SOHO Neighbor Failure was detected

7.3.3 High UL Interference Column Name Description Cell Cell Name.

Calls Evaluated The total number of calls that were evaluated for High UL Interference when this cell was Best Server. These are subscriber-generated calls where UL Interference samples were available from System Utilization measurements and UeTXPower samples were available from periodic measurements from the UE activated using MRR-W

% High UL Interference Affected Calls

The percentage of calls evaluated that were affected by a High UL Interference RF Issue

High UL Interference Affected Calls

The number calls evaluated that were affected by a High UL Interference RF Issue



7.3.4 UL/DL Imbalance Column Name Description Cell Cell name.

Calls Evaluated The total number of calls that were evaluated for UL/DL Imbalance when this cell was Best Server. These are subscriber-generated calls where UL Interference, UeTXPower (from periodic measurements from the UE activated using MRR-W ) and RSCP samples were available.

% UL/DL Imbalance Affected Calls

The percentage of calls evaluated that were affected by a UL/DL Imbalance RF Issue

UL/DL Imbalance Affected Calls

The number calls evaluated that were affected by a UL/DL Imbalance RF Issue

% UL Path Losses Percentage of UL/DL Imbalance Affected Calls where a Possible Cause of UL Path Loss was detected

% Overshooting Cell Percentage of UL/DL Imbalance Affected Calls where a Possible Cause of Overshooting Cell was detected at the call start


WCDMA –Cell Capacity Analysis Feature • 131

8 WCDMA Feature Description: Cell Capacity Analysis


The Cell Capacity Analysis feature makes it possible to easily identify cells that have resource issues. Resource usage statistics are presented for a selection of the most critical Uplink and Downlink resources. Drill-down into detailed charts for further investigation is then possible.

8.1 Prerequisites Correct setup of GPEH recordings. The GPEH message INTERNAL_SYSTEM_ UTILIZATION must have been included in the GPEH recording. For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual. The GPEH recording should be performed during busy hours.

Successful import of Cell Configuration Data. The calculations for the Cell Capacity Analysis feature require parameters from the cell configuration file such as the maximum allowed number of HSDPA users. For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual.

8.2 Technical Description All resource usage statistics are calculated from the GPEH message INTERNAL_SYSTEM_UTILIZATION. This is a periodic message generated every 2 seconds for all cells in the recording.

Resource usage grid. Resource usage statistics (either a percentile or maximum value) are calculated for each 15-minute ROP period. The values shown in the grid are for the ROP with the highest calculated value during the entire selected scope. Different resource types may show values from different ROPs.

ROP chart. Shows all the 95th percentile or maximum resource usage values as calculated for each ROP in the selected scope.

Time chart. One ROP must be selected from the ROP chart. For this ROP the time chart shows every measurement for the selected resource types – right down to 2-second resolution. All the resource types available in the INTERNAL_SYSTEM_ UTILIZATION message can be displayed on the chart.

132

8.3 View Descriptions

8.3.1 Downlink Resource Usage Column Name Description Cell Cell name

ROPs Evaluated Number of ROPs for which the INTERNAL_SYSTEM_UTILIZATION message was available and the resource usage statistics could be calculated.

Max DL Power (dBm) Maximum downlink power. Note that this is taken from the INTERNAL_SYSTEM_UTILIZATION event and not the cell configuration file. This is because the actual maximum allowed power might be lower than the parameter setting due to physical hardware limitations. IE: MAX_DL_POWER.

Peak Non-HS DL Power Consumption (%)

Value shows the 95th percentile of Non-HS DL Power usage during a 15-minute ROP. The ROP selected is the one with the highest value from all ROPs in the selected scope. For HS activated cells: DL_NON_HS_TX_POWER. For non-HS cells: DL_TX_POWER.

DL Channel Element Capacity

Available downlink Channel Elements taken from the INTERNAL_SYSTEM_UTILIZATION event. IE: CAPACITY_CREDITS_DL.

Peak DL Channel Element Consumption (%)

Value shows the 95th percentile of DL Channel Element usage during a 15-minute ROP. The ROP selected is the one with the highest value from all ROPs in the selected scope. Calculation: (CONSUMED_CREDITS_DL / CAPACITY_CREDITS_DL) *100

Max HSPDA Users Maximum allowed HS Users in the cell. Cell configuration file parameter: HsdpaUsersAdm

Max HSDPA Users (%) Value shows the highest percentage of HS users during a 15-minute ROP. The ROP selected is the one with the highest value from all ROPs in the selected scope. Calculation: (NUMBER_OF_USERS_ASSIGNED_TO_PHYS_HS_CHAN / HsdpaUsersAdm) *100


WCDMA –Cell Capacity Analysis Feature • 133

8.3.2 Uplink Resource Usage Column Name Description Cell Cell name

ROPs Evaluated Number of ROPs for which the INTERNAL_SYSTEM_UTILIZATION message was available and the resource usage statistics could be calculated.

UL Interference Peak (dBm) Value shows the 95th percentile of UL Interference usage during a 15-minute ROP. The ROP selected is the one with the highest value from all ROPs in the selected scope. Also known as the Received Total Wideband Power (RTWP). IE: UL_INTERFERENCE

UL Channel Element Capacity Available uplink Channel Elements taken from the INTERNAL_SYSTEM_UTILIZATION event. IE: CAPACITY_CREDITS_UL

UL Channel Element Peak (%) Value shows the 95th percentile of UL Channel Element usage during a 15-minute ROP. The ROP selected is the one with the highest value from all ROPs in the select scope. Calculation: (CONSUMED_CREDITS_UL / CAPACITY_CREDITS_UL) *100

Max EUL Served Users Maximum allowed EUL Users in the cell. Cell configuration file parameter: eulServingCellUsersAdm

EUL Served Users Peak (%) Value shows the highest percentage of EUL users during a 15-minute ROP. The ROP selected is the one with the highest value from all ROPs in the select scope. Calculation: (NUMBER_OF_EDCH_USERS_IN_SERVING_CELL / eulServingCellUsersAdm) * 100


WCDMA – KPI Views Feature • 135

9 WCDMA Feature Description: KPI Views The KPI views present summaries of Key Performance Indicator statistics on different dimensions. TEMS Visualization Enterprise offers the following KPI views:

• Cell KPI and Cluster KPI – Key Performance Indicators for each cell (or for user-defined groups of cells)

• Subscriber KPI (and Subscriber Group KPI) – Key Performance Indicators for each IMSI (or for user-defined groups of IMSIs)

• Phone Model KPI - Key Performance Indicators for each Phone Model OR IMEI-TAC

The Worst Cell, Worst Subscriber and Worst Phone Model sections allow the user to quickly identify the largest contributors to poor network performance and then begin to drill-down to identify the reasons. Thresholds can be set against all the “rate” type KPIs. For example, thresholds can be set to only show “Worst cells” in terms of Dropped Call Rate (%) where the number of dropped calls is 10 or more.

The individual tabs for accessibility, retainability, mobility, and data integrity allow the KPI statistics for all cells, subscribers, or phone models to be viewed. When a specific statistic is selected, the associated chart shows the variation of the selected KPIs over time.

9.1 Prerequisites Correct setup of GPEH recordings – For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user manual. The required GPEH messages or LTE CellTrace messages are described in the Server user manual under the “Profile Standard” section. This profile includes all the messages required for the KPIs and to keep track of the IMSI (subscriber KPIs) or IMEI-TAC (phone model KPIs).

9.2 Technical Description During basic call analysis, TEMS Visualization Events such as dropped calls and handover failures are generated based on defined sequences of GPEH messages.

The KPI statistics are the aggregation of these TEMS Visualization Events over each 15-minute recording period (ROP).

The KPIs are subdivided by Service - which is a grouping of RAB types. This allows the user to quickly identify if there was an issue, for example, with single CS speech RABs or CS+PS Multi-RABs.

Note that the sending of the IMEI-TAC in the RANAP messages is dependent on settings in the core network. For example it can often be the case that the IMEI-TAC is only available for Circuit-Switched connections.

136

9.3 View Descriptions The tables in the main grid on the KPI views and in the time charts include the fields listed below for Accessibility, Retainability, Mobility, and Data Integrity KPIs.

9.3.1 Accessibility Column Name Description Service Source/

Target For the Cell KPI view, the first field is: Cell Cell name, counted against Best Server

only

For the Subscriber KPI view, the first fields are: IMSI Subscriber’s International Mobile

Subscriber Identity

IMEI TAC International Mobile Equipment Identity – Type Allocation Code of the phone

Phone Manufacturer

Phone Manufacturer

Phone Model Phone Model

For the Phone Model KPI view, the first fields are: IMEI TAC International Mobile Equipment Identity

– Type Allocation Code of the phone

Phone Manufacturer

Phone Manufacturer


The remaining fields are as follows:

Call Attempts Number of attempts to setup a new RRC connection (also called a signaling RAB or SRB) for a call.

Target - always SRB

Blocked Calls A call can be blocked by admission control during the attempt to establish a signaling connection or during the attempt to establish an initial traffic RAB. Failures to establish the initial Traffic RAB are also included.

Source - always on SRB when the Call is Blocked

Blocked Call Rate (%)

Percentage of Call Attempts where a Blocked Call was detected.

RRC Connection Blocks

RRC Connection Block event is triggered when an RRC Connection Block is blocked due to Admission Control.

Target - always SRB



Column Name Description Service Source/ Target

RRC Connection Block Rate (%)

Percentage of Call Attempts where an RRC Connection Block was detected.

Initial RAB Establishment Attempts

Number of attempts to establish an initial traffic RAB.

Target

Initial RAB Establishment Blocks

Number of attempts to establish an initial traffic RAB which are blocked by Admission Control.

Target

% RAB Establishment Blocks

Percentage of RAB Establishment Attempts where an RAB Establishment Block was detected.

9.3.2 Retainability Column Name Description For the Cell KPI view, the first field is as follows: Cell Cell name, counted against Best Server only

For the Subscriber KPI view, the first fields are as follows: IMSI Subscriber’s International Mobile Subscriber Identity


Phone Manufacturer Phone Manufacturer. Phone Model file must be loaded


For the Phone Model KPI view, the first fields are: IMEI TAC International Mobile Equipment Identity

– Type Allocation Code of the phone

Phone Manufacturer

Phone Manufacturer


The remaining fields are as follows: Service End Service

Normal End Calls Number of Normal call ends

Dropped Calls Number of detected dropped calls

Dropped Call Rate (%) Dropped Call Rate (100*(Dropped Calls / (Dropped Calls + Normal End Calls)). Unknown Call Ends are excluded from the calculation.

138

Column Name Description Service Minutes Total call time on this Service.

Aggregated Minutes Per Drop

Service Minutes / Dropped Calls

9.3.3 Mobility Column Name Description For the Cell KPI view, the first fields are as follows: Cell Cell name, counted against Best Server only



Phone Manufacturer Phone Manufacturer




Phone Manufacturer Phone Manufacturer. Phone Model file must be loaded


The remaining fields are as follows: Service Service at time of Mobility event

SOHO Successes Number of successful Soft Handovers

SOHO Failures Number of failed Soft Handovers

SOHO Failure Rate (%) Percentage of Soft Handover failures (100 * SOHO Failures / SOHO Success + Failures)

Missing Neighbor Events Number of Missing Neighbor Events

Dropped Calls Due to Missing Neighbor

Number of Dropped Calls due to Missing Neighbors

IFHO Attempts Number of Inter-Frequency Handover Attempts

IFHO Successes Number of Inter-Frequency Handover Successes

IFHO Failures Number of Inter-Frequency Handover Failures

IFHO Failure Rate (%) Percentage of Inter-Frequency Handover Failures (100 * (IFHO Failures / IFHO Failures + IFHO Successes))

IRAT Attempts Number of UMTS-to-GSM IRAT Handover Attempts



Column Name Description IRAT Successes Number of IRAT Handover Successes - Normal Call End

with SubClass “Handover to GSM”

IRAT Failures Number of IRAT Handover Failures

IRAT Failure Rate (%) Percentage of IRAT Failures (100*(IRAT Failures/IRAT Failures + IRAT Successes))

IRAT CC Attempts Number of UMTS-to-GSM IRAT Cell Change Order Attempts

IRAT CC Successes Number of IRAT Cell Change Order Successes - Normal Call End with SubClass “CC to GSM”

IRAT CC Failures Number of IRAT Cell Change Order Failures

IRAT CC Failure Rate (%) Percentage of IRAT Cell Change Order Failures (100*(IRAT CC Failures/IRAT CC Failures + IRAT CC Successes))

HS CC Successes Number of High Speed Cell Change Successes

HS CC Failures Number of High Speed Cell Change Failures

HS CC Failure Rate (%) Percentage of High Speed Cell Change Failures (100 (HS CC Failures/HS CC Failures + HS CC Successes))

Compressed Mode Starts Number of Compressed Mode Start Occurrences.

9.3.4 Data Integrity Column Name Description For the Cell KPI view, the first fields are as follows: Cell Cell name, events counted against Best Server only.

For the Downlink HS throughput measurements represents HSDSC Cell 1.



Phone Manufacturer Phone Manufacturer




140

Column Name Description Phone Manufacturer Phone Manufacturer. Phone Model file must be

loaded


The remaining fields are as follows: Service Service at time of Data Integrity event.

Downlink throughput samples are only counted against RAB types with HS on DL, Uplink throughput samples are only counted on RAB types with EUL on uplink.

Avg HS Throughput (kbps) The average DL Radio Link Control throughput in kbps including retransmissions

HS Throughput Samples Number of DL high speed throughput data points.

Avg User HS Throughput (kbps)

Average user DL Radio Link Control throughput in kbps

User HS Throughput Samples Number of User High Speed Throughput data points

Avg HS Throughput Delta (kbps)

The difference between the User Throughput and the average DL HS Throughput

Avg HS Throughput Delta Samples

Number of HS Throughput Delta data points

Avg EUL Throughput (kpbs) Number of EUL Throughput data points

EUL Throughput Samples Number of EUL Throughput data points

Avg User EUL Throughput (kbps)

Average user EUL Radio Link Control Throughput in kbps

User EUL Throughput Samples Number of EUL User Throughput data points

Avg EUL Throughput Delta (kbps)

The difference between the User Throughput and the average EUL Throughput

Avg EUL Throughput Delta Samples

Number of EUL Throughput Delta data points

For the Subscriber KPI and Phone Model KPIs views, the final fields are as follows: Channel Switch Successes Number of Channel Switch Success events based on

INTERNAL_CHANNEL_SWITCHING GPEH Event

Channel Switch Failures Number of channel Switch Failure events based on INTERNAL_CHANNEL_SWITCHING GPEH Event

% Channel Switch Successes Percentage of Channel Switch Successes, calculated as (Channel Switch Success/(Channel Switch Successes + Channel Switch Failures))*100


LTE – KPI Views Feature • 141

10 LTE Feature Description: KPI Views The KPI views present summaries of Key Performance Indicator statistics on different dimensions. TEMS Visualization Enterprise offers the following KPI views:

• Cell KPI and Cluster KPI – Key Performance Indicators for each cell (or for user-defined groups of cells)

The Worst Cell section allows the user to quickly identify the largest contributors to poor network performance and then begin to drill-down to identify the reasons. Thresholds can be set against all the “rate” type KPIs. For example, thresholds can be set to only show “Worst cells” in terms of Abnormal UE Release Rate (%) where the number of Abnormal UE Releases is 10 or more.

The individual tabs for accessibility, retainability, mobility, and data integrity allow the KPI statistics for all cells to be viewed. When a specific statistic is selected, the associated chart shows the variation of the selected KPIs over time.

10.1 Prerequisites Correct setup of LTE CellTrace recordings – For more details, see the Data Collection Setup section of the TEMS Visualization Enterprise Server user’s manual. The required LTE CellTrace messages are described in the Server user’s manual under the “Profile Standard” section.

10.2 Technical Description During basic call analysis, TEMS Visualization Events such as dropped calls and handover failures are generated based on defined sequences of LTE CellTrace messages.

The KPI statistics are the aggregation of these TEMS Visualization Events over each 15-minute recording period (ROP).

The KPIs are subdivided by QCI. This allows the user to quickly identify if there was an issue, for example, with a particular QCI.

142

10.3 View Descriptions The tables in the main grid on the KPI views and in the time charts include the fields listed below for Accessibility, Retainability, Mobility, and Data Integrity KPIs.

10.3.1 Accessibility Column Name Description Cell Cell name, counted against server

QCI QoS Class Identifier

Connection Attempts Number of attempts to set up a new RRC connection

Blocked Connection Number of blocked RRC Connection establishments due to administration control, failure in RRC procedure, or license check failure

% of Blocked Connection

Percentage of connection attempts where a blocked connection was detected

Default Bearer Setup Attempt

Number of Default Bearer setup attempts

Default Bearer Setup Failure

Number of default bearer setup attempts that were blocked due to failure in radio procedure, lack of resources, license check failure etc

% of Default Bearer Setup Failure

Percentage of Default Bearer Setup attempts where a setup failure was detected

Dedicated Bearer Setup Attempt

Number of Dedicated Bearer setup attempts

% of Dedicated Bearer Setup Failure

Percentage of Dedicated Bearer Setup attempts where a setup failure was detected

10.3.2 Retainability Column Name Description Cell Cell name, counted against server


Normal UE Release Number of normal UE context releases

Abnormal UE Release Number of abnormal UE context releases

% of Abnormal UE Release

Percentage of UE context releases that were abnormal [Abnormal UE Release/(Abnormal UE Release + Normal UE Release)]*100

Normal Bearer Release Number of normal bearer releases


LTE – KPI Views Feature • 143

Column Name Description Abnormal Bearer Release Number of abnormal bearer releases

% of Abnormal Bearer Release

Percentage of bearer releases that were abnormal [Abnormal Bearer Release/(Abnormal Bearer Release + Normal Bearer Release)]*100

10.3.3 Mobility Column Name Description

Cell Cell name, counted against server


X2 Handover Success Number of successful X2 Handovers

X2 Handover Failure Number of failed X2 Handovers

% of X2 Handover Failure Percentage of X2 Handover failures [X2 Handover Failure/(X2 Handover Execution Failure + X2 Handover Success)]*100

S1 Handover Success Number of successful S1 Handovers

S1 Handover Failure Number of failed S1 Handovers

% of S1 Handover Failure Percentage of S1 Handover failures [S1 Handover Execution Failure/S1 Handover Execution Failure + S1 Handover Success)]*100

10.3.4 Data Integrity Column Name Description Cell Cell name, counted against server

Average Active Users in DL Average Active Users in DL

Average Active Users in DL Average Active Users in DL

Average DL Throughput (Mbps) Average DL Throughput (Mbps)

Average UL Throughput (Mbps) Average UL Throughput (Mbps)

Average DL Packet Loss Rate (%) Average DL Packet Loss Rate (%)

Average UL Packet Loss Rate (%) Average UL Packet Loss Rate (%)


Appendix A. MapInfo Layer Control • 145

Appendix A. MapInfo MapXtreme® Layer Control

Introduction TEMS Visualization Enterprise uses MapInfo’s MapXtreme® map engine. The map can be customized in numerous ways via the Layer Control feature, including the following:

• Setting the Map Window

• Inserting Layers

• Inserting Layers to be Labeled

• Editing Layers and Labels

• Adding a Theme to Layers or Labels

• Adding Style Overrides to Layers

• Opening Tables

Setting the Map Window

1. On the Map toolbar, click the Layer Control tool.

2. In the Layer Control dialog box, select the map.

146

View Tab On the View tab, do one or more of the following, and then click Apply.

Action Description

Specify the width and scale of the map

Type a value in the Zoom (window width) box or the Map Scale box. A value in one of the boxes determines the value in the other box.

Set the X and Y coordinates of the map’s center point

In the Center of window box, type X and Y coordinates

Set the rotation angle of the map In the Rotation Angle list, click a degree value.



Editing Tab On the Editing tab, do one or more of the following, and then click Apply.

Action Description

Select fill pattern, foreground color, and background color of the map.

Click the Area Style button and select options on the Fill tab.

Select style, color, and width of the map border.

Click the Area Style button and select options on the Border tab.

Select style, color, translucency, and width of line objects on the map.

Click the Line Style button and select options.

Select font, symbol type, color, and translucency of point objects on the map.

Click the Symbol Style button and select options on the Symbol tab.

Select background type and color of point objects on the map.

Click the Symbol Style button and select options on the Background tab.

Select effect attributes (bold, italic, drop shadow) and rotation angle of point objects on the map.

Click the Symbol Style button and select options on the Effects tab.

Select font type, size, and color; background color and type; and text effects (bold, italic) for label text.

Click the Text Style button and select options.

Delete duplicate nodes. Select Delete duplicate nodes checkbox.

Move duplicate nodes. Select Move duplicate nodes checkbox.

Allow map to be moved or resized, nodes to be edited, or nodes to be added.

Click an option in the Editing mode list.

Allow map labels to be edited. Select the Labels are editable checkbox.



Tools Tab On the Tools tab, do one or more of the following, and then click Apply.

Action Description

Show the value of the map’s label Expressions.

Select the Show InfoTips checkbox.

Allow the Selection tool to automatically search for nodes that are nearby.

Select the Snap to Node checkbox. In the Snap tolerance box, type the number of pixels the Selection tool will use when searching for a “snap-able” node. When using the Selection tool with Snap to Node turned on, a crosshair will appear to indicate the position of the nearest node.

Allow cells to be selected immediately, when the mouse button is pressed.

Select the Dynamic Selection Tools checkbox. When this checkbox is clear, the cell will be selected when the mouse button is released.

150

Extents Tab The Extents tab shows the coordinates of the x-axis and y-axis of the map. To show the full extent of the map, click the View Entire Map button.

Coordinate System Tab On the Coordinate System tab, click the Coordinate System button and select a coordinate system for the map.



Inserting Layers 1. On the Map toolbar, click the Layer Control Tool.

2. In the Layer Control dialog box, select a layer, click the Add button and then click Insert Layers or Insert Layers into Group.

3. In the Select Tables to Add dialog box, select a table.

Options Tab On the Options tab of the Layer Control dialog box, perform one or more of the following actions, and then click Apply.

Action Description

Allow the layer to be selected. Select the Selectable checkbox.

Allow the layer to be edited. Select the Editable checkbox.

Allow features to be added by means of the drawing tools.

Select the Drawing tools can add features checkbox.

Display the layer’s expression when the mouse pointer pauses on the layer.

Select the Show InfoTips checkbox.

Allow the Selection tool to automatically search for nodes that are nearby.

Select the Snap to Nodes checkbox. When you are using the Selection tool with Snap to Nodes turned on, a crosshair will appear to indicate the position of the nearest node.

Customize the layer by creating an expression based on column or column information in the table.

In the InfoTip Expression box, type the expression.

152

Extents Tab The Extents tab shows the coordinates of the X-axis and Y-axis of the layer. Click a button to view the entire layer or the default area.



Information Tab The Information tab shows the name, path, type, and coordinate system of the table. No details can be changed.

154

Inserting Layers to be Labeled 1. On the Map toolbar, click the Layer Control Tool.

2. In the Layer Control dialog box, select a layer, click the Add button. A dialog window will open with a list of tables that can be added to the label layer.

3. Select the desired table and click OK.

Visibility Tab On the Visibility tab of the Layer Control dialog box, do one or more of the following, and then click Apply.

Action Description

Display the label on the map. Select the Visible checkbox.

Set the range for displaying the label.

• Select the Display Within Range checkbox.

• Click Zoom range or Scale range.

• Type minimum and maximum values.

Remove any changes made to labels.

Click Clear Label Modifications.



AutoLabel Tab On the AutoLabel tab, do one or more of the following, and then click Apply.

Action Description

Create labels based on the content of the table.

Select the Create Labels Automatically checkbox.

Set the range for displaying the AutoLabel


• Click Zoom range or Scale range.

• Type minimum and maximum values.

156

Style Tab On the Style tab, do one or more of the following, and then click Apply.

Action Description

Set the style, color, translucency, and width of the label line.


Select a line type, or no line type, that connects the label to the anchor point.

Under Label Lines, click one of the following:

• None – no label lines

• Simple – a simple line connects the label to the anchor point

• Arrow – an arrow

Select the font type, size, and color; background color and type; text effects (such as bold or italics) for the label text.




Text Tab On the Text tab, you can create a custom label that produces label text from a column or derived information from a table.

1. Click Set.

2. In the Expression dialog box, select a column, click Add, and then select another column. You can continue adding columns.

3. Click Verify.

4. Click Apply.

158

Position Tab On the Position tab, do one or more of the following, and then click Apply.

Action Description

Specify the position of the label relative to the anchor point.

Under Orientation, click a button.

Designate the distance a label should be placed from the anchor point.

Under Label Offset, type a value in the Offset box.

Rotate labels to stay with a segment, curve the labels along a segment, or keep the label at a specific angle.

Under Rotation, click an option. For rotating text at a specific angle, type the number of degrees.



Rules Tab On the Rules tab, do one or more of the following, and then click Apply.

Action Description

Allow label text to be displayed on a map more than once.

Select the Allow Duplicate Text checkbox.

Allow labels to be drawn on top of one another.

Select the Allow Overlapping Text checkbox.

Label poly-lines and objects whose centroids are not visible on the map.

Select the Label Partial Object checkbox.

Set the maximum number of labels to display on the map.

Type a value in the Maximum Labels box.

Specify an expression for the source (table) of a label layer that will receive the highest priority when labels are being added to a map. Labels from sources that do not match the expression will be added only if there is room on the map.

• Under Per-Table Priority Expression, click Set.

• In the Expression dialog box, select a column, click Add, and then select another column. You can continue adding columns.

• Click Verify, and then click Apply.

Specify an expression for labels that will receive the highest priority when labels are being added to a map. Labels that do not match the expression will be added only if there is room on the map.

• Under Per-Label Priority Expression, click Set.

• In the Expression dialog box, select a column, click Add, and then select another column. You can continue adding columns.

• Click Verify, and then click Apply.

160

Editing Layers and Labels The following table details the information about reordering, removing, and editing layers and labels.

Action Description

Change the order of layers or labels. Right-click the item and click Move Up or Move Down.

Remove a layer or label. Right-click the item and click Remove.

Modify a layer or label. Right-click the item, click Modify and make the changes.

Adding a Theme to Layers or Labels 1. On the Map toolbar, click the Layer Control Tool.

2. In the Layer Control dialog box, select a label, click the Add button, and then click Add Label Theme or Add Theme.

3. Follow the instructions on each page of the wizard.



Adding Style Overrides to Layers A style override makes the style of layer different from the style of its parent.

1. On the Map toolbar, click the Layer Control Tool.

2. In the Layer Control dialog box, right-click a layer, and then click Add Style Override.

On the Visibility tab, do the following, and then click Apply.

Action Description

Display the layer with the style override.

Select the Visible checkbox.

Set the range for displaying the style override.


• Click Zoom range or Scale range. • Type minimum and maximum values.

Select the fill pattern, foreground color, and background color of the style override.

Click the Area Style button and select options on the Fill tab.

Select the style, color, and width of the border for the style override.

Click the Area Style button and select options on the Border tab.

Select the style, color, and width of line objects in the style override.


Select the font, symbol type, and color of point objects in the style override.

Click the Symbol Style button and select options on the Symbol tab.

Select the background type and color of point objects in the style override.

Click the Symbol Style button and select options on the Background tab.

Select effect attributes (bold, italic, drop shadow) and rotation angle of point objects in the style override.

Click the Symbol Style button and select options on the Effects tab.

Select the font type, size, and color; background color and type; and text effects (such as bold or italics) in the style override label text.


Set the drawing mode for the style override.

Under Drawing mode, click Normal or Superimpose.

162

To copy a style override, right-click a style override and select Duplicate Style Override.

Opening Tables 1. On the Map toolbar, click the Layer Control Tool.

2. In the Layer Control dialog box, click the Add button, and then click Open Tables.

3. On the Open dialog box, select a table (.tab), geoset (.gst), or workspace (.mws).


Glossary • 163

Glossary of Terms 3GPP Third Generation Partnership Program

BCG Broadband Content Guide

BLER Block Error Rate

CC Control Channel

CM Configuration Management

CPICH Common Pilot Channel

DL Downlink

eARFCN E-UTRA Absolute Radio Frequency Channel Number

Ec/No Pilot strength. Ratio of received pilot energy, Ec, to total received energy or the total power spectral density, Io.

eNB Evolved Node B

ERBS Evolved Radio Base Station

EUL Enhanced Uplink

FTP File Transfer Protocol

GPEH General Performance Event Handling

GST File extension denoting a Geoset file

HO Handover

HS High Speed

HSDPA High Speed Uplink Packet Access

IE Information Element

IFHO Inter-Frequency Handover

IMEI-TAC International Mobile Equipment Identity / Type Allocation Control

IMSI International Mobile Subscriber Identity

IRAT Inter-Radio Access Technology

KPI Key Performance Indicator

LTE Long Term Evolution (3GPP 4G technology)

MME Mobile Management Entity

MO Managed Object

MP Main Processor

MRR-W Measurement Result Recording – WCDMA

MWS File extension denoting a MapInfo Workspace file

164

NAS Network Access Switch

NBAP Node B Application Part

OSS Operations Support System

OSS-RC Operations Support System Radio and Core

OTDOA Observed Time Difference of Arrival

PCI Physical Cell Identifier

PEM Privacy Enhanced Mail

PFX Personal Information Exchange

PLMN Public Land Mobile Network

PRACH Physical Random Access Channel

QCI Quality of Service (QoS) Class Identifier

RAB Radio Access Bearer

RAN Radio Access Network

RANAP Radio Access Network Application Protocol (3GPP)

RBS Radio Base Station

RNC Radio Network Controller

RNS Radio Network Subsystem

RNSAP RNS Application Part

ROP Result Output Period

RRC Radio Resource Control

RSCP Received Signal Code Power

RTWP Received Total Wideband Power

Rx Receive

S1 The interface used to interconnect eNBs and MMEs

SC Scrambling Code

SFTP FTP using SSH2

SIR Signal-to-Interference Ratio

SMTP Simple Mail Transfer Protocol

SOHO Soft Handover

SSL Secure Sockets Layer

TLS Transport Layer Security

Tx Transmit

UAC User Account Control


Glossary • 165

UARFCN UTRAN Absolute Radio Frequency Channel

UE User Equipment

UI User Interface

UL Uplink

UMTS Universal Mobile Telecommunications System

UNC Universal Naming Convention

UNM Unmonitored Neighbor

UTRAN UMTS Radio Access Network

WCDMA Wide-band Code Division Multiple Access

X2 The interface used to interconnect eNodeBs


Index • 167

Index A

About 14 Adding a Theme to Layers or Labels

160 Adding Style Overrides to Layers 161 Application Button & Quick Access

Toolbar 8 Assign Blank Values 12 Auto-Hide Mode 17 AutoLabel Tab 155 Automated Data Processing 4 Automated Data Retrieval 4 Automated Network Diagnosis 4 B

Bin Plot Themes 33 Bin Size 33 Bridging the Optimization Gap 2 Bulk CM Cells Count 12 C

Calculation of Overshooting Cell Distance 108

Calculation of Statistics 110 Call Analysis 91 Call Search 68 Candidate Neighbors 104, 105 Candidate Neighbors – Inter-

Frequency 81 Capacity Chart 96 Cell Capacity Analysis View 54 Cell Configuration Files 6 Cell KPI Themes 30 Cell KPI View 49 Cell Settings 38 Central Data Storage 4 Chart for Selected Cell 111 Chart for Worst Cells 114 Chart Views 93 Chart Zoom 18 Clear Themes 40 Close Button 17 Cluster KPI View 53

Column Summaries 20 Connect to Server 23 Coordinate System Tab 150 Copy Cell Value 21 Coverage Area Optimization 74 Coverage Themes 32 Creation of Pilot Pollution - SOHO

Based Events 116 Creation of Pilot Pollution – SOHO

Based Statistics 116 Creation of Pilot Pollution - Threshold

Based Events 112 Creation of Pilot Pollution Threshold

Based Statistics 113 D

Data Scope 28 Data View Management 15 Data Views 25 Details Grid for Selected Bin 115 Details Grid for Selected Cell 111 Display Control 15 Distance 36 Docked State 16 Downlink Resource Usage 132 Draw Polygon 35 Dropped Calls Analyzer 66 E

Editing Layers and Labels 160 Editing Tab 147 Exception Analysis 69 Existing Neighbor Usage 101, 104 Existing Neighbor Usage – Inter-

Frequency 81 Existing Neighbor Usage – Intra-

Frequency 80 Export function 8 Export Table 21 Extents Tab 150, 152 F

Filter Tables 19 Floating State 16

168

G

General 103 Geo-Locate Dropped Calls 46 Geo-Locate Pilot Pollution - Threshold

Based 45 Geo-location of Pilot Pollution

Threshold Based Events 113 GPEH / LTE Cell Trace Messages

Summary 70 Grids 19 H

HASP USB License Key 23 Help 14 Help Buttons 13 High DL Interference 127 High UL Interference 128 Histogram View 72 Home Tab 9 I

Import Clusters 37 Information Tab 153 Inserting Layers 151 Inserting Layers to be Labeled 154 Installation, Help and Support 6 Inter-frequency Neighbor

Optimization 103 K

Key Concepts 4 L

Layer Control 36 Legends & Layers 33 License Information 13 List of Views 25 Load Map File 34 Load New UI Style 11 Load Workspace 10 Locking Windows 17 LTE Cell Trace 5 LTE Feature Description: KPI Views

141

M

Main Grid for All Cells 111, 117 Manage Clusters 36 Map Layers 34 Map Right-Click Options 41 Map Themes 30 Map Toolbar 34 Map View 29 Matching Cells Count 12 Measurement Chart 97 Minimizing Windows 17 Missing Neighbors 102 Missing Neighbors – Intra-Frequency

80 N

NAS Messages Summary 71 Navigating the TEMS Visualization

Enterprise Client UI 7 Neighbor Change Request 82 Neighbor Optimization 78 No Antenna Beamwidth Cell Count 12 No Antenna Orientation Cells Count

12 No Lat/Lon Cell Count 12 O

Opening Tables 162 Optimization Decision Support 4 Options Tab 151 OSS Overview 5 Out of Coverage 127 Overshooting Cells 107 Overshooting Cells Part 74 Overview Statistics View 48 P

Page Setup 8 Pan 36 Phone Model KPI View 63 Pilot Pollution - SOHO Based 116 Pilot Pollution – SOHO Based 77 Pilot Pollution - Threshold Based 112 Pilot Pollution Coverage – Threshold

Based 76 Pin All 15


Index • 169

Pinned Mode 17 Position Tab 158 Possible Cause: Missing IFHO/IRAT

122 Possible Cause: Missing SOHO

Neighbor 125 Possible Cause: Overshooting Cell 122 Possible Cause: Pilot Pollution -

Threshold Based 123 Possible Cause: SOHO Block 124 Possible Cause: SOHO Failure 124 Possible Cause: UL Path Losses 126 Possible Cause: Unmonitored SOHO

Neighbor 125 Print Preview 8 Q

Quick Access toolbar 8 R

Reference Cells Count 12 Refresh Button 17 RF Diagnostics (MRR-W) View 55 RF Distribution Chart 94 RF Issue Evaluation 121 RF Scatter Chart 95 Rules Tab 159 S

Save Workspace As 10 SC Collision Report 39 Search 40 Select 34 Setting the Map Window 145 Show All 15 Show All Cells With Same PCI 44 Show All Cells With Same SC 44 Show All Cells With Same UARFCN

and SC 44 Show All Defined Neighbors 41 Show Candidate Neighbors 43 Show Capacity Chart 47 Show Inter-Freq Defined Neighbors

41 Show Inter-Freq Existing Neighbors

43

Show Intra-Freq Existing Neighbors 41

Show Missing Neighbors 42 Show Overshooting Cell Coverage 44 Show RF Distribution Chart 47 Show RF Scatter Chart 47 Sigma Symbol 20 Starting the System 23 Status Bar 14 Style Tab 156 Subscriber Group KPI View 61 Subscriber KPI View 57 Summaries 20 System Overview 1 T

Table Export 21 Table Filters 19 Tables 19 TEMS Visualization Event Summary 69 Text Tab 157 Theme Settings 38 Thresholds button 33 Tools Tab 149 tv80.isl 11 U

UL/DL Imbalance 129 Unpin All 15 Uplink Resource Usage 133 User Defined Query 86 User Defined Query Output view 90 User Interface 7 V

View Buttons 17 View Data Scope Information 17 View Docking 16 View Manager tasks 15 View Tab 146 Visibility Tab 154 W

WCDMA Feature Description: Cell Capacity Analysis 131

170

WCDMA Feature Description: Coverage Area Optimization 107

WCDMA Feature Description: KPI Views 135

WCDMA Feature Description: Neighbor Optimization 99

WCDMA Feature Description: RF Diagnostics 119

WCDMA GPEH 5 What's New in This Release 3 Window Manager 15 Window Tab 11 Workflow 21 Working with Tables 19 Workspace Tab 9 Z

Zoom In 35 Zoom Out 36 Zooming on Charts 18

tems visualization 8 enterprise help client

Documents