You are on page 1of 25

MXBSC PRESENTATION

Khalil-ur-Rehman

All rights reserved 2005, Evolium

Summary
G2 BSC Hardware Overview MxBSC Software Architecture MxBSC Hardware Presentation MxBSC Functional Improvements Evolution Capacity Improvements
Page 2

G2 BSC Hardware Overview


y Commonly in G2 BSC for Alcatel

there are three racks and each rack contains eight shelves.
y There are eight shelves in one BSC

rack. Count starts from breakers shelf at the top and ends at the last shelf in the bottom.

Page 3

G2 BSC Hardware Overview


Three main Terminal Sub Units (TSUs)
y Common TSU ( Within the BSC). y Abis TSU ( BSC to BTS). y ATER TSU ( BSC to Transcoder)

G2 BSC Hardware Overview


COMMON TSU y In the common TSU the functions are carried out by the BSC. For Example call initiation, call establishment and handovers etc. y The card which comes in the common TSU domain is CPRC (cpra card) CPRC (Common Processor Type C) y There are six cpra cards in the first rack of the Alcatel BSC. y Two Cpra OSI (Open system interface). These are responsible for establishing the link b/w BSC and the OMCR. IN short the these two CPRC contain the OML of the BSC through X.25 link. y Two Cpra Sis These are the main controller processors for the BSC. The various functions are carried out through this card. y Two Cpra Broadcast. Used for the local bus interface in the BSC.

G2 BSC Hardware Overview


ABIS TSU y Abis Tsu is responsible for the link between the BTS and the BSC. One Abis TSU contains one BIUA card and eight TCUC cards and two access switches.
y

BIUA (BTS Interface Unit Type A) y One BIUA contains six abis. Abis is the link between the BTS and the BSC. Its a 2 MB link. One BIUA has eight TCUC cards. TCUC (TRX Control Unit Type C) y Basically TRX are configured on the TCUC cards. y One TCUC can contain four full rate and two half rate TRX. y TCUC also contain the OML for the site.

G2 BSC Hardware Overview


y ATER TSU y One Ater TSU contains two ASMB cards, eight DTCC cards

and two access switches. ASMB (Ater Sub Multiplexer at the BSC) y One ASMB is one Ater mux. y One DTCC (Digital trunk controller type C). TSCA (Transmisson Submultiplexer Contoller Type A) y All the transmission cards are working under this important card. Each rack contains this card at shelf eight and slot 5.

MxBSC Software Architecture

y From G2BSC to MxBSC y BSC application architecture y MxPF Software

Page 8

MxBSC Software Architecture From G2BSC to MxBSC


TP & LIU Shelf
Abis TSU
TC U C TC U C

CCP
G roup Switch 8 Planes 2Stages

Ater TSU
D TC C D TC C D TC C D TC C D TC C D TC C D TC C

6x G .703 Abis I/F


BIU A

TC U C TC U C TC U C TC U C TC U C TC U C

ASM B

AS

AS

D TC C

ASM B

2x G .703 Ater m uxed I/F

TSL

Q1 bus

SSW
TSC A

AS

No more CPR broadcast: the feature is emulated. DTC TCH-RM does not manage Ater anymore and are moved on OMCP.

OMCP

C PR C C PR C C PR C C PR C C PR C C PR C C PR C C PR C

Broadcast bus

Com m on Functions TSU

Page 9

MxBSC Software Architecture BSC application architecture


y G2BSC Control Element (TCU, DTC, CPR, TSC) becomes MxBSC

Virtual Control Element (VTCU, VDTC, VCPR, VTSC)


One E per G2 B r Mx VC -1
Application (FMM/SSM)

SC

oard VC -n
Application (FMM/SSM)

licati

( P

BSC Porting


DBCS PFM DBCS PFM

V S O N P

CMW

Boot

V S

CMW

Boot

MxPF Carrier Grade Linux


DBCS: MxPF: PFM: S D: PF: V S G2 BSC Database Management System Mx Platform software G2 BSC Platform Management G2 BSC perating System Platform drivers Simulation of S D

Page 10

MxBSC Software Architecture MxPF Software


Mx BSC applications
Adaptation Layer

MxPF EndurX Self reliant Carrier Grade Linux AdvancedTCA (PICMG 3.x)
Page 11

>

MxPF is in charge of processes management, hardware management, software management, init and few basic services like traces or date synchronization.

> EndurX library manages the hardware environment via the Hardware Platform Interface (HPI) based on IPMI software and hardware standard.

>

Self-Reliant provides the framework for developing applications that deliver service availability into a clustered distributed environment.

MxBSC HARDWARE PRESENTATION


y SSW y OMCP y CCP y TP-GSM y MUX y LIU

Page 12

MxBSC HARDWARE PRESENTATION SSW Switch Board


y SBL: SSW-HW 1&2 y Redundancy: 1+1

y Allows exchanges between all the elements of the platform and

external IP/Ethernet equipment: y OMC-R physical interface y CBC physical interface y NEM terminal connection y Second ATCA shelf connection y External Alarm Box connection

Page 13

MxBSC HARDWARE PRESENTATION OMCP O&M Control Processing board


y SBL: CP-HW, CP-LOG 1&2 y Redundancy: 1+1

y O&M Control Processing board based on ATCA technology

equipped with a permanent storage device. In charge of managing the whole platform as system manager and O&M applications. y O&M - logical interface to the Operation and Maintenance Center (OMC-R) y VCPR: S-CPR & O-CPR software y DTC TCH/RM y TSC software

Page 14

MxBSC HARDWARE PRESENTATION CCP Control Processing board


y SBL: CP-HW, CP-LOG 3, 4 & 5 y Redundancy: N+1

y Call Control Processing board based on ATCA technology used for

call control functions. y Identical to OMCP board without Hard disk. y VTCU: TCU software (50 per CCP) y VDTC: DTC software (40 CS & 24 PS per CCP)

Page 15

MxBSC HARDWARE PRESENTATION TP-GSM Transmission Processing board


y SBL: TP-HW 1&2 y Redundancy: 1+1

y Provide telecom transmission /transport interfaces to the MX

platform. y Configuration Management y Performance Parameters Management y HDLC termination y SS7 termination y NE1oE y Q1 y Ring control
Page 16

MxBSC HARDWARE PRESENTATION MUX


y SBL: ECU 1&2 y Redundancy: 1+1

y Multiplexing and de-multiplexing of up to 16 E1 streams (16 E1 each)

from the LIU boards y Configuration management and supervision of the LIU boards y 1 GbE interface y NE1oE packing/unpacking to/from up to 32 physical entities (TPGSM boards) y Debug interface

Page 17

MxBSC HARDWARE PRESENTATION LIU


y SBL: ETU 1 to 16 y No redundancy

y Connection of up to 16 physical E1 interfaces (Tx / Rx) y Multiplexing and de-multiplexing of 16 E1 to/from the two MUX

boards y LIU synchronization y Communication with the MUX boards for LIU board configuration and supervision y Detection of LOS on any E1 connected and in use

Page 18

MxBSC Functional Improvements


y New dimensioning y New switching connectivity

Page 19

MxBSC Functional Improvements

New dimensioning
fig ra ti a p a cit T e N N N TR e ll T is te r te r P S P N N N P N N N N N T T T S PS 2 2 2 200 200 200 0 0 0 2 2 20 2 00 0 2 00 2 2 0 0 20 2 2 00

T H -R p a irs P R p a irs T S C p a irs CE per CCP C E /O C P

CE per

ar

Telecom traffic: from 1900 to 600 erlangs

Page 20

MxBSC Functional Improvements

New switching connectivity


With G2 BSC the CS and the PS traffics goes through the TCU and DTC With MX BSC the CS and the PS traffics are switched inside the TP
Switc i
1 TCU = 32 BCI 1 FR TRE = 8 BCI 1 DR TRE = 16 BCI 1 EXTS = 4 BCI 1 TCU = 4 FR TRE 1 TCU = 2 DR TRE 1 TCU = 8 EXTS
CCP TCU

DTC

TCU

TC

BI
Abi

ASMB
Ater

TP
Abis Ater

Signaling Telecom Traffic

Signaling Telecom Traffic

G2BSC
Page 21

MxBSC

Evolution Capacity Improvements


TRE/VTCU Mapping

HSL MODE

Evolution Capacity Improvements


TRE/VTCU Mapping
y In B10, the maximum number of TREs mapped on a VTCU is 4

whatever their type (FR/DR). A CCP board contains 50 VTCUs and can manage upto 1500 TCHs

Evolution Capacity Improvements


y HSL MODE y In B10, in LSL mode, the bandwidth is not wide enough to carry the

No.7 signaling in the case of large-capacity y BSCs (that can support more than 600 TRXs). Therefore, the HSL mode is implemented.
y y In TDM mode, the HSL links are connected from the BSC to the

MSC without going through the TransCoder (TC). y For redundancy purposes, 2 HSLs are used. The load is shared between both HSLs.

Evolution Capacity Improvements


HSL Engineering Rules The HSL configuration requires 2 AterMux. Any AterMux can be candidate if: It does not carry Qmux. It does not carry IP over Ater. It is configured for CS traffic only. The HSL and LSL modes cannot be mixed on a BSC. The AterMux supporting HSL must be configured on different LIU boards.

Page 25

You might also like