BSC

BSC
FUNTCIONAL UNITS
& DESCRIPTIONS
SITE CREATION
PROCEDURES
CHANGE DELIVERY
PROCEDURES
TCSM
FUNTCIONAL UNITS
& DESCRIPTIONS
Company Confidential
OF TCSM
COMMISSIONING
BSC
BSC (BASE STATION CONTROLLER)
Functions of BSC:
1.Configuration and management of radio channels.
2.Allocation of traffic channels and link supervision.
3.Frequency hopping control.
4.Encryption management.
5.Paging.
6.BTS and MS power control.
7.Hand over control.
8.Interfaces to OMC,BTS and TCSM.
Management of Terrestrial Channels:

1. Allocation of traffic channels btn the BSC and BTS s.
2.Concept support for flexible channel assignments , for ex Half rate and High
Speed circuit switched data.
Management of Radio Channels:
1. Management of channel configurations, that is, how many traffic channels and signalling
channels can be used in the BSS.
2. Management of traffic channels (TCH) and stand-alone dedicated control channels
(SDCCH). This
function can be subdivided into the following tasks:
resource management
channel allocation
link supervision
channel release
power control
3. Management of broad cast control channels (BCCH) and common control channels
(CCCH). This
function can be subdivided into the following tasks:
Channel management
Random access
Access grant
Paging
Management of frequency hopping:

The BSC is charge of frequency hopping management which enables effective
use of radio resources and enhanced voice quality for GSM subscriber.
Handovers:
The freq of the mobile is changed in connection with handovers which are
executed and controlled by the BSC. Such a hand over can be one of the
following three types:
1.Intra BSC, Intra cell (both intra trx, inter trx), which means the handover takes
place with in the area controlled by the BSC and the mobile stays in the same
cell.
2. intra-BSC, inter-cell, which means that the mobile stays in the area of the BSC
but moves from one cell to another
3. inter-BSC, both outgoing and incoming, which means that the mobile moves
into the area of another BSC
Measurements and Observations:

In order to run the network effectively, that is, to minimise costs and maximise service
quality to the subscriber, you need information on the performance and service level of the
BSC and the radio network. Useful information is, for example, how much traffic different
cells carry, is there congestion on the SDCCH or TCH channels, and how many handovers
are successful and how many fail. Traffic measurements provide this information.
When you analyse the information, you can, for example, find out if the load is distributed
evenly or if there are problems in load distribution, that is, if the network has both heavily
and lightly loaded parts. If the load distribution is not even you can make changes to the
dimensioning of the network in order to balance it and to improve performance. When you
observe certain traffic characteristics over a period of time, you are able to forecast the
time when new resources or extensions must be introduced into the network.
The terms BSC, BSCE, BSCi, BSC2E/A, BSC2i and BSC3i are explained in
the table below
General
name
Product name
Explanation
BSCE
BSCE
First generation Nokia DX 200 BSC
BSCi
BSCi
High Capacity (upgraded and improved) version of the first generation Nokia
DX 200 BSC
BSC2
BSC2A
American National Standards Institute (ANSI) version of the second

generation Nokia DX 200 BSC2
BSC2E
European Telecommunications Standards Institute (ETSI) version of the

second generation Nokia DX 200 BSC2
BSC2i, ANSI
version
American National Standards Institute (ANSI) High Capacity version of the

Nokia DX 200 BSC2
BSC2i, ETSI
version
European Telecommunications Standards Institute (ETSI) High Capacity

version of the Nokia DX 200 BSC2
BSC3i, ANSI
version
American National Standards Institute (ANSI) High Capacity version of the

Nokia GSM/EDGE BSC3i
BSC3i, ETSI
version
European Telecommunications Standards Institute (ETSI) High Capacity

version of the Nokia GSM/EDGE BSC3i
BSC2i
BSC3i
Architecture of the BSC3i:

The Nokia BSC3i is based on a modular software (SW) and hardware
(HW) structure. Because there are exact specifications for the
interfaces between different modules, new functions can easily be
added without changing the architecture of the system. Thus, the
BSC3i can have a long operational lifespan and still always have upto-date functionalities.
The distributed architecture of the BSC3i is implemented by a
multiprocessor system. In a multiprocessor system the data
processing capacity is divided among several computer units, each of
which has a microcomputer of its own. Call handling capacity
depends on the number of Call Control Computer Units. The capacity
of the BSC can easily be increased by adding more Call Control
Computer Units to the BSC.
Call Control Computers:

In the BSC3i, the call control functions are executed by microcomputers,
called Call Control Computers. The Call Control Computers have an
identical Central Processing Unit (CPU), which is based on the most
suitable commercially available Intel microprocessors. The CPU board
contains a microprocessor and a local Random Access Memory (RAM).
Each Call Control Computer also contains the additional units that are
required for performing specific tasks.
All the different plug-in units of each Call Control Computer are
interconnected by a Compact PCI bus.
BSC
Functional Units of BSC:
1.OMU (Operation and maintenance unit)
2.MCMU (Marker and Cellular management unit)
3.BCSU (Base station controller signalling unit)
4.GSWB (Group switch unit)
5.ET (Exchange Terminal)
6.CLS (Clock synchronization unit)
7.PDFU (Power distribution fuse unit)
CPRJ45 : Connector panel RJ-45.
CPGO: Earth Comb panel
FTRB: Fan Tray
BCSU
Purpose: The BCSU handles those functions of the BSC which are highly dependent on
the amount of traffic. It controls the signaling and traffic on both A-interface and A-bis
interface and provide access to the GPRS core network.
BCSU is a Computer Unit ,it will have Pentium Processor.
Each BCSU handles the 110 Trx .
Redundancy: N+1.
Min no of BCSUs in BSC is 2
Max no of BCSUs in BSC is 7 (6+1 )
Plug in Units of BCSU:
1. PSC6-A (Power supply unit for cartridge)
2. AS7-B (Pre processor)
3.PCU-B (Packet Control unit for GPRS)
4.MBIF (Message bus interface)
5.CP7-10A (Central processing unit)
BCSU
One BCSU can handle traffic in a maximum of 110 transceivers (TRXs). The BCSU
is housed in a cartridge of its own. It consists of two parts, which correspond to
the A and Abis interfaces. The optional Packet Control Units (PCUs) are housed
in the same cartridge.
The A interface part of the BCSU is responsible for the following tasks:
1.performing the distributed functions of the Message Transfer Part (MTP)
and the Signalling Connection Control Part (SCCP) of SS7
2.controlling the mobile and base station signalling (Base Station
Subsystem Application Part, BSSAP)
The Abis interface part of the BCSU controls the air interface channels
associated with transceivers (TRXs) and Abis signalling channels. Every speech
circuit on the Abis interface is mapped one-to-one to a GSM-specific
speech/data channel on the air interface. The handover and power control
algorithms reside in this functional unit.
BCSU
BCSU INTERFACES :
1.GSW
2.Message bus interface
3.LAPD
4.CCS7
Message bus interface for internal Communications.
CPU will have Central processor unit and Memory modules(256mb).
Power Supply unit supplies power to that BCSU cartridge.
AS7-B plug in unit can implement a maximum of 16 CCS (Common Channel
Signalling) connections and a maximum of 64 LAPD connections.
AS7-B is connected to the GSWB via an internal 4Mbits/S PCM circuit and to
its
CPU unit via a 32 bit Compact PCI bus.
The PCU connected host CPU by DMC bus.
STRUCTURE OF THE BCSU:
The interface unit for the SS7 and the LAPD protocols are connected to the switching
network via PCM connections. Similarly redundant Ethernet interfaces from
microcomputer connect the BCSUs to the duplicated LAN switch units.
A preprocessing unit for multichannel signalling is equipped to the BCSU for both LAPD and SS7 signalling.
The SS7 interface is for the A interface. It contains a preprocessor, which is capable of handling a maximum
of four signalling channels. The regular bit rate in SS7 links is 64 kbit/s. Additionally wider 128kbit/s or
256kbit/s links can be used. The signalling terminal is semipermanently connected to the time slots used for
signalling.
The BCSU uses the LAPD Interface to supervise the 2 Mbit/s circuits (time slot 0 handling) connected to the
Bit Group Switch.
A preprocessing unit for multiprocessor signalling in the BCSU includes LAPD interfaces for signalling
towards BTSs and towards ET2s for both Abis and Ater interface directions. The bit rate of a single link can
be either 16 kbit/s, 32 kbit/s, or 64 kbit/s.
PCU:
There are two generations of Nokia PCUs. The first generation PCUs are PCU-Bs
and the second generation PCUs are PCU2-Ds in BSC3i.
In the BSC3i, there can be four logical Packet Control Units (PCUs), composed of
two physical plug-in units, per BCSU. The PCU unit performs all the data
processing tasks that are related to the (E)GPRS traffic. The main functions are
GPRS traffic radio resource management, for example connection establishment
and management, resource allocation, scheduling, data transfer, MS uplink
power control, Gb load sharing (uplink) and flow control (downlink).
The PCI mother board bus interface is used when the PCU-B is equipped in a
cartridge
with a CPU as a host.
MCMU
Purpose: The MCMU controls and supervises the GSWB and performs hunting,
connecting and releasing of switching network circuits. The range of the tasks it
handles makes up a combination of general marker functions and radio resource
management functions.
The MCMU is connected to other computer units of the exchange, OMU and BCSU
through
the message bus.
Redundancy: 2N
Interfaces: Message Bus, GSW.
Plug in Units of MCMU:
2. ESB20 (Ethernet switch for B-Series with 20 Ports)
3.SWCOP-A (Switch control processor)
MCMU
Message bus interface for internal Communications.
CPU will have Central processor unit and Memory modules(256mb).
Switch control processor control the Group switch.
ESB20 cards constitute the LAN switches for BSC.
Power Supply unit supplies power to that MCMU cartridge.
MCMU performs the control functions of switching matrix and BSC specific
management functions of radio resources.
The two ESB20 cards housed in the MCMU but these cards are independent from
MCMU equipment. The two ESB20 cards are share the power supply from MCMU
cartridge only.
The hardware of the MCMU consists of three modules: a microcomputer,

a Switch
Control Interface, and a Message Bus Interface
The marker functions of the MCMU control the Bit Group Switch. When the MCMU
performs the marker functions, it exchanges messages with other Call Control
Computers via the Message Bus (MB).
The Switch Control Interface writes the required connections into the switch
control memory and reads its contents. The switch control interface also
performs various tests on the switching network, defined by the microcomputer,
and generates the required timing signals.
The cellular management functions of the MCMU are responsible for cells and
radio channels that are controlled by the BSC. This responsibility is centralised in
the MCMU. The MCMU reserves and keeps track of the radio resources requested
by the MSC and the handover procedures of the BSC. The MCMU also manages
the
configuration of the cellular network .
The cellular management functions of the MCMU do not require any specific
hardware in addition to the standard DX200 microcomputer and a Message
Bus Interface Unit (MBIF).
One BSC3i always includes two MCMUs that are permanently connected to the
duplicated pair of the Bit Group Switches, the active MCMU to the active GSWB
and the passive MCMU to the passive GSWB.
The hardware implementation of an SWU (Integrated LAN switch unit)
contains 2 pcs of LAN switch (ESB26) plug-in units situated in both MCMU
cartridges. One LAN switch plug-in unit is dedicated for collecting user-plane
traffic from packet control units and another for collecting data from computer
units.
CLS
Purpose: The CLS generates the clock signals necessary for the BSC. The
oscillator of the CLS is normally synchronized to external source, usually an MSC
through PCM line. Up to two additional PCM inputs are provided for redundancy.
Redundancy: 2N
Two CLS units in BSC3i. One CL3TG unit contains one entire CLS unit.
Interfaces: Synchronization input.
Synchronization output.
External synchronization input.
Wired alarm interface to OMU via GSWB.
In the Plesiochronus operation mode, the frequency shift of the CL3TG is 2X10-8
With in each 24 hour period, if the temperature of environment does not vary.
No.Of synchronizations inputs: 4 from PCM lines.
CLS
ESB20
Purpose:
The LAN interfaces have two 100Mbit/S uplink connections to the IP network.
Uplink interfaces to additional LAN switch via the cabling panel for LANs and
serial interfaces (CPRJ45) in the BSC cabinet.
The integrated LAN switch provides access to the operators IP network at first
level. The LAN switch collects data from the computer and packet controller
and
sends it further to external routers and the IP network via 100Mbps uplink
connections.
One LAN switch plug in unit is dedicated to collecting user plane traffic from
packet control units and other to collecting data from computer units.
ESB20
MBIF
Purpose: The MB is the physical connection between the computer units of the
exchange. It is controlled by the message bus interface plug in units located in
every computer unit.
Redundancy: 2N (The duplicated message bus has a transfer rate of 32
Mbytes/s).
It is controlled by the message bus interface plug in units, which also acts a bidirectional interface btn the micro computer and 16bit parallel message bus.
The path of message bus through the computer units and placement of the
Power supply backup cable is shown in fig below. The figure also shows the
placement of the MB connectors and terminators on the back plane of the
cartridge as well as the power supply back cables to the MB terminators.
MBIF
A duplicated high-speed Message Bus (MB) is used for data transfer between the
OMU and the Call Control Computers of the BSC3i.
The length of each message is determined individually by a message length
parameter at the beginning of the message. The sender and the receiver of the
message are indicated in the address field of the message. The receiver can be a
single microcomputer, or it can be a group of microcomputers specified by the
broadcast address.
The hardware of the Message Bus consists of several parallel twisted pairs, which
carry the actual data and also control the information required for the message
transfer.
In the event of a failure, the hot standby Message Bus takes over the functions of
the active bus without interfering with the ongoing calls.
OMU
Purpose: The OMU acts as a interface btn the user and BSC3i and takes automatic
recovery measures on the basis of its collected fault data when its required.
The tasks of OMU can be divided into four groups:
1. Traffic control functions.
Subscriber administration, Routing administration, Traffic administration.
2.
Maintenance functions.
Supervision, Recovery, Diagnostics, Alarm output.
3. System configuration administration functions.
Exchange expansions, Introduction of new features.
4.
System management functions.
Input and Output function management, File management, System support
functions.
The OMU has dedicated storage devices, which serve as storage Ex:for the entire
system SW of the BSC as well as for the event buffer for intermediate storing of
Alarms.
The OMU receives fault indications from the BSC. It can produce local
alarm
printouts to the user or send the fault indications to Nokia NetAct. In the
event of
a fault, the OMU automatically activates appropriate recovery and
diagnostics
procedures with in the BSC. Recovery can also be activated by the
MCMU if the
OMU is lost.
The alarm interface module connects internal wired alarms to the OMU from
the BSC cartridges, power supply, air conditioning equipment, etc. This module
provides both input and output interfaces for external alarms to Nokia NetAct.
The OMU communicates with the Call Control Computers of the BSC via the
Message Bus.
The CPU controls the peripheral device interface module, which is used to
connect disk units, visual display unit, and printer to the OMU. A mirrored pair
of hard disk units, and one magneto-optical disk unit can be controlled by the
OMU.
The disk units are installed in the same OMU cartridge using dedicated plug-in
unit adapters.
The visual display unit and printer interfaces are standard asynchronous serial
interfaces complying with the ITU-T Recommendation.
OMU
Plug in Units of OMU:
2.AS7-B (Processor for LAPD and clock control channel)
3.AC25-A (Adapter for X.25 communications)
4.SERO (For serial interface)
5.HWAT-A (Hard ware alarm terminal)
8.ODPU-A+ M091 (Optical device plug in unit)
9.HDPU-A+ WDU (Hard disk plug in unit)
HWAT conveys the internal alarms to OMU and sends and receives the
external
alarms of the exchange. It performs the forced control of the change over of
GSW. HWAT contains 24 interfaces for incoming external alarms.
OMU
Plug in Units of OMU:
2.AS7-B (Processor for LAPD and clock control channel)
3.SERO (For serial interface)
4.HWAT-A (Hard ware alarm terminal)
7.ODPU-A+ M091 (Optical device plug in unit)
8.HDPU-A+ WDU (Hard disk plug in unit)
OMU
OMU
INTERFACES:
1.Message bus interface
2.GSW
3.Wired alarm interface
4.External alarm interface
5.Interface to external alarm unit (EXAU)
6.Cloc control channel
7.Serial interface (For VDU and LPT)
No redundancy for OMU.
AS7-B module is used for the network management interfaces
implemented in time slots. The X.25 connection provides via A-interface
timeslot.
It also provides an O&M interface for transcoders and transmission
equipment.
AS7-B plug in unit can implement a maximum of 16 CCS (Common Channel
Signalling)
connections and a maximum of 64 LAPD connections.
OMU
HWAT conveys the internal alarms to OMU and sends and receives the external
alarms of the exchange. It performs the forced control of the change over of
GSW. HWAT contains 24 interfaces for incoming external alarms.
The SERO-A unit is a 16 channel serial interface used to connect peripheral
Equipment. (VDU ,LPT)
Transmission rate over a serial interface is 75 to 19200 baud.
The channels of SERO-A are divided into two groups. In first group (0 to 3, 8 to
15), the signals meet V.28. While in the second group (4 to 7),the signals meet
V.28 or V.14.
SERO connected CPU by PCI bus.
The SCSI bus interface is used to connect mass memories equipped with the SCSI
interface to the micro computer units. Two identical SCSI bus interfaces available.
ET
Purpose: The ET performs the electrical synchronization and adaptation of
External PCM lines. It performs the AMI (ET2A) or HDB3(Other ET2 units)
coding
and decoding, inserts the alarm bits in the outgoing direction and
produces
PCM frame structure. All ET2E plug in units contains two separate ETs.
Redundancy: None
Plug in units:
1.ET2E-S (Exchange terminal with Euro connector, balanced E1 interface)
2.ET2E-SC (Exchange terminal with co-axial connectors, unbalanced E1
interface)
3.ET2A(Exchange terminal with RJ-45 connectors, balanced T1 interface)
Interfaces: GSWB
Control interface from a signaling unit (Via GSW)
PCM (E1/T1)
ET
In the incoming direction, the ET decodes the 2.048 Mbit/s (ETSI) or 1.544 Mbit/s
(ANSI) signal of a circuit into data signals. The decoder decodes the line code
(HDB3 in the ETSI environment, B8ZS or AMI in the ANSI environment) into binary
form. At the same time, the ET is synchronised to the bit rate of the incoming
signal.
In the outgoing direction, the ET receives a binary PCM signal from the switching
network and generates the PCM frame structure. The resulting signal is converted
into a line code (HDB3 in the ETSI environment, B8ZS or AMI in the ANSI
environment) and
transmitted further onto the 2.048 Mbit/s (ETSI) or 1.544 Mbit/s (ANSI) circuit.
The total no of plug in units in the BSC3i is 62 (32 in ET4C0, 30 in ET4C1) and the
Total no of PCMs is 124 with ET2E cards.
The total no of plug in units in the BSC3i is 62 (32 in ET4C0, 30 in ET4C1) and the
Total no of PCMs is 248 with ET4E cards.
ET
GSWB
Purpose: The duplicated group switch 256 is the switching fabric of the BSC3i.
The GSWB is housed in two identical SW1C-C cartridges, and it conveys traffic
passing through the BSC3i and switches tones to the subscribers of the exchange
and to the trunk circuits. It also establishes the needed connections to the
Signaling units and the internal data transmission channels and is responsible
for the sub multiplexing functions of the BSC3i.
The operation of the GSWB is controlled and supervised by the MCMU (SWCOP).
Redundancy: 2N
Plug in units:
1. SW64B (Switching Network, 8 Bit/s channel)
2. PSC1-S (Power supply for cartridge)
Interfaces: Switch control bus from MCMU.
GSWB PCM s to some computer units, all ETs.
GSWB
GSWB
The capacity of one SW64B 32 incoming and 32 outgoing 4.096 Mbits/s
serial
buses. Such a serial bus is referred as 4M serial bus. The capacity of one
4M serial
bus is 512 time division multiplexed 8 Kbits/S channels for one SW64B.
The size
Of entire GSWB is maximum of 128 incoming and 128 outgoing 4M serial
buses.
Peripheral devices:
The peripheral devices of the BSC3i are:
1.Hard disk units
2.Magneto-optical (MO) disk unit
3.Printer
4.Visual display unit
5.External alarm unit
Disk Units: The GSM/EDGE BSC has a duplicated system disk unit (Winchester)
and
Magneto-optical (MO) disk drive. The software can be loaded locally to the BSC by
using MO disks. The system disk units contain the operative software as well as
fallback software of the BSC and BTS software including the BTS HW database.
Traffic measurements are also stored on the system disks. All the disk drives are
connected to the OMU, which controls the system disk units.
Magneto-optical (MO) disk unit:

The GSM/EDGE BSC can have a Magneto-Optical drive which uses MO Media. The
MO drive is standard in BSC3i and optional in other BSCs. The MO drive is the
recommended solution for software backups and for other additional disk
storage, because it has very high capacity and is easy to use. In the BSC, the MO is
used for loading software locally to the BSC.
Printer (Optional):
A printer can be connected to the OMU. The interface complies with the ITU-T
Recommendation V.24. There are three V.24 interfaces and one V.11 interface
available for the printer on top of the equipment cabinet.
Visual display unit (optional):
In the BSC, a visual display unit is used as a user interface. With a VDU terminal, the
user
can perform normal operational functions with MML commands and diagnostic tests on
various units. Visual display units can be connected to the OMU in the same way as
printers by using interfaces that comply with the ITU-T Recommendation V.24.
External alarm unit (optional):

The optional external alarm unit (EXAU) provides a visual alarm of the
fault
indications of the BSC. The EXAU panel is located in the
telecommunications site
rooms, outside the network element. It is easy to install to all wall
materials.
PDFU
Purpose: The PDFU-A distributes the -48V/60V DC power from the site powersystem to the cartridges through the distribution cables. The PDFU-A also
contains the fuses for these cables, along with alarm circuits for the incoming
voltages and its own fuses.
Redundancy: 2N
Interfaces: Supply interfaces to cartridge and site power system.
wired alarm interface.
Plug in units: Power distribution fuse unit.
Each PDFU-A form an independent feeding input branch consisting of :
1.Connectors and circuit breakers for the incoming power cables
2.An integrated filter for EMF protection
3.Connectors for alarms and outgoing cables
PDFU
4.Eight fuses for outgoing distribution cables
5.Indicators for blown fuses
The circuit breakers for the incoming power cables have a 20A rating
and the
fuses for outgoing distribution cables a 10A rating.
The power feed cables from the site power system to the BSCC cabinet
are
Duplicated, with both supply lines connecting all PDFU-As (0,1,2,3) in the
BSCC
Cabinet.
PDFU
Site Creation Procedure

Steps:
1. Create the D-Channels for BCF & Trxs. (ZDSE)
2. Bring the BCF & Trxs into Wo State. (ZDTC)
3. Create BCF. (ZEFC)
4. Create BTSs. (ZEQC)
5. Trx Creations in Sectors. (ZERC)
6. Create Adjancies. (ZEAC)
7. Create power control parameters. (ZEUC)
8. Create Hand over parameters. (ZEHC)
9. Unlock Trxs. (ZERS)
10.Unlock BTSs. (ZEQS)
11.SW attachment. (ZEWA)
12. When OMU get into WO state, Unlock the site. (ZEFS)
Site Deletion Procedure

1. Lock the site. (ZEFS)
2. Lock the sectors. (ZEQS)
3. Lock the Trxs. (ZERS)
4. Delete the Trxs. (ZERD)
5. Delete the Sectors. (ZEQD)
6. Delete the BCF. (ZEFD)
7. Bring the D-channels into AD state. (ZDTC)
8. Delete the D-channels of the BCF & Trxs. (ZDSD)
TCSM
TCSM (Transcoder Submutiplexer)

Purpose: Transcoder unit to provide transcoding functions for traffic channels.
The equipment also provides sub multiplexing scheme that is used between
transcoder and BSC. These two functions together give a functional name to
the
equipment : Transcoder Submultiplexer Unit.
TCSM 2A and TCSM 2A-C are used with 1.5Mbits/S hierarchy.
TCSM 2E are used with 2.0Mbits/S hierarchy.
The position of the TCSM2 in the network in relation to the other network
elements.( Fig in next slide)
Interfaces: A interface towards to MSC.
A-Ter interface towards to BSC.
ES0,ES1 interface.
TCSM
The TCSM can be located either at the MSC or the BSC site. When located at the
MSC site, transmission capacity between the BSC and MSC is saved, because the
Signal is transmitted in up to the MSC in transcoded form.
TCSM2E units consists of four Plug in Units :
1. TRCO (Transcoder Controller).
2. TR16-S (TR-16 cards max is 14).
3. ET (Exchange Terminal).
4. PSC1-S (Power Supply Unit).
TRCO incorporates a micro computer that controls and supervises the operation
of TCSM.
The Power Supply unit supplies the +5V and -5V operating voltages to the TRCO
and TR16-S cards.
TCSM
TCSM
TR16: Transcoding and rate adaptation functions are performed by the DSPs in
the TR-16 cards. The TR-16 card is provided with 16 DSPs.
The TCSM2E have upto 7 trunk interfaces towards the MSC and 1 towards BSC.
The functions related to Line interfaces are handled by ETs.
Traffic Alternatives Offered by TCSM: The TCSM2 is supports a variety of traffic
alternatives for processing and transmitting diff types of calls.
For speech calls, Full rate (FR), Enhanced full rate(EFR), Half rate(HR) and
Adaptive-Rate submutiplexing (AMR) are provided.
For data calls, full rate and half rate sub multiplexing as well as HSCSD (High
speed circuit switched data) transmission at the rates of max. 2X FR data(HS2),
And max. 4X FR data(HS4) are available.
TCSM
TCSM
The TCSM2 and SW allow mixed allocations where diff lines of the same TCSM2
unit are programmed to handle diff types of calls. The no.of diff DSP SW s used
simultaneously on a TCSM2 unit is limited to Three. This limits the no.of diff types
Of configurations on the TCSM2 unit, because C,D,E are handled by one DSP SW
but types A,B and F require their own DSP SW.
Maximum capacity values for a one rack Configuration of TCSM2E:
1. 1680 (HR) traffic channels. (TR-16 Cards Req: 14 for 1 Cartridge)
2. 928(FR) traffic channels.
(TR-16 Cards Req: 8 for 1 Cartridge)
3. 480 (HS2) traffic channels. (TR-16 Cards Req: 4 for 1 Cartridge)

4. 240 (HS4) traffic channels. (TR-16 Cards Req: 2 for 1 Cartridge)
In practice Max capacity value is low because some time slots allocated for
through channels for EX: BSC-MSC common channel signalling reserves 1 or more
TS. BSC-NMS X.25 channel reserves 1 or more Time slots.
TCSM Alarm System Implementation
TCSM
Alarms are transferred over the O&M link from the TCSM to BSC. Current alarms
can be viewed on a local MMI terminal. For immediate understanding at a local
MMI terminal, the TRCO software assign a text string to the alarms. The BSC
assigns an identity, time stamp, alarm class, text string and physical location to
each alarm. It converts the logical information of TCSM alarms into physical
address. Alarms which indicate that traffic channels, trunks or the portions of the
Capacity or lost, cause blocking by the respective elements of BSC.
Power Distribution in TCSM:
All voltages needed by the TCSM equipment are generated by DC/DC converters,
located either in the cartridges or plug in units. They operated on a nominal voltage
Of -48V/-60V and the voltage range is -40,5,..-72.
The TCSM2 rack are provided with two feeding input branches, each consisting of one
PSA20 unit (Circuit breakers, diodes and filters) and PSFP unit (fuses). The PSA20 power
Supply adapters have two separate inputs.
The circuit breakers of PSA20 have a 20A rating and the fuses of PSFP have a 10A
rating.
TCSM COMISSIONIG PROCEDURE:

1. Check the Power supply of the cabinet and switch on the cabinet.
2. Insert all cards of TCSM.
3. For login Hyper terminal settings :
baud rate: 9600
data bits: 7
Parity: Even
Stop bits: 1
Flow control: Xon/Xoff
4. User Name:
Password:
5. Check status of all units by ZGT command.
6. Bring the TRCO card into TE state by ZUC:TE command.
TCSM
7. Run the diagnosis by ZCC: TOTAL command.
8. Bring the TCSM into WO state by ZUC: WO command.
Commissioning of TCSM is completed.
General Commands:
To check alarms by ZAI command.
To check ET modes by ZEI: ALL ( it shows ETs in CRC mode or Dblf
mode).
GENERAL COMMANDS
To Check the Site Status and BCF N0:
ZEEI :NAME=HYD001A::;
To Check the BCF:
ZEEI:BCF=20; (20 is BCF No)
To check the external alarms of the site:
ZEOL:20;
To check the alarms on ET:
ZAHO:ET,32; (32 is ET No)
To Check the ET state:
ZUSI:ET,32;
Available ET States are
1. SE NH (Separate No hardware)
2. SE OU (Separate Out of state)
3. TE (Test mode)
4. WO (Working mode)
GENERAL COMMANDS
To check the external alarm history of particular site:
ZEOH:2006-11-07,06-00-00:BCF=20:;
To check the ET alarm history of particular ET is:
ZAHP:ET,180::date,time;
To check the ET counters:
ZYMO:ET,180:;
To Check the ET mode: CRC or DBLF
ZYEI:ET,180;
To check the created packages (SW) of BSC :
ZWQO:CR:;
To check the running SW package in BSC& Functional units:
ZWQO:RUN:;
BSC
WQOO:CR::;
PACKAGES CREATED IN OMU:
SW-PACKAGE
FB050406
FB
FB_050406
SA 13.13-0
SA 13.13-0
6 CID300SX 1.9-0
SA5E802G
SA5E802G
BU
ASA_13_13_0
SA 13.13-0
SA 13.13-0
6 CID300SX 1.9-0
SA5E802G
FB150904
UT
FB_150904
SA 13.13-0
SA 13.13-0
4 CID300SX 1.9-0
SA5E600G
SA5E701C
UT
ASA_13_13_0
SA 13.13-0
SA 13.13-0
5 CID300SX 1.9-0
SA5E701C
STATUS DIRECTORY
ENVIRONMENT
PACKAGE-ID (REP-ID) DELIVERY
CD-ID
DEF ACT
BSC
WQOO:RUN:;
WORKING PACKAGES IN UNITS PAGE
MBA UNIT
NAME
STATUS PACKAGE_ID
0 OMU
SA5E802G BU
4 MCMU-0
ERROR: 10244
5 MCMU-1 SA5E802G BU
30 BCSU-0
ERROR: 10244
31 BCSU-1 SA5E802G BU
32 BCSU-2
ERROR: 10244
33 BCSU-3
ERROR: 10244
34 BCSU-4
ERROR: 10244
1
(REP-ID)
SA 13.13-0
6
DATA NOT UPDATED
SA 13.13-0
6
DATA NOT UPDATED
SA 13.13-0
6
DATA NOT UPDATED
DATA NOT UPDATED
DATA NOT UPDATED
DIAGNOSIS PROCEDURE OF UNITS IN BSC:

EX: ET DIAGONSIS.
----Diagnosis Unit get in to TE state.
STATE TRANSITION EXECUTED
UNIT = ET-35
NEW STATE = TE-EX
----Run the the diagnosis for ET unit.
UDUU:ET,35
/* IDENTIFY TEST FOR UNIT: ET-35

TEST TOTAL PLUG-IN UNITS
ET
YES ET2E_SC
OMITTED PARAMETER REFERS TO TOTAL TEST OF UNIT

UDUU:ET,35:;
DIAGNOSIS JOB ACTIVATED

UNIT = ET-35
TEST = TOTAL
*/
Result:
/* IDENTIFY UNIT WITHIN UNIT TYPE:

DECIMAL NUMBER
*/
UDHH:ET,35;
DX 200
DIAGNOSTIC REPORT HISTORY

UNIT = ET-35
REPORT-CLASS = ALL DATE = 2006-11-07 TIME = 00:00:00
DX 200 TEST_BSC
2006-11-07 14:56:18
PARTIAL DIAGNOSIS EXECUTED
ET-35
ET
DX 200
DIAGNOSTIC REPORT
TEST_BSC
TEST_BSC
2006-11-07 14:56:29
2006-11-07 14:56:19
ET-35
PARTIAL DIAGNOSIS
TOTAL
DIAGNOSTIC PROGRAM
0000
DIAGNOSIS
3999
3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK
END OF REPORT
END OF DIAGNOSTIC REPORT HISTORY
COMMAND EXECUTED
CD IMPLEMENTATION PROCEDURE:
1.Check alarms of BSC by ZAHO command.
2.Check the no of created packages in BSC. (Max no is 8)
3.If packages are max, delete the old package by ZWQD command.
4.Verify active SW package by ZWQB command.
5.Create fallback (Safe copy) by ZWKS Command.
6.Delete all the non default versions from the active package by ZIWD
command.
7.If CDtemp directory exists in the package,delete its contents by ZIWD
Command.
8.If CDtemp directory does not exist ,create by ZIWL Command.
9.Downloading CD to BSC following ways are possible:
1.Down loading from DAT
2.Down loading from MO
3.Down loading from OSS
10. Checking CD temp directory by ZDDE command. Verify all checksums are
OK.
11. CD Installation:
CD Installation during S11.5 Upgrade:
1.1 Adding the CD to existing package (Status of package must be
NW).
1.2 A Single CD can be added to S11.5 package.
1.3 Creating a new package.
1.4 Selecting new package as active.
2.Adding the CD to running package.
2.1 Adding the CD to running package by ZWNA command.
2.2 Creating a new package by ZWQC command.
2.3 Selecting the new package as active by ZWSS command.
old package BU from UT.
New package UT from BU.
CD IMPLEMENTATION PROCEDURES:
12. Checking of Package consistency :
To verify databases on disks are valid, copy database from
memory to disks
in units by following commands:
ZDBC:BSDATA
ZDBC:EQUIPM
ZDBC:OEDATA
ZDBC:ILDATA
13. Activation of new package.
Restart the OMU of BSC by MML command.
After OMU came up we need to give whole system restart by MML
command.
14. After BSC came up check the package consistency by ZWQB
command.
THANK YOU
RAJA.ASHOK
BSC 3i Commissioning Procedure:

1. Inspecting BSC3i hard ware functioning.
2. Monitoring BSC3i start up.
3. Opening first MML session in BSC3i.
4. Verifying the BSC3is SW versions.
5. Inspecting the BSC3is I/O system.
6. Inspecting MBIF in BSC3i.
7. Inspecting the BSC3i maintenance system.
8. Checking the clock equipment and HW configuration in BSC3i.
9. Inspecting the ESB switch in BSC3i.
10. Copying additional SW and setting the time zone in BSC3i.
Inspecting BSC3i hard ware functioning :

The following items are inspected in the BSC3i.
1.
2.
3.
4.
5.
6.
7.
8.
Internal Cabling
Interchangeability codes
EPROM Versions
Jumpers
DIP Switches
Flash Versions
Power supply
Peripheral equipment (VDU/LPT)
Serial no explanation: 1F 9844 0 1267

1F: Place of manfacturer, 9844: year and week of manfacturer
0:Factory Identification , 1267: Serial number .
CP710-A, Versions 2 and 4; C101180
Switch SW1 settings
Table: SW1 switch settings.

Switch
Setting
Meaning
1--12
OFF
Interchangeability code bit 3, read by software. See ICC code

settings below.
2--11
OFF

settings below.
3--10
OFF

settings below.
4--9
OFF

settings below.
5--8
OFF
Processor speedstep mode

OFF = High performance mode. Default.
6--7
OFF
Message Bus Interface (MBIF) usage

OFF = MBIF in use. Default
ON = MBIF not in use
Interchangeability code settings (SW1)

Table: Interchangeability (ICC) code settings (SW1).
ICC code
Switch setting
Switch 1-12
(MSB)
Switch 2-11
Switch 3-10
Switch 4-9
(LSB)
OFF
OFF
OFF
OFF
OFF
OFF
OFF
ON
OFF
OFF
ON
OFF
OFF
OFF
ON
ON
OFF
ON
OFF
OFF
OFF
ON
OFF
ON
OFF
ON
ON
OFF
OFF
ON
ON
ON
ON
OFF
OFF
OFF
ON
OFF
OFF
ON
ON
OFF
ON
OFF
ON
OFF
ON
ON
ON
ON
OFF
OFF
ON
ON
OFF
ON
ON
ON
ON
OFF
MBIF-B C74920
Inter chaangeability code
Ex: 1C89146 E01 (1C89146 is Identification code, E is Inter
chaangeability
Code, 01 is Version number).
Interchangeability code settings (W2)

MBIF-B
ICC
Switch (W2) settings
code
Interchangeability is coded with four bits
Switch 1
(MSB)
Switch 2
Switch 3
Switch 4
(LSB)
OFF
OFF
OFF
OFF
the table below.
OFF
OFF
OFF
ON
Note
OFF
OFF
ON
OFF
Switch 1 = MSB (the most significant bit) and

switch 4 = LSB (the least significant bit).
OFF
OFF
ON
ON
OFF = the switch is on the left; ON = the

switch is on the right.
OFF
ON
OFF
OFF
OFF
ON
OFF
ON
OFF
ON
ON
OFF
OFF
ON
ON
ON
ON
OFF
OFF
OFF
ON
OFF
OFF
ON
ON
OFF
ON
OFF
ON
OFF
ON
ON
ON
ON
OFF
OFF
ON
ON
OFF
ON
ON
ON
ON
OFF
Not
defined
ON
ON
ON
ON
using a DIP-switch W2.

Interchangeability codes are described in
Table: Interchangeability code settings of MBIF-B

(W2).
Set the Visual display units (VDU):

Table: VDU Settings in BSC3i:
Baud rate
Data bits
Stop bits
Parity
Page length
Line length
9600
7
2
Even
23
80
Table: Printer settings in BSC3i:

Baud rate
9600
Data bits
7
Stop bits
2
Parity
Even
Page length 65
Line length
80
The voltage requirements are as follows:

Table: Voltage requirements in BSC3i
EP ROM /FLASH VERSIONS
Voltage
Nominal
Tolerance
Feed voltage to DC/DC

converters
-48V or -60V
-40.5V to
-72V
Monitoring BSC3i start up:

The start-up of the whole system depends on the start-up priorities of the system's units.
A unit with higher priority is given loading permission before a unit with lower priority.
Within the system, the units are started up according to their respective priorities. For
example, all the Base Station Controller Signalling Units (BCSU) are given permission to
load simultaneously as they all have the same priority. In the case of doubled units, the
working units are given loading permission before the spare units.
The start-up order of the whole system is as follows:
1.Operation and Maintenance Unit (OMU)
2.Marker and Cellular Management Unit (MCMU)
3.Other units
Monitoring start-up of OMU in BSC3i:
RCBUGG is an extension of the service terminal software which enables the monitoring of
unit states. It is started up with a service terminal software command.
Before starting
Check that the working state of the OMU is WO-EX during the start-up of the
system.
If the state of OMU is TE or SE, the maintenance programs will be started up
in the Marker and Cellular Management Unit (MCMU) and the start-up is
monitored in the MCMU.
1.Connect the MML terminal and alarm printer
2.Connect the service terminal (Connect the service terminal to the J7 connector
of
the central processing unit (CP710-A).
3.Monitor the start up (Monitor the start-up of units with the RCBUGG extension).
4. Take the RCBUGG into use:
ZLE: U, RCBUGGGX
b) Monitor the states of the computer units:
ZUSI:COMP
5.Reset the unit (Reset the unit by pressing the reset button of the processor unit)
6.Monitor the start up of the OMU:

The first phase output indicates the start-up of the Boot Loader Program
Block (BOLERO):
DMX SYSTEM START-UP TESTS
b) Message Bus Interface (MBIF) green LEDs lit.
c) RAM tests successful:
ZERO RAM OK
d) Transmission of the RESET message successful.
RESET MESSAGE OK
e) Choosing software package in the OMU successful:
CHOOSING PACKET
f) Loading of the computer configuration table successful:
LOADING NET CONFIG...
g) Loading of the load list successful:
LOADING LOAD LIST FROM <source> .
Monitoring start-up of MCMU in BSC3i:

1. Connect the service terminal (Connect the service terminal to the J7 connector
of the central processing unit (CP710-A).
2. Reset the unit (Reset the unit by pressing the reset button of the processor unit).
3.Monitor the start up of the MCMU
a)The first phase output indicates the start-up of the Boot Loader Program Block(BOLERO):
b) The green LED in the Message Bus Interface (MBIF) is lit.
ZERO RAM OK
d) Transmission of the RESET message successful:
RESET MESSAGE OK
e) Loading of the computer configuration table successful:
f) Loading of the load list successful:
LOADING LOAD LIST FROM <source>
g) Loading of the load modules successful:
MODULE LOADING STARTS LOADING MODULES FROM <source> ALL MODULES LOADED
Monitoring start-up of BCSU in BSC3i:

1. Connect the service terminal (Connect the service terminal to the J7 connector
of the central processing unit (CP710-A).
2. Reset the unit (Reset the unit by pressing the reset button of the processor unit).
3.Monitor the start up of the BCSU.
a) The first phase output indicates the start-up of the Boot Loader ProgramBlock(BOLERO):
b) The green LED in the Message Bus Interface (MBIF) is lit.
ZERO RAM OK
d) Transmission of the RESET message successful.
RESET MESSAGE OK
e) Loading of the computer configuration table successful:
f) Loading of the load list successful:
LOADING LOAD LIST FROM <source>
g) Loading of the load modules successful:
MODULE LOADING STARTS
LOADING MODULES FROM <source>
ALL MODULES LOADED
h) Debugger software started up:

DEBUGGER READY
i) The type of the unit is clarified:
DEFINING UNIT TYPE
j) The FIZSLM is started up:
PROCESSING FAMILIES FIZ ...
k) Initialisation of work files:
INITIALIZING WORK FILES
l) The USAPRO is given permission to load:
READY - PHASE 2 FILE LOADING ACTIVATED
m) Working state of unit is WO/SP/TE/SE.
n) The FUZNLM start-up:
PROCESSING FAMILIES FUZ ...
o) Loading of first loading group:
LOADING STARTED 0009...
p) Start-up of program blocks:
PROCESSING FAMILIES...
q) Loading of a loading group:

LOADING STARTED... All remaining loading groups are loaded.
r) The USAPRO is given permission to start up program blocks:
READY - PHASE 3
s) Start-up of program blocks:
PROCESSING FAMILIES... All remaining program blocks are created andstarted.
t) Running SW package information:
RUNNING PACKAGE
u) Start-up of unit is terminated:
READY - WO or
READY - SP or
READY - TE or
READY - SE
Opening the first MML session in BSC3i :

When a system is delivered from Nokia, the user identifier of the system has been
defined
as <SYSTEM> and the password as <SYSTEM>.
These user identifier and password definitions are of general nature andthey are intended
to be used only in factory acceptance testing. The main user of the system or the system
administrator makes the actual authority definitions for the terminals and users with MML
commands.
The procedure for setting up the first session and for defining and testing the user
identifier and password is presented here. Examples are also provided.
1. Switch power on to the display terminal
The following text is displayed on the screen:
ENTER USERNAME <
2. Enter the user name system and press enter
The following text is displayed:
ENTER PASSWORD <
3. Enter the user name system and press enter

If the setting up of the session is successful, the following message is
displayed:
WELCOME TO THE DX 200 SERIES DIALOGUE MAIN LEVEL COMMAND <___>
<
4. Check that the printer interface is working properly.
Print out, for example, the states of the I/O devices:
ZISI:::,LPT0;
Verifying the BSC3i's SW version:
The purpose of this inspection is to verify the SW versions, comparing them with the
Delivery Catalogue, and making sure that the data in the modules is not corrupted.
1.Print out all SW packages (WQO).
Print out all SW packages installed on disks.
ZWQO
1.Output the packages created in the network element.

WQO:CR; or
2.Output the packages residing on disk.
WQO:EX; or
3.Output the software package running in all units
WQO:RUN;
Perform a verification (WQB).
Perform a verification for each SW package.
The display will print out on the printer during the execution of the
command
ZWQB
WQB:NAME=ANNIE:FORM=FAILED;
Check if any faults have been detected.
Expected outcome
The SW verification should be faultless and the versions should be same as those
listed in the Delivery Catalogue.
Unexpected outcome
If any faulty modules are found, replace them with new ones.
Inspecting the state of the I/O devices of BSC3i:

Display the I/O devices (ISI).
Display the I/O devices of all the units of the system.
ZISI:;
I/O DEVICE WORKING STATE AND SPARE DEVICE
SYSTEM = PALLAS UNIT = OMU
DEVICE
STATE
SPARE DEVICE DEVICE STATE TAPE STATE TAPE TYPE
FDU-00 WO-BU
-WDU-00 WO-BU
-WDU-01 WO-BU
-LPT-00
WO-ID
-LPT-01
BL-SY
-VDU-00 WO-ID
-VDU-01 SP-EX
SP
FDU = Magneto-optical disk unit

LPT = Line printer
VDU = Display unit
WDU = Winchester disk unit
VTP = Virtual Terminal
VPP = Virtual Printer Protocol
VDS = Virtual Data Storing device
A Virtual Data Storing Device (VDS) is a device for transferring data from a network
element to a post-processing system, for example, the billing centre (BC), outside a
network element.
A virtual terminal also operates as an input device. A virtual terminal is a terminal
which is
connected to a network element via a data network. Typically, the virtual terminal is a
PC
which is connected to a network element via a network.
Inspecting the mass memory devices power handling in BSC3i :

The BSC3i's mass memory devices are located in the OMU. To make the maintenance
easier it is possible to take disconnect the power and put it back on separately for the
Magneto optical (MO) driver and the Winchester Disk Units (WDU) without disturbing other
OMU activities.
Testing the MO driver power system in BSC3i:
1.Check the MO disk state (ISI).
ZISI::FDU,0;
The state of the MO driver should be WO-BU.
2. Disconnect the power.
Press the power of button on the front panel of the MO driver. After a few seconds, the red
power indicator is lit.
3. Remove the MO drive.
Now it is safe to remove the MO disk from the OMU cartridge.
4. Check the state of the alarm in the MO drive (ISI).
ZISI::FDU,0;
The MO state is BL_SY and the alarm 2692 is set.
5. Reconnect the power.
Set the MO drive into the OMU cartridge. The power reconnects automatically.
6. Check the state and the alarm in the MO drive (ISI).

After a few seconds, the state of the MO drive should be WO-BU and the
alarm 2692 should be cancelled.
Testing the power system of the WDU in BSC3i:
1. Check the state of the WDU 0 (ISI).
ZISI::WDU,0;
The WDU state should be WO-BU.
2. Disconnect the power.
Press the power of button on the front panel of the WDU. After a few
seconds, the red power indicator is lit.
3. Prevent file updates to disk (DUP).
ZDUP:OMU:NO,:;
4. Remove the WDU.
Now it is safe to remove the WDU disk from the OMU cartridge.
5. Check the state of the alarm in the WDU (ISI).
ZISI::WDU,0;
The state of the WDU is TE-ID and the alarm 2692 is set.
6. Reconnect the power.

Set the WDU 0 back into the OMU cartridge. The power is reconnected
automatically.
7. Change the state of the WDU (ZISC).
ZISC::WDU,0:WO-ID;
ZISC::WDU,0:WO-BU;
8. Resume file updates to disk (DUR).
ZDUR:OMU;
9.Check the state and the alarm of the WDU (ISI).
The state of the WDU should be WO-BU and the alarm 2692 should be
cancelled.
10.Repeat the steps 1 to 9 with the WDU 1.
Inspecting MBIF in BSC3i:

The purpose of the inspection of the message bus connections is to verify
the condition and correct installation of the message bus cables and the
condition of the plug-in units of the message bus interface (MBIF).
1.Test preparations.
Log into the OMU service terminal session with the password <SYSTEM>.
2.Execute the test.
Start the message bus test by using the command:
ZSMTAC:MB,ADD:A,B
where
MB = message bus number 0/1
ADD = the message bus addresses of the computer units to be tested
A,B = number of messages (for example 100,100).
3. Interpreting the results from the message bus test.
A sample command for starting the test for the computer units in a BSCC
cabinet, using
message bus MB-0: ZSMTAC:0,04,05,30,31,32,33,34,35,36,00:100,100
Once the test has been started, the values of the message bus counters are
displayed on the terminal as shown below:
In the example above, there is a fault in the MBIF-x card or bus of BCSU-2, and
the
TIME_OUT counter value has increased. Let the test run for at least one minute
for
both buses (0 and 1). To stop monitoring the message bus counters, press
<CTRL+C>.
Comp : The message bus address of the computer unit.

DATA_ERR:There is a difference between the transmitted and received test
message.
TIME_OUT:No response was received to a transmitted message within the
time-out period.
REC_ERR:Message reception has failed for a reason other than time-out.
LAST ERROR STATUS: The last detected error situation in the computer unit.
Inspecting the BSC3i's maintenance system:

1.Testing the alarm system of BSC3i
2.Testing the recovery from power breaks in BSC3i
3.Testing state transitions and unit diagnostics in BSC3i
4.Diagnostics of the I/O devices in BSC3i
5.Testing the spare units in BSC3i
Testing the alarm system of BSC3i :

1.Testing Wired alarms
2.Testing external alarms
Testing Wired alarms :
The purpose of the test is to ensure that the alarm files have been correctly
packaged and that the wired alarms have been correctly cabled and defined in the
database.
The following wired alarms are tested:
Cartridge power alarms
(2757 CARTRIDGE NON REDUNDANT POWER SUPPLY FAILURE)
PDFU (power distribution and fuse unit) panel alarms
(2758 POWER SUPPLY ADAPTER FAILURE)
PDFU (power distribution and fuse unit) panel alarms
(2759 POWER SUPPLY FUSE FAILURE)
FAN units alarms
(3146 FAN UNIT FAILURE)
Before the test, check that the Operation and Maintenance Unit (OMU) is in
the state WO-EX.
Steps : 1. Output the alarms.
Output the alarms with the command WAE. The command also tests all
created alarm groups. Compare the data in the lists with the configuration.
ZWAE:1A;
USED ALARMS:
2755 CARTRIDGE CLOCK FAILURE
2757 CARTRIDGE NON-REDUNDANT POWER SUPPLY FAILURE
2758 POWER SUPPLY ADAPTER FAILURE
2759 POWER SUPPLY FUSE FAILURE
3146 FAN UNIT FAILURE
2.Test the alarms:
The alarms are tested as follows:
Alarm 2757
a.Switch off the power from the computer unit cartridge PSC6_A and verify the
alarm from the alarm printer.
b.Turn the power back on and verify the cancelling of the alarm.
c.Wait until all recovery functions have been completed.
d. Repeat the same procedure for every cartridge (except OMU).
Alarm 2758
a.Switch off one switch from the PDFU and verify the alarm from the alarm printer.
b.Turn the switch on and verify the cancelling of the alarm.
c.Repeat the same procedure one by one for every switch in all PDFUs.
Alarms 2759 and 3146

a.Remove one fuse from the PDFU panel and verify the alarm 2759 from the
alarm printer.
b.When the fan unit's fuse is removed, the alarm 3146 is set and the other
fan units start to run faster.
c.Put the fuse back and verify the cancelling of the alarm.
d.Wait until all recovery functions have been completed.
e.Repeat the same procedure for every fuse one by one (except OMUs).
Testing External Alarms:
1. Output wired alarms (WAP).
2. Check external alarms (WAA).
Check that the external alarms specified in the source data have been printed out.
If there are no external alarms specified, you have to create one for testing all
external alarm inputs:
ZWAA:4000:EX:"TEST";
3. Connect alarm inputs (WAI).
Connect the alarm inputs one by one to the test alarm.
ZWAI:HWAT:OMU:<alarm input>,4000,TEST:;
Where alarm input: the input to be tested (0-9)
4. Cause the alarm.

Cause the alarm by wiring the alarm input to the ground.
The table below shows the position of external alarm pins on the
connector panel of the female D25 connector
When you wire all the alarm inputs (AEI00-AEI09) one by one, you should
receive an alarm printout concerning each alarm and the cancelling of the
alarm. In this example, the alarm number 4000 and text TEST should
appear on the alarm printer.
The polarity of the alarm input can be changed with the WAX command:
ZWAX:HWAT:OMU:<alarm input>:POL=0,TEXT=TEST:;
5.Delete the alarms.
After testing, delete the alarms you created:
Close alarm input:
ZWAD:HWAT:OMU:<alarm input>;
Remove external alarm:
ZWAR:4000;
Check the external alarms:
ZWAT;
Testing the recovery from power breaks in BSC3i

The purpose of the tests is to test the recovery of the system from different
power breaks. The system automatically disables those units which are
without power after a power break. The system starts the units in their
correct working state after the power is on again.
It is recommended that the external synchronisation is connected to the
BSC3i before the power break tests or that the ET used for synchronisation
is looped during this test. Remember to disconnect the loop immediately
after the test.
If the loop is not disconnected, the oscillators of the CLSs will drift to the end of their
control range. If the BSC3i is not getting any synchronisation, alarms 1010 and 1598
are
issued. They are cancelled automatically after the recovery actions which take
approximately 10 minutes.
1. Testing the recovery from complete power break in the system.
2.Testing power break in PDFU.
3.Testing fuse fault in supply cable.
Testing the recovery from complete power break in the system:

Steps:
Connect alarm printer and the MML terminal to the BSC.
Check that all units are in states WO-EX or SP-EX (USI, ISI).
If a unit is not in the appropriate state, change the state with the USC
command.
3. Disconnect power from the system.
4. Connect power to the system.
The system is started and it begins loading from the disks.
5. Wait until OMU starts in state WO-EX.
Monitor the alarm printer. All the starting computer units should cause a notice:
0691 AUTOMATIC RECOVERY ACTION WO-RE TO WO-EX
Doubled pre-processor units (for example, the synchronisation unit CLS)
independently
determine which unit is active and which is passive.
The following notice is displayed:
MMI SYSTEM READY
6. Start a session from an MML terminal
7. Output the working states of the units from the MML terminal..
8. Monitor the unit states (USI).

Check that every unit starts in the state it had before the power break:
ZUSI;
9. Monitor the alarm printer.
All the starting units should cause a notice (one of the following):
0691 AUTOMATIC RECOVERY ACTION WO-RE TO WO-EX
10. Print out the states (USI).
Print out the states of all the units and check that they are in the correct
working state. Use the following commands to output the working states
of the units:
ZUSI:ALL;
11. Update the date and time (DCS).
12. Check the states of WDU devices (ISI, ISC).
ZISI;
Testing power break in PDFU:
1. Connect the alarm printer and the MML terminal to the BSC.
2. Check that the units are in states WO-EX and SP-EX (USI).
3. Connect the service terminal.
To monitor the recovery functions, connect the service terminal to the MCMU.
When the power is disconnected from the OMU, the MML terminal and the alarm printer
do not function. The system, however, recovers also in this condition as the recovery
functions of the system are then handled in the active MCMU. In this case you can
monitor the recovery functions with the service terminal from the active MCMU as
follows:
Connect the service terminal to the active MCMU.
Take into use the debugger software used for testing the recovery system
ZLE:U,RCBUGGGX
Output the states of the units in a normal way as from an MML terminal (USI or
USIC)
ZUSI:COMP
4. Disconnect the power from the PDFU.
This should be done one by one so that both switches of the PDFU are switched
off at the same time.
5. Wait until all the recovery functions have been completed.
6. Check the states of WDU devices (ISI, ISC).
ZISI;
If the states are not WO, change them:
ZISC
Testing fuse fault in supply cable:

Steps
1.Connect the alarm printer and MML terminal to the BSC.
2. Check that the units are in states WO-EX and SP-EX (USI).
ZUSI;
3.Remove the fuse of the supply cable.
4.Connect the fuse.
5.Wait until the recovery measures have been completed.
6.Repeat the steps 1 to 4 for all the supply fuses.
Testing state transitions and unit diagnostics in BSC3i:

1. Connect the alarm printer and MML terminal to the BSC
2. Change the state of OMU unit from WO to TE to SE to TE (USC).
ZUSC:OMU:TE;
3. Run the diagnostics on the OMU (UDU).
ZUDU:OMU;
The diagnostics reports indicate that the unit is in working order:
4. Change the state of OMU to WO (USC).
ZUSC:OMU:WO;
Note :During the OMU restart, the MML and LPT connection is lost.
5. After the OMU recovery, change the state of the SP MCMU to TE to SE to TE (USC).
ZUSC:MCMU,<ind>:TE;
6. After the MCMU recovery, run total diagnostics (UDU).
ZUDU:MCMU,<te>;
7. Change the state of the MCMU from TE to SP (UDU).

ZUDU:MCMU,<te>:SP;
8. Change the state of the SP BCSU from SP to TE to SE to TE (USC).
ZUSC:BCSU,<ind>:TE;
9. After the BCSU recovery, run total diagnostics (UDU).
ZUDU:BCSU,<te>;
10.Change the state of the BCSU from TE to SP (USC).
ZUSC:BCSU,<ind>:SP;
11.Change the state of the WO BCSU from WO to SP (USC).
ZUSC:BCSU,<ind>:SP;
Repeat steps 8 to 11 until all BCSU units are tested.
13. Change the state of the SP CLS to TE to SE to TE (USC).
ZUSC:CLS,<ind>:TE;
14. Run total diagnostics for the CLS unit (UDU).
ZUDU:CLS,<te>;
14.Change the state of the CLS unit to SP (USC).

ZUSC:CLS,<ind>:SP;
15.Change the state of the WO CLS unit to SP (USC).
ZUSC:CLS,<ind>:SP;
Repeat steps 13 to 14.
16. Change the state of the SP MB to TE to SE to TE (USC).
ZUSC:MB,<ind>:TE;
17. Run total diagnostics for the MB (UDU).
ZUDU:MB,<te>;
18. Change the state of the MB to SP (USC).
ZUSC:MB,<ind>:SP;
19. Change the state of the WO MB unit to SP (USC).
ZUSC:MB,<ind>:SP;
Repeat steps 16 to 17.
20. Connect the ETs (WUC).
The ETs have to be connected with the WUC command before testing
21. Change the state of the ETs from SE to TE one by one (USC).
22.Run the diagnostics on the ET units (UDU, UDQ).

ZUDU:ET,<ind>;
With the UDQ command you can monitor the diagnostics being run.
23. Make a MCMU switchover (USC).
ZUSC: MCMU,<wo>:SP;
Repeat steps 2 to 19 and 21 to 23.
Diagnostics of the I/O devices in BSC3i:
1.Check the state of the I/O devices (ISI).
2.Check the state of the FDU to TE-ID (ISC).
ZISC::FDU,0:WO-ID;
ZISC::FDU,0:TE-ID;
3.Run diagnostics for the FDU (UDD).
ZUDD:OMU:FDU,0;
4.Change the FDU to the original state (ISC).

ZISC::FDU,0:WO-ID;
ZISC::FDU,0:WO-BU;
5.Repeat the steps 1 to 4 with the rest of the I/O devices.
The devices are:
LPT ... LINE PRINTER
MTU ... MAGNETIC TAPE UNIT
WDU ... WINCHESTER DISC UNIT
VDU ... VISUAL DISPLAY UNIT

BSC

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC

Uploaded by

Copyright:

Available Formats

BSC

BSC (BASE STATION CONTROLLER)

Management of Terrestrial Channels:

Management of frequency hopping:

Measurements and Observations:

First generation Nokia DX 200 BSC

American National Standards Institute (ANSI) version of the second

European Telecommunications Standards Institute (ETSI) version of the

American National Standards Institute (ANSI) High Capacity version of the

European Telecommunications Standards Institute (ETSI) High Capacity

American National Standards Institute (ANSI) High Capacity version of the

European Telecommunications Standards Institute (ETSI) High Capacity

Architecture of the BSC3i:

Call Control Computers:

STRUCTURE OF THE BCSU:

The hardware of the MCMU consists of three modules: a microcomputer,

Magneto-optical (MO) disk unit:

External alarm unit (optional):

Site Creation Procedure

Site Deletion Procedure

TCSM (Transcoder Submutiplexer)

(TR-16 Cards Req: 8 for 1 Cartridge)

3. 480 (HS2) traffic channels. (TR-16 Cards Req: 4 for 1 Cartridge)

TCSM Alarm System Implementation

TCSM COMISSIONIG PROCEDURE:

PACKAGES CREATED IN OMU:

WORKING PACKAGES IN UNITS PAGE

DIAGNOSIS PROCEDURE OF UNITS IN BSC:

/* IDENTIFY TEST FOR UNIT: ET-35

OMITTED PARAMETER REFERS TO TOTAL TEST OF UNIT

DIAGNOSIS JOB ACTIVATED

/* IDENTIFY UNIT WITHIN UNIT TYPE:

DIAGNOSTIC REPORT HISTORY

3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK

END OF DIAGNOSTIC REPORT HISTORY

BSC 3i Commissioning Procedure:

Inspecting BSC3i hard ware functioning :

Serial no explanation: 1F 9844 0 1267

CP710-A, Versions 2 and 4; C101180

Switch SW1 settings

Table: SW1 switch settings.

Interchangeability code bit 3, read by software. See ICC code

Interchangeability code bit 2, read by software. See ICC code

Interchangeability code bit 1, read by software. See ICC code

Interchangeability code bit 0, read by software. See ICC code

Processor speedstep mode

Message Bus Interface (MBIF) usage

ON = MBIF not in use

Interchangeability code settings (SW1)

Interchangeability code settings (W2)

Interchangeability is coded with four bits

the table below.

Switch 1 = MSB (the most significant bit) and

OFF = the switch is on the left; ON = the

using a DIP-switch W2.

Table: Interchangeability code settings of MBIF-B

Set the Visual display units (VDU):

Table: Printer settings in BSC3i:

The voltage requirements are as follows:

EP ROM /FLASH VERSIONS

Feed voltage to DC/DC

Monitoring BSC3i start up: