RAS05.1 Performance Monitoring Features

RAS05.1 Performance MonitoringFeatures

DN70159183Issue 1-1 en

# Nokia Siemens Networks 1 (52)

RNC3267Nokia WCDMA RAN, Rel. RAS06, SystemLibrary, v. 3

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (52) # Nokia Siemens Networks DN70159183Issue 1-1 en

RAS05.1 Performance Monitoring Features

Contents

Contents 3

1 Documentation changes in RAS05.1 Performance MonitoringFeatures 7

2 RAS05.1 performance monitoring features overview 92.1 Further information 9

3 RAN189: Automatic Definition of Neighbouring Cells 113.1 Automatic Definition of Neighbouring Cells feature description 113.1.1 Operator benefits 123.1.2 Compliance 123.1.3 Resource requirements 123.1.4 Interaction with other features 133.1.5 Limitations and restrictions 133.2 Main functionality of Automatic Definition of Neighbouring Cells 143.2.1 Using Automatic Definition of Neighbouring Cells 143.2.2 Activating Automatic Definition of Neighbouring Cells 143.2.3 Verifying Automatic Definition of Neighbouring Cells 143.2.4 Deactivating Automatic Definition of Neighbouring Cells 153.2.5 Feature management 153.2.6 Architecture 153.2.7 Capacity 163.3 Parameters 17

4 RAN956: BTS Channel Element Capacity Measuring 214.1 BTS Channel Element Capacity Measuring feature description 214.1.1 Operator benefits 234.1.2 Compliance 244.1.3 Resource requirements 244.1.4 Interaction with other features 244.1.5 Limitations and restrictions 244.2 Main functionality of BTS Channel Element Capacity Measuring 254.2.1 Using BTS Channel Element Capacity Measuring 254.2.2 Activating BTS Channel Element Capacity Measuring 254.2.3 Verifying BTS Channel Element Capacity Measuring 254.2.4 Deactivating BTS Channel Element Capacity Measuring 254.2.5 Feature management 264.2.6 Architecture 264.2.7 Capacity 26

5 RAN232: CPICH Ec/No Coverage Measurements andOptimisation 27

5.1 CPICH Ec/No Coverage Measurements and Optimisation featuredescription 27

5.1.1 Operator benefits 285.1.2 Compliance 285.1.3 Resource requirements 29



Contents

5.1.4 Interaction with other features 295.1.5 Limitations and restrictions 295.2 Main functionality of CPICH Ec/No Coverage Measurements and

Optimisation 305.2.1 Using CPICH Ec/No Coverage Measurements and Optimisation 305.2.2 Activating CPICH Ec/No Coverage Measurements and Optimisation 305.2.3 Verifying CPICH Ec/No Coverage Measurements and Optimisation 305.2.4 Deactivating CPICH Ec/No Coverage Measurements and

Optimisation 305.2.5 Feature management 305.2.6 Architecture 305.2.7 Capacity 30

6 RAN1054: Downlink Packet Data Throughput for Subscriber andEquipment Trace 31

6.1 Downlink Packet Data Throughput for Subscriber and Equipment Tracefeature description 31

6.1.1 Operator benefits 336.1.2 Resource requirements 336.1.3 Interaction with other features 336.1.4 Limitations and restrictions 336.2 Main functionality of Downlink Packet Data Throughput for Subscriber and

Equipment Trace 346.2.1 Feature management 346.2.2 Architecture 346.2.3 Capacity 34

7 RAN190: Radio Connection Performance Measurements for RLC TMand UM and Outer Loop Power Control 35

7.1 Radio Connection Performance Measurements for RLC TM and UM andOuter Loop Power Control feature description 35

7.1.1 Operator benefits 367.1.2 Compliance 367.1.3 Resource requirements 367.1.4 Interaction with other features 377.1.5 Limitations and restrictions 377.2 Main functionality of Radio Connection Performance Measurements for

RLC TM and UM and Outer Loop Power Control 387.2.1 Using Radio Connection Performance Measurements for RLC TM and UM

and Outer Loop Power Control 387.2.2 Activating Radio Connection Performance Measurements for RLC TM and

UM and Outer Loop Power Control 387.2.3 Verifying Radio Connection Performance Measurements for RLC TM and

UM and Outer Loop Power Control 397.2.4 Deactivating Radio Connection Performance Measurements for RLC TM

and UM and Outer Loop Power Control 397.2.5 Feature management 397.2.6 Architecture 407.2.7 Capacity 407.3 Connection type classification 40

8 RAN1163: Iu-PS Throughput Measurement for GTP Traffic 43



8.1 Iu-PS Throughput Measurement for GTP Traffic feature description 438.1.1 Operator benefits 468.1.2 Compliance 468.1.3 Resource requirements 468.1.4 Interaction with other features 478.1.5 Limitations and restrictions 478.2 Main functionality of Iu-PS Throughput Measurement for GTP Traffic 488.2.1 Using the Iu-PS throughput measurement for GTP traffic 488.2.2 Activating the Iu-PS throughput measurement for GTP traffic 488.2.3 Verifying the Iu-PS throughput measurement for GTP traffic 488.2.4 Deactivating the Iu-PS throughput measurement for GTP traffic 488.2.5 Feature management 488.2.6 Architecture 488.2.7 Capacity 49

Related Topics 51



Contents



1 Documentation changes in RAS05.1Performance Monitoring Features

Changes between issues 1-0 and 1-1

Table Changes in RAS05.1 Performance Monitoring Features describesthe content changes in Issue 1-1.

Table 1. Changes in RAS05.1 Performance Monitoring Features

Changed chapter Description of the change See

RAS05.1 performancemonitoring features overview

Feature RAN1163: Iu-PS ThroughputMeasurement for GTP Traffic has beenadded to the table

RAS05.1 performance monitoringfeatures overview

Section RAN04 and RAS05 performancemonitoring features overview has beenremoved and the chapter renamed.

. RAS05.1 performancemonitoring features overview

. Performance monitoringfeatures overview in RAN04and RAS05 PerformanceMonitoring Features

RAN1163: Iu-PS ThroughputMeasurement for GTP Traffic

A new feature description has been addedto the document.

RAN1163: Iu-PS ThroughputMeasurement for GTP Traffic



Documentation changes in RAS05.1 Performance MonitoringFeatures



2 RAS05.1 performance monitoringfeatures overview

Table 2. RAS05.1 performance monitoring features

Feature name Available in releases

RAN189: Automatic Definition of NeighbouringCells

RAS05.1

RAN956: BTS Channel Element CapacityMeasuring

RAS05.1

RAN232: CPICH Ec/No CoverageMeasurements and Optimisation

RAS05.1

RAN1153: Complementary Counters inRAS05.1

RAS05.1

RAN1054: Downlink Packet Data Throughputfor Subscriber and Equipment Trace

RAS05.1

RAN190: Radio Connection PerformanceMeasurements for RLC TM and UM and OuterLoop Power Control

RAS05.1

RAN1163: Iu-PS Throughput Measurement forGTP Traffic

RAS05.1 ED

2.1 Further information

For feature activation instructions, see Nokia WCDMA RNC ProductDocumentation.

For parameters, counters and alarms per feature, see RAN1.5, RAN04and RAS05 parameters, counters and alarms and RAS05.1 parameters,counters and alarms in Interdependencies of Performance MonitoringFeatures.



RAS05.1 performance monitoring features overview

For more detailed information on parameters, counters and alarms, seeReference information in Nokia WCDMA RNC Product Documentation.

For information on software requirements, see Feature compatibility inWCDMA RAN Compatibility.

For information on the RAN1153: Complementary Counters in RAS05.1feature, see the following documents:

. Measuring WCDMA RAN

. WCDMA RAN Key Performance Indicators

. RNC Counters - RNW Part in Nokia WCDMA RNC ProductDocumentation

. Features Under Development (FUD)

For information on RAN04 and RAS05 features, see RAN04 and RAS05Performance Monitoring Features.



3 RAN189: Automatic Definition ofNeighbouring Cells

3.1 Automatic Definition of Neighbouring Cells featuredescription

The automatic definition of neighbouring cells consists of operational andbasic radio network measurement aspects.

Operational aspect

The operational aspect means automatic updates and optimisation ofadjacency lists from NMS.

Handover adjacency lists are initially defined with radio network planningbased on geographical locations and the estimated behaviour of the cells.However, this is not the optimal case; unnecessary cells may be includedor necessary cells excluded. During the evolution of the network, new cellsare also added and relevant parameters of the existing cells changed. Inthis case it becomes practical that adjacency lists can be updatedautomatically and the lists are optimised based on measurements withouta laborious radio network planning process.

Basic radio network performance measurement aspect

In order to enable the network management system to optimise the cellneighbour lists, several counters are needed to be supplied by the RANsuch as cell to cell handover statistics and cell to cell CPICH Ec/Nodifference measurements.

The new handover measurements for the automatic definition ofneighbouring cells are:



RAN189: Automatic Definition of Neighbouring Cells

. 1013 Autodef SHO

. 1014 Autodef IFHO

. 1015 Autodef ISHO

However the new handover measurements can be activated and used asany other basic RAN performance measurements.

However the new handover measurements can be activated and used asany other basic RAN performance measurements.

When optimising neigbours the NetAct Optimizer also uses CPICH Ec/Nodifference information between source and target cells. Optimizer retrievesthis information directly from RNC. This information is planned to beavailable as basic counters in later releases.

3.1.1 Operator benefits

This feature improves the network quality and reduces manual workloadon network optimisation. Correct adjacency definitions are a basicassumption for further performance optimisation or traffic balancing.

The signalling load is reduced, and UE measurements and handoverstake place faster when unnecessary cells are not listed. On the other hand,when all necessary cells are listed on neighbour cell lists, the call qualityalso improves and dropped calls are avoided.

3.1.2 Compliance

The new RAN performance measurement counters are 3GPP TS 32.403compliant.

3.1.3 Resource requirements

System requirements

This feature sets no requirements outside RAN.

Software requirements

The software requirements are presented in the following table:



Table 3. SW requirements

RNC OSS

RAN2.2 OSS4.1CD

Hardware requirements

This feature sets no special hardware requirements.

Operator requirements

The NetAct support for this feature is optional and the operator needs tohave the automatic adjacency optimisation module in order to be able touse this functionality. For more information, see the Optimiser 2.0customer documentation.

End user requirements

This feature sets no additional end user requirements.

3.1.4 Interaction with other features

This feature has no interaction with other features.

3.1.5 Limitations and restrictions

The provisioning of any changes in the cell neighbour lists must take placewhile the cells are operating under low traffic because the cells must bestopped from operation before the feature can be activated. Usuallynetwork planners are using some techniques to obligate all users in thethose cells, where neighbour lists are to be modified, to handover to someother neighbouring cells because adjacency lists cannot be modified whilethe cell is operating. In order to avoid any capacity problems, it ispreferable to make those changes while the traffic is low in that part of thenetwork.




3.2 Main functionality of Automatic Definition ofNeighbouring Cells

3.2.1 Using Automatic Definition of Neighbouring Cells

This feature is used with the help of the NetAct optimiser optional feature(automatic adjacency optimisation). In the optimiser, there is a specialwork space, from which the user is able to launch the automatic definitionof neighbouring cells. The UI enables the user to set all the neededparameters for completing the task. The most important parameters aredescribed in Parameters. The optimiser uses the new RAN handoverstatistics (intra-frequency (1013 Autodef SHO), inter-frequency (1014Autodef IFHO), inter-system (1015 Autodef ISHO) handover statistics)collected by the RAN, in order to measure the performance for adjacenciesin the optimisation scope. On the RAN side this feature operates like anyother feature in the RAN. Needed RAN performance measurementsoperate similarly as other RAN performance measurements. These aremanaged by using the RNC Element Manager GUI application in RAN05.1or the NetAct Administration of Measurements application.

3.2.2 Activating Automatic Definition of Neighbouring Cells

RAN performance measurements

The needed RAN performance measurements are activated with the RNCElement Manager GUI application in RAS05.1 or with the NetActAdministration of Measurements application.

NetAct

This feature is part of the NetAct application software. To activate thefeature a separate “NetAct optmiser automatic adjacency optimisation”licence has to be bought.

For more information, see the Optimiser 2.0 customer documentation.

3.2.3 Verifying Automatic Definition of Neighbouring Cells

The user can verify that:

1. the defined minimum and maximum number of adjacencies of alltypes defined in the UI do not exceed the available adjacencies´ IDs.

2. the tool is able to get the performance measurements.



3. the created adjacencies are the strongest according to the selectioncriteria unless one of the constraints is violated, then the priority ofthat constraint is taken into account.

4. the angles and distance thresholds are fully respected

For more information about the post conditions, see the NetAct optimiserdocumentation.

The RAN performance measurement data is collected and stored in thePM databases and can be viewed with available PM tools.

3.2.4 Deactivating Automatic Definition of Neighbouring Cells


The RAN performance measurements are deactivated with RNC EM GUIand with NetAct.

NetAct

This feature is part of the NetAct operating software, so no special action isneeded to take the feature out of use.

3.2.5 Feature management


For more information on the monitored counters in measurements 1013Autodef SHO, 1014 Autodef IFHO and 1015 Autodef ISHO, see RNCCounters for RAS05.1 trial.

NetAct

The main input parameters and monitored counters are explained inParameters. For more information, see the Optimiser 2.0 customerdocumentation.

3.2.6 Architecture

To be able to optimise the adjacencies with the NetAct optimiser, thefollowing modules must be in place:




Figure 1. The essential interfaces and objects in the automatic definition ofneighbouring cells

3.2.7 Capacity


This feature has no special capacity effects.

Configurator

NetAct

RNC

Planning tool

Measurementreport

BTS

Radio

MS

Optimizer

Plan download/upload

Measurementreport

H0decision

H0decision

List

List

HCMeas. Man

RNW stats

NEMU

Start command+ params

Autotuned/initial lists H0statistics(XML)

NWI3(TCP/IP, Corba)

Meas. Man

CSV report

Initial lists

Reporter

PMfragment

FTP(TCP/IP, Corba)

NW3I IF(TCP/IP, Corba)

XML (TCP/IP)

Conf.DB



NetAct

In the pool creation phase of the adjacency optimisation, all possiblecandidates are identified in the optimiser plan. After that the rotation phasestarts. In each rotation portion of the candidate, adjacencies areprovisioned to the network and then a round of collecting performancemeasurements starts. It is recommended that in each round, the number ofrotated adjacencies does not exceed 10 adjacencies per cell. Assumingthat the number of adjacencies per RNC is about 400, the number ofrotated adjacencies might be about 4000 adjacencies.

3.3 Parameters

List of essential parameters needed for the automatic definition ofneighbouring cells using the optimiser.

Table 4. Essential parameters in autotuning algorithm

Parameter Description

Initialisation

HandoverType

Uiname (Measurement Based CheckBoxcommon for ADJS and ADJG in StartingDialog): ADJS checkbox: (adjacency typeto be optimised)

DB: User options

Selection of the handover type to beoptimised.

Range: intra-frequency/ inter-system

Default: intra-frequency

Pool

AdjacencyCreationLimitDistance (D) UIname (existing in common tab): MaxDistance

Weight factor for the distance in theformula of the ADJ creation factor

Range: [0-20000]

Default: 10000

Dynrotation UI Names (UI: (3G meas tab):radionbuttons): Static, Dynamic. Grouplabel: Rotation for ADJS and ADJG

Defines whether the rotation uses adynamic or static rotation process.

Range: [YES, NO]

Default: NO

Rotations

MaxNeighborListSize (Existing inCommon)

The maximum length of the neighbour celllist

Range: [1..31]

Default: 31




Table 4. Essential parameters in autotuning algorithm (cont.)


MinNumberOfRotatedCells

UI: (3G meas tab): Minimum Number ofRotated Cells ADJS

Defines the minimum number of poolcandidates to be tested during eachrotation. In case the algorithm does notreach the minimum number of candidatecells, this is notified to the operator.

Range: [0..100]

Default: 0

MaxNumberOfRotatedCells

UI: (3G meas tab): Maximum Number ofRotated Cells ADJS

Defines the maximum number of poolcandidates to be tested during eachrotation.

Range: [0..100]

Default: 8

Fitness evaluation

[EcnoLow, EcN0High]

UI: (3G meas tab): EcN0 Low, EcNO High

Low and high threshold for Ec/No metric

Range: -20..10

Default: [-1.5, 0]

[HoSuccessLow, HoSuccessHigh]

Low and high threshold for HO successrate metric

Range: 0.00..1.00

Default: [0.75, 0.95]

[HoRatioLow, HoRatioHigh]

Low and high threshold for HO sharemetric

Range: 0.00..1.00

Default: [0.01, 0.1]

EcnoDifferenceThreshold

Threshold for Ec/No metric filtering

Range: -20..10

Default: -6

EcnoScalingRange

Scaling parameters for Ec/No metric

Range: -20..10

Default: [-6, 3]

HoSuccessScalingRange

Scaling parameters for HO success ratemetric

Range: 0.0..1.0

Default: [0.5, 1.0]

HoRatioScalingRange

Scaling parameters for HO share metric

Range: 0.0..1.0

Default: [0.0, 0.2]



Table 4. Essential parameters in autotuning algorithm (cont.)


IntrafrequencyClass[XYZ]

Evaluation matrix: XYZ class where X, Y,Z=[Low,Med,High] referring to [Ec/No,HOshare, HOsuccess]

Range: 0..7 (0=mandatory)

Default:

ntraFrequencyClassXRanking

Scaled metrics to be used in the rankingcost function for adjacencies in class.X=1..7.

Default: Ec/No, HOratio, Hosuccess

Selection criteria

BasicListCumulativeHoRatioLimit

UI: (3G meas tab): Basic List CumulativeHO Ratio Threshold for ADJS: DB:ADCEOPTP_CUM_HO_RATIO_ADJS_TH

The cumulative %SHO threshold for thedefinition of the basic neighbour cell

Range: [0.10-0.99] percentage

Default: 0.95






4 RAN956: BTS Channel Element CapacityMeasuring

4.1 BTS Channel Element Capacity Measuring featuredescription

The BTS channel element capacity measuring feature has the featurenumber RAN956.This feature is part of the WCDMA RAN measuresolution (see Figure BTS channel element capacity measuring in WCDMAmeasure solution).



RAN956: BTS Channel Element Capacity Measuring

Figure 2. BTS channel element capacity measuring in WCDMA measuresolution

This feature introduces new statistics for monitoring the BTS channelelement capacity consumption from the BTS and the RNC point of view.The BTS counts min./max./average availability of the channel elementcapacity and min./max./average usage of the channel element capacity.The RNC counts the average usage of the channel element capacity perRB type. The RB type refers in this measurement to the Traffic class andthe allocated bit rate.

The BTS

The channel element measurement is based on the WSP capacity in NoraBTS and on the FSP capacity in FlexiBTS. In the Nora BTS case theavailable capacity means the maximum capacity (installed in the WBTS) –the disabled capacity (for example, the blocked). In the FlexiBTS case the

RNC

3GPP Itf-N interface

Nokia proprietary interface

RNCElement Manager

Reportgeneration

NetAct Northbound interface3GPP named counters

PM:Measurement

activation

PM:DataTransfer

LocalMeasurementManagement

Core Network

lub

lub

added

taadded

DL: Quality(Measured)

UL: BLER ar

Options Close

Radio 1

NokiaNetAct

Reporter

BTS Channel ElementCapacity Reports- Available ChannelElements per BTS- Used Channel

Elements per BTS

BTS CECounters



available capacity means the maximum capacity – (the disabled capacity +the not licensed capacity). The measured channel element values arereported to the BTS EM and to the NetAct via the RNC (NEMU). If thebaseband pooling is not in use or the BTS is a FlexiBTS, the values of thecounters are calculated to the LCG_0 (this is the same as BTS levelcalculation). If the baseband pooling is in use the calculation is made perLCG.

The RNC

On the RNC side the channel element measurement is based on theestimated usage of channel elements in the WBTS. The estimation is doneaccording to the following mapping table:

Table 5. Estimated usage of channel elements in the WBTS

DCH data rate / kbps Used channel element

AMR 1

<=16 1

32 2

64 4

128 4

256 8

384 16

The measured RB types in the RNC are the following:

. CS voice call (AMR)

. CS data call (conversational / streaming)

. PS call (streaming/interactive/background)


The BTS channel element capacity measuring provides the operator thenetwork level monitoring of the availability and utilisation of the BTS HWresources. This measurement also gives planning possibilities for thepresent and future needs of the BTS HW resources.




4.1.2 Compliance

This feature has no references to the standards.


System requirements



The software requirements are presented in the following table:

Table 6. Software requirements

RAN RNC BTS AXC NetAct SGSN MSC MGW UE

Release RN2.2 WN3.2 - OSS4 - - - -




This feature sets no special operator requirements.




This feature interacts with the RAS05 feature: RAN21 Licencemanagement for BTS.


This feature has no special limitations or restrictions.



4.2 Main functionality of BTS Channel ElementCapacity Measuring

4.2.1 Using BTS Channel Element Capacity Measuring

The BTS channel element capacity measuring operates similarly as othernetwork performance measurements. The BTS channel element capacitymeasuring calculation is added to the current cell resource measurementon the RNC side. On the BTS side the BTS channel element capacitymeasuring calculation is included in the new WBTS HW resourcemeasurement. It is managed by using the RNC Element Manager GUIapplication in RAS05.1 or the NetAct Administration of Measurementsapplication. The BTS channel element capacity measuring monitoring isalso possible via BTS EM.

The measurement interval for the BTS channel element capacitymeasurement in the RNC is selectable. The selection can be done usingthe RNC EM GUI or NetAct. In the BTS the measurement interval is fixedto 1 hour.

4.2.2 Activating BTS Channel Element Capacity Measuring

The measurement data transfer from BTS to RNC and NetAct is activatedeither by using the RNC EM GUI or the NetAct Administration ofMeasurements application. In the BTS the measuring is always active andresults can be viewed with the BTS EM regardless of data transfersettings.

4.2.3 Verifying BTS Channel Element Capacity Measuring

When the feature works as planned, the measurement data is collectedand stored in the PM databases and can be viewed with available PMtools.

4.2.4 Deactivating BTS Channel Element Capacity Measuring

The measurement data transfer from the BTS to the RNC and NetAct isdeactivated either by using the RNC EM GUI or the NetAct Administrationof Measurements application. In the BTS the measuring is always activeand results can be viewed with the BTS EM regardless of data transfersettings.





The related counters are described more in detail in WBTS Counters.

4.2.6 Architecture

For more information, see Section BTS Channel Element CapacityMeasuring feature description.

4.2.7 Capacity




5 RAN232: CPICH Ec/No CoverageMeasurements and Optimisation

5.1 CPICH Ec/No Coverage Measurements andOptimisation feature description

The CPICH Ec/No coverage measurements and optimisation feature hasthe feature number RAN232.

This feature is a part of the WCDMA RAN measure solution.

When the UE sends the 1A event triggered intra-frequency measurementreport to the SRNC in the MEASUREMENT REPORT (RRC) message,the CPICH Ec/No measuring is done. The received measurement reportcontains the cell-specific information about the CPICH Ec/No valuemapped from the CPICH Ec/Io reporting range by the UE.

The CPICH Ec/No measuring is done for the best SRNC side cell, whichcan be either one of the current active set cells or one of the eventtriggered cells.

To gather the data into a logical format the CPICH Ec/No measurementcan be split into classes in relation to the reported CPICH Ec/No value.These classes represent the measured quantity value area in dB. TableClasses for CPICH Ec/No coverage measurements below shows how theclasses are linked with the reported CPICH Ec/No values.

Table 7. Classes for CPICH Ec/No coverage measurements

Classes condition Measured quantityvalue area (dB)

Condition (reportedCPICH Ec/No value)

Class 9 CPICH Ec/Io < -24 CPICH_Ec/No _value = 0



RAN232: CPICH Ec/No Coverage Measurements and Optimisation

Table 7. Classes for CPICH Ec/No coverage measurements (cont.)

Classes condition Measured quantityvalue area (dB)

Condition (reportedCPICH Ec/No value)

Class 8 -24 ≤ CPICH Ec/Io < -22 1 ≤ CPICH_Ec/No _value <5



Class 5 -18 ≤ CPICH Ec/Io < -16 13 ≤ CPICH_Ec/No _value< 17





Class 0 -5 ≤ CPICH Ec/Io 39 ≤ CPICH_Ec/No _value≤ 49

When the RNC receives the 1A report from the UE, a classification countercorresponding to the reported CPICH Ec/No value is updated.


After the 3G network launch, the operator can tune the CPICH power to:

. increase the network capacity and coverage

. control the interference

The capacity gain in an interference limited case can be approximately 5%or higher since all common channels are set up with respect to the CPICHpower.

5.1.2 Compliance





System requirements



The software requirements are presented in the table SW requirements.



Release RN2.2 - - OSS4 - - - -








This feature has no interaction with other features.





RAN232: CPICH Ec/No Coverage Measurements and Optimisation

5.2 Main functionality of CPICH Ec/No CoverageMeasurements and Optimisation

5.2.1 Using CPICH Ec/No Coverage Measurements and Optimisation

The CPICH Ec/No coverage measurements and optimisation calculation isadded to the current soft handover measurement. Thus, the CPICH Ec/Nocoverage measurements and optimisation feature operates similarly asother network performance measurements. It is managed by using theRNC Element Manager GUI application in RAS05.1 or the NetActAdministration of Measurements application.

5.2.2 Activating CPICH Ec/No Coverage Measurements and Optimisation

The measurement is activated with the RNC EM GUI and/or NetAct.

5.2.3 Verifying CPICH Ec/No Coverage Measurements and Optimisation


5.2.4 Deactivating CPICH Ec/No Coverage Measurements andOptimisation

The measurement is deactivated with the RNC EM GUI or NetAct.


For more information on related counters, see RNC Counters for RAS05.1trial.

5.2.6 Architecture

For more information, see CPICH Ec/No Coverage Measurements andOptimisation feature description.

5.2.7 Capacity




6 RAN1054: Downlink Packet DataThroughput for Subscriber andEquipment Trace

6.1 Downlink Packet Data Throughput for Subscriberand Equipment Trace feature description

A new trace record is included in Subscriber and Equipment Tracesolution. This new record allows collecting RLC Acknowledged Mode data.

The RLC Acknowledged Mode Downlink record contains the followingdata for each Radio Bearer of the traced UE:

. Average buffer occupancy

. RLC activity time, i.e. time when there was RLC data to send

. PDU size

. Total number of transmitted PDUs

. Number of re-transmitted PDUs

. Number of discarded PDUs

. Number of received SDUs

. Number of transmitted SDUs

. Number of discarded SDUs

. SDU transfer delay

The Radio Bearer Trace Record will obtain the following UE QualityMeasurement related data for each Radio Bearer of the traced UE:



RAN1054: Downlink Packet Data Throughput for Subscriber andEquipment Trace

. Generation Time

. DCH ID

. UE Quality Reporting Period

. BLER

This feature will be part of WCDMA RAN Trace Solution (see FigureWCDMA RAN Trace Solution).

Figure 3. WCDMA RAN Trace Solution

RNC



RNCElement Manager

Reportgeneration

NetAct Northbound interface

NWI3: TRACE_REPORTRLC Data Included

MML: LocalTrace Activation

Core Network

lub

lub

Options Close

Radio 1

NokiaNetAct

TraceViewer

RANAPCN_INVOKE_TRACE

Activate Trace

RLCAM DL TraceRecords

Received data andbuffer occupancySent vs. not sent

data.Average Transfer

delay




This feature enables the operator to more accurately verify theperformance of the packet data Radio Bearers and to optimise the relatedparameters. Optimal parameters enable maximum radio interfacethroughput for all subscribers.


System Requirements


Software Requirements

RNC RN2.2

OSS OSS4.1

Hardware Requirements


Operator Requirements

None

End-User Requirements

This feature sets no additional end-user requirements.


This feature adds new content to Subscriber and equipment tracefunctionality which was introduced in RAN04 as the "Subscriber Trace"feature. The Subscriber Trace feature belongs to application software.





RAN1054: Downlink Packet Data Throughput for Subscriber andEquipment Trace

6.2 Main functionality of Downlink Packet DataThroughput for Subscriber and Equipment Trace


There are no new parameters related to this feature.

A more detailed description of the related counters is available in RAS05.1RNC Counters trial.

6.2.2 Architecture

Architecture of the feature is presented in Figure WCDMA RAN TraceSolution in Section Downlink Packet Data Throughput for Subscriber andEquipment Trace feature description.

6.2.3 Capacity

This feature has no special capacity effects for Trace. The existing Tracecapacity limitation of max. 16 Trace recoding sessions is also valid for thisfeature.



7 RAN190: Radio Connection PerformanceMeasurements for RLC TM and UM andOuter Loop Power Control

7.1 Radio Connection Performance Measurements forRLC TM and UM and Outer Loop Power Controlfeature description

The feature radio connection performance measurements for RLC TM andUM and outer loop power control has the feature number RAN190.

This feature extends the monitoring capabilities of the radio connection.That is, the RCPM measurement area is extended. The RCPM RLCmeasurement has been presented in RAS05. With this feature two newmeasurements are produced: the RCPM OLPC and RCPM UEQmeasurements.

The RCPM measurement area is optional. All RCPM measurements areunder the same option. The following new measured items are seen in thenew RCPM measurements:



RAN190: Radio Connection Performance Measurements for RLC TMand UM and Outer Loop Power Control

. For uplink the DCH-specific BLER, BER and Eb/No are derived fromthe outer loop power control (OLPC) algorithm (including the RCPMOLPC measurement).

. For connections using UM or TM RLC the downlink BLER isobtained by setting the UE quality (UEQ) measurement (includingthe RCPM UEQ measurement).

. The DL radio link transmission power is obtained from the dedicatedmeasurement report message received from the BTS. Themeasurement result is associated with the service (RAB) andtransport channel (DCH) carried on the radio link. The average,variance and outage percentage of the transmission power iscalculated for different traffic classes, bit rates and error targets(including the RCPM OLPC measurement).

In the RCPM OLPC/ RCPM UEQ measurements the classification forseparating the measured object level is used. The classification can bedone for RAB/RB by traffic classes with different bit rates. For moreinformation on the classification, see Connection type classification.


The RCPM OLPC and RCPM UEQ measurements extend the monitoringcapabilities to measure the uplink and downlink performance of the radioconnection between the BTS and the UE.

The RL transmission power calculation is useful for network capacityoptimising purposes.

7.1.2 Compliance



System requirements



The software requirements are presented in the table SW requirements.





Release RN2.2 - - OSS4 - - - -








The UEQ measurement can be started only for RBs using UM-RLC or thetransparent mode RLC. The RCPM RLC measurement is meant for AM-RLC connections.


With radio connection performance measurements for RLC TM and UMand outer loop power control, the measurement interval should not beshorter than 60 minutes.

Note that there are some limitations in large radio networks.

Note

NEMU (RNC):

The recommended maximum number of cells to be measured is 600.With this number of cells the load of NEMU stays on an acceptablelevel.




Note

NetAct:

Due to the large number of measured objects, the amount of RCPMdata exceeds the NetAct processing capacity if the measurements areactivated in all RNCs/NEMUs under a NetAct regional cluster. Thus,RCPM should be activated only in one RNC/NEMU at a time.

However, these restrictions are only an estimate, but at least the followingfactors affect the feature:

. the RCPM settings

. the traffic mix

. the settings for other RAN measurements

. the size of the network

. other measurements than the RAN measurements

. NetAct HW and the number of servers

. the SW build

. the number of users

7.2 Main functionality of Radio ConnectionPerformance Measurements for RLC TM and UMand Outer Loop Power Control

7.2.1 Using Radio Connection Performance Measurements for RLC TMand UM and Outer Loop Power Control

The feature radio connection performance measurements for RLC TM andUM and outer loop power control is managed by using the RNC ElementManager GUI application.

7.2.2 Activating Radio Connection Performance Measurements for RLCTM and UM and Outer Loop Power Control

This feature is part of the application software.



The RCPM includes the RCPM RLC, UEQ and OLPC measurements. TheRCPM RLC measurement has been implemented already in RAS05.

The measurement is activated with the RNC EM GUI.

The following parameters need to be defined when starting the RCPMUEQ or RCPM OLPC measurement:

. the measurement schedule, including period start/stop times andintervals

. the measured WCDMA cells

. the radio connection type, including radio access bearer and radiobearer type

. the handover mode selection to define how the calls in soft handoverare measured

When starting the measurement, the user must use these parameters todefine what types of calls are measured.

The feature radio connection performance measurements for RLC TM andUM and outer loop power control is managed by using the RNC ElementManager GUI application in RAS05.1. The measurement data is stored inthe NEMU database and it is transferred to NetAct.

7.2.3 Verifying Radio Connection Performance Measurements for RLC TMand UM and Outer Loop Power Control

When the feature works as planned, the measurement data is collectedand stored in the PM databases and can be viewed with the available PMtools.

7.2.4 Deactivating Radio Connection Performance Measurements for RLCTM and UM and Outer Loop Power Control

The measurements are deactivated and the measured objects can bechanged with the RNC EM GUI.


For more information on related counters, see RNC Counters for RAS05.1trial.




7.2.6 Architecture

Fore more information, see Radio Connection PerformanceMeasurements for RLC TM and UM and Outer Loop Power Control featuredescription.

7.2.7 Capacity

In a large radio network it may be necessary to select only a subset of theavailable measured objects, or in a restricted network area, to reduce theamount of data processed in NEMU (RNC) and sent to NetAct. For moreinformation, see Limitations and restrictions.

7.3 Connection type classification

The connection type is classified hierarchically for the RCPM OLPC andRCPM UEQ measurement as described in the following treepresentations.

Figure 4. RCPM OLPC

Signalling

Conversational

CS Voice

CS Transparent Data

Streaming

CS Non Transparent Data

PS RT Data

Interactive

PS NRT Data

Background

PS NRT Data



Figure 5. RCPM UEQ

Conversational

CS Voice

CS Transparent Data

Streaming

CS Non Transparent Data






8 RAN1163: Iu-PS ThroughputMeasurement for GTP Traffic

8.1 Iu-PS Throughput Measurement for GTP Trafficfeature description

The Iu-PS throughput measurement for GTP traffic feature has featurenumber RAN1163. This feature is a part of the WCDMA RAN measuresolution (see Figure Iu-PS throughput measurement for GTP traffic inWCDMA measure solution).



RAN1163: Iu-PS Throughput Measurement for GTP Traffic

Figure 6. Iu-PS throughput measurement for GTP traffic in WCDMA measuresolution

This feature introduces a new measurement, located in RNC, to follow theIu-PS interface traffic volumes and the number of GTP protocol specificevents. The measurement provides counters that updated per GTPU unitin RNC. The RNC specific or RAN total Iu-PS statistics can be calculatedby summing the GTPU specific counters in NetAct. The Iu-PS interfacetermination in RNC and the relation to GTPU units is described in FigureIu-PS interface termination in RNC.

RNC

lub

NokiaNetAct

PM: Measurementactivation

lu-CS lu-PS

Local MeasurementManagement

PM: Data Transfer

New: measurement: Iu-PSthroughput measurementfor GTP traffic

GTPU

Report generation

Reporter

RNCElement Manager

NetAct Northbound interface3GPP named counters



CS CoreNetwork

PS CoreNetwork

Network level reports:- Iu-PS interface totalthroughput- PS domain trafficvolumes per UMTS TC- Number of GTPtunnels

RNC levelCounters

Iub



Figure 7. Iu-PS interface termination in RNC

The GTP layer traffic volume is reported through following counters. Thecounters do not include IP, UDP or GTP transport layer headers, but onlythe user payload data.

. Total number of bytes received

. Total number of IP packets received

. Number of bytes received, UMTS TC Conversational (notsupported)

. Number of bytes received, UMTS TC Streaming

. Number of bytes received, UMTS TC Interactive

. Number of bytes received, UMTS TC Background

. Total number of bytes sent

. Total number of IP packets sent

. Number of bytes sent, UMTS TC Conversational (not supported)

. Number of bytes sent, UMTS TC Streaming

. Number of bytes sent, UMTS TC Interactive

. Number of bytes sent, UMTS TC Background

GTPU-1

GTPU-2

GTPU-n

Iu-PSPS core

RNC

There are 1-4 GTPU in RNC. The maximum throughputsupported by RNC over Iu-PS is 405 Mbit/s

One GTPU can handle both background and delay sensitivetraffic, if the feature RAN717 (IPQOS) is enabled. OtherwiseGTPU is dedicated based on UMTS traffic classes.




The counters that report the Iu-PS interface and GTPU protocolperformance calculate the number of sent and received echo messages,GTP error messages and number of tunnels.

The following events are reported through counters:

. Echo request received

. Echo response received

. Echo response sent

. Error indication received

. Error indication sent

. Extension header notification received

. Average number of GTP tunnels

. Peak number of GTP tunnels


The new measurement enables monitoring the Iu-PS resource usage anddimensioning the network resources based on the actual traffic volumes.

The information of PS traffic volumes can be used to dimension the Iu-PSinterface transmission capacity, plan the RNC capacity upgrades and toreport the PS domain traffic volumes in general for different businesspurposes. The maximum Iu-PS throughput supported by RNC is 405 Mbit/s, which is supported for HSDPA traffic in downlink. The RNC capacitystatement includes the GTP headers, which are not included to the countervalues.

8.1.2 Compliance



System requirements





The software requirements are presented in the Table SW requirements.

Table 10. RAS05.1 performance monitoring features


RAS05.1ED

RN2.2ED

- - OSS4.1CD set 2

- - - -




Operator needs to activate the measurement and select the measuredobjects.

End-user requirements

This feature sets no additional end-user requirements.


This feature supports monitoring the RAS05.1 feature “Iu-PS IP Quality ofService Support (DiffServ in GTPU)”. This feature can be used also in thecase the Iu-PS IP Quality of Service Support feature is not activated.


There is a limitation related to measurement management, which iscommon to all transport and HW related measurements in RNC. Thesemeasurements can not be activated from NetAct, but they need to beactivated separately for each RNC.




8.2 Main functionality of Iu-PS ThroughputMeasurement for GTP Traffic

8.2.1 Using the Iu-PS throughput measurement for GTP traffic

The Iu-PS throughput measurement is operated similarly as othertransport and HW related performance measurements in RNC. It ismanaged by using the RNC Element Manager GUI application in RAS05.1or alternatively using MML commands.

8.2.2 Activating the Iu-PS throughput measurement for GTP traffic

This feature is part of the application software. The measurement and thedata transfer from RNC to NetAct is activated either by using NEMeasurement Explorer application in the RNC Element Manager or usingZT2 MML command group. The measurement data can be viewed eitherlocally using NE Measurement Explorer or with NetAct reporting tools.

8.2.3 Verifying the Iu-PS throughput measurement for GTP traffic


8.2.4 Deactivating the Iu-PS throughput measurement for GTP traffic

The measurement and the data transfer from RNC to NetAct is deactivatedeither by using NE Measurement Explorer application in the RNC ElementManager or using ZT2 MML command group.


The related counters are described more in detail in RNC Counters –Transport and HW part in Nokia WCDMA RNC Product Documentation.

8.2.6 Architecture

For more information, see Figure Iu-PS throughput measurement for GTPtraffic in WCDMA measure solution.



8.2.7 Capacity







Related Topics

Automatic Definition of Neighbouring Cells featuredescription

Nokia NetAct Optimizer documentation in in Nokia NetAct ProductDocumentation for release OSS4.1.

RNC counter documentation in Nokia WCDMA RAN RNC ProductDocumentation for release RN2.2.

Main functionality of Automatic Definition of Neighbouring Cells

BTS Channel Element Capacity Measuring featuredescription

WBTS Counters in Nokia WCDMA BTS Product Documentation forrelease WBTS3.2.

Main functionality of BTS Channel Element Capacity Measuring

CPICH Ec/No Coverage Measurements andOptimisation feature description


Main functionality of CPICH Ec/No Coverage Measurements andOptimisation

Downlink Packet Data Throughput for Subscriberand Equipment Trace feature description

Main functionality of Downlink Packet Data Throughput for Subscriber andEquipment Trace



Related Topics

Radio Connection Performance Measurements forRLC TM and UM and Outer Loop Power Controlfeature description


Main functionality of Radio Connection Performance Measurements forRLC TM and UM and Outer Loop Power Control



Documents

RAS05.1 Performance Monitoring Features