Вы находитесь на странице: 1из 68

WCDMA RAN and I-HSPA, Rel.

RU30, Operating
Documentation, Issue 05

Activating and Verifying RAN04 Features


DN0988623
Issue 01B
Approval Date 2011-12-16

Confidential

Activating and Verifying RAN04 Features

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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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

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
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:

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 Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter Sicherheitshinweise im Teil Legal,
Safety and Environmental Information dieses Dokuments oder dieses Dokumentationssatzes.

Id:0900d805808e4fce
Confidential

DN0988623
Issue 01B

Activating and Verifying RAN04 Features

Table of contents
This document has 68 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1
1.1
1.1.1
1.1.1.1
1.1.2
1.1.2.1
1.1.3
1.1.4
1.1.4.1
1.1.5
1.1.5.1
1.2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Introduction to RAN04 Feature Activation Instructions . . . . . . . . . . . . . . 8
RAN04 documentation for radio resource management and telecom features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
RAN04 Transmission and Transport features . . . . . . . . . . . . . . . . . . . . . 9
Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
RAN04 documentation for operability features . . . . . . . . . . . . . . . . . . . 11
RAN04 documentation for performance monitoring features. . . . . . . . . 12
Information on Parameters, Counters, and Alarms . . . . . . . . . . . . . . . . 12
RAN04 documentation for BTS solution features . . . . . . . . . . . . . . . . . 13
Information on parameters, counters, and alarms . . . . . . . . . . . . . . . . . 14
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2
2.1
2.2
2.3
2.4

Activating RAN2.0023: Service Area Broadcast . . . .


Activating Service Area Broadcast. . . . . . . . . . . . . . .
Verifying Service Area Broadcast . . . . . . . . . . . . . . .
Deactivating Service Area Broadcast . . . . . . . . . . . .
Verifying deactivation of Service Area Broadcast . . .

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


Coordinates, Feature Activation Manual . . . . . . . . . . . . . . . . . . . . . . . . 24
Activating LCS Cell Coverage Based (RTT) with Geographical Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Verifying LCS Cell Coverage Based (RTT) with Geographical Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Deactivating LCS Cell Coverage Based (RTT) with Geographical Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.1
3.2
3.3
4

DN0988623

......
......
......
......
......

........
........
........
........
........

16
16
21
22
23

4.1
4.2
4.3
4.4
4.4.1
4.4.2
4.4.3

Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Activation Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Activating Nokia Multi-Operator RAN. . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Verifying Nokia Multi-Operator RAN . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Deactivating Nokia Multi-Operator RAN . . . . . . . . . . . . . . . . . . . . . . . . 33
Configuring parameters for MO-RAN. . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring Iu-CS parameters of RNC for MO-RAN . . . . . . . . . . . . . . . 35
Configuring Iu-PS parameters of RNC for MO-RAN . . . . . . . . . . . . . . . 36
Configuring Iu-BC parameters of RNC for MO-RAN . . . . . . . . . . . . . . . 37

5
5.1
5.2
5.2.1
5.2.2
5.2.3
5.3

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


Configuring IMSI-based handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
IMSI-based intra-frequency handover . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Activating IMSI-based intra-frequency handover . . . . . . . . . . . . . . . . . . 41
Verifying IMSI-based intra-frequency handover. . . . . . . . . . . . . . . . . . . 42
Deactivating IMSI-based intra-frequency handover. . . . . . . . . . . . . . . . 43
IMSI-based inter-frequency handover . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Id:0900d805808e4fce
Confidential

Activating and Verifying RAN04 Features

5.3.1
5.3.2
5.3.3
5.4
5.4.1
5.4.2
5.4.3
5.5
5.5.1
5.5.2
5.5.3
6

6.1
6.2
6.3
7
7.1
7.1.1
7.1.2
7.1.3
7.2
7.2.1
7.2.2
7.2.2.1
7.2.2.2
7.2.3
7.2.3.1
7.2.3.2

Activating IMSI-based inter-frequency handover . . . . . . . . . . . . . . . . . . 44


Verifying IMSI-based inter-frequency handover . . . . . . . . . . . . . . . . . . . 45
Deactivating IMSI-based inter-frequency handover . . . . . . . . . . . . . . . . 46
IMSI-based inter-system handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Activating IMSI-based inter-system handover . . . . . . . . . . . . . . . . . . . . 47
Verifying IMSI-based inter-system handover . . . . . . . . . . . . . . . . . . . . . 48
Deactivating IMSI-based inter-system handover . . . . . . . . . . . . . . . . . . 49
Immediate IMSI-based inter-frequency/inter-system handover . . . . . . . 50
Activating immediate IMSI-based inter-frequency/inter-system handover .
50
Verifying immediate IMSI-based inter-frequency/inter-system handover 52
Deactivating immediate IMSI-based inter-frequency/inter-system handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Features RAN2.0027 and RAN 2.0026: Threshold Based PM Notification
Triggering and KPI Calculations in the RNC Element Manager, Feature Activation Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Activating the threshold-based notification triggering and the KPI calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Verifying the threshold-based notification triggering and the KPI calculation
56
Deactivating the threshold-based notification triggering and the KPI calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Activating and Operating Subscriber and Equipment Trace . . . . . . . . . . 58
Activating subscriber and equipment trace . . . . . . . . . . . . . . . . . . . . . . . 58
Activating subscriber and equipment trace . . . . . . . . . . . . . . . . . . . . . . . 58
Verifying subscriber and equipment trace. . . . . . . . . . . . . . . . . . . . . . . . 60
Deactivating subscriber and equipment trace . . . . . . . . . . . . . . . . . . . . . 61
Operating subscriber and equipment trace . . . . . . . . . . . . . . . . . . . . . . . 62
Operation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Starting tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Management-based activation of trace. . . . . . . . . . . . . . . . . . . . . . . . . . 63
Signalling-based activation of trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Stopping tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Management-based deactivation of trace . . . . . . . . . . . . . . . . . . . . . . . . 65
Signalling-based deactivation of trace . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Related information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Id:0900d805808e4fce
Confidential

DN0988623

Activating and Verifying RAN04 Features

List of figures
Figure 1
Figure 2

DN0988623

Example of IPv4 configuration for Iu-BC . . . . . . . . . . . . . . . . . . . . . . . . 19


Example of locking the cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Id:0900d805808e4fce
Confidential

Activating and Verifying RAN04 Features

List of tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7

Radio resource management and telecom features . . . . . . . . . . . . . . . . 8


Transmission and transport features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Operability features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Performance monitoring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Performance monitoring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
WSMLC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Mandatory WLCSE parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Id:0900d805808e4fce
Confidential

DN0988623

Activating and Verifying RAN04 Features

Summary of changes

Summary of changes
Changes 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 Activation Manual

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

Activating and Operating Subscriber and Equipment Trace

Changes between issues 01A (2011-06-20, WCDMA RAN RU30) and 01B (2011-1216, 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 Trace

Changes between issues 01 (2011-03-25, WCDMA RAN RU30) and 01A (2011-0620, WCDMA RAN RU30)
The following feature activation instructions have been updated:

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

Issue 01
The 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 Coordinates, Feature Activation Manual
Feature RAN2.0042: Nokia Siemens Networks Multi-Operator RAN, Feature Activation Manual
Feature RAN2.0060: IMSI-based Handover, Feature Activation Manual

This is the first issue of the document.

DN0988623

Id:0900d805808f169d
Confidential

Introduction

Activating and Verifying RAN04 Features

1 Introduction
1.1
1.1.1

Introduction to RAN04 Feature Activation Instructions


RAN04 documentation for radio resource management and telecom
features
See 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 documents

This feature does not require activation

RAN475: Multi-RAB: CS data + PS


data

This feature has no related documents

This feature does not require activation

RAN920: Selective NRT DCH Data


Rate Set

WCDMA RAN RRM Packet Sched- This feature does not require activauler
tion

RAN2.0022: Support for Volume


Based Charging

This feature has no related documents

This feature does not require activation

RAN2.0023: Service Area Broadcast

This feature has no related documents

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 Geographical Coordinates, Feature Activation 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

This feature does not require activation

RAN2.0060: IMSI Based Handover WCDMA RAN RRM Handover


Control

Feature RAN2.0060: IMSI-based


Handover, Feature Activation
Manual

RAN2.0079: Directed RRC Connection Setup

WCDMA RAN RRM Handover


Control

This feature does not require activation

RAN2.0105: Inter-RNC Intra-Frequency Hard Handover

WCDMA RAN RRM Handover


Control

This feature does not require activation

RAN2.0107: RRC Connection Reestablishment

WCDMA RAN RRM Packet Sched- This feature does not require activauler
tion

Table 1

Radio resource management and telecom features

Id:0900d805808f0cf6
Confidential

DN0988623

Activating and Verifying RAN04 Features

1.1.1.1

Introduction

Reference documentation
For 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 parameters

For counter descriptions, see:

RNC counters - RNW part


RNC counters transport and HW part
WBTS counters
AXC counters
Reference Information Service in NOLS

For 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 faults

For information on license management, see Nokia Siemens Networks license management concept and its implementation in WCDMA RAN in License management in
WCDMA RAN.

1.1.2

RAN04 Transmission and Transport features


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

Feature
RAN2.0036: RNC T1 interface

Table 2

DN0988623

Other related descriptions


WCDMA RAN System Description

Related instructions
This feature does not require
activation

Transmission and transport features

Id:0900d805808f0cf6
Confidential

Introduction

Activating and Verifying RAN04 Features

Feature

Other related descriptions

Related instructions

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 Interface

WCDMA RAN ATM Transport

This feature does not require


activation

RAN653: US WCDMA BTS T1 Interface

WCDMA RAN ATM Transport

This feature does not require


activation

RAN952: Optimized Iub AAL2 Reservations for


SRBs

WCDMA RAN ATM Transport

This feature does not require


activation

Table 2

Transmission and transport features (Cont.)

1.1.2.1

Reference documentation
For 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 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 parameters

For counter descriptions, see:

10

RNC Counters - RNW Part


RNC Counters Transport and HW Part
WBTS Counters

Id:0900d805808f0cf6
Confidential

DN0988623

Activating and Verifying RAN04 Features

Introduction

AXC Counters
I-HSPA Adapter Measurements and Counters
Reference Information Service in NOLS

For 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 (70009000)
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 Alarms

For information on license management, see Nokia Siemens Networks license management concept and its implementation in WCDMA RAN in License management in
WCDMA RAN.

1.1.3

RAN04 documentation for operability features


See 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 Configuration Management

This feature does not require activation.

RAN656: WCEL Lock and Unlock


from NetAct

WCDMA RAN and I-HSPA Configuration Management

This feature does not require activation.

RAN2.0006: HW Inquiry from


NetAct

WCDMA RAN and I-HSPA Network


Inventory

This feature does not require activation.

RAN2.0073: Automatic Notification


to NetAct for Changed AXC HW
Configuration

WCDMA RAN and I-HSPA Network


Inventory

This feature does not require activation.

RAN2.0097: Time Zone Support in


Element Managers

WCDMA RAN and I-HSPA Time


Management

This feature does not require activation.

Table 3

DN0988623

Operability features

Id:0900d805808f0cf6
Confidential

11

Introduction

Activating and Verifying RAN04 Features

Feature ID: Name

Functional Area Description

Feature implementation

RAN2.0098: Daylight Saving Time


Support in the Element Manager

WCDMA RAN and I-HSPA Time


Management

This feature does not require activation.

Table 3

Operability features (Cont.)

1.1.4

RAN04 documentation for performance monitoring features


See 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

RAN2.0002: Subscriber
Trace

WCDMA RAN Subscriber and Equipment


Trace

This feature does not require activation.

RAN2.0026: KPI Calculations in RNC Element


Manager

WCDMA RAN performance management

This feature does not require activation.

RAN2.0027: Threshold
Based PM Notification
Triggering

WCDMA RAN performance management

This feature does not require activation.

RAN2.0077: AXC ATM


Performance Monitoring

WCDMA RAN performance management

This feature does not require activation.

Table 4

Performance monitoring features

1.1.4.1

Information on Parameters, Counters, and Alarms


For information on the parameters, counters and alarms related to each feature, see the
System impact section of the feature descriptions.
For parameter descriptions, see:

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 parameters

For counter descriptions, see:

RNC counters - RNW part


RNC counters transport and HW part
WBTS counters
AXC counters
Reference Information Service in NOLS

For alarm descriptions, see:

12

RNC Notices (0-999)

Id:0900d805808f0cf6
Confidential

DN0988623

Activating and Verifying RAN04 Features

Introduction

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 faults

For information on licence management, see Nokia Siemens Networks license management concept and its implementation in WCDMA RAN in License management in
WCDMA RAN.

1.1.5

RAN04 documentation for BTS solution features


See 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

This feature does not require activation.

RAN2.0043: Double Code


Channel Capacity (WSPC)

Wideband Signal Processor (WSPC) Unit


Description

This feature does not require activation.

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

AXC Product Description

This feature does not require activation.

RAN2.0066: WSMB (Wideband Summing & Multiplexing Version B) Unit

Wideband Summing and Multiplexing


(WSMB) Unit Description

This feature does not require activation.

RAN2.0071: Efficiency
Enhanced WPA (EEWPA)

Wideband Power Amplifier (WPAx) Unit


Description

This feature does not require activation.

RAN2.0072: WAM Support

Wideband Application Manager (WAMA)


Unit Description

This feature does not require activation.

RAN2.0086: Master WAM


Redundancy

Wideband Application Manager (WAMA)


Unit Description

This feature does not require activation.

RAN639: Support for 3rd


Party Mast Head Amplifier

This feature does not have related documents

This feature does not require activation.

RAN644: WCDMA Metrosite


Door Alarm

MetroSite 50 BTS Optional Unit Descriptions

This feature does not require activation.

MetroSite 50 BTS Product Description


RAN710: Micro MHA and
RealTilt+

This feature does not have related documents

This feature does not require activation.

RAN771: 1900MHz BTS


Configuration

This feature does not have related documents

This feature does not require activation.

Table 5

DN0988623

Performance monitoring features

Id:0900d805808f0cf6
Confidential

13

Introduction

Activating and Verifying RAN04 Features

Feature ID: Name


RAN899: WPAK

Table 5

Descriptions

Instructions

This feature does not have related documents

This feature does not require activation.

Performance monitoring features (Cont.)

1.1.5.1

Information on parameters, counters, and alarms


For information on the parameters, counters and alarms related to each feature, see the
System impact section of the feature descriptions.
For parameter descriptions, see:

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 parameters

For counter descriptions, see:

RNC counters - RNW part


RNC counters transport and HW part
WBTS counters
AXC counters
Reference Information Service in NOLS

For alarm 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 faults

For information on licence management, see Nokia Siemens Networks license management concept and its implementation in WCDMA RAN in License management in
WCDMA RAN.

14

Id:0900d805808f0cf6
Confidential

DN0988623

Activating and Verifying RAN04 Features

1.2

Licensing
The 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 information 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.

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 Features.
License management in mcRNC
For details on the mcRNC-specific license management, see License Management in
mcRNC in WCDMA RAN License Operation.
License management in WBTS
For details on the WBTS-specific license management, see WCDMA BTS License Management Functionality Description in WCDMA RAN License Operation.

DN0988623

Id:0900d8058083ab26
Confidential

15

Activating RAN2.0023: Service Area Broadcast

Activating and Verifying RAN04 Features

2 Activating RAN2.0023: Service Area Broadcast


2.1

Activating Service Area Broadcast


Purpose
Follow 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 start
This 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 ACTIVATED
If 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

Open the OMS Element Manager and go to Tree View.


Follow this path:
Configuration Management j Network Topology j Tree View

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

You can configure Iu-BC parameters only if Service Area Broadcast Protocol (SABP) is
in use.

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.

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

16

Id:0900d8058083b890
Confidential

DN0988623

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 Supervision.
Creating IMA group in Configuring and Supervising Physical Interfaces for RNC.
Configuring SDH for ATM transport in Physical Interfaces Configuration and Supervision.
Creating SDH protection group in Physical Interfaces Configuration and Supervision.
Creating phyTTP for ATM in Physical Interfaces Configuration and Supervision.

Configure IP for Iu-BC


Before you start
All 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 Management for RNC.
a) Check the selected ICSU unit towards the CBC
The 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 - ICSUforCBC 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 ICSU
Create 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 Connection 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 (distributing incoming traffic between several ICSU units), give the network interface

DN0988623

Id:0900d8058083b890
Confidential

17

Activating RAN2.0023: Service Area Broadcast

Activating and Verifying RAN04 Features

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-BC
For 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.

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:<unit type>, <unit index...>:[<destination IP
address>|<default route> def,[<netmask length>]]:<gateway IP
address>:[<route type>]:[<preference>];

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:<unit type>,<unit index>:<destination IP
address>,[<prefix length>]:<gateway IP address>:[<route
type>]:[<route preference>];
Example: Configuring IP for Iu-BC through ICSU units
The 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.

18

Id:0900d8058083b890
Confidential

DN0988623

Activating and Verifying RAN04 Features

RNC site

ICSU-0

Activating RAN2.0023: Service Area Broadcast

Core site
Router terminating
IP over ATM PVCs
(can also be an
extra ATM Interface)

MGW

RNC

10.1.1.1

ICSU-1

NIS

NIS

NIS

10.1.1.200

CBC
any
media

ICSU-2

...

STM-1

VPI=x

VPI=y
VP
cross
connects

ICSU-18

subnet 10.1.1.0/32

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;

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;

DN0988623

Id:0900d8058083b890
Confidential

19

Activating RAN2.0023: Service Area Broadcast

Activating and Verifying RAN04 Features

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:1
28:"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;
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 Secondary 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 outcome
The cell is unblocked and CBC receives a SABP:Restart message which means that
the Service Area Broadcast is activated in the cell.
Unexpected outcome
If 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 information
After 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.

20

Id:0900d8058083b890
Confidential

DN0988623

Activating and Verifying RAN04 Features

2.2

Verifying Service Area Broadcast


Purpose
Follow the procedure below to verify that the Service Area Broadcast feature is activated.
Steps

Send a SABP: Write Replace message from the CBC to the activated cell or
service area.
Expected outcome
The 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.

DN0988623

Id:0900d80580811550
Confidential

21

Activating and Verifying RAN04 Features

2.3

Deactivating Service Area Broadcast


Purpose
Follow the procedure below to deactivate the Service Area Broadcast feature.
Steps

Lock the cell objects.

Figure 2
2

Example of locking the cell

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.

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

Unlock the cell objects.


Expected outcome
The 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 outcome
If the deactivation fails, an error code is returned immediately.

22

Id:0900d80580811551
Confidential

DN0988623

Activating and Verifying RAN04 Features

2.4

Verifying deactivation of Service Area Broadcast


Purpose
Follow the procedure below to verify that the Service Area Broadcast feature is deactivated.
Steps

Send a SABP: Write Replace message from the CBC to the deactivated cell or
service area.
Expected outcome
The 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.

DN0988623

Id:0900d80580811552
Confidential

23

Feature RAN2.0041: LCS - Cell Coverage Based


(RTT) with Geographical Coordinates, Feature Activa-

Activating and Verifying RAN04 Features

3 Feature RAN2.0041: LCS - Cell Coverage


Based (RTT) with Geographical Coordinates,
Feature Activation Manual
3.1

Activating LCS Cell Coverage Based (RTT) with Geographical Coordinates


Purpose
Follow the procedure below to activate the LCS - Cell Coverage Based (RTT) with Geographical Coordinates feature.
For more information on the feature, see Section Cell Coverage Based (RTT) with Geographical Coordinates in Location Services.
Before you start
This 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

Open the OMS Element Manager.

Go to Tree View:
Network Management j Topology Tree View

Configure the WSMLC parameters.


Create or modify the WSMLC object by setting the WSMLC parameters. See the following 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 difference measurements lie within
the confidence area that is
reported, for example, 67 or 95
per cent.

0..100 per cent

Table 6

24

WSMLC parameters

Id:0900d8058089c122
Confidential

DN0988623

Activating and Verifying RAN04 Features

Name

Description

Range

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 formation 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 algorithms 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

Table 6
4

Feature RAN2.0041: LCS - Cell Coverage Based


(RTT) with Geographical Coordinates, Feature Activa-

WSMLC parameters (Cont.)

Configure the WLCSE parameters.


Create or modify the WLCSE object by setting the WLCSE parameters. See the following 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.

DN0988623

Id:0900d8058089c122
Confidential

25

Feature RAN2.0041: LCS - Cell Coverage Based


(RTT) with Geographical Coordinates, Feature Activa-

Activating and Verifying RAN04 Features

Parameter name

Description

Range

Antenna Bearing

This parameter defines


antenna direction
measured clockwise from
North [in degrees].

0..359 (degrees)

Antenna HPBW (Half


This parameter defines half
Power Beam Width) for Cell power beam width in
degrees (-3dB angle) of the
antenna.
Antenna Coordinates

1..360 (degrees)

Latitude: degrees (0, 90),


Coordinates of the TX
antenna of the cell in WGS- minutes (0..59), seconds
(0..59), fractions (0..99),
84 format.
Latitude sign and Longitude Latitude sign: (0,1)
sign:
0 = positive (North latitude
or East longitude)
1 = negative (South latitude
or West longitude).
Altitude direction:
0 = height (TX antenna
above sea level)

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)

1 = depth (TX antenna


below sea level)
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 characterisation

The first category corresponds to Urban or Bad


Urban channels. The
second category corresponds to Rural or
Suburban channels.

Enumerated (possibly
heavy multipath and NLOS
conditions, no or light multipath and usually LOS conditions, 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

26

Mandatory WLCSE parameters

Id:0900d8058089c122
Confidential

DN0988623

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.

Select the General tab.

Enable the LCS functionality parameter.


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

DN0988623

Id:0900d8058089c122
Confidential

27

Activating and Verifying RAN04 Features

3.2

Verifying LCS Cell Coverage Based (RTT) with Geographical Coordinates


Purpose
By trying to locate a particular UE, you can verify that the LCS Cell Coverage Based
(RTT) with Geographical Coordinates feature has been activated.
Steps

Send a LOCATION REPORTING CONTROL message to the RNC.


Send the location request by UE, iGMLC or MSC.
Expected outcome
The 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.

28

Id:0900d8058081ca7c
Confidential

DN0988623

Activating and Verifying RAN04 Features

3.3

Deactivating LCS Cell Coverage Based (RTT) with Geographical Coordinates


Purpose
Follow the procedure below to deactivate the LCS Cell Coverage Based (RTT) with
Geographical Coordinates feature.
Before you start
Make sure that the RNC is operational.
Steps

Open the OMS Element Manager.

Go to Tree View:
Network Management j Topology Tree View

Open the RNC object.


Select the RNC object and select Object Open.

Select the General tab.

Disable the LCS functionality parameter.


For the LCSfunctionality parameter, select Disabled from the drop-down menu.
Further information
When the parameter has been disabled, locationing is no longer possible. It is, however,
recommended to proceed with the next step.
Expected outcome
The LCS Cell Coverage Based (RTT) with Geographical Coordinates feature has
been deactivated.

DN0988623

Id:0900d8058089c18e
Confidential

29

Feature RAN2.0042: Nokia Siemens Networks MultiOperator RAN, Feature Activation Manual

Activating and Verifying RAN04 Features

4 Feature RAN2.0042: Nokia Siemens


Networks Multi-Operator RAN, Feature Activation Manual
4.1

Activating Nokia Multi-Operator RAN


Purpose
Follow this procedure to activate the Nokia Multi-Operator RAN feature in the RNC.
Before you start
This 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 - Parameter Handling.
Steps

g
2

Check the state of MORAN FIFILE parameter (ACTIVATED or DEACTIVATED) with


command ZWOS:2,797:;.
To proceed with activation the state must be ACTIVATED.

Open the OMS Element Manager and go to Tree View.


Follow this path:
Configuration Management j Network Topology j Tree View
You can also perform the activation in Nokia NetAct.

Expand topology tree and select Edit Parameters in IUO object.


For more information, see section Radio network management in Radio Network Administration.

Fill in the parameters of the IUO object.

Create another IUCS and IUPS object in topology tree.

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.

30

Id:0900d80580896cbe
Confidential

DN0988623

Activating and Verifying RAN04 Features

Feature RAN2.0042: Nokia Siemens Networks MultiOperator RAN, Feature Activation Manual

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 Administration.
7

Unlock the cells.


Further information
For more information on configuring the parameters and IP address of PS, see Configuring Iu-PS parameters of RNC for MO-RAN.
For more information on configuring the CS parameters, see Configuring Iu-CS parameters of RNC for MO-RAN.
Expected outcome
Nokia Multi-Operator RAN has been activated successfully. For more information, see
Verifying Nokia Multi-Operator RAN.
Further information
After 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.

DN0988623

Id:0900d80580896cbe
Confidential

31

Activating and Verifying RAN04 Features

4.2

Verifying Nokia Multi-Operator RAN


Purpose
Follow this procedure to verify that the Nokia Multi-Operator RAN feature is functioning.
Before you start
Make 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 Configuring Iu-PS parameters of RNC for MO-RAN.
Steps

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

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 outcome
Nokia Multi-Operator RAN has been activated if the calls are successful, and if the handovers are successful in the network of the correct operator.

32

Id:0900d80580815160
Confidential

DN0988623

Activating and Verifying RAN04 Features

4.3

Deactivating Nokia Multi-Operator RAN


Purpose
Follow this procedure to deactivate the Nokia Multi-Operator RAN feature in the RNC.
Before you start
Make sure that the Nokia Multi-Operator RAN has been activated.
Steps

Open the OMS Element Manager and go to Tree View.


Follow this path:
Configuration Management j Network Topology j Tree View

g
2

You can also perform the activation in Nokia NetAct.

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.
or
2.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 Administration.

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

Delete the related lUCS and lUPS object.

Delete the lUO object.

Deactivate the feature by using WO - Parameter Handling.


For more information, see WO - Parameter Handling.

DN0988623

Restart the OMS Element Manager.

Id:0900d80580815180
Confidential

33

Activating and Verifying RAN04 Features

Expected outcome
Nokia Multi-Operator RAN has been deactivated, and no calls with other operator's SIM
are possible.
Further information
After deactivating, there is no need to reset the RNC.

34

Id:0900d80580815180
Confidential

DN0988623

Activating and Verifying RAN04 Features

4.4
4.4.1

Configuring parameters for MO-RAN


Configuring Iu-CS parameters of RNC for MO-RAN
Before you start
The 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 configured, 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

Open the OMS Element Manager and go to Tree View.


Follow this path:
Configuration Management j Network Topology j Tree View

Create the lUCS object.

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 Configuration Parameters.
Note that if there are cells under this core network that are already using the Global
PLMNid parameter, its value cannot be changed.

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 information
For information on Iu-CS control plane configuration, see the following instructions:

DN0988623

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 Integrating RNC.

Id:0900d80580815184
Confidential

35

Activating and Verifying RAN04 Features

4.4.2

Configuring Iu-PS parameters of RNC for MO-RAN


Iu-PS User Plane configuration
For 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 RNC

Iu-PS Control Plane configuration


For information on the Iu-PS Control Plane configuration, see the following instructions:

36

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 Configuring IP Connection for RNC

Id:0900d80580815182
Confidential

DN0988623

Activating and Verifying RAN04 Features

4.4.3

Configuring Iu-BC parameters of RNC for MO-RAN


Before you start
Note 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

Open the OMS Element Manager and go to Tree View.


Follow this path:
Configuration Management j Network Topology j Tree View

Select Edit Parameters in the CBCI object.

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 information
For more information on parameters, see WCDMA Radio Network Configuration Parameters.

DN0988623

Id:0900d80580815183
Confidential

37

Feature RAN2.0060: IMSI-based Handover, Feature


Activation Manual

Activating and Verifying RAN04 Features

5 Feature RAN2.0060: IMSI-based Handover,


Feature Activation Manual
5.1

Configuring IMSI-based handover


Purpose
The 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 start
This feature belongs to application software. Ensure that you have a valid licence
(FIFILE licence).
Steps

Open the OMS Element Manager.

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

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 Configuring 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.

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.

Create the HOP objects if needed.


For more information, see Creating handover path.

38

Id:0900d8058083b88f
Confidential

DN0988623

Activating and Verifying RAN04 Features

Feature RAN2.0060: IMSI-based Handover, Feature


Activation Manual

Create the WBTS objects if needed.


For more information, see Creating a WCDMA BTS site.

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.

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.

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 information (DefaultAuthorisedNetworkId) in the RNC object.
Note that by default all the PLMNs are authorised.
Expected outcome
The IMSI-based handover feature has been configured and is ready to be activated.
Further information
The 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:

DN0988623

Authorised Network Identifier (AuthorisedNetworkId)


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

Id:0900d8058083b88f
Confidential

39

Feature RAN2.0060: IMSI-based Handover, Feature


Activation Manual

Activating and Verifying RAN04 Features

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.

40

Id:0900d8058083b88f
Confidential

DN0988623

Activating and Verifying RAN04 Features

5.2
5.2.1

IMSI-based intra-frequency handover


Activating IMSI-based intra-frequency handover
Purpose
Follow this procedure to activate the IMSI-based intra-frequency handover in the RNC.
Before you start
Make sure you have configured the IMSI-based handover correctly. For more information, see Configuring IMSI-based handover.
Steps

Open the OMS Element Manager.

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

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 outcome
The IMSI-based intra-frequency handover has been activated.
Further information
After activating, there is no need to reset the RNC.

DN0988623

Id:0900d8058081cb22
Confidential

41

Activating and Verifying RAN04 Features

5.2.2

Verifying IMSI-based intra-frequency handover


Purpose
When 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 start
All conditions mentioned in Activating IMSI-based intra-frequency handover must be fulfilled.
Steps

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.

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 outcome
The 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.

42

Id:0900d8058081cb20
Confidential

DN0988623

Activating and Verifying RAN04 Features

5.2.3

Deactivating IMSI-based intra-frequency handover


Purpose
Follow this procedure to deactivate the intra-frequency IMSI-based handover in the
RNC.
Steps

Open the OMS Element Manager.

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

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 outcome
The IMSI-based intra-frequency handover has been deactivated.
Further information
After deactivating, there is no need to reset the RNC.

DN0988623

Id:0900d8058081cb21
Confidential

43

Activating and Verifying RAN04 Features

5.3
5.3.1

IMSI-based inter-frequency handover


Activating IMSI-based inter-frequency handover
Purpose
Follow this procedure to activate the IMSI-based inter-frequency handover in the RNC.
Before you start
Make sure you have configured the IMSI-based handover correctly. For more information, see Configuring IMSI-based handover.
Steps

Open the OMS Element Manager.

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

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 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 outcome
The IMSI-based handover inter-frequency has been activated.
Further information
After activating, there is no need to reset the RNC.

44

Id:0900d8058081cb26
Confidential

DN0988623

Activating and Verifying RAN04 Features

5.3.2

Verifying IMSI-based inter-frequency handover


Purpose
When 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 start
All conditions mentioned in Activating IMSI-based inter-frequency handover must be fulfilled.
Steps

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 subscriber or as any PLMN in the WANE set used by the subscriber.

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-frequency measurement. Cell B is not included in the neighbour cell list in question.
Expected outcome
The 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.

DN0988623

Id:0900d8058081cb24
Confidential

45

Activating and Verifying RAN04 Features

5.3.3

Deactivating IMSI-based inter-frequency handover


Purpose
Follow this procedure to deactivate the inter-frequency IMSI-based handover in the
RNC.
Steps

Open the OMS Element Manager.

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

Modify the FMCI.


In the used FMCI sets, set the value of the parameter IMSIbasedIFHO to 'immidiate
HO not allowed'.
Expected outcome
The IMSI-based inter-frequency handover has been deactivated.
Further information
After deactivating, there is no need to reset the RNC.

46

Id:0900d8058081cb25
Confidential

DN0988623

Activating and Verifying RAN04 Features

5.4
5.4.1

IMSI-based inter-system handover


Activating IMSI-based inter-system handover
Purpose
Follow this procedure to activate the IMSI-based inter-system handover in the RNC.
Before you start
Make sure you have configured the IMSI-based handover correctly. For more information, see Configuring IMSI-based handover.
Steps

Open the OMS Element Manager.

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

Modify the FMCG object.

Set the value of the IMSIBasedGsmHo parameter from the FMCG to value 'immidiate 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 outcome
The IMSI-based inter-system handover has been activated.
Further information
After activating, there is no need to reset the RNC.

DN0988623

Id:0900d8058081cb2a
Confidential

47

Activating and Verifying RAN04 Features

5.4.2

Verifying IMSI-based inter-system handover


Purpose
When 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 start
All conditions mentioned in Activating IMSI-based inter-system handover must be fulfilled.
Steps

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 subscriber or as any PLMN in the WANE set used by the subscriber.

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 intersystem (GSM) measurement. Cell B is not included in the neighbour cell list in question.
Expected outcome
The 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.

48

Id:0900d8058081cb28
Confidential

DN0988623

Activating and Verifying RAN04 Features

5.4.3

Deactivating IMSI-based inter-system handover


Purpose
Follow this procedure to deactivate the IMSI-based inter-system handover in the RNC.
Steps

Open the OMS Element Manager.

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

Modify the FMCG.


In the used FMCG sets, set the value of the parameter IMSIbasedGsmHo to immidiate
HO not allowed'.
Expected outcome
The IMSI-based inter-system handover has been deactivated.
Further information
After deactivating, there is no need to reset the RNC.

DN0988623

Id:0900d8058081cb29
Confidential

49

Activating and Verifying RAN04 Features

5.5

5.5.1

Immediate IMSI-based inter-frequency/inter-system


handover
Activating immediate IMSI-based inter-frequency/inter-system
handover
Purpose
Follow this procedure to activate the immediate IMSI-based inter-frequency/intersystem handover in the RNC.
Before you start
Make sure you have configured the IMSI-based handover correctly. For more information, see Configuring IMSI-based handover.
Steps

Open the OMS Element Manager.

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

Modify the FMCI or FMCG.


Before you start
Set 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 outcome
The immediate IMSI-based inter-frequency/inter-system handover has been activated.
Further information
Immediate 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'.

50

Id:0900d8058081cb2f
Confidential

DN0988623

Activating and Verifying RAN04 Features

2. The active set cell in question has one or more inter-frequency/inter-system neighbour 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 measurement 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 immediate IMSI-based inter-frequency handover cause is triggered.
After activating, there is no need to reset the RNC.

DN0988623

Id:0900d8058081cb2f
Confidential

51

Activating and Verifying RAN04 Features

5.5.2

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


handover
Purpose
When the immediate IMSI-based inter-frequency/inter-system handover feature is activated, the user can verify that the activation succeeded and that the IMSI-based
handover works.
Before you start
All conditions mentioned in Activating immediate IMSI-based inter-frequency/intersystem handover must be fulfilled.
Steps

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.

Make all three cells available to the UE.


The UE sends an intra-frequency measurement report on event 1a to cell C. The intrafrequency 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 measurement. Cell B is not included in the neighbour cell list in question.
Expected outcome
The activation of immediate IMSI-based inter-frequency/inter-system handover has succeeded 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.

52

Id:0900d8058081cb2d
Confidential

DN0988623

Activating and Verifying RAN04 Features

5.5.3

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


handover
Purpose
Follow this procedure to deactivate the immediate IMSI-based inter-frequency/intersystem handover in the RNC.
Steps

Open the OMS Element Manager.

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

Modify the FMCI/FMCG.


In the used FMCI/FMCG sets, set the value of the parameters
IMSIbasedIFHO/IMSIbasedGsmHo to 'immidiate HO not allowed'.
Expected outcome
The immediate IMSI-based inter-frequency/inter-system handover has been deactivated.
Further information
After deactivating, there is no need to reset the RNC.

DN0988623

Id:0900d8058081cb2e
Confidential

53

Features RAN2.0027 and RAN 2.0026: Threshold


Based PM Notification Triggering and KPI Calculations

Activating and Verifying RAN04 Features

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 calculation
Purpose
Follow this procedure to activate the RAN2.0027: Threshold Based PM Notification Triggering and the RAN2.0026: KPI Calculations in RNC Element Manager features in the
OMS.
Before you start
These 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

Transfer the license to the /tmp folder.

Log in to the OMS as a root user.

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

Import the license file.


Use the following command:
# lmcli importLicence /tmp/<license_xml_file>

g
5

To check all the imported licenses, use the following command:


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

Check if the activation was successful.


Use the following command: # lmcli getFeatureStatus 973

54

Id:0900d805808e39a2
Confidential

DN0988623

Activating and Verifying RAN04 Features

Features RAN2.0027 and RAN 2.0026: Threshold


Based PM Notification Triggering and KPI Calculations

Expected outcome
The features are in active state.
Further information
Restart of the OMS is not required after the activation of this feature.
For more information on the threshold-based notifications, see section Threshold monitoring in WCDMA RAN Performance Management. For more information on the key
performance indicators, see section Key performance indicators in WCDMA RAN Performance Management. For more information on the features, see section Administering the Element Manager in Using Element Manager in OMS.

DN0988623

Id:0900d805808e39a2
Confidential

55

Activating and Verifying RAN04 Features

6.2

Verifying the threshold-based notification triggering and


the KPI calculation
Purpose
Follow 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

Ensure that the user has Read or Modify access rights to the performance management domain.

Open the Application Launcher session in OMS.

Start the NE Threshold Management application.


Expected outcome
The application starts without displaying any notification about the licensing. It is
possible to use the application for managing thresholds.

56

Id:0900d805808e39a0
Confidential

DN0988623

Activating and Verifying RAN04 Features

6.3

Deactivating the threshold-based notification triggering


and the KPI calculation
Purpose
Follow 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

Log in to the OMS as a root user.

Deactivate the license.


Use the following command: # lmcli deactivateFeature 973

Check if the deactivation was successful.


Use the following command: # lmcli getFeatureStatus 973
Expected outcome
The features are in inactive state.

Delete the license (optional).


Use the following command:
# lmcli deleteLicence /tmp/<license xml file>
Further information
Restart of the OMS is not required after the deactivation of this feature.

DN0988623

Id:0900d805808e39a1
Confidential

57

Activating and Operating Subscriber and Equipment


Trace

Activating and Verifying RAN04 Features

7 Activating and Operating Subscriber and


Equipment Trace
7.1
7.1.1

Activating subscriber and equipment trace


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

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 subscriber and equipment trace.
For more information, see WCDMA RAN Subscriber and Equipment Trace.
Before you start
This 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 information) 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 -> UEQualityRepInterval

The 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 subscriber trace data. For more information on subscriber trace support in NetAct, see the
NetAct operating documentation.

58

Id:0900d80580817c37
Confidential

DN0988623

Activating and Verifying RAN04 Features

Activating and Operating Subscriber and Equipment


Trace

Steps
1

Install a valid licence.


Expected outcome
The subscriber and equipment trace feature is activated.

DN0988623

Id:0900d80580817c37
Confidential

59

Activating and Verifying RAN04 Features

7.1.2

Verifying subscriber and equipment trace


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

Open an MML connection to the IPA-RNC


Or
for the mcRNC and the I-HSPA Adapter, open the SSH connection to the network
element and, at the sCLI prompt, enter command fsclish.

Start tracing a subscriber.


Give the following commands, including the IMSI of the subscriber that will be used for
the test call:

MML command for the IPA-RNC


ZT7T:IMSI=123456789:REF=123,TYPE=HO;
sCLI command for the mcRNC and the I-HSPA Adapter
set subs-trace activate-trace imsi 123456789 trace-ref 123
trace-type handover

When a subscriber trace is activated locally in the RNC using MML/sCLI, it is necessary
to create a virtual trace in NetAct TraceViewer so that TraceViewer can align the
received trace data with a proper trace reference number. For more information, see the
NetAct operating documentation.

Make a short CS voice call with the traced UE.

In NetAct TraceViewer, check that subscriber trace data is received from the RNC.
Expected outcome
The subscriber and equipment trace feature has been activated successfully if subscriber trace data is received from the RNC and can be viewed in NetAct TraceViewer.

60

Id:0900d805808ee3f4
Confidential

DN0988623

Activating and Verifying RAN04 Features

7.1.3

Deactivating subscriber and equipment trace


Please note that the RNC product naming practice is changing. For more information,
see Guide to WCDMA RAN and I-HSPA Operating Documentation.
Purpose
Follow the procedure below to deactivate the subscriber and equipment trace feature in
the RNC.
Summary
The subscriber and equipment trace feature can be deactivated by uninstalling the
license in the IPA-RNC.
After uninstalling the license, the IPA-RNC will not produce trace data even if the core
network sends RANAP: CN INVOKE TRACE, and the Subscriber Trace Handling MML
command group is disabled.
Steps

Uninstall the license.


Expected outcome
The subscriber and equipment trace feature is deactivated.

DN0988623

There is no license control for this feature in the mcRNC and the I-HSPA Adapter. The
deactivation of Activating and Operating Subscriber and Equipment Trace in these controllers does not require any actions.

Id:0900d805808ee3f6
Confidential

61

Activating and Verifying RAN04 Features

7.2
7.2.1

Operating subscriber and equipment trace


Operation overview
There are two methods for trace activation:

Management-Based Activation (MBA) uses a direct Man-Machine Language (MML)


interface to the network element from which the operator wants to get trace data.
The operator needs to know under which RNC(s) the traced IMSI is (or will be)
located.
Signalling-Based Activation (SBA) is used for activating trace in all the NEs, which
are involved in the call. The operator starts the trace either in the HLR or in
MSC/SGSN, and the RNC receives the activation message from the core network.
Therefore, the operator does not need to know under which RNC the user is located.

The management-based activation method is supported to guarantee that trace activation in the RNC succeeds in all multivendor networks (where the Core Network (CN) and
Radio Access Network (RAN) are provided by different vendors).

62

Id:0900d805805d6ec8
Confidential

DN0988623

Activating and Verifying RAN04 Features

7.2.2
7.2.2.1

Starting tracing
Management-based activation of trace
Purpose
Follow this procedure to start a trace session for a subscriber using the Management
Based Activation method.
Summary
If the location of a user in the network is known at the RNC level, the MBA Trace direct
activation in the RNC can be used. The MBA Trace is a useful tool, for example, in cases
where CN does not support the SBA Trace.
Steps

Enter the following as parameters for the (RNC-local) MML command T7T.

Trace Reference number


subscribers IMSI
Trace Type

Expected outcome
The RNC starts the trace session. There can be a maximum of 50 simultaneous trace
sessions in the RNC.
When the traced subscriber establishes a connection to the RNC, the RNC starts a trace
recording session and sends trace reports to the NetAct TraceViewer application. If the
subscriber has an active call in the RNC at the time of trace session activation, a trace
recording session is started immediately in the RNC and it starts to send trace reports
to NetAct.
Trace reports are available in the TraceViewer application in NetAct.

DN0988623

Id:0900d805805d6ebe
Confidential

63

Activating and Verifying RAN04 Features

7.2.2.2

Signalling-based activation of trace


Purpose
Follow this procedure to start a trace session for a subscriber using the Signalling Based
Activation (SBA) method.
Summary
If the location of the user or user equipment in the network is unknown, starting the SBA
trace to the RNC through the core network (CN) can be used. The CN finds out the
serving RNC and starts the trace according to the parameters entered by the user.
Note that when the CN activates the trace in the RNC, the UE is already connected to
the RNC and the RNC starts to send trace records to NetAct.
It is possible to start several traces for the same user or user equipment in the RNC with
different trace reference numbers.
Steps

Start NetAct TraceViewer.

Open the New Trace creation dialog in the TraceViewer application.


a) Select either HLR, MSC, SGSN or 3G SGSN in the Element Type menu.
b) Select IMSI as Traced Target and enter the subscriber's IMSI in the Traced Number
field.
c) Select Start Time and Stop Time.
d) Click Activate.
For more information on activating subscriber and equipment trace, see NetAct
TraceViewer documentation.
Expected outcome
The core network starts the trace recording session in the RNC.
The RNC collects trace data according to trace parameters. The RNC sends trace
reports periodically in every 60 seconds to NetAct through the NWI3 interface. The RNC
buffers the trace data for 5 minutes if the report delivery to NetAct is not successful.
The NetAct TraceViewer application receives trace reports. The NetAct TraceViewer
application provides the tools for reporting the Trace data. The details for the usage of
these tools are described in NetAct product documentation.

64

Id:0900d805805d6ebb
Confidential

DN0988623

Activating and Verifying RAN04 Features

7.2.3
7.2.3.1

Stopping tracing
Management-based deactivation of trace
Purpose
Follow this procedure to stop a subscriber trace session in the RNC.
Steps

Enter the Subscriber's IMSI as the parameter for the RNC MML command T7U.
Expected outcome
The RNC stops the trace session. The trace parameters for the specific IMSI are
removed from the RNC's trace parameter table. If a trace recording session is ongoing,
it is terminated immediately.

DN0988623

Id:0900d805805d6ec6
Confidential

65

Activating and Verifying RAN04 Features

7.2.3.2

Signalling-based deactivation of trace


Purpose
Follow this procedure to stop a subscriber trace session in the RNC.
Steps

Stop the trace session.


Use either NetAct TraceViewer or connect directly to the MML interface of the core
network elements. If an active trace recording session exists at the time of deactivation,
the recording session may continue until the Iu connection is released. This depends on
whether the core network immediately sends a RANAP: CN DEACTIVATE TRACE
command to the RNC.
Expected outcome
The trace session is stopped.

66

Id:0900d805805d6ec3
Confidential

DN0988623

Activating and Verifying RAN04 Features

Related information

Related information
Activating IMSI-based intra-frequency handover
Instructions
Verifying IMSI-based intra-frequency handover
Deactivating IMSI-based intra-frequency handover
Verifying IMSI-based intra-frequency handover
Instructions
Activating IMSI-based intra-frequency handover
Deactivating IMSI-based intra-frequency handover
Deactivating IMSI-based intra-frequency handover
Instructions
Activating IMSI-based intra-frequency handover
Verifying IMSI-based intra-frequency handover
Activating IMSI-based inter-frequency handover
Instructions
Verifying IMSI-based inter-frequency handover
Deactivating IMSI-based inter-frequency handover
Verifying IMSI-based inter-frequency handover
Instructions
Activating IMSI-based inter-frequency handover
Deactivating IMSI-based inter-frequency handover
Deactivating IMSI-based inter-frequency handover
Instructions
Activating IMSI-based inter-frequency handover
Verifying IMSI-based inter-frequency handover
Activating IMSI-based inter-system handover
Instructions
Verifying IMSI-based inter-system handover
Deactivating IMSI-based inter-system handover
Verifying IMSI-based inter-system handover
Instructions
Activating IMSI-based inter-system handover
Deactivating IMSI-based inter-system handover

DN0988623

Id:
Confidential

67

Related information

Activating and Verifying RAN04 Features

Deactivating IMSI-based inter-system handover


Instructions
Activating IMSI-based inter-system handover
Verifying IMSI-based inter-system handover
Activating immediate IMSI-based inter-frequency/inter-system handover
Instructions
Verifying immediate IMSI-based inter-frequency/inter-system handover
Deactivating immediate IMSI-based inter-frequency/inter-system handover
Verifying immediate IMSI-based inter-frequency/inter-system handover
Instructions
Activating immediate IMSI-based inter-frequency handover/inter-system handover
Deactivating immediate IMSI-based inter-frequency handover/inter-system handover
Deactivating immediate IMSI-based inter-frequency/inter-system handover
Instructions
Activating immediate IMSI-based inter-frequency/inter-system handover
Verifying immediate IMSI-based inter-frequency/inter-system handover

68

Id:
Confidential

DN0988623