Gemini Operability

Company confidential – for internal use onlyPresentation / Author / Date 1 © Nokia Siemens Networks

Tampere

February 2009

Operability for GSM/EDGE MIgration Network Infrastructure (GEMINI)


Agenda

• Miscellaneous GEMINI issues

• GEMINI solution

• GEMINI Operability– Migration procedure

– Operability after migration Configuration Management Fault Management Performance Management License Management SW Management User Management


Miscellaneous GEMINI issues

• GEMINI = GSM/EDGE MIgration Network Infrastructure

• BS2xx = Product family name for all BTSplus variants which are supported by Flexi BSC Product Family

• BTSplus = Term used for BS2xx in user interfaces in NetAct and Flexi BSC Product Family

• Flexi BSC Product Family = From RG10 onwards Flexi BSC product family includes: Flexi BSC, BSC3i 1000/2000, BSC3i 660

• GEMINI BCF = New BTS site type as seen in BSC RNW DB

• GEMINI is supported first time in OSS5.1 CD Set2 Priority CD and RG10 ED


GEMINI as the Solution


Solution Overview from BSS perspectiveNetAct

BSS Abis

Flexi BSC

Product FamilyBS2xx

Multiradio(FlexiEDGE)

TCSM3i

LAPD multiplexing

HO/PWCTRL bypass

LMT

EM

Co-

Siti

ng

Mediation function (reuse of Flexi SW)

Keep HO/PWCTRL preprocessing

Reuse of BS2xx SW

BS2xx U-Plane adapts to TCSM


BR-LMT

Flexi BSCeBSC

Net

Ac

t

Q3 mediation

Radio Commander

Flexi Edge BTS

Flexi Edge BTS

BTS Manager-

Q3Q3

3GPP/CORBA

O-link

Abis-BR

Abis-BRAbis-BSS

3GPP/CORBA SB mediation

NB mediation

GUIS

External systemsExternal Systems

Abis-BSS

Abis-BSS

Abis-BSS

Inter-operability for Management Functionalities

of CM, FM, PM, etc

Remote launch BTSManager, RC, BR-

LMT launching from NetAct GUI server using

Q1 over TCP/IP

(See next slide)

Since OSS4.2(SEMI phase1) and OSS5.1 CD1

Target for OSS5.1 CDSet2

Priority CD

BTSplusBTSplusBTSplus

BTSplus

GEMINI Operability from NetAct perspective


LMT remote launch from NetAct via FlexiBSC

BS2xx FlexiBSC Communication Service (GCS) LMT

Q1/OSI

Remote Node Manager connection• routing of LMT messages between Q1/OSI and BSS Abis

Address and connection database

O&M LinkOMUSIG

LMT commands inside BTS_TRANSMISSION_COMMAND message

LMT messages transferred over OSI transport connection (over TCP/IP in BSS14)

NetAct

Mediator

LMT is running on the Node Manager Server (Windows 2000). LMT is launched from NetAct GUI using Citrix.

Q1 over TCP/IP

Node Manager Server


From BTSplus/eBSC/RC to BS2xx/FlexiBSC/NetAct Migration Procedure


Migration procedure

Mobile Radio BR

BS2xx

eBSC

Flexi BSC

ATM BackhaulPDH/SDH

RC

IP

Mobile Radio BSS

ATM BackhaulPDH/SDH

SGSNSGSN

Mobile Core

MSCMSCBSC1

OAM BSSOAM BR

External 2G/3G

RNC BSC

NetAct

LMT

BS2xx BS2xx BS2xxLMT

Upgrade/Migration

LMT

TCSM3i

Upgrade/Migration

(e)TRAU


Network Elements and Interfaces involved in Upgrade and Migration

Flexi BSC TCSM3i

NetAct

RC

2.export of

database

1. upload database

mapping tool

3. control file +manual input

6. download andactivate BS2xx site data

4. import ofBS2xx site data(RAML 2.0 format)

remoteLMT

8. switchAbis link

7. import,download andactivate BSS Abiscapable SW

9. Alignment by Flexi BSC

5. licenses

corenetwork

10. adapt routing

corenetwork

eBSC eTRAU

Data migration from eBSC/BSC1 to Flexi BSC is supported by tools in order to avoid error prone manual handling of bulk data as far as possible.

11. Remove BS2xx site data both from RC and eBSC


1. Rehoming of all BS2xx of one eBSC/BSC1 to Flexi BSC in a single step

BS2xxBS2xx

eBSC/BSC1

Flexi BSC

BS2xxFlexi

EDGE BTS

This adaptation can be done with existing NetAct rehoming functionality


2. Rehoming of a group of BS2xx from several eBSC/BSC1 to Flexi BSC in a single step

BS2xxBS2xx

eBSC/BSC1

Flexi BSC

BS2xxFlexi EDGE BTS

eBSC/BSC1

BS2xx

Almost the same as 1st scenario as the migration can be done in several steps

BS2xx

BS2xx

No effects


Migration procedure shortly

Preparation

• Flexi BSC, TCSM3i and NetAct must exist in live network

• Download Flexi BSC compatible software to BS2xx from eBSC/BSC1

• Export site data from eBSC/BSC1 covering all BS2xx BTSs that are under upgrade

• Convert data of the BS2xx BTSs from eBSC/BSC1 format to Flexi BSC format

• Create the BS2xx data into Flexi BSC RNW database via NetAct

– Note: BS2xx is named as BTSplus in user interfaces both in NetAct and Flexi BSC

Taking into Service

• Activate the software of each BS2xx from eBSC/BSC1 (start of outage time)

• Move Abis connection(s) physically from eBSC/BSC1 to Flexi BSC

• Unlock BS2xx BTS site(s) in Flexi BSC (end of outage time)

• Update NetAct databases (by uploading data from Flexi BSC)

• Remove data of moved BS2xx BTSs from eBSC/BSC1 and RC


GEMINI Operability (After Migration)BTSplus Operability with FlexiBSC/NetAct


How GEMINI is visible in Flexi BSC/NetActGeneral

• A new BTS site type is BTSplus– Three new BTSplus subtypes: Mainline, eMicro and Basic

– Multi-BCF segments are not possible

• No changes to existing counters/measurements

• No changes to existing alarms– Some new external alarms

• No changes to DX Error Codes nor DX Cause Codes– Two new error codes in alarm 7730

• LAPD connections multiplexing is possible


Configuration Management

• A new BTS site type is BTSplus (handled as MO BCF in NetAct RNW DB)– Three new BTSplus subtypes; Mainline, eMicro and Basic– Type of BCF shall be defined in creation. It is not allowed to modify the BCF

type of BTSplus to any other or any other BCF type to BTSplus– BTSplus BTS works as like the Flexi EDGE BTS

• BTSplus manages configuration changes similarly than UltraSite (including BB unit type and supported modulation of it)

• BTSplus may consist up to 32 TRXs under BCF object, and up to 24 TRXs under BTS object– It is not possible to define two or more BTSplus from different BCFs to one

segment (Multi BCF segment is not possible with BTSplus)• It is possible to multiplex up to 16 simultaneous logical LAPD connections

(OMUSIG and/or TRXSIG) into a single 16, 32 or 64 kbps Abis timeslot– LAPD multiplexing is allowed only when BTS type is BTSplus– BTSplus can have max 11 PCM timeslots for LAPD signaling (number of TSLs

are not controlled by BSC, so this must be checked ‘manually’) – There will be separate, predefined LAPD parameters set for BTSplus (separate

because of LAPD multiplexing and different loading of LAPD links)


Fault Management

• Generally from the BTSplus can get the same alarms as from Flexi EDGE BTS– New alarm: ‘CELL CONFIGURATION UPDATE OF BTS FAILED’

– BTSplus has more external alarms than BSS. There are new external alarms 7431...7457 for BTSplus.

• Two new error codes in alarm 7730 when BTSplus configuration failed– EDAP size mismatch

– Error defined by BTS


Performance Management

• BS2xx PM counters are updated as they are updated for Flexi EDGE BTS, except:– Number of MS and BS power control commands in Power Control

Measurement are not updated because the Flexi BSC doesn’t know when the BS2xx performs power control

– Counters of unsupported features are not updated

– Note that counters based on measurement reports/results are updated with a rate of 1/8 (configurable) between BS2xx and Flexi BSC. However, this is not visible in NetAct nor PM applications of it.


License Management

• BTSplus site type does not have any specific license

• Existing capacity based licenses works also with BTSplus– License limit is checked when BTSplus is unlocked


Hardware Management

• HW changes are not needed in BTSplus; functionality can be applied with pure SW upgrade


Software Management

• BTSplus has separate software builds for each HW variant subclass (Mainline, eMicro and Basic)

• This HW variant will be defined by the operator parameter ‘Site Sub type’ in BCF creation

• Firmware build activation is not allowed from NetAct directly but from LMT

• Transferring software from NetAct is practical for mass downloads, for example, you can change the software of all target BTSplus BTS sites in the entire network in one operation.


User Management

• Subscriber trace functionality is available also with BTSplus similarly as currently with e.g. UltraSite


Back-up slides


Configuration ManagementNew/Modified parameters• New parameter ‘Channel Type’ for LAPD• New parameters for BCF;

– Site Type – BCF Abis PORT ID 0, BCF Abis PORT ID 1, … , BCF Abis PORT ID 7

• Modified parameter ‘Site Sub type’ for BCF• New parameters for SEG;

– SDCCH Measurement report sending – Measurement reports sending interval – FACH Busy Threshold – RACH Busy Threshold – Repeated Sacch Rx Lev Threshold DL – Repeated Sacch Rx Lev Threshold UL – Enable R-SACCH in DL – Enable R-SACCH in UL – Enable Temporary Overpower – Enable Repeated Facch – Enable DL Repeated FACCH – Enable Apply R-FACCH – Carrier Unit Configuration – Enable TX diversity timeshift,

• New parameters for HOC;– Enable Advanced compression Handover for AMR – New parameters for POC;– Max DL Power Reduction – Max UL Power Reduction – Derived Handover Power Security Margin – Estimated downlink interference – Enable Downlink Derived Handover Power – Enable Uplink Derived Handover Power


BSS features which are not supported with GEMINI

• Dynamic Frequency and Channel Allocation (DFCA)• Space Time Interference Rejection Combining (STIRC)• EM usage for configuration of BTSplus• IUO (Intelligent Unterlay Overlay)• DFCA Measurement (optional)• DFCA Assignment Measurement (optional)• DFCA SAIC Measurement(optional)• UTRAN Neighbouring Cell Signal Level Measurement (optional)• Scaling of DL measurements by the MS (related to feature Enhanced Measurement Report)• FlexiEDGE Abis TRS Grooming License Control • FlexiEDGE TRS Loop Protection License Control • FlexiEDGE Abis over IP/Ethernet • FlexiEDGE Additional 2 E1, T1 IF License Control• TRAU Bicasting in AMR FR/HR handover (Dual rate TRAU)• Double Power TRX for Flexi EDGE BTS• Autounlock allowed• SPLIT_PG_CYCLE


BR BTS features which are not supported with GEMINI(after migration)

• provision of external Interfaces available at RC

– RNA, OTS replaced by NetAct toolchain

– METRICA interface will be still available

– enables efficient usage of Global Reporter

• remote control of BSC from BTS site

– login to BSC with LMT from BTS site with full control of BSC

– seldom use case

• remote control of BTS HW from BSC (e.g. creation of boards)

– comissioning activities, configuration of HW parameters (link IF parameters)

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


BR BTS features which are not supported with GEMINI(not directly mappable to BSS features)

• smart carrier allocation – network optimization by specific quality/level scanners

• service dependant channel allocation (support of service groups)– designation of TRX to specific services and usage of specific HO and PWRC

parameters, eg. for FR, AMR, ASCI– different AMR FR/HR/normal speech parameterization of HO/PWRC will be

maintained

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

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


BR BTS features which are not supported with GEMINI(not directly mappable to BSS features)

• LCS: enhanced Timing Advance calculation in BTS for positioning algorithm, – TA is evaluated with increased (¼ bit) resolution

• compression decompression (HR/FR) handover for AMR and normal speech calls

– quality based compression/decompression for normal calls

– BR: load based decompression of active calls --> BSS: load based decision only at call setup

• quality based Wideband-AMR to Narrowband-AMR change

– low rate NB-AMR codecs are more robust than low rate WB-AMR codecs, if needed for quality reasons (link adaptation and PWRC capability exceeded) call is changed to NB AMR

• link adaptation for transparent data services

– HSCSD call e.g. 2*14.4 can be changed to 3* 9.6 if MS allows this

• LMT Authentication at Network Entities

– BSC wide management of login/password of BTS

– management of LMT user at LMT will be still possible


BR BTS features which are not supported with GEMINI(Features of regional or customer specific interest)

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


BR BTS features which are not supported with GEMINI(Features of regional or customer specific interest)

US:• synchronized network with TruePosition TMU/LMU• simultaneous power activation of all TRX to support FCC authority demand• Enhanced Measurement Report (e.g. used for DL FER counters)• dynamic MAIO allocation and admission control (soft blocking)

– 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

CHINA:• UTRAN Handover to TDD (relevant only in china)• support of only one CCCH timeslot per cell

– only needed in very high load scenarios, – problems encountered with legacy MS in some configurations -> used in china

only

Various• BTS hardware parameter RXLEVADJUST in BSC database CM interface

– requirement for specific tool chain


BR BTS features which are not supported with GEMINI

• GPRS CS3, CS4 coding schemes only on ECU/FCU, not GCU/CU

– critical only in cells which have pure GCU/CU equipment as typically all (E)GPRS can be served on ECU/FCU alone

• restricted number of TRX in BTSE rack

– limited by COBA memory - planned number of supported TRX is 32

• BTSone not supported


BR BTS features which are not supported with GEMINI

• PM counters from BR not present, only counters of flexi BSC– air interface quality/level/TA are collected like in BSS by using measurement

reports– reporting rate for measurement reports reduced (1/8, adaptable), but shall be not

an issue as statistically matter anyhow

• 32 GERAN+32 UTRAN neighbour cells per cell instead of 64

• redefinition of frequency hopping sequence with service interruption– calls may drop, but assumed to be a rare/ low load time operation

• BCCHextended not supported– Specific way of scheduling of SI messages in BR, not used in BSS

• detection of missing timeslots on Abis (based on statistics on remote transcoder failures)– statistics on remote transc. fail. are used to detect Abis or Asub as problematic IF– Less needed as dynamic Abis is simpler to troubleshoot related to non working

connections than flexible Abis


BR BTS features which are not supported with GEMINI features with configuration limitationsIn general configuration parameters are mapped from BR to BSS

In exceptional cases the following measures have been applied:

• UL/DL configuration attributes merged– BR: enableMSPowercontrol, enableBSPowerControl. BSS: pcControlEnabled

• fixed values instead of configurable– BR: timerFHO (time after a forced HO, a cell is excluded from PBGT HO),

using default 120S

• present at object higher in hierarchy (e.g. ADJC->BTS)– BR: timerInhibitFailHo(ADJC) BSS:

BSSMinIntBetweenUnsuccHoAttempt(HOC)


BR BTS features which are not supported with GEMINI features with configuration limitationsIn general configuration parameters are mapped from BR to BSS

Specific differences

• fine tuning of quality thresholds for Handover and Power control – (BR supports C/I steps 0..20 instead RXQUAL 0..7)

• UTRAN handover configurable only for sufficient coverage – only EC/NO reporting with optional minimum level to report criterea– no hierarchical cell structures for UTRAN cells

• Concentric Cell (Intelligent Overlay Underlay) handover only with level, without distance criteria

• number of supported cells in a BS2xx– BR: supports upto 12 BTS/cells/sectors – BSS: 12 BTS might be mapped to 6 cells/sectors using 2 BTS for each frequency band

• the number of configurable frequency hopping laws is limited– could be handled by generating separate BTS without BCCH under same BCF


New BSS features which are available after migration (compared to BR BTS)

• TFO for narrowband AMR

• interference based channel assignment– support of BSS feature based on SDCCH measurement report

• LAPD channels on Abis with 32Kbit/s– allows better optimization in BSS Abis allocation


Features available with Flexi/Ultra BTS but not in BS2xx Candidates for further extensions of BS2xx@Flexi BSC (RG20)•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– BR11 feature

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

• SMS-CB DRX mode– under discussion for BR11


Example configuration of Abis for BS2xx@flexi BSC (3/3/3 with 40 EDAP slave timeslots)

• 64K/bits LAPD for OMUSIG and TRXSIG (O&M + RSL link)

• each TRX occupies 2 PCM timeslots.

• BCCH, SDCCH are not using associated PCM resources and can be reused for e.g. additional LAPD

• (E)GPRS connection use TCH resource + 0..4 16 kbit/s slave channels from EDAP pool

•number of EDAP timeslots according (E)GPRS traffic model

back

Documents

Gemini Operability