Nokia Siemens Networks GSM/EDGE BSS, rel. RG20(BSS), operating documentation, issue 01
Changes
Changes in RG20(BSS)
DN0963445DN0963445 Issue 01Approval Date 2010-08-24
2 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058074e5bf
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2010. All rights reserved
f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.
The same text in German:
Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.
DN0963445DN0963445 Issue 01
3
Changes in RG20(BSS)
Id:0900d8058074e5bf
Table of ContentsThis document has 208 pages.
1 Documentation changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Overview of documentation changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Documentation changes in Nokia Siemens Networks GSM/EDGE BSS, rel
RG20(BSS), operating documentation, issue 01 . . . . . . . . . . . . . . . . . . . 81.2.1 Documentation changes in BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.1.1 New documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2.1.2 Modified documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2.1.3 Removed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2.2 Documentation changes in BTSplus . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.2.1 New documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.2.2 Modified documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.2.3 Removed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.3 Documentation changes in Flexi Multiradio BTS . . . . . . . . . . . . . . . . . . 141.2.3.1 New documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2.3.2 Modified documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2.3.3 Removed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2.4 Documentation changes in Flexi EDGE BTS. . . . . . . . . . . . . . . . . . . . . 151.2.4.1 New documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2.4.2 Modified documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2.4.3 Removed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2.5 Documentation changes in UltraSite EDGE BTS . . . . . . . . . . . . . . . . . 161.2.5.1 New documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.5.2 Modified documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.5.3 Removed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.2.6 Documentation changes in MetroSite EDGE BTS. . . . . . . . . . . . . . . . . 171.2.6.1 New documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.2.6.2 Modified documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.2.6.3 Removed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.2.7 Documentation changes in SiteWizard . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.7.1 New documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.7.2 Modified documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.7.3 Removed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.8 Documentation changes in Power Systems . . . . . . . . . . . . . . . . . . . . . 191.2.8.1 New Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.2.8.2 Modified documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.2.8.3 Removed documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2 Software changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1 Software changes in BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.1 Changes in Voice and Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1.2 Changes in Transmission and transport . . . . . . . . . . . . . . . . . . . . . . . . 202.1.3 Changes in O&M, Performance Management and Serviceability . . . . . 212.1.4 Changes in Site Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.2 Software changes in BTSplus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3 Software changes in Flexi Multiradio BTS . . . . . . . . . . . . . . . . . . . . . . . 23
4 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058074e5bf
2.4 Software changes in Flexi EDGE BTS . . . . . . . . . . . . . . . . . . . . . . . . . . 242.5 Software changes in UltraSite EDGE BTS . . . . . . . . . . . . . . . . . . . . . . . 252.6 Software changes in MetroSite EDGE BTS . . . . . . . . . . . . . . . . . . . . . . 26
3 Hardware changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1 Hardware changes in BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.1 Changes in hardware products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.1.1 Flexi BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1.1.2 BSC3i 1000/2000 and BSC3i 660. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.1.1.3 BSCi/BSC2i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.1.1.4 TCSM3i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.1.2 Changes in installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1.2.1 Flexi BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1.2.2 TCSM3i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1.3 Changes in network element hardware extensions and upgrades . . . . . 293.1.3.1 Flexi BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.1.3.2 TCSM3i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.2 Hardware changes in Flexi EDGE BTS . . . . . . . . . . . . . . . . . . . . . . . . . 32
4 Alarm changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.1 Alarm changes made in Nokia Siemens Networks GSM/EDGE BSS, rel.
RG20(BSS), operating documentation, issue 01 . . . . . . . . . . . . . . . . . . 334.1.1 Overview of alarm changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.1.2 New alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.1.3 Changed alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.1.4 Removed alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5 Counter changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315.1 Counter changes made in Nokia Siemens Networks GSM/EDGE BSS, rel
RG20(BSS), operating documentation, issue 01 . . . . . . . . . . . . . . . . . 1315.1.1 Overview of counter changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315.1.2 New counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335.1.2.1 New counters introduced by BSS20083: Inter-BSC NACC . . . . . . . . . 1335.1.2.2 New counters introduced by BSS21045: Inter System NACC . . . . . . . 1335.1.2.3 New counters introduced by BSS21355:Inter System NACC for LTE . 1335.1.2.4 New counters introduced by BSS21341: A over IP, Transcoder in BSS and
BSS30380: A over IP, Transcoder in MGW . . . . . . . . . . . . . . . . . . . . . 1335.1.2.5 New counters introduced by BSS21454: Packet Abis over IP/Ethernet 1355.1.2.6 New counters introduced by BSS21454: Packet Abis over IP/Ethernet and
BSS21440: Packet Abis over TDM added . . . . . . . . . . . . . . . . . . . . . . 1355.1.2.7 New counters introduced by BSS30395: Packet Abis Delay Measurement
1385.1.2.8 New counters introduced by BSS21309: OSC Half Rate with SAIC MS . .
1385.1.2.9 New counters introduced by BSS21271: Abis Delay Measurement (TDM,
PWE3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415.1.2.10 New counters introduced by BSS21343: DLDC Territory Procedures . 1425.1.2.11 New counters introduced by BSS21222: Energy optimised TCH Allocation
143
DN0963445DN0963445 Issue 01
5
Changes in RG20(BSS)
Id:0900d8058074e5bf
5.1.2.12 New counters introduced by BSS21392: TRX Specific Link Adaptation for DLDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5.1.2.13 New counters introduced by BSS101583 Precise RX Level Measurement143
5.1.2.14 New counters introduced by BSS101584 Precise Timing Advance Mea-surement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.1.2.15 New counters introduced by BSS101585 Precise Power Level Measure-ment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.1.2.16 New counters introduced by BSS101586 Adjacent Cell RX Level Measure-ment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.1.2.17 Other new counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1475.1.3 Changed counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485.1.3.1 Changes in counters introduced by BSS21454: Packet Abis over IP/Ether-
net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1485.1.3.2 Changes in counters introduced by BSS21341: A over IP, Transcoder in
BSS and BSS30380: A over IP, Transcoder in MGW . . . . . . . . . . . . . 1495.1.3.3 Changes in counters introduced by BSS21309: OSC Half Rate with SAIC
MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1545.1.3.4 Changes in counters introduced by BSS20958: Energy Saving Mode for
BCCH TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615.1.3.5 Changes in counters introduced by BSS21343: DLDC Territory Proce-
dures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1615.1.3.6 Other changed counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1625.1.4 Removed counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1685.1.5 Other changes between releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6 MML changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706.1 MML changes made in Nokia Siemens Networks GSM/EDGE BSS, rel.
RG20(BSS), operating documentation, issue 01 . . . . . . . . . . . . . . . . . 1706.1.1 About MML changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1706.1.2 New MMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1716.1.3 MML Changes made between S14 and S15 . . . . . . . . . . . . . . . . . . . . 1726.1.3.1 Modified MML Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1726.1.4 Deleted MML programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
7 Parameter changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058074e5bf
List of TablesTable 1 BSC network elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Table 2 New products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Table 3 New products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Table 4 Removed alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
DN0963445DN0963445 Issue 01
7
Changes in RG20(BSS) Documentation changes
Id:0900d8058076d927
1 Documentation changes
1.1 Overview of documentation changesNokia Siemens Networks GSM/EDGE BSS, rel. RG20(BSS), operating documentation is available as a browsable and downloadable NED documentation set. The documen-tation set is available in both XHTML and PDF formats, and you can browse and download single PDF documents. The documentation set is also available on DVD.
The Summary of Changes section of each PDF document lists the latest changes to that document. The release change documents list the technical changes made to the doc-uments in this release.
8 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807bc45f
1.2 Documentation changes in Nokia Siemens Networks GSM/EDGE BSS, rel RG20(BSS), operating documenta-tion, issue 01
1.2.1 Documentation changes in BSC
1.2.1.1 New documentsThe following documents are new:
Changes
• Changes in RG20(BSS) • Parameter Changes
Feature Descriptions:
• BSS21309: OSC Half Rate with SAIC MS • BSS30385: Circuit Switched Dynamic Abis Pool • BSS21222: Energy optimised TCH Allocation • BSS21343: DLDC Territory Procedures • BSS21392: TRX Specific Link Adaptation for DLDC • BSS20083: Inter-BSC NACC • BSS21341: A over IP • BSS21454: Packet Abis over IP/Ethernet/BSS21438: Packet Abis over Satel-
lite/BSS21444: Packet Abis Security/BSS21445: Packet Abis Congestion Reac-tion/BSS21439: Packet Abis Sync. ToP IEEE1588v2/BSS30450: Packet Abis Synchronous Ethernet
• BSS21440: Packet Abis over TDM /BSS21438: Packet Abis over Satel-lite/BSS21445: Packet Abis Congestion Reaction
• BSS30395: Packet Abis Delay Measurement • BSS21443: Packet TRS for UltraSite / BTSplus • BSS21271: Abis Delay Measurement (TDM, PWE3) • BSS21503: FlexiPacket Radio Connectivity • BSS21316: Flexi BTS Autoconnection • BSS20045: PCU Restart Handling • BSS21232: Automatic EDAP Reallocation in PCU • BSS21362: Fast BSS Restart • BSS21045: Inter System NACC • BSS21355: Inter System NACC for LTE
Reference
• 120 TDM/PW Abis Delay Measurement • 121 Circuit-switched Dynamic Abis Pool Measurement • 122 OSC RX Quality • 123 Packet Abis BTS measurement • 124 Packet Abis Traffic measurement • 125 Packet Abis SCTP measurement • 126 Packet Abis Delay measurement
DN0963445DN0963445 Issue 01
9
Changes in RG20(BSS)
Id:0900d805807bc45f
• 127 Packet Abis Congestion Control measurement • 128 ETP Ethernet BSC measurement • 129 ETP Ethernet TCSM Measurement • 130 AoIP Traffic BSC Measurement • 131 AoIP Traffic TCSM Measurement • 135 Precise RX Level Measurement • 136 Precise Timing Advance Measurement • 137 Precise Power Level Measurement • 138 Adjacent Cell RX Level Measurement
1.2.1.2 Modified documentsThe following documents have been updated:
System Descriptions
• BSS Description • Transport Network Solutions for BSS
Functional Area Descriptions
• Radio channel allocation • RF Power control and handover algorithm • Cell broadcast • TCSM Support in BSC • Transmission management in BSS • Radio Network Maintenance • Radio Network Recovery and State Management • BSSMAP Error handling
Feature Descriptions
• BSS21238: Merged P- & E-GSM900 • BSS21270: 105km Extended Cell for GPRS/EDGE • BSS20960: Wideband AMR and BSS21118: AMR TFO • BSS21120 : AMR Unpacking optimization • BSS21161: SDCCH and PS data channels on DFCA TRX • Antenna Hopping System Feature Description • BSS Synchronisation • BSS10016 and BSS10118: Common BCCH Control • Direct Access to Desired Layer/Band • Directed Retry in BSC • BSS20870: Double Power TRX for 2G BTS • BSS11052: Dynamic Frequency and Channel Allocation • Enhanced Coverage by Frequency Hopping • BSS10004 and BSS6071: Enhanced Speech Codecs: AMR and EFR • BSC3015: FACCH Call Set-up • BSS12158: IMSI-Based Handover • Intelligent Underlay-Overlay • PGSM900-EGSM900 BTS in BSC • Soft Channel Capacity in BSC
10 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807bc45f
• Handover Support for Coverage Enhancements • Radio Resource Pre-emption and Queuing • BSS20082: Single Antenna Interference Cancellation in BSC • BSS10046: Multi BCF Control • Intelligent Directed Retry in BSC • GPRS System Feature Description • EDGE System Feature Description • BSS10045: Dynamic Abis • BSS20094: Extended Cell for GPRS/EDGE • BSS7003 and BSS7037: HSCSD and 14.4 kbit/s Data Services in BSC • BSS20106: Packet Control Unit (PCU2) Pooling • BSS20958: Energy saving mode for BCCH TRX • BSS20012: File Based Plan Provisioning System Feature Description • BSS21353: LTE System Information • BSS10012 and BSS11114 Location Services in BSC
BSC/TCSM descriptions
• Product Description of BSC2i and BSCi High Capacity Base Station Controller • Product Description of BSC3i High Capacity Base Station Controller • Product Description of Flexi BSC • Product Description of TCSM2A and TCSM2E • Product Description of TCSM3i High Capacity Transcoder Submultiplexer
Plan and Dimension
• BTS EDGE Dimensioning • Abis EDGE Dimensioning • BSC EDGE Dimensioning • Gb EDGE Dimensioning • BSC Site IP Connectivity Guidelines • BSC Site IP Connectivity Examples • BSS Transmission Configuration
Install
• Creating and Managing BSC Hardware • PWT User Guide
Commission
• Commissioning Flexi BSC • Commissioning TCSM3i • BSS Integration
Activate
• Activating and Testing BSS10005: Reversed Hunting • Activating and Testing BSS8037: Enhanced Coverage by Frequency Hopping • Activating and Testing BSS6115: TRX Prioritisation in TCH Allocation • Activating and Testing BSS10046: Multi BCF Control in BSC • Activating and Testing BSS21270: 105km Extended Cell for GPRS/EDGE • Activating and Testing BSS20094: Extended Cell for GPRS/EDGE • Activating and Testing BSS11088: Coding Schemes CS-3 and CS-4
DN0963445DN0963445 Issue 01
11
Changes in RG20(BSS)
Id:0900d805807bc45f
• Activating and Testing BSS10083: EGPRS • Activating and Testing BSS9006: GPRS • Activating and Testing BSS11114: Lb interface to BSC • Activating and Testing BSS11134: Antenna Hopping
Maintain Hardware
• Creating and Managing BSC Hardware
Monitor and Measure
• BSC Statistics Administration • Radio Network Testing
Administer
• Dynamic Abis Pool Handling • Licence Management in BSC • Managing the BSS Transmission • Radio Network Administration • Integrated LAN Administration
Reference
• Disturbance Printouts (1000-1999) • Failure Printouts (2000-3999) • Base Station Alarms (7000-7999) • Transmission Equipment Alarms (8000-8999) • Handling Common Problem Situations in BSC • Call Related DX Causes in BSC • CI - Internal Routing States • D1 - Pseudo Wire ToP Synchronization Handling • D2 - IUA Message Interface over UDP Configuration Handling • DV - Disk Log Handling • DW - Primary Rate Access D-Channel for IUA Data Handling BSC • EA - Adjacent Cell Handling • EE - Base Station Controller Parameter Handling in BSC • EH - Handover Control Parameter Handling • EQ - Base Transceiver Station Handling in BSC • ER - Transceiver Handling • ES - Abis Interface Configuration • EU - Power Control Parameter Handling • FX - Gb Interface Handling • IS - IO Device Working States • RC - Circuit Group Handling (BSC) • TP - GSM Measurement Handling • UB - Single Radio Network Test Handling • Abis O&M Monitoring • BSC Measurement Counters Displaying Program (FOXMEA) • PCU2 Service Terminal Commands • EDGE, GPRS, and GSM Voice Key Performance Indicators • Performance Measurements
12 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807bc45f
• 1 Traffic Measurement • 2 Resource Availability Measurement • 4 Handover Measurement • 50 BSC Level Clear Code Measurement • 51 BSC Level Clear Code (PM) Measurement • 52 Underlay-Overlay Statistics Measurement • 70 Channel Finder Measurement • 72 Packet Control Unit Measurement • 76 Dynamic Abis Measurement • 77 FER Measurement • 95 GPRS Cell Re-selection Measurement • 100 DFCA Measurement • 108 DFCA SAIC Measurement • 110 PCU Utilisation Measurement • 113 Power Saving Measurement • 114 Pseudo Wire BSC Measurement • 116 Pseudo Wire TCSM Measurement • 118 Pseudo Wire Tunnel BTS Measurement • 119 TRE Ethernet Measurement • 17 TCH Observation • 21 Radio Measurement Report • 29 Drop Call Breakdown Observation • 226 Abis D-Channel Measurement • BSS Radio Network Configuration Database (BSDATA) • Logical Files • BSC-CBC Interface DX 200 • BSC-SGSN Interface Specification BSS GPRS Protocol (BSSGP) • BSC-SGSN Interface Specification Network Service Protocol (NS) • MSC-BSS Interface, Layer 3 Specification DX 200 BSC • BSS Radio Network Parameter Dictionary • PAFILE Timer and Parameter List • PRFILE and FIFILE Parameter List
1.2.1.3 Removed documentsThere are no removed documents in this release.
DN0963445DN0963445 Issue 01
13
Changes in RG20(BSS)
Id:0900d8058076d673
1.2.2 Documentation changes in BTSplus
1.2.2.1 New documentsThe following documents are new in release BRG2:
Feature Descriptions
• RG301397: Cositing with BS2xx
Install
• Installing Flexi Multiradio in BS-241 / 241 II
1.2.2.2 Modified documentsThe following documents have been updated in release BRG2:
Feature Descriptions
• BSS21469: BS2xx@ Flexi BSC product family
Integrate and Configure
• Migrating BTSplus to the Flexi BSC product family
BTSplus descriptions
• BS-240/241 product description • BS-240 II / 240 II B / 241 II / 241 II B product description • BTS module descriptions • BTS frame descriptions • BTS rack/shelter descriptions
Install
• Installing BS-241 / 241 II /24 II B
Reference
• Parameter/attribute mapping for migrating BTSplus to the Flexi BSC product family
BTSplus user guides
• Operating guidelines: LMT Evolution
Commission
• Commissioning BTSplus at the Flexi BSC product family
Hardware
• KPI guidelines for BTSplus migration to the Flexi BSC product family
1.2.2.3 Removed documentsThere are no removed documents in this release.
14 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d675
1.2.3 Documentation changes in Flexi Multiradio BTS
1.2.3.1 New documentsThere are no new documents in this release.
1.2.3.2 Modified documentsThere are no updated documents in this release.
1.2.3.3 Removed documentsThere are no removed documents in this release.
DN0963445DN0963445 Issue 01
15
Changes in RG20(BSS)
Id:0900d8058076d674
1.2.4 Documentation changes in Flexi EDGE BTS
1.2.4.1 New documentsThere are no new documents in release EX4.0.
1.2.4.2 Modified documentsThe following documents have updated for release EX4.0:
• Requirements for Installation and Operation • Creating Stack, Wall and Pole Configurations • Installing Flexi Cabinet for Indoor (FCIA) • Creating FCIA Configurations • Installing Flexi Cabinet for Outdoor (FCOA) • Creating FCOA Configurations • Installing Nokia Flexi EDGE BTS Optional Items • Installing Nokia Flexi EDGE BTS Modules in Citytalk Cabinet • Creating Nokia Flexi EDGE BTS Feederless Site Configurations • Expanding Nokia Flexi EDGE BTS • Maintaining Nokia Flexi EDGE BTS Modules • Maintaining Flexi Cabinet for Indoor (FCIA) • Maintaining Flexi Cabinet for Outdoor (FCOA) • Nokia Flexi EDGE BTS Product Description • Nokia Flexi EDGE BTS System Module (ESMA) Description • Nokia Flexi EDGE BTS Dual TRX Module (EXxx) Description • Optional Items Description • Nokia Flexi EDGE BTS Co-siting • Warnings and Cautions
1.2.4.3 Removed documentsThere are no removed documents in release EX4.0.
16 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d678
1.2.5 Documentation changes in UltraSite EDGE BTS
1.2.5.1 New documentsThere are no new documents in release CX8.
1.2.5.2 Modified documentsThe following documents are updated for UltraSite EDGE BTS for release CX8:
• Feature Descriptions for UltraSite EDGE BTS • Trouble Management of UltraSite EDGE BTS
1.2.5.3 Removed documentsThere are no removed documents in release CX8.
DN0963445DN0963445 Issue 01
17
Changes in RG20(BSS)
Id:0900d8058076daf9
1.2.6 Documentation changes in MetroSite EDGE BTS
1.2.6.1 New documentsThere are no new documents in this release.
1.2.6.2 Modified documentsThere are no updated documents in this release.
1.2.6.3 Removed documentsThere are no removed documents in this release.
18 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d677
1.2.7 Documentation changes in SiteWizard
1.2.7.1 New documentsThere are no new documents in this release.
1.2.7.2 Modified documentsThere are no updated documents in this release.
1.2.7.3 Removed documentsThere are no removed documents in this release.
DN0963445DN0963445 Issue 01
19
Changes in RG20(BSS)
Id:0900d8058076d676
1.2.8 Documentation changes in Power Systems
1.2.8.1 New DocumentsThe following documents are new:
Power Systems user guides
• SiteStar Cabinet CPI • SiteStar 19-inch rack CPI • SiteStar Alarm Connection
1.2.8.2 Modified documentsThere are no updated documents in this release.
1.2.8.3 Removed documentsThere are no removed documents in this release.
20 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807bc463
Software changes
2 Software changes
2.1 Software changes in BSC
2.1.1 Changes in Voice and Data
New features
2.1.2 Changes in Transmission and transport
New features
New feature Location in documentation
BSS21309: OSC Half Rate with SAIC MS
BSS21309: OSC Half Rate with SAIC MS
BSS30385: Circuit Switched Dynamic Abis Pool
BSS30385: Circuit Switched Dynamic Abis Pool
BSS21222: Energy optimised TCH Allocation
BSS21222:Energy optimised TCH Allocation
BSS21343: DLDC Territory Proce-dures
BSS21343: DLDC Territory Procedures
BSS21392: TRX Specific Link Adapta-tion for DLDC
BSS21392: TRX Specific Link Adaptation for DLDC
BSS20083: Inter-BSC NACC BSS20083: Inter-BSC NACC
BSS21045: Inter System NACC BSS21045: Inter System NACC
BSS21355: Inter System NACC for LTE
BSS21355: Inter System NACC for LTE
New feature Location in documentation
BSS21341: A over IP, Transcoder in BSS
BSS21341: A over IP
BSS30380: A over IP, Transcoder in MGW
BSS21341: A over IP
BSS21454: Packet Abis over IP/Ether-net
BSS21454: Packet Abis over IP/Ether-net/BSS21438: Packet Abis over Satel-lite/BSS21444: Packet Abis Security/BSS21445: Packet Abis Congestion Reaction/BSS21439: Packet Abis Sync. ToP IEEE1588v2/BSS30450: Packet Abis Syn-chronous Ethernet
BSS21440: Packet Abis over TDM BSS21440: Packet Abis over TDM/BSS21438: Packet Abis over Satellite/BSS21445: Packet Abis Congestion Reaction
BSS30395: Packet Abis Delay mea-surement
BSS30395: Packet Abis Delay measurement
DN0963445DN0963445 Issue 01
21
Changes in RG20(BSS) Software changes
Id:0900d805807bc463
2.1.3 Changes in O&M, Performance Management and Serviceability
New features
2.1.4 Changes in Site Solutions
New features
BSS21443: Packet TRS for UltraSite / BTSplus
BSS21443: Packet TRS for UltraSite / BTSplus
BSS21271: Abis Delay Measurement (TDM, PWE3)
BSS21271: Abis Delay Measurement (TDM, PWE3)
BSS21503: FlexiPacket Radio Con-nectivity
BSS21503: FlexiPacket Radio Connectivity
New feature Location in documentation
New feature Location in documentation
BSS21316: Flexi BTS Autoconnection BSS21316: Flexi BTS Autoconnection
BSS20045: PCU Restart Handling BSS20045: PCU Restart Handling
BSS21232: Automatic EDAP Reallo-cation in PCU
BSS21232: Automatic EDAP Reallocation in PCU
BSS21362: Fast BSS Restart BSS21362: Fast BSS Restart
New feature Location in documentation
RG301397: Cositing with BS2xx RG301397: Cositing with BS2xx
22 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d80580772375
2.2 Software changes in BTSplusThis description lists the most significant developments in the software in release BRG2.
New features
New feature Location in documentation
BSS21362: Fast BSS Restart BSS21362: Fast BSS Restart
RG301397: Cositing with BS2xx RG301397: Cositing with BS2xx
BSS20958: Energy saving mode for BCCH TRX
BSS20958: Energy saving mode for BCCH TRX
BSS21157: Integrated IP card for BSC and TCSM
BSS21443: Packet TRS for Ultra-Site/BTSplus
BSS21443: Packet TRS for Ultra Site/BTSplus
DN0963445DN0963445 Issue 01
23
Changes in RG20(BSS)
Id:0900d80580772378
2.3 Software changes in Flexi Multiradio BTSNo Changes.
24 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d80580772377
2.4 Software changes in Flexi EDGE BTSThis description lists the most significant developments in software in release EX4.0
New features
New feature Location in documentation
BSS21309: OSC Half Rate with SAIC MS
BSS21309: OSC Half Rate with SAIC MS
BSS30385: Circuit Switched Dynamic Abis Pool
BSS30385: Circuit Switched Dynamic Abis Pool
BSS21454: Packet Abis over IP/Ether-net
BSS21454: Packet Abis over IP/Ether-net/BSS21438: Packet Abis over Satel-lite/BSS21444: Packet Abis Security/BSS21445: Packet Abis Congestion Reaction/BSS21439: Packet Abis Sync. ToP IEEE1588v2/BSS30450: Packet Abis Syn-chronous Ethernet
BSS21440: Packet Abis over TDM BSS21440: Packet Abis over TDM /BSS21438: Packet Abis over Satel-lite/BSS21445: Packet Abis Congestion Reaction
BSS30395: Packet Abis Delay mea-surement
BSS30395: Packet Abis Delay measurement
BSS21271: Abis Delay Measurement (TDM, PWE3)
BSS21271: Abis Delay Measurement (TDM, PWE3)
BSS21316: Flexi BTS Autoconnection BSS21316: Flexi BTS Autoconnection
BSS21362: Fast BSS Restart BSS21362: Fast BSS Restart
DN0963445DN0963445 Issue 01
25
Changes in RG20(BSS)
Id:0900d8058077237a
2.5 Software changes in UltraSite EDGE BTSThis description lists the most significant developments in software in release CX8
New features
New feature Location in documentation
BSS21362: Fast BSS Restart BSS21362: Fast BSS Restart
BSS21443: Packet TRS for UltraSite / BTSplus
BSS21443: Packet TRS for UltraSite / BTSplus
26 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d80580772379
2.6 Software changes in MetroSite EDGE BTSNo changes
DN0963445DN0963445 Issue 01
27
Changes in RG20(BSS) Hardware changes
Id:0900d80580791e48
3 Hardware changes
3.1 Hardware changes in BSC
3.1.1 Changes in hardware productsIn S15 first deliveries, the Flexi BSC is used. Both the first delivery Flexi BSC and the upgraded Flexi BSC can be used as the BSC-part in the TCSM3i for combined BSC/TCSM installation option.
The terminology concerning BSC network elements has been revised. M92 mechanic-based BSCs are referred to as BSCi/BSC2i, and M98 mechanic-based BSCs as Flexi BSC product family. The terms BSC, BSCi, BSC2i, and Flexi BSC are explained in the following table.
The terminology concerning the cabling cabinets has also been revised. The following three cabling cabinet options are available:
• Cabling cabinet, 2 PCMs / cable (connector panels CPETS-G and CPETS-H) • Cabling cabinet, 2 PCMs / cable (connector panels CPETS-E and CPETS-F) • Cabling cabinet, coaxial PCMs (connector panels CPETC-E and CPETC-F)
3.1.1.1 Flexi BSC
New productsA new member of Flexi BSC is introduced to the Flexi BSC product family on S15 level, namely the 4200 TRX Flexi BSC. The Flexi BSC is the latest step in the evolution of Nokia Siemens Networks Base Station Controller.
The Flexi BSC consists of existing and new hardware products. The most important new products are shown in the following table.
BSC = Base Station Controller, a general term for all BSC network elements
General name Product name Explanation
BSCi/BSC2i BSCi High capacity (upgraded) version of the first generation DX 200 BSC (BSCE)
BSC2i High capacity version of the second gener-ation DX 200 BSC2
Flexi BSC product family
BSC3i 660 660 TRX one cabinet configuration, upgradable to Flexi BSC (prior to S12)
BSC3i 1000/2000 1000 TRX one-cabinet or 2000 TRX two-cabinet configuration, upgradable to Flexi BSC (S12 onwards)
Flexi BSC 3000 TRX one-cabinet configuration (S14)
4200 TRX one-cabinet configuration (S15)
Table 1 BSC network elements
28 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d80580791e48
Hardware changes
3.1.1.2 BSC3i 1000/2000 and BSC3i 660
Changed productsMandatory hardware requirements for the minimum memory capacity of CPU units of M98 mechanics BSC3i 1000/2000 and BSC3i 660 is 512 MB in BCSU and 1 GB in MCMU and OMU.
3.1.1.3 BSCi/BSC2i
Changed productsMandatory hardware requirement for the minimum memory capacity of CPU units in computer units of M92 mechanics high capacity BSCi and BSC2i is 512 MB in BCSU, MCMU and OMU.
3.1.1.4 TCSM3i
New products
New Description Location in documentation
Processor
CP1D-A Central Processor Unit For more information, see Functional unit descriptions for the Flexi BSC in Engineer-ing for Flexi BSC
Plug-in units
ETS2 Exchange Terminal for 2 x STM-1/OC-3
For more information, see Functional unit descriptions for the Flexi BSC in Engineer-ing for Flexi BSC
ETP Exchange Terminal for Packet Trans-port
For more information, see Functional unit descriptions for the Flexi BSC in Engineer-ing for Flexi BSC
ETP-A Exchange Terminal for Packet Trans-port over A-interface
For more information, see Functional unit descriptions for the Flexi BSC in Engineer-ing for Flexi BSC
Cabinets
IC209-C It is similar to the IC209-A with the exception of having three fan trays.
For more information, see Engineering for Flexi BSC
Table 2 New products
New Description Location in documentation
Cartridges
Table 3 New products
DN0963445DN0963445 Issue 01
29
Changes in RG20(BSS) Hardware changes
Id:0900d80580791e48
3.1.2 Changes in installation
3.1.2.1 Flexi BSCA new Flexi BSC release is introduced in S15. It is based on the S14 Flexi BSC and supports all existing functionalities and their implementation principles. The new IC209-C cabinet is used in new delivery S15 Flexi BSC and also in future S14 Flexi BSC instal-lations.
3.1.2.2 TCSM3iIn combined BSC/TCSM installation option, both first-delivery Flexi BSC and upgraded Flexi BSC can be used as the BSC-part.
3.1.3 Changes in network element hardware extensions and upgrades
3.1.3.1 Flexi BSC
New extensions and upgradesThe S15 new delivery Flexi BSC cabinet is based on an indoor, ventilated, 5-shelf cabinet variant IC209-C with Fan Trays FTRB-A.
Cabling cabinets
The following three cabling cabinet options are available:
• Cabling cabinet, 2 PCMs / cable - CPETS-G and CPETS-H connector panels are in use
• Cabling cabinet, 1 PCM / cable - CPETS-E and CPETS-F connector panels are in use
TC1C-A 1/1 shelf Transcoder Cartridge For more information, see Engi-neering for TCSM3i
Plug-in units
ETP-A Exchange Terminal for Packet Transport over A interface For more information, see Engi-neering for TCSM3i
Connector modules
RCOM-B Connector Module for ETP-A For more information, see Engi-neering for TCSM3i
RCM16 Connector Module for ET16 For more information, see Engi-neering for TCSM3i
Terminators and setting modules
TRMSB SBUS Termination Connector For more information, see Engi-neering for TCSM3i
TRMBTB Timing Bus Termination Connector For more information, see Engi-neering for TCSM3i
New Description Location in documentation
Table 3 New products (Cont.)
30 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d80580791e48
Hardware changes
• Cabling cabinet, coaxial PCMs - CPETC-E and CPETC-F connector panels are in use
Note that there is an additional small CPETx connector panel installed with a RACP2 roof adapter at the cabling cabinet top in S15 Flexi BSC first deliveries.
Additionally, in combined BSC/TCSM installation deliveries, one or two or three TCSA cabinets (cabinet type variant TCSA set + TCSA0-A location set + TCSA-06 cabinet upgrade set per TCSA cabinet) is / are attached to BSCC cabinet.
S14 Flexi BSC upgrade to S15 Flexi BSC
BSC3i 1000/2000 and BSC3i 660 upgrade to Flexi BSC
BSC3i 1000/2000 and BSC3i 660 upgrade to Flexi BSC can be implemented in the fol-lowing ways:
• First-delivery BSC3i 1000 to Flexi BSC upgrade • First-delivery BSC3i 2000 (2 cabinets) to Flexi BSC (1 cabinet) upgrade • First-delivery BSC3i 2000 (2 cabinets) to Flexi BSC (2 cabinets) upgrade • BSC3i 2000 (BSC3i 1000 part upgraded from BSC3i 660; 2 cabinets) to Flexi BSC
(1 cabinet) upgrade • BSC3i 2000 (BSC3i 1000 part upgraded from BSC3i 660; 2 cabinets) to Flexi BSC
(2 cabinets) upgrade • BSC3i 660 (with GSW1KB) to Flexi BSC upgrade • BSC3i 660 (with GSWB) to Flexi BSC upgrade
ETS2 options
The following ETS2 option is available for Flexi BSC: ETS2 equipment protection
ETIP1-A options
The following ETIP1-A options are available for Flexi BSC:
• ETIP1-A Exchange Terminal for IP Transmission • ETIP1-A equipment protection
ETP/ETP-A options
The following ETP/ETP-A options are available for Flexi BSC:
• ETP/ETP-A transmission protection • ETP/ETP-A equipment protection
3.1.3.2 TCSM3i
New extensions and upgrades in TCSM3i for stand-alone installation optionCabiling cabinet for Double Density
Cabling cabinet for Traditional PCMs
Cabling cabinet for Coaxial PCMs
Rear Connetction Module Set
ETIP1-A options
The following ETIP1-A options are available for stand-alone installation option:
• ETIP1-A for Ater-interface with equipment protection • ETIP1-A for A-interface • ETIP1-A equipment protection for A-interface
DN0963445DN0963445 Issue 01
31
Changes in RG20(BSS) Hardware changes
Id:0900d80580791e48
ETP-A options
The following ETP-A option is available for stand-alone installation option:
• ETP-A equipment protection
New extensions and upgrades in TCSM3i for combined BSC/TCSM installation optionCabinet upgrade
The TCSA cabinet upgrade for combined BSC/TCSM is updated to support also Flexi BSC as the BSC-part.
ETS2 options
The following ETS2 option is available for combined BSC/TCSM installation option: ETS2 equipment protection for A-interface
ETIP1-A options
The following ETIP1-A option is available for combined BSC/TCSM installation option:
• ETIP1-A equipment protection for A-interface
ETP-A options
The following ETP-A option is available for combined BSC/TCSM installation option:
• ETP-A equipment protection for A -interface
32 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058079b18a
3.2 Hardware changes in Flexi EDGE BTSAll the Flexi EDGE BTS documents have been modified for fault corrections and updated for the following:
• PASI card implementation
DN0963445DN0963445 Issue 01
33
Changes in RG20(BSS) Alarm changes
Id:0900d80580791e54
4 Alarm changes
4.1 Alarm changes made in Nokia Siemens Networks GSM/EDGE BSS, rel. RG20(BSS), operating documenta-tion, issue 01
4.1.1 Overview of alarm changesThe changes in alarms that have been made between the S14 and S15 BSC sofware releases are described here. Minor changes that do not have any effect on the function-ality of the alarm are not included.
The change descriptions of individual alarms are divided into three groups: alarm docu-mentation, printout changes, and alarm parameters. The possible statements are:
• Alarm text changed • Meaning improved • Meaning changed • Supplementary Information Field (SIF) structure changed • SIF values updated • SIF meaning updated • Instructions improved • Operating sequence improved • Cancelling updated • Alarm parameters changed
The new and changed alarms are listed by their alarm manual category. In addition, the new alarms are listed with their Meaning field and the changed alarms are listed with the supplementary information fields of the original and the updated alarm.
The alarms are listed in the following alarm manuals, under the Reference and Trouble-shoot\BSC/TCSM headings:
• Notices (0–999) • Disturbance Printouts (1000–1999) • Failure Printouts (2000–3999) • Diagnosis Reports (3700–3999) • Base Station Alarms (7000–7999) • Transmission Equipment Alarms (8000–8999)
34 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d67a
4.1.2 New alarmsFor more information on alarm changes in S15, see Overview of alarm changes.
New alarms in Disturbance Printouts (1000-1999)
New alarms in Failure Printouts (2000-3999)
Number Name Meaning
1348 ETP SPARE UNIT WARMUP FAILURE
The warm-up of the spare ETPT, ETPE or ETPC unit fails during controlled switchover. The reason may be a fault in the active or in the passive unit. The alarm is issued from both units.
Number Name Meaning
2885 SCTP CONNECTION TO PRIMARY UNIT FROM H.248 UNIT POOL IS LOST
SCTP connection to the primary unit inside a H.248 unit pool has been lost. It endangers the possible non-call related signaling and so can cause inconsistent state between MSS and MGW.
2886 NO SCTP CONN TO PRIMARY OR SECOND-ARY UNIT FOR H.248 SIGNALING
There is no SCTP connection to either primary or secondary unit inside an H.248 unit pool. Non-call related H.248 signaling is not possible and so it can cause inconsistent state between MSS and MGW.
2887 FAST BSS RESTART FAILED
The BSC restart without radio network restart has failed.
2898 DISCREPANCY BETWEEN ACTUAL HW AND HW CONFIGURA-TION DATA
This general alarm indicates that actual HW (information read from shelf SDR repository) and corresponding HW configuration data in equipment database mismatch, for example Automatic comparison of existing HW and HW configuration data finds one or more conflicts. An alarm is set during the comparison process if there is a conflict. Supplementary information fields identify the reason of the conflict.
2949 FAST BSS RESTART RNW UNBLOCKING STARTED
TRX deblocking phase of the radio network is ongoing after BSC restart.
3515 ETP ETHERNET INTER-FACE FAILURE
The Ethernet device is faulty or the Ethernet cable is discon-nected. IP packets cannot be sent to network or received from network through this interface.
3523 PCU ETP SERIAL LINK FAILURE
Serial link between packet control unit (PCU) and Exchange Terminal for Packet Transport (ETP) has failed. Cells connected to the PCU have lost General Packet Radio Service.
3524 PCU ETP ETHERNET LINK FAILURE
Ethernet link between packet control unit (PCU) and Exchange Terminal for Packet Transport (ETP) has failed. Cells connected to the PCU have lost General Packet Radio Service.
3525 FAILURE IN UPDATING CONFIGURATION PARAMETERS TO ETP
A failure has occurred in updating the BCF or BSC specific param-eters to Exchange Terminal for Packet Transport (ETP).
3536 CIRCUIT SWITCHED DYNAMIC ABIS POOL FAILURE
CSDAP has encountered a malfunction and it has been taken out of use for a penalty period. BSC sets penalty for a certain CSDAP in case of consecutive remote transcoder failures and hunting error(s).
DN0963445DN0963445 Issue 01
35
Changes in RG20(BSS)
Id:0900d8058076d67a
New alarms in Base Station Alarms (7000-7999)
3537 ETP OVERLOAD CON-DITION
A DSP or Octeon core of the ETPx is highly overloaded. Over-loaded ETPx has taken automatic recovery actions.
3541 ABNORMAL A INTER-FACE IP RES RELEASE
The BSC sets this alarm if a call is released from the A interface because of a RESET IP RECOURCE message, received from the MSC.
3542 ETPC U-PLANE IP ADDRESS ENQ FAILURE
BSC sets this alarm if ETPC IP address enquiry from ETPC fails after ETPSIG-c interface is configured.
3546 FAILURE IN UPDATING CONFIGURATION PARAMETERS TO ETPAC
A failure has occurred in updating the BSC or BCF specific param-eters to Exchange Terminal for Packet Transport (ETP).
3571 PROTECTING ETP CONFIGURATION FAILED
A failure has occurred in updating the BCF or BSC specific param-eters to protecting Exchange Terminal for Packet Transport (ETP).
Number Name Meaning
Number Name Meaning
7623 BCF SHARED RADIO MODULE SW IS UPDATED IN BCF
A shared Radio Module SW is updating and WDCMA is SW master. Radio Module(s) has gone offline.
7624 CS U-PLANE CONNEC-TION FAILURE
Packet Abis BTS has detected that 3 consecutive dummy packets are lost in CS U-plane. BSC blocks the base station.
7625 PS U-PLANE CONNEC-TION FAILURE
Packet Abis BTS has detected that 3 consecutive dummy packets are lost in PS U-plane. BSC disables GPRS use of TRXs under the BTS by sending SYS INFOs with GPRS disabled information via BTS to mobile stations.
7785 BCF UNBLOCKED WITHOUT BCF RESTART
The alarm indicates that the TRX deblocking phase of the BCF is completed and BCF is restored to normal functional state after BSC restart.
7790 CONFLICTING BTS REGISTRATION ATTEMPT SEEN
BTS registration is seen on BSC but could not been solved because of conflicting OMUSIGs of BCFs.
7791 NO SCF FILE FOR THE BTS IN BSC
BTS has sent requesting message to BSC but no (activated) SCF exists in BSC. BSC has delivered the request to NetAct.
7792 SCF FILE DOWNLOAD TO THE BTS FAILED
BSC has started SCF file download to BTS but download fails.
7793 ORTHOGONAL SUB CHANNEL ACTIVATION FAILURE
Several consecutive OSC multiplexing attempts have failed due to channel activation failure in a TCH.
The BSC has interrupted OSC multiplexing activity in the TRX. Failures due to CSDAP problems excluded.
7798 HDLC PCM FAILURE The alarm concerns a PCM containing BCF links.
The radio network objects whose Abis HDLC links are part of this particular PCM are not functioning. Significance of this alarm depends on the number and nature of Abis HDLC links connected to this PCM.
36 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d67a
New alarms in Transmission Equipment Alarms (8000-8999)
7799 HDLC LINK FAILURE This BCF-specific alarm is active, when BCF is in unlocked state and one or more Abis HDLC link(s) of the BCF is faulted.
Number Name Meaning
Number Name Meaning
8283 LICENCE FOR IP SECURITY IS NOT AVAILABLE
The feature cannot be activated without a licence. This alarm affects the provided services.
8284 TRAFFIC SHAPING MIS-CONFIGURATION
Traffic shaping misconfigured. BTS-internal traffic shaping disabled but Abis traffic shaping is enabled or CIR value of Abis traffic shaping is smaller than CIR value of the BTS-internal uplink traffic shaping.
8285 LICENCE FOR TIMING OVER PACKET IS NOT AVAILABLE
The feature cannot be activated without a licence. This alarm affects the provided services.
8286 LICENCE FOR SYN-CHRONOUS ETHERNET IS NOT AVAILABLE
The feature cannot be activated without a licence. This alarm affects the provided services.
8287 CLOCK RECOVERY IN PROGRESS
BTS Timing over Packet Slave is running clock recovery algorithm and clock synchronisation is not yet complete.
8288 FAULT IN CONNECTION TO CLOCK MASTER
Timing over Packet master is not reachable or unable to provide required synchronisation messages.
8289 SSM HAS LOST TRACE-ABILITY TO PRC CLOCK SOURCE
Invalid clock quality level received.
8290 LICENCE FOR PACKET TRS E1/T1 IS NOT AVAILABLE
The feature cannot be activated without a licence. This alarm affects the provided services.
8291 PMTU BTS TO BSC LESS THAN CONFI-GRUED MTU
Path MTU (PMTU) to BSC has been determined by BTS to be less than the configured MTU value.
8292 PMTU BTS TO SECURITY GATEWAY LESS THAN CONFIG-URED MTU
Path MTU (PMTU) to Security Gateway has been determined by BTS to be less than the configured MTU value.
DN0963445DN0963445 Issue 01
37
Changes in RG20(BSS)
Id:0900d8058076d66f
4.1.3 Changed alarmsFor more information on alarm changes in S14, see Overview of alarm changes.
Changed alarms in Disturbance Printouts (1000-1999)
1182 PREPROCESSOR UNIT RESTARTED
Change description: Meaning improved, SIF structure added
Meaning in S14 Meaning in S15
A preprocessor has restarted spontaneously. If the pre-processor is equipped into) a unit which working state is WO-EX, the restart causes disturbance to the function of the unit.
A preprocessor has restarted spontaneously or executed by the supervision program block due to fault. If the preprocessor is equipped into a unit which working state is WO-EX, the restart causes disturbance to the function of the unit.
SIF structure in S14. SIF structure in S15
1 type of the restarted preprocessor plug-in unit
2 index of the restarted preprocessor plug-in unit
1 type of the restarted preprocessor plug-in unit
2 index of the restarted preprocessor plug-in unit
RESET_INITIATOR
Reset initiator
00 spontaneous, not executed by the supervision
01 executed by the supervision program block due to fault
NR_OF_RESTARTS
number of restarts
Support rules in S14 Support rules in S15
Supporting_amount (Centralized part) is 16
Supporting_amount (Distributed part) is 16
Supporting_amount (Centralized part) is 4
Supporting_amount (Distributed part) is 4
1340 HOTLINK FAILURE
Change description: SIF values updated
SIF structure in S14 SIF structure in S15
IF_STATUS: the exact error code of the HOTLink test. Possible reasons are:
0040 HOTLink sfp module unplugged
0080 HOTLink fault
0100 HOTLink CRC transmission fault
IF_STATUS: the exact error code of the HOTLink test. Possible reasons are:
0040 HOTLink sfp module unplugged
0080 HOTLink fault
0100 HOTLink CRC transmission fault
0200 Hotlink parity error
0400 Hotlink clock error
1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED
Change description: SIF values updated
SIF structure in S14 SIF structure in S15
38 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Changed alarms in Failure Printouts (2000-3999)
COUNTER
The security reporting counter that has reached its critical limit:
02 - counter for unauthorised users of service terminal
04 - counter for unauthorised users of the network
05 - counter for use of network: unauthorised commands
07 - counter for unauthorised MML users
08 - counter for unauthorised MML commands
10 - counter for unsuccessful saves in MML log file
11 - counter for unsuccessful MML command checks
12 - counter for unsuccessful subscriber identifications
13 - counter for unidentified IMSI numbers
14 - counter for IMEI IDs on black list
15 - counter for unidentified IMEI IDs
COUNTER
The security reporting counter that has reached its critical limit:
02 - counter for unauthorised users of service terminal
04 - counter for unauthorised users of the network
05 - counter for use of network: unauthorised commands
07 - counter for unauthorised MML users
08 - counter for unauthorised MML commands
10 - counter for unsuccessful saves in MML log file
11 - counter for unsuccessful MML command checks
12 - counter for unsuccessful subscriber identifications
13 - counter for unidentified IMSI numbers
14 - counter for IMEI IDs on black list
15 - counter for unidentified IMEI IDs
16 - counter for IMEI IDs in a grey list
17 - counter for unsuccessful saves in service terminal log file
18 - counter for SSH sessions
19 - counter for unauthorised SSH sessions
1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED
2477 GLOBAL RESET MESSAGE RECEIVED
Change description: SIF structure changed
SIF structure in S14 SIF structure in S15
1 signalling point code of the MSC 1 signalling point code of the MSC
2 A-Interface Reset Selector type - TDM or IP
2794 HW BLOCK FAILURE IN PLUG-IN UNIT
Change description: SIF values updated
SIF structure in S14 SIF structure in S15
DN0963445DN0963445 Issue 01
39
Changes in RG20(BSS)
Id:0900d8058076d66f
HW_STATUS: the exact error code of the plug-in unit test. Simultaneous reasons are possible to appear. Possible reasons are:
0001 Loss of 8M clock
0002 Loss of 8k clock
0004 Overheat.
0008 Clock synthesizer: Output clock squelch
0010 Clock synthesizer: DPLL A loss of lock
0020 Clock synthesizer: DPLL B loss of lock
0040 Clock synthesizer: External VCXO clock loss
0080 Clock synthesizer: Input clock loss
0100 Synchronization Transmission Block failure
0200 Switchover logic / interconnecting backplane cable fault
0400 Memory test failure in unit computer
0800 Timing over Packet Block failure
1000 Ethernet PHY Block failure
2000 LAPD failure
4000 Primary flash image failure
8000 GSW loop test failure for ET
HW_STATUS: the exact error code of the plug-in unit test. Simultaneous reasons are possible to appear. Possible reasons are:
0001 Loss of 8M clock
0002 Loss of 8k clock
0004 Overheat.
0008 Clock synthesizer: Output clock squelch
0010 Clock synthesizer: DPLL A loss of lock
0020 Clock synthesizer: DPLL B loss of lock
0040 Clock synthesizer: External VCXO clock loss
0080 Clock synthesizer: Input clock loss
0100 Synchronization Transmission Block failure
0200 Switchover logic / interconnecting backplane cable fault
0400 Memory test failure in unit computer
0800 Timing over Packet Block failure
1000 Ethernet PHY Block failure
2000 LAPD failure
4000 Primary flash image failure
8000 GSW loop test failure for ET
8001 DSP Core Failure
8002 Ethernet Switch Failure
8003 FE-FPGA Failure
8004 PCM-MUX FPGA Failure
8005 Mount failure from Flash Bank 0
8006 Mount failure from Flash Bank 1
8007 Unmount failure in Flash Bank 0
8008 Unmount failure in Flash Bank 1
2794 HW BLOCK FAILURE IN PLUG-IN UNIT
2948 RADIO NETWORK INITIALIZATION
Change description: Meaning improved
Meaning in S14 Meaning in S15
BSC radio network has restarted due to the restart of the entire BSC or the restart of the active MCMU
BTS sites have been restarted due to the restart of the entire BSC or the restart of the active MCMU
3164 PCU PROCESSOR OVERLOAD
Change description: Instructions improved
Instructions in S14 Instructions in S15
40 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Measures the peak number of radio time slots (Abis channels) in GPRS or EGPRS use within a measure-ment period for a BTS. The total number of GPRS and EGPRS channels in a PCU is the sum of counter 002063 values of all the BTSs served by the PCU.
Measures the peak number of radio time slots in GPRS or EGPRS use within a measurement period for a BTS. The total number of GPRS and EGPRS channels in a PCU is the sum of counter 002063 values of all the BTSs served by the PCU.
3164 PCU PROCESSOR OVERLOAD
3274 NACC FAILURE
Change description: SIF structure changed
SIF structure in S14 SIF structure in S15
PCU_BCSU_LOG_ADDthe logical address of the BCSU where the PCU is located.PCU_INDEXthe PIU index of the PCU
PCU_BCSU_LOG_ADDthe logical address of the BCSU where the PCU is located. This field is 0xFFFF, in case of mcPCU.PCU_INDEXthe PIU index of the PCU. This field is 0xFF, in case of mcPCU
3293 SCTP PRIMARY PATH NOT AVAILABLE
Change description: SIF structure changed, Alarm parameters added
SIF structure in S14 SIF structure in S15
DN0963445DN0963445 Issue 01
41
Changes in RG20(BSS)
Id:0900d8058076d66f
PPI
SCTP Payload Protocol Identifier
1 - IUA [RFC3057]
2 - M2UA [RFC3331]
3 - M3UA [RFC3332]
4 - SUA [RFC2960]
5 - M2PA [RFC2960]
6 - V5UA [RFC2960]
7 - H.248 [H.248]
8 - BICC/Q.2150.3 [Q.1902.1/Q.2150.3]
9 - TALI [RFC3094]
10 - DUA <draft-ietf-sigtran-dua-03.txt> [Ong]
11 - ASAP <draft-ietf-rserpool-asap-03.txt> [Ong]
12 - ENRP <draft-ietf-rserpool-enrp-03.txt> [Ong]
13 - H.323 [H.323]
14 - Q.IPC/Q.2150.3 [Q.2631.1/Q.2150.3]
254 - IWF
DATA_1
M3UA:
the association set to which the association belongs
H248:
MGW index in MSS.
Virtual MGW index in MGW
IWF:IWF connection priority
DATA_2
M3UA:index of the association inside the association set. The value is between 0 and 31
H248:index of the controlling MSS data record in virtual MGW data in MGW. The value is between 0 and 2. 0xFFFF if not H.248 connection in MGW
IWF:no relevant data. The value is always 0xFFFF
PPI
SCTP Payload Protocol Identifier
0 - SGsAP [3GPP TS 29.118]
1 - IUA [RFC3057]
2 - M2UA [RFC3331]
3 - M3UA [RFC3332]
4 - SUA [RFC2960]
5 - M2PA [RFC2960]
6 - V5UA [RFC2960]
7 - H.248 [H.248]
8 - BICC/Q.2150.3 [Q.1902.1/Q.2150.3]
9 - TALI [RFC3094]
10 - DUA <draft-ietf-sigtran-dua-03.txt> [Ong]
11 - ASAP <draft-ietf-rserpool-asap-03.txt> [Ong]
12 - ENRP <draft-ietf-rserpool-enrp-03.txt> [Ong]
13 - H.323 [H.323]
14 - Q.IPC/Q.2150.3 [Q.2631.1/Q.2150.3]
254 - IWF
DATA_1
M3UA:
the association set to which the association belongs
H248:MGW index in MSS. Virtual MGW index in MGW
IWF:IWF connection priority
SGsAP:MME index in MSS
DATA_2
M3UA:index of the association inside the association set. The value is between 0 and 31
H248:index of the controlling MSS data record in virtual MGW data in MGW. The value is between 0 and 2. 0xFFFF if not H.248 connection in MGW
IWF:no relevant data. The value is always 0xFFFF
SGsAP:
SCTP index in MSS
Alarm parameter in S14 Alarm parameter in S15
Used_in_units = CCSU, SIGU, CM, CMM, MCMU, BCSU, GSU;
Used_in_units = CCSU, SIGU, CM, CMM, MCMU, BCSU, GSU, BSU;
3293 SCTP PRIMARY PATH NOT AVAILABLE
3379 SCTP PATH FAILURE
Change description: Meaning improved, SIF structure added, Instructions improved
Meaning in S14 Meaning in S15
42 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Two paths to each SCTP association are normally created in the SCTP association establishment. If the primary path fails, then the traffic is automatically trans-ferred via a secondary path and traffic is not affected. If the secondary path fails, then the traffic is transferred via the primary path normally and only the redundant connection is lost. If both paths of an association are lost, then the alarm is set twice: first time for the primary path and second time for the secondary path.
The alarm indicates a failure in the SCTP association. The system possibly takes into use an alternative path or the alternative path is lost.
Two paths to each SCTP association are normally created in the SCTP association establishment. If either of the paths fails, this alarm is set. If the primary path fails, then the traffic is automatically transferred via a secondary path and traffic is not affected. If the second-ary path fails, then the traffic continues via the primary path normally and only the redundant connection is lost.
When the first supplementary field indicates M3UA or IUA:
This alarm can be set and be on only if the association is active at the SCTP layer, i.e. the state of the associ-ation is other than down when checked with MML commands like OYI and OYV. That is because the path state is supervised inside an active association by SCTP.
If the SCTP association goes down, this 3379 is can-celled. When an association goes down abnormally then also 3159 is set and at the same time this 3379 alarm is cancelled. In graceful shutdown procedure do not remain any alarm for the association once this 3379 is canceled. When the association becomes active again later on, this alarm is set again if there is path failure for a path with the new association. The alarm indicates a failure in the working SCTP association. The system possibly takes into use an alternative path or the alternative path is lost.
SIF structure in S14 SIF structure in S15
3379 SCTP PATH FAILURE
DN0963445DN0963445 Issue 01
43
Changes in RG20(BSS)
Id:0900d8058076d66f
PPI
SCTP Payload Protocol Identifier:
01 IUA
02 M2UA
03 M3UA
04 SUA
05 M2PA
06 V5UA
07 H.248
08 BICC/Q.2150.3
09 TALI
10 DUA
11 ASAP
12 ENRP
13 H.323
14 Q.IPC/Q.2150.3
DATA_1
first additional information field. This field contains the following information protocol by protocol:
for IUA protocol:
association number
for M3UA protocol:
association set index
for H248 protocol: MGW index in MSS. Virtual MGW index in MGW
DATA_2
the second additional information field. This field contains the following information protocol by protocol:
for IUA protocol:
not applicable (=0xFFFF)
for M3UA protocol:
association index in association set
for H248 protocol:
index of the controlling MSS data record in virtual MGW data in MGW. The value is between 0 and 2. 0xFFFF if no H.248 connection in MGW
PPI
SCTP Payload Protocol Identifier:
01 IUA
02 M2UA
03 M3UA
04 SUA
05 M2PA
06 V5UA
07 H.248
08 BICC/Q.2150.3
09 TALI
10 DUA
11 ASAP
12 ENRP
13 H.323
14 Q.IPC/Q.2150.3
254 IWF
DATA_1
first additional information field. This field contains the following information protocol by protocol:
for IUA protocol:
association number
for M3UA protocol:
association set index
for H248 protocol: MGW index in MSS. Virtual MGW index in MGW
for IWF protocol: IWF connection priority
DATA_2
the second additional information field. This field contains the following information protocol by protocol:
for IUA protocol:
not applicable (=0xFFFF)
for M3UA protocol:
association index in association set
for H248 protocol:
index of the controlling MSS data record in virtual MGW data in MGW. The value is between 0 and 2. 0xFFFF if no H.248 connection in MGW
for IWF protocol:
not applicable (=0xFFFF)
Instructions in S14 Instructions in S15
3379 SCTP PATH FAILURE
44 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Check the configuration and state of the IP network. Each SCTP payload protocol has its own inquiry MML command OYI for its configuration. Use the OYI MML command when the SCTP payload protocol configura-tion has been checked. Check the state of the IP network using the QRS MML command. See the examples below.
In case of M3UA:OYI::A;QRS:<signaling unit>,<index>:ALL; In case of IUA:OYV::A;QRS:<sig-naling unit>,<index>:ALL; In case of H.248:JGI (at MSS) or JVI (at MGW) command QRS:<signaling unit>,<index>:ALL;
Check the configuration and the state of the IP network. Each SCTP payload protocol has its own inquiry MML command for its configuration, e.g.M3UA: OYI::A;IUA: OYV::A;H.248: JGI (at MSS) or JVI (at MGW) command IWF: JGI (at MSS or CDS) or JCI (at MGW) command
Check the used SCTP parameter set and compare it to the peer endpoint's parameters. It is recommended to use exactly the same parameters on both end points. SCTP path status and statistics can be inquired from SCTP stack with QRS MML command:QRS:<signaling unit>,<index>:ALL;QRS:<signaling unit>,<index>:PRO;SCTP parameters mismatch typi-cally causes retransmissions at one endpoint and received duplicates at the other, i.e. retransmissions are done before data is acknowledged. In this case you need to either increase Retransmission TimeOut (RTO.MIN/MAX) or decrease Selective Acknowledge-ment Delay (SACK.PERIOD), so that acknowledge-ment delay has smaller value than peer's retransmission timeout. Or to be more specific: local RTO.MIN = peer's SACK.PERIOD + Round Trip Time (RTT) + safety margin
Check also switch/router port settings. E.g. duplex mismatch and misconfigured RSTP/MSTP can cause packet loss and connectivity problems. If alarm stays on permanently, ping/traceroute (QRX command) can help locating the problem. If IP network conditions can not be improved, increase error limit for this alarm (PATH.MAX.RETRANS). In this case increasing ASSOCIATION.MAX.RETRANS should be considered too. Remember to disconnect and reconnect after changing SCTP parameters, e.g. in case of M3UA set the M3UA link inactive and then back active with the ZNLC MML command.
Instructions in S14 Instructions in S15
Cancelling the alarm
Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected (for example, after a successful transfer of traffic to the STCP primary path or after an SCTP heartbeat message passes through the secondary path).
Cancelling the alarm
Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected (for example, after a successful transfer of traffic to the STCP primary path or after an SCTP heartbeat message passes through the secondary path). For M3UA or IUA the system also cancels the alarm if the association goes down, because the path state is supervised inside an active association by SCTP. That's why this alarm can be on and has meaning only if the SCTP association is active
3379 SCTP PATH FAILURE
3415 GPRS/EDGE LOAD IS VERY HIGH IN PCU OF PSE
Change description: Instructions improved
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
45
Changes in RG20(BSS)
Id:0900d8058076d66f
Changed in Base Station Alarms (7000-7999)
Check the PSE overload alarm threshold (POAT) with the MML command EEO. If required, increase the threshold with the MML command EEQ. The alarm is cancelled when the PCUs GPRS/EDGE load is under the threshold during the next measurement period (1 hour).
If the GPRS/EDGE load is not in balance in the PCUs, reallocate the DAPs and segments within the PSE manually or by adding a new PCU into PSE with the MML command FXF.
When the system or MCMU have been reset, the alarm is always cancelled.
Check the PSE overload alarm threshold (POAT) and GPRS capacity throughput factor with the MML command EEO. If required, increase the threshold or adjust capacity throughput factor with the MML command EEQ. The alarm is cancelled when the PCUs GPRS/EDGE load is under the threshold during the next measurement period (1 hour).
If the GPRS/EDGE load is not in balance in the PCUs, reallocate the DAPs and segments within the PSE manually or by adding a new PCU into PSE with the MML command FXF.
When the system or MCMU have been reset, the alarm is always cancelled.
3415 GPRS/EDGE LOAD IS VERY HIGH IN PCU OF PSE
3483 PCU RESTARTED
Change description: SIF Structure added
SIF structure in S14. SIF structure in S15
1 Logical index of the PCU, which is restarted.
2 PCU object id. If there is not PCU object for the PCU the field is set as 0xFF.
3 Type of restart:
01 PCU HOT restart
FF PCU COLD restart
4 Source of restart:
00 System, if recovery actions have taken place
01 User, if an MML command is used.
1 Logical index of the PCU, which is restarted.
2 PCU object id. If there is not PCU object for the PCU the field is set as 0xFF.
3 Type of restart:
01 PCU HOT restart
FF PCU COLD restart
4 Source of restart:
00 System, if recovery actions have taken place
01 User, if an MML command is used
02 User, DAP configuration
3504 DLDC ACTIVATION FAILURE
Change description: SIF Structure added
SIF structure in S14. SIF structure in S15
1 Logical index of the PCU, which is restarted
2 PCU object id. If there is not PCU object for the PCU the field is set as 0xFF.
3 Type of restart:
01 PCU HOT restart
1. Index of the BCSU controlling the PCU
2. Plug-in unit index of the PCU
7401 EXTERNAL AL 1
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
46 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7401 EXTERNAL AL 1 is mapped into ENVABTSE-0 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 1.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-0.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7401 EXTERNAL AL 1
7402 EXTERNAL AL 2
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7402 EXTERNAL AL 2 is mapped into ENVABTSE-1 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
47
Changes in RG20(BSS)
Id:0900d8058076d66f
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 2.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-1.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7402 EXTERNAL AL 2
7403 EXTERNAL AL 3
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7403 EXTERNAL AL 3 is mapped into ENVABTSE-2 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 3.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-2.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
48 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
7404 EXTERNAL AL 4
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7404 EXTERNAL AL 4 is mapped into ENVABTSE-3 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 4.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-3.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7405 EXTERNAL AL 5
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7405 EXTERNAL AL 5 is mapped into ENVABTSE-4 in LMT.
For other site types, you should define the alarm in a HW database..
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
49
Changes in RG20(BSS)
Id:0900d8058076d66f
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 5.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-4.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7405 EXTERNAL AL 5
7406 EXTERNAL AL 6
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7406 EXTERNAL AL 6 is mapped into ENVABTSE-5 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 6.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-5.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
50 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
7407 EXTERNAL AL 7
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7407 EXTERNAL AL 7 is mapped into ENVABTSE-6 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 7.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-6.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7408 EXTERNAL AL 8
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7408 EXTERNAL AL 8 is mapped into ENVABTSE-7 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
51
Changes in RG20(BSS)
Id:0900d8058076d66f
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 8.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-7.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7408 EXTERNAL AL 8
7409 EXTERNAL AL 9
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7409 EXTERNAL AL 9 is mapped into ENVABTSE-8 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 9.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-8.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
52 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
7410 EXTERNAL AL 10
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7410 EXTERNAL AL 10 is mapped into ENVABTSE-9 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 10.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-9.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7411 EXTERNAL AL 11
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7411 EXTERNAL AL 11 is mapped into ENVABTSE-10 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
53
Changes in RG20(BSS)
Id:0900d8058076d66f
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 11.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-10.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7411 EXTERNAL AL 11
7412 EXTERNAL AL 12
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)"
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7412 EXTERNAL AL 12 is mapped into ENVABTSE-11 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 12.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-11.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
54 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
7413 EXTERNAL AL 13
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7413 EXTERNAL AL 13 is mapped into ENVABTSE-12 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 13.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-12.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7414 EXTERNAL AL 14
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7414 EXTERNAL AL 14 is mapped into ENVABTSE-13 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
55
Changes in RG20(BSS)
Id:0900d8058076d66f
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 14.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-13.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7414 EXTERNAL AL 14
7415 EXTERNAL AL 15
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7415 EXTERNAL AL 15 is mapped into ENVABTSE-14 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 15.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-14.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
56 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
7416 EXTERNAL AL 16
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7416 EXTERNAL AL 16 is mapped into ENVABTSE-15 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 16.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-15.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7417 EXTERNAL AL 17
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7417 EXTERNAL AL 17 is mapped into ENVABTSE-16 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
57
Changes in RG20(BSS)
Id:0900d8058076d66f
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 17.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-16.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7417 EXTERNAL AL 17
7418 EXTERNAL AL 18
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7418 EXTERNAL AL 18 is mapped into ENVABTSE-17 in LMT.
For other site types, you should define the alarm in a HW database..
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 18.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-17.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line
.2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
58 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
7419 EXTERNAL AL 19
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7419 EXTERNAL AL 19 is mapped into ENVABTSE-18 in LMT.
For other site types, you should define the alarm in a HW database..
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 19.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-18.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7420 EXTERNAL AL 20
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7420 EXTERNAL AL 20 is mapped into ENVABTSE-19 in LMT.
For other site types, you should define the alarm in a HW database..
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
59
Changes in RG20(BSS)
Id:0900d8058076d66f
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 20.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-19.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7420 EXTERNAL AL 20
7421 EXTERNAL AL 21
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7421 EXTERNAL AL 21 is mapped into ENVABTSE-20 in LMT.
For other site types, you should define the alarm in a HW database.
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 21.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-20.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
60 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
7422 EXTERNAL AL 22
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7422 EXTERNAL AL 22 is mapped into ENVABTSE-21 in LMT.
For other site types, you should define the alarm in a HW database..
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 22.
BTSplus BTS:The operation depends on what kind of alarm is used as external alarm ENVABTSE-21.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7423 EXTERNAL AL 23
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7423 EXTERNAL AL 23 is mapped into ENVABTSE-22 in LMT.For other site types, you should define the alarm in a HW database..
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
61
Changes in RG20(BSS)
Id:0900d8058076d66f
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 23.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-22.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
7423 EXTERNAL AL 23
7424 EXTERNAL AL 24
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, or Flexi EDGE BTS, see "Adding an external input and output text (MetroSite, UltraSite, and Flexi EDGE only)".
For other site types, you should define the alarm in a HW database.
This is an external user-defined alarm.
For instructions on how to define the alarm for Met-roSite BTS, UltraSite BTS, Flexi EDGE BTS or Flexi Multiradio BTS, see "Adding an external input and output text (MetroSite, UltraSite, Flexi EDGE, and Flexi Multiradio only)".
For BTSplus site type, ALARM 7424 EXTERNAL AL 24 is mapped into ENVABTSE-23 in LMT.
For other site types, you should define the alarm in a HW database..
Instructions in S14 Instructions in S15
Flexi EDGE BTS: This is an external user-defined alarm. This alarm is activated at the external equip-ment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
The operation depends on what kind of alarm is used as external alarm no. 24.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-23.
Flexi EDGE BTS and Flexi Multiradio BTS: This is an external user-defined alarm. This alarm is activated at the external equipment.
1. Check equipment connected to alarming EAC line.
2. Check that the relevant EAC line is correctly config-ured at the BSC (MML command ZEFO:<id>:IOP;).
3. Check that the cable is correctly mated between EAC port of ESMA (or EAC port of optional FSEx module, if used) and the external equipment.
4. Check the FSEx and replace it if faulty.
5. Check the ESMA and replace it if faulty.
62 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
7425 EXTERNAL AL 25
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
This is an external user-defined alarm.The alarm is defined by the user in an HW database.
For BTSplus site type, ALARM 7425 EXTERNAL AL 25 is mapped into ENVABTSE-24 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as an external alarm no. 25.
The operation depends on what kind of alarm is used as an external alarm no. 25.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-24.
7426 EXTERNAL AL 26
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
For BTSplus site type, ALARM 7426 EXTERNAL AL 26 is mapped into ENVABTSE-25 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as an external alarm no. 26.
The operation depends on what kind of alarm is used as an external alarm no. 26.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-25
7427 EXTERNAL AL 27
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
For BTSplus site type, ALARM 7427 EXTERNAL AL 27 is mapped into ENVABTSE-26 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as an external alarm no. 27.
The operation depends on what kind of alarm is used as an external alarm no. 27.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-26.
7428 EXTERNAL AL 28
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
DN0963445DN0963445 Issue 01
63
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
For BTSplus site type, ALARM 7428 EXTERNAL AL 28 is mapped into ENVABTSE-27 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as an external alarm no. 28.
The operation depends on what kind of alarm is used as an external alarm no. 28.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-27.
7428 EXTERNAL AL 28
7429 EXTERNAL AL 29
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
For BTSplus site type, ALARM 7429 EXTERNAL AL 29 is mapped into ENVABTSE-28 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as an external alarm no. 29.
The operation depends on what kind of alarm is used as an external alarm no. 29.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-28.
7430 EXTERNAL AL 30
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in an HW database..
This is an external user-defined alarm. The alarm is defined by the user in an HW database.
For BTSplus site type, ALARM 7430 EXTERNAL AL 30 is mapped into ENVABTSE-29 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as an external alarm no. 30.
The operation depends on what kind of alarm is used as an external alarm no. 30.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-29.
7431 EXTERNAL AL 31
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
64 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7431 EXTERNAL AL 31is mapped into ENVABTSE-30 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 31.
The operation depends on what kind of alarm is used as external alarm no. 31.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-30.
7431 EXTERNAL AL 31
7432 EXTERNAL AL 32
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7432 EXTERNAL AL 32 is mapped into ENVABTSE-31 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 32.
The operation depends on what kind of alarm is used as external alarm no. 32.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-31.
7433 EXTERNAL AL 33
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7433 EXTERNAL AL 33 is mapped into ENVABTSE-32 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 33.
The operation depends on what kind of alarm is used as external alarm no. 33.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-32.
7434 EXTERNAL AL 34
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
DN0963445DN0963445 Issue 01
65
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7434 EXTERNAL AL 34 is mapped into ENVABTSE-33 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 34.
The operation depends on what kind of alarm is used as external alarm no. 34.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-33.
7434 EXTERNAL AL 34
7435 EXTERNAL AL 35
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7435 EXTERNAL AL 35 is mapped into ENVABTSE-34 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 35.
The operation depends on what kind of alarm is used as external alarm no. 35.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-34.
7436 EXTERNAL AL 36
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7436 EXTERNAL AL 36 is mapped into ENVABTSE-35 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 36.
The operation depends on what kind of alarm is used as external alarm no. 36.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-35.
7437 EXTERNAL AL 37
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
66 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7437 EXTERNAL AL 37 is mapped into ENVABTSE-36 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 37.
The operation depends on what kind of alarm is used as external alarm no. 37.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-36.
7437 EXTERNAL AL 37
7438 EXTERNAL AL 38
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7438 EXTERNAL AL 38 is mapped into ENVABTSE-37 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 38.
The operation depends on what kind of alarm is used as external alarm no. 38.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-37.
7439 EXTERNAL AL 39
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7439 EXTERNAL AL 39 is mapped into ENVABTSE-38 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 39.
The operation depends on what kind of alarm is used as external alarm no. 39.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-38.
7440 EXTERNAL AL 40
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
DN0963445DN0963445 Issue 01
67
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7440 EXTERNAL AL 40 is mapped into ENVABTSE-39 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 40.
The operation depends on what kind of alarm is used as external alarm no. 40.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-39.
7440 EXTERNAL AL 40
7441 EXTERNAL AL 41
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7441 EXTERNAL AL 41 is mapped into ENVABTSE-40 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 41.
The operation depends on what kind of alarm is used as external alarm no. 41.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-40.
7442 EXTERNAL AL 42
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7442 EXTERNAL AL 42 is mapped into ENVABTSE-41 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 42.
The operation depends on what kind of alarm is used as external alarm no. 42.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-41.
7443 EXTERNAL AL 43
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
68 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7443 EXTERNAL AL 43 is mapped into ENVABTSE-42 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 43.
The operation depends on what kind of alarm is used as external alarm no. 43.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-42.
7443 EXTERNAL AL 43
7444 EXTERNAL AL 44
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7444 EXTERNAL AL 44 is mapped into ENVABTSE-43 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 44.
The operation depends on what kind of alarm is used as external alarm no. 44.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-43.
7445 EXTERNAL AL 45
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7445 EXTERNAL AL 45 is mapped into ENVABTSE-44 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 45.
The operation depends on what kind of alarm is used as external alarm no. 45.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-44.
7446 EXTERNAL AL 46
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
DN0963445DN0963445 Issue 01
69
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7446 EXTERNAL AL 46 is mapped into ENVABTSE-45 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 46.
The operation depends on what kind of alarm is used as external alarm no. 46.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-45.
7446 EXTERNAL AL 46
7447 EXTERNAL AL 47
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7447 EXTERNAL AL 47 is mapped into ENVABTSE-46 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 47.
The operation depends on what kind of alarm is used as external alarm no. 47.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-46.
7448 EXTERNAL AL 48
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7448 EXTERNAL AL 48 is mapped into ENVABTSE-47 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 48.
The operation depends on what kind of alarm is used as external alarm no. 48.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-47.
7449 EXTERNAL AL 49
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
70 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7449 EXTERNAL AL 49 is mapped into ENVABTSE-48 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 49.
The operation depends on what kind of alarm is used as external alarm no. 49.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-48.
7449 EXTERNAL AL 49
7450 EXTERNAL AL 50
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7450 EXTERNAL AL 50 is mapped into ENVABTSE-49 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 50.
The operation depends on what kind of alarm is used as external alarm no. 50.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-49.
7451 EXTERNAL AL 51
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7451 EXTERNAL AL 51 is mapped into ENVABTSE-50 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 51.
The operation depends on what kind of alarm is used as external alarm no. 51.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-50.
7452 EXTERNAL AL 52
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
DN0963445DN0963445 Issue 01
71
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7452 EXTERNAL AL 52 is mapped into ENVABTSE-51 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 52.
The operation depends on what kind of alarm is used as external alarm no. 52.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-51.
7452 EXTERNAL AL 52
7453 EXTERNAL AL 53
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7453 EXTERNAL AL 53 is mapped into ENVABTSE-52 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 53.
The operation depends on what kind of alarm is used as external alarm no. 53.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-52.
7454 EXTERNAL AL 54
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7454 EXTERNAL AL 54 is mapped into ENVABTSE-53 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 54.
The operation depends on what kind of alarm is used as external alarm no. 54.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-53.
7455 EXTERNAL AL 55
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
72 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7455 EXTERNAL AL 55 is mapped into ENVABTSE-54 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 55.
The operation depends on what kind of alarm is used as external alarm no. 55.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-54.
7455 EXTERNAL AL 55
7456 EXTERNAL AL 56
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7456 EXTERNAL AL 56 is mapped into ENVABTSE-55 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 56.
The operation depends on what kind of alarm is used as external alarm no. 56.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-55.
7457 EXTERNAL AL 57
Change description: Meaning improved, Instructions improved
Meaning in S14 Meaning in S15
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
This is an external user-defined alarm. The alarm is defined by the user in a HW database.
For BTSplus site type, ALARM 7457 EXTERNAL AL 57 is mapped into ENVABTSE-56 in LMT.
Instructions in S14 Instructions in S15
The operation depends on what kind of alarm is used as external alarm no. 57.
The operation depends on what kind of alarm is used as external alarm no. 57.
BTSplus BTS: The operation depends on what kind of alarm is used as external alarm ENVABTSE-56.
7600 BCF FAULTY
Change description: Instructions changed
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
73
Changes in RG20(BSS)
Id:0900d8058076d66f
FLEXI EDGE:
Fault reason: Critical Transmission Licence missing at the BSC. Description: Either "Flexi EDGE Abis over IP/Ethernet" or "FlexiEDGE Additional 2 E1/T1" licence has not been installed in BSC.
Instructions:
1. Check which transmission licence alarm (8273 or 8274) is active and follow the alarm specific instructions given.
Fault reason: Air i/f reference clock 26 MHz not avail-able.
Description: ESMA System module detected that its Oven Controlled 26 MHz Oscillator is broken.
Instructions:
1. Issue a HW reset to ESMA from (remote) BTS Manager.
Note: This site's bypass transmission will be cut for 1-2 minutes.
2. Replace ESMA.
FLEXI EDGE:
Fault reason: Critical Transmission Licence missing at the BSC. Description: Either "2G Flexi Abis over IP/Ethernet" or "2G FlexiAdditional 2 E1/T1" licence has not been installed in BSC.
Instructions:
1. Check which transmission licence alarm (8273 or 8274) is active and follow the alarm specific instructions given.
Fault reason: Air i/f reference clock 26 MHz not avail-able.
Description: ESMA System module detected that its Oven Controlled 26 MHz Oscillator is not generating frequency reference signal.
Instructions:
1. Make sure that ambient temperature of the site is within normal operating temperature range (-35...+50C/-31...+122F).
2. Issue a HW reset to ESMA from (remote) BTS Manager.
Note: This site's bypass transmission will be cut for 1-2 minutes.
3. Replace ESMA.
Instructions in S14 Instructions in S15
7600 BCF FAULTY
74 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
FLEXI MULTIRADIO:
Fault reason: Air i/f reference clock not available.
Description: System module detected that its Oven Controlled Oscillator is not generating the frequency reference.
Instructions:
1. Make sure that ambient temperature of the site is within normal operating temperature range (-35...+50C/-31...+122F).
2. Issue a HW reset to ESMx from (remote) BTS Manager. Note: This site's bypass transmission will be cut for 1-2 minutes.
3. Replace ESMx." Fault reason: BSS synchronisation failed Description: System module detected no syn-chronisation signal at synchronisation input (SIN) port at startup.
Instructions:
1. Check that the BCF synchronisation related settings are correct at the BSC via MML command(s) (ZEFO...).
2. If LMU provides the synchronisation, check if alarm 8202 is active and resolve.
3. If another BTS is the synchronisation master, check if that it is up and alive.
4. Check that the synchronisation cabling is correctly mated between the units. If LMU is used, check also Q1 cabling and power supply to the LMU unit.
5. Replace ESMx.
Fault reason: BTS Synchronisation source mismatch between BSC and BCF Description: Clock source received from BSC is BTS_Ext (eternal) where as BTS is commissioned in RP1 sync slave mode.
Instructions:
1. Commission the BTS in RP1 sync Slave Mode.
2. Change Clock source at BSC to some other value. Fault reason: RP1 synchronization failure during startup in ESMx System module
Description: During start-up of RP1 synchronization was not achieved by ESMx System module
Instructions:
1. Connect the cable between RP1 synchronisation master and RP1 synchronisation slave.
2. Replace the cable between RP1 synchronisation master and RP1 synchronisation slave.
7600 BCF FAULTY
DN0963445DN0963445 Issue 01
75
Changes in RG20(BSS)
Id:0900d8058076d66f
3. Issue HW reset to ESMx System module from Element Manager.
4. Replace the ESMx System module.
Fault reason: RP1 Synchronization failure during runtime in ESMx System module
Description: For ESMx System module RP1 synchroni-sation failure occurs during run-time
Instructions:
1. Connect the sync cable between RP1 synchronisa-tion master and RP1 synchronisation slave.
2. Issue BCF reset from Element Manager.
3. Issue HW reset from Element Manager.
4. Replace ESMx System module.
Fault reason: ESMAx System module has lost connec-tion to FIxx transmission submodule Description: FIEA/FIPA/FIFA/FIQA/FIYA Transport sub-module is not detected. This alarm is normally reported to the local BTS Manager only.
Instructions:
1. Check that the PIU (FIPA/FIEA/FIFA/FIQA/FIYA) is properly inserted into the ESMx.
2. Check the LED status: If LED is not lit (all PIU types) or Yellow (for FIPA/FIEA/FIQA/FIYA), check the back connector of the PIU.
3. Replace PIU.
4. Replace ESMx, system module. Note: At the BSC, alarms 7767 BCCH Missing, 7706 BTS O&M link failure may be active for the alarming BCF.
Fault reason: FIxx type mismatch between commis-sioning file and detected hardware Description: FIEA/FIPA/FIFA/FIQA/FIYA Transport sub-module is of wrong type. This alarm is normally reported to the local BTS Manager only. Instructions:
1.1 Replace PIU module with a correct type (as defined in SCF) and issue a HW reset to ESMx. OR
1.2 Set PIU type in SCF according to the actual PIU module type and re-commission the site.
2. Replace the PIU and issue a HW reset to ESMx.
Fault reason: ESMx System module has lost connec-tion to all ECxx RTCs and EXxx TRXs
7600 BCF FAULTY
76 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Description: None of the BTS modules respond to ESMx polling command. Instructions:
1. Reset BCF.
2. Check all cable connections between ESMA and ECxx RTC and EXxx TRX modules.
3. If the fault persists, replace ESMx.
Fault reason: ESMx System module temperature dan-gerously high Description: Internal temperature of ESMx System module has exceeded +95C/+203F. Instructions:
1. Ensure that the ambient temperature of the base station is below +50C/+122F.
2. Check if any fan alarms are also active. If active, refer to fan alarm instructions to resolve.
3. Replace the ESMx.
Fault reason: Critical transmission licence missing at the BS. Description: Either 'Abis over IP/Ethernet' or 'Additional 2 E1/T1' licence has not been installed in the BSC. Instructions:
1. Check which transmission licence alarm (8273 or 8274) is active and follow the alarm specific instructions given.
Fault reason: ESMx System module has lost connec-tion to all configured modules. Description: BTS is not able to detect any RP3 connectivity to SM/RFMs. Instructions:
1. Check all Optical connections between SM and RFMs/Peer SM.
Fault reason: ESMx System module internal HW failure Description: Internal initialisation failure occurred in ESMx System module. Instructions:
1. Issue BCF reset from (remote) BTS Manager.2. Replace ESMx.*/
Instructions in S14 Instructions in S15
Cancelling the alarm:
If the alarm requires no user actions, you can cancel it with the MML command EOR.
The system cancels the alarm automatically in connec-tion with the user's locking and unlocking commands, or, if the situation is solved without user actions, after the current measurement period..
Cancelling the alarm:
If the alarm requires no user actions, you can cancel it with the MML command EOR.
The system cancels the alarm automatically in connec-tion with the user's locking and unlocking commands, or, if the situation is solved without user actions, after the current measurement period.
All supplementary fields are set to zero irrespective of the alarms cancelled manually or by the system.
7600 BCF FAULTY
7601 BCF OPERATION DEGRADED
Change description: Instructions added, changed and removed.
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
77
Changes in RG20(BSS)
Id:0900d8058076d66f
METROSITE:
Fault reason: Cabinet I2C bus is jammed.
Instructions:
1. Switch the site power off and on.
2. Check the fan unit, the power supply unit and the TRXs. If necessary, replace the faulty units(s).
3. If the fault reappears, replace the cabinet. The units inside the cabinet can be reused in the new cabinet.
Fault reason: Difference between PCM and base station frequency reference.
Instructions:
1. Check the cabling
2. If the cabling is OK, replace the master TRX.
Fault reason: Incompatible unit presence has been detected in the BTS.
Instructions:
1. Replace the high power or EDGE TRX(s) with normal type TRX(s) and reset the BCF.
2. Or, replace the normal type FAN and power supply with high power or EDGE units. Now EDGE and high power TRXs are supported.
Other fault reasons
Instructions:
1. Check whether one or several of the following alarms are active:
7606 TRX FAULTY
7603 BTS FAULTY
7607 TRX OPERATION DEGRADED
7604 BTS OPERATION DEGRADED
and follow the instructions given for the active alarm(s).
INSITE:
Fault reason: AC is off and the battery voltage is too low or battery is being charged.
Instructions:
1. Check the mains supply.
2. Check the power supply unit and replace if neces-sary.
3. If the alarm reappears after the recovery actions above, replace the BTS.Fault reason: Difference between the PCM and BTS frequency reference.
Instructions:
1. Check the synchronisation settings of the transmis-sion interface.
2. If the settings are OK, check the transmission chain.
Fault reason: Loss of BSS Synch while on Abis clock.
Instructions:
1. No corrective actions required.
Note: Alarm start/cancel is based on the alignment of the BTS clock to the external clock reference after external clock reference has recovered from fault con-dition. Alarm start will equate to degradation in DFCA performance. A site reset will reduce alignment time. Note that the BTS clock will align with the external clock reference over a period of several hours.
Fault reason: Irrecoverable Loss of BSS Synch.
Instructions:
1. Site reset is required. Note that the alarm start is based on the following:
a. Large alignment problems between Abis clock and external clock reference, after external clock reference has recovered from fault condition.
b. Fluctuation in the DAC word. Alarm start will equate to significant degradation in DFCA performance.
Fault reason: Irrecoverable Loss of BSS Synch
Description: The received FCLK has slipped more than 40 microseconds away from the LMU FCLK while using the Abis clock as a secondary master-clock. This timing error is too high to be recovered reliably.
Instructions:
1. Site reset is required.
Note that the alarm start is based on the following:
1. Large alignment problems between Abis clock and external clock reference, after external clock reference has recovered from fault condition.
2. Fluctuation in the DAC word. Alarm start will equate to significant degradation in DFCA performance.
Fault reason:
Loss of BSS Synch while on Abis clock.
Description: This alarm indicates that the FCLK has slipped between 20-40 microseconds away from the LMU FCLK while using the Abis clock as a secondary master-clock.
Instructions:
1. No corrective actions required.
Note: Alarm start/cancel is based on the alignment of the BTS clock to the external clock reference after external clock reference has recovered from fault con-dition. Alarm start will equate to degradation in DFCA performance. A site reset will reduce alignment time.
7601 BCF OPERATION DEGRADED
78 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
3. If the alarm stays active or reappears after the recovery actions above, reset the BCF.
4. If the alarm reappears after the BCF reset, replace the BTS.
Fault reason: Flash operation failed.
Instructions:
1. Reset the BCF.
2. If the alarm reappears, replace the BTS.
Fault reason: The TX output power has dropped at least 3 dB.
Instructions:
1. No immediate actions required.
2. If the alarm stays active or reappears frequently, replace the BTS.
Fault reason: Oven oscillator control is close to its margins. The oven might be outdated.
Instructions:
1. Check the synchronisation settings of the transmis-sion interface.
2. If the settings are OK, check the transmission chain.
3. If the alarm stays active or reappears after the recovery actions above, reset the BCF.
4. If the alarm reappears after the BCF reset, replace the BTS.
ULTRASITE:
Fault reason: Power unit output voltage fault.
Instructions:
1. Replace all faulty power units.
Fault reason: Power unit input voltage fault.
Instructions:
1. Ensure that the input voltage is correct.
2. Replace all faulty power units.
Fault reason: No connection to power unit.
1. Replace all faulty power units.
Fault reason: Power unit temperature is dangerously high.
Instructions:
1. Ensure that the ambient temperature of the base station is within specified limits.
2. Check the cabinet fans.
3. Replace the faulty power unit(s).
Flexi Multiradio:
Fault reason: Difference between PCM and BTS fre-quency reference
Description: There is over 5 Hz difference to the 2MHz reference clock due to Abis link instability.
Instructions:
1. Check that Synchronisation priority list has correct Rx clock sources.
2. Check the Abis link quality (G.826 performance sta-tistics via BTS Manager/NetAct). Check the alarm history for 8xxx alarms reported and resolve any link problems occurred.
3. Check the network synchonisation between the BSC and the base station.
4. If alarm is active at multiple sites, check the quality of synchronisation for the whole BSS.
Fault reason: 1 PPS synchronisation reference signal missing.
Description: BTS is not able to derive air interface clock from reference 1PPS clock source. Instructions:
1. Check that PPS source has been correctly pro-grammed to provide the 1PPS signal.
2. Check the cable between the PPS source and the sync in port of ESMx.
Fault reason: Clock tuning DAC word against 1 PPS reference reaching min/max limit.
Description: When 1 PPS is chosen as reference source, difference between the calculated and previous DAC word is more than 5% of the whole tuning range of DAC
Instructions:
1. Check the configured DAC word.
Fault reason: ESMx System module has lost connec-tion to FSEx External Alarm (EAC) module.
Description: FSEx External Alarm (EAC) module does not respond to poll message of the ESMx System module.
Instructions:
1. Check that FSEx is set to Active Mode by connecting pins 3-4 of X1103 jumper.
2. Check that the cabling is correctly mated between ESMx and FSEx.
3. Replace FSEx.
4. Replace ESMx.
7601 BCF OPERATION DEGRADED
DN0963445DN0963445 Issue 01
79
Changes in RG20(BSS)
Id:0900d8058076d66f
Note: An alarm is activated when the PWSX internal temperature exceeds +85 C.
Fault reason: Transmission unit temperature is danger-ously high.
Instructions:
1. Ensure that the ambient temperature of the base station is within specified limits.
2. Check the cabinet fans.
3. Replace the faulty transmission unit.
Note: An alarm is activated when the transmission unit internal temperature exceeds +85 C.
Fault reason: Difference between PCM and base station frequency reference.
Instructions:
1. Check the network synchronisation between the BSC and the base station.
2. Check the transmission synchronisation settings on the transmission card.
3. Check the transmission cabling at the site.
4. Replace the BOI.
Note: After corrective actions, it may take several hours to adjust the clock and the alarm to disappear.
Fault reason: Flash operation failed in BOI or TRX.
Instructions:
1. Replace the BOI.
Fault reason: BOI detected that the site support is dumb.
Instructions:
1. Check the SISU cabinet and the connection.
Fault reason: Loss of BSS Synch while on Abis clock.Instructions:
1. No corrective actions required.
Note: Alarm start/cancel is based on the alignment of the BTS clock to the external clock reference after external clock reference has recovered from fault con-dition. Alarm start will equate to degradation in DFCA performance. A site reset will reduce alignment time. Note that the BTS clock will align with the external clock reference over a period of several hours.
Fault reason: Irrecoverable Loss of BSS Synch.
Instructions:
1. Site reset is required.
Note that the alarm start is based on the following:
a. Large alignment problems between Abis clock and external clock reference, after external clock reference has recovered from fault condition.
Fault reason: ESMx System module cooling fan(s) report no rotation
Description: One or more fans of the ESMx System module are not rotating. There is a danger of overheat-ing.
Instructions:
1. Check that the fan unit cable is correctly mated to ESMx.
2. Check that there are no obstacles preventing the fan(s) from rotating.
3. Clean the fan unit of dust and/or dirt.
4. Replace the fan unit.
5. Replace ESMx.
Fault reason: Commissioning failed due to BCF ID mismatch between commissioning file and BSC.
Description: Incorrect BCF ID between the BSC and the Commissioning File (SCF).
Instructions:
1. Check the transmission path of the traffic allocated to the site against the network plan.
2. Using the (remote) BTS Manager, recommission the BTS with correct BCF ID.
(Steps on the BTS Manager: Commissioning Wizard | Change Settings Manually --> Amend the BCF ID, as needed)
Note: The alarm is sent only when the BTS is uncom-missioned and a mismatch has been detected. In any other cases, for example, after a BCF reset, the alarm is not sent. If in Append commissioning, the mismatch of BCF id is visible only in the commissioning report.
Fault reason: ESMx System module FLASH memory writing error
Description: Memory write failure occurred at SW download and is not valid, previously active SW is taken into use.
Instructions:
1. Issue a HW reset to ESMx from (remote) BTS Manager.
2. Attempt the SW download again.
3. If this alarm persists, replace ESMx
Fault reason: All external Q1 devices fail to respond.
Description: None of the configured Q1 devices in the Q1 bus are responding to a polling command.
Instructions:
1. Check that Q1 addresses and baud rate match between the Q1 devices and BSC.
2. If FIFA is used and BTS is polling Q1 equipment, check that Q1 switch towards the Q1 bus is closed with FlexiHub Manager.
7601 BCF OPERATION DEGRADED
80 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
b. Fluctuation in the DAC word. Alarm start will equate to significant degradation in DFCA performance
Other fault reasons
Instructions:
1. Check whether one or several of the following alarms are active:
7606 TRX FAULTY
7603 BTS FAULTY
7607 TRX OPERATION DEGRADED
7604 BTS OPERATION DEGRADED
7602 BCF NOTIFICATION
and follow the instructions given for the active alarm(s).
Flexi EDGE:
Fault reason: Difference between PCM and BTS fre-quency reference.
Description: There is over 5 Hz difference to the 2MHz reference clock due to Abis link instability.
Instructions:
1. Check that Synchronisation priority list has correct Rx clock sources.
2. Check the Abis link quality (G.826 performance sta-tistics via BTS Manager/NetAct). Check the alarm history for 8xxx alarms reported and resolve any link problems occurred.
3. Check the network synchonisation between the BSC and the base station.
4. If alarm is active at multiple sites, check the quality of synchronisation for the whole BSS.
Fault reason: ESMA System module has lost connec-tion to FSEx External Alarm (EAC) module.
Description: FSEx External Alarm (EAC) module does not respond to poll message of the ESMA System module.
Instructions:
1. Check that FSEx is set to Active Mode by connecting pins 3-4 of X1103 jumper.
2. Check that the cabling is correctly mated between ESMA and FSEx.
3. Replace FSEx.
4. Replace ESMA.
Fault reason: ESMA System module cooling fan(s) report no rotation.
Description: One or more fans of the ESMA System module are not rotating. There is a danger of overheat-ing.
Instructions:
1. Check that the fan unit cable is correctly mated to ESMA.
3. Check that the Q1 cables are correctly mated between the ESMx and Q1 devices.
4. Replace ESMx.
Fault reason: ESMx System module has detected no fans.
Description: ESMx System module has not detected a fan unit at start up. There is a danger of overheating.
Instructions:
1. Check that the fan unit cable is correctly mated to ESMx.
2. Replace the fan unit.
3. Replace the ESMx.
Fault reason:
FxxA module SW download from ESMx System module failed.
Description: Attempt of loading Software on the RFM has failed.
Instructions:
1. Block/Unblock the RFM on which the SW download has failed.
2. Power OFF and On the RFM.
3. If still the alarm exists, then replace the alarming Module.
Fault reason: Mismatch occurred between commis-sioned and detected antenna line device.
Description: Antenna line device (ALD) configured in SCF is not physically detected.
Instructions:
1. Define antenna line device(s) via append commis-sioning.
2. Check that antenna line device is connected physi-cally as per commissioned information.
3. Replace antenna line device.Fault reason: Antenna line device configuration has failed due to parameter mismatch.
Description: Detected antenna line device (ALD) parameter(s) mismatch has occurred.
Instructions:
1. Append the ALD information via (remote) BTS manager append commissioning.
2. Remove the alarmed ALD and connect the ALD as per commissioned information.
7601 BCF OPERATION DEGRADED
DN0963445DN0963445 Issue 01
81
Changes in RG20(BSS)
Id:0900d8058076d66f
2. Check that there are no obstacles preventing the fan(s) from rotating.
3. Clean the fan unit of dust and/or dirt.
4. Replace the fan unit.
5. Replace ESMA.
Fault reason: Commissioning failed due to BCF ID mismatch between commissioning file and BSC.
Description: Incorrect BCF ID between the BSC and the Commissioning File (SCF).
Instructions:
1. Check the transmission path of the traffic allocated to the site against the network plan.
2. Using the BTS Manager, recommission the BTS with correct BCF ID. (Steps on the BTS Manager: Commis-sioning Wizard Change Settings Manually --> Amend the BCF ID, as needed)
Note: The alarm is sent only when the BTS is uncom-missioned and a mismatch has been detected. In any other cases, for example, after a BCF reset, the alarm is not sent. If in Append, the mismatch of BCF id is visible only in the commissioning report.
Fault reason: ESMA System module FLASH memory writing error.
Description: Memory write failure occurred at SW download and is not valid, previously active SW is taken into use.
Instructions:
1. Issue a HW reset to ESMA from BTS Manager.
2. Attempt the SW download again.
3. If this alarm persists, replace ESMA.
Fault reason: All external Q1 devices fail to respond.Description: None of the configured Q1 devices in the Q1 bus are responding to a polling command.
Instructions:
1. Check that Q1 addresses and baud rate match between the Q1 devices and BSC.
2. If FIFA is used and BTS is polling Q1 equipment, check that Q1 switch towards the Q1 bus is closed with FlexiHub Manager.
3. Check that the Q1 cables are correctly mated between the ESMA and Q1 devices.
4. Replace ESMA.
Fault reason: ESMA System module has detected no fans.
Description: ESMA System module has not detected a fan unit at start up. There is a danger of overheating.
Instructions:
1. Check that the fan unit cable is correctly mated to ESMA.
7601 BCF OPERATION DEGRADED
82 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
2. Replace the fan unit.
3. Replace the ESMA.
Fault reason: Module power cable connections are incorrectly configured.
Description: One or more of the internal power cable connections does not match power cabling rules. Intel-ligent shutdown feature may not operate correctly.
Instructions:
1. Check the internal power and bus cabling against the product documentation set.
2. Issue a BCF reset.
Fault reason: ESEA System Extension Module fan(s) out of order
Description: ESEA System Extension module detected reduced speed or no rotation of fan(s) against com-manded speed.
Instructions:
1. Check that the fan unit cable is correctly mated to ESEA.
2. Check that there are no obstacles preventing the fan(s) from rotating.
3. Clean the fan unit of dust and/or dirt.
4. Replace the fan unit.
5. Replace ESEA.
Fault reason: Irrecoverable Loss of BSS SynchDescip-tion: The received FCLK has slipped more than 40 microseconds away from the LMU FCLK while using the Abis clock as a secondary master-clock. This timing error is too high to be recovered reliably.
Instructions:
1. Site reset is required.
Note that the alarm start is based on the following:1. Large alignment problems between Abis clock and external clock reference, after external clock reference has recovered from fault condition.
2. Fluctuation in the DAC word.
Alarm start will equate to significant degradation in DFCA performance.
Fault reason: Loss of BSS Synch while on Abis clock.
Description: This alarm indicates that the FCLK has slipped between 20-40 microseconds away from the LMU FCLK while using the Abis clock as a secondary master-clock.
Instructions:
1. No corrective actions required..
7601 BCF OPERATION DEGRADED
DN0963445DN0963445 Issue 01
83
Changes in RG20(BSS)
Id:0900d8058076d66f
Note: Alarm start/cancel is based on the alignment of the BTS clock to the external clock reference after external clock reference has recovered from fault con-dition. Alarm start will equate to degradation in DFCA performance. A site reset will reduce alignment time
Instructions in S14 Instructions in S15
This is a start/cancel type alarm.
For the fault reasons "Incompatible unit presence has been detected in the BTS," "ESMA System module FLASH memory writing error", "ESMA System module has detected no fans", or "Module power cable connec-tions are incorrectly configured", alarm is cancelled manually (BCF reset).
For other fault reasons alarm is cancelled automati-cally.
This is a start/cancel type alarm.
For the UltraSite BTS fault reason "Irrecoverable Loss of BSS Synch", the alarm must be cancelled manually. Note that the BTS clock will align with external clock immediately after the reset completes.
For the fault reasons "Incompatible unit presence has been detected in the BTS," "ESMA System module FLASH memory writing error", "ESMA System module has detected no fans", or "Module power cable connec-tions are incorrectly configured", alarm is cancelled manually (BCF reset).
For other fault reasons alarm is cancelled automati-cally.
Instructions in S14 Instructions in S15
Note that this alarm is not supported in EP1.1 CD1.0.
7601 BCF OPERATION DEGRADED
7602 BCF NOTIFICATION
Change description: SIF Structures changed, Instructions added and changed
SIF structure in S14 SIF structure in S15
DIAGN_INFO1-6 XX XX XX XX XX XX1 2 3 4 5 6
1) rack (cabinet) number
2) shelf number
3) slot
4) type of unit
5) unit number
6) subunit number
For Flexi EDGE BTS's fault reason "Incoming reference clock has started to deviate rapidly", the rack and shelf values indicate the nominal DAC word in hexadecimal format.
For more information, see Alarm Structure.
DIAGN_INFO1-6 XX XX XX XX XX XX1 2 3 4 5 6
1) rack (cabinet) number
2) shelf number
3) slot
4) type of unit
5) unit number
6) subunit number
For Flexi EDGE BTS's fault reasons "Incoming refer-ence clock has started to deviate rapidly" and differ-ence between the current and last stable DAC word, the rack and shelf values indicate the nominal DAC word in hexadecimal format.
For more information, see Alarm Structure.
Instructions in S14 Instructions in S15
84 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
METROSITE:
Fault reason: BSS synchronisation failed.
Instructions:
1. Check the clock cabling between the external clock source and the BCF.
Fault reason: External synchronisation signals disabled
Instructions:
1. Check the clock cabling between the LMU and the BCF.
2. Check that the GPS signal cable is connected to the LMU.
Fault reason: Temperature inside the TRX is high.
Instructions:
1. Check whether the following alarm is active for fan unit: 7605 BTS NOTIFICATION and follow the instruc-tions given for the alarm.
2. Even if there are no active alarms for the fan unit, check that no foreign objects obstruct the airflow.
3. If alarm 7605 is not active, ensure that the ambient temperature of the base station is within acceptablelim-its. Note: An alarm is activated when the TRX unit internal temperature exceeds +80C.Fault reason: Tem-perature inside the TRX is low.
Instructions:1. Ensure that the ambient temperature is within acceptable limits. also check the fan unit.Note: An alarm is activated when the TRX's internal tempera-ture is below -10C.
Fault reason: Fan unit is broken.
Instructions:
1. Check whether the fan unit is installed.
2. When there is a fan unit installed, check if something has jammed the fan unit and remove the jamming object. Otherwise replace the fan unit.
ULTRASITE:
Fault reason:
Power unit temperature is low.Instructions:
1. Ensure that the ambient temperature of the base station is within specified limits.
2. Check that the heater is working properly if equipped.
3. Replace the PWSx.Note: An alarm is activated when the PWSx internal temperature is below -10C.
Fault reason: Supply voltage to ESMA near low/high limit.
Description: The input voltage to the power supply of ESMA is close to its operating limit and is about to turn off power to TRX modules.
Instructions:
1. Check that the input voltage range of System module is within specified range.
2. Replace ESMA.
Fault reason: Supply voltage to ESEA near low/high limit.
Description: The input voltage to the power supply of ESEA is close to its operating limit and is about to turn off power to TRX modules.
Instruction:
1. Check that the input voltage range of System Exten-sion module is within specified range.
2. Replace ESEA.
Fault reason: Commissioned RF cabling does not match BTS configuration.
Description: Manually defined RF cabling in SCF is incorrect as verified against BTS Configuration received from BSC; it may result in degraded BTS per-formance.
Instruction:
1. Revise manually defined RF cabling in SCF against the actual configuration.
2. Enable RF cable autodetection (RFCAD) through commissioning wizard.
Note. Rack field contains information check for cable present (1 = TX, 2=RX main, 3=RX Div, 4=both RX paths from same Ant connection). Shelf filed contains the TRX number which contains Faulty RF cables.
Refer to latest Flexi EDGE BTS Commissioning (DN70130343) document for RF cable autodetection limitations.
Fault reason: ECxx RTC module cavity is broken.
Description: ECxx RTC module has detected that its cavity stepper motor cannot be moved or its phase detection logic is broken.
Instruction:
1. Issue a TRX lock/unlock to allow RTC module recon-figuration.
2. If alarm reappears, replace ECxx.
7602 BCF NOTIFICATION
DN0963445DN0963445 Issue 01
85
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: Transmission unit temperature is low.
Instructions:
1. Ensure that the ambient temperature of the base station is within specified limits.
2. Check that the heater is working properly if equipped.
3. Replace the transmission unit.
Note: An alarm is activated when the transmission unit's internal temperature is below -10C.
Fault reason: Power unit has lost connection to temper-ature sensor.
Instructions:
1. If another slot in the cabinet is empty, move the power unit into the empty slot.
2. The temperature sensor is probably broken. Temper-ature changes cannot be measured. Replace the power unit.
Fault reason: Transmission unit has lost connection to temperature sensor.Instructions:
1. Temperature sensor is probably broken. Tempera-ture changes cannot be measured. Replace the trans-mission unit.
Fault reason: BOI detected that connection to transmis-sion unit is lost.
Instructions:
1. Open the BTS Manager and check the active alarms.If this base station or other base stations beyond it otherwise operate properly, there is no need for an immediate repair. However, the transmission alarms for the faulty unit are not reported to the BSC nor the BTSManager.
2. Reset the faulty transmission unit.Note: Resetting the unit affects the traffic routed through it.
3. If the alarm reappears after the transmission unit reset, switch the cabinet power off and on.
4. If the alarm reappears after the recovery actions above, replace the faulty transmission plug-in unit.Fault reason: Cooling fan is broken.
Instructions:
1. If something has jammed the cooling fan unit, remove the jamming object.
2. Check which fan is giving the alarm from the supple-mentary information (rack/shelf/slot).
3. If the TSxx fan is alarming: Remove the TSxx in front of the fan. If the fan starts working, the removed TSxx is broken.
Fault reason: Incoming reference clock has started to deviate rapidly
Description: DAC word has been changed more than 408 steps from original DAC word (is usually within 2048 +/- 20), due to which the incoming synchronisa-tion reference PCM clock is drifted and causes OCXO oven oscillator to tune out of correct frequency and (if fault persists) will eventually cause handover failures.
Instructions:
1. Check at NetAct if there are any active core network synchronisation related alarms starting with code 1xxx and/or 2xxx.
2. Correct the synchronisation problem in upper part of network.
Flexi Multiradio:
Fault reason: External synchronisation signals disable-Description: LMU has operated without GPS signal over specified time and is turning its FCLK output off.
Instructions:
1. Check the GPS antenna fix status is OK with LMU-Manager. Adjust the GPS antenna so that satellites become visible.
2. Check that the GPS cable is correctly mated to LMU.
3. Check that the latest LMU SW is being used. Download newer SW if necessary.
4. Replace LMU.
Fault reason:
BSS synchronisation failed
Description: System module has lost synchronisation signal at synchronisation input (SIN) port.
Instructions:
1. If LMU provides the synchronisation, check if alarm 8202 is active and resolve it.
2. If another BTS is the synchronisation master, check if that it is up and alive.
3. Check that the synchronisation cabling is correctly mated between the units. If LMU is used, check also Q1 cabling and power supply to the LMU unit.
4. Replace ESMx.
7602 BCF NOTIFICATION
86 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
If the fan still does not rotate after the first TSxx was removed, reinsert it and remove the second TSxx.
If the fan starts rotating, the second TSxx is broken.
If the fan does not work after the TSxx removal test, the fan is broken and must be replaced.
4. For other fan alarms, replace the corresponding fan unit.
5. Otherwise, replace the BOI.
Note: This alarm is related to fans located in the back of the cabinet.
Fault reason: Cabinet fan is broken.
Instructions:
1. Check that the fan cable is connected to the door switch box.
2. If something has jammed the cabinet fan unit, remove the jamming object. Otherwise, replace the fan unit.
3. Replace the door switch box.
4. Otherwise, replace the BOI.
Note: This alarm is related to door fan.
Fault reason: Cooling fan speed has reduced from the set speed.
Instructions:
1. If the fan is dirty, clean the fan unit.
2. If something has jammed the cooling fan unit, remove the jamming object. Otherwise, replace the fan unit.
Note: This alarm is related to fans located in the back of the cabinet.
Fault reason:
Cabinet fan speed has reduced from the set speed.
1. If the fan is dirty, clean the fan unit.
2. If something has jammed the cabinet fan unit, remove the jamming object. Otherwise, replace the fan unit.
Note: This alarm is related to door fan.Fault reason: Heater is broken.
Instructions:
1. Check that the heater cable is connected to the door switch box.
2. Check that the AC power supply is OK by measuring AC from the cabinet connection box (the heater always requires AC power)
.3. Replace the faulty heater, or the heater is not installed although it is defined in the configuration file, therefore an alarm is issued. Install the heater.
Fault reason: ESMx System module cooling fan speed has reduced from the set speed.
Description: The cooling fan speed has reduced sub-stantially from the commanded fan speed.
Instructions:
1. Check that nothing obstructs the fan(s) from rotating.
2. Clean the fan unit of dust and/or dirt.
3. Replace the fan unit.
4. Replace ESMx.
Note: If "Temperature high/dangerously high" and/or 7621 alarm(s) are also active, perform these actions as soon as possible.
Fault reason: ESMx System module temperature high.
Description: ESMx System module has detected that its internal temperature has exceeded +90C/+194F.
Instructions:
1. Ensure that the ambient temperature of the base station is below +50C/+122F.
2. Check if any fan alarms are also active. If active, refer to fan alarm instructions to resolve.
3. Replace the ESMx (System Module).
Note that this alarm remains active if the temperature still increases and the "temperature dangerously high" alarm is activated.
Fault reason: ESMx System module unable to read internal temperature sensors
Description: There is no temperature measurement in the ESMx System module. All temperature sensors inside the module are broken. Fans are rotating at maximum speed.
Instructions:
1. Replace the ESMx.
Note: If fan alarm(s) are active at ESMx, perform this action as soon as possible.
Fault reason: ESMx System module cooling fan speed has increased from the set speed.
Description: The cooling fan speed of System module has increased substantially from the commanded fan speed.
Instructions:
1. Check the ESMx operational voltage as an increased ESMx voltage could lead to over speeding of the fans.
2. Replace the fan unit.
3. Replace ESMx.
7602 BCF NOTIFICATION
DN0963445DN0963445 Issue 01
87
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: Power unit output voltage fault.Instruc-tions:
1. Replace the faulty power unit. The cabinet has more than one power supply unit. The other power units are still functioning.
Fault reason: Power unit input voltage fault.Instruc-tions:
1. Ensure that the input voltage is correct.
2. Replace the faulty power unit. The cabinet has more than one power supply unit. The other power units are still functioning.
Fault reason: No connection to power unit.Instructions:
1. Check if the power unit is switched off.
2. If the power unit is on, replace the faulty power unit. The cabinet has more than one power supply unit. The other power units are still functioning.
Fault reason: Common rack PWS is jammed.Instruc-tions:
1. Give a one-minute power reset to the whole BTS cabinet.
2. Check the power unit(s) and power backplane con-nectors, and replace if faulty.
Fault reason: Common rack EAC I2C bus is jammed.
Instructions:
1. Give a one-minute power reset to the whole BTS cabinet.
2. Reset the BCF.
3. If the cabling between the BOI and the Interface board on the top side of the cabinet is OK, replace the Interface board.
4. Replace the BOI.
5. Replace the common backplane.Fault reason: Mismatch between BSC/MMI configuration file and the actual configuration.
Instructions:
1. Check that all units are installed and working OK.
2. Check that the actual base station configuration, HW configuration file and BSC configuration match. Make necessary corrections.
Fault reason: BTS Trace Collection Ongoing.
Description: User initiated BTS trace collection from the BTS Manager.
Instructions:
No repair actions required, alarm is cancelled when the BTS trace collection is stopped by the user.
Fault reason: FXxA module temperature value missing.
Description: The RF Module cannot report the temper-ature value or the sensor is faulty.
Instructions:
1. Block/unblock the RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Cooling fan out of order.
Description: The RF Module cooling fan is not rotating at the specified speed.
Instructions:
1. Check the fan and cabling.
2. Block/unblock the RF Module.
3. Replace the faulty fan assembly.
Note! Perform the steps below in the listed order until the alarm disappears.
Fault reason: Shared FxxA module detected two syn-chronisation master sources.
Description: Shared RFM has detected two RP1 sync master
Instructions:
1. Commission any of the SMs in RP1 sync slave mode.
Fault reason: FxxA module detected no synchronisa-tion master at startup.
Description: RFM is not able to find RP3-01 master link during start-up.
Instructions:
Connect the sync cable between RP1 sync master and RFM.
Fault reason: Invalid BTS Topology detected.
Description: BTS has detected Topology which is invalid as per the rules defined.
Instructions:
1. Correct Topology by removing invalid optical links and perform BCF reset.
7602 BCF NOTIFICATION
88 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: BSS synchronisation failed.
Instructions:
1. Check the clock cabling between the external clock source and the BCF.
Fault reason: External synchronisation signals disabled
Instructions:
1. Check that the master clock source is OK.
2. Check the clock cabling between the LMU and the BCF.
3. Check that the GPS signal cable is connected to the LMU.Other fault reasons
Instructions:See the Alarm Descriptions document included in the BTS SW release binder of the alarming base station type.
Flexi EDGE:
Fault reason: External synchronisation signals dis-abled.
Description: LMU has operated without GPS signal over specified time and is turning its FCLK output off.
Instructions:
1. Check the GPS antenna fix status is OK with LMU-Manager. Adjust the GPS antenna so that satellites become visible.
2. Check that the GPS cable is correctly mated to LMU.
3. Check that the latest LMU SW is being used. Download newer SW if necessary.
4. Replace LMU.
Fault reason: BSS synchronisation failed.
Description: ESMA System module has lost synchroni-sation signal at synchronisation input (SIN) port.
Instructions:
1. If LMU provides the synchronisation, check if alarm 8202 is active and resolve it.
2. If another BTS is the synchronisation master, check if that it is up and alive.
3. Check that the synchronisation cabling is correctly mated between the units. If LMU is used, check also Q1 cabling and power supply to the LMU unit.
4. Replace ESMA.
Fault reason: ESMA System module cooling fan speed has reduced from the set speed.
Description: The cooling fan speed has reduced sub-stantially from the commanded fan speed.
Instructions:
1. Check that nothing obstructs the fan(s) from rotating.
Fault reason: Supply voltage to ESMx near low/high limit
Description: The input voltage to the power supply of ESMx is less than 40VDC or more than 58VDC.
Instructions:
1. Check that the input voltage range of System module is within specified range.
2. Replace ESMx.
Fault reason: ESMx System module detected GSM/EDGE incompatible RF module
Description: A non-GSM/EDGE capable RF module is connected to ESMx System module
Instructions:
1. Remove incompatible RF module from ESMx port or RFM port
2. Replace ESMx
Fault reason: Baseband bus minor operation error occurred in ESMx System module
Description: Baseband bus minor operation error has degraded in ESMx System module.
Instructions:
1. Issue BCF reset from (remote) BTS manager.
2. Issue HW reset from (remote) BTS manager.
3. Replace ESMx.
7602 BCF NOTIFICATION
DN0963445DN0963445 Issue 01
89
Changes in RG20(BSS)
Id:0900d8058076d66f
2. Clean the fan unit of dust and/or dirt.
3. Replace the fan unit.
4. Replace ESMA.
Note: If "Temperature high/dangerously high" and/or 7621 alarm(s) are also active, perform these actions as soon as possible.
Description: ESMA System module cooling fan speed has increased from the set speed.
Fault reason: The cooling fan speed of System module has increased substantially from the commanded fan speed.
Instructions:
1. Check the ESMA operational voltage as an increased ESMA voltage could lead to overspeeding of the fans.
2. Replace the fan unit.
3. Replace ESMA.
Fault reason: ESMA System module temperature high.
Description: ESMA System module has detected that its internal temperature has exceeded +90C/+194F.
Instructions:
1. Ensure that the ambient temperature of the base station is below +50C/+122F.
2. Check if any fan alarms are also active. If active, refer to fan alarm instructions to resolve.
3. Replace the ESMA.Note that this alarm remains active if the temperature still increases and the "temper-ature dangerously high" alarm is activated.
Fault reason: ECxx RTC module connected to wrong port.
Description: ECxx RTC module is not connected to port 1/2/3 of ESMA System module.
Instructions:
1. Connect ECxx to ESMA port 1, 2 or 3 and issue a BCF reset.
Fault reason: EXxx TRX module connected to wrong port.
Description: EXxx TRX Module is not connected to ESEA System Extension module.
Instructions:
1. Connect EXxx module to ESEA.
Fault reason: ESEA System Extension module con-nected to wrong port.Description: ESEA System Exten-sion module is not connected to port 6 of ESMA System Module.
1. Connect ESEA to port 6 of ESMA, and issue a BCF reset.
7602 BCF NOTIFICATION
90 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: Unknown module connected to Esxx System (Extension) module.
Description: ESMA System module does not recognise the module connected to this port. SW release incom-patibility with the connected HW.
Instructions:
1. Check the HW SW compatibility from the SW release binder.
a. If the module is compatible with the current SW running in the BTS, replace the module.
b. If the module is not compatible with the current SW running in the BTS, check which SW version supports the module. Upgrade the BTS SW to the version that supports the module.
2. Remove the unknown module
Fault reason: ESEA System Extension module temper-ature high
Description: Internal temperature of ESEA System Extension module has exceeded +85C/+185F.
Instructions:
1. Ensure that the ambient temperature of the base station is below +50C/+122F.
2. Check if fan alarm is also active. If active, refer to fan alarm instructions to resolve.
3. Replace ESEA.Note that this alarm remains active if the temperature still increases and the "temperature dangerously high" alarm is activated.
Fault reason: ESMA System module unable to read internal temperature sensors.
Description: There is no temperature measurement in the ESMA System module. All temperature sensors inside the module are broken. Fans are rotating at maximum speed.
Instructions:
1. Replace the ESMA.Note: If fan alarm(s) are active at ESMA, perform this action as soon as possible.
Fault reason: EOCA Optical module connected to wrong port
Description: EOCA Optical module is connected to both an ESMA System Extension module and an ESEA System Extension module at the same time. EXxx TRX modules cannot be connected to ESMA system module when an ESEA System Extension module is equipped, so the ESMA System module connection(s) to the EOCA Optical Unit are incorrect.
Instructions:
1. Connect Local Optical BUS connections to ESEA only, when ESEA is equipped.
7602 BCF NOTIFICATION
DN0963445DN0963445 Issue 01
91
Changes in RG20(BSS)
Id:0900d8058076d66f
Faut Reason: BTS Trace Collection Ongoing
Description: User initiated BTS trace collection from BTS Manager.
Instructions:No repair actions required, alarm is can-celled when BTS trace collection is stopped by the user.
Fault reason: Supply voltage to ESMA near low/high limit
Description: The input voltage to the power supply of ESMA is close to its operating limit and is about to turn off power to TRX modules.
Instruction:The input voltage to the power supply of ESMA is less than 44VDC or more than 58VDC.
1. Check that the input voltage range of System module is within specified range.
2. Replace ESMA.Fault reason: Supply voltage to ESEA near low/high limit.
Description: The input voltage to the power supply of ESEA is close to its operating limit and is about to turn off power to TRX modules.
Instruction:The input voltage to the power supply of ESEA is less than 44VDC or more than 58VDC.
1. Check that the input voltage range of System Exten-sion module is within specified range.
2. Replace ESEA.Fault reason: Commissioned RF cabling does not match BTS configurationDescription: Manually defined RF cabling in SCF is incorrect as verified against BTS Configuration received from BSC; it may result in degraded BTS performance
Instruction:
1. Revise manually defined RF cabling in SCF against the actual configuration.
2. Enable RF cable autodetection (RFCAD) through commissioning wizard.
Note 1: Rack field contains information check for cable present (1 = TX, 2=RX main, 3=RX Div, 4=both RX paths from same Ant connection).
7602 BCF NOTIFICATION
92 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Note 2: Shelf field contains the TRX number which contains Faulty RF cables.
Note 3: Also, there may be more RF cabling errors introduced during commissioning, but only one of those is reported.
Note 4: Refer to latest Flexi EDGE BTS Commissioning (DN70130343) document for RF cable autodetection limitations
Note that if the DDU is shared across two sectors, a BCF reset is needed.
Fault reason: ECxx RTC module cavity is broken
Description: ECxx RTC module has detected that its cavity stepper motor cannot be moved or its phase detection logic is broken.
Instruction:
1. Issue a TRX lock/unlock to allow RTC module recon-figuration.
2. If alarm reappears, replace ECxx.
Fault reason: Incoming reference clock has started to deviate rapidly
Description: DAC word has been changed more than 408 steps from original DAC word (is usually within 2048 +/- 20), due to which the incoming synchronisa-tion reference PCM clock is drifted and causes OCXO oven oscillator to tune out of correct frequency and (if fault persists) will eventually cause handover failures.
Instructions:
1. Check at NetAct if there are any active core network synchronisation related alarms starting with code 1xxx and/or 2xxx.
2. Correct the synchronisation problem in upper part of network.
Instructions in S14 Instructions in S15
Cancelling the alarm:
This is a start/cancel type alarm. Alarm is cancelled automatically.
Cancelling the alarm:
This is a start/cancel type alarm. Alarm is cancelled automatically, except in the case of the fault reasons "Commissioned RF cabling does not match BTS config-uration" and "ECxx RTC module cavity is broken" which require that you cancel the alarm manually.
7602 BCF NOTIFICATION
7603 BCF FAULTY
Change description: Instructions changed
Instructions in S14 Instructions in S15
This is a start/cancel type alarm. The alarm is cancelled automatically.
In UltraSite Base Station alarm has to be canceled manually if BaseBand hopping is used.
This is a start/cancel type alarm. The alarm is cancelled automatically.
In UltraSite base stations alarm has to be cancelled manually if baseband hopping is used.
DN0963445DN0963445 Issue 01
93
Changes in RG20(BSS)
Id:0900d8058076d66f
METROSITE and ULTRASITE:
All fault reasons
Instructions:
1. Check whether the following alarm is active:
7606 TRX FAULTY
and follow the instructions given for the alarm. If neces-sary, replace all faulty units indicated in the active alarm(s).
METROSITE, ULTRASITE, Flexi EDGE and Flexi Mul-tiradio:
All fault reasons
Instructions:
1. Check whether either of the following alarm is active:
7606 TRX FAULTY
7607 TRX OPERATION DEGRADED
and follow the instructions given for the active alarm(s).
7603 BCF FAULTY
7604 BTS OPERATION DEGRADED
Change description: Instructions changed.
Instructions in S14 Instructions in S15
94 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
METROSITE:
Other fault reasons
Instructions:
1. Check whether either of the following alarms is active:
7606 TRX FAULTY
7607 TRX OPERATION DEGRADED
and follow the instructions given for the active alarm(s).
ULTRASITE:
Fault reason: Remote tune combiner temperature is dangerously high.
Instructions:
1. Ensure that the ambient temperature of the base station is within specified limits.
2. Check the cabinet fans.
3. Replace the remote tune combiner.
Fault reason: Remote tune combiner temperature is low.
Instructions:
1. Ensure that the ambient temperature of the base station is within specified limits.
2. Check the cabinet heater if it is installed.
3. Replace the remote tune combiner.
Other fault reasons
Instructions:
1. Check whether either of the following alarms is active:
7606 TRX FAULTY
7607 TRX OPERATION DEGRADED
and follow the instructions given for the active alarm(s).
METROSITE:
Other fault reasons
Instructions:
1. Check whether either of the following alarms is active:
7606 TRX FAULTY
7607 TRX OPERATION DEGRADED
and follow the instructions given for the active alarm(s).
ULTRASITE:
Fault reason: Remote tune combiner temperature is dangerously high.
Instructions:
1. Ensure that the ambient temperature of the base station is within specified limits.
2. Check the cabinet fans.
3. Replace the RTxx.
Note: An alarm is activated when the RTxx unit internal temperature exceeds +70°C.Fault reason: Remote tune combiner temperature is low.
Instructions:
1. Ensure that the ambient temperature of the base station is within specified limits.
2. Check that the heater is working properly if equipped.
3. Replace the RTxx.
Note: An alarm is activated when the RTxx unit internal temperature is below -10°C.Fault reason: Rx levels differ too much between main and diversity antennas.
Instructions:
1. Check the RSSI measurements by BTS Manager.
2. Check and measure the antenna lines.
3. Check the BTS RF cables and connections.
4. Replace the combiner unit. Check that the RXDL parameter at the BSC is set to a reasonable value, taking into account the site conditions in order to prevent unnecessary alarms.
5. Replace the TSxx unit.
7604 BTS OPERATION DEGRADED
DN0963445DN0963445 Issue 01
95
Changes in RG20(BSS)
Id:0900d8058076d66f
Other fault reasons
Instructions:
1. Check whether either of the following alarms is active:
7606 TRX FAULTY
7607 TRX OPERATION DEGRADED
and follow the instructions given for the active alarm(s).
Flexi EDGE and Flexi Multiradio:
Other fault reasons
Instructions:
1. Check whether either of the following alarms is active:
7606 TRX FAULTY
7607 TRX OPERATION DEGRADED
and follow the instructions given for the active alarm(s).
7604 BTS OPERATION DEGRADED
7606 TRX FAULTY
Change description: Meaning improved, SIF structures added, Instructions changed.
Meaning in S14 Meaning in S15
alarm trx_faulty_a = 0x7606,
alarm_text = 'TRX FAULTY',
(
diagn_info array(6) of byte;
);
alarm trx_faulty_a = 0x7606,
alarm_text = 'TRX FAULTY',
(
diagn_info array(6) of byte;
trx_list array(15) of trx_id_t;
);
SIF structure in S14 SIF structure in S15
TRX_LIST Faulty TRX ids
Instructions in S14 Instructions in S15
96 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: EXxx TRX detected no connection to ERxx DDU/ECxx RTC
2. Check that ECxx/ERxx and EXxx are of same fre-quency (sub-)band.
Fault reason: EXxx TRX detected no connection to ERxx DDU/ECxx RTC
2. Check that ECxx and EXxx are of same frequency band.
Fault reason: Both Tx cables missing for DPTRX.
Description: Both Tx cables are detected to be missing from the DPTRX object.
Instructions:
1. Check that all Tx cables are fully mated between the EXxx, EWxA and ERxx.
2. Replace EWxA.
3. Replace EXxx.
4. Replace ERxx.
Fault reason: EXxx TRX detected no connection to ERxx DDU/ECxx RTC
2. Wait for DDU to come in supervisory (Fixed green LED on DDU).
Issue a sector reset to restart RF cable autodetection.
Fault reason: EXxx TRX detected no connection to ERxx DDU/ECxx RTC
2. Check that ECxx/ERxx and EXxx are of same fre-quency (sub-)band.
Fault reason: RF cabling missing for DPTRX.
Description: RF cabling is detected to be missing from DPTRX object.
Instructions:
1. Check that all Tx and Rx cables are fully mated between the EXxx, EWxA and ERxx.
2. Replace EWxA.
3. Replace EXxx.
4. Replace ERxx.
Fault reason: ECxx RTC module cavity is broken.
Description: ECxx RTC module has detected that its cavity stepper motor cannot be moved or its phase detection logic is broken.
Instructions:
1. Issue a TRX lock/unlock to allow RTC module recon-figuration.
2. If alarm reappears, replace ECxx.
Fault reason: Phase difference between Tx signals is too high with DPTRX.
Description: If alarm is raised on IDD/DPTRX object serving the BCCH AND another IDD/DPTRX object is available in the sector, then BSC will automatically reconfigure BCCH to the working IDD/DPTRX object. Otherwise IDD/DP enabled sector operates with reduced performance.
Instructions:
1. Check that Phase Detector cable is correctly mated between EWxA and EXxx.
2. Replace Phase Detector cable.
3. Replace EWxA.
4. Replace EXxx.
7606 TRX FAULTY
DN0963445DN0963445 Issue 01
97
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: PDU control has switched off EXxx TRX Module
Description: Either System (extension) module has switched OFF power to EXxx TRX module due to low/high voltage or power is toggled OFF by user from BTS Manager power control menu.
Instructions:
1. Check that ESMA/ESEA input voltage is within the normal operating range.
2. Power ON the PDU from BTS Manager (BTS Control | PowerControl).
3. Replace ESMA/ESEA.
Fault reason: PDU control has switched off ECxx TRX Module
Description: Either System module has switched OFF power to ECxx RTC module due to low/high voltage or power is toggled OFF by user from BTS Manager power control menu.
Instructions:
1. Check the ESMA input voltage is within the normal operating range.
2. Power ON the PDU from BTS Manager (BTS Control | Power Control).
3. Replace ESMA.
FLEXI MULTIRADIO:
Fault reason: GSM FCLK/FN synchronisation failure during startup in ESMx System module
Description: During start-up GSM synchronisaton was not achieved by ESMx System module
Instructions:
1. Issue a HW Reset to ESMx module and observe if the alarm still present.
2. If alarm is coming again then replace ESMx System module
Fault reason: GSM FCLK/FN Synchronisation failure during runtime in ESMx System module
Description: For ESMx GSM synchronisation failure occurs during run-time
Instructions:
1. Issue a HW Reset to ESMx System module and observe if the alarm still present.
2. If alarm is coming again then replace ESMx System module.
7606 TRX FAULTY
98 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: EXxx TRX module has missing transmis-sion time slot allocation
Description: TRXsig and/or TCH allocation for EXxx TRX module is missing from the Abis allocation.
Instructions:
1. Check that BTS configuration and Abis time slot allo-cation matches between the SCF, installed units and the BSC.
2. Add missing time slot allocation to the SCF/BTS by appending the commissioning file.
Fault reason: RF Module Filter input power missing
Description: The RF Module filter has measured too low TX power
Instructions:
1. Perform Sector lock/unlock or block/de-block.
2. Replace RF Module
Fault reason: FxxA module configuration failed
Description: The RF Module configuration failed because of a HW or SW fault.
Instructions:
1. Switch OFF/ON the power to alarming RFM module to restart it.
2. If still the alarm reappears then replace the alarming RFM module.
Fault reason: RF Module critical file not found
Description: A critical configuration file is missing from the RF Module.
Instructions:
1. Switch OFF/ON the alarming RFM module.
2. Verify that the HWP1 file is present in the RF Module and download the file if missing. Reset the RF Module.
3. If alarm reappears then replace the alarming RFM module.
Fault reason: FxxA frame clock missing
Description: The System Module clock reference differs from the RF Module clock.
Instructions:
1. Check the cables between the System Module and the alarming RF Module.
2. Block/unblock the alarming RF Module.
3. If that does not help, block/unblock the site.
4. If that does not help, replace the alarming RF Module.
7606 TRX FAULTY
DN0963445DN0963445 Issue 01
99
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: Optical Link Synchronisation Error
Description: The baseband bus between the System Module and RF Module is out of synchronization.
Instructions:
1. Check the cables between the System Module and the alarming RF Module.
2. Block/unblock the alarming RF Module.
3. If that does not help, block/unblock the site.
4. If that does not help, replace the alarming RF Module.
Fault reason: Optical link configuration error
Description: The RF Module baseband bus is config-ured incorrectly.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Transmission error on optical link connec-tion
Description: There is an error in the baseband or optical bus.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Tx out of order
Description: The RF Module TX path is not usable.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Rx Out of Order
Description: The RF Module RX RF synthesizer is not locked.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: FxxA module Out of Order
Description: The RF Module is out of order because of a software or hardware fault
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
7606 TRX FAULTY
100 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: FxxA Module Overheating
Description: The RF Module TX path is not usable.
Instructions:
1. Check the fans and ensure that the ambient temper-ature on the site is acceptable.
2. Block/unblock the alarming RF Module.
3. If that does not help, replace the alarming RF Module.
Fault reason: RF Module Power Output Faulty
Description: The Power Supply has detected an over voltage, under voltage or over current in the RF Module.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Power on Self Test failed
Description: An RF Module power-on self-test failed at start-up.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Module clock faulty
Description: The FXxA module has lost the lock to the incoming clock.
Instructions:
1. Check the cables between the System module and FXxA module.
2. Block/de-block the alarming FXxA module.
3. Replace FXxA.
Fault reason: Antenna Line failure
Description: Radio Module Filter has detected over current on the antenna line. The antenna line may be damaged (short circuit) or some antenna line device is causing overload.
Instructions:
1. Check the antenna line and antenna line devices. Fix or replace the faulty parts/devices.
2. If that does not help, replace the alarming RF Module.
7606 TRX FAULTY
DN0963445DN0963445 Issue 01
101
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: VSWR measurements exceed Major threshold
Description: Radio Module Filter has detected a VSWR value exceeding the defined level. The antenna line is mismatched or damaged.
Instructions:
1. Check the antenna cables, connectors, antenna and possible antenna line devices.
2. Check the antenna line (TX-cable-antenna) imped-ance matching.
3. Lock/unlock or block/deblock the sector.
4. If the alarm still appears then replace alarming RFM module.
Fault reason: Filter unit operation failed
Description: A filter has not been able to tune on an appropriate sub-band properly (tuning failure), or another major failure has been detected by the filter (unit faulty).
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Mod-ule/Filter.
Fault reason: FxxA module blocked locally
Description: A RFM is locally blocked by an Element Manager command.
Instructions: No repair actions required, alarm is can-celled when RFM is locally deblocked from Element Manager.
Fault reason: Baseband DSP module SW download in ESMx System module failed
Description: Software download has failed on the inte-grated baseband DSP module
Instructions:
1. lock/unlock the BCF.
2. Power OFF and ON the ESMx.
3. If the alarm still persist then replace the ESMx
Fault reason: Internal failure occurred during TRX con-figuration
Description: There was no internal response or timeout occurred or nack received during TRX configuration.
Instructions:
1. Lock/Unlock the TRX
2. Check the configuration set at BSC.
3. Give BCF reset.
7606 TRX FAULTY
102 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: ESMx System module has lost connec-tion to FXxA module
Description: System Module has lost connection to the RF Module
Instructions:
1. Check the RP3 cable between the ESMx the discon-nected FXxA.
2. Reconnect the FXxA to ESMx.
3. Replace FXxA.
Fault reason: Baseband resource not available for con-figured TRX objects
Description: A TRX object configured at BSC, statically maps to a Module ID. This module ID is not mapped to any Baseband CORE ID in System module
Instructions:
1. BTS Configuration file needs to be updated.
2. Remove the TRX object configured from BSC on which the alarm is reported.
3. Give BCF reset
Fault reason: ESMx System module internal HW failure
Description: Internal initialisation failure occurred in ESMx System module
Instructions:
1. Issue BCF reset from (remote) BTS manager.
2. Replace ESMx.
Fault reason: Internal baseband bus fault has occurred in ESMx System module
Description: Internal baseband bus fault occurred in ESMx System module.
Instructions:
1. Issue BCF reset from (remote) BTS manager.
2. Issue HW reset from (remote) BTS manager.
3. Replace ESMx.
Fault reason: Optical link fault detected by baseband module in ESMx System module
Description: SFP error occurred on the optical RP3 link
Instructions:
1. Check that the SFP point connections are correctly configured.
2. Issue BCF reset from (remote) BTS manager.
3. Issue HW reset from (remote) BTS manager.
7606 TRX FAULTY
DN0963445DN0963445 Issue 01
103
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: Frequency budget exceeded for FxxA module
Description: TRX allocation in the sector failed due to config error (TRX frequency does not fit into with fre-quencies of other TRXs allocated to a pipe)
Instructions:
1. Reconfigure the TRX in some other sector.
2. Add a pipe in the sector via Append commissioning
Fault reason: Power budget exceeded for FxxA module
Description: TRX allocation in the sector failed due to config error (limited transmission power available)
Instructions:
1. Reconfigure the TRX in some other sector
2. Add a pipe in the sector via Append commissioning
Fault reason: Not enough capacity available on FxxA module for 2G TRX resources
Description: Peer technology allocated RF resources meant for 2G TRX objects
Instructions:
1. Reconfigure the TRX in some other sector.
2. Add a pipe in the sector via Append commissioning
3. Change peer technology's RF resource allocation
Fault reason: Not enough frequency budget available for 2G TRX resources
Description: Frequencies of 2G TRX objects do not fit with the peer technology's carrier frequencies
Instructions:
1. Reconfigure the TRX in some other sector.
2. Add a pipe in the sector via Append commissioning
3. Change peer technology carrier frequencies
Fault reason: Not enough power budget available for 2G TRX resources
Description: Peer technology carriers configured more transmission power in a pipe and not enough power available for 2G TRX object
Instructions:
1. Reconfigure the TRX in some other sector.
2. Add a pipe in the sector via Append commissioning
3. Change peer technology carrier power allocation
7606 TRX FAULTY
104 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: HW capacity exceeded for FxxA module
Description: RF module could not allocated enough RF resources for TRX
Instructions:
1. Reconfigure the TRX in some other sector.
2. Add a pipe in the sector via Append commissioning
Fault reason: TRX resource lost due FxxA module HW fault
Description: FxxA module resource configured with a 2G TRX reported a HW fault.
Instructions:
1. Reconfigure the TRX to some other sector.
2. Replace FxxA.
Fault reason: For logical sector configured at BSC no HW has been specified in SCF
Description: Hardware not specified (Local sector infor-mation) in SCF for the configured BTS.
Instructions:
1. Remove the alarmed BTS object from the BSC.
2. Add the local sector information for the alarmed BTS defined at BSC via BTS manager append commission-ing.
3. Issue BCF reset from (remote) BTS manager.
7606 TRX FAULTY
7607 TRX OPERATION DEGRADED
Change description: Meaning improved, SIF structures added, Instructions changed and removed.
Meaning in S14 Meaning in S15
alarm trx_operation_degraded_a = 0x7607,
alarm_text = 'TRX OPERATION DEGRADED', flag_count = 1,
(
diagn_info array(6) of byte;
);
alarm trx_operation_degraded_a = 0x7607,
alarm_text = 'TRX OPERATION DEGRADED', flag_count = 1,
(
diagn_info array(6) of byte;
trx_list array(15) of trx_id_t;
);
SIF structure in S14 SIF structure in S15
TRX_LIST Faulty TRX ids
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
105
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: EXxx TRX module detected only one Rx signal during RF cable autodetection.
Description: RF cable autodetection found Rx signal missing from the sector where Rx diversity is being used.
Instructions:
1. Check that the Rx cabling between EXxx and ERxx are correctly mated. Check the condition of cables and connectors.
2. If DDU is shared between two sectors, issue BCF reset, else issue a sector reset.
3. Recommission the site with manual cabling, if Rx diversity is not to be used.
4. Replace ERxx.
5. Replace EXxx.
Fault reason: EXxx TRX module detected only one Rx signal during RF cable autodetection.
Description: RF cable autodetection found Rx signal missing from the sector where Rx diversity is being used.
Instructions:
1. Check that the Rx cabling between EXxx and ERxx are correctly mated. Check the condition of cables and connectors.
2. If DDU is shared between two sectors, issue BCF reset, else issue a sector reset.
3. Check that ECxx/ERxx and EXxx are of same fre-quency (sub-)band.
4. Recommission the site with manual cabling, if Rx diversity is not to be used.
5. Replace ERxx.
6. Replace EXxx.
Flexi Multiradio:
Fault reason: Two Rx diversity branches lost with 4UDDescription: ERxx DDU module that supplies the two diversity Rx signals for 4UD is lost.
Instructions:
1. Check that the bus and power cables are correctly mated between ESxx, EXxx and ERxx.
2. Replace ERxx.
3. Replace EXxx.
7607 TRX OPERATION DEGRADED
106 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: RF baseband energy is too high.
Description: The TX feedback signal power is too high.
Instructions:
1. Perform RFM block/de-block.
2. Replace FXxA module.
Fault reason: RF module file not found.
Description: The RF Module SW detected that a non-critical configuration file is missing.
Instructions:
1. Switch OFF/ON the alarming FXxA module.
2. Replace FXxA module.
Fault reason: FxxA Module Gain adjusting Failure.
Description: The TX output power adjustment failed.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: No feedback signal.
Description: The feedback signal to predistortion is too weak or missing. The TX performance is degraded.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Transmission quality deteriorated.
Description: The TX signal adjustment fails.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
7607 TRX OPERATION DEGRADED
DN0963445DN0963445 Issue 01
107
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: Detected unidentified unit connected to ESMx or FxxA module
Description: The permanent memory in the module is corrupted and the module product code or serial number is missing/unknown.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Configuration File Corrupted
Description: The RF Module SW detected conflicting or corrupted configuration data
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: RF output power reduced to prevent module overheating
Description: The highest temperature exceeds the power decrease limit.
Instructions:
1. Check the fans and ensure that the ambient temper-ature on the site is acceptable.
2. Block/unblock the alarming RF Module.
3. If that does not help, replace the alarming RF Module.
Fault reason: FPGA SW update failed
Description: The FPGA software update has failed.
Instructions:
1. Block/unblock the alarming FXxA module.
2. Replace FXxA.
Fault reason: Mast Head Amplifier Fault
Description: The Masthead Amplifier (MHA) does not work properly. The received RF signal level is decreased.
Instructions:
1. Check the antenna cables and connectors towards the MHA. Fix or replace the broken parts.
2. Restart the MHA by blocking and unblocking the Flexi Radio (FR) Module.
NOTE! This operation affects all antenna lines and cells related to the FR Module, not just the faulty one. If the alarm reappears, replace the alarming module.
7607 TRX OPERATION DEGRADED
108 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: VSWR measurements exceed Minor threshold
Description: Radio Module Filter has detected a VSWR value exceeding the defined level. The antenna line is slightly mismatched.
Instructions:
1. Check the antenna cables, connectors, antenna and possible antenna line devices.
2. Check the antenna line (TX-cable-antenna) imped-ance matching.
Fault reason: Low noise amplifier failure
Description: The Filter has detected a malfunction in the LNA unit.
Instructions:
1. Block/unblock the alarming RF Module.
2. If that does not help, replace the alarming RF Module.
Fault reason: Antenna line device HW failure
Description: A hardware failure detected by an antenna line device. Usually this is a permanent fault (the hardware is broken).
Instructions:
1. Block/unblock the Radio module to give a power-off reset to the antenna line devices.
2. If the reset does not cancel the alarm or the alarm continuously reappears, replace the antenna line device.
Fault reason: Antenna line device configuration failure
Description: An antenna line or antenna line device is incorrectly configured.
Instructions:
1. Update the proper SW to antenna line device.
2. Check/correct the antenna line configuration.
3. Replace antenna line device.
Fault reason: Antenna line device operation failure
Description: The device is not working properly, the configuration is not valid, or a given parameter are incorrect.
Instructions:
1. Check the functionality of the antenna line device.
2. Check the compatibility between the antenna line device and the BTS SW.
3. Check that the given parameters are in the valid range.
4. Replace antenna line device.
7607 TRX OPERATION DEGRADED
DN0963445DN0963445 Issue 01
109
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: Baseband bus operation has degraded on RP3 link in ESMx System module
Description: Baseband bus operation has degraded on RP3 link in ESMx System module.
Instructions:
1. Issue BCF reset from (remote) BTS manager.
2. Issue HW reset from (remote) BTS manager.
Fault reason: No resources available for IDD Auxiliary path allocation in FxxA module
Description: System fails to allocate Auxiliary path for the IDD TRX
Instructions:
1. Configure the IDD TRX into some other sector having at least two pipes.
2. Allocate another pipe in the same sector via Append commissioning.
3. Change the per TRX power via Append commission-ing, so that auxiliary TRX can be accommodated in the pipe.
Fault reason: Commissioning file specifies too few antennas for Rx diversity
Description: Not enough antennas are available for configuring Tx auxiliary path for an IDD TRX object
Instructions:
1. Add another antenna or pipe to the local sector
Instructions in S14 Instructions in S15
Fault reason: Phase difference between Tx signals is too high with DPTRX.
Description: Phase difference between combined Tx signals is too high, resulting in reduced Tx output power.
Instructions: If alarm is raised on IDD/DPTRX object serving the BCCH AND another IDD/DPTRX object is available in the sector, then lock the BCCH TRX object. BSC will reconfigure BCCH to the working IDD/DPTRX object. Otherwise IDD/DP enabled sector operates with reduced performance.
1. Check that the Phase Detector cable is correctly mated between EWxa and EXxx.
2. Replace the Phase Detector cable.
3. Replace EWxA.
4. Replace EXxx.
7607 TRX OPERATION DEGRADED
7608 TRX NOTIFICATION
Change description: SIF Structures added, Instructions changed
SIF Structure in S14 SIF Structure in S15
110 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
TRX_LIST Faulty TRX ids
Instructions in S14 Instructions in S15
Fault reason: ERxx DDU module SW upgrade impossi-ble, unknown manufacturer.
Description: EXxx TRX module cannot identify con-nected ERxx DDU module. SW release incompatibility with connected HW.
Instructions:
1. Download and activate the latest release of the BTS SW to ESMA System Module.
2. Replace ERxx.
Fault reason: ERxx DDU module SW upgrade impossi-ble, unknown manufacturer.
Description: EXxx TRX module cannot identify con-nected ERxx DDU module.
Instructions:
1. Download and activate the latest release of the BTS SW to the BTS Site.
7608 TRX NOTIFICATION
7612 SITE POWERING FAULTY
Change description: Instructions changed
Instructions in S14 Instructions in S15
Fault reason: CCUA PSM alarm 1.
Instructions:
1. Use the PSM Manager software to check active SISU alarms and follow the instructions given in the SISU operating manual.
Fault reason: CCUA PSM alarm 1.
Instructions:
1. Use the PSM Manager software to check active SISU alarms and follow the instructions given in the SISU operating manual.
Flexi EDGE and Flexi Multiradio:
Fault reason: Battery backup Alarm 1.
Description: Critical alarm is activated in external site support equipment.
Instructions:
1. Connect to the external site support equipment to find the alarming unit and resolve the fault.
7613 SITE POWERING OPERATION DEGRADED
Change description: Instructions changed
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
111
Changes in RG20(BSS)
Id:0900d8058076d66f
Fault reason: CCUA PSM alarm 2.
Instructions:
1. Use the PSM Manager software to check active SISU alarms and follow the instructions given in the SISU operating manual.
Fault reason: CCUA PSM alarm 2.
Instructions:
1. Use the PSM Manager software to check active SISU alarms and follow the instructions given in the SISU operating manual.
Flexi EDGE and Flexi Multiradio:
Fault reason: Battery backup Alarm 2.Description: Major alarm is activated in external site support equip-ment.
Instructions:
1. Connect to the external site support equipment to find the alarming unit and resolve the fault.
Fault reason: PSF Battery backup maintenance alarm.
Description: Alarm of severity major is activated in FPxx Power module.
Instructions:
1. Ensure that the ambient temperature of the base station is below +50C/+122F.
2. Check that nothing obstructs the fan(s) from rotating.
3. Clean the fan unit of dust and/or dirt.
4. Check that power consumption of the BTS is lower than nominal output power provided by FPMA. 5. Replace the alarming sub module.
7613 SITE POWERING OPERATION DEGRADED
7614 SITE POWERING NOTIFICATION
Change description: Instructions changed
Instructions in S14 Instructions in S15
Fault reason: CCUA PSM alarm 3.
Instructions:
1. Use the PSM Manager software to check active SISU alarms and follow the instructions given in the SISU operating manual.
Fault reason: CCUA PSM alarm 3.
Instructions:
1. Use the PSM Manager software to check active SISU alarms and follow the instructions given in the SISU operating manual.
Flexi EDGE and Flexi Multiradio:
Fault reason: Battery backup Alarm 3.
Description: Minor alarm is activated in external site support equipment.
Instructions:
1. Connect to the external site support equipment to find the alarming unit and resolve the fault
7615 RTS IS IN TEST USE
Change description: Meaning improved
Meaning in S14 Meaning in S15
112 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
The TRX and the time slot tested are reported to the BSC. The time slot cannot be used for call functions during the test.
Internal O&M software is testing time slots during the TRX loop test. The TRX and the time slot tested are reported to the BSC. The time slot cannot be used for call functions during the test.
Flexi EDGE and Flexi Multiradio:
Radio TS is in test use. Radio Time Slot(s) of EXxx TRX module are undergoing a TRX (loop) test started from (remote) BTS Manager.
7615 RTS IS IN TEST USE
7616 OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED
Change description: Instructions changed
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
113
Changes in RG20(BSS)
Id:0900d8058076d66f
1. Check the Abis connection.
2. If the Abis connection is OK, replace the faulty VIFA unit
METROSITE:
Fault reason :
Oven oscillator adjustment function interrupted.
Instructions:
1. Check the Abis connection.
2. If the Abis connection is OK, replace the faulty VIFA unit.
ULTRASITE:
Fault reason: Oven oscillator adjustment function inter-rupted.
Instructions:
1. Check that the Abis synchronisation is correct.
NOTE: The alarm is an indication that the BTS DAC control value is less than 204 steps away from either control range end limit (0 or 4095). The adjusting of the BTS clock still continues. The alarm is automatically cancelled when the control value is more than 204 steps away from the control range end limits.
Flexi EDGE and Flexi Multiradio:
Fault reason: Clock tuning DAC word reaching min/max limit.
Description: Oven oscillator DAC word is within 5% of the min/max limit. Alarm is activated if the DAC word is between 0-204 or 3891-4095. This alarm can be acti-vated due to incorrect synchronisation settings in trans-mission network.
Instructions:
1. Check the Abis synchronisation that there are valid Rx clock sources available.
a. If the reference clock is ok, tune the ESMA clock to the correct frequency.
b. If the reference clock is not ok, check the alarm history for 8xxx alarms for the possible reason for the incorrect reference clock. Follow the instructions on 8xxx alarms. After correcting the reference clock tune ESMA clock to the correct frequency.
7616 OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED
7621 INTOLERABLE CONDITIONS ON SITE
Change description: Instructions changed
Instructions in S14 Instructions in S15
Flexi EDGE: Flexi EDGE and Flexi Multiradio:
7705 D-CHANNEL FAILURE
Change description: Meaning improved, Alarm text changed, Instructions changed
Meaning in S14 Meaning in S15
114 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
The alarm concerns the LAPD link of the TRX. The alarm concerns the D-channel of the TRX.
Alarm Text in S14 Alarm Text in S15
*/
alarm_text = 'LAPD FAILURE',
*/
alarm_text = 'D-CHANNEL FAILURE',
Instructions in S14 Instructions in S15
Check the LAPD link of the TRX. Check the D-channel state of the TRX.
7705 D-CHANNEL FAILURE
7722 ERROR IN BSS RADIO NETWORK DATABASE UPDATE
Change description: SIF structure changed
SIF structure in S14 SIF structure in S15
INTERRUPTED_TASK
27 Dual TRX manual power down
28 Dual TRX power down in low traffic
INTERRUPTED_TASK
27 TRX manual power down
28 TRX automatic power down
7723 FAILURE IN SENDING SYSTEM INFORMATION TO BTS SITE
Change description: SIF structure changed
SIF structure in S14 SIF structure in S15
INTERRUPTED_TASK
27 Dual TRX manual power down
28 Dual TRX power down in low traffic
INTERRUPTED_TASK
27 TRX manual power down
28 TRX automatic power down
7724 CONFLICT BETWEEN BSS RADIO NETWORK DATABASE AND CALL CONTROL
Change description: SIF structure changed
SIF structure in S14 SIF structure in S15
INTERRUPTED_TASK
27 Dual TRX manual power down
28 Dual TRX power down in low traffic
INTERRUPTED_TASK
27 TRX manual power down
28 TRX automatic power down
7730 CONFIGURATION OF BCF FAILED
Change description: SIF structure added, Instructions changed
SIF structure in S14 SIF structure in S15
DN0963445DN0963445 Issue 01
115
Changes in RG20(BSS)
Id:0900d8058076d66f
255 UNSUCCESSFUL_ECOther malfunction between the BSC and the BTS
593 ILLEGAL_BTS_SUBTYPE_ECDefined BTS site subtype is not suitable for BTS software.
10675 OML_FAILURE_EC Configuring the BCF failed because of the O&M link state.
10921 BTT_BUSY_ECThe BTS is busy. Try again later.
10922 BTT_BAD_MESSAGE_EC An invalid message
10923 BTT_BAD_VALUE_ECAn error in the value of the parameters or data.
10925 BTT_EXEC_PROB_EC Problems have been encountered in the execution of the command.
10926 BTT_BAD_PARAMETER_EC Invalid parameter value
10927 BTT_INV_OBJECT_ID_EC Unknown object
10928 BTT_OBJECT_NOT_ALLOWED_EC The object cannot be the target of a command/message.
10929 BTT_INV_OBJECT_STATE_EC The object state is not compatible with the transaction.
10930 BTT_INIT_NOT_COMPL_ECThe unit is not yet operational.
10931 BTT_SEQUENCE_ERROR_EC A sequence error has occurred when transmitting a segmented message.
11152 BR_OF_FUS_NOT_CONSISTENT_EC Number of frame units is not consistent with the BTS database.
11153 BTS_DATABASE_DOES_NOT_EXIST_EC BTS database does not exist.
11154 NBR_OF_CUS_NOT_CONSISTENT_EC Number of carrier units is not consistent with the BTS database.
11155 DB_CREATED_BY_OLD_MMI_VERS_EC Database was created with an old MMI version.
11156 INVALID_OBJ_TYPE_IN_MSG_EC Message contains an invalid object type.
11157 RESP_FROM_BTS_TIMEOUT_EC BTS has not responded within time supervision.
255 UNSUCCESSFUL_ECOther malfunction between the BSC and the BTS
593 ILLEGAL_BTS_SUBTYPE_ECDefined BTS site subtype is not suitable for BTS software.
10675 OML_FAILURE_EC Configuring the BCF failed because of the O&M link state.
10921 BTT_BUSY_ECThe BTS is busy. Try again later.
10922 BTT_BAD_MESSAGE_EC An invalid message
10923 BTT_BAD_VALUE_EC An error in the value of the parameters or data.
10925 BTT_EXEC_PROB_EC Problems have been encountered in the execution of the command.
10926 BTT_BAD_PARAMETER_EC Invalid parameter value.
10927 BTT_INV_OBJECT_ID_EC Unknown object
10928 BTT_OBJECT_NOT_ALLOWED_EC The object cannot be the target of a command/message.
10929 BTT_INV_OBJECT_STATE_EC The object state is not compatible with the transaction.
10930 BTT_INIT_NOT_COMPL_EC The unit is not yet operational.
10931 BTT_SEQUENCE_ERROR_EC A sequence error has occurred when transmitting a segmented message.
11152 NBR_OF_FUS_NOT_CONSISTENT_EC Number of frame units is not consistent with the BTS database.
11153 BTS_DATABASE_DOES_NOT_EXIST_EC BTS database does not exist.
11154 NBR_OF_CUS_NOT_CONSISTENT_EC Number of carrier units is not consistent with the BTS database.
11155 DB_CREATED_BY_OLD_MMI_VERS_EC Database was created with an old MMI version.
11156 INVALID_OBJ_TYPE_IN_MSG_ECMessage contains an invalid object type.
11157 RESP_FROM_BTS_TIMEOUT_EC BTS has not responded within time supervision.
7730 CONFIGURATION OF BCF FAILED
116 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
11160 CONF_COMPL_TIMEOUT_EC Configuration was not completed within time supervision.
11165 GUP_ACK_TIMEOUT_EC Radio network con-figuration management system is temporarily out of resources.
11251 ILLEGAL_BTS_SITE_TYPE_EC Requested operation is not supported by the defined site type.
11365 ILLEGAL_DB_FORMAT_EC BTS does not support the database format.
11367 FLASH_ERROR_EC A fatal error occurred during the flash operation.
11369 ILLEGAL_FILE_TYPE_EC Illegal file type
11371 INV_CELL_CONFIG_EC Cell configuration is not compatible with the current hardware.
11372 INV_HOPPING_MODE_EC Hopping mode is invalid due to the restrictions of the hardware.
11478 NBR_OF_TRX_ECNumber of TRXs in the con-figuration message is not consistent with the BTS.
11870 NO_DATABASE_IN_BTS_OR_IN_BSC_EC The BTS HW database does not exist in BTS or in BSC (no database in flash memory).
12240 FATAL_SYNCH_FAIL_EC Synchronisation settings of BCF in BSC's database are invalid due to the restrictions of the hardware of BTS.
12655 SWOR_ACTIVE_EC Switchover active
12658 INTERNAL_PARAM_ERR_EC The device (other than STM or FUC) sends a nack.
12892 STATE_CHANGED_NOT_RECEIVED_EC BSC has not received the BTS_STATE_CHANGED message because the TRX configuration failed.
13443 REALTIME_UPD_OML_FAIL_EC Updating the current time failed because of an O&M link fault.
14951 REALTIME_UPD_OML_BUSY_EC Updating the current time failed because of a busy O&M link.
14969 TRX_NOT_EDGE_CAPABLE_ECGPRS enabled TRX is not EDGE capable, when EGPRS or CS3&CS4 is enabled in the BTS.
11160 CONF_COMPL_TIMEOUT_EC Configuration was not completed within time supervision.
11165 GUP_ACK_TIMEOUT_EC Radio network con-figuration management system is temporarily out of resources.
11251 ILLEGAL_BTS_SITE_TYPE_ECRequested operation is not supported by the defined site type.
11365 ILLEGAL_DB_FORMAT_ECBTS does not support the database format.
11367 FLASH_ERROR_ECA fatal error occurred during the flash operation.
11369 ILLEGAL_FILE_TYPE_ECIllegal file type
11371 INV_CELL_CONFIG_ECCell configuration is not compatible with the current hardware.
11372 INV_HOPPING_MODE_ECHopping mode is invalid due to the restrictions of the hardware.
11478 NBR_OF_TRX_ECNumber of TRXs in the con-figuration message is not consistent with the BTS.
11870 NO_DATABASE_IN_BTS_OR_IN_BSC_EC The BTS HW database does not exist in BTS or in BSC (no database in flash memory).
12240 FATAL_SYNCH_FAIL_EC Synchronisation settings of BCF in BSC's database are invalid due to the restrictions of the hardware of BTS.
12655 SWOR_ACTIVE_ECSwitchover active
12658 INTERNAL_PARAM_ERR_ECThe device (other than STM or FUC) sends a nack.
1276 BTS_VLAN_ID_CONFLICT_ECVLAN ID for unsecured and secured M-plane traffic is different in BTS.
12892 STATE_CHANGED_NOT_RECEIVED_EC BSC has not received the BTS_STATE_CHANGED message because the TRX configuration failed.
13443 REALTIME_UPD_OML_FAIL_EC Updating the current time failed because of an O&M link fault.
14951 REALTIME_UPD_OML_BUSY_ECUpdating the current time failed because of a busy O&M link.
7730 CONFIGURATION OF BCF FAILED
DN0963445DN0963445 Issue 01
117
Changes in RG20(BSS)
Id:0900d8058076d66f
15839 CLOCK_REQ_WAITING_TIME_OUT_EC BSC has not received an ack message from the BTS to the BTS_CLOCK_REQ message.
15844 EGPRS_BTS_TRXS_NOT_IN_DAP_EC GPRS enabled TRX is not attached to Dynamic Abis Pool, when EGPRS is enabled in the BTS.
15953 BCCH_GTRX_NOT_EDGE_CAPABLE_EC GPRS enabled BCCH TRX is not EDGE capable, when EGPRS or CS3&CS4 is enabled in the BTS.
15973 BCCH_EDGE_GTRX_NOT_IN_DAP_EC GPRS enabled BCCH TRX is not attached to Dynamic Abis Pool, when EGPRS is enabled in the BTS.
15954 PBCCH_SYNC_LOST_EC Abis synchronisa-tion for PBCCH/PCCCH channel is failed.
16116 ILLEGAL_OPTIONAL_FEATURE_EC Using of an optional feature of the BTS is not allowed in BTS.
16117 NON_SUPPORTED_BTS_SW_EC Unsup-ported SW package for BTS is rejected by BTS.
16368 CS3_CS4_BTS_GTRXS_NOT_IN_DAP_EC GPRS enabled TRX is not attached to Dynamic Abis Pool, when CS3&CS4 is enabled in the BTS.
16369 BCCH_CS3_CS4_GTRX_NOT_IN_DAP_EC GPRS enabled BCCH TRX is not attached to Dynamic Abis Pool, when CS3&CS4 is enabled in the BTS.
17088 TRXS_IN_GPRS_BTS_NOT_EDGE_EC TRX does not have EDGE capable HW. When Extended Cell GPRS parameter is enabled in the cell (EXGENA=Y), then all TRXs in the BTS, which has GPRS Enabled TRX (GTRX=Y), must have EDGE capable HW.
14969 TRX_NOT_EDGE_CAPABLE_ECGPRS enabled TRX is not EDGE capable, when EGPRS or CS3&CS4 is enabled in the BTS.
15839 CLOCK_REQ_WAITING_TIME_OUT_EC BSC has not received an ack message from the BTS to the BTS_CLOCK_REQ message.
15844 EGPRS_BTS_TRXS_NOT_IN_DAP_EC GPRS enabled TRX is not attached to Dynamic Abis Pool, when EGPRS is enabled in the BTS.
15953 BCCH_GTRX_NOT_EDGE_CAPABLE_EC GPRS enabled BCCH TRX is not EDGE capable, when EGPRS or CS3&CS4 is enabled in the BTS.
15973 BCCH_EDGE_GTRX_NOT_IN_DAP_EC GPRS enabled BCCH TRX is not attached to Dynamic Abis Pool, when EGPRS is enabled in the BTS.
15954 PBCCH_SYNC_LOST_ECAbis synchronisation for PBCCH/PCCCH channel is failed.
16116 ILLEGAL_OPTIONAL_FEATURE_EC Using of an optional feature of the BTS is not allowed in BTS.
16117 NON_SUPPORTED_BTS_SW_EC Unsup-ported SW package for BTS is rejected by BTS.
16368 CS3_CS4_BTS_GTRXS_NOT_IN_DAP_EC GPRS enabled TRX is not attached to Dynamic Abis Pool, when CS3&CS4 is enabled in the BTS.
16369 BCCH_CS3_CS4_GTRX_NOT_IN_DAP_EC GPRS enabled BCCH TRX is not attached to Dynamic Abis Pool, when CS3&CS4 is enabled in the BTS.
17088 TRXS_IN_GPRS_BTS_NOT_EDGE_ECTRX does not have EDGE capable HW. When Extended Cell GPRS parameter is enabled in the cell (EXGENA=Y), then all TRXs in the BTS, which has GPRS Enabled TRX (GTRX=Y), must have EDGE capable HW.
Instruction in S14 Instruction in S15
7730 CONFIGURATION OF BCF FAILED
118 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Correct the fault indicated in the supplementary infor-mation field.
If the error code in the supplementary information field is 11165, 255, 10921-10931, 11367, 11369, 11870, 12655, 12658, 16116, or 16117, lock and then unlock the BCF with the MML command EFS.
If the error code is 593 or 11251, make sure that the site type definition in the BSC corresponds to the actual BTS site type. After that, lock and unlock the BCF with the MML command EFS.
If the error code is 13443 or 14951, the current time and date in the BSC can be updated for the BTS by locking and unlocking the BCF.
If the error code is 12240 or 15839, make sure that BSC's and synchronisation settings and hardware of the BTS are compatible. After that, lock and unlock the BCF with the MML command EFS.
If the error code is 14969, lock the TRX, make the GPRS enabled TRX EDGE capable in the BTS. *After that unlock the TRX with the MML command ERS.
If the error code is 15844 or 16368, lock the GPRS enabled EDGE TRX(s) and attach it to Dynamic Abis Pool (DAP) in the BTS. *After that unlock the TRX with the MML command ERS.
If the error code is 15953, make GPRS enabled BCCH TRX EDGE capable. *After that lock and unlock the TRX with the MML command ERS.
If the error code is 15973 or 16369, make sure that GPRS enabled BCCH TRX is attached to Dynamic Abis Pool (DAP). *After that lock and unlock the TRX with the MML command ERS.*
If the error code is 14969, 15844, 16368, 15953, 15973 or 16369 and all TRXs do not have EDGE HW and they have been added to DAP in the BTS, then the following conditions must also be taken into account to make sure that the TRX recovery works correctly in the EGPRS or CS3&CS4 enabled BTS.
If a BCCH TRX is EDGE-capable, it has been added to EDAP, and it has the GTRX parameter set to Y, all EDGE-capable unlocked TRXs that have GTRX set to Y should be added to DAP and marked with the pre-ferred BCCH mark (PREF=Y).
If a BCCH TRX is non-EDGE-capable and has the parameter GTRX set to N, all the non-EDGE-capable unlocked TRXs that have GTRX set to N should be marked with the preferred BCCH mark (PREF=Y).
Correct the fault indicated in the supplementary infor-mation field.
If the error code in the supplementary information field is 11165, 255, 10921-10931, 11367, 11369, 11870, 12655, 12658, 16116, or 16117, lock and then unlock the BCF with the MML command EFS.
If the error code is 593 or 11251, make sure that the site type definition in the BSC corresponds to the actual BTS site type. After that, lock and unlock the BCF with the MML command EFS.
If the error code is 13443 or 14951, the current time and date in the BSC can be updated for the BTS by locking and unlocking the BCF.
If the error code is 12240 or 15839, make sure that BSC's and synchronisation settings and hardware of the BTS are compatible. After that, lock and unlock the BCF with the MML command EFS.
If the error code is 14969, lock the TRX, make the GPRS enabled TRX EDGE capable in the BTS. *After that unlock the TRX with the MML command ERS.
If the error code is 15844 or 16368, lock the GPRS enabled EDGE TRX(s) and attach it to Dynamic Abis Pool (DAP) in the BTS. *After that unlock the TRX with the MML command ERS.If the error code is 15953, make GPRS enabled BCCH TRX EDGE capable. *After that lock and unlock the TRX with the MML command ERS.If the error code is 15973 or 16369, make sure that GPRS enabled BCCH TRX is attached to Dynamic Abis Pool (DAP). *After that lock and unlock the TRX with the MML command ERS.*If the error code is 14969, 15844, 16368, 15953, 15973 or 16369 and all TRXs do not have EDGE HW and they have been added to DAP in the BTS, then the following conditions must also be taken into account to make sure that the TRX recovery works correctly in the EGPRS or CS3&CS4 enabled BTS.If a BCCH TRX is EDGE-capable, it has been added to EDAP, and it has the GTRX parameter set to Y, all EDGE-capable unlocked TRXs that have GTRX set to Y should be added to DAP and marked with the preferred BCCH mark (PREF=Y).If a BCCH TRX is non-EDGE-capable and has the parameter GTRX set to N, all the non-EDGE-capable unlocked TRXs that have GTRX set to N should be marked with the preferred BCCH mark (PREF=Y),
7730 CONFIGURATION OF BCF FAILED
DN0963445DN0963445 Issue 01
119
Changes in RG20(BSS)
Id:0900d8058076d66f
1. Check whether the TRXs in the BTS have been con-figured correctly, that is, whether the recommendation above has been followed.
2.
a) If the configuration of the TRXs is not in order in the BTS,
1. lock the BTS (EQS)
2. lock the required TRX(s) (ERS),
3. re-configure the TRX(s) (EQM),
4. unlock the TRX(s) (ERS),
5. unlock the BTS (EQS).
2.
b) If TRX configuration is in order in the BTS,lock & unlock the BTS (MML command EQS).
If the error code is 17088, make sure that the TRX's HW is EDGE capable. Lock the TRX and make the TRX HW EDGE capable or take the extended (E)GPRS out of use from the BTS. The Extended (E)GPRS of the BTS can be disabled out of use with the MML command EQV.
1. Check whether the TRXs in the BTS have been con-figured correctly, that is, whether the recommendation above has been followed.
2.
a) If the configuration of the TRXs is not in order in the BTS,
1. lock the BTS (EQS),
2. lock the required TRX(s) (ERS),
3. re-configure the TRX(s) (EQM),
4. unlock the TRX(s) (ERS),
5. unlock the BTS (EQS).
2.
b) If TRX configuration is in order in the BTS,lock & unlock the BTS (MML command EQS).
If the error code is 17088, make sure that the TRX's HW is EDGE capable. Lock the TRX and make the TRX HW EDGE capable or take the extended (E)GPRS out of use from the BTS. The Extended (E)GPRS of the BTS can be disabled out of use with the MML command EQV.If the error code is 1276, make sure that VLAN ID is same for unsecured and secured M-plane traffic.
7730 CONFIGURATION OF BCF FAILED
7735 TRX TEST FAILED
Change description: Instructions changed, Cancelling alarm
Instructions in S14 Instructions in S15
120 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
1. To avoid this alarm being triggered unnecessarily, the PWRx threshold values should be permanently set as follows (valid for all TX combining options):
BTS type TX power threshold Recommended value (with PMAX=0)
MetroSite PWRM +26 dBm
HP MetroSite PWRH +33 dBm
UltraSite EDGE PWRU +43 dBm
Flexi EDGE PWRE +41 dBm
These values leave room for the expected (BTS type specific) tolerances. Each threshold value applies to all similar BTS types under the same BSC. The current PWRx thresholds can be checked with MML command as follows:
ZUCV:TRP,CURRENT;
and adjusted with:
ZUCV:TRP,MODIFY:PWRx=<new value>;
Note that the recommended values are valid for PMAX=0 only. If a lower PMAX value is used (even in one BTS (sector) on the same BSC), the PWRx should be lowered accordingly. For instance, if PMAX=2 is used even in one Flexi-EDGE BTS under testing, the PWRE on that BSC should be set to +39 dBm (that is, 2 dB lower).
When the test is run by using a local or remote BTS Manager, only the BTS SW internal thresholds are used. This way, unnecessary failures because of the above-mentioned BSC (S12 or earlier) threshold issue cannot be caused. Nokia Siemens Networks recom-mends that you run the TRX test again with the BTS Manager before making a decision to replace the TRX unit.
1. Use the MML command UCV to check that the threshold values of result parameters are reasonable
ZUCV:TRP,CURRENT;
Change THE threshold values if they are not reason-able.
Instructions in S14 Instructions in S15
Do not cancel the alarm. The system cancels the alarm when the TRX test (either single or scheduled) for the MetroSite or UltraSite base station is successful in the TRX and the diversity that generated the alarm.
Do not cancel the alarm. The system cancels the alarm when the TRX test (either single or scheduled) for the Nokia Metrosite or Nokia UltraSite base station is suc-cessful in the TRX and the diversity that generated the alarm.
7735 TRX TEST FAILED
7741 MEAN HOLDING TIME ABOVE DEFINED THRESHOLD
Change description: SIF structures changed, Instructions changed
SIF structure in S14 SIF structure in S15
DN0963445DN0963445 Issue 01
121
Changes in RG20(BSS)
Id:0900d8058076d66f
SUB_CH_ID
subchannel identification
00 - 01: TCH/H subchannel
F0 : TCH/F subchannel
C0 - C7: SDCCH subchannel
SUB_CH_ID
subchannel identification
00: TCH/H subchannel 0 (OSC-0)
10: TCH/H subchannel 0 (OSC-1)
01: TCH/H subchannel 1 (OSC-0)
11: TCH/H subchannel 1 (OSC-1)
02: TCH/F subchannel (OSC-0)
12: TCH/F subchannel (OSC-1)
C0 - C7: SDCCH subchanne
Instructions in S14 Instructions in S15
Find out whether the channel seizure that caused the alarm is a real call or an unreleased channel.
Use the service terminal command S:<bts_id>,<trx_id>,B,<status = 20>
Take E00 service terminal extension into use in the working MCMU with the following command:
ZLE:<char>,E00_BXSX
Note that you need to check which MCMU is in the working state with the command ZUSI:COMP;
Use the E00 service terminal extension command S to find out whether the channel seizure that caused the alarm is a real call or an unreleased channel.
Give the following command to the working MCMU unit:
Z<char>S:<BTS_id>,0,B,20;
Note that the parameter BTS_ID is given in hexadeci-mal format.
Cancelling the alarm
If the alarm does not require user actions, you can cancel it with the MML command EOR.
The system cancels the alarm when you lock and unlock the object in question, or, if the alarm requires no user actions, after the current measurement period.
Cancelling the alarm
If the alarm does not require user actions, you can cancel it with the MML command EOR.
The system cancels the alarm when you lock and unlock the object in question, or, if the alarm requires no user actions, the system cancels the alarm at the end of the measurement period during which the channel that caused the alarm is allocated/ released normally.
7741 MEAN HOLDING TIME ABOVE DEFINED THRESHOLD
7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD
Change description: SIF structure changed, Instruction changed
SIF structure in S14 SIF structure in S15
SUB_CH_ID
identifies the subchannel in the time slot with the shortest mean holding time
00: TCH/H subchannel 0
01: TCH/H subchannel 1
02: TCH/F subchannel
SUB_CH_ID
identifies the subchannel in the time slot with the shortest mean holding time
00: TCH/H subchannel 0 (OSC-0)
10: TCH/H subchannel 0 (OSC-1)
01: TCH/H subchannel 1 (OSC-0)
11: TCH/H subchannel 1 (OSC-1)
02: TCH/F subchannel (OSC-0)
12: TCH/F subchannel (OSC-1)
122 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
Changed alarms in Transmission Alarms (8000-8999)
Instruction in S14 Instruction in S14
Cancelling AlarmIf the alarm requires no user actions, you can cancel it with the MML command EOR.The system cancels the alarm automatically in connection with the user's locking and unlocking commands, or, if the situation is solved without user actions, after the current measurement period.
Cancelling AlarmIf the alarm requires no user actions, you can cancel it with the MML command EOR.The system cancels the alarm automatically in connection with the user's locking and unlocking commands, or, if the situation is solved without user actions, after the current measurement period.All supplementary fields are set to zero irrespective of the alarms cancelled manually or by the system.
7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD
7768 INCONSISTENT DATA IN DFCA RADIO RESOURCE STATE FILES
Change description: SIF structure changed
SIF structure in S14 SIF structure in S15
NEIGHBOUR_CELL
1..1000 Internal DFCA cell index
1001..3000 External DFCA cell index
NEIGHBOUR_CELL
1..2100 Internal DFCA cell index
2101..5000 External DFCA cell index
7995 MAINS BREAKDOWN WITH BATTERY BACK-UP
Change description: Instructions changed
Instructions in S14 Instructions in S15
Check the mains supply.
If the mains supply is OK, check the EAC/Q1 cabling between the BTS and IBBU/SISU. Repair the SISU/IBBU.
Flexi EDGE:
Description: One or more AC phases of the mains supply are faulty and site is operating on battery backup.
Instructions:
1. Check the mains supply coming to the site support equipment. If the mains supply is ok,
a. Check the EAC cabling between ESMA and the site support equipment.
OR
b. Check that cable is completely mated between FPA and the power module.
2. Repair the site support equipment.
Check the mains supply. If the mains supply is OK, check the EAC/Q1 cabling between the BTS and IBBU/SISU. Repair the SISU/IBBU.
Flexi EDGE and Flexi Multi Radio:
Description: One or more AC phases of the mains supply are faulty and site is operating on battery backup.
Instructions:
1. Check the mains supply coming to the site support equipment. If the mains supply is ok,
a. Check the EAC cabling between ESMA and the site support equipment.
OR
b. Check that cable is completely mated between FPA and the power module.
2. Repair the site support equipment.
8099 RECEIVED BIT ERROR RATIO (BER) > 1E-3
Change description: SIF structure changed, Instructions changed
SIF structure in S14 SIF structure in S15
DN0963445DN0963445 Issue 01
123
Changes in RG20(BSS)
Id:0900d8058076d66f
Q1_CHANNEL_NUMBER
Number of the Q1 service channel in the BSC, 0...27. If equipment is supervised by the BTS the channel number is not relevant
Q1_CHANNEL_NUMBER
Number of the Q1 service channel in the BSC, 0...27. If equipment is supervised by the BTS the channel number is not relevant
Instructions in S14 Instructions in S15
See the equipment operating manual for more detailed information on the fault code and corrective actions.
See the equipment operating manual for more detailed information on the fault code and corrective actions.
Flexi EDGE and Flexi Multiradio:
Description: Received signal has degraded on E1/T1 interface. Bit Error Ratio (BER) is over 1E-3.
Instructions:1. If FIFA PIU is used, Refer to the FIFA product documentation for instructions.
2. Check that the interface settings are correct for the link.
3. Check quality of the E1/T1 line by enabling a Loop to Interface (line) at the far end equipment. If the alarm is cancelled during the loop test, check the far-end equip-ment.
4. Equip an external cable loop to the interface to check that the interface in FIxx is ok. If the alarm is still active during the loop test, go to step 6.
5. Check the condition of cables, connectors and correct polarities of the wire pairs.
6. Check that FIxx is fully inserted in to ESMA.
7. Replace FIxx.
8. Check the signal quality of the transmission path to the alarming equipment.
8099 RECEIVED BIT ERROR RATIO (BER) > 1E-3
8112 FREQUENCY ERROR
Change description: Instructions changed
Instructions in S14 Instructions in S15
124 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
See the equipment operating manual for more detailed information on the fault code and corrective actions.
Flexi EDGE:
Description:
The node is running on the internal clock as configured in the timing priority list. This alarm can also be raised in case synchronisation protection is configured, when the Rx source signals from both directions have its MCBs in state '1'.
Instructions:
1. Check that synchronisation priority list has Rx clock entries for used interfaces.
2. In case FIFA PIU is used, check that the microwave link is commissioned and operational. Refer to FIFA product documentation for further instructions.
3. If any of the alarms 8050, 8066, 8081, 8099, 8056 or 8073 are active, follow the instructions on them.
4. Check that interface cables are correctly mated to FIxx. Check also condition of the connectors.
5. If BTS is part of PDH loop protection configuration, check MCB/LCB configuration and operational state of loop network.
See the equipment operating manual for more detailed information on the fault code and corrective actions.
Flexi EDGE and Flexi Radio:
Description:
The node is running on the internal clock as configured in the timing priority list. This alarm can also be raised in case synchronisation protection is configured, when the Rx source signals from both directions have its MCBs in state '1'.
Instructions:
1. Check that synchronisation priority list has Rx clock entries for used interfaces.
2. In case FIFA PIU is used, check that the microwave link is commissioned and operational. Refer to FIFA product documentation for further instructions.
3. If any of the alarms 8050, 8066, 8081, 8099, 8056 or 8073 are active, follow the instructions on them.
4. Check that interface cables are correctly mated to FIxx. Check also condition of the connectors.
5. If BTS is part of PDH loop protection configuration, check MCB/LCB configuration and operational state of loop network.
8112 FREQUENCY ERROR
8273 LICENCE FOR 2G FLEXI ABIS OVER IP/ETHERNET IS NOT AVAILABLE
Change description: Alarm text changed, Instructions changed
Alarm text in S14 Alarm text in S15
LICENCE FOR FLEXIEDGE ABIS OVER IP/ETHER-NET IS NOT AVAILABLE
LICENCE FOR 2G FLEXI ABIS OVER IP/ETHERNET IS NOT AVAILABLE
Instructions in S14 Instructions in S15
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE and Flexi Multiradio:
Description: Transmission is commissioned to be in Pseudowire (PWE) mode without a licence or without configuring the BSC.
Instructions:
1. Check the status of the '2G Flexi Abis over IP/Ether-net' feature at the BSC, and if needed, install and/or activate it.
2. Configure the '2G Flexi Abis over IP/Ethernet' feature in the BSC.
Alternatively, you can:
1. Recommission the site to use TDM mode.
DN0963445DN0963445 Issue 01
125
Changes in RG20(BSS)
Id:0900d8058076d66f
8274 LICENCE FOR 2G FLEXI ADDITIONAL 2 E1/T1 IS NOT AVAILABLE
Change description: Alarm text changed, Instructions changed
Alarm text in S14 Alarm text in S15
LICENCE FOR FLEXIEDGE ADDITIONAL 2 E1/T1 IS NOT AVAILABLE
LICENCE FOR 2G FLEXI ADDITIONAL 2 E1/T1 IS NOT AVAILABLE
Instructions in S14 Instructions in S15
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE and Flexi Multiradio:
Description: The number of used E1/T1 interfaces with terminated Abis traffic is higher than the number of licensed E1/T1 interfaces or the number of the E1/T1 interfaces configured in the BSC.
Instructions:
1. Check the status of the '2G Flexi Additional 2 E1/T1' feature at the BSC, And if needed, install and/or activate it.
2. Configure the '2G Flexi Additional 2 E1/T1' feature by increasing the number of licensed E1/T1 interfaces at the BSC.
Alternatively, you can:
1. Reduce the number of E1/T1 interfaces exceeding the licence:
a. Remove the terminated Abis allocations from the number of exceeded interfaces. OR
b. Set the exceeded number of interfaces to 'Not in Use' state.
Note: Only two E1/T1 interfaces are licence free. One licence will increase the number of E1/T1 interfaces by two.
8275 LICENCE FOR 2G FLEXI ABIS TRS GROOMING IS NOT AVAILABLE
Change description: Alarm text changed, Instructions changed
Alarm text in S14 Alarm text in S15
LICENCE FOR FLEXIEDGE TRS ABIS GROOMING IS NOT AVAILABLE
LICENCE FOR 2G FLEXI ABIS TRS GROOMING IS NOT AVAILABLE
Instructions in S14 Instructions in S15
126 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE and Flexi Multiradio:
Description: Bypass cross-connections are configured in used E1/T1 interfaces without a licence or without configuring the BSC.
Instructions:
1. Check the status of the '2G Flexi Abis TRS Groom-ing' feature at the BSC, and if needed, install and/or activate it.
2. Configure the '2G Flexi Abis TRS Grooming' feature in the BSC.
Alternatively, you can:
1. Disable all the cross-connections which are con-trolled by '2G Flexi Abis TRS Grooming'.
Note: Bi-directional cross-connections controlled by '2G Flexi Abis TRS Grooming' are of the following gran-ularities: 8 kBit/s, 16 kBit/s, 32 kBit/s, 64 kBit/s and n*64 kBit/s.
8275 LICENCE FOR 2G FLEXI ABIS TRS GROOMING IS NOT AVAILABLE
8276 LICENCE FOR 2G FLEXI TRS LOOP PROTECTION IS NOT AVAILABLE
Change description: Alarm text changed, Instructions changed
Alarm text in S14 Alarm text in S15
LICENCE FOR FLEXIEDGE TRS LOOP PROTEC-TION IS NOT AVAILABLE
LICENCE FOR 2G FLEXI TRS LOOP PROTECTION IS NOT AVAILABLE
Instructions in S14 Instructions in S15
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE and Flexi Multiradio:
Description: Abis protection and/or protected cross-connections are configured in used E1/T1 interfaces without a licence or without configuring the BSC.
Instructions:
1. Check the status of the '2G Flexi TRS Loop Protec-tion' feature at the BSC, and if needed, install and/or activate it.
2. Configure the '2G Flexi TRS Loop Protection' feature in the BSC.
Alternatively, you can:
1. Disable all cross-connections which are controlled by '2G Flexi TRS Loop Protection'.
Note: Protected bi-directional cross-connections, Masked bi-directional cross-connections and Abis pro-tection are controlled by '2G Flexi TRS Loop Protec-tion'.
DN0963445DN0963445 Issue 01
127
Changes in RG20(BSS)
Id:0900d8058076d66f
8277 ETHERNET PHYSICAL LINK LAYER LOST
Change description: Instructions changed
Instructions in S14 Instructions in S15
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE and Flexi Multiradio:
Description: Physical Ethernet link is detected to be down.
Instructions:
1. Check that the Ethernet cable is connected to the right interface and the cable is correctly mated to the PIU. Check the condition of cables and connectors. Check that the length/type of the cable does not intro-duce excessive attenuation.
2. Check that the device connected to the FIxx PIU supports 100 Base-T, full duplex mode and autonegoti-ation.
3. Check that the device connected to the FIxx PIU has correct settings, such as autonegotiation and Ethernet interface enabled.
4. Replace FIxx.
8278 PSEUDOWIRE DOWN
Change description: Instructions changed
Instructions in S14 Instructions in S15
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE and Flexi Multiradio:
Description: The incoming pseudowire connection is down. There is a fault in the connection of the pseudowire. R bit is set at the CESoPSN control word and sent in the Tx direction.
Instructions:
1. Check the pseudowire and pseudowire tunnel config-uration settings at both ends.
2. Check the conditions in the transmission path of the pseudowire tunnel at the packet switched network.
3. Replace FIxx.
8280 PSEUDOWIRE REMOTE PACKET LOSS
Change description: Instructions changed
Instructions in S14 Instructions in S15
128 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d66f
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE and Flexi Multiradio:
Description: Signaled by the equipment in the far-end; indicates a serious fault in the received signal at the far-end equipment.
Instructions:
1. Check for alarms at the far-end equipment. See instructions on them.
2. Check the condition of the cables and connectors, and the correct polarities of the wire pairs at both ends.
3. Check that the pseudowire and pseudowire tunnel settings are correct at both ends.
4. Check the transmission path of the pseudowire tunnel from the alarming interface to the far end.
8280 PSEUDOWIRE REMOTE PACKET LOSS
8281 FAULT IN OPTICAL INTERFACE (SFP)
Change description: Instructions changed
Instructions in S14 Instructions in S15
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE Flexi Multiradio:
Description: A fault is detected at the Ethernet SFP interface.
Instructions:
1. Check that the SFP module is correctly installed.
2. Check that the SFP module is of supported type (Ethernet 1000 Base-SX or 1000 Base-LX).
3. Check that the electrical contacts of the SFP module are clean from dust, dirt or water.
4. Replace the SFP module.5. Replace FIxx.
8282 PSEUDOWIRE TUNNEL DOWN
Change description: Instructions changed
Instructions in S14 Instructions in S15
DN0963445DN0963445 Issue 01
129
Changes in RG20(BSS)
Id:0900d8058076d66f
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE Flexi Multiradio:
Fault reason: Transmission is commissioned to be in Pseudowire (PWE) mode without a licence.
Instructions:
1. Install and activate the 'Flexi EDGE Abis over IP/Ethernet' licence at the BSC.
2. Recommission the site to use TDM mode.
For more detailed information on the fault code and cor-rective actions, see the equipment's operating manual.
Flexi EDGE:
Fault reason: Transmission is commissioned to be in Pseudowire (PWE) mode without a licence.
Instructions:
1. Install and activate the 'Flexi EDGE Abis over IP/Ethernet' licence at the BSC.
2. Recommission the site to use TDM mode.
8282 PSEUDOWIRE TUNNEL DOWN
130 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d80580792b5c
4.1.4 Removed alarmsThe alarms listed in this section have been removed in S15.
Number Name Reason for removal
Removed from
7760 FAILURE IN PACKET SYSTEM INFORMA-TION SENDING
Removed as redundant.
Base Station Alarms (7000 - 7999)
Table 4 Removed alarms
DN0963445DN0963445 Issue 01
131
Changes in RG20(BSS) Counter changes
Id:0900d80580791e56
5 Counter changes
5.1 Counter changes made in Nokia Siemens Networks GSM/EDGE BSS, rel RG20(BSS), operating documenta-tion, issue 01
5.1.1 Overview of counter changesThis document describes the counter changes made to the BSC S15 software release. Existing counters have been modified either to:
• complement the new set of S15 software; or • improve the existing set of measurements
New S15 counters are listed in the section New counters. There are subsections for counters introduced by new and enhanced S15 software products and counters intro-duced to improve BSC Statistics. Counters that have been modified in S15 are listed in the section Changed counters. There are subsections for modifications related to new and enhanced S15 software products and modifications related to other changes in S15 software or documentation.
The S15 software release includes the changes introduced by the following new software products:
• BSS21309: OSC Half Rate with SAIC MS • BSS30385: Circuit Switched Dynamic Abis pool • BSS21222: Energy optimised TCH Allocation • BSS21343: DLDC Territory Procedures • BSS21392: TRX Specific Link Adaptation for DLDC • BSS20083: Inter-BSC NACC • BSS21341: A over IP, Transcoder in BSS and BSS30380: A over IP, Transcoder in
MGW • BSS21454: Packet Abis over IP/Ethernet • BSS21440: Packet Abis over TDM • BSS30395: Packet Abis Delay Measurement • BSS21271: Abis Delay Measurement (TDM, PWE3) • BSS21045: Inter System NACC • BSS21355: Inter System NACC for LTE • BSS101583: Precise RX Level Measurement • BSS101584: Precise Timing Advance Measurement • BSS101585: Precise Power Level Measurement • BSS101586: Adjacent Cell RX Level Measurement
New measurementsThe S15 software release introduces the following new measurements:
• 120 TDM/PW Abis Delay Measurement • 121 Circuit-switched Dynamic Abis Pool Measurement • 122 OSC RX Quality Measurement • 123 Packet Abis BTS Measurement
132 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d80580791e56
Counter changes
• 124 Packet Abis Traffic Measurement • 125 Packet Abis SCTP Measurement • 126 Packet Abis Delay Measurement • 127 Packet Abis Congestion Control Measurement • 128 ETP Ethernet BSC Measurement • 129 ETP Ethernet TCSM Measurement • 130 AoIP Traffic BSC Measurement • 131 AoIP Traffic TCSM Measurement • 135 Precise RX Level Measurement • 136 Precise Timing Advance Measurement • 137 Precise Power Level Measurement • 138 Adjacent Cell RX Level Measurement
New counters in existing measurements and observationsThe new counters in the existing measurements are:
1 Traffic Measurement: 001257 - 001270, 001272 - 001273. New spare counters 001271, 001280 - 001287.
2 Resource Availability Measurement: 002094 - 002096.
4 Handover Measurement: 004235 - 004252. New spare counters 004253 - 004258.
50 BSC Level Clear Code Measurement: 0500409, 0500377 and 0500945. Spare Counters 0500630-0500634, 0500717, 0500718, 0500941-0500944 made official.
51 BSC Level Clear Code PM Measurement: 051216 - 051220, 05122- 051223.
72 Packet Control Unit Measurement: 072260 - 072265.
95 GPRS Cell Re-selection Measurement: 095025 - 095026.
114 Pseudo Wire BSC Measurement: 114011 - 114015.
116 Pseudo Wire TCSM Measurement: 116011 - 116015.
Related topics
• New counters • Changed counters
DN0963445DN0963445 Issue 01
133
Changes in RG20(BSS)
Id:0900d805807c8f56
5.1.2 New countersFor an overview of counter changes in S15, see Overview of counter changes.
5.1.2.1 New counters introduced by BSS20083: Inter-BSC NACC
New counters in 72 Packet Control Unit Measurement
New counters in 95 GPRS Cell Re-selection Measurement
5.1.2.2 New counters introduced by BSS21045: Inter System NACC
New counters in 72 Packet Control Unit Measurement
5.1.2.3 New counters introduced by BSS21355:Inter System NACC for LTE
New counters in 72 Packet Control Unit Measurement
5.1.2.4 New counters introduced by BSS21341: A over IP, Transcoder in BSS and BSS30380: A over IP, Transcoder in MGW
New counters in 4 Handover Measurement
Number Name
072260 NACC REPORT SUBSCRIPTIONS FROM OTHER BSC
Number Name
095025 IBNACC WITH NC0
095026 IBNACC WITH NC2
Number Name
072261 NACC REPORT SUBSCRIPTIONS FROM RNC
Number Name
072262 NACC REPORT SUBSCRIPTIONS FROM LTE
Number Name
004244 BSS INTERNAL HANDOVER REQUIRED REQUESTS
004245 BSS INTERNAL HANDOVER COMMANDS
004246 BSS INTERNAL HANDOVER FAILURES
134 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f56
New counters in 50 BSC Level Clear Code Measurement
New counters in 51 BSC Level Clear Code PM Measurement
Counters in new measurement: 129 ETP Ethernet TCSM Measurement
Counters in new measurement: 130 AoIP Traffic BSC Measurement
004247 BSS INTERNAL HANDOVER REQUIRED REJECTIONS
004248 BSS INTERNAL HANDOVER SUCCESS-FUL
004249 BSS INTERNAL HANDOVER ENQUIRY
004250 BSS INTERNAL HANDOVER ENQUIRY REJECTIONS
Number Name
0500409 UNAVAIL CODEC TYPE CONF
0500945 M NO SUPP REDUNDANCY LVL
0500377 CALL FAIL DUE ETP
Number Name
051220 INTER CELL MSS TRIGGERED BSS INTERNAL HO
Number Name
129000 RECEIVED ETHERNET FRAMES
129001 ERRORED ETHERNET FRAMES
129002 TRANSMITTED ETHERNET FRAMES
129003 RECEIVED ETHERNET OCTETS
129004 TRANSMITTED ETHERNET OCTETS
Number Name
130000 RTP PACKETS RECEIVED
130001 RTP PACKETS LOST
130002 RTP PACKETS SENT
130003 RTP PACKET OCTETS RECEIVED
130004 RTP PACKET OCTETS SENT
Number Name
DN0963445DN0963445 Issue 01
135
Changes in RG20(BSS)
Id:0900d805807c8f56
Counters in new measurement: 131 AoIP Traffic TCSM Measurement
5.1.2.5 New counters introduced by BSS21454: Packet Abis over IP/Ether-net
Counters in new measurement: 128 ETP Ethernet BSC Measurement
5.1.2.6 New counters introduced by BSS21454: Packet Abis over IP/Ether-net and BSS21440: Packet Abis over TDM added
New counters in 1 Traffic Measurement
New counters in 50 BSC Level Clear Code Measurement
Number Name
131000 RTP PACKETS RECEIVED
131001 RTP PACKETS LOST
131002 RTP PACKETS SENT
131003 RTP PACKET OCTETS RECEIVED
131004 RTP PACKET OCTETS SENT
131005 RTP PACKETS TOO LATE
131006 RTP PACKETS TOO EARLY
Number Name
128000 RECEIVED ETHERNET FRAMES
128001 ERRORED ETHERNET FRAMES
128002 TRANSMITTED ETHERNET FRAMES
128003 RECEIVED ETHERNET OCTETS
128004 TRANSMITTED ETHERNET OCTETS
Number Name
001268 TCH REQ REJ DUE ABIS CONG
001269 CALL SETUP REJ DUE ABIS CONG
001270 GPRS TERR UG REJ DUE ABIS
001272 TCH REQUEST REJECT DUE TO ETP OVERLOAD
001273 CALL SETUP REJECT DUE TO ETP OVERLOAD
Number Name
0500377 CALL FAIL DUE ETP
136 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f56
Counters in new measurement: 123 Packet Abis BTS Measurement
Number Name
123000 FRAMES RECEIVED
123001 FRAMES SENT
123002 OCTETS RECEIVED
123003 OCTETS SENT
123004 UL UTILIZATION 0-25
123005 UL UTILIZATION 25-50
123006 UL UTILIZATION 50-75
123007 UL UTILIZATION 75-90
123008 UL UTILIZATION 90-100
123009 DL UTILIZATION 0-25
123010 DL UTILIZATION 25-50
123011 DL UTILIZATION 50-75
123012 DL UTILIZATION 75-90
123013 DL UTILIZATION 90-100
123014 CS U-PLANE RTP PACKETS RECEIVED
123015 CS U-PLANE RTP PACKETS LOST
123016 CS U-PLANE RTP PACKETS RECEIVED TOO LATE
123017 CS U-PLANE RTP PACKETS RECEIVED TOO EARLY
123018 CS U-PLANE RTP PACKETS SENT
123019 PS U-PLANE RTP PACKETS RECEIVED
123020 PS U-PLANE RTP PACKETS LOST
123021 PS U-PLANE RTP PACKETS RECEIVED TOO LATE
123022 PS U-PLANE RTP PACKETS RECEIVED TOO EARLY
123023 PS U-PLANE RTP PACKETS SENT
123024 CS U-PLANE UDP PACKETS RECEIVED
123025 CS U-PLANE UDP PACKETS SENT
123026 CS U-PLANE UDP OCTETS RECEIVED
123027 CS U-PLANE UDP OCTETS SENT
123028 PS U-PLANE UDP OCTETS RECEIVED
123029 PS U-PLANE UDP OCTETS SENT
123030 SCTP PACKETS RECEIVED
123031 SCTP PACKETS SENT
123032 SCTP OCTETS RECEIVED
DN0963445DN0963445 Issue 01
137
Changes in RG20(BSS)
Id:0900d805807c8f56
Counters in new measurement: 124 Packet Abis Traffic Measurement
Counters in new measurement: 125 Packet Abis SCTP Measurement
Counters in new measurement: 127 Packet Abis Congestion Control Measure-ment
123033 SCTP OCTETS SENT
123034 SCTP PACKETS RETRANSMITTED
Number Name
124000 CS U-PLANE RTP PACKETS RECEIVED
124001 CS U-PLANE RTP PACKETS LOST
124002 CS U-PLANE RTP PACKETS RECEIVED TOO LATE
124003 CS U-PLANE RTP PACKETS RECEIVED TOO EARLY
124004 CS U-PLANE RTP PACKETS RECEIVED ON TIME
124005 CS U-PLANE RTP PACKETS SENT
124006 PS U-PLANE RTP PACKETS RECEIVED
124007 PS U-PLANE RTP PACKETS LOST
124008 PS U-PLANE RTP PACKETS SENT
124009 CS U-PLANE UDP PACKETS RECEIVED
124010 CS U-PLANE UDP PACKETS SENT
124011 CS U-PLANE UDP OCTETS RECEIVED
124012 CS U-PLANE UDP OCTETS SENT
124013 PS U-PLANE UDP OCTETS RECEIVED
124014 PS U-PLANE UDP OCTETS SENT
Number Name
125000 SCTP PACKETS RECEIVED
125001 SCTP PACKETS SENT
125002 SCTP OCTETS RECEIVED
125003 SCTP OCTETS SENT
125004 SCTP PACKETS RETRANSMITTED
Number Name
127000 DURATION OF DECREASE TBF SCHED-ULING RATE BY 25 PERCENT
Number Name
138 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f56
New counters in 72 Packet Control Unit Measurement
5.1.2.7 New counters introduced by BSS30395: Packet Abis Delay Measure-ment
Counters in new measurement: 126 Packet Abis Delay Measurement
5.1.2.8 New counters introduced by BSS21309: OSC Half Rate with SAIC MS
New counters in 1 Traffic Measurement
127001 DURATION OF DECREASE TBF SCHED-ULING RATE BY 75 PERCENT
127002 DURATION OF AMR CODEC DECREASE
127003 DURATION OF LIMITATION OF NEW CS AND PS CALLS
127004 DURATION OF LIMITATION OF NEW CS CALLS DUE ETP OVERLOAD
Number Name
072265 UL MCS REDUCTION DUE PCU RESOURCES
072266 DL MCS REDUCTION DUE PCU RESOURCES
Number Name
Number Name
126000 SUM OF ABIS ROUND TRIP TIMES
126001 ABIS ROUND TRIP TIME SAMPLES
126002 ABIS ROUND TRIP TIME MIN
126003 ABIS ROUND TRIP TIME MAX
126004 MAX SLIDING 1 MINUTE ROUND TRIP TIME AVERAGE
126005 MAX SLIDING 5 MINUTE ROUND TRIP TIME AVERAGE
126006 SUM OF ROUND TRIP TIME VARIATIONS
126007 ROUND TRIP TIME VARIATION MIN
126008 ROUND TRIP TIME VARIATION MAX
126009 ROUND TRIP TIME VARIATION SAMPLES
Number Name
001263 DHR MULTIPLEXING ATTEMPTS
DN0963445DN0963445 Issue 01
139
Changes in RG20(BSS)
Id:0900d805807c8f56
New counters in 2 Resource Availability Measurement
New counters in 4 Handover Measurement
New counters in 51 BSC Level Clear Code Measurement
001264 DHR MULTIPLEXING FAILURE DUE TO TCH RESOURCE
001265 CSDAP RESOURCE ALLOCATION ATTEMPTS FOR DHR
001266 DHR MULTIPLEXING FAILURE DUE TO CSDAP RESOURCE
001267 DHR MULTIPLEXING FAILURE DUE TO OTHER REASON
Number Name
002094 AVE BUSY OSC DHR TCH PAIR
002095 AVE BUSY OSC DHR TCH PAIR DENOMI-NATOR
002096 PEAK BUSY OSC DHR TCH PAIR
Number Name
004235 HO ATTEMPT FROM AMR HR TO DHR
004236 HO ATTEMPT FROM AMR FR TO DHR
004237 HO FROM AMR HR TO DHR SUCCESSFUL
004238 HO FROM AMR FR TO DHR SUCCESSFUL
004239 INT CELL UNSUCCESS HO TO DHR DUE TO CSDAP MISMATCH
004240 HO ATTEMPT FROM DHR DUE TO RX QUALITY
004241 HO ATTEMPT FROM DHR DUE TO UL RX LEVEL DIFFERENCE
004242 HO FROM DHR DUE TO RX QUALITY SUC-CESSFUL
004243 HO FROM DHR DUE TO UL RX LEVEL DIF-FERENCE SUCCESSFUL
004251 HO ATTEMPT FROM DHR DUE TO RX LEVEL
004252 HO FROM DHR DUE TO RX LEVEL SUC-CESSFUL
Number Name
051216 INTRA HO FROM AMR HR TO DHR
051217 INTRA HO FROM AMR FR TO DHR
Number Name
140 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f56
Counters in new measurement: 121 Circuit-switched Dynamic Abis Pool Measur-ment
Counters in new measurement: 122 OSC RX Quality Measurement
051218 INTRA HO FROM DHR DUE TO RX QUALITY
051219 INTRA HO FROM DHR DUE TO UL RX LEVEL DIFFERENCE
Number Name
121000 TOTAL PCM 8 KBIT/S SUBTSLS IN CSDAP
121001 AVERAGE CSDAP 8 KBIT/S SUBTSL USAGE
121002 AVERAGE CSDAP 8 KBIT/S SUBTSL USAGE DENOMINATOR
121003 PEAK CSDAP 8 KBIT/S SUBTSL USAGE
Number Name
122000 OSC AMR HR 4.75 ON UPLINK DIRECTION WITH RXQUAL 0
122001 OSC AMR HR 4.75 ON DOWNLINK DIREC-TION WITH RXQUAL 0
: :
: :
122014 OSC AMR HR 4.75 ON UPLINK DIRECTION WITH RXQUAL 7
122015 OSC AMR HR 4.75 ON DOWNLINK DIREC-TION WITH RXQUAL 7
122016 OSC AMR HR 5.15 ON UPLINK DIRECTION WITH RXQUAL 0
122017 OSC AMR HR 5.15 ON DOWNLINK DIREC-TION WITH RXQUAL 0
: :
: :
122030 OSC AMR HR 5.15 ON UPLINK DIRECTION WITH RXQUAL 7
122031 OSC AMR HR 5.15 ON DOWNLINK DIREC-TION WITH RXQUAL 7
122032 OSC AMR HR 5.90 ON UPLINK DIRECTION WITH RXQUAL 0
122033 OSC AMR HR 5.90 ON DOWNLINK DIREC-TION WITH RXQUAL 0
: :
Number Name
DN0963445DN0963445 Issue 01
141
Changes in RG20(BSS)
Id:0900d805807c8f56
5.1.2.9 New counters introduced by BSS21271: Abis Delay Measurement (TDM, PWE3)
New counters in 114 Pseudo Wire BSC Measurement
: :
122046 OSC AMR HR 5.90 ON UPLINK DIRECTION WITH RXQUAL 7
122047 OSC AMR HR 5.90 ON DOWNLINK DIREC-TION WITH RXQUAL 7
122048 OSC AMR HR 6.70 ON UPLINK DIRECTION WITH RXQUAL 0
122049 OSC AMR HR 6.70 ON DOWNLINK DIREC-TION WITH RXQUAL 0
: :
: :
122062 OSC AMR HR 6.70 ON UPLINK DIRECTION WITH RXQUAL 7
122063 OSC AMR HR 6.70 ON DOWNLINK DIREC-TION WITH RXQUAL 7
122064 OSC AMR HR 7.40 ON UPLINK DIRECTION WITH RXQUAL 0
122065 OSC AMR HR 7.40 ON DOWNLINK DIREC-TION WITH RXQUAL 0
: :
: :
122078 OSC AMR HR 7.40 ON UPLINK DIRECTION WITH RXQUAL 7
122079 OSC AMR HR 7.40 ON DOWNLINK DIREC-TION WITH RXQUAL 7
Number Name
Number Name
114011 JITTER BUFFER UNDERFLOWS
114012 JITTER BUFFER OVERFLOWS
114013 SUM OF JITTER BUFFER FILL LEVEL MAX VALUES
114014 SUM OF JITTER BUFFER FILL LEVEL MIN VALUES
114015 JITTER BUFFER FILL LEVEL SAMPLES
142 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f56
New counters in 116 Pseudo Wire TCSM Measurement
Counters in new measurement: 120 TDM/PW Abis Delay Measurement
5.1.2.10 New counters introduced by BSS21343: DLDC Territory Procedures
New counters in 1 Traffic Measurement
Number Name
116011 JITTER BUFFER UNDERFLOWS
116012 JITTER BUFFER OVERFLOWS
116013 SUM OF JITTER BUFFER FILLLEVEL MAX VALUES
116014 SUM OF JITTER BUFFER FILL LEVEL MIN VALUES
116015 JITTER BUFFER FILL LEVEL SAMPLES
Number Name
120000 ETIP UNIT INDEX IN BSC
120001 PW ID
120002 SUM OF ABIS ROUND TRIP TIMES
120003 ABIS ROUND TRIP TIME SAMPLES
120004 ABIS ROUND TRIP TIME MAX
120005 ABIS ROUND TRIP TIME MIN
120006 SUM OF JITTER BUFFER FILL LEVEL MAX BSC
120007 SUM OF JITTER BUFFER FILL LEVEL MIN BSC
120008 JITTER BUFFER FILL LEVEL SAMPLES BSC
120009 SUM OF JITTER BUFFER FILL LEVELS BTS
Number Name
001257 GPRS TERRITORY UPGRADE REQUEST DUE DLDC
001258 GPRS TERRITORY UPGRADE DUE DLDC REJECT
DN0963445DN0963445 Issue 01
143
Changes in RG20(BSS)
Id:0900d805807c8f56
5.1.2.11 New counters introduced by BSS21222: Energy optimised TCH Allo-cation
New counters in 1 Traffic Measurement
5.1.2.12 New counters introduced by BSS21392: TRX Specific Link Adapta-tion for DLDC
New counters in 72 Packet Control Unit Measurement
5.1.2.13 New counters introduced by BSS101583 Precise RX Level Measure-ment
Counters in new measurement: 135 Precise RX Level Measurement
Number Name
001259 TCH REQUEST WITHIN DL RX LEVEL WINDOW
001260 TCH SEIZURE IN BCCH DUE TO DL RX LEVEL
001261 TCH REQUEST OUT OF DL RX LEVEL WINDOW
001262 TCH SEIZURE IN NON-BCCH DUE TO DL RX LEVEL
Number Name
072263 MCS DIFFERENCE BETWEEN TWO TRXS NUMERATOR
072264 MCS DIFFERENCE BETWEEN TWO TRXS DENOMINATOR
Number Name
135000 UPLINK RX LEVEL 0
135001 UPLINK RX LEVEL 1
135002 UPLINK RX LEVEL 2
135003 UPLINK RX LEVEL 3
135004 UPLINK RX LEVEL 4
135005 UPLINK RX LEVEL 5
: :
: :
: :
135025 UPLINK RX LEVEL 25
135026 UPLINK RX LEVEL 26
144 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f56
5.1.2.14 New counters introduced by BSS101584 Precise Timing Advance Measurement
Counters in new measurement: 136 Precise Timing Advance Measurement
135027 UPLINK RX LEVEL 27
: :
: :
: :
135061 UPLINK RX LEVEL 61
135062 UPLINK RX LEVEL 62
135063 UPLINK RX LEVEL 63
135064 DOWNLINK RX LEVEL 0
135065 DOWNLINK RX LEVEL 1
135066 DOWNLINK RX LEVEL 2
: :
: :
: :
135125 DOWNLINK RX LEVEL 61
135126 DOWNLINK RX LEVEL 62
135127 DOWNLINK RX LEVEL 63
Number Name
Number Name
136000 TIMING ADVANCE VALUE 0
136001 TIMING ADVANCE VALUE 1
136002 TIMING ADVANCE VALUE 2
136003 TIMING ADVANCE VALUE 3
136004 TIMING ADVANCE VALUE 4
136005 TIMING ADVANCE VALUE 5
: :
: :
: :
136025 TIMING ADVANCE VALUE 25
136026 TIMING ADVANCE VALUE 26
136027 TIMING ADVANCE VALUE 27
: :
: :
: :
DN0963445DN0963445 Issue 01
145
Changes in RG20(BSS)
Id:0900d805807c8f56
5.1.2.15 New counters introduced by BSS101585 Precise Power Level Mea-surement
Counters in new measurement: 137 Precise Power Level Measurement
5.1.2.16 New counters introduced by BSS101586 Adjacent Cell RX Level Measurement
Counters in new measurement: 138 Adjacent Cell RX Level Measurement
136065 TIMING ADVANCE VALUE 63
136066 TIMING ADVANCE VALUE 64
136067 TIMING ADVANCE VALUE 65
Number Name
Number Name
137000 MS POWER LEVEL 0
137001 MS POWER LEVEL 1
137002 MS POWER LEVEL 2
137003 MS POWER LEVEL 3
137004 MS POWER LEVEL 4
137005 MS POWER LEVEL 5
: :
: :
: :
137020 MS POWER LEVEL 29
136021 MS POWER LEVEL 30
136022 MS POWER LEVEL 31
136023 BTS POWER LEVEL 0
136024 BTS POWER LEVEL 1
136025 BTS POWER LEVEL 2
: :
: :
: :
136036 BTS POWER LEVEL 13
136037 BTS POWER LEVEL 14
136038 BTS POWER LEVEL 15
Number Name
138000 ADJACENT CELL RX LEVEL RANK 1
146 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f56
138001 ADJACENT CELL RX LEVEL RANK 2
138002 ADJACENT CELL RX LEVEL RANK 3
138003 ADJACENT RX LEVEL 0
138004 ADJACENT RX LEVEL 1
138005 ADJACENT RX LEVEL 2
: :
: :
: :
138064 ADJACENT RX LEVEL 61
138065 ADJACENT RX LEVEL 62
138066 ADJACENT RX LEVEL 63
138067 SERVING-ADJACENT RX LEVEL DIFFER-ENCE 0
138068 SERVING-ADJACENT RX LEVEL DIFFER-ENCE 1
138069 SERVING-ADJACENT RX LEVEL DIFFER-ENCE 2
: :
: :
: :
138115 SERVING-ADJACENT RX LEVEL DIFFER-ENCE 48
138116 SERVING-ADJACENT RX LEVEL DIFFER-ENCE 49
138117 SERVING-ADJACENT RX LEVEL DIFFER-ENCE 50
138118 SERVING-ADJACENT RX LEVEL MATRIX 0
138119 SERVING-ADJACENT RX LEVEL MATRIX 1
138120 SERVING-ADJACENT RX LEVEL MATRIX 2
: :
: :
: :
138158 SERVING-ADJACENT RX LEVEL MATRIX 40
138159 SERVING-ADJACENT RX LEVEL MATRIX 41
138160 SERVING-ADJACENT RX LEVEL MATRIX 42
: :
Number Name
DN0963445DN0963445 Issue 01
147
Changes in RG20(BSS)
Id:0900d805807c8f56
5.1.2.17 Other new counters
New counters in 1 Traffic Measurement
New counters in 4 Handover Measurement
: :
: :
138236 SERVING-ADJACENT RX LEVEL MATRIX 118
138237 SERVING-ADJACENT RX LEVEL MATRIX 119
138238 SERVING-ADJACENT RX LEVEL MATRIX 120
Number Name
Number Name
001271 SPARE
001280 SPARE
001281 SPARE
001282 SPARE
001283 SPARE
001284 SPARE
001285 SPARE
001286 SPARE
001287 SPARE
Number Name
004253 SPARE
004254 SPARE
004255 SPARE
004256 SPARE
004257 SPARE
004258 SPARE
148 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
5.1.3 Changed countersFor an overview of counter changes in S15, see Overview of counter changes.
5.1.3.1 Changes in counters introduced by BSS21454: Packet Abis over IP/Ethernet
Changes in 17 TCH Observation
Changes in 110 PCU Utilisation Measurement
017025/ ABIS ET PCM
Field Previous release Current release
Updated Identification of the Abis interface ET PCM. Identification of the Abis interface ET PCM.
Counter is not updated in case of Packet Abis over Ethernet.
Related to feature
BSS6060: Call Trace Enhancements. BSS21454: Packet Abis over IP/Ethernet
BSS6060: Call Trace Enhancements
017026/ ABIS ET TSL
Field Previous release Current release
Updated Identification of the Abis interface ET TSL. Identification of the Abis interface ET TSL.
Counter is not updated in case of Packet Abis over Ethernet.
Related to feature
BSS6060: Call Trace Enhancements. BSS21454: Packet Abis over IP/Ethernet
BSS6060: Call Trace Enhancements
017027/ ABIS ET SUB TSL
Field Previous release Current release
Updated Identification of the Abis interface ET sub-TSL. Identification of the Abis interface ET sub-TSL.
Counter is not updated in case of Packet Abis over Ethernet.
Related to feature
BSS6060: Call Trace Enhancements BSS21454: Packet Abis over IP/Ethernet
BSS6060: Call Trace Enhancements
110000 / PEAK RESERVED PCUPCM CHANNELS
Field Previous releas\e Current release
Description Peak number of reserved PCUPCM (16 kbit/s) channels. All reserved channels within a measure-ment period are taken into account: GPRS chan-nels, EGPRS master and slave channels.
Peak number of reserved PCUPCM (16 kbit/s) channels. All reserved channels within a measure-ment period are taken into account: GPRS chan-nels, EGPRS master and slave channels. With Packet Abis the peak number of maximum possible PCU resource allocation units (16 kbit/s channel equivalents) according to the maximum MCS for the territory.
DN0963445DN0963445 Issue 01
149
Changes in RG20(BSS)
Id:0900d805807c8f54
5.1.3.2 Changes in counters introduced by BSS21341: A over IP, Transcoder in BSS and BSS30380: A over IP, Transcoder in MGW
Changes in 50 BSC Level Clear Code Measurement
Related to feature
BSS20432: Packet Data Optimisation Package BSS20432: Packet Data Optimisation Package
BSS21454: Packet Abis over IP/Ethernet
110000 / PEAK RESERVED PCUPCM CHANNELS
Field Previous releas\e Current release
0500630/
Field Previous release Current release
Network element name
SPARE NO SUPPORT A IF TYPE
Description Reserved for future use. Number of Assignment Failure or Handover Failure messages which report that requested A-interface type is not supported.
Updated This is updated when BSC sends Handover Failure or Assignment Failure message to MSC with BSSMAP cause set as "Requested A-Interface Type Not Supported"
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500631/
Field Previous release Current release
Network element name
SPARE NO SUPP REDUNDANCY LEVEL
Description Reserved for future use. Description Reserved for future use. Number of Assignment Failure or Handover Failure messages which report that requested redundancy level is not supported.
Updated This is updated when BSC sends Handover Failure or Assignment Failure message to MSC with BSSMAP cause set as "Requested Redundancy Level Not Supported".
Logical type Sum
Trigger type Trigger type
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
150 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
0500632/
Field Previous release Current release
Network element name
SPARE NO SUPP CODEC TYPE CONF
Description Reserved for future use. Number of Assignment Failure or Handover Failure messages which report that requested codec type or codec configuration is not supported.
Updated This is updated when BSC sends Handover Failure or Assignment Failure message to MSC with BSSMAP cause set as "Requested Codec Type or Codec Configuration Not Supported"
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500633/
Field Previous release Current release
Network element name
SPARE UNAVAIL A IF TYPE
Description Reserved for future use. Number of Assignment Failure or Handover Failure messages which report that requested A-interface type is unavailable.
Updated This is updated when BSC sends Handover Failure or Assignment Failure message to MSC with BSSMAP cause set as "Requested A-Interface Type Unavailable"
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500634/
Field Previous release Current release
Network element name
SPARE T25 TIMER EXPIRY
Description Reserved for future use. Number of Internal Handover failures due to T25 timer expiry.
DN0963445DN0963445 Issue 01
151
Changes in RG20(BSS)
Id:0900d805807c8f54
Updated This is updated when T25 timer expires on BSC waiting for Internal Handover Command from MSC. This is incremented only when no more Handover re-tries are allowed from the BSC or the number of re-tries have exceeded the prescribed limit.
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500634/
Field Previous release Current release
0500717 /
Field Previous release Current release
Network element name
SPARE CALL ID ALR ALLOCATED
Description Reserved for future use. Number of Assignment Failure or Handover Failure messages which report that call identifier is already allocated.
Updated This is updated when BSC sends Handover Failure or Assignment Failure message to MSC with BSSMAP cause set as "Call Identifier Already Allo-cated"
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500718 /
Field Previous release Current release
Network element name
SPARE UNAVAIL TERR RESOURCE
Description Reserved for future use. Number of BSSMAP Handover Failure messages which report that requested terrestrial resource is unavailable
Updated This is updated when BSC sends Handover Failure message to MSC with BSSMAP cause set as "Requested Terrestrial Resource Unavailable"
Logical type Sum
Trigger type Event
Unit Integer number
152 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500718 /
Field Previous release Current release
0500941 /
Field Previous release Current release
Network element name
SPARE M NO SUPP CODEC TYP CONF
Description Reserved for future use. Number of Internal Handover Required Reject messages from MSC which report that requested codec type or codec configuration is not supported.
Updated This is updated when BSC receives Internal Handover Required Reject from MSC with BSSMAP cause set as "Requested Codec Type or Codec Configuration Not Supported"
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500942 /
Field Previous release Current release
Network element name
SPARE M NO SUPPORT A IF TYPE
Description Reserved for future use. Number of Internal Handover Required Reject messages from MSC which report that requested A-interface type is not supported.
Updated This is updated when BSC receives Internal Handover Required Reject from MSC with BSSMAP cause set as "Requested A-Interface Type Not Sup-ported"
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500943 /
Field Previous release Current release
Network element name
SPARE M UNAVAIL A IF TYPEx
DN0963445DN0963445 Issue 01
153
Changes in RG20(BSS)
Id:0900d805807c8f54
Description Reserved for future use. Number of Internal Handover Required Reject messages from MSC which report that requested A-interface type is not supported.
Updated This is updated when BSC receives Internal Handover Required Reject from MSC with BSSMAP cause set as "Requested A-Interface Type Unavail-able"
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
0500943 /
Field Previous release Current release
0500944 /
Field Previous release Current release
Network element name
SPARE M UNAVAIL CODEC TYP CONF
Description Reserved for future use. Number of Internal Handover Required Reject messages from MSC which reported that requested codec type or codec configuration is unavailable.
Updated This is updated when BSC receives Internal Handover Required Reject from MSC with BSSMAP cause set as "Requested Codec Type or Codec Configuration Unavailable"
Logical type Sum
Trigger type Event
Unit Integer number
Related to feature
BSS21341: A over IP, Transcoder in BSS
154 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
5.1.3.3 Changes in counters introduced by BSS21309: OSC Half Rate with SAIC MS
Changes in 21 Radio Measurement Report
0210800/ AMR UL 1
Field Previous release Current release
Description AMR codec used in uplink.
The possible values are:
4 = AMR half rate speech, 7.95 kbit/s
5 = AMR half rate speech, 7.5 kbit/s
6 = AMR half rate speech, 6.7 kbit/s
7 = AMR half rate speech, 5.9 kbit/s
8 = AMR half rate speech, 5.15 kbit/s
9 = AMR half rate speech, 4.75 kbit/s
10 = AMR full rate speech, 12.2 kbit/s
11 = AMR full rate speech, 10.2 kbit/s
12 = AMR full rate speech, 7.95 kbit/s
13 = AMR full rate speech, 7.4 kbit/s
14 = AMR full rate speech, 6.7 kbit/s
15 = AMR full rate speech, 5.9 kbit/s
16 = AMR full rate speech, 5.15 kbit/s
17 = AMR full rate speech, 4.75 kbit/s
18 = WB-AMR FR speech, 12.65 kbit/s
19 = WB-AMR FR speech, 8.85 kbit/s
20 = WB-AMR FR speech, 6.6 kbit/s
255 (0xFF) = not used
AMR codec used in uplink.
The possible values are:
4 = AMR half rate speech, 7.95 kbit/s
5 = AMR half rate speech, 7.5 kbit/s
6 = AMR half rate speech, 6.7 kbit/s
7 = AMR half rate speech, 5.9 kbit/s
8 = AMR half rate speech, 5.15 kbit/s
9 = AMR half rate speech, 4.75 kbit/s
10 = AMR full rate speech, 12.2 kbit/s
11 = AMR full rate speech, 10.2 kbit/s
12 = AMR full rate speech, 7.95 kbit/s
13 = AMR full rate speech, 7.4 kbit/s
14 = AMR full rate speech, 6.7 kbit/s
15 = AMR full rate speech, 5.9 kbit/s
16 = AMR full rate speech, 5.15 kbit/s
17 = AMR full rate speech, 4.75 kbit/s
18 = WB-AMR FR speech, 12.65 kbit/s
19 = WB-AMR FR speech, 8.85 kbit/s
20 = WB-AMR FR speech, 6.6 kbit/s
21 = OSC DHR speech, 7.4 kbit/s
22 = OSC DHR speech, 6.7 kbit/s
23 = OSC DHR speech, 5.9 kbit/s
24 = OSC DHR speech, 5.15 kbit/s
25 = OSC DHR speech, 4.75 kbit/s
255 (0xFF) = not used
Related to feature
BSS20960: Wideband AMR BSS20960: Wideband AMR
BSS21309: OSC Half Rate with SAIC MS
DN0963445DN0963445 Issue 01
155
Changes in RG20(BSS)
Id:0900d805807c8f54
0210801/ AMR DL 1
Field Previous release Current release
Description AMR codec used in uplink. The possible values are:
4 = AMR half rate speech, 7.95 kbit/s
5 = AMR half rate speech, 7.5 kbit/s
6 = AMR half rate speech, 6.7 kbit/s
7 = AMR half rate speech, 5.9 kbit/s
8 = AMR half rate speech, 5.15 kbit/s
9 = AMR half rate speech, 4.75 kbit/s
10 = AMR full rate speech, 12.2 kbit/s
11 = AMR full rate speech, 10.2 kbit/s
12 = AMR full rate speech, 7.95 kbit/s
13 = AMR full rate speech, 7.4 kbit/s
14 = AMR full rate speech, 6.7 kbit/s
15 = AMR full rate speech, 5.9 kbit/s
16 = AMR full rate speech, 5.15 kbit/s
17 = AMR full rate speech, 4.75 kbit/s
18 = WB-AMR FR speech, 12.65 kbit/s
19 = WB-AMR FR speech, 8.85 kbit/s
20 = WB-AMR FR speech, 6.6 kbit/s
255 (0xFF) = not used
AMR codec used in downlink. The possible values are:
4 = AMR half rate speech, 7.95 kbit/s
5 = AMR half rate speech, 7.5 kbit/s
6 = AMR half rate speech, 6.7 kbit/s
7 = AMR half rate speech, 5.9 kbit/s
8 = AMR half rate speech, 5.15 kbit/s
9 = AMR half rate speech, 4.75 kbit/s
10 = AMR full rate speech, 12.2 kbit/s
11 = AMR full rate speech, 10.2 kbit/s
12 = AMR full rate speech, 7.95 kbit/s
13 = AMR full rate speech, 7.4 kbit/s
14 = AMR full rate speech, 6.7 kbit/s
15 = AMR full rate speech, 5.9 kbit/s
16 = AMR full rate speech, 5.15 kbit/s
17 = AMR full rate speech, 4.75 kbit/s
18 = WB-AMR FR speech, 12.65 kbit/s
19 = WB-AMR FR speech, 8.85 kbit/s
20 = WB-AMR FR speech, 6.6 kbit/s
21 = OSC DHR speech, 7.4 kbit/s
22 = OSC DHR speech, 6.7 kbit/s
23 = OSC DHR speech, 5.9 kbit/s
24 = OSC DHR speech, 5.15 kbit/s
25 = OSC DHR speech, 4.75 kbit/s
255 (0xFF) = not used
Related to feature
BSS20960: Wideband AMR BSS20960: Wideband AMR
BSS21309: OSC Half Rate with SAIC MS
156 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
0210955 / AMR UL 32
Field Previous release Current release
Description AMR codec used in uplink. The possible values are:
4 = AMR half rate speech, 7.95 kbit/s
5 = AMR half rate speech, 7.5 kbit/s
6 = AMR half rate speech, 6.7 kbit/s
7 = AMR half rate speech, 5.9 kbit/s
8 = AMR half rate speech, 5.15 kbit/s
9 = AMR half rate speech, 4.75 kbit/s
10 = AMR full rate speech, 12.2 kbit/s
11 = AMR full rate speech, 10.2 kbit/s
12 = AMR full rate speech, 7.95 kbit/s
13 = AMR full rate speech, 7.4 kbit/s
14 = AMR full rate speech, 6.7 kbit/s
15 = AMR full rate speech, 5.9 kbit/s
16 = AMR full rate speech, 5.15 kbit/s
17 = AMR full rate speech, 4.75 kbit/s
18 = WB-AMR FR speech, 12.65 kbit/s
19 = WB-AMR FR speech, 8.85 kbit/s
20 = WB-AMR FR speech, 6.6 kbit/s
255 (0xFF) = not used
AMR codec used in uplink. The possible values are:
4 = AMR half rate speech, 7.95 kbit/s
5 = AMR half rate speech, 7.5 kbit/s
6 = AMR half rate speech, 6.7 kbit/s
7 = AMR half rate speech, 5.9 kbit/s
8 = AMR half rate speech, 5.15 kbit/s
9 = AMR half rate speech, 4.75 kbit/s
10 = AMR full rate speech, 12.2 kbit/s
11 = AMR full rate speech, 10.2 kbit/s
12 = AMR full rate speech, 7.95 kbit/s
13 = AMR full rate speech, 7.4 kbit/s
14 = AMR full rate speech, 6.7 kbit/s
15 = AMR full rate speech, 5.9 kbit/s
16 = AMR full rate speech, 5.15 kbit/s
17 = AMR full rate speech, 4.75 kbit/s
18 = WB-AMR FR speech, 12.65 kbit/s
19 = WB-AMR FR speech, 8.85 kbit/s
20 = WB-AMR FR speech, 6.6 kbit/s
21 = OSC DHR speech, 7.4 kbit/s
22 = OSC DHR speech, 6.7 kbit/s
23 = OSC DHR speech, 5.9 kbit/s
24 = OSC DHR speech, 5.15 kbit/s
25 = OSC DHR speech, 4.75 kbit/s
255 (0xFF) = not used
Related to feature
BSS20960: Wideband AMR BSS20960: Wideband AMR
BSS21309: OSC Half Rate with SAIC MS
DN0963445DN0963445 Issue 01
157
Changes in RG20(BSS)
Id:0900d805807c8f54
0210956 / AMR DL 32
Field Previous release Current release
Description AMR codec used in uplink. The possible values are:
4 = AMR half rate speech, 7.95 kbit/s
5 = AMR half rate speech, 7.5 kbit/s
6 = AMR half rate speech, 6.7 kbit/s
7 = AMR half rate speech, 5.9 kbit/s
8 = AMR half rate speech, 5.15 kbit/s
9 = AMR half rate speech, 4.75 kbit/s
10 = AMR full rate speech, 12.2 kbit/s
11 = AMR full rate speech, 10.2 kbit/s
12 = AMR full rate speech, 7.95 kbit/s
13 = AMR full rate speech, 7.4 kbit/s
14 = AMR full rate speech, 6.7 kbit/s
15 = AMR full rate speech, 5.9 kbit/s
16 = AMR full rate speech, 5.15 kbit/s
17 = AMR full rate speech, 4.75 kbit/s
18 = WB-AMR FR speech, 12.65 kbit/s
19 = WB-AMR FR speech, 8.85 kbit/s
20 = WB-AMR FR speech, 6.6 kbit/s
255 (0xFF) = not used
AMR codec used in downlink. The possible values are:
4 = AMR half rate speech, 7.95 kbit/s
5 = AMR half rate speech, 7.5 kbit/s
6 = AMR half rate speech, 6.7 kbit/s
7 = AMR half rate speech, 5.9 kbit/s
8 = AMR half rate speech, 5.15 kbit/s
9 = AMR half rate speech, 4.75 kbit/s
10 = AMR full rate speech, 12.2 kbit/s
11 = AMR full rate speech, 10.2 kbit/s
12 = AMR full rate speech, 7.95 kbit/s
13 = AMR full rate speech, 7.4 kbit/s
14 = AMR full rate speech, 6.7 kbit/s
15 = AMR full rate speech, 5.9 kbit/s
16 = AMR full rate speech, 5.15 kbit/s
17 = AMR full rate speech, 4.75 kbit/s
18 = WB-AMR FR speech, 12.65 kbit/s
19 = WB-AMR FR speech, 8.85 kbit/s
20 = WB-AMR FR speech, 6.6 kbit/s
21 = OSC DHR speech, 7.4 kbit/s
22 = OSC DHR speech, 6.7 kbit/s
23 = OSC DHR speech, 5.9 kbit/s
24 = OSC DHR speech, 5.15 kbit/s
25 = OSC DHR speech, 4.75 kbit/s
255 (0xFF) = not used
Related to feature
BSS20960: Wideband AMR BSS20960: Wideband AMR
BSS21309: OSC Half Rate with SAIC MS
158 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
Changes in 29 Drop Call Breakdown Observation
029014 / DL LAST USED BITRATE
Field Previous release Current release
Description 0x05 = AMR HR speech, 7.4 kbit/s
0x06 = AMR HR speech, 6.7 kbit/s
0x07 = AMR HR speech, 5.9 kbit/s
0x08 = AMR HR speech, 5.15 kbit/s
0x09 = AMR HR speech, 4.75 kbit/s
0x0A = AMR FR speech, 12.2 kbit/s
0x0B = AMR FR speech, 10.2 kbit/s
0x0C = AMR FR speech, 7.95 kbit/s
0x0D = AMR FR speech, 7.4 kbit/s
0x0E = AMR FR speech, 6.7 kbit/s
0x0F = AMR FR speech, 5.9 kbit/s
0x10 = AMR FR speech, 5.15 kbit/s
0x11 = AMR FR speech, 4.75 kbit/s
0x12 = FR AMR-WB speech, 12.65 kbit/s
0x13 = FR AMR-WB speech, 8.85 kbit/s
0x14 = FR AMR-WB speech, 6.6 kbit/s
0x255 = non-AMR
0x05 = AMR HR speech, 7.4 kbit/s
0x06 = AMR HR speech, 6.7 kbit/s
0x07 = AMR HR speech, 5.9 kbit/s
0x08 = AMR HR speech, 5.15 kbit/s
0x09 = AMR HR speech, 4.75 kbit/s
0x0A = AMR FR speech, 12.2 kbit/s
0x0B = AMR FR speech, 10.2 kbit/s
0x0C = AMR FR speech, 7.95 kbit/s
0x0D = AMR FR speech, 7.4 kbit/s
0x0E = AMR FR speech, 6.7 kbit/s
0x0F = AMR FR speech, 5.9 kbit/s
0x10 = AMR FR speech, 5.15 kbit/s
0x11 = AMR FR speech, 4.75 kbit/s
0x12 = WB-AMR FR speech, 12.65 kbit/s
0x13 = WB-AMR FR speech, 8.85 kbit/s
0x14 = WB-AMR FR speech, 6.6 kbit/s
0x15 = OSC DHR speech, 7.4 kbit/s
0x16 = OSC DHR speech, 6.7 kbit/s
0x17 = OSC DHR speech, 5.9 kbit/s
0x18 = OSC DHR speech, 5.15 kbit/s
0x19 = OSC DHR speech, 4.75 kbit/s
0x255 = non-AMR
Related to feature
BSS20028: Drop Call Breakdown Observation
BSS20960: Wideband AMR
BSS20028: Drop Call Breakdown Observation
BSS21309: OSC Half Rate with SAIC MS
DN0963445DN0963445 Issue 01
159
Changes in RG20(BSS)
Id:0900d805807c8f54
029015 / UL LAST USED BITRATE
Field Previous release Current release
Description 0x05 = AMR HR speech, 7.4 kbit/s
0x06 = AMR HR speech, 6.7 kbit/s
0x07 = AMR HR speech, 5.9 kbit/s
0x08 = AMR HR speech, 5.15 kbit/s
0x09 = AMR HR speech, 4.75 kbit/s
0x0A = AMR FR speech, 12.2 kbit/s
0x0B = AMR FR speech, 10.2 kbit/s
0x0C = AMR FR speech, 7.95 kbit/s
0x0D = AMR FR speech, 7.4 kbit/s
0x0E = AMR FR speech, 6.7 kbit/s
0x0F = AMR FR speech, 5.9 kbit/s
0x10 = AMR FR speech, 5.15 kbit/s
0x11 = AMR FR speech, 4.75 kbit/s
0x12 = FR AMR-WB speech, 12.65 kbit/s
0x13 = FR AMR-WB speech, 8.85 kbit/
s0x14 = FR AMR-WB speech, 6.6 kbit/s
0x255 = non-AMR
0x05 = AMR HR speech, 7.4 kbit/s
0x06 = AMR HR speech, 6.7 kbit/s
0x07 = AMR HR speech, 5.9 kbit/s
0x08 = AMR HR speech, 5.15 kbit/s
0x09 = AMR HR speech, 4.75 kbit/s
0x0A = AMR FR speech, 12.2 kbit/s
0x0B = AMR FR speech, 10.2 kbit/s
0x0C = AMR FR speech, 7.95 kbit/s
0x0D = AMR FR speech, 7.4 kbit/s
0x0E = AMR FR speech, 6.7 kbit/s
0x0F = AMR FR speech, 5.9 kbit/s
0x10 = AMR FR speech, 5.15 kbit/s
0x11 = AMR FR speech, 4.75 kbit/s
0x12 = WB-AMR FR speech, 12.65 kbit/s
0x13 = WB-AMR FR speech, 8.85 kbit/s
0x14 = WB-AMR FR speech, 6.6 kbit/s
0x15 = OSC DHR speech, 7.4 kbit/s
0x16 = OSC DHR speech, 6.7 kbit/s
0x17 = OSC DHR speech, 5.9 kbit/s
0x18 = OSC DHR speech, 5.15 kbit/s
0x19 = OSC DHR speech, 4.75 kbit/s
0x255 = non-AMR
Related to feature
BSS20028: Drop Call Breakdown Observation
BSS20960: Wideband AMR
BSS20028: Drop Call Breakdown Observation
BSS21309 : OSC Half Rate with SAIC MS
160 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
Changes in 77 FER Measurement
077002 / USED CODEC TYPE
Field Previous releas\e Current release
Updated Identification of the used codec type.
Normal channel types:
1 = half rate speech traffic channel
2 = full rate speech traffic channel
3 = enhanced full rate speech traffic channel
Adaptive Multi Rate (AMR) Codecs:
4 = adaptive multirate half rate speech, 7.95kbit/s
5 = adaptive multirate half rate speech, 7.5kbit/s
6 = adaptive multirate half rate speech, 6.7kbit/s
7 = adaptive multirate half rate speech, 5.9kbit/s
8 = adaptive multirate half rate speech, 5.15kbit/s
9 = adaptive multirate half rate speech, 4.75kbit/s
10 = adaptive multirate full rate speech, 12.2kbit/s
11 = adaptive multirate full rate speech, 10.2kbit/s
12 = adaptive multirate full rate speech, 7.95kbit/s
13 = adaptive multirate full rate speech, 7.4kbit/s
14 = adaptive multirate full rate speech, 6.7kbit/s
15 = adaptive multirate full rate speech, 5.9kbit/s
16 = adaptive multirate full rate speech, 5.15kbit/s
17 = adaptive multirate full rate speech, 4.75kbit/s
18 = wideband adaptive multirate full rate speech, 12.65kbit/s
19 = wideband adaptive multirate full rate speech, 8.85kbit/s
20 = wideband adaptive multirate full rate speech, 6.6kbit/s
Identification of the used codec type.
Normal channel types:
1 = half rate speech traffic channel
2 = full rate speech traffic channel
3 = enhanced full rate speech traffic channel
Adaptive Multi Rate (AMR) Codecs:
4 = adaptive multirate half rate speech, 7.95kbit/s
5 = adaptive multirate half rate speech, 7.5kbit/s
6 = adaptive multirate half rate speech, 6.7kbit/s
7 = adaptive multirate half rate speech, 5.9kbit/s
8 = adaptive multirate half rate speech, 5.15kbit/s
9 = adaptive multirate half rate speech, 4.75kbit/s
10 = adaptive multirate full rate speech, 12.2kbit/s
11 = adaptive multirate full rate speech, 10.2kbit/s
12 = adaptive multirate full rate speech, 7.95kbit/s
13 = adaptive multirate full rate speech, 7.4kbit/s
14 = adaptive multirate full rate speech, 6.7kbit/s
15 = adaptive multirate full rate speech, 5.9kbit/s
16 = adaptive multirate full rate speech, 5.15kbit/s
17 = adaptive multirate full rate speech, 4.75kbit/s
18 = wideband adaptive multirate full rate speech, 12.65kbit/s
19 = wideband adaptive multirate full rate speech, 8.85kbit/s
20 = wideband adaptive multirate full rate speech, 6.6kbit/s
21 = OSC half rate speech, 7.4kbit/s
22 = OSC half rate speech, 6.7kbit/s
23 = OSC half rate speech, 5.9kbit/s
24 = OSC half rate speech, 5.15kbit/s
25 = OSC half rate speech, 4.75kbit/s
Related to feature
BSS20960: Wideband AMR
BSS10022: FER Measurement
BSS20960: Wideband AMR
BSS21309: OSC Half Rate with SAIC MS
BSS10022: FER Measurement
DN0963445DN0963445 Issue 01
161
Changes in RG20(BSS)
Id:0900d805807c8f54
5.1.3.4 Changes in counters introduced by BSS20958: Energy Saving Mode for BCCH TRX
Changes in 113 Power Saving Measurement
5.1.3.5 Changes in counters introduced by BSS21343: DLDC Territory Pro-cedures
Changes in 1 Traffic Measurement
113006 / BCCH TRX IDLE TIME ON SDCCH
Field Previous release Current release
Updated Every time an idle period of an SDCCH ends and at the measurement period end.
The counter is updated also when a BTS object doesn't support the Energy Saving Mode for BCCH TRX feature or when the feature is not activated in the segment.
Every time an idle period of an SDCCH ends and at the measurement period end. The counter is updated also when a BTS object doesn't support the Energy Saving Mode for BCCH TRX feature or when the feature is not activated in the segment.
001174/ GPRS TER UPGRD REQ
Field Previous release Current release
Updated When the Radio Resource Management receives from the Packet Controller Unit a request for new radio time slots to be added into the GPRS territory. The PCU can request an upgrade after BSC has ful-filled the default territory defined by the operator parameters.
The upgrade of the GPRS territory may be started for various reasons, for example when GPRS is set enabled in a BTS, GPRS-TRX is created or deblocked, TSL inside the GPRS territory is deblocked or CS load decreases, but this counter is not triggered in these cases.
This counter is triggered only when GPRS Territory Upgrade is started by Packet Switched Radio Resource Management requesting additional GPRS capacity.
When the Radio Resource Management receives from the Packet Controller Unit a request for new radio time slots to be added into the GPRS territory. The PCU can request an upgrade after BSC has ful-filled the default territory defined by the operator parameters.
The upgrade of the GPRS territory may be started for various reasons, for example when GPRS is set enabled in a BTS, GPRS-TRX is created or deblocked, TSL inside the GPRS territory is deblocked or CS load decreases, but this counter is not triggered in these cases.
This counter is triggered only when GPRS Territory Upgrade is started by Packet Switched Radio Resource Management requesting additional GPRS capacity. In case of DLDC territory upgrade request, this counter is updated together with counter 001257 - GPRS TERRITORY UPGRADE REQUEST DUE DLDC
Related to feature
BSS9006: GPRS Telecom in BCSU and MCMU) BSS9006: GPRS Telecom in BCSU and MCMU
BSS21343: DLDC Territory Procedures
162 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
5.1.3.6 Other changed counters
Changes in 1 Traffic Measurement
001175/ INCOMPL SERV GPRS TER UPGR REQ
Field Previous release Current release
Updated When Radio Resource Management upgrades the GPRS territory with less RTSLs than the Packet Controller Unit requested for.
When Radio Resource Management upgrades the GPRS territory with less RTSLs than the Packet Controller Unit requested for. This counter is updated also when DLDC territory upgrade request is fulfilled with less TSLs than requested
Related to feature
BSS9006: GPRS Telecom in BCSU and MCMU BSS9006: GPRS Telecom in BCSU and MCMU
BSS21343: DLDC Territory Procedures
001219 /
Field Previous release Current release
NetAct name SPARE IURG RELOCATION RESOURCE REQUEST
001220 /
Field Previous release Current release
NetAct name SPARE IURG RELOCATION RESOURCE ALLOCATION SUCCESSFUL
001221 /
Field Previous release Current release
NetAct name SPARE TCH TR FAILURE FOR IURG HO WITHOUT A INTERFACE
001222 /
Field Previous release Current release
NetAct name SPARE IURG RELOCATION RESOURCE RELEASE
DN0963445DN0963445 Issue 01
163
Changes in RG20(BSS)
Id:0900d805807c8f54
Changes in 4 Handover Measurement
004033/ CAUSE HO STARTED BY OMC
Field Previous release Current release
Updated When a HO is started by OMC.
See figures:-
Successful internal intra-cell TCH to TCH handover
Successful internal inter-cell TCH to TCH handover
Successful external TCH to TCH handover, source BSC
Successful internal intra-cell SDCCH to SDCCH handover
Successful internal inter-cell SDCCH to SDCCH handover
Successful external SDCCH to SDCCH handover, source BSC
When a HO is started by OMC or if the BSS21389 Security Improvement by Immediate SDCCH Handover is employed and Immediate SDCCH Handover is started.
See figures:
Successful internal intra-cell TCH to TCH handover
Successful internal inter-cell TCH to TCH handover
Successful external TCH to TCH handover, source BSC
Successful internal intra-cell SDCCH to SDCCH handover
Successful internal inter-cell SDCCH to SDCCH handover
Successful external SDCCH to SDCCH handover, source BSC
004171 /
Field Previous release Current release
NetAct name SPARE AMR UNPACKING HO ATTEMPT DUE TO RX LEVEL
004172 /
Field Previous release Current release
NetAct name SPARE MSC I IURG TCH HO ATTEMPT
004173 /
Field Previous release Current release
NetAct name SPARE MSC I IURG TCH HO SUCCESS
004189 /
Field Previous release Current release
NetAct name SPARE MSC I UNSUCCESSFUL IURG HO DUE HO REQUEST DELAY
164 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
Changes in 50 BSC Level Clear Code Measurement
004209 /
Field Previous release Current release
NetAct name SPARE IURG HO REQUEST AFTER MS ON TARGET CHANNEL
0500717 /
Field Previous release Current release
NetAct name SPARE CALL ID ALR ALLOCATED
0500718 /
Field Previous release Current release
NetAct name SPARE UNAVAIL TERR RESOURCE
0500941 /
Field Previous release Current release
NetAct name SPARE M NO SUPP CODEC TYP CONF
0500942 /
Field Previous release Current release
NetAct name SPARE M NO SUPPORT A IF TYPE
0500943 /
Field Previous release Current release
NetAct name SPARE M UNAVAIL A IF TYPE
0500944 /
Field Previous release Current release
NetAct name SPARE M UNAVAIL CODEC TYP CONF
DN0963445DN0963445 Issue 01
165
Changes in RG20(BSS)
Id:0900d805807c8f54
Changes in 62 DMR Measurement
Changes in 68 TRE Measurement
Changes in 69 Selective TRE Measurement
062005 / RF INPUT LEVEL MIN
Field Previous release Current release
Description The minimum value of the RF input level during the measurement period.
The minimum value of the RF input level during the measurement period.The result is given in dBm. Where -100dBm means 0. (-12dBm means 88, for example).
Updated When input level received is smaller than the previous value during measurement period.
062006 / RF INPUT LEVEL MAX
Field Previous release Current release
Description The maximum value of the RF input level during the measurement period. The result is givenin dBm.
The maximum value of the RF input level during the measurement period. The result is given in dBm. Where -100dBm means 0. (-12dBm means 88, for example).
Updated When input level received is greater than the previous value during measurement period.
068006 / RF INPUT LEVEL MIN
Field Previous release Current release
Description The minimum input level received during observa-tion period.
The minimum input level received during observa-tion period. Where -100dBm means 0.(-12dBm means 88, for example).
Unit Decibels dBm
068007 / RF INPUT LEVEL MAX
Field Previous release Current release
Description The maximum input level received during observa-tion period.
The maximum input level received during observa-tion period. Where -100dBm means 0. (-12dBm means 88, for example).
Unit Decibels dBm
069006 / RF INPUT LEVEL MIN
Field Previous release Current release
Description The minimum input level received during observa-tion period.
The minimum input level received during observa-tion period. Where - 100dBm means 0. (-12dBm means 88, for example).
166 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d805807c8f54
Changes in 70 Channel Finder Measurement
Changes in 72 Packet Control Unit Measurement
Changes in 118 Pseudo Wire Tunnel BTS Measurement
069007 / RF INPUT LEVEL MAX
Field Previous release Current release
Description The maximum input level received during observa-tion period.
The maximum input level received during observa-tion period. Where - 100dBm means 0. (-12dBm means 88, for example)
070001 / DB VALUE LOW
Field Previous release Current release
NetAct name DB_VALUE_HIGH DB_VALUE_LOW
070002 / DB VALUE HIGH
Field Previous release Current release
NetAct name DB_VALUE_LOW DB_VALUE_HIGH
072236 /
Field Previous release Current release
NetAct name SPARE PACKET PAGING REQUEST FOR CS PAGING NMO II
118000/ PSEUDO WIRE TUNNEL BTS STATUS 1
Field Previous release Current release
NetAct name PW_TUNNEL_BTS_STATUS_1
118001/ PSEUDO WIRE TUNNEL BTS STATUS 2
Field Previous release Current release
NetAct name PW_TUNNEL_BTS_STATUS_2
118002/ PSEUDO WIRE TUNNEL BTS STATUS 3
Field Previous release Current release
NetAct name PW_TUNNEL_BTS_STATUS_3
DN0963445DN0963445 Issue 01
167
Changes in RG20(BSS)
Id:0900d805807c8f54
Changes in 119 TRE Ethernet Measurement
119000/ TRE ETHERNET STATUS
Field Previous release Current release
NetAct name TRE_ETHERNET_STATUS
168 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d67f
5.1.4 Removed countersFor an overview of counter changes in S15, see Overview of counter changes.
Removed countersNo counters removed from S15.
DN0963445DN0963445 Issue 01
169
Changes in RG20(BSS)
Id:0900d805807b98a7
5.1.5 Other changes between releasesIn addition to the changes listed in the sections of new, changed, and removed coun-ters,some S14 software-related changes and/or corrections have been made to existing ounter descriptions since the release of Nokia Siemens Networks GSM/EDGE BSS, rel. RG10(BSS), operating documentation, issue 01. The changes have been communi-cated as S14 Documentation Change Notes via NOLS Documentation Center, and the updated S14 Product Documentation NEDs have incorporated the changes, or will do so in the future.
These changes have been inherited to S15 where applicable, and are listed below.
Changes in 1 Traffic MeasurementSpare counters 001219, 001220, 001221 and 001222 are taken into use.
Spare counters 001223 and 001224 are taken into use.
For a detailed description of the counters, see 1 Traffic Measurement
Changes in 4 Handover MeasurementSpare counters 004172, 004173, 004189 and 004209 are taken into use.
For a detailed description of the counters, see 4 Handover Measurement
170 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d80580791eb1
MML changes
6 MML changes
6.1 MML changes made in Nokia Siemens Networks GSM/EDGE BSS, rel. RG20(BSS), operating documenta-tion, issue 01
6.1.1 About MML changesThe changes that have been made to MML programs between S14 and S15 are described here.
MMLs with only a few internal changes or guide text changes are not listed in the MML changes documentation. It is possible that command sequences must be modified due to the changes summarised here.
The MML changes documentation may contain information which is irrelevant to the customer. The relevance of the information depends on the delivered software build. For example, some MML programs are optional and are not automatically included in the software build.
For more detailed descriptions see the corresponding commands and instructions.
DN0963445DN0963445 Issue 01
171
Changes in RG20(BSS)
Id:0900d80580792ceb
6.1.2 New MMLsNo new MML programs.
172 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
6.1.3 MML Changes made between S14 and S15
6.1.3.1 Modified MML Programs
(EA) - Adjacent Cell Handling
New command(s) and menu text(s):
N CREATE LTE ADJACENT CELL PARAMETERS
U MODIFY LTE ADJACENT CELL PARAMETERS
V OUTPUT LTE ADJACENT CELL PARAMETERS
S DELETE LTE ADJACENT CELL PARAMETERS
New Command: N CREATE LTE ADJACENT CELL PARAMETERS <option>
Description of changes: New command added to create a new LTE adjacent cell object to the BSS Radio Network Configuration Database (BSDATA).
New syntax: EAN: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :[ INDEX = <lte adjacent cell index> | <serving cell first free index> def ] :([[ MCC = <mobile country code>, | <serving cell MCC> def ][ MNC = <mobile network code>, | <serving cell MNC> def ]]TAC = <LTE adjacent cell tracking area code> ) :( FREQ = <LTE adjacent cell downlink carrier fre-quency>,[[ LTEMB = <LTE adjacent cell min bandwidth> | 0 def ],LTECP = <LTE adjacent cell priority> | 0 def ],LTERUT = <LTE adjacent cell reselection upper thresh-old> | 32 dB def ],LTERLT = <LTE adjacent cell reselection lower threshold> | 32 dB def ],LTERXM = <LTE adjacent cell min RX level> | -140 dB def ]LTEBCL = <barred LTE adjacent cell list> | empty def ]LTEBCG = <barred LTE adjacent cell group> | 0 def ]LTEBCP = <barred LTE adjacent cell pattern> | 255 def ]LTEPS = <barred LTE adjacent cell pattern sense> | 0 def ]] …) ;
Parameters: BTS identification, BTS name, SEG identification <option>, SEG name <option>: LTE adjacent cell index : mobile country code, mobile network code, LTE adjacent cell tracking area code: LTE adjacent cell downlink carrier frequency, LTE adjacent cell min bandwith, LTE adjacent cell priority, LTE adjacent cell reselection upper threshold, LTE adjacent cell reselection lower threshold, LTE adjacent cell min RX level, barred LTE adjacent cell list, barred LTE adjacent cell group, barred LTE adjacent cell pattern, barred LTE adjacent cell pattern sense.
New Command: U MODIFY LTE ADJACENT CELL PARAMETERS <option>
Description of changes: New command added to modify an LTE adjacent cell object to the BSS Radio Network Configuration Database (BSDATA).
DN0963445DN0963445 Issue 01
173
Changes in RG20(BSS)
Id:0900d8058076d679
New syntax: EAU: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :[ INDEX = <lte adjacent cell index> | <serving cell first free index> def ] :([[ MCC = <mobile country code>, | <serving cell MCC> def ][ MNC = <mobile network code>, | <serving cell MNC> def ]]TAC = <LTE adjacent cell tracking area code>,FREQ = <LTE adjacent cell downlink carrier fre-quency>) :( [ NEWMCC = <new mobile country code> |NEWMNC = <new mobile network code> |NEWTAC = <new adjacent cell tracking area code > |NEWFREQ = <new LTE adjacent cell downlink carrier frequency> ] :[[ LTEMB = <LTE adjacent cell min bandwith> | 0 def ],LTECP = <LTE adjacent cell priority> | 0 def ],LTERUT = <LTE adjacent cell reselection upper threshold> | 32 dB def ],LTERLT = <LTE adjacent cell reselection lower threshold> | 32 dB def ],LTERXM = <LTE adjacent cell min RX level> | -140 dB def ]LTEBCL = <barred LTE adjacent cell list> | empty def ]LTEBCG = <barred LTE adjacent cell group> | 0 def ]LTEBCP = <barred LTE adjacent cell pattern> | 255 def ]LTEPS = <barred LTE adjacent cell pattern sense> | 0 def ]] …) ;
Parameters: BTS identification, BTS name, SEG identification <option>, SEG name <option>: LTE adjacent cell index : mobile country code, mobile network code, LTE adjacent cell tracking area code, LTE adjacent cell downlink carrier frequency: new mobile country code, new mobile network code, new adjacent cell tracking code, new LTE adjacent cell downlink carrier frequency: LTE adjacent cell min bandwith, LTE adjacent cell priority, LTE adjacent cell reselection upper threshold, LTE adjacent cell reselection lower threshold, LTE adjacent cell min RX level, barred LTE adjacent cell list, barred LTE adjacent cell group, barred LTE adjacent cell pattern, barred LTE adjacent cell pattern sense;
New Command: V OUTPUT LTE ADJACENT CELL PARAMETERS <option>
Description of changes: New command added to print the parameters of an LTE adjacent cell object to the BSS Radio Network Configuration Database (BSDATA).
New syntax: EAV: [[ BTS = <BTS identification>... |NAME = <BTS name>... |SEG = <SEG identifi-cation>... <option> |SEGNAME = <SEG name>... <option> ] | <all> def ] :[ INDEX = <adjacent cell index> : |[[[ MCC = <mobile country code>, | <serving cell MCC> def ][ MNC = <mobile network code>, | <serving cell MNC> def ]]TAC = < LTE adjacent cell tracking area code >,FREQ = <LTE adjacent cell downlink carrier frequency> ]] | <all> def ;<option>
Parameters: BTS identification, BTS name, SEG identification <option>, SEG name <option>: LTE adjacent cell index : mobile country code, mobile network code, LTE adjacent cell tracking area code, LTE adjacent cell downlink carrier frequency <option>;
New Command: S DELETE LTE ADJACENT CELL PARAMETERS <option>
Description of changes: With this command you can delete an LTE adjacent cell object from the BSS Radio Network Configuration Database (BSDATA).
New syntax: EAS: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :[ INDEX = <lte adjacent cell index> | <serving cell first free index> def ] :([[ MCC = <mobile country code>, | <serving cell MCC> def ][ MNC = <mobile network code>, | <serving cell MNC> def ]]TAC = <LTE adjacent cell tracking area code>,FREQ = <LTE adjacent cell downlink carrier fre-quency> <option> );
Parameters: BTS identification, BTS name, SEG identification <option>, SEG name <option>: LTE adjacent cell index : mobile country code, mobile network code, LTE adjacent cell tracking are code, LTE adjacent cell downlink carrier frequency <option>;
174 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Modified command(s) and menu text(s):
C CREATE ADJACENT CELL PARAMETERS
M MODIFY ADJACENT CELL PARAMETERS
O OUTPUT ADJACENT CELL PARAMETERS
Modified Command C CREATE ADJACENT CELL PARAMETERS
Description of changes: New parameter HO margin delay time has been added.
Old syntax: EAC:( BTS = <BTS identification> | NAME = <BTS name> | SEG = <SEG identifica-tion> <option> | SEGNAME = <SEG name> <option> ) : [ INDEX = <adjacent cell index> | <serving cell first free index> def ] : (([[ MCC = <mobile country code>, | <serving cell MCC> def ] [ MNC = <mobile network code>, | <serving cell MNC> def ]] LAC = <location area code>, CI = <cell identification> ) | ABTS = <adjacent cell identi-fication> | ANAME= <adjacent cell name> | ASEG = <adjacent SEG identification> <option> | ASEGNAME = <adjacent SEG name> <option> ) : [ NCC = <network colour code>, BCC = <BTS colour code>, FREQ = <BCCH frequency>, ] : [[ PMRG = <HO margin pbgt> | 6 def ] [ LMRG = <HO margin lev> | 3 def ] [ QMRG = <HO margin qual> | 0 def ] [ MRGS = <enable HO margin lev qual> | Y def ] [ PRI = <HO priority level> | 3 def ] [ OF = <HO load factor> | 1 def ] [ SL = <RX lev min cell> | -100 def ] [ AUCL = <HO level umbrella> | -47 def ] [ PMAX1 = <MS TX pwr max gsm> <option> | 33 def (GSM 900/GSM 800) ] [ PMAX2 = <MS TX pwr max gsm1x00> <option> | 30 def (GSM 1800/GSM 1900) ] [ SYNC = <synchronized> | N def ] [ TRHO = <TRHO target level> | N def ] [ ACL = <adjacent cell layer> <option> | N def ] [ FMT = <fast moving threshold> <option> | 0 def ] [ POPT = <MS pwr opt level> <option> | no optimization def ] [ CTY = <cell type> <option> | GSM def ] [ CHAIN= <chained adj cell> <option> | N def ] [ HOTA = <HO target area> <option> | 0 def ] [ DRT = <directed retry threshold> <option> | -100 def ] [ DADL = <target cell of direct access to desired layer> <option> | N def ] [ DADLA= <AMR target cell of direct access to desired layer> <option> | N def ] [ AGENA = <adjacent GPRS enabled> <option> | N def ] [ GRXP = <GPRS rxlev access min> <option> | –105 def ] [ GTXP1 = <GPRS MS TX pwr max CCH> <option> | 33 def (GSM 900/GSM 800) ] [ GTXP2 = <GPRS MS TX pwr max CCH1x00> <option> | 30 def (GSM 1800/GSM 1900) ] [ PRC = <priority class> <option> | 0 def ] [ HCS = <HCS signal level threshold> <option> | N (not in use) def] [ GTEO = <GPRS temporary offset> <option> | 0 def ] [ GPET = <GPRS penalty time> <option> | 10 def ] [ RAC = <routing area code> <option> | 255 def ] [ REP = <reporting priority> <option> | 0 (normal) def ][ EQM = <NCCR EGPRS quality margin> <option> | 0 def ] [ GQM = <NCCR GPRS quality margin> <option> | 0 def ] [ EPM = <NCCR and DTM EGPRS PBGT Margin> <option> | 6 def ] [ GPM = <NCCR and DTM GPRS PBGT Margin> <option> | 6 def ] [ DTM = <DTM enabled> | N def ] [ DPM = <DTM power budget margin> <option> | 6 def ] [ DHOPWR = <enable derived handover power> | 0 def ]... ;
DN0963445DN0963445 Issue 01
175
Changes in RG20(BSS)
Id:0900d8058076d679
New syntax: EAC:( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :[ INDEX = <adjacent cell index> |<serving cell first free index> def ] :(([[ MCC = <mobile country code>, |<serving cell MCC> def ][ MNC = <mobile network code>, |<serving cell MNC> def ]]LAC = <location area code>,CI = <cell identification> ) |ABTS = <adjacent cell identification> |ANAME= <adjacent cell name> |ASEG = <adjacent SEG identification> <option> |ASEGNAME = <adjacent SEG name> <option> ) :[ NCC = <network colour code>,BCC = <BTS colour code>,FREQ = <BCCH frequency>, ] :[[ PMRG = <HO margin pbgt> | 6 def ][ LMRG = <HO margin lev> | 3 def ][ QMRG = <HO margin qual> | 0 def ][ MRGS = <enable HO margin lev qual> | Y def ][ HOMD = <HO margin delay time> | 0 def ][ PRI = <HO priority level> | 3 def ][ OF = <HO load factor> | 1 def ][ SL = <RX lev min cell> | -100 def ][ AUCL = <HO level umbrella> | -47 def ][ PMAX1 = <MS TX pwr max gsm> <option> |33 def (GSM 900/GSM 800) ][ PMAX2 = <MS TX pwr max gsm1x00> <option> |30 def (GSM 1800/GSM 1900) ][ SYNC = <synchronized> | N def ][ TRHO = <TRHO target level> | N def ][ ACL = <adjacent cell layer> <option> |N def ][ FMT = <fast moving threshold> <option> |0 def ][ POPT = <MS pwr opt level> <option> |no optimization def ][ CTY = <cell type> <option> | GSM def ][ CHAIN= <chained adj cell> <option> | N def ][ HOTA = <HO target area> <option> | 0 def ][ DRT = <directed retry threshold> <option> | -100 def ]
[ DADL = <target cell of direct access to desired layer> <option> |N def ][ DADLA= <AMR target cell of direct access to desired layer><option> | N def ][ AGENA = <adja-cent GPRS enabled> <option> | N def ][ GRXP = <GPRS rxlev access min> <option> | –105 def ][ GTXP1 = <GPRS MS TX pwr max CCH> <option> |33 def (GSM 900/GSM 800) ][ GTXP2 = <GPRS MS TX pwr max CCH1x00> <option> |30 def (GSM 1800/GSM 1900) ][ PRC = <priority class> <option> | 0 def ][ HCS = <HCS signal level threshold> <option> | N (not in use) def][ GTEO = <GPRS temporary offset> <option> | 0 def ][ GPET = <GPRS penalty time> <option> | 10 def ][ RAC = <routing area code> <option> | 255 def ][ REP = <reporting priority> <option> | 0 (normal) def ][ EQM = <NCCR EGPRS quality margin> <option> | 0 def ][ GQM = <NCCR GPRS quality margin> <option> | 0 def ][ EPM = <NCCR and DTM EGPRS PBGT Margin> <option> | 6 def ][ GPM = <NCCR and DTM GPRS PBGT Margin> <option> | 6 def ][ DTM = <DTM enabled> | N def ][ DPM = <DTM power budget margin> <option> | 6 def ][ DHOPWR = <enable derived handover power> | 0 def ]... ;
Modified Command M MODIFY ADJACENT CELL PARAMETERS
Description of changes: New parameter HO margin delay time has been added.
176 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Old syntax: EAM: (BTS = <BTS identification> | NAME = <BTS name> | SEG = <SEG identifica-tion> <option> | SEGNAME = <SEG name> <option> ) : ( INDEX = <adjacent cell index> : | ([[ MCC = <mobile country code>, | <serving cell MCC> def ] [ MNC = <mobile network code>, | <serving cell MNC> def ]] LAC = <location area code>, CI = <cell iden-tification> ) | ABTS = <adjacent cell identification> | ANAME= <adjacent cell name> | ASEG = <adjacent SEG identification> <option> | ASEGNAME = <adjacent SEG name> <option> ) : ([ NEWMCC = <new mobile country code> | NEWMNC = <new mobile network code> | NEWLAC = <new location area code> | NEWCI = <new cell identification> | NEWABTS = <new adjacent cell identification> | NEWANAME= <new adjacent cell name> | NEWASEG = <new adjacent SEG identification> <option> | NEWASEGNAME= <new adjacent SEG name> <option> ] : [ NCC = <network colour code> | BCC = <BTS colour code> | FREQ = <BCCH frequency> | PMRG = <HO margin pbgt> | LMRG = <HO margin lev> | QMRG = <HO margin qual> | MRGS = <enable HO margin lev qual> | PRI = <HO priority level> | OF = <HO load factor> | SL = <RX lev min cell> | AUCL = <HO level umbrella> | PMAX1 = <MS TX pwr max gsm> <option> | PMAX2 = <MS TX pwr max gsm1x00> <option> | SYNC = <synchronized> | TRHO = <TRHO target level> | ACL = <adjacent cell layer> <option> | FMT = <fast moving threshold> <option> | POPT = <MS pwr opt level> <option> | CTY = <cell type> <option> | CHAIN = <chained adj cell> <option> | HOTA = <HO target area> <option> | DRT = <directed retry threshold> <option> | DADL = <target cell of direct access to desired layer> <option> | DADLA = <AMR target cell of direct access to desired layer> <option> | AGENA = <adjacent GPRS enabled> <option> | GRXP = <GPRS rxlev access min> <option> | GTXP1 = <GPRS MS TX pwr max CCH> <option> | GTXP2 = <GPRS MS TX pwr max CCH1x00> <option> | PRC = <priority class> <option> | HCS = <HCS signal level threshold> <option> | GTEO = <GPRS temporary offset> <option> | GPET = <GPRS penalty time> <option> | RAC = <routing area code> <option> | REP = <reporting priority> <option> | EQM = <NCCR EGPRS quality margin> <option> | GQM = <NCCR GPRS quality margin> <option> | EPM = <NCCR and DTM EGPRS PBGT Margin> <option> | GPM = <NCCR and DTM GPRS PBGT Margin> <option> | DTM = <DTM enabled> | DPM = <DTM power budget margin> <option> ] ) ... DHOPWR = <enable derived handover power> ] ) ...;
New syntax: EAM: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( INDEX = <adjacent cell index> : |([[ MCC = <mobile country code>, | <serving cell MCC> def ][ MNC = <mobile network code>, | <serving cell MNC> def ]]LAC = <location area code>,CI = <cell identification> ) |ABTS = <adjacent cell identification> |ANAME= <adjacent cell name> |ASEG = <adjacent SEG identification> <option> |ASEGNAME = <adjacent SEG name> <option> ) :([ NEWMCC = <new mobile country code> |NEWMNC = <new mobile network code> |NEWLAC = <new location area code> |NEWCI = <new cell identifica-tion> |NEWABTS = <new adjacent cell identification> |NEWANAME= <new adjacent cell name> |NEWASEG = <new adjacent SEG identification> <option> |NEWASEG-NAME= <new adjacent SEG name> <option> ] :[ NCC = <network colour code> |BCC = <BTS colour code> |FREQ = <BCCH frequency> |PMRG = <HO margin pbgt> |LMRG = <HO margin lev> |QMRG = <HO margin qual> |MRGS = <enable HO margin lev qual> |HOMD = <HO margin delay time> |PRI = <HO priority level> |OF = <HO load factor> |SL = <RX lev min cell> |AUCL = <HO level umbrella> |PMAX1 = <MS TX pwr max gsm> <option> |PMAX2 = <MS TX pwr max gsm1x00> <option> |SYNC = <syn-chronized> |TRHO = <TRHO target level> |ACL = <adjacent cell layer> <option> |FMT = <fast moving threshold> <option> |POPT = <MS pwr opt level> <option> |CTY = <cell type> <option> |CHAIN = <chained adj cell> <option> |HOTA = <HO target area> <option> |DRT = <directed retry threshold> <option>
DN0963445DN0963445 Issue 01
177
Changes in RG20(BSS)
Id:0900d8058076d679
(EE) - Base Station Controller Parameter Handling in BSC
DADL = <target cell of direct access to desired layer> <option> |DADLA = <AMR target cell of direct access to desired layer><option> |AGENA = <adjacent GPRS enabled> <option> |GRXP = <GPRS rxlev access min> <option> |GTXP1 = <GPRS MS TX pwr max CCH> <option> |GTXP2 = <GPRS MS TX pwr max CCH1x00> <option> |PRC = <priority class> <option> |HCS = <HCS signal level threshold> <option> |GTEO = <GPRS temporary offset> <option> |GPET = <GPRS penalty time> <option> |RAC = <routing area code> <option> |REP = <reporting priority> <option> |EQM = <NCCR EGPRS quality margin> <option> |GQM = <NCCR GPRS quality margin> <option> |EPM = <NCCR and DTM EGPRS PBGT Margin> <option> |GPM = <NCCR and DTM GPRS PBGT Margin> <option> |DTM = <DTM enabled> |DPM = <DTM power budget margin> <option> ] ) ...DHOPWR = <enable derived handover power> ] ) ...;
Modified Command O OUTPUT ADJACENT CELL PARAMETERS
Description of changes: New Parameter HO margin delay time and NACC SUPPORTED is added in the exe-cution printout.
New command(s) and menu text(s):
B CONTROL BTS COMMISSIONING
Y MODIFY PACKET TRANSPORT PARAMETERS
New Command B CONTROL BTS COMMISSIONING
Description of changes: New command added to output the progress of the commissioning of the BTS and manage the conflicting OMUSIGs situation.
New syntax: EEB:OP = <operation type>:
(CSTAT = <BTS commissioning state> ... |
BCF = <BCF identification> ... | <all> def); <option>
Parameters: New parameters have been added:
Operation type – Possible values are OUT and SEL. This parameter is obligatory.
BTS commissioning state – Possible values are CONFL, NDEF, READY, DL, INIT, COMM, NOSCF, ALL. This parameter is valid only for Flexi EDGE BTS and Flexi multi radio BTS.
Modified Command: Y MODIFY PACKET TRANSPORT PARAMETERS
Description of changes: New command added to modify the BSC level packet transport parameters including the packet abis parameters.
178 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
New syntax: EEY: ( CSUMP = <CS UDP-MUX port> |PSUMP = <PS UDP-MUX port> |MCBE = <MC-PPP Best Effort> |MCAFC1 = <MC-PPP Assured Forwarding Class 1> |MCAFC2 = <MC-PPP Assured Forwarding Class 2> |MCAFC3 = <MC-PPP Assured Forwarding Class 3> |MCAFC4 = <MC-PPP Assured Forwarding Class 4> |MCEF = <MC-PPP Expedited Forwarding> |BTON = <backhaul timer duration start reaction> |BTOFF = <backhaul timer duration stop reaction> |PLTON = <packet loss timer duration start-reaction> |PLTOFF = <packet loss timer duration stop reaction>| CSPDP = <CS packet drop period> |PSPDP = <PS packet drop period> |CPLPDP = <C-plane packet drop period> |MPLPDP = <M-plane packet drop period> |SSME = <SSM enabled> |AF4WFQ = <TS AF4 WFQ weight> |AF3WFQ = <TS AF3 WFQ weight> |AF2WFQ = <TS AF2 WFQ weight> |AF1WFQ = <TS AF1 WFQ weight> |BEWFQ = <TS BE WFQ weight> |VPBE = <VLAN priority BE> |VPAF1 = <VLAN priority AF1> |VPAF2 = <VLAN priority AF2> |VPAF3 = <VLAN priority AF3> |VPAF4 = <VLAN priority AF4> |VPEF = <VLAN priority EF> |AUCS = <abis U-plane CS to DSCP mapping> |AUPS = <abis U-plane PS to DSCP mapping> |ACP = <abis C-plane to DSCP mapping> |AMP = <abis M-plane to DSCP mapping> |CLKS = <clock-sync to DSCP Mapping> |SS = <site support traffic to DSCP mapping>ADSCPM = <A-If CS U-Plane DSCP PHB TC in MGW> |ADSCPB = <A-If CS U-Plane DSCP PHB TC in BSS> |AAF4WF = <A-If AF4 WFQ weight> |AAF3WF = <A-If AF3 WFQ weight> |AAF2WF = <A-If AF2 WFQ weight> |AAF1WF = <A-If AF1 WFQ weight> |ABEWFQ = <A-If BE WFQ weight>) ... ; <option>
DN0963445DN0963445 Issue 01
179
Changes in RG20(BSS)
Id:0900d8058076d679
Parameters: New parameters have been added:
CS UDP-MUX port - The values range from 49152 to 65534 in steps of 2. This param-eter is valid only for Flexi EDGE and Flexi Multiradio site types.
The defalut value is 49152PS UDP-MUX port - The values range from 49152 to 65534 in steps of 2. This parameter is valid only for Flexi EDGE and Flexi Multiradio site types.
The defalut value is 49152MC-PPP Best Effort – The possible values are 0, 1, 2, 3.This parameter is valid only for Flexi EDGE and Flexi Multiradio site types.
The default value is 0.
MC-PPP Assured Forwarding Class 1. The possible values are 0, 1, 2, 3. This param-eter is valid only for Flexi EDGE and Flexi Multiradio site types.The default value is 0.
MC-PPP Assured Forwarding Class 2. The possible values are 0, 1, 2, 3. This param-eter is valid only for Flexi EDGE and Flexi Multiradio site types.The default value is 1.
MC-PPP Assured Forwarding Class 3. The possible values are 0, 1, 2, 3. This param-eter is valid only for Flexi EDGE and Flexi Multiradio site types.The default value is 1.
MC-PPP Assured Forwarding Class 4. The possible values are 0, 1, 2, 3. This param-eter is valid only for Flexi EDGE and Flexi Multiradio site types.The default value is 2.
MC-PPP Expedited Forwarding - The possible values are 0, 1, 2, 3. This parameter is valid only for Flexi EDGE and Flexi Multiradio site types.The default value is 3.
backhaul timer duration start reaction - The valuesrange from 1 to 300 seconds in steps of 1 second. The default value is 4 seconds. This parameter is valid only for Flexi EDGE and Flexi Multiradio site types. The values of these timers are valid for both uplink and downlink direction.
backhaul timer duration stop reaction - The values range from 1 to 600 seconds in steps of 1 second. The default value is 10 seconds. This parameter is valid only for Flexi EDGE and Flexi Multiradio site types.The values of these timers are valid for both uplink and downlink direction.
packet loss timer duration start reaction - The values range from 1 to 300 seconds insteps of 1 second. The default value is 10 seconds.This parameter is valid only for Flexi EDGE and Flexi Multiradio site types.The values of these timers are valid for both uplink and downlink direction.
packet loss timer duration stop reaction -The values range from 1 to 1000 seconds insteps of 1 second. The default value is 100 seconds. This parameter is valid only for Flexi EDGE and Flexi Multiradio site types. The values of these timers are valid for both uplink and downlink direction.
CS packet drop period - The values range from 0 to 100 in steps of 1. The default value is 25. This parameter is valid only for Flexi EDGE and Flexi Multiradio site types.
C-plane packet drop periodThe values range from 0 to 100 in steps of 1. The defalut value is 0. This parameter is valid only for Flexi EDGE and Flexi Multiradio site types.
M-plane packet drop period
Modified command(s) and menu text(s):
H MODIFY DCFA PARAMETERS
I OUTPUT RADIO NETWORK CONFIGURATION
L OUTPUT TRX RADIO TIME SLOTS
M MODIFY GENERAL BASE STATION CONTROL PARAMETERS
O OUTPUT BASE STATION CONTROLLER PARAMETERS
Modified command H MODIFY DFCA PARAMETERS <option>
180 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Description of changes: New packing parameters have been added due to orthogonal subchannel:
C/I target OSC DHR <option> The values range from 0 to 63 dB in steps of 1 dB. The default value is 16 dB.Soft blocking.
C/I OSC DHR <option>The values range from -20 to 43 dB in steps of 1 dB. The default value is -20 dB.
Old syntax: EEH: ( CIF = <C/I target FR> |SBF = <soft blocking C/I FR> |CIUL = <C/I target UL offset> |CIH = <C/I target HR> <option> |SBH = <soft blocking C/I HR> <option> |CIT = <C/I target 14.4> <option> |SBCI = <soft blocking C/I 14.4> <option> |CIAF = <C/I target AMR FR> <option> |SBAF = <soft blocking C/I AMR FR> <option> |CIAH = <C/I target AMR HR> <option> |SBAH = <soft blocking C/I AMR HR> <option> |CISD = <C/I target SDCCH> <option> |SBSD = <soft blocking C/I SDCCH> <option> |CIGP = <C/I target GPRS> <option> |SBGP = <soft blocking C/I GPRS> <option> |SCIO = <SAIC DL C/I offset> <option> |BCP = <BIM confidence probability> |BIT = <BIM interference threshold> |BUP = <BIM update period> |BUSF = <BIM update scaling factor> |BUGT = <BIM update guard time> |DCAM = <DFCA channel allocation method> |EBID = <expected BSC-BSC interface delay> ) ... ; <option>
New syntax: EEH: ( CIF = <C/I target FR> |SBF = <soft blocking C/I FR> |CIUL = <C/I target UL offset> |CIH = <C/I target HR> <option> |SBH = <soft blocking C/I HR> <option> |CIT = <C/I target 14.4> <option> |SBCI = <soft blocking C/I 14.4> <option> |CIAF = <C/I target AMR FR> <option> |SBAF = <soft blocking C/I AMR FR> <option> |CIAH = <C/I target AMR HR> <option> |SBAH = <soft blocking C/I AMR HR> <option> |CISD = <C/I target SDCCH> <option> |SBSD = <soft blocking C/I SDCCH> <option> |CIGP = <C/I target GPRS> <option> |SBGP = <soft blocking C/I GPRS> <option> |CIDHR = <C/I target OSC DHR> <option> |SBDHR = <soft blocking C/I OSC DHR> <option> |SCIO = <SAIC DL C/I offset> <option> |BCP = <BIM confidence probability> |BIT = <BIM interference threshold> |BUP = <BIM update period> |BUSF = <BIM update scaling factor> |BUGT = <BIM update guard time> |DCAM = <DFCA channel allocation method> |EBID = <expected BSC-BSC interface delay> ) ... ; <option>
Modified command H MODIFY DFCA PARAMETERS <option>
Description of execution printout changes
The execution printout of example 1 has updated with new parameters.
Modified command I OUTPUT RADIO NETWORK CONFIGURATION
Description of changes: Parameter output type has a new value PACK.
Modified command L OUTPUT TRX RADIO TIME SLOTS
Description of execution printout changes:
Execution printout has been updated with BUSY HALF DOUBLE RATE.
Modified Command M MODIFY GENERAL BASE STATION CONTROL PARAMETERS
DN0963445DN0963445 Issue 01
181
Changes in RG20(BSS)
Id:0900d8058076d679
(EF) - Base Control Function Handling
Old syntax: EEM: ( NPC = <number of preferred cells> |GMAC = <GSM macrocell threshold> |GMIC = <GSM microcell threshold> |DMAC = <DCS macrocell threshold> |DMIC = <DCS microcell threshold> |DISB = <MS distance behaviour> |TIM = <BTS site battery backup forced HO timer> <option> |EEF = <enable emergency call on FACCH> |EPF = <enable answer to paging call on FACCH> <option> |EOF = <enable ordinary calls on FACCH> <option> |ERF = <enable call re-establishment on FACCH> <option> |HRI = <TCH in handover> <option> |HRL = <lower limit for FR TCH resources> <option> |HRU = <upper limit for FR TCH resources> <option> |AHRL = <AMR lower limit for FR resources> <option> |AHRU = <AMR upper limit for FR resources> <option> |BCN = <BSC call number> <option> |AUT = <AMH upper load threshold> <option> |ALT = <AMH lower load threshold> <option> |AML = <AMH max load target cell> <option> |
New syntax EEM: ( NPC = <number of preferred cells> |GMAC = <GSM macrocell threshold> |GMIC = <GSM microcell threshold> |DMAC = <DCS macrocell threshold> |DMIC = <DCS microcell threshold> |DISB = <MS distance behaviour> |TIM = <BTS site battery backup forced HO timer> <option> |EEF = <enable emergency call on FACCH> |EPF = <enable answer to paging call on FACCH> <option> |EOF = <enable ordinary calls on FACCH> <option> |ERF = <enable call re-establishment on FACCH> <option> |HRI = <TCH in handover> <option> |HRL = <lower limit for FR TCH resources> <option> |HRU = <upper limit for FR TCH resources> <option> |AHRL = <AMR lower limit for FR resources> <option> |AHRU = <AMR upper limit for FR resources> <option> |BCN = <BSC call number> <option> |AUT = <AMH upper load threshold> <option> |ALT = <AMH lower load threshold> <option> |AML = <AMH max load target cell> <option> |EEM MODIFY GENERAL BASE STATION CONTROLLERPARAMETERSACH = <AMR configuration in handovers> <option> |IAC = <initial AMR channel rate> <option> |SAL = <slow AMR LA enabled> <option> |ASG = <AMR set grades enabled> <option> |CSD = <free TSL for CS downgrade> <option> |CSU = <free TSL for CS upgrade> <option> |TGT = <TRHO guard time> |HDL = <HO preference order interfer-ence DL> |HUL = <HO preference order interference UL> |CLR = <load rate for channel search> |TTSAP = <triggering threshold for service area penalty> <option> |PTMP = <penalty trigger measurement period> <option> |SAPT = <service area penalty time> <option> |CTR = <CS TCH allocate RTSL0> <option> |CTC = <CS TCH allocation cal-culation> <option> |NACC = <NACC enabled> <option> |IACT = <initial AMR codec type> <option> |SCHP = <CB DRX Schedule Period> :NCM = <NCCR control mode> <option> |NIRP = <NCCR idle mode reporting period> <option> |NTRP = <NCCR transfer mode reporting period> <option> |
NOCT = <NCCR return to old cell time> <option> |NTPT = <NCCR target cell penalty time> <option> |NNCP = <NCCR neighbor cell penalty> <option> |WFNE = <WCDMA FDD NCCR enabled> <option> |WFNP = <WCDMA FDD NCCR preferred> <option> ) ... ; |;
Modified command O OUTPUT BASE STATION CONTROLLER PARAMETERS
Description of changes: Command output includes the display of new parameter CB DRX schedule period.
Old syntax: EEO: [ <parameter group> | <GEN> def ]
New syntax: EEO: [ <parameter group> | <GEN> def ]
The command entry continues in the same way as before after a semantic error.
Modified command(s) and menu text(s):
C CREATE BASE CONTROL FUNCTION
M MODIFY BASE CONTROL FUNCTION PARAMETERS
O OUTPUT BASE CONTROL FUNCTION PARAMETERS
182 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Modified Command C CREATE BASE CONTROL FUNCTION
Description of changes: New parameters Abis interface connection type, Packet TRS E1/T1 usage, ETP group ID, Packet Abis BCF group ID have been added. New parameters Abis interface con-nection type, Packet TRS E1/T1 usage, ETP group ID, Packet Abis BCF group ID have been added.
Old syntax: EFC: <BCF identification>, <site type> : <BTS site subtype> : [ AC = <autoconfigure> <option> | N def | BR = <bit rate> <option> | AU = <automatic unlock allowed> | T def | DNBR = <D-channel link set number> | DNAME = <D-channel link set name> | REF = <reference BCF identification> | RXDL = <RX difference limit> | 10 def | ] ... : [ TEST = <identification of test equipment> | NOT def ] : [ BBU = <BTS battery backup proce-dure> | ALL def | NTIM = <TRX shutdown timer> | 0 def | NTIM2 = <TRX shutdown timer 2> <option> | 0 def | NTIM3 = <TRX shutdown timer 3> <option> | 0 def | BTIM = <BCCH TRX shutdown timer> | 0 def ] ... <option> : [[ CS = <clock source> | NOT USED def | ADD = <add BCF to chain> ... | SENA = <synch enabled> | F def ] ... | [ MCBCF = <master clock BCF identification> ]] : [ TRS1 = <Flexi EDGE Abis over IP Ethernet usage> <option> | 0 def | TRS2 = <Flexi EDGE Additional 2 E1/T1 usage> <option> | 0 def | TRS3 = <Flexi EDGE TRS Abis Grooming usage> <option> | 0 def | TRS4 = <Flexi EDGE TRS Loop Protection usage> <option> | 0 def ] ... : [ PORT0 = <PCM port ID 0> | ND def | PORT1 = <PCM port ID 1> | ND def | PORT2 = <PCM port ID 2> | ND def | PORT3 = <PCM port ID 3> | ND def | PORT4 = <PCM port ID 4> | ND def | PORT5 = <PCM port ID 5> | ND def | PORT6 = <PCM port ID 6> | ND def | PORT7 = <PCM port ID 7> | ND def ] ... ;
New syntax: EFC: <BCF identification>,<site type>,<BTS site subtype>, <Abis Interface Connection Type> | 0 def]:[ AC = <autoconfigure> <option> | N def |BR = <bit rate> <option> |AU = <automatic unlock allowed> | T def |DNBR = <D-channel link set number> |DNAME = <D-channel link set name> |REF = <reference BCF identification> |RXDL = <RX dif-ference limit> | 10 def | ] ... :[ TEST = <identification of test equipment> | NOT def ] :[ BBU = <BTS battery backup procedure> | ALL def |NTIM = <TRX shutdown timer> | 0 def |NTIM2 = <TRX shutdown timer 2> <option> | 0 def |NTIM3 = <TRX shutdown timer 3> <option> | 0 def |BTIM = <BCCH TRX shutdown timer> | 0 def ] ... <option> :[[ CS = <clock source> | NOT USED def |ADD = <add BCF to chain> ... |SENA = <synch enabled> | F def ] ... |[ MCBCF = <master clock BCF identification> ]] :[ TRS1 = <Flexi EDGE Abis over IP Ethernet usage> <option> | 0 def |TRS2 = <Flexi EDGE Additional 2 E1/T1 usage> <option> | 0 def |TRS3 = <Flexi EDGE TRS Abis Grooming usage> <option> | 0 def |TRS4 = <Flexi EDGE TRS Loop Protection usage> <option> | 0 def |TRS5 = < PACKET TRS E1/T1 usage> <option> | 0 def ] ..... :ETPGID = <ETP group ID>,BHIDL = < BCF HDLC ID>,VLANID = <VLANID> | 4095 def,[ PORT0 = <PCM port ID 0> | ND def |PORT1 = <PCM port ID 1> | ND def |PORT2 = <PCM port ID 2> | ND def |PORT3 = <PCM port ID 3> | ND def |PORT4 = <PCM port ID 4> | ND def |PORT5 = <PCM port ID 5> | ND def |PORT6 = <PCM port ID 6> | ND def |PORT7 = <PCM port ID 7> | ND def ] ... ;
Command still works with old syntax.
Modified Command C CREATE BASE CONTROL FUNCTION
DN0963445DN0963445 Issue 01
183
Changes in RG20(BSS)
Id:0900d8058076d679
Description of execution printout changes:
The execution printout has been updated due to new parameters Abis interface con-nection type, Packet TRS E1/T1 usage, ETP group ID, Packet Abis BCF group ID. The value range for ETP group ID is from 0 to 15 in steps of 1. This parameter is available only for Flexi EDGE and Flexi Multiradio types. The value range for Packet Abis BCF group ID is from 1 to 3000 with steps in 1. This parameter is applicable for Packet Abis over TDM. BCF has to be locked if there is no open Abis HDLC link configured in BCF.
Following parameters are added to execution printouts:
HDLC Link ID HNBR = decimal number.
With this parameter you define High-level Data Link Control (HDLC) protocol. The range of this parameter is from 1 to 3000. NOTE: One BCF can handle max 8 HDLC links NOTE: Parameter is valid only for Flexi EDGE and Flexi Multiradio site types.
ULTS= Enumeration
With this parameter you define whether Traffic Shaping functionality is enabled or not for Packet Abis over Ethernet. The value range supported by this parameter is as below: 0 (No-shaping), 1 (Shaping-committed) Default value is 0.
UL committed information rate ULCIR = decimal number With this parameter you define the Committed Information Rate for Traffic Shaping in uplink direction. The range is from 100..250000. Default value is 0. UL committed burst size ULCBS = decimal number With this parameter you define the Committed Burst Size to be used when Traffic Shaping has to be performed in uplink direction. The range is from 0..65535. Default value is 1500.
Header compression HECOP= Enumeration
With this parameter you define whether the header compression is used or not. Header compression is regarded as optional so that it is possible to instruct the network elements to work with or without it. The value range supported by this parameter is as below: 0 (OFF) 1 (ON) Default value is 1.
BU1 abis throughput threshold BU1 = decimal number
With this parameter you define a threshold to trigger BU1 congestion reaction proce-dure. This threshold defines the value of the Abis throughput measured by BTS which triggers the BU1 congestion reaction procedures. The algorithm handling Abis uplink throughput measurements provides trigger for start/stop the congestion reaction proce-dures when the related thresholds are crossed up/down respectively. The range is from 20..150%, Default value is 75%.
BU2 abis throughput threshold BU2= decimal number
With this parameter you define a threshold to trigger BU2 congestion reaction proce-dure. This threshold defines the value of the Abis throughput measured by BTS which triggers the BU2 congestion reaction procedures. The algorithm handling Abis uplink throughput measurements provides trigger for start/stop the congestion reaction proce-dures when the related thresholds are crossed up/down respectively The range is from 20..150%. Default value is 90 %.
Packet loss in ethernet on DL Abis PL1 threshold PL1 = decimal number.
BCF HDLC id list BHIDL = decimal number
This parameter defines the Abis HDLC link ID’s that are defined for BCF. The range is from 1 to 3000 with steps in 1. This parameter is applicable for Packet Abis over TDM. BCF has to be locked if there are no open Abis HDLC link configured in BCF.
VLANID = decimal number.
This is the VLAN ID of the BTS control plane or user plane. It is an IP address contain-ing VLAN tagging.
184 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
With this parameter you define the PL1 threshold value related to the percentage of the lost frames in the PSN compared to the corresponding expected frames (lost frames + received frames). Considering the Packet Loss Congestion definition, the proper reaction procedure is triggered when the difference between the PS loss frame rate and CS loss frame rate is higher than PL1 threshold.
The range is from 1..23, and is internally interpreted as below:
1 -> 10 exp (-3)
2 -> 2x10 exp (-3)
3 -> 3x10 exp (-3)
4 -> 4x10exp (-3)
5 -> 5x10exp (-3)
6 -> 6x10exp (-3)
7 -> 7x10exp (-3)
8 -> 8x10exp (-3)
9 -> 9x10exp (-3)
10 -> 10exp (-2)
11 -> 2x10exp (-2)
12 -> 3x10exp (-2)
13 -> 4x10exp (-2)
14 -> 5x10exp (-2)
15 -> 6x10exp (-2)
16 -> 7x10exp (-2)
17 -> 8x10exp (-2)
18 -> 9x10exp (-2)
19 -> 10x10exp (-2)
20 -> 2x10exp (-1)
21 -> 3x10exp (-1)
22 -> 4x10 exp (-1)
23 -> 5x10 exp (-1)
Default value is 5 -> 5x10 exp (-3).
Packet loss in ethernet on DL Abis PL2 threshold PL2 = decimal number.
With this parameter you define the PL2 threshold value related to the percentage of the lost frames in the PSN compared to the corresponding expected frames (lost frames + received frames). Considering the Packet Loss Congestion definition, the proper reaction procedure is triggered when the difference between the PS loss frame rate and CS loss frame rate is higher than PL2 threshold. The range is from 1..23, and is inter-nally interpreted as below:
1 -> 10 exp (-3)
2 -> 2x10 exp (-3)
3 -> 3x10 exp (-3)
4 -> 4x10exp (-3)
5 -> 5x10exp (-3)
6 -> 6x10exp (-3)
7 -> 7x10exp (-3)
8 -> 8x10exp (-3)
9 -> 9x10exp (-3)
DN0963445DN0963445 Issue 01
185
Changes in RG20(BSS)
Id:0900d8058076d679
10 -> 10exp (-2)
11 -> 2x10exp (-2)
12 -> 3x10exp (-2)
13 -> 4x10exp (-2)
14 -> 5x10exp (-2)
15 -> 6x10exp (-2)
16 -> 7x10exp (-2) 17 -> 8x10exp (-2) 18 -> 9x10exp (-2) 19 -> 10x10exp (-2)20 -> 2x10exp (-1) 21 -> 3x10exp (-1)22 -> 4x10 exp (-1)23 -> 5x10 exp (-1)
Default value is 5 -> 5x10 exp (-3).packet abis congestion control PACC = Enumeration With parameter you define is Packet Abis congestion control procedure allowed, both Abis backhaul monitor and Abis Packet loss detection.The value range supported by this parameter is as below:
0 (Disable),
1 (Enable) Default value is 0.
downlink committed information rate DLCIR = decimal number.
With this parameter you define the Committed Information Rate in Downlink direction. The value range is from 100.. 250000 kbps, step 100 kbps.
maximum ETP multiplexing wait time MEMWT = Enumeration
With this parameter you define the maximum multiplexing wait time on ETP.
The value range supported by this parameter is as below:2 (2 ms), 4 (4 ms), 6 (6 ms)
Default value is 2(ms).
maximum BTS multiplexing wait time MBMWT = Enumeration
With this parameter you define the maximum multiplexing wait time on BTS.
The value range supported by this parameter is as below:
2 (2 radio timeslots),
4 (4 radio timeslots) and
8 (8 radio timeslots)
Default value is 2 radio timeslots
IPSec enabled IPSEC = Enumeration
With this parameter you define whether or not the IPSec feature is enabled in BTS.
The value range supported by this parameter is as below:
0 (Disable),
1 (Enable)
Default value is 0.
BFD Detection Time Multiplier BDTM = Number
The BFD Detect Mult parameter defines the detection time multiplier for BFD control packets indicating the number of control packets to be lost before a BFD session is declared down.
The range is from 2..10, step1
Default value is 5.
BFD Desired Minimum Interval BDMI = decimal number
The BFD Desired Min Interval parameter defines the minimum interval that the NE would like to use when transmitting BFD control packets.
The range is from 100..5000, Step 100.
Default value is 500.BFD
Required Minimum interval BRMI = decimal number
186 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
The BFD Desired Min Interval parameter defines the minimum interval between received BFD control packets that the NE is able to support. The range is from 100..5000, Step 100.
Default value is 500.
SyncE Mode
With Sync E Mode parameter you define if SyncE Mode in ETP. The value range sup-ported by this parameter is as: 0 (OFF), 1 (Master)
Default value is 0.
Modified Command M MODIFY BASE CONTROL FUNCTION PARAMETERS
Description of changes: New parameters Abis interface connection type, Packet Abis BCF group ID, Packet TRS E1/T1 usage, ETP group ID, Uplink traffic shaping, UL committed information rate, UL committed burst size, BTS C/U plane VLAN ID, Header compression for ML-PPP, Header compression for UDP IP, BU1 abis throughput threshold, 7,BU1 abis through-put threshold, Packet loss in ethernet on DL Abis PL1 threshold, Packet loss in ethernet on DL Abis PL2 threshold , Packet abis congestion control, Downlink committed infor-mation rate, Maximum ETP multiplexing wait time, Maximum BTS multi plexing wait time, Maximum multiplexing packet size, and IP sec enabled have been added.
Old syntax: EFM: <BCF identification> :( [ TYPE = <site type> |DNBR = <D-channel link set number> |DNAME = <D-channel link set name> |RXDL = <RX difference limit> |TEST = <identification of test equipment> |MCT = <master clock TRX> |ESS = <external syn-chronisation source> |AU = <automatic unlock allowed> |BBU = <BTS battery backup procedure> <option> |NTIM = <TRX shutdown timer> <option> |NTIM2 = <TRX shutdown timer 2> <option> |NTIM3 = <TRX shutdown timer 3> <option> |BTIM = <BCCH TRX shutdown timer>CS = <clock source> |SENA = <synch enabled> |ADD = <add BCF to chain> ... |REM = <remove BCF from chain> ... |OUT1 = <text ID of the output 1> |OUT2 = <text ID of the output 2> |OUT3 = <text ID of the output 3> |OUT4 = <text ID of the output 4> |OUT5 = <text ID of the output 5> |OUT6 = <text ID of the output 6> ] ... ) :[ T200F = <FACCH LAPDm T200> |T200S = <SDCCH LAPDm T200> ] :[ TRS1 = <Flexi EDGE Abis over IP Ethernet usage> <option> |TRS2 = <Flexi EDGE Additional 2 E1/T1 usage> <option> |TRS3 = <Flexi EDGE TRS Abis Grooming usage> <option> |TRS4 = <Flexi EDGE TRS Loop Protection usage> <option> ] ... ):[PORT0 = <PCM port ID 0> | ND def |[PORT1 = <PCM port ID 1> | ND def |[PORT2 = <PCM port ID 2> | ND def |[PORT3 = <PCM port ID 3> | ND def |[PORT4 = <PCM port ID 4> | ND def |[PORT5 = <PCM port ID 5> | ND def |[PORT6 = <PCM port ID 6> | ND def |[PORT7 = <PCM port ID 7> | ND def | ;
DN0963445DN0963445 Issue 01
187
Changes in RG20(BSS)
Id:0900d8058076d679
(EH) - Handover Control Parameter Handling
New syntax: EFM: <BCF identification> :( [ TYPE = <site type> | AICT=<Abis Interface Connection Type> |DNBR = <D-channel link set number> |DNAME = <D-channel link set name> |RXDL = <RX difference limit> |TEST = <identification of test equipment> |MCT = <master clock TRX> |ESS = <external synchronisation source> |AU = <automatic unlock allowed> |BBU = <BTS battery backup procedure> <option> |NTIM = <TRX shutdown timer> <option> |NTIM2 = <TRX shutdown timer 2> <option> |NTIM3 = <TRX shutdown timer 3> <option> |BTIM = <BCCH TRX shutdown timer>CS = <clock source> |SENA = <synch enabled> |ADD = <add BCF to chain> ... |REM = <remove BCF from chain> ... |OUT1 = <text ID of the output 1> |OUT2 = <text ID of the output 2> |OUT3 = <text ID of the output 3> |OUT4 = <text ID of the output 4> |OUT5 = <text ID of the output 5> |OUT6 = <text ID of the output 6> ] ... ) :[ T200F = <FACCH LAPDm T200> |T200S = <SDCCH LAPDm T200> ] :[ TRS1 = <Flexi EDGE Abis over IP Ethernet usage> <option> |TRS2 = <Flexi EDGE Additional 2 E1/T1 usage> <option> |TRS3 = <Flexi EDGE TRS Abis Grooming usage> <option> |TRS4 = <Flexi EDGE TRS Loop Protection usage> <option> |CSDAP1 = < Attached CSDAP 1> <option> |CSDAP2 = < Attached CSDAP 2> <option> |CSDAP3 = < Attached CSDAP 3> <option> |CSDAP4 = < Attached CSDAP 4> <option> |TRS5 = < PACKET TRS E1/T1 usage> <option> :| 0 def ] ..... :ETPGID = <ETP group ID> <option>,BHIDL = < BCF HDLC ID list > <option>...,[[ ULTS = <uplink traffic shaping> <option>|ULCIR = <UL committed information rate> <option>|ULCBS = <UL committed burst size> <option>|HECOP = <header compression for ML-PPP> <option>|HECOU = <header compression for UDP IP> <option>|
BU1 = <BU1 abis throughput threshold> <option>|BU2 = <BU2 abis throughput thresh-old> <option>|PL1 = <Packet loss in ethernet on DL Abis PL1 threshold> <option>|PL2 = <Packet loss in ethernet on DL Abis PL2 threshold> <option>|PACC = <packet abis congestion control> <option>|DLCIR = <downlink committed information rate> <option>|MEMWT = <maximum ETP multiplexing wait time> <option>|MBMWT = <maximum BTS multiplexing wait time> <option>|MMPS = <maximum multiplexing packet size> <option>|IPSEC = <IPSec enabled> <option>|PDV = <Packet delay vari-ation> <option>|VLANID = <VLAN id> <option>:[PORT0 = <PCM port ID 0> | ND def |[PORT1 = <PCM port ID 1> | ND def |[PORT2 = <PCM port ID 2> | ND def |[PORT3 = <PCM port ID 3> | ND def |[PORT4 = <PCM port ID 4> | ND def |[PORT5 = <PCM port ID 5> | ND def |[PORT6 = <PCM port ID 6> | ND def |[PORT7 = <PCM port ID 7> | ND def | ;
Modified Command M MODIFY BASE CONTROL FUNCTION PARAMETERS
Description of execution printout changes:
Execution printout command examples have been changed.
Modified Command O
Description of execution printout changes:
The execution printout for Flexi EDGE BTS for above parameters has been added.
Modified command(s) and menu text(s):
C CREATE HANDOVER CONTROL PARAMETERS
G MODIFY GENERAL PARAMETERS
Q MODIFY SIGNAL QUALITY THRESHOLD PARAMETERS
O OUTPUT HANDOVER CONTROL PARAMETERS
S MODIFY SIGNAL STRENGTH THRESHOLD PARAMETERS
188 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Modified Command C CREATE HANDOVER CONTROL PARAMETERS
Description of execution printout changes:
The new parameters enable hierarchical cell handover, threshold Dl Rx quality DHR, threshold Ul Rx quality DHR, OSC multiplexing Ul Rx level threshold, OSC multiplexing Ul Rx level window, OSC demultiplexing Ul Rx level margin,OSC DHR multiplexing Rx quality threshold, OSC DHR demultiplexing Rx quality threshold have been added to the additional information and the execution printouts.
Modified Command G MODIFY GENERAL PARAMETERS
Description of execution printout changes:
The new parameter enable hierarchical cell handover has been added to the command example.
Old syntax: EHG: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( EIC = <enable intracell handover interference UL> |EIH = <enable intracell handover interference DL> |EPB = <enable power budget handover> |EMS = <enable MS distance process> |ESD = <enable SDCCH handover> <option> |EUM = <enable umbrella handover> |EFA = <enable fast averaging call setup> |EFP = <enable fast averaging PC> |EFH = <enable fast averag-ing HO> |MIH = <min int between HO req> |MIU = <min int between unsucc HO attempt> |HPP = <handover period power budget> |HPU = <handover period umbrella> |ATPM = <AMH TRHO PBGT margin> <option> |ATCM = <AMH traffic control MCN> <option> |ATCI = <AMH traffic control IUO> <option> |GPP = <GSM PLMN priorisation> ) ... ;
New syntax: EHG: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( EIC = <enable intracell handover interference UL> |EIH = <enable intracell handover interference DL> |EPB = <enable power budget handover> |EMS = <enable MS distance process> |ESD = <enable SDCCH handover> <option> |EUM = <enable umbrella handover> |EFA = <enable fast averaging call setup> |EFP = <enable fast averaging PC> |EFH = <enable fast averag-ing HO> |EHC = <enable hierachical cell handover> <option> |MIH = <min int between HO req> |MIU = <min int between unsucc HO attempt> |HPP = <handover period power budget> |HPU = <handover period umbrella> |ATPM = <AMH TRHO PBGT margin> <option> |ATCM = <AMH traffic control MCN> <option> |ATCI = <AMH traffic control IUO> <option> |GPP = <GSM PLMN priorisation> ) ... ;
Modified Command Q MODIFY SIGNAL QUALITY THRESHOLD PARAMETERS
Description of changes: The new parameters OSC DHR multiplexing Rx quality threshold, OSC DHR demulti-plexing Rx quality threshold, Threshold Dl Rx Qual DHR, and Threshold Ul Rx Qual DHR have been added.
Old syntax: EHQ: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( QDR = <threshold qual downlink Rx qual> |QDP = <threshold qual downlink Px> |QDN = <threshold qual downlink Nx> |QUR = <threshold qual uplink Rx qual> |QUP = <threshold qual uplink Px> |QUN = <threshold qual uplink Nx> ) ... ;
New syntax: EHQ: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :(QDR = <threshold qual downlink Rx qual> |QDP = <threshold qual downlink Px> |QDN = <threshold qual downlink Nx> |QUR = <threshold qual uplink Rx qual> |QUP = <threshold qual uplink Px> |QUN = <threshold qual uplink Nx> |ODMQT = <OSC DHR multiplexing Rx quality threshold> <option> |ODDQT = <OSC DHR demultiplexing Rx quality threshold><option>|TDRQD = <threshold dl Rx qual DHR> <option> |TURQD = <threshold ul Rx qual DHR> <option> )... ;
DN0963445DN0963445 Issue 01
189
Changes in RG20(BSS)
Id:0900d8058076d679
Modified Command Q MODIFY SIGNAL QUALITY THRESHOLD PARAMETERSS
Description of execution printout changes:
The new parameters OSC DHR multiplexing Rx quality threshold, OSC DHR demulti-plexing Rx quality threshold, threshold Dl Rx quality DHR, and threshold Ul Rx quality DHR have been added to the execution printout of example 2.
Modified Command O OUTPUT HANDOVER CONTROL PARAMETERS
Description of execution printout changes:
The new parameters enable hierarchical cell handover, threshold Dl Rxquality DHR, threshold Ul Rx quality DHR, OSC multiplexing Ul Rx level threshold, OSC multiplexing Ul Rx level window, OSC demultiplexing Ul Rx level margin, OSC DHR multiplexing Rx quality threshold, OSC DHRdemultiplexing Rx quality threshold have been added to the additional information and the execution printouts.
Modified Command S MODIFY SIGNAL STRENGTH THRESHOLD PARAMETERS
Description of changes: The new parameters OSC multiplexing Ul Rx level threshold , OSC multiplexing Ul Rx level window, and OSC demultiplexing Ul Rx level margin have been added..
Old syntax: EHS: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( LDR = <threshold level downlink Rx level> |LDP = <threshold level downlink Px> |LDN = <threshold level downlink Nx> |LUR = <threshold level uplink Rx level> |LUP = <threshold level uplink Px> |LUN = <threshold level uplink Nx> |RPD = <threshold level uplink for rapid field drop> <option> |CNT = <count of successive rapid field drop thresholds><option> |ERFD = <enable enhanced rapid field drop> <option> |ERT = <threshold deep dropping edge> <option> |ERP = <threshold deep dropping edge Px> <option> |ERN = <threshold deep dropping edge Nx> <option> |ERMW = <deep dropping edge monitoring window> <option> |ERAW = <modified averaging window> <option> |ERZ = <modified number of zero results> <option> |ERD = <enhanced rapid field drop duration> <option> |LAR = <non bcch layer access threshold> <option> |LER = <non bcch layer exit threshold> <option> |LEP = <non bcch layer exit threshold px> <option> |LEN = <non bcch layer exit threshold nx> <option> ) ... ;
New syntax: EHS: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( LDR = <threshold level downlink Rx level> |LDP = <threshold level downlink Px> |LDN = <threshold level downlink Nx> |LUR = <threshold level uplink Rx level> |LUP = <threshold level uplink Px> |LUN = <threshold level uplink Nx> |RPD = <threshold level uplink for rapid field drop> <option> |CNT = <count of successive rapid field drop thresholds><option> |ERFD = <enable enhanced rapid field drop> <option> |ERT = <threshold deep dropping edge> <option> |ERP = <threshold deep dropping edge Px> <option> |ERN = <threshold deep dropping edge Nx> <option> |ERMW = <deep dropping edge monitoring window> <option> |ERAW = <modified averaging window> <option> |ERZ = <modified number of zero results> <option> |ERD = <enhanced rapid field drop duration> <option> |LAR = <non bcch layer access threshold> <option> |LER = <non bcch layer exit threshold> <option> |LEP = <non bcch layer exit threshold px> <option> |LEN = <non bcch layer exit threshold nx> <option> |OMLT = <OSC multiplexing ul Rx level threshold> <option> |OMLW = <OSC multiplexing ul Rx level window> <option> |ODMRG = <OSC demultiplexing ul Rx level margin> <option> )... ;
Modified Command S MODIFY SIGNAL STRENGTH THRESHOLD PARAMETERS
Description of execution printout changes:
The new parameters OSC multiplexing Ul Rx level threshold, OSC multiplexing Ul Rx level window, and OSC demultiplexing Ul Rx level margin have been added to the exe-cution printout of example 2.
190 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
(EQ) - Base Transceiver Station Handling in BSC
Modified command(s) and menu text(s)
C CREATE BTS
A MODIFY MOBILE ALLOCATION FREQUENCY LIST USAGE PARAMETERS
B MODIFY BCCH FREQUENCY LIST USAGE PARAMETERS <option>
E MODIFY BTS IDENTIFICATION PARAMETERS
M MODIFY MISCELLANEOUS PARAMETERS
O OUTPUT BTS PARAMETERS
V MODIFY GPRS PARAMETERS <option>
Modified Command C CREATE BTS
New parameters PCU index and BCU index have been added to parameter descrip-tion.
Old syntax: EQC : BCF = <BCF identification>,BTS = <BTS identification>,[[ NAME = <BTS name> | <no name> def ][ SEG = <SEG identification> <option> |<BTS identification> def ][ SEGNAME = <SEG name> <option> | <BTS name> def ][ REF = <reference BTS iden-tification> |RNAME= <reference BTS name> ]] :CI = <cell identity>,BAND = <frequency band in use>CHW = <cell number in BTS HW> :NCC = <network colour code>,BCC = <BTS colour code> :MCC = <mobile country code>,MNC = <mobile network code>,LAC = <location area code> :[[ HOP = <BTS hopping mode> | N def ][ UHOP = <underlay BTS hopping mode> <option> | N def ]HSN1 = <hopping sequence number 1> |HSN2 = <hopping sequence number 2> |UHSN = <underlay hopping sequence number> <option> ] ... :[[ GENA = <GPRS enabled> | N def <option> ][ RAC = <routing area code> | 255 def <option> ][[ NSEI = <network service entity identifier> <option> ] |[ TRAT = <transport type> | ANY def <option> ] |[ PSEI = <packet service entity iden-tifier> ]]] <option> ... ;
New syntax: EQC : BCF = <BCF identification>,BTS = <BTS identification>,[[ NAME = <BTS name> | <no name> def ][ SEG = <SEG identification> <option> |<BTS identification> def ][ SEGNAME = <SEG name> <option> | <BTS name> def ][ REF = <reference BTS iden-tification> |RNAME= <reference BTS name> ]] :CI = <cell identity>,BAND = <frequency band in use>CHW = <cell number in BTS HW> :NCC = <network colour code>,BCC = <BTS colour code> :MCC = <mobile country code>,MNC = <mobile network code>,LAC = <location area code> :[[ HOP = <BTS hopping mode> | N def ][ UHOP = <underlay BTS hopping mode> <option> | N def ]HSN1 = <hopping sequence number 1> |HSN2 = <hopping sequence number 2> |UHSN = <underlay hopping sequence number> <option> ] ... :[[ GENA = <GPRS enabled> | N def <option> ][ RAC = <routing area code> | 255 def <option> ][[ NSEI = <network service entity identifier> <option> |TRAT = <transport type> | ANY def <option> |PSEI = <packet service entity identifier> |BCSU = <base station controller signaling unit> <option> |PCU = <packet control unit> <option> ]]] <option> ... ;
The command entry continues in the same way as before after a semantic error.
Modified Command C CREATE BTS
Description of execution printout changes:
The new parameter PCU Object State has been added and execution printout has been updated.
Modified Command A MODIFY MOBILE ALLOCATION FREQUENCY LIST USAGE PARAMETERS
DN0963445DN0963445 Issue 01
191
Changes in RG20(BSS)
Id:0900d8058076d679
Description of changes: The value range of parameters Mobile allocation frequency list (MAL), Underlay mobile allocation frequency list (UMAL), DFCA mobile allocation frequency lists (DMAL), DFCA unsynchronized mode MA frequency list (DUMAL) have been updated.
Old semantics: The value range of MAL is 0 – 3000
The value range of UMAL is 0 – 3000
The value range of DMAL is 0 – 32
The values range of DUMAL is 1 - 32.
New semantics: The value range of MAL is 0 – 4200
The value range of UMAL is 0 – 4200
The value range of DMAL is 1 – 64
The values range of DUMAL is 0 – 4200.
Modified Command B MODIFY BCCH FREQUENCY LIST USAGE PARAMETERS <option>
Description of changes: The value range of parameter Identification of BCCH frequency list (IDLE) has been updated.
Old semantics: The value range of IDLE is 0 – 3000
New semantics: The value range of IDLE is 0 – 4200
Modified Command E EQE MODIFY BTS IDENTIFICATION PARAMETERS
Description of changes: The parameter description has been updated for Antenna Hopping (AHOP) parameter.
Old description Only UltraSite EDGE and Flexi EDGE hardware and EDGE transceivers (TRX) support antenna hopping.
New description Only UltraSite EDGE HW, Flexi EDGE HW, EDGE TRXs, BTSplus and Flexi Multiradio support antenna hopping.
Modified Command M EQM MODIFY MISCELLANEOUS PARAMETERS
Description of changes: New parameters upper DL RX level threshold for BCCH TRX preference (UDRB), lower DL RX level threshold for BCCH TRX preference (LDRB), Merged PGSM and EGSM Enabled (MPE), Limit for Triggering OSC DHR Multiplexing (DHRLIM), LTE CELL RESELECTION PARAMETERS [GSM PRIORITY (GPRIO), WCDMA PRIORITY (WPRIO),PRIORITY SEARCH THRESHOLD (PSTHR), LOW PRIORITY THRESH-OLD (LPTHR), RESELECTION ALGORITHM HYSTERESIS(HPRIO), TIME HYSTER-ESIS (TIMEH)] have been added to parameter description and execution printout has been updated.
192 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Old semantics EQM: ( BTS = <BTS identification> |NAME = <BTS name>SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( [ DTX = <DTX mode> |BMA = <BTS measure average> |PMAX1 = <MS tx pwr max gsm> |PMAX2 = <MS tx pwr max gsm1x00> |PMIN = <MS tx pwr min> |RET = <max number of retransmission> |NY1 = <max number of repetition> |SLO = <number of slots spread trans> |CB = <SMS CB used> |BLT = <BTS load threshold> |DMAX = <MS max distance in call setup> |TRP = <TRX priority in TCH allocation> |CLC = <cell load for channel search> |RDIV = <RX diversity> |TRIH = <TCH rate intra-cell handover> <option> |FRL = <lower limit for FR TCH resources> <option> |FRU = <upper limit for FR TCH resources> <option> |AFRL = <AMR lower limit for SEG FR resources> <option> |AFRU = <AMR upper limit for SEG FR resources> <option> |NECI = <new establishment causes support> |EXT = <radius extension> <option> |SEXT = <super radius extension> <option> |MBR = <multiband cell reporting> <option> |ESI = <early sending indication > |NBL = <non BCCH layer offset> <option> |LSEG = <BTS load in SEG> <option> |SCO = <scale ord> <option> |AUT = <AMH upper load threshold> <option> |ALT = <AMH lower load threshold> <option> |AML = <AMH max load of target cell> <option> |TGT = <TRHO guard time> |DLN = <DL noise level> |ULN = <UL noise level> |STIRC = <STIRC enabled> <option> |ISIC = <immediate SDCCH HO enabled> <option>... ] ... :[ PWDT = <DTRX power down threshold> |PWUT = <DTRX power up threshold> ] <option> ... :[ PI = <cell reselection parameter index> |QUA = <cell bar qualify> |REO = <cell reselect offset> |
TEO = <temporary offset> |PET = <penalty time> ] <option> ... :[ QSRI = <threshold to search UTRAN cells> <option> |QSRP = <gprs threshold to search UTRAN cells> <option> |FDD = <fdd and tdd cell reselect offset> <option> |FDM = <minimum fdd threshold> <option> |FDMO = <minimum fdd threshold offset> <option> |FDR = <minimum RSCP threshold> <option> ] ... :[ DMOD = <DFCA mode> |FHR = <forced HR mode C/I averaging period> <option> |FHT = <forced HR mode C/I threshold> <option> |FAHT = <forced AMR HR mode C/I threshold> <option> |FHH = <forced HR mode hysteresis> <option> ] :[ IGE = <IBHO GSM enabled> |IWE = <IBHO WCDMA enabled> ] <option> ) ... :[ SMREPS = <SDCCH measurement report sending> |IMREPS = <interval measurement report sending> |FACHBT = <FACH busy thresh-old> |RACHBT = <RACH busy threshold> |RSRDL = <repeated SACCH RX lev thresh-old DL> |RSRUL = <repeated SACCH RX lev threshold UL> |RSDL = <repeated SACCH in DL> |RSUL = <repeated SACCH in UL> |ETOP = <enable temporary over-power> |RFDL = <repeated FACCH in DL> |RFUL = <repeated FACCH in UL> |ARF = <apply repeated FACCH>|CUCONF = <carrier unit configuration> |TXDIV = <TX diver-sity time shift> ])... ;
DN0963445DN0963445 Issue 01
193
Changes in RG20(BSS)
Id:0900d8058076d679
New semantics EQM: ( BTS = <BTS identification> |NAME = <BTS name>SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( [ DTX = <DTX mode> |BMA = <BTS measure average> |PMAX1 = <MS tx pwr max gsm> |PMAX2 = <MS tx pwr max gsm1x00> |PMIN = <MS tx pwr min> |RET = <max number of retransmission> |NY1 = <max number of repetition> |SLO = <number of slots spread trans> |CB = <SMS CB used> |BLT = <BTS load threshold> |DMAX = <MS max distance in call setup> |TRP = <TRX priority in TCH allocation> |CLC = <cell load for channel search> |RDIV = <RX diversity> |TRIH = <TCH rate intra-cell handover> <option> |FRL = <lower limit for FR TCH resources> <option> |FRU = <upper limit for FR TCH resources> <option> |AFRL = <AMR lower limit for SEG FR resources> <option> |AFRU = <AMR upper limit for SEG FR resources> <option> |DHRLIM = <Limit for Triggering OSC DHR Multiplexing> <option> |NECI = <new establishment causes support> |EXT = <radius extension> <option> |SEXT = <super radius extension> <option> |MBR = <multiband cell report-ing> <option> |ESI = <early sending indication > |NBL = <non BCCH layer offset> <option> |LSEG = <BTS load in SEG> <option> |SCO = <scale ord> <option> |AUT = <AMH upper load threshold> <option> |ALT = <AMH lower load threshold> <option> |AML = <AMH max load of target cell> <option> |TGT = <TRHO guard time> |DLN = <DL noise level> |ULN = <UL noise level> |STIRC = <STIRC enabled> <option> |ISIC = <immediate SDCCH HO enabled> <option> |UDRB = <upper DL RX level threshold for BCCH TRX preference> <option> |LDRB = <lower DL RX level threshold for BCCH TRX preference> <option> ] :[ PWDT = <DTRX power down threshold> |PWUT = <DTRX power up threshold> |
MPE = <Merged PGSM and EGSM Enabled>] <option> ... :[ PI = <cell reselection parameter index> |QUA = <cell bar qualify> |REO = <cell reselect offset> |TEO = <tem-porary offset> |PET = <penalty time> ] <option> ... :[ QSRI = <threshold to search UTRAN cells> <option> |QSRP = <gprs threshold to search UTRAN cells> <option> |FDD = <fdd and tdd cell reselect offset> <option> |EQM MODIFY MISCELLANEOUS PARAMETERSFDM = <minimum fdd threshold> <option> |FDMO = <minimum fdd threshold offset> <option> |FDR = <minimum RSCP threshold> <option> ] ... :[ DMOD = <DFCA mode> |FHR = <forced HR mode C/I averaging period> <option> |FHT = <forced HR mode C/I threshold> <option> |FAHT = <forced AMR HR mode C/I thresh-old> <option> |FHH = <forced HR mode hysteresis> <option> ] :[ IGE = <IBHO GSM enabled> |IWE = <IBHO WCDMA enabled> ] <option> ) ... :[ SMREPS = <SDCCH measurement report sending> |IMREPS = <interval measurement report sending> |FACHBT = <FACH busy threshold> |RACHBT = <RACH busy threshold> |RSRDL = <repeated SACCH RX lev threshold DL> |RSRUL = <repeated SACCH RX lev thresh-old UL> |RSDL = <repeated SACCH in DL> |RSUL = <repeated SACCH in UL> |ETOP = <enable temporary overpower> |RFDL = <repeated FACCH in DL> |RFUL = <repeated FACCH in UL> |ARF = <apply repeated FACCH>|CUCONF = <carrier unit configuration> |TXDIV = <TX diversity time shift> ])... ;[ GPRIO = <GSM priority> |WPRIO = <WCDMA priority> |PSTHR = <Priority search threshold> |LPTHR = <Low priority threshold> |HPRIO = <Reselection algorithm hysteresis> |TIMEH = <Time hys-teresis> ] <option> );
Modified Command O EQO OUTPUT BTS PARAMETERS
Description of changes: The execution printouts has been updated with new parameters upper DL RX level threshold for BCCH TRX preference (UDRB), lower DL RX level threshold for BCCH TRX preference (LDRB), PCU Object State, Merged PGSM and EGSM Enabled (MPE),Limit for Triggering OSC DHR Multiplexing (DHRLIM), LTE CELL RESELEC-TION PARAMETERS [GSM PRIORITY (GPRIO), WCDMAPRIORITY (WPRIO), PRIORITY SEARCH THRESHOLD (PSTHR),LOW PRIORITY THRESHOLD (LPTHR), RESELECTION ALGORITHMHYSTERESIS (HPRIO), and TIME HYSTER-ESIS (TIMEH)].
Modified Command V MODIFY GPRS PARAMETERS <option>
194 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Description of changes: New parameters PCU index, BCU index, and GPRS capacity throughput factor (GCTF) have been added to parameter description and execution printout has been updated.
Old syntax: EQV: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( [ GENA = <GPRS enabled> |EGENA = <EGPRS enabled> <option> |RAC = <routing area code> |CDED = <dedi-cated GPRS capacity> |CDEF = <default GPRS capacity> |CMAX = <max GPRS capacity> |BFG = <prefer BCCH frequency GPRS> |DLA = <DL adaptation probability threshold> |ULA = <UL adaptation probability threshold> |DLB = <DL BLER crosspoint for CS selection no hop> |ULB = <UL BLER crosspoint for CS selection no hop> |DLBH = <DL BLER crosspoint for CS selection hop> |ULBH = <UL BLER crosspoint for CS selection hop> |COD = <coding scheme no hop> |CODH = <coding scheme hop> |MCA = <initial MCS for acknowledged mode> |MCU = <initial MCS for unacknowl-edged mode> |BLA = <maximum BLER in acknowledged mode> | BLU = <maximum BLER in unacknowledged mode> |MBG = <mean BEP offset GMSK> |MBP = <mean BEP offset 8PSK> |ELA = <EGPRS link adaptation enabled> <option> |CS34 = <coding schemes CS3 and CS4 enabled> <option> |DCSA = <DL coding scheme in acknowledged mode> |UCSA = <UL coding scheme in acknowledged mode> |DCSU = <DL coding scheme in unacknowledged mode> |UCSU = <UL coding scheme in unacknowledged mode> |ALA = <adaptive LA algorithm> |EXGENA = <extended cell GPRS/EDGE enabled> <option> |EXKEEP = <extended cell location keep period> <option> |DCSEA = <DL coding scheme in ext area acknowledged mode> <option> |DCSEU = <DL coding scheme in ext area unacknowledged mode> <option> |UCSEA = <UL coding scheme in ext area acknowledged mode> <option> |UCSEU = <UL coding scheme in ext area unacknowledged mode> <option> |MCEA = <initial MCS for ext area acknowledged mode> <option> |MCEU = <initial MCS for ext area unacknowl-edged mode> <option> ] ... :[ NSEI = <network service entity identifier> <option> |TRAT = <transport type> <option> |PSEI = <packet service entity identifier> <option> ] :[ TFU = <BTS uplink throughput factor for CS1-CS4> |
TFD = <BTS downlink throughput factor for CS1-CS4 > |TFUM1 = <BTS uplink throughput factor for MCS1-MCS4> |TFUM = <BTS uplink throughput factor for MCS1-MCS9> |TFDM = <BTS downlink throughput factor for MCS1-MCS9>EAW = <EGPRS inactivity alarm weekdays> <option> ... |EAS = <EGPRS inactivity alarm start time> <option> |EAE = <EGPRS inactivity alarm end time> <option> |DCENA = <DLDC enabled> <option> ] :[ DENA = <DTM enabled> <option> ] ) ... ; <option>
DN0963445DN0963445 Issue 01
195
Changes in RG20(BSS)
Id:0900d8058076d679
(ER) - Transceiver Handling
New syntax: EQV: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( [ GENA = <GPRS enabled> |EGENA = <EGPRS enabled> <option> |RAC = <routing area code> |CDED = <dedi-cated GPRS capacity> |CDEF = <default GPRS capacity> |CMAX = <max GPRS capacity> |BFG = <prefer BCCH frequency GPRS> |DLA = <DL adaptation probability threshold> |ULA = <UL adaptation probability threshold> |DLB = <DL BLER crosspoint for CS selection no hop> |ULB = <UL BLER crosspoint for CS selection no hop> |DLBH = <DL BLER crosspoint for CS selection hop> |ULBH = <UL BLER crosspoint for CS selection hop> |COD = <coding scheme no hop> |CODH = <coding scheme hop> |MCA = <initial MCS for acknowledged mode> |130 DN9813242Issue 26-0EQ - Base Transceiver Station Handling in BSCId:0900d80580719d64EQV MODIFY GPRS PARAMETERS <option>MCU = <initial MCS for unacknowledged mode> |BLA = <maximum BLER in acknowledged mode> |BLU = <maximum BLER in unacknowl-edged mode> |MBG = <mean BEP offset GMSK> |MBP = <mean BEP offset 8PSK> |ELA = <EGPRS link adaptation enabled> <option> |CS34 = <coding schemes CS3 and CS4 enabled> <option> |DCSA = <DL coding scheme in acknowledged mode> |UCSA = <UL coding scheme in acknowledged mode> |DCSU = <DL coding scheme in unacknowledged mode> |UCSU = <UL coding scheme in unacknowledged mode> |ALA = <adaptive LA algorithm> |EXGENA = <extended cell GPRS/EDGE enabled> <option> |EXKEEP = <extended cell location keep period> <option> |DCSEA = <DL coding scheme in ext area acknowledged mode> <option> |DCSEU = <DL coding scheme in ext area unacknowledged mode> <option> |UCSEA = <UL coding scheme in ext area acknowledged mode> <option> |UCSEU = <UL coding scheme in ext area unacknowledged mode> <option> |MCEA = <initial MCS for ext area acknowledged mode> <option> |
MCEU = <initial MCS for ext area unacknowledged mode> <option> ] ... :[ NSEI = <network service entity identifier> <option> |TRAT = <transport type> <option> |PSEI = <packet service entity identifier> <option> |BCSU = <base station controller signaling unit> <option> |PCU = <packet control unit> <option> ]|[ TFU = <BTS uplink throughput factor for CS1-CS4> |TFD = <BTS downlink throughput factor for CS1-CS4 > |TFUM1 = <BTS uplink throughput factor for MCS1-MCS4> |TFUM = <BTS uplink throughput factor for MCS1-MCS9> |TFDM = <BTS downlink throughput factor for MCS1-MCS9>GCTF = <GPRS capacity throughput factor> <option> |EAW = <EGPRS inac-tivity alarm weekdays> <option> ... |EAS = <EGPRS inactivity alarm start time> <option> |EAE = <EGPRS inactivity alarm end time> <option> |DCENA = <DLDC enabled> <option> ] :[ DENA = <DTM enabled> <option> ] ) ... ; <option>
Modified command(s) and menu text(s)
O OUTPUT TRANSCEIVER PARAMETERS
Modified Command O OUTPUT TRANSCEIVER PARAMETERS
Description of changes New TRX object parameters-TRX RF Power, Number of TRX RF Power Levels, TRX Starting Mode, and TRX OSC Capability-have been added. Possible values of these parameters are 0, 1, 2, 3 and 4.
Modified Command O OUTPUT TRANSCEIVER PARAMETERS
Description of execution printout changes:
New execution printouts have been added with these parameters information.
196 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
(ES) - Abis Interface Configuration
New command(s) and menu text(s)
A CREATE ABIS DELAY MEASUREMENT CHANNEL
R DELETE ABIS DELAY MEASUREMENT CHANNEL
Q OUTPUT ABIS DELAY MEASUREMENT CHANNEL INFORMATION
T CREATE CIRCUIT SWITCHED DYNAMIC ABIS POOL
V DELETE CIRCUIT SWITCHED DYNAMIC ABIS POOL
U MODIFY CIRCUIT SWITCHED DYNAMIC ABIS POOL
B OUTPUT CIRCUIT SWITCHED DYNAMIC ABIS POOL
X CREATE ABIS HDLC LINK
F MODIFY ABIS HDLC LINK
Y DELETE ABIS HDLC LINK
S CHANGE ABIS HDLC LINK ADMINISTRATIVE STATE
K CREATE ETP-PCU CONNECTION
H REMOVE ETP-PCU CONNECTION
L OUTPUT PACKET ABIS CONFIGURATION
J MODIFY ETP PARAMETERS
New Command A CREATE ABIS DELAY MEASUREMENT CHANNEL
Description of changes: New command added to create new measurement channel for Abis Delay Measure-ment usage.
New syntax: ESA: BCF = <BCF identification>,
CRCT = <circuit>; <option>;
Parameters: New parameters have been added:
BCF identification–This parameter is obligatory.
Circuit–This parameter is obligatory.
New Command R DELETE ABIS DELAY MEASUREMENT CHANNEL <option>
Description changes: New command added for deleting measurement channel(s) from Abis Delay Measure-ment usage.
New syntax: ESR:(ALL |
BCF = <BCF identification> |
MCH = <measurement channel identification> |
CRCT = <circuit>);
Parameters: New parameters have been added:
BCF identification–This parameter is obligatory.
Measurement channel identification–The value range is values from 1 to 1000.
Circuit–This parameter is obligatory.
DN0963445DN0963445 Issue 01
197
Changes in RG20(BSS)
Id:0900d8058076d679
New Command Q OUTPUT ABIS DELAY MEASUREMENT CHANNEL INFORMATION <option>
Description of changes: New command added for printing the information of Abis Delay Measurement chan-nel(s).
New syntax: ESQ:[[ALL | BCF=<BCF identification>] | ALL def];
Parameters: New parameter has been added:
BCF identification–This parameter is obligatory.
New Command T CREATE CIRCUIT SWITCHED DYNAMIC ABIS POOL <option>
Description of changes: New command added for creating Circuit Switched Dynamic Abis Pool.
New syntax: EST:CID = <CSDAP id>,
CRCT = <circuit>,
SIZE = <pool size>,
BAIF = <BCF Abis IF> <option>,
SHIFT = <BCF Timeslot Shift>; <option>
Parameters: New parameters have been added:
csdap ID–The value range is values from 1 to 1000. This parameter is obligatory.
Circuit –This parameter is obligatory.
Pool size–Pool size in ETSI is in the range from 1 to 31 whereas in ANSI in the range from 1 to 24.
BCF Abis Interface–The value range is from 1–16. This parameter is not obligatory.
BCF Timeslot Shift–The value range of the value is -30 to 30. This parameter is not obligatory.
New Command V DELETE CIRCUIT SWITCHED DYNAMIC ABIS POOL <option>
Description of changes: New command added for deleting the Circuit Switched Dynamic Abis Pool.
New syntax: ESV: CID = <CSDAP id>; <option>
Parameters: New parameter has been added:
csdap ID–The value range is values from 1 to 1000. This parameter is obligatory.
New Command U MODIFY CIRCUIT SWITCHED DYNAMIC ABIS POOL <option>
Description of changes: New command added for modifying Circuit Switched Dynamic Abis Pool.
New syntax: ESU:CID = <CSDAP id>,
NFT = <New First Time Slot>,
NLT = <New LastTime Slot>,
BAIF = <BCF Abis IF> <option>,
SHIFT = <BCF Timeslot Shift>; <option>;
198 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Parameters: New parameters have been added:
csdap ID - The value range is values from 1 to 1000. This parameter is obligatory.
New First Time Slot
New Last Time Slot
BCF abis interface – The value range is from 1 – 16.
BCF Timeslot Shift – The value range is from -30 to 30.
New Command B OUTPUT CIRCUIT SWITCHED DYNAMIC ABIS POOL <option>
Description of changes: New command added to show existing Circuit Switched Dynamic Abis Pool.
New syntax: ESB: CID=<CSDAP ID>; <option>
Parameters: New parameters have been added:
csdap ID - The value range is values from 1 to 1000. This parameter is obligatory.
New Command X CREATE ABIS HDLC LINK <option>
Description of changes: New command added to create Abis HDLC link.
New syntax: ESX: HNBR = <HDLC link identification>,
[ HNAME = <HDLC link name> | <no name> def ],
HPCM = <external pcm>,
HTSL = <start tsl>,
HBAND = <HDLC link bandwith>; <option>
Parameters: New parameters have been added:
HDLC link identification - The values range from 1 to 3000.
HDLC link name - The values range from 0 to 15 characters.
HDLC PCM ID - The values range from 0 to 3559.
HDLC start TSL - The values range from 1 to 30.
HDLC link bandwith - The values range from 2 to 31.
New Command F MODIFY ABIS HDLC LINK <option>
Description of changes: New command added to modify Abis HDLC link bandwidth.
New syntax: ESF: [ HNBR = <HDLC link identification>...
|HNAME = <HDLC link name> ],
HBAND = <HDLC link bandwith>; <option>
Parameters: New parameters have been added:
HDLC link identification - The values range from 1 to 3000.
HDLC link name - The values range from 0 to 15 characters.
HDLC link bandwith - The values range from 2 to 31.
New Command Y DELETE ABIS HDLC LINK <option>
Description of changes: New command added to delete Abis HDLC link.
DN0963445DN0963445 Issue 01
199
Changes in RG20(BSS)
Id:0900d8058076d679
New syntax: ESY: ( HNBR = <HDLC link identification>...
|HNAME = <HDLC link name> ); <option>
Parameters New parameters have been added:
HDLC link identification - The values range from 1 to 3000.
HDLC link name - The values range from 0 to 15 characters.
New Command S CHANGE ABIS HDLC LINK ADMINISTRATIVE STATE <option>
Description of changes New command added to change Abis HDLC link administrative state..
New syntax: ESS: ( HNBR = <HDLC link identification>...
|HNAME = <HDLC link name> ):
STATE = <HDLC link administrative state>; <option>
Parameters: New parameters have been added:
HDLC link identification - The values range from 1 to 3000.
HDLC link name - The values range from 0 to 15 characters.
HDLC link administrative state <Option> – The possible values are 1 and 3.
New Command K CREATE ETP-PCU CONNECTION <option>
Description of changes: New command added to remove ETP-PCU connection.
New syntax: ESK: <ETP type>,
<ETP group id>:
<Unit>,
<Unit Index>:
<Plugin Unit>,
<Plugin Unit Index>; <option>
Parameters: New parameters have been added:
ETP type- With this parameter you define ETP type of ETP unit to be used for Packet Abis. ETPGroup ID and ETP type is needed to identify ETP group.
ETP Group ID- With this parameter you define ETP group ID. ETP Group ID and ETP type is needed to identify ETP group.The values range from 0 to 15.
Unit-The attribute defines the unit type. For ETP-PCU Connection the Unit Type is BCSU.This parameter is obligatory.
Unit Index-The attribute defines the BCSU unit index. With this parameter you identify the basestation signalling unit logical index where you want to connect to the ETP. The value ranges from: 0 to 10 for BSC3i 2000, 0 to 6 for Flexi BSC.
Plug In Unit-The attribute defines the plug in unit connected. For ETP-PCU Connection the Plug inUnit Type is PCu. This parameter is obligatory.
Plugin Unit Index-The attribute defines the PCU unit index. With this parameter you identify the packet control unit index where you want to connect to the ETP. The value ranges from 0 to 254.
New Command H REMOVE ETP-PCU CONNECTION <option>
200 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Description of changes: New command added to remove ETP-PCU connection.
New syntax: ESH: <ETP type>,
<ETP group id>:
<Unit>,
<Unit Index>:
<Plugin Unit>,<Plugin Unit Index>; <option>
Parameters: New parameters have been added:
ETP type- With this parameter you define ETP type of ETP unit to be used for Packet Abis. ETPGroup ID and ETP type is needed to identify ETP group.
ETP Group ID- With this parameter you define ETP group ID. ETP Group ID and ETP type is needed to identify ETP group. The values range from 0 to 15.
Unit-The attribute defines the unit type. For ETP-PCU Connection the Unit Type is BCSU. This parameter is obligatory.
Unit Index-The attribute defines the BCSU unit index. With this parameter you identify the basestation signalling unit logical index where you want to connect to the ETP. The value ranges from: 0 to 10 for BSC3i 2000, 0 to 6 for Flexi BSC.
Plug In Unit-The attribute defines the plug in unit connected.For ETP-PCU Connection the Plug inUnit Type is PCu. This parameter is obligatory.
Plugin Unit Index-The attribute defines the PCU unit index. With this parameter you identify the packet control unit index where you want to connect to the ETP.The value ranges from 0 to 254.
New Command L OUTPUT PACKET ABIS CONFIGURATION <option>
Description of changes: New command added to get output of Packet Abis configuration data.
New syntax: ESL: <HDLC link id>...:
<ETP type>,
<ETP group id>:
[ <HDLC configuration> |
<BCF configuration> |
<PCU configuration> |
<all parameters> ] ; <option>
Parameters: New parameters have been added:
HDLC link ID– The possible values are 1 and 3000.
ETP type – The possible values are ETPT and ETPE.
ETP Group ID - The values range from 0 to 15.
New Command J MODIFY ETP PARAMETERS <option>
Description of change: New command created to modify ETP level application parameter SyncE Mode.
New syntax: ESJ: <ETP type>,
<ETP group id>,
<syncE Mode>; <option>
DN0963445DN0963445 Issue 01
201
Changes in RG20(BSS)
Id:0900d8058076d679
(EU) - Power Control Parameter Handling
Parameters: New parameters have been added:
ETP type – The possible values are 1 and 2.
ETP Group ID - The values range from 0 to 15.
SyncE Mode – The possible values are 1 and 2.
Modified command(s) and menu text(s)
C CREATE POWER CONTROL PARAMETERS
Q MODIFY SIGNAL QUALITY THRESHOLD PARAMETERS
O OUTPUT POWER CONTROL PARAMETERS
Modified Command C CREATE POWER CONTROL PARAMETERS
Description of changes: New parameters PC Lower Threshold Dl Rx Qual DHR, PC LowerThreshold Ul Rx Qual DHR, PC Upper Threshold Dl Rx Qual DHR, andPC Upper Threshold Ul Rx Qual DHR have been added. The value range for PC Lower Threshold Dl Rx Qual DHR <option> is from 0 to 7. The default value is 3. The value range for PC Lower Threshold Ul Rx Qual DHR <option> is from from 0 to 7. The default value is 3. The value range for PC Upper Threshold Ul Rx Qual DHR is from 0 to 7. The default value is 0.The values range for PC Upper Threshold Ul Rx Qual DHR is from 0 to 7. The default value is 0.
Old syntax: EUC: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ),[ REF = <reference BTS identifica-tion> |RNAME = <reference BTS name> |RSEG = <reference SEG identification> <option> |RSEGNAME = <reference SEG name> <option> ] ;
New syntax: EUC: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ),[ REF = <reference BTS identifica-tion> |RNAME = <reference BTS name> |RSEG = <reference SEG identification> <option> |RSEGNAME = <reference SEG name> <option> ]... :[ UDDHR = <pc upper threshold dl Rx qual DHR> |UUDHR = <pc upper threshold ul Rx qual DHR> |LDDHR = <pc lower threshold dl rx qual DHR> |LUDHR = <pc lower threshold ul Rx qual DHR> ]<option> ) ... ;
Modified Command Q MODIFY SIGNAL QUALITY THRESHOLD PARAMETERS
Description of changes: New parameters PC Lower Threshold Dl Rx Qual DHR, PC LowerThreshold Ul Rx Qual DHR, PC Upper Threshold Dl Rx Qual DHR, and PC Upper Threshold Ul Rx Qual DHR have been added. The value range for PC Lower Threshold Dl Rx Qual DHR <option> is from 0 to 7. The default value is 3. The value range for PC Lower Threshold Ul Rx Qual DHR <option> is from from 0 to 7. The default value is 3. The value range for PC Upper Threshold Ul Rx Qual DHR is from 0 to 7. The default value is 0.The values range for PC Upper Threshold Ul Rx Qual DHR is from 0 to 7. The default value is 0.
202 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
(FX) - Gb Interface Handling
Old syntax: EUQ: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( UDR = <pc upper thresholds qual dl Rx qual> |UDP = <pc upper thresholds qual dl Px> |UDN = <pc upper thresholds qual dl Nx> |UUR = <pc upper thresholds qual ul Rx qual> |UUP = <pc upper thresholds qual ul Px> |UUN = <pc upper thresholds qual ul Nx> |LDR = <pc lower thresholds qual dl Rx qual> |LDP = <pc lower thresholds qual dl Px> |LDN = <pc lower thresholds qual dl Nx> |LUR = <pc lower thresholds qual ul Rx qual> |LUP = <pc lower thresholds qual ul Px> |LUN = <pc lower thresholds qual ul Nx> |LQR = <pc lower thresholds qual144 Rx qual> |LQP = <pc lower thresholds qual144 Px> |LQN = <pc lower thresholds qual144 Nx> ) ... ;
New syntax: EUQ: ( BTS = <BTS identification> |NAME = <BTS name> |SEG = <SEG identification> <option> |SEGNAME = <SEG name> <option> ) :( UDR = <pc upper thresholds qual dl Rx qual> |UDP = <pc upper thresholds qual dl Px> |UDN = <pc upper thresholds qual dl Nx> |UUR = <pc upper thresholds qual ul Rx qual> |UUP = <pc upper thresholds qual ul Px> |UUN = <pc upper thresholds qual ul Nx> |LDR = <pc lower thresholds qual dl Rx qual> |LDP = <pc lower thresholds qual dl Px> |LDN = <pc lower thresholds qual dl Nx> |LUR = <pc lower thresholds qual ul Rx qual> |LUP = <pc lower thresholds qual ul Px> |LUN = <pc lower thresholds qual ul Nx> |LQR = <pc lower thresholds qual144 Rx qual> |LQP = <pc lower thresholds qual144 Px> |LQN = <pc lower thresholds qual144 Nx> )[ UDDHR = <pc upper threshold dl Rx qual DHR> |UUDHR = <pc upper threshold ul Rx qual DHR> |LDDHR = <pc lower threshold dl rx qual DHR> |LUDHR = <pc lower threshold ul Rx qual DHR> ]<option> ) ... ;
Modified Command Q MODIFY SIGNAL QUALITY THRESHOLD PARAMETERS
Description of execution printout changes:
New parameters PC Lower Threshold Dl Rx Qual DHR, PC Lower Threshold Ul Rx Qual DHR, PC Upper Threshold Dl Rx Qual DHR, and PC Upper Threshold Ul Rx Qual DHR have been added in examples 2 and 3 of execution printout.
Modified Command O STOP GSM MEASUREMENT
Description of execution printout changes:
New parameters PC Lower Threshold Dl Rx Qual DHR, PC Lower Threshold Ul Rx Qual DHR, PC Upper Threshold Dl Rx Qual DHR, and PC Upper Threshold Ul Rx Qual DHR have been added in example 1 of execution printout.
Modified command(s) and menu text(s)
O OUTPUT THE NETWORK SERVICE VIRTUAL CONNECTION DATA
F MODIFY PACKET SERVICE ENTITY
L OUTPUT PACKET SERVICE ENTITY DATA
Modified Command O OUTPUT THE NETWORK SERVICE VIRTUAL CONNECTION DATA
Description of execution printout changes:
The execution printout of example 5 has been updated.
Modified Command F MODIFY PACKET SERVICE ENTITY
Description of changes: The parameter explanation for RAE parameter has been changed.
DN0963445DN0963445 Issue 01
203
Changes in RG20(BSS)
Id:0900d8058076d679
(TP) - GSM Measurement Handling
Old semantics: With this parameter you can allow DAP and BTS reallocation. This means that BTS and DAP configuration is divided between the PCUs of the PSE. This can be done when anew PCU is added to the PSE.
New semantics: With this parameter you can allow DAP and BTS reallocation when a new PCU is added to the PSE. This means that BTS and DAP configuration is divided between the PCUs of the PSE.
Modified Command L OUTPUT PACKET SERVICE ENTITY DATA
Description of execution printout changes:
The execution printout of example 1, 3, 4 and 5 has been updated.
Modified command(s) and menu text(s)
M MODIFY GSM MEASUREMENT CHARACTERISTICS
I INTERROGATE GSM MEASUREMENT
S START GSM MEASUREMENT
E STOP GSM MEASUREMENT
Modified Command M MODIFY GSM MEASUREMENT CHARACTERISTICS
Description of changes: New measurements ABIS_DELAY, PA_BTS, PA_TRAFFIC, PA_SCTP, PA_DELAY, ETP_ETH_BSC, AOIP_TR_BSC, AOIP_TR_TCSM, ETP_ETH_TCSM have been added in the transmission measurements category. New measurements CSDAP, OSC_RXQUAL, and PA_CONGESTION have been added in the circuit switched mea-surements category.
Old syntax: ZTPM: TRANSM, <measurement type>,...Values for measurement type: DMR, DN2, TRU/BIE, ET_BSC, ET_TCSM, TRE, TRE_SEL, PW_BSC, ETHERNET_BSC, PW_TCSM, ETHERNET_TCSM, PWT_BTS and TRE_ETHERNET.
ZTPM: MEASUR <measurement type>,...Values for measurement type: TRAFFIC, RES_AVAIL, CCCH_ACC, HO, POWER, LOAD, AVAIL, OSI, UNDEF_ADJ, RXQUAL RX, HOADJ, BSC_CC, CC_PM, UNDERL, RXLEVEL, LINKBAL, TIMING_ADV, AVAIL_BSC, CC_SERLEV, MSSPEED, DUAL, C/I_RATIO, HOTSPOT, HIGH_SPEED, CHAN_FIN, MS_CAP, DAC, FER, PBS, REV_HUNT, NBL_OFFSET, UT_HOADJ, UT_LEVEL, TOTAL_FEP, DFCA DFCA, DFCA_ASS, BSC_BSC, WPS, IBHO, CS_DTM, AMR_RXQUAL, DFCA_SAIC, SCC, AMR_PPC, AMR_SIG, and POWER_SAV.
New syntax: ZTPM: TRANSM, <measurement type>,...Values for measurement type: DMR, DN2, TRU/BIE, ET_BSC, ET_TCSM, TRE, TRE_SEL, PW_BSC, ETHERNET_BSC, PW_TCSM, ETHERNET_TCSM, PWT_BTS, TRE_ETHERNET, ABIS_DELAY, PA_BTS, PA_TRAFFIC, PA_SCTP, PA_DELAY, PA_CONGESTION, ETP_ETH_BSC, AOIP_TR_BSC, AOIP_TR_TCSM, and ETP_ETH_TCSM.
ZTPM: MEASUR <measurement type>,...Values for measurement type: TRAFFIC, RES_AVAIL, CCCH_ACC, HO, POWER, LOAD, AVAIL, OSI, UNDEF_ADJ, RXQUAL RX, HOADJ, BSC_CC, CC_PM, UNDERL, RXLEVEL, LINKBAL, TIMING_ADV, AVAIL_BSC, CC_SERLEV, MSSPEED, DUAL, C/I_RATIO, HOTSPOT, HIGH_SPEED, CHAN_FIN, MS_CAP, DAC, FER, PBS, REV_HUNT, NBL_OFFSET, UT_HOADJ, UT_LEVEL, TOTAL_FEP, DFCA DFCA, DFCA_ASS, BSC_BSC, WPS, IBHO, CS_DTM, AMR_RXQUAL, DFCA_SAIC, SCC, AMR_PPC, AMR_SIG, POWER_SAV, CSDAP, OSC_RXQUAL, and PA_CONGESTION.
204 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
The command entry continues in the same way as before after a semantic error.
Modified Command I INTERROGATE GSM MEASUREMENT
Description of changes: New measurements ABIS_DELAY, PA_BTS, PA_TRAFFIC, PA_SCTP, PA_DELAY, ETP_ETH_BSC, AOIP_TR_BSC, AOIP_TR_TCSM, ETP_ETH_TCSM have been added in the transmission measurements category. New measurements CSDAP, OSC_RXQUAL, and PA_CONGESTION have been added in the circuit switched mea-surements category.
Old syntax: ZTPI: TRANSM, <measurement type>,...Values for measurement type: DMR, DN2, TRU/BIE, ET_BSC, ET_TCSM, TRE, TRE_SEL, PW_BSC, ETHERNET_BSC, PW_TCSM, ETHERNET_TCSM, PWT_BTS and TRE_ETHERNET.
ZTPI: MEASUR <measurement type>,...Values for measurement type: TRAFFIC, RES_AVAIL, CCCH_ACC, HO, POWER, LOAD, AVAIL, OSI, UNDEF_ADJ, RXQUAL RX, HOADJ, BSC_CC, CC_PM, UNDERL, RXLEVEL, LINKBAL, TIMING_ADV, AVAIL_BSC, CC_SERLEV, MSSPEED, DUAL, C/I_RATIO, HOTSPOT, HIGH_SPEED, CHAN_FIN, MS_CAP, DAC, FER, PBS, REV_HUNT, NBL_OFFSET, UT_HOADJ, UT_LEVEL, TOTAL_FEP, DFCA DFCA, DFCA_ASS, BSC_BSC, WPS, IBHO, CS_DTM, AMR_RXQUAL, DFCA_SAIC, SCC, AMR_PPC, AMR_SIG, and POWER_SAV.
New syntax: ZTPI: TRANSM, <measurement type>,...Values for measurement type: DMR, DN2, TRU/BIE, ET_BSC, ET_TCSM, TRE, TRE_SEL, PW_BSC, ETHERNET_BSC, PW_TCSM, ETHERNET_TCSM, PWT_BTS, TRE_ETHERNET, ABIS_DELAY, PA_BTS, PA_TRAFFIC, PA_SCTP, PA_DELAY, PA_CONGESTION, ETP_ETH_BSC, AOIP_TR_BSC, AOIP_TR_TCSM, and ETP_ETH_TCSM.
ZTPI: MEASUR <measurement type>,...Values for measurement type: TRAFFIC, RES_AVAIL, CCCH_ACC, HO, POWER, LOAD, AVAIL, OSI, UNDEF_ADJ, RXQUAL RX, HOADJ, BSC_CC, CC_PM, UNDERL, RXLEVEL, LINKBAL, TIMING_ADV, AVAIL_BSC, CC_SERLEV, MSSPEED, DUAL, C/I_RATIO, HOTSPOT, HIGH_SPEED, CHAN_FIN, MS_CAP, DAC, FER, PBS, REV_HUNT, NBL_OFFSET, UT_HOADJ, UT_LEVEL, TOTAL_FEP, DFCA DFCA, DFCA_ASS, BSC_BSC, WPS, IBHO, CS_DTM, AMR_RXQUAL, DFCA_SAIC, SCC, AMR_PPC, AMR_SIG, POWER_SAV, CSDAP, OSC_RXQUAL, and PA_CONGESTION.
The command entry continues in the same way as before after a semantic error.
Modified Command S START GSM MEASUREMENT
Description of changes: New measurements ABIS_DELAY, PA_BTS, PA_TRAFFIC, PA_SCTP, PA_DELAY, ETP_ETH_BSC, AOIP_TR_BSC, AOIP_TR_TCSM, ETP_ETH_TCSM have been added in the transmission measurements category. New measurements CSDAP, OSC_RXQUAL, and PA_CONGESTION have been added in the circuit switched mea-surements category.
Old syntax: ZTPS: TRANSM, <measurement type>,...Values for measurement type: DMR, DN2, TRU/BIE, ET_BSC, ET_TCSM, TRE, TRE_SEL, PW_BSC, ETHERNET_BSC, PW_TCSM, ETHERNET_TCSM, PWT_BTS and TRE_ETHERNET.
ZTPS: MEASUR <measurement type>,...Values for measurement type: TRAFFIC, RES_AVAIL, CCCH_ACC, HO, POWER, LOAD, AVAIL, OSI, UNDEF_ADJ, RXQUAL RX, HOADJ, BSC_CC, CC_PM, UNDERL, RXLEVEL, LINKBAL, TIMING_ADV, AVAIL_BSC, CC_SERLEV, MSSPEED, DUAL, C/I_RATIO, HOTSPOT, HIGH_SPEED, CHAN_FIN, MS_CAP, DAC, FER, PBS, REV_HUNT, NBL_OFFSET, UT_HOADJ, UT_LEVEL, TOTAL_FEP, DFCA DFCA, DFCA_ASS, BSC_BSC, WPS, IBHO, CS_DTM, AMR_RXQUAL, DFCA_SAIC, SCC, AMR_PPC, AMR_SIG, and POWER_SAV.
DN0963445DN0963445 Issue 01
205
Changes in RG20(BSS)
Id:0900d8058076d679
(UB) - Single Radio Network Test Handling
New syntax: ZTPS: TRANSM, <measurement type>,...Values for measurement type: DMR, DN2, TRU/BIE, ET_BSC, ET_TCSM, TRE, TRE_SEL, PW_BSC, ETHERNET_BSC, PW_TCSM, ETHERNET_TCSM, PWT_BTS, TRE_ETHERNET, ABIS_DELAY, PA_BTS, PA_TRAFFIC, PA_SCTP, PA_DELAY, PA_CONGESTION, ETP_ETH_BSC, AOIP_TR_BSC, AOIP_TR_TCSM, and ETP_ETH_TCSM.
ZTPS: MEASUR <measurement type>,...Values for measurement type: TRAFFIC, RES_AVAIL, CCCH_ACC, HO, POWER, LOAD, AVAIL, OSI, UNDEF_ADJ, RXQUAL RX, HOADJ, BSC_CC, CC_PM, UNDERL, RXLEVEL, LINKBAL, TIMING_ADV, AVAIL_BSC, CC_SERLEV, MSSPEED, DUAL, C/I_RATIO, HOTSPOT, HIGH_SPEED, CHAN_FIN, MS_CAP, DAC, FER, PBS, REV_HUNT, NBL_OFFSET, UT_HOADJ, UT_LEVEL, TOTAL_FEP, DFCA DFCA, DFCA_ASS, BSC_BSC, WPS, IBHO, CS_DTM, AMR_RXQUAL, DFCA_SAIC, SCC, AMR_PPC, AMR_SIG, POWER_SAV, CSDAP, OSC_RXQUAL, and PA_CONGESTION.
The command entry continues in the same way as before after a semantic error.
Modified Command E STOP GSM MEASUREMENT
Description of changes: New measurements ABIS_DELAY, PA_BTS, PA_TRAFFIC, PA_SCTP, PA_DELAY, ETP_ETH_BSC, AOIP_TR_BSC, AOIP_TR_TCSM, ETP_ETH_TCSM have been added in the transmission measurements category. New measurements CSDAP, OSC_RXQUAL, and PA_CONGESTION have been added in the circuit switched mea-surements category.
Old syntax: ZTPE: TRANSM, <measurement type>,...Values for measurement type: DMR, DN2, TRU/BIE, ET_BSC, ET_TCSM, TRE, TRE_SEL, PW_BSC, ETHERNET_BSC, PW_TCSM, ETHERNET_TCSM, PWT_BTS and TRE_ETHERNET.
ZTPE: MEASUR <measurement type>,...Values for measurement type: TRAFFIC, RES_AVAIL, CCCH_ACC, HO, POWER, LOAD, AVAIL, OSI, UNDEF_ADJ, RXQUAL RX, HOADJ, BSC_CC, CC_PM, UNDERL, RXLEVEL, LINKBAL, TIMING_ADV, AVAIL_BSC, CC_SERLEV, MSSPEED, DUAL, C/I_RATIO, HOTSPOT, HIGH_SPEED, CHAN_FIN, MS_CAP, DAC, FER, PBS, REV_HUNT, NBL_OFFSET, UT_HOADJ, UT_LEVEL, TOTAL_FEP, DFCA DFCA, DFCA_ASS, BSC_BSC, WPS, IBHO, CS_DTM, AMR_RXQUAL, DFCA_SAIC, SCC, AMR_PPC, AMR_SIG, and POWER_SAV.
New syntax: ZTPE: TRANSM, <measurement type>,…Values for measurement type: DMR, DN2, TRU/BIE, ET_BSC, ET_TCSM, TRE, TRE_SEL, PW_BSC, ETHERNET_BSC, PW_TCSM, ETHERNET_TCSM, PWT_BTS, TRE_ETHERNET, ABIS_DELAY, PA_BTS, PA_TRAFFIC, PA_SCTP, PA_DELAY, PA_CONGESTION, ETP_ETH_BSC, AOIP_TR_BSC, AOIP_TR_TCSM, and ETP_ETH_TCSM
ZTPE: MEASUR <measurement type>,...Values for measurement type: TRAFFIC, RES_AVAIL, CCCH_ACC, HO, POWER, LOAD, AVAIL, OSI, UNDEF_ADJ, RXQUAL RX, HOADJ, BSC_CC, CC_PM, UNDERL, RXLEVEL, LINKBAL, TIMING_ADV, AVAIL_BSC, CC_SERLEV, MSSPEED, DUAL, C/I_RATIO, HOTSPOT, HIGH_SPEED, CHAN_FIN, MS_CAP, DAC, FER, PBS, REV_HUNT, NBL_OFFSET, UT_HOADJ, UT_LEVEL, TOTAL_FEP, DFCA DFCA, DFCA_ASS, BSC_BSC, WPS, IBHO, CS_DTM, AMR_RXQUAL, DFCA_SAIC, SCC, AMR_PPC, AMR_SIG, POWER_SAV, CSDAP, OSC_RXQUAL, and PA_CONGESTION.
The command entry continues in the same way as before after a semantic error.
Modified command(s) and menu text(s)
K HANDLE ABIS LOOP TEST
P PRINT TEST REPORT
206 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d679
Modified Command K HANDLE ABIS LOOP TEST
Description of changes: A new parameter CSDAP ID has been added.This parameter identifies the circuit switched dynamic Abis pool in a BSC. The identification number must be unique within the BSC. CSDAP ID value range is from 1 to 1000.
Old syntax: UBK: <operation> :
( BTS = <BTS number> |
NAME = <BTS name> ),
[ TRX = <TRX number> | ALL def ] :
[ <radio time slot> | ALL def ]:
[[ SEL = <select Abis connection> <option> | 0 def ] :
[ ATSL = <Abis time slot> <option> ],
[ STSL = <sub time slot> <option> | ALL def ]] :
[ <looping time> | def = <5 seconds> in FIXED test,
<3 seconds> in DYNAMIC test ]
New syntax: UBK: <operation> :
( BTS = <BTS number> |
NAME = <BTS name> ),
[ TRX = <TRX number> | ALL def ] :
[ <radio time slot> | ALL def ]:
[<CID = csdap id>| All def] :
[[ SEL = <select Abis connection> <option> | 0 def ] :
[ ATSL = <Abis time slot> <option> ],
[ STSL = <sub time slot> <option> | ALL def ]] :
[ <looping time> | def = <5 seconds> in FIXED test,
<3 seconds> in DYNAMIC test ]
Modified Command P PRINT TEST REPORT
Description of execution printout changes
Execution printout command example 4 and its test result printout have been added.
DN0963445DN0963445 Issue 01
207
Changes in RG20(BSS)
Id:0900d80580792b5b
6.1.4 Deleted MML programsNo deleted MML programs.
208 DN0963445DN0963445 Issue 01
Changes in RG20(BSS)
Id:0900d8058076d67d
Parameter changes
7 Parameter changesFor information on BSS parameter changes, see Parameter Changes document.