bsplcml

Nokia Siemens Networks GSM/EDGE BSS, rel. RG10(BSS), operating documentation, issue 04

Reference

BTSplus mainline commands at the Flexi BSC product family

DN0933412 Issue 01

2DN0933412 Issue 01

BTSplus mainline commands at the Flexi BSC productfamily

Id:0900d805805d062b

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

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

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

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

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

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

Copyright © Nokia Siemens Networks 2009. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN0933412 Issue 013


Id:0900d805805d062b

Table of ContentsThis document has 749 pages.

Summary of changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.1.1 Structure of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.1.2 Structure of the commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.1.3 Ranges for the relative number of the BTSE objects. . . . . . . . . . . . . . . 221.1.4 Command layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.2 Graphical user interface (GUI) representation of the LMT Evolution. . . 271.2.1 Start LMT Evolution window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.2.2 LMT Evolution windows for GET, CREATE, SET, ..., commands . . . . . 301.3 Command tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.3.1 Command tree for HW objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.3.2 Alphabetical list of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2 Objects and commands in alphabetical order . . . . . . . . . . . . . . . . . . . . 48

ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49CREATE ACDCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49DELETE ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51GET ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52GETTEST ACDCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54LOCK ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55PERFTEST ACDCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57STOPTEST ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61UNLOCK ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64CREATE ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64DELETE ACT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66GET ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67GETTEST ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69LOCK ACT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70PERFTEST ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72STOPTEST ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76UNLOCK ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79CREATE BATTERY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79DELETE BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81GET BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82GETTEST BATTERY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84LOCK BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86PERFTEST BATTERY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87STOPTEST BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91UNLOCK BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4DN0933412 Issue 01


Id:0900d805805d062b

BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95CREATE BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95DELETE BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98GET BCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99GETRELATIONSHIP BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101GETTEST BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103GETWIRINGRX BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104GETWIRINGTX BCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106LOCK BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108PERFTEST BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109SET BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113SETWIRINGRX BCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115SETWIRINGTX BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117STOPTEST BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119UNLOCK BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123CREATE BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123DELETE BPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126GET BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127LOCK BPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129SET BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131UNLOCK BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135GET BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135GET BTS TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143DELETE BTSEP DBFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143FORMAT BTSEP FLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144GET BTSEP NOSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145GET BTSEP SWL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148GET ACTIVEALARMS BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149PERFTEST BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152PING BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156REQCURSTASYN BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157SET BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157STOPTEST BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

BTSETEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161GET BTSETEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163ACTIVATE BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163ACTIVATE_DELAYED BTSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165CONNBSC BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165DISCBSC BTSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167FWUPGRADE BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168GET BTSM NOSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

DN0933412 Issue 015


Id:0900d805805d062b

GET BTSM OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171GET BTSM SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172LOCKREQUEST BTSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174SET BTSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175SHUTDOWN BTSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176UNLOCKREQUEST BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179CREATE CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179DELETE CESPW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181GET CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182LOCK CESPW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184SET CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185UNLOCK CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188CREATE CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188DELETE CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189GET CESTUNNEL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190LOCK CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192SET CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193UNLOCK CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

CHAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196GET CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198CREATE COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198DELETE COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200GET COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201GETRELATIONSHIP COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203GETTEST COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204LOCK COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206PERFTEST COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207SET COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211STOPTEST COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212SWITCH COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214UNLOCK COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

COBAETHINTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217GET COBAETHINTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217LOCK COBAETHINTF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218SET COBAETHINTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219UNLOCK COBAETHINTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

COSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221CREATE COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221DELETE COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222GET COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224GETTEST COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225LOCK COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

6DN0933412 Issue 01


Id:0900d805805d062b

PERFTEST COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229STOPTEST COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233UNLOCK COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

CU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236CREATE CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236DELETE CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237GET CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239GET CU FWID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241GET CU WIRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242GETTEST CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243LOCK CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245PERFTEST CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246SET CU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250STOPTEST CU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251UNLOCK CU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

DIDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255CREATE DIDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255DELETE DIDCTMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256GET DIDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258GETTEST DIDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259LOCK DIDCTMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261PERFTEST DIDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263STOPTEST DIDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266UNLOCK DIDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270CREATE DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270DELETE DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272GET DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274GETTEST DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275LOCK DILNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277PERFTEST DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279SET DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282STOPTEST DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284UNLOCK DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287DELETE DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287GET DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288GETTEST DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289LOCK DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290PERFTEST DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291STOPTEST DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291UNLOCK DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294CREATE DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294DELETE DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

DN0933412 Issue 017


Id:0900d805805d062b

GET DUDCTMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297GETTEST DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298LOCK DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300PERFTEST DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302STOPTEST DUDCTMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305UNLOCK DUDCTMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

DULNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309CREATE DULNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309DELETE DULNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311GET DULNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313GETTEST DULNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315LOCK DULNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316PERFTEST DULNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318SET DULNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322STOPTEST DULNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323UNLOCK DULNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

DUVSWR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327CREATE DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327DELETE DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329GET DUVSWR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330GETTEST DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332LOCK DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334PERFTEST DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335SET DUVSWR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339STOPTEST DUVSWR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341UNLOCK DUVSWR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

ENVABTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344CREATE ENVABTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344DELETE ENVABTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348GET ENVABTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349LOCK ENVABTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351SET ENVABTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353UNLOCK ENVABTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

ETHCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356CREATE ETHCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356DELETE ETHCON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357GET ETHCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358LOCK ETHCON. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359SET ETHCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360UNLOCK ETHCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

ETHPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363CREATE ETHPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363DELETE ETHPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364GET ETHPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365LOCK ETHPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

8DN0933412 Issue 01


Id:0900d805805d062b

SET ETHPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367UNLOCK ETHPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

F6DCTMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370CREATE F6DCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370DELETE F6DCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371GET F6DCTMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372GETTEST F6DCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373LOCK F6DCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374PERFTEST F6DCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375STOPTEST F6DCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376UNLOCK F6DCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

F6LNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379CREATE F6LNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379DELETE F6LNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380GET F6LNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381GETTEST F6LNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383LOCK F6LNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384PERFTEST F6LNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385SET F6LNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386STOPTEST F6LNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387UNLOCK F6LNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388

F6TNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390CREATE F6TNFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390DELETE F6TNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391GET F6TNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392GETTEST F6TNFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393LOCK F6TNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394PERFTEST F6TNFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395STOPTEST F6TNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396UNLOCK F6TNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

F6VSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398CREATE F6VSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398DELETE F6VSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399GET F6VSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400GETTEST F6VSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401LOCK F6VSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402PERFTEST F6VSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403SET F6VSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404STOPTEST F6VSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405UNLOCK F6VSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408CREATE FANP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408DELETE FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410GET FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411GETTEST FANP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

DN0933412 Issue 019


Id:0900d805805d062b

LOCK FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414PERFTEST FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416STOPTEST FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420UNLOCK FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423CREATE FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423DELETE FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425GET FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427GET FCUMAIN FWID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428GET FCUMAIN WIRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429GETTEST FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430LOCK FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432PERFTEST FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433SET FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437STOPTEST FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438UNLOCK FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442CREATE FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442DELETE FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444GET FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445GETTEST FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447LOCK FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448PERFTEST FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450SET FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454STOPTEST FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455UNLOCK FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456

FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458CREATE FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458DELETE FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460GET FTNFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461GETTEST FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463LOCK FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464PERFTEST FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466STOPTEST FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470UNLOCK FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473CREATE FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473DELETE FVSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475GET FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476GETTEST FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477LOCK FVSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479PERFTEST FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481STOPTEST FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484UNLOCK FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488

10DN0933412 Issue 01


Id:0900d805805d062b

CREATE LAPDLE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488DELETE LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490GET LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493CREATE RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493DELETE RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495GET RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496LOCK RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498SET RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499UNLOCK RACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

REMINV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503DNLIDFD REMINV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503UPLLIDF REMINV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504

SOFTWARE-MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506DNLALLEXE SOFTWARE-MANAGEMENT. . . . . . . . . . . . . . . . . . . . . 506UPLBTSLOG SOFTWARE-MANAGEMENT . . . . . . . . . . . . . . . . . . . . 507

SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510GET SYNCBTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510GETTEST SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511LOCK SYNCBTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513PERFTEST SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515SET SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518STOPTEST SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520UNLOCK SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521

TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523CREATE TMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523DELETE TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525GET TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526GET TMA PRODUCTINFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527GETTEST TMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529LOCK TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530PERFTEST TMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532STOPTEST TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536UNLOCK TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

TRX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539GET TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539GETRELATIONSHIP TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

XCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543CREATE XCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543DELETE XCONNECT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545GET XCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546LOCK XCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550SET XCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552UNLOCK XCONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

DN0933412 Issue 0111


Id:0900d805805d062b

3 Parameters/attributes in alphabetical order . . . . . . . . . . . . . . . . . . . . . 555

a. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556ABISCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556ABISLKSAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556ABISTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557ACBQPFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557ACBQPMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558ACEFLFF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558ACFERMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559ACLNKTYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559ACMAXEFLDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560ACMINEFLDMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560ACONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561ACPER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561ACTVINC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562ALGNSTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562ALIGCOBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562ALRMCLET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563ALRMCOUNTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563ALRMPERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564ALRMSEVXXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564ALRMT1/2/3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565ALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566AMRLKAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566AMRLKATWFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567ANT<x>CELLNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568ANT<x>SCNRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569ANT<x>WDRX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569ANT<x>WDTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572ANTB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574ANTHOPHW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574ANTHOPMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575ANTHOPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575ANTHOPST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575ANTMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576ANTSN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576ARFACCHACMDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576ASCICIPH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577ASEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578AST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578ASTRING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579ASUBLKSAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579AVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

b. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581BATTCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581BCCHFREQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581

12DN0933412 Issue 01


Id:0900d805805d062b

BCOMTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582BCPBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583BERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583BMWD<x>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584BND<x> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584BSIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585BSWVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585BTSID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586BTSISHOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586BTSOBJID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587BURNOFFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588CCPBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588CELLNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588CELLTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589CHIDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589CHTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590CLKACC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592COMBMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592CUCONF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593CUWIRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595DESTDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595DLTESTFREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595DMACFHSYID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595DMCFWID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596DTMHOMTIMER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596DYNPOOLINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596DYNTRACGRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599

e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600EAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600EANTHOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600EAUTONEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600EAUTOREC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601EEOTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601EEXCDIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602EFCUSUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602EFLWCTRL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603EINTSITSYN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604EMT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604EMT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604ENTRIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605EQUPOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605ERFACCHALPDMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606ERFACCHCMDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608ERSACCHDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610

DN0933412 Issue 0113


Id:0900d805805d062b

ERSACCHUL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615ETOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620ETXDIVTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622EVTYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623EXCDIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623EXTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624

f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625F6FWID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625FACCHQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625FACHBT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625FBAND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626FCUMAINWIRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626FCUMODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628FILEFWV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628FILEID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628FILESWV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630FILETYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631FPGAFWVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631FRANOFFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632FWVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632

g. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633GN<x> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633GNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633GNADB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634GNR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635GSMTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635GTWADRV4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637HOPMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637HSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637

i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638INSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638INSID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638INTAVEPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638INTCLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639INTINF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639INTLVBND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639IPADR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641L1CTRLTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641L1PT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641L1RAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642LAPDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642LAPDOVLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643

14DN0933412 Issue 01


Id:0900d805805d062b

LAPDOVLTH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644LCONF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645LIMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645LMTLSESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646LMTLTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647LMTUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647LMTUNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648LNAMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648LNAMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649LNAPRED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649LOCALADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652LOCLUDP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652LOCNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652LOSPKTTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653LPDLMSAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653LRU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653LSIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

m. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656MACADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656MAIO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656MAXGN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656MAXPDV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657MINGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657MOBALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657MOEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659MONPRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659MORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660MPHERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661MPTSLXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661MRSYNCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662MSDISTBEHAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663MSTXPMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663MSTXPMAXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664MTLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665MTYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667NEPTTREP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667NTWTYPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667NTWTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667NY1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669NY2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

o . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670OMLAPDRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670OST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670OUTPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671OUTPUTPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

DN0933412 Issue 0115


Id:0900d805805d062b

OVERWRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671OVPTINS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

p. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673PCCCHLDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673PEERADDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673PEERUDPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673PKTLAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674PNGF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674PNGPKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675PNOFACCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675PRDINF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675PRDIRECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676PRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676PSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677PUSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677PWNAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678PWROUT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678PWRRED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679

r . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680RACHBT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680RACHLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680RADIOMG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680RADIOMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681RADIUSEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681RELEQUIPOBJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682RELFUNCOBJ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682REPTYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684RFRSINDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685RSACCHRXLDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685RSACCHRXLUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685RSACCHTODL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686RSACCHTOUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686RXBMAXF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686RXBMINF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687RXDIVSV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687RXLEVADJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687RXLEVADJN1D1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688RXSIGLEVADJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688RXSIGLEVADJC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689RXSWCURSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690SALUNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690SBPRT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690SCELLNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690SCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691SCLPRIOLST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692

16DN0933412 Issue 01


Id:0900d805805d062b

SEGMENTID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693SFPSERID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694SHLAPDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694SLOTNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695SRADIUSEXT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695SRCDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696SRCPATH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696STATIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696STDBYST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697SUBUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697SWBCAPABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697SWBSERVSTATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698SWLCFID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698SWLCVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699SWLDINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700SWLDSAF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701SWLDST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701SYNCHRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702SYNCSRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702SYNCSTAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703SYSID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705T200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705T3105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705T3115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706T3151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706TAADJ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706TCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707TCCCHLDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707TDMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708TEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709TESTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709TESTMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710TESTNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715TESTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715TESTPWRRED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716TESTST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716TEXT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716TIMEDELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717TNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717TNFTARGF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717TRXAREA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718TRXCPBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719TRXFREQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719TRXMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720TSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720TSLPOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

DN0933412 Issue 0117


Id:0900d805805d062b

TSYNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722TSYNCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722TSYNCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723TSYNCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723TTRAU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724TUPLREP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724TXBMAXF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725TXBMINF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725TXDIVTSEXCPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725TXDIVTSPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726TXLEVADJ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726TXSIGLEVADJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727TXSIGLEVADJC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727TYPOFETH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727TYPRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728

v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730VENDNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730VGSCULFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730VLANID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731VSWRTDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731

w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733WDDUVSWR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733WDFTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735WDLNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737

4 Nack causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

5 Appendix: values for ERFACCHALPDMF, ERFACCHCMDF, ERSACCH-DL, ERSACCHUL and ETOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

6 Appendix B: commands available only in remote mode . . . . . . . . . . . 7486.1 REQCURSTASYN BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7486.2 GET ENVABTSESUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748

18DN0933412 Issue 01


Id:0900d805805d062b

List of FiguresFigure 1 BTSplus mainline (BS240) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 2 BTSplus mainline: tree view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 3 BTSplus mainline (BS240): graphic view . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 4 BTSplus mainline tree view with list of command . . . . . . . . . . . . . . . . . . 30Figure 5 BTSplus mainline: CREATE ... ACDCP command (example) . . . . . . . . 31Figure 6 BTSplus mainline: SET ... COBA command (example) . . . . . . . . . . . . . 31Figure 7 Command viewer window: CREATE ... BPORT command (example) . . 32Figure 8 Command viewer window: SET ... COBA command (example) . . . . . . . 32Figure 9 Example of BS4x, BS240, BS241, BS240XL, BS240XS/288, BS82 eMicro

main tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

DN0933412 Issue 0119


Summary of changes

Id:0900d805805d0612

Summary of changes

Issue 01 for release RG10(BSS)

Issue Date Summary

01 07/2009 First edition for release RG10(BSS)

20DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

1 Introduction

1.1 GeneralThis document describes the objects, attributes and related commands necessary to manage the BTSplus mainline NEs.

The way to submit any command is represented by the LMT Evolution tool.

The LMT Evolution, that is the interface between the user and the NE, can manage dif-ferent BTSplus types. For instance, the LMT Evolution is able to recognize and then to visualize the command trees related to the following NEs: • BTSplus mainline (BS-240/BS-241, BS-240 II/241 II/241 II B, BS-240XL, BS-240XL

II, BS-40/41, BS-40 II, BS-82II) • BTSplus basic (BS-240XS, BS-288) • BTSplus eMicro (BS-82)

The LMT Evolution tool is the application commonly used to configure and maintain the GSM network through a set of functions and procedures tailored to operate in a local context. Refer to “Operating guidelines: LMT Evolution”.

Local context means that the LMT Evolution is physically connected to the Network Element through (refer to Figure 1) an interface based on proprietary protocols (HALCA and DLHC).

Anyway, out of the local context, LMT Evolution does not have an overall control on the GSM network and, consequently, available functions are limited to those allowed by local constraints.

The purpose of LMT Evolution is to make Operation and Maintenance easy and to provide all information about the state of an NE.

g Position of COBAs and COSAs. COBA/COSA 0 will be found always on the left side of the rack and COBA/COSA 1 on the right side of the rack.

DN0933412 Issue 0121


Introduction

Id:0900d805805b11a6

Figure 1 BTSplus mainline (BS240)

1.1.1 Structure of the manualThe manual is divided into five main sections:

1. Section 1 provides general information about command structure and LMT Evolu-tion operations

2. Section 2 describes objects and commands, listed in alphabetical order3. Section 3 describes the parameters of the commands, listed in alphabetical order.

Additionally there is the information in which commands the parameter is used4. Section 4 lists the NACK causes5. Section 5 lists the values for some parameters6. Section 6 lists the values for some commands available only in remote mode

There is the possibility to jump by clicking on the selected item (reference to the param-eter description or to the GUI representation in section 2; reference to the commands in section 3 to the requested information.

In the command representation (section 2) the parameters/attributes in brackets are optional parameters.

22DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

1.1.2 Structure of the commandsBoth generic commands which can be obtained through selections from the LMT Evo-lution tree and commands which are created by the operator using the CLI interface must use the following syntax:1. Action object [object]:NAME=object:n[/object:n],attribute=value[-value] [,attri-

bute=value];2. Action object :NAME=object:n[/object:n],attribute=value[&value] [,attribute=value];3. Action object [object]:NAME=object:n[/object:n],[REQATTL]=attribute [&attribute];4. Action object [object]:NAME=object:n[/object:n];

g The syntax rules shown in example 2. are used only for GET commands.

where:

"Action" specifies the command that is being executed and that belongs to a list of func-tions applicable to the BTSE system (for example: "CREATE", "DELETE", "SET", etc).

“object” represents the hardware or logical identifier that must be submitted to the command (for example: "RACK", "CU", "BTSM", etc).

“[object]” logical identifier that must be submitted to the commands DELETE BTSEP (for example: "DBFILE") FORMAT BTSEP (for example: "FLASH"), GET BTSEP (for example: "NOSWL", "SWL") or GET CU (for example: "ESN", "NOESN").

"name" specifies the relative number (for example: ACDCP:n n=0, CU:n n=0..11, etc. See table below). The LMT Evolution CLI allows “*” or “&” instead of a simple number for a object instance (for example: CU:* (all), CU:0&2&3 (0,2,3) or CU:0&&3 (0,1,2,3).

"attribute" is the acronym of the real attribute of an object (for example: LNAPRED= Low Noise Amplifier Predecessor of DULNA, etc.).

"value" represent the value of the attribute (or the values of its fields). It is possible to input a value not just using the default data type (usually decimal) but also to input the data e.g. as hex value or as binary value.

1.1.3 Ranges for the relative number of the BTSE objectsThe ranges shown on the LMT Evolution for the relative numbers of the managed objects depends on the type of hardware to which the LMT Evolution itself is connected. The following tables show the ranges allowed for the managed objects of the different type of BTSE racks (i.e. base, extension, service) relevant to BTSplus Mainline.

BS240 /BS241 BS240SR BS241SR

BS240XL BS240XLSR BS4x

ACDCP - 0..1 - 0..1 0

ACT 0 0 0 0 0

BATTERY - 0..3 - 0..3 0..1

BCOM 0..1 - 0..1 - -

BPORT 0..7 - 0..7 - 0..7

BTS 0..11 - 0..11 - 0..3

BTSEP 0 - 0 - 0

BTSM 0 - 0 - 0

DN0933412 Issue 0123


Introduction

Id:0900d805805b11a6

g *) ENVABTSE object instances 0..56 exist only for rack 0, for other rack instances the range is 0..8.

g **) ENVABTSE object instances 0 and 1 are not supported by BS240XL, BS240XLSR.

g ***) COSA, FANP, TMA: no processor

g The LMU function is no longer supported. Do not use any LMU commands.

CHAN 0..7 - 0..7 - 0..7

COBA 0..1 - 0..1 - 0..1

COSA***) 0..1 - 0..1 - 0..1

CU 0..7 - 0..11 - 0..3

DIDCTMA 0..3 - 0..7 - 0..1

DILNA 0..3 - 0..7 - 0..1

DUAMCO 0..3 - 0..5 - 0..1

DUDCTMA 0..7 - 0..11 - 0..3

DULNA 0..7 - 0..11 - 0..3

DUVSWR 0..7 - 0..11 - 0..3

ENVABTSE 0..56 *) 0..8 0..56 *) **) 0..8 **) 0..56

ETHCON 0 0 0 0 0

F6DCTMA 0..3 - 0..3 - -

F6LNA 0..3 - 0..3 - -

F6TNFP 0..11 - 0..11 - -

F6VSWRP 0..1 - 0..1 - -

FANP***) 0..5 0..5 0..7 0..7 0..5

FCUMAIN 0..7 - 0..11 - 0..3

FCUTR 0..15 - 0..23 - 0..7

FTNFP 0..7 - 0..7 - 0..3

FVSWRP 0..3 - 0..3 - 0..1

LAPDLE 0..10 0..10 0..10 0..10 0..10

LMU 0 - 0 - -

RACK 0..7 4..7 0, 1, 3..7 3..7 0, 4..7

BTSETEST 1..255 1..255 1..255 1..255 1..255

TMA***) 0..11 - 0..15 - 0..5

SYNCBTSE 0 0 0 0 0

TRX 0..23 - 0..23 - 0..3

XCONNECT 0..7 - 0..7 - 0..7

BS40II BS82II

ACDCP - 0

24DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

ACT 0 0

BATTERY - 0

BCOM - -

BPORT 0..7 0..3 (note)

BTS 0..3 0..5

BTSEP 0 0

BTSM 0 0

CHAN 0..7 0..7

COBA 0..1 0

COSA 0..1 -

CU 0..3 0..1

DIDCTMA - 0..1

DILNA - 0..1

DUDCTMA 0..7 0..1

DULNA 0..7 0..1

DUVSWR 0..7 0..1

ENVABTSE 0..56 *) 0..5

ETHCON 0 0

F6DCTMA - -

F6LNA - -

F6TNFP - -

F6VSWRP - -

FANP 0..4 0

FCUMAIN 0..3 0..1

FCUTR 0..7 0..3

FCUMAIN 0..3 0..1

FCUTR 0..7 0..3

FTNFP 0..7 -

FVSWRP 0..3 -

LAPDLE 0..10 0..10 (note)

LMU - -

RACK 0, 4..7 0..2

BTSETEST 1..255 1..255

TMA 0..7 0..3

SYNCBTSE 0 0

TRX 0..3 0..5

DN0933412 Issue 0125


Introduction

Id:0900d805805b11a6

g *) ENVABTSE object instances 0..56 exist only for rack 0, for other rack instances the range is 0..8.

g BS82II BPORT object: range 0..3 is supported only if COBA4P12 is installed, in all other cases the range is 0..1.

g BS82II LAPDLE object: in case of COBA4P12 the BTSE will reject the creation of object instances 5..10.

g BS82II XCONNECT object: instances #2 and #3 are supported only if COBA4P12 is installed, in all other cases only instances 0 and 1 are allowed.

g The LMU function is no longer supported. Do not use any LMU commands.

1.1.4 Command layoutThe first information given for each command is the phase, or phases, within which the command can be entered. Then, subsequent selections are shown which are required to get the command starting from the LMT Evolution Tree.

The command is specified with its syntax and it is followed by the individual fields used to explain the functions of the command itself.

Command Tree:The command tree shows the way to get the command and a hint to a GUI example in section 1.

Applicability:This field shows the working phases and the user profile which allow the execution of the command. The user profile visibility level is associated with a user identification "user_id" and password. Four user profiles visibility level are provided:

Each profile gives the user different access levels to the system features and the higher is the level the higher is the number of operations which can be performed.

g For “User_id” and Password contact your local service organization.

Command Description:This field explains the function of the command transmitted by the LMT Evolution to the BTSE (when and why it is used, for which operation task).

Long Names:This part shows (for an overview) the abbreviations of the parameters/attributes used in the command and its corresponding long names.

System Responses:

XCONNECT 0..7 0..3 (note)

0 ReadOnly

1 Command Access

2 ReadWrite

3 Super User

26DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

They are response messages sent as acknowledgment for completion of input commands or they contain information requested by the user. The typical structure of the response messages contains: the date and time, the command line, the system response. The response messages can be either normal (successful) or error mes-sages. In such a case they contain the reason for the failure.

Short system messages such as: indication of system loading/downloading functions in progress, are also reported as information to the LMT Evolution.

Application Guidelines:These are warnings given when using this command or information related to the envi-ronment in which the command is submitted.

Example of Command Execution:This is an example on how to enter the command with its parameters and their relevant values.

DN0933412 Issue 0127


Introduction

Id:0900d805805b11a6

1.2 Graphical user interface (GUI) representation of the LMT Evolutiong Reference figures: the reported figures are only for reference and could be not

aligned to the last version of LMT Evolution product.

1.2.1 Start LMT Evolution windowThe LMT Evolution tool is the graphical user interface which performs the command interaction with the Network Element. This enables the user to navigate the object con-tainment Tree View (see Figure 2) or Graphic View (see Figure 3) of the NE and to select a specific command from a list of available ones.

From the graphical point of view, the LMT Evolution Main window provides an access point to all the LMT Evolution functionality and represents an overall monitoring mode as regards the connection status information.

According to its dynamic and "adaptive" properties, the LMT Evolution Main window is displayed taking into account the connection and operating parameters that may affect the visualization of the resulting window functionalities.

The main parameters that influence the visualization of LMT Evolution main window are: • Working Context: indicates a mode in which the user is currently working with the

LMT Evolution • Network Element configuration: family, type, phase, version, etc.

By using the LMT Evolution the user can: • Acquire commands, action or scripts • Send and receive messages containing commands or responses to/from the

network element • Have script/commands translation services • Store issued commands and retrieve responses coming from the NE

28DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

Figure 2 BTSplus mainline: tree view

DN0933412 Issue 0129


Introduction

Id:0900d805805b11a6

Figure 3 BTSplus mainline (BS240): graphic view

30DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

1.2.2 LMT Evolution windows for GET, CREATE, SET, ..., commandsThe LMT Evolution is mainly used to build CREATE, SET, GET, LOCK, UNLOCK, etc. commands to be sent to the Network Element. Starting from the containment Tree View or Graphic View,you can perform the following operations: • Select the functional/equipment/software management object • Select a command from the list of commands displayed by the pop up list box (see

Figure 4)

Figure 4 BTSplus mainline tree view with list of command

The presence of ellipses (see SET ... COBA Command) following the name of the command indicates that the command could require a further configuration of the attri-butes before being submitted. In this case the Command Viewer window is opened and the user can fill in the attribute cells as desired.

If no ellipses are present (see GET COBA Command), the command does not need any further configuration and it is submitted to the network element without opening the Command Viewer window.

In case of the presence of ellipses (see CREATE ... BPORT Command in Figure 5 or SET ... COBA Command in Figure 6) the Command Viewer panel is displayed (see Figure 7 and Figure 8). The user has to perform the following operations: • Select one or more parameters and choose the appropriate values, the command is

executed after clicking on the “Submit” button • If, during the translation phase, an error is found in the command string, the

command is not sent to the N.E. In this case reenter the command following the instructions provided by the diagnostic message shown in the right middle pane.

DN0933412 Issue 0131


Introduction

Id:0900d805805b11a6

Figure 5 BTSplus mainline: CREATE ... ACDCP command (example)

Figure 6 BTSplus mainline: SET ... COBA command (example)

32DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

Figure 7 Command viewer window: CREATE ... BPORT command (example)

Figure 8 Command viewer window: SET ... COBA command (example)

For all procedures of module replacement the actions to be performed are similar. As first action, the module must be locked, replaced, tested and finally unlocked. Some modules have to be replaced without locking and for some others, the BTSEP has to be switched from phase 3 to 2.

DN0933412 Issue 0133


Introduction

Id:0900d805805b11a6

1.3 Command tree

1.3.1 Command tree for HW objects

Figure 9 Example of BS4x, BS240, BS241, BS240XL, BS240XS/288, BS82 eMicro main tree

MANAGED ELEMENTBSS-EQUIPMENT

BTSEPBPORT

LAPDLE

XCONNECT

RACK ACDCPACT

COSA

DUDCTMADULNA

BTSETESTREMINV

BSS-FUNCTIONAL

BTSM

BTSTRX

CHAN

SOFTWARE-MANAGEMENT

BATTERY

COBA

CUDIDCTMADILNA

DUVSWRENVABTSE

FCUTR

F6LNA

FANPFCUMAIN

FTNFPFVSWRPF6DTMA

F6VSWRPF6TNFP

SYNCBTSE

CESPW

COBAETHINTF

ETHPORT

CESTUNNEL

BCOM

TMALMU

DUAMCOETHCON

34DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

DN0933412 Issue 0135


Introduction

Id:0900d805805b11a6

1.3.2 Alphabetical list of commands

Managed Element Phase1 Phase2 Phase3

ACDCP

CREATE ACDCP CREATE ACDCP

DELETE ACDCP DELETE ACDCP

GET ACDCP GET ACDCP

GETTEST ACDCP GETTEST ACDCP

LOCK ACDCP LOCK ACDCP

PERFTEST ACDCP PERFTEST ACDCP

STOPTEST ACDCP STOPTEST ACDCP

UNLOCK ACDCP UNLOCK ACDCP


ACT

CREATE ACT CREATE ACT

DELETE ACT DELETE ACT

GET ACT GET ACT

GETTEST ACT GETTEST ACT

LOCK ACT LOCK ACT

PERFTEST ACT PERFTEST ACT

STOPTEST ACT STOPTEST ACT

UNLOCK ACT UNLOCK ACT


BATTERY

CREATE BATTERY CREATE BATTERY

DELETE BATTERY DELETE BATTERY

GET BATTERY GET BATTERY

GETTEST BATTERY GETTEST BATTERY

LOCK BATTERY LOCK BATTERY

PERFTEST BATTERY PERFTEST BATTERY

STOPTEST BATTERY STOPTEST BATTERY

UNLOCK BATTERY UNLOCK BATTERY


36DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

BCOM

CREATE BCOM CREATE BCOM

DELETE BCOM DELETE BCOM

GET BCOM GET BCOM

GETWIRINGRX BCOM GETWIRINGRX BCOM

GETWIRINGTX BCOM GETWIRINGTX BCOM

GETRELATIONSHIP BCOM


GETTEST BCOM GETTEST BCOM

LOCK BCOM LOCK BCOM

PERFTEST BCOM PERFTEST BCOM

SET BCOM SET BCOM

SETWIRINGRX BCOM SETWIRINGRX BCOM

SETWIRINGTX BCOM SETWIRINGTX BCOM

STOPTEST BCOM STOPTEST BCOM

UNLOCK BCOM UNLOCK BCOM


BPORT

CREATE BPORT CREATE BPORT

DELETE BPORT DELETE BPORT

GET BPORT GET BPORT

LOCK BPORT LOCK BPORT

SET BPORT SET BPORT

UNLOCK BPORT UNLOCK BPORT


BTS

GET BTS

GET BTS TIMER


BTSEP

DELETE BTSEP DBFILE

FORMAT BTSEP FLASH FORMAT BTSEP FLASH

GET BTSEP NOSWL GET BTSEP NOSWL

DN0933412 Issue 0137


Introduction

Id:0900d805805b11a6

GET BTSEP SWL GET BTSEP SWL

GETACTIVEALARMS BTSEP


PERFTEST BTSEP PERFTEST BTSEP

PING BTSEP PING BTSEP

SET BTSEP SET BTSEP

STOPTEST BTSEP STOPTEST BTSEP


BTSETEST

GET BTSETEST GET BTSETEST


BTSM

ACTIVATE BTSM ACTIVATE BTSM

ACTIVATE_DELAYED BTSM

CONNBSC BTSM

DISCBSC BTSM

FWUPGRADE BTSM FWUPGRADE BTSM

GET BTSM NOSWL GET BTSM NOSWL

GET BTSM OVERLOAD GET BTSM OVERLOAD

GET BTSM SWL GET BTSM SWL

LOCKREQUEST BTSM

SET BTSM

SHUTDOWN BTSM

UNLOCKREQUEST BTSM


CESPW

CREATE CESPW CREATE CESPW

DELETE CESPW DELETE CESPW

GET CESPW GET CESPW

LOCK CESPW LOCK CESPW

SET CESPW SET CESPW

38DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

UNLOCK CESPW UNLOCK CESPW


CESTUNNEL

CREATE CESTUNNEL

DELETE CESTUNNEL

GET CESTUNNEL GET CESTUNNEL

LOCK CESTUNNEL

SET CESTUNNEL SET CESTUNNEL

UNLOCK CESTUNNEL


CHAN

GET CHAN


COBA

CREATE COBA CREATE COBA

DELETE COBA DELETE COBA

GET COBA GET COBA

GETRELATIONSHIP COBA


GETTEST COBA GETTEST COBA

LOCK COBA LOCK COBA

PERFTEST COBA PERFTEST COBA

SET COBA SET COBA

STOPTEST COBA STOPTEST COBA

SWITCH COBA SWITCH COBA

UNLOCK COBA UNLOCK COBA


COBAETHINTF

GET COBAETHINTF GET COBAETHINTF

LOCK COBAETHINTF

SET COBAETHINTF

DN0933412 Issue 0139


Introduction

Id:0900d805805b11a6

UNLOCK COBAETHINTF


COSA

CREATE COSA CREATE COSA

DELETE COSA DELETE COSA

GET COSA GET COSA

GETTEST COSA GETTEST COSA

LOCK COSA LOCK COSA

PERFTEST COSA PERFTEST COSA

STOPTEST COSA STOPTEST COSA

UNLOCK COSA UNLOCK COSA


CU

CREATE CU CREATE CU

DELETE CU DELETE CU

GET CU GET CU

GET CU FWID GET CU FWID

GET CU WIRING GET CU WIRING

GETTEST CU GETTEST CU

LOCK CU LOCK CU

PERFTEST CU PERFTEST CU

SET CU SET CU

STOPTEST CU STOPTEST CU

UNLOCK CU UNLOCK CU


DIDCTMA

CREATE DIDCTMA CREATE DIDCTMA

DELETE DIDCTMA DELETE DIDCTMA

GET DIDCTMA GET DIDCTMA

GETTEST DIDCTMA GETTEST DIDCTMA

LOCK DIDCTMA LOCK DIDCTMA

PERFTEST DIDCTMA PERFTEST DIDCTMA

40DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

STOPTEST DIDCTMA STOPTEST DIDCTMA

UNLOCK DIDCTMA UNLOCK DIDCTMA


DILNA

CREATE DILNA CREATE DILNA

DELETE DILNA DELETE DILNA

GET DILNA GET DILNA

GETTEST DILNA GETTEST DILNA

LOCK DILNA LOCK DILNA

PERFTEST DILNA PERFTEST DILNA

SET DILNA SET DILNA

STOPTEST DILNA STOPTEST DILNA

UNLOCK DILNA UNLOCK DILNA


DUAMCO

DELETE DUAMCO DELETE DUAMCO

GET DUAMCO GET DUAMCO

GETTEST DUAMCO GETTEST DUAMCO

LOCK DUAMCO LOCK DUAMCO

PERFTEST DUAMCO PERFTEST DUAMCO

STOPTEST DUAMCO STOPTEST DUAMCO

UNLOCK DUAMCO UNLOCK DUAMCO


DUDCTMA

CREATE DUDCTMA CREATE DUDCTMA

DELETE DUDCTMA DELETE DUDCTMA

GET DUDCTMA GET DUDCTMA

GETTEST DUDCTMA GETTEST DUDCTMA

LOCK DUDCTMA LOCK DUDCTMA

PERFTEST DUDCTMA PERFTEST DUDCTMA

STOPTEST DUDCTMA STOPTEST DUDCTMA

UNLOCK DUDCTMA UNLOCK DUDCTMA

DN0933412 Issue 0141


Introduction

Id:0900d805805b11a6


DULNA

CREATE DULNA CREATE DULNA

DELETE DULNA DELETE DULNA

GET DULNA GET DULNA

GETTEST DULNA GETTEST DULNA

LOCK DULNA LOCK DULNA

PERFTEST DULNA PERFTEST DULNA

SET DULNA SET DULNA

STOPTEST DULNA STOPTEST DULNA

UNLOCK DULNA UNLOCK DULNA


DUVSWR

CREATE DUVSWR CREATE DUVSWR

DELETE DUVSWR DELETE DUVSWR

GET DUVSWR GET DUVSWR

GETTEST DUVSWR GETTEST DUVSWR

LOCK DUVSWR LOCK DUVSWR

PERFTEST DUVSWR PERFTEST DUVSWR

SET DUVSWR SET DUVSWR

STOPTEST DUVSWR STOPTEST DUVSWR

UNLOCK DUVSWR UNLOCK DUVSWR


ENVABTSE

CREATE ENVABTSE CREATE ENVABTSE

DELETE ENVABTSE DELETE ENVABTSE

GET ENVABTSE GET ENVABTSE

LOCK ENVABTSE LOCK ENVABTSE

SET ENVABTSE SET ENVABTSE

UNLOCK ENVABTSE UNLOCK ENVABTSE


ETHCON

42DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

CREATE ETHCON

DELETE ETHCON

GET ETHCON GET ETHCON

LOCK ETHCON

SET ETHCON SET ETHCON

UNLOCK ETHCON


ETHPORT

CREATE ETHPORT CREATE ETHPORT

DELETE ETHPORT DELETE ETHPORT

GET ETHPORT GET ETHPORT

LOCK ETHPORT LOCK ETHPORT

SET ETHPORT SET ETHPORT

UNLOCK ETHPORT UNLOCK ETHPORT


F6DCTMA

CREATE F6DCTMA CREATE F6DCTMA

DELETE F6DCTMA DELETE F6DCTMA

GET F6DCTMA GET F6DCTMA

GETTEST F6DCTMA GETTEST F6DCTMA

LOCK F6DCTMA LOCK F6DCTMA

PERFTEST F6DCTMA PERFTEST F6DCTMA

STOPTEST F6DCTMA STOPTEST F6DCTMA

UNLOCK F6DCTMA UNLOCK F6DCTMA


F6LNA

CREATE F6LNA CREATE F6LNA

DELETE F6LNA DELETE F6LNA

GET F6LNA GET F6LNA

GETTEST F6LNA GETTEST F6LNA

LOCK F6LNA LOCK F6LNA

PERFTEST F6LNA PERFTEST F6LNA

DN0933412 Issue 0143


Introduction

Id:0900d805805b11a6

SET F6LNA SET F6LNA

STOPTEST F6LNA STOPTEST F6LNA

UNLOCK F6LNA UNLOCK F6LNA


F6TNFP

CREATE F6TNFP CREATE F6TNFP

DELETE F6TNFP DELETE F6TNFP

GET F6TNFP GET F6TNFP

GETTEST F6TNFP GETTEST F6TNFP

LOCK F6TNFP LOCK F6TNFP

PERFTEST F6TNFP PERFTEST F6TNFP

STOPTEST F6TNFP STOPTEST F6TNFP

UNLOCK F6TNFP UNLOCK F6TNFP


F6VSWRP

CREATE F6VSWRP CREATE F6VSWRP

DELETE F6VSWRP DELETE F6VSWRP

GET F6VSWRP GET F6VSWRP

GETTEST F6VSWRP GETTEST F6VSWRP

LOCK F6VSWRP LOCK F6VSWRP

PERFTEST F6VSWRP PERFTEST F6VSWRP

SET F6VSWRP SET F6VSWRP

STOPTEST F6VSWRP STOPTEST F6VSWRP

UNLOCK F6VSWRP UNLOCK F6VSWRP


FANP

CREATE FANP CREATE FANP

DELETE FANP DELETE FANP

GET FANP GET FANP

GETTEST FANP GETTEST FANP

LOCK FANP LOCK FANP

PERFTEST FANP PERFTEST FANP

44DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

STOPTEST FANP STOPTEST FANP

UNLOCK FANP UNLOCK FANP


FCUMAIN

CREATE FCUMAIN CREATE FCUMAIN

DELETE FCUMAIN DELETE FCUMAIN

GET FCUMAIN GET FCUMAIN

GET FCUMAIN FWID GET FCUMAIN FWID

GET FCUMAIN WIRING GET FCUMAIN WIRING

GETTEST FCUMAIN GETTEST FCUMAIN

LOCK FCUMAIN LOCK FCUMAIN

PERFTEST FCUMAIN PERFTEST FCUMAIN

SET FCUMAIN SET FCUMAIN

STOPTEST FCUMAIN STOPTEST FCUMAIN

UNLOCK FCUMAIN UNLOCK FCUMAIN


FCUTR

CREATE FCUTR CREATE FCUTR

DELETE FCUTR DELETE FCUTR

GET FCUTR GET FCUTR

GETTEST FCUTR GETTEST FCUTR

LOCK FCUTR LOCK FCUTR

PERFTEST FCUTR PERFTEST FCUTR

SET FCUTR SET FCUTR

STOPTEST FCUTR STOPTEST FCUTR

UNLOCK FCUTR UNLOCK FCUTR


FTNFP

CREATE FTNFP CREATE FTNFP

DELETE FTNFP DELETE FTNFP

GET FTNFP GET FTNFP

GETTEST FTNFP GETTEST FTNFP

DN0933412 Issue 0145


Introduction

Id:0900d805805b11a6

LOCK FTNFP LOCK FTNFP

PERFTEST FTNFP PERFTEST FTNFP

STOPTEST FTNFP STOPTEST FTNFP

UNLOCK FTNFP UNLOCK FTNFP


FVSWRP

CREATE FVSWRP CREATE FVSWRP

DELETE FVSWRP DELETE FVSWRP

GET FVSWRP GET FVSWRP

GETTEST FVSWRP GETTEST FVSWRP

LOCK FVSWRP LOCK FVSWRP

PERFTEST FVSWRP PERFTEST FVSWRP

STOPTEST FVSWRP STOPTEST FVSWRP

UNLOCK FVSWRP UNLOCK FVSWRP


LAPDLE

CREATE LAPDLE CREATE LAPDLE

DELETE LAPDLE DELETE LAPDLE

GET LAPDLE GET LAPDLE


LMU The LMU function is no longer supported. Please do not use any LMU commands.


RACK

CREATE RACK CREATE RACK

DELETE RACK DELETE RACK

GET RACK GET RACK

LOCK RACK LOCK RACK

SET RACK

UNLOCK RACK UNLOCK RACK


46DN0933412 Issue 01


Id:0900d805805b11a6

Introduction

REMINV

DNLIDFD REMINV DNLIDFD REMINV

UPLLIDF REMINV UPLLIDF REMINV UPLLIDF REMINV


SOFTWARE-MAN-AGEMENT

DNLALLEXE SOFTWARE-MANAGE-MENT


UPLBTSLOG SOFTWARE-MANAGE-MENT



SYNCBTSE

GET SYNCBTSE GET SYNCBTSE

GETTEST SYNCBTSE GETTEST SYNCBTSE

LOCK SYNCBTSE LOCK SYNCBTSE

PERFTEST SYNCBTSE PERFTEST SYNCBTSE

SET SYNCBTSE SET SYNCBTSE

STOPTEST SYNCBTSE STOPTEST SYNCBTSE

UNLOCK SYNCBTSE UNLOCK SYNCBTSE


TMA

CREATE TMA CREATE TMA

DELETE TMA DELETE TMA

GET TMA GET TMA

GET TMA PRODUCT-INFO

GET TMA PRODUCT-INFO

GETTEST TMA GETTEST TMA

LOCK TMA LOCK TMA

PERFTEST TMA PERFTEST TMA

STOPTEST TMA STOPTEST TMA

UNLOCK TMA UNLOCK TMA

DN0933412 Issue 0147


Introduction

Id:0900d805805b11a6


TRX

GET TRX

GETRELATIONSHIP TRX


XCONNECT

CREATE XCONNECT CREATE XCONNECT

DELETE XCONNECT DELETE XCONNECT

GET XCONNECT GET XCONNECT

LOCK XCONNECT LOCK XCONNECT

SET XCONNECT SET XCONNECT

UNLOCK XCONNECT UNLOCK XCONNECT

48DN0933412 Issue 01


Id:0900d8058053dfb3

Objects and commands in alphabetical order

2 Objects and commands in alphabetical order

DN0933412 Issue 0149


ACDCP

Id:0900d805805b0cac

ACDCP The ACDCPconverter consists of two different power supply and control units: ACPSC (AC power supply, charging and supervising of the battery backup system) and DCPSC (DC power supply).

CREATE ACDCP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h CREATE ACDCP”

Applicability:Phase 2 and Phase 3.

Visibility level: 2.

Command Description:This command adds the AC/DC Converter Panel to the BTSE data base.

Long Names:NAME Address of the managed object

System Responses:Operation Completed

After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of create command is the following:

JOB: 41

PC Time&Date: 11:55:28 03/23/2005

NE Time&Date: 12:57:03 09/15/2004

USER NAME: NSN

COMMAND: Create ACDCP:NAME=RACK:0/ACDCP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23

COMMAND RESULT: Operation successful

END OF OUTPUT FOR JOB 41

JOB: 42

PC Time&Date: 11:55:28 03/23/2005

CREATE ACDCP NAME=RACK:0..7/ACDCP:0..1;

50DN0933412 Issue 01


Id:0900d805805b0cac

ACDCP

NE Time&Date: 12:57:03 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


CHANGED STATE EVENT REPORT:

NAME = RACK:0/ACDCP:0

Availability Status = NULL_value

Notification Identifier = 284


Operation Failed

The specified Object has not been created. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:

JOB: 43

PC Time&Date: 11:55:28 03/23/2005

NE Time&Date: 12:57:03 09/15/2004

USER NAME: NSN

COMMAND: Create ACDCP:NAME=RACK:0/ACDCP:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23

COMMAND RESULT: OPERATION FAILED

MO already created (-159)


Application Guidelines:

• The ACDCP is not necessary for the BS240

• The ACDCP can not be created for the BS240 Compact Site as it is equipped in the Energy Station Rack which is not supervised by the SW

• The ACDCP can not be created for the BS240, BS241, BS240XL, BS40II

Example of Command Execution:Create ACDCP:NAME=RACK:0/ACDCP:0;

DN0933412 Issue 0151


ACDCP

Id:0900d805805b0cac

DELETE ACDCP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h DELETE ACDCP”



Command Description:This command deletes the AC/DC Converter Panel from the BTSE data base.



After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of delete command is the following:

JOB: 38

PC Time&Date: 11:55:25 03/23/2005

NE Time&Date: 12:57:00 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


ChangedConfigurationNotification:

name = RACK:0/ACDCP:0

ChangeInfo = deleted


JOB: 39

PC Time&Date: 11:55:25 03/23/2005

NE Time&Date: 12:57:00 09/15/2004

DELETE ACDCP NAME=RACK:0..7/ACDCP:0..1;

52DN0933412 Issue 01


Id:0900d805805b0cac

ACDCP

USER NAME: NSN

COMMAND: Delete ACDCP:NAME=RACK:0/ACDCP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed

The specified Object has not been deleted. Additionally to the general NACK causes, a specific NACK cause, meaning that the command is inconsistent with physical configu-ration, is possible.


• ACDCP must be locked in phase 3 before deletion

• The ACDCP can not be deleted for the BS-240 Compact Site as it is equipped in the Energy Station Rack which is not supervised by the SW

• The ACDCP can not be deleted for the BS-40II

Example of Command Execution:Delete ACDCP:NAME=RACK:0/ACDCP:0;

GET ACDCP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h GET ACDCP”



Command Description:This command displays the attributes of the AC/DC converter Panel of the BTSE.


REQATTL Required attribute list

ALS alarmStatus

AST administrativeState

AVS availabilityStatus

OST operationalState

PRS proceduralStatus

GET ACDCP NAME=RACK:0..7/ACDCP:0..1 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ];

DN0933412 Issue 0153


ACDCP

Id:0900d805805b0cac

RELFUNCOBJ relatedFuncObjects



JOB: 23

PC Time&Date: 11:55:04 03/23/2005

NE Time&Date: 12:56:39 09/15/2004

USER NAME: NSN

COMMAND: Get ACDCP:NAME=RACK:0/ACDCP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


alarmStatus = CLEARED

administrativeState = Unlocked

availabilityStatus = NULL

operationalState = ENABLED

proceduralStatus = NULL

relatedFuncObjects =


Operation Failed

The GET command has not been successfully executed. A general NACK will indicate possible errors or a specific NACK strictly related to the single command is possible.


• The GET ACDCP command cannot be issued for the BS-240 Compact Site as the ACDCP is equipped in the Energy Station Rack which is not supervised by the SW

• The GET ACDCP command cannot be issued for the BS-40II

Example of Command Execution:Get ACDCP:NAME=RACK:0/ACDCP:0,REQATTL=ALS&AST&AVS&OST&PRS&

RELFUNCOBJ;

54DN0933412 Issue 01


Id:0900d805805b0cac

ACDCP

GETTEST ACDCP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h GETTEST ACDCP”



Command Description:This command displays the attributes of the AC/DC converter test.





JOB: 36

PC Time&Date: 11:55:22 03/23/2005

NE Time&Date: 12:56:57 09/15/2004

USER NAME: NSN

COMMAND: Gettest ACDCP:NAME=RACK:0/ACDCP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/ACDCP:0

testMonitor =

phaseId = PreliminaryTestsAcdcp

phaseStatus = Running

phaseId = CheckAlarmStatusAcdcp

phaseStatus = Waiting

phaseId = EndTestAcdcp


testOutcome = INCONCLUSIVE

GETTEST ACDCP NAME=RACK:0..7/ACDCP:0..1;

DN0933412 Issue 0155


ACDCP

Id:0900d805805b0cac

testState = INITIALIZING


Operation Failed


Application Guidelines:None.

Example of Command Execution:Gettest ACDCP:NAME=RACK:0/ACDCP:0;

LOCK ACDCP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h LOCK ACDCP”



Command Description:This command changes the administrative state of AC/DC converter Panel of the BTSE.


testMonitor it is a list of all test phases related to the selected object; for each phase the related phaseStatus is provided (Passed, Failed, Running or Waiting).

phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...

testOutcome It represents the test result: it can be Inconclusive (if the phases already executed were successful) or Fail (if at least one of the executed phases failed).

testState = Testing It can assume one of the following values: not_initialized, idle, initializing, sus-pended, testing, terminating and dis-abled.

LOCK ACDCP NAME=RACK:0..7/ACDCP:0..1;

56DN0933412 Issue 01


Id:0900d805805b0cac

ACDCP


The specified change of administrative state has been perfomed:

JOB: 24

PC Time&Date: 11:55:06 03/23/2005

NE Time&Date: 12:56:41 09/15/2004

USER NAME: NSN

COMMAND: Lock ACDCP:NAME=RACK:0/ACDCP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


administrativeState = Locked



This provides information about the administrative state, the operational state and the availability status every time a state change occurs:

JOB: 25

PC Time&Date: 11:55:06 03/23/2005

NE Time&Date: 12:56:41 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23




Administrative State = LOCKED



DN0933412 Issue 0157


ACDCP

Id:0900d805805b0cac

Operation Failed

The specified change of administrative state has not been performed (e.g. the object is redundant and its spare copy is disabled or already locked, a subordinate resource cannot go into disabled state with "dependency" availability status).


• The ACDCP can not be locked for the BS-240 Compact Site as it is equipped in the Energy Station Rack which is not supervised by the SW

• The ACDCP can not be locked for the BS-40II

Example of Command Execution:Lock ACDCP:NAME=RACK:0/ACDCP:0;

PERFTEST ACDCP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h PERFTEST ACDCP”



Command Description:This command requests the execution of a test performed by the ACDCP.



Test configuration has been set and the specified test has been started. The System response will not be addressed to the MOT but to the object BTSEP.

JOB: 27

PC Time&Date: 11:55:09 03/23/2005

NE Time&Date: 12:56:44 09/15/2004

USER NAME: NSN

COMMAND: Perftest ACDCP:NAME=RACK:0/ACDCP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


PERFTEST ACDCP NAME=RACK:0..7/ACDCP:0..1;

58DN0933412 Issue 01


Id:0900d805805b0cac

ACDCP


tO = BTSETEST:3


JOB: 28

PC Time&Date: 11:55:09 03/23/2005

NE Time&Date: 12:56:44 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:3

ChangeInfo = created


JOB: 29

PC Time&Date: 11:55:09 03/23/2005

NE Time&Date: 12:56:44 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23




Operational State = ENABLED




JOB: 30

DN0933412 Issue 0159


ACDCP

Id:0900d805805b0cac

PC Time&Date: 11:55:09 03/23/2005

NE Time&Date: 12:56:44 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:3

testOutcome = PASSED

testTermination = Normal


executedPhases =

PreliminaryTestsAcdcp

CheckAlarmStatusAcdcp

EndTestAcdcp


JOB: 31

PC Time&Date: 11:55:09 03/23/2005

NE Time&Date: 12:56:44 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:3



The test results will be displayed at the end of the test phases.

Result TEST:

60DN0933412 Issue 01


Id:0900d805805b0cac

ACDCP

Operation Failed

This NACK-message occurs in the following cases: Message cannot be performed, test not supported, capacity restrictions, physical configuration cannot be performed, object not locked.


• In phase 3 MO must be locked previous to the command execution

Example of Command Execution:Perftest ACDCP:NAME=RACK:0/ACDCP:0;

name = TEST:<n>

testOutcome = This field represents the test result; one of the fol-lowing values can be displayed:

Pass all the test phases are successfully performed.

Inconclusive the test is aborted by the system or the test is terminated by the opera-tor.

Fail if at least one of the executed phases fail.

mOts = It is the identifier of the hardware object under test.

testTermination = It specifies how the test is terminated, it can assume the following values:

Normal all the test phases are performed.

Abort the test is aborted by system.

Cancel the test is terminated by operator.

executedPhases

phaseId = It represents the list of the executed test phases (in case of successful test result, all the test phases will be listed).

additionalWords =

....

failedPhases

phaseId = It represents the list of the failed test phase; addi-tional information is provided for each phase.phaseId =

....

skippedPhases

phaseId = It represents the list of the skipped phases; they are displayed only for test stopped during it execution.phaseId =

....

poprosedRepair Action =

A list of most probable fail probable causes is shown (max four messages)

DN0933412 Issue 0161


ACDCP

Id:0900d805805b0cac

STOPTEST ACDCP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h STOPTEST ACDCP”



Command Description:This command stops a test performed by ACDCP.



Test has been stopped. The System Responses will not be addressed to the MOT but to the object BTSEP.

Operation Failed

Test has not been stopped. This NACK-message can occur when the specified test is not running or in case of test which cannot be stopped.

STOPTEST ACDCP NAME=RACK:0..7/ACDCP:0..1;

Result TEST:

name = TEST:<n>

testOutcome = inconclusive


testTermination = Cancel

executedPhases

phaseId = It represents the list of the executed test phases; the list is not shown for test in the waiting list (queued)....

.

failedPhases

phaseId = It represents the list of the failed test phase;

additional information is provided for each phase.phaseId =

....

skippedPhases

phaseId = It represents the list of the skipped phases;the list is not shown for test in the waiting list (queued).phaseId =

62DN0933412 Issue 01


Id:0900d805805b0cac

ACDCP


Example of Command Execution:Stoptest ACDCP:NAME=RACK:0/ACDCP:0;

UNLOCK ACDCP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h UNLOCK ACDCP”



Command Description:This command changes the administrative state of AC/DC converter.




JOB: 34

PC Time&Date: 11:55:18 03/23/2005

NE Time&Date: 12:56:53 09/15/2004

USER NAME: NSN

COMMAND: Unlock ACDCP:NAME=RACK:0/ACDCP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





UNLOCK ACDCP NAME=RACK:0..7/ACDCP:0..1;

DN0933412 Issue 0163


ACDCP

Id:0900d805805b0cac


JOB: 35

PC Time&Date: 11:55:18 03/23/2005

NE Time&Date: 12:56:53 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23




Administrative State = UNLOCKED



Operation Failed

The specified change of administrative state has not been performed.


• The ACDCP can not be unlocked for the BS-240 Compact Site as it is equipped in the Energy Station Rack which is not supervised by the SW

• The ACDCP can not be unlocked for the BS-40II

Example of Command Execution:Unlock ACDCP:NAME=RACK:0/ACDCP:0;

64DN0933412 Issue 01


Id:0900d805805b0cae

ACT

ACTThe ACT (Alarm Collection Terminal) object represents the terminal for all alarms col-lection.

CREATE ACT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h CREATE ACT”



Command Description:This command adds the ACT (Alarm Collection Terminal) to the BTSE data base. The ACT contains the interface to the external alarms (Operator alarms, rack alarms, shelter alarms,...) and commands and a CAN-BUS interface to the CORE.




JOB: 187

PC Time&Date: 16:48:48 03/23/2005

NE Time&Date: 16:46:42 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/ACT:0


CREATE ACT NAME=RACK:0..7/ACT:0..0;

DN0933412 Issue 0165


ACT

Id:0900d805805b0cae


JOB: 188

PC Time&Date: 16:48:48 03/23/2005

NE Time&Date: 16:46:42 09/15/2004

USER NAME: NSN

COMMAND: Create ACT:NAME=RACK:0/ACT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 72

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create ACT:NAME=RACK:0/ACT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


Message cannot be performed (-17)



• The ACTC which is a part of the DC Panel and it is always present in every rack to collect all internal alarms. It has inputs for 16 internal alarms (1 Door, 6 Fans and 9 rack/shelter internal alarms, which can be defined by the operator). The ACTC supports 9 ENVAs within the range from 0...8. BS82II support 5 internal alarms (1 Door, 1 Fans and 3 rack/shelter internal alarms, which can be defined by the oper-ator)

66DN0933412 Issue 01


Id:0900d805805b0cae

ACT

• An ACTM for 48 alarms and 8 commands is used only in the Base Rack to support the external alarm and command interface for the operator. The ACTM consists of two boards: the ACTA (Alarm and Command Interfaces) and the ACTP (Processor Core). The ACTP sends the alarms to the CORE via the CAN BUS

• For the Extension Racks and the Service Racks only few alarms (e.g. temperature supervision, FAN, ACDC alarms,..) are necessary, so an ACTP with 16 alarm or site inputs is used. The ACTP sends the alarms to the CORE via the CAN BUS

• On a BS82II (base and extension racks) temp., RDO, FAN alarms are controlled by the ACT (on other platforms from COBA in Base rack), these inputs are only handled in a correct way if the ACT is created successfully

Example of Command Execution:Create ACT:NAME=RACK:0/ACT:0;

DELETE ACT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h DELETE ACT”



Command Description:This command deletes the ACT (Alarm Collection Terminal) from the BTSE data base.




JOB: 196

PC Time&Date: 16:49:26 03/23/2005

NE Time&Date: 16:47:20 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


DELETE ACT NAME=RACK:0..7/ACT:0..0;

DN0933412 Issue 0167


ACT

Id:0900d805805b0cae


name = RACK:0/ACT:0



JOB: 197

PC Time&Date: 16:49:26 03/23/2005

NE Time&Date: 16:47:20 09/15/2004

USER NAME: NSN

COMMAND: Delete ACT:NAME=RACK:0/ACT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed

The specified object has not been deleted. Additionally to the general NACK causes, a specific NACK cause, meaning that the command is inconsistent with physical configu-ration, is possible.


• ACT must be locked in phase 3 before deletion

Example of Command Execution:Delete ACT:NAME=RACK:0/ACT:0;

GET ACT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h GET ACT”



GET ACT NAME=RACK:0..7/ACT:0..0 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ];

68DN0933412 Issue 01


Id:0900d805805b0cae

ACT

Command Description:This command displays the attributes of the ACT (Alarm Collection Terminal).



ALS alarmStatus







A message indicates the result of the operation. An example of get command is the fol-lowing:

JOB: 189

PC Time&Date: 16:49:05 03/23/2005

NE Time&Date: 16:46:59 09/15/2004

USER NAME: NSN

COMMAND: Get ACT:NAME=RACK:0/ACT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




availabilityStatus = NotInstalled

operationalState = DISABLED




Operation Failed



DN0933412 Issue 0169


ACT

Id:0900d805805b0cae

Example of Command Execution:Get ACT:NAME=RACK:0/ACT:0,REQATTL=ALS&AST&AVS&OST&

PRS&RELFUNCOBJ;

GETTEST ACT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h GETTEST ACT”



Command Description:This command displays the attributes of the ACT (Alarm Collection Terminal) test.




A message indicates the result of the operation. An example of gettest command is the following:

JOB: 26

PC Time&Date: 11:55:09 03/23/2005

NE Time&Date: 12:56:44 09/15/2004

USER NAME: NSN

COMMAND: Gettest ACT:NAME=RACK:0/ACT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/ACT:0

testMonitor =

phaseId = PreliminaryTestsAct


phaseId = CheckAlarmStatusAct


GETTEST ACT NAME=RACK:0..7/ACT:0..0;

70DN0933412 Issue 01


Id:0900d805805b0cae

ACT

phaseId = EndTestAct





Operation Failed



Example of Command Execution:Gettest ACT:NAME=RACK:0/ACT:0,REQATTL=ALS&AST&AVS&OST&PRS;

LOCK ACT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h LOCK ACT”




phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK ACT NAME=RACK:0..7/ACT:0..0;

DN0933412 Issue 0171


ACT

Id:0900d805805b0cae

Command Description:This command changes the administrative state of ACT (Alarm Collection Terminal).




JOB: 190

PC Time&Date: 16:49:10 03/23/2005

NE Time&Date: 16:47:04 09/15/2004

USER NAME: NSN

COMMAND: Lock ACT:NAME=RACK:0/ACT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 191

PC Time&Date: 16:49:10 03/23/2005

NE Time&Date: 16:47:04 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/ACT:0

72DN0933412 Issue 01


Id:0900d805805b0cae

ACT




Operation Failed



Example of Command Execution:Lock ACT:NAME=RACK:0/ACT:0;

PERFTEST ACT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h PERFTEST ACT”







JOB: 36

PC Time&Date: 11:55:22 03/23/2005

NE Time&Date: 12:56:57 09/15/2004

USER NAME: NSN

COMMAND: Perftest ACT:NAME=RACK:0/ACT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


PERFTEST ACT NAME=RACK:0..7/ACT:0..0;

DN0933412 Issue 0173


ACT

Id:0900d805805b0cae

MOT = RACK:0/ACT:0

tO = BTSETEST:2


JOB: 37

PC Time&Date: 11:55:22 03/23/2005

NE Time&Date: 12:56:57 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2



JOB: 38

PC Time&Date: 11:55:25 03/23/2005

NE Time&Date: 12:57:00 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/ACT:0




74DN0933412 Issue 01


Id:0900d805805b0cae

ACT


JOB: 39

PC Time&Date: 11:55:25 03/23/2005

NE Time&Date: 12:57:00 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:2



MOT = RACK:0/ACT:0

executedPhases =

PreliminaryTestsAct

CheckAlarmStatusAct

EndTestAct


JOB: 40

PC Time&Date: 11:55:28 03/23/2005

NE Time&Date: 12:57:03 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2



DN0933412 Issue 0175


ACT

Id:0900d805805b0cae

Operation Failed





Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



76DN0933412 Issue 01


Id:0900d805805b0cae

ACT

Example of Command Execution:Perftest ACT:NAME=RACK:0/ACT:0;

STOPTEST ACT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h STOPTEST ACT”



Command Description:This command is used to stop a diagnostic previously started.




STOPTEST ACT NAME=RACK:0..7/ACT:0..0;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


DN0933412 Issue 0177


ACT

Id:0900d805805b0cae

Operation Failed



Example of Command Execution:Stoptest ACT:NAME=RACK:0/ACT:0;

UNLOCK ACT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h UNLOCK ACT”







JOB: 192

PC Time&Date: 16:49:15 03/23/2005

NE Time&Date: 16:47:09 09/15/2004

USER NAME: NSN

COMMAND: Unlock ACT:NAME=RACK:0/ACT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




UNLOCK ACT NAME=RACK:0..7/ACT:0..0;

78DN0933412 Issue 01


Id:0900d805805b0cae

ACT



JOB: 193

PC Time&Date: 16:49:15 03/23/2005

NE Time&Date: 16:47:09 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/ACT:0




Operation Failed



Example of Command Execution:Unlock ACT:NAME=RACK:0/ACT:0;

DN0933412 Issue 0179


BATTERY

Id:0900d805805b0cb0

BATTERYOne backup battery system can be connected to the AC/DC sub-rack. The battery system consists of up to four batteries optionally housed in the battery sub-rack. The DC and Battery Controller (DCBCTRL) installed in the AC/DC subrack is the supervision unit which provides for the Batteries charging.

CREATE BATTERY

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h CREATE BATTERY”



Command Description:This command adds the BATTERY (which provides battery backup) to the BTSE data base.




JOB: 21

PC Time&Date: 11:54:46 03/23/2005

NE Time&Date: 12:56:21 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/BATTERY:0


CREATE BATTERY NAME=RACK:0..7/BATTERY:0..3;

80DN0933412 Issue 01


Id:0900d805805b0cb0

BATTERY


JOB: 22

PC Time&Date: 11:54:47 03/23/2005

NE Time&Date: 12:56:22 09/15/2004

USER NAME: NSN

COMMAND: Create BATTERY:NAME=RACK:0/BATTERY:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 23

PC Time&Date: 11:55:04 03/23/2005

NE Time&Date: 12:56:39 09/15/2004

USER NAME: NSN

COMMAND: Create BATTERY:NAME=RACK:0/BATTERY:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• The AC/DC is necessary for the charging and supervising of the battery backup system

• When a service environment (AC/DC + Battery Backup) is built on at BS60 sites, after replacement of BS60 with BS-240 a special setting of the attribute "associat-edString" in the command "CREATE ENVABTSE" for the corresponding site input allows the operator to indicate that the support of emergency configuration is

DN0933412 Issue 0181


BATTERY

Id:0900d805805b0cb0

required for battery backup unit system (Emergency Configuration after AC fault of 3rd party Service Rack)

• The BATTERY can not be created for the BS-240 Compact Site as it is equipped in the Battery Backup Rack and Energy Station Rack which are not supervised by the SW. In the BS-240 implementation the switch into emergency configuration (due to a battery discharge alarm) is triggered by an "ALARM STATUS" CAN bus message that has been received from the CAN node of the AC/DC controller. In the BS-240 Compact Site the AC/DC alarm line for the AC/DC converter and for the battery must be connected to a site input which is used as a trigger for the emergency configura-tion. A special setting of the attribute "associatedString" in the command "CREATE ENVABTSE" for the corresponding site input allows the operator to indicate that the support of emergency configuration is required for the 3rd party battery backup unit system.

• The BATTERY can not be created for the BS-40II.

Example of Command Execution:Create BATTERY:NAME=RACK:0/BATTERY:0;

DELETE BATTERY

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h DELETE BATTERY”



Command Description:This command deletes the BATTERY (which provides battery backup) from the BTSE data base.




JOB: 19

PC Time&Date: 11:54:44 03/23/2005

NE Time&Date: 12:56:19 09/15/2004

DELETE BATTERY NAME=RACK:0..7/BATTERY:0..3;

82DN0933412 Issue 01


Id:0900d805805b0cb0

BATTERY

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/BATTERY:0



JOB: 20

PC Time&Date: 11:54:44 03/23/2005

NE Time&Date: 12:56:19 09/15/2004

USER NAME: NSN

COMMAND: Delete BATTERY:NAME=RACK:0/BATTERY:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• BATTERY must be locked in phase 3 before deletion

• The BATTERY can not be deleted for the BS-240 Compact Site as it is equipped in the Battery Backup Rack and Energy Station Rack which are not supervised by the SW

• The BATTERY can not be deleted for the BS-40II

Example of Command Execution:Delete BATTERY:NAME=RACK:0/BATTERY:0;

GET BATTERYGET BATTERY NAME=RACK:0..7/BATTERY:0..3 [,REQATTL=ALS, AST,

AVS, BATTCAP, OST, PRS, RELFUNCOBJ];

DN0933412 Issue 0183


BATTERY

Id:0900d805805b0cb0

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h GET BATTERY”



Command Description:This command displays the attributes of the BATTERY.



ALS alarmStatus



BATTCAP batteryCapacity(*5Ah)





After command execution, a message indicates the result of the operation. An example of get command is the following:

JOB: 5

PC Time&Date: 11:54:18 03/23/2005

NE Time&Date: 12:55:53 09/15/2004

USER NAME: NSN

COMMAND: Get BATTERY:NAME=RACK:0/BATTERY:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





batteryCapacity(*5Ah) = 3


84DN0933412 Issue 01


Id:0900d805805b0cb0

BATTERY




Operation Failed



• The GET BATTERY command can not be issued for the BS-240 Compact Site as the BATTERY is equipped in the Battery Backup Rack and Energy Station Rack which are not supervised by the SW

• The GET BATTERY command can not be issued for the BS-40II

Example of Command Execution:Get BATTERY:NAME=RACK:0/BATTERY:0,REQATTL=ALS&AST&AVS&

BATTCAP&OST&PRS&RELFUNCOBJ;

GETTEST BATTERY

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h GETTEST BATTERY”



Command Description:This command displays the attributes of the BATTERY test.




After command execution, a message indicates the result of the operation. An example of gettest command is the following:

JOB: 14

PC Time&Date: 11:54:31 03/23/2005

GETTEST BATTERY NAME=RACK:0..7/BATTERY:0..3;

DN0933412 Issue 0185


BATTERY

Id:0900d805805b0cb0

NE Time&Date: 12:56:06 09/15/2004

USER NAME: NSN

COMMAND: Gettest BATTERY:NAME=RACK:0/BATTERY:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/BATTERY:0

testMonitor =

phaseId = PreliminaryTestsBattery


phaseId = CheckAlarmStatusBattery


phaseId = EndTestBattery





Operation Failed




phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



86DN0933412 Issue 01


Id:0900d805805b0cb0

BATTERY

Example of Command Execution:Gettest BATTERY:NAME=RACK:0/BATTERY:0;

LOCK BATTERY

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h LOCK BATTERY”



Command Description:This command changes the administrative state of the BATTERY (which provides battery backup).




JOB: 6

PC Time&Date: 11:54:22 03/23/2005

NE Time&Date: 12:55:57 09/15/2004

USER NAME: NSN

COMMAND: Lock BATTERY:NAME=RACK:0/BATTERY:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






LOCK BATTERY NAME=RACK:0..7/BATTERY:0..3;

DN0933412 Issue 0187


BATTERY

Id:0900d805805b0cb0

JOB: 7

PC Time&Date: 11:54:22 03/23/2005

NE Time&Date: 12:55:57 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/BATTERY:0




Operation Failed



• The BATTERY can not be locked for the BS-240 Compact Site as it is equipped in the Battery Backup Rack and Energy Station Rack which are not supervised by the SW

• The BATTERY can not be locked for the BS-40II

Example of Command Execution:Lock BATTERY:NAME=RACK:0/BATTERY:0;

PERFTEST BATTERY

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h PERFTEST BATTERY”



PERFTEST BATTERY NAME=RACK:0..7/BATTERY:0..3;

88DN0933412 Issue 01


Id:0900d805805b0cb0

BATTERY

Command Description:This command requests the execution of a test performed by the BATTERY (which provides battery backup).




JOB: 9

PC Time&Date: 11:54:26 03/23/2005

NE Time&Date: 12:56:01 09/15/2004

USER NAME: NSN

COMMAND: Perftest BATTERY:NAME=RACK:0/BATTERY:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:2


JOB: 10

PC Time&Date: 11:54:26 03/23/2005

NE Time&Date: 12:56:01 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2


DN0933412 Issue 0189


BATTERY

Id:0900d805805b0cb0


JOB: 11

PC Time&Date: 11:54:26 03/23/2005

NE Time&Date: 12:56:01 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23








JOB: 12

PC Time&Date: 11:54:26 03/23/2005

NE Time&Date: 12:56:01 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:2




executedPhases =

PreliminaryTestsBattery

CheckAlarmStatusBattery

EndTestBattery

90DN0933412 Issue 01


Id:0900d805805b0cb0

BATTERY


JOB: 13

PC Time&Date: 11:54:26 03/23/2005

NE Time&Date: 12:56:01 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2




Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

DN0933412 Issue 0191


BATTERY

Id:0900d805805b0cb0

Operation Failed




Example of Command Execution:Perftest BATTERY:NAME=RACK:0/BATTERY:0;

STOPTEST BATTERY

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h STOPTEST BATTERY”







failedPhases


....

skippedPhases


....



STOPTEST BATTERY NAME=RACK:0..7/BATTERY:0..3;

92DN0933412 Issue 01


Id:0900d805805b0cb0

BATTERY

Operation Failed



Example of Command Execution:Stoptest BATTERY:NAME=RACK:0/BATTERY:0;

UNLOCK BATTERY

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h UNLOCK BATTERY”



Command Description:This command changes the administrative state of the BATTERY (which provides battery backup).

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


UNLOCK BATTERY NAME=RACK:0..7/BATTERY:0..3;

DN0933412 Issue 0193


BATTERY

Id:0900d805805b0cb0




JOB: 15

PC Time&Date: 11:54:35 03/23/2005

NE Time&Date: 12:56:10 09/15/2004

USER NAME: NSN

COMMAND: Unlock BATTERY:NAME=RACK:0/BATTERY:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 16

PC Time&Date: 11:54:35 03/23/2005

NE Time&Date: 12:56:10 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23






94DN0933412 Issue 01


Id:0900d805805b0cb0

BATTERY


Operation Failed



• The BATTERY can not be unlocked for the BS-240 Compact Site as it is equipped in the Battery Backup Rack and Energy Station Rack which are not supervised by the SW

• The BATTERY can not be unlocked for the BS-40II

Example of Command Execution:Unlock BATTERY:NAME=RACK:0/BATTERY:0;

DN0933412 Issue 0195


BCOM

Id:0900d805805b0cb2

BCOMThe BCOM (Combining Module) is an equipment object that represents the combining module supporting up to 6 TRX, all within the same frequency band. The BCOM has no CAN bus interface and therefore cannot provide the remote inventory data onboard. New BCOM element shall be handled via IDF editor from LMT Evolution. No ACT-C is supported.

MDUX (a small BCOM 6:6) and HYBRID6 can replace FDUAMCOs. MDUX can fit into 2 adjacent ACOM slots of BTSplus mainline rack. If more than 6 transceivers are required, the HYBRID6 module, containing 6 hybrids and isolators, has to be addition-ally equipped. This module fits either in a BCOM slot (along with a MDUX) or in an ACOM- respectively MUCO-slot of the BTSplus mainline rack.

The alarm interface of the MDUX is identical and fully compatible to the BCOM, while the HYBRID6 is a completely passive module with only RF interfaces. It is therefore not visible for the software.

The 6:6 combining of the MDUX allows single rack cell configurations which cannot be supported with the existing combining equipment. With 2 MDUX equipped in a single BS240 II rack a 2/2/2 dual band configuration becomes possible.

All inventory units of the optional Service Rack are nob_RIUs which have to be regis-tered via LMT Evolution and IDF editor.

g BCOM command is valid only for BS240 and BS240XL.

The configurations BCOM (MDUX) + HYBRID6 +COAMCO are possible.

The maximum number of carrier unit ports, which are connected to the RX outputs of an MDUX submodule is:

• 4 for MDUX only equipped

• 8 for MDUX and COAMCO equipped.

The maximum number of carrier unit ports which are either directly or via HYBRID6 con-nected to the TX input of an MDUX submodule is:

• 1 for MDUX without HYBRID6 equipped

• 2 for MDUX with HYBRID6 equipped

• 4 for MDUX with HYBRID6 and COAMCO equipped

CREATE BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h CREATE BCOM”

CREATE BCOM NAME=RACK:0..7/BCOM:0..1 [,ANT<x>CELLNO=] [,ANT<x>SCNRX=] ,ACONN= [,FBAND=] [,BCOMTYPE=];

96DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM



Command Description:This command is used to create the instances 0 and 1 of BCOM object.

In this CREATE command cell number, an alarm connector or frequency band of Bcom can be specified.

Furthermore SetWiringRx BCOM and SetWiringTx BCOM commands have to be used to specify the wiring data. Alarm connector parameter is mandatory at the creation of BCOM.


ANT<x>CELLNO ant<x>CellNumber

ANT<x>SCNRX ant<x>SecondCellNumberRx

ACONN alarmConnector

FBAND frequencyBand

BCOMTYPE bcomType


After command execution, a message of Changed Configuration Notification is dis-played.

A further message indicates the result of the operation. An example of create command

is the following:

Create BCOM:1

JOB: 6199

PC Time&Date: 31.01.2007 16:31:00 +01:00

NE Time&Date: 31.01.2007 17:30:29 +01:00

USER NAME: NSN

COMMAND: Create BCOM:NAME=RACK:0/BCOM:1,ACONN=ENVA0,FBAND=Gsm900,

ANT0CELLNO=0,ANT0WDRX=FCUMAIN1N1,ANT0WDTX=

FCUMAIN1TX1,ANT1CELLNO=0,ANT1WDRX=FCUMAIN4N,ANT1WDTX=FCUMAIN4TX0,ANT2CELLNO=0,ANT2WDRX=FCUMAIN5N,ANT2WDTX=FCUMAIN5TX0,ANT3CELLNO=0,ANT3WDRX=FCUMAIN3N1,ANT3WDTX=FCUMAIN3TX1,ANT4CELLNO=0,ANT4WDRX=FCUMAIN0N1,ANT4WDTX=FCUMAIN0TX1,ANT5CELLNO=0,ANT5WDRX=FCUMAIN2N1,ANT5WDTX=FCUMAIN2TX1;

DN0933412 Issue 0197


BCOM

Id:0900d805805b0cb2

SW RELEASE: 01-04-18-06-13-04_07-01-26


ant0CellNumber = 0

ant1CellNumber = 0

ant2CellNumber = 0

ant3CellNumber = 0

ant4CellNumber = 0

ant5CellNumber = 0

ant0WiringDataRx = FCUMAIN1N1

ant1WiringDataRx = FCUMAIN4N

ant2WiringDataRx = FCUMAIN5N




ant0WiringDataTx = FCUMAIN1TX1






aconn=ENVA0

frequencyBand = Gsm900


Command:

6A 00 80 FF 12 02 81 A9 89 25 00 01 46 01 00 47

01 00 48 01 00 49 01 00 4A 01 00 4B 01 00 59 04

02 2A FF 01 5B 04 00 2A FF 04 5D 04 00 2A FF 05

5F 04 02 2A FF 03 61 04 02 2A FF 00 63 04 02 2A

FF 02 5A 04 01 2A FF 01 5C 04 00 2A FF 04 5E 04

00 2A FF 05 60 04 01 2A FF 03 62 04 01 2A FF 00

64 04 01 2A FF 02 70 01 00 71 01 01

Response:

6A 00 80 00 02 12 01 AA 89 25 00 01 46 01 00 47

98DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

01 00 48 01 00 49 01 00 4A 01 00 4B 01 00 59 04

02 2A FF 01 5B 04 00 2A FF 04 5D 04 00 2A FF 05

5F 04 02 2A FF 03 61 04 02 2A FF 00 63 04 02 2A

FF 02 5A 04 01 2A FF 01 5C 04 00 2A FF 04 5E 04

00 2A FF 05 60 04 01 2A FF 03 62 04 01 2A FF 00

64 04 01 2A FF 02 70 01 00 71 01 01

Operation Failed

None.


• After the CREATE command, commands SetWiringRx BCOM and SetWiringTx BCOM must be issued to specify antenna combiner wiring

Example of Command Execution:Create BCOM:NAME=RACK:0/BCOM:1, ANT0CELLNO=0, ACONN=ENVA0, FBAND=GSM900;

DELETE BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h DELETE BCOM”



Command Description:This command is used to delete BCOM.




Delete BCOM:1

JOB: 6179

DELETE BCOM NAME=RACK:0..7/BCOM:0..1;

DN0933412 Issue 0199


BCOM

Id:0900d805805b0cb2

PC Time&Date: 31.01.2007 16:25:51 +01:00

NE Time&Date: 31.01.2007 17:25:20 +01:00

USER NAME: NSN

COMMAND: Delete BCOM:NAME=RACK:0/BCOM:1;

SW RELEASE: 01-04-18-06-13-04_07-01-26



Command:

0A 00 80 FF 12 02 81 AC 89 25 00 01

Response:

0A 00 80 00 02 12 01 AD 89 25 00 01

Operation Failed

None.

Application Guidelines:None

Example of Command Execution:Delete BCOM:NAME=RACK:0/BCOM:1;

GET BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h GET BCOM”



Command Description:This command displays the attributes of the BCOM except the wiring data attributes.

GET BCOM NAME=RACK:0..7/BCOM:0..1 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, ANT<x>CELLNO, ANT<x>SCNRX, ACONN, FBAND, BCOMTYPE];

100DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM



ALS alarmStatus









FBAND frequencyBand

BCOMTYPE bcomType


A further message indicates the result of the operation. An example of get command is

the following:

JOB: 26

PC Time&Date: 12:03:04 03/24/2005

NE Time&Date: 00:02:31 11/29/2004

USER NAME: NSN

COMMAND: Get BCOM:NAME=RACK:0/BCOM:0;

SW RELEASE: 01-04-18-01- 26-51_05-02-23


alarmStatus = CRITICAL


availabilityStatus = Failed

ant<x>CellNumber = 2

ant<x>SecondCellNumberRx = 2

aconn=ENVA0

frequencyBand = Gsm900




DN0933412 Issue 01101


BCOM

Id:0900d805805b0cb2


Operation Failed



Example of Command Execution:BCOM:NAME=RACK:0/BCOM:0,REQATTL=ALS&AST&AVS&ANT<x>CELLNO&ANT <x>SCNRX&OST&PRS&RELFUNCOBJ&ACONN&FBAND;


Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h GETRELATIONSHIP BCOM”



Command Description:This command is used to retrieve the functional relationship information for the selected HMO (Hardwar Managed Object); the relationship information consists of all FMOs (Functional Managed Object) using the HMO service.




After command execution, a message of Changed configuration Notification is dis-played.

A further message indicates the result of the operation. An example of getrelationship command is the following:

JOB: 1227221

PC Time&Date: 01/29/2007 14:44:27 +01:00

NE Time&Date: 01/29/2007 15:44:11 +01:00

USER NAME: NSN


NAME=RACK:0..7/BCOM:0..1;

102DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

COMMAND: Getrelationship BCOM:NAME=RACK:0/BCOM:0;

SW RELEASE: 01-04-18-06-13-04_07-01-26



FMO = BTS:0/TRX:4

FMO = BTS:0/TRX:6

FMO = BTS:0/TRX:8

FMO = BTS:0/TRX:10

FMO = BTS:0/TRX:9

FMO = BTS:0/TRX:2


JOB: 1227222

PC Time&Date: 01/29/2007 14:44:27 +01:00

NE Time&Date: 01/29/2007 15:44:11 +01:00

USER NAME: NSN

COMMAND: Getrelationship BCOM:NAME=RACK:0/BCOM:1;

SW RELEASE: 01-04-18-06-13-04_07-01-26



FMO = BTS:0/TRX:1

FMO = BTS:0/TRX:3

FMO = BTS:0/TRX:5

FMO = BTS:0/TRX:7

FMO = BTS:0/TRX:11

FMO = BTS:0/TRX:0

Operation Failed

None.


DN0933412 Issue 01103


BCOM

Id:0900d805805b0cb2

Example of Command Execution:Getrelationship BCOM:NAME=RACK:0/BCOM:0;

GETTEST BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h GETTEST BCOM”



Command Description:This command displays the attributes of the BCOM test.




After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of gettest command is the following:

JOB: 25

PC Time&Date: 12:01:44 03/24/2005

NE Time&Date: 00:01:11 11/29/2004

USER NAME: NSN

COMMAND: Gettest BCOM:NAME=RACK:0/BCOM:0;

SW RELEASE: 01-04-17-06-26-51_05-02-23


MOT = RACK:0/BCOM:0

testMonitor =

phaseId = PreliminaryTestsBcom


phaseId = CheckAlarmStatusBcom


GETTEST BCOM NAME=RACK:0..7/BCOM:0..1;

104DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

phaseId = EndTestBcom





Operation Failed



Example of Command Execution:Gettest BCOM:NAME=RACK:0/BCOM:0,REQATTL=MORT&TESTMON&TESTOUT&

TESTST;

GETWIRINGRX BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h GETWIRINGRX BCOM”




phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



GETWIRINGRX BCOM NAME=RACK:0..7/BCOM:0..1 ,REQATTL=ANT<x>WDRX;

DN0933412 Issue 01105


BCOM

Id:0900d805805b0cb2

Command Description:This command displays the wiring data attributes of the BCOM for RX path.

It is applicable only on: BS240, BS240II, BS240XL, BS240XLII, BS241, BS241 II.



ANT<x>WDRX ant<x>WiringDataRx


A further message indicates the result of the operation. An example of getWiringRx command is the following:

********** Message 60 **********

JOB: 60

PC Time&Date: 17.12.2007 10:20:51 +01:00

NE Time&Date: 01.01.1990 00:07:40 +00:00

USER NAME: NSN

COMMAND: GetWiringRx

BCOM:NAME=RACK:0/BCOM:0,REQATTL=ANT0WDRX&ANT1WDRX&ANT2WDRX&ANT3WDRX&ANT4WDRX&ANT5WDRX;

SW RELEASE: 01-04-18-01-18-01_07-12-14

COMMAND RESULT:Operation successful

ant0WiringDataRx = CU0N & CU1N & CU2N & CU3N & FCUMAIN5N & FCUMAIN5N1 & FCUMAIN6N & FCUMAIN6N1

ant1WiringDataRx = NULL






Binary Command

12 00 80 ff 12 02 81 b3 ab 25 00 00 1a 06 59 5b 5d 5f 61 63

Binary Response

106DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

4a 00 80 00 02 12 01 82 ab 25 00 00 59 20 00 12 ff 00 00 12

ff 01 00 12 ff 02 00 12 ff 03 00 2a ff 05 02 2a ff 05 00 2a

ff 06 02 2a ff 06 5b 04 ff ff ff ff 5d 04 ff ff ff ff 5f 04

ff ff ff ff 61 04 ff ff ff ff 63 04 ff ff ff ff

Operation Failed

The GETWIRINGRX command has not been successfully executed. A general NACK will indicate possible errors or a specific NACK strictly related to the single command is possible.


Example of Command Execution:GetWiringRx

BCOM:NAME=RACK:0/BCOM:0,REQATTL=WDRX&ANT;

GETWIRINGTX BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h GETWIRINGTX BCOM”



Command Description:This command displays the wiring data attributes of the BCOM for TX path.

It is applicable only on: BS240, BS240II, BS240XL, BS240XLII, BS241, BS241 II.



ANT<x>WDTX ant<x>WiringDataTx


- Operation Completed

A further message indicates the result of the operation. An example of getWiringTx command is the following:

********** Message 61 **********

GETWIRINGTX BCOM NAME=RACK:0..7/BCOM:0..1 ,REQATTL=ANT<x>WDTX;

DN0933412 Issue 01107


BCOM

Id:0900d805805b0cb2

JOB: 61

PC Time&Date: 17.12.2007 10:20:59 +01:00

NE Time&Date: 01.01.1990 00:07:48 +00:00

USER NAME: NSN

COMMAND: GetWiringTx

BCOM:NAME=RACK:0/BCOM:0,REQATTL=ANT0WDTX&ANT1WDTX&ANT2WDTX

&ANT3WDTX&ANT4WDTX&ANT5WDTX;

SW RELEASE: 01-04-18-01-18-01_07-12-14


ant0WiringDataTx = CU0 & CU1 & CU2 & CU3

ant1WiringDataTx = NULL






Binary Command

12 00 80 ff 12 02 81 b6 ab 25 00 00 1a 06 5a 5c 5e 60 62 64

Binary Response

3a 00 80 00 02 12 01 82 ab 25 00 00 5a 10 ab 12 ff 00 ab 12

ff 01 ab 12 ff 02 ab 12 ff 03 5c 04 ff ff ff ff 5e 04 ff ff

ff ff 60 04 ff ff ff ff 62 04 ff ff ff ff 64 04 ff ff ff ff

Operation Failed

The GETWIRINGTX command has not been successfully executed. A general NACK will indicate possible errors or a specific NACK strictly related to the single command is possible.


Example of Command Execution:GetWiringTx

108DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

BCOM:NAME=RACK:0/BCOM:0,REQATTL=WDTX&ANT;

LOCK BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h LOCK BCOM”



Command Description:This command changes the administrative state of the BCOM.




JOB: 27

PC Time&Date: 12:03:17 03/24/2005

NE Time&Date: 00:02:44 11/29/2004

USER NAME: NSN

COMMAND: Lock BCOM:NAME=RACK:0/BCOM:0;

SW RELEASE: 01-04-17-06-26-51_05-02-23






JOB: 28

LOCK BCOM NAME=RACK:0..7/BCOM:0..1;

DN0933412 Issue 01109


BCOM

Id:0900d805805b0cb2

PC Time&Date: 12:03:17 03/24/2005

NE Time&Date: 00:02:44 11/29/2004

USER NAME: NSN

SW RELEASE: 01-04-17-06-26-51_05-02-23



NAME = RACK:0/BCOM:0




Operation Failed



Example of Command Execution:Lock BCOM:NAME=RACK:0/BCOM:0;

PERFTEST BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h PERFTEST BCOM”



Command Description:This command is used to start an asynchronous test in BCOM.



PERFTEST BCOM NAME=RACK:0..7/BCOM:0..1;

110DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

Test configuration has been set and the specified test has been started. The System response will not be addressed to the MOT but to the object.

JOB: 30

PC Time&Date: 12:03:25 03/24/2005

NE Time&Date: 00:02:52 11/29/2004

USER NAME: NSN

COMMAND: Perftest BCOM:NAME=RACK:0/BCOM:0;

SW RELEASE: 01-04-17-06-26-51_05-02-23


MOT = RACK:0/BCOM:0

tO = BTSETEST:1


JOB: 31

PC Time&Date: 12:03:25 03/24/2005

NE Time&Date: 00:02:52 11/29/2004

USER NAME: NSN

SW RELEASE: 01-04-17-06-26-51_05-02-23



name = BTSETEST:1



JOB: 32

PC Time&Date: 12:03:25 03/24/2005

NE Time&Date: 00:02:52 11/29/2004

DN0933412 Issue 01111


BCOM

Id:0900d805805b0cb2

USER NAME: NSN

SW RELEASE: 01-04-17-06-26-51_05-02-23




Availability Status = Failed



JOB: 33

PC Time&Date: 12:03:25 03/24/2005

NE Time&Date: 00:02:52 11/29/2004

USER NAME: NSN

SW RELEASE: 01-04-17-06-26-51_05-02-23


Test Report:

name = BTSETEST:1

testOutcome = FAILED


MOT = RACK:0/BCOM:0

executedPhases =

PreliminaryTestsBcom

EndTestBcom

failedPhases =

phaseId = CheckAlarmStatusBcom

additionalWords =

H`0001

H`0000

H`0000

H`0000

H`0000

H`0000

H`0000

112DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

H`0000

proposedRepairActions =

#0#

#0#

#0#

#0#


JOB: 34

PC Time&Date: 12:03:25 03/24/2005

NE Time&Date: 00:02:52 11/29/2004

USER NAME: NSN

SW RELEASE: 01-04-17-06-26-51_05-02-23



name = BTSETEST:1




Result TEST:

name = TEST:<n>







DN0933412 Issue 01113


BCOM

Id:0900d805805b0cb2

Operation Failed



Example of Command Execution:Perftest BCOM:NAME=RACK:0/BCOM:0;

SET BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h SET BCOM”






executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



SET BCOM NAME=RACK:0..7/BCOM:0..1 [,ANT<x>CELLNO=] [,ANT<x>SCNRX=] [,ACONN=] [,FBAND=] [,BCOMTYPE=];

114DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

Command Description:This command allows modification of the attributes of the BCOM. For setting of wiring data attributes of BCOM the commands: SetWiringRx BCOM and SetWiringTx BCOM must be used.





FBAND frequencyBand

BCOMTYPE bcomType


After command execution, a message of Changed Attribute Event Report is displayed. A further message indicates the result of the operation. An example of set command is the following:

JOB: 46

PC Time&Date: 12:07:06 03/24/2005

NE Time&Date: 00:06:33 11/29/2004

USER NAME: NSN

COMMAND: Set BCOM:NAME=RACK:0/BCOM:0;

SW RELEASE: 01-04-17-06-26-51_05-02-23



Operation Failed

The specified attributes have not been set. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible.


• The existing state and status attributes shall be assigned to the attributes group STATES

• <x> = 0 .. 5.

• With the SET BCOM command it is possible to 'unset' the parameters setting the value 'NULL', e.g. the cell parameters. To 'unset' the parameters first you must use

DN0933412 Issue 01115


BCOM

Id:0900d805805b0cb2

BCOM SetWiringTx& Set WiringRx commands, then Set command (to unset cell assignment).

Example:

SetWiringTX BCOM:NAME=RACK:0/BCOM:0, ANT0WDTX=<NULL>,

ANT1WDTX=<NULL>,

ANT2WDTX=<NULL>, ANT3WDTX=<NULL>,

,ANT4WDTX=<NULL>,,ANT5WDTX=<NULL>;

;

SetWiringRX BCOM:NAME=RACK:0/BCOM:0, ANT0WDRX=<NULL>,

ANT1WDRX=<NULL>,

ANT2WDRX=<NULL>, ANT3WDRX=<NULL>,

,ANT4WDRX=<NULL>,,ANT5WDRX=<NULL>;

;

Set BCOM:NAME=RACK:0/BCOM:0,ANT0CELLNO=<NULL>,

ANT0SCNRX=<NULL>,ANT1CELLNO=<NULL>,ANT1SCNRX=<NULL>, ANT2CELLNO=<NULL>,ANT2SCNRX=<NULL>,ANT3CELLNO=<NULL>,

ANT3SCNRX=<NULL>,ANT4CELLNO=<NULL>,ANT4SCNRX=<NULL>,

ANT5CELLNO=<NULL>,ANT5SCNRX=<NULL>;

Example of Command Execution:Set BCOM:NAME=RACK:0/BCOM:0,ant<x>CellNumber=2, ant<x>SecondCellNum-berRx= 2,ACONN=ENVA0,Fband=Gsm900;

SETWIRINGRX BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h SETWIRINGRX BCOM”



Command Description:This command allows modification of the wiring data attributes of the BCOM for RX path.

This command shall be used after creation of BCOM object. Up to 8 wiring destinations can be set allowing to define also the configuration MDUX + HYBRID6 +COAMCO.

This is valid only for: BS240, BS240II, BS240XL, BS240XLII, BS241, BS241 II.


SETWIRINGRX BCOM NAME=RACK:0..7/BCOM:0..1 [,ANT<x>WDRX=];

116DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM

ANT<x>WDRX ant<x>WiringDataRx


After command execution, a message of Changed Attribute Event Report is displayed.

A further message indicates the result of the operation. An example of SetWiringRx command is the following:

JOB: 56

PC Time&Date: 17.12.2007 10:19:03 +01:00

NE Time&Date: 01.01.1990 00:05:52 +00:00

USER NAME: NSN

COMMAND: SetWiringRx

BCOM:NAME=RACK:0/BCOM:0,ANT0WDRX=CU0N&CU1N&CU2N&CU3N&FCUMAIN5N&FCUMAIN5N1&FCUMAIN6N&FCUMAIN6N1;

SW RELEASE: 01-04-18-01-18-01_07-12-14


ant0WiringDataRx = CU0N & CU1N & CU2N & CU3N & FCUMAIN5N & FCUMAIN5N1& FCUMAIN6N & FCUMAIN6N1


Operation Failed

In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible.


• The 1 attribute for each antenna shall be assigned to 6 separate groups 'ANTENNA <x>'.

• <x> = 0 .. 5.

• With the SETWIRINGRX BCOM command it is possible to 'unset' the parameters setting the value 'NULL', for wiringDataRx attributes and with the SETWIRINGTX BCOM command it is possible to 'unset' the parameters setting the value 'NULL' and finally by using a command "SET BCOM" to 'unset' the cell parameters

Example:

SetWiringRx

BCOM:NAME=RACK:0/BCOM:0,ANT0WDRX=<NULL>,

ANT1WDRX=<NULL>,ANT2WDRX=<NULL>,

DN0933412 Issue 01117


BCOM

Id:0900d805805b0cb2

ANT3WDRX=<NULL>, ANT4WDRX=<NULL>, ANT5WDRX=<NULL>,

;

SetWiringTx

BCOM:NAME=RACK:0/BCOM:0,ANT0WDTX=<NULL>,

ANT1WDTX=<NULL>,ANT2WDTX=<NULL>,

ANT3WDTX=<NULL>, ANT4WDTX=<NULL>, ANT5WDTX=<NULL>,



ANT2CELLNO=<NULL>,ANT2SCNRX=<NULL>,ANT3CELLNO=<NULL>,



Example of Command Execution:SetWiringRx BCOM:NAME=RACK:0/BCOM:0,

ANT0WDRX=CU0N&CU1N&CU2N&CU3N&FCUMAIN5N&FCUMAIN5N1&FCUMAIN6N&FCUMAIN6N1;

g The wiring data of cell configurations with MDUX, HYBRID6 and COAMCO are neither completely visible nor configurable via RC, SetWiringRx BCOM command not forseen for RC, when to display the wiring for this configuration always max 2 CUs.TX wiring destinations and max 4 CUs Rx wiring destinations for each corre-sponding BCOM port is displayed even if 4 CUs for TX path and 8 CUs Rx path are wired.

SETWIRINGTX BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h SETWIRINGTX BCOM”



Command Description:This command allows modification of the wiring data attributes of the BCOM for TX path.

This command shall be used after creation of BCOM object. Up to 4 wiring destinations can be set allowing to define also the configuration MDUX + HYBRID6 +COAMCO.

This is valid only for: BS240, BS240II, BS240XL, BS240XLII, BS241, BS241 II.

SETWIRINGTX BCOM NAME=RACK:0..7/BCOM:0..1 [,ANT<x>WDTX=];

118DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM


ANT<x>WDTX ant<x>WiringDataTx


After command execution, a message of Changed Attribute Event Report is displayed.

A further message indicates the result of the operation. An example of SetWiringTx command is the following:

JOB: 53

PC Time&Date: 17.12.2007 10:17:53 +01:00

NE Time&Date: 01.01.1990 00:04:42 +00:00

USER NAME: NSN

COMMAND: SetWiringTx

BCOM:NAME=RACK:0/BCOM:0,ANT0WDTX=CU0&CU1&CU2&CU3;

SW RELEASE: 01-04-18-01-18-01_07-12-14


ant0WiringDataTx = CU0 & CU1 & CU2 & CU3


Binary Command

1c 00 80 ff 12 02 81 d6 ab 25 00 00 5a 10 ab 12 ff 00 ab 12

ff 01 ab 12 ff 02 ab 12 ff 03

Binary Response

1c 00 80 00 02 12 01 d7 ab 25 00 00 5a 10 ab 12 ff 00 ab 12

ff 01 ab 12 ff 02 ab 12 ff 03

Operation Failed

None.


• The 1 attribute for each antenna shall be assigned to 6 separate groups 'ANTENNA <x>'.

• <x> = 0 .. 5

DN0933412 Issue 01119


BCOM

Id:0900d805805b0cb2

• With the SETWIRINGTX BCOM command it is possible to 'unset' the parameters setting the value 'NULL', for wiringDataTx attributes and with the SETWIRINGRX BCOM command it is possible to 'unset' the parameters setting the value 'NULL' and finally by using a command "SET BCOM" to 'unset' the cell parameters.

Example:

SetWiringTx

BCOM:NAME=RACK:0/BCOM:0,ANT0WDTX=<NULL>,

ANT1WDTX=<NULL>,ANT2WDTX=<NULL>,

ANT3WDTX=<NULL>, ANT4WDTX=<NULL>, ANT5WDTX=<NULL>,

SetWiringRx

BCOM:NAME=RACK:0/BCOM:0,ANT0WDRX=<NULL>,

ANT1WDRX=<NULL>,ANT2WDRX=<NULL>,

ANT3WDRX=<NULL>, ANT4WDRX=<NULL>, ANT5WDRX=<NULL>,;



ANT2CELLNO=<NULL>,ANT2SCNRX=<NULL>,ANT3CELLNO=<NULL>,



Example of Command Execution:SetWiringTx BCOM:NAME=RACK:0/BCOM:0,ANT0WDTX=CU0&CU1&CU2&CU3;

g The wiring data of cell configurations with MDUX, HYBRID6 and COAMCO are neither completely visible nor configurable via RC. SetWiringTx BCOM command is not forseen for RC, when the wiring for this configuration is displayed always max 2 CUs.

TX wiring destinations and max 4 CUs Rx wiring destinations for each correspond-ing BCOM port is displayed even if 4 CUs for TX path and 8 CUs Rx path are wired.

STOPTEST BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h STOPTEST BCOM”




STOPTEST BCOM NAME=RACK:0..7/BCOM:0..1;

120DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM



Test has been stopped. The System Responses will not be addressed to the MOT but to the object.

Operation Failed



Example of Command Execution:Stoptest BCOM:NAME=RACK:0/BCOM:0;

UNLOCK BCOM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h UNLOCK BCOM”

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


UNLOCK BCOM NAME=RACK:0..7/BCOM:0..1;

DN0933412 Issue 01121


BCOM

Id:0900d805805b0cb2



Command Description:This command changes the administrative state of the BCOM.




JOB: 36

PC Time&Date: 12:03:45 03/24/2005

NE Time&Date: 00:03:12 11/29/2004

USER NAME: NSN

COMMAND: Unlock BCOM:NAME=RACK:0/BCOM:0;

SW RELEASE: 01-04-17-06-26-51_05-02-23






JOB: 37

PC Time&Date: 12:03:45 03/24/2005

NE Time&Date: 00:03:12 11/29/2004

USER NAME: NSN

SW RELEASE: 01-04-17-06-26-51_05-02-23


122DN0933412 Issue 01


Id:0900d805805b0cb2

BCOM






Operation Failed



Example of Command Execution:Unlock BCOM:NAME=RACK:0/BCOM:0;

DN0933412 Issue 01123


BPORT

Id:0900d805805b0cb6

BPORTThe object BPORT identifies one of the 2 PCM30/24 interfaces on the COBA and one of the 6 PCM30/24 interfaces on the COSA. The object BPORT holds the configuration data of one Abis port.

CREATE BPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h CREATE BPORT”



Command Description:This command is used for the Handling of PCM-Line Configuration and adds the BPORT (BTSE Port) together with its attributes to the BTSE data base. The object BPORT holds the configuration data of one Abis port. The instance number of this object is related to the physical Abis port number (e.g.: Instance 0 is related to the physical port 1 (OVPT), which allows the connection of the BTSE to the Abis line1 and so on).


BERT bitErrorRateThreshold

L1CTRLTS layer1ControlTs

L1PT layer1ProtocolType

L1RAT layer1RemoteAlarmType

LCONF lineConfiguration

LIMP lineImpedance



JOB: 42

PC Time&Date: 11:55:28 03/23/2005

NE Time&Date: 12:57:03 09/15/2004

CREATE BPORT NAME=BPORT:0..7 [,BERT=] [,L1CTRLTS=] ,L1PT= [,L1RAT=] ,LCONF= [,LIMP=];

124DN0933412 Issue 01


Id:0900d805805b0cb6

BPORT

USER NAME: SAG

SW RELEASE: 01-04-17-01-26-51_05-02-23 COMMAND RESULT: Operation suc-cessful


name = BPORT:1



JOB: 43

PC Time&Date: 11:55:28 03/23/2005

NE Time&Date: 12:57:03 09/15/2004

USER NAME: SAG

COMMAND: Create BPORT:NAME=BPORT:1,L1PT=pcm30crc4,LCONF=star;

SW RELEASE: 01-04-17-01-26-51_05-02-23


layer1ProtocolType = pcm30crc4

lineConfiguration = star


Operation Failed


JOB: 44

PC Time&Date: 11:55:52 03/23/2005

NE Time&Date: 12:57:27 09/15/2004

USER NAME: SAG

COMMAND: Create BPORT:NAME=BPORT:2,L1PT=pcm30crc4,LCONF=star;

SW RELEASE: 01-04-17-01-26-51_05-02-23


DN0933412 Issue 01125


BPORT

Id:0900d805805b0cb6




• Wildcard addressing is not possible

• To guarantee a correct transition of SW releases the operator must use BPort instance 0 for O&M link

• Changing or setting of layer1ProtocolType or layer1RemoteAlarm attributes means a temporary loss of service for the whole BTSE

• Layer1ControlTS must be different to the related BTSM-O&M signalling link

• Layer1ControlTS (if activated) must not be used for other purposes (e.g. signalling, traffic or cross connection and vice versa)

• SpecialBitRobbing attribute is allowed only for PCM24 and means that a special bit (bit 2) is used for signalling of a remote alarm

• BPORTs (0&1, 2&3, 4&5, 6&7) form port pairs which are short-circuited during BTSE coming up

• Bport-0 is clock master for BTSE, all other Bports are slaves. Therefore, PCM line connected to Bport-0 must arrive from different network entity

• To configure a line circuit (e.g.: multidrop, loop) 2 BPort objects have to be created by the operator. As long the 2 objects are not available all BTSEs located behind on this circuit are not reachable. Line alarms detected by one Abis port are mapped to the associated BPort instance

• One star circuit (only one port is involved) is allowed per port pair and must be placed on the lower port number

• Creation of the second port on a port pair (in case of a multidrop/loop circuit) must lead always to the same settings of the attributes as the first port has with the follow-ing exceptions

1) Activation of a layer1ControlTimeslot is only allowed for the first port in case of a multidrop circuit

2) Attribute bitErrorRateThresholds can be set independently

• If COBA2P8 is installed and COSA is disabled/not Installed, the BPORT:2-7 are in Enable.null state but they cannot be used because the HW does not support them.

If COBA4P12 is installed and COSA is disabled/not Installed, the BPORT:2,3 are in Enable.degraded state and the BPORT:4-7 are in Enable.null but they cannot be used because the HW does not support them.

g This is valid for all BTSplus mainline except for the BR BS82II.

Example of Command Execution:Create BPORT:NAME=BPORT:0,L1PT=pcm30crc4,LCONF=star,

BERT=E10_3-E10_3,L1CTRLTS=0-0,L1RAT=ProtocolSignalling,

LIMP=Imp100or120Ohm;

126DN0933412 Issue 01


Id:0900d805805b0cb6

BPORT

DELETE BPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h DELETE BPORT”



Command Description:This command deletes the BPORT (BTSE port) from the BTSE data base.




JOB: 45

PC Time&Date: 11:55:52 03/23/2005

NE Time&Date: 12:57:27 09/15/2004

USER NAME: SAG

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME=BPORT:2



JOB: 46

PC Time&Date: 11:55:56 03/23/2005

NE Time&Date: 12:57:31 09/15/2004

DELETE BPORT NAME=BPORT:0..7;

DN0933412 Issue 01127


BPORT

Id:0900d805805b0cb6

USER NAME: SAG

COMMAND: Delete BPORT:NAME=BPORT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• Before Deletion of a BPort instance in phase 3, the object must be locked before

• Deletion in phase 3 is allowed only if no TSL is assigned to BPort (XCONNECT defined)

• The BPORT 0 is one of the "Minimal Parameters" of the BTSE. If the BPORT 0 is deleted, the entire BTSE is out of service (only Phase 2)

• BPORT 0 cannot be deleted in Phase 3

Example of Command Execution:Delete BPORT:NAME=BPORT:0;

GET BPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h GET BPORT”



Command Description:This command displays the attributes of the PCM lines connected to the COBA (Core Basis).



ALS alarmStatus


GET BPORT NAME=BPORT:0..7 [,REQATTL=ALS, AST, AVS, BERT, L1CTRLTS, L1PT, L1RAT, LCONF, LSIND, LIMP, OST, PRDIRECT, PRS, RELFUNCOBJ];

128DN0933412 Issue 01


Id:0900d805805b0cb6

BPORT




L1PT layer1ProtocolType



LSIND lineStatusIndication

LIMP lineImpedance


PRDIRECT preferredDirection




After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of get command is the following:

JOB: 5

PC Time&Date: 11:31:23 03/23/2005

NE Time&Date: 11:29:14 09/15/2004

USER NAME: SAG

COMMAND: GET BPORT:NAME=BPORT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





bitErrorRateThreshold =

lowerThreshold = E10_5

upperThreshold = E10_3

layer1ControlTs =

TSL = 0

SSL = 0

layer1ProtocolType = pcm30crc4

layer1RemoteAlarmType = ProtocolSignalling

DN0933412 Issue 01129


BPORT

Id:0900d805805b0cb6

lineConfiguration = multidrop

lineStatusIndication =

remoteAlarmInd = FALSE

frameSynchronizationLoss = FALSE

CRCFailure = FALSE

noLevel = FALSE

CRCRemoteEnviroment = FALSE

BERTLowerThreshold = FALSE

BERTUpperThreshold = FALSE

promptMaintenanceAlarmInd = FALSE

lineImpedance = accDIP



preferredDirection = Null



Operation Failed



• None.

Example of Command Execution:Get BPORT:NAME=BPORT:0,REQATTL=ALS&AST&AVS&BERT&

L1CTRLTS&L1RAT&L1PT&LCONF&LIMP&LSIND&OST&PRDIRECT&PRS&

RELFUNCOBJ;

LOCK BPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h LOCK BPORT”



Command Description:This command changes the administrative state of the BPORT object.

LOCK BPORT NAME=BPORT:0..7;

130DN0933412 Issue 01


Id:0900d805805b0cb6

BPORT




JOB: 47

PC Time&Date: 11:56:00 03/23/2005

NE Time&Date: 12:57:35 09/15/2004

USER NAME: SAG

COMMAND: Lock BPORT:NAME=BPORT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23 COMMAND RESULT: Operation suc-cessful

administrativeState = LOCKED




JOB: 48

PC Time&Date: 11:56:22 03/23/2005

NE Time&Date: 12:57:57 09/15/2004

USER NAME: SAG

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME=BPORT:0;



DN0933412 Issue 01131


BPORT

Id:0900d805805b0cb6


Operation Failed



• BPORT 0 cannot be locked in Phase 3

Example of Command Execution:Lock BPORT:NAME=BPORT:0;

SET BPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h SET BPORT”



Command Description:This command permits modification of the attributes of the BPORT (BTES port), previ-ously created with the (create) CREATE BPORT command. The object BPORT holds the configuration data of one Abis port.






LIMP lineImpedance


The specified attribute has been set. In addition, a Changed Attribute Event Report indi-cates that the command has been successfully executed:

JOB: 15

SET BPORT NAME=BPORT:0..7 [,BERT=] [,L1CTRLTS=] [,L1RAT=] [,LCONF=] [,LIMP=];

132DN0933412 Issue 01


Id:0900d805805b0cb6

BPORT

PC Time&Date: 11:32:16 03/23/2005

NE Time&Date: 11:30:07 09/15/2004

USER NAME: SAG

COMMAND: Set BPORT:NAME=BPORT:0,BERT=E10_5-E10_3;

SW RELEASE: 01-04-17-01-26-51_05-02-23


bitErrorRateThreshold =

lowerThreshold = E10_5

upperThreshold = E10_3


Operation Failed

The specified attributes have not been set. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with physical configuration, is possible.


• The layer1ControlTS attribute is applicable only for the line configuration "Loop"

• Changing or setting of layer1RemoteAlarmType attribute means a temporary loss of service for the whole BTSE

• Layer1ControlTS must be different to the related BTSM-O&M signalling link

• SpecialBitRobbing attribute is allowed only for PCM24 and means that a special bit (bit 2) is used for signalling of a remote alarm

Example of Command Execution:Set BPORT:NAME=BPORT:0,BERT=E10_3-E10_3,L1CTRLTS=0-0,

L1RAT=ProtocolSignalling,LCONF=star,LIMP=Imp100or120Ohm;

UNLOCK BPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h UNLOCK BPORT”



UNLOCK BPORT NAME=BPORT:0..7;

DN0933412 Issue 01133


BPORT

Id:0900d805805b0cb6

Command Description:This command changes the administrative state of the BPORT (BTSE port).




JOB: 185

PC Time&Date: 12:06:51 03/23/2005

NE Time&Date: 13:08:26 09/15/2004

USER NAME: SAG

COMMAND: UNLOCK BPORT:NAME=BPORT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


administrativeState = UNLOCKED




JOB: 186

PC Time&Date: 12:06:51 03/23/2005

NE Time&Date: 13:08:26 09/15/2004

USER NAME: SAG

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME=BPORT:0;

134DN0933412 Issue 01


Id:0900d805805b0cb6

BPORT




Operation Failed



Example of Command Execution:Unlock BPORT:NAME=BPORT:0;.

DN0933412 Issue 01135


BTS

Id:0900d805805b0cb8

BTSThe BTS object locates a cell connected to the related Flexi BSC product family. Logi-cally it represents all the informa-tion related to the cell and to its configuration.

GET BTS

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h GET BTS”

Applicability:Phase 3.


Command Description:This command displays the cell-specific global attributes of a chosen BTS.



ACBQPFF acBQPFgtFac

ACBQPMAX acBQPMax(%)

ACEFLFF acEFLFgtFac

ACFERMAX acFERMax(%)

ACLNKTYP acLinkType

ACMINEFLDMA acMinEFLDMA(%)

ACMAXEFLDMA acMaxEFLDMA(%)

ACPER acPeriod

GET BTS NAME=BTS:0..11 [,REQATTL=ACBQPFF, ACBQPMAX, ACEFLFF, ACFERMAX, ACLNKTYP, ACMINEFLDMA, ACMAXEFLDMA, ACPER, AMRLKAT, AMRLKATWFS, ANTHOPMOD, ANTHOPP, ANTHOPST, ARFACCHAC-MDF, ASCICIPH, AST, AVS, BCCHFREQ, BSIC, BTSISHOP, BURNOFFS, SYSID, CELLTYPE, CUCONF, DTMHOMTIMER, EAC, EANTHOP, EEOTD, EEXCDIST, ERFACCHALPDMF, ERFACCHCMDF, ERSACCHDL, ERSACCHUL, ETOP, ETXDIVTS, EXCDIST, FACCHQ, FACHBT, FRANOFFS, GSMTIME, HOPMODE, INTAVE-PAR, INTCLASS, INTLVBND, MSTXPMAX, MSTXPMAXC, NEPTTREP, NTWTYPE, NY1, NY2, OST, PCCCHLDI, PNOFACCH, PWROUT, RACHBT, RACHLAS, RELEQUI-POBJ, REPTYP, RFRSINDP, RSACCHRXLDL, RSAC-CHRXLUL, RSACCHTODL, RSACCHTOUL, RXSIGLEVADJ, RXSIGLEVADJC, RXSWCURSET, SEG-MENTID, SWBCAPABILITY, SWBSERVSTATE, T3105, T3151, TCCCHLDI, BTSOBJID, RADIUSEXT, SRADIU-SEXT, MSDISTBEHAV];

136DN0933412 Issue 01


Id:0900d805805b0cb8

BTS

AMRLKAT aMRLinkAdapTuning

AMRLKATWFS aMRLinkAdapTuningWFS(dB)

ANTHOPMOD antennaHoppingMode

ANTHOPP antennaHoppingPeriod

ANTHOPST antennaHoppingStatus

ARFACCHACMDF applyRFacchOnAnyCmdFrame

ASCICIPH enableCiphForASCI



BCCHFREQ bcchFrequency

BSIC bsIdentityCode

BTSISHOP btsIsHopping

BURNOFFS burstNumberOffset

SYSID cellAllocationNumber

CELLTYPE cellType

CUCONF carrierUnitConfiguration

DTMHOMTIMER hoDTMTimer(SACCH_multiframe_480/470ms)

EAC enableAc

EANTHOP enableAntennaHopping

EEOTD enableEOTD

EEXCDIST enableExcessiveDistance

ERFACCHALPDMF enableRFacchOnAnyLapdmFrame

ERFACCHCMDF enableRFacchOnCmdFrames

ERSACCHDL enableRSacchDL

ERSACCHUL enableRSacchUL

ETOP enableTOP

ETXDIVTS enableTxDivTimeShift

EXCDIST excessiveDistance(km)

FACCHQ facchQual

FACHBT fachBusyThreshold(dBm)

FRANOFFS frameNumberOffset

GSMTIME gsmTime

HOPMODE hoppingMode

INTAVEPAR intaveParameter

INTCLASS enableInterferenceClass

INTLVBND interferenceLevelBoundaries

MSTXPMAX mSTxPwrMax(*dBm mapped)

MSTXPMAXC mSTxPwrMaxCompl

NEPTTREP notDataRepCount

DN0933412 Issue 01137


BTS

Id:0900d805805b0cb8

NTWTYPE networkType

NY1 ny1

NY2 ny2


PCCCHLDI periodCcchLoadIndication(sec)

PNOFACCH periodNotificationFACCH(sec)

PWROUT powerOutputThresholds

RACHBT rachBusyThreshold(dBm)

RACHLAS rachLoadAveragingSlots

RELEQUIPOBJ relatedEquipObjects

REPTYP reportType

RFRSINDP rfResourceIndicationPeriod

RSACCHRXLDL repSacchRxLevDL

RSACCHRXLUL repSacchRxLevUL

RSACCHTODL repSacchTimeOutDL

RSACCHTOUL repSacchTimeOutUL

RXSIGLEVADJ rxSigLevAdjust

RXSIGLEVADJC rxSigLevAdjustCompl

RXSWCURSET rxSwitchCurrentSetting

SEGMENTID segmentId

SWBCAPABILITY switchedBeamCapability

SWBSERVSTATE switchedBeamServState

T3105 btsTimer3105(*10ms)

T3151 uplBusyRepRate

TCCCHLDI thresholdCcchLoadIndication

BTSOBJID btsObjectId

RADIUSEXT radiusExtension(km)

SRADIUSEXT superRadiusExtension(km)

MSDISTBEHAV msDistanceBehaviour



JOB: 19

PC Time&Date: 11:33:29 03/23/2005

NE Time&Date: 11:31:19 09/15/2004

138DN0933412 Issue 01


Id:0900d805805b0cb8

BTS

USER NAME: SAG

COMMAND: Get BTS:NAME=BTS:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


acBQPFgtFac = 0.2

acBQPMax(%) = 5

acEFLFgtFac = 0.04

acFERMax(%) = 5.0

acLinkType = UL_SAMPLES_ONLY

acMaxEFLDMA(%) = per_50

acMinEFLDMA(%) = per_10

acPeriod = SACCH_120


aMRLinkAdapTuning = 100

antennaHoppingMode = NOBCCHTRX

antennaHoppingPeriod = SECOND

antennaHoppingStatus = FALSE


bcchFrequency = 5

bsIdentityCode =

BCC = 3

NCC = 5

btsIsHopping = FALSE

btsTimer3105(*10ms) = 4

burstNumberOffset = 0

cellAllocationNumber = BB900

cellType = STDCELL

enableAc = FALSE

enableAntennaHopping = FALSE

enableEOTD = FALSE

enableExcessiveDistance = TRUE

enableInterferenceClass = TRUE

enableTxDivTimeShift = FALSE

excessiveDistance(km) = 35

facchQual = 5

frameNumberOffset = 0

gsmTime = 30303

DN0933412 Issue 01139


BTS

Id:0900d805805b0cb8

hoppingMode = BBHOP

intaveParameter = 31

JOB: 19

interferenceLevelBoundaries =

intThrBou1 = 2

intThsBou2 = 6

intThsBou3 = 12

intThsBou4 = 22

intThsBou5 = 63

mSTxPwrMax(*dBm_mapped) = 5

mSTxPwrMaxCompl = 5

mobileCountryCode =

MCC = "555"

networkType = GSMDCS

ny1 = 50

ny2 = 20


periodCcchLoadIndication(sec) = 255

periodNotificationFACCH(sec) = 2.5

powerOutputThresholds =

oPwrFaultThreshold = m10db

redOutPwrThreshold = m6db

excesOutPwrThresh = db5

rachBusyThreshold(dBm) = 109

rachLoadAveragingSlots = 204

relatedEquipObjects =

rfResourceIndicationPeriod = 60

rxSwitchCurrentSetting = NULL

startingTime = 65535

switchedBeamCapability = none

switchedBeamServState = NULL

t200 =

sdcchSAPIO = 44

facchTCHF = 31

facchTCHH = 41

saccchTCHSAPIO = 90

sacchSDCCH = 90

sdcchSAPI3 = 90

140DN0933412 Issue 01


Id:0900d805805b0cb8

BTS

sacchTCHSAPI3 = 135

t3115(*10ms) = 4

taAdjust(microseconds) = 0.0

timerUplinkReply = 20

thresholdCcchLoadIndication = 100

tNCH(*multiframes) = 16

tSync(*10ms) = 1000

tSyncD(*10ms) = 1000

tSyncR(*10ms) = 400

tSyncU(*10ms) = 1000

JOB: 19

tTrau(*10ms) = 1000

txDivTimeShiftExcept = NONE

txDivTimeShiftParam = [-1.00]

voiceGroupUplinkFree(*10ms) = 2


Operation Failed



• The attribute HOPMODE (hoppingMode) can be set only if there are no subordinate frequency hopping system equipped

• When the attribute INTCLASS is enabled "RF resource indication" messages (rele-vant to the attributes INTAVEPAR, INTLVBND and RFRSINDP) are sent to the Flexi BSC product family

• Values indicating more than 35 Km in the attribute EXCDIST are valid only for extended cells

• The attributes ETXDIVTS, TXDIVTSEXCPT and TXDIVTSPAR have only function-ality for hh=04-01 and hh=04-06

Example of Command Execution:Get BTS:NAME=BTS:0,REQATTL=ACBQPFF&ACBQPMAX&ACEFLFF& ACFER-MAX&ACLNKTYP&ACMAXEFLDMA&ACMINEFLDMAX&ACPER& AMRLKAT& NTHOPMOD&ANTHOPP&ANTHOPST ASCICIPH &AST& AVS&BCCHFREQ&BSIC& BTSISHOP&BURNOFFS&CELLGLID&CELLTYPE&CUCONF&EAC&EANTHOP& EEXCDIST&EEQTD &ERFACCH&ETOP&ETXDI-VTS&EXCDIST&FACCHQ&FILETYPE& FRANOFFS&GSMTIME& HOP-MODE&INTAVEPAR&INTCLASS&INTLVBND&LAPDOVLTRXL&MCC&MSTXPMAX&

DN0933412 Issue 01141


BTS

Id:0900d805805b0cb8

MSTXPMAXC&NTWTYPE&NY1&NY2&OST&PCCCHLDI&PNOFACCH& PWROUT& RACHBT&RACHLAS&REPTYP&RFACCHFT&RFRSINDP&RXSWCSET&RELEQUIPOBJ&RXSIGLEVADJ&Â RXSIGLEVADJC&RXSWCURSET& STATIME&STDBYST& SWBCAPABILITY&SWBSERVSTATE&Â SWBEAMCPBL&SWBEAMSSTAT&SYSID&T200&T3105&T3115& TAADJ&TCCCHLDI&TNCH& TSYNC&TSYNCD&TSYN-CDL&TSYNCR&TSYNCU&TTRAU& TUPLREP&TXDIVTSEXCPT&TXDI-VTSPAR&TXSIGLEVADJ&TXSIGLEVADJC& VGRULF&VGSCULF

GET BTS TIMER

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h GET BTS TIMER”



Command Description:This command displays the attributes of the BTS timer.



STATIME startingTime

T200 t200

T3115 t3115(*10ms)

TAADJ taAdjust(microseconds)

TNCH tNCH(*multiframes)

TSYNC tSync(*10ms)

TSYNCD tSyncD(*10ms)

TSYNCR tSyncR(*10ms)

TSYNCU tSyncU(*10ms)

TTRAU tTrau(*10ms)

TUPLREP timerUplinkReply

TXDIVTSPAR txDivTimeShiftParam

TXDIVTSEXCPT txDivTimeShiftExcept

TXSIGLEVADJ txSigLevAdjust

TXSIGLEVADJC txSigLevAdjustCompl

VGSCULFT voiceGroupUplinkFree(*10ms)

GET BTS TIMER NAME=BTS:0..11 ,REQATTL=STATIME, T200, T3115, TAADJ, TNCH, TSYNC, TSYNCD, TSYNCR, TSYNCU, TTRAU, TUPLREP, TXDIVTSPAR, TXDIVTSEXCPT, TXSI-GLEVADJ, TXSIGLEVADJC, VGSCULFT;

142DN0933412 Issue 01


Id:0900d805805b0cb8

BTS


None

Operation Failed

None


Example of Command Execution:None

DN0933412 Issue 01143


BTSEP

Id:0900d805805b0cba

BTSEPThe BTSEP object models the BTSplus mainline family. Following BTSplus mainline tyoes are supported:

• The BS240/1 consists of a base rack with up to 8 TRXs. Optionally it can be con-nected to two extension racks to reach up to 24 TRX

• The BS240XL consists of a base rack with up to 12 TRXs. Optionally it can be con-nected an extension rack to reach up to 24 TRXs

• The BS40/1 and BS40II consists of a base rack with up to 4 TRXs • The BS82II consists of a base rack with up to 2 TRXs. Optionally it can be connected

up two extension rack to reach up to 6 TRXs

g The BTSEP object models also the BTSplus basic. The description of commands related to BTSplus basic is out of the scope of this manual.

DELETE BTSEP DBFILE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h DELETE BTSEP DBFILE”



Command Description:This command deletes the data base file.



The data base file has been deleted.

JOB: 55

PC Time&Date: 11:56:59 03/23/2005

NE Time&Date: 12:58:13 09/15/2004

USER NAME: NSN

COMMAND: Delete BTSEP DBFILE:NAME=BTSEP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


DELETE BTSEP DBFILE

NAME=BTSEP:0..0;

144DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP


Operation Failed

The data base file has not been deleted.


• The file related to REMINV isn't affected by the command

• The command cause a restart of the BTSE and that the operator has to do a new login afterward

• All HW Objects, which were created per command, will be deleted, including "Minimal Configuration"

• All stored SW Loads will still be available

• Only the db of COBA:0 will be deleted

Example of Command Execution:Delete BTSEP DBFILE:NAME=BTSEP:0;

FORMAT BTSEP FLASH

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h FORMAT BTSEP FLASH”



Dangerous

Command Description:This command formats the Flash EPROMs of COBA (Core module). Since it is consid-ered a "dangerous" command, a confirmation dialog will ask you to confirm or cancel the action.



The Flash EPROMs of the COBA have been formatted.

JOB: 56

FORMAT BTSEP FLASH

NAME=BTSEP:0..0;

DN0933412 Issue 01145


BTSEP

Id:0900d805805b0cba

PC Time&Date: 11:57:07 03/23/2005

NE Time&Date: 12:58:42 09/15/2004

USER NAME: NSN

COMMAND: Format BTSEP FLASH:NAME=BTSEP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed

The Flash EPROMs of the COBA have not been formatted.


• The command cause a restart of the BTSE and that the operator has to do a new login afterward

• All HW Objects and all SW Loads will be deleted, complete formatting in COBA:0 if COBA:1 is Power Off

Example of Command Execution:Format BTSEP FLASH:NAME=BTSEP:0;

GET BTSEP NOSWL

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h GET BTSEP NOSWL”



Command Description:This command displays the attributes related to the BTSE (BTS Site Equipment).



ALIGCOBA alignedCoba

ALRMSEVXXX alarmSeverityXXX

GET BTSEP NOSWL NAME=BTSEP:0..0 [,REQATTL=ALIGCOBA, ALRM-SEVXXX, ALS, AST, AVS, CHIDT, EAUTOREC, EQUPOS, GTWADRV4, LMTLSESS, LMTLTIME, LMTUAL, LMTU-NAME, LOCNAME, OST, OVPTINS, PRS, RELFUNCOBJ, RXDIVSV, SALUNAME, SCLPRIOLST, VENDNA];

146DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP

ALS alarmStatus



CHIDT changeOnIDT

EAUTOREC enableAutoRecovery

EQUPOS equipmentPosition

GTWADRV4 gatewayAddressIPv4

LMTLSESS lmtLogonSession

LMTLTIME lmtLogonTime

LMTUAL lmtUserAccessLevel

LMTUNAME lmtUserName

LOCNAME locationName


OVPTINS ovptInstalled



RXDIVSV enableRxDiversitySupervision

SALUNAME salesUniqueName

SCLPRIOLST serviceClassPrioList

VENDNA vendorName


After command execution, a mesNSNe of Changed Configuration Notification is dis-played. A further mesNSNe indicates the result of the operation. An example of get noswl command is the following:

JOB: 48

PC Time&Date: 11:56:22 03/23/2005

NE Time&Date: 12:57:57 09/15/2004

USER NAME: NSN

COMMAND: Get BTSEP NOSWL:NAME=BTSEP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



alarmSeverityAcdcp = DEFAULT_DB

alarmSeverityAct = DEFAULT_DB

DN0933412 Issue 01147


BTSEP

Id:0900d805805b0cba

alarmSeverityCoba = DEFAULT_DB

alarmSeverityBattery = DEFAULT_DB

alarmSeverityCosa = DEFAULT_DB

alarmSeverityCu = DEFAULT_DB

alarmSeverityDidctma = DEFAULT_DB

alarmSeverityDilna = DEFAULT_DB

alarmSeverityDudctma = DEFAULT_DB

alarmSeverityDulna = DEFAULT_DB

alarmSeverityDuvswr = DEFAULT_DB

alarmSeverityFcumain = DEFAULT_DB

alarmSeverityFcutr = DEFAULT_DB

alarmSeverityFanp = DEFAULT_DB

alarmSeverityFtnfp = DEFAULT_DB

alarmSeverityFvswrp = DEFAULT_DB

alarmSeverityLmu = DEFAULT_DB

alarmSeverityTma = DEFAULT_DB



changeOnIDT = IDTWasChanged

enableAutoRecovery = disabled

equipmentPosition = "010101"

lmtLogonSession = ACTIVE

lmtLogonTime =

year = 2003

month = Nov

day = 21

hour = 12

minute = 54

second = 51

JOB: 48

lmtUserAccessLevel = ACCESS_CONTROL_MANAGEMENT

lmtUserName = "NSN"

locationName = "EARTH"


ovptInstalled = TRUE



148DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP

BTSM:0

enableRxDiversitySupervision = disabled

salesUniqueName = "NOT_DEFINED"

vendorName = "SIEM."


Operation Failed



• The attributes have to be set beforehand, otherwise the response will be a Nack mesNSNe

Example of Command Execution:Get BTSEP NOSWL:NAME=BTSE:0,REQATTL=ALRMSEVACDCP&

ALRMSEVACT&ALRMSEVBATTERY&ALRMSEVCOBA&ALRMSEVCOSA&

ALRMSEVCU&ALRMSEVDIDCTMA&ALRMSEVDILNA&ALRMSEVDUDCTMA&

ALRMSEVDULNA&ALRMSEVDUVSWR&ALRMSEVFCUMAIN&ALRMSEVFCUTR&

ALRMSEVFVSWRP&ALRMSEVFTNFP&ALRMSEVFANP&ALRMSEVLMU&

ALRMSEVTMA&ALS&AST&AVS&CHIDT&EAUTOREC& EQUPOS&LMTLSESS&

LMTLTIME&LMTUAL&LMTUNAME&LOCNAME&OST&OVPTINS&PRS&

RELFUNCOBJ&RXDIVSV&SALUNAME&VENDNA;

GET BTSEP SWL

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h GET BTSEP SWL”






SWLDINT swLoadIntended

SWLDSAF swLoadSafety

SWLDST swLoadsStored

GET BTSEP SWL NAME=BTSEP:0..0 ,REQATTL=SWLDINT, SWLDSAF, SWLDST;

DN0933412 Issue 01149


BTSEP

Id:0900d805805b0cba


After command execution, a mesNSNe of Changed Configuration Notification is dis-played. A further mesNSNe indicates the result of the operation. An example of get swl command is the following:

JOB: 49

PC Time&Date: 11:56:26 03/23/2005

NE Time&Date: 12:58:01 09/15/2004

USER NAME: NSN

COMMAND: Get BTSEP SWL:NAME=BTSEP:0,REQATTL=SWLDINT;

SW RELEASE: 01-04-17-01-26-51_05-02-23


swLoadIntended = "HS011726.SWL:02-08-01-01-00-27_04-11-19"


Operation Failed



• The attributes have to be set beforehand, otherwise the response will be a Nack mesNSNe

• This command has another behaviour than all other commands. If you want all parameters you have to choose its own REQATTL

Example of Command Execution:Get BTSEP SWL:NAME=BTSEP:0,REQATTL=SWLDINT&SWLDSAF&SWLDST;

GET ACTIVEALARMS BTSEP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h GETACTIVEALARMS BTSEP”



NAME=BTSEP:0..0 [,EVTYP=];

150DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP


Command Description:This command is sent to the BTSE to ask for the active alarms of a certain failure_event_type. A Failre Event Report will be displayed, with the following attributes:


EVTYP eventType

eventType This attribute specifies the type of failure event alarm.

eventTime It represents the time of the event.

perceivedSeverity This attribute can assume the following values:

indeterminate

criticalFailure

majorFailure

minorFailure

warningLevelFailure

failureCeased

probableCause This attribute indicates the probable cause of the failure.

specificProblem It is a code that has to be referred to the 'Alarm Manual'.

trendIndication This attribute can assume the following values:

lessSevere

noChange

moreSevere

notificationIdentifier The range of this attribute is: 0...4294967295

correlatedNotifications This attribute is composed by the following fields:

identifier: 0...4294967295

relatedMO: object class and object instance refer to the source object in the father event. During state and alarm alignment the state class BTSEP is used.

thresholdInformation This information element is only present if a threshold is assigned to the corresponding alarm and the 'perceived severity' is not 'failure ceased'. If no threshold is exceeded only the observed value is valid.

additionalText This is a string of 26 ASCII characters which are speci-fied by the operator for the corresponding envaBTSE instance (site input). The ASCII characters are not ter-minated by a NULL character

additionalInformation This attribute specifies some additional information (Originator value, FileVersion...)

DN0933412 Issue 01151


BTSEP

Id:0900d805805b0cba


After command execution, a mesNSNe of Changed Configuration Notification is dis-played. A further mesNSNe indicates the result of the operation. An example of get active alarms command is the following:

JOB: 50

PC Time&Date: 11:56:29 03/23/2005

NE Time&Date: 12:58:04 09/15/2004

USER NAME: NSN

COMMAND: Getactivealarms BTSEP:NAME=BTSEP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



JOB: 51

PC Time&Date: 11:56:29 03/23/2005

NE Time&Date: 12:58:04 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


START ACTIVE ALARM ALIGNMENT BTSEP:

name = BTSEP:0

alignmentRequestNo = 0

notificationIdentifier = 288


JOB: 52

PC Time&Date: 11:56:29 03/23/2005

NE Time&Date: 12:58:04 09/15/2004

152DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


END ACTIVE ALARM ALIGNMENT BTSEP:

name = BTSEP:0

alignmentResult = SUCCESSFUL

correlatedNotifications =

correlatedNotificationId = 288

sourceObjectInstance = BTSEP:0


Operation Failed



Example of Command Execution:Getactivealarms BTSEP: NAME=BTSEP:0,

EVTYP= ENVIRONMENTAL_FAILURE_EVENT;

PERFTEST BTSEP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h PERFTEST BTSEP”





MORT MOT


PERFTEST BTSEP NAME=BTSEP:0..0 ,MORT=;

DN0933412 Issue 01153


BTSEP

Id:0900d805805b0cba

Test configuration has been set and the specified test has been started. The System response will not be addressed to the MOT but to the object BTSEP

JOB: 55

PC Time&Date: 11:56:59 03/23/2005

NE Time&Date: 12:59:48 09/15/2004

USER NAME: NSN

COMMAND: Perftest BTSEP:NAME=BTSEP:0,MORT=RACK:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = BTSEP:0,MORT=RACK:0;

tO = BTSETEST:1


JOB: 56

PC Time&Date: 11:57:07 03/23/2005

NE Time&Date: 12:58:42 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1



JOB: 57

PC Time&Date: 11:57:14 03/23/2005

NE Time&Date: 12:58:49 09/15/2004

154DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = BTSEP:0,MORT=RACK:0;

Availability Status = Failed



JOB: 58

PC Time&Date: 11:57:24 03/23/2005

NE Time&Date: 12:58:59 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:1

testOutcome = FAILED


MOT = BTSEP:0,MORT=RACK:0;

executedPhases =

PreliminaryTestsBtsep

BootEepromTestBtsep

SerialEepromTestBtsep

EndTestBtsep


JOB: 59

PC Time&Date: 11:57:24 03/23/2005

NE Time&Date: 12:58:59 09/15/2004

DN0933412 Issue 01155


BTSEP

Id:0900d805805b0cba

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1




Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases

156DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP

Operation Failed

This NACK-mesNSNe occurs in the following cases: MesNSNe cannot be performed, test not supported, capacity restrictions, physical configuration cannot be performed, object not locked.



Example of Command Execution:Perftest BTSEP:NAME=BTSEP:0,MORT=RACK:0/ACDCP:0;

PING BTSEP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h PING BTSEP”



Command Description:This command is used to ping the BTSE. After command execution the IP sends a response containing the following information:

• IP address of the target • Alive (TRUE/FALSE)


IPADR ipAddress


None.

Operation Failed

None.



....


A list of most probable fail probable causes is shown (max four mesNSNes)

PING BTSEP NAME=BTSEP:0..0 ,IPADR=;

DN0933412 Issue 01157


BTSEP

Id:0900d805805b0cba

Example of Command Execution:None.

REQCURSTASYN BTSEP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h REQCURSTASYN BTSEP”



Command Description:new information


ALGNSTEP alignmentStep


None.

Operation Failed

None.



SET BTSEP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SET BTSEP”



REQCURSTASYN BTSEP

NAME=BTSEP:0..0 [,ALGNSTEP=];

SET BTSEP NAME=BTSEP:0..0 [,ALIGCOBA=] [,ALRMSEVXXX=] [,CHIDT=] [,EAUTOREC=] [,EQUPOS=] [,GTWADRV4=] [,LOCNAME=] [,OVPTINS=] [,RXDIVSV=] [,SALUNAME=] [,SCLPRIOLST=] [,SWLDSAF=] [,VENDNA=];

158DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP

Command Description:This command sets general attributes of the BTS Site Equipment (BTSE). A BTSE is the physical equipment which is managed by one BTSM.


ALIGCOBA alignedCoba

ALRMSEVXXX alarmSeverityXXX

CHIDT changeOnIDT

EAUTOREC enableAutoRecovery

EQUPOS equipmentPosition

GTWADRV4 gatewayAddressIPv4

LOCNAME locationName

OVPTINS ovptInstalled

RXDIVSV enableRxDiversitySupervision

SALUNAME salesUniqueName

SCLPRIOLST serviceClassPrioList

SWLDSAF swLoadSafety

VENDNA vendorName


After command execution, a mesNSNe of Changed Attribute Event Report is displayed. A further mesNSNe indicates the result of the operation. An example of set command is the following:

JOB: 53

PC Time&Date: 11:56:35 03/23/2005

NE Time&Date: 12:58:10 09/15/2004

USER NAME: NSN

COMMAND: Set BTSEP:NAME=BTSEP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


DN0933412 Issue 01159


BTSEP

Id:0900d805805b0cba


• The supplier recommends the identification of swLoadSafety.

• The swLoadSafety will not be overwritten by a sw download via LMT Evolution

• There is no alignment to one of the SW loads stored on the Flexi BSC product family master database

• The swLoad must be stored in BTSE and must have at least once a connection with the Flexi BSC product family

• The identification of a SW load as the safety one is only accepted by the BTSE if the identified load has been activated and running on this BTSE before

• An update of the swLoadSafety attribute should be performed in each release; the swLoad of the previous release should be used as swLoadSafety

Example of Command Execution:Set BTSEP :NAME=BTSEP:0,ALRMSEVACDCP=CRITICAL,

ALRMSEVACT=CRITICAL,ALRMSEVCOBA=CRITICAL,

ALRMSEVBATTERY=CRITICAL,ALRMSEVCOSA=CRITICAL,

ALRMSEVCU=CRITICAL,ALRMSEVDIDCTMA=CRITICAL,

ALRMSEVDILNA=CRITICAL,ALRMSEVDUDCTMA=CRITICAL,

ALRMSEVDULNA=CRITICAL,ALRMSEVDUVSWR=CRITICAL,

ALRMSEVFCUMAIN= CRITICAL,ALRMSEVFCUTR= CRITICAL,

ALRMSEVFANP= CRITICAL,ALRMSEVFTNFP=CRITICAL,

ALRMSEVFVSWRP=CRITICAL,EQUPOS="020101",CHIDT=noChangeOnIDT,

EAUTOREC=disabled,LOCNAME="MUNICH",OVPTINS=true,RXDIVSV=enabled,

SALUNAME="AD042S7449E",SWLDSAF="HS011726.SWL:02-04-17-01-13-00_04-09-03",VENDNA="SIEMENS";

STOPTEST BTSEP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h STOPTEST BTSEP”



Command Description:This command requires the stop of the test on BTSE Plus.


MORT MOT

TESTNO testNo

STOPTEST BTSEP NAME=BTSEP:0..0 [,MORT=] [,TESTNO=];

160DN0933412 Issue 01


Id:0900d805805b0cba

BTSEP


Test has been stopped.

Operation Failed


Example of Command Execution:Stoptest BTSEP:NAME=BTSEP:0, MORT=RACK:0/ACDCP:0,TESTNO=23;

Test has not been stopped. This NACK-mesNSNe can occur when the specified test is not running or in case of test which cannot be stopped.

TEST REPORT: The TEST REPORT provides a list of executed, failed and skipped phases.

DN0933412 Issue 01161


BTSETEST

Id:0900d805805b0cbc

BTSETESTThe TEST locates a test object in the system. This object is created when an activation of a diagnostic occurs.

GET BTSETEST

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BTSETEST h GET BTSETEST”



Command Description:This command displays the attributes related to a test. The values 1-255 will be used for the allocated 'test object instance' to keep track of the related 'MORTs'.



MORT MOT

TESTMON testMonitor

TESTOUT testOutcome

TESTST testState


The output includes a test report containing "Executed Phases", "Failed Phases", "Tes-tOutcome", "Test Termination", "MOT". An example of "Test Report" is the following:

JOB: 19

PC Time&Date: 11:32:14 03/23/2005

NE Time&Date: 11:30:55 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report BTSETEST:

GET BTSETEST NAME=BTSETEST:1..255 [,REQATTL=MORT, TESTMON, TESTOUT, TESTST];

162DN0933412 Issue 01


Id:0900d805805b0cbc

BTSETEST

name = BTSETEST:1



MOT = RACK:0/CU:2

executedPhases =

PreliminaryTestsAct

CheckAlarmStatusAct

EndTestAct


Operation Failed

The GETTEST command has not been successfully executed.

A general NACK will indicate possible errors or a specific NACK strictly related to the single command is possible.


• Only intrusive tests are supported

• For TESTOUT attribute the value inconclusive is possible only during the start phase. It indicates that no "Pass" or "Fail" outcome has been determined yet

Example of Command Execution:Get BTSETEST :NAME=BTSETEST:1,REQATTL=MORTS&TESTMON&

TESTOUT&TESTST;

DN0933412 Issue 01163


BTSM

Id:0900d805805b0cc0

BTSMThe BTSM object provides services to control the functionalities of one or more BR BTS NEs (BTSplus mainline, eMicro, BTSplus basic) located at the same site. It performs all the operation and maintenance functions common to all transceivers.

ACTIVATE BTSM

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h ACTIVATE BTSM”

Applicability:Phase 1 and Phase 2 and Phase 3.


Command Description:This command activates one of the three SW loads stored in the BTSE.


FILEID fileId

FILESWV fileVersion


Download START:

JOB: 181

PC Time&Date: 12:06:21 03/23/2005

NE Time&Date: 13:07:57 09/15/2004

USER NAME: NSN

COMMAND: Activate BTSM:NAME=BTSM:0,FILEID="HS011726.SWL:01-04-16-01-59-00_03-11-18";

SW RELEASE: 01-04-17-01-26-51_05-02-23


fileId = "HS011722.SWL"

fileVersion = "01-04-17-01-26-51_05-02-23"


ACTIVATE BTSM NAME=BTSM:0..0 ,FILEID= ,FILESWV=;

164DN0933412 Issue 01


Id:0900d805805b0cc0

BTSM

JOB: 182

PC Time&Date: 12:06:21 03/23/2005

NE Time&Date: 13:07:57 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


ID_Message


SW ACTIVATED REPORT:

(a report is displayed)

Operation Failed

(Invalid SVR)


• If an incorrect FileVersion is given the system rejects the command

• This command is followed by a reset of the BTSE

• If the currently running SW version is activated by the command, the SW will be dis-tributed again in the BTSE

• If the intended SW is corrupted, the BTSE first tries to come up with the safety load; if this is not successful, the BTSE tries to start the third SWload, the dischargeable one

• The FileId is a parameter used within the SW download procedures and not of the type 'GET'. The corresponding attribute is SWLCFID and is related only to the swLoad-header file. All characters of the ASCII string are to be in upper case. However, the SW parts in the BTSE handling the file Id are to be case tolerant

• The FileVersion is a parameter used within the SW download procedures and not of the type 'GET'. The corresponding attribute is SWLCVER which is coded identical as File Version. However the allowed values for 'hh' are different because SWLCVER is related only to the swLoad-header file

Example of Command Execution:Activate BTSM:NAME=BTSM:0,FILEID="vHS011722.SWL",FILESWV="02-04-16-

01-05-01_03_02_25"

DN0933412 Issue 01165


BTSM

Id:0900d805805b0cc0


Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h ACTIVATE_DELAYED BTSM”



Command Description:This command activates one of the three SW loads stored in the BTSE with a defined delayed time.


FILEID fileId

FILESWV fileVersion

TIMEDELAY timeDelay(sec)


USER NAME: NSN

COMMAND: Activate_delayed BTSM:NAME=BTSM:0,FIL-EID="123456789123",FILESWV="01-01-16-00-56-00_03-10-16",TIMEDELAY=3;

SW RELEASE: 01-01-17-00-26-51_05-02-23


Operation Failed

None.


Example of Command Execution:Activate_delayed BTSM:NAME=BTSM:0,FILEID="123456789123",FILESWV="01-01-16-00-56-00_03-10-16",TIMEDELAY=3;

CONNBSC BTSM

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h CONNBSC BTSM”


NAME=BTSM:0..0 ,FILEID= ,FILESWV= ,TIMEDELAY=;

CONNBSC BTSM NAME=BTSM:0..0;

166DN0933412 Issue 01


Id:0900d805805b0cc0

BTSM



Command Description:This command starts the connection between the BTSplus mainline and the Flexi BSC product family and is followed by a transition from LMT Evolution Phase 2 to LMT Evo-lution Phase 3.



The command has been correctly executed.

JOB: 180

PC Time&Date: 12:06:20 03/23/2005

NE Time&Date: 00:00:00 00/00/0

USER NAME: NSN

COMMAND: Connbsc BTSM:NAME=BTSM:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



SWACTIVATED REPORT

Operation Failed

The command has not been correctly executed.


• After the execution of this command, the BTSM will be in the administrative state "Unlocked"

• If one of the "Minimal Parameters" of the BTSE is in the locked state, no connection to the BSC is possible

• The CCLK accuracy must be "Medium" or "High" before the connection to the BSC is possible

• The BTSM attribute TEI has to be defined

• The BPORT object has to be defined previous LAPDLE

• The LAPDLE object has to be defined

DN0933412 Issue 01167


BTSM

Id:0900d805805b0cc0

• For Radio Commander purposes the SALUNAME and TYPRACK attributes have to be set. Otherwise the OMC cannot identify the BTSE

Example of Command Execution:Connbsc BTSM:NAME=BTSM:0;

DISCBSC BTSM

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h DISCBSC BTSM”



Command Description:This command disconnects the BTSplus main line from the Flexi BSC product family and is followed by a transition from LMT Evolution Phase 3 to LMT Evolution Phase 2.



The command has been correctly executed.

JOB: 179

PC Time&Date: 12:06:20 03/23/2005

NE Time&Date: 00:00:00 00/00/0

USER NAME: NSN

COMMAND: Discbsc BTSM:NAME=BTSM:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed

The command has not been correctly executed.

DISCBSC BTSM NAME=BTSM:0..0;

168DN0933412 Issue 01


Id:0900d805805b0cc0

BTSM


• If a connection to the BSC is established, the BTSM must be in the administrative state "Locked"

• If the SW in BTSM in BSC is not the same like in BTSE, BTSM cannot be locked

(At BSC disk no SW is available) and you cannot come to Phase 2. To come to phase 2 you have to make a COBA manual reset

Example of Command Execution:Discbsc BTSM:NAME=BTSM:0;

FWUPGRADE BTSM

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h FWUPGRADE BTSM”





FILEID fileId

FILEFWV fwVersion

LRU lru

ACTVINC activationIncluded


None.

Operation Failed

None.



FWUPGRADE BTSM NAME=BTSM:0..0 ,FILEID= ,FILEFWV= [,LRU=] [,ACT-VINC=];

DN0933412 Issue 01169


BTSM

Id:0900d805805b0cc0

GET BTSM NOSWL

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h GET BTSM NOSWL”



Command Description:This command displays the attributes related to the BTSM (BTS Site Manager).



ABISLKSAT sAbisLinkSatellited

ABISTIME sAbisExternalTime

ASUBLKSAT sAsubLinkSatellited



DYNTRACGRAN dynTraceGranularity

EINTSITSYN enableInterSiteSync

EMT1 emergencyTimer1(min)

EMT2 emergencyTimer2(min)

LPDLMSAT lapdleLinkSatellited

OMLAPDRT omLapdRelTimer(sec)



TEI tei

TSLPOOL tslPool

SHLAPDIT shortLapdIntTimer(sec)


After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of get noswl command is the following:

JOB: 20

GET BTSM NOSWL NAME=BTSM:0..0 [,REQATTL=ABISLKSAT, ABISTIME, ASUBLKSAT, AST, AVS, DYNTRACGRAN, EINTSITSYN, EMT1, EMT2, LPDLMSAT, OMLAPDRT, OST, RELEQUI-POBJ, TEI, TSLPOOL, SHLAPDIT];

170DN0933412 Issue 01


Id:0900d805805b0cc0

BTSM

PC Time&Date: 11:33:34 03/23/2005

NE Time&Date: 11:31:25 09/15/2004

USER NAME: NSN

COMMAND: Get BTSM NOSWL:NAME=BTSM:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




dynTraceGranularity = 1

emergencyTimer1(min) = 10

emergencyTimer2(min) = 0

enableInterSiteSync = FALSE

lapdleLinkSatellited = terrestrialConnection

omLapdRelTimer(sec) = 30



HMO = BTSEP:0

sAbisExternalTime =

Year = 2003

Month = Jan

Day = 1

Hour = 20

Minute = 16

Second = 3

sAbisLinkSatellited = terrestrialConnection

sAsubLinkSatellited = terrestrialConnection

shortLapdIntTimer(sec) = 15

tei = 0

JOB: 20

tslPool =

TS01 TS02 TS03 TS04 TS05 TS06 TS07 TS08



TS25 TS26 TS27 TS28 TS29 TS30 TS31

BPORT0

DN0933412 Issue 01171


BTSM

Id:0900d805805b0cc0

0000 0000 0000 0000 1111 1111 0000 0000

0000 0000 0000 0000 0000 0000 0000 0000

0000 0000 0000 0000 0000 0000 0000 0000

0000 0000 0000 0000 0000 0000 0000


Operation Failed



• In order to decide whether a "fast" alignment instead of a "full" one must be started, the BSC reads the shortLAPDIntTimer and increases it of a value currently fixed to 30 seconds; for this reason the suggested values are

shortLAPDIntTimer:

• max. attribute length for attribute tslPool increased to 136

Example of Command Execution:Get BTSM NOSWL:NAME=BTSM:0,REQATTL=ABISLKSAT&ABISTIME&

AST&ASUBLKSAT&AVS&DYNTRACGRAN&EMT1&EMT2&EINTSITSYN&

LPDLMSAT&OMLAPDRT&OST&RELEQUIPOBJ&SHLAPDIT&TEI&TSLPOOL;

GET BTSM OVERLOAD

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h GET BTSM OVERLOAD”






LAPDOVLTH lapdOverloadThresholds(%)

LAPDOVLT lapdOverloadTimer(sec)


GET BTSM OVERLOAD NAME=BTSM:0..0 ,REQATTL=LAPDOVLTH, LAPDOVLT;

172DN0933412 Issue 01


Id:0900d805805b0cc0

BTSM

After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of get overload command is the following:

JOB: 23

PC Time&Date: 11:33:34 03/23/2005

NE Time&Date: 11:31:25 09/15/2004

USER NAME: NSN

COMMAND: Get BTSM OVERLOAD:NAME=BTSM:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


lapdOverloadTimer = 10

lapdOverloadThresholds(%) =

firstLevUpperThreshold = 80

firstLevLowerThreshold = 70

secLevUpperThreshold = 90

secLevLowerThreshold = 80

lapdOverloadTRXList =


Operation Failed



• The number of possible TRX instances for attribute lapdOverloadTrxList increased to 48.

Example of Command Execution:Get BTSM OVERLOAD:NAME=BTSM:0,REQATTL=LAPDOVLT&LAPDOVLTH;

GET BTSM SWL

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h GET BTSM SWL”



GET BTSM SWL NAME=BTSM:0..0 ,REQATTL=SWLCFID, SWLCVER;

DN0933412 Issue 01173


BTSM

Id:0900d805805b0cc0




SWLCFID swLoadCurrentFileId

SWLCVER swLoadCurrentFileVersion


After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of get swl command is the following:

JOB: 178

PC Time&Date: 12:06:19 03/23/2005

NE Time&Date: 13:03:28 09/15/2004

USER NAME: NSN

COMMAND: Get BTSM SWL:NAME=BTSM:0

SW RELEASE: 01-04-17-01-26-51_05-02-23


superordinateBscSwLoadCurrentVersion = "02-08-01-01-00-30_04-12-14"

swLoadCurrentFileId = "hs011713.SWL"

swLoadCurrentFileVersion = "01-04-17-01-26-51_05-02-23"


Operation Failed



Example of Command Execution:Get BTSM SWL:NAME=BTSM:0,SWLCFID&SWLCVER;

174DN0933412 Issue 01


Id:0900d805805b0cc0

BTSM

LOCKREQUEST BTSM

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h LOCKREQUEST BTSM”



Command Description:This command sends a request to the BSC for immediate locking of the BTSM.



The specified change of administrative state has been perfomed.

JOB: 56

PC Time&Date: 11:57:07 03/23/2005

NE Time&Date: 12:58:42 09/15/2004

USER NAME: NSN

COMMAND: Lockrequest BTSM:NAME=BTSM:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




This provides information about the administrative state, the operational state and the availability status every time a state change occurs.

Operation Failed



• This command should only be used when the system is in real danger. The Shutdown command is preferred

LOCKREQUEST BTSM NAME=BTSM:0..0;

DN0933412 Issue 01175


BTSM

Id:0900d805805b0cc0

Example of Command Execution:Lockrequest BTSM:NAME=BTSM:0;

SET BTSM

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h SET BTSM”



Command Description:This command sets the attributes of the BTS_Site_Manager (BTSM). The BTS Site Manager represents the O&M functionality related to a site and not to any specific BTSplus mainline. A site is a logical grouping of one or more BTSplus mainlines at a single physical location with common management needs. This configuration has to match with the related functional object in the Flexi BSC product family.


ABISLKSAT sAbisLinkSatellited

ABISTIME sAbisExternalTime



JOB: 177

PC Time&Date: 12:06:04 03/23/2005

NE Time&Date: 13:07:40 09/15/2004

USER NAME: NSN

COMMAND: Set BTSM:NAME=BTSM:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed

SET BTSM NAME=BTSM:0..0 [,ABISLKSAT=] [,ABISTIME=];

176DN0933412 Issue 01


Id:0900d805805b0cc0

BTSM



• The BPortNumber must be the same for all abisChannel attributes of the CHAN instances of the same TRX

• Except for timeslot 0 (Synchronization Time Slot) all time slots can be used to support both, traffic or signalling channels

• The ABISTIME attribute is useful for longer operation on site. In transition from Phase 2 to Phase 3 this attribute is overwritten by the BSC

• Setting of ABISLKSAT in the BTSE and of LPDLMSAT in BSC must be homoge-nous:

- terrestrialConnection (corresponds in the BSC to 'LPDLMSAT=FALSE')

- satelliteConnection (corresponds in the BSC to 'LPDLMSAT=TRUE')

Example of Command Execution:Set BTSM:NAME=BTSM:0,ABISLKSAT=terrestrialConnection, ABISTIME=1999-Oct-28-18-0-0

SHUTDOWN BTSM

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h SHUTDOWN BTSM”



Command Description:This command will not allow new telecom traffic to be transferred to the BTSM (no incoming handover, no paging, no call set up). When all calls are terminated, the transfer to "Locked" will be performed automatically.




JOB: 59

PC Time&Date: 11:57:24 03/23/2005

NE Time&Date: 12:58:59 09/15/2004

SHUTDOWN BTSM NAME=BTSM:0..0;

DN0933412 Issue 01177


BTSM

Id:0900d805805b0cc0

USER NAME: NSN

COMMAND: Shutdown BTSM:NAME=BTSM:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





Operation Failed



Example of Command Execution:Shutdown BTSM:NAME=REMINV:0;

UNLOCKREQUEST BTSM

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h UNLOCKREQUEST BTSM”



Command Description:This command sends a request to the BSC for the unlocking of the BTSM. The BTSM will be able to handle telecom traffic.




JOB: 57

UNLOCKREQUEST BTSM

NAME=BTSM:0..0;

178DN0933412 Issue 01


Id:0900d805805b0cc0

BTSM

PC Time&Date: 11:57:14 03/23/2005

NE Time&Date: 12:58:49 09/15/2004

USER NAME: NSN

COMMAND: Unlockrequest BTSM:NAME=BTSM:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





Operation Failed



• Unlocking of BTSM causes a full BTSplus mainline alignment

• In case of issuing BTSE configuration commands during an alignment, a new align-ment will be started

Example of Command Execution:Unlockrequest BTSM:NAME=BTSM:0;

DN0933412 Issue 01179


CESPW

Id:0900d805805b0cc2

CESPWThe CESPW object represents one UDP stream which is both received and simultane-ously transmitted to the peer. The object is introduced for the following purposes:

• Setting of the UPD port numbers

• Configuration of the mapping between CESoPSN payload and internal TDM highways

• Adjustment of packetization latency (transmission) and jitter buffer (reception)

CREATE CESPW

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h CREATE CESPW”



Command Description:This command adds the CESPW to the BTSE data base.


PWNAME pwName

LOCLUDP localUdpPort

PEERUDPPORT peerUdpPort

TDMAP tdmMapping

PKTLAT packetizationLatency

MAXPDV maxPdv(ms)


After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of create command is the following:JOB: 60

PC Time&Date: 02.04.2008 09:10:46 +02:00.

NE Time&Date: 01.01.1990 18:26:24 +00:00

USER NAME: NSN

COMMAND: Create CESPW:NAME=CESPW:0,LOCLUDP=49200,PEERUDP=

49200,TDMAP=1-2-3-4-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0;

SW RELEASE: 01-04-19-01-08-CR_08-03-31

CREATE CESPW NAME=CESPW:0..7 [,PWNAME=] ,LOCLUDP= ,PEERUD-PPORT= ,TDMAP= [,PKTLAT=] [,MAXPDV=];

180DN0933412 Issue 01


Id:0900d805805b0cc2

CESPW


localUdpPort = 49200

peerUdpPort = 49200

tdmMapping =

pTs1 = 1

pTs2 = 2

pTs3 = 3

pTs4 = 4

pTs5 = 0

pTs6 = 0

pTs7 = 0

pTs8 = 0

pTs9 = 0

pTs10 = 0

pTs11 = 0

pTs12 = 0

pTs13 = 0

pTs14 = 0

pTs15 = 0

pTs16 = 0

pTs17 = 0

pTs18 = 0

pTs19 = 0

pTs20 = 0

pTs21 = 0

pTs22 = 0

pTs23 = 0

pTs24 = 0

pTs25 = 0

pTs26 = 0

pTs27 = 0

pTs28 = 0

pTs29 = 0

pTs30 = 0

pTs31 = 0


Operation Failed

None.

DN0933412 Issue 01181


CESPW

Id:0900d805805b0cc2


• The creation of a CESPW instance is rejected if no CESTUNNEL has been created before

Example of Command Execution:Create CESPW:NAME=CESPW:0,LOCLUDP=49153,MAXPDV=16,PEER-UDP=49152,PKTLAT=m1000,PWN="trial1",TDMAP=1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1;

DELETE CESPW

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h DELETE CESPW”



Command Description:This command deletes the CESPW from the BTSE data base.




JOB: 503.

PC Time&Date: 05.06.2008 13:45:42 +02:00

NE Time&Date: 01.01.1990 00:42:25 +00:00

USER NAME: NSN

COMMAND: Delete CESPW:NAME=CESPW:7;

SW RELEASE: 01-04-19-01-09-ZS_08-06-05



Operation Failed

None.


DELETE CESPW NAME=CESPW:0..7;

182DN0933412 Issue 01


Id:0900d805805b0cc2

CESPW

Example of Command Execution:Delete CESPW:NAME=CESPW:0;

GET CESPW

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h GET CESPW”



Command Description: This command displays the attributes of the CESPW.



ALS alarmStatus






PWNAME pwName



TDMAP tdmMapping


MAXPDV maxPdv(ms)



JOB: 9

PC Time&Date: 02.10.2008 09:06:43 +02:00

NE Time&Date: 02.10.2008 06:50:36 +01:00

USER NAME: NSN

GET CESPW NAME=CESPW:0..7 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, PWNAME, LOCLUDP, PEERUDP-PORT, TDMAP, PKTLAT, MAXPDV];

DN0933412 Issue 01183


CESPW

Id:0900d805805b0cc2

COMMAND: Get CESPW:NAME=CESPW:0;

SW RELEASE: 01-04-19-01-12-ZT_08-09-29







relatedFuncObjects = Null

pwName = "Null"

localUdpPort = 49300

peerUdpPort = 49300

tdmMapping =

pTs1 = 1

pTs2 = 2

pTs3 = 3

pTs4 = 4

pTs5 = 5

pTs6 = 0

pTs7 = 0

pTs8 = 0

pTs9 = 0

pTs10 = 0

pTs11 = 0

pTs12 = 0

pTs13 = 0

pTs14 = 0

pTs15 = 0

pTs16 = 0

pTs17 = 0

pTs18 = 0

pTs19 = 0

pTs20 = 0

pTs21 = 0

pTs22 = 0

pTs23 = 0

pTs24 = 0

pTs25 = 0

pTs26 = 0

184DN0933412 Issue 01


Id:0900d805805b0cc2

CESPW

pTs27 = 0

pTs28 = 0

pTs29 = 0

pTs30 = 0

pTs31 = 0

packetizationLatency = m1000

maxPdv(ms) = 2.000


Operation Failed

None.


Example of Command Execution:Get CESPW:NAME=CESPW:0;REQATTL=ALS&AST&AVS&OST&PRS&RELFUN-COBJ&PWN&LOCLUDP&PEERUDP&TDMAP&PKTLAT&MAXPDV;

LOCK CESPW

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h LOCK CESPW”



Command Description:This command changes the administrative state of CESPW.



The specified change of administrative state has been perfomed. An example of lock command is the following:

JOB: 29

PC Time&Date: 05.06.2008 13:06:00 +02:00

NE Time&Date: 01.01.1990 00:02:44 +00:00

USER NAME: NSN

COMMAND: Lock CESPW:NAME=CESPW:0;

SW RELEASE: 01-04-19-01-09-ZS_08-06-03

LOCK CESPW NAME=CESPW:0..7;

DN0933412 Issue 01185


CESPW

Id:0900d805805b0cc2




Operation Failed

None.


Example of Command Execution:Lock CESPW:NAME=CESPW:0;

SET CESPW

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h SET CESPW”



Command Description:This command sets the attributes of CESPW to the BTSE data base.


PWNAME pwName



TDMAP tdmMapping


MAXPDV maxPdv(ms)


After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of set command is the following:

JOB: 32

PC Time&Date: 05.06.2008 13:06:09 +02:00

NE Time&Date: 01.01.1990 00:02:53 +00:00

USER NAME: NSN

SET CESPW NAME=CESPW:0..7 [,PWNAME=] [,LOCLUDP=] [,PEER-UDPPORT=] [,TDMAP=] [,PKTLAT=] [,MAXPDV=];

186DN0933412 Issue 01


Id:0900d805805b0cc2

CESPW

COMMAND: Set CESPW:NAME=CESPW:0,MAXPDV=0.125;

SW RELEASE: 01-04-19-01-09-ZS_08-06-03


maxPdv = 0.125


Operation Failed

None.


• Any modification of the mapping is allowed only if the CESPW has been previously locked

Example of Command Execution:Set CESPW:NAME=CESPW:0,LOCLUDP=49152,MAXPDV=16,PEER-UDP=49152,PKTLAT=m1000,PWN="trial1",TDMAP=1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1-1;

UNLOCK CESPW

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h UNLOCK CESPW”



Command Description:This command changes the administrative state of CESPW.



The specified change of administrative state has been perfomed. An example of unlock command is the following:

JOB: 84

PC Time&Date: 05.06.2008 13:17:19 +02:00NE Time&Date: 01.01.2000 00:14:03 +00:00

USER NAME: NSN

COMMAND: Unlock CESPW:NAME=CESPW:0;

SW RELEASE: 01-04-19-01-09-ZS_08-06-03


UNLOCK CESPW NAME=CESPW:0..7;

DN0933412 Issue 01187


CESPW

Id:0900d805805b0cc2



Operation Failed

None.


Example of Command Execution:Unlock CESPW:NAME=CESPW:0;

188DN0933412 Issue 01


Id:0900d805805b0cc4

CESTUNNEL

CESTUNNELThis object represents the PSN tunnel. As the BTSE is uniquely connected to one Flexi BSC product family there is only one CESTUNNEL instance per BTSE. The CESTUN-NEL object is introduced for the following purposes:

• Setting of the local (BTSE) and peer IP address

• Setting of attributes which apply for all pseudo wires

CREATE CESTUNNEL

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h CREATE CESTUNNEL”



Command Description:This command adds the CESTUNNEL to the BTSE data base.


LOCALADDR localAddress

PEERADDR peerAddress

VLANID vlanId

LOSPKTTH lostPacketThreshold

ALRMPERT alarmPersistencyTime

ALRMCLET alarmClearanceTime

NTWTYPC networkTypeCompensation

PNGF pingFrequency

PNGPKT pingPacketSize


After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of cestunnel command is the following:

JOB:59

PC Time&Date: 09.10.2008 09:46:28 +02:00

NE Time&Date: 01.01.1990 00:08:37 +00:00

CREATE CESTUNNEL NAME=CESTUNNEL:0..0 ,LOCALADDR= ,PEERADDR= [,VLANID=] [,LOSPKTTH=] [,ALRMPERT=] [,ALRMCLET=] [,NTWTYPC=] [,PNGF=] [,PNGPKT=];

DN0933412 Issue 01189


CESTUNNEL

Id:0900d805805b0cc4

USER NAME: NSN

COMMAND: Create CESTUNNEL:NAME=CESTUNNEL:0,LOCALADDR="

192.168.3.23",PEERADDR="192.168.3.25",VLANID=<NULL>;

SW RELEASE: 03-04-19-06-11-06_08-10-08


localAddress = "192.168.3.23"

peerAddress = "192.168.3.25"

vlanId = Null


Operation Failed

None.


Example of Command Execution:Create CESPW:NAME=CESPW:0,LOCLUDP=49200,MAXPDV=16,PEERUDPPORT= 49200,PKTLAT=m1000,PWNAME="trial1",TDMAP=0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0;

DELETE CESTUNNEL

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h DELETE CESTUNNEL”



Command Description:This command deletes the CESTUNNEL from the BTSE data base.


System Responses:Operation Completed.

After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of delete command is the following

JOB: 48

PC Time&Date: 09.10.2008 09:49:00 +02:00

NE Time&Date: 01.01.1990 00:11:09 +00:00

DELETE CESTUNNEL NAME=CESTUNNEL:0..0;

190DN0933412 Issue 01


Id:0900d805805b0cc4

CESTUNNEL

USER NAME: NSN

COMMAND: Delete CESTUNNEL:NAME=CESTUNNEL:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08



Operation Failed.

None.


• CESTUNNEL deletion is rejected if a CESPW object exists

Example of Command Execution:Delete CESTUNNEL:NAME=CESTUNNEL:0;

GET CESTUNNEL

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h GET CESTUNNEL”



Command Description:This command displays the attributes of the CESTUNNEL.



ALS alarmStatus








VLANID vlanId


GET CESTUNNEL NAME=CESTUNNEL:0..0 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, LOCALADDR, PEERADDR, VLANID, LOSPKTTH, ALRMPERT, ALRMCLET, NTWTYPC, PNGF, PNGPKT];

DN0933412 Issue 01191


CESTUNNEL

Id:0900d805805b0cc4




PNGF pingFrequency




JOB: 75

PC Time&Date: 09.03.2009 09:46:36 +02:00

NE Time&Date: 01.01.1990 00:08:45 +00:00

USER NAME: NSN

COMMAND: Get CESTUNNEL:NAME=CESTUNNEL:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08








localAddress = "192.168.3.23"

peerAddress = "192.168.3.25"

vlanId = Null

lostPacketThreshold = 1

alarmPersistencyTime = 3

alarmClearanceTime = 10

networkTypeCompensation = 0

pingFrequency = 0

pingPacketSize = TRAFFIC


Operation Failed

None.


Example of Command Execution:Get CESTUNNEL:NAME=CESTUN-NEL:0,REQATTL=ALS&AST&AVS&OST&PRS&RELFUNCOBJ&ALRMCLET&ALRM-

192DN0933412 Issue 01


Id:0900d805805b0cc4

CESTUNNEL

PERT&LOCALADDR&LOSPKTTH&NTWTYPC&PEERADDR&PNGF&PNGPKT&VLANID;

LOCK CESTUNNEL

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h LOCK CESTUNNEL”



Command Description:This command changes the administrative state of CESPW object.



The specified change of administrative state has been performed. An example of lock command is the following:

JOB: 39

PC Time&Date: 09.10.2008 09:46:42 +02:00

NE Time&Date: 01.01.1990 00:08:51 +00:00

USER NAME: NSN

COMMAND: Lock CESTUNNEL:NAME=CESTUNNEL:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08




Operation Failed.

None.


Example of Command Execution:Lock CESPW:NAME=CESPW:0;

LOCK CESTUNNEL NAME=CESTUNNEL:0..0;

DN0933412 Issue 01193


CESTUNNEL

Id:0900d805805b0cc4

SET CESTUNNEL

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h SET CESTUNNEL”



Command Description:This command sets the attributes of CESTUNNEL object.




VLANID vlanId





PNGF pingFrequency




JOB: 77

PC Time&Date: 09.10.2009 09:47:56 +02:00

NE Time&Date: 01.01.1990 00:10:05 +00:00

USER NAME: NSN

COMMAND: Set CESTUNNEL:NAME=CESTUNNEL:0,ALRMCLET=4,ALRMPERT=

5,LOSPKTTH=55,PNGF=12,PNGPKT=SMALL,VLANID=02;

SW RELEASE: 03-04-19-06-11-06_08-10-08


vlanId = 2

lostPacketThreshold = 55

SET CESTUNNEL NAME=CESTUNNEL:0..0 [,LOCALADDR=] [,PEERADDR=] [,VLANID=] [,LOSPKTTH=] [,ALRMPERT=] [,ALRMCLET=] [,NTWTYPC=] [,PNGF=] [,PNGPKT=];

194DN0933412 Issue 01


Id:0900d805805b0cc4

CESTUNNEL

alarmPersistencyTime = 5

alarmClearanceTime = 4

pingFrequency = 12

pingPacketSize = SMALLEND OF OUTPUT FOR JOB 77

Operation Failed.

None.


Example of Command Execution:Set CESTUNNEL:NAME=CESTUNNEL:0,ALRMCLET=4,ALPERT=5,LOSPKTTH= 55,PNGF=12,PNGPKT=SMALL,VLANID=02;?

UNLOCK CESTUNNEL

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h UNLOCK CESTUNNEL”



Command Description:This command changes the administrative state of CESTUNNEL object.




JOB: 47

PC Time&Date: 09.10.2008 09:49:48 +02:00

NE Time&Date: 01.01.1990 00:11:57 +00:00

USER NAME: NSN

COMMAND: Unlock CESTUNNEL:NAME=CESTUNNEL:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08




Operation Failed

UNLOCK CESTUNNEL NAME=CESTUNNEL:0..0;

DN0933412 Issue 01195


CESTUNNEL

Id:0900d805805b0cc4

None.


Example of Command Execution:Unlock CESTUNNEL:NAME=RACK:0/CESTUNNEL:0

196DN0933412 Issue 01


Id:0900d805805b0cc6

CHAN

CHANThe CHAN object represents the radio time slot in which the radio carrier is subdivided into time sharing; it can be differently configured depending on its usage for the tele-phone application software (full rate or half rate traffic channels, dedicated or common control channels).

GET CHAN

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h TRX h CHAN h GET CHAN”



Command Description:This command displays the physical radio channel with its specific attributes which allows logical channels to be mapped onto physical radio channels.



ABISCH abisChannel



CHTYPE channelCombination

EXTMODE extendedMode

HSN hoppingSequenceNumber

MAIO maio

MOBALLOC arfcnList



TSC trainingSequenceCode



GET CHAN NAME=BTS:0..11/TRX:0..23/CHAN:0..7 [,REQATTL=ABISCH, AST, AVS, CHTYPE, EXTMODE, HSN, MAIO, MOBALLOC, OST, RELEQUIPOBJ, TSC];

DN0933412 Issue 01197


CHAN

Id:0900d805805b0cc6

JOB: 17

PC Time&Date: 11:33:17 03/23/2005

NE Time&Date: 11:31:08 09/15/2004

USER NAME: NSN

COMMAND: Get CHAN:NAME=BTS:0/TRX:0/CHAN:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




channelCombination = MAINBCCH

extendedMode = FALSE

hoppingSequenceNumber = 0

maio = 0

arfcnList =



trainingSequenceCode = TSC_is_BCC_of_BSIC


Operation Failed



Example of Command Execution:Get CHAN:NAME=BTS:0/TRX:0/CHAN:0,REQATTL=AST&AVS&CHTYPE&

EXTMODE&HSN&MAIO&MOBALLOC&OST&RELEQUIPOBJ&TSC;

198DN0933412 Issue 01


Id:0900d805805b0cc8

COBA

COBAThe COBA module controls the entire BTSplus mainline, generates the system clocks, provides for up to 2 Abis-interfaces to the Flexi BSC product family or other BTSplus mainlines, routes the Abis-data to up to 8 Carrier Agents, provides for an interface to the LMT Evolution/OTP, handles and processes the O&M-messages.

CREATE COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h CREATE COBA”



Command Description:This command displays the attributes of the COBA (Core Basis module).


ALRMCOUNTER alarmCount

ALRMT1/2/3 alarmTiming1(sec)/2/3

EFCUSUP enableFcuSupport



JOB: 158

PC Time&Date: 16:45:36 03/23/2005

NE Time&Date: 16:43:30 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



CREATE COBA NAME=RACK:0..7/COBA:0..1 [,ALRMCOUNTER=] [,ALRMT1/2/3=] [,EFCUSUP=];

DN0933412 Issue 01199


COBA

Id:0900d805805b0cc8

name = RACK:0/COBA:1



JOB: 159

PC Time&Date: 16:45:36 03/23/2005

NE Time&Date: 16:43:30 09/15/2004

USER NAME: NSN

COMMAND: Create COBA:NAME=RACK:0/COBA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 71

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create COBA:NAME=RACK:0/COBA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23


Object instance unknown (-9)



• Only COBA:1 can be created

200DN0933412 Issue 01


Id:0900d805805b0cc8

COBA

Example of Command Execution:Create COBA:NAME=RACK:0/COBA:1,ALRMCOUNTER=234,ALRMT1=23,

ALRMT2=34,ALRMT3=45, EFCUSUP=TRUE;

DELETE COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h DELETE COBA”







JOB: 182

PC Time&Date: 16:48:02 03/23/2005

NE Time&Date: 16:45:56 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/COBA:1



JOB: 183

DELETE COBA NAME=RACK:0..7/COBA:0..1;

DN0933412 Issue 01201


COBA

Id:0900d805805b0cc8

PC Time&Date: 16:48:02 03/23/2005

NE Time&Date: 16:45:56 09/15/2004

USER NAME: NSN

COMMAND: Delete COBA:NAME=RACK:0/COBA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• Only COBA:1 can be deleted

• COBA:1 must be locked in Phase 3 before deletion

Example of Command Execution:Delete COBA:NAME=RACK:0/COBA:1;

GET COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h GET COBA”








GET COBA NAME=RACK:0..7/COBA:0..1 [,REQATTL=ALRMCOUN-TER, ALRMT1/2/3, ALS, AST, AVS, BCPBL, BSWVER, EFCUSUP, OST, PRS, RELFUNCOBJ, SLOTNO, STD-BYST];

202DN0933412 Issue 01


Id:0900d805805b0cc8

COBA

ALS alarmStatus



BCPBL boardCapability

BSWVER bootSoftwareVersion





SLOTNO slotNo

STDBYST standbyStatus



JOB: 163

USER NAME: NSN

COMMAND: Get COBA:NAME=RACK:0/COBA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


acPeriod = 20

alarmCount = 32

alarmTiming1(sec) = 20

alarmTiming2(sec) = 1

alarmTiming3(*5min) = 1




boardCapability = twoAbisLines

bootSoftwareVersion = "BTBBCX01.SWI:01-01-11-00-18-00_04-06-13"

enableFcuSupport = FALSE



slotNo = leftCOBA

standbyStatus = ProvidingService

DN0933412 Issue 01203


COBA

Id:0900d805805b0cc8


Operation Failed



• COBA:0 is the one with "Providing Service" Status, COBA:1 is in Standby Status

Example of Command Execution:Get COBA:NAME=RACK:0/COBA:0,REQATTL=ACPER&ALRMCOUNTER&

ALRMT1& ALRMT2&ALRMT3&ALS&AST&AVS&BCPBL&BSWVER&CCLKACC&

EFCUSUP&OST&PRS&SLOTNO&STDBYST;


Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h GETRELATIONSHIP COBA”







After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of getrela-tionship command is the following:

JOB: 164

PC Time&Date: 15:08:34 03/23/2005

NE Time&Date: 16:11:29 09/15/2004


NAME=RACK:0..7/COBA:0..1;

204DN0933412 Issue 01


Id:0900d805805b0cc8

COBA

USER NAME: NSN

COMMAND: Getrelationship COBA:NAME=RACK:0/COBA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



Example of Command Execution:Getrelationship COBA:NAME=RACK:0/COBA:0;

GETTEST COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h GETTEST COBA”



Command Description:This command displays the attributes of the COBA test.





JOB: 187

PC Time&Date: 12:07:21 03/23/2005

NE Time&Date: 13:08:54 09/15/2004

GETTEST COBA NAME=RACK:0..7/COBA:0..1;

DN0933412 Issue 01205


COBA

Id:0900d805805b0cc8

USER NAME: NSN

COMMAND: Gettest COBA:NAME=RACK:0/COBA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/COBA:0

testMonitor =

phaseId = PreliminaryTestsCoba


phaseId = CheckAlarmStatusCoba


phaseId = EndTestCoba





Operation Failed




phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



206DN0933412 Issue 01


Id:0900d805805b0cc8

COBA

Example of Command Execution:Gettest COBA:NAME=RACK:0/COBA:0, REQATTL=MORT&TESTMON&

TESTOUT&TESTST;

LOCK COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h LOCK COBA”



Command Description:This command changes the administrative state of the COBA (Core Basis module).



The specified change of administrative state has been perfomed. An example of lock command is the following:

JOB: 166

PC Time&Date: 16:46:53 03/23/2005

NE Time&Date: 16:44:47 09/15/2004

USER NAME: NSN

COMMAND: Lock COBA:NAME=RACK:0/COBA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23






LOCK COBA NAME=RACK:0..7/COBA:0..1;

DN0933412 Issue 01207


COBA

Id:0900d805805b0cc8

JOB: 167

PC Time&Date: 16:46:53 03/23/2005

NE Time&Date: 16:44:47 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/COBA:1




Operation Failed



• Lock COBA:0 only in Phase 2

Example of Command Execution:Lock COBA:NAME=RACK:0/COBA:0;

PERFTEST COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h PERFTEST COBA”



Command Description:This command is used to start an asynchronous test in COBA.



PERFTEST COBA NAME=RACK:0..7/COBA:0..1;

208DN0933412 Issue 01


Id:0900d805805b0cc8

COBA

Test configuration has been set and the specified test has been started. The System response will not be addressed to the MOT but to the object BTSEP. An example of perftest command is the following:

JOB: 188

PC Time&Date: 12:06:51 03/23/2009

NE Time&Date: 13:08:26 09/15/2009

USER NAME: NSN

COMMAND: Perftest COBA:NAME=RACK:0/COBA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/COBA:0

tO = BTSETEST:2


JOB: 189

PC Time&Date: 12:07:23 03/23/2009

NE Time&Date: 13:08:53 09/15/2009

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2



JOB: 190

PC Time&Date: 12:07:38 03/23/2009

NE Time&Date: 13:09:02 09/15/2009

DN0933412 Issue 01209


COBA

Id:0900d805805b0cc8

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23






Standby Status = Cold_Standby



JOB: 191

PC Time&Date: 12:07:52 03/23/2005

NE Time&Date: 13:09:34 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:2



MOT = RACK:0/COBA:0

executedPhases =

PreliminaryTestsCoba

BootEepromTestCoba

SerialEepromTestCoba

EndTestCoba


JOB: 192

210DN0933412 Issue 01


Id:0900d805805b0cc8

COBA

PC Time&Date: 12:08:04 03/23/2005

NE Time&Date: 13:09:28 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2




Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


DN0933412 Issue 01211


COBA

Id:0900d805805b0cc8

Operation Failed



• In phase 3 COBA must be locked previous to the command

• Perftest for COBA:0 in phase 2 only

Example of Command Execution:Perftest COBA:NAME=RACK:0/COBA:0;

SET COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h SET COBA”



Command Description:This command permits modification of the attributes of the COBA (Core Basis module).






....

skippedPhases


....



SET COBA NAME=RACK:0..7/COBA:0..1 [,ALRMCOUNTER=] [,ALRMT1/2/3=] [,EFCUSUP=];

212DN0933412 Issue 01


Id:0900d805805b0cc8

COBA


JOB: 172

PC Time&Date: 16:47:25 03/23/2005

NE Time&Date: 16:45:19 09/15/2004

USER NAME: NSN

COMMAND: Set COBA:NAME=RACK:0/COBA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• The alarm evaluation on BTSE for the layer 1 is based on an "Errored Second" concept. I.e.: If an error is found active (counted every 2 msec.) for x times (x = 5 for "No signal", "AIS", "Loss of frame alignment ...) within 1 second, the whole second is declared faulty otherwise the second is declared as "good". If one "Errored Second" is detected, the subsequent seconds will be also declared faulty until no error is detected within one second. This means that the layer 1 alarm handling is very sensitive. With the default setting of "ALRMT2" which is 1 second a short inter-ruption of 10 msec will cause an alarm generated by the BTSE. In order to increase the tolerance of the BTSE layer 1 alarm handling against short interruptions on the lines, the operator can change the value of the timer "ALRMT2" from the default setting (1 second) to a higher value (e.g. 2 seconds). Nevertheless if the BTSE gen-erates a layer 1 alarm no further actions are performed. Call processing is not inhib-ited as long as the layer 2 is up or the Flexi BSC product family does not declare the line disabled

Example of Command Execution:Set COBA:NAME=RACK:0/COBA:0,ACPER=20&ALRMCOUNTER=32,ALRMT1=20,

ALRMT2=2,ALRMT3=1,EFCUSUP=TRUE;

STOPTEST COBASTOPTEST COBA NAME=RACK:0..7/COBA:0..1;

DN0933412 Issue 01213


COBA

Id:0900d805805b0cc8

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h STOPTEST COBA”







Operation Failed



Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


214DN0933412 Issue 01


Id:0900d805805b0cc8

COBA

Example of Command Execution:Stoptest COBA:NAME=RACK:0/COBA:0;

SWITCH COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h SWITCH COBA”



Command Description:This command is used to switch to the standby copy of COBA.


System Responses:Operation Completed. An example of switch command is the following:

JOB: 60

PC Time&Date: 11:57:24 03/23/2005

NE Time&Date: 12:58:59 09/15/2004

USER NAME: NSN

COMMAND: Switch COBA:NAME=RACK:0/COBA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed

JOB: 61

PC Time&Date: 11:57:31 03/23/2005

NE Time&Date: 12:59:06 09/15/2004

USER NAME: NSN

COMMAND: Switch COBA:NAME=RACK:0/COBA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23

SWITCH COBA NAME=RACK:0..7/COBA:0..1;

DN0933412 Issue 01215


COBA

Id:0900d805805b0cc8


no redundant core board available (-173)



• Only COBA:0 can be switched

• No redundancy present in BS82II (the command is not applicable)

Example of Command Execution:Switch COBA:NAME=RACK:0/COBA:0;

UNLOCK COBA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h UNLOCK COBA”



Command Description:This command changes the administrative state of the COBA (Core Basis module).




JOB: 173

PC Time&Date: 16:47:33 03/23/2005

NE Time&Date: 16:45:27 09/15/2004

USER NAME: NSN

COMMAND: Unlock COBA:NAME=RACK:0/COBA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23


UNLOCK COBA NAME=RACK:0..7/COBA:0..1;

216DN0933412 Issue 01


Id:0900d805805b0cc8

COBA





JOB: 174

PC Time&Date: 16:47:33 03/23/2005

NE Time&Date: 16:45:27 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



• Unlock COBA:0 only in phase 2

Example of Command Execution:Unlock COBA:NAME=RACK:0/COBA:0;

DN0933412 Issue 01217


COBAETHINTF

Id:0900d805805b0cca

COBAETHINTFThis object represents the Ethernet interface of the new COBA which is connected to the Zarlink device. It is introduced to configure/retrieve Ethernet interface specific infor-mation (similar to UNIX eth<x>) and to indicate state information.

The object is automatically created if a new COBA with CES support is equipped.

GET COBAETHINTF

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h COBAETHINTF h GET COBAETHINTF”



Command Description:This command displays the attributes of the COBAETHINTF.



ALS alarmStatus






MACADDR macAddress

TYPOFETH typeOfEthernet


A mesNSNe indicates the result of the operation. An example of get command is the fol-lowing:

JOB: 65

PC Time&Date: 02.04.2008 09:11:51 +02:00

NE Time&Date: 01.01.1990 18:27:29 +00:00.

COMMAND: Get COBAETHINTF:NAME=COBAETHINTF:0;

SW RELEASE: 01-04-19-01-08-CR_08-03-31

COMMAND RESULT:Operation successfulalarmStatus = CLEARED

GET COBAETHINTF NAME=COBAETHINTF:0..0 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, MACADDR, TYPOFETH];

218DN0933412 Issue 01


Id:0900d805805b0cca

COBAETHINTF





macAddress = "08:00:06:78:64:63"

typeOfEthernet = ethernet_II


Operation Failed

None.


Example of Command Execution:Get COBAETHINTF:NAME=COBAETHINTF:0, REQATTL=ALS&AST&AVS&OST&PRS&RELFUNCOBJ&MACADR&TETH;

LOCK COBAETHINTF

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h COBAETHINTF h LOCK COBAETHINTF”



Command Description:This command changes the administrative state of COBAETHINTF.




JOB: 89

PC Time&Date: 05.06.2008 13:18:01 +02:00

NE Time&Date: 01.01.1990 00:14:45 +00:00

USER NAME: NSN

COMMAND: Lock COBAETHINTF:NAME=COBAETHINTF:0;

SW RELEASE: 01-04-19-01-09-ZS_08-06-03


LOCK COBAETHINTF NAME=COBAETHINTF:0..0;

DN0933412 Issue 01219


COBAETHINTF

Id:0900d805805b0cca



Operation Failed

None.


Example of Command Execution:Lock COBAETHINTF:NAME=COBAETHINTF:0;

SET COBAETHINTF

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h COBAETHINTF h SET COBAETHINTF”



Command Description:This command sets the attributes of COBAETHINTF.


TYPOFETH typeOfEthernet


After command execution, a mesNSNe of Changed Attribute Event Report is displayed. A further mesNSNe indicates the result of the operation.

An example of set command is the following:

JOB: 35

PC Time&Date: 11.02.2008 11:34:29 +01:00

NE Time&Date: 01.01.1990 00:40:35 +00:00

USER NAME: NSN

COMMAND: Set COBAETHINTF:NAME=COBAETHINTF:0,TETH=ethernet_II;

SW RELEASE: 01-04-19-01-01-CR_08-01-11


typeOfEthernet = ethernet_II


Operation Failed

SET COBAETHINTF NAME=COBAETHINTF:0..0 [,TYPOFETH=];

220DN0933412 Issue 01


Id:0900d805805b0cca

COBAETHINTF

None.


Example of Command Execution:Set COBAETHINTF:NAME=COBAETHINTF:0,TYPOFETH=ethernet_II;

UNLOCK COBAETHINTF

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h COBAETHINTF h UNLOCK COBAETHINTF”



Command Description:This command changes the administrative state of COBAETHINTF.




JOB: 98

PC Time&Date: 05.06.2008 13:18:14 +02:00

NE Time&Date: 01.01.1990 00:14:58 +00:00

USER NAME: NSN

COMMAND: Unlock COBAETHINTF:NAME=COBAETHINTF:0;

SW RELEASE: 01-04-19-01-09-ZS_08-06-03



END OF OUTPUT FOR JOB 98.

Operation Failed

None.


Example of Command Execution:Unlock COBAETHINTF:NAME=COBAETHINTF:0;

UNLOCK COBAETHINTF

NAME=COBAETHINTF:0..0;

DN0933412 Issue 01221


COSA

Id:0900d805805b0ccc

COSAThe COSA (Core Satellite Interface module) object is the core controller expansion unit and it is contained in the base rack only.

CREATE COSA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h CREATE COSA”



Command Description:This command adds the COSA (Core Satellite interface module) to the BTSE data base.




JOB: 146

PC Time&Date: 16:44:39 03/23/2005

NE Time&Date: 16:42:33 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/COSA:1



CREATE COSA NAME=RACK:0..7/COSA:0..1;

222DN0933412 Issue 01


Id:0900d805805b0ccc

COSA

JOB: 147

PC Time&Date: 16:44:39 03/23/2005

NE Time&Date: 16:42:33 09/15/2004

USER NAME: NSN

COMMAND: Create COSA:NAME=RACK:0/COSA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 70

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create COSA:NAME=RACK:0/COSA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• COSA creation is not possible for BS82II

Example of Command Execution:Create COSA:NAME=RACK:0/COSA:0;

DELETE COSADELETE COSA NAME=RACK:0..7/COSA:0..1;

DN0933412 Issue 01223


COSA

Id:0900d805805b0ccc

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h DELETE COSA”



Command Description:This command deletes the COSA (Core Satellite interface module) from the BTSE data base.




JOB: 156

PC Time&Date: 16:45:32 03/23/2005

NE Time&Date: 16:43:26 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/COSA:1



JOB: 157

PC Time&Date: 16:45:32 03/23/2005

NE Time&Date: 16:43:26 09/15/2004

USER NAME: NSN

224DN0933412 Issue 01


Id:0900d805805b0ccc

COSA

COMMAND: Delete COSA:NAME=RACK:0/COSA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• COSA must be locked in Phase 3 before deletion

Example of Command Execution:Delete COSA:NAME=RACK:0/COSA:0;

GET COSA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h GET COSA”



Command Description:This command displays the attributes of the COSA (Core Satellite interface module).



ALS alarmStatus






SLOTNO slotNo



GET COSA NAME=RACK:0..7/COSA:0..1 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, SLOTNO, STDBYST];

DN0933412 Issue 01225


COSA

Id:0900d805805b0ccc


JOB: 148

PC Time&Date: 16:45:02 03/23/2005

NE Time&Date: 16:42:56 09/15/2004

USER NAME: NSN

COMMAND: Get COSA:NAME=RACK:0/COSA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23








slotNo = leftCOSA

standbyStatus = NULL


Operation Failed



• COSA:0 is the one with "Providing Service" Status, COSA:1 is in Standby Status

Example of Command Execution:Get COSA:NAME=RACK:0/COSA:0,REQATTL=ALS&AST&AVS&

RELFUNCOBJ&OST& PRS.

GETTEST COSA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h GETTEST COSA”

GETTEST COSA NAME=RACK:0..7/COSA:0..1;

226DN0933412 Issue 01


Id:0900d805805b0ccc

COSA



Command Description:This command displays the attributes of the COSA test.





JOB: 193

PC Time&Date: 12:08:22 03/23/2005

NE Time&Date: 13:09:33 09/15/2004

USER NAME: NSN

COMMAND: Gettest COSA:NAME=RACK:0/COSA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/COSA:0

testMonitor =

phaseId = PreliminaryTestsCosa


phaseId = CheckAlarmStatusCosa


phaseId = EndTestCosa





Operation Failed


DN0933412 Issue 01227


COSA

Id:0900d805805b0ccc


Example of Command Execution:Gettest COSA:NAME=RACK:0/COSA:0;

LOCK COSA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h LOCK COSA”



Command Description:This command changes the administrative state of COSA (Core Satellite interface module).





phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK COSA NAME=RACK:0..7/COSA:0..1;

228DN0933412 Issue 01


Id:0900d805805b0ccc

COSA

JOB: 149

PC Time&Date: 16:45:07 03/23/2005

NE Time&Date: 16:43:01 09/15/2004

USER NAME: NSN

COMMAND: Lock COSA:NAME=RACK:0/COSA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 150

PC Time&Date: 16:45:07 03/23/2005

NE Time&Date: 16:43:01 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/COSA:1




Operation Failed


DN0933412 Issue 01229


COSA

Id:0900d805805b0ccc

Application Guidelines:If the second line does not end in the first station (or is looped back by a plug!) also the following points must considered for BS240/241 and BS40/41:

• Before a LOCK COSA command (over this board the information of the second line is distributed within the BS240/241 and BS40/41) is applied by the user, the user should lock the service distributed over the second line to this BTSE otherwise some channels (associated to a COBA CU) remain enabled

• In case of a defective COSA, the channels which are associated to a COBA CU but transported over the second line remain enabled

Example of Command Execution:Lock COSA:NAME=RACK:0/COSA:0;

PERFTEST COSA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h PERFTEST COSA”



Command Description:This command is used to start an asynchronous test in COSA.



Test configuration has been set and the specified test has been started. The System response will not be addressed to the MOT but to the object BTSE.

JOB: 193

PC Time&Date: 12:08:42 03/23/2005

NE Time&Date: 13:09:41 09/15/2004

USER NAME: NSN

COMMAND: Perftest COSA:NAME=RACK:0/COSA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


PERFTEST COSA NAME=RACK:0..7/COSA:0..1;

230DN0933412 Issue 01


Id:0900d805805b0ccc

COSA

MOT = RACK:0/COSA:0

tO = BTSETEST:8


JOB: 194

PC Time&Date: 12:08:55 03/23/2005

NE Time&Date: 13:09:59 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:8



JOB: 195

PC Time&Date: 12:09:05 03/23/2005

NE Time&Date: 13:10:11 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23









DN0933412 Issue 01231


COSA

Id:0900d805805b0ccc

JOB: 196

PC Time&Date: 12:09:16 03/23/2005

NE Time&Date: 13:10:22 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:8



MOT = RACK:0/COSA:0

executedPhases =

PreliminaryTestsCosa

SerialEepromTestCosa

EndTestCosa


JOB: 197

PC Time&Date: 12:09:23 03/23/2005

NE Time&Date: 13:10:34 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:8



232DN0933412 Issue 01


Id:0900d805805b0ccc

COSA

Operation Failed





Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



DN0933412 Issue 01233


COSA

Id:0900d805805b0ccc

Example of Command Execution:Perftest COSA:NAME=RACK:0/COSA:0;

STOPTEST COSA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h STOPTEST COSA”







STOPTEST COSA NAME=RACK:0..7/COSA:0..1;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


234DN0933412 Issue 01


Id:0900d805805b0ccc

COSA

Operation Failed



Example of Command Execution:Stoptest COSA:NAME=RACK:0/COSA:0;

UNLOCK COSA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h UNLOCK COSA”



Command Description:This command changes the administrative state of COSA (Core Satellite interface module).




JOB: 151

PC Time&Date: 16:45:12 03/23/2005

NE Time&Date: 16:43:06 09/15/2004

USER NAME: NSN

COMMAND: Unlock COSA:NAME=RACK:0/COSA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




UNLOCK COSA NAME=RACK:0..7/COSA:0..1;

DN0933412 Issue 01235


COSA

Id:0900d805805b0ccc



JOB: 152

PC Time&Date: 16:45:12 03/23/2005

NE Time&Date: 16:43:06 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23





Standby Status = Providing_service



Operation Failed



Example of Command Execution:Unlock COSA:NAME=RACK:0/COSA:0;

236DN0933412 Issue 01


Id:0900d805805b0cce

CU

CUThe CU (Carrier Unit) represents the carrier hardware required for a TRX.

CREATE CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h CREATE CU”



Command Description:This command adds the CU (Carrier Unit) to the BTSE data base.


RXLEVADJ rxLevAdjust(dB)

TXLEVADJ txLevAdjust(dB)



JOB: 124

PC Time&Date: 16:43:07 03/23/2005

NE Time&Date: 16:41:01 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/CU:0



CREATE CU NAME=RACK:0..7/CU:0..11 [,RXLEVADJ=] [,TXLEVADJ=];

DN0933412 Issue 01237


CU

Id:0900d805805b0cce

JOB: 125

PC Time&Date: 16:43:08 03/23/2005

NE Time&Date: 16:41:02 09/15/2004

USER NAME: NSN

COMMAND: Create CU:NAME=RACK:0/CU:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 69

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create CU:NAME=RACK:0/CU:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• When using the CLI interface for the RXLEVADJ parameter, the negative values must be in brackets (refer to Examples of Command Execution)

Example of Command Execution:Create CU:NAME=RACK:0/CU:0,RXLEVADJ=[-1]-0,TXLEVADJ=1;

DELETE CUDELETE CU NAME=RACK:0..7/CU:0..11;

238DN0933412 Issue 01


Id:0900d805805b0cce

CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h DELETE CU”



Command Description:This command deletes the CU (Carrier Unit) from the BTSE data base.




JOB: 138

PC Time&Date: 16:44:00 03/23/2005

NE Time&Date: 16:41:54 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/CU:0



JOB: 139

PC Time&Date: 16:44:00 03/23/2005

NE Time&Date: 16:41:54 09/15/2004

USER NAME: NSN

COMMAND: Delete CU:NAME=RACK:0/CU:0;

DN0933412 Issue 01239


CU

Id:0900d805805b0cce

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• CU has to be locked in Phase 3 before deletion

Example of Command Execution:Delete CU:NAME=RACK:0/CU:0;

GET CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h GET CU”



Command Description:This command displays the attributes of the CU (Carrier Unit).



ALS alarmStatus




CCPBL carrierCapability


OUTPUTPR outputPowerReduction




GET CU NAME=RACK:0..7/CU:0..11 [,REQATTL=ALS, AST, AVS, BSWVER, CCPBL, OST, OUTPUTPR, PRS, RELFUN-COBJ, RXLEVADJ, TXLEVADJ, FPGAFWVER, STDBYST];

240DN0933412 Issue 01


Id:0900d805805b0cce

CU


FPGAFWVER fpgaFwVer




JOB: 127

PC Time&Date: 16:43:13 03/23/2005

NE Time&Date: 16:41:07 09/15/2004

USER NAME: NSN

COMMAND: Get CU:NAME=RACK:0/CU:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





bootSoftwareVersion = ""

carrierCapability = unknown

outputPowerReduction = 0




rxLevAdjust(dB) =

adjustValue = 0.0

adjustDivValue = 0.0

txLevAdjust(dB) = 0.0


Operation Failed


DN0933412 Issue 01241


CU

Id:0900d805805b0cce


• The value for the attribute GSM functional ID in LMT Evolution Phase 2 is "not con-figured"

• CCPBL: After creation in advance of a CU object the attribute has the value "unknown" in case of hh-ii =04-01 and hh-ii = 04-06. The value "fourRXdiv" is used always in combination with either the value "gsm" or "edge"

Example of Command Execution:Get CU:NAME=RACK:0/CU:0,REQATTL=ALS&AST&AVS&BSWVER&CCPBL&

OUTPUTPR&OST&PRS&RELFUNCOBJ&RXLEVADJ;

GET CU FWID

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h GET CU FWID”



Command Description:This command provides information on the FPGA FW images that are contained in the boards flash prom together with an indication of the “active” version. Up to 4 images are provided per board. For FlexCUv2 or ECUv6 boards the FPGA FW versions are provided together with an indication whether the FW version is the active one.





JOB: 6.

PC Time&Date: 26.06.2008 11:13:51 +02:00

NE Time&Date: 01.01.1990 00:13:15 +00:00

USER NAME: NSN

COMMAND: Get CU FWID:NAME=RACK:0/CU:0;SW RELEASE: 01-04-19-01-09-01_08-06-23


fpgaFwVer = Null


GET CU FWID NAME=RACK:0..7/CU:0..11;

242DN0933412 Issue 01


Id:0900d805805b0cce

CU

Operation Failed

None.


Example of Command Execution:Get CU FWID:NAME=RACK:0/CU:0,REQATTL=FPGAFWVER;

GET CU WIRING

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h GET CU WIRING”



Command Description:This command displays the attributes of the CU (Carrier Unit).




After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of get wiring command is the following:

JOB: 127

PC Time&Date: 16:43:13 03/23/2005

NE Time&Date: 16:41:07 09/15/2004

USER NAME: NSN

COMMAND: Get CU WIRING:NAME=RACK:0/CU:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


cuWiring =

GET CU WIRING NAME=RACK:0..7/CU:0..11;

DN0933412 Issue 01243


CU

Id:0900d805805b0cce

variable

rxNWiring = RACK:0/DULNA:0


Operation Failed



• Refer to “CUWIRING”

Example of Command Execution:Get CU WIRING:NAME=RACK:0/CU:0;

GETTEST CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h GETTEST CU”



Command Description:This command displays the attributes of the object test.





JOB: 198

PC Time&Date: 12:11:08 03/23/2005

NE Time&Date: 13:12:44 09/15/2004

USER NAME: NSN

COMMAND: Gettest CU:NAME=RACK:0/CU:0;

GETTEST CU NAME=RACK:0..7/CU:0..11;

244DN0933412 Issue 01


Id:0900d805805b0cce

CU

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/CU:0

testMonitor =

phaseId = PreliminaryTestsCu


phaseId = CheckAlarmStatusCu


phaseId = EndTestCu





Operation Failed



Example of Command Execution:Gettest CU:NAME=RACK:0/CU:0;


phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



DN0933412 Issue 01245


CU

Id:0900d805805b0cce

LOCK CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h LOCK CU”



Command Description:This command changes the administrative state of CU (Carrier Unit).




JOB: 132

PC Time&Date: 16:43:41 03/23/2005

NE Time&Date: 16:41:35 09/15/2004

USER NAME: NSN

COMMAND: Lock CU:NAME=RACK:0/CU:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 133

PC Time&Date: 16:43:41 03/23/2005

NE Time&Date: 16:41:35 09/15/2004

LOCK CU NAME=RACK:0..7/CU:0..11;

246DN0933412 Issue 01


Id:0900d805805b0cce

CU

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/CU:0




Operation Failed



Example of Command Execution:Lock CU:NAME=RACK:0/CU:0;

PERFTEST CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h PERFTEST CU”



Command Description:This command is used to start an asynchronous test in the object.




JOB: 199

PERFTEST CU NAME=RACK:0..7/CU:0..11;

DN0933412 Issue 01247


CU

Id:0900d805805b0cce

PC Time&Date: 12:11:12 03/23/2005

NE Time&Date: 13:12:48 09/15/2004

USER NAME: NSN

COMMAND: Perftest CU:NAME=RACK:0/CU:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/CU:0

tO = BTSETEST:1


JOB: 200

PC Time&Date: 12:11:12 03/23/2005

NE Time&Date: 13:12:48 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1



JOB: 201

PC Time&Date: 12:11:12 03/23/2005

NE Time&Date: 13:12:59 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


248DN0933412 Issue 01


Id:0900d805805b0cce

CU


NAME = RACK:0/CU:0






JOB: 202

PC Time&Date: 12:11:18 03/23/2005

NE Time&Date: 13:13:11 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:1



MOT = RACK:0/CU:0

executedPhases =

PreliminaryTestsCu

SerialEepromTestCu

EndTestCu


JOB: 203

PC Time&Date: 12:11:20 03/23/2005

NE Time&Date: 13:13:25 09/15/2004

USER NAME: NSN

DN0933412 Issue 01249


CU

Id:0900d805805b0cce

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1




Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases

250DN0933412 Issue 01


Id:0900d805805b0cce

CU

Operation Failed




Example of Command Execution:Perftest CU:NAME=RACK:0/CU:0;

SET CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h SET CU”



Command Description:This command sets the attributes of CU (Carrier Unit) to the BTSE data base.






JOB: 131

PC Time&Date: 16:43:27 03/23/2005


....



SET CU NAME=RACK:0..7/CU:0..11 [,RXLEVADJ=] [,TXLEVADJ=];

DN0933412 Issue 01251


CU

Id:0900d805805b0cce

NE Time&Date: 16:41:21 09/15/2004

USER NAME: NSN

COMMAND: Set CU:NAME=RACK:0/CU:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• When using the CLI interface for the RXLEVADJ parameter, the negative values must be in brackets (see Example of Command Execution)

• The MGMSKOUTPUTP power reduction parameter is used for all existing high power variants ECUxHPV2 and ECUxHPV3 (x= D or P)

Example of Command Execution:Set CU:NAME=RACK:0/CU:0,TXLEVADJ=1,RXLEVADJ=[-1]-[-1];

STOPTEST CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h STOPTEST CU”







STOPTEST CU NAME=RACK:0..7/CU:0..11;

252DN0933412 Issue 01


Id:0900d805805b0cce

CU

Operation Failed



Example of Command Execution:Stoptest CU:NAME=RACK:0/CU:0;

UNLOCK CU

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h UNLOCK CU”



Command Description:This command changes the administrative state of CU (Carrier Unit).


Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


UNLOCK CU NAME=RACK:0..7/CU:0..11;

DN0933412 Issue 01253


CU

Id:0900d805805b0cce



JOB: 134

PC Time&Date: 16:43:50 03/23/2005

NE Time&Date: 16:41:44 09/15/2004

USER NAME: NSN

COMMAND: Unlock CU:NAME=RACK:0/CU:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 135

PC Time&Date: 16:43:50 03/23/2005

NE Time&Date: 16:41:44 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/CU:0




254DN0933412 Issue 01


Id:0900d805805b0cce

CU

Operation Failed



Example of Command Execution:Unlock CU:NAME=RACK:0/CU:0;

DN0933412 Issue 01255


DIDCTMA

Id:0900d805805b1080

DIDCTMAThe DIDCTMA object represents the power supply module of a TMA (Tower Mounted Amplifier) connected to DIAMCO.

CREATE DIDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h CREATE DIDCTMA”



Command Description:This command adds the DIAMCO_DC_TMA (DC Power Supply Module of TMA) to the BTSE data base.




JOB: 111

PC Time&Date: 16:41:43 03/23/2005

NE Time&Date: 16:39:37 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/DIDCTMA:0



CREATE DIDCTMA NAME=RACK:0..7/DIDCTMA:0..7;

256DN0933412 Issue 01


Id:0900d805805b1080

DIDCTMA

JOB: 112

PC Time&Date: 16:41:43 03/23/2005

NE Time&Date: 16:39:37 09/15/2004

USER NAME: NSN

COMMAND: Create DIDCTMA:NAME=RACK:0/DIDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 68

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create DIDCTMA:NAME=RACK:0/DIDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





Example of Command Execution:Create DIDCTMA:NAME=RACK:0/DIDCTMA:0;

DELETE DIDCTMADELETE DIDCTMA NAME=RACK:0..7/DIDCTMA:0..7;

DN0933412 Issue 01257


DIDCTMA

Id:0900d805805b1080

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h DELETE DIDCTMA”



Command Description:This command deletes the DIAMCO_DC_TMA (DC Power Supply Module of TMA) from the BTSE data base.




JOB: 120

PC Time&Date: 16:42:08 03/23/2005

NE Time&Date: 16:40:02 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/DIDCTMA:0



JOB: 121

PC Time&Date: 16:42:08 03/23/2005

NE Time&Date: 16:40:02 09/15/2004

USER NAME: NSN

258DN0933412 Issue 01


Id:0900d805805b1080

DIDCTMA

COMMAND: Delete DIDCTMA:NAME=RACK:0/DIDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• DIDCTMA must be locked in phase 3 before deletion

Example of Command Execution:Delete DIDCTMA:NAME=RACK:0/DIDCTMA:0;

GET DIDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h GET DIDCTMA”



Command Description:This command displays the attributes of the DIAMCO_DC_TMA (DC Power Supply Module of TMA).



ALS alarmStatus







GET DIDCTMA NAME=RACK:0..7/DIDCTMA:0..7 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ];

DN0933412 Issue 01259


DIDCTMA

Id:0900d805805b1080


JOB: 113

PC Time&Date: 16:41:48 03/23/2005

NE Time&Date: 16:39:41 09/15/2004

USER NAME: NSN

COMMAND: Get DIDCTMA:NAME=RACK:0/DIDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23









Operation Failed



Example of Command Execution:Get DIDCTMA:NAME=RACK:0/DIDCTMA:0,REQATTL=ALS&AST&AVS&OST&PRS;

GETTEST DIDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h GETTEST DIDCTMA”



GETTEST DIDCTMA NAME=RACK:0..7/DIDCTMA:0..7;

260DN0933412 Issue 01


Id:0900d805805b1080

DIDCTMA






JOB: 204

PC Time&Date: 12:11:28 03/23/2005

NE Time&Date: 13:13:04 09/15/2004

USER NAME: NSN

COMMAND: Gettest DIDCTMA:NAME=RACK:0/DIDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/DIDCTMA:0

testMonitor =

phaseId = PreliminaryTestsDidctma


phaseId = CheckAlarmStatusDidctma


phaseId = EndTestDidctma





Operation Failed


DN0933412 Issue 01261


DIDCTMA

Id:0900d805805b1080


Example of Command Execution:Gettest DIDCTMA:NAME=RACK:0/DIDCTMA:0;

LOCK DIDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h LOCK DIDCTMA”



Command Description:This command changes the administrative state of DIAMCO_DC_TMA (DC Power Supply Module of TMA).





phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK DIDCTMA NAME=RACK:0..7/DIDCTMA:0..7;

262DN0933412 Issue 01


Id:0900d805805b1080

DIDCTMA

JOB: 114

PC Time&Date: 16:41:53 03/23/2005

NE Time&Date: 16:39:47 09/15/2004

USER NAME: NSN

COMMAND: Lock DIDCTMA:NAME=RACK:0/DIDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 115

PC Time&Date: 16:41:53 03/23/2005

NE Time&Date: 16:39:47 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/DIDCTMA:0




Operation Failed



DN0933412 Issue 01263


DIDCTMA

Id:0900d805805b1080

Example of Command Execution:Lock DIDCTMA:NAME=RACK:0/DIDCTMA:0;

PERFTEST DIDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h PERFTEST DIDCTMA”



Command Description:This command is used to start an asynchronous test in DIDCTMA.




JOB: 205

PC Time&Date: 12:13:07 03/23/2005

NE Time&Date: 13:14:42 09/15/2004

USER NAME: NSN

COMMAND: Perftest DIDCTMA:NAME=RACK:0/DIDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:2


JOB: 206

PC Time&Date: 12:13:22 03/23/2005

PERFTEST DIDCTMA NAME=RACK:0..7/DIDCTMA:0..7;

264DN0933412 Issue 01


Id:0900d805805b1080

DIDCTMA

NE Time&Date: 13:14:57 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2



JOB: 207

PC Time&Date: 12:13:31 03/23/2005

NE Time&Date: 13:15:06 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23









JOB: 208

PC Time&Date: 12:13:35 03/23/2005

NE Time&Date: 13:15:10 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


DN0933412 Issue 01265


DIDCTMA

Id:0900d805805b1080

Test Report:

name = BTSETEST:2




executedPhases =

PreliminaryTestsDidctma

SerialEepromTestDidctma

EndTestDidctma


JOB: 209

PC Time&Date: 12:13:35 03/23/2005

NE Time&Date: 13:15:10 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2




Result TEST:

name = TEST:<n>




266DN0933412 Issue 01


Id:0900d805805b1080

DIDCTMA

Operation Failed




Example of Command Execution:Perftest DIDCTMA:NAME=RACK:0/DIDCTMA:0;

STOPTEST DIDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h STOPTEST DIDCTMA”







executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



STOPTEST DIDCTMA NAME=RACK:0..7/DIDCTMA:0..7;

DN0933412 Issue 01267


DIDCTMA

Id:0900d805805b1080







Operation Failed



Example of Command Execution:Stoptest DIDCTMA:NAME=RACK:0/DIDCTMA:0;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


268DN0933412 Issue 01


Id:0900d805805b1080

DIDCTMA

UNLOCK DIDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h UNLOCK DIDCTMA”



Command Description:This command changes the administrative state of DIAMCO_DC_TMA (DC Power Supply Module of TMA).




JOB: 116

PC Time&Date: 16:41:57 03/23/2005

NE Time&Date: 16:39:51 09/15/2004

USER NAME: NSN

COMMAND: Unlock DIDCTMA:NAME=RACK:0/DIDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 117

PC Time&Date: 16:41:57 03/23/2005

UNLOCK DIDCTMA NAME=RACK:0..7/DIDCTMA:0..7;

DN0933412 Issue 01269


DIDCTMA

Id:0900d805805b1080

NE Time&Date: 16:39:51 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



Example of Command Execution:Unlock DIDCTMA:NAME=RACK:0/DIDCTMA:0;

270DN0933412 Issue 01


Id:0900d805805b1082

DILNA

DILNAThe DILNA object represents the low noise amplifier of DIAMCO (Diversity Antenna Multicoupler).

CREATE DILNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h CREATE DILNA”



Command Description:This command adds the DILNA (Low Noise Amplifier of Diversity Multicoupler) together with its attributes to the BTSE data base.


CELLNO cellNumber

COMBMD combMode

LNAPRED lnaPredecessor

SCELLNO secondCellNumber

WDLNA wiringDataLna



JOB: 96

PC Time&Date: 16:40:26 03/23/2005

NE Time&Date: 16:38:20 09/15/2004

USER NAME: NSN_Frank

SW RELEASE: 01-04-17-01-26-51_05-02-23


CREATE DILNA NAME=RACK:0..7/DILNA:0..7 ,CELLNO= [,COMBMD=] [,LNAPRED=] [,SCELLNO=] ,WDLNA=;

DN0933412 Issue 01271


DILNA

Id:0900d805805b1082


name = RACK:0/DILNA:0



JOB: 97

PC Time&Date: 16:40:26 03/23/2005

NE Time&Date: 16:38:20 09/15/2004


COMMAND: Create DILNA:NAME=RACK:0/DILNA:0,CELLNO=1,WDLNA=CU0N;

SW RELEASE: 01-04-17-01-26-51_05-02-23


cellNumber = 1

secondCellNumber = 2

wiringDataLna = CU0N


Operation Failed


JOB: 74

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004


COMMAND: Create DILNA:NAME=RACK:0/DILNA:0,CELLNO=1,WDLNA=CU0N;

SW RELEASE: 01-04-17-01-26-51_05-02-23



272DN0933412 Issue 01


Id:0900d805805b1082

DILNA



• The DIAMCO_LNA and the CUs are in the same rack and belong to the same cell

• Each CU has a 'normal path' RX input and a 'diversity path' RX input and the operator must indicate which of them is wired to the DIAMCO_LNA

• If there is no wiring the operator must not provide a value for the attribute LNAPRED (if a get is done the attribute identifier will be put into the list of unavailable attributes)

• If there is no wiring for the attribute LNAPRED and the operator enters a value, this error can be corrected by a deletion of the object and a re-creation of the object

• The BTSE SW doesn't check if the entered "predecessor (relative number)" is com-patible with typeOfBTSE; e.g. an input of TMA 11 is not rejected in a BS40 although BS40 allows only the creation of TMA 0-5

The BTSE SW doesn't check if the entered "predecessor (rack)" is compatible with typeOfBTSE; e.g. an input of RACK 1 is not rejected in a BS40 although BS40 allows only the creation of RACK 0


Example of Command Execution:Create DILNA:NAME=RACK:1/DILNA:0,CELLNO=0,COMBMD=EightToTwo,

SCELLNO=2,WDLNA=CU0D&CU1D&CU2D&CU3D,

LNAPRED=TMA (RACK:0-TMA:0);

DELETE DILNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h DELETE DILNA”



Command Description:This command deletes the DILNA (Low Noise Amplifier of Diversity Multicoupler) together with its attributes from the BTSE data base.




DELETE DILNA NAME=RACK:0..7/DILNA:0..7;

DN0933412 Issue 01273


DILNA

Id:0900d805805b1082

JOB: 106

PC Time&Date: 16:40:51 03/23/2005

NE Time&Date: 16:38:45 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/DILNA:0



JOB: 107

PC Time&Date: 16:40:51 03/23/2005

NE Time&Date: 16:38:45 09/15/2004


COMMAND: Delete DILNA:NAME=RACK:0/DILNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• DILNA must be locked in Phase 3, before deletion

• If this object is deleted, the related TRXs are out of service

Example of Command Execution:Delete DILNA:NAME=RACK:0/DILNA:0;

274DN0933412 Issue 01


Id:0900d805805b1082

DILNA

GET DILNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h GET DILNA”



Command Description:This command displays the attributes of the DILNA (Low Noise Amplifier of Diversity Multicoupler).



ALS alarmStatus



CELLNO cellNumber

GNA gainAdjust(dB)

COMBMD combMode

LNAMODE lnaMode






WDLNA wiringDataLna



JOB: 99

PC Time&Date: 16:40:32 03/23/2005

NE Time&Date: 16:38:26 09/15/2004

GET DILNA NAME=RACK:0..7/DILNA:0..7 [,REQATTL=ALS, AST, AVS, CELLNO, GNA, COMBMD, LNAMODE, LNAPRED, OST, PRS, RELFUNCOBJ, SCELLNO, WDLNA];

DN0933412 Issue 01275


DILNA

Id:0900d805805b1082


COMMAND: Get DILNA:NAME=RACK:0/DILNA:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23





cellNumber = 1

cableLossAdjust(dB) = Null

combMode = EightToTwo

lnaMode = UNKNOWN

lnaPredecessor = Null




secondCellNumber = NotUsed

wiringDataLna = CU3N & CU2N & CU0D & CU0N


Operation Failed



• The value for the attribute relatedFuncObjects in LMT Evolution Phase 2 is "not con-figured"

• The value for proceduralStatus must be NULL

Example of Command Execution:Get DILNA:NAME=RACK:0/DILNA:0,REQATTL=ALS&AST&AVS&CELLNO&

CLADJ&COMBMD&LNAMODE&LNAPRED&OST&PRS&SCELLNO&WDLNA;

GETTEST DILNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h GETTEST DILNA”

GETTEST DILNA NAME=RACK:0..7/DILNA:0..7;

276DN0933412 Issue 01


Id:0900d805805b1082

DILNA








JOB: 210

PC Time&Date: 12:13:35 03/23/2005

NE Time&Date: 13:15:10 09/15/2004


COMMAND: Gettest DILNA:NAME=RACK:0/DILNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/DILNA:0

testMonitor =

phaseId = PreliminaryTestsDilna


phaseId = CheckAlarmStatusDilna


phaseId = EndTestDilna





Operation Failed


DN0933412 Issue 01277


DILNA

Id:0900d805805b1082


Example of Command Execution:Gettest DILNA:NAME=RACK:0/DILNA:0;

LOCK DILNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h LOCK DILNA”



Command Description:This command changes the administrative state of DILNA (Low Noise Amplifier of Diver-sity Multicoupler).





phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK DILNA NAME=RACK:0..7/DILNA:0..7;

278DN0933412 Issue 01


Id:0900d805805b1082

DILNA

JOB: 100

PC Time&Date: 16:40:38 03/23/2005

NE Time&Date: 16:38:32 09/15/2004


COMMAND: Lock DILNA:NAME=RACK:0/DILNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 101

PC Time&Date: 16:40:38 03/23/2005

NE Time&Date: 16:38:32 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/DILNA:0




Operation Failed



DN0933412 Issue 01279


DILNA

Id:0900d805805b1082

Example of Command Execution:Lock DILNA:NAME=RACK:0/DILNA:0;

PERFTEST DILNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h PERFTEST DILNA”







JOB: 211

PC Time&Date: 12:13:39 03/23/2005

NE Time&Date: 13:15:13 09/15/2004


COMMAND: Perftest DILNA:NAME=RACK:0/DILNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:1


JOB: 212

PC Time&Date: 12:13:42 03/23/2005

PERFTEST DILNA NAME=RACK:0..7/DILNA:0..7;

280DN0933412 Issue 01


Id:0900d805805b1082

DILNA

NE Time&Date: 13:15:17 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1



JOB: 213

PC Time&Date: 12:13:50 03/23/2005

NE Time&Date: 13:15:25 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23









JOB: 214

PC Time&Date: 12:13:50 03/23/2005

NE Time&Date: 13:15:25 09/15/2004


DN0933412 Issue 01281


DILNA

Id:0900d805805b1082

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:1




executedPhases =

PreliminaryTestsDilna

SerialEepromTestDilna

EndTestDilna


JOB: 215

PC Time&Date: 12:13:50 03/23/2005

NE Time&Date: 13:15:25 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1




Result TEST:

name = TEST:<n>



282DN0933412 Issue 01


Id:0900d805805b1082

DILNA

Operation Failed




Example of Command Execution:Perftest DILNA:NAME=RACK:0/DILNA:0;

SET DILNA








executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



SET DILNA NAME=RACK:0..7/DILNA:0..7 [,SCELLNO=] [,WDLNA=];

DN0933412 Issue 01283


DILNA

Id:0900d805805b1082

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h SET DILNA”



Command Description:This command sets the attributes of the DILNA (Low Noise Amplifier of Diversity Multi-coupler) to the BTSE data base.



WDLNA wiringDataLna



JOB: 62

PC Time&Date: 11:57:39 03/23/2005

NE Time&Date: 12:59:14 09/15/2004


COMMAND: Set DILNA:NAME=RACK:0/DILNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• The DIAMCO_LNA and the CUs are in the same rack and belong to the same cell

• Each CU has a 'normal path' RX input and a 'diversity path' RX input and the operator must indicate which of them is wired to the DIAMCO_LNA


284DN0933412 Issue 01


Id:0900d805805b1082

DILNA

• All CUs which are listed in a previous GET DILNA for WDLNA have to be locked (LOCK CU command) before one of these CUs can be removed from WDLNA. Before locking these CUs first a shutdown of the TRXs related to these CUs should be done

Example of Command Execution:Set DILNA:NAME=RACK:0/DILNA:0,SCELLNO=2,WDLNA=CU0D&CU1D&

CU2D&CU3D;

STOPTEST DILNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h STOPTEST DILNA”







STOPTEST DILNA NAME=RACK:0..7/DILNA:0..7;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



DN0933412 Issue 01285


DILNA

Id:0900d805805b1082

Operation Failed



Example of Command Execution:Stoptest DILNA:NAME=RACK:0/DILNA:0;

UNLOCK DILNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h UNLOCK DILNA”



Command Description:This command changes the administrative state of the DILNA (Low Noise Amplifier of Diversity Multicoupler).




JOB: 102

PC Time&Date: 16:40:43 03/23/2005

NE Time&Date: 16:38:37 09/15/2004


COMMAND: Unlock DILNA:NAME=RACK:0/DILNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23

....

skippedPhases


UNLOCK DILNA NAME=RACK:0..7/DILNA:0..7;

286DN0933412 Issue 01


Id:0900d805805b1082

DILNA






JOB: 103

PC Time&Date: 16:40:43 03/23/2005

NE Time&Date: 16:38:37 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



Example of Command Execution:Unlock DILNA:NAME=RACK:0/DILNA:0;

DN0933412 Issue 01287


DUAMCO

Id:0900d805805b1084

DUAMCOThe DUAMCO object is mainly used to represent the status of the firmware download; the state changes of the DUAMCO object are triggered by subsystems RC, AE and DG as usual.

DUAMCO object is automatically created if an MFDUAMCO is successfully registered.

DELETE DUAMCO

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h DELETE DUAMCO”



Command Description:This command deletes the DUAMCO from the BTSE data base.

Automatic deletion is also possible.




JOB: 71

PC Time&Date: 05.05.2008 11:35:33 +02:00

NE Time&Date: 01.01.1990 00:12:10 +00:00

USER NAME: NSN_Cindy

COMMAND: Delete DUAMCO:NAME=RACK:0/DUAMCO:0;

SW RELEASE: 01-04-19-01-86-MF_08-04-24

COMMAND RESULT:Operation successful.


Operation Failed

None.


• The automatic deletion is not possible when a BCOM/FCOM is inserted in ACOM slot

DELETE DUAMCO NAME=RACK:0..7/DUAMCO:0..5;

288DN0933412 Issue 01


Id:0900d805805b1084

DUAMCO

Example of Command Execution:DELETE DUAMCO:

NAME=RACK:0/ DUAMCO:0;

GET DUAMCO

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h GET DUAMCO”



Command Description:This command displays the attributes of DUAMCO object.



ALS alarmStatus





DMCFWID duamcoFwId




JOB: 86

PC Time&Date: 05.05.2008 11:35:48 +02:00

NE Time&Date: 01.01.1990 00:12:25 +00:00


COMMAND: Get DUAMCO:NAME=RACK:0/DUAMCO:0;

SW RELEASE: 01-04-19-01-86-MF_08-04-24




GET DUAMCO NAME=RACK:0..7/DUAMCO:0..5 [,REQATTL=ALS, AST, AVS, OST, PRS, DMCFWID, RELFUNCOBJ];

DN0933412 Issue 01289


DUAMCO

Id:0900d805805b1084




duamcoFwId = "BFDU0250.SWI:00-50-19-02-15-00_08-01-01"



Operation Failed

None.


Example of Command Execution:GetDU-AMCO:NAME=RACK:0/DUAMCO:0,REQATTL=ALS&AST&AVS&OST&PRS&DMCF-WID&RELFUNCOBJ;

GETTEST DUAMCO

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h GETTEST DUAMCO”







None.

Operation Failed

None.


GETTEST DUAMCO NAME=RACK:0..7/DUAMCO:0..5;

290DN0933412 Issue 01


Id:0900d805805b1084

DUAMCO

Example of Command Execution:Gettest DUAMCO:NAME=RACK:0/DUAMCO:0,REQATTL=MORT&TESTMON&TES-TOUT& TESTST;.

LOCK DUAMCO

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h LOCK DUAMCO”



Command Description:This command changes the administrative state of DUAMCO.



After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of Lock command is the following:

JOB: 99

PC Time&Date: 05.05.2008 11:36:17 +02:00.

NE Time&Date: 01.01.1990 00:12:54 +00:00


COMMAND: Lock DUAMCO:NAME=RACK:0/DUAMCO:0;

SW RELEASE: 01-04-19-01-86-MF_08-04-24




Operation Failed

None.


Example of Command Execution:Lock DUAMCO:NAME=RACK:0/DUAMCO:0, AST=“Locked”;

LOCK DUAMCO NAME=RACK:0..7/DUAMCO:0..5;

DN0933412 Issue 01291


DUAMCO

Id:0900d805805b1084

PERFTEST DUAMCO

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h PERFTEST DUAMCO”






After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of perftest command is the following:

JOB: 138.

PC Time&Date: 05.05.2008 11:36:42 +02:00

NE Time&Date: 01.01.1990 00:13:19 +00:00


COMMAND: Perftest DUAMCO:NAME=RACK:0/DUAMCO:0;

SW RELEASE: 01-04-19-01-86-MF_08-04-24


MOT = RACK:0/DUAMCO:0

tO = BTSETEST:1


Operation Failed

None.


Example of Command Execution:Perftest DUAMCO:NAME=RACK:0/DUAMCO:0;

STOPTEST DUAMCO

PERFTEST DUAMCO NAME=RACK:0..7/DUAMCO:0..5;

STOPTEST DUAMCO NAME=RACK:0..7/DUAMCO:0..5;

292DN0933412 Issue 01


Id:0900d805805b1084

DUAMCO

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h STOPTEST DUAMCO”



Command Description:This command is used to interrupt a running asynchronous test in the object.



None.

Operation Failed

None.


Example of Command Execution:Stoptest DUAMCO:NAME=RACK:0/DUAMCO:0;

UNLOCK DUAMCO

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h UNLOCK DUAMCO”



Command Description:This command changes the administrative state of DUAMCO.



After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of unlock command is the following:

UNLOCK DUAMCO NAME=RACK:0..7/DUAMCO:0..5;

DN0933412 Issue 01293


DUAMCO

Id:0900d805805b1084

JOB: 108

PC Time&Date: 05.05.2008 11:36:35 +02:00

NE Time&Date: 01.01.1990 00:13:12 +00:00


COMMAND: Unlock DUAMCO:NAME=RACK:0/DUAMCO:0;

SW RELEASE: 01-04-19-01-86-MF_08-04-24


administrativeState = Unlocked.

Operation Failed

None.


Example of Command Execution:Unlock DUAMCO:NAME=RACK:0/DUAMCO:0, AST=“Unlocked”;

294DN0933412 Issue 01


Id:0900d805805b1087

DUDCTMA

DUDCTMAThe DUDCTMA object represents the power supply module of a TMA (Tower Mounted Amplifier) connected to DUAMCO.

CREATE DUDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA h CREATE DUDCTMA”



Command Description:This command adds the DUAMCO_DC_TMA (DC Power Supply Module of TMA) to the BTSE data base.




JOB: 78

PC Time&Date: 16:38:29 03/23/2005

NE Time&Date: 16:36:23 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/DUDCTMA:0



CREATE DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;

DN0933412 Issue 01295


DUDCTMA

Id:0900d805805b1087

JOB: 79

PC Time&Date: 16:38:29 03/23/2005

NE Time&Date: 16:36:23 09/15/2004

USER NAME: NSN

COMMAND: Create DUDCTMA:NAME=RACK:0/DUDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 75

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create DUDCTMA:NAME=RACK:0/DUDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





Example of Command Execution:Create DUDCTMA:NAME=RACK:0/DUDCTMA:0;

DELETE DUDCTMADELETE DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;

296DN0933412 Issue 01


Id:0900d805805b1087

DUDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA h DELETE DUDCTMA”



Command Description:This command deletes the DUAMCO_DC_TMA (DC Power Supply Module of TMA) from the BTSE data base.




JOB: 90

PC Time&Date: 16:39:22 03/23/2005

NE Time&Date: 16:37:16 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/DUDCTMA:0



JOB: 91

PC Time&Date: 16:39:22 03/23/2005

NE Time&Date: 16:37:16 09/15/2004

USER NAME: NSN

DN0933412 Issue 01297


DUDCTMA

Id:0900d805805b1087

COMMAND: Delete DUDCTMA:NAME=RACK:0/DUDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• DUDCTMA must be locked in phase 3 before deletion

Example of Command Execution:Delete DUDCTMA:NAME=RACK:0/DUDCTMA:0;

GET DUDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA h GET DUDCTMA”



Command Description:This command displays the attributes of the DUAMCO_DC_TMA (DC Power Supply Module of TMA).



ALS alarmStatus







GET DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ];

298DN0933412 Issue 01


Id:0900d805805b1087

DUDCTMA


JOB: 82

PC Time&Date: 16:38:53 03/23/2005

NE Time&Date: 16:36:47 09/15/2004

USER NAME: NSN

COMMAND: Get DUDCTMA:NAME=RACK:0/DUDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23









Operation Failed



Example of Command Execution:Get DUDCTMA:NAME=RACK:0/DUDCTMA:0,REQATTL=ALS&AST&AVS&

OST&PRS&RELFUNCOBJ;

GETTEST DUDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA h GETTEST DUDCTMA”



GETTEST DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;

DN0933412 Issue 01299


DUDCTMA

Id:0900d805805b1087






JOB: 216

PC Time&Date: 12:13:57 03/23/2005

NE Time&Date: 13:15:32 09/15/2004

USER NAME: NSN

COMMAND: Gettest DUDCTMA:NAME=RACK:0/DUDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/DUDCTMA:0

testMonitor =

phaseId = PreliminaryTestsDudctma


phaseId = CheckAlarmStatusDudctma


phaseId = EndTestDudctma





Operation Failed


300DN0933412 Issue 01


Id:0900d805805b1087

DUDCTMA


Example of Command Execution:Gettest DUDCTMA:NAME=RACK:0/DUDCTMA:0;

LOCK DUDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA h LOCK DUDCTMA”



Command Description:This command changes the administrative state of DUAMCO_DC_TMA (DC Power Supply Module of TMA).





phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;

DN0933412 Issue 01301


DUDCTMA

Id:0900d805805b1087

JOB: 83

PC Time&Date: 16:38:58 03/23/2005

NE Time&Date: 16:36:52 09/15/2004

USER NAME: NSN

COMMAND: Lock DUDCTMA:NAME=RACK:0/DUDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 84

PC Time&Date: 16:38:58 03/23/2005

NE Time&Date: 16:36:52 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/DUDCTMA:0




Operation Failed



302DN0933412 Issue 01


Id:0900d805805b1087

DUDCTMA

Example of Command Execution:Lock DUDCTMA:NAME=RACK:0/DUDCTMA:0;

PERFTEST DUDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA h PERFTEST DUDCTMA”







JOB: 216

PC Time&Date: 12:13:57 03/23/2005

NE Time&Date: 13:15:32 09/15/2004

USER NAME: NSN

COMMAND: Perftest DUDCTMA:NAME=RACK:0/DUDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:2


JOB: 217

PC Time&Date: 12:13:58 03/23/2005

PERFTEST DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;

DN0933412 Issue 01303


DUDCTMA

Id:0900d805805b1087

NE Time&Date: 13:15:33 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2



JOB: 218

PC Time&Date: 12:13:58 03/23/2005

NE Time&Date: 13:15:33 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23









JOB: 219

PC Time&Date: 12:13:58 03/23/2005

NE Time&Date: 13:15:33 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23

304DN0933412 Issue 01


Id:0900d805805b1087

DUDCTMA


Test Report:

name = BTSETEST:2




executedPhases =

PreliminaryTestsDudctma

BootEepromTestDudctma

SerialEepromTestDudctma

EndTestDudctma


JOB: 220

PC Time&Date: 12:13:58 03/23/2005

NE Time&Date: 13:15:33 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:2




Result TEST:

name = TEST:<n>



DN0933412 Issue 01305


DUDCTMA

Id:0900d805805b1087

Operation Failed




Example of Command Execution:Perftest DUDCTMA:NAME=RACK:0/DUDCTMA:0;

STOPTEST DUDCTMA








executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



STOPTEST DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;

306DN0933412 Issue 01


Id:0900d805805b1087

DUDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA h STOPTEST DUDCTMA”







Operation Failed



Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


DN0933412 Issue 01307


DUDCTMA

Id:0900d805805b1087

Example of Command Execution:Stoptest DUDCTMA:NAME=RACK:0/DUDCTMA:0;

UNLOCK DUDCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA h UNLOCK DUDCTMA”



Command Description:This command changes the administrative state of DUAMCO_DC_TMA (DC Power Supply Module of TMA).




JOB: 85

PC Time&Date: 16:39:03 03/23/2005

NE Time&Date: 16:36:57 09/15/2004

USER NAME: NSN

COMMAND: Unlock DUDCTMA:NAME=RACK:0/DUDCTMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






UNLOCK DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;

308DN0933412 Issue 01


Id:0900d805805b1087

DUDCTMA

JOB: 86

PC Time&Date: 16:39:03 03/23/2005

NE Time&Date: 16:36:57 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



Example of Command Execution:Unlock DUDCTMA:NAME=RACK:0/DUDCTMA:0;

DN0933412 Issue 01309


DULNA

Id:0900d805805b1089

DULNAThe DULNA object represents the low noise amplifier of DUAMCO (Dual Antenna Mul-ticoupler) or FDUAMCO.

CREATE DULNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h CREATE DULNA”



Command Description:This command adds the DULNA (Low Noise Amplifier of Duplex Antenna Multicoupler) together with its attributes to the BTSE data base.


CELLNO cellNumber

COMBMD combMode

LNAMDB lnaModeDb



WDLNA wiringDataLna

GNADB gainAdjustDb



JOB: 92

PC Time&Date: 11:59:23 03/23/2005

NE Time&Date: 13:00:58 09/15/2004

USER NAME: NSN

CREATE DULNA NAME=RACK:0..7/DULNA:0..11 ,CELLNO= ,COMBMD= [,LNAMDB=] [,LNAPRED=] [,SCELLNO=] ,WDLNA= [,GNADB=];

310DN0933412 Issue 01


Id:0900d805805b1089

DULNA

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/DULNA:0



JOB: 93

PC Time&Date: 11:59:23 03/23/2005

NE Time&Date: 13:00:58 09/15/2004

USER NAME: NSN

COMMAND: Create DULNA:NAME=RACK:0/DULNA:0,CELLNO=0,COMBMD=One-ToOne,WDLNA=CU0N;

SW RELEASE: 01-04-17-01-26-51_05-02-23


cellNumber = 0

combMode = OneToOne

secondCellNumber = 2

wiringDataLna = CU0N


Operation Failed


JOB: 94

PC Time&Date: 11:59:23 03/23/2005

NE Time&Date: 13:00:58 09/15/2004

USER NAME: NSN

COMMAND: Create DULNA:NAME=RACK:0/DULNA:2;

DN0933412 Issue 01311


DULNA

Id:0900d805805b1089

SW RELEASE: 01-04-17-01-26-51_05-02-23





• One DUAMCO contains two DUAMCO_LNA. The first DUAMCO within the rack is put in the first slot, the second DUAMCO in the second slot and so on. This means that DUAMCO_LNA 0 and DUAMCO_LNA 1 are always physically located in the first slot within the rack, the DUAMCO_LNA 2 and DUAMCO_LNA 3 in the second slot and so on

• The DUAMCO_LNA and the CUs must be in the same rack and must belong to the same cell

• Each CU has a 'normal path' RX input and a 'diversity path' RX input and the operator must indicate which of them is wired to the DUAMCO_LNA

• If there is no wiring the operator must not provide a value for the attribute LNAPRED (if a get is done the attribute identifier will be put into the list of unavailable attributes)

• If there is no wiring for the attribute LNAPRED and the operator enters a value, this error can be corrected by a deletion of the object and a re-creation of the object

• The BTSE SW doesn't check if the entered "predecessor (relative number)" is com-patible with typeOfBTSE; e.g. an input of TMA 11 is not rejected in a BS40 although BS40 allows only the creation of TMA 0-5

The BTSE SW doesn't check if the entered "predecessor (rack)" is compatible with typeOfBTSE; e.g. an input of RACK 1 is not rejected in a BS40 although BS40 allows only the creation of RACK 0


Example of Command Execution:Create DULNA:NAME=RACK:1/DULNA:0,CELLNO=0,COMBMD=FourToOne,

SCELLNO=2,WDLNA=CU0N&CU1N&CU2N&CU3N,LNAPRED=DULNA-RACK0-0;

DELETE DULNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h DELETE DULNA”



DELETE DULNA NAME=RACK:0..7/DULNA:0..11;

312DN0933412 Issue 01


Id:0900d805805b1089

DULNA

Command Description:This command deletes the DULNA (Low Noise Amplifier of Duplex Antenna Multicou-pler) together with its attributes from the BTSE data base.




JOB: 86

PC Time&Date: 11:58:47 03/23/2005

NE Time&Date: 13:00:22 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/DULNA:0



JOB: 87

PC Time&Date: 11:58:47 03/23/2005

NE Time&Date: 13:00:22 09/15/2004

USER NAME: NSN

COMMAND: Delete DULNA:NAME=RACK:0/DULNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed

DN0933412 Issue 01313


DULNA

Id:0900d805805b1089



• DULNA must be locked in Phase 3, before deletion


Example of Command Execution:Delete DULNA:NAME=RACK:0/DULNA:0;

GET DULNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h GET DULNA”



Command Description:This command displays the attributes of the DULNA (Low Noise Amplifier of Duplex Antenna Multicoupler).



ALS alarmStatus



CELLNO cellNumber

GNA gainAdjust(dB)

COMBMD combMode

LNAMDB lnaModeDb

LNAMODE lnaMode






GET DULNA NAME=RACK:0..7/DULNA:0..11 [,REQATTL=ALS, AST, AVS, CELLNO, GNA, COMBMD, LNAMDB, LNAMODE, LNAPRED, OST, PRS, RELFUNCOBJ, SCELLNO, WDLNA, GNADB];

314DN0933412 Issue 01


Id:0900d805805b1089

DULNA

WDLNA wiringDataLna

GNADB gainAdjustDb



JOB: 63

PC Time&Date: 11:58:17 03/23/2005

NE Time&Date: 12:59:52 09/15/2004

USER NAME: NSN

COMMAND: Get DULNA:NAME=RACK:0/DULNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





cellNumber = 0

cableLossAdjust(dB) = N_00

combMode = OneToOne

lnaMode = AMCO_MODE






wiringDataLna = CU1


Operation Failed


DN0933412 Issue 01315


DULNA

Id:0900d805805b1089




Example of Command Execution:Get DULNA:NAME=RACK:0/DULNA:0,REQATTL=ALS&AST&AVS&CELLNO&

CLADJ&COMBMD&RELFUNCOBJ&LNAMODE&LNAPRED&OST&PRS&SCELLNO&

WDLNA;

GETTEST DULNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h GETTEST DULNA”







After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of getest command is the following:

JOB: 72

PC Time&Date: 11:58:33 03/23/2005

NE Time&Date: 13:00:08 09/15/2004

USER NAME: NSN

COMMAND: Gettest DULNA:NAME=RACK:0/DULNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


GETTEST DULNA NAME=RACK:0..7/DULNA:0..11;

316DN0933412 Issue 01


Id:0900d805805b1089

DULNA

MOT = RACK:0/DULNA:0

testMonitor =

phaseId = PreliminaryTestsDulna


phaseId = CheckAlarmStatusDulna


phaseId = EndTestDulna





Operation Failed



Example of Command Execution:Gettest DULNA:NAME=RACK:0/DULNA:0;

LOCK DULNA


phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK DULNA NAME=RACK:0..7/DULNA:0..11;

DN0933412 Issue 01317


DULNA

Id:0900d805805b1089

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h LOCK DULNA”



Command Description:This command changes the administrative state of DULNA (Low Noise Amplifier of Duplex Antenna Multicoupler).




JOB: 73

PC Time&Date: 11:58:33 03/23/2005

NE Time&Date: 13:00:08 09/15/2004

USER NAME: NSN

COMMAND: Lock DULNA:NAME=RACK:0/DULNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 74

PC Time&Date: 11:58:33 03/23/2005

NE Time&Date: 13:00:08 09/15/2004

318DN0933412 Issue 01


Id:0900d805805b1089

DULNA

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/DULNA:0




Operation Failed



Example of Command Execution:Lock DULNA:NAME=RACK:0/DULNA:0;

PERFTEST DULNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h PERFTEST DULNA”







JOB: 77

PERFTEST DULNA NAME=RACK:0..7/DULNA:0..11;

DN0933412 Issue 01319


DULNA

Id:0900d805805b1089

PC Time&Date: 11:58:39 03/23/2005

NE Time&Date: 13:00:14 09/15/2004

USER NAME: NSN

COMMAND: Perftest DULNA:NAME=RACK:0/DULNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:4


JOB: 78

PC Time&Date: 11:58:39 03/23/2005

NE Time&Date: 13:00:14 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:4



JOB: 79

PC Time&Date: 11:58:39 03/23/2005

NE Time&Date: 13:00:14 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



320DN0933412 Issue 01


Id:0900d805805b1089

DULNA






JOB: 80

PC Time&Date: 11:58:39 03/23/2005

NE Time&Date: 13:00:14 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:4




executedPhases =

PreliminaryTestsDulna

CheckAlarmStatusDulna

EndTestDulna


JOB: 81

PC Time&Date: 11:58:39 03/23/2005

NE Time&Date: 13:00:14 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


DN0933412 Issue 01321


DULNA

Id:0900d805805b1089


name = BTSETEST:4




Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



322DN0933412 Issue 01


Id:0900d805805b1089

DULNA

Operation Failed




Example of Command Execution:Perftest DULNA:NAME=RACK:0/DULNA:0;

SET DULNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h SET DULNA”



Command Description:This command sets the attributes of the DULNA (Low Noise Amplifier of Duplex Antenna Multicoupler) to the BTSE data base.


LNAMDB lnaModeDb


WDLNA wiringDataLna

GNADB gainAdjustDb



JOB: 75

PC Time&Date: 11:58:36 03/23/2005

NE Time&Date: 13:00:11 09/15/2004

SET DULNA NAME=RACK:0..7/DULNA:0..11 [,LNAMDB=] [,SCELLNO=] [,WDLNA=] [,GNADB=];

DN0933412 Issue 01323


DULNA

Id:0900d805805b1089

USER NAME: NSN

COMMAND: Set DULNA:NAME=RACK:0/DULNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• One DUAMCO contains two DUAMCO_LNA. The first DUAMCO within the rack is put in the first slot, the second DUAMCO in the second slot and so on. This means that DUAMCO_LNA 0 and DUAMCO_LNA 1 are always physically located in the first slot within the rack, the DUAMCO_LNA 2 and DUAMCO_LNA 3 in the second slot and so on

• The DUAMCO_LNA and the CUs must be in the same rack and must belong to the same cell

• Each CU has a 'normal path' RX input and a 'diversity path' RX input and the operator must indicate which of them is wired to the DUAMCO_LNA


• All CUs which are listed in a previous GET DULNA for WDLNA have to be locked (LOCK CU command) before one of these CUs can be removed from WDLNA. Before locking these CUs first a shutdown of the TRXs related to these CUs should be done

Example of Command Execution:Set DULNA:NAME=RACK:0/DULNA:0,SCELLNO=2,WDLNA=CU0N&CU1N&

CU2N&CU3N;

STOPTEST DULNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h STOPTEST DULNA”




STOPTEST DULNA NAME=RACK:0..7/DULNA:0..11;

324DN0933412 Issue 01


Id:0900d805805b1089

DULNA




Operation Failed



Example of Command Execution:Stoptest DULNA:NAME=RACK:0/DULNA:0;

UNLOCK DULNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h UNLOCK DULNA”

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


UNLOCK DULNA NAME=RACK:0..7/DULNA:0..11;

DN0933412 Issue 01325


DULNA

Id:0900d805805b1089



Command Description:This command changes the administrative state of the DULNA (Duplex Antenna Multi-coupler).




JOB: 82

PC Time&Date: 11:58:41 03/23/2005

NE Time&Date: 13:00:16 09/15/2004

USER NAME: NSN

COMMAND: Unlock DULNA:NAME=RACK:0/DULNA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 83

PC Time&Date: 11:58:41 03/23/2005

NE Time&Date: 13:00:16 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


326DN0933412 Issue 01


Id:0900d805805b1089

DULNA






Operation Failed



Example of Command Execution:Unlock DULNA:NAME=RACK:0/DULNA:0;

DN0933412 Issue 01327


DUVSWR

Id:0900d805805b108b

DUVSWRThe DUVSWR object represents the VSWR of DUAMCO. A VSWR alarm indicates an antenna failure.

CREATE DUVSWR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h CREATE DUVSWR”



Command Description:This command adds the DUVSWR (Voltage Standing Wave Ratio Duplex Antenna Mul-ticoupler) together with its attributes to the BTSE data base.


CELLNO cellNumber

COMBMD combMode

WDDUVSWR wiringDuamcoVswr

VSWRTDB vswrThresholdDb



JOB: 112

PC Time&Date: 12:00:05 03/23/2005

NE Time&Date: 13:01:40 09/15/2004

USER NAME: NSN_Robert

SW RELEASE: 01-04-17-01-26-51_05-02-23



CREATE DUVSWR NAME=RACK:0..7/DUVSWR:0..11 ,CELLNO= ,COMBMD= ,WDDUVSWR= [,VSWRTDB=];

328DN0933412 Issue 01


Id:0900d805805b108b

DUVSWR

name = RACK:0/DUVSWR:0



JOB: 113

PC Time&Date: 12:00:05 03/23/2005

NE Time&Date: 13:01:40 09/15/2004


COMMAND: Create DUVSWR:NAME=RACK:0/DUVSWR:0,CELLNO=0,WDDU-VSWR=CU0,COMBMD=OneToOne;

SW RELEASE: 01-04-17-01-26-51_05-02-23


cellNumber = 0

wiringDuamcoVswr = CU0

combMode = OneToOne


Operation Failed


JOB: 114

PC Time&Date: 12:00:05 03/23/2005

NE Time&Date: 13:01:40 09/15/2004


COMMAND: Create DUVSWR:NAME=RACK:0/DUVSWR:2;

SW RELEASE: 01-04-17-01-26-51_05-02-23




DN0933412 Issue 01329


DUVSWR

Id:0900d805805b108b


• One DUAMCO contains two DUAMCO_VSWR. The first DUAMCO within the rack is put in the first slot, the second DUAMCO in the second slot and so on. This means that DUAMCO_VSWR 0 and DUAMCO_VSWR 1 are always physically located in the first slot within the rack, the DUAMCO_VSWR 2 and DUAMCO_VSWR 3 in the second slot and so on

• The DUAMCO_VSWR and the CUs must be in the same rack and must belong to the same cell

• Due to the physical properties of the DUAMCO_VSWR, up to 4 CUs can be con-nected


Example of Command Execution:Create DUVSWR:NAME=RACK:0/DUVSWR:0,CELLNO=0,COMBMD=TwoToTwo,

WDDUVSWR=CU0&CU1;

DELETE DUVSWR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h DELETE DUVSWR”



Command Description:This command deletes the DUVSWR (Voltage Standing Wave Ratio Duplex Antenna Multicoupler) together with its attributes from the BTSE data base.




JOB: 110

PC Time&Date: 11:59:58 03/23/2005

NE Time&Date: 13:01:33 09/15/2004

DELETE DUVSWR NAME=RACK:0..7/DUVSWR:0..11;

330DN0933412 Issue 01


Id:0900d805805b108b

DUVSWR


SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/DUVSWR:0



JOB: 111

PC Time&Date: 11:59:58 03/23/2005

NE Time&Date: 13:01:33 09/15/2004


COMMAND: Delete DUVSWR:NAME=RACK:0/DUVSWR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• DUVSWR must be locked in Phase 3, before deletion


Example of Command Execution:Delete DUVSWR:NAME=RACK:0/DUVSWR:0;

GET DUVSWRGET DUVSWR NAME=RACK:0..7/DUVSWR:0..11 [,REQATTL=ALS, AST,

AVS, CELLNO, COMBMD, OST, PRS, RELFUNCOBJ, WDDUVSWR, VSWRTDB];

DN0933412 Issue 01331


DUVSWR

Id:0900d805805b108b

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h GET DUVSWR”



Command Description:This command displays the attributes of the DUVSWR (Voltage Standing Wave Ratio Duplex Antenna Multicoupler).



ALS alarmStatus



CELLNO cellNumber

COMBMD combMode








JOB: 95

PC Time&Date: 11:59:35 03/23/2005

NE Time&Date: 13:01:10 09/15/2004


COMMAND: Get DUVSWR:NAME=RACK:0/DUVSWR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



332DN0933412 Issue 01


Id:0900d805805b108b

DUVSWR



cellNumber = 0

combMode = TwoToTwo



relatedFuncObjects = BTS:0/TRX:2

wiringDuamcoVswr = CU0


Operation Failed



• The value for the attribute gsmFunctionalID in LMT Evolution Phase 2 is "not con-figured"


Example of Command Execution:Get DUVSWR:NAME=RACK:0/DUVSWR:0,REQATTL=ALS&AST&AVS&CELLNO&

COMBMD&OST&PRS&RELFUNCOBJ&DDUVSWR;

GETTEST DUVSWR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h GETTEST DUVSWR”







GETTEST DUVSWR NAME=RACK:0..7/DUVSWR:0..11;

DN0933412 Issue 01333


DUVSWR

Id:0900d805805b108b


JOB: 101

PC Time&Date: 11:59:50 03/23/2005

NE Time&Date: 13:01:25 09/15/2004


COMMAND: Gettest DUVSWR:NAME=RACK:0/DUVSWR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/DUVSWR:0

testMonitor =

phaseId = PreliminaryTestsDuvswr


phaseId = CheckAlarmStatusDuvswr


phaseId = EndTestDuvswr





Operation Failed



phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...

334DN0933412 Issue 01


Id:0900d805805b108b

DUVSWR


Example of Command Execution:Gettest DUVSWR:NAME=RACK:0/DUVSWR:0;

LOCK DUVSWR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h LOCK DUVSWR”



Command Description:This command changes the administrative state of DUVSWR (Voltage Standing Wave Ratio Duplex Antenna Multicoupler).




JOB: 99

PC Time&Date: 11:59:48 03/23/2005

NE Time&Date: 13:01:23 09/15/2004


COMMAND: Lock DUVSWR:NAME=RACK:0/DUVSWR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



LOCK DUVSWR NAME=RACK:0..7/DUVSWR:0..11;

DN0933412 Issue 01335


DUVSWR

Id:0900d805805b108b






JOB: 100

PC Time&Date: 11:59:48 03/23/2005

NE Time&Date: 13:01:23 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/DUVSWR:0




Operation Failed



Example of Command Execution:Lock DUVSWR:NAME=RACK:0/DUVSWR:0;

PERFTEST DUVSWR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h PERFTEST DUVSWR”

PERFTEST DUVSWR NAME=RACK:0..7/DUVSWR:0..11;

336DN0933412 Issue 01


Id:0900d805805b108b

DUVSWR







JOB: 102

PC Time&Date: 11:59:50 03/23/2005

NE Time&Date: 13:01:25 09/15/2004


COMMAND: Perftest DUVSWR:NAME=RACK:0/DUVSWR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:5


JOB: 103

PC Time&Date: 11:59:50 03/23/2005

NE Time&Date: 13:01:25 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



DN0933412 Issue 01337


DUVSWR

Id:0900d805805b108b

name = BTSETEST:5



JOB: 104

PC Time&Date: 11:59:50 03/23/2005

NE Time&Date: 13:01:25 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23








JOB: 105

PC Time&Date: 11:59:50 03/23/2005

NE Time&Date: 13:01:25 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:5




executedPhases =

338DN0933412 Issue 01


Id:0900d805805b108b

DUVSWR

PreliminaryTestsDuvswr

CheckAlarmStatusDuvswr

EndTestDuvswr


JOB: 106

PC Time&Date: 11:59:50 03/23/2005

NE Time&Date: 13:01:25 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:5




Result TEST:

name = TEST:<n>










DN0933412 Issue 01339


DUVSWR

Id:0900d805805b108b

Operation Failed




Example of Command Execution:Perftest DUVSWR:NAME=RACK:0/DUVSWR:0;

SET DUVSWR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h SET DUVSWR”



Command Description:This command sets the attributes of the DUVSWR (Voltage Standing Wave Ratio Duplex Antenna Multicoupler) to the BTSE data base.


executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



SET DUVSWR NAME=RACK:0..7/DUVSWR:0..11 [,WDDUVSWR=] [,VSWRTDB=];

340DN0933412 Issue 01


Id:0900d805805b108b

DUVSWR





JOB: 109

PC Time&Date: 11:59:53 03/23/2005

NE Time&Date: 13:01:28 09/15/2004


COMMAND: Set DUVSWR:NAME=RACK:0/DUVSWR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• One DUAMCO contains two DUAMCO_VSWR. The first DUAMCO within the rack is put in the first slot, the second DUAMCO in the second slot and so on. This means that DUAMCO_VSWR 0 and DUAMCO_VSWR 1 are always physically located in the first slot within the rack, the DUAMCO_VSWR 2 and DUAMCO_VSWR 3 in the second slot and so on

• The DUAMCO_VSWR and the CUs must be in the same rack and must belong to the same cell

• Due to the physical properties of the DUAMCO_VSWR, up to 4 CUs can be con-nected


• All CUs which are listed in a previous GET DUVSWR for WDDUVSWR have to be locked (LOCK CU command) before one of these CUs can be removed from WDDUVSWR. Before locking these CUs first a shutdown of the TRXs related to these CUs should be done

Example of Command Execution:Set DUVSWR:NAME=RACK:0/DUVSWR:0,WDLNA=CU0N&CU1N&CU2N&CU3N;

DN0933412 Issue 01341


DUVSWR

Id:0900d805805b108b

STOPTEST DUVSWR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h STOPTEST DUVSWR”







Operation Failed


STOPTEST DUVSWR NAME=RACK:0..7/DUVSWR:0..11;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


342DN0933412 Issue 01


Id:0900d805805b108b

DUVSWR


Example of Command Execution:Stoptest DUVSWR:NAME=RACK:0/DUVSWR:0;

UNLOCK DUVSWR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h UNLOCK DUVSWR”



Command Description:This command changes the administrative state of the DUVSWR (Voltage Standing Wave Ratio Duplex Antenna Multicoupler).




JOB: 97

PC Time&Date: 11:59:44 03/23/2005

NE Time&Date: 13:01:19 09/15/2004


COMMAND: Unlock DUVSWR:NAME=RACK:0/DUVSWR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





UNLOCK DUVSWR NAME=RACK:0..7/DUVSWR:0..11;

DN0933412 Issue 01343


DUVSWR

Id:0900d805805b108b


JOB: 98

PC Time&Date: 11:59:44 03/23/2005

NE Time&Date: 13:01:19 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



Example of Command Execution:Unlock DUVSWR:NAME=RACK:0/DUVSWR:0;

344DN0933412 Issue 01


Id:0900d805805b108d

ENVABTSE

ENVABTSEThe ENVABTSE object is used to manage the enviromental alarms of the BTSplus mainline.

CREATE ENVABTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE h CREATE ENVABTSE”



Command Description:This command configures one of the 9 possible environmental alarms (in the Base Rack optionally the ACTM can be installed that supplies 48 additional ENVAs) in the BTSE database (BS40/41, BS240/241, BS240XL, BS40II).

For BS82II this command configures one of the 6 possible environmental alarms.


ASEV associatedSeverity

ASTRING associatedString

INTINF interfaceInformation



JOB: 116

PC Time&Date: 12:00:26 03/23/2005

NE Time&Date: 13:02:01 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


CREATE ENVABTSE NAME=RACK:0..7/ENVABTSE:0..56 [,ASEV=] [,ASTRING=] ,INTINF=;

DN0933412 Issue 01345


ENVABTSE

Id:0900d805805b108d


name = RACK:0/ENVABTSE:0



JOB: 117

PC Time&Date: 12:00:26 03/23/2005

NE Time&Date: 13:02:01 09/15/2004

USER NAME: NSN

COMMAND: Create ENVABTSE:NAME=RACK:0/ENVABTSE:0,INTINF=low;

SW RELEASE: 01-04-17-01-26-51_05-02-23


interfaceInformation = low


Operation Failed


JOB: 119

PC Time&Date: 12:00:31 03/23/2005

NE Time&Date: 13:02:06 09/15/2004

USER NAME: NSN

COMMAND: Create ENVABTSE:NAME=RACK:0/ENVABTSE:1,INTINF=high;

SW RELEASE: 01-04-17-01-26-51_05-02-23




346DN0933412 Issue 01


Id:0900d805805b108d

ENVABTSE

Application Guidelines:For BS241:

• All ENVAs can be left as not equipped

• In the Base Rack with only ACTC installed 9 ENVAs within the range from 0...8 are supported as shown in the table below. In the Base Rack optionally the ACTM can be installed that supplies 48 additional ENVAs

• In the other Racks with ACTC installed 9 ENVAs within the range from 0...8 are sup-ported as shown in the table below

For BS240 Compact Site:

• The AC/DC alarm line for the AC/DC converter and for the battery must be con-nected to a site input which is used as a trigger for the emergency configuration

• A special setting of the attribute "associatedString" in the corresponding site input allows the operator to indicate that the support of emergency configuration is required for the 3rd party battery backup unit system. The string indicates from which source, AC/DC CAN node or site input, the trigger for the emergency config-uration is expected. In case the string pattern is set to "##ACDC_FAULT" the trigger is expected from the site input of the corresponding ENVABTSE object. In all other cases the normal behavior is maintained

• For simplicity there is no check if the string "##ACDC_FAULT" is used for more than one ENVABTSE object. If the operator has set the "associatedString" attribute of an ENVABTSE object to "##ACDC_FAULT" for the AC/DC alarm line, the emergency configuration is deactivated if all trigger sources have ceased their alarm

ENVA No. Application

0 Heatexchanger - 0

1 Heatexchanger - 1

2 Heatexchanger - 2

3 Rack/Shelter in service

4 Smoke

5 Battery Fuse 0, 1, 2

6 Over Voltage Protection (it has to be configured with "HIGH")

7

8 Microwave

ENVA No. Applica-tion

Severity String

6 HIGH CRITICAL Over Voltage Protection (Â¿Â¿Â¿)

9 HIGH CRITICAL Shelter door open

10 HIGH CRITICAL Conditioners FAULT

DN0933412 Issue 01347


ENVABTSE

Id:0900d805805b108d

For BS40II:

– The FAN5 alarm is not utilized in the case of a BS-40II (deactivated by S/W).

– ACTC-3 alarms

11 HIGH CRITICAL Shelter Temperature Out Tolerance

12 HIGH CRITICAL Shelter in service

13 HIGH CRITICAL Not connected

14 HIGH CRITICAL Mains Breakdown

15 HIGH CRITICAL Critical Battery Breakdown

16 HIGH CRITICAL Critical Battery Charging Fault

17 HIGH CRITICAL -48 dc Out Tolerance

18 HIGH CRITICAL Redundancy Lost





27 HIGH CRITICAL Critical Smoke

28 HIGH CRITICAL Critical Available 1


30 HIGH CRITICAL Critical AC lightning Protection




34 HIGH CRITICAL Critical Conditioner ALM

34 HIGH CRITICAL Critical Filters ALM






ENVA No.

0 High / Low Active

1 High / Low Active

2 High / Low Active Mains Breackdown (MBR) note 1 and 2

3 High / Low Active Battery Breackdown (BBR) note 1

348DN0933412 Issue 01


Id:0900d805805b108d

ENVABTSE

Note:

1. Only relevant for BS with AC/DC system, all AC/DC alarms are "High Active".

2. For MBR alarm the 'associated string' must be: '##ACDC_FAULT' to make this alarm trigger the 'emergency configuration'.'emergency configuration'

Example of Command Execution:Create ENVABTSE:NAME=RACK:0/ENVABTSE:17,INTINF=high,

ASEV=CRITICAL, ASTRING="Air Condition. Sys. Fault";

DELETE ENVABTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE h DELETE ENVABTSE”



Command Description:BS24x, BS4x

This command deletes one of the 9 possible environmental alarms (in the Base Rack optionally the ACTM can be installed that supplies 48 additional ENVAs) from the BTSE database.




JOB: 130

PC Time&Date: 12:00:52 03/23/2005

4 SMOKE - High / Low Active

5 Battery Breacker (BB) - High / Low Active

6 Over Voltage Protection(OVP) - High / Low Active

7 High / Low Active - Battery Charger Fault (BCHF) note 1

8 High / Low Active - -48Vdc Out of Tolerance (48OTB) note 1

DELETE ENVABTSE NAME=RACK:0..7/ENVABTSE:0..56;

DN0933412 Issue 01349


ENVABTSE

Id:0900d805805b108d

NE Time&Date: 13:02:27 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/ENVABTSE:0



JOB: 131

PC Time&Date: 12:00:52 03/23/2005

NE Time&Date: 13:02:27 09/15/2004

USER NAME: NSN

COMMAND: Delete ENVABTSE:NAME=RACK:0/ENVABTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• ENVABTSE must be locked in phase 3 before deletion

Example of Command Execution:Delete ENVABTSE:NAME=RACK:0/ENVABTSE:17;

GET ENVABTSEGET ENVABTSE NAME=RACK:0..7/ENVABTSE:0..56 [,REQATTL=ALS,

ASEV, AST, ASTRING, AVS, INTINF, OST, PRS, RELFUN-COBJ];

350DN0933412 Issue 01


Id:0900d805805b108d

ENVABTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE h GET ENVABTSE”



Command Description:This command displays the attributes of the specified Environmental Alarm stored in the BTSE database.



ALS alarmStatus

ASEV associatedSeverity


ASTRING associatedString








JOB: 118

PC Time&Date: 12:00:29 03/23/2005

NE Time&Date: 13:02:04 09/15/2004

USER NAME: NSN

COMMAND: Get ENVABTSE:NAME=RACK:0/ENVABTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



associatedSeverity = DEFAULT_DB

DN0933412 Issue 01351


ENVABTSE

Id:0900d805805b108d


associatedString =


interfaceInformation = low





Operation Failed



• For BS24x all environmental alarms can be left as not equipped (default value)

• Refer to Application Guidelines: in CREATE ENVABTSE command for more detailed information.

Example of Command Execution:Get ENVABTSE:NAME=RACK:0/ENVABTSE:17,REQATTL=ALS&ASEV&

ASTRING&AST&AVS&INTINF&OST&PRS&RELFUNCOBJ;

LOCK ENVABTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE h LOCK ENVABTSE”



Command Description:This command changes the administrative state of the environmental alarms.




JOB: 128

LOCK ENVABTSE NAME=RACK:0..7/ENVABTSE:0..56;

352DN0933412 Issue 01


Id:0900d805805b108d

ENVABTSE

PC Time&Date: 12:00:47 03/23/2005

NE Time&Date: 13:02:22 09/15/2004

USER NAME: NSN

COMMAND: Lock ENVABTSE:NAME=RACK:0/ENVABTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 129

PC Time&Date: 12:00:47 03/23/2005

NE Time&Date: 13:02:22 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/ENVABTSE:0




Operation Failed



• If the administrative state is set to locked, no alarm is generated

DN0933412 Issue 01353


ENVABTSE

Id:0900d805805b108d

Example of Command Execution:Lock ENVABTSE:NAME=RACK:0/ENVABTSE:0;

SET ENVABTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE h SET ENVABTSE”



Command Description:This command configures one of the 9 possible environmental alarms (in the Base Rack optionally the ACTM can be installed that supplies 48 additional ENVAs) in the BTSE database.





JOB: 125

PC Time&Date: 12:00:39 03/23/2005

NE Time&Date: 13:02:14 09/15/2004

USER NAME: NSN

COMMAND: Set ENVABTSE:NAME=RACK:0/ENVABTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


SET ENVABTSE NAME=RACK:0..7/ENVABTSE:0..56 [,INTINF=];

354DN0933412 Issue 01


Id:0900d805805b108d

ENVABTSE


• For BS24x all environmental alarms can be left as not equipped (default value)

• See Application Guidelines: in CREATE ENVABTSE command for more detailed information

• For BS41 and BS241 the smoke alarm must be set on low-active or high-active depending on the respective installed sensor type

Example of Command Execution:Set ENVABTSE:NAME=RACK:0/ENVABTSE:4,INTINF=high;

UNLOCK ENVABTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE h UNLOCK ENVABTSE”



Command Description:This command changes the administrative state of the environmental alarms.




JOB: 126

PC Time&Date: 12:00:41 03/23/2005

NE Time&Date: 13:02:16 09/15/2004

USER NAME: NSN

COMMAND: Unlock ENVABTSE:NAME=RACK:0/ENVABTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




UNLOCK ENVABTSE NAME=RACK:0..7/ENVABTSE:0..56;

DN0933412 Issue 01355


ENVABTSE

Id:0900d805805b108d



JOB: 127

PC Time&Date: 12:00:41 03/23/2005

NE Time&Date: 13:02:16 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/ENVABTSE:0




Operation Failed



Example of Command Execution:Unlock ENVABTSE:NAME=RACK:0/ENVABTSE:0;

356DN0933412 Issue 01


Id:0900d805805b1091

ETHCON

ETHCONThe ETHCON board provides external electrical and optical Ethernet interfaces to connect the related Flexi BSC product family, other BTSplus mainlines in multidrop-like configurations and test equipment for Abis monitoring.

It therefore houses a manageable Ethernet switch which is controlled by the COBA. Nevertheless the board is able to operate autonomously from the COBA in order to maintain multidrop-like connections to other BTSE e.g. in case of a COBA reset.

The ETHCON board (ETHernet CONnection) is modeled by:

• one ETHCON instance representing the board

• n ETHPORT instances representing the external Ethernet ports (except for monitor-ing port(s))

The ETHCON object is introduced for state indication and alarm reporting. The object state comprise the board, the traffic link and the switch management link to the COBA.

CREATE ETHCON

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h CREATE ETHCON”



Command Description:This command adds an Ethernet Connection board to the BTSE data base.




JOB: 15

PC Time&Date: 09.10.2008 09:40:08 +02:00

NE Time&Date: 01.01.1990 00:02:17 +00:00

USER NAME: NSN_Paul

COMMAND: Create ETHCON:NAME=RACK:0/ETHCON:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08



CREATE ETHCON NAME=RACK:0..7/ETHCON:0..0;

DN0933412 Issue 01357


ETHCON

Id:0900d805805b1091

JOB: 18

PC Time&Date: 09.10.2008 09:40:08 +02:00

NE Time&Date: 01.01.1990 00:02:17 +00:00

USER NAME: NSN_Paul

SW RELEASE: 03-04-19-06-11-06_08-10-08



NAME = RACK:0/ETHCON:0


Availability Status = NULL_VALUE



Operation Failed

None.


• The creation is rejected if a COBA2P8 or COBA4P12 is already equipped

Example of Command Execution:Create ETHCON:NAME=RACK:0/ETHCON:0;

DELETE ETHCON

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h DELETE ETHCON”



Command Description:This command deletes the ETHCON (ETHernet CONnection) board from the BTSE data base.




JOB: 32

DELETE ETHCON NAME=RACK:0..7/ETHCON:0..0;

358DN0933412 Issue 01


Id:0900d805805b1091

ETHCON

PC Time&Date: 09.10.2008 09:41:07 +02:00

NE Time&Date: 01.01.1990 00:03:16 +00:00

USER NAME: NSN_Paul

COMMAND: Delete ETHCON:NAME=RACK:0/ETHCON:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08



Operation Failed

None.


• The deletion is rejected as long as an ETHPORT and/or CESTUNNEL object exists.

Example of Command Execution:Delete ETHCON:NAME=RACK:0/ETHCON:0;

GET ETHCON

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h GET ETHCON”



Command Description:This command displays the attributes of the ETHCON.



ALS alarmStatus





FWVER firmwareVersion


MONPRT monitoringPort

GET ETHCON NAME=RACK:0..7/ETHCON:0..0 [,REQATTL=ALS, AST, AVS, OST, PRS, FWVER, RELFUNCOBJ, MONPRT];

DN0933412 Issue 01359


ETHCON

Id:0900d805805b1091


After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. A message indicates the result of the operation. An example of get command is the following:

JOB: 24

PC Time&Date: 09.10.2008 09:40:41 +02:00

NE Time&Date: 01.01.1990 00:02:50 +00:00

USER NAME: NSN_Paul

COMMAND: Get ETHCON:NAME=RACK:0/ETHCON:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08




availabilityStatus = NULL.




monitoringPort = none


Operation Failed

None.


Example of Command Execution:Get ETHCON:NAME=RACK:0/ETHCON:0,REQATTL=ALS&AST&AVS&OST& PRS& RELFUNCOBJ& MONPRT;

LOCK ETHCON

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h LOCK ETHCON”



Command Description:This command changes the administrative state of the ETHCON board.

LOCK ETHCON NAME=RACK:0..7/ETHCON:0..0;

360DN0933412 Issue 01


Id:0900d805805b1091

ETHCON




JOB: 19

PC Time&Date: 09.10.2008 09:40:20 +02:00

NE Time&Date: 01.01.1990 00:02:29 +00:00.

USER NAME: NSN_Paul

COMMAND: Lock ETHCON:NAME=RACK:0/ETHCON:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08




Operation Failed

None.


Example of Command Execution:Lock ETHCON:NAME=RACK:0/ETHCON:0;

SET ETHCON

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h SET ETHCON”



Command Description:This command sets the attributes of ETHCON board to the BTSE data base.


MONPRT monitoringPort


SET ETHCON NAME=RACK:0..7/ETHCON:0..0 [,MONPRT=];

DN0933412 Issue 01361


ETHCON

Id:0900d805805b1091


JOB: 26.

PC Time&Date: 09.10.2008 09:40:57 +02:00

NE Time&Date: 01.01.1990 00:03:06 +00:00

USER NAME: NSN_Paul

COMMAND: Set ETHCON:NAME=RACK:0/ETHCON:0,MONPRT=coba;

SW RELEASE: 03-04-19-06-11-06_08-10-08


monitoringPort = coba


Operation Failed

None.


Example of Command Execution:Set ETHCON:NAME=RACK:0/ETHCON:0,MONPRT=none;

UNLOCK ETHCON

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h UNLOCK ETHCON”



Command Description:This command changes the administrative state of the ETHCON board.




JOB: 21

PC Time&Date: 09.10.2008 09:40:25 +02:00

NE Time&Date: 01.01.1990 00:02:34 +00:00

USER NAME: NSN_Paul

UNLOCK ETHCON NAME=RACK:0..7/ETHCON:0..0;

362DN0933412 Issue 01


Id:0900d805805b1091

ETHCON

COMMAND: Unlock ETHCON:NAME=RACK:0/ETHCON:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08




Operation Failed

None.


Example of Command Execution:Unlock ETHCON:NAME=RACK:0/ETHCON:0;

DN0933412 Issue 01363


ETHPORT

Id:0900d805805b1093

ETHPORTThe ETHPORT object is introduced to indicate the state of the Ethernet port and to allow the configuration of port specific attributes. There is no ETHPORT instance for Ethernet ports which are not externally visible (connection to COBA) nor used for monitoring.

The Ethernet port supports full duplex mode.

CREATE ETHPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h CREATE ETHPORT”



Command Description:This command adds the ETHPORT to the BTSE data base.


EAUTONEG enableAutoNegotiation

EFLWCTRL enableFlowControl

PUSG portUsage



JOB: 39

PC Time&Date: 08.02.2008 13:20:45 +01:00

NE Time&Date: 01.01.1990 00:47:41 +00:00

USER NAME: NSN

COMMAND: Create ETHPORT:NAME=ETHPORT:0;

SW RELEASE: 01-04-19-01-01-CR_08-02-08.



Operation Failed

None.

CREATE ETHPORT NAME=ETHPORT:0..3 [,EAUTONEG=] [,EFLWCTRL=] ,PUSG=;

364DN0933412 Issue 01


Id:0900d805805b1093

ETHPORT


• Default values apply for the typical Abis Ethernet configuration • An ETHPORT object can be only created if the ETHCON object has been created

before. Physical ports of the Ethernet switch without related ETHPORT object (except for the monitoring port(s)) are blocked

Example of Command Execution:Create ETHPORT:NAME=ETHPORT:0,EAUTONEG=TRUE,EFLWC-TRL=FALSE,PUSG=null;

DELETE ETHPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h DELETE ETHPORT”



Command Description:This command deletes the ETHPORT from the BTSE data base.



A further message indicates the result of the operation. An example of delete command is the following:

JOB: 39

PC Time&Date: 30.05.2008 11:00:01 +02:00

NE Time&Date: 01.01.1990 00:04:34 +00:00?

USER NAME: NSN ?

COMMAND: Delete ETHPORT:NAME=ETHPORT:0;?

SW RELEASE: 01-04-19-01-01-ZS_08-05-29?

COMMAND RESULT:Operation successful?

END OF OUTPUT FOR JOB 39?

Operation Failed

None.


DELETE ETHPORT NAME=ETHPORT:0..3;

DN0933412 Issue 01365


ETHPORT

Id:0900d805805b1093

Example of Command Execution:Delete ETHPORT:NAME=ETHPORT:0;

GET ETHPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h GET ETHPORT”



Command Description:This command displays the attributes of the ETHPORT.



ALS alarmStatus








MTYP mediaType

PSTAT portStatus

PUSG portUsage

SFPSERID sfpSerialId



JOB: 58

PC Time&Date: 09.10.2008 09:43:52 +02:00

NE Time&Date: 01.01.1990 00:06:01 +00:00

USER NAME: NSN

GET ETHPORT NAME=ETHPORT:0..3 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, EAUTONEG, EFLWCTRL, MTYP, PSTAT, PUSG, SFPSERID];

366DN0933412 Issue 01


Id:0900d805805b1093

ETHPORT

COMMAND: Get ETHPORT:NAME=ETHPORT:0;

SW RELEASE: 03-04-19-06-11-06_08-10-08








enableAutoNegotiation = TRUE

enableFlowControl = FALSE

mediaType = electrical

portStatus =

speed = speed100M

duplexMode = enabled

flowControl = disabled

portUsage = bscLink

sfpSerialId = Null


Operation Failed

None.


Example of Command Execution:Get ETHPORT:NAME=ETHPORT:0,REQATTL=ALS&AST&AVS&OST&PRS&REL-FUNCOBJ&EAUTONEG&EFLWCTRL&MTYP&PSTAT&PUSG&SPFSERID;

LOCK ETHPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h LOCK ETHPORT”



Command Description:This command changes the administrative state of ETHPORT.

LOCK ETHPORT NAME=ETHPORT:0..3;

DN0933412 Issue 01367


ETHPORT

Id:0900d805805b1093




JOB: 49

PC Time&Date: 27.08.2008 14:16:31 +02:00

NE Time&Date: 27.08.2008 14:05:17 +01:00

USER NAME: NSN

COMMAND: Lock ETHPORT:NAME=ETHPORT:0;

SW RELEASE: 01-04-19-01-11-ZT_08-08-23




Operation Failed

None.


Example of Command Execution:Lock ETHPORT:NAME=ETHPORT:0;

SET ETHPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h SET ETHPORT”



Command Description:This command sets the attributes of ETHPORT to the BTSE data base.




PUSG portUsage

SET ETHPORT NAME=ETHPORT:0..3 [,EAUTONEG=] [,EFLWCTRL=] [,PUSG=];

368DN0933412 Issue 01


Id:0900d805805b1093

ETHPORT



JOB: 59

PC Time&Date: 09.10.2008 09:44:20 +02:00

NE Time&Date: 01.01.1990 00:06:29 +00:00

USER NAME: NSN

COMMAND: Set ETHPORT:NAME=ETHPORT:0,EAUTONEG=TRUE,EFLWC-TRL=FALSE,PUSG=bscLink;

SW RELEASE: 03-04-19-06-11-06_08-10-08

COMMAND RESULT: Operation failed

enableAutoNegotiation = TRUE

enableFlowControl = FALSE

portUsage = bscLink

MO or MOT not locked (-151)


Operation Failed

None.


Example of Command Execution:Set ETHPORT:NAME=ETHPORT:0,EAUTONEG=TRUE,EFLWC-TRL=FALSE,PUSG=null;

UNLOCK ETHPORT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h UNLOCK ETHPORT”



Command Description:This command changes the administrative state of ETHPORT.


UNLOCK ETHPORT NAME=ETHPORT:0..3;

DN0933412 Issue 01369


ETHPORT

Id:0900d805805b1093



JOB: 52

PC Time&Date: 27.08.2008 14:16:56 +02:00

NE Time&Date: 27.08.2008 14:05:42 +01:00

USER NAME: NSN

COMMAND: Unlock ETHPORT:NAME=ETHPORT:0;

SW RELEASE: 01-04-19-01-11-ZT_08-08-23

COMMAND RESULT:Operation successf



Operation Failed

None.


Example of Command Execution:Unlock ETHPORT:NAME=ETHPORT:0;

370DN0933412 Issue 01


Id:0900d805805b1095

F6DCTMA

F6DCTMAThis object represents the TMA power supply of one antenna port. The functionality of the object is identical to the DUDCTMA object of an MFDUAMCO.

CREATE F6DCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h CREATE F6DCTMA”



Command Description:This command adds the F6DCTMA to the BTSE data base.



After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation.

JOB: 288

PC Time&Date: 17.10.2008 09:24:24 +02:00

NE Time&Date: 01.01.1990 19:05:33 +00:00

USER NAME: NSN

COMMAND: Create F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16



Operation Failed

The specified object has not been created. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:

JOB: 34

PC Time&Date: 25.09.2008 14:46:58 +02:00

NE Time&Date: 02.01.1990 00:03:39 +00:00

USER NAME: NSN

COMMAND: Create F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24

CREATE F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3;

DN0933412 Issue 01371


F6DCTMA

Id:0900d805805b1095

COMMAND RESULT:Operation failed

Creation out of sequence (-162)


None.


Example of Command Execution:Create F6DCTMA:NAME=RACK:0/F6DCTMA:0;

DELETE F6DCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h DELETE F6DCTMA”



Command Description:This command deletes the F6DCTMA to the BTSE data base.




JOB: 59

PC Time&Date: 17.10.2008 09:05:13 +02:00

NE Time&Date: 01.01.1990 18:46:22 +00:00

USER NAME: NSN

COMMAND: Delete F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16



Operation Failed

The specified Object has not been deleted. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:

DELETE F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3;

372DN0933412 Issue 01


Id:0900d805805b1095

F6DCTMA

JOB: 137

PC Time&Date: 24.09.2008 15:06:31 +02:00

NE Time&Date: 01.01.1990 00:23:14 +00:00

USER NAME: NSN

COMMAND: Delete F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24





Example of Command Execution:Delete F6DCTMA:NAME=RACK:0/F6DCTMA:0;

GET F6DCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h GET F6DCTMA”



Command Description:This command displays the attributes of F6DCTMA.



ALS alarmStatus








GET F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ];

DN0933412 Issue 01373


F6DCTMA

Id:0900d805805b1095

JOB: 140

PC Time&Date: 16.09.2008 15:59:02 +02:00

NE Time&Date: 01.01.1990 00:19:44 +00:00

USER NAME: NSN

COMMAND: Get F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-12-MB_08-09-16









Operation Failed

None.


Example of Command Execution:Get F6DCTMA:NAME=RACK:0/F6DCTMA:0, REQATTL=ALS&AST&AVS&OST&PRS&&RELFUNCOBJ;

GETTEST F6DCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h GETTEST F6DCTMA”







GETTEST F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3;

374DN0933412 Issue 01


Id:0900d805805b1095

F6DCTMA

A message indicates the result of the operation.

JOB: 173

PC Time&Date: 28.10.2008 16:31:01 +01:00

NE Time&Date: 01.01.1990 00:21:30 +00:00

USER NAME: NSN

COMMAND: Gettest F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-11-08_08-10-17



Operation Failed

The specified action cannot be performed. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:

JOB: 48

PC Time&Date: 17.10.2008 09:04:29 +02:00

NE Time&Date: 01.01.1990 18:45:38 +00:00

USER NAME: NSN

COMMAND: Gettest F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16


MOT = RACK:0/F6DCTMA:0

Object instance unknown or not allowed (-9)



Example of Command Execution:Gettest F6DCTMA:NAME=RACK:0/F6DCTMA:0;?

LOCK F6DCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h LOCK F6DCTMA”



Command Description:This command changes the administrative state of F6DCTMA.

LOCK F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3;

DN0933412 Issue 01375


F6DCTMA

Id:0900d805805b1095




JOB: 40

PC Time&Date: 17.10.2008 09:04:19 +02:00

NE Time&Date: 01.01.1990 18:45:28 +00:00

USER NAME: NSN

COMMAND: Lock F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16




Operation Failed

None.


Example of Command Execution:Perftest F6DCTMA:NAME=RACK:0/F6DCTMA:0;

PERFTEST F6DCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h PERFTEST F6DCTMA”






Test configuration has been set and the specified test has been started. An example is the following:

PERFTEST F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3;

376DN0933412 Issue 01


Id:0900d805805b1095

F6DCTMA

JOB: 43

PC Time&Date: 17.10.2008 09:04:27 +02:00

NE Time&Date: 01.01.1990 18:45:36 +00:00

USER NAME: NSN

COMMAND: Perftest F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16



tO = BTSETEST:1

END OF OUTPUT FOR JOB 43Operation Failed

The specified test cannot be performed. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:

JOB: 140

PC Time&Date: 24.09.2008 15:06:41 +02:00

NE Time&Date: 01.01.1990 00:23:24 +00:00

USER NAME: NSN

COMMAND: Perftest F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24



Physical configuration cannot be performed (-30)



Example of Command Execution:Perftest F6DCTMA:NAME=RACK:0/F6DCTMA:0;

STOPTEST F6DCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h STOPTEST F6DCTMA”




STOPTEST F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3;

DN0933412 Issue 01377


F6DCTMA

Id:0900d805805b1095



Test has been stopped. The System Responses will not be addressed to the MOT but to the object.STOPTEST F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3;Result TEST:

name = TEST:<n>



testTermination = CancelexecutedPhases

phaseId = It represents the list of the executed test phases; the list is not shown for test in the waiting list (queued)

failedPhases

phaseId = It represents the list of the failed test phase

phaseId = additional information is provided for each phase....

skippedPhases

phaseId = It represents the list of the skipped phases; the list is not shown for test in the waiting list (queued).

phaseId

Operation Failed

The specified test cannot be stopped. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical config-uration, is possible. An example is the following:

JOB: 55

PC Time&Date: 17.10.2008 09:04:59 +02:00

NE Time&Date: 01.01.1990 18:46:08 +00:00

USER NAME: NSN

COMMAND: Stoptest F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16






Example of Command Execution:Stoptest F6DCTMA:NAME=RACK:0/F6DCTMA:0;

378DN0933412 Issue 01


Id:0900d805805b1095

F6DCTMA

UNLOCK F6DCTMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h UNLOCK F6DCTMA”



Command Description:This command changes the administrative state of F6DCTMA object.




JOB: 56

PC Time&Date: 17.10.2008 09:05:06 +02:00

NE Time&Date: 01.01.1990 18:46:15 +00:00

USER NAME: NSN

COMMAND: Unlock F6DCTMA:NAME=RACK:0/F6DCTMA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16




Operation Failed

None.


Example of Command Execution:Unlock F6DCTMA:NAME=RACK:0/F6DCTMA:0;

UNLOCK F6DCTMA NAME=RACK:0..7/F6DCTMA:0..3;

DN0933412 Issue 01379


F6LNA

Id:0900d805805b1099

F6LNAThe F6LNA object integrates the HW functionality of both DILNA and DULNA objects.

CREATE F6LNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h CREATE F6LNA”



Command Description:This command adds the F6LNA to the BTSE data base.


CELLNO cellNumber


GNADB gainAdjustDb


WDLNA wiringDataLna

LNAMDB lnaModeDb



JOB: 71

PC Time&Date: 26.09.2008 13:12:42 +02:00

NE Time&Date: 26.09.2008 10:20:00 +01:00

USER NAME: NSN

COMMAND: Create

F6LNA:NAME=RACK:0/F6LNA:1,CELLNO=1,WDLNA=FCUMAIN1N;

SW RELEASE: 03-04-19-01-11-05_08-09-24


cellNumber = 1

wiringDataLna = FCUMAIN1N


CREATE F6LNA NAME=RACK:0..7/F6LNA:0..3 ,CELLNO= [,SCELLNO=] [,GNADB=] [,LNAPRED=] ,WDLNA= [,LNAMDB=];

380DN0933412 Issue 01


Id:0900d805805b1099

F6LNA

Operation Failed


JOB: 9

PC Time&Date: 25.09.2008 14:46:05 +02:00

NE Time&Date: 02.01.1990 00:02:46 +00:00

USER NAME: NSN

COMMAND: Create

F6LNA:NAME=RACK:0/F6LNA:1,CELLNO=0,GNADB=N_00,LNAPRED=TMA(RACK

0-TMA1),WDLNA=CU0D;

SW RELEASE: 03-04-19-01-11-05_08-09-24


cellNumber = 0

gainAdjustDb = N_00

lnaPredecessor =

predType =

TMA

predRack = RACK0

predNo = TMA1

wiringDataLna = CU0D



Application Guidelines:F6LNA creation attempts with more than 6 wiring paths specified in “wiringDataLna” attribute are rejected by BTS SW.

Example of Command Execution:Create F6LNA:NAME=RACK:0/F6LNA:1,CELLNO=1,WDLNA=FCUMAIN1N.

DELETE F6LNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h DELETE F6LNA”



DELETE F6LNA NAME=RACK:0..7/F6LNA:0..3;

DN0933412 Issue 01381


F6LNA

Id:0900d805805b1099

Command Description:This command deletes the F6LNA to the BTSE data base.




JOB: 29

PC Time&Date: 25.09.2008 14:46:53 +02:00

NE Time&Date: 02.01.1990 00:03:34 +00:00

USER NAME: NSN

COMMAND: Delete F6LNA:NAME=RACK:0/F6LNA:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24



Operation Failed

None.


Example of Command Execution:Delete F6LNA:NAME=RACK:0/F6LNA:0;

GET F6LNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h GET F6LNA”



Command Description:This command displays the attributes of F6LNA object.

GET F6LNA NAME=RACK:0..7/F6LNA:0..3 [,REQATTL=ALS, AST, OST, PRS, AVS, CELLNO, SCELLNO, GNA, GNADB, LNAPRED, WDLNA, LNAMDB, LNAMODE, RELFUN-COBJ];

382DN0933412 Issue 01


Id:0900d805805b1099

F6LNA



ALS alarmStatus





CELLNO cellNumber


GNA gainAdjust(dB)

GNADB gainAdjustDb


WDLNA wiringDataLna

LNAMDB lnaModeDb

LNAMODE lnaMode




JOB: 60

PC Time&Date: 17.10.2008 09:05:21 +02:00

NE Time&Date: 01.01.1990 18:46:30 +00:00

USER NAME: NSN

COMMAND: Get F6LNA:NAME=RACK:0/F6LNA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16







cellNumber = 0


gainAdjust(dB) = N_00

gainAdjustDb = DIP


wiringDataLna = CU0N & CU1N & CU2N & CU3N

DN0933412 Issue 01383


F6LNA

Id:0900d805805b1099

lnaModeDb = DIP.

lnaMode = AMCO_MODE



Operation Failed

None.


Example of Command Execution:Get F6LNA:NAME=RACK:0/F6LNA:0;REQATTL= ALS& AST& OST& PRS& AVS&CELLNO& SCELLNO& GNA& GNADB&LNAPRED& WDLNA& LNAMDB& NAMODE& RELFUNCOBJ;

GETTEST F6LNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h GETTEST F6LNA”








JOB: 273

PC Time&Date: 17.10.2008 09:21:19 +02:00

NE Time&Date: 01.01.1990 19:02:28 +00:00

USER NAME: NSN

COMMAND: Gettest F6LNA:NAME=RACK:0/F6LNA:1;.

SW RELEASE: 01-04-19-01-11-07_08-10-16



GETTEST F6LNA NAME=RACK:0..7/F6LNA:0..3;

384DN0933412 Issue 01


Id:0900d805805b1099

F6LNA

Operation Failed

The GETTEST command has not been successfully executed. A general NACK will indicate possible errors or a specific NACK strictly related to the single command is pos-sible. An example of specific NACK is the following:

JOB: 69

PC Time&Date: 17.10.2008 09:05:40 +02:00

NE Time&Date: 01.01.1990 18:46:49 +00:00

USER NAME: NSN

COMMAND: Gettest F6LNA:NAME=RACK:0/F6LNA:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16


MOT = RACK:0/F6LNA:0


END OF OUTPUT FOR JOB 69e.


Example of Command Execution:Gettest F6LNA:NAME=RACK:0/F6LNA:0;?

LOCK F6LNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h LOCK F6LNA”



Command Description:This command changes the administrative state of F6LNA.



After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of lock command is the following:

JOB: 113

PC Time&Date: 28.10.2008 16:26:55 +01:00

LOCK F6LNA NAME=RACK:0..7/F6LNA:0..3;

DN0933412 Issue 01385


F6LNA

Id:0900d805805b1099

NE Time&Date: 01.01.1990 00:17:24 +00:00

USER NAME: NSN

COMMAND: Lock F6LNA:NAME=RACK:0/F6LNA:0;

SW RELEASE: 01-04-19-01-11-08_08-10-17




Operation Failed

None.


Example of Command Execution:Lock F6LNA:NAME=RACK:0/F6DCTMA:0;

PERFTEST F6LNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h PERFTEST F6LNA”






After command execution, a message of Changed Configuration Notification is dis-played.? A further message indicates the result of the operation. An example of perftest? command is the following:

JOB: 13?

PC Time&Date: 26.09.2008 13:05:27 +02:00?

NE Time&Date: 26.09.2008 10:12:45 +01:00?

USER NAME: NSN ?

COMMAND: Perftest F6LNA:NAME=RACK:0/F6LNA:0;?

SW RELEASE: 03-04-19-01-11-05_08-09-24?

COMMAND RESULT:Operation successful?

PERFTEST F6LNA NAME=RACK:0..7/F6LNA:0..3;

386DN0933412 Issue 01


Id:0900d805805b1099

F6LNA

MOT = RACK:0/F6LNA:0?

tO = BTSETEST:7?

END OF OUTPUT FOR JOB 13?.

Operation Failed

The specified test cannot be performed. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:

JOB: 145

PC Time&Date: 16.09.2008 16:01:13 +02:00

NE Time&Date: 01.01.1990 00:21:55 +00:00

USER NAME: NSN

COMMAND: Perftest F6LNA:NAME=RACK:0/F6LNA:0;

SW RELEASE: 01-04-19-01-12-MB_08-09-16






Example of Command Execution:Perftest F6LNA:NAME=RACK:0/F6DCTMA:0;

SET F6LNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h SET F6LNA”



Command Description:This command sets the attributes F6LNA obejct.



GNADB gainAdjustDb

WDLNA wiringDataLna

SET F6LNA NAME=RACK:0..7/F6LNA:0..3 [,SCELLNO=] [,GNADB=] [,WDLNA=] [,LNAMDB=];

DN0933412 Issue 01387


F6LNA

Id:0900d805805b1099

LNAMDB lnaModeDb



JOB: 219.

PC Time&Date: 24.09.2008 14:37:37 +02:00

NE Time&Date: 24.09.2008 10:46:11 +00:00

USER NAME: NSN

COMMAND: Set F6LNA:NAME=RACK:0/F6LNA:0,GNADB=N_00;

SW RELEASE: 03-04-19-01-11-05_08-09-24


gainAdjustDb = N_00


Operation Failed

The specified object has not been set. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible.


Example of Command Execution:Set F6LNA:NAME=RACK:0/F6LNA:0,GNADB=N_00;

STOPTEST F6LNA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h STOPTEST F6LNA”






STOPTEST F6LNA NAME=RACK:0..7/F6LNA:0..3;

388DN0933412 Issue 01


Id:0900d805805b1099

F6LNA

Test has been stopped. The System Responses will not be addressed to the MOT but to the object. An example of stoptest command is the following:

STOPTEST F6LNA NAME=RACK:0..7/F6LNA:0..3;

Result TEST:

name = TEST:<n>




executedPhases

phaseId = It represents the list of the executed test phases; the... list is not shown for test in the waiting list (queued)..failedPhases


phaseId = additional information is provided for each phase..

skippedPhases

phaseId = It represents the list of the skipped phases;the list is

phaseId = not shown for test in the waiting list (queued).

Operation Failed

The specified test cannot be stopped. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical config-uration, is possible. An example is the following:

JOB: 274

PC Time&Date: 17.10.2008 09:21:25 +02:00

NE Time&Date: 01.01.1990 19:02:34 +00:00

USER NAME: NSN

COMMAND: Stoptest F6LNA:NAME=RACK:0/F6LNA:1;

SW RELEASE: 01-04-19-01-11-07_08-10-16






Example of Command Execution:Stoptest F6LNA:NAME=RACK:0/F6DCTMA:0;

UNLOCK F6LNAUNLOCK F6LNA NAME=RACK:0..7/F6LNA:0..3;

DN0933412 Issue 01389


F6LNA

Id:0900d805805b1099

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h UNLOCK F6LNA”



Command Description:This command changes the administrative state of F6LNA object.



After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of unlock command is the following:

JOB: 18

PC Time&Date: 26.09.2008 13:06:03 +02:00

NE Time&Date: 26.09.2008 10:13:21 +01:00

USER NAME: NSN

COMMAND: Unlock F6LNA:NAME=RACK:0/F6LNA:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24


administrativeState = Unlocked.

Operation Failed

None.


Example of Command Execution:Unlock F6LNA:NAME=RACK:0/F6DCTMA:0;

390DN0933412 Issue 01


Id:0900d805805b1029

F6TNFP

F6TNFPThis object provides the functionality to configure and supervise the turnable narrow-band filter of one TX path.

CREATE F6TNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h CREATE F6TNFP”



Command Description:This command adds the F6TNFP to the BTSE data base.


WDFTNFP wiringDataFtnfp



JOB: 201

PC Time&Date: 17.10.2008 09:13:37 +02:00

NE Time&Date: 01.01.1990 18:54:46 +00:00

USER NAME: NSN

COMMAND: Create F6TNFP:NAME=RACK:0/F6TNFP:0,WDFTNFP=CU0-FVSWRP0;

SW RELEASE: 01-04-19-01-11-07_08-10-16


wiringDataFtnfp =

CUWiring = CU0

FVSWRPWiring = FVSWRP0.


Operation Failed

The specified Object has not been created. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible.

CREATE F6TNFP NAME=RACK:0..7/F6TNFP:0..11 ,WDFTNFP=;

DN0933412 Issue 01391


F6TNFP

Id:0900d805805b1029


Example of Command Execution:Create F6TNFP:NAME=RACK:0/F6TNFP:0,WDFTNFP=CU0-FVSWRP0;

DELETE F6TNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h DELETE F6TNFP”



Command Description:This command deletes the F6TNFP from the BTSE data base.



After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of delete-command is the following:

JOB: 90

PC Time&Date: 17.10.2008 09:07:57 +02:00

NE Time&Date: 01.01.1990 18:49:06 +00:00

USER NAME: NSN

COMMAND: Delete F6TNFP:NAME=RACK:0/F6TNFP:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16



Operation Failed

None.


Example of Command Execution:Delete F6TNFP:NAME=RACK:0/F6TNFP:0;

DELETE F6TNFP NAME=RACK:0..7/F6TNFP:0..11;

392DN0933412 Issue 01


Id:0900d805805b1029

F6TNFP

GET F6TNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h GET F6TNFP”



Command Description:This command displays the attributes of F6TNFP object.



ALS alarmStatus






TNFTARGF tnfTargetFrequency




JOB: 88

PC Time&Date: 17.10.2008 09:07:54 +02:00

NE Time&Date: 01.01.1990 18:49:03 +00:00

USER NAME: NSN

COMMAND: Get F6TNFP:NAME=RACK:0/F6TNFP:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16




availabilityStatus = Dependency



GET F6TNFP NAME=RACK:0..7/F6TNFP:0..11 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, TNFTARGF, WDFTNFP];

DN0933412 Issue 01393


F6TNFP

Id:0900d805805b1029


tnfTargetFrequency = Null

CUWiring = CU0

FVSWRPWiring = FVSWRP0


Operation Failed

None.


Example of Command Execution:Get F6TNFP:NAME=RACK:0/F6TNFP:0;

GETTEST F6TNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h GETTEST F6TNFP”








JOB: 90

PC Time&Date: 29.10.2008 16:24:05 +01:00

NE Time&Date: 01.01.1990 00:14:34 +00:00

USER NAME: NSN

COMMAND: Gettest F6TNFP:NAME=RACK:0/F6TNFP:0;

SW RELEASE: 01-04-19-01-11-08_08-10-17



GETTEST F6TNFP NAME=RACK:0..7/F6TNFP:0..11;

394DN0933412 Issue 01


Id:0900d805805b1029

F6TNFP

Operation Failed

The gettest command has not been successfully executed. A general NACK will indicate possible errors or a specific NACK strictly related to the single command is possible. An example is the following:

JOB: 85

PC Time&Date: 28.10.2008 16:24:05 +01:00

NE Time&Date: 01.01.1990 00:14:34 +00:00

USER NAME: NSN

COMMAND: Gettest F6TNFP:NAME=RACK:0/F6TNFP:0;

SW RELEASE: 01-04-19-01-11-08_08-10-17


MOT = RACK:0/F6TNFP:0



Operation Failed

None.


Example of Command Execution:Gettest F6TNFP:NAME=RACK:0/F6TNFP:0;

LOCK F6TNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h LOCK F6TNFP”



Command Description:This command changes the administrative state of F6TNFP.




JOB: 153

PC Time&Date: 24.09.2008 15:14:50 +02:00

LOCK F6TNFP NAME=RACK:0..7/F6TNFP:0..11;

DN0933412 Issue 01395


F6TNFP

Id:0900d805805b1029

NE Time&Date: 01.01.1990 00:31:33 +00:00

USER NAME: NSN

COMMAND: Lock F6TNFP:NAME=RACK:0/F6TNFP:1;

SW RELEASE: 03-04-19-01-11-05_08-09-24




Operation Failed

None.


Example of Command Execution:Lock F6TNFP:NAME=RACK:0/F6TNFP:1;

PERFTEST F6TNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h PERFTEST F6TNFP”






Test configuration has been set and the specified test has been started.

JOB: 23

PC Time&Date: 26.09.2008 13:06:13 +02:00

NE Time&Date: 26.09.2008 10:13:31 +01:00

USER NAME: NSN

COMMAND: Perftest F6TNFP:NAME=RACK:0/F6TNFP:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24



PERFTEST F6TNFP NAME=RACK:0..7/F6TNFP:0..11;

396DN0933412 Issue 01


Id:0900d805805b1029

F6TNFP

tO = BTSETEST:8


Operation FailedThe specified test cannot be performed. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsis-tent with the physical configuration, is possible.


Example of Command Execution:Perftest F6TNFP:NAME=RACK:0/F6DCTMA:0;

STOPTEST F6TNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h STOPTEST F6TNFP”






Test has been stopped. The System Responses are not be addressed to the MOT but to the object.

Operation Failed

The specified test has not been stopped. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:

JOB: 214

PC Time&Date: 17.10.2008 09:14:33 +02:00

NE Time&Date: 01.01.1990 18:55:42 +00:00

USER NAME: NSN

COMMAND: Stoptest F6TNFP:NAME=RACK:0/F6TNFP:0;

SW RELEASE: 01-04-19-01-11-07_08-10-16



STOPTEST F6TNFP NAME=RACK:0..7/F6TNFP:0..11;

DN0933412 Issue 01397


F6TNFP

Id:0900d805805b1029




Example of Command Execution:Stoptest F6TNFP:NAME=RACK:0/F6DCTMA:0;

UNLOCK F6TNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h UNLOCK F6TNFP”







JOB: 93

PC Time&Date: 24.09.2008 14:21:38 +02:00

NE Time&Date: 24.09.2008 10:30:12 +00:00

USER NAME: NSN

COMMAND: Unlock F6TNFP:NAME=RACK:0/F6TNFP:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24




Operation Failed

None.


Example of Command Execution:Unlock F6TNFP:NAME=RACK:0/F6DCTMA:0;

UNLOCK F6TNFP NAME=RACK:0..7/F6TNFP:0..11;

398DN0933412 Issue 01


Id:0900d805805b102b

F6VSWRP

F6VSWRPThe F6VSWRP object models the common functions of one FICOM6. Its creation is therefore mandatory if the module is equipped.

CREATE F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h CREATE F6VSWRP”



Command Description:This command adds the F6VSWRP object to the BTSE data base.


CELLNO cellNumber




JOB: 36

PC Time&Date: 25.09.2008 14:47:06 +02:00

NE Time&Date: 02.01.1990 00:03:47 +00:00

USER NAME: NSN

COMMAND: Create

F6VSWRP:NAME=RACK:0/F6VSWRP:0,CELLNO=0,VSWRTDB=LOW_2_5_HIGH_3_5;

SW RELEASE: 03-04-19-01-11-05_08-09-24


cellnumber = 0

vswrThresholdDb = LOW_2_5_HIGH_3_5


Operation Failed

CREATE F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1 ,CELLNO= [,VSWRTDB=];

DN0933412 Issue 01399


F6VSWRP

Id:0900d805805b102b


JOB: 85

PC Time&Date: 16.09.2008 15:48:10 +02:00

NE Time&Date: 01.01.1990 00:08:52 +00:00

USER NAME: NSN

COMMAND: Create F6VSWRP:NAME=RACK:0/F6VSWRP:0,CELLNO=1;

SW RELEASE: 01-04-19-01-12-MB_08-09-16


cellNumber = 1




• The creation is mandatory if the module is equipped • The creation is rejected if any other combiner instance (DUAMCO,

DUVSWR,DULNA, DUDCTMA, FVSWRP, FTNFP, BCOM) is already created for the relatedACOM slots

• The creation of any other combiner object has to be rejected if a FICOM6 object iscreated for the slot(s)

Example of Command Execution:Create F6VSWRP:NAME=RACK:0/F6VSWRP:0,CELLNO=0,VSWRTDB=LOW_2_5_HIGH_3_5;e.

DELETE F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h DELETE F6VSWRP”



Command Description:This command deletes the F6VSWRP object from the BTSE data base.



DELETE F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1;

400DN0933412 Issue 01


Id:0900d805805b102b

F6VSWRP


JOB: 25

PC Time&Date: 25.09.2008 14:46:50 +02:00

NE Time&Date: 02.01.1990 00:03:31 +00:00

USER NAME: NSN

COMMAND: Delete F6VSWRP:NAME=RACK:0/F6VSWRP:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24



Operation Failed



Example of Command Execution:Delete F6VSWRP:NAME=RACK:0/F6TNFP:0;

GET F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h GET F6VSWRP”



Command Description:This command displays the attributes of F6VSWRP object.



ALS alarmStatus



CELLNO cellNumber

GET F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1 [,REQATTL=ALS, AST, AVS, CELLNO, OST, PRS, RELFUNCOBJ, VSWRTDB, F6FWID];

DN0933412 Issue 01401


F6VSWRP

Id:0900d805805b102b





F6FWID ficom6FwId



JOB: 148

PC Time&Date: 16.09.2008 16:06:01 +02:00

NE Time&Date: 01.01.1990 00:26:43 +00:00

USER NAME: NSN

COMMAND: Get F6VSWRP:NAME=RACK:0/F6VSWRP:0;

SW RELEASE: 01-04-19-01-12-MB_08-09-16





cellNumber = 1





ficom6FwId = "BFFCiihh.SWI:00-hh-19-ii-ss-00_08-01-01"


Operation Failed

None.


Example of Command Execution:Get F6VSWRP:NAME=F6VSWRP:0, REQATTL=ALS& AST& AVS& CELLNO& OST&PRS& RELFUNCOBJ& VSWRTDB& F6FWID;

GETTEST F6VSWRPGETTEST F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1;

402DN0933412 Issue 01


Id:0900d805805b102b

F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h GETTEST F6VSWRP”








JOB: 296

PC Time&Date: 17.09.2008 16:12:51 +02:00

NE Time&Date: 17.09.2008 13:21:24 +01:00

USER NAME: NSN

COMMAND: Gettest F6VSWRP:NAME=RACK:0/F6VSWRP:1;

SW RELEASE: 01-04-19-01-12-MB_08-09-12



Operation Failed

None.


Example of Command Execution:Gettest F6VSWRP:NAME=RACK:0/F6TNFP:0;

LOCK F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h LOCK F6VSWRP”


LOCK F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1;

DN0933412 Issue 01403


F6VSWRP

Id:0900d805805b102b


Command Description:This command changes the administrative state of F6TNFP.




JOB: 228

PC Time&Date: 17.09.2008 16:03:11 +02:00

NE Time&Date: 17.09.2008 13:11:44 +01:00

USER NAME: NSN

COMMAND: Lock F6VSWRP:NAME=RACK:0/F6VSWRP:0;

SW RELEASE: 01-04-19-01-12-MB_08-09-12




Operation Failed

None.


Example of Command Execution:Lock F6VSWRP:NAME=RACK:0/F6TNFP:0;

PERFTEST F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h PERFTEST F6VSWRP”





PERFTEST F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1;

404DN0933412 Issue 01


Id:0900d805805b102b

F6VSWRP


After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of perftest command is the following:

JOB: 35

PC Time&Date: 26.09.2008 13:06:37 +02:00

NE Time&Date: 26.09.2008 10:13:55 +01:00

USER NAME: NSN

COMMAND: Perftest F6VSWRP:NAME=RACK:0/F6VSWRP:0;

SW RELEASE: 03-04-19-01-11-05_08-09-24


MOT = RACK:0/F6VSWRP:0

tO = BTSETEST:9


Operation Failed

The specified test cannot be performed. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible.

Operation Failed

None.


Example of Command Execution:Perftest F6VSWRP:NAME=RACK:0/F6DCTMA:0;

SET F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h SET F6VSWRP”



Command Description:This command sets general attributes of F6VSWRP object.


SET F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1 [,VSWRTDB=];

DN0933412 Issue 01405


F6VSWRP

Id:0900d805805b102b




JOB: 53

PC Time&Date: 24.09.2008 14:13:35 +02:00

NE Time&Date: 24.09.2008 10:22:09 +00:00

USER NAME: NSN

COMMAND: Set

F6VSWRP:NAME=RACK:0/F6VSWRP:0,VSWRTDB=LOW_3_0_HIGH_4_0;

SW RELEASE: 03-04-19-01-11-05_08-09-24




Operation Failed

None.


Example of Command Execution:Set F6VSWRP:NAME=RACK:0/F6VSWRP:0,VSWRTDB=LOW_3_0_HIGH_4_0;

STOPTEST F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h STOPTEST F6VSWRP”






STOPTEST F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1;

406DN0933412 Issue 01


Id:0900d805805b102b

F6VSWRP

The test has been stopped. The System Responses will not be addressed to the MOT but to the object.

Operation Failed

The specified action has not been performed. In addition to the general NACK causes, a specific NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:

JOB: 244

PC Time&Date: 17.09.2008 16:07:01 +02:00

NE Time&Date: 17.09.2008 13:15:34 +01:00

USER NAME: NSN

COMMAND: Stoptest F6VSWRP:NAME=RACK:0/F6VSWRP:1;

SW RELEASE: 01-04-19-01-12-MB_08-09-12


MOT = RACK:0/F6VSWRP:1




Example of Command Execution:Stoptest F6VSWRP:NAME=RACK:0/F6DCTMA:0;

UNLOCK F6VSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h UNLOCK F6VSWRP”







JOB: 227

PC Time&Date: 17.09.2008 16:03:02 +02:00

UNLOCK F6VSWRP NAME=RACK:0..7/F6VSWRP:0..1;

DN0933412 Issue 01407


F6VSWRP

Id:0900d805805b102b

NE Time&Date: 17.09.2008 13:11:35 +01:00

USER NAME: NSN

COMMAND: Unlock F6VSWRP:NAME=RACK:0/F6VSWRP:0;

SW RELEASE: 01-04-19-01-12-MB_08-09-12




Operation Failed

None.


Example of Command Execution:Unlock F6VSWRP:NAME=RACK:0/F6DCTMA:0;

408DN0933412 Issue 01


Id:0900d805805b102d

FANP

FANPThe self controlled central FAN units are used to guarantee a sufficient airflow for con-vection cooling of the modules. Two fans are responsible for each sub-rack. An inte-grated temperature sensor enables the fan control.

CREATE FANP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h CREATE FANP”



Command Description:This command adds the FANP unit to the BTSE data base.




JOB: 147

PC Time&Date: 12:01:41 03/23/2005

NE Time&Date: 13:03:16 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FANP:0



CREATE FANP NAME=RACK:0..7/FANP:0..7;

DN0933412 Issue 01409


FANP

Id:0900d805805b102d

JOB: 148

PC Time&Date: 12:01:41 03/23/2005

NE Time&Date: 13:03:16 09/15/2004

USER NAME: NSN

COMMAND: Create FANP:NAME=RACK:0/FANP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 149

PC Time&Date: 12:02:04 03/23/2005

NE Time&Date: 13:03:39 09/15/2004

USER NAME: NSN

COMMAND: Create FANP:NAME=RACK:0/FANP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• In operation, all FANPs must be created

• The maximum number of FANPs is: 6 for BS240/241/240SR/241SR and BS40/41, 8 for BS240XL/BS240XLSR, 5 for BS40II and 1 for BS82II

• The FANP object is always created with status unlocked.enable.null.null.cleared. If the HW is not connected or not present or if the board has a HW failure the object is then immediatly set to unlocked.disabled.failed

• If the operator creates in advance the object FANP in an extension rack which is not yet connected to the Base rack or if the ACT is not enabled, the FANP always keep

410DN0933412 Issue 01


Id:0900d805805b102d

FANP

the states unlocked.enabled.null.null.cleared and no alarm is visible, even if the FAN-HW is not present or the board has an HW-failure

• In the BS82 II the ACT must also be enabled in the base rack for correct displaying of the FAN status

Example of Command Execution:Create FANP:NAME=RACK:0/FANP:0;

DELETE FANP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h DELETE FANP”



Command Description:This command deletes the FANP unit from the BTSE data base.




JOB: 145

PC Time&Date: 12:01:38 03/23/2005

NE Time&Date: 13:03:13 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FANP:0


DELETE FANP NAME=RACK:0..7/FANP:0..7;

DN0933412 Issue 01411


FANP

Id:0900d805805b102d


JOB: 146

PC Time&Date: 12:01:38 03/23/2005

NE Time&Date: 13:03:13 09/15/2004

USER NAME: NSN

COMMAND: Delete FANP:NAME=RACK:0/FANP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• FANP must be locked in Phase 3, before deletion

• The deletion of a FANP is critical in operation

Example of Command Execution:Delete FANP:NAME=RACK:0/FANP:0;

GET FANP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h GET FANP”



Command Description:This command displays the attributes of the FANP units of the BTSE.



GET FANP NAME=RACK:0..7/FANP:0..7 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ];

412DN0933412 Issue 01


Id:0900d805805b102d

FANP

ALS alarmStatus








JOB: 132

PC Time&Date: 12:01:18 03/23/2005

NE Time&Date: 13:02:53 09/15/2004

USER NAME: NSN

COMMAND: Get FANP:NAME=RACK:0/FANP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23









Operation Failed



• The value for ProcStatus must be Null Status

• The relatedFuncObjects always empty

Example of Command Execution:Get FANP:NAME=RACK:0/FANP:0,REQATTL=ALS&AST&AVS&OST&PRS;

DN0933412 Issue 01413


FANP

Id:0900d805805b102d

GETTEST FANP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h GETTEST FANP”



Command Description:This command displays the attributes of the FANP test.





JOB: 140

PC Time&Date: 12:01:25 03/23/2005

NE Time&Date: 13:03:00 09/15/2004

USER NAME: NSN

COMMAND: Gettest FANP:NAME=RACK:0/FANP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/FANP:0

testMonitor =

phaseId = PreliminaryTestsFanp


phaseId = CheckAlarmStatusFanp


phaseId = EndTestFanp



GETTEST FANP NAME=RACK:0..7/FANP:0..7;

414DN0933412 Issue 01


Id:0900d805805b102d

FANP



Operation Failed



Example of Command Execution:Gettest FANP:NAME=RACK:0/FANP:0;

LOCK FANP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h LOCK FANP”



Command Description:This command changes the administrative state of the FANP unit of the BTSE.



phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK FANP NAME=RACK:0..7/FANP:0..7;

DN0933412 Issue 01415


FANP

Id:0900d805805b102d



JOB: 143

PC Time&Date: 12:01:36 03/23/2005

NE Time&Date: 13:03:11 09/15/2004

USER NAME: NSN

COMMAND: Lock FANP:NAME=RACK:0/FANP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 144

PC Time&Date: 12:01:36 03/23/2005

NE Time&Date: 13:03:11 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/FANP:0




Operation Failed


416DN0933412 Issue 01


Id:0900d805805b102d

FANP


• After locking of the FANP, the FANP will still be in operation, but in the administrative state Locked.

Example of Command Execution:Lock FANP:NAME=RACK:0/FANP:0;

PERFTEST FANP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h PERFTEST FANP”



Command Description:This command is used to start an asynchronous test in FANP.




JOB: 136

PC Time&Date: 12:01:25 03/23/2005

NE Time&Date: 13:03:00 09/15/2004

USER NAME: NSN

COMMAND: Perftest FANP:NAME=RACK:0/FANP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/FANP:0

tO = BTSETEST:6


PERFTEST FANP NAME=RACK:0..7/FANP:0..7;

DN0933412 Issue 01417


FANP

Id:0900d805805b102d

JOB: 137

PC Time&Date: 12:01:25 03/23/2005

NE Time&Date: 13:03:00 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:6



JOB: 138

PC Time&Date: 12:01:25 03/23/2005

NE Time&Date: 13:03:00 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23








JOB: 139

PC Time&Date: 12:01:25 03/23/2005

418DN0933412 Issue 01


Id:0900d805805b102d

FANP

NE Time&Date: 13:03:00 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:6



MOT = RACK:0/FANP:0

executedPhases =

PreliminaryTestsFanp

CheckAlarmStatusFanp

EndTestFanp


JOB: 140

PC Time&Date: 12:01:25 03/23/2005

NE Time&Date: 13:03:00 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:6




Result TEST:

name = TEST:<n>

DN0933412 Issue 01419


FANP

Id:0900d805805b102d

Operation Failed




Example of Command Execution:Perftest FANP:NAME=RACK:0/FANP:0;










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



420DN0933412 Issue 01


Id:0900d805805b102d

FANP

STOPTEST FANP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h STOPTEST FANP”







Operation Failed


STOPTEST FANP NAME=RACK:0..7/FANP:0..7;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


DN0933412 Issue 01421


FANP

Id:0900d805805b102d


Example of Command Execution:Stoptest FANP:NAME=RACK:0/FANP:0;

UNLOCK FANP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h UNLOCK FANP”



Command Description:This command changes the administrative state of the FANP unit of the BTSE.




JOB: 141

PC Time&Date: 12:01:28 03/23/2005

NE Time&Date: 13:03:03 09/15/2004

USER NAME: NSN

COMMAND: Unlock FANP:NAME=RACK:0/FANP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





UNLOCK FANP NAME=RACK:0..7/FANP:0..7;

422DN0933412 Issue 01


Id:0900d805805b102d

FANP


JOB: 142

PC Time&Date: 12:01:28 03/23/2005

NE Time&Date: 13:03:03 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



• After locking of the FANP, the FANP will still be in operation, but in the administrative state Locked

Example of Command Execution:Unlock FANP:NAME=RACK:0/FANP:0;

DN0933412 Issue 01423


FCUMAIN

Id:0900d805805b102f

FCUMAINThe FlexCU board is modeled with three HMO instances: 1 instance of the FCUMAIN HMO and 2 instances of the FCUTR HMO. The FCUMAIN instance represents that part of the board which performs board related activities and the FCUTR instances represent carrier (TRX) specific activities. There is a dependency of the FCUTR instances towards the FCUMAIN instance of a FlexCU.

CREATE FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h CREATE FCUMAIN”



Command Description:This command adds the FCUMAIN unit to the BTSE data base.


FCUMODE fcuMode


RXLEVADJN1D1 rxLevAdjustN1D1(dB)

TCC txCoherentComb



JOB: 56

PC Time&Date: 16:34:31 03/23/2005

NE Time&Date: 16:32:25 09/15/2004

USER NAME: NSN

COMMAND: Create FCUMAIN:NAME=RACK:0/FCUMAIN:0,FCUMODE=single-CUMode,RXLEVADJ=1-1,RXLEVADJN1D1=1-1;

SW RELEASE: 01-04-17-01-26-51_05-02-23

CREATE FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11 [,FCUMODE=] [,RXLE-VADJ=] [,RXLEVADJN1D1=] [,TCC=];

424DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN



name = RACK:0/FCUMAIN:0


M


JOB: 57

PC Time&Date: 16:34:31 03/23/2005

NE Time&Date: 16:32:25 09/15/2004

USER NAME: NSN

COMMAND: Create FCUMAIN:NAME=RACK:0/FCUMAIN:0,FCUMODE=singleCU-Mode,RXLEVADJ=1-1,RXLEVADJN1D1=1-1;

SW RELEASE: 01-04-17-01-26-51_05-02-23


fcuMode = singleCUMode

rxLevAdjust(dB) =

adjustValue = 1.0


rxLevAdjustN1D1(dB) =

adjustValueN1 = 1.0

adjustDivValueD1 = 1.0


Operation Failed


JOB: 76

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

DN0933412 Issue 01425


FCUMAIN

Id:0900d805805b102f

USER NAME: NSN

COMMAND: Create FCUMAIN:NAME=RACK:0/FCUMAIN:0,FCUMODE=single-CUMode,RXLEVADJ=1-1,RXLEVADJN1D1=1-1;

SW RELEASE: 01-04-17-01-26-51_05-02-23


fcuMode = singleCUMode

rxLevAdjust(dB) =

adjustValue = 1.0



adjustValueN1 = 1.0





Example of Command Execution:Create FCUMAIN: NAME=RACK:0/FCUMAIN:0,FCUMODE=singleCUMode,

RXLEVADJ-20,RXLEVADJN1D1-20;

DELETE FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h DELETE FCUMAIN”



Command Description:This command deletes the FCUMAIN unit from the BTSE data base.



DELETE FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11;

426DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN


JOB: 66

PC Time&Date: 16:35:23 03/23/2005

NE Time&Date: 16:33:17 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FCUMAIN:0



JOB: 67

PC Time&Date: 16:35:23 03/23/2005

NE Time&Date: 16:33:17 09/15/2004

USER NAME: NSN

COMMAND: Delete FCUMAIN:NAME=RACK:0/FCUMAIN:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



Example of Command Execution:Delete FCUMAIN:NAME=RACK:0/FCUMAIN:0;

DN0933412 Issue 01427


FCUMAIN

Id:0900d805805b102f

GET FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h GET FCUMAIN”



Command Description:This command displays the attributes of the FCUMAIN unit of the BTSE.



ALS alarmStatus




FCUMODE fcuMode






FPGAFWVER fpgaFwVer

TCC txCoherentComb



JOB: 59

PC Time&Date: 16:34:52 03/23/2005

NE Time&Date: 16:32:46 09/15/2004

USER NAME: NSN

GET FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11 [,REQATTL=ALS, AST, AVS, BSWVER, FCUMODE, OST, PRS, RELFUNCOBJ, RXLEVADJ, RXLEVADJN1D1, FPGAFWVER, TCC];

428DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN

COMMAND: Get FCUMAIN:NAME=RACK:0/FCUMAIN:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





bootSoftwareVersion = ""

fcuMode = doubleCUMode




rxLevAdjust(dB) =

adjustValue = 0.0



adjustValueN1 = 0.0



Operation Failed



Example of Command Execution:Get FCUMANIN:NAME=RACK:0/FTNFP:0,REQATTL=ALS&AST&AVS&BSWVER&

FCUMODE&OST&PRS&RELFUNCOBJ& RXLEVADJ&RXLEVADJN1D1;

GET FCUMAIN FWID

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h GET FCUMAIN FWID”



GET FCUMAIN FWID NAME=RACK:0..7/FCUMAIN:0..11;

DN0933412 Issue 01429


FCUMAIN

Id:0900d805805b102f

Command Description:This command provides information on the FPGA FW images that are contained in the boards flash prom together with an indication of the “active” version. Up to 4 images are provided per board. For FlexCUv2 or ECUv6 boards the FPGA FW versions are provided together with an indication whether the FW version is the active one.




None.

Operation Failed

None.


Example of Command Execution:Get FCUMAIN FWID:NAME=RACK:0/FCUMAIN:1, REQATTL=FPGAFWVER;

GET FCUMAIN WIRING

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h GET FCUMAIN WIRING”



Command Description:This command displays the attributes of the FCUMAIN unit of the BTSE.




After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of get wiring command is the following:

JOB: 221

GET FCUMAIN WIRING NAME=RACK:0..7/FCUMAIN:0..11;

430DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN

PC Time&Date: 12:13:58 03/23/2005

NE Time&Date: 13:15:33 09/15/2004

USER NAME: NSN

COMMAND: Get FCUMAIN WIRING:NAME=RACK:0/FCUMAIN:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23COMMAND RESULT: Operation suc-cessful

fcumainWiring =

variable


Operation Failed



• Refer to “FCUMAINWIRING”

Example of Command Execution:Get FCUMAIN WIRING:NAME=RACK:0/FCUMAIN:0;

GETTEST FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h GETTEST FCUMAIN”



Command Description:This command displays the attributes of the FCUMAIN test.




GETTEST FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11;

DN0933412 Issue 01431


FCUMAIN

Id:0900d805805b102f


JOB: 221

PC Time&Date: 12:13:58 03/23/2005

NE Time&Date: 13:15:33 09/15/2004

USER NAME: NSN

COMMAND: Gettest FCUMAIN:NAME=RACK:0/FCUMAIN:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/FCUMAIN:0

testMonitor =

phaseId = PreliminaryTestsFCUMAIN


phaseId = CheckAlarmStatusFCUMAIN


phaseId = EndTestFCUMAIN





Operation Failed



phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...


432DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN


Example of Command Execution:Gettest FCUMAIN:NAME=RACK:0/FCUMAIN:0;

LOCK FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h LOCK FCUMAIN”



Command Description:This command changes the administrative state of the FCUMAIN object of the BTSE.




JOB: 60

PC Time&Date: 16:35:08 03/23/2005

NE Time&Date: 16:33:02 09/15/2004

USER NAME: NSN

COMMAND: Lock FCUMAIN:NAME=RACK:0/FCUMAIN:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




LOCK FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11;

DN0933412 Issue 01433


FCUMAIN

Id:0900d805805b102f




JOB: 61

PC Time&Date: 16:35:08 03/23/2005

NE Time&Date: 16:33:02 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/FCUMAIN:0




Operation Failed



Example of Command Execution:Lock FCUMAIN:NAME=RACK:0/FCUMANIN:0

PERFTEST FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h PERFTEST FCUMAIN”



PERFTEST FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11;

434DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN

Command Description:This command is used to start an asynchronous test in FCUMAIN .




JOB: 222

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

COMMAND: Perftest FCUMAIN:NAME=RACK:0/FCUMAIN:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:6


JOB: 223

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:6


DN0933412 Issue 01435


FCUMAIN

Id:0900d805805b102f


JOB: 224

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23








JOB: 225

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:6




executedPhases =

PreliminaryTestsFCUMAIN

CheckAlarmStatusFCUMAIN

436DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN

EndTestFCUMAIN


JOB: 226

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:6




Result TEST:

name = TEST:<n>










executedPhases

DN0933412 Issue 01437


FCUMAIN

Id:0900d805805b102f

Operation Failed



Example of Command Execution:Perftest FCUMAIN:NAME=RACK:0/FCUMANIN:0

SET FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h SET FCUMAIN”



Command Description:This command is used to set the attributes of the specified FCUMAIN .





additionalWords =

....

failedPhases


....

skippedPhases


....



SET FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11 [,RXLEVADJ=] [,RXLEVADJN1D1=] [,TCC=];

438DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN

TCC txCoherentComb



JOB: 176

PC Time&Date: 12:05:36 03/23/2005

NE Time&Date: 13:07:12 09/15/2004

USER NAME: NSN

COMMAND: Set FCUMAIN:NAME=RACK:0/FCUMAIN:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



Example of Command Execution:Set FCUMAIN:NAME=RACK:0/FCUMANIN:0,RXLEVADJ=-2,RXLEVADJN1D1=-2

STOPTEST FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h STOPTEST FCUMAIN”




STOPTEST FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11;

DN0933412 Issue 01439


FCUMAIN

Id:0900d805805b102f




Operation Failed



Example of Command Execution:Stoptest FCUMAIN:NAME=RACK:0/FCUMANIN:0;

UNLOCK FCUMAIN

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h UNLOCK FCUMAIN”

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


UNLOCK FCUMAIN NAME=RACK:0..7/FCUMAIN:0..11;

440DN0933412 Issue 01


Id:0900d805805b102f

FCUMAIN



Command Description:This command changes the administrative state of the FCUMAIN object of the BTSE.




JOB: 62

PC Time&Date: 16:35:12 03/23/2005

NE Time&Date: 16:33:06 09/15/2004

USER NAME: NSN

COMMAND: Unlock FCUMAIN:NAME=RACK:0/FCUMAIN:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 63

PC Time&Date: 16:35:12 03/23/2005

NE Time&Date: 16:33:06 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


DN0933412 Issue 01441


FCUMAIN

Id:0900d805805b102f






Operation Failed



Example of Command Execution:Unlock FCUMAIN:NAME=RACK:0/FCUMANIN:0;

442DN0933412 Issue 01


Id:0900d805805b1031

FCUTR

FCUTRThe FlexCU board is modeled with three HMO instances: 1 instance of the FCUMAIN HMO and 2 instances of the FCUTR HMO. The FCUMAIN instance represents that part of the board which performs board related activities and the FCUTR instances represent carrier (TRX) specific activities. There is a dependency of the FCUTR instances towards the FCUMAIN instance of a FlexCU.

CREATE FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h CREATE FCUTR”



Command Description:This command adds the FCUTR unit to the BTSE data base.





JOB: 56

PC Time&Date: 16:34:31 03/23/2005

NE Time&Date: 16:32:25 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FCUTR:0

CREATE FCUTR NAME=RACK:0..7/FCUTR:0..23 [,TXLEVADJ=];

DN0933412 Issue 01443


FCUTR

Id:0900d805805b1031



JOB: 57

PC Time&Date: 16:34:31 03/23/2005

NE Time&Date: 16:32:25 09/15/2004

USER NAME: NSN

COMMAND: Create FCUTR:NAME=RACK:0/FCUTR:0,TXLEVADJ=1;

SW RELEASE: 01-04-17-01-26-51_05-02-23




Operation Failed


JOB: 76

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create FCUTR:NAME=RACK:0/FCUTR:0,TXLEVADJ=1;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Creation out of sequence (-162)



444DN0933412 Issue 01


Id:0900d805805b1031

FCUTR

Example of Command Execution:Create FCUTR:NAME=RACK:0/FCUTR:0,TXLEVADJ=-20;

DELETE FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h DELETE FCUTR”



Command Description:This command deletes the FCUTR unit from the BTSE data base.




JOB: 66

PC Time&Date: 16:35:23 03/23/2005

NE Time&Date: 16:33:17 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FCUTR:0



JOB: 67

DELETE FCUTR NAME=RACK:0..7/FCUTR:0..23;

DN0933412 Issue 01445


FCUTR

Id:0900d805805b1031

PC Time&Date: 16:35:23 03/23/2005

NE Time&Date: 16:33:17 09/15/2004

USER NAME: NSN

COMMAND: Delete FCUTR:NAME=RACK:0/FCUTR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



Example of Command Execution:Delete FCUTR:NAME=RACK:0/FCUTR:0;

GET FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h GET FCUTR”



Command Description:This command displays the attributes of the FCUTR unit of the BTSE.



ALS alarmStatus



CCPBL carrierCapability

GET FCUTR NAME=RACK:0..7/FCUTR:0..23 [,REQATTL=ALS, AST, AVS, CCPBL, OST, OUTPUTPR, PRS, RELFUNCOBJ, TXLEVADJ, STDBYST];

446DN0933412 Issue 01


Id:0900d805805b1031

FCUTR


OUTPUTPR outputPowerReduction







JOB: 59

PC Time&Date: 16:34:52 03/23/2005

NE Time&Date: 16:32:46 09/15/2004

USER NAME: NSN

COMMAND: Get FCUTR:NAME=RACK:0/FCUTR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





carrierCapability = edgeFourRxDiv


outputPowerReduction = db0



FMO = BTS:2/TRX:6



Operation Failed



Example of Command Execution:Get FCUTR:NAME=RACK:0/FCUTR:0,REQATTL=ALS&AST&AVS& CCPBL&OUT-PUTPR&OST&PRS&RELFUNCOBJ& TXLEVADJ;

DN0933412 Issue 01447


FCUTR

Id:0900d805805b1031

GETTEST FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h GETTEST FCUTR”



Command Description:This command displays the attributes of the FCUTR test.





JOB: 221

PC Time&Date: 12:13:58 03/23/2005

NE Time&Date: 13:15:33 09/15/2004

USER NAME: NSN

COMMAND: Gettest FCUTR:NAME=RACK:0/FCUTR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/FTNFP:0

testMonitor =

phaseId = PreliminaryTestsFCUTR


phaseId = CheckAlarmStatusFCUTR


phaseId = EndTestFCUTR



GETTEST FCUTR NAME=RACK:0..7/FCUTR:0..23;

448DN0933412 Issue 01


Id:0900d805805b1031

FCUTR



Operation Failed



Example of Command Execution:Gettest FCUTR:NAME=RACK:0/FCUTR:0;

LOCK FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h LOCK FCUTR”



Command Description:This command changes the administrative state of the FCUTR object of the BTSE.



phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK FCUTR NAME=RACK:0..7/FCUTR:0..23;

DN0933412 Issue 01449


FCUTR

Id:0900d805805b1031



JOB: 60

PC Time&Date: 16:35:08 03/23/2005

NE Time&Date: 16:33:02 09/15/2004

USER NAME: NSN

COMMAND: Lock FCUTR:NAME=RACK:0/FCUTR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 61

PC Time&Date: 16:35:08 03/23/2005

NE Time&Date: 16:33:02 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/FCUTR:0




450DN0933412 Issue 01


Id:0900d805805b1031

FCUTR

Operation Failed



Example of Command Execution:Lock FCUTR:NAME=RACK:0/FCUTR:0;

PERFTEST FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h PERFTEST FCUTR”



Command Description:This command is used to start an asynchronous test in FCUTR.




JOB: 222

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

COMMAND: Perftest FCUTR:NAME=RACK:0/FCUTR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/FCUTR:0

tO = BTSETEST:6

PERFTEST FCUTR NAME=RACK:0..7/FCUTR:0..23;

DN0933412 Issue 01451


FCUTR

Id:0900d805805b1031


JOB: 223

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:6



JOB: 224

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23








JOB: 225

452DN0933412 Issue 01


Id:0900d805805b1031

FCUTR

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:6



MOT = RACK:0/FCUTR:0

executedPhases =

PreliminaryTestsFCUTR

CheckAlarmStatusFCUTR

EndTestFCUTR


JOB: 226

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:6




Result TEST:

DN0933412 Issue 01453


FCUTR

Id:0900d805805b1031

Operation Failed



Example of Command Execution:Perftest FCUTR:NAME=RACK:0/FCUTR:0;

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



454DN0933412 Issue 01


Id:0900d805805b1031

FCUTR

SET FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h SET FCUTR”



Command Description:This command is used to set the attributes of the specified RACK.





JOB: 176

PC Time&Date: 12:05:36 03/23/2005

NE Time&Date: 13:07:12 09/15/2004

USER NAME: NSN

COMMAND: Set FCUTR:NAME=RACK:0/FCUTR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



Example of Command Execution:Set FCUTR:NAME=RACK:0/FCUTR:0;

SET FCUTR NAME=RACK:0..7/FCUTR:0..23 [,TXLEVADJ=];

DN0933412 Issue 01455


FCUTR

Id:0900d805805b1031

STOPTEST FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h STOPTEST FCUTR”







Operation Failed


STOPTEST FCUTR NAME=RACK:0..7/FCUTR:0..23;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


456DN0933412 Issue 01


Id:0900d805805b1031

FCUTR


Example of Command Execution:Stoptest FCUTR:NAME=RACK:0/FCUTR:0;

UNLOCK FCUTR

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h UNLOCK FCUTR”



Command Description:This command changes the administrative state of the FCUTR object of the BTSE.




JOB: 62

PC Time&Date: 16:35:12 03/23/2005

NE Time&Date: 16:33:06 09/15/2004

USER NAME: NSN

COMMAND: Unlock FCUTR:NAME=RACK:0/FCUTR:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





UNLOCK FCUTR NAME=RACK:0..7/FCUTR:0..23;

DN0933412 Issue 01457


FCUTR

Id:0900d805805b1031


JOB: 63

PC Time&Date: 16:35:12 03/23/2005

NE Time&Date: 16:33:06 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



Example of Command Execution:Unlock FCUTR:NAME=RACK:0/FCUTR:0;

458DN0933412 Issue 01


Id:0900d805805b1033

FTNFP

FTNFPThe FTNFP object represents the hardware of the tunable filters in dowlink direction.

CREATE FTNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h CREATE FTNFP”



Command Description:This command adds the FICOM_TNF unit to the BTSE data base.


CELLNO cellNumber




JOB: 56

PC Time&Date: 16:34:31 03/23/2005

NE Time&Date: 16:32:25 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FTNFP:0



CREATE FTNFP NAME=RACK:0..7/FTNFP:0..7 ,CELLNO= ,WDFTNFP=;

DN0933412 Issue 01459


FTNFP

Id:0900d805805b1033

JOB: 57

PC Time&Date: 16:34:31 03/23/2005

NE Time&Date: 16:32:25 09/15/2004

USER NAME: NSN

COMMAND: Create FTNFP:NAME=RACK:0/FTNFP:0,CELLNO=1,WDFT-NFP=CU0-FVSWRP0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


cellNumber = 1

wiringDataFtnfp =

CUWiring = CU0



Operation Failed


JOB: 76

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create FTNFP:NAME=RACK:0/FTNFP:0,CELLNO=1,WDFT-NFP=CU0-FVSWRP0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• The FICOM_TNFP, the CU and the FICOM_VSWRP are in the same rack and belong to the same cell

460DN0933412 Issue 01


Id:0900d805805b1033

FTNFP

Example of Command Execution:Create FTNFP:NAME=RACK:0/FTNFP:0,CELLNO=0,WDFTNFP=CU0-FVSWRP0;

DELETE FTNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h DELETE FTNFP”



Command Description:This command deletes the FICOM_TNF unit from the BTSE data base.




JOB: 66

PC Time&Date: 16:35:23 03/23/2005

NE Time&Date: 16:33:17 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FTNFP:0



JOB: 67

DELETE FTNFP NAME=RACK:0..7/FTNFP:0..7;

DN0933412 Issue 01461


FTNFP

Id:0900d805805b1033

PC Time&Date: 16:35:23 03/23/2005

NE Time&Date: 16:33:17 09/15/2004

USER NAME: NSN

COMMAND: Delete FTNFP:NAME=RACK:0/FTNFP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• FTNFP must be locked in Phase 3, before deletion

• If this object is deleted, the related TRX is out of service

Example of Command Execution:Delete FTNFP:NAME=RACK:0/FTNFP:0;

GET FTNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h GET FTNFP”



Command Description:This command displays the attributes of the FICOM_TNF unit of the BTSE.



ALS alarmStatus



GET FTNFP NAME=RACK:0..7/FTNFP:0..7 [,REQATTL=ALS, AST, AVS, CELLNO, OST, PRS, RELFUNCOBJ, TNFTARGF, WDFTNFP];

462DN0933412 Issue 01


Id:0900d805805b1033

FTNFP

CELLNO cellNumber




TNFTARGF tnfTargetFrequency




JOB: 59

PC Time&Date: 16:34:52 03/23/2005

NE Time&Date: 16:32:46 09/15/2004

USER NAME: NSN

COMMAND: Get FTNFP:NAME=RACK:0/FTNFP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





cellNumber = 1




tnfTargetFrequency = Null

wiringDataFtnfp =

CUWiring = CU0



Operation Failed


DN0933412 Issue 01463


FTNFP

Id:0900d805805b1033


• The value for the attribute relatedFuncObjects in LMT Phase 2 is "not configured"

• For list of extended values / wiringDataFtnfp refer to Chapter 9 of the FS

Example of Command Execution:Get FTNFP:NAME=RACK:0/FTNFP:0,REQATTL=ALS&AST&AVS&CELLNO&

RELFUNCOBJ&OST&PRS&TNFTARGF&WDFTNFP;

GETTEST FTNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h GETTEST FTNFP”



Command Description:This command displays the attributes of the FTNFP test.





JOB: 221

PC Time&Date: 12:13:58 03/23/2005

NE Time&Date: 13:15:33 09/15/2004

USER NAME: NSN

COMMAND: Gettest FTNFP:NAME=RACK:0/FTNFP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



testMonitor =

GETTEST FTNFP NAME=RACK:0..7/FTNFP:0..7;

464DN0933412 Issue 01


Id:0900d805805b1033

FTNFP

phaseId = PreliminaryTestsFtnfp


phaseId = CheckAlarmStatusFtnfp


phaseId = EndTestFtnfp





Operation Failed



Example of Command Execution:Gettest FTNFP:NAME=RACK:0/FTNFP:0;

LOCK FTNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h LOCK FTNFP”


phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK FTNFP NAME=RACK:0..7/FTNFP:0..7;

DN0933412 Issue 01465


FTNFP

Id:0900d805805b1033



Command Description:This command changes the administrative state of the FICOM_TNF object of the BTSE.




JOB: 60

PC Time&Date: 16:35:08 03/23/2005

NE Time&Date: 16:33:02 09/15/2004

USER NAME: NSN

COMMAND: Lock FTNFP:NAME=RACK:0/FTNFP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 61

PC Time&Date: 16:35:08 03/23/2005

NE Time&Date: 16:33:02 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


466DN0933412 Issue 01


Id:0900d805805b1033

FTNFP


NAME = RACK:0/FTNFP:0




Operation Failed



Example of Command Execution:Lock FTNFP:NAME=RACK:0/FTNFP:0

PERFTEST FTNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h PERFTEST FTNFP”



Command Description:This command is used to start an asynchronous test in FTNFP.




JOB: 222

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

PERFTEST FTNFP NAME=RACK:0..7/FTNFP:0..7;

DN0933412 Issue 01467


FTNFP

Id:0900d805805b1033

USER NAME: NSN

COMMAND: Perftest FTNFP:NAME=RACK:0/FTNFP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:6


JOB: 223

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:6



JOB: 224

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23




468DN0933412 Issue 01


Id:0900d805805b1033

FTNFP





JOB: 225

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:6




executedPhases =

PreliminaryTestsFtnfp

CheckAlarmStatusFtnfp

EndTestFtnfp


JOB: 226

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



DN0933412 Issue 01469


FTNFP

Id:0900d805805b1033

name = BTSETEST:6



Operation Failed


Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



470DN0933412 Issue 01


Id:0900d805805b1033

FTNFP




Example of Command Execution:Perftest FTNFP:NAME=RACK:0/FTNFP:0;

STOPTEST FTNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h STOPTEST FTNFP”







STOPTEST FTNFP NAME=RACK:0..7/FTNFP:0..7;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases

DN0933412 Issue 01471


FTNFP

Id:0900d805805b1033

Operation Failed



Example of Command Execution:Stoptest FTNFP:NAME=RACK:0/FTNFP:0;

UNLOCK FTNFP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h UNLOCK FTNFP”



Command Description:This command changes the administrative state of the FICOM_TNF object of the BTSE.




JOB: 62

PC Time&Date: 16:35:12 03/23/2005

NE Time&Date: 16:33:06 09/15/2004

USER NAME: NSN



....

skippedPhases


UNLOCK FTNFP NAME=RACK:0..7/FTNFP:0..7;

472DN0933412 Issue 01


Id:0900d805805b1033

FTNFP

COMMAND: Unlock FTNFP:NAME=RACK:0/FTNFP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 63

PC Time&Date: 16:35:12 03/23/2005

NE Time&Date: 16:33:06 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



Example of Command Execution:Unlock FTNFP:NAME=RACK:0/FTNFP:0;

DN0933412 Issue 01473


FVSWRP

Id:0900d805805b1035

FVSWRPThe FVSWRP object represents the hardware of the tunable filters in the dowlink direc-tion. There is only one FVSWR per cell, which performs also some functionalities common to the cell (e.g. alarm generation).

CREATE FVSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h CREATE FVSWRP”



Command Description:This command adds the FICOM_VSWR unit to the BTSE data base.


CELLNO cellNumber



JOB: 40

PC Time&Date: 16:31:19 03/23/2005

NE Time&Date: 16:29:13 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FVSWRP:0


CREATE FVSWRP NAME=RACK:0..7/FVSWRP:0..3 ,CELLNO=;

474DN0933412 Issue 01


Id:0900d805805b1035

FVSWRP


JOB: 41

PC Time&Date: 16:31:19 03/23/2005

NE Time&Date: 16:29:13 09/15/2004

USER NAME: NSN_Ross

COMMAND: Create FVSWRP:NAME=RACK:0/FVSWRP:0,CELLNO=1;

SW RELEASE: 01-04-17-01-26-51_05-02-23


cellNumber = 1


Operation Failed


JOB: 77

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN_Ross

COMMAND: Create FVSWRP:NAME=RACK:0/FVSWRP:0,CELLNO=1;

SW RELEASE: 01-04-17-01-26-51_05-02-23





Example of Command Execution:Create FVSWRP:NAME=RACK:0/FVSWRP:0,CELLNO=0;

DN0933412 Issue 01475


FVSWRP

Id:0900d805805b1035

DELETE FVSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h DELETE FVSWRP”



Command Description:This command deletes the FICOM_VSWR unit from the BTSE data base.




JOB: 51

PC Time&Date: 16:33:29 03/23/2005

NE Time&Date: 16:31:23 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/FVSWRP:0



JOB: 52

PC Time&Date: 16:33:29 03/23/2005

NE Time&Date: 16:31:23 09/15/2004

DELETE FVSWRP NAME=RACK:0..7/FVSWRP:0..3;

476DN0933412 Issue 01


Id:0900d805805b1035

FVSWRP

USER NAME: NSN_Ross

COMMAND: Delete FVSWRP:NAME=RACK:0/FVSWRP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• FVSWRP must be locked in Phase 3, before deletion


Example of Command Execution:Delete FVSWRP:NAME=RACK:0/FVSWRP:0;

GET FVSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h GET FVSWRP”



Command Description:This command displays the attributes of the FICOM_VSWR unit of the BTSE.



ALS alarmStatus



CELLNO cellNumber




GET FVSWRP NAME=RACK:0..7/FVSWRP:0..3 [,REQATTL=ALS, AST, AVS, CELLNO, OST, PRS, RELFUNCOBJ];

DN0933412 Issue 01477


FVSWRP

Id:0900d805805b1035



JOB: 43

PC Time&Date: 16:32:46 03/23/2005

NE Time&Date: 16:30:40 09/15/2004

USER NAME: NSN_Ross

COMMAND: Get FVSWRP:NAME=RACK:0/FVSWRP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





cellNumber = 1





Operation Failed



• The value for the attribute relatedFuncObjects in LMT Phase 2 is "not configured"

Example of Command Execution:Get FVSWRP:NAME=RACK:0/FVSWRP:0,REQATTL=ALS&AST&AVS&CELLNO&

RELFUNCOBJ&OST&PRS;

GETTEST FVSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h GETTEST FVSWRP”

GETTEST FVSWRP NAME=RACK:0..7/FVSWRP:0..3;

478DN0933412 Issue 01


Id:0900d805805b1035

FVSWRP



Command Description:This command displays the attributes of the FVSWRP test.





JOB: 227

PC Time&Date: 12:14:01 03/23/2005

NE Time&Date: 13:15:36 09/15/2004

USER NAME: NSN_Ross

COMMAND: Gettest FVSWRP:NAME=RACK:0/FVSWRP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/FVSWRP:0

testMonitor =

phaseId = PreliminaryTestsFvswrp


phaseId = CheckAlarmStatusFvswrp


phaseId = EndTestFvswrp





Operation Failed


DN0933412 Issue 01479


FVSWRP

Id:0900d805805b1035


Example of Command Execution:Gettest FVSWRP:NAME=RACK:0/FVSWRP:0;

LOCK FVSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h LOCK FVSWRP”



Command Description:This command changes the administrative state of FICOM_VSWR unit of the BTSE.




JOB: 45


phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK FVSWRP NAME=RACK:0..7/FVSWRP:0..3;

480DN0933412 Issue 01


Id:0900d805805b1035

FVSWRP

PC Time&Date: 16:33:14 03/23/2005

NE Time&Date: 16:31:08 09/15/2004

USER NAME: NSN_Ross

COMMAND: Lock FVSWRP:NAME=RACK:0/FVSWRP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 46

PC Time&Date: 16:33:14 03/23/2005

NE Time&Date: 16:31:08 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/FVSWRP:0




Operation Failed



DN0933412 Issue 01481


FVSWRP

Id:0900d805805b1035

Example of Command Execution:Lock FVSWRP:NAME=RACK:0/FVSWRP:0;

PERFTEST FVSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h PERFTEST FVSWRP”



Command Description:This command is used to start an asynchronous test in FVSWRP.




JOB: 228

PC Time&Date: 12:14:07 03/23/2005

NE Time&Date: 13:15:42 09/15/2004

USER NAME: NSN_Ross

COMMAND: Perftest FVSWRP:NAME=RACK:0/FVSWRP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



tO = BTSETEST:1


JOB: 229

PERFTEST FVSWRP NAME=RACK:0..7/FVSWRP:0..3;

482DN0933412 Issue 01


Id:0900d805805b1035

FVSWRP

PC Time&Date: 12:14:18 03/23/2005

NE Time&Date: 13:15:49 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1



JOB: 230

PC Time&Date: 12:14:18 03/23/2005

NE Time&Date: 13:15:49 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23








JOB: 231

PC Time&Date: 12:14:23 03/23/2005

NE Time&Date: 13:15:52 09/15/2004

USER NAME: NSN_Ross

DN0933412 Issue 01483


FVSWRP

Id:0900d805805b1035

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:1




executedPhases =

PreliminaryTestsFvswrp

CheckAlarmStatusFvswrp

EndTestFvswrp


JOB: 232

PC Time&Date: 12:14:41 03/23/2005

NE Time&Date: 13:16:05 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1




Result TEST:

name = TEST:<n>



484DN0933412 Issue 01


Id:0900d805805b1035

FVSWRP

Operation Failed




Example of Command Execution:Perftest FVSWRP:NAME=RACK:0/FVSWRP:0;

STOPTEST FVSWRP








executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



STOPTEST FVSWRP NAME=RACK:0..7/FVSWRP:0..3;

DN0933412 Issue 01485


FVSWRP

Id:0900d805805b1035

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h STOPTEST FVSWRP”







Operation Failed



Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


486DN0933412 Issue 01


Id:0900d805805b1035

FVSWRP

Example of Command Execution:Stoptest FVSWRP:NAME=RACK:0/FVSWRP:0;

UNLOCK FVSWRP

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h UNLOCK FVSWRP”



Command Description:This command changes the administrative state of FICOM_VSWR unit of the BTSE.




JOB: 47

PC Time&Date: 16:33:19 03/23/2005

NE Time&Date: 16:31:13 09/15/2004

USER NAME: NSN_Ross

COMMAND: Unlock FVSWRP:NAME=RACK:0/FVSWRP:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






UNLOCK FVSWRP NAME=RACK:0..7/FVSWRP:0..3;

DN0933412 Issue 01487


FVSWRP

Id:0900d805805b1035

JOB: 48

PC Time&Date: 16:33:19 03/23/2005

NE Time&Date: 16:31:13 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23







Operation Failed



Example of Command Execution:Unlock FVSWRP:NAME=RACK:0/FVSWRP:0;

488DN0933412 Issue 01


Id:0900d805805b1037

LAPDLE

LAPDLEThe LAPDLE object identifies the logical link used by the BTSplus mainline to commu-nicate with the Flexi BSCproduct family for operational and maintenance purposes.

CREATE LAPDLE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h LAPDLE h CREATE LAPDLE”



Command Description:This command adds a LAPDLE object in the BTSE database.


LAPDCH lapdChannel



JOB: 150

PC Time&Date: 12:02:21 03/23/2005

NE Time&Date: 13:03:56 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = LAPDLE:2



CREATE LAPDLE NAME=LAPDLE:0..10 ,LAPDCH=;

DN0933412 Issue 01489


LAPDLE

Id:0900d805805b1037

JOB: 151

PC Time&Date: 12:02:31 03/23/2005

NE Time&Date: 13:04:06 09/15/2004

USER NAME: NSN_Ross

COMMAND: Create LAPDLE:NAME=LAPDLE:2,LAPDCH=BPORT0-1-SSL0_16KB;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 152

PC Time&Date: 12:02:31 03/23/2005

NE Time&Date: 13:04:06 09/15/2004

USER NAME: NSN_Ross

COMMAND: Create LAPDLE:NAME=LAPDLE:1,LAPDCH=BPORT0-1-SSL0_16KB;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• The LAPDLE object must be always created before the creation of the correspond-ing object on Flexi BSC product family side, otherwise the Abis Alignment procedure is going to fail

Example of Command Execution:Create LAPDLE:NAME=LAPDLE:0,LAPDCH=2-2-FULL_64KB;

490DN0933412 Issue 01


Id:0900d805805b1037

LAPDLE

DELETE LAPDLE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h LAPDLE h DELETE LAPDLE”



Command Description:This command deletes the LAPDLE from the BTSE data base.




JOB: 158

PC Time&Date: 12:03:55 03/23/2005

NE Time&Date: 13:05:22 09/15/2004

USER NAME: NSN_Ross

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = NAME=LAPDLE:2;



JOB: 159

PC Time&Date: 12:04:03 03/23/2005

NE Time&Date: 13:05:35 09/15/2004

DELETE LAPDLE NAME=LAPDLE:0..10;

DN0933412 Issue 01491


LAPDLE

Id:0900d805805b1037

USER NAME: NSN_Ross

COMMAND: Delete LAPDLE:NAME=LAPDLE:2;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



Example of Command Execution:Delete LAPDLE:NAME=LAPDLE:0;

GET LAPDLE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h LAPDLE h GET LAPDLE”



Command Description:This command displays the attributes of the LAPDLE unit of the BTSE.



ALS alarmStatus



LAPDCH lapdChannel





GET LAPDLE NAME=LAPDLE:0..10 [,REQATTL=ALS, AST, AVS, LAPDCH, OST, PRS, RELFUNCOBJ, STDBYST];

492DN0933412 Issue 01


Id:0900d805805b1037

LAPDLE



JOB: 149

PC Time&Date: 12:02:04 03/23/2005

NE Time&Date: 13:03:39 09/15/2004

USER NAME: NSN_Ross

COMMAND: Get LAPDLE:NAME=LAPDLE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





lapdChannel =

BPORT = BPORT0

TSL = 17

SSL = FULL_64KB




standbyStatus = ColdStandBy


Operation Failed




Example of Command Execution:Get LAPDLE:NAME=RACK:0,REQATTL=ALS&AST&AVS&LAPCH&

RELFUNCOBJ&OST&PRS&STBYST;

DN0933412 Issue 01493


RACK

Id:0900d805805b103b

RACKThe RACK object models the rack of the BTSplus mainline family.

The BS240/1 consists of a base rack with up to 8 TRXs. Optionally it can be connected to two extension racks to reach up to 24 TRX. The BS240XL consists of a base rack with up to 12 TRXs. Optionally it can be connected to an extension rack to reach up to 24 TRXs.

CREATE RACK

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CREATE RACK”



Command Description:This command adds the object RACK together with its attributes to the BTSE data base.


TYPRACK typeOfBtse



JOB: 230

PC Time&Date: 14:50:07 03/23/2005

NE Time&Date: 00:17:45 09/15/2004

USER NAME: NSN_ Eberhard

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:1

CREATE RACK NAME=RACK:0..7 ,TYPRACK=;

494DN0933412 Issue 01


Id:0900d805805b103b

RACK



JOB: 231

PC Time&Date: 14:50:08 03/23/2005

NE Time&Date: 00:17:46 09/15/2004


COMMAND: Create RACK:NAME=RACK:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23

COMMAND RESULT Operation successful


Operation Failed


JOB: 232

PC Time&Date: 14:50:08 03/23/2005

NE Time&Date: 00:17:46 09/15/2004


COMMAND: Create RACK:NAME=RACK:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• RACK:0 can never be created. It had to be set, with Set RACK as first command

• If an other rack type for RACK:0 is create, you had to format the flash and had to make a power on; e.g. if you have at coba in DB (rack0) racktype BS242 (pico) and want a racktype 240XL at coba. You had to format the flash and had to make a power on at coba. With set rack or delete db this is not possible. (here you have dif-ferent SW)

DN0933412 Issue 01495


RACK

Id:0900d805805b103b

( ! ) The Command Create RACK is no longer supported for BS240SWB, BS241SWB and BS240XLSWB

Example of Command Execution:Create RACK:NAME=RACK:1,TYPRACK=BS240;

DELETE RACK

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DELETE RACK”



Command Description:This command deletes the object RACK together with its attributes from the BTSE data base.




JOB: 233

PC Time&Date: 14:50:08 03/23/2005

NE Time&Date: 00:17:46 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:1


DELETE RACK NAME=RACK:0..7;

496DN0933412 Issue 01


Id:0900d805805b103b

RACK


JOB: 234

PC Time&Date: 14:50:08 03/23/2005

NE Time&Date: 00:17:46 09/15/2004


COMMAND: Delete RACK:NAME=RACK:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• RACK:0 can never be deleted by DELETE command only using FORMAT FLASH and power on

Example of Command Execution:

• Delete RACK:NAME=RACK:1

• It can be deleted with format flash and power on

GET RACK

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h GET RACK”



Command Description:This command displays the attributes related to the specified RACK.



ALS alarmStatus

GET RACK NAME=RACK:0..7 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, TYPRACK];

DN0933412 Issue 01497


RACK

Id:0900d805805b103b






TYPRACK typeOfBtse



JOB: 5

PC Time&Date: 12:03:10 03/23/2005

NE Time&Date: 12:01:00 09/15/2004


COMMAND: Get RACK:NAME=RACK:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


alarmStatus = MINOR






typeOfBtse = BS240XL


Operation Failed



Example of Command Execution:Get RACK:NAME=RACK:0,REQATTL=ALS&AST&AVS&RELFUNCOBJ&OST&

498DN0933412 Issue 01


Id:0900d805805b103b

RACK

PRS&TYPRACK;

LOCK RACK

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h LOCK RACK”



Command Description:This command changes the administrative state of the object RACK.




JOB: 235

PC Time&Date: 14:50:08 03/23/2005

NE Time&Date: 00:17:46 09/15/2004


COMMAND: Lock RACK:NAME=RACK:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 236

LOCK RACK NAME=RACK:0..7;

DN0933412 Issue 01499


RACK

Id:0900d805805b103b

PC Time&Date: 14:50:08 03/23/2005

NE Time&Date: 00:17:46 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:1




Operation Failed



• RACK:0 can never be locked

Example of Command Execution:Lock RACK:NAME=RACK:1;

SET RACK

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h SET RACK”



Command Description:This command is used to set the attributes of the specified RACK.


TYPRACK typeOfBtse


SET RACK NAME=RACK:0..7 [,TYPRACK=];

500DN0933412 Issue 01


Id:0900d805805b103b

RACK


JOB: 176

PC Time&Date: 12:05:36 03/23/2005

NE Time&Date: 13:07:12 09/15/2004


COMMAND: Set RACK:NAME=RACK:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• The attribute TYPRACK must be set. Otherwise the NetAct system is not able to identify the correct BTSplus mainline

• RACK:0 has to be set, otherwise no object can be created

• RACK:0 cannot be changed, it has to be deleted by delete BTSEPDBFILE (e.g., if you have a coba with rack BS240 and want a racktype 240XL you have to delete dbfile (delete DB). Here you have the same SW)

( ! ) The Command Set RACK is no longer supported for BS240SWB, BS241SWB and BS240XLSWB

Example of Command Execution:Set RACK:NAME=RACK:0,TYPRACK=BS240;

UNLOCK RACK

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h UNLOCK RACK”



UNLOCK RACK NAME=RACK:0..7;

DN0933412 Issue 01501


RACK

Id:0900d805805b103b

Command Description:This command changes the administrative state of the object RACK.




JOB: 237

PC Time&Date: 14:50:08 03/23/2005

NE Time&Date: 00:17:46 09/15/2004


COMMAND: Unlock RACK:NAME=RACK:1;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 238

PC Time&Date: 14:50:09 03/23/2005

NE Time&Date: 00:17:47 09/15/2004


SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:1

502DN0933412 Issue 01


Id:0900d805805b103b

RACK




Operation Failed



Example of Command Execution:Unlock RACK:NAME=RACK:0;

DN0933412 Issue 01503


REMINV

Id:0900d805805b103d

REMINVThe REMINV object manages the BTSplus mainline local Inventory Data Table in case of installation of new hardware objects or replacement of already existing hardware objects.

DNLIDFD REMINV

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h REMINV h DNLIDFD REMINV”



Command Description:This command executes the download of the NOB file (containing nob_RIUs of the IDF) from the LMT hard disk to the BTSE flash EPROMs.


SRCDIR sourceDir


After command execution, a further message indicates the result of the operation. An example of dnlidfd command is the following:

JOB: 155

PC Time&Date: 12:03:15 03/23/2005

NE Time&date: 0:00:00 00/00/0

USER NAME: NSN

COMMAND: Dnlidfd REMINV:NAME=REMINV:0,SRCDIR="C:\labuser\BsPlus";

SW RELEASE: N.A.



Operation Failed

None.

DNLIDFD REMINV NAME=REMINV:0..0 [,SRCDIR=];

504DN0933412 Issue 01


Id:0900d805805b103d

REMINV


• This file is to be created previously using the "IDF-Editor". The name for BTSE is fix "BTS_NRIU"

Example of Command Execution:Dnlidfd REMINV:SRCDIR="C:\Programme\IdfEditor|\dnload";

UPLLIDF REMINV

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h REMINV h UPLLIDF REMINV”



Command Description:This command executes the uploading of the IDF (Inventory Data File) from the BTSE flash EPROMs to the LMT hard disk.


DESTDIR destinationDir

FILE file

OVERWRITE Overwrite


After command execution, a further message indicates the result of the operation. An example of upllidf command is the following:

JOB: 156

PC Time&Date: 12:03:18 03/23/2005

NE Time&date: 0:00:00 00/00/0

USER NAME: NSN

COMMAND: Upllidf REMINV:NAME=REMINV:0,OVERWRITE=YES;

SW RELEASE: N.A.


Uploading File: BTSE.IDT

UPLLIDF REMINV NAME=REMINV:0..0 [,DESTDIR=] [,FILE=] ,OVERWRITE=;

DN0933412 Issue 01505


REMINV

Id:0900d805805b103d

To: BTSE.IDT

On Directory: ..\Idf\Upload


JOB: 157

PC Time&Date: 12:03:19 03/23/2005

NE Time&date: 00:00:00 00/00/0

USER NAME: NSN

COMMAND: Upllidf REMINV:NAME=REMINV:0,OVERWRITE=YES;

SW RELEASE: 01-04-17-01-26-51_05-02-23


Upload End: File BTSE.IDT Transfer Completed


Operation Failed

None.


• The offline tool "IDF-Editor" is used to display and modify the uploaded IDT. It is used also for converting the IDT into an IDF or to extract the NOB file

• The default value of FILE is BTSE.IDT

Example of Command Execution:Uplidfd REMINV:DESTDIR="c:\rem_inve",FILE="bts_inv.idt",OVERWRITE=YES;

506DN0933412 Issue 01


Id:0900d805805b103f

SOFTWARE-MANAGEMENT

SOFTWARE-MANAGEMENTThe SOFTWARE-MANAGEMENT object supports software management functions and manages the BTSplus mainline file system.

DNLALLEXE SOFTWARE-MANAGEMENT

Command Tree:“MANAGED-ELEMENT h SOFTWARE-MANAGEMENT h DNLALLEXE SOFTWARE-MANAGEMENT”



Command Description:This command executes the software downloading of the BTSplus mainline SW from the LMT Evolution PC hard disk to the COBA board.

Long Names:IDSOFTWARE-MANAGEMENT Address of the managed object

SRCPATH srcpath

OVERWRITE Overwrite


Download START. After command execution, a further message indicates the result of the operation. An example of dnlallexe command is the following:

JOB: 175

PC Time&Date: 12:05:17 03/23/2005

NE Time&date: 0:00:00 00/00/0

USER NAME: NSN

COMMAND: DNLALLEXE:SRCPATH="C\test\hs031785\HS011722.SWL",OVER-WRITE=YES;

SW RELEASE: 01-04-17-01-26-51_05-02-23


Downloading File: HS011726.SWL:01-04-17-01-26-51_05-02-23


SRCPATH= ,OVERWRITE=;

DN0933412 Issue 01507


SOFTWARE-MANAGEMENT

Id:0900d805805b103f

Version: 02-08-01-01-00-27_04-11-19


Operation Failed

= (invalid SW-Version, defective SW)


• If the incorrect SW version is given, the system will reject the command

• The SWLoadSafety will not be overwritten

• In Phase 1 this command is followed by a forced download

• In Phase 2 the command is followed by a forced download if the SwVersion is iden-tical to the currentSWLoad

Example of Command Execution:Dnlallexe:SRCPATH="c:\path\HS011722.SWL", OVERWRITE= YES;

UPLBTSLOG SOFTWARE-MANAGEMENT

Command Tree:“MANAGED-ELEMENT h SOFTWARE-MANAGEMENT h UPLBTSLOG SOFTWARE-MANAGEMENT”



Command Description:The usage of this command is reserved to the R&D and should be used only under R&D request.

Long Names:IDSOFTWARE-MANAGEMENT Address of the managed object

FILETYPE FileType

DESTDIR destinationDir

FILE file

ENTRIES entries

OVERWRITE Overwrite


After command execution, a further message indicates the result of the operation. An example of uplbtslog command is the following:


FILETYPE= ,DESTDIR= ,FILE= [,ENTRIES=] ,OVER-WRITE=;

508DN0933412 Issue 01


Id:0900d805805b103f

SOFTWARE-MANAGEMENT

JOB: 177

PC Time&Date: 12:06:04 03/23/2005

NE Time&date: 0:00:00 00/00/0

USER NAME: NSN

COMMAND: UPLBTSLOG:DESTDIR="D:\DocumentBtsplus",FILE="240xl",OVER-WRITE=YES;

SW RELEASE: N.A.


Uploading File: 240xl

To: 240xl

On Directory: D:\DocumentBtsplus


JOB: 178

PC Time&Date: 12:06:25 03/23/2005

NE Time&date: 00:00:00 00/00/0

USER NAME: NSN

COMMAND: UPLBTSLOG:DESTDIR="D:\DocumentBtsplus",FILE="240xl",OVER-WRITE=YES;

SW RELEASE: 01-04-17-01-26-51_05-02-23


Uploading File 240xl:

100 packets received


Operation Failed

None.


DN0933412 Issue 01509


SOFTWARE-MANAGEMENT

Id:0900d805805b103f

Example of Command Execution:The execution of this command is reserved to the R&D and should be executed only under R&D request.

510DN0933412 Issue 01


Id:0900d805805b1041

SYNCBTSE

SYNCBTSEThe SYNCBTSE object holds parameters that the user can configure. The object indi-cates the synchronization state and accuracy. This is sufficient to maintain configuration and states, so no further modeling of the external GPS equipment is necessary.

GET SYNCBTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h GET SYNCBTSE”



Command Description:This command displays the attributes of the SYNCBTSE of the BTSE.



ALS alarmStatus



CLKACC clockAccuracy

MPHERR maxPhaseError(microsec)

MRSYNCT maxResyncTime(min)




SBPRT syncBport

SYNCSRC syncSource

SYNCSTAT syncState



GET SYNCBTSE NAME=SYNCBTSE:0..0 [,REQATTL=ALS, AST, AVS, CLKACC, MPHERR, MRSYNCT, OST, PRS, RELFUN-COBJ, SBPRT, SYNCSRC, SYNCSTAT];

DN0933412 Issue 01511


SYNCBTSE

Id:0900d805805b1041

JOB: 7

PC Time&Date: 16:24:35 03/23/2005

NE Time&Date: 16:22:29 09/15/2004

USER NAME: NSN

COMMAND: Get SYNCBTSE:NAME=SYNCBTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





clockAccuracy = high

maxPhaseError(microsec) = 1.5

maxResyncTime(min) = 180




syncSource = abis

syncState = abis


Operation Failed



Example of Command Execution:Get SYNCBTSE:NAME=SYNCBTSE:0,REQATTL=ALS&AST&AVS&BCPBL&

CLKACC&MPHERR&MRSYNCT&OST&PRS&RELFUNCOBJ&SYNCSRC&

SYNCSTAT;

GETTEST SYNCBTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h GETTEST SYNCBTSE”

GETTEST SYNCBTSE NAME=SYNCBTSE:0..0;

512DN0933412 Issue 01


Id:0900d805805b1041

SYNCBTSE



Command Description:This command displays the attributes of the SYNCBTSE test.





JOB: 300

PC Time&Date: 14:50:17 03/23/2005

NE Time&Date: 00:17:55 09/15/2004

USER NAME: NSN

COMMAND: Gettest SYNCBTSE:NAME=SYNCBTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = SYNCBTSE:0

testMonitor =

phaseId = PreliminaryTestsSYNCBTSE


phaseId = CheckAlarmStatusSYNCBTSE


phaseId = EndTestSYNCBTSE





Operation Failed


DN0933412 Issue 01513


SYNCBTSE

Id:0900d805805b1041


Example of Command Execution:Gettest SYNCBTSE:NAME=SYNCBTSE:0,REQATTL=MORT&TESTMON&

TESTOUT&TESTST;

LOCK SYNCBTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h LOCK SYNCBTSE”



Command Description:This command changes the administrative state of the SYNCBTSE of the BTSE.





phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK SYNCBTSE NAME=SYNCBTSE:0..0;

514DN0933412 Issue 01


Id:0900d805805b1041

SYNCBTSE

JOB: 8

PC Time&Date: 16:24:42 03/23/2005

NE Time&Date: 16:22:36 09/15/2004

USER NAME: NSN

COMMAND: Lock SYNCBTSE:NAME=SYNCBTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 9

PC Time&Date: 16:24:42 03/23/2005

NE Time&Date: 16:22:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = SYNCBTSE:0




Operation Failed


DN0933412 Issue 01515


SYNCBTSE

Id:0900d805805b1041

Application Guidelines:Lock of SYNCBTSE (= SET administrativeState to â??locked) is rejected if syncSource = ext_1pps_only

Example of Command Execution:Lock SYNCBTSE:NAME=SYNCBTSE:0;

PERFTEST SYNCBTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h PERFTEST SYNCBTSE”



Command Description:This command is used to start an asynchronous test in SYNCBTSE.




JOB: 240

PC Time&Date: 14:50:09 03/23/2005

NE Time&Date: 00:17:47 09/15/2004

USER NAME: NSN

COMMAND: Perftest SYNCBTSE:NAME=SYNCBTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = SYNCBTSE

tO = BTSETEST:1


PERFTEST SYNCBTSE NAME=SYNCBTSE:0..0;

516DN0933412 Issue 01


Id:0900d805805b1041

SYNCBTSE

JOB: 241

PC Time&Date: 14:50:09 03/23/2005

NE Time&Date: 00:17:47 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1



JOB: 242

PC Time&Date: 14:50:12 03/23/2005

NE Time&Date: 00:17:51 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = SYNCBTSE:0





JOB: 243

PC Time&Date: 14:50:12 03/23/2005

NE Time&Date: 00:17:51 09/15/2004

USER NAME: NSN

DN0933412 Issue 01517


SYNCBTSE

Id:0900d805805b1041

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:1



MOT = SYNCBTSE:0

executedPhases =

PreliminaryTestsSYNCBTSE

CheckAlarmStatusSYNCBTSE

EndTestSYNCBTSE


JOB: 244

PC Time&Date: 14:50:09 03/23/2005

NE Time&Date: 00:17:47 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1




Result TEST:

name = TEST:<n>



518DN0933412 Issue 01


Id:0900d805805b1041

SYNCBTSE

Operation Failed



Example of Command Execution:Perftest SYNCBTSE:NAME=SYNCBTSE:0;

SET SYNCBTSE








executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



SET SYNCBTSE NAME=SYNCBTSE:0..0 [,MPHERR=] [,MRSYNCT=] [,SYNCSRC=];

DN0933412 Issue 01519


SYNCBTSE

Id:0900d805805b1041

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h SET SYNCBTSE”



Command Description:This command sets the attributes for the mapping of the SYNCBTSE.


MPHERR maxPhaseError(microsec)

MRSYNCT maxResyncTime(min)

SYNCSRC syncSource



JOB: 20

PC Time&Date: 12:06:33 03/23/2005

NE Time&Date: 12:04:23 09/15/2004

USER NAME: NSN

COMMAND: Set SYNCBTSE:NAME=SYNCBTSE:0,MPHERR=1.5,SYNC-SRC=abis;

SW RELEASE: 01-04-17-01-26-51_05-02-23


maxPhaseError(microsec) = 1.5

syncSource = abis


Operation Failed


520DN0933412 Issue 01


Id:0900d805805b1041

SYNCBTSE


• Setting syncSource to "ext_1pps_only" is rejected for COBA different than COBA4P12 version 2 or CESCOBA

• Setting syncSource to "ext_1pps_only" is rejected if administrativeState of SYNCBTSE is locked

Example of Command Execution:Set SYNCBTSE:NAME=SYNCBTSE:0,MPHERR=1.5,MRSYNCT=200,

SYNCSRC=extGPS;

STOPTEST SYNCBTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h STOPTEST SYNCBTSE”







STOPTEST SYNCBTSE NAME=SYNCBTSE:0..0;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases

DN0933412 Issue 01521


SYNCBTSE

Id:0900d805805b1041

Operation Failed



Example of Command Execution:Stoptest SYNCBTSE:NAME=SYNCBTSE:0;

UNLOCK SYNCBTSE

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h UNLOCK SYNCBTSE”



Command Description:This command changes the administrative state of the SYNCBTSE to the BTSE.




JOB: 10

PC Time&Date: 16:24:48 03/23/2005

NE Time&Date: 16:22:42 09/15/2004

USER NAME: NSN



....

skippedPhases


UNLOCK SYNCBTSE NAME=SYNCBTSE:0..0;

522DN0933412 Issue 01


Id:0900d805805b1041

SYNCBTSE

COMMAND: Unlock SYNCBTSE:NAME=SYNCBTSE:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 11

PC Time&Date: 16:24:48 03/23/2005

NE Time&Date: 16:22:42 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = SYNCBTSE:0




Operation Failed



Example of Command Execution:Unlock SYNCBTSE:NAME=SYNCBTSE:0;

DN0933412 Issue 01523


TMA

Id:0900d805805b1043

TMAThe TMA object models the tower mounted amplifier.

CREATE TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h CREATE TMA”



Command Description:This command adds the TMA (Tower Mounted Amplifier) to the BTSE data base.




JOB: 5

PC Time&Date: 16:24:23 03/23/2005

NE Time&Date: 16:22:17 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/TMA:0



JOB: 6

CREATE TMA NAME=RACK:0..7/TMA:0..15;

524DN0933412 Issue 01


Id:0900d805805b1043

TMA

PC Time&Date: 16:24:23 03/23/2005

NE Time&Date: 16:22:17 09/15/2004

USER NAME: NSN

COMMAND: Create TMA:NAME=RACK:0/TMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 80

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create TMA:NAME=RACK:0/TMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• The DUAMCO/DIAMCO amplifier has two different operation modes which can be selected by e.g. DIP switches. In case a TMA is used the DUAMCO/DIAMCO must be configured in the MUCO mode. If no TMA is used the DUAMCO/DIAMCO must be configured in the AMCO mode

• As in the MUCO mode the gain is reduced to about 0 dB, the exact gain of the DUAMCO/DIAMCO to compensate the cable losses must be adjusted once during the installation of the BTSplus mainline by the service personnel

Example of Command Execution:Create TMA:NAME=RACK:0/TMA:0;

DN0933412 Issue 01525


TMA

Id:0900d805805b1043

DELETE TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h DELETE TMA”



Command Description:This command deletes the TMA (Tower Mounted Amplifier) to the BTSE data base.




JOB: 14

PC Time&Date: 16:24:59 03/23/2005

NE Time&Date: 16:22:53 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = RACK:0/TMA:0



JOB: 15

PC Time&Date: 16:24:59 03/23/2005

NE Time&Date: 16:22:53 09/15/2004

DELETE TMA NAME=RACK:0..7/TMA:0..15;

526DN0933412 Issue 01


Id:0900d805805b1043

TMA

USER NAME: NSN

COMMAND: Delete TMA:NAME=RACK:0/TMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• TMA must be locked in phase 3 before deletion

• If a DULNA or DILNA with attribute "InaPredecessor" containing a TMA should be deleted, then the tMA contained the attribute has to be deleted before

Example of Command Execution:Delete TMA:NAME=RACK:0/TMA:0;

GET TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h GET TMA”






ALS alarmStatus




GET TMA NAME=RACK:0..7/TMA:0..15 [,REQATTL=ALS, AST, AVS, OST, PRS, RELFUNCOBJ, PRDINF, ANTMN, ANTSN, BND<x>, BMWD<x>, GN<x>, SUBUNT, RXBMINF, RXBMAXF, TXBMINF, TXBMAXF, MAXGN, MINGN, GNR, INSD, INSID, BTSID, SCID, ANTB, MTLT];

DN0933412 Issue 01527


TMA

Id:0900d805805b1043



PRDINF productInfo(prodNbr_SN_HwVer_SwVer)

ANTMN antennaModelNumber

ANTSN antennaSerialNumber

BND<x> band<x>

BMWD<x> beamWidth<x>(degree)

GN<x> gain0(dBi*1<x>)

SUBUNT subUnitType

RXBMINF rxBandMinFreq(kHz*100)

RXBMAXF rxBandMaxFreq(kHz*100)

TXBMINF txBandMinFreq(kHz*100)

TXBMAXF txBandMaxFreq(kHz*100)

MAXGN maxGain(dB*4)

MINGN minGain(dB*4)

GNR gainResolution(dB*4)

INSD installDate

INSID installerId

BTSID baseStationId

SCID sectorId

ANTB antennaBearing(degree)

MTLT mechanicalTilt(degree*10)


None.

Operation Failed

None.


Example of Command Execution:GET TMA: NAME=RACK:0/TMA:0, REQATTL=ALS&AST&AVS&OST&PRS&REL-FUNCOBJ&ANTMN& ANTSN& BND0& BMWD0& GN0& BND1& BMWD1& GN1&BND2& BMWD2& GN2& BND3& BMWD3& GN3& SUBUNT& RXBMINF& RXB-MAXF&TXBMINF& TXBMAXF& MAXGN& MINGN& GNR& INSD& INSID& BTSID& SCID&ANTB& MTLT;

GET TMA PRODUCTINFOGET TMA PRODUCT-INFO

NAME=RACK:0..7/TMA:0..15;

528DN0933412 Issue 01


Id:0900d805805b1043

TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h GET TMA PRODUCTINFO”







After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of get product info command is the following:

JOB: 90

PC Time&Date: 15.05.2008 10:09:30 +02:00

NE Time&Date: 01.01.1990 00:05:05 +00:00

USER NAME: NSN

COMMAND: Get TMA PRODUCTINFO:NAME=RACK:0/TMA:0;

SW RELEASE: 01-04-19-01-01-MB_08-05-13


productInfo(prodNbr_SN_HwVer_SwVer) = "CS7299111.02; X9081012052;

HW_V_A06; FW_V02.02.00_BL_V02.02.00"


Binary Command

0d 00 80 ff 12 02 81 81 ab 1a 00 00 1a 01 a1

Binary Response

4a 00 80 00 02 12 01 82 ab 1a 00 00 a1 3e 43 53 37 32 39 39

31 31 31 2e 30 32 3b 20 58 39 30 38 31 30 31 32 30 35 32 3b

20 48 57 5f 56 5f 41 30 36 3b 20 46 57 5f 56 30 32 2e 30 32

2e 30 30 5f 42 4c 5f 56 30 32 2e 30 32 2e 30 30

Operation Failed

None.


DN0933412 Issue 01529


TMA

Id:0900d805805b1043

Example of Command Execution:GET TMA PRODUCTINFO: NAME=RACK:0TMA:0, REQATTL= PRDINF;

GETTEST TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h GETTEST TMA”



Command Description:This command displays the attributes of the TMA test.





JOB: 239

PC Time&Date: 14:50:09 03/23/2005

NE Time&Date: 00:17:47 09/15/2004

USER NAME: NSN

COMMAND: Gettest TMA:NAME=RACK:0/TMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


MOT = RACK:0/TMA:0

testMonitor =

phaseId = PreliminaryTestsTma


phaseId = CheckAlarmStatusTma


GETTEST TMA NAME=RACK:0..7/TMA:0..15;

530DN0933412 Issue 01


Id:0900d805805b1043

TMA

phaseId = EndTestTma





Operation Failed



Example of Command Execution:Gettest TMA:NAME=RACK:0/TMA:0;

LOCK TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h LOCK TMA”




phaseId =

phaseStatus =

phaseId =

phaseStatus =

...

...



LOCK TMA NAME=RACK:0..7/TMA:0..15;

DN0933412 Issue 01531


TMA

Id:0900d805805b1043

Command Description:This command changes the administrative state of the TMA (Tower Mounted Amplifier) of the BTSE.




JOB: 8

PC Time&Date: 16:24:42 03/23/2005

NE Time&Date: 16:22:36 09/15/2004

USER NAME: NSN

COMMAND: Lock TMA:NAME=RACK:0/TMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 9

PC Time&Date: 16:24:42 03/23/2005

NE Time&Date: 16:22:36 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/TMA:0


532DN0933412 Issue 01


Id:0900d805805b1043

TMA



Operation Failed



Example of Command Execution:Lock TMA:NAME=RACK:0/TMA:0;

PERFTEST TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h PERFTEST TMA”



Command Description:This command is used to start an asynchronous test in TMA.




JOB: 240

PC Time&Date: 14:50:09 03/23/2005

NE Time&Date: 00:17:47 09/15/2004

USER NAME: NSN

COMMAND: Perftest TMA:NAME=RACK:0/TMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


PERFTEST TMA NAME=RACK:0..7/TMA:0..15;

DN0933412 Issue 01533


TMA

Id:0900d805805b1043

MOT = RACK:0/TMA:0

tO = BTSETEST:1


JOB: 241

PC Time&Date: 14:50:09 03/23/2005

NE Time&Date: 00:17:47 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1



JOB: 242

PC Time&Date: 14:50:12 03/23/2005

NE Time&Date: 00:17:51 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/TMA:0





534DN0933412 Issue 01


Id:0900d805805b1043

TMA

JOB: 243

PC Time&Date: 14:50:12 03/23/2005

NE Time&Date: 00:17:51 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23


Test Report:

name = BTSETEST:1



MOT = RACK:0/TMA:0

executedPhases =

PreliminaryTestsTma

CheckAlarmStatusTma

EndTestTma


JOB: 244

PC Time&Date: 14:50:09 03/23/2005

NE Time&Date: 00:17:47 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = BTSETEST:1




DN0933412 Issue 01535


TMA

Id:0900d805805b1043

Operation Failed




Result TEST:

name = TEST:<n>










executedPhases


additionalWords =

....

failedPhases


....

skippedPhases


....



536DN0933412 Issue 01


Id:0900d805805b1043

TMA

Example of Command Execution:Perftest TMA:NAME=RACK:0/TMA:0;

STOPTEST TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h STOPTEST TMA”







STOPTEST TMA NAME=RACK:0..7/TMA:0..15;

Result TEST:

name = TEST:<n>




executedPhases


.

failedPhases



....

skippedPhases


DN0933412 Issue 01537


TMA

Id:0900d805805b1043

Operation Failed



Example of Command Execution:Stoptest TMA:NAME=RACK:0/TMA:0;

UNLOCK TMA

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h UNLOCK TMA”



Command Description:This command changes the administrative state of the TMA (Tower Mounted Amplifier) to the BTSE.




JOB: 10

PC Time&Date: 16:24:48 03/23/2005

NE Time&Date: 16:22:42 09/15/2004

USER NAME: NSN

COMMAND: Unlock TMA:NAME=RACK:0/TMA:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23




UNLOCK TMA NAME=RACK:0..7/TMA:0..15;

538DN0933412 Issue 01


Id:0900d805805b1043

TMA



JOB: 11

PC Time&Date: 16:24:48 03/23/2005

NE Time&Date: 16:22:42 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = RACK:0/TMA:0




Operation Failed



Example of Command Execution:Unlock TMA:NAME=RACK:0/TMA:0;

DN0933412 Issue 01539


TRX

Id:0900d805805b1045

TRXThe TRX object models the transceivers connected to a certain Flexi BSCproduct family.

GET TRX

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h TRX h GET TRX”



Command Description:This command displays the attributes of the specified Transceiver.



ABISCH abisChannel

ANTHOPHW antennaHoppingHw



DLTESTFREQ dlTestFrequency

DMACFHSYID dmaCFHSyId

DYNPOOLINFO dynamicPoolInfo

MOEC memberOfEmergencyConfig


PWRRED txPwrMaxReduction(*-2dB)

RADIOMG radioMeasGran

RADIOMR radioMeasRep

TEI tei

TESTMODE enableTestMode

TESTPWRRED testPowerReduction

TRXAREA trxArea

TRXCPBL trxCapability

GET TRX NAME=BTS:0..11/TRX:0..23 [,REQATTL=ABISCH, ANTHOPHW, AST, AVS, DLTESTFREQ, DMACFHSYID, DYNPOOLINFO, MOEC, OST, PWRRED, RADIOMG, RADIOMR, TEI, TESTMODE, TESTPWRRED, TRXAREA, TRXCPBL, TRXFREQ, TRXMD, RADIUSEXT];

540DN0933412 Issue 01


Id:0900d805805b1045

TRX

TRXFREQ carrierFrequency

TRXMD trxMode

RADIUSEXT radiusExtension(km)



JOB: 18

PC Time&Date: 11:33:24 03/23/2005

NE Time&Date: 11:31:14 09/15/2004

USER NAME: NSN

COMMAND: Get TRX:NAME=BTS:0/TRX:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23


abisChannel =

BPORT = 0

TSL = 1

SSL = NOT_USED

antennaHoppingHw =


availabilityStatus = Dependency

memberOfEmergencyConfig = TRUE


txPwrMaxReduction(*-2dB) = 6

radioMeasGran = 1

radioMeasRep = ON

trxArea = NONE

carrierFrequency = 21

tei = 1

trxCapability = UNKNOWN

trxMode = GSM


Operation Failed

DN0933412 Issue 01541


TRX

Id:0900d805805b1045



• The TRX attribute trxCapability reflects the type of CU (GSM or EDGE) which is allo-cated to the TRX. If no CU isallocated, the attribute is set to "none". This static assignment is not reasonable, because even if the TRX is disabled a CU may be still allocated to the TRX (e.g. faulty combiner equipment)

Example of Command Execution:Get TRX:NAME=BTS:0/TRX:0,REQATTL=ABISCH&ANTHOPHW&AST&AVS&

DMACFHSYID&MOEC&OST&PWRRED&RADIOMG&RADIOMR&TEI&TRXAREA&

TRXCPBL&TRXFREQ&TRXMD;

GETRELATIONSHIP TRX

Command Tree:“MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h TRX h GETRELATIONSHIP TRX”



Command Description:This command displays the attributes of the specified Transceiver.




After command execution, a message of Changed Configuration Notification is dis-played. A further message indicates the result of the operation. An example of get rela-tionship command is the following:

JOB: 161

PC Time&Date: 12:04:08 03/23/2005

NE Time&Date: 13:05:43 09/15/2004

USER NAME: NSN

COMMAND: Getrelationship TRX:NAME=BTS:0/TRX:0;

GETRELATIONSHIP TRX

NAME=BTS:0..11/TRX:0..23;

542DN0933412 Issue 01


Id:0900d805805b1045

TRX

SW RELEASE: 01-04-17-01-26-51_05-02-23



RACK:0/COBA:0

RACK:0/CU:3

RACK:0/DUVSWR:3

RACK:0/DULNA:2

RACK:0/TMA:2

RACK:0/DUDCTMA:2

RACK:0/DULNA:3

RACK:0/TMA:3

RACK:0/DUDCTMA:3


Operation Failed



Example of Command Execution:Getrelationship TRX:NAME=BTS:0/TRX:0;

DN0933412 Issue 01543


XCONNECT

Id:0900d805805b1047

XCONNECTThe XCONNECT object represents an hardware BTSE object that enables the cross-connection between PCM timeslots of different ports of related BTSplus mainline.

CREATE XCONNECT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h CREATE XCONNECT”



Command Description:This command provides the XCONNECT (Multidrop-Star CrossConnect) of 64Kbit/s timeslots and additionally a mapping of the timeslot position is provided. This command allows also the PCM30/24 conversion.


MPTSLXX mappingTSLXX



JOB: 15

PC Time&Date: 12:05:31 03/23/2005

NE Time&Date: 12:03:22 09/15/2004

USER NAME: NSN_Brigitte

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = XCONNECT:0


CREATE XCONNECT NAME=XCONNECT:0..7 [,MPTSLXX=];

544DN0933412 Issue 01


Id:0900d805805b1047

XCONNECT


JOB: 16

PC Time&Date: 12:05:31 03/23/2005

NE Time&Date: 12:03:22 09/15/2004

USER NAME: NSN_Brigitte

COMMAND: Create XCONNECT:NAME=XCONNECT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed


JOB: 81

PC Time&Date: 16:37:54 03/23/2005

NE Time&Date: 16:35:47 09/15/2004

USER NAME: NSN

COMMAND: Create XCONNECT:NAME=XCONNECT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





• A XConnect instance is always related to a primary BPort instance. So this target BPort instance must be created before and configured as StarX

• A cross connection can only be established between a primary circuit and a second-ary circuit, but not between two primary circuits or secondary circuits

• A secondary circuit can only be used for cross connect functionality

• A remapping can only be performed for a primary circuit. Only for traffic or signalling timeslots the remapping is applicable, but not for a layer1 control timeslot

DN0933412 Issue 01545


XCONNECT

Id:0900d805805b1047

• TS 0 means to delete the TS of the XConnect

Example of Command Execution:Create XCONNECT:NAME=XCONNECT:0,MPTSL01=0-0;

DELETE XCONNECT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h DELETE XCONNECT”



Command Description:This command deletes the XCONNECT (Multidrop-Star CrossConnect) of 64Kbit/s timeslots from the BTSE data base.




JOB: 25

PC Time&Date: 12:07:08 03/23/2005

NE Time&Date: 12:04:59 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



name = XCONNECT:0



DELETE XCONNECT NAME=XCONNECT:0..7;

546DN0933412 Issue 01


Id:0900d805805b1047

XCONNECT

JOB: 26

PC Time&Date: 12:07:08 03/23/2005

NE Time&Date: 12:04:59 09/15/2004

USER NAME: NSN

COMMAND: Delete XCONNECT:NAME=XCONNECT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23



Operation Failed



• Deletion of a secondary circuit is only allowed, if there are no cross connections established to the related BPort instance

• Deletion of XConnect is possible in phase 2 or phase 3

• In phase 3 the XConnect object must be locked before it can be deleted

Example of Command Execution:Delete XCONNECT:NAME=XCONNECT:0;

GET XCONNECT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h GET XCONNECT”



Command Description:This command displays the attributes of XCONNECT (Multidrop-Star CrossConnect) and additionally of the timeslot position mapping.


GET XCONNECT NAME=XCONNECT:0..7 [,REQATTL=ALS, AST, AVS, MPTSLXX, OST, PRS, RELFUNCOBJ];

DN0933412 Issue 01547


XCONNECT

Id:0900d805805b1047


ALS alarmStatus









JOB: 17

PC Time&Date: 12:05:47 03/23/2005

NE Time&Date: 12:03:37 09/15/2004

USER NAME: NSN

COMMAND: Get XCONNECT:NAME=XCONNECT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23





mappingTSL01 =

targetBport = 0

targetTSL = 0

mappingTSL02 =

targetBport = 0

targetTSL = 0

mappingTSL03 =

targetBport = 0

targetTSL = 0

mappingTSL04 =

targetBport = 0

targetTSL = 0

548DN0933412 Issue 01


Id:0900d805805b1047

XCONNECT

mappingTSL05 =

targetBport = 0

targetTSL = 0

mappingTSL06 =

targetBport = 0

targetTSL = 0

mappingTSL07 =

targetBport = 0

targetTSL = 0

mappingTSL08 =

targetBport = 0

targetTSL = 0

mappingTSL09 =

targetBport = 0

targetTSL = 0

mappingTSL10 =

targetBport = 0

targetTSL = 0

mappingTSL11 =

targetBport = 0

targetTSL = 0

JOB: 17

mappingTSL12 =

targetBport = 0

targetTSL = 0

mappingTSL13 =

targetBport = 0

targetTSL = 0

mappingTSL14 =

targetBport = 0

targetTSL = 0

mappingTSL15 =

targetBport = 0

targetTSL = 0

mappingTSL16 =

targetBport = 0

targetTSL = 0

mappingTSL17 =

targetBport = 0

DN0933412 Issue 01549


XCONNECT

Id:0900d805805b1047

targetTSL = 0

mappingTSL18 =

targetBport = 0

targetTSL = 0

mappingTSL19 =

targetBport = 0

targetTSL = 0

mappingTSL20 =

targetBport = 0

targetTSL = 0

mappingTSL21 =

targetBport = 0

targetTSL = 0

mappingTSL22 =

targetBport = 0

targetTSL = 0

mappingTSL23 =

targetBport = 0

targetTSL = 0

mappingTSL24 =

targetBport = 0

targetTSL = 0

mappingTSL25 =

targetBport = 0

targetTSL = 0

mappingTSL26 =

targetBport = 0

targetTSL = 0

mappingTSL27 =

targetBport = 0

targetTSL = 0

JOB: 17

mappingTSL28 =

targetBport = 0

targetTSL = 0

mappingTSL29 =

targetBport = 0

targetTSL = 0

mappingTSL30 =

550DN0933412 Issue 01


Id:0900d805805b1047

XCONNECT

targetBport = 0

targetTSL = 0

mappingTSL31 =

targetBport = 0

targetTSL = 0





Operation Failed



Example of Command Execution:Get XCONNECT:NAME=XCONNECT:0,REQATTL=ALS&AST&AVS&

MPTSL01&MPTSL02&MPTSL03&MPTSL04&MPTSL05&MPTSL06&MPTSL07&




MPTSL29&MPTSL30&MPTSL31&OST&PRS&RELFUNCOBJ;

LOCK XCONNECT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h LOCK XCONNECT”



Command Description:This command changes the administrative state of the XCONNECT (Multidrop-Star CrossConnect).



LOCK XCONNECT NAME=XCONNECT:0..7;

DN0933412 Issue 01551


XCONNECT

Id:0900d805805b1047


JOB: 19

PC Time&Date: 12:06:07 03/23/2005

NE Time&Date: 12:03:58 09/15/2004

USER NAME: NSN

COMMAND: Lock XCONNECT:NAME=XCONNECT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 18

PC Time&Date: 12:06:02 03/23/2005

NE Time&Date: 12:03:54 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = XCONNECT:0




Operation Failed

552DN0933412 Issue 01


Id:0900d805805b1047

XCONNECT



• This command has no effect on the established connections

Example of Command Execution:Lock XCONNECT:NAME=XCONNECT:0;

SET XCONNECT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h SET XCONNECT”



Command Description:This command sets the attributes for the mapping of the XCONNECT (Multidrop-Star CrossConnect) 64Kbit/s timeslot position.





JOB: 20

PC Time&Date: 12:06:33 03/23/2005

NE Time&Date: 12:04:23 09/15/2004

USER NAME: NSN

COMMAND: Set XCONNECT:NAME=XCONNECT:0;

SW RELEASE: 01-04-17-01-26-51_05-02-23

COMMAND RESULT: SET-NACK

Operation successful

SET XCONNECT NAME=XCONNECT:0..7 [,MPTSLXX=];

DN0933412 Issue 01553


XCONNECT

Id:0900d805805b1047


Operation Failed



• A secondary circuit cannot be changed to a primary circuit and vice versa via a SET command

• A remapping can only be performed for a primary circuit

• Only for traffic or signalling timeslots the remapping is applicable, but not for a layer1 control timeslot

Example of Command Execution:Set XCONNECT:NAME=XCONNECT:0,MPTSL01=0-0;

UNLOCK XCONNECT

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h UNLOCK XCONNECT”



Command Description:This command changes the administrative state of the XCONNECT (Multidrop-Star CrossConnect).




JOB: 22

PC Time&Date: 12:06:46 03/23/2005

NE Time&Date: 12:04:37 09/15/2004

USER NAME: NSN

COMMAND: Unlock XCONNECT:NAME=XCONNECT:0;

UNLOCK XCONNECT NAME=XCONNECT:0..7;

554DN0933412 Issue 01


Id:0900d805805b1047

XCONNECT

SW RELEASE: 01-04-17-01-26-51_05-02-23






JOB: 21

PC Time&Date: 12:06:46 03/23/2005

NE Time&Date: 12:04:37 09/15/2004

USER NAME: NSN

SW RELEASE: 01-04-17-01-26-51_05-02-23



NAME = XCONNECT:0




Operation Failed



• This command has no effect on the established connections

Example of Command Execution:Unlock XCONNECT:NAME=XCONNECT:0;

DN0933412 Issue 01555


Parameters/attributes in alphabetical order

Id:0900d8058053dfb4

3 Parameters/attributes in alphabetical orderg Please note that the abbreviations marked with an * are not real parameters.

556DN0933412 Issue 01


Id:0900d805805b2e2f

a

a

ABISCHabisChannel

This attribute identifies the Timeslot Number and Sublot Number allocated on the Abis-interface.This attribute exists for CHAN and TRX objects. The attribute refers to a radio signalling link (RSL): it indicates just the default channel for the RSL - a more actual information is reflected in the object LAPDLE.

Validity RangeBPORT (TRX): 00-07 (for BS-82 II only, BPortNumber 00-03 is allowed)

TSL:

• 01-1Ffor PCM30 • 01-18 for PCM24

SSL:

• 0 for bit 7 and 6 on LMT Evolution displayed "SSL0” • 1 for bit 5 and 4 on LMT Evolution displayed "SSL1" • 2 for bit 3 and 2 on LMT Evolution displayed "SSL2" • 3 for bit 1 and 0 on LMT Evolution displayed "SSL3"

g 0x10 for bit 7, 6, 5 and 4 on LMT Evolution displayed "SSL0_32KB", 0x11 for bit 3, 2, 1 and 0 on LMT Evolution displayed "SSL1_32KB", 0xFF 64 kbit/sec on LMT Evolution displayed "NOT_USED" are valid only for the abisChannel attribute on object TRX.

There is no dedicated message to connect the terrestrial traffic channel. The connection is executed by means of the reception of the “SET” message containing this channel attribute.

When this attribute is related to the TRX object, the attribute identifies the associated Abis physical link for RSL signaling. Moreover, there must be a LAPDLE instance asso-ciated with this link.

When this attribute is related to the CHAN object, the attribute identifies the associated Abis physical link for radio traffic channel.

Default ValueNone.

Contained in the following commands: GET CHAN, GET TRX

ABISLKSATsAbisLinkSatellited

The attribute informs the BTSE SW about the presence of a satellite on the Asub inter-face.

DN0933412 Issue 01557


a

Id:0900d805805b2e2f

Validity Range

Default ValueterrestrialConnection

Contained in the following commands: GET BTSM NOSWL, SET BTSM

ABISTIMEsAbisExternalTime

This attribute provides the time-of-day time of the BTSE. This attribute functions as a reference for all time stamp activities in the BTSE. A daily update of the attribute is per-formed via Abis. Additionally the attribute is update after each successful Abis-align-ment.

Validity RangeIn commands GET BTSM NOSWL:

In commands SET BTSM:

Default ValueNone.

Contained in the following commands: GET BTSM NOSWL, SET BTSM

ACBQPFFacBQPFgtFac

acBQPFgtFac defines the forgetting factor for the time exponential filter used for BQP averaging. A change of the attribute becomes effective at the next AC period.

terrestrialConnection

satelliteConnection

<ANY>

<NULL>

year 1992 - 2099

month 1 - 12

day 1 - 31

hour 0 - 23

min 0 - 59

sec 0 - 59

offsetHour -12 - 14

offsetMinute 0 - 45

558DN0933412 Issue 01


Id:0900d805805b2e2f

a

Validity Range

Default Value 0.2

Contained in the following commands: GET BTS

ACBQPMAXacBQPMax(%)

acBQPMax specifies the maximum tolerated Bad Quality Probability (outage probability) in the cell. If e.g. acFERMax is 5% and acBQPMax is 10% it indicates that more than 10% of the speech samples having a FER with more than 5% is not acceptable. A change of the attribute becomes effective at the next AC period.

Validity Range

Default Value 5%


ACEFLFFacEFLFgtFac

acEFLFgtFac defines the forgetting factor for the exponential filter used for fractional load averaging. A change of the attribute becomes effective at the next AC period.

Validity Range

0.1 - 1.0 10 entries can be selected:

- 1 corresponds to the attribute value 0.1


2 - 10 9 entries can be selected:

- 2 corresponds to the attribute value 2%

- 10 corresponds to the attribute value 10%




DN0933412 Issue 01559


a

Id:0900d805805b2e2f

Default Value 0.04


ACFERMAXacFERMax(%)

acFERMax is a criterion for the speech quality in terms of frame erasure rate (FER).

acFERMax specifies the maximum tolerated FER for speech samples taken over 4 SACCH periods, e.g. acFERMax = 5.0% requires that not more than 5% bad speech frames are allowed in a sample taken over 4 SACCH periods, i.e. the FER over the sampling period of 4 SACCH frames shall be less or equal to 5%. In other words, if the percentage of bad frames (FER > acFERMax) is greater than acFERMax the respective sample will increase the BQP. A change of the attribute becomes effective at the next AC period.

Validity Range

Default Value 5.0%


ACLNKTYPacLinkType

acLinkType defines the type of samples to be collected. It also specifies the way they will be used for the BQP evaluation.

acLinkType == 0 and acLinkType == 2 require EMR (ENHANCED MEASUREMENT REPORTING). A change of the attribute becomes effective at the next AC period.

Validity Range


- 1 corresponds to the attribute value 1.0%

- 19 corresponds to the attribute value 10.0%

(the step size is 0.5%)

UL_AND_DL_SAMPLES_SEPARATELY

UL_SAMPLES_ONLY

UL_AND_DL_SAMPLES_COMMONLY

560DN0933412 Issue 01


Id:0900d805805b2e2f

a

Default Value UL_SAMPLES_ONLY (Collect and evaluate UL samples only)


ACMAXEFLDMAacMaxEFLDMA(%)

acMaxEFLDMA specifies the maximum effective frequency load (EFL). The value is valid for each DMA layer of the cell. A change of the attribute becomes effective at the next AC period.

Validity Range 10%

15%

. .

. .

100%

(starting from 10, 19 entries could be selected, with step size = 5)

Default Value 50%


ACMINEFLDMAacMinEFLDMA(%)

acMinEFLDMA specifies the minimum EFL. The value is valid for each DMA layer of the cell. A change of the attribute becomes effective at the next AC period.

Validity Range 5 5%

10 10%

..

..

50 50%

(starting from 5, the entries could be selected, with step size=5)

Default Value 50%

DN0933412 Issue 01561


a

Id:0900d805805b2e2f


ACONNalarmConnector

The MDUX alarm line can be assigned to any ACTC alarm connector which is freely configurable via an ENVABTSE object. The relative ENVABTSE must not be created if the related connector is used for the MDUX.

Validity Range

Default ValueNone.

Contained in the following commands: CREATE BCOM, GET BCOM, SET BCOM

ACPERacPeriod

acPeriod specifies the time/length of every Admission Control Period in measurement reporting periods (480 milliseconds) (e.g. 100 periods) used for the periodic AC evalua-tion and the periodic reporting to the Flexi BSC product family via the 'Radio Link Admis-sion Control Message. A change of the attribute becomes effective at the next AC period.

Validity Range 20 20 measurement reporting periods

24 24 measurement reporting periods

. . measurement reporting periods

. . measurement reporting periods



(96 possible entries with step size equal to 4)

Default Value 120 measurement reporting periods


ENVA0

ENVA1

...

ENVA8

562DN0933412 Issue 01


Id:0900d805805b2e2f

a

ACTVINCactivationIncluded

This attribute indicates whether the installed FW is activated automatically by LRU reset or not.

Validity Range

Default ValueNone.

Contained in the following commands: FWUPGRADE BTSM

ALGNSTEPalignmentStep

new information

Validity Range

Default ValueNone.

Contained in the following commands: REQCURSTASYN BTSEP

ALIGCOBAalignedCoba

The attribute indicates that the flash content is potentially incomplete due to a previously interrupted

COBA alignment. 16

The alignedCOBA attribute is automatically set to 'False' by the BTSE if the passive COBA could not be aligned. If the attribute is set to TRUE by the operator (to indicate, that he checked and, if necessary, corrected the Flash-contents to his needs) the according alarm is ceased.

The setting to 'False' via command is rejected.

Validity Range

TRUE

FALSE

summaryObjectsOnly

summarisedObjectsOnly

allObjects

TRUE

DN0933412 Issue 01563


a

Id:0900d805805b2e2f

Default Value

Contained in the following commands: GET BTSEP NOSWL, SET BTSEP

ALRMCLETalarmClearanceTime

An alarm must not be active at least for this time before it is ceased. The time is expressed by the number of polling periods (1 s).

Validity Range

Default Value

Contained in the following commands: CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL

ALRMCOUNTERalarmCount

FALSE

TRUE

1 - 20

10

The BTSE supports a filter mechanism for the following failure event reports related to pcm line problems (and is valid for all created BPORT instances).

1. "lower BER threshold exceeded"

2. "external signal absence"

3. "AIS alarm"

4. "frame alignment loss"

5. "higher BER threshold exceeded"

6. "remote alarm"

The following filter mechanism is applied for the failure event reports 1-6 listed above.

An alarm is generated because of 2 possible events:

a) If it is found active for a time interval equal or greater than alarmTiming2.

564DN0933412 Issue 01


Id:0900d805805b2e2f

a

Validity Range

Default Value

Contained in the following commands: CREATE COBA, GET COBA, SET COBA

ALRMPERTalarmPersistencyTime

All alarms which could toggle must persist at least for this time before an alarm is reported. The time is expressed by the number of polling periods (1 s).

Validity Range

Default Value


ALRMSEVXXXalarmSeverityXXX

b) If it is found active with a duration less than alarmTiming2 but it is found active at least as often as alarmCount in a time interval equal to alarmTiming3. The number of the alarm is incremented every time a transition 'not active' to 'active' is detected.

The alarm contains an information in the additional information parameter whether it was detected due to event a) or event b).

An active alarm is cleared if no alarm is found for a time interval equal to alarmTiming1.

1 - 254

32

1 - 20

3

This attribute defines the severity that the BTSE SW has to use for the given type of HW board in case of state transitions from 'enabled' to 'disabled failed'.

A change of the attribute becomes effective with the start of a new failure, i.e. if the attribute is changed and a failure is still pending the change of the attribute will not trigger a 'failure ceased' failure event report together with a failure event report with the new alarmSeveri-tyXXX.

DN0933412 Issue 01565


a

Id:0900d805805b2e2f

Validity Range

Default Value


ALRMT1/2/3alarmTiming1(sec)/2/3

List of BS240, BS24XL, BS241, BS40, BS41 HW:

ALRMSEVACDC, ALRMSEVACT, ALRMSEVBATTERY,

ALRMSEVCOBA, ALRMSEVCOSA, ALRMSEVCU,

ALRMSEVDIDCTMA, ALRMSEVDILNA, ALRMSEVDUDCTMA,

ALRMSEVDULNA, ALRMSEVDUVSWR, ALRMSEVFANP,

ALRMSEVFCUMAIN,ALRMSEVFCUTR,ALRMSEVFTNFP,

ALRMSEVFVSWRP,ALRMSEVTMA

CRITICAL

MAJOR

MINOR

DEFAULT_DB

DEFAULT_DB

The attribute value is valid for all created BPORT instances.

The BTSE supports a filter mechanism for the following failure event reports related to pcm line problems:

1. "lower BER threshold exceeded"

2. "external signal absence"

3. "AIS alarm"

4. "frame alignment loss"

5. "higher BER threshold exceeded"

6. "remote alarm"

The following filter mechanism is applied for the failure event reports listed above.

An alarm is generated because of 2 possible events:

a) If it is found active for a time interval equal or greater than alarmTiming2.

566DN0933412 Issue 01


Id:0900d805805b2e2f

a

Validity Range

Default Value


ALSalarmStatus

This attribute shows the highest severity of all active alarm conditions related to the managed object. In case of summarization objects a proprietary semantics is used.

Validity Range CLEARED

MINOR

MAJOR

CRITICAL

Default Value CLEARED

Contained in the following commands: GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTSEP NOSWL, GET CESPW, GET CESTUNNEL, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA, GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET XCONNECT

AMRLKATaMRLinkAdapTuning

This parameter is used by the AMR Uplink Codec Mode Adaptation in the BTSplus mainline. It tunes the transition between codec modes determined by internal thresh-

b) If it is found active with a duration less than alarmTiming2 but it is found active at least as often as alarmCount in a time interval equal to alarmTiming3. The number of the alarm is incremented every time a transition 'not active' to 'active' is detected.

- The alarm contains an information in the additional information parameter whether it was detected due to event a) or event b).

- An active alarm is cleared if no alarm is found for a time interval equal to alarmTiming1.

1 - 254

20

DN0933412 Issue 01567


a

Id:0900d805805b2e2f

olds. A value higher than the default shifts the transition towards higher carrier-to-inter-ferer or signal-to-noise ratios. A value lower than the default has the opposite effect. The step size is 0,1dB. Adaptation of AMR Half Rate and AMR Full Rate is affected simulta-neously. All possible transitions between modes are generally shifted by the same amount.

However, to account for a limited range of the underlying measurements, shifts of tran-sitions near the upper range limit tend to saturate when shifted closer to the limit. The default value is the optimum setting and normally requires no modification.

Validity Range

Default Value 0 dB


AMRLKATWFSaMRLinkAdapTuningWFS(dB)

This attribute indicates whether the installed FW is be activated automatically by LRU reset or not. This parameter is used by the AMR Uplink Codec Mode Adaptation in the BTSplus mainline. It tunes the transition between codec modes determined by internal thresholds.

A value higher than the default shifts the transition towards higher carrier-to-interferer or signal-to-noise ratios.

A value lower than the default has the opposite effect. The step size is 0,1dB. Adapta-tion of AMR Half Rate and AMR Full Rate is affected simultaneously. All possible tran-sitions between modes are generally shifted by the same amount. However, to account for a limited range of the underlying measurements, shifts of transitions near the upper range limit tend to saturate when shifted closer to the limit.

The default value is the optimum setting and normally requires no modification.

0 - 200 00 -100 (-10 dB)

01 -99

. .

. .

99 -1

100 0 (0 dB)

101 +1

. .

. .

200 +100 (10 dB)

568DN0933412 Issue 01


Id:0900d805805b2e2f

a

Validity Range

Default ValueNone.


ANT<x>CELLNOant<x>CellNumber

This attribute specifies the number of the cell. The value corresponds to the instance number of the object BTS. The attribute can be only modified if no wiring destinations are configured.

Note: <x> ... <0...5>

so the names of the attributes read:

GUI: ant0CellNumber CLI: ANT0CELLNO

ant1CellNumber ANT1CELLNO





g With the SET BCOM command it is possible to "delete" the parameters setting the value "NULL", not all together but first the wiring date and in a second command the cell parameters (see Application Guidelines: of SET BCOM).

Validity RangeIn commands CREATE BCOM, SET BCOM:

In commands GET BCOM:

Default ValueIn moc(s) BCOM:

None.

In moc(s) BCOM:


-10.0 - 10.0

0 - 11

<NULL>

<ANY>

NULL

DN0933412 Issue 01569


a

Id:0900d805805b2e2f

ANT<x>SCNRXant<x>SecondCellNumberRx

This parameter allows the sharing of one antenna by two cells in order to receive diver-sity.

Validity RangeIn commands CREATE BCOM, SET BCOM:

In commands GET BCOM:

Default ValueIn moc(s) BCOM:

None.

In moc(s) BCOM:


ANT<x>WDRXant<x>WiringDataRx

The attribute specifies the carrier unit ports, which are connected to the Rx outputs of a MDUX submodule. The maximum number of destinations is:

• 4 if MDUX only equipped

• 8 if MDUX and DUAMCO equipped

Note: <x> ... <0...5> so the names of the attributes read:

GUI: ant0WiringDataRx CLI: ANT0WDRX

ant1WiringDataRx ANT1WDRX





The following values are possible for 'RX_wiring n':

H'0012FF00 CU0N (CU0 normal path)

H'00FF00 CU0D (CU0 diversity path)



0 - 11

<NULL>

<ANY>

NULL

570DN0933412 Issue 01


Id:0900d805805b2e2f

a


H'0112FF02 CU2D (CU2diversity path)







H'002AFF00 FCUMAIN0N (FCUMAIN0 normal path)

H'012AFF00 FCUMAIN0D (FCUMAIN0 diversity path)

H'022AFF00 FCUMAIN0N1 (FCUMAIN0 Rx C / N1 path)

g With the SET BCOM command it is possible to "delete" the parameters setting the value "NULL", not all together but first the wiring date and in a second command the cell parameters (see Application Guidelines: of SET BCOM).

Validity Range

1 to 8 items of

CU0N

CU0D

CU1N

CU1D

CU2N

CU2D

CU3N

CU3D

CU4N

CU4D

CU5N

CU5D

CU6N

CU6D

CU7N

CU7D

CU8N

CU8D

CU9N

CU9D

DN0933412 Issue 01571


a

Id:0900d805805b2e2f

CU10N

CU10D

CU11N

CU11D

FCUMAIN0N

FCUMAIN0D

FCUMAIN0N1

FCUMAIN0D1

FCUMAIN1N

FCUMAIN1D

FCUMAIN1N1

FCUMAIN1D1

FCUMAIN2N

FCUMAIN2D

FCUMAIN2N1

FCUMAIN2D1

FCUMAIN3N

FCUMAIN3D

FCUMAIN3N1

FCUMAIN3D1

FCUMAIN4N

FCUMAIN4D

FCUMAIN4N1

FCUMAIN4D1

FCUMAIN5N

FCUMAIN5D

FCUMAIN5N1

FCUMAIN5D1

FCUMAIN6N

FCUMAIN6D

FCUMAIN6N1

FCUMAIN6D1

FCUMAIN7N

FCUMAIN7D

FCUMAIN7N1

FCUMAIN7D1

572DN0933412 Issue 01


Id:0900d805805b2e2f

a

Default ValueNone.

Contained in the following commands: SETWIRINGRX BCOM

ANT<x>WDTXant<x>WiringDataTx

The attribute specifies the carrier unit ports which are either directly or via HYBRID6 connected to the TX input of an MDUX submodule. The maximum number of destina-tions is:

• 1 if MDUX without HYBRID6 equipped

• 2 if MDUX with HYBRID6 equipped

• 4 if MDUX with HYBRID6 and COAMCO equipped

Validity Range

FCUMAIN8N

FCUMAIN8D

FCUMAIN8N1

FCUMAIN8D1

FCUMAIN9N

FCUMAIN9D

FCUMAIN9N1

FCUMAIN9D1

FCUMAIN10N

FCUMAIN10D

FCUMAIN10N1

FCUMAIN10D1

FCUMAIN11N

FCUMAIN11D

FCUMAIN11N1

FCUMAIN11D1

NULL

<NULL>

1 to 4 items of

CU0

CU1

CU2

DN0933412 Issue 01573


a

Id:0900d805805b2e2f

CU3

CU4

CU5

CU6

CU7

CU8

CU9

CU10

CU11

FCUMAIN0TX0

FCUMAIN0TX1

FCUMAIN1TX0

FCUMAIN1TX1

FCUMAIN2TX0

FCUMAIN2TX1

FCUMAIN3TX0

FCUMAIN3TX1

FCUMAIN4TX0

FCUMAIN4TX1

FCUMAIN5TX0

FCUMAIN5TX1

FCUMAIN6TX0

FCUMAIN6TX1

FCUMAIN7TX0

FCUMAIN7TX1

FCUMAIN8TX0

FCUMAIN8TX1

FCUMAIN9TX0

FCUMAIN9TX1

FCUMAIN10TX0

FCUMAIN10TX1

FCUMAIN11TX0

FCUMAIN11TX1

NULL

<NULL>

574DN0933412 Issue 01


Id:0900d805805b2e2f

a

Default ValueNone.

Contained in the following commands: SETWIRINGTX BCOM

ANTBantennaBearing(degree)

Attribute data provided by TMA.

Validity Range

Default ValueNone.

Contained in the following commands: GET TMA

ANTHOPHWantennaHoppingHw

Validity Range

Default ValueNone.

Contained in the following commands: GET TRX

0 - 65535

<NULL>

The attribute shows which antenna hardware is used by a TRX for antenna hopping. The attribute doesn't show how often an antenna hardware is used - i.e. the attribute doesn't reflect the actual antenna hopping sequence. The attribute length is 0 for hh-ii=04-01 if no antenna hopping is used.

Not BR8.0: In a switched beam cell, the attribute shows a list of SDUSEC instances which are enabled in the cell and offer service to the input TRXs (in this case 0 < n < 10).

type of HW = DUVSWR or SDUSEC

N <= 98 (decimal) 0 <= n < 24

0 to 23 items of

Pathname

DN0933412 Issue 01575


a

Id:0900d805805b2e2f

ANTHOPMODantennaHoppingMode

This attribute specifies whether the BCCH transceiver has to be included in the hopping sequence for Antenna Hopping or not. The attribute is only valid if the feature Antenna Hopping is enabled (attribute enableAntennaHopping).

Validity Range

Default Value NOBCCHTRX


ANTHOPPantennaHoppingPeriod

This attribute specifies how many frames will be transmitted over each antenna before the next antenna will be used to send the frames. The number of antenna changes depends on the number of used antennas and service (4-4-5 used for EDGE).The attri-bute is only valid if the feature Antenna Hopping is enabled (attribute enableAntenna-Hopping).

Validity Range

Default Value SECOND


ANTHOPSTantennaHoppingStatus

This attribute indicates the current status of Antenna Hopping. For a BTSplus mainline using only FICOM (FVSWRP) in transmit direction the attribute value is 'hopping off'. (FALSE = hopping off)

Validity Range

NOBCCHTRX

ALLTRX

ALL

SECOND

FOURTH

SEQ_445

TRUE

576DN0933412 Issue 01


Id:0900d805805b2e2f

a

Default Value FALSE


ANTMNantennaModelNumber


Validity Range

Default ValueNone.


ANTSNantennaSerialNumber


Validity Range

Default ValueNone.


ARFACCHACMDFapplyRFacchOnAnyCmdFrame

This attribute determines the LAPDm frame type on which R-FACCH (Repeated FACCH) is allowed, if the latter has been enabled by the parameter enableRFACCH on the respective codec type. The parameter is implemented as a bitmap consisting of 4 bits:

Bitmap Frame Type LAPDm Frame Type Description

0/1 I (ASSHOCMD) Only I-frames carrying ASS_CMD and HO_CMD. See note 1.

FALSE

0..15 characters string


DN0933412 Issue 01577


a

Id:0900d805805b2e2f

0/1 UI (PHSY_INFO) UI-frames carrying the PHSY_INFO. See note 1.

0/1 I (COMPLEMENTARY) I-frames excluding I (ASSHOCMD). See note 2.

0/1 UA UA response frames. See note 3.

The value '0' denotes R-FACCH is allowed while the value '1' denotes R-FACCH is not allowed on the respective LAPDm frame type.

g Notes:

1. R-FACCH shall not be used on command frames other than I-frames and UI-frames. Both I-frames and UI-frames of LAPDm protocol are used for Information transfer i.e. they contain payload of higher signaling layer. I-frames are transferred in acknowledged mode whereas UI-frames are transferred in Unacknowledged mode.

2. Distinguishing between I-frames carrying ASS_CMD and HO_CMD: I(ASSHOCMD) and the rest of I-frames: I(COMPLEMENTARY) is necessary due to problems antic-ipated with some types of legacy MS when receiving (COMPLEMENTARY) frames in R-FACCH mode.

3. UA-frames are not allowed by the 3GPP-standard now, but a Change Request to allow R-FACCH on UA-frames might be issued in the future. UA-frames of LAPDm protocol are sent as Unnumbered Acknowledgement i.e. they are used to send response to commands delivered previously in S-frames (Supervisory) frames.

Validity Range

Default ValueNone.


ASCICIPHenableCiphForASCI

The attribute enableCiphForASCI indicates whether ciphering for VGCS (Voice Group Call Service) is

enabled or disabled. VGCS ciphering allows to offer a secured path on the radio inter-face for mobiles engaged in point to multipoint connections, as it was already possible for the point to point calls.

Validity Range

TRUE

FALSE

TRUE

578DN0933412 Issue 01


Id:0900d805805b2e2f

a

Default ValueNone.


ASEVassociatedSeverity

The attribute allows the operator to define a specific severity for the failure event report related to a envaBTSE instance (site input).

The severity of alarm database is used (DEFAULT_DB) as default value.

Validity Range

Default Value

Contained in the following commands: CREATE ENVABTSE, GET ENVABTSE

ASTadministrativeState

This attribute indicates whether the management services have permitted or prohibited the use of the resource.

Validity Range

Default Value Locked for functional objects

Unlocked for equipment objects

Contained in the following commands: GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTS, GET BTSEP NOSWL, GET BTSM NOSWL, GET CESPW, GET CESTUNNEL, GET CHAN, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA,

FALSE

CRITICAL

MAJOR

MINOR

DEFAULT_DB

DEFAULT_DB

Locked

Unlocked

ShuttingDown

DN0933412 Issue 01579


a

Id:0900d805805b2e2f

GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET TRX, GET XCONNECT

ASTRINGassociatedString

This attribute allows the operator to define a specific text string for the failure event report related to an environmental alarm. It will be put into the information element "addi-tional text" of the failure event report. In case of hh=04 a specific string (##ACDC_FAULT) can be used to indicate that the support of emergency configuration in case of e.g. third party battery backup units is derived from the corresponding envaBTSE instance.

The ASCII characters are not terminated by a NULL character.

Validity Range

Default Value

Contained in the following commands: CREATE ENVABTSE, GET ENVABTSE

ASUBLKSATsAsubLinkSatellited

This attribute informs the BTSE SW about the presence of a satellite on the Asub inter-face.

Validity Range

Default Value terrestrialConnection

Contained in the following commands: GET BTSM NOSWL

AVSavailabilityStatus


""


satelliteConnection

580DN0933412 Issue 01


Id:0900d805805b2e2f

a

This attribute elaborates the Operational state and gives detailed information about the actions that occur.

Validity Range

Default Value Not Installed for equipment objects

Off line for TRX

NULL value for BTS / CHAN / BTSM

Contained in the following commands: GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTS, GET BTSEP NOSWL, GET BTSM NOSWL, GET CESPW, GET CESTUNNEL, GET CHAN, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA, GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET TRX, GET XCONNECT

1 to 6 items of

InTest

Failed

PowerOff

OffLine

OffDuty

Dependency

Degraded

NotInstalled

NULL

DN0933412 Issue 01581


b

Id:0900d805805b2e31

b

BATTCAPbatteryCapacity(*5Ah)

This attribute contains the value of the actual capacity of the installed battery in units of 5 Ah. The attribute reflects the setting of the DIP switch on the ACDCP controller board.

The value 0 corresponds to no battery backup.

The value 255 corresponds to battery backup 1275 Ah.

Note: The value 'no battery backup (0 Ah)' for a created object 'BATTERY' means that the operational state of the object will be "disabled". All other values result in the opera-tional state "enabled".

Validity Range

Default ValueNone.

Contained in the following commands: GET BATTERY

BCCHFREQbcchFrequency

0 - 255

<NULL>

This attribute is used for the objects BTS and ADJC and ADJCUMTS. It contains the absolute radio frequency channel number of the BCCH channel. It is identical to the GSM attribute BCCH ARFCN.

cellAllocationNum-ber

Hex Decimal

GSM900 "BB900" 0001 ... 007C 1 ... 124

GSM EXTENDED "F2ONLY900"

0000 ... 007C

03CF ... 03FF

0 ... 124

975 ... 1023

GSM EXTENDED REDUCED "EXT900"

0000 ... 007C

03CF ... 03FF

0 ... 124

975 ... 1023

DCS 1800 "DCS1800"

0200 ... 0375 512 ... 885

PCS 1900 0200 ... 032A 512 ... 810

GSM-R 03BB ... 03CE 955 ... 974

582DN0933412 Issue 01


Id:0900d805805b2e31

b

Validity Range

Default ValueNone.


BCOMTYPEbcomType

The attribute specifies the BCOM type. It is highly recommended to set this attribute to the correct value in order to ensure software checks for a consistent wiring in terms of the number of carrier units which can be wired to the BCOM.

It is under the user’ s responsibility to configure the correct value because the system cannot check if the value fits to the equipped hardware.

Validity Range

Default Value


GSM-DCS 0000 ... 007C

03CF ... 03FF

0200 ... 0375

0 ... 124

975 ... 1023

512 ... 885

GSM850 0080 ... 00FB 128 ... 251

GSM850-PCS 0080 ... 00FB

0200 ... 032A

128 ... 251

512 ... 810

GSM850-DCS 0080 ... 00FB

0200 ... 0375

128 ... 251

512 ... 885

0 - 1023

SixToSix

TwelveToSix

SixToSixMDUX

TwelveToSixMDUX

TwelveToSixCOAMCO

NotSet

NotSet

DN0933412 Issue 01583


b

Id:0900d805805b2e31

BCPBLboardCapability

This attribute returns the amount of configurable BPort interfaces on the related COBA board.

Validity Range

Default ValueNone.

Contained in the following commands: GET COBA

BERTbitErrorRateThreshold

This attribute defines thresholds allowed for a PCM30 or PCM24 line. The Bit Error Rate is estimated using code violation counters. The specified thresholds influence the setting of the corresponding status bits of the attribute 'lineStatusIndication'. When the lower or upper threshold is reached, a failure event report is sent. Reaching the upper threshold in a loop configuration triggers a direction switch.

g The values indicated as 'GET only' are values which were stored in a previous release in the BTSE flash eprom when these values were still allowed in a SET command.

Validity RangeIn commands CREATE BPORT, SET BPORT:

In commands GET BPORT:

twoAbisLines

fourAbisLines

ces

<NULL>

lowerThreshold E10_3

E10_4

...

E10_9

upperThreshold E10_3

E10_4

E10_5


E10_1

...

584DN0933412 Issue 01


Id:0900d805805b2e31

b

Default ValueIn moc(s) BPORT:

None.

In moc(s) BPORT:

Contained in the following commands: CREATE BPORT, GET BPORT, SET BPORT

BMWD<x>beamWidth<x>(degree)


Validity Range

Default ValueNone.


BND<x>band<x>


Validity Range

E10_9


E10_1

...

E10_5



0 - 65535

<NULL>

operating_band_I

operating_band_II

operating_band_III

operating_band_IV

operating_band_V

operating_band_VI

DN0933412 Issue 01585


b

Id:0900d805805b2e31

Default ValueNone.


BSICbsIdentityCode

This attribute contains the Base Transceiver Station Identity Code (BSIC), which is transmitted on the SCH and used for identifying a BTSplus mainline. The BSIC consists of the Network Colour Code (NCC) and the Base Station Colour Code (BCC).

Validity Range

Default ValueNone.


BSWVERbootSoftwareVersion

This attribute defines the firmware item code number. It can be read from the Boot EPROM of each processor module. The values for this attribute are identical with the SW image format (file ID and version) used in the swLoad-header-file. (exception: two bootSoftwareVersions for the TPU) or 'Not Existing' for Modules that are not equipped with a processor.

Each single field of the validity range has the following meaning.

bootSWfield 'BTBrrrhh.SWI', where:

rr BCX for COBA

BIX for CU

hh identical with the corresponding part of the bootSWversion

bootSwVersion 'cn-hh-vv-ii-ss-pp_yy-mm-dd, where:

cn Version part (network operator code)

hh Version part (HW/SW compatibility code)

vv Version part (feature package code)

operating_band_VII

operating_band_VIII

operating_band_IX

<NULL>

BCC 0 - 7

NCC 0 - 7

586DN0933412 Issue 01


Id:0900d805805b2e31

b

ii Version part (sub-feature package code)

ss Version part (actual state)

pp Patch version (usually 00)

yy-mm-dd Production date (optional)

Validity Range

Default ValueNone.

Contained in the following commands: GET COBA, GET CU, GET FCUMAIN

BTSIDbaseStationId


Validity Range

Default ValueNone.


BTSISHOPbtsIsHopping

This attribute indicates whether the BTSplus mainline uses frequency hopping or not.

FALSE = Indicates that none of the channels in the BTS hops from the O&M point of view; from radio signalling point of view this can mean either that there is really no hopping at all or that there is hopping over a single frequency.

TRUE = Means that hopping is specified on a per channel basis.

Validity Range

Default Value FALSE




TRUE

FALSE

DN0933412 Issue 01587


b

Id:0900d805805b2e31

BTSOBJIDbtsObjectId

The BTS object id is used in Flexi BSC product family MML for the BTS object. Within the BTS, the value is only used for display purposes in the BTS manager (LMT Evolu-tion).

Validity Range

Default ValueNone.


BURNOFFSburstNumberOffset

This attribute allows to adjust the burst number offset for a cell. Equal burst number offsets result in synchronized TDMA frames.

This attribute is only meaningful if the enableInterSiteSync attribute is set to 'TRUE'.

Validity Range

Default Value 0


1 - 3000

0 - 7

588DN0933412 Issue 01


Id:0900d805805b2e33

c

c

CCPBLcarrierCapability

This attribute describes the call processing capabilities of the CU and FCUTR.

- In case of CU the attribute value is derived from the ESN/PID value of the CU.

- In case of FCUTR the attribute value depends on the istance number and the fcuMode of the corrisponding FCUMAIN object.

The attribute is read-only from the Abis/LMT Evolution point of view (GET CU/ GET FCUTR). After creation in advance of a CU/FCUTR object the attribute has the value "unknown" in case of hh-ii =04-01.

The BTSE SW maps the values of the attribute carrierCapability to the values of the attri-bute trxCapability

In case of FCUTR object, the validity range is:

- unknown

- edge

- edgeFourRXdiv

- in case of FCUTR both the values 'edge' and 'edgeFourRXdiv' are mapped to 'trxCa-pability=edge'.

Validity RangeIn commands GET CU:

In commands GET FCUTR:

Default ValueNone.

Contained in the following commands: GET CU, GET FCUTR

CELLNOcellNumber

unknown

gsm

edge

unknown

edge

edgeFourRxDiv

DN0933412 Issue 01589


c

Id:0900d805805b2e33

This attribute indicates the cell number to which a HW object for the antenna combining (DILNA, DULNA, DUVSWR, FTNFP, FVSWRP) is related to. It allows to have more than one antenna combining object in a cell.

Validity Range

Default ValueNone.

Contained in the following commands: CREATE DILNA, CREATE DULNA, CREATE DUVSWR, CREATE F6LNA, CREATE F6VSWRP, CREATE FTNFP, CREATE FVSWRP, GET DILNA, GET DULNA, GET DUVSWR, GET F6LNA, GET F6VSWRP, GET FTNFP, GET FVSWRP

CELLTYPEcellType

This attribute indicates the type of cell. It is used by BTSE for compatibility checks of the HW of a cell.

Validity Range

Default ValueNone.


CHIDTchangeOnIDT

This attribute indicates a potential change of the IDTwF file. Whenever the IDFwF file was uploaded by the Flexi BSC product family the value is set to 'no change on IDT'. If a change of objects and attributes with relation to the IDT file occurs the value is set to 'IDT was changed'. If a local download of IDT data is done the value must be set manually to 'IDT was changed'.

Validity Range

Default Value IDTWasChanged

0 - 11

STDCELL

EXTCELL

DBSTDCELL

noChangeOnIDT

IDTWasChanged

590DN0933412 Issue 01


Id:0900d805805b2e33

c


CHTYPEchannelCombination

This attribute defines the logical channel combination mapped onto the physical channel (timeslot).Changing or setting this attribute means a temporary loss of service for the whole TRX.

00 TCHFULL: TCH/F + FACCH/F + SACCH/TF

03 SDCCH: SDCCH/8 + SACCH/C8 Note 3

04 MAINB-CCH:

FCCH + SCH + BCCH + CCCH Note 4

05 MBCCHC: FCCH + SCH + BCCH + CCCH +SDCCH/4 + SACCH/C4

Note 4

06 CCCH: BCCH + CCCH Note 5

07 SCBCH: SDCCH/8 + SACCH/C8 + CBCH Note 1/6

08 BCBCH: FCCH + SCH + BCCH + CCCH + SDCCH/4 + SACCH/4 + CBCH

Note 1/7

09 TCHF_HLF:

TCH/H(0,1) + FACCH/H(0,1) + SACCH/TH (0,1) or TCH/F + FACCH/F + SACCH/TF

Note 2

0A TCHSD: TCH/H(0,1) + FACCH/H(0,1) + SACCH/TH (0,1) or TCH/F + FACCH/F + SACCH/TF or SDCCH/8 + SACCH/C8

Note 2/3

Note 1: These two channel combinations are created by replacing the logical channel SDCCH number 2 with the CBCH channel.

Note 2: The actual mode is decided on a per call basis.

Note 3: Not allowed for CHAN #0 of BCCH-TRX. Only allowed up to 3 times together with SDCCH/4 on BCCH-TRX. With no SDCCH/4 on the BCCH carrier up to four SDCCH/8 are allowed on the BCCH carrier. (For hh=04 this restriction may be dropped in a later release).

Note 4: Allowed only for CHAN #0 of BCCH-TRX.

Note 5: Allowed only for CHAN #2, #4, #6 of BCCH-TRX. Not allowed together with SDCCH/4.

Note 6: Allowed only for CHAN #0, #1, #2, #3. Not allowed for CHAN #0 of BCCH-TRX. Only one CBCH is allowed per cell.

DN0933412 Issue 01591


c

Id:0900d805805b2e33

Validity Range

Note 7: Only one CBCH is allowed per cell.

Note 8: The Flexi BSC product family checks guarantee that the first SDCCH/8 is created on the BCCH TRX and that a CBCH is allowed only on the BCCH TRX.

where:

TCH = Traffic Channel

FACCH = Fast Associated Control Channel

SACCH = Slow Associated Control Channel

/H = Half Rate

/F = Full Rate

FCCH = Frequency Correction Channel

SCH = Synchronization Channel

BCCH = Broadcast Control Channel

CCCH = Common Control Channel (CCCH = PCH + RACH + AGCH)

PCH = Paging Channel

RACH = Random Access Channel

AGCH = Access Grant Channel

CBCH = Cell Broadcast Channel

The SDCCH combinations for the BCCH-TRX can be summarized as follows:

1 MAIN BCCH + 4 SDCCH/8

1 MAIN BCCH COMBINED (SDCCH/4) + 3 SDCCH/8

1 MAIN BCCH + SCBCH (SDCCH/7) + 3 SDCCH/8

1 BCBCH (SDCCH/3) + 3 SDCCH/8

TCHFULL

SDCCH

MAINBCCH

MBCCHC

CCCH

SCBCH

BCBCH

TCHF_HLF

TCHSD

TCHSF

592DN0933412 Issue 01


Id:0900d805805b2e33

c

Default ValueNone.

Contained in the following commands: GET CHAN

CLKACCclockAccuracy

This attribute indicates the accuracy of the clock.

Validity Range

Default ValueNone.

Contained in the following commands: GET SYNCBTSE

COMBMDcombMode

This attribute describes the combining mode of ACOM, DUVSWR (DUAMCO_VSRW), DULNA (DUAMCO_LNA) and DILNA(DIAMCO_LNA) . The "n:m" values listed below have the meaning "n RF inputs are combined to m RF output(s) by the ACOM, DUAMCO/FDUAMCO or DIAMCO board ". The values are not checked by BTSE appli-cations, the values are only stored for the convenience of the operator.

Validity RangeIn commands CREATE DILNA, GET DILNA:

In commands CREATE DULNA, CREATE DUVSWR, GET DULNA, GET DUVSWR:

Default ValueIn moc(s) DULNA, DUVSWR:

high

medium

low

phase

EightToTwo

OneToOne

TwoToOne

TwoToTwo

FourToTwo

EightToTwo

TwoToOneCOAMCO8

DN0933412 Issue 01593


c

Id:0900d805805b2e33

None.

In moc(s) DILNA:

Contained in the following commands: CREATE DILNA, CREATE DULNA, CREATE DUVSWR, GET DILNA, GET DULNA, GET DUVSWR

CUCONFcarrierUnitConfiguration

Validity Range

Default Value homogeneous


CUWIRINGcuWiring

EightToTwo

This attributes describes, if in a cell a homogeneous configuration of carrier units is present (default value) or if one of the defined excep-tions is configured.

The following configurations are defined:

- CU_FlexCU_BS82II: This value has to be set if the cell is served by a BS82II and has an inhomogeneous carrier unit configuration with FlexCU and CU/ECU/GCU.

- CU_ECU_DCSPCS: This value has to be set if the cell has an inhomogeneous carrier unit configuration with old 1800/1900 MHz CUs (45.3 dBm output power) and ECU V2/3/3a of the same frequency band. This value replaces the former setting of the CU attribute maxGMSKOutputPower to dBm46_3.

- homogeneous: This value has to be set if the carrier unit con-figuration is homogeneous or shall be considered as homoge-neous. All carrier units use the maximum output power, which is provided by the hardware. No adaptation of the output power is performed. This implies, that output power differ-ences greater than 2 dB will be accepted. This setting corre-sponds to the current system behaviour.

homogenous

CU_FlexCU_BS82II

CU_ECU_DCSPCS

594DN0933412 Issue 01


Id:0900d805805b2e33

c

The attribute describes the Tx and Rx wiring of the CU to the combining equipment. The attribute identifier cannot be present in the listOfRequiredAttributes together with other attribute identifiers; the attribute is not sent by the BTSE if a "Get CU" is done without the information element listOfRequiredAttributes.

Below are indicated some details about the validity range.

choice tag:

1 '0-3 optional subfields of fixed length follow (length=4-16)

txWiringPresence: (present only if choice tag is 1)

1 the next 4 bytes contain object class & instance of the object wired to the TX output

0 object class & instance don't follow

rxNWiringPresence: (present only if choice tag is 1, Octet position is variable)

1 the next 4 bytes contain object class & instance of the object wired to the RX output N


rxDWiringPresence: (present only if choice tag is 1, Octet position is variable)

1 the next 4 bytes contain object class & instance of the object wired to the RX output D


Validity Range

Default ValueNone.

Contained in the following commands: GET CU WIRING

<ANY>

DN0933412 Issue 01595


d

Id:0900d805805b11ae

d

DESTDIRdestinationDir

Validity Range

Default ValueNone.

Contained in the following commands: UPLBTSLOG SOFTWARE-MANAGEMENT, UPLLIDF REMINV

DLTESTFREQdlTestFrequency

This attribute defines the transmit frequency (ARFCN value) if the downlink interference analysis mode is enabled.

Validity Range

Default ValueNone.


DMACFHSYIDdmaCFHSyId

This attribute is used for distinguishing DMA-enabled TRXs, which are operating on dif-ferent frequency bands or at different subbands in the same cell.

Validity Range

Destination directory

This attribute specifies the directory on the LMT Evolution hard disk where the BTSE alarm buffer sw will be copied (UPLBTSLOG).

This attribute specifies the directory on the LMT Evolution hard disk where the IDT file will be copied (UPLLIDF).


<ANY>

usedOnCFHSY0

usedOnCFHSY1

596DN0933412 Issue 01


Id:0900d805805b11ae

d

Default Value DMA not used on TRX


DMCFWIDduamcoFwId

This attribute provides information of the file ID and the FW version that is active on a MFDUAMCO board.

Validity Range

Default ValueNone.

Contained in the following commands:GET DUAMCO

DTMHOMTIMERhoDTMTimer(SACCH_multiframe_480/470ms)

This attribute determines whether handover due to DTM(Dual Transfer Mode) power budget is enabled.

This attribute is only relevant if inter-cell handover is enabled in the cell (see attribute enableInterCellHO).

DTM Power budget handover means: handover to another cell if this cell offers a higher transmission level. No matter if the power level of the actual cell is above the minimum or not.

Validity Range

Default ValueNone.


DYNPOOLINFOdynamicPoolInfo

This attribute manages the dynamic allocation of traffic channels for EDGE and GPRS traffic. A timeslot from a dynamic pool is allocated only when the Abis resource (corre-

notUsed


1 - 21

DN0933412 Issue 01597


d

Id:0900d805805b11ae

sponding fixed Abis timeslots) associated with a given radio timeslot cannot any longer provide bandwidth required for transmission rates of GPRS/EDGE traffic. StartTsl and endTsl values are set to Null when the EDAP feature is disabled.

Validity Range

PortNumber PORT0

PORT1

PORT2

PORT3

PORT4

PORT5

PORT6

BPORT7

Null

startTsl TSL_01

TSL_02

TSL_03

TSL_04

TSL_05

TSL_06

TSL_07

TSL_08

TSL_09

TSL_10

TSL_11

TSL_12

TSL_13

TSL_14

TSL_15

TSL_16

TSL_17

TSL_18

TSL_19

TSL_20

TSL_21

TSL_22

TSL_23

TSL_24

598DN0933412 Issue 01


Id:0900d805805b11ae

d

TSL_25

TSL_26

TSL_27

TSL_28

TSL_29

TSL_30

TSL_31

Null

endTsl TSL_01

TSL_02

TSL_03

TSL_04

TSL_05

TSL_06

TSL_07

TSL_08

TSL_09

TSL_10

TSL_11

TSL_12

TSL_13

TSL_14

TSL_15

TSL_16

TSL_17

TSL_18

TSL_19

TSL_20

TSL_21

TSL_22

TSL_23

TSL_24

TSL_25

TSL_26

TSL_27

TSL_28

DN0933412 Issue 01599


d

Id:0900d805805b11ae

Default ValueNone.

Contained in the following commands:GET TRX

DYNTRACGRANdynTraceGranularity

dynTraceGranularity is an attribute of the BTSM and specifies the granularity (multiples of SACCH reporting period) in which the TRACE MEASUREMENT RESULT messages are transmitted on the Abis interface in case the trace is activated. A value of N means that every N-th message is transmitted. The trace is activated per channel via the acknowledged message START TRACE. The trace is stopped via the acknowledged message STOP TRACE on the radio signalling link; it is stopped also implicitly at a release of the channel.

Validity RangeThe validity range is indicated in number of "SACCH multiframes".

Default Value1

Contained in the following commands:GET BTSM NOSWL

TSL_29

TSL_30

TSL_31

Null

1 - 254

600DN0933412 Issue 01


Id:0900d805805b11b0

e

e

EACenableAc

This attribute determines, whether Admission Control evaluation must be performed. A change of the attribute becomes effective in the next AC period.

(TRUE = AC evaluation enabled)

Validity Range

Default Value FALSE (AC evaluation disabled)


EANTHOPenableAntennaHopping

This attribute indicates whether Antenna Hopping is enabled or disabled for BTS. All TRX which are not connected to FICOM will hop.

A change of the attribute becomes effective with starting time algorithm handled inter-nally by the BTSE.

TRUE = enabled

Validity Range

Default Value FALSE (disabled)


EAUTONEGenableAutoNegotiation

The attribute indicates whether the Ethernet auto negotiation for speed, duplex mode and optionally flow control is enabled for the instance of an Ethernet port.

If auto negotiation is disabled the speed will be set to 100M and duplex mode will be enabled. Also in case when this attribute is set to TRUE there will be propagated only

TRUE

FALSE

TRUE

FALSE

DN0933412 Issue 01601


e

Id:0900d805805b11b0

100M and duplex mode. If the peer Ethernet device cannot provide 100M Duplex mode, then the link remains down. Only FlowControl is really negotiated according to the setting of the attribute "enableFlowControl".

AutoNegotiation is only relevant for electrical Ethernet interfaces.

Validity Range

Default Value

Contained in the following commands: CREATE ETHPORT, GET ETHPORT, SET ETHPORT

EAUTORECenableAutoRecovery

This attribute indicates whether an automatic recovery is enabled or disabled. Prerequi-sites for an automatic recovery in case the feature is enabled are the following:

• HW-Reset cause is "Power-On" • The board is disabled.failed.unlocked

Validity Range

Default Value disabled


EEOTDenableEOTD

This attribute indicates if the Location Services (LCS) positioning method 'Enhanced Observed Time dufference' (EOTD) is being used.

(TRUE = enabled)

Validity Range


TRUE

FALSE

TRUE

disabled

enabled

TRUE

FALSE

602DN0933412 Issue 01


Id:0900d805805b11b0

e


EEXCDISTenableExcessiveDistance

This attribute indicates whether the sending of call release is enabled/disabled when the distance between the MS and the BTSplus mainline exceeds the excessive distance.

TRUE = enabled

Validity Range

Default Value TRUE (enabled)


EFCUSUPenableFcuSupport

FALSE

TRUE

For a COB4P12, 'TRUE' is the only possible value and will be assigned by the BTSE-software in case no value is provided by the operator; the attribute value 'TRUE' cannot be changed by the oper-ator.

For COBA2P8 both values are possible.

Ã½ 'FALSE' will be assigned by the BTSE-software in case no value is provided by the operator. In this case the BTSE handles up to 24 CU boards (distributed to rack 0-2). If enableFcuSupport is set to 'FALSE', the creation of the objects FCUMAIN / FCUTR is possible but any created objects FCUMAIN / FCUTR will remain in state: oper-ationalState 'DISABLED', availabilityStatus 'Not Installed'.

Ã½ 'TRUE' means that the BTSE can handle only up to 12 boards. Within these 12 boards (allowed only in base rack in case of BTS240XL, respectively allowed only in base rack and the first 4 instances of 1st extension-rack in case of BTS240 distributed to rack 0-2) any mix of CU boards and FlexCU boards (modeled as FCUMAIN and FCUTR objects) is possible.

--> The creation of any boards (CU or FlexCU) will be answered with a NACK by the BTSE, if:

- typeofBTSE is BS240XL and the board to be created is in the extension rack

DN0933412 Issue 01603


e

Id:0900d805805b11b0

The value FALSE in the validity range means:

support of FLEXCU disabled

The value TRUE in the validity range means:

support of FLEXCU enabled

Validity Range

Default ValueNone.


EFLWCTRLenableFlowControl

The attribute enables the Ethernet flow control. Flow control requires full duplex opera-tion. Received Ethernet PAUSE frames are ignored if set to â??falseâ??.

The following attribute is relevant: enableAutonegotiation

Validity Range

Default Value

- typeofBTSE is BS240 and the board to be created is in the 1st extension rack and would have an instance number greater 3, or is in the 2nd extension rack.

A change of the attribute value is possible only on a COBA2P8 and causes a reset of the BTSE. In LMTphase 3 a change of the attribute value is allowed only if the administrativeState of BTSM is 'Locked'.

--> The BTSE SW will answer with a NACK if the operator tries to set the attribute to 'TRUE' if:

- typeofBTSE is BS240XL and a board (FlexCU or CU) is created in an extension rack

- typeofBTSE is BS240 and a FlexCU or CU with an instance greater than 3 is created in 1st extension rack or any instance is created in 2nd extension rack.

TRUE

FALSE

TRUE

FALSE

FALSE

604DN0933412 Issue 01


Id:0900d805805b11b0

e


EINTSITSYNenableInterSiteSync

The attribute enableInterSiteSync allows to disable or enable the inter site synchroniza-tion.

If intersite synchronisation is enabled, the attributes burstNumberOffset and frameNum-berOffset attributes related to the BTS object become effective. As a result different transceivers of the same BTSE may have asynchronous frame and burst numbers.

TRUE = enabled

Validity Range



EMT1emergencyTimer1(min)

This attribute specifies after which time (minutes) the BTSE will be switched to an emer-gency configuration if a "battery backup operation" (due to "mains breakdown") occurs. The switch includes the power-down of TRX related equipment.

BS241: emerg. timer starts if first ACDC fails.

(step size 1 minute)

Validity Range

Default Value 10 minutes


EMT2emergencyTimer2(min)

This attribute specifies after which time (minutes) the BTSE will be switched to a zero carrier configuration if a switch to emergency configuration has been performed due to a "battery backup operation". The switch includes the power-down of TRX related equip-

TRUE

FALSE

0 - 1400

DN0933412 Issue 01605


e

Id:0900d805805b11b0

ment. The value 0 means the emergencyTimer2 is not valid, i.e. the BTSE will not switch to a zero carrier configuration. For other values the zero carrier configuration will be reached after the sum of the times specified in emergencyTimer1 and emergencyTimer2.

Validity Range

Default Value 0 minutes


ENTRIESentries

Validity Range Number of the requested Entries <1-65534>

Getting all Entries stored in the buffer 65535

For the upload of MIB_DATA_HW_STATES only the value 65535 is used.

For the upload of INVENTORY_DATA_TABLE, MIT and SCA the attribute has no meaning.

Default ValueNone.

Contained in the following commands: UPLBTSLOG SOFTWARE-MANAGEMENT

EQUPOSequipmentPosition

The attribute contains the room / row and rack number as 6 ASCII characters not termi-nated by a NUL character. The attribute should be set by the operator before a upload of the IDT is performed.

Validity Range

Default Value

0 - 1400

Number of entries

This attribute is used to indicate the number of the entries to be uploaded.


"010101"

606DN0933412 Issue 01


Id:0900d805805b11b0

e


ERFACCHALPDMFenableRFacchOnAnyLapdmFrame

This attribute determines whether R-FACCH (Repeated FACCH) is enabled or disabled on cell basis for the specified codec type. Attribute is implemented as a bit map consist-ing of 6 bits, one bit per codec type.

Bitmap Codec Type Codec Type Description

0/1 TCH/AFS Narrow-band Adaptive Multi-Rate Full Rate Speech

0/1 TCH/EFS Enhanced Full Rate Speech

0/1 TCH/FS GSM Full Rate Speech

0/1 TCH/WFS Wide-band Adaptive Multi-Rate Full Rate Speech

0/1 TCH/AHS Narrow-band Adaptive Multi-Rate Half Rate Speech

0/1 TCH/HS GSM Half Rate Speech

Validity Range

NOT_SET

AFS

AHS

AFS_AHS

EFS

AFS_EFS

AHS_EFS

AFS_AHS_EFS

FS

AFS_FS

AHS_FS

AFS_AHS_FS

EFS_FS

AFS_EFS_FS

DN0933412 Issue 01607


e

Id:0900d805805b11b0

AHS_EFS_FS

AFS_AHS_EFS_FS

HS

AFS_HS

AHS_HS

AFS_AHS_HS

EFS_HS

AFS_EFS_HS

AHS_EFS_HS

AFS_AHS_EFS_HS

FS_HS

AFS_FS_HS

AHS_FS_HS

AFS_AHS_FS_HS

EFS_FS_HS

AFS_EFS_FS_HS

AHS_EFS_FS_HS

AFS_AHS_EFS_FS_HS

WFS

AFS_WFS

AHS_WFS

AFS_AHS_WFS

EFS_WFS

AFS_EFS_WFS

AHS_EFS_WFS

AFS_AHS_EFS_WFS

FS_WFS

AFS_FS_WFS

AHS_FS_WFS

AFS_AHS_FS_WFS

EFS_FS_WFS

AFS_EFS_FS_WFS

AHS_EFS_FS_WFS

AFS_AHS_EFS_FS_WFS

HS_WFS

AFS_HS_WFS

608DN0933412 Issue 01


Id:0900d805805b11b0

e

Default ValueNone.


ERFACCHCMDFenableRFacchOnCmdFrames

This attribute determines whether "DL Repeated FACCH" is enabled or disabled on a cell basis for those MS not having signaled their Repeated ACCH Capability as '1'. Those types of MS include legacy MS and new MS that have to signal their Repeated ACCH Capability as "0". To enable R-FACCH on LAPDm command frames for a certain codec in the cell, the name of that codec shall be entered in a list.

Validity Range

AHS_HS_WFS

AFS_AHS_HS_WFS

EFS_HS_WFS

AFS_EFS_HS_WFS

AHS_EFS_HS_WFS

AFS_AHS_EFS_HS_WFS

FS_HS_WFS

AFS_FS_HS_WFS

AHS_FS_HS_WFS

AFS_AHS_FS_HS_WFS

EFS_FS_HS_WFS

AFS_EFS_FS_HS_WFS

AHS_EFS_FS_HS_WFS

AFS_AHS_EFS_FS_HS_WFS

NOT_SET

AFS

AHS

AFS_AHS

EFS

AFS_EFS

AHS_EFS

AFS_AHS_EFS

FS

DN0933412 Issue 01609


e

Id:0900d805805b11b0

AFS_FS

AHS_FS

AFS_AHS_FS

EFS_FS

AFS_EFS_FS

AHS_EFS_FS

AFS_AHS_EFS_FS

HS

AFS_HS

AHS_HS

AFS_AHS_HS

EFS_HS

AFS_EFS_HS

AHS_EFS_HS

AFS_AHS_EFS_HS

FS_HS

AFS_FS_HS

AHS_FS_HS

AFS_AHS_FS_HS

EFS_FS_HS

AFS_EFS_FS_HS

AHS_EFS_FS_HS

AFS_AHS_EFS_FS_HS

WFS

AFS_WFS

AHS_WFS

AFS_AHS_WFS

EFS_WFS

AFS_EFS_WFS

AHS_EFS_WFS

AFS_AHS_EFS_WFS

FS_WFS

AFS_FS_WFS

AHS_FS_WFS

AFS_AHS_FS_WFS

EFS_FS_WFS

610DN0933412 Issue 01


Id:0900d805805b11b0

e

Default ValueNone.


ERSACCHDLenableRSacchDL

The attribute is implemented as a list of values representing combinations of signaling and allowed codec types and/or signaling. This list is present in Appendix. For the binary representation 0 means that R-SACCH in DL on a per cell basis is notapplied for spec-ified speech codec type and /or signaling. Value 1 means that R-SACCH in DL is applied for specified speech codec type and/or signaling. Value 0x00 has specific meaning and should be read as R-SACCH in DL is not applied for any speech codec type.

When enabling R-SACCH feature on the BTSplus mainline, where only old CUs are created, the SET command is acked but ignored locally.

Validity Range

AFS_EFS_FS_WFS

AHS_EFS_FS_WFS

AFS_AHS_EFS_FS_WFS

HS_WFS

AFS_HS_WFS

AHS_HS_WFS

AFS_AHS_HS_WFS

EFS_HS_WFS

AFS_EFS_HS_WFS

AHS_EFS_HS_WFS

AFS_AHS_EFS_HS_WFS

FS_HS_WFS

AFS_FS_HS_WFS

AHS_FS_HS_WFS

AFS_AHS_FS_HS_WFS

EFS_FS_HS_WFS

AFS_EFS_FS_HS_WFS

AHS_EFS_FS_HS_WFS


NOT_SET

AFS

DN0933412 Issue 01611


e

Id:0900d805805b11b0

AHS

AFS_AHS

EFS

AFS_EFS

AHS_EFS

AFS_AHS_EFS

FS

AFS_FS

AHS_FS

AFS_AHS_FS

EFS_FS

AFS_EFS_FS

AHS_EFS_FS

AFS_AHS_EFS_FS

HS

AFS_HS

AHS_HS

AFS_AHS_HS

EFS_HS

AFS_EFS_HS

AHS_EFS_HS

AFS_AHS_EFS_HS

FS_HS

AFS_FS_HS

AHS_FS_HS

AFS_AHS_FS_HS

EFS_FS_HS

AFS_EFS_FS_HS

AHS_EFS_FS_HS

AFS_AHS_EFS_FS_HS

WFS

AFS_WFS

AHS_WFS

AFS_AHS_WFS

EFS_WFS

AFS_EFS_WFS

612DN0933412 Issue 01


Id:0900d805805b11b0

e

AHS_EFS_WFS

AFS_AHS_EFS_WFS

FS_WFS

AFS_FS_WFS

AHS_FS_WFS

AFS_AHS_FS_WFS

EFS_FS_WFS

AFS_EFS_FS_WFS

AHS_EFS_FS_WFS

AFS_AHS_EFS_FS_WFS

HS_WFS

AFS_HS_WFS

AHS_HS_WFS

AFS_AHS_HS_WFS

EFS_HS_WFS

AFS_EFS_HS_WFS

AHS_EFS_HS_WFS

AFS_AHS_EFS_HS_WFS

FS_HS_WFS

AFS_FS_HS_WFS

AHS_FS_HS_WFS

AFS_AHS_FS_HS_WFS

EFS_FS_HS_WFS

AFS_EFS_FS_HS_WFS

AHS_EFS_FS_HS_WFS


SIGNALING

AFS_SIGNALING

AHS_SIGNALING

AFS_AHS_SIGNALING

EFS_SIGNALING

AFS_EFS_SIGNALING

AHS_EFS_SIGNALING

AFS_AHS_EFS_SIGNALING

FS_SIGNALING

DN0933412 Issue 01613


e

Id:0900d805805b11b0

AFS_FS_SIGNALING

AHS_FS_SIGNALING

AFS_AHS_FS_SIGNALING

EFS_FS_SIGNALING

AFS_EFS_FS_SIGNALING

AHS_EFS_FS_SIGNALING

AFS_AHS_EFS_FS_SIGNALING

HS_SIGNALING

AFS_HS_SIGNALING

AHS_HS_SIGNALING

AFS_AHS_HS_SIGNALING

EFS_HS_SIGNALING

AFS_EFS_HS_SIGNALING

AHS_EFS_HS_SIGNALING

AFS_AHS_EFS_HS_SIGNALING

FS_HS_SIGNALING

AFS_FS_HS_SIGNALING

AHS_FS_HS_SIGNALING

AFS_AHS_FS_HS_SIGNALING

EFS_FS_HS_SIGNALING

AFS_EFS_FS_HS_SIGNALING

AHS_EFS_FS_HS_SIGNALING

AFS_AHS_EFS_FS_HS_SIGNALING

WFS_SIGNALING

AFS_WFS_SIGNALING

AHS_WFS_SIGNALING

AFS_AHS_WFS_SIGNALING

EFS_WFS_SIGNALING

614DN0933412 Issue 01


Id:0900d805805b11b0

e

AFS_EFS_WFS_SIGNALING

AHS_EFS_WFS_SIGNALING

AFS_AHS_EFS_WFS_SIGNALING

FS_WFS_SIGNALING

AFS_FS_WFS_SIGNALING

AHS_FS_WFS_SIGNALING

AFS_AHS_FS_WFS_SIGNALING

EFS_FS_WFS_SIGNALING

AFS_EFS_FS_WFS_SIGNALING

AHS_EFS_FS_WFS_SIGNALING

AFS_AHS_EFS_FS_WFS_SIGNALING

HS_WFS_SIGNALING

AFS_HS_WFS_SIGNALING

AHS_HS_WFS_SIGNALING

AFS_AHS_HS_WFS_SIGNALING

EFS_HS_WFS_SIGNALING

AFS_EFS_HS_WFS_SIGNALING

AHS_EFS_HS_WFS_SIGNALING

AFS_AHS_EFS_HS_WFS_SIGNALING

FS_HS_WFS_SIGNALING

AFS_FS_HS_WFS_SIGNALING

AHS_FS_HS_WFS_SIGNALING

DN0933412 Issue 01615


e

Id:0900d805805b11b0

Default ValueNone.


ERSACCHULenableRSacchUL

The attribute is implemented as a list of values representing combinations of signalin-gand allowed codec types and/or signaling. This list is present in Appendix. For the binary representation “0” means that R-SACCH in DL on a per cell basis is not applied for specified speech codec type and /or signaling. Value “1” means that RSACCH in DL is applied for specified speech codec type and/or signaling. Value 0x00 has specific meaning and should be read as R-SACCH in DL is not applied for any speech codec type.This attribute is used to enable the R-SACCH in UL feature on a per cell basis for different codec types and /or signaling only for MS with R-ACCH_CAP = 1.

When enabling the R-SACCH feature on the BTSplus mainline, where only old CUs are created, the SET command s acked but ignored locally.

Validity Range

AFS_AHS_FS_HS_WFS_SIGNALING

EFS_FS_HS_WFS_SIGNALING

AFS_EFS_FS_HS_WFS_SIGNALING

AHS_EFS_FS_HS_WFS_SIGNALING

AFS_AHS_EFS_FS_HS_WFS_SIGNALING

NOT_SET

AFS

AHS

AFS_AHS

EFS

AFS_EFS

AHS_EFS

AFS_AHS_EFS

FS

AFS_FS

AHS_FS

616DN0933412 Issue 01


Id:0900d805805b11b0

e

AFS_AHS_FS

EFS_FS

AFS_EFS_FS

AHS_EFS_FS

AFS_AHS_EFS_FS

HS

AFS_HS

AHS_HS

AFS_AHS_HS

EFS_HS

AFS_EFS_HS

AHS_EFS_HS

AFS_AHS_EFS_HS

FS_HS

AFS_FS_HS

AHS_FS_HS

AFS_AHS_FS_HS

EFS_FS_HS

AFS_EFS_FS_HS

AHS_EFS_FS_HS

AFS_AHS_EFS_FS_HS

WFS

AFS_WFS

AHS_WFS

AFS_AHS_WFS

EFS_WFS

AFS_EFS_WFS

AHS_EFS_WFS

AFS_AHS_EFS_WFS

FS_WFS

AFS_FS_WFS

AHS_FS_WFS

AFS_AHS_FS_WFS

EFS_FS_WFS

AFS_EFS_FS_WFS

AHS_EFS_FS_WFS

DN0933412 Issue 01617


e

Id:0900d805805b11b0

AFS_AHS_EFS_FS_WFS

HS_WFS

AFS_HS_WFS

AHS_HS_WFS

AFS_AHS_HS_WFS

EFS_HS_WFS

AFS_EFS_HS_WFS

AHS_EFS_HS_WFS

AFS_AHS_EFS_HS_WFS

FS_HS_WFS

AFS_FS_HS_WFS

AHS_FS_HS_WFS

AFS_AHS_FS_HS_WFS

EFS_FS_HS_WFS

AFS_EFS_FS_HS_WFS

AHS_EFS_FS_HS_WFS


SIGNALING

AFS_SIGNALING

AHS_SIGNALING

AFS_AHS_SIGNALING

EFS_SIGNALING

AFS_EFS_SIGNALING

AHS_EFS_SIGNALING

AFS_AHS_EFS_SIGNALING

FS_SIGNALING

AFS_FS_SIGNALING

AHS_FS_SIGNALING

AFS_AHS_FS_SIGNALING

EFS_FS_SIGNALING

AFS_EFS_FS_SIGNALING

AHS_EFS_FS_SIGNALING

AFS_AHS_EFS_FS_SIGNALING

618DN0933412 Issue 01


Id:0900d805805b11b0

e

HS_SIGNALING

AFS_HS_SIGNALING

AHS_HS_SIGNALING

AFS_AHS_HS_SIGNALING

EFS_HS_SIGNALING

AFS_EFS_HS_SIGNALING

AHS_EFS_HS_SIGNALING

AFS_AHS_EFS_HS_SIGNALING

FS_HS_SIGNALING

AFS_FS_HS_SIGNALING

AHS_FS_HS_SIGNALING

AFS_AHS_FS_HS_SIGNALING

EFS_FS_HS_SIGNALING

AFS_EFS_FS_HS_SIGNALING

AHS_EFS_FS_HS_SIGNALING

AFS_AHS_EFS_FS_HS_SIGNALING

WFS_SIGNALING

AFS_WFS_SIGNALING

AHS_WFS_SIGNALING

AFS_AHS_WFS_SIGNALING

EFS_WFS_SIGNALING

AFS_EFS_WFS_SIGNALING

AHS_EFS_WFS_SIGNALING

AFS_AHS_EFS_WFS_SIGNALING

FS_WFS_SIGNALING

AFS_FS_WFS_SIGNALING

DN0933412 Issue 01619


e

Id:0900d805805b11b0

AHS_FS_WFS_SIGNALING

AFS_AHS_FS_WFS_SIGNALING

EFS_FS_WFS_SIGNALING

AFS_EFS_FS_WFS_SIGNALING

AHS_EFS_FS_WFS_SIGNALING

AFS_AHS_EFS_FS_WFS_SIGNALING

HS_WFS_SIGNALING

AFS_HS_WFS_SIGNALING

AHS_HS_WFS_SIGNALING

AFS_AHS_HS_WFS_SIGNALING

EFS_HS_WFS_SIGNALING

AFS_EFS_HS_WFS_SIGNALING

AHS_EFS_HS_WFS_SIGNALING

AFS_AHS_EFS_HS_WFS_SIGNALING

FS_HS_WFS_SIGNALING

AFS_FS_HS_WFS_SIGNALING

AHS_FS_HS_WFS_SIGNALING

AFS_AHS_FS_HS_WFS_SIGNALING

EFS_FS_HS_WFS_SIGNALING

AFS_EFS_FS_HS_WFS_SIGNALING

AHS_EFS_FS_HS_WFS_SIGNALING

AFS_AHS_EFS_FS_HS_WFS_SIGNALING

620DN0933412 Issue 01


Id:0900d805805b11b0

e

Default ValueNone.


ETOPenableTOP

This attribute determines whether TOP(Temporary Overpower) is enabled or disabled on cell basis for the specified codec type. Attribute is implemented as a bit map consist-ing of 6 bits, one bit per codec type.

Validity Range

Bitmap

Codec Type Codec Type Description

0/1 TCH/AFS Narrow-band Adaptive Multi-Rate Full Rate Speech

0/1 TCH/EFS Enhanced Full Rate Speech

0/1 TCH/FS GSM Full Rate Speech

0/1 TCH/WFS Wide-band Adaptive Multi-Rate Full Rate Speech

0/1 TCH/AHS Narrow-band Adaptive Multi-Rate Half Rate Speech

0/1 TCH/HS GSM Half Rate Speech

NOT_SET

AFS

AHS

AFS_AHS

EFS

AFS_EFS

AHS_EFS

AFS_AHS_EFS

FS

AFS_FS

AHS_FS

AFS_AHS_FS

EFS_FS

AFS_EFS_FS

AHS_EFS_FS

AFS_AHS_EFS_FS

DN0933412 Issue 01621


e

Id:0900d805805b11b0

HS

AFS_HS

AHS_HS

AFS_AHS_HS

EFS_HS

AFS_EFS_HS

AHS_EFS_HS

AFS_AHS_EFS_HS

FS_HS

AFS_FS_HS

AHS_FS_HS

AFS_AHS_FS_HS

EFS_FS_HS

AFS_EFS_FS_HS

AHS_EFS_FS_HS

AFS_AHS_EFS_FS_HS

WFS

AFS_WFS

AHS_WFS

AFS_AHS_WFS

EFS_WFS

AFS_EFS_WFS

AHS_EFS_WFS

AFS_AHS_EFS_WFS

FS_WFS

AFS_FS_WFS

AHS_FS_WFS

AFS_AHS_FS_WFS

EFS_FS_WFS

AFS_EFS_FS_WFS

AHS_EFS_FS_WFS

AFS_AHS_EFS_FS_WFS

HS_WFS

AFS_HS_WFS

AHS_HS_WFS

AFS_AHS_HS_WFS

622DN0933412 Issue 01


Id:0900d805805b11b0

e

Default ValueNone.


ETXDIVTSenableTxDivTimeShift

The attribute indicates whether Tx Diversity Time Shift is enabled or disabled for a BTSplus mainline. As a consequence all TRXs of the cell will operate in "double-power/half capacity" Mode (called Coverage Mode) or in "normal-power/normal capac-ity" Mode (called Capacity Mode).

The value 'TRUE' means that all CUs or FCUTRs in the a cell operate as CU pairs or FCUTR pairs in a master slave mode. Pairs are defined as follows (k=0, 1, 2, etc.):

- A CU pair consists of the master CU (instance 2k) and the slave CU (instance 2k+1)

- A FCUTR pair consists of the master FCUTR (instance 2k) and the slave FCUTR (instance 2k+1).

The two members of each pair should be wired to different antennas of the same cell otherwise the combining loss would nullify the additional gain of the coverage mode. A change of the attribute becomes effective after reconfiguration of the cell handled inter-nally by the BTSE and causes a reset of the related CU or FCUMAIN objects. The BSC takes care that the BTS object is locked whenever the value of the attribute is changed.

Validity Range

EFS_HS_WFS

AFS_EFS_HS_WFS

AHS_EFS_HS_WFS

AFS_AHS_EFS_HS_WFS

FS_HS_WFS

AFS_FS_HS_WFS

AHS_FS_HS_WFS

AFS_AHS_FS_HS_WFS

EFS_FS_HS_WFS

AFS_EFS_FS_HS_WFS

AHS_EFS_FS_HS_WFS


TRUE

FALSE

DN0933412 Issue 01623


e

Id:0900d805805b11b0



EVTYPeventType

This attribute specifies the type of failure event alarm.

Validity Range

Default ValueNone.

Contained in the following commands: GETACTIVEALARMS BTSEP

EXCDISTexcessiveDistance(km)

This attribute indicates the distance limit to be used for call release when the distance between the MS and the BTSplus mainline exceeds the excessiveDistance. Value indi-cating more 35 km are valid only for extended cells. A change of the attribute becomes effective in the next SACCH multiframe.

Validity Range

Default Value 100 Km


COMMUNICATION_FAILURE_EVENT

QUAL_SERVICE_FAILURE_EVENT

PROCESSING_FAILURE_EVENT

EQUIPMENT_FAILURE_EVENT

ENVIRONMENTAL_FAILURE_EVENT

1 - 100

624DN0933412 Issue 01


Id:0900d805805b11b0

e

EXTMODEextendedMode

This attribute indicates whether a channel instance operates in the extended mode (usage of two radio timeslots) which is needed for extended cells. The value TRUE is allowed only for even channel instances. Before an even channel instance N can be created with the value TRUE for the extendedMode it must be guaranteed that channel instance N+1 does not exist.

Validity Range

Default Value FALSE


TRUE

FALSE

DN0933412 Issue 01625


f

Id:0900d805805ca0eb

f

F6FWIDficom6FwId

This attribute provides information of the “file ID” and the “FW version” that is active on a FICOM6 board.

Validity Range

Default ValueNone.

Contained in the following commands:GET F6VSWRP

FACCHQfacchQual

This attribute defines the number of FACCH (stealing flags minus 1) to be received for detecting a FACCH frame.

(step size 1 FACCH frame)

Validity Range

Default Value 5

Contained in the following commands:GET BTS

FACHBTfachBusyThreshold(dBm)

This attribute defines a threshold for the received signal level during handover proce-dure when mobile station transmits HANDOVER ACCESS or ASCI uplink access burst message on the FACCH (Fast Associated Control Channel). A signal exceeding this threshold is interpreted as a busy FACCH.

Validity Range

Default ValueNone.


0 - 7

<ANY>

626DN0933412 Issue 01


Id:0900d805805ca0eb

f


FBANDfrequencyBand

The attribute specifies the frequency band of the BCOM. It is highly recommended to set this attribute to the correct value in order to ensure software checks for a consistent wiring especially in case of dual band configurations.

The user must configure the correct value because the system cannot check if the value fits to the equipped hardware.

Validity Range

Default Value

Contained in the following commands:CREATE BCOM, GET BCOM, SET BCOM

FCUMAINWIRINGfcumainWiring

The attribute describes the Tx and Rx wiring of the FlexCU board to the combining equipment. The attribute identifier cannot be present in the listOfRequiredAttributes together with other attribute identifiers and it is not sent by the BTSE object if a "Get FCUMAIN" is done without the information element listOfRequiredAttributes.

The attribute is not visible at the RC.

Validity Range choice tag

1 = 'variable'

tx0WiringPresence:

1 = the next 4 bytes contain object class & instance of the object wired to the TX output 0

0 = object class & instance don't follow

rxNWiringPresence: Octect position is variable

Gsm850

Gsm900

Dcs1800

Pcs1900

NotSet

NotSet

DN0933412 Issue 01627


f

Id:0900d805805ca0eb

1 = the next 4 bytes contain object class & instance of the object wired to the RX output N


rxDWiringPresence: Octect position is variable

1 = the next 4 bytes contain object class & instance of the object wired to the RX output D


tx1WiringPresence: Octect position is variable

1 = the next 4 bytes contain object class & instance of the object wired to the TX output 1


rxN1WiringPresence: Octect position is variable

1 = the next 4 bytes contain object class & instance of the object wired to the RX output N1


rxD1WiringPresence: Octect position is variable

1 = the next 4 bytes contain object class & instance of the object wired to the RX output D1


Default ValueNone.

Contained in the following commands:GET FCUMAIN WIRING

FCUMODEfcuMode

This attribute specifies in which mode a FlexCU board shall operate.

A FlexCU in 'singleCUMode' has the following characteristics:

• Does not allow the creation of the odd instance of the FCUTRobject • Does not support the feature 'TX diversity time shift'. If thevalue of the attribute

'enableTxDivTimeShift' is 'TRUE', anappropriate FCUMAIN alarm is emitted and the FCUMAINand FCUTR instance are set to disabled

• Supports only 1 TRX with up to 4 RX branches

A FlexCU board in 'doubleCUMode' supports up to 2 TRX instances:

• Support of two TRX instances ('enableTxDivTimeShift' is'FALSE' • Support of 1 TRX with 'TX diversity time shift' ('enableTxDiv-TimeShift' is 'TRUE')

628DN0933412 Issue 01


Id:0900d805805ca0eb

f

Validity Range

Default Value doubleCUMode

Contained in the following commands:CREATE FCUMAIN, GET FCUMAIN

FILEfile

This attribute specifies the file within the destinationDirectory on the LMT Evolution hard disk where the alarm buffer sw will be copied (UPLBTSLOG) or where the IDT file will be copied (UPLLIDF).

Validity Range

Default ValueNone.

Contained in the following commands:UPLBTSLOG SOFTWARE-MANAGEMENT, UPLLIDF REMINV

FILEFWVfwVersion

This attribute states the name and version of the fwImage file. The file is transferred to the dedicated board to perform the FW upgrade.

Validity Range

Default ValueNone.

Contained in the following commands:FWUPGRADE BTSM

FILEIDfileId

singleCUMode

doubleCUMode



DN0933412 Issue 01629


f

Id:0900d805805ca0eb

g This value may only be used in conjunction with the FileVersion "00 " (indicating the destination "Easy-Disk").

Validity Range

Default ValueNone.

Contained in the following commands:ACTIVATE BTSM, ACTIVATE_DELAYED BTSM, FWUPGRADE BTSM

The FileId is a parameter used within the SW download procedures and not of the type 'GET'. The corresponding attribute is swLoadCur-rentFileId and is related only to the swLoad-header file. All charac-ters of the ASCII string are to be in upper case. However, the SW parts in the BTSE handling the file Id are to be case tolerant.

This attribute is a string of 12 alphanumerical characters with the fol-lowing format:

ASCII String for: For download of test SW from local LMT Evo-lution acc.

For download of boot SW from local LMT Evolution acc.

for swLoad-header file

HScnv-vss.SWL

HSTTv-vss.SWL

HSBBv-vss.SWL

for the VAM table file

VScnv-vss.VAM

VSTTv-vss.VAM

VSBBv-vss.VAM

for swImages BTSrrrhh.SWI BTTrrrhh.SWI BTBrrrhh.SWI

for PID files PSBBvvss.PID

hh, cn, vv and ss are identical with the corresponding parts of the FILESWV - please note that thevalues of 'hh' in the FileId of swImages do not reflect the BTSplus mainline family but reflect the HW version of the board. (eg.BTSBIX01.SWI is for the CU and the file BTSBIX07.SWI is for newer CU-variants, eg. the ECU).

The 3 characters used for 'rrr' identify different units:

rrr BS240, BS241, BS240XL,

BS240SR,BS241SR, BS240XLSR,

BS40, BS40II, BS41, BS82, BS82II

BCX for COBA

BIX for CU

LMX for LMU (only BS240, BS241, BS240XL)


630DN0933412 Issue 01


Id:0900d805805ca0eb

f

FILESWVfileVersion

The File Version is a parameter used within the SW download procedures and not of the type 'GET'. The corresponding attribute is swLoadCurrentVersion and is coded identical as File Version. However the allowed values for 'hh' are different because wLoadCur-rentVersion is related only to the swLoad-header file.

Validity Range ASCII string: cn-hh-vv-ii-ss-pp_yy-mm-dd, where:


01 = Ciphering A5.0 + A5.1 + A5.2

02 = Ciphering A5.0 + A5.2 12

03 = Ciphering A5.0 only



02 = BR 2.0

03 = BR 2.1

04 = BR 3.0

07 = BR 3.7

08,09 = BR 4.0

10 = BR 4.5

11 = BR 5.0

12 = BR 5.5

13 = BR 6.0

14 = BR 6.01

15 = BR 6.02

16 = BR 7.0 / 7.01

17 = BR 8.0

18 = BR 9.0

19 = BR 10.0

ii: Version part (sub-feature package code). This field assumes the values: 21 (BTSplus mainline), 26 (BTSplus basic), 25 (BTSplus eMicro)

ss : Version part (actual state)

pp: Patch version (usually 00)

yy-mm-dd: production date (optional)

Notes:

1) For the SWL file of the downloadable test SW of BTSplus mainline, basic and eMicro, the following special value is used:

cn = TT

DN0933412 Issue 01631


f

Id:0900d805805ca0eb

3) For the SWL file of the downloadable boot SW of BTSplus mainline, basic and eMicro, the following special value is used:

cn = BB

In addition to the ASCII string described above values, the following values are allowed for generic filedownload.

"00" ....Destination ID for Easy-Disk (remaining 24 characters are filled with blanks)

"01" ....Destination ID for Light-Disk Partition 1 (reserved)



Default ValueNone.

Contained in the following commands:ACTIVATE BTSM, ACTIVATE_DELAYED BTSM

FILETYPEFileType

This attribute specifies the file type to be transferred.

Validity Range

Default ValueNone.

Contained in the following commands:UPLBTSLOG SOFTWARE-MANAGEMENT

FPGAFWVERfpgaFwVer

This attribute gives information on the FPGA FW images that are contained in the board's flash prom together with an indication of the “active” version.

The attribute identifier cannot be present in the listOfRequiredAttributes together with other attribute identifiers and it is not sent by the BTSE obejct if a "Get FCUMAIN"/"Get CU"is done without the information element listOfRequiredAttributes.

Validity Range

ALARM_BUFFER

TRACE_FILE

1 to 4 items of

FPGAfwVer 39..39 characters string

activeFlag active

632DN0933412 Issue 01


Id:0900d805805ca0eb

f

Default ValueNone.

Contained in the following commands:GET CU, GET CU FWID, GET FCUMAIN, GET FCUMAIN FWID

FRANOFFSframeNumberOffset

This attribute allows to adjust the TDMA frame number offset for a cell. Equal frame and burst number offsets result in synchronized TDMA frames and synchronized TDMA frame numbers.

This attribute is only meaningful enableInterSiteSync is set to 'TRUE'.

Validity Range

Default Value 0


FWVERfirmwareVersion

This attribute provides the firmware version stored on the ETHCON board.

Validity Range

Default ValueNone.

Contained in the following commands:GET ETHCON

stored

0 - 255

0 - 255

<NULL>

DN0933412 Issue 01633


g

Id:0900d805805b2913

g

GN<x>gain0(dBi*1<x>)

Attribute data provided by the TMA. This attribute shows the gain of the operating band<X> in (dBi * 10).

Validity Range

Default ValueNone.


GNAgainAdjust(dB)

This attribute represents the cable loss measured during installation and entered by the operator at the DIP switch related to a DILNA or DULNA. So the attribute allows the operator to 'GET' the actual DIP switch setting. In 'AMCO_MODE' (attribute lnaMode) the value 0 is returned, in MUCO_MODE (attribute lnaMode) the value 0..7 can be returned. If the value 7 is returned this means that the operator has performed a DIP switch setting at the DIAMCO or DUAMCO/FDUAMCO board which isn't allowed.

Validity RangeIn commands GET DILNA, GET DULNA, GET F6LNA:

0 - 255

<NULL>

N_00

N_01

N_02

N_03

N_04

N_05

N_06

N_07

N_08

N_09

N_10

N_11

N_12

634DN0933412 Issue 01


Id:0900d805805b2913

g

In commands GET DILNA, GET DULNA:

Default ValueNone.

Contained in the following commands: GET DILNA, GET DULNA, GET F6LNA

GNADBgainAdjustDb

This attribute sets the attenuation value of a MFDUAMCO RX amplifier chain in theda-tabase. The value is aligned with the combiner if a MFDUAMCO is equipped. If the DIP value is set, the MFDUAMCO DIP switch setting is used. The attribute is meaningless if an old DUAMCO or FDUAMCO is equipped. Nevertheless the value is stored in the database and used if a MFDUAMCO is equipped later on

Validity Range

ILLEGAL_VALUE

UNKNOWN

<NULL>

N_00

N_01

N_02

N_03

N_04

N_05

N_06

N_07

N_08

N_09

N_10

N_11

N_12

ILLEGAL_VALUE

UNKNOWN

N_00

N_01

N_02

N_03

N_04

DN0933412 Issue 01635


g

Id:0900d805805b2913

Default Value

Contained in the following commands: CREATE DULNA, CREATE F6LNA, GET DULNA, GET F6LNA, SET DULNA, SET F6LNA

GNRgainResolution(dB*4)


Validity Range

Default ValueNone.


GSMTIMEgsmTime

This attribute represents the current frame number of the radio interface. It is counted as a binary presentation 'frame number modulus 42432'.

Validity Range

Default ValueNone.

N_05

N_06

N_07

N_08

N_09

N_10

N_11

N_12

DIP

DIP

0 - 255

<NULL>

0 - 42432

<NULL>

636DN0933412 Issue 01


Id:0900d805805b2913

g


GTWADRV4gatewayAddressIPv4

This attribute specifies the IPv4 address of the default IP gateway including the subnet-work information. The address is input in the usual IPv4 format. The subnetwork is added in CIDR notation.

Example for CIDR notation:

192.168.2.7/24 corresponds to the host address 192.168.2.7 with subnet mask 255.255.255.0

g Value “0.0.0.0/0” and “0.0.0.0” are intrepreted as attribute not set.

This attribute is visible and configurable only in phase 2 in LMT Evolution local.

Validity Range

Default Value



""

DN0933412 Issue 01637


h

Id:0900d805805b2915

h

HOPMODEhoppingMode

This attribute specifies whether baseband hopping or synthesizer hopping is to be done. This attribute can be changed only when hopping is switched off (Attribute btsIsHop-ping). A prerequisite for synthesizer hopping is that the corresponding HW (TPU + PA) is installed.

Validity Range

Default ValueNone.


HSNhoppingSequenceNumber

This attribute determines the order in which the allocated frequencies are used.

This parameter is used in the frequency hopping algorithm. Any instance of the CHAN object, which is not assigned to any explicit frequency hopping system instance should contain the default value 0 for this attribute.

Changing this attribute is allowed only if there is no hopping (i.e. attribute btsIsHopping = FALSE).

Validity Range

Default Value 0


BBHOP

SYNHOP

0 - 63

638DN0933412 Issue 01


Id:0900d805805b2917

i

i

INSDinstallDate


Validity Range

Default ValueNone.


INSIDinstallerId


Validity Range

Default ValueNone.


INTAVEPARintaveParameter

This attribute contains the measurement and averaging period for the interference clas-sification of idle traffic channels in units of SACCH multiframes.

Validity Range

Default Value 31




1 - 31

DN0933412 Issue 01639


i

Id:0900d805805b2917

INTCLASSenableInterferenceClass

This attribute indicated whether the interference classification of idle traffic channels is enabled or disabled.

A change of the attribute becomes effective in the next SACCH multiframe.

A consequence of the value 'disabled' is that no 'RF resource indication' messages are sent to the Flexi BSC product family.

(TRUE = enabled)

Validity Range

Default Value TRUE (enabled)


INTINFinterfaceInformation

This attribute is used to configure one of the envaBTSE instances with the following information:

positive logic with external detector

or

negative logic with external detector

Validity Range

Default ValueNone.

Contained in the following commands: CREATE ENVABTSE, GET ENVABTSE, SET ENVABTSE

INTLVBNDinterferenceLevelBoundaries

This attribute defines the boundary limits of five interference bands for the unallocated timeslots.

The Flexi BSC product family maps the averaged interference level measurements into these five bands.

FALSE

TRUE

low

high

640DN0933412 Issue 01


Id:0900d805805b2917

i

A change of the attribute becomes effective in the next SACCH multiframe.

The validity range of the attribute is 0 ... 63 (less than -110 dBm...more than -48 dBm) in steps of 1 dBm.

Validity Range

Default Value intThrBou1 : 2

intThsBou2 : 6

intThsBou3 : 12

intThsBou4 : 22

intThsBou5 : 63


IPADRipAddress

This attribute specifies the IP address of the host which shall respond to the ping request. The address is input in the usual IPv4.

The length may vary from minimum length (7 ) -> 1.3.6.9 up to maximum length (15) -> 192.120. 110.124

Validity Range

Default ValueNone.

Contained in the following commands: PING BTSEP

intThrBou1 0 - 63

intThsBou2 0 - 63

intThsBou3 0 - 63

intThsBou4 0 - 63

intThsBou5 0 - 63


DN0933412 Issue 01641


l

Id:0900d805805b2919

l

L1CTRLTSlayer1ControlTs

This attribute defines in case of a LOOP configuration which dedicated layer 1 16kbit/s subchannel is to be used for the layer 1 supervision. In a star or multidrop configuration the given time slot is used for a loopback supervision.

Below are indicated some more detailed information about the attribute validity range:

• TimeSlotNumber for Time Slot in 2 Mb/s link:validity range: 1..31 (if dedicated 16k subchannel is used fo supervision

• TimeSlotNumber for Time Slot in 1,5 Mb/s link:validity range: 1..21 (if dedicated 16k subchannel is used fo supervision

• SubSlotNumber for SubSlot within time slotvalidity range: 0..3 (if dedicated 16k subchannel is used fo supervision

Validity Range

Default Value TimeSlotNumber:

0 (deactivated)

SubSlotNumber:

octet #2 = 3

octet #4 = 0


L1PTlayer1ProtocolType

"This attribute defines the type of protocol that is used on layer 1 of the Abis-line. One of the following values has to be set by the operator at installation time for a PCM30 line:

The value 'pcm30crc4' means that a cyclic redundancy check (CRC4) is performed, the value 'pcm30noncrc4doubleframe' means that CRC4 is not performed and that the line remains in Doubleframe mode.

The value 'pcm24sf' means the 'superframe' format is used.

The value 'pcm24crc6esf' means the 'extended superframe' format is used and a cyclic redundancy check (CRC6) is performed.

TSL 0 - 31

SSL 0 - 3

642DN0933412 Issue 01


Id:0900d805805b2919

l

Validity Range

Default ValueNone.

Contained in the following commands: CREATE BPORT, GET BPORT

L1RATlayer1RemoteAlarmType

This attribute defines how the signalling of a remote alarm is done for both detection and transmission. It must be set accordingly in the remote environment. 'Special Bit Robbing' is allowed only for PCM24 and means that a special bit (bit 2) is used for signalling a remote alarm.

Validity Range

Default Value ProtocolSignalling


LAPDCHlapdChannel

This attribute exists for only for LAPDLE. It identifies the BPortNumber, Timeslot Number and Subslot Number allocated on the Abis-interface for the LAPD signaling links to the Flexi BSC product family.

Notes:

The BPortNumber (BPORT) field assumes the following values:

• 00-07 for hh-ii = 04-21 (enums: BPORT0, BPORT1, ..., BPORT7) *) • 00 for hh-ii = 04-25 (enum: BPORT0) • 00-03 for hh-ii = 04-26 (enum: BPORT0, …, BPORT3)

*) for BS82II only BPortNumber 00-03 value is allowed.

- the TSL field has the following ranges:

pcm30crc4

pcm30noncrc4doubleframe

pcm24sf

pcm24crc6esf

ProtocolSignalling

SpecialBitRobbing

DN0933412 Issue 01643


l

Id:0900d805805b2919

• 01-1F for PCM30 • 01-18 for PCM24

- the SSL field has the following bit associations:

• 0for bit 7 and 6 on LMT Evolution displayed "SSL0_16KB" • 1for bit 5 and 4 on LMT Evolution displayed "SSL1_16KB" • 2for bit 3 and 2 on LMT Evolution displayed "SSL2_16KB" • 3for bit 1 and 0 on LMT Evolution displayed "SSL3_16KB" • 0x10 for bit 7, 6, 5 and 4 on LMT Evolution displayed "SSL0_32KB" • 0x11for bit 3, 2, 1 and 0 on LMT Evolution displayed "SSL1_32KB" • 0xFF 64 kbit/sec on LMT Evolution displayed "FULL_64KB"

Validity Range

Default ValueNone.

Contained in the following commands: CREATE LAPDLE, GET LAPDLE

LAPDOVLTlapdOverloadTimer(sec)

The attribute defines the time between two subsequent 'LAPD overload' messages (in seconds), as long as any radio signalling LAPD link on Abis is overloaded.

The validity range is indicated in seconds.

Validity Range

BPORT BPORT0

BPORT1

...

BPORT7

TSL 1 - 18

SSL SSL0_16KB

SSL1_16KB

SSL2_16KB

SSL3_16KB

SSL0_32KB

SSL1_32KB

FULL_64KB

lapdOverloadTimer 1 - 60

644DN0933412 Issue 01


Id:0900d805805b2919

l

Default ValuelapdOverloadTimer: 1 second

lapdUsageOverloadTimer: 1 second

Contained in the following commands: GET BTSM OVERLOAD

LAPDOVLTHlapdOverloadThresholds(%)

Validity Range

lapdUsageOver-loadTimer

0.5 - 10.0

The thresholds give the percentage of the LAPD transmit queue filling, allowed range is 10 to 100 (decimal):

a) first level upper threshold : when exceeded sending of mea-surement report messages on Abis will be suspended.

b) second level upper threshold : when exceeded on any of the LAPD links the periodical sending 'LAPD overload' message is started.

c) first level lower threshold: when filling level falls below, sending of measurement reports on Abis will resume.

d) second level lower threshold : when filling level falls below, sending of 'LAPD overload' indication will be stopped.

For thresholds the following restriction is valid:

- first level lower threshold < first level upper threshold =< second level lower threshold < second level upper threshold

Default Value:

50 first level upper threshold

40 first level lower threshold

90 second level upper threshold

80 second level lower threshold

firstLevUp-perThreshold

10 - 100

firstLevLow-erThreshold

10 - 100

firstLevReduction-Step

10 - 100

secLevUp-perThreshold

10 - 100

DN0933412 Issue 01645


l

Id:0900d805805b2919

Default ValueNone.

Contained in the following commands: GET BTSM OVERLOAD

LCONFlineConfiguration

Validity Range

Default ValueNone.


LIMPlineImpedance

secLevLow-erThreshold

10 - 100

This attribute defines the configuration of the BTSplus mainlines on the Abis interface.

Notes:

a) 'star' means either a BTSE which is directly connected to the Flexi BSC product family or the last BTSplus mainline of a multidrop chain.

b) In general 'star' is allowed only for even BPORT instances. Only for hh-ii = 04-01 'star' may be used also for odd BPORT instances (2k+1, k=0, 1, 2, 3) - in this case the related even BPORT instance (2k, k=0, 1, 2, 3) must be configured as 'star' too.

c) more information can be found in the document 'Configuration Rules for BTSE Abis Line Interface'.

star

multidrop

loop

starX

This attribute defines the impedance setting of the related Abis (BPort) interface.

Notes:

646DN0933412 Issue 01


Id:0900d805805b2919

l

Validity Range

Default Value accDIP (fully correct for COBA2P8 internal used by subsystem DM)


LMTLSESSlmtLogonSession

This attribute indicates if a LMT Evolution session is active or not.

Validity Range

a) On a COBA2P8 the adjustment of the impedance is done by DIP switches. So the only acceptedvalue on a COBA2P8 is 'AccDIP'.

b) On a COBA4P12 the adjustment is performed by software. So the value must be 'Imp100or120Ohm' or 'Imp75Ohm'.

c) If a value which is not allowed is entered the BTSE SW will answer with a NACK.

d) The initial value 02 will be changed by BTSE subsystem A1 to 00 in case of COBA4P12."

e) In case of backup from COBA2P8 to COBA4P12 it is handled "fault tolerantly", SET message will be acknowledged and alarm will be issued. A1 sub-system will change value of the attribute to appropriate default value 00 automatically.

Imp100or120Ohm

Imp75Ohm

accDIP

NOT_ACTIVE

ACTIVE

DN0933412 Issue 01647


l

Id:0900d805805b2919

Default Value NOT_ACTIVE

Contained in the following commands: GET BTSEP NOSWL

LMTLTIMElmtLogonTime

This attribute specifies the date and time of the logon attempt. It is set by the BTSE when the T- interface message 'Logon' from the local LMT Evolution is received.

Validity Range

Default Value year : 1995

month : 8

day : 1

hour : 0

minute : 0

second : 0


LMTUALlmtUserAccessLevel

This attribute indicates the LMT Evolution user profile.

Validity Range

year 1990 - 2037

month 1 - 12

day 1 - 31

hour 0 - 23

minute 0 - 59

second 0 - 59

offsetHour -12 - 14

offsetMinute 0 - 45

READ_ONLY

COMMAND

READ_WRITE

648DN0933412 Issue 01


Id:0900d805805b2919

l

Default Value NOT_DEFINED


LMTUNAMElmtUserName

Validity Range

Default Value octet 3-10 = 0, octet 2 = 7


LNAMDBlnaModeDb

new information

Validity Range

Default Value

ACCESS_CONTROL_MANAGEMENT

SECURITY_OPERATOR

NOT_DEFINED

The user name consists of a character string containing maximal 7 characters for the user name. The user name must be terminated by a NUL character value (last byte of the user name). The content of this attribute is identical with the content of the information element 'user identification' of the T-interface message 'Logon'.

Default Value: octet 3-10 = 00, octet 2 = 07


MUCO_MODE

AMCO_MODE

DIP

DIP

DN0933412 Issue 01649


l

Id:0900d805805b2919

Contained in the following commands: CREATE DULNA, CREATE F6LNA, GET DULNA, GET F6LNA, SET DULNA, SET F6LNA

LNAMODElnaMode

This attribute indicates the current amplification mode of a DUAMCO_LNA or DIAMCO_LNA. (The information is derived from the setting of the DIP switch 'mode switch' and from the actual situation e.g. regarding the TMA) This attribute is 'readonly'.

Validity Range

Default Value UNKNOWN

Contained in the following commands: GET DILNA, GET DULNA, GET F6LNA

LNAPREDlnaPredecessor

This attribute is optional and indicates the wiring of the RX input of a DUAMCO_LNA/ DIAMCO_LNA to the RX cascade output (RXCA) of another DUAMCO_LNA/DIAMCO_LNA or to the RX output of a TMA.

From SW point of view the FDUAMCO is considered just as an HW variant of the DUAMCO, so an extra term like 'FDUAMCO_LNA' is not introduced.

If there is no wiring the operator must not provide a value for the attribute.

If there is no wiring and the operator enters a value for the attribute he can correct the error only by a deletion of the object and a re-creation of the object.

Detailed information about the validity range:

predecessor (Type):

DULNA (not allowed for BS82II)

DILNA (not allowed for BS82II)

TMA

predecessor (Rack):

RACK0

RACK1

RACK2

MUCO_MODE

AMCO_MODE

UNKNOWN

650DN0933412 Issue 01


Id:0900d805805b2919

l

If predecessor(type) is TMA the predecessor(rack) must be the same as the rack of the DILNA/DULNA, i.e. the TMA connected to a DILNA/DULNA must be created in the same rack as the DILNA/DULNA object.

predecessor (relative number):

DULNA 0 ... 7

DILNA 0 ... 7 (for BS240XL only 4 ... 7)

TMA 0 ... 15 (for BS240XL only 12 ... 15)

Validity RangeIn commands CREATE DILNA, CREATE DULNA, CREATE F6LNA:

predType DILNA predRack RACK0

RACK1

RACK2

predNo DILNA0

DILNA1

...

DILNA7

DULNA predRack RACK0

RACK1

RACK2

predNo DULNA0

DULNA1

...

DULNA7

TMA predRack RACK0

RACK1

RACK2

predNo TMA0

TMA1

...

TMA15

F6LNA predRack RACK0

RACK1

RACK2

predNo F6LNA0

F6LNA1

...

F6LNA3

DN0933412 Issue 01651


l

Id:0900d805805b2919

In commands GET DILNA, GET DULNA, GET F6LNA:

Default ValueNone.

Contained in the following commands: CREATE DILNA, CREATE DULNA, CREATE F6LNA, GET DILNA, GET DULNA, GET F6LNA

predType DILNA predRack RACK0

RACK1

RACK2

predNo DILNA0

DILNA1

...

DILNA7

DULNA predRack RACK0

RACK1

RACK2

predNo DULNA0

DULNA1

...

DULNA7

TMA predRack RACK0

RACK1

RACK2

predNo TMA0

TMA1

...

TMA15

F6LNA predRack RACK0

RACK1

RACK2

predNo F6LNA0

F6LNA1

...

F6LNA3

<NULL>

652DN0933412 Issue 01


Id:0900d805805b2919

l

LOCALADDRlocalAddress

Local IP address of the Circuit Emulation Service Tunnel. The address is input in the usual IPv4 format. For addressing examples please see also attribute ipAddress. The object must be locked before modifying the address via the SET command.

Validity Range

Default ValueNone.


LOCLUDPlocalUdpPort

Local UDP port number of the CESPW instance. It is recommended to use identical port numbers for the local and the peer UDP port. The object must be locked before modi-fying the port number via the SET command.

Validity Range

Default ValueNone.

Contained in the following commands: CREATE CESPW, GET CESPW, SET CESPW

LOCNAMElocationName

Validity Range

Default ValueNone.



49152 - 65535

This attribute is a ASCII string (max 37 characters) which identifies a location.

Default Value: EARTH


DN0933412 Issue 01653


l

Id:0900d805805b2919

LOSPKTTHlostPacketThreshold

new information

Validity Range

Default Value


LPDLMSATlapdleLinkSatellited

The attribute informs the BTSplus mainline SW about the settings in the Flexi BSC product family regarding the presence of a satellite on the Abis interface. The attribute is sent only during the 'BTSE Alignment Procedure'. The BTSE SW stores the value only as information for the operator. However when the attribute is stored the BTSE SW performs a semantic check which compares the value of lapdmLinkSatellited with the value of the attribute sAbisLinkSatellited (ABISLKSAT). The BTSE SW reports a minor alarm if both values do not match. The BTSE object is set to enabled.degraded as long as the alarm is active. In order to clear the alarm the operator has to take steps that LPDLMSAT and ABISLKSAT have a consistent value - a consequence of this action is an interruption of the Abis link (as a change of ABISLKSAT is only possible at the BTSE-LMT Evolution in phase 2 and a change of LPDLMSAT requires a deletion and re-creation of the BTSM object at the LMT Evolution or at the NetAct).

Validity Range

Default Value terrestrialConnection


LRUlru

This attribute describes an object class and instance of a specific board that is affected by the firmware upgrade.

1 - 100

1


satelliteConnection

654DN0933412 Issue 01


Id:0900d805805b2919

l

Validity Range

Default ValueNone.

Contained in the following commands: FWUPGRADE BTSM

LSINDlineStatusIndication

siemensHw HwP

HwXS

typeOfHw Cu

Coba

Fcumain

Duamco

Ficom6

rackNbr 0 - 2

boardNbr 0 - 11

This attribute identifies the PCM link status values, that additionally will be displayed via LED(s) at the LI or COBA/COSA. More than one status might be valid at a time.

Bit 0: RemoteAlarmIndication

01 TRUE

00 FALSE always FALSE in case of ISDN S0

Bit 1: FrameSynchronizationLoss

01 TRUE

00 FALSE

Bit 2: CRCFailure

01 TRUE


Bit 3: NoLevel (Line is broken)

01 TRUE

00 FALSE

Bit 4: CRCFailureRemoteEnvironment

01 TRUE


Bit 5: BitErrorRate > lowerThreshold of 'bitErrorRateThresholds'

DN0933412 Issue 01655


l

Id:0900d805805b2919

Validity Range

Default ValueNone.

Contained in the following commands: GET BPORT

01 TRUE


Bit 6: BitErrorRate > upperThreshold of 'bitErrorRateThresholds'

01 TRUE


Bit 7: PromptMaintenanceAlarmIndication

01 TRUE

00 FALSE

RemoteAlarmInd FALSE

TRUE

FrameSynchroniza-tionLoss

FALSE

TRUE

CRCFailure FALSE

TRUE

NoLevel FALSE

TRUE

CRCRemoteEnviro-ment

FALSE

TRUE

BERTLowerThresh-old

FALSE

TRUE

BERTUpperThresh-old

FALSE

TRUE

PromptMainte-nanceAlarmInd

FALSE

TRUE

<NULL>

656DN0933412 Issue 01


Id:0900d805805b291b

m

m

MACADDRmacAddress

This attribute provides the MAC address of the Ethernet port instance. Attribute is coded as a string with 17 characters with hexadecimal representation of the MAC address (e.g. 09:03:20:ae:ec:7b).

Validity Range

Default ValueNone.

Contained in the following commands: GET COBAETHINTF

MAIOmaio

"Hopping physical channels on the same timeslot with the same mobile allocation (con-tained in the aRFCNList) must use the same value of hoppingSequenceNumber and dif-ferent values for MAIO (Mobile Allocation Index Offset). This prevents frequency collision.

The maximum value of mAIO depends on the number of frequencies in the attached ARFCNList. For a set of N allocated frequencies in the ARFCNList there must be N dif-ferent values for mAIO (0...N-1).

Any instance of the object CHAN which is not assigned to any explicit frequency hopping system instance should contain the default value 0 for this attribute."

Changing this attribute is allowed only if there is no hopping (i.e. attribute btsIsHopping = FALSE).

Validity Range

Default Value 0


MAXGNmaxGain(dB*4)



0 - 63

DN0933412 Issue 01657


m

Id:0900d805805b291b

Validity Range

Default ValueNone.


MAXPDVmaxPdv(ms)

The attribute defines the maximum packet delay variation value. It is used for dimension-ing of the jitter buffer. The object must be locked before modifying the maxPdv value via SET command.

Validity Range

Default Value


MINGNminGain(dB*4)


Validity Range

Default ValueNone.


MOBALLOCarfcnList

0 - 255

<NULL>

0.125 - 30.000

2.000

0 - 255

<NULL>

mobileAllocation / trxFrequency

658DN0933412 Issue 01


Id:0900d805805b291b

m

This attribute is contained in the functional objects transceiver and channel.

Octet 2 tells the number of frequencies in the list. The remaining number of octets of this information element (aRFCNList) is twice the value of this field.

If the attribute is contained in a message related to the transceiver the value of "Number of ARFCNs in List" must be 1, i.e. only one ARFCN is allowed. (The name at the GUI is 'trxFrequency" in this case.

If the attribute is contained in a message related to the channel (The name at the GUI is 'mobileAllocation" in this case.) the value of "Number of ARFCNs in List" is : <00-40>, <0- 64> (decimal)

The value 0 has the special meaning that the corresponding channel instance is not assigned to any frequency hopping system instance and that the BTSE has to use the ARFCN value of the TRX which contains the channel.

ARFCN1..ARFCNn shall be contained in ascending order with no duplicates.


Hex Decimal

GSM900 "BB900" 0001 ... 007C 1 ... 124


0000 ... 007C

03CF ... 03FF

0 ... 124

975 ... 1023


0000

0000 ... 007C

03CF ... 03FF

0

0 ... 124

975 ... 1023

DCS 1800 "DCS1800"

0200 ... 0375 512 ... 885

PCS 1900 0200 ... 032A 512 ... 810

GSM-R 03BB ... 03CE 955 ... 974

GSM-DCS 0000 ... 007C

03CF ... 03FF

0200 ... 0375

0 ... 124

975 ... 1023

512 ... 885

GSM850 0080 ... 00FB 128 ... 251

GSM850-PCS 0080 ... 00FB

0200 ... 032A

128 ... 251

512 ... 810

GSM850-DCS 0080 ... 00FB

0200 ... 0375

128 ... 251

512 ... 885

DN0933412 Issue 01659


m

Id:0900d805805b291b

Validity Range

Default Value octet #2 = 0 (only for aRFCNList related to "CHAN")


MOECmemberOfEmergencyConfig

The attribute memberOfEmergencyConfiguration specifies whether a TRX should still operate for a given time (emergencyTimer1) if a "battery backup operation" (due to "mains breakdown") occurs. If an emergency because of overtemperature occurs, this attribute specifies a TRX which is not powered off immediately.

If this feature is wanted the value TRUE should be used at least for the BCCH TRX. If FALSE is used for the BCCH TRX and TRUE is used for another TRX in the cell a BCCH reconfiguration would be triggered if a "battery backup operation" (due to "mains break-down") or overtemperature occurs.

g The switch to emergency configuration or zero configuration in case of overtemper-ature only depends on the temperature itself (two different values for emergency and zero configuration) and does not depend on the emergencyTimer1/2.

Validity Range

Default Value TRUE


MONPRTmonitoringPort

This attribute defines the port which is used for Abis traffic monitoring on the ETHCON module.

Changing or setting this attribute for a TRX means a temporary loss of service for the TRX.

Changing this attribute for a CHAN is allowed only if there is no fre-quency hopping (i.e. attribute btsIsHopping = FALSE).

0 to 64 items of

0 - 1023

TRUE

FALSE

660DN0933412 Issue 01


Id:0900d805805b291b

m

The attribute enables mirroring of packets for the configured monitoringPort. The port number corresponds to the ETHPORT instance number. Port mirroring can be enabled for maximum one port.

The system does not check if the referenced port is already created.

Validity Range

Default Value

Contained in the following commands: GET ETHCON, SET ETHCON

MORTMOT

This Attribute describes an object instance. The MOT attribute defines the HW-MO that will have its internal resources tested.

Below are reported some detailed information about the validity range.

for: BS240, BS40 BS240SR BS40II BS82II

BS241, BS41 BS241SR

BS240XL BS240XLSR

ACDCP - Y Y - Y

ACT Y Y Y Y Y

BATTERY - Y Y - Y

COBA #) Y Y - Y Y

COSA Y Y - Y -

CU Y Y - Y Y

DIDCTMA Y Y - - Y

DILNA Y Y - - Y

DUDCTMA Y Y - Y Y

DULNA Y Y - Y Y

DUVSWR Y Y - Y Y

none

port0

port1

port2

port3

coba

none

DN0933412 Issue 01661


m

Id:0900d805805b291b

FANP *) Y Y Y Y Y

FCUMAIN Y Y - Y Y

FCUTR Y Y - Y Y

FTNFP Y Y - Y -

FVSWRP Y Y - Y -

LMU Y - - - -

TMA *) Y Y - Y Y

*) no processor #) COBA #0 only possible via LMT Evolution on

phase 2

Validity Range

Default ValueNone.

Contained in the following commands: GET BTSETEST, PERFTEST BTSEP, STOPTEST BTSEP

MPHERRmaxPhaseError(microsec)

This attribute specifies the desired maximum phase deviation of the base clock on the COBA in respect to the GPS clock. If the current phase deviation exceeds this desired maximum value an alarm is issued and the attribute clockAccuracy is set to the reduced accuracy level 'high'. This attribute is only meaningful if the attribute syncSource is set to 'extGPS' and the attribute enableInterSiteSync is set to 'TRUE'.

Validity Range

Default Value

Contained in the following commands: GET SYNCBTSE, SET SYNCBTSE

MPTSLXXmappingTSLXX

This attribute describes to which "time slot" of the specified Bport the TS xx of the Bport related to the given XConnect instance is to be mapped; e. g. 'mappingTSL02' of XConnect 0 describes the mapping of time slot 2 of BPort 0 (which corresponds to XConnect 0) to a time slot (targetTSL) of a BPort instance (targetBPort). If the 'target BPort' value is equal to the value of the XConnect instance this means that a "remap-ping" between the time slot position on the Abis line and the BTSplus mainline internal

Pathname

1.5 - 15.0

1.5

662DN0933412 Issue 01


Id:0900d805805b291b

m

position is done- this is allowed only in LMT Evolution phase 2. The purpose for this "remapping" usually is to have the traffic data and signalling data in the BTSplus mainline at the same positions as at the PCM lines directly connected to the Flexi BSC product family (and as indicated in the attributes abisChannel and lapdChannel)- this is needed e.g. if there is a sequence of several PCM lines between Flexi BSC product family and the BTSplus mainline involving multidrop/loop and cross connect configura-tions.

In case of PCM24 only mappingTSL01..mappingTSL24 are meaningful.

XConnect instance 0 is related to BPORT instance 0








note on targetTSL validity range:

- targetTSL : 0 ... 24 for time slot in 1,5 Mb/s link

- targetTSL : 0 ... 31 for time slot in 2 Mb/s link

targetBport = 0 and targetTSL = 0 mean 'no mapping'

Validity Range

Default Value

Contained in the following commands: CREATE XCONNECT, GET XCONNECT, SET XCONNECT

MRSYNCTmaxResyncTime(min)

This attribute allows the operator to adjust the maximum re-synchronization time to reach the desired phase accuracy defined with the attribute maxPhaseError. If the esti-mated re-synchronization time exceeds this value an alarm is issued, which informs the operator that a manual re-synchronization should be considered. The time can be adjusted between 0 and 24 hours (i.e. 0-1440 minutes). This attribute is only meaningful if the attribute syncSource is set to 'extGPS' and the attribute enableInterSiteSync is set to 'TRUE'.

targetBport 0 - 7

targetTSL 0 - 31

targetBport 0

targetTSL 0

DN0933412 Issue 01663


m

Id:0900d805805b291b

Validity Range

Default Value


MSDISTBEHAVmsDistanceBehaviour

This attribute defines the executions allowed after the Timing Advance parameter has exceeded the threshold.

Validity Range

Default ValueNone.


MSTXPMAXmSTxPwrMax(*dBm mapped)

This attribute indicates the maximum power level an MS may use in the serving cell. In case of GSMDCS, GSM850-PCS and GSM850-DCS mixed cells the attribute repre-sents the maximum power level a MS may use in the band to which the BCCH belongs.

Below are listed some detailed validity range values

GSM / GSM-R:

39 dBm

37 dBm

:

33 dBm, Default Value

:

15 dBm

13 dBm

DCS 1800:


28 dBm

:

02 dBm

0 - 1440

180

0 - 255

664DN0933412 Issue 01


Id:0900d805805b291b

m

00 dBm

PCS 1900:


28 dBm

:

02 dBm

00 dBm

33 dBm

32 dBm

Validity Range

Default ValueNone.


MSTXPMAXCmSTxPwrMaxCompl

This attribute is meaningful only in case of GSM-DCS, GSM850-PCS and GSM850-DCS mixed cells and represents the maximum power level a MS can use in the band of the serving cell to which the BCCH doesn't belong. A change of the attribute becomes effective with the next call.

BCCH is in the DCS or PCS band - the MS can use the specified value

for the maximum power in the GSM band (i.e. in the band complementary

to the BCCH band)

39 dBm

37 dBm

:


:

15 dBm

13 dBm

BCCH is in the GSM band - the MS can use the specified value for the

maximum power in the DCS band (i.e. in the band complementary to

the BCCH band)


0 - 31

DN0933412 Issue 01665


m

Id:0900d805805b291b

28 dBm

:

02 dBm

00 dBm

BCCH is in the GSM band - the MS can use the specified value for the

maximum power in the PCS band (i.e. in the band complementary to

the BCCH band)


28 dBm

:

02 dBm

00 dBm

33 dBm

32 dBm

Validity Range

Default ValueNone.


MTLTmechanicalTilt(degree*10)


Validity Range

Default ValueNone.


MTYPmediaType

This attribute indicates the type of the physical medium used for the given instance of Ethernet port.

0 - 31

0 - 65535

<NULL>

666DN0933412 Issue 01


Id:0900d805805b291b

m

Validity Range

Default ValueNone.

Contained in the following commands: GET ETHPORT

electrical

optical

<NULL>

DN0933412 Issue 01667


n

Id:0900d805805b291d

n

NEPTTREPnotDataRepCount

The attribute allows to choose between different PDV compensation parameter sets which are optimized to certain network behaviors.

Validity Range

Default ValueNone.


NTWTYPCnetworkTypeCompensation

This attribute defines the type of network (in terms of frequency band(s)) the BTSplus mainline is working in. Further more it indicates the type of a possible complementary frequency band when handling Dual Band MSs.

Validity Range

Default Value


NTWTYPEnetworkType

This attribute defines the type of network (in terms of frequency band(s)) the BTSplus mainline is working in. Further more it indicates the type of a possible complementary frequency band when handling Dual Band MSs.

Below are listed some details about the attribute validity range:

GSMDCS:

GSM 900

DCS 900

GSM EXTENDED

0 - 3

0 - 255

0

668DN0933412 Issue 01


Id:0900d805805b291d

n

GMS EXTENDED REDUCED

GMS-DCS

GSMPCS:

GSM 900

GSM EXTENDED


PCS 1900

GSMR:

GSM-R

.

.

GSM850PCS:

PCS 1900

GSM850

GSM850PCS

GSM850DCS:

DCS 1800

GSM850

GSM850DCS

GSMRAIL PUB:

GSM 900

DCS 1800

GSM EXTENDED


GSM-R

GSM-DCS

Validity Range

GSMDCS

GSMPCS

GSMR

GSM850PCS

GSM850DCS

DN0933412 Issue 01669


n

Id:0900d805805b291d

Default ValueNone.


NY1ny1

This attribute indicates the maximum number of repetitions of the PHYSICAL INFOR-MATION message on the radio interface. This message is sent by the BTSplus mainline to the MS during a handover procedure between two not synchronised cells, in order to establish a physical channel connection on the new cell. If the maximum number of rep-etitions is reached, the newly allocated channels are released and the context related to the handover is abandoned. ny1 is a binary presentation of maximum number of repeti-tions of PHYSICAL INFORMATION.

Note: (ny1) * (BTS Air Timer t3105) must be greater than the maximum Um Layer 2 response time.

Validity Range

Default Value 30


NY2ny2

As a result of an Uplink Access of a mobile station the network grants the uplink to the mobile station by sending a VGCS UPLINK GRANT message periodically. ny2 is the counter value which defines the number of repetitions of sending the message.

Validity Range

Default Value 20


1 - 254

1 - 254

670DN0933412 Issue 01


Id:0900d805805b2e35

o

o

OMLAPDRTomLapdRelTimer(sec)

At the detection time of the Abis link failure (which may happen at different times in the BTSplus mainline and in the Flexi BSC product family), the BTSplus mainline starts the timer omLAPDRelTimer and the Flexi BSC product family starts the timer shortLAPDInt-Timer. If the timer omLAPDRelTimer expires, the BTSplus mainline blocks the call pro-cessing. After that the BTSplus mainline forces the Flexi BSC product family (via a RestartSendingEventReports-NACK message) to perform a complete Abis alignment. If none of the two timers expires, the Flexi BSC product family performs a 'Short Abis alignment'. The default value of omLAPDRelTimer should be kept greater than the default value of the attribute shortLAPDIntTimer.

The validity range step size is 1 second.

Validity Range

Default Value 30 seconds


OSToperationalState

This attribute defines whether or not the resource is physically installed and working.

Validity Range

Default Value DISABLED for Functional Objects

Contained in the following commands: GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTS, GET BTSEP NOSWL, GET BTSM NOSWL, GET CESPW, GET CESTUNNEL, GET CHAN, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA, GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET TRX, GET XCONNECT

3 - 300

DISABLED

ENABLED

DN0933412 Issue 01671


o

Id:0900d805805b2e35

OUTPUToutput

New Information.

Validity Range

Default ValueNone.

Contained in the following commands:None.

OUTPUTPRoutputPowerReduction

The attribute specifies if and how the maximum output power of the carrier unit / FlexCU carrier has to be reduced because of the setting of the BTS attribute 'carrierUnitConfig-uration.

This attribute is valid only for CU and FlexCU.

Validity Range

Default ValueNone.

Contained in the following commands: GET CU, GET FCUTR

OVERWRITEOverwrite


db0

db1

...

db4

This attribute specifies whether the existing BTS-SW on the Flexi BSC product family hard disk will be overwritten (YES) or not (NO) (UPLBTSLOG).

This attribute specifies whether the existing file containing the Alarm Buffer SW will be overwritten (YES) or not (NO) (UPLBTSLOG).

This attribute specifies whether the existing IDT file will be overwritten (YES) or not (NO) (UPLLIDF).

672DN0933412 Issue 01


Id:0900d805805b2e35

o

Validity Range

Default ValueNone.

Contained in the following commands: DNLALLEXE SOFTWARE-MANAGEMENT, UPLBTSLOG SOFTWARE-MANAGE-MENT, UPLLIDF REMINV

OVPTINSovptInstalled

This attribute indicates whether an OVPT board is installed or not. It can be set only in LMT Evolution phase 2. The attribute is used to adapt the pulse mask according to the recommendations.

Validity Range

Default Value


NO

YES

TRUE

FALSE

TRUE

DN0933412 Issue 01673


p

Id:0900d805805b2e37

p

PCCCHLDIperiodCcchLoadIndication(sec)

This attribute indicates the frequency with which the CCCH load indication is sent to the Flexi BSC product line. This attribute is also used to enable the Paging Overload Han-dling.

The value 0 has following two meanings:

• The CCCH Load Indication message is sent only once, every time an overload occurs, with no repetition (frequency = 0)

• The feature Paging Overload Handling is not enabled

Validity Range



PEERADDRpeerAddress

Peer IP address of the Circuit Emulation Service Tunnel.The address is input in the usual IPv4 format. The object must be locked before modifying the address via the SET command. For addressing examples see description for attribute ipAddress.

Validity Range

Default ValueNone.


PEERUDPPORTpeerUdpPort

Peer UDP port number of the CESPW instance. It is recommended to use identical port numbers for the local and the peer UDP port. The object must be locked before modify-ing the port number via the SET command.

0 - 255


674DN0933412 Issue 01


Id:0900d805805b2e37

p

Validity Range

Default ValueNone.


PKTLATpacketizationLatency

The attribute defines the number of frames which are contained in the payload of each UDP packet.

The latency is expressed in micro seconds. Every 125 Î¼sec correspond to 1 TDM frame in the payload. A lower value means a lower delay but a bigger protocol overhead. The object must be locked before modifying the latency value via SET command.

Validity Range

Default Value


PNGFpingFrequency

The attribute is only meaningful if the ping delay measurement is activated via the PM scanner SCANBTSM - RNDTDELBTS. It defines how many ping request packets are sent per minute.

SCANBTSM provides only ping delay measurement results if the attribute is set to a value greater than 0.

Validity Range

49152 - 65535

m125

m500

m1000

m2000

m3000

m4000

m5000

m1000

0 - 120

DN0933412 Issue 01675


p

Id:0900d805805b2e37

Default Value


PNGPKTpingPacketSize

The attribute is only meaningful if the ping delay measurement is activated via the PM scanner SCANBTSM - RNDTDELBTS. It defines the size of a ping request packet. The value small corresponds to the default packet size of the ICMP ping request. Value traffic corresponds to the maximum packet size within the pseudo wires of the tunnel.

Validity Range

Default Value


PNOFACCHperiodNotificationFACCH(sec)

The attribute defines the period (repetition rate) for the FACCH notification for a given ASCI call.

A change of the attribute becomes effective at expiration of the current time period, latest after the time given by "periodNotificationFACCH".

Validity Range

Default Value 2.5 seconds


PRDINFproductInfo(prodNbr_SN_HwVer_SwVer)

0

SMALL

TRAFFIC

TRAFFIC

1.0 - 5.0

676DN0933412 Issue 01


Id:0900d805805b2e37

p

The attribute shows product specific information of the TMA if HDLC signaling is used and information is provided by the TMA. It is represented by a single string, consistingof four parts, separated by a couple of defined delimiters:

• Delimiter1 • Delimiter2 (a white space)

This attribute will be retrieved by own command get TMA prodInfo.

Validity Range

Default ValueNone.

Contained in the following commands: GET TMA, GET TMA PRODUCTINFO

PRDIRECTpreferredDirection

The attribute indicates whether the RX downlink information is gained from the related BPORT or not. In a loop configuration the preferred direction is changed, if e.g. the Bit Error Rate is greater than a certain threshold or if the link fails.

'TRUE' means that the RX data at the given BPORT instance is used as input data.

'FALSE' means that the RX data at the given BPORT instance is not used as input data.

The attribute is meaningful only in a loop configuration. If a GET is done in other config-urations the length will be set to 0.

Validity Range

Default ValueNone.

Contained in the following commands: GET BPORT

PRSproceduralStatus

This attribute is contained in all equipment related managed objects. It indicates whether the assigned HW board performs an initialization procedure. For non processor HW boards, the proceduralStatus is always NULL.

This attribute is readable by the operator but is not contained in the "Changed State Event Report" notification.


TRUE

FALSE

<NULL>

DN0933412 Issue 01677


p

Id:0900d805805b2e37

Validity Range

Default Value NULL

Contained in the following commands: GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTSEP NOSWL, GET CESPW, GET CESTUNNEL, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA, GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET XCONNECT

PSTATportStatus

This attribute provides the result of the auto negotiation procedure. If auto negotiation is disabled the current setting of the port is shown.

Validity Range

Default ValueNone.


PUSGportUsage

This attribute determines usage of the Ethernet port for the BTSplus mainline. Only one ETHPORT instance can be set to BSClink. The attribute is only informational.

Validity Range

NULL

initializing

speed speed100M

speed1000M

duplexMode disabled

enabled

flowControl disabled

enabled

bscLink

multidropLink

678DN0933412 Issue 01


Id:0900d805805b2e37

p

Default ValueNone.


PWNAMEpwName

This attribute specifies optional symbolic name of the pseudo wire, the same name should be configured at the peer side. The name has to be unique within all CESPW instances on given host.

Validity Range

Default ValueNone.


PWROUTpowerOutputThresholds

The attribute value is indicated in dB.

The letter "m" before the value range values, means minus

Validity Range


This attribute defines the three power output thresholds:

- Output Power Fault Threshold: defines the minimal output power level "transmitter-fault", which results in generating an alarm.

- Reduced Output Power Threshold: defines the power level, when an alarm (warning) is generated (Pout alm red) due to less output power.

- Excessive Output Power Threshold: defines the power level, when an alarm is generated (Pout alm fault) due to too much power level at the output of the power amplifier.

oPwrFaultThreshold m10db

m8db

redOutPwrThresh-old

m10db

m8db

DN0933412 Issue 01679


p

Id:0900d805805b2e37

Default Value m10dB = -10dB

m6db = - 6dB

db5 = 5dB


PWRREDtxPwrMaxReduction(*-2dB)

This attribute specifies the number of 2dB steps the TRX should be reduced from the maximum transmit power, for tuning the cell coverage. The resulting attenuated transmit power is the maximum nominal power Pn.

(values from 0 dB to -12 dB, with step size - 2 dB)

Validity Range

Default ValueNone.


m6db

m4db

excesOutPwrThresh db3

db5

0 - 9

680DN0933412 Issue 01


Id:0900d805805b2e39

r

r

RACHBTrachBusyThreshold(dBm)

Validity Range

Default Value 109


RACHLASrachLoadAveragingSlots

This attribute defines the number of RACH bursts over which RACH measurements are performed.

Validity Range

Default Value 204 = 4 CCCH multiframes


RADIOMGradioMeasGran

This is an attribute of the TRX and specifies the granularity (multiples of 480 ms) in which the radio measurements have to be transmitted on the Abis interface in case they are enabled.

The attribute is indicated in SACCH multiframes.

This attribute defines a threshold for the received signal level con-cerning both:

- RACH access bursts

- intercell HO access bursts.

A signal level exceeding this threshold is interpreted as a busy RACH respective as a valid burst due to an intercell HO.

<ANY>

102 - 65535

DN0933412 Issue 01681


r

Id:0900d805805b2e39

Validity Range

Default Value 254 in SACCH multiframe


RADIOMRradioMeasRep

(ON = enabled)

Validity Range

Default Value OFF (disabled)


RADIUSEXTradiusExtension(km)

This attribute identifies the radius extension (in km) of an extended cell.

1 - 254

This is an attribute of the TRX and specifies whether the radio mea-surements have to be transmitted on the Abis interface.

Notes:

- A consequence of the value 'disabled' is that no 'Measure-ment result' messages are sent to the Flexi BSC product line.

- Special care has to be applied if the attribute is set to "ON" for several TRXs: the appropriate Abis signalling capacity must be provided by creating a sufficient number of LAPDLE instances each with a full 64 KBit/s timeslot. If this prerequisite is not fulfilled (e.g. just 1 LAPDLE and 11 TRXs with full and half rate are fully exploited) the Call Failure Rate will increase (increased delay times in the BTSE LAPD queues due to the huge amount of measurement result messages lead to more CHANNEL REQUIRED messages because of a too late Immediate Assignment command etc. etc.). This is especially critical if RADIOMG is set to 1 (corresponding to 480 ms).

OFF

ON

682DN0933412 Issue 01


Id:0900d805805b2e39

r

Validity Range

Default ValueNone.

Contained in the following commands: GET BTS, GET TRX

RELEQUIPOBJrelatedEquipObjects

Validity Range

Default ValueNone.

Contained in the following commands: GET BTS, GET BTSM NOSWL, GET CHAN, GETRELATIONSHIP TRX

RELFUNCOBJrelatedFuncObjects

0 - 35

This attribute represents the relationships between a specific FMO instance and none, one or several HMO instances. The HMO instances in this list offers their services to the given FMO instance. This attribute is only allowed for BTSM, BTS, TRX and CHANNEL objects.

FMO maximal number of related HMOs

N (decimal)

BTS 0 2

BTSM 1 6

CHAN 0 2

TRX 30 122

0 to 47 items of

Pathname

DN0933412 Issue 01683


r

Id:0900d805805b2e39

This attribute represents the relationships between a specific HMO instance and none, one or several FMO instances. The FMO instances in this list make use of the services of the given HMO instance. This attribute is allowed for each HMO instance of the actual hardware variant. Currently only BTSM and TRX are contained in the list.

Since the maximal number of related FMO instances in the list depends on the special type of HMO, the following list shows the real-istic values for the each HMO that may contain related FMO instances. The table shows for each HMO the maximal number of FMO instances and the maximum number of octets of the attribute including the attribute identifier and attribute length field.

HMO maximal number of related FMOs

N (decimal)

BPORT 0 2

BTSE 1 6

ENVABTSE 0 2

LAPDLE 0 2

RACK 0 2

SYNCBTSE 48 194

XCONNECT 0 2

HMO maximal number of related FMOs

N (decimal)

ACDCP 0 2

ACT 0 2

BATTERY 0 2

COBA 48 194

COSA 24 (note) 98

CU 1 6

DIDCTMA 24 98

DILNA 24 98

DUDCTMA 24 98

DULNA 24 98

DUVSWR 24 98

FANP 0 2

FCUMAIN 2 10

FCUTR 1 6

684DN0933412 Issue 01


Id:0900d805805b2e39

r

Validity Range

Default ValueNone.

Contained in the following commands: GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTSEP NOSWL, GET CESPW, GET CESTUNNEL, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA, GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET XCONNECT, GETRELATIONSHIP BCOM, GET-RELATIONSHIP COBA

REPTYPreportType

This parameter is used to indicate to the mobile station to use the ENHANCED MEA-SUREMENT REPORT or MEASUREMENT REPORT messages for reporting, and it can assume two values:

- NORMAL: the MS uses the MEASUREMENT REPORT message for reporting

- ENHANCED: the MS uses the ENHANCED MEASUREMENT REPORT message for reporting if at least one BSIC (Base Station Identity Code) is allocated to each frequency of the BA (BCCH Allocation) list . Otherwise, the MEASUREMENT REPORT message is used.

Validity Range

Default ValueNone.

FTNFP 1 6

FVSWRP 8 34

TMA 24 98

Note: COSA old (if enableFcuSupport = TRUE) and COSA new only can handle up to 12 FCU (24 TRX)

0 to 48 items of

Pathname

ENHANCED

NORMAL

ENHANCED_ONLY_FOR_R43G_MS

DN0933412 Issue 01685


r

Id:0900d805805b2e39


RFRSINDPrfResourceIndicationPeriod

This attribute indicates the sending rate of the signalling message RF RES IND to the Flexi BSC product line.

The attribute is indicated in unit of SACCH multiframes

Validity Range

Default Value 60 in unit of SACCH multiframe


RSACCHRXLDLrepSacchRxLevDL

This attribute is used to define, on a per cell basis, the threshold for RXLEV_DL_SUB used in the decision algorithm for activating R-SACCH in DL and UL for MS with Repeated SACCH Capability, i.e. R-ACCH_CAP = 1.

Validity Range

Default ValueNone.


RSACCHRXLULrepSacchRxLevUL

This attribute is used to define, on a per cell basis, the threshold for RXLEV_UL_SUB used in the decision algorithm for activating R-SACCH in DL and UL for MS with Repeated SACCH Capability, i.e. R-ACCH_CAP = 1.

Validity Range

1 - 254

0 - 25

0 - 25

686DN0933412 Issue 01


Id:0900d805805b2e39

r

Default ValueNone.


RSACCHTODLrepSacchTimeOutDL

This attribute is used to define, on a per cell basis, the threshold for deactivation of R-SACCH mode in the decision algorithm for R-SACCH in DL for MS with Repeated SACCH Capability, i.e. RACCH_CAP = 1.

Validity Range

Default ValueNone.


RSACCHTOULrepSacchTimeOutUL

This attribute is used to define, on a per cell basis, the threshold for deactivation of R-SACCH mode in the decision algorithm for R-SACCH in UL for MS with Repeated SACCH Capability, i.e. RACCH_CAP = 1.

Validity Range

Default ValueNone.


RXBMAXFrxBandMaxFreq(kHz*100)


Validity Range

0 - 10

0 - 10

0 - 65535

<NULL>

DN0933412 Issue 01687


r

Id:0900d805805b2e39

Default ValueNone.


RXBMINFrxBandMinFreq(kHz*100)


Validity Range

Default ValueNone.


RXDIVSVenableRxDiversitySupervision

The attribute enableRxDiversitySupervision of the object 'BTSE' indicates whether the supervision of the RX levels and the signal to noise ratio of both receiver branches is enabled or disabled. A prerequisite is that diversity is configured and that a TCH or SDCCH is on at least 2 time slots of the TRX. Due to the supervision failure event reports for the TPU / CU related to a TRX may be sent.

Validity Range

Default Value


RXLEVADJrxLevAdjust(dB)

This attribute specifies the value needed to adjust the RXLEV value of both receiver branches ("N" and "D") of the TPU, CU and of the FCUMAIN.

The attribute has no functionality in case a FCUMAIN is wired to a SDUAMCO.

0 - 65535

<NULL>

disabled

enabled

disabled

688DN0933412 Issue 01


Id:0900d805805b2e39

r

(values from -24 dB to +23 dB)

Validity Range

Default Value

Contained in the following commands: CREATE CU, CREATE FCUMAIN, GET CU, GET FCUMAIN, SET CU, SET FCUMAIN

RXLEVADJN1D1rxLevAdjustN1D1(dB)

This attribute specifies the value needed to adjust the RXLEV value of the additional receiver branches "Rx C / N1" and "Rx D / D1" of the FCUMAIN.

The attribute has no functionality in case a FCUMAIN is wired to a SDUAMCO).

Validity Range

Default Value

Contained in the following commands: CREATE FCUMAIN, GET FCUMAIN, SET FCUMAIN

RXSIGLEVADJrxSigLevAdjust

The attribute specifies the signal level adjust values which shall be applied to the receive paths of transceivers using the same frequency band as the BCCH transceiver.

Validity Range

Default ValueNone.

adjustValue -24.0 - 24.0

adjustDivValue -24.0 - 24.0

adjustValue 0.0

adjustDivValue 0.0

adjustValueN1 -24.0 - 24.0

adjustDivValueD1 -24.0 - 24.0

adjustValueN1 0.0

adjustDivValueD1 0.0

<ANY>

DN0933412 Issue 01689


r

Id:0900d805805b2e39


RXSIGLEVADJCrxSigLevAdjustCompl

The attribute specifies the signal level adjust values which shall be applied to the transmit paths oftransceivers using the complementary frequency band. The value is only meaningful in case of a multiband cell.

Validity Range

Default ValueNone.


RXSWCURSETrxSwitchCurrentSetting

Usually the content of this attribute is identical to the value of the attribute rxSwitchReq-Setting. A deviation is possible e.g. in case of HW failures - in these cases the attribute shows the real situation. The attribute has a meaning only if the value of the attribute switchedBeamCapability has the value four_beams.

The BTSplus mainline sends a change of the attribute value via CAER to the Flexi BSC product line.

Validity Range

Default ValueNone.


<ANY>

NULL

690DN0933412 Issue 01


Id:0900d805805b2e3b

s

s

SALUNAMEsalesUniqueName

Validity RangeIn commands GET BTSEP NOSWL:

In commands SET BTSEP:

Default Value length = 1, octet 3 = 0


SBPRTsyncBport

This attribute indicates the port which is currently used for synchronization. This infor-mation is specially useful in case of a PCM loop configuration.

Validity Range

Default ValueNone.


SCELLNOsecondCellNumber

The attribute contains an ASCII string with 11 characters which don't contain a NUL character. The operator has always to enter 11 char-acters for the attribute. If the operator has not yet supplied a value for the attribute but does a GET, the BTSplus mainline SW will return the 'default value'. The attribute should be set by the operator before a upload of the IDT is performed.

The attribute is also used during the Abis alignment for checking if the right BTSplus mainlineis connected to the Abis link.

Default Value: length = 1, octet 3 = 0



<ANY>

DN0933412 Issue 01691


s

Id:0900d805805b2e3b

This attribute allows to indicate a second cell number for the objects DILNA and DULNA. Value <FF> means that a secondCellNumber is not used.

The second cell number allows sharing an antenna for receive diversity, i.e. it allows that two cells with different MNC (Mobile Network Code) which cover the same area (e.g. the same sector) at the BTSplus mainline site can share the same DUAMCO/FDUAMCO or IAMCO if receive diversity is required. As a consequence a DULNA-, DILNA- or TMA instance may belong to two cells.

The relation between a carrier unit and cell is derived from the TX wiring only, i.e. the attribute cellNumber of the wired DUVSWR object determines the cell a CU/FCUTR belongs to. The BTSplus mainline checks for each CU that one of the attributes cellNum-ber and secondCellNumber of all wired DULNA/DILNA objects matches with the attri-bute cellNumber of the wired DUVSWR.

It is strongly recommended to ensure for each CU/FCUTR that the attribute cellNumber of one wired DULNA object matches with the cellNumber of the wired DUVSWR.

Validity Range

Default ValueNone.

Contained in the following commands: CREATE DILNA, CREATE DULNA, CREATE F6LNA, GET DILNA, GET DULNA, GET F6LNA, SET DILNA, SET DULNA, SET F6LNA

SCIDsectorId


Validity Range

N_00

N_01

N_02

N_03

N_04

N_05

N_06

N_07

N_08

N_09

N_10

N_11

NotUsed


692DN0933412 Issue 01


Id:0900d805805b2e3b

s

Default ValueNone.


SCLPRIOLSTserviceClassPrioList

Default settings of this attribute for CES service correspond to “expedited forwarding”:

List of up to 8 service classes. Currently only the service class CES is supported. When the CES value is set for serviceClass all other attributes must not be set to default val-ues.Maximum one list entry is allowed for each service class.

Validity RangeIn commands GET BTSEP NOSWL:

Service Class CES Service Class to which the priority settings apply

vlanPrio 7 This attribute is not relevant if vlanid is set to “NULL.”

dscpClass 5 DSCP class selector. The value is the decimal representation of DSCP bits 0-2

dscpDropPre 6 DSCP drop precedence. The value is the decimal representation of DSCP bits 3-5

Table Default settings for CES service

0 to 8 items of

serviceClass ces

vlanPrio vPrio0

vPrio1

...

vPrio7

dscpClass dCl0

dCl1

...

dCl7

dscpDropPre dDP0

dDP1

...

dDP7

<NULL>

DN0933412 Issue 01693


s

Id:0900d805805b2e3b

In commands SET BTSEP:

Default ValueIn moc(s) BTSEP:

None.

In moc(s) BTSEP:


SEGMENTIDsegmentId

This attribute holds the “cellNumber” (from BR HMO data) parameter (configured by the user) to define the mapping of BTS instances to combiner equipment according HW configuration. The same “cellNumber” has to be set for all BTS in a segment. If a wrong value has been set by the user, either no HW (the alarm “HW cannot be assigned” is generated) or wrong HW is used for the BTS instance. In this case the underying FMOs must be deleted and created again with correct “cellNumber”.

g Since this attribute is reused to ensure a 1:1 mapping with the HW configuration within BSxx, there is a different view of segment Id as seen on BSS Abis (segment Id, range 0..3000) and LMT Evolution (“cellNumber”, range 0..11).

1 to 8 items of

serviceClass ces

vlanPrio vPrio0

vPrio1

...

vPrio7

dscpClass dCl0

dCl1

...

dCl7

dscpDropPre dDP0

dDP1

...

dDP7

serviceClass ces

vlanPrio vPrio7

dscpClass dCl5

dscpDropPre dDP6

694DN0933412 Issue 01


Id:0900d805805b2e3b

s

Validity Range

Default ValueNone.


SFPSERIDsfpSerialId

This attribute represents serial Id data if a SFP module is equipped.

The attribute is only meaningful for ports with SFP cages, i.e. it is not relevant for the ETHPORT instances 0 and 1.

The structure of the octet string is compliant to the addresses 0 â?? 127 of the Serial ID data at address A0.

Validity Range

Default ValueNone.


SHLAPDITshortLapdIntTimer(sec)

The BTSplus mainline uses the value of this timer to calculate the value of timer T202 which is used for the TEI assignment procedure.

This attribute is the timer used by the Flexi BSC product family in case of Abis link failure in order to discriminate between a "fast alignment" or a "full alignment". With the detec-tion of the link failure (which may happen at different times in BTSplus mainline and Flexi BSC product family) the BTSplus mainline starts the timer 'omLAPDRelTimer' and the Flexi BSC product family starts the timer 'shortLAPDIntTimer'. If any LAPD link on any of the LAPDLE signalling timeslots is up again within a certain time (i.e. the timer 'short-LAPDIntTimer' in the Flexi BSC product family has not yet expired) the Flexi BSC product family may decide to perform the fast alignment procedure.

At the detection time of the Abis link failure the BTSplus mainline starts the timer omLAPDRelTimer and the Flexi BSC product family starts the timer shortLAPDIntTimer. If the timer omLAPDRelTimer expires, the BTSplus mainline blocks the call processing. After that the BTSplus mainline forces the Flexi BSC product family (via a Restart Sending Event Reports NACK message) to perform a complete Abis alignment. If none of the two timers expires, the Flexi BSC product family performs a 'Short Abis alignment'.

0 - 11

0 to 128 items of

H#0 - H#ff

DN0933412 Issue 01695


s

Id:0900d805805b2e3b

(step size 1 second)

Validity Range



SLOTNOslotNo

The attribute indicates the slot number of the COBA and COSA. Since the modelling of the MO COBA is fixed (active COBA/COSA always COBA(0)/COSA(0), passive COBA/COSA always COBA(1)/COSA(1)), this is the only way to find out the slot of the active / passive COBA/COSA.

Validity Range

Default ValueNone.

Contained in the following commands: GET COBA, GET COSA

SRADIUSEXTsuperRadiusExtension(km)

This attribute defines the distance (measured in km) of the inner edge of 35 km wide super extended area from the BTS. Thevalue “0” means that the super extended area is not in use.

Validity Range

Default ValueNone.


3 - 20

leftCOBA

rightCOBA

leftCOSA

rightCOSA

0 - 70

696DN0933412 Issue 01


Id:0900d805805b2e3b

s

SRCDIRsourceDir

Validity Range

Default ValueNone.

Contained in the following commands: DNLIDFD REMINV

SRCPATHsrcpath

The sourceDirectory indicates the directory containing the BTS-SW to be downloaded (DNLALLEXE).

Validity Range

Default ValueNone.

Contained in the following commands: DNLALLEXE SOFTWARE-MANAGEMENT

STATIMEstartingTime

This attribute is only used together with btsIsHopping and can not be set by the operator.

Current Frame No is a binary presentation Frame Number Modulus 42432.

Note: startingTime is only used together with btsIsHopping.

Validity Range

Default ValueNone.

The sourceDirectory indicates the directory containing the BTS-SW to be downloaded (DNLALLEXE).

The sourceDirectory indicates the directory containing the BTSE nob-RIU file to be downloaded (DNLIDFD).



0 - 65535

<NULL>

DN0933412 Issue 01697


s

Id:0900d805805b2e3b

Contained in the following commands: GET BTS TIMER

STDBYSTstandbyStatus

The resource is not providing service but is able to take over the role of the resource to be backed-up without an initialization. The resource is providing service and is backing up another resource.

Validity Range

Default ValueNone.

Contained in the following commands: GET COBA, GET COSA, GET CU, GET FCUTR, GET LAPDLE

SUBUNTsubUnitType

new information

Validity Range

Default ValueNone.


SWBCAPABILITYswitchedBeamCapability

This attribute reflects the capability of the BTSplus mainline hardware and software. A change of the attribute value is sent by the BTSplus mainline via CAER to the Flexi BSC product family.

- unknown means the BTSplus mainline is not yet fully configured.

Reserved

ColdStandBy

ProvidingService

NULL

vswr

bypass

<NULL>

698DN0933412 Issue 01


Id:0900d805805b2e3b

s

- none means the BTSplus mainline hardware and/or software does not support switched beams.

- four_beams means the BTSplus mainline hardware and software supports 4 switched beams.

Validity Range

Default ValueNone.


SWBSERVSTATEswitchedBeamServState

The attribute indicates the current state of the switched beam functionality. A change of the attribute value is sent by the BTSplus mainline via CAER to the Flexi BSC product family. The values have the following meaning:

NULL Initial value if BTSplus mainline is not aligned or default value if the BTSplus mainline types does not support switched beams.

Validity Range

Default ValueNone.


SWLCFIDswLoadCurrentFileId

This attribute contains the fileID (name of the SW load, 12 byte) of the software load that is currently running in the BTSplus mainline. A SW load is the SW for the whole NE, that is able to run on the processors of the NE at the same time. It consists of a certain number of SW images, that are not shown to the user for the BTSplus mainline.

Notes on validity range:

ASCII String: 'HScnvvss.SWL" (swLoad-header file), where:

none

NULL

DN0933412 Issue 01699


s

Id:0900d805805b2e3b


01 = Ciphering A5.0 + A5.1 + A5.2

02 = Ciphering A5.0 + A5.2 12




Validity Range

Default ValueNone.

Contained in the following commands: GET BTSM SWL

SWLCVERswLoadCurrentFileVersion

This attribute contains the version number of the software load (26 bytes) that is cur-rently running in the BTSplus mainline. Under normal operation conditions it is the same as the version number of the swLoadIntended (SWLDINT). If the latter SW load is cor-rupted, the swLoadCurrentVersion is identical to the version number of the swLoad-Safety (SWLDSAF) or the version number of the third SW load that is stored in the BTSplus mainline (the dischargeable one). It is guaranteed that only SW loads are auto-matically started by the BTSplus mainline, which have been executed on that BTSplus mainline before.


ASCII String:cn-hh-vv-ii-ss-pp_yy-mm-dd, where:


01 = Ciphering A5.0 + A5.1 + A5.2

02 = Ciphering A5.0 + A5.2 12



01 = BS20, BS21E, BS60, BS61E or BS22

04 = BS240, BS241, BS240XL, BS240SR, BS241SR,

BS240XLSR, BS40, BS40II, BS41, BS82II, BS82,

BS240XS, BS288


ii Version part (sub-feature package code)


700DN0933412 Issue 01


Id:0900d805805b2e3b

s

00 = independent (e.g. loadable boot/test SW

01 = BS240, BS241, BS240XL, BS40, BS40II, BS41,

BS82II

05 = BS82

06 = BS240XS, BS288


pp Patch version (usually 00)

yy-mm-dd production date (optional)

Validity Range

Default ValueNone.

Contained in the following commands: GET BTSM SWL

SWLDINTswLoadIntended

This attribute is divided into 2 parts and defines the file ID (=file name) and version number of the SW load stored in the BTSplus mainline, that has been activated over the Abis- or T-interface with the latest 'Activate SW' message. This SW load is automatically activated from the BTSplus mainline firmware at power on time.

The file ID (= file ID for a SW load) and the version number () are supplied by the BTSplus mainline after the 'Activate SW' message was sent. The value for both parts is 'not valid', if there was no 'Activate SW' message before, or "swLoadCurrent", if the intended SW load is corrupted.


swLoadIntendedFileId: Coding according to swLoadCurrentFileId

Default Value: 0"filename.ext"

Octet #15 contains the ASCII character ":".

swLoadIntendedVersion: Coding according to swLoadCurrentVersion

Default Value: "cn-hh-vv-ii-ss-pp_yy-mm-dd"

The value 'not valid' for this attribute is indicated via '0' as byte 3.

Validity Range



DN0933412 Issue 01701


s

Id:0900d805805b2e3b

Default ValueNone.

Contained in the following commands: GET BTSEP SWL

SWLDSAFswLoadSafety

This attribute is divided into 2 parts and describes the file ID (= file ID for a SW load) and the version number () of the SW load stored in the BTSplus mainline, that is identified by the operator at the OMC or LMT Evolution (via a 'Set Attribute' message at the Abis- or T- interface or a M-SET service at the O-interface) as the most trusted SW load (in the sense of its ability to handle the Abis-link to build up a connection to the Flexi Flexi BSC product family product family). It is used if the swLoadIntended is damaged in some way. There is no alignment to one of the SW loads stored on the Flexi Flexi BSC product family product family master database. It is even not necessary, that this SW load is stored in the Flexi Flexi BSC product family product family master database. The iden-tification of a SW load as the safety one is only accepted by the BTSplus mainline, if the identified load has been activated and executed on this BTSE before. It is recommended that an update of the attribute is performed in each release and that the swLoad of the previous release is used as 'swLoadSafety'.

The value 'not valid' indicates that the safety SW load is corrupted or has not been iden-tified by the operator.


swLoadSafetyFileId: Coding according to 'swLoadCurrentFileId'

default value: 0"filename.ext"

Octet #15 contains the ASCII character ":".

swLoadSafetyVersion: Coding according to 'swLoadCurrentVersion'

default value: "cn-hh-vv-ii-ss-pp_yy-mm-dd"

The value 'not valid' for this attribute is indicated via '0' as byte 3.

Validity Range

Default ValueNone.

Contained in the following commands: GET BTSEP SWL, SET BTSEP

SWLDSTswLoadsStored


702DN0933412 Issue 01


Id:0900d805805b2e3b

s

This attribute contains the file IDs (= file ID for a SW load) and version numbers of up to three SW loads, that are stored in the Flash Eprom. The attribute is divided into 3 main parts, each part split up in the fileID and file version of one SW load.

In principle there are two different 'kinds' of values for one load version: one indicating the file ID and load version number of the SW load of the BTSplus mainline, that has been successfully downloaded and that has been recognized by the BTSplus mainline as a complete load; the second one, the 'not valid' value, indicating that no load has been downloaded into that partition of the Flash Eprom, or that the download is not com-plete, or that the stored SW load is corrupted as the check sum is not correct any more.

Octets #15, #55 and #93 contain the ASCII character ":".

The value 'not valid' is indicated as 0 (hexadecimal) for the octets #3 or #42 or #81.

Validity Range

Default ValueNone.

Contained in the following commands: GET BTSEP SWL

SYNCHROsynchro

new information

Validity Range

Default ValueNone.

Contained in the following commands:None.

SYNCSRCsyncSource

This attribute specifies the preferred synchronization source, i.e. whether the BTSplus mainline should be synchronized via Abis or to a 3rd party GPS receiver.

If the attribute value is extGPS further following attributes become relevant:

• enableInterSiteSync • burstNumberOffset • frameNumberOffset

3 to 3 items of


NO

YES

DN0933412 Issue 01703


s

Id:0900d805805b2e3b

• maxPhaseError • maxResyncTime

By setting the syncSource attribute to ext_1pps_only the BTSE 1 is synchronized to an external device which delivers 1pps pulses. There is no switching to a secondary syn-chronization source if the 1pps signal fails.

The attribute "1pps only" is supported only for COBA4P12v2 and CESCOBA.

Validity Range

Default Value


SYNCSTATsyncState

This attribute indicates the details of the synchronisation process of the BTSplus main-line.

Validity Range

Default ValueNone.


SYSIDcellAllocationNumber

This attribute indicates the frequency band used by the traffic channels.

abis

extGPS

ext_1pps_only

abis

init

ready

abis

abisHoldMode

syncUnit

syncUnitHoldMode

704DN0933412 Issue 01


Id:0900d805805b2e3b

s

Validity Range

Default ValueNone.


BB900

DCS1800

F2ONLY900

EXT900

PCS1900

GSMR

GSMDCS

GSM850

GSM850PCS

GSM850DCS

DN0933412 Issue 01705


t

Id:0900d805805b2e3d

t

T200t200

This attribute contains values for the LapDm timer T200 to be used on different control channels.

Validity Range

Default ValueSDCCH 29 ms

FACCH/Full rate 31 ms

FACCH/Half rate 38 ms

SDCCH SAPI3 90 ms

SACCH with TCH SAPI0 70 ms

SACCH with SDCCH 29 ms

SACCH with TCH 168 ms


T3105btsTimer3105(*10ms)

This attribute contains the value of the timer T3105, which is used for the repetition of the PHYSICAL INFORMATION message.

The attribute step size is 10 msec.

Validity Range

Default Value 1 (corresponding to 10 ms)


sdcchSAPIO 0 - 255

facchTCHF 0 - 255

facchTCHH 0 - 255

saccchTCHSAPIO 0 - 255

sacchSDCCH 0 - 255

sdcchSAPI3 0 - 255

sacchTCHSAPI3 0 - 255

1 - 254

706DN0933412 Issue 01


Id:0900d805805b2e3d

t

T3115t3115(*10ms)

T3115 is a timer to define the repetition rate of sending the VGCS UPLINK GRANT message. In case of a ASCI-call the network grants the uplink to one mobile station by sending a VGCS UPLINK GRANT message to the mobile station. After having sent this message the BTSplus mainline starts T3115 to repeat this message as long as a counter not reached the value of ny2 or a correctly decoded frame was received.

(value indicated in milliseconds; step size 10 ms)

Validity Range

Default Value 4 (corresponding to 40 ms)


T3151uplBusyRepRate

This attribute determines the repetition rate for the “upl_busy” message per cell. Default suggested value: 3 sec.

Validity Range

Default ValueNone.


TAADJtaAdjust(microseconds)

This attribute takes the propagation delay created on the BTSplus mainline internal signal path into account. It comprises both transmit and receive direction i.e. it is the sum of the transmit delay and the receive delay. The attribute taAdjust refers to the whole cell.

(value indicated in nanoseconds; step size 100 ns).

Validity Range

Default Value 0 (0 nanoseconds)

1 - 254

1 - 9

0.0 - 10.0

DN0933412 Issue 01707


t

Id:0900d805805b2e3d


TCCtxCoherentComb

Attribute reserved for future implementation.

Validity Range

Default Value

Contained in the following commands: CREATE FCUMAIN, GET FCUMAIN, SET FCUMAIN

TCCCHLDIthresholdCcchLoadIndication

This attribute is used if the Paging Overload Handling is active in the BTSplus mainline (refer to "periodCCHLoadInd"), to stop the Paging Overload Regulation, when the Paging Load goes below the threshold.

Suggested value is: 50 (hex).

Note that when Paging Overload is active, all Pagings with IMSI are discharged until the Paging Load goes below the threshold.

Note: in case of ASCI enabled in the cell, that is P1 Rest Octets for NCH info are set in Paging Request Type 1, only one IMSI could fit in a Paging Request Type 1 and even though Paging Load is only 50%, there is not enough space for the second IMSI in Paging Request Type 1. In this case it could make sense to set the threshold to lower values but take care that meanwhile all Pagings with IMSI are discharged.

The attribute value is indicated in %.

Validity Range

Default Value 100%


TRUE

FALSE

FALSE

0 - 100

708DN0933412 Issue 01


Id:0900d805805b2e3d

t

TDMAPtdmMapping

This attribute determines the mapping of the payload data to internal TDM ports of virtual BPORT corresponding to the given instance of CESPW. For each payload time slot (pTs), which is contained in the UDP stream the target time slot number on the virtual bport has to be set. Only subsequent payload time slots beginning with pTs1 can be selected. The value 0 means no mapping.

Validity Range

pTs1 0 - 31

pTs2 0 - 31

pTs3 0 - 31

pTs4 0 - 31

pTs5 0 - 31

pTs6 0 - 31

pTs7 0 - 31

pTs8 0 - 31

pTs9 0 - 31

pTs10 0 - 31

pTs11 0 - 31

pTs12 0 - 31

pTs13 0 - 31

pTs14 0 - 31

pTs15 0 - 31

pTs16 0 - 31

pTs17 0 - 31

pTs18 0 - 31

pTs19 0 - 31

pTs20 0 - 31

pTs21 0 - 31

pTs22 0 - 31

pTs23 0 - 31

pTs24 0 - 31

pTs25 0 - 31

pTs26 0 - 31

pTs27 0 - 31

pTs28 0 - 31

pTs29 0 - 31

DN0933412 Issue 01709


t

Id:0900d805805b2e3d

Default ValueNone.


TEItei

This attribute contains the Terminal Endpoint Identifier used in the layer2 addressing on the Abis-Interface for the logical O&M or Radio Signalling Link.

The values 0..63 of the validity range refers tro the 'Initial TEI'

Validity Range

Default ValueNone.

Contained in the following commands: GET BTSM NOSWL, GET TRX

TESTMODEenableTestMode

This attribute determines whether transceiver test mode can be activated. This is only possible for non BCCH transceivers if their administrative state is "locked". If the test mode is activated, the transceiver sends dummy bursts on all time slots with the fre-quency dlTestFrequency and the output power reduced by testPowerReduction. All other transceiver attributes are meaningless in test mode in the DL direction. In UL direc-tion the transceiver attributes for normal operation apply.

If the test mode is deactivated, the attributes for normal operation apply in DL direction again and the attributes dlTestFrequency and testPowerReduction are meaningless instead.

Validity Range

Default ValueNone.

pTs30 0 - 31

pTs31 0 - 31

0 - 128

TRUE

FALSE

710DN0933412 Issue 01


Id:0900d805805b2e3d

t


TESTMONtestMonitor

Up to 6 testMonitorInfo fields can present (depend on the board).

Working phases:

ACDCP PreliminaryTestsAcdcp CU PreliminaryTestsCu

CheckAlarmStatusAcdcp BootEepromTestCu

EndTestAcdcp SerialEepromTestCu

ACT PreliminaryTestsAct LocalTestLoopCu

CheckAlarmStatusAct EndTestCu

EndTestAct DILNA PreliminaryTestsDilna

BATTERY PreliminaryTestsBattery CheckAlarmStatusDilna

CheckAlarmStatusBattery EndTestDilna

EndTestBattery DIDCTMA PreliminaryTestsDidctma

COBA PreliminaryTestsCoba CheckAlarmStatusDidctma

BootEepromTestCoba EndTestDidctma

SerialEepromTestCoba DUDCTMA PreliminaryTestsDudctma

EndTestCoba CheckAlarmStatusDudctma

COSA PreliminaryTestsCosa EndTestDudctma

SerialEepromTestCosa DULNA PreliminaryTestsDulna

EndTestCosa CheckAlarmStatusDulna

EndTestDulna

Working phases:

DUVSWR PreliminaryTestsDuvswr LMU PreliminaryTestsLmu

CheckAlarmStatusDuvswr CheckAlarmStatusLmu

EndTestDuvswr EndTestLmu

FANP PreliminaryTestsFanp FTNFP PreliminaryTestsFtnfp

CheckAlarmStatusFanp CheckAlarmStatusFtnfp

EndTestFanp EndTestFtnfp

FCUMAIN PreliminaryTestsFcumain FVSWRP PreliminaryTestsFvswrp

BootEepromTestFcumain CheckAlarmStatusFvswrp

SerialEepromTestFcu-main

EndTestFvswrp

DN0933412 Issue 01711


t

Id:0900d805805b2e3d

Validity Range

EndTestFcumain SYNCBTSE PreliminaryTestsSyncbtse

FCUTR PreliminaryTestsFcutr ResyncTestSyncbtse

LocalTestLoopFcutr EndTestSyncbtse

EndTestFcutr TMA PreliminaryTestsTma

CheckAlarmStatusTma

EndTestTma

1 to 6 items of

phaseId PreliminaryTestsAct

PreliminaryTestsCu

PreliminaryTest-sCoba

PreliminaryTests-Cosa

PreliminaryTests-Fanp

PreliminaryTests-Dilna

PreliminaryTestsDu-vswr

PreliminaryTests-Dulna

PreliminaryTests-Battery

PreliminaryTestsB-com

PreliminaryTest-sTma

PreliminaryTests-Dudctma

PreliminaryTests-Didctma

PreliminaryTest-sAcdcp

PreliminaryTests-Fvswrp

PreliminaryTestsFt-nfp

PreliminaryTest-sLmu

712DN0933412 Issue 01


Id:0900d805805b2e3d

t

PreliminaryTestsS-dulna

PreliminaryTestsS-dusec

PreliminaryTestsS-dusubsec

PreliminaryTestsS-dutxsw

EndTestAct

EndTestCu

EndTestCoba

EndTestCosa

EndTestFanp

EndTestDilna

EndTestDuvswr

EndTestDulna

EndTestBattery

EndTestTma

EndTestDudctma

EndTestDidctma

EndTestFvswrp

EndTestFtnfp

EndTestLmu

EndTestSdulna

EndTestSdusec

EndTestSdusubsec

EndTestSdutxsw

Seria-lEepromTestCu

SerialEepromTest-Coba

SerialEepromTest-Cosa

BootEepromTestCu

BootEepromTest-Coba

CheckAlarmStatus-Act

DN0933412 Issue 01713


t

Id:0900d805805b2e3d

CheckAlarmStatus-Fanp

CheckAlarmStatus-Dilna

CheckAlarmStatus-Duvswr

CheckAlarmStatus-Dulna

CheckAlarmStatus-Battery

CheckAlarmStatus-Bcom

CheckAlarmStatu-sTma

CheckAlarmStatus-Dudctma

CheckAlarmStatus-Didctma

CheckAlarmSta-tusAcdcp

CheckAlarmStatus-Fvswrp

CheckAlarmStatus-Ftnfp

CheckAlarmStatus-Lmu

CheckAlarmSta-tusSdulna

CheckAlarmSta-tusSdusec

CheckAlarmSta-tusSdusubsec

CheckAlarmSta-tusSdutxsw

LocalTestLoopCu

SerialEepromTest-Fcumain

ResynctestSyn-cBtse

PreliminaryTest-sSyncBtse

714DN0933412 Issue 01


Id:0900d805805b2e3d

t

PreliminaryTestsFc-utr

PreliminaryTests-Fcumain

LocalTestLoopFcutr

EndTestSyncBtse

EndTestBcom

EndTestFcutr

EndTestFcuMain

BootEepromTest-Fcumain

PreliminaryTestsDu-amco

CheckAlarmStatus-Duamco

EndTestDuamco

PreliminaryTestsF6dctma

PreliminaryTestsF6lna

PreliminaryTestsF6tnfP

PreliminaryTestsF6vswrP

CheckAlarmStatusF6dctma

CheckAlarmStatusF6lna

CheckAlarmStatusF6tnfP

CheckAlarmStatusF6vswrP

EndTestF6dctma

EndTestF6lna

EndTestF6tnfP

EndTestF6vswrP

EndTestAcdcp

phaseStatus Waiting

Pass

Fail

DN0933412 Issue 01715


t

Id:0900d805805b2e3d

Default ValueNone.

Contained in the following commands: GET BTSETEST

TESTNOtestNo

This attribute corrisponde to the instance numeber of the test object.

Validity Range

Default ValueNone.

Contained in the following commands: STOPTEST BTSEP

TESTOUTtestOutcome

This attribute informs the operator about the outcome of the current test phase. It is con-tained in the "Test Report" and can be queried by the user during the test via a "GET".

INCONCLUSIVE indicates that no "Pass" or " Fail" outcome has been determinated yet.

PASSED and FAIL are possible for all phases of the test. Further information (e.g. about the number of the failed test phase) is only available in the test report which is sent at the end of the test.

PASSED generally indicates that the test was executed correctly and no problems were found.

FAILED generally indicates that the test was executed correctly and a problem was found.

Validity Range

Default ValueNone.


Running

0 - 255

INCONCLUSIVE

PASSED

FAILED

716DN0933412 Issue 01


Id:0900d805805b2e3d

t

TESTPWRREDtestPowerReduction

This attribute defines the output power reduction if the transceiver test mode is acti-vated. Its value is adapted to the static power reduction range.

The default value means that the testPowerReduction is not set and as a consequence the test mode can not be enabled.

Validity Range

Default ValueNone.


TESTSTtestState

This attribute defines the current state of the test.

Validity Range

Default ValueNone.


TEXTtext

new information

Validity Range

Default ValueNone.

Contained in the following commands: None.

<ANY>

IDLE

INITIALIZING

TESTING

TERMINATING


DN0933412 Issue 01717


t

Id:0900d805805b2e3d

TIMEDELAYtimeDelay(sec)

This parameter is sent in the 'Activate SW Delayed' command by the Flexi BSC product family. It identifies the number of seconds that the BTSplus mainline waits before acti-vating the specified SW version.

Validity Range

Default ValueNone.

Contained in the following commands: ACTIVATE_DELAYED BTSM

TNCHtNCH(*multiframes)

This attribute describes the minimum repetition period for the Notification/NCH mes-sages. The NCH blocks are a subset of the CCCH blocks reserved for AGCH.

The attribute doesn't denote the minimum repetition period within one CCCH block. Within a CCCH block 1 ... 7 NCH blocks can be used.

(the attribute is indicated in units of multiframes)

Validity Range

Default Value 16


TNFTARGFtnfTargetFrequency

0 - 254

1 - 254

This attribute defines the target frequency the TNF is to be tuned. It is set internally by the BTSplus mainline after creation, frequency update or deletion of any functional-related TRX instance and is read-only for any external interface of the BTSplus mainline.

In case of "FTNFP" the attribute shows the "actual frequency" of the TNF: this means that the value of the attribute changes during the "tuning" of the TNF or during the "parking" of the TNF.

718DN0933412 Issue 01


Id:0900d805805b2e3d

t

Validity Range

Default ValueNone.

Contained in the following commands: GET F6TNFP, GET FTNFP

TRXAREAtrxArea

This attribute specifies whether a TRX belongs to a concentric cell and to which area it belongs.

The attribute also indicates whether the concentric cell intracell handover algorithm is enable (value 01 or 02) or disabled (value 00). If it is enabled it will be executed before the conventional inter/intracell handover algorithms.

Validity Range

Default Value NONE - TRX doesn't belong to a concentric cell



Hex Decimal

GSM900 "BB900" 0001 ... 007C 1 ... 124


0000 ... 007C

03CF ... 03FF

0 ... 124

975 ... 1023


0000

0000 ... 007C

03CF ... 03FF

0000

0 ... 124

975 ... 1023

DCS 1800 "DCS1800"

0200 ... 0375 512 ... 885

PCS 1900 0200 ... 032A 512 ... 810

GSM-R not supported not supported

ANY (only Parking position)

FF00 65280

0 - 65535

<NULL>

NONE

INNER

COMPLETE

DN0933412 Issue 01719


t

Id:0900d805805b2e3d

TRXCPBLtrxCapability

This attribute reflects the real capabilities of a TRX after harware has been assigned to it. It is set after the TRX allocation by the BTSplus mainline. If the TRX object is created in advance or hardware is not allocated to the TRX the attribute has the value unknown. It is read-only from the Abis/LMT Evolution point of view (GET TRX). The Flexi BSC product family has to perform a GET on this attribute each time the TRX performs a tran-sition to "enabled".

Validity Range

Default Value UNKNOWN


TRXFREQcarrierFrequency

UNKNOWN

GSM

EDGE

This attribute defines the radio frequency allocated and available to a cell.


Decimal

GSM900 "BB900" 1 ... 124


0 ... 124

975 ... 1023

GSM-R 955 ... 974


0 ... 124

975 ... 1023

DCS 1800 "DCS1800"

512 ... 885

PCS 1900 512 ... 810

GSM-DCS 0 ... 124

975 ... 1023

512 ... 885

GSM850 128 ... 251

720DN0933412 Issue 01


Id:0900d805805b2e3d

t

Validity Range

Default ValueNone.


TRXMDtrxMode

This attribute defines the mode of a TRX that required from the operator. Depending on it's value the BTSplus mainline tries to allocate an appropriate hardware to the TRX object.

Validity Range

Default Value GSM


TSCtrainingSequenceCode

GSM850-PCS 128 ... 251

512 ... 810

GSM850-DCS 128 ... 251

512 ... 885

0 to 64 items of

0 - 1023

GSM

EDGE

This attribute contains the Training Sequence Code (TSC) of a radio channel. If the TSC value is set NULL, TSC is always equal to the BCC (Base Transceiver Station Colour Code) for both control and traffic channels.

Notes:

1. A NULL (FF) value is possible for both control and traffic channels and signifies that the BCC (BS colour code of attri-bute "bsIdentityCode / BSIC") shall be used as the TSC value for the channel.

DN0933412 Issue 01721


t

Id:0900d805805b2e3d

Validity Range

Default ValueNone.


TSLPOOLtslPool

The BportNumber validity range is specified as follows:

00..07 (not only for BS82II)

2. In case of a control channel only the NULL (FF) value can be specified, i.e. only a reference to the BCC is allowed.

TSC_00

TSC_01

TSC_02

TSC_03

TSC_04

TSC_05

TSC_06

TSC_07

TSC_is_BCC_of_BSIC

This attribute defines the pool of Abis timeslots (TSL) on a granularity of 16Kbit/s subslots (SSL) which can be used for traffic within a BTSplus mainline.

The attribute contains an entry of 17 bytes for each used BPort:

- the first byte indicates the number of the BPort (BPortNum-ber),

- the following 16 bytes (BPortBitmap) contain a bitmap - the subslots which can be used for traffic are indicated by setting the corresponding bits in the BPortBitmap bytes to 1. In case of PCM24 the TSL 0 and TSL 25-31 don't exist, therefore the related bits are set to 0.

Out of this pool the Flexi BSC product family assigns dynamically the Abis timeslots to a call. The information about the actual timeslot/sub-slot ("Abis Resources") is sent by the Flexi BSC product family to the BTSplus mainline on the radio signalling link at the begin of each call ("channel Activation") and during the call ("Modify Abis Channel") if a modification is necessary.

722DN0933412 Issue 01


Id:0900d805805b2e3d

t

00..03 (only for BS82II)

Validity Range

Default ValueNone.


TSYNCtSync(*10ms)

This attribute defines the timer value, that will be used by the BTSplus mainline to super-vise timeout of TRAU frame handling. This timer is used only if a BTSplus mainline-TRAU traffic connection is already established. If the BTSplus mainline detects a loss of frame synchronisation it starts the timer tSync. It is cleared, if a frame is received again. If it expired, a connection failure indication is reported to the Flexi BSC product family.

A change of the attribute becomes effective after the reception of a TRAU frame i.e. in the case after 20 ms and in the worst case after the expiration of the current timer.


Validity Range

Default Value 1000 (corresponding to 10 sec.)


TSYNCDtSyncD(*10ms)

This attribute defines the timer value, that will be used by the BTSplus mainline to super-vise timeout of downlink TRAU frame handling in case of 14.5kbit/s data connections. If loss of frame synchronization detected by the BTSplus mainline it starts a timer TsyncD and starts sending Data TRAU Frames in the uplink direction to trigger the TRAU to start

1 to 8 items of

BPortNumber BPORT0

BPORT1

...

BPORT7

BPortBitMap 16 to 16 items of

B#0 - B#11111111

10 - 10000

DN0933412 Issue 01723


t

Id:0900d805805b2e3d

sending Data TRAU Frames in the downlink direction to be used for downlink Synchro-nization Recovery. TsyncD is reset every time frame synchronization is again obtained. If TsyncD expires before frame synchronization is again obtained, a connection failure indication is reported to the Flexi BSC product family.


Validity Range



TSYNCRtSyncR(*10ms)

This attribute defines the timer value, that will be used by the BTSplus mainline to super-vise the uplink Synchronization Recovery in case of 14.5kbit/s data connections. When the BTSplus mainline receives an Extended Data TRAU Frame indicating an Uplink Frame Error and which has no errors on the synchronization pattern and the control bits, it starts the timer TsyncR. TsyncR is reset every time three consecutive TRAU frames are received without Uplink Frame Error indication, without errors on the frame synchro-nization pattern and on the control bits. If TsyncR expires before frame synchronization is again obtained, the BTSplus mainline starts sending Data TRAU Frames in the uplink direction to be used for uplink Synchronization Recovery.


Validity Range



TSYNCUtSyncU(*10ms)

This attribute defines the timer value, that will be used by the BTSplus mainline to super-vise timeout of uplink TRAU frame handling in case of 14.5kbit/s data connections. When the BTSplus mainline receives an Extended Data TRAU Frame indicating an Uplink Frame Error and which has no errors on the synchronization pattern and the control bits, it starts a timer TsyncU. TsyncU is reset every time three consecutive TRAU

10 - 10000

10 - 10000

724DN0933412 Issue 01


Id:0900d805805b2e3d

t

frames are received without Uplink Frame Error indication, without errors on the frame synchronization pattern and on the control bits. If TsyncU expires before frame synchro-nization is again obtained, a connection failure indication is reported to the Flexi BSC product family.


Validity Range



TTRAUtTrau(*10ms)

This attribute defines the timer value, that will be used by the BTSplus mainline to super-vise timeout of TRAU datalink (traffic) at connection establishment or handover. It is set with sending the first TRAU dataframe uplink and cleared, when the first frame downlink arrives. If it is expires, a connection failure indication is reported to the Flexi BSC product family.


Validity Range



TUPLREPtimerUplinkReply

The attribute defines the timer for the repetition of the UplinkFree message with "reply on uplink access request".

Validity Range


10 - 10000

10 - 10000

5 - 60

DN0933412 Issue 01725


t

Id:0900d805805b2e3d


TXBMAXFtxBandMaxFreq(kHz*100)


Validity Range

Default ValueNone.


TXBMINFtxBandMinFreq(kHz*100)


Validity Range

Default ValueNone.


TXDIVTSEXCPTtxDivTimeShiftExcept

The TX Diversity Time Shift operation might be disabled for certain type of TX burst, which are timing-sensitive (e.g. SCH channel for location services). In this case the parallel transmission of the slave CU is disabled when the certain burst type is going to be transmitted. The attribute txDivTimeShiftExcept allows to configure time slots or logical channels, which shall be excluded from applying the Tx Diversity Time Shift. The call processing software supervises bursts to be transmitted and disables the slave transmission if the burst should not be transmitted. The attribute is only valid if the feature Tx Diversity Time Shift is enabled (attribute enableTxDivTimeShift). A change of the attribute value causes a traffic interruption on all TRX of the BTS and a restart of the feature Tx Diversity Time Shift.

0 - 65535

<NULL>

0 - 65535

<NULL>

726DN0933412 Issue 01


Id:0900d805805b2e3d

t

Validity Range

Default Value NONE (diversity applied for all channel)


TXDIVTSPARtxDivTimeShiftParam

The attribute txDivTimeShiftParam is used to set the time shift between the transmit signals of the master and the slave CU. The time shift is specified on a symbol base in the range between -5 .... +5 symbols in steps of 0,25 symbols. A symbol represents one information unit (e.g. 1 bit) is transmitted within 3,693 s. The attribute is only valid if the feature Tx Diversity Time Shift is enabled (attribute enableTxDivTimeShift). A change of the attribute value causes a traffic interruption on all TRX of the BTS and a restart of the feature Tx Diversity Time Shift.

Validity Range

Default Value -1 symbol, but has to be evaluated during field tests


TXLEVADJtxLevAdjust(dB)

NONE

SCH

BCCHTRXTS0

BCCHTRX

-5.00 - 5.00

The attribute specifies the value needed to adjust the TXLEV value of the transmit path of the CU/FCUTR. For a FCUTR with an even object instance the related transmit path is TX0, for a FCUTR with an odd object instance the related transmit path is TX1.

The attribute value which will be used to compensate attenuation effects caused by combiner equipment, RF cabling and amplification effects of optionally used booster equipment. The operator has to set a reasonable value according the following formula:

txLevAdjust = Attention Factor of used Combiner + Attention Factor of RF Cable - Amplification Factor of used Booster

DN0933412 Issue 01727


t

Id:0900d805805b2e3d

Validity Range

Default Value

Contained in the following commands: CREATE CU, CREATE FCUTR, GET CU, GET FCUTR, SET CU, SET FCUTR

TXSIGLEVADJtxSigLevAdjust

The attribute specifies the signal level adjust values which shall be applied to the transmit paths oftransceivers using the same frequency band as the BCCH transceiver.

Validity Range

Default ValueNone.


TXSIGLEVADJCtxSigLevAdjustCompl

The attribute specifies the signal level adjust values which shall be applied to the transmit paths oftransceivers using the complementary frequency band. The value is only meaningful in case of a multiband cell.

Validity Range

Default ValueNone.


TYPOFETHtypeOfEthernet

The attribute defines the type of Ethernet framing which is used for transmitted packets.

-63.0 - 63.0

0.0

<ANY>

<ANY>

728DN0933412 Issue 01


Id:0900d805805b2e3d

t

Validity Range

Default Value

Contained in the following commands: GET COBAETHINTF, SET COBAETHINTF

TYPRACKtypeOfBtse

This attribute identifies the type of BTSplus mainline.

This attribute defines the type of the rack.

For the BTSplus mainline family given by 'hh=04' , it is possible to set the value of typeOfBTSE for rack #0 only once - if the operator wants to change the stored value he has to format the FLASH EPROM first or delete the Flash-DB.

For an rack instance number <> 0 an update of the attribute is blocked by the BTSplus mainline SW. This means if an operator wants to change the attribute value in a rack <> 0 he has to delete the rack first and then recreate it with the new value of typeOfBTSE.

Below are reported more detailed information about the validity range:

BS20 (value only possible for rack #0)

BS21E (value only possible for rack #0)



BS61E (value only possible for rack #0)

not_valid (value possible only in LMT Evolution phase 2 as result of a

GET command for rack #0)

Validity RangeIn commands CREATE RACK, SET RACK:

ethernet_II

iEEE802_SNAP

ethernet_II

BS240

BS241

BS240SR

BS241SR

BS40

BS40II

BS41

BS240XL

BS240XLSR

DN0933412 Issue 01729


t

Id:0900d805805b2e3d

In commands GET RACK:

Default ValueNone.

Contained in the following commands: CREATE RACK, GET RACK, SET RACK

BS82II

BS240

BS241

BS240SR

BS241SR

BS40

BS41

BS240XL

BS240XLSR

BS240XS

BS240SWB

BS241SWB

BS240XLSWB

BS82II

BS40II

not_valid

730DN0933412 Issue 01


Id:0900d805805b2929

v

v

VENDNAvendorName

This attribute type identifies the vendor of the associated Object. This attribute is defined as an "ASCII String" and is not terminated by a NULL character.

Validity Range

Default ValueNone.


VGSCULFTvoiceGroupUplinkFree(*10ms)


If the uplink of the group call is free, and also no talker is in the cell on a dedicated channel, the network provides an UPLINK FREE message on the main signalling channel periodically. The timer vgscULFreeTimer plus an offset of 440ms defines the repetition rate of sending this message; the BTSplus mainline limits the maximum repetition rate on 1440ms.

The BTSplus mainline stops the timer when the uplink is free again, and also no talker is in the cell on a dedicated channel.

Setting this attribute to the lowest possible value means that a talker request by a mobile station can be started with most minimal delay. On the other side, a high repetition rate of UPLINK FREE messages leads to a certain speech frame erasure rate, which may cause an audible degradation of the speech quality on the group downlink channel; although there is no talker in the group call at this state, there may be dispatchers speaking on the group downlink channel.

vgcsULFreeTimer value (decimal)

vgcsULFreeTimer

* 10 ms

UPLINK FREE

repetition rate

1 10 ms 450 ms

2 20 ms 460 ms

3 30 ms 470 ms

: : :

100 100 ms 1440 ms

DN0933412 Issue 01731


v

Id:0900d805805b2929

Validity Range

Default Value 10 ms


VLANIDvlanId

This attribute defines optional virtual LAN (VLAN) identifier. The vlanId is used by all pseudo wires (CESPW) of the CESTUNNEL instance.

If vlanId is set to none the VLAN tag in the Ethernet Header will be omitted. The object must be locked before modifying the vlanId via the SET command.

Validity RangeIn commands CREATE CESTUNNEL, SET CESTUNNEL:

In commands GET CESTUNNEL:

Default ValueIn moc(s) CESTUNNEL:

None.

In moc(s) CESTUNNEL:


VSWRTDBvswrThresholdDb

This attribute determines the repetition rate for the “upl_busy” message per cell.

Default suggested value: 3 sec. The value sets the TX return loss threshold value of an MFDUAMCO antenna branch. The value is aligned with the combiner if a MFDUAMCO is equipped.

The object is set to degraded if the low threshold is crossed. Crossing the high threshold leads to disabled state.

Default Value: 10 ms

1 - 100

0 - 4094

<NULL>

<ANY>

NULL

732DN0933412 Issue 01


Id:0900d805805b2929

v

The attribute is meaningless if an old DUAMCO or FDUAMCO is equipped. Neverthe-less the value is stored in the database and used if a MFDUAMCO will be equipped later on.

Validity Range

Default Value

Contained in the following commands: CREATE DUVSWR, CREATE F6VSWRP, GET DUVSWR, GET F6VSWRP, SET DUVSWR, SET F6VSWRP

LOW_2_0_HIGH_3_0

LOW_2_5_HIGH_3_5

LOW_3_0_HIGH_4_0

LOW_2_0_HIGH_3_0

DN0933412 Issue 01733


w

Id:0900d805805b292b

w

WDDUVSWRwiringDuamcoVswr

This attribute represents the wiring between a DUAMCO_VSWR and several CUs (TX output)/FCUMAINs (TX0 output or TX1 output) which the operator has to perform at installation time.

In case of FCUMAIN with fcuMode=singleCUMode or in case of CU, the DUAMCO_VSWR and the CUs/FCUMAINs are in the same rack and belong to the same cell.

In case of FCUMAIN with fcuMode=douleCUMode, the objects can belong to two differ-ent cells.

Due to the physical properties of the DUAMCO_VSWR, up to 4 CUs/FCUMAINs can be connected."

From SW point of view the FDUAMCO is considered just as an HW variant of the DUAMCO, so an extra term like 'FDUAMCO_DUVSWR' is not introduced.

The BTSplus mainline SW does not check if the entered value is compatible with typeOf-BTSE; e.g. an input of CU7 is not rejected in a BTSplus mainline BS40 although BS40 allows only the creation of CU 0-3.

g All CUs/FCUMAINs which are listed in a GET DUVSWR for WDDUVSWR have to be locked before the cabling of one of these CUs/FCUMAINs can be removed from WDDUVSWR.

g The UIDL construct used is enumList.

Below are reported some detailed information about validity range values:

CU0 ... CU11 (CU4 ... CU7 only for BS240 and BS241)

(CU4 ... CU11 only for BS240XL)

FCUMAIN0TX0

FCUMAIN0TX1

:

FCUMAIN11TX0

FCUMAIN11TX1

(FCUMAIN4TX0 ... FCUMAIN7TX1 only for BS240

and BS241)

:

(FCUMAIN4TX0 ... FCUMAIN11TX1 only for

BS240XL)

Validity Range

1 to 4 items of

CU0

CU1

734DN0933412 Issue 01


Id:0900d805805b292b

w

Default ValueNone.

CU2

CU3

CU4

CU5

CU6

CU7

CU8

CU9

CU10

CU11

FCUMAIN0TX0

FCUMAIN0TX1

FCUMAIN1TX0

FCUMAIN1TX1

FCUMAIN2TX0

FCUMAIN2TX1

FCUMAIN3TX0

FCUMAIN3TX1

FCUMAIN4TX0

FCUMAIN4TX1

FCUMAIN5TX0

FCUMAIN5TX1

FCUMAIN6TX0

FCUMAIN6TX1

FCUMAIN7TX0

FCUMAIN7TX1

FCUMAIN8TX0

FCUMAIN8TX1

FCUMAIN9TX0

FCUMAIN9TX1

FCUMAIN10TX0

FCUMAIN10TX1

FCUMAIN11TX0

FCUMAIN11TX1

DN0933412 Issue 01735


w

Id:0900d805805b292b

Contained in the following commands: CREATE DUVSWR, GET DUVSWR, SET DUVSWR

WDFTNFPwiringDataFtnfp

The following values are possible for 'CU_wiring':

CU0 ... CU11 (CU4 ... CU7 only for BS240 and BS241)


FCUMAIN0TX0

FCUMAIN0TX1

:

FCUMAIN11TX0

FCUMAIN11TX1

(FCUMAIN4TX0 ... FCUMAIN7TX1 only for BS240

and BS241)

:

(FCUMAIN4TX0 ... FCUMAIN11TX1 only for

BS240XL)

This attribute defines the pool of Abis timeslots (TSL) on a granularity of 16Kbit/s subslots (SSL) which can be used for traffic within a BTSplus mainline.

This attribute represents the wiring:

- between the TX input of a FICOM_TNFP and the TX output of a CU

- between the TX input of a FICOM_TNFP and the TX0 or TX1 output of a FCUMAIN

and furtheron it describes to which FICOM_VSWR the FICOM_TNFP is related to. The wiring has to be done by the operator at installation time.

In case of FCUMAIN with fcuMode=singleCUMode or in case of CU, the FICOM_TNFP, the CU/FCUMAIN and the FICOM_VSWRP are in the same rack and belong to the same cell.

In case of FCUMAIN with fcuMode=douleCUMode, the objects can belong to two different cells.

The BTSplus mainline SW does o't check if the entered value is com-patible with typeOfBTSE; e.g. an input of CU7 isn't rejected in a BS40 although BS40 allows only the creation of CU 0-3.

Note: 'CU_wiring' is used for CU as well as for FCUMAIN, the name 'CU_wiring' has not been changed because it is used in LMT Evolu-tion-GUI/CLI.

736DN0933412 Issue 01


Id:0900d805805b292b

w

The following values are possible for 'FVSWRP wiring':

FVSWRP0

FVSWRP1

FVSWRP2

FVSWRP3

Validity Range

CUWiring CU0

CU1

CU2

CU3

CU4

CU5

CU6

CU7

CU8

CU9

CU10

CU11

FCUMAIN0TX0

FCUMAIN0TX1

FCUMAIN1TX0

FCUMAIN1TX1

FCUMAIN2TX0

FCUMAIN2TX1

FCUMAIN3TX0

FCUMAIN3TX1

FCUMAIN4TX0

FCUMAIN4TX1

FCUMAIN5TX0

FCUMAIN5TX1

FCUMAIN6TX0

FCUMAIN6TX1

FCUMAIN7TX0

FCUMAIN7TX1

FCUMAIN8TX0

FCUMAIN8TX1

DN0933412 Issue 01737


w

Id:0900d805805b292b

Default ValueNone.

Contained in the following commands: CREATE F6TNFP, CREATE FTNFP, GET F6TNFP, GET FTNFP

WDLNAwiringDataLna

This attribute represents the wiring between a DUAMCO_LNA or a DIAMCO_LNA and several CUs/FCUMAINs the operator has to perform at installation time and that is not foreseen to be fixed by the configuration rules.

In case of FCUMAIN with fcuMode=singleCUMode or in case of CU, the DUAMCO/DIAMCO_LNA and the CUs/FCUMAINs are in the same rack and belong to the same cell.

In case of FCUMAIN with fcuMode=douleCUMode, the objects can belong to two differ-ent cells.

When a second cell number is indicated (see attribute secondCellNumber), also in case of CU the objects can belong to two different cells.

Due to the physical properties of the DUAMCO_VSWR, up to 8 different Us/FCUMAINs can be connected. Each CU has a 'normal path' RX input and a 'diversity path' RX input and the operator must indicate which of them is wired to the DUAMCO/DIAMCO_LNA. The FCUMAIN supports the 'normal path' RX input, the diversity path RX input and two further Rx inputs: Rx C / N1 and Rx D / D1.

The BTSplus mainline SW does not check if the entered value is compatible with typeOf-BTSE; e.g. an input of CU7N / CU7D isn't rejected in a BS40 although BS40 allows only the creation of CU 0-3.

Validity Range (object DILNA/DULNA) are possible for 'RX_wiring n':

CU0N (CU0 normal path)

CU0D (CU0 diversity path)

:

CU11N (CU11 normal path)

FCUMAIN9TX0

FCUMAIN9TX1

FCUMAIN10TX0

FCUMAIN10TX1

FCUMAIN11TX0

FCUMAIN11TX1

FVSWRPWiring FVSWRP0

FVSWRP1

...

FVSWRP3

738DN0933412 Issue 01


Id:0900d805805b292b

w

CU11D (CU11 diversity path)

FCUMAIN0N (FCUMAIN0 normal path)

FCUMAIN0D (FCUMAIN0 diversity path)

FCUMAIN0N1 (FCUMAIN0 Rx C / N1 path)

FCUMAIN0D1 (FCUMAIN0 Rx D / D1 path)

:

FCUMAIN11N (FCUMAIN11 normal path)

FCUMAIN011D (FCUMAIN11 diversity path)

FCUMAIN11N1 (FCUMAIN11 Rx C / N1 path)

FCUMAIN11D1 (FCUMAIN011 Rx D / D1 path)

(CU4 ... CU7 only for BS240 and BS241)


(FCUMAIN4N ... FCUMAIN7D1 only for BS240 and BS241)

(FCUMAIN4N ... FCUMAIN11D1 only for BS240XL)

Validity Range

1 to 8 items of

CU0N

CU0D

CU1N

CU1D

CU2N

CU2D

CU3N

CU3D

CU4N

CU4D

CU5N

CU5D

CU6N

CU6D

CU7N

CU7D

CU8N

CU8D

CU9N

CU9D

CU10N

DN0933412 Issue 01739


w

Id:0900d805805b292b

CU10D

CU11N

CU11D

FCUMAIN0N

FCUMAIN0D

FCUMAIN0N1

FCUMAIN0D1

FCUMAIN1N

FCUMAIN1D

FCUMAIN1N1

FCUMAIN1D1

FCUMAIN2N

FCUMAIN2D

FCUMAIN2N1

FCUMAIN2D1

FCUMAIN3N

FCUMAIN3D

FCUMAIN3N1

FCUMAIN3D1

FCUMAIN4N

FCUMAIN4D

FCUMAIN4N1

FCUMAIN4D1

FCUMAIN5N

FCUMAIN5D

FCUMAIN5N1

FCUMAIN5D1

FCUMAIN6N

FCUMAIN6D

FCUMAIN6N1

FCUMAIN6D1

FCUMAIN7N

FCUMAIN7D

FCUMAIN7N1

FCUMAIN7D1

FCUMAIN8N

740DN0933412 Issue 01


Id:0900d805805b292b

w

Default ValueNone.

Contained in the following commands: CREATE DILNA, CREATE DULNA, CREATE F6LNA, GET DILNA, GET DULNA, GET F6LNA, SET DILNA, SET DULNA, SET F6LNA

FCUMAIN8D

FCUMAIN8N1

FCUMAIN8D1

FCUMAIN9N

FCUMAIN9D

FCUMAIN9N1

FCUMAIN9D1

FCUMAIN10N

FCUMAIN10D

FCUMAIN10N1

FCUMAIN10D1

FCUMAIN11N

FCUMAIN11D

FCUMAIN11N1

FCUMAIN11D1

DN0933412 Issue 01741


Nack causes

Id:0900d805805bfdaa

4 Nack causesString table for ABIS nack causes used by the LMT Evolution

H'1, Incorrect message structure

H'2, Invalid message type value

H'3, <reserved>

H'4, <reserved>

H'5, Invalid object class value

H'6, Object class not supported

H'7, BTS no. unknown

H'8, Transceiver no. unknown

H'9, Object instance unknown

H'A, <reserved>

H'B, <reserved>

H'C, Invalid attribute identifier value

H'D, Attribute identifier not supported

H'E, Parameter value outside permitted range

H'F, Inconsistency in attribute list

H'10, Specified implementation not supported

H'11, Message cannot be performed

H'12, Busy

H'13, <reserved>

H'14, <reserved>

H'15, <reserved>

H'16, <reserved>

H'17, <reserved>

H'18, <reserved>

H'19, Resource not implemented

H'1A, Resource not available

H'1B, Frequency not available

H'1C, Test not supported

H'1D, Capacity restrictions

H'1E, Physical configuration cannot be performed

H'1F, Test not initiated

H'20, Physical configuration cannot be restored

H'21, No such test

H'22, Test cannot be stopped

742DN0933412 Issue 01


Id:0900d805805bfdaa

Nack causes

H'23, Message inconsistent with physical config.

H'24, File already received

H'25, Complete file not received

H'26, File not available at destination

H'27, File cannot be activated

H'28, Request not granted

H'29, Wait

H'2A, <reserved>

H'7F, <reserved>

H'80, BTSE not able to begin DB Transmission

H'81, DB Transmission failed

H'82, Conflicting channel assignment

H'83, Specified connection does not exist

H'84, Specified Test is not running

H'85, swLoad-header not stored

H'86, swLoad-header mismatch with swImage or VAM file id

H'87, Files listed in swLoad header not stored

H'88, Request already in progress

H'89, Load has not been activated before

H'8A, Starting Time already in use

H'8B, Configuration of specified object not allowed during alignment

H'8C, Update of specified object not allowed in LMT Evolution phase 3

H’8D, Configuration of specified object not allowed during FW download

H'90, invalid file name

H'91, invalid file type

H'92, file not found

H'93, file in use

H'94, file present

H'95, file corrupted

H'96, file test failed

H'97, MO or MOT not locked

H'98, VAM check failed

H'99, VAM file not stored in Flash Eprom

H'9A, Scanner is suspended

H'9B, TEI already in use

H'9C, Update not allowed from Abis interface

DN0933412 Issue 01743


Nack causes

Id:0900d805805bfdaa

String table for LMT Evolution nack causes used by BTSE

H'9D, Update not allowed from T interface

H'9E, Update not allowed

H'9F, MO already created

H'A0, requested information exceeds maximal message length

H'A1, sw load not compatible with typeOfBTSE

H'A2, Creation out of sequence

H'A3, Invalid attribute value

H'A4, Conflicting timeslot assignment

H'A5, Deletion not possible in Phase3

H'A6, Deletion out of sequence

H'A7, Related BPort instance not created

H'A8, Configuration of remapped timeslots not possible in Phase3

H'A9, feature not released

H'AA, typeOfBTSE has to be set first

H'AB, typeOfBTSE not compatible with typeOfBTSE in other rack(s)

H'AC, max number of object instances is already created

H'AD, no redundant core board available

H’AE, TRX/LPDM related LADPLE doesn’t exist or isn’t consistent

H’AF, Requested data not available

H’B0, Conflicting feature activation

H’B1, Re-synchronization not possible

H’B2, Inconsistency in wiring configuration

H’B3, No FPGA on board

H’B4-F3, Not used

H'F4, Change password failed: syntax error

H'F5, Change password failed: new pwd is the same as old pwd

H’F6-F7, Not used

H'F8, Mandatory security attribute missing

H'F9, Security transmission failed

H'FA, Security transmission missing

H'FB-FE, Not used

H'FF, NULL

H'01, Incorrect message structure

H'02, Invalid message type value

H'03, <reserved>

744DN0933412 Issue 01


Id:0900d805805bfdaa

Nack causes

H'04, <reserved>

H'05, Invalid object class value

H'06, Object class not supported

H'07, BTS no. unknown

H’08, Transceiver no. unknown

H’09, Object instance unknown

H’0A, <reserved>

H’0B, <reserved>

H'0C, Invalid attribute identifier value

H’0D, Attribute identifier not supported

H’0E, Parameter value outside permitted range

H’0F, Inconsistency in attribute list

H’10, Specified implementation not supported

H'11, Message cannot be performed

H'12, System busy

H’13, <reserved>

H’14, <reserved>

H’15, <reserved>

H’16, <reserved>

H’17, <reserved>

H’18, <reserved>

DN0933412 Issue 01745


Appendix: values for ERFACCHALPDMF, ERFACCH-CMDF, ERSACCHDL, ERSACCHUL and ETOP

Id:0900d8058053dfb7

5 Appendix: values for ERFACCHALPDMF, ERFACCHCMDF, ERSACCHDL, ERSAC-CHUL and ETOP

Assigned Values

Binary Dec Hex

TCH_WFS TCH_HS TCH_FS TCH_EFS TCH_AHS TCH_AFS

0 0 0 0 0 0 0 0 00 0x00

0 0 0 0 0 0 0 1 01 0x01

0 0 0 0 0 0 1 0 02 0x02

0 0 0 0 0 0 1 1 03 0x03

0 0 0 0 0 1 0 0 04 0x04

0 0 0 0 0 1 0 1 05 0x05

0 0 0 0 0 1 1 0 06 0x06

0 0 0 0 0 1 1 1 07 0x07

0 0 0 0 1 0 0 0 08 0x08

0 0 0 0 1 0 0 1 09 0x09

0 0 0 0 1 0 1 0 10 0x0A

0 0 0 0 1 0 1 1 11 0x0B

0 0 0 0 1 1 0 0 12 0x0C

0 0 0 0 1 1 0 1 13 0x0D

0 0 0 0 1 1 1 0 14 0x0E

0 0 0 0 1 1 1 1 15 0x0F

0 0 0 1 0 0 0 0 16 0x10

0 0 0 1 0 0 0 1 17 0x11

0 0 0 1 0 0 1 0 18 0x12

0 0 0 1 0 0 1 1 19 0x13

0 0 0 1 0 1 0 0 20 0x14

0 0 0 1 0 1 0 1 21 0x15

0 0 0 1 0 1 1 0 22 0x16

0 0 0 1 0 1 1 1 23 0x17

0 0 0 1 1 0 0 0 24 0x18

0 0 0 1 1 0 0 1 25 0x19

0 0 0 1 1 0 1 0 26 0x1A

0 0 0 1 1 0 1 1 27 0x1B

0 0 0 1 1 1 0 0 28 0x1C

746DN0933412 Issue 01


Id:0900d8058053dfb7


g ERFACCHALPDMF:

0 0 0 1 1 1 0 1 29 0x1D

0 0 0 1 1 1 1 0 30 0x1E

0 0 0 1 1 1 1 1 31 0x1F

0 0 1 0 0 0 0 0 32 0x20

0 0 1 0 0 0 0 1 33 0x21

0 0 1 0 0 0 1 0 34 0x22

0 0 1 0 0 0 1 1 35 0x23

0 0 1 0 0 1 0 0 36 0x24

0 0 1 0 0 1 0 1 37 0x25

0 0 1 0 0 1 1 0 38 0x26

0 0 1 0 0 1 1 1 39 0x27

0 0 1 0 1 0 0 0 40 0x28

0 0 1 0 1 0 0 1 41 0x29

0 0 1 0 1 0 1 0 42 0x2A

0 0 1 0 1 0 1 1 43 0x2B

0 0 1 0 1 1 0 0 44 0x2C

0 0 1 0 1 1 0 1 45 0x2D

0 0 1 0 1 1 1 0 46 0x2E

0 0 1 0 1 1 1 1 47 0x2F

0 0 1 1 0 0 0 0 48 0x30

0 0 1 1 0 0 0 1 49 0x31

0 0 1 1 0 0 1 0 50 0x32

0 0 1 1 0 0 1 1 51 0x33

0 0 1 1 0 1 0 0 52 0x34

0 0 1 1 0 1 0 1 53 0x35

0 0 1 1 0 1 1 0 54 0x36

0 0 1 1 0 1 1 1 55 0x37

0 0 1 1 1 0 0 0 56 0x38

0 0 1 1 1 0 0 1 57 0x39

0 0 1 1 1 0 1 0 58 0x3A

0 0 1 1 1 0 1 1 59 0x3B

0 0 1 1 1 1 0 0 60 0x3C

0 0 1 1 1 1 0 1 61 0x3D

0 0 1 1 1 1 1 0 62 0x3E

0 0 1 1 1 1 1 1 63 0x3F

DN0933412 Issue 01747



Id:0900d8058053dfb7

For the binary representation 0 means that R-FACCH for any LAPDm command or response frames is not applied for specified speech codec type and 1 means that R-FACCH for any LAPDm 5 command or response frames is applied for specified speech codec type.Value 0x00 has specific meaning and should be read as R-FACCH for any LAPDm command or response frames is not applied for any speech codec type. All other values are reserved for the future use.

ERFACCHCMDF: For the binary representation 0 means that R-FACCH on LAPDm command frames is not applied for specified speech codec type and 1means that R-FACCH on LAPDm command frames is applied for apecified speech codec type.

Value 0x00 has specific meaning and should be read as R-FACCH on LAPDm command frames is not applied for any speech codec type. All other values are reserved for the future use.

ETOP:

For the binary representation 0 means that TOP is not applied for specified speech codec type and 1 means that TOP is applied for specified speech codec type.Value 0x00 has specific meaning and should be read as TOP is not applied for any speech codec type. All other values are reserved for the future use.

748DN0933412 Issue 01


Id:0900d8058057b3aa

Appendix B: commands available only in remote mode

6 Appendix B: commands available only in remote mode

6.1 REQCURSTASYN BTSEP

Command Tree:“MANAGED-ELEMENT -> BSS-EQUIPMENT -> BTSEP -> REQCURSTASYN BTSEP”





ALGNSTEP alignmentStep


None.

Operation Failed

None.



6.2 GET ENVABTSESUM

Command Tree:“MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEEM h RACK h ENVABTSESUM h GET ENVABTSESUM”



REQCURSTASYN BTSEEP

NAME=BTSEP:0..0 [ALGNSTEP=];

GET ENVABTSESUM NAME=BTSEEM:0..0/RACK:0..1/ENVABTSESUM:0..0 [,REQATTL=ALS, AST, AVS, OST];

DN0933412 Issue 01749


Appendix B: commands available only in remote mode

Id:0900d8058057b3aa




ALS alarmStatus





None.

Operation Failed

None.



bsplcml

Documents

Transcript of bsplcml