netan 2000 version 7 user manual

A powerful traffic measurement analysis tool for

SIEMENS 2G and 3G core network elements

NETAN2000 User Manual V7.0 ICM N MS P 6 1 / 111

INDEX:

........................................................................... 1

A POWERFUL TRAFFIC MEASUREMENT ANALYSIS TOOL FOR ................................................. 1

SIEMENS 2G AND 3G CORE NETWORK ELEMENTS ......................................................................... 1

1 INTRODUCTION TO NETAN2000....................................................................................................... 4

2 BASICS...................................................................................................................................................... 6

2.1 INSTALLATION ........................................................................................................................................ 6 2.2 STARTING TRAFFIC MEASUREMENT JOBS............................................................................................. 6 2.3 TRANSFER OF TRAFFIC MEASUREMENT FILES ..................................................................................... 8 2.3.1 BASIC CRAFT TERMINAL BCT.................................................................................................................... 8 2.3.2 OPERATION MAINTENANCE CENTER OMC .................................................................................................. 9 2.3.3 SWITCH COMMANDER SC ........................................................................................................................ 10 2.3.4 EXAMPLES: ............................................................................................................................................ 11 2.4 QUICKSTART......................................................................................................................................... 12 2.5 AVAILABILITY CHECK ......................................................................................................................... 15 2.6 FORCE EVALUATION ............................................................................................................................ 17 2.7 CYCLIC FILE CONVERSION................................................................................................................... 18 2.8 'PSEUDO CYCLIC' FILE CONVERSION .................................................................................................. 19 2.9 RAW FILE CONVERSION ....................................................................................................................... 20 2.9.1 RESULT FILE VIEWER............................................................................................................................... 22 2.10 TOOLS - OPTIONS ............................................................................................................................... 23 2.10.1 PRINTING ............................................................................................................................................. 23 2.10.2 EVALUATION ........................................................................................................................................ 24 2.10.3 CHART SETTINGS .................................................................................................................................. 24 2.10.4 CLEARING THE DATABASE...................................................................................................................... 25 2.11 SUPPORT.............................................................................................................................................. 25 2.12 REGISTRATION ................................................................................................................................... 25 2.13 LICENCE AGREEMENT........................................................................................................................ 26 2.14 HINTS AND TIPS .................................................................................................................................. 27 2.15 NETAN 2000 DIRECTORY STRUCTURE............................................................................................. 28 2.15.1 SUBDIRECTORY ‘DEFINITION FILES’........................................................................................................ 28 2.15.2 SUBDIRECTORY ‘COUNTER FILES’ .......................................................................................................... 28 2.15.3 SUBDIRECTORY ‘STATISTIC FILES’.......................................................................................................... 28 2.15.4 SUBDIRECTORY ‘COUNTER CLASSES’...................................................................................................... 29 2.15.5 SUBDIRECTORY ‘CELL INFO ................................................................................................................... 29 2.15.6 SUBDIRECTORY ‘DB’ ............................................................................................................................. 29 2.15.7 SUBDIRECTORY ‘EVALUATION FILES’ ..................................................................................................... 29 2.15.8 SUBDIRECTORY ‘USER DEFINED FILES’ ................................................................................................... 29 2.15.9 SUBDIRECTORY ‘LOG FILES’ .................................................................................................................. 29 2.15.10 SUBDIRECTORY ‘BIN’ .......................................................................................................................... 29 2.15.11 NETAN ROOT DIRECTORY ................................................................................................................... 29 2.16 UPDATES / NEW FEATURES................................................................................................................. 30


2.16.1 NEW FEATURES IN NETAN 2000 V4.1.................................................................................................... 30 2.16.2 NEW FEATURES IN NETAN 2000 V5.0 (SR7-9) ....................................................................................... 30 2.16.3 NEW FEATURES IN NETAN 2000 V6.0 (SR7-9 / SSNC / GPRS) ............................................................... 30 2.16.4 NEW FEATURES IN NETAN 2000 V6.2 (SR7-CS2.0 / SSNC V13/15 / GPRS) ............................................ 30 2.16.5 NEW FEATURES IN NETAN 2000 V7 (SR8-CS2.1 / SSNC V13/15 / PO20/21, GR30/GR31 ........................ 31

3 NETAN2000 RESULT FILES............................................................................................................... 32

3.1 GENERAL HANDLING ........................................................................................................................... 32 3.2 ‘SAVE TO TEXT’ FUNCTIONALITY................................................................................................... 33 3.3 THE ‘CHART EDITOR’ .......................................................................................................................... 35 3.3.1 SUBMENU ‘CHART’ ................................................................................................................................. 36 3.3.2 SUBMENU ‘SERIES’ ................................................................................................................................. 37 3.3.3 SUBMENU ‘EXPORT’................................................................................................................................ 37 3.3.4 SUBMENU ‘PRINT’................................................................................................................................... 37 3.3.5 EXAMPLE FOR CHART EDITING.................................................................................................................. 38 3.4 EVALUATIONS....................................................................................................................................... 39 3.4.1 CS (CIRCUIT SWITCHED) TRAFFIC ............................................................................................................. 39 3.4.1.1 GOS - Grade Of Service .................................................................................................................. 39 3.4.1.2 Traffic Model................................................................................................................................... 50 3.4.1.3 Trunk Group Evaluation .................................................................................................................. 52 3.4.1.4 Cell Evaluation - INTCRELL.......................................................................................................... 54 3.4.1.5 Cell Evaluation - HOTRFS.............................................................................................................. 60 3.4.2 SSNC / GPRS ........................................................................................................................................ 66 3.4.2.1 MP Load .......................................................................................................................................... 68 3.4.2.2 MTP/SCCP load .............................................................................................................................. 73 3.4.2.3 SGSN ............................................................................................................................................... 85 3.5 DETAILED EVALUATION / TIME LINE CHARTS .................................................................................. 98 3.5.1 STORE TABLE FOR POST PROCESSING......................................................................................................... 99 3.5.2 ENHANCED CHART OPTIONS .................................................................................................................. 100 3.5.3 DETAILED VIEW FOR THE PO PART: ........................................................................................................ 101

4 LONG TERM STATISTIC PROGRAM ........................................................................................... 102

4.1 LTS PROGRAM OVERVIEW ............................................................................................................... 102 4.2 IMPORT OF DATA INTO LTS............................................................................................................... 103 4.2.1 ADDING GOS, TM, TGRP, CCNC, CELL, HOTRFS AND GPRS DATA INTO LTS......................... 103 4.2.2 ADDING MP AND SSNC DATA INTO LTS......................................................................................... 104 4.3 WORKING WITH THE LTS TABLES.................................................................................................... 105 4.3.1 ‘SAVE TO TXT’ FUNCTION................................................................................................................ 106 4.3.2 ‘FILTER’ FUNCTION........................................................................................................................... 106 4.3.3 ‘SORT’ FUNCTION ............................................................................................................................. 107 4.3.4 MISCALENIOUS FEATURES ................................................................................................................ 107 4.3.5 ‘TIMELINE’ MODE ............................................................................................................................. 108

5 APPENDIX............................................................................................................................................ 109

5.1 BUTTON BAR .................................................................................................................................... 109 5.2 SUMMARY MENU BAR........................................................................................................................ 110 5.3 RESTRICTIONS .................................................................................................................................... 111 This document refers to NETAN2000 program version V7.0


1 Introduction to NETAN2000 NETAN2000 is a powerful and easy to use traffic measurement Analyzer, fully programmed with BORLAND C++. There is no need for any additional programs like MS EXCEL to run NETAN2000. NETAN2000, the NETwork ANalyzer for SIEMENS MSC/VLR/HLR and 2G/3G SGSN/GGSN/SSNC is the tool you need if you are: * A network operator or service specialist who wants to be informed about the Grade Of Service of the network * A network operator or service specialist who wants to look for problems with the help of traffic measurement * A network operator who wants to detect traffic bottlenecks as soon as possible * A network operator who wants to make a traffic forecast, essential for demand-oriented expansion * A network operator who wants to be informed about the actual traffic model All these tasks can be performed by using the integrated traffic measurement functions in a SIEMENS 2G or 3G core network. The various measurements can deliver more than 2000 different counters, which is of course a huge amount of information. To manage this information easily, to differ between important and unimportant counters and to set the different counters in a correct relation the NETAN2000 tool was developed. NETAN2000 offers the following evaluations: MSC/VLR/HLR: Grade of Service: The 'Grade Of Service' (GOS) contains the most significant values, which indicate the performance and quality of a MSC/VLR. The GOS is based on the MSC traffic measurements RECMSC, RECVLR, RECCP. Call Model: The ‚Traffic Model Evaluation' contains the most significant values, which are important for the capacity of a MSC/VLR or HLR. The 'Traffic Model Evaluation' is based on the SSS traffic measurements RECMSC, RECVLR, RECHLR, RECCP. C7 Link Load: The CCS7 Link Load analysis calculates the load of each CCS7 link. The result shows the design specific usage of the CCNC with its allocated HW-units and the relevant load in Erlang. The ‚C7 Link Load Evaluation' is based on the SSS traffic measurements REC C7LLOAD together with the DISP C7LINK command. Trunkgroup: The trunk group analysis can be separated in two blocks: • Planning values: The planning values can be used for the dimensioning of the trunk groups. The Trunk

Group Analysis detects possible bottlenecks and resource problems on the trunk groups. • 'Grade of Service' values: The 'Grade of Service' values show the success of the handled calls, e.g. the

answer rate, possible technical problems in own or other exchanges as well as possible database problems.

Cell Analysis INTCRELL/HOTRFS: By analyzing the Cell Specific Traffic Measurement Data, possible existing problem areas can be detected by the cells' geographical location. If the radio side of the network is from a different supplier than SIEMENS, the MSC traffic measurement on a cell basis is a very fast and effective way, to get an overview on the performance of the radio subsystem. Additionally the main results of the above mentioned evaluations could be stored in a database called 'Long Term Statistic'. With the 'Long Term Statistic' you will get an easy to use instrument, which allows observing the quality of the network over a long period. This is important to see figures like success rates, number of subscribers or CP load evolution.


SSNC: MP Load: The SSNC consists of several Main Processors (MP). A main processor can handle several software processes, such as packet processing, protocol handling, performance measurement and OA&M functions. Here the load of each MP is shown. The ‚MP load Evaluation' is based on the measurement CR MPLDME as well as some DISP commands. C7 Link Load: The CCS7 Link Load analysis calculates the load of each CCS7 link. The result shows the design specific usage of the SSNC with its allocated HW-units (MP) and the relevant load in Erlang. The ‚C7 link load Evaluation' is based on the measurement CR SIGLME as well as some DISP commands. GPRS / UMTS: MP load see SSNC C7 Link Load: see SSNC Grade of Service: The 'Grade Of Service' (GOS) contains the most significant values, which indicate the performance and quality of a SGSN. The GOS is based on the SGSN measurements CR GMEALL or CR UMEALL respectively. The measurements are subdivided in

• Registration (SLR) • SMS-CAMEL (SMS and CAMEL subscribers) • PDP Context (act, deact, mod, upd Contexts) • Throughput (2G) (LLC and SNDCP frames, packets, octets) • Overload (discarded and rejected packets) • Routing Area

Update (RAU) 2G (cluster change) • Routing Area (attaches and detaches) • Miscellaneous (Gr/Gs if, authentications, identifications)

Traffic model: The ‚Traffic Model Evaluation' contains the most significant values, which are important for the capacity of a SGSN.


2 Basics 2.1 Installation Hardware prerequisites: NETAN2000 runs on every Windows 32 bit operating system like WIN95 or higher. NETAN2000 needs about 4 Mbytes hard disc space and about 10 Mbytes additionally for the Borland database engine. NETAN2000 is fully programmed in BORLAND C++ Version 5 and uses for the database functions the BORLAND database engine Version 5, which will also be installed on your PC during the installation progress. NETAN2000 comes with an installation routine, which will guide you automatically through the whole installation progress. You have only to select the directory on your hard disc where you would like the tool to be installed. To start the installation routine simply double click the SETUP.EXE file and follow the steps. Please read carefully the Licence agreement.

2.2 Starting traffic measurement jobs Following measurements can be evaluated within NETAN2000: MSC/VLR/HLR (with CCNC): REC MSC MSC traffic load and grade-of-service measurement REC VLR VLR traffic load and grade-of-service measurement REC HLR HLR traffic load REC INTCELL INTCREL internal cell related measurement REC INTCELL HOTRFS Handover related files REC CP Call Processor load measurement REC TGRP Trunk group measurement REC C7LLOAD CCS7 Link Load measurement A measurement job is activated by an MML command in which the type of traffic measurement, the objects to be measured, the recording period, and the output device are specified. For NETAN2000 a continuous measurement job with output to day or cyclic files on magnetic disc is used (so called daily or cyclic files). DAILY files: Daily files contain only the data related to one measurement day. A day file is assigned to only one specific measurement job, i.e., only one traffic measurement type per file. Up to seven files can exist simultaneously for each job. If the user does not delete the file after it is evaluated, it is overwritten on the same day of the following week. Usually the measurement data is taken continuously but is processed only after input of an MML command. This means none of these measurements causes an additional CP load. The coordination processor (CP) main memory reads the data selected by the operator and outputs it to specified devices. This takes place every fifteen minutes during the active traffic measurement intervals. MML commands: REC MSC: REC MSC: UNIT=MDD-DAILY; File: MT.USMM.xxy REC VLR: REC VLR: UNIT=MDD-DAILY; File: MT.USVM.xxy REC HLR: REC HLR: UNIT=MDD-DAILY; File: MT.USHM.xxy REC INTCELL: REC INTCELL: UNIT=MDD-DAILY, TYPE=INTCREL; File: MT.USIM.xxy REC INTCELL: REC INTCELL: UNIT=MDD-DAILY, TYPE=HOTRFS; File: MT: USTM.xxy REC CP: REC CP: UNIT=MDD-DAILY; (def. 3 min.) File: TS.CPXX.xxy REC TGRP: REC TGRP: UNIT=MDD-DAILY, TGRP = X; File: TS.TGRP.xxy REC C7LLOAD: REC C7LLOAD: UNIT=MDD-DAILY, LSNAM=X; File: TS.C7LL.xxy


CYCLIC files: Cyclic files contain data of up to two days in one file. A day file is assigned to only one specific measurement job, i.e., only one traffic measurement type per file. After transferring the file to the switch commander the cyclic file has to be reset. Cyclic files can be transferred at any moment of the day. To avoid losing measurement data, it may be kept on disk for a maximum of 2 days only before being transferred to tape. . MML commands: REC MSC: REC MSC: UNIT=MDD-CYCLIC; File: MF.USMM.CYy REC VLR: REC VLR: UNIT=MDD-CYCLIC; File: MF.USVM.CYy REC HLR: REC HLR: UNIT=MDD-CYCLIC; File: MF.USHM. CYy REC INTCELL: REC INTCELL: UNIT=MDD-CYCLIC, TYPE=INTCREL; File: MF.USIM. CYy REC INTCELL: REC INTCELL: UNIT=MDD-CYCLIC, TYPE=HOTRFS; File: MF:USTM. CYy REC CP: REC CP: UNIT=MDD-CYCLIC; (def. 3 min.) File: TF.CPXX. CYy REC TGRP: REC TGRP: UNIT=MDD-CYCLIC, TGRP = X; File: TF.TGRP. CYy REC C7LLOAD: REC C7LLOAD: UNIT=MDD-CYCLIC, LSNAM=X; File: TF.C7LL. CYy


SSNC/SGSN: CR MPLDME Create MP Load Measurement CR SIGLME Create Signaling Link Meas. CR SPME Create SCCP Measurements PM_SCANREP_NExx_dd0hhmm.spf CR GMEALL/UMEALL Create SGSN Measurements All 140: To be filled

2.3 Transfer of traffic measurement files The transfer of daily files is only possible after the day concerned or at the end of a measurement job. The traffic measurement raw files have to be transferred from the magnetic disc to the PC where NETAN is installed. Therefore different possibilities can be used. Following some of these procedures will be described in detail:

2.3.1 Basic Craft Terminal BCT On the BCT you have to start the 'openFT' function. In the 'Transfer file' menu select the following parameter: File Type = Text. In the BCT you can use any available file compressor like WINZIP, WINRAR or ARJ.


2.3.2 Operation Maintenance Center OMC On the OMCS you have first to open an EMML session. Then select the GUI sub window 'Filetransfer'. A mask will pop up which looks like this:

In this window you have to specify the following parameters: Selection: OMC or OMT depending to where the file is to be transferred LOCFIL: file name on local HD (including path) REMFILE: filename on MSC TRDIR: GET (if file is to be transferred to the OMC-S) PRONAM: logical name of MSC USRINF: user log-in SESPSW: user password WRMOD: OVWR COPMOD: CHAR This will transfer the traffic measurement files from the MSC to a directory on your local OMT HD (to be specified in LOCFIL). To transfer the data from the OMT to a PC - insert floppy without write protection into floppy drive of OMT - on a UNIX shell enter 'volcheck' - enter 'cp "name" /floppy/floppy0' ("name": name of traffic file on OMT HD including path - enter 'eject' to remove the floppy from the HD In case the files are too big to be copied to a floppy, you can use the 'compress' command on a UNIX shell: compress usmmsc1 If 'compress' is used the files which are transferred must not have any extension: (e.g. 'usmmsc1' rather than 'usmmsc1.txt')


2.3.3 Switch Commander SC For getting data of MP, SSNC, and SGSN/GGSN measurement the PDC (performance data collector, see description A50016-D521-B100-2-7620) must be installed. Here the data are available and can be copied to disc as they are; if there are many files, zipping is recommended. For the copy of the DISP commands please make sure to use the ASCII mode, not UNICODE for creating the file!

NETAN2000 User Manual V7.0 ICM N MS P 6

No

Yes

10 / 111

2.3.4 Examples: You can easily check the correct format of the file after transferring to your PC, the file must be readable in a normal text editor and must not contain any unreadable characters. Example of a RECMSC raw file format: 11671929G016 151MSC0199-06-2800-00-0000-00-0000-00-0099-06-2800-00-00-0000-00-00-0000-00-00-0000-00-00-00000000MT.USMM.MO1 99-06-2800:15 ***1862 0 0 0 0 0 0 0 0 0 2924 0 0 0 0 0 0 0 1174 0 3674 2868 4200 6030 58780 151693 0 147685 132634 154281 21262 0 125323 114362 19561 0 1556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1954 0 1799 1383 1825 206 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 174 1240 149 0 142 0 0 0 1854 0 0 1089 0 0 0 0 0 0 0 0 0 0 0 Example of a SSNC/SGSN raw file format: HEADER;vcpuCurrentdata;26;EWSDV13; ;0;SCANNER; ;0;vcpu00mpTotalAverageLoad;vcpu00mpTotalMaximumLoad;vcpu01SystemIntegrityAverageLoad;vcpu01SystemIntegrityMaximumLoad;vcpu02sltPrhAverageLoad;vcpu02sltPrhMaximumLoad;vcpu03oamAverageLoad;vcpu03oamMaximumLoad;vcpu04callpAverageLoad;vcpu04callpMaximumLoad;vcpu05SystemUpgradeAverageLoad;vcpu05SystemUpgradeMaximumLoad;vcpu06ccs7NmAverageLoad;vcpu06ccs7NmMaximumLoad;vcpu07vcpuSpare07AverageLoad;vcpu07vcpuSpare07MaximumLoad;vcpu08vcpuSpare08AverageLoad;vcpu08vcpuSpare08MaximumLoad;vcpu14backgroundAverageLoad;vcpu14backgroundMaximumLoad;vcpu15auditAverageLoad;vcpu15auditMaximumLoad;vcpu16idleAverageLoad;vcpu16idleMaximumLoad;vcpu17SystemBaseLoadAverageLoad;vcpu17SystemBaseLoadMaximumLoad vcpuCurrentdata;EWSDV13;2001/10/11;05:30:00;SGSN4.1;900;FALSE;SCANNER;26;997;999;0;0;0;0;15;500;0;0;0;0;0;0;0;0;0;0;0;0;0;3;960;976;22;43 vcpuCurrentdata;EWSDV13;2001/10/11;05:30:00;SGSN4.8;900;FALSE;SCANNER;26;997;999;0;0;0;0;1;10HEADER;switchingElementMeasurement;4;EWSDV13; ;0;SCANNER; ;0;numInMSU;numLostMSURoutErr;numOutMSU;numTransitMSU;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1 switchingElementMeasurement;EWSDV13;2001/10/11;05:30:00;SGSN4;900;FALSE;SCANNER;4;10;0;0;0;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1 HEADER;sgsn2gCamelCurrentData;3;GR20; ;0;SCANNER; ;0;attCamelDialogues;unsuccCamelDialoguesSsf;unsuccCamelDialoguesScf;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1 sgsn2gCamelCurrentData;GR20;2001/10/11;05:30:00;SGSN4.1;900;FALSE;SCANNER;3;0;0;0;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1


2.4 Quickstart • Copy the measurement files of the NE's you want to analyze into a directory on your PC. • Choose 'START EVALUATION' from the 'EVALUATION' menu. The 'Availability Check' window will

appear.

• Select the 'Source Directory' where the measurement files are stored. • Select a 'Result Directory' where you want to store the result files. • Alternatively, the box ‘Map RESULT to SOURCE directory’ can be ticked which automatically sets the

result directory the same as the source directory. • Paths in 'Source Directory' and 'Result Directory' can contain a maximum of 50 characters. Press The availability check will be performed. This means all files in the specified 'Source Directory' will be scanned for the following information: - Measurement file, which can be used for an evaluation? - Date and NE name of the measurement file - All necessary measurement files included?


After finishing the availability check the window will change and present all possible evaluations:

Here you will get a choice of all possible evaluations found in the specified directory. You can now select all evaluations, all evaluations of a common type or only a single evaluation. When you have chosen the evaluations you want to perform click on the button.


In the 'EVALUATION WINDOW' you can observe the progress of the current evaluations. After finishing the evaluation you can close the window and open a result file by choosing 'OPEN RESULT FILE' from the 'FILE' menu in the main window.


2.5 Availability Check The availability check is the first program part, which runs immediately after starting an evaluation. The main tasks of AV check are: - Checking a specified directory (optional with its subdirectories) on availability of traffic measurement files which can be used for evaluations - Checking the contents of the files for MSCNAME, DATE and TYPE of traffic measurement - Checking the availability of a MLOG file with additional information like DISPC7LINK, DISPMP….. - Checking the traffic measurement files on completeness of all measurement intervals When AV check is finished the results will be shown in the lower part of the window:

With these 2 butttons you can select and deselect all possible evaluations (all NE's, all dates)

Here you can select all possible evaluations of one type (e.g. Grade of Service)

Selecting a NE and a Date will present the possiblevaluations on the right side

e


For SSNC/GPRS availability check shows also the available/missing measurement files (ID groups):


2.6 Force Evaluation Usually a GOS or TM evaluation is only possible if all required files are found by the ‘Availability Check’. For GOS this is RECCP, RECMSC and RECVLR. For TM this is RECCP, RECMSC and RECVLR or RECCP and RECHLR. Now in some cases it might be necessary to allow an evaluation even if not all of the required files are found. Examples: A Traffic Model evaluation has to be made for a pure Gateway MSC: only RECCP, RECMSC are available A GOS evaluation has to be made but no RECCP file is available: only RECMSC and RECVLR. For such cases one can use the ‘Force Evaluation’ feature:

By checking this box NETAN will use dummy files from the directory ‘Evaluation Files’ (all counters in that files are set to 0) to allow GOS and TM evaluation. Attention: Use this function only if you have to. Otherwise the results might be confusing.


2.7 Cyclic file conversion In software version SR8 a new possibility to record measurement files in a cyclic file format was introduced. The advantage of this type is that the user can transfer the result file from a running measurement at any time. As these files can contain data from one quarter up to app. 3 days a new routine had to be implemented in NETAN2000 to produce readable result files out of this data. Explanation how it works: First the 'Availability Check' checks the header of the measurement files. A cyclic file is identified within the header by the filename 'MF.xxxx.CYy'. 01931G018 15 MSC04 MF.USVM.CY1 00-11-1401:00 630123180 3570 4675 6742 39019 0 930 39 25 Example of a cyclic file A special routine within the 'Availability Check' converts now all detected cyclic files into pseudo daily files. This means the contents of the cyclic files will be rearranged and copied into files, which correspond to the format of the known daily files. The new files will become following naming construction: - MSC0400-11-14USVM.craw (includes MSC name, data, measurement type). After the CRAW files are prepared the following procedure is the same as with original daily files. Even if the CRAW files do not contain the complete data of a full day e.g. only one hour an evaluation will be possible if there are the same intervals available in the needed measurements (e.g. for GOS evaluation RECCP, RECMSC and RECVLR).


2.8 'Pseudo cyclic' file conversion The so-called 'pseudo cyclic' file format is used in some projects. It works in that way that the measurement is started as daily/single but with OMC scripts the measurements can be stopped after 15 minutes transferred to the OMC and started again. This means that the contents look the same like for cyclic files but the header is different. For this files a new function is implemented.

If you want to translate such files you have to select the function 'ALL AS CYCLIC' before you start the AV check. During the AV check following decision box appears:

Here you have to select 'YES' or 'JA' which means that the original files will be deleted and only the combined CRAW files will exist in the directory. After the AV checks you can select as usual the evaluation types you want to perform.


2.9 Raw file conversion The traffic measurement data generated by the MSC is kept on the MDD. The format of the files is an MSC internal format and cannot directly be interpreted by some common PC-software (e.g. EXCEL). In order to overcome those weaknesses, a conversion routine is part of NETAN2000. This routine serves as an interface between the MSC's daily traffic measurement files (also referred to as 'source files’) and the so-called 'traffic measurement result files'. NETAN2000 can automatically detect the type of traffic measurement and converts the file from its MSC-internal format to a uniform text format. Even for different traffic measurement types, the format of the result file has the same and a very simple structure. As they consist of text only, the result files can easily be imported into EXCEL sheets or word processing software. 80931929G018 151TES5100-03-0900-00-0000-00-0000-00-0000-03-0900-00-00-0000-00-00-0000-00-00-0000-00-00-00000000MT.USMM.TH1 00-03-0900:15 ***1862 0 0 0 0 0 0 0 0 0 2299 1246 1245 0 1 0 0 0 1003 0 1642 1246 8010 5756 16955 101896 35393 46389 98635 86028 3822 32688 39051 89051 3706 0 4515 278 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 931 245 412 521 627 128 0 2 4 0 0 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 108 490 39 376 0 0 0 1 819 0 0 445 0 0 0 0 805 441 279 0 0 0 0 0 0 0 0 0 36 0 5864 1 20 15 0 4 0 0 0 0 0 1 0 0 1 0 0 0 0 1 0 0 4 7 17 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 13 0 2 0 0 0 0 0 0 0 19 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 450 804 0 0 441 0 1 29 0 356 0 Example of a source file File: MT.USMM.TH1 MSC: TES51 Ver. G018-SR8 Date: 00-03-09 Time: 00:00 - 00:00 Counter 00:15 00:30 00:45 01:00 01:15 01:30 01:45 02:00 NUM_RESET 0 0 0 0 0 0 0 0 NUM_RESET_CIRCUIT 0 0 0 0 0 0 0 0 NUM_SSP_BSSAP 0 0 0 0 0 0 0 0 NUM_SIGN_POINT_PROHIB 0 0 0 0 0 0 0 0 NUM_CALLS_REL_BS 0 0 0 0 0 0 0 0 0 NUM_RECEIVED_OVERLOAD 0 0 0 0 0 0 0 0 NUM_SEND_OVERLOAD 0 0 0 0 0 0 0 0 NUM_RECEIVED_GCP 0 0 0 0 0 0 0 0 NUM_RECEIVED_CIP 0 0 0 0 0 0 0 0 NUM_RECEIVED_CLASSM_UPD 2299 2163 1958 1743 1546 1516 1478 1447 NUM_TOTAL_START_IMEI_CHECK 1246 914 766 678 539 465 389 287 NUM_IMEI_CHECK_WHITE 1245 914 766 678 539 465 389 287 NUM_IMEI_CHECK_GREY 0 0 0 0 0 0 0 0 NUM_IMEI_CHECK_BLACK 1 0 0 0 0 0 0 0 NUM_IMEI_CHECK_UNKNOWN 0 0 0 0 0 0 0 0 Example of a result file imported in MS EXCEL


Once an 'availability check' is finished you have the possibility to start only a raw data conversion by clicking on 'Translate All': All files in the source directory will be translated!

The new files will have the following naming construction: - MSC0401-07-05USVM.resh (includes MSC name, data, measurement type). Following measurement types are supported in the current NETAN version: REC MSC CR MPLDME REC VLR CR SIGLME REC HLR CR SIGNEME REC INTCELL (INTCREL) CR SIGPTME REC INTCELL (HOTRFS) CR SIGLSME REC LOCAREA CR SIGDPME REC CP CR SPMESSN REC TGRP CR SPME REC ANGRP CR GMEALL / UMEALL (2G / 3G) REC C7LL REC DEST REC SCTC REC AC REC SSERV REC IWE REC EIR Measurements from REC GP SP:BSSGP REC LTG SP:GTP (SGSN) REC DLU SP:GTP (GGSN) REC PBX – not supported in current version SP:ISP This list will be extended.


2.9.1 Result file viewer This function allows viewing the .RESH files by using the MS EXCEL OLE embedding function. Prerequisite is an installation of MS EXCEL on the PC. From the menu 'File' and 'Open Result File' you will come to following window:

Here you can select any translated file with the extension .RESH. By clicking on 'Öffnen' or 'Open' the file will be opened in an embedded MS EXCEL application:

Right click with mouse on ‘OPEN’ – you are in MS EXCEL

Here you can have a look on the counters or open the file in MS EXCEL for further processing like adding charts or calculations. Attention: The regional settings of your windows system must be ',' for the 'list separator'. (Control Panel - Regional Settings)


2.10 Tools - Options

2.10.1 Printing With the Printing Options you can arrange the position of the result files within the printed pages. The distance to the margins can be selected and also the distance to the text charts. This has to be done for the different result files separately. Attention: An error message will occur after closing the Options window if the line margin is equal or bigger than one of the text margins. Example: You have also the possibility to select your own Footer text for the printouts. The header will be added automatically by the program using NE NAME, MEASUREMENT DATE, APS RELEASE on the left side and TYPE OF EVALUATION and EVALUATION DATE on the right side. Additionally to the normal print option in GOS there is also the possibility to select 'print all GOS' in the file menu. This prints all sheets at once.


2.10.2 Evaluation

If the checkbox 'Restrict Trunk Groups' is marked, some restrictions on displaying trunkgroups are set. Attention: This restriction is only valid during the evaluation of a trunkgroup file. It has no influence on opening already existing trunkgroup result files. The restrictions are:

• Trunkgroups with no call attempts but showing low traffic volume are not displayed (signaling trunk groups)

• Trunkgroups with call attempts but no traffic are not displayed

2.10.3 Chart Settings

Allows configuring the cake charts within the GOS result file.


2.10.4 Clearing the database In order to start a new set of evaluations, the old database files have to be removed. This can be done by clicking ‘Clear DB’ in the 'Tools' menu. If not the open result file process uses the existing temporary DB files.

2.11 Support Any errors, questions, feature reports, comments, criticism, praise or others please report to the following e-mail address:

[email protected]

We will do our best to adapt NETAN2000 to the users requirements.

2.12 Registration NETAN2000 is copy protected by a simple software solution. Every registered NETAN2000 user is allowed to enable the tool on ONE single workstation only. On the first start of the tool the user will be asked for an 'Authorization Code'.

By clicking on 'OK' or 'CANCEL', a second mask will appear and a 'PC identification' is displayed.

A registered user can now obtain the valid 'Authorization Code' for this 'PC identification' from the SIEMENS AG, ICM OP MS ND6.


The 'Authorization Code' can be obtained by sending an e-mail to following address:

[email protected]

fter the correct authorization key has been entered correctly, NETAN2000 starts normally. On any further

icences can include the full functionality of the tool or just single functionalities (like 'no evaluation possible’)

o remove a Licence key one can use the function 'Tools' - 'Remove Licence' - e.g. to change from a

lease notice that if you are using a network PC the code is always related to the User Identification (means

Authentication can be removed by Menu bar : Tools � Remove licence.

2.13 Licence agreement

. Binary Code Licence "Licence") contains rights and restrictions associated with use of the

alling the

. Copyright is confidential copyrighted information of Siemens. You shall not modify, decompile,

ased,

. Trademarks and logos ademark of Microsoft Corporation. Borland is a trademark of Borland international,

. Disclaimer of warranty S IS," without a warranty of any kind. ALL EXPRESSED OR IMPLIED

NT, ARE

. Limitation of liability BE LIABLE FOR ANY DAMAGES SUFFERED BY YOU OR ANY THIRD PARTY

EGARDLESS

. Severability sume the entire risk of using the program. IN NO EVENT WILL SIEMENS BE LIABLE FOR

. Termination

Astarts of NETAN2000 no more dialogs will be displayed. Land the licences can also have an expiry date (for e.g. test licences). Trestricted Licence to a full Licence. Pe.g. NT login).

1This binary code Licence (accompanying software and documentation ("Software"). Read the Licence carefully before instSoftware. By installing the Software you agree to the terms and conditions of this Licence. 2The Softwaredisassemble, decrypt, extract, or otherwise reverse engineer Software. The Software may not be leassigned, or sublicenced, in whole or in part. You may access the commercial version of NETAN2000 through a network, provided that you have obtained individual licences for the Software covering all workstations that will access the Software through the network. 3Windows is a registered trInc. All other trademarks and service marks are the property of their respective owners. 4The Software is provided "AREPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMEHEREBY EXCLUDED. 5SIEMENS SHALL NOTAS A RESULT OF USING OR DISTRIBUTING SOFTWARE. IN NO EVENT WILL SIEMENS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND ROF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SIEMENS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 6The user must asANY DAMAGES IN EXCESS OF THE AMOUNT SIEMENS RECEIVED FROM YOU FOR A LICENCE TO THE SOFTWARE, EVEN IF SIEMENS SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCHDAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY. 7


The Licence will terminate automatically if you fail to comply with the limitations described herein. On termination, you must destroy all copies of the Software. 8. Governing law Any action related to this Licence will be governed by German law. No choice of law rules of any jurisdiction will apply. 9. Limitation of support If you are using the Software free of charge under the terms of this agreement, you are not entitled to support or telephone assistance. 10. Multi-user packages, company Licences If the copy of the Software you received was accompanied by a printed or other form of "hard-copy" Licence whose terms vary from this agreement, then the hard-copy Licence governs your use of the Software. 11. High risk activities The Software is not fault-tolerant and is not designed, manufactured or intended for use or resale as on-line control equipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapons systems, in which the failure of the Software could lead directly to death, personal injury, or severe physical or environmental damage ("High Risk Activities"). Siemens specifically disclaims any express or implied warranty of fitness for High Risk Activities.

2.14 Hints and Tips - When I zoom into a chart, how can I come back to the full view? • By drawing a rectangle with the mouse on the chart you can zoom into the timeline. Drawing a rectangle

by starting in the chart and ending outside the left border will change back to the 24-hour chart. - Is it possible to sort a result table within the TGRP or CELL evaluation? • Yes, it is. By clicking on the header of a column the table will be sorted in ascending order to the values

in the column. A second click on the same column sorts the table descending. - If I have lots of measurement files from different network elements, how can I find out which measurements can be evaluated? • NETAN2000 automatically reads the headers of all files in the 'source directory' and checks which files

can be used for evaluation. If it's necessary to have more than on file for a measurement (e.g. for GOS or Traffic model), NETAN2000 will automatically scan through those files and check for their availability.

-When you try to open a ‘Result File’ you get the error message " '00:00' is not a valid time " • Solution: Change the windows settings in 'Control Panel' - 'Country Settings'.

There is a possibility in the sheet 'Time' to change the separator. It must be set to ‘:’


2.15 NETAN 2000 directory structure All files used by the NETAN2000 application are structured in different subdirectories. These files are simple text files, which are used to define externally different things like formulas, counters.... Please notice: Manipulating the DEF, STAT, COUNTER or INI files in an incorrect way may cause system crashes in NETAN 2000. All manipulations will lead to the loss of any kind of warranty. Explanation of the different subdirectories:

2.15.1 Subdirectory ‘Definition Files’ Contains various definition files: - BUSY.DEF Contains the formulas to calculate the busy hour/quarter for the GOS, TM, TGRP, CELL and CCS7 evaluation. - MLOG.DEF Defines the position of the used information in the DISPC7LINK displays - RESTRICT.DEF Definition of trunkgroups with unnormal behavior - TM2TXT.DEF Definition the values from a TM evaluation which will be imported to a txt file

2.15.2 Subdirectory ‘Counter Files’ One counter file exists for each APS version. Used for the translation of the measurement files. Contains for every counter measurement type, byte position, field length, counter name e.g. CS21.cnt

2.15.3 Subdirectory ‘Statistic Files’ Defines the formulas used in the different evaluations e.g. CS21.stat - LTSstat.stat Defines the rates used in the LTS file, which are extracted from the NETAN result files. Each Line contains the evaluation type, rate name and the unit Please notice: If you want to add new rates add them at the end of the evaluation section only. Otherwise you cannot use your old LTS files.


2.15.4 Subdirectory ‘Counter Classes’ Contains the .cc files which describe for the PO part the different measurement counter classes

2.15.5 Subdirectory ‘Cell Info Contains the cell information ini file which define the relation between CELL-ID/LAC and cell names and categories - optional.

2.15.6 Subdirectory ‘db’ Used by NETAN to store temporarily database files.

2.15.7 Subdirectory ‘Evaluation Files’ Dummy files for the ‘Forced Evaluation’ feature

2.15.8 Subdirectory ‘User Defined Files’ Contains the files for the ‘User Defined Page’ feature – optional.

2.15.9 Subdirectory ‘Log Files’ Contains the ‘Availability’, ‘Evaluation’ and ‘NETAN2000’ LOG files

2.15.10 Subdirectory ‘Bin’ This directory is used to story files which created error during availability check or evaluation.

2.15.11 NETAN root directory - NETAN2000.INI The main initialization file of NETAN2000 contains:

• Relation between the Version number in the measurement file and the APS version • Relation between APS version and used COUNTER.XXX file • The OPTIONS settings • The rates displayed in the LTS tool


2.16 Updates / new features NETAN2000 is continuously updated and adapted to field requirements. There is a set of new features planned such as:

• Performance improvements • LTS management report improvements • IP measurement for PO

2.16.1 New features in NETAN 2000 V4.1 • Now able to handle the cyclic file format (from GSM version SR8 on available) • Translation of raw data files like RECLTG, RECSCTC, RECPBX, RECDEST... • Now able to handle the 'pseudo cyclic' file format • Borland Database engine V5

2.16.2 New features in NETAN 2000 V5.0 (SR7-9) • Support of SR9 measurement files • Faster raw data translation routine • New copy protection routine (higher security and flexibility) • Some bugs removed • Availability check possible with long directory names, files without attribute 'archive' • Linkset names up to 12 characters • More tolerant with DISPC7Link files • More supported measurement types for the raw data conversation • Result file viewer function • Option for setting restrictions on trunkgroup result files

2.16.3 New features in NETAN 2000 V6.0 (SR7-9 / SSNC / GPRS) • Translation of PDC output files into ‚daily’ files and sorted type specific • MP load evaluation • SSNC evaluation • SGSN evaluation • HOTRFS evaluation • ‘Copy to clipboard’ functions

2.16.4 New features in NETAN 2000 V6.2 (SR7-CS2.0 / SSNC V13/15 / GPRS) • TGRP evaluation – now source and result directory can be different again • Some corrections in the counter.def and stat.def files • TMtoTEXT function allows an automatic export of all traffic model variables from different NE’s

during the evaluation. • Better overview in MP evaluation incl. LOAD A indication • Linkset ID in MTP evaluation • Bugfixes for graph mode in SGSN evaluation


2.16.5 New features in NETAN 2000 V7 (SR8-CS2.1 / SSNC V13/15 / PO20/21, GR30/GR31 - Official CS2.1 Evaluation - New directory structure

Cell Info: optional ini file with additional cell information per MSC Counter Classes: SGSN, SSNC counter class definition Counter Files: All counter definition files Db: temporarily database files Definition Files: Busy, MLOG, TMtoTXT, RESTRICTION definition files Evaluation Files: dummy files for GOS, TM forced evaluation LOG Files: Evaluation, Availability Log files Statistic Files: All statistic definition files User Defined Files: optional all files for the UDP feature

- GOS/TM Forced evaluation check box If only CP and MSC file If only MSC and VLR file evaluation is possible Dummy files will be used from folder: Evaluation Files - Cell evaluation (FRQ 21/11) Added Call Success/Failure Rate Added Total Line at the table end Added information about total/excluded cells (if filter is used) Added Cell Info: In directory Cell Info a file for each MSC can be stored which contains Cell Names, Categories This information will apply in the result file! It can be filtered according two categories (categories e.g. SBS, Motorola, D900, D1800.......) - GOS User defined Labels can be changed now – see stat files

- Under ‚Save to Text’ now option to save ‚Counter’ or ‚Statistic’ Table to text format available for post processing options

- Chart Editor functionality in the Pie Charts of GOS

- Chart Editor in detailed view (right mouse click)

- SSNC: LIC/HS Link tables corrected

- SSNC V15 evaluation new and separated Counter/Statistic files

- GR20, GR30, GR31 separated statistic files

- Log files for evaluation and availability (directory: Log)

- NETAN starts with maximized window

- Enhanced LTS tool


3 NETAN2000 Result Files

3.1 General Handling Main features:

- The result files contain lots of predefined formulas - Several different Result Files can be opened at the same time in different windows - The user can easily switch between the Result Files and arrange all the files horizontally, vertically

or cascade it - Result Files can be printed (one page or all pages) - Result Files can be saved to Bitmap format - The size of the Result Files on screen can be changed by the user to his requirements (resolution of

the monitor) - The user can select the Busy Hour or any full hour of the day - Additionally, the evaluated interval can also chosen to be the whole day. In this case an average of

all parameters over the whole day are calculated. - The Time Line Chart functions can show each counter and formula in a result file

The following picture gives an overview about the general functions:

Copies the whole page into the ‚Clipboard’ resize the result appearance

Right mouse click opens the chart editor

Copies the graph into the ‚Clipboard’


3.2 ‘SAVE TO TEXT’ functionality This feature allows the user to save the complete database from one result file into a text file which can be easily imported into MS EXCEL. One can save either the ‘COUNTER DATABASE ‘which are all raw counter for the whole day or the ‘STATISTIC DATABASE’. The ‘STATISTIC DATABASE’ contains the calculated statistic values from all intervalls.

xample of a ‘Counter Database’ file imported into MS EXCEL:

E



Example of a ‘Statistic Database’ file imported into MS EXCEL:

The Result File Database contains values for each individual interval as well as for all complete hours, for the busy hour and the whole day of each individual object (e.g. one cell, one trunkgroup…). HINT: If you want to work only with the quarterly values in EXCEL use the ‘FILTER’ option and select for the column ‘DurType’ only ‘Quarterly’ values.

3.3 The ‘Chart Editor’

You can activate the ‘Chart Editor’ by ‘Right Mouse Click’ within the ‘Evaluation Windows’ or in the ‘Graphical Analysis’ window.

Clicking on ‘Cha select the general type of the shown graph: nge’ will open a menu where you can


3.3.1 Submenu ‘Chart’

he he background ‘PANEL’:

In the menu ‘Chart’ you can change the general format of the chart and you can format the ‘AXIS’, t‘TITLES’, the ‘LEGEND’ and t


3.3.2 Submenu ‘Series’

This menu allows to change the formatting individually for each series.

3.3.3 Submenu ‘Export’

3.3.4 Submenu ‘Print’


3.3.5 Example for chart editing


3.4 Evaluations

.4.1 CS (circuit switched) traffic

ll the formulas you can find in the documents: • MNSI_GOS for GOS evaluation • MNSI_TM for traffic model evaluation • MNSI_TGRP for trunk group evaluation • MNSI_CCS7 for Nr7 evaluation in CCNC • MNSI_CELL for cell evaluation in MSC

.4.1.1 GOS - Grade Of Service

.4.1.1.1 Prerequisites

3 A

3

3

he Grade Of Service evaluation requires following measurements: - REC CP Call Processing Load - REC MSC MSC specific measurement - REC VLR VLR specific measurement

.4.1.1.2 Basics

T

3

hat is Grade Of Service: Requests and attempts for certain services and system functions are offered to or generated by the PLMN and its units according to the model above and used for obtaining the data for GRADE OF SERVICE measurement. These requests and attempts can be generated by either the mobile subscriber (e.g. by dialing a number) or by the system (e.g. by starting a handover). The servabanUnsucom

W

Requests Attempts

Behaviour of mobile subscriber

Unsuccessfully terminated

System behaviour

Reasons related to user/network

NET

uccessfully completedS

requests and attempts bring about system activities being are carried out with a certain grade of ice. Some attempts are completed successfully whereas others are terminated unsuccessfully (loss, donment or rejection). ccessful attempts can be offered again or automatically repeated by the system. Successfully

pleted actions can lead to further activities.

AN2000 User Manual V7.0 ICM N MS P 6 39 / 111

A distinction can be made between the following groups of unsuccessfully terminated attempts: • Behavior of the mobile subscriber (e.g. incorrect dialing, replacing of the handset during call set up...)

.g. lack of resources, overload...) • Reasons related to the user or the network (e.g. certain features are blocked, subscriber blocked by the

rement jobs are derived from the error causes within the protoco s ...). Two rel e disti• The le cted e in the LTG (GP) is sent as a "reason for call

failu " lease side and B-side) to the CP. The call is then pre d.

The rele ected e in the CP is sent as a "reason for call termination " (RCT) in a command (e.g. TERMINATE) to the LTG's. The call is then prematurely

i

ent part includes data concerning the call set up for speech and data calls. easurement part, most of the counters can be differentiated by several traffic

pes. The traffic types provided in the MSC contain information on the origin and destination of the call.

he observed MSC detects whether the call to be handled either has been originated in its own area, or ansmitted by another exchange. From this po h: Mobile originating traffic (MORTR): All traffic being initiated by a mobile subscriber in the area of the

observed MSC, whatever the destination will be. Mobile incoming traffic (MICTR): Mobile traffic that has been directed to the observed MSC by another

exchange.

ext ss is started as the result of digit analyzing. Once the result of the interrogation as been established through digit translation, the observed MSC knows where to find the call destination, hanging the original traffic type into one of the following types:

a of

N). • Mobile transit traffic (MTRANS): Traffic that has neither been initiated nor terminated at the observed

MS.

• System behavior (e

operator...). Certain errors within the grade of service measu

ls u ed (e.g. MAPeas events can be nguished: re ase event dete by the call processing softwarre (RCF) in the re message from the LTG's (A-

maturely terminatease event det by the call processing softwar•

term nated. The MSC basic traffic measuremWithin this MSC basic traffic mty

BSSMORTR

PSTN PSTN

MSCMTRANS

MSC

PSTN

MOUT_PLMN

UT_NOT_PLMN

BSSBSSMORTR

PSTNPSTN PSTNPSTN

MSCMTRANS

MSC

PSTNPSTN

MOUT_PLMN

UT_NOT_PLMN

MSCMSC

MICTRMICTR

MSCMSC

BSSMTER BSSBSSMTER

MOMO

Ttr int of view one can distinguis•

•

N an interrogation procehc• Mobile terminating traffic (MTER): This applies to the traffic towards each mobile station in the are

the observed MSC • Mobile originating outgoing traffic to a mobile party who is subscribed in the home PLMN

(MOUT_PLMN), wherever he is actually roaming. • Mobile originating outgoing traffic to a party from the PSTN or another PLMN (MOUT_NOT_PLM


3.4.1.1.3 Evaluation MOUT Table (Mobile outgoing):

The diagrams are divided into MOC’s for MOUT_PLMN and MOUT_NOT_PLMN. For each case, the ‘answer’, ‘no answer’ and ‘B-busy’ rates are shown. These three values are combined in ‘MOC success rate’. The rest which is covered with ‘Others’ indicates potential problems. Additionally, ‘average call duration’ and ‘Fax/Data’ success rates are displayed. MTER Table (mobile terminated):

r are m

Add lly, ‘average call duration’ and ‘Fax/Data’ success rates are displayed.

Fo MTC’s the ‘answer’, ‘no answer’ ‘B-busy’ and ‘Call Forwarding’ rate are printed. These four values co bined in ‘MTC success rate’. The rest which is covered with ‘Others’ indicates potential problems.

itiona


MOBILE ORIGINATED TRAFFIC analysis table:

UT_PLMN’, ‘MOC warding MORTR’.

success rates’ might be poor or even zero. LOCATION UPDATE and PAGING table:

For MORTR traffic the calls are split up in ‘MMC to own MS , ‘MMC MO

OUT_NOT_PLMN, ‘NO TCH Allocation BSC’, ‘No TCH request generated’ and ‘Call forC’

MThe rest ‘Others’ are indicating problems. Handover Analysis Table:

Handover success rates are detailed in ‘intra MSC success rate’, ‘inter MSC A success rate’, ‘inter MSC B success rate’, ‘HO not allowed’ and ‘HO fail’. Depending on the geographic coverage of the radio network, the VLR area measured might not have common borders with other VLR's. In this case, the ‘inter MSC


ocation Updates are detailed in ‘Location update success Rate’ and ‘Others’. ‘Others’ canL be interpreted as

For SMS the statistics covers ‘successful SMS Attempts’ and ‘unsuccessful SMS Attempts’ (‘Absent MS’ and ‘Delivery failure’).

location update failures.

HORT MESSAGE SERVICE table:

Paging is split up in ‘successful paging’, ‘paging time out’ and ‘Others’. ‘Others’ covers all cases, which are not contained in ‘successful paging’ and ‘paging timeout’. S

MSC/VLR LOAD ANALYSIS table:


NETAN2000 User Manual V7.0 ICM N MS P 6 44 / 111 NETAN2000 User Manual V7.0 ICM N MS P 6 44 / 111

User Defined table:

This part allows the user to add his own calculation formulas to the GOS evaluation. The values appear each time a GOS result file is loaded. The user can define the name of the parameter and the calculation formula. Up to 20 different parameter can be created in the current NETAN version.

See next page how to create a formula!


How to create a ‘Use


*** USER DEFINED FORMULAS DEFINITION *** // The Label of the User Defined Formula must always start with # GOSX,User1,real,CALL_ATTS_MORTR + CALL_ATTS_MICTR,#All_CA_into_MSC GOSX,User2,real,CALL_ATTS_MONPLMN+CALL_ATTS_MOPLMN+CALL_ATTS_MTER+CALL_ATTS_MTRANS,#All_CA_out_of_MSC GOSX,User3,real,100*(User2/User1),#Call_IN/OUT_Rate GOSX,User4,real,4,#_ GOSX,User5,real,5,#_ GOSX,User6,real,6,#User Defined Label 6 GOSX,User7,real,7,#User Defined Label 7 GOSX,User8,real,8,#User Defined Label 8 GOSX,User9,real,9,#User Defined Label 9 GOSX,User10,real,10,#User Defined Label 10 GOSX,User11,real,11,#User Defined Label 11 GOSX,User12,real,12,#_ GOSX,User13,real,13,#Hi NETAN Users, GOSX,User14,real,14,#_ GOSX,User15,real,15,#Now You GOSX,User16,real,16,#can change GOSX,User17,real,17,#this names and GOSX,User18,real,18,#formulas GOSX,User19,real,19,#as you GOSX,User20,real,20,#like !!!!!!

r Defined Formula’

earch for the following text string: 'USER DEFINED FORMULAS DEFINITION'.

Use the following syntax: GOSX,User1, real,formula definition,# name of the formula

xample: GOSX,User1,real,CALL_ATTS_MORTR + CALL_ATTS_MICTR,#All_CA_into_MSC

ll_CA_into_MSC’ will be desplayed in NETAN!

ttention: The used counter name must match to the name defined in the ‘XXX.cnt’ file (e.g. SR9.CNT in directory ‘Counter Files’) Be careful while changing the 'Definition Files'. Formulas with wrong syntax may lead to program crashes during the evaluation.

To define formulas open the file SR9.STAT (from the ‘Statistic Files’ directory) with a text editor like Notepad. S

ere you will find the definition of the formulas: H //

E ‘A A

IN evaluation table:

This table gives information about the IN successful and unsuccessful events.

ble: Fax and Data evaluation ta

This table shows information about the fax and data attempts and success rates.


Key Figure Table:

his table shows on overview about the T

main KPI’s (Key performance indicators) of the measured MSC.

Also it shows the comparison of the measured KPI’s with predefined benchmark values. These values are derived from the experience and in reality reachable values in a SIEMENS network. The benchmark values can also be changed in case of e.g. different contracted values. Following section in the NETAN2000.ini file defines the benchmark values: GOS Key Figures BM1=95 -> MTC GOS Key Figures BM2=95 -> MO_PLMN GOS Key Figures BM3=95 -> MO_PSTN GOS Key Figures BM4=95 -> LUP GOS Key Figures BM5=95 -> IN MORTR GOS Key Figures BM6=95 -> IN MICTR GOS Key Figures BM7=90 -> PAGING GOS Key Figures BM8=85 -> Handover GOS Key Figures BM9=70 -> CP LOAD


GOS counter page:

he GOS counter page allows a fast and simple overview about all detailed counter values from a GOS

shows all counters out of RECMSC and RECVLR measurement and also all calculated statistical values.

ted with the elected data.

Tevaluation. It The MSC counters are due to the amount arranged in 3 different tables. Select the table you want to check and press ‘Refresh Data’. The counter table will be updas


3.4.1.2 Traffic Model

3.4.1.2.1 Prerequisites The traffic model evaluation requires the RECMSC, RECVLR, RECCP, RECHLR data files. As a result, a set of parameters will be calculated which unequivocally describe the capacity requirements of a network in order to make most efficient use of a network without causing overload or congestion. These parameters are: - Number of VLR subscribers - BHCA total/SUB - BHCA mobile/SUB - Interrogation for MTC/SUB - Interrogation for Transit Calls /SUB - MMC to other MSC /SUB - Internal MMC (MIC)/SUB - TRANSIT-CA/SUB - Handover/SUB

- INTRA-BSS-HO/SUB; BSC controlled - INTRA-MSC-HO/SUB; MSC controlled - MSC-MSC-HO - LUP/SUB with/without HLR Interworking - SMS /SUB for MOC/MTC - Mean Holding Time [sec] - Mean Call Duration [sec] for MOC/MTC - CP load etc....

3.4.1.2.2 Basics The traffic model is crucial to the dimensioning of the measured exchange as well as for the wh network.

ince the hardware/software configuration of each exchange is based on a set of pre-defined T fic Model

e traffic model parameters will change as well and the dimensioning of the exchanges and the

ole rafS

parameters, these parameters have to be permanently monitored. If the call behavior in the network is changing, thtrunks have to be adjusted.


3.4.1.2.3 Evaluation

The traffic model gives a complete set of traffic parameters that are necessary for the appropriate planning f a mobile network. s an additional feature, the result parameters can be saved as text ('save to text' in File Menu). This text rmat can then directly be imported into analysis tools for radio planning.

oAfo


3.4.1.3 Trunk Group Evaluation

3.4.1.3.1 Prerequisites The Trunk Group Evaluation requires only the REC TGRP measurement as input file. The measurement can be started for all trunkgroups (TGRP=X) or only for selected trunkgroups. If there is more than one trunkgroup file from the same NE and Date NETAN2000 will combine the results in one result file.

3.4.1.3.2 Basics Trunkgroup related traffic measurement (REC TGRP) jobs register data for the following positions: • Traffic load and seizure related data (e.g. number of seizures, traffic volume) • Resource and structure related data (e.g. number of lines, number of blocked lines) • Data related to grade of service (number of successful calls). The results of trunk group measurement are the counts recorded by event counters, holding time counters and overload counters. By clicking the header cell of a certain parameter, the TGRP data can be rearranged in descending order. A double click on the header arranges the TGRP data in descending order. The TGRP evaluation program contains all call success relevant data split up for each TGRP. The following table gives an overview over all relevant parameters: Not all of the created trunkgroups might appear in the result file, please refer to chapter 2.9.3, evaluations.


By clicking the header cell of a certain parameter, the TGRP data can be rearranged in ascending order. A double click on the header arranges the TGRP data in descending order. The TGRP evaluation program contains all call success relevant data split up for each TGRP.



ulated with an ERLANG B formula based on the offered Traffic (also a

theoretically calculated value).

he calculation of ‘Required Trunks’ is based on a so-called GOS or Blocking Factor. This factor is per

the corresponding DEF file.

u have to open the file stat_SR9.def in a text editor and search for following line:

,integer,@ErlangBTrunks(1,Offered_Traffic)

The column ‘Required Trunks’ is calc

Tdefault set to 1%. If you want to calculate with a different factor than 1 you can change this in E.g. for SR9 yo

TGRP,Required_Trunks If you like to calculate with a GOS of 0,1% change ‘1’ to ‘0.1’.

3.4.1.3.4 Export to txt function

Statistics Database (TGRP)NE Name: MSC-XDate: 03.04.2008Version: SR9

TGRP_Name DurType Interval StartTime NATC_Outgoing TC_Incoming TC_Total TC_per_TrunkOffered_TraffiRequired_Tru Call_Atts_OutB501(B) Quarterly 00:00-00:15 00:00:00 4.04 0.84 4.89 0.03 4.89 11 57B501(B) Quarterly 00:15-00:30 00:15:00 1.73 1.07 2.8 0.02 2.8 8 44B501(B) Quarterly 00:30-00:45 00:30:00 0.79 0.81 1.6 0.01 1.6 6 33B501(B) Quarterly 00:45-01:00 00:45:00 0.74 0.54 1.28 0.01 1.28 5 36B501(B) Quarterly 01:00-01:15 01:00:00 0.3 0.56 0.86 0.01 0.86 4 16B501(B) Quarterly 01:15-01:30 01:15:00 0.45 0.75 1.2 0.01 1.2 5 16B501(B) Quarterly 01:30-01:45 01:30:00 0.72 0.5 1.23 0.01 1.23 5 17B501(B) Quarterly 01:45-02:00 01:45:00 0.44 0.48 0.91 0.01 0.91 5 12B501(B) Quarterly 02:00-02:15 02:00:00 0.42 0.35 0.77 0 0.77 4 9B501(B) Quarterly 02:15-02:30 02:15:00 0.4 0.38 0.79 0.01 0.79 4 8B501(B) Quarterly 02:30-02:45 02:30:00 0.2 0.67 0.87 0.01 0.87 5 7B501(B) Quarterly 02:45-03:00 02:45:00 0.3 0.42 0.72 0 0.72 4 10B501(B) Quarterly 03:00-03:15 03:00:00 0.1 0.67 0.77 0 0.77 4 9

93 0.01 0.93 5 9B501(B) Quarterly 04:30-04:45 04:30:00 0.15 0.34 0.49 0 0.49 4 9B501(B) Quarterly 04:45-05:00 04:45:00 0.09 0.36 0.46 0 0.46 4 6B501(B) Quarterly 05:00-05:15 05:00:00 0.04 0.44 0.48 0 0.48 4 5B501(B) Quarterly 05:15-05:30 05:15:00 0.6 0.22 0.83 0.01 0.83 4 17B501(B) Quarterly 05:30-05:45 05:30:00 0.62 0.67 1.29 0.01 1.29 5 20

B501(B) Quarterly 03:15-03:30 03:15:00 0.44 0.62 1.06 0.01 1.06 5 5B501(B) Quarterly 03:30-03:45 03:30:00 0.74 0.26 1 0.01 1 5 13B501(B) Quarterly 03:45-04:00 03:45:00 0.56 0.36 0.92 0.01 0.92 5 5B501(B) Quarterly 04:00-04:15 04:00:00 0.16 0.5 0.65 0 0.65 4 4B501(B) Quarterly 04:15-04:30 04:15:00 0.26 0.67 0.

3.4.1.4 Cell Evaluation - INTCRELL

3.4.1.4.1 Prerequisites The CELL Evaluation requires only the REC INTCELL, DTYPE INTCRELL measurement as input file. The

easurement should be started for all cells. m

3.4.1.4.2 Basics Cell related measurements evaluate all important cell quality parameters such as:

- Assignment failure ssible

Lack of air interfaces Interference Installation and commissioning faults HW problems

- Setup Failure:

Possible reasons: Lack of air interfaces Interference Installation and commissioning faults HW problems

- Dropped calls:

Possible reasons: Hardware problems Interference Poor coverage

- Handover failure:

Possible reasons: Poor coverage Interference Lack of air interfaces

This evaluation gives an accurate and comprehensive quality overview over all cells. This is particularly important since the radio part is most critical to the performance of a radio network. According to the above stated parameters, certain reasons for problems can be determined and solutions be worked out. The cell data can also be sorted in ascending or descending order: by clicking the corresponding cell header once, the table will be rearranged in descending order, a double click will sort them in descending order. Changing the value in 'Show Call Attempts' allows filtering out all cells that don't reach the defined value of call attempts.

Po reasons:


3.4.1.4.3 Using the ‘CELL INFO’ feature

ll.

ion has to be stored in a separate .INI file for each MSC and the ithin the NETAN outputs.

E.g. it i- Compa ith cells from other vendors - Compa with ‘1800’ cells

How to creat :

ated for each MSC and this file has to be stored in the directory ‘CELL INFO’ w n directory. The name of t st be exactly like MSCNAME.ini and the MSCNAME must fit to the MSC identifica ecause this is the reference for NETAN to find the information

The ‘CELL INFO’ feature allows the user to add the internal ‘CELL NAME’ as well as up to 20 different categories to each individuell ce This additional informatinformation will apply w

ith the categories it is possible to filter the output in NETAN: W

s possible to: re ‘SIEMENS’ cell wre ‘900’ cells

e the INI file One INI file has to be cre

ithin the NETAN installatiohe INI file mution within the measurement files b.



ILTER]

ategory3=No Diversity

ategory6=DCS 1800

ategory8=Microwave er

Cat oategory12=Ericson BSS

[CELL INFO] 10102-1126=TestName2,Category3,Category1,Category9 10102-1130=Zylinx,Category13,Category15,Category4 10102-1168=TestName8,Category6,Category8,Category15

xample:

Within the [FILTER] section the user can define the possible categories. This section can be copied as it is in each INI file. If you need different categories just change one of the existing or use one of the empty categories. Within the [CELL INFO] section the user can assign the cell name and the category to each cell. The syntax is: LAC-CELL ID=CELL NAME,CATEGRIES 10102-1126=TESTNAME2,CATEGORY3,CATEGORY1,CATEGORY9 Here the cell 10102-1126 has the name ‘TESTNAME2’ and categories 3,1,9 means ‘No Diversity’, ‘OMNI’ and ‘CITY CENTER’.

E [FCategory1=Omni Category2=Sectorized CCategory4=3 TRX or more Category5=GSM 900 CCategory7=Telkom_Link CCategory9=City CentCat oeg ry10=Indoor

eg ry11=Siemens BSS CCategory13=Motorola BSS

ategory14=Nokia BSS CCategory15=SBS Phase1 Category16= Category17= Category18= Category19= Category20=

Now you have the possiblity to filter the table in a way that the table contains only that cells which

ed to e.g. the categrie ‘SBS Phase1’

re ‘2’) and how many are exclude (118).

t in

are assign

In the section ‘Display Info’ you find also the information how many cells are assigned to this categories (he

HINT: The relation between CELL ID and cell name should be already available in your projeca format which you can easily use for the INI file.



tandard’ page‘S

‘Handover’ page


3.4.1.5 Cell Evaluation - HOTRFS

3.4.1.5.1 Prerequisites The CELL Evaluation requires only the REC INTCELL, DTYPE HOTRFS measurement as input file. The measurement should be started for all cells.

3.4.1.5.2 Basics For a detailed analysis of the traffic flow between two radio cells caused by handovers, both cells are measured. The target cell can belong to either the MSC being measured or to another MSC. Only MSC controlled handovers are registered. Therefore, two matrices are built up for every cell (identified by a LACOD and a cell identity CI) of the MSC area. - One matrix consists of origin cells where all outgoing handovers (attempts and successful completions leaving the cell) are measured. - The other matrix consists of target cells where all incoming handovers (attempts and successful completions entering the cell) are measured.



3.4.1.5.4 Prerequisites The CCS7 Evaluation requires the REC C7LLOAD measurement as input file. The measurement should be started for all #7 Links. Additionally a MLOG Display with the result of the command 'DISPC7LINK: LINKNO=X;' is required. From SR4 on the relation between LINKNO and SILTNO can only be found by using the MML command DISPC7LINK:SILTNO = X; the relation is necessary to get the distribution of C7 Links within the CCNC hardware structure. Attention: If new links were added or old links removed the measurement has to be stopped and started again. Otherwise the changes will not appear in the measurement.

3.4.1.5.5 Basics Why CCNC Load Balancing The CCS7 signaling links connect signaling points in a communication network. The signaling points and the signaling links form an independent signaling network that is overlaid over the circuit network. In a D900 entity all CCS7 signaling links are connected to the CCNC. The CCNC handles the message exchange between various nodes for controlling and monitoring connections as well as for operating the signaling network. In a constantly growing GSM-network the load on the signaling links will change permanently.


To account for this changes and due to the design specific construction of the CCNC certain configuration rules must be considered. The load dimensioning should be done on a regular basis, depending on the activity changes in the #7 etwork.

SIEMENS recommends a monthly evaluation if the activities in the network are normal. Balancing and Dimensioning Rules Recommended load values for CCNC Units in Erl.: C7-Link Load should not exceed the value of 0.2 Erl. per link. The total load of a SIPA should not be higher than 1.6 Erl. This value will only be achieved if all four SILTC's are connected and carry an even balanced load. The above given recommendations should be applied in the complete D900 Nr7- network. SILTD: 0.2 Erl. The direction with higher load should be considered (RX or TX) SILTC: 0.4 to 0.8 Erl. Depending on how many SILTC's are connected to a SIPA SIPA: 1.4 to 1.6 Erl. Best SIPA performance is if all 4 SILTC's are connected and allocated with

equal load

n



Example of the printed or ‚saved to bitmap’ file:



For the CCS7 evaluation the traffic measurement and the DISPC7LINK Mlog output of the exchange has to ation result displays the load per SILTD as well as well as per SIPA (sheet

er SIPA'). Additionally, the total load of the CCNC is displayed. he 'per link set' sheet displays the link load according to all links in a C7LSET.

The distribution sheet details the SILT-C load in a bar diagram. This allows one to monitor the load distribution and draw conclusions as to how to balance the load.

be collected. The CCNC evalu'pT

Per Link Set Table:


his table allows checking the current load sharing within all links of the selected linkset.

T

3.4.2 SSNC / GPRS The formulas that are used in SSNC/GPRS evaluation you find in the documents

• MP Load Measurements formulas.doc • SSNC formulas.doc • GPRS formulas GR20.doc

Figure: SSNC Power Node


Figure: Which Measurements and Displays are needed for an SSNC Evaluation.

101 vcpuCurrentData vcpu-load111 mhCurrentData message handler load

CR SIGNEME 202 Net Element meas. # of MSU's per node inc/out/trans/lost;204 SignPointutilization meas # and duration of unavailability of any adjacent SPC206 obligatory SignPoint util. meas duration of unavailability of any adjacent SPC208 Network MSU meas # of MSU's per network inc/out/trans210 SignPoint meas MSU's discarded per link212 Linkset Duration meas # and time of unavailability of a linkset234 Linkset Utilization meas # of MSU's / bytes received/transmitted/discarded

CR SIGDPME 214 Dest point meas # and time of unavailability of a DPC (route set)216 oblSignallingLinkDuration meas availability of a link218 link duration meas duration the link was working/faulty/unavailable

0 oblSignallingLinkUtilization meas received/transmitted/discarded octetts2 allSignallingLinkUtilization meas # of MSU / bytes received/transmitted/discarded

224 signallingLinkCongestionData # and duration of congestion per link226 saalAllSignallingLinkUtilisationData (HS) transmitted/received/discarded SD PDU/octets228 saalOblSignallingLinkUtilisationData transmitted/received octets230 signallingLinkCongestionDataANSI congestion indication232 signallingLinkCongestionDataCombined234 signallingLinkSetUtilisationDataITU received/transmitted octetts/MSU, lost MSU236 signallingLinkSetUtilisationDataANSI received/transmitted octetts/MSU, lost MSU310 sccpErrorPerformance errors in SCCP320 sccpQualityOfService # of msgs received/sent330 sccpUtilization # of msgs handled/GTT /transit/local SS

CR SPMESSN 340 sccpUtilizationPerSsn360 sccpScreeningFailures370 sccpScreeningTrafficMeas

CR SIGLME

SCCP(MP:SLT)

CR SPME(N)

CR SPSME

MP MP:xx CR MPLDME

MTP (MP:SLT)

CR SIGPTME

CR SIGLSME

Figure: Overview of SSNC Measurements.

2222

SS7


Additionally to D900 evaluations you will find the ‚quarterly period’ button for time selection. That means that you are able to select not only an hour (e.g. busy hour) but also any quarter of the day (e.g. busy quarter).

3.4.2.1 MP Load

3.4.2.1.1 Prerequisites CR MPLDME Create MP Load Measurement DISP MP display of the types of MP The MP evaluation needs – besides the measurement file- the DISP MP command file to indicate the type of MP. This is important for a calculation of specific load. MP evaluation The SSNC/SGSN consists of several Main Processors (MP). A main processor can handle several software processes, such as packet processing, protocol handling, performance measurement and OA&M functions. The ‚MP load Evaluation' is based on the measurement CR MPLDME as well as some DISP commands. For calculation of LOAD A (%) we use the following procedure: The actual Load (total – idle - audit) represents sort of ‘LOAD B’. This value we divide by 1.25 to get LOAD A (~700 mErl). These 700 mErl represent 100% LOAD A. Please take this value as an approximate value!


3.4.2.1.2 Evaluation:

Figure: MP Evaluation With the very first Icon (open result file) you are able to load the wanted result files. In this example the MP-Load result file was loaded. Interval (below the title line MP Evaluation): If Busy quarter/hour was selected, then the indicated time is the quarter/hour with the highest load of all MP’s, taken as average. LOAD A % column: The percentage is referring to a base value of 700 mErl (~(1000 mErl – 100 mErl Reserve) /1.25). It should give a first hint when coming to values, where it is necessary to think about extension (extra MP, new SGSN) Type SW/HW: As these values are taken from DISP commands, please verify on the exchange, if HW type is correct. For Example: SM/C means Signalling Manager / MPU : C.


Figure: MP Evaluation, Counters Detailed

Via the icon you can store the contents of MP evaluation as a text file, which is easily loadable into an EXCEL table:

ate:,01-10-11

P Number,Type(SW/HW),Interval,Load A (%),Actual Load, OAM, Total(SLT), …. 15:15,50,349,286,0,0,0,0,0,63,0,0,0

/ C,01:30-01:45,3,22,1,0,0,0,0,0,21,0,0,0 9,MM / C,01:45-02:00,3,24,0,0,0,0,0,0,23,0,1,0

:45-02:00,6,40,0,21,0,19,2,0,19,0,0,0

19,0,0,0 otal,All,15:00-15:15,10,580,288,81,11,57,10,2,210,0,1,0

Example: MP NE Name:,SGSN4 DVersion:,EWSDV13 Interval:,15:00-15:15 (Busy Quarter) M01,SA / C,15:00-02,SM / C,01:30-01:45,3,23,1,0,0,0,0,0,22,0,0,0 04,SLT MTP SGTR 2 / C,01:30-01:45,6,42,0,18,11,0,4,2,24,0,0,0 08,ACC011,PD / C,0112,PD / C,01:45-02:00,6,40,0,21,0,19,2,0,19,0,0,0 13,PD / C,01:45-02:00,6,40,0,21,0,19,2,0,T


All MP counters with all the contents for the whole day:

Figure: MP Evaluation, Counters Detailed

ents Selection on Statistic (formula used) and/or counter cont

Figure: MP Evaluation, Graphical Statistic Checkbox


contents

Unit - load type / HW type

Figure: MP Evaluation, Graphical Statsitc Example

his is an example of using the ‘COPY’ button that uses the clipboard and is quite useful for reports: T

Figure: MP Evaluation, Clipboard


3.4.2.2 MTP/SCCP load

3.4.2.2.1 Prerequisites Please Refer to Chapter 3.4.2 for the Prerequisites for the MTP and SCCP Load Evaluation. NETAN processes the DISP SIGDL and DISP SIGLINK command files. They serve to indicate the relation between linkset name (as the operator knows them) and the internal name (given by the system).

3.4.2.2.2 Evaluation: General remark: SSNC description shows that the SSNC can handle a permanent load of 0.4 mErl. This is internal handling and has nothing to do with the ITU recommendation of 0.2 mErl maximum load. Thus a provider may apply the 0.4 mErl limit internally in his network if the counterpart is a SSNC as well; if the traffic is going out of the network he should restrict to the ITU recommendation (<0.2mErl. load per link).



ment per MP3.4.2.2.3 MTP Measure

nk information HW-oriented (per MP), additionally the total load per P and SSNC.

MTP measurement shows liM

Figure: MTP Measurement Per MP Netan automatically shows the Datalinkname, DataLink ID, Linkset Name, Linkset ID and Link Code in one row. Without Netan you have to correlate the Linkset Name and the Linkset ID manually.

Max load of Receive or transmit side

Links per MP

MP selectable

3.4.2.2.4 MTP Measurement per MP

ary per MP Summ

Figure: MTP Measurement for All MP´s This page is an overview where you can find the load of all MP´s on one page.


3.4.2.2.5 MTP Measurement for Linksets (Detail)

Links per Linkset

Selection possible per Linkset name or network ID-Linkset ID

Figure: MTP Measurement for Linksets (Detail)

verview of all link sets: Linkset shows link information software oriented (per link set).

ain advantage is to have the possibility to check if the loadsharing within one link set works.

O M NETAN2000 User Manual V7.0 ICM N MS P 6 76 / 111

3.4.2.2.6 MTP Measurement for Linksets (Summary)

Overview Linksets

NB means Narrowband, HS means Highspeed

Figure: MTP Measurement for Linksets (Summary)

n this page an overview over all Linksets is shown. O


3.4.2.2.7 MTP Measurement for LICs

• A LIC provides a maximum of 8 E1 interfaces which results in a maximum

of 248 signaling links • A LIC provides the connectivity for 248 signaling links which could each carry a

maximum of 1 Erlang signaling traffic • A LIC can terminate a maximum of 8 HSL, it is possible to have Narrow Band

signaling links and MTP Measurement for LIC´s: Informations how many Links are connected to a LIC, and the Load of the LIC´s.

High Speed signaling links on the same LIC

Figure: MTP Measurement for LIC´s. MTP Measurement for LIC´s: Signalling Mode, Informations how many Links are connected to a LIC, and the Load of the LIC´s.

Overview LIC


3.4.2.2.8 MTP Measurement for High Speed Links (Detail)

Def ti The etwork odes. y powerful SS7 overlay etwork consisting of (fully or partially meshed) standalone signaling transfer points (STP).

ervice control points (SCP) of an intelligent network (IN) to the standalone signaling ansfer points (STP).

ini on:

High-Speed Signaling Links (HSL) feature increases the bandwith between SS7 n High-speed signaling links can, for example, be used to set up a vern

nThe signaling end points (SEP) of the SS7 network are connected to the assigned mated pairs of standalone STPs via conventional signaling links. Hig-Speed Signaling Links can also be used to onnect the sc

tr

Selection possible per Linkset name or network ID-Linkset ID

High Speed Link (Detail)


3.4.2.2.9 MTP Measurement for High Speed Links (Detail)

Links (Summary): All High Speed Links are listed here. High Speed

High Speed Link (Summary)


3.4.2.2.10 SLT Statistics

SLT Statistics is a general overview about links.

Statistics

New in Version 7 are the informations for Highspeed Links.


3.4.2.2.11 MTP Counters

ll MTP counters with all the contents for the whole day:

A

MTP Counters


3.4.2.2.12 SCCP Counters

lobal title translation:

SCCP counters with formulas for STP/SEP function and g

SCCP Counters


3.4.2.2.13 Graph mode:

The following table is the bitmap or printout with the overview of the load of all link sets with all links MP oriented:

1st select linkset 2nd press refresh


3.4.2.3 SGSN

3 .4.2.3.1 Registration:

General. If Interval shows 00:00-00:00 then no MP evaluation was done and we have no calculated busy time. It is then up to the user to select another criteria (e.g. throughput or ?). However this must be done manually (e.g. select graph and select busy time via daily curve). N/A indicates that this value cannot be calculated as there are no counters. If there are separated counters for 2G and 3G, this is shown in the 2 columns. If actions are counted together (in one counter), result is shown in 1 box (column) only. Please observe, that for clear definition in subsequent pages I use following terminology:

• Registered subscribers: subscribers in SLR (above in Total amount) • Attached subscribers: subscribers in ready/standby state or from the mean number

of attached subscribers (should be same) • Active subscribers: Subscribers which have PDP context active


3.4.2.3.2 SMS, CAMEL


3.4.2.3.3 PDP Context

Attention: rejections are not separately counted!


3.4.2.3.4 Throughput (2G only)

hroughput shows LLC frames and SNDCP packets and octets.

Throughput exists only for 2G! 3G throughputs must be counted in SP:GTPU. Please do not use the information ‘Statistics per subscriber per second’ in selected cluster mode: As ‘subscriber (= registered subscriber)’ is SGSN wide based, the throughput however cluster information, the values in this box are only valid if on top ‘cluster = total’ is selected!

T


3.4.2.3.5 Overload

Overload information is MP oriented and not separated for 2G and 3G.


3.4.2.3.6 Routing area update

Routing Area Update (RAU) here is subdivided into

• Cluster change SGSN internal (= from one to another cluster inside this SGSN) • Incoming Change, i. e. a subscriber comes into this SGSN area newly

G only!

2


3.4.2.3.7 Routing area


3.4.2.3.8 Miscellaneous


3.4.2.3.9 Traffic model

Traffic model shows the activities in the system broken down to one subscriber that will serve as ‚typical subscriber’ for planning purposes. a


3.4.2.3.10 Graph routing area related

With Icon 8 (save current page to text) you may copy the data of the lower half into a text file. This may be used for further processing via EXCEL etc.


3.4.2.3.11 Graph cluster related


3.4.2.3.12 Graph MP related


3.4.2.3.13 Graph SGSN related


3.5 Detailed Evaluation / Time Line Charts If you want to see a daily chart for a calculated value or any counter in the measurement, this is the function you need. Also you can put different counters or statistics in relation and observe the behavior over 24 hours. You get also the possibility to look for counters that are not in the predefined formulas. For trouble shooting this is the functionality you always have been looking for. It will become an easy task to look for overload problems or something similar. How does it work?

Click on this button

Save the table to a txt file

Search function for

statistics /counters

Adjustable window sizes for table and graph! Total / average value for

each line!


3.5.1 Store table for post processing

mma separated txt file which can easily be imported.

hoose the counters/statistics you need and press the

If you need to work with the selected figures in other application like MS EXCEL you can save the complete table to a co

C button or select ‘FILE’ – ‘SAVE TO TXT’ –

elect a location and a name for the txt file and press O.K.

xample for a text file imported into MS EXCEL:

‘CURRENT’. S E



.5.2 Enhanced Chart Options

hart Editor’ – or details see chapter 4.2 The ‘Chart Editor’

3 By ‘Right Mouse Click’ within the chart window you can open the ‘C f


3.5.3 Detailed View for the PO part:

With a double-click on any position within the chart window the 'Selection Window' will appear. Here you can add the statistics or counters to the 'Showed Values' window. When finished click on the OK button and the chart will be presented.

Please select counters / formulas based onthe groups

where they belong to:

e.g.: nbr_sub_ready is a counter per RoutiArea; therefore select tabsheet „cluster,Land RA“ and then the counter!

ng A

4 Long Term Statistic Program

Grade Of Service results

ults • CELL (INTCELL) evaluation results • CELL (HOTRFS) evaluation results • MP evaluation results • SSNC evaluation results • GPRS evaluation results

The following part is related the the LTS tool version 4.00 only! The LTS program can be opened within NETAN2000 in the menu 'TOOLS' - 'LAUNCH LTS' or by double-click on LTS.EXE in the NETAN2000 directory.

4.1 LTS Program Overview This tool gives you two possibility:

- Monitoring and evaluation of performance parameters from one exchange over several evaluation dates

- Comparing performance parameters from different exchanges and projects The program reads the measurement parameters for the busy hour or a preselected interval of each day into a long-term textoriented database and displays the parameters in a table or chart format. Following NETAN result files can be used with the LTS program:

It is possible to add multiple result file in one step. When adding a result file you will be asked for a project name. This allows keeping the results of different projects in one LTS file.

•• Traffic Model results • CCNC evaluation results • TGRP evaluation res



4.2 Import of data into LTS

here are two ways to add data into the LTS database.

.2.1 Adding GOS, TM, TGRP, CCNC, CELL, HOTRFS and GPRS data into LTS

he ‘Hour to e parameter values

his is impo e same time interval!

In the ‘Add to Result file’ dialog you can enter a project name and select the files you want to add to the LTS database.

T

4 To add this data to the LTS you can use the ‘Data’ – ‘Add from Result file’ command or simply push the econd button s

T Use’ drop down box allows to select the interval from which th

rtant if you want to see the parameters from different MSC at thshould be imported. T

4.2. Adding MP and SS2 NC data into LTS

o add this kind of data to the LTS you have to open the result file first with NETAN and then use

In the following window you can select the result directory and after ‘OK’ a file will be stored with the name ‘MSCdateMP.ltsn’ or ‘MSCdataSSNC.ltsn’ This files can be imported into the LTS database in the same way like the other result files.

Tthe option ‘Tools’ – ‘LTS’ – ‘Create LTS Statistic Output’


4.3 Working with the LTS tables

A double left mouse click into the right window opens a window where you can select the values which should be shown in the table.


4.3. ‘Save to TXT’ function 1

ith the ‘Save to TXT’ function which you start with the button

W saves the complete active table as a txt file. This file can easily imported into MS EXCEL:

4.3.2 ‘Filter’ function With the ‘Filter’ function the table can be filtered with various criterias.

You can set filter for:

- Project Name - MSC (NE) Name - Date (with Start and End Date) - APS Version - TGRP Name

ou can also choose if you want to filter all tables or only the active one.

Y


4.3.3 ‘Sort’ function The ‘Sort’ function allows to sort the table on various criterias.

The possible criterias are:

- Project Name - MSC Name - Measurement Date - APS Version - TGRP Name

4.3.4 Miscalenious features

he complete LTS database can be saved as .lts file. is possible to import the complete .lts file into MS EXCEL

The to add another LTS file to an already open one with the

TIt

re is also a possibility button.


4.3.5 ‘Timeline’ mode

T

he Timeline mode can be activated with the button.

For the network element that is selected in the table on the right side graphs can be shown. This works only if for the chosen network element data from more than one date is available. By double click in the graph a new window appears there the user can select the rates to be shown.

- A double left click opens the ‘Choose counters / Statistics to be shown’ window there you can select what graph should be displayed.

- A double right click opens the ‘Editing Chart’ window (for detailed info about the ‘Chart editor functionality’ please read the chapter 3.3.

Copies the graph to the clipboard


5 Appendix

5.1 BUTTON Bar

1 2 3 4 5 6 7 8 9 10 11 12 13 14 Functionality of the buttons:

1. ‘Open Result File’ opens NETAN result files (.res files) 2. ‘View Result File’ opens files created with the ‘TRANSLATE ALL’ function (.resh files) 3. ‘Start Evaluation’ opens the ‘Availability Check’ window 4. ‘Show Summary Evaluation’ shows the evaluation tables 5. ‘Show Detail Evaluation’ opens graphic display 6. ‘Print Current Page’ prints current page 7. ‘Save Current Page to Bitmap’ stores information on ‘~.bmp’ file 8. ‘Save Current Page to Text’ stores the data of graphic display in a text file 9. ‘Copy to Clipboard’ copies current page to clipboard 10. ‘View Options’ to control printer output, chart setting 11. ‘Setup Printer’ to select printer 12. ‘Delete Database Files’ deletes temporary data files 13. ‘Information’ Shows the ‘NETAN ABOUT’ box

14. Arrow buttons Change the Windows size


5.2 Summary Menu Bar

Open Result File… To open the evaluated file(s)

View Result File… See chapter 2.8.1: to look at any translated file Close Close one result file Close All Close all result files Print To print the actual open information to be seen on the screen Save to Bitmap To store the actual open information to be seen on the screen

S or GPRS) ~ current - stores in graphic mode the actual data in text file ~ counter DB - stores in graphic mode ALL counter contents in text file

DB - stores in graphic mode ALL statistic values in text file Exit Close the NETAN2000 program

Eva t S Too

P the printing format, e.g. distance to the margin Evaluation: to restrict trunk group evaluation

rd S Remove Licence Cancel the licence Win Tile Vertically

S e arranged in horizontal, vertical or cascaded level.

Hel

Contents Not used About Information about the tool Netan2000

File

Save to Text To store all evaluations of this type (e.g. GO ~ statistic

lua ion

Start Evaluation election of input and output directory

ls Options rint: to adjust

Copy to ClipboaClear DB Cancel existing temporary files View Database Launch LTS tart the LTS program

dow

Tile Horizontally everal evaluation sheets will b

Cascade

p



5.3 Restrictions

1. Please do not keep the ‘old’ file types MT.xxxx, TS.xxxx with the new file types PM.xxx together in the same directory for evaluation.

2. The or ev haracters for evaluation.

3. For S nd GPRS evaluati y shall be the same as the source directory.

4. spf f mes should begin w"PM _SCAN ", "PM bvccnt", "M

5. SGSN files m pf otherw

6. If MP uation is missing, G

files must not be in UNICODE.

path- and file name f aluation must not exceed 50 c

SNC a on the result director

iles na ith "TS_MPLOAD", "TS_MTP", "TS_SCCP", "MT_GPRS", _SCANREP", "PM REPQOS", "PM_QOS", "MT_GPRS36140", "MT_MCP", "MT_MIB2_36140", "MT_ T_nsecnt", "MT_nsvccnt".

ust end with .s ise the files will not be combined.

eval PRS/UMTS has no busy quarter/hour

7. DISP

netan 2000 version 7 user manual

Education

subdirectory counter

subdirectory definition

subdirectory statistic

subdirectory evaluati

subdirectory counter

traffic measurement

subdirectory cell info

raw file conversion