Flexi BSC Gemini

FLEXI BSC & GEMINI
Flexi BSC in Brief
Flexi BSC in Brief

Flexi BSC Product Highlights
Very high circuit-switched capacity for voice
Up to 18,000 Erlangs
Very high packet data capacity for EDGE evolution
Up to 30,720 channels
Very high footprint efficiency
Low site-space costs for capacity of 3,000 TRXs and
3,000 BTS sectors and sites in one cabinet
Excellent power consumption efficiency
Market-leading power consumption per capacity
Support for most cost-efficient transport options
IP/Ethernet available for all interfaces
Full flexibility to configure preferred or mixed integrated
transmission type (E1/T1, STM-1/OC-3, IP/Ethernet)
Scalability
Capacity and transmission can be flexibly configured in
small resolution steps to support pay-as-you-grow
approach
High reliability
Redundancy, fault management and overload protection
on top of very high availability design
Flexi BSC in Brief

Flexi BSC comparison to current BSC3i
Maximum capacity
BSC3i2000
Flexi BSC
Racks
1-2 racks
1 rack
TRXs
2,000
3,000
BTS cells
2,000
3,000
BTS sites
2,000
3,000
Erlangs
12,000
18,000
Packet Data channels

(16 kbit/s Abis)
25,600
30,720
PCM/SDH transport lines
800 E1/T1
16 + 16 STM-1/OC-3
(mixed/simultaneous use possible)
800 E1/T1
16 + 16 STM-1/OC-3
(mixed/simultaneous use
possible)
Integrated IP transmission
12 + 12 Gigabit Ethernet connections for

all interfaces (RG10)
12 + 12 Gigabit Ethernet
connections for all
interfaces
SS7 Signalling
IP based SS7 (SIGTRAN) links

64/128/256/512kbit/s, 1Mbit/s or
2Mbit/s links
IP based SS7
(SIGTRAN) links
64/128/256/512kbit/s,
1Mbit/s or 2Mbit/s links
HW upgrade path to Flexi BSC
Supported from all BSC3i configurations

(BSC3i 660/1000/2000)
Flexi BSC in Brief
Third generation
General Evolution of BSC Products

Second generation
First generation
BSC3i
BSC2i
BSCE
First BSC generation
Up to 128 TRX with 2
high racks
1991
BSC2
2nd BSC generation
Large Capacity SW
up to 256 TRX (S6)
with 2 racks
1995
High Capacity BSC

along with smooth
upgrade path (S8)
Capacity increase up
to 512 TRX
with 2 racks
1999
660 TRXs with 1-cabinet

BSC3i 660 configuration (S10.5)
1000 TRX with 1-cabinet and up to
2000 TRXs with 2 cabinets by BSC3i
1000/2000 (S12 & S13)
3000 TRX with 1-cabinet by Flexi
BSC (BSC3i 3000) (S14)
Complete solution for future CS and
PS traffic handling capacity
requirements with IP connectivity
2002
2007
2009
Flexi BSC in Brief

Flexicapacity
BSC increases
CS Traffic handling
usable
capacity
PS Traffic
handling capacity
1.2 x
BSCE
128 TRX
BSC2E
256 TRX
BSC2i
BSC3i 660 BSC3i 2000 Flexi BSC
512 TRX
660 TRX
2000 TRX 3000 TRX
number of Abis
channel @16kbPs
PS TCH
FLEXI BSC (BSC3i 3000)
Not
supportedin S14
BSC3i 2000
BSC3i 660
BSC2i
Not
supportedin S14
5x
BSC3i
4.5 x
BSC3i 2000 (11880Erl)
6x
3000)
(BSC3i Erl
BSC (11880
BSC3i
FLEXI2000
) (18000 Erl)
1.5 x
BSCE
2048
BSC2E
4096
BSC2i
BSC3i 660 BSC3i 2000 Flexi BSC
4096
6144
25600
30720
(8x1x1x256)
(8x1x2x256) (8x1x2x256) (6x2x2x256) (10x5x2x256) (6x5x1x1024)
# BCSUs/BSC x # PCU pius/BCSU x #

logical PCUs/PCU piu x #max Abis
channel @16Kbps for PS TCH
Flexi BSC product family

The Flexi BSC product family consists of:
0
BSC3i 660
BSC3i 1000
BSC3i 2000
Flexi BSC pcu2-e 1024 660pcu2-d256
Flexi BSC Hardware and Functionality

Cabinet Mechanical
2000
mm
Fast installation and very easy expansion

Simple mechanical structure
Relatively few components
Internal cabling ready
No special site requirements

No need for raised floor
Compact size reduces site space needs
Weight is approx. 350 kg, floor load below 500 kg/m2
Simplified cabling with compact design
Overhead cable and raised-floor options
Dimensioned according to international standards
and recommendations
Designed on IEC, EN, ETSI, UL and Telcordia
Enhanced earthquake and fire resistance
Advanced features in terms of safety, protection
against interference, stability and durability
Welded frame structure
Low power consumption
M98
600 mm
900mm

Computer Units (1/4)
MCMU
Flexi BSC cabinet
BCSU
MCMU
BCSU
MCMU
In the Flexi BSC, the call

control functions are
executed by microcomputers, called
Call Control Computers
OMU
OMU
BCSU
BCSU BCSU
BCSU
BCSU BCSU
2000 x 900 x 600 cabinet (HxWxD)

Computer Units MCMU (Marker and Cellular
Management Unit) (2/4)
CP816-AC
SWPRO-C
ESB24-A
PSC6-AB
MCMU
Plug-in units
MCMU
MCMU
The Marker and Cellular Management

Unit (MCMU) controls and supervises the
Bit Group Switch and performs the
hunting, connecting and releasing of the
switching network circuits.
The cellular management functions of
the MCMU are responsible for cells and
radio channels that are controlled by the
BSC. The MCMU reserves and keeps track
of the radio resources requested by the
MSC and the handover procedures of the
BSC.
MCMU also manages the configuration of
the cellular network.
Redundancy 2N

New SWPRO-C
Flexi BSC
PDFU
The SWPRO-C plug-in unit is used as a control
GTIC
ETC
ETC
GSW2KB
GTIC
ETC
ETC
BCSU 4
SWPRO-C
OMU
BCSU 2
BCSU 3
FTRB
LANU
FTRB
MCMU
BCSU 1
LANU
BCSU
FTRB
MCMU
FTRB
BCSU 5
BCSU 6
CLS
GSW2KB
CLS
unit for a bit-oriented group switch (GSWB).

The GSWB control unit functionality provides
two control bus interfaces through the
backplane connection.
Processor Intel Celeron 1.0 GHz, 400 MHz with
SDRAM: 1 GB (with x8 memory configuration)
SWPRO-C allows to control higher amount of
connections and generates less load to the
MCMU CPU in comparison to SWCOP-A
PDFU
BSC3i 1000 & 2000 Hardware and Functionality

ESB24 Ethernet Switch
Used in Flexi BSC first delivery for EMB and IP LAN switching
In front panel there are:
4 SFP Ethernet ports (ETH1,2 & ETH23,24) 1000Base-T ports in Gigabit mode
1 MGT ports (RJ45) serial port for switch menagement
1 SER1 ports (RJ45) console connector used for initial configuration
In back panel there are:
20 Full-duplex 10/100/1000Base T/TX ethernet Ports
ESB24 unit located in MCMU is used for EMB switching
Connects all CPUs
ESB24 units located in LANU are used for IP LAN Switching
Connects together all CPUs and all PCUs

Computer Units BCSU (BSC SIgnalling Unit) (3/4)
The BSC Signalling Unit (BCSU) performs those
BSC functions that are highly dependent on the
volume of traffic.
Consists of two parts, which correspond to the A
and Abis interfaces
Packet Control Units (PCUs) are housed in the
same cartridge.
The A interface part of the BCSU is responsible for
performing all message handling and processing
functions of the signalling channels connected to
it
BCSU
The Abis interface part of the BCSU controls the

air interface channels associated with transceivers
(TRXs) and Abis signalling channels.
The handover and power control algorithms
reside in this functional unit.
Redundancy N + 1
Plug-in units
CP816-AC
AS7-D
PCU2-E
PSC6-D
Performing the distributed functions of the

Message Transfer Part (MTP) and the Signalling
Connection Control Part (SCCP) of SS7
Controlling the mobile and base station signalling
(Base Station Subsystem Application Part, BSSAP)
BCSU
BCSU BCSU
BCSU
BCSU BCSU

New AS7-D (1/2)
Flexi BSC
PDFU
- The AS7 plug-in unit function as a general
- Memory::SDRAM: 1 GB
- Capacity:
AS7-D PIU
Channels: 512
2M PCMs: 16 (32)
ETC
GSW2KB
GTIC
ETC
ETC
BCSU 1
FTRB
BCSU 4
MCMU
BCSU
FTRB
MCMU
FTRB
LANU
L1 Instruction cache: 32 kB
L1 Write Back Data Cache: 32 kB
L2 Cache: 512 kB
ETC
OMU
BCSU 2
BCSU 3
FTRB
LANU
GTIC
BCSU 5
BCSU 6
CLS
MHz FSB (Data quad pumped, 3.2 GB/s).
GSW2KB
CLS
purpose peripheral slot computing engine

- 512 HDLC channels (2x that of AS7-C), 8x more
memory, data processing performance is
estimated to be ~1.4x that of AS7-C
- an interface to OMC (X.25), then it is installed
in OMU.
- Processor and capacity Performance:
- Processor: Intel Celeron M ULV 1.0 GHz, 400
PDFU

New AS7-D (2/2)
AS7_D 14 TRACK: 8
MS:FA000000 ME:FBFFFFFF IS:E240 IE:E27F
INT:20H SW:0649005E
TSLS 30
20
10
0
LAPD
8M PCM: 400 B
11111111111111111111111111111111
R 11111111111111111111111111111111
CONNECTOR SIDE: HOR: VER: POINT: 1
AS7_D 13 TRACK: 7
MS:F8000000 ME:F9FFFFFF IS:E200 IE:E23F
INT:22H SW:0649005C
TSLS 30
20
10
0
CCS7
8M PCM: 416 B 11111111111111111111111111111111
R 11111111111111111111111111111111
LAPD
8M PCM: 401 B
11111111111111111111111111111111
R 11111111111111111111111111111111
LAPD
LAPD
8M PCM: 402 B
11111111111111111111111111111111
R 11111111111111111111111111111111
LAPD
LAPD
8M PCM: 403 B
11111111111111111111111111111111
R 11111111111111111111111111111111
LAPD
LAPD
8M PCM: 404 B
11111111111111111111111111111111
R 11111111111111111111111111111111
LAPD
8M PCM: 415 B
11111111111111111111111111111111
R 11111111111111111111111111111111
8M PCM: 418 B 11111111111111111111111111111111

R 11111111111111111111111111111111
8M PCM: 419 B 11111111111111111111111111111111
R 11111111111111111111111111111111
8M PCM: 420 B 11111111111111111111111111111111
R 11111111111111111111111111111111
.
LAPD
8M PCM: 431 B 11111111111111111111111111111111

R 11111111111111111111111111111111
Above is example of internal PCM connection for BCSU-1:

On track 8 : PCM 400 PCM 415 (16 PCMs) all TSL (0-31) used for LAPD
On track 7 : PCM 416 (1 PCM) all TSL (0-31) used for SS7, PCM 418-431 (14 PCM) all TSL (0-31) used for LAPD

New PCU2-E
Flexi BSC
PCU functionality in Flexi BSC can be realized by:
GSW2KB
GTIC
ETC
ETC
GSW2KB
GTIC
ETC
ETC
FTRB
BCSU 4
OMU
BCSU 2
BCSU 3
FTRB
LANU
MCMU
BCSU 1
LANU
BCSU
FTRB
MCMU
FTRB
BCSU 5
10 (active) BCSU/BSC x 5 PCU2-D/BCSU x 2 logical

PCU/PCU2-D 256 Abis Channel / logical PCU =
25600 Abis Channel
PCU2-E Capacity
PCU2-E PIU
BTS Objects
TRX Objects
Abis Channels
Up to 30 x 384
Up to 30 x 1,024
Up to 30 x 1,024
BCSU 6
CLS
16 Kbps
up to 5 PCU/BCSU x 6 BCSU/BSC = 30 logical
PCU/BSC => 30720 Abis channels / BSC3i 3000
If compared with PCU2-D:
:Consist of 2 logical PCU
1 logical PCU can handle 256 Abis Channel
16 Kbps
In BSC 2000, the capacity =
PDFU
CLS
PCU2-E
New PCU2-E offering significant capacity
enhancements:
Consist of 1 logical PCU
1 logical PCU can handle 1024 Abis Channel
PDFU

Computer Units OMU (Operation and
Maintenance Unit) (4/4)
OMU
OMU
Plug-in units
CP816-AC
AS7-D
SERO-B
Mass
memory
adapter:
PSC6-AB
DCAR1-A
HWAT-B
OMU is an interface between the BSC and a

higher-level network management system
and/or the user. The OMU receives fault
indications. It can produce local alarm
printouts to the user or send the fault
indications to NetAct
In a fault situation, the OMU automatically
activates appropriate recovery and diagnostics
procedures. Recovery can also be activated by
the MCMU if the OMU is lost.
The OMU consists of microcomputers and
contains I/O interfaces for local operation.
The tasks of the OMU can be divided into five
groups:
traffic measurement functions

maintenance functions
system configuration administration functions
system management functions
LAN topology management

DCAR1-A Plug in Unit
USB port in DCAR1-A

PIU
HDSAM (contained
HSD07) also in DCAR1A PIU
USB memory stick will provide
Duplicated Hard disk units are
reliable means for backup

copying SW and database on a
transferable media in BSC
Capacity of memory stick
is 4 GB
installed with carrier adapter

per BSC to ensure high
reliability
Easy to change or upgrade
without traffic interruption
Capacity of HSD07 is 73 GB
Red - out of
Service
green Power
good
amber hard disk
drve activity
LED indicator on DCAR1A :

green normal operation
red failure condition
Blue Hot Swap
Hard disk AMC front panel

(HDSAM-A)

Other Units
Flexi BSC cabinet
CLOC
GSWB
GTIC
ETC
ETC
CLOC
GSWB
GTIC
ETC
ETC
CLOC
GSW2KB
LANU
LANU
LANU
GTIC
ETC
BCSU 1
LANU 0
BCSU 1
LANU 1
BCSU 0
GTIC 1
ETC
0
ETC
1
BCSU 3
ETC
2
ETC
3
CLS 1
GSWB
1
GTIC 0
MCMU
0
MCMU
1
GSWB
0
CLS 0

Hardware Changes compare to BSC3i 1000/2000
Flexi BSC cabinet
OMU
BCSU 5
BCSU 3 BCSU 5
2000 x 900 x 600 cabinet (HxWxD)
New Plug In Unit:

ETIP1-A for EET interface
PCU2-E for Packet data
PSC6-D for power supply in each
ESB24-A for ethernet switch
SWPRO-C for controlling GSWB
Common Unit:
FTRB-A enhanced fan units
CP816-A CPU for all computer
units
Bit based group switch for 2048
PCMs (GSW2KB)
ET16 for E1/T1 interface
ETS2 for STM-1 or OC-3 interface
DCAR-A for mass memory
LANU
Ethernet Message Bus (EMB)
Removed Units:
ESB26 Ethernet Switch
CLAB for clock repeating
Architecture changes
6 + 1 BCSU units
No extension cabinet
Flexi BSC Capacity
Flexi BSC Capacity

Configuration steps
Flexi BSC maximum capacity steps in S14 hardware environment
#TRX per BSC (*1)
1500
5011000
10011500
15012000
20012500
25013000
500
1000
1500
2000
2500
3000
10
15
20
25
30
max #PS Abis chan@16
5120
10240
15360
20480
25600
30720
max #RTSL
4000
8000
12000
16000
20000
24000
max #SS7 links:

64 kbps
128 kbps
256 kbps
512 kbps
1024 kbps
HSL
8
4
2
2
1
2
16
8
4
4
2
4
16
12
6
6
3
6
16
16
8
8
4
8
16
16
10
10
5
10
16
16
12
12
6
12
max #LAPD (*2)
992
1984
2976
3968
4960
5952
#PCM (*3):
ET16(*4)
SET (*5)
ETIP(*5)
800
16
12
800
16
12
800
16
12
800
16
12
800
16
12
800
16
12
#active BCSU
max #BTS / #BCF
max #logical PCU2-E
(*1): Software is scalable in 1 TRX steps with licence key.

(*2): #LAPD links achievable with low capacity SS7 links. Therefore in 3000 TRX conf. SS7 over IP (SIGTRAN) should be used to avoid lack of LAPD links.
(*3): #controllable PCM lines does not depend on #BCSU
(*4): above 48 requires a cabling cabinet

(*5): Active interfaces. Doubled for redundancy: 16 + 16 (SET) or 12 + 12 (ETIP).
GEMINI OVERVIEW
GEMINI Overview
GEMINI stands for GSM/EDGE Migration Network Infrastructure
The program adapts BTSplus product family (BR-BTS) SW to work with

FlexiBSC product family (BSS-BSC)
GEMINI denotes SW adaptation, no HW modifications are foreseen on the BTSplus
GEMINI does not affect connections between BSS-BTS products and BSC3i
Base station types of the BSS

product line
The Flexi BSC product family has been adapted, allowing it

to manage the BTSplus as a new BSS BTS type, in addition to
the base station types of the BSS product line:
UltraSite EDGE BTS

MetroSite EDGE BTS
Talk-family BTS
Flexi EDGE BTS
GEMINI is fully transparent for BSS-BTS families, no impact on any of them (not only on FlexiEDGE)
BTSplus product family
The BTSplus product range can be divided into three type groupings:
BTSplus
mainline:
BS-240/BS-241
BS-240 II/241 II/241 II B
BS-240XL
BS-240XL II
BS-40 II
BS-40/41
BS-82 II M
BTSplus eMicro:
BS-82
E
BTSplus basic:
BS-240XS B
BS-288
BTS configuration limits

in GEMINI
BSC3i point of view:

FlexiBTS/UltraSiteBTS/MetroSiteBTS limits are not affected but the ranges of
TRX-id and cell-id must be adjusted in BSC3i due to introduction of GEMINI (e.g.
TRX-id from 24 to 32)
BTSplus point of view:
The number of TRX in BTSE rack is restricted (limited by COBA memory) from 48
to 32
32 TRXs/BCF corresponds to usage of up to 16 FlexCU
Network architecture Changed during

Migration
After migration, the LMT Evolution has been integrated into NetAct to replace the
Radio Commander.
Features and capabilities of the various

Network Elements during Migration
eBSC/BSC1
Download new BSS-compatible software to the BTSplus
Activate new BSS-compatible software in the BTSplus
Upload configuration data to RC and the LMT
Export configuration data for migration to the Flexi BSC
Flexi BSC
Tolerate or ignore BR Abis-like connection establishment attempts
Support new BTSplus software build types
GEMINI Abis Interface
Abis allocation in BR product line

Signalling and traffic timeslots are configurable in a BTSE on up to 4 PCMB lines
with the BTSplus family => these PCM lines support load-sharing and fault
management
LAPD signalling timeslots are 16 kbps sub-slots or 64 kbps timeslots => mixture of
signalling links of different capacities is not allowed between BTS and BSC
On the BTSE side the LAPD timeslots are called LAPDLE while in the BSC database
they are called LPDLM although they may carry both LPDLM (management) and
LPDLR (TRX) type signalling
For each PCMB line at least one LAPDLE/LPDLM is required
For a single BTSE up to 11 LPDLM objects can be defined
The TRXs belonging to the same BTSE can be configured on one common physical
LAPD link
The LAPD pool is a set of 16 kbps PCM sub-slots represented in the data-base by
the LPDLM object
11
max

Site_1
BTSM_1
BSC
sub-pool_A
Cell 1
Cell 2
PCU
sub-pool_B
PCM-0
PCM-1
Cell 2
sub-pool_B
sub-pool_C
PCU
Cell 3
Site_2
sub-pool_C
PCM-2
Cell 4
PCM-1
BTSM_2
sub-pool_C
In case of a PCM-0 failure traffic is

dynamically reallocated to subpool_B of the pool_BTSM_1
Cell 5
Cell 6
sub-pool_A
Cell 1
PCM-1
BTSM_2
Cell 4
BSC
BTSM_1
PCM-0
Cell 3
Site_2
Site_1
Star configuration
Integrated cross-connect or
multi-drop configuration
sub-pool_A
pool_BTSM_1
sub-pool_B
sub-pool_C
pool_BTSM_2
Cell 5
sub-pool_A
pool_BTSM_1
Cell 6
sub-pool_B
sub-pool_C
pool_BTSM_2
Abis pool = set of 16 kbps Abis sub-slots

reserved for a BTSM (on up to 4 PCM lines),
which are dynamically available for radio
timeslots of the BTSM
Abis sub-pool = set of 16 kbps Abis sub-slots on a specific PCM
line reserved for a BTSM, all Abis sub-pools reserved for a given
BTSM constitutes the Abis pool, each Abis sub-pool is
associated with the LPDLM channel

The idea of the Abis sub-pools defined for the Abis pool associated with a
BTSM was developed to make the PCMB fault management flexible
The PCMB fault is detected by the LPDLM fault:
Up to BR6.0: radio channels statically associated with the corresponding Abis subslots of the faulty PCMB are disabled until the fault is repaired
disabled radio channels
BSC
PCMB:1
Abis sub-pool
PCMB:0
Abis sub-pool
PCM fault detected by LPDLM
BTSM
BTS1
BTS2
static allocation
From BR7.0: Abis sub-pools are configured on different PCMB lines => radio
channels so far transmitted within the Abis sub-pool of the faulty PCMB are
dynamically rearranged and transmitted within the Abis sub-pool of the operative
PCMB
BSC
PCMB:1
Abis sub-pool
PCMB:0
Abis sub-pool
PCM fault detected by LPDLM
BTSM
BTS1
BTS2
dynamic allocation
radio channels are dynamically rearranged to

the operative PCMB
Distribution of the Abis sub-pools over different PCMB lines ensures the
highest resilience against the PCMB faults
BR Network Architecture
Definitions and Basic Configuration Management (1/2)
BTSE (BTS Site Equipment) represents one or more physical BTS
cabinets, e.g. BS-240 base rack or BS-240 base rack + BS-240
extension racks, that make up a site
BTSM (BTS Site Manager) represents a logical functionality
controlling one or more BTSs (cabinets = base rack or base rack +
extension racks) within one BTSE => performs all the O&M
functions common to all transceivers
CREATE BTSM NAME=BTSM:0199*,
[OPTIONAL PARAMETERS]**;
BS-240 extension racks

eBSC
Example:
Step 1: create a new BTSM:
CREATE BTSM NAME=BTSM:0;
=> The BTSM is created
BTSM:0
BS-240 (base
rack)
Definitions and Basic Configuration
Management (2/2)
BTS (Base Transceiver Station) locates a cell connected to

a BSC and logically represents all information related to
the cell and its configuration
The command CREATE BTS sets the configuration of the
cell by specifying the global parameters necessary for the
creation:
Cell 1
BTS:0
CREATE BTS NAME=BTSM:0199/BTS:011,

[OPTIONAL_PARAMETERS]*;
Example:
BS-240 extension racks

eBSC
Step 2: create a new BTS:

CREATE BTS NAME=BTSM:0/BTS:0
=> The BTS is created and assigned to the
BTSM
BTSM:0
BS-240 base rack
Classical Single Band Network
CREATE BTS NAME=BTSM:0/BTS:0,CELLTYP=STDCELL,SYSID=BB900,BCCHFREQ=12;
CREATE TRX NAME=BTSM:0/BTS:0/TRX:0,TRXFREQ=12;
CREATE TRX NAME=BTSM:0/BTS:0/TRX:1,TRXFREQ=...;
Cell 3
BCCH 900
...
Cell 1
BCCH 900

...
BCCH 900
Cell 2
...
BSC
defines the bandwidth of a

cell, e.g. BB900 = PGSM
site
BTSM:0
BTS:0
BTS:1
defines the type of a cell
Each 900 MHz cell has its

own BCCH carrier
eBSC
Cell 1
BTS:2
Cell 2
TRX:0
TRX:3
TRX:6
TRX:1
TRX:4
TRX:7
BCCH carrier
layer
Cell 3
BS-240
TRX:2
TRX:5
TRX:8
Cell 1
Cell 2
Cell 3
See the previous slide for

the BTSM:0
Classical Dual Band Network
CREATE BTS NAME=BTSM:1/BTS:0,CELLTYP=STDCELL,SYSID=DCS1800,BCCHFREQ=975;
BCCH 900
Cell 3
...
BCCH 900
BCCH
1800

...
- 900 MHz
- 1800 MHz
BCCH
1800
Cell 5
...
BCCH carrier
layer
BSC
BTSM:0
BTS:1
Cell 4
BCCH
1800
Cell 2
BCCH 900
BCCH carrier
layer
site
site
BTS:0
Cell 1
Cell 6
BTSM:1
BTS:2
eBSC
BTS:0
BTS:1
BTS:2
TRX:0
TRX:3
TRX:6
TRX:0
TRX:3
TRX:6
TRX:1
TRX:4
TRX:7
TRX:1
TRX:4
TRX:7
TRX:2
TRX:5
TRX:8
TRX:2
TRX:5
TRX:8
Cell 1
Cell 2
Cell 3
Cell 4
Cell 5
Cell 6
Cell 1
Cell 4
Cell 2
Cell 5
Cell 3
Cell 6
BS-240
BS-240
Dual Band Standard Cell Network
CREATE BTS NAME=BTSM:0/BTS:0,CELLTYP=DBSTDCELL,SYSID=GSMDCS,BCCHFREQ=12;
separate band specific

antennas or a common
dual-band antenna

Cell 3
...
BCCH 900
Cell 1
BCCH 900

...
- 900 MHz
- 1800 MHz

BCCH 900
Cell 2
...
BSC
site
BTSM:0
In case the greater number of TRXs is

required just add (an) extension rack(s)
and create new TRXs
separate feeder and

combiner systems are
necessary
BS-240 base
rack
eBSC
BTS:0
BTS:1
BTS:2
Cell 1
TRX:0
TRX:3
TRX:6
TRX:1
TRX:4
TRX:7
TRX:2
TRX:5
TRX:8
Cell 1
Cell 2
Cell 3
BCCH carrier
layer
Cell 2
Cell 3
BSS Network Architecture

Management (1/6)
BCF (Base Control Function) is a functional entity which handles
common control functions of a base transceiver station:
Associated with a physical base station cabinet, e.g. with the
UltraSite BTS
Usually contains several BTS objects or SEG objects which represent
cells (sectors)
Created in the BSS database using the following syntax in the
command line:
ZEFC:<BCF identification>,<site
type>:<D-channel link set name>;*
Example:
Step 1: create a new BCF:
ZEFC:1,P:DNAME=OMU23;
=> The BCF is created and associated with
the OMUSIG LAPD channel
B: 2nd generation
D: Talk-family
F: PrimeSite
C: MetroSite
I: InSite
P: UltraSite
E: Flexi EDGE
BSC3i
BCF-1
Ultra Site
PCM line with OMUSIG=OMU23

Definitions and Basic Configuration Management
(2/6)
BTS (Base Transceiver Station) is a cell consisting of TRXs
belonging to the same base transceiver station and
operating on the same frequency band:
Cell 1
In the BSS database the cell is represented by the BTS object

Created in the BSS database using the following syntax in the
command line:
BTS-1
ZEQC:<BCF identification>,<BTS identification>:<cell

identity>,<frequency band in use>:<network colour
code>,<BTS colour code>:<mobile country code>,<mobile
network code>,<location area code>;
Example:
BSC3i
Step 2: create a new BTS:
Cell 1
ZEQC:BCF=1,BTS=1:CI=11,BAND=900:
NCC=3,BCC=4:MCC=111,MNC=02,LAC=3
344;EFC:1,D:DNAME=OMU23;
=> The BTS is created in the BCF
BCF-1
Applicable to the standard single or dual band network
Ultra Site

Management (3/6)
SEG (Segment) is a cell consisting of TRXs belonging to:
More than one co-located and synchronised base transceiver stations served
by a common BCCH channel
The different frequency bands served by a common BCCH channel
In the BSS database the segment is represented by the SEG object

Created in the BSS database using the following command line with the
optional SEG identification:
ZEQC:<BCF identification>,<BTS identification>, <SEG identification>:<cell identity>,
<frequency band in use>:<network colour code>,<BTS colour code>:<mobile
country code>,<mobile network code>,<location area code>;
The multi BCF control and common BCCH control use the concept of the
segment:
The maximum number of BTSs in a segment is 32
The maximum number of TRXs in a segment is 36

Management (4/6)
The BTS object in a segment must consist of TRXs of the same frequency band =>
PGSM 900, EGSM 900, GSM 1800, GSM 800 or GSM 1900
The BTS object in a segment must consist of TRXs of the same base station site type
=> Talk family, UltraSite, Flexi EDGE or MetroSite
common to BTS specific TRXs
common to all TRXs
The use the segment concept is not restricted to the multi BCF control or to the
common BCCH control => e.g. multiple hopping groups in a cell can be setup by
creating several BTS objects in a segment and grouping TRXs of each hopping rule
in each BTS object

Management (5/6)
dual-band antenna
Example 1: the number of TRXs in a site requires use

of one cabinet only (no multi BCF control)
Step 3: create a new SEG and assign BTSs to the SEG:
ZEQC:BCF=1,BTS=1,
SEG=1:CI=11,BAND=900:NCC=3,BCC=4:MCC=111,MNC=02,LAC=33
ZEQC:BCF=1,BTS=2,
=> 1 SEG object is created and associated with 1 BCF object, 2 BTS objects are
assigned to the SEG object
SEG-1
BTS-1
BTS-2
separate feeder and

combiner systems are
necessary
BSC3i
Cell 1
BCF-1
Ultra Site

Management (6/6)
dual-band antenna
Example 2: the number of TRXs in a site requires use

of few cabinets (multi BCF control)
Step 3: create a new SEG and assign BTSs to the SEG:
ZEQC:BCF=1,BTS=1,
ZEQC:BCF=2,BTS=2,
SEG-1
=> 1 SEG object is created and associated with 2 BCF objects, 2 BTS objects are
assigned to the SEG object
BTS-1
BTS-2
SYNC
BSC3i
Cell 1
BCF-1
Ultra Site
BCF-2
Ultra Site
Create BTSPLUS in
FlexiBSC
Creating BTSPLUS in FlexiBSC

Database in eBSC
CREATE BTSM:NAME=BTSM:2,<..>,PCMCON0=PCMB_003-PORT_0,PCMCON1=PCMB_004-PORT_2,<>;
CREATE LPDLM:NAME=BTSM:2/LPDLM:0,ABISCH=3-31,LAPDPOOL=1;
CREATE LPDLM:NAME=BTSM:2/LPDLM:1,ABISCH=4-30,LAPDPOOL=1;
CREATE BTS:NAME=BTSM:2/BTS:0,CELLGLID="460"-"00"-6378-36897,BSIC=65,PLMNP=100,CELLTYP=STDCELL,SYSID=BB900,BCCHFREQ=27,CALLF01=56,CALLF02=32,<..>;
CREATE BTS:NAME=BTSM:2/BTS:1,CELLGLID="460"-"00"-6378-36898,BSIC=6-3,PLMNP=100,<>;
SET PWRC:NAME=BTSM:2/BTS:0/PWRC:0,<.>;
CREATE PTPPKF:NAME=BTSM:2/BTS:0/PTPPKF:0,RACODE=1,RACOL=0,<>;
CREATE FHSY:NAME=BTSM:2/BTS:0/FHSY:1,HSN=3,MOBALLOC=CALLF01&CALLF03&CALLF04&CALLF05&CALLF06;
CREATE TRX:NAME=BTSM:2/BTS:0/TRX:0,TRXFREQ=BCCHFREQ,, TRXMD=EDGE,<>;
CREATE TRX:NAME=BTSM:2/BTS:0/TRX:1,TRXFREQ=CALLF01, TRXMD=GSM,<>;
CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:0,CHTYPE=MAINBCCH, FHSYID=FHSY_0,<>;

CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:1,CHTYPE=SDCCH,
CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:2,CHTYPE=CCCH,
CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:3,CHTYPE=TCHF_HLF,
CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:3,CHTYPE=TCHSD,

Database in eBSC
CREATE TGTBTS:NAME=TGTBTS:66,CELLGLID="460"-"00"-6244-13409,BSIC=60,BCCHFREQ=9,SYSID=BB900,MSTXPMAXGSM=5,<..>;
CREATE TGTPTPPKF:NAME=TGTBTS:66/TGTPTPPKF:0,RACODE=1,RACOL=0,GRXLAMI=6,GMSTXPMAC=2,<>;
CREATE TGTTDD:NAME=TGTTDD:52,CELLGLID="460"-"00"-43030-32817,RNCID=390,BNDWID,<..>;
SET HAND:NAME=BTSM:3/BTS:0/HAND:0,<>;
SET BTS:NAME=BTSM:3/BTS:0,BTSHSCSD=FALSE,<>;
CREATE
ADJC:NAME=BTSM:2/BTS:0/ADJC:33,TGTCELL=BTSM:68/BTS:0,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0,H
OMDOFF=0,<>;
CREATE
ADJC3G:NAME=BTSM:2/BTS:0/ADJC3G:0,TGTCELL=TGTTDD:0,USRSCP=18,USECNO=23,UMECNO=19,UADJ=63,PLNC=
0,<>;
CREATE
ADJC:NAME=BTSM:3/BTS:0/ADJC:8,TGTCELL=BTSM:2/BTS:0,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0,HO
MDOFF=0,<>;
Creating BTSPLUS in Flexi BSC

Frequency bands Supported in GEMINI
The BTSplus supports the following frequency bands:

GSM 850 MH
GSM 900 MHz (primary GSM)
GSM 900 MHz extended (EGSM)
GSM 1800 MHz (DCS)
GSM 1900 MHz (PCS)
Note: When operating the BTSplus with

the Flexi BSC product family, the GSM-R
frequency band is not used.

BB HOPPING in BR
Baseband hopping with CU and ECU in one cell still using EGPRS
in BR hopping system (FHSY) is defined per TSL and 11 FHSYs per cell are allowed
In case of baseband hopping (BB) if FHSY include ECU and CU then EDGE is not supported on
that TSL where this FHSY is running
this gives huge flexibility in hopping configuration eg. following BB hopping configuration is
supported
In BR it is possible to define BB hopping with ECU only (TRX1-4) for certain timslots (TSL 0-4)
serving EGPRS and for normal calls on the other TSLs (TSL 5-7) BB hopping including all CUs in
the cell (TRX1 -6).

BB HOPPING in GEMINI
Baseband hopping with CU and ECU in one cell still using EGPRS
in BSS one hopping system can be configured in one BTS but it is possible to have multiple
BTS (up to 32) per segement (cell) (COMMON BCCH in used)
In case of mixed configuration (cells with EDGE capable and EDGE not capable TRXs) 2 BB
hopping systems must be configured by means of 2 BTS objects per segement and each of
them must be using only TRXs of the same type; otherwise EDGE will be not supported
ECU/FCU supports EDGE while CU/GCU does not

Points in Creating BTSPLUS in Flexi BSC
BTSM refers to BCF in Flexi BSC
Define the port and PCM during creating BCF
Multiplexing LAPD in Flexi BSC
LAPD mapping between BSC and BTS site
Plan TRX LAPD multiplexing into different LAPD( LAPD overload protection )
Max to 11 LAPD per BCF

BTS refers to CELL(SEGMENT) in Flexi BSC
Common BCCH allows EGSM/PGSM used in the same cell
Define the CHW (refers to BTM NO. in eBSC database) during creating BTS
Plan the TRX TCH TSL mapping into PCM-TSL
Max to 32 TRX per BCF of BTSPLUS

Create LAPD
Create OM LAPD( Lapd mutiplexing)
N ... NORMAL CHANNEL

C ... COMBINED CHANNEL
TRXSIG and OMUSIG channels that share the same timeslot

(physical LAPD link) must be configured to the same BCSU unit and
to the same signaling terminal
OMU TEI=1
M ... MULTIPLEXED CHANNEL
ZDSE:OM001:BCSU,0:62,1:64,265-31:M,2;
0 ... STANDARD ABIS SETUP
62- OM LAPD
LAPD BIT RATE=64K
1 ... SATELLITE ABIS SETUP

2 ... BTSPLUS ABIS SETUP
3 ... BTSPLUS SATELLITE ABIS SETUP
4 ... IP ABIS SETUP 1
Create TRX LAPD ( Lapd mutiplexing)

TRX LAPD controlled by the same BCSU as OM Lapd
5 ... IP ABIS SETUP 2 (FOR LONG DELAYS)

6 ... IP ABIS SETUP 3 (FOR LOW QUALITY LINES)
7 ... ENHANCED SATELLITE ABIS SETUP
8 ... STANDARD ABIS SETUP
ZDSE:T0011:BCSU,0:0,1:64,265-31:M,2;
0- TRX LAPD
ZDSE:T0012:BCSU,0:0,2:64,265-31:M,2;

Create BCF
B .... 2ND GENERATION
Create BCF
D .... TALK-FAMILY
F .... PRIMESITE
C .... METROSITE
I .... INSITE
P .... ULTRASITE
PCM connect to BTS.
E .... FLEXI EDGE

X .... BTSPLUS
PORT0/PORT2 --- the PCM interface in the BTS Site
ZEFC:4,X,M:DNAME=OM004:::::PORT0=267,PORT2=268,PORT4=269;
BTS HW TYPE
M ... MAINLINE
E ... EMICRO
B ... BASIC
BTSplus mainline:
BS-240/BS-241
BS-240 II/241 II/241 II B
BS-240XL
BS-240XL II
BS-40 II
BS-40/41
BS-82 II
BTSplus eMicro:
BS-82
BTSplus basic:
BS-240XS
BS-288

Create BTS
Create Main BTS
ZEQC:BCF=4,BTS=8,NAME=GSMINGBO3:CI=49203,BAND=900,
CHW=2:NCC=5,BCC=7:MNC=00,MCC=460,LAC=6378:HOP=BB,HSN1=11,HSN2=11;
Cell id, BTS number in eBSC Database
From 0-2
Create other BTS in the Segment
ZEQC:BCF=4,BTS=9,SEG=8,NAME=GSMINGBO3E:CHW=2,BAND=900;
Cell id : same as the BTS NO. in eBSC database

Create other objects :Same as creating the Flexi BTS
Create EDAP
ZESE:ID=268,CRCT=268-19&&-24,BCSU=0,PCU=6;
Create TRX
ZERC:BTS=4,TRX=1:GTRX=N,DAP=N,PREF=P:FREQ=27,TSC=5,PCMTSL=2671:DNAME=T0041:CH0=MBCCH,CH1=SDCCH,CH2=TCHD,CH3=TCHD,CH4=TCHD,CH5=TCHD,CH6=TCHD,CH7=SDC
CH;
ZERC:BTS=4,TRX=4:GTRX=Y,DAP=268,PREF=N:FREQ=39,TSC=5,PCMTSL=2683:DNAME=T0044:CH0=SDCCH,TCT=TCHD;
(Extended cells)
ZERC:BTS=4,TRX=1:GTRX=Y,ETRX=N,PREF=P:FREQ=27,TSC=5,PCMTSL=2671:DNAME=T0041:CH0=MBCCH,CH1=NOUSED,CH2=LRTCH,CH3=LRTCH;
ZERC:BTS=4,TRX=2:GTRX=Y,ETRX=E,PREF=N:FREQ=39,TSC=5,PCMTSL=2683:DNAME=T0042:CH0=ERACH,CH1=SDCCH,CH2=TCHD,CH6=EGTCH,CH7=EGTCH;

Create other objects :Same as creating the Flexi BTS
Create Power Control parameters
ZEUC:SEG=4;
Create Handover parameters

ZEHC:SEG=4;
Create 2G ADJ
ZEAC:SEG=4::MCC=460,MNC=00,LAC=30027,CI=26261:NCC=4,BCC=5,FREQ=49:RAC=1
00;
Create W ADJ
ZEAE:BTS=4::MCC=460,MNC=01,RNC=1280,CI=1472:LAC=50432,SCC=25,SAC=1472,FR
EQ=10713;
Review of Create BTSplus in

GEMINI
Multiplexing the LAPD

Identify BTS site subtype
Identify the PCM&BPORT
Identify the CHW
Official process of BTSplus

Migration in GEMINI
Official Migration Process
Official Migration Process

Data export and migration
Dbaem
Used in BR line to get database with a format of ASCII file.

Each released BSC software load has a dedicated dbaem version.
Exporter migration tool

The exporter migration tool is a new offline tool used to map BTSplus
configuration data, in the form of an eBSC/BSC1 configuration ASCII command
file, to a Flexi BSC configuration file in the NetAct Configurator-compliant RAML
2.0 XML format.
exporter --bscfile <ASCII command file> --template <list of BTSMs>--outfile

<template control file name>
Replace all instances of TBD with appropriate values for the mapped IDs.
exporter --bscfile <ASCII command file> --ctfile <XML control file>
Conversion tool Control File (TBD file)
Conversion tool output

(configuration script (RAML 2.0 format)
suitable for importing in NetAct)
Exporter Tool Not Supprot
The exporter migration tool does not

automatically migrate:
eBSC/BSC1 licensing data: new Flexi BSC licenses have to be provided and
installed according to contract
GPRS configuration data
Frequency hopping system configuration
Extended cell and concentric cell configurations

BTS cells with the following system indicators (SYSID):
EXT900
GSMDCS
GSM850PCS
GSM850DCS
GSMR
Exporter Tool Not Supprot
Requirements for additional measures

Abis loop connection between the BTSplus and the eBSC/BSC1
Insufficient bandwidth on the BSS Abis interface
Abis compression/optimization equipment is installed

Non BTSplus site-specific data
Extended cells
Baseband hopping in a cell with mixed GSM/EDGE transceiver hardware
BTSplus migrated to another location
Change in BTSplus hardware configuration
Change in the CGI of BTSplus cells
Process of BTSplus Migration in

HLJ
Process of BTSplus Migration in HLJ

Preparing
Check all the related elements are available for
Migration
In SHMCC S14 pilot ,the Software of elements are:
Check RC and LMT available

Upload eBSCs database --- eBSC
The database mainly contains:
BTSM HW database: BTSM type, port
LAPD: LAPD PCM, LAPD TSL
BTS HW basic parameters:

LAC/CI/NCC/BCC/BAND/PLMN/HOP
TRX FREQ&INDEX&TCH TYPE
Download the new software load to BSXXX from

eBSC
Monitor KPI of the Site to be rehosting
Element
Software
BR line
BR9029
FlexiBSC
S14 ??
NetAct
OSS5.1 CDSet2 PCD

MML command generate and send to Flexi BSC
Check the new Flexi BSC is ready
Modify the parameters (ZEEO/ZEGO/ZOCI)
Enable Features and Licenses (ZWOI/ZWOS/ZW7I)
Enable the measurement report (ZTPI/ZTPM/ZTPS)
Create the new SW package for BTSPLUS in Flexi BSC
Prepare the MML command

Prepare the MML command according to the plan data and new PCM
Integrate the BTSPLUS in Flexi BSC
Check new configurations consistency

Cutover
Check the status of eBSC and BSxxx

Check the alarms and working states of the rehosting BSxxx and the alarms of the eBSC
Active the new SW load in RC

After the GEMINI SW load active, the icon of the btsplus in RC will be out of control with grey color.
Disconnect PCM from eBSC then connect to the new Flexi BSC in 20 mins
There is a timer to set automatic fallback of BSxx to BR-Abis capable software load. If the PCM cant be connected to Flexi BSC within 20
minutes, the BSxx software load will fallback to old software load that available in eBSC. Those BSxx can be afterwards managed via
Radio Commander again. The timer will be disabled after BTSplus connected to Flexi BSC.
Check the MSS configuration

Unlock the BCF in Flexi BSC
Monitor the restart phase in Flexi BSC
Maybe it takes a long time to restart some BCFs, Mornitor the restart phase with ST RPHASESX
Update the incoming ADJ

Check all rehosting BTSPLUS working status, alarms, and BSC alarms
Clean-up
Delete old data in eBSC if the result of drive test is OK
Safecopy in Flexi BSC
Optimization
Network optimization to reach measured KPIs
Adapt network planning parameters to improve the KPI.
Points during cutover
The PCM should be connect to Flexi BSC within 20 mins.
The LAPDs state may be down to UA-AD during the PCM cutover
Monitor the BCF restart phase, make sure all phases OK. Some sites may take
more than 20 mins to finish the restart phase.
Some TRX may be BL-SYS or BL-RSL or BL-RST after the BCF restart
phase finish and the TRX LAPD is ok, Lock and Unlock the BTS

Flexi BSC Gemini

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Flexi BSC Gemini

Transféré par

Droits d'auteur :

Formats disponibles

FLEXI BSC & GEMINI

Flexi BSC in Brief

Flexi BSC in Brief

Flexi BSC in Brief

Packet Data channels

PCM/SDH transport lines

12 + 12 Gigabit Ethernet connections for

IP based SS7 (SIGTRAN) links

HW upgrade path to Flexi BSC

Supported from all BSC3i configurations

Flexi BSC in Brief

General Evolution of BSC Products

High Capacity BSC

660 TRXs with 1-cabinet

Flexi BSC in Brief

FLEXI BSC (BSC3i 3000)

BSC3i 2000 (11880Erl)

(8x1x2x256) (8x1x2x256) (6x2x2x256) (10x5x2x256) (6x5x1x1024)

# BCSUs/BSC x # PCU pius/BCSU x #

Flexi BSC product family

Flexi BSC Hardware and Functionality

Flexi BSC Hardware and Functionality

Fast installation and very easy expansion

No special site requirements

Flexi BSC Hardware and Functionality

Flexi BSC cabinet

In the Flexi BSC, the call

2000 x 900 x 600 cabinet (HxWxD)

Flexi BSC Hardware and Functionality

The Marker and Cellular Management

Flexi BSC Hardware and Functionality

The SWPRO-C plug-in unit is used as a control

unit for a bit-oriented group switch (GSWB).

BSC3i 1000 & 2000 Hardware and Functionality

Flexi BSC Hardware and Functionality

The Abis interface part of the BCSU controls the

Performing the distributed functions of the

Flexi BSC Hardware and Functionality

- The AS7 plug-in unit function as a general

MHz FSB (Data quad pumped, 3.2 GB/s).

purpose peripheral slot computing engine

Flexi BSC Hardware and Functionality

8M PCM: 418 B 11111111111111111111111111111111

8M PCM: 431 B 11111111111111111111111111111111

Above is example of internal PCM connection for BCSU-1:

Flexi BSC Hardware and Functionality

PCU functionality in Flexi BSC can be realized by:

10 (active) BCSU/BSC x 5 PCU2-D/BCSU x 2 logical

Flexi BSC Hardware and Functionality

OMU is an interface between the BSC and a

traffic measurement functions

Flexi BSC Hardware and Functionality

USB port in DCAR1-A

USB memory stick will provide

Duplicated Hard disk units are

reliable means for backup

installed with carrier adapter

LED indicator on DCAR1A :

Blue Hot Swap

Hard disk AMC front panel

Flexi BSC Hardware and Functionality

Flexi BSC Hardware and Functionality

2000 x 900 x 600 cabinet (HxWxD)