You are on page 1of 78

Performance measurements management

Siemens

Performance measurements management

Contents
1 1.1 1.2 1.3 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 3 3.1 3.2 3.3 4 4.1 4.2 4.3 5 5.1 5.2 5.3 6 7 Background Introduction Performance Measurement Categories and Parameters Common Parameters for Scanner Objects Performance Measurement Management Creation of PLMN Scanners Setting, Locking/Unlocking, and Deleting Scanners Automatic Adaptation of PLMN Scanners Retrieving Scanner Results Current Performance Measurement Data Handling of Measurement Groups Symbolic Names for Scanners File Conversion to ASCII & XML Format SCA Handling Creation of an SCA Object Uploading the SCA Results Elaboration of SCA Data RFLOOP Handling Creation of an RFLOOP Object Uploading the RFLOOP Results Conversion of the RFLOOP Data History on Dropped Calls Basics Implementation Handling on Radio Commander Exercise Solution 3 4 5 6 9 10 12 16 18 22 24 28 31 35 36 38 40 43 46 48 50 53 54 54 57 65 69

MN1783EU11MN_0001
© 2003 Siemens AG

1

Siemens

Performance measurements management

2

MN1783EU11MN_0001
© 2003 Siemens AG

Performance measurements management

Siemens

1

Background

Fig. 1

MN1783EU11MN_0001
© 2003 Siemens AG

3

For example performance measurements give hints about the load in radio cells. about bottlenecks in the system. Information is collected about many aspects of the network.Siemens Performance measurements management 1.1 Introduction Performance measurements or scanners are an essential tool to survey a PLMN and gather information about its quality. which are not detected by the fault management. so that after a detailed analysis of the measurement results an optimization and fine-tuning of the network parameters is possible. about handover performance etc. 4 MN1783EU11MN_0001 © 2003 Siemens AG . The performance measurement results enable the operator to identify failures and problem zones within the network.

Performance measurements management Siemens 1. which are not described in this document! MN1783EU11MN_0001 © 2003 Siemens AG 5 . e. to UMTS (FDD) or TD-SCDMA (TDD) Measurements related to flexible Abis interface Measurements related to GPRS service Measurements for supervision of RF link Measurements related to Smart Carrier Allocation TIP The scanner objects with the ending TD refer to TD-SCDMA network element. GERAN Network measurement category SCANBSC SCANSS7L SCANBTSM SCANBTSE SCANBTS SCANTRX SCANCTRX SCANCHAN SCANBTSIHO SCANBTSOHOI SCANBTSOHON SCANBTSOHOS SCANFBTSM SCANGPRS RFLOOP SCA Meaning Measurements related to the BSC Measurements related to CCSS7 signaling Measurements related to a BTS Site Manager Measurements related to a BTSE Measurements related to a cell Measurements related to transceivers Correlated TRX measurements Measurements related to the air interface Measurements related to incoming handovers Measurements related to outgoing handovers intra-BSC Measurements related to outgoing handovers inter-BSC Measurements related to outgoing handovers intersystem.2 Performance Measurement Categories and Parameters The performance measurements can be grouped into the categories shown below.g. For each of these categories. one ore more measurements exist.

15. weekly or all the time. Attribute Granularity Meaning The granularity defines the duration of a measurement and the time interval between subsequent measurement reports. cells. The most important common parameters are shown below. Measurement list Object list Recording interval Start and stop date 6 MN1783EU11MN_0001 © 2003 Siemens AG . 30 and 60 minutes.3 Common Parameters for Scanner Objects Performance measurements of one category are defined with a set of parameters. A measurement works on an object.Siemens Performance measurements management 1. With this attribute the measurement can be scheduled to run daily. which can be chosen here. Possible values are 5. If it is scheduled. e. The object(s) can be defined here. In a measurement category several separate measurements are contained. The parameters from one category may differ to the one from another category.g. Dates for begin and end of a measurement campaign can be defined. up to 7 measurement periods can be entered.

2 MN1783EU11MN_0001 © 2003 Siemens AG 7 .Performance measurements management Siemens Fig.

Siemens Performance measurements management 8 MN1783EU11MN_0001 © 2003 Siemens AG .

Performance measurements management Siemens 2 Performance Measurement Management MN1783EU11MN_0001 © 2003 Siemens AG 9 .

3 10 MN1783EU11MN_0001 © 2003 Siemens AG . Fig. If the user has entered an inadmissible value.1 Creation of PLMN Scanners Performance measurements are created from the BSS Summary panel with the command create <SCAN_OBJ>. When a scanner is created. the parameters required have to be filled. the RC performs scanner checks on the specified attribute values.g. he is informed immediately.Siemens Performance measurements management 2. correct combination of measurement types and observed objects) • restriction checks (e. Upon entering this command. specification of measurement types which are not allowed to report by event). Some examples of the implemented checks are: • value range checks • consistency checks (e.g.

Performance measurements management Siemens Fig. 4 MN1783EU11MN_0001 © 2003 Siemens AG 11 .

the scanner objects have to be selected and the corresponding action must be chosen: Fig. Therefore the scanner summary has to be opened.Siemens Performance measurements management 2.2 Setting. locked or unlocked as well as deleted. Locking/Unlocking. 5 12 MN1783EU11MN_0001 © 2003 Siemens AG . and Deleting Scanners Scanner objects can be set.

Performance measurements management Siemens Fig. 7 MN1783EU11MN_0001 © 2003 Siemens AG 13 . 6 Fig.

or if measurements should be added to the measurement list. 8 14 MN1783EU11MN_0001 © 2003 Siemens AG . this can be performed by the add command: Fig.Siemens Performance measurements management If objects have to be added to the objects list.

10 MN1783EU11MN_0001 © 2003 Siemens AG 15 . 9 Fig.Performance measurements management Siemens Fig.

g. This will lead to a short outage time of the scanner and unreliable measurement results in that time interval. etc. addition of TRX. the scanners that are observing the performance of these PLMN objects must be adapted too. Therefore another possibility is offered by the system: In case that all existing objects of one category are objects of a scanner. the following situations happens: • in case of object creation. if the manual procedure is not executed. the new object is not included in the measurements. the objects. that are observed. • in case of object deletion. the setting self adapting in the objects list will enable the scanner to react to configuration changes in order to always include all existing objects without any further user intervention. the counters related to the deleted object (even if equal to 0) are always reported with “suspect flag” set to TRUE.). and unlocked after the command. the scanner has to be locked before the set command. To set the properties of a scanner. e. 16 MN1783EU11MN_0001 © 2003 Siemens AG .Siemens Performance measurements management 2.3 Automatic Adaptation of PLMN Scanners As networks continuously change (addition and reconfiguration of sites. Otherwise.

Performance measurements management Siemens Fig. 11 MN1783EU11MN_0001 © 2003 Siemens AG 17 .

<StartingDateTime>. the file SCAN_xx.TMP file. • Automatic upload.ZIP in the BSC DBFH_ZIP directory (the LOG file is deleted after successful compression). is renamed and saved as SCAN_xx. To make the identification of the cells easier. The compressed file can now be uploaded from BSC to OMP.LOG ready to be transferred from BSC to OMP is compressed to a file SCAN_xx. LOG. The interface to the O&M Toolset has changed due to this redesign. The raw measurement data are kept. Its structure remains unchanged. that is in a BSC directory named MEASURE_DIR. Then data storing continues in a new SCAN. 18 MN1783EU11MN_0001 © 2003 Siemens AG .every 15 minutes until the deletion of the files. the file used for temporary storage). Just before its uploading. The presence of files in the directory DBFH_ZIP is notified to the RC. The binary file is transferred from the BSC to the RC through a compressed format (it is however possible also that the binary file is in uncompressed format).. relieving its CPU to a large extent without reducing the operator’s comfort. The trigger to upload a measurement data file from the BSC can be: • Manual upload. BTSM and TGTBTS Symbolic Names. SPOTS).e. A header containing a list of the symbolic names of the BSC. The PM-data files are uploaded and the temporary files reside in the directory $DATADIR_ON_OMP/ OMP/PMG/binaryPmg/ and are named as <SwVersion>_<BssId>. When the compressed file is successfully uploaded. containing the current BSC. To save upload time.LOG file. by METRICA. BTS and TGTBTS is added to the file. the compressed file is deleted from the BSC hard disk. <EndingDateTime>.g. for a specific time period. during the data post-processing phase (e. • Periodic upload.4 Retrieving Scanner Results Performance measurement data in binary format (as they are gathered by file on the BSC) are uploaded and parked by RC on OMP disk.Siemens Performance measurements management 2.LOG in the BSC READY_MEAS directory. depending on the number and type of the measurements. the buffer size. The measurement data binary format is a BSC-RC internal format and it can be modified in each BSS release. under an appropriate directory. The PM data are no longer inserted in the Radio Commander’s relational database as in previous releases. the number and length of the measurement counters and so on. a section.TMP file (i. the SCAN. where xx is the progressive creation number of the . BTS. is inserted by the RC in each raw measurement file.

which is found at the measurements summary icon in the BSS summary panel.4. 12 MN1783EU11MN_0001 © 2003 Siemens AG 19 . Fig.Performance measurements management Siemens 2.1 Manual uploading of performance measurement results The manual upload is triggered with the command UploadMeasFile.

2 Periodic uploading of performance measurement results The periodic upload can be performed by setting the values MeasurementDataFileUploadStart and MeasurementDataFileUploadPeriod in the BSC basic settings 2.4.3 Automatic uploading of performance measurement results An upload can also be triggered if the file size reaches a predefined threshold (value maxScannerLogFileSize) which can be set in the BSC basic settings.4. 20 MN1783EU11MN_0001 © 2003 Siemens AG .Siemens Performance measurements management 2.

Performance measurements management Siemens Fig. 13 Fig. 14 MN1783EU11MN_0001 © 2003 Siemens AG 21 .

as RC-BSC channel overloading. Each of these will contain an identifier that refers to the command that triggered the event reporting.SCANSS7L SCANTRX Behavior of these commands • Only one command can be started on one monitored object at a time with a delay defined by the BSC.SCANBTSOHOI • getIHOCurrentMeasurementValues for SCANBTSIHO SCANBTSOHON .5 Current Performance Measurement Data To get current performance measurement data for scanners belonging to BSC use one of the following commands: • getCurrentMeasValues for SCANBSC • getMonObjCurrentMeasValues for SCANBTS .Siemens Performance measurements management 2. • The RC translates the scanner information into a plain text format. to avoid performance degradation on both sides as well 22 MN1783EU11MN_0001 © 2003 Siemens AG .SCANGPRS . The parsing • BSC can reply. • The measurement information is reported in one or more events.SCANFBTSM . algorithm is the same as used for performance measurement binary files.SCANBTSOHOS . • The reported scan report buffer is the same as used for the performance measurement binary files. if needed.

16 MN1783EU11MN_0001 © 2003 Siemens AG 23 .Performance measurements management Siemens Fig. 15 Fig.

3. • <OBJ>Measures: Specifies a set of measurements of the same scanner object.9 for every scanner object). slashes ('/'). Enter the values for the following parameters.6 Handling of Measurement Groups The RC allows the user to create self-defined measurement groups containing one or more measurement types of the same Scanner Object. Æ The Create MEAS_GRP_<OBJ> dialog opens. Creation of a Measurement Group: 1. Click OK to save your settings. 2. • measGroupName: Specifies the name of the group (from 1 to a maximum of 25 4. Open the RC Sum panel.Siemens Performance measurements management 2. Do not use the following characters: blanks (' '). For the following twelve Scanner Objects it is possible to create measurement groups: • SCANBSC • SCANBTS • SCANBTSE • SCANBTSIHO • SCANBTSM • SCANBTSOHOI • SCANBTSOHON • SCANBTSOHOS • SCANFBTSM • SCANSS7L • SCANGPRS • SCANTRX. characters). asterisks ('*') and question marks ('?'). At least one measurement must be selected. 24 MN1783EU11MN_0001 © 2003 Siemens AG . Right-click the RC icon and select Configuration Management > create > Create MEAS_GRP_<OBJ>. • Naming Attribute: Specifies the instance number that identifies the measurement group (0..

18 MN1783EU11MN_0001 © 2003 Siemens AG 25 . 17 Fig.Performance measurements management Siemens Fig.

The groups are available on a per OMP basis.e. another user on another OMT may use this group independently of the BSS in which the measurement job runs. 26 MN1783EU11MN_0001 © 2003 Siemens AG . Furthermore. The measurement group defined is then saved on the OMP.Siemens Performance measurements management After a measurement group creation. set and get command are provided for measurement groups. it is possible to specify the group name instead of selecting each measurement one by one. This possibility is given selecting the measList parameter in the measureListattribute from the Create ScannerObject window. i. when the user creates a new scanner related to this type of measurement. a delete.

19 Fig. 20 MN1783EU11MN_0001 © 2003 Siemens AG 27 .Performance measurements management Siemens Fig.

The symbolic names will be used instead of the complete path information in commands. logs and exported data. a command is available to set the symbolic name of this scanner. scanners can be addressed by symbolic names instead of using their fully distinguished name (FDN). This requires that the usage of symbolic names is enabled generally for the BSS.7 Symbolic Names for Scanners To increase the comfort of the RC user interface. 28 MN1783EU11MN_0001 © 2003 Siemens AG .Siemens Performance measurements management 2. after selecting a scanner. In the scanner summary.

Performance measurements management Siemens Fig. 21 Fig. 22 MN1783EU11MN_0001 © 2003 Siemens AG 29 .

Siemens Performance measurements management 30 MN1783EU11MN_0001 © 2003 Siemens AG .

1 3134 77 393% 160% original 799 (uncompressed) original (compressed) 48 Note: The “schema based XML format” has been preferred to the “DTD based XML format” in close harmony with other Siemens O&M systems. MN1783EU11MN_0001 © 2003 Siemens AG 31 . • XML data can be transformed to other data-formats using XSL-stylesheets.8 File Conversion to ASCII & XML Format While the translation of the binary files into the ASCII format is still supported for BR 8. An exemplary file size comparison is given below: Filesizes in kByte BSC RC 820 48 103% 100% XML Schema 2907 75 364% 156% ASN.1 format) has been chosen due to the following reasons: • XML is better readable than ASN.0.or CSS (cascading style sheet)stylesheet the XML-format can be displayed very convenient in an operator definable way using a standard Internet browser.1. The standard compliant XML-format (in contrast to the ASN. • Using an XSL (extensible stylesheet language).Performance measurements management Siemens 2. it is strongly recommended that operators migrate their PM-data handling to the XML-files as supported interface to PM-tools.

Siemens Performance measurements management The configuration of the conversion of binary PM-data files to files in XML-format is done in a panel that can be opened from the icon “Meas File Admin”. Which filename shall be used for the exported file (using relative or absolute filenames)? Each binary file stored in directory “$DATADIR_ON_OMP/OMP/PMG/binaryPmg/“ is translated into one file in XML-format. specified by the environment variable MEAS_PERM_TIME_XML). After this time the files are automatically deleted from the disk without giving any additional information to the user. Operators can choose the following options: • For which BSC shall the file conversion be done? • Which identifiers for the managed objects are used in the xml-files: symbolic names. 1-15 days configurable during SW installation. 32 MN1783EU11MN_0001 © 2003 Siemens AG . The XML-Files are stored in the directory “$DATADIR_ON_OMP/OMP/PMG/xmlPmg/“ using the 3GPP standard compliant filename “<Type><Startdate>. defining an XML-processing statement that is added into the header of the XML-file (<?xml-stylesheet type="text/xsl" href=". CGID or distinguished names? • Shall a reference to a stylesheet (CSS or XSL) be added to all XML-Files.<Starttime>-<Enddate>. An analogous solution is already implemented for binary files./MeasDataCollection. The XML measurement files are kept for a user definable time (default 10 days.xsl" ?>).<Endtime>_<BSSId>”.

Performance measurements management Siemens Fig. 24 Set Meas Conv Mode parameters MN1783EU11MN_0001 © 2003 Siemens AG 33 . 23 Set Meas XML Conv mode command Fig.

Siemens Performance measurements management 34 MN1783EU11MN_0001 © 2003 Siemens AG .

Performance measurements management Siemens 3 SCA Handling MN1783EU11MN_0001 © 2003 Siemens AG 35 .

• Definition of the list of frequencies to put under observation. • Extended Idle Channels Measurements (only on uplink). Configuration is done at the RC by appropriate set-up of SCA parameters. the Extended Idle Channel Measurements subwindow contains the information about SCA Extended Measurements. Each type of measurement must be treated separately from the others. and the Normal Measurements subwindow contains information about both the SCA Normal Measurement kinds.m. • Definition of accumulation times up to four in a day between 6 o’clock a. • Selection of type of measurements Normal measurements on downlink data (NM_DL). on demand: Busy Cumulative Measurements. 3. that allow the user to really know the interference situation of the network: • Normal Measurements. Moreover. The Smart Carrier Allocation feature comprises three different kinds of measurements. they can be elaborated by the RC after their upload from BSC. or to put in service a carrier that has been foreseen as hardware but it has not had frequency planning done. Busy Cumulative Measurement data (BCM) Extended Idle Channel measurements data (E-ICM) • Eventually change the ”adjacent relationships” 36 MN1783EU11MN_0001 © 2003 Siemens AG . or to change an existing frequency much disturbed by surrounding frequencies. which are split in two different kinds of measurements: by default: Normal Measurements.m. up to 12 o’clock p.1 Creation of an SCA Object When creating a SCA object a window is displayed to the user in which there are three subwindows: the Basics subwindow contains general information about the SCA object.Siemens Performance measurements management The SCA feature consists of providing histograms of measurements on frequency basis and elaborating them to determine in a ranked list of frequencies the best one to substitute an under-test frequency for a microcell. In each of these sub windows the user must specify some parameters. The following parameters have to be defined: • Selection of cells under observation.

Fig. 25 MN1783EU11MN_0001 © 2003 Siemens AG 37 . unlock and delete are available. lock. set.Performance measurements management Siemens SCA is set on a per cell basis and can be disabled by default after a system startup. For an already created SCA object the commands get. SCA can be activated for up to 2000 cells per Radio Commander. It is possible to put up to 250 cells per BSC under observation.

Once the SCA file is completely decompressed. The uploaded file is saved in the directory $DATADIR_ON_OMP/SBS_i/PMG. SCA binary files are automatically uploaded between 3:00 a. outputs of elaborations.LOG.m. In this directory many directories naming with the BSS identifier number are created.2 Uploading the SCA Results When the feature is activated the measurements begin to be stored. under the directory $DATADIR_ON_OMP/OMP/SCA. They can also be uploaded on user request. a directory for each day is created and named with the date it refers to. Three different places are used to store data: • into the BTSs: rough data • into BSC: rough data. the interference matrix . the best frequency or the best ones.m.e. statistics. The path is then the following: $DATADIR_ON_OMP/OMP/SCA/date/xx where: date: directory named with the upload date xx (hex): BSS identifier number The decompressed uploaded file is transferred in the right directory of the OMP disk in its original binary format and named as SCAyyzz_CGI. the compressed file is deleted. where: yy (hex): BTSM identifier number zz (hex): BTS identifier number CGI: Cell Global Identifier The retention period of the SCA binary files is 30 days.Siemens Performance measurements management 3. After this time. from the BSC to the RC. 38 MN1783EU11MN_0001 © 2003 Siemens AG . i. the directories and all the included files are automatically removed from the OMP disk without giving any additional information to the user. Simultaneously. The Radio Commander then decompresses the file. . frequencies lists (and BSICs only for Normal Measurement) • into the RC: rough data.6:00 a. where the $DATADIR_ON_OMP is an environmental variable set on OMP.

27 MN1783EU11MN_0001 © 2003 Siemens AG 39 . 26 Fig.Performance measurements management Siemens Fig.

the cumulative histogram is the enlarged one with all the frequencies. time range of data collection and thresholds used to filter input data. • ranked frequencies lists. The first step of the elaboration is to create cumulative histograms. starting from histograms collected from more than a day of observation for each cell. rough data are kept for at least 1 week. partial cumulative data is created. For each type of input a cumulative histogram is created. the final cumulative data are available. Before erasing them. In case of monthly observation. The allowed elaborations on SCA measurements are the following: • average • bad adjacent cells • best frequency • coverage probability • interference matrix • Nth percentile • outage rate • quality link 40 MN1783EU11MN_0001 © 2003 Siemens AG . The user can indicate which data have to be used in the procedures giving input type.3 Elaboration of SCA Data The elaboration activity consists in the generation of: • statistics.Siemens Performance measurements management 3. At the end of the whole observation period. If the observation period is limited at just one day. If the list of frequencies inside a cell has been changed. • interference matrixes. no cumulative histograms are required and the original data are elaborated.

28 Fig. 29 MN1783EU11MN_0001 © 2003 Siemens AG 41 .Performance measurements management Siemens Fig.

Siemens Performance measurements management 42 MN1783EU11MN_0001 © 2003 Siemens AG .

Performance measurements management Siemens 4 RFLOOP Handling MN1783EU11MN_0001 © 2003 Siemens AG 43 .

This information allows a further fault localization 44 MN1783EU11MN_0001 © 2003 Siemens AG . reduced RF power). an alarm is sent for the carrier concerned. For the RFLOOP measurements four of these measurements are of interest: • power generated by the BTS transmitter on the channel’s downlink. A first evaluation of the measurement results is performed in the BTSE. A difference between the two indicates a problem. which is documented in a periodically sent measurement report Using these measurements the path loss on the downlink as well as the path loss on the uplink can be calculated.Siemens Performance measurements management The RF Loopback feature provides a complete test and diagnosis at TRX/carrier level in order to detect both not working TRX and minor service degradations (e. The alarm message indicates that the RF-TX/RX signal path of the concerned carrier shows a service degradation. If the average difference exceeds an operator defined threshold. the related combiner equipment and the averaged path loss difference.g. They are then sent from the BTSE to the RC through BSC. This is achieved by utilizing standard measurements: Whilst a call is in progress the BTSE gathers a series of call related standard measurements that are used for handover decisions and power control. The alarm message contains the TRX. • power generated by the MS transmitter on the channel’s uplink • received signal strength detected by the BTS receiver on the channel’s uplink • signal strength detected by the MS receiver on the channel’s downlink.

30 MN1783EU11MN_0001 © 2003 Siemens AG 45 .Performance measurements management Siemens TxPwr (BTS) RxLev (BTS) RxLev (MS) TxPwr (MS) BTSE Fig.

1 Creation of an RFLOOP Object When creating the RF Loop object.Siemens Performance measurements management 4. This attribute specifies the bandwidth of hysteresis expressed in db unit. 46 MN1783EU11MN_0001 © 2003 Siemens AG . This attribute specifies the minimum required measurement samples count. This attribute specifies the minimum number of calls. a window is displayed in which the user must specify the following parameters: Parameter alarmThreshold autoReport bandWidthOfHysteresis measCount minCallCount rxLevel Meaning This attribute specifies the alarm threshold expressed in db unit. This attribute specifies the minimum RXLEV value to take a connection into account. This flag enables/disables the automatic file upload.

31 MN1783EU11MN_0001 © 2003 Siemens AG 47 .Performance measurements management Siemens Fig.

48 MN1783EU11MN_0001 © 2003 Siemens AG . The retention period of an RF Loopback . To manually upload RFL measurement data files stored in the BSC: 1. Right-click the RF Loop icon and select Performance Management > uploadRFLFile . After this time the file is automatically deleted from the disk without giving any additional information to the user. the decompressed uploaded file is transferred under the directory $DATADIR_ON_OMP/OMP/PMG/binaryRfl in its original binary format and named as BSS<nn>-Rel-<RFxxyy>. Once the RFLOOP file is completely decompressed. Simultaneously.LOG. the compressed file is deleted from the $DATADIR_ON_OMP/SBS_i/PMG directory.23) Only the last uploaded file for every cell is maintained. the uploaded compressed files are saved in an RC directory named: $DATADIR_ON_OMP/SBS_i/PMG where the SBS_i is the subdirectory for the i-th SBS and $DATADIR_ON_OMP is an environment variable set on OMP. Open the BTS Sum panel.Siemens Performance measurements management 4. The Radio Commander then activates the task that provides file decompression. The command for the manual upload is uploadRFLFile. As happens for scanners and SCA files. Open a text editor to browse the file.199) yy: BTS identifier (0.2 Uploading the RFLOOP Results In the current implementation of the Online RF Loopback feature. One file for every cell put under observation by the user is automatically uploaded every 24 hours or manually uploaded on user command at any moment. Æ If the file is successfully uploaded from the BSC to the RC it is stored in the default path: $DATADIR ON OMP/OMP/RFL/binaryRFL/SBS/<data> 3.. 2. where: nn: BSS identifier number Rel: BR release xx: BTSM identifier (0..LOG file is chosen during the installation phase and its value has the range 1-15 days (default value: 10 days). both the automatic upload and the manual upload are supported.

Performance measurements management Siemens Fig. 32 MN1783EU11MN_0001 © 2003 Siemens AG 49 .

Click OK.LOG file to be converted in ASCII format. 5. Open the RC Sum panel.199) yy: BTS identifier (0.ASCII file is chosen during the installation phase and its value has the range 1-15 days (default value: 10 days). Right-click the Meas File Admin icon and select Performance Management > convertRFL. After this command has been launched a window is displayed in which the user must specify the name of the . 50 MN1783EU11MN_0001 © 2003 Siemens AG . which is the total conversion of related binary file uploaded from BSC on RC. However. 4..Siemens Performance measurements management 4. After this time the file is automatically deleted from the disk without giving any additional information to the user. save: Specifies whether the file is automatically saved (True) or not (False). Enter the name directly or open the File Browser dialog and select the file from the Files field.. The retention period of an RF Loopback . If the user then clicks the OK button. TIP By default.3 Conversion of the RFLOOP Data The parsing and conversion of the binary RF Loopback files into ASCII format must be initiated manually via the user convertRFLFile command.ASCII. Æ The Text Editor opens displaying the ASCII file. Æ The convertRFL MEASFILE_ADMIN dialog opens. 2. To convert and save an RFL measurement data file: 1. 3. This means that the converted ASCII file will be deleted when closing the Text Editor window. You may browse the file and search for keywords. select save as from the File menu. if you want to save the data. save is set to False (step 3).23) RC generates one RF Loopback ASCII file. the file is saved under the directory $DATADIR_ON_OMP/OMP/PMG/asciiRfl and named as BSS<nn>-Rel<RFxxyy>. Enter the value for the following parameter: fileName: Name of the binary file to convert. where: nn: BSS number Rel: BR release xx: BTSM identifier (0.

34 MN1783EU11MN_0001 © 2003 Siemens AG 51 . 33 Fig.Performance measurements management Siemens Fig.

Siemens Performance measurements management 52 MN1783EU11MN_0001 © 2003 Siemens AG .

Performance measurements management Siemens 5 History on Dropped Calls MN1783EU11MN_0001 © 2003 Siemens AG 53 .

• the receive quality in the uplink and downlink. the number of dropped calls per channel type and so on. for example the number of dropped calls per timing advance. • the power values of uplink and downlink power control (of MS and BTS). The history data on a dropped call means the following data are recorded and stored by the BTSE: • the receive levels in the uplink and downlink. but only the data for dropped calls are sent to BSC. • the receive level of neighboring cells before the call drop. 54 MN1783EU11MN_0001 © 2003 Siemens AG . Location update procedures on SDCCH. This feature is required for the operator to do operator specific dropped call statistics.2 Implementation The drops are observed for TCH and SDCCH channels. ASSIGNMENT failure • the last monitored HO CONDITION INDICATION cause • the last monitored HO. it is very important and necessary to provide the system operator more detailed data for each dropped call. In order to do this. ASSIGNMENT COMMAND. so the term “call” is used here for calls on TCH channels as well as for SMS. This makes it possible to easily find out the reasons and locations of the dropped calls. the following functionality is supported: • The operator at the RC activates/stops/modifies the measurement ‘history data on the dropped calls’.1 Basics A main aspect of network optimization is to reduce the number of call drops in the network. 5. HO-failure. the number of dropped calls per TRX. In order to do this. • the timing advance.Siemens Performance measurements management 5. • flags indicating the occurrence of HO-COMMAND. • The BTS collects and records the history data for all calls. It is very important for Radio Network Optimisation and Self-Optimizing Network SON.or ASSIGNMENT COMMAND message Note: For neighboring cells the six strongest BCCH frequencies of the BA/3G BA list (BCCH Allocation) are reported (only if enhanced MEASUREMENT REPORT is used more than six neighbors are possible).

35 Principle of event data record collection in the BSS MN1783EU11MN_0001 © 2003 Siemens AG 55 . to the history data on the dropped call. which can be uploaded to the RC. the BSC generates a history data record and stores it in the History Data logfile.Performance measurements management Siemens • After having received a history data message related to a dropped call. • The OMC tool set (OTS) provides the evaluation and statistic functionality related Up to 16 valid event data records Time 470 or 480 ms units Valid Measurement Reports Call drop Skipped event data records: 3 Fig.

TA. etc. DTX flag. TCH/H) Mobile ID (e. TCH/F.Siemens Performance measurements management Data collected by this feature • The BSC stores the history data uploaded from the BTSE in a so-called HDCTR logfile.IMEISV) Event records (RXLEV. One BSC HDCTR logfile contains all trace data recorded per BSC.) Number of skipped event data records • Commands and signaling: Assignment commands Handover commands (with preceding HO CONDITION INDICATION) Power control commands • etc. • Each dropped call contained in this file is characterized by • Cell ID • TRX ID • BSIC • Neighbor cell IDs • Cause of the call drop: Error indication: T200 expired N200+1 times Error indication: sequence error Connection failure: Distance Limit Exceeded Connection failure: Handover access failure Connection failure: Radio link failure Connection failure: Remote transcoder failure Expiry of T10 for intracell handover failures Expiry of T8 for internal intercell handover failures etc. MS and BS power. • History Information: Timeslot number Channel mode (speech or data) Channel type (SDCCH.g. RXQUAL. 56 MN1783EU11MN_0001 © 2003 Siemens AG .

3.1 Handling on Radio Commander Activation of the History Data of Dropped Calls Feature HDCTR object The HDCTR object can be created from the BSS icon in the BSS Summary panel: Fig.Performance measurements management Siemens 5. 36 Create HDCTR command MN1783EU11MN_0001 © 2003 Siemens AG 57 .3 5.

Siemens Performance measurements management The parameters have the following meaning: Parameter Measurement Sets Periodicity Start and Stop date Meaning the number of valid event data records (measurements. 58 MN1783EU11MN_0001 © 2003 Siemens AG . true) This attribute is used to enable HDCTR data provisioning for a BTS. the BSC will ask the BTS for history data in case of a call drop event within this BTS. one for every day of the week with start and end time (analogous to CTRSCHED) the dates when the collection of history data starts and stops BTS object In the BTS object only one parameter is important: Parameter Enable HDCTR Meaning (range: false.) stored before a call dropped list of trace periods. If this flag is set (true). etc.

37 Creation of the History of dropped calls object Fig. 38 Enabling History on Dropped Call Trace MN1783EU11MN_0001 © 2003 Siemens AG 59 .Performance measurements management Siemens Fig.

60 MN1783EU11MN_0001 © 2003 Siemens AG . the upload will be performed every X (configured) hours at the full minute. 8.2 Transfer of BSS Logfiles to the RC The transferring of the BSS History Data logfiles to the RC is the same as for other CTR logfiles.Siemens Performance measurements management 5.3. 2. 1 hour. 6. 24 hours) The attribute defines the period between two automatic uploads of HDCTR logfiles. The upload takes place in one of the following cases: • After a configurable period (0 = not automatically. For the LMT only the manual upload is available and in this case the logfiles on the BSC are not deleted. 4. 2 hours. where ‘0’ means ‘no automatic (periodic) upload’. BSC object Also in the BSC object some parameters are of relevance for the handling of the history data files: Parameter File size Upload Period Meaning (range: 1 to 12 MByte) history on dropped calls file size (0. As no starting time parameter for the automatic upload is foreseen. • At any time when the operator issues a corresponding upload command (all files). • If the maximum logfile size at BSC is reached. An upload of the History Data logfile is initiated by a BSC Trace logfile upload notification.…. 1. 24 hours) the BSC sends an HDCTR upload request notification to the RC with the list of HDCTR trace logfile ready to be uploaded. 12. 3.

Performance measurements management Siemens Fig. 39 Parameters to configure the upload of History data file for dropped calls MN1783EU11MN_0001 © 2003 Siemens AG 61 .

TGTBTS) with the related symbolic names. a postprocessing tool can load the history data logfiles from RC via FTP.3 History data administration and conversion at the RC The History Data logfile uploaded from BSC are handled in the same way as other CTR logfiles. and the Cell Global Identifiers of the BTSs and TGTBTSs. the uploaded files are moved to a predefined directory. BTS. At the RC. During this phase a header file containing the symbolic names of the objects of the BSS (BSC.3. and then stored in the binaryHistory directory. O&M toolset). Therefore. A History Data file conversion can be performed on operator request and the operator can ask for the conversion to ASCII format or to XML format. 62 MN1783EU11MN_0001 © 2003 Siemens AG . In that conversion process there is an automatic replacement of the Network Element Id of the objects (BTS. BTSM. 5. if available. are attached to the uploaded file. TGTBTS).3.Siemens Performance measurements management 5.4 Export of history data The history data logfiles in binary or converted (ASCII/XML) file format can be exported to a post-processing tool (third party tool.

Performance measurements management Siemens Fig. 40 Export options for history data files MN1783EU11MN_0001 © 2003 Siemens AG 63 .

Siemens Performance measurements management 64 MN1783EU11MN_0001 © 2003 Siemens AG .

Performance measurements management Siemens 6 Exercise MN1783EU11MN_0001 © 2003 Siemens AG 65 .

Siemens Performance measurements management 66 MN1783EU11MN_0001 © 2003 Siemens AG .

Create another scanner that reports the processor load of a single BTSE periodically every 30 minutes. Handling of scanners Handling of scanners MN1783EU11MN_0001 © 2003 Siemens AG 67 . Change it to always include all existing BTSE.Performance measurements management Siemens Exercise Title: Objectives: Task Create a scanner that reports the processor load of the BSC with the minimum reporting interval. Manually upload the results and convert them to xml-format. Change the scanner to include a second BTSE. Trigger an automatic upload every day at a predefined time.

Siemens Performance measurements management 68 MN1783EU11MN_0001 © 2003 Siemens AG .

Performance measurements management Siemens 7 Solution MN1783EU11MN_0001 © 2003 Siemens AG 69 .

Siemens Performance measurements management 70 MN1783EU11MN_0001 © 2003 Siemens AG .

Fig. 41 MN1783EU11MN_0001 © 2003 Siemens AG 71 .Performance measurements management Siemens Solution Title: Objectives: Handling of scanners Handling of scanners Task Create a scanner that reports the processor load of the BSC with the minimum reporting interval.

42 72 MN1783EU11MN_0001 © 2003 Siemens AG . Fig.Siemens Performance measurements management Create another scanner that reports the processor load of a single BTSE periodically every 30 minutes.

Performance measurements management

Siemens

Change the scanner to include a second BTSE.

Fig. 43

MN1783EU11MN_0001
© 2003 Siemens AG

73

Siemens

Performance measurements management

Change it to always include all existing BTSE.

Fig. 44

74

MN1783EU11MN_0001
© 2003 Siemens AG

Performance measurements management

Siemens

Manually upload the results and convert them to xml-format.

Fig. 45

MN1783EU11MN_0001
© 2003 Siemens AG

75

46 76 MN1783EU11MN_0001 © 2003 Siemens AG .Siemens Performance measurements management Fig.

Performance measurements management Siemens Trigger an automatic upload every day at a predefined time. 47 MN1783EU11MN_0001 © 2003 Siemens AG 77 . Fig.

Siemens Performance measurements management 78 MN1783EU11MN_0001 © 2003 Siemens AG .