BSCe 3

BSC e3 and TCU e3
Local Maintenance
OML14 Course
Course #1596AEN
Copyright 2003Nortel Networks, All Rights Reserved

Printed in France
NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of Nortel Networks. Except as specifically
authorized in writing by Nortel Networks, the holder of this document shall keep the information contained
herein confidential and shall protect same in whole or in part from disclosure and dissemination to third
parties and use for evaluation, operation and maintenance purposes only.
You may not reproduce, represent, or download through any means, the information contained herein in any
way or in any form without prior written consent of Nortel Networks.
The following are trademarks of Nortel Networks Corporation: *NORTEL NETWORKS, the NORTEL
NETWORKS corporate logo, the NORTEL Globemark, HOW THE WORLD SHARES IDEAS, UNIFIED
NETWORKS, BSC6000. GSM is a trademark of France Telecom.
All other brand and product names are trademarks or registered trademarks of their respective holders.
PE/TRD/CN/4273
14.00/EN
April, 2003
BSC e3/TCU e3 Local Maintenance
Publication History
Date
mm/dd/yy
Version
Comments
PE/TRD/CN/4273
13.01/EN
Mars 2001
13.02/EN
July 2001
14.00/EN
April 2003
Creation
Updating of the section 7: BSC e3 and TCU e3
Troubleshooting (TML part)
Update
"Confidential information -- may not be copied or disclosed without permission".
PE/TRD/CN/4273
14.00/EN
April, 2003
ii
OML14 Course
Introduction
BSC e3 and TCU e3 Architecture
BSC e3 and TCU e3 Board Description
Thermic, Energetic and Cabling Aspects
Hardware Features and Configuration
BSC e3 and TCU e3 Startup
BSC e3 and TCU e3 Troubleshooting
BSC e3 and TCU e3 Module Replacement
Glossary
PE/TRD/CN/4273
14.00/EN
April, 2003
iii
Volume Composition
No.
Title
Reference
Version/Edition
OML14 BSC e3 and TCU e3

Local Maintenance
PE/TRD/CN/4273
14.00/EN
PE/TRD/CN/4273
14.00/EN
April, 2003
iv
Course Presentation
This course covers the BSC e3 and TCU e3 local maintenance.
It describes how to use the TML e3 equipment to troubleshoot a BSC e3/TCU
e3 on site.
It describes also fault finding and software upgrading.
Course Objectives
Upon completion of this course, you will be able to:
Describe the architecture of the BSC e3 and TCU e3.
Describe all board functions and interfaces.
Use the TML e3 equipment to interpret events coming from the BSC e3
and TCU e3 to perform tests and upgrades.
Identify, with leds and panel displays, the faulty modules and replace
them.
Prerequisites
This course is designed for people who maintain the BSS on site (Operator
Field Technicians, Supervisors).
Before attending this course, you need to have a good understanding of the
Telecommunication systems (hardware and software) or equivalent systems.
This knowledge is provided by the following course:
SY1ven: GSM System and Products Overview.
Scope
This course applies to the BSC e3 and TCU e3 V14 version.
PE/TRD/CN/4273
14.00/EN
April, 2003
v
Table of Contents
COURSE NOTES CONTENTS
PUBLICATION H ISTORY
ii
OML14 C OURSE
iii
VOLUME C OMPOSITION
iv
COURSE I NTRODUCTION
TABLE OF CONTENTS
vii
1. INTRODUCTION
1-1
GSM/GPRS/UMTS TRAINING C URRICULUM
1-2
BSS NORTEL T ECHNICAL P UBLICATIONS
1-3
CONTENTS
1-4
OBJECTIVES
1-5
2. BSC E3 AND TCU E3 FUNCTIONAL ARCHITECTURE
2-1
OBJECTIVES
2-2
CONTENTS
2-3
BSS IN THE GSM NETWORK
2-4
BSS ARCHITECTURE
2-5
BSC E3 AND TCU E3 E XTERNAL LINKS
2-6
BSC E3 AND TCU E3 MIXED SYSTEM ARCHITECTURE
2-7
BSC E3 AND TCU E3 P RESENTATION
2-8
BSC E3 A RCHITECTURE
2-9
D ESCRIPTION
2-9
FUNCTIONAL A RCHITECTURE
2-10
TCU E3 A RCHITECTURE
2-11
D ESCRIPTION
2-11
FUNCTIONAL A RCHITECTURE OF A TRANSCODING NODE
2-12
PE/TRD/CN/4273
14.00/EN
April, 2003
vi
3. BSC E3 AND TCU E3 BOARD DESCRIPTION
3-1
OBJECTIVES
3-2
CONTENTS
3-3
CONTROL NODE
3-5
ARCHITECTURE
3-6
HARDWARE MODULES
3-7
THE CN S LICES
3-8
TM F UNCTIONS
3-9
MEMORY MASS S TORAGE
3-10
OMU
3-11
ATM-SW
3-12
TMU
3-13
MINIMAL C ONFIGURATION FOR THE C N
3-14
INTERFACE N ODE
3-15
ARCHITECTURE
3-16
BOARD LAYOUT
3-17
CEM
3-18
8K-RM
3-19
ATM-RM
3-20
LSA-RC
3-21
MINIMAL C ONFIGURATION FOR THE IN
3-24
TRANSCODING NODE
3-25
ARCHITECTURE
3-26
BOARD LAYOUT
3-27
TRM
3-28
MINIMAL C ONFIGURATION FOR THE T N
3-29
PE/TRD/CN/4273
14.00/EN
April, 2003
vii
4. THERMIC, ENERGETIC AND CABLING ASPECTS.
4-1
OBJECTIVES
4-2
CONTENTS
4-3
POWER S UPPLY AND ALARMS SYSTEMS
4-4
PCIU MODULES
4-4
SIM MODULE
4-5
COOLING S YSTEM
4-6
LOCATION OF THE COOLING & F AN U NITS
4-6
COOLING & F AN U NITS
4-7
BSC E3/TCU E3 CABLING
4-8
SAI F RAME
4-8
BSC E3 O PTICAL FIBER C ABLING
4-9
PCM CABLING BETWEEN SAI & LSA-RC
4-10
PCM CABLING: CONNECTION LAS-RC/CTU
4-11
PCM CABLING: CTU CONNECTIONS
4-12
OPTIONAL HUB
4-13
48 V DC & ALARMS C ABLING
4-14
BSC E3 A LARM CABLING
4-15
TCU E3 A LARM CABLING
4-16
BSC E3/TCU E3 FUSES
4-17
5. HARDWARE FEATURES, CONFIGURATION & DIMENSIONING
5-1
OBJECTIVES
5-2
CONTENTS
5-3
HARDWARE F EATURES
5-4
MAIN C HA RACTERISTICS
5-4
FILLER MODULE
5-5
BSC E3 &TCU E3 C ONFIGURATIONS
5-6
MIN & MAX C ONFIGURATIONS
5-6
BSC E3 & TCU E3 TYPICAL CONFIGURATIONS
5-7
BSC E3 C ONFIGURATION EXAMPLES
5-8
PE/TRD/CN/4273
14.00/EN
April, 2003
viii
6. BSC E3/TCU E3 STARTUP
6-1
OBJECTIVES
6-2
CONTENTS
6-3
EQUIPMENT S TARTUP
6-4
PRINCIPLE
6-4
LED DISPLAY
6-5
BSC STARTUP AT THE OMC-R

HOT S TARTUP (MIB
6-7
BUILT)
COLD S TARTUP (MIB
6-7
NOT B UILT)
6-8
CONTROL NODE S TARTUP
6-9
MAIN P RINCIPLES
6-10
BOARD RECOVERY
6-11
SLICE RECOVERY
6-12
D EAD O FFICE RECOVERY
6-13
CN C OMPLETE S TARTUP S EQUENCE
6-14
CN S TARTUP T IMER
6-15
INTERFACE N ODE & TRANSCODING NODE STARTUP
6-17
IN S TARTUP: PRINCIPLES
6-18
IN S TARTUP: CEM/RM MODULES S TATES
6-19
TN S TARTUP
6-20
FAULT TOLERANCE
6-21
SOFTWARE
6-22
CELLGROUP CONCEPT
6.23
SWACT ON TMU FAILURE
6-24
PE/TRD/CN/4273
14.00/EN
April, 2003
ix
7. BSC E3 AND TCU E3 TROUBLESHOOTING
7-1
OBJECTIVES
7-2
CONTENTS
7-3
MAINTENANCE OVERVIEW
7-4
TML/RACE HARDWARE ARCHITECTURE
7-5
R EMOTE ACCESS EQUIPMENT
7-7
ENVIRONMENT
7-8
OVERVIEW
7-9
LOGIN W INDOW
7-10
TML E3
7-11
ENVIRONMENT
7-12
OVERVIEW
7-13
CONNECTIONS
7-14
TML E3 MAN MACHINE INTERFACE
7-15
LOGIN W INDOW
7-16
CONNECTION W INDOWS
7-17
STARTING W INDOWS
7-18
MAIN W INDOWS: INTERFACE NODE
7-19
CONFIGURATION MENU
7-20
TEST MENU (1/2)
7-21
TEST MENU (2/2)
7-22
DISK MENU (1/2)
7-23
DISK MENU (2/2)
7-24
MISCELLANEOUS MENU
7-25
VIEW MENU
7-26
PE/TRD/CN/4273
14.00/EN
April, 2003
x
8. BSC E3 & TCU E3 MODULE REPLACEMENT
8-1
OBJECTIVES
8-2
CONTENTS
8-3
SAFETY INSTRUCTIONS
8-4
EXTRACTION/INSERTION OF A M ODULE
8-5
LOCATION OF M ODULES
8-6
M ODULE R EPLACEMENT P ROCEDURE
8-8
GENERAL P RINCIPLES
8-8
OMU MODULE
8-9
PRIVATE MMS MODULE
8-10
SHARED MMS MODULE
8-11
ATM-SW MODULE
8-12
ATM-RM MODULE
8-13
TRM MODULE
8-14
TMU MODULE
8-15
CEM MODULE
8-16
8K-RM MODULE
8-17
BOARDS OF THE LSA-RC MODUL E
8-18
SIM MODULE
8-19
FAN UNIT
8-20
AIR F ILTER
8-21
9. GLOSSARY
9-1
PE/TRD/CN/4273
14.00/EN
April, 2003
xi
BSCe3 and TCUe3 Local Maintenance
BSCe3 and TCUe3 Local

Maintenance
Course #1596
The copyright of this document is the property of Nortel Networks. Without
the written consent of Nortel Networks, given by contract or otherwise, this
document must not be copied, reprinted or reproduced in any material form,
either wholly or in part, and the contents of this document, or any methods or
techniques available therefrom, must not be disclosed to any other person
whatsoever.
V14.00/EN
June 2003
Section 1
Introduction
whatsoever.
V14.00/EN
June 2003
GSM/GPRS Training Curriculum

BSS, NSS and GPRS Courses
NSS System Courses
487
900
930
931
935
937
950
951
955
970
972
974
DMS XA-CORE Maintenance

GSM Intelligent Networks
Overview
GSM DMS Overview
GSM NSS Overview
GSM HLR- PS (Provisioning
Server)
OMC- S Overview & Operation
GSM DMS Maintenance Part 1
GSM DMS Maintenance Part 2
SDM/FT Maintenance
GSM- MSC/VLR Translations
GSM HLR Service Datafill
GSM CCS7 Transl. and
Operations
3 days
2 days
3 days
2 days
5 days
10 days
2 days
10 days
5 days
5 days
Cellular Network Engine. Process

RF Basics
Cell Planning Fundamentals
Network and RF Engineering
Course
1 day
3 days
2 days
5 days
BSS Installation & Commissioning

PIC13 BSCe3 and TCUe3
Installation and
Commissioning
SY0
SY1
2 days
5 days
SYS
GSM General Overview

GSM System and Products
Overview
GSM System Overview
TL1
TL2
TL3
TL4
Telecommunications Overview
Frame Relay Overview
TCP/IP Overview
ATM Overview
2 days
1 day
2 days
1 day
3 days
3 days
BSS System Courses

ARI
BS21
NE2
NMO
Radio and Network Engineering Courses

CNE
RF0
CP1
NETRF1
GPRS Courses
System Courses
3 days
4 days
PR1
PR3
PR4
SY2
SR14.2
Advanced Radio Interface

Description
BSC 12000 and TCU
Advanced Description
BSS Optimization Parameters
Network Monitoring and
Optimization
S8000 BTS Family
Advanced Description
BSS Products Overview
BSCe3 and TCUe3 Advanced
Description
BSS Dimensioning
GSM GPRS SYSTEM RELEASE
V14
GP0
GP1
GP3
GP20
GP21
GP22
GPRS General Overview

1 day
GPRS Technical Description
3 days
SGSN Configuration and Operation
3 days
PCUSN Description and Configuration 4 days
PCUSN performance Management
2 days
PCUSN Integration and
Fault Management
3 days
GP5 OMC-D Operation
5 days
GP6 Charging Gateway Operation
1 day
GP8 SIG Operation
1 day
GP100 PCUSN Local Maintenance
4 days
3 days
2 days
3 days
2 days
2 days
2 days
2 days
2 days
2 days
BSS Operation
& Maintenance Courses
OM1/2
OM4
OM6
OM9
OM31
OM36
OML14
OMV14
BSS Operation and Maintenance 10 days

OMC-R Administration
4 days
S8000 BTS Local Maintenance
2 days
BSS Operation and Fault Handling 4 days
BSC and TCU Local Maintenance 3 days
BSC, TCU and BTS S8000
5 days
Local Maintenance
BSCe3 and TCUe3
2 days
Local Maintenance
V14 BSS Operation & Maintenance 1 day
for V12 Experts
NORTEL NETWORKS CONFIDENTIAL
The BSS and NSS training courses are split into several families according to the
different skills required to deal with GSM networks:
System: general knowledge about GSM, as well as a general view of the
different Telecom technologies.
BSS System: general knowledge of the BSS system: products, dimensioning,
optimization.
BSS Operation and Maintenance: how to operate and maintain a
telecommunication network by using the OMC-R facilities fully. It gives an indepth understanding of BSS functions and equipment.
NSS System: knowledge of the operation and maintenance of the NSS part of
the system.
Radio and Network Engineering: cell planning, BSS network topology, field
tests, data fill or BSS parameter optimization.
BSS Installation and Commissioning: how to install, cable, and run on-site tests.
GPRS: an overview of this new system and an advanced description of the new
nodes.
V14.00/EN
June 2003
UMTS Training Curriculum

UMTS Courses
System Courses
UM0
UM10
UM11
UM12
UM19
UMTS Introduction
UMTS System Description
UMTS System & Products
Description
Advanced UMTS Radio Interface
UMTS General Overview
Installation & Commissioning Courses

1 day
3 days
5 days
3 days
2 days
UM21
UM22
UM30
UM31
UMTS Radio Access Network

Description
iRNC Detailed Description
iBTS Detailed Description
Wireless Gateway Detailed
Description
Shasta GGSN Detailed
Description
2 days
2 days
2 days
2 days
1 day
Radio and Network Engineering Courses

UM40
UM41
UM42
UMTS RF Engineering
Fundamentals
UMTS Radio Network Planning
Fundamentals
UMTS Radio Network Planning
Project
iRNC Physical Installation
UM52
iBTS Outdoor Physical

1 day
Installation
iBTS Indoor Physical Installation 1 day
UM53
UM801 Practical Implementation of a

UMTS Access Network
1 day
5 days
UM100 Wireless Gateway First Line

Maintenance
UM101 Shasta GGSN First Line
Maintenance
UM640 UMTS Passport 7K & 15K
Operation
UM900 Wireless DMS Intelligent

Networks Operation and Datafill
UM930 Wireless DMS Overview
UM931 Wireless Circuit Core Network
Overview
UM950 Wireless DMS Maintenance Part 1
5 days
3 days
2 days
5 days
UM951 Wireless DMS Maintenance Part 2 10 days
Operation & Maintenance Courses
ProductCourses
UM20
Circuit Core Networks Courses
UM51
4 days
1 day
3 days
UM641 Wireless Gateway Configuration 5 days

and Troubleshooting
UM642 GGSN Configuration and
3 days
Operation
UM955 Wireless SDM-FT Maintenance

UM956 Wireless DMS XA-Core
Maintenance
UM957 SBA
2 days
3 days
UM966 UMTS01/GSM 14 Delta Release
2 days
UM970 Wireless DMS MSC /VLR

Translations
UM972 Wireless DMS HLR Services
Datafill
UM938 UMTS GPP IWF
10 days
2 days
5 days
5 days
2 days
3 days
5 days
UMTS: an overview of this new system and an advanced description of the new nodes.
V14.00/EN
June 2003
BSS Nortel Technical Publications

S4000/
S4000C 03
Indoor BTS
OMC-R
Architecture 06
and Reference
Security
OMC-R
BSS
BSS ObservationsObjects Configuration
BSS
BSS
V11/ V12
Administration Preventive Operating
Operating Parameters Counters
and Performance
O&M
and
SMS-CB & Corrective ProceduresParameters
Principles Dictionary Dictionary Faults Maintenance
User Guide Evolutions
and Help Maintenance
07
124
125
128
129
BSC 22
PE/CDC/DD/0004
CD-ROM of
GSM BSS NTPs
General
Information
e-cell
BTS 92
BSC e3
and 126
TCU e3
Whats new
BSS Product
in the
GPRS
Documen- BSS
tation OverviewBSS V12 Overview
Overview
NTP suite
Reference
Manuals
S4000
Smart 43
BTS
S2000/
S2000E 53
BTS
S8000/
S8002 63
BTS
PCUSN 91
34
36
52
User Manual
User Manual
Operations
Manuals
S4000
Outdoor 23
BTS
S2000H/L
BTS 35
32
Principles
50 TML (BSC/TCU)
51 TML (BTS)
ROT 14
TCU 16
130
39 Maintenance
00
01
88
PE/CDC/DD/0026
CD-ROM of
BSS Parameters User Guide
+
PE/CDC/DD/0083
CD-ROM of
GPRS Access Network
Parameters User Guide
Maintenance
Manuals
41 BSC Maintenance
Procedures
42 TCU Maintenance
Procedures
S2000/S2000E BTS
46 Maintenance
Procedures
BTS
47 S4000
Maintenance
Procedures
BTS
48 S8000
Maintenance
Procedures
117
H/L BTS
49 S2000
Maintenance
Procedures
BTS
84 S8002
Maintenance
Fault Number Description
Procedures
CT Tools (optional)
S2000/ S8000/ S2000H/L Advanced

BSC e3 CT1000
BSC/TCU S2000E
e-cell Maintenance PCUSN and
User
S4000 S8002
BTS
BTS Procedures
TCU e3 Manual
BTS
CT1000/
Instal .
Manual
BTS
85 S8006
Maintenance
CT7100 CT7100 Call Trace/

User
User Call Path Trace
Manual Manual Analyzer
(BSS) (NSS) User Manual
Procedures
e-cell BTS
90 Maintenance
Manual
132 BSC e3 and

101
102
103
104
105
106
131
29
38
20
121
60
TCU e3
123 BSS Network

Inventory Tool
The BSS product documentation or BSS Nortel Technical Publications comprises 53

manuals. The BSS NTPs (except optional NTPs) are available in the CD-ROM of GSM
BSS NTPs (PE/CDC/DD/0004).
Main kinds of manual:
General information
BSS Product Documentation Overview (00) is a general manual that
introduces all the manuals of BSS NTPs and includes the glossary.
BSS Overview (01) is an overview of the digital cellular network and of
its division into subsystems.
Reference manuals detail each subsystem or equipment in terms of the architecture,
hardware and software of its modules and indicate general dimensioning rules.
Maintenance manuals include both preventive and corrective maintenance and details of
the various maintenance procedure. BSS Maintenance Principles describes the
principles of maintenance and gives the list of faults.
Operating manuals
BSS Operating Principles gives the general principles of operation and
a dictionary of GSM parameters and observation counters.
BSS parameters User Guide (optional) aims at describing BSS GSM
and Nortel Networks parameters, formulae and engineering issues for
algorithm parameters; this manual is available in the CD-ROM
(PE/CDC/DD/0026).
V14.00/EN
June 2003
Contents
Introduction
BSC e3 and TCU e3 Functional Architecture
Thermic, Energetic and Cabling Aspects
Hardware Features, Configuration and Dimensioning.
BSC e3 and TCU e3 Startup
BSC e3 Troubleshooting
BSC e3 and TCU e3 Module Replacement
Annex: ATM Reminders
Glossary
V14.00/EN
June 2003
Objectives
Upon completion of this course, you will be able to:

Describe the hardware and functional architecture of the
BSC e3 and the TCU e3
Describe the boards functions and interfaces
Identify with leds the equipment status
Troubleshoot the Equipment with the TML.
V14.00/EN
June 2003
Section 2
BSC e3 and TCU e3
Functional Architecture
whatsoever.
V14.00/EN
June 2003
Objectives
After completion of this section, the students will be able

to:
Recognize the BSC e3 and TCU e3 Cabinets
Describe the internal architecture of the BSC e3 and
TCU e3
Describe the different functions handled by each
Node.
V14.00/EN
June 2003
Contents
BSS in the GSM Network

BSS Architecture
BSC e3 and TCU e3 External Links
BSC e3 and TCU e3 Presentation
BSC e3 Architecture
TCU e3 Architecture
V14.00/EN
June 2003
BSS in the GSM Network

BSS
E-Cell
BTS
MSC
TCU
A Interface
NSS
Radio
Interface
Public Telephone Network
S2000H&L
BTS
Ater Interface
OMC-R
MS
Abis Interface
OMN Interface
Sun
BSC
StorEdge A5000
S8000
Outdoor
BTS
Radio
Interface
Agprs Interface
GPRS Core Network

Internet
PCUSN
Gb Interface
S8000
Indoor
BTS
MS
10
The Base Station Subsystem includes the equipment and functions related to the
management of the connection on the radio path.
It mainly consists of one Base Station Controller (BSC), and several Base Transceiver
Stations (BTSs), linked by the Abis interface.
An equipment, the Transcoder/Rate Adapter Unit (TRAU) so called TransCoder Unit
(TCU) within Nortel Networks BSS products, is designed to reduce the number of PCM
links.
These different units are linked together through specific BSS interfaces:
each BTS is linked to the BSC by an Abis interface,
the TCUs are linked to the BSC by an Ater interface,
the A interface links the BSC/TCU pair to the MSC.
V14.00/EN
10
June 2003
BSS Architecture
PCUSN
OMC-R
Internet
OMN Interface
GPRS Core
Network
Remote
RACE client
TCP/IP
Ethernet
Agprs
BSC
e3
PSTN
TCU e3
Gb Interface
MS
Contr
ol
Node
Service
Area
Interface
BTS
Air
TCU 1
ATM
DMS
MSC/HLR
Optical
Interface
Ater
Interfac
e Node
TCU 0
Abis
Service
Area
Interface
Service
Area
Interface
11
The hardware architecture of the BSC e3 is based on 2 platforms:

The Control Node is a multi-application platform (computing and signaling) built
around an ATM -based switch (CC1 boards). It performs:
Call Processing
BSS OAM functions.
The Interface Node (as well as the TCU) is based on the Spectrum platform. It
provides dense PCM connectivity on the Abis and Ater interfaces and an
optional optical fiber interface (SONET = Synchronous Optical NETwork)
towards external equipment. It includes:
a 64 kbit/s time switch for DS0 path switching
a 8 kbit/s time switch for Voice path switching.
Maximum Capacity
The highest configuration of the BSC e3 and TCU e3 is able to handle up to 3000 Erlang
as maximum traffic load.
Note
DS0 = Digital Signal level 0 : digital signal transmitted at the nominal rate of 64 kbps
(PCM 30).
V14.00/EN
11
June 2003
BSC e3 and TCU e3 External Links

PCUSN
LAPD O
ML
LAPD R
SL
OMC-R
Ethernet
Agprs
BSC
LAPD GSL
Data
BTS
GPRS
LAPD
OML
LAPD
RSL
LAPD
GSL
TCU
MSC
LAPD
OML
SS7
Voice
Data
Ater
Abis
12
Three types of signaling are transported over the Abis Interface:

LAPD/OML related to Operation and Maintenance,
LAPD/RSL related to Radio Signaling Link,
LAPD/GSL related to GPRS Radio Signaling Link.
The BSC can be connected to the OMC-R through an Ethernet network or through the A
Interface.
Two types of signaling can be transported over the Ater Interface:
the LAPD/OML for control of the TCU transcoders by the BSC,
the SS7 going to the MSC.
Three types of GPRS signaling can be transported over the Agprs Interface:
the LAPD/OML for control of the PCUSN by the BSC,
the LAP/RSL for control of Radio Signaling Link,
the LAPD/GSL for control of GPRS Radio Signaling Link.
V14.00/EN
12
June 2003

BSC e3 and TCU e3 Mixed System Architecture
OMC-R
V14.3
X.25
TCU 2G
V12.4
(TCB2)
TCU e3
V14.3
TCU 2G
V12.4
(TCB2)
PCU SN
V14.3
Ethernet
BSC 2G
V12.4
BSC e3
V14.3
BSC e3
V14.3
BTSs
V12.4
BTSs
V12.4
BTSs
V14.3
13
The BSC e3 and TCU e3 are intended to interwork with current BSC 2G (12000), BTS
and OMC-R products.
Note that BSC e3 is able to support TCU 2G as well, but only with TCB2 boards (EFR).
The OMC-R - BSC e3 link is TCP/IP over Ethernet, instead of native X.25 for BSC 2G.
The OMC-R BSC e3 link over A/Ater Interface is not available in the V14.3 release
(V15 candidate feature).
Either TCU 2G and/or TCU e3 can be used to recover the synchronizing clock and to
carry SS7 links.
Each TCU (2G and e3) requires LAPD link to communicate with BSC e3.
V14.00/EN
13
June 2003
BSC e3 and TCU e3 Presentation
BSC e3
TCU e3
14
The BSC e3 and the TCU e3 are one-cabinet equipment, composed of two Nodes and
one Service Area Interface.
These Nodes are each housed in a sub rack comprising two shelves.
The cabinet is designed for indoor applications.
The design allows front access to the equipment.
External cabling from below or above is supported.
The Service Area Interface or SAI is installed on the left side of the cabinet:
It provides front access to the PCM cabling.
It contains the electrical equipment to interface the BSC or the TCU and the
customer cables.
The product is EMC compliant. No rack enclosure is required for this reason, as EMC
compliance is achieved at the sub rack level (Control and Interface Node).
V14.00/EN
14
June 2003
BSC e3 Architecture
1 - Description
BSC (doors closed)
Power Supplies
BSC (one door

open)
Fans
Service
Area
Interface
Control
Node
Service
Area
Interface
Control
Node
Fans
Interface
Node
Interface
Node
15
The BSC e3 is a one-cabinet equipment, composed of 3 frames:

The Control Node (one upper dual-shelf assembly located above the Interface
Node). It is ATM-based and ensures:
GSM call & signaling processing
Operation, Administration & Maintenance of the BSS.
It is connected to the Interface Node by two optical fiber cables (one for Transmission
and one for Reception) with a standard ATM interface.
The Interface Node (one lower dual shelf). It is also ATM-based and provides:
PCM connectivity (and an optional fiber interface in the future) towards
the TCU, BTS and PCU
Circuit switching functions.
The Service Area Interface is installed on the left side of the cabinet. It provides:
Front access to the PCM cabling
An interface between the BSC e3 and the customer cables.
The BSC e3 supports major GSM features, such as GPRS, the new vocoder AMR
(Adaptive Multi-Rate FR) and the new modulation scheme EDGE
V14.00/EN
15
June 2003
BSC e3 Architecture
2 - Functional Architecture
BSC e3
Control Node
OMU
TMU
TMU
TMU
ATM SW
Traffic
Traffic
Mgt
Traffic
Mgt
Mgt
OAM
Optical Interface
Interface Node
ATM RM
Ater
Interface
TCU
Abis
Interface
Switching Unit
LSA RC
CEM
8K RM
LSA RC
PCM
Interfac
e
64 kbps
8 kbps
PCM
Interfac
e
BTS
16
The Control Node is a computing and signaling platform built around an ATM Switch.
It contains the BSC processing core that handles overall BSC operations including
Interface Node operations, and enables communication with the OMC-R.
It is composed of the following three functional modules:
the ATM SW (Asynchronous Transfer Mode Switch)
the OMU (Operation and Maintenance Unit)
the TMU (Traffic Management Unit).
The Interface Node is a circuit switch platform which provides dense PCM connectivity.
It is made up of the following four major hardware modules:
the ATM -RM (Asynchronous Transfer Mode Resource Module)
the CEM (Common Equipment Module)
the 8K RM (8K subrate matrix Resource Module)
the LSA RC (Low Speed Access Resource Complex).
NB: The BSC e3 cabinet is powered by four SIMs (Shelf Interface Module).
V14.00/EN
16
June 2003
TCU e3 Architecture
1 - Description
TCU (doors closed)
Power Supplies
TCU (one door

open)
Fans
Service
Area
Interface
Transcoding
Node
Service
Area
Interface
Transcoding
Node
Fans
Transcoding
Node
Transcoding
Node
17
The TCU e3 is a one-cabinet equipment, composed of 3 frames:

Two Transcoding Nodes (one dual-shelf per transcoder node) is designed to
reduce the number of PCM links needed to convey radio speech and data
channels in the BSS. It provides:
Switching: the TCU e3 manages a multiplexer connecting the BSC and
MSC.
PCM link management: using the configuration data provided by the
BSC e3, the TCU e3 configures and monitors the PCM links on the A
and Ater interfaces.
Transcoding and rate adaptation: coding/decoding of speech frames
and rate adaptation.
TCU e3 equipment management: OAM functions: initialization, startup,
clock synchronization from A interface links, supervision, fault
management, software and configuration management.
The Service Area Interface is installed on the left side of the cabinet. It provides:
Front access to the PCM cabling
An interface between the TCU e3 and the customer cables.
The TCU supports the new vocoder AMR, allowing half-rate and enhanced voice quality
full rate communications.
V14.00/EN
17
June 2003
TCU e3 Architecture
2 - Functional Architecture of a Transcoding Node
Transcoding Node
12
TRM
2
1
TRM
S links
BSC
Ater
Interface
LSA RC
CEM
S links
S links
PCM
Interfac
e
64 kbps
LSA RC
A
Interface
MSC
PCM
Interfac
e
18
The Transcoding Node performs the following main tasks related to communication,
switching and transcoding.
The TCU e3 cabinet is made of two Transcoding nodes.
It is composed of the following three major hardware modules:
The CEM (Common Equipment Module)
The TRM (Transcoding Resource Module)
The LSA RC (Low Speed Access Resource Complex).
NB: The TCU e3 cabinet is powered by four SIMs (Shelf Interface Module).
V14.00/EN
18
June 2003
Section 3

whatsoever.
V14.00/EN
19
June 2003
Objectives
After completion of this section, the students will be able to:

Understand how each module interacts with the other
ones within the BSC e3 and TCU e3.
Know the physical characteristics of the BSC e3 and TCU
e3.
V14.00/EN
20
20
June 2003
Contents
Control Node Boards

Interface Node Boards
Transcoding Node Boards
V14.00/EN
21
21
June 2003
Control Node
V14.00/EN
22
22
June 2003
Control Node
1 - Architecture
Ethernet
Link
Passive Mirrored
OMU Shared
Disks
Private
Disk
Private Disk
OAM
ATM links
25 Mb/s
ATM Links
155 Mb/s
ATM links
25 Mb/s
ATM SW
25
Mb/s
1
1
TMU
ATM Links
155 Mb/s
ATM SW
AT
M
25 link
Mb s
/s
s
ink
M l /s
AT Mb
25
Towards
Interface Node
Active
OMU
Traffic
Mgt
TMU
Traffic
Mgt
14
TMU
Towards
Interface Node
Traffic
Mgt
23
The Control Node is the processing unit of the BSC e3. It is an ATM-based engine that
handles the following functions:
OAM
Traffic Management
Call & Signaling processing.
These main functions are performed by three sub-assemblies:
OMU = Operation and Maintenance Unit (OA&M + Disk Management)
ATM -SW = ATM Switch (Interconnection between OMUs and TMUs with
Communication Controller boards and optical connection with the Interface
Node)
TMU = Traffic Management Unit (Traffic Management + Signaling Processing).
The platform is full ATM inside: the links between the different modules inside the CN
are ATM links at 25 Mb/s, they are all redundant for safety reasons.
The Control Node is connected to the Interface Node by an optical fiber cable based on
a standard ATM interface at 155 Mb/s.
V14.00/EN
23
June 2003
Control Node
10
11
12
13
14
SIM B
14
Dual Shelf 01 Shelf

00
BSC e3
Contro
l Node
15
SIM A
TMU
13
TMU
TMU
12
TMU
TMU
11
TMU
TMU
10
TMU
MMS Private
OMU
ATM SW
Dual Shelf 01 Shelf

01
MMS Shared
Filler
ATM SW
6
Filler
OMU
5
MMS Shared
MMS Private
TMU
TMU
TMU
Filler
2
TMU
TMU
Shelf 00
Filler
TMU
Shelf 01
2 - Hardware Modules
15
24
The OMU (Operation & Maintenance Unit) controls all the BSC e3 elements
(both Control and Interface Nodes) and TCU e3 elements, is responsible for
Operation, Administration and Maintenance (OA&M) of the BSS, deals with disk
management, and ensures Ethernet access to the OMC-R and TML.
The MMS (Mass Memory Storage) are the 4 storage disks (2 private disks for
OMUs and 2 shared disks; one of these shared disk only is mandatory). If the
private MMS is in default state, the whole BSC e3 is in Exposure state.
The ATM SW is the ATM switch that provides the interconnexion between the
OMU and the TMU modules. It also provides connectivity with the Interface
Node through an OC-3c link.
The TMU (Traffic Management Unit) is in charge of GSM traffic and signaling
processing (LAPD and SS7).
The SIM (Shelf Interface Module) is the power supply for both shelves and the
alarm interface between the dual-shelf and the PCIU. It provides 48 V dc to
the Control Node. For redundancy purposes, there are 2 SIMs per equipment:
each SIM contributes to supply each shelf (at 50% level).
Filler Boards are empty containers which occupy any unused slots to ensure
EMC shielding.
Duplication schemes:
1 + 1 redundancy = 1 active element + 1 passive (or active) element.
N + P redundancy = N active elements to provide the targeted performance. P means
that P boards can be in default state, without loosing any established communication.
V14.00/EN
24
June 2003
Control Node
3 - The CN Slices
1
3
Generic Module View
Common Architecture inside each CN module
The CN Slices:
OMU
MMS
ATM-SW
TMU
25
A slice is the name given to a set of boards plugged into a slot on a shelf.
The Control Node is composed of the following slices:
OMU, MMS, TMU and ATM -SW
Plus SIM and Fillers.
The OMU, TMU and ATM -SW slices have a common hardware architecture and are
divided into 3 parts:
A Single Board Computer board (SBC) = Computer Board.
A PCI Mezzanine Card (PMC) = Front Panel Board.
A Transition Module board (TM) = Interface Adapter Board.
To identify each part of the slice, suffixes have been added to the board names:
xxx SBC
Single Board Computer
xxx TM
Transition Module
xxx PMC
PCI Mezzanine Card
Each module has two visual indicators on the top of the front panel, which indicate its
status:
A red LED with a triangular shape,
A green LED with a rectangular shape.
V14.00/EN
25
June 2003
Control Node
4 - TM Functions
MAIN FUNCTION: ATM ADAPTATION
TMU
VME & SCBus
to
ATM
conversion
OMU
VME
Interface with
SBC
+
ATM 25
Interface
with ATM-SW.
ATM-SW
SBC
Interface
with CN
backplane
+
OC-3c
Optical
Interface
26
The TM (Transition Module) is mainly an ATM Adapter.

All communication between modules on the ATM subsystem uses ATM Adaptation
Layer (AAL) protocols.
The TM is responsible for:
Adapting the VME-64 Bus to ATM variable bit-rate:
IP packets carrying internal BSC communications are translated over
ATM using the AAL5 protocol.
AAL5 is routed by the CPU to / from the SBC board via a VME bus.
The TM carries traffic between each module inside the CN and the IN.
Adapting the SC-Bus to the ATM constant bit-rate:
LAPD & SS7 links carried on PCM TS (DS0) are translated over ATM
using the AAL1 protocol.
AAL1 is routed to / from the PMC board via an SC-Bus.
It carries messages between the BSC and MSC and OAM information
for the entire BSS.
Board Location: in the OMU, TMU and ATM -SW modules.
V14.00/EN
26
June 2003
Control Node
5 - Memory Mass Storage
Front
Panel
SCSI -bus
Always available
View
Mirrored Shared Disks
When OMU 1 active

When OMU 2 active
BSS
OMU 1
OMU 2
Spare
OMU
Ethernet Link
Removal
Request Push
Button
Active
OMU
O.S.
O.S.
BSS
Private Disk
For OMU 1
Private Disk
For OMU 2
Mirrored Shared Disks

MMS MAIN FUNCTION: DATA STORAGE
27
The MMS (Memory Mass Storage) modules are SCSI 9 Gbytes Hard Disks in the
Control Node.
These 4 MMS are linked to the OMU modules through 4 SCSI-buses.
They are split as follows:
Two mirrored shared hard disks for both OMU modules. They contain the data
that must be secured and still be accessible in the event of an OMU failure or a
disk failure (BSS data).
Two private disks (one for each OMU). These disks hold all the private data for
the module (Operating System data).
External Interfaces on the Front Panel:
Two LEDs,
One removal request push button
Redundancy scheme: 1 + 1 operating simultaneously for the mirrored shared disks.
Board Location: Dual Shelf 01, Shelf 00, slots 5 & 6 & 9 & 10.
LED Status:
V14.00/EN
Red LED
Green LED
Status
Unlit
Lit
Disk operational
and Updated
27
June 2003
Control Node
6 - OMU
2 MMS
OMC-R
Shared
OMU Module
Ethernet Link
Disk Management
MMS
Private
VME
OMU
Boar
d
TM
TML
RJ45
Board
SCSI
Buses
D-sub 9-pins
For RS 232 debug
RS 232 Debug Bus
Unused
MMS
n
tio
Private
lica
p
u
rD
Fo
Etherne
t link
with
OMU
ATM 25
link
with
ATM-SW
Removal
Request
Push -button
MTM Bus
(Board Reset and
LED commands)
BACKPLANE
Front
Panel
OMU MAIN FUNCTION: MANAGEMENT OF ALL THE BSC

RESOURCES
View
28
The OMU (Operation and Maintenance Unit) manages all the BSC resources.
It does the following:
Disk management (Private and Shared MMS; private disk duplication),
Interface with the OMC-R or TML through an Ethernet access.
System maintenance (by using the TML) and OAM of the BSS.
Two LEDs,
One RJ45 connector for one 10/100 base T Ethernet OMC-R + TML port,
One 9-pin D-sub connector for the RS 232 debug port,
One removal request push button (shut down and SWACT of the OMU)
Redundancy scheme: 1 + 1 Hot Stand-by.
Board Location: Dual Shelf 01, Shelf 01, slots 5+6 & 9+10.
LED Status:
Red-TM
LED
ATM layers: OMU
board.
Green LED
Status
Lit
Module active
and Unlocked
Base Operating System: AIX
Unlit
V14.00/EN
28
June 2003
Control Node
OMU
7 - ATM SWitch
Activ
e
OMU
ATM SWitch
Utopia Bus
BACKPLAN
E
6 x ATM 25
Optical
Interface
ATM SW
ATM 155 Int.
OAM
3x ATM 25
Interface
OC-3 Link
ATM 155 Mb/s
TX OC-3c
Connecto
r
To RX
on the IN
Towards / From
ATM-RM
Interface Node
RX OC -3c
Connecto
r
From TX
On the IN
TMU
Front
Traffic
Mgt
Panel
ATM-SW MAIN FUNCTION: BOARDS INTERCONNEXION
View
29
The ATM SW (ATM Switch) provides a backplane board interconnection with live
insertion capabilities.
It provides:
interconnection between the OMU and TMU modules,
ATM switching, adaptation and interface on an OC-3 optical multimode fiber
towards the Interface Node. The TX connector on the ATM-SW is linked to the
ATM -RM RX connector; the RX connector on the ATM -SW is linked to the ATMRM TX connector.
Two LEDs,
1 TX OC-3 (upper) + 1 RX OC-3 (lower) optical connectors
Redundancy Scheme: 1+ 1 simultaneous work
Board Location: Dual Shelf 01, Shelf 01, slot 7 & 8.
LED Status:
Red LED
Green LED
Status
Lit
Module active
and Unlocked
Base Operating System: Vx Works
Unlit
V14.00/EN
29
June 2003
Control Node
8 - TMU
TMU Module
VME
Board
ATM 25
link
with
ATM-SW
TMU
SCSI Buses
+ VME Buses
TM
Board
VME
link
with
OMU
BACKPLANE
Front
Panel
View
30
The TMU (Traffic Management Unit) manages traffic. It is equivalent to a set of three
boards in the 2G release (SICD + CCS7 + BIFP).
It is in charge of:
GSM & GPRS traffic management,
GSM signaling processing (LAPD & SS7)
GPRS signaling processing
BTS OAM (software downloading, BTS configuration).
Two LEDs
Redundancy Scheme: N + P load sharing.
Board Location: Dual Shelf 01, Shelves 00 & 01, slots 1 & 3 & 4 & 11 to 14.
LED Status:
Red LED
Base Operating System:
Unlit Vx Works
Green LED
Status
Lit
Module active
and Unlocked
ATM layers: TMU TM board.

Note: Each TMU provides: 62 LAPD links + 2 SS7 links.
V14.00/EN
30
June 2003
Control Node
9 - Minimal Configuration for the CN
1 OMU
The corresponding Private MMS
1 shared MMS
1 ATM-SW (+ the corresponding ATM-RM in the IN)
n TMUs (according to the traffic load)
1 SIM
V14.00/EN
31
31
June 2003
Interface Node
V14.00/EN
32
32
June 2003
Interface Node
1 - Architecture
ATM RM
TOWARDS CN
S links
Switching Unit
CEM
64 kbps
Abis
TOWARDS
BTS
Ater
LSA RC
LSA RC
S links
S links
PCM
Interface
PCM
Interface
TOWARDS
TCU
8K RM
8 kbps
33
The Interface Node is based on the Nortel Networks SPECTRUM platform.

The Interface Node provides:
Network connectivity on the Abis & Ater interfaces.
Communications with the Control Node.
16 kbps or 8 kbps circuit switching for the bearer speech / data channels
between the BTSs and the MSC via the TCU e3.
It shares some major hardware modules with the Transcoding Node, such as the CEM
and LSA-RC boards.
V14.00/EN
33
June 2003
Interface Node
Dual Shelf 00 Shelf

01
Dual Shelf 00 Shelf
00
10
12
13
11
12
13
14
15
14
15
SIM
11
SIM
LSA RC
N3
LSA RC
N2
Filler
7
10
Filler
LSA RC
N5
BSC e3
Interfac
e Node
LSA RC
N4
Filler
8K-RM
8K-RM
CEM
CEM
LSA RC
N 0
ATM RM
ATM RM
LSA RC
N1
Filler
1
SHELF 00
SHELF 01
2 - Board Layout
Synchronizatio
n
34
The Interface Node is the connectivity component of the BSC e3, after the SAI.
It is responsible for:
establishing all the connections between the BSC and the other entities of the
network
supervising the physical links.
The Interface Node is divided into the following hardware modules:
The CEM (Common Equipment Module), which controls the resource modules
of the IN, provides system maintenance, clock synchronization and traffic
switching.
The ATM RM (ATM - Resource Module), which adapts Time Slots (DS0) based
voice and data channels of S-links to ATM cells for transmission over a
Synchronous Optical NETwork (SONET), OC-3c interface,
The 8K RM (8K subrate matrix Resource Module), which adds subrate
switching capability to the IN, as the CEM is only capable of switching at a TS
(DS0) level (64 kbps).
The LSA RC (Low Speed Access Resource Complex), which is the PCM
interface module, used to interface the BSC to both the TCU and BTS, providing
modularity (up to 21 E1 or 28 T1 links). Each LSA-RC block consists of 3
boards. They must be inserted in ordered steps.
the Interface Node. For redundancy purposes, there are 2 SIMs per equipment:
each SIM contributes to supply each shelf (at 50% level).
V14.00/EN
34
June 2003
Interface Node
3 - CEM
Front
Panel
ATM RM
LSA RC
PCM
Interface
3 S-links
3 S-links
View
Caution: only
rescue way of
connection
TML
Switching
Unit
Unused
CEM
Ethernet
link
RJ45
9 S-links
Clock
Synchronization
Alarms
processing
OAM
Interface
SWITCHING
CEM MAIN FUNCTION: MASTER BOARD FOR THE

IN
35
The CEM (Common Equipment Module) is the master board of the Interface Node.
It provides the following features:
64K Traffic Switching Matrix,
OA&M interface,
Control of the Resource Modules (8K RM, ATM -RM and LSA RC),
Clock synchronization,
Alarm processing,
Two LEDs,
RJ45 connector (Ethernet Link) for TML ( rescue connection only)
4 unused connectors.
Redundancy scheme: 1 + 1 Hot Stand-by
Board Location: Dual Shelf 00, Shelf 00, slots 7 & 8
LED Status:
V14.00/EN
Red LED
Green LED
Status
Unlit
Lit
Module active
and Unlocked
35
June 2003
Interface Node
4 - 8K RM
Switching Unit
CEM
Unused
9 S-links
SUB RATE
SWITCHIN
G
8K RM
Front
Panel
8K-RM MAIN FUNCTION: SUB RATE SWITCHING
View
36
The 8K RM (8K Resource Module) is also named SubRate Time Switch.

Its role is to provide a subrate switching capability, as the CEM module only switches at
the DS0 level (64 kbps). The 8K RM switching activity is controlled by the CEM Module.
The 8K RM can switch at DS0 sublevels: 8 kbps and 16 kbps, and its total switching
capacity is 2268 DS0 channels.
It performs the following functions:
Transmits and receives data to / from both CEM modules through 9 S-links,
Provides 8 kbps time-switching.
Two LEDs,
4 unused connectors.
Redundancy scheme: 1+ 1 Hot Stand-by.
Board Location: Dual Shelf 00, Shelf 00, slots 9 & 10
LED Status:
V14.00/EN
Red LED
Green LED
Status
Unlit
Lit
Module active
and Unlocked
36
June 2003
Interface Node
5 - ATM RM
Control
Node
Interface
Node
3 S-links
(768 TS)
ATM RM
ATM SW
CEM
CEM
OC-3c Link
155 Mb/s
T
X
R
X
Redundant
Optical
Connection
TX OC-3c
Connecto
r
To RX on
the CN
3 S-links
(768 TS)
AAL1
LAPD, SS7
AAL5
OAM, CallP
RX OC -3c
Connecto
r
From TX
On the CN
Front
Panel
View
ATM-RM MAIN FUNCTION: ATM RESOURCES FOR IN

APPLICATIONS
37
The ATM RM (ATM Resource Module) provides the centralized resources required to
support the Interface Node applications.
It performs:
A SONET OC-3c physical interface, that allows direct connection to the ATM
network located in the Control Node. Caution an optical attenuator must be
inserted on the TX connector output.
adaptation between the ATM cells of the Control Node (high bitrate: 155 Mbps)
and the DS0 circuits of the Interface Node (low bitrate: 64 kbps):
AAL1 adaptation for LAPD and SS7 channels
AAL5 adaptation for OAM and Call Processing Signaling.
Two LEDs
1 TX OC-3 (upper) + 1 RX OC-3 (lower) optical connectors.
Redundancy scheme: 1+ 1 (simultaneous work).
Board Location: Dual Shelf 00, Shelf 01, slots 5 & 6.
LED Status:
Red LED
Green LED
Status
Unlit
Lit
Module active
and Unlocked
Operating System: VRTX

V14.00/EN
37
June 2003
Interface Node
6 - LSA-RC Module 1/3
Backplane
IEM
IEM
TIM
Active
LSA RC
Module
Passive
To SAI
From SAI
LSA RC MAIN FUNCTION: PCM INTERFACE MODULE
38
The LSA RC (Low Speed Access Resource Complex) is the PCM Interface module. All
external communications run through this board.
Each LSA RC can manage up to 21 E1 or 28 T1 PCM links.
It provides the electrical interface for the signal on the PCM links.
This module is common to the Interface Node and the Transcoding Node.
In the IN, it is used to interface the BTS and the TCU.
In the Transcoding Node, it is used to interface the MSC and the BSC.
Each LSA block is a 3-slot slice made of:
2 IEM boards (Interface Electronic Module), which are in charge of the PCMs.
1 TIM board (Terminal Interface Module) which is a passive board that routes
the PCM towards the active IEM board.
Redundancy scheme:
for IEM: 1 + 1 Hot Stand-by
For TIM: no redundancy (only connecting and filtering functions).
V14.00/EN
38
June 2003
Interface Node
1
62-pin Sub D
Connector
to SAI
Red LED
blinks
Signal Failure
Indication
Red LED
blinks
Signal Failure
Indication
4
62-pin Sub D
Connector
from SAI
Up and down
Buttons
Front Panel
View for PCM
E1 links
Up and down
Buttons
Front Panel
View for PCM
T1 links
39

IEM board.
1) Two status LEDs
2) One multiple Span Failure Red LED
3) Signal Failure Indication head LEDs
4) Visual Display unit for span number
5) Up and Down arrow buttons.
TIM board.
Two LEDs
1 TX Sub D 62-pin (upper) + 1 RX Sub D 62-pin (lower) connectors.
Board Location:
Dual Shelf 00, Shelf 00, slots 1 & 2 & 3 + slots 4 & 5 & 6 + slots 12 & 13 & 14.
Dual Shelf 00, Shelf 01, slots 2 & 3 & 4 + slots 8 & 9 & 10 + slots 11 & 12 & 13.
LED Status
V14.00/EN
Red LED
Green LED
Status
Unlit
Lit
Module active
and Unlocked
39
June 2003
Interface Node
FRONT PANELS
DETAILS
NO information is displayed
when there is NO problem to
report.
Red Multiple
Span Alarms
Signal Failure
Indication
* Only the highest severity signal

failure is displayed on the front
panel LEDs.
PCM Failure
Indication
Up and Down
Buttons
Front Panel
View for PCM
E1 links
Front Panel
View for PCM
T1 links
LSA RC FAILURE INDICATORS
40
The interactive portion of the faceplate consists of the following elements:

Multiple span failure indication red LED:
LED OFF: zero or one PCM failure
LED BLINKS: two or more PCM failures.
Signal failure indication LEDs (transparent text cover), same behavior for all the
alarms:
LED ON: when the fault is the highest ranking fault
LED OFF: when the fault is no longer the highest ranking

fault.
LOS: Loss of Signal
AIS: Alarm Indication Signal
LFA (for E1): Loss of Frame Alignment = LOF (for T1): Loss Of signal
Frame alignment
RAI: Remote Alarm Indicator.
PCM failure indicator:

BLANK if IEM module not in service, and for the inactive IEM module.
Text OK if there is NO provisioned PCM link failure.
Text XX: problem with copper connection between the IEM and the
SAI.
Number from 1 to 21 for E1 links, and from 1 to 28 for T1 links.
Increment / decrement control to show alarms for multiple failed spans: pressing
the Up or Down arrow key will increment or decrement the information displayed
to the next fault alarm.
V14.00/EN
40
June 2003
Interface Node
7 - Minimal Configuration for the IN
1 ATM-RM (+ the corresponding ATM-SW in the CN)

1 CEM
1 8K RM
n LSA-RC (= 1 TIM + 1 IEM, but always the LSA n0)
1 SIM
V14.00/EN
41
41
June 2003
Transcoding Node
V14.00/EN
42
42
June 2003
Transcoding Node
1 - Architecture
TRM
TRM
TRM
TRM
S links
TOWARDS
BSC
Ater
Interface
CEM
LSA RC
PCM
Interfac
e
S links
LSA RC
S links
64 kbps
PCM
Interfac
e
A
Interface
TOWARDS
MSC
43
The Transcoding Node is based on the Nortel Networks SPECTRUM platform.

Each TCU cabinet consists of 2 Transcoding Node shelves and 1 SAI (Cabling Interface
Unit) providing front access to the PCM cabling.
The Transcoding Node does the following:
Provides network connectivity with the BSC e3 and the MSC.
Converts LAPD channels into DS0 links.
Transports SS7 signaling links via DS0 links.
Allows communication between the Transcoding Node and the Control Node
via LAPD channels over DS0 links and via the Interface Node.
Manages GSM vocoding of the speech / data channels.
Reduces of the number of PCM links required.
N.B: The Transcoding Node shares some major hardware modules with the Interface
Node, such as the CEM and the LSA-RC boards.
V14.00/EN
43
June 2003
Transcoding Node
Dual Shelf 01 Shelf

00
Dual Shelf 00 Shelf

01
Dual Shelf 00 Shelf
00
Transcodin
g Node no.
01
11
12
13
13
14
14
SIM
15
SIM
TRM
LSA RC
N3
10
12
TRM
11
TRM
10
TRM
TRM
LSA RC
N2
Filler
8
TRM
TRM
TRM
4
TRM
CEM
CEM
LSA RC
N0
TRM
TRM (opt)
TRM (opt)
SHELF 00
Dual Shelf 01 Shelf

01
LSA RC
N1
Filler
SHELF 01
2 - Boards Layout
15
Synchronization
Transcodin
g Node no.
00
44
The main function of the TCU (TransCoder Unit) is to perform the main tasks related to
communication, switching and transcoding.
The following hardware modules are part of the Transcoding Node:
The CEM (Common Equipment Module), which controls the BSC Interface
Node Resource Modules, and provides system maintenance, clock
synchronization, and traffic switching.
The TRM (Transcoder Resource Module), which performs the GSM transcoding
functions. Each shelf of the TCU can contain up to 12 TRMs (the boards located
in the slots 1 and 2 are optional).
The LSA RC (Low Speed Access Resource Complex), which is used to
interface the TCU to both the MSC and BSC using PCM links (E1 or T1). They
must be inserted in ordered steps.
the TCU. For redundancy purposes, there are 2 SIMs per equipment: each SIM
contributes to supply each shelf (at 50% level).
V14.00/EN
44
June 2003
Transcoding Node
3 - TRM
TRM Module
#3
PPU SPU PPU SPU PPU SPU
#2
SPU PPU SPU PPU SPU
#1 Mail PPU SPU
Mail
Box PPU
SPU
PPU SPUSPU
PPU SPUSPU
Mail
Box
SPU
SPU
SPU
Box
SPUSPU
SPUSPU
SPUSPU
SPU
SPU
SPU
SPUSPU
SPUSPU
SPUSPU
SPU
SPU
SPU
SPU
SPU
SPU
PP
QUICC
CEM
3 S-links
1 Island
1 DSP Archipelago
Front
Panel
TRM MAIN FUNCTION: VOCODING OF SPEECH / DATA
CHANNELS
View
45
The TRM (Transcoder Resource Module) performs the GSM vocoding of the speech / data
channels. Up to 12 TRMs boards can be housed in one single TCU shelf.
The TRM provides:
Voice coding / decoding in Full Rate (FR), Enhanced Full Rate (EFR) and AMR.
Physical Organization:
9 Islands (1 island = 1 PPU (Pre Processing Unit) + 4 SPU (Signal Processing Unit))
3 Archipelagoes = TRM module (1 archipelago = 1 MLB (Mail Box ) + 3 Islands)
1 TRM = 216 voice channels in normal mode
1 TRM = 180 voice channels in TTY (US specific)
Two status LEDs .
Redundancy scheme: N + P load sharing
Board Location:
For both Dual Shelf 00 & 01,
Shelf 00, slots 1 to 3 + slots 9 to 14
Shelf 01, slots 5 & 6 & 14
LED Status:
V14.00/EN
Red LED
Green LED
Status
Unlit
Lit
Module active
and Unlocked
45
June 2003
Transcoding Node
4 - Minimal Configuration for the TN
1 CEM
n TRM (according to the traffic load)
n LSA-RC (= 1 TIM + 1 IEM, but always the LSA n0)
1 SIM
V14.00/EN
46
46
June 2003
Section 4
Thermic,, Energetic and Cabling Aspects
Thermic
whatsoever.
V14.00/EN
47
June 2003
Objectives
After completion of this section, the students will be able to:

Describe the power supply, alarms and cooling system
Understand the role of the SAI
Identify BSC e3/TCU e3 cabinet cables.
V14.00/EN
48
48
June 2003
Contents
Power Supply & Alarm Systems

Cooling System
BSC e3/TCU e3 Cabling
Fuses
V14.00/EN
49
49
June 2003
Power Supply & Alarms Systems

1 - PCIU Module
50
The Power Supply and the Alarm Systems of the BSC e3/TCU e3 are composed of:
One PCIU (Power Cabling Interface Unit): provides central distribution and
gathering of all power and alarm cabling used inside the BSC e3/TCU e3
frames.
4 SIMs (Shelf Interface Module): used to transfer the -48 V dc and the alarms to
and from each module via the PCIU.
The PCIU is located in a frame power distribution tray and is mounted on the top of the
BSC e3/TCU e3 frame. It contains the following modules:
ALM (Alarm Module): monitors the SIM modules, the cooling units and the fuse
failures, provides control for each LED on the fan units, reports alarms on each
dualshelf, reports the PCIU fail function.
2 FMU (Fan Management Unit): softstart used to limit capacitor inrush current,
capacitor fault alarm, 48V / 60V at 30 A input capability, input transient
protection alarm.
When the frame summary indicator (amber lamp) located on the front cover is:
OFF: there is no active alarm in the BSC e3 or TCU e3 frame,
ON: there is an active alarm in the BSC e3 or TCU e3 frame.
V14.00/EN
50
June 2003
Power Supply & Alarms Systems

2 - Shelf Interface Module
Switch
On / Off
Alarm Indicators
-48 V dc / alarms
Connector
To / from PCIU
Front
Panel
View
SIM MAIN FUNCTION: POWER SUPPLY
51
SIM means Shelf Interface Module. It is the power supply of the BSC e3/TCU e3 frames.
The input voltage is -48 V dc. It transmits also alarms notifications.
The SIM boards are the dc power conditioner for each Dual-shelf.
The SIM board manages the following functions:
Current limiting during Startup
Alarms
Filtered 48 V dc and Power conditioning.
Two status LEDs,
One Switch On/Off,
Amber LEDs Alarm Indicators,
A 48 V dc/alarms connector (7 pins).
Redundancy scheme: 1 + 1, simultaneous work.
Board Location: Dual Shelf 00 & 01, Shelves 00 & 01, slot 15.
LED Status:
V14.00/EN
Red LED
Green LED
Status
Unlit
Lit
Module active
and Unlocked
51
June 2003
Cooling System
1 - Location of the Cooling & Fan Units
Upper
grill
assembly
Lower
grill
assembly
52
The BSC e3/TCU e3 frames are cooled by two cooling units.

A cooling unit dedicated to the upper dual-shelf and including:
The upper grill assembly
The upper air filter
The upper fan units.
A cooling unit dedicated to the lower dual-shelf and including:
The lower grill assembly
The lower air filter
The lower fan units.
V14.00/EN
52
June 2003
Cooling System
2 - Cooling & Fan Units
COOLING UNIT
FAN UNIT
53
State of the LEDs located on the front panel of the Fan Unit:
Green LED
Red LED
Action
Faulty
Module
Press the lamp test: if

both LEDs turn on,
then
NO
If both LEDs remain on

after the end of the
self-test, then
YES

both LEDs turn on,
then
NO
---
YES
Note
The Test Lamp button re-lights (during 20 seconds) all the LEDs which have turned
to sleep mode, to detect any eventual LED malfunction.
V14.00/EN
53
June 2003

1 - SAI Frame
SAI
BSC e3 Cabinet
(*) the optional

HUBs can be
installed inside
or outside the
SAI.
HARDWARE OVERVIEW
54
The SAI (Service Area Interface) is a 30 cm-wide auxiliary frame attached at the left side
of the BSC e3/TCU e3 frame. It enables front access to the PCM cabling.
The SAI cabinet can host:
in the TCU e3: up to 8 CTUs (Cable Termination Unit)
In the BSC e3: up to 6 CTUs + 2 optional HUBs.
The CTU module is a frame assembly which provides the physical interface (PCM
E1/T1 links) between the TIM module of the LSA-RC and the other BSS products
(copper concentration).
It is split as follows:
1 x CTB (Cable Transition Board) which is the backplane,
7 x CTMx (Cable Transition Modules) that are either:
CTMP, E1, twisted pair, Z=120 Ohms: processes 3 spans.
CTMC, E1, coax, Z=75 Ohms: processes 3 spans.
CTMD, T1, twisted pair, Z=100 Ohms: processes 4 spans.
For local maintenance purposes, the TML can be plugged into a HUB of the BSC e3.
Note
The CTU provides the ability for each E1 or T1 PCM to be set in loopback mode, in
order to help the diagnostic of PCM faults.
V14.00/EN
54
June 2003

2 - BSC e3 Optical Fiber Cabling
Zoom on optical Cabling
ATM SW
TX
RX
Module
s
Optical Multimode Fibers
In the
CN
ATM RM
TX
RX
Module
s
In the IN
55
This figure shows how to connect the OC-3c optical multi-mode fibers.
They are used to connect the ATM backplane in the Control Node via the ATM -SW
module to the S-links backplane in the Interface Node via the ATM-RM module.
Notes
The optical link goes from the TX (ATM -SW in the CN) to the RX (ATM-RM in the IN),
The RX (ATM -SW in the CN) goes to the TX (ATM-RM in on the IN).
An optical attenuator must be inserted on the optical fiber at the output of the ATM -SW
module.
Reference of the Optical Fiber: NTQE0607.
V14.00/EN
55
June 2003

3 - PCM Cabling between SAI and LSA-RC
2 3
LSA-RC
1
Interface node
5 0
LSA-RCLSA-RC
5
0
LSA-RC
4
FILLER
TRM
TRM
TRM
IEM
TIM
IEM
CEM
CEM
TRM
TRM
TRM
TRM
TRM
TRM
SIM
LSA-RC
0
Air f ilter
IEM
TIM
IEM
IEM
TIM
IEM
CEM
CEM
8K-RM
8K-RM
FILLER
IEM
TIM
IEM
SIM
Transcoder node
LSA-RCLSA-RC
2
3
Cooling unit
2 3
LSA-RC
1
LSA-RCLSA-RC
2
3
Transcoder node
Air f ilter
2 3
LSA-RCLSA-RC
2
3
TRM
SIM
Cooling unit
Upper
Node
Lower
Node
LSA-RC
1
FILLER
IEM
TIM
IEM
TRM
TRM
FILLER
IEM
TIM
IEM
IEM
TIM
IEM
FILLER
IEM
TIM
IEM
ATM-RM
ATM-RM
FILLER
IEM
TIM
IEM
IEM
TIM
IEM
FILLER
SIM
Air f ilter
Cooling unit
TRM
TRM
TRM
IEM
TIM
IEM
CEM
CEM
TRM
TRM
TRM
TRM
TRM
TRM
SIM
TMU
TMU
TMU
TMU
SIM
OMU
OMU
ATM-SW
ATM-SW
TMU
FILLER
TMU
TMU
Control node
TMU
FILLER
TMU
TMU
MMS private
MMS shared
FILLER
FILLER
MMS shared
MMS private
TMU
TMU
TMU
TMU
SIM
TCU
PCIUe3
Cooling unit
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
IEM
TIM
IEM
TRM
TRM
FILLER
IEM
TIM
IEM
IEM
TIM
IEM
TRM
SIM
BSC
PCIUe3
LSA-RC
0
Air f ilter
56
Note: For both BSC e3 and TCU e3, all the cables linking the CTUs and the LSA-RCs
have the same length (1.66 meter).
BSC e3
In the case of a BSC e3, the SAI includes a maximum of 6 CTUs which are numbered
from the top to the bottom: 0, 1, 2, 3, 4, 5.
Each CTU must be connected to the relevant LSA-RC as follows:
CTU 0 < -- > LSA 1
CTU 1 < -- > LSA 2
CTU 2 < -- > LSA 3
CTU 3 < -- > LSA 5
CTU 4 < -- > LSA 0
CTU 5 < -- > LSA 4.
TCU e3
In the case of a TCU e3, the SAI includes a maximum of 8 CTUs; the 4 upper CTUs are
dedicated to the upper transcoder node dual-shelf, the 4 lower CTUs are dedicated to
the lower transcoder node dual-shelf. They are numbered from the top to the bottom: 0,
1, 2, 3, 4, 5, 6, 7.
Each CTU must be connected as follows:
V14.00/EN
CTU 0 < -- > LSA 1-up
CTU 4 < -- > LSA 1-down
CTU 1 < -- > LSA 2-up
CTU 2 < -- > LSA 3-up
CTU 3 < -- > LSA 0-up
CTU 7 < -- > LSA 0-down.

56
June 2003

4 - PCM Cabling: connection LSA-RC/CTU
IEM
TIM
Multiple
Span
Alarms
IEM
Multiple
Span
Alarms
Tx signals
62-pin
connector
CTU
Rx signals
Tx
62-pin
connector
Rx
LSA-RC
57
Both cables are identical. Each of them is symmetrical (its two connectors are identical 62-pin connectors).
Both cables have to be connected as follows:
Tx signals: upper connector of the CTU with the upper connector of the front
panel of the TIM module.
Rx signals: lower connector of the CTU with the lower connector of the front
panel of the TIM module.
Note
The Rx cable must be connected before the Tx cable.
V14.00/EN
57
June 2003

5 - PCM Cabling: CTU connections
PCM
BSC
e3
PCIU
TMU
TMU
TMU
TMU
SIM
OMU
OMU
TMU
FILLER
TMU
TMU
MMS private
MMS shared
FILLER
FILLER
MMS shared
MMS private
TMU
TMU
TMU
TMU
SIM
Control Node
Air filter
CTU 4
CTMx6
CTMx5
CTMx4
CTMx3
CTMx2
CTMx1
CTMx0
IEM
TIM
IEM
ATM-RM
ATM-RM
FILLER
IEM
TIM
IEM
IEM
TIM
IEM
FILLER
SIM
FILLER
Cooling unit
LSA-RC
1
LSA-RCLSA-RC
2
3
Interface Node
IEM
TIM
IEM
IEM
TIM
IEM
CEM
CEM
8K-RM
8K-RM
FILLER
IEM
TIM
IEM
SIM
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
CTMX
ATM-SW
ATM-SW
TMU
FILLER
TMU
TMU
Cooling unit
LSA-RCLSA-RC
5
0
LSA-RC
4
Air filter
58
The number of the CTM in the SAI depends on the number of the given LSA-RC in the
shelf.
The numbering of the CTM ports goes from the left to the right and from the bottom to
the top: from 0 to 20 for E1 and from 0 to 27 for T1.
Example:
The PCM nb 0 from the LSA-RC nb 0 is linked to the CTU nb 0, CTM nb 0, port nb 0
V14.00/EN
58
June 2003

6 - Optional Hub: Bay Stack 250
59
A Hub is an active node which regenerates the Ethernet signal: it is the central switch in
a twisted pair network.
The equipment that is used is the BayStack 250 (Nortel Equipment).
BayStack 250 Series
The BayStack 250 is a standard stackable Ethernet Hub that contains:
12 RJ45 ports for twisted pair 10/100 Base T conductors. It is possible to
connect up to 5 Hubs together obtaining a 60-port logical Hub.
One LED display: Each port has two LEDs to indicate its port status.
One switch for connection to an Ethernet switch or another Hub.
Notes
Each port is a repeater.
The ports can be active simultaneously.
A slot is available for a management module. Two chained Hubs make a logical Hub.
V14.00/EN
59
June 2003

7 - BSC e3 and TCU e3 Alarms & - 48 V dc Cabling
60
For the BSC e3.

The figure shows how to connect the internal 48 V dc and alarm cables between:
the PCIU
and the four SIM modules located in the Control Node and the Interface Node.
The internal 48 V dc and the alarm links are distributed:
for the Control Node: from the SIM modules to the OMU modules and the other
modules via the ATM backplane.
for the Interface Node: from the SIM modules to the CEM modules and the other
modules via the Slink backplane.
For the TCU e3.
The figure shows how to connect the internal 48 V dc and alarm cables between:
the PCIU
and the four SIM modules located on both Transcoder Nodes.
The internal 48 V dc and the alarm cables are distributed on each Transcoder Node
from the SIM modules to the CEM modules and each RM via the S-link backplane.
V14.00/EN
60
June 2003

8 - BSC e3 Alarm Cabling
The regular lines show

the alarm internal ways on the back panel.
The bold lines show the alarm external way.
61
Alarm links
For the BSC e3 Frame.
The figure shows the internal and external alarm links for the frame assembly of the
BSC e3 cabinet.
V14.00/EN
61
June 2003

9 - TCU e3 Alarm Cabling
The regular lines show
the alarm internal ways on the back panel.
The bold lines show the alarm external way.
62
Alarm links
For the TCU e3 Frame.
The figure shows the internal and external alarm links for the frame assembly of the
TCU e3 cabinet.
V14.00/EN
62
June 2003
BSC e3/TCU e3 Fuses
FOR THE POWER SUPPLY BOX

1 main breaker (32 A) for the whole site
4 breakers or fuses (32 A) per cabinet.
FOR EACH BOARD

1 fixed fuse
63
Fuses
The power supply box is equipped with:
1 main breaker for the whole site
and 4 breakers or fuses (32 A) for the cabinet.
The general breaker/fuse value is the general value on the clients site, which depends
on the on-site equipments.
The following boards house a fixed fuse to protect each component:
OMU,
TMU,
MMS,
CEM,
ATM -RM,
8K-RM,
IEM (from the LSA-RC),
TRM.
V14.00/EN
63
June 2003
Section 5
BSC e3 and TCU e3 Hardware
Features and Configurations
whatsoever.
V14.00/EN
64
June 2003
Objectives

to:
Describe the hardware features of the BSC e3 and
TCU e3
Know about BSC e3 and TCU e3 configuration.
V14.00/EN
65
65
June 2003
Contents
Hardware Feature s
Configurations
V14.00/EN
66
66
June 2003
Hardware Features
1 - Main Characteristics
600
Service
Area
Interfac
e
BSC e3
TCU e3
600
Service
Area
Interfac
Transcoding
e
Transcoding
Node
Node
Control Node
Operating Temperature
(long term)
+ 40 C
+ 5 C
2200
2200
Transcoding
Node
Interface
Node
Transcoding
Node
Maximum
Relative humidity
85%
960
960
5%
Weight
Maximum Weight 570 kg
NB: dimensions are given in mm

67
The BSC e3 cabinet is a one-cabinet equipment made of 3 parts:

2 main frames hosting the Control Node and the Interface Node
a PCM cabling frame, called SAI (Service Area Interface).
The TCU e3 cabinet is a one-cabinet equipment made of 3 parts:
the 2 main frames hosting the Transcoding Nodes
a PCM cabling frame, called SAI (Service Area Interface).
The hardware design allows a complete front access to the equipment (SAI), including
fans, power supplies, and PCM cabling.
External cabling from below and above are supported.
There are 2 cooling units in each cabinet. Each cooling unit consists of 4 replaceable
fans and air filter, and a grill assembly.
The BSC e3/TCU e3 is designed to operate in clean rooms. It must be anchored to the
floor, not to the wall. The minimum floor resistance must be 1000 kg/m2.
The cabinet complies with ETSI standards.
V14.00/EN
67
June 2003
Hardware Features
2 - Filler Module
Front
Panel
View
Filler Module MAIN FUNCTION: FILL IN THE UNUSED SLOTS
68
The Filler Module is an empty module container which can be used inside all the Nodes
of the BSC e3/TCU e3 which are not filled with any other module.
It manages the following functions:
To maintain Electro Magnetic Interference (EMI) integrity,
To maintain shelf airflow patterns to ensure proper cooling.
External Interfaces on the Front Panel: NA
Board Location: the Filler Module can occupy any slot that does not house a module.
Note
Caution: If one or more slots remain empty on a powered shelf, then TCU e3 or BSC e3
frames may be damaged. These fillers ensure:
A good equipment cooling
A proper EMI shielding.
V14.00/EN
68
June 2003
BSC e3 and TCU e3 Configurations

1 - Min and Max Configurations
BSC e3 and TCU e3 dimensioning
Min
Max
Erlang
600
3000
TRX
360
1000
BTS
120
500
Cells
360
600
LAPD links
120
600
E1 / T1 PCM (BSC e3)
42 / 56
126 / 168
E1 / T1 PCM (TCU e3)
21 / 28
84 / 112
A interface circuits (TCU e3)
200
1944
A interface circuits (BSC e3)
620
3112
16
SS7 links
69
This table gives the minimum and maximum possible configurations for the BSC e3 and
TCU e3 cabinets.
BSC e3 configuration:
The minimum is a 600 Erlang BSC e3 with 3 TMU modules (2+1 for
redundancy) and 2 LSAs (42 E1 or 56 T1 PCMs).
The maximum is a 3000 Erlang BSC e3 with 14 TMU modules (12+2 for
redundancy) and 6 LSAs (126 E1 or 168 T1 PCMs). In this case, the BSC e3
requires 2 TCU e3 cabinets .
TCU e3 configuration:
The minimum is a 200 Erlang TCU e3 (in the case of EFR) with 2 TRM modules
(1+1 for redundancy), 1 LSA (21 E1 or 28 T1 PCMs).
The maximum is a 1800 Erlang TCU e3 with 10 TRM modules (9+1 for
redundancy) and 4 LSAs (84 E1 or 112 T1 PCMs) in each TCU e3 shelf.
Notes
Between these minimum and maximum configurations, different configurations can be
offered. Nevertheless, in the TCU e3 cabinets, the number of TRMs and LSAs is directly
linked to the A Interface capacity.
Moreover, some product engineering rules have been defined to avoid inconsistency
between the number of TMUs and the number of LSAs.
V14.00/EN
69
June 2003

2 - BSC e3 & TCU e3 Typical Configurations
Typical
Configurations
BSC e3
TMU
LSA
Nb of LAPD
Nb of E1
Nb of
T1
600 E
2+1
2
120
42
56
1500 E
5+1
3
300
63
84
2400 E
8+2
5
480
105
140
3000 E
10+2
6
600
126
168
X (active) + X (redundant) = Total Number of Boards
TCU e3
TRM
LSA
Nb of E1
200 E
1+1
1
21
600 E
3+1
2
42
1200 E
6+1
3
63
1800 E
9+1
4
84
Nb of T1
28
56
84
112
70
Nortel Networks has defined some market model configurations (rural, semi-urban,
urban), and optional extension kits (comprised of TMU, TRM & LSA) in order to help the
operators select the appropriate number of modules.
A rural type of configuration with
a relatively low number of TMUs (low traffic capacity)
a maximum number of LSAs (because many small BTSs used for
coverage need to be connected).
An urban type of configuration with
a high number of TMUs (high traffic capacity)
a relatively low number of LSAs (because BTSs have many TRXs per
cell, and there are relatively few BTSs to be connected to the BSC).
Note: The BSC can have a maximum of 14 TMU modules (12+2) for very tough traffic
profiles.
V14.00/EN
70
June 2003

3 - BSC e3 Configuration Examples
BSS Configuration
S111
S222
S333
S444
S888
Nb of BTSs
BSC capacity (Erl)
Nb of TRXs
200
1300
600
125
3000
750
70
3000
630
50
3000
600
20
3000
480
12
5
70 / 70
12
4
50 / 62
12
4
40 / 46
TMU
LSA
Abis E1 / T1
6
12
6
6
115 / 150 100 / 126
Ater E1 / T1
11 / 18
26 / 42
26 / 42
26 / 42
26 / 42
Agprs E1 / T1
10 / 14
7 / 10
7 / 10
5/7
4/6
71
This table gives some dimensioning examples of BSC e3 according to the type of BTS
site.
The figures in italics are the dimensioning factors for the BSC e3.
With the exception of a pure S111 BTS configuration, the only dimensioning factor is the
maximum Erlang capacity (3000 E).
If the network consists of 100% S111 BTSs, the maximum number of cells (600)
supported by a BSC e3 is reached before the maximum Erlang capacity.
In S111 and S222 cases, Abis concentration is assumed.
V14.00/EN
71
June 2003
Section 6
BSC e3 and TCU e3 Startu
Start up
whatsoever.
V14.00/EN
72
June 2003
Objectives

to:
Describe the global startup sequence of the BSC e3/TCU
e3
Identify the different levels of BSC e3 and TCU e3
startup
Understand the right procedure to be applied for each
hardware entity.
V14.00/EN
73
73
June 2003
Contents
Equipment Startup
BSC e3 and TCU e3 Startup at the OMC-R
CN Startup
IN Startup
TN Startup
Fault-Tolerance
V14.00/EN
74
74
June 2003
Equipment Startup
1 - Principle
BSS
BSC
TCU
Interface Node
Control Node
Transcoder
Node
75
The BSC e3 and TCU e3 are:

Hot Swap (a switch between active/passive modules can be performed without
any interruption of service).
Plug and Play (cards can be added/removed at any time without powering
down).
Note: Do not insert/extract modules while the BSC e3 & TCU e3 are powered down (risk
of equipment damaging).
The following devices are said to be operational when:
Board => Platform Initialization completed
Slice => all its boards are operational.
Control Node => Application Initialization is completed.
BSC => both CN and IN are operational.
The BSC e3 startup can be divided into two types:

Hot start where the MIB is already built.
Cold startup involving the MIB build phase (Management Information Base).
V14.00/EN
75
June 2003
Equipment Startup
2 - LED Display (1/2)
Module Front Panel Indicator
76
Each module inside each dualshelf houses the same two LEDs on the upper part of the
front panel to ease onsite maintenance and reduce the risk of human error.
The actual color of these LEDs are referenced as:
red with a triangular shape
green with a rectangular shape.
The red and green LEDs indicate the module status.
V14.00/EN
76
June 2003
Equipment Startup
2 - LED Display (2/2)
Unlit LED
Unlit LED
Lit LED
Lit LED
* Module not powered

* BIST terminated successfully
* Test Lamp button not
pressed
Unlit LED
Table 2
Unlit LED
Lit LED
Lit LED
Unlit LED
For MMS Module
Unlit LED
For each Module except MMS
Unlit LED
Unlit LED
Lit LED
Lit LED
Table 1
Unlit LED
Unlit LED
Unlit LED
Lit LED
Winking LED
Lit LED
Unlit LED
Unlit LED
77
Table 1 gives the description, combinations and states of the red and green LEDs for
each module (except the MMS module) inside the BSC e3 and TCU e3 cabinets.
Note: Table 2 is for the MMS modules.
Scenarii for modules except MMS: (description of LED behavior).
Scenario 1: module insertion (general case): step 1 -> step 2 -> step 1 -> step 4.
Scenario 2: insertion of a TMU or an ATMSW module (administrative state unlocked):
step 1 -> step 2 -> step 1 -> step 3 -> step 4.
Scenario 3: removal of a passive OMU module, one must press the removal request
button (a TML command also exists): step 3 -> step 1 -> step 6.
Scenario 4: removal of an active OMU: step 4 ->step 3 -> step 1 -> step 6.
Scenarii for MMSs modules: (description of LED behavior).
Scenario 1: insertion of a MMS module (normal case: administrative state unlocked):
step 1 -> step 2 -> step 3 [updating ...] -> step 4.
Scenario 2: insertion of a MMS module (administrative state locked):
-> step 2 -> step 3.
step 1
Scenario 3: removal of a MMS module, one must press the removal request button (a
TML command also exists): step 4 -> step 3 -> step 6.
V14.00/EN
77
June 2003
BSC Startup at the OMC-R

1 - Hot Startup (MIB already built)
IN
OMC- R
OUT
Notifications
BSC e3/TCU e3
Initial Hardware Configuration
78
A Hot Startup is performed when the MIB is already built. This is the case when a BSC
e3 is restarted for example. (Note that the Hot Startup principle is the same as in BSC
2G).
Three cases may occur:
A module was extracted: a specific event is sent indicating a state change to
disabled/{not Installed} of the object that was previously in the slot. On
reception of this state change, the OMC-R will delete the corresponding logical
object at the MMI and in the MIB. An alarm is triggered at the father object level
to indicate the deletion.
A new module was inserted: (it was plugged into a previously-free slot): the
corresponding CN & IN objects are automatically created at the MMI as well as
in the MIB. The platform will send notifications indicating that the hardware
configuration has been detected on the corresponding platform object (CN, IN,
LSA or Transcoder equipment). This information is stored on the OMU disk and
sent to the OMC. The information is also stored at OMC-R level and can be
displayed upon operator request.
A module was replaced by another one: the initial object is removed at the MMI
and deleted in the MIB. The new object is created at the MMI as well as in the
MIB. Alarms are triggered at the father object level to indicate both
modifications.
V14.00/EN
78
June 2003
BSC Startup at the OMC-R

2 - Cold Startup (MIB not built)
OMC-R
BDE
2. MIB build request
k
Lin
SC
B
/
-R
d
MC she
1.O tabli
s
e
BSC e3
MIB
BTS
3. MIB build phase
MIB
Building
BTS
79
A Cold Startup is when the MIB (Management Information Base) is not built. (Note that
the Cold Startup principle is the same as in BSC 2G).
Note: the maximum acceptable configuration of the equipment is stored in the MIB. But
the new modules inserted are taken into account in the configuration only when the
OMC-R is connected to the BSC e3.
The startup sequence includes the following steps:
The operator builds the network at the OMC-R level and creates the BSC logical
object. He also has to define the CN, IN and LSA-RC modules, indicating their
hardware positions.
As soon as the OMC-R/BSC link is established, the BSC sends a notification
indicating that an MIB build is requested.
Upon receipt of this notification, the OMC-R triggers the MIB build phase. This
phase ends with the creation of the MIB logical objects followed by the reception
of a report build message.
The BSC sends a global notification giving the OMC-R the description of the
detected hardware components.
The detected modules appear on the MMI.
These modules are created at the BSC/OMC-R interface.
The supervision software reports the state of all created modules.
V14.00/EN
79
June 2003
Control Node Startup
V14.00/EN
80
80
June 2003
CN Startup
1 - Main Principles
Control Node
Slice
Dead Office Recovery
Board
Slice Recovery
Board Recovery
Hardware Startup Progress
81
There are three different levels of Control Node startup:

Board Recovery consists of performing the board startup sequence. Some boards are able to start
autonomously (booting from non-volatile storage) whereas others must wait as they require the
services of a board which must already be operational.
Slice Recovery means a startup sequence of one individual module. This sequence applies when
the on-site staff adds hardware resources to a BSC which is already powered up and operational.
The aim here is to increase the BSC capacity or to allow hardware repairs without powering down
the whole BSC.
Dead Office Recovery involves all components of the BSC and goes from power-up (without
software running) to a fully operational state of the equipment. It means that all slices must perform
their own slice recovery. Since the boards without processor cannot perform self-recovery, this
operation must be handled by another board.
This scenario applies to the CN slices: OMU, TMU and ATM SW.
V14.00/EN
81
June 2003
CN Startup
2 - Board Recovery
Startup Dependencies
Boot
Platform
Application
Sequence
Initialization
Initialization
OMU
SBC
OMU TM
ATM-SW
SBC
TMU TM
TMU SBC
TMU
PMC
Inter-board startup Dependencies
Means software downloading

(flash)
82
Board Recovery consists of performing the board startup sequence.

For each board, the startup sequence includes the following three ordered steps:
1) The Boot Sequence gets the software image, loads it into RAM and runs it.
Software images can be stored on the board itself or downloaded from a boot
server.
2)
Platform Initialization involves starting the Minimal Non Fault Tolerant
Platform which provides the applications to be run on the board (such as OAM
and messaging).
3)
Application Initialization covers both the creation and initialization of
BSC applications. This phase is managed in accordance with the BSC
configuration and available resources.
Note
At a given time, different boards are in different phases of the startup sequence.
V14.00/EN
82
June 2003
CN Startup
3 - Slice Recovery
Slice
OMU
TMU
ATM-SW
Number of
Slices
2
2 to 14
Boards
included
Processor
present
TM
Yes
SBC
Yes
PMC
No
TM
Yes
SBC
Yes
PMC
Yes
TM
No
SBC
Yes
83
Slice Recovery consists of recovering each board on the slice.

A slice is a card plugged into a slot on a shelf of the BSC e3 and TCU e3.
It is also called an FRU (Field Replaceable Unit) and it is the smallest
replaceable/ removable unit from the shelf.
A slice is made up of boards.
A board is a Printed Circuit Board which has (or does not have) a processor.
Boards that do not have a processor cannot recover by themselves and their recovery
must be handled by another board.
V14.00/EN
83
June 2003
CN Startup
10
11
12
13
14
SIM B
15
SIM A
TMU
14
TMU
TMU
13
TMU
TMU
12
TMU
11
TMU
10
MMS Private
TMU
OMU
ATM SW
8
MMS Shared
Filler
ATM SW
6
Filler
OMU
5
MMS Shared
TMU
4
MMS Private
TMU
TMU
Filler
2
TMU
TMU
Shelf 00
Filler
TMU
Shelf 01
4 - Dead Office Recovery
15
84
Dead Office Recovery consists of all the slices performing their slice recovery.
A BSC e3 is in Dead Office State when both OMUs are in an undefined activity state, i.e.
neither is passive nor active.
When a Dead Office State is detected, the active OMU resets all the TMUs (loss of
traffic service).
If a Dead Office State is incorrectly detected, it will result in a service interruption and all
the TMUs are reset.
The entire Control Node startup sequence must be performed.
V14.00/EN
84
June 2003
CN Startup
5 - CN Complete Startup Sequence
Boards
Active OMU-SBC
Passive OMU -SBC
OMU-TM/TMU -TM
TMU-SBC
TMU-PMC
ATM-SW
Slices
OMU
TMU
ATM-SW
CN Startup
IN Startup
TN Startup
85
The ATM-SW load their static AAL5 configuration.

Each OMU boots from its own local disk, independently from the others.
Both OMU-TM slices boot from their attached OMU-SBC. It acts as a local boot
server for the slice.
Both OMU-SBCs debate to elect the active OMU. This active OMU acts as the
local boot server for the shelf.
TMU-TMs and ATM-SWs boot in parallel from the active OMU.
TMU-SBCs boot from the active OMU via their TMs.
TMU-PMCs boot from the active OMU via their TMU-SBC and TMU-TM.
Note
If both OMUs fail, when the active OMU re-starts, it resets all the TMUs. All the traffic is
lost.
V14.00/EN
85
June 2003
CN Startup
6 - CN Startup Timer
1
2
Some TMUs are
Not operational
All TMUs are

Operational
86
Note: The BSC e3 has a startup timer in order to detect problems with the Control Node and the
Interface Node.
The Control Node startup sequence runs in parallel with and independently with respect to the IN
startup sequence: if the CN and IN indicate that they are operational, then the BSC e3 is said to be
operational.
The Control Node has a startup timer in order to detect problems with slices during recovery. This
timer is started once the active OMU has completed Platform Initialization.
Each slice sends a notification when it becomes operational. If all the slices send a notification before
the end of the startup timer, then the timer is stopped.
If the timer expires then those slices which have not sent a notification are considered as inoperative.
When the startup timer is stopped or if it expires, the CN startup sequence continues if and only if there
are enough operational slices to face the BSC e3 theoretical workload.
This theoretical workload is a configured parameter which indicates the minimum number of operational
slices required for service.
If there are not enough operational slices to handle the BSC e3 engineered workload, the CN manages
a certain number of cells, with the number of TMUs available. A notification is sent to the operator, to
indicate a lack of resources.
V14.00/EN
86
June 2003
Interface Node Startup

Transcoding Node Startup
V14.00/EN
87
87
June 2003
IN Startup
1 - Main Principles
CRITICAL PATH TO THE
CN
Creation
Platform Object
Creation
CEM board
Creation
ATM -RM
CONFIGURATION
OF THE OBJECTS
STORED IN MIB
MIB
Switch on
Set
In
Service
Set
In
Service
88
Each card of the IN contains a software release in its Flash Memory in order to have at
least the boards of the critical path able to run as soon as possible.
Critical path = set of boards (CEM + ATM-RM) that must be ready to establish
immediate communication with the CN when the IN starts.
The configuration data for these boards are stored in the IN non-volatile memory. Other
cards will be treated later, once this link is established.
An operator can add a module in the IN, whatever its software configuration.
The starting phase of a module depends on the state of its Flash Memory:
Either the Flash is empty: it contains only the IBL (Initial Boot Loading).
Or it contains a software release that will be loaded into the RAM and the
module is valid.
4 starting cases can occur:
1) Restarting with the CEM in the IBL state
2) Restarting a valid CEM: minimal configuration
3) Restarting a critical pathed RM in IBL state
4) Starting a non-critical pathed RM in the IBL state.
V14.00/EN
88
June 2003
IN Startup
2 - CEM/RM Modules States
2
IBL STATE
VALID SATE
3
INITIAL STATE
89
States of the Non-volatile memory of the CEM or RM boards:

Initial: contains nothing
IBL state: does not contain any valid release of the software
Valid state: contains a valid state of the software release.
Two cases can occur:
1)
at startup: the modules inserted in the IN (respectively Transcoding Node)
must be configured with the IN (resp. TN) software.
2)
at any other time: if a module is inserted with a software version which
does not correspond to the Node, it is considered as being in the IBL state, and
an update is performed.
Note: the software checking is automatically activated when the module is inserted into
the Node.
Phases of Commissioning:
1)
Writing the IBL into the Flash.
2)
The first release of the software has been loaded into the Flash, or the
software has been downloaded after failure during the previous upgrade.
3)
There has been a failure during the previous on field release upgrade.
The module automatically comes back into the IBL state.
V14.00/EN
89
June 2003
TN Startup
CRITICAL PATH TO THE BSC
e3
Creation
Platform Object
Creation
CEM board
Creation
LSA-RC
Creation
IEM
CONFIGURATION
OF THE OBJECTS
STORED IN MIB
Creation
PCMs
MIB
Switch on
Set
In
Service
Set
In
Service
90
When the TCU e3 is switched on, it has to deal with its critical path management. The
critical path represents the TCU e3 objects which needs to be in service in order to
enable the dialogue between the CN and the TCU e3 through the IN.
On the TCU e3, critical path management consists of:
Creation of the platform object (logical representation of the TCU)
Creation and setting in service of one of the CEM boards
Creation of the LSA no.0, located into the slots no. 4, 5 and 6 (synchronization)
Creation and setting in service of the IEM of this LSA
Creation and setting in service of PCMs associated with this LSA
Attempting to open a LAPD dialogue with the CN on one of these PCMs.
Once the BSC e3/TCU e3 dialogue is established, the TCU sends the OMC-R its
Hardware configuration (i.e. the identification of the different boards detected in the TCU
by the CEM).
Then, it can start the creation of the logical objects (Platform, LSA, PCMs) and the
creation of the hardware objects (CEM, TRM, IEM).
The MIB is updated, and the hardware objects associated with the new inserted boards
are created.
V14.00/EN
90
June 2003
Fault Tolerance
V14.00/EN
91
91
June 2003
Fault Tolerance
1 - Fault Tolerance Software
Fault Tolerance
Platform
1
Active
Instance
Current context
update
Passive
Instance
Fault Tolerance
Platform
2
ACT
SW
Active
Instance
FAU
LT
Passive
Instance
Active
Instance
92
A Fault Tolerant Application (FT) is an application which is replicated: it has at least one
passive mate hosted on another board. The passive module can take over and continue
to run the application without any break in service.
The active instance of the FT application runs the application code.
The passive instances of the FT application are simply kept up-to-date with the current
context of the active instance.
The process of changing a passive instance to an active instance is called a SWACT
(SWitch of ACTivity).
Load Balancing (LB) is the ability of the Control Node to balance resources of Fault
Tolerant Applications (CPU load, memory, ATM network, Abis links, Ater links, timers)
on TMUs. It has been designed to minimize overload issues by sharing well distributed
resources and distribute passive entities in order to have well balanced entities after a
swact.
V14.00/EN
92
June 2003

Fault Tolerance
2 Cell Group Concept
BSC e3
Load
Balancin
g
New Site
93
The Cellgroup (CG) is a group of radio cells managed by the same call processing
application instances. A BSC e3 can manage a maximum of 96 CG. Each Cellgroup
manages an average of 60 Erlang and its maximum capacity in term of traffic is the one
of a TMU board: 300 Erlang. Each TMU module is able to manage up to 95 sites
arranged in 16 (8 actives, 8 passives) Cellgroups per TMU (up to 100 TRX). The
Cellgroups are determined at boot time by the Load Balancing function.
The CG dimensioning must respect:
96 CG maximum per BSC e3
24 sites maximum per CG
48 cells maximum per CG
48 TRX maximum per CG
300 Erlang per CG
Note: if some BTS sites or TRX are added, the load balancing function may reorganize
the traffic load on the TMUs.
A site must be placed in a CG by a BSC at its creation and cannot be moved to another
CG after that. The only way to move a site from one CG to another is to delete it and
then to re-create it.
Another possibility is to perform a on-line build (with complete service loss of the whole
BSC for a few minutes).
V14.00/EN
93
June 2003
Fault Tolerance
3 - Example: SWACT on TMU Failure
TMU#1
TMU#2
A1
P2
TMU#1
P1
A1
A2
P3
A1
TMU#3
Active Process
P2
A3
P1
TMU#2
TMU#3
A1
A2
P2
P3
A3
Passive Process
94
All the processing relative to a Cellgroup is executed on a single TMU. The

corresponding passive (or redundant) process is executed on another TMU.
In this example, there are three groups of processes, each is composed of one active
process Ai plus one passive process Pi with i as the application identifier.
The three active processes are distributed across three TMUs.
The passive process related to one active process does not run on the same TMU as
the active process. The passive processes are directly and continuously updated by
their corresponding active process, using internal messaging.
On failure of TMU1, the Fault Tolerance algorithm performs a SWACT by electing the
passive P1 process as Active.
The figure shows the new distribution of processing over the two available TMUs.
V14.00/EN
94
June 2003
Section 7
BSC e3 and TCU e3 Troubleshooting
whatsoever.
V14.00/EN
95
June 2003
Objectives
After completion of this section, the students will be

able to:
Describe the BSS equipment troubleshooting
stages
Briefly describe the RACE and TML e3 equipment
Know how to use the TML e3.
V14.00/EN
96
96
June 2003
Contents
Overview
TML e3/RACE Hardware Architecture
TML e3/RACE Environment
RACE: Remote Access Equipment
TML e3: Terminal de Maintenance Locale
V14.00/EN
97
97
June 2003
Overview
Maintenance
TML
RACE
OMC-R
Terminal de
Maintenance
Locale
Remote ACcess
Equipment
98
The BSC e3 and TCU e3 can perform many OAM tasks in parallel.
This decreases:
The upgrade duration
The time required to bring the whole BSS network back into servi ce after a
restart.
Immediate and precise Fault Detection, even at module level, is enabled for software
and hardware failures on the BSC e3 and TCU e3.
Each hardware module is a Field Replaceable Unit (FRU) and is hot Plug and Play.
The Maintenance operations can be done from three types of equipment:
OMC-R: Operation and Maintenance Center-Radio,
TML: Terminal de Maintenance Locale (Local Maintenance Terminal),
RACE: Remote ACcess Equipment.
V14.00/EN
98
June 2003
TML/RACE Hardware Architecture
PCMCIA interfaces
TML
Or R
ACE
99
The same laptop PC can be used for:

The TML e3 application: it is a Java applet stored in the BSC e3 disk. It it
downloaded into the laptop PC and executed on the BSC e3 disk. It can be used
for all BSS equipment commissioning and maintenance.
The RACE application: it is acting as a Remote Workstation. It displays the
windows available on the OMC-R.
Minimum hardware configuration:

Pentium processor
6 Gb Hard Disk
64 Mo RAM
20 Mo (recommended 50 Mo) of free disk space
3.5'' floppy drive
SVGA color monitor
Windows 95, 98, 2000 or NT4
CD-ROM 4x drive
PCMCIA interface type 3 (or 2 of type 2)
Ethernet board in a PCMCIA format
RJ45 not crossed cable (connection through a hub)
RJ45 crossed cable (direct connection to a module).
V14.00/EN
99
June 2003
RACE
Remote ACcess Equipment
V14.00/EN
100
100
June 2003
RACE
1 - Environnement
LAN
RA CE
RA CE
OMC-R Server
(1) Remote
RACE client
(2) RACE client used as

light OMC -R station on
OMC-R location
PSTN
BT
S
(4) RACE client on BSS

location through a BSC e3
(3) RACE client on BSS

location through a BTS
BSC
e3
RA CE
RA CE
101
The RACE (Remote Access Equipment) is a Web interface to the OMC-R. The RACE
can be used as a particular OMC-R Workstation, excepted some particular functions.
This equipment replaces the ROT.
The advantages of this new product are the following:
Operations and Maintenance can be done from a remote site without requesting
an OMC-R on-site operator:
(1) using PSTN, modem and firewall
(2) through LAN (using an Ethernet board)
(3) via BTS S8000 / S12000 equipments
(4) via BSC e3 equipment
the interface is user-friendly, it is close to the interface of the OMC-R. Thus, the
tool is easy to manipulate for the user who is used to the OMC-R interface.
The unique requirement is to have a Web browser: the installation is done
quickly and its upgrade is done on-line, nothing will be modified on the client site
It is able to ensure a secure access to the network, which was no longer
guaranteed with the ROT.
V14.00/EN
101
June 2003
RACE
2 - Overview
JAVA
Real time information
MMI
Interface
OMC-R
Kernel
Server
Http
server
Web
browser
RACE Client
OMC-R Workstation/RACE server
OMC-R Server
102
The aim of the RACE is to access the OMC-R from a remote PC client using a Web
Browser.
This new application is composed of Web pages and Java applets that can be run
through a Web navigator (Netscape or Internet Explorer). All the software is on the
server html pages and Java applets and is downloaded to the client.
The RACE Client sends requests to an http Server, located on the LAN of the OMC-R
server. The requests are transmitted to a RACE Server running on an OMC-R
workstation.
RACE Client: this is the laptop PC on which the RACE application runs.
http Server: it receives the requests coming from the RACE client and transmits them to
the RACE server; it is installed on the same OMC-R workstation as the RACE server.
RACE Server: this is the link between the RACE client and the applications hosted
inside the OMC-R station. It transmits commands to the Kernel, and the submittals to
the relevant applications. It also translates the internal messages of the MMI for the
RACE client.
This application is adapted to individual operator needs:
when the operator must work from home
when operating at BTS or BSC e3 sites.
V14.00/EN
102
June 2003
RACE
3 - Login Window
The RACE needs the OMC-R username and password.
RACE
103
When starting a session, the user is asked for his OMC-R user name and password.
The password is encrypted before being sent to the server.
Login and password are then checked by the security task from the server. If the
username and password match the security information, a new OMC-R session is
started.
The RACE application can manage several connections; the maximum number of
communications is defined offline.
The process running on the RACE server manages the list of connected users, and the
beginning and end of sessions. It works as a new OMC-R task.
As the feature is multi-user, the first step is to identify each connection: since http is not
a continuous communication, the user has to be authenticated each time he sends a
new request to the server.
A better presentation of the data allows the customers to save time; suppose for
instance, that an operator must modify a list of parameters and makes a mistake. With
the RACE, using the Back button of the navigator, he just has to modify the wrong
parameters.
V14.00/EN
103
June 2003
TML e3
Terminal de Maintenance Locale
V14.00/EN
104
104
June 2003
TML e3
1 - Environnement
(1)
TCP/I
P/Eth
ernet
TML
PC
PSTN
LAN
Mode
m
(2)
(2)
TCP/IP/Ethern
et
(1)
TML
PC
(3)
TML
PC
TCP
/IP/E
the
rne
t
(4)
OMU
CEM
t
rne
the
/IP/E
TCP
TML
PC
BSC e3
105
TML means Terminal de Maintenance Locale.

TML connections:
The TML e3 uses Ethernet to connect the BSC e3.
The TML e3 PC uses a RJ45 crossed cable for a direct connection to the OMU or a
RJ45 non-crossed cable for a connection through a Hub.
Different physical connections are possible on the BSC e3 for the TML e3 equipment:
To the active OMU through a LAN (1)
To the active OMU through a LAN and the PSTN (2)
Directly to an OMU module of the BSC e3 (3)
Directly to an CEM module of the BSC e3 (4).
Notes
The TML e3 can be connected to the OMU module through an Ethernet connection, or
it can be plugged into a Hub.
The TML e3 communicates only with the active OMU module. When connected directly
to a OMU, the TML e3 can communicate with both OMU modules. Hence it can always
reach the active one.
The type (3) of connection is impossible if an OMC-R is already connected to the BSC
e3.
In the case of communication problems between IN and CN, it remains possible to
connect the TML e3 PC directly to the active CEM module.
V14.00/EN
105
June 2003
TML e3
2 - Overview
BSC e3
HTTP
Server
LAN
FTP
Server
Physical
Path
Manager
HTML
JAVA
Test
Management
S/W
Bus
Test
Server
TML
Interface
Node
Access
ATM
Manager
Hardware
Manager
Connection to a BSC e3 from a PC equipped with an http client.

106
The TML e3 hardware is a laptop PC working under Windows and behaving like a Java
Browser.
The TML e3 Application is a Java applet stored in the BSC e3 disk. It is stored in the
MMS module. Its interface is independent from the BSC e3/TCU e3 software evolution.
The TML e3 allows the user to:
Perform tests after an equipment installation (commissioning). In this case, the
equipment is off-line and the OMC-R link is out of service
Perform an audit before an important operation (an upgrade for example). In this
case, the equipment is on-line and the OMC-R link is in service.
Perform some upgrade (software or hardware) tasks. In this case, the
equipment is on-line and the OMC-R link is in service.
Perform corrective maintenance. In this case, the equipment can be on-line and
processing traffic. The OMC-R link can be in service or down.
Investigate and to localize any product problem. In this case, the equipment can
be on-line and processing traffic. The OMC-R link can be in service or down.
Note: Same TML PC for e3 as the one used for 2G BTS/BSC/TCU.
V14.00/EN
106
June 2003
TML e3
3 - Connections
Example of connection to a BSC e3
WEB
Browser
http://xxxxxxxxxx. html
Download html page

and Java applet
TML e3
Application
HTTP
server
HTML
JAVA
Try Connection
Send USER and PASSWORD
Send Commands
Test
Server
Receive Answers
TML
e3 Platform
107
Principle:
Using a web browser, the TML e3 operator loads an html page (through http) holding the
TML e3 applet.
When the TML e3 applet is downloaded to the TML e3 laptop PC using the http server: a
test session can be started.
The messages exchanged between the TML e3 and the BSC e3 are then carried
through a TCP/IP connection
The TML e3 communicates with the Test server software module.
Advantages:
The TML e3 PC will be able to run on a platform with any OS (theoretically including
Windows, Mac OS, Unix, Linux and so on).
No specific software to install. Only a web browser (with Java enabled) is needed.
The TML e3 release is always on time, on site, and up to date (Software integrated to
the e3 equipment)
It is possible to have a remote TML e3 connected to the BSC e3 LAN.
Only one standard hardware interface is used : Ethernet.
The TML e3 is used to perform a whole set of tests to check the integrity of the BSC e3
configuration (to check the correct operation of a hardware module, to check the
communication between two hardware modules, to perform loop-back testing (LAPD,
PCM, etc.).
The TML e3 also provides on-line equipment-monitoring capabilities such as software
spies, traces, notification decoding, dump decoding.
V14.00/EN
107
June 2003
TML e3
4 - TML e3 Man Machine Interface
V14
V14
108
General points when using Windows

Using the mouse: it is used to click directly in the menus. Simply place the mouse cursor
over the option required and click on the left-hand button. The prompt boxes, where
keywords ENTER or ESC appear, are selected by placing the cursor on the chosen box
and by clicking on the left mouse button.
Role of the keyboard: it is the basic dialog medium used with the TML. It can be used to
select options and to enter parameters for these selected options (disk name, file size,
etc.).
Title bar: it is located at the top of the window and it shows:
on the left, the window name
on the right, three icons performing the following functions: reduce to an icon,
expand to full-screen or close the window.
Proportional window size reduction, allows to reduce the window size proportionally:
position the cursor on an edge or in a corner of the window, and the cursor becomes a
double-arrow. Then press and hold the left mouse button, and drag the mouse to obtain
the required window size. Finally, release the mouse button.
Scroll bars: there are two scroll bars in each window.
a vertical scroll bar on the right
a horizontal scroll bar at the bottom.
V14.00/EN
108
June 2003
TML e3
5 - Login Window
TML
TML e3 Login Window

RJ45
TCP/IP
Ethernet
V14
Front
Panel
View
109
Connect the laptop PC with a RJ45 crossed cable to:

the active OMU module of the CN in the BSC e3,
the active CEM module of the IN in the BSC e3,
the active CEM module of the Transcoding Node in the TCU e3.
This allows Ethernet direct access between the equipment and the TML e3.
Launch the Web browser application by selecting the appropriate menu from the laptop.
Select the menu File/Open Page... and select the tmle3.html file of the TML e3
application: the above main TML e3 screen appears.
Start the TML e3 application according the right language user interface by clicking on
the right icon:
Dmarrer launches the French version
Start launches the English version.
When using the TML e3 for the first time, several Java Security windows will appear.
Each time, click on Grant.
V14.00/EN
109
June 2003
TML e3
6 - Connection Windows
1. Connection window
3. Error window
2. IP address and Port

Number
110
In the Connection window, select the node you want to connect to and click on the
Validate button:
CN for Control Node of BSC e3
IN for Interface Node of BSC e3
TCU for Transcoding Node of TCU e3.
In the TML connection menu, enter the IP address and the port number corresponding
to the Node the user wants to connect to (port number 11000 for IN and TCU, 12000 for
CN). Then click on the Connection button.
In case of connection problem, an Error window appears. It may be due to the fact that
the module is not the active one. In this case, connect the cable to the other module and
repeat the connection procedure.
V14.00/EN
110
June 2003
TML e3
7 - Starting Windows
Command in progress
window
Summary window
111
If the connection to the module is correct, the command Get hardware configuration is
launched at the startup of the TML e3.
The following windows appear. The Summary window gives a list of all the modules
detected by the TML e3, as well as their location in the cabinet.
By clicking on the OK button, the Summary window closes and the main window is
displayed on the screen (see next slide).
V14.00/EN
111
June 2003
TML e3
8 - Main Windows: Interface Node
V14
V14
Contextual Menu
112
For each connection Node (CN, IN and TCU), there is a corresponding main window.
The TML e3 main window is divided into 2 parts:
menu items, which are: Configuration, Test, Disk/Memory, Miscellaneous, View.
the e3 graphical view of the equipment. Each module present in each Node is
displayed in the equipment view with the indication of its position in the shelf.
The faulty modules are also notified on the view.
Notes about the general use of the TML e3:
Each time a new command is launched, a window appears allowing the cancellation of
the command in progress.
At the end of each command, a Summary window appears and gives the results of the
last command executed.
All the results of all the commands are stored in the Result window. This window may be
opened or closed through the command View/ Result view.
From this window, the TML e3 user is able to start the commands and tests using:
the main menu
the contextual menu, when clicking on the right button of the mouse, the cursor
being located on the graphical view of a module.
V14.00/EN
112
June 2003
TML e3
9 - Configuration Menu
V14
Configuration Menu
software markers summary

window
Get hardware Config summary

window
Marker reading selection

window
113
The Configuration Menu gives information about the hardware/software configuration;

the possible commands are:
Markers reading: the hardware and the software markers from the selected
boards are listed in the summary window. The information displayed are:
For the hardware markers: PEC code, serial number, product release,
manufacture date, insertion date, localization (unit, site, floor, row, bay,
shelf and slot) that can be modified later.
The software markers contain the software marking type of each
module (MIB, PROM, CODE) and marking result. The marking of the
OMU/CEM module corresponds to the current software version of the
node.
Software Markers: the user can consult the software markers of the selected
boards. This function is applicable to the following modules (ATM-SW, OMU,
TMU, ATM -RM, 8K-RM, LSA-RC, CEM and TRM ). The target modules can be
selected according to 2 choices:
All the modules on a defined type
A module defined by its location in the equipment.
The result displayed gives the marking type (MIB, PROM,

CODE) and the mark result.
Get hardware configuration: allows to refresh the graphical view of the e3

equipment and to see any configuration change that occurred recently. A
Summary window appears, displaying information about all the current
modules (board, instance, shelf, Slot and Number of slots).
V14.00/EN
113
June 2003
TML e3
10 - Test Menu (1/2)
Module Isolation
summary window
V14
Test Module menu window
Led Test selection

window
Warning window
Module Isolation process

duration window
114
The Test Menu gives access to several tests the TML can perform to check the e3 equipment
modules and links: the sub-menus are:
Module test:
SIM modules alarms: this test checks the SIM modules alarm signal states. The
target module can be selected by giving its location in the equipment or by
selecting all the modules of the same type. The result is displayed in the
Summary window: the state (Enabled or Disabled) of the PCU alarm and the
CU alarm relative to each SIM module is given.
LED test: this helps to check visually the LEDs status. The concerned modules
are: OMU, TMU, ATM-SW (CC1) and MMS. The target module can be selected
by giving its location in the equipment or by selecting all the modules of the
same type. The LEDs of the selected module light for 5 seconds. In the case of
several modules, the test is performed sequentially on each module.
Reset: to reset a module in the BSc e3 or in the Tcu e3. The concerned
modules are: OMU, TMU, ATM-SW (CC1). Only one module defined by its
position can be selected. A Warning window appears, notifying that this action
may have an impact on service. Once launched, it is impossible to abort the
reset command. CAUTION: DO NOT APPLY ON THE ACTIVE OMU OR
ACTIVE CEM MODULES.
Module Isolation: this resets a module for a defined time, to simulate a module
failure. The concerned modules are: OMU, TMU, ATM-SW (CC1). Only one
module defined by its position can be selected. A duration process setting
window appears (hours, minutes and seconds). As a result, the selected
module is isolated for the defined duration.
Set MMS busy: this simulates a busy state of a selected MMS module for a
defined duration. Only the module defined by its position can be selected. A
duration process setting window appears. As a result, the selected MMs
module is set in a busy state for the defined duration.
V14.00/EN
114
June 2003
TML e3
11 - Test Menu (2/2)
V14
Test Menu
Check OMU-OMU Ethernet summary

window
115
Link test:
CCS7/ LAPD Global Path: this test consists of sending a LAPD
sequence from one or several source modules, to one or several
targeted modules, on which a loop-back is performed. The possible
source modules are OMU and TMU. The possible target loop-back
modules are: CEM, LSA-RC and SAI. All PCM links or only one specific
can be selected. The Summary window gives the list of the failing links
between the OMU and TMU modules.
Check CC1 switch: this test checks communications between OMU and
TMU modules of the Control Node through the ATM-SW (CC1) module
switches. The Summary window presents the source module, the
destination module and the percentage of received frames/sent frames.
Check OMU-OMU ethernet: this test checks the ethernet
communication link between both OMU modules. The Summary
window gives the percentage of received frames/sent frames.
Check IN-CN optical link: this test checks the OC-3 optical connection
between the Control Node and the Interface Node.
V14.00/EN
115
June 2003
TML e3
12 - Disk Menu (1/2)
V14
Disk Menu
Customization window
116
The Disk Menu gives access to several operations on disk functions.

This Menu is organized as follows:
Customization: this menu allows to read and modify customization parameters.
A Warning window appears, notifying that this action may have an impact on
service. To modifiy a parameter, the new value must be entered in the
corresponding field. Then a click on the Customization button resets the e3
equipment. When the Node restarts, it takes the new parameters into account.
The result is displayed in the Summary window.
V14.00/EN
116
June 2003
TML e3
13 - Disk Menu (2/2)
V14
V14
Initialization Menu
Verification Menu
117
WARNING: the Interface Node/Transcoding Node INITIAL version must be at least

V13.0_AD_10. If not, it will not be possible to upgrade the software with the TML e3.
Initialization: the CN is delivered with an installed software version. However, in
some cases, some updating has to be done. Depending on the availability (or
not) of the OMC-R, the initialization tasks are shared between the TML and the
OMC-R. A software updating procedure includes the following tasks
(downloading, installation and activation). The downloading is performed
through a ftp server. This latter is therefore mandatory on BSC e3.
BSC software download: the BSC software is downloaded from the TML
to the shared MMS disks in the CN. The drive containing the EFT must
be selected. Note: do not click on the Cancel button to abort this
command while the process is running.
BSC software installation: the new software package is automatically
installed, when this command is launched.
BSC software activation: this command activates automatically the new
software after downloading and installation.
Verification: physical and logical tools are provided through the TML, to check
the disk structure and to perform a read/write test on each disk sector.
MMS Scan disk: a physical verification is performed on the MMS
modules. If an error is detected, error rates are directly displayed on the
main screen, above the faulty MMS module.
V14.00/EN
117
June 2003
TML e3
14 - Miscellaneous Menu
V14
Miscellaneous Menu
Save Log File window
118
The Miscellaneous Menu enables specific commands.

Save log File: the user can save (in a text format), a test session log file
containing all past commands and their results. The user can browse in the TML
PC file system to define the target directory and the file name. By clicking on the
save button, the file containing the test session is created in the TML file
system.
V14.00/EN
118
June 2003
TML e3
15 - View Menu
V14
View Menu
Result Window
119
The View Menu displays the result windows, the BSC directory containing the
notification files and the BSC directory software error file.
Result view: displays the Summary window presenting all past commands and
their results.
Software error view: displays the BSC e3 error log file directory.
V14.00/EN
119
June 2003
Section 8
BSC e3 and TCU e3
Module Replacement
whatsoever.
V14.00/EN
120
June 2003
Objectives
After completion of this section, the students will be

able to:
Know about the safety instructions
Perform the replacement of these faulty modules.
V14.00/EN
121
121
June 2003
Contents
Safety Instructions
Extraction/Insertion of a Module
Location of Modules inside the Cabinets
Module Replacement Procedures
V14.00/EN
122
122
June 2003
Safety Instructions
123
The BSC e3 and TCU e3 are:

Hot Swap (a switch between active/passive modules can be performed without
any interruption of service).
Plug and Play (cards can be added/removed at any time without powering
down).
This chapter gives the replacement procedure of each FRU (Field Replaceable Unit) of
the BSC e3/TCU e3.
These procedures do not require the equipment shutdown.
CAUTION: use a replacement module with the same PEC code, to avoid equipment
malfunction.
V14.00/EN
123
June 2003
Extraction/Insertion of a Module
Module
Module
Extraction
Insertion
124
Intervention time: approximatively 5 to 15 minutes.

Tools required: none or a screwdriver.
Impact on Service: according to the module, the service can be lost or not.
Product Reference: all modules are referenced by a PEC code (Product Engineering
Code). It is made up of three parts: prefix, root and suffix.
The prefix is fixed: NT (Northern Telecom).
The root is made of 2 letters (QE for France Project = BSC e3 Hardware; LX for
Raleigh Project = Spectrum Hardware) plus two digits (representing a product in
the product line).
The suffix is made of two letters (for complete modules).
Location of the defective module with the LEDs status.
Extraction of the defective module: never extract a module when the redundant one is
not ready to take over (the green LED must be lit).
Insertion of the new module.
Self-test on the module: wait until the module performs a self-test. The selftest is
complete when the green LED remains on and the red LED remains off. If both LEDs
stay on for an extended period of time, the replacement module may be defective;
remove the module and replace it with another one.
Note
Check that the event hardware insertion has been created by the OMC (except for the
TIM module or for the SIM module).
V14.00/EN
124
June 2003
Location of Modules
Inside the BSC e3 Cabinet
Equipment Type
Location
Equipment Number
OMU Module
Control Node
Dual-shelf 01, Shelf 01
(5, 6) or (9, 10)
Private MMS Module
Control Node
5 and 10
Shared MMS Module
Control Node
6&9
7 & 8 for private MMS duplication
ATM-SW Module
Control Node
7 or 8
ATM-RM Module
Interface Node
5 or 6
TMU Module
Control Node
Dual-shelf 01, Shelf 00 or 01
Shelf 00 (1, 3, 4, 11, 12, 13, 14) or

Shelf 01 (1, 3, 4, 11, 12, 13, 14)
CEM Module
Interface Node
7 or 8
8K-RM Module
Interface Node
9 or 10
IEM Module
Interface Node
Dual-shelf 00 , Shelf 00 or 01
Shelf 00 (1, 3, 4, 6, 12, 14) or

Shelf 01 (2, 4, 8, 10, 11, 13)
TIM Module
Interface Node
Dual-shelf 00, Shelf 00 or 01
Shelf 00 (2, 5, 13) or

Shelf 01 (3, 9, 12)
SIM Module
Control Node, Interface Node

Dual-shelf 00 or 01, Shelf 00
or 01
15
Fan Unit
1, 2, 3, 4
Air Filter Assembly
V14.00/EN
125
125
June 2003
Location of Modules
Inside the TCU e3 Cabinet
Equipment Type
TRM Module
Location
Equipment Number
Transcoder Node
Dual-shelf 00 or 01
Shelf 00 (1, 2, 3, 9,
10, 11, 12, 13, 14) or
Shelf 00 or 01
Shelf 01 (5, 6, 14)
Transcoder Node
CEM Module
Dual-shelf 00 or 01
7, 8
Shelf 00
IEM Module
Transcoder Node
Shelf 00 (4, 6) or
Dual-shelf 00 or 01
Shelf 01 (2, 4, 8, 10,

11, 13)
Shelf 00 or 01
Transcoder Node
TIM Module
Dual-shelf 00 or 01
Shelf 00 or 01
Shelf 00 (5) or
Shelf 01 (3, 9, 12)
Transcoder Node
SIM Module
Dual-shelf 00 or 01
15
Shelf 00 or 01
V14.00/EN
126
126
June 2003
Module Replacement Procedure

1 - General Points
State of the LEDs located on the front panel of the modules
Green
LED
Red LED
Action
Faulty
Module
Press the lamp test

button: if both
LEDs turn on, then
NO
If both LEDs remain on

after the end of the
self-test, then
YES

both LEDs turn on,
then
NO
---
YES
127
Location of the faulty module: the OMC-R has given the shelf number and the logical
slot number of the faulty module.
State of the LEDs located on the front panel of the module:
Green LED OFF and red LED OFF: press the lamp test button (located on the
front panel of the cooling unit). If both LEDs turn on, the module is not faulty.
Green LED ON and Red LED ON: wait the end of the self-test (if any). If both
LEDs still remain ON, the module is faulty.
Green LED ON and red LED OFF: press the lamp test button (located on the
front panel of the cooling unit). If both LEDs turn on, the module is not faulty.
Green LED OFF and Red LED ON: the module is faulty.
Check-up of the LED status after module insertion:
At first, both Green and Red LEDs turn ON (during the self-test).
After a time, the Red LED turns OFF and the Green LED remains ON. Thus, the
module is operational.
After another time (about 15 to 20 minutes), the Green LED turns OFF (it turns
to sleep mode which allows LED life to be prolonged).
V14.00/EN
127
June 2003

2 - OMU Module
Product Reference:
128
PEC code: NTQE03AA
Tools required: none.

Impact on Service: none ( 1+1 hot stand-by redundancy).
Extraction of an OMU module: two cases can occur
The module is faulty (Red LED ON). It can be extracted without pressing the
removal push button.
The module is not faulty (Red LED OFF). The operator must first isolate the
module hard disk by pressing the "Removal request push button. After about 15
minutes, the Green LED turns OFF, then the Red LED begins to flicker: from
this moment, it is possible to extract the OMU module during a 15 minutes
period. At the end of this period, if the OMU module has not been replaced, it is
automatically brought back into service.
Insertion of a new OMU module:
Before inserting a new OMU module, always extract the corresponding private MMS
module from its slot, and re-insert it. This helps the MMS module to reset properly and
avoid a blocking state.
V14.00/EN
128
June 2003

3 - Private MMS Module
Product Reference:
129
PEC code: NTQE05AA
Impact on Service: none (one private MMS per OMU). If the private MMS is extracted, then the
OMU is out of service.
Update the spare module with the content of the active private MMS disk:
Insert the new MMS module into the slot 7 or 8 of the shelf 00
At first both green and red LEDs turn on (self-test)
Then the content of the active MMS module is duplicated on the MMS module. When the
green LED turns off and the red LED begins to flicker, the duplication is completed
Insert the MMS at its right position (slot 5 or 10, shelf 00).
Extraction of an MMS module: two cases can occur
The module is faulty (Red LED ON): extract it without pressing the removal push button.
The module is not faulty (Red LED OFF). The operator must first isolate the module by
pressing the Removal request push button. After few minutes, the Green LED turns off,
then the Red LED begins to flicker: from this moment, it is possible to extract the MMS
module.
Abort Procedure: if the module was not faulty, and if it is not extracted during the 15
minutes following the Red LED flickering, the module automatically returns back into
service.
Insertion of the updated MMS module:
Insert the updated module into the slots 5 or 10 of the shelf 00. Both green and red
LEDs turn on.
These LEDS remain on while the corresponding OMU boots during a few minutes.. Then
only the green LED remains on.
V14.00/EN
129
June 2003

4 - Shared MMS Module
Product Reference:
130
PEC code: NTQE05AA

Impact on Service: none (1+1 mirrored for the shared MMSs). These two modules work
in parallel.
Extraction of an MMS module: two cases can occur
The module is faulty (Red LED ON). It can be extracted without pressing the
removal push button.
The module is not faulty (Red LED OFF). The operator must first isolate the
module hard disk by pressing the "Removal request push button. The CN stops
to duplicate the content of the shared disks files on this MMS module, and
isolates the Bus. After few minutes, the Green LED turns OFF, then the Red
LED begins to flicker: from this moment, it is possible to extract the MMS
module during a 15 minutes period. At the end of this period, if the MMS module
has not been replaced, it is automatically brought back into service.
Insertion of a new MMS module:
When the new MMS module is inserted, both Red and Green LEDs turn on.
Then the content of the remaining shared MMS is duplicated on the new shared
one. This takes few minutes, during which both LEDs remain on.
The module is operational when only the green LED remains on.
V14.00/EN
130
June 2003

5 - ATM-SW Module
Product Reference:
131
PEC code: NTQE06AA

Impact on Service: none (1+1 in parallel work).
Extraction of an ATM-SW module:
First remove the optical fibers from each optical connector
Then replace the ATM -SW module
Finally, re-insert the optical fibers on the new module. Note that:
The TX connector (coming from the ATM -RM module) is connected to
the RX connector on the ATM -SW module;
the RX connector (coming from the ATM -RM module) is connected to
the TX connector on the ATM-SW module.
Insertion of an ATM-SW module: No special remark.
V14.00/EN
131
June 2003

6 - ATM-RM Module
M
AT W
S
Tx
Rx
+
Optical
Attenuator
Attenuator
M
AT M
R
Tx
Rx
Product Reference:
132
PEC code: NTLX73BA

Impact on Service: none (1+1 in parallel work).
Extraction of an ATM-RM module:
First remove the optical fibers from each optical connector
Then replace the ATM -RM module
Finally, re-insert the optical fibers on the new module. Note that:
The TX connector (coming from the ATM -SW module) is connected to
the RX connector on the ATM -RM module;
the RX connector (coming from the ATM -SW module) is connected to
the TX connector on the ATM-RM module.
Insertion of an ATM-RM module: No special remark.
Notes
An external optical Attenuator is connected on the TX side of the ATM -RM fiber. Dont
forget to use it, or the equipment may be damaged.
The ATM-SW in the slot 7 is connected to the ATM-RM in the slot 5.
The ATM-SW in the slot 8 is connected to the ATM-RM in the slot 6.
V14.00/EN
132
June 2003

7 - TRM Module
Product Reference:
133
PEC code: NTQE08AA

Impact on Service: none (n+p redundancy per dual-shelf).
In case of TRM failure, the traffic managed by this board is lost.
Extraction of an TRM module: No special remark.
A period of 15 minutes minimum must be respected between the insertion and the
extraction of the same type of boards, in order not to loose service.
Insertion of an TRM module: No special remark.
V14.00/EN
133
June 2003

8 - TMU Module
Product Reference:
134
PEC code: NTQE04AA

Impact on Service: none (n+p redundancy per dual-shelf).
In case of TMU failure, all the communications which are not in a steady state may be
lost (communication in progress or Handover).
Extraction of a TMU module:
When a TMU board is extracted, the Load Balancing function is activated, and a reorganization of the traffic load over the remaining boards is done.
If a second board is extracted before the end of this re-organization, the traffic may be
lost.
Insertion of a TRMUmodule: No special remark.
V14.00/EN
134
June 2003

9 - CEM Module
Product Reference:
135
PEC code: NTLX82AA

Impact on Service: none (1+1hot stand-by redundancy per dual-shelf).
Extraction of an CEM module: No special remark.
Insertion of an CEM module: No special remark.
V14.00/EN
135
June 2003

10 - 8K RM Module
Product Reference:
136
PEC code: NTQE07AA

Impact on Service: none (1+1 redundancy per dual-shelf).
Extraction of an 8K-RM module: No special remark.
Insertion of an 8K-RM module: No special remark.
V14.00/EN
136
June 2003

11 - Boards of the LSA-RC Module
Front Panel
View for PCM
E1 links
Product Reference: for IEM (E1)
137
PEC code: NTLX89AA
for IEM (T1)
PEC code: NTLX89DA
for TIM (E1/T1)
PEC code: NTLX92AA
Impact on Service: none (1+1 redundancy).

Display of the SPAN# LEDs:
Blank on the inactive IEM.
The faulty span number on the active IEM.
XX on the active IEM where there is a problem with the copper connection
between the IEM and the SAI frame.
OK on the active IEM when there are no signal failures on the spans.
Extraction of an IEM module: do not extract simultaneously both IEM modules located
on the LSA no. 0, or the synchronization inside the equipment will be lost.
Insertion of an IEM module: No special remark.
Extraction of an TIM module: DO NOT EXTRACT the TIM module or all the traffic will
be lost.
V14.00/EN
137
June 2003

12 - SIM Module
Product Reference:
138
PEC code: NTLX61AA
Tools required: screwdriver.

Impact on Service: none (1+1 redundancy).
There are 2 SIMs per equipment: each SIM contributes to supply each shelf (at 50%
level). When one SIM is in default, the other one supplies totally the Node. Extracting
this SIM modules causes a shut-down of the equipment.
Extraction of a SIM module:
When the equipment is shut down, for safety reasons, wait minimum 15 seconds before
extracting any SIM module. Some big capacitors need 15 seconds to be completely
discharged, to ensure a proper reset of the module.
Insertion of an SIM module: No special remark.
Same as previous. Wait minimum 15 seconds between the moment where the
equipment has been shut down and the moment where it is powered again.
V14.00/EN
138
June 2003

13 - Fan Unit
unused
Product Reference:
139
PEC code: NTLX56AA
Tools required: screwdriver.

Impact on Service: none (still operational with 3 fan units).
CAUTION:
All fan slots must be equipped with fan unit assemblies to maintain EMI integrity
and to maintain shelf airflow patterns to ensure proper cooling.
Do not have the equipment run with any empty fan unit slot.
WAIT UNTIL THE FAN STOPS SPINNING before extracting it.
V14.00/EN
139
June 2003

14 - Air Filter
Product Reference:
140
PEC code: NTLX5015

Impact on Service: none.
Extraction of an Air-filter: No special remark.
Insertion of an Air-filter: No special remark.
V14.00/EN
140
June 2003
Student notes
V14.00/EN
141
June 2003

BSCe 3

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

BSCe 3

Enviado por

Direitos autorais:

Formatos disponíveis

BSC e3 and TCU e3

Copyright 2003Nortel Networks, All Rights Reserved

BSC e3/TCU e3 Local Maintenance

"Confidential information -- may not be copied or disclosed without permission".

BSC e3/TCU e3 Local Maintenance

BSC e3 and TCU e3 Architecture

BSC e3 and TCU e3 Board Description

Thermic, Energetic and Cabling Aspects

Hardware Features and Configuration

BSC e3 and TCU e3 Startup

BSC e3 and TCU e3 Troubleshooting

BSC e3 and TCU e3 Module Replacement

"Confidential information -- may not be copied or disclosed without permission".

BSC e3/TCU e3 Local Maintenance

OML14 BSC e3 and TCU e3

"Confidential information -- may not be copied or disclosed without permission".

BSC e3/TCU e3 Local Maintenance

"Confidential information -- may not be copied or disclosed without permission".

BSC e3/TCU e3 Local Maintenance

GSM/GPRS/UMTS TRAINING C URRICULUM

BSS NORTEL T ECHNICAL P UBLICATIONS

2. BSC E3 AND TCU E3 FUNCTIONAL ARCHITECTURE

BSS IN THE GSM NETWORK

BSC E3 AND TCU E3 E XTERNAL LINKS

BSC E3 AND TCU E3 MIXED SYSTEM ARCHITECTURE

BSC E3 AND TCU E3 P RESENTATION

FUNCTIONAL A RCHITECTURE OF A TRANSCODING NODE

"Confidential information -- may not be copied or disclosed without permission".

BSC e3/TCU e3 Local Maintenance

3. BSC E3 AND TCU E3 BOARD DESCRIPTION

MEMORY MASS S TORAGE

MINIMAL C ONFIGURATION FOR THE C N

MINIMAL C ONFIGURATION FOR THE IN

MINIMAL C ONFIGURATION FOR THE T N

"Confidential information -- may not be copied or disclosed without permission".

BSC e3/TCU e3 Local Maintenance

4. THERMIC, ENERGETIC AND CABLING ASPECTS.

POWER S UPPLY AND ALARMS SYSTEMS

LOCATION OF THE COOLING & F AN U NITS

COOLING & F AN U NITS

BSC E3/TCU E3 CABLING

BSC E3 O PTICAL FIBER C ABLING

PCM CABLING BETWEEN SAI & LSA-RC

PCM CABLING: CONNECTION LAS-RC/CTU

PCM CABLING: CTU CONNECTIONS

48 V DC & ALARMS C ABLING

BSC E3 A LARM CABLING

TCU E3 A LARM CABLING

BSC E3/TCU E3 FUSES

5. HARDWARE FEATURES, CONFIGURATION & DIMENSIONING

BSC E3 &TCU E3 C ONFIGURATIONS

MIN & MAX C ONFIGURATIONS

BSC E3 & TCU E3 TYPICAL CONFIGURATIONS

BSC E3 C ONFIGURATION EXAMPLES

"Confidential information -- may not be copied or disclosed without permission".

BSC e3/TCU e3 Local Maintenance

6. BSC E3/TCU E3 STARTUP

BSC STARTUP AT THE OMC-R

COLD S TARTUP (MIB

CONTROL NODE S TARTUP

D EAD O FFICE RECOVERY

CN C OMPLETE S TARTUP S EQUENCE