This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
ALCATEL 9120 Base Station Controller MaintenanceALCATEL 9120 Base Station Controller MaintenanceS1 Local maintenance principle
DefinitionsManaged objectsSBL operator commandsSBL state descriptionSBL hierarchy
S2 BSC local maintenanceTelecom and O&M SBLTransmission SBL at BSC sideLEDs and AlarmsBSC terminal descriptionBSC terminal functions Definition
S3 BSC local maintenancePlatform Hardware IdentificationBSC terminal practice and BSS software overview SBL practice Replace an RIT using the appropriate BSC task procedureAnalyse fault messages using the alarm dictionaryAnalyse the BTS software download
S4 TC G2 local maintenanceTransmission SBL at TC sideTC G2 LEDs and AlarmsTC G2 terminal descriptionTC G2 terminal functions
S5 TC G2 local maintenancePlatform Hardware IdentificationSBL practice Check the transmission equipment settingsReplace an RIT using the appropriate TC task procedureAnalyse fault messages using the alarm dictionary
0 OMC-R : supervises and controls the whole BSS0 BSC local terminal : supervises and controls BSC, TC, BTS’s, and
transmission SBL’s0 Transmission terminal : supervises and control local transmission
equipment (BSC & TC site)0 BTS local terminal : supervises and controls one BTS0 TC terminal : configuration and alarm reporting for Alcatel 9125 TC0 IMT terminal : supervises and controls the MFS
Since release B6.2 transmission SBLs are no more handled by the Transmission Terminal, but by the BSCTerminal. The Transmission Terminal is only used to configure, read transmission boards files, collect alarms, and perform tests and measurements (local use).
During this course we are going to learn how to use the BSC and the Transmission terminal.
A RIT is the lowest assembly piece such as boards, DC/DC converter.
A RIT may contain different SBL’s
Repair block
A Repair Block is the smallest number of SBL’s that must be taken out of service during board replacement to ensure that the faulty RIT is correctly repaired without endangering other SBL
S1: Local maintenance principleSBL operator commands
Maintenance operator commands
Disable : It allows to kill the functionality of an SBL
0 Purpose• Inhibit the functionality of a target SBL and filters alarms• The Wait Traffic Clear parameter introduce a delay into the command execution• The traffic may be stopped in a clean way
0 Impact• The context is lost (calls / signalling)
S1: Local maintenance principleSBL operator commands
Tests operator commands
Verify
0 Purpose• It allows to check a working SBL which behaviour is doubtful• WTC parameter is included• May be seen as the combination of Disable & Diagnostic tests & Init• Only applies to processors SBL• Stops on going calls in a clean way
0 Impact• Inhibit the functionality of a target SBL• Filters alarms• The context is lost (calls / signalling)
S1: Local maintenance principleSBL operator commands
Tests operator commands
Diagnostic tests
0 Purpose• Check before / after performing a repair action that SBL is working or not• SBL must not be in service• Only applies to processor SBL• Stops on going calls in a clean way
0 Impact• SW is downloaded and all its data are initialised
S1: Local maintenance principleSBL state description
Human operationOPR (Operator)0 The object is subject to an operator intervention0 It cannot perform its functions
Level of serviceIT (In traffic)0 The object is ready to perform all its functions0 The provided service is acceptable
FIT (Faulty in traffic)0 The object is ready to perform its functions in a degraded mode0 A non fatal error has been detected0 The provided service is acceptable
S1: Local maintenance principleSBL state description
Level of serviceFLT (Faulty out of service)0 A fatal error has been detected0 The service is unavailable0 The provided object has the capability to recover autonomously
FOS (Forced out of service)0 A fatal error has been detected0 The service is unavailable0 The provided object has not the capability to recover autonomously
UT (Under test)0 The object is being tested by automatic processes0 The service is momentary unavailable
S1: Local maintenance principleSBL state description
Inhibition due to system administrationSOS (Software out of service)0 The object can not performed its functions because a parent object is out of
service
EF (External fault)0 The object can not performed its functions because an other co-operating
item is out of service
Configuration managementNEQ (Non equipped)
WTC (Wait for traffic clear)0 This state is linked with the WTC timer parameter0 Corresponding SBL can not be selected for new transactions0 The traffic still goes on until the WTC timer expires
SBL’s identification (1)0 ACH : A channel0 ATR : A trunk0 BATTERY : battery0 BC RACK BUS : broadcast rack bus0 BC SYS BUS : broadcast system bus0 BSC : base station controller0 BSS_TEL : BSS telecom capability (all cells)0 BTS OM (*) : BTS operation and maintenance capability0 BTS TEL (*) : BTS telecom capability (one cell per sector)0 CLK GEN : clock generator0 CLK REP : clock repeater0 CONV : converter0 CPR : central processor
• * : logically associated with BTS, managed by BSC
ACH : provides a 64 kbps data path which flows between the MSC and the BSC. The channels are used as:
•PCM speech and data channels
•N7 channels.
ATR : provides a 2 Mbps link from the MSC to the BSC. The link carries up to 31 A-Channels (up to 30 PCMs, 1 N7 (optional), 1 X.25 (optional)).
BC_RACK_BUS : distributes each paging message to all boards within the required rack. The rack is determined by the destination LAC.
BC_SYS_BUS : distributes each paging message to all BCLA Rack boards
BTS_TEL : this is the radio channel management part of a given BTS. It also provides the radio signal preprocessing (Mode A) needed to support the RR session (error rate, power control, handover, timing advance, etc.).
CPR :
Layer 1:support of HDLC controller (which supports the LAPB), interface to the internal switch.
Signalling: X.25 Layers 2 and 3 protocol, OSI high layer protocol (CMISE and FTAM)
Radio Channel Management: centralised radio channel resource management, telecom supervision to control the overload procedure and handles the reset procedure (initiated by MSC or BSC).
SBL’s identification (2)0 DISC : solid state disk0 DTC : digital trunk controller0 GSL : GPRS signalling link0 N7 : number 7 signalling link0 OML (*) : operations and maintenance signalling link0 RSL (*) : radio signalling link0 RS232 : RS232 connection0 SWITCH : network switch0 TCU : Terminal control unit0 TR OM (**) : transmission operation and maintenance capability0 X25 : X25 link
• ** : logically associated with TSC, managed by BSC
DTC :
Layer 1: supports Digital Trunk Control (G703),Supports HDLC Controller (support MTP) , extracts clock information on received A-Trunks interface to the internal switch.
Radio Channel Management: receives and forwards paging commands and performs the paging group calculation, performs the SCCP mobile user function, controls intra-BSC handovers, controls the assignment of channels by the MSC, distinguishes between transparent and non-transparent messages and routes the transparent messages to the correct TCU.
GSL : Carries GPRS signalling between MFS and BSC
N7 : Carries (between BSS and MSC) the signalling information associated with the traffic channels contained in the A-Channel. The signalling is arranged according to the CCITT Recommendation Q700.
RSL : Carries through the BSC-BTS path, the routing information associated with the traffic channels contained in one BSC-BTS 2 Mbps link. The signalling is arranged according to a LAPD protocol. There is one RSL for one FU/TRX .
These SBLs are at the same level as the BSC SBL. They are reported to the OMC-R as isolated SBLs.
BSS_TEL
BSC
TCU DTC CPR
GSL ATRDISC
X25
RS232
BC_SYS_BUS
BC_RACK_BUS
SWITCH CONV BATTERY CLK-GENCLK-GEN
CLK-REP
ACHN7
LAPD
OML*
LAPD
TSL**
LAPD
RSL*
* = BTS SBLs, ** = TSC SBLs. All these SBLs are managed by the BSC. Note that the TSL is routed via the first TCUC in
each cabinet which is connected to the BIUA PBA with Q1 address 2. ACH = A-Trunk Channel ATR = A-Trunk
TCU :
Layer 1: supports proprietary interface (to FU), known as Base Station (BS) -trunks, supports HDLC controller (support of LAPD), interface to the internal switch.
Signalling: LAPD L2 signalling, radio signalling link control (towards FUs), O&M link (towards OMU), terrestrial channel management (BSC-BTS channel allocation).
Radio Channel Management: receives random access channel request on Abis interface, sends broadcast and paging messages on Abis interface, manages DCCH resources (allocation, link supervision, channel release, power control), selects outgoing SCCP routing on A-interface, taking into account the best signalling spread over N7 links, sets start time and timing advance on all channel allocations, processes measurements for handover requests, processes measurements for power control, routes transparent messages to the correct SCCP, connects BS-channel to the switch, on connection request, manages channel configuration (if modified), manages frequency hopping (if modified), handles trace-invocation.
Those explanations are valid for Telecom functions. For O&M functions please refer to BSS reference guide.
S2: BSC local maintenance Transmission SBL at BSC side
SBL’s identification
0 ABIS HWAY TP : abis highway termination point0 ATER HWAY TP : sub multiplexer highway termination point0 BSC ADAPT : base station controller adapter0 BTS ADAPT : base transceiver station adapter0 SM ADAPT : sub multiplexer adapter0 TC 16 : 16 channels transcoder function 0 TC TS : transcoder time slot (*)0 TSC : transcoder sub multiplexer controller
• (*) not seen by the BSC terminal
Abis-HWAY-TP : Provides a G703/G704 link between BSC and BTS. The multiplexing scheme depends on the BTS network topology (ring/star) and on the BTS configuration (number of FUs installed, channels rate, etc.). The mapping is produced by a configuration tool. It carries speech and data.
ATER-HWAY-TP : G703/G704 link multiplexing A-trunks (the multiplexing sheme can be either 3 or 4 A-trunks per submultiplexer highway).
BSC-ADAPT : Multiplexes BS-trunks onto an Abis highway. The number of multiplexed BS-trunks is configurable on the BSC-BTS interface at the BSC site.
BTS-ADAPT : Demultiplexes Abis channels from an Abis highway. The number of demultiplexed Abis channels is configurable on the BSC-BTS interface at the BTS site.
SM-ADAPT : Performs the multiplexing of Ater links.
TC16 : Performs the transcoding between the PSTN coding (64 kbps channel) and the GSM/DCS coding (13 kbps) for 16 channels.
Those explanations are valid for Telecom functions. For O&M functions please refer to BSS reference guide.
ON for the following errors :- reference failure- PLL out of control range- Broadcast signal failure
Note 2 : LED 4 flashing indicates one of the following :Flashing rate = 1s On / 1s OffPower on : the PBA is initialised and a time out is started to get the PLL locked on to the local oscillator.
Flashing rate = 150 ms On / 150 ms OffError after power on : the PLL locked on time out has expired and either the POOR state still exists or a reference failure has been detected. The PBA does not start the normal function and waits until the poor and / or reference failure disappears. Normally, the PBA must be repaired.
Flashing rate = 300 ms On / 300 ms OffTest mode
Flashing rate = 600 ms On / 600 ms OffThe PBA is forced to “local oscillator” by means of a plug on the backpanel.
Note 1 : LED 4 is ON for the following errors :- reference failure- PLL out of control range- Broadcast signal failure- Clock drivers disabled
Note 2 : LED 4 flashing indicates one of the following :Flashing rate = 1s On / 1s OffPower on
Flashing rate = 150 ms On / 150 ms OffError after power on : the PLL locked on time out has expired and either the POOR state still exists or a reference failure has been detected. The PBA does not start the normal function and waits until the poor and / or reference failure disappears. Normally, the PBA must be repaired.
S2: BSC local maintenance BSC terminal description
Hardware requirements (minimum)
0 Pentium 233 MHz processor0 64 Mb of RAM0 At least 100 Mb free for program and data storage0 1 3½“ floppy drive0 1 CD-ROM drive0 1 serial RS232 port0 1 X25 serial communication board (*)0 1 SVGA video adapter with1024x768pixel resolution0 1 SVGA monitor0 1 PS2 or serial mouse
• see BSC terminal user guide for board compatibility
S2: BSC local maintenance BSC terminal description
Software requirements
0 Microsoft Windows 2000 / XP operating system0 Windows BSC terminal application software0 Optional Connections for Windows software for the X.25 EICON C91 or
S2: BSC local maintenance BSC terminal description
Two kind of BSC connection : RS232 - X25RS232
X25 type 1 (EICON C91 X25 board)
There are two ways to connect on the BSC with the BSC terminal.
The first one is to use the RS232 link. This is done normally at the first step of the commissioning while the mini build is not yet loaded in the BSC. Anyway the “normal” way to connect the BSC terminal is to use the X25 connection.
This menu, the command menu is the one which is mostly used for BSC maintenance.It allows to read and change SBL states, to manage SSD content, to perform tests and to extend or reduce
Confirm the results found in previous exercise using the BSC terminal0 What kind of method are you going to use ?0 Is it possible to find the TRX number for each BTS ?0 Is it possible to find the sector number for each BTS ?
At the BSC terminal identify SBL’s0 Which kind of SBL have « BSC », « BSS », « BTS » for parents ?0 Is it possible for some SBL to have more than one parent ?0 Which ones ?
Disable a TCU SBL0 Print out the states of the offspring SBLs and the BTS_TEL 0 What do you notice ?0 Reactivate the TCU SBL0 Check that the SBLs are IT
Restart the active system CPR0 Check the LEDs states during and after the switchover0 Connect the X25 link to the new active system CPR0 Note how the LEDs react
Objective : To replace an RIT using the appropriate BSC task procedure (1)
Replace a TCUC using the task procedure0 Deactivate the SBL0 Print out the states of the SBLs supported by this RIT0 Replace the RIT0 Reactivate the SBL
Objective : To replace an RIT using the appropriate BSC task procedure (2)
Replace a DTCC using the task procedure0 Deactivate the SBL0 Print out the states of the SBLs supported by this RIT0 Replace the RIT0 Reactivate the SBL
Objective : To replace an RIT using the appropriate BSC task procedure (3)
Replace a CPRC SYS using the task procedure0 Deactivate the SBL0 Print out the states of the SBLs supported by this RIT0 Replace the RIT0 Reactivate the SBL
Objective : To replace an RIT using the appropriate BSC task procedure (4)
Replace a TSCA using the task procedure0 Deactivate the SBL0 Print out the states of the SBLs supported by this RIT0 Replace the RIT0 Reactivate the SBL
Objective : To analyse fault messages using the alarm dictionary (2)
Ask the instructor to disconnect a PCM interface on the BIE at the BTS side0 Analyse the fault messages using the alarm dictionary0 Note down the states of the LEDs
List the BTS files while the OMU is loading0 Connect the BSC terminal to the standby CPR (X25)0 Find the « BTS download status » sub menu0 Ask the instructor to reset the BTS from the OMC/R0 Note down the time it takes to load the BTS0 Print out a list of the BTS files
0 A PCM TP : A trunk link termination point0 ATER HWAY TP : sub multiplexer highway termination point0 SM ADAPT : sub multiplexer adapter0 TC ADAPT : transcoder adapter
• please refer to BSC transmission for hierarchy mapping
A-PCM-TP : G703/G704 MSC TC link which can carry speech and data channels.
ATER-HWAY-TP : G703/G704 link multiplexing A-trunks (the multiplexing scheme can be either 3 or 4 A-trunks per submultiplexer highway).
TC-ADAPT : Performs the adaptation between MSC-TIU links and TIU-SM links.
Those explanations are valid for Telecom functions. For O&M functions please refer to BSS reference guide.
S4: TC G2 local maintenance TC terminal description
Hardware & software requirementsHardware0 Pentium 233 MHz processor0 64 Mb of RAM0 Cache Memory 512 KByte0 At least 100 Mb free for program and data storage0 1 3½“ floppy drive0 1 serial RS232 port0 1 SVGA video adapter (Video RAM 4 Mbyte)0 1 SVGA monitor0 1 PS2 or serial mouse
Software0 Microsoft Windows 2000 / XP operating system
Depending on which transmission board you are connected, the service menu may change a little bit.This menu is used to perform tests, measurements, configuration and alarms collection on ATBX (TC), ASMB
Objective : To analyse fault messages using the alarm dictionary (1)
Ask the instructor to disconnect the first A-ter Mux PCM link between BSC and TC0 Analyse the fault messages using the alarm dictionary0 Note down the states of the LEDs
Objective : To analyse fault messages using the alarm dictionary (2)
Ask the instructor to disconnect the first A PCM link between TC and MSC0 Analyse the fault messages using the alarm dictionary0 Note down the states of the LEDs
In this window you can:– Connect and disconnect from the TC rack (SERIAL ⌫
CONNECT/ DISCONNECT).– View messages in hexadecimal, TLV or decoded text.– Filter messages and alarms to reduce noise.– Create a log file to consult on site or later.
With A925 transcoder, you can access all the MT120 boards by connecting to one MT120board. With EVOLIUMTM G2 transcoder, you must connect on each MT120 board individually.
Message area: Displays the messages and alarms appearing during the connection. Message input in hexadecimal decoded: Displays messages and alarms in hexadecimal, TLV or decoded text.Filter area to filter and reduce noise in the message area.
When you select SERIAL ⌫ CONNECT:The connection messages are displayed in the communication windows. The TCC window appears.The Compact TC terminal opens a monitoring window for each MT120 board.The tittle bar of each window shows the TEI (Terminal End Identifier) of each board.
– Example MT120 25 means that the TEI for that board is 25.
In this window you can:– Locate board OVERVIEW panel.– Check Ater mux and A interfaces OVERVIEW panel.– Declare BSC CONFIGURATION panel.– Download software to MT120 boards DOWNLOAD panel.– Edit site inventory SITE INFO panel.– Check fans FAN & TEMPERATURE
panel.– Supervise boards temperature FAN & TEMPERATURE.– View software inventory FILE INFO.
In TCIL bus MT120 uses a simplified LPD protocol. Consequently the MT120 addressing in TCIL use the TEI value.The TEI is derived from its physical location and is unique in a TC rack.
Using LAPD protocol between BSC and each MT120 board will be possible in future realease for software downloading.
Use this panel to:– Locate boards.– Check A-termux and A interfaces.– Enable fault indication RIGHT CLICK on a BOARD ⌫ FAULT INDICATION ⌫
ON ALL BOARD ON.– Reset /restart software RIGHT CLICK on a BOARD ⌫ RESTART or RESET.– Run a commissioning loop test RIGHT CLICK on a BOARD ⌫ COMMISSIONING.– To access to MT120 individual panel DOUBLE CLICK ON A BOARD.
Top area : indicatesThe PCMs-links connection status:
– GREEN and letter C: connection with PCM links.– RED and letter DC: no connection with PCM link.
For each MT120 board:– The A-termux connected.– BSC connected.– TSC connected that mean the BSC rack.– TEI number, Subrack and slot.– The software version.
Bottom area: displays where the MT120 boards are located in A925 transcoder for G2 this area is blank.Each MT120 board is allocated a number (TEI) and a color. The board numbered in italic-bold is the master (the board you are connected to).
The colors and the meaning are the following:– Green: the board is running correctly.– Yellow : the board presents minor problem(s).– Orange: the board presents fatal problem(s).– Red: the board need to be replaced.
If it is not on display, open the TCC tree VIEW ⌫ OVERVIEW:
The TCC TREE indicates:– On which subracks MT120 boards are located.– Under which number each board is referenced.– And depending on the color, whether each board is functioning correctly.
The colors and the meaning are the following:– Green: the board is running correctly.– Yellow : the board presents minor problem(s).– Orange: the board presents fatal problem(s).– Red : the board need to be replaced.
You can DOUBLE CLICK ON A BOARD to display its individual panel.
1.5 - Analyse MT120 board alarmsIn this window, you can:
– View alarms which are specific to the board.– Download software.– Activate software.– Define BSC and Hardware configuration.– Run a commissioning loop test.– Modify the remote inventory.– Execute the board replacement software procedure.
Top area :Displays all the alarms for the board, in their order of appearance. If MT120 board is the master board (the board you are connected to) you can also see the alarms for the rack:
– A check in the active column indicates that the problem which generated the alarms has not been solved.
– A square in the Active column indicates that the problem which generated the alarm has been solved.
Bottom area :Displays all the pending alarms.
The time stamp column does not indicate when the alarm occurred, but when the Compact TC Terminal has received it.
For a full description of alarms and how to solve the problem, refer to BSC/TC Alarm dictionary.
In this example the BSC1 is connected to two different TC (rack 1 to TC2 and rack 2 to TC3).BSC2 rack 1 is connected to TC2.The MT120 boards could be any board of the rack.The rule for qmux addressing is the following:
– 2.2.2 - Config (changeable) panelIn this window, you can:
Define BSC and hardware configuration.Execute on line configuration of the board (transmission programming).Execute the board replacement software procedure.
Top area:To define which BSC the board is in connection with and the A-termux number.
Middle area:To enable Qmux and set the DSP configuration.
Bottom area :To execute on line configuration or replace a board.
2.3 - Check Transmission ConfigurationIn this window you can:
– Define BSC and hardware configuration.– Execute on line configuration of the board (Transmission programming).– Execute the board replacement software procedure.
Top area :Check LAPD configuration.
Middle area :To read if CRC4 is enabled or not.
Bottom area :To Check transmission setting.
Predefined files are used:– A law or mu law.– A-termux mapping 3:1 or 4:1.– N7 or not.– X25 or not.
3 - Check the current Software Version on MT120 Board3.1 - File Info panelUse the configuration panel to:
– View the software inventory for each board of the rack.
3.2 - MT120 SW versions handlingThe MT120 is able to store 3 SW versions in its flash EPROM memory:
– V0 is store in factory in a protected area ( p).– V1 and V2 are stored on site by preload mechanism, in a non protected area of the flash. A
compressed (c) and a non compressed version are stored in flash memory (f). The MT120 uses VO at first installation or when V1 or V2 are corrupted. V1 is the running version and V2 is the previous version. The MT120 board uses V1 (current) after correct preload and activation, and uses V2 (previous) if V1 is corrupted.
For each MT120 SW a status is defined:– Current SW that is currently running the board.– Previous SW that used to run the board before the current SW.– Preloaded SW which has been downloaded but not yet been activated.– Fallback last remaining preloaded version of the current software.– Original Factory software that originally came with the board.
Hardware Module ReplacementReplace MT120 Board, using Replacement Command
2EXECUTE
THE MANUAL REPLACEMENT
2 Execute the Module Replacement CommandThe TC terminal uploads the configurations files (this includes the SW
version and the configurations files) in the directory c:\programfiles\Alcatel\Tcterminal\trm
Are the Configuration Filesuploaded ?
1 Connect TC terminal to any board
Replacement 1
Yes No
2 - Replace MT120 Board using the Replacement Command2.1 - Replacement
– 2.1.1 - Overview•This command is used to ease the replacement procedure; the actions of the operator are limited to the strict necessary. The only constraint is that the TC terminal must be able to retrieve the current configuration of the MT120 board to replace (this includes the SW version and the configuration parameters to run the MT120 board).
3.2 - Set up board remote inventory data–1. Open the “TCC - Site Info” window
In the TCC window, click the “Site Info” tab.The “TCC - Site Info” window shows up. SEE BEGIN
–2. Complete the site and rack/fan informationA On the bottom part of the window click the <Default> button to completethe fields with the default RI data in the “other” area of the window. B In the
“other” area complete also the following fields: SEE BEGIN–Site name: name of the site (max. 10 characters)–Rack Serial No: rack serial number–NbrFanUnitsInRack: number of fan units in the rack (max. 12)–Commissioning date: date of commissioning (YYMMDD)–First commissioning date: see NOTE (YYMMDD)
–NOTE: It is the same as commissioning date.C On the bottom of the “TCC - Site Info” window choose: Site Info text used to reload all MT120: other
–3. Update all MT120 with site and rack/fan dataA Click <Update All>B Wait for the action to complete.
–At the end of the process all the RI data can be seen in the “most used” area and all the MT120 boards are listed in the corresponding “TEI” column (no board is left in the “other” area). SEE END.
3.3 - Setup board logical data–They are 12 generic files 6 for A law and 6 for MU law.–For each coding 3 for 3:1 and 3 for 4:1 multiplexing type.–For each multiplexing type they are 3 files:
•no X25 (No X25 and N7).•X25 MSC (X25 at MSC and N7).•X25 TC (X25 at TC and N7).
–Top area: To select a SW to download.–Bottom area: To select board to:
– from which to download software.– On which to download, activate or delete software.
–With a G2 TC this area is blank.–TCC enable you to download software to one or several board at the same time.You can download software that is in your PC or on one board of he rack.–When you download SW that is in your PC, it is first preloaded onto a board, then block-loaded from that board onto the other board.–When you select the software (...) check the color of the board:
– White:the board can be selected for the download.– Green: the software is currently running the board.– Orange: the software has already been preloaded on the board. It is from that board that
the software will be block-loaded on to the other board.–During the download check the color of the boards:
– Yellow: the software is being downloaded.– Green: the software has successfully downloaded.– Red: failure in downloading.