Accela Consistency Analysis RAN - User Manual v.2.1

Accela Consistency Analysis

Consistency Check – Parameter Analysis – Optimisation

Playground [RAN ]

User Manual

Document type

Technical

Prepared for

Accela Consistency Check Module Users

Prepared by

Innovile Support Team

October 5, 2013

INNOVILE

Beyazevler 545 Sk. Nr. 34 Gaziemir Izmir – TURKEY

Distribution List

Name Position

Innovile Support Support Unit

Network Group Company

INNOVILE , Innovative Mobile Network Solutions / 25

Document Name Accela Consistency Analysis – User Manual

Prepared by: Atacan EMRE Checked by: Fernando NUNES Approved by: Serkan TAŞKIN

Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013

Document version [2.1] – [05.10.2013]

Statement of Confidentiality & Non-Disclosure

Innovile Software Team

12 July 2013

This document provides KPI definitions integration procedure for Focus

www.innovile.com

Disclaimer: This document is provided by Innovile Telecommunications Ltd. without any claims, warranties or

indemnifications.

Improvements and changes in this document due to typographical errors, inaccuracy in current information, or

improvements to programs and/or equipment may be made by Innovile Telecommunications Ltd. at any time

without any notice(s). These changes will, however, be incorporated into new revisions 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, manual or

otherwise, without the prior written permission of the copyrighted owner, Innovile Telecommunications Ltd.

All other trademarks are the property of their respective holders.

Copyright © 2013 Innovile Telecommunications Ltd.

All rights reserved.

Company Information

Innovile Telecommunications Ltd.

Beyazevler 545 St. No: 34

35410 Gaziemir-Izmir Turkey

Support Contacts

E-Mail: [email protected]

Phone : 90-232-2820268

Fax : 90-232-2820109

Web : www.innovile.com

mailto:[email protected]

http://www.innovile.com/




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


Contents Statement of Confidentiality & Non-Disclosure .......................................................................................................... 2

1. Introduction ......................................................................................................................................................... 5

2. Purpose of this document .................................................................................................................................... 5

3. Audience .............................................................................................................................................................. 5

4. Terms and Definitions .......................................................................................................................................... 5

5. Revision History.................................................................................................................................................... 6

6. RACI Chart for this document .............................................................................................................................. 6

7. Roles and Responsibilities .................................................................................................................................... 7

8. System Environment ............................................................................................................................................ 7

8.1 System Software Components ..................................................................................................................... 7

8.2 Security Considerations ............................................................................................................................... 7

8.3 Special Hardware Considerations ................................................................................................................ 7

9. Accela Enter Page and Sub Modules .................................................................................................................... 8

9.1 Data Planning ............................................................................................................................................... 8

9.2 Operational Support .................................................................................................................................... 9

9.3 Consistency Analysis .................................................................................................................................... 9

10. Consistency Analysis RAN Sub Modules ........................................................................................................ 10

10.1 Workspace ................................................................................................................................................. 10

10.2 Node ........................................................................................................................................................... 11

10.3 Functions .................................................................................................................................................... 12

11. Functions Items Details .................................................................................................................................. 13

11.1 Neighbour Relations Check ........................................................................................................................ 13

11.1.1 One way Missing Relations ................................................................................................................ 13

11.1.2 Co-Site Missing Relations Check ........................................................................................................ 13

11.1.3 Number of Relations .......................................................................................................................... 13

11.2 Multi Carrier Neighbour Definitions Check ................................................................................................ 14

11.2.1 Neighbour Definitions Between 2G And F2 Cells ............................................................................... 14

11.2.2 Neighbour Definitions Between F2 And F1 Cells ............................................................................... 14

11.2.3 UMTS Co-Cell Neighbourhood Consistency ....................................................................................... 14




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11.3 OSS Definitions Check ................................................................................................................................ 15

11.3.1 RAN Definitions .................................................................................................................................. 15

11.3.2 MSC Definitions .................................................................................................................................. 16

11.4 Geographical Check.................................................................................................................................... 17

11.4.1 Cell - Neighbour Distance ................................................................................................................... 17

11.4.2 Cell - Non Neighbour Distance ........................................................................................................... 17

11.4.3 Same BCCH Distance .......................................................................................................................... 17

11.4.4 Same BCCH/BSIC Pair Distance .......................................................................................................... 17

11.4.5 Same Scrambling Code Distance ........................................................................................................ 17

11.4.6 Selection Priority Based on Distance ................................................................................................. 17

11.5 Parameter & Feature Check ....................................................................................................................... 18

11.5.1 Conditional Check Items .................................................................................................................... 18

11.6 Statistical Check ......................................................................................................................................... 21

11.6.1 Serving Area – Tilt .............................................................................................................................. 21

11.6.2 Overlapping Cells ............................................................................................................................... 21

11.6.3 Soft Handover Overhead – Tilt ........................................................................................................... 21

11.6.4 Channel Element Utilisation ............................................................................................................... 21

11.6.5 Possible Missing Neighbourhoods based on Co-Site Neighbour Relations ....................................... 21

11.6.6 Hardware Check Requirement ........................................................................................................... 21

11.6.7 Cell LAC Control from Handover Relations ........................................................................................ 22

11.6.8 Unnecessary Neighbours ................................................................................................................... 22

11.6.9 Unbalanced Cell Traffic Distribution between Carriers ..................................................................... 22

12. Special Functions ............................................................................................................................................ 23

13. Parameter Analysis ........................................................................................................................................ 23

14. Optimisation Playground ............................................................................................................................... 25




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


1. Introduction Accela is a multi-vendor and technology operation platform used for Data Planning, Parameter Changes

and Consistency Analysis. The Accela platform aims to increase operational efficiency through a

transparent interface that enables the automation of data preparation, eases and speeds up parameter

changes and enables consistency analyses under several parameters and statistics scenarios. This Platform

consists of 3 (three) modules: Data Planning, Operational Support and Consistency Analysis.

2. Purpose of this document

The purpose of this document is to outline the basic functionalities of the Consistency Analysis Module,

sub-module operation principles and sub-functions at RAN (Radio Access Network) level. This document

also gives a basic description of the consistency items with the rules defined.

3. Audience

The target audience of this document is the Network and Network Support Groups of Mobile Operators

Audience type chapters Network Group 1-2-3-4-5 Network Support Group 1-2-3-4-5

4. Terms and Definitions

Workspace: Defined scope of consistency analysis sub-set with pre-defined node and functions

Node: Cell to Network levels subject to analysis

Functions: Pre-defined functions in Accela backbone

Special Functions: Customised functions that can be added to the module as per customer requests

without any development

RAN: Radio Access Network

Description: Additional information

OSS: Operation Support System




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


5. Revision History Version Date Authorisation Author Description

1 01.07.2011 Burak Arslan Atacan EMRE Pre-Regression

1.1 12.07.2012 Burak Arslan Atacan EMRE Post Regression

2.0 05.10.2013 Burak Arslan Atacan EMRE New features added

6. RACI Chart for this document * Authorise This individual has ultimate signing authority for any changes to the document. R Responsible Responsible for creating this document. A Accountable Accountable for accuracy of this document. (E.g., Project Manager) C Consulted Provides input (interviewee, etc.) I V S

Informed Verifier Signatory

Must be informed of any changes. Responsible for checking whether the product meets the acceptance criteria set forth in the product description Responsible for approving the verify decision and authorise the product hand-off.

Name Position * R A C I V S

Customer Company Sponsor *

Serkan Taşkın Project Office Director * * * * *

Atacan EMRE Support Head * * * * * *

Innovile Support Support & Integration Unit * * * *




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


7. Roles and Responsibilities

Role Responsibilities Responsible

Innovile Support Preparation of the User Manual

Burak ARSLAN

Controller Control the document accuracy Atacan EMRE

Project Sponsor Conducts project flows and assures

successful completion

Serkan TAŞKIN / Ahmet ÖZTÜRK

8. System Environment

8.1 System Software Components

Oracle Client

Operational IDM platform

IBS Manager

8.2 Security Considerations

Passwords and privileges settings for IBS users.

8.3 Special Hardware Considerations

Innovile Licence Dongle must be plugged into the Server.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


9. Accela Enter Page and Sub Modules Accela is a web-based application that can be run in all common web browsers (IE, Google Chrome and Mozilla

Firefox)

9.1 Data Planning Data Planning is used to create Cell Design Data with all required inputs. Process starts from finding required data

(BCCH, PSC, neighbours) with an intelligent algorithm. Data Planning is an end-to-end process that includes RF

and transmission data with a customisable (executable or basic text ) output.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


9.2 Operational Support Operational Support handles basic OSS functionalities on a (vendor and technology free) transparent

platform. Single or bulk parameter changes and Cell-Site deletion or creation jobs can easily be prepared

through this console with executable outputs ready to run at every vendor OSS.

9.3 Consistency Analysis

Consistency Analysis module is designed to track and find all type of system inconsistencies at every level of a mobile network. System is operational at RAN (Radio Access Network) , Core Network and Transport Network Levels. Each Level has 3 (three) sub menu: Consistency Check, Parameter Analysis and Optimisation Playground.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


10. Consistency Analysis RAN Sub Modules

Consistency Check module conducts main inconsistency tracking and reporting functions with 4 menu titles: Workspace, Node, Functions and Special Functions

10.1 Workspace

Workspace enables to record own customised consistency check criteria through node and function selections. Recording can be Public (open to other users) or private (specific to user)




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


Recordings can be reported to a pre-defined e-mail list. Exchange settings should be adjusted accordingly.

10.2 Node

Node selection can be done under this menu with basic and advanced filter options. Basic filter gives a list of choice where advanced enables AND/OR functions




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


10.3 Functions

Functions are the core part of the Consistency Check module. It includes all basic default inconsistency items:

Neighbour Relation Check

Multi Carrier Neighbour Definitions Check

OSS Definitions Check

Geographical Check

Parameter and Feature Check

Statistical Check




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11. Functions Items Details

11.1 Neighbour Relations Check

Neighbour relations check has 3 (three) check groups:

11.1.1 One way Missing Relations

Reports missing relations for one way neighbour definitions for 2g-2g, 2g-3g, 3g-2g and 3g-3g. Eg: Suppose there are two cells A and B. If A-->B is defined as a neighbour but B-->A is not defined then B will be reported as an inconsistency.

11.1.2 Co-Site Missing Relations Check

Reports missing neighbour relations between cells of the same site.

11.1.3 Number of Relations

Consists of two different functions;

Reports neighbour count according to the selected condition. Ex: 2G_2G neighbours where neighbour count is > 20.

Show cells that have no defined neighbour.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11.2 Multi Carrier Neighbour Definitions Check

11.2.1 Neighbour Definitions Between 2G And F2 Cells

Reports Neighbour definitions between 2G and any 3G carrier (Or all carriers together depending on user selection). Used to detect unnecessary (user-specific) neighbour definitions.

11.2.2 Neighbour Definitions Between F2 And F1 Cells

Reports neighbour definitions between 3G carriers selected by the user. The function is used to detect unwanted relations between different carriers.

11.2.3 UMTS Co-Cell Neighbourhood Consistency

Reports missing neighbour relations by taking as reference co-cell neighbour definitions. Consists of two functions 3G-3G relations and 3G-2G relations.

E.g.: Assume three different 3G carriers are used A, B and C. First function reports cells that have neighbour relation from A-->B and missing relation from A-->C. Second function reports cells that have neighbour relation from A-->2G and missing relation from B-->2G.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11.3 OSS Definitions Check

11.3.1 RAN Definitions

11.3.1.1 Inconsistent External Cell Attributes

Checks 2G, 3G cells external definitions in RNC or BSC for BCCH, BSIC, CI, LAC, SC, UARFCN and reports as an inconsistency if the external definitions for these parameters are different from the actual values. Ex: Assume 2G Cell A has BCCH value 55 but in RNC1's external definitions this cells BCCH is defined as 50, then cell A will be reported as inconsistency with Reason "Different BCCH". The same check is performed for the other parameters in the same way.

11.3.1.2 Neighbour-External Cell Definitions Check

Reports missing external definitions between BSCs for cells that are defined as neighbours. E.g.: Assume Cell A in BSC1 is defined as neighbour to Cell B in BSC2. If cell A is missing in external definition of BSC2 it will be reported as inconsistency.

11.3.1.3 Wrong LAC-CI Definitions

Wrong LAC-CI in external definitions (takes the internal cell definition under BSC/RNC as reference (master definition of MO) and compares with the external cell definition under neighbour BSC/RNC (slave definition of MO)

11.3.1.4 Multiple Definitions

Consists of three functions:

1-Checks for duplicate CI which are defined as an internal cell and also as an external cell in the same RNC.

2-Checks if a BCCH-BSIC pair is defined more than once under the same BSC.

3-Checks if a UARFCN-SC pair is defined more than once under the same RNC.

11.3.1.5 Same BCCH-BSIC-SC Pairs in Neighbours

Checks first degree and second degree neighbours that have the same BCCH, BCCH-BSIC pair and SC.

11.3.1.6 Wrong Frequency Definition Checks

Checks irregular and non-optimised frequency definitions for TCH and BCCH frequencies:

1-Co-Channel Frequencies: Checks if the same TCH frequencies are used under the same cell, same Site or on the frequencies of the best 5 neighbours.

2-Adjacent Frequency: Checks if adjacent TCH frequencies are used under the same cell or same Site.

3- Irregular Frequencies: Checks if the given BCCH frequencies are in the proper range defined by the user.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11.3.2 MSC Definitions

11.3.2.1 Internal-External MSC LAC-CI Check

Shows wrong LAC-CI in MSC external definitions.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11.4 Geographical Check

11.4.1 Cell - Neighbour Distance

Shows cells with the neighbour distances greater than the user-defined value.

11.4.2 Cell - Non Neighbour Distance

Shows cells that are closer than the distance (in meters) defined by the user and are not defined as neighbours.

11.4.3 Same BCCH Distance

Shows cells that are closer than the distance defined by the user (in meters) and having same BCCH value.

11.4.4 Same BCCH/BSIC Pair Distance

Shows cells that are closer than the distance defined by the user (in meters) and having same BCCH-BSIC Pair.

11.4.5 Same Scrambling Code Distance

Shows cells that are closer than the distance defined by the user (in meters) and having same Scrambling Code.

11.4.6 Selection Priority Based on Distance

Show neighbours inconsistency of selection priority based on distance according to the given selection priority list.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11.5 Parameter & Feature Check

11.5.1 Conditional Check Items

Site Type – Power: Checks the relation between site type and PCPICH power according to the selection of the user. Defined PCPICH power can change for different type of sites.

Ex: Assume PCPICH power for indoor sites should be defined as 330 dbm. By using this function it will report if there is any indoor site for which PCPICH power is defined different than 330 dbm. The function helps the user to correct wrong definitions of PCPICH power.

Power and Attenuation Checks: Consist of 5 functions: 1- Inconsistent DlAttenuation: Checks the downlink attenuation parameter value and compares it

with the NODEB_DLATTENNUATION values defined for each cabinet type. If the parameter value does not match with the required value it will be reported as inconsistency and the proper value will be recommended in ACTION column.

2- Inconsistent MaxTotalOutputPower: Checks the MaxTotalOutputPower parameter value and compares it with the required MaxTotalOutputPower values defined for the cabinet types. If the parameter value does not match with the required value it will be reported as inconsistency and the proper value will be recommended in ACTION column. Ex: For some cells the MaxTotalOutputPower in oss is defined as -1 instead of 60. By using this function cells with wrong definitions can be detected.

3- Inconsistent MaxTransmissionPower: Checks the MAXIMUMTRANSMISSIONPOWER parameter value and compares it with the required MAXIMUMTRANSMISSIONPOWER which in this case should be equal to "448 - DLATTENUATION-2-ANTENNASYSTEMCONTROLLER". In this equation ANTENNASYSTEMCONTROLLER value is defined based on cabinet type. If the MAXIMUMTRANSMISSIONPOWER parameter value does not match the equation value then the required value that will match the equation is recommended in ACTION Column.

4- DL Attenuation - UL Attenuation Mismatches: Checks if the parameter values of DLATTENUATION and ULATTENUATION are equal or not. If the values are not equal it is reported as inconsistency.

5- Power and Attenuation Co-Cell Consistency: Checks the DLATTENUATION, ULATTENUATION, MAXIMUMTRANSMISSIONPOWER, MAXDLPOWERCAPABILITY , PCPICH and SC parameter values for Co-Cells and reports the ones that are not equal. Ex: Assume cell AAAAA11 has PCPICH power =300 and its Co-Cell AAAAA12 has PCPICH power =315. This case will be reported as inconsistency.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


CPICH Power - MaxTransmission Power Comparison: Checks the relation of PCPICH and MAXIMUMTRANSMISSIONPOWER parameter values according to the user defined range.

TRX Number Decreasing-Increasing Cells: Shows cells that have a difference in trx number compared to the previous day. Cells on which TRX addition or removal is performed will be reported.

TRX - TCH Count: Checks the TCH -TRX count mismatches. Used in systems with Baseband Hopping. Cells with TRX number lower than 2 are not taken into account.

TRX Numreqbpc Comparison: Checks if TRX number is equal to NUMREQBPC_SUM/8. If not then it will be reported as inconsistency.

Cell On-air Status Change: Check on-air status of cells comparing with the previous day and reports the changes.

Unique SIB1PLMNTAG Under Same LAC: Check SIB1PLMNTAG parameter value under each LAC and reports the non-unique ones. SIB1PLMNTAG parameter should be unique under each LAC and it is available only for ERICSSON.

Same LAC In More Than One BSC / RNC: Reports the LAC values used in more than one RNC/BSC.

Missing BA List Active/Idle: Gets the BCCH values of the neighbours of a cell and searches for these BCCH values in the Active/Idle BA LIST of this cell. If any of the neighbours BCCH's is missing in the BA LIST the cell won’t be able to perform a HO or a Cell reselection towards that neighbour. So the function will report the missing BCCHs as an inconsistency.

Missing NCCPERM: Gets the NCC value of the neighbours of a cell and search for these values in the NCCPERM list of the cell. If the NCC value of any of the neighbours is missing in the list then it will be reported as inconsistency. For proper HO process between a cell and its neighbours the NCC value of the neighbours which is the first number of the BSIC should be included in the NCCPERM list, otherwise the BSIC can’t be detected and the HO between these cells is impossible.

Missing UMFI Active/Idle: Gets the UARFCN-SC pair from the neighbours of a cell and searches these UARFCN-SC pairs into UMFI_ACTIVE or UMFI_IDLE list of this cell. If any of the neighbours UARFCN-SC value is missing in these lists it will be reported as inconsistency. In order for the cell to perform HO or cell Reselection UARFCN-SC values of the neighbours should be included in the UMFI_ACTIVE/UMFI_IDLE lists.

Non-Defined HSDPA_QAM64, EUL, Multi Carrier: Consist of 3 functions: 1-HSDPA_QAM64: Checks for each cell's parameter value of HSDPA_SUPPORT and if it is not equal to 1 it is reported as non-defined HSDPA. 2-EUL: Checks for each cell's parameter value of EUL_SUPPORT and if it is not equal to 1 it is reported as non-defined EUL. 3-Multi Carrier: Checks for each cell's parameter value of MULTICARRIERSUPPORT and if it is not equal to 1 it is reported as non-defined MULTICARRIER.

Qoffset2sn Checks in 3G -> 3G Neighbourhoods: Qoffset2sn Checks in 3G -> 3G Neighbourhoods: Checks QOFFSET2SN parameter value and if it doesn’t match the value of the conditions below then it is reported as inconsistency: EUL_SUPPORT is defined on both cells -> qoffset2sn = 0 EUL_SUPPORT is missing on any of cells - Intra Relation -> qoffset2sn = 0 - Inter Relation - F1 -> F2 : qoffset2sn = +9 - F2 -> F1 : qoffset2sn = -9

EDGE TS & CSPSALLOC, CSPSPRIO Configuration: This function checks the current status of CSPSALLOC and CSPSPRIO parameters and according to CH012_NUMREQEGPRSBPC definition gives recommendations for the required values of CSPSALLOC and CSPSPRIO in the Action column. If EDGE timeslots are defined CSPSALLOC and CSPSPRIO values should be CSLASTPSFIRST and PSPRIO.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


Co-site 2G/3G Cell Number Difference: Checks 2g/3g cell count in a site and if the cell count is different between 2G and 3G it is reported.

Own BCCH Check in BA List: Consists of two functions: 1-Defined in active BA List: Checks if BCCH of the cell is defined in its own Active BA list. The own BCCH of a cell should not be in the Active BA list as a cell should not have a neighbour with the same BCCH. 2-Not defined in Idle BA List: Checks if BCCH of the cell is missing in its own Idle BA List. In Idle BA list a cells own BCCH should be added in case a cell reselection to a cell with the same BCCH is needed.

DCHNO - MAIO Array Consistency: Checks DCHNO count and compares it with the given MAIO count. If the count number does not match with each other it will be reported as inconsistency. The DCHNO count should be equal to MAIO count.

Cell Electrical Tilt Change: Compares the latest Electrical_Tilt value with the previous value and reports the changes.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11.6 Statistical Check

11.6.1 Serving Area – Tilt

Checks the cells serving area percentage based on TA statistics for the distance range, tilt value and percentage selected by the user. Cells that do not meet the criteria of the parameters defined in the function will be reported as inconsistency.

11.6.2 Overlapping Cells

Reports possibly overlapping cells based on the HO count of that cell over the total HO's to all cells. The cells that have a high HO percentage with each other are considered as overlapping cells.

E.g.: Assume Cell A and B defined as neighbours. If the outgoing HO Count of cell A toward cell B is higher than 50 % of the total outgoing HO's of cell A then we can say that Cell A and B are serving in the same area , so they are overlapping. This case will be reported as inconsistency. The percentage here is defined by the user.

11.6.3 Soft Handover Overhead – Tilt

Reports cells that do not meet the criteria based on SHO_OVERHEAD KPI and cell tilt value defined by the user in the function.

11.6.4 Channel Element Utilisation

Checks the correlation between RAB Fail Uplink Hardware and CE Utilisation based on the user defined value. It is used to sort cells with high RAB Fail Uplink Hardware count due to high CE utilisation. In this function the cells that need CE extension can be sorted out. CE_UTILIZATION: 100 * ULCE_USAGE_COUNT/ULCE_AVAILABILITY

11.6.5 Possible Missing Neighbourhoods based on Co-Site Neighbour Relations

Reports the best possible number of potential neighbours between the selected cells using co-site cell's azimuth and neighbour relations as a reference.

E.g.: Assume 2G-2G neighbour relation between cell A1 and cell B1. Suppose these two cells have 3G co-cells A11 and B11 not defined as neighbours to each other. If we select Reference Relation as 2G-2G and Missing relation as 3G-3G and the Azimuth degree as 20. The function first will sort the neighbour list of cell A1 starting from the best neighbour based on HO success rate. Let’s say that B1 is one of the top neighbours of A1. In this case the function will check the 3G co-cells of these two cell A11 and B11 and if the azimuth of A11 is inside +- 20 degree range of A1's azimuth and B11 is inside +- 20 degree range of B1's azimuth then B11 will be reported as a potential neighbour of A11 cell. The number of recommended neighbours in this function is defined by the user as well.

11.6.6 Hardware Check Requirement

Checks the correlation of Handovers and HO failures between neighbours to identify hardware problems. Neighbours that have low percentage of HO and high HO failures are reported as hardware faulty cells.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


11.6.7 Cell LAC Control from Handover Relations

Checks for any wrong LAC definitions by taking in consideration the percentage of handovers performed to neighbours with a different LAC.

11.6.8 Unnecessary Neighbours

This function sorts the neighbours based on the handover count and reports the lowest ones as unnecessary neighbours. The reported cells are given based on the neighbour count and HO percentage condition selected by the user. Ex: We can list worst neighbours starting from the 28'th neighbour, according to the HO attempts, where the handovers performed towards these neighbours are less than the 0.05% of the total handovers performed. In this case we can get a list of the neighbours that have very low HO attempts which means that these neighbour relations are not necessary.

11.6.9 Unbalanced Cell Traffic Distribution between Carriers

Reports the cells that have an unbalanced HSDPA traffic distribution between carriers. The level of percentage unbalance is defined by the user in the function.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


12. Special Functions

Special functions are customised reports as per customer request without any development action on the Tool with the existing database accessed. Reports can also be prepared by the Tool Admin.

13. Parameter Analysis

Parameter Analysis module runs big scale queries on network parameter database in order to track pre-defined parameter changes. Workspace enables to record own customised parameter analysis criteria through node and function selections. Recording can be Public (open to other users) or private (specific to user)




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


Recordings can be reported to a pre-defined e-mail list. Exchange settings should be adjusted accordingly.

Output module enables various types of parameter change and history queries as listed below:

Get Single Date : Get single date pre-defined list of parameter dump

Different than Default / Range Value (With and Exception List): Get Nodes with parameter values different than default value. An exception list can be defined.

User Parameter Check: Get Nodes with parameter values different than user defined criteria.

Node Comparison with a Reference Node: Compare a Node parameter with another good performing one.

Compare Two Dates: Compare two dates in terms of parameter changes for a Node after any type of activity.

Parameter Change History: Get parameter change history for a pre-defined Node and period.

Big Changes in a specified Region: Track user-defined big scale changes for a Node or Region.




Date: 12.07.2013 Date: 05.10.2013 Date: 05.10.2013


14. Optimisation Playground

Optimisation Playground is used to create cross-queries between cell physical database, configuration parameters and statistics in order to troubleshoot any problem linked with one of the query items.

Workspace enables to record own customized cross query criteria through node and function selections. Recording can be Public (open to other users) or private (specific to user)

Accela Consistency Analysis RAN - User Manual v.2.1

Documents

Transcript of Accela Consistency Analysis RAN - User Manual v.2.1