activating and verifying ras05 1 features

WCDMA RAN, Rel. RU50 andRU50 EP1, OperatingDocumentation, Issue 04

Activating and VerifyingRAS5.1 Features DN0988647Issue 04AApproval Date 2014-11-28

Nokia Networks

The information in this document applies solely to the hardware/software product (“Product”) specifiedherein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may notbe used except for the purposes defined in the agreement between You and Nokia Solutions and Networks(“Agreement”) under which this document is distributed. No part of this document may be used, copied,reproduced, modified or transmitted in any form or means without the prior written permission of NokiaSolutions and Networks. If you have not entered into an Agreement applicable to the Product, or if thatAgreement has expired or has been terminated, You may not use this document in any manner and Youare obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and Youassume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part ofthe process of continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statementsconcerning the suitability, capacity, fitness for purpose or performance of the Product are given solely onan “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the rightto change any such information and statements without notice. Nokia Solutions and Networks has made allreasonable efforts to ensure that the content of this document is adequate and free of material errors andomissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correctionof such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Productwill be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TOANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THECONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BELIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OFERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not bedistributed or disclosed to any third parties without the prior written consent of Nokia Solutions andNetworks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this documentmay be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

f Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle thisproduct and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety andEnvironmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services weoffer, please contact us at Nokia Solutions and Networks for any additional information.

Activating and Verifying RAS5.1 Features

2 DN0988647 Issue: 04A

Table of ContentsThis document has 86 pages

Summary of changes..................................................................... 8

1 Introduction.................................................................................... 91.1 Introduction to RAS05.1 Feature Activation Instructions................91.1.1 RAS05.1 documentation for radio resource management and

telecom features.............................................................................91.1.1.1 Reference documentation............................................................ 101.1.2 RAS05.1 documentation for transmission and transport features....

111.1.2.1 Reference documentation............................................................ 121.1.3 RAS05.1 documentation for operability features..........................131.1.3.1 Reference documentation............................................................ 141.1.4 RAS05.1 documentation for performance monitoring features.... 151.1.4.1 Reference documentation............................................................ 161.1.5 RAS05.1 documentation for RNC solution features.....................171.1.5.1 Reference documentation............................................................ 171.1.6 BTS Solution Features Overview................................................. 181.1.6.1 BTS solution features overview....................................................181.1.6.2 Reference documentation............................................................ 191.2 Licensing...................................................................................... 20 2 Radio Resource Management and Telecom Feature Activation

Manuals........................................................................................222.1 Feature RAN134: Support for Tandem/Transcoder Free

Operation, Feature Activation Manual..........................................222.1.1 Activating support for tandem/transcoder free operation............. 222.1.1.1 Activating tandem/transcoder free operation............................... 222.1.1.2 Activating AMR codec set with AMR Codec Selection and with

TFO/TrFO features.......................................................................232.1.2 Verifying support for tandem/transcoder free operation............... 232.1.3 Deactivating tandem/transcoder free operation........................... 242.2 Feature RAN140: Load and Service Based IS/IF Handover,

Feature Activation Manual........................................................... 252.2.1 Activating Load and Service Based IS/IF Handover.................... 252.2.2 Verifying Load and Service Based IS/IF Handover...................... 272.2.2.1 Preconditions for load-based IF handover verification................. 272.2.2.2 Verifying load-based IF handover................................................ 282.2.2.3 Preconditions for service-based IS handover verification............ 292.2.2.4 Verifying service-based IS handover............................................312.2.3 Deactivating Load and Service Based IS/IF Handover................ 322.3 Feature RAN146: Power Balancing, Feature Activation Manual. 332.3.1 Activating Power Balancing..........................................................332.3.2 Verifying Power Balancing........................................................... 34


Issue: 04A DN0988647 3

2.3.3 Deactivating Power Balancing..................................................... 342.4 Features RAN242 and RAN409: Flexible Upgrade of NRT DCH

Data Rate and Throughput-based Optimisation of the PacketScheduler Algorithm, Feature Activation Manual......................... 35

2.4.1 Activating RAN242: Flexible Upgrade of NRT DCH Data Rate....352.4.1.1 Activating flexible upgrade of NRT DCH data date...................... 352.4.1.2 Verifying flexible upgrade of NRT DCH data rate.........................372.4.1.3 Deactivating flexible upgrade of NRT DCH data rate...................402.4.2 Activating RAN409: Throughput-based Optimisation of the Packet

Scheduler Algorithm.....................................................................402.4.2.1 Activating throughput-based optimisation of packet scheduler

algorithm...................................................................................... 402.4.2.2 Verifying throughput-based optimisation of the packet scheduler

algorithm...................................................................................... 432.4.2.3 Deactivating throughput-based optimisation of packet scheduler

algorithm...................................................................................... 442.5 Features RAN384 and RAN814: Emergency and Intelligent

Emergency Call Inter-System Handover, Feature ActivationManual......................................................................................... 45

2.5.1 Activating Emergency and Intelligent Emergency Call Inter-systemHandover......................................................................................45

2.5.2 Verifying Emergency and Intelligent Emergency Call Inter-SystemHandover......................................................................................46

2.5.2.1 Verifying Emergency Call Inter-system Handover........................462.5.2.2 Verifying Intelligent Emergency Call Inter-system Handover....... 472.5.3 Deactivating Emergency and Intelligent Emergency Call Inter-

system Handover......................................................................... 472.6 Feature RAN830: AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and

(5.9, 4.75), Feature Activation Manual......................................... 482.6.1 Activating AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75).

482.6.2 Verifying AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75)...

502.6.3 Deactivating AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9,

4.75)............................................................................................. 512.7 RAN827: AMR Service with HS-DSCH........................................522.7.1 Activating AMR Service with HS-DSCH.......................................522.7.2 Verifying AMR Service with HS-DSCH.........................................532.7.3 Deactivating AMR Service with HS-DSCH...................................542.8 Feature RAN1180: Wireless Priority Service, Feature Activation

Manual......................................................................................... 552.8.1 Activating Wireless Priority Service..............................................552.8.2 Verifying Wireless Priority Service............................................... 562.8.3 Deactivating Wireless Priority Service......................................... 582.9 HSDPA Mobility............................................................................592.9.1 Activating HSDPA Mobility........................................................... 592.9.2 Verifying HSDPA Mobility............................................................. 602.9.3 Deactivating HSDPA Mobility....................................................... 612.10 RAN839: HSDPA 16 Users per Cell.............................................62


4 DN0988647 Issue: 04A

2.10.1 Activating HSDPA 16 Users per Cell............................................622.10.2 Verifying HSDPA 16 Users per Cell..............................................632.10.3 Deactivating HSDPA 16 Users per Cell........................................642.11 RAN1164: HSPA Service Indicator...............................................642.11.1 Activating HSPA Service Indicator............................................... 642.11.2 Verifying HSPA Service Indicator................................................. 662.11.3 Deactivating HSPA Service Indicator........................................... 67 3 Operability Feature Activation Instructions...................................693.1 Feature RAN619: Flexible Connection of VPCs for WBTS Object

in RNC, Feature Activation Manual..............................................693.1.1 Activating flexible connection of VPCs for WBTS object in RNC.693.1.2 Verifying flexible connection of VPCs for WBTS object in RNC...713.1.3 Deactivating flexible connection of VPCs for WBTS object in RNC.

723.2 Features RAN801 and RAN1167: Radio Network Access

Regulation and Domain Specific Access Class Restriction,Feature Activation Manual........................................................... 72

3.2.1 Radio Network Access Regulation...............................................723.2.1.1 Activating Radio Network Access Regulation.............................. 723.2.1.2 Verifying Radio Network Access Regulation................................ 743.2.1.3 Deactivating Radio Network Access Regulation.......................... 753.2.2 Domain Specific Access Class Restriction...................................763.2.2.1 Activating Domain Specific Access Class Restriction.................. 763.2.2.2 Verifying Domain Specific Access Class Restriction....................773.2.2.3 Deactivating Domain Specific Access Class Restriction..............783.3 Activating RAN1453: Iu Link Break Protection.............................793.3 Summary of changes................................................................... 793.3.1 Activating RAN1453: Iu Link Break Protection.............................793.3.2 Verifying RAN1453: Iu Link Break Protection...............................803.3.3 Deactivating RAN1453: Iu Link Break Protection.........................81 4 BTS solution Feature Activation Instructions............................... 834.1 Activating RAN905: Flexi WCDMA BTS MHA CWA Support.......834.1.1 Activating RAN905: Flexi WCDMA BTS MHA CWA Support.......834.1.2 Verifying the RAN905: Flexi WCDMA BTS MHA CWA Support . 854.1.3 Deactivating the RAN905: Flexi WCDMA BTS MHA CWA Support

..................................................................................................... 86


Issue: 04A DN0988647 5

List of FiguresFigure 1 Verifying the RAN905: Flexi WCDMA BTS MHA CWA Support.........86


6 DN0988647 Issue: 04A

List of TablesTable 1 Radio resource management and telecom features.............................9Table 2 Transmission and transport features for RAS05.1..............................11Table 3 Operability features............................................................................ 13Table 4 Performance monitoring features....................................................... 15Table 5 RNC solution features........................................................................ 17Table 6 BTS solution features for RAS05.1.....................................................18Table 7 Sales item related to the feature RAN905: Flexi WCDMA BTS MHA

CWA Support......................................................................................83


Issue: 04A DN0988647 7

Summary of changesChanges between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.

g RNC196/RNC450 products related information is not valid for RU50.

Changes between issues 04 (2014-08-27, RU50 and RU50 EP1) and04A (2014-11-28, RU50 and RU50 EP1)

The RAN1164: HSPA Service Indicator feature has been updated and moved to thisdocument from Activating and Verifying RU10 Features document.

Changes between issues 03A (2014-06-04, RU50) and 04 (2014-08-27,RU50 and RU50 EP1)

General changes:

Activating AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75)

• The instructions have been updated.

Verifying AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75)


Deactivating AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75)


Changes between issues 03 (2014-02-28, RU50) and 03A (2014-06-04,RU50)

Reference documentation sections have been updated.

Summary of changes Activating and Verifying RAS5.1 Features

8 DN0988647 Issue: 04A

1 Introduction

1.1 Introduction to RAS05.1 Feature ActivationInstructions

1.1.1 RAS05.1 documentation for radio resource managementand telecom features

See the following table for more detailed information on WCDMA RAN functionality andfeature activation:

Table 1 Radio resource management and telecom features

Feature ID: Name

Functional area descriptions and otherrelated documents

Feature implementation

RAN140: Load and Service Based IS/IFHandover

WCDMA RAN RRM Handover Control

WCDMA RAN RRM Admission Control

Feature RAN140: Load and Service BasedIS/IF Handover, Feature Activation Manual

RAN1195: Multi-band Support for RNC WCDMA RAN RRM Handover Control This feature does not require activation

RAN242: Flexible Upgrade of NRT DCHData Rate

WCDMA RAN RRM Packet Scheduler


Features RAN242 and RAN409: FlexibleUpgrade of NRT DCH Data Rate andThroughput-based Optimisation of the PacketScheduler Algorith, Feature Activation Manual

RAN409: Throughput Based Optimisationof the Packet Scheduler Algorithm

WCDMA RAN RRM Packet Scheduler Features RAN242 and RAN409: FlexibleUpgrade of NRT DCH Data Rate andThroughput-based Optimisation of the PacketScheduler Algorithm, Feature ActivationManual

RAN1180: Wireless Priority Service WCDMA RAN RRM Handover Control


Feature RAN1180: Wireless Priority Service,Feature Activation Manual

RAN146: Power Balancing Power Control in WCDMA RAN


Feature RAN146: Power Balancing, FeatureActivation Manual

RAN830: AMR Codec Sets (12.2, 7.95,5.90, 4.75) and (5.90, 4.75)

WCDMA RAN RRMAdmission Control Feature RAN830: AMR Codec Set with AMRCodec Selection, Feature Activation Manual

RAN1224: HSDPA Dynamic PowerAllocation

WCDMA RAN HSDPA in BTS This feature does not require activation

RAN829: HSDPA Soft/softer Handoverfor Associated DPCH

WCDMA RAN RRM HSDPA This feature does not require activation

RAN828: HSDPA Serving Cell Change WCDMA RAN RRM HSDPA



This feature does not require activation

Activating and Verifying RAS5.1 Features Introduction

Issue: 04A DN0988647 9

Table 1 Radio resource management and telecom features (Cont.)

Feature ID: Name

Functional area descriptions and otherrelated documents


RAN827: HSDPA with SimultaneousAMR Voice Call

WCDMA RAN RRM HSDPA This feature does not require activation

RAN849: HSDPA Proportional FairResource Packet Scheduler

WCDMA RAN HSDPA in BTS This feature does not require activation

RAN839: HSDPA 16 Users per Cell WCDMA RAN HSDPA in BTS

WCDMA RAN RRM Packet Scheduler

Activating HSPA features

RAN223: UE Based A-GPS UsingExternal Reference Network

WCDMA RAN Location Services Activating RAN223, RAN875 and RAN1920:A-GPS Using External Reference Networkand Iu-PC SCTP Association Priority

RAN875: Network Based A-GPS UsingExternal Reference Network

WCDMA RAN Location Services Activating RAN223, RAN875 and RAN1920:A-GPS Using External Reference Networkand Iu-PC SCTP Association Priority

RAN815: Point-to-Point Iu-PC Interface WCDMA RAN Location Services This feature does not require activation

RAN814: Intelligent Directed EmergencyCall Inter-system Handover for US

WCDMA RAN Location Services Features RAN384 and RAN814: Emergencyand Intelligent Emergency Call Inter-SystemHandover, Feature Activation Manual

RAN1184: Configurable Location Shapes WCDMA RAN Location Services This feature does not require activation

RAN134: Support for Tandem/TranscoderFree Operation)

RNC Call Setup and Release Feature RAN134: Support forTandem/Transcoder Free Operation, FeatureActivation Manual

RAN1164: HSDPA Service Indicator There are no related documents Activating HSPA features

1.1.1.1 Reference documentation

For information on the parameters, counters and alarms related to each feature, see theManagement data section of the feature descriptions.

For parameter descriptions, see:

• WCDMA Radio Network Configuration Parameters• IP Configuration Plan Interface Parameters for Multicontroller RNC• OMS LDAP parameters• Flexi Transport Module Parameters• Flexi Multiradio BTS WCDMA Parameters• Multicontroller Radio Network Configuration Parameters• ATM Configuration Plan Interface Parameters• Frequently Used Parameters for SS7 signalling over IP• IP Configuration Plan Interface Parameters for Flexi Direct RNC• Radio Network Parameters in Flexi Direct• Reference Information Service in NOLS for RNC parameters

Introduction Activating and Verifying RAS5.1 Features

10 DN0988647 Issue: 04A

wcdma_ran_rel_ras05_1_feature_descriptions.pdf






For counter descriptions, see:

• RNC Counters - RNW Part• RNC Counters – Transport and HW Part• WBTS Counters• Reference Information Service in NOLS

For alarm descriptions, see:

• IPA-RNC Notices (0-999)• IPA-RNC Disturbances (1000-1999)• IPA-RNC Failure Printouts (2000-3999)• IPA-RNC Diagnosis Reports (3700-3999)• Multicontroller RNC, IPA-RNC and Flexi Direct RNC Base Station Alarms (7000-

9000)• Flexi WCDMA Base Station Faults• OMS Alarms

For key performance indicator descriptions, see:

• WCDMA RAN Key Performance Indicators

1.1.2 RAS05.1 documentation for transmission and transportfeatures


Table 2 Transmission and transport features for RAS05.1

Feature

Other related descriptions

Related instructions

RAN1086: AXC ATM interfaceoversubscription

WCDMA RAN ATM Transport Activating AXC ATM interfaceoversubscription

RAN324: Dynamic HSDPA TransportScheduling

WCDMA RAN ATM Transport Activating Dynamic HSDPA TransportScheduling

RAN1020: Route Selection - Activating Route Selection

RAN944: Use of GSM Transmission (FlexiWCDMA BTS)

- This feature does not require activation

RAN940: E1 Interface for Flexi WCDMA BTS - This feature does not require activation

RAN939: Flexbus Interface for Flexi WCDMABTS


RAN941: JT1 Interface for Flexi WCDMABTS


RAN946: T1 Interface for Flexi WCDMA BTS - This feature does not require activation


Issue: 04A DN0988647 11



















Table 2 Transmission and transport features for RAS05.1 (Cont.)

Feature

Other related descriptions

Related instructions

RAN942: SDH STM-1 Interface for FlexiWCDMA BTS


RAN935: BTS AAL2 Multiplexing for FlexiWCDMA BTS


RAN165: IP Based Control Plane at Iu andIur

WCDMA RAN and I-HSPA IPTransport

Activating IP Based Control Plane at Iuand Iur




• WCDMA Radio Network Configuration Parameters• IP Configuration Plan Interface Parameters for Multicontroller RNC• OMS LDAP parameters• Flexi Transport Module Parameters• Flexi Multiradio BTS WCDMA Parameters• Multicontroller Radio Network Configuration Parameters• ATM Configuration Plan Interface Parameters• Frequently Used Parameters of SS7 signalling over IP• IP Configuration Plan Interface Parameters for Flexi Direct• Radio Network Parameters in Flexi Direct• Reference Information Service in NOLS for RNC parameters








12 DN0988647 Issue: 04A










1.1.3 RAS05.1 documentation for operability features


Table 3 Operability features

Feature ID: Name

Functional Area Description


RAN1453: Iu Link Break Protection WCDMA RAN network protection Feature RAN1453: Iu Link BreakProtection, Feature ActivationManual

RAN619: Flexible Connection ofVPCs for WBTS Object in RNC

Shared RAN Feature RAN619: FlexibleConnection of VPCs for WBTSObject in RNC, Feature ActivationManual

RAN1167: Domain Specific AccessRestriction

WCDMA RAN access regulation Features RAN801 and RAN1167:Radio Network Access Regulationand Domain Specific Access ClassRestriction, Feature ActivationManual

RAN801: Radio NetworkRegulation Function

WCDMA RAN access regulation Features RAN801 and RAN1167:Radio Network Access Regulationand Domain Specific Access ClassRestriction, Feature ActivationManual

RAN1193: Plan based RNCATM/IP Configuration

This feature does not requireactivation.

RAN882: AXC ATM LayerConfiguration Management for BTS

WCDMA RAN configurationmanagement


RAN96: Automated RNS Split WCDMA RAN configurationmanagement


RAN1040: Data Backup for AXC WCDMA RAN configurationmanagement


RAN183: Remote User Event LogManagement for RNC

WCDMA RAN O&M security This feature does not requireactivation.

RAN615: Remote User Event LogManagement for AXC


RAN617: Remote User InformationManagement for AXC



Issue: 04A DN0988647 13

Table 3 Operability features (Cont.)

Feature ID: Name

Functional Area Description


RAN181: Remote User InformationManagement for RNC


RAN893: Alarm Architecture forFlexi WCDMA BTS

WCDMA RAN fault management This feature does not requireactivation.

RAN1302: Non-Performing CellRecovery

Administering radio networks Features RAN1302, RAN1810 andRAN1823: Non-Performing CellRecovery, Feature ActivationManual

RAN369: Automated IP AddressConfiguration for BTS

WCDMA RAN configurationmanagement


RAN1152: WCEL Lock and UnlockDuring RNW Plan Activation


RAN1091: BTS SW Managementwith RNC/NEMU Mediation

WCDMA RAN softwaremanagement


RAN817: Combined SWManagement for Flexi WCDMABTS and its Transport Module

WCDMA RAN softwaremanagement


RAN557: Combined HWManagement for Flexi WCDMABTS and its Transport Module

WCDMA RAN access regulation This feature does not requireactivation

RAN375: Read Only -Access forRNC & AXC Element Managers

WCDMA RAN network elementmanagement


RAN812: Local User Authenticationfor BTS


RAN1181: RNC NEMU Firewall This feature has no relateddocuments

This feature does not requireactivation

RAN1290: AXC Local AccountMass Change

WCDMA RAN O&M security This feature does not requireactivation




• WCDMA Radio Network Configuration Parameters• IP Configuration Plan Interface Parameters for Multicontroller RNC• OMS LDAP parameters


14 DN0988647 Issue: 04A

• Flexi Transport Module Parameters• Flexi Multiradio BTS WCDMA Parameters• Multicontroller Radio Network Configuration Parameters• ATM Configuration Plan Interface Parameters• Frequently Used Parameters for SS7 signalling over IP• IP Configuration Plan Interface Parameters for Flexi Direct RNC• Radio Network Parameters in Flexi Direct• Reference Information Service in NOLS for RNC parameters








1.1.4 RAS05.1 documentation for performance monitoringfeatures


Table 4 Performance monitoring features

Feature ID: Name

Functional Area Descriptions and otherrelated documents


RAN190: Radio ConnectionPerformance Measurementsfor RLC TM and UM andOuter Loop Power Control

RNC counters - RNW part This feature does not require activation.

RAN1163: Iu-PS ThroughputMeasurement for GTP Traffic

RNC Counters – Transport and HW Part This feature does not require activation.


Issue: 04A DN0988647 15



Table 4 Performance monitoring features (Cont.)

Feature ID: Name



RAN1054: Downlink PacketData Throughput forSubscriber and EquipmentTrace

WCDMA RAN subscriber and equipment trace This feature does not require activation.

RAN189: Automatic Definitionof Neighbouring Cells


RAN956: BTS ChannelElement Capacity Measuring

RNC counters - RNW part

WBTS Counters

This feature does not require activation.

RAN1153: ComplementaryCounters in RAS05.1


RAN232: CPICH Ec/NoCoverage Measurements andOptimisation









• IPA-RNC Notices (0-999)


16 DN0988647 Issue: 04A







• IPA-RNC Disturbances (1000-1999)• IPA-RNC Failure Printouts (2000-3999)• IPA-RNC Diagnosis Reports (3700-3999)• Multicontroller RNC, IPA-RNC and Flexi Direct RNC Base Station Alarms (7000-




1.1.5 RAS05.1 documentation for RNC solution features


Table 5 RNC solution features

Feature ID: Name



RAN607: Connectivity Support for 512 BTSs This feature does not have relateddocuments


RAN640: Star Configuration: 512 BTSs This feature does not have relateddocuments





• WCDMA Radio Network Configuration Parameters• OMS LDAP parameters• Flexi Transport Module Parameters• Flexi Multiradio BTS WCDMA Parameters• ATM Configuration Plan Interface Parameters• Frequently Used Parameters for SS7 signalling over IP• PRFILE Descriptions• Reference Information Service in NOLS for RNC parameters





Issue: 04A DN0988647 17







For information on license management, see WCDMA RAN License Operationdocument.

1.1.6 BTS Solution Features Overview1.1.6.1 BTS solution features overview

Table 6 BTS solution features for RAS05.1

Feature ID: Name

Descriptions

Instruction

RAN1062: IMA (Flexi WCDMA BTS) This feature does not haverelated documents


RAN1133: Configurable MHA alarms for Flexi BTS This feature does not haverelated documents


RAN900: Flexi WCDMA BTS This feature does not haverelated documents


RAN999: Flexi WCDMA BTS 1700/2100 This feature does not haverelated documents


RAN916: Flexi WCDMA BTS 900 This feature does not haverelated documents






RAN907: Antenna Line Supervision This feature does not haverelated documents


RAN1046: Feederless site solution for Flexi WCDMA This feature does not haverelated documents


RAN905: Flexi WCDMA BTS Nokia MHA Support This feature does not haverelated documents



18 DN0988647 Issue: 04A

Table 6 BTS solution features for RAS05.1 (Cont.)

Feature ID: Name

Descriptions

Instruction

RAN912: Licence Based BTS Channel Capacity This feature does not haverelated documents


RAN943: Synchronising WCDMA RAN (Flexi WCDMABTS)

This feature does not haverelated documents


RAN1000: Baseband Extension for Flexi WCDMA BTS This feature does not haverelated documents


RAN1002: Flexi WCDMA BTS 40 W Carrier PowerSupport



RAN1144: Flexi WCDMA BTS 8 W RF power limitation This feature does not haverelated documents


RAN1146: Flexi WCDMA BTS Horizontal Mounting Kit forGSM EDGE BTS



RAN1145: Flexi WCDMA BTS RF Module with AC InputPower



RAN1001: Flexi WCDMA BTS Second Carrier Support This feature does not haverelated documents


RAN1439: Distributed BTS solution This feature does not haverelated documents


RAN1469: Flexi Mounting Shields This feature does not requireactivation






Issue: 04A DN0988647 19








1.2 LicensingThe application software features (ASW) are under license key management. A licenseis a file that includes the feature information. Before a licensed feature can be activated,the license file needs to be transferred to and installed in the network element. Forinformation on transferring the license, see License Management Operations in RNC inWCDMA RAN License Operation. For information on installing the license, see Installinglicenses in the network element in Managing License-based Features.

g Some RNC-controlled features are activated using an RNC general parameter file(PRFILE) or a feature information control file (FIFILE). For details, seeParameter-based Option Management in WCDMA RAN License Operation.

A license can be installed using NetAct or a local MML (IPA-RNC) or SCLI (mcRNC)interface. If it is installed using NetAct, the licensed feature state is automatically set toON state. If the MML/SCLI interface is used, the default value is OFF, and you need toset the feature to ON state manually. For information on feature states, see FeatureStates in WCDMA RAN License Operation. The license-related MML commands aredescribed in W7 - License and Feature Handling.

For details on license management in WCDMA RAN, see License Management inWCDMA RAN and License Management Principles.

For details on managing the license-based features, see Managing License-basedFeatures.

License management in mcRNCFor details on the mcRNC-specific license management, see License Management inmcRNC in WCDMA RAN License Operation.


20 DN0988647 Issue: 04A

License management in WBTSFor details on the WBTS-specific license management, see WCDMA BTS LicenseManagement Functionality Description in WCDMA RAN License Operation.


Issue: 04A DN0988647 21

2 Radio Resource Management and TelecomFeature Activation Manuals

2.1 Feature RAN134: Support for Tandem/TranscoderFree Operation, Feature Activation Manual

2.1.1 Activating support for tandem/transcoder free operation2.1.1.1 Activating tandem/transcoder free operation

Purpose

Follow the procedure below to configure and activate the Support forTandem/Transcoder Free Operation feature in the network.

Before you start

This feature belongs to application software.

Ensure that you have a valid licence (FIFILE licence). For more information on licensing,see Licensing chapter.

For more information on the feature, see Section Transcoder Free Operation (TrFO) andTandem Free Operation (TFO) in WCDMA Call Setup and Release.

1 Open the OMS Element Manager and go to Tree View.Expand the topology tree of the RNC.

2 Select Edit Parameters in the RNAC object.

3 Configure the PeriodULRCAMR parameter in the RNAC object.Under the Admission Control tab, set the PeriodULRCAMR parameter. It can havethe following values:

• 255 - TFO/TrFO support is disabled• 0...254 - TFO/TrFO support is enabled

For more information on RNC object handling, see Modifying RNC parameters.

Expected outcome

The Support for Tandem/Transcoder Free Operation feature is activated in the RNCcontrolled network.

Parameters related to tandem/transcoder free operation

RNC parameter: Period for CS AMR RRC TFC control requests (PeriodULRCAMR)

Radio Resource Management and Telecom FeatureActivation Manuals


22 DN0988647 Issue: 04A

2.1.1.2 Activating AMR codec set with AMR Codec Selection and withTFO/TrFO features

Purpose

Follow the procedure below to activate the supported AMR codec sets in WCDMA RAN.

Before you start

Configure the MSS so that it initiates TFO/TrFO AMR calls with a particular AMR modeset.

1 Ensure that a TFO/TrFO compatible AMR codec set is configured in the MSS.The AMR codec set used in the MSC Server must be TFO compatible with the AMRcodec sets that are supported and configured to be used in the RNC. Therefore theMSS has to use one of the following AMR mode sets in its AMR RAB assignmentwhen the TFO/TrFO is (possibly) used for the call, depending on which AMR featuresare activated in RNC:

• NB-AMR (12.2)• NB-AMR (12.2, 7.95, 5.9, 4.75) – requires that the AMR Codec Sets (12.2, 7.95,

5.90, 4.75) and (5.90, 4.75) feature is enabled in the RNC• WB-AMR mode set which includes the mode set (12.65, 8.85, 6.6) – requires that

the Wideband AMR Codec Set (12.65, 8.85, 6.6) feature is enabled in the RNC

Use the MML commands of the Radio Network Controller Parameter Handling in theMSS, E2 command group. For more information on configuration in the MSS, seeMSC/HLR documentation.Further informationIn MSS Iu UP version 2 should be activated. It can be checked and changed with E2MML command in MSS.



4 Set the value of the PeriodULRCAMR parameter to a value other than 255. Therecommended value is '1'.

Further information

After activating the feature, there is no need to reset the RNC.

2.1.2 Verifying support for tandem/transcoder free operationPurpose

Follow the procedure below to verify that the Support for Tandem/Transcoder FreeOperation feature and the supported AMR codec sets are activated in the WCDMA RAN.

Activating and Verifying RAS5.1 Features Radio Resource Management and Telecom FeatureActivation Manuals

Issue: 04A DN0988647 23

1 Use the following MML command in the MGW to output the measurementparameters and their values:ZJKH:VID=<VMGW ID>,:TTYP=<TERM TYPE>,:TER=<TERMINATION ID>,;

2 Check the printout of the command for the values of the followingmeasurement parameters:

• TFO Status

• TrFO status

Expected outcome

The printout displays TFO status (unit) as TRFO and TrFO status (value) ON, forexample:

Measurement Parameter Value Unit Measurement Parameter Value Unit

----------------------------COMMON--------------------------

TrFO status........ ON -

TFO Status........ OFF TRFO Call Type......... Speech -

2.1.3 Deactivating tandem/transcoder free operationPurpose

Follow the procedure below to deactivate the Support for Tandem/Transcoder FreeOperation feature in the network.

Before you start

Before you deactivate the feature in the RNC, the MSS shall be configured so that itdoes not attempt to establish any TFO/TrFO AMR call.



3 Configure the PeriodULRCAMR parameter in the RNAC object.Under the Admission Control tab, modify the value of the PeriodULRCAMRparameter to 255.

Expected outcome

The Support for Tandem/Transcoder Free Operation feature is deactivated in the RNCcontrolled network.



24 DN0988647 Issue: 04A

2.2 Feature RAN140: Load and Service Based IS/IFHandover, Feature Activation Manual

2.2.1 Activating Load and Service Based IS/IF HandoverPurpose

Follow the procedure below to configure and activate the Load and Service Based IS/IFHandover feature in the RNC. For more information on the feature, see SectionIntroduction to IMSI-based handover in Handover Control.

g This feature must be activated before enabling the handover control-relatedCommon load measurement over Iur function.

This feature belongs to application software. This feature is controlled with the FIFILEparameter and its value is ON by default. For information, see Licensing.

1 Open the OMS Element Manager.

2 Go to Topology and expand ROOT.

3 Configure the RNC/RNMOBI object with the SLHO parameters.You can specify the SLHO-related call types with the following parameters:

• SLHOUseBackgroundPSNRTData

• SLHOUseConvCSSpeech

• SLHOUseConvCSTData

• SLHOUseConvPSRTData

• SLHOUseConvPSSpeech

• SLHOUseInteractivePSNRTData

• SLHOUseStreamCSNTData

• SLHOUseStreamPSRTData

You can specify the preferred RAT or WCDMA layer for SLHO-related call types withthe following parameters:

• SLHOProfileBackgroundPSNRTData

• SLHOProfileConvCSSpeech

• SLHOProfileConvCSTData

• SLHOProfileConvPSRTData

• SLHOProfileConvPSSpeech

• SLHOProfileInteractivePSNRTData

• SLHOProfileStreamCSNTData

• SLHOProfileStreamPSRTData

For more information on RNC object handling, see Modifying RNC parameters inAdministering radio networks.


Issue: 04A DN0988647 25

4 Create or modify the Inter-Frequency Measurement Control (FMCI) and Inter-System Measurement Control (FMCG) objects.Configure and check the SLHO-related FMCI and FMCG parametrization. For moreinformation on Frequency Measurement Control (FMC) object handling, see Creatingfrequency measurement control and Modifying frequency measurement controlparameters in Administering radio networks.

5 Create or modify the WCDMA Cell (WCEL) objects.Configure and check the SLHO-related WCEL parameters.You can specify which load measurements can trigger load-based handover with thefollowing parameters:

• LHOWinSizeONInterference

• LHOWinSizeONResRateSC

• LHOWinSizeONCapaReqRejRate

• LHOWinSizeONHardBlocking

Use the LHONumbUEInterFreq parameter to enable load-based inter- frequencyhandover.Use the LHONumbUEInterRAT parameter to enable load-based inter-RAT handover.Use the ServHOPeriodInterFreq parameter to enable service-based inter-frequency handover.Use the ServHOPeriodInterRAT parameter to enable service-based inter- RAThandover.The default value of the above parameters is 0 (SLHO disabled).For more information on WCEL handling, see Creating a WCDMA cell and ModifyingWCDMA cell parameters in Administering radio networks.

6 Create or modify the Inter-Frequency Handover Path (HOPI) and Inter-SystemHandover Path (HOPG) objects.Configure and check the SLHO-related HOPI and HOPG parametrization. For moreinformation on HOP object handling, see Creating handover path and Modifyinghandover path parameters in Administering radio networks.

7 Create or modify the Inter-Frequency Adjacency (ADJI) objects.Configure and check the neighboring cell configuration according to the networkplanning. Check the SLHO-related parameters from the ADJ objects. For moreinformation on ADJI handling, see Creating an internal adjacency for a WCDMA celland Modifying WCDMA cell adjacencies in Administering radio networks.

Expected outcome

The Load and Service Based IS/IF Handover feature is activated in the RNC controllednetwork.

Further information

After activating, there is no need to reset the RNC.



26 DN0988647 Issue: 04A

The Core Network (CN) can send RANAP: Service Handover IE to RNC message, whichimproves the operation of the SLHO. However, this message is not a must. For moreinformation on the related parameters, see WCDMA Radio Network ConfigurationParameters.

2.2.2 Verifying Load and Service Based IS/IF Handover2.2.2.1 Preconditions for load-based IF handover verification

Purpose

Follow the procedure below to activate the Load-Based IF Handover feature forbackground PS NRT calls in the RNC and DL Scrambling Code Reservation Rate triggerfor a WCEL.

Please note that the following procedure is an example to configure the feature in acertain way and to verify the functionality with that certain configuration.

For more information on the related parameters, see Section Activating Load andService Based IS/IF Handover.

Before you start

Before activating this feature, make sure that the Radio Network (RNW) is alreadycreated.



3 Verify that the Inter-Frequency Measurement Control (FMCI) is created and alltriggers are disabled (to avoid other Inter-Frequency Handover (IFHO)triggers).For more information on Frequency Measurement Control (FMC) object handling,see Creating frequency measurement control and Modifying frequency measurementcontrol parameters in Administering radio networks.To disable the triggers turn off the following RNC/FMCI parameters:

• IFHOcauseCPICHEcNo• IFHOcauseCPICHrscp• IFHOcauseTxPwrDL• IFHOcauseTxPwrUL• IFHOcauseUplinkQuality• IMSIbasedIFHO

4 Verify that Inter-Frequency Handover Path (HOPI) is created.For more information on HOP object handling, see Creating handover path andModifying handover path parameters in Administering radio networks.


Issue: 04A DN0988647 27

5 Create the Inter-Frequency Adjacency (ADJI) object.Configure and check the neighboring cell configuration according to the networkplanning. For more information on ADJI handling, see Creating an internal adjacencyfor a WCDMA cell and Modifying WCDMA cell adjacencies in Administering radionetworks.

6 Verify that the Compressed mode master switch parameter is set to 'Used'(RNC/RNFC parameter).

7 Set the Service profile for background PS NRT data in SLHO parameter to'WCDMA Micro layer' (RNC/RNMOBI parameter).

8 Set the Use of SLHO for background PS NRT data parameter to 'Load HO'(RNC/RNMOBI parameter).

9 Verify that the CM allowed for NRT connection in SLHO is set to 'allowed'(RNC/RNFC parameter).

10 Change the Number of UEs in inter-frequency load HO parameter's value toother than '0' (WCEL/Handover Control parameter).

11 Change the Window size for DL SC reservation rate measurement to startLHOs parameter's value to other than '0' (WCEL/Handover Control parameter).

Expected outcome

The Load-Based IF Handover feature is activated in the RNC controlled network.

2.2.2.2 Verifying load-based IF handover

Purpose

Follow the procedure below to verify that the Load-Based IF Handover feature isoperating in the network for background NRT calls, and the DL Scrambling CodeReservation Rate is used for triggering the load state in a cell.

Before you start

For a successful test, the following environment setup is needed:

• 2 WCDMA cellsOne operates on frequency F1 and another one on F2.

• ADJI defined between the two cells.• Cell on F1 is defined as a macro cell (HCS priority 0…3).

The HOPI object defines the HCS priority of a neighboring cell.• Cell on F2 is defined as a micro cell (HCS priority 4…7).

The HOPI object defines the HCS priority of a neighboring cell.



28 DN0988647 Issue: 04A

For more information on the preliminary preparation needed, see Section Preconditionsfor load-based IF handover verification.

1 Set the Load HO reservation rate of DL spreading codes parameter to a valueof 10% (WCEL/Handover Control parameter).This is enough for triggering a Load HO state in a non-HSDPA cell with just one PSNRT DL:384 call. (With 2 SCCPCH configuration, common channels reserve 5/128codes. DL:384 DCH reserves 16/128 codes. Altogether 21/128 are reserved, whichis greater than 10% of all codes.)

2 Activate measurement M1008 Intra-System Handover from RNW MeasurementManagement using a 15 minute interval.Wait until a measurement interval starts, that happens in every 15 minutes afterstarting the measurement.

3 Make a PS NRT (Background) call (DL bit rate 64) in the WCDMA macro cell.Let the call continue for longer than the value of Load handover minimum NRT DCHallocation time (default is 20 seconds).

4 Upgrade the DL bit rate to 384 kbps to trigger load-based HO state in the cell.

5 Verify that the PS NRT (Background) call is handed over to the neighboringWCDMA micro cell after the load state has been 'on' for the time defined byWindow size for DL SC reservation rate measurement to start LHOs.

6 Wait until the measurement period ends and the measurement data istransferred from OMU to NEMU.Data transfer takes no more than 5 minutes after the measurement period ends.

7 Use the RNW Measurement Presentation application to verify the appropriatecounters (Measurement type/1008 Intra System Handover/M1008C174 &M1008C186).Verify that the values of the counters M1008C174 LOAD BASED IFHO ATTEMPTSCAUSED BY RESERVATION RATE SC FOR NRT and M1008C186 SUCCESSFULLOAD BASED IFHO CAUSED BY RESERVATION RATE SC FOR NRT are bothupdated by one if one load-based IF handover was performed.

2.2.2.3 Preconditions for service-based IS handover verification

Purpose

Follow the procedure below to configure and activate the Service-Based IS Handoverfeature in the network.

Please note that the following procedure is an example to configure the feature in acertain way and to verify the functionality with that certain configuration.


Issue: 04A DN0988647 29

For more information on the related parameters, see Section Activating Load andService Based IS/IF Handover.

Before you start

Before activating this feature, make sure that the RNW is already created.



3 Verify that the Compressed mode master switch parameter is set to 'Used'(RNC/RNFC parameter).

4 Verify that the Inter-System Measurement Control (FMCG) is created and alltriggers are disabled.For more information on Frequency Measurement Control (FMC) object handling,see Creating frequency measurement control and Modifying frequency measurementcontrol parameters in Administering radio networks.To disable the triggers turn off the following RNC/FMCG parameters:

• GSMcauseCPICHEcNo• GSMcauseCPICHrscp• GSMcauseTxPwrDL• GSMcauseTxPwrUL• GSMcauseUplinkQuality• IMSIbasedGsmHo

5 Verify that Inter-System Handover Path (HOPG) is created.For more information on HOP object handling, see Creating handover path andModifying handover path parameters in Administering radio networks.

6 Create the Inter-System Adjacency (ADJG) object.Configure and check the neighboring cell configuration according to the networkplanning. For more information on ADJG handling, see Creating an internaladjacency for a WCDMA cell and Modifying WCDMA cell adjacencies inAdministering radio networks.



30 DN0988647 Issue: 04A

7 Verify that Handover of AMR Service to GSM parameter is set to 'Yes’(RNC/RNMOBI parameter).

8 Set the Service profile for conversational CS speech in SLHO parameter to'GSM' (RNC/RNMOBI parameter).

9 Set the Use of SLHO for conversational CS speech parameter to 'Service HO'(RNC/RNMOBI parameter).

10 Set the Period to start inter-RAT service HOs parameter's value to somethingother than '0' (for example, 10 seconds) (WCEL/Handover Control parameter).

11 Deactivate the sending of the Service HO Information Element (IE) from the CScore network using the SPEECH_CALL_PREF (029:0016) PRFILE parameterwith the commands of the ED and WO MML command groups. If the IE isdeactivated, the feature works as it is defined in the RNC.

Expected outcome

The Service-Based IS Handover feature is activated in the RNC controlled network.

2.2.2.4 Verifying service-based IS handover

Purpose

Follow the procedure below to verify that the Service-Based IS Handover feature isoperating in the network.

Before you start

For more information on the preliminary preparation needed, see Section Preconditionsfor service-based IS handover verification.

1 Activate measurement M1010 Inter-System Handover from RNW MeasurementManagement using a 15 minute interval.Wait until a measurement interval starts, that happens in every 15 minutes afterstarting the measurement.

2 Make an AMR call in the WCDMA.

3 Verify that the AMR call is handed over to the GSM network after the timedefined by Period to start inter-RAT service HOs.

4 Wait until the measurement period ends and the measurement data istransferred from OMU to OMS.Data transfer takes no more than 5 minutes after the measurement period ends.


Issue: 04A DN0988647 31

5 Use the RNW Measurement Presentation application to verify the appropriatecounters (Measurement type/1010 Inter System Handover/M1010C141 &M1010C153).Verify that the values of the counters M1010C141 SERVICE BASED ISHOATTEMPTS FOR RT and M1010C153 SUCCESSFUL SERVICE BASED ISHO FORRT are both updated by one if one service-based IF handover was performed.

2.2.3 Deactivating Load and Service Based IS/IF HandoverPurpose

Follow the procedure below to deactivate the Load and Service Based IS/IF Handoverfeature in the RNC.



3 Configure the RNC/RNMOBI object with the SLHO parameters.You can disable the SLHO functionality with the following parameters:

• SLHOUseBackgroundPSNRTData

• SLHOUseConvCSSpeech

• SLHOUseConvCSTData

• SLHOUseConvPSRTData

• SLHOUseConvPSSpeech

• SLHOUseInteractivePSNRTData

• SLHOUseStreamCSNTData

• SLHOUseStreamPSRTData

For more information on RNC object handling, see Modifying RNC parameters inAdministering radio networks.

4 Modify the WCDMA Cell (WCEL/Handover Control) objects.You can disable the load measurements with the following parameters:

• LHOWinSizeONInterference

• LHOWinSizeONResRateSC

• LHOWinSizeONCapaReqRejRate

• LHOWinSizeONHardBlocking

For more information on WCEL handling, see Creating a WCDMA cell and ModifyingWCDMA cell parameters in Administering radio networks.

Expected outcome

The Load and Service Based IS/IF Handover feature is deactivated in the RNCcontrolled network.



32 DN0988647 Issue: 04A

Further information

After deactivating the feature, set the feature state to OFF. For more information, seeSection Removing licenses from the network element in License-based FeatureManagement.

After deactivation, there is no need to reset the RNC.

2.3 Feature RAN146: Power Balancing, FeatureActivation Manual

2.3.1 Activating Power BalancingPurpose

Follow the procedure below to configure and activate the Power Balancing feature in theRNC.

This feature belongs to application software. This feature is controlled with the FIFILEparameter and its value is ON by default. For information, see Licensing.

Before activating the feature, set up the power balancing algorithm in the BTS and thereference power calculation algorithms in the RNC. For more information, see SectionPower balancing algorithm in Power Control.


2 Expand the RNC object.

3 Configure the RNFC object:

a) Right click on the RNFC object and select Edit Parameters.b) Set the value of the PowerBalancing parameter to Power Balancing is in use

For more information on RNFC object handling, see Section Editing RNFCparameters in Administering WCDMA Radio Networks.

Expected outcome

Feature Power Balancing is activated in the network controlled by the RNC.

Further information

After activation, there is no need to reset the RNC.

For more information on the related parameters, see WCDMA Radio NetworkConfiguration Parameters.


Issue: 04A DN0988647 33

managing_license_based_features_in_ipa_rnc.pdf

2.3.2 Verifying Power BalancingPurpose

Follow the procedure below to verify that the Power Balancing feature is activated in theRNC.

1 Open the RNW Measurement Management application.

2 Activate the 1005 L3Iub measurement in the RNW and BTS measurementswindow.Wait until the measurement data collection starts, for example, wait 15 full minutes if15-minute interval is used.

3 Make one AMR call.

4 Add a new radio link to a cell under another WBTS in order to create a SoftHandover situation.Power balancing is initiated in Soft Handover.

5 Release the AMR call.

6 Wait until the measurement data gets collected, for example, wait 15 fullminutes if 15-minute interval is used.

7 Open the RNW Measurement Presentation application.

8 Check that the following counter has been updated:M1005C149: ALL IUB DL POWER CONTROL MESSAGES IN SRNC

2.3.3 Deactivating Power BalancingPurpose

Follow the procedure below to deactivate the Power Balancing feature in the RNC.



34 DN0988647 Issue: 04A


2 Expand the RNC object.

3 Configure the RNFC object:

a) Right click on the RNFC object and select Edit Parameters.b) Set the value of the PowerBalancing parameter to Power Balancing is not in

use.

For more information on RNFC object handling, see Section Editing RNFCparameters in Administering WCDMA Radio Networks.

Expected outcome

The Power Balancing feature is deactivated in the network controlled by the RNC.

Further information

After deactivation, there is no need to reset the RNC.

2.4 Features RAN242 and RAN409: Flexible Upgrade ofNRT DCH Data Rate and Throughput-basedOptimisation of the Packet Scheduler Algorithm,Feature Activation Manual

2.4.1 Activating RAN242: Flexible Upgrade of NRT DCH DataRate

2.4.1.1 Activating flexible upgrade of NRT DCH data date

Purpose

Follow this procedure to configure and activate the Flexible Upgrade of NRT DCH DataRate feature in the network.

Before you start

This feature belongs to application software. Ensure that you have a valid licence(FIFILE licence).


Issue: 04A DN0988647 35


2 Configure the RNC object.Create or modify the RNC object by setting the value of the FlexUpgrUsageparameter to ON. You can specify the data rate and throughput using the parametersrelated to the flexible upgrade of NRT DCH data rate. For more information, see theparameters of this section.For more information on RNC object handling, see Section Modifying RNCparameters in Radio Network Administration.

3 Configure the WBTS object.Create or modify the WBTS object by using the DLORLAveragingWindowSize andPSRLAveragingWindowSize parameters.For more information on WBTS object handling, see Section Modifying WCDMA BTSparameters in Radio Network Administration.

Expected outcome

The upgrade of NRT DCH Data Rate and Throughput-based Optimisation of PacketScheduler Algorithm feature is activated in the network that is controlled by the RNC.

Parameters related to flexible upgrade of NRT DCH data rate

The following parameters are related to the feature.

RNC object:

• Window size for the high throughput measurement (DCHUtilHighAveWin)• Threshold below the NRT DCH data rate (DCHUtilHighBelowNRTDataRateThr)• Time to trigger for the high throughput measurement

(DCHUtilHighTimeToTrigger)• Dynamic usage of UL NRT DCH HSDPA return channel

(DynUsageHSDPAReturnChannel)• Usage of the Flexible Upgrade of the NRT DCH data rate (FlexUpgrUsage)• Downlink traffic volume measurement high threshold (TrafVolThresholdDLHigh)• Traffic volume threshold for downlink NRT DCH bit rates

(TrafVolThresholdDLHighBitRate)• Traffic volume threshold for DL NRT DCH of 8 kbps

(TrafVolThresholdDLHighDCH8)• Traffic volume threshold for DL NRT DCH of 16 kbps





(TrafVolThresholdDLHighDCH256)



36 DN0988647 Issue: 04A

• Uplink traffic volume measurement high threshold (TrafVolThresholdULHigh)• Traffic volume threshold for uplink NRT DCH bit rates

(TrafVolThresholdULHighBitRate)• Traffic volume threshold for UL NRT DCH of 8 kbps

(TrafVolThresholdULHighDCH8)• Traffic volume threshold for UL NRT DCH of 16 kbps





(TrafVolThresholdULHighDCH256)

WBTS object:

• Tx power of radio link averaging window size for DLO(DLORLAveragingWindowSize)

• Tx power of radio link averaging window size for PS (PSRLAveragingWindowSize)

For a list of related parameters, see WCDMA Radio Network Configuration Parameters.


2.4.1.2 Verifying flexible upgrade of NRT DCH data rate

Purpose

Follow the procedure below to verify the activation of the Flexible Upgrade of NRT DCHData Rate feature.

Before you start

Check that one cell WCEL A is active in the WBTS and configure it according to thefollowing:

• Set the HLR QOS profile to at least UL384/DL384.• Set the initial bit rate for PS-data call to 64/64. The minimum bit rate can be 8 kbps.• Set the bit rate for NRT DCH to the value OFF with the BitRateSetPSNRT RNC

parameter.• Set the FlexUpgrUsage RNC parameter to the value ON to enable flexible upgrade.• Set the RNC parameters DCHUtilHighTimeToTrigger and DCHUtilHighAveWin to a

suitable value. These together define the supervision period when throughput has tobe above the threshold to trigger an upgrade.

• Note that in initial bit rate allocation, the high threshold is set with theTrafVolThresholdDLHigh / TrafVolThresholdULHigh RNC parameter even if Flexibleupgrade is enabled.

Repeat the verification steps three times:

1. with FlexUpgrUsage = OFF to see the difference2. using DL data


Issue: 04A DN0988647 37

3. using UL dataFor UL data, the corresponding RNC parameters are TrafVolThresholdULHigh andTrafVolThresholdULHighBitRate. Ignore steps 4 and 5 during the UL test.

Modify the DCHUtilHighTimeToTrigger and DCHUtilHighAveWin RNC parametersbetween repetitions to find a suitable value for the supervision period before an upgradeis triggered.

Use a suitable UDP/FTP application for sending specific amounts of data to UL/DL.



38 DN0988647 Issue: 04A

1 Start a PS NRT call and data transfer with low throughput ping in WCEL A.

2 When the initial bit rate is assigned, start FTP data transfer with a higherthroughput than the one set in the TrafVolThresholdDLHighBitRate parameter.

3 When the upgrade happens (after DCHUtilHighTimeToTrigger +DCHUtilHighAveWin), keep the FTP throughput higher than the one set inTrafVolThresholdDLHighBitRate for the allocated bit rate.

4 When the RAB maximum bit rate is achieved, attenuate WCEL A and follow inNethawk 3G analyser that the UE is moved to DyLo (or follow with Exchange2000 (E2K) that the service is downgraded). Alternatively, use an incomingAMR to make the downgrade happen.

5 Decrease attenuation in WCEL A. When the UE leaves DyLo range (or AMR isended), it is upgraded.

6 Stop data transfer so that the state transition to Cell-FACH happens.

7 Start data transfer with low throughput ping.

8 When the initial bit rate is assigned, start the FTP data transfer with a higherthroughput than the one set in the TrafVolThresholdDLHighBitRate parameter.

9 When the upgrade happens, keep FTP throughput higher than the one set inTrafVolThresholdDLHighBitRate for the allocated bit rate.

10 Stop the data transfer and let the UE go to Cell-FACH state.

11 Start data transfer with high throughput FTP transfer.

12 Follow with E2K that the upgrade to high bit rate is triggered, and trafficvolume measurement is released if RB maximum bit rate is allocated.

13 Release the PS call.

Expected outcome

1. Initial capacity request is successful, and upgrade happens with flexible upgrade.2. Upgrade from a bit rate other than the initial bit rate is successful (flexible upgrade

occurs after Dylo is removed).3. Capacity request from Cell-FACH is successful.4. PS data throughput is as expected.


Issue: 04A DN0988647 39

5. There are no unexpected alarms.

2.4.1.3 Deactivating flexible upgrade of NRT DCH data rate

Purpose

Follow this procedure to deactivate the flexible upgrade of NRT DCH data rate feature.


2 Configure the RNC object.Modify the RNC object by setting the value of the FlexUpgrUsage parameter toOFF.For more information on RNC object handling, see Section Modifying RNCparameters in Radio Network Administration.

3 Configure the WBTS object.Modify the WBTS object by setting the value of the DLORLAveragingWindowSizeand PSRLAveragingWindowSize parameters to 0.For more information on WBTS object handling, see Section Modifying WCDMA BTSparameters in Radio Network Administration.

Expected outcome

The flexible upgrade of NRT DCH data rate feature is deactivated in the network that iscontrolled by the RNC.

2.4.2 Activating RAN409: Throughput-based Optimisation of thePacket Scheduler Algorithm

2.4.2.1 Activating throughput-based optimisation of packet scheduleralgorithm

Purpose

Follow this procedure to configure and activate the throughput-based optimisation ofpacket scheduler algorithm feature in the network.

Before you start




40 DN0988647 Issue: 04A


2 Configure the RNC object.Create or modify the RNC object by setting the value of the PSOpThroUsageparameter to ON. You can specify the data rate and throughput to be used by usingthe parameters related to the throughput-based optimisation of packet scheduleralgorithm. For more information, see section Parameters related to throughput-basedoptimisation of the packet scheduler algorithm.For more information on RNC object handling, see section Modifying RNCparameters in Radio Network Administration.

Expected outcome

The throughput-based optimisation of the packet scheduler algorithm feature is activatedin the network that is controlled by the RNC.

Parameters related to throughput-based optimisation of the packet scheduleralgorithm

The following RNC object parameters are related to the feature:

• Threshold below the downgrade bit rate (DCHUtilBelowDowngradeThr)• Window size for the lower throughput measurement

(DCHUtilLowerAveWinBitRate)• Lower measurement window size for NRT DCH of 32 kbps

(DCHUtilLowerAveWin32)• Lower measurement window size for NRT DCH of 64 kbps




(DCHUtilLowerAveWin384)• Lower downgrade threshold (DCHUtilLowerDowngradeThrBitRate)• Lower downgrade threshold for the NRT DCH of 32 kbps

(DCHUtilLowerDowngradeThr32)• Lower downgrade threshold for the NRT DCH of 64 kbps




(DCHUtilLowerDowngradeThr384)• Time to trigger for the lower throughput measurement

(DCHUtilLowerTimeToTriggerBitRate)• Lower time to trigger for the NRT DCH of 32 kbps

(DCHUtilLowerTimeToTrigger32)


Issue: 04A DN0988647 41

• Lower time to trigger for the NRT DCH of 64 kbps(DCHUtilLowerTimeToTrigger64)




• Guard time for throughput measurement(DCHUtilMeasGuardTime)

• Window size for the release throughput measurement (DCHUtilRelAveWin)• Time to trigger for the release throughput measurement

(DCHUtilRelTimeToTrigger)• Window size for the upper throughput measurement

(DCHUtilUpperAveWinBitRate)• Upper measurement window size for NRT DCH of 32 kbps

(DCHUtilUpperAveWin32)• Upper measurement window size for NRT DCH of 64 kbps




(DCHUtilUpperAveWin384)• Upper downgrade threshold (DCHUtilUpperDowngradeThrBitRate)• Upper downgrade threshold for the NRT DCH of 32 kbps

(DCHUtilUpperDowngradeThr32)• Upper downgrade threshold for the NRT DCH of 64 kbps




(DCHUtilUpperDowngradeThr384)• Time to trigger for the upper throughput measurement

(DCHUtilUpperTimeToTriggerBitRate)• Upper time to trigger for the NRT DCH of 32 kbps

(DCHUtilUpperTimeToTrigger32)• Upper time to trigger for the NRT DCH of 64 kbps




(DCHUtilUpperTimeToTrigger384)



42 DN0988647 Issue: 04A

• Dynamic usage of UL NRT DCH HSDPA return channel(DynUsageHSDPAReturnChannel)

• Throughput-based optimisation of the PS algorithm usage (PSOpThroUsage)

The following WAC object parameters are related to the feature:

• Downlink traffic volume measurement pending time after trigger(TrafVolPendingTimeDL)

• Uplink traffic volume measurement pending time after trigger(TrafVolPendingTimeUL)

For a list of related parameters, see WCDMA Radio Network Configuration Parameters.

In the RNC, the current RRM features support the dynamic use of lower DCH data ratesfor HSDPA UL DCH return channel. In the case of (BTS, AAL2, spreading factor or air)congestion, the Priority Based Scheduling feature downgrades the existing DCHs fromhigher data rates either to the initial or minimum bit rate of HSDPA UL DCH returnchannel, depending on the cause of congestion. If the downgrade is not possible or notenough, the Priority Based Scheduling feature releases the HSDPA UL DCH returnchannel of the existing DCH. For more information on the Priority Based Scheduling, seePacket Scheduler.

When the DynUsageHSDPAReturnChannel parameter value is set to On, thethroughput-based optimisation of packet scheduler algorithm feature also downgradesthe DCH bit rate down to minimum bit rate of the HSDPA UL DCH return channel, if thehigh bit rate DCH is used inefficiently.


2.4.2.2 Verifying throughput-based optimisation of the packet scheduleralgorithm

Purpose

Follow this procedure to verify the activation of the Throughput-Based Optimisation ofthe Packet Scheduler Algorithm feature.

Before you start

Check that WCEL A is active and set the RNC parameter PSOpThroUsage ‘ON’ for thetested traffic class. Set the parameters according to the following:

• Set the initial and minimum bit rate for both UL and DL PS data to 8/8.• Activate the lower throughput measurement by setting the averaging window (RNC:

DCHUtilLowerAveWinBitRate) to a value ≠ 0.• Activate the upper throughput measurement by setting the averaging window (RNC:

DCHUtilUpperAveWinBitRate) to a value ≠ 0.• Activate the release throughput measurement by setting the averaging window

(RNC: DCHUtilRelAveWin) to a value ≠ 0.• Set the RNC parameter InactivityTimerDownlinkDCH to a value larger than RNC

parameters DCHUtilRelAveWin + DCHUtilRelTimeToTrigger to ensure thatInactivityTimerDownlinkDCH does not trigger first.

When performing the test, use a suitable UDP/FTP application for sending specificamounts of data to UL/DL.


Issue: 04A DN0988647 43

1 Make a test where both UL and DL are requested to release.

a) Start a PS call and UL data transfer, for example FTP.b) Let UL go inactive (‘release’ indication for UL). Send DL data, with a lower

throughput than the one set in DCHUtilRelThrDL.c) Check with E2K that DCH is released after the timers DCHUtilRelAveWin +

DCHUtilRelTimeToTrigger expire.d) Repeat the previous three steps with multi-RAB.

As a result, the NRT DCH is downgraded to 8/8.e) Release the call.

2 Make a test where only DL is requested to release.

a) Start a PS call and UL data transfer, for example FTP.b) Send DL data with a lower throughput than the one set in DCHUtilRelThrDL.c) Check with E2K that DL is not released, if DL throughput goes above the release

threshold before DCHUtilRelTimeToTrigger expires.d) Check with E2K that DL is downgraded to MinAllowedBitRateDL after the timers

DCHUtilRelAveWin + DCHUtilRelTimeToTrigger expire.e) Release the call.

3 Make a test for downgrade measurements.

a) Start a PS call.b) Send DL data with lower throughput than the throughput of lower threshold

configured to MAC-d for the currently allocated bit rate.c) Check with E2K that DL is not downgraded if DL throughput goes above the

lower threshold before DCHUtilLowerTimeToTrigger expires.d) Check that DL is downgraded to the target lower downgrade bit rate

(DCHUtilLowerDowngradeThrBitRate) after the timersDCHUtilLowerAveWinBitRate + DCHUtilLowerTimeToTriggerBitRate expire.

e) Repeat the previous three steps for throughput upper threshold. Verify that theguard time (DCHUtilMeasGuardTime) and pending time (TrafVolPendingTimeDL)are taken into account after downgrades.

f) Release the call.

Expected outcome

1. Downgrades and releases happen as expected.2. Throughput is modified and resources are reconfigured after downgrades.3. There are no unexpected alarms.

2.4.2.3 Deactivating throughput-based optimisation of packet scheduleralgorithm

Purpose

Follow this procedure to deactivate the throughput-based optimisation of packetscheduler algorithm feature.



44 DN0988647 Issue: 04A


2 Configure the RNC object.Modify the RNC object by setting the value of the PSOpThroUsage parameter toOFF.For more information on RNC object handling, see Section Modifying RNCparameters in Radio Network Administration.

Expected outcome

The throughput-based optimisation of packet scheduler algorithm feature is deactivatedin the network controlled by the RNC.

2.5 Features RAN384 and RAN814: Emergency andIntelligent Emergency Call Inter-System Handover,Feature Activation Manual

2.5.1 Activating Emergency and Intelligent Emergency Call Inter-system HandoverPurpose

Follow these instructions to activate the Emergency Call Inter-system Handover(EMISHO) or the Intelligent Emergency Call Inter-system Handover (iEMISHO) feature.

For more information on the features, see Section EMISHO and Intelligent EMISHO inLocation Services.

Before you start


Make sure that the RNC is operational and that the following features are active in thenetwork element:

• RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates• RAN1.5009: WCDMA-GSM Inter-System Handover

For information on activating RAN2.0041, see Section Activating LCS – Cell CoverageBased (RTT) with Geographical Coordinates in Feature RAN2.0041: LCS – CellCoverage Based (RTT) with Geographical Coordinates, Feature Activation Manual.

The parameters can be configured using the Parameter Editor in the OMS ElementManager.


Issue: 04A DN0988647 45

activating_and_verifying_ran04_features.pdf

activating_and_verifying_ran04_features.pdf

1 Open the OMS Element Manager and go to Topology Tree View.

2 Select Edit Parameters in the RNC object.

3 Under General tab check that the LCS Functionality parameter is enabled.

4 Go back to Topology Tree View and click on the arrow next to the RNFC objecticon and select Edit -> Edit Parameters.

5 Under Handover Control tab enable the Emergency Call ISHO Supportparameter or the Intelligent Emergency Call ISHO Support parameter.You can enable the EMISHO feature by selecting Enabled from the drop-down menuof the Emergency Call ISHO Support parameter.You can enable the iEMISHO feature by selecting Enabled from the drop-downmenu of the Intelligent Emergency Call ISHO Support parameter.If one of these parameters is enabled, the other one has to be disabled.

Expected outcome

The EMISHO or iEMISHO feature is successfully activated. RNC reset is not required.

Further information

See also:

• Verifying Emergency Call Inter-system Handover• Verifying Intelligent Emergency Call Inter-system Handover• Deactivating Emergency and Intelligent Emergency Call Inter-system Handover

2.5.2 Verifying Emergency and Intelligent Emergency Call Inter-System Handover

2.5.2.1 Verifying Emergency Call Inter-system Handover

Purpose

Follow these instructions to verify the activation of the EMISHO feature.

For more information on the feature, see EMISHO and Intelligent EMISHO, in LocationServices.

1 Send a RANAP: Location Request message related to an emergency call.If ISHO is not performed, make sure that GSM coverage exists.

Expected outcome

The emergency call is handed over to the GSM network.



46 DN0988647 Issue: 04A

Further information

See also:

• Activating Emergency and Intelligent Emergency Call Inter-system Handover• Deactivating Emergency and Intelligent Emergency Call Inter-system Handover

2.5.2.2 Verifying Intelligent Emergency Call Inter-system Handover

Purpose

Follow these instructions to verify the activation of the iEMISHO feature.

For more information on the feature, see EMISHO and Intelligent EMISHO, in LocationServices.

Before you start

Use an UE that is not A-GPS capable, or disable the A-GPS capability in the RNC.

1 Send a RANAP: Location Request message related to an emergency call.RNC calculates the CI+RTT location estimate for the UE.If ISHO is not performed, ensure that GSM coverage exists. Also verify that thelocation request was not served by the WCDMA RAN.If a RANAP: Location Report message was sent from the RNC, use a tighteraccuracy requirement with the original RANAP: Location Reporting Control messageto make sure that the CI+RTT based location estimate does not fulfil the requestedaccuracy.

Expected outcome

The emergency call is handed over to the GSM network.

Further information

See also:

• Activating Emergency and Intelligent Emergency Call Inter-system Handover• Deactivating Emergency and Intelligent Emergency Call Inter-system Handover

2.5.3 Deactivating Emergency and Intelligent Emergency CallInter-system HandoverPurpose

Follow these instructions to deactivate the EMISHO or iEMISHO feature.

For more information on the features, see EMISHO and Intelligent EMISHO, in LocationServices.

Before you start

Make sure that the RNC is operational.


Issue: 04A DN0988647 47

1 Open the OMS Element Manager and go to Topology Tree View.Expand the topology tree of the RNC.

2 Select Edit Parameters in the RNFC object.

3 Under Handover Control tab disable the Emergency Call ISHO Support orthe Intelligent Emergency Call ISHO Support parameter.You can disable the EMISHO feature by selecting Disabled from the drop-downmenu of the Emergency Call ISHO Support parameter.You can disable the iEMISHO feature by selecting Disabled from the drop-downmenu of the Intelligent Emergency Call ISHO Support parameter.

Expected outcome

The EMISHO or iEMISHO feature is deactivated successfully.

Further information

See also:

• Activating Emergency and Intelligent Emergency Call Inter-system Handover• Verifying Emergency Call Inter-system Handover• Verifying Intelligent Emergency Call Inter-system Handover

2.6 Feature RAN830: AMR Codec Sets (12.2, 7.95, 5.9,4.75) and (5.9, 4.75), Feature Activation Manual

2.6.1 Activating AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9,4.75)Purpose

Follow the procedure below to activate the AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and(5.9, 4.75) feature in the RNC.

For more information on the feature, see Section AMR Codec Sets (12.2, 7.95, 5.9, 4.75)and (5.9, 4.75) in Admission Control.

Before you start

This feature belongs to application software. This feature is controlled with the FIFILEparameter. For information, see Licensing.



48 DN0988647 Issue: 04A

g Check the state of the AMR_CODEC_SET_SUPPORT FIFILE parameter with the followingcommand:

• for IPA-RNC use the MML command:ZWOS:2,1217;

• for mcRNC use the SCLI command:fsclish -c "show app-parameter feature-optionality class 2number 1217"

If the state is DEACTIVATED, activate it with the following command:

• for IPA-RNC use the MML command:ZWOA:2,1217,A;

• for mcRNC use the SCLI command:fsclish -c "set app-parameter feature-optionality class 2number 1217 activation-status activated"


2 Configure the WCEL object.Under the CSAMRModeSET parameter, set the values of chosen AMR codec sets toTrue.The recommended configuration for a cell that permits the set (12.2, 7.95, 5.9, 4.75)is that the sets (5.9, 4.75), and (12.2, 7.95, 5.9, 4.75) are set.The recommended configuration for a cell that permits the set (5.9, 4.75) but not theset (12.2, 7.95, 5.9, 4.75) is that only the set (5.9, 4.75) is set.

3 Configure the RNFC object.Set the AMRCodecSetEnabled RNFC management parameter value to Enabled.

Expected outcome

The AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75) feature is activated.

Further information


The following parameters are related to this feature:

RNAC parameters

• Downlink puncturing limit (DLpuncturingLimit)• Maximum DL bit rate with spreading factor 256 (DLmaxBitRateSF256)• Period for CS AMR RRC TFC control requests (PeriodULRCAMR)

WCEL parameters

• Configured CS AMR mode sets (CSAMRModeSET)

RNFC parameters


Issue: 04A DN0988647 49

• AMR codec mode set enabled (AMRCodecSetEnabled)

For more information, see WCDMA Radio Network Configuration Parameters.

2.6.2 Verifying AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9,4.75)Purpose

Follow the procedure below to verify that the AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and(5.9, 4.75) feature is activated in the RNC.

Before you start

Configure the MSS so that the Active Codec Set (ACS) of the AMR becomes '(12.2,7.95, 5.9, 4.75)' for the resource allocation from the Radio Network Subsystem (RNS)with RAB assignment or Relocation Request.

g If the PeriodULRCAMR parameter value is other than 255, indicating that the support ofthe TFO/TrFO calls is enabled in RNC, MSS should not use multi-mode codec sets inthe AMR call assignments other than (12.2, 7.95, 5.9, 4.75). When the value of theAMRCodecSetEnabled parameter is set to Enabled, RNC is able to establish the callat least with the codec set (12.2, 7.95, 5.9, 4.75) or with the codec set (12.2) regardlessof the value of the CSAMRModeSet management parameter, provided the two codecsets are exactly the ones MSS is allowed to use in the AMR call assignments.

Check that the parameter DLpuncturingLimit has the value of 0.60 and theparameter DLmaxBitRateSF256 has at least the value of 35kbps.

When the RAN830 AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75) feature isdeactivated in the RNC, the recommended configuration in the core network requests asingle (12.2) codec mode.

For information on activating TFO/TrFO in the WCDMA RAN, see Section Activatingtandem/transcoder free operation in Feature RAN134: Support for Tandem/TranscoderFree Operation, Feature Activation Manual.


2 Activate the 1002 Traffic measurement in the RNW and BTS measurementswindow.

3 Make one UE to UE call using the following parameter settings:

CSAMRModeSET

Expected max AMR mode

(5.9, 4.75), (12.2, 7.95, 5.9, 4.75) 12.2

(5.9, 4.75) 5.9



50 DN0988647 Issue: 04A

4 Open the RNW Measurement Presentation application.

5 Check that the following counters have been updated.

• M1002C33 RT DCH ALLO FOR AMR 12.2 KBPS IN DL IN SRNC• M1002C25 RT DCH ALLO FOR AMR 12.2 KBPS IN UL IN SRNC• M1002C28 RT DCH ALLO FOR AMR 5.9 KBPS IN DL IN SRNC• M1002C20 RT DCH ALLO FOR AMR 5.9 KBPS IN UL IN SRNC• M1002C49 RT DCH ALLO DURA FOR AMR 12.2 KBPS IN DL IN SRNC• M1002C41 RT DCH ALLO DURA FOR AMR 12.2 KBPS IN UL IN SRNC• M1002C44 RT DCH ALLO DURA FOR AMR 5.9 KBPS IN DL IN SRNC• M1002C36 RT DCH ALLO DURA FOR AMR 5.9 KBPS IN UL IN SRNC

For instructions on using the RNW Measurement Presentation application, seeSection Using RNW Measurement Presentation in Managing and Viewing RNCMeasurements.

g All UEs do not support setup or reconfiguration if maximum bit rate in codec mode set,which the RNC has selected, is lower than the maximum bit rate in codec mode setrequested by core network. For this reason AMR5.9 call is set up first as AMR12.2 calland immediately it is downgraded to AMR5.9 call. It is seen in both 12.2 and 5.9allocation statistic counters:

• M1002C33 RT DCH ALLO FOR AMR 12.2 KBPS IN DL IN SRNC• M1002C25 RT DCH ALLO FOR AMR 12.2 KBPS IN UL IN SRNC• M1002C28 RT DCH ALLO FOR AMR 5.9 KBPS IN DL IN SRNC• M1002C20 RT DCH ALLO FOR AMR 5.9 KBPS IN UL IN SRNC

g If TFO/TrFO is not in use and only IuUP mode version 1 is included in CN request, theAMR5.9 call can be set up immediately but not as AMR12.2 call first.

2.6.3 Deactivating AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and(5.9, 4.75)Purpose

Follow the procedure below to deactivate the AMR Codec Sets (12.2, 7.95, 5.9, 4.75)and (5.9, 4.75) feature in the RNC.

1 Configure the MSS.Configure the MSS so that with RAB assignment or Relocation Request the ActiveCodec Set (ACS) of the AMR is '(12.2)'.


3 Configure the RNFC object.Modify the RNFC object by setting the value of the AMRCodecSetEnabledparameter to Disabled.


Issue: 04A DN0988647 51

Expected outcome

The AMR Codec Sets (12.2, 7.95, 5.9, 4.75) and (5.9, 4.75) feature is deactivated.

Further information

After deactivating the feature, there is no need to reset the RNC.

2.7 RAN827: AMR Service with HS-DSCH2.7.1 Activating AMR Service with HS-DSCH

Purpose

Follow this procedure to activate the RAN827: AMR Service with HS-DSCH feature.

The RAN827: AMR Service with HS-DSCH feature can be activated with the Usageof AMR service with HS-DSCH (AMRWithHSDSCH) parameter.

Before you start

This feature belongs to application software. Ensure that you have a valid license. Thisfeature is under license key management. For more information on licensing, seeLicensing chapter.

To set the feature state to ON, use the following command:

• for IPA-RNC:ZW7M: FEA=968:ON;

• for mcRNC:set license feature-mgmt code 0000000968 feature-admin-stateon

The basic HSDPA must be configured before this feature can be activated. Forinstructions, see Section Activating Basic HSDPA with QPSK and 5 codes in HSDPAFeatures, Feature Activation Manual.

Make sure that FMC objects in the WCEL for the HSDPA FMC S/I/G AMR multi-serviceare defined.

Steps

1 Open the OMS Element Manager

2 Go to Tree ViewExpand the topology tree of the RNC.

3 Open the RNC objectSelect Edit parameters from the RNC object.



52 DN0988647 Issue: 04A

activating_and_verifying_ras05_features.pdf

4 Change the value of the Usage of AMR service with HS-DSCH (AMRWithHSDPA) RNC parameter.In order to activate the feature, set the value of the parameter to Enabled.For more information on the relevant RNC parameters, see WCDMA Radio NetworkConfiguration Parameters.

Further information

It is not necessary to reset the RNC after activating this feature.

2.7.2 Verifying AMR Service with HS-DSCHPurpose

Follow this procedure to verify that the activation has succeeded and the AMR Servicewith HS-DSCH feature works.

Before you start

Ensure that the BTS and RNC are configured and in the working mode. The BTS or cellin question has to be configured so that the basic HSDPA is activated and the AMRService with HS-DSCH feature is enabled.

Steps

1 If the M1002 Traffic measurement is not active, start it with the RNWMeasurement Management application in OMS Element Manager.For more information on starting measurements, see Sections Management of basicRNW measurements and Starting radio network measurements in RNCMeasurement Management.

2 Wait until the measurement period starts, then make an AMR call.

3 Make a PS NRT call.

4 After the measurement data has been collected, use the RNW MeasurementPresentation application to check if counter M1002C405 AMR + HS-DSCHALLOCATIONS FOR BACKGROUND or counter M1002C485 AMR + HS-DSCHALLOCATIONS FOR INTERACTIVE has been updated.For more information on how to view measurement data, see Managing and viewingRNC measurements.For more information on counters, see RNC Counters – RNW Part and RNCCounters – Transport and HW Part.

Expected outcome


Issue: 04A DN0988647 53

managing_and_viewing_rnc_measurements.pdf



The AMR Service with HS-DSCH feature has been activated successfully if counterM1002C405 or M1002C485 has been updated depending on the type of PS call made(interactive or background).

Unexpected outcome

Counters M1002C405 AMR + HS-DSCH ALLOCATIONS FOR BACKGROUND andM1002C485 AMR + HS-DSCH ALLOCATIONS FOR INTERACTIVE are not updated,indicating that the AMR Service with HS-DSCH feature is not active.

2.7.3 Deactivating AMR Service with HS-DSCHPurpose

Follow this procedure to deactivate the AMR Service with HS-DSCH feature.

Steps




4 Set the value for the Usage of AMR service with HS-DSCH (AMRWithHSDPA) RNC parameter to Disabled.For more information on the relevant RNC parameters, see WCDMA Radio NetworkConfiguration Parameters.

Expected outcome

The AMR Service with HS-DSCH feature is deactivated.

Further information

After deactivating the feature, set the feature state to OFF. For more information, seeSection Removing licences from the network element in Licence-based FeatureManagement.



54 DN0988647 Issue: 04A

2.8 Feature RAN1180: Wireless Priority Service,Feature Activation Manual

2.8.1 Activating Wireless Priority ServicePurpose

Follow the procedure below to configure and activate the Wireless Priority Servicefeature in the Radio Network Controller (RNC).

Before you start

This feature is controlled by a license. For information on managing licenses,seeLicensing.

Note that to activate this feature, the OMS Element Manager should be closed andstarted after the licence has been set to ON state.

1 Start the OMS Element Manager.

2 Perform the following steps for every WCEL in which the Wireless PriorityService feature needs to be activated.

a) Select the ADJG object identified with Object identifier = 0.b) Change the value of the AdjgSIB ADJG parameter to For SIBSIB and CELL

DCH meas (default value).The AdjgSIB parameter is visible as Include in System Information.

c) If the WCDMA Cell (WCEL) does not have an ADJG definition with ADJGId 0parameter, create a new one with ADJGId value 0, and set the value of theAdjgSIB ADJG parameter to For SIBSIB and CELL DCH meas.

3 Select Edit parameters from the RNC object.

4 Set the value of the Usage of the Wireless Priority Service(WireLessPriorityService) RNC parameter to Enabled.If the WireLessPriorityService parameter has the value Disabled, it meansthat the Wireless Priority Service feature is disabled in the RNC, even if there isexisting Wireless Priority Service (WPS) configuration in it.For more information about how to configure the RNC, see Section Modifying RNCparameters in Radio Network Administration.

Expected outcome

The Wireless Priority Service feature is activated in the RNC.

Further information



Issue: 04A DN0988647 55


RNC parameters:

• WireLessPriorityService (Usage of the Wireless Priority Service)• WPSCallRestriction (Restricting overloaded WPS calls)

WCEL parameters:

• PtxOffsetWPS (Offset for transmitted Wireless Priority Service power)• PrxOffsetWPS (Offset for received Wireless Priority Service power)

ADJG parameters:

• ADJGId (Inter-system adjacency identifier)• AdjgSIB (Include in System Information)

You can configure the above parameters with the RNC RNW Object Browser GUI.

For more information on the relevant parameters, see WCDMA Radio NetworkConfiguration Parameters.

2.8.2 Verifying Wireless Priority ServicePurpose

Follow the procedure below to verify that the Wireless Priority Service feature has beenactivated in the RNC.

The verification is done through testing that a WPS call is handed to GSM using inter-system directed retry when the RAB setup phase fails and the normal pre-emption failsas well.

No GSM measurements are done and the directed retry of the WPS call is done as ablind handover.

Before you start

• Pre-emption needs to be enabled• Priority parameters need to be set in the HLR and in the MSC• Priority Classes need to be activated on a used SIM-card• One cell needs to have an ADJG_0 neighbor in the GSM Network

The target cell is the first neighbor cell in the neighbor cell list. The first neighbor cellis the cell whose Object identifier has value 0.



56 DN0988647 Issue: 04A


2 Activate both the M1001 Service Level measurement and the M1010 Inter-System Handover measurement. Wait until the measurement data collectionstarts, for example, wait for the next 15 minutes if 15-minute interval is used.

3 Establish a CS speech call as a WPS call and cause congestion in the UTRANnetwork by modifying the Iub AAL2 user plane size.When this is done in both the RNC and the BTS,

a) the CN sends a RAB ASSIGNMENT REQUEST (setup) with the followingparameters:ARP sub parameters are as follows:

• Queuing Allowed = Queuing Allowed• Pre-emption Capability = Shall not trigger pre-emption• Pre-emption Vulnerability = Not pre-emptable• Priority Level set to a pre-determined WPS range as follows:

– WPS Service User 1: Priority Level = 2– WPS Service User 2: Priority Level = 3– WPS Service User 3: Priority Level = 4– WPS Service User 4: Priority Level = 5– WPS Service User 5: Priority Level = 6

Priority levels between WPS users shall be ignored.

b) If the RAB establishment for the WPS service fails due to DCH resource or Iubresource allocation failure, the normal pre-emption is used. If pre-emption failstoo, the RNC triggers a directed retry of the WPS call to GSM.

c) The handover is performed as a blind handover without any RSSI measurementsor compressed mode usage.

d) The call is succeeded through GSM network.

4 Repeat the above procedure, but now trigger the WPS with using mobile-terminated call setup.

5 Wait until the measurement data is collected, for example, for the next 15minutes if 15-minute interval is used.

6 Open the RNW Measurement Presentation application and check the followingcounters of the M1001 Service Level measurement and the M1010 Inter-SystemHandover measurement:

M1001C599 RAB SETUP ATTEMPT CS VOICE WPS

M1001C601 RAB ACCESS COMPLETE CS VOICE WPS


Issue: 04A DN0988647 57

M1010C185 INTER SYSTEM HO ATTEMPTS CAUSED BY WPSFOR RT

M1010C186 SUCCESSFUL INTER SYSTEM HANDOVERSCAUSED BY WPS FOR RT

7 Check that the M1001C599, M1001C601, M1010C185, and M1010C186 countershave been updated when the WPS Inter-System Handover was performed.For instructions on using the RNW Measurement Presentation application, seeSection Using RNW Measurement Presentation in Managing and Viewing RNCMeasurements.

Expected outcome

1. The RNC terminates the RAB Assignment procedure by sending a RABASSIGNMENT RESPONSE message with cause value 'directed retry' and invokesinter-RAT HHO by sending a RELOCATION REQUIRED message with cause'directed retry'.

2. Directed retry (blind Inter-System Handover (ISHO)) started and performedsuccessfully.

3. The compressed mode with Received Signal Strength Indicator (RSSI)measurements and Base Station Identity Code (BSIC) verification are not used.(RRC: Measurement Control message is not sent to the UE to enable ISHOmeasurements).

4. The counters are updated correctly.

Unexpected outcome

1. RNC terminates the RAB ASSIGNMENT procedure by sending a RABASSIGNMENT RESPONSE message with cause value 'no resources available'.

2. Any other of the expected outcome is not realized.

2.8.3 Deactivating Wireless Priority ServicePurpose

Follow the procedure below to deactivate the Wireless Priority Service feature in theRNC.


2 Select Edit parameters from the RNC object.

3 Set the value of the Usage of the WirelessPriority (ServiceWireLessPriorityService) RNC parameter to Disabled.If the WireLessPriorityService parameter has the value Disabled, it meansthat the Wireless Priority Service feature is disabled in the RNC, even if there isexisting Wireless Priority Service (WPS) configuration in it.



58 DN0988647 Issue: 04A

All ADJG neighboring definitions are now identified as normal ADJG neighbors,instead of Wireless Priority Service neighbors.For more information on how to configure the RNC, see Section Modifying RNCparameters in Radio Network Administration. For more information on the relevantparameters, see WCDMA Radio Network Configuration Parameters.

Expected outcome

The Wireless Priority Service feature is deactivated in the RNC.

Further information

After deactivating the feature, set the feature state to OFF. For more information, seeRemoving licences from the network element in Licence-based Feature Management.

After deactivating the feature, there is no need to reset the RNC.

2.9 HSDPA Mobility2.9.1 Activating HSDPA Mobility

Purpose

Follow this procedure to activate the HSDPA Mobility feature.

HSDPA Mobility refers to the RAN828: Serving Cell Change and RAN829: SoftHandover features. These features can be activated and deactivated with the ServingCell Change and SHO On/Off switch (HSDPAMobility) and SHO of theHSDPA Capable UE (HSDPARRCDiversity) OMS RNC parameters.

Before you start


Use the ZW7M command to activate the license for the feature with the feature code 967.



• for mcRNC:set license feature-mgmt id 0000000967 feature-admin-state on

The basic HSDPA must be configured before this feature can be activated. Forinstructions, see Activating Basic HSDPA with QPSK and 5 codesin HSDPA Features,Feature Activation Manual.


Issue: 04A DN0988647 59



Steps




4 Change the value of the Serving HS-DSCH Cell change and SHO on/offswitch and SHO of the HSDPA Capable UE RNC parameters.In order to activate the feature, set the value of the Serving HS-DSCH Cellchange and SHO on/off switch parameter to Enabled. For the SHO of theHSDPA Capable UE parameter the default value can be used.For more information on the relevant RNC parameters, see WCDMA Radio NetworkConfiguration Parameters.

Further information

It is not necessary to reset the RNC after activating this feature.

2.9.2 Verifying HSDPA MobilityPurpose

Follow this procedure to verify that the activation has succeeded and the HSDPAMobility feature works.

Before you start

Ensure that the BTS and RNC are configured and in the working mode. The BTS or cellin question has to be configured so that the basic HSDPA is activated and the featuresServing Cell Change and HSDPA Soft/softer Handover for Associated DPCH areenabled.

Steps

1 If the M1007 and M1008 RRC measurements are not active, start them with theRNW Measurement Management application in OMS Element Manager.For more information on starting measurements, see Sections Management of basicRNW measurements and Starting radio network measurements in RNCMeasurement Management.



60 DN0988647 Issue: 04A




2 Wait until the measurement period starts and make a PS NRT call in cell A.

3 Start a continuous FTP download over the PS NRT data connection.

4 Make the neighbouring cell B available to the UE.

5 Move the UE to cell B.A serving cell change is made at this stage.

6 After the measurement data has been collected, use the RNW MeasurementPresentation application to check that the following counters have beenupdated:

• M1007C49 TWO CELLS IN THE ACTIVE SET FOR HSDPA MOBILITYand

• M1008C222 HS-DSCH INTRA BTS SERVING CELL CHANGES SUCCESSFULor

• M1008C223 HS-DSCH INTER BTS SERVING CELL CHANGES SUCCESSFUL

The counter value can be 1 or larger depending on the number of cell changes.For more information on how to view measurement data, see Managing and viewingRNC measurements.For more information on counters, see RNC Counters – RNW Part and RNCCounters – Transport and HW Part.

Expected outcome

The HSDPA Mobility feature has been activated successfully if the counters indicatethat the serving cell was changed and the soft handover was made.

Unexpected outcome

The following counters are not updated, indicating that the serving cell was not changedand the soft handover was not made:

• M1007C49 TWO CELLS IN THE ACTIVE SET FOR HSDPA MOBILITYand

• M1008C222 HS-DSCH INTRA BTS SERVING CELL CHANGES SUCCESSFULor

• M1008C223 HS-DSCH INTER BTS SERVING CELL CHANGES SUCCESSFUL

2.9.3 Deactivating HSDPA MobilityPurpose

Follow this procedure to deactivate the HSDPA Mobility features.


Issue: 04A DN0988647 61

Steps




4 Set the value for the HS-DSCH Cell Change and SHO On/Off switch andSHO of the HSDPA Capable UE RNC parameters to Disabled.For more information on the relevant RNC parameters, see WCDMA Radio NetworkConfiguration Parameters.

Expected outcome

The HSDPA Mobility features are deactivated.

Further information

After deactivating the feature, set the feature state to OFF. For more information, seeChapter Removing licences from the network element in Licence-based FeatureManagement.

2.10 RAN839: HSDPA 16 Users per Cell2.10.1 Activating HSDPA 16 Users per Cell

Purpose

Follow this procedure to activate feature RAN839: Activating HSDPA 16 Users per Cell.

This optional feature enables a cell-dedicated packet scheduler in the BTS, which iscapable of serving 16 simultaneous HSDPA users.

Before you start

The following features with RNC licenses need to be activated in order to activate thisfeature:

• RAN763: Basic HSDPA with QPSK and 5 codes

For instructions, see Activating Basic HSDPA with QPSK and 5 codes.


Use the ZW7M command to activate the license for the feature with the feature code 865.



62 DN0988647 Issue: 04A




• for mcRNC:set license feature-mgmt code 0000000865 feature-admin-stateon

Steps

1 Open the Nokia WCDMA BTS Site Manager.

2 Set the commissioning parameter HSDPA.BB.Resource.Allocation to value16 HSDPA Users per Cell.The corresponding value in the commissioning file is Cell.

Expected outcome

The BTS is restarted and the feature is activated. The BTS accepts up to 16 users percell.

Further information

Recommissioning the BTS baseband setting requires a BTS restart for the newconfiguration to activate. RNC restart is not required to activate this feature.

Note that if RNC has a valid license for feature RAN1033: HSDPA 48 Users per Cell orRAN1464: HSDPA 64 Users per Cell, BTS rejects the setups exceeding 16 users perscheduler in this baseband configuration. With RAN1033: HSDPA 48 Users per Cell, theBTS baseband should be configured instead to setting Full Baseband or SharedHSDPA Scheduler for Baseband Efficiency. For more information, see thefollowing activation instructions:

• Activating HSDPA 48 users per cell• Activating Shared HSDPA Scheduler for Baseband Efficiency

For more information on baseband options, see Baseband options in HSDPA in BTS.See also Dimensioning WCDMA RAN.

2.10.2 Verifying HSDPA 16 Users per CellPurpose

Follow this procedure to verify the activation of feature RAN839: Activating HSDPA 16Users per Cell.


Issue: 04A DN0988647 63



Steps

1 If the M1000 Cell Resource measurement is not active, start the RNWMeasurement Management application in the OMS Element Manager.For more information on starting measurements, see, for example, Management ofbasic RNW measurements and Starting radio network measurements in RNCMeasurement Management.

2 Make 16 simultaneous PS NRT calls and download simultaneously some data.

3 After the measurement data has been collected, use the RNW MeasurementPresentation application to check that counter M1000C175 DURATION OFACTIVE HSDPA USERS – 15 OR 16 SIMULTANEOUS USERS has beenupdated.

Expected outcome

The feature has been activated successfully if the counter M1000C175 has beenupdated.

2.10.3 Deactivating HSDPA 16 Users per CellPurpose

Follow this procedure to deactivate feature RAN839: Activating HSDPA 16 Users perCell.

In practice this feature is deactivated only when BTS baseband configuration is changed.

Steps

1 See Baseband options in HSDPA in BTS. Select a new baseband configurationto use.

2 Configure the BTS with the desired baseband configuration according to theinformation in HSDPA in BTS and the corresponding activation instructions.

Expected outcome

The BTS is restarted and the new baseband configuration is activated.

2.11 RAN1164: HSPA Service Indicator2.11.1 Activating HSPA Service Indicator

Purpose

Follow the procedure below to activate the HSPA Service Indicator features.



64 DN0988647 Issue: 04A




HSPA Service Indicator refers to:

• RAS05.1 feature RAN1164: HSDPA Service indicator• RAS06/RN3.0 feature RAN826: Basic HSUPA• RAN763: Basic HSDPA with QPSK and 5 codes in the RNC

HSPA Service Indicator indicates the HSPA capability to the UEs. HSPA-capable cellmeans that the UE may consider this cell/any cell in the same sector as part of the HSPAcoverage area to display HSPA service indication.

Before you start

The following feature with RNC license needs to be activated in order to activate thisfeature:

• RAN826: Basic HSUPA• RAN763: Basic HSDPA with QPSK and 5 codes in the RNC

For instructions, see Activating Basic HSUPA and HSUPA Basic RRM and ActivatingBasic HSDPA with QPSK and 5 codes.

g Note that this feature requires restarting the RNC after the activation procedure.

Steps

1 Start the man-machine interface (MMI).

2 Use the specified MML command to activate the features:ZWOC:2,1300,24; to activate HSDPA Service IndicatorZWOC:2,1632,66; to activate HSUPA Service Indicator

Steps

1 Open the Secure Shell connection (SSH).

2 Use the specified SCLI command to activate features:To activate HSDPA Service Indicator:fsclish -c “set app-parameter configuration-parameter class 2number 1300 value 24”

To activate HSUPA Service Indicator:fsclish -c “set app-parameter configuration-parameter class 2number 1632 value 66”

Expected outcome

HSDPA and HSUPA Service Indicator features have been activated.


Issue: 04A DN0988647 65

2.11.2 Verifying HSPA Service IndicatorPurpose

Follow the procedure below to verify that the activation of the HSPA Service Indicatorfeatures has been successful.

Steps


2 Use the specific MML command to verify the features:ZWOI:2,1300; to verify HSDPA Service IndicatorIf the feature is active, the following message is shown:

LOADING PROGRAM VERSION 7.18-0 EXECUTION STARTEDPARAMETER CLASS: 2 SYSTEM_FUNCT_CONFIGURIDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITY01300 RN22_FEATURE_OPT_004 0024 YESZWOI:2,1632; to verify the HSUPA Service IndicatorIf the feature is active, the following message is shown:

LOADING PROGRAM VERSION 7.18-0 EXECUTION STARTEDPARAMETER CLASS: 2 SYSTEM_FUNCT_CONFIGURIDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITY01632 HSUPA_SERVICE_INDICATOR 0066 YES

3 Use service indicator capable UEs to verify these features.

Steps


2 Use the specific SCLI command to verify the features:To verify HSDPA Service Indicator:fsclish -c “show app-parameter configuration-parameter class 2number 1300”

If the feature is active, the following message is shown:

EXECUTION STARTEDPARAMETER CLASS: 2 SYSTEM_FUNCT_CONFIGURIDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITY1300 RN22_FEATURE_OPT_004 24 YESCOMMAND EXECUTED



66 DN0988647 Issue: 04A

To verify the HSUPA Service Indicator:fsclish -c “show app-parameter configuration-parameter class 2number 1632”

If the feature is active, the following message is shown:

EXECUTION STARTEDPARAMETER CLASS: 2 SYSTEM_FUNCT_CONFIGURIDENTIFIER NAME OF PARAMETER VALUE CHANGE POSSIBILITY1632 HSUPA_SERVICE_INDICATOR 66 YESCOMMAND EXECUTED

3 Use service indicator capable UEs to verify these features.

Expected results

In idle state the indicator is shown on the UE (UE that has service indicator functionality)display when the UE is within the HSPA capable cell.

2.11.3 Deactivating HSPA Service IndicatorPurpose

Follow the procedure below to deactivate the HSPA Service Indicator features.

Steps


2 Use the specific MML command to deactivate the features:ZWOC:2,1300,0; to deactivate HSDPA Service IndicatorZWOC:2,1632,67; to deactivate HSUPA Service Indicator

3 Restart the RNC after the deactivation procedure.

Steps


2 Use the specific SCLI command to deactivate the features:To deactivate HSDPA Service Indicator:fsclish -c “set app-parameter configuration-parameter class 2number 1300 value 0”

To deactivate HSUPA Service Indicator:


Issue: 04A DN0988647 67

fsclish -c “set app-parameter configuration-parameter class 2number 1632 value 67”

3 Restart the RNC after the deactivation procedure.

Expected outcome

HSDPA and HSUPA Service Indicator features have been deactivated.



68 DN0988647 Issue: 04A

3 Operability Feature Activation Instructions

3.1 Feature RAN619: Flexible Connection of VPCs forWBTS Object in RNC, Feature Activation Manual

3.1.1 Activating flexible connection of VPCs for WBTS object inRNCPurpose

Follow the procedure below to configure and activate the Flexible Connection of VPCsfor WBTS Object in RNC feature in the RNC.

Before you start

This feature belongs to application software. Ensure that you have a valid licence. Thisfeature is under licence key management.

Before licensed feature(s) can be activated, the licence (a file including the featureinformation) must be transferred and installed to the RNC. The licence can be installedby using NetAct or a local MML interface. If the installation is done by using NetAct, thefeature(s) covered by the licence are automatically set to the ON state. If the installationis done by using the MML interface, the feature state (ON/OFF/CONFIG) must be set bythe user. In new installations, the default state is OFF. For more information on featurestates, see Section Installing licences in the network element in Licence-based FeatureManagement.

Make sure that the BTS/AXC is also configured to support the same kind of Iubconnection as in the RNC.

Steps


2 Configure a COCO object with several ATM interfaces and Virtual PathIdentifiers (VPIs).Before you startNote that the maximum amount of ATM interface and VPI pairs that can be created inone COCO is eight, and that the interfaces need to be created in the RNC by usingMML commands before creating the COCO.

a) Create the COCO and the connection identifiers; One VP and one interfaceneeds to be given.

b) Define the ATM interfaces to use in the interface list.c) Define the ATM interface and VPI parameters in the VPLTPList planned to be

used for the BTS connections at the RNC end.d) Select the planned ATM interface id / VPI and define the VCI values for the

Common NBAP link.

Activating and Verifying RAS5.1 Features Operability Feature Activation Instructions

Issue: 04A DN0988647 69

e) Select the planned ATM interface id / VPI and define the VCI values for theDedicated NBAP link(s).

f) Select the planned ATM interface id / VPI and define the VCI values for the AAL2signaling link(s).

g) Define the planned ATM interface id / VPI / VCI values for the AAL2 userplanelink(s) and the WAM ID, ATM interface id / VPI / VCI values for the related AAL2signalling link.

For more information, see Section Radio network management in Radio NetworkAdministration.

Expected outcome

• The Flexible Connection of VPCs for WBTS Object in RNC feature is activatedbetween the RNC and the BTS.

• The created COCO object includes several Virtual Paths (VPs)• Several ATM interfaces can be included to one COCO object.

Further information



COCO parameters:

VPLTPList - VPLTP

COCOVPI Virtual Path Identifier

VPLTPATMIfId VPLTP ATM interface identifier

CNBAPTP

CNBAPTPATMIfId C-NBAP ATM interface identifier

CNBAPVPI C-NBAP Virtual Path Identifier

CNBAPVCI C-NBAP Virtual Channel Identifier

DNBAPTPList - DNBAPTP

DNBAPATMIfId D-NBAP ATM interface identifier

DNBAPVPI D-NBAP Virtual Path Identifier

DNBAPVCI D-NBAP Virtual Channel Identifier

AAL2SignLinkTPList - AAL2SignLinkTP

AAL2SignLinkATMIfId AAL2 signalling link ATM interface identifier

AAL2SignLinkVPI AAL2 signalling link Virtual Path Identifier

Operability Feature Activation Instructions Activating and Verifying RAS5.1 Features

70 DN0988647 Issue: 04A

administering_wcdma_rnw.pdf

AAL2SignLinkVCI AAL2 signalling link Virtual Channel Identifier

AAL2TPList - AAL2TP

AAL2SignLinkATMIfId AAL2 sign link reference ATM interface identifier

AAL2SignLinkVPI AAL2 sign link reference Virtual Path Identifier

AAL2SignLinkVCI AAL2 signalling link Virtual Channel Identifier

AAL2UPATMIfId AAL2 user plane ATM interface identifier

AAL2UPVPI AAL2 user plane Virtual Path Identifier

AAL2UPVCI AAL2 user plane Virtual Channel Identifier

For more information on the relevant parameters, see WCDMA Radio NetworkConfiguration Parameters.

3.1.2 Verifying flexible connection of VPCs for WBTS object inRNCPurpose

Follow the procedure below to verify that the Flexible Connection of VPCs for WBTSObject in RNC feature has been activated in the RNC.

Steps

1 Check that one COCO can use several ATM interface and VPI pairs.If one COCO cannot use several ATM interface and VPI pairs, the FlexibleConnection of VPCs for WBTS Object in RNC feature is not activated between theRNC and the BTS.

2 Check that no error codes or alarms were set during the COCO-object creation.

3 Check that the cells under the WBTS that is connected to the COCO are in WOstate.

4 Initiate a call that goes through those cells.

Expected outcome

The call goes through and can be established.


Issue: 04A DN0988647 71

3.1.3 Deactivating flexible connection of VPCs for WBTS objectin RNCPurpose

Follow the procedure below to deactivate the Flexible Connection of VPCs for WBTSObject in RNC feature in the RNC.

Steps


2 Lock all cells under the WBTS that is connected to a COCO with more than oneVPIs or ATM interfaces.

3 Delete the COCOs that include more than one VPIs or ATM interfaces.

4 Remove the corresponding interfaces from the RNC.Make sure that other COCOs or VCCs do not use these interfaces.

Expected outcome

The Flexible Connection of VPCs for WBTS Object in RNC feature is deactivatedbetween the RNC and the BTS.

Further information

After deactivating the feature, set the feature state to OFF. For more information, seeSection Removing licences from the network element in Licence-based FeatureManagement.

After deactivating, there is no need to reset the RNC.

3.2 Features RAN801 and RAN1167: Radio NetworkAccess Regulation and Domain Specific AccessClass Restriction, Feature Activation Manual

3.2.1 Radio Network Access Regulation3.2.1.1 Activating Radio Network Access Regulation

Purpose

Follow this procedure to activate the Radio Network Access Regulation (RNAR).


72 DN0988647 Issue: 04A


Before you start

This feature belongs to application software. Ensure that the RNAR feature option isenabled in the RNC.

For more information on RNAR, see WCDMA RAN System Documentation.

RNC creates 'forced' CMOB for RNAR during startup if the object does not exist. OtherRNAR settings in all cells are overridden by using 'forced' CMOB.

The following parameters are related to the feature:

WCEL parameters

• RNARGroupId

RNC parameters

• RestrictionInterval

CMOB parameters

• CellAccessRestriction

• ACBarredListSystem

• RestrictionGroupType

• RestrictionGroupName

• TrafficRestriction

When the RNAR feature is active in a WCDMA cell, the ACBarredList parameter ispartly overrun by the ACBarredListSystem parameter. Therefore, cell-specific ACrestrictions do not apply when the RNAR feature is active.

The CellAccessRestriction parameter defines the number of simultaneouslybarred access classes.

The RestrictionInterval is the time period during which the access-class barringinformation remains the same. After the restriction period expires, the RNC selects anew set of access classes to be barred. The RNC rotates the access classes which arebarred.

The ACBarredListSystem parameter is only valid when RNAR is active.

For more information on the parameters, see WCDMA RAN Parameter Dictionary.

The parameter value can be changed by using RNW plan (NetAct Radio AccessConfigurator) or RNW Object Browser (RNC Element Manager application).

Steps

1 Open the RNC RNW Object Browser from RNC Element Manager.To use the RNC RNW Object Browser, you need to have the RNC Element Managerrunning on your computer. You can launch the RNC RNW Object Browser applicationfrom the RNC Element Manager.


Issue: 04A DN0988647 73

2 Set the RestrictionInterval RNC object parameter value as required.

3 There are two alternatives to enable the RNAR feature in the RNC:

• Follow the steps below to enable RNAR in the RNC in selected BTSs/cells:

a) Create the CMOB object with the RNAR type.b) Modify the WCEL object parameter RNARGroupId in case of the RNAR

feature. The value of the parameter has to be the same as the CMOB objectidentifier.

c) Set the CMOB object parameter CellAccessRestriction value to therequired restriction level.

• Follow the steps below to enable RNAR in all cells in the RNC:

a) Select CMOB whose 'RestrictionGroupType' is 'Forced RNAR'.b) Set the CMOB object parameter CellAccessRestriction value to the

required restriction level.

4 Activate CMOB by setting the TrafficRestriction CMOB parameter to'enabled'.

5 Lock the cell.

6 Unlock the cell.

Expected outcome

The RNAR feature is activated in the selected WCDMA cells controlled by the RNC.

The ACBarredListSystem parameter (in CMOB object view) indicates the currentlybarred access classes.The amount of barred access classes matches the value of theCellAccessRestriction parameter.

3.2.1.2 Verifying Radio Network Access Regulation

Purpose

Follow this procedure to verify the Radio Network Access Regulation (RNAR).

Steps

1 Ensure that the following alarm is triggered: 2868 LIMITED UE ACCESS TORADIO NETWORKThere is one instance of the alarm active in the RNC when RNAR is activated (DSACactivation causes another instance of the alarm to appear).


74 DN0988647 Issue: 04A

2 Perform test calls to/from the barred user equipment (UE). A UE with barredaccess class cannot initiate or receive any calls.

Expected outcome

The RNAR feature is verified.

3.2.1.3 Deactivating Radio Network Access Regulation

Purpose

Follow this procedure to deactivate the Radio Network Access Regulation.

Steps


2 There are two possibilities to deactivate the feature:

• If RNAR was activated by using 'forced' CMOB, deactivate RNAR by setting theTrafficRestriction CMOB parameter to 'disabled'.

• If 'RNAR was activated by using non-forced' CMOB, then deactivate RNAReither:

– from the single cell by setting the RNARGoupId WCEL object parameter to '0'

or:

– from the group of cells by setting the TrafficRestriction CMOBparameter to 'disabled'

Expected outcome

The RNAR feature is deactivated in the selected WCDMA cells.

Post requisites

To verify that the RNAR feature has been deactivated, do as follows:

1. Ensure that the following alarm is cancelled:2868 LIMITED UE ACCESS TO RADIO NETWORK

2. Check that the cell specific access class barring settings (ACBarredListparameter) are restored. Calls to/from a UE with non-barred access class aresuccessful in the cell.

Further information


Issue: 04A DN0988647 75

As a precaution, to minimise the impact on the network if the RNAR feature is mistakenlyactivated, you can set the CMOB object parameter CellAccessRestriction to thevalue '10%'. This means that only one access class is barred.

3.2.2 Domain Specific Access Class Restriction3.2.2.1 Activating Domain Specific Access Class Restriction

Purpose

Follow this procedure to activate the Domain Specific Access Class Restriction function(DSAC).

Before you start

This feature belongs to application software. Ensure that the RNAR feature option isenabled in the RNC.

For more information on DSAC, see WCDMA RAN System Documentation.

The DSAC can be activated for all cells in the RNC by using the 'forced' CMOB.

The following parameters are related to the feature:

RNC parameters

• RestrictionInterval

CMOB parameters

• CellAccessRestriction

• ACBarredListSystem

• RestrictionGroupType

• RestrictionGroupName

• TrafficRestriction

WCEL parameters

• CSGroupID

• PSGroupID

The CellAccessRestriction parameter defines the number of simultaneouslybarred access classes.

The RestrictionInterval is the time period during which the access-class barringinformation remains the same. After the restriction period expires, the RNC selects anew set of access classes to be barred. The RNC rotates the access classes which arebarred.

The ACBarredListSystem parameter is only valid when the DSAC feature is active.

For more information on the parameters, see WCDMA RAN Parameter Dictionary.

The parameter value can be changed by using RNW plan (NetAct Radio AccessConfigurator) or RNW Object Browser (RNC Element Manager application).


76 DN0988647 Issue: 04A

Steps


2 Set theRestrictionInterval RNC object parameter value as required.

3 There are two alternatives to enable the DSAC feature in the RNC:

• Follow the steps below to enable DSAC in the RNC in selected BTSs/cells:

a) Create a CMOB object with RestrictionGroupType set as 'CS-DSAC' or'PS-DSAC' (depending on which domain calls need to be limited). Set theCMOB object parameter CellAccessRestriction value to the requiredrestriction level.

b) Modify the WCEL parameter CSGroupId or PSGroupId (depending on theCMOB RestrictionGroupType) to 'connect' the cell into the restrictiongroup.

• Follow the steps below to enable DSAC in all cells in the RNC:

a) Select CMOB whose RestrictionGroupType is ‘Forced CS-DSAC’ or‘Forced PS-DSAC’.

b) Set the CMOB object parameter CellAccessRestriction value to therequired restriction level.

4 Activate CMOB by setting the TrafficRestriction CMOB parameter to'enabled'.

Expected outcome

The DSAC feature is activated in selected or all WCDMA cells controlled by the RNC.The following alarm is triggered to indicate that the feature has been activated:

2868 LIMITED UE ACCESS TO RADIO NETWORK

The ACBarredListSystem parameter (in CMOB object view) indicates the amount(percent) of barred access classes. The amount of barred access classes matches thevalue of the CellAccessRestriction parameter.

3.2.2.2 Verifying Domain Specific Access Class Restriction

Purpose

Follow this procedure to verify the Domain Specific Access Class Restriction function(DSAC).


Issue: 04A DN0988647 77

Steps

1 Ensure that the following alarm is triggered: 2868 LIMITED UE ACCESS TORADIO NETWORKThere is one instance of the alarm active in the RNC when DSAC is activated (RNARactivation causes another instance of the alarm to appear).

2 Perform test calls to/from user equipment (UE) that are barred in the selecteddomain (CS or PS). A UE with barred access class cannot initiate or receiveany calls.

Expected outcome

The Domain Specific Access Class Restriction has been verified.

3.2.2.3 Deactivating Domain Specific Access Class Restriction

Purpose

Follow this procedure to deactivate the Domain Specific Access Class Restrictionfunction (DSAC).

Steps


2 Deactivate the DSAC feature.There are three ways to deactivate the DSAC feature:If DSAC was activated in 'non-forced' manner, the individual cells can be removedfrom 'DSAC group' by changing the CSGroupId and/or PSGroupId WCELparameters to 'not defined'.The whole 'DSAC group' can be deactivated by changing the CMOB object'sTrafficRestriction parameter to 'disabled'.If the DSAC was activated in 'forced' manner, DSAC is deactivated by changing the'forced' TrafficRestriction CMOB parameter to 'disabled'.

Expected outcome

The DSAC feature is deactivated in the selected WCDMA cells.

The following alarm is cancelled:

2868 LIMITED UE ACCESS TO RADIO NETWORK

Post requisites

To verify that the DSAC feature has been deactivated, do as follows:


78 DN0988647 Issue: 04A

1. Ensure that the following alarm is cancelled:2868 LIMITED UE ACCESS TO RADIO NETWORK

2. Check that the cell specific access class barring settings (ACBarredListparameter) are restored. Calls to/from a UE with non-barred access class aresuccessful in the cell.

3.3 Activating RAN1453: Iu Link Break ProtectionSummary of changes

Changes between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.

Changes between issues 3-1 and 04Verifying section has been changed.

The document has been updated to be in accordance with RU30 release.

Changes between issues 3-0 and 3-1Editorial corrections. No content changes.

Changes between issues 2-1 and 3-0Added preconditions for activating the Iu link break protection feature.

3.3.1 Activating RAN1453: Iu Link Break ProtectionPurpose

Follow the procedure below to activate the Iu Link Break Protection feature in the RNC.

Before you start

Before activating Iu Link Break Protection, make sure that features Multiple CN andFlexible Iu are not active.

This feature belongs to application software. Ensure that you have a valid license. Thisfeature is under license key management.

Before licensed feature(s) can be activated, the license (a file including the featureinformation) must be transferred to and installed in the RNC. The license can be installedby using NetAct or a local MML interface.

If the installation is done using NetAct, the feature(s) covered by the license areautomatically set to the ON state. If the installation is done using the MML interface, thefeature state (ON/OFF/CONFIG) must be set by the user. In new installations, the defaultstate is OFF. Before activating the feature, set the feature state to ON. For moreinformation on feature states, see Section Installing licenses in the network element inLicense-based Feature Management.

Licenses or features can be handled using the commands of the W7 command group.For more information, see W7 - License and Feature Handling.


Issue: 04A DN0988647 79


2 Select Configuration Management -> Network Topology -> Tree View.

3 Click the "+" symbol to expand the objects.

4 Modify the related parameters.The following parameters define the length of delay taking place before the Iu linkstate change is handled when only one Core Network (CN) service is unavailable:

• IuBarringDelayTimerCS (Iu Barring Delay Timer for CS) in IUCS object• IuBarringDelayTimerPS (Iu Barring Delay Timer for PS) in IUPS object

The following parameters define the number of cells for which the SystemInformation Block (SIB) information is updated at a time when the CN servicerecovers:

• IuBarringRecoveryGroupCS (Iu Barring Recovery Group for CS) in IUCSobject

• IuBarringRecoveryGroupPS (Iu Barring Recovery Group for PS) in IUPSobject

Further informationFor more information on parameters, see WCDMA Radio Network ConfigurationParameters.Note that if any of the features Multi-operator RAN, Multiple CN, or Flexible Iu isactivated, the Iu barring is not longer delayed.

Expected outcome

The Iu Link Break Protection feature is activated.

Note that the change comes into effect during the 10-minute period following theactivation or when the next Iu link state changes.

Further information


3.3.2 Verifying RAN1453: Iu Link Break ProtectionPurpose

Follow the procedure below to verify that the Iu Link Break Protection feature is active.

g Take the IuCS as an example. The IuPS is the same.

1 Monitor the link between the RNC and the BTS.You can monitor the NBAP message using a message monitoring tool (for example:wireshark or nethawk).


80 DN0988647 Issue: 04A

2 Disconnect the IuCS link.

3 Check that the SIB1 was sent on the Iub interface within the timer range set inparameter IuBarringDelayTimerCS.

4 Recover the IuCS link.

5 Check that the SIB was sent on the Iub interface based on the cell groupssetting in parameter IuBarringRecoveryGroupCS.The first SIB is sent to the first cell group as soon as the IuCS link is recovered. Thenext SIB is sent to the second cell group after a specific timer-defined interval and soon for any remaining groups.

6 After all SIBs are sent, the CS core service is recovered for all impacted cells.

3.3.3 Deactivating RAN1453: Iu Link Break ProtectionPurpose

Follow the procedure below to deactivate the Iu Link Break Protection feature in theRNC.


2 Select Configuration Management -> Network Topology -> Tree View.

3 Click the "+" symbol to expand the objects.

4 Set the length of the delays to 0.Define the length of the delays with one of the following parameters:IuBarringDelayTimerCS (Iu Barring Delay Timer for CS) in IUCS objectIuBarringDelayTimerPS (Iu Barring Delay Timer for PS) in IUPS objectFurther informationFor more information on parameters, see WCDMA Radio Network ConfigurationParameters.

Expected outcome

The Iu Link Break Protection feature is deactivated.

Note that the change comes into effect during the 10-minute period following thedeactivation or when the next Iu link state changes.

Further information


Issue: 04A DN0988647 81

After deactivating, there is no need to reset the RNC.


82 DN0988647 Issue: 04A

4 BTS solution Feature Activation Instructions

4.1 Activating RAN905: Flexi WCDMA BTS MHA CWASupport

4.1.1 Activating RAN905: Flexi WCDMA BTS MHA CWA SupportPurpose

To activate the RAN905: Flexi WCDMA BTS MHA CWA Support, follow this procedure.

Before you start

g Confirm that the MHA & RET units have been physically installed and connected on thesite. For details, see Installing Antenna Systems document inAntenna Systems, Operating Documentation.

g Note that this feature is under license control and requires a valid license file. SeeTable 7: Sales item related to the feature RAN905: Flexi WCDMA BTS MHA CWASupport.

Table 7 Sales item related to the feature RAN905: Flexi WCDMA BTS MHA CWASupport

Featurecode

License name

Feature ID

NE Type

Licensing variant

Type

310Nokia MHAsupportCapacity unit: MastHead Amplifiers

RAN905 Flexi BTS License Key, PoolLicensing Capacity

The BTS Site Manager (BTSSM) can be connected to the BTS either locally or remotely.

Steps

1 Start the BTSSM application and establish connection to the BTS.For details, see BTS Site Manager Online Help.

g Make sure that the BTS is switched on.

2 Import the license file.The RAN905: Flexi WCDMA BTS MHA CWA Support is a license feature. See Table7: Sales item related to the feature RAN905: Flexi WCDMA BTS MHA CWA Support.

Activating and Verifying RAS5.1 Features BTS solution Feature Activation Instructions

Issue: 04A DN0988647 83

3 Start commissioning the BTS. Upload the configuration plan file from the BTS.When BTSSM is connected to the BTS, it automatically uploads the currentconfiguration plan file from the BTS.

• Select View ► Commissioning or click Commissioning on the View bar.

4 Configure Antenna Line Management settings.Move to the 'Commissioning - Antenna Line Settings' page. Make sure that DCfeeder voltage is enabled for the antenna line (the DC Voltage checkbox is selected).

g Changes made to these settings are not taken into use before BTS reset or relevantradio modules are manually blocked and unblocked.

5 Configure AISG MHA Settings.To activate the feature RAN905: Flexi WCDMA BTS MHA CWA Support, selectCurrent mode radio button.

6 Define Antenna Line Settings.a) Enable MHA in use.

Use checkbox to enable further options, that needs to be set.

b) Define MHA type.Select MHA type from drop-down list.

g For MHA manufactured by NSN some further settings might be preselected.

c) Select WMH port.

g This option is applicable only for specific MHAs.

d) Define MHA gain.This option might be preselected for some MHA types.

e) Define Feeder voltage.This option might be preselected for some MHA types.

f) Fill in MHA serial number.Find the MHA serial number on the MHA cover and type it into designated textbox.

g LNAs that are part of a single MHA must have identical product code and serial number.Make sure that you set the serial number and product code properly set.

g) Double check MHA Product code.Product code is filled in automatically for all MHA types manufactured by NSN,nevertheless its recommended to check if the value is correct. For non-NSNMHAs product code needs to be typed in manually.

BTS solution Feature Activation Instructions Activating and Verifying RAS5.1 Features

84 DN0988647 Issue: 04A

g LNAs that are part of a single MHA must have identical product code and serial number.Make sure that you set the serial number and product code properly set.

h) Select MHA faults enabled.This option might be preselected for some MHA types.

i) Define Fault threshold.This option might be preselected for some MHA types.Example of the correct WMHC commissioning.Commissioning of the LNA 1.

1. To commission LNA1, highlight the ANT1 from Antenna list and enable MHAin use checkbox.

2. MHA type: WMHC3. WMH port: BTS1 (pass-through)4. MHA gain: preselected value (12.00 dB)5. Feeder voltage: Automatic6. Serial number: Type in the serial number from MHA.7. Product code: preselected value (470057A)8. MHA faults disabled by default.

Commissioning of the LNA 2.

1. To commission LNA2, highlight the ANT2 from Antenna list and enable MHAin use checkbox.

2. MHA type: WMHC3. WMH port: BTS2 (power).4. MHA gain: preselected value (12.00 dB)5. Feeder voltage: Automatic6. Serial number: Type in the serial number from MHA.7. Product code: preselected value (470057A)8. MHA faults disabled by default.

7 Continue commissioning according to standard procedure.For details, see BTS Site Manager Online Help or Commissioning Flexi MultiradioBTS WCDMA document.

8 The new commissioning plan file is automatically activated in the BTS.After sending parameters, a new commissioning file is activated in the BTS. The filewill be taken into use after a BTS reset.

4.1.2 Verifying the RAN905: Flexi WCDMA BTS MHA CWASupportPurpose

To verify that this feature has been activated successfully, follow these steps.

Activating and Verifying RAS5.1 Features BTS solution Feature Activation Instructions

Issue: 04A DN0988647 85

Steps

1 Log in to the BTS Site Manager.

2 Check the status of newly commisioned MHAs.

• Operating mode is 'Current'• Operating status is 'Working'• Commissioning status is 'Yes'• No alarms have been reported

Figure 1 Verifying the RAN905: Flexi WCDMA BTS MHA CWA Support.

4.1.3 Deactivating the RAN905: Flexi WCDMA BTS MHA CWASupportPurpose

To deactivate the RAN905: Flexi WCDMA BTS MHA CWA Support feature, follow thisprocedure.

Before you start

Remove the license using License Management tool.

Steps

1 Recommission the BTS.

g A restart of the BTS is required after the deactivation of this feature.

BTS solution Feature Activation Instructions Activating and Verifying RAS5.1 Features

86 DN0988647 Issue: 04A

activating and verifying ras05 1 features

Documents

trained personnel

business opportunity

business interruption

qualified personnel

nokianetworksthe information

andtheyaremen important

ru50 andru50 ep1

ismade inrelationtothecontent