NED 3g

WCDMA RAN and I-HSPA, Rel. RU30, Operating Documentation, Issue 05

Activating and Verifying RAN04 Features

DN0988623

Issue 01BApproval Date 2011-12-16

Confidential

2 DN0988623Issue 01B


Id:0900d805808e4fceConfidential

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

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

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

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

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

Copyright Nokia Siemens Networks 2011. All rights reserved

f Important Notice on Product SafetyThis 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 this product 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 and Environmental Information part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt knnen Gefahren durch Laser, Elektrizitt, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal, Safety and Environmental Information dieses Dokuments oder dieses Dokumentations-satzes.

DN0988623 3



Table of contentsThis document has 68 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1 Introduction to RAN04 Feature Activation Instructions . . . . . . . . . . . . . . 81.1.1 RAN04 documentation for radio resource management and telecom fea-

tures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1.1.1 Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1.2 RAN04 Transmission and Transport features . . . . . . . . . . . . . . . . . . . . . 91.1.2.1 Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.1.3 RAN04 documentation for operability features . . . . . . . . . . . . . . . . . . . 111.1.4 RAN04 documentation for performance monitoring features. . . . . . . . . 121.1.4.1 Information on Parameters, Counters, and Alarms . . . . . . . . . . . . . . . . 121.1.5 RAN04 documentation for BTS solution features . . . . . . . . . . . . . . . . . 131.1.5.1 Information on parameters, counters, and alarms . . . . . . . . . . . . . . . . . 141.2 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2 Activating RAN2.0023: Service Area Broadcast . . . . . . . . . . . . . . . . . . 162.1 Activating Service Area Broadcast. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2 Verifying Service Area Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3 Deactivating Service Area Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . 222.4 Verifying deactivation of Service Area Broadcast . . . . . . . . . . . . . . . . . 23

3 Feature RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates, Feature Activation Manual . . . . . . . . . . . . . . . . . . . . . . . . 24

3.1 Activating LCS Cell Coverage Based (RTT) with Geographical Coordi-nates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.2 Verifying LCS Cell Coverage Based (RTT) with Geographical Coordi-nates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.3 Deactivating LCS Cell Coverage Based (RTT) with Geographical Coor-dinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4 Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Fea-ture Activation Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.1 Activating Nokia Multi-Operator RAN. . . . . . . . . . . . . . . . . . . . . . . . . . . 304.2 Verifying Nokia Multi-Operator RAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 324.3 Deactivating Nokia Multi-Operator RAN . . . . . . . . . . . . . . . . . . . . . . . . 334.4 Configuring parameters for MO-RAN. . . . . . . . . . . . . . . . . . . . . . . . . . . 354.4.1 Configuring Iu-CS parameters of RNC for MO-RAN . . . . . . . . . . . . . . . 354.4.2 Configuring Iu-PS parameters of RNC for MO-RAN . . . . . . . . . . . . . . . 364.4.3 Configuring Iu-BC parameters of RNC for MO-RAN . . . . . . . . . . . . . . . 37

5 Feature RAN2.0060: IMSI-based Handover, Feature Activation Manual 385.1 Configuring IMSI-based handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.2 IMSI-based intra-frequency handover . . . . . . . . . . . . . . . . . . . . . . . . . . 415.2.1 Activating IMSI-based intra-frequency handover . . . . . . . . . . . . . . . . . . 415.2.2 Verifying IMSI-based intra-frequency handover. . . . . . . . . . . . . . . . . . . 425.2.3 Deactivating IMSI-based intra-frequency handover. . . . . . . . . . . . . . . . 435.3 IMSI-based inter-frequency handover . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4 DN0988623



5.3.1 Activating IMSI-based inter-frequency handover . . . . . . . . . . . . . . . . . . 445.3.2 Verifying IMSI-based inter-frequency handover . . . . . . . . . . . . . . . . . . . 455.3.3 Deactivating IMSI-based inter-frequency handover . . . . . . . . . . . . . . . . 465.4 IMSI-based inter-system handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.4.1 Activating IMSI-based inter-system handover . . . . . . . . . . . . . . . . . . . . 475.4.2 Verifying IMSI-based inter-system handover . . . . . . . . . . . . . . . . . . . . . 485.4.3 Deactivating IMSI-based inter-system handover . . . . . . . . . . . . . . . . . . 495.5 Immediate IMSI-based inter-frequency/inter-system handover . . . . . . . 505.5.1 Activating immediate IMSI-based inter-frequency/inter-system handover .

505.5.2 Verifying immediate IMSI-based inter-frequency/inter-system handover 525.5.3 Deactivating immediate IMSI-based inter-frequency/inter-system han-

dover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6 Features RAN2.0027 and RAN 2.0026: Threshold Based PM Notification Triggering and KPI Calculations in the RNC Element Manager, Feature Ac-tivation Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.1 Activating the threshold-based notification triggering and the KPI calcula-tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

6.2 Verifying the threshold-based notification triggering and the KPI calculation56

6.3 Deactivating the threshold-based notification triggering and the KPI calcu-lation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7 Activating and Operating Subscriber and Equipment Trace . . . . . . . . . . 587.1 Activating subscriber and equipment trace . . . . . . . . . . . . . . . . . . . . . . . 587.1.1 Activating subscriber and equipment trace . . . . . . . . . . . . . . . . . . . . . . . 587.1.2 Verifying subscriber and equipment trace. . . . . . . . . . . . . . . . . . . . . . . . 607.1.3 Deactivating subscriber and equipment trace. . . . . . . . . . . . . . . . . . . . . 617.2 Operating subscriber and equipment trace. . . . . . . . . . . . . . . . . . . . . . . 627.2.1 Operation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627.2.2 Starting tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637.2.2.1 Management-based activation of trace. . . . . . . . . . . . . . . . . . . . . . . . . . 637.2.2.2 Signalling-based activation of trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.2.3 Stopping tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657.2.3.1 Management-based deactivation of trace. . . . . . . . . . . . . . . . . . . . . . . . 657.2.3.2 Signalling-based deactivation of trace . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Related information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

DN0988623 5



List of figuresFigure 1 Example of IPv4 configuration for Iu-BC . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 2 Example of locking the cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6 DN0988623



List of tablesTable 1 Radio resource management and telecom features . . . . . . . . . . . . . . . . 8Table 2 Transmission and transport features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 3 Operability features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 4 Performance monitoring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Table 5 Performance monitoring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 6 WSMLC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Table 7 Mandatory WLCSE parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

DN0988623 7

Activating and Verifying RAN04 Features Summary of changes

Id:0900d805808f169dConfidential

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

The following feature activation instructions have not been tested for RN6.0:

Feature RAN2.0060: IMSI-based Handover, Feature Activation Manual Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Activa-

tion Manual

The following feature activation instructions have not been tested for mcRNC2.0:

Activating and Operating Subscriber and Equipment TraceChanges between issues 01A (2011-06-20, WCDMA RAN RU30) and 01B (2011-12-16, WCDMA RAN RU30)The following feature activation instructions have been updated:

Features RAN2.0027 and RAN 2.0026: Threshold Based PM Notification Triggering and KPI Calculations in the RNC Element Manager, Feature Activation Manual

Activating and Operating Subscriber and Equipment TraceChanges between issues 01 (2011-03-25, WCDMA RAN RU30) and 01A (2011-06-20, WCDMA RAN RU30)The following feature activation instructions have been updated:

Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Activa-tion Manual

Issue 01The following instructions were updated due to the new equpment naming in RU30:

Feature RAN2.0023: Service Area Broadcast, Feature Activation Manual Feature RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordi-

nates, Feature Activation Manual Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Activa-

tion Manual Feature RAN2.0060: IMSI-based Handover, Feature Activation ManualThis is the first issue of the document.

8 DN0988623


Id:0900d805808f0cf6Confidential

Introduction

1 Introduction

1.1 Introduction to RAN04 Feature Activation Instructions

1.1.1 RAN04 documentation for radio resource management and telecom featuresSee the following table for more detailed information on WCDMA RAN functionality and feature activation:

Feature ID: Name Functional area descriptions and other related documents

Feature implementation

RAN474: Multi-RAB: AMR + 3 PS data

This feature has no related docu-ments

This feature does not require activa-tion

RAN475: Multi-RAB: CS data + PS data



RAN920: Selective NRT DCH Data Rate Set

WCDMA RAN RRM Packet Sched-uler


RAN2.0022: Support for Volume Based Charging



RAN2.0023: Service Area Broad-cast


Feature RAN2.0023: Service Area Broadcast, Feature Activation Manual

RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates

WCDMA RAN Location Services

Feature RAN2.0041: LCS - Cell Coverage Based (RTT) with Geo-graphical Coordinates, Feature Acti-vation Manual

RAN2.0042: Nokia Multi-Operator RAN

Shared RAN Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Activation Manual

RAN2.0051: Streaming Packet Switched Quality of Service

WCDMA RAN RRM Admission Control


RAN2.0060: IMSI Based Handover WCDMA RAN RRM Handover Control

Feature RAN2.0060: IMSI-based Handover, Feature Activation Manual

RAN2.0079: Directed RRC Con-nection Setup

WCDMA RAN RRM Handover Control


RAN2.0105: Inter-RNC Intra-Fre-quency Hard Handover

WCDMA RAN RRM Handover Control


RAN2.0107: RRC Connection Re-establishment

WCDMA RAN RRM Packet Sched-uler


Table 1 Radio resource management and telecom features

DN0988623 9

Activating and Verifying RAN04 Features Introduction


1.1.1.1 Reference documentationFor information on the parameters, counters and alarms related to each feature, see the Management 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 AXC Parameters Flexi Transport Module Parameters Flexi WCDMA BTS Parameters UltraSite WCDMA BTS Parameters Reference Information Service in NOLS for RNC parametersFor counter descriptions, see:

RNC counters - RNW part RNC counters transport and HW part WBTS counters AXC counters Reference Information Service in NOLSFor alarm descriptions, see:

Multicontroller RNC Notices (0-999) Multicontroller RNC Disturbances (1000-1999) Multicontroller RNC Failure Printouts (2000-3999) RNC Notices (0-999) IPA-RNC Disturbances (1000-1999) IPA-RNC Failure Printouts (2000-3999) IPA-RNC Diagnosis Reports (3700-3999) Multicontroller RNC and IPA-RNC Base Station Alarms (7000-9000) Troubleshooting Flexi WCDMA Base Station Flexi WCDMA Base Station faults Troubleshooting UltraSite and MetroSite WCDMA Base Station UltraSite and MetroSite WCDMA Base Station faultsFor information on license management, see Nokia Siemens Networks license manage-ment concept and its implementation in WCDMA RAN in License management in WCDMA RAN.

1.1.2 RAN04 Transmission and Transport featuresSee the following table for more detailed information on WCDMA RAN functionality and feature activation:

Feature Other related descriptions Related instructions

RAN2.0036: RNC T1 interface WCDMA RAN System Description This feature does not require activation

Table 2 Transmission and transport features

10 DN0988623



Introduction

1.1.2.1 Reference documentationFor information on the parameters, counters and alarms related to each feature, see the Management data section of the feature descriptions.


WCDMA Radio Network Configuration Parameters IP Configuration Plan Interface Parameters for Multicontroller RNC OMS LDAP parameters AXC Parameters Flexi Transport Module Parameters Flexi Multiradio BTS WCDMA Parameters UltraSite 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 PRFILE Descriptions Radio Network Parameters in I-HSPA I-HSPA Adapter Signaling Plan Parameters Reference Information Service in NOLS for RNC parametersFor counter descriptions, see:

RNC Counters - RNW Part RNC Counters Transport and HW Part WBTS Counters

RAN2.0037: RNC Sonet OC-3c interface WCDMA RAN System Description This feature does not require activation

RAN2.0061: BTS STM-1/VC-12 WCDMA RAN System Description This feature does not require activation

RAN2.0070: AXC Compact (AXC-C) WCDMA RAN ATM Transport This feature does not require activation

RAN2.0085: AAL2 Reconfiguration WCDMA RAN ATM Transport This feature does not require activation

RAN2.0094: Optimised Iub AAL2 reservations for common channels

WCDMA RAN ATM Transport This feature does not require activation

RAN2.0096: OSPF for Iu-PS redundancy WCDMA RAN ATM Transport This feature does not require activation

RAN649: US WCDMA BTS Sonet OC-3c Inter-face


RAN653: US WCDMA BTS T1 Interface WCDMA RAN ATM Transport This feature does not require activation

RAN952: Optimized Iub AAL2 Reservations for SRBs


Feature Other related descriptions Related instructions

Table 2 Transmission and transport features (Cont.)

DN0988623 11



AXC Counters I-HSPA Adapter Measurements and Counters Reference Information Service in NOLSFor alarm descriptions, see:

Multicontroller RNC Notices (0-999) Multicontroller RNC Disturbances (1000-1999) Multicontroller RNC Failure Printouts (2000-3999) Multicontroller RNC Alarms (70000-72000) 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 I-HSPA Adapter Base Station Alarms (7000-

9000) Troubleshooting Flexi WCDMA Base Station Flexi WCDMA Base Station Faults Troubleshooting UltraSite and MetroSite WCDMA Base Station UltraSite and MetroSite WCDMA Base Station Faults I-HSPA Adapter Notices (0-999) I-HSPA Adapter Disturbances (1000-1999) I-HSPA Adapter Failure Printouts (2000-3999) I-HSPA Adapter Alarms (70000-72000) OMS Alarms AXC AlarmsFor information on license management, see Nokia Siemens Networks license manage-ment concept and its implementation in WCDMA RAN in License management in WCDMA RAN.

1.1.3 RAN04 documentation for operability featuresSee the following table for more detailed information on WCDMA RAN functionality and feature activation:

Feature ID: Name Functional Area Description Feature implementation

RAN2.0058: RNW Configuration Event Management

WCDMA RAN and I-HSPA Config-uration Management

This feature does not require acti-vation.

RAN656: WCEL Lock and Unlock from NetAct

WCDMA RAN and I-HSPA Config-uration Management


RAN2.0006: HW Inquiry from NetAct

WCDMA RAN and I-HSPA Network Inventory


RAN2.0073: Automatic Notification to NetAct for Changed AXC HW Configuration

WCDMA RAN and I-HSPA Network Inventory


RAN2.0097: Time Zone Support in Element Managers

WCDMA RAN and I-HSPA Time Management


Table 3 Operability features

12 DN0988623



Introduction

1.1.4 RAN04 documentation for performance monitoring featuresSee the following table for more detailed information on WCDMA RAN functionality and feature activation:

1.1.4.1 Information on Parameters, Counters, and AlarmsFor information on the parameters, counters and alarms related to each feature, see the System impact section of the feature descriptions.


WCDMA radio network configuration parameters RNC OMS LDAP parameters Plan Editor AXC Parameters Plan Editor Flexi Transport Module Parameters Plan Editor Flexi WCDMA BTS Parameters Plan Editor UltraSite WCDMA BTS Parameters Reference Information Service in NOLS for RNC parametersFor counter descriptions, see:


RNC Notices (0-999)

RAN2.0098: Daylight Saving Time Support in the Element Manager

WCDMA RAN and I-HSPA Time Management


Feature ID: Name Functional Area Description Feature implementation

Table 3 Operability features (Cont.)

Feature ID: Name Functional Area Descriptions and other related documents

Feature implementation

RAN2.0002: Subscriber Trace

WCDMA RAN Subscriber and Equipment Trace

This feature does not require activa-tion.

RAN2.0026: KPI Calcula-tions in RNC Element Manager

WCDMA RAN performance management This feature does not require activa-tion.

RAN2.0027: Threshold Based PM Notification Triggering


RAN2.0077: AXC ATM Performance Monitoring


Table 4 Performance monitoring features

DN0988623 13



RNC Disturbances (1000-1999) RNC Failure Printouts (2000-3999) RNC Diagnosis Reports (3700-3999) RNC Base Station Alarms (7000-7900) Troubleshooting Flexi WCDMA Base Station Flexi WCDMA Base Station faults Troubleshooting UltraSite and MetroSite WCDMA Base Station UltraSite and MetroSite WCDMA Base Station faultsFor information on licence management, see Nokia Siemens Networks license manage-ment concept and its implementation in WCDMA RAN in License management in WCDMA RAN.

1.1.5 RAN04 documentation for BTS solution featuresSee the following table for more detailed information on WCDMA RAN functionality and feature activation:

Feature ID: Name Descriptions Instructions

RAN2.0001: Double Capacity WTR (WTRB)

Wideband Transmitter and Receiver (WTRx) Unit Description


RAN2.0043: Double Code Channel Capacity (WSPC)

Wideband Signal Processor (WSPC) Unit Description


RAN2.0062: X 10Mbit/s Ethernet Hub for O&M (IFUG)

AXC Product Description This feature does not require activa-tion.

RAN2.0066: WSMB (Wide-band Summing & Multiplex-ing Version B) Unit

Wideband Summing and Multiplexing (WSMB) Unit Description


RAN2.0071: Efficiency Enhanced WPA (EEWPA)

Wideband Power Amplifier (WPAx) Unit Description


RAN2.0072: WAM Support Wideband Application Manager (WAMA) Unit Description


RAN2.0086: Master WAM Redundancy

Wideband Application Manager (WAMA) Unit Description


RAN639: Support for 3rd Party Mast Head Amplifier

This feature does not have related docu-ments


RAN644: WCDMA Metrosite Door Alarm

MetroSite 50 BTS Optional Unit Descrip-tions

MetroSite 50 BTS Product Description


RAN710: Micro MHA and RealTilt+



RAN771: 1900MHz BTS Configuration



Table 5 Performance monitoring features

14 DN0988623



Introduction

1.1.5.1 Information on parameters, counters, and alarmsFor information on the parameters, counters and alarms related to each feature, see the System impact section of the feature descriptions.


WCDMA radio network configuration parameters RNC OMS LDAP parameters Plan Editor AXC Parameters Plan Editor Flexi Transport Module Parameters Plan Editor Flexi WCDMA BTS Parameters Plan Editor UltraSite WCDMA BTS Parameters Reference Information Service in NOLS for RNC parametersFor counter descriptions, see:


RNC Notices (0-999) RNC Disturbances (1000-1999) RNC Failure Printouts (2000-3999) RNC Diagnosis Reports (3700-3999) RNC Base Station Alarms (7000-7900) Troubleshooting Flexi WCDMA Base Station Flexi WCDMA Base Station faults Troubleshooting UltraSite and MetroSite WCDMA Base Station UltraSite and MetroSite WCDMA Base Station faultsFor information on licence management, see Nokia Siemens Networks license manage-ment concept and its implementation in WCDMA RAN in License management in WCDMA RAN.

RAN899: WPAK This feature does not have related docu-ments


Feature ID: Name Descriptions Instructions

Table 5 Performance monitoring features (Cont.)

DN0988623 15


Id:0900d8058083ab26Confidential

1.2 LicensingThe application software features (ASW) are under license key management. A license is 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. For infor-mation on transferring the license, see License Management Operations in RNC in WCDMA RAN License Operation. For information on installing the license, see Installing licenses 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, see Parameter-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 to ON state. If the MML/SCLI interface is used, the default value is OFF, and you need to set the feature to ON state manually. For information on feature states, see Feature States in WCDMA RAN License Operation. The license-related MML commands are described in W7 - License and Feature Handling.

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

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

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

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

16 DN0988623


Id:0900d8058083b890Confidential

Activating RAN2.0023: Service Area Broadcast

2 Activating RAN2.0023: Service Area Broad-cast

2.1 Activating Service Area BroadcastPurposeFollow this procedure to activate the RAN2.0023: Service Area Broadcast (SAB) feature in the cell. The activation takes place in the RNC. For more information on this feature, see Section Feature RAN2.0023: Service Area Broadcast, Feature Description in RAN04 and RAS05 Telecom Features.

Before you startThis feature belongs to application software and is under license key management. Make sure you have a valid license (a file including the feature information) installed.

Ensure also that the SAB_SUPPORT feature is activated using the command ZWOS:2,1031;Expected output:

01031 SAB_SUPPORT ACTIVATEDIf it is not activated use the command ZWOA:2,1031,A:; to active it.If the SAB_SUPPORT feature is not found then the licence must be installed.

Steps

1 Open the OMS Element Manager and go to Tree View.Follow this path:

Configuration Management j Network Topology j Tree View

2 Configure the RNC object with the CBC and Iu-BC interface parameters.Before you startThe RNC object has to be opened before this procedure can take place.

g You can configure Iu-BC parameters only if Service Area Broadcast Protocol (SABP) is in use.g If several operators share an RNC, the number of cell broadcast centres (CBC) that can be configured for the RNC is 4. In case there is only one operator, there is only one CBC.g If the IMSI-based handover is in use, you can configure up to four PLMN IDs per core item.

a) Expand topology tree and select Edit parameters in the CBCI object to enter the Parameter Editor.

b) Fill in and check CBC-related parameters.Fill in and check CBC-related data, that is, IP addresses and Global PLMN IDs. For a list of parameters, see Section Feature RAN2.0023: Service Area Broadcast, Feature

DN0988623 17

Activating and Verifying RAN04 Features Activating RAN2.0023: Service Area Broadcast


Description in RAN04 and RAS05 Telecom Features. For the appropriate parameter values, see WCDMA Radio Network Configuration Parameters.

For more information, see the following:

Configuring PDH for ATM transport in Physical Interfaces Configuration and Super-vision.

Creating IMA group in Configuring and Supervising Physical Interfaces for RNC. Configuring SDH for ATM transport in Physical Interfaces Configuration and Super-

vision. Creating SDH protection group in Physical Interfaces Configuration and Supervi-

sion. Creating phyTTP for ATM in Physical Interfaces Configuration and Supervision.

3 Configure IP for Iu-BCBefore you startAll user data and signalling (SABP) traffic goes through the same Interface Control and Signalling Unit (ICSU). You must configure one VCC and one static route towards the CBC for the selected ICSU. Static routes are needed only in the case when the CBC is not directly connected to the RNC (for example, router is connected between the RNC and the CBC). In case of ICSU switchover, IP over ATM interface, IP address and static routes will move to the new unit.

The ATM resources for Iu-BC need to be created before this procedure is commenced. For instructions, see Section Creating ATM resources in RNC in ATM Resource Man-agement for RNC.

a) Check the selected ICSU unit towards the CBCThe RNC allocates the ICSU unit for the CBC when the CBC reference data is created to the RNC configuration. You can check the selected ICSU (logical address for the selected ICSU) from the Parameter Editor in OMS Element Manager.For more information on the parameters, see RNC - CBList - CBCItem - ICSU-forCBC in WCDMA RAN Parameter Dictionary.Check the ICSU-id based on the logical address selected towards the CBC with the following command:ZUSI:ICSU;

b) Create the IP over ATM interface to selected ICSUCreate the IP over ATM interface to selected ICSU towards the CBC according to the instructions in Sections Creating and modifying internal IP over ATM interfaces and Creating and modifying external IP over ATM interfaces in Configuring IP Con-nection for RNC.If you want to distribute the incoming traffic between several ICSU units, create as many IP over ATM interfaces as needed (one separate IP over ATM interface for each used ICSU) towards the CBC. In this case, only the selected ICSU unit is sending RNC- riginated Restart and Failure messages towards the CBC. The CBC must be configured to send data to different IP addresses, that is, to different ICSU units. When assigning an IP address to the ICSU unit, assign a logical IP address to the unit by giving value L to the IP address type parameter.If you want to configure several IP over ATM interfaces towards the CBC (distribut-ing incoming traffic between several ICSU units), give the network interface

18 DN0988623




parameter a different value in all units, value L to the IP address type parameter, and assign a different IP address to each unit.The destination IP address is the address of the router interface or the CBC interface which terminates the VCC.

c) Create a static route for Iu-BCFor Iu-BC connections towards the CBC, configure one static route with route type "LOG" for selected ICSU to the IP address of the router terminating IP over ATM PVCs. Static routes are needed only in case the CBC is not directly connected to the RNC.

g Only static routes can be configured for ICSU units. Static routes are only required for ICSUs if any of the IP packets have a different destination address than the IP address of the CBC (for example, if a router is used between the RNC and CBC), and they are to be transferred via the VCC.

For IPv4 use the following command:ZQKC:, :[| def,[]]::[]:[];

g The parameter local IP address is only valid for the local IP address based default routes. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, see Section Creating and modifying static routes in IP Connection Configuration for RNC.

For IPv6 use the following command:ZQ7C:,:,[]::[]:[];

Example: Configuring IP for Iu-BC through ICSU unitsThe following figure shows an example of IP configuration for Iu-BC interface with IPv4 and IPv6 addresses. The ICSU-0 is selected to be used towards the CBC.

DN0988623 19

Activating and Verifying RAN04 Features Activating RAN2.0023: Service Area Broadcast


Figure 1 Example of IPv4 configuration for Iu-BC

The following examples show how to configure the IP for the Iu-BC interface between the RNC and the CBC. The ICSU-0 is selected to be used towards the CBC. The Iu-BC PVCs are configured to the STM-1 interface between the RNC and the MGW. The IPoA PVCs are terminated in a router. The PVCs can also be terminated in the CBC, if it is located in the same site.

For IPv4 case:

a) Create ATM resources as instructed in Creating ATM resources in RNC in Managing ATM Resources in RNC.

b) Create IP over ATM interfaces connected to subnetwork 10.1.1.1/32 to selected ICSU.ZQMF:ICSU,0,L:AA1:1,0,40:1,IPOAUD;

g Note: The ICSU-0 is selected to be used towards the CBC.c) Assign an IPV4 address to the selected ICSU.

ZQRN:ICSU,0:AA1:10.1.1.1,L:32:10.1.1.200;d) Create a static route for selected ICSU.

With the following default routes, all traffic is forwarded to the router terminating IP over ATM PVCs.ZQKC:ICSU,0::10.1.1.200,:LOG;

For IPv6 case: with the same figure, replace the IPv4 address "10.1.1.1" with IPv6 address "3FFE:1200:3012:C020:580:8FFF:FE7A:7BB7" and the IPv4 address "10.1.1.200" with IPv6 address "3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4".

a) Create ATM resources as instructed in Creating ATM resources in RNC in Managing ATM Resources in RNC.

b) Create IPv6 over ATM interfaces connected to subnetwork to selected ICSU.ZQMF:ICSU,0,L:AA1:1,0,40:1,IPOAUD;

ICSU-1

ICSU-2

ICSU-18

...

RNC

NIS

STM-1

MGW

VP

cross

connects

NIS

VPI=x

NIS

VPI=y

Router terminating

IP over ATM PVCs

(can also be an

extra ATM Interface)

any

media

Core siteRNC site

ICSU-0

10.1.1.1

CBC

subnet 10.1.1.0/32

10.1.1.200

20 DN0988623




g The ICSU-0 is selected to be used towards the CBC.c) Assign an IPv6 address to the selected ICSU.

ZQ6N:ICSU,0:AA1:"3FFE:1200:3012:C020:580:8FFF:FE7A:7BB7",L:128:"3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4";

d) Create a static route for each ICSU.With the following default routes, all traffic is forwarded to the router terminating IP over ATM PVCs. A static route is needed for each ICSU because during the ICSU switchover static route is not switching to the new unit.ZQ7C:ICSU,0::"3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4":LOG;ZQ7C:ICSU,1::"3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4":LOG;...ZQ7C:ICSU,18::"3FFE:1200:3012:C020:580:8FFF:FE7A:4BB4":LOG;

4 Create or modify the WCEL objects.a) Select Edit Parameters in created or modified WCEL object.b) Configure and check the SAB-related WCEL parametrisation and enable three Sec-

ondary Common Control Physical Channel (SCCPCH) configurations for the cell. For more information on WCEL handling, see sections Creating a WCDMA cell and Modifying WCDMA cell parameters in Radio Network Administration.

Expected outcomeThe cell is unblocked and CBC receives a SABP:Restart message which means that the Service Area Broadcast is activated in the cell.

Unexpected outcomeIf the activation is unsuccessful, that is, the cell is not created properly or the cell is not unlocked, the operator will be notified by alarms or error codes.

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

The Cell Broadcast Centre (CBC) shall be connected to the RNC via Iu-BC interface. For further information, see section Iu-BC interface in WCDMA RAN Interfaces.

DN0988623 21


Id:0900d80580811550Confidential

2.2 Verifying Service Area BroadcastPurposeFollow the procedure below to verify that the Service Area Broadcast feature is acti-vated.

Steps

1 Send a SABP: Write Replace message from the CBC to the activated cell or service area.

Expected outcomeThe activation of the Service Area Broadcast feature has succeeded if the CBC receives the SABP: Write Replace Complete message and the user equipment receives the message.

22 DN0988623



2.3 Deactivating Service Area BroadcastPurposeFollow the procedure below to deactivate the Service Area Broadcast feature.

Steps

1 Lock the cell objects.

Figure 2 Example of locking the cell

2 Reconfigure the cell objects to two SCCPCH or one SCCPCH configuration.a) Expand topology tree and select Edit Parameters in the WCEL object.b) Set the Number of SCCPCHs (NbrOfSCCPCHs)parameter.

g Reconfigure the cell object to one SCCPCH only if the PCH24kbpsEnabled param-eter for the cell is set as Disabled.c) Repeat for other WCEL objects.For more information, see Modifying WCDMA cell parameters in Radio Network Admin-istration.

3 Unlock the cell objects.Expected outcomeThe cell is reconfigured to two SCCPCH or one SCCPCH, which means that the feature is deactivated. CBC receives the SABP: Failure message for SAI of that cell.

Unexpected outcomeIf the deactivation fails, an error code is returned immediately.

DN0988623 23



2.4 Verifying deactivation of Service Area BroadcastPurposeFollow the procedure below to verify that the Service Area Broadcast feature is deacti-vated.

Steps

1 Send a SABP: Write Replace message from the CBC to the deactivated cell or service area.

Expected outcomeThe deactivation of the Service Area Broadcast feature has succeeded if the CBC receives the SABP: Write Replace Failure message and the UE does not receive the message.

24 DN0988623


Id:0900d8058089c122Confidential

Feature RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates, Feature Activa-

3 Feature RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates, Feature Activation Manual

3.1 Activating LCS Cell Coverage Based (RTT) with Geo-graphical CoordinatesPurposeFollow the procedure below to activate the LCS - Cell Coverage Based (RTT) with Geo-graphical Coordinates feature.

For more information on the feature, see Section Cell Coverage Based (RTT) with Geo-graphical Coordinates in Location Services.

Before you startThis feature belongs to application software. Ensure that you have a valid licence (LCS basic with cell area & RTT).

Make sure that the RNC is operational.

Steps

1 Open the OMS Element Manager.

2 Go to Tree View:Network Management j Topology Tree View

3 Configure the WSMLC parameters.Create or modify the WSMLC object by setting the WSMLC parameters. See the follow-ing table. For more information, see Sections Creating WSMLC object or Modifying WSMLC parameters in Radio Network Administration.

Name Description Range

Confidence Area Level This parameter defines how many per cent of range differ-ence measurements lie within the confidence area that is reported, for example, 67 or 95 per cent.

0..100 per cent

Table 6 WSMLC parameters

DN0988623 25

Activating and Verifying RAN04 Features Feature RAN2.0041: LCS - Cell Coverage Based(RTT) with Geographical Coordinates, Feature Activa-


4 Configure the WLCSE parameters.Create or modify the WLCSE object by setting the WLCSE parameters. See the follow-ing table. The locationing parameters for the cell or adjacent inter-frequency cell of the RNC are set with the WLCSE object. For more information, see Sections Creating WLCSE object or Modifying WLCSE parameters in Radio Network Adminstration.

RNC Low Delay response time

This parameter defines the exact maximum time to process when CN has requested direct reporting with Low Delay response time. If this time is exceeded, RNC sends a response to the CN without location estimate.

Integer (1...255).

RNC Delay Tolerant response time

This parameter defines the exact maximum time to process when CN has requested direct reporting with Delay Tolerant response time. If this time is exceeded, RNC sends response to the CN without location estimate.

Integer (1...255).

Shape List The list contains priorities of shapes to location calculation. The algorithms try to present the responce from algorithms in the shape that has the highest priority (1). If the for-mation fails for any reason, the next shape in the priority order is formed. If the shape has value 'Not Used', it is never formed nor returned to CN.

Not Used, priorities from 1 to 7

Emergency Shape List The list contains priorities of shapes to Emergency call location calculation. The algo-rithms try to present the response from algorithms in the shape that has the highest priority (1). If the formation fails for any reason, the next shape in the priority order is formed. If the shape has value 'Not Used', the shape is never formed nor returned to CN.

Not Used, priorities from 1 to 7

Name Description Range

Table 6 WSMLC parameters (Cont.)

26 DN0988623



Feature RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates, Feature Activa-

Parameter name Description Range

Antenna Bearing This parameter defines antenna direction measured clockwise from North [in degrees].

0..359 (degrees)

Antenna HPBW (Half Power Beam Width) for Cell

This parameter defines half power beam width in degrees (-3dB angle) of the antenna.

1..360 (degrees)

Antenna Coordinates Coordinates of the TX antenna of the cell in WGS-84 format.

Latitude sign and Longitude sign:

0 = positive (North latitude or East longitude)

1 = negative (South latitude or West longitude).

Altitude direction:

0 = height (TX antenna above sea level)

1 = depth (TX antenna below sea level)

Latitude: degrees (0, 90), minutes (0..59), seconds (0..59), fractions (0..99), Latitude sign: (0,1)

Longitude: degrees (0, 180), minutes (0..59), seconds (0..59), fractions (0..99), Longitude sign: (0,1)

Altitude: meters (0...10 000), Altitude direction: (0,1)

Coverage Type This parameter defines type of coverage: outdoor, indoor.

1..2 (outdoor, indoor)

Maximum Cell back radius This parameter defines maximum radius of antenna back radiation beam in meters.

0...200000 meters, step 10 meters 1

Maximum cell radius This parameter defines maximum radius of antenna main radiation beam in meters.

1...200001 meters, step 10 meters 2

Repeater exist These parameters define whether a repeater exists in the cell or not.

Exist/No exist

WLCSE Id This parameter defines WLCSE identification.

1...65535 (integer)

Environment characterisa-tion

The first category corre-sponds to Urban or Bad Urban channels. The second category corre-sponds to Rural or Suburban channels.

Enumerated (possibly heavy multipath and NLOS conditions, no or light multi-path and usually LOS con-ditions, not defined or mixed environment)

WLCSE UTRAN Cell Id Structure

This parameter defines Utran Cell identification.

PLMN-id (MCC+MNC), RNC-id, Cell id

Table 7 Mandatory WLCSE parameters

DN0988623 27

Activating and Verifying RAN04 Features Feature RAN2.0041: LCS - Cell Coverage Based(RTT) with Geographical Coordinates, Feature Activa-


1) The range of Maximum cell back radius has been extended by optional feature Extended Cell (180 km). If that feature is not activated, the range is 0...64000 meters.

2) The range of Maximum cell radius has been extended by optional feature Extended Cell (180 km). If that feature is not activated, the range is 1...64001 meters.

For more information on the Extended Cell (180 km) feature, see WCDMA RAN System, Rel. RAS06, Feature Descriptions.

5 Open the RNC object.Select the RNC object and select Object Open.

6 Select the General tab.

7 Enable the LCS functionality parameter.For the LCSfunctionality parameter, select Enabled from the drop-down menu.Expected outcomeThe LCS Cell Coverage Based (RTT) with Geographical Coordinates feature has been activated. RNC reset is not required.

28 DN0988623


Id:0900d8058081ca7cConfidential

3.2 Verifying LCS Cell Coverage Based (RTT) with Geo-graphical CoordinatesPurposeBy trying to locate a particular UE, you can verify that the LCS Cell Coverage Based (RTT) with Geographical Coordinates feature has been activated.

Steps

1 Send a LOCATION REPORTING CONTROL message to the RNC.Send the location request by UE, iGMLC or MSC.

Expected outcomeThe activation of the feature has succeeded if the serving mobile location centre (SMLC) reports the geographical coordinates of the UE and the accuracy of the estimate. The radio resource control (RRC) signalling entity sends the results to the CN (core network) via RANAP signalling entity.

DN0988623 29


Id:0900d8058089c18eConfidential

3.3 Deactivating LCS Cell Coverage Based (RTT) with Geo-graphical CoordinatesPurposeFollow the procedure below to deactivate the LCS Cell Coverage Based (RTT) with Geographical Coordinates feature.

Before you startMake sure that the RNC is operational.

Steps


2 Go to Tree View:Network Management j Topology Tree View

3 Open the RNC object.Select the RNC object and select Object Open.

4 Select the General tab.

5 Disable the LCS functionality parameter.For the LCSfunctionality parameter, select Disabled from the drop-down menu.Further informationWhen the parameter has been disabled, locationing is no longer possible. It is, however, recommended to proceed with the next step.

Expected outcomeThe LCS Cell Coverage Based (RTT) with Geographical Coordinates feature has been deactivated.

30 DN0988623


Id:0900d80580896cbeConfidential

Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Activation Manual

4 Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Acti-vation Manual

4.1 Activating Nokia Multi-Operator RANPurposeFollow this procedure to activate the Nokia Multi-Operator RAN feature in the RNC.

Before you startThis feature belongs to application software.

This is an optional feature. Make sure there is a valid option (FIFILE parameter) installed with MORAN feature set to active.

For more information, see section Flexible Iu in WCDMA RAN Call Setup and Release.

For instructions on activating the Nokia Multi-Operator RAN feature, see WO - Param-eter Handling.

Steps

1 Check the state of MORAN FIFILE parameter (ACTIVATED or DEACTIVATED) with command ZWOS:2,797:;.

g To proceed with activation the state must be ACTIVATED.



You can also perform the activation in Nokia NetAct.

3 Expand topology tree and select Edit Parameters in IUO object.For more information, see section Radio network management in Radio Network Admin-istration.

4 Fill in the parameters of the IUO object.

5 Create another IUCS and IUPS object in topology tree.

6 Create additional cells.Specify the additional cells which use the additionally created CS and PS cores.

a) Expand the topology tree and WBTS object group.

DN0988623 31

Activating and Verifying RAN04 Features Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Activation Manual

Id:0900d80580896cbeConfidential

b) Click the arrow next to the name of WCEL group object and select Create j new WCEL.

For more information, see section Radio network management in Radio Network Admin-istration.

7 Unlock the cells.Further informationFor more information on configuring the parameters and IP address of PS, see Config-uring Iu-PS parameters of RNC for MO-RAN.

For more information on configuring the CS parameters, see Configuring Iu-CS param-eters of RNC for MO-RAN.

Expected outcomeNokia Multi-Operator RAN has been activated successfully. For more information, see Verifying Nokia Multi-Operator RAN.

Further informationAfter activating, there is no need to reset the RNC.

For more information on the feature, see section Description of MORAN functionality in Nokia Multi-Operator RAN.

32 DN0988623



4.2 Verifying Nokia Multi-Operator RANPurposeFollow this procedure to verify that the Nokia Multi-Operator RAN feature is functioning.

Before you startMake sure that the BTS , the CELL and the RNC are configured and they are in the working mode.

Make sure that the Iu-CS and Iu-PS links have been configured. If they have not been configured, see sections Configuring Iu-CS parameters of RNC for MO-RAN and Con-figuring Iu-PS parameters of RNC for MO-RAN.

Steps

1 Make CS/PS calls using frequencies of both operators to observe if the Nokia Multi-Operator RAN feature works as expected.

2 Make inter-and intra-BTS handovers using frequencies of both operators in one operator network at time to see that the Multi-Operator RAN feature works as expected.

Expected outcomeNokia Multi-Operator RAN has been activated if the calls are successful, and if the han-dovers are successful in the network of the correct operator.

DN0988623 33



4.3 Deactivating Nokia Multi-Operator RANPurposeFollow this procedure to deactivate the Nokia Multi-Operator RAN feature in the RNC.

Before you startMake sure that the Nokia Multi-Operator RAN has been activated.

Steps



g You can also perform the activation in Nokia NetAct.

2 Lock the cells that use other operator's core networks.WCEL uses a specific core network if that core network is assigned to it in parameter Circuit Switched Core Network or Packet Switched Core Network in the WCEL object.

To lock a cell:

1. Expand the WBTS object group in topology tree. 2. Click on:

2.1 the WBTS object, select the WCell(s) tab in main window and the cell to lock, and click the Lock button.

or2.2 the WCEL group object, select the cell to lock in WCell(s) window, and click the

Lock button.

For more information, see section Radio network management in Radio Network Admin-istration.

3 Delete all cells that use other operator's core networks.

4 Delete the related lUCS and lUPS object.

5 Delete the lUO object.

6 Deactivate the feature by using WO - Parameter Handling.For more information, see WO - Parameter Handling.

7 Restart the OMS Element Manager.

34 DN0988623



Expected outcomeNokia Multi-Operator RAN has been deactivated, and no calls with other operator's SIM are possible.

Further informationAfter deactivating, there is no need to reset the RNC.

DN0988623 35



4.4 Configuring parameters for MO-RAN

4.4.1 Configuring Iu-CS parameters of RNC for MO-RAN

Before you startThe RNC object has to be opened before the procedure can take place.Note that if the Nokia Multi-Operator RAN feature is in use and the lU-Operator is con-figured, you have to create and configure one Iu-CS interface per operator.Note that if the IMSI-based handover is in use, you can configure up to four PLMN IDs per core item.

Steps



2 Create the lUCS object.

3 Fill in and check the core network-related parameters.Fill in and check the core network-related data, that is, SS7 signalling parameters and the identification parameter of the core network element. Also fill in all RANAP-related parameters. For more information on parameters, see WCDMA Radio Network Config-uration Parameters.

Note that if there are cells under this core network that are already using the Global PLMNid parameter, its value cannot be changed.

4 Check the value of the digit analysis tree.Note that once you have created digit analyses with an MML, do not change the value of digit analysis tree from the GUI.

Further informationFor information on Iu-CS control plane configuration, see the following instructions:

Configuring ATM-based signalling channels in Integrating RNC. Configuring Signalling Transport over IP over ATM for control plane in Integrating

RNC. Configuring Signalling Transport over IP over Ethernet for control plane in Integrat-

ing RNC.

36 DN0988623



4.4.2 Configuring Iu-PS parameters of RNC for MO-RAN

Iu-PS User Plane configurationFor information on the Iu-PS User Plane configuration, see the following instructions:

Configuring IP for Iu-PS user plane with GTPU in Configuring IP Connection for RNC

Configuring IP for Iu-PS user plane with NPS1(P) in Configuring IP connection for RNC

Configuring IP for user plane with NPGE(P)in Configuring IP Connection for RNCIu-PS Control Plane configurationFor information on the Iu-PS Control Plane configuration, see the following instructions:

Configuring ATM-based signalling channels in Integrating RNC Configuring Signalling Transport over IP over ATM for control plane in Configuring

IP Connection for RNC Configuring Signalling Transport over IP over Ethernet for control plane in Configur-

ing IP Connection for RNC

DN0988623 37



4.4.3 Configuring Iu-BC parameters of RNC for MO-RAN

Before you startNote that the RNC object has to be opened before the procedure can take place.Note that if the Nokia Multi-Operator RAN and SAB_SUPPORT feature is in use, you have to create and configure one Iu-BC interface per operator.Note that if the IMSI-based handover is in use, you can configure up to four PLMN IDs per core item.

Steps



2 Select Edit Parameters in the CBCI object.

3 Fill in and check the CBC-related parameters.Fill in and check the Cell Broadcast Centre (CBC) related data, that is, IP addresses and Global PLMN IDs.

Further informationFor more information on parameters, see WCDMA Radio Network Configuration Param-eters.

38 DN0988623


Id:0900d8058083b88fConfidential


5 Feature RAN2.0060: IMSI-based Handover, Feature Activation Manual

5.1 Configuring IMSI-based handoverPurposeThe procedure below is a prerequisite for activating the different types of IMSI-based handover. For information on the feature, see Section Functionality of IMSI-based handover in Handover Control.

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

Steps


2 Go to Tree View:Configuration Management j Network Topology j Tree View

3 Check and modify the RNC parameters.For more information, see Modifying the RNC parameters.

a) Configure the Iu-CS and the Iu-PS parameters of the RNC.Check and modify the primary PLMN ID and the shared area PLMN ID definitions for the IuItemCS and IuItemPS parameters. Shared area PLMN IDs must be used and defined if there are more than one PLMNs defined in RNC and if intra-RNC and inter-PLMN handovers are needed to be used in the RNC.Add all the used PLMN IDs in the SRNC to the Iu list for the CS and PS domains.For more information, see Configuring Iu-CS parameters of the RNC and Configur-ing Iu-PS parameters of the RNC.

b) Check and configure the neighbour RNC definitions.Add all the PLMN IDs of each neighbour DRNC to the SRNC Iur list.For more information, see Configuring Iur parameters of the RNC.

4 Create or modify the FMC objects.Enable the IMSI-based handover for the cells with the corresponding FMC parameters.

For more information, see Creating frequency measurement control.

5 Create the HOP objects if needed.For more information, see Creating handover path.

DN0988623 39

Activating and Verifying RAN04 Features Feature RAN2.0060: IMSI-based Handover, FeatureActivation Manual


6 Create the WBTS objects if needed.For more information, see Creating a WCDMA BTS site.

7 Create the WCEL objects if needed.The PLMN ID given for the cell must be found in the IuItemCS/PS definitions either from the primary PLMN ID or the shared area PMLN ID definitions.

For more information, see Creating a WCDMA cell.

8 Create the ADJ objects if needed.Create the neighbouring cells for all needed authorised networks.

For more information see Creating an internal adjacency for a WCDMA cell and Creating an external adjacency for a WCDMA cell.

9 Create the WANE objects.Set the correct authorised PLMN ID information in the WANE object. The given PLMNs are considered equal to the home PLMN of the subscriber.

For more information, see Creating WANE object and Modifying WANE parameters.

10 Create the WSG objects.Set the home PLMN of the subscriber and the identifier of the authorised network list into the WSG.

For more information, see Creating WSG object and Modifying WSG parameters.

11 Modify the default authorised network information in the RNC object.Set the identifier of the authorised network list into the default authorised network infor-mation (DefaultAuthorisedNetworkId) in the RNC object.

Note that by default all the PLMNs are authorised.

Expected outcomeThe IMSI-based handover feature has been configured and is ready to be activated.

Further informationThe following RNC object parameters are related to the feature:

Identifier of the Default Authorised Network (DefaultAuthorisedNetworkId) Shared area Mobile Country Code (SharedAreaMCC) Shared area Mobile Network Code (SharedAreaMNC) Shared area Mobile Network Code Length (SharedAreaMNClength)The following WANE object parameters are related to the feature:

Authorised Network Identifier (AuthorisedNetworkId) Authorised Network Mobile Country Code (AuthorisedNetworkMCC) Authorised Network Mobile Network Code (AuthorisedNetworkMNC)

40 DN0988623




Authorised Network Mobile Network Code Length (AuthorisedNetworkMNClength)

Technology used in the Authorised Network (Technology) WANE Name (WANEName)The following WSG object parameters are related to the feature:

GSM Roaming allowed (GSMRoaming) Home PLMN Mobile Country Code (HomePlmnMCC) Home PLMN Mobile Network Code (HomePlmnMNC) Home PLMN Mobile Network Code Length (HomePlmnMNCLength) Name of the subscriber home PLMN (OperatorName) Subscriber Group Identifier (SubscriberGroupId) Identifier of the Authorised Network (WSGAuthorisedNetworkId)The following FMCS object parameters are related to the feature:

IMSI-based SHO (IMSIbasedSHO)The following FMCI object parameters are related to the feature:

IMSI-based IFHO (IMSIbasedIFHO)The following FMCG object parameters are related to the feature:

IMSI-based GSM HO (IMSIbasedGsmHo)For more information, see WCDMA RAN Parameter Dictionary.

DN0988623 41


Id:0900d8058081cb22Confidential

5.2 IMSI-based intra-frequency handover

5.2.1 Activating IMSI-based intra-frequency handover

PurposeFollow this procedure to activate the IMSI-based intra-frequency handover in the RNC.

Before you startMake sure you have configured the IMSI-based handover correctly. For more informa-tion, see Configuring IMSI-based handover.

Steps



3 Modify the FMCS.In the FMCS set, set the IMSIBasedSHO parameter to 'Allowed' in order to enable the IMSI-based intra-frequency handover in the related WCELs.

Expected outcomeThe IMSI-based intra-frequency handover has been activated.


42 DN0988623



5.2.2 Verifying IMSI-based intra-frequency handover

PurposeWhen the IMSI-based intra-frequency handover feature is activated, the user can verify that the activation succeeded and that the IMSI-based handover works.

Before you startAll conditions mentioned in Activating IMSI-based intra-frequency handover must be ful-filled.

Steps

1 Make a call in a cell that has two intra-frequency neighbouring cells, cell A and cell B.The PLMN of the neighbouring cell A is included in the WANE set, and either has the same PLMN as the subscriber or as the cell to which the call was established. The PLMN of cell B is not the same as the PLMN of the subscriber or as the PLMN in the cell to which the call was made. It is also not the same as any PLMN in the WANE set used by the subscriber.

2 Make both cells available to the UE.The UE then sends an intra-frequency measurement report on event 1a to both cells. Handover is only allowed to the first cell, neighbour cell A. Handover is not allowed to the neighbour cell B.

Expected outcomeThe activation of IMSI-based intra-frequency handover has succeeded if a handover to cell A is allowed and a handover to cell B is not allowed.

DN0988623 43



5.2.3 Deactivating IMSI-based intra-frequency handover

PurposeFollow this procedure to deactivate the intra-frequency IMSI-based handover in the RNC.

Steps



3 Modify the FMCS.In the FMCS set, set the IMSIBasedSHO parameter to Not allowed in order to disable the IMSI-based intra-frequency handover in the related WCELs.

Expected outcomeThe IMSI-based intra-frequency handover has been deactivated.


44 DN0988623



5.3 IMSI-based inter-frequency handover

5.3.1 Activating IMSI-based inter-frequency handover

PurposeFollow this procedure to activate the IMSI-based inter-frequency handover in the RNC.


Steps



3 Modify the FMCI. Set the value of the IMSIBasedIFHO parameter from the FMCI to value 'immidiate

HO allowed' to activate the IMSI-based inter-frequency handover in the related WCELs.

Enable the wanted inter-frequency handover causes in the FMCI set, for example UE TX Power, CPICH EcNo, CPICH RSCP, DL DPCH Tx Power or Uplink DCH Quality.Note that when the IMSI-based inter-frequency handover is enabled in an active set cell, the RNC selects only those neighbouring cells into the inter-frequency neigh-bour cell list whose PLMN identifier is either included in the relevant WANE list or which have the same PLMN identifier as the subscriber.

Expected outcomeThe IMSI-based handover inter-frequency has been activated.


DN0988623 45



5.3.2 Verifying IMSI-based inter-frequency handover

PurposeWhen the IMSI-based inter-frequency handover feature is activated, the user can verify that the activation succeeded and that the IMSI-based handover works.

Before you startAll conditions mentioned in Activating IMSI-based inter-frequency handover must be ful-filled.

Steps

1 Make a call in a cell that has two inter-frequency neighbouring cells, cell A and cell B.The PLMN of neighbouring cell A is either included in the WANE set or has the same PLMN as the subscriber. The PLMN of cell B is not the same as the PLMN of the sub-scriber or as any PLMN in the WANE set used by the subscriber.

2 Make both cells available to the UE.An inter-frequency handover is triggered, for example due to UE TX power. Only the first cell, neighbour cell A, is included in the neighbour cell list sent to the UE for inter-fre-quency measurement. Cell B is not included in the neighbour cell list in question.

Expected outcomeThe activation of IMSI based inter-frequency handover has succeeded if a handover to cell A is performed, while a handover to cell B is not possible.

46 DN0988623



5.3.3 Deactivating IMSI-based inter-frequency handover

PurposeFollow this procedure to deactivate the inter-frequency IMSI-based handover in the RNC.

Steps



3 Modify the FMCI.In the used FMCI sets, set the value of the parameter IMSIbasedIFHO to 'immidiate HO not allowed'.

Expected outcomeThe IMSI-based inter-frequency handover has been deactivated.


DN0988623 47


Id:0900d8058081cb2aConfidential

5.4 IMSI-based inter-system handover

5.4.1 Activating IMSI-based inter-system handover

PurposeFollow this procedure to activate the IMSI-based inter-system handover in the RNC.


Steps



3 Modify the FMCG object. Set the value of the IMSIBasedGsmHo parameter from the FMCG to value 'immidi-

ate HO allowed' to activate the IMSI-based inter-system handover in the related WCELs.

Enable the wanted inter-system handover causes in the FMCI set, for example UE TX Power, CPICH RSCP, CPICH ECNO, DL DPCH TX power or Uplink DCH Quality.

Note that when the IMSI-based inter-frequency handover is enabled in an active set cell, the RNC selects only those GSM neighbour cells into the inter-system neighbour cell list whose PLMN identifier is either included in the relevant WANE list or which have the same PLMN identifier as the subscriber.

Expected outcomeThe IMSI-based inter-system handover has been activated.


48 DN0988623



5.4.2 Verifying IMSI-based inter-system handover

PurposeWhen the IMSI-based inter-system handover feature is activated, the user can verify that the activation succeeded and that the IMSI-based handover works.

Before you startAll conditions mentioned in Activating IMSI-based inter-system handover must be ful-filled.

Steps

1 Make a call in a cell that has two inter-system (GSM) neighbour cells, cell A and cell B.The PLMN of neighbouring cell A is either included in the WANE set or has the same PLMN as the subscriber. The PLMN of cell B is not the same as the PLMN of the sub-scriber or as any PLMN in the WANE set used by the subscriber.

2 Make both cells available to the UE.An inter-system handover to GSM is triggered, for example due to UE TX power. Only the first cell, neighbour cell A, is included in the neighbour cell list sent to the UE for inter-system (GSM) measurement. Cell B is not included in the neighbour cell list in question.

Expected outcomeThe activation of IMSI based inter-system handover has succeeded if a handover to cell A is performed, while a handover to cell B is not possible.

DN0988623 49



5.4.3 Deactivating IMSI-based inter-system handover

PurposeFollow this procedure to deactivate the IMSI-based inter-system handover in the RNC.

Steps



3 Modify the FMCG.In the used FMCG sets, set the value of the parameter IMSIbasedGsmHo to immidiate HO not allowed'.

Expected outcomeThe IMSI-based inter-system handover has been deactivated.


50 DN0988623


Id:0900d8058081cb2fConfidential

5.5 Immediate IMSI-based inter-frequency/inter-system handover

5.5.1 Activating immediate IMSI-based inter-frequency/inter-system handover

PurposeFollow this procedure to activate the immediate IMSI-based inter-frequency/inter-system handover in the RNC.


Steps



3 Modify the FMCI or FMCG.Before you startSet the value of the IMSI-based handover parameterIMSIbasedSHO in FMCS set to value 'Allowed'.

Set the value of the IMSI-based handover parameter IMSIBasedIFHO in FMCI set to 'immidiate HO allowed'.

Set the value of the IMSI-based handover parameter IMSIBasedGsmHo in FMCG set to value 'immidiate HO allowed'.

Note that a monitored intra-frequency neighbouring cell, which has a PLMN that is not allowed to the subscriber, should trigger an intra-frequency measurement report with event 1a or 1c in order to get inter-system or inter-frequency measurements started due to immediate IMSI-based handover.

When such intra-frequency measurement report is received, the RNC cannot allow a handover to the cell triggered by the measurement report because its PLMN is not allowed and hence inter-system/inter-frequency measurements are started.

Expected outcomeThe immediate IMSI-based inter-frequency/inter-system handover has been activated.

Further informationImmediate IMSI-based handover is an internally triggered cause and it does not require any additional measurements. The following four conditions must be met in order to trigger the immediate IMSI-based handover cause.

1. Immediate IMSI-based handover is enabled by setting the IMSIbasedIFHO and/or IMSIbasedGsmHo parameter to 'immidiate HO allowed'.

DN0988623 51


Id:0900d8058081cb2fConfidential

2. The active set cell in question has one or more inter-frequency/inter-system neigh-bour cells whose PLMN ID equals either the home PLMN ID of the subscriber or a PLMN ID in the WANE list.

3. IMSI-based intra-frequency handover is enabled with the intra-frequency measure-ment control parameter IMSIbasedSHO of an active set cell controlled by the serving RNC.

4. The PLMN ID of a monitored cell (that has triggered the reporting event 1A or 1C) does not fulfil the requirement of the home/authorised/active set PLMNs and the RNC cannot add the monitored cell into the active set.

When the RNC receives any branch addition or replacement event reported by the UE for a monitored cell which is unauthorised (conditions three and four above are fulfilled), the first two conditions are also checked. If all the above conditions are met, the imme-diate IMSI-based inter-frequency handover cause is triggered.

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

52 DN0988623


Id:0900d8058081cb2dConfidential

5.5.2 Verifying immediate IMSI-based inter-frequency/inter-system handover

PurposeWhen the immediate IMSI-based inter-frequency/inter-system handover feature is acti-vated, the user can verify that the activation succeeded and that the IMSI-based handover works.

Before you startAll conditions mentioned in Activating immediate IMSI-based inter-frequency/inter-system handover must be fulfilled.

Steps

1 Make a call in a cell that has two inter-frequency/inter-system neighbour cells, cells A and B, and one intra-frequency neighbour cell, cell C.The PLMN of neighbour cell A is either included in the WANE set or has the same PLMN as the subscriber. The PLMNs of cells B and C are not the same as the PLMN of the subscriber or as the PLMN of the cell in which the call was made. Neither are they the same as any PLMN in the WANE set used by the subscriber.

2 Make all three cells available to the UE.The UE sends an intra-frequency measurement report on event 1a to cell C. The intra-frequency handover to neighbour cell C is not allowed. Thus an immediate IMSI-based inter-frequency/inter-system handover is triggered. Only the first cell, neighbour cell A, is included in the neighbour cell list sent to the UE for inter-frequency/inter-system mea-surement. Cell B is not included in the neighbour cell list in question.

Expected outcomeThe activation of immediate IMSI-based inter-frequency/inter-system handover has suc-ceeded if a handover to cell A is performed because intra-frequency handover to cell C is not allowed. An inter-frequency/inter-system handover to cell B is not possible.

DN0988623 53


Id:0900d8058081cb2eConfidential

5.5.3 Deactivating immediate IMSI-based inter-frequency/inter-system handover

PurposeFollow this procedure to deactivate the immediate IMSI-based inter-frequency/inter-system handover in the RNC.

Steps



3 Modify the FMCI/FMCG.In the used FMCI/FMCG sets, set the value of the parameters IMSIbasedIFHO/IMSIbasedGsmHo to 'immidiate HO not allowed'.Expected outcomeThe immediate IMSI-based inter-frequency/inter-system handover has been deacti-vated.


54 DN0988623


Id:0900d805808e39a2Confidential

Features RAN2.0027 and RAN 2.0026: Threshold Based PM Notification Triggering and KPI Calculations

6 Features RAN2.0027 and RAN 2.0026: Threshold Based PM Notification Triggering and KPI Calculations in the RNC Element Manager, Feature Activation Manual

6.1 Activating the threshold-based notification triggering and the KPI calculationPurposeFollow this procedure to activate the RAN2.0027: Threshold Based PM Notification Trig-gering and the RAN2.0026: KPI Calculations in RNC Element Manager features in the OMS.

Before you startThese features belong to application software and are under license key management. Ensure that you have a valid license (both features are controlled by the same license).

If the license is disabled, the icon for the NE Threshold Management GUI is visible in the Application Launcher, but when you try to start it, a message that the feature is not licensed is displayed and it is not possible to perform any operation with the GUI.

Steps

1 Transfer the license to the /tmp folder.

2 Log in to the OMS as a root user.

3 Set the full permission for all users to the license xml file. Use the following command: chmod 777 /tmp/

4 Import the license file.Use the following command:

# lmcli importLicence /tmp/

g To check all the imported licenses, use the following command:# lmcli listAllLicences

5 Activate the license.Use the following command: # lmcli activateFeature 973

6 Check if the activation was successful.Use the following command: # lmcli getFeatureStatus 973

DN0988623 55

Activating and Verifying RAN04 Features Features RAN2.0027 and RAN 2.0026: ThresholdBased PM Notification Triggering and KPI Calculations


Expected outcomeThe features are in active state.

Further informationRestart of the OMS is not required after the activation of this feature.

For more information on the threshold-based notifications, see section Threshold mon-itoring in WCDMA RAN Performance Management. For more information on the key performance indicators, see section Key performance indicators in WCDMA RAN Per-formance Management. For more information on the features, see section Administer-ing the Element Manager in Using Element Manager in OMS.

56 DN0988623



6.2 Verifying the threshold-based notification triggering and the KPI calculationPurposeFollow this procedure to verify that the RAN2.0027: Threshold Based PM Notification Triggering and the RAN2.0026: KPI Calculations in RNC Element Manager features are active.

Steps

1 Ensure that the user has Read or Modify access rights to the performance man-agement domain.

2 Open the Application Launcher session in OMS.

3 Start the NE Threshold Management application.Expected outcomeThe application starts without displaying any notification about the licensing. It is possible to use the application for managing thresholds.

DN0988623 57



6.3 Deactivating the threshold-based notification triggering and the KPI calculationPurposeFollow this procedure to deactivate the RAN2.0027: Threshold Based PM Notification Triggering and the RAN2.0026: KPI Calculations in RNC Element Manager features in the OMS.

Steps

1 Log in to the OMS as a root user.

2 Deactivate the license.Use the following command: # lmcli deactivateFeature 973

3 Check if the deactivation was successful.Use the following command: # lmcli getFeatureStatus 973

Expected outcomeThe features are in inactive state.

4 Delete the license (optional).Use the following command:

# lmcli deleteLicence /tmp/Further informationRestart of the OMS is not required after the deactivation of this feature.

58 DN0988623



Activating and Operating Subscriber and Equipment Trace

7 Activating and Operating Subscriber and Equipment Trace

7.1 Activating subscriber and equipment trace

7.1.1 Activating subscriber and equipment trace

g Please note that the RNC product naming practice is changing. For more information, see Guide to WCDMA RAN and I-HSPA Operating Documentation.PurposeFollow the procedure below to activate the subscriber and equipment trace feature in the IPA-RNC.

g There is no license control for this feature in the mcRNC and the I-HSPA Adapter. To activate this feature in the mcRNC and the I-HSPA Adapter, see Steps inVerifying sub-scriber and equipment trace.

For more information, see WCDMA RAN Subscriber and Equipment Trace.

Before you startThis feature belongs to application software. Make sure you have a valid license installed in the IPA-RNC.

Before a licensed feature can be activated, the license (a file including the feature infor-mation) must be transferred and installed in the IPA-RNC.

You can install the license by using NetAct or a local MML interface. If you install the license using NetAct, the feature covered by the license is automatically set to the ON state. If you use the MML interface, you must also set the feature state (ON/CONF/OFF). In new installations, the default state is OFF. When installing a new increment, the previously set state remains as the default.

For more information, see License-based Feature Management, W7 - License and Feature Handling and License Management Principles. See also System Administration Principles in the NetAct operating documentation.

Use the ZW7 command to activate the license for the feature with the feature code 975.The following WCDMA RAN parameter is related to the feature:

RNC -> UEQualityRepIntervalThe parameters can be configured both with the Parameter Editor in the OMS Element Manager GUI and via the plan operations from NetAct. For more information on the related parameters, see WCDMA Radio Network Configuration Parameters.

Check also that NetAct support for the subscriber and equipment trace feature is installed and licensed, because NetAct TraceViewer is the only tool for viewing sub-scriber trace data. For more information on subscriber trace support in NetAct, see the NetAct operating documentation.

DN0988623 59

Activating and Verifying RAN04 Features Activating and Operating Subscriber and EquipmentTrace


Steps

1 Install a valid licence.Expected outcomeThe subscriber and equipment trace feature is activated.

60 DN0988623


Id:0900d805808ee3f4Confidential

7.1.2 Verifying subscriber and equipment trace

g Please note that the RNC product naming practice is changing. For more information, see Guide to WCDMA RAN and I-HSPA Operating Documentation.PurposeFollow this procedure to verify that the activation of the subscriber and equipment trace feature is successful.

Steps

1 Open an MML connection to the IPA-RNCOrfor the mcRNC and the I-HSPA Adapter, open the SSH connection to the

NED 3g

Documents

Transcript of NED 3g