Huawei - BSC6900 & BTS3900

GSM Principles
www.huawei.com
Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.
Objectives
Upon completion of this course, you will be able to:

Grasp basic idea of GSM system such as frequency spectrum,

frequency reuse etc.
Grasp the structure of the GSM system and the protocol used.
Grasp certain numbers that refer to BSS
Grasp the 4 kinds of channel combination and understand the idea

of multi-frame.
Know some radio techniques
Get the idea of EDGE
Page1
References
BSS Feature Description
BSS Signaling Analysis Manual
BSC Technical Manual
Page2
Contents
1. GSM System Overview
2. GSM Network Structure
3. Service Area and Number Planning
4. Channels on the Wireless Interface
5. Radio Techniques
6. GPRS & EDGE Introduction
Page3
Contents
5. Radio Techniques
Page4
GSM system overview

The GSM system is a frequency- and time-division cellular system,

each physical channel is characterized by a carrier frequency and a
time slot number
Cellular systems are designed to operate with groups of low-power

radios spread out over the geographical service area. Each group of
radios serve MSs presently located near them. The area served by each
group of radios is called a CELL
Uplink and downlink signals for one user are assigned different
frequencies, this kind of technique is called Frequency Division Duplex
(FDD)
Data for different users is conveyed in time intervals called slots ,

several slots make up a frame. This kind of technique is called Time
Division Multiple Access (TDMA)
Page5
GSM Development
1989
Standard Protocol for GSM take effect
1991
GSM system began to provide service in Europe(2G)
1992
System was named as Global System for

Mobile Communication
1994
Provide services for the whole world
1996
Micro Cell Technique is used in GSM system
Page6
Cell Technique
Macro Cell and Micro Cell

A certain radio coverage area formed by a set of transceivers that

connected to a set of antennas is called a CELL.
Macro Cell
In the beginning , High-Power BTSs are adopted to provide services. The

BTS covers a wider area , but its frequency utilization is not efficient. So , it
can only provide a few channels for subscribers.
Micro Cell
Later the Low-Power BTS joins the system for getting a better service area
with high capacity . At the same time it adopts the frequency reuse
technique to improve the efficiency of the frequency utilization and also the
whole capacity of the network.
Page7
Multiple Access Technique

Multiple Access Technique allows many subscribers to

use the same communication medium.
There are three kinds of basic Multiple Access Technique :

FDMA , TDMA and CDMA.
GSM system adopt FDD-TDMA (FDMA and TDMA

together).
Page8
FDMA
FDMA uses different frequency

channels to accomplish
communication.
Frequency
The whole frequency spectrum

available is divided into many
individual channels (for
transmitting and receiving)
every channel can support the
traffic for one subscriber or some
Time
control information.
Page9
TDMA
TDMA accomplishes the

communication in different
timeslot.
Frequency
A carrier is divided into

channels based on time.
Different signals occupy
different timeslots in certain
sequence , that is , many
signals are transmitted on the
Time
same frequency in different

time.
Page10
CDMA
CDMA accomplishes the

communication in different code
sequences.
Frequency
Special coding is adopted before

transmission, then different
information will lose nothing
after being mixed and
transmitted together on the
same frequency and at the same
time.
Time
Page11
The Frequency Spectrum

GSM 900
Uplink
890
Downlink
915
935
960MHz
Duplex Separation:
Channel Bandwidth:
45MHz
200KHz
Page12

DCS 1800
Base Station Receive
1710
Base Station Transmit
1785 1805
Duplex Separation:
Channel Bandwidth:
1880MHz
95MHz
200KHz
Page13

Frequency
Point
Available
Downlink
Frequency
Fu(n)=450.6+0.2(n259)
259<=n<=293
Fd(n)=Fu(n)+1
0
478.8~486
488.8~496
Fu(n)=479+0.2(n-306)
306<=n<=340
Fd(n)=Fu(n)+1
0
GSM 850
824~849
869~894
Fu(n)=824.2+0.2(n128)
128<=n<=251
Fd(n)=Fu(n)+4
5
E-GSM
900
880~915
925~960
0<=n<=124
Fu(n)=890+0.2n
975<=n<=102
Fu(n)=890+0.2(n-1024)
3
Fd(n)=Fu(n)+4
5
R-GSM
900
876~915
921~960
0<=n<=124
Fu(n)=890+0.2n
955<=n<=102
Fu(n)=890+0.2(n-1024)
3
Fd(n)=Fu(n)+4
5
PCS 1900
1850~1910
1930~1990
Frequency
Spectrum
Range
(MHz)
GSM 450
450.4~457.
6
460.4~467.
6
GSM 480
Uplink Frequency
Fu(n)=1850.2+0.2(n512)
512<=n<=810
Fd(n)=Fu(n)+8
0
Page14
Frequency Reuse
The frequency resource of mobile system is very limited.
The different Subscribers can use the same frequency in

different places.
The quality of communication must be ensured.
Page15
Frequency Reuse
7(Site)X 1(Cell) reuse
2
7
23
1
4
5
Page16
Frequency Reuse
7
11
6
2
10
4
12
4 site X 3 cells reuse
Page17
Cell Types
Omni
Omni-directional
Omni-directional Cell
Cell
1
1
120 Degree Cell
120
degree
3
Page18
Contents
5. Radio Techniques
Page19
GSM-GPRS Network Component

MSC/VLR
PSTN
ISDN
GMSC
GSM /GPRS BSS

BSC
MS
HLR/AUC
BTS
PCU
SS7
BSC
SMS system
MS
BTS
Internet,
Intranet
GPRS Backbone
SGSN
GGSN
OMC
CG
BG
Other PLMN
Page20
Interface Between Different Entities

MSC/VLR
PSTN
ISDN
GMSC
GSM /GPRS BSS

Abis
MS
BSC
A
HLR/AUC
BTS
C/D/Gs
PCU
BSC
SS7
Gb
MS Um
SMS system
Gr/Gs/Gd/Ge
Gc
BTS
GPRS backbone
SGSN
Gi
GGSN
Ga
OMC
CG
Internet,
Intranet
BG
Gp
Page21
Other PLMN
Mobile StationMS
MS=ME+SIM
MS=ME+SIM
International Mobile Equipment Identity

(IMEI)
Mobile Equipment
International Mobile Subscriber Identity (IMSI)
Subscriber Identity Module
Page22
Subscriber Identity Module SIM

International Mobile Subscriber

Identity (IMSI)
Temporary Mobile Subscriber
SIM
Identity (TMSI)
Location Area Identity (LAI)
Subscriber Authentication Key (Ki)
Page23
Base Station Subsystem BSS

The Base Station Controller
MSC
BSC
The Base Transceiver Station
BSS
BTS
TC/SM
TC/SM
The Trans-coder TC and

Sub multiplexer (SM)
BSC
BSC
BTS
BTS
Page24
Packet Control Unit-----PCU

Packet data
MSC
switching
Bridge between
SGSN and BSC
Provide Pb and Gb
interface
BSS
TC/SM
TC/SM
BSC
BSC
GPRS
Backbone
PCU
PCU
BTS
BTS
Page25
SGSN
SGSN
The Network Switching System

AUC
AUC
HLR
HLR
EIR
EIR
NSS
OMC
EC
EC
MSC/VLR
MSC/VLR
Mobile-service Switching Center

Home Location Register
Visitor Location Register
Equipment Identity Register
Authentication Center
Echo Cancellor
MSC
HLR
VLR
EIR
AUC
EC
BSS
Page26
Mobile-service Switching Center

MSC
Call Processing
Operations and Maintenance Support
Interface management
Inter-network & Inter-working
Billing
Page27
PSTN
Home Location Register HLR

Subscriber ID (IMSI and MSISDN)
Current subscriber VLR (current location)
Supplementary service information
Subscriber status (registered/deregistered)
Authentication key and AuC functionality
Page28
Visitor Location Register VLR

Mobile Status (IMSI attached / detached / busy / idle etc.)
Location Area Identity(LAI)
Temporary Mobile Subscriber Identity(TMSI)
Allocating the Roaming Number
Page29
Equipment Identity Register EIR

White List
Black List
Grey List
IMEI is Checked In White List
If NOT found
EIR focus on the
equipment , not the
subscriber!
IMEI is Checked in Black/Grey List
Page30
OMC Functional Architecture

Security
Management
Event/Alarm
Management
MMI
OS
DB
Fault
Management
Configuration
Management
Performance
Management
Page31
Contents
5. Radio Techniques
Page32
Service Area
Service Area
PLMN
PLMN service
service area
area
MSC service area...
PLMN service area

MSC service area...
Location area...
Location area...
cell
cell
Page33
......
LAI
MCC
MNC
LAC
Location Area Identification
The LAI is the international code for a location area.

MCC: Mobile Country Code
It consists of 3 digits .
For example: The MCC of China is "460"
MNC: Mobile Network Code
For example: The MNC of China Mobile is "00"
LAC: Location Area Code
It is a two bytes hex code.
The value 0000 and FFFF is invalid.
For example: 460-00-0011
Page34
CGI
CGI: Cell Global Identification
The CGI is a unique international identification for a cell

The format is LAI+CI
LAI: Location Area Identification
CI: Cell Identity. This code uses two bytes hex code to
identify the cells within an LAI.
For example : 460-00-0011-0001
Page35
BSIC
BSIC
Base Station Identification Color Code)
NCC
BCC
BSIC
NCC: PLMN network color code. It comprises 3 bit. It

allows various neighboring PLMNs to be
distinguished.
BCC: BTS color code. It comprises 3 bit, used to
distinguish different cells assigned the same
frequency!
Page36
MSISDN
CC
NDC
SN
National (significant)
Mobile number
Mobile station international
ISDN number
CC: Country Code. For example: The CC of China is "86".

NDC: National Destination Code. For example: The NDC of
China Telecom is 139, 138, 137, 136, 135.
SN: Subscriber Number. Format:H0 H1 H2 H3 ABCD
Example: 86-139-0666-1234
Page37
IMSI
Not more than 15 digits
3 digits
2 digits
MCC
MNC
MSIN
NMSI
IMSI
For example: The MCC of China is "460"

For example: The MNC of China Telecom is "00"
MSIN: Mobile Subscriber Identification Number. H1H2H3 S ABCDEF

For example: 666-9777001
NMSI: National Mobile Subscriber Identification
MNC and MSIN
form it together.
For Example of IMSI : 460-00-666-9777001
Page38
TMSI
TMSI: Temporary Mobile Subscriber Identification)
The TMSI is assigned only after successful subscriber

authentication.
The VLR controls the allocation of new TMSI numbers

and notifies them to the HLR.
TMSI is used to ensure that the identity of the mobile

subscriber on the air interface is kept secret.
The TMSI consists of 4 bytes( 8 HEX numbers) and

determined by the operator.
Page39
IMEI
IMEI: International Mobile Station Equipment Identification
TAC
FAC
SNR
SP
IMEI
TAC:
TAC: Type
Type approval
approval code,
code, 66 bit,
bit, determined
determined by
by the
the type
type approval
approval center
center
FAC:
Final
assembly
code,
2
bit,
It
is
determined
by
the
manufacturer.
FAC: Final assembly code, 2 bit, It is determined by the manufacturer.
SNR:
SNR: Serial
Serial number,
number, 66 bits,
bits, ItIt isis issued
issued by
by the
the manufacturer
manufacturer of
of the
the MS.
MS.
SP:
1
bit
,
Not
used.
SP: 1 bit , Not used.
Check
Check the
the IMEI
IMEI in
in your
your MS
MS :: *#06#
*#06#
Page40
Contents
5. Radio Techniques
Page41
Physical Channel and Logical Channel

The physical channel is the medium over which the
information is carried: 200KHz and 0.577ms
The logical channel consists of the information carried
over the physical channels
1 2
Timeslot
3 4
5 6
7 0
1 2
The
Theinformation
informationcarried
carriedin
inone
onetime
time
slot
is
called
a
burst
slot is called a burst
TDMA FRAME
TDMA FRAME
Page42
Two types of Logical Channel

Traffic Channel (TCH) :
Transmits traffic information, include data
and speech.
Control Channel (CCH) :

Or Signaling Channel, transmits all kinds of
control information.
Page43
Traffic Channel (TCH)

TCH
Traffic Channels
Speech
Data
TCH/HS
TCH/FS
TCH/9.6
TCH Traffic Channel

TCH/FS Full rate Speech Channel
TCH/HS Half rate Speech Channel
TCH/9.6 Data Channel 9.6kb/s
TCH/4.8 Data Channel 4.8kb/s
TCH/2.4 Data Channel 2.4Kb/s
TCH/2.4
TCH/4.8
Page44
Control Channel (CCH)

CCH (Control Channels)
DCCH
SDCCH
FACCH
BCH
ACCH
BCCH
SACCH
Broadcast Control Channel BCCH

Common Control Channel CCCH
Dedicated Control Channel DCCH
Associated Control Channel ACCH
Synch. CH.
CCCH
SCH
RACH
CBCH
PCH/AGCH
Page45
FCCH
Broadcast Control Channel

BCCH
CCH
The information carried on the BCCH

is monitored by the MS
BCH
periodically when it is in idle mode

BCCH: Broadcast Control Channel
FCCH: Frequency Correction Channel
BCCH
Synch.
Channels
SCH
FCCH
SCH: Synchronization Channel
Page46
Common Control Channel CCCH

CCH
The CCCH is responsible for

transferring control information
between all mobiles and the
network.
CCCH
RACH: Random Access Channel

PCH: Paging Channel
AGCH: Access Granted Channel
CBCH: Cell Broadcast Channel
RACH
uplink
CBCH
downlink
PCH/AGCH
downlink
Page47
Dedicated Control Channel

DCCH
CCH
DCCH is assigned to a single

wireless connection for
measurement and handover
purpose.
SDCCH: Stand-alone Dedicated
Control Channel
ACCH: Associated Control Channel
SACCH: Slow Associated
Control Channel
FACCH: Fast Associated Control
Channel
DCCH
SDCCH
FACCH
ACCH
SACCH
Page48
Uplink Logical channel

CCH
RACH
CCCH
SDCCH
SACCH
DCH
DCCH
FACCH
TCH/F
TCH/H
TCH
Page49
Downlink Logical channel

FCCH
CCH
BCCH
SCH
BCCH
CCCH
PCH
AGCH
SDCCH
DCH
DCCH
SACCH
FACCH
TCH
TCH/F
TCH/H
Page50
How to use these channels?

Power-off
Search for frequency correction burst
FCCH
SCH
BCCH
Search for synchronous burst

Extract system information
Idle mode
Monitor paging message
PCH
RACH
AGCH
SDCCH
SDCCH
TCH
FACCH
Send access burst

Allocate signaling channel
Dedicated mode
Set up the call

Allocate voice channel
Conversation
Idle mode
Release the call
Page51
Packet logic channel

Packet data channel (PDCH)

TCH
Comprising packet service channel and packet control

channel
TCH
Packet service channel (PDTCH)

Combined into the single-directional service channel

BCCH
CCCH
Packet control channel
SACCH
Broadcast control channel: PBCCH
Public control channel: PPCH, PRACH, PAGCH
Private control channel: PACCH, PTCCH
Page52
GSM Logical Channel Combination

Main BCCH combination FCCH + SCH + BCCH + CCCH
SDCCH combination SDCCH/8 + SACCH/8
Combined BCCH BCCH + CCCH +SDCCH/4 + SACCH/4
TCH/FR combination TCH/F + FACCH/F + SACCH/F
TCH/HR combination TCH/H + FACCH/H + SACCH/H
Page53
Combination of packet logic

channel
Packet logic channels (PDCH) can be combined via the

following three modes
Mode 1: PBCCH+PCCCH+PDTCH+PACCH+PTCCH;
Mode 2: PCCCH+PDTCH+PACCH+PTCCH;
Mode 3: PDTCH+PACCH+PTCCH
In case of small GPRS traffic, GPRS and circuit services use the
same BCCH and CCCH in the cell. In this case, only combination
mode 3 is needed in the cell
With the increase of traffic, the packet public channel should

be configured in the cell. Channel combination mode 1 and
mode 2 should be adopted
Page54
GSM Multi-frames
TDMA Frames
0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
46 47 48 49 50
51 Frame Multi-frames
CONTROL
CHANNELS
Page55
GSM Multi-frames
TDMA Frames
0
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
0 1 2 3 4
21 22 23 24 25
26 Frame Multi-frames
TRAFFIC
CHANNELS
Page56
Contents
5. Radio Techniques
Page57
Power Control
Both Uplink and Downlink
power
settings
can
be
controlled independently and
individually.
5W
0.8W
Saves battery power

Reduces co-channel and
adjacent channel interference
8W
BCCH ------Does not attend Power

control
Page58
DTX and VAD

Discontinuous Transmission DTX
Voice Activity Detection VAD
Battery Saving
Interference reduction
Page59
Timing Advance (TA)

The mobile phone should
send the signal in advance!
TA
Transmission delay t
Transmission delay t
Page60
Multi-path Fading
Diversity
Frequency Hopping
Time Dispersion
Page61
Diversity Whats Diversity?

Receive diversity provides an effective technique for both

overcoming the impact of fading across the radio channel
and increasing the received signal to interference ratio.
The former is achieved by ensuring uncorrelated (i.e.

low enough correlated) fading between antenna
branches i.e. not all antennas experience fades at the
same time.
Page62
Kinds of Diversity
Time diversity
Coding, interleaving
Frequency diversity
Frequency hopping
Space diversity
Multiple antennas
Polarization diversity
Dual-polarized antennas
Multi-path diversity
Equalizer
Page63
Frequency Hopping
Frequency
f0
f1
f2
f3
f4
Frame
Time
Page64
Contents
5. Radio Techniques
Page65
GSM Development Evolution

3G
2.5G
2Mbps
EDGE
115 kbps
2G
57.6 kbps
9.6 kbps
IMT-2000
384kbps
GPRS
HSCSD
GSM
Page66
Data rate of EDGE and GPRS

Kbps
59.2
60.0
54.4
50.0
GPRS
EGPRS
40.0
44.8
29.6
30.0
22.4
21.4
20.0
13.4
10.0
17.6
15.6
14.8
9.0
8.8
11.2
0.0
CS-1
CS-2
CS-3
CS-4
MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
GMSK
8PSK
Page67
Huawei EDGE Test Result

Downlink, 4 TS, MCS-9
Page68
Page69
BSC6900 GSM V900R013

Product Description
www.huawei.com
Foreword
The BSC6900 is an important network element (NE) of

Huawei Single RAN solution. It adopts the industry-leading
multiple radio access technologies, IP transmission mode,
and modular design. It features high capacity, high
integration, excellent performance, and low power
consumption.
The BSC6900 can be flexibly configured as a BSC6900

GSM only, BSC6900 UMTS only, or BSC6900 GU as
required in different networks
Page1
References
BSC6900 GSM Product Description
BSC6900 GSM Technical Description
BSC6900 GSM Hardware Description
Page2
Objectives

Detail the functions of the components of BSC6900
Detail the hardware structure of BSC6900
Detail the signal flows in BSC6900
List the typical hardware configuration of BSC6900
Page3
Contents
1. BSC6900 System Overview
2. BSC6900 Hardware Architecture
3. BSC6900 Signal Flows
4. BSC6900 Typical Configuration
Page4
BSC6900 Position in UMTS/GSM

UTRAN/GBSS
UE/MS
CN
Uu/Um
Iu/A/Gb
BSC6900 GU
Iu-CS/A
Iub
NodeB
Ab
is
CS
Iur
BTS
Iub/Abis
MBTS
BSC6900 GU
Iu-PS/Gb
Page5
PS
Capacity
Specification
ITEM
System Capacity (Boards

Supported by BSC6900
V900R012)
System Capacity
(Boards Supported by
BSC6900 V900R013)
GSM network
Traffic (Erl)
24,000
Same
Number of cells
2,048
Same
Number of TRXs
4096
Same
Maximum number of
PDCHs to be configured
30,720
Same
Maximum number of
activated PDCHs (MCS-9)
16,384
Same
Gb interface throughput
(Mbit/s)
1,536
Same
*A multi-core board DPUf is added in the TC subrack. In BM/TC combined and allTDM mode, the number of subracks is reduced from 1MPS+3EPS to 1MPS+2EPS.
Page6
Flexible Topologies and Smooth Evolution

The BSC6900 can be flexibly configured as a BSC6900

GSM, BSC6900 UMTS, or BSC6900 GU; therefore, it is
applicable to various networking scenarios.
The BSC6900 can be configured as one of the three

variants, therefore facilitating the smooth evolution
between GSM, GSM&UMTS, and UMTS.
Page7
High Integration and Capacity of GSM

Dual Switching Planes (IP+TDM)

The IP plane supports a maximum of 240 Gbit/s switching

capacity.
The TDM plane supports a maximum of 128K128K

switching capacity.
A maximum of 16,384 active PDCHs are supported.
Maximum traffic: 24,000 Erl
Comprehensive BHCA: 5,900,000
Gb throughput: 1,536 Mbit/s
Page8
Features
Supporting GSM/UMTS dual-mode network and the all-IP

platform
Supporting dynamic data configuration and smooth

expansion of the system capacity
Supporting different types of clock sources

Line clock, BITS, GPS, external 8 kHz clock
Supporting star, chain, and tree networking with NodeBs

and BTSs
Supporting E1/T1, STM-1, FE and GE transmission
Page9
Flexible Hardware Configuration

GSM have three kinds of Hardware Configuration

BM/TC separated mode
BM/TC combined mode
A over IP mode
Page10
BSC6900 Evolution Paths

BSC6810
(UMTS)
SW upgrade with
Legacy HW + New HW
(optional)
SW upgradewith Legacy HW
+ New HW (mandatory)
BSC6900
UMTS only
BSC6900
UMTS only
BSC6900
Dual mode
BSC6900
Dual mode
SW upgradewith Legacy
HW + New UMTS HW
(mandatory)
BSC6000
(GSM)
GBSS8.1/RAN10
SW upgradewith
Legacy HW + New HW
(optional)
BSC6900
GSM only
BSC6900
GSM only
GBSS9.0/RAN11
2006
2008
GBSS12.0-13.0
2009
/RAN12-13
Page11
Dual Mode Designs

GSM&UMTS Co-cabinet
GSM&UMTS Cabinet
RNC
BSC
RNC
Software
Upgrade

RNC
BSC
RNC
RNC
BSC
BSC
Smooth evolution from BSC to RNC with software upgrade

Reducing CAPEX by reusing hardware
Dynamic capacity adjustment between 2G&3G
Page12
Feature of BSC6900-Co OAM

Unified CME:
Simultaneous 2G/3G data
configuration,
correctness, and
efficiency guaranteed
Unified WEB LMT for
maintenance:
Easy and visual maintenance of
2G/3G systems
Page13
Feature of BSC6900-Co TRM
GSM data
3G
2G
UMTS data
IP/TDM networks
Dual-mode BTS
3G
2G
GSM data
Co-TRM
Interface
board
UMTS data
BSC6900
Page14
Feature of BSC6900-Co RRM

Service direction on UMTS/GSM
Load control between UMTS/GSM

UMTSHeavy load Heavy load
UMTS
Load control
by inter-RAT HO
Voice service
Data service
GSM
The load control between GSM/UMTS improves the
service quality by directing services to different RATs
(GSM/UMTS) based on the service type.
GSM
Heavy load Heavy load
Load control between GSM/UMTS enables the

traffic to be shared between GSM and UMTS
networks. This improves network utilization.
Huawei Lab Simulation
Page15
Contents
2. BSC6900 Hardware Structure
Page16
Contents
2.1 Cabinets
2.2 Subracks
2.3 Subsystems and Boards
2.4 Cables
Page17
BSC6900 Cabinet

The BSC6900 uses the standard N68E-22 cabinet

The N68E-22 cabinet is of
two types, the single-door
cabinet and the double-
2200 mm
2200 mm
door cabinet
800
mm
800
mm
600
mm
600
mm
N68E-22 Cabinet (Singledoor/Double-door)

Page18
Components of the Cabinet

Based on functions,
cabinets are classified into
the following types:
MPR: main processing rack

EPR: extended processing rack
TCR: transcoder rack
(1) Air inlet
(2) Subrack
(3) Air defense

frame
(4) Power
distribution box
(5) Cable rack in

the cabinet
(6) Rear cable

trough
Page19
Main Processing Rack (MPR)

Only one MPR is configured in the

Power distribution box
BSC6900.
Components of the cabinet:
Main processing subrack (MPS)
Extended processing subrack (EPS)
Power consumption of a GSM MPS
EPS
EPS
MPS
1200 W
MPR
Power consumption of a GSM EPS

1200 W
Page20
Extended Processing Rack(EPR)

A BSC6900 can be configured with
one EPR or no EPR.

EPS
EPS
EPS

Extended processing subrack (EPS)
Power consumption of a GSM EPS

1200 W
EPR
Page21
TransCoder Rack (TCR)

A BSC6900 can be configured
with 0 to 2 TCRs.
TCS
TCS
TCS

Transcoder subrack (TCS)
Power consumption of a GSM

TCS 1000 W
TCR
Page22
Power Distribution Box

2 groups of -48 V inputs in 1+1 hot backup mode

6 groups of independent -48 V outputs
Subrack 2
Subrack 1
Subrack
subrack 0
(1) Power distribution
(2) Run indicator
(3) Alarm indicator
(5) Power output switch
(6) Power output switch labels
monitoring board
(4) Mute switch
Page23
Contents
2.1 Cabinets
2.2 Subracks
2.4 Cables
Page24
Subrack
436 mm
12 U
500 mm
(1) Fan box
(2) Mounting ear
(3) Guide rail
(4) Front cable trough
(5) Board
(6) Ground screw
(7) DC power input port
(8) Monitoring signal input port for

the power distribution box
(9) DIP switch
Page25
DIP Switch on the Subrack

The DIP switch on the subrack consists of eight bits from bit 1 to bit 8.
Subrack No.
0
1
2
3
4
5
Bit
1
ON
ON
ON
ON
ON
OFF
ON
ON
ON
ON
ON
OFF
ON
ON
ON
OFF
OFF
ON
ON
ON
ON
ON
OFF
ON
ON
OFF
ON
OFF
ON
ON
ON
ON
OFF
OFF
ON
OFF
OFF
ON
OFF
ON
ON
OFF
OFF
ON
OFF
ON
ON
OFF
Page26
Slots in the Subrack

The boards are installed on both the front and rear sides
of the backplane, which is located in the middle of the
subrack.
(1) Front
slot
(2) Backplane
(3) Rear
slot
Page27
GSM MPS (in BM/TC Separated Mode)

Only one MPS is configured in the BSC6900.
Rear panel
Front panel
Page28
GSM EPS (in BM/TC Separated Mode)

A BSC6900 GSM can be configured with 0 to 3 EPSs.
Rear panel
Front panel
Page29
GSM MPS (in BM/TC Combined Mode)

Rear panel
Front panel
Page30
GSM EPS (in BM/TC Combined Mode)

Rear panel
14
15
16
17
18
19
20
21
22
23
24
25
26
27
I
N
T
I
N
T
I
N
T
I
N
T
I
N
T
I
N
T
I
N
T
I
N
T
I
N
T
I
N
T
I
N
T
I
N
T
D
P
U
f
D
P
U
f
Backpl ane
Front panel
X
P
U
X
P
U
X
P
U
X
P
U
T
N
U
a
T
N
U
a
S
C
U
a
S
C
U
a
D
P
U
g
D
P
U
g
D
P
U
g
D
P
U
f
D
P
U
f
D
P
U
f
10
11
12
13
Page31
GSM MPS (in A over IP Mode)

Rear panel
Front panel
Page32
GSM EPS (in A over IP Mode)

Rear panel
Front panel
Page33
Transcoder Subrack (TCS)

A BSC6900 GSM can be configured with a maximum of four TCSs.
Rear panel
Front panel
Page34
Contents
2.1 Cabinets
2.2 Subracks
2.4 Cables
Page35
BSC6900 Logical Structure

Clock (optional)
Clock
synchronization
subsystem
To BTS/NodeB
To other BSCs/RNCs
To MSC
To SGSN
Interface
processing
subsystem
Switching
subsystem
Service
processing
subsystem
OM subsystem
LMT/M2000
Page36
Switching Subsystem
The switching subsystem performs the following

functions:
Provides data and signaling switching

Intra-subrack Media Access Control (MAC) switching
Intra-subrack Time Division Multiplexing (TDM) switching
Inter-subrack MAC and TDM switching
Provides OM channels
Distributes clock signals to each service board
Page37
Network Topologies Between Subracks

MAC switching - star topology

One node functions as the center node and it is connected

to each of the other nodes. The communication between
the other nodes must be switched by the center node.
TDM switching - mesh topology

There is a connection between every two nodes. When any

node is out of service, the communication between other
nodes is not affected.
Page38
Switching Subsystem
Structure of the MAC switching subsystem

EPS
Switching
and
control
unit
Another
board
Another
board
Switching
and
control
unit
Another
board
MPS
High-speed backplane channel

Ethernet cable
Another
board
Switching
and
control
unit
TCS
Another
board
Another
board
Page39
Switching Subsystem
Inter-subrack cable for MAC switching

EPS
MPS
EPS
SCU
SCU
SCU
SCU
SCU
SCU
Page40
SCUa Board
Functions

Provides the maintenance management function

Monitors the power supply, fans, and environment of
the cabinet

Supports the port trunking function

Provides configuration and maintenance of a subrack
or the whole BSC

Provides a total switching capacity of 60 Gbit/s

Distributes clock signals and RFN signals for the
BSC6900
Working mode

Located in slots 6 and 7

Working in dual-plane mesh topology
Page41
SCUb Board
Functions

Provides the maintenance management function

Monitors the power supply, fans, and environment of
the cabinet

Supports the port trunking function

Provides configuration and maintenance of a subrack
or the whole BSC

Provides a total switching capacity of 240 Gbit/s

Distributes clock signals and RFN signals for the
BSC6900
Working mode

Located in slots 6 and 7

Working in dual-plane mesh topology
Page42
Inter-Subrack Connections
Inter-Subrack SCUa
Interconnection Ethernet
Cable
SCUa
(Active)
SCUa
(Active)
SCUa
(Standby)
SCUa
(Standby)
Page43
Interconnections Between SCUb Boards

Inter-subrack cable
connections between
SCUb boards by
using SFP+ highspeed cables
(MPR/EPR in full
configuration,
remote TC
configuration)
Blue lines indicate

the SFP+ high-speed
cables.
Page44
Interconnections Between SCUb Boards

Inter-subrack cable
connections between
SCUb boards by using
SFP+ high-speed cables
(Local TC configuration)
Blue lines indicate the

SFP+ high-speed cables.
Green lines indicate

the unshielded
straight-through cables.
Page45
Switching Subsystem
Structure of the TDM switching subsystem

Another board
.
.
.
TDM
switching
unit
Another board
Another board
.
.
.
TDM
switching
unit
EPS
Another board
Another board
MPS
.
.
.
TDM
switching
unit
High-speed backplane
channel
TNU crossover cable
Another board
EPS
Page46
TNUa Board
Functions

Provides 128 k * 128 k TDM switching

Allocates the TDM network resources
Supports only GSM
Page47
TNUa Board
Inter-TNUa
crossover cables
between subracks
Page48
Service Processing Subsystem

The service processing subsystem performs the

following functions:
User data and signaling processing
Radio channel ciphering and deciphering
Radio resource management and control
System information and user message tracing
Page49
Service Processing Subsystem

Signaling
processing unit
Data processing
unit
Data processing
unit
Signaling
processing unit
MPS
EPS
channel
Page50
XPUa Board
The XPUa board has four logic subsystems

Main Control XPUa board (MPU)

Subsystem 0 of the main control XPUa

board is the Main Processing Unit (MPU). It
is used to manage the user plane
Main control
XPUa
resources, control plane resources, and

transmission resources of the system.
Non-Main Control XPUa Board (SPU)

Subsystems 1 to 3 of the main control

XPUa board belong to the CPU for Service
(CPUS), which is used to process the
services on the control plane.
Work mode: active and standby
Page51
Non-main control
XPUa
XPUb Board
The XPUb board has eight logical subsystems.

Main Control XPUb Board (MPU)

Subsystem 0 of the main control XPUb board

is the Main Processing Unit (MPU). It is used
to manage the user plane resources, control
Main control
XPUb
Non-main control
XPUb
plane resources, and transmission resources

of the system.
Non-Main Control XPUb Board (SPU)

Subsystems 1 to 7 of the main control XPUb

board belong to the CPU for Service (CPUS),
which is used to process the services on the
control plane.
Page52
SPUa/SPUb Board
Functions
The SPUa and SPUb boards support both GSM and UMTS.
The SPUa board has four logic subsystems, whereas the

SPUb board has eight logic subsystems. Therefore, the
processing capability of the SPUb board is higher than the
SPUa board by 75% to 100%.
Page53
SPUa Board
The SPUa board has four logic subsystems.

Main control SPUa board (MPU)

Manages the user plane resources; manages the

load sharing of the user plane resources
Main control
SPUa
Non-main control
SPUa
between subracks
Maintains the load of the control plane within the

subrack; exchanges the load information on the
control planes between subracks
Non-main control SPUa board (SPU)

Processes upper-layer signaling over the Uu, Iu,

Iur, Iub, A, Um, Abis, and Ater interfaces
Page54
SPUb Board
The SPUb board has eight subsystems.

Main control SPUb board (MPU)

Manages the user plane resources; manages

the load sharing of the user plane resources
Main control
SPUb
Non-main control
SPUb
between subracks
Maintains the load of the control plane within

the subrack; exchanges the load information
on the control planes between subracks
Non-main control SPUb board (SPU)

Processes upper-layer signaling over the Uu,

Iu, Iur, Iub, A, Um, Abis, and Ater interfaces
Page55
DPUc Board
Components
22 DSP chips
Functions
Converts the speech format and forwards data
Performs codec of voice services of 960 TCH/Fs and supports

3,740 IWF flow numbers
Provides the Tandem Free Operation (TFO) function
Provides the voice enhancement function
Detects voice faults automatically
Work mode: resource pool
Page56
DPUd Board
Components
Functions

22 DSP chips
Processes the PS services on up to 1,024 simultaneously active
PDCHs where signals are coded in MCS9
Processes packet links
Detects packet faults automatically

Supports GSM only
Page57
DPUg Board
The DPUg board has almost the same functions as the DPUd
board, whereas its capacity is higher than the DPUd board.
The DPUg board supports the same number of active PDCHs as

the DPUd board, whereas its packet service processing capability
(number of accessing subscribers) is much higher than the DPUd
board.
DPUd: Process 48 simultaneously active PDCHs (MCS9) per cell
DPUg: Process 110 simultaneously active PDCHs (MCS9) per cell
The DPUg board can process the PS services on up to 1,024

simultaneously active PDCHs where signals are coded in MCS9.
Page58
DPUf Board
Components
48 DSP chips
Functions
Converts the speech format and forwards data
Encodes and decodes voice services
Provides the Tandem Free Operation (TFO) function
Provides the voice enhancement function
Detects voice faults automatically
Supports GSM only
Page59
Clock Subsystem
CN
BITS
GPS
MPS
To
MBTS
I
N
T
I
N
T
GCUa
Clock module
8 kHz
S
C
U
a
19.44 MHz, 32.768 MHz, 8 kHz
EPS
To BTS
I
N
T
8 kHz
S
C
U
a
19.44 MHz, 32.768 MHz, 8 kHz
S
C
U
a
EPS
I
N
T
To NodeB
19.44 MHz, 32.768 MHz, 8 kHz
channel
Clock
cable
Page60
GCUa/GCGa Board
Functions
Extracts timing signals from the external synchronization

timing port and from the synchronization line signals,
processes the timing signals,
Provides the timing signals and the reference clock for the
entire system
Performs the fast pull-in and holdover functions on the

system clock
Generates RFN signals for the system
Supports active/standby switchover
Page61
GCUa/GCGa Board
Clock cable between

the GCUa/GCGa
board and the SCUa
board
Page62
Transport Subsystem-Interface Board

Board categorization
Page63
Interface Processing Subsystem

Interface board categorization

Board
Type
Transmission
Mode
Connector Type
Electrical port
Board
Supported Mode
EIUa
GSM Only
OIUa
GSM Only
POUc
GSM&UMTS
FE/GE
FG2a/FG2c
GSM&UMTS
E1
PEUa
GSM&UMTS
STM-1
POUc
GSM&UMTS
GE
GOUa/GOUc
GSM&UMTS
TDM
Optical port
INT
Electrica
l port
IP
Optical
port
Page64
EIUa Board
Functions
Transmits and receives 32 E1/T1 signals, and encodes and

decodes the E1/T1 signals
Processes signals according to the Link Access Procedure on

the D channel (LAPD) protocol and SS7 Message Transfer
Part Layer 2 (MTP2) protocol
Provides the board-level Tributary Protect Switch (TPS)

function
Provides the OM links when the TCS is configured on the

MSC side

Supports the A, Abis, Ater, and Pb interfaces

Supports 384 TRXs when serving as the Abis interface board
and supports 960 CICs when serving as the A interface board
Page65
OIUa Board
Functions
Provides one STM-1 port for TDM transmission and supports the rate of
155.52 Mbit/s

Provides the board-level Automatic Protection Switching (APS) function

Processes signals according to the Link Access Procedure on the D
channel (LAPD) protocol and SS7 Message Transfer Part Layer 2
(MTP2) protocol

Provides the OM links when the TCS is configured on the MSC side
Supports the A, Abis, Ater, and Pb interfaces
Supports 384 TRXs when serving as the Abis interface board and
supports 1920 CICs when serving as the A interface board
Page66
FG2a Board
Functions
Provides transmission of IP over Ethernet
Provides 8 channels over FE ports or 2 channels over

GE electrical ports
Provides the routing-based backup and load sharing
Provides the link aggregation function at the MAC

layer
Supports the A, Abis, Gb, Iu, Iur, and Iub interfaces
Supports 384 TRXs when serving as the Abis interface

board, supports 6144 CICs when serving as the A
interface board, and supports a maximum data flow of
128 Mbit/s when serving as the Gb interface board
Page67
FG2c Board
Functions
10M/100M/1000M
Provides transmission of IP over Ethernet
Provides 12 channels over FE ports or 4 channels over

GE electrical ports
Supports 2048 TRXs when serving as the Abis
10M/100M
interface board, supports 23040 CICs when serving as

the A interface board, and supports a maximum data
flow of 1024 Mbit/s when serving as the Gb interface
board
Page68
PEUa Board
Functions
Provides 32 channels of HDLC over E1/T1 or 32 channels of IP over

PPP/MLPPP over E1/T1
Provides 128 PPP links or 32 MLPPP groups, with each MLPPP

group containing eight MLPPP links
Provides the board-level Tributary Protect Switch (TPS) function
Transmits, receives, encodes, and decodes the 32 E1s/T1s. The E1

transmission rate is 2.048 Mbit/s; the T1 transmission rate is 1.544
Mbit/s
Supports the Abis, Gb, and Iub interfaces
Supports 384 TRXs when serving as the Abis interface board and
supports 64 Mbit/s throughput when serving as the Gb interface
board
Page69
POUc Board
Functions
Provides four channels over the channelized STM-1/OC-3c optical

ports based on TDM or IP
Supports the Point-to-Point Protocol (PPP)
Provides the line clock recovery function
Provides the board-level Automatic Protection Switching (APS)

function
Supports the A, Abis, Gb, Ater, Pb, Iur, and Iub interfaces
In TDM mode, it supports 512 TRXs when serving as the Abis

interface board in POUc over TDM mode, supports 3906 CICs when
serving as the A interface board, and supports 504 Mbit/s
throughput when serving as the Gb interface board.
In IP mode, it supports 2048 TRXs when serving as the Abis interface

board and supports 23,040 CICs when serving as the A interface
board.
Page70
GOUa Board
Functions
Provides two channels over GE ports, which are used for

IP transmission
Provides the board-level Tributary Protect Switch (TPS)

function
Supports the A, Abis, Iu, Iur, and Iub interfaces
Supports 384 TRXs when serving as the Abis interface

board and supports 6144 CICs when serving as the A
interface board
Page71
GOUc Board
Functions
Provides four channels over GE ports, which are used for IP

transmission
Supports the extraction of line clock signals
Supports 2048 TRXs when serving as the Abis interface board,

supports 23040 CICs when serving as the A interface board, and
supports a maximum data flow of 1024 Mbit/s when serving as the
Gb interface board
Page72
OM Subsystem
Intranet
Extranet
To M2000
O
M
U
O
M
U
S
C
U
a
S
C
U
a
S
C
U
a
S
C
U
a
EPS
MPS
HUB
Ethernet cable
Alarm
box
Serial port
cable
LMT
Page73
Dual OM Plane
The OMU works in active and

standby mode.
The active/standby OMU boards

use the same external virtual IP
address to communicate with the
LMT or M2000.
The active/standby OMU boards

use the same internal virtual IP
address to communicate with the
SCU boards.
Page74
OMUa/OMUb Board
The OMUa/OMUb board works as a back

administration module (BAM). It performs
the following functions:
Manages the configuration, performance,

and loading, facilitates troubleshooting,
and ensures security
Provides LMT or M2000 users with an

interface for OM of BSC6900
Page75
OMUc Board
The OMUc board works as a back

administration module (BAM) of BSC6900.
It performs the following functions:
Manages the configuration, performance,

and loading, facilitates troubleshooting,
and ensures security
Provides LMT or M2000 users with an

interface for OM of BSC6900
Difference:
An OMUc board occupies only one slot and

contains a single hard disk.
Page76
Hardware Reliability
Board
Redundancy Mode
SCUa/SCUb
Board redundancy + port trunking on GE ports
XPUa/XPUbSPUa/SPUb
Board redundancy
DPUb/DPUc/DPUd/DPUf/DPUg
Board resource pool
GCUa/GCGa
Board redundancy
AOUa/AOUc/OIUa/
UOIa/UOIc/POUa/POUc
Board redundancy + MSP 1:1 or MSP 1+1 optical port

redundancy
TNUa
Board redundancy
PEUa/AEUa/EIUa
Board redundancy
GOUa/GOUc
Board redundancy + GE port redundancy or load sharing
FG2a/FG2c
Board redundancy + GE/FE port redundancy or load

sharing
OMUa/OMUc
Board redundancy
Page77
Overall Structure
Page78
Classification of BSC6900 Boards (GSM)

OM boards: OMUa/OMUb/OMUc
Switching and control boards: SCUa/SCUb/TNUa
Clock signal processing board: GCUa/GCGa
Signaling processing board: SPUa/SPUb/XPUa/XPUb
Universal data processing board:

DPUa/DPUc/DPUd/DPUf/DPUg
Interface processing board:

EIUa, OIUa, FG2a, FG2c, GOUa, GOUc ,PEUa, POUc
Page79
Classification of BSC6900 Boards

Board
Logical Function
GCP
UCP
eXtensible
Processing Unit
(XPU)
SPUa/SPUb
RGCP
RUCP
MCP
GCP
XPUa/XPUb
RGCP
MCP
Data Processing
Unit (DPU)
DPUa/DPUc/DPUf
GTC/ITC
DPUd/DPUg
GPCU
Page80
Contents
2.1 Cabinets
2.2 Subracks
2.4 Cables
Page81
BSC6900 Cable Connections
Page82
Cables
Trunk cables:
75-ohm coaxial cables and active/standby 75-ohm coaxial cables
120-ohm twisted pair cables and active/standby 120-ohm twisted pair

cables
Ethernet cables
Optical fibers
Y-shaped clock cables
TNUa connection cables
Alarm cables
Monitoring cables
Page83
Trunk Cables
75-ohm coaxial cables/120-ohm twisted pair cables
(1) DB44 connector
(2) Main label (containing the cable code,

version, and manufacturer information)
(3) Label (identifying a coaxial

cable/twisted pair)
(4) Metallic jacket of the DB44 connector
Page84
Trunk Cables
Active/standby 75-ohm coaxial cable
(1) DB44 connector
(3) Label 1 (identifying a coaxial

cable)
(4) Main label (containing the cable code, version, and

manufacturer information)
(5) Label 2 (identifying a coaxial

cable)
Page85
Trunk Cables
Active/standby 120-ohm twisted pair cable
(1) DB44 connector
(3) Label 1 (identifying a twisted

pair cable)
(4) Main label (containing the cable code, version, and

manufacturer information)
(5) Label 2 (identifying a twisted

pair cable)
Page86
Ethernet Cables
Straight-Through Cables
Page87
Ethernet Cables
Crossover Cables
Page88
Optical Fibers
An optical fiber is used to connect the optical interface

board to the Optical Distribution Frame (ODF) or other
NEs.
*The optical cable has an LC/PC connector at one end connected to the optical
interface board in the BSC6900. The other end of the optical cable can use an LC/PC
connector, SC/PC connector, or FC/PC connector as required.
*LC/PC-LC/PC single-mode/multi-mode optical fibers can be used to connect an
optical interface board to another optical interface board as well as to the ODF or
other NEs.
In practice, two optical cables form a pair. Temporary labels are attached to both
ends of each cable in the pair. If one end of the cable is connected to the TX port,
the other end should be connected to the RX port.
Page89
Y-Shaped Clock Cables

The Y-shaped clock cable transmits 8 kHz clock signals from
the GCUa/GCGa board in the MPS to the SCUa boards in the
EPSs.
(1) Label (identifying a
(2) RJ45 connector
twisted pair cable)
Page90
Monitoring Cables for the Power

Distribution Box
The monitoring cable for the power distribution box

transmits monitoring signals from the power distribution
box to each service processing subrack.
Page91
Contents
Page92
BSC6900 GSM Signal Flows

User-Plane Signal Flow

GSM CS Signal Flow
GSM PS Signal Flow
Control-Plane Signal Flow

Signaling Flow on the A Interface
Signaling Flow on the Abis Interface
Signaling Flow on the Gb Interface
Page93
GSM CS Signal Flow

Abis over TDM & A over TDM
BM/TC
Separated
Mode
BM/TC
Combined
Mode
Page94
GSM CS Signal Flow

Abis over IP & A over TDM
BM/TC
Separated
Mode
BM/TC
Combined
Mode
Page95
GSM PS Signal Flow

Abis over TDM
Abis over IP
Page96

A over TDM
BM/TC
Separated
Mode
BM/TC
Combined
Mode
Page97

A over IP
Page98
Signaling Flow on the Abis

Interface
Abis over TDM
Abis over IP
Page99
Signaling Flow on the Gb Interface

Gb over IP/FR
Page100
Contents
Page101
Typical Hardware Configuration (GSM)

Service processing boards

The number of A-interface circuits should be considered in the configuration

of DPUc/f boards.
The number of PDCHs should be considered in the configuration of DPUd/g

boards.
The number of TRXs should be considered in the configuration of XPUa/XPUb

boards.
Interface boards
In Abis over IP mode, the FG2a, FG2c, PEUa, POUc, GOUa, and GOUc boards
can be configured. In Abis over TDM mode, the EIUa and OIUa boards can be
configured.
In A over IP mode, the FG2a, FG2a, GOUa, and GOUc boards can be
configured. In A over TDM mode, the EIUa, OIUa, and POUc boards can be
configured.
Page102
Typical Configuration
Specifications (GSM)
Configuration of service processing boards of BSC6000 V900R008 and

BSC6900 V900R012/R013
BSC6000 V900R008
Board
Number of
TRXs
Number of
cells
Number of
BTSs
Number of
active PDCHs
(MCS-9)
Number of
TCHs/Fs
BSC6900
V900R013
BSC6900 V900R012
Nonmain
control
XPUa
DPUc
270
360
640
640
270
360
640
640
270
360
640
640
1024
1024
1024
960
960
1920
Main
control
XPUa
Main
control
XPUb
DPUd
Non-main
control
XPUb
DPUc
DPUd
Page103
DPUf
DPUg
Typical Configuration Specification (GSM)

Interface board specifications

Item
EIUa
FG2a
OIUa
PEUa
GOUa
FG2c
Number of
TRXs
384
384
384
384
384
2048
2048
512
2048
Number of
CICs (64 K)
over the A
interface
960
6144
1920
6144
23,040
23,040
3906
23,040
Gb (Mbit/s)
128
64
1024
1024
504
GOUc
POUc_TDM
POUc_IP
Page104
Maximum Specifications (V900R012/R013 GO)

R12
R13
1536 TRXs
EPS
1024 TRXs
EPS
EPS
1024 TRXs
EPS
EPS
512 TRXs
MPS
MPS
R12/R13
BM/TC Combined
R12/R13
1536 TRXs
1536 TRXs
EPS
1536 TRXs
1536 TRXs
EPS
2048 TRXs
EPS
1024 TRXs
1024 TRXs
MPS
1024 TRXs
MPS
1024 TRXs
BM/TC Separated
EPS
A over IP
Page105
Typical Configuration (V900R013 GO)

BM/TC Separated (4096 TRXs)

The DPUf/g board is used.
Abis/Ater/A interface: TDM (optical

transmission)
Gb interface: FR (optical
transmission)
Because of the lack of backplane

TDM resource, the POUc and OIUa
boards that serve as the Ater
interface boards have the same
specifications.
Page106

BM/TC Combined (4096 TRXs)

The DPUf board is used.
Abis/Ater/A interface: TDM (optical

transmission)
Gb interface: FR (optical transmission)
Page107

All-IP transmission
The DPUf/g board is used.
All-IP transmission is used.

Abis/A/Gb interface: IP
Page108
Summary
We have learned about the BSC6900 in terms of its

features and functions, subracks, boards, subsystems,
signal flows of both the control plane and user plane of
all interfaces, configuration principles, and typical
configurations.
Page109
BSC6900 Initial
Data Configuration
Based on CME
www.huawei.com
Foreword
The CM Express, also called CME, is the core of the

integrated solution of multi-standard radio access
network provided by Huawei. It can be used in various
scenarios of the UMTS and GSM networks, such as initial
deployment, network expansion, NodeB/BTS rebuilding,
and routine reconfiguration. In this way, the CME
functions as a configuration management system for the
entire network in various stages.
Page1
Objectives

Describe CME Window
Outline BSC6900 data configuration procedure based on

CME
Complete GSM BSC data configuration
Backup and restore the configuration data
Page2
Contents
1. Basic Concepts of CME
2. BSC6900 Data Configuration
Page3
CME General Configuration Window
Page4
Concepts of CME
Current Area
The CME data areas consist of one current data area and multiple
planned data areas
The current data area stores the configuration data on the existing
network, and the data can only be browsed
Page5
Concepts of CME
Planned Area
The planned data areas are used by different users for data planning
and data configuration. Users can create multiple planned data areas
based on the data in the current data area to perform different
configuration tasks.
By dividing planned data areas, different users can have different

workspaces, which allows multiple engineers to work in parallel. The
modifications in one area do not affect the services on the existing
network before the modified configuration data is activated. This
enhances the reliability and security of configuration data.
Page6
Planned Configuration and Current

Configuration
Page7
Contents
1. Basic Concepts of CME
2. BSC6900 Data Configuration
Page8
Steps of Data Configuration

START
Configuring Global Data

Configuring Equipment Data
Configuring the Clock Source
Configuring Interface Data
END
Page9
STEP1 Configuring Global Data

The BSC global data is a prerequisite to the configuration

of other data.
The BSC global data includes the data that is closely

related to the service, such as the BSC attributes, the
originating signaling point (OSP), the PCU type, and the
clock mode. After the global data takes effect, do not
modify it unless the network is replanned.
Page10
Configuring Global Data (Cont.)
Choose:
GSM Global
Configuration Express
Choose:
BSC Basic
Configuration
Page11

Basic Attributes of BSC
System Information
GSM CN Operator
Originating Signaling Point
Destination Signaling Point
PCU Type
Clock Source
Clock Mode
Page12
Example: Configure Basic Attributes

Choose:
Basic Attributes
of BSC
Choose
Parameter to
modify
Select value
Page13

(Optional) When the A interface uses the IP transmission

mode, it should be configured with the local and
destination entities of the M3UA.
Page14

1
Page15
STEP2 Configuring Equipment Data

The equipment data is the basis for transmitting service

data of the upper layer.
The equipment data includes the data of the cabinets,

subracks, and boards. The CME allows you to configure
the equipment data in device panel mode.
Page16
Configuring Equipment Data (Cont.)

In the Main navigation tree in the left pane of the

planned data area, right-click a BSC, and then choose
Device Panel from the shortcut menu.
1
2
Select Device Panel
Page17
Configuring Equipment Data (Cont.)

Add cabinets and boards based on the actual location of

the BSC hardware
1
Select Slot
Select Board
Type
Page18
STEP3 Configuring the Clock Source of the Interface Board

A line clock refers to an 8 kHz clock that runs from the interface
board of a subrack to the GCUa board. Therefore, when a line clock
is used as the system clock, you need to configure the clock source
of the interface board.
In BM/TC combined mode, the interface board that extracts the clock from the core network (CN)
is located in the MPS subrack. In this way, the clock signal can be transmitted to the GCUa board
from the LINE1 or LINE2 channels of the MPS backplane or from the 2 MHz clock output interface
(using clock signal lines) on the panel of the interface board.
In BM/TC separated mode, the interface board that extracts the clock from the CN is located in the
TCS subrack. In this way, the clock signal is transmitted to Ater interface board of this subrack
through the backplane, to the Ater interface board of the MPS subrack through the cable that
connects the subracks of the Ater interface, and then to the GCUa or GCGa board through the
backplane channel of the MPS subrack.
If the BSC is configured with a Gb interface board that is based on FR transmission, the Gb
interface board needs to lock the clock signals of the SGSN, because the clocks of the CS and PS
domains are not synchronized.
Page19
Configuring the Clock Source of the

Interface Board (Cont.)
Configuring the clock source of the interface board
Select BSC
Select Interface
Board
Select Properties
Select Parameter
Page20
STEP4 Configuring Interface Data

Configuring the GSM network interface data, which

includes the data of the Ater, A, and Gb interfaces.
The A and Gb interfaces are standard interfaces, which

ensure the interconnection and communication between
the devices of different manufacturers.
The other interfaces are internal interfaces (that is,

private interfaces) that do not support the
interconnection between the devices of different
manufacturers.
Page21
Configuring Ater Interface(TDM)

Configure the Ater interface between the MPS/EPS and

the TCS in the BSC.
Configuring the Ater interface only when the BSC is in

BM/TCS separated mode.
This configuration facilitates data transmission between

the MPS/EPS and the TCS.
Page22
Configuring A Interface (TDM)

The A interface is a standard interface between the BSC

and the MSC.
To configure the data of the A interface in TDM mode,

you need to configure the E1/T1 data at the physical
layer, the data of the SS7 signaling link, and the
information about the peer destination signaling point
(DSP).
Page23

Configure GSM CN Node
In the Transport navigation tree in the left pane of the planned data
area, choose NE to be configured > GSM. The interface information
about the NE is displayed under the GSM node.
Click A under the GSM node. The configuration window is displayed.
The system displays the configuration object tree and the property
parameters of the selected objects.
Choose MSC > GSM CN Node under the A Configuration Express node.
Configure the properties of the MSC node based on the planned data.
This configuration is applicable in adding GSM Core Network (CN)

nodes and signaling point groups, mapping DSPs and CN nodes, and
specifying groups for signaling points.
CAUTION:
Each CN connected to the BSC must be configured with node

information. Otherwise, calls cannot be accessed through the CN.
Click the configuration objects in sequence under TDM Transport and

configure the link information about the A interface, as shown in Table
1.
Page24

Add A Interface E1/T1
4
1
2
Page25

Configure MTP3 Signalling Link Set
Configure MTP3 Signalling Link
Configure MTP3 Signalling Route
Page26
Configuring A Interface (IP)

In IP mode, the functions of the TC are performed by the

MGW, that is, the voice processing function is performed
by the core network. In this case, the TCS is not
configured for the BSC. The A interface data that you
need to configure includes the data of local entities, the
data at the physical layer and data link layer, and the link
data on the control plane.
Page27

Configure GSM CN Node
In the Transport navigation tree in the left pane of the planned data
area, choose NE to be configured > GSM. The interface information
about the NE is displayed under the GSM node.
Click A under the GSM node. The configuration window is displayed.
The system displays the configuration object tree and the property
parameters of the selected objects.
Choose MSC > GSM CN Node under the A Configuration Express node.
Configure the properties of the MSC node based on the planned data.
This configuration is applicable in adding GSM Core Network (CN)

nodes and signaling point groups, mapping DSPs and CN nodes, and
specifying groups for signaling points.
CAUTION:
Each CN connected to the BSC must be configured with node

information. Otherwise, calls cannot be accessed through the CN.
Click the configuration objects in sequence under TDM Transport and

configure the link information about the A interface, as shown in Table
1.
Page28

Set Ethernet Port IP Address
Page29

Configure SCTP Signalling Link
Configure M3UA Signalling Link Set
Configure M3UA Signalling Link
Configure M3UA Signalling Route
Page30

Configure Adjacent Node
Configure Adjacent Node Mapping
Configure Transport Resource Group
Configure IP Path
Binding Relation Between IPPATH

And MBFD
Page31
Configuring Gb Interface (FR)

When an internal PCU is configured for the BSC, you need

to configure the Gb interface for the BSC so that the
communication in frame relay (FR) mode can be
established between the BSC and the SGSN.
Gb interface data that you need to configure includes the

information about the SGSN and the data of bearer links.
Page32

Add an SGSN node
Page33
Page34
Configuring Gb Interface (IP)

When an internal PCU is configured for the BSC, you need

to configure the Gb interface for the BSC so that the
communication in IP mode can be established between
the BSC and the SGSN. In IP mode, the Gb interface data
that you need to configure includes the information
about the SGSN and the data of bearer links.
Page35

Add an SGSN node
Page36

Set Ethernet Port Parameters
Set Ethernet Port IP Address
Page37

Configure network service entity
Configure local NSVL
Configure remote NSVL (optional)
Page38

Configure PTPBVC
Page39
Export MML Script
Page40
Summary
BSC6900 data configuration procedure
The meaning of some important parameter
Backup and restore the configuration data
Page41
BSC6900 GO
Data Configuration
www.huawei.com
Objectives

Detail the Procedure of BSC6900 Data Configuration
Perform Global Data Configuration
Perform Equipment Data Configuration
Perform Interface Configuration
Page1
Contents
1. Data Configuration Overview
2. Preparation
3. Configuring the Global Information
4. Configuring the Equipment Data
5. Configuring the Interfaces
Page2
Data Configuration Overview

Configuration Tools
Web LMT (Local Maintenance Terminal)

CME (Configuration Management Express)

Based on MML (Man Machine Language)
Based on GUI (Graphic User Interface)
LMT Execution Modes

Batch mode
multiple MML commands in a script
Single Command Mode

one command at a time and carry it out directly
Page3
Data Configuration Procedure

Preparation
Configuring the Global

Information
Configuring the Equipment Data
Configuring the Interfaces
LOAD
Page4
Contents
2. Preparation
Page5
Preparation
Data Configuration Right Management

Forcibly Obtain CM Control Right (FOC CMCTRL)
Request the CMC right (REQ CMCTRL)
BSC6900 controls whether LMT or M2000 has the permission

to configure the data at a moment to avoid the data conflict
Set CM Control enable switch (SET CMCTRLSW)
Check the status of CMC (LST CMCTRL)
Lock the CMC right (LCK CMCTRL)
Unlock the CMC right (ULK CMCTRL)
Page6
Preparation
Data Configuration Mode

Set Offline State (SET CFGDATAINEFFECTIVE)
Set Online State (SET CFGDATAEFFECTIVE)
Page7
Preparation
Data Initialization (RST DATA)

RST DATA will remove all configuration data in BAM
Data in BAM
(OMUa)
OMUa)
RST DATA
Data in FAM
(Other Boards)
Page8
Contents
Preparation

2. Preparation

Information
LOAD
Page9
Basic Data
OPC
DPC
M3UA Entities
Global Data configuration

Configuring the Basic Data
Configuring the OPC (Original Signaling Point Code)
Configuring the DPC (Destination Signaling Point Code)
Configuring the M3UA Local and Destination Entities

This section describes how to configure the local and

destination M3UA entities. You need to configure the M3UA
entities when the IP-based networking is used.
Basic Data
OPC
Page10
DPC
M3UA Entities

Add GSM BSC Basic Information (SET BSCBASIC)

Area Code: Local area code, for example, 021 for Shanghai.
CC: Country code, for example, 86 for China
Interface Tag : Phase tag for GSM protocols supported by the A,

Um, Abis interface
Support TFO Codec Optimize: Whether to enable the tandem free

operation (TFO) Codec optimizing function
Support High Frequency Band : DCS1800, PCS1900
Service Mode: Service mode of the BSC6900, Actual Value Range:

SEPARATE, TOGETHER
Page11
Basic Data
OPC
DPC
M3UA Entities

Add GSM Operator (ADD GCNOPERATOR)

Operator Type: Primary operator or secondary operator

Each BSC6900 must be configured with one and only one primary
operator. In the case of RAN Sharing, a maximum of fifteen
secondary operators can be configured.
Actual Value Range: PRIM, SEC
Operator Index
Operator Name
Basic Data
OPC
Page12
DPC
M3UA Entities
Configuring the OPC

Add OSP (Original Signaling Point) (ADD OPC)

OSP name
OSP index
Network ID: INT, INTB, NAT, NATB
OSP code bits:BIT14, BIT16, BIT24
Signal point data format:

WNF(Whole Number Format), DNF(Divided Number Format)
OSP code [Whole Number]

The OSP code cannot be 0. It is assigned in the SS7 signaling

network and each OSP code is unique
Page13
Basic Data
OPC
DPC
M3UA Entities
Configuring the DPC

Add DSP (ADD N7DPC)

DSP name
DSP index
OSP index
Signal point data format
DSP code [Whole Number]
DSP type
Signaling route mask: Signaling route load sharing.

In the value, the number of 1s (represented by n) determines the

maximum number (2) of routes for the load sharing.
Basic Data
OPC
Page14
DPC
M3UA Entities
Configuring the M3UA Local Entities

Add M3UA Local Entity (ADD M3LE)

Local entity No.
OSP index
Local entity type

M3UA_ASP, M3UA_IPSP
Local entity name
Page15
Basic Data
OPC
DPC
M3UA Entities
Application scenario of ASP and IPSP

ASP: A process instance of

BSC
an application server
Scenario 1 MSC Server

/ SGSN
IPSP
IPSP: A process instance
AS
of an IP_based application
AS: Application Server
BSC
(MSC server/SGSN)
Scenario 2
ASP
MGW
SG
SG: Signaling Gateway

(MGW)
Basic Data
OPC
Page16
DPC
M3UA Entities
Configuring the M3UA Destination Entities

Add M3UA Destination Entity (ADD M3DE)

Destination entity No.
Local entity No.
DSP index
Destination entity type

M3UA_SGP(M3UA SGP), M3UA_IPSP(M3UA IPSP),

M3UA_SS7SP(M3UA SS7SP), M3UA_SP(M3UA SP)
Destination entity name
Page17
Contents
Preparation

2. Preparation

Information
LOAD
System
Hardware
Page18
Clocks
Equipment Data Configuration

Configuring the System Information
Configuring a Cabinet
Configuring a Subrack
Configuring a Board
Configuring the Clocks
Configuring the Time
Configuring the IP Address of the EMS Server
Page19
EMS
System
Hardware
Clocks
EMS
Configuring the System Information

Set Base Station Controller System Information (SET SYS)

(Optional)
System description
NE Name
Contact mode of the manufacturer
System Location
System services
System
Page20
Hardware
Clocks
Configuring a Cabinet & Subrack

Add Cabinet (ADD CAB)

Use this command to add an EPR or TCR.
Cabinet No.
Is remote cabinet :Yes/No
Add Service Processing Subrack (ADD SUBRACK)

Subrack No.
Subrack name
Connect power monitoring board: Yes/No
Subrack Type: EPS, TCS
Page21
EMS
System
Hardware
Clocks
EMS
Open SCUa Ports

Open SCUa Ports (SET SCUPORT)

After a subrack is added, run this command to enable the

corresponding port on the SCU board in the main subrack.
Subrack No
Port No
Port Switch: Close, Open
If the SCUa ports are closed, the MAC switching couldnt be

implemented between subracks. So we should use this
command to open the SCUa ports
System
Hardware
Page22
Clocks
EMS
Configuring a Board
Add Board (ADD BRD)

This command can be used by all types of boards except the

SCUa, GCUa, and GCGa
Subrack No.
Board Class : INT, DPU, XPU, OMU, SAU, TNU
Board Type
Slot No.
Backup: Whether to configure the backup board
Page23
System
Hardware
Clocks
EMS
Configuring a Board
Add Board (ADD BRD)

Logical Function Type: OAM, TDM_Switching, GCP, RGCP,

MCP, GTC, GPCU, IP, FR, HDLC, TDM, GbIP, Abis_TDM,
Ater_TDM, Pb_TDM, A_TDM, Abis_IP, SAU
TC board: Whether it is configured inside the TCS
MPU Subrack No.
MPU Slot No.
System
Hardware
Page24
Clocks
EMS
Configuring the Clocks

Set Board Clock Source (SET CLK)

Set the clock source data on the interface board in the MPS or EPS
subrack
Add Clock Source (ADD CLKSRC)

Set Clock Working Mode (SET CLKMODE)

BITS,8k,GPS,Line clock
Set the working modes of clock sources: manual /auto /free
Set Clock Board Type (SET CLKTYPE)

Set the type of a clock board: GCUa /GCGa
Page25
System
Hardware
Clocks
EMS
Configuring the Time

Set Information About Time Zone and Daylight Saving

Time (SET TZ)
Set the time zone and daylight saving time to ensure a

correct local time for the current system
Add SNTP Server for the Network Element (ADD

SNTPSRVINFO)
Add the information of the SNTP server connected to the

network element
System
Hardware
Page26
Clocks
EMS
Configuring the IP Address of the EMS Server

Add IP Address For EMS (Element Management System)

(ADD EMSIP)
EMS IP Address: IP address of the NE management system
Subnet Mask
OMU External Network Virtual IP
OMU External Network Mask
Page27
Contents
Preparation

2. Preparation

Information

LOAD
Page28
Contents
5. Interface Data Configuration

Ater Interface Data Configuration (over TDM)
Ater Interface Data Configuration (over IP)
A Interface Data Configuration (over TDM)
A Interface Data Configuration (over IP)
Gb Interface Data Configuration (over FR)
Gb Interface Data Configuration (over IP)
Pb Interface Data Configuration (only Outer PCU need

configure)
Page29
Path
OML
SL
Ater Connection Path Configuration

Add Ater connection path (ADD ATERCONPATH)

Ater connection path index
BM subrack No.
BM slot No.
TC subrack No.
TC slot No.
TC port No.
Path
Page30
OML
SL
Ater OML Configuration

Add Ater OML (ADD ATEROML) (Only for remote TCS)

Ater OML Index
Ater Connection Path Index: Select Ater connection path

that the OML is located at
Timeslot Mask : Select the timeslots configured for the OML
Page31
Path
OML
SL
Ater SL Configuration
Add Ater SL (ADD ATERCONSL) (Only for remote TCS)

Ater signaling Channel ID
Ater connection path index: Select Ater connection path

that the RSL is located at
Ater mask: Select the timeslot configured for the RSL
Page32
Contents


configure)
Page33
Ater Interface over IP

In the case of IP over Ater, IP over Ethernet is not

supported over the Ater interface, and the user plane can
adopt only the IP over TDM mode.
Timeslot switching is applicable to data transmission on

the control plane. Therefore, the configuration for the
control plane in this mode is similar to that in Ater TDM
mode.
Page34
Introduction to PPP/MP
E1 link
TS0~TS31
PPP/MP link1 (TS1~TS31)
TS1
TS2
TS3
TCS
MPS/EPS
PPP/MP link 2 (TS1~TS31)

TS1
TS2
TS3
TCS
MP group
PPP/MP link3 (TS1~TS31)
E1 link
TS0~TS31

BC2(TS1~TS3)
Page35
IP over E1
BSC Basic
IPPATH
Configure the physical layer and

data link layer for the POUc board.
The POUc board is configured in the subrack to be

configured with an Ater connection path.
Determine the type of link carried on the E1/T1 link (PPP

link or MP link group)
If the E1/T1 link carries PPP link: (ADD PPPLNK)
If the E1/T1 link carries MP link group: (ADD MPGRP ) &

(ADD MPLNK )
IP over E1
Page36
BSC Basic
IPPATH
Configure the physical layer and data

link layer for the POUc board.
Configure a PPP link. (ADD PPPLNK)

Board type: POUc
PPP link No.: PPP link number
E1T1 port No.: Number of the E1T1 port for bearing the PPP link
Bearing time slot: Bearer E1/T1 port timeslot of PPP link
Borrow DevIP: whether to use the device IP address as the local IP

address or not.
Set to YES, the device IP address is used as the local IP address.
Set to NO, the device IP address is not used as the local IP address.
Page37
IP over E1
BSC Basic
IPPATH
Configure the physical layer and

data link layer for the POUc board
Add an MP link group (ADD MPGRP)

Board type: POUc
MP Group No.: MLPPP group number. 0~167(POUc)
Borrow DevIP: YES/NO
Add an MP link (ADD MPLNK)

Board type: POUc
MP Group No.
PPP sub-link No.
E1T1 port No.
Bearing time slot
IP over E1
Page38
BSC Basic
Set the Transmission Mode

Set the Transmission Mode (SET BSCBASIC)

Set Service mode to SEPARATE.
Set Ater Interface Transfer Mode to IP.
Page39
IPPATH
IP over E1
BSC Basic
IPPATH
Add an Adjacent Node

Add an adjacent node (ADD ADJNODE)

Adjacent Node ID
Adjacent Node Name
Adjacent Node Type
BSC(Ater Interface on BSC)
TC(Ater Interface on TC)
BSC ID
IP over E1
Page40
BSC Basic
IPPATH
Add an IP Path
Add an IP path (ADD IPPATH)

Adjacent Node ID
IP path ID
Interface Type: ATER(ATER Interface)
IP path type: An IP path is of either the QoS type or the non-QoS

type.
Local IP address
Peer IP address
Forward Bandwidth: Transmit bandwidth of IP path
Backward Bandwidth: Receive bandwidth of IP path

Page41
Contents


configure)
GCNNODE
E1/T1
MTP3LKS
Page42
MTP3LNK
MTP3RT
GSM CN Node Configuration (Over TDM)

Add GSM CN Node (ADD GCNNODE)

CN node index
DSP index
DPC group index: Index of a DPC group

When multiple DPCs or one DPC serves as a logical entity, this

logical entity is called a DPC group. When the MSC pool function
is activated, the user plane resources on the A interface are
shared among the MSCs in the pool, and thus load balancing is
achieved
Operator name
MSC ID
Page43
GCNNODE
E1/T1
MTP3LKS
MTP3LNK
MTP3RT
A Interface E1T1 Configuration (Over TDM)

Add A interface E1/T1 (ADD AE1T1)

Subrack No.
Slot No.
Port No.
DPC group index
OPC index
Timeslot type: Set all timeslots to CIC or NULL
BSC flag: Main BSC or subsidiary BSC
Start CIC: The start CIC No. of the E1/T1
GCNNODE
E1/T1
MTP3LKS
Page44
MTP3LNK
MTP3RT
A MTP3 Link Set Configuration (Over TDM)

Add MTP3 link set (ADD MTP3LKS)

Signaling link set index: To identify an signaling link set

uniquely
DSP index
Signaling link mask: Indicates link load sharing.

In the value, the number of 1s (represented by n) determines the

maximum number (2^n) of links for the load sharing.
Signaling link set name
Page45
GCNNODE
E1/T1
MTP3LKS
MTP3LNK
MTP3RT
A MTP3 Link Configuration (Over TDM)

Add MTP3 links (ADD MTP3LNK)

Signaling link set index
Signaling link code
Link bearer type

MTP2: indicates that the lower layer link bearer is the MTP2 used in TDM scenario
SAAL: indicates that the lower layer link bearer is the M3UA used in SAAL scenario
TC mode: To specify the mode of TC
MTP2 Link No.: the A interface E1 No. bearing this signaling link
A interface timeslot mask
Link Rate Type: 64kbps or 2Mbps
Signaling Link Name
GCNNODE
E1/T1
MTP3LKS
Page46
MTP3LNK
MTP3RT
A MTP3 Routing Configuration (Over TDM)

Add MTP3 routing information (ADD MTP3RT)

DSP index
Signaling link set index: To identify an signaling link set

uniquely
Signaling route name
Page47
Contents


configure)
Page48
Protocol stack of A Interface over IP

Signaling plane adopts M3UA/SCTP/IP protocol stack.
User plane adopts RTP/UDP/IP protocol stack.

BSC A Interface MSC Server
BSC
A Interface
DTAPBSSMAP
DTAP BSSMAP
SCCP
M3UA
SCTP
IP
MAC/PPP
SCCP
M3UA
SCTP
IP
MAC/PPP
MSC
DTAP BSSMAP
DTAP BSSMAP
SCCP
MTP
Layer1
SCCP
MTP
Layer1
A over TDM
Signaling plane of A over IP

BSC A Interface
Voice
RTP
UDP
IP
MAC/PPP
MGW
Voice
RTP
UDP
IP
MAC/PPP
User plane of A over IP
Page49
IP over Ethernet networking

IP over Ethernet Networking (Layer 2)
IP over Ethernet Networking (Layer 3)
GCNNODE
PHY Layer
Data Link
Control plane
Page50
Mapping
User Plane
A Interface Data Configuration (Over IP)

Configuration Procedure
Configuring GSM CN Node
Configuring Physical Layer
Configuring Data Link Layer
Configuring Control Plane
Configuring the Mapping
BSC
DPU
Between Service Types and

Transmission Resources for
the Adjacent Node
Configuring User Plane
Page51
GCNNODE
PHY Layer
Data Link
Control plane
Mapping
User Plane
GSM CN Node Configuration (Over TDM)

Add GSM CN Node (ADD GCNNODE)

CN node index
DSP index
DPC group index: Index of a DPC group

When multiple DPCs or one DPC serves as a logical entity, this

logical entity is called a DPC group. When the MSC pool function
is activated, the user plane resources on the A interface are
shared among the MSCs in the pool, and thus load balancing is
achieved
Operator name
MSC ID
GCNNODE
PHY Layer
Data Link
Control plane
Page52
Mapping
User Plane
Configuring the Physical Layer and Data Link Layer

for the FG2a/FG2c/GOUa/GOUc Board
Set attributes of the Ethernet port (SET ETHPORT)

Subrack No.
Slot No.
Board type
Port No.
0~7(FG2a), 0~1(GOUa), 0~11(FG2c), 0~3(GOUc)
Auto negotiation
ENABLE, DISABLE
Page53
GCNNODE
PHY Layer
Data Link
Control plane
Mapping
User Plane
Configuring the Physical Layer and Data Link

Layer for the FG2a/FG2c/GOUa/GOUc Board
Add a standby Ethernet port (ADD ETHREDPORT)

(Optional)
Subrack No.
Main Board Logic slot No.
Port No.
0~7(FG2a), 0~1(GOUa), 0~11(FG2c), 0~3(GOUc)
GCNNODE
PHY Layer
Data Link
Control plane
Page54
Mapping
User Plane

Add IP address of the Ethernet port (ADD ETHIP) ( in link

non-aggregation mode)
Subrack No.
Slot No.
Port No.
IP address index
Local IP address
Subnet mask
Page55
GCNNODE
PHY Layer
Data Link
Control plane
Mapping
User Plane

Add a link aggregation group (ADD ETHTRK) ( in link

aggregation mode)
Subrack No.
Slot No.
Trunk No.: Aggregation group number
Aggregation mode
When this parameter is set to static aggregation, the LACP

protocol is activated; otherwise, the LACP protocol is deactivated.
Value Range: STATIC_LACP, MANUAL_AGGREGATION
GCNNODE
PHY Layer
Data Link
Control plane
Page56
Mapping
User Plane

Add a link to the aggregation group (ADD ETHTRKLNK)

( in link aggregation mode)
Subrack No.
Slot No.
Trunk No.
Trunk Link Slot No.
Trunk Link No.
Page57
GCNNODE
PHY Layer
Data Link
Control plane
Mapping
User Plane

Add the IP address of the link aggregation group (ADD

ETHTRKIP) ( in link aggregation mode)
Subrack No.
Slot No.
Trunk No.
IP address index
Local IP address
Subnet mask
GCNNODE
PHY Layer
Data Link
Control plane
Page58
Mapping
User Plane

Add the device IP address of the board in case of layer 3

networking (ADD DEVIP) (Optional)
Subrack No.
Slot No.
Device IP address type: LOGIC_IP(Logical IP Address),

IPOA_CLIENT_IP(IPOA Client IP Address
Boards in IP transmission mode can be configured with the DEVIP only in

the type of "LOGIC_IP".
Boards in ATM transmission mode can be configured with the DEVIP only in
the type of "IPOA Client IP Address".
IP address
Page59
GCNNODE
PHY Layer
Data Link
Control plane
Mapping
User Plane
A Interface Physical Layer and Data

Link Layer Configuration (Over IP)
Board
Physical layer
Data link layer
POU
SET E1T1
SET OPT
SET COPTLNK
ADD PPPLNK
or
ADD MPGRP ADD MPLNK
PEU
SET E1T1
ADD PPPLNK
or
ADD MPGRP ADD MPLNK
FG2
SET ETHPORT
ADD ETHIP/ADD DEVIP
ADD ETHTRK,
ADD ETHTRKLNK,
ADD ETHTRKIP
GOU
SET ETHPORT
ADD ETHIP/ADD DEVIP
ADD ETHTRK,
ADD ETHTRKLNK,
ADD ETHTRKIP
GCNNODE
PHY Layer
Data Link
Page60
Control plane
Mapping
User Plane
Configuring the Control Plane of the A Interface (over IP)

Add SCTP Signalling Link (ADD SCTPLNK)

Signalling link mode :Server/Client

Server mode: BSC6900 starts the listening and waits for the peer
to send the SCTP-INIT message.
Client mode: BSC6900 actively sends the SCTP-INIT message.
Application type :NBAP, M3UA, BBAP

The upper layer application type of A interface is M3UA.
Local/Destination SCTP port No.
First local/destination IP address
Second local/destination IP address
Page61
GCNNODE
PHY Layer
Data Link
Control plane
Mapping
User Plane
Configuring the Control Plane of the A Interface (over IP)

Add M3UA link set (ADD M3LKS)

Signalling link set index
Destination entity No.
M3UA signaling link name
Add an M3UA route (ADD M3RT)

Destination entity No
Signalling link set index
M3UA route name
GCNNODE
PHY Layer
Data Link
Control plane
Page62
Mapping
Configuring the Control Plane of the A

Interface (over IP)
Add M3UA link (ADD M3LNK)

SCTP link No.
M3UA Signaling link name
Add an adjacent node (ADD ADJNODE)

Adjacent Node ID
Adjacent Node Name
Adjacent Node Type
Page63
User Plane
GCNNODE
PHY Layer
Data Link
Control plane
Mapping
User Plane
Configuring the Mapping Between Service Types

and Transmission Resources for the Adjacent Node
Add Transport Resource Mapping (ADD TRMMAP)

Add Factor Table (ADD TRMFACTOR)

Add a transport resource mapping
Add an activation factor table
Add Node Mapping (ADD ADJMAP)

Add the TRM mapping to an adjacent node and to add the

mapping from interface transmission type to TRMMAP
index and factor index
GCNNODE
PHY Layer
Data Link
Control plane
Page64
Mapping
Configuring the User Plane of the A

Interface (over IP)
Add an IP path (ADD IPPATH)

Adjacent Node ID
IP path ID
Interface Type
Forward Bandwidth
Backward Bandwidth
Page65
User Plane
GCNNODE
PHY Layer
Data Link
Control plane
Mapping
User Plane

Interface (over IP)
Add an IP route (ADD IPRT) (Optional)

To add an IP route when the layer 3 networking mode is

used between the BSC6900 and the CS domain. To add
more IP routes, run this command repeatedly.
DSTIP: Destination IP address
DSTMASK: Destination address mask
NEXTHOP: Forward route address
PRIORITY: Priority
REMARK: Route use description
GCNNODE
PHY Layer
Data Link
Page66
Control plane
Mapping
User Plane

Interface (over IP)
Set TC DSP Resource Type (SET TCTYPE)

The TC resource type can be set only when the

DPUb/DPUc/DPUf board is configured in the MPS/EPS subrack
and the logical function type is GTC.
DSP No.: Number of a DSP in the DPU board.

The number of a DSP in the DPUf board ranges from 0 to 47.
The number of a DSP in the DPUb/DPUc board ranges from 0 to 21.
The type of TC resource: GTC/UTC/ITC
Page67
Contents


configure)
Page68
Protocol Stack of the Gb Interface
LLC
relay
Relay
RLC
BSSGP
BSSGP
MAC
Network
Service
Network
Service
GSM RF
L1bis
L1bis
BSS
Gb
SGSN
Page69
Components of Gb Interface
data
PVC(DLCI)
BC(BCID)
PVC(DLCI)
data
Page70
NS Basic Concept
BC (Bearer Channel)
Consist of one group of time slots in one E1
DLCI (Data Link Connection Identifier)

The identifier of PVC having end-to-end significance across

the Gb interface
NSVC (Network Service Virtual Connection)

Provide end-to-end communication between the BSS and

SGSN irrespective of the exact configuration of the Gb
interface
NSE (NS entity)

Responsible for management of all of NSVC
Page71
Sub-Network Service Functions

The Sub-Network Service functions of the Network

Service shall provide access to the intermediate network
(or to the peer entity in case of direct point-to-point
configuration) and shall provide NS-VCs between NS peer
entities
Gb
FR Network
Gb
DTE
DTE
SGSN
BSS
Gb
DTE
DCE
Page72
NS Load-sharing
Two users in the same cell
SGSN
BVC1
cell
BSS
BVC2
BSSGP Layer
BVC1
BVC2
ms#1
ms#2
NSE1
NSE3
NSE2
NS Layer
NSVC channel=20
NSE1
NSE3
NSE2
DLCI=16
NSVC channel=10 DLCI=259
Page73
BSSGP Virtual Connections

BVC provide communication paths between BSSGP entities.

Each BVC is used in the transport of BSSGP PDUs between the
following entities:
peer point-to-point (PTP) functional entities
peer point-to-multipoint(PTM) functional entities
peer signalling functional entities
BVCI (BSSGP Virtual Connection Identifier)

The BVCI is used to enable the lower network service layer to

efficiently route the BSSGP PDU to the peer entity
PCU creates a BVC for each cell and assigns a BVCI for it , and then
sends them to SGSN via procedure, on which SGSN can create a
cell list
Page74
The Difference btw. PTP BVC and SIG BVC

PTP BVC
SIG BVC
Cell1
Cell1
Cell2
Cell2
NSE
NSE
Signaling
NSVC1
User data
NSVC2
Page75
Relations between the Objects to

be Configured
Basic
NSE
BC
Page76
NSVC
PTPBVC
Configuring the Gb Interface (over FR)

Set the PCU type (SET BSCPCUTYPE)

Type : Inner
Add an SGSN node (ADD SGSNNODE)

OPNAME: Name of the operator. This parameter uniquely

identifies an operator
CNID : Identifies a node of SGSN with the operator name

uniquely
Page77
Basic
NSE
BC
NSVC
PTPBVC

Add an NSE (ADD NSE)

NSEI: Identifies a unique NSE
SRN: Subrack number of the XPU bound to the NSE
SN: Slot number of the XPU bound to the NSE
Subnet protocol type : Gb over FR


uniquely
Basic
NSE
BC
Page78
NSVC

Add a BC (ADD BC)

Subrack No.
Slot No.
Port No.
BC Identifier
Bearing timeslot
Page79
PTPBVC
Basic
NSE
NSVC
BC
PTPBVC

Add an NSVC (ADD NSVC)

NSVCIDX: NSVC index, identifies a unique NSVC
NSVCI: NSVC ID, identifies a unique NSVC. This ID must be

negotiated with the peer SGSN
NSEI: Identifies a unique NSE
SRN: Number of the subrack
SN: Number of the slot
BCID: Identifies one BC at the same port
DLCI: ID of the data link connection of the NSVC
Basic
NSE
BC
Page80
NSVC

Add a PTPBVC (ADD PTPBVC)

NSE Identifier
PTP BVC Identifier
Index Type
Cell Index
Cell Name
Page81
PTPBVC
Contents


configure)
Basic
NSE
Page82
NSVL
PTPBVC
Configuring the Gb Interface (over IP)


Type : Inner
Add an SGSN node (ADD SGSNNODE)



uniquely
Add an NSE (ADD NSE)

Subnet protocol type : Gb over IP
Configuring Physical Layer and Data Link Layer
Page83
Basic
NSE
NSVL
PTPBVC

Add an local NSVL (ADD NSVLLOCAL)

Local IP Address
Local UDP Port No. : UDP port number of the local NSVL
When Subnet Protocol Type of NSE is "Gb over IP" and

Subnetwork Configure Mode is "Static", the setting of this
parameter must be consistent with the setting at the SGSN side.
Value Range: 1214~2001, 2005~3783, 3786~4783, 4785~65000
Subrack No.
Slot No.
Basic
NSE
Page84
NSVL
PTPBVC

Add an remote NSVL (ADD NSVLREMOTE) (Optional)

If the NSE is in static configuration mode, run this

command to add an NSVL on the SGSN side.
Remote IP Address
Remote UDP Port No.: UDP port number of the remote

NSVL.
The setting of this parameter must be consistent with the setting

at the SGSN side.
Value Range: 0~65535
Page85
Basic
NSE
NSVL
PTPBVC

Add a PTPBVC (ADD PTPBVC)

NSE Identifier
PTP BVC Identifier
Index Type
Cell Index
Cell Name
Page86
Contents


configure)
Page87
Basic
PB E1/T1
PB SL
Configuring the Pb Interface


Type : Outer
Add a PCU (ADD PCU)

PCU Name
PCU No.
Operator Name
Basic
Page88
PB E1/T1
PB SL

Set the Pb interface E1/T1s (ADD PBE1T1)

Subrack No.
Slot No.
Port No.
PCU No.
Start PCIC: The value of Start PCIC must be the multiple of

128
Page89
Basic
PB E1/T1
PB SL

Set the Pb interface signaling link (ADD PBSL)

Subrack No.
Slot No.
Port No.
Timeslot No.
Page90
Summary
We have configured the finished the BSC6900(GO) data

configuration, including: global data configuration,
equipment data configuration, interfaces data
configuration and clock data configuration.
Page91
BSC6900
Data Reconfiguration
www.huawei.com
References
HEDEX
GBSS Reconfiguration Guide
Page 1
Objectives

Change the Connection between the BSC and the MSC
Modify OPC and DPC
Modify the N7 signaling link from 64k to 2M
Add a STP in A interface
Add subracks and boards in the BSC
Remove Boards and Subracks from the BSC
Modify a single OMU to a double OMU
Expand the transmission resources in A, GB and Abis interface.
Reconfigure the Transmission Mode on A, Ater, Gb and Abis interface
Adjust the cell processing in DPU board
Page 2
Contents
1. Changing the Connection Between the BSC and the MSC
2. Modify OPC and DPC
3. Modify a N7 signaling link from 64k to 2M
4. Add an STP in A interface
5. Add subracks and boards to the BSC
6. Remove Boards and Subracks from the BSC
7. Modify a single OMU to a double OMU
8. Reconfigure the Transmission Mode
Page 3
Contents
1.1 Cutting Over an MSC (with IP Transmission Mode Retained over the A Interface)
1.2 Cutting Over an MSC (TDM to TDM Transmission Mode over the A Interface)
1.3 Cutting Over an MSC (TDM to IP Transmission Mode over the A Interface)
Page 4
Cutting Over an MSC (IP Transmission

Mode Retained)
Prerequisites
The transmission device between the BSC and the new MSC is ready.
The interconnection parameters between the BSC and the new MSC
have been negotiated.
The new MSC has been commissioned and is ready to work.
A BSC license is ready.
Page 5
Cutting Over an MSC (IP Transmission Mode Retained)

Context
As an MSC cutover interrupts BSC services perform it when traffic load is

small.
Cut over the MSC in either of the following ways:

If the BSC has an idle interface board or an interface board has idle ports:
configure the new MSC data,
check that the new MSC works normally,
finally remove the original MSC data.
If the BSC has no idle interface board or an interface board has no idle
port:
remove the original MSC data,
disconnect the BSC interface board from the original MSC,
configure the new MSC data,
finally connect the BSC interface board to the new MSC.
In the following slides you will find the first way explained
Page 6
Cutting Over an MSC

(IP Transmission Mode Retained)
Procedure overview
1. Add a DPC to the new MSC.
2. Add the MSC node.
3. Configure IP transmission to the new MSC.
4. Modify LAC, CI, and MNC of cells, if necessary.
5. Modify A interface interconnection parameters, if necessary.
6. Define the new MSC as default MSC.
7. Perform a dialing test to verify that the new MSC functions normally.
8. Remove the transmission from the BSC to the original MSC.
9. Remove the original MSC node.
10.Remove a DPC from the original MSC.
11.Activate the GSM License.
Page 7
Cutting Over an MSC

Procedure
Example:
ADD N7DPC: NAME="NO2", DPX=2, SPX=2, SPDF=WNF, DPC=H'AA, DPCT=A,
SLSMASK=B0001, NEIGHBOR=YES, STP=ON, BEARTYPE=MTP3, PROT=ITUT;
Notes:
A DSP can be configured only when the Originating Signaling Point (OSP) is configured.
This is already the case.
The DSP code must be unique and cannot be the same as OSP code.
The number of DSPs of the A type cannot exceed 32.
All DSPs are numbered from 0 to 186. That is, at most 187 DSPs are supported by the
BSC.
Page 8
Cutting Over an MSC

Procedure
Example:
Notes:
A DSP can be configured only when the Originating Signaling Point (OSP) is configured.
This is already the case.
The DSP code must be unique and cannot be the same as OSP code.
The number of DSPs of the A type cannot exceed 32.
All DSPs are numbered from 0 to 186. That is, at most 187 DSPs are supported by the
BSC.
Page 9
Cutting Over an MSC

Procedure
Example:
ADD GCNNODE: CNNODEIDX=0, DPX=1, DPCGIDX=0, OPNAME="MBSC", MSCCAP=0,
CNID=0, MSCSTATUE=NORMAL, DFDPC=YES, FORBIDNO7FLASHDISC=15;
Notes:
Each CN connected to the BSC must be configured with necessary information so that
calls can be routed to this CN.
Page 10
Cutting Over an MSC

Procedure
Notes:
Several steps may be necessary to define the IP transmission parameters.
E.g. to define it via Fast Ethernet the following steps may be needed:
Add an Ethernet port and an IP address to the Ethernet port.
Define a M3UA local entity and a M3UA destination entity.
Add a M3UA link set and a M3UA route.
Add an SCTP link and a M3UA link.
Add a MSC adjacent node.
Add an IP path.
Page 11
Cutting Over an MSC

Procedure
Example:
MOD GCELL: IDTYPE=BYID, CELLID=1, LAC=23, CI=325;
Notes:
If LAC, CI, and MNC of the original MSC differ from those of the new MSC then the cell
parameters need to be modified.
Page 12
Cutting Over an MSC

Procedure
Example:
SET AITFOTHPARA: CNNODEIDX=0, DirectedRetryAssFailSendEnable=NO;
Notes:
Modify the parameters if the parameters associated with interconnection over the A interface
of the original MSC differ from those of the new MSC.
The parameters associated with interconnection over the A interface depend on network
planning.
The parameters on the BSC side must be consistent with those on the MSC side.
Page 13
Cutting Over an MSC

Procedure
Example:
MOD GCNNODE: CNNODEIDX=0, DPCGIDX=1;
Notes:
Run the MOD GCNNODE command to modify the parameters of a CN node.
In this step, set GCNNODE of the new MSC to Default DPC.
Page 14
Cutting Over an MSC

Procedure
Prerequisites
The verification of Abis, A, and Ater interfaces is successful. The MSs used for
test are functional and are registered in the HLR.
You have logged in to the BSC6900 through the LMT.
Test
20 calls (> 60 s) from a MS to a fixed-line phone: > 90%success, voice is clear, no drop.
20 calls (> 60 s) from a fixed-line phone to a MS : > 90%success, voice is clear, no drop.
20 calls (> 60 s) from a MS to another MS: > 90%success, voice is clear, no drop.
Send a fax from and to a MS: Faxes are sent and received normally.
Check also for inter-RAT handover, location services and AMR service.
Page 15
Cutting Over an MSC

Procedure
Notes:
Several steps may be necessary to remove the transmission parameters:
Remove the IP path and the MSC adjacent node.
Remove the M3UA link and the SCTP link.
Remove the M3UA route and the M3UA link set.
Remove the M3UA destination entity and the M3UA local entity.
Remove the IP address of an Ethernet port and the Ethernet port.
Procedure
Example:
RMV GCNNODE: CNNODEIDX=0;
Page 16
Cutting Over an MSC

Procedure
Example:
RMV N7DPC: DPX=0;
Notes:
Before removing the destination signaling point code, the MTP3LKS and the MTP3RT or
M3LKS have to be removed. This was described in step 8 of this procedure.
Otherwise, the execution of this command fails.
Page 17
Cutting Over an MSC

Procedure
Prerequisites:
The BSC6900 is in service.
The LMT is started and you are logged in to the BSC6900.
The valid BSC6900 license is obtained and stored in the OMU active workspace
\FTP\License
Example:
LST LICENSE:;
LST CFGMODE:;
ACT LICENSE: FN="license.dat";
Page 18
Contents
Page 19
Cutting Over an MSC

(TDM Transmission Mode retained)
Procedure overview
3. Configure TDM transmission to the new MSC.
10. Remove a DPC from the original MSC.
11. Activate the GSM License.
Page 20
Cutting Over an MSC

Procedure
Example:
ADD GCNNODE: CNNODEIDX=0, DPX=1, DPCGIDX=0, OPNAME="MBSC", MSCCAP=0,
CNID=0, MSCSTATUE=NORMAL, DFDPC=YES, FORBIDNO7FLASHDISC=15;
Notes:
The steps are the same as described for the IP mode.
Page 21
Cutting Over an MSC

Procedure
3. Configure TDM transmission to the new MSC.
Notes:
Several steps are necessary to define the TDM transmission parameters:
Add an E1 line.
Define a MTP3 link set, a MTP3 link and a MTP3 route.
Example:
ADD AE1T1: SRN=0, SN=14, PN=0, DPCGIDX=0, OPCIDX=0, ALLTSTYPE=ALLNULL,
BSCFLAG=SUBBSC, SUBBSCTID=1, STCIC=100;
Page 22
Cutting Over an MSC

Procedure
3. Configure TDM transmission to the new MSC (continued).
Example:
ADD MTP3LKS: SIGLKSX=0, DPX=1, LNKSLSMASK=B0001, EMERGENCY=OFF,
NAME="NAME1";
ADD MTP3LNK: SIGLKSX=0, SIGSLC=1, TCMODE=TOGETHER, ASRN=0, ASN=24,
MTP2LNKN=0, APN=0, ATSMASK=TS1-0&&TS15-0&TS16-1&TS17-0&&TS31-0,
NAME="name1";
ADD MTP3RT: DPX=1, SIGLKSX=2, PRIORITY=0, NAME="name1";
Page 23
Cutting Over an MSC

Procedure
Example:
Notes:
Page 24
Cutting Over an MSC

Procedure
Notes:
Several steps are necessary to remove the transmission parameters:
Remove the MTP3 signaling link route, the MTP3 signaling link and the MTP3
signaling link set.
Remove the E1/T1 on the A interface.
Example:
RMV MTP3RT: DPX=1, SIGLKSX=2;
RMV MTP3LNK: SIGLKSX=0, SIGSLC=1;
RMV MTP3LKS: SIGLKSX=0;
RMV AE1T1: SRN=0, SN=16, PN=0;
Page 25
Cutting Over an MSC

Procedure
Example:
RMV N7DPC: DPX=0;
LST LICENSE:;
LST CFGMODE:;
Notes:
Page 26
Contents
Page 27
Cutting Over an MSC (Change from

TDM to IP Transmission Mode)
Procedure overview
3. Install and configure a DPUc board
4. Set the TC type
5. Install and configure an IP interface board
13. Remove a DPC from the original MSC.
Page 28

Prerequisites
Additionally to the prerequisites above a DPUc board and an IP interface board

are required in the BSC.
Context
If TDM transmission is used over the A interface, you can infer that the
BSC6900 TC subrack has been installed with a DPUc board and the BM subrack
has not.
Before changing the transmission mode over the A interface from TDM to IP,
add a DPUc board to the BM subrack, and swap the DPUc services in the TC
subrack to the DPUc board in the BM subrack.
Page 29
Cutting Over an MSC (Change from TDM to

IP Transmission Mode)
Procedure
Example:
ADD N7DPC: NAME="NO2", DPX=2, SPX=2, SPDF=WNF, DPC=H'AA, DPCT=A, SLSMASK=B0001, NEIGHBOR=YES,
STP=ON, BEARTYPE=MTP3, PROT=ITUT;
ADD GCNNODE: CNNODEIDX=0, DPX=1, DPCGIDX=0, OPNAME="MBSC", MSCCAP=0, CNID=0, MSCSTATUE=NORMAL,
DFDPC=YES, FORBIDNO7FLASHDISC=15;
Notes:
Procedure
3.
Install and configure a DPUc board
Example:
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUc, LGCAPPTYPE=GPCU, SN=10, ISTCBRD=NO, MPUSUBRACK=0,
MPUSLOT=2;
Notes:
Take care of dip switch settings when adding boards
Page 30
Cutting Over an MSC (Change from TDM to

IP Transmission Mode)
Procedure
4. Set the TC type
Example:
SET TCTYPE: SRN=0, SN=10, TCTYPE=ITC;
Notes:
The TC resource type can be set only when the DPUc board is configured in
the MPS/EPS subrack and the logical function type is GTC.
Procedure
5. Install and configure an IP interface board
Example:
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUc, LGCAPPTYPE=GPCU, SN=10,
ISTCBRD=NO, MPUSUBRACK=0, MPUSLOT=2;
Notes:
Take care of dip switch settings when adding boards
Page 31

Procedure
Notes:
Several steps may be necessary to define the IP transmission parameters.
E.g. to define it via Fast Ethernet the following steps may be needed:
Add an Ethernet port and an IP address to the Ethernet port.
Define a M3UA local entity and a M3UA destination entity.
Add a M3UA link set and a M3UA route.
Add an SCTP link and a M3UA link.
Add a MSC adjacent node.
Add an IP path.
Page 32

Procedure
10.Perform a dialing test to verify that the new MSC functions normally.
Example:
Notes:
Page 33

Procedure
11.Remove the transmission from the BSC to the original MSC.
Example:
RMV MTP3RT: DPX=1, SIGLKSX=2;
Notes:
The steps are the same as described for the TDM mode.
Page 34

Procedure
12.Remove the original MSC node.
Example:
RMV N7DPC: DPX=0;
LST LICENSE:;
LST CFGMODE:;
Notes:
Page 35
Contents
Page 36
Modify OPC and DPC

Prerequisites
The LMT runs normally.
The LMT communicates with the BSC6900 properly.
A BSC license is ready.
Caution
Changing signaling points will interrupt BSC6900 services. Therefore, change

signaling points at midnight when the traffic load is light.
When an Originating Signaling Point Code (OPC) or Destination Signaling Point

Code (DPC) changes, the Equipment Serial Number (ESN) of the BSC changes.
The ESN of the BSC is bound with a license. Therefore, after the OPC or DPC
changes, you must apply for a new BSC license based on the new ESN and
then activate it.
Page 37
Modify OPC and DPC

Notes
Query the ESN corresponding to the new signaling point
Deactivate all the GSM cells before changing a signaling point.
When an OPC is used by an M3UA local entity (M3LE), set all subracks to
ineffective mode and then change the OPC.
If the OPC to be changed is not used by an M3LE, change the OPC in online
mode.
Check whether the OPC to be changed is used by an M3LE.
Example:
LST ESN: MODE=CUSTOM, SPCBITS=BIT14, SPDF=WNF, SPC=164, DPC=194;
LST M3LE:;
Page 38
Modify OPC and DPC

Procedure overview Change OPC (OPC used by M3LE)
1.
Deactivate all the GSM cells.
2.
Set all subracks to ineffective mode.
3.
Change the OSP name and OSP code.
4.
Define the OPCs mapping the GSM cells.
5.
Set all subracks to effective mode.
6.
Create a data configuration file.
7.
Reset the BSC6900.
8.
Activate the GSM License.
9.
Activate all the GSM cells.
Page 39
Modify OPC and DPC

Procedure Change OPC (OPC used by M3LE)
1. Deactivate all the GSM cells.
2. Set all subracks to ineffective mode
Example:
DEA GCELL: IDTYPE=BYID, CELLID=0;
SET CFGDATAINEFFECTIVE: SRN=1;
Notes:
When a cell is deactivated, the cell becomes out of service.
In ineffective mode only the configuration data on the OMU is updated.
To validate the configuration data modified you must reset the host.
When all subracks are in ineffective mode, configuring data is without license
verification.
Page 40
Modify OPC and DPC

3. Change the OSP name and OSP code.
4. Define the OPCs mapping the GSM cells.
Example:
MOD OPC: SPX=1, NAME="MBSC_01";
MOD GCELLOSPMAP: IDTYPE=BYID, CELLID=0, OPC=1000;
Notes:
The OSP code bits cannot be modified.
The OSP which is used by an M3UA local entity cannot be modified.
Page 41
Modify OPC and DPC

5. Set all subracks to effective mode.
6. Create a data configuration file.
7. Reset the BSC6900.
Example:
SET CFGDATAEFFECTIVE: ;
FMT DATA:WORKAREA=Active;
RST BSC: BSCID=0;
Notes:
Forcibly format the load file and reset the board whose data is modified.
The system will check whether the configuration data is out of license limit.
Page 42
Modify OPC and DPC

9. Activate all the GSM cells.
Example:
ACT GCELL: IDTYPE=BYNAME, CELLNAME="CELL0", ACTTYPE=ACTALL;
Notes:
Activation of a license has been discussed above
Page 43
Modify OPC and DPC

Procedure overview Change OPC (OPC not used by M3LE)
1.
Deactivate all the GSM cells.
2.
Change the OSP name and the OSP code.
3.
Configure the OPCs mapping the GSM cells.
4.
5.
Activate all the GSM cells.
Notes:
All the commands are the same as in the procedure before.
Page 44
Modify OPC and DPC

Procedure Change DPC
1.
Change the DSP name and the DSP code.
2.
Example:
MOD N7DPC: DPX=1, SLSMASK=B0100;
Notes:
You cannot modify a DSP in case a link set exists.
The modified DPC cannot be the same as the configured original signaling
point code.
If the DSP bearing type is M3UA or MTP3_M3UA, you cannot modify "STP"
and "NEIGHBOR".
Page 45
Contents
Page 46
Modify N7 signaling link from 64k to 2M

Prerequisites
Network planning is complete.
The MSC supports the signaling data rate of 2 Mbit/s.
The TDM transmission mode is applied over the A interface.
The EIUa/OIUa board is configured.
The license for the high-speed signaling link is activated.
Page 47

Context
A license is required to activate the high-speed signaling link feature.
The high-speed signaling link refers to the 2 Mbit/s signaling link. Generally, high-speed
signaling links are used for terrestrial transmission. Satellite transmission does not use
high-speed signaling links.
CAUTION:
Reconfiguring the signaling link over the A interface will interrupt the services of the
BSC6900. Therefore, perform the operation when the traffic is low.
The whole process (including board restart) takes about 10 minutes.
NOTE:
The signaling link rate over the A interface must be negotiated between the BSC6900 and
MSC.
After adjusting the signaling link rate over the A interface, you must adjust the signaling
link rate at the MSC. For details about the configuration at the MSC, see relevant
documents of the MSC.
Page 48

Procedure overview:
A) Reconfiguring the Signaling Link Data Rate over the A Interface
1. Query the configuration data of an MTP3 signaling link over the A interface.
2. Remove the MTP3 signaling link.
CAUTION:
Removing the signaling link over the A interface will interrupt the services of the
BSC6900. Therefore, perform the operation when the traffic is low. The rates
of the A interface signaling links in the same link set must be identical. If the
rate of one signaling link must be changed from 64 kbit/s to 2 Mbit/s, all the
signaling links in the link set must be deleted.
Page 49

Procedure overview (continued):
3. Add an MTP3 signaling link. Set Link Bear type to MTP2.
4. Set Link rate type to 2M(2Mbit/s).
5. In BM/TC separated mode with remote TCS set Ater Mask of the MTP3
signaling links on the main TCS to other values rather than TS1.
6. Reset the interface board. In case of active/standby mode, reset the standby
boards before resetting the active board.
B) Verifying the High-Speed Signaling Links:

1. Query the configuration of an MTP3 signaling link. The Link rate type is
2Mbit/s.
2. Query the status of an SS7 DSP.
Page 50

Procedure:
A) Reconfiguring the Signaling Link Data Rate over the A Interface
1. Query the configuration data of an MTP3 signaling link over the A interface.
2. Remove the MTP3 signaling link.
Example:
LST MTP3LNK: SIGLKSX=3, SIGSLC=0, LstFormat=VERTICAL;
Note:
1. If one of the MTP3 links in an MTP3 link set is removed, the services carried by
the entire MTP3 link set may be affected.
2. If the last MTP3 link in an MTP3 link set is removed, the MTP3 link set will be
inaccessible.
Page 51

Procedure (continued):
3. Add an MTP3 signaling link. Set Link Bear type to MTP2.
4. Set Link rate type to 2M (2Mbit/s).
5. In BM/TC separated mode with remote TCS set Ater Mask of the MTP3
signaling links on the main TCS to other values rather than TS1.
6. Reset the interface board. In case of active/standby mode, reset the standby
boards before resetting the active board.
Example:
ADD MTP3LNK: SIGLKSX=0, SIGSLC=1, LKTATE=2M, NAME="name1";
RST BRD: SRN=3, SN=7;
Page 52

B) Verifying the High-Speed Signaling Links:
1. Query the configuration of an MTP3 signaling link. The Link rate type is
2Mbit/s.
2. Query the status of an SS7 DSP.
Example
LST MTP3LNK: SIGLKSX=3, SIGSLC=0, LstFormat=VERTICAL;
DSP N7DPC: DPX=0,TOSPECSSN=NO;
Page 53
Contents
Page 54
Add an STP in A interface

Prerequisites
The XPUa board is configured.
The OPC is configured.
The physical layer and the data link layer on the A interface are configured.
The CN supports this feature.
Context
According to the requirements of the operator, the BSC can be connected to

the MSC directly or through STP.
To use an MGW as an STP, ensure that the MGW supports MTP3/M3UA

signaling transfer.
Page 55

Procedure overview:
A) Adding a STP for TDM transmission
1.
Add an Originating Signaling Point (OSP).
2.
Add the MGW as the destination signaling point. Set the DSP code to the
signaling point code of the MGW, DSP type to STP, and DSP bear type to
M3UA.
3.
Add an MTP3 link set, an MTP3 link to the link set, and an MTP3 route.
4.
Add the MSC as the destination signaling point. Set the DSP code to the
signaling point code of the MSC, DSP type to A, and DSP bear type to MTP3.
5.
Add an MTP3 route.
6.
Add a CN node.
Page 56

Procedure (TDM):
1.
Add an Originating Signaling Point (OSP).
2.
M3UA.
3.
Add an MTP3 link set, an MTP3 link to the link set, and an MTP3 route.
Example:
ADD OPC: NAME="test", SPX=1, NI=NAT, SPCBITS=BIT14, SPDF=WNF, SPC=260;
ADD N7DPC: NAME="MGW", DPX=1, SPX=1, SPDF=WNF, DPC=270, DPCT=STP, BEARTYPE=MTP3;
ADD MTP3LKS: SIGLKSX=1, DPX=1, NAME="MGWMTP3LKS";
ADD MTP3LNK: SIGLKSX=1, SIGSLC=1, BEARTYPE=MTP2, TCMODE=SEPERATE_PRINCIPAL, ATERIDX=0,
ATERMASK=TS16-0, ASRN=3, ASN=18, MTP2LNKN=1, APN=0, ATSMASK=TS16-0, LKTATE=64K,
NAME="MTP3LNKS1_1";
ADD MTP3RT: DPX=1, SIGLKSX=1, NAME="MGWRT";
Page 57

Procedure (TDM, continued):
4.
Add the MSC as the destination signaling point. Set the DSP code to the
signaling point code of the MSC, DSP type to A, and DSP bear type to MTP3.
5.
Add an MTP3 route.
6.
Add a CN node.
Example:
ADD N7DPC: NAME="MSC", DPX=2, SPX=1, SPDF=WNF, DPC=280, DPCT=A,
BEARTYPE=MTP3;
ADD MTP3RT: DPX=2, SIGLKSX=1, NAME="MSCRT";
ADD GCNNODE: CNNODEIDX=1, DPX=2, DPCGIDX=1, OPNAME="share", CNID=2,
DFDPC=YES, ATransMode=TDM;
Page 58

Procedure overview:
B) Adding a STP for IP transmission
1. Add an M3UA local entity and an SCTP link.
2. Add the MGW as the destination signaling point. Set the DSP code to the
M3UA.
3. Add an M3UA destination entity.
4. Add an M3UA signaling link set, add an M3UA link and an M3UA route.
5. Add the MSC as the destination signaling point.
6. Add an M3UA destination entity.
7. Add an M3UA route.
Page 59

Procedure (IP):
1.
Add an M3UA local entity and an SCTP link.
2.
M3UA.
3.
Add an M3UA destination entity.
Example:
ADD M3LE: LENO=1, SPX=1, ENTITYT= M3UA_IPSP, NAME="LOCALBSC";
ADD SCTPLNK: SRN=1, SN=0, SCTPLNKN=100, MODE=CLIENT, APP=M3UA,
LOCIP1="172.17.15.253", PEERIP1="172.17.12.253", PEERPN=2905,
LOGPORTFLAG=NO, VLANFLAG1=DISABLE, VLANFLAG2=DISABLE,
SWITCHBACKFLAG=YES;
ADD N7DPC: NAME="MGW", DPX=1, SPX=1, SPDF=WNF, DPC=270, DPCT=STP,
BEARTYPE=M3UA;
ADD M3DE: DENO=1, LENO=1, DPX=1, ENTITYT=M3UA_IPSP, NAME="MGW";
Page 60

Procedure (IP, continued):
4.
Add an M3UA signaling link set, add an M3UA link and an M3UA route.
5.
Add the MSC as the destination signaling point.
6.
Add an M3UA destination entity.
7.
Add an M3UA route.
Example:
ADD M3LKS: SIGLKSX=1, DENO=1, WKMODE=M3UA_IPSP, NAME="MGWLKS";
ADD M3LNK: SIGLKSX=1, SIGLNKID=1, SRN=1, SN=0, SCTPLNKN=100, NAME="MGWLNK";
ADD M3RT: DENO=1, SIGLKSX=1, NAME="MGWM3RT";
ADD N7DPC: NAME="MSC", DPX=2, SPX=1, SPDF=WNF, DPC=280, DPCT=A,
BEARTYPE=M3UA;
ADD M3DE: DENO=2, LENO=1, DPX=2, ENTITYT=M3UA_IPSP, NAME="MSCM3DE";
ADD M3RT: DENO=2, SIGLKSX=1, NAME="MSCM3RT";
Page 61
Contents
Page 62
Contents
5.1 Adding a subrack
5.2 Adding XPUa/XPUb boards
5.3 Adding interface boards
Page 63
Adding subracks to the BSC

Prerequisites
Network design is complete.
Network design involves planning of traffic volume in each subrack, planning of the
quantity of subracks, and planning of the quantity of boards and types of boards.
Tools required for adding subracks are ready. The tools are the ESD wrist strap,
Phillips screwdriver, flat-head screwdriver, ESD box or bag, dustfree cotton cloth,
and fiber cleaner.
The parts needed for adding subracks are all ready. The parts include subracks,
screws, power cables, PGND cables, and signal cables connecting new subracks and
NEs.
Subracks to be added are ready.
If there is space in the cabinet, add a subrack there. If idle space is not available,
another cabinet is needed.
Check whether the program files of the OMU board in the OMU active workspace
installation directory\bin\fam are correct
Page 64

Context
When original subracks are in effective mode, adding subracks does not affect
ongoing service.
When original subracks are in ineffective mode, the BSC6900 needs restarting
to add a subrack. Restarting the BSC6900 interrupts the ongoing services.
Therefore, add new subracks when original subracks are in effective mode.
CAUTION:
To avoid damage to the boards, ASIC chips, or other electronic components,

wear an ESD wrist strap. Ensure that it is properly connected to the ESD
connector on the cabinet. If no ESD wrist strap or no proper grounding point is
available, wear ESD gloves.
It is recommended that you use the same board type to replace the old board.
To use a board of the different version to replace the board, contact Huawei
for technical support.
Page 65

Procedure overview (part 1):
1.
Set the DIP switches according to the location of the new subrack.
2.
Turn off the power switch for the new subrack.
3.
Make sure floating nuts are installed in the mounting bar.
4.
Slide the subrack along the guiding rail into the cabinet, and fasten the
screws.
5.
Install the power cables for the new subrack.
6.
Install the boards in the new subrack.
7.
Install the total four network cables.
8.
Install other connecting cables for the new subrack.
9.
Check whether cables in the new subrack are connected correctly.
10. Attach the Engineering Labels to the Signal Cables.

11. Turn on the power switch for the new subrack.
Page 66

Procedure overview (part 2):
12. Log in to the LMT, and check the subrack configuration mode.
13. Via MML command add a subrack.
14. Set the new subrack to effective mode.
15. Add the XPUa/XPUb board.
16. Add the DPU board.
17. Add the interface board.
18. Check the process of adding the boards with the LMT.
19. Check whether alarms such as board fault alarms are reported.
20. Query the software version of the new board.
21. Perform dialing tests and browse webpages to check that service is normal.
Page 67

Procedure:
1. Set the DIP switches according to the location of the new subrack.
Caution:
Wear an ESD wrist strap and connect it to the ESD connector on the cabinet
before you perform the operation.
Set the DIP switches before powering on the subrack. Settings of the DIP
switches after powering on the subrack are invalid.
Set the DIP switches for the new subrack. Different subracks must have
different settings of DIP switches. If two subracks in the BSC6900 share the
same settings of the DIP switches, services on the two subracks will be
disrupted.
Page 68

2.
Turn off the power switch for the new subrack
When the MPR is configured with the OMU board, the distribution of power
switches of the MPR is the same as the distribution of power switches on the
power distribution box of the EPR/TCR.
The mapping is different when the MPR is configured with GBAM.
with OMU
with GBAM
Page 69

3.
Make sure floating nuts are installed in the mounting bar at the front side of
the cabinet. If no floating nuts are available, take floating nuts out of the ESD
bag at the bottom of the cabinet and install them in the place highlighted in
yellow shown below.
4.
Slide the subrack along the guiding rail into the cabinet, and fasten the
screws
Page 70

5.
Install the power cables for the new subrack.
6.
Install the boards in the new subrack.
Notes:
The figure below shows the cabling for a rack configured with OMU.
In case of other configurations refer to the Huawei documentation
Page 71

7.
Install the total four network cables
Prerequisites:
The straight-through cables to be installed are available.
The required cable ties and wax strings are available.
The tools required for the installation are available. The tools are ESD gloves or ESD wrist
strap, and wire cutter.
Caution:
Wear an ESD wrist strap and connect it to the ESD connector on the cabinet before you
perform the operation.
Do not forcefully bend the inter-SCUb SFP+ high-speed cable, which contains an optical
fiber. Ensure that the bending radius of the cable is equal to or more than 25 mm when
binding the cable.
Page 72

8.
Install other connecting cables for the new subrack.

Inter-TNU cables
Clock signal cables
Ethernet cables
E1/T1 cables
Optical cables
GPS surge protection
9.
Check whether cables in the new subrack are connected correctly.
10. Attach the Engineering Labels to the Signal Cables.

11. Turn on the power switch for the new subrack.
Page 73

12. Log in to the LMT, and check the subrack configuration mode.
13. Via MML command add a subrack.
14. Set the new subrack to effective mode.
Example:
ADD SUBRACK: SRN=2, SRName="test2", CONNPWR=NO, TYPE=EPS, WORKMODE=GO,
SCUTYPE=SCUa;
SET CFGDATAEFFECTIVE: SRN=1;
Page 74

15. Add the XPUa/XPUb board.
16. Add the DPU board.
17. Add the interface board.
18. Check the process of adding the boards with the LMT.
19. Check whether alarms such as board fault alarms are reported.
20. Query the software version of the new board.
Example:
DSP BRDVER: SRN=0, SN=7;
Page 75
Contents
Page 76
Adding XPUa/XPUb boards

Prerequisites:
The XPUa/XPUb board is ready.
ESD wrist strap, Phillips screwdriver, flat-head screwdriver, ESD box or bag,
and dustfree cotton cloth for installing boards are ready.
Caution:
To avoid damage to the boards wear an ESD wrist strap properly.
When replacing boards of different versions contact Huawei for technical

support
When the board types bound to the MPU subsystem are not complete or when
the proportion of the boards is inappropriate, the exchange message through
the MPU subsystems surges, which affects the system stability.
Page 77
Adding XPUa/XPUb boards

Procedure:
1.
Install the SPUb boards
2.
Add the XPUa/XPUb board
3.
Query the new boards status
4.
Check alarms for the new board
5.
Configure BTS / Reparent BTS to the new board
Example:
ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=SPUb, LGCAPPTYPE=UCP, SN=4,

MPUSUBRACK=0, MPUSLOT=0;
DSP BRD: SRN=0, SN=7;
Page 78
Contents
Page 79
Adding interface boards

Prerequisites:
Cables for connecting the interface boards are ready
Peer equipment and transmission equipment connected to interface boards are

ready.
ESD wrist strap, Phillips screwdriver, flat-head screwdriver, ESD box or bag, and
dustfree cotton cloth for installing boards are ready.
Caution:
When replacing boards of different versions contact Huawei for technical support
When the Data Configuration Modes of the subrack is effective mode, adding
interface boards does not interrupt ongoing services of the BSC6900.
When the subrack is in ineffective mode, the subrack needs to be restarted to add
boards. Restarting subracks interrupts ongoing services.
Page 80

Procedure overview:
1.
Set dip switches of the board if necessary.
2.
Install the signal cable (Ethernet cable or optical fiber) and cables for
extracting clock signals.
3.
Install the board.
4.
Attach the Engineering Labels to the Signal Cables.
5.
Configure the new interface boards.
6.
Check the port according to the board type.
7.
Query the new board status.
8.
Check whether board fault alarms are reported.
9.
Check whether software versions of the new boards are correct
Page 81

Procedure:
1.
Set dip switches of the board if necessary.
2.
Install the signal cable (Ethernet cable or optical fiber) and cables for
extracting clock signals.
3.
Install the board.
4.
Attach the Engineering Labels to the Signal Cables.
5.
Configure the new interface boards.
Page 82

Procedure:
6.
Check the port according to the board type.
7.
Query the new board status.
8.
Check whether board fault alarms are reported.
9.
Check whether software versions of the new boards are correct
Example:
DSP OPT: SRN=0, SN=16, BT=POUc, PFMT=GROUP, PN=0;
CMP BRDVER: SRN=0;
Page 83
Contents
Page 84
Contents
6.1 Removing a DPUc/DPUd/DPUf/DPUg Board
6.2 Removing a subrack
Page 85
Removing a DPUc/DPUd/DPUf/DPUg Board

Prerequisites:
Risk assessment is complete: Removing the board decreases the capacity of

the BSC6900. Risk evaluation should evaluate the impact on the network.
ESD wrist strap, Phillips screwdriver, flat-head screwdriver, ESD box or bag,
and dustfree cotton cloth for installing boards are ready.
Caution:
Do not remove all the DPUc, DPUd, DPUf, and DPUg boards at a time. Retain
at least one board of each type for each subrack to sustain normal services.
Page 86
Removing a DPUc/DPUd/DPUf/DPUg Board

Procedure:
1.
Logically disable the DPUc/DPUd/DPUf/DPUg board.
2.
Physically remove the DPUc/DPUd/DPUf/DPUg board
3.
Via MML remove the DPUc/DPUd/DPUf/DPUg board
Example:
INH BRD: INHT=LOGIC, SRN=m, SN=n;
RMV BRD: SRN=m, SN=n;
Page 87
Removing a subrack
Prerequisites:
Risk assessment is complete: NodeB reparenting interrupts its ongoing services. Risk
evaluation should evaluate the impact on the network.
Network planning is complete: This involves planning of NodeB carried by each

subrack, by the XPUa/XPUb board or by each subsystem.
ESD wrist strap, Phillips screwdriver, flat-head screwdriver, ESD box or bag, and
dustfree cotton cloth for installing boards are ready.
Caution:
Removing subracks interrupts services on these subracks.
Page 88
Removing a subrack
Procedure:
1.
Configure the target subrack to achieve NodeB reparenting
2.
Remove the XPUa/XPUb board.
3.
Remove the DPU board.
4.
Remove the interface board.
5.
Remove the MPU board.
6.
Remove the subrack.
7.
Disconnect all the signal cables in the subrack.
8.
Unfasten the screws in the subrack
9.
Slide the subrack out of the cabinet
Example:
RMV SUBRACK: SRN=4;
Page 89
Contents
Page 90

Prerequisites: You have
queried the slot No. for the OMU
queried the OMU version and whether the OMU is in single or dual mode
queried the OMU language version and Workspaces
queried the OMU product running mode
Context:
If the working mode is changed from single-OMU mode to dual-OMU mode,

apply the settings to both the active and standby OMUs. If the working mode
is changed from dual-OMU mode to single-OMU mode, apply the settings to
only the working OMU.
If the working mode of the OMU is changed from single-OMU mode to dualOMU mode, ensure that the operating system and version of the active OMU
are the same as those of the standby OMU.
Page 91

Context :
Changing the working mode is possible

using the OMU applications
without using the OMU applications
The following shows the procedure without using OMU applications. For the
other procedure refer to the documentation.
Examples:
LST BRD: SRN=0, SN=6, LstFormat=VERTICAL;
DSP OMU:;
LST OMUAREA:;
LST MBSCMODE:;
Page 92

Procedure overview:
1.
Stop the omud on the original working OMU.
2.
Start the omutool on the original working OMU.
3.
Set the working mode of the OMU to active/standby mode.
4.
Start the omud on the original working OMU.
5.
Insert an OMUa/OMUb/OMUc board into the slot for the standby OMU.
6.
Change the IP addresses and masks of the OMU Ethernet adapters.
7.
Start the omud on the standby OMU.
8.
Change the password of the operating system the standby OMU.
9.
Via MML add the OMU.
10. Check that Data-sync state is Data synchronization normal.

11. Connect an Ethernet cable to the Ethernet port on the added OMU.
Page 93

Procedure:
1.
Stop the omud on the original working OMU.
Caution:
When the omud is stopped, all the OMU service processes will also stop. In
turn, the OMU stops providing services for the BSC6900. Therefore, perform
this task with caution.
When the omud is stopped, the connection between the OMU and the
peripheral devices is terminated if you have logged in to the OMU through
the external virtual IP address.
Page 94

2.
Start the omutool on the original working OMU.
3.
Set the working mode of the OMU to active/standby mode.
4.
Start the omud on the original working OMU.
5.
Insert an OMUa/OMUb/OMUc board into the slot for the standby OMU.
Warning:
You should start the standby OMU five minutes after the active OMU is
started to avoid the problem that the two OMUs compete for active state.
Thus, data loss can be avoided.
Page 95

6.
Change the IP addresses and masks of the OMU Ethernet adapters.
7.
Start the omud on the standby OMU.
8.
Change the password of the operating system the standby OMU.
9.
Via MML add the OMU.
10. Check that Data-sync state is Data synchronization normal.

11. Connect an Ethernet cable to the Ethernet port on the added OMU.
Example:
ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUa, LGCAPPTYPE=OAM, SN=23;
DSP OMU:;
Page 96
Contents
Page 97
Contents
8.1 Changing the Transmission Mode on the A Interface
8.2 Reconfiguring the Transmission Mode on the Ater Interface
8.3 Changing the Transmission Mode on the Gb Interface
8.4 Changing the Transmission Mode on the Abis Interface
Page 98
Changing the Transmission Mode on

the A Interface
Prerequisites:
The peer end supports the A over IP mode.
The FG2a/FG2c/GOUa/GOUc/PEUa/POUc is configured in the MPS/EPS subrack.
Networking planning is complete.
The license A over IP has been activated.
The DPUc board is configured in MPS/EPS of BSC6900.
Context:
In A over IP mode, only system clock is supported. The line clock is not supported.
Changing the transmission mode on the A interface involves the following scenarios:
Changing the transmission mode from TDM to IP over FE/GE
Changing the transmission mode from TDM to IP over E1
The following example is for changing to IP over FE/GE
Page 99

the A Interface
Procedure overview:
1.
In case of TDM transmission in BM/TC separated mode remove Ater interface

data.
2.
Remove A interface data.
3.
Remove the TDM-based interface boards from all the subracks and other service
processing boards from the TCS.
4.
In case of TDM transmission in BM/TC separated mode remove TCS data.
5.
Set the Service mode to AIP(AIP).
6.
Add an IP-based board.
7.
Configure the Physical Layer and Data Link Layer for the FG2a/FG2c/GOUa/GOUc
Board.
8.
Configure the Control Plane of the A Interface (over IP).
9.
Configure the Mapping Between Service Types and Transmission Resources for the
Adjacent Node.
10. Perform the operations in Configuring the User Plane of the A Interface (over IP).
Page 100

the A Interface
Procedure:
1.
In case of TDM transmission in BM/TC separated mode remove Ater interface

data.
Example:
RMV ATERCONSL: ATERSLID=1;
RMV ATEROML: ATEROMLINX=0;
RMV ATERE1T1: SRN=0, SN=16, PN=0;
RMV ATERCONPATH: ATERIDX=0;
Page 101

the A Interface
2.
Remove A interface data.
3.
Remove the TDM-based interface boards from all the subracks and other
service processing boards from the TCS.
Note:
Before removing the A interface board, ensure that the line clock carried on
the A interface board in the TCS is removed.
Example:
RMV BRD: SRN=0, SN=10;
Page 102

the A Interface
4.
In case of TDM transmission in BM/TC separated mode remove TCS data.
5.
Set the Service mode to AIP(AIP).
Note:
After the service mode of the BSC is changed, the resources to each subrack
need to be reloaded. Therefore, you need to run the RST BSC to reset the
BSC.
Example:
RMV SUBRACK: SRN=4;
SET BSCBASIC: SERVICEMODE=SEPARATE;
RST BSC: BSCID=0;
Page 103

the A Interface
6.
Add an IP-based board.
7.
Configure the Physical Layer and Data Link Layer for the FG2a/FG2c/GOUa/GOUc Board.
Note:
In link non-aggregation mode, run the ADD ETHIP command to add the IP
address of the Ethernet port. When multiple VLAN gateways are planned,
repeat this step until all the IP addresses are added.
Example:
ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=FG2c, LGCAPPTYPE=IP, SN=12;
LST ETHPORT: SRN=2, SN=21, PN=0, LstFormat=VERTICAL;
ADD ETHIP: SRN=3, SN=20, PN=0, IPINDEX=0, IPADDR="10.171.35.123",
MASK="255.255.255.0";
Page 104
Changing the Transmission Mode on the A Interface

8.
Configure the Control Plane of the A Interface (over IP).
Prerequisites:
The M3UA local and destination entities are configured.
The physical layer and data link layer of the A interface are configured.
Example:
ADD GCNNODE: CNNODEIDX=0, DPX=1, DPCGIDX=0, OPNAME="MBSC", MSCCAP=0, CNID=0,
MSCSTATUE=NORMAL, DFDPC=YES;
ADD SCTPLNK: SRN=1, SN=2, SCTPLNKN=1, MODE=SERVER, APP=M3UA, DSCP=62, LOCIP1="11.11.11.11",
PEERIP1="11.11.11.111";
ADD M3LKS: SIGLKSX=0, DENO=1, LNKSLSMASK=B1001, TRAMODE=M3UA_LOADSHARE_MOD,
WKMODE=M3UA_ASP, PDTMRVALUE=6, NAME="SGSN";
ADD M3RT: DENO=1, SIGLKSX=2, PRIORITY=1, NAME="SGSN";
ADD M3LNK: SIGLKSX=2, SIGLNKID=1, SRN=1, SN=2, SCTPLNKN=2, PRIORITY=2, LNKREDFLAG=M3UA_SLAVE_MOD,
NAME="MBSCMSC";
ADD ADJNODE: ANI=3, NAME=MSC", NODET=A;
Page 105
Changing the Transmission Mode on the A Interface

9.
Configure the Mapping Between Service Types and Transmission Resources for the
Adjacent Node.
Example:
ADD TRMMAP: TMI=20, REMARK="A", ITFT=A, TRANST=IP;
ADD TRMFACTOR: FTI=10, REMARK=Test";
ADD ADJMAP: ANI=11, ITFT=A;
10. Perform the operations in Configuring the User Plane of the A Interface (over IP).
Example:
ADD IPPATH: ANI=0, PATHID=1, ITFT=A, TRANST=IP,PATHT=BE, IPADDR="80.1.1.1",
PEERIPADDR="10.161.0.1", PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000,
VLANFLAG=DISABLE, PATHCHK=ENABLED, ECHOIP="22.22.22.20", CHECKT=UDP;
Page 106
Contents
Page 107
Reconfiguring the Transmission Mode

on the Ater Interface
Prerequisites:
The POUc board is configured in the TCS and the MPS/EPS.
The optical cable on the POUc board is connected.
Network planning is complete.
Context:
The Ater interface does not support IP over E1/T1/FE/GE. It supports only IP
over STM-1, and only the POUc board supports IP over Ater.
Caution:
Reconfiguring the transmission mode applied over the Ater interface will
interrupt the services of the BSC6900. Therefore, perform the operation when
the traffic is low, for example, in the early morning.
The whole process (including board restart) takes about 20 minutes.
Page 108

Procedure:
1.
Remove the Ater OML between the MPS and the main TCS.
2.
Remove the Ater connection path.
3.
Add an Ater connection path.
4.
Add the Ater OML between the MPS and the main TCS.
5.
Add an Ater signaling link between the MPS/EP and the TCS.
Page 109

Example:
RMV ATEROML: ATEROMLINX=1;
RMV ATERCONPATH: ATERIDX=0;
ADD ATERCONPATH: ATERIDX=0, BMSRN=0, BMSN=18, BMPN=0, TCSRN=3, TCSN=14,
TCPN=0;
ADD ATEROML: ATEROMLINX=0, ATERPIDX=0, TSMASK=TS3-1&TS4-1&TS5-1&TS6-1&TS71&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1;
ADD ATERSL: BTCFLAG=CFGBM, ATERIDX=0, ATERMASK=TS1-0&TS2-1&TS3-0&TS4-0&TS50&TS6-0&TS7-0&TS8-0&TS9-0&TS10-0&TS11-0&TS12-0&TS13-0&TS14-0&TS15-0&TS160&TS17-0&TS18-0&TS19-0&TS20-0&TS21-0&TS22-0&TS23-0&TS24-0&TS25-0&TS260&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0, TNMODE=TRRS;
ADD ATERSL: BTCFLAG=CFGTC, BSCTID=0, ATERIDX=0, ATERMASK=TS1-0&TS2-1&TS30&TS4-0&TS5-0&TS6-0&TS7-0&TS8-0&TS9-0&TS10-0&TS11-0&TS12-0&TS13-0&TS140&TS15-0&TS16-0&TS17-0&TS18-0&TS19-0&TS20-0&TS21-0&TS22-0&TS23-0&TS240&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0, TNMODE=TRRS;
Page 110
Contents
Page 111

the Gb Interface
Prerequisites:
The built-in PCU is used. The DPUd board is configured.
The peer end supports the Gb over IP mode.
A PEUa board is replaced by FG2a/FG2c/GOUc board.
The license Gb over IP has been activated.
Context:
To improve the transmission efficiency, increase the throughput, and reduce the
transmission delay on the Gb interface, you can change the transmission mode on
the Gb interface from FR to IP.
Page 112

the Gb Interface
Procedure overview:
1.
Remove the PTPBVC corresponding to the cell.
2.
Remove NSVC data.
3.
Remove BC data.
4.
Remove NSE data.
5.
Remove the interface board for FR transmission mode.
6.
Add the NSE.
7.
Configure the NSVL.
8.
Add the PTPBVC and to bind the GPRS cell with the NSE.
Page 113

the Gb Interface
Procedure:
1.
Remove the PTPBVC corresponding to the cell.
2.
Remove NSVC data.
3.
Remove BC data.
Example:
RMV PTPBVC: NSEI=9, BVCI=2;
RMV NSVC: NSVCIDX=1;
RMV BC: SRN=0, SN=18, BCID=11;
Page 114

the Gb Interface
4.
Remove NSE data.
5.
Remove the interface board for FR transmission mode.
6.
Add the NSE.
Example:
RMV NSE: NSEI=1;
ADD NSE: NSEI=0, SRN=0, SN=0, PT=GB_OVER_FR, OPNAME="46000", CNID=0;
Page 115

the Gb Interface
7.
Configure the NSVL.
Add an NSVL at the BSC6900 side.
Optional: When the NSE is in static configuration mode, add the NSVL at the
SGSN side.
8.
Add the PTPBVC and to bind the GPRS cell with the NSE.
Example:
ADD NSVLLOCAL: LOCALNSVLI=0, NSEI=180, IP="1.2.3.4", UDPPN=55555, SRN=0, SN=22;
ADD NSVLREMOTE: REMOTENSVLI=1, NSEI=180, IP="2.2.2.2", UDPPN=55555;
ADD PTPBVC: NSEI=181, BVCI=5, IDTYPE=BYID, CELLID=0;
Page 116
Contents
Page 117

the Abis Interface
Prerequisites:
The peer end supports the Abis over IP mode.
The FG2a/FG2c/GOUa/GOUc/PEUa/POUc board is configured.
The license for Abis over IP has been activated.
The DPUc board is configured in the MPS/EPS of the BSC6900.
The built-in PCU is used. If an external PCU is used, replace the external PCU with a
built-in PCU and configure the required data.
Context:
Changing the transmission mode on the Abis interface consists of the following:
Changing the transmission mode from TDM to IP over FE/GE
Changing the transmission mode from TDM to IP over E1
The example below focuses on IP over FE/GE
Page 118

the Abis Interface
Procedure overview:
1.
Reset the BTS.
2.
Deactivate the BTS.
3.
Remove the connection to the BTS.
4.
Add an IP-based interface board on the BSC.
5.
Configure the physical layer and data link layer for the
FG2a/FG2c/GOUa/GOUc board.
6.
Add an adjacent node.
7.
Configure the user plane in IP transmission mode.
8.
Modify the BTS and set Service Type to IP (IP_OVER_FE/GE).
Page 119

the Abis Interface
Procedure overview (continued):
9.
Add the equipment serial number (ESN) of the BTS.
10. Add a board in IP transmission mode to the BTS.

11. Set the IP address of the BTS ports.
12. Set the BSC IP.
13. Configure the IP clock for the BTS.
14. Activate the BTS.
Page 120

the Abis Interface
Procedure:
1.
Reset the BTS.
2.
Deactivate the BTS.
Note:
If the level 4 reset is not performed on the BTS, the transmission mode fails
to be changed from TDM to IP, leading to intermittent connectivity on the
operation and maintenance links.
When detecting intermittent connectivity on an operation and maintenance

link, the BTS waits for 15 minutes and then restarts automatically.
Example
RST BTS: TYPE = BTSSOFT, IDTYPE = BYID, BTSID = 0, LEVEL = 4-LEVEL;
DEA BTS: IDTYPE=BYID, BTSID=0;
Page 121

the Abis Interface
3.
Remove the connection to the BTS.
4.
Add an IP-based interface board on the BSC.
Example:
RMV BTSCONNECT: IDTYPE=BYNAME, BTSNAME="BTS3012", INPN=1;
ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=FG2c, LGCAPPTYPE=IP, SN=10, ISTCBRD=NO,
MPUSUBRACK=0, MPUSLOT=2;
Page 122

the Abis Interface
5.
Configure the physical and data link layer for the FG2a/FG2c/GOUa/GOUc
board.
Set the Ethernet port attributes.
Optional: Configure Ethernet port backup and add the device IP address of the
board in the case of logical IP networking.
In link non-aggregation mode:

Add the IP address of the Ethernet port. When multiple VLAN gateways are planned,
repeat this step until all the IP addresses are added.
Optional: Add an IP address to the VLAN ID mapping table.
In link aggregation mode, complete the following steps:

Add a link aggregation group.
Add a link to the link aggregation group.
Add the IP address of the link aggregation group.
Page 123

the Abis Interface
5.
Configure the physical and data link layer for the FG2a/FG2c/GOUa/GOUc
board.
Example (non-aggregation mode):

SET ETHPORT: SRN=0, SN=24, BRDTYPE=FG2a, PTYPE=FE, PN=0, AUTO=ENABLE, MTU=1500;
ADD ETHREDPORT: SRN=0, SN=18, PN=0;
ADD DEVIP: SRN=0, SN=24, DEVTYPE=LOGIC_IP, IPADDR="10.171.35.123";
ADD ETHIP: SRN=3, SN=20, PN=0, IPINDEX=0, IPADDR="10.171.35.123",
MASK="255.255.255.0";
ADD VLANID: SRN=0, SN=14, IPADDR="10.10.10.11", VLANID=5;
Page 124

the Abis Interface
Example (aggregation mode):
SET ETHPORT: SRN=0, SN=24, BRDTYPE=FG2a, PTYPE=FE, PN=0, AUTO=ENABLE, MTU=1500;
ADD ETHREDPORT: SRN=0, SN=18, PN=0;
ADD DEVIP: SRN=0, SN=24, DEVTYPE=LOGIC_IP, IPADDR="10.171.35.123";
ADD ETHTRK: SRN=0, SN=18, TRKN=0, WORKMODE=LOAD_SHARING,
LACPMODE=STATIC_LACP, FLOWCTRLSWITCH=ON, FCINDEX=1;
ADD ETHTRKLNK: SRN=0, SN=18, TRKN=0, TRKLNKSN=18, TRKLNKPN=0,
WORKMODE=LOAD_SHARING;
ADD ETHTRKIP: SRN=0, SN=8, TRKN=0, IPINDEX=0, IPADDR="9.9.9.9",
MASK="255.255.255.0";
Page 125

the Abis Interface
6.
Add an adjacent node.
7.
Configure the user plane in IP transmission mode:
Add an IP path for the user plane
In case of layer 3 networking it may be necessary to configure an IP route on

the BSC side.
Example:
ADD ADJNODE: ANI=3, NAME="BTS-1", NODET=ABIS, BTSIDX=1;
ADD IPPATH: ANI=0, PATHID=1, ITFT=ABIS, TRANST=IP,PATHT=BE, IPADDR="80.1.1.1",
PEERIPADDR="10.161.0.1", PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000,
VLANFLAG=DISABLE, PATHCHK=ENABLED, ECHOIP="22.22.22.20", CHECKT=UDP;
ADD IPRT: SRN=3, SN=20, DSTIP="35.35.35.35", DSTMASK="255.255.255.255",
NEXTHOP="26.26.26.28", PRIORITY=HIGH, REMARK="route1";
Page 126

the Abis Interface
8.
Modify the BTS and set Service Type to IP (IP_OVER_FE/GE).
Example:
MOD BTS: IDTYPE=BYID, BTSID=0, NEWNAME="bts-3900", SERVICEMODE=IP;
Page 127

the Abis Interface
9.
Add the equipment serial number (ESN) of the BTS.
10. Add a board in IP transmission mode to the BTS.

Perform this step only when the BTS is a double-transceiver BTS
11. Set the IP address of the BTS ports.
Example:
ADD BTSESN: IDTYPE=BYID, BTSID=0, MAINDEVTAB="21021127226T8C007274";
ADD BTSBRD: IDTYPE=BYID, BTSID=9, SRN=2, SN=10, BT=FMU;
SET BTSETHPORT: IDTYPE = BYID, BTSID = 0, PN = 0, MTU = 1500;
Page 128

the Abis Interface
12. Set the BSC IP.
13. Configure the IP clock for the BTS.
14. Activate the BTS.
Example:
SET BTSIP: IDTYPE = BYID, BTSID = 0, BTSIP = 3.6.5.2, BSCIP = 1.1.0.1;
SET BTSIPCLKPARA: IDTYPE=BYID, BTSID=10, CLKPRTTYPE=PTP, DN=1,
CLKTOPOMODE=PTPOVERUDP, SYNMODE=CONSYN, ISCLKREDUCY=UNSUPPORT,
MASTERIPADDR="10.10.20.1";
ACT BTS: IDTYPE=BYID, BTSID=0, ACTTYPE=ACTALL;
Page 129
BSC6900 GSM
Operation and
Maintenance
www.huawei.com
Objectives

Detail the structure of operation and maintenance

subsystem
Perform the BSC6900 Routine Operation
Perform the BSC6900 Routine Maintenance
Page1
Contents
1. OM System Introduction
2. Operation Right Management
3. Alarm management
4. Log management
5. Device panel management
6. BSC maintenance
7. Routine Maintenance MML
8. Trace management
9. Performance monitoring
10. License Management
11. Board Replacement
Page2
Contents
1.1 OM Network Introduction
1.2 Web LMT Introduction
1.3 LMT Offline Tool
Page3
O&M Network
SRAN O&M Network
Unified M2000/CME Client
for GSM&UMTS
TM
M2000
Unified WEB LMT for
GSM&UMTS
BSC6900
GSM BTS
MBTS(GSM/UMTS)
UMTS NodeB
Page4
System Overview
Page5
Web LMT Introduction

The LMT provides graphical user interface (GUI) for you

to operate and maintain the BSC6900 on the Web page.
The alarm management, trace management, performance

monitoring, and device maintenance can be performed
through menu operations
The MML commands can be run for data configuration

and O&M on the LMT
Page6
LMT Login
OMU external virtual

IP
Page7
Components of Web LMT

Functional Tab
Navigation
Tree
Command Area
Page8
Running an MML Command

1
7
Page9
Batch Running MML Commands
Page10
Querying the Data Configuration Mode

and Data Configuration Rights
Querying the data configuration mode
Querying data configuration rights
Page11
LMT Offline Tool

The Local Maintenance Terminal (LMT) software consists

of:
FTP Client
FTP Server
LMT Offline MML
Convert Management System
Performance Browser Tool
Traffic Recording Review Tool
Page12
Questions
There are two modes the data configuration: effective

mode and ineffective mode, please describe what the
difference between these two mode, and which
command is used to change the data configuration mode?
Page13
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page14
Contents
2.1 Basic Concepts
2.2 Management of User Accounts
2.3 Management of Command Groups
Page15
User Types
Local user
Being created and authorized by MBSC LMT
The internal operator is admin, and the

default password is 11111111
The external operators are divided into five

levels. Each level has different authorities
EMS user
Being created, managed and authorized by

M2000
The authorized EMS users can also log in to

the M2000 server through the M2000 client
for BSC6900 operations.
Page16
Command Group
The BSC6900 system uses 32 command groups (G_0 to

G_31) to manage commands. Different command groups
can be assigned to different operators, so that they will
have different operation authorities.
Groups G_0 to G_14 are predefined by the system, the

contents cannot be changed
Groups G_15 to G_31 are initially null, the contents can be

defined.
Page17
Operation Rights
Operator level
ADMINISTRATOR
OPERATOR
USER
GUEST
CUSTOM
Authorized command
group
G_0 - G_14
Authority
Remarks
All authorities
Authorities of
USER-level operator
Data configuration
Authority of
GUEST-level
G_0, G_2, G_4, G_6 - G_14
operator
System O&M
G_0, G_2, G_4, G_6, G_8, G_13 Data query
G_0, G_2 - G_14
The authorities are

predefined by the
system and cannot
be changed.
Changeable; different
Command groups will be
The authority will
CUSTOM-level
assigned to the account when be specified during
operators can have
it is added.
account addition
different authorities.
Page18
Management of User Accounts

Creating an External User Account: ADD OP
Page19
Management of User Accounts

Changing the Password of the Active User Account
Setting Password Policy: SET PWDPOLICY
Page20
Management of Command Groups

Querying a Command Group: LST CCG
Adding Commands to Command Group: ADD CCG
Listing Command Groups of Operator Levels: LST OPCG
Page21
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page22
Contents
3. Alarm Management
3.1 Basic Concepts
3.2 Monitoring Alarms
3.3 Managing the Shielded Alarm
3.4 Managing the Alarm Logs
Page23
Alarm Classification
Alarm Type
Alarm Severity
Fault alarm
Critical alarm
Event alarm
Major alarm
Minor alarm
Warning alarm
The fault alarm

Classification
Cleared alarm
Active alarm
Page24
Alarm Box
BSC6900 uses the Huawei universal alarm box. The

BSC6900 alarm box provides audible and visual
indications based on the alarm severity. It is optional and
the BSC6900 can be configured with only one alarm box.
Page25
Monitoring Alarms
Browsing
Alarms
Querying
Alarm
Handling
Suggestions
Monitoring Alarms
Querying
and
Modifying the Alarm
Configuration
Filtering
Fault
Alarm
Page26
Browsing Alarm/Event
Page27
Querying the Alarm Log
Page28
Querying and Modifying the Alarm

Configuration
Page29
Filtering Fault Alarm/Event
Page30
Managing the Shielded Alarm

Adding
Shield of
Alarm Object
ADD OBJALMSHLD
Managing the
Shielded Alarm
Listing
Shield of
Alarm Object
LST OBJALMSHLD
Setting
Alarm
Shield Flag
SET ALMSHLD
Page31
Managing the Alarm Logs

Querying
the
Alarm Logs
LST ALMLOG
Managing the
Alarm Logs
Setting
Storage Conditions
of Alarm Logs
SET ALMCAPACITY
Querying
Storage
Conditions of Alarm Logs
LST ALMCAPACITY
Page32
Querying the Alarm/Event Log
Page33
Querying Storage Conditions of

Alarm Logs
LST ALMCAPACITY
Page34
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page35
Contents
4. Log Management
4.1 Basic Concepts
4.2 Querying Logs
4.3 Log Storage Conditions Management
Page36
Log Types
Operation log:
The operation log refers to all the real-time operation

information recorded in the OMU database
Security log:
The security log refers to the NE or EMS information related

to security events such as login, logout, and authorization
Running log:
The running log refers to the system running information of

the host recording in real time
Page37
Querying Logs
Querying Operation Logs: LST OPTLOG
Querying Security Logs: LST SECLOG
Page38
Log Storage Conditions Management
Querying Log
Storage Conditions
LST LOGLIMIT
Log Storage
Conditions
Management
Setting Log
Storage Conditions
SET LOGLIMIT
Exporting Logs
EXP LOG
Page39
Log Storage Conditions

Management
Setting Log Storage Conditions: SET LOGLIMIT
Exporting Logs: EXP LOG
Page40
Questions
If the number of logs exceeds the set count limit, what

operation the system will perform?
What is the function of COL LOG, and how to get path

the log result?
After log exported, what kind of methods could we

use to download the log files to local PC?
Page41
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page42
Contents
5.1 Basic Concepts
5.2 Device Panel Operations
5.3 Emulation Panel Operations
Page43
Introduction to the Device Panel
Page44
Introduction to the Emulation Panel
Double-click the
peripheral of the
displayed device panel
Page45
Device Panel Operations

Querying the Status of an E1/T1 Port
Querying the CPU Usage
Querying the BSC Board Clock Status
Querying the BSC Board Information
Resetting the BSC Board
Switching Over the BSC Boards
Page46
Emulation Panel Operations

Querying the Status of an FE Port
Querying the Status of an GE Port
Querying the Status of an Optical Port
Querying the DSP Status of a DPU
Querying Alarm LED Information
Page47
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page48
Contents
6. BSC maintenance
6.1.Maintaining the Equipment
6.2 Maintaining Transmission and Signaling
6.3 Maintaining BSC User Resources
Page49
Browsing Configuration Data

Browse the configuration data, including the

configuration data of BSCs, BTSs, TRXs, and channels.
Browse All/Save as
Page50
Backing Up Data
Backup files in
OMU
Download the
backup file to a
local PC
Page51
Restoring Data
Page52
Maintaining device
Querying the BSC Board

Information
Querying BSC Board Clock

Status
Switching over the BSC

Boards
Maintaining Fan Box
Maintaining the Power

Distribution Box
Page53
Querying the BSC Board Information

You can query the status of a board through menu

operations or through MML commands.
Page54
Querying BSC Board Clock Status

You can query the clock status of the BSC board.
Page55
Switching over the BSC Boards

You can switch over the active BSC board and the standby BSC
board. When the active board is faulty, you can switch all the
services over to the standby board to ensure the normal
operation of the system.
Page56

You can reset the BSC board, the CPU on the XPUa
board, and the DSP on the DPU board.
Page57
Maintaining Transmission and Signaling

Maintaining Signaling
Maintaining LAPD Link
Querying Ater Link Status
Maintaining SCCP Links
Maintaining MTP3 Links
Querying the Status of
Maintaining Transmission
Querying the Interface

Board Port Information
Looping Back the Interface

Board Port/Timeslot
Maintain IP links
MTP2 Links
Page58
Maintaining LAPD Link

You can query the status of the OML, RSL, EML, and ESL, and
the status of the PBSL when the PCU is in external mode. In
addition, it also describes how to perform loopback test on
LAPD links and how to reset LAPD links
Page59
Maintaining SS7 Links

Querying the Status of MTP2

Links
Page60

By monitoring the status of the DPCs and subsystems,

you can know whether the SCCP signaling link works
normally.
Page61

You can query the link status, route status, and DSP
status of MTP3 links, and how to activate, deactivate,
disable, and enable MTP3 links based on the query result.
Page62
Querying the Status of MTP2 Links

You can query the status of an MTP2 link.
Page63
Maintaining BSC User Resources

Maintain User
Resource
Maintain Interface
Resource
Querying DSP
Resources
Maintenance DSP
resource
Querying Single
User Resources
Collecting BSC
Local Information
Querying the Status
of the Abis Interface

Timeslot
Maintaining Ater
Interface Resources
Maintaining the
Circuits on the A
Interface
Maintaining
BSC User
Resources
Loopback
Looping Back Remote Speech
Channel
Testing the Internal Speech Channel
Looping Back DSP Path/Lin
Page64
Maintaining the Circuits on the A Interface

You can query the circuit state on the A interface, and

how to block, unblock, and reset the A interface circuits
based on the query results.
Page65
Querying DSP Resources

You can query the information about the DSP resources

and the DSP link status.
Page66
Maintaining DSP Resources

You can query or modify the DSP status (Inhibited or

Uninhibited).
Page67
Querying Single User Resources

You can query the usage of single-user resources in the CS or

PS domain. The resources include the common information and
mobile information about the MS and the information about
BM subrack and TC subrack.
single user.txt
Page68
Remote Speech Channel Loopback

A interface
to MSC
E
I
U
a
MS A
BTS
T
N
U
a
E
I
U
a
Afer
E
I
U
a
MPS/EPS
T
N
U
a
D
P
U
c
E
I
U
a
MSC
Fix Phone B
TCS
A interface
to MS
E
I
U
a
MS A
BTS
T
N
U
a
MPS/EPS
E
I
U
a
Afer
E
I
U
a
T
N
U
a
D
P
U
c
E
I
U
a
TCS
Page69
MSC
Fix Phone B
Remote Speech Channel Loopback
DSP Channels/Links Loopback

A Interface
E
I
U
a
MS A
T
N
U
a
E
I
U
a
Afer
E
I
U
a
T
N
U
a
MPS/EPS
BTS
D
P
U
c
E
I
U
a
MSC
Fix Phone B
MSC
Fix Phone B
TCS
Abis Interface
E
I
U
a
MS A
BTS
T
N
U
a
MPS/EPS
E
I
U
a
Afer
E
I
U
a
T
N
U
a
D
P
U
c
E
I
U
a
TCS
Page71
DSP Channels/Links Loopback

To check whether voice problems are caused by the

faulty DSP of the BSC.
Page72
Interface Board Port Timeslot Loopback

BM subrack Ater
int. local loopback
Abis int. remote

loopback
Abis int. local

loopback
BM subrack Ater int.

remote loopback
A int. local
loopback
TC subrack Ater int.

remote loopback
TC subrack Ater int.

local loopback
Page73
A int. remote
loopback
Voice Log Analysis

Automatic analysis of one-way audio voice logs facilitates

location of the faulty node causing one-way audio.
Mute_Level 1
Mute_Level 1
Mute_Level 1
Ater Interface
Abis Interface Board
Cell
Page74
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page75
Protocol Structure for the Abis Interface
LLC
relay
Relay
BSSGP
BTSM
BTSM
SCCP
MTP
LAPD
LAPD
L1bis
L1bis
BSC
L1bis
Abis
BTS
Page76
Routine Maintenance MML for the

Abis Interface(Abis over TDM)
DSP LAPDLNK to check whether the Link Access Protocol

on the D channel (LAPD) link on the Abis interface is
normal.
DSP ABISTS to query the timeslot status of the Abis

interface.
To query the Subrack No., Slot No., and Port No. of the timeslots,
run the MML command LST BTSCONNECT .
DSP BTSSTAT to query the status of cells and channels.
Page77
Routine Maintenance MML for the

Abis Interface(Abis over IP)
DSP LAPDLNK to check whether the LAPD link on the

Abis interface is normal.
DSP ADJNODE to query the status of the adjacent node.
DSP IPPATH to query the status of the IP path on the

Abis interface.
DSP BTSSTAT to query the status of the cells and

channels.
Page78
Protocol stack of A Interface

Protocol stack of A Interface over IP

Signaling plane adopts M3UA/SCTP/IP protocol stack.
User plane adopts RTP/UDP/IP protocol stack.

BSC A Interface MSC Server
BSC
A Interface
DTAPBSSMAP
DTAP BSSMAP
SCCP
M3UA
SCTP
IP
MAC/PPP
SCCP
M3UA
SCTP
IP
MAC/PPP
MSC
DTAP BSSMAP
DTAP BSSMAP
SCCP
MTP
Layer1
SCCP
MTP
Layer1
A over TDM
Signaling plane of A over IP

BSC A Interface
Voice
RTP
UDP
IP
MAC/PPP
MGW
Voice
RTP
UDP
IP
MAC/PPP
User plane of A over IP
Page79
Routine Maintenance MML for the A

Interface (A over TDM)
DSP E1T1 to query the status of the E1/T1 ports.
DSP MTP2LNK to query the status of the Message

Transfer Part Level 2 (MTP2) signaling link.
DSP MTP3LNK to query the status of the Message

Transfer Part Level 3 (MTP3) signaling link.
DSP SSN to query the status of the SCCP SSN.
Page80

Interface (A over TDM) (Cont.)
DSP N7DPC to query the status of the SS7 destination

signaling point.
DSP ACIC to query the status of A interface circuits.
Page81

Interface(A over IP)
DSP ETHPORT to query the status of the Ethernet port.
DSP SCTPLNK to query the status of the Stream Control

Transmission Protocol (SCTP) link.
DSP M3LNK to query the status of the MTP3 User

Adaption Layer (M3UA) signaling link.
Page82

Interface(A over IP) (Cont.)
DSP SSN to query the status of the SCCP SSN.
DSP N7DPC to query the status of the SS7 destination

signaling point.
DSP ADJNODE to query the status of the adjacent node.
DSP IPPATH to query the status of the IP path.
Page83
Protocol Structure for the Gb Interface
LLC
relay
Relay
RLC
BSSGP
BSSGP
MAC
Network
Service
Network
Service
GSM RF
L1bis
L1bis
BSS
Gb
SGSN
Page84
Routine Maintenance MML for the Gb

Interface (Gb over FR)
LST NSE to query the configuration of the NSE
DSP BC to query the status of the Bearer Channel (BC)
DSP NSVC to query the status of the Network Service

Virtual Connection (NSVC)
DSP SIGBVC to query the SIG BSSGP Virtual Connection

(SIGBVC) status of the Network Service Entity (NSE)
DSP PTPBVC to query the status of the PTP BSSGP Virtual

Connection (PTPBVC) of the NSE
Page85
Routine Maintenance MML for the Gb

Interface(Gb over IP)
LST NSE to query the configuration of the NSE
LST NSVLLOCAL or LST NSVLREMOTE to query the configuration of

the local or remote NSVL
DSP NSVL to query the status of the Network Service Virtual Link
(NSVL)
DSP IPRT to check whether the route configuration on the Gb

interface is correct.
DSP GBIPROUTE to query the status of the IP connection
DSP SIGBVC to query the SIGBVC status of the NSE.
DSP PTPBVC to query the PTPBVC status of the NSE.
Page86
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page87
Contents
8. Trace management
8.1 Basic Concepts
8.2 GSM Services
Page88
Principles of the Message Tracing

Creating a Tracing Task
Closing a Tracing Task
Reporting Traced Messages to the LMT
Page89
Trace Mode
When you creating the tracing task, two types of Trace

Mode can be selected:
Report
Save to OMU
Page90
Browsing Traced Messages Offline

There are two format of tracing files: .tmf or .csv. Only

the the trace result in .tmf format can be browsed offline
by LMT Offline Tool
BSSAP Trace File
Page91
Basic Tracing Operations

Managing Tracing Tasks
Managing the Trace File
Page92
GSM Service
PS Domain
CS Domain
A Interface Tracing
Um Interface Tracing
Abis Interface Tracing
Ater Interface Tracing
A Single Subscriber
Tracing
GSM Service
Monitoring
Um Interface Tracing
Abis Interface Tracing
Pb Interface Tracing
Gb Interface Tracing
PTP Messages
SIG Messages
A Single Subscriber
Tracing
Tracing Messages on the Cb

Interface
Tracing Group Call Messages
BTS Signaling Messages
Page93
Tracing Messages on the A Interface
Page94
Tracing CS Domain Messages of a

Single Subscriber
Page95
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page96
Service Monitoring
Common Monitoring
GSM Monitoring
Page97
Monitoring CPU/DSP Usage
Page98
Monitoring BER
Page99
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page100
Contents
10.1 Downloading License
10.2 Checking License
10.3 Activating License
10.4 Querying ESN
Page101
Maintaining License
Command group for the license management
Maintaining License
Downloading License file from PC to OMU: DLD LICENSE
IP Address : PC IP Address
FTP User/Password : By default admin/admin
Directory : The path the file is kept in PC
Filename : Filename of the license. (include the
extension, .dat)
Maintaining License
Downloading License file from PC to OMU through FTP Tool
Files in Local
Files in Server
Page104
Maintaining License
Downloading License file from PC to OMU through File Manager
Upload File to the

current directory on
OMU
Page105
Maintaining License
Successful in downloading the file
File is available when LST LICENSE is

executed
Maintaining License
Querying License File in OMU: LST LICENCE
To query the detailed

information of a specified
license file, input the
license file name here.
Maintaining License
Activating License: ACT LICENCE

Sucessful in activation
and License file in use
Maintaining License
Querying ESN for BSC6900: LST ESN
Maintaining License
To remove unused license file from OMU: RMV LICENSE
Maintaining License
To check the License items, including the ESN, version, and
configuration : CHK DATA2LIC
Maintaining License
To check whether the running license on the
host is consistent with that on the OMU : CMP

LICENSE
Maintaining License
To query the license usage of a specified operator of
the NE : DSP LICUSAGE
Contents
3. Alarm management
4. Log management
6. BSC maintenance
8. Trace management
Page114
Contents
11.1 Service Board replacement
11.2 OMU Board replacement
Page115
Replacing a Board
There are two steps in replacing a BSC6900 board: Remove the

faulty board and insert the new board.
Prerequisites
Background information
The tools required for unfastening the board are available,

including ESD wrist strap, Phillips screwdriver, ESD box or ESD
bag, dustfree cloth, and fiber cleaner.
All the boards except the OMUa support hot swap.
Precautions
To avoid electrostatic damage, wear ESD wrist strap correctly

before replacing a board. If an ESD wrist strap is not available or
cannot be properly grounded, please wear ESD gloves.
Page116
Removing the Faulty Board

Unfasten the faulty board from the subrack.
Page117
Inserting the New Board

Insert the new BSC6900 board to the subrack.
Page118
Principles of replacing a board

Replacing an active or standby board

To replace an active board, run SWP BRD to switch over the

boards, pull out the now-standby board, and insert the new
board.
To replace a standby board, pull out the standby board and

insert the new board.
Replacing an independent board

This operation impacts the services and can cause service

interruption. To replace an independent board, transfer the
services of the board, run INH BRD to inhibit the board, pull out
the faulty board, and insert the new board.
Page119
Principles of replacing a board (Cont.)

Replacing a faulty board

If the faulty board is the DPU and only one or several DSPs
are faulty, inhibit the normal DSPs, and replace the faulty
board with a new one.
Verifying the board replacement

Run LST BRD to query the board inhibition status. If the

board is in "Inhibited" status, run UIN BRD to uninhibit the
board and observe whether the board works normally. If
not, check for alarms and analyze the problem according to
the alarm.
Page120
Replacing a DPUc/DPUd/DPUf /DPUg Board

Run the LST SUBRACK command to query the inhibited status of

the board.
If not inhibited, Run the INH BRD command to physically inhibit

the board.
Remove and insert the board.
Run the UIN BRD command to unblock the new board.
Run the DSP BRD command to query the status of the new board.
Check whether a board failure alarm is reported on the LMT.
Run the CMP BRDVER command to check whether the software

version of the new board is consistent with the board version
matching table.
Page121
Replacing an XPUa/XPUb Board

Run the DSP BRD command to query the status of the

XPUa board to be replaced.
If it is active board, Run SWP BRD to switch the board over

to standby
Remove and insert the board.
Run DSP BRD to query the status of the new board, the
CPU status is Active/Standby normal
Run the CMP BRDVER command to check the software

version
Page122
Contents
11.1 Service Board replacement
11.2 OMU Board replacement
Page123
Procedure for replacing an OMU board
Page124
Replacing OMU
A faulty OMU board needs to be replaced to prevent data from

being lost when OMU operation and maintenance are interrupted
due to disconnection between the OMU and host boards.
Prerequisites
The following installation information about the OMU board to be

replaced is obtained:
FTP server password
Administrator password
Operating system (OS) type of the OMU board
Information about all IP addresses of the OMU board, including

external fixed IP address (external gateway IP address), external virtual
IP address, internal fixed IP address, internal virtual IP address, backup
channel IP address of the active and standby OMUs, and debugging IP
address.
Page125
Checking OMU Status Before Replacing

an OMU Board
Check consistency in the configuration data, version software, and

license.
ACT CRC to check whether the configuration data of all BSC6900

host boards and the OMU board is consistent.
CMP BRDVER to check whether the running versions of all

BSC6900 host boards and the OMU board are consistent.
CMP LICENSE to check whether the licenses of all BSC6900 host

boards and the OMU board are consistent.
Run the MML command LST VER. Query and record the value of OS
type.
Run the MML command LST MBSCMODE. Query and record the OMU
mode.
Page126
Checking OMU Status Before Replacing

an OMU Board (Cont.)
Query and record the external gateway IP address of the OMU board
to be replaced.
DSP OMU to query and record the information about the OMU board
to be replaced.
Only one OMU board is configured, Replacing an OMU Board in

Single-OMU Mode.
If two OMU boards are configured, Check whether the OMU board to
be replaced is active or on standby.
The board is in Standby normal state, Replacing the Standby OMU

in Dual-System Mode.
The board is in Active normal state, SWP OMU to manually switch

over the active and standby OMU boards.
Page127
Replacing an OMU Board in SingleOMU Mode

Replacing an OMU board in single-OMU mode will

disconnect the OMU board from the host boards and
interrupt OMU operation and maintenance.
System running data during this period of time will be

lost.
Page128
Replacing an OMU Board in SingleOMU Mode

Replacing an OMU board in single-OMU mode occurs in

one the following scenarios:
Old and New OMU Boards Running the Same OS
Old OMU Board Running Dopra Linux and New OMU Board
Running Suse Linux/Windows
Old OMU Running Suse Linux and New OMU Running Dopra
Linux
Old OMU Running Windows and New OMU Running Dopra

Linux
Page129
Old and New OMU Boards Running the

Same OS
Replace an OMU board of a BSC6900 configured with

only one OMU board when the OMU board to be
replaced and the new OMU board run the same
operating system (OS).
BKP DB to back up system files to the specified path.
Save the performance configuration files, SSL certificate

files, license files, and OMU system data to the LMT PC.
Page130
Old and New OMU Boards Running the

Same OS (Cont.)
Unscrew the captive screws on the OMU board

counterclockwise.
Flip outward the ejector levers of the OMU board, as

shown in Figure.
Remove the Ethernet cable, mouse cable, keyboard cable,

and monitor cable (if configured) from the OMU board
after the OFFLINE LED flashes fast and then is steady
blue.
Remove the OMU board along the guide rails
Slide the new board along the guide rails into the
subrack.
The new board automatically loads software and

configuration data, and the RUN LED blinks 0.125 second
on and 0.125 second off.
Connect the cables by referring to the labels.
Page131
Install OMU applications and change IP

addresses of the new OMU
Install OMU applications as instructed in <BSC6900 GSM

V900R013 Installation and Commissioning> Charter 2
BSC6900 Software Installation
Change IP addresses of the new OMU so that they match

those of the replaced OMU board
We discuss changing the IP addresses when the OMU OS is Dopra

Linux.
Page132
Change IP addresses of the new OMU

Type the command cd /mbsc/bam/version_a/bin/bam and press

Enter to navigate to the directory containing omutool.
Change the OMU IP addresses by referring to the IP addresses

of the replaced OMU board.
The ./omutool innercard IP address mask command is used to

change the internal fixed IP address and mask.
The ./omutool innervip IP address mask command is used to

change the internal virtual IP address and mask.
The ./omutool extercard IP address mask (gateway) command

is used to change the external fixed IP address and mask.
Page133
Change IP addresses of the new

OMU(Cont.)
The ./omutool extervip IP address mask command is used to change

the external virtual IP address and mask.
Use the command ./omutool backupcard IP address mask to change

the backup channel IP address of the active and standby OMUs and
mask of the ETH3-UPDATE Ethernet adapter on an OMUa/OMUb
board.
Use the command ./omutool backupcard_for_omuc IP address mask to

change the backup channel IP address of the active and standby OMUs
and mask of the B_UPDATE0 Ethernet adapter on an OMUc board.
The ./omutool debugcard IP address mask command is used to change

the debugging IP address and mask.
Type the command /etc/rc.d/omud start and press Enter to start the
omud process.
Page134
Restore OMU Data

Connect the LMT PC to the OMU external network and

log in to the LMT.
Start the file manager, Select the target file on the LMT
PC and click Upload to upload the saved OMU system
data to the active workspace.
Ensure that the upload path is the same as the backup data
download path.
Page135
Restore OMU Data (Cont.)

The OMU OS is Dopra Linux
Log in to the OMU using the external network fixed IP address.
Type the command /etc/rc.d/omud stop and press Enter to stop the omud
process.
Type the command cd /mbsc/bam/common/services and press Enter to

navigate to the directory containing the omu_backup_linker tool.
Type the command ./omu_backup_linker and press Enter to start the

omu_backup_linker tool.
A message is displayed "Please input a valid bkp_res_type :." Type restore and
press Enter.
A message is displayed "Please input a valid backup file pathname : ." Type the
backup file save path and the file name and press Enter. The system starts to
restore data. A message will be displayed showing success or failure. For
example, "Restore OMU database succeed!" may be displayed.
Type the command /etc/rc.d/omud start and press Enter to start the omud
process.
Page136
Verifying OMU Board Replacement

DSP OMU to Query OMU running status, fixed IP addresses,

virtual IP addresses, data synchronization state, internal
network connection state, external network connection state,
and backup channel connection state.
LST VER and LST PATCHVER to query whether the OMU

software version and patch version are correct.
DSP OMUMODULE to query the status of the OMU processes.

Expected result is Active
CMP LICENSE to check whether the running license on the host

is consistent with that on the OMU.
Page137
Verifying OMU Board

Replacement(Cont.)
CMP BRDVER to check whether the running version on the

host is consistent with that of the OMU.
ACT CRC to check whether the configuration data on the host

is consistent with that of the OMU.
LST BRD to query Slot No. and Board Type of the OMU board.
View the device panel on the LMT and check the status of all
devices.
The board type is consistent before and after the OMU board
replacement
No abnormal device state is introduced by the replacement
The OMU board replacement is complete.
Page138
Replacing the Standby OMU in DualSystem Mode

Old and New OMUs Running the Same Operating System

In dual-system mode, if the active OMU fails, the system

automatically performs a switchover. Therefore, only the
standby OMU needs to be replaced.
Procedure
Remove the standby OMU board to be replaced and insert

the new one.(the same as Single-System Mode)
Install OMU applications
Verifying OMU Board Replacement
Page139
BSC6900 GSM
V900R013 Installation
and Commissioning
www.huawei.com
Foreword
The OMU operating system is installed before the OMU is

delivered.
BSC6900 commissioning is performed after the hardware

is installed and before the services are provided. It aims
to ensure that the BSC6900 can work normally through
tasks such as equipment verification, BSC6900 board
software and data file loading, interface verification, and
service verification.
Page1
Reference
BSC6900 GU Commissioning Guide
BSC6900 OMU Administration Guide
Page2
Objectives

Describe BSC6900 commissioning procedure
Outline OMU structure and OMU software functions
Complete BSC6900 commissioning
Page3
Contents
1. BSC6900 O&M System Introduction
2. BSC6900 Software Installation
3. BSC6900 Commissioning
Page4
BSC6900 O&M Subsystem

Component
LMT
OMUa/OMUc boards
SCUa/SCUb boards
OM modules
Other boards
Page5
BSC6900 O&M Subsystem

BSC6900 O&M system adopts server and client mode

OMU as a server
LMT as a client
EMS (Element Management System) system

iManager M2000 works for integrated O&M
Page6
OMU Ethernet Adapt Configuration

An OMU board is configured with six

Ethernet adapters in total.
ETH0 and ETH1(bond1/bond1:0 )
ETH2: ETH2 (bond2)
ETH3-UPDATE (bond3)
ETH4-SCU7 and ETH5-SCU6 (bond0

(vlan1/vlan1:0))
Note: The figure shows the configuration

of Ethernet adapters on the OMUa
board. There is an additional backup
channel Ethernet adapter on the OMUc
board so that mixed insertion of OMUc
board and OMUa board is available.
Page7
Definitions of IP address of the OMU

The OMU IP addresses include:

External fixed IP addresses
Internal fixed IP addresses
External virtual IP addresses
Internal virtual IP addresses
Debugging IP address.
Backup channel IP address of the active and standby OMUs.

(Optional)
Page8
Definitions of IP address of the OMU

Before an OMU is delivered, six IP addresses are configured.

The default IP addresses may not meet the requirement of
onsite planning. All the OMU IP addresses need to be
planned on site, and some of the IP addresses need to be reset.
Page9
OMU IP Address Planning

IP Address
Planning Principle
Internal fixed IP
The preset IP addresses of the internal Ethernet adapters are:
address
Active BAM: 80.168.3.50 (255.0.0.0)
Standby BAM: 80.168.3.60 (255.0.0.0)
External fixed IP
The preset IP addresses of the external Ethernet adapters are:
address
Active BAM: 172.121.139.201 (255.255.255.0)
Standby BAM: 172.121.139.202 (255.255.255.0)
The settings can be reconfigured on site based on the actual

networking topology
Page10
OMU IP Address Planning

IP Address
Planning Principle
Internal/External virtual IP
The virtual IP address is set in the same subnet with the internal/ external fixed IP addresses of the
address
active and standby OMUs.
Backup channel IP addresses
The default backup channel IP addresses of the active and standby OMUs are:
Active BAM: 192.168.3.50 (255.255.255.0)
Standby BAM: 192.168.3.60 (255.255.255.0)
The IP addresses can be changed based on the network plan.
The backup channel IP addresses of the OMUc board is:
Active OMU: 192.168.9.50 (255.255.255.0)
Standby OMU: 192.168.9.60 (255.255.255.0)
Debugging IP address
The default debugging IP addresses are:

Active BAM: 192.168.6.50 (255.255.255.0)
Standby BAM: 192.168.6.60 (255.255.255.0)
The IP addresses can be changed based on the network plan.
Page11
OMU Internal Network IP Address Planning

Virtual
Virtual IP
IP
Standby OMUa
Active OMUa
80.168.3.40/8
80.168.3.40/8
80.168.3.50/8
80.168.3.50/8
80.168.3.60/8
80.168.3.60/8
ETH4-SCU7
ETH5-SCU6
Internal
network
segment
ETH4-SCU7
ETH5-SCU6
192.168.3.60/24
192.168.3.60/24
192.168.3.50/24
192.168.3.50/24
Intel Ethernet
adapters
ETH3UPDATE
Intel Ethernet
adapters
Dedicated
backup
channel
ETH3UPDATE
SCUa
SCUa
Backboard
Page12
OMU External Network IP Address Planning

Active OMUa
Standby OMUa
172.121.139.202/24
172.121.139.202/24
172.121.139.201/24
172.121.139.201/24
External
network
Segment
GE adapter
Virtual
Virtual IP
IP
172.121.139.200/24
172.121.139.200/24
ETH0
ETH0
ETH1
ETH1
Hub
Commissioning
Ethernet
adapter
ETH2
ETH2
LMT/
M2000
192.168.6.50/24
192.168.6.50/24
192.168.6.60/24
192.168.6.60/24
Page13
Contents
Page14
BSC6900 Software
MPS/EPS
LMT
Windows XP
Java Environment
Host Software
Program
File
Data File
OMU Server
Patch File
(optional)
OMU Application
Dopra Linux
Mysql Database
Page15
OMU Software
The OMU software

consist of multi-level
service monitoring
entities and service
processes
Page16
OMU Software Installation Procedure

Obtain the Installation Information on the OMU
Logging In to the OMU
Uploading the OMU Application Installation Package to the

OMU
Installing the OMU Application in the Active Workspace
Checking the Installation Directory of the OMU Applications
Checking the Status of omud Process
Page17
Obtaining the installation on the OMU

Before the installation, obtain the following information from

Data Sheet of BAM Software Installation
Password of the operating system administrator
Fixed IP address of the external network, virtual IP address of

the external network, or debugging IP address of the OMU.
Page18

On the computer run the

SSH terminal, PuTTY.
Enter the IP address of

the OMU.
Log in to the OMU as user

root.
Page19
Uploading the OMU Application Installation

Packet to the OMU
Decompress the BSC6900 version software package to the

local drive D.
Log in to the OMU through the psftp software.

Run the lcd D:\ command to set the local directory.
Run the mkdir /mbsc/upgrade command to create the target

directory.
Page20
Uploading the OMU Application Installation

Packet to the OMU
Run the cd /mbsc/upgrade command to go to the target

directory.
Run the put -r V900R013C00 command to upload the OMU

application installation packet to the OMU.
After the loading is complete, enter the exit command to exist

the psftp software.
Page21
Installation the OMU Application in the

active area
Assume that the OMU application installation package

install_bam.sh is saved in
/mbsc/upgrade/V900R013C00/install/setup.
On the PuTTY terminal, run the following commands
Page22

active area
cd /mbsc/upgrade/V900R013C00/install/setup
chmod +x ./install_bam.sh
./install_bam.sh
Enter the
Setting the office name
Setting the language
Setting the admin/FTP password
Setting the external virtual IP address
Setting the OMU system type
run mode
Page23

active area
Setting the run mode of product
Setting the office name
Setting the language
Page24

active area
Setting the admin/FTP password
Setting the external virtual IP address
Page25

active area
Setting the OMU system type
Confirming the installation
Enter Y to install the OMU applications.

When the message "Install OMU succeed!" is displayed, you

can infer that the OMU applications are successfully installed.
Page26
Checking the Installation Directory

of the OMU Applications
The version_a and version_b folders

save active/standby OMU
workspace files.
Log in to the OMU by PuTTY.
Run the cd /mbsc/bam command.
Check whether the OMU installation

directory.
Page27
Checking the Status of omud Process

Log in to the OMU by PuTTY.
Run the /etc/rc.d/omud status command.

The returned information is running, it means the omud is

working normally.
The returned information is unused, run the /etc/rc.d/omud

start command to start the omud.
The returned information is neither running nor unused,

reinstall the OMU application in the active workspace.
Page28
USB Storage Device

A USB storage device is used in the following three scenarios:

1. Initial installation of the OMU operating system and
applications
2. Recovery of the collapsed OMU operating system
3. Switchover of the OMU operating system from Windows

2003 server or Suse Linux to Dopra Linux.
For details about scenarios 1 and 2, see the BSC6900 OMU

Administration Guide.
For details about scenario 3, see the Operation Guide to Switching

BSC6900 OMU Operating System Through USB Disks.
Page29
Contents
Page30
Contents
3.1 BSC6900 Commissioning Introduction
3.2 BSC6900 Commissioning Procedure
Page31
Introduction to BSC6900 Commissioning

Introduction to BSC6900 Commissioning
BSC6900 commissioning is performed after the

BSC6900 hardware is installed and before services
are started. BSC6900 commissioning includes device
commissioning, BSC6900 board software and data
loading, interface verification, and service verification.
BSC6900 commissioning ensures that the BSC6900

works properly.
Page32
Preparation For BSC6900 Commissioning


Verify hardware status

BSC6900 hardware is installed and passed the hardware

installation check and powering-on check
OMU is configured before delivery
LMT PC meets the configuration requirements
Software preparation
BAM and LMT application software are ready
License file is ready
MML command script for initial configuration is ready
Page33

Verify commissioning network status

At least one BTS and one NodeB are connected to the local
BSC6900. The BTS and the NodeB should have passed
commissioning and can provide basic functions
At least one set of Core Network (CN) equipment is connected to

the local BSC6900. The CN equipment should have passed the
commissioning and can provide basic functions
If the BSC6900 is connected to the RNC, then that RNC must have
passed the commissioning
Three single-mode UEs, three single-mode MSs and one dualmode UE are ready for test and are registered in the HLR
Page34
Contents
3.1 BSC6900 Commissioning Introduction
3.2 BSC6900 Commissioning Procedure
Page35
BSC6900 Commissioning Procedure

Commissioing Prerequsites
Local operation
Check hardware operating

Status
Remote
operation
Verify OMU
based on local through USB Disk
coopertation
Remote operation
Remote operation
Load BSC6900 Board
Software and Data
files
Local operation
Verify OMU
Locally
Connect BSC6900 to
M2000
Log in to BSC6900
through LMT
Update OMU
Database
Activate and Verify
the License
Page36

(Cont.)
Remote operation
Verify interfaces
through M2000
Set NE to be in
maintenance mode
Verify Interface
Verify interfacesRemote operation

through LMT based on local
cooperation
Verify GSM Interface
Verify UMTS Interface

Verify UMTS services
End the maintenance

mode of NE
Create scheduled task
Handle alarms
Page37
Checking the Operating Status of the

Hardware
Before verifying the equipment, ensure that the cabinet is

powered on and operates normally
Checklist of the power supply to the cabinet components
Page38
Main Steps of Commissioning

Verifying the OMU
Activating and Verifying the License
1. Logging in to the OMU

2. Check the running status
of the OMU process
3. Query the current version
of the OMU application.
Loading the BSC6900 Board Software and Data Files

Verifying the Interfaces
Handling the Alarms
4. Change the external fixed/

virtual IP address
6. Change the name and set
the work mode of the OMU
7. Check the operating status
of the OMU
Verifying the Services

Connecting the BSC6900 to the M2000
Creating Scheduled Tasks
Page39

On the computer run the

SSH terminal, PuTTY.
Enter the IP address of

the OMU.
Log in to the OMU as user

root.
Page40
Check the Operating status of OMU

Processes
Run the /etc/rc.d/omud status command to check the

running status of OMU processes.
Page41
Querying the Current Version of the

OMU Application
Run the cd /mbsc/upgrade command to switch to the OMU

installation directory, and then run the ls command to query
the current version of the OMU application.
If the version of the OMU application is different from that

required by the operator, Uninstalling the OMU application
firstly , and then install the OMU application in the active
workspace
Page42
Querying the Network Configuration of

the OMU Ethernet Adapters
Querying the external fixed IP address: ifconfig bond1
Querying the external virtual IP address: ifconfig bond1:0
Querying the internal fixed IP address: ifconfig vlan1
Querying the internal virtual IP address: ifconfig vlan1:0
Querying the debugging IP address: ifconfig bond2
Querying the IP address for the backup channel between

the active OMU and the standby OMU: ifconfig bond3
Page43
Changing the External IP Address

Run the cd /mbsc/bam/version_a/bin/bam command to

switch to the directory where the omutool program locates.
Run the ./omutool command to start omutool.
Run the ./omutool extercard The external fixed IP address

The subnet mask The gateway IP address command to
change the external fixed IP address and the subnet mask.
./omutool extercard 10.161.10.100 255.255.255.0 10.161.10.1
Run the ./omutool extervip The external virtual IP address

The subnet mask command to change the external virtual IP
address and the subnet mask.
./omutool extervip 10.161.10.102 255.255.255.0
Page44
Changing the Name and Setting

the Work Mode of the OMU
Run the ./omutool hostname OMU name command to

change the name of the OMU.
For example, you can run the following command and then
press Enter to change the OMU name to omu_123: ./omutool
hostname omu_123.
Page45
Changing the Name and Setting

the Work Mode of the OMU
Set the work mode of the OMU according to the number of

OMUa boards that are configured.
If only one OMUa board is configured, run the ./omutool

dualmode single command to set the work mode to the
single-server mode.
If two OMUa boards (active and standby OMUa boards) are

configured, run the ./omutool dualmode dual command to set
the work mode to the dual-server mode.
Page46
Check the Operating Status of the OMU

Run the /etc/rc.d/omud start

command to start the OMU
application.
Run the ps -afx command to

check the operating status of
the OMU.
You can infer that the OMU is

in normal state if all OMU
processes exist in the OMU
active workspace
directory/mbsc/bam/version
_a/bin/bam/monitor.
Page47

Verifying the OMU Locally
Handling the Alarms
Page48


Downloading license to OMU active workspace directory

/ftp/license (DLD LICENSE)
Querying the detail information of the license file (LST

LICENSE)
Activating the license file (ACT LICENSE)
Checking the license consistency between host and OMU

(CMP LICENSE)
Page49
Loading the BSC6900 Board Software

and Data Files

Generating the Data File

Clear the data in the BAM database (RST DATA)
Generate the data file in ineffective state

SET CFGDATAINEFFECTIVE
Batch Commands
FMT DATA
Page50
Loading the BSC6900 Board Software

and Data Files
Setting the Loading Mode (SET LODCTRL)
Loading the MPS/EPS/TCS (RST SUBRACK)
Checking the consistency of the data and the version (ACT

CRC & CMP BRDVER)
Page51

1. Verifying the Abis

Interface
2. Verifying the A Interface
3. Verifying the Gb Interface

4. Verifying the Ater
Interface (Optional)
Handling the Alarms
5. Verifying the Pb Interface

(Optional)

Page52
Verifying the Abis Interface

Verifying the Abis interface (Abis over TDM)

Verifying Physical Links at the BSC (DSP E1T1 & DSP OPT)
Verifying the Control Plane on the Abis Interface (DSP

LAPDLNK)
Verifying the timeslot status of the Abis interface (DSP

ABISTS)
To query the Subrack No., Slot No., and Port No. of the timeslots
to be verified, run the MML command (LST BTSCONNECT)
Verifying the Status of Cells and Channels (DSP BTSSTAT)
Page53
Verifying the Abis Interface

Verifying the Abis interface (Abis over IP)

Verifying Physical Links at the BSC (DSP ETHPORT)
Verifying the Control Plane on the Abis Interface (DSP

LAPDLNK)
Verifying the User Plane on the Abis Interface (DSP

ADJNODE & DSP IPPATH)
Verifying the Status of the Cells and Channels (DSP

BTSSTAT)
Page54
Verifying the A Interface

Verifying the A interface (A over TDM)

Verifying the Control Plane on the A Interface
DSP N7DPC
DSP MTP3LNK
DSP MTP2LNK
Verifying the User Plane on the A Interface (DSP ACIC)

To query the OPC Index and DPC Group Index of the E1/T1 to be
verified on the A interface, run the MML command LST AE1T1.
Page55
Verifying the A Interface

Verifying the A interface (A over IP)

Verifying Physical Links at the BSC (DSP ETHPORT )
Verifying the Control Plane on the A Interface
DSP N7DPC
DSP M3LKS
DSP SCTPLNK
Verifying the User Plane on the A Interface (DSP ADJNODE &

DSP IPPATH )
Page56
Verifying the Gb Interface

Verifying the Gb interface (Gb over FR)

Verifying the status of the Bearer Channel (DSP BC)
Verifying the status of the Network Service Virtual Connection

(DSP NSVC)
Verifying the SIG BSSGP Virtual Connection (SIGBVC) status

of the Network Service Entity (DSP SIGBVC & DSP PTPBVC)
To query the configuration of the NSE to be verified, run the MML

command LST NSE
Page57
Verifying the Gb Interface

Verifying the Gb interface (Gb over IP)

Verifying the status of the Network Service Virtual Link (DSP

NSVL)
To query the configuration of the local or remote NSVL to be

verified, run the MML command LST NSVLLOCAL or LST
NSVLREMOTE.
Verifying the status of the IP Route (DSP GBIPROUTE)
Verifying the SIG BSSGP Virtual Connection (SIGBVC) status of

the Network Service Entity (DSP SIGBVC & DSP PTPBVC)
To query the configuration of the NSE to be verified, run the MML

command LST NSE
Page58
Verifying the Ater and Pb Interface (Optional)

Verifying the Ater Interface
Verifying the Status of Timeslots on the Ater interface. (DSP

ATERTS)
If the TCS is configured remotely, run the MML command DSP

ATERSL to query whether the Ater signaling link is normal.
Verifying the Pb Interface
Verifying the LAPD link on the Pb interface (DSP LAPDLNK)
Verifying the status of the circuit on the Pb interface (DSP PBCIC)
Page59

Handling the Alarms
Verifying the GSM Services

Page60
Handling the Alarms Generated

During the Commissioning
Handling Alarms During Commissioning

Checking alarm on the LMT
Handling the Alarms by LMT online help
Page61
Verifying the GSM Services

To be sure BSC can provide services defined in license file

Basic services
The basic services consist of speech service and data service.
Feature services
The feature services consist of the inter-RAT handover, location

service, and AMR service.
If the result of service verification cannot meet the expected

results, start message tracing on the LMT over the Um,
Abis, A, Gb, Pb, and Ater interfaces.
Page62

Handling the Alarms
Page63
Connecting the BSC6900 to the

M2000
Connect the BSC6900 to the OM network
Configure the IP route from the BSC6900 to the M2000
ADD OMUIPRT
ADD EMSIP
Create the BSC6900 on the M2000

iManagerTM M2000
DCN
Page64

Scheduled tasks for backing up system data

ADD SCHTSK
ADD SUBTSK
Scheduled tasks for backing up logs

ADD SCHTSK
ADD SUBTSK
Page65
GSM BTS3900
Product Description
www.huawei.com
Foreword
The BTS3900 developed by Huawei is an indoor macro

BTS. The BTS3900 mainly consists of the BBU and DRFU.
Compared with traditional BTS, the BTS3900 features
simpler structure and higher integration
References
31183198-BTS3900 GSM Documentation

BTS3900 GSM Hardware Description
BTS3900 GSM Product Description
Page1
Objectives

Know the application scenarios of BTS3900
Grasp the hardware structure of BTS3900
Grasp the functions of the modules
Master typical configuration of BTS3900
Know the networking topology of BTS3900
Page2
Contents
1. BTS3900 Overview
2. BTS3900 Hardware Components
3. BTS3900 Signal Flow
4. BTS3900 Configuration
5. BTS3900 Network
6. GRFU Introduction
Page3
Location of BTS3900
Um Interface
MS
PSTN
ISDN
PSPDN
TUP,ISUP
BTS3900
BSC
A Interface
MS
MSC/VLR
M
MAP
BTS3900
HLR/AUC/EIR
BTS3900
MS
BTS3900
AP
SMC/VM
OMC
MS: Mobile Station
BTS: Base Transceiver Station
BSC: Base Station Controller
HLR: Home Location Register
AUC: Authentication Center
EIR: Equipment Identity Register
MSC: Mobile Switching

Center
VM: Voice Mailbox
VLR: Visitor Location Register
SMC: Short Message Center
OMC: Operation and Maintenance Center
Page4
Functions and Features

It supports multiple frequency bands, such as PGSM900,

EGSM900, and GSM1800
It supports the Abis IP/FE interface in hardware and enables

Abis over IP through software upgrade if required
It supports transmit diversity and PBT
It supports 2-antenna and 4-antenna receive diversity to

improve the uplink coverage
It is developed on the basis of the unified BTS platform for

Huawei wireless products and enables the smooth evolution
from 2G to 3G
Page5
Functions and Features

When the DRFU is configured, a BTS3900 can support a

maximum of 12 carriers in the maximum cell configuration of
S4/4/4. In addition, a site configured with the BTS3900s can
support a maximum of 36 carriers in the maximum cell
configuration of S12/12/12
When the GRFU is configured, a BTS3900 can support a

maximum of 36 carriers in the maximum cell configuration of
S12/12/12. In addition, a site configured with the BTS3900s can
configuration of S24/24/24
Page6
Contents
1. BTS3900 Overview
5. BTS3900 Network
Page7
BTS3900 Hardware Structure

The dimensions of the BTS3900

cabinet
600mm(Width)*450mm(Depth)
*900mm(Height)
The weight of the BTS3900 cabinet

Empty cabinet:57kg
Full Configuration: 132kg
Page8
Structure of the BTS3900 Cabinet
Double radio filter unit
Fan box
GSM antenna and TMA control module
Baseband unit
Direct current distribution unit
-48V Cabinet
Page9
Structure of the BTS3900 Cabinet
Double radio filter unit
Fan box
GSM antenna and TMA control module
Baseband unit
Direct current distribution unit
Power supply unit
+24V or 220VAC Cabinet
Page10
Logical Structure and Signal Flow
Page11
Contents
2.1 BBU Unit
2.2 RF Unit
2.3 Power module & Components
Page12
BBU
The typical power consumption of BBU is 35W
The weight of the BBU is 12 kg at most
All the boards can be inserted from the front panel
The permissible range of power input is 38.4 V DC to 57 V DC
Page13
Working Principles of the BBU
Page14
Boards and Modules in BBU

BSBC: The universal BBU Subrack Backplane type C
GTMU: The GSM Transmission, Timing and Management Unit
UBFA: The Universal BBU Fan unit type A
UPEU: The Universal Power and Environment interface Unit
UELP: The Universal E1/T1 Lightning Protection unit
UEIU: The Universal Environment Interface Unit
Page15
BSBC Board
The BSBC provides slot 6 for the GTMU, slot 7 for a main control
board that supports 3G, and slots 0 to 5 as common slots. The GTMU
is 1 U high. Therefore, from the view of the front panel, the GTMU is
located in slots 5 and 6
Provide backplane interfaces, communication channels, distribute

clock signal and +12V power supply for the other boards
Page16
GTMU
The GSM Transmission, Timing, and Management Unit for

BBU (GTMU) controls and manages the entire BTS. It provides
interfaces related to the reference clock, power monitoring,
OM, and external alarm collection.
Distributes and manages BTS clock signals
Provides the Ethernet port for terminal maintenance
Supports four routes of E1 inputs
Provides the CPRI ports for communication with the DRFU
Page17
GTMU Ports
Label
Connector
Type
Description
CPRI0CPRI5
SFP
Ports for the communication between the BBU and the RF module;
support input and output of the optical and electrical signal .
ETH
RJ45
Port for local maintenance and commissioning
FE0
RJ45
A reserved port that performs the following function:

Connects the BBU to a routing device in the equipment room through
the Ethernet cable to transmit network information.
FE1
DLC

Connects the BBU to a routing device in the equipment room through
the optical cable to transmit network information.
USB
USB

Enables the automatic software upgrade from a USB disk.
TST
USB
Provids a reference clock for the tester.
E1/T1
DB26
female
Provides the input and output of the four E1/T1 signals between the
GTMU and the UELP or between the GTMU and the BSC.
Page18
GTMU Indicators
LED
RUN
Color
The board is faulty.
OFF
No power supply is available or the board is faulty.
ON for 1s, OFF for 1s
The board is operational.
ON for 2s, OFF for 2s
The OML link is abnormal.
ON for 0.125s
OFF for 0.125s
The board is loading software.
ON
A fault occurs in the running board.
OFF
No alarm is generated.
ON
The board is operational.
OFF
The board is faulty.
ON
This link is not used.
ON for 0.125s
OFF for 0.125s
A remote E1/T1 alarm is generated.
OFF
This link is operational.
Green
ON
The CPRI link is normal.
Red
ON
The reception of the optical module is abnormal and an

alarm is generated.
Green
Red
ACT
Green
CPRI0CPRI5
Description
ON
ALM
LIU0-LIU3
Status
Green
Page19
UELP
UELP is the E1/T1 signal lightening protection unit of BBU and

it can provide protection for 4 route E1/T1 signal
GTMU
Port
Type
Relative cables
INSIDE
DB25 male
E1 transferring
cable
OUTSIDE
DB26 male
E1/T1 cable
Description
Transfers the four E1/T1
signals between the UELP
and the GTMU
Provides the input and
output of the four E1/T1
signals between the BBU and
the BSC
Page20
UPEU
The universal power and environment interface unit (UPEU) supports

the -48V /-24V DC power input, supplies power to the boards, modules,
and fan in the BBU, and provides access to multiple environment
monitoring signals
Port
Type
Description
MON
0
RJ45
Port for RS485 input 0
MON
1
RJ45
Port for RS485 input 1
EXTALM0
RJ45
Transmitting four dry contact

alarms
EXTALM1
RJ45
Transmitting four dry contact

alarms
PWR
3V3
+24 V/-48 V DC power input
Page21
UEIU
UEIU is the environment interface board of BBUit can support

multi-route monitoring signal input
UEIU is optional and is only used when more ports are needed
Label
Connector
Type
Description
MON0
RJ45
One RS485 signal
MON1
RJ45
One RS485 signal
EXTALM0
RJ45
Four dry contact

signals
EXTALM1
RJ45
Four dry contact

signals
Page22
Monitoring System
Page23
USCU
The Universal Satellite Card and Clock Unit (USCU) is compatible with six
types of satellite card, provides absolute timing information and the 1 Pulse
Per Second (PPS) reference clock for the main control board, and provides
the RGPS ports and BITS port.
Port
Description
1 GPS port
Used for receiving GPS signals
2 RGPS ports
Used for receiving RGPS signals
3 BITS port
Connected to the BITS clock; supporting adaptive input

of the 2.048 MHz and 10 MHz clocks
4 TEST port
Used for testing the clock
Page24
UBFA
The universal BBU fan unit type A (2U) (UBFA) works with the air inlet box
of the cabinet to form a ventilation circuit, thus cooling the entire cabinet
The UBFA module communicates with the GTMU to regulate the

temperature, adjust the fan speed, and report alarms. The UBFA module is
hot swappable
Label
STATE
Color
Red
/Green
Status
Description
0.125s ON,
0.125s OFF
(Green)
The module is not registered,

and no alarm is reported.
1s ON, 1s
OFF (Green)
The module is running properly.
1s ON, 1s
OFF (Red)
The module is reporting alarms.
OFF
The module is powered off or

the program is not loaded.
Page25
BBU Cables Connection

BBU cables connection between BBU, BSC, RFU and

Auxiliary equipment
Page26
Contents
2.1 BBU Unit
2.2 RF Unit
2.3 Power module and Components
Page27
RF Unit
RF Unit handles modulation and demodulation between

baseband signals and RF signals, data processing, and
combining-distribution. There are two kinds RF Unit,
DRFU and GRFU
One Double Radio Frequency Unit (DRFU) provides two

TRXs.
One GSM Radio Frequency Unit (GRFU) provides a

maximum of six TRXs.
Page28
Main Functions of DRFU

One double radio filter unit (DRFU) provides two TRXs
The DRFU performs modulation and demodulation

between baseband signals and RF signals, processes data,
and combines and divides signals
Page29
Working Principles of the DRFU

The DRFU consists of the high-speed interface unit,

signal processing unit, power amplifier, and dualduplexer
Page30
Ports of the DRFU

Type
Port for
transmitting
and receiving
RF signals
CPRI port
Connector
Ports
ANT1
N female
connector
SFP female
connector
ANT2
Power port
QMA
female
connector
7W2 power
connector
Used in connection to the antenna subsystem
CPRI0
Used in connection to the BBU, or in

connection to the upper-level cascaded DRFU
CPRI1
Used in connection to the lower-level cascaded

DRFU
RX2
out
Input port for diversity signals in antenna

channel 1
Output port of diversity signals in antenna
channel 1
Input port for diversity signals in antenna
channel 2
Output port of diversity signals in antenna
channel 2
PWR
Receives power input
RX1 in
Port for
transmitting RF
signals
between DRFUs
Description
RX1
out
RX2 in
Page31
LEDs of the DRFU

LED
RUN
ALM
ACT
Color
Green
Red
Green
Status
Description
On
The power input is normal, but the module is

faulty.
Off
No power input is available, or the module is

faulty.
On for 1s
Off for 1s
The module is functional.
On for
0.125s
Off for
0.125s
The module is loading data.
On for 1s
Off for 1s
A fault alarm is generated.
Off
On
A fault alarm is generated, need to chang

another module.
On
The module is functional and is correctly

connected to the BBU.
Off
The connection with the BBU is not established.
On for 1s
Off for 1s
The DRFU is being tested on the Site

Maintenance
Page32
LEDs of the DRFU
VSWR
CPRI0
CPRI1
Red
Red
Green
Red
Green
Off
No VSWR alarm is detected.
On for 1s
Off for 1s
The VSWR alarm is generated only on the

ANT2 port.
On for
0.125s
Off for
0.125s
The VSWR alarms are generated on the ANT1

and ANT2 ports.
On
The VSWR alarm is generated only on the

ANT1 port.
On (green)
The CPRI link is functional.
On (red)
The interface module fails to receive signals.
On for 1s
Off for 1s
(red)
The CPRI link has a loss-of-lock error.
On (green)
The CPRI link is functional.
On (red)
The interface module fails to receive signals.
On for 1s
Off for 1s
(red)
The CPRI link has a loss-of-lock error.
Page33
Contents
2.1 BBU Unit
2.2 RF Unit
2.3 Power module and Components
Page34
Main Functions of DCDU

Receiving -48 V DC power input
Distributing the -48 V DC power of 10 outputs for boards and

modules in the cabinet
Providing surge protection of 10 kA in differential mode and 15

kA in common mode and providing dry contact for surge
protection failure
Page35
Power Subrack (AC/DC)

The power subrack (AC/DC) consists of the PMU, PSU (AC/DC)

and the wiring unit of the power subrack (220 V).
The power subrack (AC/DC) converts the 220 V AC power to the

-48 V DC power.
1) PMU
2) PSU
3) Wiring unit
Page36
Main Functions of PMU(AC/DC)

The Power and Environment Monitoring Unit (PMU) provides a

comprehensive function of power supply management, power
distribution check, and alarm reporting.
Communicates with the GTMU through the RS232/RS422 serial port
Manages the power system and the battery charging and discharging
Detects and reports monitoring signals
1.
2.
3.
4.
5.
LEDs
Power supply test ports
RS232/RS422 ports
Battery control switch
COM port
Page37
Ports of PMU
Ports
Function
RS232/RS422
port
Used in communication with the central processing unit
Battery switch
The battery switch has two control ports ON and OFF, which are
used for switching on and switching off the battery
Press and hold the port ON for 5-10 seconds to switch on the
battery
Press and hold the port OFF for 5-10 seconds to switch off the
battery
Power supply
test port
Two power supply test holes -48V and 0V are available for
measurement through an ordinary multi-meter
COM port
Used in connection to the external signal transfer board
Backplane port
Used in connection to the backplane
Page38
Main Functions of PSU(AC/DC)

Converting 220 V AC power to -48 V DC power and supplying -48 V

DC power to the DCDU
Monitoring alarms related to module faults (such as output

overvoltage, no output, and fan faults), alarms related to module
protection (such as over temperature protection and input
overvoltage/undervoltage protection), and module out-of-position
alarm
1
2
3
1 Power running LED

2 Protection LED
3 Fault LED
Page39
Power Subrack (DC/DC)

The power subrack (DC/DC) provides access for the external

+24 V DC. In the power subrack, it contain two components,
PSUs (DC/DC) and Wiring unit.
PSUs (DC/DC) convert the +24 V DC power into the -48 V DC

power, and then leads the -48 V DC power to the DCDU-01
over the power cable through the wiring unit of the power
subrack.
Page40
Main Functions of PSU(DC/DC)

Converting +24 V DC power to -48 V DC power and

leading the -48 V DC power to the DCDU
1 Power running LED

2 Protection LED
3 Fault LED
Page41
Power Distribution Mode 1

The BTS3900 cabinet can use three types of power inputs, namely, -48 V
DC, +24 V DC, and 220 V AC
If the external -48 V DC power input is used, no additional power system

is required. The external -48 V DC power input is directly connected to the
power input terminals on the DCDU (10 outputs). Then, the DCDU
distributes the -48 V DC power to each module in the cabinet
Page42

When the external +24 V DC power or +220V AC power is used, PSUs

and a cable in/out unit are configured in the cabinet. The PSUs convert
the external power into the -48 V DC power and supply the -48 V DC
power to the DCDU Then, the DCDU distributes the -48 V DC power to
each module in the cabinet
Page43

This is the power distribution when a -48 V DC cabinet is stacked on a

+24 V DC cabinet or +220V AC cabinet. The PSUs convert the external
+24 V DC or +220VAC power into the -48 V DC power and supply -48
V DC power to the DCDUs in both cabinets. Then, the DCDUs
distribute the -48 V DC power to the modules in both cabinets
Page44
Main Functions of GATM

The GSM antenna and TMA control module (GATM) is a module

that controls the antenna and TMA. The GATM is optional
when the DRFU module is configured.
Controls the RET antenna
Feeds power to the TMA
Reports the RET control alarm signals
Monitors the current from the feeder
Page45
Ports on the GATM

Ports
Connector
Function
ANT0
ANT2
ANT4
SMA
female
Providing power for the RET antenna and

transmitting control signals for the RET antenna
ANT1
ANT3
ANT5
SMA
female
Providing power for the TMA
COM1
RJ45
Used in connection to the BBU
COM2
RJ45
Providing the extended RS485 port to be

cascaded with other devices
-48 V
7W2
Receiving the -48 V power input
Page46
Features and Functions of Fan Box

The FAN unit, also called the fan box module, dissipates the
heat in the cabinet. One FAN unit has four independent fans.
Detects the temperature
Communicates with BBU unit to report alarms and the

adjusted rotation speed of the fans to BBU
Page47
Cable Connection of -48V Cabinet

Cable
Number
Cable Name
Quantity
R1-R12
RF Jumpers
12
P1-P2
External Power Cables (-48 V)
P3-P8
Power Cables Between the DCDU and

DRFUs
P9
Power Cable Between the DCDU and Fan

Box
P10
Power Cable Between the DCDU and BBU
P11-P12
Reserved
S1-S6
CPRI Signal Cables Between the BBU and

DRFU
S7
E1 Transfer Cable of the BBU
S8
Monitoring Signal Cables for the DCDU
S9
Monitoring Signal Cable for the Fan Box
S10
E1/T1 Cable of the BBU
Page48
Contents
1. BTS3900 Overview
5. BTS3900 Network
Page49
BTS3900 Signal Flow

The signal flow of the BTS3900 consists of the traffic

signal flow and the signaling flow of the BTS.
DL traffic signal flow
UL traffic signal flow
Signaling flow
Page50
Traffic Signal Flow

The DL traffic signal flow is transmitted from the BSC to the

MS through the BTS3900. The BBU and RFUs work together to
process the DL traffic signals
Opposite to the DL traffic signal flow, the UL traffic signal flow

is transmitted from the MS to the BSC through the BTS3900.
The BBU and RFUs work together to process the UL traffic
signals
BSC
BBU
E1
DBUS
CBUS
FHBUS
RF
DRFU
CPRI
Page51
Signaling Flow
This describes the BTS3900 signaling flow on the Abis

interface. The BBU serves as the control unit and works
with the RFUs to process the signaling.
DBUS
CBUS
FHBUS
BSC
E1
BBU
CPRI
DRFU
Page52
Contents
1. BTS3900 Overview
5. BTS3900 Network
Page53
Contents
4. Configurations of the BTS3900
4.1 Configuration Principle
4.2 Antenna Mode
4.3 Transmit Mode and Receive Mode
4.4 Typical Configuration
Page54
Basic Configuration Principles

The DRFU supports a maximum of two carriers and it is

applicable to small- and middle-capacity scenarios
The GRFU supports a maximum of six carriers and it is

applicable to large-capacity scenarios
The DRFU and GRFU can be configured in the same cabinet or

cell to support flexible capacity expansion
Wide coverage is preferred. The DRFU supports the PBT, TX

diversity, and 4-way RX diversity mode. Therefore, the DRFU
can be applied to wide-coverage scenarios
Page55
Antenna Configuration Principles

One dual-polarized antenna can serve a maximum of two RFUs.
By default, RX diversity is adopted on the GSM network. That

is, two feeders connected to two single-polarized antennas or
one dual-polarized antenna must be configured in a cell.
Each cell of the BTS must be configured with the minimum

number of antennas.
For the 2-way RX diversity, each cell has two antenna channels;
for the 4-way RX diversity, each cell has four antenna channels.
Page56
DRFU Configuration Principles

A single DRFU does not support the S1/1 application;

however, three DRFUs support the S3/3 application
When the DRFU works in TX PBT, TX diversity, or 4-way

RX diversity mode, a DRFU provides only one TRX.
When only DRFU are configured, One BTS3900 can

configuration of S4/4/4. A site configured with the
BTS3900s can support a maximum of 36 carriers in the
maximum cell configuration of S12/12/12
Page57
Contents
4.2 Antenna Mode
Page58
DRFU Antenna Mode

Single Antenna
Single Antenna (1TX + 1RX), for one DRFU configuration
Single Antenna (1TX + 2RX), for two DRFUs configuration
Double Antenna
Double Antenna (1TX + 1RX), for one DRFU configuration
Double Antenna (2TX + 4RX), for two DRFUs configuration
Page59
Single Antenna
TX/RX
TX/RX
Single Antenna (1TX + 1RX)
TX/RX
Single Antenna (1TX + 2RX)
Page60
Double Antenna
TX
RX
Double Antenna (1TX + 1RX)
TX/RX
RX
Page61
Double Antenna
TX/RX
TX/RX
TX/RX TX/RX
TX/RX TX/RX
Page62
Contents
4.2 Antenna Mode
Page63
Transmit Mode and Receive Mode

DRFU transmit mode

Transmit independency or combining
PBT
Dynamic PBT
Diversity transmitter
DRFU receive mode

Main diversity receiver
Four diversity receiver
Page64
DRFU Internal Structure

2 TRXs and 2 duplexers are integrated in DRFU module which can

be connected to antenna directly
The RX_IN and RX_OUT port of DRFU can support the receiving
signal interconnection between 2 DRFUs, so that the 2 DRFUs can
share different feeders
CPRI-1
Interface Processing Unit
CPRI-0
DUP
ANTA
ANTB
DUP
RX-IN
RX_OUT
Page65
Transmit Independency
In transmit independency mode, TRX0 occupies channel A

while TRX1 occupies channel B
CPRI1
Interface
Processing Unit
CPRI0
DUP
ANT1
DUP
ANT2
Page66
Transmit Combining
In transmit combining modethe two TRXs are combined

and transmitted through channel A
CPRI1
Interface
Processing Unit
CPRI0
DUP
ANT1
DUP
ANT2
Page67
PBT
In PBT mode, only the TRX0 can work
PBT mode can improve the transmitting power
In PBT modeonly channel A is used by downlink signal
CPRI1
Interface
Processing Unit
CPRI0
DUP
ANT1
DUP
ANT2
Page68
Dynamic PBT
Dynamic PBT is a mode based on the operation of timeslots,

compared with static PBT, it brings the balance between
capacity and coverage and does not cause the 50% decrease of
capacity
The subscriber occupies a TS under the detection of measure

report. When the quality is lower than a threshold, the same
No. of TS of the adjacent TRX will be used as the secondary TS
by the subscriber to start PBT. (The former subscriber in the
secondary TS will handover) When the quality is higher than a
threshold, the PBT will be canceled and the secondary TS will
be released
Page69
The Principle of Dynamic PBT

Timeslots
TRXs
Poor quality
Good quality
No signal
Signal quality
Page70
Transmit Diversity
In Transmit diversity mode, only the TRX0 can work
Transmit diversity mode improves the quality of downlink signal
In Transmit diversity modethe signal from the TRX0 is divided to 2

channels and be transmitted through ANTA and ANTB
CPRI1
Interface
Processing Unit
CPRI0
DUP
ANT1
DUP
ANT2
Page71
Main Diversity receiver

In this modeboth of the 2 TRXs can work
Each TRX receives the signal from 2 feeders
In the following figurethe TRX gets the receiving signal from channel A and B
of the single DRFU
It is also possible for TRX to share the receiving channels with another DRFU
CPRI1
Interface
Processing Unit
CPRI0
DUP
ANT1
DUP
ANT2
If only one ANT

channel is used,
TRX can also
use the ANT
channel of other
DRFU through
RX-in to ensure
2 way receiving
RX-IN
RX_OUT
Page72
Four Diversity Receiver

In this mode, only the first TRX can work
The working TRXs get the uplink signals from 4 ANT ports of
2 DRFUs
CPRI1
Interface
Processing
Unit
CPRI0
DUP
ANT1
DUP
ANT2
RX-IN
RX_OUT
CPRI1
Interface
Processing
Unit
CPRI0
DUP
ANT1
DUP
ANT2
RX-IN
RX_OUT
Page73
Cable
connection for
sharing the
receiving signals
Contents
4.2 Antenna Mode
Page74
DRFU S1/S2 Configuration

S1 Configuration
TX mode: Transmit Independency or Combining
RX mode: Main diversity receiver
Antenna mode: Double antenna(1TX+2RX)
S1 Configuration
TX mode: Transmit diversity
S2 Configuration
TX mode: Transmit Independency or Combining
Page75
DRFU S2/S3/S4 Configuration

S2 Configuration
TX mode: PBT
Antenna mode: Single antenna(1TX+2RX)
S3/S4 Configuration
TX mode: Transmit Independency or

Combining
Page76

S5/S6 Configuration

Combining
Antenna mode
DRFU0: Single antenna(1TX+2RX)
DRFU2: Double antenna(1TX+2RX)
Page77

S7/S8 Configuration

Combining
Page78
DRFU S3/3 Configuration

S3/3 Configuration

Combining
Antenna mode
DRFU1: Double antenna(2TX+4RX)
Page79
Contents
1. BTS3900 Overview
5. BTS3900 Network
Page80
BTS Star Topology

The star topology applies to common areas, especially densely

populated areas, such as cities
In the star topology, each site is directly connected to the BSC
Page81
BTS Chain Topology

The chain topology applies to sparsely populated areas in

strip-like terrain, such as areas along highways and railway
tracks
The chain topology reduces cost in transmission equipment,

construction, and transmission link lease
Page82
BTS Tree Topology

The tree topology applies to areas where network

structures, site distribution, and subscriber distribution are
complicated
The tree topology requires fewer transmission cables

compared with the star topology
Page83
BTS Ring Topology

The ring topology applies to common scenarios. Due to its

strong self-healing capability, the ring topology is preferred if
permitted by the routing
If there is a breaking point in the ring, the ring breaks into

two chains at the breaking point automatically. In this way,
the BTSs preceding and following the breaking point can
work normally despite the breaking point; thus improving the
robustness of the system
Page84
DRFU Topologies Configuration

The DRFU supports

various network
topologies: star, chain,
and ring
Page85
Contents
1. BTS3900 Overview
5. BTS3900 Network
Page86
Introduction of GRFU
GRFU is based on multi-carrier technology, one GRFU can

support six TRXs at most.
GRFU performs modulation and demodulation between

baseband signals and RF signals, processes data, and
combines and divides signals.
The main new features and functions of GRFU

Inner Bias-Tee. Integration of feeder current to TMA.
Provides power sharing. Improves the network coverage,

reduces the interference and power consumption and save
the device cost.
Page87
Ports of GRFU
Port Type
Connector
Type
Label
Description
ANT_RXB
DIN
connector
ANT_TX/RXA
DIN
connector
CPRI0
SFP female
connector
Connecting to the BBU, or the upper-level

RFU during the cascading.
CPRI1
SFP female
connector
Connecting to the lower-level RFU during

the cascading.
RX_INB
QMA
female
connector
Input port of diversity signals in the

antenna channel.
RX_OUTA
QMA
female
connector
Output port of diversity signals in the

antenna channel.
Power supply port
PWR
3V3 power
connector
Feeding power.
Monitoring port
MON
RJ45
connector
Monitoring port.
Port for trancieving

RF signals
Connecting to the antenna subsystem.
CPRI
Interconnection port
for RF receive
signals
Page88
LEDs of GRFU
LED
RUN
ALM
ACT
VSWR
Color
Green
Red
Status
Description
ON
The power input is normal, but the module is faulty.
OFF
There is no power supply, or the module is faulty.
1s ON
1s OFF
The module is running properly.
0.2s ON
0.2s OFF
The software is being loaded to the module.
1s ON
1s OFF
A fault alarm is generated.
OFF
ON
The module is functional and is correctly connected to

the BBU.
OFF
The connection with the BBU is not set up.
OFF
No VSWR alarm is generated.
ON
The VSWR alarm is generated on the ANT_TX/RX port.
Green
Red
Page89
LEDs of GRFU
CPRI0
CPRI1
Red
Green
Red
Green
ON (Green)
ON (Red)
The interface module fails to receive

signals.
1s ON
1s OFF(Red)
The CPRI link is out of lock.
ON (Green)
ON (Red)
The interface module fails to receive

signals.
1s ON,
1s OFF (Red)
The CPRI link is out of lock.
Page90
Compare GRFU with DRFU

Port Type
Port for
transceiving
RF signals
CPRI
GRFU
ANT_TX/RXA
Relative
position
DRFU
Relative
position
lower
ANT1
upper
upper
ANT2
lower
CPRI0
lower
CPRI0
upper
CPRI1
upper
CPRI1
lower
RX_INB
upper
ANT_RXB
Rx_1 in
Interconnection
Rx_1 out
port for RF
Receive signals
Rx_2 in
RX_OUTA
lower
Rx_2 out
Monitoring port
MON
existence
Non
existence
Page91
Output power of GRFU

The output power of different configuration is also

configured differently
Frequency bands
Output power
Configuration
GMSK/8PSK
PGSM 900MHz / GSM1800MHz
S1
80W/53W
S2
40W/26W
S3
31W/20W
S4
27W/17W
S5
18W/12W
S6
16W/10W
Page92
Limitation of GRFU
If the frequency interval of a cell is outside the range of 15MHz, 2 GRFUs can
be considered to be used and the range of frequency for each GRFU also
should be within15MHz.
Generally, it is suggested that the number of carriers should be set to 2

GRFUs averagely if 2 GRFUs are used in a cell. For example: S8 should be
configured as 4+4 when 2 GRFU are used.
GRFU supports whole frequency band of PGSM 900MHz, high 45MHz

frequency band and low 45MHz frequency band of DCS1800MHz.
GRFU
DL
UL
Whole 25MHz frequency

band of 900MHz
935-960MHz
890-915MHz
Low 45MHz of 1800MHz
1805-1850MHz
1710-1755MHz
High 45MHz of 1800MHz
1835-1880MHz
1740-1785MHz
Page93
Configuration Principle of GRFU

The DRFU and GRFU can be configured in the same cabinet.
When the GRFU is configured, a single BTS3900 provides a

maximumof 36 carriers with the maximum cell configuration of
S12/12/12. In addition, a site configured with the BTS3900s
can support a maximum of 72 carriers, with the maximum cell
configuration of S24/24/24.
One GRFU does not serve two cells.
Each cell with a single antenna can be configured with a

maximum of two GRFUs.
Page94
Transmit Mode and Receive Mode of

GRFU
GRFU Transmit Mode

Transmit independency or combining
GRFU Receive Mode

Main diversity receiver
Page95
GRFU S2-S6 Configuration

S2-S6 Configuration

Combining
Page96
GRFU S7-S12 Configuration

S7-S12 Configuration
TX mode: Transmit Independency

or Combining
Antenna mode: Single

antenna(1TX+2RX)
Page97
DRFUGRFU Configuration

Combining
Antenna mode:
GRFU: Single antenna(1TX+2RX)
DRFU: Single antenna(1TX+2RX)
Page98

Combining
Antenna mode:
GRFU: Double antenna(1TX+2RX)
DRFU: Double antenna(1TX+2RX)
Page99
GSM BTS3900
Commissioning
www.huawei.com
Foreword
describes the procedures for commissioning and verifying

the BTS3900/BTS3900A GSM after it is installed. The
commissioning and verification procedures ensure that
the BTS3900/BTS3900A GSM operates as required
Page1
Contents
1. Overview of the Commissioning
2. Commissioning Procedure
3. Implementation
Page2
Overview of the commissioning

Before the commissioning, you must arrange for the tools,

obtain the information about the site to be commissioned, and
download the correct software for the boards in the
BTS3900/BTS3900A
Tools: PC, Multimeter, Power Meter, Site Master, GSM MSs for
testing, Ethernet cable, Serial port cable, Flat-head screwdriver,
Light emitting diode (LED)
Page3
Contents
2. Commissioning Procedure
3. Implementation
Page4
Commissioning Procedure
Page5
Commissioning Procedure
Page6
Contents
2. Run the Site Maintenance Terminal
3. Implementation
Page7
Contents
3. Technical Description
3.1 Starting the Site Maintenance Terminal
3.2 Configuring the Basic Data of the BTS
3.3 Configuring Logical Objects of the BTS
3.4 Checking the Active Software Version
3.5 Checking the Transmission Between the BBU and RFU
3.6 Checking the Running Status of the BTS
3.7 Checking the Alarm Information of the BTS
Page8
Local Maintenance
Connect the maintenance terminal computer with the ETH port

on TMU by crossed cable.
Page9
Start the Local Terminal System
Page10
Login
Page11
Obtaining the Site Management right
Page12
Contents
Page13
Board Configuration
Click Board in the navigation pane. Board Configuration

and Board Management are displayed.
Double-click Board Configuration. The Board

Configuration window is displayed
Page14
Board Configuration
Page15
Board Configuration
Double-click GTMU. The Topology Configuration window

is displayed
Page16
Board Configuration
Click Add RRU. Set the parameters in the Deploy DRRU

dialog box, Set Card Type to DRFU, Card No. to 0, SFP No.
to 0, and Hop No. to 1. These values are taken only as an
example in this section
Page17
Board Configuration
Double-click GTMU. The Topology Configuration window

is displayed
Page18
Board Configuration
Click Close to return to the Board Configuration window.

Right-click the slot, and choose the board to be
configured from the shortcut menu. Set PMU, FMU, and
GATM
Page19
Contents
Page20
Add a cell
Click Site0, and

double-click
Site
Configuration in
the Function
area. The Site
Configuration
dialog box is
displayed
Page21
Add a cell
Click Site0, and

then click Add
Subobject. In the
Object Attributes
area, specify
Object No. and
Object Name. In
the Object
Operation area,
Cell0 is added
Page22
Bind the carrier

Click Cell0, and

select the TRX
to be
configured in
the Boardtype
drop-down list
box. Set the
board type to
DRFU
Page23
Bind the carrier

Click Add Subobject.

In the Object
Attributes area,
specify Object No.,
Object Name, Board
No., and Pass No..
Carrier0 is added in
the Object Operation
area. The carrier is
bound to pass 0 of
the TRX whose
board number is 0
Page24
Configure the second carrier

Set Object
Name to
Carrier1, Board
No. to 0, and
Pass No. to 1
Page25
Configure the second carrier

Click Site0. The

Set button is
available. Click
Set, Configuring
cell succeeded
is available
Page26
Configured cell and channels

Close the dialog box.

The configured cell is
displayed in the
navigation pane
Page27
Activate the site data

Choose Site0 >

Site Opstart >
OK. Site Opstart
successfully. is
displayed, and
click Close
Page28
Activate the cell data

Choose Cell0 >

Cell Opstart >
OK. Cell Opstart
successfully. is
displayed, and
click Close
Page29
Activate the TRX data

Choose BT0 >

BT Opstart > OK.
BT Opstart
successfully. is
displayed, and
click Close
Page30
Specify frequency in ARFCN

Choose RC0 > RC

Attributes Management.
Specify frequency in
ARFCN, and click Set.
Getting RC attributes
succeeded is displayed.
Click Close
Page31
Activate the RC data

Choose RC0 >

RC Opstart >
OK. RC Opstart
successfully is
displayed. Click
Close
Page32
Board Management window

SFP Port
Inconsistency
Alarm is cleared.
The status of
the GTMU is
Active normal
Page33
Contents
Page34
Checking the Active Software Version

In the left pane of

the Site
Maintenance
Terminal System
window, select
Board. In the right
pane of the
window, doubleclick Board
Management
Page35
Checking the DRFU Software Version

Double-click
GTMU in the
Board
Management
window. The
Topology
Management
window is
displayed
Page36
Checking the DRFU Software Version

Right-click DRFU0,
and then click
Board
Information. The
query is
successful. The
Board
Information
dialog box is
displayed
Page37
Checking the GTMU Software Version

Right-click GTMU,
and choose Board
Information from
the shortcut
menu. The Board
Information
dialog box is
displayed
Page38
Contents
Page39
Checking the Transmission Between

the BBU and RFU
Check the status of the CPRI0 LED on the GTMU panel of

the BBU and the status of the CPRI0 and CPRI1 LEDs in
the RFU panel
If all the LEDs are in the on in green status, the

communication between the CPRI0 port on the BBU and
the RFU is normal
Page40
Contents
Page41
LEDs on the BBU

Board or
Module
GTMU
LED
Color
Normal State
RUN
Green
Blinking (ON for 1s and OFF for 1s)
ALM
Red
OFF
ACT
Green
ON
LIU0 to LIU3
Green
LEDs LIU0 to LIU3 represent the four E1

links. If the links are connected normally,
LIU LEDs are OFF. If the links are not
connected to the BSC yet or the
transmission is unavailable, LIU LEDs
are ON.
CPRI0 to
CPRI5
Green
When CPRI0 to CPRI5 ports are not in use,

the LEDs are OFF. When the BBU is
normally connected to the RFU, the
corresponding LED is ON.
UBFA
STATE
Green
UPEU
RUN
Green
ON
Page42
LEDs on the DRFU

LED
Color
Normal State
RUN
ALM
OFF
ACT
ON steady: The DRFU works properly.
VSWR
Red
OFF
CPRI0
Green
If the DRFU is normally connected to the

BBU or another RFU, the LED is ON. If the
DRFU is not connected, the LED is OFF.
CPRI1
Green
If the DRFU is normally connected to the

BBU or another RFU, the LED is ON. If the
DRFU is not connected, the LED is OFF.
Page43
LEDs on the GATM

LED
Color
Normal State
RUN
Green
ACT
Green
ON: The AISG link is available.
Green
Blinking quickly: The AISG link is in transmission

status.
Red
OFF
ALM
Page44
LEDs on the FAN & PMU

LED
Color
Normal State
RUN
Green
Blinking (ON for 1s and

OFF for 1s)
ALM
Red
OFF
Page45
LEDs on the PSU

PSU
PSU (AC/DC)
PSU (DC/DC)
LED
Color
Normal State
Power input LED (top) Green
ON
Power protection
LED (middle)
Yellow
OFF
Power failure LED

(bottom)
Red
OFF
Power input LED (left) Green
ON
Power protection
LED (middle)
Yellow
OFF
Power failure LED

(right)
Red
OFF
Page46
Contents
Page47
Checking the Alarm Information of the BTS

In the left pane of

the Site
Maintenance
Terminal System
window, select
Board. In the right
pane of the
window, doubleclick Board
Management
Page48
Checking the Alarm Information of the BTS

Right-click the
board or module to
be queried, and
choose Board
Alarm. Click the
red grid, then the
details about the
alarm are displayed
in the right pane
Page49
MBTS3900
0. Generate BSC Configuration Files for CME
1. GSM BTS3900 abis over TDM
2. GSM BTS3900 abis over IP
3. Optional
3.1 1 BTS BSC. ( Reparent BTS Inside one BSC)
3.2 / 1 BTS BSC
3.3 TCH SDCH
3.4 TS FR/HR
3.5 HDX
prepared by Rukhlov.Artyom@huawei.com
0.
Generate BSC Configuration Files for CME
LMT BSC6900 EXP CFGSYNFILE, BCP, - CME.
0.1. File Manager BSC f : /bam/version_a/ftp/ExportCMESyncView

/bam/version_b/ftp/ExportCMESyncView ..
0.3 CME Data Management Add NE.
0.4 Network Element Main.
1. GSM BTS3900 abis over TDM

1.1. BSC, NE (). ( offline
NE)
1.2. A-bis_
1.3. ( )
Multiplexing mode Abis

1:1 OML, RSL 64 kbit/s 1 TS Fix/Flex ( 10 TRx FR/HR )
2:1 - OML, RSL 32 kbit/s Fix/Flex ( 12 TRx FR/HR )
3:1 - Fix/Flex
4:1 - OML, RSL 16 kbit/s Fix/Flex ( 15 TRx FR )
5:1 OML +ESL + 3RSL 64 kbit/s (31TS) Flex (21TRx/HR & 23TRx/FR)
6:1 OML +ESL + 4RSL 64 kbit/s (31TS) Flex 21TRx/HR & 23TRx/FR)
16k test
(OML operation & maintenance Link BTS)
(RSL radio signaling link TRx)
(ESL enhanced signaling link) TRx RSL
1.4. ( )
, .
10
1.5.
11
Cell Frequency , ,
12
1.6.
13
14
15
16
1.7. TRx-
BTS3900. ( RFU config by slot (.5), , !)
17
18
1.8. (CPRI)
, !
19
20
1.9.
0-3-0 -
.
Sending Receiving mode 2Tx + 2Rx!!! 1Tx + 2Rx, =3,3 dB!!!
21
22
(8-15 )
23
1.10. BCCH TRx Bind TRx

Close.
.
24
25
26
1.11. Fix abis, Idle TS
1.12.
27
28
1.13. PCU
29
1.14. . , - ,
.
30
!!!
31
32
1.15. MML .
2. GSM BTS3900 abis over IP

2.1. BSC
2.2. A-bis_ (IP)
33
2.3. abis-
34
2.3
35
Abis TDM ( c 1.4 1.13)

2.14 IP
36
, BTS Equipment Serial Number (ESN BBU)
37
Transport/ Abis/ Adjacent Node/ +/

Adjacent Node BTS over IP
38
Adjacent Node Mapping/ +/ ANI BTS
39
Gold user TRMMAP index
Factor table index 0 -
2.15 , .
2.16 MML
BSC6900!!!
40
3. Optional
3.1 1 BTS BSC. ( Reparent BTS Inside one BSC).
41
42
43
44
45
3.2 / 1 BTS BSC.
46
47
48
3.3 TCH SDCH
The process of converting the SDCCH to the TCH is as follows:

1. Each cell is configured with a counter.
2. Each time when the TCH is converted to the SDCCH, the counter is set to TCH Minimum Recovery Time. The value of the counter is
adjusted every three seconds.
o If the number of idle SDCCHs > 8 + Idle SDCCH Threshold N1, the value of the counter is subtracted by 3.
o If the number of current idle SDCCHs < 8 + Idle SDCCH Threshold N1, the value of the counter is added by 12, but the value of the
counter should not exceed the TCH minimum recovery time.
o If the number of idle SDCCHs = 8 + Idle SDCCH Threshold N1, the value of the counter remains unchanged.
3. If the value of the counter is smaller than or equal to 0 after adjustment, the SDCCH is converted to the TCH.
49
50
3.4 TS FR/HR
1. In the Main navigation tree of the planned data area, right-click any TRX, and then choose TRX Configuration Express from the shortcut
menu. The window for configuring the parameters is displayed in the right pane.
2. In the lower left part of the configuration window, select GTRXDEV > Site TRX Dev Property, and then set TCH Rate Adjust Allowed to
YES in the right pane of the window.
51
52

100, TS
FR!
3. In the Main navigation tree of the planned data area, right-click a cell, and then choose Cell Configuration Express from the shortcut menu. The
window for configuring this cell is displayed in the right pane.
4. In the lower left part of the configuration window, select Channel Management, select the configuration objects in sequence, and then modify
the attribute values in the right pane of the window.
53
54
3.5 HDX.

Huawei - BSC6900 & BTS3900

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Huawei - BSC6900 & BTS3900

Diunggah oleh

Hak Cipta:

Format Tersedia

GSM Principles

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Upon completion of this course, you will be able to:

Grasp basic idea of GSM system such as frequency spectrum,

Grasp certain numbers that refer to BSS

Grasp the 4 kinds of channel combination and understand the idea

Know some radio techniques

Get the idea of EDGE

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

BSS Feature Description

BSS Signaling Analysis Manual

BSC Technical Manual

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

GSM system overview

The GSM system is a frequency- and time-division cellular system,

Cellular systems are designed to operate with groups of low-power

Data for different users is conveyed in time intervals called slots ,

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Standard Protocol for GSM take effect

GSM system began to provide service in Europe(2G)

System was named as Global System for

Provide services for the whole world

Micro Cell Technique is used in GSM system

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Macro Cell and Micro Cell

A certain radio coverage area formed by a set of transceivers that

In the beginning , High-Power BTSs are adopted to provide services. The

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Multiple Access Technique

Multiple Access Technique allows many subscribers to

There are three kinds of basic Multiple Access Technique :

GSM system adopt FDD-TDMA (FDMA and TDMA

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

FDMA uses different frequency

The whole frequency spectrum

TDMA accomplishes the

A carrier is divided into

same frequency in different

CDMA accomplishes the

Special coding is adopted before

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

The Frequency Spectrum

The Frequency Spectrum

Base Station Receive

Base Station Transmit

The Frequency Spectrum

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

The frequency resource of mobile system is very limited.

The different Subscribers can use the same frequency in

The quality of communication must be ensured.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

4 site X 3 cells reuse

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

120 Degree Cell

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.

GSM-GPRS Network Component

GSM /GPRS BSS

Copyright 2010 Huawei Technologies Co., Ltd. All rights reserved.