Change in RU10

7/26/2019 Change in RU10

http://slidepdf.com/reader/full/change-in-ru10 1/261

Changes in RU10

DN70515054Issue 1-0 en draft30/09/2008

# Nokia Siemens Networks 1 (261)

Nokia Siemens Networks WCDMA RAN, Rel.

RU10, Pre-release, System Library, v. 4



The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is not an officialcustomer document and Nokia Siemens Networks does not take responsibility for any errors or omissions in this document. This document is intended for the use of Nokia Siemens Networkscustomers only for the purposes of the agreement under which the document is submitted. Nopart of this documentation may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation hasbeen 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 thedocumentation.

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 liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer.

IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, that might arise from the use of this document or the information in it.

THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIREDBY APPLICABLE MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT,

ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THISDOCUMENT. NOKIA SIEMENS NETWORKS RESERVES THE RIGHT TO REVISE THISDOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE.

This document 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 2008. All rights reserved.

2 (261) # Nokia Siemens Networks DN70515054Issue 1-0 en draft

30/09/2008

Changes in RU10



Contents

Contents 3

List of tables 7

1 Documentation changes 111.1 Introduction to Documentation Changes 111.2 New documents 131.3 Modified documents 151.4 Removed documents 171.5 Documentation changes in Flexi WCDMA BTS 181.5.1 Documentation changes to WBTS5.0 release 18

1.6 Documentation changes in AXC 221.6.1 Documentation changes in release C5.5 221.6.1.1 New documentation 22

2 Software changes 252.1 Introduction to new SW in this release 252.2 New and removed features 252.3 SW changes in the WBTS5.0 release 262.4 SW changes in release C5.5 26

3 HW changes 293.1 RNC HW changes 29

3.1.1 RNC HW changes between RN3.0 and RN4.0 293.1.2 RNC HW changes between RN2.2 and RN3.0 303.1.2.1 Upgrading the RNC to RN3.0 303.1.3 RNC HW changes between RN2.1 and RN2.2 313.1.3.1 New hardware products 323.1.3.2 Upgrading the RNC to RN2.2 RNC196 333.2 Flexi WCDMA BTS HW changes 353.2.1 Changes in Flexi WCDMA BTS hardware products 353.3 Ultrasite WCDMA BTS HW Changes 363.3.1 UltraSite WCDMA BTS HW Changes 363.4 MetroSite 50 BTS HW changes 363.4.1 Changes in MetroSite 50 BTS hardware products 363.5 AXC changes 363.5.1 HW changes in release C5.5 36

4 RNC alarm changes 374.1 Changes in alarms 374.1.1 New alarms 374.1.2 Changed alarms 424.1.3 Removed alarms 464.1.4 Alarm system configuration changes 46

5 Key indicator changes 475.1 Changes in key performance indicators 47

DN70515054Issue 1-0 en draft30/09/2008


Contents



6 Measurement changes 516.1 Measurement changes 516.1.1 RNC Radio Network Measurements 516.1.2 RNC Transport & HW Measurements 926.1.3 WBTS Radio Network Measurements 1176.1.4 FlexiBTS Transmission Measurements 1246.1.5 AXC Measurements 127

7 MML command changes 1317.1 Introduction to MML changes between releases RN3.0 and RN4.0 1317.2 New MML programs 1327.2.1 (I2) S0SHAN - SSH Protocol Layer Handling 1327.2.2 (QA) ENJOYY - Ethernet Parameter Handling 1327.2.3 (YG) BFHAND - BFD Supervision Handling 133

7.3 Modified MML programs 1337.3.1 (IA) AUTHOR - MMI System Authority Handling 1337.3.2 (ID) DKOMFI - Disk Command File Execution 1367.3.3 (LJ) AM8HAN - ATM Endpoint Handling 1377.3.4 (QR) YOOHOO - TCP/IP Stack Data Handling 1387.3.5 (RD) DIGANA - Digit Analysis Handling 1437.3.6 (RI) ANAINQ - Digit Analysis Interrogation 1447.3.7 (RM) DANAMO - Digit Analysis Modification 1447.3.8 (YE) ETSHAN - Exchange Terminal Supervision Handling 1457.4 Deleted MML programs 147

8 New and removed features in earlier releases 149

8.1 New and removed features in RAS06 1498.2 New and removed features in RAS05.1 1528.3 New and removed features in RAS05 1558.4 New and removed features in RAN04 1578.5 New and removed features in RAN1.5 159

9 Parameter changes 1639.1 RNC Parameter Changes 1639.2 Changes in Plan Editor AXC Parameters 1639.2.1 Introduction 1639.2.2 New Parameters in AXC PE 5.5 1639.2.2.1 AXC 1639.2.2.2 IEIF 164

9.2.2.3 MODUL 1649.2.2.4 TOPIK 1659.2.3 Changed parameters in AXC PE 5.5 1669.2.3.1 ACCP 1669.2.3.2 AXC 1679.2.3.3 IEIF 1689.2.3.4 PWMP 1689.2.3.5 SRCK 1699.2.3.6 STPG 1699.2.4 Removed Parameters in AXC PE 5.5 1709.2.4.1 ETHLK 1709.2.4.2 PWTIP 170

9.3 Changes in Plan Editor Flexi Transport Module Parameters 171


30/09/2008

Changes in RU10



9.3.1 Introduction 1719.3.2 New Parameters in WBTS5.0 1719.3.2.1 FTM_A2UT 1719.3.2.2 FTM_BFD 1719.3.2.3 FTM_CCFA 1729.3.2.4 FTM_CERTH 1729.3.2.5 FTM_FRLI 1729.3.2.6 FTM_IEIF 1739.3.2.7 FTM_IPNO 1749.3.2.8 FTM_PWMP 1749.3.2.9 FTM_QOS 1749.3.2.10 FTM_QOS_TRAFFICTYPE 1759.3.2.11 FTM_TMPAR 1759.3.2.12 FTM_TOPIK 176

9.3.3 Changed parameters in WBTS5.0 1779.3.3.1 FTM 1779.3.3.2 FTM_A2ST 1779.3.3.3 FTM_A2UT 1779.3.3.4 FTM_ACCP 1789.3.3.5 FTM_ANBA 1799.3.3.6 FTM_ETHLK 1809.3.3.7 FTM_IAIF 1809.3.3.8 FTM_IHCP 1819.3.3.9 FTM_IHCP_CLIENT 1819.3.3.10 FTM_IHCP_HW 1829.3.3.11 FTM_IHCP_RANGE 183

9.3.3.12 FTM_IPRM_EX 1849.3.3.13 FTM_IPRT 1869.3.3.14 FTM_PPTT 1879.3.3.15 FTM_PWMP 1889.3.3.16 FTM_STPG 1899.3.3.17 FTM_TCTT 1909.3.3.18 FTM_UNIT 1909.3.3.19 FTM_VCCT 1919.3.3.20 FTM_VCTT 1919.3.3.21 FTM_VPCT 1919.3.3.22 FTM_VPTT 1929.3.4 Removed Parameters in WBTS5.0 1929.3.4.1 FTM_ETHLK 192

9.3.4.2 FTM_IPRM_EX 1929.3.4.3 FTM_PWNE 1929.3.4.4 FTM_PWTIP 1939.4 Changes in Plan Editor Flexi WCDMA BTS Parameters 1939.4.1 Introduction 1939.4.2 New Parameters in WBTS5.0 1949.4.2.1 ANTL 1949.4.2.2 ANTLD 1959.4.2.3 BTSSC 1959.4.2.4 LCEL 2069.4.2.5 LCELG 2089.4.2.6 MHA 209

9.4.2.7 RET 210

DN70515054Issue 1-0 en draft30/09/2008


Contents



9.4.3 Removed Parameters in WBTS5.0 2119.4.3.1 WCEL_HW 2119.4.3.2 ANTENNA_HW 2119.4.3.3 WBTS_HW 2129.4.3.4 WBTS 2139.4.3.5 OUTPUT_EAC 2139.4.3.6 FILEMODE_UNIT 2139.4.3.7 PASSIVE_UNIT 2139.4.3.8 TILT 2139.4.3.9 WCEL 2149.4.3.10 MHA 2149.4.3.11 CELL_GROUP 2149.4.3.12 INPUT_EAC 2159.5 Changes in Plan Editor UltraSite WCDMA BTS Parameters 215

9.5.1 Introduction 2159.5.2 New Parameters in WBTS5.0 2159.5.2.1 ANTL 2159.5.2.2 ANTLD 2189.5.2.3 BTSSC 2199.5.2.4 LCEL 2279.5.2.5 LCELG 2309.5.2.6 MHA 2319.5.2.7 PATH 2319.5.3 Removed Parameters in WBTS5.0 2339.5.3.1 ANTENNA_HW 2339.5.3.2 WBTS_HW 233

9.5.3.3 OUTPUT_EAC 2349.5.3.4 WTR 2349.5.3.5 WCEL 2359.5.3.6 BTU 2359.5.3.7 TX_CABLE 2359.5.3.8 RX_CABLE 2359.5.3.9 WCEL_HW 2369.5.3.10 WBTS 2369.5.3.11 WIA 2369.5.3.12 MHA 2369.5.3.13 CELL_GROUP 2379.5.3.14 INPUT_EAC 2379.6 Changes in WBTS Commissioning Parameters 237

9.6.1 Overview of parameter changes in WCDMA BTS releases 2379.6.2 Parameter changes in the WN3.2, WN3.3, WN4.0 and WN5.0 software

releases 2389.6.2.1 UltraSite WCDMA BTS 2389.6.2.2 Flexi WCDMA BTS 2419.6.3 WBTS commissioning parameter structure for UltraSite WCDMA

BTS 2489.6.4 WBTS commissioning parameter structure for Flexi WCDMA BTS 255


30/09/2008

Changes in RU10



List of tables

Table 1. WCDMA RAN system documentation 11

Table 2. Documentation changes in Nokia Siemens Networks WCDMA RAN, Rel.RU10, Pre-release, System Library, v. 4 18

Table 3. New features for UltraSite WCDMA BTS and MetroSite 50 BTS 26

Table 4. New features for Flexi WCDMA BTS 26

Table 5. New features 27

Table 6. New features 27

Table 7. New hardware 35

Table 8. New hardware 36

Table 9. New KPIs for RU10 47

Table 10. Updated KPIs in RU10 48

Table 11. Substituted KPIs in RU10 49

Table 12. Corrected KPIs in RU10 49

Table 13. Measurement M1024 RCPM OLPC WCEL, new counters 51

Table 14. Measurement M1025 RCPM OLPC RNC, new counters 52

Table 15. Measurement M1026 RCPM RLC WCEL, new counters 53

Table 16. Measurement M1027 RCPM RLC RNC, new counters 56

Table 17. Measurement M1028 Autodef SHO DSR, new counters 58

Table 18. Measurement M1000 Cell Resource, new counters 59

Table 19. Measurement M1001 Service Level, new counters 62

Table 20. Measurement M1002 Traffic, new counters 63

Table 21. Measurement M1003 L3 Signalling at Iu, new counters 67

Table 22. Measurement M1004 L3 Signalling at Iur and M1009 L3 RelocationSignalling, new counters 67

Table 23. Measurement M1005 L3 Signalling at Iub, new counters 68

Table 24. Measurement M1006 RRC Signalling, new counters 68

Table 25. Measurement M1007 Soft Handover, new counters 71

Table 26. Measurement M1008 Intra System Hard Handover, new counters 71

Table 27. Measurement M1010 Inter System Hard Handover, new counters 72

DN70515054Issue 1-0 en draft30/09/2008


List of tables



Table 28. Measurement M1011 Location Services, new counters 73

Table 29. Measurement M1013 Autodef SHO, new counters 73

Table 30. Measurement M1014 Autodef IFHO, new counters 73

Table 31. Measurement M1015 Autodef ISHO, new counters 74

Table 32. Measurement M1021 Iu-PC interface, new counters 74

Table 33. Measurement M1022 Packet Call, new counters 75

Table 34. Measurement M1023 Cell Throughput, new counters 81

Table 35. Removed counters 83

Table 36. Measurement M145 PDH Statistics, new counters 93

Table 37. Measurement M208 MTP Signalling link availability, new counters 95

Table 38. Measurement M209 MTP signalling link performance, new counters 96

Table 39. Measurement M210 MTP signalling link utilization, new counters 97

Table 40. Measurement M211 MTP signalling point status, new counters 97

Table 41. Measurement M212 MTP Signalling link set and route set availability, newcounters 98

Table 42. Measurement M213 MTP Signalling traffic report of signalling points, newcounters 98

Table 43. Measurement M214 MTP Signalling traffic report of user parts, newcounters 99

Table 44. Measurement M215 MTP matrix signalling traffic, new counters 99

Table 45. Measurement M216 SCCP signalling point, new counters 100

Table 46. Measurement M217 SCCP subsystem, new counters 103

Table 47. Measurement M218 SCCP local subsystem availability, newcounters 104

Table 48. Measurement M219 SCCP single meters, new counters 105

Table 49. Measurement M548 AAL2 signalling protocol at UNI, new counters 105

Table 50. Measurement M552 AAL2 signalling at NNI, new counters 106

Table 51. Measurement M553 AAL2 Scheduling Performance in RNC, newcounters 106

Table 52. Measurement M563 TCP/IP Protocol, new counters 108

Table 53. Measurement M564 Ethernet Interface Performance, new counters 109

Table 54. Measurement M565 IP measurement on IP interface, new counters 110


30/09/2008

Changes in RU10



Table 55. Measurement M566 UDP measurement on IP interface, newcounters 111

Table 56. Measurement M567 IP QoS measurement, new counters 111

Table 57. Measurement M568 IP Based Route, new counters 112

Table 58. Measurement M609 DSP service statistics, new counters 112

Table 59. Measurement M612 DSP state changes, new counters 112

Table 60. Measurement M615 DSP Resource Utilization, new counters 113

Table 61. Measurement M617 DSP load, new counters 113

Table 62. Measurement M661 M3UA Association Set, new counters 114

Table 63. Measurement M802 RNC capacity usage, new counters 114

Table 64. Measurement M803 RNC RTP/RTCP, new counters 115

Table 65. Measurement M804 RNC IP CAC, new counters 116

Table 66. Measurement M5002 Cell Throughput in WBTS, new counters 117

Table 67. Measurement M5003 Frame Protocol in WBTS, new counters 119

Table 68. Measurement M5000 HSPA in WBTS, new counters 120

Table 69. Measurement 5115 AAL2 Scheduling Performance in BTS, Counters 124

Table 70. Measurement 5116 FTM Timing over packet, Counters 125

Table 71. Measurement 5117 FTM IP statistics, Counters 125

Table 72. Measurement 5118 FTM PHB Statistics, Counters 125

Table 73. Measurement M5113 FTM Pseudowire MPLS, new counters 126

Table 74. Measurement M5114 FTM PSN tunnel IP, new counters 126

Table 75. Measurement 5213, AXC Pseudowire MPLS, Counters 127

Table 76. Measurement 5216, AXC Timing over Packet, Counters 127

Table 77. Measurement 5217, AXC IP statistics, Counters 127

Table 78. Measurement 5218, AXC PHB statistics, Counters 128

Table 79. Measurement 5210, AXC Ethernet link, Counters 128

DN70515054Issue 1-0 en draft30/09/2008


List of tables




30/09/2008

Changes in RU10



1 Documentation changes

1.1 Introduction to Documentation Changes

This document describes changes in the structure and content of the RANsystem documentation. You will find information on documents that arenew, modified, or have been removed in the current release.

Structural changes in the documentation set

The most important documentation change between the RAS06 and RU10releases is that the NOM categories have been updated, that is, mostRAS06 categories have been renamed and new ones have also been

added. This means that the location of most documents has changed. Themain idea behind the new categories is to get rid of the product-relatedcategories (such as Flexi WCDMA BTS guidelines ) and include all similar information under one category regardless of the product.

The following tables provide information on where you can find thecontents of the RAS06-level document set in the RU10-leveldocumentation set.

Table 1. WCDMA RAN system documentation

Information categories in

WCDMA RAN, Rel. RAS06,

System Library


WCDMA RAN, Rel. RU10,

System Library

Description of the new or

updated category

System and Product Descriptions System Descriptions This category used to include alsoproduct descriptions but now onlyincludes system descriptions.

RNC descriptions This category includes only theRNC-related product descriptions.

WCDMA BTS descriptions This category includes only theWCDMA BTS-related product

descriptions.

DN70515054Issue 1-0 en draft30/09/2008


Documentation changes



Table 1. WCDMA RAN system documentation (cont.)


WCDMA RAN, Rel. RAS06,

System Library


WCDMA RAN, Rel. RU10,

System Library

Description of the new or

updated category

Feature and FunctionalDescriptions

Functional Area Descriptions This category includes onlyfunctional area descriptions.

Feature Descriptions This category includes onlyfeature descriptions.

WCDMA RAN system guidelines

WCDMA RNC guidelines

Flexi WCDMA BTS guidelines

Plan and Dimension This category includes informationrelated to planning anddimensioning the WCDMA RAN.

Install This category includes informationrelated to installing the WCDMARAN.

Commission This category includes informationrelated to commissioning theWCDMA RAN.

Integrate and Configure This category includes informationrelated to integrating andconfiguring the WCDMA RAN.

Activate This category includes allinformation related to activating

the features included in theWCDMA RAN.

Operate and Maintain This category includes informationrelated to operating andmaintaining the WCDMA RAN.

Troubleshoot This category includes informationrelated to troubleshooting theWCDMA RAN.

Expand and Upgrade This category includes informationrelated to expanding andupgrading the WCDMA RAN.

The documentation set now also includes UltraSite, MetroSite, AXC andantenna documentation.

All procedural information categories now follow the operator processes,and they also have subdivisions for system-level and NE-level documents.These subdivisions follow the same order throughout the documentationset:

. system-level information

. BTS-related information


30/09/2008

Changes in RU10



. AXC-related information

. antenna-related information

For detailed information on the new documentation set structure, see Architecture of the WCDMA RAN System Library in Guide to Nokia

WCDMA RAN Documentation .

Change documentation

The division of change documentation has been updated. There are twochange documents now listing change information, RU10 Changes andChanges in WCDMA RAN Parameters . Information from the following

change documents has been incorporated into the RU10 Changes document:

. Documentation Changes

. SW Changes

. RNC HW Changes

. RNC Alarm Changes

. Changes in Flexi WCDMA BTS

.

Changes in WBTS Commissioning Parameters. Key Indicator Changes

. Measurement Changes

. Changes in MML Programs between Releases RN2.2 and RN3.0

. Changes in Plan Editor AXC Parameters

. Changes in Plan Editor Flexi WCDMA BTS Parameters

. Changes in Plan Editor UltraSite WCDMA BTS Parameters

.

Parameters Changes in WBTS Commissioning Parameters

1.2 New documents

The following sections list documents that are new in RAS, RNC or FlexiWBTS as compared to their earlier releases, that is, new RAS documentsthat have been created between RAS06 and RU10 and new RNCdocuments that have been created between RN3.0 and RN4.0.

The following documents have been introduced in RU10:

DN70515054Issue 1-0 en draft30/09/2008





Functional Area Descriptions

. WCDMA RAN IP Transport

. WCDMA RAN ATM Transport

. WCDMA RAN Protection

. WCDMA RAN Synchronisation

. RNC Backup Server

. WCDMA RAN O&M Security

Feature Descriptions

. RU10 Feature Descriptions

. Subscriber and Equipment Trace Feature Description

RNC Descriptions

. RNC2600 Product Description

. SW Licence Key Controlled RNC Capacity

WCDMA BTS Descriptions

. Flexi WCDMA BTS Transmission Description

Activate

. Activating RAN74 and RAN1449: IP Based Iub for Flexi WCDMABTS and Dual Iub for Flexi

. Activating RAN75 and RAN750: IP based Iu-cs and IP based Iu-ps

. Activating RAN76: IP based Iur

.

Activating RAN86: Cell Throughput Measurements in Serving RNCand RAN1101: Cell Throughput Measurements in BTS

. Activating RAN285: HSPA Multi NRT RABs

. Activating RAN580: Load Based AMR Codec Mode Selection

. Activating RAN930: PS RAB Reconfiguration

. Activating RAN1102 Secure Management Interface for FlexiWCDMA BTS

. Activating RAN1126: Counters for RAB and DCH Setups and FailureCases


30/09/2008

Changes in RU10



. Activating RAN1185: LCS Support in Drift RNC

. Activating RAN1187 and RAN1296: SAS-Centric Iupc and LCSPeriodical Reporting

. Activating RAN1187 and RAN1296: SAS-Centric Iupc and LCSPeriodical Reporting

. Activating RAN1189, RAN1191, and RAN1245: Handover Optimisation Statistics

. Activatinh RAN1206: Secure File Transfer

. Activating RAN1208: Secure MMI

.

Activating RAN1253: Iub Transport QoS

. Activating RAN1262 and RAN1004: QoS for PS services

. Activating RAN1266: Soft Handover Based on Detected SetReporting

. Activating RAN1275: Inter-system Handover Cancellation

. Activating RAN1276: HSPA Inter-frequency Handover

Operate and maintain

. Maintaining Flexi WCDMA BTS Hardware

Reference

Counters:

. WCDMA RAN and UMR Counter Mapping

Key Indicators:

. WCDMA RAN and UMR KPI Mapping

Parameters:

. WCDMA RAN and UMR Parameter Mapping

1.3 Modified documents

Major structural changes in documents are listed here.

DN70515054Issue 1-0 en draft30/09/2008





For information on documentation content updates, see the Summary of

changes section in the PDF version of each document.

Changes

All delta documentation has been restructured for RU10. There are twodelta documents, RU10 Changes and WCDMA RAN Parameter Changes .The RU10 Changes document includes information that was included inthe following RAS06-level documents:

. Documentation Changes

. SW Changes

. RNC HW Changes

. RNC Alarm Changes

. Changes in Flexi WCDMA BTS

. Key Indicator Changes

. Measurement Changes

. Changes in MML Programs between Releases RN2.2 and RN3.0

. Changes in Plan Editor AXC Parameters

. Changes in Plan Editor Flexi WCDMA BTS Parameters

. Changes in Plan Editor UltraSite WCDMA BTS Parameters

. Parameters Changes in WBTS Commissioning Parameters

These are now moved to correct subsections in the RU10 Changes

document and they cover the changes between RAS06 as compared withRU10.


. In the previous releases, separate functional area descriptiondocuments were published for Load Control and Resource Manager .In RU10, these functional area descriptions have been integratedinto the Admission Control document.

. In the previous release, there were two functional area descriptiondocuments related to security, WCDMA RAN User Security andWCDMA RAN O&M Network Security. In RU10, these twodocuments have been combined into one document called WCDMA

RAN O&M Security .


30/09/2008

Changes in RU10



. In the previous release, the following Functional Area Description

documents , , and included only WCDMA RAN system-levelinformation.. WCDMA RAN Fault Management

. WCDMA RAN Network Topology

. WCDMA RAN Mass Operations

. WCDMA RAN Direct Configuration Operations

. WCDMA RAN Licence Key Management Operations

. WCDMA RAN Network Inventory

. WCDMA RAN Software Management

. WCDMA RAN Network Element Management

In RU10 these documents also include RNC-specific information.

. Subscriber and Equipment Trace-related information has beenremoved from RAN04 and RAS05 Performance Monitoring Features

and RAS05.1 Performance Monitoring Features documents. Thisinformation is now available in Subscriber and Equipment Trace

Feature Description .

Activate

The titles of all documents in this category have been modified to follow acommon naming practice. The naming should be Activating <ID and name

of the feature> (for example, Activating RAN1266: Soft Handover Based on Detected Set Reporting ).

1.4 Removed documents

The following documents have been removed and are therefore notincluded in the RU10 System Library:


. Load Control

The information has been moved into the Admission control

document.

. Resource Manager

The information has been moved into the Admission control

document.

. RNC Operation and Maintenance

DN70515054Issue 1-0 en draft30/09/2008





Activate

. Feature RAN1192: UBR+ for Control Plane and Iu/Iur User Plane

. Feature RAN1246: WBTS EM Manager Launch from RNC

. Feature RAN2.0051: Streaming Packet Switched Quality of Service

. Feature RAN223: UE Based A-GPS Using External ReferenceNetwork, Feature Activation Manual

. Feature RAN875: Network Based A-GPS Using External ReferenceNetwork, Feature Activation Manual

References

. Notices (0-999)

. WCDMA RAN Key Alarm Indicators

1.5 Documentation changes in Flexi WCDMA BTS

1.5.1 Documentation changes to WBTS5.0 release

Changes have been made to the documentation since the lastdocumentation release. The changes are available via NOLSdocumentation update.

Changed documentation

Table 2. Documentation changes in Nokia Siemens Networks WCDMA RAN,Rel. RU10, Pre-release, System Library, v. 4

t name and DN Change description Related Pronto

MA BTS Product

5

Transmission-related documentation has been removed fromthis document to Flexi WCDMA BTS Transmission

Description .

MA BTS Systemscription

5

Editorial changes made.


30/09/2008

Changes in RU10



Table 2. Documentation changes in Nokia Siemens Networks WCDMA RAN,Rel. RU10, Pre-release, System Library, v. 4 (cont.)

cument name and DN

mber

Change description Related Pronto

i WCDMA BTS RF ModuleRemote Radio Headcription

085361

The following sections have been edited:

. RF Module and Remote Radio Head operation and main

blocks

. RF Module and Remote Radio Head power requirements

i WCDMA BTS Optionals Description

086754


. Flexi mounting kit for floor, wall and pole (FMFA) description

. Flexi Pole Installation Kit (FPIA) description

. Flexi Pole Mounting Kit (FPKA) description

. Flexi Mounting Covers for Back and Front (FMCA and

FMCB) description

. Flexi Power Module (FPMA) and sub-modules (FPAA and

FPBA) operation

. Flexi power DC/DC sub-module (FPDA) operation

. FCIA cabinet construction

. FCIA cabinet optional items

. FCOA optional items

. FCOA dimensions and weight

. Physical dimensions of the I-HSPA Adapter

. Physical interfaces of the I-HSPA Adapter

. Talk Conversion Kit (EMIA)

alling Flexi Cabinet for door (FCOA)

062824


. Anchoring the FCOA

. Installing the FCOA security lock

. Routing the cables through FCOA cabinet bottom

. Grounding the FCOA

. Installing batteries

. Installing PDU and site support module

. Installing fire detector

alling Flexi Cabinet for Indoor A)

0306329

The following sections have been edited:. Overview of installing FCIA

. FCIA clearances and anchoring holes

. Installing Power Distribution Unit in FCIA (renamed toInstalling MIBBU WPUB (469784A) and WPUC (469955A) )

. Contents of Flexi Cabinet for Indoor (FCIA)

The following section has been removed:

. Installing Flexi System External Alarm (FSEB)

DN70515054Issue 1-0 en draft30/09/2008







exi WCDMA BTSr Stack, Wall, andurations

45


. Grounding principle of the stand-alone BTS

. Installing modules on the floor

. Mounting the plinth on the wall

. Mounting the modules on a wall

. Mounting the modules on a pole

. Overview of installing Remote Radio Heads

. Contents of the Flexi Pole Mounting Kit (FPKA)

. Contents of the transmission sub-module deliveries

. Contents of the transmission cable deliveries

. Contents of the shorthaul optical transmission cable

deliveries

exi WCDMA BTSCabinets

69


. Installing Flexi Mounting Shield 6U (FMSA)

. Installing Flexi Mounting Shield 18U (FMSB)

. Overview of installing Flexi BTS modules in Citytalk cabinet

. Grounding principle for Flexi WCDMA BTS modules in

Citytalk cabinets

. Preparing Citytalk cabinet for Talk Conversion Kit

. Installing Talk Conversion Kit and modules in Citytalk

cabinet

. Contents of Flexi Cabinet for Indoor (FCIA) delivery

. Contents of the Talk Conversion Kit (EMIA)

.


. Installation tools for Talk Conversion Kit

exi WCDMA BTSms

84


. Installing Flexi Power Module (FPMA)

. Installing Flexi Power DC/DC Module 24V FPDA

. Installing Flexi System External Alarm (FSEB)

. Introduction to installing Nokia Siemens Networks I-HSPA

Adapter with Nokia Flexi WCDMA BTS

. Installing the I-HSPA Adapter front cover

. Contents of the I-HSPA Adapter delivery

. Contents of the Flexi Mounting Auxiliary Brackets (FMAA)


30/09/2008

Changes in RU10




cument name and DN

mber

Change description Related Pronto

ing Flexi WCDMA BTS andating Configurations

038109


. Module interfaces

. Stand-alone BTS cabling principle

. Connecting the FTCP transmission cable to FTHA

. Connecting the FTCP transmission cable to remote

equipment

. Connecting the FTCP transmission cable to Digital

Distribution Frame (DDF) . Connecting the FTCP transmission cable to symmetric

patch panels

. Connecting the FTCP transmission cable to asymmetric

patch panels without baluns

. Connecting the FTCP transmission cable to asymmetric

patch panels with baluns

. Connecting Power Module alarm cables

. Installing feederless or distributed site

. Connecting the BTS/Iub cable of the I-HSPA Adapter

. Connecting the I-HSPA Adapter Ethernet transmission

cable

. Connecting I-HSPA Adapter optical cables

. Creating cost-optimised 1+1+1 (20 W/40 W) and 2+2 +2 (20

W) configurations

. Creating upgrade-optimised configuration for 1+1 +1 (20 W/

40 W) and 2+2+2 (20 W/40 W)

. Flexi WCDMA BTS configurations

ntaining Flexi WCDMA BTSsmission

0143712

The following sections have been added:

. Configuring VCC bundle

. Configuring weights for 4 AAL2 priority queues of an AAL2

VCC

. Configuring Ethernet interface settings

. Configuring transport Ethernet addresses

. Configuring IP quality of service parameters

. Configuring CA certificates manually

. Configuring BTS keys and certificates manually

. Configuring CMP and CR server IP address

. Verifying the connection status

. Commissioning Timing over Packet with FTIB

ntaining Flexi Cabinet for door (FCOA)

067391


. Checking the FCOA and FMSA/B door or roof locks

. Replacing FCFA fans (083589A)

.

Replacing MIBBU WPUB (469784A) and WPUC (469955A)

DN70515054Issue 1-0 en draft30/09/2008







Flexi WCDMA BTSd fans

6


. Title of the document changed from Maintaining the Stand-

alone Flexi WCDMA BTS to Replacing Flexi WCDMA BTS

modules and fans

. Disconnecting cables

. Replacing module fans from the back

. Replacing module fans from the front

. Replacing FPMA

. Replacing battery sub-modules FPBA

. Replacing module fans from the rear (FMSA)

. Replacing module fans from the rear (FMSB)

. LED indications


. Performing routine maintenance tasks

1.6 Documentation changes in AXC

1.6.1 Documentation changes in release C5.5

1.6.1.1 New documentation

The following documentation is new in release C5.5:

. Remote User Event Log Management

See: AXC product description

. Configuring Timing over Packet

See: Commissioning AXC

. Commissioning Timing over Packet with IFUH

See: Commissioning AXC

. Monitoring Timing over Packet performance

See: Operating and maintaining AXC


30/09/2008

Changes in RU10



. Installing the TOPA module to the IFUH

See: Expanding and upgrading AXC

. 61203 Module missing

See: AXC alarms

DN70515054Issue 1-0 en draft30/09/2008






30/09/2008

Changes in RU10



2 Software changes

2.1 Introduction to new SW in this release

RU10 introduces several new features. In transport solutions, the new IPbased interfaces are a major improvement. These enable the user tochoose between the ATM and IP solutions, thus making the networkconfigurations more flexible.

The RU10 specification baseline is 3GPP Release 6.

2.2 New and removed featuresNew features

For new software features in RU10, see WCDMA RAN System, Rel.

RU10, Feature Descriptions .

For new hardware features in RU10, see RNC HW Changes .

Removed features

The following features are removed in RAS06:

. RAN2.0084: Packet Scheduler Interruption Timer

. RAN1094: HSDPA Resumption Timer

DN70515054Issue 1-0 en draft30/09/2008


Software changes



2.3 SW changes in the WBTS5.0 release

Table 3. New features for UltraSite WCDMA BTS and MetroSite 50 BTS

Feature name Location in documentation

Timing over Packet RAN1326: Timing over Packet Module

"TOPA" for WCDMA UltraSite BTS inWCDMA RAN, Rel. RU10, Feature

Descriptions

Antenna Alarm with Receiver SignalComparison

RAN119: Antenna Alarm with Receiver

Signal Comparison in WCDMA RAN, Rel.

RU10, Feature Descriptions

Table 4. New features for Flexi WCDMA BTS


Timing over Packet RAN1155: Flexi WCDMA BTS Eth+E1/T1/

JT1 Sub-Module "FTIB" with Timing over

Packet in WCDMA RAN, Rel. RU10,

Feature Descriptions

Defining Timing over Packet settings inCommissioning Flexi WCDMA BTS

Support for Large BTS Configurations upto 12 Cells

RAN1092: Support for Large BTS

Configurations up to 12 Cells (FlexiBTS)

in WCDMA RAN, Rel. RU10, Feature

Descriptions

MORAN - Operator Dedicated BB for Flexi WCDMA BTS

RAN1274: MORAN - Operator Dedicated

BB for Flexi WCDMA BTS in WCDMA

RAN, Rel. RU10, Feature Descriptions

Antenna Alarm with Receiver SignalComparison

RAN119: Antenna Alarm with Receiver

Signal Comparison in WCDMA RAN, Rel.

RU10, Feature Descriptions

2.4 SW changes in release C5.5

Introduction to new SW in this release

Timing over Packet , enabled by the IFUH interface unit, is used for BTSsynchronisation in Full Ethernet/IP packet transport networks. SeeSynchronisation of AXC in AXC product description .


30/09/2008

Changes in RU10



Remote User Event Log Management is a feature that allows a network

management system to trace operations done in network elements bydifferent users. See Remote User Event Log Management in AXC product

description .

Changes in commissioning

Table 5. New features


Timing over Packet Commissioning Timing over Packet with

IFUH Configuring Timing over Packet inCommissioning AXC

Commissioning Timing over Packet with

IFUH in Commissioning AXC

Changes in licensing

Table 6. New features


Timing over Packet Managing licences in Operating and

maintaining AXC

Licensing in AXC in AXC product

description

DN70515054Issue 1-0 en draft30/09/2008


Software changes




30/09/2008

Changes in RU10



3 HW changes

3.1 RNC HW changes

3.1.1 RNC HW changes between RN3.0 and RN4.0

This section summarises the differences in the hardware implementationbetween RN3.0 and RN4.0.

Main functional changes are Iub throughput capacity increase to 2600Mbit/s (450 Mbit/s), DL 2000Mbit/s and UL 600/840Mbit/s, HSDPA peakrate capacity increase and connectivity increase.

New plug-in units

Compared to RNC450, RNC2600 contains the following new plug-in units:

. CDSP-DH configurable digital signal processing platform

. SF20H 20 Gbits/s switching fabric supports 32pcs new high speedSFU-ports

. MX1G6-A ATM multiplexer 1.6 Gbit/s

. NP2GE-B network interface and processing 2x1000Base-T/LX

. NP8S1-B network interface and processing 8xSTM-1 / 2xSTM-4(RN4.0 SW is not supported STM-4 interface)

Functional units changes

. Does not include A2SU units – function is included in the STM-1interface unit

. Does not include GTPU units – function is included in the Ethernet or STM-1 interface units

DN70515054Issue 1-0 en draft30/09/2008


HW changes



. Does not include RRMU – function is included in ICSU and RSMU/

OMU units. Does not include NIP1

New mechanics and electromechanics

. BISFA back interface panel with SFP connectors for SF20H

. BISFB back interface panel with SFP connectors for MX1G6-A

. BISFC back interface panel with SFP connectors for NP2GE-B andfor NP8S1-B

.

BISFD back interface panel with SFP connectors for SF20H. CSB intermediate cable with SFP connectors



New hardware products

.

A new CPU variant CCP18-C. CCP18-A is still used for OMU,because the USB port is needed for backup purposes

3.1.2.1 Upgrading the RNC to RN3.0

Mandatory upgrades for RNC450

There are no mandatory upgrades for RNC450.


. For RN3.0, NEMU has been replaced by OMS and MCPC2,

MCPC2-A, HDS9, and HDS are no longer supported

. CCPC2-A for OMU, MDS/MDS-B for FDU and HDS9/HDS for WDUare no longer supported

. CCPC2-A and CDSP-B are no longer supported. Thus, plug-in unitupgrades from CCPC2-A and CDSP-B are no longer needed duringthe upgrade as the units need to have been upgraded already beforethe RN3.0 SW release upgrade.

Not supported in RN3.0 Upgraded to


30/09/2008

Changes in RU10



MCPC2, MCPC2-A MCP18-B

HDS9, HDS HDS-A

CCPC2-A CCP18-C / CCP18-A

MDS, MDS-B MDS-A

CDSP-B CDSP-C

Refer to HW Technical Note 98 Windows NEMU replacement with Linux

OMS in RN3.0.

Optional upgrades and extensions for RNC196

Refer to Hardware changes between releases RN2.1 and RN2.2 for details on optional upgrades and extensions for RNC196. All of theoptional upgrades and extensions apply also to RN3.0 if they have notalready been made earlier for RN2.2.



Notation changes in the capacity step naming

RN2.2 introduces three new capacity steps for new deliveries (RNC450)and two new capacity steps (6 –7) for upgrades from previously deliveredRNCs (RNC196). In RNCs delivered prior to RN2.2 (RNC196), capacitysteps have been named with numbers from 1 to 5. In RN2.2, the capacitysteps are named according to the Iub throughput capacity each step addsto the RNC. Capacity steps 1 to 5 have been renamed accordingly. Thebelow notations are used for RNC450 and RNC196 capacity steps.

RN2.2 new deliveries = RNC450

.

RNC450 Capacity step 150 = RNC450/150

. RNC450 Capacity step 300 = RNC450/300

. RNC450 Capacity step 450 = RNC450/450

Previously delivered RNCs upgraded to RN2.2 = RNC196

. Capacity step 1 = RNC196 Capacity step 48 = RNC196/48

.

Capacity step 2 = RNC196 Capacity step 85 = RNC196/85

DN70515054Issue 1-0 en draft30/09/2008


HW changes








3.1.3.1 New hardware products

The following new hardware products are introduced to the RNC at RN2.2release:

Mechanics and electromechanics:

. EC216: Equipment cabinet

. CPD120-A: Cabinet power distribution

. FTRA-B: Fan tray

. SRA3: Subrack

. SRBI-C: Subrack for the Back Interfaces

.

CPAL-A: Connector Panel for Alarm Signals. CPSY-A and CPSY-B: Connector Panels for Synchronizations

Plug-in units:

. AL2S-D*: new variant for A2SU

. CCP18-C, the default CPU variant. For OMU, CCP18-A*: ControlComputer with Pentium M processor (1.8GHz), including 2GBmemory

. HDS-B: new variant for Hard Disk SCSI adapter

. PD30: subrack power distribution unit

*AL2S-D and CCP18-A are also used in RN2.1 with supportprovided in RN2.1 SW GCD2.0.


30/09/2008

Changes in RU10



3.1.3.2 Upgrading the RNC to RN2.2 RNC196


For RN2.2 SW release upgrade, NEMU hard disks must be at least 18GBin size. Please refer to HW Technical Note 46 RNC RN2.2 Minimum HW

Requirements.

For HSDPA, CDSP-C is required for all DMCU units.

For increased AAL2UP connectivity, AL2S-D is required for all A2SU units.

Optional upgrades and extensions for RNC196

RN2.2 introduces two new capacity steps as well as other optionalhardware upgrades and extensions for previously delivered RNCs(RNC196). See chapter Overview of RN2.2 capacity extensions and

upgrades for more information on the hardware changes. For detailedinformation on how to carry out the upgrades and extensions, seedocuments Hardware upgrade to RNC196/300 and RNC196/450,

Hardware upgrades and extensions for RNC196 and Hardware extensions

for RNC450.

Upgrades with capacity steps:

. Capacity upgrade to RNC196/300: capacity step 6

. Capacity upgrade to RNC196/450: capacity step 7

Optional ESA24 upgrades:

. ESA24 upgrade

This upgrade is for replacing ESA12 with ESA24.

. Redundant ESA24 upgrade

This upgrade is for adding a second ESA24 unit. Redundant ESA24is needed for the AGPS feature.

Optional upgrades when capacity steps RNC196/300 and RNC196/450are not taken into use:

. NEMU upgrades with MCP18-B and HDS-A

NEMU upgrades replace:

DN70515054Issue 1-0 en draft30/09/2008


HW changes



3.2 Flexi WCDMA BTS HW changes

3.2.1 Changes in Flexi WCDMA BTS hardware products

Table 7. New hardware

New Description Location in

documentation

Flexi RF Module 2100MHzTriple 70W (FRGF)

471483A

A stand-alone transceiver module with integrated

antenna filters.

For description information,see Flexi WCDMA BTS RF

Module and Remote Radio Head Description .

Flexi RRH 2100 Single70W (FRGG) 471882A

A stand-alone transceiver module with integratedantenna filters.


Module and Remote Radio

Head Description .

Flexi RRH 2100 Single50W (FRGN) 471833A

A stand-alone transceiver module with integratedantenna filters.


Module and Remote Radio

Head Description .

System Module (FSMC)471401A

A module that hosts thetelecom control, system

operation andmaintenance, basebandapplication, transmission,and power distributionfunctionality.

For description information,see Flexi WCDMA BTS

System Module

Description .

System Module (FSMD)471402A

A module that hosts thetelecom control, systemoperation andmaintenance, basebandapplication, transmission,and power distributionfunctionality.


System Module

Description .

Transmission sub-moduleTransport PDH/Ethernet(FTIB) 471720A

A sub-module that providesthe physical Iub interface tothe radio network controller (RNC) or I-HSPA Adapter.


System Module

Description .

Transmission sub-moduleTransport PDH E1/T1 HighDensity (FTHA) 471522A

A sub-module that providesthe physical Iub interface tothe radio network controller (RNC) or I-HSPA Adapter.


System Module

Description .

DN70515054Issue 1-0 en draft30/09/2008


HW changes



3.3 Ultrasite WCDMA BTS HW Changes

3.3.1 UltraSite WCDMA BTS HW Changes

Table 8. New hardware

New Description Location in

documentation

IFUH interface unit ATM over Ethernetinterface

For description information,see UltraSite WCDMA BTS

Product Description .

3.4 MetroSite 50 BTS HW changes

3.4.1 Changes in MetroSite 50 BTS hardware products

There are no hardware changes for this release.

3.5 AXC changes

3.5.1 HW changes in release C5.5

Timing over Packet is enabled by a new module that can installed to theIFUH interface unit.

See Installing the TOPA module to the IFUH in Expanding and upgrading

AXC .


30/09/2008

Changes in RU10



Number Name Location in

documentation

3320

HIGH LOAD OFUNSUCCESSFULSECURITY EVENTS

3320 HIGH LOAD OF

UNSUCCESSFUL

SECURITY EVENTS

in Failure Printouts

(2000-3999)

3342 CABLING ERROR

3342 CABLING

ERROR in Failure

Printouts (2000-3999)

3353

ERRONEOUS IUA

MESSAGE

3353 ERRONEOUS

IUA MESSAGE inFailure Printouts

(2000-3999)

3364OPTICAL MODULE ISDETACHED

3364 OPTICAL

MODULE IS

DETACHED in Failure


3365OPTICAL MODULE ISFAULTY

3365 OPTICAL

MODULE IS FAULTY

in Failure Printouts

(2000-3999)

3372

PHYSICAL LAYERRESOURCE DETACHEDFROM NETWORKINTERFACE UNIT

3372 PHYSICAL

LAYER RESOURCE

DETACHED FROM

NETWORK

INTERFACE UNIt inFailure Printouts

(2000-3999)

3376CO-UNIT CONNECTIONFAILURE

3376 CO-UNIT

CONNECTION

FAILURE in Failure


3378

OPTICAL MODULE TX

POWER LEVELDECREASED

3378 OPTICAL

MODULE TX

POWER LEVEL

DECREASED in

Failure Printouts (2000-3999)

3379 SCTP PATH FAILURE

3379 SCTP PATH

FAILURE in Failure


3384HMS TRANSMISSION LINEFAULTY

3384 HMS

TRANSMISSION

LINE FAULTY inFailure Printouts

(2000-3999)

DN70515054Issue 1-0 en draft30/09/2008


RNC alarm changes

http://localhost/var/www/apps/conversion/tmp/scratch_3/NED?action=retrieve&library=ru_pre_rel_10_v4&identifier=dn99580865&edition=3&language=en&coverage=global&encoding=pdf_online_a4&component=data&item=data





























































documentation

3385PLUG-IN UNITINSTALLATION ERROR

3385 PLUG-IN UNIT

INSTALLATION

ERROR in Failure


3386

DISCREPANCY BETWEEN ACTUAL HARDWARE ANDITS DESCRIPTION

3386 DISCREPANCY

BETWEEN ACTUAL

HARDWARE AND

ITS DESCRIPTION inFailure Printouts

(2000-3999)

3388

EXCEPTIONALLY HIGHTEMPERATURE IN PLUG-IN UNIT

3388

EXCEPTIONALLY HIGH

TEMPERATURE IN

PLUG-IN UNIT inFailure Printouts

(2000-3999)

3389TOO LOW TEMPERATUREIN PLUG-IN UNIT

3389 TOO LOW

TEMPERATURE IN

PLUG-IN UNIT inFailure Printouts

(2000-3999)

3393TWO ACTIVE HMSMASTERS DETECTED

3393 TWO ACTIVE

HMS MASTERS DETECTED in Failure


3394HMS MASTERNETMALFUNCTION

3394 HMS

MASTERNET

MALFUNCTION inFailure Printouts

(2000-3999)

3408CONNECTIONDISTURBANCE

3408 CONNECTION

DISTURBANCE inFailure Printouts

(2000-3999)

3422SSL/TLS PROTOCOLLAYER MALFUNCTION

3422 SSL/TLS PROTOCOL LAYER

MALFUNCTION inFailure Printouts

(2000-3999)

3445SECURITY REPORTINGDATA FILE CORRUPTED

3445 SECURITY

REPORTING DATA

FILE CORRUPTED inFailure Printouts

(2000-3999)


30/09/2008

Changes in RU10






























































documentation

3469COLD RESTART FAILUREIN PLUG-IN UNIT

3469 COLD

RESTART FAILURE

IN PLUG-IN UNIT inFailure Printouts

(2000-3999)

3471 CPLD UPDATE FAILED

3471 CPLD UPDATE

FAILED in Failure


3472 IU-PS IP ROUTING ERROR

3472 IU-PS IP

ROUTING ERROR inFailure Printouts

(2000-3999)

3484CONFLICTINGSCRAMBLING CODES

3484 CONFLICTING

SCRAMBLING

CODES in Failure


3485SCRAMBLING CODECONFLICT

3485 SCRAMBLING

CODE CONFLICT inFailure Printouts

(2000-3999)

3486

AAL TYPE 2 CAC

REJECTION LEVELEXCEEDED FOR NPS1/ NPS1P UNIT

3486 AAL TYPE 2

CAC REJECTION

LEVEL EXCEEDED

FOR NPS1/NPS1P

UNIT in Failure


3497

IP CONNECTIVITYBROKEN BETWEEN TPG

AND IPNIU

3497 IP

CONNECTIVITY

BROKEN BETWEEN

TPG AND IPNIU inFailure Printouts

(2000-3999)

3993CONGESTION HANDLINGERROR RATIO EXCEEDED

3993 CONGESTION

HANDLING ERROR

RATIO EXCEEDED

in Failure Printouts (2000-3999)

3999

OPTICAL SFPTRANSCEIVER TYPE ISINCORRECT

3999 OPTICAL SFP

TRANSCEIVER

TYPE IS

INCORRECT inFailure Printouts

(2000-3999)

DN70515054Issue 1-0 en draft30/09/2008


RNC alarm changes




























































documentation

7781NETWORK ELEMENTCONFIGURATION ERROR

7781 NETWORK

ELEMENT

CONFIGURATION

ERROR in Base

Station Alarms (7000-

7900)

7783IP BASED D-NBAP LINKFAILURE

7783 IP BASED D-

NBAP LINK FAILURE

in Base Station

Alarms (7000-7900)

7784RECOVERY ACTIONFAILURE

7784 RECOVERY

ACTION FAILURE inBase Station Alarms

(7000-7900)

4.1.2 Changed alarms

There are changes to the following alarms in RN4.0:

Note that SIF means Supplementary Information Field in the table.

Number Name

Change

description

Location in

documentation

1016 MB INTERFACE FAILUREField descriptionschanged

1016 MB INTERFACE

FAILURE in Disturbance


1020PROGRAM BLOCK STARTUP FAILURE

Field descriptionscorrected

1020 PROGRAM BLOCK

START UP FAILURE inDisturbance Printouts

(1000-1999)

1070CCS7 PROGRAM BLOCKDATA ERROR

Instructions

updated, MMLcommandcorrected AHO ->

AAP

1070 CCS7 PROGRAM BLOCK DATA ERROR inDisturbance Printouts

(1000-1999)

1113

STATISTICSMEASUREMENT OUTPUTFAILURE

Instructionsupdated, MMLcommand ISI ->

IHI

1113 STATISTICS

MEASUREMENT

OUTPUT FAILURE inDisturbance Printouts

(1000-1999)

1228

UNIT SUPERVISION NOT

FUNCTIONING

Field descriptions

corrected

1228 UNIT SUPERVISION

NOT FUNCTIONING inDisturbance Printouts

(1000-1999)


30/09/2008

Changes in RU10





































Number Name

Change

description

Location in

documentation

1269 AAL5 FRAMECORRUPTED

SIF structurechanged

1269 AAL5 FRAME

CORRUPTED inDisturbance Printouts

(1000-1999)

1285 AAL5 FRAME LOSTSIF structurechanged

1285 AAL5 FRAME LOST

in Disturbance Printouts

(1000-1999)

1297SOCKET INTERFACEFAILURE

Field descriptionschanged

1297 SOCKET

INTERFACE FAILURE inDisturbance Printouts

(1000-1999)

1425OVERFLOW IN ALARMBUFFERING

Meaning and fielddescriptionsupdated, Q3interface changedto NWI3 interface

1425 OVERFLOW IN

ALARM BUFFERING inDisturbance Printouts

(1000-1999)

1685 UNIT RESTART FAILURE Incorrect format

1685 UNIT RESTART

FAILURE in Disturbance


1806

PRINTER SPOOLER

DISABLED

Instructionsupdated, MMLcommandschanged AHO/ISC

-> AAP/IHE

1806 PRINTER SPOOLER

DISABLED in Disturbance


2274 SOMAFI ERRORMeaning of thealarm updated

2274 SOMAFI ERROR inFailure Printouts (2000-

3999)

2427MMI SYSTEM FILEERROR


2427 MMI SYSTEM FILE

ERROR in Failure


2794HW BLOCK FAILURE INPLUG-IN UNIT

Alarm descriptionchanged

2794 HW BLOCK

FAILURE IN PLUG-IN

UNIT in Failure Printouts

(2000-3999)

2806 SOMAFI UPDATE ERROR

Meaning andinstructionsupdated

2806 SOMAFI UPDATE ERROR in Failure


3046CONNECTION FAILUREIN PLUG-IN UNIT

Instructionsupdated

3046 CONNECTION

FAILURE IN PLUG-IN

UNIT in Failure Printouts

(2000-3999)

3049FAILURE IN PORTCONFIGURATION


3049 FAILURE IN PORT

CONFIGURATION inFailure Printouts (2000-

3999)

DN70515054Issue 1-0 en draft30/09/2008


RNC alarm changes

























Number Name

Change

description

Location in

documentation

3156 ASSOCIATION ROUTINGFAILURE

SIF structurechanged,instructionsupdated

3156 ASSOCIATION

ROUTING FAILURE inFailure Printouts (2000-

3999)

3159SCTP ASSOCIATIONLOST

SIF structurechanged,instructionsupdated

3159 SCTP

ASSOCIATION LOST inFailure Printouts (2000-

3999)

3186

UPPER LIMIT OFPROCESSOR LOAD

EXCEEDED

Alarm description

changed

3186 UPPER LIMIT OF

PROCESSOR LOAD

EXCEEDED in Failure


3188NO RESPONSE TO AAL5CHANNEL SUPERVISION

SIF structurechanged

3188 NO RESPONSE TO

AAL5 CHANNEL

SUPERVISION in Failure


3195LCS CONNECTIONFAILURE

Alarm descriptionchanged

3195 LCS CONNECTION

FAILURED in Failure


3275SEMIPERMANENTCONNECTION ERROR

Alarm instructionsupdated

3275 SEMIPERMANENT

CONNECTION ERROR inFailure Printouts (2000-

3999)

3325

INCONSISTENCY INNOKIA SPECIFICCONFIGURATIONPARAMETERS

Terminologycorrection(branding), alarmtext changed

3325 INCONSISTENCY IN

NOKIA SPECIFIC

CONFIGURATION

PARAMETERS in Failure


3344UX LINK CONNECTIONFAILURE


3344 UX LINK

CONNECTION FAILURE

in Failure Printouts (2000-

3999)

3390SAS DECREASEDSERVICE

Instructionsupdated, RRMUunit remarksremoved

3390 SAS DECREASED

SERVICE in Failure


3391SAS SERVICEUNAVAILABLE


3391 SAS SERVICE

UNAVAILABLE in Failure


3416GPS DATA ACQUISITIONFAILURE


3416 GPS DATA

ACQUISITION FAILURED

in Failure Printouts (2000-

3999)


30/09/2008

Changes in RU10



Number Name

Change

description

Location in

documentation

7650 BASE STATION FAULTY

Instructionsupdated, BTS SWrelease WN4.5updates done

7650 BASE STATION

FAULTY in Base Station

Alarms (7000-7900)

7651BASE STATIONOPERATION DEGRADED


7651 BASE STATION

OPERATION DEGRADED

in Base Station Alarms

(7000-7900)

7652

BASE STATION

NOTIFICATION

Instructionsupdated, BTS SWrelease WN4.5

updates done

7652 BASE STATION

NOTIFICATION in Base


7900)

7653 CELL FAULTY


7653 CELL FAULTY inBase Station Alarms

(7000-7900)

7654CELL OPERATIONDEGRADED


7654 CELL OPERATION

DEGRADED in Base


7900)

7655 CELL NOTIFICATION

Instructionsupdated, BTS SWrelease WN4.5

updates done

7655 CELL

NOTIFICATION in Base


7900)

7660BASE STATION LICENCEEXPIRED


7660 BASE STATION

LICENCE EXPIRED inBase Station Alarms

(7000-7900)

7661BASE STATION LICENCENOTIFICATION


7661 BASE STATION

LICENCE NOTIFICATION


(7000-7900)

7665BASE STATIONTRANSMISSION ALARM


7665 BASE STATION

TRANSMISSION ALARM


(7000-7900)

7750

FAILURE IN WCDMAWBTS O&MCONNECTION


7750 FAILURE IN

WCDMA WBTS O&M

CONNECTION in Base


7900)

7771WCDMA CELL OUT OFUSE

Instructionsupdated

7771 WCDMA CELL OUT

OF USE in Base Station

Alarms (7000-7900)

DN70515054Issue 1-0 en draft30/09/2008


RNC alarm changes



Number Name

Change

description

Location in

documentation

7772HSDPA CONFIGURATIONFAILED


7772 HSDPA

CONFIGURATION FAILED


(7000-7900)

7779RECOVERY ACTIONSONGOING


7779 RECOVERY

ACTIONS ONGOING inBase Station Alarms

(7000-7900)

7782

HSUPA CONFIGURATION

FAILED

Field descriptions

changed

7782 HSUPA

CONFIGURATION FAILED


(7000-7900)

4.1.3 Removed alarms

There are the following alarms removed in RN4.0:

Number Name

Reason for

removal Removed from

3406FAN POWER SUPPYFAILURE

Not included in RN4.0anymore

Failure Printouts (2000-3999)

4.1.4 Alarm system configuration changes

There are the following changes in alarm parameters in RN4.0:

Number Name Change

Location in

documentation

1277PLUG IN UNITCONNECTION FAILURE

RNC alarm systeminternal parameter change.

This alarm can nowbe set also in unit thatis in the TE state.

1277 PLUG IN

UNIT

CONNECTION

FAILURE inDisturbances

(1000-1999)

3975VP/VC LEVEL RDIRECEIVED

Default cancellingdelay changed from10 seconds to 120seconds

3975 VP/VC

LEVEL RDI

RECEIVED inFailure Printouts

(2000-3999)


30/09/2008

Changes in RU10

















5 Key indicator changes

5.1 Changes in key performance indicators

The following changes have been made to WDCMA RAN keyperformance indicators (KPIs) in RU10.

There are the following new KPIs for RU10. Note that the new KPIs are notnumbered until later during RU10. The KPI names used for the new KPIsin this document are only temporary.

All KPI IDs have been updated:

. RAN_KPI_ID -> RNC_ID

All new, updated, and existing KPI formulas have been updated:

. Added a second formula based on counter (short) names

Table 9. New KPIs for RU10

KPI See

RNC_5026a Call Setup Success Ratio [%]

RNC_5006a Packet Session Setup Success Ratio (SSSR) [%]






RNC_5008a Serving Radio Network Subsystem Accessibility Ratio [%]


DN70515054Issue 1-0 en draft30/09/2008


Key indicator changes



Table 9. New KPIs for RU10 (cont.)

KPI See


RNC_5005a Transmission Resource Accessibility Ratio [%]

RNC_5014a Packet Session Success Ratio (SSR) [%]






RNC_5016a Peak Resource Reservation Numbers [Integer number]



RNC_5019a Radio layer (RLC, MAC or FP) Data Volumes [kbit]

RNC_5020a Radio layer (RLC, MAC or FP) Data Volumes [kbit]

RNC_5021a Iu-PS peak throughput [Mbit/s]

RNC_5022a IP based RAN logical interface data volume [Mbit]

RNC_5029a IP based RAN logical interface data volume [Mbit]

RNC_5027a RAN logical interface data volume [Mbit]

RNC_960a ATM layer traffic load [%]

RNC_5023a Block Error ratio (BLER) [%]

RNC_5024a Block Error ratio (BLER) [%]

Table 10. Updated KPIs in RU10

KPI Description of the update

RNC_916a, RNC_922a The ID and definition have been updated.

The changes are needed because the definition must explicitlyindicate that the KPIs are only for the NRT cases (since PacketSessions can also be RT in RU10).

RNC_914b, RNC_915b The formulas have been updated with new counters indicatingthe setup reject in non HSPA capable cells.


30/09/2008

Changes in RU10



Table 10. Updated KPIs in RU10 (cont.)

KPI Description of the update

RNC_920a, RNC_921a, RNC_943a,RNC_944a

The definitions have been updated.

The changes are needed because the definitions mustexplicitly indicate that these KPIs are only for the NRT cases(since Packet Sessions can also be RT in RU10).

RNC_941b The unit of the KPI has been changed.

A note has been added because this KPI is valid only for GTPU unit-based RNCs.

RNC_565f The KPI name has been updated.

RNC_918a The object summary level has been updated.

RNC_95d, RNC_217e The formulas have been updated due to new functionality inRU10

RNC_945b, RNC_946b, RNC_950b,RNC_951b

The definitions have been adjusted to better fit the supposedusage.

The unit of the KPIs has been changed.

RNC_732b The definition has been adjusted to better fit the need.

Table 11. Substituted KPIs in RU10

Old KPI New KPI

RNC_954a RNC_5017a

The substitution has been done because the previous KPI wasbased on a measurement that is not available in RU10.

Table 12. Corrected KPIs in RU10

KPI Description of the correction

rnc_100d Documentation correction: an already available formulacorrection that has not been documented before.

RNC_605a Formula/Description correction: failed setups notified by theUE have impacts and must be included in the KPI.

RNC_949b The formula has been corrected.

DN70515054Issue 1-0 en draft30/09/2008


Key indicator changes




30/09/2008

Changes in RU10



Table 13. Measurement M1024 RCPM OLPC WCEL, new counters (cont.)

PI ID Name

M1024C8 UL AVERAGE BER FOR WCEL

M1024C9 UL AVERAGE BER DENOMINATOR FOR WCEL

M1024C10 SUM OF SQUARED UL BER VALUES FOR WCEL

M1024C11UL NUMBER OF RECEIVED UL BER REPORTS FORWCEL

M1024C12 BAD UPLINK CONNECTIONS FOR WCEL

M1024C13 IDEAL UPLINK CONNECTIONS FOR WCEL

M1024C14 TOO GOOD UPLINK CONNECTIONS FOR WCEL

M1024C15 AVERAGE RADIO LINK POWER IN DL FOR WCEL

M1024C16SUM OF SQUARED RADIO LINK POWER VALUES IN DLFOR WCEL

M1024C17 DL RADIO LINK POWER SAMPLES FOR WCEL

M1024C18RL REPORTS WITH MAXIMUM POWER VALUE FORWCEL

M1024C19 UL E-DCH HARQ RETRANSMISSIONS FOR WCEL

Table 14. Measurement M1025 RCPM OLPC RNC, new counters

PI ID Name

M1025C0 AVERAGE UL EB/NO FOR RN

M1025C1 UL AVERAGE EB/NO DENOMINATOR FOR RNC

M1025C2 UL SUM OF SQUARED EB/NO VALUES FOR RNC

M1025C3 UL NUMBER OF RECEIVED EB/NO REPORTS FOR RNC

M1025C4 UPLINK CRC OK BLOCKS FOR RNC

M1025C5 UPLINK CRC NOK BLOCKS FOR RNC

M1025C6 SUM OF SQUARED BLER VALUES FOR RNC

M1025C7 UL NUMBER OF RECEIVED BLER REPORTS FOR RNC

M1025C8 UL AVERAGE BER FOR RNC

M1025C9 UL AVERAGE BER DENOMINATOR FOR RNC

M1025C10 SUM OF SQUARED UL BER VALUES FOR RNC

M1025C11 UL NUMBER OF RECEIVED UL BER REPORTS FOR RNC

M1025C12 BAD UPLINK CONNECTIONS FOR RNC

M1025C13 IDEAL UPLINK CONNECTIONS FOR RNC


30/09/2008

Changes in RU10



Table 16. Measurement M1027 RCPM RLC RNC, new counters

PI ID Name

M1027C0 AVERAGE AM RLC TRANSMISSION BUFFEROCCUPANCY FOR RNC

M1027C1 AVERAGE PDCP BUFFER OCCUPANCY FOR RNC

M1027C2SUM OF SQUARED AM RLC BUFFER OCCUPANCYVALUES FOR RNC

M1027C3SUM OF SQUARED PDCP BUFFER OCCUPANCYVALUES FOR RNC

M1027C4

REPORTS FOR AVERAGE DL BUFFER OCCUPANCY

FOR RNC

M1027C5 DL PDU ERROR RATIO IN AM RLC FOR RNC

M1027C6 AM RLC PDUS TRANSMITTED IN DOWNLINK FOR RNC

M1027C7 SUM OF SQUARED DL PDU ERROR RATIO FOR RNC

M1027C8 RECEIVED DL PDU REPORTS FOR RNC

M1027C9 BAD RLC AM DL CONNECTIONS FOR RNC

M1027C10 TOO GOOD RLC AM DL CONNECTIONS FOR RNC

M1027C11 IDEAL RLC AM DL CONNECTIONS FOR RNC

M1027C12 DL GROSS THROUGHPUT OF AM RLC PDU FOR RNC

M1027C13SUM OF SQUARED DL GROSS THROUGHPUT OF RLC

AM PDU FOR RNC

M1027C14 REPORTS FOR DL AM RLC THROUGHPUT FOR RNC

M1027C15 DL NET THROUGHPUT OF AM RLC PDU FOR RNC

M1027C16SUM OF SQUARED DL NET THROUGHPUT OF AM RLCPDU FOR RNC

M1027C17SUM OF SQUARED TRANSMISSION TIME VALUES FORDL AM RLC FOR RNC

M1027C18 AVERAGE NUMBER OF TRANSMISSIONS PER PDU IN AM RLC DL FOR RNC

M1027C19 PDU DISCARD RATIO IN AM RLC DL FOR RNC

M1027C20SUM OF SQUARED AVE NUMBER OF PDUTRANSMISSIONS FOR RNC

M1027C21 AM RLC DL PDUS FOR TRANSMISSION FOR RNC

M1027C22 RLC AM SDU DL ERROR RATIO FOR RNC

M1027C23SUM OF SQUARED RLC AM SDU DL ERROR RATIO FORRNC

M1027C24RLC AM DL AVERAGE TRANSFER DELAY OF SDU FORRNC


30/09/2008

Changes in RU10



Table 16. Measurement M1027 RCPM RLC RNC, new counters (cont.)

PI ID Name

M1027C25RLC AM DL SUM OF AVE TRANSFER DELAY OF SDUFOR RNC

M1027C26RLC AM DL SUM OF STANDARD DEVIATIONS OFTRANSFER DELAY OF SDU FOR RNC

M1027C27RLC AM DL SUM OF SQUARED TRANSMISSION DELAYOF SDU FOR RNC

M1027C28 SDUS FOR TRANSMISSION IN RLC AM DL FOR RNC

M1027C29

MEASUREMENT TIME PERIOD FOR DL RLC AM FOR

RNC

M1027C30 UL RLC AM SDU PAYLOAD OF PS TRAFFIC FOR RNC

M1027C31 DL RLC AM SDU PAYLOAD OF PS TRAFFIC FOR RNC

M1027C32 TRANSMITTED AM RLC PDUS IN UPLINK FOR RNC

M1027C33MEASUREMENT TIME PERIOD FOR UL RLC AM FORRNC

M1027C34USER DL THROUGHPUT DISTRIBUTION - CLASS 1 FORRNC










M1027C44RLC RETRANSMISSION DISTRIBUTION - CLASS 0 FORRNC


DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 16. Measurement M1027 RCPM RLC RNC, new counters (cont.)

PI ID Name








M1027C53USER UL THROUGHPUT DISTRIBUTION - CLASS 1 FORRNC


M1027C55 USER UL THROUGHPUT DISTRIBUTION - CLASS 3 FORRNC



Table 17. Measurement M1028 Autodef SHO DSR, new counters

PI ID Name

M1028C0 CPICH ECNO DETECTED CELL SUM

M1028C1 CPICH ECNO DETECTED CELL DENOM

M1028C2 CPICH RSCP DETECTED CELL SUM

M1028C3 CPICH RSCP DETECTED CELL DENOM


30/09/2008

Changes in RU10



Measurements with new counters

The following RNC radio network measurements have new counters inRN4.0:

. M1000 Cell Resource

. M1001 Service Level

. M1002 Traffic

. M1003 L3 Signalling at Iu

. M1004 L3 Signalling at Iur and M1009 L3 Relocation Signalling

. M1005 L3 Signalling at Iub

. M1006 RRC Signalling

. M1007 Soft Handover

. M1008 Intra System Hard Handover

. M1010 Inter System Hard Handover

. M1011 Location Services

. M1021 Iu-PC interface

. M1022 Packet Call

. M1023 Cell Throughput

Table 18. Measurement M1000 Cell Resource, new counters

PI ID Name

M1000C282 MAX NUMBER OF HSDPA USERS PER CELL

M1000C283 MAX NUMBER OF HSUPA USERS PER CELL

M1000C284 SUM OF HSDPA USERS PER CELL

M1000C285 HSDPA USERS PER CELL DENOMINATOR

M1000C286 SUM OF HSUPA USERS PER CELL

M1000C287 HSUPA USERS PER CELL DENOMINATOR

M1000C288 AMR TXPOWER LOAD UNDERLOAD

M1000C289 AMR TXPOWER LOAD BELOW TARGET

M1000C290 AMR TXPOWER LOAD OVER TARGET

M1000C291 AMR TXPOWER LOAD OVERLOAD

M1000C292 AMR SPREADING CODE UNDERLOAD

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 18. Measurement M1000 Cell Resource, new counters (cont.)

PI ID Name

M1000C293 AMR SPREADING CODE LOAD BELOW TARGET

M1000C294 AMR SPREADING CODE LOAD OVER TARGET

M1000C295 AMR SPREADING CODE LOAD OVERLOAD

M1000C296 AMR TRANSMISSION LOAD UNDERLOAD

M1000C297 AMR TRANSMISSION LOAD BELOW TARGET

M1000C298 AMR TRANSMISSION LOAD OVER TARGET

M1000C299 AMR TRANSMISSION LOAD OVERLOAD

M1000C300 SUM STREAMING HS-DSCH MAC-D IN CELL

M1000C301 STREAMING HS-DSCH MAC-D DENOMINATOR

M1000C302 SUM INTERACTIVE HS-DSCH MAC-D IN CELL

M1000C303 INTERACTIVE HS-DSCH MAC-D DENOMINATOR

M1000C304 SUM BACKGROUND HS-DSCH MAC-D IN CELL

M1000C305 BACKGROUND HS-DSCH MAC-D DENOMINATOR

M1000C306 SUM STREAMING E-DCH MAC-D IN CELL

M1000C307 STREAMING E-DCH MAC-D DENOMINATOR

M1000C308 SUM INTERACTIVE E-DCH MAC-D IN CELL

M1000C309 INTERACTIVE E-DCH MAC-D DENOMINATOR

M1000C310 SUM BACKGROUND E-DCH MAC-D IN CELL

M1000C311 BACKGROUND E-DCH MAC-D DENOMINATOR

M1000C312DURATION OF ACTIVE HSDPA USERS - 1SIMULTANEOUS USER

M1000C313DURATION OF ACTIVE HSDPA USERS - 3SIMULTANEOUS USERS

M1000C314DURATION OF ACTIVE HSDPA USERS - 49 TO 52SIMULTANEOUS USERS




M1000C318DURATION OF ACTIVE HSUPA USERS - 1SIMULTANEOUS USER

M1000C319DURATION OF ACTIVE HSUPA USERS - 3SIMULTANEOUS USERS


30/09/2008

Changes in RU10



Table 18. Measurement M1000 Cell Resource, new counters (cont.)

PI ID Name

M1000C320 RECEIVED TOTAL WIDEBAND POWER CLASS 0






















M1000C342 TRANSMITTED CARRIER POWER CLASS 0










DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 19. Measurement M1001 Service Level, new counters (cont.)

PI ID Name

M1001C629 RRC CONN RELEASE DUE TO RNC HW RESOURCES

M1001C630 RRC SETUP SUCCESS CONVERSATIONAL

M1001C631 RRC SETUP SUCCESS STREAMING

M1001C632 RRC SETUP SUCCESS INTERACTIVE

M1001C633 RRC SETUP SUCCESS BACKGROUND

M1001C634 RRC SETUP SUCCESS OTHER

M1001C635 SRB ACTIVE FAILURE CONVERSATIONAL

M1001C636 SRB ACTIVE FAILURE STREAMING

M1001C637 SRB ACTIVE FAILURE INTERACTIVE

M1001C638 SRB ACTIVE FAILURE BACKGROUND

M1001C639 SRB ACTIVE FAILURE OTHER

M1001C640RRC ACTIVE RELEASE AFTER SUCCESSFUL DIRECTEDRETRY

M1001C641 UE SUPPORT FOR GANHO

M1001C642 RRC ACTIVE REL DUE TO INTRA-FREQ HHO

M1001C643 RRC ACTIVE REL DUE TO GANHOM1001C800 RRC ACTIVE REL DUE TO INTER-FREQ HHO

M1001C803 RRC ACTIVE REL DUE TO ISHO

Table 20. Measurement M1002 Traffic, new counters

PI ID Name

M1002C553

NRT DCH SETUP REJECT FOR INTERACTIVE DUE TO

OUT OF CODES DL

M1002C554NRT DCH SETUP REJECT FOR BACKGROUND DUE TOOUT OF CODES DL

M1002C555NRT DCH SETUP REJECT FOR INTERACTIVE DUE TOPOWER LIMITS DL

M1002C556NRT DCH SETUP REJECT FOR BACKGROUND DUE TOPOWER LIMITS DL

M1002C557NRT DCH RECONFIG REJECT FOR INTERACTIVE DUETO OUT OF CODES DL

M1002C558NRT DCH RECONFIG REJECT FOR BACKGROUND DUETO OUT OF CODES DL

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 20. Measurement M1002 Traffic, new counters (cont.)

PI ID Name

M1002C559NRT DCH RECONFIG REJECT FOR INTERACTIVE DUETO POWER LIMITS DL

M1002C560NRT DCH RECONFIG REJECT FOR BACKGROUND DUETO POWER LIMITS DL

M1002C561 AMR LOWER CODEC SF128 SELECTED FOR INCOMINGCALL

M1002C562 AMR LOWER CODEC SF256 SELECTED FOR INCOMINGCALL

M1002C563LOAD BASED AMR CODEC DOWNGRADE SF128SUCCESSFUL

M1002C564LOAD BASED AMR CODEC DOWNGRADE SF256SUCCESSFUL

M1002C565 LOAD BASED AMR CODEC UPGRADE SUCCESSFUL

M1002C566 AMR CODEC CHANGE FAIL DUE TO ICSU LOAD

M1002C567 AMR CODEC CHANGE FAIL DUE TO OTHER REASONS

M1002C568CHANNEL TYPE SWITCH FROM DCH TO HS-DSCH FORSTREAMING

M1002C569

HS-DSCH MAC-D FLOW ALLOCATIONS FOR

STREAMING

M1002C570HS-DSCH 16 KBPS RETURN CH ALLOCATIONS FORSTREAMING



M1002C573 HS-DSCH MAC-D FLOW DURATION FOR STREAMING

M1002C574HS-DSCH 16 KBPS RETURN CH DURATION FORSTREAMING



M1002C577 REJECTED HS-DSCH RETURN CH FOR STREAMING

M1002C578 HS-DSCH NORMAL RELEASE FOR STREAMING

M1002C579HS-DSCH RELEASE DUE TO OTHER FAILURE FORSTREAMING

M1002C580HS-DSCH RELEASE DUE TO MOBILITY DCHTRANSITION FOR STREAMING


30/09/2008

Changes in RU10



Table 21. Measurement M1003 L3 Signalling at Iu, new counters

PI ID Name

M1003C9 RAB RECONF REQ BY CN

M1003C12 RAB RECONF SUCC

M1003C20 RAB RECONF NONSUCC DUE TO RN LAYER CAUSE

M1003C24 RAB RECONF NONSUCC DUE TO MISC CAUSE

Table 22. Measurement M1004 L3 Signalling at Iur and M1009 L3 RelocationSignalling, new counters

PI ID Name

M1004C147 TRANSFERRED DATA FOR AMR IN UL FROM DRNC

M1004C148 TRANSFERRED DATA FOR AMR IN DL TO DRNC

M1004C149TRANSFERRED DATA FOR INTERACTIVE IN UL FROMDRNC

M1004C150TRANSFERRED DATA FOR INTERACTIVE IN DL TODRNC

M1004C151TRANSFERRED DATA FOR BACKGROUND IN UL FROMDRNC

M1004C152TRANSFERRED DATA FOR BACKGROUND IN DL TODRNC

M1004C153TRANSFERRED DATA FOR CS CONVERSATIONAL IN ULFROM DRNC

M1004C154TRANSFERRED DATA FOR CS CONVERSATIONAL IN DLTO DRNC

M1004C155TRANSFERRED DATA FOR CS STREAMING IN UL FROMDRNC

M1004C156 TRANSFERRED DATA FOR PS STREAMING IN UL FROMDRNC

M1004C157TRANSFERRED DATA FOR CS STREAMING IN DL TODRNC

M1004C158TRANSFERRED DATA FOR PS STREAMING IN DL TODRNC

M1004C159 TRANSFERRED DATA FOR PS STREAMING DCH IN UL

M1004C160 TRANSFERRED DATA FOR PS STREAMING DCH IN DL

M1004C161TRANSFERRED DATA FOR NRT INTERACTIVE DCH INUL

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 22. Measurement M1004 L3 Signalling at Iur and M1009 L3 RelocationSignalling, new counters (cont.)

PI ID Name

M1004C162TRANSFERRED DATA FOR NRT INTERACTIVE DCH INDL

M1004C163TRANSFERRED DATA FOR NRT BACKGROUND DCH INUL

M1004C164TRANSFERRED DATA FOR NRT BACKGROUND DCH INDL

M1004C165 NRT DCH SETUP FAIL DUE TO IUR

M1004C166 NRT DCH UL RECONFIG FAIL FOR NRT RB DUE TO IUR

M1004C167 NRT DCH UL RECONFIG FAIL FOR NRT RB DUE TO IUR

M1004C168 SHO BRANCH SETUP FAIL DUE TO IUR

Table 23. Measurement M1005 L3 Signalling at Iub, new counters

PI ID Name

M1005C241 MAC-D SETUP ATTEMPT FOR HSDPAM1005C242 SUCCESSFUL MAC-D SETUP FOR HSDPA

M1005C243 RADIO LINK SETUP TIME

M1005C244 DENOMINATOR FOR RADIO LINK SETUP TIME

M1005C247FAILED MAC-D SETUP FOR HSDPA DUE TO NORESPONSE

M1005C248 FAILED MAC-D SETUP FOR HSDPA DUE TO RN LAYER

M1005C249FAILED MAC-D SETUP FOR HSDPA DUE TOTRANSPORT LAYER

M1005C250 FAILED MAC-D SETUP FOR HSDPA DUE TO PROTOCOL

M1005C251 FAILED MAC-D SETUP FOR HSDPA DUE TO MISC

Table 24. Measurement M1006 RRC Signalling, new counters

PI ID Name

M1006C41 URA UPDATE ATT DUE TO CHANGE OF URA

M1006C42 URA UPDATE ATT DUE TO PER UPDATE

M1006C49 CELL FACH STATE TO URA PCH


30/09/2008

Changes in RU10



Table 24. Measurement M1006 RRC Signalling, new counters (cont.)

PI ID Name

M1006C96 SUM OF UE OPERATING TIME IN URA_PCH

M1006C98 NUM OF UE MEASURED IN URA_PCH

M1006C110 RRC REL DUE TO MS IS LOST IN URA_PCH

M1006C149 RB SETUP ATTEMPT FOR HSDPA

M1006C150 SUCCESSFUL RB SETUP FOR HSDPA

M1006C151 FACH TO HS-DSCH ATTEMPTS

M1006C152 FACH TO HS-DSCH SUCCESSFUL

M1006C153 HS-DSCH TO FACH ATTEMPTS

M1006C154 HS-DSCH TO FACH SUCCESSFUL

M1006C155 PAGING OCCASIONS IN CELL_PCH

M1006C156 PAGING MESSAGES IN CELL_PCH

M1006C157 CELL UPDATE AFTER PAGING IN CELL_PCH

M1006C158 PAGING FAILURE DUE TO NO RESPONSE IN CELL_PCH

M1006C159 PAGING OCCASIONS IN URA_PCH

M1006C160 PAGING MESSAGES IN URA_PCH

M1006C161 CELL UPDATE AFTER PAGING IN URA_PCH

M1006C162 PAGING FAILURE DUE TO NO RESPONSE IN URA_PCH

M1006C163 PAGING DELAY UNTIL CELL UPDATE IN CELL_PCH

M1006C164 PAGING DELAY UNTIL UE RESPONSE IN CELL_PCH

M1006C165PAGING DELAY UNTIL UE RESPONSE IN CELL_PCHDENOMINATOR

M1006C166 PAGING DELAY UNTIL CELL UPDATE IN URA_PCH

M1006C167 PAGING DELAY UNTIL UE RESPONSE IN URA_PCH

M1006C168

PAGING DELAY UNTIL UE RESPONSE IN URA_PCH

DENOMINATOR

M1006C169 PRACH DELAY RANGE PARAMETER VALUE

M1006C170 STATE TRANSITION TIME PCH TO FACH

M1006C171DENOMINATOR FOR STATE TRANSITION TIME PCH TOFACH

M1006C172 STATE TRANSITION TIME FACH TO DCH

M1006C173DENOMINATOR FOR STATE TRANSITION TIME FACH TODCH

M1006C174 STATE TRANSITION TIME PCH TO DCH

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 24. Measurement M1006 RRC Signalling, new counters (cont.)

PI ID Name

M1006C175DENOMINATOR FOR STATE TRANSITION TIME PCH TODCH

M1006C176 STATE TRANSITION TIME DCH TO FACH

M1006C177DENOMINATOR FOR STATE TRANSITION TIME DCH TOFACH

M1006C178 STATE TRANSITION TIME DCH TO PCH

M1006C179DENOMINATOR FOR STATE TRANSITION TIME DCH TOPCH

M1006C180 STATE TRANSITION TIME FACH TO PCH

M1006C181DENOMINATOR FOR STATE TRANSITION TIME FACH TOPCH

M1006C182 RESOURCE ALLOCATION TIME IN RRC SETUP

M1006C183DENOM FOR RESOURCE ALLOCATION TIME IN RRCSETUP

M1006C184 RESOURCE ALLOCATION TIME FROM CELL_FACH

M1006C185DENOM FOR RESOURCE ALLOCATION TIME FROMCELL_FACH

M1006C186 RRC RE-ESTABLISH SUCCESS RT

M1006C187 RRC RE-ESTABLISH FAIL UE RT

M1006C188 RRC RE-ESTABLISH FAIL NO REPLY RT

M1006C189 RRC RE-ESTABLISH SUCCESS MULTI RAB

M1006C190 RRC RE-ESTABLISH FAIL UE MULTI RAB

M1006C191 RRC RE-ESTABLISH FAIL NO REPLY MULTI RAB

M1006C192 RB SETUP FAIL FOR HSDPA DUE TO NO REPLY

M1006C193 RB SETUP FAIL FOR HSDPA DUE TO UE NACK

M1006C194 AAL2 SETUP TIME

M1006C195 DENOMINATOR FOR AAL2 SETUP TIME

M1006C196 ATTEMPTED PCH TO DCH TRANSITIONS USING UM-RLC

M1006C197SUCCESSFUL PCH TO DCH TRANSITIONS USING UM-RLC

M1006C198CELL RESELECTIONS DURING PCH TO DCHTRANSITIONS USING UM-RLC

M1006C199 CELL UPDATE ATT DUE TO DATA TRANSM TVM TRUE


30/09/2008

Changes in RU10



Table 30. Measurement M1014 Autodef IFHO, new counters (cont.)

PI ID Name

M1014C3 CPICH ECNO IFHO DENOMINATOR

M1014C4 CPICH RSCP IFHO SUM

M1014C5 CPICH RSCP IFHO DENOMINATOR

Table 31. Measurement M1015 Autodef ISHO, new counters

PI ID Name

M1015C2 RSSI SUM

M1015C3 RSSI DENOMINATOR

M1015C4 BSIC VERIFICATION TIME

M1015C5 BSIC DENOMINATOR

Table 32. Measurement M1021 Iu-PC interface, new counters

PI ID Name

M1021C9 DIRECT POSITION INITIATION REQUESTS TO SAS

M1021C10 DIRECT POSITION INITIATION RESPONSES FROM SAS

M1021C11 DIRECT POSITION INITIATION FAILURES FROM SAS

M1021C12 SUCCESSFUL CIRTT POSITION ACTIVATION

M1021C13 UNSUCCESSFUL CIRTT POSITION ACTIVATION

M1021C14 SUCCESSFUL AGPS POSITION ACTIVATION

M1021C15 UNSUCCESSFUL AGPS POSITION ACTIVATION

M1021C16 PERIODIC POSITION INITIATION REQUESTS TO SAS

M1021C17PERIODIC POSITION INITIATION RESPONSES FROMSAS

M1021C18 PERIODIC POSITION INITIATION FAILURES FROM SAS

M1021C19PERIODIC POSITION ACTIVATION REQUESTS FROMSAS

M1021C20 PERIODIC POSITION ACTIVATION RESPONSES TO SAS

M1021C21 PERIODIC POSITION ACTIVATION FAILURES TO SAS

M1021C22 PERIODIC POSITION REPORTS TO SAS


30/09/2008

Changes in RU10



Table 32. Measurement M1021 Iu-PC interface, new counters (cont.)

PI ID Name

M1021C23REJECTED DIRECT LOCATION REQUESTS DUE TOFAILED CONNECTION TO SAS

M1021C24REJECTED PERIODIC LOCATION REQUESTS DUE TOFAILED CONNECTION TO SAS

Table 33. Measurement M1022 Packet Call, new counters

PI ID Name

M1022C83INITIAL DCH REQUESTS FOR BITRATE 64 KBPS ANDLOWER UL

M1022C84INITIAL DCH REQUESTS FOR BITRATE 64 KBPS ANDLOWER DL

M1022C85 INITIAL DCH REQUESTS FOR BITRATE 128 KBPS UL

M1022C86 INITIAL DCH REQUESTS FOR BITRATE 128 KBPS DL





M1022C91DCH UPGRADE REQUESTS FOR BITRATE 64 KBPS ANDLOWER UL

M1022C92DCH UPGRADE REQUESTS FOR BITRATE 64 KBPS ANDLOWER DL

M1022C93 DCH UPGRADE REQUESTS FOR BITRATE 128 KBPS UL

M1022C94 DCH UPGRADE REQUESTS FOR BITRATE 128 KBPS DL





M1022C99INITIAL DCH ALLOCATION SUCCESS FOR NRT BITRATE64 KBPS AND LOWER UL

M1022C100INITIAL DCH ALLOCATION SUCCESS FOR NRT BITRATE64 KBPS AND LOWER DL

M1022C101INITIAL DCH ALLOCATION SUCCESS FOR NRT BITRATE128 KBPS UL

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 33. Measurement M1022 Packet Call, new counters (cont.)

PI ID Name

M1022C168 BACKGROUND HS-DSCH RB DURATION DENOMINATOR

M1022C169MAXIMUM DURATION OF STREAMING E-DCH RADIOBEARER

M1022C170MINIMUM DURATION OF STREAMING E-DCH RADIOBEARER

M1022C171SUM OF STREAMING E-DCH RADIO BEARERDURATIONS

M1022C172 STREAMING E-DCH RB DURATION DENOMINATOR

M1022C173MAXIMUM DURATION OF INTERACTIVE E-DCH RADIOBEARER

M1022C174MINIMUM DURATION OF INTERACTIVE E-DCH RADIOBEARER

M1022C175SUM OF INTERACTIVE E-DCH RADIO BEARERDURATIONS

M1022C176 INTERACTIVE E-DCH RB DURATION DENOMINATOR

M1022C177MAXIMUM DURATION OF BACKGROUND E-DCH RADIOBEARER

M1022C178

MINIMUM DURATION OF BACKGROUND E-DCH RADIO

BEARER

M1022C179SUM OF BACKGROUND E-DCH RADIO BEARERDURATIONS

M1022C180 BACKGROUND E-DCH RB DURATION DENOMINATOR

M1022C181 HS-DSCH/E-DCH PACKET CALL ATT FOR STREAMING

M1022C182 HS-DSCH/DCH PACKET CALL ATT FOR STREAMING

M1022C183 DCH/DCH PACKET CALL ATT FOR STREAMING

M1022C184PACKET CALL SETUP FAIL DUE TO AC FORSTREAMING

M1022C185PACKET CALL SETUP FAIL DUE TO BTS FORSTREAMING

M1022C186PACKET CALL SETUP FAIL DUE TO DMCU RES FORSTREAMING

M1022C187PACKET CALL SETUP FAIL DUE TO TRANSM FORSTREAMING

M1022C188PACKET CALL SETUP FAIL DUE TO UE FORSTREAMING

M1022C189PACKET CALL SETUP FAIL DUE TO OTHER REASONSFOR STREAMING

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes




PI ID Name

M1022C190HS-DSCH/E-DCH ALLO AFTER HS-DSCH/E-DCH REQFOR STREAMING

M1022C191HS-DSCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ FORSTREAMING

M1022C192HS-DSCH/DCH ALLO AFTER HS-DSCH/DCH REQ FORSTREAMING

M1022C193DCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ FORSTREAMING

M1022C194DCH/DCH ALLO AFTER HS-DSCH/DCH REQ FORSTREAMING

M1022C195 DCH/DCH ALLO AFTER DCH/DCH REQ FOR STREAMING

M1022C196SWI HS-DSCH/E-DCH TO HS-DSCH/DCH FORSTREAMING

M1022C197 SWI HS-DSCH/E-DCH TO DCH/DCH FOR STREAMING

M1022C198 SWI HS-DSCH/DCH TO DCH/DCH FOR STREAMING

M1022C199SWI HS-DSCH/DCH TO HS-DSCH/E-DCH FORSTREAMING

M1022C200 SWI DCH/DCH TO HS-DSCH/DCH FOR STREAMING

M1022C201 SWI DCH/DCH TO HS-DSCH/E-DCH FOR STREAMING

M1022C202HS-DSCH/E-DCH PACKET CALL NORM REL FORSTREAMING

M1022C203HS-DSCH/DCH PACKET CALL NORM REL FORSTREAMING

M1022C204 DCH/DCH PACKET CALL NORM REL FOR STREAMING

M1022C205HS-DSCH/E-DCH PACKET CALL REL DUE TO PRE-EMPFOR STREAMING

M1022C206HS-DSCH/DCH PACKET CALL REL DUE TO PRE-EMPFOR STREAMING

M1022C207DCH/DCH PACKET CALL REL DUE TO PRE-EMP FORSTREAMING

M1022C208HS-DSCH/E-DCH PACKET CALL REL DUE TO RL FAILFOR STREAMING

M1022C209HS-DSCH/DCH PACKET CALL REL DUE TO RL FAIL FORSTREAMING

M1022C210DCH/DCH PACKET CALL REL DUE TO RL FAIL FORSTREAMING

M1022C211HS-DSCH/E-DCH PACKET CALL REL DUE TO OTHERFAIL FOR STREAMING


30/09/2008

Changes in RU10




PI ID Name

M1022C212HS-DSCH/DCH PACKET CALL REL DUE TO OTHER FAILFOR STREAMING

M1022C213DCH/DCH PACKET CALL REL DUE TO OTHER FAIL FORSTREAMING

M1022C214HS-DSCH/DCH ALLO AFTER HS-DSCH/E-DCH REQINTERA DUE CELL CAPABILITY

M1022C215HS-DSCH/DCH ALLO AFTER HS-DSCH/E-DCH REQBACKG DUE CELL CAPABILITY

M1022C216HS-DSCH/DCH ALLO AFTER HS-DSCH/E-DCH REQSTREAM DUE CELL CAPABILITY

M1022C217DCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ INTERADUE CELL CAPABILITY

M1022C218DCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ BACKGDUE CELL CAPABILITY

M1022C219DCH/DCH ALLO AFTER HS-DSCH/E-DCH REQ STREAMDUE CELL CAPABILITY

M1022C220DCH/DCH ALLO AFTER HS-DSCH/DCH REQ INTERADUE CELL CAPABILITY

M1022C221 DCH/DCH ALLO AFTER HS-DSCH/DCH REQ BACKG DUECELL CAPABILITY

M1022C222DCH/DCH ALLO AFTER HS-DSCH/DCH REQ STREAMDUE CELL CAPABILITY

Table 34. Measurement M1023 Cell Throughput, new counters

PI ID Name

M1023C11 TRANSFERRED DATA FOR AMR IN UL

M1023C12 TRANSFERRED DATA FOR AMR IN DL

M1023C13 TRANSFERRED DATA FOR CS CONVERSATIONAL IN UL

M1023C14 TRANSFERRED DATA FOR CS CONVERSATIONAL IN DL

M1023C15 TRANSFERRED DATA FOR CS STREAMING IN UL

M1023C16 TRANSFERRED DATA FOR CS STREAMING IN DL

M1023C17 TRANSFERRED DATA FOR PS STREAMING IN UL

M1023C18 TRANSFERRED DATA FOR PS STREAMING IN DL

M1023C19 TRANSFERRED DATA FOR INTERACTIVE IN UL

M1023C20 TRANSFERRED DATA FOR INTERACTIVE IN DL

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 34. Measurement M1023 Cell Throughput, new counters (cont.)

PI ID Name

M1023C21 TRANSFERRED DATA FOR BACKGROUND IN UL

M1023C22 TRANSFERRED DATA FOR BACKGROUND IN DL

M1023C23 TRANSFERRED DATA FOR RT E-DCH STREAMING UL

M1023C24TRANSFERRED DATA FOR RT DCH STREAMING FORHSDPA RETURN CHANNEL UL

M1023C25 TRANSFERRED DATA FOR RT HS-DSCH STREAMING DL

Modified counters and measurements

. The following M1001 counters are not supported anymore:. M1001C106 DCH SETUP FAILURES DUE TO IUB AAL2

TRANS FOR PS DATA INTERA. M1001C111 DCH SETUP FAILURES DUE TO IUB AAL2

TRANS FOR PS DATA BACKG

. M1004 L3 Signalling at Iur and M1009 L3 Relocation Signalling. The second object level is generalized from “RNC” to “HOT”

(=Handover Target) so that it can represent both another RNCand I-HSPA Adapter

. M1013 Autodef SHO. New object level "serving RNC" is added to the beginning of

the object hierarchy to represent the RNC which controls theUE. This change corrects some problems experienced inearlier releases when two RNCs produced identical objects toNetAct thus causing measurement data to be lost.

. New object naming "HOS/SCID" (=Handover Source/SourceCell-ID) and "HOT/TCID" (=Handover Target/Target Cell-ID) isused to represent the handover source and target cells. This is

done due to I-HSPA compatibility.

. M1014 Autodef IFHO. New object level "serving RNC" is added to the beginning of

the object hierarchy to represent the RNC which controls theUE. This change corrects some problems experienced inearlier releases when two RNCs produced identical objects toNetAct thus causing measurement data to be lost.

. New object naming "HOS/SCID" (=Handover Source/SourceCell-ID) and "HOT/TCID" (=Handover Target/Target Cell-ID) isused to represent the handover source and target cells. This is

done due to I-HSPA compatibility.


30/09/2008

Changes in RU10



Table 35. Removed counters (cont.)

PI ID Name

M1001C149RAB ACT FAIL FOR CS VOICE CALL DUE TO INTEGRITYCHECK

M1001C159RAB ACT FAIL FOR CS DATA CONV CLASS CALL DUETO INTEGRITY CHECK

M1001C165RAB ACT FAIL FOR CS DATA CALL STREAM CLASS DUETO INTEGRITY CHECK

M1001C177RAB ACT FAIL FOR PS DATA CALL CONV CLASS DUETO INTEGRITY CHECK

M1001C183RAB ACT FAIL FOR PS DATA CALL STREAM CLASS DUETO INTEGRITY CHECK

M1001C189RAB ACT FAIL FOR PS DATA CALL INTERA CLASS DUETO INTEGRITY CHECK

M1001C195RAB ACT FAIL FOR PS DATA CALL BACKG CLASS DUETO INTEGRITY CHECK

M1001C535RAB SETUP FAILURES DUE TO IUR AAL2 TRANS FORCS VOICE

M1001C536RAB SETUP FAILURES DUE TO IUR AAL2 TRANS FORCS CONV

M1001C537 RAB SETUP FAILURES DUE TO IUR AAL2 TRANS FORCS STREAM

M1001C538RAB SETUP FAILURES DUE TO IUR AAL2 TRANS FORPS DATA STREAM

M1001C539RAB SETUP FAILURES DUE TO IU CS AAL2 TRANS FORCS VOICE

M1001C540RAB SETUP FAILURES DUE TO IU CS AAL2 TRANS FORCS CONV

M1001C541RAB SETUP FAILURES DUE TO IU CS AAL2 TRANS FORCS STREAM

M1001C542 DCH HOLDING TIME FOR PS RAB INTERACTIVE THP1



M1001C545DENOMINATOR FOR DCH HOLDING TIMES PS RABINTERACTIVE THP1



M1002C62RT DCH ALLO FOR TRANS CS DATA CONV CLASS 28.8KBPS IN SRNC

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes




PI ID Name

M1002C63RT DCH ALLO FOR TRANS CS DATA CONV CLASS 32KBPS IN SRNC

M1002C64RT DCH ALLO FOR TRANS CS DATA CONV CLASS 33.6KBPS IN SRNC

M1002C66RT DCH ALLO DUR FOR TRANS CS DATA CONV CLASS28.8 KBPS IN SRNC

M1002C67RT DCH ALLO DUR FOR TRANS CS DATA CONV CLASS32 KBPS IN SRNC

M1002C68RT DCH ALLO DUR FOR TRANS CS DATA CONV CLASS33.6 KBPS IN SRNC

M1002C71RT DCH ALLO FOR NONTRANS CS DATA STREAMCLASS 28.8 KBPS IN UL IN SRNC

M1002C74RT DCH ALLO FOR NONTRANS CS DATA STREAMCLASS 28.8 KBPS IN DL IN SRNC

M1002C77RT DCH ALLO DUR FOR NONTRANS CS DATA STREAMCLASS 28.8 KBPS IN UL IN SRNC

M1002C80RT DCH ALLO DUR FOR NONTRANS CS DATA STREAMCLASS 28.8 KBPS IN DL IN SRNC

M1002C116 RT DCH ALLO FOR PS CALL CONV CLASS 320 KBPS INUL IN SRNC

M1002C124RT DCH ALLO FOR PS CALL CONV CLASS 320 KBPS INDL IN SRNC

M1002C132RT DCH ALLO FOR PS CALL STREAM CLASS 320 KBPSIN UL IN SRNC

M1002C140RT DCH ALLO FOR PS CALL STREAM CLASS 320 KBPSIN DL IN SRNC

M1002C148NRT DCH ALLO FOR PS CALL INTERA CLASS 320 KBPSIN UL IN SRNC

M1002C156

NRT DCH ALLO FOR PS CALL INTERA CLASS 320 KBPS

IN DL IN SRNC

M1002C164NRT DCH ALLO FOR PS CALL BACKG CLASS 320 KBPSIN UL IN SRNC

M1002C172NRT DCH ALLO FOR PS CALL BACKG CLASS 320 KBPSIN DL IN SRNC

M1002C180RT DCH ALLO DUR FOR PS CALL CONV CLASS 320KBPS IN UL IN SRNC

M1002C188RT DCH ALLO DUR FOR PS CALL CONV CLASS 320KBPS IN DL IN SRNC

M1002C196

RT DCH ALLO DUR FOR PS CALL STREAM CLASS 320

KBPS IN UL IN SRNC


30/09/2008

Changes in RU10




PI ID Name

M1002C204RT DCH ALLO DUR FOR PS CALL STREAM CLASS 320KBPS IN DL IN SRNC

M1002C212NRT DCH ALLO DUR FOR PS CALL INTERA CLASS 320KBPS IN UL IN SRNC

M1002C220NRT DCH ALLO DUR FOR PS CALL INTERA CLASS 320KBPS IN DL IN SRNC

M1002C228NRT DCH ALLO DUR FOR PS CALL BACKG CLASS 320KBPS IN UL IN SRNC

M1002C236NRT DCH ALLO DUR FOR PS CALL BACKG CLASS 320KBPS IN DL IN SRNC

M1002C301 DCH ALLO FOR DATA CALL 320 KBPS IN UL IN DRNC

M1002C313 DCH ALLO FOR DATA CALL 320 KBPS IN DL IN DRNC

M1002C325DCH ALLO DURA FOR DATA CALL 320 KBPS IN UL INDRNC

M1002C337DCH ALLO DURA FOR DATA CALL 320 KBPS IN DL INDRNC

M1002C445 ALLO FOR COM MODE DL USING PUNCTURINGMETHOD IN DRNC

M1002C450 ALLO DURA FOR COM MODE DL USING PUNCTURINGMETHOD IN DRNC

M1002C451RT DCH SHO BRANCH SETUP FAILURE CS VOICE DUETO RNC EXTERNAL TRANSPORT

M1002C452RT DCH SHO BRANCH SETUP FAILURE CS CONV DUETO RNC EXTERNAL TRANSPORT

M1002C453RT DCH SHO BRANCH SETUP FAILURE CS STREAMDUE TO RNC EXTERNAL TRANSPORT

M1002C454RT DCH SHO BRANCH SETUP FAILURE PS STREAMDUE TO RNC EXTERNAL TRANSPORT

M1002C455 NRT DCH SHO BRANCH SETUP FAILURE PS INTERACTDUE TO RNC EXTERNAL TRANSPORT

M1002C456NRT DCH SHO BRANCH SETUP FAILURE PS BACKGDUE TO RNC EXTERNAL TRANSPORT

M1002C457UL NRT DCH INITIAL SETUP FAILURE FOR INTERACTDUE TO IUB AAL2

M1002C458UL NRT DCH UPGRADE FAILURE FOR INTERACT DUETO IUB AAL2

M1002C459DL NRT DCH INITIAL SETUP FAILURE FOR INTERACTDUE TO IUB AAL2

M1002C460

DL NRT DCH UPGRADE FAILURE FOR INTERACT DUE

TO IUB AAL2

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes




PI ID Name

M1002C461UL NRT DCH INITIAL SETUP FAILURE FORBACKGROUND DUE TO IUB AAL2

M1002C462UL NRT DCH UPGRADE FAILURE FOR BACKGROUNDDUE TO IUB AAL2

M1002C463DL NRT DCH INITIAL SETUP FAILURE FORBACKGROUND DUE TO IUB AAL2

M1002C464DL NRT DCH UPGRADE FAILURE FOR BACKGROUNDDUE TO IUB AAL2

M1002C465UL NRT DCH INITIAL SETUP FAILURE FOR INTERACTDUE TO IUR AAL2

M1002C466UL NRT DCH UPGRADE FAILURE FOR INTERACT DUETO IUR AAL2

M1002C467DL NRT DCH INITIAL SETUP FAILURE FOR INTERACTDUE TO IUR AAL2

M1002C468DL NRT DCH UPGRADE FAILURE FOR INTERACT DUETO IUR AAL2

M1002C469UL NRT DCH INITIAL SETUP FAILURE FORBACKGROUND DUE TO IUR AAL2

M1002C470 UL NRT DCH UPGRADE FAILURE FOR BACKGROUNDDUE TO IUR AAL2

M1002C471DL NRT DCH INITIAL SETUP FAILURE FORBACKGROUND DUE TO IUR AAL2

M1002C472DL NRT DCH UPGRADE FAILURE FOR BACKGROUNDDUE TO IUR AAL2

M1002C473DCH SETUP FAILURES IN DRNC DUE TO RNCEXTERNAL TRANSPORT FOR AMR

M1002C474DCH SETUP FAILURES IN DRNC DUE TO RNCEXTERNAL TRANSPORT FOR DATA

M1003C49 SIGN CONN REL BY CN SUCCESS DUE TO NCCR

M1005C10 RL SETUP FAIL FOR FIRST RL DUE TO O&M INTERV

M1005C11 RL SETUP FAIL FOR FIRST RL DUE TO ALREADY ACTIV

M1005C12RL SETUP FAIL FOR FIRST RL DUE TO HW RES NOT

AVAIL

M1005C13RL SETUP FAIL FOR FIRST RL DUE TO NOT ENOUGHRES

M1005C15 RL SETUP FAIL FOR FIRST RL DUE TO BTS GEN REA

M1005C16RL SETUP FAIL FOR SHO ON SRNC DUE TO O&MINTERV


30/09/2008

Changes in RU10




PI ID Name

M1005C46RL BRANCH ADD FAIL FOR SHO ON SRNC DUE TOO&M INTERV

M1005C47RL BRANCH ADD FAIL FOR SHO ON SRNC DUE TO

ALREADY ACTIV

M1005C48RL BRANCH ADD FAIL FOR SHO ON SRNC DUE TO HWRES NOT AVAIL

M1005C49RL BRANCH ADD FAIL FOR SHO ON SRNC DUE TO NOTENOUGH RES

M1005C51RL BRANCH ADD FAIL FOR SHO ON SRNC DUE TO BTSGEN REA

M1005C52RL BRANCH ADD FAIL FOR SHO ON DRNC DUE TOO&M INTERV

M1005C53RL BRANCH ADD FAIL FOR SHO ON DRNC DUE TO

ALREADY ACTIV

M1005C54RL BRANCH ADD FAIL FOR SHO ON DRNC DUE TO HWRES NOT AVAIL

M1005C55RL BRANCH ADD FAIL FOR SHO ON DRNC DUE TONOT ENOUGH RES

M1005C57 RL BRANCH ADD FAIL FOR SHO ON DRNC DUE TO BTSGEN REA

M1005C59 RL FAIL ON SRNC DUE TO ACT RL SYN FAIL

M1005C60 RL FAIL ON SRNC DUE TO BTS HW OVERL

M1005C61 RL FAIL ON SRNC DUE TO BTS EQUIP FAIL

M1005C63 RL FAILURE ON DRNC DUE TO ACT RLSYN FAIL

M1005C64 RL FAIL ON DRNC DUE TO BTS HW OVERL

M1005C65 RL FAIL ON DRNC DUE TO BTS EQUIP FAIL

M1005C90RL RECONF PREP SYNCH FOR DCH ADD FAIL ONSRNC DUE TO O&M INTERV

M1005C91RL RECONF PREP SYNCH FOR DCH ADD FAIL ONSRNC DUE TO ALREADY ACTIV

M1005C92RL RECONF PREP SYNCH FOR DCH ADD FAIL ONSRNC DUE TO HW RES NOT AVAIL

M1005C93RL RECONF PREP SYNCH FOR DCH ADD FAIL ONSRNC DUE TO NOT ENOUGH RES

M1005C95RL RECONF PREP SYNCH FOR DCH ADD FAIL ONSRNC DUE TO BTS GEN REA

M1005C96RL RECONF PREP SYNCH FOR DCH MOD FAIL ONSRNC DUE TO O&M INTERV


30/09/2008

Changes in RU10




PI ID Name

M1005C121RL RECONF PREP SYNCH FOR DCH DEL FAIL ONDRNC DUE TO ALREADY ACTIV

M1005C122RL RECONF PREP SYNCH FOR DCH DEL FAIL ONDRNC DUE TO HW RES NOT AVAIL

M1005C123RL RECONF PREP SYNCH FOR DCH DEL FAIL ONDRNC DUE TO NOT ENOUGH RES

M1005C125RL RECONF PREP SYNCH FOR DCH DEL FAIL ONDRNC DUE TO BTS GEN REA

M1006C43RRC CONNECTED MODE MOBILES THAT HAVE LEFTTHE CELL

M1006C82 MEAS REPORT MESSAGES WITH EVENT 7A

M1006C83 MEAS REPORT MESSAGES WITH EVENT 7B

M1006C84 MEAS REPORT MESSAGES WITH EVENT 7C

M1006C106 CELL UPDATE ATTEMPT DUE TO NCCR

M1006C107 CELL UPDATE SUCCESS DUE TO NCCR

M1006C108 INTER RAT HO FROM UTRAN ATTEMPT DUE TO NCCR

M1007C3 FOUR CELLS IN THE ACTIVE SET FOR RT (SRNC)

M1007C4 FIVE CELLS IN THE ACTIVE SET FOR RT (SRNC)

M1007C5 SIX CELLS IN THE ACTIVE SET FOR RT (SRNC)

M1007C22 FOUR CELLS IN THE ACTIVE SET FOR NRT (SRNC)

M1007C23 FIVE CELLS IN THE ACTIVE SET FOR NRT (SRNC)

M1007C24 SIX CELLS IN THE ACTIVE SET FOR NRT (SRNC)

6.1.2 RNC Transport & HW Measurements

There are the following new transport and HW measurements in RN4.0:

New measurements

. M145 PDH Statistics

. M208 MTP Signalling link availability

. M209 MTP signalling link performance

. M210 MTP signalling link utilization

. M211 MTP signalling point status


30/09/2008

Changes in RU10



Table 36. Measurement M145 PDH Statistics, new counters (cont.)

PI ID Name

M145B2C54 FRA_CTR_3_UPPER_LIMIT

M145B2C55 FRA_CTR_4_LOWER_LIMIT

M145B2C56 FRAME_ALIGNMENT_ERROR_CTR_1




M145B2C60 NEGATIVE_SLIPS

M145B2C61 POSITIVE_SLIPS

M145B2C62 LOCAL_END_TOTAL_TIME

M145B2C63 LOCAL_END_AVAIL_TIME

M145B2C64 LOCAL_END_UNAVAIL_TIME

M145B2C65 LOCAL_END_DEGRADED_MINUTES

M145B2C66 LOCAL_END_ERRORED_SECONDS

M145B2C67 LOCAL_END_ERROR_FREE_SEC

M145B2C68 LOCAL_END_SER_ERRORED_SEC

M145B2C69 LOCAL_END_BBE

M145B2C70 REMOTE_END_TOTAL_TIME

M145B2C71 REMOTE_END_AVAIL_TIME

M145B2C72 REMOTE_END_UNAVAIL_TIME

M145B2C73 REMOTE_END_DEGRADED_MINUTES

M145B2C74 REMOTE_END_ERRORED_SECONDS

M145B2C75 REMOTE_END_ERROR_FREE_SEC

M145B2C76 REMOTE_END_SER_ERRORED_SEC

M145B2C77 REMOTE_END_BBE

Table 37. Measurement M208 MTP Signalling link availability, new counters

PI ID Name

M208B2C1 DUR_OF_UNAVAIL

M208B2C2 DUR_OF_UNAVAIL_LINK_FAILURE

M208B2C3 DUR_OF_UNAVAIL_LOCAL_BLOCKING

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 37. Measurement M208 MTP Signalling link availability, new counters(cont.)

PI ID Name

M208B2C4 DUR_OF_UNAVAIL_REM_PROC_OUTAGE

M208B2C5 DUR_OF_INHIBIT_LOC_MANAG_ACT

M208B2C6 DUR_OF_INHIBIT_REM_MANAG_ACT

M208B2C7 DUR_OF_LOCAL_BUSY

M208B2C8 LOCAL_MANUAL_CHANGEOVERS

M208B2C9 REMOTE_INITIATIVE_CHANGEOVERS

M208B2C10 REM_PROC_OUTAGE_START

M208B2C11 REM_PROC_OUTAGE_STOP

M208B2C12 LOC_MANAG_INHIBIT

M208B2C13 LOC_MANAG_UNINHIBITED

M208B2C14 REM_INHIBIT

M208B2C15 REM_UNINHIBITED

M208B2C16 DURAT_LOC_BUSY_ATM

Table 38. Measurement M209 MTP signalling link performance, new counters

PI ID Name

M209B2C1 DUR_IN_SERVICE_STATE

M209B2C2 LINK_FAILURES_ALL_REASONS

M209B2C3 LINK_FAILURES_ABNORM_FIBR_BSNR

M209B2C4 LINK_FAILURES_EXC_DEL_OF_ACK

M209B2C5 LINK_FAILURES_EXC_ERROR_RATE

M209B2C6 LINK_FAILURES_EXC_DUR_OF_CONG

M209B2C7 LINK_FAILURES_ALI_OR_PROV_FAIL

M209B3C1 SIGN_UNITS_RECEIVED_IN_ERROR

M209B3C2 NEGATIVE_ACKS

M209B3C3 AUTOMATIC_CHANGEOVERS

M209B3C4 AUTOMATIC_CHANGEBACKS

M209B3C5 LINK_RESTORATIONS

M209B3C6 SD_LOSS


30/09/2008

Changes in RU10



Table 39. Measurement M210 MTP signalling link utilization, new counters

PI ID Name

M210B1C2 BIT_RATE

M210B2C1 SIF_AND_SIO_OCTETS_TRANSMITTED

M210B2C2 SIF_AND_SIO_OCTETS_RECEIVED

M210B2C3 MSUS_TRANSMITTED

M210B2C4 MSUS_RECEIVED

M210B2C5 OCTETS_RETRANSMITTED

M210B2C6 SL_CONGESTION_LEVEL1



M210B2C9 MSUS_DISCARDED_LEVEL1



M210B2C12 EVENTS_RES_IN_LOSS_OF_MSUS_L1



M210B2C15 CUMULATIVE_DURATION_LEVEL1



M210B3C1 30_MIN_PEAKLOAD_TRAFFIC_IN

M210B3C2 30_MIN_PEAK_TRAF_IN_STARTED

M210B3C3 30_MIN_PEAKLOAD_TRAFFIC_OUT

M210B3C4 30_MIN_PEAK_TRAF_OUT_STARTED

M210B3C5 5_MIN_PEAKLOAD_TRAFFIC_IN

M210B3C6 5_MIN_PEAK_TRAF_IN_STARTED

M210B3C7 5_MIN_PEAKLOAD_TRAFFIC_OUT

M210B3C8 5_MIN_PEAK_TRAF_OUT_STARTED

Table 40. Measurement M211 MTP signalling point status, new counters

PI ID Name

M211B2C1 ADJACENT_SP_INA_DURATION

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 42. Measurement M213 MTP Signalling traffic report of signalling points,new counters (cont.)

PI ID Name

M213B3C2 TRANSMITTED_OCTETS_1

M213B3C3 STP_2


M213B3C5 STP_3


M213B3C7 STP_4


M213B3C9 STP_5


M213B3C11 STP_6


M213B3C13 STP_7


M213B3C15 STP_8


M213B2C2 TOTAL_OCTETS_TRANS_TO_DPC

Table 43. Measurement M214 MTP Signalling traffic report of user parts, newcounters

PI ID Name

M214B2C1 RECEIVED_OCTETS

M214B2C2 TRANSMITTED_OCTETS

Table 44. Measurement M215 MTP matrix signalling traffic, new counters

PI ID Name

M215B2C1 NBR_OF_SIF_AND_SIO_OCTETS

M215B2C2 NBR_OF_MSUS

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 45. Measurement M216 SCCP signalling point, new counters (cont.)

PI ID Name

M216B3C72 SS_CONGESTED_MESSAGES_RXED_15

M216B3C73 SS_PROHIBITED_MESSAGES_RXED_15

M216B3C74 SS_ALLOWED_MESSAGES_RXED_15

M216B3C75 SUBSYSTEM_NUMBER_16




















Table 46. Measurement M217 SCCP subsystem, new counters

PI ID Name

M217B2C1 SS_OOS_REQUEST_GRANTED_LOCAL

M217B2C2 SS_OOS_REQUEST_GRANTED_REMOTE

M217B2C3 SS_OOS_REQUEST_DENIED_LOCAL

M217B2C4 SS_OOS_REQUEST_DENIED_REMOTE

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 46. Measurement M217 SCCP subsystem, new counters (cont.)

PI ID Name

M217B2C5 TOTAL_MSGS_TO_LOC_SS_NO_GT

M217B2C6 TOTAL_MSGS_TO_LOC_SS_WITH_GT

M217B2C7 TOTAL_MSGS_FROM_LOC_SS_NO_GT

M217B2C8 TOTAL_MSGS_FROM_LOC_SS_WITH_GT

M217B2C9 TOTAL_MESSAGES_FOR_LOCAL_SS

M217B2C10 TOTAL_MSGS_SENT_TO_BACKUP_SS

M217B2C11 TOTAL_MESSAGES_SENT_CLASS_0

M217B2C12 TOTAL_MESSAGES_SENT_CLASS_1

M217B2C13 TOTAL_MESSAGES_RXED_CLASS_0

M217B2C14 TOTAL_MESSAGES_RXED_CLASS_1

M217B2C15 DT_1_MESSAGES_RECEIV_FROM_MTP

M217B2C16 DT_1_MESSAGES_SENT_TO_MTP

M217B2C17 DT_2_MESSAGES_RECEIV_FROM_MTP

M217B2C18 DT_2_MESSAGES_SENT_TO_MTP

M217B2C19 ED_MESSAGES_RECEIVED_FROM_MTP

M217B2C20 ED_MESSAGES_SENT_TO_MTP

M217B2C21 LOCAL_SS_PROHIBITED_START

M217B2C22 LOCAL_SS_PROHIBITED_STOP

M217B2C23 MSGS_TOO_BIG_FOR_SEGMENTATION

Table 47. Measurement M218 SCCP local subsystem availability, newcounters

PI ID Name

M218B2C1 START_LOC_SCCP_UNAV_FAILURE

M218B2C2 START_LOC_SCCP_UNAV_MAINT_BUSY

M218B2C3 START_LOC_SCCP_UNAV_MAINT_CONG

M218B2C4 STOP_OF_LOCAL_SCCP_UNAVAILABLE

M218B2C5 DURA_OF_LOCAL_SCCP_UNAVAILABLE


30/09/2008

Changes in RU10



Table 51. Measurement M553 AAL2 Scheduling Performance in RNC, newcounters (cont.)

PI ID Name

M553C16 Q1_QUE_DRP_EVENTS

M553C17 Q2_QUE_USAGE_PEAK

M553C18 Q2_QUE_PACKETS_SUM

M553C19 Q2_QUE_SAMPLES

M553C20 Q2_QUE_DELAY_PEAK

M553C21 Q2_QUE_DELAY_SUM

M553C22 Q2_QUE_DELAY_SAMPLES
















M553C38 AAL2_PATH_QUE_DOWN_MSGS

M553C39 AAL2_PATH_QUE_UP_MSGS

M553C40 AAL2_PATH_QUE_STOP_MSGS

M553C41 AAL2_PATH_QUE_FULL_MSGS

M553C42 AAL2_PATH_QUE_HALF_MSGS

Measurement M553 AAL2 Scheduling Performance in RNC is redesignedand counters M553C0-M553C9 are replaced by M550C10-M553C42.

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 52. Measurement M563 TCP/IP Protocol, new counters

PI ID Name

M563C236 SCTP_CURRENT_ESTABLISHMENT

M563C237 SCTP_ACTIVE_ESTABLISHMENT

M563C238 SCTP_PASSIVE_ESTABLISHMENT

M563C239 SCTP_RESTARTED

M563C240 SCTP_ABORTED

M563C241 SCTP_SHUTDOWNS

M563C242 SCTP_TOO_MANY_RETRANSMISSIONS

M563C243 SCTP_RECEIVED_BYTES

M563C244 SCTP_RECEIVED_PACKETS

M563C245 SCTP_RECEIVED_DATAGRAMS

M563C246 SCTP_RECEIVED_CONTROL

M563C247 SCTP_RECEIVED_OOTB

M563C248 SCTP_RECEIVED_DUPLICATED_TSN

M563C249 SCTP_DROPPED_FRAGMENT

M563C250 SCTP_BAD_SSN

M563C251 SCTP_BAD_CSUM

M563C252 SCTP_BAD_VTAG

M563C253 SCTP_BAD_STREAM_NBR

M563C254 SCTP_IN_MULTICAST

M563C255 SCTP_HEADER_DROPS

M563C256 SCTP_RECEIVE_WINDOW_DROPS

M563C257 SCTP_NO_PORTS

M563C258 SCTP_NO_MEMORY

M563C259 SCTP_SENT_BYTES

M563C260 SCTP_SENT_DATAGRAMS

M563C261 SCTP_SENT_CONTROL

M563C262 SCTP_SENT_RETRANSMISSIONS

M563C263 SCTP_SENT_FAST_RETRANSMISSIONS

M563C264 SCTP_SENT_WINDOW_PROBE

M563C265 SCTP_RECEIVED_CHUNK_DATA

M563C266 SCTP_SENT_CHUNK_DATA

M563C267 SCTP_RECEIVED_CHUNK_SACK


30/09/2008

Changes in RU10



Table 52. Measurement M563 TCP/IP Protocol, new counters (cont.)

PI ID Name

M563C268 SCTP_SENT_CHUNK_SACK

M563C269 SCTP_RECEIVED_CHUNK_HBREQ

M563C270 SCTP_SENT_CHUNK_HBREQ

M563C271 SCTP_RECEIVED_CHUNK_HBACK

M563C272 SCTP_SENT_CHUNK_HBACK

Table 53. Measurement M564 Ethernet Interface Performance, new counters

PI ID Name

M564C0 ETHER_RX_FRAME

M564C1 ETHER_RX_KILOBYTE

M564C2 ETHER_RX_MULTICAST_FRAME

M564C3 ETHER_RX_BROADCAST_FRAME

M564C4 ETHER_RX_UNICAST_FRAME

M564C5 ETHER_RX_64_FRAME

M564C6 ETHER_RX_65_127_FRAME




M564C10 ETHER_RX_1024_MAX_FRAME

M564C11 ETHER_RX_FRAME_ALIGMENT_ERR

M564C12 ETHER_RX_TOO_LONG_FRAME

M564C13 ETHER_RX_TOO_SHORT_FRAME

M564C14 ETHER_RX_CRC_ERR

M564C15 ETHER_RX_BUFFER_OVERFLOW

M564C16 ETHER_RX_VLAN_TAGGED

M564C17 ETHER_TX_FRAME

M564C18 ETHER_TX_KILOBYTE

M564C19 ETHER_TX_MULTICAST_FRAME

M564C20 ETHER_TX_BROADCAST_FRAME

M564C21 ETHER_TX_UNICAST_FRAME

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 54. Measurement M565 IP measurement on IP interface, new counters(cont.)

PI ID Name

M565C18 IP6_IN_NO_ROUTES

M565C19 IP6_IN_REAS_REQDS

M565C20 IP6_IN_TOO_BIG_ERRORS

M565C21 IP6_IN_TRUNCATED_PKTS

M565C22 IP6_OUT_BYTES

M565C23 IP6_OUT_REQUESTS

M565C24 IP6_OUT_NO_L2_ROUTES

M565C25 IP6_OUT_FRAG_OKS

M565C26 IP6_OUT_FRAG_FAILS

M565C27 IP6_OUT_FRAGREATES

Table 55. Measurement M566 UDP measurement on IP interface, newcounters

PI ID Name

M566C0 IN_DATAGRAMS

M566C1 NO_PORTS

M566C2 IN_ERRORS

M566C3 OUT_DATAGRAMS

Table 56. Measurement M567 IP QoS measurement, new counters

PI ID Name

M567C0 INGRESS_RECEIVED_PACKETS

M567C1 INGRESS_RECEIVED_BYTES

M567C2 EGRESS_SENT_PACKETS

M567C3 EGRESS_SENT_BYTES

M567C4 DISCARDED_PACKETS

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 57. Measurement M568 IP Based Route, new counters

PI ID Name

M568C0 OUT_DATA_IP_ROUTE

M568C1 IN_DATA_IP_ROUTE

M568C2 COMMITTED_BIT_RATE_IP_ROUTE

M568C3 SUM_RESERVED_RATE_IP_ROUTE

M568C4 MIN_RESERVED_RATE_IP_ROUTE

M568C5 MAX_RESERVED_RATE_IP_ROUTE

M568C6 SUM_IP_UDP_CONN_IP_ROUTE

M568C7 MIN_IP_UDP_CONN_IP_ROUTE

M568C8 MAX_IP_UDP_CONN_IP_ROUTE

M568C9 NBR_SAMPLES_IP_ROUTE

Table 58. Measurement M609 DSP service statistics, new counters

PI ID Name

M609C0 DSP_SERVICE_CURR_RES_ALLOC

M609C1 DSP_SERVICE_PEAK_RES_ALLOC

M609C2 DSP_SERVICE_SUCC_RES_ALLOC

M609C3 DSP_SERVICE_FAIL_RES_ALLOC

M609C4 DSP_SERVICE_FAIL_RES_MODIFY

Table 59. Measurement M612 DSP state changes, new counters

PI ID Name

M612C0 RESTART_SYS

M612C1 RESTART_USER


30/09/2008

Changes in RU10



Table 60. Measurement M615 DSP Resource Utilization, new counters

PI ID Name

M615C0 AVAILABLE_CAP_ON_NE

M615C1 LOWEST_CAP_ON_NE

M615C2 CURR_RES_ALLOC_ON_NE

M615C3 PEAK_RES_ALLOC_ON_NE

M615C4 SUCC_RES_ALLOC_ON_NE

M615C5 FAIL_ALLOC_DSP_ON_NE

M615C6 FAIL_ALLOC_PPC_ON_NE

M615C7 FAIL_MODIFY_ON_NE

M615C8 SER_POOL_OVERFLOW_ON_NE

Table 61. Measurement M617 DSP load, new counters

PI ID Name

M617C0 PROC_NUM_AVG

M617C1 CPU_LOAD_AVG

M617C2 MEM_USE_INTER_AVG

M617C3 MEM_USE_EXTER_AVG

M617C4 PROC_NUM_MAX

M617C5 CPU_LOAD_MAX_PROC_NUM

M617C6 MEM_USE_INTER_MAX_PROC_NUM

M617C7 MEM_USE_EXTER_MAX_PROC_NUM

M617C8 CPU_LOAD_MAX

M617C9 PROC_NUM_MAX_CPU_LOAD

M617C10 MEM_USE_INTER_MAX_CPU_LOAD

M617C11 MEM_USE_EXTER_MAX_CPU_LOAD

M617C12 MEM_USE_INTER_MAX

M617C13 PROC_NUM_MAX_MEM_USE_INTER

M617C14 CPU_LOAD_MAX_MEM_USE_INTER

M617C15 MEM_USE_EXTER_MAX_MEM_USE_INT

M617C16 MEM_USE_EXTER_MAX

M617C17 PROC_NUM_MAX_MEM_USE_EXTER

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 63. Measurement M802 RNC capacity usage, new counters (cont.)

PI ID Name

M802C6 AMR_DISTR_CLASS_4

M802C7 AMR_LIC_CAPACITY

M802C8 IU_PS_THR_AVERAGE

M802C9 IU_PS_THR_PEAK

M802C10 IUB_PS_THR_DISTR_CLASS_0





M802C15 IUB_PS_THR_LIC_CAPACITY

M802C16 IU_PS_THR_LIMIT_DURATION

M802C17 AVE_RRC_CONN_MODE_USERS

M802C18 MAX_RRC_CONN_MODE_USERS

M802C19 AVE_USERS_CELL_DCH

M802C20 AVE_USERS_CELL_FACH

M802C21 AVE_USERS_CELL_PCH

M802C22 AVE_USERS_URA_PCH

Table 64. Measurement M803 RNC RTP/RTCP, new counters

PI ID Name

M803C0 REC_RTP_PACKETS

M803C1 REC_RTP_PAYLOAD

M803C2 SENT_RTP_PACKETS

M803C3 SENT_RTP_PAYLOAD

M803C4 LOST_RTP_PACKETS

M803C5 SENT_RTCP_PACKETS

M803C6 REC_RTCP_PACKETS

M803C7 RTP_JITTER_CLASS_1



DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 64. Measurement M803 RNC RTP/RTCP, new counters (cont.)

PI ID Name


















M803C27 MAX_RTP_JITTER

M803C28 LOST_EGRESS_RTP_PACKETS

Table 65. Measurement M804 RNC IP CAC, new counters

PI ID Name

M804C0 SUCC_RNC_IP_RES

M804C1 FAIL_RNC_IP_RES_EXT

M804C2 FAIL_RNC_IP_RES_INT

M804C3 FAIL_RNC_IP_RES_OTHER

M804C4 SUCC_BTS_IP_RES

M804C5 FAIL_BTS_IP_RES_EXT_TRANS

M804C6 FAIL_BTS_IP_RES_OTHER_TRANS


30/09/2008

Changes in RU10



Table 67. Measurement M5003 Frame Protocol in WBTS, new counters

PI ID Name

M5003C3 CCH DATA VOLUME TO IUB-INTERFACE

M5003C4 CCH DATA VOLUME FROM IUB-INTERFACE

M5003C5 DCH DATA VOLUME TO IUB-INTERFACE

M5003C6 DCH DATA VOLUME FROM IUB-INTERFACE

M5003C7 E-DCH DATA VOLUME TO IUB-INTERFACE

M5003C8 CCH FP DATA FRAMES SUCCESSFULLY RECEIVED

M5003C9CCH FP DATA FRAMES DISCARDED DUE TO HEADERCRC ERROR

M5003C10CCH FP DATA FRAMES DISCARDED DUE TO TOO HIGHDELAY

M5003C11CCH FP DATA FRAMES DISCARDED DUE TO OTHERREASONS

M5003C12 DCH FP DATA FRAMES SUCCESSFULLY RECEIVED

M5003C13DCH FP DATA FRAMES DISCARDED DUE TO HEADERCRC ERROR

M5003C14DCH FP DATA FRAMES DISCARDED DUE TO TOO HIGHDELAY

M5003C15DCH FP DATA FRAMES DISCARDED DUE TO OTHERREASONS

M5003C16 HS-DSCH FP DATA FRAMES SUCCESSFULLY RECEIVED

M5003C17HS-DSCH FP DATA FRAMES DISCARDED DUE TOHEADER CRC ERROR

M5003C18HS-DSCH FP DATA FRAMES DISCARDED DUE TOOTHER REASONS

M5003C19 MAC-E PDU LOST

M5003C20 HS-DSCH DATA VOLUME FROM IUB-INTERFACE

Measurements with new counters

The following measurements have new counters in WN5.0:

. M5000 HSPA in WBTS

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



Table 68. Measurement M5000 HSPA in WBTS, new counters

PI ID Name

M5000C40 MAC-D PDUS SIZE OF 656

M5000C158 HSDPA USERS 0 IN TARGET CELL 4 IN OTHER CELL


















M5000C176 HS-DSCH CREDIT REDUCTIONS DUE TO IUB DELAY

M5000C177HS-DSCH CREDIT REDUCTIONS DUE TO SEVERE IUBDELAY

M5000C178 HS-DSCH CREDIT REDUCTIONS DUE TO FRAME LOSS

M5000C179

HS-DSCH CREDIT REDUCTIONS DUE TO MAC-HS

BUFFER FILLING

M5000C180 UE SERVING POWER HEADROOM VALUE 00









30/09/2008

Changes in RU10



Table 68. Measurement M5000 HSPA in WBTS, new counters (cont.)

PI ID Name

M5000C220 UE NON-SERVING POWER HEADROOM VALUE 08
























M5000C244 NON-SERVING E-RGCH COMMANDS

M5000C245 FRACTIONAL LOAD VALUE DISTRIBUTION - CLASS 00








30/09/2008

Changes in RU10



Table 68. Measurement M5000 HSPA in WBTS, new counters (cont.)

PI ID Name















M5000C266 HSUPA NUMBER OF HAPPY BITS

M5000C267 HSUPA NUMBER OF UNHAPPY BITS

M5000C268 SAMPLES IN HS-PDSCH POWER CLASS 01










M5000C278DROPPED 656 BIT MAC-D PDUS DUE TO BUFFEROVERFLOW

M5000C279 DROPPED MAC-D PDUS DUE TO MAX RETX

M5000C280 DROPPED 656 BIT MAC-D PDUS DUE TO MAX RETX

M5000C281 DROPPED MAC-D PDUS DUE TO OTHER REASON

M5000C282DROPPED 656 BIT MAC-D PDUS DUE TO OTHERREASON

DN70515054Issue 1-0 en draft30/09/2008


Measurement changes



7.2.3 (YG) BFHAND - BFD Supervision Handling

Program's function: With this MML command group you can handle thesession and profile parameters related to BFDconnections in packet networks.

New command(s) andmenu text(s):

R HANDLE PROFILE

S HANDLE SESSION

7.3 Modified MML programs

7.3.1 (IA) AUTHOR - MMI System Authority Handling

Modified command(s) andmenu text(s):

A CREATE OR MODIFY PROFILE

D DELETE USER ID

I INTERROGATE USER IDs, TERMINALS ANDPROFILES

Q RESET LOGIN DELAYS

Modified command: A CREATE OR MODIFY PROFILE

DN70515054Issue 1-0 en draft30/09/2008


MML command changes



Modified command: A CREATE OR MODIFY PROFILE

Description of changes: New parameters ADMPROF and DABLETIME havebeen added. Administrative profile: with theparameter ADMPROF, the operator can definewhether the profile is an administrative profile or not.Possible values are YES and NO. The default isNO. When an administrative user logs into thesystem, the notice admin_user_logged_in_a is set.This makes it possible to supervise users with ahigh authorization level. If the parameter's value isYES, the disable time parameter is automatically setto 0 so that the account of the administrative profilewill not be disabled. This is an optional parameter. Itis visible if the User Account Policy feature isactivated. Disable time: With the parameter DABLETIME, the operator can define the maximaltime between successful logins; that is, the timeafter which a user account is disabled if it is notused. Possible values are whole numbers from 0 to250 (indicating days). The value 0 means that theuser will not be disabled automatically. If <administrative profile> has the value YES, the<disable time> parameter is automatically set to 0.This is to ensure that there is at least one user account with a high authorization level that will notbe disabled. This is an optional parameter. It isvisible if the User Account Policy feature isactivated.

Old syntax: IAA:<profile>: [ BASEP = <base profile> |

[ [ <command class> = ALL def ] = [

<authority> | 1 def ] ] ... ] ... : [ VTIME =

[ <password validity time> | FOREVER | 100

def ], MINVTIME = [ <minimum password

validity time> | 0 def ], ACCESS = [COM |

MED | LIM def ], UNIQUE = [ YES | NO def ] ]

... , PWPOLICY = [ <password policy name> ]

]: [ TLIMIT =

<MML_session_idle_time_limit> | 15 def ]:

FTP = [ W | R | NO def ] ;

New syntax: IAA:<profile>: [ BASEP = <base profile> |

[ [ <command class> = ALL def ] = [<authority> | 1 def ] ] ... ] ... : [ VTIME =

[ <password validity time> | FOREVER | 100

def ], MINVTIME = [ <minimum password

validity time> | 0 def ], ACCESS = [COM |

MED | LIM def ], UNIQUE = [ YES | NO def ] ]

... , PWPOLICY = [ <password policy name>

], ADMPROF = [ YES | NO def ], DABLETIME = [

<disable time > | 0 def ] ]: [ TLIMIT =

<MML_session_idle_time_limit> | 15 def ]:

FTP = [ W | R | NO def ] ;

The command still works with the old syntax.


30/09/2008

Changes in RU10



Modified command: G REMOVE NETWORK INTERFACE

Old semantics: The interface name must start with 'AA' (external ATM point to point interface), 'AI' (internal ATM pointto point interface), 'EL' (Ethernet interface in DMXunits), 'IFETH' and 'IFFGE' (Etherent interfaces inChorus units), 'PPP' (POS interface in IP-NIU units),or 'LO' (Loopback interface).

New semantics: The interface name must start with 'AA' (externalIPOA interface), 'AI' (internal IPOA interface), 'IFAE'(external IPOA interface), 'IFAI' (internal IPOAinterface) , 'EL' (Ethernet interface), 'IFETH' and'IFFGE' (ethernet interface), 'IFFE' and 'IFGE'(Ethernet interface), 'LO' (loopback interface), or 'VL'(VLAN interface).

The command entry continues in the same way asbefore after a semantic error.

Modified command: W FORCE INTERFACE SWITCHOVER

Description of changes: VLAN interface has been added as a new option for the <interface name> parameter, which defines thenetwork interface that you want to force toswitchover. In addition, new interface names have

been added for external and internal IP over ATMinterface and for Ethernet interface, and the POSinterface in IP-NIU units has been removed.


New semantics: The interface name must start with 'AA' (externalIPOA interface), 'AI' (internal IPOA interface), 'IFAE'(external IPOA interface), 'IFAI' (internal IPOAinterface) , 'EL' (Ethernet interface), 'IFETH' and

'IFFGE' (ethernet interface), 'IFFE' and 'IFGE'(Ethernet interface), 'LO' (loopback interface), or 'VL'(VLAN interface).


Modified command: I INTERROGATE NETWORK INTERFACE

DN70515054Issue 1-0 en draft30/09/2008


MML command changes



Modified command: I INTERROGATE NETWORK INTERFACE

Description of changes: VLAN interface has been added as a new option for the <interface name> parameter, which defines thenetwork interface that you want to force toswitchover. In addition, new interface names havebeen added for external and internal IP over ATMinterface and for Ethernet interface, and the POSinterface in IP-NIU units has been removed.


New semantics: The interface name must start with 'AA' (externalIPOA interface), 'AI' (internal IPoA interface), 'IFAE'(external IPoA interface), 'IFAI' (internal IPOAinterface) , 'EL' (Ethernet interface), 'IFETH' and'IFFGE' (ethernet interface), 'IFFE' and 'IFGE'(Ethernet interface), 'LO' (loopback interface), or 'VL'(VLAN interface).


Modified command: S INTERROGATE NETWORK STATUS

Description of changes: VLAN interface has been added as a new option for the <interface name> parameter, which defines thenetwork interface that you want to force toswitchover. In addition, new interface names havebeen added for external and internal IP over ATMinterface and for Ethernet interface, and the POSinterface in IP-NIU units has been removed.

Old semantics: The interface name must start with 'AA' (external ATM point to point interface), 'AI' (internal ATM pointto point interface), 'EL' (Ethernet interface in DMX

units), 'IFETH' and 'IFFGE' (Etherent interfaces inChorus units), 'PPP' (POS interface in IP-NIU units),or 'LO' (Loopback interface).

New semantics: The interface name must start with 'AA' (externalIPOA interface), 'AI' (internal IPoA interface), 'IFAE'(external IPoA interface), 'IFAI' (internal IPOAinterface) , 'EL' (Ethernet interface), 'IFETH' and'IFFGE' (ethernet interface), 'IFFE' and 'IFGE'(Ethernet interface), 'LO' (loopback interface), or 'VL'(VLAN interface).



30/09/2008

Changes in RU10



7.3.6 (RI) ANAINQ - Digit Analysis Interrogation


I INTERROGATE DIGIT ANALYSES

R SEARCH DIGIT ANALYSES

Modified command: I INTERROGATE DIGIT ANALYSES

Description of executionprint-out changes:

The optional value % has been added to the DIGITvalues. It indicates that the analysis has a default

result. Unused parameters CT, SP, NL and RC havebeen removed from the printout.

Modified command: R SEARCH DIGIT ANALYSES

Description of executionprint-out changes:

The optional value % has been added to the DIGITvalues. It indicates that the analysis has a defaultresult. Unused parameters CT, SP, NL and RC havebeen removed from printout text.

7.3.7 (RM) DANAMO - Digit Analysis Modification


M MODIFY GENERAL DATA OF DESTINATION

Deleted command(s) andmenu text(s):

F MODIFY ADDITIONAL DATA (This command hashad no use in IPA)

Modified command: M MODIFY GENERAL DATA OF DESTINATION

Description of changes: In the third parameter block, the names of theparameters subdestination type and percentage

value of subdestination (SPERC0-SPERC4) have

been changed to P00-P04. The maximum count of the parameters is the same as the amount of thealternatives. The values of the parameters must addup to 100, or all types are alternative (A).

Old syntax: RMM:<destination>::SPREC0=50,

SPERC1=50:;


30/09/2008

Changes in RU10



Modified command: M MODIFY GENERAL DATA OF DESTINATION

New syntax: RMM:<destination>::P00=50,P01=50:;

The command still works with the old syntax.

7.3.8 (YE) ETSHAN - Exchange Terminal Supervision Handling


A MODIFY ALARM LIMITS

C MODIFY FUNCTIONAL MODES

G MODIFY T1 AND JT1 FUNCTIONAL MODES

M MODIFY ET PARAMETERS

S MODIFY STATISTICS COUNTERS LIMITS

U MODIFY SLIP LIMITS

Modified command: A MODIFY ALARM LIMITS

Description of changes: Default value of parameter <unit index> haschanged.

Old semantics: Default value is <all> unit indexes.

New semantics: Command is not possible without parameter <unitindex> except with value ALL in parameter <unittype>.

The command entry does not continue in the sameway as before after a semantic error.

Modified command: C MODIFY FUNCTIONAL MODES





DN70515054Issue 1-0 en draft30/09/2008


MML command changes



Modified command: G MODIFY T1 AND JT1 FUNCTIONAL MODES





Modified command: M MODIFY ET PARAMETERS





Modified command: S MODIFY STATISTICS COUNTERS LIMITS





Modified command: U MODIFY SLIP LIMITS





30/09/2008

Changes in RU10




30/09/2008

Changes in RU10



8 New and removed features in earlier

releases

8.1 New and removed features in RAS06

New features

The following radio resource management and telecom features havebeen introduced in RAS06:

. Feature RAN928: Directed Retry

. Feature RAN831: Wideband AMR Codec Set (12.65, 8.85, 6.6)

. Feature RAN1013: 16 kbit/s Return Channel DCH Data RateSupport for HSDPA

. Feature RAN852: HSDPA 15 Codes

. Feature RAN853: HSDPA Code Multiplexing

. Feature RAN1033: HSDPA 48 Users per Cell

. Feature RAN1034: Shared HSDPA Scheduler for BasebandEfficiency

.

Feature RAN312: HSDPA Dynamic Resource Allocation. Feature RAN826: Basic HSUPA

. Feature RAN973: HSUPA Basic RRM

. Feature RAN968: HSUPA BTS Packet Scheduler

. Feature RAN970: HSUPA Handovers

. Feature RAN992: HSUPA Congestion Control

. Feature RAN974: HSUPA with Simultaneous AMR Voice Call

DN70515054Issue 1-0 en draft30/09/2008


New and removed features in earlier releases



. Feature RAN1150: RNC Support for Traffica

. Feature RAN1128: Dynamic Access Class Restriction

. Feature RAN212: Selectable RNW Plan Activation Mechanism

. Feature RAN1059: Flexi WCDMA BTS Support for RNS Split

. Feature RAN1084: Direct Activation of RNW Changes Using NWI3

. Feature RAN618: Centralised User Information Management for BTS

. Feature RAN1159: IP Address & Port based Filtering for BTS LMPs

.

Feature RAN33: IP Security for O&M Traffic between RNC andNetAct

. Feature RAN1451: Mass Change of Local BTS Passwords

The following performance monitoring features have been introduced inRAS06:

. Feature RAN1068: 3GPP TS 32.403 Related Counter Additions for RAN

. Feature RAN868: ATM Transport Statistics Reporting in RAN

. Feature RAN86: Cell Throughput Measurements in Serving RNC

. Feature RAN234: HSDPA Subscriber Trace

. Feature RAN1052: HSUPA Subscriber Trace

The following RNC solution features have been introduced in RAS06:

. Feature RAN1151: Linux Based OMS Replacing NEMU

. Feature RAN1623: Carrier Connectivity Optimised RNC450

The following BTS solution features have been introduced in RAS06:

. Feature RAN906: Flexi WCDMA BTS 3GPP Antenna Tilt Support

. Feature RAN908: Flexi WCDMA BTS AISG MHA Support

. Feature RAN1670: UltraSite EDGE Wideband Combiner for WCDMA Refarming

. Feature RAN1223: 40W Remote Radio Head 2100

. Feature RAN1222: External GPS Synchronisation for Flexi BTSSystem Module Rel 1

DN70515054Issue 1-0 en draft30/09/2008





. Feature RAN1091: BTS SW Management with RNC/NEMU

Mediation. Feature RAN557: Combined HW Management for Flexi WCDMA

BTS and its Transport Module

. Feature RAN1040: Data Backup for AXC

. Feature RAN1181: RNC NEMU Firewall

. Feature RAN812: Local User Authentication for BTS

. Feature RAN617: Remote User Information Management for AXC

. Feature RAN375: Read Only -Access for RNC & AXC Element

Managers

. Feature RAN183: Remote User Event Log Management for RNC

. Feature RAN615: Remote User Event Log Management for AXC

. Feature RAN181: Remote User Information Management for RNC

. Feature RAN1167: Domain Specific Access Class Restriction

. Feature RAN801: Radio Network Access Regulation Function

. Feature RAN956: BTS Channel Element Capacity Measuring

. Feature RAN1153: Complementary Counters in RAS05.1

. Feature RAN190: Radio Connection Performance Measurementsfor RLC TM and UM and Outer Loop Power Control

. Feature RAN1054: Downlink Packet Data Throughput for Subscriber and Equipment Trace

. Feature RAN189: Automatic Definition of Neighbouring Cells

. Feature RAN232: CPICH Ec/No Coverage Measurements andOptimisation

.

Feature RAN1036: RNC196 / Step6-300M and Step7-450MCapacity Upgrades

. Feature RAN607: Connectivity Support for 512 BTSs

. Feature RAN640: Star Configuration: 512 BTSs

. Feature RAN1186: RNC450

. Feature RAN900: Nokia Flexi WCDMA BTS

. Feature RAN999: Flexi WCDMA BTS 1700/2100

. Feature RAN1046: Feederless Site Solution for Flexi WCDMA BTS


30/09/2008

Changes in RU10



. Feature RAN905: Flexi WCDMA BTS Nokia MHA Support

. Feature RAN907: Antenna Line Supervision

. Feature RAN943: Synchronising WCDMA RAN (Flexi WCDMABTS)

. Feature RAN1093: HSDPA 16QAM SW Licence Support

. Feature RAN912: Licence Based BTS Channel Capacity

Removed features

No removed features.

8.3 New and removed features in RAS05

New features

The following features have been introduced in RAS05:

. Feature RAN395: Enhanced Priority Based Scheduling andOverload Control for NRT Traffic

.

Feature RAN763: HSDPA with QPSK and 5 Codes. Feature RAN869: HSDPA BTS Packet Scheduler

. Feature RAN871: HSDPA Flow Control

. Feature RAN821: HSDPA Resource Allocation

. Feature RAN235: HSDPA Channel Switching

. Feature RAN1094: HSDPA Resumption Timer

. Feature RAN766: Shared Control Channel Power Control

.

Feature RAN233: HSDPA Associated Uplink DPCH Scheduling

. Feature RAN764: HSDPA 16QAM Support

. Feature RAN1148: HSDPA Cell Reselection

. Feature RAN230: HSDPA Mobility Handling with DCH Switching

. Feature RAN964: Directed RRC Connection Setup for HSDPA Layer

. Feature RAN820: HSDPA with Additional RAB Initiation

. Feature RAN236: HSDPA Transport with Best Effort AAL2 QoS

DN70515054Issue 1-0 en draft30/09/2008





. Feature RAN1131: Alternative AAL2 Routing for Iu-cs

. Feature RAN954: Redundant Static Routes at Iu-PS

. Feature RAN844: Management for BTS Performance Data

. Feature RAN891: Configurable Heart-beat Interval for RNC

. Feature RAN881: DST Indication in RNC Alarm Display

. Feature RAN880: Time-zone Indication in RNC Alarm Display

. Feature RAN178: RNC Management Tool for Fault Localisation

. Feature RAN068: Larger Font Size for Element Managers

. Feature RAN1025: Remote RNC SW Management Tool in NEMU

. Feature RAN594: Automatic Notification to NetAct for Changed RNCHW Configuration

. Feature RAN2.0089: Service Differentiation and Iu CS ThroughputCounters

. Feature RAN773: AAL2 Resource Reservation Statistics

. Feature RAN224: ATM VP/VC Traffic Measurement

. Feature RAN953: Radio Connection Performance Measurements

for RLC Acknowledged Mode

. Feature RAN1194: WCELL Based Alarms in Threshold Monitoring

. Feature RAN1141: AAL2 Connectivity Improvement

. Feature RAN1111: Additional STM-1 Units in RNC Capacity Steps1...5

. Feature RAN611: MetroSite50

. Feature RAN685: Support for Asymmetric BTS Configurations

.

Feature RAN393: Support for Large BTS Configurations. Feature RAN120: Advanced Indoor Radio (AIR)

. Feature RAN1056: MORAN - Operator Dedicated BB

Removed features



30/09/2008

Changes in RU10



8.4 New and removed features in RAN04

New features

The following features have been introduced in RAN04:

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

. Feature RAN2.0060: IMSI Based Handover

. Feature RAN2.0084: Packet Scheduler Interruption Timer

. Feature RAN1039: Lightweight Flexible Upgrade of NRT DCH Data

Rate. Feature RAN920: Selective NRT DCH Data Rate Set

. Feature RAN2.0107: RRC Connection Re-establishment

. Feature RAN2.0022: Support for Volume Based Charging

. Feature RAN2.0079: Directed RRC Connection Setup

. Feature RAN474: Multi-RAB: AMR + 3 PS data

. Feature RAN475: Multi-RAB: CS data + PS data

.

Feature RAN2.0051: Streaming Packet Switched Quality of Service. Feature RAN2.0041: LCS - Cell Coverage Based (RTT) with

Geographical Coordinates

. Feature RAN384: Directed Emergency Call Inter-System Handover for US

. Feature RAN2.0023: Service Area Broadcast

. Feature RAN2.0042: Nokia Multi-Operator RAN

. Feature RAN2.0085: AAL2 Reconfiguration

. Feature RAN2.0070: AXC-C

. Feature RAN2.0061: BTS STM-1/VC-12 OC-3/VC-11

. Feature RAN649: US WCDMA BTS Sonet OC-3c Interface

. Feature RAN653: US WCDMA BTS T1 Interface

. Feature RAN2.0037: RNC Sonet OC-3c Interface

. Feature RAN2.0036: RNC T1 Interface

. Feature RAN2.0094: Optimized Iub AAL2 Reservations for Common

Channels

DN70515054Issue 1-0 en draft30/09/2008





. Feature RAN2.0086: Master WAM Redundancy

. Feature RAN710: Micro MHA and RealTilt+

. Feature RAN639: Support for 3rd Party Mast Head Amplifier

. Feature RAN644: WCDMA Metrosite Door Alarm

. Feature RAN899: WPAK

. Feature RAN2.0066: WSMB (Wideband Summing & MultiplexingVersion B) Unit

. Feature RAN771: 1900MHz BTS Configuration

Removed features


8.5 New and removed features in RAN1.5

New features

The following features have been introduced in RAN1.5:

. Feature RAN1.007: RAN Procedures for the Idle UEs

. Feature RAN1.008: RAN - UE Connection Establishment

. Feature RAN1.009: Management of the Connected Mode UE

. Feature RAN1.010: Radio Access Bearer Establishment andRelease

. Feature RAN1.012: Radio Link Allocation for Real-Time Radio Access Bearer Services

. Feature RAN1.011: UE Location Management with Handover Procedures

. Feature RAN419: SRNS Relocation

. Feature RAN1.015: Packet Data Transfer States

. Feature RAN1.020: Encryption and Integrity Protection

. Feature RAN1.022: Packet Data Handling on Iu

. Feature RAN1.013: Layer 2 for the Real-Time Radio Access Bearers

. Feature RAN1.016: Layer 2 for the Non-Real-Time Radio Access

Bearers

DN70515054Issue 1-0 en draft30/09/2008





. Feature RAN1.014: Macro Diversity Combining and Splitting

. Feature RAN1.017: Transport Channels and Physical Channels

. Feature RAN1.018: Transport Channel Coding and Multiplexing

. Feature RAN1.019: Spreading and Modulation

. Feature RAN1.021: Logical Resource Management

. Feature RAN1.027: Admission Control Algorithm

. Feature RAN1.028: Resource Manager Algorithm

. Feature RAN1.029: Packet Scheduler Algorithm

. Feature RAN1.025: Power Control Algorithm

. Feature RAN1.026: Load Control Algorithm

. Feature RAN1.024: Soft Handovers

. Feature RAN1.5010: Inter-Frequency Handover

. Feature RAN1.5009: WCDMA - GSM Inter-System Handover

. Feature RAN1.5008: GSM - WCDMA Inter-System Handover

. Feature RAN866: Dynamic Link Optimization for NRT Traffic

Coverage. Feature RAN919: Decrease of the Retried NRT DCH Bit Rate

. Feature RAN1124: Paging Channel State (Cell_PCH)

. Feature RAN1.038: ATM-based Iu

. Feature RAN1.037: ATM-based Iub/Iur

. Feature RAN1.5060: Crossconnecting E1 Frames through BTS/ AXC

. Feature RAN1.034: E1 Physical Interface

. Feature RAN1104: Integrated ATM Functionality

. Feature RAN1.036: Synchronising WCDMA RAN

. Feature RAN1.039: Use of GSM Transmission

. Feature RAN1.057: Standalone AXC Site Solution

. Feature RAN1.5021: BTS Flexbus Interface

. Feature RAN1.030: JT1 Physical Interface (Japan)

. Feature RAN1.035: STM-1 Physical Interface


30/09/2008

Changes in RU10



. Feature RAN1.032: STM-1 Physical Interface (Japan)

. Feature RAN1.5024: RNC STM-1/3xVC-3 Interface

. Feature RAN1.5026: RNC STM-1/VC-4 Interface

. Feature RAN1.5057: BTS AAL2 Multiplexing Function

. Feature RAN1.5058: Efficient ATM Capacity Sharing Using CircuitEmulation

. Feature RAN1.5020: Transmission Capacity Sharing with FractionalE1/JT1

. Feature RAN1.5056: Transmission Capacity Sharing with

Unstructured CES

. Feature RAN1.5034: MSP Protection for RNC STM-0 and STM-1

. Feature RAN151: BTS SDH Interface Protection Using StandardMSP

. Feature RAN1.051: Alarm System

. Feature RAN1.041: Graphical User Interface

. Feature RAN1.050: RNC Computing Platform System Maintenance

.

Feature RAN1.5050: BTS Shutdown with Battery Back Up Unit. Feature RAN1.5027: AXC Q1 Support

. Feature RAN1.5053: BTS Testing Functions

. Feature RAN1.048: Radio Network Recovery

. Feature RAN1.5054: Nokia Power System Management (PSM)

. Feature RAN1.044: Radio Network Configuration Management

. Feature RAN1.043: Radio Network Integration

.

Feature RAN1.5051: Automated Roll-out Support in BTS and AXC. Feature RAN1.5028: Combined GSM & WCDMA Management

. Feature RAN1.042: Transmission Network Management

. Feature RAN1.5029: DCN Configuration Enhancement

. Feature RAN1.040: DCN Architecture for O&M

. Feature RAN1.046: HW Management

. Feature RAN1.045: SW Management

.

Feature RAN1.049: Resets and Initialisations

DN70515054Issue 1-0 en draft30/09/2008





. Feature RAN1.054: Performance Management

. Feature RAN1.052: Radio Network Monitoring Statistics

. Feature RAN1.053: Radio Network Online Monitoring

. Feature RAN1458: RNC196

. Feature RAN1.059: Nokia UltraSite WCDMA BTS Optima Compact

. Feature RAN1.5039: Nokia UltraSite WCDMA BTS Optima Indoor

. Feature RAN1.001: Nokia UltraSite WCDMA BTS Supreme Indoor

. Feature RAN1.5055: Nokia UltraSite WCDMA BTS Supreme

Outdoor . Feature RAN1.5044: Triple-Mode Nokia UltraSite EDGE BTS Indoor

and Outdoor

. Feature RAN1.5040: Nokia MetroSite WCDMA BTS

. Feature RAN1.5033: 40 W Transmit Power with Single WPA Unit

. Feature RAN1.5042: ROC Rollout Optimised Concept

. Feature RAN1.004: WCDMA BTS/GSM BTS Co-Siting Solution

Removed features



30/09/2008

Changes in RU10



9 Parameter changes

9.1 RNC Parameter Changes

For more information on changes in RNC parameters, see WCDMA RAN

parameter changes document.

9.2 Changes in Plan Editor AXC Parameters

9.2.1 Introduction

The following sections describe the changes in parameters supported byNetAct Radio Access Configurator among Plan Editor AXC C5.5 and AXCC3.0. The information is intended for those involved in network planning,implementation and roll-out, configuration management, and engineeringsupport.

For more information on parameters in Plan Editor AXC Parameters, seePlan Editor AXC Parameters .

9.2.2 New Parameters in AXC PE 5.5

9.2.2.1 AXC

Parameter Description

vccBundleEnabled (VCCBundle Enabling Flag)

This parameter enables VCC bundling for collecting extra bandwidth unused byneighbour VCCs.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.2.2.2 IEIF


activeEthernetLink (ActiveEthernet Link)

Active Ethernet Link. E.g. for pseudowire theethernet link which actually carries thetunnel. The activeEthernetLink has tosupport the vlan Tag defined by vlanId.

ethIfNetId (EthernetInterface Identifier )

Identifies an ethernet interface on the AXC.The first interface is always used for theLMP. Range: slot# where slot number = 1..6.

localIpAddr (Local Addressof the IP Interface)

IP address of the BTS in the transportnetwork. To be entered in dotted decimal

format.

shapedBandwidth(Shaping Bandwidth)

This is the egress shaping bandwidth on thenetwork interface (in kbit/s). The relatedparameter upperLayingShaping decides if shaping is for the IP layer only or if theethernet overhead is taken into account.

upperLayerShaping (Upper Layer Shaping EnabledFlag)

This parameter decides if shaping takes theethernet overhead into account whenshaping the bandwidth or not. If the flag hasvalue true, the associated shapedBandwidthis the bandwidth on the IP layer only. If theflag has value false the Ethernet header iscounted also. Use "true" for an IP onlynetwork, e.g. xDSL, use "false" for anEthernet network, e.g. Metro Ethernet.

vLanEnabled (Vlanmapping enabled flag)

This flag indicates if Vlan mapping isenabled for this ethernet interface. Value"true" means that Vlan mapping is enabled.In case Vlan mapping is not enabled, allmessages on the interface will be sent inplain format.

vlanId (Vlan ID) Vlan ID to be used over this ethernetinterface. The parameter is only relevant if vlan mapping is enabled (parameter vlanEnabled has value true).

9.2.2.3 MODUL


moduleId (ModuleIdentifier)

This is the naming attribute of the class.Currently only the TOP chip set is modelled.The value is therefore always 1.

moduleTypeActual (ActualModule Type)

Returns the type of the module. For the TOPchip set the value is T32107.13.


30/09/2008

Changes in RU10




moduleTypeExpected(Expected Module Type)

Defines the type of the module expected for a specific unit. For the TOP chip set theexpected type is T32107.13.

9.2.2.4 TOPIK


administrativeState(Administrative State)

Used to lock and unlock the TOP objectinstance. Locking the object deactivates itand supresses all its alarms. values are:

locked, unlocked

logMeanSyncValue (Logmean synchronizationvalue)

This indicates how often a ToP syncmessage shall be send by the ToP master within the transmission duration requestperiod. (The transmission duration periodcurrently is fixed to 300 seconds.) Thefollowing values are defined: -3: 8 per second -4: 16 per second -5: 32 per second

masterClockState (Master clock state)

This parameter holds the state of theTimeOverPacket master clock. It is a read-only parameter. Values are:MASTER_CLOCK_OK,

MASTER_CLOCK_UNKNOWN,MASTER_CLOCK_DISABLED,MASTER_CLOCK_NOT_OK

masterIpAddr (IP Addressof the ToP master)

IP address of the ToP master. To be enteredin dotted format.

nextHopIpAddr (Next hopIP address of the ToPmaster)

Next Hop IP address for reaching the ToPmaster. To be entered in dotted decimalformat. Value 0.0.0.0 indicates "not used".

topId (Identifier of the ToPinstance)

This parameter uniquely defines the instanceof the ToP class. The value corresponds tothe number of the slot that contains the IFUHcard with the TOP chip set.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.2.3 Changed parameters in AXC PE 5.5

9.2.3.1 ACCP

egressBandwidth (Egress Bandwidth)

Field AXC_PE 3.0 AXC_PE 5.5

Description Defines the maximum allowed egressbandwidth in cells per second for a logical

ATM interface. Nokia AXC Manager automatically sets the following values (cells/ s) for each interface type: - STM-1/STS-3c:353207 - E1/VC-12: 4528 - T1/JT1: 3622 -

fractional E1: int(m*150,9434) where m =number of timeslots - fractional T1/JT1: int(m*150,9434) where m = number of timeslots- IMA E1: int[n*4528*(m-1)/m*2048/2049]where m = Tx Frame Length and n = number of IMA links in a group - IMA T1/JT1: int[n*3622*(m-1)/m*2048/2049] where m = TxFrame Length and n = number of IMA linksin a group - ATM over Ethernet: 72452Range is 1..4294967295 cps.

Defines the maximum allowed egressbandwidth in cells per second for a logical

ATM interface. The AXC Manager automatically sets the following values (cells/ s) for each interface type: - STM-1/STS-3c:353207 - E1/VC-12: 4528 - T1/JT1: 3622 -

fractional E1: int(m*150,9434) where m =number of timeslots - fractional T1/JT1: int(m*150,9434) where m = number of timeslots- IMA E1: int[n*4528*(m-1)/m*2048/2049]where m = Tx Frame Length and n =number of IMA links in a group - IMA T1/JT1:int[n*3622*(m-1)/m*2048/2049] where m = TxFrame Length and n = number of IMA linksin a group - ATM over Ethernet: 72452


30/09/2008

Changes in RU10



ingressBandwidth (Ingress Bandwidth)


Description Defines the maximum allowed ingressbandwidth in cells per second for a logical

ATM interface. Nokia AXC Manager automatically sets the following values (cells/ s) for each interface type: - STM-1/STS-3c:353207 - E1/VC-12: 4528 - T1/JT1: 3622 -fractional E1: int(m*150,9434) where m =number of timeslots - fractional T1/JT1: int(m*150,9434) where m = number of timeslots- IMA E1: int[n*4528*(m-1)/m*2048/2049]

where m = Tx Frame Length and n = number of IMA links in a group - IMA T1/JT1: int[n*3622*(m-1)/m*2048/2049] where m = TxFrame Length and n = number of IMA linksin a group - ATM over Ethernet: 72452 STM-1/STS-3c -> 353207 E1/VC-12 -> 4528 T1/ JT1 -> 3622 Fractional E1 -> int(m*150,9434) //m: number of timeslotsFractional T1/JT1 -> int(m*150,9434) //m:number of timeslots IMA E1 -> int[n*4528*(m-1)/m*2048/2049] //m: Tx Frame Length; n:number of IMA links in a group IMA T1/JT1 -> int[n*3622*(m-1)/m*2048/2049] //m: TxFrame Length; n: number of IMA links in a

group Range is 1..4294967295 cps.

Defines the maximum allowed ingressbandwidth in cells per second for a logical

ATM interface. The AXC Manager automatically sets the following values (cells/ s) for each interface type: - STM-1/STS-3c:353207 - E1/VC-12: 4528 - T1/JT1: 3622 -fractional E1: int(m*150,9434) where m =number of timeslots - fractional T1/JT1: int(m*150,9434) where m = number of timeslots- IMA E1: int[n*4528*(m-1)/m*2048/2049]

where m = Tx Frame Length and n =number of IMA links in a group - IMA T1/JT1:int[n*3622*(m-1)/m*2048/2049] where m = TxFrame Length and n = number of IMA linksin a group - ATM over Ethernet: 72452

9.2.3.2 AXC

equipmentHolderSpecificType (Basestation Variant)


Description Indicates the Basestation Variant. TheBasestation Variant is derived from theBackplane the AXC is connected to. The

number of WAMs within a Basestationdepend on the Basestation Variant. Thefollowing mapping applies: Variant # Slots #WAM Value MetroSite WCDMA 2 1"068796A" UltraSite WCDMA Optima 4 4"070055A" UltraSite WCDMA OptimaCompact 4 4 "070055A" UltraSite WCDMAOptima 4 4 "079688A" UltraSite WCDMASupreme 6 6 "T32101.01" UltraSite WCDMASupreme 6 6 "075983A" UltraSite WCDMASupreme 6 6 "080436A" Triple-ModeUltraSite Edge 2 2 "071086A" NokiaMetroSite 50 2 1 "081212A" Stand Alone

AXC 6 0 "T32106.01"

Indicates the Basestation Variant. TheBasestation Variant is derived from theBackplane the AXC is connected to. The

number of WAMs within a Basestationdepend on the Basestation Variant. Thefollowing mapping applies: Variant # Slots #WAM Value MetroSite WCDMA 2 1"068796A" UltraSite WCDMA Optima 4 4"070055A" UltraSite WCDMA OptimaCompact 4 4 "070055A" UltraSite WCDMAOptima 4 4 "079688A" UltraSite WCDMASupreme 6 6 "T32101.01" UltraSite WCDMASupreme 6 6 "075983A" UltraSite WCDMASupreme 6 6 "080436A" Triple-ModeUltraSite Edge 2 2 "071086A" MetroSite 50 21 "081212A" Stand Alone AXC 6 0

"T32106.01"

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.2.3.3 IEIF

netmask (IP Network Mask)


Full name Netmask IP Network Mask

Description Specif ies the size of the LMP subnet, that ishow many hosts on the LMP are possible.The value is an IP address with all thenetwork bits set to 1 and all the host bits set

to 0. The Public IP Address in IP Node(IPNO) has to be configured first.

Network mask for the IP address of the BTSin the transport network. To be entered indotted decimal format.

Interfaces Planner <-> RNC, EM <-> RNC AXC <-> RAC, AXC <-> EM, RAC <->RACApp

9.2.3.4 PWMP

perHopBehaviour (Per hop behaviour DiffServ)


Description Per hop behaviour (DiffServ). (The DSCP(DiffServ CodePoint) value is stored in thefirst 6 bits of the Type of Service (ToS) fieldthat is part of the standard IP header.) (Usedas key in the NE prio tables) Values are:expeditedForwarding,assuredForwardingClass4,assuredForwardingClass3,assuredForwardingClass2,assuredForwardingClass1, bestEffort

Per hop behaviour (DiffServ). This parameter is used to determine the DSCP value(Diff Serv Code Point) that must be stored in thefirst 6 bits of the 'Type of Service' (ToS) fieldthat is part of the standard IP header. Valuesare: expeditedForwarding,assuredForwardingClass4,assuredForwardingClass3,assuredForwardingClass2,assuredForwardingClass1, bestEffort

RAC DB Table C_AXC_PWMP

RAC DB Column PWMP_PER_HOP_BEHAVIOUR


30/09/2008

Changes in RU10



9.2.3.5 SRCK

supportingIfPtrIf (Reference pointer to the synchronization Interface)


Description Specifies interface location of an instance of the PDH or SDH/SONET transmissioninterface source to be used as asynchronization source. Values 1..8 are usedfor AXC Compact. Values 1..100 are used for Modular Embedded AXC. An IMA groupcannot be used as clock source, but thePPTT instance of IMA links can be

configured.

Specifies interface location of an instance of the PDH or SDH/SONET transmissioninterface source to be used as asynchronization source. Values -1, 1..8 areused for AXC Compact. Values -1, 1..100are used for Modular Embedded AXC. Value-1 (Not defined) is used for referencingTOPIK instance. An IMA group cannot be

used as clock source, but the PPTT instanceof IMA links can be configured.

Range 1...100 -1...100

Step 1 1

Unit

9.2.3.6 STPG

timingSourcePtrIf1 (Timing Generator 1 Interface)


Description Defines the interface location of PrimarySynchronization Source. It can be a PDHInterface, a SDH Interface or an externalClock connected to the AXUA, AXUB, AXCCor AXCD. Values -1 (not defined), 1...8 areused for AXC Compact. Values -1 (notdefined), 1...16, 100 are used for Modular Embedded AXC. timingSourcePtrIf1 isrelevant only when timingSourcePtrType1has value SRCK.

Specifies either the interface location on theunit (value range 1..16) or references aninstance of class TimeOverPacket (valuerange 33..). 33 maps to object "TOPIK-1", 34to object "TOPIK-2" etc. Values -1 (notdefined), 1...63, 100 timingSourcePtrIf1 isrelevant only when timingSourcePtrType1has value SRCK.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



timingSourcePtrIf2 (Timing Generator 2 Interface)


Description Defines interface location of SecondarySynchronization Source. It can be a PDHInterface, a SDH Interface or an externalClock connected to the AXUA, AXUB, AXCCor AXCD. Valid values: -1 (not defined),1...16, 100. timingSourcePtrIf2 is relevantonly when timingSourcePtrType2 has valueSRCK.

Specifies either the interface location on theunit (value range 1..16) or references aninstance of class TimeOverPacket (valuerange 33..). 33 maps to object "TOPIK-1", 34to object "TOPIK-2" etc. timingSourcePtrIf1 isrelevant only when timingSourcePtrType1has value SRCK. Valid values: -1 (notdefined), 1...63, 100. timingSourcePtrIf2 isrelevant only when timingSourcePtrType2has value SRCK.

9.2.4 Removed Parameters in AXC PE 5.5

9.2.4.1 ETHLK

. accFrameTypes (Accepted Frame Types)

. shapedBandwidth (Shaped Ethernet Bandwidth)

. vlanTags1 (VLAN Tag List 1)

9.2.4.2 PWTIP

. activeEthernetLink (Active Ethernet Link)

. ethLinkList1 (Ethernet Links List 1)



. localIpv4Addr (Local IPv4 Address)

.

vlanTagList1 (VLAN Tag List 1)


30/09/2008

Changes in RU10



9.3 Changes in Plan Editor Flexi Transport Module

Parameters

9.3.1 Introduction

The following sections describe the changes in parameters supported byNetAct Radio Access Configurator among Plan Editor Flexi TransportModule WBTS5.0 and WBTS4.0. The information is intended for thoseinvolved in network planning, implementation and roll-out, configurationmanagement, and engineering support.

For more information on parameters in Plan Editor Flexi Transport ModuleParameters, see Plan Editor Flexi Transport Module Parameters .

9.3.2 New Parameters in WBTS5.0

9.3.2.1 FTM_A2UT


queue2Weight (Weight of AAL2 user path queue Q2)

This is the weight of AAL2 User Path queueQ2.





9.3.2.2 FTM_BFD


bfdActivation (BidirectionalForwarding Detection Activation Flag)

This flag indicates if Bidirectional ForwardingDetection is activated.

bfdAdminUp (BFD actualsession administrationflag)

This parameter is used to switch on or off the actual BFD session. Only if theparameter has value true, BFD alarms willbe propagated. Note that this parameter isonly relevant if parameter bfdActivation hasvalue true.

bfdDestAddress(Bidirectional ForwardingDetection Destination

Address)

This is the IP address to be used inBidirectional Forwarding Detection. To beentered in dotted decimal format.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




bfdId (BidirectionalForwarding DetectionNaming Attribute)

This is the naming attribute of the uniqueBidirectional Forwarding Detection objectinstance of the BTS. Value is always 1.

9.3.2.3 FTM_CCFA


vccBundleEnabled (VCCBundle Enabling Flag)

This parameter enables VCC bundling for collecting extra bandwidth unused byneighbour VCCs.

9.3.2.4 FTM_CERTH


certhId (CertificationHandler Id)

Naming Attribute. This parameter identifiesthe unique instance of the certificationhandler object class of the BTS. Value isalways 1.

cmpServerIpAddress

(CMP Server IP Address)

This is the IP address of the CMP server.

Format = dotted decimal.cmpServerPort (CMPServer Port)

This is the port number to be used for addressing the Certificate ManagementProtocol server.

crServerIpAddress (CRServer IP Address)

Address of the CR Server in dotted decimalformat.

crServerPort (CR Server Port)

This is the port number to be used for addressing the CR server in certificatemanagement.

9.3.2.5 FTM_FRLI


interfaceNumber (InterfaceIdentifier)

Defines the location on the unit of the PDHinterface that is used for fractional mode.

maxTimeslot (Max TS) Specifies the last consequtive timeslot that isto be used for an ATM interface. At least twotimeslots must be used.


30/09/2008

Changes in RU10




unitNumber (Unit Number) This parameter identifies the slot number of the unit of the PDH interface that is used for fractional mode. The value is always 1 (only1 slot available in this release).

9.3.2.6 FTM_IEIF


ieifId (IEIF Identifier) IEIF Identifier

activeEthernetLink (ActiveEthernet Link) Active Ethernet Link. E.g. for pseudowire theethernet link which actually carries thetunnel. The activeEthernetLink has tosupport the vlan Tag defined by vlanId.

localIpAddr (Local Addressof the IP Interface)

IP address of the BTS in the transportnetwork. It is accompanied with a subnetmask.

mtu (Maximum Transfer Unit)

Specifies the Maximum Transfer Unit of theinterface in octets.

netmask (IP NetworkMask)

Network mask for the IP address of the BTSin the transport network. To be entered indotted decimal format.

shapedBandwidth (ShapedBandwidth)

The egress shaping bandwidth on thenetwork interface shall be configurable inkpbs. Value range is from 1000 (1 MBit/s) to1000000 (1GBit/s) with step 500.

upperLayerShaping (Upper Layer Shaping EnabledFlag)

This parameter decides if shaping takes theethernet overhead into account whenshaping the bandwidth or not. If the flag hasvalue true, the associated shapedBandwidthis the bandwidth on the IP layer only. If theflag has value false the Ethernet header iscounted also. Use "true" for an IP onlynetwork, e.g. xDSL, use "false" for anEthernet network, e.g. Metro Ethernet.

vlanEnabled (VlanEnabled flag)

This flag indicates if Vlan mapping isenabled for this ethernet interface. Value"true" means that Vlan mapping is enabled.In case Vlan mapping is not enabled, allmessages on the interface will be sent inplain format.

vlanId (Vlan ID) Vlan ID to be used over this ethernetinterface. The parameter is only relevant if vlan mapping is enabled (parameter vlanEnabled has value true).

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.3.2.7 FTM_IPNO


omsTls (TLS usagetowards NEMU/OMS)

Defines the usage of TLS between BTS andNEMU/OMS. The usage of TLS requires thatvalid certificates are installed to the BTS.

transportMode(transportMode)

This parameter selects between the transportmodes AtmOverEthernet, Dual Iub and Iub/ IP.

9.3.2.8 FTM_PWMP


bfdAdminUp (BFD actualsession administrationflag)

This parameter is used to switch on or off the actual BFD session. Note that thisparameter is only relevant if parameter bfdEnable has value true.

9.3.2.9 FTM_QOS


assuredForwardingClass1(Assured Forwarding Class1 Weight Value)

This is the weight value of the traffic queueassociated to the Per Hop Behaviour

Assured Forwarding Class 1 (AF1).







assuredForwardingClass4

(Assured Forwarding Class4 Weight Value)

This is the weight value of the traffic queue

associated to the Per Hop Behaviour Assured Forwarding Class 4 (AF4).

bestEffort (Best EffortWeight Value)

This is the weight value of the traffic queueassociated to the Per Hop Behaviour BestEffort (BE).

qosId (QOS class namingidentifier)

This parameter identifies the unique instanceof the QOS class of the BTS. Value always1.


30/09/2008

Changes in RU10



9.3.2.10 FTM_QOS_TRAFFICTYPE


dscpList (dscpList) This is the list of DSCP codes that relate toa specific traffic category. The list is acomma-seperated value list. The values areDSCP decimal values. The list can containup to 64 entries.

pHB (Per Hop Behaviour) This parameter designates a Per HopBehaviour. The following values arepredefined: 0 = EF (meaning: ExpeditedForwarding) 1 = AF4 (Assured Forwarding 4)2 = AF3 (Assured Forwarding 3) 3 = AF2

(Assured Forwarding 2) 4 = AF1 (AssuredForwarding 1) 5 = BE (Best Effort).

trafficType (Traffic Type) This parameter designates a traffic type.Values for transport mode AtmOEth: "TOP""SG1" - Pseudowire (PW) for perHopBehaviour (pHB) EF "SG2" - PW for pHB AF4 "SG3" - PW for pHB AF3 "SG4" -PW for pHB AF2 "SG5" - PW for pHB AF1"SG6" - PW for pHB BE "ICMP" Values for transport mode DualIub: "BFD" "TOP" "SG1"- Signalled traffic for pHB EF "SG2" -Signalled traffic for pHB AF4 "SG3" -Signalled traffic for pHB AF3 "SG4" -Signalled traffic for pHB AF2 "SG5" -Signalled traffic for pHB AF1 "SG6" -Signalled traffic for pHB BE "ICMP" Valuesfor transport mode IubIP: "DCN" "NBAP""BFD" "TOP" "SG1" - Signalled traffic for pHB EF "SG2" - Signalled traffic for pHB

AF4 "SG3" - Signalled traffic for pHB AF3"SG4" - Signalled traffic for pHB AF2 "SG5" -Signalled traffic for pHB AF1 "SG6" -Signalled traffic for pHB BE "ICMP"

vlanPrio (Vlan priority flag) This is the vlan priority to be used on allconnections for a given Per Hop Behaviour.

9.3.2.11 FTM_TMPAR


cacCommittedBitRate(CAC Committed Bit Rate)

Connection Admission Control Committed BitRate. Used in Dual Iub and Iub/IP transportmodes.

dcnCommittedBitRate(DCN Committed Bit Rate)

DCN Committed Bit Rate. Used in transportmode Iub/IP.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




externalNATIpAddress(External NAT IP Address)

This is the IP address to be used inaddressing the external NAT device.

farEndSctpSubnetIpAddress (Far End SCTP SubnetIP Address )

This is the IP address to be used in thetransport network at the far end of the SCTPtunnel. The address is the SCTP tunnelsubnet address, i.e all its host bits must beset to 0s. It must be entered in dotteddecimal format. The parameter is used inIub/IP transport mode. The associatedsubnet mask is defined in parameter farEndSctpSubnetMask.

farEndSctpSubnetMask

(Far End SCTP SubnetMask)

This is the subnet mask for the far end

SCTP tunnel subnet IP address (parameter farEndSctpSubnetIpAddress). To be enteredin dotted decimal format.

minSCTPPort (MinimumSCTP port number)

This is is the minimum value of the portnumber to be used for SCTP. Used intransport mode Iub/IP.

minUDPPort (MinimumUDP port number)

This is is the minimum value of the portnumber to be used over UDP connections.

signallingCommittedBitRate (Signalling CommittedBit Rate)

Signalling Committed Bit Rate. Used intransport mode Iub/IP.

tmparId (TMPAR ObjectInstance Identifier)

This parameter identifies the unique objectinstance of the TMPAR clas. Value is always1.

9.3.2.12 FTM_TOPIK


administrativeState(Administrative State)

Used to lock and unlock the TOP objectinstance. Locking the object deactivates itand supresses all its alarms.

logMeanSyncValue (Logmean synchronizationvalue)

This indicates how often a ToP syncmessage shall be send by the ToP master within the transmission duration requestperiod. (The transmission duration requestperiod is currently fixed to 300 seconds.) Thefollowing values are defined: -3: 8 per second -4: 16 per second -5: 32 per second

masterClockState (Master clock state)

This parameter holds the state of theTimeOverPacket master clock. It is a read-only parameter.

masterIpAddr (IP Addressof the ToP master)

IP address of the ToP master. To be enteredin dotted format.


30/09/2008

Changes in RU10




topId (Identifier of the ToPinstance)

This parameter uniquely defines the instanceof the ToP class. Always 1.

9.3.3 Changed parameters in WBTS5.0

9.3.3.1 FTM

Version (Software Release Version)

Field FTM_PE WN4.0 FTM_PE WN5.0

Default value WN3.2 WN5.0

9.3.3.2 FTM_A2ST

interfaceNumber (Interface Number)


Description Defines the interface location on the unit.

The number of interfaces depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTFA: 1..16 For IMA, possible IMAGIdentifiers: 33..75 ATM over EthernetPseudowire: 76

Defines the interface location on the unit.

The number of interfaces depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTIB: 1..4 FTFA: 1..16 FTHA: 1..16 FTJA:1..4 In case of Inverse Multiplexing for ATM(IMA), the following IMAG Identifier arepossible: 33..75; ATM over EthernetPseudowire takes the number 76

Modification onLine unmodifiable

Interfaces FTM -> EM FTM -> EM, FTM -> RAC

9.3.3.3 FTM_A2UT

a2utInterfaceNumber (A2UT Interface Number)


Description Defines the A2UT interface location on theunit. The number of interfaces depends onthe unit type. FTEB: 1..8 FTPB: 1..8 FTIA:1..4 FTFA: 1..16 In case of InverseMultiplexing for ATM (IMA), the followingIMAG Identifier are possible: 33..75 In caseof ATMoEthernet, it is always 76.

Identifies the physical interface on the unit.The range depends on the unit type. FTEB,FTPB: 1..8 FTIA, FTIB, FTJA: 1..4 FTFA,FTHA: 1..16 In case of Inverse Multiplexingfor ATM (IMA), the following values arepossible: 33..75. In case of ATMoEthernet, itis always 76.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.3.3.4 FTM_ACCP

egressBandwidth (Egress Bandwidth)


Description Defines the maximum allowed egressbandwidth in cells per second for a logical

ATM interface. For the following interfacesthe values are fixed: - E1: 4528 - STM-1:72452(16 x E1) - T1/JT1: 3622 - IMA E1: int[n*4526*(m-1)/m] where m = Tx Frame

Length and n = number of IMA links in agroup - IMA T1/JT1: int[n*3621*(m-1)/m]where m = Tx Frame Length and n = number of IMA links in a group For ATM over Ethernet (Pseudowire tunnel) the value isoperator configurable from 1132 to 72448 insteps of 1132.

Defines the maximum allowed egressbandwidth in cells per second for a logical

ATM interface. The value range of egressBandwidth is as follows: - E1: fixedvalue 4528 - T1/JT1: fixed value 3622 -STM-1: 36..144896, step 1, default 144896

(32 x E1) - ATM over Ethernet (pseudowire):1132..144896, step 1132, default 144896. -IMA E1: fixed value: int[n*4526*(m-1)/m]where m = Tx Frame Length and n =number of IMA links in a group - IMA T1/JT1fixed value: int[n*3621*(m-1)/m] where m =Tx Frame Length and n = number of IMAlinks in a group

Range 1132...72448 36...144896

Step 1132 1

Unit cells/s cells/s

Default value 72448 144896

Default value notes The default value refers only to ATM over Ethernet, because this is the only casewhere the parameter is settable. For theother cases always the values from the"description" apply.

The range and step and the default valuerefer only to ATM over Ethernet, becausethis is the only case where the parameter isconfigurable. For the other cases always thevalues from the "description" apply.

RAC DB Table C_FTM_ACCP

RAC DB Column ACCP_EGR_B_N_WIDTH


30/09/2008

Changes in RU10



ingressBandwidth (Ingress Bandwidth)


Description Defines the maximum allowed ingressbandwidth in cells per second for a logical

ATM interface. For the following interfacesthe values are fixed: - E1: 4528 - STM-1:72452(16 x E1) - T1/JT1: 3622 - IMA E1: int[n*4526*(m-1)/m] where m = Tx FrameLength and n = number of IMA links in agroup - IMA T1/JT1: int[n*3621*(m-1)/m]where m = Tx Frame Length and n = number of IMA links in a group For ATM over

Ethernet (Pseudowire tunnel) the value isoperator configurable from 1132 to 72448 insteps of 1132.

Defines the maximum allowed ingressbandwidth in cells per second for a logical

ATM interface. For the following interfacesthe values are fixed: - E1: 4528 - STM-1:144896 (32 x E1) - T1/JT1: 3622 - IMA E1:int[n*4526*(m-1)/m] where m = Tx FrameLength and n = number of IMA links in agroup - IMA T1/JT1: int[n*3621*(m-1)/m]where m = Tx Frame Length and n =number of IMA links in a group For ATM

over Ethernet (Pseudowire tunnel) the valueis operator configurable from 1132 to 144896in steps of 1132.

Range 1132...72448 1132...144896

Step 1132 1132

Unit cells/s cells/s

Default value 72448 144896

Default value notes The default value refers only to ATM over Ethernet, because this is the only casewhere the parameter is settable. For theother cases always the values from the

"description" apply.

Range and step and default value refer onlyto ATM over Ethernet, because this is theonly case where the parameter isconfigurable. For the other cases always the

values from the "description" apply.

RAC DB Table C_FTM_ACCP

RAC DB Column ACCP_ING_B_N_WIDTH

9.3.3.5 FTM_ANBA

interfaceNumber (Interface Identifier)


Full name Interface Number Interface Identifier

Description Defines the interface location on the unit.The number of interfaces depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTFA: 1..16 In case of Inverse Multiplexingfor ATM (IMA), the following IMAG Identifier are possible: 33..75. For ATM over Ethernetthe value 76 is used.

Defines the interface location on the unit.The value depends on the unit type. FTEB:1..8 FTPB: 1..8 FTIA: 1..4 FTIB: 1..4 FTFA:1..16 FTHA: 1..16 In case of InverseMultiplexing for ATM (IMA), the followingvalues are possible: 33..75; for ATM over Ethernet the value 76 is used.



DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.3.3.6 FTM_ETHLK

speedAndDuplex (Speed and Duplex flag)


Description This parameter specificies if linkcharacteristics are autonegotiated or not. If no, the attribute contains the capacity andthe duplex mode to be set forcibly. Note that100 MBit is available only on Fast Ethernetinterfaces (FE) and 1000 MBit only on theGigabit Ethernet interface (GE).

This parameter specificies if linkcharacteristics are autonegotiated or not. If not, the attribute contains the capacity andthe duplex mode to be set forcibly. Note that1000 MBit is available only on GigabitEthernet interfaces (GE).

Range 0 (AUTODETECT), 1 (1000MBIT_FULL), 2(100MBIT_FULL)

0 (AUTODETECT), 1 (1000MBIT_FULL), 2(100MBIT_FULL), 3 (10MBIT_FULL)

Step

Unit

Formula for getting internalvalue

internal_value = AUTODETECT ==> 0,1000MBIT_FULL ==> 1, 100MBIT_FULL ==>2

internal_value = AUTODETECT ==> 0,1000MBIT_FULL ==> 1, 100MBIT_FULL ==>2, 10MBIT_FULL ==> 3

Modification onLine

Interfaces FTM <-> EM, FTM <-> RAC, RACApp <->RAC

9.3.3.7 FTM_IAIF



Description Identif ies the interface on the unit. Thenumber of interfaces depends on the unittype. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4 FTFA:1..16 In case of Inverse Multiplexing for ATM(IMA), the values 33..75 are possible. For

ATM over Ethernet the value is 76

Defines the interface location on the unit.The number of interfaces depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTIB: 1..4 FTFA: 1..16 FTHA: 1..16 FTJA:1..4 In case of Inverse Multiplexing for ATM

(IMA), the following IMAG Identifier arepossible: 33..75; ATM over EthernetPseudowire takes the number 76

RAC DB Table C_FTM_IAIF

RAC DB Column IAIF_IF_NBR


30/09/2008

Changes in RU10



9.3.3.8 FTM_IHCP

dhcpAccessId (DHCP Server Identifier)


Description Identifies the DHCP Server in the FTM.Since the FTM contains only one DHCPserver, the identifier is always 1.

This parameter identifies the unique DHCPServer object in the BTS. Value is always 1.

Default value notes Always 1.


Interfaces FTM -> EM FTM <-> EM, FTM <-> RAC, RAC <->

RACAppRAC Planning interfacename

$instance

9.3.3.9 FTM_IHCP_CLIENT

dhcpClientIdentifier (DHCP Client Identifier)


Description Specifies a unique string used in the DHCPserver (FTM) to assign a specified IPaddress to a DHCP client that requests alease and is identified by this client-identifier label.

This is a unique string used in the DHCPserver of the BTS for identifying a DHCPclient that is assigned a fixed IP address.This may either be one of the predefinednames "RET1" (Remote Electrical Tilt),"RET2", "BBU" and "LMU" or a user-definedname consisting of up to 20 digits [0-9] andlower-case letters [a-z].

Default value notes In AXC Manager the following clientidentifers are predefined:OAMMASTERWAM, RET1 (RemoteElectrical Tilt), RET2, BBU (Battery BackupUnit), LMU (Location Measurement Unit)

Related parameters dhcpConfigurationInfoIdentifier of IHCP

Parameter relationships DHCP Configuration Information Identifier must be client_identifier.

Interfaces FTM <-> EM FTM <-> EM, FTM <-> RAC, RAC <->RACApp

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



dhcpFixedIpAddress (DHCP Fixed IP Address)


Description Specif ies a fixed IP address to be assignedto the DHCP client if it requests a lease withthe specified client-identifier. The IP addressmust be within the public IP subnet of theLMP. However, neither the IP addresses of the FTM and the subnet IP address can beused.

Specifies a fixed IP address to be assignedto the DHCP client if it requests a lease withthe specified client-identifier. The IP addressmust be within the public IP subnet of theLMP. However, neither the IP addresses of the BTS nor its subnet IP address can beused.


Parameter relationships DHCP Configuration Information Identifier

must be client_identifier. The IP addressmust be within the public IP subnet of theLMP. However, neither the IP addresses of the FTM and the subnet IP address can beused.


9.3.3.10 FTM_IHCP_HW

dhcpFixedIpAddress (DHCP Fixed IP Address)


Description Specif ies a fixed IP address to be assignedto the DHCP client if it requests a lease withthe specified hardware (MAC) address. TheIP address must be within the public IPsubnet of the LMP. However, neither the IPaddresses of the AXC and the subnet nor the broadcast IP address can be used.

Specifies the fixed IP address to beassigned to the DHCP client if it requests alease with the hardware (MAC) addressspecified in parameter "DHCP HardwareIdentifier". The IP address must be within thepublic IP subnet of the LMP. However, the IPaddresses of the BTS, its subnet IP addressand its broadcast IP address cannot beused.

Related parameters dhcpConfigurationInfoIdentifier of IHCPParameter relationships DHCP Configuration Information Identifier

must be hardware_identifier. The IP addressmust be within the public IP subnet of theLMP. However, neither the IP addresses of the AXC and the subnet nor the broadcast IPaddress can be used.

Interfaces RAC -> AXC, EM -> AXC, RAC <-> RACApp FTM <-> RAC, FTM <-> EM, RAC <->RACApp

RAC DB Table C_IHCP_HARDWARE_ID_LIST

RAC DB Column HI_DHCP_FIXED_IP_ADDRESS


30/09/2008

Changes in RU10



dhcpHardwareIdentifier (DHCP Hardware Identifier)


Description Specifies a unique hardware (MAC) addressused in the DHCP server (FTM) to assign aspecified IP address to a DHCP client thatrequests a lease and is identified by thishardware address.

This is the unique hardware (MAC) addresswithin the DHCP server of the BTS by whicha DHCP client identifies itself at the BTS.The server will then assign the IP address of parameter "DHCP Fixed IP Address" to theclient.


Parameter relationships DHCP Configuration Information Identifier must be hardware_identifier.


9.3.3.11 FTM_IHCP_RANGE

dhcpRangeEnd (DHCP Range End IP Address)


Description Specifies the ending IP address of the DHCPrange (pool). The IP address must be withinthe public IP subnet of the LMP. However,neither the IP addresses of the FTM and thesubnet IP address can be used.

Specifies the final IP address of the DHCPIP address range. The IP address must bewithin the public IP subnet of the LMP.However, neither the IP addresses of theBTS nor its subnet IP address shall be used.


Parameter relationships DHCP Configuration Information Identifier must be range_identifier. The IP addressmust be within the public IP subnet of theLMP. However, neither the IP addresses of the FTM and the subnet IP address can beused.


DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



dhcpRangeStart (DHCP Range Start IP Address)


Description Specif ies the starting IP address of theDHCP range (pool). The IP address must bewithin the public IP subnet of the LMP.However, neither the IP addresses of theFTM and the subnet IP address can beused.

Specifies the starting IP address of theDHCP IP address range. The IP addressmust be within the public IP subnet of theLMP. However, neither the IP addresses of the BTS nor its subnet IP address shall beused.

Range 7...15 0...15

Step

Unit characters characters


Parameter relationships DHCP Configuration Information Identifier must be range_identifier. The IP addressmust be within the public IP subnet of theLMP. However, neither the IP addresses of the FTM and the subnet IP address can beused.


9.3.3.12 FTM_IPRM_EX

sourceOne (Source One Identifier)


Range 0 (BTS), 1 (TRS), 2 (LMP) 2 (LMP)

Step

Unit

Formula for getting internal

value

internal_value = BTS ==> 0, TRS ==> 1,

LMP ==> 2

internal_value = LMP ==> 2

RAC DB Column RE_SRC_ONE


30/09/2008

Changes in RU10



sourceTwoDiscr (How is source two defined?)


Description With this parameter the user can select theway how to define source two. Possiblevalues are: ALIAS: reference to an IP sourcealready configured in the system for other contexts SINGLE: a single IP addressRANGE: a range of IP addresses given byan IP address and a subnet maskWILDCARD: any IP adress is allowed

With this parameter the user can select theway how to define source two. Possiblevalues are: SINGLE: a single IP addressRANGE: a range of IP addresses given byan IP address and a subnet maskWILDCARD: any IP adress is allowed

Range 0 (ALIAS), 1 (SINGLE), 2 (RANGE), 3(WILDCARD)

1 (SINGLE), 2 (RANGE), 3 (WILDCARD)

Step

Unit


internal_value = ALIAS ==> 0, SINGLE ==>1, RANGE ==> 2, WILDCARD ==> 3

internal_value = SINGLE ==> 1, RANGE==> 2, WILDCARD ==> 3

RAC DB Column RE_SRC_TWO_DISCR

sourceTwoIpAddr (IP address for source two)


Description This parameter is meaningful if and only if source two is defined as SINGLE or asRANGE; in all other cases it is ignored. "IPaddress source two" specifies a single IPaddress; if source two is defined as SINGLE,this is the only allowed IP address. If sourcetwo is defined as RANGE, then the allowedrange of IP addresses is obtained byapplying the "IP subnet mask for source two"to this IP address. The IP address must begiven as "dotted decimal" string.

This parameter is meaningful if and only if source two is defined as SINGLE or asRANGE; in all other cases it is ignored. "IPaddress source two" specifies a single IPaddress. If source two is defined as SINGLE,this is the only allowed IP address. If sourcetwo is defined as RANGE, then the allowedrange of IP addresses is obtained byapplying the "IP subnet mask for source two"to this IP address. The IP address must begiven as "dotted decimal" string.

Related parameters sourceTwoDiscr of IPRMParameter relationships sourceTwoIpAddr is only relevant if

parameter sourceTwoDiscr has valueSINGLE or RANGE.

RAC DB Column RE_SRC_TWO_IP_ADDR

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




RAC Planning interfacename

$instance

9.3.3.14 FTM_PPTT



Description Defines the interface location on the unit.The number of interfaces depends on the

unit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTFA: 1..8

Defines the interface location on the unit.The number of interfaces depends on the

unit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTIB: 1..4 FTFA: 1..16 FTHA: 1..16 FTJA:1..4

Range 1...8 1...16

Step 1 1

Unit



pdhLineType (PDH Line Type)


Description Specifies the frame format of the PDH signalfor a physical PDH interface of a unit. E1(G.704): DOUBLEFRAME or MULTIFRAMEJT1: EXTENDED_MULTIFRAME T1:SUPERFRAME or EXTENDED_SUPERFRAME

Specifies the frame format of the PDH signalfor a physical PDH interface of a unit. E1(G.704): DOUBLEFRAME or MULTIFRAMEor DOUBLEFRAME UNBALANCED or MULTIFRAME UNBALANCED JT1:EXTENDED_MULTIFRAME T1:SUPERFRAME or EXTENDED_SUPERFRAME

Range 1(PDH_LINE_TYPE_DOUBLE_FRAME_ G704), 2(PDH_LINE_TYPE_MULTI_FRAME_G704),8(PDH_LINE_TYPE_EXTENDED_MULTIFRAME), 10 (PDH_LINE_TYPE_SUPERFRAME),11(PDH_LINE_TYPE_EXTENDED_SUPERFR

AME)

1(PDH_LINE_TYPE_DOUBLE_FRAME_ G704), 2(PDH_LINE_TYPE_MULTI_FRAME_G704),8(PDH_LINE_TYPE_EXTENDED_MULTIFRAME), 10(PDH_LINE_TYPE_SUPERFRAME), 11(PDH_LINE_TYPE_EXTENDED_SUPERFR

AME), 12(PDH_LINE_TYPE_DOUBLE_FRAME_ G704_UNBALANCED), 13(PDH_LINE_TYPE_MULTI_FRAME_G704_U

NBALANCED)

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




Step

Unit

Default value notes PDH_LINE_TYPE_DOUBLE_FRAME_G704(E1 | AXCC/AXCD/IFUA/IFUD)PDH_LINE_TYPE_MULTI_FRAME_G704(for E1 default | default on AXCC/AXCD/ IFUA/IFUD/IFUE)PDH_LINE_TYPE_EXTENDED_MULTIFRAME (for JT1 default | AXCC/IFUA)PDH_LINE_TYPE _SUPERFRAME (T1 |

AXCC/IFUA) PDH_LINE_TYPE _EXTENDED_SUPERFRAME (for T1 default

| AXCC/IFUA)

Defaults depend on E1/T1/JT1: E1:PDH_LINE_TYPE_MULTI_FRAME_G704T1:PDH_LINE_TYPE_EXTENDED_SUPERFRAME JT1:PDH_LINE_TYPE_EXTENDED_MULTIFRAME


internal_value =PDH_LINE_TYPE_DOUBLE_FRAME_G704==> 1,PDH_LINE_TYPE_MULTI_FRAME_G704==> 2,PDH_LINE_TYPE_EXTENDED_MULTIFRAME ==> 8, PDH_LINE_TYPE_SUPERFRAME==> 10,PDH_LINE_TYPE_EXTENDED_SUPERFRAME ==> 11

internal_value =PDH_LINE_TYPE_DOUBLE_FRAME_G704==> 1,PDH_LINE_TYPE_MULTI_FRAME_G704==> 2,PDH_LINE_TYPE_EXTENDED_MULTIFRAME ==> 8,PDH_LINE_TYPE_SUPERFRAME ==> 10,PDH_LINE_TYPE_EXTENDED_SUPERFRAME ==> 11,PDH_LINE_TYPE_DOUBLE_FRAME_ G704_UNBALANCED ==> 12,

PDH_LINE_TYPE_MULTI_FRAME_G704_UNBALANCED ==> 13

Interfaces AXC <-> RAC, AXC <-> EM, RAC <->RACApp

FTM <-> RAC, FTM <-> EM, RAC <->RACApp

RAC DB Table C_PPTT

RAC DB Column PPTT_PDH_LINE_TYPE

9.3.3.15 FTM_PWMP

perHopBehaviour (Per hop behaviour DiffServ)


Description Per hop behaviour (DiffServ). The DSCP(DiffServ CodePoint) value is stored in thefirst 6 bits of the Type of Service (ToS) fieldthat is part of the standard IP header (usedas key in the NE prio tables)

Per hop behaviour (DiffServ). This parameter is used to determine the DSCP value(Diff Serv Code Point) that must be stored in thefirst 6 bits of the 'Type of Service' (ToS) fieldthat is part of the standard IP header. TheDSCP for the given perHopBehaviour isconfigured in the trafficTypesMap of the QOSobject.

Related parameters trafficTypesMap of QOS


30/09/2008

Changes in RU10




Parameter relationships perHopBehaviour is used as a searchcriterium in the trafficTypesMap to find thecorresponding DSCP value.

RAC DB Table C_FTM_PWMP

RAC DB Column PWMP_PER_HOP_BEHAVIOUR

9.3.3.16 FTM_STPG

synchroSource1InterfaceNumber1 (Interface Number 1)


Description Specifies the interface location on the unit of the primary synchronization source. Values -1 (Not defined), 1..16.

Specifies either the interface location on theunit (value range 1..16) of the primarysynchronization source or references aninstance of class TimeOverPacket (valuerange 33..). 33 maps to object "TOPIK-1", 34to object "TOPIK-2" etc. Values -1 (Notdefined), 0..63.

Range -1...16 -1...63

Step 1 1

Unit

synchroSource2InterfaceNumber1 (Interface Number 2)


Description Specifies the interface location on the unit of the secondary synchronization source. TheFTM switches to the secondarysynchronization source in case the primarysynchronization source fails. Values -1 (Not

defined), 1..16.

Specifies either the interface location on theunit (value range 1..16) of the secondarysynchronization source or references aninstance of class TimeOverPacket (valuerange 33..). 33 maps to object "TOPIK-1", 34

to object "TOPIK-2" etc. Values -1 (Notdefined), 0..63.

Range -1...16 -1...63

Step 1 1

Unit

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.3.3.17 FTM_TCTT

interfaceNumber (Interface number)


Full name Interface Number Interface number

Description Identif ies the interface on the unit. Thephysical interfaces the range depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTFA: 1..16 In case of Inverse Multiplexingfor ATM (IMA), the IMAG Identifier (in therange 33..75) is used. For Pseudowires(ATMoE), it is always 76

Identifies the physical interface on the unit.The value range depends on the unit type.FTEB: 1..8 FTPB: 1..8 FTIA: 1..4 FTIA: 1..4FTJA: 1..4 FTFA: 1..16 FTHA: 1..16 In caseof Inverse Multiplexing for ATM (IMA), theIMAG identifier is used. Range is: 33..75. For Pseudowires (ATMoE), the value is always:76

RAC DB Table C_FTM_TCTT

RAC DB Column TCTT_IF_NBR

9.3.3.18 FTM_UNIT

unitTypeActual (Actual Unit Type)


Description Returns the unit type actually installed.FTPB: 470137A FTEB: 470156A FTFA:470134A FTIA: 471025A FTOA: 470133AFTJA: 471248A FTHA: 471522A

Returns the unit type actually installed unit.FTPB: 470137A FTEB: 470156A FTFA:470134A FTHA: 471522A FTIA: 471025AFTIB: 471720A FTOA: 470133A FTJA:471248A

Modification unmodifiable onLine

Interfaces FTM -> EM, FTM -> RAC FTM -> EM

RAC DB Table C_FTM_UNIT

RAC DB Column UNIT_UNIT_TYPE_ACTUAL


30/09/2008

Changes in RU10



9.3.3.19 FTM_VCCT



Description Defines the physical interface location on theunit. The number of interfaces depends onthe unit type. FTEB: 1..8 FTPB: 1..8 FTIA:1..4 FTFA: 1..16 In case of InverseMultiplexing for ATM (IMA) the values rangeis: 33..75. For ATM over Ethernet the value76 is used.

Defines the physical interface location on theunit. The number of interfaces depends onthe unit type. FTEB: 1..8 FTPB: 1..8 FTIA:1..4 FTIB: 1..4 FTJA: 1..4 FTFA: 1..16 FTHA:1..16 In case of Inverse Multiplexing for ATM(IMA), the following values are possible:33..75; for ATM over Ethernet the value 76 isused

RAC DB Table C_FTM_VCCT

RAC DB Column VCCT_IF_NBR

9.3.3.20 FTM_VCTT



Description Defines the location of the pyhsical interface

on the unit. The value range depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTFA: 1..16 In case of Inverse Multiplexingfor ATM (IMA), the value range is: 33..75.For ATM over Ethernet, the value is always:76.

Defines the location of the pyhsical interface

on the unit. The value range depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTIB: 1..4 FTJA: 1..4 FTFA: 1..16 FTHA:1..16 In case of Inverse Multiplexing for ATM(IMA), the value range is: 33..75. For ATMover Ethernet, the value is always: 76.

RAC DB Table C_FTM_VCTT

RAC DB Column VCTT_IF_NBR

9.3.3.21 FTM_VPCT



Description Defines the interface location on the unit.The number of interfaces depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTFA: 1..16 In case of Inverse Multiplexingfor ATM (IMA), the following values arepossible: 33..75 For ATM over Ethernet, thevalue is 76

Defines the location of the physical interfaceon the unit. The value range depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4FTIB: 1..4 FTJA: 1..4 FTFA: 1..16 FTHA:1..16 In case of Inverse Multiplexing for ATM(IMA) the value range is: 33..75. For ATMover Ethernet, the value is always: 76.

RAC DB Table C_FTM_VPCT

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




RAC DB Column VPCT_IF_NBR

9.3.3.22 FTM_VPTT



Description Defines the interface location on the unit.The number of interfaces depends on theunit type. FTEB: 1..8 FTPB: 1..8 FTIA: 1..4

FTFA: 1..16 For Inverse Multiplexing for ATM(IMA), the following values are possible:33..75; for ATM over Ethernet, the value is76

Defines the location of the physical interfacelocation on the unit. The value rangedepends on the unit type. FTEB: 1..8 FTPB:

1..8 FTIA: 1..4 FTIB: 1..4 FTJA: 1..4 FTFA:1..16 FTHA: 1..16 For Inverse Multiplexingfor ATM (IMA) the value range is: 33..75. For

ATM over Ethernet, the value is always: 76.

RAC DB Table C_FTM_VPTT

RAC DB Column VPTT_IF_NBR

9.3.4 Removed Parameters in WBTS5.0

9.3.4.1 FTM_ETHLK

. accFrameTypes (Accepted Frame Types)

. shapedBandwidth (Shaped Ethernet Bandwidth)

. vlanTags1 (VLAN Tag List 1)

9.3.4.2 FTM_IPRM_EX

. sourceOnePorts (Ports associated to source one)

. sourceTwoAlias (Name reference for source two)

. sourceTwoPorts (Ports associated to source two)

9.3.4.3 FTM_PWNE

. psnAssuredForwardingClass1 (PSN Assured Forwarding Class 1)





30/09/2008

Changes in RU10



. psnBestEffort (PSN Best Effort)

. psnExpeditedForwarding (PSN Expedited Forwarding)

. vlanAssuredForwardingClass1 (VLAN Assured Forwarding Class 1)




. vlanBestEffort (VLAN Best Effort)

. vlanExpeditedForwarding (VLAN Expedited Forwarding)

9.3.4.4 FTM_PWTIP

. activeEthernetLink (Active Ethernet Link)




. localIpv4Addr (Local IPv4 Address)

. nextHopIpAddr (Next Hop IP Address)

. vlanTagList1 (VLAN Tag List 1)

9.4 Changes in Plan Editor Flexi WCDMA BTSParameters

9.4.1 Introduction

The following sections describe the changes in parameters supported byNetAct Radio Access Configurator among Plan Editor Flexi WCDMA BTSWBTS5.0 and WBTS4.0 CD2. The information is intended for thoseinvolved in network planning, implementation and roll-out, configurationmanagement, and engineering support.

For more information on parameters in Plan Editor Flexi WCDMA BTSParameters, see Plan Editor Flexi WCDMA BTS Parameters .

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




9.4.2.1 ANTL


antennaRoundTripDelay(Antenna Round TripDelay)

The delay of the all passive units of antennaline can be entered into this parameter,which is then used as the RTT value insteadof calculating the value using the BTS SiteManager.

antennaTotalLoss(Antenna Total Loss)

This parameter contains the total losscalculated from the feederLoss and passive

units.antlId (Antenna Identifier) Identifies the specific antenna. The value is

given as FRx-ANTx, where FRx=1..3 and ANTx=1..6. For example, FR1-ANT1.

cableLength (CableLength)

Defines the antenna RF cable length inmeters. This parameter is used by BTS SiteManager to calculate antenna round tripdelay. The delay is 4.5 ns/m. The value for this parameter must be 0 if the RTT valuehas already been entered in theantennaRoundTripDelay parameter. TheantennaRoundTripDelay value is then usedinstead of letting the BTS Site Manager calculate the value based on, for example,cableLength.

feederLoss (Feeder Loss) Defines the feeder loss of the antenna cable.

feederVoltage (Feeder Voltage)

Defines the voltage level supplied to theantenna line. The values entered for thisparameter depend on the MHA type. PassiveMHAs: WMHA, WMHB: 12 WMHC, WMHD:BTS1 empty value (Manual voltage overrideis allowed: possible values [0 V / +12 V/ +28V (+28 only for Main branch)]), BTS2 12MDPA, MDTA, MDGA, MDDA: empty valueOther: 0 (User can change the line voltage to

12V or automatic. AISG MHAs: Currently for all AISG MHA empty string "" = "Automatic"value is used. Note: At NetAct and PlanEditor, the empty value is represented by -1.

velocityFactor (VelocityFactor)

The velocity factor is used to calculate RTTmore exactly. The velocity factor can beobtained from the specifications of the usedcable.


30/09/2008

Changes in RU10




btsscId (BTS SiteIdentification)

Defines specific Base Station site.

cabinetId (CabinetIdentification)

Defines the specific cabinet

cabinetType (CabinetType)

Defines the cabinet type. The allowed valueis: FlexiBTS: 17

commHList(Commissioning HistoryList)

Defines the Commissioning history for thespecific BTS.

btsManVer (BTS Manager Version)

Defines the version of the BTS Manager.

commType(Commissioning Type)

Defines the type of the commissioning.Expected values: Manual | Planned |Template | Reconfiguration | Upgrade

fileAuthor (File Author) Defines the name of the commissioningengineer.

fileCDate (File CreationDate)

Defines the date of the commissioning.Expected type of date: yyyy.mm.dd.

previousFileV (PreviousFile Version)

Defines the structure version of the SiteConfiguration File (SCF). For FlexiBTS, theallowed file versions start from 380.

ext2M048ClkInUse

(external 2.048MHzSynchronisation In Use)

Defines the usage of the external 2.048MHz

synchronisation reference.

extAlList (External AlarmInput Signal List)

The list defines the external alarm inputsignals.

descr (Description) Defines the external alarm description.

id (Line ID) Defines the external alarm lines. module,inUse, description, polarity and severity mustbe defined for input signals. There are 14input signals in FlexiBTS system module.Lines 13 and 14 are reserved for the FlexiPower Module and cannot be assigned to

other use. Values 1-14 are allowed. InWN5.0 and onwards input signals can bedefined also for some RF modules (in WN5.0only for RRH modules). The number of supported input lines in RF module aredefined in BTS Property File (in WN5.0maximum number is 2). Values 1-2 areallowed. Maximum total number of inputsignals is 16.

inUse (In Use) Defines is particular EAC line in use or not inuse.


30/09/2008

Changes in RU10




module (Module) Defines the module where EAC inputs arecommissioned. Allowed modules are FSM1,FR1, FR2 and FR3

polarity (Polarity) Defines the used polarity of the externalalarm line: normally open or normally closed.Normally_open: when the connector is open,there is no alarm. Normally_closed: when theconnector is closed, there is alarm.

severity (Severity) Defines the seriousness of the externalalarm condition in question. Minor = 1 Major = 2 Critical = 3

extCtrlList (External

Control Signal List)

The list defines the external alarm output

signals.


id (Line ID) Defines the external alarm lines. module,inUse, description and initialState must bedefined for Control Signals. There are 6output signals in FlexiBTS system module. Inthe future there can be output signals also inFlexiBTS RF modules (in WN5.0 RF modulecan have only input signals). Values 1-6 areallowed.

inUse (In Use) Defines is particular external control l ine inuse or not in use. For FSM multiplicity is 6.For FR multiplicity is 2.

initState (Initial State) Defines the initial state of the external controlline after a reset of the BTS. The options are"On" and "Off". If the initial state is "On",current is going through.

module (Module) Defines the module where EAC outputs arecommissioned. Allowed modules are FSM1,FR1, FR2 and FR3

externalAlarmInputSignalList (External Alarm InputSignal List)


description (Description) Defines the external alarm description.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




id (Line ID) Defines the external alarm lines. module,inUse, description, polarity and severity mustbe defined for input signals. There are 14input signals in FlexiBTS system module.Lines 13 and 14 are reserved for the FlexiPower Module and cannot be assigned toother use. Values 1-14 are allowed. InWN5.0 and onwards input signals can bedefined also for some RF modules (in WN5.0only for RRH modules). The number of supported input lines in RF module aredefined in BTS Property File (in WN5.0maximum number is 2). Values 1-2 areallowed. Maximum total number of inputsignals is 16.


module (Module) Defines the module where EAC inputs arecommissioned. Allowed modules are FSM1,FR1, FR2 and FR3



externalAlarmOutputSignalList (External Alarm OutputSignal List)

The list defines the external alarm outputsignals.


id (Line ID) Defines the external alarm lines. module,inUse, description and initialState must bedefined for Control Signals. There are 6output signals in FlexiBTS system module. In

the future there can be output signals also inFlexiBTS RF modules (in WN5.0 RF modulecan have only input signals). Values 1-6 areallowed.

inUse (In Use) Defines is particular external control l ine inuse or not in use. For FSM multiplicity is 6.For FR multiplicity is 2.

initialState (Initial State) Defines the initial state of the external controlline after a reset of the BTS. The options are"On" and "Off". If the initial state is "On",current is going through.


30/09/2008

Changes in RU10




module (Module) Defines the module where EAC outputs arecommissioned. Allowed modules are FSM1,FR1, FR2 and FR3




fileCrDate (File CreationDate)


gpsInUse (GPS In Use) Defines the usage of the GPS.

happyBitPingFiltUse(HSUPA Happy Bit -ratioping filtering)

Parameter is used to to define filtering for Happy Bit -ratio measurement. If filtering isactive, then Happy Bit -ratio counter is notupdated based on Happy bit preceding DTXframe/subframe. The target for filtering is tofilter out small data bursts (such as ping)from Happy Bit -ratio measurement as theydo not give reliable information of UEallocation.

happyBitPingFilterInUse(HSUPA Happy Bit -ratioping filtering)


happyBitUphThreshold(HSUPA Happy Bit -ratioUPH threshold)

Parameter defines threshold value for UEPower Headroom (UPH) values in Happy Bit-ratio measurement. Happy Bits that areassociated to UPH values that are below thedefined threshold, are not taken into accountin Happy Bit -ratio measurement. The targetfor filtering is to filter out power limitedsituation from Happy Bit -ratio measurement

as they do not give reliable information of UEallocation.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




hsdpaBbResAllocation(HSDPA BB Resource

Allocation)

Defines how HSDPA users are allocated.The options are Minimum Baseband (BTS),16 HSDPA users per cell (Cell) and Fullbaseband (Full). If the selected option isBTS, it is possible to set 1 - 3 HSDPA cells,each of them situated in the same FSP. Thetotal amount of the HSDPA users cannotexceed 16 in BTS. The HSDPA capacityrequirement is 32 channel elements fromFSP. If the selected option is Cell, it ispossible to set 1 - n HSDPA cells and eachHSDPA cell is situated in a different FSP.The total number of HSDPA users is notlimited, but the maximum amount of HSDPAusers in one cell (one FSP) is 16. TheHSDPA capacity requirement is 32 channelelements from FSP. If the selected option isFull, it is possible to set 1 - n HSDPA cellsand each HSDPA cell is situated in adifferent FSP. The total number of HSDPAusers is not limited, but the maximumamount of HSDPA users in one cell (oneFSP) is 64. The HSDPA capacityrequirement is 72 channel elements fromFSP.

hsdpaBbResourceAllocatio

n (HSDPA BB Resource Allocation)

Defines how HSDPA users are allocated.

The options are Full, BTS and Cell. If theselected option is BTS, it is possible to set 1- 3 HSDPA cells, each of them situated inthe same FSP. The total amount of theHSDPA users cannot exceed 16. TheHSDPA capacity requirement is 32 channelelements from FSP. If the selected option isCell, it is possible to set 1 - n HSDPA cellsand each HSDPA cell is situated in adifferent FSP. The total number of HSDPAusers is not limited, but the maximumamount of HSDPA users in one cell (oneFSP) is 16. The HSDPA capacityrequirement is 32 channel elements from

FSP.

intShutdownInUse(Intelligent Shutdown InUse)

Defines the usage of the IntelligentShutdown feature. If there are externalbatteries used this is "1" and intelligentshutdown timeout is filled in for local cells.

intelligentShutdownInUse(Intelligent Shutdown InUse)

Defines the usage of the IntelligentShutdown feature. If there are externalbatteries used this is "1" and intelligentshutdown timeout is filled in for local cells.

iubClkInUse (IubSynchronisation In Use)

Defines the usage of the Iub synchronisationreference.


30/09/2008

Changes in RU10




mainsPowerAlarmId(Mains Power Alarm ID)

Defines the starting external alarm line for the mains power alarm when the intelligentshutdown is in use. Default values: FlexiPower Module: 13 NSN BBU: 1 Other BBU:a value between 1-12 can be chosen

maxIubDelayThreshold(Maximum Iub DelayThreshold)

The maximum delay threshold after thesystem is interpreted to be in very severecongestion and propability to reduce creditsis 100%. Threshold defines the deviation of arrival interval from the TTI given to Iub.Note: Thmin < Thmid < Thmax

maximumIubDelayThreshol

d (Maximum Iub DelayThreshold)

The maximum delay threshold after the

system is interpreted to be in very severecongestion and propability to reduce creditsis 100%. Threshold defines the deviation of arrival interval from the TTI given to Iub.Note: Thmin < Thmid < Thmax

midIubDelayThreshold(Middle Iub DelayThreshold)

The middle delay threshold after the systemis interpreted to be in more severecongestion and MECN procedure is moreaggressive. Threshold defines the deviationof arrival interval from the TTI given to Iub.Note: Thmin < Thmid < Thmax

middleIubDelayThreshold(Middle Iub DelayThreshold)


minIubDelayThreshold(Minimum Iub DelayThreshold)

Defines the minimum delay threshold after the MECN procedure activates. Thresholddefines the deviation of arrival interval fromthe TTI given to Iub. Note: Thmin < Thmid <Thmax

minimumIubDelayThreshold (Minimum Iub DelayThreshold)

Defines the minimum delay threshold after the MECN procedure activates. Thresholddefines the deviation of arrival interval from

the TTI given to Iub. Note: Thmin < Thmid <Thmax

moduleList (Module List) The list defines the module and its locatione.g. place or address.

module (Module) Defines a one of the following Flexi modules:Module="FSM1" | Module ="FSM2" | Module="FR1" | Module ="FR2" | Module ="FR3"Location information can be defined to thesemodules.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




moduleLocation (ModuleLocation)

Defines a location of Flexi module in freetext with maximum 50 characters or has thevalue -1 (Not defined). The value -1 (Notdefined) is not used at the commissioningfile. Location can be e.g. place or address of the module.

numOfLines (Number of Mains Power Alarm Lines)

Defines the number of External Alarm Linesreserved by Mains Break. The allowedvalues are 0,1 and 3.

numberOfLines (Number of Mains Power AlarmLines)


passiveUnitList (PassiveUnit List)

The list defines commissioned passive units.

comment (Comment) Free text about the passive unit in question.

name (Name) Defines the name of the passive unit inquestion.

prodCode (Product Code) Defines the product code of the passive unitin question.

productCode (ProductCode)

Defines the product code of the passive unitin question.

serNum (Serial Number) Defines the serial number of the passive unit

in question.serialNumber (SerialNumber)

Defines the serial number of the passive unitin question.

version (Version) Defines the version of the passive unit inquestion.

qosSchedList (HSDPAQuality of ServiceScheduling for SPIClasses)

HSDPA Quality of Service Scheduling for SPI classes


30/09/2008

Changes in RU10




ccPolicy (HSDPACongestion Control Policyfor SPI Class)

This parameter is used to select how theHSDPA Congestion Control (when enabled)treats different traffic classes in case of Iuboverload. 0: This setting is intended for Background and Interactive NRT trafficclasses. In case of Iub overload, congestioncontrol is allowed to reduce the bit rate onIub frame protocol level down to 0 credits, if needed. Nominal Bit Rate (NBR - notguaranteed) can be mapped to a Interactiveclass SPI value and for those "0" is therecommended setting. 1: This setting isintended for Streaming and ConversationalRT traffic classes to protect the GuaranteedBit Rate (GBR). In case of Iub overload,congestion control is allowed to reduce thebit rate on Iub frame protocol level only downto bit rate defined by GBR, if needed. It ispossible to allocate extra capacity on top of GBR with scheduling weight parameters, butrecommended setting is that there should beno excess bit rate allocated on top of GBRwith scheduling weights. Nominal Bit Rate(NBR - not guaranteed) can be mapped to aInteractive class SPI value and for thosesetting "1" behaves similarly as for Streaming and Conversational. It is however

not recommended, because the NBR is notguaranteed traffic on Iub. 2: CongestionControl is off for this SPI class.

id (QoS Scheduling for SPI Class Identification)

HSDPA Quality of Service SchedulingPriority Indicator (SPI) Class identifier (0-15).This is standard defined identification of apriority class with zero being the lowestpriority and 15 the highest.

weight (Scheduling Weightfor SPI class)

Defines a scheduling weight for priorityqueues with specific SPI value. When thereare no services with Guaranteed Bit Rate(GBR) in a cell, the weights are used to

define the proportion in which the queues ina cell are scheduled in proportion to eachother (the proportion is roughly the weight of queue divided by the sum of the weights of all queues). When there are priority queueswith GBR service in a cell, the weights areused to divide in similar manner the possiblyremaining scheduling capacity what is leftafter GBR requirements of queues are met.

qosSchedulingList(HSDPA Quality of ServiceScheduling for SPIClasses)


DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




ccPolicy (HSDPACongestion Control Policyfor SPI Class)

This parameter is used to select how theHSDPA Congestion Control (when enabled)treats different traffic classes in case of Iuboverload. 0: This setting is intended for Background and Interactive NRT trafficclasses. In case of Iub overload, congestioncontrol is allowed to reduce the bit rate onIub frame protocol level down to 0 credits, if needed. Nominal Bit Rate (NBR - notguaranteed) can be mapped to a Interactiveclass SPI value and for those "0" is therecommended setting. 1: This setting isintended for Streaming and ConversationalRT traffic classes to protect the GuaranteedBit Rate (GBR). In case of Iub overload,congestion control is allowed to reduce thebit rate on Iub frame protocol level only downto bit rate defined by GBR, if needed. It ispossible to allocate extra capacity on top of GBR with scheduling weight parameters, butrecommended setting is that there should beno excess bit rate allocated on top of GBRwith scheduling weights. Nominal Bit Rate(NBR - not guaranteed) can be mapped to aInteractive class SPI value and for thosesetting "1" behaves similarly as for Streaming and Conversational. It is however

not recommended, because the NBR is notguaranteed traffic on Iub. 2: CongestionControl is off for this SPI class.




Defines a scheduling weight for priorityqueues with specific SPI value. When thereare no services with Guaranteed Bit Rate(GBR) in a cell, the weights are used to

define the proportion in which the queues ina cell are scheduled in proportion to eachother (the proportion is roughly the weight of queue divided by the sum of the weights of all queues). When there are priority queueswith GBR service in a cell, the weights areused to divide in similar manner the possiblyremaining scheduling capacity what is leftafter GBR requirements of queues are met.

rncType (RNC Type) Defines the type of the RNC. If a NSN RNCis in use, there is no need to fill in any other RNC parameters.


30/09/2008

Changes in RU10




timeZone (Time Zone) Defines the used Time Zone. The format ispredefined, for example for Helsinki "(GMT+2) Europe/Helsinki".

unitList (Unit List) The list defines the unit information for offlinemode commissioning.

prodCode (Product Code) Defines the variant of the unit/module. Thisparameter is used in the offlinecommissioning mode.


Defines the product code of the module inquestion.

unitName (Unit Name) Defines the name of the unit/module in the

BTS. This parameter is used in the offlinecommissioning mode.

unitNumber (Unit Number) Defines the number of the unit/module in theBTS. This parameter is used in the offlinecommissioning mode.

variant (Variant) Defines the variant of the unit/module. Thisparameter is used in the offlinecommissioning mode.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.4.2.4 LCEL


allowedCarrierList (AllowedCarrier List)

Based on the hardware in the BTS, the BTSSite Manager checks which carrier valuesare allowed for BTS testing in each cell.Note: At Netact Plan Editor, the allowedcarriers are represented by parameters

AllowedCarrier1, AllowedCarrier2, AllowedCarrier3 and AllowedCarrier4. Thevalue -1 (Not defined) is not used at thecommissioning file. UARFCN TX valueranges for 2100 MHz frequency band:

10562-10838 1700/2100 MHz frequencyband: 1537-1738 1800 MHz frequency band:1162-1513 1700 MHz frequency band: 9237-9387 1900 MHz frequency band: 9662-9938850 MHz frequency band: 4357-4458 900MHz frequency band: 2937-3088 2000 MHzfrequency band: 10912-10988 AdditionalUARFCN values for 1700/2100 MHzfrequency band: 1887, 1912, 1937, 1962,1987, 2012, 2037, 2062, 2087 1900 MHzfrequency band: 412, 437, 462, 487, 512,537, 562, 587, 612, 637, 662, 687 850 MHzfrequency band: 1007, 1012, 1032, 1037,1062, 1087 2000 MHz frequency band:

5912, 5937, 5962, 5987

antennaList (Antenna List) Defines the antenna ID of the radio moduleassigned to the local cell. The used antIdnotation is FRx-ANTx, where FRx=1..3 and

ANTx=1..6. Sector Configuration Type F(Single Antenna Receiving) is using only oneantId per radio module. Sector ConfigurationType A, B and C are using two antIds per radio module.

cellRange (Cell Range) The radius of one cell. The maximum rangeof the cell, i.e. the maximum distance fromthe cell site where a MS can have a radio

connection to the cell including soft handover situations. The value is given in meters for non-NSN RNCs.

defaultCarrier (DefaultCarrier)

This parameter defines the default carrier used in tests for local cells. The UARFCNvalues used are operator-specific anddefined by the 3GPP. For example, for the2100 MHz frequency, the allowed values are10562-10838.

expirationTime (ExpirationTime)

This parameter sets the SIB7 expirationtimer for the UE. The allowed values are1,2,4,8,16,32,64,128, and 256.


30/09/2008

Changes in RU10




intShutdownTimeout(Intelligent ShutdownTimeout)

Defines the backup time after which the cellstarts to shut down itself. This parameter isused only when battery backup is used. Thetime is given in seconds. 0 is immediate and599940 is infinite. Note that BTS SiteManager UI values are in minutes (0...9999).

intelligentShutdownTimeout (Intelligent ShutdownTimeout)


lCelId (Local CellResource Identifier) The Local cell resource is an object, whichconsists of the HW required by one cell for transmission and receiving. Local cellresource identifier is used to address oneparticular local cell resource at the BTS. ThelCelId is unique within a BTS. With theConfiguration Data message the local cellresource can be associated to the cellidentifier (C-ID) used at the radio interface. Incases when configuration is initialized at theBTS, the signalling related to a cell isaddressed using C-ID instead of the localcell resource identifier.

maxCarrierPower (Maximum Carrier Power) The maximum TX carrier power for the localcell in dBm. The value is shown in Watts inthe BTS Site Manager. The allowed valuesare 39.0, 40.0, 41.8, 43.0, 44.8, 46.0 and47.8.

rachCapacity (RACHCapacity)

RACH Capacity defines the HW capacityreserved for a RACH transport channel inthe BTS. RACH Capacity is given as anumber of decoded RACH messages in a 10ms or 20 ms radio frame. The options are1,2,3 and 4.

shutdownStepAmount(Shutdown Step Amount)

A 3GPP Iub parameter for the gradualshutdown procedure. Indicates in how manysteps the transmission power for CPICH,BCH and all other common physical andtransport channels is shut down within theshutdown window.

shutdownWindow(Shutdown Window)

A 3GPP Iub parameter for the shutdownprocedure. Indicates how long the actualshutdown procedure for CPICH, BCH and allother common physical and transportchannels lasts. The time is given in seconds.If the value is 0, the gradual shutdownprocedure is not used at all.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.4.2.5 LCELG


accessBbCapacity (AccessBaseband Capacity)

Defines the LCGs access to BasebandCapacity from 0 to 100%, when BBParameter Supports.Flexible.Bb.Configuration is TRUE for all Modules. If atleast one of the used modules has BPFparameter Supports.Flexible.Bb.Configurationequal to FALSE, then the LCG access to BBcapacity is fixed according to BB Busconfiguration.

cellGroupId (Cell Group

Identification)

Cell Group Identification

cellGroupName (CellGroup Name)

User definable name for Cell Group. 1-20characters.

dedicatedBbCapacity(Dedicated BasebandCapacity)

Defines the quaranteed CE capacity for eachLCG. BTS Manager shall allow dedicatedBaseband options in percentages from 0 to100%. The sum of all dedicated options of LCGs shall not exceed 100%. If dedicatedBB Capacity is not taken in use 0% shall beused as default value.

hsupaBbDecodingCapacity(HSUPA BB DecodingCapacity)

Defines Minimum HSUPA decoding capacityper LCG in Mbit/s.

hsupaBbMinimumUsers(HSUPA BB MinimumUsers)

Defines Minimum amount of Users allocateto BaseBand in HSUPA.

hsupaBbSharingInUse(HSUPA BB Sharing InUse)

This parameter defines HSUPA BB SharingUsage.

lCelIdList (Local CellIdentifier List)

Defines the list of local cells belonging to thelocal cell groups.

lCelId (Local Cell ID) Defines LCELs which belong to a cell group;this links the LCELs to the cell groups. Thelocal cell identifier must be unique in theBTS. The value for this parameter cannotstart with a zero, so for example 011 is notan allowed value.


30/09/2008

Changes in RU10



9.4.2.6 MHA


active (Active) Defines is MHA AISG MHA or Non-AISGMHA. Selectable values is 0 (false)= Non-

AISG MHA and 1 (true )= AISG MHA .

alarmThresholdLevel(Alarm Threshold Level)

Defines a configurable alarm threshold levelfor the mast-head amplifier, used if the MHA

Alarm Detection parameter has the value 1(in use). Default value is depending on FlexiFilter (FF).

connection (Connection) Defines the connection type for MHA/LNA.

Expected values: Internal | Shared | External

downlinkDelay (DownlinkDelay)

Defines the MHA delay in the downlinkdirection. If the BTS Site Manager is used tocalculate RTT delay, this value must bespecified for an "Other" type MHA.

lnaNumber (LNA Number) Parameter for MHA telling LNA number inside one MHA. For Non AISG MHAs isused -1 (not defined).

mhaAlarmDetection (MHA Alarm Detection)

Defines if alarm detection is used or not. Theoptions are 0 (false) and 1 (true). Defaultvalues for Non-AISG MHAs and AISG MHAsin passive mode: 1 Default values for AISG

and third party MHAs:0 Note: ConfigurableMHA alarms are allowed only for passiveMHAs

mhaGain (MHA Gain) Defines the gain of the mast-head amplifier.

mhaId (MHA Identifier) Defines the specific mast-head amplifier unit.The value is given as FRx-MHAx or EXTERNALx, where FRx=1..3 andMHAx=1..6 and EXTERNALx = 1..6. For example, FR1-MHA1. Following parameterswill be included for MHAs: active,alarmThresholdLevel, antId, connection,downlinkDelay, lnaNumber,

mhaAlarmDetection, mhaGain, mhaId,mhaType, productCode,scannedAntennaInterface, serialNumber,uplinkDelay, wmhConnector

mhaType (MHA Type) Defines the type of the MHA. The supportedMHA types are: WMHA, WMHB, WMHC,WMHD, MDTA, MDPA, MDGA, MDDA,FLJA, DTMAFV1, DTMAFV3, DTMAFV4,DTMARETFV1, DTMARETFV2,DTMARETFV3, DTMARETFV4,SDTMARETFV1, SDTMARETFV2,SDTMARETFV3, TMAFV1, TMAFV3,TMAFV4, TMARETFV1 and other.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes





Defines the product code of the unit inquestion.

scannedAntennaInterface(Scanned AntennaInterface)

Defines which antenna interface is scanned.Expected value: FRx-ANTx and empty stringwhere FRx: 1...3 and ANTx: 1...6 It isdepending on radio module type whichantennas are capable for scanning / AISGdevice detection.

serialNumber (SerialNumber)

Defines the serial number of the unit inquestion.

uplinkDelay (Uplink Delay) Defines the MHA delay in the uplink directionfor an "Other" type MHA. If the BTS Site

Manager is used to calculate antenna roundtrip time delay, this value must be specified.

wmhConnector (WMHConnector)

Defines the WMH connector in question for WMHC and WMHD. The options are BTS1(Pass-through) and BTS2 (Power). If MHAtype is other than WMHC/WMHD thenwmhConnector parameter value is empty.

9.4.2.7 RET


connection (Connection) Defines the connection type for TILT.Expected values: Internal | Shared | External



retId (RET Identifier) Defines the specific Antenna tilting unit. Thevalue is given as FRx-TILTx or EXTERNALx,where FRx=1..3 and TILTx=1..6 andEXTERNALx = 1..6. For example, FR1-TILT1.

scannedAntennaInterface

(Scanned AntennaInterface)

Defines which antenna interface is scanned.

Expected value: FRx-ANTx and empty stringwhere RFx: 1...3 and ANTx: 1...6 It isdepending on radio module type whichantennas are capable for scanning / AISGdevice detection.




30/09/2008

Changes in RU10




9.4.3.1 WCEL_HW

. AllowedCarrier (Allowed Carrier)

. CellRange (Cell Range)

. Concept (Concept)

. DefaultCarrier (Default Carrier)

. ExpirationTime (Expiration Time)

. FrAntId (FR ANT ID)

. IntelligentShutdownTimeout (Intelligent Shutdown Timeout)

. MaxCarrierPower (Max Carrier Power)

. RACHCapacity (RACH Capacity)

. ShutdownStepAmount (Shutdown Step Amount)

. ShutdownWindow (Shutdown Window)

9.4.3.2 ANTENNA_HW

. AntennaId (Antenna Id)

. AntennaRoundTripDelay (Antenna Round Trip Delay)

. AntennaTotalLoss (Antenna Total Loss)

. CableLength (Cable Length)

. DiplexerAmount (Diplexer Amount)

. DiplexerInUse (Diplexer In Use)

. DiplexerLoss (DiplexerLoss)

. DiplexerTotalDelay (DiplexerTotalDelay)

. DiplexerType (Diplexer Type)

. FeederLoss (Feeder Loss)

. FeederVoltage (Feeder Voltage)

. PHSFilterInUse (PHS Filter In Use)

. PHSTotalDelay (PHS filter Total Delay)

. SBCInUse (Same Band Combiner In Use)

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



. SBCProductCode (Same Band Combiner Product Code)

. TriplexerInUse (Triplexer in use)

. VelocityFactor (Velocity Factor)

9.4.3.3 WBTS_HW

. AscuIpAddress (ASCU IP Address)

. AuthenticationServerIpAddress (Authentication Server IP Address)

. AuthenticationServerName (Authentication Server Name)

. BsConfigurationIdentifier (BS Configuration Identifier)

. CabinetIdInLargeWBTS (Cabinet Id)

. CabinetType (Cabinet Type)

. CommissioningMode (Commissioning Mode)

. FileAuthor (File Author)

. FileCreationDate (File Creation Date)

. FileVersionIdentification (File Version Identification)

. Fr1ModuleLocation (FR1 Module Location)



. Fsm1ModuleLocation (FSM1 Module Location)

. Fsm2ModuleLocation (FSM2 Module Location)

. HSDPABBResourceAllocation (HSDPA BB Resource Allocation)

. IntelligentShutdownInUse (Intelligent Shutdown In Use)

.

MainsPowerAlarmId (Mains Power Alarm Id). MainsPowerAlarmLines (Number of Mains Power Alarm Lines)

. RNCType (RNC Type)

. TimeZone (Time Zone)

. Version (WBTS SW Version)


30/09/2008

Changes in RU10



9.4.3.4 WBTS

. WBTSId (WBTS Identifier)

. WBTSName (WCDMA BTS name)

9.4.3.5 OUTPUT_EAC

. InitialOutputAlarmState (Initial State)

. OutputAlarmDescription (Description)

. OutputLineId (Line Id)

9.4.3.6 FILEMODE_UNIT

. FuName (Filemode Unit Name)

. UnitNumber (Unit Number)

. Variant (Variant)

9.4.3.7 PASSIVE_UNIT

. Comment (Comment)

. ProductCode (Product Code)

. PuName (Passive Unit Name)

. PuVersion (Version)

. SerialNumber (Serial Number)

9.4.3.8 TILT


. ConfigFile (Configuration File)

. Connection (Connection)

. Manufacturer (Manufacturer)


. ScannedAntennaInterface (Scanned Antenna Interface)


. TILTAntennaId (TILT Id)

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.4.3.9 WCEL

. LcrId (Local cell resource identifier)

9.4.3.10 MHA

. Active (Active)

. AlarmThresholdLevel (Alarm Threshold Level)


. Connection (Connection)

.

DownlinkDelay (Downlink Delay). LNANumber (LNA Number)

. MHAAlarmDetection (MHA Alarm Detection)

. MHAType (MHA Type)

. MhaAntennaId (MHA Id)

. MhaGain (MHA Gain)


.

ScannedAntennaInterface (Scanned Antenna Interface). SerialNumber (Serial Number)

. UplinkDelay (Uplink Delay)

. WMHConnector (WMH Connector)

9.4.3.11 CELL_GROUP

. CellGroupId (Cell Group Id)

. HSUPABBDecodingCapacity (HSUPA BaseBand Decoding

Capacity). HSUPABBMinimumUsers (HSUPA BaseBand Minimum Users)

. HSUPABBSharingInUse (HSUPA BaseBand Sharing In Use)

. LcrId (LCR ID)

. WspId (WSP ID)


30/09/2008

Changes in RU10



9.4.3.12 INPUT_EAC

. InputAlarmDescription (Description)

. InputAlarmSeverity (Severity)

. InputLineId (Line Id)

. InputSignalPolarity (Polarity)

9.5 Changes in Plan Editor UltraSite WCDMA BTSParameters

9.5.1 Introduction

The following sections describe the changes in parameters supported byNetAct Radio Access Configurator among Plan Editor UltraSite WCDMABTS WBTS5.0 and WBTS4.0 CD2. The information is intended for thoseinvolved in network planning, implementation and roll-out, configurationmanagement, and engineering support.

For more information on parameters in Plan Editor Flexi WCDMA BTS

Parameters, see Plan Editor UltraSite WCDMA BTS Parameters .


9.5.2.1 ANTL


antennaRoundTripDelay(Antenna Round TripDelay)

The delay of the all passive units of antennaline can be entered into this parameter,which is then used as the RTT value instead

of calculating the value using the BTS SiteManager.

antlId (Antenna Id) Identifies the specific antenna. The value isgiven as Antennaid, where id=1..12.

btuList (Bias-T Unit List) The list defines the parameters for Bias-TUnits.





DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




vswrAlarmDetection(VSWR Alarm Detection)

Defines the usage of the VSWR alarmdetection.

cableLength (CableLength)

Defines the antenna RF cable length inmeters. This parameter is used by BTS SiteManager to calculate antenna round tripdelay. The delay is 4.5 ns/m. The value for this parameter must be 0 if the RTT valuehas already been entered in theantennaRoundTripDelay parameter. TheantennaRoundTripDelay value is then usedinstead of letting the BTS Site Manager calculate the value based on, for example,cableLength.

feederLoss (Feeder Loss) Defines the feeder loss of the antenna cable.

feederVoltage (Feeder Voltage)

Defines the voltage level supplied to theantenna line. The values entered for thisparameter depend on the MHA type: WMHA,WMHB: 10 WMHC, WMHD: BTS1 0, BTS210 MDTA: 0 Other: 0

multiplexerList (Multiplexer List)

The list defines the parameters for multiplexers.

diplexerType (Diplexer Type)

Defines type of multiplexer.

rxCablingList (RX CablingList)

The list defines the parameters for RXcabling.

externalGain (ExternalGain)

Defines the dB value of the external gain.This parameter is currently not used and canbe left empty.

input (Input) Defines the input unit for RX cabling beingeither WAF or WOU. The values are enteredas WAFid and WOUid, where id=1..6.

inputPort (Input Port) Defines the RX cable input port. The allowedvalues are RX1, RX2, RX3, RX4, RX DIV1,RX DIV2, RX DIV3, RX DIV4 andEXTERNAL.

rxCableId (RX Cable Id) A running number starting from 1, used tonumber each RX cable.

wicId (WIC Id) Identifies the specific wideband inputcombiner. The allowed values are: WIC1WIC2 WIC3 EXTCOMB If an AIR combiner is used, EXTCOMB is selected.

wicPort (WIC Port) Defines the port of the wideband inputcombiner. The allowed values are: Comb In1 Comb In 2 Comb Out Div Out 1 Div Out 2Div In


30/09/2008

Changes in RU10




wtrId (WTR Id) Identifies the specific WCDMA transceiver unit. The values are entered as WTRid,where id=1..6.

wtrPort (WTR Port) Defines the port of the WCDMA receiver unit. The allowed values depend on the WTRtype: WTRA: Port="RX1" | Port="RX2"WTRB, WTRD, WTRF, WTRG: Port="RXM1"| Port="RXD1" | Port="RXM2" | Port="RXD2"

rxSignalUsage (RX SignalUsage)

Defines the usage of the RX signal. Theoptions are Main and Diversity.

txCablingList (TX CablingList)

The list defines the parameters for TXcabling.

output (Output) Defines the output unit for TX cabling beingeither WAF or WOU. The values are enteredas WAFid and WOUid, where id=1..6.

txCableId (TX Cable Id) A running number starting from 1, used tonumber each TX cable.


wicPort (WIC Port) Defines the port of the wideband inputcombiner. The allowed values are: Comb In

1 Comb In 2 Comb Out Div Out 1 Div Out 2Div In

wpaId (WPA Id) Defines the specific WCDMA linear power amplifier unit. The allowed values are:WPA1, WPA2, WPA3, WPA4, WPA5, WPA6,WMP1, WMP2, WMP3


wtrPort (WTR Port) Defines the port of the WCDMA transceiver unit. The allowed values are: TX1, TX2 andSUMTX.

velocityFactor (VelocityFactor)

The velocity factor is used to calculate RTTmore exactly. The velocity factor can beobtained from the specifications of the usedcable.

wafAntennaId (WAF Antenna Id)

The WAF Antenna Id parameter has values1-3, and the value depends on the WAFtype. For WAFG values 1-3 are available, for WAFH values 1-2 and for all other WAFvariants value 1. For WOU, the only allowedvalue is 1.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




wafId (WAF Id) Defines the specific WCDMA antenna filter unit. This parameter is also used for WOUdefining. The allowed values are WAFid andWOUid, where id=1..6.

wiaList (WIA List) The list defines parameters for WIA units.





9.5.2.2 ANTLD


antldId (Antenna LineDevice Identification)

Antenna Line Device Identification

btuList (Bias-T Unit List) The list defines the parameters for Bias-TUnits.



serialNumber (Serial

Number)

Defines the serial number of the unit in

question.

vswrAlarmDetection(VSWR Alarm Detection)

Defines the usage of the VSWR alarmdetection.

multiplexerList (Multiplexer List)

The list defines the parameters for multiplexers.

diplexerType (Diplexer Type)

Defines type of multiplexer.

wiaList (WIA List) The list defines parameters for WIA units.






30/09/2008

Changes in RU10



9.5.2.3 BTSSC


adaptationVersionMajor (Adaptation Version Major)

AdaptationVersionMajor shows the lastrelease main part where changes have cometo the SCF file (e.g. WN5.00).

AdaptationVersionMajor is updated toindicate compatiblity changes.

adaptationVersionMinor (Adaptation Version Minor)

AdaptationVersionMinor of WBTS-objectcontains the current commissioning fileversion (e.g. 450).

btsConfiguration (BTS

Configuration)

A free text field for defining the used BTS

configuration. For example: 1+1+1 20 W.

btsName (BTS Name) This parameter can be used for identificationof the WCDMA BTS (Node B).

btsscId (BTS SiteIdentification)

Defines specific Base Station site. This isunique indentifier inside network.

cabinetId (CabinetIdentification)

Defines the specific cabinet

cabinetType (CabinetType)

Defines the cabinet type. The allowed valuesare: 1 or 12 (=Supreme-Indoor) 2(=Supreme-Outdoor) 3 (=Optima-Indoor) 4(=Optima-Outdoor) 5 (=Triple-Mode-Indoor) 6

(=Triple-Mode Outdoor) 7 or 9 (=Optima-Compact (IBBU)) 8 or 10 (=Optima Compact(RF Extension)) 11 (=MetroSite) 13 (=OptimaCompact Outdoor) 14 (=METROSITE_50)

commHList(Commissioning HistoryList)

Defines the Commissioning history for thespecific BTS.

btsManVer (BTS Manager Version)

Defines the version of the BTS Manager.

commType(Commissioning Type)

Defines the type of the commissioning.Expected values: Manual | Planned |Template | Reconfiguration




previousFileV (PreviousFile Version)

Defines the structure version of the SiteConfiguration File (SCF).

doorSwitchInUse (Door Switch In Use)

Defines the usage of the door switch. If thisparameter is in use, an alarm is triggeredwhen the door of the BTS cabinet is opened.

extAlList (External AlarmInput Signal List)


DN70515054Issue 1-0 en draft30/09/2008


Parameter changes





id (Line ID) Defines the external alarm lines. inUse,description, polarity and severity must bedefined for input signals. There are 24 InputSignals in UltraSite.





extCtrlList (ExternalControl Signal List)



id (Line ID) Defines the external alarm lines. inUse,description and initialState must be definedfor Control Signals. There are 6 outputsignals in UltraSite.

inUse (In Use) Defines is particular external control l ine inuse or not in use.


polarity (Polarity) efines the used polarity of the external alarmline: normally open or normally closed.

Normally_open: when the connector is open,there is no alarm. Normally_closed: when theconnector is closed, there is alarm.


externalAlarmInputSignalList (External Alarm InputSignal List)




30/09/2008

Changes in RU10




id (Line ID) Defines the external alarm lines. inUse,description, polarity and severity must bedefined for input signals. There are 24 InputSignals in UltraSite.



polarity (Polarity) Defines the used polarity of the externalalarm line: normally open or normally closed.

Normally_open: when the connector is open,there is no alarm. Normally_closed: when theconnector is closed, there is alarm.


externalAlarmOutputSignalList (External Alarm OutputSignal List)



id (Line ID) Defines the external alarm lines. inUse,

description and initialState must be definedfor Control Signals. There are 6 outputsignals in UltraSite.

inUse (In Use) Defines is particular external control l ine inuse or not in use.


polarity (Polarity) efines the used polarity of the external alarmline: normally open or normally closed.Normally_open: when the connector is open,there is no alarm. Normally_closed: when theconnector is closed, there is alarm.





fileCrDate (File CreationDate)


DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




happyBitPingFiltUse(HSUPA Happy Bit -ratioping filtering)


happyBitPingFilterInUse(HSUPA Happy Bit -ratioping filter)

Parameter is used to to define filtering for Happy Bit -ratio measurement. If filtering isactive, then Happy Bit -ratio counter is notupdated based on Happy bit preceding DTX

frame/subframe. The target for filtering is tofilter out small data bursts (such as ping)from Happy Bit -ratio measurement as theydo not give reliable information of UEallocation.

happyBitUphThreshold(HSUPA Happy Bit -ratioUPH threshold)

Parameter defines threshold value for UEPower Headroom (UPH) values in Happy Bit-ratio measurement. Happy Bits that areassociated to UPH values that are below thedefined threshold, are not taken into accountin Happy Bit -ratio measurement. The targetfor filtering is to filter out power limitedsituation from Happy Bit -ratio measurement

as they do not give reliable information of UEallocation.


30/09/2008

Changes in RU10




mainsPowerAlarmId(Mains Power Alarm ID)

Defines the starting external alarm line for the mains power alarm when the intelligentshutdown is in use. Default values: NSNBBU: 19 Other BBU: a value between 1-24can be chosen

maxIubDelayThreshold(Maximum Iub DelayThreshold)

The maximum delay threshold after thesystem is interpreted to be in very severecongestion and propability to reduce creditsis 100%. Threshold defines the deviation of arrival interval from the TTI given to Iub.Note: Thmin < Thmid < Thmax

maximumIubDelayThreshol

d (Maximum Iub DelayThreshold)

The maximum delay threshold after the

system is interpreted to be in very severecongestion and propability to reduce creditsis 100%. Threshold defines the deviation of arrival interval from the TTI given to Iub.Note: Thmin < Thmid < Thmax

mibbuType (MIBBU Type) Defines the integrated battery backup type of the UltraSite Optima Compact Outdoor (WREB) cabinet. 0 = IBBU not equipped 1 =IBBU with Basic Batteries 2 = IBBU withBasic and Extesion Batteries Note!Exceptionally integer enumration values areused in implementation.

midIubDelayThreshold(Middle Iub DelayThreshold)


middleIubDelayThreshold(Middle Iub DelayThreshold)


minIubDelayThreshold

(Minimum Iub DelayThreshold)

Defines the minimum delay threshold after

the MECN procedure activates. Thresholddefines the deviation of arrival interval fromthe TTI given to Iub. Note: Thmin < Thmid <Thmax

minimumIubDelayThreshold (Minimum Iub DelayThreshold)

Defines the minimum delay threshold after the MECN procedure activates. Thresholddefines the deviation of arrival interval fromthe TTI given to Iub. Note: Thmin < Thmid <Thmax

noiseKitInUse (Noise Kit InUse)

Defines the usage of the noise reduction kit.The noise kit is used only with the UltraSitecabinets Supreme Outdoor and Optima

Compact Outdoor.


30/09/2008

Changes in RU10




numOfLines (Number of Mains Power Alarm Lines)


numberOfLines (Number of Mains Power AlarmLines)

Defines the number of External Alarm Linesreserved by Mains Break. The allowedvalues are 0, 1 and 3.

qosSchedList (HSDPAQuality of ServiceScheduling for SPIClasses)


ccPolicy (HSDPACongestion Control Policy

for SPI Class)

This parameter is used to select how theHSDPA Congestion Control (when enabled)

treats different traffic classes in case of Iuboverload. 0: This setting is intended for Background and Interactive NRT trafficclasses. In case of Iub overload, congestioncontrol is allowed to reduce the bit rate onIub frame protocol level down to 0 credits, if needed. Nominal Bit Rate (NBR - notguaranteed) can be mapped to a Interactiveclass SPI value and for those "0" is therecommended setting. 1: This setting isintended for Streaming and ConversationalRT traffic classes to protect the GuaranteedBit Rate (GBR). In case of Iub overload,

congestion control is allowed to reduce thebit rate on Iub frame protocol level only downto bit rate defined by GBR, if needed. It ispossible to allocate extra capacity on top of GBR with scheduling weight parameters, butrecommended setting is that there should beno excess bit rate allocated on top of GBRwith scheduling weights. Nominal Bit Rate(NBR - not guaranteed) can be mapped to aInteractive class SPI value and for thosesetting "1" behaves similarly as for Streaming and Conversational. It is however not recommended, because the NBR is notguaranteed traffic on Iub. 2: Congestion

Control is off for this SPI class.



DN70515054Issue 1-0 en draft30/09/2008


Parameter changes





Defines a scheduling weight for priorityqueues with specific SPI value. When thereare no services with Guaranteed Bit Rate(GBR) in a cell, the weights are used todefine the proportion in which the queues ina cell are scheduled in proportion to eachother (the proportion is roughly the weight of queue divided by the sum of the weights of all queues). When there are priority queueswith GBR service in a cell, the weights areused to divide in similar manner the possiblyremaining scheduling capacity what is leftafter GBR requirements of queues are met.

qosSchedulingList(HSDPA Quality of ServiceScheduling for SPIClasses)


ccPolicy (HSDPACongestion Control Policyfor SPI)

This parameter is used to select how theHSDPA Congestion Control (when enabled)treats different traffic classes in case of Iuboverload. 0: This setting is intended for Background and Interactive NRT trafficclasses. In case of Iub overload, congestioncontrol is allowed to reduce the bit rate onIub frame protocol level down to 0 credits, if needed. Nominal Bit Rate (NBR - not

guaranteed) can be mapped to a Interactiveclass SPI value and for those "0" is therecommended setting. 1: This setting isintended for Streaming and ConversationalRT traffic classes to protect the GuaranteedBit Rate (GBR). In case of Iub overload,congestion control is allowed to reduce thebit rate on Iub frame protocol level only downto bit rate defined by GBR, if needed. It ispossible to allocate extra capacity on top of GBR with scheduling weight parameters, butrecommended setting is that there should beno excess bit rate allocated on top of GBR

with scheduling weights. Nominal Bit Rate(NBR - not guaranteed) can be mapped to aInteractive class SPI value and for thosesetting "1" behaves similarly as for Streaming and Conversational. It is however not recommended, because the NBR is notguaranteed traffic on Iub. 2: CongestionControl is off for this SPI class.




30/09/2008

Changes in RU10





Defines a scheduling weight for priorityqueues with specific SPI value. When thereare no services with Guaranteed Bit Rate(GBR) in a cell, the weights are used todefine the proportion in which the queues ina cell are scheduled in proportion to eachother (the proportion is roughly the weight of queue divided by the sum of the weights of all queues). When there are priority queueswith GBR service in a cell, the weights areused to divide in similar manner the possiblyremaining scheduling capacity what is leftafter GBR requirements of queues are met.

rncType (RNC Type) Defines the type of the RNC. If a NSN RNCis in use, there is no need to fill in any other RNC parameters.

smokeAlarmInUse (Smoke Alarm In Use)

Defines the usage of the smoke alarm.

smokeAlarmPolarity(Smoke Alarm Polarity)

Defines the used polarity of the externalalarm line: Normally_open or Normally_closed.

timeZone (Time Zone) Defines the used Time Zone. The format ispredefined, for example for Helsinki "(GMT+2) Europe/Helsinki".

9.5.2.4 LCEL


allowedCarrierList (AllowedCarrier List)

Based on the hardware in the BTS, the BTSSite Manager checks which carrier valuesare allowed for BTS testing in each cell.UARFCN TX value ranges for 2100 MHzfrequency band: 10550-10850 1900 MHzfrequency band: 9262-9950 850 MHzfrequency band: 4132-4470 AdditionalUARFCN values for 1900 MHz frequencyband: 412, 437, 462, 487, 512, 537, 562,587, 612, 637, 662, 687 850 MHz frequencyband: 1007, 1012, 1032, 1037, 1062, 1087

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




carrier (Allowed Carrier List)

Based on the hardware in the BTS, the BTSSite Manager checks which carrier valuesare allowed for BTS testing in each cell.Note: At Netact Plan Editor, the allowedcarriers are represented by parameters

AllowedCarrier1, AllowedCarrier2, AllowedCarrier3 and AllowedCarrier4. Thevalue -1 (Not defined) is not used at thecommissioning file. UARFCN TX valueranges for 2100 MHz frequency band:10550-10850 1900 MHz frequency band:9262-9950 850 MHz frequency band: 4132-4470 Additional UARFCN values for 1900MHz frequency band: 412, 437, 462, 487,512, 537, 562, 587, 612, 637, 662, 687 850MHz frequency band: 1007, 1012, 1032,1037, 1062, 1087

cellRange (Cell Range) The radius of one cell. The maximum rangeof the cell, i.e. the maximum distance fromthe cell site where a MS can have a radioconnection to the cell including soft handover situations. The value is given in meters for non-NSN RNCs.

concept (Concept) Defines the used configuration concept. Theoptions are: CEC CEC with WOC ROC-2ROC-3 ARIO ARIO with CEC

defaultCarrier (DefaultCarrier)

This parameter defines the default carrier used in tests for local cells. The UARFCNvalues used are operator-specific anddefined by the 3GPP. For example, for the2100 MHz frequency, the allowed values are10562-10838.

expirationTime (ExpirationTime)

This parameter sets the SIB7 expirationtimer for the UE. The allowed values are1,2,4,8,16,32,64,128, and 256.

intShutdownTimeout(Intelligent ShutdownTimeout)


intelligentShutdownTimeout (Intelligent ShutdownTimeout)

Defines the backup time after which the cellstarts to shut down itself. This parameter isused only when battery backup is used. Thetime is given in seconds. 0 is immediate and599940 is infinite. Note that UI values are inminutes (0...9999).


30/09/2008

Changes in RU10




lCelId (Local CellResource Identifier)

The Local cell resource is an object, whichconsists of the HW required by one cell for transmission and receiving. Local cellresource identifier is used to address oneparticular local cell resource at the BTS. ThelCelId is unique within a BTS. With theConfiguration Data message the local cellresource can be associated to the cellidentifier (C-ID) used at the radio interface. Incases when configuration is initialized at theBTS, the signalling related to a cell isaddressed using C-ID instead of the localcell resource identifier.

rachCapacity (RACHCapacity)

RACH Capacity defines the HW capacityreserved for a RACH transport channel inthe BTS. RACH Capacity is given as anumber of decoded RACH messages in a 10ms or 20 ms radio frame. The options are1,2,3 and 4.

shutdownStepAmount(Shutdown Step Amount)

A 3GPP Iub parameter for the gradualshutdown procedure. Indicates in how manysteps the transmission power for CPICH,BCH and all other common physical andtransport channels is shut down within theshutdown window.

shutdownWindow(Shutdown Window) A 3GPP Iub parameter for the shutdownprocedure. Indicates how long the actualshutdown procedure for CPICH, BCH and allother common physical and transportchannels lasts. The time is given in seconds.If the value is 0, the gradual shutdownprocedure is not used at all.

trxId (TRX Identification) Identifies the specific WCDMA transceiver unit in specific WTR. The allowed values are:WTR1-TRX1 WTR1-TRX2 WTR2-TRX1WTR2-TRX2 WTR3-TRX1 WTR3-TRX2WTR4-TRX1 WTR4-TRX2 WTR5-TRX1WTR5-TRX2 WTR6-TRX1 WTR6-TRX2

""(Not used)

trxList (TRX List) The list defines the parameters for commissioned TRXs.

intTxSumInUse (InternalTX Summing In Use)

Defines the usage of internal TX summing.Internal TX summing can be used only for double-capacity WTR units, which have 2TRXs in the same physical unit.

internalTxSummingInUse(Internal TX Summing InUse)

Defines the usage of internal TX summing.Internal TX summing can be used only for double-capacity WTR units, which have 2TRXs in the same physical unit.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




trxId (TRX ID) Identifies the specific WCDMA transceiver unit in specific WTR. The allowed values are:WTR1-TRX1 WTR1-TRX2 WTR2-TRX1WTR2-TRX2 WTR3-TRX1 WTR3-TRX2WTR4-TRX1 WTR4-TRX2 WTR5-TRX1WTR5-TRX2 WTR6-TRX1 WTR6-TRX2""(Not used)

txRxUsage (TX RX Usage) Defines the TX/RX usage. The options are:Only_RX_used Only_TX_usedTX_and_RX_used Neither_TX_or_RX_used

wocInUse (WOC In Use) Defines the usage of the WCDMA outputcombiner. If WOC is used, it combines the

output of 2 WPA units.

9.5.2.5 LCELG


cellGroupId (Cell GroupIdentification)

Cell Group Identification

hsupaBbDecodCapacity(HSUPA BB DecodingCapacity)


hsupaBbDecodingCapacity(HSUPA BB DecodingCapacity)


hsupaBbMinimumUsers(HSUPA BB MinimumUsers)

Defines Minimum amount of Users allocateto BaseBand in HSUPA.

hsupaBbSharingInUse(HSUPA BB Sharing InUse)

This parameter defines HSUPA BB SharingUsage.

lCelIdList (Local CellIdentifier List)

Defines the list of local cells belonging to thelocal cell groups.

signalProcessorIdList(Signal Processor Identifier List)

Defines the list of signal processor unitsbelonging to the local cell group.

wspId (WSP ID) Defines the WSP unit belonging to the localcell group. The allowed values are WSPidand -1 (Not defined), where id=1..18.


30/09/2008

Changes in RU10



9.5.2.6 MHA


antId (Antenna Id) Identifies the specific antenna. The value isgiven as Antennaid, where id=1..12.

downlinkDelay (DownlinkDelay)

Defines the MHA delay in the downlinkdirection. If the BTS Site Manager is used tocalculate RTT delay, this value must bespecified for an "Other" type MHA.

mhaAlarmDetection (MHA Alarm Detection)

Defines if alarm detection is used or not. Theoptions are 0 (false) and 1 (true). true:WMHA, WMHB, WMHC Power, WMHD

Power false: WMHC Pass-trough, WMHDPass-trough, Other.

mhaGain (MHA Gain) Defines the gain of the mast-head amplifier.

mhaId (MHA Id) Defines the specific mast-head amplifier unit.The value is given as MHAid, whereid=1..12.

mhaType (MHA Type) Defines the type of the MHA. The supportedMHA types are: WMHA, WMHB, WMHC,WMHD and Other.

prodCode (Product Code) Defines the product code of the unit inquestion.



serNum (Serial Number) Defines the serial number of the unit inquestion.



uplinkDelay (Uplink Delay) Defines the MHA delay in the uplink directionfor an "Other" type MHA. If the BTS SiteManager is used to calculate antenna roundtrip time delay, this value must be specified.

wmhConnector (WMH

Connector)

Defines the WMH connector in question for

WMHC and WMHD. The options are BTS1(Pass-through) and BTS2 (Power).

9.5.2.7 PATH


pathId (PATHIdentification)

Defines specific radio path for BTS internalRF cabling.

rxCablingList (RX Cabling

List)

The list defines the parameters for RX

cabling.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




externalGain (ExternalGain)

Defines the dB value of the external gain.This parameter is currently not used and canbe left empty.

input (Input) Defines the input unit for RX cabling beingeither WAF or WOU. The values are enteredas WAFid and WOUid, where id=1..6.

inputPort (Input Port) Defines the RX cable input port. The allowedvalues are RX1, RX2, RX3, RX4, RX DIV1,RX DIV2, RX DIV3, RX DIV4 andEXTERNAL.

rxCableId (RX Cable Id) A running number starting from 1, used tonumber each RX cable.




wtrPort (WTR Port) Defines the port of the WCDMA receiver unit. The allowed values depend on the WTRtype: WTRA: Port="RX1" | Port="RX2"WTRB, WTRD, WTRF, WTRG: Port="RXM1"| Port="RXD1" | Port="RXM2" | Port="RXD2"

txCablingList (TX CablingList)

The list defines the parameters for TXcabling.

output (Output) Defines the output unit for TX cabling beingeither WAF or WOU. The values are enteredas WAFid and WOUid, where id=1..6.

txCableId (TX Cable Id) A running number starting from 1, used tonumber each TX cable.



wpaId (WPA Id) Defines the specific WCDMA linear power amplifier unit. The allowed values are:WPA1, WPA2, WPA3, WPA4, WPA5, WPA6,

WMP1, WMP2, WMP3


30/09/2008

Changes in RU10





wtrPort (WTR Port) Defines the port of the WCDMA transceiver unit. The allowed values are: TX1, TX2 andSUMTX.


9.5.3.1 ANTENNA_HW


. AntennaRoundTripDelay (Antenna Round Trip Delay)

. CableLength (Cable Length)

. DuplexerInUse (Duplexer in Use)

. FeederLoss (Feeder Loss)

. FeederVoltage (Feeder Voltage)

.

RXSignalUsage (RX Signal Usage). TriplexerInUse (Triplexer in use)

. VelocityFactor (Velocity Factor)

. WafAntennaId (WAF Antenna Id)

. WafId (WAF Id)

9.5.3.2 WBTS_HW

. A2EAFormula (A2EA Formula)

. AAL2MultiplexingInUse (AAL2 Multiplexing in Use)

. AscuIpAddress (ASCU IP Address)

. AuthenticationServerIpAddress (Authentication Server IP Address)

. AuthenticationServerName (Authentication Server Name)

. BsConfigurationIdentifier (BS Configuration Identifier)

. CabinetIdInLargeWBTS (Cabinet Id)

. CabinetType (Cabinet Type)

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



9.5.3.9 WCEL_HW

. AllowedCarrier (Allowed Carrier)

. CellRange (Cell Range)

. Concept (Concept)

. DefaultCarrier (Default Carrier)

. ExpirationTime (Expiration Time)

. IntelligentShutdownTimeout (Intelligent Shutdown Timeout)

. RACHCapacity (RACH Capacity)

. ShutdownStepAmount (Shutdown Step Amount)

. ShutdownWindow (Shutdown Window)

. TrxId (TRX ID)

. WocInUse (WOC in Use)

9.5.3.10 WBTS

. WBTSId (WBTS Identifier)

.

WBTSName (WCDMA BTS name)

9.5.3.11 WIA



9.5.3.12 MHA


.

DownlinkDelay (Downlink Delay). MHAAlarmDetection (MHA Alarm Detection)

. MHAType (MHA Type)

. MhaAntennaId (MHA Id)

. MhaGain (MHA Gain)




30/09/2008

Changes in RU10



. UplinkDelay (Uplink Delay)

. WMHConnector (WMH Connector)

9.5.3.13 CELL_GROUP

. CellGroupId (Cell Group Id)

. HSUPABBDecodingCapacity (HSUPA Baseband DecodingCapacity)

. HSUPABBMinimumUsers (HSUPA Baseband Minimum Users)

. HSUPABBSharingInUse (HSUPA Baseband Sharing In Use)

. LcrId (LCR ID)

. WspId (WSP ID)

9.5.3.14 INPUT_EAC

. InputAlarmDescription (Description)

. InputAlarmSeverity (Severity)

. InputLineId (Line Id)

. InputSignalPolarity (Polarity)

9.6 Changes in WBTS Commissioning Parameters

9.6.1 Overview of parameter changes in WCDMA BTS releases

This document describes the WCDMA RAN BTS commissioning filestructure and parameter changes for the Flexi WCDMA BTS platform andthe UltraSite WCDMA BTS platform in the WN3.2, WN3.3, WN4.0 and

WN5.0 software releases. The UltraSite WCDMA BTS platform comprisesUltraSite and MetroSite50 base station products.

The document is intended for network planners, commissioning engineers,and operating personnel responsible for managing the configurations of the WCDMA BTSs.

For parameter descriptions, see the Plan Editor Flexi WCDMA BTS

Parameters and Plan Editor UltraSite WCDMA BTS Parameters

documents in the Nokia NetAct OSS Product Documentation set.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



AAL2.Multiplexing.In.Use

AAL2.Signalling.VCC

AAL2.Termination.Point

AAL2.Termination.Points

AAL5.ATM.VCC.Path

ATM.Transport.Sub-System

BTS.C-NBAP.ATM.Termination

WAM.ATM.Terminations

VCC.A2EA

VCC.CDVT

VCC.CLASS

VCC.PATH.ID

VCC.PCR.Egress

VCC.VCI

VCC.VPI

Id This parameter refers to the BTS Id under the WBTS.

Identification parameter. This parameter is not inuse, as it is now commissioned on the AXC.

Name The maximum length of the BTS name has beenchanged from 40 to 15 characters.

Authentication.Server.Identification

This parameter is not in use.

RNC.Identification

This parameter is not in use, as it is nowcommissioned on the AXC.

Removed parameters in WN3.2

There are no removed parameters.

WN3.3

There are no changes in the UltraSite commissioning parameters betweenWN3.2 and WN3.3.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



WN4.0

New parameters in WN4.0

The HSUPA.BB.Sharing.In.Use, HSUPA.BB.Minimum.Users, andHSUPA.BB.Decoding.Capacity parameters have been added in WN4.0.However, the HSUPA.BB.Sharing.In.Use is not supported in WN4.0 butthe default value for it is used.

Modified parameters in WN4.0

HSDPA.BB.Resource.Allocation

The following option has been added for thisparameter: Full.

MHA.Type The following MHA type has been added for thisparameter: WMHD.

Cell.Range The maximum value for this parameter has beenchanged from 60000 to 180000.

File.Version.Identification

The minimum value for this parameter has beenchanged from 1 to 400.

Cell.Group.Id The type of this attribute has been changed fromInteger to String.


There are no removed parameters in WN4.0.

WN5.0


Site The following elements have been added for thisparameter: Iub.Delay.Maximum.Threshold, Iub.

Delay.Middle.Threshold and Iub.Delay.Minimum.Threshold. For more information on theparameters, see HSPA in BTS .

The following element has been added for thisparameter: QOS.Scheduling with the sub-element

SPI.Class containing the attribute Id, and the sub-elements Weight and CC.Policy. For moreinformation on the parameters, see HSPA in BTS .


30/09/2008

Changes in RU10



WN3.3


There are no new parameters in WN3.3.


Diplexer.Type The value FDIA has been removed from thisparameter, the value Other is used instead.

MHA.Type The following MHA types have been added for thisparameter: MDTA, MDPA, MDGA, and MDDA. The

MHA type FLIA has been removed, the value Other isused instead.

WSP.Id Because of the Flexi Extension Module support, thefollowing changes have been made: the maximumvalue for the WSP.Id parameter has been changedfrom 3 to 6, and the values FSM2/FSP1, FSM2/FSP2,FSM2/FSP3 have been added.


There are no removed parameters in WN3.3.

WN4.0


Antenna.Sub-System

The following parameters have been added for MHA:Scanned.Antenna.Interface, Connection, Active

and LNA.Number.

The following parameter has been added for RTT:

PHS.Filter.

The TILT sub-category has been added with thefollowing parameters: In.Use, Serial.Number,

Product.Code, Scanned.Antenna.Interface,

Connection, Manufacturer, and Configuration.

File.

Parameters Manufacturer and Configuration.

File are not in use.

The Same.Band.Combiner sub-category has beenadded with the following parameters: In.Use andProduct.Code.


30/09/2008

Changes in RU10



commissioned but detected synchronisation source.

During the BTS runtime, the fault management isbased only on the status changes of thesynchronisation reference signals.

Site The following elements have been added for thisparameter: Iub.Delay.Maximum.Threshold, Iub.

Delay.Middle.Threshold, Iub.Delay.Minimum.

Threshold, Happy.Bit.Ping.Filter.In.Use,

Happy.Bit.UPH.Threshold and QOS.Scheduling

with the sub-element SPI.Class containing theattribute Id, and the sub-elements Weight and CC.

Policy. For more information on the parameters, see

HSPA in BTS .BTS.Manager.Specific.Parameters

Product.Code has been added to Unit ->Configuration -> File.Mode.Parameters for thisparameter.

The parameter is used on the HW Selection page inthe BTS Site Manager Create Commissioning Filefeature.

External.Alarm.Input.Signals.Line

The Module attribute has been added for this

parameter. The supported values are FSM1, FR1,FR2 and FR3.

WN5.0 supports external alarm lines and control linesfor certain radio module types. Radio module andsystem module (BTS) EACs are separate by this newparameter.

External.Control.Output.Signals.Line

The Module attribute has been added for thisparameter. The supported values are FSM1, FR1,FR2 and FR3.

WN5.0 supports external alarm lines and control lines

for certain radio module types. Radio module andsystem module (BTS) EACs are separate by this newparameter.

Cell.Group The following element has been added for thisparameter: BB.Capacity.Requested.Access.

The maximum HW baseband capacity (BB.

Capacity.Requested.Access) reserves a certainamount of baseband capacity for the local cell groupsbased on the available total amount of HW-basedbaseband capacity. If the detected HW (radiomodules and system modules) supports flexible


30/09/2008

Changes in RU10



baseband pooling, the maximum HW baseband

capacity can be from 1 to 99% for each local cellgroup. The sum of maximum HW baseband capacityfor LCGs must be always 100%. If some of thedetected HW (radio modules and system modules)does not support flexible baseband pooling, value 0 isused. In this case the BTS makes the actualmaximum HW baseband allocation according to theHW configuration by pre-defined rules.

Cell.Group The following element has been added for thisparameter: BB.Capacity.Dedicated.Access.

The minimum licensed baseband capacity (BB.

Capacity.Dedicated.Access) is the amount of baseband capacity that is guaranteed for each localcell group. The minimum licensed baseband capacityreserves a certain amount of baseband capacity for the local cell groups based on the available totalamount of baseband capacity licences. With theminimum licensed baseband capacity, each operator (LCG) gets a certain amount of baseband capacity inuse. The minimum licensed baseband capacity canbe set from 0 to 99% for each local cell group. Onelocal cell group cannot use all capacity if there is

more than one local cell group. The sum of minimumlicensed baseband capacity for LCGs shall notexceed 100%. If all the minimum licensed basebandcapacity (100%) is not reserved for local cell groups,the remaining capacity is left for common licensedbaseband capacity. The common licensed basebandcapacity can be accessed by all local cells groups. If the HW (radio modules and system modules)supports flexible baseband pooling, there is nospecial restrictions for the minimum licensedbaseband capacity per local cell group in addition tothe rules mentioned above. If some of the detected

HW (radio modules and system modules) does notsupport flexible baseband pooling, in case the Master System Module (MSM) and Extension SystemModule (ESM) exist, the maximum percentage valuethat can be selected for local cell groups divided for MSM and ESM can be calculated from the totalamount of channel elements supported by the MSMand ESM. For local cell group allocated for the MSM:(MSM Total.Amount.Of.CE)/(MSM Total.Amount.Of.CE+ ESM Total.Amount.Of.CE) x 100% = Maximumpercentage value for minimum baseband for MSM.

For local cell groups divided for ESM: (ESM Total.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



Amount.Of.CE)/(MSM Total.Amount.Of.CE+ ESM

Total.Amount.Of.CE) x 100% = Maximum percentagevalue for minimum licensed baseband capacity for ESM. In case the ESM does not exist and at least oneof the HW (system module and radio modules) doesnot support flexible baseband pooling, the maximumnumber of local cell groups is limited to 2 local cellgroups and the maximum percentage value for minimum licensed baseband capacity is limited to50% for each LCG.

Cell.Group The following element has been added for thisparameter: Cell.Group.Name. The operator can

assign, for example, operator-specific names for eachlocal cell group used in MORAN (multi operator RAN)BTSs.


Antenna The following values have been added to the Id

attribute for this parameter: FR1-ANT5, FR1-ANT6,FR2-ANT5, FR2-ANT6, FR3-ANT5 and FR3-ANT6.Three pipe RF modules with six antenna connectorsare supported since WN5.0.

The Max occurs has been changed from 12 to 18 for this parameter.

WCEL The following values have been added to the FR.

Ant.Id element for this parameter: FR1-ANT5, FR1- ANT6, FR2-ANT5, FR2-ANT6, FR3-ANT5 and FR3- ANT6. Three pipe RF modules with six antennaconnectors are supported since WN5.0.

The Max occurs has been changed from 6 to 12 for this parameter. The maximum number of supportedlocal cells is 12 in WN5.0.

MHA The following values have been added to the Idattribute for this parameter: FR1/MHA5, FR1/MHA6,FR2/MHA5, FR2/MHA6, FR3/MHA5 and FR3/MHA6.Three pipe RF modules with six antenna connectorsare supported since WN5.0.

The following values have been added to theScanned.Antenna.Interface element for thisparameter: FR1-ANT5, FR1-ANT6, FR2-ANT5, FR2-

ANT6, FR3-ANT5 and FR3-ANT6. Three pipe RFmodules with six antenna connectors are supportedsince WN5.0. Scanned.Antenna.Interface tells the

antenna where the AISG MHA is auto-detected from.


30/09/2008

Changes in RU10



TILT The following values have been added to the Id

attribute for this parameter: FR1/TILT5, FR1/TILT6,FR2/TILT5, FR2/TILT6, FR3/TILT5 and FR3/TILT6.Three pipe RF modules with six antenna connectorsare supported since WN5.0.

The following values have been added to the

Scanned.Antenna.Interface element for thisparameter: FR1-ANT5, FR1-ANT6, FR2-ANT5, FR2-

ANT6, FR3-ANT5 and FR3-ANT6. Three pipe RFmodules with six antenna connectors are supportedsince WN5.0. Scanned.Antenna.Interface tells theantenna where the AISG RET (TILT) is auto-detectedfrom.

Cell.Group The Max occurs has been changed from 2 to 4 for this parameter. The maximum number of supportedlocal cell groups is 4 in WN5.0.

External.Alarm.Input.Signals

The Max occurs has been changed from 14 to 26 tothe Line element for this parameter. Certain systemmodule types support 24 external alarm lines inWN5.0.

MHA.Type The following values have been added to thisparameter for TMARET units: DTMAFV1, DTMAFV3,

DTMAFV4, DTMARETFV1, DTMARETFV2,DTMARETFV3, DTMARETFV4, SDTMARETFV1,SDTMARETFV2, SDTMARETFV3, TMAFV1,TMAFV3, TMAFV4 and TMARETFV1. Ex-siemensTMARET unit is supported. TMARET is a combinedunit containing MHA and RET.

WMH.Connector The following values have been added to thisparameter for TMARET units: NODEB0 andNODEB1. Port information is needed for MHAs for Ex-Siemens TMARET unit.

Max.Carrier.Power

The data type has been changed from integer to floatfor this element. Values 39.0 (8 W), 40.0 (10 W), 41.8(15 W), 43.0 (20 W), 44.8 (30 W), 46.0 (40 W) and47.8 (60 W) are supported. The supported carrier power values depend on the radio module type. 60 Wradio modules are supported since WN5.0.


The minIncl has been changed from 400 to 450 for this parameter. The parameter is used when the BTSSite Manager validates commissioning parametersfor a specific SW release.

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes




TILT Manufacturer and Configuration.File elementshave been removed from this element.

Cell.Group WSP.Id has been removed from this parameter.

BTS.Manager.Specific.Parameters

Ascu.Units with the sub-elements In.Use and IP.

Address has been removed from this parameter.

General.Parameters

Authentication.Server.Identification and

Commissioning.Mode have been removed from thisparameter.

WCEL Concept has been removed from this parameter.

9.6.3 WBTS commissioning parameter structure for UltraSite WCDMABTS

The following figures show the commissioning parameter structure in theWN5.0 software release for the UltraSite platform.

Figure 1. Main level commissioning parameter structure for the UltraSiteplatform

WBTS

General.Parameters

WBTS.Commissioning.Configur...

Non.LCR.Sub-Systems

LCR.Sub-System

RF.Cabling.Definitions


BS.Configuration.Identifier

Time.Zone


File.Author

File.Creation.Date


30/09/2008

Changes in RU10



Figure 2. Non.LCR.Sub-Systems parameters for the UltraSite platform

Cabinet

WTR.Information

Non.LCR.Sub-Systems

External.Alarm.Sub-System

In.Use

TX.RX.Usage

Site

1..4Type

Id

Attributes

Id

Attributes

WTR

1..6

Internal.TX.Summing.In.Use

TRX

1..2

Id

Attributes

In.Use

Antenna.Sub-System

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



Figure 3. Site parameters for the UltraSite platform

Site

Intelligent.Shutdown.In.Use

Noise.Kit.In.Use

MIBBU.Type

RNC.Type


Iub.Delay.Maximum.Threshold

Iub.Delay.Middle.Threshold

Iub.Delay.Minimum.Threshold

Happy.Bit.Ping.Filter.In.Use

Happy.Bit.UPH.Threshold

WBTS.Identification Name

QOS.Scheduling SPI.Class

Id

CC.Policy

Weight


30/09/2008

Changes in RU10



Figure 4. External.Alarm.Sub-System parameters for the UltraSite platform


External.Control.Output.Signals

0..6

Door.Switch.In.Use

Smoke.Alarm

In.Use

Polarity

In.Use

Initial.State

Description

Line

Polarity

Severity

Id

Attributes

0..24

In.Use

Initial.State

Description

Line

Polarity

Severity

Id

Attributes

Mains.Power.Alarm.IdNumberOfLines

Attributes

External.Alarm.Sub_System

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



Figure 5. Antenna.Sub-System parameters for the UltraSite platform

Antenna

WIA.Unit Serial.Number

Product.Code

1..12

Id

Attributes

WAF.IdAntenna

Attributes

Antenna.Sub_System

In.Use

WMH.Connector

Uplink.Delay

MHA.Type

Serial.Number

Product.Code

In.Use

MHA.Gain

Downlink.Delay

MHA.Alarm.Detection

Serial.Number

Product.Code

In.Use

VSWR.Alarm.Detection

Triplexer.In.Use

Velocity.Factor

Cable.Length

Duplexer.In.Use

In.Use

RX.Signal.Usage

Feeder.Loss

Feeder.Voltage

Antenna.Round.Trip.Delay

Id

Attributes

Id

Attributes

RTT

BTU

MHA


30/09/2008

Changes in RU10



Figure 6. LCR.Sub-System parameters for the UltraSite platform

Cell.Group

1..2

Id

Attributes

LCR.Id

LCR.Sub-System

Allowed.Carriers

WOC.In.Use

Local.Cell.Parameters

In.Use

Concept

Default.Carrier

Shutdown.Window

Shutdown.Step.Amount

Cell.Range

RACH.Capacity

In.Use

HSUPA.BB.Sharing.In.Use

LCR.Id

Attributes

WCEL

1..12

1..12

WSP.Id

1..18

HSUPA.BB.Minumum.Users

HSUPA.BB.Decoding.Capacity

Expiration.Time

Intelligent.Shutdown.Timeout

TRX.Id

1.. 8

Carrier

1..4

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



Figure 7. RF.Cabling.Definitions parameters for the UltraSite platform

Internal WBTS parameters

The following parameters are defined by the BTS Site Manager:

. Allowed.Carriers

. BTS.Manager.Specific.Parameters

. BTSManager.Version

. Cabinet

RF.Cabling.Definitions

TX.Cabling

In.Use

External.Gain

TX.Cable

1..36

RX.Cabling RX.Cable

1..24

Id

Attributes

InputPort

Attributes

WIC.IdPort

Attributes

WTR.IdPort

Attributes

In.Use

Id

Attributes

WIC.IdPort

Attributes

WTR.IdPort

Attributes

WPA.Id

Output


30/09/2008

Changes in RU10



. Commissioning.History

. Commissioning.Mode

. Commissioning.Type

. File.Creation.Date

. MHA.Alarm.Detection

. Previous.File.Version

. PSM.Alarms

. Time.Stamp

. Type (Cabinet)

9.6.4 WBTS commissioning parameter structure for Flexi WCDMA BTS

The following figures show the commissioning parameter structure in theWN5.0 software release for the Flexi WCDMA BTS.

Figure 8. Main level commissioning parameter structure for the FlexiBTSplatform

WBTS

General.Parameters

WBTS.Commissioning.Configur...

Non.LCR.Sub-Systems

LCR.Sub-System


BS.Configuration.Identifier

Time.Zone


File.Author

File.Creation.Date

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



Figure 9. LCR.Sub-System parameters for the FlexiBTS platform

Cell.Group

1..4

Id

Attributes

LCR.Id

LCR.Sub-System

Allowed.Carriers

Max.Carrier.Power

Local.Cell.Parameters

In.Use

Default.Carrier

Shutdown.Window

Shutdown.Step.Amount

Cell.Range

RACH.Capacity

In.Use

HSUPA.BB.Sharing.In.Use

LCR.Id

Attributes

WCEL

1..12

1..6

HSUPA.BB.Minumum.Users

HSUPA.BB.Decoding.Capacity

Expiration.Time

Intelligent.Shutdown.Timeout

FR.Ant.Id

1.. 8

Carrier

1..4

BB.Capacity.Requested.Access

BB.Capacity.Dedicated.Access

Cell.Group.Name


30/09/2008

Changes in RU10



Figure 10. Non.LCR.Sub-System parameters for the FlexiBTS platform

Cabinet

Non.LCR.Sub-Systems

External.Alarm.Sub-System

Site

1..4Type

Id

Attributes

Antenna.Sub-System

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



Figure 11. Site parameters for the FlexiBTS platform

Module.Locations

Serial.Number

VersionSite

Intelligent.Shutdown.In.Use

WBTS.Identification Name

RNC.Type


Location

0.. 8Module

Attributes

Passive.Units Unit

0..100

Name

Comment

Product.Code

GPS.In.Use

Ext.2M048.Clk.In.Use

Iub.Delay.Maximum.Threshold

Iub.Delay.Middle.Threshold

Iub.Delay.Minimum.Threshold

Happy.Bit.Ping.Filter.In.Use

Iub.Clk.In.Use

Happy.Bit.UPH.Threshold

QOS.Scheduling SPI.Class

Id

CC.Policy

Weight


30/09/2008

Changes in RU10



Figure 12. External.Alarm.Sub-System parameters for the FlexiBTS platform


External.Control.Output.Signals

0..6 In.Use

Initial.State

Description

Line

Id

Attributes

0..26

In.UseLine

Polarity

Severity

Id

Attributes

Mains.Power.Alarm.IdNumberOfLines

Attributes

External.Alarm.Sub_System

Description

Module

Attributes

Module

Attributes

DN70515054Issue 1-0 en draft30/09/2008


Parameter changes



Figure 13. Antenna.Sub-System parameters for the FlexiBTS platform (firstpart)

Antenna

1..18

Id

Attributes

Antenna.Sub_System

WMH.Connector

Uplink.Delay

MHA.Type

Serial.Number

Product.Code

In.Use

MHA.Gain

Downlink.Delay

MHA.Alarm.Detection

In.Use

Total.Delay

Triplexer.In.Use

Velocity.Factor

Cable.Length

Diplexer

In.Use

Feeder.Loss

Feeder.Voltage

Antenna.Round.Trip.Delay

Id

Attributes

RTT

MHA

1.. 8

Alarm.Threshold.Level

Connection

Scanned.Antenna.Interface

Active

LHA.Number

PHS.Filter

In.Use

Total.Delay

Diplexer.Loss

Diplexer.Amount

Diplexer.Type

...


30/09/2008

Changes in RU10



...

Parameter changes

Change in RU10

Documents

Transcript of Change in RU10