features in gemini in nutshell

1 © Nokia Siemens Networks Presentation / Author / DateFor internal use

Krystian MajchrowiczNetwork EngineeringAugust, 2009

GEMINI Network Engineering InformationGSM/EDGE Migration Network Infrastructure

Features in GEMINI (in nutshell)

2 © Nokia Siemens Networks For internal use Presentation / Author / Date

GEMINI

• GEMINI master v1.0.1, Stefano Basile

• BSS BR main requirements v4.0, Jörg Monschau

• BSXX@BSC3I RRM & LAPD SFS v1.0.0, J.Hartikainen

• GEMINI Adaptation of M-plane v1.0.0, Erich Wiehart

• GEMINI Adaptation of C -, U-plane v1.0.0, Jörg Monschau

• Upgrade and Migration Procedures SFS v1.0.0, H.Hofmeister

• BSS Operability and LMT SFS v2.0.0 M. Alice Fontana

• Packet Data Service Implementation Specification in GEMINI

References (1/2)References (1/2)


GEMINI

• BS2XX@FLEXI BSC Product family BSS21469 BSC S14.1 BSC Requirements Specification v1.1.1 Harri Tervonen, Esa Tuovinen

• GEMINI Support BSC S14.1 BSS21469 BSC IR1 Implementation SpecificationTero Niemensivu, Marika Koivisto, Petri Jolanki, Juha Rimpiläinen

• GEMINI Support BSC S14.1 BSS21469 BSC IR2 Implementation SpecificationTero Niemensivu, Marika Koivisto, Petri Jolanki, Juha Rimpiläinen Ilari Sainio

• GEMINI Support BSC S14.1 BSS21469 BSC IR3 Implementation SpecificationTero Niemensivu, Marika Koivisto, Petri Jolanki, Juha Rimpiläinen Ilari Sainio\

• Migration to GEMINI from BR - Differences on BTS related features Jörg Monschau

• Feature Complex Planning Manual: CS Mobility, Handover & Power Control Eckardt Bertermann

References (2/2)References (2/2)


• Features supported in GEMINI

• BR features introduced to BSC 3i in GEMINI

• BSS features supported on BSxx with GEMINI

• BR features not supported with GEMINI

• BSS features not supported on BSxx with GEMINI

Features supported in GEMINI

ContentsContents


Features supported in GEMINIFeatures supported in GEMINI


• Concentric cells

• Hierarchical Cells Structure

• Combiner shared between 2 cells

• UL & DL Diversity

• Frequency Hopping

• UL and DL DTX

• Max CU output power configuration

• Static power reduction

• Uplink Interference Cancelation

• Channel types

• Combined TCH/SDCCH pools

• Cell Broadcast

• Ciphering

Features supported in GEMINIFeature list (1/2)Feature list (1/2)

• Tandem Free Operation

• Interference based channel assignment

• Different RLT for AMR

• Radio link failure warning

• Call drop reduction features

• Thresholds for access burst

• Handover and power control

• Reduced speech break during HO

• Derived Handover Power

• Extended Cells

• (E)GPRS

• Dual Transfer Mode

• Measurement counters


Abis features:

• LAPD multiplexing

– multiplexed OMUSIG and TRXSIG on one LAPD

– LAPD links 16kbits, and 64Kbits

– LAPD links 32 kbits

– support of up to 11 phisical LAPD links

– LAPD overload handling

• supported physical interfaces

– E1/T1 transmission system

– satellite Abis

– up to 8 PCM lines per site

– BS2xx and Flexi on same PCM line (not collocated)

• supported Abis configurations

– star configuration

– multidrop

– cross connect

• BSxx sync by 1pps signal

Features supported in GEMINIFeature list (2/2)Feature list (2/2)

This features are described

in the separate slideset:

”GEMINI overview & Access features

Abis dimensioning and planning in

GEMINI” available at:https://sharenet-

ims.inside.nokiasiemensnetworks.com

/Open/407517434


• Frequency bands supported in GEMINI:

• GSM 900,

• E-GSM,

• GSM 1800,

• GSM 1900,

• GSM 850


FFrequency bandsrequency bands


• Common BCCH for dual band cell (850/1900, 850/1800, 900/1800)

• cells may be configured having TRXs of two different frequency bands

• in BR this is done by the concept of a dual band standard cell or concentric cell

• in BSS this is configured as a Segment having two or more BTS of different frequency

band while only one BTS has a BCCH carrier. • Concentric cells

• cells may be configured having TRXs with a max output power lower than the output power on the BCCH TRX.

• The different link budget is takeninto account in assignmentprocedures and handover evaluation.Reduced output power is usedby some customer to allow tighterfrequency reuse.

• The corresponding featurein BSS is calledIntelligent Underlay Overlay(IUO) so concentric cell of BRare mapped on IUO feature

Features supported in GEMINICommon BCCH features Common BCCH features

(1/3)(1/3)


• Parameters “non BCCH layer offset” and “TRX Frequency Type” are used to define ”cell type” of BTSplus that BSC knows how to allocate a TCH.

• It is possible to configure these parameter for BTSplus with same optionality rules of Common BCCH or Multi BCF options as for other site types. These parameters are used in the BSC to recognize “cell type” of BTSplus as following:

• cell is a “dual band standard cell” if Non BCCH Layer Offset = 0 for all BTSs in a segment

• cell is a “dual band concentric cell” if Non BCCH Layer Offset <> 0 for at least one BTSs in a segment

• cell is a “standard cell” if “Trx Frequency Type” of all TRXs in a segment = 0:

• cell is a “concentric standard cell” if “Trx Frequency Type” of at least one TRXs in a segment <> 0

• This classification affects in the BTS how it maps BSC parameters to it’s own parameters. Also BSC according to cell type decides what internal HO signaling procedure to use to allocate channels in different HO scenarios.

• TCH allocation in case of “dual band standard cell”• In a ”dual band standard cell” it is assumed that operator adjusts output power of layers so that the

both BCCH and non-BCCH layers are always similarly usable. BSC allocates TCH according to current Common BCCH principles assuming that both layers are similarly usable from signal propagation point of view.

Features supported in GEMINICommon BCCH features Common BCCH features

(2/3)(2/3)



BR Parameter BSS Parameter Mapping ruleTRXAREA

object: TRX

range: NONE, INNER,COMPLETE

default: NONE The attribute specifies whether a TRX belongs to a concentric cell and to which area it belongs

trxFrequencyType

object: TRX

Range and step: 0...16, step 1

default: 0

With this parameter you define the type of the TRX's radio frequency used with the optional Intelligent Underlay-Overlay feature. Values 1..16 indicate that the radio frequency is super-reused and show the number of a super-reuse frequency group. If the type of radio frequency is regular, the value is 0.

if (BTS CELLTYP = STDCELL)

{ if (BTS is a dualBand)

{ for all TRX belong to the BCCH layer : TRXAREA = COMPLETE for all TRX different layer : TRXAREA = INNER

} else

{if for all TRX same SEGID

(trxFrequencyType) = 0

{TRXAREA = NONE}

else

if (trxFrequencyType) = 0 (default) TRXAREA=COMPLETE

else TRXAREA = INNER }}

else /* (DBSTDCELL & EXTCELL) */ TRXAREA = NONE

CELLTYP

object: BTS

range: STDCELL, EXTCELL, DBSTDCELL

default: DBSTDCELL

It specifies the type of the cell.

nonBCCHLayerOffset

object: BTS

Range and step: -40...40, , step 1

default: 0

With this parameter you define whether the predefined offset margin is used when evaluating the signal level of the non BCCH layer.

if (BTS is a dualBand)

{if (for all BTS in the segment (same SEGMID) is :

Non BCCH Layer Offset = 0)

{CELLTYP = DBSTDCELL}

else {CELLTYP = STDCELL

CONCELL= TRUE}

} else CELLTYP = STDCELL

Common BCCH features Common BCCH features (3/3)(3/3)

• in GEMINI Common BCCH features works BR like but the parameter are BSS like (IUO)

• no automatic convertion of Common BCCH cells is provided in Exporter => trxFrequencyType and nonBCCHLayerOffset parameters together with SEG/BTS must be plan appropriately in NetAct Plan Editor or NetAct RAC


• The operator may plan the usage of certain cellwithin the network with a different preference according its need (capacity, coverage)

• The hierarchical cell feature allows to prioritize certain cells in the target cell list generation process in the BTS when having decided to request an handover.

• Hierarchical cell structures for UTRAN cells are not supported in GEMINI

Features supported in GEMINIHHierarchical ierarchical CCellells Structure s Structure

(1/4) (1/4)

Macro Cell GSM1800Radio Coverage Layer 4

Umbrella Cell GSM900Radio Coverage Layer 6

Macro Cell GSM900Radio Coverage Layer 5

Micro Cell GSM900Radio Coverage Layer 3

Micro Cell GSM1800Radio Coverage Layer 2

Pico Cell GSM900Radio Coverage Layer 1


• In BR Hierarchical cell ranking flag is used to switch between two alternative ranking methodsin case of imperative HO.

• IN GEMINI HIERF was fixed to default (Rank0). This means that Rank1 is not supported

• Rank0 (Ranking Method 0):

All adjc. cells where RXLEV_NCELL(n) > RXLEVMIN(n) + Max(0,Pa) are subdivided into two sublists:

- the upper sublist consists of all NB cellswhere PBGT(n) - HO_MARGIN(n) > 0 ,

- the lower sublist consists of all NB cellswhere PBGT(n) - HO_MARGIN(n) ≤ 0.

Within each sublist the cells are sortedin increasing order of priority

Neighbour cells with the same priorityare sorted by PBGT(n) - HO_MARGIN(n).

• This ranking method is only relevant for imperative HO (except fast UL HO) and forced HOs• Rank1 (Ranking Method 1):

All adjc. cells where RXLEV_NCELL(n) > RXLEVMIN(n) + Max(0,Pa) are subdivided into two sublists:

The upper sublist consists of all neighbour cells where :RXLEV_NCELL(n) > RXLEVMIN(n) + Max(0,Pa) + levelOffsetNcell,

the lower sublist consists of all neighbour cells where: RXLEV_NCELL(n) ≤ RXLEVMIN(n) + Max(0,Pa) + levelOffsetNcell,

where evelOffsetNcell = LEVONC

Within each sublist the cells are sorted in increasing order of priority. NB cells with the same priority are sorted by PBGT(n) - HO_MARGIN(n).

Features supported in GEMINIHHierarchical ierarchical CCellells Structure s Structure

(2/4) (2/4)



BR Parameter BSS Parameter Mapping ruleHIERC

object: HAND

range: TRUE, FALSE

default: FALSE

Hierarchical Cell Handover indicates whether the ranking of the target cells based on the priority layer is enabled or disabled.

enableUmbrellaHo

object: HOC

range and step: 0 - disabled, 1 – enabled

Default: 0

With this parameter you indicate whether the BTS umbrella handover is enabled.

enableUmbrellaHo

if HIERC= TRUE → enableUmbrellaHo=1

if HIERC= FALSE → enableUmbrellaHo=0

PLNC

object: ADJC

range: 0..15

default: 0

priority layer of the neighbour cell (0 highest priority; 15 lowest priority)

hcsPriorityLevel

object: ADCE


default: 3

With this parameter you define the priority level for an adjacent cell.

(hoPriorityLevel) * 2

• BR parameters mapped to BSS:

• in GEMINI all HCS related parameters are converted automatically by Exporter

HHierarchical ierarchical CCellells Structure s Structure (3/4) (3/4)



BR Parameter BSS Parameter Mapping rule

PL

object: HAND

range: 0..16

default: 0 Priority layer - if hierarchical cell handover is enabled (HIERC=TRUE) this parameter determines the priority layer of the own cell. This priority is only evaluated for the Power Budget handover decision and the traffic handover decision. The priority layers of the neighbour cells are administered in the ADJC object (PPLNC parameter).

hcsPriorityClass

object: BTS


default: 0

With this parameter you define the HCS (hierarchical cell structures) priority for the cells. 0 is the lowest and 7 is the highest priority.

hcsPriorityClass * 2

PPLNC

object: ADJC

range: 0..15

default: 0

Penalty priority layer of neighbour cell - this parameter is relevant for speed sensitive handover; it determines the temporary priority layer of the neighbour cell.

hcsPriorityClass

object: ADCE


default: 0

With this parameter you define the HCS (hierarchical cell structures) priority for the cells. 0 is the lowest and 7 is the highest priority. In the adjacent cell creation, if this parameter is not given and the SEG and the adjacent cell are in the same BSS, the value of this parameter is copied from the SEG.

hcsPriorityClass * 2


HHierarchical ierarchical CCellells Structure s Structure (4/4) (4/4)


• In GEMINI both UL and DL diversity are supported and works BR like

• UL (Receive Diversity):

– Four Branch RX diversity works BR like.

• DL (Transmit Diversity):– Time Delay Transmit Diversity works BR like (controlled by newly introduced to BSC3i

parameter)

– Antenna hopping works BR like:

▪ previously configurable (in BR) antenna hopping period parameter (ANTHOPP),which specifies how many frames are transmitted over each antenna beforethe next one is used to send the frames, was fixed in GEMINI to default-> this means that Antenna Hopping is performed after two frames were

transmitted on one antenna

▪ Additionally BR possibility to exclude the BCCH transceiver from the hopping sequence for Antenna Hopping does not exists in GEMINI (ANTHOPMOD parameter was fixed to value ALLTRX)


Diversity techniques (1/2)Diversity techniques (1/2)



• BR parameters mapped to existing BSS parameters:

• New parameter introduced to BSC3i:

BR Parameter BSS ParameterEANTHOP

object: BTS

range: TRUE, FALSE

default: FALSE

This parameter indicates whether Antenna Hopping is enabled or disabled for the BTS..

antennaHopping object: BTS

range:

antenna hopping not used (N) (0),

antenna hopping used (Y) (1)

default: 0

With this parameter you define whether antenna hopping is used in the BTS or not.

Diversity techniques (2/2)Diversity techniques (2/2)

Parameter Description

TX Diversity Time Shift object: BTS

range:

0 (DISABLED), 1 (NO EXEPTION), 2 (SCH EXEPTION), 3 (BCCH TRX TS0 EXEPTION), 4 (BCCH TRX EXEPTION) 0 default: 0MML command: EQM, EQO

MML Abbreviated Name: TXDIV

TX Diversity Time Shift (txDiversityTimeShift) – with this parameter you switch TX diversity time between coverage mode (enabled) and standard mode (disabled). You also configure time slots or logical channels which are excluded from being sent in TX Diversity Time Shift mode. Parameter is valid only for BTSplus.


• In GEMINI Uplink Interference Cancellation Techniques works BR like.This means that:

– Uplink Interference Cancellation (UIC) and Improved UIC are supported(more info at: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/394701699 and at https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/353433384)

– BSS Uplink Interference Cancellation Technique - Space Time Interference Rejection Combining (STIRC) is not supported on BSxx sites


Interference cancellation techniquesInterference cancellation techniques


• Both baseband and synthesized hopping types are supported in GEMINI

• BR parameters mapped to existing BSS parameters:


BR Parameter BSS Parameter Mapping ruleHOPMODE

object: BTS

range: BBHOP, SYNHOP

default: BBHOP

With this parameter you define the frequency hopping mode of the BTS.

hoppingMode

object: BTS

Range: Non-hopping (0), Baseband hopping (1), Radio Frequency hopping (2)

default: 0

·

If HOPMODE= BBHOP -> hoppingMode =1;

else hoppingMode =2

HSN

object: FHSY

range:0..63

default: 0

With this parameter you define hopping sequence number

hoppingSequenceNumber1

object: BTS

range : 0 ..63

Default: 0

With this parameter you define whether cyclic or random hopping is used in BB hopping group 1 and in RF hopping.

hoppingSequenceNumber2

With this parameter you define whether cyclic or random hopping is used in BB hopping group 2 and in RF hopping.

If HOPMODE= SYNHOP

hoppingSequenceNumber1 = hsn

If HOPMODE = bbhop : hoppingSequenceNumber1 = hsn for FHSY assosiated with channel0

If HOPMODE= SYNHOP

hoppingSequenceNumber2 = 0

If HOPMODE = bbhop : hoppingSequenceNumber2 = hsn for FHSY assosiated with channels 1-7

Frequency hopping (1/2)Frequency hopping (1/2)



BR Parameter BSS Parameter Mapping ruleMAIO

object: CHAN

range:0..63

With this parameter you define mobile allocation index offset

channel0Maio

object: TRX

range : 0 ..63

Mobile allocation index offset (MAIO).channel1Maio .. channel7Maio

channel0Maio = MAIO

take MAIO from TRX but if it is NULL then from 1st channel of that TRX

channel1Maio = MAIO


channel7Maio = MAIO


• BR parameters mapped to existing BSS parameters

• in BR hopping system (FHSY) is defined per TSL and up to 11 FHSYs per cell are allowed

• in BSS one hopping system can be configured in one BTS but it is possible to have multiple BTS (up to 32) per segment (cell)

• In case of more then one FHSY in the cell, Exporter does not provide automatic conversion => parameters and SEG/BTS must be plan appropriately in NetAct Plan Editor or NetAct Radio Access Configurator

Frequency hopping (2/2)Frequency hopping (2/2)


• In GEMINI both UL and DL DTX works BSS like• In DL DTX is enabled in the BSC3i by modifying the value of the appropriate PAFILE

parameter: ZEGP:18:1;

Downlink DTX is disabled by default.

• In UL DTX is configurable via BSC3i parameter:


Discontionues TransmissionDiscontionues Transmission

BR Parameter BSS ParameterDTXUL

object: BTS

range:MAYFSHNH, SHLFSHNH, SHNFSHNH, MAYFMAYH, SHLFSHLH, SHNFSHLH ; default: SHLFSHLH

Specifies whether DTX shall be used by the MS

dtxMode

object: BTS; range : 0..2; default: 2

Defines how the MS uses DTX. Meaning of the values:

0 -> MS may use DTX

1 -> MS shall use DTX

2 -> MS shall not use DTX

• Currently Exporter does not provide automatic conversion => dtxMode to be set in NetAct Plan Editor or NetAct Radio Access Configurator according to the rule:

• dtxMode = 1 if DTXUL = SHLFSHLH;

• dtxMode = 2 if DTXUL =SHNFSHNH;

• else dtxMode = 0


• Maximum Carrier Unit output power configurable on cell level

• A CU configuration is called inhomogeneous, if the maximum output power of at least 2 CUs differs by more than 2 dB

• This value (2dB) is exceeded in case of a BS82II, if a cell is equipped with FlexCU and any other CU-Type (CU, GCU, ECU). This is because the FlexCU output power is restricted to maximum 45 dBm vs ~ 48dBm of ECU

• in GEMNI as well as in BR cells with inhomogeneous carrier unit configurations are supported:

– BS82II with FlexCU and CU/ECU/GCU

– cell with old 1800/1900 MHz CUs (45.3 dBm output power) and ECU V2/3/3a of the same frequency band

• configuration attribute on cell level is used, which has to be set to an appropriate value, if the cell is equipped with inhomogeneous CUs. This new attribute (for BSC3i) acts like a 'selective' static power reduction and adjusts the output power of stronger CUs to the weakest CU.

Features supported in GEMINIMax CU output power Max CU output power configurationconfiguration

(1/2)(1/2)


GEMINI


Carrier Unit Configuration object: BTS

range:

0 (HOMOGENEOUS),1 (CU_FLEXCU_BS82II D),2 (CU_ECU_DCSPCS)

default: 0MML command: EQM, EQO

MML Abbreviated Name: CUCONF

Carrier Unit Configuration (carrierUnitConfiguration) - with this parameter you indicate which types of carrier units are used within the BTSplus serving the cell. This information must be considered for power aspects, as different carrier unit types differ in their transmission power levels.

This parameter should be set in case of a cell with an inhomogeneous carrier unit configuration to ensure that the maximum output power difference between the carrier units is below 2 dB.

MML Range:

0 = (homogeneous)

This value is used when the carrier unit configuration is homogeneous or shall be considered as homogeneous. All carrier units use the maximum output power, which is provided by the hardware. No adaptation of the output power is performed. This implies, that output power differences greater than 2 dB will be accepted. This setting corresponds to the current system behavior.

1 = (cu_flexcu_bs82II)

This value is used when the cell is served by a BS82II and has an inhomogeneous carrier unit configuration with FlexCU and CU/ECU/GCU.

2 = (cu_ecu_dcspcs)

This value is used when the cell has an inhomogeneous carrier unit configuration with old 1800/1900 MHz CUs (45.3 dBm output power) and ECU V2/3/3a of the same frequency band. Parameter is valid only for BTSplus site type.

• New parameter introduced to BSC3i

Max CU output power Max CU output power configurationconfiguration (2/2)(2/2)


• The output power of each TRX can be adjusted separately to be reducedby 0 till 18dB in order to meet the required output power without the need to use external attenuation equipment.

• also energy consumption is reduced

• some TRX of the CELL can be configured as low power TRX to form a concentric cell (super reused frequency of the TRX in IUO feature)

• BR parameter mapped to BSS:


Static power reductionStatic power reduction

BR Parameter BSS Parameter Mapping rulePWRRED

object: TRX

range: 0..9 step 1 (2dB)

default: 6

txPwrMaxReduction - specifies the number of 2 dB steps the TX power should be reduced from the maximum transmit power, for tuning the cell coverage.

bsTxPwrMax

object: POC

range: 0..30 step 2 dB

default: 0

This parameter is used to identify the maximum transmission power of the BTS as an attenuation from the peak power of the TRX in GSM 800 and GSM 900 bands

bsTxPwrMax1x00

object: POC

range: 0..30 step 2 dB

default: 0

This parameter is used to identify the maximum transmission power of the BTS as an attenuation from the peak power of the TRX in GSM 1800 and GSM 1900 bands

Read value X accoring to band (X = bsTxPwrMax, or X = bsTxPwrMax1x00)

and set

PWRRED =

If X <=9

txPwrMaxreduction = X

else

txPwrMaxreduction = 9




BR Parameter BSS ParameterCHTYPE

object: CHAN

range: 1 (TCHFULL), 2(SDCCH), 3(MAINBCCH),

4(MBCCHC), 5(CCCH), 6 (SCBCH), 7(BCBCH),

8(TCHF_HLF), 9 (TCHSD)

no defaultThis parameter - defines the logical channel combination mapped onto the physical channel.

channel<n>Type (n: number of TSLS 0..7) object: TRX

Range: TCHF (0), TCHH (1), TCHD (2), SDCCH (3), MBCCH (4), MBCCHC (5), MBCCB (7), Not allowed in CH0 (8), Not In Use (9), ERACH (10),

Not allowed in CH0 (13), EGTCH (14), Not allowed in CH0 (15)

default: TCHF (0)

With this parameter you define the logical channel combination that has to be mapped onto the basic physical channel.

Channel typesChannel types

• All available in BR channel configurations are supported in GEMINI and converted by Exporter according to the mapping table:

• In case of extended cellsEGTCH must be setmanualy

• CCCH can be configuredonly on TSL 0 of BCCHTRX (more than 1 CCCHis not supported)

• PBCCH is not supported


• Dynamic SDCCH/TCH reconfiguration feature is available on both BR and BSS system

• BSS “Dynamic SDCCH" is a feature in which timeslots are configured to work either as TCH/FR or SDCCH.

• the number of timeslots configured as Dynamic SDCCH plus the one SDCCH pure is however limited up to four per TRX due to memory and CPU load limitations in both BR and BSS

• In GEMINI BSS Dynamic SDCCH feature replaces BR Smooth Channel Modification feature - > this means no need to configure TCHSD channels anymore


Dynamic SDCCHDynamic SDCCH


• All ciphering algorithms: A5/0, A5/1, A5/3 are supported and work BSS like (including A5/1 improvements)

• A5/3 ciphering in case of BTSplus

– In BSS system possibility of A5/3 usage on the radio path depends among others on SW and HW of the BTS:

▪ SW: The similar procedure as for Flexi EDGE (support depends on SW version of BCF)

▪ HW: All TRXs could use A5/3 (no relation to BB unit HW capability as it was e.g. for Ultrasite or Metrosite)


In BSS system strongest common A5 ciphering algorithm in BSC is selected according to: information from MSC, parameters in BSC, TRX’s capability, MS capability.

CipheringCiphering


• AMR Link Adaptation works like in BR

• BSC3i parameters are used:

• Existing BSC3i parameters like: codec set, thresholds for LA switching and histeresis are used for LA in GEMINI

Features supported in GEMINIAMR Link Adaptation AMR Link Adaptation

(1/2)(1/2)

BSS Parameter BR Parameter Mapping ruleslowAmrLaEnabled

object: BSC

range: 0, 1

default: 1

With this parameter you define the AMR link adaptation (LA) mode within the BSS.

AMRACMRDL

object: BTS

range: 1..31 (unit 1 CMR)

default: 5

Handover averaging parameters for AMR CODEC MODE REQUESTs - defines the size of the averaging window for Codec Mode Requests (CMR's) received from the MS during an AMR call.

AMRWBACMRDL

object: BTS

range: 1..31 (unit 1 CMR)

default: 5

Handover averaging parameters for AMR CODEC MODE REQUESTs - defines the size of the averaging window for Codec Mode Requests (CMR's) received from the MS during an AMR call.

AMRACMRDL = AMRWBACMRDL = 1 if slowAmrLaEnabled=0

else

AMRACMRDL = AMRWBACMRDL = 3 if slowAmrLaEnabled=1


• Existing in BR possibility to adjust hardcoded UL LA thresholds is not supported in GEMINI anymore (existing parameters AMRLKAT and AMRLKATWFS are mapped fixed to 100 what means adjustment by 0 dB)

Features supported in GEMINIAMR Link Adaptation AMR Link Adaptation

(2/2)(2/2)


• Tandem Free Operation (TFO) for WB-AMR is supported by BR with a proprietary solution (more info at: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/391945452 )

which uses only in-band signalling in TRAU frames whereas BSS applies the 3GPP compliant solution with dedicated Abis messages (more info at: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/397576352)

• In GEMINI the solution for TFO for WB-AMR is BSS like

• In addition, TFO for NB-AMR (not supported in BR) is implemented in GEMINI (works BSS like)


TFOTFO


• In GEMINI channel selection criteria works like in BSS

• Based on UL interference measurements on idle timeslots channel is allocated

• BSS reports also UL interference levels for active SDCCH and TCH channels (assuming that UL DTX is in use on the channel and there are enough silent periods).

– The BTS can measure the UL interference of an active channel when UL DTX is used

– BTS actually measures both the active channel UL RX level and the interference.

– When there are twelve or more silent TDMA burst periods, the active channel interference measurement result is considered to be valid for a HR TCH during one SACCH multiframe

– For FR TCH at least four TDMA bursts are required - this is always the case since the measurement is done from the four idle TDMA frames on a FR TCH ; this definition is based on the fact that idle slots are spread evenly throughout the SACCH multiframe, thus averaging away the effect of fading).

• Interference measurements on active channels are used to decide which channel to select on next allocation of a TCH/SDCCH (otherwise it could happen that channel is idle only for a short time without having received idle measurements)


Channel allocation based on interference (1/Channel allocation based on interference (1/33))


• In GEMINI, BSxx is aligned to BSS implementation sending interference levels relative to SDCCH and TCH channels too.

• 3rd measurement report is sent for an SDCCH connection (assumption is that 3rd MR has already some valid info) from that time on every n-th MR is sent. BSC uses the measurements for selecting an appropriate channel for the TCH

• In BR interference measurements on the idle traffic channels can be disabled by setting INTCLASS=FALSE.

• In GEMINI BTS permanently performs UL interference measurements on the idle and active channels and reports the measurement results in form of “RF Resource Indication” (INTCLASS mapped fixed to TRUE)

• Interference band thresholds and averaging parameters are mapped from existing BSC3i parameters; Exporter converts them automatically


Channel allocation based on interference (Channel allocation based on interference (22//33))


Parameter DescriptionSDCCH Measurement Report Sending

object: BTS

range:0 (radio measurements not transmitted (N), 1 (radio

measurements transmitted (Y) default: 0MML command: EQM, EQO

MML Abbreviated Name: SMREPS

SDCCH Measurement Report Sending (sdcchMeasReportSending), with this parameter you define whether or not the SDCCH radio measurements have to be transmitted on the A-bis interface. Parameter is valid only for BTSplus.

Interval Measurement Report Sending

object: BTS

range: 1..254, step 1 default:8

MML command: EQM, EQO

MML Abbreviated Name: IMREPS

Interval Measurement Report Sending (intervalMeasReportSending) - with this parameter you specify the granularity in which the radio measurements have to be transmitted on the A-bis interface in case they are enabled (e.g 8 = 1/8). Parameter is valid only for BTSplus site type


Channel allocation based on interference (Channel allocation based on interference (33//33))

BR Parameter BSS Parameter Mapping ruleRFRSINDP

object: BTS

range: 1-254 (SACCH multiframe)

default: 60

rfResourceIndicationPeriod - this parameter defines the sending rate of the ”RF Resource Indication” message from BTS to BSC

interferenceAveragingProcessAverPeriod

object: BTS

range: 1...32, step 1

default: 6

With this parameter you define the number of SACCH multiframes over which the averaging of the interference level in the unallocated time slots is performed.

RFRSINDP = interferenceAveragingProcessAverPeriod + 16 sec


• Radio Link Timeout

• In BR different settings of RLT per codec type for UL and DL are allowed by means of Service Group related PC parameters

• Since in GEMINI Service Group related PC and HO parameters features is not supported different RLT settings for AMR FR, AMR HR and non-AMR calls are supported as implemented in BSS: channel specific SI6 containing the RLT values is used by both the MS and the BTS to check the link quality -> as the consequence it is not possible to set different RLT valuesfor UL and DL

• Additionally in GEMINI it is not possible any more to set different thresholds for hopping and non hopping layer (as the consequence of removed concept of SG related PC parameters )

Features supported in GEMINICall Drop Mechanisms Call Drop Mechanisms

(1/3)(1/3)


• Existing BSS parameters are used to define RLT:


(2/3)(2/3)

Parameter DescriptionRadio Link Timeout

object: BTS

range: 4...64 SACCH, step 4 SACCH

default: 20 SACCHMML command: EQG, EQO

MML Abbreviated Name: RLT

Radio Link Timeout (radioLinkTimeout) with this parameter you define the maximum value of the radio link counter expressed in SACCH frame (480ms).

AMR Radio Link Timeout

object: BTS



MML Abbreviated Name: ARLT

AMR Radio Link Timeout (radioLinkTimeoutAmr) with this parameter you define the maximum value of the radio link counter expressed in SACCH frame for AMR calls.

AMR HR Radio Link Timeout

object: BTS



MML Abbreviated Name: AHRLT

AMR HR Radio Link Timeout (radioLinkTimeoutAmrHr) with this parameter you define the maximum value of the radio link counter expressed in SACCH frame for AMR calls.


• Radio link failure and radio link failure warning

• The BTS monitors the link by observing the decoded SACCH blocks.

• After a certain number of SACCH (PCRLFTH) have not been decoded (the power is increased to the maximum output power radio link failure warning) . This feature in BR is called ”Power Control Indication due to link failure warning”. There is no counterpart in BSS14

• This feature was fixed to be always used on BSxx in GEMINI (EPWCRLFW fixed to TRUE)

• Moreover the configurable in BR threshold (PCRLFTH) in GEMINI was fixed to 18.


(3/3)(3/3)


• Temporary Overpower on FACCH/SACCH• BR feature named “Temporary overpower” (NE description can be found at:

https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/353428962 ) is available in BSS side as “FACCH Power Increment”

• The feature activation in BR is based on a O&M parameter that specifies the codecs for which the feature has to be enabled

• In BSS FACCH Power Increment is supported only for AMR

• In GEMINI TOP works like in BR, thus also all the other codecs are supported in BR way to maintain the complete feature for BR customers

• Therefore BSxx activates the feature taking into consideration the relevant O&M attribute as in BR which was introduced in BSS too

Features supported in GEMINIFeatures for Call drop reduction Features for Call drop reduction

(1/5)(1/5)


Enable Temporary Overpower object: BTS

range:

Bit 0: TCH_AFS, Bit 1: TCH_AHS, Bit 2: TCH_EFS, Bit 3: TCH_FS ,

Bit 4: TCH_HS, Bit 5: TCH_WFS,


MML Abbreviated Name: ETOP

Enable Temporary Overpower (enableTemporaryOverpower) - with this parameter you determine whether TOP (Temporary Overpower) is enabled or disabled on cell basis for the specified codec type. MML Range:

0: disabled; 1: TCH_AFS; 2: TCH_AHS; 4: TCH_EFS; 8: TCH_FS

16: TCH_HS; 32: TCH_WFS;

You can give 0 or 1-6 values at the same time by using the wild card character &.

Parameter is valid only for BTSplus site type.


• FACCH /SACCH repetition• FACCH/SACCH repetition is available both in BSS and BR side (NE description can be

found at: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/353428962

and at https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/390619674 )

• The feature activation in BR is based on a O&M parameter that specify the codecs for which the feature has to be enabled.

• In GEMINI R-FACCH/SACCH works like in BR

• In BSS only AMR is supported so with GEMINI all the others codecs are supported in BR way to maintain the complete feature for BR customers.

• For all the other codec types BSxx activates the feature taking into consideration all the related O&M attribute as in BR which are introduced in BSS too.


(2/5)(2/5)


• FACCH /SACCH repetition – new parameters



Repeated FACCH In UL object: BTS

range:




MML Abbreviated Name: RFUL

Repeated FACCH In UL (repeatedFacchInUl) - with this parameter you determine whether repeated FACCH in uplink is enabled or disabled on cell basis for the specified codec type

MML Range:





Repeated FACCH In DL object: BTS

range:




MML Abbreviated Name: RFDL

Repeated FACCH In DL (repeatedFacchInDl) - with this parameter you determine whether repeated FACCH in downlink is enabled or disabled on cell basis for the specified codec type

MML Range:





Features for Call drop reduction Features for Call drop reduction (3/5)(3/5)


• FACCH /SACCH repetition – new parameters



Apply Repeated FACCH object: BTS

range:

0 (Apply R-FACCH is disabled (N)),

1 (Apply R-FACCH is enabled (Y)) default: 0MML command: EQM, EQO

MML Abbreviated Name: ARF

Apply Repeated FACCH (applyRepeatedFacch) - with this parameter you enable applying repeated FACCH on any command frames. Parameter is valid only for BTSplus.

Features for Call drop reduction Features for Call drop reduction (4/5)(4/5)


• Compressed HO/ASS CMD (BR8.0) vs AMR signaling optimization (BSS14)

• In GEMINI it is BSC who decides how HO/ASS CMD looks like

• Therefore HO CMD is not reduced and the length of ASS CMD can be optimized according to BSS14 feature ”AMR HO signaling optimization”.

For more details on this feature please refer to https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/400823185


(5/5)(5/5)


• In BSxx there are 2 different thresholds used for RACH access burst and handover access burst

Features supported in GEMINIThresholds for access bursts Thresholds for access bursts

(1/2)(1/2)

RXLEV of RACH burst > RACHBT?

RXLEV of HO ACC burst > FACHBT?

RACH access scenario

Intercell HO ACCESS scenario

more info can be found at:https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/390618652



Parameter DescriptionFACH Busy Threshold

object: BTS

range: 0..127, step 1 default: 109MML command: EQM, EQO

MML Abbreviated Name: FACHBT

FACH Busy Threshold (fachBusyThreshold) - with this parameter you define the threshold for the received signal level during handover access. A signal level exceeding this threshold is interpreted as a busy FACCH (Handover ACCESS). Parameter is valid only for BTSplus site type

RACH Busy Threshold

object: BTS

range: 0..127, step 1 default: 109MML command: EQM, EQO

MML Abbreviated Name: RACHBT

RACH Busy Threshold (rachBusyThreshold) - with this parameter you define the threshold for the received signal level during network access. A signal level exceeding this threshold is

interpreted as a busy RACH. Parameter is valid only for BTSplus.

Thresholds for access bursts Thresholds for access bursts (2/2)(2/2)

• Since RACHBT and FACHBT functionallity is not implemented in BSS new 2 thresholds were introduced to BSC3i in GEMINI

• New parameters:


• Handover algorithm is located in the BSxx - BTS evaluates HO criteria and triggers HO (generates HO CONDITION INDICATION message with target cell list)

• There is no handover algorithm running in BSC3i (BSC only selects the candidate from target cell list and allocates channel)

• BSC3i can only request BSxx to start a handover if needed e.g. due to congestion

• even though Measurement Result (MR) messages are not needed for the HO purposes the BSC is able to receive them from BTS and update supported statistics and traces as well as to deliver all needed radio measurement data for positioning system and real-time road traffic monitoring system just like with Flexi EDGE BTS.

• As HO algorithm is in the BTSplus, the BSC needs to use BTSplus specific signaling to start intra-and inter-cell HOs.


Handover Handover algorithmalgorithm


• Level and quality handover

– In GEMINI due to function split the evaluation algorithm for the handover criteria is like in BR while BSC3i handles the evaluation and selection of the given target cells.

– The parameters required for the BTS handover evaluation are provided by BSC3i

– All parameters related to level/quality HOs are converted by Exporter automatically

– Since in BSS there is one flag enabling level handover margin for both level HO and quality HO it is not possible in GEMINI to have it enabled for one of them only

• Distance handover

– In GEMINI BSS like behaviour was implemented

– Depending on setting of MS Distance Behaviour, after the predefined TA threshold is exceeded:

▪ call is released immediately

▪ handover due to distance is attempted within predefined time period, after that time if HO is unsuccessful call is released

▪ handover due to distance is attempted; no possibility for call release due to distance

– Only flag enabling distance HO is set automatically by Exporter; the other 2 parametersto be planned in Netact Plan Editor or Radio Access Configurator

Features supported in GEMINIEmergency hEmergency handoverandovers s

(1/2)(1/2)



Parameter DescriptionEnable MS Distance Process

object: HOC

range: distance process is disabled (N) ==> 0

distance process is enabled (Y) ==> 1

default: distance process is disabled (N)==> 0

MML command: EHC, EHG, EHO

MML Abbreviated Name: EMS

Enable MS Distance Process (enableMsDistance) - with this parameter you indicate whether the BTS - MS distance process is enabled.

MS Distance Threshold Param MS Max

object: HOC

range: 0...63 bits, step 1 bit

default: 63MML command: EHC, EHD, EHO

MML Abbreviated Name: MSR

MS Distance Threshold Param MS Max Range (msDistanceHoThresholdParamMsRangeMax) - the parameters compare the MS-BS distance with the maximum allowed distance

MS distance behaviour

object: BSC

range: 0..60, 255, step 1

default: 255

MML command: EEM, EEO

MML Abbreviated Name: DISB

MS distance behaviour (msDistanceBehaviour) with this parameter you define the executions allowed after the Timing Advance has exceeded the threshold.

Meaning of the values:

0 (release immediately)

1 (1 s to try handover, release if handover does not succeed)

…60 (60 s to try handover, release if handover does not succeed)

255 (no release, only handover attempts)

• Existing BSS parameters used for distance HO:

Emergency hEmergency handoverandovers s (2/2)(2/2)


• In GEMINI due to function split the evaluation algorithm for the handover criteria is like in BR while BSC3i handles the evaluation and selection of the given target cells.

• The parameters required for the BTS handover evaluation are provided by BSC3i

• UMTS better cell HO is not supported in GEMINI

• All parameters related to this HOs are converted by Exporter automatically


BBetter Cell Handoveretter Cell Handover


• In BR this type of HO was introduced for Hierarchical Cell Structures (HCS). In this implementation certain cells are penalized in the process to find appropriate handover target cells depending on the time an MS is reporting this cell.

• In BSS a feature with similar name: ”MS Speed Detection” exploits specific information coming from the layer 1 receiver to estimate the MS speed

• In GEMINI BR like solution is supported

• BSC3i provides required parameters


Features supported in GEMINISSpeed peed ssensitive Handoverensitive Handover

(1/3)(1/3)



BR Parameter BSS Parameter Mapping ruleDPBGTHO

object: ADJC

range: FALSE, TRUE

default: FALSE

Dynamic power budget handover - this attribute indicates whether the speed sensitive handover decision algorithm is enabled or not. This attribute enables/disables the mobile speed sensitivity of the following handovers: - Power Budget handover from a GSM serving cell to a GSM neighbour cell - Power Budget handover from a GSM serving cell to an UMTS neighbour cell - Sufficient UMTS coverage handover from a GSM serving cell to an UMTS neighbour cell.

msSpeedDetectionState

object: HOC

Range and step 0...100, step 1

default: 0

With this parameter you indicate the method used for MS speed detection algorithm.

0 → FALSE

!= 0 → TRUE

MICROCELL

object: ADJC

range: FALSE, TRUE

default: FALSE

This parameter determines whether the adjacent cell is regarded as a 'microcell'. Only if this parameter is set at TRUE the 'speed sensitive handover' algorithm will be in effect for this neighbour cell.

gsmMicrocellThreshold

object BSC

Range and step 5...39 dBm, step 2 dBm

Default: 33 dBm

With this parameter you define the microcell size by means of the maximum transmission power of the MS in a GSM cell. If you set the parameter value at 43

dBm, the division of cells into macrocells and microcells is not in use.

Rely on a new internal prm which BSC3i calculates according to

mstxpwrmax and

gsmMicrocellThreshold

if (msTxPwrMaxGSM (ADJC, - for GSM, 850) or msTxPwrMaxGSM1x00 (ADJC, - for DCS, PCS) <= GSMmicrocell_threshold){ microcell = true;}

SSpeed peed ssensitive Handoverensitive Handover (2/3)(2/3)



BR Parameter BSS ParameterHOMDTIME

object: ADJC

range: 0..255 [SACCH frames]; default: 0

HO margin delay time - this parameter is relevant for speed sensitive HO; it specifies the time an immediate HO request is delayed when a power budget HO is requested.

fastMovingThreshold

object: ADCE

Range and step 0...255 [SACCH frames], step 1, default: 0

Fast moving threshold- defines the limit which is compared with the identification counter (fast moving MS) in the NB cell. If the limit is exceeded, the call is handed over from the macrocell to the best microcell.

HOMSOFF

object: ADJC

range: 0..127 [dB], default: 0

HO margin static offset - this parameter is only relevant for speed sensitive handover; it specifies the static offset by which the handover margin is increased as long as the timer HOMDTIME runs

msSpeedThresholdNx

object: HOC

Range and step 1...32, step 1, default: 6

MS Speed Threshold Nx - the parameter is used in threshold comparison between the averaged MS speed and the upper and lower speed thresholds. Nx is the total number of averages to be taken into account before the decision is possible. The meaning of this parameter is totally different for BTSplus in GEMINI than in standard BSS

HOMDOFF

object: ADJC

range: 0..127 [dB], default: 0

HO margin dynamic offset - this parameter is only relevant for speed sensitive handover; it specifies the dynamic offset by which the handover margin is reduced after expiry of HOMDTIME

msSpeedThresholdPx

object: HOC

Range and step 1...32, step , default: 3

MS Speed Threshold Px - the parameter is used in threshold comparison between the averaged MS speed and the upper and lower speed thresholds. Px is the number of averages out of total averages that have to be lower/higher than the threshold, before a handover due to MS speed is possible. The meaning of this parameter is totally different for BTSplus in GEMINI than in standard BSS

SSpeed peed ssensitive Handoverensitive Handover (3/3)(3/3)


• Fast Uplink Handover (FUHO) evaluates a potential handover need based on uplink measurements with a very short averaging period and predefined neighbour cells.

• In BR FULHO mechanism is decoupled from power control• In GEMINI BR like solution is implemented• The needed parameters are mapped from the corresponding BSS feature

(Deep droping edge)


Features supported in GEMINIFFast ast UUplink plink HHandoverandover

(1/3)(1/3)



BR Parameter BSS ParameterEFULHO

object: HAND

range: TRUE, FALSE

default: FALSE

Enable Fast Uplink handover - this attribute allows to enable or disable the Fast Uplink Handover.

enaFastAveHo

Range and step: method is disabled (N) (0), method is enabled (Y) (1)

Default: method is disabled (N) (0)

Enable Fast Averaging HO - with this parameter you indicate whether the Fast Handover Measurement Averaging Method is enabled after handovers and in the new TCH..

THLEVFULHO object: HAND

range: 0..63dB

default: 8

Level threshold for fast uplink handover - this attribute defines the receive signal strength threshold for an inter-cell fast uplink HO decision.

ddeThresholdsLevRxLevel

Object: HOC

Range and step 0...63 dB, step 1 dB

default: 10 dB

Threshold Deep Dropping EDGE - the parameter is used for comparing the size of the signal drop for triggering the rapid field drop handover

FFast ast UUplink plink HHandoverandover (2/3)(2/3)

If RxLev< THLEVFULHO then target cell list is generated based on the shorter avg window (ALEVFULHO) according to formula:

RXLEV_NCELL(n) > RXLEVMIN(n) + Max(0, Pa) + FULRXLVMOFF(n)

where: Pa = MS_TXPWR_MAX(n) – P ; P - power capability of the MS; MS_TXPWR_MAX(n) - max allowed MS transmit power in the NB cell

FULRXLVMOFF - Fast uplink handover RxLev minimum offset, this parameter is used during the target cell list generation process and represents an additional offset which is added to the handover minimum criterion to qualify an adjacent cell as a target cell for fast uplink handover. In GEMINI this parameter was fixed to default (6dB).



BR Parameter BSS Parameter Mapping ruleALEVFULHO

object: HAND

format: averaging period - DTX weighting factor

range: 1..31 (averaging period) - 1..3 (DTX weight. factor)

unit: 1 SACCH multiframe=480ms

default: 2-1

Handover averaging parameters for fast uplink handover decision - defines two averaging parameters for signal strength measurements, used for fast uplink handover decision. The first field defines the averaging window size (that is smaller than the normal window size), the second one, indicates the averaging weighting factor

modifiedAveWinNCell object: HOC ; Range and step 1...3, step 1 ;default: 2

Modified Averaging Window - with this parameter you indicate the new averaging window size of the serving cell and adjacent cell. A new averaging window is employed after the deep dropping edge in serving cell signal is detected.

No modified weighting factor in BSS

modifiedAveWinNCell = averaging period of ALEVFULHO

weighting factor of ALEVFULHO is set to fixed default value of 1.

FFast ast UUplink plink HHandoverandover (3/3)(3/3)


• For decompression/unpacking loadis not considered (quality only)

• In GEMINI (as well as in BSS) compression/decompression HO for non-AMR calls is not supported

• Existing in BSS mechanisms to prevent unpacking in poor radio conditionsare not supported in GEMINI as it is BTS that starts unpacking

Features supported in GEMINICCompression ompression / / decompression decompression HO HO

(1/3)(1/3)

– Load evaluation for triggering packingworks BSS like

– BSC (when load criteria is fulfilled) instructs BTSplus to start evaluation of the quality for candidates for packing/compression

– Abis load is not considered as the load criterion for compression HO anymore

– Quality evaluation for candidates for compression works BR like (BSC3i provides parameters mapped from packing HO)

• In GEMINI packing/compression HO is supported in that way that:



Lower Limit For FR TCH Resources object: BSC

range: 0..100% step 1%

default: 40%


MML Abbreviated Name: HRL

Lower Limit For FR TCH Resources (btsLoadDepTchRateLower),

the parameter controls the TCH channel rate determination on the BSC level according to the cell load in traffic channel allocation. With this parameter you define the lower limit for the percentage of free full rate resources. Full rate TCHs are allocated until the number of free full rate resources is reduced below the value of the parameter. The half rate resources are then allocated

Upper Limit For FR TCH Resources

object: BSC


default: 60%


MML Abbreviated Name: HRU

Upper Limit For FR TCH Resources (btsLoadDepTchRateUpper), the parameter controls the TCH channel rate determination on the BSC level according to the cell load in traffic channel allocation. With this parameter you define the upper limit for the percentage of free full rate resources. Full rate TCHs are allocated when the number of free full rate resources exceeds the value of the parameter.


• Existing BSC3i parameters used for compression/decompression HO

CCompression ompression / / decompression decompression HO HO (2/3)(2/3)

• Load thresholds are to be set manually (no automatic conversion)



Lower Limit For FR TCH Resources object: BTS


default: 100%

MML command: EQM, EQQ

MML Abbreviated Name: FRL

Lower Limit For FR TCH Resources (btsLoadDepTchRateLower),

with this parameter you define the percentage of full rate TCH resources that must be available for traffic channel allocation. Full rate TCHs are allocated until the number of free full rate resources is reduced below the threshold given in the parameter. The half rate resources are then allocated.

Upper Limit For FR TCH Resources

object: BTS


default: 0%

MML command: EQM, EQQ

MML Abbreviated Name: FRU

Upper Limit For FR TCH Resources (btsLoadDepTchRateUpper), with this parameter you define the percentage of full rate TCH resources that must be available for traffic channel allocation. Full rate TCHs are again allocated when the number of the free full rate resources increases above the threshold given by the parameter.


• Existing BSC3i parameters used for compression/decompression HO

CCompression ompression / / decompression decompression HO HO (3/3)(3/3)

• Any other quality thresholds related to compression/decompression are automaticaly converted by Exporter


• Intersystem handover due to sufficient coverage is the only HO type to 3G cells available in GEMINI

• Since in most of BR networks SC HOs is not used it requires total replanning of GEMINI networks interworking with 3G

• In BR BTS triggers a SC HO from GSM cell to UMTS neighbour cell if the MS/UE receives the 3G neighbour cell with an RSCP (or Ec/No, depending on the configured reporting quantity) value that is regarded as 'sufficient'.

• In GEMINI SC HO is triggered based on Ec/No only (the lowest Ec/No value for the 'sufficient' criterion is defined via a corresponding database parameter)

• Threshold for SC HO is automatically converted by Exporter


Intersystem handoverIntersystem handovers (1/2)s (1/2)


• In GEMINI reporting can be configured only BSS style: Ec/No reporting. Minimum RSCP criteria can be used to force th UE/MS to report only these 3G cells with RSCP> threshold

• Intersystem handovers are supported in GEMINI to FDD (also 900, 850) but not to TDD

• 32 Neighbour cells to be defined – this number is reduced in GEMINI from 64 (in BR)

• In case of standard 2G HOs (e.g. Level, Quality, PBGT HOs) UMTS cells are no more evaluated as the HO candidates in GEMINI

• No hierarchical cell structures for UTRAN cells are supported in GEMINI

• BSS feature Inter System Handover for CS due to traffic is not supported in GEMINI

• The optional Service Handover IE included in ASS/HO REQ specifies whether a handover to UMTS should be, should not be or shall not performed. The value is taken from the Assignment Request message (in call setup) or Handover Request (in incoming HO) message sent from MSC to BSC and is further forwarded from BSC to BSxx. It is used in BSxx to enable/disable handovers to UTRAN. Handovers due to sufficient UMTS coverage could take place if the value of Service Handover IE is empty or equal to SHOULD.


Intersystem handoverIntersystem handovers (2/2)s (2/2)


• Both MSC initiated Traffic Reason HO (TRHO) and BSC controlled Traffic Reason HO are supported in GEMINI

• In BSS as well as in GEMINI it's recommended not to enable BSC-initiated Traffic reason HO (AMH feature) and MSC-inititated Traffic reason HO simultaneously

– Technically it is possible to use both TRHOs at same time and it's up to operator to use them simultaneously,

– two simultaneous and separate TRHO algorithms may work not so reasonable together.

• In BSC iniitiate TRHO and provides the parameters mapped from AMH feature – these parameters are converted automaticaly by Exporter. Then BTS evaluates TRHO candidates in the same way as in BR

Features supported in GEMINITraffic Traffic HandoverHandover

(1/2)(1/2)


• Following BR parameters used in TRHO procedure were fixed in GEMINI:



TRFHOT

object: BTS

range: 2..20s

default: 10s

Traffic handover timer is used for the traffic handover decision in the BTS and defines the cycle in which the BTS recalculates the dynamic traffic handover margin while traffic handover is enabled in the BTS. In GEMINI fixed to default.

TRFKPRI

object: BTS

range: TRUE, FALSE

default: FALSE

Traffic keep priority - this attribute determines whether candidate cells have to be of the same priority as the serving cell or may be of the same or higher priority. In GEMINI fixed to default.

TRFMMA

object: BTS

range: 1.. 48 dB

default: 9

Traffic handover margin maximum reduction establishes the maximum reduction for trafficHoMargin (TRFHOM). In GEMINI fixed to default.

TRFMS

object: BTS

range: 1.. 6 dB

default: 3

Traffic handover margin reduction step defines the minimum reduction for the value of the attribute trafficHoMargin (TRFHOM). In GEMINI fixed to default.

BHOFOT

object: ADJC

range: 1..120s

default: 30s

Back handover forbidden timer for traffic handover is used to prevent back handover towards the originating cell for Traffic and Power Budget reasons when the previous handover was performed for traffic reasons. In GEMINI this BR parameter was mapped fixed to 60 s

Traffic Traffic HandoverHandover (2/2)(2/2)




FHORLMO

object: ADJC; range: 0..24

default: 6

Forced handover received level minimum offset parameter - this parameter is used by the HO decision algorithm to determine whether a neighbour cell is regarded as suitable target cell for forced HO or not. It enhances the minimum criteria defined by the attribute RXLEVMIN.

Forced Forced HandoverHandover• In GEMINI BSC3i uses Forced HO Request message to indicate to the BSxx that

a handover is needed. This procedure is used to start HO for:– Directed Retry

– O&M triggered HO

– Pre-emption

– PS territory upgrade

• Forced HO is needed for example in following features:– Forced HO due to “BSS7072 Intelligent Shutdown with Timer Control and Adjustable

Intelligent Shutdown” feature

– Forced HO due “BSS20984 Flexi EDGE Dual TRX Automatic Power Down” feature

– Forced HO due to “change of administrative state of TRX object from UNLOCKED to LOCKED”

• BSC3i supports both intra-cell and inter-cell Forced HO for BTSplus with same triggers as with Flexi EDGE BTS.

• BR parameter used in Forced HO procedure was fixed to default in GEMINI:


• Concentric Cell feature works in GEMINI like Intelligent Overlay Underlay

• Handover from inner area to complete and vice versa are supported based on the level criteria only (distance criteria is not supported anymore)

• Thresholds to trigger this HOs are mapped from IUO feature and converted by Exporter automaticaly


HandoverHandover in Concentric Cells in Concentric Cells


• In BR it is possible to disable intercell HO by setting INTERCH = FALSE;In GEMINI this parameter is fixed to TRUE and therefore this option is not possible anymore

• In BR it is possible to disable handover due to UL or DL received low level by setting RXLEVHO = FALSE;In GEMINI this parameter is fixed to TRUE and therefore this option is not possible anymore

• In BR it is possible to disable handover due to poor UL or DL RxQual by settingRXQUALHO= FALSE;In GEMINI this parameter is fixed to TRUE and therefore this option is not possible anymore

• In BR it is possible to disable GSM to UMTS handovers by setting EUHO= FALSE;In GEMINI this parameter is fixed to TRUE and therefore this option is not possible anymore

• In BR it is possible to disable Sufficient Coverage Handover to UMTS by settingEUSCHO= FALSE;In GEMINI this parameter is fixed to TRUE and therefore this option is not possible anymore

• In BR it is possible to disable advanced Compression/Decompression Handover algorithm (algorithm considers the current power control situation when deciding on whether to compress or decompress a call) by setting EADVCMPDCMHO = FALSE;In GEMINI this parameter is fixed to TRUE and therefore this option is not possible anymore


HandoverHandover limitations (1/2) limitations (1/2)


• Following BR HOs are not supported in GEMINI anymore:

– Compresion/decompression for standard FR/HR

– Enhanced pairing – intracell HO of one HR to another TSL where one HR call is already allocated

– UMTS better cell handover

– UMTS imperative handover

– Concentric cell handover based on distance criteria


HandoverHandover limitations (2/2) limitations (2/2)


• Available in BR functionallity to reduce speech break during HO called "Reduced Muting Gap During Handover” is not supported in GEMINI

• Instead BSS like feature called “DL-bi-casting” works in GEMINI

• The BSS feature, named “Dual Rate TRAU”, also supports bi-casting with changes in encoding algorithm rate: this functionality is not supported by BSxx and therefore not available in GEMINI

Features supported in GEMINIRReduceducinging speech break during speech break during

HO HO



Parameter DescriptionPWRCONF

object: PWRC

range: 1..31

unit: 2 SACCH frames

default: 2

Power confirmation interval, defines the maximum interval that the BTS will wait for the confirmation of a newly set RF power level by the MS in units of 2 SACCH multiframes. The timer administered with PWRCONF is started after a new MS power level was set. As long as this timer is running the BTS compares the received MS power level with the requested one. If the timer expires before the MS confirmed the requested power level the power control decisionprocess is resumed.

Power controlPower control• In GEMINI PC algorithm is running in BSxx

• The current PC algorithm of the BSC3i is disabled when the call is on BSxx

• BSxx runs power control independently and BSC3i only needs to send PC parameters

• Both classic and adaptive PC is supported

• UL/DL configuration attributes merged:

• BR: enableMSPowercontrol, enableBSPowerControl -> BSS: pcControlEnabled

• This means that in GEMINI or PC is disabled or enabled in both UL and DL

• Power Control for DTM

• In BSxx changes were introduced to its current implementation to fit into BSC3i realization

• All Power Control related parameters are converted automatically by Exporter

• Following BR parameter used in PC procedure was fixed to default in GEMINI:


• In BR quality thresholds for Handover and Power Controlare defined in C/I (0..20dB)

• In BSS quality thresholds for Handover and Power Controlare defined in RxQual (0..7)

• During migration process to GEMINI quality thresholds from BR(C/I thresholds) are converted to BSC3i RxQual parameters according to the following mapping table:

• In the BTS they are mapped back to C/I according to the following mapping table:

• This requires careful parameter audit after migration e.g. C/I=4 dB is converted to RxQual 7 and mapped again to C/I=1 dB => this can distort relation between parameters and as a consequence one procedureunintentionally might be triggered before another

Features supported in GEMINIFFine tuning of quality thresholds ine tuning of quality thresholds

(1/2)(1/2)


• Affected parameters:


BR name BSS name Meaning

HOLTHQUDL hoTQDlRxQual Threshold trigerring HOdue to quality

HOLTHQUUL hoTQUlRxQual

HOTHCUL amrHoFrInHoThrDlRxQual Threshold trigerring compression /packing HO

HOTHCDL amrHoFrInHoThrDlRxQual

HOTHDUL amrHoHrInHoThrDlRxQual Threshold trigerring decompression /unpacking HO

HOTHDDL amrHoHrInHoThrDlRxQual

LOWTQUAD pcLTQualDlRxQual PC threshold trigerring power increase due to quality

LOWTQUAU pcLTQualUlRxQual

UPTQUAD pcUTQualDlRxQual PC threshold trigerring power reduction due to quality

UPTQUAU pcUTQualDlRxQual

FFine tuning of quality thresholds ine tuning of quality thresholds (2/2)(2/2)


• In BSS UL power can be optimized in the handover and decrease UL interference with the feature called "Optimization of the MS power level in intra-BSC handover".

• In BSS network architecture this feature is implemented only in BSC, differently in BR architecture the power control evaluations have to be made in BTS.

•

• Due to the different functional split in handover and power control, the “Derived handover power” feature is implemented in GEMINI as in BR. More info on Derived HO Power can be found at: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/353434893

• New parameters (exactly the same as existing in BR) are introduced to BSC3i in GEMINI


Derived HO PowerDerived HO Power


• Current BR solution (pool of double timeslots to be used in the extended area irrespectively of the TS allocation to TRX) is no longer used in GEMINI. BSS approach was taken.

• Following BSS features are used for the extended cells:

• Non E-Cells related parameters are converted automaticaly. This means that planning of Extended cells need to be started from the scratch


Release Feature no. Feature nameBSS 4 4015 Extended Cell Radius BSS 6 6037 Improved Solution for Extended Cell (Talk BTS) BSS 11.5 11102 Extended Cell for UltraSite BTS BSS 13 20882 Extended Cell Range for FlexiEDGE BTS BSS 13 21274 Long Reach TSL BSS 13 20094 Extended Cell for GPRS/EDGEBSS13ED 21277 105km Extended Cell (FlexiEDGE BTS)) BSS13ED 21270 105km Extended Cell for GPRS/EDGE

Extended cellsExtended cells


• The BR implementation of (E)GPRS is completely different from BSS one

• In GEMINI BSxx has to adapt BSS solution for (E)GPRS.

• This means new Abis messages, new procedures and new PCU frame format.

• In GEMINI PS is served by PCU2 therefore (E)GPRS works like in BSS

• PS territory concept is inherited from BSS

• EDAP concept is inherited from BSS

• Link Adaptation is inherited from BSS

• In GEMINI on CU and GCU GPRS is supported but CS1 and CS2 only

• Both GPRS (CS1-CS4) and EGPRS are supported on ECU and FCU

• GPRS is also supported on extended cell

• Downlink Dual Carrier implementation in GEMINI is BSS like


PS servicesPS services (1/2) (1/2)


• All PS related parameters in GEMINI are not convertible by Exporter tool

• Therefore default values for these parameters will be used in GEMINI unless not set differently

• Since default for CDEF =1 this means that only 1 TSL will be used as default PS territory if not specified differently (while in most of the cases in BR 100% of all resources are shared dynamically between PS and CS)

• For that reason some configuration rules for PS territory in GEMINI shall be applied

– dedicatedgprsCapacity (CDED) shall be set according to settings of BR parameter: EMANPRESPRM / GMANPRESPRM

– defaultgprsCapacity (CDEF) shall be set according to the average number of used PDCH before migration to GEMINI – this average number of PDCHs can be retrieved from PM counter: mean number of used PDCHs with active TBF NALLPDCH[6]

• Additionally EDAP and all other PS related parameters (e.g. cell reselection, NCCR, NACC) need to be planned


PS servicesPS services (2/2) (2/2)


• In GEMINI DTM works BSS like and therefore a new information element was introduced in BSS Abis to enable the support of DTM with the changed function split of power control in BSxx

• Moreover existing in BR paging coordination (not impelmeneted in BSS) is not supported with GEMINI. – This paging coordination means that if Gs interface is not implemented it is not

possible to page MS in Packet Transfer Mode via PACCH

– In BR BSC recognizes that the MS is in Packet Transfer Mode and transfers CS paging to the PCU which sends it via PACCH


Dual Transfer ModeDual Transfer Mode


• Location services:Location services:

– The procedures used for location services in GEMINI is supported as implemented in BSS.

– BSC3i is using the measurement report sent by BTS at reduced rate what also reduces the number of Measurement Reports available for LCS purposes

• Support for Support for real time road traffic information real time road traffic information Tom-TomTom-Tom

– BSS implementation is used in GEMINI. It means that separate Road Traffic Reports (as in BR) via Abis is not sent.


OthersOthers


• Measurement Reports

• In BR Measurement Reports are normally not transmiited on Abis since in BR the pre-evaluation of measurement reports for handover and power control decisions is done in the BTS.

• In some cases, however, it is useful to transmit measurement results on the Abis interface for test purposes (traces). This can be enabled by setting RADIOMR =ON.

• In BSS a BTS averages measurement results over configurable (btsMeasAver) number of SACCH multiframes (1..4). Value 1 actually means that the BTS does not perform averaging and sends every single MR.

• Regardless of BTS averaging, in BSS measurement results (contain averaged results from measurement reports) are always sent on Abis since it is BSC who makes decison for HO & PC. Additionally they are needed for channel allocation based on interference.

Features supported in GEMINIPM counters and measurementsPM counters and measurements

(1/4)(1/4)


• Measurement Reports• In GEMINI HO & PC is BR like therefore BSC3i does not need MR for these purposes,

however they are needed for channel allocation (based on interference) and measurements

• MR are sent from BSxx to BSC3i in a certain configurable frequency(every nth report is sent).

• Although parameter range allows sending every single MR it is not recommended since it generates high load on LAPD channels.

• NetAct reporting tools know how many MR have been arrived from BSxx in the certain time period. This information is needed in order to scale some performance reports (e.g. Erlangs) in case of BSxx.

• With IMSI trace all MR are sent regardless of setting intervalMeasReportSending


Parameter DescriptionInterval Measurement Report Sending

object: BTS

range: 1..254, step 1 default:8

MML command: EQM, EQO

MML Abbreviated Name: IMREPS

Interval Measurement Report Sending (intervalMeasReportSending) - with this parameter you specify the granularity in which the radio measurements have to be transmitted on the A-bis interface in case they are enabled(e.g 8 = 1/8). Parameter is valid only for BTSplus site type

PM counters and measurementsPM counters and measurements (2/4)(2/4)


• Measurement Reports• Measurement results from TCH are sent always (according to configurable frequency

intervalMeasReportSending)

• Additionally it is possible to enable sending measurement reports from SDCCH

• On SDCCH, the 3rd measurement report is sent by BSxx (first two MRs are not sent as it is assumed that they might not contain credible information)

• BSC uses these SDCCH measurements for selecting an appropriate channel for the TCH



SDCCH Measurement Report Sending object: BTS

range: 0, 1


MML Abbreviated Name: SMREPS

SDCCH Measurement Report Sending (sdcchMeasReportSending), with this parameter you define whether or not the SDCCH radio measurements have to be transmitted on the A-bis interface. Parameter is valid only for BTSplus.

Value 0 – means that (radio measurements not transmitted (N)

Value 1 – means that (radio measurements transmitted (Y)

PM counters and measurementsPM counters and measurements (3/4)(3/4)


• The measurement counters in the GEMINI are reused from BSS. All the counters can be post-processed and handled as it is in today’s BSS networks.

• BR counters are removed and are not longer supported in GEMINI configuration.

• This means also that known post-processing tools for BR PM raw data cannot be used any more (must be exchanged at customer side to equivalent tools for BSS PM raw data). Furthermore the known KPIs and other results from BR PM data are no more available in this configuration. So description of delivered PM data / counters is BSS like

• power control command related counters are not updated in ‘Power Control Measurement’ because the BSC doesn’t know when the BTSplus performs PC

• in case of “Concentric Cell” feature counters related to IUO procedures (IUO Direct Access and IUO Direct Access to regular cell) are updated as in IUO although IUO itself is not supported

• BSS Counters based on Measurement report might not be updated as frequently for BSxx as for N-BTS (BSxx send every n-th ‘Measurement Reports’)

• On enabling of “IMSI trace” feature, BTS will start sending MRs every SACCH period. That applies to a certain and low number of simultaneous calls.

• Dropped call Observation and Drop call Breakdown Observation are supported in GEMINI like in BSS (instead of History on Dropped Calls)

• Abis D Channel Measurement can be used to observe load on LAPD

Features supported in GEMINIPM counters and measurementsPM counters and measurements

(4/4)(4/4)


BR features supported by BSC3iBR features supported by BSC3i in GEMINI in GEMINI


• LAPD multiplexing - for more details please refer to dedicated presentation at https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/407517434

• Hierarchial Paging

BR features introduced to BSC 3i with GEMINI

Feature listFeature list


BSS features supported in BSxxBSS features supported in BSxx with GEMINI with GEMINI


• TRX Automatic Power Down

• In the case of BSxx single TRX can be shut down

• TFO for NB AMR

• Dynamic Abis - for more details please refer to dedicated presentation: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/406534184

BSS features supported on BSxx with GEMINI

Feature listFeature list


BRBR features features NOT supportedNOT supported in GEMINI in GEMINI


• No support of GPRS CS3/4 on CU/GCU

• Dynamic MAIO Allocation (DMA)

• Service Dependant Channel Allocation

• Paging coordination for DTM and packet

• Service group dependant HO and PCsetting

• Enhanced Pairing

• Abis load based compression HO

• PCU capacity licensing per 16Kbitsnot possible

• BCCH extended not supported

BR features not supported with GEMINI

Feature list (1/2)Feature list (1/2)

• PBCCH support by BSC3i

• Additional CCCH

• BTSone not support

• Physical Layer aspects (Circuit Emulation Service over Packet)

• Flexible Abis (replaced by dynamic Abis)

• Abis configured as loop with direction switch

• GSM – R basket

• Inter Site Synchronization

• UTRAN Handover to TDD


• Control of BSC via Local Terminal connected to BTS

• PM counters from BR, (only counters from BSS)

• Cell Trace feature is not supported any more, as it’s not available in BSS environment.

• Interfaces at RC (Metrica, RNA, SAMSON, CM*)

• Remote control of BTS HW objects from BSC site

• Online RF Loopback

• Smart Carrier Allocation (SCA)

• Support for more than 32 neighbour cells

• Redefinition of hopping sequence without service interruption

• Changing of various BTS parameters without interuption of service

• Detection of missing TS on Abis

• BR-LMT security

Feature list (2/2)Feature list (2/2)



• No support of GPRS CS3/4 on CU/GCU

– for CU/GCU EDAP handling is not implemented therefore GPRS coding schemes 3 and 4 are not supported.

– Coding schemes 1 and 2 are supported using standard PCU frames.

– EGPRS is not supported by CU/GCU anyhow -> really critical only in cells with pure GCU/CU equipment

• Dynamic MAIO Allocation (DMA) – assignment of MAIO in synthesizer hopping scenarios interference based per channel

activation, measurement of quality to decide on additional traffic

– in use mainly in 1:1 frequency reuse scenarios with synthesizer hopping

• Multi Service Layer Support (aka Service Dependant Channel Allocation)– Allocation of different services to the layer according to the priority list

– The solutions is to set preferences for TCH and GPRS via available BSS parameters

• Paging coordination for DTM and packet data– This paging coordination means that if Gs interface is not implemented it is not

possible to page MS in Packet Transfer Mode via PACCH

– In BR BSC recognizes that the MS is in Packet Transfer Modeand transfers CS paging to the PCU which sends it via PACCH

General (1/2)General (1/2)



• Service group dependant HO and PC setting– it is still possible to set quality thresholds for PC & HO separately for AMR and non AMR

– it is not possible to set different HO and PC level thresholds for AMR and non AMR calls

– no possibility to set different thresholds for hopping and non hopping layer

• Enhanced Pairing

• PCU capacity licensing per 16 kbits not possible

• BCCH extended not supported– specific way of scheduling of SI messages in BR, not used in BSS

• PBCCH support by BSC3i

• BTS one not supported

• Physical Layer aspects (Circuit Emulation Service over Packet)

• Flexible Abis (replaced by dynamic Abis)

• Abis configured as loop with direction switch – redundant BTS/BSC connection with detection and bypass of single line failure

– this configuration can not be migrated as this is a proprietary BR solution which is not supported by Flexi BSC. External transport equipment needs to be installedat BSxx and Flexi BSC side if link redundancy shall be maintained.

General (2/2)General (2/2)



• GSM-R/ASCI

• ASCI related features (VGCS, VBS, EMLPP)– Voice Group calls (point to multipoint), enhanced prioritization and

preemption mechanisms

– used mainly in GSM-R networks

• Support of GSM-R frequencies

• Management of standby TRX – additional TRX can be installed and remain passive but actively

monitored

– redundant TRX handling to meet GSM-R redundancy requirements

Features of regional or customer specific interestFeatures of regional or customer specific interest (1/2)(1/2)



• US

• Inter Site Synchronization - synchronized network with TruePosition TMU/LMU)

• simultaneous power activation of TRX to support FCC authority demand

• China:

• UTRAN Handover to TDD (relevant only in China)

• Additional CCCH (2nd CCCH) – although the BSxx supports BCCH on other timeslots than timeslot 0

on BCCH carrier this is not supported by BSC3i and therefore not available with GEMINI

– only needed in very high load scenarios,

– problems encountered with legacy MS in some configurations -> used in China only

Features of regional or customer specific interestFeatures of regional or customer specific interest (2/2)(2/2)



• Control of BSC via Local Terminal connected to BTS– login to BSC with LMT from BTS site with full control of BSC

– seldom use case

• PM counters from BR (only counters from BSS)

• Cell Trace feature is not supported any more, as it’s not available in BSS environment.

• Interfaces at RC (Metrica, RNA, SAMSON, CM*) – METRICA interface will be available at NetAct

• Online RF Loopback– online monitoring of UL/DL path loss to detect defective RF-equipment

– The solution is to use Link Balance measurements

• Smart Carrier Allocation (SCA) – allows to create measurement report based interference matrix by specific quality/level

scanners

– counterpart BSS feature ”Defined Adjacent Cell and Channel Finder measurements” is available in GEMINI. For more info on interefrence matrix creation in GEMINI please refere to: https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/409766765

Performance and operation Performance and operation (1/2)(1/2)



• Remote control of BTS HW objects form BSC site– commissioning activities, configuration of HW parameters (link IF

parameters)

– settable at BTS local LMT, or remote with LMT at NetAct

• Support for more than 32 neighbour cells (only 32 neighbour cells will be supported per cell, instead of e.g. BR range 64)

• Redefinition of hopping sequence without service interruption– calls may drop, but asumed to be a rare/ low load time operation

• Changing of various BTS parameters without interuption of service

• Detection of missing TS on Abis (based on statistics on remote transcoder failures)

– statistics on RTF. are used to detect problems on Abis or Asub

– less needed as dynamic Abis is simpler to troubleshoot than flexible Abis

• BR-LMT security– BSC wide management of login/password of BTS

– management of LMT user al LMT will be still possible

BR features not supported with GEMINIPerformance and operation Performance and operation

(2/2)(2/2)


BSSBSS features features NOT supportedNOT supported on BSxx on BSxx with GEMINIwith GEMINI


• MultiBCF concept

• BCCH TRX energy saving mode

• Dynamic Frequency and Channel Allocation (DFCA) including:

• DFCA Measurement (optional)

• DFCA Assignment Measurement (optional)

• DFCA SAIC Measurement (optional)

• Space Time Interference Rejection Combining (STIRC)

• ICE (Intelligent Coverage Enhancement)

• IUO (Intelligent Underlay Overlay)

• BS2xx uses concentric cell HO algorithm

• IUO as feature is not supported by BTSplus

• Some IUO/ICE related parameters are used to configure the concentric cell feature and those parameters are available also in the case of BTSplus.

• AMH (Advanced Multilayer Handling)

• AMH as feature is not supported by BTSplus

• Some AMH related parameters are used to parameterize traffic reason HOand those parameters are available also in the case of BTSplus.

BSS features not supported with GEMINI Feature list (1/3)Feature list (1/3)


• DADL (Direct Access to Desired Layer)

• BS2xx uses preferred area request procedure instead

• Progressive Power Control

• UTRAN Neighbouring Cell Signal Level Measurement

• Traffic reason HO to 3G

• Scaling of DL measurements by the MS (related to feature Enhanced Measurement Report)

• HSCSD (multiple timeslots in >35 Km area)

• FlexiEDGE Abis transport Grooming License Control

• FlexiEDGE Loop Protection License Control

• FlexiEDGE Abis over IP/Ethernet

• FlexiEDGE additional 2 E1, T1 interface License Control

• TRAU Bicasting in AMR FR/HR handover (Dual rate TRAU)

• Double Power TRX for Flexi EDGE BTS

• PCU1 is not supported in GEMINI (GEMINI modifications will not be implemented in PCU1)

BSS features not supported with GEMINI Feature list (2/3)Feature list (2/3)


• MultipleBCF feature for BS2xx (Co-Siting)– allows BS2xx to be used in same segment/cell as Ultra/Flexi

• Dual Rate TRAU – switching between 8/16kbits TRAU resource during AMR FR/HR HO to

shorten speech break by allowing bicast during AMR FR<->HR HO

• AMR signaling measurement– counters for repeated SACCH/FACCH execution

• BCCH TRX energy saving, dummy burst and power reduction

• IMSI based handover– target cell selection process different for different IMSI

• SMS-CB DRX mode

Feature list (3/3): Candidates for next release of Feature list (3/3): Candidates for next release of GEMINIGEMINI

BSS features not supported with GEMINI


For more info on features and parameters For more info on features and parameters in GEMINI please refer to:in GEMINI please refer to:

https://sharenet-https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/407567011ims.inside.nokiasiemensnetworks.com/Open/407567011

features in gemini in nutshell

Documents