GEMINI Guideline (Common Abis)

December 2010

NOKIA SIEMENS NETWORKS

NPO Sub Region Indonesia

1 Nokia Siemens Networks . All rights reserved.

Revision History

Issue Date Changes Summary

1.0 01/2011 First Issue of GEMINI Guideline
 Table of Contents :

1. GEMINI Overview
2. Dimensioning
3. Preparation
4. KPI
5. Performance Report
6. Lesson Learned From Other Projects
1. GEMINI Overview
GEMINI = GSM/EDGE Migration Network Infrastructure

The next generation of BR and BSS products is developed on a common

platform:
Former BSS and BR releases are replaced by a single common RG release
(Release GSM)

BR10.01
RG10 RG20
BSS14 ED

The functions and features of the BR BSxxx base-stations and BSS Abis
interface connected to the FlexiBSC* family are modified to enable
seamless operation of the network entities so far coming from the
different releases

* - from RG10 onwards Flexi BSC product family includes: Flexi BSC, BSC3i 1000/2000, BSC3i 660
Application Scenario

BR Abis
BSxxx BSC HC72/120 eBSC Radio
Commander
BSxxx BR Abis
BSC HC72/120 eBSC Radio Commander

BSS Abis
Flexi BTS BSC3i
NetAct
Flexi BTS BSS Abis
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
 Introduction, target and scope

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.
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)
Functional feature description

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

BTS
FlexiEDGE / UltraSiteBTS / MetroSiteBTS:
GEMINI is fully transparent for BSS-BTS families,
no impact on any of them (not only on FlexiEDGE)

BTSplus:
BTSplus product family is only supported

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
Ref. S. Basile, GEMINI master SFS (e.g. TRX-id from 24 to 32)
November 2008, version 1.0.1

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
Functional feature description

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

BSC
Flexi BSC product family is required, i.e.
BSC3i 660/1000/2000 as well as FlexiBSC

PCU2 is required
(although BSC3i can work with PCU1)

Ref. S. Basile, GEMINI master SFS

November 2008, version 1.0.1 TCSM
not affected as located behind BSC
TCSM3i is required
Functional feature description

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

Abis (towards FlexiBTS => Dynamic Abis)

GEMINI does not affect Dynamic Abis at all, its
concept is fully maintained, no adaptation to the
existing implementation needed

Abis (towards BTSplus => Dynamic Abis for BTSplus)

Abis adaptation consisting in replacement of
Flexible Abis with Dynamic Abis principles is
needed
Dynamic Abis concept is reused for CS/PS traffic
while LAPD multiplexing concept is kept for
signaling traffic
Such configuration of Abis is hereafter referred to
as Dynamic Abis for BTSplus

Ater / Gb
not affected as they are located behind BSC

Ref. S. Basile, GEMINI master SFS

November 2008, version 1.0.1
Functional feature description

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

NetAct (OMC for BSC3i and FlexiBSC):

is the master OMC that manages a meshed
network consisting of BSC3i/FlexiEDGE and BTSplus
is connected with BSC via Q3 interface

Radio Commander (OMC for eBSC and BSC1):

is the OMC connected to eBSC or BSC1 which
realize O&M functions for the network area served
by BTSplus still controlled by BR-BSC
is connected with eBSC or BSC1 via O-link

LMT (Local Maintenance Terminal):

used in GEMINI to connect to BTSplus locally
used in GEMINI to connect to BTSplus remotely
via NetAct

Ref. S. Basile, GEMINI master SFS

November 2008, version 1.0.1

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.
2. DIMENSIONING
1. Radio Capacity
TCH Channel Capacity (FR/HR)
SDCCH Capacity TCHSD (Smooth Channel Modification, BR) vs Dynamic SDCCH (Features (Basic),
BSS)
Extended CCCH (Mapped from BR)
PS Territory Dedicated PS Timeslot (CDED) & Dynamic PS Timeslot (CDEF, CMAX) Dimens ioning Radio

2. Transmission Capacity
Abis Pool (EDAP) capacity EDGE Activation
Number of LAPD used (Multiplexed)
Number of TRX / E1
Dimens ioning Abis

3. BSC Capacity
PCU capacity
Paging Load
Signaling Load (SS7, HSL)
Dimens ioning PCU
Processor Load (BSCU Load)
Gb Load
TCSM Load
3. PREPARATION
FEATURES (Applied also for BSS Flexi family)

PAFILE (BSC Control Parameter File)

Interrogate using ZEGO command, modify BSC timer parameter using ZEGT and modify BSC parameter using
ZEGP. Refer to BSC Default parameter document as Telkomsel default.

BSC Default Z EGO

parameter

PRFILE (General Parameter File)

Interrogate using ZWOI command and modify using ZWOC. Sample of commonly used settings on attachment.
00016 PREEMPT_USAGE 00FF YES
00042 DYNAMIC_SDCCH 00FF YES Z WOI

FIFILE (Feature Information Control File)

Interrogate using ZWOS command and modify using ZWOA. Deactivating EXT_UTBF_USAGE have good impact
for TBF completion SR KPI. Detail sample on attachment.
00899 EXT_UTBF_USAGE DEACTIVATED
Z WOS
LICENCE OR FEATURE INFORMATION
Interrogate using ZW7I, make sure license have enough capacity. AMR Unpacking Optimization should be
installed before rehoming, & set appropriate parameters setting to disable AMR Packing/unpacking
attempt (detail settings on Parameters section).

Z W7I
 PARAMETERS
cell number in BTS HW (CHW) (abrv : cellNumberInBtsHw) BTS Object
Should be checked before creating Common Abis database at FlexiBSC/BSC3i, changing this value
means delete-create BTS database. Below is example how to get this parameter value from RC.
Typical settings for 3 sectors are 0, 1 & 2.

Radio Commander (RC), BR

Setting on BSS parameter

CHW using this value

Get Info from RC,

Check DUVSWR
obj serving for
each Sector,
 PCM PORT ID BCF Object
Should be checked before creating Common Abis database at FlexiBSC/BSC3i, changing this value
means delete-create BCF database. BCF odject PCM PORT ID equal to BPORT number at BR. Below is
example how to get this parameter value from RC.

Radio Commander (RC), BR

MML ZEFO, BSS

BPORT
BPORT00==PCM
PCM
PORT
PORTID
ID00used
used
 T200F & T200S Timer BCF Object
Mapped from BTS object parameter at BR to BCF object at BSS. This parameter not readable via
DUMP parameter, so need to interrogate via MML ZEFO (read) & ZEFM (write). Mapping rule :
sdcchSAPI0 (BR) = T200S (BSS), facchTCHF (BR) = T200F (BSS), parameter unit is ms. Below is
sample output of ZEFO.

MML ZEFO, BSS

 max number of repetition (NY1) (abrv : maxNumberOfRepetition) BTS Object
Default value is 5. With this parameter you define the maximum number of repetitions of the
PHYSICAL INFO message during a handover that the transceiver can perform) needs to be set to
max value 35.

min int between unsucc HO attempt (MIU) (abrv : minIntBetweenUnsuccHoAttempt) HOC

Object
Default value is 3s. With this parameter you define the minimum interval between unsuccessful
handover attempts related to the same connection. Recommended settings of this parameter is 10s
to put a delay during unsuccessful handover attempt.

Minimum CPICH Ec/Io Level (MET) (abrv : minEcnoThreshold) ADJW Object

Default value is 18. Recommended setting of this parameter is 49 (disable), so there are no ISHO
attempt from 2G to 3G.

AMR Packing/Unpacking parameters.

Some parameters need adjusted to minimize packing/unpacking attempt.
BTS Object : HOC Object :
amrHoFrInHoThrDlRxQual = 0 intraHoLoRxLevLimAmrHr = 63
amrHoHrInHoThrDlRxQual = 7 intraHoLoRxQualLimAmr = 7
intraHoUpRxLevLimAmrHr = 63

Umbrella Handover BTS & ADCE Object

When Umbrella HO enabled concurrently with power budget HO, BSC HO algorithm takes layer
definition of adjacent cell into account. So Enable Umbrella Handover can be used, but not working like in
BSS.
 RACH busy threshold (RACHBT) (abrv : rachBusyThreshold) BTS Object
Default value is -109 dbm. With this parameter you define the threshold for the received signal level
during network access and handover access. A signal level exceeding this threshold is interpreted as
a busy RACH (when transmitting CHANNEL REQUEST (RACH)).
FACCH busy threshold (FACHBT) (abrv : facchBusyThreshold) BTS Object
Default value is -109 dbm. With this parameter you define the threshold for the received signal level
during network access and handover access. A signal level exceeding this threshold is interpreted as
a busy RACH (when transmitting CHANNEL REQUEST (RACH)).

RACHBT & FACHBT are valid only for BTSplus site type and its recommended to kept the previous value.
Modification of RACHBT and FACHBT may have impact on Traffic, so proper benchmarking
will help after modification.

Others Parameter Mapping

Detail mapping in attachment.

Detail Parameter Abis Mediation

Mapping
 MIXED CONFIGURATION OF CU/GCU and ECU/FCU
If CU/GCU and ECU/FCU shall be used within one BTS (segment) with EDGE, some parameters must
be set accordingly. With mixed configuration it is recommended to configure BCCH TRX on EDGE
Capable (ECU/FCU). Minimum 2 CU supporting EDGE required for EDGE activation.

General settings :

Only 1 EDGE capable CU available : 2 or more EDGE capable CU available : All EDGE capable CU available :

BTS Obj : GENA : Yes BTS Obj : GENA : Yes BTS Obj : GENA : Yes
EGENA : No EGENA : Yes EGENA : Yes
CS3/CS4 : No CS3/CS4 : Yes CS3/CS4 : Yes
hoppingMode : RF/BB hoppingMode : only RF hoppingMode : RF/BB

TRX Obj : ECU/FCU, GTRX = True TRX Obj : ECU/FCU, GTRX = True TRX Obj : GTRX = True
CU/GCU, GTRX = True CU/GCU, GTRX = False

MML ZEEI, BSS

non capable EDGE CU hw

EDGE capable CU hw
MIX CU Guideline
 ABIS MAPPING
LAPD multiplexing in GEMINI

LAPD multiplexing aims at optimizing usage of the LAPD channels by reduction of required signaling bandwidth

Up to now on Abis interface controlled by the BSC3i/FlexiBSC a dedicated LAPD signaling channel is foreseen for each
TRX

Each logical LAPD link called TRXSIG has

its own physical channel created on PCM line

In GEMINI, when BSC3i/FlexiBSC controls BTSplus, several TRXs can be multiplexed in the same LAPD (just like for
Flexible Abis), allowing all the TRXs belonging to the same site to be configured on one common physical LAPD link

Several logical LAPD links are multiplexed within

a single physical channel created on PCM line
 Abis Mapping Conversion
Below is example how to convert BR Flexible Abis to BSS Dynamic Abis (for BTSplus/Common Abis).
From BR database need to check CREATE TRX, CREATE LPDLM & CREATE SUBTSLB object for Abis Mapping
creation. For example, below is database for BTSM 68.

BTS M 68 s ample
databas e
The summaries are :

1.LAPD using TS 30. Checked from CREATE LPDLM at BR database

2.TCH timeslot at Abis using timeslot 1-3 (64 kbps), 4 (16 kbps) & 16-29 (64 kbps). Total used Abis 16 kbps
timeslot for TCH are 69 TS. Checked from CREATE SUBTSLB at BR database.

3.LAPD timeslot need to be created at the same timeslot at BSC database (BSS) while rehome to FlexiBSC family.
Changing LAPD timeslot requires site visit & object locking.

4.No need to map TCH timeslot from BR and no need to define dedicated timeslot for TRXSIG. TRXSIG & OMUSIG
can be multiplexed at LAPD timeslot.

5.TRX Configuration is 3/4/4. Checked from CREATE TRX at BR database.

6.CS3/CS4 & EDGE requires Abis pool (DAP/EDAP) to be created at BSS Dynamic Abis (for BTSplus/Common Abis)
Here is Abis Mapping result for BTSM 68:
 Another example for BTSM 5, TRX configuration is 2/3/0 and using 2 LAPD at timeslot 29 &30. Here is
the result :

BTSM 5 s ample
databas e
 OMUSIG & TRXSIG
At sample below, the fist LAPD (TS 31) shared for OMUSIG, signaling TRX 1, 2, 5, 6, 9 & 10, while the
second LAPD (TS 30) shared for signaling TRX 3, 4, 7, 8, 11 & 12.
 In BSS database, OMUSIG need to be created at the same timeslot like before in BR. Below is example
how to get this parameter value from RC. Changing this value means delete-create OMUSIG at BSS
database.
Interrogate at BSS using MML ZDTI:::PCM=[ET Number];. SAPI=62 for OMUSIG, SAPI=0 for TRXSIG.

Radio Commander (RC), BR

Active OAM Standby OAM

MML ZDTI, BSS

OMUSIG,
Active
ActiveOAM
OAMusing
using first
firstLAPD
LAPD TS 31
(TS
(TS31)
31)in
inBR.
BR.so,
so,ininBSS,
BSS,
OMU
OMUcreated
createdat
atTS
TS31 31also
also

TRXSIG, TS
30 & 31
 DATAFILL TEMPLATE (Manual Database Creation)

BTS datafill Template

Datafill Template

Abis Mapping Template

GEMINI Abis
Mapping Template

PCR Template

PCR Template CLI for Updating

ADJC
 4. KPI & Performance Report
Comparison (before x after migration) must be done using only recommended KPIs.

Possibly changed with new formula

GEMINI (Common DAILY

Abis ) Formula PERFORMANCE REPORT
5. Lesson Learned
Known Limitation
MA list must have a maximum of 51 channels.
Maximum TRX per BTSM reduced from 48 to 32.
Only 32 neighbor cells will be supported per cell, instead of e.g. BR range 64
MultiBCF concept
Traffic reason HO to 3G not supported
Detail for supported/not supported features in attachment :

GEMINI Features

Lesson learned from TSEL project other project (separate files) :

GEMINI Maumere
Les s on Learned
 Thank You

29 Nokia Siemens Networks . All rights reserved.