Anda di halaman 1dari 51

Gemini Overview

Soc Classification level


1 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Agenda of the Presentation

General
Motivation
Gemini features
Gemini Application scenarios
Gemini Overview - Technical implementation
BSS Network architecture
Object definitions
BCF
BTS
SEG
Gemini Planning tasks

Soc Classification level


2 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GSM/EDGE RG Release Roadmap [7]

Motivation
feature evolution for BR customers
feature evolution for BR customers migrating to FlexiBSC with Flexi
EDGE / Flexi Multiradio BTS / BTS plus

Gemini Features
BS2xx@FlexiBSC family
Packet TRS for UltraSite / BTSplus

Soc Classification level


3 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GSM/EDGE RG Release Roadmap
RG10 RG20 RG25 RG30
Available Ready For Contract Study Item Study items
Voice and Data Voice and Data Voice and Data Voice and Data
Wideband AMR Orthogonal Sub Channel OSC support for AMR FR PS HO
Tandem Free Operation for AMR High Symbol Rate Downlink ** OSC support for Ultra Site Precise Paging
A5/3 Ciphering
High Symbol Rate Uplink ** OSC support for VAMOS
SDCCH and PS Data Channels on DFCA TRX
Merged P- & E-GSM900 Interworking and Network Evolution AQPSK with VAMOS 2 handset
Dual Carrier in Downlink
AMR HO Signalling Optimisation
Individual Carrier LA for DL DC RF Sharing GSM LTE Earthquake and Tsunami warning system
AMR Unpacking Optimisation Tandem Free Operation for NB-AMR A5/4 Ciphering
105km Extended Cell 2G BTS* Interworking and Network Evolution Transport Interworking and Network Evolution
105km Extended Cell for GPRS/EDGE* LTE System Information Packet Abis aggregation over TDM QoS interworking with LTE
PCU2 Acceleration 2G 3G interworking improvements Flexible MCPA TX Power Pooling
Extended CCCH* SIGTRAN over A-interface O&M, Performance Management and
Paging Coordination*
A over IP Serviceability
Extended BCCH*
O&M, Performance Management and Real time call tracing
Interworking and Network Evolution Serviceability
Multi-Operator BSS Site solutions
Flexi BTS Autoconnection
IMSI based Handover Multicontroller BSC
Fast BSS Restart
Load Reporting via Iur-g* Dynamic PCU2 Pooling
ISHO with TD-RNC over Iur-G* Abis Delay Measurement
RF Sharing GSM-WCDMA* Cositing with BS2xx
Transport
O&M, Performance Management and IPSec for O&M Link
Serviceability Packet Abis VLAN Traffic Differentiation
Energy Optimized TCH allocation
Secure remote MMI Ethernet OAM support
Energy Saving Package for BS2xx
Energy Saving Mode for BCCH TRX Packet Abis Auto Commissioning
Automatic EDAP Reallocation in PCU
2G TRX Automatic Power Down Packet Abis IP network measurement
OSI over TCP/IP CMAS Support for BSS
Packet Abis Security Improvements
Site solutions CMAS Support
Advanced Speech Call Items (ASCI)
Flexi BSC Site solutions
GSM-R standardisation adaptations
Integrated IP card for BSC and TCSM * Flexi BSC Capacity Evolution
Flexi Multiradio BTS * TCSM3i Capacity Evolution
BS2xx@Flexi BSC family * FlexiPacket Radio Connectivity
Virtual (multiple TRAUs in one) eTRAU) Transport
Transport
Packet Abis over IP/ Ethernet
IP/Eth E2E Connectivity
Packet Abis over TDM
Packet TRS for UltraSite / BTSplus * late feature
Advanced Speech Call Items (ASCI) **depending on MS support/availability
Soc Classification level ASCI Cell reselection-Introduction
4 Nokia Siemens Networks of7 new
Dec 2009/Raimo
SI10bis Ahosola
BS2xx@Flexi BSC product family RG10ED

Flexi BSC for BTSplus, Flexi EDGE and UltraSite EDGE

Minimized Controller hardware in the network


Centralized control of all Base Stations
Enables smooth evolution
Several simultaneous Abis applications:
Dynamic Abis
BTSplus (BS2xx@FlexiBSC)
UltraSite EDGE
Flexi EDGE
UltraSite EDGE
Abis over IP (PWE)
Packet Abis over TDM (RG20) Flexi BSC
E1/T1/FB
Packet Abis over IP/Ethernet (RG20) product family
BTSplus

E1/T1
E1/T1
TDM Network STM1/OC-3

FlexiEDGE

Soc Classification level E1/T1/FB


5 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
RG20
Packet TRS for UltraSite / BTSplus
Installed base Evolution with Flexi System Module

Integrated IP/Ethernet connectivity with CESoPSN

Cost effective transport media Integrated ETH


for all interfaces
Enables smooth upgrade to EDGE II, OSC (Abis, Ater, A)

by MultiBCF in co-location

UltraSite EDGE

Packet Switched ETH


Network
E1

ETH
Flexi BSC

Feature ID(s): BSS21443


Soc Classification level
6 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Note: See external IP / Ethernet solution with A-1200 in RG10
GEMINI Application scenarios
Technical implementation

Soc Classification level


7 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI Application Scenarios
Application Scenario (1/3)

BR Abis
BSxxx BSC HC72/120 eBSC Radio Commander

BR Abis
BSxxx BSC HC72/120 eBSC Radio Commander
BSS Abis
Flexi BTS BSC3i
NetAct
BSS Abis
Flexi BTS Flexi BSC*
Product
BSS Abis/LAPDmux
BSxxx Family

UltraSite BTS MetroSite BTS

No HW change necessary to introduce BSS Abis at BRxxx base stations


FlexiBSC provides high capacity to a network and adds flexibility
BSxxx, FlexiBTS, UltraSite BTS and MetroSite BTS can be fully utilised
NetAct serves as common management system and reduces OPEX
* - from RG10 onwards Flexi BSC product family includes: Flexi BSC, BSC3i 1000/2000, BSC3i 660
Soc Classification level
8 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI Application Scenarios
Application Scenario (2/3)

BSS region

BR region
Source: GSM guidance to protect our installed base, Manfred Rau, 2008

Soc Classification level


9 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI Application Scenarios
Application Scenario (3/3)
Boundaries between the
networks disappear

Flexi
BSC

FlexiBSC is able to replace, e.g.


Capacity is relocated and more than one BSC120 which
transmission optimised means reduction of complexity,
transmission costs, footprint and
power consumption

Source: GSM guidance to protect our installed base, Manfred Rau, 2008

Soc Classification level


10 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Gemini Overview
Technical implementation

Soc Classification level


11 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI overview [2]
Introduction, target and scope

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

BTSplus product family FlexiBSC product family

Flexi BSC product family is a general term for all


BSC3i versions upgradeable to Flexi BSC configuration.
These are:
BSC3i 660
BSC3i 1000
BSC3i 2000
Flexi BSC

Please note that the limits


on the right are related to
BR product.
For the limits related to
GEMINI please refer to
here.

Soc Classification level


12 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI overview
Introduction, target and scope

Related programs
GEMINI concept is delivered within RG10 system program
RG10 is the NSN first common harmonized GERAN system program release
BSS and BR programs/roadmaps are discontinued and will be replaced with the new
consolidated one (beginning from RG10)
RG10 is based on BSS14/BSS14ED and BR10.01

SW requirements for GEMINI and migration paths towards RG10


GEMINI is supported in RG10 MP load
BSS releases earlier than S12 must be upgraded to BR releases earlier than BR9 must be upgraded to
either S12 or S13 first and next to RG10 either BR9 or BR10 first and next to RG10

BSSx...BSS11.5 BR7, BR8


RG10
BSS12 BR9
GEMINI
BSS13 BR10
Upgrade to RG10 is possible from BSS12 and BSS13 GEMINI allows migration of BSxx
from eBSC/BSC1 product (running with BR10 or BR9)
to FlexiBSC product (running with BSS14/BSS14ED)

Soc Classification level


13 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI overview
Functional feature description

Network Architecture in GEMINI (1/5): GERAN Elements


BSxx BTS
BSxx
FlexiEDGE / UltraSiteBTS / MetroSiteBTS:
BSxx
BSxx GEMINI is fully transparent for BSS-BTS families,
Flexi no impact on any of them (not only on FlexiEDGE)
Flexi BTSplus:
BTSplus product family is only supported
BR-LMT BTS configuration limits in GEMINI:
Ab Ab Ab
is- Ab is -BS Ab is- Ab
BR is- is BS is-
BR S( -BS S BS
*) S( S
*)

eBSC BSC3i

Abis-BSS (*)
O-link
BSC3i point of view:
BSS Abis applies apart from e.g. Q3
HO and Power Control issues,
which cannot be adapted due to BR-LMT
FlexiBTS/UltraSiteBTS/MetroSiteBTS limits are
BSxx constraint
not affected but
RC NetAct the ranges of TRX-id and cell-id must be
Ref. S. Basile, GEMINI master SFS adjusted in BSC3i due to introduction of GEMINI
November 2008, version 1.0.1
(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
Soc Classification level
usage of up to 16 FlexCU
14 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI overview
Functional feature description

Network Architecture in GEMINI (2/5): GERAN Elements


BSxx BSC
BSxx
Flexi BSC product family is required, i.e.
BSxx
BSxx BSC3i 660/1000/2000 as well as FlexiBSC
Flexi
PCU2 is required
Flexi (although BSC3i can work with PCU1)

BR-LMT
Ab Ab Ab
is- Ab is -BS Ab is- Ab
BR is- is BS is-
BR S( -BS S BS
*) S( S
*)

eBSC BSC3i

Abis-BSS (*)
BSS Abis applies apart from e.g.
O-link Q3
HO and Power Control issues,
which cannot be adapted due to BR-LMT
BSxx constraint

RC NetAct

Ref. S. Basile, GEMINI master SFS


November 2008, version 1.0.1

TCSM
not affected as located behind BSC
TCSM3i is required

Soc Classification level


15 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI overview
Functional feature description

Network Architecture in GEMINI (3/5): BSC interfaces


BSxx Abis (towards FlexiBTS => Dynamic Abis)
BSxx
GEMINI does not affect Dynamic Abis at all, its
BSxx
BSxx concept is fully maintained, no adaptation to the
Flexi existing implementation needed
Flexi

Abis (towards BTSplus => Dynamic Abis for


BR-LMT
BTSplus)
Ab Ab
Abis adaptation consisting in replacement of
is- Ab is Ab Ab
BR is- -BS Ab is- is-
BR S( is - BS BS
*) BS S S
S(
*) Flexible Abis with Dynamic Abis principles is
BSC3i
eBSC needed
Dynamic Abis concept is reused for CS/PS traffic
Abis-BSS (*)
BSS Abis applies apart from e.g.
HO and Power Control issues,
O-link Q3 while LAPD multiplexing concept is kept for
which cannot be adapted due to
BSxx constraint
BR-LMT signaling traffic
RC NetAct
Such configuration of Abis is hereafter referred to
as Dynamic Abis for BTSplus
Ref. S. Basile, GEMINI master SFS
November 2008, version 1.0.1

Ater / Gb
not affected as they are located behind BSC

Soc Classification level


16 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI overview
Functional feature description

Network Architecture in GEMINI (4/5): O&M system


BSxx NetAct (OMC for BSC3i and FlexiBSC):
BSxx
is the master OMC that manages a meshed
BSxx
BSxx network consisting of BSC3i/FlexiEDGE and
Flexi BTSplus
Flexi is connected with BSC via Q3 interface

BR-LMT
Ab Ab
Radio Commander (OMC for eBSC and BSC1):
is Ab
is the OMC connected to eBSC or BSC1 which
is- Ab -BS Ab is- Ab
BR is- is BS is-
BR S( -BS S BS
*) S( S
*)
realize O&M functions for the network area served
eBSC BSC3i
by BTSplus still controlled by BR-BSC
Abis-BSS (*)
is connected with eBSC or BSC1 via O-link
BSS Abis applies apart from e.g.
O-link Q3
HO and Power Control issues,
which cannot be adapted due to BR-LMT
LMT (Local Maintenance Terminal):
BSxx constraint

RC NetAct
used in GEMINI to connect to BTSplus locally
Ref. S. Basile, GEMINI master SFS
November 2008, version 1.0.1 used in GEMINI to connect to BTSplus remotely
via NetAct

In the network controlled by both BSC1/eBSC and BSC3i/FlexiBSC, where during migration BSC(BR) are
replaced by BSC(BSS), RC is not needed anymore. NetAct serves as common management system and
reduces OPEX.
Soc Classification level
17 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI overview
Functional feature description

Network Architecture in GEMINI (5/5): summary


Flexible Abis
BTSplus BSC1 / eBSC Radio Commander

Flexible Abis
BTSplus BSC1 / eBSC Radio Commander

Dynamic Abis
FlexiBTS
FlexiBSC NetAct
family product

BTSplus Dynamic Abis


Dynamic Abis

UltraSite BTS MetroSite BTS

No HW change necessary to introduce Dynamic Abis at BTSplus base station


FlexiBSC product family provides high capacity and flexibility
BTSplus and UltraSite BTS can be fully utilized
NetAct serves as common management system and reduces OPEX
Ref. PLM, RG Release secures Customer Investment,
November 2008: modified by author

Soc Classification level


18 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
GEMINI overview
Functional feature description

BSC3i impacts
The adaptation required to support GEMINI is mainly addressed to the BTSplus side
(a new) BTSplus mediation layer is supposed to take over adaptation activities related to GEMINI

however, some changes in BSC handling are also necessary; these are related to the
following topics:
impacts on BSS info model (e.g. new BTS type, range of TRX-id extended)
=> refer to https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/407567011
LAPD multiplexing
=> refer to https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/408629334
support for Handover and Power Control
=> refer to https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/407567011
behavior of extended cells
=> refer to https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/407567011
impacts on PM data collection and online tracing
=> refer to https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/407567011
increase of the max number of TRXs per BTS
=> refer to here

Soc Classification level


19 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture [3a]

Soc Classification level


20 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Definitions and Basic Configuration
Management [3a]

Soc Classification level


21 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture
Definitions and Basic Configuration 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>;*
B: 2nd generation
D: Talk-family BSC3i
Example: F: PrimeSite
C: MetroSite
I: InSite
Step 1: create a new BCF: P: UltraSite
E: Flexi EDGE
ZEFC:1,P:DNAME=OMU23; BCF-1
=> The BCF is created and associated
with the OMUSIG LAPD channel Ultra Site

* - for the information on how to configure LAPD channels please


refer to slide 21
Soc Classification level
PCM line with OMUSIG=OMU23
22 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture
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 BTS-1
Created in the BSS database using the following syntax in the
command line:
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 BCF-1
344;EFC:1,D:DNAME=OMU23;
=> The BTS is created in the BCF Ultra Site

Applicable to the standard single or dual band network


PCM line with OMUSIG=OMU23
Soc Classification level
23 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture
Definitions 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:
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

Soc Classification level


24 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture
Definitions 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

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

Soc Classification level


25 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture
Definitions and Basic Configuration Management (5/6)
separate band specific
Example 1: the number of TRXs in a site requires use of antennas or a common
dual-band antenna
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
44;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=3 SEG-1 BTS-1
344;EFC:1,D:DNAME=OMU23;
=> 1 SEG object is created and associated with 1 BCF object, 2 BTS separate feeder and BTS-2
combiner systems
objects are assigned to the SEG object are necessary

BSC3i

Cell 1

BCF-1

Ultra Site

Soc Classification level PCM line with OMUSIG=OMU23


26 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture
Definitions and Basic Configuration Management (6/6)
separate band specific
Example 2: the number of TRXs in a site requires use of antennas or a common
dual-band antenna
few cabinets (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
44;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=3
344;EFC:1,D:DNAME=OMU23; SEG-1 BTS-1
=> 1 SEG object is created and associated with 2 BCF objects, 2 BTS
BTS-2
objects are assigned to the SEG object

SYNC
BSC3i

Cell 1

BCF-1 BCF-2

Ultra Site Ultra Site

Soc Classification level


27 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Basic Network Architectures [3a]

Soc Classification level


28 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture
Classical Single Band Network
Classical single-band network structure:
BSC Cell 3
BCCH 900
Cell 1
BCCH 900
site
BCF-1 Each 900 MHz cell has its
own BCCH carrier

BTS-1 BTS-2 BTS-3


BCCH 900
Cell 2
TRX-7 BCCH
TRX-1 TRX-4
carrier layer

TRX-2 TRX-5 TRX-8

TRX-3 TRX-6 TRX-9 BSC3i

Cell 1 Cell 2 Cell 3


Cell 1

In the BSS database a logical cell is represented by Cell 2


the BTS object Cell 3
A site (a physical BTS cabinet) is represented in the
database by the BCF object Ultra Site

Note: The creation of the SEG object is NOT required

Soc Classification level


29 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BSS Network Architecture
Classical Dual Band Network
Classical dual-band network structure: BCCH 900
Cell 3
BSC BCCH 900
Cell 6 Cell 1
BCCH
site site Cell 4
1800
Each 900 MHz cell has its BCCH
BCF-1 BCF-2 1800
own BCCH carrier

BCCH
Each 1800 MHz cell has 1800
BTS-1 BTS-2 BTS-3 BTS-1 BTS-2 BTS-3 its own BCCH carrier Cell 5
Cell 2
Each cell has its own list
TRX-1 TRX-4 TRX-7 TRX-1 TRX-4 TRX-7 BCCH 900
of neighbours

TRX-2 TRX-5 TRX-8 TRX-2 TRX-5 TRX-8

TRX-3 TRX-6 TRX-9 TRX-3 TRX-6 TRX-9

Cell 1 Cell 2 Cell 3 Cell 4 Cell 5 Cell 6 BSC3i


Cell 1 Cell 4

In the BSS database a logical cell is represented by Cell 2 Cell 5


the BTS object Cell 3 Cell 6
Each site (a physical BTS cabinet) is represented in
the database by its own BCF object Ultra Site Ultra Site

Note: The creation of the SEG object is NOT required

Soc Classification level


30 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Common BCCH Control [3a]

Soc Classification level


31 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Common BCCH Control
Introduction
Common BCCH control allows integration of resources of different frequency
bands in a single logical cell
TRXs of different frequency bands are configured in the same cell by letting them
share a common BCCH frequency allocated to one of the frequency bands used in
the cell
Each logical cell is represented by a segment (the SEG object) consisting of the
resources (TRXs) of different frequency bands grouped by the BTS objects
If the resources of several base stations (physical cabinets) are combined within
the same cell the multi BCF control must be activated => the common BCCH
control is then a specific case of the multi BCF control
Supported by the Talk-family, UltraSite, Flexi EDGE and MetroSite base stations

Soc Classification level


32 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Common BCCH Control
Network Architecture (1/2)
Common BCCH control network structure:
BSC Cell 3
BCCH
900 Cell 1
site - 900 MHz BCCH
BCF-1 900
- 1800 MHz

BTS-1 BTS-2 BTS-3 Each segment has the BCCH


BTS-4 BTS-5 BTS-6 BCCH carrier from one of 900
the frequency bands
TRX-1 TRX-3 TRX-4 TRX-6 TRX-7 TRX-9 Cell 2

TRX-2
SEG-1 SEG-2
TRX-5 SEG-3
TRX-8

Cell 1 Cell 2 Cell 3

BSC3i
Cell 1

In the BSS database a logical cell is represented by the Cell 2


SEG object Cell 3
Band specific parameters are now represented by the
BTS object associated with the SEG object Ultra Site

A site (a physical BTS cabinet) is represented in the


database by the BCF object
Soc Classification level
33 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Common BCCH Control
Network Architecture (2/2)
Common BCCH control network structure with the multi-BCF control:
BSC Cell 3
BCCH
900 Cell 1
site - 900 MHz BCCH
BCF-1 BCF-2 900
- 1800 MHz

BTS-1 BTS-2 BTS-3 Each segment has the BCCH


BTS-4 BTS-5 BTS-6 BCCH carrier from one of 900
the frequency bands
TRX-1 TRX-4 TRX-7 TRX-10 TRX-13 TRX-16 Cell 2

TRX-2 TRX-5 TRX-8 TRX-11 TRX-14 TRX-17


SEG-1 SEG-2 SEG-3 SYNC
TRX-3 TRX-6 TRX-9 TRX-12 TRX-15 TRX-18

Cell 1 Cell 2 Cell 3 BSC3i


Cell 1

In the BSS database a logical cell is represented by the Cell 2


SEG object Cell 3
Band specific parameters are now represented by the
BTS object associated with the SEG object Ultra Site Ultra Site

A site (a physical BTS cabinet) is represented in the


database by the BCF object
Soc Classification level
34 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Multi BCF Control [3a]

Soc Classification level


35 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Multi BCF Control
Introduction
Multi BCF Control allows combining resources of several physical base
stations into a single logical cell
Increases the Talk family BTS and MetroSite BTS cell capacity up to 24
TRXs, the UltraSite BTS and Flexi EDGE BTS cell capacity up to 36 TRXs
without the necessity of defining an extra BCCH channel
Allows the gradual deployment of EDGE into the GSM networks => EDGE
can be implemented in the Talk family cells by expanding them with the
UltraSite or Metrosite BTSs which have EDGE capable TRXs
The BSC supports the multi BCF control in the Talk family BTS, UltraSite
BTS, Flexi EDGE BTS and MetroSite BTS
The BSC accepts up to 36 TRX objects (physical TRXs) and 32 BTS
objects in a single SEG object (a logical cell)

Soc Classification level


36 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Multi BCF Control
Configuration Guidelines
The following combinations of BTS cabinets are supported with the multi BCF
control:

BTS cabinet BTS cabinet Max number BTS cabinet Max number of
(master BCF) cabinets in the chain (BCF) TRXs in a BCF
UltraSite UltraSite 9 UltraSite 12
MetroSite MetroSite 3 MetroSite 12
UltraSite FlexiEDGE 3+6, 2+7 or 1+8 FlexiEDGE 24
FlexiEDGE FlexiEDGE 9

Preconditions before setting up the multi BCF control:


The synchronisation between the BTS sites (physical cabinets) is kept
Abis lines are connected to the added BTS site (the new physical cabinet, e.g.
UltraSite)
LAPD links are created for the added site*
The segments (SEG objects) are created in the BSS database see slide 38

* - for the information on how to configure LAPD channels please refer to slide 21

Soc Classification level


37 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Multi BCF Control
Network Architecture
Multi-BCF control network structure:
BSC Cell 3
BCCH
900 Cell 1
site - non-EDGE capable BCCH
BCF-1 BCF-2 900
- EDGE capable

BCCH
BTS-1 BTS-2 BTS-3 BTS-4 BTS-5 BTS-6 900
Cell 2
TRX-1 TRX-4 TRX-7 TRX-10 TRX-13 TRX-16

TRX-2 TRX-5 TRX-8 TRX-11 TRX-14 TRX-17


SEG-1 SEG-2 SEG-3 SYNC
TRX-3 TRX-6 TRX-9 TRX-12 TRX-15 TRX-18

Cell 1 Cell 2 Cell 3 BSC3i


Cell 1

In the BSS database a logical cell is represented by the Cell 2


SEG object Cell 3
Parameters associated with specific functionalities are
represented by the BTS object Talk BTS Flexi EDGE

A site (a physical BTS cabinet) is represented in the


database by the BCF object
Soc Classification level
38 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Gemini Planning Tasks
Task during the Migration

Soc Classification level


39 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Tasks during the Migration - overview
The main activities required to
NW assessment
successfully re-home selected
BS2xx to FlexiBSC family BSC
Cluster definitions

Feature mapping

BSC DB conversion

BSC DB completion

BTS site re-homing

Cluster verification

Soc Classification level


40 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Tasks during the Migration NW assessment
The existing network is assessed
NW assessment
BR configuration
BR performance
Cluster definitions
BSS performance if applicable

Feature mapping
Neighbors
Parameters
BSC DB conversion

BSC DB completion

BTS site re-homing

Cluster verification

Soc Classification level


41 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Tasks during the Migration cluster definitions
The network is divided into smaller,
NW assessment
more manageable areas, clusters
Group of sites which
Cluster definitions
forms a continuous area
can be re-homed in the same
Feature mapping maintenance window

BSC DB conversion

BSC DB completion

BTS site re-homing

Cluster verification

Soc Classification level


42 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Tasks during the Migration feature mapping
The feature mapping
NW assessment
Feature availability (SW/HW
support is checked)
Cluster definitions
Feature availability (license)

Feature mapping
The feature list for [3]
Features supported by GEMINI
BSC DB conversion
Features not supported by GEMINI

BSC DB completion
Different requirement for the same
feature is considered e.g. EGPRS
BTS site re-homing approach

Cluster verification

Soc Classification level


43 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Tasks during the Migration DB conversion
The BR DB is converted into BSS
NW assessment
format
Some planning data may be helpful
Cluster definitions in this process
Exporter tool may be used
Feature mapping Typically1) not a NPO task

BSC DB conversion

BSC DB completion

BTS site re-homing


note 1: depends heavily the future development of the
Exporter tool and the ability to use the tool for
Cluster verification actual planning tasks

Soc Classification level


44 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Tasks during the Migration DB completion
BSC DB Completion
NW assessment
The tool covers subset of all
parameters (300/1400)
Cluster definitions
e.g. the EGPRS related parameters
needs to be added
Feature mapping

the DB needs to be completed


BSC DB conversion before it is ready to be used

BSC DB completion

BTS site re-homing

Cluster verification

Soc Classification level


45 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Tasks during the Migration re-homing
BTS site re-homing
NW assessment
not a NPO task
The BS2xx SW is updated
Cluster definitions
Re-homing
The PCM lines of the BS2xx are
Feature mapping
reconnected to target BSC
The BS2xx operation is verified
BSC DB conversion within 30 min test window
Fall back to old BSC possible
BSC DB completion
NPO: The physical LAPD link
BTS site re-homing positions must be as before re-
homing to ensure the O&M link
operation. If the O&M link fails the
Cluster verification site does not come up

Soc Classification level


46 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Tasks during the Migration cluster verification
Cluster verification
NW assessment
traffic
neighbor relations
Cluster definitions
performance
Feature mapping

BSC DB conversion

BSC DB completion

BTS site re-homing

Cluster verification

Soc Classification level


47 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Gemini Planning Tasks
Other planning considerations

Soc Classification level


48 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
BS2xx Implementation Strategy

Options
There are two main strategies available. The BS2xx can be migrated to new BSC applying the existing
DB as far as possible. In this approach the DB is converted and completed according the principles
shown later in this presentation. Another approach is to treat the BS2xx as a new site and integrate it to
Flexi BSC almost as Flexi EDGE BTS. The Abis is planned according the BS2xx requirements and the
EDGE is dimensioned like in case of the Flexi BTS.

Migration (preferred option) [4]


DB conversion from existing BR-DB to BSS-DB
DB conversion tool used
Rest of the parameters planned as matching as possible

New site approach (backup option) [5]


BSS defaults used
No conversion
Planned as new site

Soc Classification level


49 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Example of manual DB conversion of BTSM20

Work split between NI and NPO teams

BR
BSC
NI Focus area

Macros INPUT OUTPUT Macros


Manual XLS XLS MML

NI Focus area NPO Focus area


Flexi
BSC

Soc Classification level


50 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola
Reference material

Network Engineering Information


https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/406502780
[1] GEMINI scenarios
[2] GEMINI Overview Planning and Dimensioning aspects
[3] Features in GEMINI
[3b] GEMINI Introduction

FlexiBSC documentation in NOLS


[4] Migrating BTSplus to the Flexi BSC product family
[5] Commissioning BTSplus at the Flexi BSC product family
[6] Monitor and measure, KPI guidelines for BTSplus migration to the Flexi
BSC product family

[7] GSM/EDGE Roadmap


https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/374616316

Soc Classification level


51 Nokia Siemens Networks 7 Dec 2009/Raimo Ahosola