bs20mt

Maintenance

Base Transceiver Station Equipment

MMN:BTSE BS 20

A30808-X3247-M321-1-7620

2 A30808-X3247-M321-1-7620

MMN:BTSE BS 20 MaintenanceBase Transceiver Station Equipment

f Important Notice on Product Safety

DANGER - RISK OF ELECTRICAL SHOCK OR DEATH - FOLLOW ALL INSTALLATION INSTRUCTIONS.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected to the system mustcomply with the applicable safety standards.Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components mayalso have high operating temperatures.Failure to observe and follow all installation and safety instructions can result in serious personal injuryor property damage.Therefore, only trained and qualified personnel may install and maintain the system.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

LEBENSGEFAHR - BEACHTEN SIE ALLE INSTALLATIONSHINWEISE.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Alle an das System angeschlossenenGeräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.In diesen Anlagen stehen die Netzversorgungsleitungen unter gefährlicher Spannung. Einige Komponentenkönnen auch eine hohe Betriebstemperatur aufweisen.Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Körperverletzungen oderSachschäden führen.Deshalb darf nur geschultes und qualifiziertes Personal das System installieren und warten.

Caution:This equipment has been tested and found to comply with EN 301489. Its class of conformity is defined in tableA30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for aClass A digital device, pursuant to part 15 of the FCC Rules.These limits are designed to provide reasonable protection against harmful interference when the equipment isoperated in a commercial environment.This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accor-dance with the relevant standards referenced in the manual “Guide to Documentation”, may cause harmful inter-ference to radio communications.For system installations it is strictly required to choose all installation sites according to national and local require-ments concerning construction rules and static load capacities of buildings and roofs.For all sites, in particular in residential areas it is mandatory to observe all respectively applicable electromagneticfield / force (EMF) limits. Otherwise harmful personal interference is possible.

Trademarks:

All designations used in this document can be trademarks, the use of which by third parties for their own purposescould violate the rights of their owners.

Copyright (C) Siemens AG 2005.

Issued by the Communications GroupHofmannstraße 51D-81359 München

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

A30808-X3247-M321-1-7620 3

MaintenanceBase Transceiver Station Equipment

MMN:BTSE BS 20

Reason for UpdateSummary:

First Edition for New Release BR 8.0

Details:

Chapter / Section Reason for Update

all New Release BR 8.0

Issue HistoryIssue

Number

Date of Issue Reason for Update

1 01/2005 First Edition for New Release BR 8.0

4 A30808-X3247-M321-1-7620


A30808-X3247-M321-1-7620 5


MMN:BTSE BS 20

This document consists of a total of 216 pages. All pages are issue 1.

Contents

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.5.3 Removing and Inserting Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.5.4 Quick Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 Task List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 Fault Clearance Procedures for Modules and Interfaces . . . . . . . . . . . . . . 233.1 Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.2 ACDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3 ALCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4 BBSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.5 BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.6 CCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483.7 CCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.8 DUKIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.9 FAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.10 GPSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.11 HYCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.12 LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.13 LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.14 MCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.15 OVPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.16 PA / DCPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003.17 PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063.18 RXAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1073.19 RXAMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133.20 RXMUCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193.21 TPU / DCTPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253.22 TX/RX Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313.23 Remote Inventory Data Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

4 Tables, Lists and Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414.1 Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424.2 Front View of the BS 20 Rack and Mounting Positions . . . . . . . . . . . . . . 1434.3 General Information on BTSE LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454.4 AC/DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1464.5 ALCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484.6 BBSIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1514.7 CCTRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

6 A30808-X3247-M321-1-7620


4.8 DCPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574.9 DUKIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584.10 FAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1604.11 Fuses BS20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614.12 GPSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1624.13 HYCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1644.14 LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674.14.1 LI – Link Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674.14.2 LIPA – Link Interface for Primary Access. . . . . . . . . . . . . . . . . . . . . . . . . . 1724.15 MCLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1774.16 OVPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1804.17 PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1824.17.1 Jumper Settings on GSM 1800 PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834.17.2 Jumper Settings on GSM 900 PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854.18 RXAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1884.19 RXAMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904.20 RXMUCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914.21 RXMUCO2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1944.22 TPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

5 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2015.1 HW/SW Compatibility during Download from LMT/BSC . . . . . . . . . . . . . . 2015.2 State/Status Attributes of BTSE Managed Objects . . . . . . . . . . . . . . . . . . 2025.3 BTSE Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2035.3.1 Probable Cause Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045.3.2 Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2045.3.3 Severity Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055.3.4 Trend Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055.3.5 Immediate Defense Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055.3.6 Threshold Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2055.3.7 Proposed Repair Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065.3.8 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065.3.9 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065.4 Fault Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2065.4.1 Fault Messages at the Radio Commander. . . . . . . . . . . . . . . . . . . . . . . . . 2065.4.2 Fault Messages at the LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2075.5 BTSE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085.5.1 BTSE Components Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085.5.2 Numbering of BTSE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2085.5.3 Remote Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2095.6 Diagnostics / Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2115.6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2115.6.2 Requirements for Starting the BTSE Module Test . . . . . . . . . . . . . . . . . . . 2115.6.3 Incompatible Tests for Multiple Test Processing . . . . . . . . . . . . . . . . . . . . 213

6 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

A30808-X3247-M321-1-7620 7


MMN:BTSE BS 20

IllustrationsFig. 1.1 Structure of the MMN:BTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Fig. 1.2 Used Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Fig. 1.3 Fault Clearance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Fig. 1.4 ESD Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Fig. 1.5 Module Fastening Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Fig. 1.6 Location of the Plug-in Module Code Keys . . . . . . . . . . . . . . . . . . . . . . 19

Fig. 1.7 Location of the Code Key Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Fig. 4.1 Functional blocks, 2 Carrier BTSE with DUKIT (1 Cell / 2 Carriers) . . 142

Fig. 4.2 2 Carrier BTSE BS 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Fig. 4.3 AC/DC (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Fig. 4.4 ALCO (Front View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Fig. 4.5 ALCO (Top View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Fig. 4.6 BBSIG44 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Fig. 4.7 BBSIG44 (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Fig. 4.8 CCTRL (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Fig. 4.9 CCTRL (Top View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Fig. 4.10 DCPA (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Fig. 4.11 DUKIT20 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Fig. 4.12 FAN (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Fig. 4.13 Fuses BS20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Fig. 4.14 GPSU (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Fig. 4.15 HYCOM two 1-WAY Horizontal (Front View). . . . . . . . . . . . . . . . . . . . 164

Fig. 4.16 HYCOM 2-/4-WAY Horizontal (Front View) . . . . . . . . . . . . . . . . . . . . . 165

Fig. 4.17 LI (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Fig. 4.18 LI; Variant 1 (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Fig. 4.19 LI; Variant 2 (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Fig. 4.20 LI; Variant 2 (Submodule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Fig. 4.21 LIPA (Front View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Fig. 4.22 LIPA (Top View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Fig. 4.23 Switches for Line Impedance Matching (PCM30 120 Ω) . . . . . . . . . . . 176

Fig. 4.24 Switches for Line Impedance Matching (PCM30 75 Ω) . . . . . . . . . . . . 176

Fig. 4.25 Switches for Line Impedance Matching (PCM24 100 Ω) . . . . . . . . . . . 176

Fig. 4.26 MCLK (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Fig. 4.27 MCLK (Top View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Fig. 4.28 OVPT, with Terminal Block (Top View) . . . . . . . . . . . . . . . . . . . . . . . . 180

Fig. 4.29 OVPT with SMA Connectors (75 Ω) . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Fig. 4.30 PA (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Fig. 4.31 GSM 1800 PA 10W/25W (U434/U466) . . . . . . . . . . . . . . . . . . . . . . . . 183

Fig. 4.32 GSM 1800 PA25D (U519) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Fig. 4.33 GSM 900 PA 25W (U435) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Fig. 4.34 GSM 900 PA 25W/40W (U538/U520) . . . . . . . . . . . . . . . . . . . . . . . . . 186

Fig. 4.35 RXAMCO (Front View). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Fig. 4.36 RXAMOD (Bottom View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

8 A30808-X3247-M321-1-7620


Fig. 4.37 RXMUCO (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Fig. 4.38 RXMUCO (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Fig. 4.39 RXMUCO 2 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Fig. 4.40 RXMUCO2 (Top View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Fig. 4.41 TPU / TPU2 (Front View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Fig. 5.1 Fault Messages at the Radio Commander . . . . . . . . . . . . . . . . . . . . . . 206

A30808-X3247-M321-1-7620 9


MMN:BTSE BS 20

TablesTab. 4.1 Mounting Units for the 2 Carrier BTSE Rack R:BS 20. . . . . . . . . . . . . 144

Tab. 4.2 Mounting Position and Simulated Processor IDs (R:BS 20) . . . . . . . . 144

Tab. 4.3 Mounting Position and Slot-ID for the 2 Carrier Rack (R:BS 20) . . . . . 144

Tab. 4.4 Positions of Contacts for PCM30 120 Ω . . . . . . . . . . . . . . . . . . . . . . . 176

Tab. 4.5 Positions of Contacts for PCM30 75 Ω . . . . . . . . . . . . . . . . . . . . . . . . 176

Tab. 4.6 Positions of Contacts for PCM24 100 Ω . . . . . . . . . . . . . . . . . . . . . . . 176

Tab. 4.7 Pinning Label of the Terminal Block . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Tab. 4.8 Jumper Settings on GSM 1800 PA 10W/25W (U434/U466) . . . . . . . . 184

Tab. 4.9 Jumper Settings on GSM 1800 PA25D (U519) . . . . . . . . . . . . . . . . . . 185

Tab. 4.10 Jumper Settings on GSM 900 PA 25W (U435) . . . . . . . . . . . . . . . . . . 186

Tab. 4.11 Jumper Settings on GSM 900 PA 25W/40W (U538/U520) . . . . . . . . . 187

Tab. 4.12 Dip Switches Configuration Versus RF Attenuation. . . . . . . . . . . . . . . 196

Tab. 5.1 State/Status Attributes of BTSE MOs . . . . . . . . . . . . . . . . . . . . . . . . . 202

Tab. 5.2 List of nob_RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

10 A30808-X3247-M321-1-7620


A30808-X3247-M321-1-7620 11


MMN:BTSE BS 20

1 Introduction

1.1 Structure of the Maintenance Manual

The following diagram gives an overview of the structure of this manual and the purposeof its chapters.

Fig. 1.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 becarried out

Chapter 6 Abbreviations

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

Chapter 4

Fault Clearance Procedures for Modulesand Interfaces– Fault clearance procedures (modules/in-terfaces/HMOs in alphabetical order)– Concluding procedure “Remote InventoryData 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 workefficient and safe)

(Main Part for Fault Clearance Tasks)

(Reference Chapter)

(Reference Chapter)

(General Maintenance)

(Reference Chapter)

Chapter 4

12 A30808-X3247-M321-1-7620


1.2 Used Symbols

The following symbols are used in this manual:

Fig. 1.2 Used Symbols

Reference to another procedure step

Symbol Meaning

ESD (Electrostatically Sensitive Devices) precautions to be taken

Note; important 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.

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

A30808-X3247-M321-1-7620 13


MMN:BTSE BS 20

1.3 Fault Clearance Principle

The high system functionality of the Siemens base station system is achieved by meansof system-integrated routine tests. These routine tests continually check the correctfunctioning of the base station subsystems including the BTSEs.

The fault clearance procedures in this manual are based on these routine tests. In mostcases, the results of these routine tests are sufficient to localize the fault and clear it im-mediately at the BTSE.

The modular design of the BTSE allows you to clear a large percentage of faults in thesystem 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 tohigh operational efficiency.

14 A30808-X3247-M321-1-7620


1.4 Fault Clearance Guidelines

The following diagram gives an overview of the fault clearance procedure (detailed de-scription below):

Fig. 1.3 Fault Clearance Overview

7.

YN

Y

6.AnotherProbableCause?

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

Fault and Test Man-agement at theOMC via Radio

Commander

N

1. System Integrated Routine Test Detects a Fault

3.Local Fault

Clearance at theBTSE Neces-

sary?

YN

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

Local FaultClearance

at the BTSE

4. Fault Clearance Proce-dure for the Suspected

Module or Interface

8. CallTAC

5.Fault

ClearanceSuccess-

ful?

Content of this Manual

A30808-X3247-M321-1-7620 15


MMN:BTSE BS 20

Fault Clearance Guidelines

(The numbering refers to the above diagram.)

1. The system integrated routine test detects a fault.

2. A fault message is displayed at the Radio Commander.

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 Ra-dio Commander documentation).

4. Interpret the fault message and go to the fault clearance procedure of the suspectedmodule 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 ifthey may 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 wassuccessful:

– 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, checkwhether there is another probable cause.

7. If there is another probable cause, reinsert the recently replaced original module andgo to the corresponding fault clearance procedure for the next suspected module orinterface.

8. It should be possible to clear most faults that may occur in the BTSE by following thefault clearance procedures described in this manual. However, if the fault should stillexist 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

iFor the local fault clearance at the BTSE :Make sure that all spare parts that might be required to clear the fault are availableat the site. Note that sometimes more than one module may be suspected of beingdefective. This is particularly important if the failure is located in the TX/RX path(see 3.22 "TX/RX Path").For general module replacement instructions see also 1.5 "Module ReplacementInstructions".

16 A30808-X3247-M321-1-7620


1.5 Module Replacement Instructions

1.5.1 ESD Precautions

Fig. 1.4 ESD Symbol

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

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

1.5.2 Avoiding the Loss of Calls

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

1. Find out the corresponding TRX:To find out which TRX is related to the module, perform the following LMT command:MANAGED-ELEMENTBSS-EQUIPMENTBTSERACK<Module>GET <Module>NAME=RACK:<no>/<Module>:<no>REQATTL=RELFUNCOBJGet <Module>:Name=BTSE:<no>/<Module>:<no>,REQATTL=RELFUNCOBJIn the system response, the corresponding TRX is listed as related Functional Ob-ject: 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:MANAGED-ELEMENTBSS-EQUIPMENTBSS-FUNCTIONAL

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

A30808-X3247-M321-1-7620 17


MMN:BTSE BS 20

BTSMBTSTRXGET TRXNAME=BTS:<no>/TRX:<no>REQATTL=OST/ASTGet TRX:Name=BTS:<no>/TRX:<no>,REQATTL=<AST>&<OST>The states of the TRX are listed in the system response.

3. If the states of the TRX are either administrativeState = Unlocked / operational-State = 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 afew 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 afew minutes and check the state of the TRX again. As soon as the TRX is locked,you can start with your maintenance task.

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

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

18 A30808-X3247-M321-1-7620


1.5.3 Removing and Inserting Modules

There are two variants for fastening modules in the subracks.

Some modules, e.g. the ALCO, BBSIG, CCTRL, MCLK, and LI are equipped with a levermechanism at their front panel. For removing or inserting these modules, they can befastened / unfastened by swivelling the levers at the top and bottom edges of the mod-ule.

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

Fig. 1.5 Module Fastening Variants

The module RXAMOD located at the MHU (mast head unit) must be replaced completewith 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).

lever mechanism in open position

push together

lever mechanism in locked position torx screw

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

iIt must be ensured that the modules are only replaced by modules with the same (or acompatible) HW and SW functional status!Modules with switches or jumpers (module ALCO, LI and RXMUCO) must be comparedwith the removed module for safety reasons.The modules should be removed and inserted as fast as possible, in order to preventreading in false module addresses from the CAN BUS.

A30808-X3247-M321-1-7620 19


MMN:BTSE BS 20

Handling Modules with Code Keys

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

Fig. 1.6 Location of the Plug-in Module Code Keys

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

In general, after having removed a module from a base station frame, please make surethat 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 thebackplane.

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),

Fig. 1.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 thebackplane.

When inserting a module, do not use excessive pressure.

Code Keys

2

code key number

20 A30808-X3247-M321-1-7620


1.5.4 Quick Module Replacement

In 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 lockedand, after their replacement, tested and unlocked via an LMT.

For the quick replacement procedure, an LMT is not required. The module can be re-placed directly and is put into service automatically after a successful replacement (Au-torecovery).Precondition for the quick replacement procedure: the attribute Autorecovery (EAU-TOREC) is enabled.

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

MANAGED-ELEMENTBSS-EQUIPMENTBTSEGET BTSE NOSWLREQATTLEAUTOREC

Get BTSE NOSWL:NAME=BTSE:<no>,REQATTL=EAUTOREC

To set this attribute, refer to ITMN:BTSE BS 20, chapter “Setting Attributes for the BT-SE”.

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

– Connect all semi-rigid cables.

– Fully insert the module.

iQuick Replacement Procedure and Semi-Rigid CablingModules with semi-rigid cabling require a special handling!It is important that all semi-rigid cables are connected before the module is fully insert-ed. Otherwise, the module is not put into service. The reason for this is that the auto-matic recovery process starts as soon as the module comes into contact with thebackplane connectors. Semi-rigid cables that are not connected during this processcause errors which will prevent the autorecovery of the module.

A30808-X3247-M321-1-7620 21


MMN:BTSE BS 20

2 Task List

Not relevant.

22 A30808-X3247-M321-1-7620


A30808-X3247-M321-1-7620 23


MMN:BTSE BS 20

3 Fault Clearance Procedures for Modules andInterfaces

24 A30808-X3247-M321-1-7620


3.1 Abis

1 Open the BTSE Door

Open the BTSE Door.

2 Check the LEDs on the LI/LIPA and MCLK

You can recognize an Abis alarm by the red LEDs “xRAI” and “xER-3” on theLI/LIPA, as well as “HMO” on the MCLK.If one of these LEDs is on, an Abis problem is indicated.

3 Optional: Check the Active Alarms with the LMT

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

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEGETACTIVEALARMS BTSE

All active alarms will be listed in the Message Browser Window.

Typical failure event report for an Abis cable problem:

NAME = BPORT:0Event Type = Communication Failure EventEvent Time = 26/Jan/2001 00:13:03Probable Cause = Transmission ErrorSpecific Problems = 10270 - Loss of signalSeverity = Major

iIn some cases, Abis alarms originate from loose or damaged PCM cables on the BTSEAbis Interface (OVPT) or in the corresponding distribution frame (NTPM, BSC connec-tor, customer terminal equipment) in BSC direction. Therefore, the relevant cables mustbe checked first, according to the following procedure.

Typical Abis alarms concerning cable problems may be indicated by the alarm messageBPORT – Loss of signal.

iBPORT is the logical object that is related to the Abis interface (OVPT).The Abis lines are also referred to as PCM lines.

A30808-X3247-M321-1-7620 25


MMN:BTSE BS 20

4 Physical Check of the Abis Cable Connections (OVPT)

Are the PCM lines fastened correctly– in the terminal block of the OVPT and– in BSC direction (NTPM, BSC connector, customer terminal equipment)? Y h...7

N h...5

For further information on the Abis interface on the OVPT, please refer to the In-stallation Manual. ...... (see IMN:BT-

SE BS 20)

5 Fasten the 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? Y h...11N h...7

It may take up to 10 minutes until the LED “HMO” on the MCLK goes off.

7 Visual Check of the Abis Lines (OVPT)

Write down the cable colors and their corresponding terminals before discon-necting any cables.

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

Do you see a broken or corroded cable, or an insulation that interrupts the con-tact? Y h...8

N h...10

8 Repair Bad 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? Y h...11N h...10

It may take up to 10 minutes until the LED “HMO” on the MCLK goes off.

10 Replace OVPT

Refer to the fault clearance procedure for the OVPT. h...Procedure: 3.15

26 A30808-X3247-M321-1-7620


11 Prepare End of Fault Clearance

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

END

A30808-X3247-M321-1-7620 27


MMN:BTSE BS 20

3.2 ACDC

1 Interpret the Fault Message ...... (see 5.5.2)

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

– Module(s) ??– BTS-no ??– Rack-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. ...... (see Fig. 4.2)

Start LOGON-Procedure.

3 Lock Suspected Module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACDCLOCK ACDC

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

28 A30808-X3247-M321-1-7620


4 System Response

Several CHANGED STATE EVENT REPORTs will follow. They can be examinedin the LMT Message Browser Window.

5 Module Replacement

1. Check fuse first, refer to 4.4 "AC/DC".

2. Disconnect all cables.

3. Pull affected module.

4. Select a module with a functional HW / SW state compatible to that of themodule which is being replaced.

5. Insert prepared module.

6. Connect all cables.

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

<date> <time> Command

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

JOB: <no>

PC Time&Date: <time> <date>

NE Time&Date: <time> <date>

USER: <user>

COMMAND: Lock ACDC:NAME=RACK:<no>/ACDC:<no>

SW RELEASE: <no>

COMMAND RESULT: <command result>

LOCK/UNLOCK ACDC ACK:

name = RACK:<no>/ACDC:<no>

administrativeState = Locked

END OF OUTPUT FOR JOB <no>

!ESD precautions must be taken when pulling and inserting a module.Refer to 1.5.1 "ESD Precautions".

A30808-X3247-M321-1-7620 29


MMN:BTSE BS 20

6 Run Test for Replaced Module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACDCPERFTEST ACDC

PERFTEST ACDC:NAME=RACK:<no>/ACDC:<no> ;

7 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:

name = BTSETEST:<no>

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

tO = BTSETEST:1


30 A30808-X3247-M321-1-7620


8 Test Report

The test report can be examined in the LMT Message Browser Window.Note the test outcome.

If the test outcome is "fail", some more information is given, such as "ProposedRepair Action" etc.

9 Unlock Suspected Module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACDCUNLOCK ACDC

UNLOCK ACDC:NAME=RACK:<no>/ACDC:<no> ;

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:


testOutcome = <passed or fail>

testTermination = Normal

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

executedPhases

phaseId = PreliminaryTestsACDC

phaseId = CheckAlarmStatusACDC

phaseId = EndTestACDC


A30808-X3247-M321-1-7620 31


MMN:BTSE BS 20

10 System Response


11 Get Active Alarms


GETACTIVEALARMS BTSE:NAME=RACK:<no>

The active alarms will be listed in the LMT Message Browser Window.

12 Result of Module Replacement

The module replacement was successful if:– the test outcome was "pass"and if– there are no relevant active alarmsand if– there are no red LEDs, except R1/RE on ALCO.

Was the module replacement successful? Y h...17N h...13

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


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

JOB: <no>



USER: <user>

COMMAND: Unlock ACDC:NAME=RACK:<no>/ACDC:<no>

SW RELEASE: <no>


LOCK/UNLOCK ACDC ACK:

name = RACK:<no>/ACDC:<no>

administrativeState = Unlocked


32 A30808-X3247-M321-1-7620


13 Reinsert the Replaced Module

It is probable that the original module did not cause the failure and was not de-fective. Therefore, the currently inserted module must be removed and the origi-nal module must be reinserted.

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

14 Another Probable Cause?

Is there another suspected module/interface in the fault message? Y h...15N h...16

15 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

16 Call TAC h...19

17 Mark the Replaced Module as Defective

18 Update the Remote Inventory Data

Update the remote inventory data and renew the backup copy of the inventorydata table.For updating the remote inventory data and renewing the backup copy, go toprocedure “Remote Inventory Data Update” in this manual.

h...Procedure: 3.23


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

Close the BTSE door.

END

A30808-X3247-M321-1-7620 33


MMN:BTSE BS 20

3.3 ALCO








3 Lock BTS Site Manager

b MANAGED-ELEMENTBSS-FUNCTIONALBTSMLOCKREQUEST BTSMNAME=BTSM:0

LOCKREQUEST BTSM:NAME=BTSM:0;

4 System Response

iModule ALCO may be removed while power is on!

Lockrequest BTSM:NAME=RACK:<no>/BTSM:<no>


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

JOB: <no>



USER: <user>

COMMAND: Lockrequest BTSM:NAME=RACK:<no>/BTSM:<no>

SW RELEASE: <no>


LOCK BTSM ACK:

34 A30808-X3247-M321-1-7620


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

b MANAGED-ELEMENTBSS-FUNCTIONALBTSMDISCBSC BTSMNAME=BTSM:0

DISCBSC BTSM:NAME=BTSM:0;

6 System Response

Several CHANGED STATE EVENT REPORTs will appear. They can be exam-ined in the LMT Message Browser window.

7 Logon

b LogonUserID: <user>Password: <password>Connect

The BTSE is now in phase 2.


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKALCOLOCK ALCO

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

name = BTSM:<no>


A30808-X3247-M321-1-7620 35


MMN:BTSE BS 20

9 System Response







b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKALCOPERFTEST ALCO

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

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK ALCO ACK:

name = RACK:<no>/ALCO:<no>




36 A30808-X3247-M321-1-7620


12 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


A30808-X3247-M321-1-7620 37


MMN:BTSE BS 20

13 Test Report


If the test outcome was "fail", some more information will follow, such as "Pro-posed Repair Action" etc.


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKALCOUNLOCK ALCO

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:




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

executedPhases

phaseId = PreliminaryTestsALCO

phaseId = SerialEepromTestAlco

phaseId = EndTestALCO


38 A30808-X3247-M321-1-7620


15 System Response


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

b MANAGED-ELEMENTBSS-FUNCTIONALBTSMCONNBSC BTSMNAME=BTSM:0

CONNBSC BTSM:NAME=BTSM:0;

17 System Response


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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK ALCO ACK:

name = RACK:<no>/ALCO:<no>



A30808-X3247-M321-1-7620 39


MMN:BTSE BS 20

18 Logon


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










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



Check also modules LI, OVPT, NTPM or WAVE and connection to BSC

– for NTPM or WAVE see manuals of OEM

– for BSC refer to MMN:BSC

40 A30808-X3247-M321-1-7620




24 Call TAC h...26





END

A30808-X3247-M321-1-7620 41


MMN:BTSE BS 20

3.4 BBSIG





2 Autorecovery (EAUTOREC) Enabled?

Is the attribute Autorecovery (EAUTOREC) enabled? Y h...3N h...5

If you have no information on this attribute, continue with “N”.

3 Quick Module Replacement





All LEDs have to signal normal operation. No red LEDs may be on exceptR1/RE on ALCO.Call OMC to make sure that the BTSE has gone back to normal operation.


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

iModule BBSIG may be removed while power is on!


42 A30808-X3247-M321-1-7620



Plug the LMT cable into the corresponding socket. ......(see Fig. 4.2)



b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKBBSIGLOCK BBSIG

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

7 System Response



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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK BBSIG ACK:

name = RACK:<no>/BBSIG:<no>




A30808-X3247-M321-1-7620 43


MMN:BTSE BS 20





b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKBBSIGPERFTEST BBSIG

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

10 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


44 A30808-X3247-M321-1-7620


11 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKBBSIGUNLOCK BBSIG

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:




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

executedPhases

phaseId = PreliminaryTestsBBSIG

phaseId = BootEepromTestBbsig

phaseId = SerialEepromTestBbsig

phaseId = Bus2ClockControlTestBbsig

phaseId = EndTestBbsig


A30808-X3247-M321-1-7620 45


MMN:BTSE BS 20

13 System Response









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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK BBSIG ACK:

name = RACK:<no>/BBSIG:<no>



46 A30808-X3247-M321-1-7620




Go back to the beginning of this procedure to reinsert the original module intothe BTSE. After having reinserted (without AUTORECOVERY: tested/unlocked)the original module, continue with the now following step.





19 Call TAC h...21



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


END

A30808-X3247-M321-1-7620 47


MMN:BTSE BS 20

3.5 BPORT

BPORT is the managed object which represents the BTSE Abis ports.

1 Go to Procedure “Abis”

Go to procedure “Abis”. h...Procedure: 3.1

END

48 A30808-X3247-M321-1-7620


3.6 CCLK

1 Interpret the Fault Message ......(see 5.5.2)










3. Insert new module (the insertion starts the boot process).

– Wait a few minutes until the boot process is finished.

4 Get Active Alarms




iModule MCLK may be removed while power is on!

iIn commands the module is called CCLK.


A30808-X3247-M321-1-7620 49


MMN:BTSE BS 20


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




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





9 Call TAC h...11





END

50 A30808-X3247-M321-1-7620


3.7 CCTRL

The reconfiguration of the BTSE can be done via the Backup BTS tool, if a backup copyof the site specific configuration is available.To rebuild the inventory data, a backup IDF-file is usually available. Otherwise, the datacan be extracted from the BSC-IDF.











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 (andyellow) LEDs go on – exception can be R1 LED on ALCO.

– Do not login in Phase 1 and 2!

iModule CCTRL may be removed while power is on!

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


A30808-X3247-M321-1-7620 51


MMN:BTSE BS 20

4 System Response

Several CHANGED STATE EVENT REPORTs will follow.

5 Software Download and Activation

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

i ... ITMN:BTSE BS20

6 Reconfiguration of the BTS via Backup Copy or Installation Procedure?

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

Is a backup copy of the former configuration available? Y h...7N h...10

7 Copy the Backup Script Files to the BKBTS\BTSONE Subdirectory ...... (seeITMN:BTSE BS20)

b Copy all backup script files “script*.lmt” from the storage media into the followingdirectory of the LMT PC:

[Drive]:\[LMT_Root]\BKBTS\BTSONE.

8 Start the Backup BTS Tool

b Start the Backup BTS Tool via the WINDOWS Start menu (“Start” -> “Programs”-> “LMT...” -> “Backup BTS”),orclick on the “Backup BTS” icon in the “LMT Control Center” window.

The “BACKUPBTS” window opens.

9 Restore the HW Configuration

b Click on the button “Restore HW Configuration”.

After the HW configuration is restored, the following message is displayed:

THE SCRIPT WAS DONE SUCCESSFULLY h...11

10 Start Installation Procedure

Refer to ITMN:BTSE BS 20, chapter “Procedures”. i ... ITMN:BTSE BS20

52 A30808-X3247-M321-1-7620



Is the result for all modules as follows?

CHANGED STATE EVENT REPORT

NAME = RACK:<no>/<module>:<no>Operational State: ENABLEDNotification Identifier = <no>

End of Job Y h...16N h...12


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

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





15 Call TAC h...31


17 Remote Inventory Data Restore via IDF-File, BSC-IDF or Manually?

Usually, a backup of the IDF-File is available on site. If not, the data can beextracted from the BSC-IDF or must be entered again manually.

Is a backup copy of the former BTSE IDF-file available? Y h...21N h...18

A30808-X3247-M321-1-7620 53


MMN:BTSE BS 20

18 Backup Copy of the BSC IDF-File

Is a backup copy of the BSC IDF-file available? Y h...20N h...19

19 Create all nob_RIUs Manually

For the creation of the inventory data for all nob_RIUs refer to the ITMN:BTSEBS 20, chapter “Remote Inventory”.

i ... ITMN:BTSE BS20

Continue with the download and backup storage of the inventory data. h...24

20 Extract BTSE Data from BSC-IDF

The data for the relevant BTSE must be separated from the inventory datastored as central IDT in the BSC or its backup file of the BSC area where theBTSE belongs to.

Call TAC to get the data of the BTSE provided in an appropriate IDF-file. h...31

54 A30808-X3247-M321-1-7620


21 Start IDF Editor

b Start the IDF editor:

– Start the IDF editor via the WINDOWS Start menu (“Start” -> “Programs” ->“LMT...” -> “IDF Editor”),or

– click on the “IDF” icon on the “LMT Control Center” window.

The “IDF Editor” window opens:

22 Copy the IDF-File to the LMT

b Copy the IDF-file from the storage media to the harddisk of the LMT PC.

23 Open IDF-File

b Open the IDF-file:

– Select “Open” in the “File” menu.

– Enter path and file name of the IDF-file or select them from the list in theappearing window; e.g.: <C:...\LMT<version>\Idf\*.idf>.

– Double-click on the file name or select the file name and click on the “Open”button.

A30808-X3247-M321-1-7620 55


MMN:BTSE BS 20

24 Export Nob_Riu part for Download to the BTSE

Only the nob_RIU-part has to be exported for downloading into the BTSE.

b Export the nob_RIU-part:

– Select “NOB” in the “Export” menu.

The file name is automatically composed of the “SalesUniqueName” with theextension “.nob ” .

– Click on the “Save” button.

A question window opens: Create Nob RIUs file for Download?

– Click on the “Yes” button.

A window opens which displays the destination path of the NOB-file, forexample:C:...\LMT<version>\IDF\Dnload\BTS_NRIU.nob

– Click on the “OK” button.

25 Download nob_RIU File to the BTSE

Change to the LMT application!

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEREMINVDNLIDF REMINVSRCDIR=<source directory>

SRCDIR: enter the source directory in which the exported NOB-file was saved,for example C:...\LMT<version>\Idf\Dnload.

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

26 System Response


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

JOB: <no>

PC Time&Date: <time>/<date>

COMMAND: DNLIDF REMINV:NAME=REMINV:<no>,SRCDIR=”<for example:C:...\LMT<ver-sion>\Idf\Dnload”:

56 A30808-X3247-M321-1-7620


27 Upload IDT-File from BTSE

The remote inventory data of the ob-RIUs must be loaded to the LMT PC inorder to create an up-to-date IDF file for backup.

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEREMINVUPLLIDF REMINV(DESTDIR=<path>)(FILE=<file name>)OVERWRITE=YES

The values DESTDIR and FILE are optional. If no special path or file name isentered, the file is uploaded to the default directory of the IDF editor.If the value OVERWRITE=YES is selected, a former version of an uploaded IDT-file will be overwritten.

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

COMMAND RESULT: OPERATION COMPLETED

Downloading File <for example: BTS_NRIU>:

100% of packets transferred



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

JOB: <no>


COMMAND: DNLIDF REMINV:NAME=REMINV:<no>,SRCDIR=”<for example: C:...\LMT<ver-sion>\Idf\Dnload”:


Download End: File <for example: BTS_NRIU> Transfer Completed


A30808-X3247-M321-1-7620 57


MMN:BTSE BS 20

28 System Response


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

JOB: <no>


COMMAND: UPLLIDF REMINV:NAME=REMINV:<no>,OVERWRITE=Yes;


Uploading File <for example: BTSE.IDT>:

To: <for example: BTSE.IDT>

On Directory:<for example:...\Idf\Upload>



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

JOB: <no>




Uploading End: File <for example: BTSE.IDT> Transfer Completed


58 A30808-X3247-M321-1-7620


29 Open the Uploaded File

b Open the uploaded file:

– Change back to the IDF Editor application.


– Select the uploaded file from the list in the appearing window; e.g.:<C:...\LMT<version>\Idf\Upload\BTSE.idt”>.

– Click on the “Open” button.

30 Export File for Backup

b Export the IDF-file:

– Select “IDF” in the “Export” menu.

– Select the destination path in the appearing window, preferably “A:\”.

The file name is automatically composed of the “SalesUniqueName” with theextension “.idf ” .


– Put the disk with the backup file of the inventory data to the site specificdocumentation.




END

A30808-X3247-M321-1-7620 59


MMN:BTSE BS 20

3.8 DUKIT





2 Interpret the Alarm Type

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

– VSWR Alarm– Cable Problem– Transmitter Problem– Receiver Failure/Problem– Transceiver Problem Y h...Procedure:

3.22

N h...3




iDUKIT is one of the 2 possible HW modules (DUKIT, HYCOM) for the transceiving andcombining part of the BTSE. Both modules are managed via the managed object ACOMin the LMT.

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

iThe module ALCO must be inserted and fault free!

iThe module DUKIT may be removed while power is on!

60 A30808-X3247-M321-1-7620



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

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


4. Select a module with a functional HW/SW state compatible to that of themodule which is being replaced.

5. Partly insert the prepared module. Make sure that it does not yet come intocontact with the back plane connectors by leaving about 2 cm distance be-tween module and back plane.

6. Connect the cables in the following order:– antenna cables– semi-rigid cables– signalling cable.

7. Fully insert the prepared module.

8. Check the Voltage Standing Wave Ratio VSWR!Refer to chapter 4.9 "DUKIT" or 4.13 "HYCOM".

9. The alarm LED must not go on after module insertion!If an LED goes on, check the antenna connection.








iIf there was contact beteen the module and the back plane connectors beforeall semi-rigid cables were connected, pull the module again about 2 cm outof the rack until it is no longer connected to the back plane.

A30808-X3247-M321-1-7620 61


MMN:BTSE BS 20


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACOMLOCK ACOM

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

8 System Response



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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK ACOM ACK:

name = RACK:<no>/ACOM:<no>




62 A30808-X3247-M321-1-7620


1. Disconnect all semi-rigid cables, antenna and signalling cable.




5. Connect all semi rigid cables, antenna and signalling cable.




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACOMPERFTEST ACOM

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

11 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


A30808-X3247-M321-1-7620 63


MMN:BTSE BS 20

12 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACOMUNLOCK ACOM

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:





executedPhases

phaseId = PreliminaryTestsACOM

phaseId = CheckAlarmStatusACOM

phaseId = EndTestACOM


64 A30808-X3247-M321-1-7620


14 System Response









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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>






A30808-X3247-M321-1-7620 65


MMN:BTSE BS 20






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



20 Call TAC h...22





END

66 A30808-X3247-M321-1-7620


3.9 FAN









b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKFANLOCK 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.

A30808-X3247-M321-1-7620 67


MMN:BTSE BS 20

4 System Response



1. Switch power off for the suspected FAN, refer to chapter 4.10 "FAN".

2. Pull affected module FAN.

3. Insert new module.

4. Switch power on for the suspected FAN.


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKFANPERFTEST FAN

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

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK FAN ACK:

name = RACK:<no>/FAN:<no>




68 A30808-X3247-M321-1-7620


7 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


A30808-X3247-M321-1-7620 69


MMN:BTSE BS 20

8 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKFANUNLOCK FAN

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:




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

executedPhases

phaseId = PreliminaryTestsFAN

phaseId = CheckAlarmStatusFAN

phaseId = EndTestFAN


70 A30808-X3247-M321-1-7620


10 System Response







The module replacement was successful if:– the test outcome was "pass"and if– there are no relevant active alarms


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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK FAN ACK:

name = RACK:<no>/FAN:<no>



A30808-X3247-M321-1-7620 71


MMN:BTSE BS 20



Go back to the beginning of this procedure to reinsert the original module intothe BTSE. After having reinserted/tested/unlocked the original module, continuewith the now following step.





16 Call TAC h...19




h...Procedure: 3.23




END

72 A30808-X3247-M321-1-7620


3.10 GPSU











3. 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 yel-low) LEDs go on – exception can be R1 LED on ALCO.

– Do not login in Phase 1 and 2!

4 System Response

Several CHANGED STATE EVENT REPORTs will appear.

The BTSE is in phase 3 after approximately 10 minutes.

iThe GPSU may be used in redundant configuration. Both modules are handled asGPSU_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 theavailability status of all TRXs to “degraded”, but it does not restrict their functionality.

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


A30808-X3247-M321-1-7620 73


MMN:BTSE BS 20

5 Get Active Alarms





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









10 Call TAC h...13


74 A30808-X3247-M321-1-7620




h...Procedure: 3.23




END

A30808-X3247-M321-1-7620 75


MMN:BTSE BS 20

3.11 HYCOM








3.22

N h...3




iHYCOM is one of the 2 possible HW modules (DUKIT, HYCOM) for the transceiving andcombining part of the BTSE. Both modules are managed via the managed object ACOMin the LMT.


iThe module ALCO must be inserted and fault free!

iThe module HYCOM may be removed while power is on!

76 A30808-X3247-M321-1-7620



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

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



5. Partly insert the prepared module. Make sure that it does not yet come intocontact with the back plane connectors by leaving about 2 cm distance be-tween module and back plane.

6. Connect the cables in the following order:– antenna cables– semi-rigid cables– signalling cable.

7. Fully insert the prepared module.










iIf there was contact beteen the module and the back plane connectors beforeall semi-rigid cables were connected, pull the module again about 2 cm outof the rack until it is no longer connected to the back plane.

A30808-X3247-M321-1-7620 77


MMN:BTSE BS 20


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACOMLOCK ACOM

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

8 System Response



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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>







78 A30808-X3247-M321-1-7620


1. Disconnect all semi-rigid cables, antenna and signalling cable.




5. Connect all semi rigid cables , antenna and signalling cable.




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACOMPERFTEST ACOM

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

11 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:



tO = BTSETEST:1


A30808-X3247-M321-1-7620 79


MMN:BTSE BS 20

12 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKACOMUNLOCK ACOM

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:





executedPhases

phaseId = PreliminaryTestsACOM

phaseId = CheckAlarmStatusACOM

phaseId = EndTestACOM


80 A30808-X3247-M321-1-7620


14 System Response









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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>






A30808-X3247-M321-1-7620 81


MMN:BTSE BS 20









20 Call TAC h...22





END

82 A30808-X3247-M321-1-7620


3.12 LAPDLE



END

A30808-X3247-M321-1-7620 83


MMN:BTSE BS 20

3.13 LI









b MANAGED-ELEMENTBSS-FUNCTIONALBTSMLOCKREQUEST BTSMNAME=BTSM:0


4 System Response

iModule LI may be removed while power is on!

iWhen the module LI is plugged off, the PCM-line is interrupted also for all subsequentBTSEs in case of multidrop configuration.Since a defective module LI is still able to switch the PCM-line to all subsequentBTSEs in case of multidrop configuration, the module LI may be pulled only for modulereplacement!

iIf a failure of the module LI is reported, the OVPT has to be considered as a possiblefailure cause as well.



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

JOB: <no>


84 A30808-X3247-M321-1-7620



b MANAGED-ELEMENTBSS-FUNCTIONALBTSMDISCBSC BTSM


6 System Response

Some CHANGED STATE EVENT REPORTs will appear. They can be examinedin the LMT Message Browser window.

7 Logon




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKLILOCK LI

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


USER: <user>


SW RELEASE: <no>


LOCK BTSM ACK:

name = BTSM:<no>


A30808-X3247-M321-1-7620 85


MMN:BTSE BS 20

9 System Response




2. Select a module with a functional HW/SW state compatible to that of themodule which is being replaced and set the switches according to the affect-ed module.

– For the relevant switch settings of module LI refer to 4.14.1 "LI – Link In-terface".

– For the relevant switch settings of module LIPA refer to 4.14.2 "LIPA – LinkInterface for Primary Access".


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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK LI ACK:

name = RACK:<no>/LI:<no>




86 A30808-X3247-M321-1-7620



b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKLIPERFTEST LI

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

12 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


A30808-X3247-M321-1-7620 87


MMN:BTSE BS 20

13 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKLIUNLOCK LI

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:





executedPhases

phaseId = PreliminaryTestsLI

phaseId = SerialEepromTestLi

phaseId = Bus2ClockControlTestLi

phaseId = EndTestLi


88 A30808-X3247-M321-1-7620


15 System Response





17 System Response


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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK LI ACK:




A30808-X3247-M321-1-7620 89


MMN:BTSE BS 20

18 Logon

















90 A30808-X3247-M321-1-7620


24 Call TAC h...26





END

A30808-X3247-M321-1-7620 91


MMN:BTSE BS 20

3.14 MCLK

1 Go to Procedure “CCLK”

Go to procedure “CCLK”. h...Procedure: 3.14

END

iIn commands the module MCLK is called CCLK.

92 A30808-X3247-M321-1-7620


3.15 OVPT









b MANAGED-ELEMENTBSS-FUNCTIONALBTSMLOCKREQUEST BTSM


4 System Response

iModule OVPT may be removed while power is on!

iWhen the OVPT fails, the PCM-line is interrupted also for all subsequent BTSEs in caseof multidrop configuration.



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

JOB: <no>



USER: <user>


SW RELEASE: <no>


A30808-X3247-M321-1-7620 93


MMN:BTSE BS 20


b MANAGED-ELEMENTBSS-FUNCTIONALBTSMDISCBSC BTSMNAME=BTSM:0


6 System Response


7 Logon




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKLILOCK LI

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

LOCK BTSM ACK:

name = BTSM:<no>


94 A30808-X3247-M321-1-7620


9 System Response



1. Disconnect the Abis-cable.

2. Take out affected module OVPT.


4. Mount and connect new module OVPT.

5. Connect the Abis-cable.


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKLIPERFTEST LI

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

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK LI ACK:





A30808-X3247-M321-1-7620 95


MMN:BTSE BS 20

12 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:



tO = BTSETEST:1


96 A30808-X3247-M321-1-7620


13 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKLIUNLOCK LI

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:





executedPhases

phaseId = PreliminaryTestsLI

phaseId = SerialEepromTestLi

phaseId = Bus2ClockControlTestLi

phaseId = EndTestLi


A30808-X3247-M321-1-7620 97


MMN:BTSE BS 20

15 System Response





17 System Response


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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK LI ACK:




98 A30808-X3247-M321-1-7620


18 Logon

















A30808-X3247-M321-1-7620 99


MMN:BTSE BS 20

24 Call TAC h...27




h...Procedure: 3.23




END

100 A30808-X3247-M321-1-7620


3.16 PA / DCPA








3.22

N h...3

!CAUTION!Switch off the power before exchanging the modules PA and/or DCPA!Non-observance can lead to personal injury or property damage.This warning must appear in the original German text:ACHTUNG!Strom abschalten , bevor die Module PA und/oder DCPA ausgetauscht werden.Nichtbeachtung kann zu Körperverletzung oder Sachschäden führen.

iModules PA and DCPA are both created as module PA!


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

iIf you replace a PA with ESN data by the enhanced version without ESN data, youmust delete the PA after the replacement and re-create it. This is necessary for the au-tomatic update of the Remote Inventory Data.

A30808-X3247-M321-1-7620 101


MMN:BTSE BS 20





– for module TPU see 3.21 "TPU / DCTPU"

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKPALOCK PA

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

5 System Response



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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK PA ACK:

name = RACK:<no>/PA:<no>




102 A30808-X3247-M321-1-7620


1. Switch power off by means of the coresponding fuse, refer to chapter4.11 "Fuses BS20".

2. In case of PA, disconnect all semi-rigid cables from the module PA.

3. Pull affected module PA and/or DCPA.


– Any jumpers have to be inserted and any switches set identically to thoseon the module which is being replaced. Refer to chapter 4.17 "PA".


6. Connect all semi-rigid cables at module PA.

7. Switch power on by the coresponding fuse.



b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKPAPERFTEST PA

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

8 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


A30808-X3247-M321-1-7620 103


MMN:BTSE BS 20

9 Test Report





b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKPAUNLOCK PA

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:




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

executedPhases

phaseId = PreliminaryTestsPA

phaseId = PreliminaryTestsPa

phaseId = EndTestPA


104 A30808-X3247-M321-1-7620


11 System Response









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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK PA ACK:

name = RACK:<no>/PA:<no>



A30808-X3247-M321-1-7620 105


MMN:BTSE BS 20









17 Call TAC h...20




h...Procedure: 3.23




END

106 A30808-X3247-M321-1-7620


3.17 PCM



END

A30808-X3247-M321-1-7620 107


MMN:BTSE BS 20

3.18 RXAMCO








3.22

N h...3




iModule RXAMCO or RXAMCO_WITH RACKEXT is managed via the managed objectRXMUCO in the LMT.


iModule RXAMCO may be removed while power is on!

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

108 A30808-X3247-M321-1-7620



b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXMUCOLOCK RXMUCO

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

5 System Response



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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK RXMUCO ACK:

name = RACK:<no>/RXMUCO:<no>




A30808-X3247-M321-1-7620 109


MMN:BTSE BS 20

1. Disconnect all semi-rigid cables.



4. Jumpers have to be inserted and any switches set identically to those of themodule which is being replaced. Refer to chapter 4.18 "RXAMCO",4.20 "RXMUCO" or 4.21 "RXMUCO2".


6. Connect all semi-rigid cables.


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXMUCOPERFTEST RXMUCO

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

8 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


110 A30808-X3247-M321-1-7620


9 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXMUCOUNLOCK RXMUCO

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:





executedPhases

phaseId = PreliminaryTestsRXMUCO

phaseId = CheckAlarmStatusRXMUCO

phaseId = EndTestRXMUCO


A30808-X3247-M321-1-7620 111


MMN:BTSE BS 20

11 System Response









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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>






112 A30808-X3247-M321-1-7620










17 Call TAC h...20




h...Procedure: 3.23




END

A30808-X3247-M321-1-7620 113


MMN:BTSE BS 20

3.19 RXAMOD








3.22

N h...3





b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXAMODLOCK RXAMOD

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


iModule RXAMOD may be removed while power is on!

114 A30808-X3247-M321-1-7620


5 System Response



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

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK RXAMOD ACK:

name = RACK:<no>/RXAMOD:<no>




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

A30808-X3247-M321-1-7620 115


MMN:BTSE BS 20


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXAMODPERFTEST RXAMOD

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

8 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


116 A30808-X3247-M321-1-7620


9 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXAMODUNLOCK RXAMOD

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:




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

executedPhases

phaseId = PreliminaryTestsRXAMOD

phaseId = CheckAlarmStatusRXAMOD

phaseId = EndTestRXAMOD


A30808-X3247-M321-1-7620 117


MMN:BTSE BS 20

11 System Response









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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK RXAMOD ACK:

name = RACK:<no>/RXAMOD:<no>



118 A30808-X3247-M321-1-7620










17 Call TAC h...20




h...Procedure: 3.23




END

A30808-X3247-M321-1-7620 119


MMN:BTSE BS 20

3.20 RXMUCO








3.22

N h...3





b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXMUCOLOCK RXMUCO

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


iModule RXMUCO may be removed while power is on!

120 A30808-X3247-M321-1-7620


5 System Response



1. Disconnect all semi-rigid cables.



4. Jumpers have to be inserted and any switches set identically to those of themodule which is being replaced. Refer to chapter 4.18 "RXAMCO",4.20 "RXMUCO" or 4.21 "RXMUCO2".


6. Connect all semi-rigid cables.

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>







A30808-X3247-M321-1-7620 121


MMN:BTSE BS 20


b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXMUCOPERFTEST RXMUCO

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

8 System Response

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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:



tO = BTSETEST:1


122 A30808-X3247-M321-1-7620


9 Test Report




b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKRXMUCOUNLOCK RXMUCO

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:





executedPhases

phaseId = PreliminaryTestsRXMUCO

phaseId = CheckAlarmStatusRXMUCO

phaseId = EndTestRXMUCO


A30808-X3247-M321-1-7620 123


MMN:BTSE BS 20

11 System Response









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


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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>






124 A30808-X3247-M321-1-7620










17 Call TAC h...20




h...Procedure: 3.23




END

A30808-X3247-M321-1-7620 125


MMN:BTSE BS 20

3.21 TPU / DCTPU








3.22

N h...3

!CAUTION!Switch off the power before exchanging modules TPU and/or DCTPU!Non-observance can lead to personal injury or property damage.This warning must appear in the original German text:ACHTUNG!Strom abschalten, bevor die Module TPU und/oder DCTPU ausgetauscht werden.Nichtbeachtung kann zu Körperverletzung oder Sachschäden führen.


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

iModules TPU and DCTPU are both created as module TPU!

126 A30808-X3247-M321-1-7620






– for module PA see 3.16 "PA / DCPA"

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKTPULOCK TPU

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

5 System Response



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

<no> Command

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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK TPU ACK:

name = RACK:<no>/TPU:<no>




A30808-X3247-M321-1-7620 127


MMN:BTSE BS 20

1. Switch power off by means of the corresponding fuse, refer to chapter4.11 "Fuses BS20".

2. In case of TPU, disconnect all semi-rigid cables from TPU.

3. Pull affected module TPU and/or DCTPU.



6. Connect all semi-rigid cables at module TPU.

7. Switch power on by the corresponding fuse.



b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKTPUPERFTEST TPU

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

8 System Response

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

<no> Command

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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


PERFTEST ACK BTSE:


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

tO = BTSETEST:1


128 A30808-X3247-M321-1-7620


9 Test Report


If the “testOutcome” is "fail", some more information is given, such as "ProposedRepair Action" etc.



b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACKTPUUNLOCK TPU

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

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:

name = BTSE:<no>



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

executedPhases

phaseId = PreliminaryTestsTPU

phaseId = BootEepromTestDRCTpu

phaseId = SerialEepromTestDRCTpu

phaseId = SerialEepromTestARCTpu

phaseId = LocalTestLoopDRCARCTpu

phaseId = #Invalid Value 268


A30808-X3247-M321-1-7620 129


MMN:BTSE BS 20

11 System Response









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

<no> Command

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

JOB: <no>



USER: <user>

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

SW RELEASE: <no>


LOCK/UNLOCK TPU ACK:

name = RACK:<no>/TPU:<no>



130 A30808-X3247-M321-1-7620










17 Call TAC h...20




h...Procedure: 3.23




END

A30808-X3247-M321-1-7620 131


MMN:BTSE BS 20

3.22 TX/RX Path

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 correct-ly? Y h...9

N h...2

2 Fasten Cable Connections

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




iIn 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 proce-dure.

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 (DUKIT, HYCOM, RXAMCO, RXMUCO)– antenna (including RXAMOD)– TPU– PA.It is recommended to start with the replacement of the module that is addressed in thefault message. Afterwards – if the error is still there – take the other modules in theTX/RX path into consideration.

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

132 A30808-X3247-M321-1-7620


4 Lock All Disabled Modules

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACK<Module>LOCK <Module>

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

5 Test All Disabled Modules

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACK<Module>PERFTEST <Module>

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

6 Unlock All Locked Modules

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACK<Module>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.) Y h...8

N h...11

8 Additional Check

If an LMT is available, perform the following command:


All active alarms will be listed in the Message Browser Window.

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

Does the alarm still appear? Y h...9N h...12

A30808-X3247-M321-1-7620 133


MMN:BTSE BS 20

9 Do the Cables Look O.K.?

Examine the cables visually for damages, such as sharp bends, cracks or badsoldering connections. Do the cables look O.K.? Y h...11

N h...10

10 Call Tac

Call Tac to have the damaged cable(s) replaced. h...12

11 Continue with the Fault Clearance Procedure

Continue with the fault clearance procedure of the module that is addressed inthe fault message. Afterwards – if the error is still there – take the other modulesin the TX/RX path into consideration.

h...Procedure: 3.x




END

134 A30808-X3247-M321-1-7620


3.23 Remote Inventory Data Update

After the replacement of a nob_RIU component, the remote inventory data and thebackup copy must be updated.

1 Upload IDT-File from BTSE

The remote inventory data have to be loaded to the LMT PC.

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEREMINVUPLLIDF REMINV(DESTDIR=<path>)(FILE=<file name>)OVERWRITE=YES

The values DESTDIR and FILE are optional. If no special path or file name isentered, the file is uploaded to the default directory of the IDF editor.If the value OVERWRITE=YES is selected, a former version of an uploaded IDT-file will be overwritten.

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

2 System Response

iStarting with BR7.0, a second LMT software is available: the new LMT Evolution. Forperforming this procedure with the LMT Evolution, refer to the operator guidelinesOGL:LMT Evolution and OGL:IDF Evolution.


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

JOB: <no>




Uploading File <for example: BTSE.IDT>:

To: <for example: BTSE.IDT>

A30808-X3247-M321-1-7620 135


MMN:BTSE BS 20

On Directory:<for example:...\Idf\Upload>



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

JOB: <no>




Uploading End: File <for example: BTSE.IDT> Transfer Completed


136 A30808-X3247-M321-1-7620


3 Start IDF Editor

b Start the IDF editor:

– Start the IDF editor via the WINDOWS Start menu (“Start” -> “Programs” ->“LMT...” -> “IDF Editor”),or

– click on the “IDF” icon on the “LMT Control Center” window.

4 Open IDT-File

b Open the IDT-file:


– Select the uploaded file from the list in the appearing window; e.g.:<C:...\LMT<version>\Idf\Upload\BTSE.idt>.

– Click on the “Open” button.

A30808-X3247-M321-1-7620 137


MMN:BTSE BS 20

5 Edit Remote Inventory Data of the Replaced Unit

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

b Edit the remote inventory data of the replaced unit(s):

– Move the mouse cursor to the record of the replaced unit.

– Press the right mouse button.

An “Edit” button appears.

– Click on the “Edit” button.

The “PIDnobRIU’s” window opens.

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

– Edit the data manually, or

– click on the “Scan” button to use the 2D-Code Reader.

When the 2D-Code Reader is used for the first time, the “Common Port: Setting”window opens.

– Select the serial port.

– To start the scanning process, press the button on the 2D-Code Reader.

The data is inserted into the corresponding fields.

– Confirm by clicking on the “OK!” button.

– Click on “Save” in the “File” menu.

138 A30808-X3247-M321-1-7620


6 Export IDF-File for Backup

b Export IDF-file:

– Select “IDF” in the “Export” menu.

– Select the destination path in the appearing window, preferably “A:\”.

The file name is automatically composed of the “SalesUniqueName” with theextension “.idf ” .


– Put the disk with the backup file of the inventory data to the site specificdocumentation.

7 Export Nob_Riu part for Download to the BTSE

Only the nob_RIU-part has to be exported for downloading into the BTSE.

b Export the nob_RIU-part:

– Select “NOB” in the “Export” menu.

The file name is automatically composed of the “SalesUniqueName” with theextension “.nob ” .


A question window opens: Create Nob RIUs file for Download?

– Click on the “Yes” button.

A window opens which displays the destination path of the NOB-file, forexample:C:...\LMT<version>\Idf\Dnload\BTS_NRIU.nob

– Click on the “OK” button.

A30808-X3247-M321-1-7620 139


MMN:BTSE BS 20

8 Download nob_RIU File to BTSE

Change to the LMT application!

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEREMINVDNLIDF REMINVSRCDIR=<source directory>

SRCDIR: enter the source directory in which the exported NOB-file was saved,for example C:...\LMT<version>\Idf\Dnload.

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

9 System Response


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

JOB: <no>


COMMAND: DNLIDF REMINV:NAME=REMINV:<no>,SRCDIR=”<for example:C:...\LMT<ver-sion>\Idf\Dnload”:


Downloading File <for example: BTS_NRIU>:

100% of packets transferred



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

JOB: <no>


COMMAND: DNLIDF REMINV:NAME=REMINV:<no>,SRCDIR=”<for example: C:...\LMT<ver-sion>\Idf\Dnload”:


140 A30808-X3247-M321-1-7620





END

Download End: File <for example: BTS_NRIU> Transfer Completed


A30808-X3247-M321-1-7620 141


MMN:BTSE BS 20

4 Tables, Lists and Figures

142 A30808-X3247-M321-1-7620


4.1 Hardware Architecture

Fig. 4.1 Functional blocks, 2 Carrier BTSE with DUKIT (1 Cell / 2 Carriers)

A bis

LMT

Site Outputs

Site Inputs

0

1

0

1

Diversity

FAN 0

GPSU 0

DCTPU0

DCTPU1

DCPA0

DCPA1

230 V AC-48V

0

0

1

1

BU

S 1 B

US

2

BBSIG 0

BBSIG 1

MCLK 0

CCTRL 0

ALCO 0

PA 0

PA 1

RXAMCO0

BackupBattery

DCBreaker PDBAC/DC 0

TPU 0

TPU 1

DUKIT0

DUKIT1x(2:1)

LI 0

RXAMCO1

Cell 0

A30808-X3247-M321-1-7620 143


MMN:BTSE BS 20

4.2 Front View of the BS 20 Rack and Mounting Positions

Fig. 4.2 2 Carrier BTSE BS 20

Fan Unit 0

Front Door

RXMUCOorRXAMCO0 1 2 3

TP

U 1

PA

1

TP

U 0

PA

0

CC

TR

0

MC

LK 0

LI 0

BB

SIG

1B

BS

IG 0

ALC

O 0

AC

/DC

0

GPSU 0

DC

PA

0

DC

TP

U 0

DC

TP

U 1

DC

PA

1

HYCOM 0 or DUKIT 0 or DUPL20R 0

RXAMOD0RXAMOD

1RXAMOD2RXAMOD

3

GPSU 1

LMT Connector

RX Filter

DC Breaker

Power Distribution Board

Access for External Cabling

Backup Batteries

OVPT

LMT Connector

Managed viathe HMO:

ACOM 0

CCLK 0 PA 0,1

TPU 0,1

RXMUCO0,1,2,3

Additional HMOs:

BPORTLAPDLEXCONNECTENVABTSE

144 A30808-X3247-M321-1-7620


Mounting Unit(MUT)

Device / Module

Name Full Name

B C001 HYCOM Hybrid Combiner

CF F:BTS Frame for 2 Carrier BTSE

G C PDB Power Distribution Box

G C DC Breaker Unit DC Breaker Unit

G C002 OVPT Over Voltage Protection Unit

S001 RXAMOD Receiver Antenna Module

Tab. 4.1 Mounting Units for the 2 Carrier BTSE Rack R:BS 20

Position Device / Module

Mounting Slot-ID Name Full Name

S001 70H RXAMOD 0 Receiver Antenna Module 0




Tab. 4.2 Mounting Position and Simulated Processor IDs (R:BS 20)



CF F104 1EH GPSU 0 Generic Power Supply 0

CF F152 1DH GPSU 1 Generic Power Supply 1

CF F199 80H RXMUCO 0 Receiver Multicoupler 0




CF F259 DCPA 0 DCDC Converter for PA 0

CF F275 DCTPU 0 DCDC Converter for TPU 0

DCPA 1 DCDC Converter for PA 1

DCTPU 1 DCDC Converter for TPU 1

Tab. 4.3 Mounting Position and Slot-ID for the 2 Carrier Rack (R:BS 20)

A30808-X3247-M321-1-7620 145


MMN:BTSE BS 20

4.3 General Information on BTSE LEDs

This chapter contains the common LED signal mechanisms of the BTSE boards. All themodules of the BTSE and the rack itself have LEDs to indicate their status, except thefilter box and the fuse panel in the BTS rack and the RXAMOD, which is mounted closeto the RX antenna.

After the startup a HW test will be executed on each module of the BTSE. Detected HWerrors will be indicated by the flashing reset LED where the number of the failed test isbinary 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:

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

CF E101 40H Fan 0 Fan Unit 0

CF C103 AC/DC 0 AC/DC Converter 0

CF C138 0FH ALCO 0 Alarm and Controller Module

CF C147 01H BBSIG 0 Baseband and Signalling 0

CF C161 03H BBSIG 1 Baseband and Signalling 1

CF C175 0DH LI 0 Link Interface 0

CF C199 09H MCLK 0 Master Clock 0

CF C223 0BH CCTRL 0 Core Controller 0

CF C249 21H PA 0 Power Amplifier 0

CF C272 21H TPU 0 Transceiver and Processor Unit 0

CF C285 23H PA 1 Power Amplifier 1

CF C308 23H TPU 1 Transceiver and Processor Unit 1

B C001 50H51H

HYCOM 0HYCOM 1

Hybrid Combiner 0Hybrid Combiner 1

B C001 50H51H

DUKIT 0DUKIT 1

Duplex Combiner Kit 0Duplex Combiner Kit 1



Tab. 4.3 Mounting Position and Slot-ID for the 2 Carrier Rack (R:BS 20)

– green: Hardware and software are O.K.– red: After reset, during software initialization (one for each processor)– yellow: Active module of redundant boards

146 A30808-X3247-M321-1-7620


4.4 AC/DC

Fig. 4.3 AC/DC (Front View)

FUSE10AT250V

AC230V

45Hz – 65Hz7,5 AMPS

AC

TEMP

BAT

DC

ALARMSAND DCOUTPUT

BATTERY

DISCONNECTED

DC

DC

VOLTAGE

CURRENT10mV/A

LED green

LED red

LED green

LED green

+

-Scale 1:1

A30808-X3247-M321-1-7620 147


MMN:BTSE BS 20

LED

AC Alternating CurrentThe primary power source is present

BAT BatteryNo battery charging fault

DC Direct CurrentDC output voltage is in specified tolerance

TEMP TemperatureOver temperature indication

Connectors

AC Alternating CurrentAC input (230 V)

ALARMS ANDDC OUTPUT

Alarms and DC output

DC VoltageDC Current DC measurement points

Switch

Switch for the disconnection of the battery from AC/DC module be-hind the cover plate. For disconnection unscrew the cover plate!

148 A30808-X3247-M321-1-7620


4.5 ALCO

Fig. 4.4 ALCO (Front View)

TAD

ALCO without redundancy (Q300)

RY RE

AC S3

S1 S2

RES

LED red

LED red

LED red

LED green

LED yellow

LED red

Push Button

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

Push Button

S1 S2

AC S3

RY R0

RES 0

LED red

LED red

LED red

LED red

LED yellow

LED green

Push Button

A30808-X3247-M321-1-7620 149


MMN:BTSE BS 20

LED

AC Active blockThe active block LED indicates which ALCO block (0 or 1) hastaken over service.It is then switched on parallel to the ready LED

RY ReadyThe Ready LED indicates that the ALCO has passed the initialmodule tests and is ready for the communication with the con-nected interface partner (CCTRL or Test-PC).It is switched on by the subsystem RC after successful initializa-tion of the O&M subsystems

R0 RESET Block 0R1 Reset Block 1RE The Reset LED indicates the phase from a reset until the fin-

ished recovery in the Load-SW. It is switched on by a reset andoff by the subsystem RC after successful initialization of theO&M subsystems.An additional task is the signalling of Hardware Errors detectedduring the initial (Boot-SW) or extended (Load-SW) HardwareTests

S1 not usedS2 not usedS3 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)

Test Adapter

TAD Test Adapter50 pin AMP jack for ALCO (test adapter for V24 interface ac-cess)

150 A30808-X3247-M321-1-7620


Fig. 4.5 ALCO (Top View)

Plu

g

1

Fro

nt P

anel

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 “ze-

Address Switch 1 Switch 2 Switch 3 Switch 4

0 ON ONONON

A30808-X3247-M321-1-7620 151


MMN:BTSE BS 20

4.6 BBSIG

Fig. 4.6 BBSIG44 (Front View)

BBSIG44

TAD

RBB1

SPA1

RES

LED red

LED green

LED red

LED green

Pushbutton

RBBC

RY

152 A30808-X3247-M321-1-7620


LED

RBB 1 Reset BB1 Base Band Slave 1RBBC Reset BBC Base Band Controller

The reset LEDs indicate the phase from a reset until the moment whenall O&M subsystems in the Load-SW are initialized.The LED is switched on: by a reset

off: by the recovery managementNote:1) An additional task is the signalling of Hardware errors detected dur-ing the initial (Boot-SW) or extended (Load-SW) Hardware Tests. TheLED 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, theRBBC 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 1requesting and/or providing data from/to the Um interface (Spare 1).It is also called SW signal 1 LED

RY ReadyThe Ready LED indicates that the BBSIG has passed the initial moduletests and is ready for the communication to the connected interfacepartner (CCTRL or Test PC). This LED is also called SW signal 2 LED.It is switchedon: by the boot management after the initial module tests and task ini-tialization in Boot-SWoff: by reset or a failed Hardware Test

Switch

RES ResetResets all BBSIG processors

Test Adapter

TAD Test Adapter100 pin AMP jack for test adapter for C 40 boards

A30808-X3247-M321-1-7620 153


MMN:BTSE BS 20

Fig. 4.7 BBSIG44 (Top View)

Plu

g

Fro

nt P

anel

D104

EPROM

1

154 A30808-X3247-M321-1-7620


4.7 CCTRL

Fig. 4.8 CCTRL (Front View)

LED red

LED red

LED green

LED green

LED yellow

LED green

Push Button

TAD

RY

ACT

SPA1

RES

RBM

PRGA

SPA2

A30808-X3247-M321-1-7620 155


MMN:BTSE BS 20

LED

RY ReadyThe Ready LED indicates that the CCTRL has passed the initial mod-ule tests and is ready for the communication to the connected inter-face partner (LMT or Test PC).It is switchedon: by the boot management after the initial module tests and task ini-tialization in Boot-SWoff: by reset or a failed Hardware Test

RBM Reset Bus Master ControllerThe 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 connec-tion to the Abis will be established).It is switchedon: by a resetoff: by the recovery managementNote:An additional task is the signalling of hardware errors detected duringthe initial (Boot-SW) or extended (Load-SW) hardware tests. The LEDflashes with a sequence in which the test number is coded.

ACT Active masterThe Active Master LED signals which CCTRL has the master state.It is switchedon: if the ready LED is switched on and the module has got the masterstateoff: by a reset

PRGA Programming ActiveThe flash LED is switched on when the programming voltage for theFlash EPROM is activated.

SPA1 not usedIt is also called SW Signal 1 LED.

SPA2 The flashing SW Signal 2 LED signals a running OS (Operating Sys-tem). This LED is also called SW Signal 2 LEDIt is switched:on: by the OSoff: by the OS and a reset

Switch

RES ResetResets the entire CCTRL.

156 A30808-X3247-M321-1-7620


Fig. 4.9 CCTRL (Top View)

Test Adapter

TAD Test Adapter50 pin AMP jack for test adapter for serial interface access

Plu

g

Fro

nt P

anel

1

D88

EPROM

A30808-X3247-M321-1-7620 157


MMN:BTSE BS 20

4.8 DCPA

Fig. 4.10 DCPA (Front View)

LED green

LED

PS Power SupplyThis LED indicates: Power on

158 A30808-X3247-M321-1-7620


4.9 DUKIT

Fig. 4.11 DUKIT20 (Front View)

Scale 1:2, 1:4

TX1 TX0 ANT1 ANT0TP1

Ala

rm1

Pow

er2x

1:1

2:1

ANTDIV1 ANTDIV0RXDIV1 RXDIV0

RX1 RX0TP0

Ala

rm0

VSWR

2.0

1.75 1.5

LED red

LED red LED green

Connector

TX 0/1 TX-Input 0/1TX-Input 0/1 for connection with module PA: RF-output

ANT 0/1 Antenna OutputOutput for antenna connection

ANT div 0/1 Antenna Output for Diversity

TP 0/1 Connector for test loop 0/1

RX 0/1 RX-output 0/1RX-output 0/1 for connection with module RXAMCO

A30808-X3247-M321-1-7620 159


MMN:BTSE BS 20

RXDIV 0/1 RX-diversity output 0/1RX-output 0/1 for connection with module RXAMCO for diversitypath

LED

Power Power SupplyThis LED indicates: Power on

Alarm 0/1 VSWR alarm

Switch

VSWR adjust the selected VSWR

2x1:1/2:1 Configuration switch for DUKIT mode selection

160 A30808-X3247-M321-1-7620


4.10 FAN

Fig. 4.12 FAN (Front View)

Switch LED green

OFF

ON

LED

Power on This LED indicates: Power on

Switch

Power on/off

A30808-X3247-M321-1-7620 161


MMN:BTSE BS 20

4.11 Fuses BS20

Fig. 4.13 Fuses BS20

ON

OFF

Switch Fuse Overvoltage EarthProtection leakage

circuit breaker

FU1 FU04

AC DC

ON

OFF

ON

OFF

ON

OFF

Fuses

FU 01 10 A Fuse for TPU 0/PA 0 (DCTPU 0/DCPA 0)

FU 02 10 A Fuse for TPU 1/PA 1 (DCTPU 1/DCPA 1)

FU 03 16 A Fuse for GPSU and BBSIG 0/1

FU 04 4 A Fuse -48V external

Switch Fuse Fuse for Rack Power Supply

Earth leakagecircuit breaker

40A/300mA for Rack Power Supply and 25A/30mA for 220Vsocket (under the rack)

162 A30808-X3247-M321-1-7620


4.12 GPSU

Fig. 4.14 GPSU (Front View)

LED green

LED green

LED green

LED green

PIP

5V

PS

12V

5V12VPIP

LED

PS Power SupplyAll functions are O.K.

PIP Primary Input PowerPrimary Input Power is O.K.

5 V The 5 V output is O.K.12 V The 12 V output is O.K.

A30808-X3247-M321-1-7620 163


MMN:BTSE BS 20

Connector

5 V12 VPIP Primary Input Power

164 A30808-X3247-M321-1-7620


4.13 HYCOM

Fig. 4.15 HYCOM two 1-WAY Horizontal (Front View)

LED green

LED red

Scale 1:2, 1:4

TESTOUT1

ANTOUT1 ANTOUT0

TESTOUT0

TXIN1 TXIN0

HYSIGN1 HYSIGN0POWER1

ALARM1VSWR1

POWER0

ALARM0VSWR01,51,72,0

1,51,72,0

LED red

LED green

A30808-X3247-M321-1-7620 165


MMN:BTSE BS 20

Fig. 4.16 HYCOM 2-/4-WAY Horizontal (Front View)

Scale 1:2, 1:4

ANTOUT

TXIN1 TXIN0

HYSIGN

POWER

ALARMVSWR1,51,72,0

LED red

LED green

TXIN3 TXIN2

TESTOUT

TXIN1 TXIN0

2-WAY

4-WAY

Connector

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




HY SIGN Alarm and Signalling

166 A30808-X3247-M321-1-7620


Detection of combined configuration and operation parametersANTOUT 0/1 Antenna Output

Output for antenna connection

Switch

Selector Voltage Standing Wave Ratio (VSWR)

A30808-X3247-M321-1-7620 167


MMN:BTSE BS 20

4.14 LI

4.14.1 LI – Link Interface

Fig. 4.17 LI (Front View)

LED red

LED red

LED red

LED green

LED yellow

LED red

Push Button

TAD

RY

ACT

1ER-3

RES

RLIC

SPA

2ER-3

LED red

LED red

LED red

LED red

1RAI

1ER-6

2RAI

2ER-6

168 A30808-X3247-M321-1-7620


LED

1/2RAI Remote Alarm Indication Port 1/2The LED indicates the remote alarms (A-/E-Bit) received on port 1.

1/2ER-6 Port 1/2, Bit Error Rate > 10 Exp-6If the BER is greater than 10 Exp-6 for 1 minute or PCM30 CRC4 er-rors 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 minuteand no CRC4 errors are detected.

RY ReadyThe Ready LED indicates that the LI has passed the initial moduletests and is ready for communication to the connected interface part-ner (CCTRL or Test PC). It is switched on by the recovery manage-ment after successful initialization of the O&M subsystems.

RLIC Reset LIThe Reset LED indicates the phase from a reset until the finished re-covery in the Load-SW. It is switched on by a reset and off by the re-covery management after successful initialization of the O&Msubsystems.An additional task is the signalling of hardware errors detected dur-ing the initial (Boot-SW) or extended (Load-SW) hardware tests. TheLED flashes with a sequence in which the test number is coded.

ACT Activenot used

SPA Sparenot used

1/2ER-3 Port 1/2, Bit Error Rate > 10 Exp-3The LED will be switched on if the BER is > 10 Exp-3 for 1 sec or thesignal or the frame synchronization are lost on port 1. It will beswitched off after the disturbances are removed.

Switch

RES ResetResets the link interface.

Test Adapter

TAD Test Adapter50 pin AMP jack for test adapter access

A30808-X3247-M321-1-7620 169


MMN:BTSE BS 20

Fig. 4.18 LI; Variant 1 (Top View)

Plu

g

Fro

nt P

anel

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

170 A30808-X3247-M321-1-7620


Switches Variant 1

Fig. 4.19 LI; Variant 2 (Top View)

Switch Position FunctionS2/6 1

2outgoing 75 Ωoutgoing 120 Ω

S3/7 12

incoming 75 Ωincoming 120 Ω

S4/8 12

outgoing groundedoutgoing not grounded

S5/9 12

incoming groundedincoming not grounded

Plu

g

Fac

epla

te

1

D6

EPROMSubmodule 2

Submodule 1

Submodule 1 and submodule 2 aremounted upside down. The switchesface the motherboard.

A30808-X3247-M321-1-7620 171


MMN:BTSE BS 20

Fig. 4.20 LI; Variant 2 (Submodule)

Switches Variant 2

* The PCM30 clocks are routed via transformers on the PCM30 module to the TAD plugof the module LI. Two lines for every clock are utilized on the PCM30 module to transferthese clocks (a/b-wires). For each clock only the a-wire is routed to the TAD. The b-wireshould be connected to ground via switch S5 on the PCM30 module. Then the signallevel is as follows: approx. +/-3V symmetrical to ground.

SwitchesSubmodule 1 / 2

S2

S3

S4

S5

1 2

1 2

1 2

1 2

1 2

S1

Switch Position FunctionS1 1

2outgoing 75 Ωoutgoing 120 Ω

S2 12

incoming 75 Ωincoming 120 Ω

S3 12

outgoing groundedoutgoing not grounded

S4 12

incoming groundedincoming not grounded

S5 * 1

2

PCM Receive/Transmit-Clock grounded at measurementoutputPCM Receive/Transmit-Clock not grounded at measure-ment output

172 A30808-X3247-M321-1-7620


4.14.2 LIPA – Link Interface for Primary Access

Fig. 4.21 LIPA (Front View)

LED red

LED red

LED red

LED green

LED yellow

LED red

Push Button

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

A30808-X3247-M321-1-7620 173


MMN:BTSE BS 20

LED

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-BitYellow Alarm

for PCM30 (from BR3.7 upwards)for PCM24

xER-6 Port x (x=1,2,3,4), Bit Error Rate > 10 Exp-6If the BER is greater than 10 Exp-6 for 1 minute or PCM30 CRC4 errorsare 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 noCRC4 errors are detected.CRC errors are:CRC4CRC6

for PCM30crc4 format (from BR3.7 upwards)for PCM24crc6esf format

xER-3 Port 1, Bit Error Rate > 10 Exp-3The LED will be switched on if the BER is > 10 Exp-3 for 1 sec. or the sig-nal or the frame synchronization are lost on port 1. It will be switched offafter the disturbances are removed.

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

RLIC Reset LIThe Reset LED indicates the phase from a reset until the finished recoveryin the Load-SW. It is switched on by a reset and off by the recovery man-agement after successful initialization of the O&M subsystems.An additional task is the signalling of hardware errors detected during theinitial (Boot-SW) or extended (Load-SW) hardware tests. The LED flasheswith a sequence in which the test number is coded.

ACT Activecurrently not used

SPA Sparecurrently not used

1ER-3 Port 1, Bit Error Rate > 10 Exp-3The LED will be switched on if the BER is > 10 Exp-3 for 1 sec. or the sig-nal or the frame synchronization are lost on port1. It will be switched off af-ter the disturbances are removed.

Switch

RES ResetResets the link interface.

174 A30808-X3247-M321-1-7620


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 theirfunctions and correct settings.

Test Adapter

TAD Test Adapter50 pin AMP jack for test adapter access

A30808-X3247-M321-1-7620 175


MMN:BTSE BS 20

Fig. 4.22 LIPA (Top View)

Plu

g

Fro

nt P

anel

EPROM1

D94

S1

S2

S3

S4

110

98

76

54

32

ON

Port 1

Port 2

Port 3

Port 4

176 A30808-X3247-M321-1-7620


Fig. 4.23 Switches for Line Impedance Matching (PCM30 120 Ω)



1 1098765432

ONPCM30120 Ω

Switch 1 2 3 4 5 6 7 8 9 10

Position OFF ON OFF OFF OFF OFF OFF OFF OFF OFF

Tab. 4.4 Positions of Contacts for PCM30 120 Ω

1 1098765432

ONPCM3075 Ω

Switch 1 2 3 4 5 6 7 8 9 10

Position ON OFF ON ON ON OFF OFF ON OFF OFF


1 1098765432

ONPCM24100 Ω

Switch 1 2 3 4 5 6 7 8 9 10

Position ON OFF OFF ON OFF ON OFF OFF ON OFF


A30808-X3247-M321-1-7620 177


MMN:BTSE BS 20

4.15 MCLK

Fig. 4.26 MCLK (Front View)

LED red

LED red

LED yellow

LED green

LED yellow

LED green

Push Button

TAD

RY

ACT

FLOC

RES

RCCK

HMO

PMO

178 A30808-X3247-M321-1-7620


LED

RY ReadyThe Ready LED indicates that the MCLK has passed the initial moduletests and is ready for communication to the connected interface partner(CCTRL or Test PC). It is switched on by the recovery management af-ter successful initialization of the O&M subsystems.

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

RCCK Reset Common Clock ControllerThe Reset LED indicates the phase from a reset until the finished recov-ery in the Load-SW. It is switched on by a reset and off by the recoverymanagement after successful initialization of the O&M subsystems.An additional task is the signalling of hardware errors detected duringthe initial (Boot-SW) or extended (Load-SW) hardware tests. The LEDflashes with a sequence in which the test number is coded.

HMO Holdover ModeThe holdover mode signals that the Abis line frequency is not correct forregulation.

FLOC Frequency LockedThis LED indicates that MCLK accuracy level has reached high, whichmeans that the frequency accuracy is better than +/- 0.05 ppm.

PMO Plesiochronous ModeThis LED indicates that the clock is not phase synchronized to the Abisline. If the Frequency Locked LED is off, the LED indicates that the ac-curacy level is MEDIUM (accuracy > +/-0.05 ppm).

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

LED State MatrixFLOC PMO HMO Meaning

on Accuracy level = MEDIUMon on Accuracy level = HIGH: not phase synchronized to Abis Lineon Accuracy level = HIGH: phase synchronized to Abis Lineon on on Holdover Mode: Accuracy level = HIGH

on on Holdover Mode: Accuracy level = MEDIUMAccuracy level = LOW

A30808-X3247-M321-1-7620 179


MMN:BTSE BS 20

Fig. 4.27 MCLK (Top View)

LEDRES Reset

Reset the MCLK

Test AdapterTAD Test Adapter

50 pin AMP jack for test adapter access

Plu

g

Fro

nt P

anel

1

D89

EPROM

180 A30808-X3247-M321-1-7620


4.16 OVPT

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

Tab. 4.7 Pinning Label of the Terminal Block

A30808-X3247-M321-1-7620 181


MMN:BTSE BS 20

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

182 A30808-X3247-M321-1-7620


4.17 PA

Fig. 4.30 PA (Front View)

ALM

LED red

TXOUT

TXIN

A30808-X3247-M321-1-7620 183


MMN:BTSE BS 20

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

4.17.1 Jumper Settings on GSM 1800 PA

Fig. 4.31 GSM 1800 PA 10W/25W (U434/U466)

LEDALM ALARM

This LED indicates a power amplifier alarm.

ConnectorTXOUT RF output for connection with HYCOMTXIN 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

Fron

t Pan

el

184 A30808-X3247-M321-1-7620


Fig. 4.32 GSM 1800 PA25D (U519)

Location Connection Effect

A 1-22-3open

normal operationmicroprocessor resetnot applicable

B 1-2open

normal operationmicroprocessor stopped

C 1-2open

normal operationHSCX stopped

D 1-22-33-41-4

not applicablenormal operationcontrol loop opennot applicable

E open test points; to be left open

F open test points; to be left open

G 1-2open

normal operationonly for test of IC9

Tab. 4.8 Jumper Settings on GSM 1800 PA 10W/25W (U434/U466)

A B

C

123

1 2

1 2

D

E

TP14 TP15

TP13

TP17

TP19Fron

t Pan

el

A30808-X3247-M321-1-7620 185


MMN:BTSE BS 20

4.17.2 Jumper Settings on GSM 900 PA

Fig. 4.33 GSM 900 PA 25W (U435)


A 1-22-3open


B 1-2open


C 1-2open


D TP13-TP14TP14-TP15

normal operationtest phase only

E openTP17-TP19

to be left open for normal operationtest phase only

Tab. 4.9 Jumper Settings on GSM 1800 PA25D (U519)

D

E

1 2

34

AB

C

123

1 2

21

Fron

t Pan

el

186 A30808-X3247-M321-1-7620


Fig. 4.34 GSM 900 PA 25W/40W (U538/U520)


A 1-22-3open


B 1-2open


C 1-2open


D 1-22-33-41-4

not applicablenormal operationcontrol loop opennot applicable

E open test points; to be left open

Tab. 4.10 Jumper Settings on GSM 900 PA 25W (U435)

123

1 2

21

123

A B

D

C

Fron

t Pan

el

A30808-X3247-M321-1-7620 187


MMN:BTSE BS 20


A 1-22-3open


B 1-2open


C 1-2open


D 1-22-3

control loop opennormal operation

Tab. 4.11 Jumper Settings on GSM 900 PA 25W/40W (U538/U520)

188 A30808-X3247-M321-1-7620


4.18 RXAMCO

Fig. 4.35 RXAMCO (Front View)

BIAS

LED green

RX

O3

RX

O2

RX

O1

RX

O0

RX

CA

RF

LBIN

RX

IN

LED

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

A30808-X3247-M321-1-7620 189


MMN:BTSE BS 20

Connector

RXIN Receive InputRF-Input

RFLBIN Radio Frequency Loopback InputRF-Input for Loopback

RXCA Receive Cascading OutputRF-Output for further cascading

RXO0 Receive Output 0RF-Output for connection with module TPU:RF-input




190 A30808-X3247-M321-1-7620


4.19 RXAMOD

Fig. 4.36 RXAMOD (Bottom View)

RFOUT

RFIN

View of Mast Head Unit MHU from below

Connector

7 / 16” female 50 ΩRF IN Receive Input

RF InputRF OUT Receive Output

RF Output for RXMUCO

A30808-X3247-M321-1-7620 191


MMN:BTSE BS 20

4.20 RXMUCO

Fig. 4.37 RXMUCO (Front View)

BIAS

RXIN

RXCA

RXO0

RXO1

RXO2

RXO3

LED green

LED


192 A30808-X3247-M321-1-7620


Fig. 4.38 RXMUCO (Top View)

Connector



RXO0 Receive Output 0RF-Output for connection with module TPU:RF input




Jumpers

A30808-X3247-M321-1-7620 193


MMN:BTSE BS 20

Jumper

The operational setting for the jumper is shown in the figure above.The module signals are switched through to the backplane in this set-ting.

194 A30808-X3247-M321-1-7620


4.21 RXMUCO2

Fig. 4.39 RXMUCO 2 (Front View)

BIAS

LED green

RX

O3

RX

O2

RX

O1

RX

O0

RX

CA

RF

LBIN

RX

IN

LED


A30808-X3247-M321-1-7620 195


MMN:BTSE BS 20

Fig. 4.40 RXMUCO2 (Top View)

Connector


RFLBIN Radio Frequency Loopback InputRF-Input for loopback






Jumpers

S1

S2

S3

S4

Attenuation

196 A30808-X3247-M321-1-7620


Gain Control

A step RF attenuator from 0 dB to 10 dB with 1 dB steps is provided in order to set therequired RF level in the RX chain for a given value of the RXAMOD-RXMUCO2 cableattenuation.In this way 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 Fig. 4.40and Tab. 4.12).

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 valueof 0 dB.

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

0 Open Open Open Open

1 Close 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

Tab. 4.12 Dip Switches Configuration Versus RF Attenuation

Jumper

The operational settings for the jumpers are shown in the figure above.The module signals are switched through to the backplane in this setting.

A30808-X3247-M321-1-7620 197


MMN:BTSE BS 20

4.22 TPU

Fig. 4.41 TPU / TPU2 (Front View)

TAD

RX

RXDIV

TX

RD1

SPA

DC5

RES

LED red

LED green

LED green

LED red

LED green

LED green

Push Button

RD2

RYD

RYA

RAC LED redLED red RDC

TAD

RX

RXDIV

TX

RD1

SPA

RES

LED red

LED green

LED red

LED green

Push Button

RD2

RYD

RAC LED redLED red RDC

TPU TPU2

198 A30808-X3247-M321-1-7620


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

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 re-covery in the Load-SW. It is switched on by a reset and off by theSubsystem RC after successful initialization of the O&M subsystems.An additional task is the signalling of hardware errors detected duringthe initial (Boot-SW) or extended (Load-SW) hardware tests. TheLED flashes with a sequence in which the test number is coded.

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 momentwhen all O&M subsystems in the Load-SW are initialized.The LED is switched as follows:switch on: by a resetswitch off: by the recovery managementNote:1) An additional task is the signalling of hardware errors detected dur-ing the initial (Boot-SW) or extended (Load-SW) hardware tests. TheLED 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, theRDC LED is switched off 0.25 seconds before a SW-reset is initiated.

SPA SpareIn 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 (hardwaretest) test loop. After unblocking the CP processes, the Spare LEDmakes an off-on-off transition for 256 UL-bursts sent to CH (ChannelControl) on BBSIG.This LED is also called SW Signal 1 LED.

RYD Ready TRXD (DRC + DR1 + DR2)The Ready LED TRXD indicates that the TRXD has passed the initialmodule tests and is ready for the communication to the connected in-terface partner (CCTRL or TPC).This LED is also called SW Signal 2 LED.It is switched as follows:on: by the recovery management after the initial module tests andtask initialization in Boot-SWoff: by reset or a failed hardware test

A30808-X3247-M321-1-7620 199


MMN:BTSE BS 20

DC5 DC 5 VoltThis LED signals the presence of the +5 volt power supply from thededicated power supply unit.

RYA Ready TRXAThe Ready LED indicates that the TRXA has passed the initial mod-ule tests and is ready for the communication to the connected inter-face partner (DRC or TPC). It is switched on by the recoverymanagement after successful activation of the load software.

Switch

RES ResetResets the TRXD and the TRXA.

Connector

RX Receive InputRX-Input for connection with module RXMUCO: RF output

TX Transmit OutputRF-Output for connection with module PA: RF input

RXDIV Receive Input DiversityRX-Input for connection with module RXMUCO: RF outputUsed for diversity antenna.

Test Adapter

TAD Test Adapter100 pin AMP jack for test adapter for C 40 boards.

200 A30808-X3247-M321-1-7620


A30808-X3247-M321-1-7620 201


MMN:BTSE BS 20

5 Appendix

5.1 HW/SW Compatibility during Download from LMT/BSC

This feature allows a compatibility check of the swLoad and the current HW situation ofthe BTSE. Thus, it can be avoided that a swLoad which will not run on the specific BTSEis 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 whenthis VAM file is received in the BTSE. If the result is negative, the download of the swIm-ages is stopped.

This check is performed during the load phase.

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

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

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

Output 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: <user>COMMAND: DNLALLEXE:SRCPATH=”\...\...\... <name>.swl”,OVER-

WRITE=YESSW RELEASE: <no>COMMAND RESULT: OPERATION FAILED

VAM check failed


JOB: <no>

PC Time&Date: <time> <date>NE Time&Date: <time> <date>

USER: <user>SW RELEASE: <no>COMMAND RESULT: OPERATION COMPLETED

FAILURE EVENT REPORT

202 A30808-X3247-M321-1-7620


5.2 State/Status Attributes of BTSE Managed Objects

The following state/status attributes are used for BTSE MOs:

NAME = RACK:0/<module>:0Event Type = Processing Failure EventEvent Time = <Date> <Time>Probable Cause = Configuration or Customization ErrorSpecific Problems = 26676 - Board type not supportedSeverity = WarningTrend Indication = No ChangeNotification Identifier = 48Proposed Repair Action 1 = 189 - Check configuration dataOriginator = 3329Additional Words =Octets 01 to 16: H’6264 H’6c78 H’636d H’6d73 H’07ac H’5a01 H’0212 H’3b3bOctets 17 to 30: H’c304 H’ffff H’ffff H’ffff H’ffff H’ffff H’ffffSoftware Version = <SW Version>


State/Status At-tribute

State/Status Explanation

AdministrativeState (AST)

This state informs whether or not the MO is permitted to provide ser-vice.

Locked The related MO is not permitted to provide service, but is addressablefor maintenance tasks and fully operable (it can, for example, be test-ed). 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 interrupt-ed, 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.

Tab. 5.1 State/Status Attributes of BTSE MOs

A30808-X3247-M321-1-7620 203


MMN:BTSE BS 20

5.3 BTSE Alarm Information

On each BTSE module a local alarm queue for 30 alarms is available. Every 100ms,there is 1 alarm sent to the CCTRL. If currently more alarms are generated, the queuegets full and a reset is performed on the module. After the module is restarted, a corre-sponding Failure Event Report is sent.

Alarm Status(ALS)

This status reports the severity level of active alarms. If more thanone alarm is active, the level of the alarm with the highest severity lev-el 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.

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

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 “Un-locked”. The MO provides service.

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

State/Status At-tribute

State/Status Explanation

Tab. 5.1 State/Status Attributes of BTSE MOs

204 A30808-X3247-M321-1-7620


The following information is forwarded from the BTSE to the BSC:

1. Managed object class

2. Managed object instance

3. Event information

– probable cause value

– event type

– perceived severity

– trend indication

– immediate defense action

– threshold information

5.3.1 Probable Cause Value

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

5.3.2 Event Types

Errors 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

5.3.2.5 Environmental ErrorsThese errors depend on environmental conditions e.g. temperature, door open orsmoke.In general, these faults are signalled to the ALCO module.

A30808-X3247-M321-1-7620 205


MMN:BTSE BS 20

5.3.3 Severity Levels

The severity level indicates to what extent the functionality of the BTSE is affected. Thefollowing values are used:

5.3.3.1 CriticalThe critical severity level indicates that a service affecting condition has occurred andan immediate corrective action is required. Such a severity can be reported, for exam-ple, 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 andan urgent corrective action is required. Such a severity can be reported for example, ifthere 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 conditionand that corrective action should be taken in order to prevent a more serious (for exam-ple, service affecting) fault. Such a severity can be reported, for example, when the de-tected alarm condition is not currently degrading the capacity of the equipment relatedmanaged objects (MO).

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

5.3.4 Trend Indication

This parameter specifies the current severity trend of the equipment related managedobject.

5.3.5 Immediate Defense Action

The immediate defense action is performed by the BTSE software to try and solve theproblem. If there is no corresponding defense action, NA is reported.

5.3.6 Threshold Information

Actual value: lower threshold (if any)upper threshold (if any)

206 A30808-X3247-M321-1-7620


5.3.7 Proposed Repair Action

Suggested repair actions. Consult also the corresponding user manual.

5.3.8 Error Description

Detailed description of the error and its probable cause.

5.3.9 Additional Information

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

5.4 Fault Messages

5.4.1 Fault Messages at the Radio Commander

Fig. 5.1 Fault Messages at the Radio Commander

A30808-X3247-M321-1-7620 207


MMN:BTSE BS 20

5.4.2 Fault Messages at the LMT

JOB: 64

PC Time&Date: 08:51:46 13/07/2001

NE Time&Date: 1:03:22 01/01/1970

USER: SAG

SW RELEASE: 01-04-13-01-01-03-84-11

COMMAND RSULT: OPERATION COMPLETED

FAILURE EVENT REPORT:

NAME = BPORT:0

Event Type = Communication Failure Event

Event Time = 08:51:46 13/07/2001

Probable Cause = Transmitter Error

Specivic Problems = 10270 - Loss of signal

Severity = Major

Trend Indication = More Severe

Notification Identifier = 322

Proposed Repair Actions_1 = 185 - Collect infor for assistance

Proposed Repair Actions_2 = 181 - Test the addressed card

Originator = 1281

Additional Word =

H'6c61 H'316c H'7361 H'6566 H'0108

H'5f01 H'1a00 H'0d03 H'00ff H'ffff

H'ffff H'ffff H'ffff H'ffff H'ffff

Software Version = 01-01-13-01-01-01:01-04-05

END OF OUTPUT FOR JOB 64

208 A30808-X3247-M321-1-7620


5.5 BTSE Components

5.5.1 BTSE Components Overview

For a system overview of all BTSE components (modules, frames, racks and managedobjects), 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 unitsstarts with the figure zero (0). That means the first of a set of devices, modules or racksgets 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 mi-croprocessor reads a slot-ID number, supplied from the backplane by connector pinswith a fixed logical level for a particular mounting location.

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

Mounting Unit (MUT)

The mounting unit numbers indicate the installation section of the units in the rack(see Fig. 4.2). 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. Thisnumber 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 num-ber. Definition in this way is helpful for the service staff, gives better clarity and smallerlogistics for the system cabling. The following table shows the fixed assignment:

Cell no. Equipment assigned to cell no.0 ACOM 01 ACOM 12 ACOM 20 FVSWR 01 FVSWR 12 FVSWR 20 RXMUCO 0

A30808-X3247-M321-1-7620 209


MMN:BTSE BS 20

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 Data

The function “Remote Inventory” of the Siemens Basestation System performs electron-ic, non volatile storing of the complete, individual product identification data (PID) ofeach inventory object.

Modules that have their inventory data on board are called ob_RIUs (on-board RemoteInventory Units). The PID of these ob_RIUs is automatically loaded to the inventory datafile (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 RemoteInventory Units) are entered into an inventory data table (IDT) via the LMT and the offlinetool “IDF editor”. These data is stored on the CCTRL as a nob_RIU file (NOB). Supple-mented with a footer and header, the IDT can be exported and stored as an inventorydata file (IDF) for backup purposes.

In case of the replacement of a nob_RIU component, the NOB file must be updatedmanually and the backup IDF-file with the inventory data, which is stored on site, mustbe updated as well.

In case of a CCTRL replacement, the inventory data that was stored on the removedCCTRL must be rebuilt. This can be done by using the backup IDF-file.

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

The following list shows all nob_RIU components:

0 RXMUCO 1 (for diversity)1 RXMUCO 21 RXMUCO 3 (for diversity)2 RXMUCO 42 RXMUCO 5 (for diversity)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

ACDC-0/n 0 ACDC

BATTERY-0/n 0 BACKUPBATTERY

CABLEBOX-0/n 0 CABLE-BOX

DCBUNIT-0/n 0 DC-BREAKER

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

Tab. 5.2 List of nob_RIUs

210 A30808-X3247-M321-1-7620


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

DUKIT-0/n 0 DUKIT

DUPL-0/n 0 DUPL

DUSIMRA-0/n 0 DUSIMRA

FAN-0/n 0 FAN

FRABTS2-0/n 0 F:BTS2

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

HPDU-0/n 0, 2 HPDU

HYBRID-0/n 0 HYBRID

HYCOM-0/n 0 HYCOM

MKOVPT-0/n 0 MK:OVPT

MKRXFIL-0/n 0 MK:RXFIL20

MOUNTFLOOR-0/n 0 MOUNT:FLOOR

MOUNTWALL-0/n 0 MOUNT:WALL

OVPT-0/n 0 OVPT

PDB-0/n 0 PDB

RBS20-0/n 0 R:BS20

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

RXAMOD-0/n 0...3 RXAMOD

RXFIL-0/n 0...3 RXFIL

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

Functional Address Range of “n” Functional Address Type

Tab. 5.2 List of nob_RIUs

A30808-X3247-M321-1-7620 211


MMN:BTSE BS 20

5.6 Diagnostics / Test

5.6.1 General

In general the diagnosis subsystem is for testing the functionality of BTSE HW resourc-es to detect and localize hardware faults. The verification of the functionality of a new orreplaced 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 fromthe LMT.

A successful replacement of analog modules can only be verified by reactivating the BT-SE.

5.6.2 Requirements for Starting the BTSE Module Test

The module test is controlled by the LMT. It is therefore necessary that the LMT isplugged in at the plug position and that it is logged in. The principle sequence is as fol-lows:

– change the administrative state from “unlocked” to “locked”

– start the module test

– change the administrative state from “locked” to “unlocked”

The modules CCTRL, LI, CCLK 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 theBTSE is to be transferred from phase 3 to phase 2. The administrative state must thenbe 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)MANAGED-ELEMENTBSS-FUNCTIONALBTSMLOCKREQUEST BTSMNAME=BTSM:0

LOCK BTSM:NAME=BTSM:0;

5.6.2.2 Change BTSE from Phase 3 to Phase 2 (only relevant for some mod-ules)MANAGED-ELEMENTBSS-FUNCTIONALBTSMDISCBSC BTSMNAME=BTSM:0


212 A30808-X3247-M321-1-7620


5.6.2.3 Lock Suspected Module (all modules)MANAGED-ELEMENTBSS-EQUIPMENTBTSERACK<module>LOCK <module>

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

5.6.2.4 Run Test for Replaced ModuleMANAGED-ELEMENTBSS-EQUIPMENTBTSERACK<module>PERFTEST <module>

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

Explanation of the test parameters:

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

System Response

Example for Test Report

Perftest <module>:NAME=RACK:<no>/<module>:<no><no> Command============================================JOB: <no>PC Time&Date: <time> <date>NE Time&Date: <time> <date>USER: <user>COMMAND: Perftest <module>:NAME=RACK:<no>/<module>:<no>SW RELEASE: <no>COMMAND RESULT: <command result>

PERFTEST ACK BTSE:

name = BTSETEST:<no>MOT = RACK:<no>/<module>:<no>tO = BTSETEST:1


JOB: <no>PC Time&Date: <time> <date>NE Time&Date: <time> <date>

A30808-X3247-M321-1-7620 213


MMN:BTSE BS 20

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

5.6.2.5 Unlock Suspected Module (all Modules)MANAGED-ELEMENTBSS-EQUIPMENTBTSERACK<module>UNLOCK <module>

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

5.6.3 Incompatible Tests for Multiple Test Processing

The reason of Multiple Test Processing is to provide more than one test at the sametime.

However, only one test of the same processor or nonprocessor module can be execut-ed at the same time. A second test request for the same module will be rejected imme-diately, 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 nullno 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 PAcannot be tested.

USER: <user>SW RELEASE: <no>COMMAND RESULT: <command result>

Test Report:

name = BTSETEST:<no>testOutcome = <test outcome> (see below)testTermination = NormalMOT = RACK:<no>/<module>:<no>

214 A30808-X3247-M321-1-7620


A30808-X3247-M321-1-7620 215


MMN:BTSE BS 20

6 AbbreviationsACOM Antenna Combiner

ALCO Alarm and Control Board

ANT Antenna Transmitter Output

ARC Analog Radio Controller -> TRXA

BBC Baseband Controller

BBSIG Baseband Signal Processing Board

BER Bit Error Rate

BPORT BTS Port

BSC Base Station Controller

BSS Base Station Subsystem

BTS Base Transceiver Station

BTSE Base Transceiver Station Equipment

CAN Controller Area Network

CCLK Common Clock

CCTRL Core Controller

CONT Control

CRC Cyclic Redundancy Check

DCPA Direct Current Converter PA

DCTPU Direct Current Converter TPU

DRC Digital Radio Controller -> TRXD

DUKIT Duplex Combiner Kit

ESD Electrostatically Sensitive Device

ESN Electronical Serial Number

GPSU Generic Power Supply Unit

HMO Hardware-Related Managed Object

HSCX High Level Serial Communication ControllerExtended

HW Hardware

IDF Inventory Data File

IDT Inventory Data Table

LAPD Link Access Protocol on the D-Channel

LAPDLE LAPD Link Equipment

LED Light Emitting Diode

LI Link Interface

LIPA Link Interface for Primary Access

LMT Local Maintenance Terminal

MCLK Master Clock

MHU Mast Head Unit

MOT Managed Object Under Test

n no

216 A30808-X3247-M321-1-7620


NOB nob_RIUs only

nob_RIU not on-board Remote Inventory Data

O&M Operation and Maintenance

ob_RIU on-board Remote Inventory Data

OMC Operation and Maintenance Center

OS Operating System

PA Power Amplifier

PCM Pulse Code Modulation

PID Product Identification Data

PIP Primary Input Power

PS Power Supply

RAC Reset Analog Radio Controller ARC

RBBC Reset Baseband Controller BBC

RDC Reset Digital Radio Controller DRC

RLIC Reset Link Interface Controller

RXAMOD Receiver Antenna Module

RXMUCO Receiver Multicoupler

SBS Siemens Base Station

TAC Technical Assistance Center

TAD Test Adapter

TPU Transceiver and Processing Unit

TRXA Transceiver Analog

TRXD Transceiver Digital

VAM Version Attachment Mechanism

y yes

Date post:	14-Dec-2015
Category:	Documents
Upload:	sinasabikona
View:	214 times
Download:	1 times

bs20mt

Documents