You are on page 1of 210

WCDMA RAN and I-HSPA, Rel.

RU30, Operating Documentation, Issue 08

Activating and Verifying RU20 Features


DN0988674 Issue 01H Approval Date 2012-08-24

Confidential

Activating and Verifying RU20 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 2012. 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:0900d8058095ac7a Confidential

DN0988674 Issue 01H

Activating and Verifying RU20 Features

Table of contents
This document has 210 pages. Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1 1.1 1.1.1 1.1.1.1 1.1.2 1.1.2.1 1.1.3 1.1.3.1 1.1.4 1.1.5 1.1.5.1 1.1.6 1.1.6.1 1.1.7 1.1.7.1 1.2 2 2.1 2.1.1 2.1.2 2.1.3 2.2 2.2.1 2.2.2 2.2.3 2.3 2.3.1 2.3.2 2.3.3 2.4 2.4.1 2.4.1.1 2.4.1.2 2.4.1.3 2.4.2 2.4.2.1 2.4.2.2 2.4.2.3 2.5 2.5.1 2.5.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to RU20 Feature Activation Instructions. . . . . . . . . . . . . . . RU20 radio resource management features . . . . . . . . . . . . . . . . . . . . . Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RU20 telecom features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RU20 transmission and transport features . . . . . . . . . . . . . . . . . . . . . . Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RU20 operability features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RU20 performance monitoring features. . . . . . . . . . . . . . . . . . . . . . . . . Information on parameters, counters, and alarms . . . . . . . . . . . . . . . . . RU20 RNC solution features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RU20 BTS solution features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information on Parameters, Counters, and Alarms . . . . . . . . . . . . . . . . Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activate and verify radio resource management and telecom features . Activating RAN876: Broadcast of A-GPS Assistance Data . . . . . . . . . . Activating Broadcast of A-GPS Assistance Data . . . . . . . . . . . . . . . . . . Verifying Broadcast of A-GPS Assistance Data. . . . . . . . . . . . . . . . . . . Deactivating Broadcast of A-GPS Assistance Data. . . . . . . . . . . . . . . . Activating RAN955: Power Saving Mode for BTS . . . . . . . . . . . . . . . . . Deactivating Power Saving Mode for BTS. . . . . . . . . . . . . . . . . . . . . . . Verifying Power Saving Mode for BTS. . . . . . . . . . . . . . . . . . . . . . . . . . Activating Power Saving Mode for BTS . . . . . . . . . . . . . . . . . . . . . . . . . RAN981: HSUPA 5.8 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating HSUPA 5.8 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying HSUPA 5.8 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivating HSUPA 5.8 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating RAN1201 and RAN1644: Fractional DPCH and Continuous Packet Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating RAN1201: Fractional DPCH . . . . . . . . . . . . . . . . . . . . . . . . . Activating Fractional DPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Fractional DPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deactivating Fractional DPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating RAN1644: Continuous packet connectivity . . . . . . . . . . . . . . Activating Continuous packet connectivity. . . . . . . . . . . . . . . . . . . . . . . Verifying Continuous packet connectivity . . . . . . . . . . . . . . . . . . . . . . . Deactivating Continuous packet connectivity. . . . . . . . . . . . . . . . . . . . . Activating RAN1202: 24 kbps Paging Channel . . . . . . . . . . . . . . . . . . . Activating 24 kbps paging channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying 24 kbps paging channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 10 10 13 14 14 15 16 17 18 18 19 20 21 22 24 25 25 25 27 28 29 29 30 31 35 35 37 38 39 39 39 44 46 47 47 50 51 52 52 54

DN0988674

Id:0900d8058095ac7a Confidential

Activating and Verifying RU20 Features

2.5.3 2.6 2.6.1 2.6.1.1 2.6.1.2 2.6.2 2.6.3 2.7 2.7.1 2.7.2 2.7.3 2.8 2.8.1 2.8.1.1 2.8.1.2 2.8.2 2.8.3 2.9 2.9.1 2.9.2 2.9.3 2.10 2.10.1 2.10.2 2.10.3 2.11 2.11.1 2.11.1.1 2.11.1.2 2.11.2 2.11.3 2.12 2.12.1 2.12.2 2.12.3 2.13 2.13.1 2.13.2 2.13.3 2.14 2.14.1 2.14.2 2.14.3 2.15 2.15.1 2.15.2 2.15.3

Deactivating 24 kbps paging channel . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 RAN1231: HSPA over Iur (On Top) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Activating HSPA over Iur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Activating HSPA over Iur for IPA-RNC solution . . . . . . . . . . . . . . . . . . . 57 Activating HSPA over Iur for I-HSPA Adapter solution . . . . . . . . . . . . . . 59 Verifying HSPA over Iur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Deactivating HSPA over Iur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 RAN1470: HSUPA 2ms TTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Activating HSUPA 2 ms TTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Verifying HSUPA 2 ms TTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Deactivating HSUPA 2 ms TTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 RAN1642: MIMO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Activating MIMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Activating MIMO for IPA-RNC and mcRNC solution. . . . . . . . . . . . . . . . 69 Activating MIMO for I-HSPA solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Verifying MIMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Deactivating MIMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 RAN1643: HSDPA 64QAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Activating HSDPA 64QAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Verifying HSDPA 64QAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Deactivating HSDPA 64QAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 RAN1686: HSPA 72 Users per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Activating HSPA 72 Users per Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Verifying HSPA 72 Users per Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Deactivating HSPA 72 Users per Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . 85 RAN1689: CS Voice over HSPA (On Top) . . . . . . . . . . . . . . . . . . . . . . . 86 Activating CS Voice over HSPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Activating CS Voice over HSPA for IPA-RNC and mcRNC solution. . . . 86 Activating CS Voice over HSPA for I-HSPA Adapter solution . . . . . . . . 88 Verifying CS Voice over HSPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Deactivating CS Voice over HSPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Activating RAN1758: Multiple BSIC Identification . . . . . . . . . . . . . . . . . . 92 Activating Multiple BSIC Identification . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Verifying Multiple BSIC Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Deactivating Multiple BSIC Identification . . . . . . . . . . . . . . . . . . . . . . . . 94 RAN1906: Dual-Cell HSDPA 42Mbps (On Top) . . . . . . . . . . . . . . . . . . . 95 Activating Dual-Cell HSDPA 42Mbps (On Top) . . . . . . . . . . . . . . . . . . . 95 Verifying Dual-Cell HSDPA 42Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Deactivating Dual-Cell HSDPA 42Mbps . . . . . . . . . . . . . . . . . . . . . . . . . 99 Activating RAN2067: LTE Interworking. . . . . . . . . . . . . . . . . . . . . . . . . 100 Activating LTE Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Verifying LTE Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Deactivating LTE Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Activating RAN2176: LTE PS Handover . . . . . . . . . . . . . . . . . . . . . . . . 103 Activating LTE PS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Verifying LTE PS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Deactivating LTE PS Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Id:0900d8058095ac7a Confidential

DN0988674

Activating and Verifying RU20 Features

2.16 2.16.1 2.16.2 2.16.3 3 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.2 3.2.1 3.2.2 3.2.3 3.3 3.3.1 3.3.2 3.3.3 3.4 3.4.1 3.4.2 3.4.3 3.4.4 3.5 3.5.1 3.5.2 3.5.3 3.6 3.6.1 3.6.2 3.6.3 4 4.1 4.1.1 4.1.2 4.1.3 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.4.1

Activating RAN2289 Blind IFHO in RAB Setup Phase . . . . . . . . . . . . Activating Blind IFHO in RAB Setup Phase . . . . . . . . . . . . . . . . . . . . . Verifying Blind IFHO in RAB Setup Phase. . . . . . . . . . . . . . . . . . . . . . Deactivating Blind IFHO in RAB Setup Phase. . . . . . . . . . . . . . . . . . .

106 106 110 111

Activate and verify transmission and transport features . . . . . . . . . . . 112 Activating RAN74, RAN1634, RAN1449, and RAN1633: IP Based Iub and Dual Iub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Activating IP based Iub for Flexi WCDMA BTS . . . . . . . . . . . . . . . . . . 112 Activating IP based Iub for UltraSite WCDMA BTS . . . . . . . . . . . . . . . 118 Verifying IP based Iub for Flexi and UltraSite WCDMA BTS . . . . . . . . 124 Deactivating IP based Iub for Flexi and UltraSite WCDMA BTS . . . . . 125 Activating Dual Iub for Flexi WCDMA BTS . . . . . . . . . . . . . . . . . . . . . 126 Verifying Dual Iub for Flexi WCDMA BTS . . . . . . . . . . . . . . . . . . . . . . 132 Deactivating Dual Iub for Flexi WCDMA BTS . . . . . . . . . . . . . . . . . . . 133 Activating RAN1578: HSPA Transport Fallback . . . . . . . . . . . . . . . . . 134 Activating HSPA Transport Fallback . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Verifying HSPA Transport Fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Deactivating HSPA Transport Fallback . . . . . . . . . . . . . . . . . . . . . . . . 139 Activating RAN1707: Flexi WCDMA Integrated CESoPSN . . . . . . . . . 140 Activating Flexi WCDMA Integrated CESoPSN. . . . . . . . . . . . . . . . . . 140 Verifying Flexi WCDMA Integrated CESoPSN . . . . . . . . . . . . . . . . . . 143 Deactivating Flexi WCDMA Integrated CESoPSN. . . . . . . . . . . . . . . . 144 Activating RAN1708: BTS Synchronous Ethernet . . . . . . . . . . . . . . . . 145 Activating BTS Synchronous Ethernet in Flexi WCDMA BTS . . . . . . . 145 Activating BTS Synchronous Ethernet in UltraSite WCDMA BTS . . . . 147 Verifying BTS Synchronous Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . 149 Deactivating BTS Synchronous Ethernet. . . . . . . . . . . . . . . . . . . . . . . 150 Activating RAN1709: VLAN Traffic Differentiation . . . . . . . . . . . . . . . . 151 Activating RAN1709: VLAN Traffic Differentiation . . . . . . . . . . . . . . . . 151 Verifying RAN1709: VLAN Traffic Differentiation. . . . . . . . . . . . . . . . . 163 Deactivating RAN1709: VLAN Traffic Differentiation . . . . . . . . . . . . . . 164 Activating RAN1749: BTS Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Activating BTS Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Verifying BTS Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Deactivating BTS Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Activate and verify operability and transport features . . . . . . . . . . . . . 168 Activating RAN1174: Secure AXC NWI3 Management Interface . . . . 168 Activating RAN1174: Secure AXC NWI3 Management Interface . . . . 168 Verifying RAN1174: Secure AXC NWI3 Management Interface . . . . . 170 Deactivating RAN1174: Secure AXC NWI3 Management Interface . . 171 Activating RAN1298 and RAN1299: BTS plug-and-play . . . . . . . . . . . 172 Activating RAN1298: BTS auto connection . . . . . . . . . . . . . . . . . . . . . 172 Verifying RAN1298: BTS auto connection . . . . . . . . . . . . . . . . . . . . . . 178 Deactivating RAN1298: BTS auto connection . . . . . . . . . . . . . . . . . . . 180 Activating BTS Auto connection and Auto configuration through the NetAct 181 About this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

DN0988674

Id:0900d8058095ac7a Confidential

Activating and Verifying RU20 Features

4.2.4.2 4.2.4.3 4.2.4.4 4.2.4.5 4.2.4.6 4.3 4.3.1 4.3.2 4.3.3 4.4 4.4.1 4.4.2 4.4.3 4.4.4 5 5.1 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.2.2 5.2.3 5.3 5.3.1 5.3.2 5.3.3

Preconditions and requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Enabling autotriggering of WBTS auto configuration (optional) . . . . . . 186 Configuring e-mail notification (optional). . . . . . . . . . . . . . . . . . . . . . . . 187 Auto Configuration Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Where to find more information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Feature RAN1453: Iu Link Break Protection, Feature Activation Manual . . 190 Activating RAN1453: Iu Link Break Protection . . . . . . . . . . . . . . . . . . . 190 Verifying RAN1453: Iu Link Break Protection . . . . . . . . . . . . . . . . . . . . 192 Deactivating RAN1453: Iu Link Break Protection . . . . . . . . . . . . . . . . . 193 Activating RAN1461: RNC RNW alarm reduction. . . . . . . . . . . . . . . . . 194 Activating RAN1461: RNC RNW alarm reduction. . . . . . . . . . . . . . . . . 194 Verifying RAN1461: RNC RNW alarm reduction . . . . . . . . . . . . . . . . . 196 Modifying RAN1461: RNC RNW alarm reduction functionality. . . . . . . 198 Deactivating RAN1461: RNC RNW alarm reduction . . . . . . . . . . . . . . 200 Activate and verify performance monitoring features . . . . . . . . . . . . . . 201 Activating RAN1311: Position Information in Subscriber Trace Report 201 Activating Position Information in Subscriber Trace Report . . . . . . . . . 201 Verifying Position Information in Subscriber Trace Report . . . . . . . . . . 203 Deactivating Position Information in Subscriber Trace Report . . . . . . . 204 Activating RAN1312: Channel Element Utilization in WBTS . . . . . . . . 205 Activating Channel Element Utilization in WBTS . . . . . . . . . . . . . . . . . 205 Verifying Channel Element Utilization in WBTS . . . . . . . . . . . . . . . . . . 206 Deactivating Channel Element Utilization in WBTS . . . . . . . . . . . . . . . 207 Activating RAN1509: RAB Bit Rate Counters . . . . . . . . . . . . . . . . . . . . 208 Activating RAB Bit Rate Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Verifying RAB Bit Rate Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Deactivating RAB Bit Rate Counters . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Id:0900d8058095ac7a Confidential

DN0988674

Activating and Verifying RU20 Features

List of figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Object locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Selecting the Edit parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Example of configuring FDPCHAndSRBOnHSPATC RNHSPA parameter with parameter editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Example of configuring AMRLCSRBHSPA RNRLC parameter with parameter editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Selecting the Edit parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Configuring the RNHSPA parameters for NRT traffic class with 10 ms TTI with parameter editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 IP-based Iub connectivity for Flexi WCDMA BTS . . . . . . . . . . . . . . . . 112 IP-based Iub connectivity for UltraSite WCDMA BTS . . . . . . . . . . . . . 118 Dual Iub connectivity for Flexi WCDMA BTS . . . . . . . . . . . . . . . . . . . . 127 Example of IP addressing scheme for VLAN Traffic Differentiation. . . 151 Example of IP addressing scheme for VLAN Traffic Differentiation for mcRNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 RNC, WBTS, CA/CR settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 The BTS object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Auto Connection HW ID and Site ID parameters. . . . . . . . . . . . . . . . . 179 Upload dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 BTS Auto Connection option under the RNC Options parameter . . . . 184 Software Manager view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

DN0988674

Id:0900d8058095ac7a Confidential

Activating and Verifying RU20 Features

List of tables
Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Radio resource management features . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Radio resource management and telecom features . . . . . . . . . . . . . . . 14 Transmission and transport features . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Operability features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Performance monitoring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 RNC solution features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 BTS solution features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Counters that values are incremented after activating the RAN1201: Fractional DPCH feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 The counter that value is incremented after activating the RAN1644: Continuous packet connectivity feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Allowed combinations for transport bearers on IP transport network . 126 Site router static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 VLANs for different traffic types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 WBTS static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 NPGE static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 licenses needed for BTS auto configuration. . . . . . . . . . . . . . . . . . . . . 182 licenses recommended for BTS auto configuration . . . . . . . . . . . . . . . 182

Id:0900d8058095ac7a Confidential

DN0988674

Activating and Verifying RU20 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 mcRNC2.0: Activating RAN2067: LTE interworking Activating RAN2176: LTE PS Handover

Changes between issues 01G (2012-05-25, RU30) and 01H (2012-08-24, RU30) The following feature activation instructions has been updated: Activating RAN1686: HSPA 72 Users Per Cell

Changes between issues 01F (2012-04-20, RU30) and 01G (2012-05-25, RU30) List of untested feature activation instructions has been updated. The following feature activation instructions has been updated: Activating RAN2289: Blind IFHO in RAB Setup Phase Activating RAN1231: HSPA over Iur Activating RAN2067: LTE interworking Activating RAN2176: LTE PS Handover

Changes between issues 01E (2012-02-23, RU30) and 01F (2012-04-20, RU30) List of untested feature activation instructions has been updated. The following feature activation instructions has been updated: Activating RAN1758: Multiple BSIC Identification Activating RAN1298 and RAN1299: BTS plug-and-play

Changes between issues 01B (2011-07-26, RU30) and 01C (2011-09-23, RU30) The following feature activation instructions have been updated: Activating RAN1311: Position Information in Subscriber Trace Report

DN0988674

Id:0900d8058095ac8c Confidential

Introduction

Activating and Verifying RU20 Features

1 Introduction
1.1
1.1.1

Introduction to RU20 Feature Activation Instructions


RU20 radio resource management features
See the following table for more detailed information on WCDMA RAN functionality and feature activation:

Feature ID: Name RAN1643: HSDPA 64QAM

Functional Area Description and other related documents WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN HSDPA in BTS

Feature implementation Activating RAN1643: HSDPA 64QAM

RAN1470: HSUPA 2ms TTI

WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM HSUPA

Activating RAN1470: HSUPA 2ms TTI

RAN1201: Fractional DPCH

WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM HSUPA WCDMA RAN RRM Admission Control RNC Call Setup and Release WCDMA RAN HSDPA in BTS WCDMA RAN HSUPA in BTS

Activating RAN1201 and RAN1644: Fractional DPCH and Continuous packet connectivity

RAN1644: Continuous Packet Con- WCDMA RAN Radio Resource nectivity Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM HSUPA Packet Data Transfer States WCDMA RAN HSUPA in BTS Table 1 Radio resource management features

Activating RAN1201 and RAN1644: Fractional DPCH and Continuous packet connectivity

10

Id:0900d8058092ab86 Confidential

DN0988674

Activating and Verifying RU20 Features

Introduction

Feature ID: Name RAN1638: Flexible RLC (DL)

Functional Area Description and other related documents WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM HSUPA WCDMA RAN RRM Admission Control WCDMA RAN HSDPA in BTS

Feature implementation Activating RAN1643: HSDPA 64QAM

RAN955: Power Saving Mode for BTS

WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM Admission Control WCDMA RAN RRM Handover Control

Activating RAN955: Power Saving Mode for BTS

RAN1686: HSPA 72 Users Per Cell WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN HSDPA in BTS WCDMA RAN HSUPA in BTS RAN1642: MIMO RAN1758: Multiple BSIC Identification (On Top) WCDMA RAN Radio Resource Management Overview WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM Handover Control RAN2067: LTE interworking (On Top) WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM Handover Control WCDMA RAN RRM Admission Control RAN2176: LTE PS Handover (On Top) WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM Handover Control WCDMA RAN RRM Admission Control WCDMA RAN RRM HSDPA Table 1 Radio resource management features (Cont.)

Activating RAN1686: HSPA 72 Users Per Cell

Activating RAN1642: MIMO Activating RAN1758: Multiple BSIC Identification

Activating RAN2067: LTE interworking

Activating RAN2176: LTE PS Handover

DN0988674

Id:0900d8058092ab86 Confidential

11

Introduction

Activating and Verifying RU20 Features

Feature ID: Name RAN2289: Blind IFHO in RAB Setup Phase (On Top)

Functional Area Description and other related documents WCDMA RAN RRM Handover Control WCDMA RAN RRM Admission Control

Feature implementation RAN2289: Blind IFHO in RAB Setup Phase

RAN1689: CS Voice Over HSPA (On Top)

WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM HSUPA WCDMA RAN RRM Admission Control WCDMA RAN RRM Handover Control WCDMA RAN RRM Packet Scheduler RNC Call Setup and Release Power Control in WCDMA RAN WCDMA RAN HSDPA in BTS WCDMA RAN HSUPA in BTS

Activating RAN1689: CS Voice Over HSPA (On Top)

RAN1906: Dual-Cell HSDPA 42 Mbps (On Top)

WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM Handover Control RNC Call Setup and Release

Activating RAN1906: Dual-Cell HSDPA 42 Mbps (On Top)

RAN1231: HSPA over Iur (On Top)

WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM HSUPA WCDMA RAN SRNS Relocation WCDMA RAN RRM Handover Control WCDMA RAN RRM Admission Control

Activating RAN1231: HSPA over Iur (On Top)

RAN1762: Direct Resource Allocation for HSPA (On Top)

WCDMA RAN Radio Resource Management Overview WCDMA RAN RRM HSDPA WCDMA RAN RRM HSUPA

This feature does not require activation.

Table 1

Radio resource management features (Cont.)

12

Id:0900d8058092ab86 Confidential

DN0988674

Activating and Verifying RU20 Features

Introduction

Feature ID: Name

Functional Area Description and other related documents

Feature implementation

RAN2136: Fast Dormancy (On Top) WCDMA RAN Packet Data Transfer This feature does not require activaStates tion. Table 1 Radio resource management features (Cont.)

1.1.1.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 RNC Counters - RNW Part RNC Counters Transport and HW Part WBTS Counters AXC Counters I-HSPA Adapter Measurements and Counters Reference Information Service in NOLS 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)

For counter descriptions, see:

For alarm descriptions, see:

DN0988674

Id:0900d8058092ab86 Confidential

13

Introduction

Activating and Verifying RU20 Features

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

RU20 telecom features


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

Feature ID: Name

Functional Area Description and other related documents

Feature implementation Activating RAN1202: 24 kbps Paging Channel Activating RAN981: HSUPA 5.8 Mbps This feature does not require activation. Activating RAN876: Broadcast of AGPS Assistance Data

RAN1202: 24 kbps Paging Channel WCDMA RAN RRM Admission Control RNC Call Setup and Release RAN981: HSUPA 5.8 Mbps RAN1322: Fast L1 Syncronisation RAN876: Broadcast of A-GPS Assistance Data Table 2 WCDMA RAN RRM HSUPA WCDMA RAN HSUPA in BTS WCDMA RAN RRM Admission Control WCDMA RAN Location Services

Radio resource management and telecom features

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 WCDMA BTS Parameters UltraSite WCDMA BTS Parameters Reference Information Service in NOLS for RNC parameters

14

Id:0900d8058092ab86 Confidential

DN0988674

Activating and Verifying RU20 Features

Introduction

For counter descriptions, see: RNC counters - RNW part RNC counters transport and HW part WBTS counters AXC counters Reference Information Service in NOLS 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 alarm descriptions, see:

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

RU20 transmission and transport features


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

Feature RAN1578: HSPA Transport Fallback RAN1708: BTS Synchronous Ethernet RAN1706: Transport sub-module FTFB for Flexi WCDMA BTS RAN1819: Transport sub-module FTLB for Flexi Multimode BTS RAN1701: AXCF Unit for UltraSite WCDMA BTS RAN1633: Dual Iub for UltraSite WCDMA BTS RAN1749: BTS Firewall

Other related descriptions WCDMA RAN and I-HSPA Network Protection WCDMA RAN and I-HSPA Synchronization Flexi Multiradio BTS WCDMA Transmission Description Flexi Multiradio BTS WCDMA Transmission Description UltraSite WCDMA BTS Product Description AXC Product Description AXC Product Description WCDMA RAN and I-HSPA IP Transport WCDMA RAN and I-HSPA Transport Security

Related instructions Activating RAN1578: HSPA Transport Fallback Activating RAN1708: BTS Synchronous Ethernet This feature does not require activation This feature does not require activation Activating and operating the feature in RAN1701: AXCF Unit for the UltraSite WCDMA BTS Activating RAN74, RAN1634, RAN1449, and RAN1633: IP based Iub and Dual Iub Activating RAN1749: BTS Firewall

Table 3

Transmission and transport features

DN0988674

Id:0900d8058092ab86 Confidential

15

Introduction

Activating and Verifying RU20 Features

Feature RAN2381: Juniper EX4200 as RNC Site Router RAN1883: FlexiPacket Radio Connectivity (On Top) RAN1707: Flexi WCDMA Integrated CESoPSN (On Top)

Other related descriptions

Related instructions

This feature does not have any related docu- Configuring RNC IP Site Solution ments. Based on Juniper EX4200 Routers This feature does not have any related docu- This feature does not require activaments. tion This feature does not have any related docu- Activating RAN1707: Flexi WCDMA ments. Integrated CESoPSN Activating RAN1709: VLAN Traffic Differentiation

RAN1709: VLAN Traffic Differentia- WCDMA RAN and I-HSPA IP Transport tion (On Top) RAN2427: Juniper Mx-series as RNC Site Router (On Top)

This feature does not have any related docu- Configuring RNC IP site solution ments. based on Juniper MX series routers

Table 3

Transmission and transport features (Cont.)

1.1.3.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 RNC Counters - RNW Part RNC Counters Transport and HW Part WBTS Counters AXC Counters I-HSPA Adapter Measurements and Counters Reference Information Service in NOLS Multicontroller RNC Notices (0-999) Multicontroller RNC Disturbances (1000-1999) Multicontroller RNC Failure Printouts (2000-3999) Multicontroller RNC Alarms (70000-72000)

For counter descriptions, see:

For alarm descriptions, see:

16

Id:0900d8058092ab86 Confidential

DN0988674

Activating and Verifying RU20 Features

Introduction

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

RU20 operability features


See the following table for more detailed information on WCDMA RAN functionality and feature activation:
Feature ID: Name RAN1461: RNC RNW Alarm Reduction RAN1298: BTS Auto Connection RAN1299: BTS Auto Configuration RAN885: Remote BTS SCF Management for Flexi/Ultra/MetroSite BTSs RAN1646: Parallel RNW Direct activations and plan operation RAN1653: Remote RNC SW management Functional Area Description Feature implementation WCDMA RAN and I-HSPA Fault Management This feature does not have any related documents. This feature does not have any related documents. WCDMA RAN and I-HSPA Configuration Management WCDMA RAN and I-HSPA Configuration Management WCDMA RAN and I-HSPA Software Management Activating RAN1461: RNC RNW alarm reduction Activating RAN1298 and 1299: BTS plug-and-play Activating RAN1298 and 1299: BTS plug-and-play This feature does not require activation. This feature does not require activation. This feature does not require activation.

RAN1849: BTS Licensing WCDMA RAN License Opera- This feature does not require Logical Target ID for Flexi BTS tion activation. RAN1851: BTS Licensing Configuration and Alarm enhancements WCDMA RAN License Opera- This feature does not require tion activation.

Table 4

Operability features

DN0988674

Id:0900d8058092ab86 Confidential

17

Introduction

Activating and Verifying RU20 Features

Feature ID: Name RAN1209: Secure BTS Element Manager Interface RAN1174: Secure AXC NWI3 Management Interface RAN1313: Support for Longer User Name and RUIM Activation in RNC RAN1717: Network Element Certificate Management for Ultrasite RAN1750: NetAct integrated RET management (On Top)

Functional Area Description Feature implementation WCDMA RAN and I-HSPA O&M Security WCDMA RAN and I-HSPA O&M Security WCDMA RAN and I-HSPA O&M Security WCDMA RAN and I-HSPA O&M Security WCDMA RAN and I-HSPAConfiguration Management This feature does not require activation. Activating RAN1174: Secure AXC NWI3 Management Interface This feature does not require activation. This feature does not require activation. This feature does not require activation.

Table 4

Operability features (Cont.)

1.1.5

RU20 performance monitoring features


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

Feature ID: Name RAN1136: Separate Counters for Relocations RAN1509: RAB Bit Rate Counters RAN1713: Ethernet QoS Monitoring in BTS RAN1312: Channel Element Utilization in WBTS RAN1311: Position Information in Subscriber Trace Report Table 5

Functional Area Descriptions and other related documents Measuring WCDMA RAN RNC counters - RNW part RNC counters - RNW part WBTS Counters Measuring WCDMA RAN WBTS Counters WCDMA RAN subscriber and equipment trace

Feature implementation This feature does not require activation. Activating RAN1509: RAB Bit Rate Counters. This feature does not require activation. Activating RAN1312: Channel Element Utilization in WBTS. Activating RAN1311: Position Information in Subscriber Trace Report

Performance monitoring features

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

18

Id:0900d8058092ab86 Confidential

DN0988674

Activating and Verifying RU20 Features

Introduction

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 RNC counters - RNW part RNC counters transport and HW part WBTS counters AXC counters Reference Information Service in NOLS 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 counter descriptions, see:

For alarm descriptions, see:

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

RU20 RNC solution features


See the following table for more detailed information on WCDMA RAN functionality and descriptive documents:

Feature ID: Name RAN1783: Standalone OMS for RNC

Descriptions Standalone RNC OMS Product Description

Instructions Installing and Commissioning OMS Upgrading from Integrated RNC 5.0 OMS to Standalone RNC 6.0 OMS This feature does not require activation. HW upgrade instructions This feature does not require activation. This feature does not require activation.

RAN1795: RNC2600 coverage opti- RNC2600 Product Description mized solution RAN1766: Gigabit level RNC196 step8 upgrade RAN1782: OMS disk capacity increase RNC196 Product Description This feature does not have any related documents

RAN1793: SW Enhanced RNC2600 RNC2600 Product Description

Table 6

RNC solution features

DN0988674

Id:0900d8058092ab86 Confidential

19

Introduction

Activating and Verifying RU20 Features

1.1.6.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 RNC Counters - RNW Part RNC Counters Transport and HW Part WBTS Counters AXC Counters I-HSPA Adapter Measurements and Counters Reference Information Service in NOLS 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)

For counter descriptions, see:

For alarm descriptions, see:

20

Id:0900d8058092ab86 Confidential

DN0988674

Activating and Verifying RU20 Features

Introduction

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

RU20 BTS solution features


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

Feature ID: Name RAN1671: Enhanced UltraSite Base Band (EUBB)

Descriptions UltraSite EUBB WCDMA BTS product description Wideband Signal Processing (WSPF) unit description Wideband Summing and Multiplexing (WSMF) unit description AXC product description

Instructions This feature does not require activation

RAN1079: Multiradio Combiner 850MHz

For more information see: Nokia Siemens Networks Antenna Systems, Operating Documentation available in NOLS Flexi Multiradio BTS WCDMA RF Module and Remote Radio Head Description

Multi Radio Combiner is activated through BTS Site EM check box during commssioning. As a reference see: Activating RAN1216: Flexi RF Module Triple 70W 2100. Commissioning Flexi Multiradio BTS WCDMA

RAN1870: Flexi 3-sector RF Module 1500

RAN1876: Smart Diplexer

For more information see: Nokia Siemens Networks Antenna Systems, Operating Documentation available in NOLS

FAWA and FDWA has to be it self configured without any particular BTS SW activity. Startup immediately when FAWA DC (-48V) is on. FAWA and FDWA units are transparent for BTS during startup and after this process. Commissioning Flexi Multiradio BTS WCDMA Commissioning Flexi Multiradio BTS WCDMA Commissioning Flexi Multiradio BTS WCDMA

RAN1575: Flexi 3-sector RF Module 1900 (On Top) RAN1768: Flexi 3-sector RF Module 900 (On Top) RAN2062: Flexi 3-sector RF Module 2100 (On Top)

Flexi Multiradio BTS WCDMA RF Module and Remote Radio Head Description Flexi Multiradio BTS WCDMA RF Module and Remote Radio Head Description Flexi Multiradio BTS WCDMA RF Module and Remote Radio Head Description

Table 7

BTS solution features

DN0988674

Id:0900d8058092ab86 Confidential

21

Introduction

Activating and Verifying RU20 Features

Feature ID: Name RAN2046: Flexi 3-sector RF Module 850 (On Top) RAN1871: Flexi 3-sector RF Module 1.7/2.1 (On Top)

Descriptions

Instructions

This feature does not have related doc- Commissioning Flexi Multiradio uments BTS WCDMA Flexi Multiradio BTS WCDMA RF Module and Remote Radio Head Description Flexi Multiradio BTS WCDMA RF Module and Remote Radio Head description This feature does not require activation Commissioning Flexi Multiradio BTS WCDMA This feature does not require activation This feature does not require activation Installing Flexi Multiradtio BTS WCDMA Optional Items

RAN2112: Flexi RRH 2TX 2100

RAN2382: Flexi BTS Multimode Flexi Multiradio BTS WCDMA System SystemModule - FSMC (On Top) Module Description RAN1757: 24 External Alarm interfaces for Flexi WCDMA BTS (On Top) RAN2514: Rx Diversity Sharing RAN1806: Enable LTE SW download on top of WBTS6.0 RAN2615: Flexi 3-sector RF Module 900J (On Top) FSEB description can be found in Flexi Multiradio BTS WCDMA Optional Items Description

This feature does not have related doc- Commissioning Flexi Multiradio uments BTS WCDMA This feature does not have related doc- LTE SW has to be activated after uments downloading. Flexi Multiradio BTS WCDMA RF Module and Remote Radio Head Description Commissioning Flexi Multiradio BTS WCDMA

Table 7

BTS solution features (Cont.)

1.1.7.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 RNC counters - RNW part RNC counters transport and HW part WBTS counters AXC counters Reference Information Service in NOLS

For counter descriptions, see:

For alarm descriptions, see:

22

Id:0900d8058092ab86 Confidential

DN0988674

Activating and Verifying RU20 Features

Introduction

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.

DN0988674

Id:0900d8058092ab86 Confidential

23

Activating and Verifying RU20 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.

24

Id:0900d805808fb9f5 Confidential

DN0988674

Activating and Verifying RU20 Features

Activate and verify radio resource management and telecom features

2 Activate and verify radio resource management and telecom features


2.1
2.1.1

Activating RAN876: Broadcast of A-GPS Assistance Data


Activating Broadcast of A-GPS Assistance Data
Purpose Follow the procedure below to activate the RAN876: Broadcast of A-GPS Assistance Data feature. For more information on the feature, see the RAN876: Broadcast of A-GPS Assistance Data Feature Description in WCDMA RAN, Rel. RU20, Feature Descriptions. Before you start This feature is controlled by a license. For information on managing licenses, see Licensing. The RAN876 feature code is 1100. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=1100:ON for mcRNC: fsclish -c set license feature-mgmt id 0000001100 feature-admin-state on Check that WSMLC and WLCSE objects do exists in those WBTSs WCELLs where Broadcast of A-GPS Assistance Data will be activated (if not then they must be created and configured). Check that the IP-based signalling configuration and SCCP configuration are done as described in Activating RAN223, RAN875 and RAN1920: A-GPS Using External Reference Network and Iu-PC SCTP Association Priority. Steps

1 2 3 4

Open the OMS Element Manager and launch the Parameter Editor application. Set the LCSFunctionality parameter in RNC object to Enabled. Set the LCS interface option parameter in WSMLC object to value iupc. Set the BroadcastSIB15 parameter to value Enabled for every WBTS object where the broadcast of A-GPS Assistance Data is to be enabled. If also SIB15.2 needs to be broadcasted, set the BroadcastSIB15.2 parameter to value Enabled for every WBTS object where the broadcast of A-GPS Assistance Data is to be enabled.

DN0988674

Id:0900d8058095ac78 Confidential

25

Activate and verify radio resource management and telecom features

Activating and Verifying RU20 Features

If also SIB15.3 needs to be broadcasted, set the BroadcastSIB15.3 parameter to value Enabled for every WBTS object where the broadcast of A-GPS Assistance Data is to be enabled. Expected outcome RAN876: Broadcast of A-GPS Assistance Data feature is activated in the RNC.

26

Id:0900d8058095ac78 Confidential

DN0988674

Activating and Verifying RU20 Features

2.1.2

Verifying Broadcast of A-GPS Assistance Data


Purpose Follow the procedure below to verify that the activation of the RAN876: Broadcast of AGPS Assistance Data feature has been successful. Steps

Start the M1021 Iupc Interface measurement using the RNW Measurement Management application in RNC Element Manager. After the measurement data is collected, use the RNW Measurement Presentation GUI to check that the M1021C25 ASSISTANCE DATA REQUESTS FOR BROADCAST TO SAS counter has a value greater than 0.

DN0988674

Id:0900d8058081c8e8 Confidential

27

Activating and Verifying RU20 Features

2.1.3

Deactivating Broadcast of A-GPS Assistance Data


Purpose Follow the procedure below to deactivate the feature. Steps

1 2

Open the OMS Element Manager and launch the Parameter Editor application. Set the BroadcastSIB15, BroadcastSIB15.2 and BroadcastSIB15.3 parameters to value Disabled for every WBTS object where the broadcast of A-GPS Assistance Data will be deactivated. Further information After deactivating the feature, set the feature license state to OFF. Expected outcome The RAN876: Broadcast of A-GPS Assistance Data feature is deactivated.

28

Id:0900d8058090bded Confidential

DN0988674

Activating and Verifying RU20 Features

2.2
2.2.1

Activating RAN955: Power Saving Mode for BTS


Deactivating Power Saving Mode for BTS
Purpose Follow the procedure below to deactivate the feature. Steps

1 2

Open the RNC RNW Object Browser GUI in RNC Element Manager. Configure BTS object. Set the PWSMinUse parameter to OFF.

When deactivating Power Saving Mode, PowerSaveHSPAType parameter needs to be changed to "No HSPA05_Reconfig" value, otherwise HSPA operational state cannot be enabled. The cells that were shutdown, are to be activated. Further information After deactivating the feature there is no need to restart RNC or BTS. After deactivating the feature set the feature license state to OFF. Expected outcome The RAN955: Power Saving Mode for BTS feature is deactivated.

DN0988674

Id:0900d8058090d756 Confidential

29

Activating and Verifying RU20 Features

2.2.2

Verifying Power Saving Mode for BTS


Purpose Follow the procedure below to verify that the activation of the RAN955: Power Saving Mode for BTS feature has been successful. Steps

1 2

In the RNC object, under the general tab, set timer to trigger PWSM more quickly. In the WCEL-1 object, under the general tab, set the PWSM cell group of a cell as 1, the shutdown order of cells in one PWSM cell group as 0, and HSPA Type of Cell in Power Saving Mode as HSPA0. In the WCEL-2 object, under the general tab, set the PWSM cell group of a cell as 1, the shutdown order of cells in one PWSM cell group as 1, and HSPA Type of Cell in Power Saving Mode as HSPA5. In the WBTS object, enable PWSM by setting the PWSM usage in BTS as ON, and modify the shutdown time period. If no call exists in WCEL-2, shutdown because of Power Saving Mode for BTS will be performed. The cell state will be changed to BL(P).

30

Id:0900d8058090d74c Confidential

DN0988674

Activating and Verifying RU20 Features

2.2.3

Activating Power Saving Mode for BTS


Purpose Follow the procedure below to activate the RAN955: Power Saving Mode for BTS feature. For more information on the feature, see the RAN955: Power Saving Mode Feature Description in WCDMA RAN, Rel. RU20, Feature Descriptions. Before you start This feature belongs to application software. Ensure that you have a valid license (a file including the information), because this feature is under license key management. For information on managing licenses, see Licensing. The feature code for this feature is 1459. Before a license feature can be activated, the license must be transferred to and installed in the RNC. The license can be installed by using NetAct or a local MML interface. If the installation is done with NetAct, the feature covered by the license is automatically set to the ON state. If the installation is done with an MML interface, the feature state (ON/CONFIG/OFF) must be set by the user. In new installations, the default state is OFF. Installing of new increment does the change the previously set state it remains the default. The parameters for this feature can be configured with the RNC RNW Object Browser GUI. The Power Saving Mode feature can be activated on BTS only if the BTS is either Flexi BTS or Ultra BTS with software release WBTS6.0 onwards. Ensure that the O&M DCN link status is set to Enabled(check in RNC RNW Object Browser in WCDMA BTS object). Preconditions: To activate HSPA05 reconfiguration the following criteria must be fulfilled: The BTS has cells on exactly two frequencies All cells in the BTS belong to the same Power Saving Mode cell group. The value of the PWSMCellGroup parameter is different from zero All cells of the BTS belong to the same Local Cell Group Every non-remaining cell in one frequency has PWSMShutdownOrder parameter value set to 1 and the PowerSaveHSPAType parameter in all these cells is set to HSPA5 Every remaining cell in one frequency have all PWSMShutdownOrder parameter value set to 0 and the PowerSaveHSPAType parameter in all these cells is set to HSPA0 The HSDPA is enabled in all cells in the BTS (HSDPAenabled parameter has value set to Enabled in all cells in the BTS) The remaining cells are not allowed to be shutdown (PWSMShutdownRemCell parameter value in all remaining cells is set to No). DCN is working and WBTS type is FlexiBTS. Licence is installed in RNC.

If one or more criterias are not fulfilled, then HSPA05 reconfiguration is not needed, the cell shutdown decision is based on other cell shutdown criteria. If a need for HSPA05

DN0988674

Id:0900d8058090d74b Confidential

31

Activating and Verifying RU20 Features

reconfiguration is detected, the HSPA0 cells are to be reconfigurated to HSPA5 cells, and the HSPA5 cells are to be reconfigurated to HSPA0 cells before shutdown. Instructions to network operator Power Saving Mode instructions: The usage of gradual power ramp-down in Cell Deletion procedure is recommended. During gradual common pilot channel (CPICH) power ramp-down, the UE initiates a soft handover branch removal. Also, during or after gradual CPICH power ramp-down the RNC detects a need for handover (inter-frequency or inter-system handover) and starts the procedure. The gradual power ramp-down is the basis of the UE management in Cell Deletion procedure, and therefore it is recommended. After CPICH power decrease, RNC performs forced inter-frequency handover for the remaining UEs. When the gradual CPICH power ramp-down is used, the success rate of branch removals and interfrequency/inter-system handovers is increased (the number of lost calls during cell shutdown is smaller because of the RNC capability to handle simultaneous inter-frequency/inter-system handovers). Also, the number of remaining UEs in a cell is lower. The following features are recommended to be in use in the RNC, as they help balancing the traffic between cells after shutdown and after activation: Service and Load Based Handover Direct RRC Connection Setup HSPA Capability Based Handover. The multi-operator RAN (MORAN) needs to be taken into consideration according to the definitions of the feature management parameters, the MORAN network operators have to define the PWSMCellGroup and PWSMShutdownOrder parameters correctly. The RNC does not verify the MORAN definitions in Power Saving Mode. If the operator's actions lead to the situation when Power Saving Mode environment is not according to Power Saving Mode concept, the network can turn off the Power Saving Mode feature in BTS by the PWSMInUse parameter. For example if both a non-remaining cell and a remaining cell in Power Saving Mode two-cell group are shut down and the operator deletes the remaining cell from RNC, the non-remaining cell cannot be activated for traffic by means of Power Saving Mode. The HSPA05 reconfiguration (resource swapping in BTS) can be made only between cells belonging to the same Local Cell Group (LCG). Therefore, the network operator has to take the LCG - cell mapping into consideration when setting the PWSMCellGroup and PowerSaveHSPAType parameters. The cells controlled by the shared MAC high speed entity are selected with the RNC Tcell parameter (Frame timing offset of a cell). BTS maps the cells that belong to the same Tcell group to the same MAC high speed entity. This rule applies only for shared schedulers. The cell and Tcell mapping have to be defined correctly by network operator ,so that the MAC high speed entity in HSPA0 - HSPA5 reconfiguration is made correctly (the HSPA5 and HSPA0 cells using same scheduler are defined to the same Tcell group). The network operator should take also into consideration the BTS HW units (that is Rel1 and Rel2 system modules) in HSPA. In Flexi BTS the Rel2 system module supports HSPA+ functionalities and Rel1 system module does not. If the HSPA05

HSPA05 reconfiguration instructions:

32

Id:0900d8058090d74b Confidential

DN0988674

Activating and Verifying RU20 Features

reconfiguration is made between different system module releases, some of the HSPA functionalities might not be available. For working HSPA0 and HSPA5 configuration and reconfiguration, all cells need to be assigned to the same Power Saving Mode cell group. The parameter HSDPAenabled has to be set to value Enabled in both HSPA5 and HSPA0 cells if HSPA05 reconfiguration is to be used. In cell setup the HSDPA is not to be configured to a cell with PowerSaveHSPAType parameter value set to HSPA0, even if the HSDPAenabled parameter is set to value Enabled. The activation status of Power Saving Mode for BTS feature is not relevant. When HSUPA services are to be used, the HSUPAenabled parameter has to be set to value Enabled in both HSPA5 and HSPA0 cells if HSPA05 reconfiguration is to be used

Steps 1 Check the RNC time setting. For RNC use the MML command: ZDCD For mcRNC/ADA use the sCLI command: show networking-service ntp 2 3 Open the RNC RNW Object Browser GUI. Configure WBTS object. Set the non-remaining cell shutdown start time by configuring the PWSMShutdownBeginHour and the PWSMShutdownBeginMin parameters. Set the non-remaining cell shutdown end time by configuring the PWSMShutdownEndHour and the PWSMShutdownEndMin parameters and ensure that current RNC time is within this shutdown duration. Set the remaining cell shutdown start time by configuring the PWSMRemCellSDBeginHour and the PWSMRemCellSDBeginMin parameters. Set the remaining cell shutdown end time by configuring the PWSMRemCellSDEndHour and the PWSMRemCellSDEndMin parameters. Set the remaining cell shutdown day by configuring the PWSMWeekday parameter. 4 Configure WCEL object. To meet the HSPA5 criteria, the BTS has cells on exactly two frequencies. To meet the shutdown criteria, two different cells with different frequencies cannot be assigned to the same shutdown order. Please note, that before configuring the PowerSaveHSPAType parameter, the related WCEL object needs be locked. Set two cells with the same frequency as remaining cells, by configuring the PWSMShutdownOrder parameter to value "0", and set the PowerSaveHSPAType parameter to value "HSPA0".

g g

DN0988674

Id:0900d8058090d74b Confidential

33

Activating and Verifying RU20 Features

Set the third cell as a non-remaining cell, by configuring the PWSMShutdownOrder parameter to value "1", and set the PowerSaveHSPAType parameter to value "HSPA5". Configure the PWSMShutdownReCell parameter to value No to avoid the remaining cell shutdown. 5 Configure BTS object. Set the PWSMinUse parameter to value ON. 6 Cell shutdown When cell does not have any emergency calls or Wireless Priority Service calls, and if the cell 3 traffic is low and it fullfils the shutdown criteria, then after five minutes cell 3 shutdown is to be performed. HSPA05 reconfiguration is triggered, cell 3 reconfiguration to HSPA0 and cells 1 and 2 reconfiguration to HSPA5 is performed. Expected outcome RAN955: Power Saving Mode for BTS feature is activated in the RNC. Further information After activating the feature there is no need to restart RNC or BTS.

34

Id:0900d8058090d74b Confidential

DN0988674

Activating and Verifying RU20 Features

2.3
2.3.1

RAN981: HSUPA 5.8 Mbps


Activating HSUPA 5.8 Mbps
Purpose Follow the procedure below to activate the RAN981: HSUPA 5.8 Mbps feature. For more information on the feature, see the RAN981: HSUPA 5.8 Mbps feature description in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. For more information on licensing, see Licensing. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=1086:ON; for mcRNC: set license feature-mgmt id 0000001086 feature-admin-state on BTS: Flexi Rel. 2 RAN 1671: Enhanced ultrasite baseband (EUBB) (this feature only applies to the Ultrasite WBTS) RNC: For the RNC196 and RNC450, a hardware upgrade is required according to feature RAN1226: HSPA peak rate upgrade in RNC196 and RNC450 . This means that the support of HSUPA 2 ms TTI is possible only with the new hardware CDSP-DH (DMCU) configured as feature upgrade.

Hardware requirements:

The parameters can be configured with the RNC RNW object browser GUI. Note that the RAN981: HSUPA 5.8 Mbps feature can be activated only if the RAN1470: HSUPA 2 ms TTI feature is enabled in a cell. To activate the RAN1470: HSUPA 2 ms TTI, see Activating RAN1470: HSPA 2ms TTI feature activation manual.

Note that with the current default value of the WCEL PrxMaxTargetBTS parameter, the maximum UL bit rate may not be reached. Therefore, it is advised to increase the value of the PrxMaxTargetBTS parameter. Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

Lock the cell.

DN0988674

Id:0900d8058090e523 Confidential

35

Activating and Verifying RU20 Features

In the WCEL object under the Admission Control tab, enable HSDPAenabled (HSDPA enabled) parameter and under the Packet Scheduler tab, HSUPAenabled (HSUPA enabled) parameter. Under the Identification tab, define the WBTS object type using the NBAPCommMode (NBAP Communication Mode) parameter. In the WCEL object under the Admission Control tab, enable the HSUPA2MSTTIEnabled (HSUPA 2 ms TTI enabled) parameter. Under the Packet Scheduler tab, set the WCEL MaxTotalUplinkSymbolRate (Maximum total uplink symbol rate) parameter to maximum 5760 kbps (2*SF2+2*SF4). Unlock the WCEL object. Expected outcome RAN981: HSUPA 5.8 Mbps feature has been activated.

36

Id:0900d8058090e523 Confidential

DN0988674

Activating and Verifying RU20 Features

2.3.2

Verifying HSUPA 5.8 Mbps


Purpose Follow the procedure below to verify that the activation of the RAN981: HSUPA 5.8 Mbps feature has been successful. Steps

Start measurement M1002 Traffic with 15 minutes interval. Use RNW measurement application in the Application Launcher to start this measurement. Alternatively the measurement can be started using NetAct administration of measurement application.

2 3

Wait until the measurement interval starts. Start the HSUPA 5.8 Mbps call. Setup a PS NRT call with HSUPA 5.8 Mbps capable UE.

After the measurement data has been collected, use the RNW measurement presentation GUI to check that some of the following counter has a value greater than zero: M1002C664 E-DCH ALLO FOR SRB IN SRNC.

Further information After activating the feature, the PS NRT call is made from the cell. After that HSPA is allocated to UE.

DN0988674

Id:0900d80580812f45 Confidential

37

Activating and Verifying RU20 Features

2.3.3

Deactivating HSUPA 5.8 Mbps


Purpose Follow the procedure below to deactivate the feature. Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

3 4

Lock the WCEL object. Set the WCEL MaxTotalUplinkSymbolRate (Maximum total uplink symbol rate) parameter value to a value lower than 5760 kbps. Unlock the WCEL object. Further information After deactivating the feature, set the feature license state to OFF using: for IPA-RNC: ZW7M:FEA=1086:OFF; for mcRNC: set license feature-mgmt id 0000001086 feature-admin-state off

Expected outcome The RAN981: HSUPA 5.8 Mbps feature has been deactivated.

38

Id:0900d8058090e52d Confidential

DN0988674

Activating and Verifying RU20 Features

2.4

Activating RAN1201 and RAN1644: Fractional DPCH and Continuous Packet Connectivity
Activating RAN1201: Fractional DPCH Activating Fractional DPCH
Purpose Follow the procedure below to activate the RAN1201: Fractional DPCH (F-DPCH) feature. For more information on the feature, see RAN1201: Fractional DPCH feature description in WCDMA RAN, Rel. RU20, Feature Descriptions. Before you start Restart of the RNC and the BTS is not required after activation of this feature. This feature is controlled by a license. For information on managing licenses, see Licensing.

2.4.1 2.4.1.1

The feature code for this feature is 1476. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M:FEA=1476:ON; for mcRNC: set license feature-mgmt id 0000001476 feature-admin-state on

The following requirements must be fulfilled before the procedure is carried out by the user: Feature license CPC & F-DPCH is active. F-DPCH feature is enabled in all active set cells with WCEL parameter FDPCHEnabled . The BTS indicates for all active set cells that it supports Rel-6 F-DPCH using NBAP: F-DPCH CAPABILITY information element. This is not applicable for radio links over Iur. The BTS indicates for all active set cells that it supports Rel-7 F-DPCH using NBAP: F-DPCH SLOT FORMAT CAPABILITY information element. This is not applicable for radio links over Iur. The HSDPA is enabled in all active set cells with RNP parameter HSDPAEnabled. The HSUPA is enabled in all active set cells with RNP parameter HSUPAEnabled. The BTS type is defined as WBTS in all active set cells with RNP parameter NBAPCommMode.

The FDPCHEnabled parameter is allowed to be set to Enabled state only if the following requirements are fulfilled: The license CPC & F-DPCH is active. The HSDPA is enabled in the cell with RNP parameter HSDPAEnabled. The HSUPA is enabled in the cell with RNP parameter HSUPAEnabled.

DN0988674

Id:0900d805809086f7 Confidential

39

Activating and Verifying RU20 Features

The BTS type is defined as WBTS in all active set cells with RNP parameter NBAPCommMode.

Steps 1 2 Open the OMS Element Manager. Go to Tree View: Configuration Management j Network Topology j Tree View 3 Lock the WCEL object: 1. Select the WCELs object. 2. Select a cell for locking in the WCell(s) table. 3. Press the lock button under the WCell(s) table.

Figure 1 4

Object locking

For IPA-RNC check and modify the ATM Iub configuration in the COCO object. Note that the step is ATM transport-specific. There are no special actions for this feature activation with IP transport option. In order to have the SRB carried on top of the HSDPA/HSUPA channel type, the HSPA traffic type has to be added to AAL2 VCC containing the Stringent path type.

g g

Note that before modifying the COCO object, all cells under the BTS must be locked. The following AAL2 VCC combinations are recommended (the license for the RAN759: Path Selection feature is required): Combination 1: DCH & HSPA Stringent DCH & HSPA Stringent bi-level

40

Id:0900d805809086f7 Confidential

DN0988674

Activating and Verifying RU20 Features

HSPA Tolerant Combination 2: DCH & HSPA Stringent & Stringent bi-level HSPA Tolerant

For more AAL2 VCC combinations, see WCDMA RAN ATM Transport. 5 Select Edit parameters from the WCEL object.

Figure 2 6

Selecting the Edit parameters

Configure the following WCEL parameters under the Admission Control tab: 1. Set the parameter F-DPCH enabled (FDPCHEnabled) to Enabled. 2. For the following parameters the default values are recommended: F-DPCH maximum transmission power (PtxFDPCHMax) F-DPCH minimum transmission power (PtxFDPCHMin) The power offset of F-DPCH for SHO (PtxOffsetFDPCHSHO) TPC command error rate target (TPCCommandERTarget) The power offset of E-xxCH for 2ms TTI (PtxOffsetExxCH2ms) The power offset of E-xxCH for SHO (PtxOffsetExxCHSHO)

g
7 8

The F-DPCH setup (FDPCHSetup ) parameter is already configured properly - it is set to Immediate F-DPCH allocation.

Unlock the WCEL object. Select Edit parameters from the RNHSPA object.

DN0988674

Id:0900d805809086f7 Confidential

41

Activating and Verifying RU20 Features

Configure the following RNHSPA parameters, the default values are recommended: select the Handover Control tab: CPICH RSCP Threshold for SRBs on HSDPA (CPICHRSCPThreSRBHSDPA) CPICH Ec/No window for SRBs on HS-DSCH cell selection (HSDPASRBWindow) CPICH EcNo for SRB on HSPA (CPICHECNOSRBHSPA) select the Packet Scheduler tab: Offset for activation time of SRBs on HSPA (ATOSRBsOnHSPA) E-DCH maximum # of HARQ retransmissions for 10 ms SRB (EDCHMaxHarqReTxSRB)

Some of the parameters are already configured properly. These are the following: The F-DPCH and SRBs on HSPA per TC (FDPCHAndSRBOnHSPATC) RNHSPA parameter is configured as shown in figure Example on configuring RNC FDPCHAndSRBOnHSPATC parameter with parameter editor:

Figure 3

Example of configuring FDPCHAndSRBOnHSPATC RNHSPA parameter with parameter editor

The AM RLC configuration for SRB on HSPA (AMRLCSRBHSPA) RNRLC parameter is configured as shown in figure Example of configuring AMRLCSRBHSPA RNRLC parameter with parameter editor:

42

Id:0900d805809086f7 Confidential

DN0988674

Activating and Verifying RU20 Features

Figure 4

Example of configuring AMRLCSRBHSPA RNRLC parameter with parameter editor

The Priority for SRBs on HSPA (PriForSRBsOnHSPA) RNPS parameter is set to 15.

Expected outcome RAN1201: Fractional DPCH feature has been activated in the RNC. After activating the feature, there is no need to reset the RNC.

DN0988674

Id:0900d805809086f7 Confidential

43

Activating and Verifying RU20 Features

2.4.1.2

Verifying Fractional DPCH


Purpose Follow the procedure below to verify that the activation of RAN1201: Fractional DPCH feature has been successful. The verification is done by testing if standalone SRBs are mapped to the HSPA with FDPCH allocation. Also there is a direct allocation of the HSPA resources for RBs. Soft handover for standalone SRBs or SRBs and RBs mapped to the HSPA is also supported. Steps

1 2

Perform the RRC connection setup with a UE that supports Rel-7 F-DPCH. Check if the parameters in the RNC are configured as described in the activation procedure. Use RNW measurement management application in the OMS element manager to start M1002 Traffic measurements with 15 minute intarval. Alternatively, the measurement can be started using NetAct Administration of Measurements Application. Wait until the measurement interval starts. Make a PS NRT call from the cell where the parameters described in the activation procedure are enabled, then check if the HSPA is allocated to UE.

4 5

After the measurement data has been collected, use the RNW measurement presentation GUI to check if some of the following counters have their value greater than zero:

Check if the values of the following counters are incremented: Counter ID M1002C664 M1002C666 Name E-DCH ALLO FOR SRB IN SRNC HS-DSCH ALLO FOR SRB IN SRNC Abbreviation ALLO_EDCH_SRB_SRNC ALLO_HS_DSCH_SRB_SRNC

Table 8

Counters that values are incremented after activating the RAN1201: Fractional DPCH feature

44

Id:0900d8058081a598 Confidential

DN0988674

Activating and Verifying RU20 Features

Expected outcome The counter value has increased and the RAN1201: Fractional DPCH feature has been activated successfully.

DN0988674

Id:0900d8058081a598 Confidential

45

Activating and Verifying RU20 Features

2.4.1.3

Deactivating Fractional DPCH


Purpose Follow this procedure to deactivate the RAN1201: Fractional DPCH feature. Steps

1 2

Open the OMS Element Manager. Set the status of WCEL parameter FDPCHEnabled to Disabled.

Set the feature state to OFF using the following command: for IPA-RNC: ZW7M:FEA=1476:OFF; for mcRNC: set license feature-mgmt id 0000001476 feature-admin-state off

Expected outcome The RAN1201: Fractional DPCH feature has been deactivated in the RNC.

46

Id:0900d80580907965 Confidential

DN0988674

Activating and Verifying RU20 Features

2.4.2 2.4.2.1

Activating RAN1644: Continuous packet connectivity Activating Continuous packet connectivity


Purpose Follow the procedure below to activate the RAN1644: Continuous packet connectivity feature. For more information on the feature, see RAN1644: Continuous packet connectivity feature description in WCDMA RAN, Rel. RU20, Feature Descriptions. Before you start Restart of the RNC and the BTS is not required after activation of this feature. This feature is controlled by a license. For information on managing licenses, see Licensing.

The feature code for this feature is 1476. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M:FEA=1476:ON; for mcRNC: set license feature-mgmt id 0000001476 feature-admin-state on

To reduce the UE battery consumption, see Recommended new HSPA CPC value for better UE battery life TS-RNC-SW-157 Technical Support Note in Product Documentation Center. The following requirements must be fulfilled before the procedure is carried out by the user: Feature license CPC & F-DPCH is active. F-DPCH feature is enabled in all active set cells with WCEL parameter FDPCHEnabled . Continuous packet connectivity feature is enabled in all active set cells with WCEL parameter CPCEnabled . The BTS indicates for all active set cells that it supports Rel-7 CPC using NBAP: CONTINUOUS PACKET CONNECTIVITY DTX-DRX CAPABILITY information element. The HSDPA is enabled in all active set cells with RNP parameter HSDPAEnabled. The HSUPA is enabled in all active set cells with RNP parameter HSUPAEnabled. The BTS type is defined as WBTS in all active set cells with RNP parameter NBAPCommMode.

The CPCEnabled parameter is allowed to be set to Enabled state only if the following requirements are fulfilled: The license CPC & F-DPCH is active. F-DPCH feature is enabled in all active set cells with WCEL parameter FDPCHEnabled . The HSDPA is enabled in the cell with RNP parameter HSDPAEnabled. The HSUPA is enabled in the cell with RNP parameter HSUPAEnabled.

DN0988674

Id:0900d80580907e38 Confidential

47

Activating and Verifying RU20 Features

The BTS type is defined as WBTS in all active set cells with RNP parameter NBAPCommMode.

Steps 1 2 Open the OMS Element Manager. Go to Tree View: Configuration Management j Network Topology j Tree View 3 Select Edit parameters from the WCEL object:

Figure 5 4

Selecting the Edit parameters

Configure the following WCEL parameters: Select the Admission Control tab. Set the parameter F-DPCH enabled (FDPCHEnabled) to Enabled. Select the Packet Scheduler tab. Set the parameter CPC enabled (CPCEnabled) to Enabled.

5 6

Select Edit parameters from the RNHSPA object. Configure the following RNHSPA parameters structures depending on traffic class and transmission time interval (TTI); the default values are recommended: 1. Select the Packet Scheduler tab. 2. Select a desired parameters structure: CPC NRT 10 ms TTI (CPCNRT10msTTI) CPC NRT 2 ms TTI (CPCNRT2msTTI) CPC Streaming 10 ms TTI (CPCStreaming10msTTI)

48

Id:0900d80580907e38 Confidential

DN0988674

Activating and Verifying RU20 Features

CPC Streaming 2 ms TTI (CPCStreaming2msTTI) CPC Voice 10 ms TTI (CPCVoice10msTTI) CPC Voice 2 ms TTI (CPCVoice2msTTI)

For example, to configure the parameters for NRT traffic class with 10 ms TTI: 1. Select CPC NRT 10 ms TTI. 2. Select Item 1 and configure the parameters that appear on the lower right-hand side. For example, see figure Configuring the RNHSPA parameters for NRT traffic class with 10 ms TTI with parameter editor.

Figure 6

Configuring the RNHSPA parameters for NRT traffic class with 10 ms TTI with parameter editor

Expected outcome RAN1644: Continuous packet connectivity feature has been activated in the RNC. After activating the feature, there is no need to reset the RNC.

DN0988674

Id:0900d80580907e38 Confidential

49

Activating and Verifying RU20 Features

2.4.2.2

Verifying Continuous packet connectivity


Purpose Follow the procedure below to verify that the activation of RAN1644: Continuous packet connectivity feature has been successful. The verification is done through testing if the HSPA is allocated with the CPC activation. Steps

1 2

Perform the RRC connection setup with a UE that supports Rel-7 CPC. Check if the parameters in the RNC are configured as described in the activation procedure. Use RNW measurement management application in the OMS element manager to start M1001 Service Level with 15 minute intarval. Alternatively, the measurement can be started using NetAct Administration of Measurements Application. Wait until the measurement interval starts. Make a PS NRT call from the cell where the parameters described in the activation procedure are enabled, then check if the HSPA is allocated to UE. Check if the value of the counter is incremented: Counter ID M1001C677 Name UE SUPPORT FOR CONTINUOUS PACKET CONNECTIVITY Abbreviation UE_SUPP_CPC

4 5

Table 9

The counter that value is incremented after activating the RAN1644: Continuous packet connectivity feature

Expected outcome The counter value has increased and the RAN1644: Continuous packet connectivity feature has been activated successfully.

50

Id:0900d8058081a59c Confidential

DN0988674

Activating and Verifying RU20 Features

2.4.2.3

Deactivating Continuous packet connectivity


Purpose Follow this procedure to deactivate the RAN1644: Continuous packet connectivity feature. Steps

1 2 3

Open the OMS Element Manager. Set the status of WCEL parameter CPCEnabled to Disabled. Set the feature state to OFF using the following command: for IPA-RNC: ZW7M:FEA=1476:OFF; for mcRNC: set license feature-mgmt id 0000001476 feature-admin-state off

Expected outcome The RAN1644: Continuous packet connectivity feature has been deactivated in the RNC.

DN0988674

Id:0900d80580907967 Confidential

51

Activating and Verifying RU20 Features

2.5
2.5.1

Activating RAN1202: 24 kbps Paging Channel


Activating 24 kbps paging channel
Purpose Follow the procedure below to activate the RAN1202: 24 kbps paging channel feature in the RNC, using RNC object browser. For more information on the feature, see RAN1202: 24 kbps paging channel in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. 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. For more information see section Licensing. To set the feature state to ON use the following command: For IPA-RNC, use the MML command: ZW7M:FEA=1485:ON; For mcRNC, use the SCLI command: set license feature-mgmt id 0000001485 feature-admin-state on

I-HSPA Adapter is not under license control, therefore no MBLB license is needed for these products. With RAN1202: 24 kbps paging channel feature, the PCH has to be mapped to a separate. This means that when 24kbps PCH is activated (licensed and enabled), there must be at least two secondary common control physical channels (SCCPCH) supported in the cell (the maximum number of SCCPCHs per cell is 3).The number of SCCPCHs in a cell is defined by the cell level NbrOfSCCPCHs parameter. With the activation of 24 kbps PCH, the minimum value of NbrOfSCCPCHs parameter should be enhanced to 2. Prior to RAN1202 feature, this minimum value was equal to 1. To enable or disable 24kbps paging channel feature, the PCH24kbpsEnabled parameter is used. It is effective on a cell level and can be modified by object locking. Steps

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

Select the appropriate WBTS object and lock the WCEL where this feature needs to be activated. Click the arrow next to the locked WCEL object icon and select Edit Parameters.

52

Id:0900d805808f9d8d Confidential

DN0988674

Activating and Verifying RU20 Features

Update the WCEL-NbrOfSCCPCHs parameter in the WCEL object. Under SystemInfo tab, change the value of WCEL-NbrOfSCCPCHs (Number of SCCPCHs) parameter to 2 or to 3 (if SAB also needs to be configured/activated at the same time). It is required only when the current value of WCEL-NbrOfSCCPCHs parameter is 1.

g
5

Activation of the 24 kbps PCH is possible ONLY AFTER the feature license state is ON and the NbrOfSCCPCHs parameter value has been changed from the default value 1 to the new value 2 or 3.

Enable the feature in the WCEL object. Under General tab, select the WCEL-PCH24kbpsEnabled (Activate\Deactivate support for 24kbps PCH) parameter and switch it to Enabled value.

Unlock the cell. Before cell unlocking ensure that the feature license state is ON and the invalid combination of WCEL-PCH24kbpsEnabled as Enabled and WCEL-NbrOfSCCPCHs parameter value as 1 is not configured for a cell. During cell unlock all needed PRBs should check the usage of 24 kbps and should act accordingly.

Repeat steps 3-7 for every WCEL where the 24 kbps PCH requires activation. Expected outcome The RAN1202: 24 kbps paging channel feature has been activated in the RNC. The 24 kbps PCH is effective.

DN0988674

Id:0900d805808f9d8d Confidential

53

Activating and Verifying RU20 Features

2.5.2

Verifying 24 kbps paging channel


Purpose Follow the procedure below to verify that the activation of RAN1202: 24 kbps paging channel feature has been successful. Before you start Required RNC functional testing environment: RNC HW configuration is not significant for this feature. Any HW type (RNC196RNC2600) can be used and either the ATM or IP transmission. BTS should support 24 kbps paging channel. There are no special requirements for the core network. MTC calls are needed. UE should be able to accept 24 kbps PCH. There are no other requirements for the UE.

Steps Improved PCH throughput is the indication that the feature is activated. 1 Check the status of WCEL-PCH24kbpsEnabled parameter. WCEL-PCH24kbpsEnabled (Activate\Deactivate support for 24kbps PCH) parameter needs to be in Enabled state to verify that the feature is active. 2 Check the PCH throughput with MT calls. Make Mobile Terminal calls. Check the change in PCH throughput. Expected outcome The activation of RAN1202: 24 kbps paging channel feature has been verified. The 24 kbps PCH is effective.

54

Id:0900d8058080b16d Confidential

DN0988674

Activating and Verifying RU20 Features

2.5.3

Deactivating 24 kbps paging channel


Purpose Follow the procedure below to deactivate the RAN1202: 24 kbps paging channel feature in the RNC. Before you start NbrOfSCCPCHs parameter value 3 is used in case of SAB configured in the cell. Steps

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

Select the appropriate WBTS object and lock the WCEL where this feature needs to be deactivated. Click the arrow next to the locked WCEL object icon and select Edit Parameters. Update the WCEL-NbrOfSCCPCHs parameter in the WCEL object (optional). This step is optional. It is not mandatory to modify the number of SCCPCHs to 1 when deactivating this feature. 24 kbps PCH activation requires the support of at least 2 SCCPCHs, but 8 kbps PCH can be activated with any number (1, 2, or 3) of SCCPCHs. Under SystemInfo tab change the value of WCEL-NbrOfSCCPCHs (Number of SCCPCHs) parameter from 2 or 3 to 1. Values 1, 2, and 3 (based on SAB) are supported. Value 3 is used in case of SAB configured in the cell.

3 4

Disable the feature in the WCEL object. Under General tab select the WCEL-PCH24kbpsEnabled (Activate\Deactivate support for 24kbps PCH) parameter and switch it to Disabled value.

6 7

Unlock the cell. Repeat steps 3-7 for every WCELL where the 24 kbps PCH requires deactivation.

DN0988674

Id:0900d805808fb9c1 Confidential

55

Activating and Verifying RU20 Features

Change the feature license state. Set the feature license to OFF using the following command: For IPA-RNC, use the MML command: ZW7M:FEA=1485:OFF; For mcRNC, use the SCLI command: set license feature-mgmt id 0000001485 feature-admin-state off

The 24 kbps paging channel feature MUST be deactivated for all the cells in the RNC before changing the feature license state to OFF. Expected outcome The RAN1202: 24 kbps paging channel feature has been deactivated in the RNC. The 8 kbps PCH is effective.

56

Id:0900d805808fb9c1 Confidential

DN0988674

Activating and Verifying RU20 Features

2.6
2.6.1

RAN1231: HSPA over Iur (On Top)


Activating HSPA over Iur
Purpose Follow the procedure below to activate the RAN1231: HSPA over Iur feature. For more information on the feature, see the RAN1231: HSPA over Iur feature description in WCDMA RAN, rel. RU20, feature descriptions. Before you start For IPA-RNC/I-HSPA Adapter solutions: Restart of the RNC/I-HSPA Adapter and the WBTS is not required after activation of this feature. RAN1231: HSPA over Iur feature needs the following features to be activated before it can be enabled: HSDPA HSUPA RAN76: IP based Iur (optional feature) RAN312: HSDPA Dynamic Resource Allocation RAN828: HSDPA Serving Cell Change RAN829: HSDPA Soft/softer Handover for Associated DPCH RAN1515: HSPA Inter-RNC Cell Change

Note that Serving RNC (SRNC) and Drift RNC (DRNC) are equivalent to Serving IHSPA Adapter and Drift I-HSPA Adapter in terms of functionality. For the sake of clarity, SRNC and DRNC are used across the document as a reference to both controllers.

2.6.1.1

Activating HSPA over Iur for IPA-RNC solution


Before you start This feature belongs to application software and is under license key management. Make sure you have a valid license installed.

g g

There is no separate license for HSPA over Iur. This feature uses the same license as RAN1515: HSPA Inter-RNC Cell Change feature.The feature code for this feature is 1061. For more information on licensing, see Licensing. Note that there is a necessity for appropriate ATM transport configuration to contain a VCC that is able to carry HSPA traffic. This is valid when ATM-based Iur is in use. In ATM environment the AAL2 configuration should be changed with MMI command: ZLJC:<ROUTE NUMBER>,<CONNECTION ID>:<INTERFACE ID>,<VPI>,<VCI>:PEER:<LOSS RATIO>,<MUX DELAY>::IUR=YES,USAGE=DCHSPA,:; for example: ZLJC:22,1:107,1,36:PEER:5,100::IUR=YES,USAGE=DCHSPA,:;

DN0988674

Id:0900d80580935df6 Confidential

57

Activating and Verifying RU20 Features

Steps 1 2 Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC. 3 Configure the following RNFC parameters. a) Select Edit parameters from the RNFC object. b) Under the Packet Scheduler tab, set the HSDPADynamicResourceAllocation (HSDPA Dynamic Resource Allocation) management parameter to Enabled (1). c) Under the Handover Control tab, set the HSDPAMobility (Serving HS-DSCH cell change and SHO on/off switch) management parameter to Enabled (1). For more information on how to activate RAN312: HSDPA Dynamic Resource Allocation and HSDPA Mobility features, see Activating HSDPA Dynamic Resource Allocation and Activating HSDPA Mobility. 4 Make sure that the following related RNMOBI parameters have the default values. a) Under the Handover Control tab, check that the HSPADRNCEcNoOffset (DRNC Ec/No offset for HSPA Inter-RNC Cell Change) parameter is set to the default value (3 db). b) Under the Handover Control tab, check that the HSDPAServCellWindow (CPICH Ec/No window for serving HS-DSCH cell selection) parameter is set to the default value (2 db). 5 Configure the following IUR parameters. a) Select Edit parameters from the IUR object. b) Set the NRncVersion (Release version of Neighbouring RNC) parameter to Rel6 or later. c) Set the HSPAOverIur (HSPA over Iur) parameter to 1 (HSPA over Iur enabled) in the source RNC. d) Configure the MaxIurNRTHSDSCHBitRate (Maximum NRT HS-DSCH MAC-d flow bit rate over Iur) parameter in the source RNC. 6 Create one VCEL and VBTS object in the source RNC. Note that you can create only one VCEL object and it does not matter what RAC/LAC values are given. a) Select Create j new VBTS from the VBTS object. b) Select Create j new VCEL from the VCEL object. 7 Configure the following VBTS parameters. a) Select Edit parameters from the VBTS object.

58

Id:0900d80580935df6 Confidential

DN0988674

Activating and Verifying RU20 Features

b) Configure the HARQRVConfiguration (HARQ RV Configuration) parameter. 8 Configure the following VCEL parameters. Select Edit parameters from the VCEL object. Set the HSDPAenabled (HSDPA enabled) parameter to Enabled. Set the HSUPAenabled (HSUPA enabled) parameter to Enabled. Configure the following parameters: MaxTotalUplinkSymbolRate (maximum total uplink symbol rate) HSPAFmcsIdentifier (HSPA FMCS identifier) EDCHMinimumSetETFCI (E-DCH minimum set E-TFCI) HSDPAHopsIdentifier (HSDPA HOPS identifier) PtxOffsetHSSCCH (the power offset of the HS-SCCH) HSDPAFmcsIdentifier (HSDPA FMCS identifier) HSDPAFmciIdentifier (HSDPA FMCI identifier) HSDPAFmcgIdentifier (HSDPA FMCG identifier) e) Configure HOPS for the DRNC neighbor cell: HSDPAAvailabilityIur (HSDPA availability of the neighboring DRNC cell) parameter set to HSDPA available (1) HSUPAAvailabilityIur (HSUPA availability of the neighboring DRNC cell) parameter set to HSUPA available (1) Expected outcome Feature RAN1231: HSPA over Iur has been activated in the IPA-RNC. a) b) c) d)

2.6.1.2

Activating HSPA over Iur for I-HSPA Adapter solution


Before you start In I-HSPA Adapter there is no need to activate feature licenses. Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the I-BTS.

Configure the following RNFC parameters. a) Select Edit RNW parameters from the RNFC object. b) Under the Packet Scheduler tab, set the HSDPADynamicResourceAllocation (HSDPA Dynamic Resource Allocation) management parameter to Enabled (1). c) Under the Handover Control tab, set the HSDPAMobility (Serving HS-DSCH cell change and SHO on/off switch) management parameter to Enabled (1).

DN0988674

Id:0900d80580935df6 Confidential

59

Activating and Verifying RU20 Features

Make sure that the following related RNMOBI parameters have the default values. a) Under the Handover Control tab, check that the HSPADRNCEcNoOffset (DRNC Ec/No offset for HSPA Inter-RNC Cell Change) parameter is set to the default value (3 db). b) Under the Handover Control tab, check that the HSDPAServCellWindow (CPICH Ec/No window for serving HS-DSCH cell selection) is set to the default value (2 db).

Configure the following IUR parameters. a) Select Edit RNW parameters from the IUR object. b) Set the NRncVersion (Release version of Neighbouring RNC) parameter to Rel6 or later. c) Set the HSPAOverIur (HSPA over Iur) parameter to 1 (HSPA over Iur enabled) in the source RNC. d) Configure the MaxIurNRTHSDSCHBitRate (Maximum NRT HS-DSCH MAC-d flow bit rate over Iur) parameter in the source RNC.

Create one VCEL and VBTS object in the source IADA. Note that you can create only one VCEL object and it does not matter what RAC/LAC values are given. a) Select Create j new VBTS from the VBTS object. b) Select Create j new VCEL from the VCEL object.

Configure the following VBTS parameters. a) Select Edit RNW parameters from the VBTS object. b) Configure the HARQRVConfiguration (HARQ RV Configuration) parameter.

Configure the following VCEL parameters. Select Edit RNW parameters from the VCEL object. Set the HSDPAenabled (HSDPA enabled) parameter to Enabled. Set the HSUPAenabled (HSUPA enabled) parameter to Enabled. Configure the following parameters: MaxTotalUplinkSymbolRate (maximum total uplink symbol rate) HSPAFmcsIdentifier (HSPA FMCS identifier) EDCHMinimumSetETFCI (E-DCH minimum set E-TFCI) HSDPAHopsIdentifier (HSDPA HOPS identifier) PtxOffsetHSSCCH (the power offset of the HS-SCCH) HSDPAFmcsIdentifier (HSDPA FMCS identifier) HSDPAFmciIdentifier (HSDPA FMCI identifier) HSDPAFmcgIdentifier (HSDPA FMCG identifier) e) Configure HOPS for the DRNC neighbor cell: HSDPAAvailabilityIur (HSDPA availability of the neighboring DRNC cell) parameter set to HSDPA available (1) a) b) c) d)

60

Id:0900d80580935df6 Confidential

DN0988674

Activating and Verifying RU20 Features

HSUPAAvailabilityIur (HSUPA availability of the neighboring DRNC cell) parameter set to HSUPA available (1)

Expected outcome Feature RAN1231: HSPA over Iur has been activated in the I-HSPA Adapter.

DN0988674

Id:0900d80580935df6 Confidential

61

Activating and Verifying RU20 Features

2.6.2

Verifying HSPA over Iur


Purpose Follow the procedure below to verify that the activation of the RAN1231: HSPA over Iur feature has been successful. Note that the same verifying procedure applies to IPA-RNC and I-HSPA Adapter. Before you start To be able to verify the activation of the feature, the following network configurations are required: The feature has to be activated in SRNC. HSPA Inter-RNC Cell Change license must be enabled in the DRNC. Required in DRNC: HSDPAMobility and HSDPADynamicResourceAllocation parameters set to Enabled HSPA is enabled and the cell supports HSPA Minimum one BTS and one cell should support the required features.

Steps 1 Open the RNW Measurement Management application in the Application Launcher. Start the M1008 and M1004 measurements in the source RNC (SRNC) with the RNW Measurement Management application in the Application Launcher. Start the M1002 measurements in the drift RNC (DRNC). Wait until the measurement data collection starts and after that make a PS NRT call for HSPA Capable UE in SRNC cell. Start a continuous FTP download over the PS NRT data connection. Move the UE to DRNC cell. Check if the HSPA Serving Cell Change procedure is successfully executed from source RNC cell to drift RNC cell over Iur and the PS NRT HSPA call continues normally with the HS-DSCH/E-DCH Mac-d flow over Iur in the DRNC AS cell after HSPA SCC. After the measurement data has been collected, use the RNW Measurement Presentation application to verify the counter values in the source and drift RNC. a) Check if the following counters have value 1 in the source RNC: M1008C275 HS-DSCH INTER RNC SERVING CELL CHANGES SUCCESSFUL M1008C277 E-DCH INTER RNC SERVING CELL CHANGES SUCCESSFUL

4 5 6

62

Id:0900d8058089fe92 Confidential

DN0988674

Activating and Verifying RU20 Features

M1004C173 HS-DSCH MAC-D FLOW ALLOCATION ATTEMPTS OVER IUR ON SRNC M1004C174 HS-DSCH MAC-D FLOW ALLOCATION SUCCESS OVER IUR ON SRNC b) Check if the following counters have value 1 in the drift RNC: M1002C630 HS-DSCH ATTEMPTS IN DRNC M1002C631 HS-DSCH ALLOCATIONS IN DRNC M1002C633 E-DCH ATTEMPTS IN DRNC M1002C634 E-DCH ALLOCATIONS IN DRNC Expected outcome The RAN1231: HSPA over Iur feature has been activated successfully.

DN0988674

Id:0900d8058089fe92 Confidential

63

Activating and Verifying RU20 Features

2.6.3

Deactivating HSPA over Iur


Purpose Follow the procedure below to deactivate the RAN1231: HSPA over Iur feature in source RNC. Note that the same deactivating procedure applies to IPA-RNC and I-HSPA Adapter. Steps

1 2

Open the OMS Element Manager. Configure the IUR object. Set the HSPAOverIur (HSPA over Iur) parameter to 0 (HSPA over Iur disabled). Expected outcome The RAN1231: HSPA over Iur feature has been deactivated in the SRNC.

64

Id:0900d8058089fe90 Confidential

DN0988674

Activating and Verifying RU20 Features

2.7
2.7.1

RAN1470: HSUPA 2ms TTI


Activating HSUPA 2 ms TTI
Purpose Follow the procedure below to activate the RAN1470: HSUPA 2 ms TTI feature. For more information on the feature, see the RAN1470: HSUPA 2 ms TTI feature description in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. This feature belongs to application software and is under license key management. Make sure you have a valid license installed. For more information on licensing, see Licensing. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=1475:ON; for mcRNC: set license feature-mgmt id 0000001475 feature-admin-state on BTS: Flexi Rel. 2 RAN1671: Enhanced ultrasite baseband (EUBB) (this feature only applies to the Ultrasite WBTS) RNC: For the RNC196 and RNC450, a hardware upgrade is required according to feature RAN1226: HSPA peak rate upgrade in RNC196 and RNC450 . This means that the support of HSUPA 2 ms TTI is possible only with the new hardware CDSP-DH (DMCU) configured as feature upgrade.

Hardware requirements:

Note that the RAN1470: HSUPA 2 ms TTI feature can be activated only if HSDPA and HSUPA are enabled in a cell and the BTS type is set as WBTS beforehand.

With the ATM Iub transport the AAL2 VCC configuration requires special emphasis once activating the SRB HSPA services. See step 4 Check and modify the ATM Iub configuration (only for IPA-RNC). Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

Lock the cell.

DN0988674

Id:0900d8058090d764 Confidential

65

Activating and Verifying RU20 Features

Check and modify the ATM Iub configuration (only for IPA-RNC). In order to have SRB HSPA services carried on top of the HSDPA/HSUPA channel type, the HSPA traffic type has to be added to AAL2 VCC containing the Stringent path type in the COCO object.

Note that before modifying the COCO object, all cells under the BTS must be locked. The following AAL2 VCC combinations are recommended (the license for the RAN759: Path Selection feature is required): Combination 1: DCH & HSPA Stringent DCH & HSPA Stringent bi-level HSPA Tolerant Combination 2: DCH & HSPA Stringent & Stringent bi-level HSPA Tolerant

For more AAL2 VCC combinations, see WCDMA RAN ATM Transport.

g
5

Note that ATM part is IPA-RNC specific. There is no special handling in transport area for mcRNC. In the WCEL object under the Admission Control tab, enable HSDPAenabled (HSDPA enabled) parameter and under the Packet Scheduler tab, HSUPAenabled (HSUPA enabled) parameter. Under the Identification tab, define the WBTS object type using the NBAPCommMode (NBAP Communication Mode) parameter. In the WCEL object under the Admission Control tab, enable the HSUPA2MSTTIEnabled (HSUPA 2 ms TTI enabled) parameter. Unlock the WCEL object. Expected outcome RAN1470: HSUPA 2 ms TTI feature has been activated.

66

Id:0900d8058090d764 Confidential

DN0988674

Activating and Verifying RU20 Features

2.7.2

Verifying HSUPA 2 ms TTI


Purpose Follow the procedure below to verify that the activation of the RAN1470: HSUPA 2 ms TTI feature has been successful. Steps

Start measurements M5000 and M5002 Traffic with 1 hour interval. Use RNW measurement application in the Application Launcher to start this measurement. Alternatively the measurement can be started using NetAct administration of measurement application.

Enable the following counters: HSUPA throughput distribution (M5002C38-M5002C49) Reporting E-DCH TTI efficiency (M5000C320 - M5000C323) Reporting of number of HSUPA users per TTI (M5000C324- M5000C325)

3 4

Use the existing counters to monitor the mapping of the SRBs. Make a few calls and check the counters once the reporting period for the measurements has been completed.

DN0988674

Id:0900d80580812ec3 Confidential

67

Activating and Verifying RU20 Features

2.7.3

Deactivating HSUPA 2 ms TTI


Purpose Follow the procedure below to deactivate the feature. Steps The RAN1470: HSUPA 2ms TTI feature can be deactivated by setting the WCEL parameter HSUPA2MSTTIEnabled value of the used cell to Disabled.

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

3 4

Lock the WCEL object. Set the WCEL HSUPA2MSTTIEnabled (HSUPA 2 ms TTI enabled) parameter value to Disabled. Unlock the WCEL object. Further information After deactivating the feature, set the feature license state to OFF using: for IPA-RNC: ZW7M: FEA=1475:OFF; for mcRNC: set license feature-mgmt id 0000001475 feature-admin-state off

Expected outcome The RAN470: HSUPA 2 ms TTI feature has been deactivated.

68

Id:0900d8058090e553 Confidential

DN0988674

Activating and Verifying RU20 Features

2.8
2.8.1

RAN1642: MIMO
Activating MIMO
Purpose Follow the procedure below to activate the RAN1642: MIMO feature. For more information on the feature, see the RAN1642: MIMO feature description in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. RAN1642: MIMO feature needs the following features to be activated before it can be enabled: HSDPA HSUPA RAN827 HSDPA Dynamic Resource Allocation RAN828: HSDPA Serving Cell Change RAN829: HSDPA Soft/softer Handover for Associated DPCH RAN1258: HSDPA 14 Mbps per User RAN1470: HSUPA 2 ms TTI RAN1638: Flexible RLC

g
2.8.1.1

If the SRB is mapped to DCH in DL and E-DCH in UL, the RNC assigns MIMO resources to the UE only if the EcNo value reported by the UE in rrcConnectionRequest is better as the threshold defined by the CPICH EcNo Threshold for EDCH 2ms RNC parameter. Otherwise a normal HSPA call is established.

Activating MIMO for IPA-RNC and mcRNC solution


Before you start This feature belongs to application software and is under license key management. Make sure you have a valid license installed. For more information on licensing, see Licensing chapter. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=1554:ON; for mcRNC: set license feature-mgmt id 0000001554 feature-admin-state on

Steps 1 2 Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

DN0988674

Id:0900d8058090d768 Confidential

69

Activating and Verifying RU20 Features

Configure the following RNFC parameters. 1. Select Edit parameters from the RNFC object. 2. Under the Packet Scheduler tab, set the HSDPADynamicResourceAllocation (HSDPA Dynamic Resource Allocation) parameter to Enabled (1). 3. Under the Handover Control tab, set the HSDPAMobility (Serving HS-DSCH cell change and SHO on/off switch) parameter to Enabled (1). 4. Under the Admission Control tab, set the FRLCEnabled (Flexible RLC Enabled) parameter to Enabled (1).

Configure the following WBTS parameters. 1. Select Edit parameters from the WBTS object. 2. Under the Admission Control tab, set the HSDPA14MbpsPerUser parameter to Enabled (1). 3. Under the Identification tab, set the NBAPCommMode (NBAP Communication Mode) parameter to 0 (UltraSite BTS, FlexiBTS, PicoBTS).

5 6

Lock the cell. Configure the following WCEL parameters. 1. Select Edit parameters from the WCEL object. 2. Under the Admission Control tab, set the HSDPAenabled (HSDPA enabled) parameter to Enabled (1). 3. Under the Packet Scheduler tab, set the HSUPAEnabled (HSUPA enabled) parameter to Enabled (1). 4. Under the Admission Control tab, set the HSUPA2MSTTIEnabled (HSUPA 2 ms TTI enabled) parameter to Enabled (1). 5. Under the Packet Scheduler tab, set the MIMOEnabled (MIMO enabled) parameter to Enabled (1).

7 8

Unlock the cell. Configure MIMO in the BTS. 1. MIMO is commissioned in the BTS and it needs to follow the restrictions: Software needed: WN6.0EP1 For Flexi: Flexi rel2 System Module is required. FSMC/D/E HW is required unit. MIMO is not supported on legacy of FSMB HW units. Two TRXs are needed for each MIMO local cell resource (LCR). Rel1 single RF module cannot be part of MIMO cell. Others are supported. Mixture of rel1 power amplifier and rel2 power amplifier branches for one cell/sector is not allowed. For Ultra:

70

Id:0900d8058090d768 Confidential

DN0988674

Activating and Verifying RU20 Features

2 wideband power amplifiers (WPA) are required per MIMO cell. Enhanced UltraSite Baseband (EUBB) HW is required. MIMO is not supported on legacy of WSPC HW units. Both TX branches have to be configured from the same WTRB/D HW. Each MIMO LCR requires two TRXs. 2. One of the following schedulers can be chosen: Full baseband = dedicated cell based scheduler Shared Scheduler for BB efficiency = two cells scheduler in MIMO usage 3. Virtual antenna mapping (VAM) can be used with MIMO in cell. When local cell resource (LCR) is configured to MIMO-capable, the BTS informs the RNC in NBAP: AUDIT RESPONSE that the cell is MIMO-capable. Expected outcome Feature RAN1642: MIMO has been activated in the RNC.

2.8.1.2

Activating MIMO for I-HSPA solution


Steps

1 2 3

Open the OMS Element Manager. In OMS Element Manager, expand the topology tree of the IADA. Configure the following I-HSPA Adapter parameters 1. Under IADA topology tree create or modify the RNFC object. 1.1 Select the RNFC object and from drop-down menu select Edit parameters. 1.2 In the Packet Scheduler tab set the HSDPADynamicResourceAllocation parameter to Enabled. 1.3 In the Handover Control tab set the HSDPAMobility parameter to Enabled. 1.4 In the Admission Control tab set the FRLCEnabled parameter to Enabled.

Configure the following WBTS parameters 1. Select the WBTS object and from drop-down menu select Edit parameters. 2. In the Admission Control tab set the HSDPA14MbpsPerUser parameter to Enabled.

Configure the WCEL parameters 1 2 3 In the Topology Tree View go to I-HSPA Topology IADA WBTS WCEL of interest. Lock the cell. Select the WCEL of interest and from drop-down menu select Edit parameters.

DN0988674

Id:0900d8058090d768 Confidential

71

Activating and Verifying RU20 Features

Configure the following WCEL parameters 1. In the Admission Control tab set the HSDPAenabled parameter to Enabled. 2. In the Packet Scheduler tab set the HSUPAEnabled parameter to Enabled. 3. In the Admission Control tab set the HSUPA2MSTTIEnabled parameter to Enabled. 4. In the Packet Scheduler set the MIMOEnabled parameter to Enabled.

5 6

Unlock the cell

Configure MIMO in the BTS 1. MIMO is commissioned in the BTS and it needs to follow the restrictions: Software needed: WN6.0EP1 For Flexi: Flexi rel2 System Module is required. FSMC/D/E HW is required unit. MIMO is not supported on legacy of FSMB HW units. Two TRXs are needed for each MIMO local cell resource (LCR). Rel1 single RF module cannot be part of MIMO cell. Others are supported. Mixture of rel1 power amplifier and rel2 power amplifier branches for one cell/sector is not allowed. For Ultra: 2 wideband power amplifiers (WPA) are required per MIMO cell. Enhanced UltraSite Baseband (EUBB) HW is required. MIMO is not supported on legacy of WSPC HW units. Both TX branches have to be configured from the same WTRB/D HW. Each MIMO LCR requires two TRXs. 2. One of the following schedulers can be chosen: Full baseband = dedicated cell based scheduler Shared Scheduler for BB efficiency = two cells scheduler in MIMO usage 3. Virtual antenna mapping (VAM) can be used with MIMO in cell. When local cell resource (LCR) is configured to MIMO-capable, the BTS informs the RNC in NBAP: AUDIT RESPONSE that the cell is MIMO-capable. Expected outcome Feature RAN1642: MIMO has been activated in the I-HSPA Adapter.

72

Id:0900d8058090d768 Confidential

DN0988674

Activating and Verifying RU20 Features

2.8.2

Verifying MIMO
Purpose Follow the procedure below to verify that the activation of the RAN1642: MIMO feature has been successful. Steps

1 2

Perform the RRC connection setup with a UE that supports MIMO. Open the RNW measurement management application from Application Launcher. Use the RNW measurement management application to start measurements M5000 HSPA in WBTS with 15 minute interval. Alternatively the measurement can be started using NetAct Administration of Measurements Application. Wait until the measurement interval starts.

After the measurement data has been collected, use the RNW Measurement presentation GUI to check if the following counters have their values greater than 0. Only some of the counters are updated depending on the events in the radio interface. Counter updated in In I-HSPA Adapter or WCDMA RNC: M1006C245 - RADIO BEARER CONFIGURED FOR MIMO Counters M5000 HSPA updated in WBTS: M5000C335 - TTIS SCHEDULED FOR MIMO USERS WITH SINGLE STREAM M5000C336 - TTIS SCHEDULED FOR MIMO USERS WITH DUAL STREAM M5000C337 - ORIGINAL MAC-EHS PDU TRANSMISSION WITH MIMO DUAL STREAM M5000C338 - MAC-EHS PDU RETRANSMISSION WITH MIMO DUAL STREAM M5000C339 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS0 M5000C340 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS1 M5000C341 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS2 M5000C342 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS3 M5000C343 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS4 M5000C344 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS5 M5000C345 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS6 M5000C346 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS7 M5000C347 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS8 M5000C348 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS9 M5000C349 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS10 M5000C350 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS11 M5000C351 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS12 M5000C352 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS13

DN0988674

Id:0900d805808bc972 Confidential

73

Activating and Verifying RU20 Features

M5000C353 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS14 M5000C354 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS15 M5000C355 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS16 M5000C356 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS17 M5000C357 - CQI CORRELATED FOR MIMO DUAL STREAM CLASS18 M5000C358 - SUM OF USERS WITH ACTIVE MIMO

Expected outcome The counters are being updated. The measured throughput, based on terminal capabilities (theoretical peak throughput of UE category 16 is 28 Mbit/s), UE receiver quality, and radio conditions, is as expected. The RAN1642: MIMO feature has been activated successfully.

74

Id:0900d805808bc972 Confidential

DN0988674

Activating and Verifying RU20 Features

2.8.3

Deactivating MIMO
Purpose Follow the procedure below to deactivate the RAN1642: MIMO feature. Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

3 4

Lock the cell. Configure the WCEL object. Set the MIMOEnabled (MIMO enabled) parameter to Disabled (0).

5 6

Unlock the cell. Set the feature state to OFF. for IPA-RNC: ZW7M: FEA=1554:OFF; for mcRNC: set license feature-mgmt id 0000001554 feature-admin-state off

Expected outcome The RAN1642: MIMO feature has been deactivated.

DN0988674

Id:0900d805808a8629 Confidential

75

Activating and Verifying RU20 Features

2.9
2.9.1

RAN1643: HSDPA 64QAM


Activating HSDPA 64QAM
Purpose Follow the procedure below to activate the RAN1643: HSDPA 64QAM feature. For more information on the feature, see the RAN1643: HSDPA 64QAM feature description in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. This feature belongs to application software and is under license key management. Make sure you have a valid license installed. For more information on licensing, see Licensing. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=1471:ON; for mcRNC: set license feature-mgmt id 0000001471 feature-admin-state on

Before activating the RAN1643: HSDPA 64QAM feature, enable the RAN1638: Flexible RLC feature. For information about activating the RAN1638: Flexible RLC, see Activating and operating the feature in RAN1638: Flexible RLC (DL) feature description. Both features RAN1638: Flexible RLC and RAN1643: HSDPA 64QAM can be used only under the WCDMA BTSs in the network that supports these features. WBTS capabilities are received by the RNC in NBAP: Audit response and NBAP: Resource status Indication messages. WBTS capabilities are read from IEs: SixtyfourQAM DL capability and HS-DSCH MAC-d PDU size capability. If the corresponding capabilities in any WBTS are reported as not supported, the feature is not available to the UEs under that WCDMA BTS even if it is activated in the RNC. Note that feature RAN1643: HSDPA 64QAM and feature RAN1642: MIMO 2x2 cannot be enabled simultaneously. 64QAM can be enabled only on System Module Rel2 (FSMC/ FSMD/ FSME) or EUBB. For best performance: 64QAM should be enabled on HSPA carrier (not shared) in order: to decrease interferences from R99 users not to decrease available number of spreading codes F-DPCH feature should be used if available. It reduces code tree occupation and introduces higher probability of 64QAM usage.

Support of HSDPA 64QAM is possible only with the CDSP-DH (DMCU) configured as Feature Upgrade.

w g
76

Ensure you have configured the QoS profile of the UE in HLR in order to reach the downlink bit rate of 21M or higher. For information about HLR, see Nokia Siemens Networks DX HLR, Product Description. In order to guarantee a full utilization of the 64QAM modulation, the value of the MaxNbrOfHSSCCHCodes parameter is supposed to be 2 at the minimum, and feature

Id:0900d805809138cf Confidential

DN0988674

Activating and Verifying RU20 Features

HSDPA code multiplexing is to be supported in a cell where feature HSDPA 64QAM is enabled. If HSSCCHCode number is 1, then the utilization is not always the best possible because of the relationship between number of HS-PDSCH codes and HSSCCHCode number defined in standard TS 25.212 (chapter 4.6.2.3 Channelization codeset mapping). Steps 1 Ensure that the license of HSDPA 15 codes feature is active. For more information about activating RAN852: HSDPA 15 codes feature, see Activating HSDPA 15 codes. 2 Ensure that the license of HSDPA code multiplexing feature is active if a full utilization of 64QAM is wanted. Feature RAN853: HSDPA code multiplexing should be activated if a full utilization of the 64QAM is wanted. For more information, see notification in Before you start section. For more information about activating RAN853: HSDPA code multiplexing, see Activating HSDPA code multiplexing. 3 4 Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC. 5 Ensure that HS-PDSCH 15 codes is available: HSPDSCHCodeSet (HS-PDSCH code set) contains 5, 8, 10, 12, 14, and 15 codes Under the SystemInfo tab, configure only one SCCPCH (Reduce the DL code occupation) (parameter Number of SCCPCHs) Under the Admission Control tab, set MaxNbrOfHSSCCHCodes (Maximum number of HS-SCCH codes) parameter value to 1 or if a full utilization of HSDPA 64QAM is wanted, set the MaxNbrOfHSSCCHCodes parameter value to 2. Note that to guarantee the full utilization also step 2 has to be done. For more information, see notification in Before you start section.

Ensure that the Flexible RLC feature is activated in the RNC as mentioned in the Before you start section. Under the Admission Control tab, set the WCEL level management HSDPA64QAMAllowed (HSDPA 64 QAM allowed) parameter to Enabled (1). Change the RNHSPA level MaxBitRateNRTMACDFlow (Maximum bit rate of NRT MAC-d flow) parameter to HSDPA 64QAM maximum value 20992 (under the Admission Control tab).

DN0988674

Id:0900d805809138cf Confidential

77

Activating and Verifying RU20 Features

Expected outcome RAN1643: HSDPA 64QAM feature has been activated.

78

Id:0900d805809138cf Confidential

DN0988674

Activating and Verifying RU20 Features

2.9.2

Verifying HSDPA 64QAM


Purpose Follow the procedure below to verify that the activation of the RAN1643: HSDPA 64QAM feature has been successful. Steps The activation of the RAN1643: HSDPA 64QAM feature can be verified by observing throughput, because bitrates exceeding 14Mbps can be achieved only with this HSDPA 64QAM feature.

1 2

Ensure that the HS-DSCH serving cell is Flexible RLC size capable. Ensure that the UE is Flexible RLC size capable. Use UE with HSDPA categories 13, 14, 17 or 18.

3 4 5 6 7

Make an HSDPA/HSUPA call. Ensure that the allocated RB channel type is HSPA. Start a large FTP transfer. Verify that the application level bit rate of the HSPA call is above 14 Mbps. Release the call.

DN0988674

Id:0900d80580812ee1 Confidential

79

Activating and Verifying RU20 Features

2.9.3

Deactivating HSDPA 64QAM


Purpose Follow the procedure below to deactivate the feature. Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

Set the WCEL level management HSDPA64QAMAllowed (HSDPA 64 QAM allowed) parameter to Disabled (0). Further information To deactivate the RAN1643: HSDPA 64 QAM feature in the whole RNC, set the feature state to OFF. Expected outcome The RAN1643: HSDPA 64QAM feature has been deactivated.

80

Id:0900d8058090e55b Confidential

DN0988674

Activating and Verifying RU20 Features

2.10
2.10.1

RAN1686: HSPA 72 Users per Cell


Activating HSPA 72 Users per Cell
Purpose Follow the procedure below to activate the RAN1686: HSPA 72 Users per Cell feature. For more information on the feature, see the RAN1686: HSPA 72 Users per Cell feature description in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. This feature belongs to application software and is under license key management. Make sure you have a valid license installed. For more information on licensing, see Licensing. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=1478:ON; for mcRNC: set license feature-mgmt id 0000001478 feature-admin-state on

RAN1686: HSPA 72 Users per Cell feature needs the following features to be activated before it can be enabled: HSDPA HSUPA RAN312: HSDPA Dynamic Resource Allocation RAN1464: HSDPA 64 Users per Cell RAN1465: HSUPA 60 Users per BTS

g
1 2

The value of the MaxNumberEDCHLCG parameter depends on the BTS HW. The value of MaxNbrOfHSSCCHCodes can be 4 only when the flexi release2 HW/EUBB is used. Steps Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

Configure the RNFC object. 1. Select Edit parameters from the RNFC object. 2. Under the Packet Scheduler tab, enable HSDPA dynamic resource allocation with HSDPADynamicResourceAllocation (HSDPA Dynamic Resource Allocation) configuration parameter.

Lock the cell.

DN0988674

Id:0900d8058095ac76 Confidential

81

Activating and Verifying RU20 Features

Configure the WCEL object. 1. Select Edit parameters from the WCEL object. 2. Under the Admission Control tab, enable HSDPA with HSDPAEnabled (HSDPA enabled) RNP parameter, and under the Packet Scheduler tab HSUPA with HSUPAEnabled (HSUPA enabled) RNP parameter. 3. Under the Admission Control tab, enable the HSPA 72 users per cell feature with HSPA72UsersPerCell (HSPA 72 Users per Cell) management parameter.

Unlock the cell. Expected outcome Feature HSPA 72 Users per Cell has been activated.

82

Id:0900d8058095ac76 Confidential

DN0988674

Activating and Verifying RU20 Features

2.10.2

Verifying HSPA 72 Users per Cell


Purpose Follow the procedure below to verify that the activation of the RAN1686: HSPA 72 Users per Cell feature has been successful. Steps

Open the RNW measurement management application from Application Launcher. If the M1000 Cell Resource measurement is not active, start the RNW measurement management application in application launcher. For more information on starting measurements, see Management of basic RNW measurements and Starting radio network measurements.

3 4

Make more than 64 simultaneous PS NRT calls using HSPA capable UEs. After the measurement data has been collected, use the RNW Measurement Presentation application to check that some of the following counters have a value other than 0. M1000C364 DURATION OF ACTIVE HSDPA USERS - 65 TO 72 SIMULTANEOUS USERS M1000C365 DURATION OF ACTIVE HSUPA USERS - 21 TO 24 SIMULTANEOUS USERS M1000C366 DURATION OF ACTIVE HSUPA USERS - 25 TO 28 SIMULTANEOUS USERS M1000C367 DURATION OF ACTIVE HSUPA USERS - 29 TO 32 SIMULTANEOUS USERS M1000C368 DURATION OF ACTIVE HSUPA USERS - 33 TO 36 SIMULTANEOUS USERS M1000C369 DURATION OF ACTIVE HSUPA USERS - 37 TO 40 SIMULTANEOUS USERS M1000C370 DURATION OF ACTIVE HSUPA USERS - 41 TO 44 SIMULTANEOUS USERS M1000C371 DURATION OF ACTIVE HSUPA USERS - 45 TO 48 SIMULTANEOUS USERS M1000C372 DURATION OF ACTIVE HSUPA USERS - 49 TO 52 SIMULTANEOUS USERS M1000C373 DURATION OF ACTIVE HSUPA USERS - 53 TO 56 SIMULTANEOUS USERS M1000C374 DURATION OF ACTIVE HSUPA USERS - 57 TO 60 SIMULTANEOUS USERS M1000C375 DURATION OF ACTIVE HSUPA USERS - 61 TO 64 SIMULTANEOUS USERS

DN0988674

Id:0900d80580812f09 Confidential

83

Activating and Verifying RU20 Features

M1000C376 DURATION OF ACTIVE HSUPA USERS - 65 TO 72 SIMULTANEOUS USERS M1031C0 SIMULTANEOUS MAX HSDPA USERS COUNTERS PER BTS M1031C1 SIMULTANEOUS MAX HSUPA USERS COUNTERS PER BTS M1031C2 SUM OF THE SAMPLED VALUES FOR NUMBER OF SIMULTANEOUS HSDPA USERS PER WBTS M1031C3 SUM OF THE SAMPLED VALUES FOR NUMBER OF SIMULTANEOUS HSUPA USERS PER WBTS M1031C4 COMMON DENOMINATOR COUNTER FOR HSDPA AND HSUPA Expected outcome The RAN1686: HSPA 72 Users per Cell feature has been activated successfully.

84

Id:0900d80580812f09 Confidential

DN0988674

Activating and Verifying RU20 Features

2.10.3

Deactivating HSPA 72 Users per Cell


Purpose Follow the procedure below to deactivate the RAN1686: HSPA 72 Users per Cell feature. Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

3 4

Lock the cell. Configure the WCEL object. Under the Admission Control tab, set the HSPA72UsersPerCell (HSPA 72 Users per Cell) parameter to Not enabled (0).

5 6

Unlock the cell. Set the feature state to OFF. for IPA-RNC: ZW7M: FEA=1478:OFF; for mcRNC: set license feature-mgmt id 0000001478 feature-admin-state off

Expected outcome The RAN1686: HSPA 72 Users per Cell feature has been deactivated.

DN0988674

Id:0900d80580875ddd Confidential

85

Activating and Verifying RU20 Features

2.11
2.11.1

RAN1689: CS Voice over HSPA (On Top)


Activating CS Voice over HSPA
Purpose Follow the procedure below to activate the RAN1689: CS Voice over HSPA feature. For more information on the feature, see the RAN1689: CS Voice over HSPA feature description in WCDMA RAN, rel. RU20, feature descriptions. Before you start For RNC/I-HSPA Adapter solutions: Restart of the RNC/I-HSPA Adapter and the WBTS is not required after activation of this feature. This is an optional feature in the RNC/I-HSPA Adapter. RAN1689: CS Voice over HSPA feature needs the following features to be activated before it can be enabled: HSDPA HSUPA RAN312: HSDPA Dynamic Resource Allocation RAN767: HSDPA with Simultaneous AMR Voice Call RAN974: HSUPA with Simultaneous AMR Voice Call RAN1201: Fractional DPCH RAN1262: QoS Aware HSPA Scheduling RAN1638: Flexible RLC RAN1644: Continuous Packet Connectivity

2.11.1.1

Activating CS Voice over HSPA for IPA-RNC and mcRNC solution


Before you start This feature belongs to application software and is under license key management. Make sure you have a valid license installed. For more information on licensing, see Licensing chapter. For I-HSPA Adapter go directly to the first step as the license verification is not needed in I-HSPA. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=1477:ON; for mcRNC: set license feature-mgmt id 0000001477 feature-admin-state on

In IPA-RNC the activation of the CS Voice over HSPA feature is possible only when there are CDSP-DH cards in upgrade mode. Note that CDSP-DH cards in RNC2600 are already in upgrade mode without any further configuration. In RNC196 and RNC450 CDSP-DH cards are in replacement mode after first installation. To set them to upgrade mode perform the following steps: delete corresponding DMCUs execute ZWPU MML command (only in IPA-RNC)

86

Id:0900d8058090d76c Confidential

DN0988674

Activating and Verifying RU20 Features

install the DMCUs back

Note that in ATM transport appropriate VCC configuration is required to handle CS Voice over HSPA traffic. For example, in case RAN759: Path Selection feature is enabled, the CS Voice over HSPA connection is mapped to HSPA/HSDPA/HSUPA Stringent path type - VCC configuration should contain these path types in order to handle the traffic. See step 6 Check and modify the ATM Iub configuration (only for IPARNC). Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

Configure the following RNPS parameter. 1. Select Edit parameters from the RNPS object. 2. Under the Packet Scheduler tab, check the PriForConvOnHSPA (Priority for conversational on HSPA) value of the QoSPriorityMapping (QoS Priority Mapping) management parameter and update it, if the default value is not set according to the prioritization needs.

g
4

For conversational services set the priority lower than the priority set for SRBs, but higher than the priority set for PS streaming services.

Configure the following RNHSPA parameter. 1. Select Edit parameters from the RNHSPA object. 2. Check if the use of HSPA for CS voice service is allowed with the following parameters: Under the Packet Scheduler tab, the EDCHQOSClasses (E-DCH QoS classes) Under the Admission Control tab, the HSDSCHQoSclasses (HS-DSCH QoS classes) 3. Under the Admission Control tab, check with the FDPCHSetupEC (FDPCH Setup based on Establishment Cause) parameter, whether priority/emergency CS voice call can be mapped to HSPA.

5 6

Lock the cell. Check and modify the ATM Iub configuration (only for IPA-RNC). In order to have RT HSPA services carried on top of the HSDPA/HSUPA channel type, the HSPA traffic type has to be added to AAL2 VCC containing the Stringent path type in the COCO object.

g
DN0988674

Note that before modifying the COCO object, all cells under the BTS must be locked.

Id:0900d8058090d76c Confidential

87

Activating and Verifying RU20 Features

The following AAL2 VCC combinations are recommended (the license for the RAN759: Path Selection feature is required): Combination 1: DCH & HSPA Stringent DCH & HSPA Stringent bi-level HSPA Tolerant Combination 2: DCH & HSPA Stringent & Stringent bi-level HSPA Tolerant

For more AAL2 VCC combinations, see WCDMA RAN ATM Transport.

g
7

Note that ATM part is IPA-RNC specific. There is no special handling in transport area for mcRNC.

Configure the following WCEL parameter. 1. Select Edit parameters from the WCEL object. 2. Under the Packet Scheduler tab, set the value of HSPAQoSEnabled (HSPA QoS enabled) management parameter that activates the CS Voice over HSPA feature. This can be performed by setting the parameter to HSPA CS Voice is in use or HSPA streaming and CS voice are in use values.

g
3.

Note that before setting the HSPAQoSEnabled parameter to HSPA streaming and CS voice are in use value, the RAN1004: Streaming QoS for HSPA feature needs to be activated. Under the Admission Control tab, set the PtxTargetTotMin (Minimum value for dynamic total tx power) and PtxTargetTotMax (Maximum value for dynamic total tx power) parameters to optimize the performance of CS traffic.

Unlock the cell. Expected outcome RAN1689: CS Voice over HSPA feature has been activated.

2.11.1.2

Activating CS Voice over HSPA for I-HSPA Adapter solution


In I-HSPA Adapter there is no need to activate feature licenses. Steps

g
1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the I-HSPA Adapter.

88

Id:0900d8058090d76c Confidential

DN0988674

Activating and Verifying RU20 Features

Configure the following RNPS parameter. 1. Select Edit parameters from the drop-down menu of RNPS object. If there is no RNPS object, create it. 2. Under the Packet Scheduler tab, go to QoSPriorityMapping (QoS Priority Mapping) list and set the value of PriForConvOnHSPA (Priority for conversational on HSPA) parameter.

g
4

For conversational services set the priority lower than the priority set for SRBs, but higher than the priority set for PS streaming services.

Configure the following RNHSPA parameter. 1. Select Edit parameters from the RNHSPA object. 2. Check if the use of HSPA for CS voice service is ENABLED with the following parameters: Under the Packet Scheduler tab, set the EDCHQOSClasses: 05 (E-DCH QoS classes: CS voice ) parameter to enabled. Under the Admission Control tab, set the HSDSCHQoSclasses: 05 (HS-DSCH QoS classes: CS Voice) parameter to enabled. Under the Admission Control tab, set the FDPCHSetupEC:05 (FDPCH Setup based on Establishment Cause: Emergency Call) parameter to disabled so that SRB is mapped to HSPA.

5 6

Lock the cell. Configure the following WCEL parameter. 1. Select Edit parameters from the drop-down menu of WCEL object. 2. Under the Packet Scheduler tab, set the value of HSPAQoSEnabled (HSPA QoS enabled) management parameter that activates the CS Voice over HSPA feature. This can be performed by setting the parameter to HSPA CS Voice is in use or HSPA streaming and CS voice are in use values.

g
3.

Note that before setting the HSPAQoSEnabled parameter to HSPA streaming and CS voice are in use value, the RAN1004: Streaming QoS for HSPA feature needs to be activated. Under the Admission Control tab, set the PtxTargetTotMin (Minimum value for dynamic total tx power) and PtxTargetTotMax (Maximum value for dynamic total tx power) parameters to optimize the performance of CS traffic.

Unlock the cell. Expected outcome RAN1689: CS Voice over HSPA feature has been activated.

DN0988674

Id:0900d8058090d76c Confidential

89

Activating and Verifying RU20 Features

2.11.2

Verifying CS Voice over HSPA


Purpose Follow the procedure below to verify that the activation of the RAN1689: CS Voice over HSPA feature has been successful. Steps

1 2 3

Open the Application Launcher. Make several AMR voice calls. Check if the HS-DSCH/E-DCH is allocated for the AMR calls.

90

Id:0900d8058090580d Confidential

DN0988674

Activating and Verifying RU20 Features

2.11.3

Deactivating CS Voice over HSPA


Purpose Follow the procedure below to deactivate the feature. Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

3 4

Lock the cell. Configure the following WCEL parameter. 1. Select Edit parameters from the WCEL object. 2. Under the Packet Scheduler tab, switch the HSPAQoSEnabled (HSPA QoS enabled) management parameter to the value that disables CS Voice over HSPA feature.

5 6

Unlock the cell. Set the feature state to OFF. for IPA-RNC: ZW7M: FEA=1477:OFF; for mcRNC: set license feature-mgmt id 0000001477 feature-admin-state off

Expected outcome The RAN1689: CS Voice over HSPA feature is deactivated. Further Information There is no need to restart the RNC/I-HSPA Adapter after deactivating the feature.

DN0988674

Id:0900d8058090580b Confidential

91

Activating and Verifying RU20 Features

2.12
2.12.1

Activating RAN1758: Multiple BSIC Identification


Activating Multiple BSIC Identification
Purpose Follow the procedure below to activate the RAN1758: Multiple BSIC Identification feature. For more information on the feature, see the RAN1758: Multiple BSIC Identification Feature Description in WCDMA RAN, Rel. RU20, Feature Descriptions. Before you start Before activating RAN1758: Multiple BSIC identification feature, make sure that WCDMA - GSM Inter-system handover is activated and operational. Steps

1 2

Open the OMS Element Manager. Go to Tree View: Configuration Management j Network Topology j Tree View

Configure RNMOBI object. Select Edit parameters from the RNMOBI object. Set the Multiple BSIC identification, by configuring the MultipleBSICIdent parameter to value ON.

Configure FMCG object. Select Edit parameters from the FMCG object. Set the Maximum BSIC identification time, by configuring the MaxBSICIdentTime parameter value. Parameter must be set to value greater than zero. Expected outcome RAN1758: Multiple BSIC identification feature is activated in the RNC. Further information After activating the feature there is no need to restart RNC or BTS.

92

Id:0900d80580918587 Confidential

DN0988674

Activating and Verifying RU20 Features

2.12.2

Verifying Multiple BSIC Identification


Purpose Follow the procedure below to verify that the activation of the RAN1758: Multiple BSIC identification feature has been successful. Steps

Start the 1010 Inter System Handover measurement using Management application in RNC Element Manager. After failed inter-system handover attempt and after the measurement data is collected, use the RNW Measurement Presentation GUI to check if the following counters: M1010C229 INTER SYSTEM HO ATTEMPTS FOR M1010C230 INTER SYSTEM HO ATTEMPTS FOR M1010C231 INTER SYSTEM HO ATTEMPTS FOR M1010C232 INTER SYSTEM HO ATTEMPTS FOR 2ND BEST CELL FOR 3RD BEST CELL FOR 2ND BEST CELL FOR 3RD BEST CELL FOR RT RT NRT NRT

has a value greater than 0.

DN0988674

Id:0900d8058081c8ab Confidential

93

Activating and Verifying RU20 Features

2.12.3

Deactivating Multiple BSIC Identification


Purpose Follow the procedure below to deactivate the feature. Steps

1 2

Open the OMS Element Manager. Go to Tree View: Configuration Management j Network Topology j Tree View

Configure RNMOBI object. Select Edit parameters from the RNMOBI object. Set the MultipleBSICIdent parameter to value OFF. Further information After deactivating the feature there is no need to restart RNC or BTS. Expected outcome The RAN1758: Multiple BSIC identification feature is deactivated.

94

Id:0900d805809061c8 Confidential

DN0988674

Activating and Verifying RU20 Features

2.13
2.13.1

RAN1906: Dual-Cell HSDPA 42Mbps (On Top)


Activating Dual-Cell HSDPA 42Mbps (On Top)
Purpose Follow the procedure below to activate the RAN1906: Dual-Cell HSDPA 42Mbps feature. For more information on the feature, see the RAN1906: Dual-Cell HSDPA 42Mbps feature description in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature.

This feature is supported also with 2+2+2+2+2+2 (six sector) configuration when all 12 cells are in the same Local Cell Group (LCG) and the System Module/Radio Modules are of release 2. In this configuration the HSPA is processed within one system module. Second system module can be added to increase the R99 capacity. BTS restart is needed in case LCG commissioning is changed. For more information on LCG commissioning, see Dimensioning WCDMA RAN: Flexi BTS Baseband and Dimensioning WCDMA RAN: Ultra BTS Baseband. This feature belongs to application software and is under license key management. Make sure you have a valid license installed. For more information on licensing, see Licensing. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M: FEA=1686:ON; for mcRNC: set license feature-mgmt id 0000001686 feature-admin-state on

RAN1906: Dual-Cell HSDPA 42Mbps feature needs the following features to be activated before it can be enabled: RAN826: HSUPA (required in the primary cell) RAN852: HSDPA 15 Codes RAN1034: Shared HSDPA scheduler for baseband efficiency RAN1258: HSDPA 14 Mbps per User RAN1638: Flexible RLC

Use of 64QAM modulation requires RAN1643: HSDPA 64QAM feature. With RAN1643, it is recommended to configure at least two HS-SCCH codes in each cell to allow more flexibility to the scheduler. With RAN1686: HSPA 72 Users Per Cell, it is recommended to configure maximum amount of HS-SCCH codes to each cell because the additional HS-SCCH codes are used only in case code multiplexing is needed (otherwise same code tree branch used for HS-PDSCH transmission).

w g
DN0988674

Note that the DC-HSDPA must be activated in both cells of the DC-HSDPA cell pair. Note that setting of the HSPDSCHMarginSF128 and HSPDSCHCodeSet parameters is not required for activating the RAN1906: Dual-Cell HSDPA 42Mbps feature. However,

Id:0900d8058090d778 Confidential

95

Activating and Verifying RU20 Features

setting of those parameters is needed to maximize the DL throughput and to reach the 42 Mbps peak data rate. Steps 1 2 Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC. 3 Configure the following RNFC parameters. 1. Select Edit parameters from the RNFC object. 2. Under the Handover Control tab, set the HSDPAMobility (Serving HS-DSCH cell change and SHO on/off switch) parameter to Enabled (1). 3. Under the Admission Control tab, set the FRLCEnabled (Flexible RLC Enabled) parameter to Enabled (1). 4 Configure the following WBTS parameters. 1. Select Edit parameters from the WBTS object. 2. Under the Admission Control tab, set the HSDPA14MbpsPerUser (HSDPA14MbpsPerUser) parameter to Enabled (1). 5 6 Lock the cell. Configure the following WCEL parameters. 1. Select Edit parameters from the WCEL object. 2. Under the Admission Control tab, set the HSDPAenabled (HSDPA enabled) parameter to Enabled (1). 3. Under the Packet Scheduler tab, set the HSUPAEnabled (HSUPA enabled) parameter to Enabled (1). 4. Ensure that HS-PDSCH 15 codes is available in order to maximize the cell throughput: HSPDSCHCodeSet (HS-PDSCH code set) contains 5, 8, 10, 12, 14, and 15 codes Under the Admission Control tab, set the HSPDSCHMarginSF128 (HS-PDSCH code upgrade margin for SF128 codes) parameter to value 0 or any other value greater than 0, which makes 15 codes for HS-PDSCH available for both cells.

Setting of this parameter is needed in order to maximize the cell throughput. 5. Under the Packet Scheduler tab, set the HSPAQoSEnabled (HSPA QoS enabled) parameter to the same value in both cells of the DC HSDPA cell pair. 6. Under the General tab, set the Tcell (Frame timing offset of a cell) parameter to the same value in both cells of DC-HSDPA cell pair. Any value within the range can be used.

96

Id:0900d8058090d778 Confidential

DN0988674

Activating and Verifying RU20 Features

In order to support 2+2+2+2+2+2 configuration (in RU30) all 12 cells must be in single LCG and Rel2 BB and Rel2 RF must be used. 7. Under the Admission Control tab, set the SectorID (Sector Identifier) parameter value to the same value in both cells of the DC-HSDPA cell pair. The value can vary between 1 and 12. 8. Under the Handover Control tab, configure the UARFCN (UTRA Absolute Radio Frequency Channel Number) parameter. Note that the DC-HSDPA cell must have adjacent (not the same) frequencies within the same frequency band. 9. Under the Handover Control tab, define the DCellHSDPAFmcsId (DC HSDPA FMCS Identifier) parameter. 10. Under the Packet Scheduler tab, set the DCellHSDPAEnabled (DC HSDPA Enabled) parameter to Enabled (1).

Configure Dual-Cell in the BTS. During BTS commissioning some restrictions needs to be followed: Release 2 hardware (Flexi Rel2 or Ultra EUBB) is required LCG configuration needs to be performed: for RU20 EP1 release: one LCG can handle 6 cells => 3 x DC-HSDPA cell pairs for RU30: one LCG can handle 12 cells (Rel2 BB and Rel2 RF must be used) minimum 2 cells (adjacent frequencies) for sector is configured shared scheduler is activated (It is not needed in RU30)

Unlock the cell. Expected outcome Feature RAN1906: Dual-Cell HSDPA 42Mbps has been activated in the RNC.

DN0988674

Id:0900d8058090d778 Confidential

97

Activating and Verifying RU20 Features

2.13.2

Verifying Dual-Cell HSDPA 42Mbps


Purpose Follow the procedure below to verify that the activation of the RAN1906: Dual-Cell HSDPA 42Mbps feature has been successful. Before you start

Note that the RNC verifies if the Local Cells in the BTS support the DC HSDPA configuration (which has been configured in the RNW database). If DC HSDPA is enabled in the cell, but the Local Cell is not Multi Cell Capable, the RNC sets an 7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG (Multi Cell operation not available) alarm. There is also the 3325 INCONSISTENCY IN CONFIGURATION PARAMETERS RNC-specific alarm, which is related to the 7795 alarm and one instance of it is activated when one or more cells in a certain RNC has inconsistency in high peak rate HSPA configuration. Steps

Perform the RRC connection setup with a Rel-8 UE that supports Dual-Cell HSDPA. Open the RNW measurement management application from Application Launcher. Use the RNW measurement management application to start measurements M1005 and M1006 Traffic with 15 minute interval. Alternatively the measurement can be started using NetAct Administration of Measurements Application. Wait until the measurement interval starts.

After the measurement data has been collected, use the RNW Measurement presentation GUI to check if the following counters have a value greater than 0. M1005C252 - MAC-D SETUP ATTEMPT FOR DC-HSDPA M1005C253 - SUCCESSFUL MAC-D SETUP FOR DC-HSDPA M1005C254 - FAILED MAC-D SETUP FOR DC-HSDPA M1006C209 - RB SETUP ATTEMPT FOR DC-HSDPA M1006C210 - SUCCESSFUL RB SETUP FOR DC-HSDPA M1006C211 - RB SETUP FAIL FOR DC-HSDPA DUE TO NO REPLY M1006C212 - RB SETUP FAIL FOR DC-HSDPA DUE TO UE NACK

Expected outcome The approximate throughput is 42 Mbit/s. The RAN1906: Dual-Cell HSDPA 42Mbps feature has been activated successfully.

98

Id:0900d80580812f41 Confidential

DN0988674

Activating and Verifying RU20 Features

2.13.3

Deactivating Dual-Cell HSDPA 42Mbps


Purpose Follow the procedure below to deactivate the RAN1906: Dual-Cell HSDPA 42Mbps feature. Steps

1 2

Open the OMS Element Manager. Go to the Tree View. Expand the topology tree of the RNC.

3 4

Lock the cell. Configure the WCEL object. Set the DCellHSDPAEnabled (DC HSDPA Enabled) parameter to Disabled (0).

5 6

Unlock the cell. Set the feature state to OFF. for IPA-RNC: ZW7M: FEA=1686:OFF; for mcRNC: set license feature-mgmt id 0000001686 feature-admin-state off

Expected outcome The RAN1906: Dual-Cell HSDPA 42Mbps feature has been deactivated.

DN0988674

Id:0900d8058090e57f Confidential

99

Activating and Verifying RU20 Features

2.14
2.14.1

Activating RAN2067: LTE Interworking


Activating LTE Interworking
Purpose Follow the procedure below to activate the RAN2067: LTE Interworking feature. For more information on the feature, see the RAN2067: LTE interworking feature description in WCDMA RAN, rel. RU20, Feature Descriptions. Before you start Restart of the RNC and the BTS is not required after activation of this feature.

Before activation of this feature create and configure the ADJL and HOPL objects. If the ADJL and HOPL objects are not created, the SIB19 is not transmitted. The RAN2067: LTE Interworking is controlled by the license key Cell Reselection to LTE. This is a long-term capacity license. Capacity license stands for the number of cells. For IPA-RNC and mcRNC make sure the license is valid. For information on managing licenses, see Licensing. For I-HSPA Adapter go directly to the first step.

The feature code for this feature is 1755. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M:FEA=1755:ON; for mcRNC: set license feature-mgmt id 0000001755 feature-admin-state on

Steps 1 2 3 4 Open the OMS Element Manager. Go to Topology and expand the ROOT directory. Expand the RNC object and then the WBTS object. Configure the WCEL object: 1. Right-click on the WCEL object and select Edit parameters. 2. Set the LTE Cell Reselection parameter to Enabled. Expected outcome The RAN2067: LTE Interworking feature has been activated in the network element. After activating the feature, there is no need to reset the network element.

100

Id:0900d8058092ce3d Confidential

DN0988674

Activating and Verifying RU20 Features

2.14.2

Verifying LTE Interworking


Purpose Follow the procedure below to verify that the activation of the RAN2067: LTE Interworking feature has been successful. Before you start The RAN2067: LTE Interworking feature uses system information block 19 (SIB19), which contains information on neighboring evolved UTRAN (E-UTRAN) cells, thus enabling the UE cell reselection procedure to the E-UTRAN. The presence of SIB19 on the broadcast control channel (BCCH) indicates that the RAN2067: LTE Interworking feature is active in the cell within the UTRAN. For end-to-end verification of the RAN2067: LTE Interworking feature, the LTE network is required to validate if the UE performed the cell reselection to LTE procedure successfully, and if the UE is able to set up a call in the LTE system. From the RNC perspective the following steps can be verified: Preconditions The cell is set up. The Cell Reselection to LTE license is active in the IPA-RNC and mcRNC. Steps

Activate the RAN2067: LTE Interworking feature (see Activating LTE Interworking). Expected outcome The RNC sends the NBAP: SYSTEM INFORMATION UPDATE message, with SIB19 included, to the BTS. SIB19 is included in the SIBs being broadcast in the cell. The RAN2067: LTE Interworking feature has been activated successfully in the RNC.

DN0988674

Id:0900d8058092dc56 Confidential

101

Activating and Verifying RU20 Features

2.14.3

Deactivating LTE Interworking


Purpose Follow this procedure to deactivate the RAN2067: LTE Interworking feature. Steps

1 2 3 4

Open the OMS Element Manager. Go to Topology and expand the ROOT directory. Expand the RNC object and then the WBTS object. Configure the WCEL object: 1. Right-click on the WCEL object and select Edit parameters. 2. Set the LTE Cell Reselection parameter to Disabled.

Set the feature state to OFF using the following command: for IPA-RNC: ZW7M:FEA=1755:OFF; for mcRNC: set license feature-mgmt id 0000001755 feature-admin-state off

Expected outcome After deactivation of the LTE Interworking feature, the RNC sends the NBAP: SYSTEM INFORMATION UPDATE message, without SIB19 included, to the BTS. SIB19 is removed from the SIBs being broadcast in the cell. The RAN2067: LTE Interworking feature has been deactivated in the network element.

102

Id:0900d8058092dc58 Confidential

DN0988674

Activating and Verifying RU20 Features

2.15
2.15.1

Activating RAN2176: LTE PS Handover


Activating LTE PS Handover
Purpose Follow the procedure below to activate the RAN2176: LTE PS Handover feature. For more information on the feature, see the RAN2176: LTE PS Handover feature description in WCDMA RAN, Rel. RU20, Feature Descriptions. Before you start Restart of the RNC and the BTS is not required after activation of this feature. The RAN2176: LTE PS Handover feature is controlled by the license key LTE PS Handover and SRVCC. This is a long-term capacity license. Capacity license refers to the number of cells. For information on managing licenses, see Licensing. For I-HSPA Adapter go directly to the first step.

The feature code for this feature is 1756. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M:FEA=1756:ON; for mcRNC: set license feature-mgmt id 0000001756 feature-admin-state on

Steps 1 2 3 4 Open the OMS Element Manager. Go to Topology and expand the ROOT directory. Expand the RNC object and then the WBTS object. Configure the WCEL object: 1. Right-click on the WCEL object and select Edit parameters. 2. Set the Incoming ISHO from LTE parameter to Enabled. Expected outcome The RAN2176: LTE PS Handover feature has been activated in the RNC. After activating the feature, there is no need to reset the RNC.

DN0988674

Id:0900d8058092ce3f Confidential

103

Activating and Verifying RU20 Features

2.15.2

Verifying LTE PS Handover


Purpose Follow the procedure below to verify that the activation of the RAN2176: LTE PS Handover feature has been successful. Steps

Start the M1009 L3 Relocation Signaling measurement using the RNW measurement management application in OMS element manager. For more information on starting the measurements, see Management of basic RNW measurements and Starting radio network measurements in Managing and viewing RNC measurements.

2 3 4

Wait until the measurement period starts and make a PS call from LTE. Trigger an inter-system handover from LTE to UTRAN. Check that the PS call continues uninterrupted during the inter-system handover from LTE to UTRAN. After the measurement data has been collected, use the RNW measurement presentation GUI to check that the M1009C285 LTE PS HHO IN COMPLETE counter has a value greater than zero. Expected outcome The RAN2176: LTE PS Handover feature has been activated successfully in the RNC.

104

Id:0900d8058092d2a7 Confidential

DN0988674

Activating and Verifying RU20 Features

2.15.3

Deactivating LTE PS Handover


Purpose Follow this procedure to deactivate the RAN2176: LTE PS Handover feature. Steps

1 2 3 4

Open the OMS Element Manager. Go to Topology and expand the ROOT directory. Expand the RNC object and then the WBTS object. Configure the WCEL object: 1. Right-click on the WCEL object and select Edit parameters. 2. Set the Incoming ISHO from LTE parameter to Disabled.

Set the feature state to OFF using the following command: for IPA-RNC: ZW7M:FEA=1756:OFF; for mcRNC: set license feature-mgmt id 0000001756 feature-admin-state off

Expected outcome The RAN2176: LTE PS Handover feature has been deactivated in the RNC.

DN0988674

Id:0900d8058092d2a9 Confidential

105

Activating and Verifying RU20 Features

2.16
2.16.1

Activating RAN2289 Blind IFHO in RAB Setup Phase


Activating Blind IFHO in RAB Setup Phase
Purpose Follow the procedure below to activate the RAN2289: Blind IFHO in RAB Setup Phase feature. For more information on the feature, see the RAN2289: Blind IFHO in RAB Setup Phase Feature Description in WCDMA RAN, Rel. RU20, Feature Descriptions. Before you start Note that this feature is under the same license as feature RAN2172: Multi Band Load Balancing. For information on managing licenses, see Licensing. Steps

1 2

Open the OMS Element Manager. Go to Tree View: Expand the topology tree of the RNC.

Configure WCEL parameters For each cell where the Blind IFHO in RAB Setup Phase can be started, configure the following WCEL parameters: MBLBRABSetupEnabled parameter is configured to value Enabled. MBLBRABSetupMultiRAB parameter is configured appropriately. This parameter defines if Blind IFHO in AMR RAB setup for Multi RAB is enabled when UE is in Cell_FACH/Cell_PCH state or when UE is in Cell_DCH state or when UE is in Cell_DCH/Cell_FACH/Cell_PCH state). RACHInterFreqMesQuant is configured appropriately. Set the parameter value to RsCp for those cells where at least for one ADJI-neighbor cell the BlindHOTargetCell parameter is set to value Enabled in next step. BlindHORSCPThrTarget parameter is configured appropriately. If the Multi-Band Load Balancing is not to be done from the cell, based on target cell measurement, set the parameter to the highest value.

Configure ADJI parameters For the cells configured in step 3 Configure WCEL parameters, define those Intra-RNC inter-frequency neighbor cells that can be target cells for Blind IFHO in RAB Setup Phase by configuring the BlindHOTargetCell parameter to the value Enabled.

Under one WCEL it is possible to configure only one ADJI-neighbor/per frequency with BlindHOTargetCell configured as status Enabled.

106

Id:0900d80580937c12 Confidential

DN0988674

Activating and Verifying RU20 Features

Configure HOPI parameters. For the ADJI-neighbor cells configured in step 4 Configure ADJI parameters, configure the BlindHORSCPThr parameter.

Configure PFL parameters. Configure the PFLIdentifier parameter, BlindHORSCPThrAbove parameter, BlindHORSCPThrBelow parameter and LaySelWeightRsCp parameter. If LaySelWeightRsCp parameter value is set to bigger than zero, also define: The RSCP value under which the UE is to be transferred to lower frequency band with BlindHORSCPThrBelow parameter The RSCP value above which the UE is to be transferred to higher frequency band with BlindHORSCPThrAbove parameter.

Configure the LaySelWeightPrefLayer parameter, if it is set to value greater than zero, then define the preferred frequency band with PreferBandForLayering parameter, see step 7 Configure RNMOBI parameters for details. Configure LaySelWeightPrefLayer parameter, if it is set to value greater than zero, then define the preferred layer for different UE capability and service combinations. The desired frequency layer on desired frequency band is configured with PFLCSHSAMR parameter. CS Voice over HSPA capable UEs with AMR or other CS RAB are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLCSHSAMRNRT. CS Voice over HSPA capable UEs with AMR or other CS RAB + PS NRT and/or PS Streaming multi RAB (s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLCSHSNRT parameter. CS Voice over HSPA capable UEs with PS NRT RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLCSHSStr parameter. CS Voice over HSPA capable UEs with PS Streaming and PS NRT multi RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLDCHSDAMR parameter. DC HSDPA capable UEs with AMR or other CS RAB are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLDCHSDAMRNRT parameter. DC HSDPA capable UEs with AMR or other CS RAB and PS NRT and/or PS Streaming multi RAB (s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLDCHSDNRT parameter. DC HSDPA capable UEs with PS NRT RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLDCHSDStr parameter. DC HSDPA capable UEs with PS Streaming and PS NRT multi RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLMIMOAMR parameter. MIMO capable UEs with AMR or other CS RAB are directed to that frequency band and layer.

DN0988674

Id:0900d80580937c12 Confidential

107

Activating and Verifying RU20 Features

The desired frequency layer on desired frequency band is configured with PFLMIMOAMRNRT parameter. MIMO capable UEs with AMR or other CS RAB and PS NRT and/or PS Streaming multi RAB (s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLMIMONRT parameter. MIMO capable UEs with PS NRT RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLMIMOStr parameter. MIMO capable UEs with PS Streaming and PS NRT multi RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFL64QAMAMR parameter. HSDPA 64QAM capable UEs with AMR or other CS RAB are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFL64QAMAMRNRT parameter. HSDPA 64 QAM capable UEs with AMR or other CS RAB + PS NRT and/or PS Streaming multi RAB (s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFL64QAMNRT parameter. HSDPA 64 QAM capable UEs with PS NRT RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFL64QAMStr parameter. HSDPA 64 QAM capable UEs with PS Streaming and PS NRT multi RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLFDPCHAMR parameter. F-DPCH capable UEs with AMR or other CS RAB are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLFDPCHAMRNRT parameter. F-DPCH capable UEs with AMR or other CS RAB and PS NRT and/or PS Streaming multi RAB (s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLFDPCHNRT parameter. F-DPCH capable UEs with PS NRT RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLFDPCHStr parameter. F-DPCH capable UEs with PS Streaming + PS NRT multi RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLHSPAAMR parameter. HSPA capable UEs with AMR or other CS RAB are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLHSPAAMRNRT parameter. HSPA capable UEs with AMR or other CS RAB and PS NRT and/or PS Streaming multi RAB (s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLHSPANRT parameter. HSPA capable U's with PS NRT RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLHSPAStr parameter. HSPA capable UEs with PS Streaming and PS NRT multi RAB(s) are directed to that frequency band and layer.

108

Id:0900d80580937c12 Confidential

DN0988674

Activating and Verifying RU20 Features

The desired frequency layer on desired frequency band is configured with PFLHSDPAAMR parameter. HSDPA capable UEs with AMR or other CS RAB are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLHSDPAAMRNRT parameter. HSDPA capable UEs with AMR or other CS RAB + PS NRT and/or PS Streaming multi RAB (s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLHSDPANRT parameter. HSDPA capable UEs with PS NRT RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLHSDPAStr paramter. HSDPA capable UEs with PS Streaming and PS NRT multi RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLR99AMR parameter. R99 capable UEs with AMR or other CS RAB are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLR99AMRNRT parameter. R99 capable UEs with AMR or other CS RAB and PS NRT and/or PS Streaming multi RAB (s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLR99NRT parameter. R99 capable UEs with PS NRT RAB(s) are directed to that frequency band and layer. The desired frequency layer on desired frequency band is configured with PFLR99Str parameter. R99 capable UEs with PS Streaming and PS NRT multi RAB(s) are directed to that frequency band and layer.

Attach the PFL object to appropriate cells with PFLIdentifier parameter. There can be as many PFL object as needed for using different settings in different areas. 7 Configure RNMOBI parameters Configure PreferBandForLayering parameter. If value of the parameter LaSelWeightBand is set to value greater than zero in step 6 Configure PFL parameters., then define the preferred frequency band with PreferBandForLayering parameter. Expected outcome RAN2289: Blind IFHO in RAB Setup Phase feature is activated in the RNC. Further information After activating the feature there is no need to restart RNC or BTS.

DN0988674

Id:0900d80580937c12 Confidential

109

Activating and Verifying RU20 Features

2.16.2

Verifying Blind IFHO in RAB Setup Phase


Purpose Follow the procedure below to verify that the activation of the RAN2289: Blind IFHO in RAB Setup Phase feature has been successful. Steps

Use RNW Measurement Management application in the OMS Element Manager to start measurements M1006 Traffic with 15 minute interval. Alternatively the measurement can be started using NetAct Administration of Measurements Application. Make a call with a UE in a WCEL where the RAN2289: Blind IFHO in RAB Setup Phase feature is activated and suitable Blind IFHO target cell is free to UE. Check that the value of the following counters are incremented M1006C234 RB SETUP ATTEMPT WITH BLIND HO M1006C235 RB SETUP SUCCESSFUL WITH BLIND HO

110

Id:0900d805809363bc Confidential

DN0988674

Activating and Verifying RU20 Features

2.16.3

Deactivating Blind IFHO in RAB Setup Phase


Purpose Follow the procedure below to deactivate the RAN2289: Blind IFHO in RAB Setup Phase feature. Steps

1 2

Open the OMS Element Manager. Go to Tree View: Expand the topology tree of the RNC.

Configure WCEL parameter. Set the MBLBRABSetupEnabled parameter to value Disabled. Further information After deactivating the feature there is no need to restart RNC or BTS. Expected outcome The RAN2289: Blind IFHO in RAB Setup Phase feature is deactivated.

DN0988674

Id:0900d805809363be Confidential

111

Activate and verify transmission and transport features

Activating and Verifying RU20 Features

3 Activate and verify transmission and transport features


3.1 Activating RAN74, RAN1634, RAN1449, and RAN1633: IP Based Iub and Dual Iub
Activating IP based Iub for Flexi WCDMA BTS
Purpose Follow the procedure below to activate feature RAN74: IP based Iub for Flexi WCDMA BTS. For more information on the feature, see RAN74: IP based Iub for Flexi WCDMA BTS in WCDMA RAN, rel. RU10, feature descriptions. Exemplary reference configurations using this feature are presented in Configuring WCDMA RAN transport document. The configuration examples in the activation instructions use the IP addressing presented in figure IP-based Iub connectivity for Flexi WCDMA BTS.

3.1.1

Figure 7

IP-based Iub connectivity for Flexi WCDMA BTS

Before you start Enabling IP-based Iub requires the following interface units in the RNC: in RNC2600, the NPGE Gigabit Ethernet interface unit - RAN77: RNC Ethernet Physical Interface feature in RNC196/450, IP-interface upgrade - RAN1225: IP Interface Upgrade for RNC196 and RNC450 feature

In the Flexi WBTS, an FTIA, FTIB, FTJA, FTFB, or FTLB hybrid PDH/Ethernet transport sub-module is required. The feature is an optional application with a separate license control. This feature belongs to the application software. Before you activate the feature, make sure you have a valid license (a file including the feature information) installed. Before a licensed feature can be activated, the license must be transferred and installed in the

112

Id:0900d8058092ab88 Confidential

DN0988674

Activating and Verifying RU20 Features

Activate and verify transmission and transport features

RNC. For information on transferring the license to the RNC, see License management operations in RNC in WCDMA RAN license operation. 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/CONFIG/OFF). In new installations, the default state is OFF. When installing a new increment, the previously set state remains as the default. For the specific instructions on the license installation in the RNC, see W7L INSTALL OR UPDATE LICENCE in W7 - Licence and Feature Handling. For more information, see Licence-based feature management, W7 - Licence and Feature Handling, and License management principles. See also System Administration Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN . Use the ZW7 command to activate the license for the feature with feature code 1079. Note that the license is capacity based, and the measure of the capacity is the number of BTSs. If the IP-based Iub is not ON, the IP based route ID cannot be configured. RNW configuration has to be done according to the network plan. Configuration can be created by using either the Parameter editor or the RNW plan interface. The IP-layer configuration can be managed using the local MML interface or the IP plan interface from NetAct. The following parameters are related to this feature: IPNB parameters for IP Iub control plane connections: IPNBId WBTSId IPBasedRouteId MinSCTPPortIub NodeBIPAddress NBAPDSCP CNBAP SCTPPortNumberCNBAP DNBAPList DNBAP CControlPortID SCTPPortNumberDNBAP IubTransportMedia IPNBId IPBasedRouteId MinUDPPortIub DSCPMedDCH DSCPLow DSCPHigh DSCPMedHSPA HSDPAULCToDSCP

WBTS parameters for IP Iub user plane connections:

DN0988674

Id:0900d8058092ab88 Confidential

113

Activate and verify transmission and transport features

Activating and Verifying RU20 Features

HSUPADLCToDSCP ToAWEOffsetNRTDCHIP ToAWEOffsetRTDCHIP ToAWSOffsetNRTDCHIP ToAWSOffsetRTDCHIP

The parameters can be configured with the Parameter Editor. BTS parameters can be configured with the BTS Site Manager or NetAct. For more information about BTS parameters, see Plan Editor Flexi Transport Module Parameters. Restart of the WBTS is required after activation of this feature.

In case RNC and BTS are configured to the same Layer 2 broadcast domain(s) (for example to the same VLANs), the IP addressing used for the user plane traffic and BFD sessions termination requires a special emphasis. For more details, see T echnical Support Note, TN-RNC-SW-146 in NOLS. Steps

Configure the IP-based Iub in the RNC with the MML interface. If NPGEP unit is used, all physical connections must be plugged in during creation of IFGEx otherwise all the NPGEP units report a fault and NPGEP with any missing Ethernet connection restarts. If VLAN is used: a) Enable and check administrative status of IFGE0: ZQRN:NPGE,0:IFGE0:::::UP; ZQRI; b) Create a VLAN interface to the NPGE-0 unit. The VLAN name is 'VL1', VLAN ID is 2 (VLAN ID can have value between 2 to 4094), the VLAN is attached to the physical interface IFGE0. ZQRM:NPGE,0:VL1:2:IFGE0; c) Configure the IP address of the VLAN interface. ZQRN:NPGE,0:VL1:10.2.1.1,P:29:;

Pay attention to the IP address planning with the VLAN configuration at system level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option. If VLAN is not used: d) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; ZQRI:NPGE,0:; Proceed with the configuration for both cases: e) Configure the gateway for the NPGE to the external router: ZQKC:NPGE,0:10.3.1.0,30:10.2.1.2:LOG; f) Create a DSPM (DSCP to PHB mapping) profile for the Ethernet interface (IFGE0): Refer to the ZQ8B command in the MML manual. This is optional; also a default value can be used.

114

Id:0900d8058092ab88 Confidential

DN0988674

Activating and Verifying RU20 Features

Activate and verify transmission and transport features

g) Assign a DSPM profile to an IP interface in the NPGE by using the given profile ID or the default profile ID: ZQ8S:NPGE,0:IFGE0:ENA::; h) Check the internal IPoATM from the NPGE to ICSU: ZQMQ:ICSU,0::NPGE,0:::ALL; i) Configure the Iub control plane subnet for ICSU units: ZQMN:1:10.1.1.0,26:; ZQML:;

The system configures the MTU for ICSU IP over ATM interface to value 1472 for the automatically generated internal full mesh IPoA. The ICSU Iub IPoA interface MTU value should not be configured greater than 1472 in order to keep the SCTP layer fragmentation aligned with the BTS SCTP defragmentation functionality. If the MTU size on Iub is configured to be smaller than 1500, respectively the MTU size for ICSU unit has to be descreased (with the MML ZQRN command) to avoid fragmentation at NPGE. j) Configure the IP based route to the IFGE0 for the Iub. Enter values for the bandwidth allocation according to the transport network dimensioning plan: ZQRU:ADD:1,"IUBWBTS1":8000:500:100:100:ON; ZQRC:NPGE,0:IFGE0:IPV4=10.2.1.1:ID=1:; or in case VLAN is used: ZQRC:NPGE,0:VL1:IPV4=10.2.1.1:ID=1:;

Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. BFD configuration is an optional step. a) Configure the BFD profile: ZYGR:C:PROF=1,RXINT=500,TXINT=500,DMULT=2; b) Configure the BFD session between the RNC and BTS: ZYGS:C:NPGE,0,1,10.2.1.1,10.3.1.1:PROF=1,ALARM=OFF; c) Set the BFD session state to enabled and the alarm state to on when the BTS is integrated to the RNC: ZYGS:S:NPGE,0,1:ALARM=ON,MODE=0; Configure DCN for the RNC. For instructions on configuring RNC (OMU) for data communication network (DCN), see Configuring IP stack in OMU in Configuring IP connection for RNC.

Configure the IP-based Iub in the Parameter Editor. The system configures the static IP route in ICSU towards Control Plane Destination Address Iub. When the IPNB object is disconnected from the WBTS, the static IP route is deleted based on its ROUTE NUMBER. Do not delete the static IP route manually, as it may cause a situation where the ROUTE NUMBER which might be used by other manually created IP routes, is removed while the IPNB object is disconnected from the WBTS.

DN0988674

Id:0900d8058092ab88 Confidential

115

Activate and verify transmission and transport features

Activating and Verifying RU20 Features

a) Open the Parameter Editor. Go to Configuration Management j Network Topology j Tree view b) Create the IPNB object for the IP-based Iub control plane connections by selecting Topology j RNCxx j IPNB j Create j New IPNB. 1. Provide the IPNB with an object identifier. 2. Give BTS CP/UP 10.3.1.1 IP address as a Control Plane Destination Address Iub. 3. The IP Based Route Identification value is retrieved from the WBTS object once IPNB and WBTS are connected (when the IPNB ID is set in the WBTS and the corresponding IPNB exists in the system). 4. Configure minSCTPPort (Minimum SCTP port number). Make sure that the SCTP Port ID have a unique value. 5. In the D-NBAP List enter 1 for the Communication Control Port ID; the SCTP Port Number for D-NBAP is automatically calculated. c) Create or modify the WBTS object so that it contains the IPNB reference and IP Iub user plane configuration. Ensure that the IPNB is selected, the IP Based Route ID is given, and the Iub Transport media selection is IP Iub. 1. Configure IPNBId (IPNB object identifier) into the WBTS data. 2. Set the attributes related to IP-based Iub user plane correctly. Set IPBasedRouteIdIub so that it refers to the IP based route configured per MML ZQRU / ZQRC for the given BTS. In the example provided, value 1 is used. In the IubTransportMedia (Iub Transport Media Selection) parameter, check IP Iub only. The default values can be used for MinUDPPortIub, DSCPMedDCH, DSCPLow, DSCPHigh, DSCPMedHSPA, HSDPAULCToDSCP, HSUPADLCToDSCP, ToAWEOffsetNRTDCHIP, ToAWEOffsetRTDCHIP, ToAWSOffsetNRTDCHIP, and ToAWSOffsetRTDCHIP. 5 Configure the IP-based Iub in the Flexi WCDMA BTS. Please note that depending on the BTS software release (WN6.0 or WN6.0 On Top), the order of the steps might be different. a) Open the BTS Site Manager. b) Start TRS Commissioning.

g g

The selection of the transport mode (ATM Iub/IP Iub/Dual Iub) can be made only in the BTS Site Manager Commissioning Wizard, not in the Flexi TRS Manager. c) Enter the name and Id of the BTS. Enter the transport (TRS) and BTS IP address for DCN. d) Set Transport Mode to Iub IP and take Ethernet interface (EIF) in use. e) Configure the Transport Ethernet Interface IP address (use example value 10.3.1.1/30). With WN6.0 On Top, when using VLANs, leave the IP address field empty and add new VLAN, configure the IP address, enter the Committed information rate and select Enable QoS checkbox. f) Configure Quality of Service settings or use default values.

116

Id:0900d8058092ab88 Confidential

DN0988674

Activating and Verifying RU20 Features

Activate and verify transmission and transport features

g) With WN6.0 and earlier releases, if VLAN was configured in the RNC, take the VLAN in use and assign a VLAN Id. h) Configure Far end SCTP subnet and ensure that the RNC ICSU IP is included in the subnet. In the example provided, the ICSU control plane subnet in the RNC is 10.1.1.1/26. i) Configure Minimum SCTP Port and Minimum UDP Port. The value of Minimum SCTP Port has to match the value set previously using Parameter Editor. j) Fill in the values according to transport network planning for the CAC Committed Bit Rate, Signalling Bit Rate, and DCN Bit Rate. In the example provided, these are: 8 Mbit for CAC Committed Bit Rate, 100 kbit for Signalling, and DCN Bit Rate. k) Configure the BFD sessions to supervise the IP path to the RNC.

The BFD configuration is an optional step. It requires BFD session established in the RNC as instructed in step Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. l) Configure the synchronization source. m) Add the default gateway; ensure that the gateway is reachable given by the subnet mask in the Transport Ethernet Interface. In the example provided, the external router default gateway is 10.3.1.2.

A timing source is not automatically available for the IP Iub, and the synchronization source is provided by either a timing over packet master or Synchronous Ethernet. For more information, see Activating RAN1254: Timing over Packet for BTS Application SW and Activating RAN1708: BTS Synchronous Ethernet. Expected outcome The RAN74: IP based Iub for Flexi WCDMA BTS feature has been activated, and after the IPNB object creation NBAP/SCTP terminations are created at the RNC.

DN0988674

Id:0900d8058092ab88 Confidential

117

Activating and Verifying RU20 Features

3.1.2

Activating IP based Iub for UltraSite WCDMA BTS


Purpose Follow the procedure below to activate feature RAN1634: IP Based Iub for UltraSite WCDMA BTS. For more information on the feature, see RAN1634: IP Based Iub for UltraSite WCDMA BTS in WCDMA RAN, rel. RU10, feature descriptions. Exemplary reference configurations using this feature are presented in Configuring WCDMA RAN transport document. The configuration examples in the activation instructions use the IP addressing presented in figure IP-based Iub connectivity for UltraSite WCDMA BTS.

Figure 8

IP-based Iub connectivity for UltraSite WCDMA BTS

Before you start Enabling IP-based Iub requires the following interface units in the RNC: in RNC2600, the NPGE Gigabit Ethernet interface unit - RAN77: RNC Ethernet Physical Interface feature in RNC196/450, IP-interface upgrade - RAN1225: IP Interface Upgrade for RNC196 and RNC450 feature

In the UltraSite WBTS, the IFUH or AXCF (available in RU20) unit is required. This feature is an optional application with a separate license control and belongs to the application software. Before you activate the feature, make sure you have a valid license (a file including the feature information) installed. Before a licensed feature can be activated, the license must be transferred and installed in the 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/CONFIG/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 Licence-based feature management, W7 - Licence and Feature Handling, and License management principles. See also System Administration

118

Id:0900d8058084d91e Confidential

DN0988674

Activating and Verifying RU20 Features

Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN . Use the ZW7 command to activate the license for the feature with feature code 1294. Note that the license is capacity based, and the measure of the capacity is the number of BTSs. If the IP-based Iub is not ON, the IP based route ID cannot be configured. RNW configuration has to be carried out according to the network plan. Configuration can be done by using either the Parameter Editor, or the RNW plan interface. The IPlayer configuration can be managed using the local MML interface or the IP Plan interface from NetAct. The following parameters are related to this feature: IPNB parameters for IP Iub control plane connections: IPNBId WBTSId IPBasedRouteId MinSCTPPortIub NodeBIPAddress NBAPDSCP CNBAP SCTPPortNumberCNBAP DNBAPList DNBAP CControlPortID SCTPPortNumberDNBAP IubTransportMedia IPNBId IPBasedRouteIdlub MinUDPPortIub DSCPMedDCH DSCPLow DSCPHigh DSCPMedHSPA HSDPAULCToDSCP HSUPADLCToDSCP ToAWEOffsetNRTDCHIP ToAWEOffsetRTDCHIP ToAWSOffsetNRTDCHIP ToAWSOffsetRTDCHIP

WBTS parameters for IP Iub user plane connections:

The parameters can be configured with the Parameter Editor. BTS parameters can be configured with the AXC Manager or NetAct. For more information about BTS parameters, see Plan Editor AXC Parameters. Restart of the WBTS is required during activation of this feature.

DN0988674

Id:0900d8058084d91e Confidential

119

Activating and Verifying RU20 Features

In case RNC and BTS are configured to the same Layer 2 broadcast domain(s) (for example to the same VLANs), the IP addressing used for the user plane traffic and BFD sessions termination requires a special emphasis. For more details, see T echnical Support Note, TN-RNC-SW-146 in NOLS. Steps

Configure the IP-based Iub in the RNC with the MML interface. If NPGEP unit is used, all physical connections must be plugged in during creation of IFGEx otherwise all the NPGEP units report a fault and NPGEP with any missing Ethernet connection restarts. If VLAN is used: a) Enable and check administrative status of IFGE0: ZQRN:NPGE,0:IFGE0:::::UP; ZQRI; b) Create a VLAN interface to the NPGE-0 unit. The VLAN name is 'VL1', VLAN ID is 2 (VLAN ID can have value between 2 to 4094), the VLAN is attached to the physical interface IFGE0. ZQRM:NPGE,0:VL1:2:IFGE0; c) Configure the IP address of the VLAN interface. ZQRN:NPGE,0:VL1:10.2.1.1,P:29:;

Pay attention to the IP address planning with the VLAN configuration at system level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option. If VLAN is not used: d) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; ZQRI:NPGE,0:; Proceed with the configuration for both cases: e) Configure the gateway for the NPGE to the external router: ZQKC:NPGE,0:10.3.1.0,30:10.2.1.2:LOG; ZQKB:; f) Create a DSPM profile for the Ethernet interface (IFGE0): Refer to the ZQ8B command in the MML manual. This is optional; also a default value can be used. g) Assign a DSPM profile to an IP interface in the NPGE by using given profile ID or the default profile: ZQ8S:NPGE,0:IFGE0:ENA::; h) Check the internal IPoATM from the NPGE to ICSU: ZQMQ:ICSU,0::NPGE,0:::ALL; i) Configure the Iub control plane subnet for ICSU units: ZQMN:1:10.1.1.0,26:; ZQML:;

g
120

The system configures ICSU IP over ATM interface MTU to value 1472 for the automatically generated internal full mesh IPoA. The ICSU Iub IPoA interface MTU value should not be configured greater than 1472 in order to keep the SCTP layer frag-

Id:0900d8058084d91e Confidential

DN0988674

Activating and Verifying RU20 Features

mentation aligned with the BTS SCTP defragmentation functionality. If the MTU size on Iub is configured to be smaller than 1500, respectively the MTU size for ICSU unit has to be descreased (with the MML ZQRN command) to avoid fragmentation at NPGE. j) Create a static route from the ICSU to the NPGE as a gateway: ZQKC:ICSU,0:10.3.1.0,30:10.2.1.1:LOG; ZQKB:; k) Configure the IP based route to the IFGE0 for the Iub. Give values for the bandwidth allocation according to the transport network dimensioning plan: ZQRU:ADD:1,"IUBWBTS1":8000:500:100:100:ON; ZQRC:NPGE,0:IFGE0:IPV4=10.2.1.1:ID=1:; or in case VLAN is used: ZQRC:NPGE,0:VL1:IPV4=10.2.1.1:ID=1:; 2 Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. BFD configuration is an optional step. a) Configure the BFD profile: ZYGR:C:PROF=1,RXINT=500,TXINT=500,DMULT=2; b) Configure the BFD session between the RNC and BTS: ZYGS:C:NPGE,0,1,10.2.1.1,10.3.1.1:PROF=1,ALARM=OFF; c) Set the BFD session state to enabled and the alarm state to on when the BTS is integrated to the RNC: ZYGS:S:NPGE,0,1,:ALARM=ON,MODE=0; Configure DCN for the RNC. For instructions on configuring RNC (OMU) for DCN, see Configuring IP stack in OMU in Configuring IP connection for RNC. 4 Configure the IP-based Iub in the Parameter Editor. The system configures the static IP route in ICSU towards Control Plane Destination Address Iub. When the IPNB object is disconnected from the WBTS, the static IP route is deleted based on its ROUTE NUMBER. Do not delete the static IP route manually, as it may cause a situation where the ROUTE NUMBER which might be used by other manually created IP routes, is removed while the IPNB object is disconnected from the WBTS. a) Open the Parameter Editor. Go to Configuration Management j Network Topology j Tree view b) Create the IPNB object for the IP-based Iub control plane connections by selecting Topology j RNCxx j IPNB j Create j New IPNB. 1. Provide the IPNB with an object identifier. 2. Give BTS CP/UP 10.3.1.1 IP address as a Control Plane Destination Address Iub.

DN0988674

Id:0900d8058084d91e Confidential

121

Activating and Verifying RU20 Features

3. The IP Based Route Identification value is retrieved from the WBTS object once IPNB and WBTS are connected (when the IPNB id is set in the WBTS and the corresponding IPNB exists in the system). 4. Configure minSCTPPort (Minimum SCTP port number). Make sure that the SCTP Port ID have a unique value. 5. In the D-NBAP List, when using the IFUH, the Communitcation Control Port ID must be set for each WAM unit (D-NBAP is terminated in WAM units). When using AXCF unit, the only possible value for the communication control port is 1. After entering the communication control port, the SCTP Port Number for DNBAP is automatically calculated. c) Create or modify the WBTS object so that it contains the IPNB reference and IP Iub user plane configuration. 1. Configure IPNBId (IPNB object identifier) in the WBTS object data. 2. Set the attributes related to IP-based Iub user plane correctly. Set IPBasedRouteIdIub so that it refers to the IP based route configured for the given BTS. In the example value 1 is used. In the IubTransportMedia (Iub Transport Media Selection) parameter, check the IP Iub only. Default values can be used for MinUDPPortIub, DSCPMedDCH, DSCPLow, DSCPHigh, DSCPMedHSPA, HSDPAULCToDSCP, HSUPADLCToDSCP, ToAWEOffsetNRTDCHIP, ToAWEOffsetRTDCHIP, ToAWSOffsetNRTDCHIP, and ToAWSOffsetRTDCHIP. 5 Configure the IP-based Iub in the transport module of UltraSite WCDMA BTS (AXC). The transport mode is changed by downloading an XML configuration file with IP Iub settings in the AXC and activating it (for instructions, see Commissioning AXC with XML configuration file in Commissioning AXC). Note that the transport mode can also be changed with the AXC Manager, but this is supported only in a local connection with the AXC Manager. The amount of configured NBAP links should follow the UltraSite WCDMA BTS configuration. Please note that depending on the BTS software release (WN6.0 or WN6.0 On Top), the order of the steps might be different. a) Open the AXC Manager. b) Switch the transport mode to Iub IP in a local connection with the AXC Manager. Click Node j Switch Transport Mode and select Iub IP in the dialog window that opens. Click Switch to change the transport mode. c) Configure IFUH/AXCF interfaces. Select the interface in the hardware view. Take the IFUH/AXCF interface in use and modify Speed and Duplex if required. d) Configure transport addresses.

g g g

g
122

Transport address settings are needed for the IP Iub and synchronization. Click IP j Settings and select the Transport addresses tab.

Id:0900d8058084d91e Confidential

DN0988674

Activating and Verifying RU20 Features

Select the unit from the list and click Modify. Enter the Local IP Address and Netmask. Modify the bandwidth limit if needed, and take Virtual LAN (VLAN) in use if necessary. e) Configure IP Iub settings. Click IP j Settings, select the IP Iub tab, and click Modify. Define the following settings: Far End SCTP Address and Far End SCTP Subnet (this is the RNC ICSU subnet) Minimum SCTP Port: possible values range from 49152 to 65529. The value of Minimum SCTP Port has to match the value set previously using Parameter Editor. Note that the BTS is reset if you modify the value of Minimum SCTP Port. Minimum UDP Port: possible values range from 49152 to 63135. It is recommended not to change the value of Minimum UDP Port during the AXC operation so that no calls are lost. CAC Committed Bit Rate: possible values range from 0.5 to 100 Mbps in 0.5 Mbps steps. Signaling Bit Rate: possible values range from 50 to 1000 kbps in 50 kbps steps. DCN Bit Rate: possible values range from 50 to 1000 kbps in 50 kbps steps. Configure the BFD sessions to supervise the IP path to the RNC.

g
f)

The BFD configuration is an optional step. It requires BFD session established in the RNC as instructed in step Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. Configure IP routing Click IP j Settings, select Routing tab, select Display transport routing and add new routes by clicking Add. g) Click Activate BTS Settings in the Iub IP tab to activate the settings. h) Configure the Quality of Service settings. Click IP j Settings, select the Quality of Service tab, and click Modify Queue Weights and Modify Traffic Types. i) Configure other settings, such as synchronization and Management Protocol.

g g

A timing source is not automatically available for the IP Iub, and the synchronization source is provided by either a timing over packet master or Synchronous Ethernet. For more information, see Activating RAN1254: Timing over Packet for BTS Application SW and Activating RAN1708: BTS Synchronous Ethernet. For detailed instructions on configuring AXC, see Commissioning AXC. Expected outcome The RAN1634: IP based Iub for UltraSite WCDMA BTS feature has been activated, and during the IPNB object creation NBAP/SCTP terminations are created in the RNC.

DN0988674

Id:0900d8058084d91e Confidential

123

Activating and Verifying RU20 Features

3.1.3

Verifying IP based Iub for Flexi and UltraSite WCDMA BTS


Purpose Follow the procedure below to verify that the activation of the RAN74: IP based Iub for Flexi WCDMA BTS and RAN1634: IP based Iub for UltraSite WCDMA BTS features has been successful.

g
1 2 3 4

If the features are not working as expected, check the alarms for Ethernet/BFD related failures. Steps Open the Parameter Editor. Check the NBAP link states. Check whether the cell states are up and running. Perform the calls. Expected outcome IP-based Iub features RAN74 and RAN1634 have been activated successfully if the whole traffic can be carried over the IP transport.

124

Id:0900d8058084d9de Confidential

DN0988674

Activating and Verifying RU20 Features

3.1.4

Deactivating IP based Iub for Flexi and UltraSite WCDMA BTS


IP-based Iub is not deactivated separately for the Flexi and UltraSite WCDMA BTS. The IP Iub configuration can be changed to the Dual Iub or ATM Iub configuration by following relevant instructions. In this case the Iub transport and BTS configuration need to be changed accordingly.

DN0988674

Id:0900d8058084d9e1 Confidential

125

Activating and Verifying RU20 Features

3.1.5

Activating Dual Iub for Flexi WCDMA BTS


Purpose Follow the procedure below to activate feature RAN1449: Dual Iub for Flexi WCDMA BTS. With Dual Iub feature up and running the Iub Control Plane connections and User Plane connections for common channels, basic SRB on R99 DCH, and RT DCH bearers are always carried on top of the ATM transport. With the WBTS IubTransportMedia attribute, part of the call and traffic types can be configured to be carried on top of the IP transport. PS NRT DCH NRT HSDPA x x x x x x x x x x x x x x x NRT HSUPA Streaming HSDPA Streaming HSUPA

HSDPA non-realtime traffic offload HSPA non-realtime offload HSPA traffic offload PS non-realtime traffic offload Full PS traffic offload Table 10

Allowed combinations for transport bearers on IP transport network With the feature RAN1470: HSUPA 2ms TTI or RAN1201: Fractional DPCH (SRB on HSPA) Dual Iub allows also to separate the following traffic classes: SRB HSPA Associated DL SRB DCH

For more information on the feature, see RAN1449: Dual Iub for Flexi WCDMA BTS in WCDMA RAN, rel. RU10, feature descriptions. Exemplary reference configuration using this feature is presented in Dual Iub for combined E1 and DSL backhaul network in Configuring WCDMA RAN and I-HSPA Transport document. From the capacity dimensioning viewpoint, Dual Iub requires planning the capacity requirements separately for the ATM and the IP parts of the Iub. For more information on the dimensioning of the Iub interface, see Dimensioning WCDMA RAN. The configuration examples in the activation instructions use the IP addressing presented in figure Dual Iub connectivity for Flexi WCDMA BTS.

126

Id:0900d8058089bfa1 Confidential

DN0988674

Activating and Verifying RU20 Features

Figure 9

Dual Iub connectivity for Flexi WCDMA BTS

Before you start Enabling Dual Iub requires the following interface units in the RNC: in RNC2600, the NPGE Gigabit Ethernet interface unit - RAN77: RNC Ethernet Physical Interface feature in RNC196/450, IP-interface upgrade - RAN1225: IP Interface Upgrade for RNC196 and RNC450 feature the support of SDH interfaces by NIS1 or NPS1 interface units

In the Flexi WBTS, an FTIA, FTIB, FTJA, FTFB, or FTLB hybrid PDH/Ethernet transport sub-module is required. The feature RAN1449: Dual Iub for Flexi WCDMA BTS is an optional application controlled with a separate license. This feature belongs to application software. Before you activate the feature, make sure you have a valid license installed. Before a licensed feature can be activated, the license (a file including the feature information) must be transferred and installed in the 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/CONFIG/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 Licence-based feature management, W7 - Licence and Feature Handling, and License management principles. See also System Administration Principles in NetAct Product Documentation and Licensed sales items in RU20 in License management in WCDMA RAN . Use the ZW7 command to activate the license for the feature with feature code 1246. Note that the license is capacity based, and the measure of the capacity is the number of BTSs. If the Dual Iub feature is not ON, the IP based route ID cannot be configured. The count of Dual Iub WBTSs (the IP based route ID is defined and IubTransportMedia is HSPA) exceeding the capacity of Dual Iub is not allowed. RNW configuration is to be carried out according to the network plan. Configuration can be done by using either the Parameter Editor, or the RNW plan interface. IP-layer configuration can be managed using the local MML interface or the IP Plan interface from NetAct.

DN0988674

Id:0900d8058089bfa1 Confidential

127

Activating and Verifying RU20 Features

The following WBTS parameters for user plane connections carried on top of the IP transport are related to this feature: IubTransportMedia IPBasedRouteIdlub MinUDPPortIub DSCPMedDCH DSCPLow HSDPAULCToDSCP HSUPADLCToDSCP ToAWEOffsetNRTDCHIP

BTS parameters can be configured with the BTS Site Manager or NetAct. For more information about BTS parameters, see Plan Editor Flexi Transport Module Parameters. Restart of the WBTS is required after activation of this feature.

In case RNC and BTS are configured to the same Layer 2 broadcast domain(s) (for example to the same VLANs), the IP addressing used for the user plane traffic and BFD sessions termination requires a special emphasis. For more details, see T echnical Support Note, TN-RNC-SW-146 in NOLS. Steps

Configure the ATM resources for Iub control plane connections and user plane connections. a) Create the Physical Trail Termination Point: ZYDC:1:SET=1::; b) Create the ATM interface: ZLAC:1:UNI,1,:; c) Create the Access Profile for the ATM interface: ZLAF:1:8:14:E:;

Configure the IP layer resources for the Iub user plane. If NPGEP unit is used, all physical connections must be plugged in during creation of IFGEx otherwise all the NPGEP units report a fault and NPGEP with any missing Ethernet connection restarts. If VLAN is used: a) Enable and check administrative status of IFGE0: ZQRN:NPGE,0:IFGE0:::::UP; ZQRI; b) Create a VLAN interface to the NPGE-0 unit. The VLAN name is 'VL1', VLAN ID is 2 (VLAN ID can have value between 2 to 4094), the VLAN is attached to the physical interface IFGE0. ZQRM:NPGE,0:VL1:2:IFGE0; c) Configure the IP address of the VLAN interface. ZQRN:NPGE,0:VL1:10.2.1.1,P:29:;

128

Id:0900d8058089bfa1 Confidential

DN0988674

Activating and Verifying RU20 Features

Pay attention to the IP address planning with the VLAN configuration at system level. The sample IP addressing figures shown here depict the configuration with IP layer routing without the VLAN configuration option. If VLAN is not used: d) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; Proceed with the configuration for both cases: e) Configure the IP address for the NPGE GE interface: ZQRN:NPGE,0:IFGE0:10.2.1.1,:29:; f) Configure the gateway for the NPGE to the external router: ZQKC:NPGE,0:10.3.1.0,30:10.2.1.2:LOG; g) Create a DSPM profile for the Ethernet interface (IFGE0): Refer to the ZQ8B command in the MML manual. This is optional; also a default value can be used h) Assign a DSPM profile to an IP interface in the NPGE by using the given profile ID or the default profile: ZQ8S:NPGE,0:IFGE0:ENA::; i) Configure the IP based route to the IFGE0 for the Iub. Give values for the bandwidth allocation according to the transport network dimensioning plan: ZQRU:ADD:1,"IUBWBTS1":2000:500:100:100:ON; ZQRC:NPGE,0:IFGE0:IPV4=10.2.1.1:ID=1:; or in case VLAN is used: ZQRC:NPGE,0:VL1:IPV4=10.2.1.1:ID=1:;

Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. BFD configuration is an optional step. However, by configuring BFD session and binding it to the IP based route, IP path protection is ensured. a) Configure the BFD profile: ZYGR:C:PROF=1,RXINT=500,TXINT=500,DMULT=2; b) Configure the BFD session between the RNC and BTS and bind it to previously configured IP based route (ROUTE=IP based route ID): ZYGS:C:NPGE,0,1,10.2.1.1,10.3.1.1:PROF=1,ALARM=OFF,ROUTE=1; c) Set the BFD session state to enabled and the alarm state to on, when the BTS is integrated to the RNC: ZYGS:S:NPGE,0,1,:ALARM=ON,MODE=0;

Configure the Dual Iub in the Parameter Editor. a) Configure attributes related to the IP-based Iub user plane in the WCDMA BTS object. Set IPBasedRouteIdIub so that it refers to the IP based route configured for the given BTS. In the example provided, value 1 is used. IubTransportMedia should be configured according to the transport network planning. For example the NRT HSDPA and NRT HSUPA can be configured to the IP transport path, while the other traffic is routed to the ATM path.

DN0988674

Id:0900d8058089bfa1 Confidential

129

Activating and Verifying RU20 Features

Default values can be used for MinUDPPortIub, DSCPMedDCH, DSCPLow, DSCPHigh, DSCPMedHSPA, HSDPAULCToDSCP, HSUPADLCToDSCP, ToAWEOffsetNRTDCHIP, and ToAWSOffsetNRTDCHIP. b) Create the COCO object and give the desired COCO object id in the WBTS object. Configure the NBAP, AAL2 signalling, and AAL2 user plane connections according to the normal ATM Iub configuration principles. For the user plane connections the ATM and IP transport selection is based on the WBTS object IubTransportMedia parameter, and it is not directly dependent on the AAL2 VCC configuration in the COCO object. 5 Configure the Dual Iub in the Flexi WCDMA BTS. Please note that depending on the BTS software release (WN6.0 or WN6.0 On Top), the order of the steps might be different. a) Open the BTS Site Manager. b) Start Commissioning TRS.

g g

The selection of the transport mode (ATM Iub/IP Iub/Dual Iub) can be made only in the Flexi BTS Site Manager Commissioning Wizard, not in the Flexi TRS Manager. c) Enter the name and Id of the BTS, and IP addresses for the DCN. d) Select at least one PDH interface and one Ethernet interface that are in use. Select the transport mode of the FTM as Dual Iub. e) Give BTS Transport Ethernet Interface address (in the example provided: 10.3.1.1/30). With WN6.0 On Top, when using VLANs, leave the IP address field empty and add new VLAN, configure the IP address, enter the Committed information rate and select Enable QoS checkbox. f) Configure Quality of Service settings or use default values. g) With WN6.0 and earlier releases, if VLAN was configured in the RNC, take the VLAN in use and assign a VLAN Id. h) Configure the minimum UDP port and CAC committed bit rate value (in the example provided: 2 Mbit/s). i) Configure the BFD session to supervise the IP path to the RNC.

The BFD configuration is an optional step. It requires BFD session established in the RNC as instructed in step Configure the bidirectional forwarding detection (BFD) session to supervise the IP path to the BTS. j) Select primary and secondary timing sources. k) Configure the default gateway for BTS routing (in the example provided: 10.3.1.2). Also add static routes if necessary. l) Create at least four traffic descriptors: one for the BTS capacity on the VP level, one for Iub signaling Terminations, one for AAL2 User Path, and one for DCN.

For detailed instructions on creating traffic descriptors, see Defining traffic descriptors in Commissioning Flexi WCDMA BTS. m) Create ATM Iub Terminations to BTS. Mandatory terminations for commissioning are the following: Common NBAP, Dedicated NBAP, AAL2 Signaling, and at least one User Path.

130

Id:0900d8058089bfa1 Confidential

DN0988674

Activating and Verifying RU20 Features

g g g

For detailed instructions on creating traffic descriptors, see Defining IUB terminations to BTS in Commissioning Flexi WCDMA BTS. n) Create a DCN interface for the remote access to the BTS. o) Configure the default gateway for DCN routing. Also add static routes if necessary. For the NBAP/Signalling and RT user traffic, the ATM VCCs for the Dual Iub are configured in the same way as for ATM Iub. For detailed instructions on commissioning, see Commissioning Flexi WCDMA BTS. Expected outcome The RAN1449: Dual Iub for Flexi WCDMA BTS feature has been activated.

DN0988674

Id:0900d8058089bfa1 Confidential

131

Activating and Verifying RU20 Features

3.1.6

Verifying Dual Iub for Flexi WCDMA BTS


Purpose Follow the procedure below to verify that the activation of the RAN1449: Dual Iub for Flexi WCDMA BTS feature has been successful.

g
1 2 3

In case the feature is not working as expected, check the alarms for the Ethernet/BFD related failures. Steps Open the Parameter Editor. Check the NBAP link states. Check the status of the user plane with the Bidirectional Forwarding Detection (BFD). Check that the cell states are up and running. Perform the calls. Expected outcome The feature RAN1449: Dual Iub for Flexi WCDMA BTS has been activated successfully if all HSPA traffic can be carried over the IP transport.

4 5

132

Id:0900d8058084d9e0 Confidential

DN0988674

Activating and Verifying RU20 Features

3.1.7

Deactivating Dual Iub for Flexi WCDMA BTS


The Dual Iub for Flexi WCDMA BTS feature is not deactivated separately. The Dual Iub configuration can be changed to the full IP Iub or ATM Iub configuration by following the corresponding instructions. In this case the Iub transport and BTS configuration needs to be changed accordingly.

DN0988674

Id:0900d8058084d9df Confidential

133

Activating and Verifying RU20 Features

3.2
3.2.1

Activating RAN1578: HSPA Transport Fallback


Activating HSPA Transport Fallback
Purpose Follow the procedure to activate Feature RAN1578: HSPA Transport Fallback. For more information on the feature, see RAN1578: HSPA Transport Fallback in WCDMA RAN, rel. RU20, Feature Descriptions. Before you start In case of Dual Iub scenario, the BFD session (configured in the RNC) that monitors availability of the IP link must be bound to the respective IP based route. An IP link failure causes the change of the BFD state to DOWN, which makes the related IP based route unavailable for new connections. The RNC does not use this IP based route for ongoing or new calls as long as the BFD state remains DOWN. Restart of the RNC and the WBTS is not required after activation of this feature. 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. To check if the RNC license is activated, use the W7I command. For more information on using the command, see W7 - Licence and Feature Handling. Before a licensed feature can be activated, the license must be transferred to and installed in the RNC. For information on transferring the license to the RNC, see License management operations in RNC in WCDMA RAN license management. You can install the license 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. For information on license management in NetAct, see Managing Licenses, License Manager Help, Licence Manager Technical Reference Guide, and Licence Manager problems in Troubleshooting System Management Problems in Nokia Siemens Networks NetAct documentation. If you use the MML interface, you must also set the feature state (ON/CONFIG/OFF). In new installations, the default state is OFF. For the specific instructions on the license installation in the RNC, see W7L INSTALL OR UPDATE LICENCE in W7 - Licence and Feature Handling. For more information on license management, see Managing licence-based feature, License management principles, and License management in WCDMA RAN. To set the feature state, use the following command: W7M:FEA=<feature code>:<feature state>;

The feature code for this feature is 1482. In case of Dual Iub scenario (native IP transport), the following features are prerequisites: RAN77: RNC Ethernet Physical Interface (HW support in the RNC for IP-based transport) RAN1064: Ethernet+E1/T1/JT1 Interface Unit (Iub User Plane) for Flexi WCDMA BTS (HW support in Flexi WBTS for IP-based transport)

134

Id:0900d805808f1b82 Confidential

DN0988674

Activating and Verifying RU20 Features

RAN1701: AXCF unit for UltraSite WCDMA BTS (HW support in UltraSite WBTS for Dual Iub transport) RAN1449: Dual Iub for Flexi WCDMA BTS RAN1633: Dual Iub for UltraSite WCDMA BTS

In case of Hybrid BTS Backhaul scenario (emulated IP transport), the following features are prerequisites: RAN1064: Ethernet+E1/T1/JT1 Interface Unit (Iub User Plane) for Flexi WCDMA BTS (HW support in Flexi WBTS for IP-based transport) RAN1097: Ethernet Interface Unit IFUH (Iub User Plane) for AXC(HW support in UltraSite WBTS for IP-based transport) RAN1142: ATM over Ethernet for BTS (PWE3-emulated SW support in Flexi WBTS and UltraSite WBTS) RAN1063: Hybrid Backhaul with Pseudo Wires RAN759: Path Selection (the feature allows to configure RT DCH, NRT DCH, HSDPA, and HSUPA traffics over different VCCs)

Optional Feature RAN1253: Iub Transport QoS adds flexibility in enabling protection for QoS-differentiated traffic classes. Steps 1 2 3 4 5 Start the OMS Element Manager. Select Configuration Management -> Network Topology -> Tree View. Click "+" symbol to expand the objects. Lock all the WCELs under the relevant WBTS object. Enable HSPA Transport Fallback feature. a) Open the relevant WBTS object. b) Set the value of the BTSFallbackEnabled (BTS Fallback enabled) parameter to ENABLED. 6 Define user plane traffic classes to be protected in case of Dual Iub configuration. The configuration of the IubTransportFallback parameter is required and applicable only in Dual Iub scenario. In the relevant WBTS object, use the IubTransportFallback (Iub Transport Fallback Mapping) parameter to define the user plane traffic classes to be protected. The following user plane traffic classes can be protected: NRT DCH NRT HSPA RT HSPA

DN0988674

Id:0900d805808f1b82 Confidential

135

Activating and Verifying RU20 Features

g g
7

The RT HSPA means HSPA streaming traffic class. SRB HSPA

By default, all user plane traffic classes are protected. For more information on the IubTransportFallback parameter, see Protected traffic classes in WCDMA RAN Network Protection . Define protection for the QoS-differentiated DCH and HSPA transport bearers in Dual Iub configuration. The FallbackForDCHQoSPriXX and FallbackForHSPAQoSPriXX parameters in the TQM object are applicable only in Dual Iub configuration. The protection selection is extended in accordance with Scheduling Priority Indicator (SPI) values received from the core network (CN) during each radio access bearer (RAB) setup. To define protection for the QoS-differentiated DCH and HSPA transport bearers, the feature RAN1253: Iub Transport QoS must be active. For more information, see RAN1253: Iub Transport QoS and Activating RAN1253: Iub Transport QoS. a) Open the relevant TQM object. b) For the QoS-differentiated DCH transport bearers intended to be protected, set the value of FallbackForDCHQoSPriXX (Fallback for DCH QoS Priority Mapping) parameters to PROTECTED . c) For the QoS-differentiated HSPA transport bearers intended to be protected, set the value of FallbackForHSPAQoSPriXX (Fallback for HSPA QoS Priority Mapping) parameters to PROTECTED . d) Enable HSPA QoS in each intended cell. In the given WCEL object, configure the HSPAQoSEnabled parameter. If you enable QoS for streaming HSPA or CS voice over HSPA, the QoS for NRT HSPA is also enabled.

g g
8

To activate the FallbackForDCHQoSPriXX and FallbackForHSPAQoSPriXX parameters, all WBTSs connected to the considered TQM object must have the BTSFallbackEnabled parameter set to ENABLED. By default, all QoS-differentiated DCH and HSPA transport bearers are protected.

Define fallback VCCs in Hybrid BTS backhaul configuration. The AAL2FallbAttribute parameter at the ATM end point configuration indicates whether the given AAL2 VCC should be used as a fallback for the protected traffic when the default VCC is not available. The parameter is used to control the AAL2 VCC selection at the transport bearer setup only in the Hybrid BTS backhaul scenario. The parameter is not used in Dual Iub scenario. In Dual Iub scenario, the HSPA Fallback functionality is managed from the WBTS object level (the IubTransportFallback parameter). a) Open the relevant COCO object.

136

Id:0900d805808f1b82 Confidential

DN0988674

Activating and Verifying RU20 Features

b) In the topology tree, select AAL2 user plane links folder and then AAL2 User plane link data tab. c) For the VCC intended to be a fallback VCC, set the value of the AAL2FallbAttribute (Fallback attribute) parameter to Enabled. 9 Unlock all the WCELs under the relevant WBTS object. Expected outcome Feature RAN1578: HSPA Transport Fallback has been activated for the relevant WBTS.

DN0988674

Id:0900d805808f1b82 Confidential

137

Activating and Verifying RU20 Features

3.2.2

Verifying HSPA Transport Fallback


Purpose Follow the procedure to verify Feature RAN1578: HSPA Transport Fallback. Before you start Make sure the protected traffic classes are carried over IP-based path. Steps

Generate IP-based path failure. a) In Dual Iub scenario, generate the failure between the WBTS and RNC. b) In Hybrid BTS Backaul scenario, generate the failure between the WBTS and PWE3 gateway at the RNC site.

Check if the appropriate alarms have been raised in the RNC a) In Dual Iub scenario, check if the BFD LINK FAILURE alarm has been raised. b) In Hybrid BTS Backaul scenario, check if the AIS/RDI-related alarms have been raised.

g
3 4

These alarms trigger the HSPA Transport Fallback functionality.

Make an HSPA call through the relevant WBTS. Check if the new HSPA call is admitted over ATM-based path in accordance with the chosen HSPA Transport Fallback configuration. Expected outcome Feature RAN1578: HSPA Transport Fallback has been successfully activated for the relevant WBTS.

138

Id:0900d8058062d820 Confidential

DN0988674

Activating and Verifying RU20 Features

3.2.3

Deactivating HSPA Transport Fallback


Purpose Follow the procedure to deactivate Feature RAN1578: HSPA Transport Fallback. Steps

1 2 3 4 5

Start the OMS Element Manager. Select Configuration Management -> Network Topology -> Tree View. Click "+" symbol to expand the objects. Lock all the WCELs under the relevant WBTS object. Disable HSPA Transport Fallback feature. a) Open the relevant WBTS object. b) Set the value of the BTSFallbackEnabled (BTS Fallback enabled) parameter to NOT ENABLED.

Unlock all the WCELs under the relevant WBTS object. Expected outcome Feature RAN1578: HSPA Transport Fallback has been deactivated for the relevant WBTS.

DN0988674

Id:0900d80580822666 Confidential

139

Activating and Verifying RU20 Features

3.3
3.3.1

Activating RAN1707: Flexi WCDMA Integrated CESoPSN


Activating Flexi WCDMA Integrated CESoPSN
Purpose Follow the procedure below to activate the RAN1707: Flexi WCDMA Integrated CESoPSN feature in the Flexi WCDMA BTS (WBTS) using BTS Site Manager. For more information on the feature, see RAN1707: Flexi WCDMA Integrated CESoPSN in WCDMA RAN, rel. RU20, Feature Descriptions, Dimensioning WCDMA RAN, and Flexi Multiradio BTS WCDMA Transmission Description. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. 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. Before a licensed feature can be activated, the license must be transferred to and installed in the WBTS. For information on transferring the license to the WBTS, see Managing licences in Integrating and configuring Flexi WCDMA BTS transmission. To check if the WBTS license is present, choose the Configuration j License Management in the BTS Site Manager, to open license management dialog box. You can install the license using NetAct or a local EM tool. If you install the license using NetAct, the feature covered by the license is automatically set to the ON state. For information on license management in NetAct, see Managing Licenses, License Manager Help, Licence Manager Technical Reference Guide, and Licence Manager problems in Troubleshooting System Management Problems in Nokia Siemens Networks NetAct documentation. For more information on license management, see License management principles, and License management in WCDMA RAN.

The feature code for this feature is 1544. For operating the feature, RAN74: IP Based Iub for Flexi WCDMA BTS is required. The feature also requires one of the following sub-modules: RAN1155: Flexi WCDMA BTS Eth+E1/T1/JT1 Sub-Module 'FTIB' with Timing over Packet RAN1706: Transport sub-module FTFB for Flexi WCDMA BTS RAN1819: Transport sub-module FTLB for Flexi Multimode BTS

As a counterpart to the Flexi BTS, a CESoPSN gateway is needed to convert the TDM traffic from the BSC towards IP. The following gateways are supported: A-1200 / FlexiPacket Hub A-2200 / FlexiPacket Hub BSC3i 1000/2000 (with ETIP unit) FlexiBSC (with ETIP unit) Tellabs 8630 & 8660

It is recommended to separate CESoPSN and regular Iub traffic into different VLANs. This requires the RAN1709: VLAN Traffic Differentiation licence to be activated.

140

Id:0900d8058083ab1e Confidential

DN0988674

Activating and Verifying RU20 Features

After the configuration and activation of the feature, a constant part of the traffic to/from the WBTS will be CESoPSN traffic. This constant CES traffic has to be taken into account for dimensioning. It is also recommended to map the CESoPSN to Expedited Forwarding (EF) traffic class, so that it experiences similar treatment as in the TDM transmission case. Steps

1 2

Launch WCDMA BTS Site Manager. Make sure Ethernet and PDH interfaces are configured, and WBTS is in IP Iub mode. For details on configuring Ethernet and PDH interfaces, see Integrating and configuring Flexi WCDMA BTS transmission.

g
3

Configure CES over PSN settings. Select View j IP and go to the CES Over PSN tab. Enter the minimum UDP port from the available range. Make sure that the port number does not overlap with the UDP port for the user plane traffic.

g
4

The required bandwidth displayed is the bandwidth required for each of the pseudowire created. Since there are no pseudowires configured, the bandwidth is displayed as zero. Configure the PSN tunnel. Click New PSN Tunnel and enter destination IP address.

g
5

Currently, one pseudowire (PW) tunnel and up to 16 pseudowires are supported.

Configure the pseudowire configurations. Click New Pseudowire and take it in use. Configure the pseudowire parameters: payload timeslots of TDM frame, remote UDP port, DSCP, jitter buffer size, and number of frames per packet. After configuring the settings, the bandwidth required for each pseudowire is calculated.

g
6

Up to 4 pseudowires can be configured for FTIB and FTLB sub-modules. Up to 16 pseudowires can be configured for FTFB sub-module.

Configure VLAN for PW tunnel. This is an optional step. The CESoPSN traffic can be untagged or using the Iub VLAN. However, it is recommended to separate CESoPSN and regular Iub traffic into different VLANs. This requires the RAN1709: VLAN Traffic Differentiation licence to be activated. In the IP Interfaces tab, select Transport Ethernet interface and click New VLAN. Configure the VLAN id and the IP address and select the CES Over PSN check box.

DN0988674

Id:0900d8058083ab1e Confidential

141

Activating and Verifying RU20 Features

Select VLAN mapping and assign previously configured VLAN to the CES over PSN traffic. 7 Enable synchronization co-location. With co-location synchronization enabled, the TDM PDH interfaces are working with a clock derived from the selected synchronization reference. The synchronization support for collocation is independent of the availability of RAN1707 license. For more information on synchronization, see WCDMA RAN synchronization. For enabling the synchronization co-location, proceed with the BTS commissioning. In the Define settings for BTS page, select the Forward synchronization in co-siting check box. The synchronization co-location can be also enabled with a syncPropagationEnabled parameter in the Site Configuration File of the BTS. Expected outcome The feature RAN1707: Flexi WCDMA Integrated CESoPSN in the Flexi WCDMA BTS has been activated. Further information Before the CESoPSN traffic can be utilized, a proper setup of the gateway side is needed.

142

Id:0900d8058083ab1e Confidential

DN0988674

Activating and Verifying RU20 Features

3.3.2

Verifying Flexi WCDMA Integrated CESoPSN


Purpose Follow the procedure below to verify that the activation of RAN1707: Flexi WCDMA Integrated CESoPSN feature has been successful. Before you start Check that the pseudowires are correctly configured on both sides using a valid UDP port range. Steps

Check that the following alarms do not show up. 61070: CES_PWT_DOWN, which indicates a CES pseudowire tunnel in Up state, but no IP packets are received on the tunnel in the last second 61071: CES_PW_DOWN, which indicates the CES pseudowire in Up state, but the number of received packets in the CES pseudowire is less than 10% compared to the expected number of packets for 1 second 61072: CES_PW_Remote_Packet_Loss, which indicates that packet loss condition for packets of the given CES pseudowire persists for more than 1 second in ingress

Check the counters for CESoPSN traffic. If the CESoPSN traffic is running error free, the counters CES_Packets_Tx and CES_Packets_Rx (the number of frames sent over/received over the CES interface) will be incremented. Non-zero value of counters CES_OutofSyncPackets, CES_LostPackets_PW, and CES_LBit_Packets_PW indicate problems with the CESoPSN traffic. Expected outcome The activation of the RAN1707: Flexi WCDMA Integrated CESoPSN feature has been verified.

DN0988674

Id:0900d805806faf3b Confidential

143

Activating and Verifying RU20 Features

3.3.3

Deactivating Flexi WCDMA Integrated CESoPSN


Purpose Follow the procedure below to deactivate feature RAN1707: Flexi WCDMA Integrated CESoPSN in the WBTS. Steps

1 2

Open the BTS Site Manager. Disable or delete the pseudowires and PSN tunnel. Select View j IP and go to the CES Over PSN tab. In the Psedowire view disable each pseudowire by clearing the In use checkbox and click Send. Alternatively, delete all pseudowires and in the end, the PSN tunnel.

Delete the CESoPSN VLAN (optional). If a separate VLAN for CESoPSN traffic is used, in the IP interfaces tab, select the VLAN previously configured for CESoPSN traffic and delete it. Expected outcome The RAN1707: Flexi WCDMA Integrated CESoPSN feature has been deactivated in the WBTS.

144

Id:0900d805807a7bdf Confidential

DN0988674

Activating and Verifying RU20 Features

3.4
3.4.1

Activating RAN1708: BTS Synchronous Ethernet


Activating BTS Synchronous Ethernet in Flexi WCDMA BTS
Purpose Follow the procedure to activate feature RAN1708: BTS Synchronous Ethernet in Flexi WCDMA BTS. For activating Synchronous Ethernet (SyncE) in UltraSite WCDMA BTS, see Activating BTS Synchronous Ethernet in UltraSite WCDMA BTS. RAN1708: BTS Synchronous Ethernet requires considering additional bandwidth on the BTS side in the downlink due to terminating synchronization status messages (SSM) in there. This bandwidth, of 10 kbps at maximum, is to be allocated on the Ethernet layer only (is not visible to higher layers, for example IP). For more details on bandwidth requirements of synchronization signals, see Dimensioning WCDMA RAN: Access Network (RNC and Transport). For more information on the feature, see RAN1708: BTS Synchronous Ethernet in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. The feature RAN1708: BTS Synchronous Ethernet is an optional application with a separate license control. The feature belongs to application software. Before you activate the feature, make sure you have a valid license installed. Before a licensed feature can be activated, the license (a file including the feature information) must be transferred and installed in the WBTS. You can install the license by using NetAct or a local BTS Site Manager interface. Once the license file has been installed, the activation of the feature takes place through the configuration of the SyncE as a synchronization clock source, as explained later in this document. For more information on transferring the license using NetAct, see License management operations in BTS in WCDMA RAN license operation. For more information on transferring the license for Flexi WBTS using BTS Site Manager, see Managing licences in Integrating and configuring Flexi WCDMA BTS transmission.

The feature code for this feature is 1515. For more information, see the following documentation: Managing licence-based feature License management principles Licensed sales items in RU20 in License management in WCDMA RAN System Administration Principles in NetAct Product Documentation

The feature RAN1708: BTS Synchronous Ethernet also requires specific hardware. The FTIB, FTFB, or FTLB (available in RU20 On Top) sub-modules are required for Flexi WCDMA BTS. For more information, see RAN1155: Flexi WCDMA BTS Eth+E1/T1/JT1 Sub-Module "FTIB" with Timing over Packet, RAN1819: Transport Sub-module FTLB for Flexi Multimode BTS, or RAN1706: Transport Sub-module FTFB for Flexi WCDMA BTS.

DN0988674

Id:0900d8058083ab1c Confidential

145

Activating and Verifying RU20 Features

For Flexi WCDMA BTS, this feature is based on or requires the following features: Either RAN1142: ATM over Ethernet or RAN74: IP Based Iub for Flexi WCDMA BTS for the configuration of the packet transfer mode on the packet backhaul as Pseudo Wires or Native Iub/IP respectively RAN1449: Dual Iub for Flexi WCDMA BTS

Both RAN1708: BTS Synchronous Ethernet and RAN1254: Timing over Packet can be activated at the same time; one is set as primary and the other as secondary synchronization source. The feature RAN74: IP Based Iub for Flexi WCDMA BTS requires RAN1708: BTS Synchronous Ethernet feature for synchronization in case other synchronization methods are not available. Even though SyncE can work perfectly in the ATM over Ethernet Iub mode, the target application for SyncE is explicitly meant to be used in the IP-based Iub mode. It is because of the fact that in the ATM over Ethernet Iub mode there are classical alternatives for the provision of synchronization to the WCDMA BTS based on PDH/SDH TDM signal transmission. Steps

Take an Ethernet interface in use. In the TRS Hardware view of the BTS Site Manager, under Physical Interfaces tab, take an Ethernet interface in use.

Acknowledge the changes. Click Send.

Activate SyncE. In the Configuration menu of the BTS Site Manager, select TRS Configuration and Synchronization. Select Synchronous Ethernet<IF> as the primary timing source.

g
4

By default the SSM messages are enabled and message timeout is set to 5 seconds.

Acknowledge the changes. Click Send. Close the window. Expected outcome The feature RAN1708: BTS Synchronous Ethernet has been activated in the Flexi WBTS. Further information When Synchronous Ethernet is operational in the FTxx sub-module, a clock output of 2.048 MHz is forwarded towards the BTS. When the internal clock is taken into use, there is no clock forwarded towards the BTS.

146

Id:0900d8058083ab1c Confidential

DN0988674

Activating and Verifying RU20 Features

3.4.2

Activating BTS Synchronous Ethernet in UltraSite WCDMA BTS


Purpose Follow the procedure to activate feature RAN1708: BTS Synchronous Ethernet in UltraSite WCDMA BTS. The SyncE in UltraSite WBTS is supported from RU20 On Top. For activating Synchronous Ethernet (SyncE) in Flexi WCDMA BTS, see Activating BTS Synchronous Ethernet in Flexi WCDMA BTS. RAN1708: BTS Synchronous Ethernet requires considering additional bandwidth on the BTS side in the downlink due to terminating synchronization status messages (SSM) in there. This bandwidth, of 10 kbps at maximum, is to be allocated on the Ethernet layer only (is not visible to higher layers, for example IP). For more details on bandwidth requirements of synchronization signals, see Dimensioning WCDMA RAN: Access Network (RNC and Transport). For more information on the feature, see RAN1708: BTS Synchronous Ethernet in WCDMA RAN, rel. RU20, feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. The feature RAN1708: BTS Synchronous Ethernet is an optional application with a separate license control. The feature belongs to application software. Before you activate the feature, make sure you have a valid license installed. Before a licensed feature can be activated, the license (a file including the feature information) must be transferred and installed in the WBTS. You can install the license by using NetAct or a local AXC Manager interface. Once the license file has been installed, the activation of the feature takes place through the configuration of the SyncE as a synchronization clock source, as explained later in this document. For more information on transferring the license using NetAct, see License management operations in BTS in WCDMA RAN license management. For more information on transferring the license for UltraSite WBTS using AXC Manager, see Managing licences in Operating and maintaining AXC.

The feature code for this feature is 1515. For more information, see the following documentation: Managing licence-based feature License management principles Licensed sales items in RU20 in License management in WCDMA RAN System Administration Principles in NetAct Product Documentation

The feature RAN1708: BTS Synchronous Ethernet also requires specific hardware. The AXCF unit is required for AXC. For more information on AXCF, see RAN1701: AXCF unit for UltraSite WCDMA BTS. For UltraSite WCDMA BTS, this feature is based on or requires the following features: Either RAN1142: ATM over Ethernet or RAN1634: IP Based Iub for UltraSite WCDMA BTS for the configuration of the packet transfer mode on the packet backhaul as Pseudo Wires or Native Iub/IP respectively RAN1633: Dual Iub for UltraSite WCDMA BTS

DN0988674

Id:0900d80580863d85 Confidential

147

Activating and Verifying RU20 Features

Both RAN1708: BTS Synchronous Ethernet and RAN1254: Timing over Packet can be activated at the same time; one is set as primary and the other as secondary synchronization source. The feature RAN1634: IP Based Iub for UltraSite WCDMA BTS requires RAN1708: BTS Synchronous Ethernet feature for synchronization in case other synchronization methods are not available. Even though SyncE can work perfectly in the ATM over Ethernet Iub mode, the target application for SyncE is explicitly meant to be used in the IP-based Iub mode. It is because of the fact that in the ATM over Ethernet Iub mode there are classical alternatives for the provision of synchronization to the WCDMA BTS based on PDH/SDH TDM signal transmission. Steps

Launch AXC Manager. Make sure Ethernet interfaces are configured (AXCF unit is in use), and WBTS is in IP Iub or Dual Iub mode. Define SyncE as the timing source. Click Configuration j Synchronization to open the synchronization window. Add new timing source by checking in the Transmission interface and selecting AXCF along with its Ethernet interface.

Configure SyncE parameters. In the same window, configure the SSM timeout. You can also enable the SSM monitoring on the selected interface.

g
4

The SSM value shows the current SSM value obtained from the concrete timing source.

Acknowledge the changes. Click OK to close the window.

Change the priority of synchronization timing sources if necessary. Select the timing source and use the arrow buttons to change the priority.

Acknowledge the changes. Click OK to send the changes and close the window. Expected outcome The feature RAN1708: BTS Synchronous Ethernet has been activated in the UltraSite WBTS.

148

Id:0900d80580863d85 Confidential

DN0988674

Activating and Verifying RU20 Features

3.4.3

Verifying BTS Synchronous Ethernet


To verify that the feature RAN1708: BTS Synchronous Ethernet has been activated, check that there is no pending Synchronization lost alarm. Use the BTS Site Manager or AXC Manager to confirm that the alarm is not visible. The currently active timing source is displayed in the BTS Site Manager in Configuration j TRS Configuration j Synchronization under Active source in TRS and in the AXC Manager in the Configuration j Synchronization window. The feature RAN1708: BTS Synchronous Ethernet has been activated successfully if there are no synchronization alarms and Synchronous Ethernet is the active source in synchronization window.

DN0988674

Id:0900d805807012cd Confidential

149

Activating and Verifying RU20 Features

3.4.4

Deactivating BTS Synchronous Ethernet


To deactivate the feature RAN1708: BTS Synchronous Ethernet, change the source for synchronization. For Flexi WBTS, in the Configuration menu of the BTS Site Manager, select TRS Configuration and Synchronization. Either delete the Synchronous Ethernet from the list of timing sources by selecting the checkbox and pressing Send, or select different source of synchronization. For UltraSite WBTS, in the Configuration j Synchronization window of AXC Manager, remove SyncE from the timing sources list and click OK.

Before deleting the Synchronous Ethernet, check that you have an alternative synchronization source available. In this case the synchronization automatically switches to the secondary source. If there is no secondary source, the system goes to internal clock automatically.

150

Id:0900d805807012c9 Confidential

DN0988674

Activating and Verifying RU20 Features

3.5
3.5.1

Activating RAN1709: VLAN Traffic Differentiation


Activating RAN1709: VLAN Traffic Differentiation
Purpose Follow the procedure to activate the feature RAN1709: VLAN Traffic Differentiation. For more information on the feature, see RAN1709: VLAN Traffic Differentiation in WCDMA RAN, rel. RU30, feature descriptions. Before you start Restart of the RNC is not required after the activation of this feature. The WBTS requires restarting if new VLAN IP addresses have been configured to be used by the user, control or management plane. The feature RAN1709: VLAN Traffic Differentiation is an optional application feature. The license is required to configure more than one VLAN interface in the WBTS. Before you activate the feature, make sure a valid license has been installed. For information on managing licenses, see Licensing.

The feature code for this feature is 1640. The feature RAN1709: VLAN Traffic Differentiation requires certain hardware and is dependant on other features. For more information, see Hardware requirements and Interdependencies between features in RAN1709: VLAN Traffic Differentiation in WCDMA RAN, rel. RU20, feature descriptions. This document presents the procedures on how to configure the new functionalities introduced by the feature RAN1709: VLAN Traffic Differentiation. For more information on how to configure IP-based Iub, see Activating RAN74, RAN1634, RAN1449, and RAN1633: IP based Iub and Dual Iub. The configuration examples in the activation instructions use the IP addressing presented in the figure Figure 10 Example of IP addressing scheme for VLAN Traffic Differentiation.

Figure 10

Example of IP addressing scheme for VLAN Traffic Differentiation

Static routes are configured in the RNC and WBTS as presented in the following steps. In this example, static routes must also be configured in the site router. For details, see the table Site router static routes.

DN0988674

Id:0900d8058092ab8a Confidential

151

Activating and Verifying RU20 Features

site router static routes usage CP MP (RNC) MP (WBTS) Table 11 destination subnet 10.1.0.0/24 10.0.0.0/24 10.4.0.0/30 gateway 10.2.30.2 10.2.40.2 10.3.80.2

Site router static routes

Steps for activating RAN1709: VLAN Traffic Differentiation on the WBTS 1 Configure VLANs in the WBTS via the Element Manager. For Flexi WBTS, open the BTS Site Manager. For UltraSite WBTS, open the AXC Manager. If you follow the example IP addressing used in this document, make sure that the following WBTS IP addresses are configured as described: The BTS IP address belongs to the 10.4.0.0/30 BTS O&M subnet. The RNC IP address is the IP address assigned to the OMU unit in the RNC and belongs to the 10.0.0.0/24 RNC O&M subnet. The Far end SCTP address is the IP address assigned to the ICSU unit in the RNC and the Far end SCTP subnet is the Iub CP subnet configured in the RNC.

a) Configure VLANs for different traffic types.

For Flexi WBTS, select IP j IP Interfaces j New VLAN. For UltraSite WBTS, select IP j Settings j Transport addresses j Configure j Add. For this configuration example, configure VLANs for different traffic types in accordance with the table VLANs for different traffic types. usage UP1 UP2 CP MP ToP Table 12 VLAN ID 50 60 70 80 90 address/mask 10.3.50.2/24 10.3.60.2/24 10.3.70.2/24 10.3.80.2/24 10.3.90.2/24

VLANs for different traffic types

The Enable QoS option must be selected for the VLANs used for user plane, otherwise no user plane resource can be allocated to these VLANs. b) Configure Commited Information Rate for each VLAN.

g
152

When M-plane or C-plane are configured with a virtual address: IP Interface Signalling CBR is not considered.

Id:0900d8058092ab8a Confidential

DN0988674

Activating and Verifying RU20 Features

IP Interface DCN CBR is not considered. The sum of interface CIRs (cirs in IEIFs) should be configured below the available capacity.

c) Configure Shaper Information Rate and Shaper Burst Size. These parameters are used only when VLAN level shaping is configured. For more information, see substep b) in step Configure traffic shaping type. d) Configure BFD sessions for VLAN interfaces used by user plane traffic.

BFD configuration is optional. Up to two BFD sessions for each VLAN and the plain Ethernet interface can be established. Configure one multihop BFD session for each of the two VLAN interfaces used by the user plane. The configuration must be in accordance with the parameters and IP addresses of the RNC BFD sessions configured in step Create BFD sessions.

Configure traffic shaping type. For Flexi WBTS, select IP j IP Interfaces j Transport Ethernet interface. For UltraSite WBTS, select IP j Settings j Transport Addresses j Modify. Traffic shaping can be performed either on Ethernet interface level or individually for each VLAN. For more information on the WBTS shaping functionality, see WBTS scheduling and shaping in RAN1709: VLAN Traffic Differentiation in WCDMA RAN, rel. RU20, feature descriptions. a) Configure traffic shaping on Ethernet interface level. Set the Traffic shaping type parameter to WFQ. Configure Total Shaper Information Rate and Total Shaper Burst Size. The whole aggregated egress traffic is shaped on the Ethernet interface port level with regard to these two parameters. b) Configure traffic shaping on VLAN interface level. Set the Traffic shaping type parameter to Path. Configure Shaper Information Rate and Shaper Burst Size to shape all traffic that is sent over the Ethernet interface (if the Ethernet interface is configured). The shaping on VLAN level is performed in accordance with the parameters configured in substep c) in step Configure VLANs in the WBTS via the Element Manager.

Configure static routes in the WBTS for different traffic types. a) Configure static routes in the WBTS for Iub traffic.

For Flexi WBTS, select IP j BTS Routing. For UltraSite WBTS, select IP j Settings j Routing. It is assumed that all WBTS VLANs are terminated in the site router. The site router 10.3.XX.1 IP addresses are the gateways for the respective egress WBTS traffic types. The table WBTS static routes presents the static routes that must be configured in the WBTS in this configuration example.

DN0988674

Id:0900d8058092ab8a Confidential

153

Activating and Verifying RU20 Features

WBTS static routes usage UP1 UP2 CP MP ToP Table 13 destination subnet gateway

10.2.10.0/24 10.3.50.1 10.2.20.0/24 10.3.60.1 10.1.0.0/24 10.0.0.0/24 ToP subnet 10.3.70.1 10.3.80.1 10.3.90.1

WBTS static routes

b) Configure a static route in the WBTS towards the NetAct network. The static route in the WBTS should have the gateway configured to the IP address of the site router's VLAN interface used by management plane (in this configuration example, the IP address is 10.3.80.1). The site router should have the routing information configured accordingly to forward all O&M traffic destined for the NetAct network. Steps for activating RAN1709: VLAN Traffic Differentiation on the IPA-RNC 1 Configure VLAN interfaces for different traffic types in the RNC via MML. In the configuration example presented, only one non-redundant NPGE unit connected to one site router is used. The VLANs for different traffic types configured in the RNC are terminated in the site router. a) Interrogate the state of the units. ZUSI:NPGEP,0; b) Configure the Ethernet shaping rate to limit the outgoing traffic. The same configuration must be set to the redundant unit separately. ZQAS:NPGEP,0:IFGE0:BANDWIDTH=800; c) Change the state of the given Gigabit Ethernet interface to UP. ZQRN:NPGE,0:IFGE0:::::UP; d) Configure VLAN interface used by user plane 1. ZQRM:NPGE,0:VL10:10:IFGE0; ZQRN:NPGE,0:VL10:10.2.10.2,P:24; e) Configure VLAN interface used by user plane 2. ZQRM:NPGE,0:VL20:20:IFGE0; ZQRN:NPGE,0:VL20:10.2.20.2,P:24; f) Configure VLAN interface used by control plane. ZQRM:NPGE,0:VL30:30:IFGE0; ZQRN:NPGE,0:VL30:10.2.30.2,P:24; g) Configure VLAN interface used by management plane. ZQRM:NPGE,0:VL40:40:IFGE0; ZQRN:NPGE,0:VL40:10.2.40.2,P:24;

154

Id:0900d8058092ab8a Confidential

DN0988674

Activating and Verifying RU20 Features

Configure two IP based routes towards the given WBTS for user plane traffic differentation. It is also possible to configure only one IP based route per WBTS in the RNC. In this case, the IP based route must be associated with two different IP addresses to support traffic differentiation. The mechanism of the IP based route selection for user plane traffic is described in User plane transport bearer setup in RAN1709: VLAN Traffic Differentiation in WCDMA RAN, rel. RU20, feature descriptions. a) Configure IP based route for user plane 1 ZQRU:ADD:10,"IPROUTE1":11000:10000:100:100:ON,20; ZQRC:NPGE,0:VL10:IPV4=10.2.10.2:ID=10:PHB=EF,AF4,AF3,AF2,AF 1; b) Configure IP based route for user plane 2 ZQRU:ADD:20,"IPROUTE2":11000:10000:100:100:ON,20; ZQRC:NPGE,0:VL20:IPV4=10.2.20.2:ID=20:PHB=BE;

g g

The PHB sets assigned to the two IP addresses should cover all possible PHB values (BE, AF1, AF2, AF3, AF4, and EF). Only then can each kind of user plane traffic be mapped to one of the two dedicated VLANs. Ensure the IP QoS is enabled in IP interfaces by using MML command Q8S. For more information, see Configuring IP QoS section in Configuring IP Connection for IPA-RNC document.

Configure static routes in the RNC for different traffic types. It is assumed that all RNC VLANs are terminated in the site router. The site router 10.2.XX.1 IP addresses are the gateways for the respective egress RNC traffic types. The table Table 14 NPGE static routes presents the static routes that must be configured in the NPGE in this configuration example. NPGE static routes usage UP1 UP2 CP MP Table 14 destination subnet gateway

10.3.50.0/24 10.2.10.1 10.3.60.0/24 10.2.20.1 10.3.70.0/24 10.2.30.1 10.4.0.0/30 10.2.40.1

NPGE static routes

a) Configure a static route for the user plane 1 subnet between the site router and WBTS. ZQKC:NPGE,0:10.3.50.0,24:10.2.10.1:PHY;

DN0988674

Id:0900d8058092ab8a Confidential

155

Activating and Verifying RU20 Features

b) Configure a static route for the user plane 2 subnet between the site router and WBTS. ZQKC:NPGE,0:10.3.60.0,24:10.2.20.1:PHY; c) Configure a static route for the control plane subnet between the site router and WBTS. ZQKC:NPGE,0:10.3.70.0,24:10.2.30.1:PHY; d) Configure a static route for the BTS O&M subnet in the NPGE unit. With the ZQKC command configure a static route in the NPGE towards the WBTS O&M subnet (10.4.0.0/30) with the gateway that is the IP address of the site router's VLAN interface used by management plane (in this configuration example, this IP address is 10.2.40.1). ZQKC:NPGE,0:10.4.0.0,24:10.2.40.1:PHY; e) Configure a static route for the BTS O&M subnet in the OMU unit. With the ZQKC command configure a static route in the OMU towards the WBTS O&M subnet (10.4.0.0/30) with the gateway that is the IP address of the NPGE in the same subnet as the OMU (10.0.0.0/24). ZQKC:OMU,0:10.4.0.0,24:10.0.0.X:LOG;

10.0.0.X is the IP address of the NPGE unit in the RNC O&M subnet (10.0.0.0/24). f) Configure static routes in the OMU and NPGE units towards the NetAct network. The static route in the OMU unit should have the gateway configured to the IP address of the RNC's VLAN interface used by management plane (in this configuration example, this IP address is 10.2.40.2). The static route in the NPGE unit should have the gateway configured to the IP address of the site router's VLAN interface used by management plane (in this configuration example, this IP address is 10.2.40.1). The site router should have the routing information configured accordingly to forward all O&M traffic destined for the NetAct network.

Create BFD sessions and associate them with the IP based routes configured. BFD configuration is optional. By configuring a BFD session and binding it to the IP based route, IP path protection is ensured. a) Configure a BFD profile. ZYGR:C:PROF=1,RXINT=500,TXINT=500,DMULT=2; b) Configure a BFD session for the user plane 1 traffic between the RNC and WBTS and associate it with the respective IP based route.

Use the values of the IP based route IDs configured in step Configure two IP based routes towards the given WBTS for user plane traffic differentation. ZYGS:C:NPGE,0,1,10.2.10.2,10.3.50.2:PROF=1,ALARM=OFF,ROUTE=1 0; c) Configure a BFD session for the user plane 2 traffic between the RNC and WBTS and associate it with the respective IP based route. ZYGS:C:NPGE,0,2,10.2.20.2,10.3.60.2:PROF=1,ALARM=OFF,ROUTE=2 0;

156

Id:0900d8058092ab8a Confidential

DN0988674

Activating and Verifying RU20 Features

d) Enable the BFD sessions configured and their alarms when the WBTS has been configured to the RNC. ZYGS:S:NPGE,0,1:ALARM=ON,MODE=0; 5 6 Open the OMS Element Manager. Go to Tree View: Configuration Management j Network Topology j Tree View 7 Configure Iub IP based route identifiers. a) Open the relevant WBTS object. b) Assign the IP based route IDs to the given WBTS. Use the values of the IP based route IDs configured in step Configure two IP based routes towards the given WBTS for user plane traffic differentation. If you follow the exemplary configuration presented in this document, assign 10 to IP Based Route Id Iub (IPBasedRouteIdIub) and 20 to IP Based Route Id Iub 2 (IPBasedRouteIdIub2).

It is possible to configure one IP based route per WBTS in the RNC. In this case, only IP Based Route Id Iub must be configured. If there are two VLANs attached to one IP based route, IP Based Route Id Iub 2 does not need to be configured. If you plan two IP based routes per WBTS, IP Based Route Id Iub 2 can be configured only when IP Based Route Id Iub has been configured. IP Based Route Id Iub 2 is used only for user plane connections. IP Based Route Id Iub is mapped by the system to IP Based Route Identification (IPBasedRouteId) in the respective IPNB object and used during both user and control plane connections. While configuring IP Based Route Id Iub and IP Based Route Id Iub 2, use the IDs of the IP based routes that have already been configured via MML in the IPA platform. Configuration of IP Based Route Id Iub 2 with a nonexisting IP based route ID is not checked by the system and results with a failure of user plane transport bearer establishment. Configuration of IP Based Route Id Iub with a nonexisting IP based route ID results with the Error 17126 The IP based route ID cannot be found, as this ID is used by the IPNB object during CNBAP link creation. The control plane traffic uses only IP Based Route Id Iub. Steps for activating RAN1709: VLAN Traffic Differentiation on the Multicontroller RNC Purpose Follow the procedure to activate the feature RAN1709: VLAN Traffic Differentiation for mcRNC. For more information on the feature, see RAN1709: VLAN Traffic Differentiation for mcRNC in WCDMA RAN, rel. RU30, feature descriptions. Before you start Restart of the RNC is not required after the activation of this feature. The WBTS requires restarting if new VLAN IP addresses have been configured to be used by the user, control or management plane.

DN0988674

Id:0900d8058092ab8a Confidential

157

Activating and Verifying RU20 Features

This document presents the procedures on how to configure the new functionalities introduced by the feature RAN1709: VLAN Traffic Differentiation. For more information on how to configure IP-based Iub, see Configuring IP Connection for Multicontroller RNC. The configuration examples in the activation instructions use the IP addressing presented in the figure Figure 11 Example of IP addressing scheme for VLAN Traffic Differentiation for mcRNC.

Figure 11

Example of IP addressing scheme for VLAN Traffic Differentiation for mcRNC

The traffic is separated to four different VLANs: A VLAN for high priority user plane traffic mcRNC/site routers: VLAN11&12, BTS/Routers VLAN 50 A VLAN for low priority user plane traffic mcRNC/site routers: VLAN13&14, BTS/Routers VLAN 60 A VLAN for signalling traffic mcRNC/site routers: VLAN15&16, BTS/Routers VLAN 70 A VLAN for O&M traffic

158

Id:0900d8058092ab8a Confidential

DN0988674

Activating and Verifying RU20 Features

mcRNC/site routers: separate VLANs in between CFPU units and site routers (not visible in figure)

In addition a separate VLAN is configured on WBTS for ToP traffic. The WBTS configuration can be done as in Steps for activating RAN1709: VLAN Traffic Differentiation on the WBTS. 1 Configure VLAN interfaces for different traffic types in the mcRNC via SCLI. For VLAN configuration, see chapter 3.6 Configuring Iu, Iur and Iub interface, mcRNC evolved site solution in the Configuring IP Connection for Multicontroller RNC document.

g
2

Configure two IP based routes towards the given WBTS for user plane traffic differentation. a) Configure IP based route for user plane 1 add ipbr ipbr-id 10 committed-bandwidth 17000 committed-dcnbandwidth 0 committed-sig-bandwidth 0 ipbr-name highprio-10 route-bandwidth 10000 scheduler-type none IP Plan Related object class: IPBR, IPRO RNC-xx/IP-1/IPBR-10 ipBasedRouteName = Iubipbr-10 routeBW = 10000 committedBW = 7000 committedDcnBW = 0 committedSigBW = 0 dspmProfileID = 0 (default) phbProfileID = 0 (default) schedulerType = virtual (none) RNC-xx/IP-1/OWNER-QNUP-0/IPRO-1-10.1.0.1-lo No attributes needed, default values applied b) Configure IP based route for user plane 2 add ipbr ipbr-id 20 committed-bandwidth 5000 committed-dcnbandwidth 0 committed-sig-bandwidth 0 ipbr-name lowprio-20 route-bandwidth 5000 scheduler-type none

Configure static routes in the mcRNC for different traffic types. It is assumed that all mcRNC VLANs are terminated in the site router. The site router IP addresses are the gateways for the respective egress RNC traffic types.

DN0988674

Id:0900d8058092ab8a Confidential

159

Activating and Verifying RU20 Features

a) Configure a static route for the user plane 1 VLAN between the mcRNC and WBTS. set routing node EIPU-0 static-route 10.3.50.0/30 nexthop gateway address 10.0.1.33 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on set routing node EIPU-1 static-route 10.3.50.0/30 nexthop gateway address 10.0.1.33 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on set routing node EIPU-0 static-route 10.3.50.0/30 nexthop gateway address 10.0.1.1 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 set routing node EIPU-1 static-route 10.3.50.0/30 nexthop gateway address 10.0.1.13 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on IP Plan Related object class: SRT4, ADR4GW RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/SRT4-10.3.50.0-30 nexthop = 2 (gateway) RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/SRT4-10.3.50.0-30/ADR4GW10.0.1.1 No attributes needed, default values applied RNC-xx/IP-1/OWNER-EIPU-0/RTINST-default/SRT4-10.3.50.0-30/ADR4GW10.0.1.33 No attributes needed, default values applied b) Configure a static route for the user plane 2 subnet between the mcRNC and WBTS. set routing node EIPU-0 static-route 10.3.60.0/30 nexthop gateway address 10.0.2.33 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on set routing node EIPU-1 static-route 10.3.60.0/30 nexthop gateway address 10.0.2.33 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on set routing node EIPU-0 static-route 10.3.60.0/30 nexthop gateway address 10.0.2.1 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on set routing node EIPU-1 static-route 10.3.60.0/30 nexthop gateway address 10.0.2.1 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on

160

Id:0900d8058092ab8a Confidential

DN0988674

Activating and Verifying RU20 Features

c) Configure a static route for the control plane subnet between the mcRNC and WBTS. set routing node EIPU-0 static-route 10.3.70.0/30 nexthop gateway address 10.0.3.33 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on set routing node EIPU-1 static-route 10.3.70.0/30 nexthop gateway address 10.0.3.33 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on set routing node EIPU-0 static-route 10.3.70.0/30 nexthop gateway address 10.0.3.1 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on set routing node EIPU-1 static-route 10.3.70.0/30 nexthop gateway address 10.0.3.1 bfd-detect-mult 4bfd-rx-interval 250 bfd-monitoring enabled bfd-tx-interval 250 on 4 Create BFD sessions. BFD configuration is optional. By configuring a BFD session an alarm is set if BFD session fails. a) Configure a BFD session for the user plane 1 traffic between the RNC and WBTS. add networking instance default bfd session /EIPU-0 srcaddr x.y.z.2 dstaddr 10.3.50.3 tx-interval 1000 rx-interval 1000 detect-mult 6 add networking instance default bfd session /EIPU-1 srcaddr x.y.z.2 dstaddr 10.3.50.3 tx-interval 1000 rx-interval 1000 detect-mult 6 b) Configure a BFD session for the user plane 2 traffic between the RNC and WBTS. add networking instance default bfd session /EIPU-0 srcaddr x.y.z.3 dstaddr 10.3.60.3 tx-interval 1000 rx-interval 1000 detect-mult 6 add networking instance default bfd session /EIPU-1 srcaddr x.y.z.3 dstaddr 10.3.60.3 tx-interval 1000 rx-interval 1000 detect-mult 6 5 6 Open the OMS Element Manager. Go to Tree View: Configuration Management j Network Topology j Tree View 7 Configure Iub IP based route identifiers in the RNC RNW Object Browser GUI. a) Open the relevant WBTS object.

DN0988674

Id:0900d8058092ab8a Confidential

161

Activating and Verifying RU20 Features

b) Assign the IP based route IDs to the given WBTS. Use the values of the IP based route IDs configured in step Configure two IP based routes towards the given WBTS for user plane traffic differentation. If you follow the exemplary configuration presented in this document, assign 10 to IP Based Route Id Iub (IPBasedRouteIdIub) and 20 to IP Based Route Id Iub 2 (IPBasedRouteIdIub2).

It is possible to configure one IP based route per WBTS in the RNC. In this case, only IP Based Route Id Iub must be configured. If there are two VLANs attached to one IP based route, IP Based Route Id Iub 2 does not need to be configured. If you plan two IP based routes per WBTS, IP Based Route Id Iub 2 can be configured only when IP Based Route Id Iub has been configured. IP Based Route Id Iub 2 is used only for user plane connections. IP Based Route Id Iub is mapped by the system to IP Based Route Identification (IPBasedRouteId) in the respective IPNB object and used during both user and control plane connections. While configuring IP Based Route Id Iub and IP Based Route Id Iub 2, use the IDs of the IP based routes that have already been configured via MML in the IPA platform. Configuration of IP Based Route Id Iub 2 with a nonexisting IP based route ID is not checked by the system and results with a failure of user plane transport bearer establishment. Configuration of IP Based Route Id Iub with a nonexisting IP based route ID results with the Error 17126 The IP based route ID cannot be found, as this ID is used by the IPNB object during CNBAP link creation. The control plane traffic uses only IP Based Route Id Iub.

The RNC type is not visible in WBTS. See the Steps for activating RAN1709: VLAN Traffic Differentiation on the WBTS. Expected outcome RAN1709: VLAN Traffic Differentiation has been activated.

162

Id:0900d8058092ab8a Confidential

DN0988674

Activating and Verifying RU20 Features

3.5.2

Verifying RAN1709: VLAN Traffic Differentiation


Purpose Follow the procedure to verify the feature RAN1709: VLAN Traffic Differentiation. Before you start The measurements M565 IP measurement on IP interface and M566 UDP measurement on IP interface support also the measuring of VLAN interfaces. These measurements can be used to verify the correctness of the activation. Steps

Start the M565 IP measurement on IP interface measurement with the RNW Measurement Management and RNW Measurement Presentation. Create a new measurement object for the M565 IP measurement on IP interface measurement. Choose the VLAN interfaces configured for the user plane traffic.

Make suitable calls through the relevant WBTS. The measurement object for the M565 IP measurement on IP interface measurement is updated every time the traffic generated by the given call is sent over any of the VLAN interfaces configured for the user plane traffic. a) Make an AMR, PS RT DCH, PS NRT DCH, or PS RT HSPA call. b) Make a PS NRT HSPA call.

Verify the allocation of the generated traffic to the proper VLAN interface. a) Stop the measurement. b) Verify if the traffic generated by the call has been allocated to the proper VLAN interface in accordance with the PHB profile configuration. If configured as presented in the given example in Activating RAN1709: VLAN Traffic Differentiation, the traffic generated by the PS NRT HSPA call should be sent over VL20 interface. It is assumed that the PHB=BE is configured only to PS NRT HSPA calls. The traffic generated by all the other types of calls should be sent over VL10 interface.

For more information on the PHB profile configuration, see step Configure two IP based routes towards the given WBTS for user plane traffic differentation. Expected outcome The feature RAN1709: VLAN Traffic Differentiation has been successfully activated.

DN0988674

Id:0900d80580903044 Confidential

163

Activating and Verifying RU20 Features

3.5.3

Deactivating RAN1709: VLAN Traffic Differentiation


Purpose Follow the procedure to deactivate the feature RAN1709: VLAN Traffic Differentiation. Steps

Reconfigure WBTS. Restore the old WBTS configuration so that all traffic types use the same IP address assigned to the Ethernet interface.

Reconfigure RNC. Restore the old RNC configuration so that only one IP based route is used by the user plane to reach the WBTS. Configure only one local IP address to be used by the user plane traffic. Configure only one remote IP addresses (the static route towards the given WBTS in the RNC routing table) to be used by both the user and control planes.

3 4

Open the OMS Element Manager. Go to Tree View: Configuration Management j Network Topology j Tree View

Reconfigure Iub IP based route identifiers. a) Open the relevant WBTS object. b) Assign only one IP based route to IP Based Route Id Iub (IPBasedRouteIdIub). c) Assign zero value to IP Based Route Id Iub 2 (IPBasedRouteIdIub2), which means that the IP based route is not defined.

Uninstall the license in the WBTS. Expected outcome The feature RAN1709: VLAN Traffic Differentiation has been deactivated for the relevant WBTS.

164

Id:0900d805808f8bcd Confidential

DN0988674

Activating and Verifying RU20 Features

3.6
3.6.1

Activating RAN1749: BTS Firewall


Activating BTS Firewall
Purpose Follow the procedure to activate the feature RAN1749: BTS Firewall. For more information on the feature, see RAN1749: BTS Firewall in WCDMA RAN, rel. RU20, Feature Descriptions. Before you start For Iub/Ethernet traffic protection, RAN1749: BTS Firewall requires one of the following features as prerequisite: RAN74: IP Based Iub for Flexi WCDMA BTS RAN1634: IP Based Iub for UltraSite WCDMA BTS RAN1449: Dual Iub for Flexi WCDMA BTS RAN1633: Dual Iub for UltraSite WCDMA BTS

The feature RAN1701: AXCF unit for UltraSite WCDMA BTS is required to provide hardware support in UltraSite WBTS. Steps 1 Enable ICMP Echo Replay in the WBTS. a) b) c) d) Open the BTS Site Manager. In the left navigation bar choose the IP tab. In the IP control panel choose the Security tab. Check the Enable ping and traceroute box.

By default, the ICMP Echo Replay is disabled.

For more information on IP filtering in the Flexi WBTS, see Inspecting and modifying IP filtering settings in Integrating and configuring Flexi WCDMA BTS transmission. For more information on IP filtering in the AXC, see Configuring BTS Firewall in Commissioning AXC.

DN0988674

Id:0900d8058083aa97 Confidential

165

Activating and Verifying RU20 Features

3.6.2

Verifying BTS Firewall


Before you start Make sure the ICMP Echo Replay is enabled. Steps

Verify the enabling of the ICMP Echo Reply. From a remote or local host ping one of the IP addresses configured in the WBTS. Expected outcome If you have received a ping replay from the WBTS, the ICMP Echo Reply has been enabled.

166

Id:0900d805806fcd7e Confidential

DN0988674

Activating and Verifying RU20 Features

3.6.3

Deactivating BTS Firewall


Steps

Disable ICMP Echo Replay in the WBTS. a) b) c) d) Open the BTS Site Manager. In the left navigation bar choose the IP tab. In the IP control panel choose the Security tab. Uncheck the Enable ping and traceroute box.

DN0988674

Id:0900d805806fcd7f Confidential

167

Activate and verify operability and transport features

Activating and Verifying RU20 Features

4 Activate and verify operability and transport features


4.1 Activating RAN1174: Secure AXC NWI3 Management Interface
Activating RAN1174: Secure AXC NWI3 Management Interface
Purpose Follow the procedure below to activate the RAN1174: Secure AXC NWI3 Management Interface feature.

4.1.1

Activating the feature might cause temporary downtime during the re-establishment of the BTS O&M interface connections. Setting the TLS operating mode to Forced disconnects the currently open insecure interface connections. Setting the TLS operating mode to Off disconnects the currently opened secure connections. Extra load is caused by the Transport Layer Security (TLS) Protocol handshake procedure when the secure BTS O&M interface connections are set up.

Before you start This feature belongs to the application software and is under license key management.

Before the RAN1174: Secure AXC NWI3 Management Interface feature can be activated in the RNC, the license (a file including the feature information) must be transferred to and installed in the OMS. Before activating the feature, download the license for feature with feature code 1244 from Nokia Online Services (NOLS). For information on how to activate the license for the feature with the feature code 1244 in the OMS, see Activating RAN1102: Secure BTS Management Interface. For more information on license management in OMS, see Licensing. The TLS Handshake procedure requires that peer network elements present valid endentity certificates on secure BTS O&M connection attempt. The procedure described in this document assumes that private keys and end-entity certificates have been already installed to the AXC and NetAct. For more information, see Managing security with RNC OMS, Activating RAN1102: Secure BTS Management Interface, and NetAct documentation. For more information on the AXC certificate installation, see Commissioning AXC, Installing CA certificates manually and Installing AXC Certificate and AXC private key manually section.

168

Id:0900d8058090d77e Confidential

DN0988674

Activating and Verifying RU20 Features

Activate and verify operability and transport features

Steps 1 2 Start the man-machine interface (MMI) Activate RAN1174: Secure AXC NWI3 Management Interface feature: for IPA-RNC, type the following MML command: ZW7M:FEA=1244:ON; for mcRNC, type the following SCLI command: set license feature-mgmt id 0000001244 feature-admin-state on

Expected outcome The RAN1174: Secure AXC NWI3 Management Interface feature has been activated.

DN0988674

Id:0900d8058090d77e Confidential

169

Activating and Verifying RU20 Features

4.1.2

Verifying RAN1174: Secure AXC NWI3 Management Interface


Purpose Follow the procedure below to verify that the activation of the RAN1174: Secure AXC NWI3 Management Interface feature has been successful. Steps

1 2

Start the man-machine interface (MMI) Verify the feature activation in the RNC: for IPA-RNC, type the following MML command: ZW7I:FEA,FULL:FEA=1244; for mcRNC, type the following SCLI command: show license feature-mgmt id 0000001244

Expected outcome If the feature has been activated FEATURE STATE parameter value is set to ON

170

Id:0900d80580902105 Confidential

DN0988674

Activating and Verifying RU20 Features

4.1.3

Deactivating RAN1174: Secure AXC NWI3 Management Interface


Purpose Follow the procedure below to deactivate the RAN1174: Secure AXC NWI3 Management Interface feature. Steps

1 2

Start the man-machine interface (MMI) Dectivate RAN1174: Secure AXC NWI3 Management Interface feature: for IPA-RNC, type the following MML command: ZW7M:FEA=1244:OFF; for mcRNC, type the following SCLI command: set license feature-mgmt id 0000001244 feature-admin-state off

Expected outcome The RAN1174: Secure AXC NWI3 Management Interface feature has been deactivated.

DN0988674

Id:0900d80580902103 Confidential

171

Activating and Verifying RU20 Features

4.2
4.2.1

Activating RAN1298 and RAN1299: BTS plug-and-play


Activating RAN1298: BTS auto connection
Purpose Follow the procedure below to activate RAN1298: BTS auto connection feature. Before you start Restart of the RNC and the BTS is not required after activation of this feature. 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. To check if the RNC license is activated, use the W7I command. For more information on using the command, see W7 - Licence and Feature Handling. Before a licensed feature can be activated, the license must be transferred to and installed in the RNC. For information on transferring the license to the RNC, see License management operations in RNC in WCDMA RAN license management. You can install the license 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. For information on license management in NetAct, see Managing Licenses, License Manager Help, Licence Manager Technical Reference Guide, and Licence Manager problems in Troubleshooting System Management Problems in Nokia Siemens Networks NetAct documentation.

BTS plug-and-play feature requires that RAN1299: BTS auto configuration feature license is activated in NetAct. If you use the MMI, you must also set the feature state (ON/CONFIG/OFF). In new installations, the default state is OFF. For the specific instructions on the license installation in the RNC, see W7L INSTALL OR UPDATE LICENCE in W7 - Licence and Feature Handling. For more information on license management, see License management principles, and License management in WCDMA RAN. To set the feature state, use the following command: ZW7M:FEA=<feature code>:<feature state>

g
1 2

The feature code for this feature is 1479. Steps Start the man-machine interface (MMI) Use ZW7M:FEA=1479:ON; MML command to activate the feature Expected outcome RAN1298: BTS auto connection feature has been activated. Use W7I:FEA,FULL:FEA=1479; MML command to verify if the feature has been activated. If the feature has been activated FEATURE STATE parameter value is set to ON

172

Id:0900d8058083aa9c Confidential

DN0988674

Activating and Verifying RU20 Features

< ZW7I:FEA,FULL:FEA=1479; LOADING PROGRAM VERSION 1.20-0 FEATURE INFORMATION: ---------------------------------------------FEATURE CODE:..............1479 FEATURE NAME:..............RAN1298 BTS Auto Connection FEATURE STATE:.............ON COMMAND EXECUTED

DHCP server in RNC needs to be configured before BTS Auto-Connection can be started, see Configuring DHCP server on RNC in Configuring IP connection for RNC. DHCP Server Settings in RNC - Example Figure 12 presents a simplified example of an RNC, WBTS and CA/CR server. The IP adresses in the figure correspond to the MML printouts in this chapter.

CA/CR 172.16.67.108

RNC
OMU

172.16.67.105

172.16.67.110 (IFFE0) NPGEP-0/1 172.16.58.129 (VL968) DHCP pool for VL968 172.16.58.138 172.16.58.142

WBTS
Figure 12 ZUSI:OMU; LOADING PROGRAM VERSION WORKING STATES OF UNITS 11:22:01 UNIT OMU-0 PHYS LOG 6.17-1 RNC, WBTS, CA/CR settings

2010-04-30

STATE SP-EX

INFO -

0000H 4002H

DN0988674

Id:0900d8058083aa9c Confidential

173

Activating and Verifying RU20 Features

OMU-1

0001H 4002H

WO-EX

NUMBER OF UNITS DISPLAYED = 2

COMMAND EXECUTED

WORKING STATE AND RESTART HANDLING COMMAND <US> < ZUSI:NPGEP; LOADING PROGRAM VERSION WORKING STATES OF UNITS 11:22:06 UNIT NPGEP-0 NPGEP-1 PHYS LOG STATE WO-EX SP-EX INFO 6.17-1 2010-04-30

0025H 48DFH 0041H 48DFH

NUMBER OF UNITS DISPLAYED = 2

COMMAND EXECUTED

WORKING STATE AND RESTART HANDLING COMMAND <US_>

ZQRI:OMU,1;

LOADING PROGRAM VERSION 6.15-0

RNC

IPA2800

2010-04-30

11:22:18

IINTERROGATING NETWORK NTERFACE DATA

IIF UNIT NAME

ADM STATE

FRAG MTU

IF

ADDR TYPE IP ADDR

SUPP PRIO TYPE

------------------- ------------- ------------ ------------------- ---------------- ---------- ----------OMU-1 EL0 UP 1500 Y -L 172.16.6 7.105/28

COMMAND EXECUTED

174

Id:0900d8058083aa9c Confidential

DN0988674

Activating and Verifying RU20 Features

TCP/IP STACK DATA HANDLING COMMAND <QR_> < MAIN LEVEL COMMAND <___> <QRI:NPGEP,0;

LOADING PROGRAM VERSION 6.15-0

RNC

IPA2800

2010-04-30

11:22: 43

INTERROGATING NETWORK INTERFACE DATA

IF UNIT NAME

ADM STATE

FRAG MTU

IF SUPP TYPE PRIO

ADDR TYPE IP ADDRESS

-------------- ----------- ------------ ------------------- --------- ------------ ----------------------------NPGEP-0 IFAI0 IFAI1 IFFE0 IFGE0 IFGE1 LO0 VL968 UP UP UP UP UP UP UP 1500 Y 1500 Y 1500 Y 1500 Y 1500 Y 1500 Y 1500 Y U U L L L L L L L 172.16.70.178/30 172.16.58.129/28 172.16.70.178/32 172.16.70.194/32 172.16.67.110/28

COMMAND EXECUTED

TCP/IP STACK DATA HANDLING COMMAND <QR_> <ZQKB:OMU,1;

LOADING PROGRAM VERSION 6.15-0

RNC

IPA2800

2010-0430

11:23: 24

INTERROGATING STATIC ROUTES ROUTE

DN0988674

Id:0900d8058083aa9c Confidential

175

Activating and Verifying RU20 Features

UNIT

DESTINATION

GATEWAY

ADDRESS TYPE Prefere nce NBR

----------------------------- ----------------------- ------------------- ------------OMU-1 OMU-1 OMU-1 DEFAULT ROUTE 172.16.71.0/24 172.16.67.97 LOG

-------- -------0 0 0 1 85 115

172.16.67.110 LOG

172.16.58.128/27 172.16.67.110 LOG

COMMAND EXECUTED IP ROUTING DATA HANDLING COMMAND <QK_> < MAIN LEVEL COMMAND <___>

<

? ..... O ..... C: ..... Q: ..... D: ..... K: ..... B: ..... L: ..... N: ..... I: ..... T: ..... A: ..... S: ..... G: ..... Z: .....

DISPLAY MENU MANAGE DHCP SERVER STATUS CONFIGURE IP ADDRESS POOL INTERROGATE IP ADDRESS POOL DELETE IP ADDRESS POOL MANAGE IP ADDRESS RANGE LIST MANAGE POOL BINDING INFORMATION INTERROGATE POOL BINDING INFORMATION CONFIGURE DHCP SERVER OPTIONS INTERROGATE DHCP SERVER OPTIONS MANAGE DHCP SERVER CLIENT STATUS INTERROGATE DHCP CLIENT DYNAMIC INFORMATION MANAGE DHCP SERVER LOGS DISPLAY LOG INFORMATION RETURN TO MAIN LEVEL

DHCP SERVER DATA HANDL COMMAND <Q9_> <Q;

176

Id:0900d8058083aa9c Confidential

DN0988674

Activating and Verifying RU20 Features

INTERROGATE POOL INFORMATION

POOL ID

POOL NAME SUBNET/MASK

GATEWAY

RANGE

-------------------- ------------------ ----------------------1 BTSDHCP 172.16.58.128/28

------------------- -------------172.16.58.129 172.16.58.138 >172.16.58.142

Q9L:;

INTERROGATE POOL BINDING INFORMATION

POOL ID

POOL NAME

UNIT

IF NAME

-------------------- ------------------ ----------------------1 BTSDHCP

------------------- -------------NPGEP-0 VL968

COMMAND EXECUTED

Q9I:;

LOADING PROGRAM VERSION 1.19-0

INQUIRE DHCP VENDOR OPTION IP PARAMETER INFORMATION:

CA/CMP CERTIFICATE O&M MEDIATOR CA/CMP SERVER SERVER ----------------------- ------------------------- ----------------172.16.67.105 172.16.67.108 8080

CERTIFICATE PORT REPOSITORY REPOSITORY ------------------- --------------------172.16.67.108 389

COMMAND EXECUTED

DN0988674

Id:0900d8058083aa9c Confidential

177

Activating and Verifying RU20 Features

4.2.2

Verifying RAN1298: BTS auto connection


Purpose Follow the procedure below to verify that the activation of the RAN1298: BTS auto connection feature has been successful. Steps

1 2

Open the RNC RNW object browser from application launcher Open WBTS object, then check if Auto Connection HW ID (Auto Connection Hardware ID) or Site ID (Auto Connection Site ID) parameter fields are active. Double click on RNC object if WBTS objects cannot be seen.

Figure 13

The BTS object

178

Id:0900d805807138b5 Confidential

DN0988674

Activating and Verifying RU20 Features

Figure 14

Auto Connection HW ID and Site ID parameters

DN0988674

Id:0900d805807138b5 Confidential

179

Activating and Verifying RU20 Features

4.2.3

Deactivating RAN1298: BTS auto connection


Purpose Follow the procedure below to deactivate RAN1298: BTS auto connection feature. Steps

1 2

Start the man-machine interface (MMI) Use ZW7M:FEA=1479:OFF; MML command to deactivate the feature Expected outcome RAN1298: BTS auto connection feature has been deactivated Use ZW7I:FEA,FULL:FEA=1479; MML command to verify if the feature has been deactivated. If the feature has been deactivated FEATURE STATE parameter value is set to OFF < W7I:FEA,FULL:FEA=1479; LOADING PROGRAM VERSION 1.20-0 FEATURE INFORMATION: ---------------------------------------------FEATURE CODE:..............1479 FEATURE NAME:..............RAN1298 BTS Auto Connection FEATURE STATE:.............OFF COMMAND EXECUTED

180

Id:0900d805807138b7 Confidential

DN0988674

Activating and Verifying RU20 Features

4.2.4

Activating BTS Auto connection and Auto configuration through the NetAct About this chapter
This section provides you information on how to check if all requirements needed for BTS auto connection and BTS auto configuration are met on the NetAct site. For instructions on manual connection and manual activation of WBTS, see Plan-based roll-out method in Rolling out the WCDMA RAN . For instructions on using BTS Auto connection and BTS Auto configuration features, see Rolling out the WCDMA RAN document. This section is intended for operators and administrators of radio networks, and anyone requiring information about the activation procedure of the BTS Auto connection and BTS Auto configuration features.

4.2.4.1

NetAct compatibility and capacity information


For information on NetAct system and capacity, and the compatibility between NetAct and network element releases, see the NetAct compatibility and capacity information document.

4.2.4.2

Preconditions and requirements


Auto connection and Auto configuration features are supported only by FlexiBTS. FlexiBTS version WN6.0 and onwards support these features. The following NetAct tools are used in the operations: CM Editor CM Operations Manager (Workflow Engine, Plan Actual Compare) Software Manager

Before starting to use BTS Auto connection and BTS Auto configuration features, the following preconditions have to be met: BTS auto connection license is active in the RNC under which you want to auto connect the BTS. BTS auto configuration license is active in NetAct. RNC software version is updated to RN5.0 level. Autotriggering of WBTS auto configuration is enabled (optional). E-mail notification properties are configured (optional). It is up to Operator to decide whether he wants to have E-mail notification or not. Auto Configuration Report is available. Additionally, the following licenses are active in the NetAct:

DN0988674

Id:0900d805807138b9 Confidential

181

Activating and Verifying RU20 Features

Sales item WBTS Autoconfiguration for 3G Remote Site Configuration Management for 3G FlexiTRS Parameter Management XML interface for radio access planning data CM Editor for RAN CM Operations Manager for RAN CM Workflow Engine Table 15

license name CM_MGMT_3G_AUTOCONFIGURAT ION CM_MGMT_3G_SITE_CONFIGURAT ION CM_FLEXI_TRS XML_RA_PLAN_IF CM_EDITOR_RAN CM_OPMGR_RAN CM_WORKFLOW

licenses needed for BTS auto configuration.

The following licenses are recommended to be active in the NetAct: Sales item RNC ATM/IP Management Direct activation for RNC Plan Actual Compare 3G Table 16 license name CM_RNC_ATM_IP CM_RNC_DIRECT_ACTIVATION PLAN_ACTUAL_COMPARE_3G

licenses recommended for BTS auto configuration

Chapters below give instructions on how to check these preconditions.

Checking BTS Auto connection feature license


This procedure describes how to check if the license for Auto connection feature is active in RNC. Before checking that the needed option is available, upload the latest option information from the RNC. To check BTS auto connection options 1. Open CM Operations Manager. 2. Select Upload New Upload. Expected outcome The Upload dialog opens. 3. Select all the RNC(s) which you want to upload.

182

Id:0900d805807138b9 Confidential

DN0988674

Activating and Verifying RU20 Features

Figure 15

Upload dialog

4. Click Start to start the upload operation. For more information, see CM Operations Manager Help. 5. After upload is done, open CM Editor. 6. In the Actual Configuration node select the RNC under which you want to perform the auto connection and auto configuration. 7. Check if the BTS Auto Connection option is visible in the RNC Options parameter.

DN0988674

Id:0900d805807138b9 Confidential

183

Activating and Verifying RU20 Features

Figure 16

BTS Auto Connection option under the RNC Options parameter

If the BTS Auto Connection option is visible under the RNC Options parameter, the auto connection service is activated in the RNC. If the auto connection option is not visible, you need to purchase the auto connection option from Nokia Siemens Networks.

Checking BTS Auto configuration feature license


This chapter provides instructions on how to check the status of BTS Auto configuration feature license.

g g

Auto configuration feature is supported only by FlexiBTS. For further information about BTS Auto configuration feature, see Configuring WCDMA FlexiBTS Using Auto Connection and Auto Configuration document. You cannot rely on that if auto connection license exists (in RNC) then also auto configuration license is active in Configurator. You have to check the auto configuration license status separately. To check BTS Auto configuration feature license 1. Login to Connectivity Server as omc user. 2. Open lmdlicmx.dat license file by running the following command:

184

Id:0900d805807138b9 Confidential

DN0988674

Activating and Verifying RU20 Features

less /etc/opt/nokia/oss/common/conf/lmdlicmx.dat The lmdlicmx.dat license file lists all active licenses in the system. 3. Check if the licenses needed for BTS auto configuration exist in the lmdlicmx.dat license file.

Example of the license entry in the lmdlicmx.dat license file: # RAC OSSWxx51 TBD / Configuring and Optimising / Radio Access Configurator / CM Operations Manager RACPMG FEATURE CM_MGMT_3G_AUTOCONFIGURATION lmdntcmx 50.000 01-jan-0 0 4D2BC06FC8067A717740 \ HOSTID=ANY ck=17 license entry has the following structure: <sales item> / <functionality area> / <system component> / <feature name> 4. Close the lmdlicmx.dat license file, by putting the following command: q

Checking the version of RNC software


In order to support Auto connection and Auto configuration features, the RNC(s) under which you want to perform BTS auto connection and BTS auto configuration should have the RN5.0 software package installed. This section describes how to check that the RNC is updated to RN5.0 level. Checking the status of RNC software can be done by using Software Manager or CM Editor.

It is recommended to use Software Manager to check software version of more than one RNC at the same time. To check the RNC software (with NetAct Software Manager) 1. Open NetAct Software Manager. 2. Select RNC as the NE type from the Show: drop-down list. 3. Select the appropriate parent network from the Parent tab. Expected outcome The network elements under the selected parent are displayed in the Network elements table on the right-hand side. 4. From the Network elements table select the network elements in which the Auto configuration feature will be activated. 5. Open the New Task tab at the bottom of the pane. The selected network elements are shown in the Selected network elements table on the right-hand side. 6. Select upload from the Task type drop-down list. 7. Click the Start Task button to continue. Expected outcome The software information upload starts. You can follow the progress of the upload operation in the Tasks tab. 8. Go to the Network SW Status tab. 9. From the Network elements table, check if all selected RNC(s) have the required software package installed.

DN0988674

Id:0900d805807138b9 Confidential

185

Activating and Verifying RU20 Features

Figure 17

Software Manager view

If the required software packages have not been installed on all necessary RNCs, you need to download and activate appropriate software packages. For instructions, see Software Manager Help. To check the RNC software (with CM Editor) 1. Open CM Editor. 2. In the Actual Configuration node move your mouse cursor on top of the RNC under which you want to perform the auto connection and auto configuration. 3. Wait until hint window is shown. Hint window shows the RNC software version.

4.2.4.3

Enabling autotriggering of WBTS auto configuration (optional)


This section gives instructions on activating the autotriggering of workflow operations in order to commission WBTS without operator user attention.

This functionality is optional. You can perform this operation manually by using BTS configuration trigger workflow in CM Operations Managers Workflow Engine. For more information, see chapter Triggering a BTS auto configuration polling mechanism in Configuring WCDMA FlexiBTS Using Auto Connection and Auto Configuration document. To enable autotriggering of WBTS auto configuration 1. Login to Connectivity Server as omc user. 2. Open crontab file by running the following command: crontab -e

186

Id:0900d805807138b9 Confidential

DN0988674

Activating and Verifying RU20 Features

3. Add new line at the end of the crontab file: 0,15,45 * * * * /bin/bash -lc "racclimx.sh -v -opsFile /etc/opt/nokia/oss/rac5.0/conf/opdefs/ops/operations/bts_auto_conf_trigger.xml -op 'BTS auto configuration trigger'" 4. Save and exit crontab file, by running the following command: :qw! Expected outcome crontab: installing new crontab

4.2.4.4

Configuring e-mail notification (optional)


This section describes how to configure e-mail notification functionality. After performing the following procedure, the NetAct system will be able to notify the user about the status of BTS auto connection and auto configuration by sending notification e-mails. This procedure has two main steps: Configuration of SMTP (Simple Mail Transfer Protocol) server in LDAP Configuration of e-mail notification recipients list

To configure the SMTP (Simple Mail Transfer Protocol) server in LDAP 1. Login to DS-1 server as root user. 2. Add the FQDN of SMTP server in /etc/ClusterConfig.xml file. <SMTP Setup="yes" FQDN="mailserver.rc502040.netact.noklab.net"/>

In the above tag, the attribute value mailserver.rc502040.netact.noklab.net should be replaced with adequate domain name of the mail server. 3. Configure the SMTP server entry in LDAP either for adding or deleting using the following steps: To add an entry to LDAP, perform the following steps: In the /tmp directory, create ADD_mail.xml file with the following content:

In the above step, the ADD_mail.xml file is only an example. You can create an xml file with any name.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <LDAPContent> <LDAPEntry Type="Modify" DN="cn=cluster,ou=config,ou=region-502040, ou=regions,ou=netact,dc=noklab,dc=net" Overwrite="No"> <!--Note: In the above tag, the string value "502040" should be replaced with adequate Cluster ID.--> <Attr Name="ossSmtpFQDN" Changetype="add" Value="mailserver.rc502040.netact.noklab.net"/> <!--Note: In the above tag, the attribute value "mailserver.rc502040.netact.noklab.net" should be replaced with adequate domain name of the mail server.--> </LDAPEntry>

DN0988674

Id:0900d805807138b9 Confidential

187

Activating and Verifying RU20 Features

</LDAPContent> Add the following entry to LDAP using the xml file created: /opt/nokia/oss/bin/XML2LDAP.pl --install --file /tmp/ADD_mail.xml

To delete an entry from LDAP, perform the following steps: In /tmp directory, create DEL_mail.xml with the following content:

In the above step, the DEL_mail.xml file is only an example. You can create an xml file with any name.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <LDAPContent> <LDAPEntry Type="Modify" DN="cn=cluster,ou=config,ou=region-502040, ou=regions,ou=netact,dc=noklab,dc=net" Overwrite="No"> <!--Note: In the above tag, the string value "502040" should be replaced with adequate Cluster ID.--> <Attr Name="ossSmtpFQDN" Changetype="delete" Value="mailserver.rc502040.netact.noklab.net"/> <!--Note: In the above tag, the attribute value "mailserver.rc502040.netact.noklab.net" should be replaced with adequate domain name of the mail server.--> </LDAPEntry> </LDAPContent> Remove the following entry from LDAP using the created xml file: /opt/nokia/oss/bin/XML2LDAP.pl --install --file /tmp/DEL_mail.xml 4. Check the SMTP entry in LDAP by executing the following command: ldapacmx.pl -directQuery "cn=cluster" |grep ossSmtpFQDN The following is the output: ossSmtpFQDN=mailserver.rc502040.netact.noklab.net To create an e-mail notification sending list 1. Login to Data Storage Server as omc user. 2. Open the /etc/opt/nokia/oss/custom/conf/autoconfiguration_recipients file by running the following command: vim /etc/opt/nokia/oss/custom/conf/autoconfiguration_recipients

If there is no file, create a new one by running the following command: touch /etc/opt/nokia/oss/custom/conf/autoconfiguration_recipients 3. Add appropriate e-mail address(es) to which you want to send the e-mail notification.

g
188

Add one e-mail address per line.

Id:0900d805807138b9 Confidential

DN0988674

Activating and Verifying RU20 Features

4. Save and exit the autoconfiguration_recipients file by running the following command: :qw!

4.2.4.5

Auto Configuration Report


Auto Configuration Report is a web-based application which allows you to view status of auto configuration of the WBTS(s) in the network. The configuration of Auto Configuration Report user account does not require any specific steps on the NetAct site. The only thing that need to be done is the first time login to the application. To open Auto Configuration Report 1. In the web browser, enter the following URL: http://<clustername>.netact.noklab.net/RAC_cmpser/report where <clustername> stands for the host name that has been assigned to the LinAS server. If not known, contact your system administrator. 2. Fill in the Username and Password field. 3. Click Login button to enter the Auto Configuration Report.

Steps 2 and 3 are required only during the first use the application unless you use the logout function. To exit Auto Configuration Report To exit the Auto Configuration Report use one of the following alternatives: a) Close the web browser. b) Click the logout button (to force login operation during the next Auto Configuration Report opening) and close the web browser.

4.2.4.6

Where to find more information


When you perform the tasks described in this section, you may need to refer to other documents for further information. The document list given below contains useful documents and a brief description of their contents. Help documents For more information on using Software Manager, see Software Manager Help. For more information on using CM Operation Manager, see CM Operations Manager Help. For more information on using license Manager, see license Manager Help .

DN0988674

Id:0900d805807138b9 Confidential

189

Activating and Verifying RU20 Features

4.3

Feature RAN1453: Iu Link Break Protection, Feature Activation Manual


Activating RAN1453: Iu Link Break Protection
Purpose Follow the procedure below to activate the Iu Link Break Protection feature in the RNC. Before you start Before activating Iu Link Break Protection, make sure that features Multiple CN and Flexible Iu are not active. This feature belongs to application software. Ensure that you have a valid license. This feature is under license key management. Before licensed feature(s) can be activated, the license (a file including the feature information) must be transferred to and installed in the RNC. The license can be installed by using NetAct or a local MML interface. If the installation is done using NetAct, the feature(s) covered by the license are automatically set to the ON state. If the installation is done using the MML interface, the feature state (ON/OFF/CONFIG) must be set by the user. In new installations, the default state is OFF. Before activating the feature, set the feature state to ON. For more information on feature states, see Section Installing licenses in the network element in License-based Feature Management. Licenses or features can be handled using the commands of the W7 command group. For more information, see W7 - license and Feature Handling. Steps

4.3.1

1 2 3 4

Start the OMS Element Manager. Select Configuration Management -> Network Topology -> Tree View. Click the "+" symbol to expand the objects. Modify the related parameters. The following parameters define the length of delay taking place before the Iu link state change is handled when only one Core Network (CN) service is unavailable: IuBarringDelayTimerCS (Iu Barring Delay Timer for CS) in IUCS object IuBarringDelayTimerPS (Iu Barring Delay Timer for PS) in IUPS object

The following parameters define the number of cells for which the System Information Block (SIB) information is updated at a time when the CN service recovers: IuBarringRecoveryGroupCS (Iu Barring Recovery Group for CS) in IUCS object IuBarringRecoveryGroupPS (Iu Barring Recovery Group for PS) in IUPS object

190

Id:0900d8058090d786 Confidential

DN0988674

Activating and Verifying RU20 Features

Further information For more information on the parameters, see WCDMA Radio Network Configuration Parameters. Note that if any of the features Multi-operator RAN, Multiple CN, or Flexible Iu is activated, the Iu barring is not longer delayed. Expected outcome The Iu Link Break Protection feature is activated. Note that the change comes into effect during the 10-minute period following the activation or when the next Iu link state changes. Further information After activating, there is no need to reset the RNC.

DN0988674

Id:0900d8058090d786 Confidential

191

Activating and Verifying RU20 Features

4.3.2

Verifying RAN1453: Iu Link Break Protection


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

g
1

Take the IuCS as an example. The IuPS is the same. Steps Monitor the link between the RNC and the BTS. You can monitor the NBAP message using a message monitoring tool (for example: wireshark or nethawk).

2 3

Disconnect the IuCS link. Check that the SIB1 was sent on the Iub interface within the timer range set in parameter IuBarringDelayTimerCS. Recover the IuCS link. Check that the SIB was sent on the Iub interface based on the cell groups setting in parameter IuBarringRecoveryGroupCS. The first SIB is sent to the first cell group as soon as the IuCS link is recovered. The next SIB is sent to the second cell group after a specific timer-defined interval and so on for any remaining groups.

4 5

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

192

Id:0900d80580858322 Confidential

DN0988674

Activating and Verifying RU20 Features

4.3.3

Deactivating RAN1453: Iu Link Break Protection


Purpose Follow the procedure below to deactivate the Iu Link Break Protection feature in the RNC. Steps

1 2 3 4

Start the OMS Element Manager. Select Configuration Management -> Network Topology -> Tree View. Click the "+" symbol to expand the objects. Set the length of the delays to 0. Define the length of the delays with one of the following parameters: IuBarringDelayTimerCS (Iu Barring Delay Timer for CS) in IUCS object IuBarringDelayTimerPS (Iu Barring Delay Timer for PS) in IUPS object Further information For more information on the parameters, see WCDMA Radio Network Configuration Parameters. Expected outcome The Iu Link Break Protection feature is deactivated. Note that the change comes into effect during the 10-minute period following the deactivation or when the next Iu link state changes. Further information After deactivating, there is no need to reset the RNC.

DN0988674

Id:0900d8058081b1a7 Confidential

193

Activating and Verifying RU20 Features

4.4
4.4.1

Activating RAN1461: RNC RNW alarm reduction


Activating RAN1461: RNC RNW alarm reduction
Purpose Follow the procedure below to activate the following functions of the RAN1461: RNC RNW alarm reduction feature. 1. WBTS-level fault indication 2. Suspend mode

This feature is optional; therefore, no licensing is applied. This feature is active by default and can be deactivated manually.

Steps 1 Open the connection to the required IPA-RNC or mcRNC IP address to start the ManMachine Interface (MMI) or Structured Command Line Interface (SCLI) respectively. Make sure you are logged into the fsclish interactive mode. The default user account of the mcRNC logs into that mode automatically. To log into fsclish interactive mode manually, use the fsclish command. To activate the WBTS-level fault indication, change the PRFILE parameter 016:0009 value to 1. For IPA-RNC use the MML command of: ZWOC:16,9,1; For mcRNC use the SCLI command of: set app-parameter configurationparameter class 16 number 9 value 1

To activate the RNW alarm system Suspend mode, change the PRFILE parameter 016:0010 value to 1. For IPA-RNC use the MML command of: ZWOC:16,10,1; For mcRNC use the SCLI command of: set app-parameter configurationparameter class 16 number 10 value 1

This change affects handling of faults generated after the alarm change. If the number of alarms during the Suspend mode activation time exceeds the defined limit for a certain fault type group, and when a new alarm of that group is received and assigned a suspended status, the alarm indicating the Suspend mode activation is set on.

194

Id:0900d8058090d788 Confidential

DN0988674

Activating and Verifying RU20 Features

Expected outcome The WBTS-level fault indication function and the Suspend mode function of RAN1461: RNC RNW alarm reduction feature have been activated. Alarm change after the functions are switched to active: WBTS-level fault indication switched to active The activation affects only alarm setting for the BTS-level failures raised after the functionality is switched to active. Currently active WCEL alarms remain active, and no WBTS-level alarms are set for sites that had failures before the activation of the feature. Suspend mode switched to active The Suspend mode alarm 2881 RNW ALARM SYSTEM SUSPEND MODE ACTIVATED is set only if a new alarm is set and the new alarm is assigned the suspended status.

DN0988674

Id:0900d8058090d788 Confidential

195

Activating and Verifying RU20 Features

4.4.2

Verifying RAN1461: RNC RNW alarm reduction


Purpose Follow the procedure below to verify that the activation of the following functions of the RAN1461: RNC RNW alarm reduction feature has been successful. 1. WBTS-level fault indication functionality 2. The Suspend mode functionality

Steps

Verifying these functions requires an RNC with at least one working BTS site with multiple WCELs in working state (WO state). During the verification procedure the WCELs are disabled and thus the BTS becomes unavailable for traffic.

Verifying WBTS-level fault indication functionality 1 Ensure that WBTS-level fault indication is active. For details see Activating RAN1461: RNC RNW alarm reduction, section 1. 2 Simulate C-NBAP link break between the RNC and the BTS, for example, by breaking the transmission connection between these elements. Wait one minute. Restore the transmission between the RNC and the BTS. Wait one minute.

3 4 5

Expected outcome After executing step 3, alarm 7786 WCDMA BASE STATION OUT OF USE is set to active and 77xx alarms are not raised for the WCEL objects that were in WO state prior to the transmission break. After executing step 6, alarm 7786 should no longer be active, and all the WCELs under the BTS should be restored to WO state.

196

Id:0900d80580903b21 Confidential

DN0988674

Activating and Verifying RU20 Features

Steps Verifying the Suspend mode functionality 1 Open the connection to the required IPA-RNC or mcRNC IP address to start the ManMachine Interface (MMI) or Structured Command Line Interface (SCLI) respectively. Switch off the WBTS level fault indication. For details see Activating RAN1461: RNC RNW alarm reduction, section 4. This allows to generate enough WCEL alarms in a small environment. 3 Ensure that the Suspend mode is on. For details see Activating RAN1461: RNC RNW alarm reduction, section 1. 4 Change the PRFILE parameter 016:0011 value to be low enough for activating the Suspend mode in the system. The value should be lower than the number of working WCELs available in the verification environment. 5 Simulate a C-NBAP link break for a BTS site (or multiple sites) so that more WCELs are dropped from WO state. Wait three minutes. Restore C-NBAP link(s). Wait three minutes.

6 7 8

Expected outcome After executing step 6, alarm 2881 RNW ALARM SYSTEM SUSPEND MODE ACTIVATED is raised. After executing step 8, alarm 2881 should no longer be active.

DN0988674

Id:0900d80580903b21 Confidential

197

Activating and Verifying RU20 Features

4.4.3

Modifying RAN1461: RNC RNW alarm reduction functionality


Purpose Follow the procedure below to modify the following feature of the RAN1461: RNC RNW alarm reduction feature. 1. Individual fault type limits 2. Threshold limit For the RNW alarm system Suspend mode, it is possible to change the limit values for individual fault types that can trigger the Suspend mode, and also the threshold value that controls writing of the buffered alarms in the system to the alarm system database in the RNC.

Steps 1 Open the connection to the required IPA-RNC or mcRNC IP address to start the ManMachine Interface (MMI) or Structured Command Line Interface (SCLI) respectively. Make sure you are logged into the fsclish interactive mode. The default user account of the mcRNC logs into that mode automatically. To log into fsclish interactive mode manually, use the fsclish command. To change individual fault type limits, change parameters 0011-0014 under parameter class 016 within the accepted ranges. Setting the limit value to 0 disables the Suspend mode for the fault type indicated by the <parameter> variable. For IPA-RNC use the MML command of: ZWOC:16,<parameter>,<limit value in hexadecimal format>; For mcRNC use the SCLI command of: set app-parameter configurationparameter class 16 number <parameter> value <limit value in decimal format>

To change the threshold limit after which the buffered alarms in the system are to be written to the alarm database and shown as active alarms: For IPA-RNC use the MML command of: ZWOC:16,15,<treshold value>; For mcRNC use the SCLI command of: set app-parameter configurationparameter class 16 number 15 value <treshold value>

The parameter value should not be increased to the maximum as the alarm system requires some free resources to handle alarms. If the threshold value is too low, any reappearing fault (after corrective actions have been taken according to alarm manual) may become suspended. This can prevent verification of the result of the corrective actions.

198

Id:0900d80580903b23 Confidential

DN0988674

Activating and Verifying RU20 Features

Expected outcome The outcome depends on the way the parameters are changed. A fault type specific limit increase may cancel alarm 2881, and cause new alarms to be activated from the buffer in the RNC. Decreasing these limit parameters does not change the number of active alarms displayed, but if the limit is dropped below the current number of active alarms of that fault type, the next alarm set of that fault type group could trigger the Suspend mode on. Increasing the threshold limit may cause some alarms to be activated from the buffer, depending on the ratio of buffered alarms and free alarm system capacity set for the fault type groups.

DN0988674

Id:0900d80580903b23 Confidential

199

Activating and Verifying RU20 Features

4.4.4

Deactivating RAN1461: RNC RNW alarm reduction


Purpose Follow the procedure below to deactivate the following feature of the RAN1461: RNC RNW alarm reduction feature. 1. WBTS-level fault indication functionality 2. The Suspend mode functionality

Steps 1 Open the connection to the required IPA-RNC or mcRNC IP address to start the ManMachine Interface (MMI) or Structured Command Line Interface (SCLI) respectively. Make sure you are logged into the fsclish interactive mode. The default user account of the mcRNC logs into that mode automatically. To log into fsclish interactive mode manually, use the fsclish command. To deactivate the WBTS-level fault indication, change the PRFILE parameter 016:0009 value to 0. For IPA-RNC use the MML command of: ZWOC:16,9,0; For mcRNC use the SCLI command of: set app-parameter configurationparameter class 16 number 9 value 0

To deactivate the RNW alarm system Suspend mode, change the PRFILE parameter 016:0010 value to 0. For IPA-RNC use the MML command of: ZWOC:16,10,0; For mcRNC use the SCLI command of: set app-parameter configurationparameter class 16 number 10 value 0

Expected outcome The WBTS level fault indication functionality and the Suspend mode functionality of the RAN1461: RNC RNW alarm reduction feature has been deactivated. When deactivating the WBTS level fault indication, any 7786 alarms active in the system remain unchanged. They are cancelled when the WCELs are recovered. When deactivating the Suspend mode, the buffered alarms are written to the alarm system as active alarms and any 2881 alarms are cancelled. The number of alarms activated from the buffer depends on the current alarm system capacity for storing new active alarms.

This change affects the alarm handling of the faults generated after the alarm change. The WBTS-level alarms are cleared only after at least one WCEL is successfully restored to the WO state. If the Suspend mode was deactivated, and the suspend-mode indicating alarm (2881) was active at the time, the alarm system attempts to write any buffered alarms to the alarm system database as active alarms.

200

Id:0900d80580903b25 Confidential

DN0988674

Activating and Verifying RU20 Features

Activate and verify performance monitoring features

5 Activate and verify performance monitoring features


5.1 Activating RAN1311: Position Information in Subscriber Trace Report
Activating Position Information in Subscriber Trace Report
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 RAN1311: Position information in subscriber trace report in the RNC. For more information on the feature, see RAN1311: Position information in subscriber trace report in WCDMA RAN, rel. RU20, Feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. Features RAN2.0002: Subscriber Trace and RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates need to be activated before RAN1311 can work. RAN2.0002 and RAN2.0041 are controlled by their own licenses.

5.1.1

RAN2.0041 requires many parameters to be configured before it can work properly. For details, see Feature RAN2.0041: LCS - Cell Coverage Based (RTT) with Geographical Coordinates, Feature Activation Manual. Other location services features like RAN223: UE Based A-GPS Using External Reference Network are not mandatory for RAN1311, but they provide enhanced accuracy to the location information. Feature RAN875: Network Based A-GPS Using External Reference Network makes it possible to utilize network-based A-GPS for subscriber trace purposes. Subscriber trace also utilizes feature RAN1187: SAS-Centric Iupc. NetAct TraceViewer application is used to view the subscriber trace data. To support the new trace record, NetAct has to be upgraded to OSS5.2 CD1. RNC license management This feature belongs to application software (ASW) and is under license key management in the IPA-RNC and the mcRNC.

g g

There is no license control for this feature in the I-HSPA Adapter. For information on licensing, see Licensing in Activating and Verifying RU20 Features. The feature code for this feature is 1434. To set the feature state to ON, use the following command:

DN0988674

Id:0900d8058090d5b8 Confidential

201

Activate and verify performance monitoring features

Activating and Verifying RU20 Features

for the IPA-RNC: ZW7M:FEA=1434:ON; for the mcRNC: set license feature-mgmt id 0000001434 feature-admin-state on

Steps After the feature is set to ON state, no further actions are required. It is not mandatory to change any of the feature parameters during activation, but these parameters can be adjusted if needed: RNC/IADA RNC/IADA RNC/IADA RNC/IADA TraceLCSWaitPeriod TraceLCSPriority TraceLCSHorizAccur TraceLCSVertAccur

The managed object for the IPA-RNC and the mcRNC is RNC, while for the I-HSPA Adapter this is ADA. Expected outcome Subscriber trace data produced by the RNC contains the new UE location trace record.

202

Id:0900d8058090d5b8 Confidential

DN0988674

Activating and Verifying RU20 Features

5.1.2

Verifying Position Information in Subscriber Trace Report


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 verify that the activation of Position information in subscriber trace report is successful. Steps

Start the subscriber trace session for the IMSI that is used to make the test call. The trace session can be started either using NetAct TraceViewer application or using the following commands: MML command for the IPA-RNC ZT7T:IMSI=<international mobile subscriber identity>:REF=<trace reference>; sCLI command for the I-HSPA Adapter and mcRNC set subs-trace activate-trace imsi <international mobile subscriber identity> trace-ref <trace reference>

2 3

Make an AMR call with the traced UE and keep the call active for a few minutes. Check if NetAct TraceViewer shows RAN_UELocation records arriving and that they contain valid position information.

For more information on using the MML command, see T7 - Subscriber Trace Handling. For information on TraceViewer application, see NetAct product documentation.

DN0988674

Id:0900d805808ba424 Confidential

203

Activating and Verifying RU20 Features

5.1.3

Deactivating Position Information in Subscriber Trace Report


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 Position information in subscriber trace report feature.

Deactivate the license in the RNC. IPA-RNC To deactivate the feature in the IPA-RNC, use the following command: ZW7M:FEA=1434:OFF; To remove the license from the IPA-RNC, use the following command: ZW7D:<license file name>; It is also possible to stop UE Location trace record production by setting the RNCTraceLCSWaitPeriod parameter to special value 255 (disabled). mcRNC To deactivate the feature in the mcRNC, use the following command: set license feature-mgmt id 0000001434 feature-admin-state off To remove the license from the mcRNC, use the following command: delete license unique-id <unique-id> To disable the feature in the mcRNC, set the RNC-TraceLCSWaitPeriod parameter to special value 255 (disabled). I-HSPA Adapter To disable the feature in the I-HSPA Adapter, set the IADA-TraceLCSWaitPeriod parameter to value 255.

204

Id:0900d805808fc65f Confidential

DN0988674

Activating and Verifying RU20 Features

5.2
5.2.1

Activating RAN1312: Channel Element Utilization in WBTS


Activating Channel Element Utilization in WBTS
Purpose Follow this procedure to activate RAN1312: Channel Element Utilization in WBTS in the RNC. For more information on the feature, see RAN1312: Channel Element Utilization in WBTS in WCDMA RAN, rel. RU20, Feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. Make sure that the WBTS has at least the WN6.0 software installed (the counters introduced in this feature do not work in earlier releases). This feature is controlled by a license. For information on managing licenses, see Licensing. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M:FEA=1490:ON; for mcRNC: set license feature-mgmt id 0000001490 feature-admin-state on

Steps After the feature is set to ON state, no further actions are required. Expected outcome Channel Element Utilization in WBTS feature is active in the RNC.

DN0988674

Id:0900d80580907832 Confidential

205

Activating and Verifying RU20 Features

5.2.2

Verifying Channel Element Utilization in WBTS


Purpose Follow this procedure to verify that the activation of Channel Element Utilization in WBTS is successful. Steps

Start the M5001 measurement using the RNW Measurement Management application in the RNC Element Manager. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management application in Managing and viewing RNC measurements.

g
2

The M5001 counters are supported by FlexiBTS Rel1 HW. For FlexiBTS Rel2 with WN7.0 or later SW, start the M5006 measurement. Wait for the next full hour and additional 10 minutes for the measurement data to be transferred to OMS. Check in the RNW Measurement Presentation application (in the RNC Element Manager) if the M5001 measurement data is available and the feature-related counters are updated. For details on using the RNW Measurement Presentation application, see Radio network measurement presentation in Managing and viewing RNC measurements. Expected outcome Any counters in range of M5001C15 - M5001C36 have values higher than zero.

For FlexiBTS Rel2 with WN7.0 or later SW, check the counters in range of M5006C9 M5006C38.

206

Id:0900d80580907830 Confidential

DN0988674

Activating and Verifying RU20 Features

5.2.3

Deactivating Channel Element Utilization in WBTS


Purpose Follow this procedure to deactivate the Channel Element Utilization in WBTS feature. Steps

Uninstall the license in the RNC. To deactivate the feature, use the following command: for IPA-RNC: ZW7M:FEA=1490:OFF; for mcRNC: set license feature-mgmt id 0000001490 feature-admin-state off

Expected outcome Feature-related counters are no longer updated.

DN0988674

Id:0900d80580907831 Confidential

207

Activating and Verifying RU20 Features

5.3
5.3.1

Activating RAN1509: RAB Bit Rate Counters


Activating RAB Bit Rate Counters
Purpose Follow this procedure to activate RAN1509: RAB Bit Rate Counters in the RNC. For more information on the feature, see RAN1509: RAB Bit Rate Counters in WCDMA RAN, rel. RU20, Feature descriptions. Before you start Restart of the RNC and the WBTS is not required after activation of this feature. This feature is controlled by a license. For information on managing licenses, see Licensing. To set the feature state to ON, use the following command: for IPA-RNC: ZW7M:FEA=1435:ON; for mcRNC: set license feature-mgmt id 0000001435 feature-admin-state on

Steps After the feature is set to ON state, no further actions are required. Expected outcome RAB Bit Rate Counters feature is active in the RNC.

208

Id:0900d80580907909 Confidential

DN0988674

Activating and Verifying RU20 Features

5.3.2

Verifying RAB Bit Rate Counters


Purpose Follow this procedure to verify that the activation of RAB Bit Rate Counters is successful. Before you start Make sure that at least one working cell with a possibility to make a PS call is available. Set the uplink and downlink maximum bitrate of the QoS user profile in HLR to 128 kbps. Steps

Start the M1001 measurement (schedule: 7 days, 00:00-24:00, 15 minutes interval) using the RNW Measurement Management application in the RNC Element Manager. For details on using the RNW Measurement Management application, see Using the RNW Measurement Management application in Managing and viewing RNC measurements.

2 3 4

Wait for the next full 15 minutes till the measurement interval starts. Make one PS data call using the 128 kbps QoS profile. Wait for the next full 15 minutes for the measurement collection and additional 10 minutes for the measurement data to be transferred to OMS. Check in the RNW Measurement Presentation application (in the RNC Element Manager) if the M1001 measurement data is available and the feature-related counters are updated. For details on using the RNW Measurement Presentation application, see Radio network measurement presentation in Managing and viewing RNC measurements. Expected outcome Counters M1001C659 and M1001C666 have values higher than zero.

DN0988674

Id:0900d80580907907 Confidential

209

Activating and Verifying RU20 Features

5.3.3

Deactivating RAB Bit Rate Counters


Purpose Follow this procedure to deactivate the RAB Bit Rate Counters feature.

Uninstall the license in the RNC. To deactivate the feature, use the following command: for IPA-RNC: ZW7M:FEA=1435:OFF; for mcRNC: set license feature-mgmt id 0000001435 feature-admin-state off

Expected outcome Feature-related counters are no longer updated.

210

Id:0900d80580907908 Confidential

DN0988674