FLEXI BSC FLEXI BSC & & GEMINI
Flexi BSC in Brief
Very high circuit-switched capacity for voiceUp to 18,000 ErlangsVery high packet data capacity for EDGE evolutionUp to 30,720 channelsVery high footprint efficiencyLow site-space costs for capacity of 3,000 TRXs and
3,000 BTS sectors and sites in one cabinetExcellent power consumption efficiencyMarket-leading power consumption per capacitySupport for most cost-efficient transport optionsIP/Ethernet available for all interfacesFull flexibility to configure preferred or mixed integrated
transmission type (E1/T1, STM-1/OC-3, IP/Ethernet)ScalabilityCapacity and transmission can be flexibly configured in
small resolution steps to support pay-as-you-grow approach
High reliabilityRedundancy, fault management and overload
protection on top of very high availability design
Flexi BSC in BriefFlexi BSC Product Highlights
Flexi BSC in BriefFlexi 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/T116 + 16 STM-1/OC-3 (mixed/simultaneous use possible)
800 E1/T116 + 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 BriefGeneral Evolution of BSC Products
• 2nd BSC generation• Large Capacity SW
up to 256 TRX (S6) with 2 racks
Third generation
• 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
• High Capacity BSC along with smooth upgrade path (S8)
• Capacity increase up to 512 TRX with 2 racks
1991 1995 1999 2002
Second generation
BSC3i
BSC2i
BSCE• First BSC generation• Up to 128 TRX with 2
high racks
BSC2
First generation
2007 2009
Flexi BSC in BriefFlexi BSC increases usable capacity
BSCE BSC2E BSC2i BSC3i 660 BSC3i 2000 Flexi BSC128 TRX 256 TRX 512 TRX 660 TRX 2000 TRX
BSC2
iBS
C2i
BSC3
i 660
BSC3
i 660
BSC3
i 200
0 (1
1880
Erl)
BSC3
i 200
0 (1
1880
Erl)
PS Traffic handling capacity
BSCE BSC2E BSC2i BSC3i 660 BSC3i 2000 Flexi BSC2048 4096 4096
4.5 x6 x
Notsupportedin S14 Not
supportedin S14BS
C3i 2
000
(118
80 Er
l)FL
EXI B
SC (B
SC3i
300
0) (1
8000
Erl)
1.5 x
3000 TRX
(8x1x1x256) (8x1x2x256) (8x1x2x256)
6144
(6x2x2x256)
25600
(10x5x2x256)30720
(6x5x1x1024)
5 x
BSC3
i 200
0BS
C3i 2
000
BSC3
iBS
C3i
FLEX
I BSC
(BSC
3i 3
000)
1.2 x
number of Abis channel @16kbPs PS TCH
# BCSU’s/BSC x # PCU piu’s/BCSU x # logical PCU’s/PCU piu x #max Abis channel @16Kbps for PS TCH
CS Traffic handling capacity
Flexi BSC product family •The Flexi BSC product family consists of:
BSC3i 660 BSC3i 1000 BSC3i 2000 Flexi BSC pcu2-e 可以带 1024 动态时隙 以前 660pcu2-d 是 256
0
Flexi BSC Hardware and Functionality
• 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
2000 mm
600 mm900mm
Flexi BSC Hardware and Functionality Cabinet Mechanical
M98
Flexi BSC Hardware and Functionality Computer Units (1/4)
MCMUMCMU
BCSUBCSU
OMUOMU
MCM
UM
CMU
OMUOMU
BCSUBCSUBCSUBCSU BCSUBCSU
BCSUBCSUBCSUBCSU BCSUBCSU
Flexi BSC cabinet Flexi BSC cabinet
In the Flexi BSC, the call control functions are executed by micro-computers, calledCall Control Computers
In the Flexi BSC, the call control functions are executed by micro-computers, calledCall Control Computers
MCM
UM
CMU
BCSUBCSU
2000 x 900 x 600 cabinet (HxWxD)
Flexi BSC Hardware and Functionality Computer Units – MCMU (Marker and Cellular
Management Unit) (2/4)
• 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
MCMUMCMU
Plug-in units
• CP816-AC
• SWPRO-C
• ESB24-A
• PSC6-AB
MCM
UM
CMU
MCM
UM
CMU
Flexi BSC Hardware and Functionality New SWPRO-C
• The SWPRO-C plug-in unit is used as a control 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 PDFU
BCSU 1
CLS
GSW2KB
GSW2KB
CLS
LAN
U
LAN
U
FTRB FTRB
Flexi BSC
GTIC
GTIC
ETC
ETC
ETC
ETC
BCSU
BCSU 2 BCSU 3
BCSU 5BCSU 4 BCSU 6
FTRB FTRB
MCM
U
MCM
U
OMU
SWPRO-C
BSC3i 1000 & 2000 – Hardware and FunctionalityESB24 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 CPU’s
• ESB24 units located in LANU are used for IP LAN Switching• Connects together all CPU’s and all PCU’s
• 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
– 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)
• 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
BCSUBCSU
Plug-in units
• CP816-AC
• AS7-D
• PCU2-E
• PSC6-D
BCSUBCSUBCSUBCSU BCSUBCSU
BCSUBCSUBCSUBCSU BCSUBCSU
Flexi BSC Hardware and Functionality Computer Units – BCSU (BSC SIgnalling Unit) (3/4)
Flexi BSC Hardware and Functionality New AS7-D (1/2)
- The AS7 plug-in unit function as a general 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 MH
z FSB (Data quad pumped, 3.2 GB/s).- L1 Instruction cache: 32 kB ▪ L1 Write Back Data Cache: 32 kB ▪ L2 Cache: 512 kB
- Memory::SDRAM: 1 GB - Capacity:
▪ Channels: 512▪ 2M PCMs: 16 (32)
PDFU PDFU
BCSU 1
CLS
GSW2KB
GSW2KB
CLS
LAN
U
LAN
U
FTRB FTRB
Flexi BSC
GTIC
GTIC
ETC
ETC
ETC
ETC
BCSU
BCSU 2 BCSU 3
BCSU 5BCSU 4 BCSU 6
FTRB FTRB
MCM
U
MCM
U
OMU
AS7-D PIU
Flexi BSC Hardware and Functionality 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
• LAPD 8M PCM: 401 B 11111111111111111111111111111111
• R 11111111111111111111111111111111 • CONNECTOR SIDE: HOR: VER: POINT: 1
• LAPD 8M PCM: 402 B 11111111111111111111111111111111
• R 11111111111111111111111111111111 • CONNECTOR SIDE: HOR: VER: POINT: 1
• LAPD 8M PCM: 403 B 11111111111111111111111111111111
• R 11111111111111111111111111111111 • CONNECTOR SIDE: HOR: VER: POINT: 1
• LAPD 8M PCM: 404 B 11111111111111111111111111111111
• R 11111111111111111111111111111111 • CONNECTOR SIDE: HOR: VER: POINT: 1
• ………
• LAPD 8M PCM: 415 B 11111111111111111111111111111111
• R 11111111111111111111111111111111 • CONNECTOR SIDE: HOR: VER: POINT: 2•
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 CONNECTOR SIDE: HOR: VER: POINT: 1
LAPD 8M PCM: 418 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 1
LAPD 8M PCM: 419 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 1
LAPD 8M PCM: 420 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 1
……….
LAPD 8M PCM: 431 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 2
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 LAPDOn 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
Flexi BSC Hardware and Functionality New PCU2-E
• PCU functionality in Flexi BSC can be realized by: PCU2-E
• New PCU2-E offering significant capacity enhancements:
– Consist of 1 logical PCU– 1 logical PCU can handle 1024 Abis Channel @
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 =
10 (active) BCSU/BSC x 5 PCU2-D/BCSU x 2 logical PCU/PCU2-D 256 Abis Channel / logical PCU = 25600 Abis Channel
PDFU PDFU
CLS
GSW2KB
GSW2KB
CLS
LAN
U
LAN
U
FTRB FTRB
Flexi BSC
GTIC
GTIC
ETC
ETC
ETC
ETC
BCSU
BCSU 2 BCSU 3
BCSU 5BCSU 4 BCSU 6
FTRB FTRB
MCM
U
MCM
U
OMU
BCSU 1
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
PCU2-E Capacity
Flexi BSC Hardware and Functionality Computer Units – OMU (Operation and Maintenance
Unit) (4/4)
• 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
OMUOMU
OMUOMUPlug-in units
•CP816-AC
•AS7-D
•HWAT-B
•SERO-B
•PSC6-AB
Mass memory adapter:
• DCAR1-A
Flexi BSC Hardware and FunctionalityDCAR1-A Plug in Unit
USB port in DCAR1-A PIU• USB memory stick will provide
reliable means for backup copying SW and database on a transferable media in BSC
• Capacity of memory stick is 4 GB
HDSAM (contained HSD07) also in DCAR1-A PIU• Duplicated Hard disk units are
installed with carrier adapter per BSC to ensure high reliability
• Easy to change or upgrade without traffic interruption
• Capacity of HSD07 is 73 GB
LED indicator on DCAR1A :green normal operationred failure condition
Hard disk AMC front panel (HDSAM-A)
Red - out of Service
green – Power good
Blue – Hot Swap
amber – hard disk drve activity
Flexi BSC cabinet Flexi BSC cabinet
Flexi BSC Hardware and FunctionalityOther Units
LANULANU
GSW2KBGSW2KB
GTICGTIC
CLOCCLOC ETCETC
ETC
ETC
ETC
ETC
LAN
ULA
NU
LAN
ULA
NU
GTI
CG
TIC
GSW
BG
SWB
CLO
CCL
OC
ETC
ETC
ETC
ETC
GTI
CG
TIC
GSW
BG
SWB
CLO
CCL
OC
Flexi BSC Hardware and FunctionalityHardware Changes compare to BSC3i 1000/2000
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)
MCM
U
MCM
U
11
OMUOMU
Flexi BSC cabinet Flexi BSC cabinet M
CMU
M
CMU
00
BCSU 0BCSU 0
2000 x 900 x 600 cabinet (HxWxD)
BCSU 1BCSU 1 BCSU 3BCSU 3 BCSU 5BCSU 5
LAN
U
0LA
NU
0
BCSU 1BCSU 1 BCSU 3BCSU 3 BCSU 5BCSU 5
LAN
U
1LA
NU
1
GTIC 1GTIC 1GSWB GSWB 11
ETC ETC 11
ETC ETC 33
CLS
1CL
S 1
GTIC 0GTIC 0GSWB GSWB 00
ETC ETC 00
ETC ETC 22
CLS
0CL
S 0
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
#TRX per BSC (*1)
#active BCSU
max #BTS / #BCF
max #logical PCU2-E
max #PS Abis chan@16
max #RTSL
max #SS7 links:64 kbps128 kbps256 kbps512 kbps1024 kbpsHSL
max #LAPD (*2)
#PCM (*3):ET16(*4)SET (*5)ETIP(*5)
1…500
1
500
5
5120
4000
842212
992
8001612
501…1000
2
1000
10
10240
8000
1684424
1984
8001612
1001…1500
3
1500
15
15360
12000
16126636
2976
8001612
1501…2000
4
2000
20
20480
16000
16168848
3968
8001612
2001…2500
5
2500
25
25600
20000
16161010510
4960
8001612
2501…3000
6
3000
30
30720
24000
16161212612
5952
8001612
(*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).
Flexi BSC maximum capacity steps in S14 hardware environment
GEMINI OVERVIEWGEMINI 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 3232 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
– 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
Abis allocation in BR product line
max11
Abis allocation in BR product line
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
Site_1
Cell 1
Cell 2
Cell 3
BTSM_1
Site_2
Cell 4
Cell 5
Cell 6
BTSM_2
BSC
PCU
sub-pool_C
sub-pool_A
sub-pool_B sub-pool_C
sub-pool_A
sub-pool_B pool_BTSM_1
sub-pool_C pool_BTSM_2
PCM-0
PCM-1
PCM-1
Site_1
Cell 1
Cell 2
Cell 3
BTSM_1
Site_2
Cell 4
Cell 5
Cell 6
BTSM_2
BSC
PCU
sub-pool_A
sub-pool_B
sub-pool_C
sub-pool_A
sub-pool_B pool_BTSM_1
sub-pool_C pool_BTSM_2
PCM-0
PCM-1
PCM-2
Integrated cross-connect or multi-drop configurationStar configuration
In case of a PCM-0 failure traffic is dynamically reallocated to sub-
pool_B of the pool_BTSM_1
– 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 sub-
slots of the faulty PCMB are disabled until the fault is repaired
• 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
– Distribution of the Abis sub-pools over different PCMB lines ensures the highest resilience against the PCMB faults
Abis allocation in BR product line
BTS1
BTS2
BTSMPCMB:0
PCMB:1
BSC
PCM fault detected by LPDLM static allocation
disabled radio channelsAbis sub-pool
Abis sub-pool
BTS1
BTS2
BTSMPCMB:0
PCMB:1
BSC
PCM fault detected by LPDLM dynamic allocation radio channels are dynamically rearranged to the operative PCMB
Abis sub-pool
Abis sub-pool
Step 1: create a new BTSM:
CREATE BTSM NAME=BTSM:0;
=> The BTSM is created
– 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
– Example:
BR Network ArchitectureDefinitions and Basic Configuration Management (1/2)
CREATE BTSM NAME=BTSM:0…199*, [OPTIONAL PARAMETERS]**; eBSC
BS-240 (base rack)
BS-240 extension racks
BTSM:0
Step 2: create a new BTS:
CREATE BTS NAME=BTSM:0/BTS:0
=> The BTS is created and assigned to the BTSM
– 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:
– Example:
BR Network ArchitectureDefinitions and Basic Configuration
Management (2/2)
CREATE BTS NAME=BTSM:0…199/BTS:0…11, [OPTIONAL_PARAMETERS]*;
eBSCBS-240 extension racks
BTSM:0
Cell 1
BTS:0
BS-240 base rack
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=...;
...
CREATE BTS NAME=BTSM:0/BTS:1,CELLTYP=STDCELL,SYSID=BB900,BCCHFREQ=17;
CREATE TRX NAME=BTSM:0/BTS:1/TRX:3,TRXFREQ=17;
CREATE TRX NAME=BTSM:0/BTS:1/TRX:4,TRXFREQ=...;
...
CREATE BTS NAME=BTSM:0/BTS:2,CELLTYP=STDCELL,SYSID=BB900,BCCHFREQ=23;
CREATE TRX NAME=BTSM:0/BTS:2/TRX:6,TRXFREQ=23;
CREATE TRX NAME=BTSM:0/BTS:2/TRX:7,TRXFREQ=...;
...
BR Network ArchitectureClassical Single Band Network
BTS:0
TRX:0
BTSM:0
TRX:3 TRX:6
BTS:1 BTS:2
TRX:1 TRX:4 TRX:7
BSC
Cell 1 Cell 2 Cell 3
siteeBSC
Cell 1
Cell 2
Cell 3
BS-240
Cell 1
Cell 2
Cell 3
BCCH 900
BCCH 900
BCCH 900
BCCH carrier layer
Each 900 MHz cell has its own BCCH carrier
TRX:2 TRX:5 TRX:8
defines the bandwidth of a cell, e.g. BB900 = PGSM
defines the type of a cell
CREATE BTS NAME=BTSM:1/BTS:0,CELLTYP=STDCELL,SYSID=DCS1800,BCCHFREQ=975;
CREATE TRX NAME=BTSM:1/BTS:0/TRX:0,TRXFREQ=975;
CREATE TRX NAME=BTSM:1/BTS:0/TRX:1,TRXFREQ=...;
...
CREATE BTS NAME=BTSM:1/BTS:1,CELLTYP=STDCELL,SYSID=DCS1800,BCCHFREQ=979;
CREATE TRX NAME=BTSM:1/BTS:1/TRX:3,TRXFREQ=979;
CREATE TRX NAME=BTSM:1/BTS:1/TRX:4,TRXFREQ=...;
...
CREATE BTS NAME=BTSM:1/BTS:2,CELLTYP=STDCELL,SYSID=DCS1800,BCCHFREQ=983;
CREATE TRX NAME=BTSM:1/BTS:2/TRX:6,TRXFREQ=983;
CREATE TRX NAME=BTSM:1/BTS:2/TRX:7,TRXFREQ=...;
...
BR Network ArchitectureClassical Dual Band Network
BTS:0
TRX:0
BTSM:0
TRX:3 TRX:6
BTS:1 BTS:2
TRX:1 TRX:4 TRX:7
BSC
Cell 1 Cell 2 Cell 3
site
BCCH carrier layer
TRX:2 TRX:5 TRX:8
BTS:0
TRX:0
BTSM:1
TRX:3 TRX:6
BTS:1 BTS:2
TRX:1 TRX:4 TRX:7
TRX:2 TRX:5 TRX:8
Cell 4 Cell 5 Cell 6
BS-240
Cell 4
Cell 5
Cell 6
eBSC
Cell 1
Cell 2
Cell 3
BS-240
Cell 1
Cell 2
Cell 3
Cell 4
Cell 6
Cell 5
BCCH 900
BCCH 900
BCCH 900
BCCH 1800 BCCH
1800
BCCH 1800
BCCH carrier layer
site
See the previous slide for the BTSM:0
- 900 MHz
- 1800 MHz
CREATE BTS NAME=BTSM:0/BTS:0,CELLTYP=DBSTDCELL,SYSID=GSMDCS,BCCHFREQ=12;
CREATE TRX NAME=BTSM:0/BTS:0/TRX:0,TRXFREQ=12;
CREATE TRX NAME=BTSM:0/BTS:0/TRX:1,TRXFREQ=975;
...
CREATE BTS NAME=BTSM:0/BTS:1,CELLTYP=DBSTDCELL,SYSID=GSMDCS,BCCHFREQ=17;
CREATE TRX NAME=BTSM:0/BTS:1/TRX:3,TRXFREQ=17;
CREATE TRX NAME=BTSM:0/BTS:1/TRX:4,TRXFREQ=979;
...
CREATE BTS NAME=BTSM:0/BTS:2,CELLTYP=DBSTDCELL,SYSID=GSMDCS,BCCHFREQ=23;
CREATE TRX NAME=BTSM:0/BTS:2/TRX:6,TRXFREQ=23;
CREATE TRX NAME=BTSM:0/BTS:2/TRX:7,TRXFREQ=981;
...
BR Network Architecture
Dual Band Standard Cell Network
BTS:0
TRX:0
BTSM:0
TRX:3 TRX:6
BTS:1 BTS:2
TRX:1 TRX:4 TRX:7
BSC
Cell 1 Cell 2 Cell 3
site
TRX:2 TRX:5 TRX:8
eBSC
Cell 1
Cell 2
Cell 3
BS-240 base rack
Cell 1
Cell 2
Cell 3
BCCH 900
BCCH 900
BCCH 900
BCCH carrier layer
separate feeder and combiner systems are
necessary
separate band specific antennas or a common
dual-band antenna
In case the greater number of TRXs is required just add (an) extension
rack(s) and create new TRXs
- 900 MHz
- 1800 MHz
Step 1: create a new BCF:
ZEFC:1,P:DNAME=OMU23;
=> The BCF is created and associated with the OMUSIG LAPD channel
– 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:
– Example:
BSS Network ArchitectureDefinitions and Basic Configuration
Management (1/6)
ZEFC:<BCF identification>,<site type>:<D-channel link set name>;*
BSC3i
Ultra Site
PCM line with OMUSIG=OMU23
BCF-1
B: 2nd generationD: Talk-familyF: PrimeSiteC: MetroSiteI: InSiteP: UltraSiteE: Flexi EDGE
– BTS (Base Transceiver Station) is a cell consisting of TRXs belonging to the same base transceiver station and operating on the same frequency band:
• 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:
– Example:
– Applicable to the standard single or dual band network
Step 2: create a new BTS:
ZEQC:BCF=1,BTS=1:CI=11,BAND=900:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;EFC:1,D:DNAME=OMU23;
=> The BTS is created in the BCF
BSS Network ArchitectureDefinitions and Basic Configuration Management
(2/6)
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>;
BSC3i
Cell 1
Ultra Site
Cell 1
PCM line with OMUSIG=OMU23
BCF-1
BTS-1
BSS Network ArchitectureDefinitions and Basic Configuration
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:
– 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
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>;
BSS Network ArchitectureDefinitions and Basic Configuration
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
– 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
common to all TRXscommon to BTS specific TRXs
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=3344;EFC:1,D:DNAME=OMU23;
ZEQC:BCF=1,BTS=2, SEG=1:CI=11,BAND=1800:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;EFC:1,D:DNAME=OMU23;
=> 1 SEG object is created and associated with 1 BCF object, 2 BTS objects are assigned to the SEG object
BSS Network ArchitectureDefinitions and Basic Configuration
Management (5/6)
BSC3i
Ultra Site
Cell 1
PCM line with OMUSIG=OMU23
BCF-1
BTS-2
BTS-1SEG-1
– Example 1: the number of TRXs in a site requires use of one cabinet only (no multi BCF control)
separate band specific antennas or a common
dual-band antenna
separate feeder and combiner systems are
necessary
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=3344;EFC:1,D:DNAME=OMU23;
ZEQC:BCF=2,BTS=2, SEG=1:CI=11,BAND=1800:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;EFC:1,D:DNAME=OMU23;
=> 1 SEG object is created and associated with 2 BCF objects, 2 BTS objects are assigned to the SEG object
BSS Network ArchitectureDefinitions and Basic Configuration
Management (6/6)
Ultra Site
BSC3i
Ultra Site
Cell 1
SYNC
BTS-2
BTS-1SEG-1
BCF-1 BCF-2
– Example 2: the number of TRXs in a site requires use of few cabinets (multi BCF control)
separate band specific antennas or a common
dual-band antenna
Create BTSPLUS in Create BTSPLUS in FlexiBSCFlexiBSC
Creating BTSPLUS in FlexiBSCCreating BTSPLUS in FlexiBSCDatabase in eBSCDatabase 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=6-5,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,
Creating BTSPLUS in FlexiBSCCreating BTSPLUS in FlexiBSCDatabase in eBSCDatabase in eBSC
•CREATE TGTBTS:NAME=TGTBTS:66,CELLGLID="460"-"00"-6244-13409,BSIC=6-0,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,HOMDOFF=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,HOMDOFF=0,<>;
Creating BTSPLUS in Flexi BSCCreating BTSPLUS in Flexi BSC Frequency bands Supported in GEMINIFrequency 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.
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).
Creating BTSPLUS in Flexi BSCCreating BTSPLUS in Flexi BSC BB HOPPING in BRBB HOPPING in BR
• 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
Creating BTSPLUS in Flexi BSCCreating BTSPLUS in Flexi BSC BB HOPPING in GEMINIBB HOPPING in GEMINI
Creating BTSPLUS in Flexi BSCCreating BTSPLUS in Flexi BSCPoints in Creating BTSPLUS in Flexi BSCPoints 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
Creating BTSPLUS in FlexiBSCCreating BTSPLUS in FlexiBSCCreate LAPDCreate LAPD
•Create OM LAPD( Lapd mutiplexing)
•Create TRX LAPD ( Lapd mutiplexing)
ZDSE:OM001:BCSU,0:62,1:64,265-31:M,2;
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
62- OM LAPD
OMU TEI=1
LAPD BIT RATE=64K
N ... NORMAL CHANNEL
C ... COMBINED CHANNEL
M ... MULTIPLEXED CHANNEL
0 ... STANDARD ABIS SETUP
1 ... SATELLITE ABIS SETUP
2 ... BTSPLUS ABIS SETUP
3 ... BTSPLUS SATELLITE ABIS SETUP
4 ... IP ABIS SETUP 1
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;
TRX LAPD controlled by the same BCSU as OM Lapd
0- TRX LAPD
ZDSE:T0012:BCSU,0:0,2:64,265-31:M,2;
Creating BTSPLUS in FlexiBSCCreating BTSPLUS in FlexiBSCCreate BCFCreate BCF
•Create BCF
ZEFC:4,X,M:DNAME=OM004:::::PORT0=267,PORT2=268,PORT4=269;
PCM connect to BTS.
PORT0/PORT2 --- the PCM interface in the BTS Site
B .... 2ND GENERATION
D .... TALK-FAMILY
F .... PRIMESITE
C .... METROSITE
I .... INSITE
P .... ULTRASITE
E .... FLEXI EDGE
X .... BTSPLUS
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
Creating BTSPLUS in FlexiBSCCreating BTSPLUS in FlexiBSCCreate BTSCreate BTS
•Create Main BTS
•Create other BTS in the Segment
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
ZEQC:BCF=4,BTS=9,SEG=8,NAME=GSMINGBO3E:CHW=2,BAND=900;
Cell id : same as the BTS NO. in eBSC database
Creating BTSPLUS in FlexiBSCCreating BTSPLUS in FlexiBSCCreate other objects :Same as creating the Flexi BTSCreate other objects :Same as creating the Flexi BTS
•Create EDAP
•Create TRX
ZESE:ID=268,CRCT=268-19&&-24,BCSU=0,PCU=6;
ZERC:BTS=4,TRX=1:GTRX=N,DAP=N,PREF=P:FREQ=27,TSC=5,PCMTSL=267-1:DNAME=T0041:CH0=MBCCH,CH1=SDCCH,CH2=TCHD,CH3=TCHD,CH4=TCHD,CH5=TCHD,CH6=TCHD,CH7=SD
CCH;
ZERC:BTS=4,TRX=4:GTRX=Y,DAP=268,PREF=N:FREQ=39,TSC=5,PCMTSL=268-3:DNAME=T0044:CH0=SDCCH,TCT=TCHD;
ZERC:BTS=4,TRX=1:GTRX=Y,ETRX=N,PREF=P:FREQ=27,TSC=5,PCMTSL=267-1: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=268-3:DNAME=T0042:CH0=ERACH,CH1=SDCCH,CH2=TCHD,CH6=EGTCH,CH7=EGTCH;
(Extended cells)
Creating BTSPLUS in FlexiBSCCreating BTSPLUS in FlexiBSCCreate other objects :Same as creating the Flexi BTSCreate other objects :Same as creating the Flexi BTS
•Create Power Control parameters
•Create Handover parameters
•Create 2G ADJ
•Create W ADJ
ZEUC:SEG=4;
ZEHC:SEG=4;
ZEAC:SEG=4::MCC=460,MNC=00,LAC=30027,CI=26261:NCC=4,BCC=5,FREQ=49:RAC=100;
ZEAE:BTS=4::MCC=460,MNC=01,RNC=1280,CI=1472:LAC=50432,SCC=25,SAC=1472,FREQ=10713;
Review of Create BTSplus in GEMINI
Multiplexing the LAPDIdentify BTS site subtypeIdentify the PCM&BPORTIdentify the CHW
Official process of BTSplus Official process of BTSplus Migration in GEMINIMigration 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 toolThe 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 measuresAbis 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 Process of BTSplus Migration in HLJHLJ
Process of BTSplus Migration in HLJProcess of BTSplus Migration in HLJPreparing
Check all the related elements are available for Migration
In SHMCC S14 pilot ,the Software of elements are:
Check RC and LMT available
Upload eBSC’s 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 SoftwareBR line BR9029
FlexiBSC S14 ??
NetAct OSS5.1 CDSet2 PCD
Process of BTSplus Migration in HLJProcess of BTSplus Migration in HLJ 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 configuration’s consistency
Process of BTSplus Migration in HLJProcess of BTSplus Migration in HLJCutoverCutover
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 can’t 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 BSCMaybe 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
Process of BTSplus Migration in HLJProcess of BTSplus Migration in HLJ
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 LAPD’s 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