bsc description (3fl12479abaawbzza4)

9130 BSC Evolution Description in B10 Page 1

All Rights Reserved Alcatel-Lucent 2010

Do not delete this graphic elements in here:


3FL12479ABAAWBZZA Edition 4

Mobile Network9130 BSC Evolution Description

in B10

STUDENT GUIDE




Alcatel Lucent 9130 BSC Evolution Description in B10Mobile Network

Blank Page

This page is left blank intentionally

First editionLast name, first nameYYYY-MM-DD01

RemarksAuthorDateEdition

Document History





Module Objectives

Upon completion of this module, you should be able to:

Identify the location of the 9130 BSC Evolution within the GSM network

Describe the functions implemented in the 9130 BSC Evolution

Describe the hardware architecture of the 9130 BSC Evolution

Describe the software architecture organization of the 9130 BSC Evolution

Describe the IP architecture of the 9130 BSC Evolution

Describe the defense mechanism of the 9130 BSC Evolution in case of hardware or software failure





Module Objectives [cont.]

This page is left blank intentionally





Table of Contents

Switch to notes view!Page

1 9130 BSC Evolution Functions Description 72 9130 BSC Evolution Hardware Description 152.1 An Architecture Based on the MX Platform 162.2 General View of the Hardware Architecture 182.3 Hardware Description of ATCA Modules 222.4 Hardware Description of LIU Modules 392.5 Power Distribution Unit Cabling 42

3 9130 BSC Evolution Software Architecture 463.1 Generalities 473.2 9130 BSC Evolution Software Organization 483.3 BSS Software Organization 56

4 9130 BSC Evolution IP Architecture 654.1 9130 BSC Evolution Traffic Flows 664.2 Internal IP Addresses of the 9130 BSC Evolution 684.3 External IP Addresses of the 9130 BSC Evolution 72

5 9130 BSC Evolution Defense Mechanism 775.1 Redundancy Schemes 785.2 Switchover Scenarios 79

6 9130 BSC Evolution Performance 816.1 9130 BSC Evolution Standalone Configuration 826.2 9130 BSC Evolution Rack-Shared Configuration 836.3 Capacity: BSC Capacities in Terms of Boards 846.4 Capacity: Capacity and Dimensioning for E1 Links 856.5 Capacity: Abis and Atermux Allocation on LIU Boards 866.6 HSL Introduction 87

7 Annex 917.1 ATCA Shelf Layout for BSC "Standalone Configuration" 927.2 Board Allocation in LIU Shelf for BSC "Standalone Configuration" 937.3 BSC Standalone and Rack-Shared Configurations 947.4 IP Addresses in Subnets A/B/C 957.5 9130 BSC Evolution VLAN 967.6 Interface between 9130 BSC Evolution and OMC-R: Direct IP Network 977.7 Interface between 9130 BSC Evolution and OMC-R: IP over Ater 987.8 Interface between 9130 BSC Evolution and CBC: Direct IP Network 997.9 Interface between 9130 BSC Evolution and CBC: IP over Ater 1007.10 ATCA Back Panel 1017.11 Architecture BSC G2 Mx BSC 1027.12 Abis Signaling Flow for LAPD QMUX RW 1037.13 Ater Signaling Flow 1047.14 Traffic Flow PS CS 1057.15 TDM Extraction 1067.16 Alarm Octet Principle 1077.17 TCP/IP Model 1087.18 MAC Address Definition 1097.19 IP Address Definition 1107.20 What Is a LAN? 1127.21 LAN Definition: Subnetwork Constitution 1137.22 Network Packet Transfer 115

8 Abbreviations and Acronyms 117





Table of Contents [cont.]

Switch to notes view!Page





1 9130 BSC Evolution Functions Description






Location and Functions of the 9130 BSC Evolution in the GSM Architecture

The 9130 BSC, one component of the BSS has 3 functions:

Telecom

Transmission

O&M

Abis Atermux

A

Gb

GSM Core Network

GPRS Core Network

Gr

BTS9130 BSC TC

MFS

Mobile Radio Acces

Ms

Air

AuC

VLR

MSC

PDN

ISDN

PSTN

GGSNSGSN

HLR

IP

In a Mobile Radio Network, the Mobile Radio Access part or BSS provides radio coverage for GSM/GPRS/EDGE

subscribers in a defined area. Its principal role is to provide traffic channels and support signaling between:

Mobile Stations and the Mobile Core Circuit-Switching part in case of GSM circuit-switched transmission for

voice.

Mobile Stations and the General Packet Radio Services (GPRS) Mobile Core Network interconnecting the

Internet world in case of packet-switched transmission for data.

IP network






Telecom Functions

The main telecom functions performed by the 9130 BSC Evolution are:

GSM and GPRS Radio Frequency Management: managing the radio resources

Traffic Channel Resources Management: Selecting TCH.

Establishing and releasing radio resources in response to requests from the MSC, the MFS and the MS

Short Message Service Cell Broadcast: Broadcasting messages to all the MSs of one or more cells

BSSAP Protocol Management: Handling messages between the MS and the MSC for circuit service

BSCGP Protocol management: Handling messages between MS and MFS for packet service

The GSM Radio Frequency Management consists of 4 sub-functions:

Managing the broadcast and common control channels.

Managing the signaling channels.

Processing radio measurements.

Handling the "In call-modification".

The GPRS radio frequency management consists of 4 sub-functions:

Managing the packet broadcast and common control channels.

Managing the packet data channels

TCH RM

The selection of a TCH can be requested for a variety of reasons such as the initial assignment as a channel

for speech and data use, the handover of a channel, etc.

Normally acts on requests immediately.

Can queue requests, if a TCH is not available, until either a TCH becomes free or a timer expires.

SMS-Cell Broadcast

There are two types of Short Message Service (SMS):

Point-to-point SMS, which allows a short message to be sent to, or received from, a specific MS.

SMS-CB service, which allows messages to be broadcast to all the MSs of a cell. This service can be used for

a number of reasons. For example, to transmit charging information, road traffic information, etc. An SMS-CB

message is transmitted to all the cells connected to the BSC, or to selected cells only, as required.






Telecom Functions [cont.]

The BSSAP protocol which handles messages distribution between the MS and the MSC is composed of 2 protocols:

DTAP: messages transparent for the 9130 BSC Evolution.

BSSMAP: messages understood by the 9130 BSC Evolution.

The BSCGP protocol used between the 9130 BSC Evolution and the MFS is responsible for:

GSM/GPRS paging.

GPRS access procedure.

Allocation / de-allocation of PDCH or MPDCH within a cell.

Activation / release of PDCH.

BSSMAPDTAP

BSCGP

TCBSC

MFS

MSC

BTS

The BSSMAP performs radio channel management functions such as assignment, handover for channels that

are used for circuit-switched calls.

The GPRSAP performs radio channel management functions for channels that are used for packet-switched

calls.






Transmission Functions

The transmission functions consist for the 9130 BSC Evolution inproviding BTS to TC access for CS Services and MFS access for PSservices.

The transmission architecture can be viewed as four major parts:

NE1oE control

Remote Tributary Alarm management

Remote NE configuration and supervision via Qmux

Ring control for Abis.

The Qmux protocol is a transmission protocol used to supervise and to configure the transmission element of TC equipment and non-EvoliumBTS.

This implies a Transmission Sub-system Controller (TSC) function, responsible for:

Polling the transmission elements.

Sending data to the transmission elements.

Reporting alarms.

The transmission architecture can be viewed as four major parts:

NE1oE control:

NE1oE control provides TDM frame transferring inside the 9130 BSC Evolution platform, and user plane

supervision and redundancy management.

This NE1oE will be explained in the 9130 BSC Evolution Hardware Description chapter.

Remote Tributary Alarm management:

This allows to supervise A terminations points on TC side

(For more information about alarm octet, consult the Annex chapter)

Remote NE configuration and supervision via Qmux.

Ring control for Abis:

The purpose of a ring configuration is to protect against any fault on a link or a BTS, which leads to the

loss of BTSs that are not faulty.

This protection is performed by TPGSM (see the 9130 BSC Evolution Hardware Description chapter).

The TSC is not involved in the supervision and the configuration of the transmission board on Evolium BTS

because these operations are done via OML.






Transmission Functions - TSC Clustering

: Qmux

TCIL bus

Mux/ Demux

f unct ion

Atermux1

Atermux2

Atermux6

Cluster

Switching

Function

MT120

MT120

BSC TC

Atermux7

Atermux8

Atermux12

MT120

One TC cluster is a group of 6 MT120 boards allocated to one BSC in case of an A925 TC, or 6 ASMC, 24 ATBX,

48 DT16 in case of a TC G2.

The TSC is not involved in the supervision and the configuration of the transmission board on Evolium BTS

because these operations are done via OML.

Rule: 1 TSC per TC cluster (6 atermux). The first 2 Atermux support Qmux nibble for security reasons. The Qmux nibble is located on the first nibble of the TS 14 on the first 2 atermux of each group of 6 atermux.






Transmission Functions - 9130 BSC Evolution and Channels

In the diagram below, find the mapping of channels on Abis, Atermux, A and Gb interfaces.

GPRS Core Network

QmuxN7

RSL

OML GCH

GSL

CIC

N7

Bearer Channel

TCH

BTS

Alarmoctet

MFS

TC

Atermux Gb

9130 BSC

AtermuxAbis

GSM Core Network

A

CIC compressed






O&M Functions

The main O&M functions performed by the 9130 BSC Evoultion are:

Database Management

Software Management

Logical and Hardware Configuration Management

Fault Management

Performance Management

Remote Inventory Management

BSC

OMC-R

BSC terminal

The Database (or DLS for Data Load Segment) of the 9130 BSC Evolution ontains all the hardware and logical configuration of the BSS.

This Database is updated via operator commands from the OMC-R.

Software Management allows the operator to upgrade or maintain the current BSS Software.

Logical and Hardware Configuration Management allows the operator to display or modify the current BSS hardware and logical Configuration (extension reduction operations on the field, configure certain BSS parameters like BTS characteristics, modify or create cell, etc.).

Fault Management

The 9130 BSC Evolution manages all the maintenance functions relating to itself, that is, detection, localization, defense and reconfiguration. Reports are sent to the OMC-R when the BSC detects faults or performs maintenance functions.

Performance Management

The BSC Performance Management function, on request of the OMC-R, monitors the telecommunication operations and produces reports. These reports contain processed counters. The reports are stored on disk and are available to the operator at the OMC-R. The BSC controls the sampling, data collection and generation of observation and measurement files. It then transfers the files (either on-demand or autonomously) to the OMC-R.

Remote Inventory Management

The Remote Inventory is a facility which consists in retrieving inventory hardware and firmware of the 9130 BSC Evolution. This facility can be performed locally but also remotely with the OMC-R.

All those functions are performed by the BSC and the OMC-R.

If the OMC-R is not connected, the network is still operational, but these tasks may not be performed.





2 9130 BSC Evolution Hardware Description






2.1 An Architecture Based on the MX Platform

The MX platform is the Multi-Standard Controller Platform for the Alcatel-Lucent Mobile Equipment:

9130 BSC

9130 MFS

Interests of MX platform:

Increasing BSC and MFS capacities

Optimization of BSC and MFS configuration

Equipment cost reduction

Network maintenance simplification

Characteristics of the MX platform: based on ATCA technology

The 9130 BSC capacity ranges from 200 TRXs (1 active CCP board) to 1000 TRXs (5 active CCP boards).

Maintenance is easier thanks to redundancy and a short number of board types.





2.1 An Architecture Based on the MX Platform

ATCA Shelf Description

Characteristics of the ATCA Subrack:

A standard development fully compliant with the PICMG 3.0 R1.0 specifications.

14 slots which can be equipped with ATCA node blades.

Gigabit Ethernet architecture.

Two ShMC shelf manager boards. Each blade is connected to the shelf manager through an Intelligent Platform Management Bus (IPMB).

"five nines" uptime

(99.999%)

The PCI Industrial Computer Manufacturers Group (PICMG) is a consortium of more than 700 companies who collaboratively develop specifications that adapt PCI technology for use in industrial and telecommunications

applications. PICMG specifications include Compact PCI for Euro card, rack mount applications and PCI/ISA

for passive backplane, standard format cards.

Today, with the development of high-rate Internet, the PCI bus reaches its limits in terms of bandwidth for

the implementation of system of switching.

Thats why PICMG has defined a new standard based on a new electromechanical platform.

This new standard called Advanced Telecom Computer Architecture (ATCA) is specified in PICMG 3.x.

One of the major characteristics of this PICMG 3.x standard is an architecture based on gigabit Ethernet

switching.






2.2 General View of the Hardware Architecture

ONEATCA shelf

External Ethernet links (OMC and local terminal)

ONE LIU shelf

Abis & Ater-muxlinks

Working function

Ethernet links

Redundant function

OMCPOMCP

SSWSSW

CCP1

CCP2

CCP N

Spare CCP

TP GSM

TP GSM

MUX 2MUX 1

LIU2LIU1

LIU 16

An ATCA rack can contain two ATCA shelves and 2 LIU shelves.

Each ATCA shelf is paired with a unique LIU shelf.

The number of CCP boards depends on the configuration of the 9130 BSC Evolution.

TP boards manage the transmission part.

CCP boards manage the Telecom part.

OMCP boards manage the O&M part.

One LIU board can connect up to 16 E1 links.

Physical characteristics of the MX rack:

Standard 19" rack (0.6 x 0.6 x 2 m)

Useful height (40 U)

1 PDU with 2-wire power supply

1 or 2 ATCA shelves (height = 13 U each)

1 or 2 LIU shelves (height = 3 U each)

A standard unit is 1U of 44.45 mm.

The same equipment platform is used for BSC and MFS (PCU).

19" rack = 19 inches rack

1 inch = 25 mm






LIU Modules

The 9130 BSC Evolution equipment is composed of 6 types of modules.

Associate each module from the list on the left with the appropriate definition from the list on the right.

LIU

OMCP

MUX Allows exchanges between all the elements of the platform and external IP/Ethernet equipment

Is in charge of call control processing

Is in charge of physical E1 connections

TPGSM

CCP

SSW

Is in charge of managing the whole platform

Is in charge of transmission processing features

Is in charge of multiplexing n E1 links into one Ethernet link






NE1oE Protocol

In the 9130 BSC Evolution, the NE1oE protocol is used between the E1 LIU shelf and the TPGSM module.

The NE1oE protocol consists in transporting n E1 frames embedded into an Ethernet payload to a board assigned by its MAC address.

The NE1oE protocol carries telecom traffic flow: it includes voice and data traffic, telecom signaling (RSL, GSL, SS7) and O&M signaling (OML, Q1, ML-PPP).

CCP1 CCPP

1 Gigabit Ethernet - ATCA Base Interface

O&M + TELECOM

CCPN

SSW W

SSW P

OMCPw

LIU Shelf

External E1 links

pOMCP

pTP

WTP

NE1oE

The different messages from telecom traffic are distributed to different planes (User Plane and Control Plane)

by TPGSM (see the 9130 BSC Evolution IP Architecture chapter).

O&M and Telecom signaling are distributed to the control plane as the BSC internal message flow.

The voice/data traffic is switched then re-encapsulated into Ethernet frames and routed back to the LIU

shelf.






IPMI Bus

The low-level management of the modules at the ATCA shelf is performed by one Shelf Management Module (SMM) via two redundantIPMI Buses (IPMBs).

SMM Functions:

Board powering-up

Temperature Regulation

ATCA boards and other shelf components monitoring and controlling

Inventory information retrieving

Communication with the system manager

Etc.

ShMC

SMM

(backup)

ShMC

SWW

CCP

TPGSM

FAN

tray

OMCP

Systemmanager

IPMB2IPMB1

IPMC

IPMC

IPMC

IPMC

IPMC

SMM

(active)

The Intelligent Platform Management Interface (IPMI) is a specification that defines a set of common interfaces to computer hardware and firmware that is used to monitor system health and manage the system

as the regulation of temperature, voltage and power.

IPMI operates independently from the Operating System, and as defined in the IPMI specification, there are 2

Shelf Management Modules (SMMs) implemented in the architecture of 9130 BSC Evolution: one active and one backup for redundancy reasons.

On the Shelf Management Module, there is one Shelf Management Controller (ShMC) which interrogates each IPMI Controller (IPMC) located in each module using the IPMI protocol. They operate in master-slave mode.

The role of the ShMC consists in sending messages to the system manager in order to supervise all the ATCA

shelves remotely.

The system manager is the highest level of management entity referenced in this specification, responsible for managing one or more systems, each compring one or more shelves.

The system manager is designed to:

watch over the basic health of the system,

report anomalies,

take corrective action when needed.

The remote inventory is a facility which consists in retrieving inventory hardware and firmware of the 9130

BSC Evolution. This facility can be performed locally but also remotely with the OMC-R.

By the way, the OMC-R operator can access the inventory data for maintenance purposes and list the

necessary information to replace a board in case of failure.






2.3 Hardware Description of ATCA Modules

The ATCA shelf is composed of CCP, OMCP, SSW and TPGSM modules. The shelf ensures the power supply of boards and the air cooling inside the rack.

Air inlet

ATCA shelf front view ATCA shelf rear viewATCA shelf right-side view

Fan

This ATCA shelf is based on a 14-slot Dual-Star Middle plane, and is always equipped with:

4 individual fan trays.

4 Power Entry Modules (PEMs) located on the rear side.

2 Shelf Management Controllers (ShMCs) located on the rear side.

2 Personality Cards (PCs) located on the rear side. One of the functions of the PC is the setting of the

geographical address of the ATCA shelf by adjusting 2 rotary switches.

According to the number of TRXs managed by the 9130 BSC Evolution, different configurations are defined:

Conf1 (1 active CCP + 1 stand by CCP) = 200TRXs

Conf2 (2 active CCP + 1 stand by CCP) = 400 TRXs




A module or a board inside the ATCA shelf is composed of one front RIT and optionally one rear RIT.

For all configurations based on ATCA shelf, each slot unused by a board has to be closed by a filler plate with

front panel on the front and rear sides of the shelf.

The ATCA front fillers are used to create the appropriate air flow within the subrack.






ATCA Back Panel

1G Ethernet

Layer 3 Switch

10G Ethernet

Layer 2 Switch

ShMC

TDM

Clock Generator

I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O I/OI/O

Fabric (Dual Star)

Power Distribution

System Management

Update Ports

Base Channel

TDM Clocks

1G Ethernet

Layer 2+ Switch

1G Ethernet

Layer 2 Switch

ShM

PMC

1G Ethernet

L 2 Switch

Pentium M

CG Linux

PMC

PMC

PMC

TDM

Clock Generator

Fans, Thermal Sensors, Power Monitor

SSW1/2OMCP/CCP

PCI

Backplane

ATCA-M100 / SMM

Characteristics:

Base channel: Board communication.

Fabric interface: not used.

Update port: Bus between two colocated boards (for example, TPGSM or SSW).

TDM clock: clock distribution.

Power distribution.

System management: IMPI bus.






SSW Module: Board Description

Characteristics:

GbE Base Interface Switch 16 Base channels (allowing Gigabit Ethernet switching at shelf level)

8 GbE uplinks via RTM (allowing Ethernet external connection) OMC-R/CBC/EAB/NE1o1/NEM Daisy chain, etc.)

Layer 2 switching

Update Channel

IPMI V1.5

Front Ethernet and serial ports (Debug)

Front RIT: JBXSSW Rear RIT: JAXSSW

Not UsedNot Used

Other components:

GbE Fabric Interface Switch (not used):

15 fabric channels.

1 GbE uplink via RTM.

SNMP agent for switch management.






SSW Module: Composition

Gethswitch

SSW module

Backplane interfaces

External interfaces:GbE (NE1oE), CBC, OMC-R, EAB, NEM, etc.

2 external interfaces:

1st ATCA to 2nd ATCA shelves

10 Gb Ethernet

SMM10/100BASE-T

External interfaces

Interconnection with the second SSW

Module - same shelf

ATCAmodule 1

1000BASE-T

ATCAmodule 12

1000BASE-T

IPMI interf

TCP, CCP, OMCP

1000BASE-T

10/100/1000BASE-T

The SSW module has:

12 x 1000BASE-T interfaces in backpanel, compliant with ATCA PICMG 3.0.

2 shelf interfaces (the second Gigabit Ethernet is not used in this case because there are only 2 ATCA

shelves).

At least four 10/100/1000BASE-T interfaces in rear panel for connection of external equipment: E1

Termination Shelf, CBC, etc.

One 1000BASE-T interface for interconnection between pairs of SSW.

One 10/100BASE-T interface (switch port) to link the SMM.

An IPMI interface.

The Gigabit Ethernet switch allows exchanges between all the elements of the platform and external IP/

Ethernet equipment and supports IP layer 3 functions.






SSW Module

Shelf location of the SSW module

Thanks to Annex 7.1, fill in the diagram at the end of this section with the appropriate RIT names that compose the SSW module.






SSW Module: Connection Ports

Thanks to Annex 7.3, associate each external equipment from the middle of the diagram with the appropriate connection port on eachrear RIT.

Rear RIT: JAXSSWRear RIT: JAXSSW

OMC-R

External AlarmBox

CBC

NEM PC

LIU shelf

EAB

E1 External links

1GbE links 48 VDC48 VDC

PEM

PEM

LIU

LIU

LIU

LIU

MUX

MUX

Each Ethernet port from the JAXSSW switch is pre-configured.






TPGSM Module: Board Description

Characteristics:

Multiplexing/demultiplexing of up to 252 E1 links from/to the Gigabit Ethernet interface (NE1oE)

Handling of GSM protocolsHDLC, SS7, Q1 and R/W bits

(ML-)PPP handling and IP routing

Gigabit Ethernet switching

TDM switching

IPMI V1.5

New hardware version of JBXTP3with one cage supporting hot insertion of 4 STM-1 electro/optic modules (multi- or monomode fiber optic transceivers)

(ML-)PPP: IP extraction over Ater

R/W:

R: Ring control

W: alarm byte

The E1 VC-12 module supports the Automatic Protection Switching (APS) function, required for optical line

interface. The APS decision is independent for each STM-1 link.






TPGSM Module: General Architecture of the TPGSM Board

TDM switch (nx8kbps)

HDLC+ SS7

Q1R/Wbits

Controlprocessor

252 xE1 framer

NE1oE

GbE

GbE

GbEswitch

NE1o1

GbEswitch

O&M and Sig.

The TPGSM has the following external interfaces:

Dual Gigabit Ethernet interfaces on the backplane carrying O&M, Telecom and Signaling.

One fast Ethernet interface for test and debug on the front panel.

An IPMI interface on the back panel.

The control processor is a Pentium M at 1.6 GHz.

The GbE links between the TPGSM and the SSW carry 3 flows of information:

O&M: to/from the OMCP (commands, files, etc.).

Signaling: to / from the CCP (No.7, RSL).

Telecom (NE1oE): to / from the MUX, via the SSW (all the channels: OML, RSL, TCH, No.7, etc.).






TPGSM Module: Exercise

According to you, why are there two Gb Ethernet switches in the TPGSM?

----------------------------------------------------------------------------------

The diagram represents another view of the hardware architecture of the 9130 BSC Evolution.

Fill in the blanks in the diagram with the appropriate module names.

The proposed values are given in the commentary page.

SSW2

SSW1

The proposed values are:

CCP1,

CCPn,

TPGSM1,

TPGSM2,

OMCP1,

OMCP2,






TPGSM Module

Shelf location of the TPGSM module

The TPGSM module is composed of one front RIT named JBXTP and one rear RIT which is a filler.

Thanks to Annex 7.1, fill in the diagram at the end of this section with the appropriate RIT names that compose the TPGSM module.






CCP Module: Board Description

Characteristics:

Pentium M, 1.8 GHz

2GB SDRAM

Redundant ATCA Base Interface

2 x USB 2.0 ports at face plate

Carrier Grade Linux Ed. 3.1

IPMI V.1.5 (2 buses)






CCP Module: Functions

The CCP module performs:

GSM and GPRS radio frequency management.

Signaling protocol processing (BSSAP/SCCP/GPRSAP).

Data processing:

radio measurements,

handover measurements,

performance counters.

A CCP board is able to support200 TRXs whatever their type.






CCP Module

Shelf Location of the CCP board

The CCP module is composed of one front RIT named JBXCCP and one rear RIT which is a filler.

Thanks to Annex 7.1, fill in the diagram at the end of this section with the appropriate RIT names that compose the CCP (with a conf2 9130 BSC Evolution) module.






OMCP Module: Board Description

Characteristics:

Pentium M, 1.8 GHz

2GB SDRAM

60GB hard disk drive IDE

Redundant ATCA base interface

2 x USB 2.0 ports at face plate

Carrier Grade Linux Ed. 3.1

IPMI V.1.5






OMCP Module: Functions

The OMCP module performs:

Traffic channel resource management.

O&M control of the BSC functions.

Short Message Service Cell Broadcast.

Transmission function:

Abis and Ater termination points (BTS/BSC/TC).

management of TC equipment.

transmission links.






OMCP Module

Shelf location of the OMCP module

The OMCP module is composed of one front RIT named JBXOMCP and one rear RIT which is a filler.

Thanks to Annex 7.1, fill in the diagram at the end of this section with the appropriate RIT names that compose the OMCP module.





Thanks to Annex 7.1, fill in each slot of the rear and front view of the ATCA shelf with the appropriate RIT names that compose the SSW, TPGSM, CCP (with a conf2 9130 BSC) and OMCP modules.


ATCA Shelf Layout

Front view of the ATCA shelf

1 2 3Slot number 4 145 6 7 8 9 10 11 12 13

Mid plane

Rear view of the ATCA shelf

The SSW module is composed of one front RIT named JBXSSW and on rear RIT named JAXSSW.

The TPGSM module is composed of one front RIT named JBXTP and one rear RIT which is a filler.

The CCP module is composed of one front RIT named JBXCCP and one rear RIT which is a filler.

The OMCP module is composed of one front RIT named JBXOMCP and one rear RIT which is a filler.






2.4 Hardware Description of LIU Modules

The LIU shelf is based on a 21-slot capacity on front side access only, composed of:

2 Power Entry Modules (JBXPEM).

2 MUX boards (JBXMUX).

8 or 16 LIU boards (JBXLIU).

E1 External links

1GbE links48 VDC48 VDC

P

E

M

P

E

M

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

L

I

U

M

U

X

M

U

X

An LIU shelf configuration is always equipped with two (for redundancy) Power Entry Modules (JBXPEM)

installed in the first and last slots of the shelf. They include each DC/DC converter (-48VDC to -12VDC), fuses

and line filter. These two JBXPEMs are installed in slot 1 and 21.

Slot 11 is in the center of shelf and is always free, which allows the access to the shelf address jumpers.

18 slots are free for other types of boards dedicated to BSS applications.

Note: For all configurations based on LIU shelf, each slot unused by a board has to be closed by a filler front

panel.






Global Architecture of the LIU Shelf

One LIU board is able to manage up to 16 E1 links.

One MUX board is able to manage up to 256 E1 links.

Each LIU board is designed to ensure connections of up to 16 physical E1 interfaces (Tx/Rx) and multiplexing and demultiplexing of 16 E1 to/from the two concentration boards.

Each MUX board is designed to ensure multiplexing and demultiplexing of up to 16 E1 streams from the LIU boards (16 E1 for each LIU board) and NE1oE packing/unpacking (TPGSM boards).

The mechanical shelf is able to interconnect 16 LIU boards, with 1 active MUX board + 1 standby MUX board.

The LIU shelf handles 16 x 16 E1s = 256 E1 links max among which only 252 are usable.






LIU Shelf Layout

Thanks to Annex 7.2, fill in each slot of the LIU shelf with the appropriate RIT name, in case of a 400-TRX configuration.

Front view of the LIU shelf

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

PEM

PEM

MUX

MUX






2.5 Power Distribution Unit Cabling

The BSC rack is supplied with 2 redundant DC power supplies of -48 VDC.

ATCA Shelf 1

ATCA Shelf 2

LIU Shelf 1

LIU Shelf 2

PEM

PEM

PEM

PEM

A2

A4

A1

A3

B4

B2

B1

B3

PDU

PEM

PEM

PEM

PEM

PEM

PEM

PEM

PEM

B1 B2 B3 B4 B5A1 A2 A3 A4 A5

The BSC rack is supplied with 2 redundant DC nominal voltages: -48 VDC.

The PDU is in charge of power supply distribution and protection inside the rack.

10 circuit breakers are mounted on the PDU. From left to right, we have switches A1 to A5 and then B1 to B5.

Each one corresponds to one ATCA shelf or LIU shelf and to one distribution branch:

A1 and B1 supply the ATCA shelf No.2.

A2 and B2 supply the LIU shelf No.2.

A3 and B3 supply the ATCA shelf No.1.

A4 and B4 supply the LIU shelf No.1.

A5 and B5 are not used.

Note:

Power cables from the PDU to the shelves (ATCA and/or LIU) are always pre-equipped.

Power supply and signal cables may enter the MX cabinet from the top or the bottom.

Maximum dissipated power per shelf:

ATCA shelf: 2400 W (14x150 processing blades, + cooling).

LIU shelf: 100 W.





2.5 Power Distribution Unit Cabling

ATCA 48V Rack Distribution

JBXPS boards distribute 48V inside the ATCA shelf.

The JBXPS 1 and 2 supply the JAXSMM and JBXFAN boards and all the odd parity slots of the ATCA shelf.

The JBXPS 3 and 4 supply all the even parity slots of the ATCA shelf.




ATCA shelf: 2400 W (14x150W for processing blades, + 300W for cooling).

LIU shelf: 100 W.





5 PDU Description

Power Distribution Unit Cabling [cont.]

ATCA low power distribution:

The low power (3.4V) coming from the redundant JAXSMM supplies all the modules related to all the IPMI modules of each ATCA shelf.




ATCA shelf: 2400 W (14x150 processing blades, + cooling).

LIU shelf: 100 W.





Exercise

How many lines is the 9130 BSC Evolution supplied by?

--------------------------------------------------------

How many PEMs are used to supply the ATCA shelf?

---------------------------------------------------------------





3 9130 BSC Evolution Software Architecture






3.1 Generalities

The 9130 BSC software is composed of 2 software operating with Linux:

9130 BSC application software.

9130 BSC platform software

High Availability Services:Responsible for fault detection, notification and recovery

Control Services:Responsible for hardware and software components management

Application Support Services:Responsible for resource monitoring, time synchronization, miscellaneous real-time services

LINUX Carrier Grade Operating system

A9130 BSC PLATFORM

Adaptation layer

A9130 BSC APPLICATION

ApplicationSupportServices

High AvailabilityServices

ControlServices

The 9130 BSC Evolution software is composed of:

One 9130 BSC application software which supports telecommunication function of the 9130 BSC Evolution.

One 9130 BSC platform software which is in charge of processes management, hardware management, software management, initialization and a few basic services like traces or date synchronization.

High Availability Services

Through a high-availability service interface, the PMS and HWM subsystems receive service calls from, and send eventnotifications to the applications. The Self-Reliant middleware product implements the fault detection and low-levelcomponent control.

PMS: The PMS subsystem manages processes at platform level.

HMS: Low-level component control.

Application Support Services

This layer covers aspects related to the usability and manageability of the platform and application components:

logs and traces services.

post mortem and live debugging.

Network Time Protocol (NTP).

Simple Network Management Protocol (SNMP).

Control Services

The aim of control services is the automation of MxPF software and hardware management, minimizing manualinterventions and associated risks.

Concerning the software (SWM), the main objective is the management of new software releases and correction patches.Importance is placed on integrating new software into the MxPF without causing unnecessary service disruptions.

Concerning the hardware (HWM), the best effort is focused on giving assistance on fault detection, isolation and recoveryand minimizing the outage in case of replacement of a Field Replaceable Unit. Thanks to HPI support provided by the Self-Reliant and EndurX software, the application may control (Reset, Power on or off, blinks the Led), monitor (Insertion, Removal and failure notifications) and audit (alarms, states).






3.2 9130 BSC Evolution Software Organization

In the 9130 BSC Evolution, the basic element of software is called process.

DefinitionProcess

Name

Process responsible for coordinating and supervising all local SUPIt is a global manager process that runs on OMCP boards in active/standby mode

GSUP

Process responsible for the management of all the processes at board levelOne SUP process per board

SUP

Process that allows the communication between A9130 BSC application and A9130 platform services

CPI

Process that allows the internal communication among the application processes

CMW

Process responsible for one telecommunication function handling

VCE

ATCA board

PLATFORM

APPLICATION

TCP/IP

VCEn

VCE1VCE2

CMW

SUP

CPI

GSUP

The CMW process allows the communication of all the application processes located on the board or on

another board of the same shelf.

When one application service requests a platform service, the CMW sends messages to the CPI. The CPI calls

platform services so that they provide the requested services. Once the service is treated, the CPI process

sends back the corresponding messages.

The platform services that go through CPI are:

Process management: starting or stopping a process, etc.

Hardware management: remote inventory, board commands (reset, power off/on), board supervision

(insertion, removal, fault), etc.

Software management: download, pre-download, activation, etc.

Communication: internal and external files transfer, supervision of IP internal and external link, etc.

Basic services: trace log, date and time synchronization, etc.

NE1oE agent management.






BSC Application Software

In the 9130 BSC Evolution, a VCE is defined according to the functions it performs.

TSC functionsV-TSC

No.7 terminationSLH

SMS-CB, Logical and Hardware Configuration ManagementV-oCPR

Database managementV-sCPR

External communication management with the CBC and the OMC-REIM-R

TCP connection management with the 9130 BSC terminal and NEMEIM-L

Traffic Channel Resource managementV-DTCtchrm

Signaling protocol processing (BSSAP/SCCP/GPRSAP)V-DTC

GSM and GPRS radio frequency managementV-TCU

VCE FunctionsVCE Names






BSC Application Software [cont.]

One ATCA module is able to support more than one VCE. A CP_LOG is a group of VCE mapped on one ATCA module.

In order to allow the communication between VCEs of one board or between VCEs on different boards, it is necessary to have a routing table which contains the address of each VCE. This routing table is located in each CMW.

IP@-nniVCEn

IP@-3132VCE3

IP@-2121VCE2

IP@-2121VCE1

Ip-@CP_HWCP-LOGProc_name

Fields of the Routing Table:

Proc_ name: is the identification of the process related to intra- or inter-board communication. It is the logical identification of a VCE.

CP-LOG: is the logical aspect with a group of VCEs mapped.

The mapping between VCEs and CP-LOG is determined according to the BSC configuration type.

CP-HW: is the physical CP which represents CCP, OMCP or TPGSM board.

IP-@: is the IP address of the board.

For example:

TCUs have the same CP-LOG number.

DTCs have the same CP-LOG number.






BSC Application Software [cont.]

The diagram below shows the path followed by VCE3 to communicatewith VCE6.

OMCPCCP / TPGSM

TCP/IP

VCE4 VCE5

VCE6 CMW

VCE1

CMW

VCE2 VCE3

CPI

SUP

CPI

SUPGSUP






Process Mapping on OMCP Board

According to the processes mentioned in the commentary page and to the functions of the boards seen in the previous chapter, fill in the diagram below with the appropriate VCE names.The proposed values are given in the commentary page.

CPI

GSUPSUP

CMW

NE1oEAgent

FTPserver

DHCPserver

Init/SW

HWmgt


EIM-L,

EIM-R,

SLH,

V-DTC,

V-DTC (TCH-RM),

V-SCPR,

V-TCU,

V-TSC,

V-OCPR.

The OMCP board is used to manage the O&M function of both platform services and application services. But

according to some specific requirements of 9130 BSC application, some processes not used for O&M function

but for telecom function are also mapped on the OMCP board.

CPI, NE1oE agent, HW management, GSUP/SUP, init/SW and FTP server are the platform service processes. All

the services are used for O&M management of the Mx platform. The service is covering Mx hardware

management, Mx platform process management, Mx platform software management, Mx platform installation

and initialization, NE1oE traffic O&M management.






Process Mapping on CCP Board

According to the processes mentioned in the commentary page and to the functions of the boards seen in the previous chapter, fill in the diagram below with the appropriate VCE names.The proposed values are given in the commentary page.

CPI

GSUPInit/SW

CMW


EIM-L,

EIM-R,

SLH,

V-DTC,

V-DTC (TCH-RM),

V-SCPR,

V-TCU,

V-TSC,

V-OCPR.

The CCP board is used to handle the 9130 BSC Evolution telecom functions.

The CCP board is passively managed by a platform service in the OMCP, so there is less platform service

running on this board. Only the SUP for process management and init&SW for software loading are mapped on

this board.






Process Mapping on TPGSM Board

According to the processes mentioned in the commentary page and to the functions of the boards seen in the previous chapter, fill in the diagram below with the appropriate VCE name.The proposed values are given in the commentary page.

CMW

CPI

SUPInit/SW

Qmuxhandler

TDM handler

HDLCMLPPPhandler

HDLCLAPD

handler

R/W bitsAlarm octet

handler

TP-Main


EIM-L,

EIM-R,

SLH,

V-DTC,

V-DTC (TCH-RM),

V-SCPR,

V-TCU,

V-TSC,

V-OCPR.

TPGSM is the centralized board handling the lower layer of GSM signaling protocol and the switching function

in the 9130 BSC Evolution.

TP-Main is the high centralized process in the 9130 BSC Evolution. It covers HDLC, Qmux, R/W bit handling,

ML-PPP switching and the O&M function.






Communication Process between VCEs

Illustration of communication process between VCEs (case of HDLC RSL signaling processing).

CCPTPGSM

TCP/IPNE1o1

VDTC

NE1oEAgent

TDM handler

HDLCLAPD

handlerTP-Main CPI

R/W bitsAlarm octet

handler

Qmuxhandler

SUP

CPI SUP

SLH

CMW CMW

VTCUVTCUVTCUVTCU

VTC1

VDTCU

VDTCU

VDTCU

VDTCU

VDTC1






3.3 BSS Software Organization

The BSS software is composed of the Mx BSC software and BTS software.

The BSS software consists of a collection of files, representing the programs, patches and data needed for a particular and complete load of every module in the BSS, BSC or BTS.

The Master Files (MFs) concept is used in the BSS environment to define the software context of the complete BSS. An MF identifies clearly and unambiguously the set of files which together represent the software package and the database needed for the whole BSS, BSC or BTS types.

The BSS software is also called build.






MF Concept

Bootroot File

n

BSS Master File

Master Files

Application Files

BSS-MF

BSC-SW-MF BSC-DB-MFBSS-Map File BTS-SW-MF BTS-DB-MF

n

Application File1

DLS

MX-BSC conf

TC_CPF

n

Application File1 n

OMU-CPF File1

MX Platform-MF

Platform File1

m

MX-BSC conf is a file describing the configuration of the 9130 BSC Evolution.

There are more than one BTS-SW-MF depending on the generation of the BTS.






MF Organization

BSS Master File:

This file for a given BSS and a specific SW version identifies the BSC SW Master File, BSC DB Master File, BSS Mapping File, BTS DB Master File and the list of needed BTS SW Master Files.

MX platform Master File:

This file contains the list of all Mx platform files. It is a simplified MF. It just gives the MxPF version.

BSC SW Master File:

This file references all application files that correspond to BSC software application.

BSC DB Master File:

This file for a given BSC SW version identifies the BSS Database file (DLS) and the CPF files for BSC and TC. The DLS gives the logical configuration and hardware configuration of the BSS.






MF Organization [cont.]

BTS DB Master File:

This file identifies all the OMU-CPF files for the BTSs. The OMU-CPF file defines the HW for each type of BTS.

BTS SW Master File:

This file for a given BTS SW gives the code files (but not the OMU-CPFs) associated to that version. Because the name part of the BTS SW Master File does not identify the BTS, it is possible to assign BTS SW Master File to more than one BTS and consequently there are less BTS SWMaster Files in the BSS Master File than there are BTSs.

BSS Map File:

This file links each BTS index (corresponding to the declared BTSs in the BSS) to one BTS-SW-Master File and one OMU-CPF identified in the BTS-DB-MSF.






File Naming Convention

The general format of a loadable file name is AAAAAAAA.BBC.

AAAAAAAA is the main part. It comprises a string of 8 charactersbetween [ A .. Z ] and / or [ 0 .. 9 ] and / or [ - ].

BBC is the extension part which has 3 characters, where:

BB is the file version number. The allowed range of values is between [ 00 .. 99 ].

C is the sub-version character. Only one character is allowed between [ A .. Z ].






File Naming Convention [cont.]






File Numbering Convention

The file number is an internal BSC reference stored in the last field of the file descriptor.

The following ranges of file numbers are allowed, depending on the sub-system involved:

BSC files:

Most of the files have four-digit numbers, where the first digit indicates the release. E.g., the BSS Master File for the various releases is:

2100: release B9

3100: release B10

BTS files: for BTS files, the allowed range for file numbers is [x700..x999].






File Numbering Convention [cont.]

BSS master file ML3MAW01.01A 3100

BSC- SW Master file BSXMAW30.30.R 3101

BSC-DB Master file ML3LAW01.01A 3102

DLS ML3DAW01.01A 3280

BTS-SW Master file BM1SAWD7.07D 3112

BTS-DB Master file ML3CAW01.01A 3180

BSS Mapfile ML3XAW01.01A 3182

MxPF Master file MXPFAA03.19D 3190





Exercise

Can you mention at least 3 processes from:

the 9130 BSC platform software?

the 9130 BSC application software?

What is a master file?

Is there always the same number of BTS SW Master Files as there are BTSs?

What is an OMU-CPF file?

How to identify BSS files?





4 9130 BSC Evolution IP Architecture






4.1 9130 BSC Evolution Traffic Flows

The 9130 BSC Evolution manages 3 types of traffic using the IP protocol: telecom traffic. Internal traffic. External traffic.

OMCP

OMC-R/CBC router

LIU shelf

TPGSMOMCP

SSW

SSW

TPGCCP1CCPn

External E1 links





4 9130 BSC Evolution IP architecture

4.1 9130 BSC Evolution Traffic Flows [cont.]

Due to the number of flows implemented in the 9130 BSC Evolution, VLAN concept is implemented.

A Virtual Local Area Network is a logical sub-network defined on the same physical network, by assigning the various ports of the switchesadministrable in the various sub-networks.

2 kinds of IP addresses are used within the 9130 BSC Evolution:

Internal IP addresses

External IP addresses

A VLAN is a way to distinguish different flows of information at MAC layer. A tag is assigned to each VLAN and

is used for routing in the Ethernet network.

The principle of VLAN is to have more than one virtual network on one ethernet network. The routing of the

Ethernet frame inside a switch is performed thanks to an identification called tag. Each port of an Ethernet

switch is configured to change the value of a tag.

Internal Traffic (VLAN 1)

This is the default VLAN also called No Tag/ untagged VLAN or VLAN tag 1. It is used for internal

communication. The subnets 172.16.0.0/16, 172.17.0.0/16, 172.18.0.0/16 are assigned on this VLAN.

Telecom Traffic (VLANs 3 and 4)

These two VLANs ensure NE1oE Ethernet communications between the MUX boards of the LIU shelf and TPGSM

NE1oE component. These two VLANs are the VLANs tag 3 and tag 4.

External Traffic (VLANs 22 and 23)

These two VLANs are used for external communications between the Mx BSC, the Mx MFS and can be accessed

from the exterior: OMC-R, CBC, etc. The external VLANs are composed of VLAN tag 22 on the SSW1 and VLAN

tag 23 on the SSW2.

For more information about VLANs inside the 9130 BSC Evolution, consult the Annex.






4.2 Internal IP Addresses of the 9130 BSC Evolution

In the 9130 BSC Evolution, there are two Ethernet networks:

SMM and MUX have access to only one Ethernet network.

TP, CCP and OMCP have access to both Ethernet networks.

Physical @: 172.17

Physical @: 172.18

Logical @: 172.16TP1 TP2 CCP 4 CCP 2 CCP 3

SMM 2

SMM 1 MUX 1

MUX 2

OMCP 1 OMCP 2

Virtual @:Act: 172.16.33.1Stb: 172.16.34.1

CCP 1

SSW 2

SSW 1

3 types of addresses are defined:

physical,

logical,

virtual.

The Ethernet interface from ATCA boards connected to SSW1 board is called ETH0.

The Ethernet interface from ATCA boards connected to SSW2 board is called ETH1.





4.2 Internal IP Addresses in the 9130 BSC Evolution

Types of Internal IP Addresses

The physical IP address is the board IP address on one Ethernet interface:

Physical IP SSW1 plane: 172.17. . (172.17.2.70)

Physical IP SSW2 plane: 172.18. . (172.17.2.80)

The logical board IP address is the IP address used to communicate with a board independently of the Ethernet port used (logical board IP address: 172.16. . ).

The virtual IP OMCP is the IP address used to communicate with the active or the standby board:

Virtual IP address (active OMCP board): 172.16.33.1

Virtual IP address (standby OMCP board): 172.16.34.1

An internal IP address is an IP address solely used internally to the MxPF and used for inter-boardcommunication.

An internal IP address can be:

a physical IP address SSW1: board IP address on Ethernet interface ETH0 plugged on the switch 1.

a physical IP address SSW2: board IP address on Ethernet interface ETH1 plugged on the switch 2.

a logical board IP address: IP address used to communicate with a board independently of the Ethernet port used (ETH0 or ETH1). It can be mapped either to the "Physical IP address SSW1" or to the "Physical IP

address SSW2".

a virtual IP active: IP address used to communicate with the active board. It is mapped on the active Ethernet port of the active board (4 choices).

a virtual IP standby: IP address used to communicate with the standby board. Used for OMCP. It is mappedon the active Ethernet port of the standby board (4 choices).

a virtual IP SSW1: IP address used by Ne1oE to communicate with the OMCP active board. It is mapped on the active SSW1 Ethernet port of the active OMCP board (2 choices).

a virtual IP SSW2: IP address used by Ne1oE to communicate with the OMCP active board. It is mapped on the active SSW2 Ethernet port of the active OMCP board (2 choices).

an external IP address: IP address that is visible from the external world and used to access particularboard/application in the Mx BSC.





4.2 Internal IP Addresses in the 9130 BSC Evolution

Types of Internal IP Addresses

ATCA shelf physical and logical slots.

Front view of the ATCA shelf with a 1000-TRX configuration BSC

Physical slot

Logical slot

1

13

2

11

3

9

4

7

5

5

6

3

7

1

8

2

9

4

10

6

11

8

12

10

13

12

14

14

JBXTP

JBXTP

JBXCCP

JBXCCP

JBXCCP

JBXOMCP

JBXSSW

JBXSSW

JBXOMCP

JBXCCP

JBXCCP

JBXCCP

FILLER

FILLER

Only physical slots are written and so visible on the ATCA shelf.





Exercise

An operator suspects an Ethernet link failure on the board which is inserted in the physical slot numbered 4 of the first ATCA shelf.

What can you suggest him to do once he is connected to the OMCP board with his local terminal?






4.3 External IP Addresses of the 9130 BSC Evolution

The OMC-R communicates with the 9130 BSC Evolution using the IP protocol. The network access can be done either:

Via ethernet: SSW connected to one or 2 external routers, or

Via the Ater interface: usage of n TSs at 64 Kb/s on atermuxes with ML-PPP.

Fill in the diagram below with the names of the modules on which the links are connected.

BSC terminal / NEM

OMC-R

IP/X.25router

IP over Ater

IP on Ethernet

MSCTC

A9130BSC

IP Network

IP router/ML-PPP

EAB

2

1

1

2

The 2 OMCP boards from the 9130 BSC Evolution are responsible for supervision and configuration parts of the BSS. The active OMCP provides the OMC-R with the logical interface.

The OMC-R can supervise and configure the 9130 BSC Evolution in 2 ways:

Direct IP network.

IP over Ater.

In case of IP over Ater, MultiLink PPP (ML-PPP) is used in order to split, recombine and sequence datagrams across multiple logical data links.

The O&M traffic coming from 9130 BSC Evolution is spread over 2 to 16 E1 timeslots at 64Kbit/s, but the recommended value is 4 E1 timeslots (256 Kbit/s).

The last timeslots from Ater are routed by MSC on the PCM link(s) between the MSC and the Cisco router. Each timeslot from PCM link(s) is defined as virtual serial interface in the Cisco router by its E1 controller. All these virtual serial interfaces are integrated, by the Cisco router, in the MultiLink PPP interface.

The extraction can be done on MSC or TC side.

External alarms are available and managed on the 9130 BSC Evolution through an External Alarms Box (EAB).

The alarms are:

routed through an external Ethernet link IP connection to the OMC-R via O&M links,

transparent for the 9130 BSC application.

The External Alarms Box provides external alarm inputs which can be adapted to the requirements of each customer. Typically, they are used for main power supply, rectifiers, batteries, air conditioning, intrusion etc.

The SMS-CB service uses the X.25 protocol, according to 3GPP definition.

2 possibilities are offered to the customer:

Communication between CBC and 9130 BSC Evolution over Ater on TC or MSC site (use of ML-PPP).

Communication between CBC and 9130 BSC Evolution over IP network.






External Subnet of the 9130 BSC Evolution

The 9130 BSC Evolution is able to support different LANs configuration:

Two-LAN solution via a CISCO router: One external subnet called A subnet

2 local subnets called B and C subnets

Usage of RIP protocol

One-LAN solution via a CISCO router: Only one external subnet called A

No usage of RIP protocol, static routing is used

The ONE LAN solution is not possible over Ater

2 different LANs configuration are available on the 9130 BSC Evolution.

Historically, Alcatel-Lucent implemented first the Two-LAN solution with RIP protocol.

Standard RIP is used to perform the path failure detection and routes update for the O&M flows.

This solution implies to define 3 different subnets (A,B and C). B and C are internal and only the subnet A is

visible from the IP Network. Thats why it is called 2 LANs

One drawback of RIP protocol can be the reaction time for updating routing tables when a failure (SSW, link,

or Router problem) appears. This is not a problem from the O&M point of view, but with the introduction of

some Telecom facilities based on IP in the next release (such as A Flex), RIP solution protocol will be not able

to guarantee the continuity of the telecom service.

Thats why Alcatel-Lucent proposes another solution based on the one-LAN solution .






External Subnet of the 9130 BSC Evolution

2-LAN

Solut

ion

IP Network

OMC-R

Engineering rules for A subnet:A1 for OMCP1 AIP addressA2 for OMCP2 AIP address + 1A3 for Active OMCP AIP address + 2

A6 for Alarm box AIP address + 5

Subnet A

Subnet B Subnet C

B1

B2

B6 C6

C1

C2

AlarmBox

SSW1 SSW2OMCP2

OMCP1

Active board

Standby board

The above diagram represents the 9130 BSC Evolution communicating via an Ethernet link with the OMC-R (the scenario will be the same in case of IP over Ater interface (ML-PPP on TPGSM active board)).

The use of the RIP V2 protocol on OMCP, TPGSM boards and on an external router provides a way to automatically update the routing table on these stations each time a change occurs (link, switch failure, OMCP switchover, etc.)

The subnet A is visible everywhere in the IP network.

The OMC-R uses the A3 IP address in order to communicate with the active OMCP of the 9130 BSC Evolution. Once the router receives A3 IP, it converts this AIP into B or into CIP address according to the active couple switch/OMCP board.

The alarm box may be connected to the SSW1 of the 9130 BSC Evolution or directly to a LAN.

The local subnets B and C are visible only by the routers in entrance of the IP network.

For the definition of the subnet B, the necessary O&M parameters are set in the 9130 BSC Evolution in the following way:

B1: OMCP 1 connected to SSW1 = BIP address

B2: OMCP 2 connected to SSW1 = BIP address +1

B6: external router connected to SSW1 = BIP address + 5

For the definition of the subnet C, the necessary O&M parameters are set in the 9130 BSC Evolution in the following way:

C1: OMCP 1 connected to SSW2 = BIP address

C2: OMCP 2 connected to SSW2 = BIP address +1

C6: external router connected to SSW2 = BIP address + 5

In case of MFS colocated with the BSC, a supplementary AIP address is assignable to the active OMCP from the MFS. This address is named A4 (AIP address + 3) and is mapped on the active ethernet from the active OMCP.






External Subnet of the 9130 BSC Evolution [cont.]

1-LAN

Solut

ion

IP Network

OMC-R

Subnet A

AlarmBox

SSW1 SSW2OMCP2

OMCP1

Active board

Standby board

Engineering rules for A subnet:A1 for OMCP1 AIP addressA2 for OMCP2 AIP address + 1A3 for Active OMCP AIP address + 2

A6 for Alarm box AIP address + 5

In a one-LAN solution, it is possible to get 2 routers instead of one, as represented above. The advantage of 2 routers is to provide a redundancy router with the implementation of the VRRP or HSRP protocol.

Virtual Router Redundancy Protocol (VRRP) specifies an election protocol that dynamically assignsresponsibility for a virtual router (a Virtual router composed of 2 physical routers). VRRP controls the IP addresses associated with a virtual router.

Alcatel-Lucent recommends to connect the external alarm box directly to the router, even if connection atBSC switch remains possible.

In the one-LAN solution, the address of the router has only one address which is unique. By default, this address is A5 (AIP address + 4).

Router access or BSC switch failure scenario:

Detected through a reachability test on both switch sides (active OMCP).

Test based on ARP echo request.

In case of failure of active switch side, the BSC swaps its addresses to the other switch side.

Gratuitous ARP sent by the BSC, triggering the ARP cache update on router side.

OMCP switchover scenario:

Gratuitous ARP sent by newly active OMCP.

Same switch as before OMCP switchover remains active.

In case of MFS colocated with the BSC, a supplementary AIP address is assignable to the active OMCP from the MFS. This address is named A4 (AIP address + 3) and is mapped on the active ethernet from the active OMCP.






IP Addresses in Subnets A/B/C

Let's assume SSW2 and OMCP1 are active.

Fill in the diagram below with the IP address of Subnets A, B and C.The proposed values are given in the commentary page.

(w)

SSW1

SSW2 (W)OMCP1

OMCP2

OMC-R


A1, A2, A3.

B1, B2, B6.

C1, C2, C6.





5 9130 BSC Evolution Defense Mechanism






5.1 Redundancy Schemes

The architecture of the 9130 BSC Evolution enables an excellent

availability and reliability of the functions.

2 redundancy schemes are implemented: N+1 and 1+1.

Fill in the tables below with the appropriate redundancy scheme.

Defense mechanism in the ATCA shelf Defense mechanism in the LIU shelf

BoardRedundancy

scheme

CCP

OMCP

TP-GSM

SSW

BoardRedundancy

scheme

LIU

MUX

PEM






5.2 Switchover Scenarios

Switchover scenario for 1+1 (duplication) redundancy scheme.

OMCP1

CCP1

Working function

Redundant function

CCP2

CCPN

OMCP2

TP1

TP2

SSW1 SSW2






5.2 Switchover Scenarios [cont.]

Switchover scenario for N+1 redundancy scheme.

TP2

Working function

Redundant function

CCP1

CCP2

CCPN

OMCP2

TP1

SSW1

OMCP1SSW2

In the N+1 scheme, the redundant CCP board takes over the processing and capacity of the failed CCP with a

minimum service interruption.





6 9130 BSC Evolution Performance






6.1 9130 BSC Evolution Standalone Configuration

The 9130 BSC Evolution standalone configuration consists of one rack dedicated to one BSC.

Rules: A single BSC is always installed with:

Shelf 3 dedicated to the ATCA shelf.

Shelf 1 dedicated to the LIU shelf.

BSC standalone

PDU

Shelf 4none

ATCA Shelf 3(BSC)

LIU Shelf 2none

LIU Shelf 1(BSC)

Rules are applied for shelf positions regarding weight, security stability constraints and logistics benefit.

As for the BSC, there is also an MFS standalone configuration which is called:

Either "MFS 9 GP standalone". The cabinet is composed of 1 ATCA shelf (shelf 3) and 1 LIU shelf (shelf 1),

Or "MFS 21 GP standalone". The cabinet is composed of 2 ATCA shelves (shelves 3 and 4) and one LIU shelf

(shelf 1). The whole cabinet is seen as one single network element.






6.2 9130 BSC Evolution Rack-Shared Configuration

The 9130 BSC Evolution rack-shared configuration consists of one rack shared between 2 BSCs or between one MFS and one BSC.

BSC-MFS rack-shared2 x BSC rack-shared BSC-MFS rack-shared

LIU Shelf 1(MFS)

ATCA Shelf 3(MFS)

PDU

LIU Shelf 2(BSC)

ATCA Shelf 4(BSC)

LIU Shelf 1(BSC)

ATCA Shelf 3(BSC)

LIU Shelf 2(MFS)

ATCA Shelf 4(MFS)

LIU Shelf 1(BSC1)

ATCA Shelf 3(BSC1)

LIU Shelf 2(BSC2)

ATCA Shelf 4(BSC2)

PDUPDU

Rules are applied for shelf positions regarding weight, security stability constraints and logistics benefit.

The "BSC rack-shared" configuration which is composed of two shelves is also called a "BSC double capacity"

because of two independent network elements.






6.3 Capacity: BSC Capacities in Terms of Boards

Three BSC capacities are defined depending on the number of TRXs.

Equipment BSC capacity

200 TRX 400 TRX 600 TRX 800 TRX 1000 TRX

ATCA shelf 1

CCP 1 2 3 4 5

Spare CCP 1

TP-GSM 2

OMCP 2

SSW 2

LIU Shelf 1

MUX 2

LIU Shelf 8 16

The quantity of TPGSM, OMCP, SSW and MUX boards has to be considered as 1 active + 1 standby for

redundancy purposes in the shelf.






6.4 Capacity: Capacity and Dimensioning for E1 Links

The 9130 BSC Evolution is able to process up to 4500 erlangs.

Equipment BSC capacity

200 TRX 400 TRX 600 TRX 800 TRX 1000 TRX

Max number of BTS 150 255 255 255 255

Max number of cells 200 400 500 500 500

Total number of E1's 112 128 224 240 252

Number of Abis 96 96 176 176 176

Number of Atermux CS 10 20 30 40 48

Number of Atermux PS 6 12 18 24 28

Number of Erlangs 900 1800 2700 3600 4500

traffic Ater PS (Mbps 12 24 36 53 67






6.5 Capacity: Abis and Atermux Allocation on LIU Boards

Abis and Atermux allocation

bsc description (3fl12479abaawbzza4)

Documents

bsc evolution performance

bsc evolution vlan

bsc evolution ip architecture

bsc capacities

bsc evolution traffic

bsc standalone configuration

alcatel lucent

hardware architecture