mmnbs60

GERAN

MaintenanceBase Transceiver Station Equipment

MMN:BTSE BS-60A50016-G5100-A324-01-7620

2 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012f4f2

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

A50016-G5100-A324-01-7620

3

MMN:BTSE BS-60

Id:0900d8058012f4f2

Table of ContentsThis document has 203 pages.

Reason for Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Structure of the Maintenance Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.2 Used Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3 Fault Clearance Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4 Fault Clearance Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.5 Module Replacement Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.5.1 ESD Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.5.2 Avoiding the Loss of Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.5.3 Removing and Inserting Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.5.4 Quick Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2 Task List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3 Fault Clearance Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.1 Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.2 ALCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3 BBSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.4 BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.5 CCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.6 CCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.7 DUCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.8 FAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.9 FICOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.10 FTNF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.11 FVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.12 GPSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643.13 HYCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.14 LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.15 LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.16 MCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.17 OVPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.18 PA / DCPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.19 PCM Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.20 RXAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.21 RXAMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.22 RXMUCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033.23 TPU / DCTPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083.24 TX/RX Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.25 Remote Inventory Data Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1163.26 Remote Inventory Data Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

4 Tables Lists and Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.1 Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1224.2 Front View of the BS 60 Rack and Mounting Positions . . . . . . . . . . . . . . 125

4 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012f4f2

4.3 General Information on BTSE LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1314.4 ALCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1324.5 BBSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1354.6 CCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384.7 DC Fuse Panel / Connection Board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414.8 DCPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434.9 DUCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444.10 FAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.11 FICOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.12 GPSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1524.13 HYCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1534.14 LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554.14.1 LI - Link Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554.14.2 LIPA - Link Interface for Primary Access . . . . . . . . . . . . . . . . . . . . . . . . . . 1604.15 MCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654.16 OVPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684.17 PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704.17.1 Jumper Settings on GSM 1800 PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714.17.2 Jumper Settings on GSM 900 PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1734.18 RCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1754.19 RXAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764.20 RXAMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784.21 RXMUCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1794.22 RXMUCO2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1814.23 TPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

5 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1895.1 HW/SW Compatibility during Download from LMT/BSC . . . . . . . . . . . . . . 1895.2 State/Status Attributes of BTSE Managed Objects . . . . . . . . . . . . . . . . . . 1915.3 BTSE Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.3.1 Probable Cause Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.3.2 Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.3.2.1 Equipment Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.3.2.2 Processing Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.3.2.3 Communication Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.3.2.4 Quality of Service Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1935.3.2.5 Environmental Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.3.3 Perceived Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.3.3.1 Critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.3.3.2 Major . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.3.3.3 Minor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.3.3.4 Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.3.4 Trend Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.3.5 Immediate Defense Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1945.3.6 Threshold Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955.3.7 Proposed Repair Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955.3.8 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1955.3.9 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

A50016-G5100-A324-01-7620

5

MMN:BTSE BS-60

Id:0900d8058012f4f2

5.4 Fault Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965.4.1 Fault Messages at the Radio Commander . . . . . . . . . . . . . . . . . . . . . . . . 1965.4.2 Fault Messages at the LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965.5 BTSE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.5.1 BTSE Components Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.5.2 Numbering of BTSE Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.5.2.1 General Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.5.2.2 Specific Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1975.5.3 Remote Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1985.6 Diagnostics / Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2005.6.2 Requirements for Starting the BTSE Module Test . . . . . . . . . . . . . . . . . . 2005.6.2.1 Lock BTS Site Manager (only relevant for some modules). . . . . . . . . . . . 2005.6.2.2 Change BTSE from Phase 3 to Phase 2 (only relevant for some modules) . .

2005.6.2.3 Lock Suspected Module (all modules) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015.6.2.4 Run Test for Replaced Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015.6.2.5 Unlock Suspected Module (all Modules). . . . . . . . . . . . . . . . . . . . . . . . . . 2025.6.2.6 Change BTSE from Phase 2 to Phase 3 (only relevant for some modules) . .

2035.6.2.7 Unlock BTS Site Manager (only relevant for some modules) . . . . . . . . . . 2035.6.3 Incompatible Tests for Multiple Test Processing . . . . . . . . . . . . . . . . . . . 203

6 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012f4f2

List of FiguresFigure 1 Structure of the MMN:BTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 2 Used Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 3 Fault Clearance Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 4 ESD Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 5 Module Fastening Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 6 Location of the Plug-in Module Code Keys. . . . . . . . . . . . . . . . . . . . . . . 20Figure 7 Location of the Code Key Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 8 Editing Nob_RIU Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Figure 9 Functional Blocks, 6 Carrier BTSE with HYCOM (1 Cell / 4 Carriers) . 122Figure 10 Functional Blocks, 6 Carrier BTSE with DUCOM (1 Cell / 4 Carriers) . 123Figure 11 Functional Blocks, 6 Carrier BTSE with FICOM (1 Cell / 6 Carriers) . . 124Figure 12 BS 60 Rack with ACOM Frame (Front View) . . . . . . . . . . . . . . . . . . . . 125Figure 13 ALCO (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Figure 14 ALCO (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Figure 15 BBSIG44 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Figure 16 BBSIG44 (Top View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Figure 17 CCTRL (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Figure 18 CCTRL (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Figure 19 Fuse Panel / Connection Board for 11 Fuses . . . . . . . . . . . . . . . . . . . . 141Figure 20 Fuse Panel / Connection Board for 12 Fuses . . . . . . . . . . . . . . . . . . . . 141Figure 21 DCPA (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Figure 22 DUCOM2 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Figure 23 DUCOM4 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Figure 24 FAN (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Figure 25 Kathrein FICOM Base Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Figure 26 Kathrein FICOM Expansion Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Figure 27 Forem FICOM Base Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Figure 28 GPSU (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Figure 29 HYCOM Vertical (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Figure 30 LI (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Figure 31 LI; Variant 1 (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Figure 32 LI; Variant 2 (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Figure 33 LI; Variant 2 (Submodule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Figure 34 LIPA (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Figure 35 LIPA (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Figure 36 Switches for Line Impedance Matching (PCM30 120 Ω) . . . . . . . . . . . 164Figure 37 Switches for Line Impedance Matching (PCM30 75 Ω) . . . . . . . . . . . . 164Figure 38 Switches for Line Impedance Matching (PCM24 100 Ω) . . . . . . . . . . . 164Figure 39 MCLK (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Figure 40 MCLK (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Figure 41 OVPT with Terminal Block (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . 168Figure 42 OVPT with SMA Connectors (75 Ω) . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Figure 43 PA (Front View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Figure 44 GSM 1800 PA 10W/25W (U434/U466). . . . . . . . . . . . . . . . . . . . . . . . . 171Figure 45 GSM 1800 PA25D (U519) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

A50016-G5100-A324-01-7620

7

MMN:BTSE BS-60

Id:0900d8058012f4f2

Figure 46 GSM 900 PA 25W (U435) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Figure 47 GSM 900 PA 25W/40W (U538/U520) . . . . . . . . . . . . . . . . . . . . . . . . . 175Figure 48 RCAP BS 60 (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Figure 49 RXAMCO (Front View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Figure 50 RXAMOD (Bottom View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Figure 51 RXMUCO (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Figure 52 RXMUCO (Top View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Figure 53 RXMUCO 2 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Figure 54 RXMUCO2 (Top View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Figure 55 TPU / TPU2 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Figure 56 Fault Messages at the Radio Commander . . . . . . . . . . . . . . . . . . . . . 196

8 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012f4f2

List of TablesTable 1 Mounting Units for the 6 Carrier BTSE Rack R:BS 60. . . . . . . . . . . . . 126Table 2 Mounting Positions and Slot-IDs for the Core Part of the Frame . . . . . 126Table 3 Mounting Positions and Slot-IDs for the Carrier Part of the Frame . . . 127Table 4 Mounting Positions and Slot-IDs: ACOM Frame; HYCOM, DUCOM . . 128Table 5 Mounting Positions and Slot-IDs: ACOM Frame; FICOM . . . . . . . . . . 129Table 6 Mounting Positions and Simulated Processor IDs . . . . . . . . . . . . . . . . 131Table 7 Positions of Contacts for PCM30 120 Ω . . . . . . . . . . . . . . . . . . . . . . 164Table 8 Positions of Contacts for PCM30 75 Ω . . . . . . . . . . . . . . . . . . . . . . . 164Table 9 Positions of Contacts for PCM24 100 Ω . . . . . . . . . . . . . . . . . . . . . . 164Table 10 Pinning Label of the Terminal Block . . . . . . . . . . . . . . . . . . . . . . . . . . 168Table 11 Jumper Settings on GSM 1800 PA 10W/25W (U434/U466) . . . . . . . . 171Table 12 Jumper Settings on GSM 1800 PA25D (U519) . . . . . . . . . . . . . . . . . . 173Table 13 Jumper Settings on GSM 900 PA 25W (U435) . . . . . . . . . . . . . . . . . . 174Table 14 Jumper Settings on GSM 900 PA 25W/40W (U538/U520) . . . . . . . . . 175Table 15 DIP Switch Configuration Versus RF Attenuation . . . . . . . . . . . . . . . . 184Table 16 State/Status Attributes of BTSE MOs . . . . . . . . . . . . . . . . . . . . . . . . . 191Table 17 List of nob_RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

A50016-G5100-A324-01-7620

9

MMN:BTSE BS-60 Reason for Update

Id:0900d8058013669f

Reason for UpdateIssue History

Issue Date Reason for Update

1 01/2005 New release for BR 8.0

2 04/2005 New LMT Software

3 07/2005 Revision

10 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058013669f

Reason for Update

A50016-G5100-A324-01-7620

11

MMN:BTSE BS-60 Introduction

Id:0900d8058012be7a

1 Introduction

1.1 Structure of the Maintenance ManualThe following diagram gives an overview of the structure of this manual and the purpose of its chapters.

Figure 1 Structure of the MMN:BTSE

Chapter 1

Chapter 2

Chapter 3

Chapter 5

Introduction– Basic information on this manual– Basic information on fault clearance– Guidelines– General replacement Instructions– Preparatory work if relevant

Task ListInformation on routine tasks that need to be carried out

Chapter 6 Abbreviations

AppendixBasic required knowledge in more detail, e.g. explanation of alarm messages

Chapter 4

Fault Clearance Procedures for Modules and Interfaces– Fault clearance procedures (modules/in-terfaces/ HMOs in alphabetical order)– Concluding procedure “Remote Inventory Data Update” that some fault clearance pro-cedures require (if necessary, links are pro-vided to this concluding procedure)

Tables, Lists and Figures– Information on replaceable modules, e.g. LEDs, connectors etc.– Overview of the HW architecture as ad-ditional information

(Important information to make your work efficient and safe)

(Main Part for Fault Clearance Tasks)

(Reference Chapter)

(Reference Chapter)

(General Maintenance)

(Reference Chapter)

Chapter 4

12 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be7a

Introduction

1.2 Used SymbolsThe following symbols are used in this manual:

Figure 2 Used Symbols

g Some abbreviations are used in general, e.g. BS61 stands for BS61E and BS61U, LI for LI and LIPA, if a distinction is not necessary for technical reasons.

Reference to another procedure step

Symbol Meaning

ESD (Electrostatically Sensitive Devices) precautions to be taken

Note; important additional information

Warning; the notes given here are to be followed with care.

b

h

Use LMT to enter commands

Reference to another chapter

Reference to another procedure. Return after finishing.i

i

! Non-observance can lead to personal injury or property damage.

A50016-G5100-A324-01-7620

13


Id:0900d8058012be7a

1.3 Fault Clearance PrincipleThe high system functionality of the Siemens Base Station System (SBS) is achieved by means of system-integrated routine tests. These routine tests continually check the correct functioning of the base station subsystems including the BTSEs.

The fault clearance procedures in this manual are based on these routine tests. In most cases, the results of these routine tests are sufficient to localize the fault and clear it immediately at the BTSE.

The modular design of the BTSE allows you to clear a large percentage of faults in the system by replacing a defective module.

Sometimes, however, it may happen that faults do not result from defective modules, but from interface problems in general (for example interrupted cables). In this case, special trouble shooting procedures for interfaces are provided.

This maintenance concept guarantees a simple and fast fault clearance and leads to high operational efficiency.

14 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be7a

Introduction

1.4 Fault Clearance GuidelinesThe following diagram gives an overview of the fault clearance procedure (detailed description below):

Figure 3 Fault Clearance Overview

Fault Clearance Guidelines

(The numbering refers to the preceding diagram.)

1. The system integrated routine test detects a fault.2. A fault message is displayed at the Radio Commander.

7.

6. Another Probable Cause?

9. End of Fault Clearance: Faulty Modules are Sent to Repair Depot

Fault and Test Man-agement at the OMC via Radio

Commander

1. System Integrated Routine Test Detects a Fault

3. Local Fault

Clearance at the BTSE Neces-

sary?

2. Fault Message Displayed at Radio Commander:Information for example on– probable cause – suspected modules(s)/interface(s)– location ...

Local Fault Clearance at

the BTSE

4. Fault Clearance Proce-dure for the Suspected

Module or Interface

8. Call TAC

5. Fault

Clearance Success-

ful?

Content of this Manual

YN

Y

N

Y

N

A50016-G5100-A324-01-7620

15


Id:0900d8058012be7a

3. The fault and test management at the Operation and Maintenance Center (OMC) must verify whether a local fault clearance at the BTSE is required (see Radio Com-mander documentation).g For the local fault clearance at the BTSE:

Make sure that all spare parts that might be required to clear the fault are avail-able at the site. Note that sometimes more than one module may be suspected of being defective. This is particularly important if the failure is located in the TX/RX path (see PROC: TX/RX Path).For general module replacement instructions see also 1.5 “Module Replace-ment Instructions”.

4. Interpret the fault message and go to the fault clearance procedure of the suspected module or interface in chapter 3 "Fault Clearance Procedures for Modules and Inter-faces" (module/interface names as well as HMOs are listed in alphabetical order if they appear in the fault message).Localize the fault and clear it according to the corresponding procedure.

5. As described in the corresponding procedure, verify whether the fault clearance was successful:– Was the outcome of the hardware test “pass”?– Are there any relevant active alarms?– Do the LEDs signal normal operation?

6. If the fault should still exist and the replaced module was not the fault cause, check whether there is another probable cause.

7. If there is another probable cause, reinsert the recently replaced original module and go to the corresponding fault clearance procedure for the next suspected module or interface.

8. It should be possible to clear most faults that may occur in the BTSE by following the fault clearance procedures described in this manual. However, if the fault should still exist after considering all probable causes, contact the Technical Assistance Center (TAC). Here you will obtain help from specially trained troubleshooting experts.

9. End of fault clearance. Pack and tag all faulty modules for transport to a repair depot.Write a fault report in which the following information is given in detail:– name and code of the site– BSS area, cabinet and slot number– name, code and serial number of the module– description of the system response– description of the fault– name and phone number of the originator

16 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be7a

Introduction

1.5 Module Replacement Instructions

1.5.1 ESD Precautions

Figure 4 ESD Symbol

Many system modules are equipped with electrostatically sensitive components (marked by an ESD symbol). Therefore, precautions must be taken when removing and inserting modules.

During module replacement, personnel must wear a conductive wrist strap to discharge electrostatic charging. Before modules, lines or components are touched, this wrist strap must be connected to the ground potential of the rack/shelter by means of a flexible lead integrating a 1 MΩ resistor. Note that the conducting parts of the split pin or the clamp should not be touched when inserting/connecting (so as to avoid bypassing the 1 MΩ resistor).

A50016-G5100-A324-01-7620

17


Id:0900d8058012be7a

1.5.2 Avoiding the Loss of Calls

g The following procedure is only relevant if the BTSE is in phase 3. In phase 1 or 2, the BTSE cannot establish calls. For a description of the BTSE phases, refer to OGL:LMT Evolution.

g If you lock or replace modules in the TX/RX path of the BTSE, calls may be lost. To avoid the loss of calls, perform the following procedure before you lock or replace a module in the TX/RX path.

1. Find out the corresponding TRX:To find out which TRX is related to the module, perform the following LMT command:BSSBE Btse Br<no>:<NE id>BSS-EQUIPMENTBTSEBTSE<no>RACKRACK<no><Module><Module><no>GET <Module>NAME=RACK:<no>/<Module>:<no>Get <Module>:Name=BTSE:<no>/<Module>:<no>

In the system response, the corresponding TRX is listed as related Functional Object: relatedFuncObjects FMO = BTS:<no>/TRX:<no>.

2. Check the state of the corresponding TRX (only possible in phase 3):To check the state of the corresponding TRX, perform the following LMT command:BSSBE Btse Br<no>:<NE id>BSS-FUNCTIONALBTSMBTSM<no>BTSTRXTRX<no>GET <TRX>NAME=BTS:<no>/TRX:<no>Get TRX:Name=BTS:<no>/TRX:<no>

The states of the TRX are listed in the system response.3. If the states of the TRX are either administrativeState = Unlocked / operationalState

= Disabled or administrativeState = Locked / operationalState = Enabled, the module is not used for calls anymore. You can start with your maintenance task.

4. If the administrativeState = Shutting Down, the shutdown is in progress. Wait a few minutes and check the state of the TRX again. As soon as the TRX is locked, you can start with your maintenance task.

5. If the TRX is unlocked/enabled, call the OMC to have the TRX shut down. Wait a few minutes and check the state of the TRX again. As soon as the TRX is locked, you can start with your maintenance task.

18 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be7a

Introduction

The modules in the TX/RX path are listed in 3.24 "TX/RX Path".

For a description of the state/status attributes, refer to 5.2 "State/Status Attributes of BTSE Managed Objects".

A50016-G5100-A324-01-7620

19


Id:0900d8058012be7a

1.5.3 Removing and Inserting ModulesThere are two variants for fastening modules in the subracks.

Some modules, e.g. the ALCO, BBSIG, CCTRL, MCLK, and LI are equipped with a lever mechanism at their front panel. For removing or inserting these modules, they can be fastened / unfastened by swivelling the levers at the top and bottom edges of the module.

Other modules, e.g. the GPSU, DCPA, DCTPU, PA, TPU, RXMUCO and ACOM are fastened with slotted, crosshead or TORX-headed knurled screws. Replacement of these modules requires a suitable screwdriver.

Figure 5 Module Fastening Variants

The module RXAMOD located at the Mast Head Unit (MHU) must be replaced complete with its housing (to be mounted on / unmounted from the mast).The semi-rigid cables on modules ACOM, PA, RXMUCO and TPU must be fastened / unfastened with a special spanner (torque wrench, 2 sizes).

g It must be ensured that all cables are fastened correctly. Make sure that the connec-tors are aligned straight on the screw threads. Then screw on the cable connector coupling nuts manually. The position and alignment is correct if the connector can be turned easily. Finally, fasten the cables by tightening their coupling nuts with a torque wrench.

g It must be ensured that the modules are only replaced by modules with the same (or a compatible) HW and SW functional status!

Modules with switches or jumpers (module ALCO, LI and RXMUCO) must be compared with the removed module for safety reasons.

The modules should be removed and inserted as fast as possible, in order to prevent reading in false module addresses from the CAN BUS.

lever mechanism in open position

push together

lever mechanism in locked position torx screw

20 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be7a

Introduction

Handling Modules with Code Keys

To prevent the installation of the modules at incorrect mounting positions, code keys are used on all relevant plug-in modules.

Figure 6 Location of the Plug-in Module Code Keys

In order to avoid module and backplane connector damage when modules are removed from / inserted into a base station frame, please observe the following:

In general, after having removed a module from a base station frame, please make sure that the module’s code keys (at the rear connector terminals) are mechanically intact, and that a code key plug has not been torn out from its socket and is now jammed in the backplane.

When replacing a module, please make sure

– that the code keys of the new module have the same setting as those of the old one (see figure below),

Figure 7 Location of the Code Key Number

– that all code keys (also those of the old module) are mechanically intact, and

– that a code key plug has not been torn out from its socket and is now jammed in the backplane.

When inserting a module, do not use excessive pressure.

Code Keys

2

code key number

A50016-G5100-A324-01-7620

21


Id:0900d8058012be7a

1.5.4 Quick Module ReplacementIn general, there are 2 replacement procedures:

– the standard replacement procedure

and

– the facilitated, quick replacement procedure (only applicable for some partic-ular modules).

For the standard replacement procedure, an LMT is required. The modules are locked and, after their replacement, tested and unlocked via an LMT.

For the quick replacement procedure, an LMT is not required. The module can be replaced directly and is put into service automatically after a successful replacement (Autorecovery).

Precondition for the quick replacement procedure: the attribute Autorecovery (EAU-TOREC) must be enabled.

To check whether this attribute is enabled, perform the LMT command:

BSS

BE Btse Br<no>:<NE id>

BSS-EQUIPMENT

BTSE

BTSE<no>

GET BTSE NOSWL

Get BTSE NOSWL:NAME=BTSE:<no>

You will find the attribute and the value for EAUTOREC in the “Object Details”.

To set this attribute perform the command “Set BTSE – EAUTOREC = “enabled”.

g Quick Replacement Procedure and Semi-Rigid Cabling

Modules with semi-rigid cabling require a special handling!

It is important that all semi-rigid cables are connected before the module is fully inserted. Otherwise, the module is not put into service. The reason for this is that the automatic recovery process starts as soon as the module comes into contact with the backplane connectors. Semi-rigid cables that are not connected during this process cause errors which will prevent the autorecovery of the module.

– In order to be able to connect the semi-rigid cables, insert the prepared module as far as necessary. It is recommended to leave about 2 cm distance between module and backplane connectors.

– Connect all semi-rigid cables.– Fully insert the module.

22 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800e935b

Task List

2 Task ListThe filter mat usually has to be cleaned every six months. After having been cleaned repeatedly, the filter mat must be replaced.

A50016-G5100-A324-01-7620

23

MMN:BTSE BS-60 Fault Clearance Procedures

Id:0900d8058012fa48

3 Fault Clearance Procedures

3.1 Abisg In some cases, Abis alarms originate from loose or damaged PCM cables on the

BTSE Abis Interface (OVPT) or in the corresponding distribution frame (NTPM, BSC connector, customer terminal equipment) in BSC direction. Therefore, the relevant cables must be checked first, according to the following procedure.

Typical Abis alarms concerning cable problems may be indicated by the alarm message

“BPORT - Loss of signal”

g BPORT is the logical object that is related to the Abis Interface (OVPT);

The Abis lines are also referred to as PCM lines.

1 Open the BTSE Door

To verify an Abis alarm you have to open the BTSE door and check the LEDs on various module front panels.

2 Check the LEDs on the LI/LIPA and MCLK

3 Optional: Check the Active Alarms with the LMT

If an LMT is available, you can check the active Abis alarms. Perform the following command:

b BSS

NE Btse Br<no>:<NE id>

BSS-EQUIPMENT

BTSE

BTSE:<no>

GETACTIVEALARMS BTSE

Getactivealarms BTSE:NAME=BTSE:<no>;

You can recognize an Abis alarm by the red LEDs “xRAI” and “xER-3” on the LI/LIPA, as well as “HMO” on the MCLK.

If one of these LEDs is on, an Abis problem is indicated.

24 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48

Fault Clearance Procedures

4 Physical Check of the Abis / PCM Cable Connections (OVPT)

Are the PCM lines fastened correctly in the terminal block of the OVPT and in the dis-tributing frame (NTPM) in BSC direction ?

Yes h......... 6No h.......... 5For further information on the Abis interface on the OVPT, please refer to the Installation Manual.

See ........... IMN:BS 60

5 Fasten the Abis / PCM Lines Correctly in their Terminals

Fasten the PCM lines correctly in their terminals.

Do the red LEDs on the LI/LIPA and on the MCLK go off ?

Yes h......... 9No h.......... 6It may take up to 10 minutes until the LED “HMO” on the MCLK goes off.

6 Visual Check of the Abis / PCM Lines (OVPT)

Write down the cable colors and their corresponding terminals before disconnecting any cables.

Remove the PCM lines in the terminal blocks (OVPT and distributing frame in BSC direction) and examine the cables visually for damages.

Do you see a broken or corroded cable, or an insulation that interrupts the contact ?

Yes h......... 7No h.......... 8

System Response:

The command is acknowledged (ACK).

All active alarms are listed in the “Message Viewer” window.

Typical failure event report for an Abis cable problem:

NAME = BPORT:0

Event Type = Communication Failure Event

Event Time = 26/Jan/2001 00:13:03

Probable Cause = Transmission Error

Specific Problems = 10270 - Loss of signal

Severity = Major

A50016-G5100-A324-01-7620

25


Id:0900d8058012fa48

7 Repair Bad Abis / PCM Lines

Repair bad PCM lines or exchange the PCM line.

Do the red LEDs on the LI/LIPA and on the MCLK go off ?

Yes h......... 9No h ......... 8It may take up to 10 minutes until the LED “HMO” on the MCLK goes off.

8 Replace OVPT

Refer to the fault clearance procedure for the OVPT

h ......... PROC: 3.17

9 Prepare End of Fault Clearance

If an LMT was connected, log off the LMT and disconnect the LMT cable.

Close the BTSE door.

END

26 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.2 ALCOg Module ALCO may be removed while power is on!

1 Interpret the Fault Message

See ........... 5.5.2

Note the values specified in the fault message, for example:– Module(s) ??– Rack-no ??– BTS-no ??– Module address ??

Use these values for command input.

Use the logical address to find the mounting location of the module(s).

2 Connect the LMT to the BTSE

Plug the LMT cable into the corresponding socket.

Start LOGON-Procedure.

3 Lock BTS Site Manager

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

LOCKREQUEST BTSM

Lockrequest BTSM:NAME=BTSM:0;

4 Disconnect BTS Site Manager from BSC / Switch Phase 3 to Phase 2

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

DISCBSC BTSM

Discbsc BTSM:NAME=BTSM:0;

System Response:


A50016-G5100-A324-01-7620

27


Id:0900d8058012fa48

5 Logon

b Local Logon at NE Btse

UserName:<user>

Password:<password>

Ok

The BTSE is now in phase 2.

6 Lock Suspected Module

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

ALCO

ALCO:<no>

LOCK ALCO

Lock ALCO:NAME=RACK:<no>/ALCO:<no>;

7 Module Replacement

1. Remove affected module2. Select a module with a functional HW / SW state compatible to that of the module

which is being replaced3. Insert prepared module

System Response:


Several CHANGED STATE EVENT REPORTs will follow. They can be examined in the “Message Viewer” window.

System Response:



!CAUTION

ESD precautions must be taken when removing and inserting a module.

Refer to 1.5.1 "ESD Precautions".

28 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


8 Run Test for Replaced Module

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

ALCO

ALCO:<no>

PERFTEST ALCO

Perftest ALCO:NAME=RACK:<no>/ALCO:<no>;

9 Unlock Suspected Module

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

ALCO

ALCOO:<no>

UNLOCK ALCO

Unlock ALCO:NAME=RACK:<no>/ALCO:<no>;

System Response:


Test Result:

The test report can be examined in the “Message Viewer” window.

Note the testOutcome.

If the testOutcome is "fail", some more information is given, such as "Proposed Repair Action" etc.

System Response:



A50016-G5100-A324-01-7620

29


Id:0900d8058012fa48

10 Start the Connection to the BSC / Switch Phase 2 to Phase 3

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM

Connbsc BTSM:NAME=BTSM:0;

11 Logon


UserName:<user>

Password:<password>

Ok

The BTSE is now in phase 3. The BSC will start the alignment with the BTSE.

12 Unlock BTS Site Manager

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

UNLOCKREQUEST BTSM

Unlockrequest BTSM:NAME=BTSM:0;

13 Get Active Alarms

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>


System Response:



System Response:


30 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


Getactivealarms BTSE:NAME=RACK:<no>

14 Result of Module Replacement

The module replacement was successful:

– If the test outcome was “pass”, and– If there are no relevant active alarms, and– If there are no red LEDs, except R1/RE on ALCO.

Was the module replacement successful?

Yes h......... 19

No h.......... 15

15 Reinsert the Replaced Module

It is probable that the original module did not cause the failure and was not defective. Therefore, the currently inserted module must be removed and the original module must be reinserted.

Go back to the beginning of this procedure to reinsert the original module into the BTSE. After having tested/unlocked the original module, continue with the now following step.

16 Another Probable Cause?

Is there another suspected module/interface in the fault message?

Yes h......... 17

No h.......... 18

– Check also modules LI, OVPT, NTPM or µWAVE and connection to BSC– for NTPM or µWAVE, see OEM manuals– for BSC refer to MMN:BSC

17 Fault Clearance Procedure for the Next Suspected Module/Interface

Go to the fault clearance procedure for the next suspected module/interface.

h.......... Procedure: 3.x

18 Call TAC

h.......... 20

19 Mark the Replaced Module as Defective

System Response:



A50016-G5100-A324-01-7620

31


Id:0900d8058012fa48


Log off the LMT and pull the LMT cable out of the socket.


END

32 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.3 BBSIGg “BBSIG” is used as a general expression for the BBSIG44 module

g Module BBSIG may be removed while power is on!


See ........... 5.5.2




2 Autorecovery (EAUTOREC) Enabled?

Is the attribute Autorecovery (EAUTOREC) enabled?

Yes h......... 3No h.......... 5If you have no information on this attribute, continue with “N”.

3 Quick Module Replacement

1. Remove affected module.2. Select a module with a functional HW / SW state compatible to that of the module

which is being replaced.3. Insert prepared module.



Yes ........... 16

No ........... 12

!CAUTION



All LEDs have to signal normal operation. No red LEDs may be on except R1/RE on ALCO.

Call OMN to make sure that the BTSE has gone back to normal operation.

A50016-G5100-A324-01-7620

33


Id:0900d8058012fa48





b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

BBSIG

BBSIG:<no>

LOCK BBSIG

Lock BBSIG:NAME=RACK:<no>/BBSIG:<no>;



which is being replaced.3. Insert prepared module.


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

System Response:



!CAUTION



34 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


RACK:<no>

BBSIG

BBSIG:<no>

PERFTEST BBSIG

Perftest BBSIG:NAME=RACK:<no>/BBSIG:<no>;


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

BBSIG

BBSIG:<no>

UNLOCK BBSIG

Unlock BBSIG:NAME=RACK:<no>/BBSIG:<no>;


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



System Response:


Test Result:




System Response:



A50016-G5100-A324-01-7620

35


Id:0900d8058012fa48





Yes h......... 16

No h ......... 12






Yes h......... 14

No h ......... 15



h ......... Procedure: 3.x

15 Call TAC

h ......... 17



If an LMT was connected, log off the LMT and pull the LMT cable out of the socket.


END

System Response:



36 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.4 BPORTBPORT is the managed object which represents the BTSE Abis ports.

1 Go to Procedure “Abis”

Go to procedure “Abis”.

h.......... PROC: 3.1

END

A50016-G5100-A324-01-7620

37


Id:0900d8058012fa48

3.5 CCLKg Module MCLK may be removed while power is on!

g In commands the module is called CCLK.


See ........... 5.5.2









which is being replaced3. Insert new module (the insertion starts the boot process)

– wait a few minutes until the boot process is finished

4 Get Active Alarms

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



!CAUTION



38 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48




– If there are no relevant active alarms, and– If there are no red LEDs, except R1/RE on ALCO.


Yes h......... 10

No h.......... 6



Go back to the beginning of this procedure to reinsert the original module into the BTSE. After having reinserted the original module, continue with the now following step.



Yes h......... 8No h.......... 9




9 Call TAC

h.......... 11





END

System Response:



A50016-G5100-A324-01-7620

39


Id:0900d8058012fa48

3.6 CCTRLg Module CCTRL may be removed while power is on!

g After replacement of the CCTRL the BTSE specific data base is lost! It is necessary to:

– download and activate the software,

– reconfigure the BTSE,

– rebuild the inventory data that was stored on the removed CCTRL.

The reconfiguration of the BTSE can be done via the Backup BTS tool, if a backup copy of the site specific configuration is available.

To rebuild the inventory data, a backup IDF-file is usually available. Otherwise, the data can be extracted from the BSC-IDF.


See ........... 5.5.2









which is being replaced.3. Insert new module (the insertion starts the boot process).

– wait a few minutes until the boot process is finished.– on modules CCTRL, MCLK and GPSU no red LEDs only green (and yellow)

LEDs go on – exception can be R1 LED on ALCO.– Do not login in Phase 1 and 2!

!CAUTION



40 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


4 Software Download and Activation

Download and activate the software. Refer to ITMN:BTSE BS 60, chapter “SW Download and Activation”.

i .......... ITMN:BTSE BS 60

5 Reconfiguration of the BTS via Backup Copy or by Hand?

If available, a backup copy of the initial configuration can be used to reconfigure the BTSE. Usually the files are stored on site with the site specific documentation.

Is a backup copy of the former configuration available?

Yes h......... 7No h.......... 6

6 Reconfigure the BTSE by Hand

Repeat all tasks for the BTSE installation. Refert to ...

i .......... ITMN:BTSE BS 60

Afterwards, proceed to step ...

h.......... 9

7 Copy the Backup Script Files to the BKBTS\BTSONE Subdirectory

b Copy the backup script files “script*.lmt” from the storage media to the harddisk of the LMT PC e.g., C:\...\LMT<version>\BKBTS\BTSONE\Backup1.

8 Restore the HW Configuration

b To restore the HW configuration:

1. Select “File” -> “Backup BTS” from the LMT menu or click on the corresponding icon in the tool bar.

2. Click on the “Restore” button in the “Backup BTS” window or select “File” -> “Restore”.

3. Select the correct configuration (e.g. Backup1) and confirm by clicking on “Ok”.4. After the restore procedure you can choose to repeat it or to go on working with the

LMT. Click on the “Ok” button to finish the process.


Is the result for all modules as follows?

Yes h......... 14

No h.......... 10

System Response:


A50016-G5100-A324-01-7620

41


Id:0900d8058012fa48



Go back to the beginning of this procedure to reinsert the original module into the BTSE. After having tested/unlocked the original module, and after the BTSE reconfiguration, continue with the now following step.



Yes h......... 12

No h ......... 13




13 Call TAC

h ......... 26


15 Remote Inventory Data Restore via IDF File, BSC-IDF or by Hand?

Usually, a backup of the IDF file is available on site. If not, the data can be extracted from the BSC-IDF or must be entered by hand.

Inventory data restore via backup IDF file?

h ......... 18

Inventory data restore by hand?

h ......... 16

CHANGED STATE EVENT REPORT

NAME = RACK:<no>/<module>:<no>

Operational State: ENABLED

Notification Identifier = <no>

End of Job

42 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


Inventory data restore via extraction of the IDF data from the BSC IDF?

h.......... 17

16 Create all nob_RIUs by Hand

For the creation of the inventory data for all nob_RIUs go to ...

i .......... Procedure 3.26 "Remote Inventory Data Creation"

After this procedure, the fault clearance is finished.

h.......... 26

17 Call TAC

Call TAC to have the data extracted from the BSC IDF. Afterwards, continue with the now following step.

18 Copy IDF File to LMT PC

b Copy the IDF backup file from the storage media to the harddisk of the LMT PC e.g., C:\...\LMT<version>\IDF\*.idf.

19 Start IDF Evolution

b To start the IDF Evolution, select “IDF GSM” -> “IDF Editor” from the Windows program menu.

20 Open IDF File

b To open the IDF file:

1. Select “File” -> “Open” from the menu of the IDF Evolution.2. Enter path and file name of the IDF file or select the file from the list in the appearing

window.3. Double-click on the file name or click on the “Open” button.

21 Export the nob_RIU Part of the IDF File for the Download to the BTSE

Only the nob_RIU data must be downloaded to the BTSE. Therefore, it is necessary to export the nob_RIU part of the IDF file.

b To export the nob_RIU data:

1. Select “Export” -> “NOB” from the menu.2. A window opens in which you can edit the file name and select the directory into

which you want to save the file. By default, the file name is composed of the “Sales UniqueName” with the extension “.nob”. Edit the file name and select the source directory or confirm the default name and directory by clicking on the “Save” button.

3. The nob_RIU data are exported to the NOB file. The selected destination path of this file is displayed in an attention window. Confirm by clicking on the “OK” button.

4. A question window is displayed: “Create BTS_NRIU for download?” Click on the “Yes” button.

A50016-G5100-A324-01-7620

43


Id:0900d8058012fa48

22 Download nob_RIU File to the BTSE

b BSSChange to the LMT application!


BSS-EQUIPMENT

BTSE

BTSE:<no>

REMINV

REMINV:<no>

DNLIDF REMINV

SRCDIR=<source directory>

DNLIDFD REMINV:NAME=REMINV:<no>, SRCDIR=”C:...\LMT<version>\Idf\Dnload”;

Additional Information: SRCDIR: enter the source directory to which the exported NOB file was saved, for example C:...\IDF GSM<version>\Idf\Dnload.

System Response: The command result is displayed: “Operation completed”.

23 Upload IDT File from BTSE

Now you must upload the Remote Inventory Data of the ob-RIUS to the LMT PC in order to create an up-to-date IDF file for backup. These data are stored in the BTSE (IDT file).

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

REMINV

REMINV:<no>

UPLLIDF REMINV

(DESTDIR=<path>)

(FILE=<file name>)

OVERWRITE=YES

UPLLIDF REMINV: NAME=REMINV<no>, (DESTDIR=”<for example: C:...\LMT<ver-sion>\Idf\Upload”>,FILE=<for example: “btse.idt”>,) OVERWRITE= YES;

Additional Information: The attributes DESTDIR and FILE are optional. If no special path or file name is entered, the file is uploaded to the default directory: C:\...\LMT<ver-sion>\IDF\upload,OVERWRITE=<yes> of the IDF Evolution. If the attribute OVER-WRITE=<yes> is selected, a former version of an uploaded IDT file will be overwritten.

System Response: The command is acknowledged (ACK). In the “Message Viewer” window, the command result “Operation completed” is displayed.

24 Open the Uploaded File

Change to the IDF Evolution main window.

44 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


b To open the uploaded file:

1. Select “File” -> “Open” from the menu.2. Select the uploaded file from the list in the appearing window; e.g.,: <C:...\LMT<ver-

sion>\Idf\Upload\BTSE.idt”>.3. Click on the “Open” button.

25 Export File for Backup

Now you must create an up-to-date IDF file for backup.

b To export the Remote Inventory Data for backup:

1. Select “Export” -> "IDF" from the menu.2. Select the destination path in the appearing window, preferably “A:\”. The file name

is automatically composed of the “SalesUniqueName” with the extension “.idf”.3. Click on the “Save” button.4. Put the disk with the backup file of the inventory data to the site specific documen-

tation.




END

A50016-G5100-A324-01-7620

45


Id:0900d8058012fa48

3.7 DUCOMg DUCOM is one of the 2 possible HW modules (DUCOM, HYCOM) for the transceiv-

ing and combining part of the BTSE. Both modules are managed via the managed object ACOM in the LMT.

g f the suspected module is not “disabled/failed”, it may still be used for calls. To make sure that no calls are lost, check whether the corresponding TRX is shut down before the module is locked/replaced. If the TRX is still in use, call the OMC to have it shut down. For more information, refer to 1.5.2 "Avoiding the Loss of Calls".

g This module may be removed while power is on!

g The module ALCO must be inserted and fault free!


See ........... 5.5.2




2 Interpret the Alarm Type

Is one of the following values listed in the fault message?

Yes h......... PROC: 3.24

No h ......... 3– VSWR Alarm– Cable Problem– Transmitter Problem– Receiver Failure/Problem– Transceiver Problem



Yes h......... 4No h ......... 6If you have no information on this attribute, continue with “N”.

46 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



1. Pull the affected module about 2 cm out of the rack until it is no longer connected to the back plane.

2. Disconnect the cables in the following order: – signalling cable– semi-rigid cables– antenna cables.

3. Remove affected module.4. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced.5. Partly insert the prepared module. Make sure that it does not yet come into contact

with the back plane connectors by leaving about 2 cm distance between module and back plane.

6. Connect the cables in the following order:– antenna cables.– semi-rigid cables– signalling cableg If there was contact beteen the module and the back plane connectors before

all semi-rigid cables were connected, pull the module again about 2 cm out of the rack until it is no longer connected to the back plane.

7. Fully insert the prepared module.8. Check the Voltage Standing Wave Ratio VSWR!

Refer to chapter 4.9 "DUCOM" or 4.13 "HYCOM".9. The alarm LED must not go on after module insertion!

If an LED goes on, check the antenna connection.



Yes h......... 17

No h.......... 13




!CAUTION


Refer to 1.5.1 "ESD Precautions"



A50016-G5100-A324-01-7620

47


Id:0900d8058012fa48


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

ACOM

ACOM:<no>

LOCK ACOM

Lock ACOM:NAME=RACK:<no>/ACOM:<no>;


1. Disconnect all semi-rigid cables, antenna and signalling cable2. Remove affected module3. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced4. Insert prepared module5. Connect all semi-rigid cables, antenna and signalling cable6. Check the Voltage Standing Wave Ratio VSWR!

Refer to chapter 4.9 "DUCOM" or 4.13 "HYCOM".7. The alarm LEDs must not go on after module insertion!



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

System Response:



!CAUTION



48 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


RACK

RACK:<no>

ACOM

ACOM:<no>

PERFTEST ACOM

Perftest ACOM:NAME=RACK:<no>/ACOM:<no>;


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

ACOM

ACOM:<no>

UNLOCK ACOM

Unlock ACOM:NAME=RACK:<no>/ACOM:<no>;


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



System Response:


Test Result:




System Response:



A50016-G5100-A324-01-7620

49


Id:0900d8058012fa48





Yes h......... 17

No h ......... 13






Yes h......... 15

No h ......... 16

An Alarm in the TX/RX path may not only originate from the module addressed in the fault message, but from any other module located in the TX/RX path. In this case, consider these modules as suspected modules as well.




16 Call TAC

h ......... 18




System Response:



50 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



END

A50016-G5100-A324-01-7620

51


Id:0900d8058012fa48

3.8 FAN


See ........... 5.5.2








b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

FAN

FAN:<no>

LOCK FAN

Lock FAN:NAME=RACK:<no>/FAN:<no>;

!CAUTION

Switch off the power before exchanging module FAN!

Non-observance can lead to personal injury or property damage.

This warning must appear in the original German text:

ACHTUNG!

Strom abschalten, bevor das Modul FAN ausgetauscht wird.

Nichtbeachtung kann zu Körperverletzung oder Sachschäden führen.

52 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



1. Switch power off for the suspected FAN, refer to chapter 4.10 "FAN".2. Remove affected module FAN.3. Insert new module.4. Switch power on for the suspected FAN.


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

FAN

FAN:<no>

PERFTEST FAN

Perftest FAN:NAME=RACK:<no>/FAN:<no>;


b BSS


System Response:



!CAUTION



System Response:


Test Result:




A50016-G5100-A324-01-7620

53


Id:0900d8058012fa48

BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

FAN

FAN:<no>

UNLOCK FAN

Unlock FAN:NAME=RACK:<no>/FAN:<no>;

7 Get Active Alarms

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>





– If the test outcome was “pass”, and– If there are no relevant active alarms, and


Yes h......... 13

No h ......... 9



System Response:



System Response:



54 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


Go back to the beginning of this procedure to reinsert the original module into the BTSE. After having reinserted/tested/unlocked the original module, continue with the now fol-lowing step.



Yes h......... 11

No h.......... 12




12 Call TAC

h.......... 15


14 Update the Remote Inventory Data

Update the remote inventory data and renew the backup copy of the inventory data table.

For updating the remote inventory data and renewing the backup copy, go to procedure “Remote Inventory Data Update” in this manual.

h.......... PROC: 3.25




END

A50016-G5100-A324-01-7620

55


Id:0900d8058012fa48

3.9 FICOMg FVSWR

Is one of the two managed objects of the FICOM. It exists only once per base module (not in expansion modules)

FTNF

There are two managed objects of this type per module. They must be handled sep-arately

All managed objects must be locked before replacement!

g Modules may be removed while power is on!


See ........... 5.5.2

Note the values specified in the fault message, for example:

– Module(s) ??– BTS-no ??– Rack-no ??– Module address ??





Yes h......... PROC: 3.24





56 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



1. Disconnect all semi-rigid and antenna cables and all expansion cables (between the different modules) from the suspected module. In certain cases a coupler for power monitoring may be used. Be careful not to mix up the connections for the input and the monitoring output when reconnecting the cables!


which is being replaced4. Partly insert the prepared module. Make sure that it does not yet come into contact

with the backplane connectors by leaving a distance of about 2 cm between module and backplane.

5. Connect all semi-rigid and antenna cables (use a torque spanner)g If there was contact beteen the module and the backplane connectors before all

semi-rigid and antenna cables were connected, pull the module out of the rack again by 2 cm until it is no longer connected to the backplane.

6. Insert the prepared module completely.7. The alarm LEDs must not go on after module insertion! If the LED goes on: check

antenna connection.

A) Replacement successful

h.......... 22

B) Replacement not successful

h.......... 18




6 Lock the FVSWR Object of the Suspected Module

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

!CAUTION

All FICOM modules which are used for one cell must be the same variant. ESD precautions must be taken when removing and inserting a module. Refer to 1.5.1 "ESD Precautions".


All LEDs have to signal normal operation (no red LEDs may be on).


A50016-G5100-A324-01-7620

57


Id:0900d8058012fa48

RACK

RACK:<no>

FVSWR

FVSWR:<no>

LOCK FVSWR

LOCK FVSWR:NAME=RACK:<no>/FVSWR:<no>;

7 Lock the FTNF Objects of the Suspected Module

The relative number “no” is the one assigned to the managed object, not the address set by the DIP switches at the front of the module!

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

FTNF

FTNF:<no>

LOCK FTNF

LOCK FTNF:NAME=RACK:<no>/FTNF:<no>;

8 Second FTNF Object

Is there a second FTNF object created and not locked?

Yes h......... 7No h ......... 9

System Response:



System Response:



58 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



1. Disconnect all semi-rigid and antenna cables. In certain cases a coupler for power monitoring purposes may be used. Be careful not to mix up the connections for the input and the monitoring output when reconnecting the cables!

2. Remove affected module3. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced4. Insert prepared module5. Connect all semi-rigid and antenna cables (use a torque spanner).6. Compare the TNF AD0 and AD1 DIP switch settings with those of the replaced

module! Refer to 4.11 "FICOM"

The alarm LEDs must not go on after module insertion!

If an alarm LED goes on, check the antenna connection.

10 Run Test for FVSWR Object of the Replaced Module

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

FVSWR

FVSWR:<no>

PERFTEST FVSWR

Perftest FVSWR:NAME=RACK:<no>/FVWSR:<no>;

!CAUTION

All FICOM modules which are used for one cell must be the same variant. ESD precautions must be taken when removing and inserting a module. Refer to 1.5.1 "ESD Precautions".

System Response:


Test Result:




A50016-G5100-A324-01-7620

59


Id:0900d8058012fa48

11 Run Test for FTNF Objects of the Replaced Module

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

FTNF

FTNF:<no>

PERFTEST FTNF

Perftest FTNF:NAME=RACK:<no>/FTNF:<no>;


Is there a second FTNF object to be tested?

Yes h......... 11

No h ......... 13

13 Unlock FVSWR Objects

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

FVSWR

FVSWR:<no>

UNLOCK FVSWR

Unlock FVSWR:NAME=RACK:<no>/FVSWR:<no>;

System Response:


Test Result:




60 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


14 Unlock FTNF Objects

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

FTNF

FTNF:<no>

UNLOCK FTNF

Unlock FTNF:NAME=RACK:<no>/FTNF:<no>;


Has a second FTNF object been created and not unlocked?

Yes h......... 16

No h.......... 14


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



System Response:



System Response:



System Response:



A50016-G5100-A324-01-7620

61


Id:0900d8058012fa48


– The module replacement was successful:– If the test outcome was “pass”, and– If there are no relevant active alarms.– If there are no red LEDs, except R1/RE on ALCO.


Yes h......... 22

No h ......... 18






Yes h......... 20

No h ......... 21




21 Call TAC

h ......... 23





END

62 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.10 FTNFFTNF is a functional part of the module FICOM and can not be replaced separately.

1 Go to Procedure “FICOM”

For fault clearance continue with procedure “FICOM”:

h.......... PROC: 3.9

END

A50016-G5100-A324-01-7620

63


Id:0900d8058012fa48

3.11 FVSWRFVSWR is a functional part of the module FICOM and can not be replaced separately.

1 Go to Procedure “FICOM”

For fault clearance continue with procedure “FICOM”:

h ......... PROC: 3.9

END

64 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.12 GPSUg The GPSU may be used in redundant configuration. Both modules are handled as

GPSU_0. If the redundant GPSU fails, the availability status changes to degraded, which will inform the operator of the lost redundancy. This causes also a change of the availability status of all TRXs to degraded. But the functionality is not restricted at all.

g In redundant configuration the module GPSU must be removed while power is on!


See ........... 5.5.2









which is being replaced3. Insert prepared module (the insertion starts the boot process)

– wait a few minutes until the boot process is finished– on modules CCTRL, MCLK and GPSU no red LEDs, only green (and yellow)

LEDs go on - exception can be R1 LED on ALCO– do not login in Phase 1 and 2!

!CAUTION


Refer to 1.5.1 "ESD Precautions"

System Response:


The BTSE is in phase 3 after approximately10 minutes.

A50016-G5100-A324-01-7620

65


Id:0900d8058012fa48

4 Get Active Alarms

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>




The module replacement was successful:– If there are no relevant active alarms, and– If there are no red LEDs, except R1/RE on ALCO.


Yes h......... 10

No h ......... 6






Yes h......... 8No h ......... 9




9 Call TAC

h ......... 12

System Response:



66 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48






h.......... PROC: 3.25




END

A50016-G5100-A324-01-7620

67


Id:0900d8058012fa48

3.13 HYCOMg HYCOM is one of the 2 possible HW modules (DUCOM, HYCOM) for the transceiv-

ing and combining part of the BTSE. Both modules are managed via the managed object ACOM in the LMT.

g If the suspected module is not “disabled/failed”, it may still be used for calls. To make sure that no calls are lost, check whether the corresponding TRX is shut down before the module is locked/replaced. If the TRX is still in use, call the OMC to have it shut down. For more information, refer to 1.5.2 "Avoiding the Loss of Calls".

g This module may be removed while power is on!

g The module ALCO must be inserted and fault free!


See ........... 5.5.2






Yes h......... PROC: 3.24





68 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



1. Pull the affected module about 2 cm out of the rack until it is no longer connected to the back plane.

2. Disconnect the cables in the following order:– signalling cable– semi-rigid cables– antenna cables.

3. Remove affected module.4. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced.5. Partly insert the prepared module. Make sure that it does not yet come into contact

with the back plane connectors by leaving about 2 cm distance between module and back plane.

6. Connect the cables in the following order:– antenna cables.– semi-rigid cables– signalling cableg If there was contact beteen the module and the back plane connectors before

all semi-rigid cables were connected, pull the module again about 2 cm out of the rack until it is no longer connected to the back plane.

7. Fully insert the prepared module.8. Check the Voltage Standing Wave Ratio VSWR!

Refer to chapter 4.9 "DUCOM" or 4.13 "HYCOM".9. The alarm LED must not go on after module insertion!




Yes h......... 17

No h.......... 13




!CAUTION





A50016-G5100-A324-01-7620

69


Id:0900d8058012fa48


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

ACOM

ACOM:<no>

LOCK ACOM

Lock ACOM:NAME=RACK:<no>/ACOM:<no>;


1. Disconnect all semi-rigid cables, antenna and signalling cable2. Remove affected module3. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced4. Insert prepared module5. Connect all semi-rigid cables, antenna and signalling cable6. Check the Voltage Standing Wave Ratio VSWR!

Refer to chapter 4.9 "DUCOM" or 4.13 "HYCOM".7. The alarm LEDs must not go on after module insertion!



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

System Response:



!CAUTION



70 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


RACK

RACK:<no>

ACOM

ACOM:<no>

PERFTEST ACOM

Perftest ACOM:NAME=RACK:<no>/ACOM:<no>;


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

ACOM

ACOM:<no>

UNLOCK ACOM

Unlock ACOM:NAME=RACK:<no>/ACOM:<no>;


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



System Response:


Test Result:




System Response:



A50016-G5100-A324-01-7620

71


Id:0900d8058012fa48


– if the test outcome was “pass”, and– If there are no relevant active alarms, and– If there are no red LEDs, except R1/RE on ALCO.


Yes h......... 17

No h ......... 13






Yes h......... 15

No h ......... 16





16 Call TAC

h ......... 18




System Response:



72 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



END

A50016-G5100-A324-01-7620

73


Id:0900d8058012fa48

3.14 LAPDLE



h ......... PROC: 3.1

END

74 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.15 LIg Module LI may be removed while power is on!

g When the module LI is plugged off, the PCM line is interrupted also for all subse-quent BTSE in case of multidrop configuration.

Since a defective module LI is still able to switch the PCM line to all subsequent BTSEs in case of multidrop configuration, the module LI may be pulled only for module replacement!

g If a failure of the LI is reported, the OVPT must be considered as a possible failure cause as well.


See ........... 5.5.2








b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

LOCKREQUEST BTSM



b BSS


BSS-FUNCTIONAL

BTSM

System Response:


A50016-G5100-A324-01-7620

75


Id:0900d8058012fa48

BTSM:<no>

DISCBSC BTSM


5 Logon


UserName:<user>

Password:<password>

Ok



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

LI

LI:<no>

LOCK LI

Lock LI:NAME=RACK:<no>/LI:<no>;


System Response:



System Response:



!CAUTION



76 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



which is being replaced and set the switches according to the affected module– for the relevant switch settings of module LI refer to 4.14.1 "LI - Link Interface"– for the relevant switch settings of module LIPA refer to 4.14.2 "LIPA - Link Inter-

face for Primary Access"3. Insert prepared module


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

LI

LI:<no>

PERFTEST LI

Perftest LI:NAME=RACK:<no>/LI:<no>;


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

LI

LI:<no>

UNLOCK LI

Unlock LI:NAME=RACK:<no>/LI:<no>;

System Response:


Test Result:




A50016-G5100-A324-01-7620

77


Id:0900d8058012fa48


b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM


11 Logon


UserName:<user>

Password:<password>

Ok


12 Unlock BTS Site Manager

b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

UNLOCKREQUEST BTSM

Unlockrequest BTSM:NAME=BTSM:0;


b BSS

System Response:



System Response:



System Response:


78 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



BSS-EQUIPMENT

BTSE

BTSE:<no>







Yes h......... 19

No h.......... 15






Yes h......... 17

No h.......... 18




18 Call TAC

See ........... 20

System Response:



A50016-G5100-A324-01-7620

79


Id:0900d8058012fa48





END

80 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.16 MCLKg In commands the module MCLK is called CCLK.

1 Go to Procedure “CCLK”

Go to procedure “CCLK”.

h.......... PROC: 3.5

END

A50016-G5100-A324-01-7620

81


Id:0900d8058012fa48

3.17 OVPTg Module OVPT may be removed while power is on!

g Module OVPT is the interface module between BSC and BTSE (for outdoor versions in common with µWAVE or NTPM). Therefore, if a failure of the module LI is reported, the OVPT has to be considered as a possible failure cause as well.

The procedure of fault clearance for the module OVPT follows the same rules as for module LI.

g When the OVPT fails, the PCM line is interrupted also for all subsequent BTSEs in case of multidrop configuration.


See ........... 5.5.2

Note the values specified in the fault message, for example:– Module(s) ??– BTS-no ??– Rack-no ??– Module address ??







b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

LOCKREQUEST BTSM



b BSS


BSS-FUNCTIONAL

BTSM

System Response:


82 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


BTSM:<no>

DISCBSC BTSM


5 Logon


UserName:<user>

Password:<password>

Ok



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

LI

LI:<no>

LOCK LI

Lock LI:NAME=RACK:<no>/LI:<no>;


System Response:



System Response:



!CAUTION



A50016-G5100-A324-01-7620

83


Id:0900d8058012fa48

1. Disconnect the Abis- cable2. Take out affected module OVPT3. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced4. Mount and connect new module OVPT5. Connect the Abis cable


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

LI

LI:<no>

PERFTEST LI

Perftest LI:NAME=RACK:<no>/LI:<no>;


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

LI

LI:<no>

UNLOCK LI

Unlock LI:NAME=RACK:<no>/LI:<no>;

System Response:


Test Result:




84 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



b BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM


11 Logon


UserName:<user>

Password:<password>

Ok



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



System Response:



System Response:



System Response:



A50016-G5100-A324-01-7620

85


Id:0900d8058012fa48


The module replacement was successful:– If the test outcome was “pass”, and– If there are no relevant active alarms, and– If there are no red LEDs, except R1/RE on ALCO.


Yes h......... 18

No h ......... 14






Yes h......... 16

No h ......... 17




17 Call TAC

h ......... 20





h ......... PROC: 3.25

86 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48





END

A50016-G5100-A324-01-7620

87


Id:0900d8058012fa48

3.18 PA / DCPA

g Modules PA and DCPA are both created as module PA!


g It is only possible to switch off the power for both PA and TPU!

Therefore, it is necessary to change the administrative state and to run the test for TPU too.

g If you replace a PA with ESN data by the enhanced version without ESN data, you must delete the PA after the replacement and re-create it. This is necessary for the automatic update of the Remote Inventory Data.


See ........... 5.5.2






Yes h......... PROC: 3.24


!CAUTION

Switch off the power before exchanging the modules PA and/or DCPA!



ACHTUNG

Strom abschalten, bevor die Module PA und/oder DCPA ausgetauscht werden.


88 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48






– for module TPU see 3.23 "TPU / DCTPU"

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

PA

PA:<no>

LOCK PA

Lock PA:NAME=RACK:<no>/PA:<no>;


1. Switch power off by means of the corresponding fuse, refer to chapter 4.7 "DC Fuse Panel / Connection Board"

2. Disconnect all semi-rigid cables at module PA3. Remove affected module PA and/or DCPA4. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced– any jumpers have to be inserted and any switches set identically to those on the

module which is being replaced. Refer to chapter 4.17 "PA"5. Insert prepared module6. Connect all semi-rigid cables at module PA7. Switch power on by the corresponding fuse.

System Response:



!CAUTION



A50016-G5100-A324-01-7620

89


Id:0900d8058012fa48



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

PA

PA:<no>

PERFTEST PA

Perftest PA:NAME=RACK:<no>/PA:<no>;



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

PA

PA:<no>

UNLOCK PA

Unlock PA:NAME=RACK:<no>/PA:<no>;

System Response:


Test Result:




System Response:



90 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


8 Get Active Alarms

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>






Yes h......... 14

No h.......... 10






Yes h......... 12

No h.......... 13





System Response:



A50016-G5100-A324-01-7620

91


Id:0900d8058012fa48

13 Call TAC

h ......... 16





h ......... PROC: 3.25




END

92 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.19 PCM Lines



h.......... PROC: 3.1

END

A50016-G5100-A324-01-7620

93


Id:0900d8058012fa48

3.20 RXAMCOg Module RXAMCO or RXAMCO_WITH RACKEXT is managed via the managed

object RXMUCO in the LMT.


g Module RXAMCO may be removed while power is on!

g Locking of an RXAMCO used for rack extension (created as RXAMCO_WITH RACKEXT) leads to a loss of the cell!


See ........... 5.5.2


– Module(s) ??

– BTS-no ??

– Rack-no ??

– Module address ??





Yes h......... PROC: 3.24






b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

94 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


RACK

RACK:<no>

RXMUCO

RXMUCO:<no>

LOCK RXMUCO

Lock RXMUCO:NAME=RACK:<no>/RXMUCO:<no>;


1. Disconnect all semi-rigid cables2. Remove affected module3. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced4. Jumpers have to be inserted and any switches set identically to those on the module

which is being replaced. Refer to chapter 4.19 "RXAMCO", 4.21 "RXMUCO" or 4.22 "RXMUCO2"

5. Insert prepared module6. Connect all semi-rigid cables


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

RXMUCO

RXMUCO:<no>

PERFTEST RXMUCO

Perftest RXMUCO:NAME=RACK:<no>/RXMUCO:<no>;

System Response:



!CAUTION



A50016-G5100-A324-01-7620

95


Id:0900d8058012fa48


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

RXMUCO

RXMUCO:<no>

UNLOCK RXMUCO

Unlock RXMUCO:NAME=RACK:<no>/RXMUCO:<no>;

8 Get Active Alarms

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



System Response:


Test Result:




System Response:



System Response:



96 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48





Yes h......... 14

No h.......... 10






Yes h......... 12

No h.......... 13





13 Call TAC

h.......... 16





h.......... PROC: 3.25

A50016-G5100-A324-01-7620

97


Id:0900d8058012fa48




END

98 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.21 RXAMODg If the suspected module is not “disabled/failed”, it may still be used for calls. To

make sure that no calls are lost, check whether the corresponding TRX is shut down before the module is locked/replaced. If the TRX is still in use, call the OMC to have it shut down. For more information, refer to 1.5.2 "Avoiding the Loss of Calls".

g Module RXAMOD may be removed while power is on!


See ........... 5.5.2


– Module(s) ??

– BTS-no ??

– Rack-no ??

– Module address ??





Yes h......... PROC: 3.24

No h.......... 3– VSWR Alarm

– Cable Problem

– Transmitter Problem

– Receiver Failure/Problem

– Transceiver Problem





b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

A50016-G5100-A324-01-7620

99


Id:0900d8058012fa48

RXAMOD

RXAMOD:<no>

LOCK RXAMOD

Lock RXAMOD:NAME=RACK:<no>/RXAMOD:<no>;


1. Disconnect both antenna cables 7 / 16 “2. Remove the whole mast head unit (MHU)3. Install a new mast head unit (MHU)4. Connect both antenna cables 7 / 16 ”


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

RXAMOD

RXAMOD:<no>

PERFTEST RXAMOD

Perftest RXAMOD:NAME=RACK:<no>/RXAMOD:<no>;

System Response:



!CAUTION



!CAUTION

Do not mix up the cables because the power supply is fed into the RF output of the module!

System Response:


100 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

RXAMOD

RXAMOD:<no>

UNLOCK RXAMOD

Unlock RXAMOD:NAME=RACK:<no>/RXAMOD:<no>;

8 Get Active Alarms

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>




The module replacement was successful:– If the test outcome was “pass”, and– If there are no relevant active alarms, and

Test Result:




System Response:



System Response:



A50016-G5100-A324-01-7620

101


Id:0900d8058012fa48

– If there are no red LEDs, except R1/RE on ALCO.


Yes h......... 14

No h ......... 10






Yes h......... 12

No h ......... 13





13 Call TAC

h ......... 16





h ......... PROC: 3.25



102 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48



END

A50016-G5100-A324-01-7620

103


Id:0900d8058012fa48

3.22 RXMUCOg RXMUCO can be module RXMUCO or module RXAMCO/RXAMCO_WITH

RACKEXT

g Module RXMUCO may be removed while power is on!


g Locking of an RXMUCO used for rack extension (created as RXAMCO_WITH RACKEXT) leads to a loss of the cell!


See ........... 5.5.2

Note the values specified in the fault message, for example:– Module(s) ??– BTS-no ??– Rack-no ??– Module address ??





Yes h......... PROC: 3.24






b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

104 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


RACK

RACK:<no>

RXMUCO

RXMUCO:<no>

LOCK RXMUCO

Lock RXMUCO:NAME=RACK:<no>/RXMUCO:<no>;


1. Disconnect all semi-rigid cables2. Remove affected module3. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced4. Jumpers have to be inserted and any switches set identically to those on the module

which is being replaced. Refer to chapter 4.19 "RXAMCO", 4.21 "RXMUCO" or 4.22 "RXMUCO2"

5. Insert prepared module6. Connect all semi-rigid cables


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

RXMUCO

RXMUCO:<no>

PERFTEST RXMUCO

Perftest RXMUCO:NAME=RACK:<no>/RXMUCO:<no>;

System Response:



!CAUTION



A50016-G5100-A324-01-7620

105


Id:0900d8058012fa48


b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

RXMUCO

RXMUCO:<no>

UNLOCK RXMUCO

Unlock RXMUCO:NAME=RACK:<no>/RXMUCO:<no>;

8 Get Active Alarms

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



System Response:


Test Result:




System Response:



System Response:



106 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48





Yes h......... 14

No h.......... 10






Yes h......... 12

No h.......... 13





13 Call TAC

h.......... 16





h.......... PROC: 3.25

A50016-G5100-A324-01-7620

107


Id:0900d8058012fa48




END

108 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.23 TPU / DCTPU


g Modules TPU and DCTPU are both created as module TPU!

g It is only possible to switch off the power for both PA and TPU! Therefore, it is neses-sary to change the administrative state and to run the test for PA, too.


See ........... 5.5.2


– Module(s) ??– BTS-no ??– Rack-no ??– Module address ??





Yes h......... PROC: 3.24

No h.......... 3– VSWR Alarm

– Cable Problem

– Transmitter Problem

– Receiver Failure/Problem

– Transceiver Problem



!CAUTION

Switch off the power before exchanging modules TPU and/or DCTPU!



ACHTUNG!

Strom abschalten, bevor die Module TPU und/oder DCTPU ausgetauscht werden.


A50016-G5100-A324-01-7620

109


Id:0900d8058012fa48



– for module PA see 3.18 "PA / DCPA"

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

TPU

TPU:<no>

LOCK TPU

Lock TPU:NAME=RACK:<no>/TPU:<no>;


1. Switch power off by means of the corresponding fuse, refer to chapter 4.7 "DC Fuse Panel / Connection Board".

2. In case of TPU, disconnect all semi-rigid cables from TPU.3. Remove affected module TPU and/or DCTPU.4. Select a module with a functional HW/SW state compatible to that of the module

which is being replaced.5. Insert prepared module.6. Connect all semi-rigid cables at module TPU.7. Switch power on by the corresponding fuse.



b BSS


System Response:



!CAUTION



110 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

TPU

TPU:<no>

PERFTEST TPU

Perftest TPU:NAME=RACK:<no>/TPU:<no>;



b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

TPU

TPU:<no>

UNLOCK TPU

Unlock TPU:NAME=RACK:<no>/TPU:<no>;

8 Get Active Alarms

b BSS


BSS-EQUIPMENT

System Response:


Test Result:




System Response:



A50016-G5100-A324-01-7620

111


Id:0900d8058012fa48

BTSE

BTSE:<no>






Yes h......... 14

No h ......... 10






Yes h......... 12

No h ......... 13





13 Call TAC

h ......... 16

System Response:



112 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48






h.......... PROC: 3.25




17 END

A50016-G5100-A324-01-7620

113


Id:0900d8058012fa48

3.24 TX/RX Pathg In most cases, alarms in the TX/RX path originate from loose or damaged cables.

Therefore, the relevant cables must be checked first, according to the following pro-cedure.

If the alarm cannot be cleared in this way, the suspected modules must be replaced. Note that the failure cause may be located in any module of the TX/RX path:

– The module(s) addressed in the error message– Combining equipment (DUCOM, HYCOM, RXAMCO, RXMUCO)– Antenna (including RXAMOD)– TPU– PA

It is recommended to start with the replacement of the module which is addressed in the fault message. Afterwards - if the error is still there - to take the other modules in the TX/RX path into consideration.

g To make sure that no calls are lost, check whether the corresponding TRX is shut down before cables/modules are disconnected. If the TRX is still in use, call the OMC to have it shut down. For more information, refer to 1.5.2 "Avoiding the Loss of Calls".

Examples for Alarms in the TX/RX Path:

Error ID 34892 RF power reflected into power stage

Error-ID 49365, Cell 0,1,2: Antenna System TX

1 Cable Connections Fastened Correctly?

Are the TX/RX cable connections of the suspected module(s) fastened correctly?

Yes h......... 9No h ......... 2

2 Fasten Cable Connections

Fasten the cables by tightening their coupling nuts with a torque wrench.




4 Lock All Disabled Modules

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

114 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


RACK:<no>

<Module>

<Module>:<no>

LOCK <Module>

Lock <Module>:NAME=RACK:<no>/<Module>:<no>;

5 Test All Disabled Modules

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

<Module>

<Module>:<no>

PERFTEST <Module>

Perftest <Module>:NAME=RACK:<no>/<Module>:<no>;

6 Unlock All Locked Modules

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

<Module>

<Module>:<no>

UNLOCK <Module>

Unlock <Module>:NAME=RACK:<no>/<Module>:<no>;

7 Check the LEDs

Do the LEDs signal normal operation after a few seconds? (No red LEDs may be on except R1/RE on ALCO.)

Yes h......... 8No h.......... 11

A50016-G5100-A324-01-7620

115


Id:0900d8058012fa48

8 Additional Check

If an LMT is available, perform the following command:

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>



If no LMT is available, call OMC to make sure that the BTSE has gone back to normal operation.

Does the alarm still appear?

Yes h......... 9No h ......... 12

9 Do the Cables Look O.K.?

Examine the cables visually for damages, such as sharp bends, cracks or bad soldering connections. Do the cables look O.K.?

Yes h......... 11

No h ......... 10

10 Call TAC

Call TAC to have the damaged cable(s) replaced.

h ......... 12

11 Continue with the Replacement Procedure

Continue with the replacement procedure of the module, which is addressed in the fault message. Afterwards - if the fault is still there - take the other modules in the TX/RX path into consideration.





END

System Response:



116 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


3.25 Remote Inventory Data UpdateAfter replacement of a nob_RIU component, the remote inventory data and the backup copy must be updated.

1 Upload IDT File from BTSE

You must upload the Remote Inventory Data that is stored in the BTSE as IDT file to the LMT PC.

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

REMINV

REMINV:<no>

UPLLIDF REMINV

[BASICS]

(DESTDIR=<path>)

(FILE=<file name>)

OVERWRITE=YES


Additional Information: The attributes DESTDIR and FILE are optional. If no special path or file name is entered, the file is uploaded to the default directory of the IDF Evo-lution. If the attribute OVERWRITE=<yes> is selected, a former version of an uploaded IDT file will be overwritten.



b To start the IDF Evolution select “IDF GSM” -> “IDF Editor” from the Windows program menu.

3 Open IDT File

b To open the IDT file:

1. Select “File” -> "Open" from the menu.2. Select the uploaded file from the list in the appearing window; e.g.: <C:...\LMT<ver-

sion>\Idf\Upload\BTSE.idt>.3. Double-click on the file name or click on the "Open" button.4. Select “View” -> “nob_RIUs” from the menu to get a list of all nob_RIUs.

4 Edit Remote Inventory Data of the Replaced Unit

The records of the nob-RIUs are shown in bold letters. Only these records are editable.

A50016-G5100-A324-01-7620

117


Id:0900d8058012fa48

The data can be edited manually or automatically via the 2D-Code Reader.

b To edit the Remote Inventory Data of the nob_RIU units:

1. Select the I-Record Inventory Data of the unit you need to edit and click the right mouse button.

2. Click on the appearing “Edit” button.

Figure 8 Editing Nob_RIU Units

3. Edit the data manually, or click on the “Scan” button to use the 2D-Code Reader.4. If the 2D-Code Reader is used for the first time, select the serial port in the appearing

window.5. To start the scanning process, press the button on the 2D-Code Reader. 6. The data are inserted into the corresponding fields. Confirm the data by clicking on

the “OK” button.7. Select “File” -> “Save” from the menu.

5 Export Remote Inventory Data for Backup

Now, you must create an IDF file for backup. This IDF file replaces the IDF file delivered with the rack, because it contains the modified data of the BTSE.

b To export the Remote Inventory data for backup:



tation.

118 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


6 Export Nob_RIU Data

The nob_RIU data must be attached to the Remote Inventory data stored in the BTSE (IDT file). In order to attach the nob_RIU data to the IDT file, you must export them into a NOB file.


1. Select “Export” -> "NOB" from the menue.2. A window opens in which you can edit the file name and select the directory in which

the file is saved. By default, the file name is composed of the “SalesUniqueName” with the extension “.nob”. Edit the file name and select the source directory or confirm the default name and directory by clicking on the “Save” button.


4. A question window is displayed: “Create BTS_NRIU for download?” Confirm by clicking on the “Yes” button. An attention window is displayed that informs you on the destination path and file name to which the BTS_NRIU download is saved. Confirm by clicking on the “OK” button.

7 Download nob_RIU File to BTSE

Change to the LMT application!

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

REMINV

REMINV:<no>

DNLIDF REMINV

[BASICS]

SRCDIR=<enter the source directory in which the exported NOB file was saved>

Dnlidfd REMINV:NAME=REMINV:<no>,SRCDIR=<source directory>





END

A50016-G5100-A324-01-7620

119


Id:0900d8058012fa48

3.26 Remote Inventory Data CreationAfter replacing the CCTRL, it is necessary to rebuild the inventory data that was stored on the removed CCTRL. Usually, a backup IDF file is available for this purpose, which is stored on site with the site specific documentation. The following procedure describes how to enter the data by hand if there is no backup IDF file.

1 Upload IDT File from the BTSE

You must upload the Remote Inventory Data that is stored in the BTSE as IDT file to the LMT PC. This file contains the remote inventory data of the ob_RIU modules.

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

REMINV

REMINV:<no>

UPLLIDF REMINV

(DESTDIR=<path>)

(FILE=<file name>)

OVERWRITE=YES


Additional Information: The attributes DESTDIR and FILE are optional. If no special path or file name is entered, the file is uploaded to the default directory of the IDF Evo-lution. If the attribute OVERWRITE=<yes> is selected, a former version of an uploaded IDT file will be overwritten.



b To start the IDF Evolution select “IDF GSM” -> “IDF Editor” from the Windows program menu.

3 Open IDT File

b To open the IDT file:

1. Select “File” -> "Open" from the menu.2. Select the uploaded file from the list in the appearing window; e.g.: <C:...\LMT<ver-

sion>\Idf\Upload\BTSE.idt>.3. Double-click on the file name or click on the "Open" button.

4 Create the Remote Inventory Data of the nob_RIU Units

The data can be entered manually or automatically via the 2D-Code Reader.

120 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012fa48


b To create the Remote Inventory Data of the nob_RIU units:

1. Click the right mouse button on the N-Record.2. Click on the appearing “Create” button.3. Select the network entity type (“Ney Type”), the Functional Address and Type of the

module you want to create (“FunctionalAddress:FunctionalAddressType”), and the equipment position (“SBS_Equipment_Position”).

4. Click on the “Inventory” button.5. A pop-up window opens in which you must enter the data. Key in the data, or click

on the “Scan” button to use the 2D-Code Reader.6. If the 2D-Code Reader is used for the first time, select the serial port in the appearing

window.7. To start the scanning process, press the button on the 2D-Code Reader. The data

will be inserted into the corresponding fields.8. Confirm the data by clicking on the “OK” button.9. Repeat these steps for the next module you want to create.10. After creating all nob_RIU units, select “File” -> “Save” from the menu to save the

data.

5 Export Remote Inventory Data for Backup

Now, you must create an IDF file for backup.

b To export the Remote Inventory data for backup:



tation.

6 Export Nob_RIU Data

The nob_RIU data must be attached to the Remote Inventory data stored in the BTSE (IDT file). In order to attach the nob_RIU data to the IDT file, you must export them into a NOB file.


1. Select “Export” -> “NOB” from the menu.2. A window opens in which you can edit the file name and select the directory in which

the file is saved. By default, the file name is composed of the “SalesUniqueName” with the extension “.nob”. Edit the file name and select the source directory or confirm the default name and directory by clicking on the “Save” button.


4. A question window is displayed: “Create BTS_NRIU for download?” Confirm by clicking on the “Yes” button. An attention window is displayed that informs you on the destination path and file name to which the BTS_NRIU download is saved. Confirm by clicking on the “OK” button.

7 Download the nob_RIU File to the BTSE

Change to the LMT evolution window.

A50016-G5100-A324-01-7620

121


Id:0900d8058012fa48

b BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

REMINV

REMINV:<no>

DNLIDF REMINV

SRCDIR=<source directory>

DNLIDFD REMINV:NAME=REMINV:<no>, SRCDIR=”C:...\LMT<version>\Idf\Dnload”;

Additional Information: SRCDIR: enter the source directory to which the exported NOB file was saved, for example C:...\IDF GSM<version>\Idf\Dnload.





END

122 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de

Tables Lists and Figures

4 Tables Lists and Figures

4.1 Hardware Architecture

Figure 9 Functional Blocks, 6 Carrier BTSE with HYCOM (1 Cell / 4 Carriers)

BBSIGBBSIG

BBSIGBBSIG

BU

S1

BU

S2

LI

PA

Site Inputs

Site Outputs

LMT

TPU

CCTRL

CCLK

PA TPUPA TPU

TPU

ALCO

Diversity

PA

-48 V DC

FAN0

FAN1

FAN2

DCPADCPA

DCPADCPA

GPSU FPDCTPU

A bis

(OVPT, NTPM or µWave)

RXAMOD

RXAMOD

HYCOM

RXMUCO

RXMUCO

A50016-G5100-A324-01-7620

123

MMN:BTSE BS-60 Tables Lists and Figures

Id:0900d805800a05de

Figure 10 Functional Blocks, 6 Carrier BTSE with DUCOM (1 Cell / 4 Carriers)

BBSIGBBSIG

BBSIG

BU

S1

BU

S2

LI

PA

Site

Site

LMT

Diversity

TPU

CCTRL

CCLK

PA TPUPA TPU

ALCO

PA

-48 V DC

FAN0

FAN1

FAN2

DCPADCPA

DCPADCPA DCTPU

A bis

RXAMCO

RXAMCO

BBSIGTPU

FP

Inputs

Outputs

DUCOM

GPSU

124 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Figure 11 Functional Blocks, 6 Carrier BTSE with FICOM (1 Cell / 6 Carriers)

LI

Site Inputs

Site Outputs

LMT

CCTRL

CCLK

ALCO

-48 V DCFP

A bis

BBSIG

Diversity

FAN0

FAN1

FAN2 DCTPUDCTPU

BU

S1

BU

S2

PA TPUPA TPU

PA TPUTPUPA

TPUPATPUPA

FICOM

RXFIL

RXFIL RXAMCO

RXMUCO

RXAMCO

DCPA

RXMUCO

GPSU

A50016-G5100-A324-01-7620

125


Id:0900d805800a05de

4.2 Front View of the BS 60 Rack and Mounting Positions

Figure 12 BS 60 Rack with ACOM Frame (Front View)

BB

SIG

0B

BS

IG 1

BB

SIG

2B

BS

IG 3

BB

SIG

4B

BS

IG 5

SIEMENS

CB FP

MC

LK

0

CC

TR

L 0

LI 0

ALC

O 0

GPSU 0

FAN 0

FAN 1

FAN 2

Air Filter

DC

PA

0

DC

TP

U 0

DC

PA

1

DC

TP

U 1

DC

PA

2

DC

TP

U 2

DC

PA

3

DC

TP

U 3

DC

PA

4

DC

TP

U 4

DC

PA

5

DC

TP

U 5

PA

0

TP

U 0

PA

1

TP

U 1

PA

2

TP

U 2

PA

3

TP

U 3

PA

4

TP

U 4

PA

5

TP

U 5

RX

MU

CO

0R

XM

UC

O 1

RX

MU

CO

2R

XM

UC

O 3

RX

MU

CO

4R

XM

UC

O 5

RX

MU

CO

6R

XM

UC

O 7

ACOM 0 ACOM 1 ACOM 2

EX

AC

O 0

RF

LB

OB

IX 0

OB

IX 1

OB

IX 2

MC

LK 1

CC

TR

L 1

LI 1

MUT ROW

RXAMOD

5

RXFIL5

RCAP

RXAMOD4

RXAMOD3

RXAMOD2

RXAMOD1

RXAMOD

0

RXFIL4

RXFIL3

RXFIL2

RXFIL1

RXFIL0

99S001...S006

98D002...D012

00

01

11

B

C

C

D

E101

F

G101

H

J

K101

02

08

ACOMx can be:- HYCOMx- DUCOMxor FICOMx

RXAMOD 0...5 must be used with RXMUCO 0...5 at the rack entry.

If DUCOM is used, or RXFIL in the RX-path, RXAMCO is required at the rack entry

RXMUCO 6, 7 are for cascading purposes only.

MCLK 1, CCTRL 1, LI 1, OBIX 0,1,2, RFLB 0, EXACO 0 are not relevant

LMTconnector

GPSU 1

HMOs if FICOM is used as ACOM:FTNF, FVSWR

Hardware Related Managed Object (HMO): CCLK

Additional HMOs: BPORTLAPDLEXCONNECTENVABTSE

OVPT

HMOs forPA0 ... 5 andDCPA0 ... 5:

PAx

HMOs forTPU0 ... 5 andDCTPU0 ... 5:

TPUx

126 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Mounting Unit (MUT)

Device / Module

Name Long Name

00 C002 OVPT Overvoltage Protection and Tracer

01 FP / CB Fuse Panel / Connection Board

02 F:ACOM Frame for Antenna Combiner (ACOM)

08 F:BTS6 Frame for 6 Carrier BTSE

11 FIBOX Air Filter Box

99 S001 RXAMOD 0...5 Receiver Antenna Module 0...5

98 D002..D005

RXFIL 0...5 Receiver Frequency Bandpass Filter 0...5

Table 1 Mounting Units for the 6 Carrier BTSE Rack R:BS 60.

Position Device / Module

Mounting Slot-ID Name Long Name

08 H103 01H M:BBSIG 0 Baseband Signal Processing 0






08 H187 09H M:MCLK 0 Master Clock 0

08 H199 0AH1) free (M:MCLK 1) free (reserved for Master Clock 1)

08 H211 0BH M:CCTRL 0 Core Controller 0

08 H223 0CH1) free (M:CCTRL 1) free (reserved for Core Controller 1)

Table 2 Mounting Positions and Slot-IDs for the Core Part of the Frame

A50016-G5100-A324-01-7620

127


Id:0900d805800a05de

08 H235 0DH M:LI 0 Link Interface 0

08 H247 0EH1) free (LI 1) free (reserved for LI 1)

08 H259 0FH10H1)

M:ALCO 0 2) Alarm and Controller Board 0 2)

08 H271 1DH3) M:GPSU 1 Generic Power Supply 1

08 J271 1EH3) M:GPSU 0 Generic Power Supply 0

Notes:

1) Slot-ID is for redundancy purpose only, not used in this release

2) The new ALCO Q300 without redundancy (S30861-Q300-X-1-*) uses only one Slot-ID (=0FH)

3) Simulated Processor ID for non-processor units



08 F103 DCPA 0 5) DC/DC Converter for PA 0

08 F119 DCTPU 0 5) DC/DC Converter for TPU 0











08 F283 11/12H 2) free (M:OBIX 0) free (reserved for OBIX 0)



08 C105 21H PA 0 5) Power Amplifier 0

08 C128 21H TPU 0 5) Transceiver and Processor Unit 0


Table 3 Mounting Positions and Slot-IDs for the Carrier Part of the Frame



Table 2 Mounting Positions and Slot-IDs for the Core Part of the Frame (Cont.)

128 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de











Notes:

2) Slot-ID is reserved for OBIX and not used in this release

5) PAn+DCPAn and TPUn+DCTPUn respectively with the same relative number make up one LRU



Table 3 Mounting Positions and Slot-IDs for the Carrier Part of the Frame (Cont.)



02 Bxxx Carrier related Switch Box (not for BR 3.6)

02 B002 50H 3) ACOM 0 1) Antenna Combiner 0 (vertical version)



02 B008 80H 3) M:RXMUCO 0 or Receiver Multicoupler 0 or

M:RXAMCO 0 Receiver Antenna Module and Multicoupler 0







02 B012 90H 3) free free

2) (M:EXACO 0) (reserved f. Ext. Alarm Controller 0)

Table 4 Mounting Positions and Slot-IDs: ACOM Frame; HYCOM, DUCOM

A50016-G5100-A324-01-7620

129


Id:0900d805800a05de

02 C008 84H 3) M:RXMUCO 4 or Receiver Multicoupler 4 or


02 C009 85H 3) M:RXMUCO 5 or Receiver Multicoupler 5 or


02 C010 86H 3) M:RXMUCO 6 5) Receiver Multicoupler 6

02 C011 87H 3) M:RXMUCO 7 5) Receiver Multicoupler 7

02 C012 91H 3) free free

2) (M:RFLB 0) (reserved for RF Loopback 0)



Table 4 Mounting Positions and Slot-IDs: ACOM Frame; HYCOM, DUCOM (Cont.)

Notes:

1) ACOM can be DUCOM or FICOM. If FICOM have to be installed to combine more than 2 carriers, the equipment for one cell occupies more than one ACOM slot in the ACOM subrack. In this case the mechanical assignment rule Cell# / ACOM slot# is no longer valid. Also new Slot-IDs are generated for the FICOM modules (see next table).

2) Slot-ID is not used in this release


5) RXMUCO 6, 7 are for cascading purposes only



02 Bxxx Carrier related Switch Box (not for BR 3.0)

02 B002 B0H FBM2_0 1) FICOM Base Module (2 RF inputs) for cell 0

02 B004 or 02 B006

B1H FBM2_1 1) FICOM Base Module (2 RF inputs) for cell 1

02 B006 B2H FBM2_2 1) FICOM Base Module (2 RF inputs) for cell 2

02 B002 C0H, C1H FICOM_TNF 0,1 FICOM_TNF 0 and 1 fitted into FBM 2 for cell 0

02 B004 or 02 B006

D0H, D1H FICOM_TNF 0,1 FICOM_TNF 0 and 1 fitted into FBM 2 for cell 1

02 B006 E0H, E1H FICOM_TNF 0,1 FICOM_TNF 0 and 1 fitted into FBM 2 for cell 2

02 B/C004 02 B/C006

C2H...C5H FICOM_TNF 2 .5 FICOM_TNF 2...5 fitted into FXMx for cell 0 7)

Table 5 Mounting Positions and Slot-IDs: ACOM Frame; FICOM

130 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


C6H, C7H FICOM_TNF 6,7 FICOM_TNF 6 and 7 fitted into FXMx for cell 0 (not relevant for BR 3.0)

7)

02B/C006 D2H, D3H FICOM_TNF 2,3 FICOM_TNF 2 and 3 fitted into FXMx for cell 1 7)

D4H...D7H FICOM_TNF 4...7 FICOM_TNF 4...7 fitted into FXMx for cell 1 (not relevant for BR 3.0)

7)

E2H E7H FICOM_TNF 2...7 FICOM_TNF 2 and 7 fitted into FXMx for cell 2 (not relevant for BR 3.0)

7)

02B008 80H 3)) M:RXMUCO 0 or Receiver Multicoupler 0 or

M:RXAMCO 0 Receiver Antenna Module and Multicoupl. 0

02B009 81H 3) M:RXMUCO 1 or Receiver Multicoupler 1 or






02B012 90H 3) free free

2) (M:EXACO o) reserved f. Ext. Alarm Controller 0)

02C008 84H 3) M:RXMUCO 4 or Receiver Multicoupler 4 or


02C009 85H 3) M:RXMUCO 5 or Receiver Multicoupler 5 or


02C010 86H 3) M:RXMUCO 6 5) Receiver Multicoupler 6

2)

02C011 87H 3) M:RXMUCO 7 5) Receiver Multicoupler 7

2)

02C012 91H 3) free free

2) (M:RFLB 0) (reserved for RF Loopback 0)



Table 5 Mounting Positions and Slot-IDs: ACOM Frame; FICOM (Cont.)

Notes::

1) If FICOMs have to be installed in the ACOM subrack to combine more than 2 carriers, the equipment for one cell occupies more than one ACOM slot. In this case the mechanical assignment rule Cell# / ACOM slot# is no longer valid.

2) Slot-ID is not used in this release


A50016-G5100-A324-01-7620

131


Id:0900d805800a05de

4.3 General Information on BTSE LEDsThis chapter contains the common LED signal mechanisms of the BTSE boards. All the modules of the BTSE and the rack itself have LEDs to indicate their status, except the filter box and the fuse panel in the BTS rack and the RXAMOD, which is mounted close to the RX antenna.

After the startup a HW test will be executed on each module of the BTSE. Detected HW errors will be indicated by the flashing reset LED where the number of the failed test is binary coded in the flashing sequence. The test number is an 8-bit value where the LSB (Least Significant Bit) is transferred first and the MSB (Most Significant Bit) last.

General meanings of the LED colour when the LED is on:

5) RXMUCO 6, 7 are for cascading purposes only

7) One TNF is fitted into an FXM1 (FICOM Expansion Module with 1 RF input, half size) or 2 TNFs are fitted into an FXM2 (FICOM Expansion Module with 2 RF inputs)



08 K101 40H Fan 0 Fan Unit 0

08 G101 41H Fan 1 Fan Unit 1

08 E101 42H Fan 2 Fan Unit 2

99 S001 70 H RXAMOD 0 Receiver Antenna Module 0






98 D002 RXFIL 0 Receive Frequency Bandpass Filter 0






Table 6 Mounting Positions and Simulated Processor IDs

- green: Hardware and software are O.K.

- red: After reset, during software initialization (one for each processor)

- yellow: Active module of redundant boards

132 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


There are additional LEDs and further meanings specific to each type of module, these are described in their respective section. There are also LEDs which show the status of software. These are described in the following module description.

4.4 ALCO

TAD

ALCO without redundancy (Q300)

RY RE

AC S3

S1 S2

RES

LED red

LED red

LED red

LED green

LED yellow

LED red

Pushbutton

ALCO with redundancy (Q342)

Block 0

Block 1

TAD

RY R1

AC S3

S1 S2

RES 1

LED red

LED red

LED red

LED green

LED yellow

LED red

Pushbutton

S1 S2

AC S3

RY R0

RES 0

LED red

LED red

LED red

LED red

LED yellow

LED green

Pushbutton

A50016-G5100-A324-01-7620

133


Id:0900d805800a05de

Figure 13 ALCO (Front View)

LED

AC Active block

The active block LED indicates which ALCO block (0 or 1) has taken over service.

It is then switched on parallel to the ready LED.

RY Ready

The Ready LED indicates that the ALCO has passed the initial module tests and is ready for the communication with the connected interface partner (CCTRL or Test-PC).

It is switched on by the subsystem RC after successful initialization of the O&M subsystems.

R0 RESET Block 0

R1 Reset Block 1

RE The Reset LED indicates the phase from a reset until the finished recovery in the Load-SW. It is switched on by a reset and off by the subsystem RC after successful initialization of the O&M subsystems.

An additional task is the signalling of hardware errors detected during the initial (Boot-SW) or extended (Load-SW) hardware tests.

S1 not used

S2 not used

S3 not used

Switch

RES 0 Reset Block 0 (ALCO with Redundancy)

Resets the ALCO-block 0

RES 1 Reset Block 1 (ALCO with Redundancy)

Resets the ALCO-block 1

RES Resets ALCO (ALCO without Redundancy)

134 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Test Adapter

TAD Test Adapter

50 pin AMP jack for ALCO (test adapter for V24 interface access)

Plu

g

1

Fro

nt

Pan

el

D6

Rack-ID

OFF ON

EPROM

S10

S10

S1

S2

S3

S4

The switch positions are:ON = “0”OFF = “1”The only permitted address is “zero”

Address Switch 1 Switch 2 Switch 3 Switch 4

0 ON ONONON

A50016-G5100-A324-01-7620

135


Id:0900d805800a05de

Figure 14 ALCO (Top View)

4.5 BBSIG

Figure 15 BBSIG44 (Front View)

BBSIG44

TAD

RBB1

SPA1

RES

LED red

LED green

LED red

LED green

Pushbutton

RBBC

RY

136 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


LED

RBB 1 Reset BB1 Base Band Slave 1

RBBC Reset BBCBBC Base Band Controller

The reset LEDs indicate the phase from a reset until the moment when all O&M subsystems in the Load-SW are initialized.

The LED is switched on: by a reset

off: by the recovery management

Note:

1) An additional task is the signalling of hardware errors detected during the initial (Boot-SW) or extended (Load-SW) hardware tests. The LED flashes with a sequence in which the test number is coded.

2) In case the Bus-1 clock is missing at the initial hardware tests, the RBBC LED is switched off 0.25 seconds before a SW-reset is initiated.

SPA1 It is turned on and off each 64th traffic burst sent to any TPU on BUS 1 requesting and/or providing data from/to Um interface (Spare 1).

It is also called SW signal 1 LED.

RY Ready

The Ready LED indicates that the BBSIG has passed the initial module tests and is ready for the communication to the connected interface partner (CCTRL or Test PC). This LED is also called SW signal 2 LED.

It is switched

on :by the boot management after the initial module tests and task initialization in Boot-SW

off: by reset or a failed hardware test

Switch

RES Reset

Resets all BBSIG processors

Test Adapter

TAD Test Adapter

100 pin AMP jack for test adapter for C 40 boards

A50016-G5100-A324-01-7620

137


Id:0900d805800a05de

Figure 16 BBSIG44 (Top View)

Plu

g

Fro

nt

Pan

el

D104

EPROM

1

138 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


4.6 CCTRL

Figure 17 CCTRL (Front View)

LED

LED red

LED red

LED green

LED green

LED yellow

LED green

Pushbutton

TAD

RY

ACT

SPA1

RES

RBM

PRGA

SPA2

A50016-G5100-A324-01-7620

139


Id:0900d805800a05de

RY Ready

The Ready LED indicates that the CCTRL has passed the initial module tests and is ready for the communication to the connected interface partner (LMT or Test PC).

It is switched

on: by the boot management after the initial module tests and task initialization in Boot-SW


RBM Reset Bus Master Controller

The Reset LED indicates the phase from a reset until the moment that

- all O&M subsystems are initialized

- the HW related objects are created

- the startup of the peripheral boards is enabled,

- a logon from LMT is possible (if no LMT is connected, the connection to the Abis will be established).

It is switched

on: by a reset

off: by the recovery management

Note:

An additional task is the signalling of hardware errors detected during the initial (Boot-SW) or extended (Load-SW) hardware tests. The LED flashes with a sequence in which the test number is coded.

ACT Active master

The Active Master LED signals which CCTRL has the master state.

It is switched

on: if the ready LED is switched on and the module has got the master state

off: by a reset

PRGA Programming Active

The flash LED is switched on when the programming voltage for the Flash EPROM is activated.

SPA1 not used

It is also called SW Signal 1 LED.

SPA2 The flashing SW Signal 2 LED signals a running OS (Operating System). This LED is also called SW Signal 2 LED

It is switched:

on: by the OS

off: by the OS and a reset

140 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Figure 18 CCTRL (Top View)

Switch

RES Reset

Resets the entire CCTRL.

Test Adapter

TAD Test Adapter

50 pin AMP jack for test adapter for serial interface access

Plu

g

Fro

nt

Pan

el

1

D88

EPROM

A50016-G5100-A324-01-7620

141


Id:0900d805800a05de

4.7 DC Fuse Panel / Connection Board

Figure 19 Fuse Panel / Connection Board for 11 Fuses

Figure 20 Fuse Panel / Connection Board for 12 Fuses

PCM 30(RCAP)

01Fuse

Unit

Type 4A

FAN0 - 2

024A

GPSU0 - 1

0316A

RXMUCO2

RXAMCO

04

0 - 7

10A

BBSIG0 - 5

0510A

TPUPA

06

0

10A

TPUPA

07

1

10A

TPUPA

08

2

10A

TPUPA

09

3

10A

TPUPA

10

4

10A

TPUPA

11

5

10A

A SIGN 048 V

48 V

48 V

FU 1 FU 6 FU 11

A SIGN 1

A SIGN 2

FI SIGN

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

PCM 30(RCAP)

01Fuse

Unit

Type 4A

TADC

024A

FAN0 - 2

034A

GPSU0 - 1

0416A

RXMUCO2

RXAMCO

05

0 - 7

10A

BBSIG0 - 5

0610A

TPUPA

07

0

10A

TPUPA

08

1

10A

TPUPA

09

2

10A

TPUPA

10

3

10A

TPUPA

11

4

10A

TPUPA

12

5

10A

HY SIGN 048 V

48 V

48 V

FU 1 FU 6 FU 12

HY SIGN 1

HY SIGN 2

FI SIGN

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

ON

OFF

Connector

142 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


HY SIGN 0 Hybrid Combiner Signalling for HYCOM 0



FI SIGN Filter Combiner Signalling (not used)

Jack

- 48 V

- 48 V

- 48 V

Fuse

Fuse 01........11

Fuse 01........12

A50016-G5100-A324-01-7620

143


Id:0900d805800a05de

4.8 DCPA

Figure 21 DCPA (Front View)

LED

PS Power Supply

This LED indicates: Power on

LED green

144 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


4.9 DUCOM

Figure 22 DUCOM2 (Front View)

LED green

LED red

LED red

Alarm 1

Power

Alarm 0

VSWR

Testout 0

Testout 1

TX0

TX1

TX2

TX3

RX0

RX1

1,5

1,7

2,0

ANT0 ANT1

LED green

LED red

LED red

Alarm 1

Power

Alarm 0

VSWR

Testout 1

TX0

TX1

RX0

RX1

1,5

1,7

2,0

ANT0 ANT1

Testout 0

CELWAVE

Scale 1:2

FOREM

A50016-G5100-A324-01-7620

145


Id:0900d805800a05de

Figure 23 DUCOM4 (Front View)

LED green

LED red

LED red

Alarm 1

Power

Alarm 0

VSWR

Testout 1

TX0

TX1

TX2

TX3

RX0

RX1

1,5

1,7

2,0

ANT0 ANT1

Testout 0

CELWAVE

LED green

LED red

LED red

Alarm 1

Power

Alarm 0

VSWR

Testout 0

Testout 1

TX0

TX1

TX2

TX3

RX0

RX1

1,5

1,7

2,0

ANT0 ANT1

Scale 1:2

FOREM

LED

Alarm 0 Alarm Indication (e.g.: VSWR >3) for antenna 0

Alarm 1 Alarm Indication (e.g.: VSWR >3) for antenna 1

Power This LED indicates voltage is present.

146 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Connector

RX 0 RX-output 0

RX-output 0 for connection with module RXAMCO

RX 1 RX-output 1

RX-output 1 for connection with module RXAMCO

Testout 0/1 Connector for test loop 1/2

TX 0 TX-input 0

TX-input 0 for connection with module PA: RF-output

TX 1 TX-input 1


TX 2 TX-input 2


TX 3 TX-input 3


AP 0 Antenna 0 Output

Output for antenna connection

AP1 Antenna 1 Output


Switch

Selector Voltage Standing Wave Ratio (VSWR)

A50016-G5100-A324-01-7620

147


Id:0900d805800a05de

4.10 FAN

Figure 24 FAN (Front View)

4.11 FICOMThere are two variants of FICOM: the Forem- and the Kathrein-FICOM. Within these variants one has to distinguish between basic and extension modules.

g Modules of the same supplier must be used for the basic and the expansion part!

Switch LED green

OFF

ON

LED

Power on This LED indicates: Power on

Switch

Power on/off

148 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Figure 25 Kathrein FICOM Base Module

LED green

TNF ALM

DC ON

VSWR ALM

TX 1

EXP

TEST OUT

RF

TNF AD0

LSBMSB

TNF AD1LED red

LED red

TX 0

LED redswitch

switch10

10

A50016-G5100-A324-01-7620

149


Id:0900d805800a05de

Figure 26 Kathrein FICOM Expansion Module

LED green

TNF ALM

DC ON

TX 1

EXPRF

TNF AD0

LSBMSB

TNF AD1LED red

LED red

TX 0

switch

switch

10

10

150 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Figure 27 Forem FICOM Base Module

TNF ALM

LSB

TNF AD0

1

0

DC ON

1

0

LSB

VSWR ALM

MSBMSB

RF EXP

ANT OUT

TEST OUT

TX 1

TX 0

TNF AD1

LED red

LED green

LED red

switch switch

LED

DC ON Direct Current On

DC is present

TNF ALM TNF alarm

indicates if a TNF is unable to tune

VSWR ALM VSWR alarm

A50016-G5100-A324-01-7620

151


Id:0900d805800a05de

VSWR is higher than the fixed threshold

Connectors

ANT OUT Output to antenna

RF/EXP Connector for RF Expansion

TEST OUT Test output

Output of RF test signal

TX1/TX2 TX-Input 1/2

TX-Input for connection with PA (-RF output)

Switches

TNF AD0/ TNF AD1

DIL Switch for TNF 0/1

8 bit DIL switch to address the TNF.

Bit 0...3 reserved for TNF address selection

Bit 4...5 reserved for cell selection

Bit 6...7 reserved for VSWR alarm threshold setting

152 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


4.12 GPSU

Figure 28 GPSU (Front View)

LED

PS Power Supply

All functions are O.K.

PIP Primary Input Power

Primary Input Power is O.K.

5 V The 5 V output is O.K.

12 V The 12 V output is O.K.

LED green

LED green

LED green

LED green

PIP

5V

PS

12V

5V12VPIP

A50016-G5100-A324-01-7620

153


Id:0900d805800a05de

4.13 HYCOM

Figure 29 HYCOM Vertical (Front View)

Connector

5 V

12 V

PIP Primary Input Power

LED green

LED red

PWR

ALMVSWR

1,51,72,0

ANTOUT

Scale 1:2

TESTOUT

TXIN 1

TXIN 0TXIN 2

TXIN 3

HYSIGN

LED green

LED red

PWR

ALMVSWR

1,51,72,0

ANTOUT

TESTOUT

TXIN 1

TXIN 0

HYSIGN

2-WAY 4-WAY

Connector

154 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


TX 0 TX-input 0


TX 1 TX-input 1


TX 2 TX-input 2


TX 3 TX-input 3


CONTHYSIGN Alarm and Signalling

Detection of combined configuration and operation parameters

ANT Antenna Output


Switch

Selector Voltage Standing Wave Ratio (VSWR)

A50016-G5100-A324-01-7620

155


Id:0900d805800a05de

4.14 LI

4.14.1 LI - Link Interface

Figure 30 LI (Front View)

LED

LED red

LED red

LED red

LED green

LED yellow

LED red

Pushbutton

TAD

RY

ACT

1ER-3

RES

RLIC

SPA

2ER-3

LED red

LED red

LED red

LED red

1RAI

1ER-6

2RAI

2ER-6

156 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


1/2RAI Remote Alarm Indication Port 1/2

The LED indicates the remote alarms (A-/E-Bit) received on port 1.

1/2ER-6 Port 1/2, Bit Error Rate > 10 Exp-6

If the BER BERis greater than 10 Exp-6 for 1 minute or PCM30 CRC4 errors are detected on port 1, this LED is switched on.

It will be switched off if the BER is less than 10 Exp-6 for 1 minute and no CRC4 errors are detected.

RY Ready

The Ready LED indicates that the LI has passed the initial module tests and is ready for communication to the connected interface partner (CCTRL or Test PC). It is switched on by the recovery management after successful initialization of the O&M subsystems.

RLIC Reset LI

The Reset LED indicates the phase from a reset until the finished recovery in the Load-SW. It is switched on by a reset and off by the recovery management after successful initialization of the O&M subsystems.


ACT Active

not used

SPA Spare

not used

1/2ER-3 Port 1/2, Bit Error Rate > 10 Exp-3

The LED will be switched on if the BER is > 10 Exp-3 for 1 sec or the signal or the frame synchronisation are lost on port 1. It will be switched off after the disturbances are removed.

Switch

RES Reset

Resets the link interface.

Test Adapter

TAD Test Adapter

50 pin AMP jack for test adapter access

A50016-G5100-A324-01-7620

157


Id:0900d805800a05de

Figure 31 LI; Variant 1 (Top View)

Plu

g

Fro

nt

Pan

el

1

D6

EPROM

S2

S2

S3

S4

S5

S3

S4

S5

Port 1

Port 2

1 2

1 2

1 2

1 2

S6

S7

S8

S9

158 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Switches Variant 1

Figure 32 LI; Variant 2 (Top View)

Switch Position Function

S2/6 1 outgoing 75 Ω

2 outgoing 120 Ω

S3/7 1 incoming 75 Ω

2 incoming 120 Ω

S4/8 1 outgoing grounded

2 outgoing not grounded

S5/9 1 incoming grounded

2 incoming not grounded

Plu

g

Fro

nt

Pan

el

1

D6

EPROMSubmodule 2

Submodule 1

Submodule 1 and submodule 2 are mounted upside down. The switches face the motherboard.

A50016-G5100-A324-01-7620

159


Id:0900d805800a05de

Figure 33 LI; Variant 2 (Submodule)

Switches Variant 2

* The PCM30 clocks are routed via transformers on the PCM30 module to the TAD plug of the module LI. Two lines for every clock are utilized on the PCM30 module to transfer these clocks (a/b-wires). For each clock only the a-wire is routed to the TAD. The b-wire should be connected to ground via switch S5 on the PCM30 module. Then the signal level is as follows: approx. +/-3V symmetrical to RLICground.

Switch Position Function

S1 1 outgoing 75 Ω

2 outgoing 120 Ω

S2 1 incoming 75 Ω

2 incoming 120 Ω

S3 1 outgoing grounded

2 outgoing not grounded

S4 1 incoming grounded

2 incoming not grounded

S5 * 1 PCM Receive/Transmit-Clock grounded at measure

2 PCM Receive/Transmit-Clock not grounded at measurement output

SwitchesSubmodule 1 / 2

S2

S3

S4

S5

1 2

1 2

1 2

1 2

1 2

S1

160 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


4.14.2 LIPA - Link Interface for Primary Access

Figure 34 LIPA (Front View)

LED

LED red

LED red

LED red

LED green

LED yellow

LED red

Pushbutton

TAD

RY

ACT

1ER-3

RES

RLIC

SPA

2ER-3

LED red

LED red

LED red

LED red

1RAI

1ER-6

2RAI

2ER-6

LED red

LED red

LED red

LED red

3ER-6

3ER-3

4ER-6

4ER-3

LED redLED red 3RAI 4RAI

A50016-G5100-A324-01-7620

161


Id:0900d805800a05de

xRAI Remote Alarm Indication Port x (x=1,2,3,4)

The LED indicates the remote alarms received on port x.

These are:

A-Bit, E-Bit

Yellow Alarm

for PCM30 (from BR 3.7 upwards)

for PCM24

xER-6 Port x (x=1,2,3,4), Bit Error Rate > 10 Exp-6

If the BER is greater than 10 Exp-6 for 1 minute or PCM30 CRC4 errors are detected on port x, this LED is switched on.

It will be switched off if the BER is less than 10 Exp-6 for 1 minute and no CRC4 errors are detected.

CRCCRC errors are:

CRC4

CRC6

for PCM30crc4 format (from BR 3.7 upwards)

for PCM24crc6esf format

xER-3 Port 1, Bit Error Rate > 10 Exp-3

The LED will be switched on if the BER is > 10 Exp-3 for 1 sec or the signal or the frame synchronisation are lost on port 1. It will be switched off after the disturbances are removed.

RY Ready

The Ready LED indicates that the LI has passed the initial module tests and is ready for communication to the connected interface partner (CCTRL or Test PC). It is switched on by the recovery management when the Load-SW is started.

RLIC Reset LI



ACT Active

currently not used

SPA Spare

currently not used

1ER-3 Port 1, Bit Error Rate > 10 Exp-3

The LED will be switched on if the BER is > 10 Exp-3 for 1 sec or the signal or the frame synchronisation are lost on port1. It will be switched off after the disturbances are removed.

Switch

162 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


For line impedance matching there is one DIP switch with 10 contacts for every PCM port on the LIPA (so 4 DIP switches in sum). The following picture and tables show their functions and correct settings.

RES Reset

Resets the link interface.

Test Adapter

TAD Test Adapter


A50016-G5100-A324-01-7620

163


Id:0900d805800a05de

Figure 35 LIPA (Top View)

Plu

g

Fro

nt

Pan

el

EPROM1

D94

S1

S2

S3

S4

110

98

76

54

32

ON

Port 1

Port 2

Port 3

Port 4

164 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Figure 36 Switches for Line Impedance Matching (PCM30 120 Ω)



Switch 1 2 3 4 5 6 7 8 9 10

Position OFF ON OFF OFF OFF OFF OFF OFF OFF OFF

Table 7 Positions of Contacts for PCM30 120 Ω

Switch 1 2 3 4 5 6 7 8 9 10

Position ON OFF ON ON ON OFF OFF ON OFF OFF


Switch 1 2 3 4 5 6 7 8 9 10

Position ON OFF OFF ON OFF ON OFF OFF ON OFF


1 1098765432

ONPCM30120 Ω

1 1098765432

ONPCM3075 Ω

1 1098765432

ONPCM24100 Ω

A50016-G5100-A324-01-7620

165


Id:0900d805800a05de

4.15 MCLK

Figure 39 MCLK (Front View)

LED

LED red

LED red

LED yellow

LED green

LED yellow

LED green

Pushbutton

TAD

RY

ACT

FLOC

RES

RCCK

HMO

PMO

166 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


RY Ready

The Ready LED indicates that the MCLK has passed the initial module tests and is ready for communication to the connected interface partner (CCTRL or Test PC). It is switched on by the recovery management after successful initialization of the O&M subsystems.

ACT Active

This LED signals which MCLK is active. The active one supports the BTSE with the BUS 1/2 clocks and frame signals. In addition the active MCLK transmits the broadcast burst during load phase.

RCCK Reset Common Clock Controller



HMO Holdover Mode

The holdover mode signals that the Abis line frequency is not correct for regulation.

FLOC Frequency Locked

This LED indicates that MCLK accurancy level has reached high, which means that the frequency accuracy is better than +/- 0.05 ppm.

PMO Plesiochronous Mode

This LED indicates that the clock is not phase synchronised to the Abis line. If the Frequency Locked LED is off, the LED indicates that the accuracy level is MEDIUM (accuracy > +/-0.05 ppm).

Note:

If during Load Phase (RY LED is on) the HMO (LED)HMO, PMO AND FLOC LEDs are off, this means that the accuracy level is low.

LED State Matrix

FLOC PMO HMO Meaning

on Accuracy level = MEDIUM

on on Accuracy level = HIGH: not phase synchronised to Abis Line

on Accuracy level = HIGH: phase synchronised to Abis Line

on on on Holdover Mode: Accuracy level = HIGH

on on Holdover Mode: Accuracy level = MEDIUM

A50016-G5100-A324-01-7620

167


Id:0900d805800a05de

Figure 40 MCLK (Top View)

Accuracy level = LOW

LED

RES Reset

Reset the MCLK

Test Adapter

TAD Test Adapter


Plu

g

Fro

nt

Pan

el

1

D89

EPROM

168 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


4.16 OVPT

Figure 41 OVPT with Terminal Block (Top View)

1

23

3

5

7

9

11

13

15

17

19

21

2

24

4

6

8

10

12

14

16

18

20

22

2 PCM4-ULB 1 PCM4-DLB

4 PCM4-ULA 3 PCM4-DLA

6 GND 5 GND



12 GND 11 GND



18 GND 17 GND



24 GND 23 GND

Table 10 Pinning Label of the Terminal Block

A50016-G5100-A324-01-7620

169


Id:0900d805800a05de

Figure 42 OVPT with SMA Connectors (75 Ω)

PCM1-UL

PCM2-UL

PCM3-UL

PCM4-UL

PCM1-DL

PCM2-DL

PCM3-DL

PCM4-DL

PCM1-UL-MON

PCM2-UL-MON

PCM3-UL-MON

PCM4-UL-MON

PCM1-DL-MON

PCM2-DL-MON

PCM3-DL-MON

PCM4-DL-MON

Monitoring Interfaces for PCM lines SMA-male connectors for PCM lines fixing screws

170 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


4.17 PA

Figure 43 PA (Front View)

LED

ALM ALARM

ALM

LED red

TXOUT

TXIN

A50016-G5100-A324-01-7620

171


Id:0900d805800a05de

For normal operation some jumpers on some types of PAs have to be checked. The corresponding figure shows the correct jumper settings.

No jumpers are to be set for PA types that are not illustrated.

Check whether the jumpers are set correctly.

4.17.1 Jumper Settings on GSM 1800 PA

Figure 44 GSM 1800 PA 10W/25W (U434/U466)

This LED indicates a power amplifier alarm.

Connector

TXOUT RF output for connection with HYCOM

TXIN RF input for connection with TPU-RF output

1 2

341

2

1

2

1 2

123

21

1 2

AB

C

D

E

FG

Fro

nt P

anel

Location Connection Effect

A 1-2 normal operation

2-3 microprocessor reset

open not applicable

Table 11 Jumper Settings on GSM 1800 PA 10W/25W (U434/U466)

172 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Figure 45 GSM 1800 PA25D (U519)

B 1-2 normal operation

open microprocessor stopped

C 1-2 normal operation

open HSCX stopped

D 1-2 not applicable

2-3 normal operation

3-4 control loop open

1-4 not applicable

E open test points; to be left open

F open test points; to be left open

G 1-2 normal operation

open only for test of IC9


Table 11 Jumper Settings on GSM 1800 PA 10W/25W (U434/U466) (Cont.)

A B

C

123

1 2

1 2

D

E

TP14 TP15

TP13

TP17

TP19

Fro

nt P

anel

A50016-G5100-A324-01-7620

173


Id:0900d805800a05de

HSCX

4.17.2 Jumper Settings on GSM 900 PA




open not applicable




open HSCX stopped

D TP13-TP14 normal operation

TP14-TP15 test phase only

E open to be left open for normal operation

TP17-TP19 test phase only

Table 12 Jumper Settings on GSM 1800 PA25D (U519)

D

E

1 2

34

AB

C

123

1 2

21

Fro

nt P

anel

174 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Figure 46 GSM 900 PA 25W (U435)




open not applicable




open HSCX stopped

D 1-2 not applicable


3-4 control loop open

1-4 not applicable

E open test points; to be left open

Table 13 Jumper Settings on GSM 900 PA 25W (U435)

123

1 2

21

123

A B

D

C

Fro

nt P

anel

A50016-G5100-A324-01-7620

175


Id:0900d805800a05de

Figure 47 GSM 900 PA 25W/40W (U538/U520)

4.18 RCAPAll external interfaces are available on the rack cabling access panel (RCAP). Check whether all equipped interfaces are connected correctly.

Figure 48 RCAP BS 60 (Top View)




open not applicable




open HSCX stopped

D 1-2 control loop open


Table 14 Jumper Settings on GSM 900 PA 25W/40W (U538/U520)

Earthingscrew

Abis-IF SAL OAL

LMT -48 V DCNT

Serial IF

access to-48 V DC terminal

OVPT

PCM1

+Ue

-Ue

RX0 RX1 RX2 RX3 RX4 RX5

PCM2

PCM3

PCM4

Earth

For pinning of the Abis interface see installation manual (IMN:BTSE).

176 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


4.19 RXAMCO

Figure 49 RXAMCO (Front View)

LED

BIAS This LED indicates that the idle current of both RF amplifier branches is O.K.

Connector

BIAS

LED green

RX

O3

RX

O2

RX

O1

RX

O0

RX

CA

RF

LBIN

RX

IN

A50016-G5100-A324-01-7620

177


Id:0900d805800a05de

RXIN Receive Input

RF-Input

RFLBIN Radio Frequency Loopback Input

RF-Input for loopback

RXCA Receive Cascading Output

RF-Output for further cascading

RXO0 Receive Output 0

RF-Output for connection with module TPU:RF-input







178 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


4.20 RXAMOD

Figure 50 RXAMOD (Bottom View)

RFOUT

RFIN

View of Mast Head Unit MHU from below

Connector

7 / 16” female 50 Ω

RF IN Receive Input

RF Input

RF OUT Receive Output

RF Output for RXMUCO

A50016-G5100-A324-01-7620

179


Id:0900d805800a05de

4.21 RXMUCO

Figure 51 RXMUCO (Front View)

LED


Connector

BIAS

RXIN

RXCA

RXO0

RXO1

RXO2

RXO3

LED green

180 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Figure 52 RXMUCO (Top View)

RXIN Receive Input

RF-Input




RF-Output for connection with module TPU:RF input







Jumpers

Jumpers

A50016-G5100-A324-01-7620

181


Id:0900d805800a05de

4.22 RXMUCO2

Figure 53 RXMUCO 2 (Front View)

The operational settings for the jumpers are shown in the figure above.

The module signals are switched through to the backplane in this setting.

LED

BIAS

LED green

RX

O3

RX

O2

RX

O1

RX

O0

RX

CA

RF

LBIN

RX

IN

182 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de



Connector

RXIN Receive Input

RF-Input

RFLBIN Radio Frequency Loopback Input

RF-Input for loopback











A50016-G5100-A324-01-7620

183


Id:0900d805800a05de

Figure 54 RXMUCO2 (Top View)

Gain Control

A step RF attenuator from 0 dB to 10 dB with 1 dB steps is provided in order to set the required RF level in the RX chain for a given value of the RXAMOD-RXMUCO2 cable attenuation.

Therefore, an external attenuator between RXAMOD and RXMUCO2 is no longer nec-essary.

The RF attenuation can be set by DIP switches placed on the RXMUCO2 (see Figure 54 and Table 15)

The overall value for the RX chain attenuation must be 6 dB. In case of RXMUCO2 cas-cading, the step attenuator of the cascaded RXMUCO2 must be set to the default value of 0 dB.

Jumpers

S1

S2

S3

S4

Attenuation

184 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Attenuation (dB) Switch 1 Switch 2 Switch 3 Switch 4

0 Open Open Open Open

1 Closed Open Open Open

2 Open Closed Open Open

3 Closed Closed Open Open

4 Open Open Closed Open

5 Closed Open Closed Open

6 Open Closed Closed Open

7 Closed Closed Closed Open

8 Open Open Open Closed

9 Closed Open Open Closed

10 Open Closed Open Closed

Table 15 DIP Switch Configuration Versus RF Attenuation

Jumpers

The operational settings for the jumpers are shown in the figure above.

The module signals are switched through to the backplane in this setting.

A50016-G5100-A324-01-7620

185


Id:0900d805800a05de

4.23 TPU

Figure 55 TPU / TPU2 (Front View)

TAD

RX

RXDIV

TX

RD1

SPA

DC5

RES

LED red

LED green

LED green

LED red

LED green

LED green

Pushbutton

RD2

RYD

RYA

RAC LED redLED red RDC

TAD

RX

RXDIV

TX

RD1

SPA

RES

LED red

LED green

LED red

LED green

Pushbutton

RD2

RYD

RAC LED redLED red RDC

TPU TPU2

The module TPU / TPU2 consists of two boards: Transceiver Digital (TRXD) and Transceiver Analog (TRXA).

186 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


Processors on TRXD: Digital Radio Controller (DRC)

Digital Radio Slave 1 (DR1)

Digital Radio Slave 2 (DR2)

Processors on TRXD: Analog Radio Controller (ARC)

LED

RAC Reset Analog Radio Controller (ARC)

The Reset LED indicates the phase from a reset until the finished recovery in the Load-SW. It is switched on by a reset and off by the subsystem RC after successful initialization of the O&M subsystems.


RDC Reset Digital Radio Controller (DRC)

RD1 Reset Digital Radio Slave 1 (DR1)

RD2 Reset Digital Radio Slave 2 (DR2)

The reset LED indicates the phase from a reset until the moment when all O&M subsystems in the Load-SW are initialized.

The LED is switched as follows:

switch on: by a reset

switch off: by the recovery management

Note:

1) An additional task is the signalling of hardware errors detected during the initial (Boot-SW) or extended (Load-SW) hardware tests. The LED flashes with a sequence in which the test number is coded.

2) In case the BUS-1 clock is missing at the initial hardware tests, the RDC LED is switched off 0.25 seconds before a SW-reset is initiated.

SPA Spare

In the start-up phase of the Load-SW, the Spare LED performs an off-on-off transition for 256 UL (up link)-bursts sent to the HT (hardware test) test loop. After unblocking the CP processes, the Spare LED makes an off-on-off transition for 256 UL-bursts sent to CH (Channel Control) on BBSIG.

This LED is also called SW Signal 1 LED.

RYD Ready TRXD (DRC + DR1 + DR2)

A50016-G5100-A324-01-7620

187


Id:0900d805800a05de

The Ready LED TRXD indicates that the TRXD has passed the initial module tests and is ready for the communication to the connected interface partner (CCTRL or Test-PC).

This LED is also called SW Signal 2 LED.

It is switched as follows:

on: by the recovery management after the initial module tests and task initialization in Boot-SW


DC5 DC 5 Volt

This LED signals the presence of the +5 volt power supply from the dedicated power supply unit.

RYA Ready TRXA

The Ready LED indicates that the TRXA has passed the initial module tests and is ready for the communication to the connected interface partner (DRC or Test-PC). It is switched on by the recovery management after successful activation of the load software.

Switch

RES Reset

Resets the TRXD and the TRXA.

Connector

RX Receive Input

RX-Input for connection with module RXMUCO: RF output

TX Transmit Output

RF-Output for connection with module PA: RF input

RXDIV Receive Input Diversity

RX-Input for connection with module RXMUCO: RF output

Used for diversity antenna.

Test Adapter

TAD Test Adapter

188 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d805800a05de


100 pin AMP jack for test adapter for C 40 boards.

A50016-G5100-A324-01-7620

189

MMN:BTSE BS-60 Appendix

Id:0900d8058012be5a

5 Appendix

5.1 HW/SW Compatibility during Download from LMT/BSCThis feature allows a compatibility check of the swLoad and the current HW situation of the BTSE. Thus, it can be avoided that a swLoad which will not run on the specific BTSE is downloaded.

This check is done by means of a compatibility matrix – the Version Attachment Mech-anism (VAM) file which is the second file of the swLoad. The check is carried out when this VAM file is received in the BTSE. If the result is negative, the download of the swImages is stopped.

swLoad: GSM notation for a complete SW package containing all the load SW of a network element.

swImage: GSM notation for the load SW package for a single module inside a network element.

VAM file: represents the context between the swImages and the HW-SW compatibility.

Output Example in Case of a Failed VAM Check (after the BTS received the VAM file):

JOB: <no>

PC Time&Date: <time> <date>

NE Time&Date: <time> <date>

USER NAME: <user>

COMMAND: DNLALLEXE:SRCPATH=”...\...\...\xxxxxxxx.swl”,OVERWRITE=YES;

SW RELEASE: <no>

COMMAND RESULT: OPERATION FAILED

VAM check failed

END OF OUTPUT FOR JOB <no>

JOB: <no>



USER NAME: <user>

SW RELEASE: <no>

190 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be5a

Appendix

COMMAND RESULT: OPERATION COMPLETED

FAILURE EVENT REPORT:

NAME = RACK:0/CCTRL:0

Event Type = Processing Failure Event

Event Time = <time>

Probable Cause = Configuration or Customization Error

Specific Problems = 26676 - Board Type not supported

Severity = Warning

Trend Indication = No Change

Notification Identifier = 48

Proposed Repair Actions_1 = 189 - Check configuration data.

Originator = 3329

Additional Words =

Octets = 01 to 16: H’6264 H’6c78 H’636d H’6d73 H’07ac H’5a01 H’0212 H’3b3b

Octets = 17 to 30: H’c304 H’ffff H’ffff H’ffff H’ffff H’ffff H’ffff

Software Version = <version>


A50016-G5100-A324-01-7620

191


Id:0900d8058012be5a

5.2 State/Status Attributes of BTSE Managed ObjectsThe following state/status attributes are used for BTSE MOs:

State/Status/Attribute

State/Status Explanation

Administrative State (AST)

This state informs whether or not the MO is permitted to provide service.

Locked The related MO is not permitted to provide service, but is addressable for maintenance tasks and fully operable (it can, for example, be tested). This state can be brought about via the LMT “Lock” command. Note: At the BTSE, only HMOs can be locked / unlocked.

Shutting Down The MO is currently shutting down, i.e. ongoing calls are not interrupted, but no new calls are permitted.

This state cannot be brought about via LMT at the BTSE.

Unlocked Service is permitted.

This state can be brought about via the LMT “Unlock” command. Note: At the BTSE, only HMOs can be locked / unlocked.

Operational State (OST)

This state informs whether or not the MO is able to provide service.

Enabled (ena) The MO is able to provide service.

(Exception: the MOs “RACK”, “BTSE” and “ENVABTSE” are always “Enabled”, even if, for example, a service rack is not installed.)

Disabled (dis) The MO is not able to provide service.

Alarm Status (ALS)

This status reports the severity level of active alarms. If more than one alarm is active, the level of the alarm with the highest severity level is reported.

Critical At least one active alarm with severity level “critical” (see 5.3.3).

Major At least one active alarm with severity level “major” (see 5.3.3).

Minor At least one active alarm with severity level “minor” (see 5.3.3).

Cleared No active alarms.

Availability Status This status reports details on AST or OST.

In Test (tst) Intrusive test under progress.

Failed (fail) MO is defective/not operable.

Power Off (pof) The power of the MO is switched off.

Degraded (deg) The service is degraded.

Off Line (ofl) The creation of the MO is in progress.

Dependency (Dep)

The MO cannot operate because of another MO on which it depends.

Not Installed (noi) The MO is not installed.

Table 16 State/Status Attributes of BTSE MOs

192 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be5a

Appendix

Null Value (nul) Value after the creation of an MO (+Disabled/Locked).

Certain processes still in progress (e.g. alignment).

MO TRX: transient failure of a HMO.

Procedural Status (PRS)

This status reports whether or not the MO performs an initialization procedure.

Initialising (ini) Initialization is in progress.

Null Value (nul) No initialization

Standby Status (STS)

This status reports information on redundant MOs.

Null This value is used in combination with OST “Disabled”.

Providing Service This value is used in combination with OST “Enabled”/AST “Unlocked”. The MO provides service.

Cold Standby The MO is able to provide service but it is either not active or it is locked.

State/Status/Attribute

State/Status Explanation

Table 16 State/Status Attributes of BTSE MOs (Cont.)

A50016-G5100-A324-01-7620

193


Id:0900d8058012be5a

5.3 BTSE Alarm InformationOn each BTSE board a local alarm queue for 30 alarms is available. Every 100 ms 1 alarm is sent to the CCTRL. If currently more alarms are generated than 10 per second, the queue gets full and a reset is performed on the board. After the board is restarted, a corresponding Failure Event Report is sent.

The following information is forwarded from the BTSE to the BSC :1. Managed object class2. Managed object instance3. Error information

– probable cause value– event type– perceived severity– trend indication– immediate defense action– threshold information– proposed repair action– error description– additional information

5.3.1 Probable Cause ValueProbable cause of the fault or error. The probable cause is taken out of a predefined set of values, defined for each event type.

5.3.2 Event TypesErrors are classified in the following categories (so called “event types”):

5.3.2.1 Equipment Errors– detected by hardware check or application software

5.3.2.2 Processing Errors– detected by online software checks and audits

5.3.2.3 Communication Errors– detected by protocols

5.3.2.4 Quality of Service ErrorsThey depend on:– traffic overload conditions– excessive instability of the hardware– loss of hardware components

194 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be5a

Appendix

5.3.2.5 Environmental ErrorsThese errors depend on environmental conditions e.g. temperature, door open or smoke.

In general, these faults are signalled to the ALCO module.

5.3.3 Perceived SeverityThe severity level indicates to what extent the functionality of the BTSE is affected. The following values are used:

5.3.3.1 CriticalThe critical severity level indicates that a service affecting condition has occurred and an immediate corrective action is required. Such a severity can be reported, for example, if an equipment related managed object MO breaks down completely.

5.3.3.2 MajorThe major severity level indicates that a service affecting condition has developed and an urgent corrective action is required. Such a severity can be reported for example, if there is a severe degradation in the capability of the equipment related managed object (MO).

5.3.3.3 MinorThe minor severity level indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious (for example, service affecting) fault. Such a severity can be reported, for example, when the detected alarm condition is not currently degrading the capacity of the equipment related managed objects (MO).

5.3.3.4 WarningThe warning severity level indicates the detection of a potential or impending service affecting fault, before any significant effects have been detected. Actions should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a fault causing more severe interference to services.

5.3.4 Trend IndicationThis parameter specifies the current severity trend of the equipment related managed object.

5.3.5 Immediate Defense ActionThe immediate defense action is performed by the BTSE software to try and solve the problem. If there is no corresponding defense action, NA is reported.

A50016-G5100-A324-01-7620

195


Id:0900d8058012be5a

5.3.6 Threshold Information

5.3.7 Proposed Repair ActionSuggested repair actions. Consult also the corresponding user manual.

5.3.8 Error DescriptionDetailed description of the error and its probable cause.

5.3.9 Additional InformationA fixed length buffer contains additional information concerning the detected fault/error. This information depends on the error.

Actual value: lower threshold (if any)

upper threshold (if any)

196 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be5a

Appendix

5.4 Fault Messages

5.4.1 Fault Messages at the Radio Commander

Figure 56 Fault Messages at the Radio Commander

5.4.2 Fault Messages at the LMTJOB: 64PC Time&Date: 08:51:46 2003/11/28NE Time&Date: 08:51:46 2003/11/28USER NAME: LMT_USERSW RELEASE: 01-04-16-01-61-00_03-11-28COMMAND RSULT: OPERATION COMPLETEDFAILURE EVENT REPORT:NAME = RACK:0/FAN:1Event Type = Environmental Failure EventEvent Time = 01/Jan/1990 00:00:00Probable Cause = FAN FailureSpecific Problems = 20542 - FAN unit failedSeverity = MinorTrend Indication = More SevereNotification Identifier = 9Proposed Repair Actions_1 = 181 - Test the addressed module(s)Proposed Repair Actions_2 = 184 - Check the corresponding cables / connections, consult the corresponding maintenance manual for detailsOriginator = 5889Additional Words = Octets 01 to 16: H'6d63 H'6e61 H'6c72 H'6d66 H'0720 H'5a01 H'0100 H'0000Octets 17 to 30: H'ffff H'ffff H'ffff H'ffff H'ffff H'ffff H'ffff

Software Version = 01-01-16-01-59-00_03-11-26END OF OUTPUT FOR JOB 64

Example Fault Messages

A50016-G5100-A324-01-7620

197


Id:0900d8058012be5a

5.5 BTSE Components

5.5.1 BTSE Components OverviewFor a system overview of all BTSE components (modules, frames, racks and managed objects), refer to chapter 4 "Tables, Lists and Figures"

5.5.2 Numbering of BTSE Components

5.5.2.1 General Rules

Relative Numbering

In general, the relative numbering (in the meaning of logical numbering) of the units starts with the figure zero (0). That means the first of a set of devices, modules or racks gets the number 0, the next one the number 1 in sequence, etc.

Slot-ID

For electrical coding each module equipped with a Bus1 Access Circuit (BAC) and a microprocessor reads a slot-ID number, supplied from the backplane by connector pins with a fixed logical level for a particular mounting location.

For the relevant units, the slot-IDs to the corresponding mounting locations see figure Rack BTSE.

Mounting Unit (MUT)

The mounting unit numbers indicate the installation section of the units in the rack (see Fig. 4.4). This number is essential for installation and service purposes.

Mounting Location

A unique number is assigned to every mounting location in which a unit can be inserted, irrespective of whether or not a unit is equipped with a BAC and a microprocessor. This number is required for installation, O&M and service purposes.

5.5.2.2 Specific Rules

Relationship between equipment with relative numbers to cell number.

Please note that there is a fixed assignment of some equipment to a specific cell number. Definition in this way is helpful for the service staff, gives better clarity and smaller logistics for the system cabling.

The following table shows the fixed assignment:

Cell no. Equipment assigned to cell no.

0 ACOM 0

1 ACOM 1

2 ACOM 2

0 FVSWR 0

198 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be5a

Appendix

Rack Numbering

The master rack (0) is the only rack in this release.

Mounting Unit Numbering

The mounting unit number gives the physical position of the relevant unit in the rack.

5.5.3 Remote Inventory DataThe function “Remote Inventory” of the Siemens Basestation System performs elec-tronic, non volatile storing of the complete, individual product identification data (PID) of each inventory object.

Modules that have their inventory data on board are called ob_RIUs (on-board Remote Inventory Units). The PID of these ob_RIUs is automatically loaded to the inventory data file (IDF).

In order to include inventory data of objects without a non volatile storage (e.g. frames, racks, OEM components), the data of these so called nob_RIUs (not on-board Remote Inventory Units) are entered into an inventory data table (IDT) via the LMT and the offline tool “IDF Evolution”, and supplemented with a footer and header to the inventory data file (IDF). This file is stored on the CCTRL and must be updated manually in case of the replacement of a nob_RIU component.

For ob-RIU replacements the file will be updated automatically.

The following list shows all nob_RIU components:

1 FVSWR 1

2 FVSWR 2

0 RXMUCO 0

0 RXMUCO 1 (for diversity)

1 RXMUCO 2


2 RXMUCO 4


n RXMUCO 6 (for cascading of RXMUCO 0, 2 or 4)

n RXMUCO 7 (for cascading of RXMUCO 1, 3 or 5)

Functional Address Range of “n” Functional Address Type

ACK-0/n 0 ACK

DCPA-0/n 0...5 M:DCPA

DCTPU-0/n 0...5 M:DCTPU

DUCOM-0/n 0...2 DUCOM

FAN-0/n 0...2 FAN

Table 17 List of nob_RIUs

A50016-G5100-A324-01-7620

199


Id:0900d8058012be5a

The backup file with the inventory data, which is stored on site, must be updated after exchanging a nob_RIU component.

FIBOX-0/n 0 FILTERBOX

FICOM-0/n 0a, 0b, 1a, 1b, 2a, 2b FICOM

FP-0/n 0 FUSE-PANEL

FRAACOM-0/n 0 F:ACOM

FRABTS6-0/n 0 F:BTS6

FRAFIB-0/n 0 F:FIB60

GPSU-0/n 0...1 M:GPSU

HPDU-0/n 0, 2, 4 HPDU

HYCOM-0/n 0...2 HYCOM

MKOVPT-0/n 0 MK:OVPT

MKRXFIL-0/n 0 MK:RXFIL60

OVPT-0/n 0 OVPT

RBS60-0/n 0 R:BS60

RCBRIDGE-0/n 0 RCBRIDGE

RXAMCO-0/n 0...7 M:RXAMCO

RXAMOD-0/n 0...5 RXAMOD

RXFIL-0/n 0...5 RXFIL

RXMUCO-0/n 0...7 M:RXMUCO

Functional Address Range of “n” Functional Address Type

Table 17 List of nob_RIUs (Cont.)

200 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be5a

Appendix

5.6 Diagnostics / Test

5.6.1 GeneralIn general the diagnosis subsystem is for testing the functionality of BTSE HW resources to detect and localize hardware faults. The verification of the functionality of a new or replaced hardware unit before operation is an especially important feature of diagnosis.

The task of diagnosis is to perform tests for the BTS processor modules, initiated from the LMT.

A successful replacement of analog modules can only be verified by reactivating the BTSE.

5.6.2 Requirements for Starting the BTSE Module TestThe module test is controlled by the LMT. It is therefore necessary that the LMT is plugged in at the plug position and that it is logged in. The principle sequence is as follows:– change the administrative status from unlocked to locked– start the module test– change the administrative status from locked to unlocked

The modules CCTRL, LI, CCLK ALCO and GPSU can not be locked from the LMT in phase 3. Therefore the BTS manager BTSM must be disconnected from the BSC control and the BTSE is to be transferred from phase 3 to phase 2. The administrative state must then be set to “locked” for the module to be tested.

The requisite command sequence is as follows:

5.6.2.1 Lock BTS Site Manager (only relevant for some modules)BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

LOCKREQUEST BTSM

Lockrequest BTSM:NAME=BTSM:<no>

5.6.2.2 Change BTSE from Phase 3 to Phase 2 (only relevant for some modules)BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

DISCBSC BTSM

Discbsc BTSM:NAME=BTSM:<no>

A50016-G5100-A324-01-7620

201


Id:0900d8058012be5a

5.6.2.3 Lock Suspected Module (all modules)BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

<module>

<module>:<no>

LOCK <module>

Lock <module>:NAME=RACK:<no>/<module>:<no>

5.6.2.4 Run Test for Replaced ModuleBSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

<module>

<module>:<no>

PERFTEST <module>

Perfest <module>:NAME=RACK:<no>/<module>:<no>

Explanation of the test parameters:

Refer to the manual “CML:BS-2x/6x”.

System Response

Perftest <module>:NAME=RACK:<no>/<module>:<no>

<no> Command

============================================

JOB: <no>



USER: <user>

COMMAND: Perftest <module>:NAME=RACK:<no>/<module>:<no>

SW RELEASE: <no>

202 A50016-G5100-A324-01-7620

MMN:BTSE BS-60

Id:0900d8058012be5a

Appendix

Example for Test Report

If the test outcome is “fail”, some more information is given, such as “Proposed Repair Action” etc.

5.6.2.5 Unlock Suspected Module (all Modules)BSS


BSS-EQUIPMENT

BTSE

BTSE:<no>

RACK

RACK:<no>

<module>

<module>:<no>

COMMAND RESULT: <command result>

PERFTEST ACK BTSE:

name = BTSETEST:<no>

MOT = RACK:<no>/<module>:<no>

tO = BTSETEST:1


JOB: <no>



USER: <user>

SW RELEASE: <no>

COMMAND RESULT: <command result>

Test Report:

name = BTSETEST:<no>

testOutcome = <test outcome> (see below)

testTermination = Normal

MOT = RACK:<no>/<module>:<no>

A50016-G5100-A324-01-7620

203


Id:0900d8058012be5a

UNLOCK <module>

Unlock <module>:NAME=RACK:<no>/<module>:<no>

5.6.2.6 Change BTSE from Phase 2 to Phase 3 (only relevant for some modules)BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

CONNBSC BTSM

Connbsc BTSM:NAME=BTSM:<no>

5.6.2.7 Unlock BTS Site Manager (only relevant for some modules)BSS


BSS-FUNCTIONAL

BTSM

BTSM:<no>

UNLOCKREQUEST BTSM

Unlockrequest BTSM:NAME=BTSM:<no>

5.6.3 Incompatible Tests for Multiple Test ProcessingThe reason of Multiple Test Processing is to provide more than one test at the same time.

However, only one test of the same processor or nonprocessor module can be executed at the same time. A second test request for the same module will be rejected immediately, but identical tests for other parallel modules are permitted.

Incompatible tests ALCO - nonprocessor Modules:

A nonprocessor module can be tested when the following test conditions are fulfilled:

ALCO: OST=enabled

nonprocessor module: AST=locked, OST= enabled, disabled, disabled&failed.

If the ALCO is in the status disabled failed, disabled failed & test or disabled null no nonprocessor tests are possible.

All test requests will be rejected with PERFORM_TEST_NACK.

Incompatible tests TPU - PA:

In general it is possible to perform PA and TPU tests in parallel.

If the status of the TPU OST=disabled, AVS=failed&test, null, the according PA cannot be tested.

mmnbs60

Documents

line impedance matching

fault clearance guidelines

proposed repair action

nokia siemens networks

fault clearance procedures

message viewer window

local fault clearance

ne btse username