BSS B11 Optimization and Frequency Planning With RMS

BSS B11 BSS B11 Optimization and Frequency Planning using RMS
TMO18110 D0 SG DEN I1.0 Issue 1.0
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent 2010
All rights reserved Alcatel-Lucent 2010 Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved Alcatel-Lucent 2010 BSS B11 Optimization and Frequency Planning using RMS - Page 1
Empty page
Switch to notes view!
2
This page is left blank intentionally
Terms of Use and Legal Notices

1. Safetyto Warning Switch notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment alone. The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent. All other trademarks, service marks and logos (Marks) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark. Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent. Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited. User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and is expressly prohibited from modifying the information or creating derivative works without the express All Rights Reserved Alcatel-Lucent 2010 3 written consent of Alcatel-Lucent.
All rights reserved Alcatel-Lucent 2010
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not AlcatelLucent has been advised of the possibility of such damages. Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement, nor a recommendation. This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely accurate. Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and its operation, or contact your nearest Alcatel-Lucent representative for more information. The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties, including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of dealing, usage or trade practice. Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including, but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these Terms of Use and Legal Notices shall remain in full force and effect.
Blank Page
4
Course Outline
1. Optimization & FP using RMS About This Course
4. Topic/Section is Positioned Here
Course outline 1. Radio Measurements Overview 3JK12103AAAAWBZZA Technical 2.support RMS Feature Description 3JK12104AAAAWBZZA 5. Topic/Section is Positioned Here Course objectives
3. Radio measurements statistics Data 3JK12105AAAAWBZZA 5. RMS Based AFP 3JK12107AAAAWBZZA 6. Annex 3JK12108AAAAWBZZA
4. RMS is Based Radio Network 3JK12106AAAAWBZZA 6. Topic/Section is Positioned Here 1. Topic/Section Positioned Here Optimization
Xxx Xxx Xxx
7. Topic/Section is Positioned Here
2. Topic/Section is Positioned Here 3. Topic/Section is Positioned Here
5
Course Outline [cont.]

6
Course Objectives
Welcome to BSS B11 Optimization and Frequency Planning using RMS
Upon completion of this course, you should be able to:
By the end of the course, the trainee will be able to: Describe the Radio Measurements Statistics (RMS) feature Activate the RMS job and tune RMS templates Interpret RMS counters And through relevant case studies Use RMS data for Optimization Use RMS data for Frequency planning
7
Course Objectives [cont.]

8
About this Student Guide

Conventions used in this guide Switch to notes view!
Note
Provides you with additional information about the topic being discussed. Although this information is not required knowledge, you might find it useful or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment damage or personal injury.
Where you can get further information

If you want further information you can refer to the following: Technical Practices for the specific product Technical support page on the Alcatel website: http://www.alcatel-lucent.com
About this Student Guide [cont.]

10
Self-assessment of Objectives
Contract number : Course title :
At the end of each section you will be asked to fill this questionnaire Please, return this sheet to the trainer at the end of the training to notes view!
Dates from : Location : to :
Client (Company, Center) : Language : Switch
Number of trainees : Surname, First name :
Did you meet the following objectives ? Tick the corresponding box Please, return this sheet to the trainer at the end of the training
Yes (or globally yes) No (or globally no)
Instructional objectives 1 To be able to XXX
Comments
2
11
BSS B11 BSS B11 Optimization and Frequency Planning using RMS All Rights Reserved Alcatel-Lucent 2010
Self-assessment of Objectives [cont.]

Instructional objectives Yes (or Globally yes) No (or globally no) Comments
12
Other comments
Thank you for your answers to this questionnaire
11
Do not delete this graphic elements in here:
Section 1 Optimization & FP using RMS

Module 1 Radio Measurements Overview
3JK12103AAAAWBZZA Edition 1
All Rights Reserved 2007, Alcatel-Lucent 3JK12103AAAAWBZZA Edition 1 Section 1 Module 1 Page 1
Blank Page
Optimization & FP using RMS Radio Measurements Overview 11
Document History Edition 01 Date YYYY-MM-DD Author Last name, first name Remarks First edition
Objectives
To be able to describe radio measurments
Objectives [cont.]
Table of Contents

1 2 3 4 5 Introduction Radio Link Measurements Radio Measurements Statistics Electro-Magnetic Environment (EME) statistics CCCH load measurements
Page 7 9 20 27 29
Table of Contents [cont.]

BSS B11 BSS B11 Optimization and Frequency Planning using This RMS
All Rights Reserved Alcatel-Lucent 2007 page is left blank intentionally
Optimization & FP using RMS Radio Measurements Overview
11
1 Introduction
1 Introduction
Radio Measurements
The Radio Link Measurements: Performed in the BTS on a per channel basis, and used in the BTS and BSC by Telecom functions. The Radio Measurements Statistics (RMS): Performed in the BTS on a per TRX basis, and aggregated at cell level in the BSC. Those statistics are controlled by Performance Management functions, and used for operation purposes. Electro-Magnetic Environment (EME) measurements CCCH Load Measurements
11
2 Radio Link Measurements
Principle
10
The radio measurements are performed in the BTS on a per channel basis.
The following channels are concerned :
bi-directional active traffic channels and dedicated control channels, idle traffic channels, random access channel (RACH).
For active channels, the radio measurements consist in :

The carrying out of the uplink measurements, The collection of the downlink measurements, The computation of the Timing Advance (TA) command to be applied by the MS
For idle channels, the radio measurements consist in the measurement of the received interference level. For RACH, the radio measurements consist in measuring the load of the channel.
RLM Metrics
11
The basic radio link metrics are :

The signal strength The signal quality The MS-BS absolute distance
The signal strength:

The received signal level is denoted as RXLEV by 3GPP The BTS must measure the RMS signal level at the receiver input over the full range of -110 dBm to -48 dBm The reported value shall be the average of the received signal level Measurement samples in dBm taken within the reporting period of length one SACCH multiframe. The actual averaging performed by the BTS is done with linear values
RXLEV
12
RXLEV is used for active channels as an input parameter by the power control and handover preparation functions For idle channels, RXLEV gives an estimation of the interference level on the channel The received signal level shall be mapped to an RXLEV value between 0 and 63:
RXLEV 0 1 2 : 62 63 RMS received signal level < -110 dBm -110 dBm to -109 dBm -109 dBm to -108 dBm : : RXLEV 0 1 2 : 62 63 Assumed values of signal level -110 dBm -109 dBm -108 dBm : -48 dBm -47 dBm
-49 dBm to -48 dBm > -48 dBm

3GPP TS 45.008 definition
Values assumed by the power control and handover algorithms in the ALCATEL BSS.
RXQUAL
13
The signal quality is denoted as RXQUAL by 3GPP RXQUAL is used for active channels as a criterion by the power control and handover preparation functions By definition, there is no RXQUAL estimation for idle channels. The received signal quality shall be measured by the BTS in a manner that can be related to an equivalent average BER before channel decoding (i.e. chip error ratio), assessed over the reporting period of one SACCH multiframe. The reported parameter (RXQUAL) shall be the received signal quality averaged over the reporting period of length one SACCH multiframe The BTS estimated quality value is divided into eight quality bands.
RXQUAL [cont.]
14
The mapping of the equivalent BER before channel decoding on the quality bands:
RXQUAL 0 1 2 3 4 5 6 7 BER before channel decoding less than 0.2% 0.2% to 0.4% 0.4% to 0.8% 0.8% to 1.6% 1.6% to 3.2% 3.2% to 6.4% 6.4% to 12.8% greater than 12.8% Assumed value of BER 0.14% 0.28% 0.57% 1.13% 2.26% 4.53% 9.05% 18.10%
Timing Advance
15
The absolute MS-BS distance is estimated by measuring the Time of Arrival (TOA) of the received burst at the BTS for each allocated timeslot (activated channel/subchannel) or for RACH. The absolute MS-BS distance is evaluated by the BTS to calculate the TA command to be applied by the MS for adaptive time alignment purposes with the BTS The value is expressed by a number of bit periods on the Radio interface. The bit rate on the Radio interface is 270.8 kbit/s therefore a bit period lasts 3.69 *s which corresponds to a distance of 1.1 km. But due to the roundtrip delay between MS and BS, a bit period corresponds to a MS-BS distance of (1.1/2) km i.e. around 550 m.
Reporting periods
16
The statistical values of signal level and quality are obtained over a measurement period. This period is also called "reporting period". For a TCH, the reporting period of length 104 TDMA frames (480 ms) is defined in terms of TDMA frame numbers (FN) as shown in table Table:
SACCH Multiframe
17
FACCH
Fast Associated 11.4 kb/s or 22.8kb/s - Call Setup, Call Release, Control Channel BSS B11 BSS B11 Optimization and Frequency Planning using All Rights Reserved Alcatel-Lucent 2007 RMS
TCH cycle stealing
peak
On-demand signalling
HO Command, DTM procedures
Measurements Reports
18
Radio Measurement Reporting :

For each MS connected to the BTS (TCH or SDCCH)
Measurement Result
Measurement Report DL measurements
UL+DL measurements
MS
BTS
BSC
The UL received level and quality are measured every SACCH The Timing advance (TA) is computed The UL information is gathered into a measurement report this is the message result sent by the BTS to the BSC
Measurements Results
19
Measurement Result message:

L1 info: SACCH Layer 1 header containing: MS_TXPWR_CONF and TOA. L3 info: MEASUREMENT REPORT from the MS: This message contains the downlink measurements and neighboring cell measurements. Uplink measurements performed by the BTS. SACCH BFI BTS power level used.
11
20
3 Radio Measurements Statistics
Principle
21
Radio Measurements Statistics are compound statistics based on available radio link measurements for Circuit Switched TCH calls, either performed by the BTS or reported by the MS No RMS measurements are performed for SDCCH calls. TCHs allocated to (E)GPRS traffic are not concerned by RMS. These measurements are controlled by the Performance Management function
RMS Entities
22
BTS RMS entity: This is the entity responsible for the RMS function in a TRX. It is controlled by the BSC RMS entity through the Abis RMS protocol. BSC RMS entity: This is the BSC entity responsible for the control of the BTS TRX RMS function. There is one BSC RMS entity per TRX.
RMS Data
23
General information : These are general information to allow PM to make efficient use of the following statistics. C/I vector : This C / I ratio gives a representation of the difference of receive level on the downlink between the serving cell and the neighbor cell. RXQUAL_UL / RXLEV_UL matrix : This 2-dimension matrix gives for each entry defined by (RXLEV uplink in a given band, RXQUAL uplink in a given band),
the total number of reports, an average of the corresponding MS power level, an average of the corresponding MS Timing Advance.
RMS Data [cont.]

24
RXQUAL_DL / RXLEV_DL matrix : Same matrix but for the downlink. BFI / RXLEV_UL matrix : This 2-dimension matrix gives for each entry defined by (RXLEV uplink in a given band , Number of consecutive BFI in a given band): the total number of reports. Radio link Counter (S) vector : This vector gives for each entry defined by Radio link Counter (S) in a given interval:the total number of reports. Path balance vector : This vector gives for each entry defined by (path balance in a given interval): the total number of reports.
RMS Data [cont.]

25
Voice quality statistics : A set of counters is defined to represent the distribution of quality for speech calls, based on measurements of RXQUAL & RXLEV on the uplink and downlink, the FER on the uplink. AMR measurements: A set of counters is defined feature to allow monitoring the usage of each allowed AMR codecs (FR or HR), compared to the link level, in order to help the operator tuning the AMR parameters. Timing Advance (TA) statistics: The aim of this feature is to provide statistics information on timing advance, in order to understand geographical traffic distribution in a cell, to identify resurgences and hot spots
Mobile Assisted Frequency Allocation:MAFA

26
This RMS sub-feature allows the RMS function to gather C/I information (see above) for specific frequencies declared by the operator (called EMO-frequencies). This typically allows to monitor specific propagation conditions to optimize frequency plan If allowed by configuration , the BSS sends the Extended Measurement Order (EMO) to the MS on SACCH with the list of EMO-frequencies to be reported, the MS supporting the MAFA feature answers with a single Extended Measurement Report.
11
27
4 Electro-Magnetic Environment (EME) statistics
4 Electro-Magnetic Environment (EME) statistics
Principle
28
The EME feature performs the assessment of the average power emitted at the BTS antenna output connector over time. Power data is provided per cell and per frequency band. This feature provides:
Power evolution over time for each cell (per band), Warning report on the delta power between the emitted power and a predefined threshold, Statistics and tendencies on the emitted power for each cell (per band).
EME measurement statistics are permanently handled by EVOLIUM BTS/TRE on any downlink channel. Once started, TRE collects permanently power data. At the end of each measurement period, triggered by reception of EME_DATA_REQ, TRE finalizes EME statistics and generates 2 new counters:
Statistics on emitted absolute power on the GSM band (850MHz and 900MHz) Statistics on emitted absolute power on the DCS band (1800MHz and 1900MHz)
11
29
5 CCCH load measurements
5 CCCH load measurements
Principle
30
The CCCH load measurements feature performs the assessment of load on CCCH channels. This feature provides:
Number of blocks sent on AGCH and PCH, Number of busy RACH slots, Number of received channel requests Statistics about IMMEDIATE ASSIGNMENT and pagings received from BSC
CCCH load measurements are permanently handled by EVOLIUM BTS/TRE on any CCCH channel. Once started, TRE collects permanently power data. At the end of each measurement period, triggered by reception of CCCH LOAD REQUEST, TRE finalizes CCCH load measurements and generates 8 new counters:see comments pages
11
31
End of Module Radio Measurements Overview
12

Module 2 RMS Feature Description
All Rights Reserved Alcatel-Lucent-Lucent 2007
All Rights Reserved 2007, Alcatel-Lucent-Lucent 3JK12104AAAAWBZZA Edition 1 Section 1 Module 2 Page 1
Blank Page
Optimization & FP using RMS RMS Feature Description 12
All Rights Reserved Alcatel-LucentLucent 2007
Objectives
To be able to describe the Radio Measurements Statistic mechanism and activate the RMS job
Objectives [cont.]
2007intentionally This page is left Lucent blank
All Rights Reserved Alcatel-Lucent-
Table of Contents

1 2 3 4 5 Introduction How Does it work? RMS Job Activation RMS Message Flow Scenario MAFA
Page 7 11 14 19 23

All is Rights Reserved Alcatel-Lucentpage left blank intentionally Lucent 2007
Optimization & FP using RMS RMS Feature Description
12
1 Introduction
1 Introduction
Objectives
Radio Measurements Statistics (RMS) is a feature introduced since B7 BSS software release Designed to make far easier the work for planning and optimisation of a network Allowing to constantly check pure network QoS and optimize various network parameters:
Provides useful statistics on reported radio measurements Based on real field measurements and not in predictions Users mobiles and BTSs are acting as measurement equipments
RMS are performed by mobiles and BTSs and made available at the OMC-R through the usual PM application.
1 Introduction
Objectives [cont.]
Using RMS, the operator is able to : Detect interfered frequencies and interferes Assess quality of the cell coverage Assess radio link quality Evaluate the voice quality Assess the traffic distribution from statistics
On reported neighbour cells Based in Timing advance statistics
Monitor AMR codec use to evaluate AMR operation and the quality of radio coverage in a cell
1 Introduction
RMS results usage

10
Optimize the neighborhood and frequency planning Detection of the origin of a bad QoS in order to optimize consequently the network parameters.
Benefit to whole NPO
NPO
RMS Templates MAFA tuning
OMCR
RMS Binary Files
Compute Interference Matrix RNP

BSC BTS
12
11
2 How Does it work?
2 How Does it work?
Principle
12
Radio Measurement Statistics are performed by mobiles and BTSs on TCH channels The BTS format those requested statistics and stores all the results
Voice: SF22 SF21 SF20 SF19 SF18 SF17 SF16 SF15
Measurement Report (MR)
Speech Frame
MR
Serving cell
6 strongest neighboring cells
BTS
Call quality statistics Radio quality statistics Serving cell C/I statistics
2 How Does it work?
Principle [cont.]
13
At the end of observation period, BTS builds a report and sends it to BSC BSC forwards the measurement to the OMC-R thought PM application RMS results can be exported from OMC-R to a post-processing tool RMS results are retrieved once per job
12
14
3 RMS Job Activation
Activations methods
15
RMS Job can be activated from OMC-R via two methods:

Permanent Measurement Campaign On demand measurement campaign
Activating RMS wont overload the network

Most of the work is done in the BTS 1 job per day
RMS can be activated permanently on all the cells of the network

This has been done on several main Alcatel-Lucent networks
Frequently asked question: Will activating RMS overload the network? No, activating RMS wont overload the network since most of the work is done in the BTS. That's why RMS can be activated permanently on all the cells of the network, this has been done on several main Alcatel-Lucent networks.
Permanent Measurement Campaign

16
Permanently through the PM type 31 Provide start & stop time RMS job is launched automatically
every day between the same hours on all the cells of the OMC-R
On demand measurement campaign

17
On demand measurement campaign

Provide start & stop time Provide BSS identity & object list Accumulation period Must be restarted after the RMS stop time, so as to get new RMS data. On demand RMS job is launched only once
How to Do It
18
PMC activation through UFM ODMC activation through BSSUSM Check Campaigns are unlocked and enabled
12
19
4 RMS Message Flow Scenario
RMS protocol
20
The BSC initiates the RMS job for the concerned TRX. The BTS starts the measurements job for all new TCH calls, based on:
BTS uplink measurements, MS downlink measurement reports. MS downlink Extended Measurements Report (EMR) MS BTS START_RMS_REQ BSC
Start of RMS Job START_RMS_REP
RMS protocol [cont.]

21
The BSC stops the RMS job, The BTS stops the RMS measurements, finishes compiling the statistics, and prepares the measurement report for upload.
MS
BTS STOP_RMS_REQ
BSC
Finalise RMS stats Prepare upload STOP_RMS_REP
RMS protocol [cont.]

22
The BSC asks for the current RMS results by sending the RMS_DATA_REQ message. The BTS transfers the RMS measurements, segmented in blocks The BTS uses timer T_RMS_BTS to interleave the reported data at regular interval, in order to avoid LAPD overload. The BTS notifies that the RMS transfer has finished by sending the RMS_DATA_REP (success) message.
MS start T_RMS_BTS T_RMS_BTS expiry restart T_RMS_BTS T_RMS_BTS expiry restart T_RMS_BTS stop T_RMS_BTS
BTS RMS_DATA_REQ
BSC
RMS_DATA_IND (Block 1) RMS_DATA_IND (last Block) RMS_DATA_REP(success)
12
23
5 MAFA
5 MAFA
Principle
24
Provides a way for the system to ask each MS to measure extrafrequencies (frequencies of non-neighbour cells) MAFA can be used to check interferences from non-neighbour cells and help the operator find "clean" frequencies Frequencies will be reported even if they are received with a lower level than the BCCH frequency of neighbour cells It is a standardized GSM feature Mobile dependent feature. MAFA is totally included in the RMS feature, Nevertheless, some specific actions are required at the OMC-R and BSC side in order to launch the MAFA procedure
Serving cell 6 strongest neighboring cells EMO-frequencies
5 MAFA
How does it work?

25
Inside a RMS job is possible to apply the Mobile Assisted Frequency Allocation (MAFA) or Extended Measurement Reporting:
Consists in sending an Extended Measurement Order (EMO) to the mobiles Mobile takes one SACCH multiframe to perform measurements on specific frequencies These measurements are reported via the EXTENDED_MEASUREMENT_REPORT message
The EMO is only sent once per call. The statistics related to MAFA will be collected in the BTS and integrated in the RMS results
5 MAFA
How does it work?

26
MS
BSC BTS TCH ASSIGNMENT PHASE (OC or TC)

< -------------------------------------------------------PHYSICAL CONTEXT REQUEST -------------------------------------------------------- > PHYSICAL CONTEXT CONFIRM < -------------------------------------------------------CHANNEL ACTIVATION (TCH) (EMO included) -------------------------------------------------------- > CHANNEL ACTIVATION ACKNOWLEDGE . . TCH establishment. . ------------------------------------------------------- > ASSIGNMENT COMPLETE
MSC
< ----------------------------------ASSIGNMENT REQUEST
--------TCH---------> ASSIGNT COMPLETE <------SACCH---------------SACCH------> <------SACCH---------------SACCH------> <-------SACCH-------EMO (MAFA freq. List) --------SACCH------> EMR (MAFA freq.RxLev) <------SACCH---------------SACCH------>
----------------------------------- > ASSIGNMENT COMPLETE
5 MAFA
Activation
27
MAFA job is included in the RMS job

MAFA job that allows measurements of specific frequencies by MAFA mobiles during the RMS job
Two aspects on MAFA job definition:

The activation of the MAFA feature, that can be done through the flag EN_EXT_MEAS_REP The definition of the frequencies to be monitored by the MAFA mobiles (called MAFA frequencies)
The definition of the MAFA frequencies and EN_EXT_MEAS_REP flag can be performed thought NPO also
5 MAFA
How to Do It
28
Using OMCR: PRC
5 MAFA
How to Do It
29
Using NPO tuning session: MAFA Tuning
12
30
End of Module RMS Feature Description
13

Module 3 Radio measurements statistics Data
Blank Page
Optimization & FP using RMS Radio measurements statistics Data 13
Objectives
To be able to describe RMS data
Objectives [cont.]
Table of Contents

1 General information TRX based information 2 The neighbor cells statistics Name of No Level Name of No Level CI-vector based on Normal Measurement Report CI-vector based on EMR Example Exercise 3 Radio Quality related statistics The RXQUAL_UL/RXLEV_UL matrix The RXQUAL_DL/RXLEV_DL matrix Example BFI/RXLEV_UL Matrix Example Radio link Counter (S) vector Example Path Balance vector Example Exercise 4 Voice Quality Statistics Name of No Level Computation of Voice Quality statistics BSS B11 VQ RMS Counters BSS B11 Example Optimization and Frequency Planning using All Rights Reserved Alcatel-Lucent 2007 RMS 5 AMR Statistics Measurement of AMR codec usage AMR FR UL BFI vector AMR HR UL BFI vector Example AMR FR XL usage/XL_RXLEV matrix AMR HR XL usage/XL_RXLEV matrix Example Exercise 6 TA Statistics Name of No Level Timing advance distribution Average RXLEV per TA band counters Average RXQUAL per TA band counters Example End of Module
Page 7 8 10 11 12 13 17 18 19 20 21 24 27 28 32 33 35 36 38 39 40 41 42 49 57 58 59 61 62 63 64 65 66 67 68 69 70 71 72 73 74

Page
Optimization & FP using RMS Radio measurements statistics Data
13
1 General information
TRX based information

The TRX based information indicators:

Indicate whether the report does not include all the reported neighbor cells(overflow, see note below). Indicate whether a TRX overload occurred. Indicate whether a partial restart (C/I only) of the RMS job on the TRX occurred.
RNO RMS Indicators:

- RMS_info_CI_overload_indication:
Flag indicating that the upper limit of 42 C/I vectors is exceeded during RMS job duration. In this case, new C/I vectors are not taken into account The list of frequencies to be monitored by the mobile is limited to 33 but due to resurgence the same frequency can be reported several times (each time with a different BSIC). If the number of reported cells is above the dimensioning limit (maximum 42 CI-vectors are reported), the extra new reported frequencies are not taken into account anymore. In the result report the related overflow indicator is set accordingly. - RMS_info_overload_indication: Indication whether a TRX overload occurred during RMS job duration. In this case, the measurements data collection is interrupted until the overload situation disappears. RMS statistics are thus based on partial measurements collection -RMS_info_Partial_Restart_indication: Bit map indicating that the measurements (for and only for CI vector computation) on either Neighbour cells or on MAFA frequencies or on both or none were restarted during RMS job duration. The bitmap is represented as follows : 0 : no CI partial resul
TRX based information [cont.]

Total number of MEASUREMENT RESULTS messages used for statistics Total number of EXTENDED_MEASUREMENT_REPORT messages, used for (C/I) statistics
RMS_Extended_Meas_Report_total: Total number of extended measurements (through MAFA) during the RMS statistics retrieval
13
10
2 The neighbor cells statistics
CI-Vector
11
The RMS function builds C/I statistics based on measurement reports gathered:
for regular neighbour cells from MS MEASUREMENT REPORT, and for EMO-frequencies from MS EXTENDED MEASUREMENT REPORT.
I
MC F
MC A
MC B
MC E
S C MC C MC D
CI-Vector [cont.]
12
Declared/reported neighbor cell:

For each declared/reported neighbor cell:
The Neighbor cell identity CI-vector.
The identification of the Neighbor cell shall be done using:

BCCH_ARFCN and BSIC.
EMO-frequency:
For each reported EMO-frequency:
The frequency_id CI-vector.
The identification of these frequencies shall be done using:

Frequency ARFCN.
- The BCCH ARFCN is deduced in the BTS from the BCCH frequency index and the list of indexed
frequencies (sent by the BSC at the beginning of the RMS job).

- In case of a frequency reported via Extended Measurement Reporting, no BSIC is required : the
frequency ARFCN is not directly linked to a BCCH frequency. The ARFCN value of the frequency is deduced in the BTS from the place of the measurement in the EXTENDED_ MEASUREMENT_REPORT and from the ordered list of the EMO-frequencies. This list is built by the OMCR and passed via BSC to BTS at the beginning of the RMS job.
- The CI-vector shall be provided for each requested (by operator) frequency in context of Extended
Measurement Reporting. The maximum number of frequencies in the order (EMO) is the maximum defined in 3GPP (=21). Hence the maximum in the report is 21 also. When in exceptional cases, more results are available (future expansion in 3GPP), only the first 21 are reported.
CI-vector based on Normal Measurement Report

13
This vector gathers measurements related to regular neighbor cells For each neighbor cell, it gives the total number of measurement reports in which the C/I related to the neighbor cell is reported in C/I band X (as described next slides) C/I is expressed in dB and it is computed as follows :
If EN_BALANCED_CI = TRUE then : C/I (dB) = RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX) RXLEV_NCELL else : C/I (dB) = RXLEV_DL (dBm) - RXLEV_NCELL (dBm)
- The difference of (BS_TXPWR - BS_TXPWR_MAX) has been introduced in order to compensate the
differences of the power transmission levels due to the DL power control.

- The expression (RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX)) can be seen as a kind of normalized
received power level in case the BTS would always have used the maximum allowed power level.
- Note that the formula is written independently of the coding used for the variables. - RXLEV_DL and RXLEV_NCELL are the received signal levels of the serving and of the neighbor cells,
expressed in dBm.
- BS_TXPWR is the BTS transmitted power - and BS_TXPWR_MAX is the maximum allowed BTS transmission power. - Both are defined relatively to the maximum absolute output power of the BTS
(BTS_MAX_OUTPUT_POWER).
- BS_TXPWR and BS_TXPWR_MAX are expressed in dB. - The function abs() gives the absolute value of its argument.
CI-vector based on Normal Measurement Report [cont.]

14
The difference of (BS_TXPWR - BS_TXPWR_MAX) has been introduced in order to compensate the differences of the power transmission levels due to the DL power control
BTS Power (dBm) BS_TXPWR (dB) BTS_MAX_OUTPUT_POWER
BS_TXPWR_MAX (dB)
BS_TXPWR - BS_TXPWR_MAX BS_power_level (real transmission power level) Path loss DL RXLEV_DL (dBm) (real received power level)
- The difference of (BS_TXPWR - BS_TXPWR_MAX) has been introduced in order to compensate the
differences of the power transmission levels due to the DL power control.

- The expression (RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX)) can be seen as a kind of normalized
received power level in case the BTS would always have used the maximum allowed power level.
- Note that the formula is written independently of the coding used for the variables. - RXLEV_DL and RXLEV_NCELL are the received signal levels of the serving and of the neighbor cells,
expressed in dBm.
- BS_TXPWR is the BTS transmitted power - and BS_TXPWR_MAX is the maximum allowed BTS transmission power. - Both are defined relatively to the maximum absolute output power of the BTS
(BTS_MAX_OUTPUT_POWER).
- BS_TXPWR and BS_TXPWR_MAX are expressed in dB. - The function abs() gives the absolute value of its argument. - Note:
From B9, the variable BTS_MAX_OUTPUT_POWER (used for the power control and the path balance statistics) should be reported as a new RMS counter.

15
There are 10 C/I bands which are defined through 9 thresholds parameters, tuneable on a per RMS template basis:
C/I -63 dB MEAS_STAT_C/I_3 C1 C2 C3 MEAS_STAT_C/I_6 63 dB C10
Vector Maximum Max
C1,C10: Indicate the number of measurement reports received for the corresponding band
C/I band 1 is defined by : C/I band 2 is defined by : C/I band 3 is defined by :
-63 dB <= C/I < MEAS_STAT_C/I_1 MEAS_STAT_C/I_1 <= C/I < MEAS_STAT_C/I_2 MEAS_STAT_C/I_2 <= C/I < MEAS_STAT_C/I_3 : : :
C/I band 10 is defined by :
MEAS_STAT_C/I_9 <= C/I <= 63 dB

16
Memory limitations have led to the use of 10 slots, or buckets that gather the data. The bucket width and position can be adjusted by tweaking the 9 internal boundaries in each cell (the extreme boundaries are fixed). This template adjustment can be easily done in RNO. The number of drops in each bucket is also an approximation and is only one byte (0..255) which is then multiplied by a factor (the MAX_SAMPLE value)
-63dB
MEAS_STAT_C/I_5
63dB
C1
C2
C3
C4
C5
C6
C7
C8
C9
C10
To save on the memory resources, these counters are in a coded format. The used coding mechanism is the following: The counters in the table (C1,C10) are one-byte percentage-counters. In fact the counters indicate the fraction of the row-maximum. (see Max). At coding time the coded values (the fraction) are determined as follows: Ci = Vi x 254 / row_maximum Notes: Vi represents the real number of measurements the value Ci=0 indicates number_of_meas = 0 the value Ci=254(0FE) indicates number_of_meas = row_max the value Ci=255(0FF) is reserved to indicate overflow At decoding time the real values are determined as follows: Vi = Ci x row_maximum / 254 Max: Max The maximum number of measurement reports received. = max of (V1,V2,V10)
CI-vector based on EMR

17
RMS 9a:
Same format as regular neighbor cells based vector The EMO based CI-vector is identified by the ARFCN only.
Example
18
C/I band 1 is defined by : C/I band 2 is defined by : C/I band 3 is defined by :
-63 dB <= C/I < MEAS_STAT_C/I_1 MEAS_STAT_C/I_1 <= C/I < MEAS_STAT_C/I_2 MEAS_STAT_C/I_2 <= C/I < MEAS_STAT_C/I_3 : : :
C/I band 10 is defined by :
MEAS_STAT_C/I_9 <= C/I <= 63 dB
To save on the memory resources, these counters are in a coded format. The used coding mechanism is the following: The counters in the table (C1,C10) are one-byte percentage-counters. In fact the counters indicate the fraction of the row-maximum. (see Max). At coding time the coded values (the fraction) are determined as follows: Ci = Vi x 254 / row_maximum Notes: Vi represents the real number of measurements the value Ci=0 indicates number_of_meas = 0 the value Ci=254(0FE) indicates number_of_meas = row_max the value Ci=255(0FF) is reserved to indicate overflow At decoding time the real values are determined as follows: Vi = Ci x row_maximum / 254 Max: Max The maximum number of measurement reports received. = max of (V1,V2,V10)
Exercise
19
Compute the C/I for the case hereafter:

EN_BALANCED_CI = TRUE BS_TXPWR_MAX = - 2 dB BS_TXPWR = - 6 dB RXLEV_DL = - 84 dBm RXLEV_NCELL = - 102 dBm C/I (dB) = (RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX) - RXLEV_NCELL) = ((-84dBm + abs(-6dB - (-2dB))) - (-102dBm) = (-84dBm + 4dB) + 102dBm = -80dB + 102dBm = 22dB
13
20
3 Radio Quality related statistics
The RXQUAL_UL/RXLEV_UL matrix

21
One Matrix of total number of reports in which: the uplink RXQUAL is reported in quality band X and the uplink RXLEV is reported in level band Y. For each total number of reports, the corresponding averaged value of MS power level and Timing Advance are given Quality
C
Level
PWR TA
The RXQUAL_UL/RXLEV_UL matrix [cont.]

22
RMS3a: Consist..
RXQUAL_UL - 47 dBm
0
C1 PWR1 TA1
1
C2 PWR2 TA2
2
C3 PWR3 TA3
7
Max1
MEAS_STAT_LEV_3 MEAS_STAT_LEV_4 RXLEV_UL
- 110- dBm
C80 PWR80 TA80
Max10
This counter RMS3a=TPR_RXQUAL_UL_RXLEV_UL is a matrix represented on the left side This counter RMS3b=TMR_RXQUAL_UL_RXLEV_UL is a vector represented on the right side The real number of Measurement Results in which UL RxQual is equal to i and UL RxLev is in RXLEV band j, is equal to : S(RXQUAL i, RXLEV band j) x Max j / 254 TPR_RXQUAL_UL_RXLEV_UL(i,j) x TMR_RXQUAL_UL_RXLEV_UL(j) / 254
The RXQUAL_UL/RXLEV_UL matrix [cont.]

23
There are 10 levels bands which are defined through 9 thresholds parameters tuneable on a per RMS template basis:
MEAS_STAT_LEV1 to MEAS_STAT_LEV9: -110 MEAS_STAT_LEV(i+1) MEAS_STAT_LEV(i) < -47 dBm
RXQUAL bands are fixed and they correspond to the possible values of the RXQUAL measurement : 0 to 7
0 being the best quality value and 7 the worst one
The matrix gathers following different information :

C1,C80: Indicate the number of measurement reports received for the corresponding row and column PWR1PWR80: Averaged value of MS_TXPWR in dBm for that total number of reports TA1TA80: Averaged value of Timing Advance for that total number of reports
There are 10 levels bands which are defined through 9 thresholds parameters, tuneable on a per RMS template basis, as follows : Level band 1 is defined by : MEAS_STAT_LEV_1 Level band 2 is defined by : Level band 3 is defined by : : Level band 10 is defined by : MEAS_STAT_LEV_9 >= RXLEV >= -110 dBm -47 dBm >= RXLEV > MEAS_STAT_LEV_1 >= RXLEV > MEAS_STAT_LEV_2 MEAS_STAT_LEV_2 >= RXLEV > MEAS_STAT_LEV_3
C1,C80: Indicate the number of measurement reports received for the corresponding row and column. To save on the memory resources, these counters are in a coded format. The used coding mechanism is as described in the CI-vector section. Max1,Max10: corresponding ROW. Max_1 Max_2 Max_10 The maximum number of measurement reports received for the
= max of (V1,V2,V8) = max of (V9,V10,V16) : = max of (V72,V73,V80)
In order to provide correct averages, the TRE cumulates the MS_TXPWR and timing advance. Therefore during measurement the TRE requires a 4 byte-storage for every counter. At the end of the observation, before passing it to the BSC, the TRE determines the average value (with one decimal) and coded it into a one_byte_average value.
The RXQUAL_DL/RXLEV_DL matrix

24
Matrix of total number of reports in which:

the downlink RXQUAL is reported in quality band X
the downlink RXLEV is reported in level band Y
For each total number of reports, the corresponding averaged value of:
BS power level and Timing Advance are given
The RXQUAL_DL/RXLEV_DL matrix [cont.]

25
RMS4a:
RXQUAL_DL - 47 dBm
0
C1 PWR1 TA1
Row Maximum
4 5 6 7
Max1
1
C2 PWR2 TA2
2
C3 PWR3 TA3
MEAS_STAT_LEV_3 MEAS_STAT_LEV_4 RXLEV_DL
- 110- dBm
C80 PWR80 TA80
Max10
There are 10 levels bands which are defined through 9 thresholds parameters, tuneable on a per RMS template basis, as follows : Level band 1 is defined by : MEAS_STAT_LEV_1 Level band 2 is defined by : Level band 3 is defined by : : Level band 10 is defined by : MEAS_STAT_LEV_9 >= RXLEV >= -110 dBm -47 dBm >= RXLEV > MEAS_STAT_LEV_1 >= RXLEV > MEAS_STAT_LEV_2 MEAS_STAT_LEV_2 >= RXLEV > MEAS_STAT_LEV_3
C1,C80: Indicate the number of measurement reports received for the corresponding row and column. To save on the memory resources, these counters are in a coded format. The used coding mechanism is as described in the CI-vector section. Max1,Max10: corresponding ROW. Max_1 Max_2 Max_10 The maximum number of measurement reports received for the
= max of (V1,V2,V8) = max of (V9,V10,V16) : = max of (V72,V73,V80)
The RXQUAL_DL/RXLEV_DL matrix [cont.]

26
Level bands are defined as previously RXQUAL bands are fixed and they correspond to the possible values of the RXQUAL measurement : 0 to 7 The matrix gathers following different information :
C1,C80: Indicate the number of measurement reports received for the corresponding row and column PWR1PWR80: Averaged value of the BS power level in dBm for that total number of reports, i.e. the corresponding averaged value of [BTS_MAX_OUTPUT_POWER - abs(BS_TXPWR)], TA1TA80: Averaged value of Timing Advance for that total number of reports
BS_TXPWR is the BTS transmitted power defined relatively to the maximum absolute output power of the BTS. BS_TXPWR is expressed in dB, whereas BTS_MAX_OUTPUT_POWER is expressed in dBm. The function abs( ) gives the absolute value of its argument Remark: In order to provide correct averages, the TRE cumulates the BS_TXPWR and timing advance. Therefore during measurement the TRE requires a 4 byte-storage for every counter. At the end of the observation, before passing it to the BSC, the TRE determines the average value (with one decimal) and coded it into a 1-byte_average value.
Example
27
BFI/RXLEV_UL Matrix
28
Matrix of total number of reports in which:

the number of consecutive BFI (Bad Frame Indication) is in BFI band X the uplink RXLEV is reported in level band Y
The number of consecutive BFI is computed over one SACCH multiframe The BTS increments the BFI (or CFE) counter as soon as consecutive speech frames cannot be decoded (next slide)
Consecutive Frame Erasure (CFE): MEAS_STAT_BFIi parameters define 9 intervals of cumulated numbers of consecutive speech frames which have a Bad Frame Indicator value set to 1 (it means that the speech frame is considered as erroneous by the BTS). As the TC will erase speech frames for which a Bad Frame Indicator flag (BFI) has been set to the value 1 by the BTS, a BFI is used in the RMS counters description whereas the CFE is used in the RMS indicators defined in the RNO tool. Note: By default, a BFI relates to a speech frame. When considering SACCH measurement, SACCH_BFI should be used.
BFI/RXLEV_UL Matrix [cont.]

29
Consecutive Frame Erasure:

The BTS increments the BFI (or CFE) counter as soon as consecutive speech frames cannot be decoded:
isolated speech frames with BFIs set to 1 are not counted sequences of not decoded speech frames are cumulated
SACCH Multiframe
SF SF SF SF SF SF SF SF SF 09 SF SF SF SF SF SF SF SF SF 18 SF SF SF SF SF SF SACCH FRAME BFI 0 CFE 7
01 02 03 04 05 06 07 08
10 11 12 13 14 15 16 17
19 20 21 22 23 24
BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI BFI 0 0 0 1 0 0 0 1 1 1 1 0 0 1 1 0 1 1 1 0 1 0 1 1
CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE CFE 0 0 0 0 0 0 0 0 1 2 3 3 3 3 4 4 4 5 6 6 6 6 6 7
The number of consecutive BFI is computed over one SACCH multiframe in the following way : In the period of the SACCH multiframe, a counter counts the number of speech frames which are consecutive and with BFI = 1 (it means that the speech frame is counted if its BFI = 1 and the previous frame has also BFI = 1). The counter must hold concurrently several periods of consecutive bad speech frames within the SACCH multiframe. Consecutive Frame Erasure (CFE): MEAS_STAT_BFIi parameters define 9 intervals of cumulated numbers of consecutive speech frames which have a Bad Frame Indicator value set to 1 (it means that the speech frame is considered as erroneous by the BTS). As the TC will erase speech frames for which a Bad Frame Indicator flag (BFI) has been set to the value 1 by the BTS, a BFI is used in the RMS counters description whereas the CFE is used in the RMS indicators defined in the RNO tool. Note: By default, a BFI relates to a speech frame. When considering SACCH measurement, SACCH_BFI should be used. If during this SACCH multiframe, DTX is applied on the uplink path (DTX_UL =1), the counter on consecutive BFI shall be ignored and the corresponding report shall not be taken into account in the statistics. Otherwise, the counter of consecutive BFI is computed over 25 frames (the 24 speech frames and the SACCH frame).

30
The matrix consists in BFI bands on X axis and level bands on Y axis
CONSECUTIVE BFI COUNTER
MEAS_STAT_BFI_3 MEAS_STAT_BFI_4
Max1
Row Maximum
- 47 dBm
C1 C2 C3
MEAS_STAT_LEV_3 MEAS_STAT_LEV_4 RXLEV_UL
- 110- dBm
C100
Max10
Level bands are defined as previously.

31
Level bands are defined as previously There are 10 BFI bands which are defined through 9 thresholds parameters, tuneable on a per RMS template basis:
MEAS_STAT_BFI1 to MEAS_STAT_BFI9:
0 < MEAS_STAT_BFI(i) MEAS_STAT_BFI(i+1) 25 speech frame
C1,C100: Indicate the number of measurement reports received for the corresponding row and column.
BFI band 1 is defined by :0 <= Consecutive BFI counter < MEAS_STAT_BFI_1 BFI band 2 is defined by :MEAS_STAT_BFI_1 <= Consecutive BFI counter < MEAS_STAT_BFI_2 BFI band 3 is defined by :MEAS_STAT_BFI_2 <= Consecutive BFI counter < MEAS_STAT_BFI_3 : : : BFI band 10 is defined by : MEAS_STAT_BFI_9 <= Consecutive BFI counter <= 25
Max1,Max10: The maximum number of measurement reports received for the corresponding ROW. Max_1 Max_2 Max_10 = max of (V1,V2,V10) = max of (V11,V12,V20) : = max of (V90,V91,V100)
To save on the memory resources, these counters are in a coded format. The used coding mechanism is as described in the CI-vector section
Example
32
Radio link Counter (S) vector

33
vector of total number of measurement reports for which the value of S (Radio link counter) is in S band X
Radio Link Counter S 0 C1 MEAS_STAT_S_3 C2 C3 MEAS_STAT_S_6 128 C10 Vector Maximum Max
To save on the memory resources, these counters are in a coded format. The used coding mechanism is as described in the CI-vector section The real number of Measurement Results in which Uplink Radio Link Counter is in S band j, is equal to: S(S band j) x Max / 254 TPR_RADIO_LINK(j) x MAX_RADIO_LINK / 254 Recall on the Uplink Radio Link Supervision procedure: For each active dedicated radio channel in a cell, a counter S called Radio Link Counter is: decremented by 1 by the BTS each time an SACCH measurement from the mobile cannot be decoded (SACCH_BFI=1). incremented by 2 by the BTS each time a valid SACCH measurement is received from the mobile (SACCH_BFI=0). Initial value of S = RADIOLINK_TIMEOUT_BS (cell parameter) if S reaches N_BSTXPWR_M, a radio link recovery is triggered (BTS and MS power increased at their maximum). if S reaches 0, a Radio Link Failure is triggered (channel drop). Therefore the value of S gives a measure of the quality of the radio uplink. RADIOLINK_TIMEOUT_BS: Counter threshold to detect a radio link failure on the uplink path. Min value : 1 Max value: 128 Samfr Default value: 18 Samfr
Radio link Counter (S) vector [cont.]

34
There are 10 S bands which are defined through 9 thresholds parameters, tuneable on a per RMS template basis:
MEAS_STAT_S1 to MEAS_STAT_S9: 0 < MEAS_STAT_S(i) MEAS_STAT_S(i+1) 128 SACCH mfr
C1,C10: Indicate the number of measurement reports received for the corresponding column
S band 1 is defined by : S band 2 is defined by : S band 3 is defined by : : : : S band 10 is defined by : Max: Max
0 <= S < MEAS_STAT_S_1 MEAS_STAT_S_1 <= S < MEAS_STAT_S_2 MEAS_STAT_S_2 <= S < MEAS_STAT_S_3
MEAS_STAT_S_9 <= S <= 128
The maximum number of measurement reports received. = max of (V1,V2,V10)
Example
35
S: counter managed by the BTS on a per call basis S = RADIOLINK_TIMEOUT_BS if good radio conditions S decremented if bad radio conditions The BSS triggers a call drop when S = 0
Path Balance vector

36
The Path balance is the difference between :

Path loss on the uplink : received level by the BTS - MS power level Path loss on the downlink : received level by the MS - BS power level
Path balance = path loss Uplink - path loss Downlink =

(RXLEV_UL - MS_TXPWR ) - ( RXLEV_DL - [BTS_MAX_OUTPUT_POWER - abs(BS_TXPWR )]
The BS power level is computed as the BTS nominal power decreased by the BS power relative level
SS U L PATH LO SS D L PATH LO
BS_TXPWR is the BTS transmitted power defined relatively to the maximum absolute output power of the BTS. BS_TXPWR is expressed in dB, BTS_MAX_OUTPUT_POWER is expressed in dBm. It is the maximum power level at the combiner output (given by the BTS). RXLEV_UL and RXLEV_DL are the received signal levels by the base station and by the mobile station respectively. They are expressed in dBm. MS_TXPWR is the transmission power of the mobile station and expressed in dBm. The function abs() gives the absolute value of its argument. Path Balance enables to detect System or aerials problems that can induce bad coverage but not real bad coverage problems. RMS_PathBalance_avg= If more than 3dB (considering the absolute value), some problems may occur. NOTE: Additional asymetric DL loss (external combiner) or UL gain (TMA) are not taken into account in the computation, so they must be considered when interpreting the RMS results.
Path Balance vector [cont.]

37
vector of total number of reports for which the value of the Path balance is in Path balance band X
Path Balance -110 dB MEAS_STAT_PATH_BALANCE_3 C1 C2 C3
MEAS_STAT_ PATH_BALANCE _6
110 dB C10
Vector Maximum Max
There are 10 path balance bands which are defined through 9 thresholds parameters, tuneable on a per cell basis:
MEAS_STAT_LEV1 to MEAS_STAT_LEV9: -110 MEAS_STAT_LEV(i+1) MEAS_STAT_LEV(i) < -47 dBm
C1,C10:Indicate the number of measurement reports received for the corresponding column
Path balance band 1 is defined by :-110 dB <= Path balance < MEAS_STAT_PATH_BALANCE_1 Path balance band 2 is defined by :MEAS_STAT_PATH_BALANCE_1 <= Path balance < MEAS_STAT_PATH_BALANCE_2 Path balance band 3 is defined by :MEAS_STAT_PATH_BALANCE_2 <= Path balance < MEAS_STAT_PATH_BALANCE_3 : : Path balance band 10 is defined by : Max: Max MEAS_STAT_PATH_BALANCE _9 <= Path balance <= 110 dB
The maximum number of measurement reports received. = max of (V1,V2,V10)
To save on the memory resources, C1,C10 counters are in a coded format. The used coding mechanism is as described in the CI-vector section
Example
38
Exercise
39
We assume that:
BTS_MAX_OUTPUT_POWER = 39dBm BS_TXPWR = - 6 dB RXLEV_DL = - 84 dBm RXLEV_UL = - 88 dBm MS_TXPWR = 30 dBm
Compute the Path_Balance?

PATH_BALANCE (dB) = (RXLEV_UL - MS_TXPWR) - (RXLEV_DL - [BTS_MAX_OUTPUT_POWER abs(BS_TXPWR)]) = (-88dBm - 30dBm) - (-84dBm - [39dBm - abs(-6dB)]) = - 118 dB - (-84dBm - 33dBm) = - 118 dB + 117 dB = - 1 dB
Then, add a LNA with 12 dB gain. What would be the Path Balance value ?
PATH_BALANCE (dB) = (-88dBm + 12dB - 30dBm) - (-84dBm - [39dBm - abs(-6dB)]) = + 11dB
LNA : low noise amplifier (also known as TMA : tower mounted amplifier) If LNA Gain is set at 12dB, its "link budget" contribution in the UL is only 3dB (Friess Formula). Gain 4dB 6dB 8dB 10dB 12dB 14dB Contribution 1.22dB 2dB 2.5dB 3dB 3.2dB 3.4dB
13
40
4 Voice Quality Statistics
Principle
41
Voice Quality indicators are based on calls : Noisy calls are detected and they are characterised with a cause : bad coverage, interference or undefined. On UL path, calls are also characterised through the FER measurements. It is linked to Quality Voice because it shows the percentage of samples during calls with high loss of speech frames, that impact perception of voice.
Computation of Voice Quality statistics

42
Voice Quality statistics are based on non-sliding averages of RXQUAL, RXLEV measurements on both paths and FER measurements on the uplink path The averaging window size is the parameter VQ_AVERAGE
Speech Call SAMFR n SAMFR n+1 SAMFR n+2 SAMFR n+3 SAMFR n+4 SAMFR n+5
Averaging
AV_RXLEV_XL_VQ
CQS
AV_RXQUAL_XL_VQ AV_RXFER_UL_VQ
VQ_AVERAGE: Average window size on measurements to obtain samples for Voice Quality statistics. changeable at the OMC-R on a per BSS basis Default value: 6 SAMFR (6 SACCH Multiframe) AV_RXLEV_UL_VQ = (RxlevUL1++RxlevUL6) / 6 AV_RXLEV_DL_VQ = (RxlevDL1++RxlevDL6) / 6 AV_RXQUAL_UL_VQ = (RxqualUL1++RxqualUL6) / 6 AV_RXQUAL_DL_VQ = (RxqualDL1++RxqualDL4) / 6 AV_RXFER_UL_VQ = (Nb of speech frames wrongly decoded (BFI=1) / Total nb of speech frames of the CQS) CQS = Call Quality Sample = (VQ_AVERAGE x SAMFR) Voice Quality statistics are only performed on traffic channels (TCH) and only related to speech calls. They will be computed on a per TRX basis.
Computation of Voice Quality statistics [cont.]

43
Thresholds used to specify bad quality samples for Voice Quality statistics:
VQ_RXQUAL VQ_RXLEV 7 Quality
bad quality & level bad coverage CQS VQ_RXQUAL bad quality + good level interfered CQS
CQS
0 -110
VQ_RXLEV
Level (dBm)
-47
CQS: Call Quality Sample VQ_RXQUAL: Radio quality threshold to specify bad quality samples for Voice Quality statistics. changeable at the OMC-R on a per BSS basis Default value: 4 VQ_RXLEV: Radio level threshold to specify bad quality samples for Voice Quality statistics. changeable at the OMC-R on a per BSS basis Default value: -95dBm

44
for each speech call and on a per TRX basis, the following counters will start to be collected on speech call beginning (or on incoming intercell or intracell HO):
INTERFERED_UL_SAMPLES = number of samples where:
AV_RXQUAL_UL_VQ > VQ_RXQUAL and AV_RXLEV_UL_VQ > VQ_RXLEV
INTERFERED_DL_SAMPLES = number of samples where:

AV_RXQUAL_DL_VQ > VQ_RXQUAL and AV_RXLEV_DL_VQ > VQ_RXLEV
Quality
bad quality + good level interfered CQS
VQ_RXQUAL CQS 0 -110

Level (dBm)
VQ_RXLEV -47

45
BAD_COVERAGE_UL_SAMPLES = number of samples where :

AV_RXQUAL_UL_VQ > VQ_RXQUAL and AV_RXLEV_UL_VQ <= VQ_RXLEV
BAD_COVERAGE_DL_SAMPLES = number of samples where:

AV_RXQUAL_DL_VQ > VQ_RXQUAL and AV_RXLEV_DL_VQ <= VQ_RXLEV 7
bad quality & level bad coverage CQS
Quality
bad quality + good level interfered CQS
VQ_RXQUAL CQS
0 -110 VQ_RXLEV -47
Level (dBm)
A coverage problem is observed when a significant amount of the traffic of a cell is suffering from both low level and bad quality (RxQual). To confirm the distribution of samples per RXLEV band, should be also considered to know the proportion of calls which are experiencing a low signal level. If a lot of samples of low level and bad quality are observed for only a sub-part of the TRXs (can be one only) then a BTS hardware problem or a problem on the aerials should be suspected. If all the TRXs are experiencing a lot of samples of low level and bad quality then a coverage problem shall be suspected. These RMS indicators are provided on the RNO tool per TRX, per Cell: Matrix of Number of Measurement Results per DL RxQual value and per DL RxLev band RMQLDSAM = RMS_DL_RxQuality_RxLevel_sample Vector of Percentage of Samples per DL RxLev band RMQLDLVDV = RMS_DL_RxLevel_distrib Vector of Percentage of Samples per DL RxQual band RMQLDQUDV = RMS_DL_RxQuality_distrib

46
BAD_QUAL_BAD_FER_UL_SAMPLES = number of samples where :

AV_RXQUAL_UL_VQ > VQ_RXQUAL_VS_RXFER, and AV_RXFER_UL_VQ > VQ_BAD_RXFER (= 3%)
Quality
7
AND AV_RXFER_UL_VQ > VQ_BAD_RXFER
VQ_RXQUAL_VS_RXFER CQS
0 -110 VQ_RXLEV -47
Level (dBm)
The parameters VQ_RXLEV, VQ_RXQUAL, VQ_BAD_RXFER, VQ_GOOD_RXFER and VQ_RXQUAL_VS_RXFER are changeable at the OMC-R side on a per BSS basis. VQ_RXQUAL_VS_RXFER: Radio quality threshold to specify a bad or a good quality CQS correlated to bad or good FER measurements for noisy call statistics (0 to 7) B9 default value = 4 VQ_BAD_RXFER: FER threshold to specify a bad FER CQS for noisy call statistics (0 to 20%) B9 default value = 3% All these parameters are included in the RMS PM Type 31 result files as RMS counters: RMSpc = PAR_VQ_AVERAGE RMSpd = PAR_VQ_RXLEV RMSpe = PAR_VQ_RXQUAL RMSpf = PAR_VQ_RXQUAL_VS_RXFER
Note:The fact that FER measurements are more reliable than RXQUAL ones to assess the VQ is even more true when using Slow Frequency Hopping. In this case, RXQUAL values are not anymore correlated to Voice Quality as perceived by the end user. FER measurements are available for the uplink path only.

47
BAD_QUAL_GOOD_FER_UL_SAMPLES = number of samples where :

AV_RXQUAL_UL_VQ > VQ_RXQUAL_VS_RXFER, and AV_RXFER_UL_VQ <= VQ_GOOD_RXFER (=1%)
Quality
7
AND AV_RXFER_UL_VQ <= VQ_GOOD_RXFER
0 -110 VQ_RXLEV -47
Level (dBm)

48
FAIR_QUAL_BAD_FER_UL_SAMPLES = number of samples where :

AV_RXQUAL_UL_VQ < VQ_RXQUAL_VS_RXFER, and AV_RXFER_UL_VQ > VQ_BAD_RXFER (=3%)
Quality
AND AV_RXFER_UL_VQ > VQ_BAD_RXFER
0 -110 VQ_RXLEV -47
Level (dBm)
VQ RMS Counters
49
VQ_NOISY_UL_INTERFERENCE = RMS10
Number of calls suffering from interference problem on the uplink path
This counter is incremented whenever a call verifies:

100*(INTERFERED_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD
with INTERFERED_UL_SAMPLES = number of times where

AV_RXQUAL_UL_VQ > VQ_RXQUAL and AV_RXLEV_UL_VQ>VQ_RXLEV
At the end of the call (or after an intracell or intercell handover),if 100* (interfered_ul_samples / num_ul_samples) > VQ_INTF_THRESHOLD then the counter VQ_NOISY_UL_INTERFERENCE is incremented VQ_INTF_THRESHOLD: Radio interference threshold to detect noisy calls for Voice Quality statistics Default value = 30%
NUM_UL_SAMPLES: total number of averages calculated on UL measurements during the call on the considered TRX
VQ RMS Counters [cont.]

50
VQ_NOISY_DL_INTERFERENCE = RMS11
Number of calls suffering from interference problem on the downlink path

100*(INTERFERED_DL_SAMPLES / NUM_DL_SAMPLES) > VQ_INTF_THRESHOLD
With INTERFERED_DL_SAMPLES = number of times where

AV_RXQUAL_DL_VQ > VQ_RXQUAL and AV_RXLEV_DL_VQ>VQ_RXLEV
At the end of the call (or after an intracell or intercell handover),if 100* (interfered_dl_samples / num_dl_samples) > VQ_INTF_THRESHOLD then the counter VQ_NOISY_DL_INTERFERENCE is incremented VQ_INTF_THRESHOLD: Radio interference threshold to detect noisy calls for Voice Quality statistics Default value = 30%

51
VQ_NOISY_UL_COVERAGE = RMS12
Number of calls suffering from bad coverage problem on the uplink path

100*(BAD_COVERAGE_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD
with BAD_COVERAGE_UL_SAMPLES = nb of times when

AV_RXQUAL_UL_VQ > VQ_RXQUAL and AV_RXLEV_UL_VQ<= VQ_RXLEV
At the end of the call (or after an intracell or intercell handover), If 100*(bad_coverage_ul_samples / num_ul_samples) > VQ_INTF_THRESHOLD then the counter VQ_NOISY_UL_BAD_COVERAGE is incremented.

52
VQ_NOISY_DL_COVERAGE = RMS13
Number of calls suffering from bad coverage problem on the uplink path

100*(BAD_COVERAGE_DL_SAMPLES / NUM_DL_SAMPLES) > VQ_INTF_THRESHOLD
with BAD_COVERAGE_DL_SAMPLES = nb of times when

AV_RXQUAL_DL_VQ > VQ_RXQUAL and AV_RXLEV_DL_VQ<= VQ_RXLEV
At the end of the call (or after an intracell or intercell handover), If 100*(bad_coverage_dl_samples / num_dl_samples) > VQ_INTF_THRESHOLD then the counter VQ_NOISY_DL_BAD_COVERAGE is incremented.

53
VQ_NOISY_UL_UNDEFINED = RMS14
Number of calls suffering from both problems of interference and bad coverage on the uplink path These calls are not counted in VQ_NOISY_UL_COVERAGE or VQ_NOISY_UL_INTERFERENCE

100*(BAD_COVERAGE_UL_SAMPLES / NUM_UL_SAMPLES) <= VQ_INTF_THRESHOLD and 100*(INTERFERED_UL_SAMPLES / NUM_UL_SAMPLES) <= VQ_INTF_THRESHOLD and 100*(BAD_QUALITY_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD with BAD_QUALITY_UL_SAMPLES = INTERFERED_UL_SAMPLES + BAD_COVERAGE_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ > VQ_RXQUAL

54
VQ_NOISY_DL_UNDEFINED = RMS15
Number of calls suffering from both problems of interference and bad coverage on the downlink path These calls are not counted in VQ_NOISY_DL_COVERAGE or VQ_NOISY_DL_INTERFERENCE

100*(BAD_COVERAGE_DL_SAMPLES / NUM_DL_SAMPLES) <= VQ_INTF_THRESHOLD and 100*(INTERFERED_DL_SAMPLES / NUM_DL_SAMPLES) <= VQ_INTF_THRESHOLD and 100*(BAD_QUALITY_DL_SAMPLES / NUM_DL_SAMPLES) > VQ_INTF_THRESHOLD with BAD_QUALITY_DL_SAMPLES = INTERFERED_DL_SAMPLES + BAD_COVERAGE_DL_SAMPLES = nb of times when AV_RXQUAL_DL_VQ > VQ_RXQUAL

55
VQ_NOISY_UL_BAD_FER = RMS16
Number of calls with bad quality measurements and with bad FER measurements on the uplink path

100*(BAD_QUALITY_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD 100*(BAD_QUAL_BAD_FER_UL_SAMPLES/BAD_QUALITY_UL_SAMPLES)> VQ_FER_THRESHOLD with BAD_QUALITY_UL_SAMPLES = INTERFERED_DL_SAMPLES + BAD_COVERAGE_DL_SAMPLES BAD_QUAL_BAD_FER_UL_SAMPLES = nb of times when AV_RXQUAL_UL_VQ > VQ_RXQUAL_VS_RXFER and AV_RXFER_UL_VQ > VQ_BAD_RXFER
VQ_FER_THRESHOLD: Radio FER threshold to detect calls with bad speech quality for Voice Quality statistics. Default value = 30%

56
VQ_NOISY_UL_GOOD_FER = RMS17
Number of calls with bad quality measurements but with good FER measurements on the uplink path

100*(BAD_QUALITY_UL_SAMPLES / NUM_UL_SAMPLES) > VQ_INTF_THRESHOLD 100*(BAD_QUAL_BAD_FER_UL_SAMPLES/BAD_QUALITY_UL_SAMPLES)< VQ_FER_THRESHOLD
VQ_NOISY_ABNORMAL_BAD_FER = RMS18
Number of calls with fair quality measurements but with bad FER measurements on the uplink path

100*(FAIR_QUAL_BAD_FER_UL_SAMPLES / FAIR_QUALITY_UL_SAMPLES) > VQ_FER_THRESHOLD
Example
57
13
58
5 AMR Statistics
5 AMR Statistics
Measurement of AMR codec usage

59
The goal of the feature is to monitor the usage of each allowed AMR codecs (FR or HR), compared to the link level, in order to help the operator tuning the AMR parameters. As parameters are different for AMR FR and AMR HR, information shall be provided separately for AMR FR and AMR HR The codecs used in UL and in DL can be different, therefore interpretation of results would be easier if results are provided separately for uplink and downlink.
Speech Frame
MR
Bad frame indicator/ AMR codec Channel coding = speech protection Speech coding = speech information
AMR codec usage Compared to RXLEV
Measurement of AMR codec usage in RMS will allow monitoring the proper operation of AMR and the quality of the radio coverage in a cell. It also gives the possibility to tune the AMR parameters. Indeed, statistics about frame erasure rate in uplink and comparison between codec distribution and RXLEV allow to assess the voice quality, and adapt AMR thresholds to the situation of a given cell AMR measurements are available only in Evolium cells. Be careful: Whenever, during the measurement period, the AMR parameters (codec set, thresholds, and hysteresis) are modified, in FR or in HR, the measurement will continue with the new parameters. This will not be reported to the operator Recall: AMR Principle The AMR principle is to have a set of speech codecs and, for any radio conditions, to use the one with the best speech quality. Under good radio conditions, a codec with a high bit-rate is used. Speech is encoded with more information so the quality is better. In the channel coding, only little place is left for redundancy Under poor radio conditions, a codec with a low bit-rate is chosen. Speech is encoded with less information, but this information can be well protected due to redundancy in the channel coding. The BSS adapts dynamically the codec in uplink direction and in downlink direction, taking into account the C/I measured by the BTS (for uplink adaptation) and by the MS (for downlink adaptation). The codec used in uplink and used in downlink can be different: the adaptation is independent in each direction
5 AMR Statistics
Measurement of AMR codec usage [cont.]

60
The measurement of AMR codec usage in RMS is split into 2 sub-features at TRX level:
RMS_I12 : distributions showing speech quality of AMR (number of bad speech frames per codec).
2 vectors shall be defined (AMR FR uplink, AMR HR uplink). Such a result is not available in downlink.
RMS_I13 : Matrixes showing usage of AMR codecs compared to RXLEV (total number of good speech frames per codec gathered in RXLEV intervals).
Four matrixes shall be implemented (AMR FR uplink, AMR FR downlink, AMR HR uplink, AMR HR downlink).
Results are provided at TRX level, as TRXs are not homogeneous within one cell : in terms of transmit power (concentric cells), frequency bands (multiband cells), frequency planning (NH/FH), interference (BCCH, TCH).
5 AMR Statistics
AMR FR UL BFI vector

61
Vector of number of bad speech frames using any AMR FR codec in uplink
4.75 Kbit/s C1
5.15 Kbit/s C2
5.9 Kbit/s C3
6.7 Kbit/s C4
7.4 Kbit/s C5
7.95 Kbit/s C6
10.2 Kbit/s C7
12.2 Kbit/s C8
Vector Maximum
Row_Max
The TRE counts for each AMR FR codec the number of bad speech frames received from the MS in uplink
At the end of the measurement period (i.e. before uploading the results to the BSC), the TRE calculates the usage of each codec as follows : . Where: Nk represents the total number of bad speech frames counted in a TRX for a given AMR codec row_max represents the maximum value of all Nk Ci = 0 indicates that number of measurements = 0 Ck = 254 (FE) means that number of measurements = row_max Ck = 255 is reserved for overflow AMR_FR_UL_BAD= RMS44a that has 8 cells (1 for each FR codec) with the relative number of bad speech frames received in uplink. MAX_AMR_FR_UL_BAD= RMS44b that indicates the maximum number of bad speech frames received in uplink in one FR codec.
5 AMR Statistics
AMR HR UL BFI vector

62
Vector of number of bad speech frames using any AMR HR codec in uplink:
4.75 Kbit/s C1
5.15 Kbit/s C2
5.9 Kbit/s C3
6.7 Kbit/s C4
7.4 Kbit/s C5
Vector Maximum
Row_Max
The TRE counts for each AMR HR codec the number of bad speech frames received from the MS in uplink
AMR_HR_UL_BAD= RMS45a that has 5 cells (1 for each HR codec) with the relative number of bad speech frames received in uplink. MAX_AMR_HR_UL_BAD= RMS45b that indicates the maximum number of bad speech frames received in uplink in one HR codec.
5 AMR Statistics
Example
63
Good/Bad speech frames AMR FR UL

3500000000 3000000000 2500000000 2000000000 1500000000 1000000000 500000000 0 4.75 5.15 5.90 6.70 7.40 7.95 10.20 12.20
FR AMR Codec ( kbi/s )
50 40 30 20 10 0
Bad Frames Good Frames % Bad Frames
Good/Bad speech frames AMR FR UL
4.75
5.15 18022799 6 69295380 38,45%
5.90
6.70
7.40
7.95
10.20
12.20 217875696 4 946906343 43,46%
Good Frames Bad Frames % Bad Frames
48007489 7734495 16,11%
219 93 42,47%
0 0 0,00%
5320 771 14,49%
607487643 162938094 26,82%
0 0 0,00%
5 AMR Statistics
AMR FR XL usage/XL_RXLEV matrix

64
Matrix of total number of speech frames using one AMR FR codec mode in XL for the TRX is reported in level band Y on the uplink
4.75 Kbit/s 5.15 Kbit/s
C12 C22
5.9 Kbit/s
C13 C23
6.7 Kbit/s
C14
7.4 Kbit/s
C15
7.95 Kbit/s
10.2 Kbit/s
12.2 Kbit/s
R_max
B1 B2 B3 B4 RXLEV_XL B5 B6 B7 B8 B9 B10
C11 C21
R_max1 R_max2 R_max3 R_max4 R_max5 R_max6 R_max7 R_max8 C98 C107 C108 R_max9 R_max10
X = DL ou UL RXLEV XL bands are defined as follows: Level B1 is defined by: -47 dBm >= RXLEV > MEAS_STAT_LEV_1 Level B2 is defined by: MEAS_STAT_LEV_1 >= RXLEV > MEAS_STAT_LEV_2 Level B10 is defined by:MEAS_STAT_LEV_9 >= RXLEV >= -110 dBm The number of frames using one specific AMR codec mode is computed over one SACCH multiframe in the following way : In the period of the SACCH multiframe, the TRE counts for each AMR call and for each AMR FR codec the number of correct speech frames received from the MS in uplink, N1 to N8. At reception of the measurement report of a given MS, the results are gathered in the line of the matrix corresponding to reported XL RXLEV. At the end of the measurement period (i.e. before uploading the results to the BSC), the TRE calculates the usage of each codec as follows : Where: Nik represents the total number of speech frames counted in a TRX for AMR codec k, and RXLEV band i row_maxi represents the maximum value of all Nik for line i Cik = 254 (FE) means that number of measurements = row_maxi
5 AMR Statistics
AMR HR XL usage/XL_RXLEV matrix

65
Matrix of total number of speech frames using one AMR HR codec mode in XL for the TRX is reported in level band Y
4.75 Kbit/s 5.15 Kbit/s
C12 C22
5.9 Kbit/s
C13 C23
6.7 Kbit/s
C14
7.4 Kbit/s
C15
R_max
B1 B2 B3 B4 RXLEV_XL B5 B6 B7 B8 B9 B10
C11 C21
R_max1 R_max2 R_max3 R_max4 R_max5 R_max6 R_max7 R_max8 R_max9
C105
R_max10
X = UL ou DL RXLEV XL bands are defined as follows: Level B1 is defined by: -47 dBm >= RXLEV > MEAS_STAT_LEV_1 Level B2 is defined by: MEAS_STAT_LEV_1 >= RXLEV > MEAS_STAT_LEV_2 Level B10 is defined by:MEAS_STAT_LEV_9 >= RXLEV >= -110 dBm The number of frames using one specific AMR codec mode is computed over one SACCH multiframe in the following way : In the period of the SACCH multiframe, the TRE counts for each AMR call and for each AMR HR codec the number of correct speech frames received from the MS in uplink, N1 to N8. At reception of the measurement report of a given MS, the results are gathered in the line of the matrix corresponding to reported XL RXLEV. At the end of the measurement period (i.e. before uploading the results to the BSC), the TRE calculates the usage of each codec as follows : Where: Nik represents the total number of speech frames counted in a TRX for AMR codec k, and RXLEV band i row_maxi represents the maximum value of all Nik for line i Cik = 254 (FE) means that number of measurements = row_maxi
5 AMR Statistics
Example
66
Correct speech frames per AMR FR codec and RxLevel in downlink

FR (AMR) (kbi/s) 12.20 10.20
[-1850685312,-1450834080] ]-1450834080,-1050982848] ]-1050982848,-651131616]
7.95
]-651131616,-251280384]
7.40
]-251280384, 148570848]
6.70 5.90 5.15 4.75 ]-88,-83] ]-83,-78] ]-78,-73] [-110,-104] ]-99,-94] ]-94,-88] ]-73,-67] ]-67,-62] ]-104,-99] ]-62,-47]
] 148570848, 548422080] ] 548422080, 948273312] ] 948273312, 1348124544]

X Out of Range
Rxlev
5 AMR Statistics
Exercise
67
At the end of the measurement period, we have following results:

4.75 Kbit/s 150 5.15 Kbit/s 0 5.9 Kbit/s 1 6.7 Kbit/s 0 7.4 Kbit/s 214 7.95 Kbit/s 0 10.2 Kbit/s 300 12.2 Kbit/s 0
what will be reported to the BSC?

C1 127 C2 0 C3 1 C4 0 C5 181 C6 0 C7 254 C8 0 MAX 300
13
68
6 TA Statistics
6 TA Statistics
Objective
69
The aim of this feature is to provide statistics information on TA, in order to understand geographical traffic distribution in a cell and to identify resurgences and hot spots.
TA Max value: 63
Speech Frame
MR
TA distribution Average RXLEV per TA band Min value: 0 Average RXQUAL per TA band
In B8, two counters only are defined for Timing Advance (TA):

PERC_TA_GT_TA_STAT MAX_TA
PERC_TA_GT_TA_STAT: Percentage of measurement results reported with a TA value higher then the TA_STAT parameter.
MAX_TA: Maximum value of TA among all TA values reported in the measurement results used for RMS. The aim of this feature is to provide statistics information on TA, in order to understand geographical traffic distribution in a cell and to identify resurgences and hot spots.
B8 RMS statistics are still available in B9.
Statistics on timing advance are available only in Evolium cells.
6 TA Statistics
Timing advance distribution

70
The distribution of number of measurement reports for which the value of timing advance is in TA band X
B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 Vector Max
Row_M ax
C1
C2
C3
C4
C5
C6
C7
C8
C9
C10
There are 10 TA bands which are defined through 9 thresholds parameters, tunable on a cell basis, using the RMS_parameters_template
0 C1
C1
TA Band B1 is defined by: 0 <= TA < Meas_STAT_TA_1 TA Band B2 is defined by: MEAS_STAT_TA_1 <= TA < MEAS_STAT_TA_2 TA Band B10 is defined by: MEAS_STAT_TA_9 <= TA < 63 The TRE counts for each TA band the number of measurement results, N1 to N10. To save on the memory resources, these counters are sent to the BSC in a coded format. At the end of counting period, the coded values are computed as follow:
Where: Nk represents the real number of measurements row_max represents the maximum value of all Ni Ck = 0 indicates that number of measurements = 0 Ck = 254 (FE) means that number of measurements = row_max Ck = 255 is reserved for overflow
6 TA Statistics
Average RXLEV per TA band counters

71
Two vectors (one for uplink, and one for downlink) of 10 elements of 2 bytes, containing the average value of RXLEV per TA band.
B1
B2
B3
B4
B5
B6
B7
B8
B9
B10
Vector Max
Row_M ax
C1
C2
C3
C4
C5
C6
C7
C8
C9
C10
The 10 TA bands are defined through threshold parameter MEAS_STAT_TA_1 to 9 C1..C10: averaged value of RXLEV
6 TA Statistics
Average RXQUAL per TA band counters

72
Two vectors (one for uplink, and one for downlink) of 10 elements of 2 bytes, containing the average value of RXQUAL per TA band.
B1
B2
B3
B4
B5
B6
B7
B8
B9
B10
Vector Max
Row_M ax
C1
C2
C3
C4
C5
C6
C7
C8
C9
C10
The 10 TA bands are defined through threshold parameter MEAS_STAT_TA_1 to 9 C1..C10: averaged value of RXQUAL
6 TA Statistics
Example
73
Number of samples per Timing Advance band

50000 45000 40000 35000 30000 25000 20000 15000 10000 5000 0 [0,7[ [7,13[ [13,19[ [19,25[ [25,31[ [31,37[ [37,43[ [43,49[ [49,55[ [55,63] TA band ( 533m ) 30 20 10 0 60 50 40
Nb Samples % Samples dist
13
74
End of Module Radio measurements statistics Data
14

Module 4 RMS Based Radio Network Optimization
Blank Page
Optimization & FP using RMS RMS Based Radio Network Optimization 14
Objectives
To be able to use RMS data to detect the origin of a bad QoS and optimize consequently the radio network parameters
Objectives [cont.]
Table of Contents

1 2 3 4 5 6 7 RMS Activation Global analysis of the RMS results Detailed analysis of the worst cell Detection of Coverage problems using RMS Analysis of coverage problems using RMS Detection of Interference problems using RMS Analysis of Interference problems using RMS
Page 7 9 18 32 41 51 60

Page
Optimization & FP using RMS RMS Based Radio Network Optimization
14
1 RMS Activation
1 RMS Activation
RMS measurements
RMS counters (type 31) should be activated for the OMC, as PMC, during a larger period that will include the busy hours. Check if the RMS measurement is enough Are the RMS measurements enough on the cells below?
Cell Cell_A Cell_B Cell_C RMS_meas_results_total 920785 156743 13776 RTCH_Erlang_BH 10.7 3.4 0.02
Cell_C do not handle enough calls. It will lead to an unreliability of the RMS results. Avoid unreliability by studying cells with RTCH_Erlang_BH > 0.1 Erl.
Template 1 (with default values) should be used at the first analysis.
14
2 Global analysis of the RMS results
Case study
10
Extract the main RMS unit indicators and the main QoS indicators for whole working zone and two frequency bands Objective: to compare the 2 bands If the network in analysis is a dual band network The Attached file shows the main RMS indicators, concerning radio link quality and voice quality Working Zone:49 cells; an urban area where the classical band is 1800 band
Microsoft Office Excel Worksheet
In this table, the figures in gray are not valid and the figures in red are the most important ones
Case study
11
Which band takes more traffic?

1800 cells take almost three times more traffic (in terms of TCH seizures and measurements) than the 900 cells: more capacity in 1800, and preferred band HO go from 900 to 1800
Compare the received level on both band?

The average received level on downlink and uplink path on 900 cells is lower than on 1800 cells: around 7.5 dB lower in downlink and 3 dB lower in uplink.
Case study
12
Does this lower received level in 900 cells bring quality problems on the downlink path ?
It does not bring quality problems on the downlink path: on 1800 and 900 cells, average DL RxQual is fair (considering a bad average RxQual starting at 0.5) and noisy call rate on downlink path is rather low: 4.01 % on 1800 cells, 2.59 % on 900 cells (indicating that quality problems on downlink path are perhaps more in 1800 cells, perhaps due to a tighter frequency planning (ref. also to distribution causes of noisy calls on DL path)).
What about the Uplink?

On the contrary, on the uplink path, lower received level in 900 cells seem quite problematic The average UL RxQual is higher than 0.5 in 900 cells, twice the value of average UL RxQual in 1800 cells.
Case study
13
Check the Consecutive Frame Erasure on both band ?

The average Consecutive Frame Erasure is 0.24 in 900 cells, 0.14 in 1800cells
Check the noisy call rate on the Uplink?
The noisy call rate on uplink path is 6.64% in 900 cells, more than twice the value in 1800 cells and the main cause of this UL noisy calls in 900 cells is bad coverage
Case study
14
Is there any voice quality problem ?

70% of these UL noisy calls in 900 cells suffer from bad Frame Erasure Rate (4.67% compared to 6.64%), indicating probable voice quality problems (also shown by the high UL Consecutive Frame Erasure).
What about abnormal bad Frame Erasure Rate ?
Abnormal bad Frame Erasure Rate is more than 40% in 900 cells, whereas it is around 25% in 1800 cells (however, these high values are quite suspicious, perhaps due to a wrong tuning of the voice quality counters, i.e., the threshold on FER should be put higher).
Case study
15
Can we explain such UL quality problems by hardware or installation problem at BTS sites?
The good values of average path balance (close to 0 dB) in 900 cells and 1800 cells seem to show that there is neither hardware nor installation problem at BTS sites that could explain such UL quality problems however, to be sure on that, a deeper analysis on a per TRX basis on each cell should be Performed.
The power control settings does not seem to be suspicious. Is it true ?

The power control settings does not seem to be suspicious as it can be seen that average MS and BTS power in 900 cells are rather high, proving that the powers must be often at maximum level, so as to compensate coverage problems (BTS Power Control is also often always ? - disabled)
Case study
16
Check the average Radio Link Counter ?

The average Radio Link Counter could also be applied to characterize uplink radio link quality in 900 cells. However, the corresponding thresholds in the RMS templates are wrongly tuned, giving always the same value for this average.
Can you explain such UL quality problems in 900 band ?

One explanation for these UL quality problems in 900 band could be that mobiles in the 900 bands are the ones that could not be captured by 1800 cells. So these mobiles have naturally low received levels (especially when 900 and 1800 cells are co-located) and are more likely to suffer from interference (in case of coverage reappearance). Timing advance indicators could also show that mobiles in 900 cells are further from the sites, compared to mobiles in 1800 cells. More investigations can be performed while selecting the worst cell in 900 band and analyzing deeper RMS data for this cell.
Case study
17
Check the main QoS indicators, any remark?

When looking at the main QoS indicators on a per BSC and a per band basis, it can be clearly seen that the UL quality problems in 900 cells detected through RMS has a major impact on QoS figures in this band
14
18
3 Detailed analysis of the worst cell
Top Worst reports

19
Next step is a global analysis on the network/working zone should be performed with the Top Worst RNO/NPO reports in order to detect the main problems in terms of radio link quality and voice quality
Alc_warning_top_worst_rms_radio_link Alc_warning_top_worst_rms_ul_voice_quality Alc_warning_top_worst_rms_dl_voice_quality
Investigate the UL quality problems:

the worst cell is to be found in the UL voice quality report and also in some specific UL measurements as Consecutive Frame Erasure and Radio Link Counter, that can be found in the radio link report.
From Alc_warning_top_worst_rms_radio_link, the worst cells can be filtered by: Average RxLevel (UL/DL) Average RxQuality (UL/DL) Average Power (UL/DL) Average PathBalance Average Uplink RadioLinkCounter Average Timing Advance Average Uplink Consecutive Frame Erasure From Alc_warning_top_worst_rms_ul/dl_voice_quality, the worst cells can be detected by: Split of uplink/downlink noisy calls causes Bad Coverage Interference Undefined
Worst cells
20
Worst cells according to UL voice quality Lets take the next example :
UL noisy call rate 12,8% 11,7% 10,3% due to bad coverage 10,55% 4,72% 7,93% due to with bad Average average interference FER CFE RLC < 2% 6,83% < 2% 10,72% 7,39% 8,89% 0,32 0,3 < 0.3 74,8 74,5 75
CI 11075 12175 13463
It is also important that these figures are based on sufficient calls, so as to give reliable statistics. In the case of the three cells above, each of them had more than 5000 calls during the RMS job. It is seen as quite sufficient to get reliable results.
The worst cell

21
Which cell is the worst?

it can already been seen that cell 11075 and 13643 suffers from serious coverage problems (perhaps due to some coverage holes) whereas cell 12175 seems to suffer more from interference (for example due to coverage re-appearance). From the QoS point of view (see comments below), it seems that it is the cell 11075 that is the worst cell:
others cells could be found, for example if main criteria was Consecutive Frame Erasure: For example, cell CI 13647 shows the highest average CFE (0.42) but calls do not suffer from bad RxQuality: they suffer only from bad frame Erasure Rate. Thats why, for this cell, UL noisy call rate is low (below 5 %) but calls suffering from abnormal bad FER (bad FER while RxQual is fair) are a lot: more than half of the calls (exactly 54 %) suffer from bad FER. It is not quite clear in which radio conditions such results can be found, and it probably indicates a TRX failure. Correlate with main QoS: In terms of call drop rate, cells 11075 and 12175 are respectively ranked as the second and the fourth worst cell in the BSC (with call drop rate equal to respectively 3.48% and 2.95%, with a large part due to radio problems) In terms of call setup success rate, cells 11075 and 12175 are respectively ranked as the second and the eighth worst cell in the BSC (with a call setup success rate equal to respectively 95.24% and 96.11%). In terms of incoming HO unsuccess rate, cell 11075 is ranked as the seventh worst cell (with the highest incoming handover failure rate, equal to 7.72%). In terms of outgoing HO unsuccess rate, these cells are not seen in the 10 worst cells. This can be seen as normal as radio problems in one cell do not really impact its outgoing HO success rate. So, it seems more valuable to investigate RMS on the cell 11075, so as to try to improve not only the radio link quality in this cell but also the quality of service provided to subscribers (another important criteria to take into account would also be the amount of traffic in this cell compared to the total traffic in the BSC, but this was not done in this example).
UL RxLevel distribution
22
The worst cell detected on the previous example (cell 11075) is a 900 cell with only one TRX. Interpret the UL Rxlev distribution of this cell?
it can be seen that a lot of measurements show low received level on uplink path in this cell: almost 50% of the measurements show an uplink received level lower than 90 dBm.
Uplink RxLevel distribution
40 35 30 25 20 15 10 5 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm )
% RxLev distrib
Average UL RxQuality per UL RxLevel

23
Does such bad radio conditions (low received level) impact the UL Quality on that cell?
These low UL received levels correspond to high RxQual: 0.8 between 91 dBm and 96 dBm, 2.7 between 97 dBm and 103 dBm, 5.2 between 104 dBm and 110 dBm
Uplink RxQuality per RxLevel

6 5 4 3 60000 2 1 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 40000 20000 0 140000 120000 100000 80000
RxQuality Avg Nb Lev Samples
Uplink CFE per Rxlev

24
Does such bad radio conditions (low received level) impact the voice quality on that cell?
Yes; The average CFE is higher than 1 between 96 dBm and 103 dBm and higher than 2 between 104 dBm and 110 dBm and this concerns 18% of the measurements.
Uplink CFE per RxLevel

140000 120000 100000 80000 3 60000 40000 20000 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 2 1 0 6 5 4
Nb Lev Samples CFE Avg RxQuality Avg
Uplink CFE per Rxlev

25
How can you explain such bad received levels?

So, these low UL received levels are not acceptable, from the radio and voice quality point of view. It can be deduced that these low UL received levels are not to be expected (like in an open area, with sensitivity limited environment) but they are due to coverage hole (bad network design) and/or interference (bad frequency planning).
Uplink TA per Rxlev

26
Is that coverage problem at cell border?

Uplink Timing Advance per RxLevel
1.4 1.2 1 0.8 0.6 0.4 0.2 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 140000 120000 100000 80000 60000 40000 20000 0
TA Avg Nb Lev Samples
So, these low UL received levels are not acceptable, from the radio and voice quality point of view. It can be deduced that these low UL received levels are not to be expected (like in an open area, with sensitivity limited environment) but they are due to coverage hole (bad network design) and/or interference (bad frequency planning). This means that the coverage and/or interference problem should not be at cell border (cell environment is not dense and intersite distance must be more than 1 kilometer) but they are more likely to be in the service area of the cell
Uplink TA per RxQual

27
To confirm that; check the Average Timing Advance per UL RxQuality graph?
it can be seen that the highest Timing Advance is obtained at RxQual = 4, indicating that the quality should be rather fair at cell border. On the contrary, RxQual higher than 4 correspond to lower average Timing advance, indicating that coverage and/or interference problems are not at cell border
Uplink Timing Advance per RxQuality

1.4 1.2 1 0.8 150000 0.6 0.4 0.2 0 0 1 2 3 4 5 6 7 RxQuality ( nb ) 100000 50000 0 300000 250000 200000
TA Avg Nb Samples
Uplink power per Rxlev & Rxqual

28
Check if power control does not reduce too much MS power, leading to this quality problems at low received levels on the uplink path
Uplink Power per RxLevel
35 30 25 20 15 10 5 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 140000 120000 100000 80000 60000 40000 20000 0
MS Power Avg Nb Lev Samples
Uplink Power per RxQuality

33 32.5 32 31.5 31 30.5 30 29.5 29 28.5 28 0 1 2 3 4 5 6 7 RxQuality ( nb ) 0 100000 50000 150000 250000 200000 300000
MS Power Avg
Nb Qual
At this level, it can be interesting to look at the power control behavior, to check if it does not reduce too much MS power, leading to this quality problems at low received levels on the uplink path. For this to be possible, it is interesting to look at the Average MS power according to UL RxLevel graph and the Average MS power according to UL RxQuality grap
Uplink power per Rxlev & Rxqual

29
Interpret the 2 previous graphs?

These graphs show that the MS power is not at maximum level at the lowest received level (32 dBm) and at highest RxQual (32.4 dBm and 32.2 dBm at respectively RXQUAL=5 and 6). The case of RxQual = 7 is particular for the MS power because it is often linked to the Minimum Coupling loss. So, it could be interesting to modify power control settings, so that it ensures maximum MS power in the bad radio conditions. However, the power control settings is already very conservative (see comments below)
Upper and lower thresholds are high (upper at 80 dBm and lower at 90 dBm). POW_INC_FACTOR and POW_RED_FACTOR (Power increase and reduction factor) have default tuning (0.8 for the increase, 0.5 for the reduction). POW_INC_STEP_SIZE and POW_RED_STEP_SIZE (Power increase and reduction step size in case of only quality problems) are equal respectively to 6 dB and 2 dB. One could imagine to make the power control more reactive while putting POW_INC_FACTOR to 1.0, so that the MS power is quicker increase when quality and level problems occur. However, power control fine tuning does not seem to be the sufficient solution for this problem. The good solution would be to identify the coverage hole where UL interference occur (one could for example, imagine a high building where indoor is not well covered and interfered by many cells at high floors).
C/I overlap per neighbour cells

30
So as to identify the possible interferers on cell 11075, it can be quite interesting to study the C/I overlap according to neighbour cells
CI overlap per Neighbour cells
40 35 30 25 20 15 10 5 0
11 26 7 12 17 3 ,5 5) 11 26 6 11 07 3 (1 3, 54 8) 11 56 6 40 15 6 11 22 1 40 15 2 (3 9, 25 ) (1 4, 41 ) (1 0, 59 1) 11 26 2 11 26 1 (9 ,6 8) (1 1, 25 ) (1 4, 52 2) (1 5, 55 0) (1 2, 29 ) (1 3, 31 ) (8
300000 250000 200000 150000 100000 50000 0
C/I overlap Nb C/I Samples
Neighbour cells ( nb )
The C/I overlap correspond to the average C/I computed from C/I distribution. It is called overlap because more than interference, it shows the overlap between cells, that may or cannot interfere (for example, co-located 900 and 1800 cells will have a very low C/I but it does not mean they interfere each other, it only means that they have a strong overlap between them).
C/I overlap per neighbour cells

31
Are there possible interferers?

From the previous graph, it is possible to see that several 900 cells have large overlap with 900 cell 11075 (leading to possible interference). However, these cells do not show very low C/I (it is higher than 12 dB) but this could be due to the C/I thresholds in the RMS template: indeed this one does not really allow precise value at low C/I. Moreover, as these cells will low C/I are not identified as neighbour cells by RNO (they are not expressed in CI but in (BSIC, BCC)), a search should be performed in the vicinity of the cell 11075, so as to identify these possible interferers
The C/I overlap correspond to the average C/I computed from C/I distribution. It is called overlap because more than interference, it shows the overlap between cells, that may or cannot interfere (for example, co-located 900 and 1800 cells will have a very low C/I but it does not mean they interfere each other, it only means that they have a strong overlap between them).
14
32
4 Detection of Coverage problems using RMS
Introduction
33
Coverage problems are often detected through RxLevel and RxQuality measurements coverage problems are linked to many calls with low RxLevel and bad RxQuality measurements In this sub-chapter, it will be shown how coverage problems in a network can be detected through the NPO reports:
RMS_DL_Voice_Quality, RMS_UL_Voice_Quality and RMS_Radio_Link_Quality
The analysis of a coverage problem on one particular cell can be performed based on the correlation of RxLevel, RxQuality and Timing Advance measurements.
The case of good low RxLevel and bad RxQuality is identified as being interference problems
Radio link reports

34
Radio link reports (RMS_Radio_Link_Quality reports) allow the viewing of for example the worst cells in one area according to the basic measurement RxLevel, RxQuality and Timing Advance. Average RxLevel :
Average RxLevel
N1_City_Mall_1 (LAC = 203, CI = 23551) 0 Parow_North_3 (LAC = 203, CI = 29833) Parow_North_2 (LAC = 203, CI = 29832) Tygerberg_Hospital_ 3 (LAC = 203, CI = 60593) Tygerberg_Hospital_ 2 (LAC = 203, CI = 60592) Welgedacht_2 (LAC = 203, CI = 24272) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100 Welgedacht_1 (LAC = 203, CI = 24271) Parow_North_1 (LAC = 203, CI = 29831) Welgemoed (LAC = 203, CI = 24040) Parow_West_1 (LAC = 203, CI = 26761)
DL RxLevel avg UL RxLevel avg
In theses graphs the cells are sorted according to the lowest Rxlevel, worst RxQuality and highest Timing advance.
0,8 0,6 0,4
0,2 0
1,2 1
3,5 3 2,5 2 1,5 1 0,5 0 Welgedacht_2 (LAC = 203, CI = 24272) Welgedacht_1 (LAC = 203, CI = 24271) Parow_North_3 (LAC = 203, CI = 29833) Parow_1 (LAC = 203, CI = 23511) De_Tijger_2 (LAC = 203, CI = 65092) Parow_North_1 (LAC = 203, CI = 29831) De_Tijger_3 (LAC = 203, CI = 65093) Parow_North_2 (LAC = 203, CI = 29832) N1_City_Mall_1 (LAC = 203, CI = 23551) De_Tijger_1 (LAC = 203, CI = 65091)
N1_City_Mall_1 (LAC = 203, CI = 23551) De_Tijger_1 (LAC = 203, CI = 65091)
Average RxQuality
Radio link reports
Average Timing Advance

Louis_Leipoldt_3 (LAC = 203, CI = 60613) N1_City_Mall_3 (LAC = 203, CI = 23553) Parow_North_1 (LAC = 203, CI = 29831) Parow_West_2 (LAC = 203, CI = 26762) De_Tijger_2 (LAC = 203, CI = 65092)
Average RxQuality
TA avg
Karl_Bremmer_2 (LAC = 203, CI = 60602)
Louis_Leipoldt_2 (LAC = 203, CI = 60612)
Parow_North_3 (LAC = 203, CI = 29833)
UL RxQual avg
DL RxQual avg
14
35
Radio link reports

36
Using the previous graphs, on which cell can we suspect a coverage problem?
Parrow_North_3 shows a low average UL and DL received level (-86.27 dBm in UL, -79.93 in DL), a high average Timing advance (2.64) and a rather bad average UL and DL Quality (0.71 in UL, 0.67 in DL)
On the contrary, Welgedacht_2 has the lowest average UL received level (-87.12 dBm) and the highest average Timing advance (3.32). But it does no show bad RxQual, neither in UL path, nor in DL path. So, even if this cell has a wide coverage, there is no reason why coverage should be improved
Voice Quality reports

37
Voice Quality reports (RMS_DL_Voice_Quality and RMS_UL_Voice_Quality reports) allow the viewing of for example the worst cells in one area according to some call statistics that correlate RxLevel, RxQuality and FER In the graphs below the cells are sorted according to the highest rate of noisy calls (in UL and DL path) and the highest rate of UL noisy calls with bad FER.
900 800 700 600 500 400 300 200 100 0

100% 20% 40% 60% 80% 0%
De_Tijger_2 (LAC = 203, CI = 65092)

De_Tijger_2 (LAC = 203, CI = 65092)
De_Tijger_3 (LAC = 203, CI = 65093)

De_Tijger_3 (LAC = 203, CI = 65093)
Uplink noisy calls with bad FER

Split of Uplink noisy calls causes
Parow_3 (LAC = 203, CI = 23513)
Parow_3 (LAC = 203, CI = 23513)
Parow_West_2 (LAC = 203, CI = 26762)

Parow_2 (LAC = 203, CI = 23512)
Parow_2 (LAC = 203, CI = 23512)
Split of uplink noisy calls causes
Uplink noisy calls with bad FER
Parow_West_2 (LAC = 203, CI = 26762) N1_City_Mall_2 (LAC = 203, CI = 23552) Parow_West_3 (LAC = 203, CI = 26763) 8 7 6 5 4 3 2 1 0
N1_City_Mall_2 (LAC = 203, CI = 23552)
10
12
% Bad Coverage
% Interference
% noisy call
% Undefined
Bad FER % Bad FER
14
38
3500 3000 2500 2000 1500 1000 500 0
1200 1000 800 600 400 200 0 Tygerberg_Hospit al_2 (LAC = 203, CI = 60592) N1_City_Mall_1 (LAC = 203, CI = 23551) N1_City_Mall_2 (LAC = 203, CI = 23552)
Tygerberg_Hospital _2 (LAC = 203, CI = 60592) N1_City_Mall_1 (LAC = 203, CI = 23551) Louis_Leipoldt_3 (LAC = 203, CI = 60613)
Parow_North_3 (LAC = 203, CI = 29833) De_Tijger_2 (LAC = 203, CI = 65092) Parow_North_2 (LAC = 203, CI = 29832) Loevenstein (LAC = 203, CI = 26750) N1_City_Mall_3 (LAC = 203, CI = 23553) Louis_Leipoldt_2 (LAC = 203, CI = 60612) Welgedacht_2 (LAC = 203, CI = 24272) 5 4,5 4 3,5 3 2,5 2 1,5 1 0,5 0
De_Tijger_2 (LAC = 203, CI = 65092)
Split of downlink noisy calls causes
N1_City_Mall_3 (LAC = 203, CI = 23553)
Downlink noisy calls with bad coverage

Parow_North_1 (LAC = 203, CI = 29831) Louis_Leipoldt_2 (LAC = 203, CI = 60612)
Downlink noisy calls with bad coverage
% Bad coverage Bad coverage
Loevenstein (LAC = 203, CI = 26750)
Karl_Bremmer_2 (LAC = 203, CI = 60602)
Parow_North_2 (LAC = 203, CI = 29832) 16 14 12 10 8 6 4 2 0
Undefined
Bad coverage Interference
% noisy call
14
39

40
What can you deduce from previous graphs regarding Parrow_North_3?

In these graphs, it can be seen that the cell Parrow_North_3 has one the highest UL noisy call rate (with a value of 9.6 %, this means that 9.6 % of the calls in this cell suffer from bad UL radio link quality). This high UL noisy call rate is due in majority (88% of the cases) to bad coverage (that is low UL RxLevel and bad UL RxQuality). These UL noisy calls are also suffering from bad FER : 7.09 % of the calls (out of the 9.6% of noisy calls) show 30% of call samples with a FER above 3%.
On the downlink path, it can be seen that no cells present a majority of noisy calls due to bad coverage: for all the cells with highest DL noisy call rate, DL noisy calls come mainly from interference problems. However, if the cells are sorted according to the highest DL noisy call rate due to bad coverage, it can be seen that Parrow_North_3 is in good position : 3.81% of the calls in this cell are noisy calls due to bad coverage on the downlink path. The fact that the bad coverage issue can be detected both on the UL and DL path makes clear that the problem should come from a coverage hole in the service area or at the edge of the cell. Otherwise (if the detection can be done only in UL or DL path), the bad coverage issue could also be linked due to path balance problems
14
41
5 Analysis of coverage problems using RMS
Introduction
42
The coverage problems can be characterized according to the way it has been detected: If the coverage problem has been detected only on one path, especially the UL one, a path balance problem can be suspected If the coverage problem has been detected both in the UL and DL path and for all the TRXs of the cells, the problem can be seen as a coverage hole A coverage hole must be analyzed and localized through TA measurements, Rxlevel and RxQuality measurements Mobile with a high TA are not always suffering from bad radio link quality It can happen that due to some field topology aspects, mobiles close to the site are suffering from coverage problems
The analysis of coverage hole can thus follow two axis: one concerning the coverage hole at the border of the cell and another concerning the coverage hole within the service area of the cell.
Coverage hole at the border of the cell

43
Such coverage issue can be characterized through the viewing of the average timing advance according to Rxlevel and RxQuality measurements

44
Interpret the previous graph?

a rough idea of the localization of the coverage limit can be obtained. The matrix above shows that the cell border corresponds to very low Rxlev and to possibly high RxQual on the UL path. It also corresponds to a Timing advance around 11 units (that is around 6 kilometers from the site)
In practice, this matrix must be associated with other representations, in order to get a complete and precise picture of some possible problems of coverage hole at the border of one cell.

45
Interpret the distribution below?

12 10 8 6 4 2 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 400000 350000 300000 250000 200000 150000 100000 50000 0
TA Avg Nb Lev Samples
The distribution of average timing advance value and number of measurements according to the Rxlevel intervals show that a majority of measurements are done at low received level (below 91 dBm) and that it corresponds to high average timing advance (above 7 units). 20 % of the measurements are done at the lowest Rxlevel interval and the highest timing advance.

46

Uplink TA and RxQual per RxLev
3 2,5 2 1,5 1 0,5 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 12 10 8 6 4 2 0
RxQuality Avg TA Avg
These 20% of measurements are linked to a very bad RxQual in average : 2.4. Whereas the measurement with an Rxlevel in the next interval does not suffer from bad RxQual: the average is 0.4. This means clearly that these 20% of measurements are no longer in the service area of the cell : they correspond to a coverage hole at the border of the cell. This can be due to lack of overlap between the cells.
Coverage hole in the service area of the cell

47
Interpret the graph below?
In this graph, the average timing advance values on the UL path are very distributed and they are very close to each others (often between 0.5 and 1.5 units, that is around 500 meters). The possible existence of a coverage hole with the service area must be checked through the other representation of Timing Advance with RxLev and RxQual measurements

48

1,4 1,2 1 0,8 0,6 0,4 0,2 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 140000 120000 100000 80000
TA Avg
60000 40000 20000 0
Nb Lev Samples
In this graph, almost 50 % of the measurements show an RxLev below 91 dBm with an average timing advance always around 1.2 units (around 600 meters).

49

Uplink TA and RxQual per RxLev
6 5 4 3 0,6 2 1 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 0,4 0,2 0 1,4 1,2 1 0,8
These measurements correspond to high average RxQual values : 0.8 between 91 and 96 dBm, 2.7 between 97 and 103 dBm and 5.2 between 104 and 110 dBm As the timing advance is very close between these different radio conditions, one can say that it is not linked to cell border : these bad radio conditions are met within the cell

50

Downlink TA and RxQual per RxLev
2,5 2 1,5 1 0,5 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 1,4 1,2 1 0,8
RxQuality Avg
0,6 0,4 0,2 0
TA Avg
This graph confirms the fact that the converge problem is within the service area of the cell. In deed; in the DL path the worst radio conditions (lowest Rxlevel, worst RxQual) is not linked to the highest value of average timing advance
Explain the coverage hole in the service area of a cell?

It can be explained by specific field topology aspects. In urban and dense urban environment, it is often linked to bad coverage of indoor or deep indoor and if too critical, it can require dedicated indoor designs
14
51
6 Detection of Interference problems using RMS
Introduction
52
Interference problems are often detected through RxLevel and RxQuality measurements. Interference problems are linked to many calls with high RxLevel and bad RxQuality measurements.
Radio link Reports

53
Radio link reports (RMS_Radio_Link_Quality reports) allow the viewing the worst cells in one area according to the basic measurement RxLevel, RxQuality and Timing Advance In the graphs below the cells are sorted according to the highest Rxlevel, worst RxQuality and lowest Timing advance. Average RxLevel :
Average RxLevel
0 -10 -20 -30 -40 -50 -60 -70 -80 -90 -100 CALin CAIm2 CAIm1 CAV1 CAVD3 CAX2 CAIO2 CBRE1 CAVD1 CAV2 CAVD2 CAX2d CAIO2d CBRE3 CAIO1 CBRE2 CAX1 CAIO1d CAX1d
DL RxLev avg UL RxLev avg
Radio link Reports

54
Average RxQuality :
Average RxQuality
1.8 1.6 1.4 1.2 1 0.8 0.6 0.4 0.2 0
1 1d 2 2d E1 C AI O 1d C AI O 2d C AI m 2 2 D 1 1 D 2 1 D 3 E2 E3 2 1 C AI m C AI O C AI O C BR C BR C BR C AV C AV C AV C AL in AX C AV C AV AX C C AX AX
DL RxQual avg UL RxQual avg

2.5 2 1.5 1 0.5 0
1 2 1d 2d D 3 D 1 D 2 1d 2d 1 2 1 2 C AL i C AV C AV C AX C AX AI m AI m AI O AI O C AI O C AI O C BR C BR C AX C AX C BR C AV C AV C AV E2 E1 E3 n 1 2
TA avg
Radio link Reports

55
Using the previous graphs, on which cell can you suspect an interference problem?
In these graphs, it can be seen that CAV1 has a rather of bad average UL and DL Quality (1.57 in UL, 0.78 in DL) and one of the highest average UL and DL received level (-81.05 dBm in UL, -69.5 in DL). According this and the Timing Advance (1) we can suspect an interference problem.
What about CAX1?

CAX1 shows too a rather of bad average UL and DL Quality (1.31 in UL, 0.97 in DL), but this cell have a low average UL received level (-89.49 dBm). On this cell we can suspect a coverage problem.
Voice Quality Reports

56
Voice Quality reports (RMS_DL_Voice_Quality and RMS_UL_Voice_Quality reports) allow the viewing the worst cells in one area according to some call statistics that correlate
RxLevel, RxQuality and FER (only on the UL path) measurements
In the graphs below the cells are sorted according to the highest rate of noisy calls (in UL and DL path) and the highest rate of UL noisy calls with bad FER.

57
Split of Uplink noisy calls causes

Split of uplink noisy calls causes
100.00% 90.00% 80.00% 70.00% 60.00% 50.00% 40.00% 30.00% 20.00% 10.00% 0.00%
2 CB R CB R 1 CA IO 1 2d 1d E1 2d D2 E3 AI O 2 AX E2 1d 1 1 1 n 2 2 3 AV D AV D AI m CA V AI m AL i AV AX AX AI O AI O BR AV C C C AX
16 14 12 10 8 6 4 2 0
Undefined Bad Coverage Interference % noisy call
Uplink noisy calls with interference

Uplink noisy calls with interference
180 160 140 120 100 80 60 40 20 0 2.5 2 1.5
Interference
1 0.5 0
% Interference
1d
2d
1d
2d AI O C
D3
D1
D2
E1
E3
E2
C AX
C AX
CA Im
CA X
C AX
C AL i
CA IO
CB R
BR
BR
AV
AV
AV
AI m
AV
AV
AI O
AI O

58

100.00% 90.00% 80.00% 70.00% 60.00% 50.00% 40.00% 30.00% 20.00% 10.00% 0.00% 25 20 15 10 5 0
Undefined Bad coverage Interference % noisy call
1d
1d
2d C AX C
D 3
D1
C AX
C AX
AI m
CA V
C AL i
C AX
AI O
AI m
AV
AI O
AI O
D2
E3
E1
E2
CB R
CB R
CA V
Downlink noisy calls with interference

Downlink noisy calls with interference
1400 1200 1000 800 600 400 200 0
C AX 2 1 d E2 E3 D1 1d 2d 1 2 AI O 1 AI O 2 E1 C AX AX 1 D AI m D AI m AV AV CA IO CA X AL i CB R CB R CA V AI O BR AV AV C C 2d 2 1 2 3 n
AI O
BR
AV
AV
2d
25 20 15
Interference
10 5 0
% Interference

59
Interpret the previous graphs and find out the most interfered cell?
In these graphs, it can be seen that the cell CAV1 the highest DL noisy call rate (with a value of 23.24 %). This high DL noisy call rate is due in majority (91.36 % of the cases) to interference problems. On the uplink path, it can be seen two groups of cells: CAV1, CAV2 and CAX2 present a majority of interfered calls compared with all the others. However, if the cells are sorted according to the highest rate of calls suffering from interference problem on downlink path, it can be seen that CAV1 have more than 20%.
14
60
7 Analysis of Interference problems using RMS
Introduction
61
If the interference problem has been detected both in the UL and DL path and for one TRXs (case of non-Hopping) or for all TRXs (case of Hopping) of the cells, the problem can be seen as an interference problem. An interference problem must be analyzed through Rxlevel and RxQuality measurements. Indeed, mobile with a high RxQuality is not always suffering from interference problems. Such interference can be characterized through the viewing of the samples distribution between RxLevel and RxQuality intervals in the reports
Alc_Mono_DL_RxQuality_Rxlevel and Alc_Mono_DL_RxQuality_Rxlevel
Rxqual/Rxlev distribution
62
Here is the Rxqual/Rxlev distributions of cell CAV1 Interpret the Uplink matrix below?
In the circles presented on this figure, it is possible to see that the corresponding cell has many samples with good RxLevel and bad RxQual
Rxqual/Rxlev distribution
63
Interpret the Downlink matrix below?
In the circles presented on this figure, it is possible to see that the corresponding cell has many samples with good RxLevel and bad RxQual
Downlink TA and Rxqual per Rxlev

64
In practice, the previous matrix must be associated with other distributions, in order to get a complete and precise picture of some possible problems of interference Interpret this graph?
Downlink TA and RxQual per RxLev
4.5 4 3.5 3 2.5 2 1.5 1 0.5 0 [-110,-104[ [-104,-97[ [-97,-91[ [-91,-85[ [-85,-79[ [-79,-72[ [-72,-66[ [-66,-60[ [-60,-53[ [-53,-47] RxLevel ( dBm ) 2 1.8 1.6 1.4 1.2 1 0.8 0.6 0.4 0.2 0
On above figures, it can be seen that the downlink RxQuality starts with high values in good RxLevel intervals: 1.2 of RxQuality between 60 and 66 dBm
Carrier over Interference

65
The interference source should be detected in order to solve the problem Such source interference can be detected through the report Alc_Mono_Carrier_over_interference Distribution of C/I Distribution samples per Neighbour Cell:
Carrier over Interference

66
The firsts analysis is to filter the neighbours with no significant samples measured.
In previous graph, the neighbours with just green values should be despicable, because no many samples and the results can be wrong
The second step consists in checking the neighbour cells with the lowest C/I:
no co-channel or adjacent frequencies should be applied between these neighbour cells and the serving cell. If it is the case, the frequencies should be changed.
Another way to detect an interfered frequency on one cell is to study the RMS statistics (especially RxQual statistics) on a per TRX basis, considering that each TRX corresponds to one particular frequency. However, such method has the drawback to require the disabling of all the hopping modes (Base band Hopping, Radio Hopping) , in order to see which frequency is the cause of interference. After, there should the frequencies that are causing the problem should be changed. In order to find new frequencies, it is possible to declare extra-frequencies to be monitored by the MS when it is in dedicated mode. The selected method is the application of the Extended Measurement Reporting (GSM feature MAFA).
14
67
End of Module RMS Based Radio Network Optimization
15

Module 5 RMS Based AFP
Blank Page
Optimization & FP using RMS RMS Based AFP 15
Objectives
To be able to use RMS data for Frequency planning
Objectives [cont.]
Table of Contents

1 RMS Frequency Planning Basics C/I Vector C/I Vector Mutual Interference Probability Mutual Interference Probability Answer the Question 2 Dummy neighbors concept Purpose Purpose RMS measurements with dummy neighbors Dummy Neighbors Algorithms Narrow BCCH Band Algorithm Wide BCCH Band Algorithm Resulting Interference Matrix Answer the Question 3 RMS FP Process RMS Based FP steps Step 1 (OMC) Step 2 Step 3 (Planning Tool) Step 4 (Planning Tool) Step 4 (Planning Tool) Step 4 (Planning Tool) BSS B11 Step 4 (Planning Tool) BSS B11 Step Optimization and Frequency Planning using 4 (Planning Tool) All Rights Reserved Alcatel-Lucent 2007 RMS Step 4 (PRC Generator) Step 4 (OMC) Step 5&6 (OMC) Step 7 Step 7 Step 7 step 8 (Planning Tool) step 8 (Planning Tool) step 8 (Planning Tool) step 9 (Planning Tool) step 9 (Planning Tool) step 9 (Planning Tool) step 9 (Planning Tool) step 9 (Planning Tool) step 10: Frequency Plan Qualification step 10: Frequency Plan Qualification step 10: Frequency Plan Qualification step 10: Frequency Plan Qualification Exercise Summary Self-Assessment on the Objectives Abbreviations and Acronyms Glossary References End of Module
Page 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 55 57 58

All Rights Reserved Alcatel-Lucent 2007 page is left blank intentionally
Optimization & FP using RMS RMS Based AFP
15
1 RMS Frequency Planning Basics
C/I Vector
C/I measurements are performed on all frequencies that appear in the Neighbor BCCH List Measured Cells (MCs) are:
Defined Neighbor Cells Cells that have the same BCCH frequencies like the neighbor cells
Recall: The equation used for C/I calculation (if EN_BALANCED_CI = TRUE ) at the BTS is: C/I (dB) = RXLEV_DL + abs(BS_TXPWR - BS_TXPWR_MAX) - RXLEV_NCELL RXLEV_DL: Received signal level of the serving cell. RXLEV_NCELL: Received signal level of the neighbor cell. BS_TXPWR: BTS transmitted power BS_TXPWR_MAX: maximum allowed BTS transmission power
C/I Vector
For each pair of Serving Cell (SC) and Measured Cell (MC), one C/I Vector is created
I
MC F MC A
MC B
SC MC A
SC MC E MC C MC D
C/I
Pots defined by C/I thresholds (templates)
White cell is serving cell MC A, MC B, MC C, MC D, MC E and MC F are Interferers
Mutual Interference Probability

10
Mutual Interference Probability between SC and MC X

C/I Interference Threshold
- -12
-9
-6
-3
12
Interfered
Non-Interfered
Mutual Int. Prob (SC, MC X) = # Interfered / (# Interfered + # Non-Interfered )
Mutual Interference Probability

A
15
11
Resulting RMS Interference Probability Matrix
F SC E D
Interf. Server SC A B C D E F
SC
0.28 0.21 0.19 0.51 0.28 0.09
0.31 0.3 0.15 0.11 0.08 0.09
0.23 0.28 0.21 0.15 0.04 0.08
0.18 0.12 0.18 0.37 0.13 0.04
0.54 0.10 0.13 0.35 0.28 0.21
0.3 0.09 0.06 0.07 0.29 0.40
0.1 0.10 0.07 0.01 0.18 0.38 -
the precision of the interference matrix is dependant on : C/I threshold : they should not be changed from default values (Template 1) Start time of the RMS job : it should be set in order to collect measurements related to the most important traffic position
A9155 handles different interference matrixes: Predicted IM Defined based on predictions calculation: A9155 has several prediction models from standard Hata-Okumura model to 3D models Based different maps: height, clutter, buildings, traffic, etc. RMS IM IM obtained from real field measurements T180 IM Takes into account the HO traffic, to provide certain channel separation (Easy RNP functionality) to be released soon (now, in validation phase) Mixed RMS-Predicted IM For new sites (for whom RMS is not available) provided by RMS Get a clear image on the network interference and traffic distribution
Answer the Question

12
Is there an incompatibility between the RMS counters and the downlink power control activation?
No, RMS C/I measurements are performed on neighbor BCCH; where the downlink power control has no effect. For serving cell measurements, the effect of power control is compensated internally inside the BTS .
15
13
2 Dummy neighbors concept
Purpose
14
MS will measure only defined neighbor BCCHs

Cell close to serving cell but not using neighbor BCCHs are:
not reported not contributing to overall interference matrix
RMS interference matrix is not reflecting the complete network interference
Some interferer BCCH frequencies are not reported
Serving cell Neighbor cell cell using Neighbor BCCHs Other cells
Purpose
15
Solution: Boosting the Approach by Adding Dummy Neighbors
Dummy neighbors are generated in order to get more reliable RMS measurement. This method allows measuring all potential interferers from the network. By skipping one of these interferers the final frequency plan may be not optimal. This step, the definition of dummy neighbours, is the most important step, since any error in this step may lead to bad results.
RMS measurements with dummy neighbors

16
All cells close to the serving cell are measured and reported to the OMC-R Target is to measure as many different BCCH as possible Dummy neighbors:
Not real neighbors Different BCCH than:
Serving cell Neighbor Cells
When a set of dummy neighbour cells have been defined for each cell, these dummy neighbour cells must be inserted to the adjacency list provided to the BSS, taking into account the following limitations: 32 neighbour frequencies (max different 32 BCCH) 64 neighbour cells (it must be noted that since B7, out of the 32 first neighbour cells corresponding to the 32 neighbour frequencies, the remaining cells will be defined with an adjacency type Handover only).
Dummy Neighbors Algorithms

17
Two main algorithms implemented and used by A9155v6 frequency planning tool:
Narrow band BCCH algorithm. Wide band BCCH algorithm. Narrow band algorithm has two sub-cases:
BCCH with dedicated band. No dedicated band for BCCH.
The common idea is to make mobile measure as many frequencies as possible
Narrow BCCH Band Algorithm

18
Narrow BCCH Band Approach ( BCCH band <= 32 ) Assumption: All BCCHs are from a specific dedicated Frequency Block Goal: Measuring all BCCHs means measuring of all Cells possible Method:
Add External Cells with BCCH between B1 B32 and create HOs on them when necessary but inhibit HO by parameter setting (f.I. HO_MARGIN = 127)
BCCH B1 BCCH B2 BCCH B3
HO
BCCH B4 BCCH B5 BCCH B6 ...

BCCH B32
Inhibition of the HO attempts towards Dummy Neighbors : Parameters per adjacency with a dummy neighbor : HO_MARGIN = HO_MARGIN_DIST = HO_MARGIN_QUAL = HO_MARGIN_LEV = 127 127 127 127 dB dB dB dB
Wide BCCH Band Algorithm

19
Wide BCCH Band Approach ( BCCH band >= 32 ) Assumption: BCCHs are homogenous distributed over a band Goal: Measuring cells in consecutive packages starting with the most important Method:
Setting up HOs to real existing cells in the network Inhibiting HO execution by parameter setting ( for instance HO_MARGIN =127) Selection of important cells by using other criteria ( for instance Predicted IM)
In very dense and mostly in dual band networks the number of neighbours is quite high. This leads to a small amount of dummy neighbours for RMS measurements and therefore an incomplete RMS interference matrix. The solution to overcome this situation is to implement dummy neighbours in cycles. This will lead to a longer period needed for RMS frequency planning process (at least one week for one cycle). The option for the user is to use: one cycle or several cycles for dummy neighbours implementation. The main issue is that in the neighbours table the dummy neighbours are created based on different ranks. The column RMS_DUMMY_NEIGHBOURS should take the following values: 0, for normal neighbours 1,2,3, etc for dummy neighbours of different ranks. After all dummy neighbours have been created the tool will be able to: Provide the total number of cycles required Remove some dummy neighbours of different ranking, for uploading to the OMC purposes. In that way, the 9155 will be able to create different PRC with different dummy neighbours.
Resulting Interference Matrix

20
Achievement: An extensive RMS Interference Matrix

A A B C D E F G H I J K L .. .. B C D E F G H I J K L .. ..
Answer the Question

21
Is the maximum number of dummy neighbors that could be declared impacted by the number of "real" adjacency already declared at OMC level?
Yes & No; defining dummy neighbor cells is limited by 32 neighbor frequencies (max different 32 BCCH) 64 neighbor cells However, this is not as real limitation; since 32 potential interferer are quite enough to create the interference matrix. Also cleaning for unnecessary neighbors can be applied before dummy neighbors.
There are several solutions to overcome this situation. One of the solutions is the implementation of dummy neighbors in cycles Another solution implemented in the tool is the neighbor cleanup. The neighbor clean up consists in deleting the unnecessary neighbors before starting the whole process. This module is helpful in several situations: -Creates more space for dummy neighbors -Ease the task of the frequency planning process (less constraints to fulfill) -Improve the overall quality of the network, due to an optimized neighbor plan The main input for this process is the T180 counters (HO traffic). The handover statistics (T180 counters) are simply containing information about the HO traffic of one cell with all its neighbors. Three set of counters are available: C400: HO Requests C401: HO Execution Attempts C402: HO Success Basically, in the dummy cleanup module, the incoming and outgoing handover requests (C400) for all HO/HO + reselection adjacencies are monitored for a week. Based on these counters, the HO relations which are below one threshold are marked for deletion, since it makes no sense to keep them as neighbors without HOs. The default value of the threshold is 0.1% of the total HO requests of all adjacencies of a cell then it can be removed. But in order to have a control of the deleted neighbors another input is added to this process: the RMS counters. With the help of RMS measurements the tool can compute a cell overlap between the adjacencies marked to be deleted by the T180 counters. The RMS double checks the adjacencies before their deletion
15
22
3 RMS FP Process
3 RMS FP Process
RMS Based FP steps

23
1- Get network configuration
10-Frequency plan assessment
Duration : 2 Weeks Network Freeze
2- Convert from CSV to COF
9- Automatic frequency plan
Duration : 2 Weeks
3- Import data into Planning Tool
Topology import 8- Mixing interference matrices
4- Dummy neighbors generation/ implementation Implementation OMC Planning Tool

7- IM generation Duration RMS files collection : 2 Weeks Network Freeze Dummy Neighbors deletion
5- Activate RMS
6- RMS files collection
A9155 AFP Module: Possibility to allocate Frequencies, Frequency hopping groups (FHS), HSN, MAIO, BSIC Goal of AFP Find optimal allocations that minimise interferences over the network and comply with a set of constraints (separation, frequency domain limitation) Principle of an AFP model Convergence criterion based on a cost function simulating annealing The cost function consists of two main components Cost component due to interferences Cost component due to separation constraint violations The AFP model tries to minimise the value of the cost function
Inputs: existing dimensioning results (number of requested TRXs per transmitter) existing neighbour allocation definition of subcell hopping mode subcells in A9155 are: BCCH, TCH and TCH_INNER Interference matrix AFP possible on all the transmitters or for a group of transmitters Allocation steps Setting AFP inputs Loading and checking the network Optionally computing interference histograms and starting the AFP Analysing allocation results
3 RMS FP Process
Step 1 (OMC)
24
Get the logical parameters from the OMC-R to be imported in the FP tool. This configuration includes the frequency and neighborhood plans besides all the other logical parameters.
Frequency plan: used for evaluation of existing frequency plan and define the weak points and possible improvements area Neighbors plan: used to generate dummy neighbors.
3 RMS FP Process
Step 2
25
Convert csv files exported from OMC to the format used by the Planning tool In case of A9155v6 planning tool. The files are called cof files. The PRC-Generator tool could be used to achieve this step
3 RMS FP Process
Step 3 (Planning Tool)

26
The cof files resulting from PRC-Generator are imported into A9155v6 at this stage. After specifying the location of cof, press import.
3 RMS FP Process

27
Dummy data is generated in this step
Two options exist in RMS dummy management Add-in.
3 RMS FP Process

28
A9155v6 will automatically select the suitable algorithm according to the network configuration
3 RMS FP Process

29
Narrow band BCCH
Wide band BCCH
This menu enables the user to set the basic parameters for dummy cells, used for a better identification of the cell in the network. The user is able to set: LAC, of the dummy cells. All cells will have the same LAC First CI. This is the CI of the first dummy cell created. The CI of the each created dummy cell is then incremented with 1. MNC value - Mobile Network Code MCC value Mobile Color Code BSIC of the implemented dummy cells. If there is a not used BSIC code within the network it is recommended to use it for dummy cells. Please avoid using the BSIC=0 values. The default name of all cells created.
3 RMS FP Process

30
Dummy neighbors are seen directly from neighbor table (Intratechnology Neighbors) in the column RMS_DUMMY_NEIGHBOURS
3 RMS FP Process

31
Export Dummy neighbors in cof format
3 RMS FP Process
Step 4 (PRC Generator)

32
Put the cof files exported from A9155v6 in the appropriate directory; C:\Program Files\Alcatel\PRC_Generator V3.3\RNP_Export\cof_files
Always check the log window
The generated CSVs should contain dummy neighbors only

Check the status of the generated CSVs
Dummy data generated must be uploaded to the network in order to be measured during RMS measurement campaign. This process is done using additional software modules, depending on the tool used for RMS based frequency planning (e.g. A9155 PRC Generator Module for A9155 AlcAFP).
3 RMS FP Process
Step 4 (OMC)
33
Dummy Neighbors Implementation: Activate PRC with dummy neighbors It is very important to monitor the network QoS after dummy neighbor implementation. This is used to:
Check that dummy neighbors have been successfully implemented Compare the network behavior with the KPIs measured without dummy neighbors Check that there is no major impact bring by dummy neighbors in the network behavior
3 RMS FP Process
Step 5&6 (OMC)

34
Step 5:
Enable RMS measurements at the OMC-R Measurements must be taken for at least one week, for example between 9AM-11PM everyday During this period the network must be frozen. The network freeze, in this case, means:
No cells addition. Neighbor relations must be kept frozen during measurement period. No physical adjustments (power, tilts, azimuths). No change in the frequency plan.
Step 6: RMS files collection

Transfer RMS files to local machine (each day).
After the RMS campaign is finished all files are transferred locally. Using these files the tool used for frequency planning will create an interference matrix. The big benefit is that the computed interference matrix (IM) is created out of real interference information. The created interference matrix is used as input during frequency allocation process and used in order to minimize the overall interference. The RMS files are located in the folder: /alcatel/var/share/mpm and the names for all RMS measurement files are starting with PMRES-31
3 RMS FP Process
Step 7
35
Remove Dummy Neighbors:

From RMS Dummy Management delete the dummy neighbors.
Export COF files after the deletion of dummy neighbors. Convert the files into csv format. Apply the csv to the OMC. Now we have the dummy neighbors removed from the network
Dummy Neighbour Deletion: Dummy neighbours are removed after the RMS measurement campaign is finished and all RMS files are transferred locally. After this process, the network is not mandatory frozen, anymore even it is recommended to keep it frozen. Any cells added into the network, before the frequency plan implementation, have to be treated separately since no RMS measurements are available for them. Therefore the user has to set the channel separation for these cells have to be done manually (based on the experience matrix). The algorithms consist in removing the dummy adjacencies from the tool used for frequency planning. The dummy neighbours are removed from the system after the new ACIE files (created in the tool after deleting dummy neighbours) are activated in the OMC-R.
3 RMS FP Process
Step 7
36
Now the RMS IM will be generated.
3 RMS FP Process
Step 7
37
The following parameters have to be specified

Path to input directory. Starting date. Ending date
Export the RMS IM for later use. The format of interference matrix is an A9155 internal format with extension rms.
3 RMS FP Process

38
This is an optional step for mixing several interference matrices. User is able to combine RMS interference matrix with predicted interference matrix using different methods:
Worst Case
Highest Priority
Weighted Average
3 RMS FP Process

39
Predicted IM should be calculated first. Open interference matrices. Choose mixing method 1 2
3 RMS FP Process

40
Calculate/ Export/ Open mixed IM. Choose the IM to be used for AFP
3 RMS FP Process

41
Start the AFP.
FP creation algorithm is really dependent on the tool used for frequency allocation. RMS information is then introduced in the frequency allocation process by the IM computed from the collected RMS files. Before FP creation, the planner should check weather all cells have RMS reports available. There are several reasons that a cell doesnt have the RMS reports: BTS HW support, site not commercial use, key parameter change, unexpected reasons. For these cells additional separation matrix must be used.
3 RMS FP Process

42
Select the properties of the AFP model.
3 RMS FP Process

43
Select the interference matrix to be used.
3 RMS FP Process

44
Run AFP
Progress window: Best Cost Best Elapsed Time Elapsed Separation Component Separation
3 RMS FP Process

45
Resume the Frequency Plan:

the frequency plan is re-started and all allocations done so far are lost.
Commit the Frequency Plan:

This loads the plan into the A9155 V6 database.
Cancel the AFP process.

The window is left without any action and the program returns to the AFP start window.
The FP creation process is composed by the following steps: FP Generation: algorithm dependent on the tool used. The output of this step is the new created frequency plan. Comparison of new/old FP. This step is performed in order to decide if the new created frequency plan is better than the previous one. This is a milestone where the decision to implement frequency planning should be taken Coordination on the planning border. This issue should be taken into account to coordinate the RMS frequency plan with the frequency plan of the neighbour area. This coordination is not related to RMS but with frequency planning. Network QoS monitoring, after dummy neighbours have been removed, in order to assure that network performs as before dummy neighbours implementation. FP Implementation
3 RMS FP Process
Step 10: Frequency Plan Qualification

46
Using frequency histogram.
Old FP
New FP
QoS Analysis: In order to check the frequency plan after implementation, intensive QoS analysis must be performed. All problems discovered must be solved immediately. Drive tests have to be performed in the entire area of the new frequency plan. In this way the problematic areas are found and solved very fast. The optimization solutions are: - Using joker frequencies. Problems discovered can be solved very easy and quickly if joker frequencies have been reserved from the beginning. - Using MAFA feature. If joker frequencies are not available, finding clean frequencies could be useful in order to replace interfered ones. Traditionally, these measurements are obtained through measurement campaigns realized on the field. However, with features RMS and MAFA these measurements are available directly from the network for any period of time. - Manual optimization. This solution consists in changing manually the frequency plan, while trying to fulfill al imposed constraints.
3 RMS FP Process

47
Using audit function
Audit results in Event-window
3 RMS FP Process

48
Using C/I calculations.

Old FP New FP
3 RMS FP Process

49
Visual evaluation
Self-Assessment on the Objectives

50
Please be reminded to fill in the form Self-Assessment on the Objectives for this module The form can be found in the first part of this course documentation
15
51
End of Module RMS Based AFP
16

Module 6 Annex
Blank Page
Optimization & FP using RMS Annex 16
Objectives
Objectives [cont.]
Table of Contents

1 RMS Indicators Thresholds 2 Different Interference Matrix 3 Format of RMS Interference Matrix
Page 7 11 13

BSS B11 BSS B11 Optimization and Frequency Planning using Allpage Rights Reserved Alcatel-Lucent 2007 This is left blank intentionally RMS
Optimization & FP using RMS Annex
16
1 RMS Indicators Thresholds
16
Indicator
Sensitivity
High sensitivity
Red threshold Orange threshold 0.4 0.5 0.6 -85 -90 -95 0.7 0.8 0.9 -90 -95 -100 0.7 0.8 0.9 0.4 0.4 0.4 0.3 0.4 0.5 -80 -85 -90 0.4 0.5 0.6 -85 -90 -95 0.4 0.5 0.6 0.2 0.2 0.2
Yellow threshold
RMS_UL_ConsecutiveFrameErasure_avg
Medium sensitivity Low sensitivity High sensitivity
RMS_DL_RxLevel_avg
Medium sensitivity Low sensitivity
High sensitivity
RMS_DL_RxQuality_avg
RMS_UL_RxLevel_avg
RMS_UL_RxQuality_avg
RMS_Call_abnormal_bad_FER_rate
0.2 0.3 0.4 -75 -80 -85 0.2 0.3 0.4 -80 -85 -90 0.2 0.3 0.4 0.1 0.1 0.1
16
Indicator
Sensitivity High sensitivity
Red threshold Orange threshold 0.08 0.1 0.12 0.08 0.1 0.12 0.08 0.1 0.12 0.08 0.1 0.12 0.08 0.1 0.12 0.08 0.1 0.12 0.06 0.08 0.1 0.06 0.08 0.1 0.06 0.08 0.1 0.06 0.08 0.1 0.06 0.08 0.1 0.06 0.08 0.1
Yellow threshold
RMS_Call_noisy_DL_bad_coverage_rate
RMS_Call_noisy_DL_interference_rate
RMS_Call_noisy_DL_rate
RMS_Call_noisy_UL_bad_coverage_rate
RMS_Call_noisy_UL_interference_rate
RMS_Call_noisy_UL_rate
0.04 0.06 0.08 0.04 0.06 0.08 0.04 0.06 0.08 0.04 0.06 0.08 0.04 0.06 0.08 0.04 0.06 0.08
16
10
Indicator
Sensitivity High sensitivity
Red threshold Orange threshold 0.08 0.1 0.12 0.06 0.08 0.1
Yellow threshold
RMS_Call_noisy_bad_FER_rate
0.04 0.06 0.08
16
11
2 Different Interference Matrix
2 different Interference Matrix (es)
Pros & cons

12
Description Predicted Interference Matrix Drive Test Interference Matrix C/I RMS IM
Automatic RNP created Interference IM based on field strength prediction Covers all cells Fast creation
Needs exact NW design Model Calibration Geo databases
IM based on C/I drive test measurements
IM directly from the user
High creation effort Not all area covered
IM based on measurements performed by each user mobile
Real Traffic Amount Real Traffic Distribution Interesting in Costs
Network Freeze Period Non-operational Cells not considered
Experience Matrix
Manually created In-compatibility Matrix based on RNEs local experience
Covers singular incompatibilities that have not been detected by any other method
Uncomplete Matrix
A9155 handles different interference matrixes: Predicted IM Defined based on predictions calculation: A9155 has several prediction models from standard Hata-Okumura model to 3D models Based different maps: height, clutter, buildings, traffic, etc. RMS IM IM obtained from real field measurements T180 IM Takes into account the HO traffic, to provide certain channel separation (Easy RNP functionality) to be released soon (now, in validation phase) Mixed RMS-Predicted IM For new sites (for whom RMS is not available) provided by RMS Get a clear image on the network interference and traffic distribution
16
13
3 Format of RMS Interference Matrix
Overview
14
# #
Mapping section. Total Number of Total Number of Number Unidentified Number of Unidentified of Cells cells Records Records 10 15 2 1 200 324 5 6 Total Number of Samples 450 236 Number of Unidentified Samples. 23 12
#Cell Name
Cell Index
[MAPPING] Cell_a 1 Cell_b # 2
Thresholds section -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 # # # 13 14 15
[THRESHOLDS]
ities
# Servig Target cell cell (interfe (interfer red er) [PROBABILITIE S] 1 2 2 1 1 5 1 4 1 5 1 4 1 5 1 4 1 5 1 4 1 5 1 4 1 5 1 1 1 1 1 1 1 1 1 1 1 1 4 5 4 5 4 5 4 5 4 5 4 5 1 4 1 5
Mapping Section
15
The RMS interference matrix format, as presented in the previous table, is composed by the following sections: Files used for IM computation are presented first. This section is only for informative purposes and it is not used by A9155 AlcAFP module. Mapping section. This section provides a mapping between the cell name and an A9155 internal index, for all cells:
Cell name: the name of the serving cell Cell index: internal index of A9155 Total Number of Cells: total number of target cells identified in the rms files for the impacted serving cell Number of Unidentified Cells: the number of target cells present in the rms file for the impacted serving cell, but not identified by the A9155 cell identification algorithm Total Number of Records: Total number of C/I measurements of the impacted serving cell in all rms input files. Number of Unidentified Records: Number of C/I measurements, related to the serving cell, from the input rms files not identified by the A9155 identification algorithm not identified Total Number of Samples: Total number of C/I samples related to the serving cell, from rms files Number of Unidentified Samples: Total number of samples not identified by A9155. These are all samples from the non identified cells/records
Thresholds & Probabilities Sections

16
Thresholds section contains the different thresholds used for interference probability computation
Each threshold is used by interference probability formula in the following way: Pint=Prob(C/I<C/Ithreshold)
Probabilities section. It provides the computed interference probability for all impacted cell couples
Serving cell (interfered): this field contains the index of the serving cell, index shown in the Mapping section. Target cell (interferer): this field contains the index of the target cell, index shown in the Mapping section. Probabilities: There are 25 different probabilities values due to 25 different thresholds (from -9 to 15). The value represents actually the non-interfering probability, since the A9155 AlcAFP takes into account this kind of probabilities. The non-interfering probabilities are computed in the following way: Pnon-int=1-Pint =1-Prob(C/I<C/Ithreshold).
16
17
End of Module Annex
Last But One Page

1
@@PRODUCT @@COURSENAME
All Rights Reserved Alcatel-Lucent @@YEAR
All Rights Reserved Alcatel-Lucent @@YEAR @@COURSENAME - Page 1
All rights reserved Alcatel-Lucent @@YEAR Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved Alcatel-Lucent @@YEAR @@COURSENAME - Page 2

BSS B11 Optimization and Frequency Planning With RMS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSS B11 Optimization and Frequency Planning With RMS

Uploaded by

Copyright:

Available Formats

BSS B11 BSS B11 Optimization and Frequency Planning using RMS

TMO18110 D0 SG DEN I1.0 Issue 1.0

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

Terms of Use and Legal Notices

All rights reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

4. Topic/Section is Positioned Here

7. Topic/Section is Positioned Here

2. Topic/Section is Positioned Here 3. Topic/Section is Positioned Here

All Rights Reserved Alcatel-Lucent 2010

Course Outline [cont.]

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

Welcome to BSS B11 Optimization and Frequency Planning using RMS

Upon completion of this course, you should be able to:

All Rights Reserved Alcatel-Lucent 2010

Course Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

About this Student Guide

All Rights Reserved Alcatel-Lucent 2010

Where you can get further information

About this Student Guide [cont.]

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

Client (Company, Center) : Language : Switch

Number of trainees : Surname, First name :

Instructional objectives 1 To be able to XXX

Self-assessment of Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2010

Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:

Section 1 Optimization & FP using RMS

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

To be able to describe radio measurments

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2007

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007

Table of Contents [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2007 page is left blank intentionally

Optimization & FP using RMS Radio Measurements Overview

All Rights Reserved Alcatel-Lucent 2007

All Rights Reserved Alcatel-Lucent 2007

Optimization & FP using RMS Radio Measurements Overview

2 Radio Link Measurements

All Rights Reserved Alcatel-Lucent 2007

2 Radio Link Measurements

For active channels, the radio measurements consist in :

All Rights Reserved Alcatel-Lucent 2007

2 Radio Link Measurements

The basic radio link metrics are :

The signal strength:

All Rights Reserved Alcatel-Lucent 2007

2 Radio Link Measurements

-49 dBm to -48 dBm > -48 dBm

All Rights Reserved Alcatel-Lucent 2007

2 Radio Link Measurements