flexi bsc & gemini

FLEXI BSC & GEMINI

Flexi BSC in Brief

Very high circuit-switched capacity for voiceUp to 18,000 ErlangsVery high packet data capacity for EDGE evolutionUp to 30,720 channelsVery high footprint efficiencyLow site-space costs for capacity of 3,000 TRXs and 3,000 BTS sectors and sites in one cabinetExcellent power consumption efficiencyMarket-leading power consumption per capacitySupport for most cost-efficient transport optionsIP/Ethernet available for all interfacesFull flexibility to configure preferred or mixed integrated transmission type (E1/T1, STM-1/OC-3, IP/Ethernet)ScalabilityCapacity and transmission can be flexibly configured in small resolution steps to support pay-as-you-grow approachHigh reliabilityRedundancy, fault management and overload protection on top of very high availability designFlexi BSC in Brief Flexi BSC Product Highlights

Flexi BSC in Brief Flexi BSC comparison to current BSC3i

Maximum capacityBSC3i2000Flexi BSCRacks1-2 racks 1 rackTRXs2,0003,000BTS cells2,0003,000BTS sites2,0003,000Erlangs12,00018,000Packet Data channels (16 kbit/s Abis)25,60030,720PCM/SDH transport lines800 E1/T116 + 16 STM-1/OC-3 (mixed/simultaneous use possible)800 E1/T116 + 16 STM-1/OC-3 (mixed/simultaneous use possible)Integrated IP transmission12 + 12 Gigabit Ethernet connections for all interfaces (RG10)12 + 12 Gigabit Ethernet connections for all interfacesSS7 SignallingIP based SS7 (SIGTRAN) links64/128/256/512kbit/s, 1Mbit/s or 2Mbit/s linksIP based SS7 (SIGTRAN) links64/128/256/512kbit/s, 1Mbit/s or 2Mbit/s linksHW upgrade path to Flexi BSCSupported from all BSC3i configurations (BSC3i 660/1000/2000)

Flexi BSC in BriefGeneral Evolution of BSC Products 2nd BSC generation Large Capacity SW up to 256 TRX (S6) with 2 racksThird generation660 TRXs with 1-cabinet BSC3i 660 configuration (S10.5)1000 TRX with 1-cabinet and up to 2000 TRXs with 2 cabinets by BSC3i 1000/2000 (S12 & S13)3000 TRX with 1-cabinet by Flexi BSC (BSC3i 3000) (S14)Complete solution for future CS and PS traffic handling capacity requirements with IP connectivity

High Capacity BSC along with smooth upgrade path (S8)Capacity increase up to 512 TRX with 2 racks1991199519992002Second generationBSC3iBSC2iBSCEFirst BSC generationUp to 128 TRX with 2 high racksBSC2First generation20072009

Flexi BSC in BriefFlexi BSC increases usable capacityBSCEBSC2E BSC2i BSC3i 660 BSC3i 2000 Flexi BSC128 TRX 256 TRX 512 TRX 660 TRX2000 TRXBSC2iBSC2iBSC3i 660BSC3i 660BSC3i 2000 (11880 Erl)BSC3i 2000 (11880 Erl)PS Traffic handling capacityBSCE BSC2E BSC2i BSC3i 660 BSC3i 2000 Flexi BSC2048 409640964.5 x6 xNotsupportedin S14Notsupportedin S14BSC3i 2000 (11880 Erl)FLEXI BSC (BSC3i 3000) (18000 Erl) 1.5 x3000 TRX(8x1x1x256)(8x1x2x256)(8x1x2x256)6144(6x2x2x256)25600(10x5x2x256)30720(6x5x1x1024)number of Abis channel @16kbPs PS TCH# BCSUs/BSC x # PCU pius/BCSU x # logical PCUs/PCU piu x #max Abis channel @16Kbps for PS TCHCS Traffic handling capacity

Flexi BSC product family The Flexi BSC product family consists of:

BSC3i 660 BSC3i 1000 BSC3i 2000 Flexi BSC pcu2-e 1024 660pcu2-d256

0

Flexi BSC Hardware and Functionality

Fast installation and very easy expansionSimple mechanical structureRelatively few componentsInternal cabling readyNo special site requirements No need for raised floorCompact size reduces site space needsWeight is approx. 350 kg, floor load below 500 kg/m2Simplified cabling with compact designOverhead cable and raised-floor options Dimensioned according to international standardsand recommendationsDesigned on IEC, EN, ETSI, UL and TelcordiaEnhanced earthquake and fire resistanceAdvanced features in terms of safety, protection against interference, stability and durabilityWelded frame structureLow power consumption2000 mm600 mm900mmFlexi BSC Hardware and Functionality Cabinet MechanicalM98

3000 TRXs (500 TRXs per capacity step)Flexi BSC Hardware and Functionality Flexi BSC technical specificationsEnvironmentPower consumptionPower supplyDimensions (H x W x D)WeightMax. number of BCSUsMax. capacity of BCF/BTSMax. capacity of BSC TRXs3000 BCF (BTS sites) / 3000 BTS objects (Sectors)(500 BCF / 500 BTS per capacity step)6+1 BCSU units (500 TRX each)16 STM-1/OC-3, 12 Giga Ethernet or 800 E1/T1 PCM interfacesApprox. 350 kg, floor loading below 500 kg/m2, no need for raised floor2000 x 900 x 600 mm Inputs 48 or 60 V DC (ETS 300 132-2) Direct floating batteries can be usedNormal operations fully loaded ~ 2.7 kWSafety: EN 60950 and UL 60950 Fire resistance: GR63CORE & TP76200MPEarthquake resistance: ETS300019 & GR63COREEnvironmental requirements: ETS 300019-1-3EMC specifications: EN 300386-2 & FCC part 15Acoustics noise: ETS 300 753 & GR63CORERestriction of Hazardous Substances: EU 2002/95/EC (RoHS)Product collection and disposal: 2002/96/EC (WEEE)Max. number of ext. interfaces

Flexi BSC Hardware and Functionality Computer Units (1/4)MCMUBCSUOMUMCMUOMUBCSUBCSUBCSUBCSUBCSUBCSUFlexi BSC cabinet In the Flexi BSC, the call control functions are executed by micro-computers, calledCall Control ComputersMCMUBCSU2000 x 900 x 600 cabinet (HxWxD)

Flexi BSC Hardware and Functionality Computer Units MCMU (Marker and Cellular Management Unit) (2/4) The Marker and Cellular Management Unit (MCMU) controls and supervises the Bit Group Switch and performs the hunting, connecting and releasing of the switching network circuits.The cellular management functions of the MCMU are responsible for cells and radio channels that are controlled by the BSC. The MCMU reserves and keeps track of the radio resources requested by the MSC and the handover procedures of the BSC. MCMU also manages the configuration of the cellular network.Redundancy 2NMCMUPlug-in units CP816-AC SWPRO-C ESB24-A PSC6-ABMCMUMCMU

Flexi BSC Hardware and Functionality New SWPRO-CThe SWPRO-C plug-in unit is used as a control unit for a bit-oriented group switch (GSWB). The GSWB control unit functionality provides two control bus interfaces through the backplane connection.Processor Intel Celeron 1.0 GHz, 400 MHz with SDRAM: 1 GB (with x8 memory configuration)SWPRO-C allows to control higher amount of connections and generates less load to the MCMU CPU in comparison to SWCOP-A

SWPRO-C

BSC3i 1000 & 2000 Hardware and FunctionalityESB24 Ethernet SwitchUsed in Flexi BSC first delivery for EMB and IP LAN switchingIn front panel there are:4 SFP Ethernet ports (ETH1,2 & ETH23,24) 1000Base-T ports in Gigabit mode1 MGT ports (RJ45) serial port for switch menagement1 SER1 ports (RJ45) console connector used for initial configurationIn back panel there are:20 Full-duplex 10/100/1000Base T/TX ethernet PortsESB24 unit located in MCMU is used for EMB switchingConnects all CPUs ESB24 units located in LANU are used for IP LAN SwitchingConnects together all CPUs and all PCUs

The BSC Signalling Unit (BCSU) performs those BSC functions that are highly dependent on the volume of traffic. Consists of two parts, which correspond to the A and Abis interfacesPacket Control Units (PCUs) are housed in the same cartridge.The A interface part of the BCSU is responsible for performing all message handling and processing functions of the signalling channels connected to it Performing the distributed functions of the Message Transfer Part (MTP) and the Signalling Connection Control Part (SCCP) of SS7 Controlling the mobile and base station signalling (Base Station Subsystem Application Part, BSSAP)The Abis interface part of the BCSU controls the air interface channels associated with transceivers (TRXs) and Abis signalling channels. The handover and power control algorithms reside in this functional unit.Redundancy N + 1

BCSUPlug-in units CP816-AC AS7-D PCU2-E PSC6-DBCSUBCSUBCSUBCSUBCSUBCSUFlexi BSC Hardware and Functionality Computer Units BCSU (BSC SIgnalling Unit) (3/4)

Flexi BSC Hardware and Functionality New AS7-D (1/2)The AS7 plug-in unit function as a general purpose peripheral slot computing engine 512 HDLC channels (2x that of AS7-C), 8x more memory, data processing performance is estimated to be ~1.4x that of AS7-Can interface to OMC (X.25), then it is installed in OMU.Processor and capacity Performance:Processor: Intel Celeron M ULV 1.0 GHz, 400 MHz FSB (Data quad pumped, 3.2 GB/s).L1 Instruction cache: 32 kB L1 Write Back Data Cache: 32 kB L2 Cache: 512 kBMemory::SDRAM: 1 GB Capacity: Channels: 5122M PCMs: 16 (32)AS7-D PIU

Flexi BSC Hardware and Functionality New AS7-D (2/2) AS7_D 14 TRACK: 8 MS:FA000000 ME:FBFFFFFF IS:E240 IE:E27F INT:20H SW:0649005E TSLS 30 20 10 0 LAPD 8M PCM: 400 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 1

LAPD 8M PCM: 401 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 1




LAPD 8M PCM: 415 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 2 AS7_D 13 TRACK: 7 MS:F8000000 ME:F9FFFFFF IS:E200 IE:E23F INT:22H SW:0649005C TSLS 30 20 10 0 CCS7 8M PCM: 416 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 1




.

LAPD 8M PCM: 431 B 11111111111111111111111111111111 R 11111111111111111111111111111111 CONNECTOR SIDE: HOR: VER: POINT: 2Above is example of internal PCM connection for BCSU-1:On track 8 : PCM 400 PCM 415 (16 PCMs) all TSL (0-31) used for LAPDOn track 7 : PCM 416 (1 PCM) all TSL (0-31) used for SS7, PCM 418-431 (14 PCM) all TSL (0-31) used for LAPD

Flexi BSC Hardware and Functionality New PCU2-EPCU functionality in Flexi BSC can be realized by: PCU2-ENew PCU2-E offering significant capacity enhancements:Consist of 1 logical PCU1 logical PCU can handle 1024 Abis Channel @ 16 Kbpsup to 5 PCU/BCSU x 6 BCSU/BSC = 30 logical PCU/BSC => 30720 Abis channels / BSC3i 3000If compared with PCU2-D::Consist of 2 logical PCU1 logical PCU can handle 256 Abis Channel @ 16 KbpsIn BSC 2000, the capacity =10 (active) BCSU/BSC x 5 PCU2-D/BCSU x 2 logical PCU/PCU2-D 256 Abis Channel / logical PCU = 25600 Abis Channel PDFU PDFU CLS GSW2KB GSW2KB CLS LANU LANU FTRB FTRB Flexi BSCGTIC GTIC ETC ETC ETC ETC BCSU BCSU 2BCSU 3BCSU 5BCSU 4BCSU 6FTRB FTRB MCMU MCMU OMUBCSU 1PCU2-E PIUPCU2-E Capacity

BTS ObjectsTRX ObjectsAbis ChannelsUp to 30 x 384Up to 30 x 1,024Up to 30 x 1,024

Flexi BSC Hardware and Functionality Computer Units OMU (Operation and Maintenance Unit) (4/4)OMU is an interface between the BSC and a higher-level network management system and/or the user. The OMU receives fault indications. It can produce local alarm printouts to the user or send the fault indications to NetActIn a fault situation, the OMU automatically activates appropriate recovery and diagnostics procedures. Recovery can also be activated by the MCMU if the OMU is lost.The OMU consists of microcomputers and contains I/O interfaces for local operation.The tasks of the OMU can be divided into five groups:traffic measurement functionsmaintenance functionssystem configuration administration functionssystem management functionsLAN topology managementOMUOMUPlug-in unitsCP816-ACAS7-DHWAT-BSERO-BPSC6-ABMass memory adapter: DCAR1-A

Flexi BSC Hardware and FunctionalityDCAR1-A Plug in UnitUSB port in DCAR1-A PIUUSB memory stick will provide reliable means for backup copying SW and database on a transferable media in BSCCapacity of memory stick is 4 GBHDSAM (contained HSD07) also in DCAR1-A PIUDuplicated Hard disk units are installed with carrier adapter per BSC to ensure high reliabilityEasy to change or upgrade without traffic interruptionCapacity of HSD07 is 73 GB

LED indicator on DCAR1A :green normal operationred failure conditionHard disk AMC front panel (HDSAM-A) Red - out of Servicegreen Power goodBlue Hot Swapamber hard disk drve activity

Flexi BSC cabinet Flexi BSC Hardware and FunctionalityOther Units LANUGSW2KBGTICCLOCETCETCETCLANULANUGTICGSWBCLOCETCETCGTICGSWBCLOC

Flexi BSC Hardware and FunctionalityHardware Changes compare to BSC3i 1000/2000New Plug In Unit: ETIP1-A for EET interface PCU2-E for Packet data PSC6-D for power supply in each ESB24-A for ethernet switch SWPRO-C for controlling GSWB

Common Unit:FTRB-A enhanced fan unitsCP816-A CPU for all computer unitsBit based group switch for 2048 PCMs (GSW2KB)ET16 for E1/T1 interfaceETS2 for STM-1 or OC-3 interfaceDCAR-A for mass memoryLANUEthernet Message Bus (EMB)MCMU 1OMUFlexi BSC cabinet MCMU 0BCSU 02000 x 900 x 600 cabinet (HxWxD)BCSU 1BCSU 3BCSU 5LANU 0BCSU 1BCSU 3BCSU 5LANU 1GTIC 1GSWB 1ETC 1ETC 3CLS 1GTIC 0GSWB 0ETC 0ETC 2CLS 0Removed Units:ESB26 Ethernet SwitchCLAB for clock repeating

Architecture changes6 + 1 BCSU units No extension cabinet

Flexi BSC Capacity

Flexi BSC Capacity Configuration steps#TRX per BSC (*1)#active BCSUmax #BTS / #BCFmax #logical PCU2-Emax #PS Abis chan@16max #RTSLmax #SS7 links:64 kbps128 kbps256 kbps512 kbps1024 kbpsHSLmax #LAPD (*2)#PCM (*3):ET16(*4)SET (*5)ETIP(*5)15001500551204000

842212992800161250110002100010102408000

1684424198480016121001150031500151536012000

16126636297680016121501200042000202048016000

16168848396880016122001250052500252560020000

16161010510496080016122501300063000303072024000

1616121261259528001612(*1): Software is scalable in 1 TRX steps with licence key. (*2): #LAPD links achievable with low capacity SS7 links. Therefore in 3000 TRX conf. SS7 over IP (SIGTRAN) should be used to avoid lack of LAPD links. (*3): #controllable PCM lines does not depend on #BCSU (*4): above 48 requires a cabling cabinet(*5): Active interfaces. Doubled for redundancy: 16 + 16 (SET) or 12 + 12 (ETIP). Flexi BSC maximum capacity steps in S14 hardware environment

GEMINI OVERVIEW

GEMINI Overview

GEMINI stands for GSM/EDGE Migration Network Infrastructure The program adapts BTSplus product family (BR-BTS) SW to work with FlexiBSC product family (BSS-BSC)GEMINI denotes SW adaptation, no HW modifications are foreseen on the BTSplusGEMINI does not affect connections between BSS-BTS products and BSC3i

Base station types of the BSS product lineThe Flexi BSC product family has been adapted, allowing it to manage the BTSplus as a new BSS BTS type, in addition to the base station types of the BSS product line: UltraSite EDGE BTSMetroSite EDGE BTSTalk-family BTSFlexi EDGE BTS

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

BTSplus product family The BTSplus product range can be divided into three type groupings:

BTSplus mainline: BS-240/BS-241 BS-240 II/241 II/241 II B BS-240XL BS-240XL II BS-40 II BS-40/41 BS-82 II M

BTSplus eMicro: BS-82 E

BTSplus basic: BS-240XS B BS-288

BTS configuration limits in GEMINIBSC3i point of view:FlexiBTS/UltraSiteBTS/MetroSiteBTS limits are not affected but the ranges of TRX-id and cell-id must be adjusted in BSC3i due to introduction of GEMINI (e.g. TRX-id from 24 to 32)

BTSplus point of view:The number of TRX in BTSE rack is restricted (limited by COBA memory) from 48 to 3232 TRXs/BCF corresponds to usage of up to 16 FlexCU

Network architecture Changed during MigrationAfter migration, the LMT Evolution has been integrated into NetAct to replace the Radio Commander.

Features and capabilities of the various Network Elements during MigrationeBSC/BSC1 Download new BSS-compatible software to the BTSplus Activate new BSS-compatible software in the BTSplus Upload configuration data to RC and the LMT Export configuration data for migration to the Flexi BSC

Flexi BSC Tolerate or ignore BR Abis-like connection establishment attempts Support new BTSplus software build types

GEMINI Abis Interface

Signalling and traffic timeslots are configurable in a BTSE on up to 4 PCMB lines with the BTSplus family => these PCM lines support load-sharing and fault managementLAPD signalling timeslots are 16 kbps sub-slots or 64 kbps timeslots => mixture of signalling links of different capacities is not allowed between BTS and BSCOn the BTSE side the LAPD timeslots are called LAPDLE while in the BSC database they are called LPDLM although they may carry both LPDLM (management) and LPDLR (TRX) type signallingFor each PCMB line at least one LAPDLE/LPDLM is requiredFor a single BTSE up to 11 LPDLM objects can be definedThe TRXs belonging to the same BTSE can be configured on one common physical LAPD linkThe LAPD pool is a set of 16 kbps PCM sub-slots represented in the data-base by the LPDLM objectAbis allocation in BR product line

Abis allocation in BR product lineAbis pool = set of 16 kbps Abis sub-slots reserved for a BTSM (on up to 4 PCM lines), which are dynamically available for radio timeslots of the BTSMAbis sub-pool = set of 16 kbps Abis sub-slots on a specific PCM line reserved for a BTSM, all Abis sub-pools reserved for a given BTSM constitutes the Abis pool, each Abis sub-pool is associated with the LPDLM channelSite_2Cell 4Cell 5Cell 6BTSM_2sub-pool_C sub-pool_A sub-pool_B sub-pool_C PCM-0PCM-1PCM-1Integrated cross-connect or multi-drop configurationStar configurationIn case of a PCM-0 failure traffic is dynamically reallocated to sub-pool_B of the pool_BTSM_1

The idea of the Abis sub-pools defined for the Abis pool associated with a BTSM was developed to make the PCMB fault management flexibleThe PCMB fault is detected by the LPDLM fault:Up to BR6.0: radio channels statically associated with the corresponding Abis sub-slots of the faulty PCMB are disabled until the fault is repaired

From BR7.0: Abis sub-pools are configured on different PCMB lines => radio channels so far transmitted within the Abis sub-pool of the faulty PCMB are dynamically rearranged and transmitted within the Abis sub-pool of the operative PCMB

Distribution of the Abis sub-pools over different PCMB lines ensures the highest resilience against the PCMB faultsAbis allocation in BR product line

Step 1: create a new BTSM:CREATE BTSM NAME=BTSM:0;=> The BTSM is createdBTSE (BTS Site Equipment) represents one or more physical BTS cabinets, e.g. BS-240 base rack or BS-240 base rack + BS-240 extension racks, that make up a site

BTSM (BTS Site Manager) represents a logical functionality controlling one or more BTSs (cabinets = base rack or base rack + extension racks) within one BTSE => performs all the O&M functions common to all transceivers

Example:BR Network ArchitectureDefinitions and Basic Configuration Management (1/2)CREATE BTSM NAME=BTSM:0199*, [OPTIONAL PARAMETERS]**;eBSCBS-240 (base rack)BS-240 extension racksBTSM:0

Step 2: create a new BTS:CREATE BTS NAME=BTSM:0/BTS:0=> The BTS is created and assigned to the BTSMBTS (Base Transceiver Station) locates a cell connected to a BSC and logically represents all information related to the cell and its configurationThe command CREATE BTS sets the configuration of the cell by specifying the global parameters necessary for the creation:

Example:BR Network ArchitectureDefinitions and Basic Configuration Management (2/2)CREATE BTS NAME=BTSM:0199/BTS:011, [OPTIONAL_PARAMETERS]*;eBSCBS-240 extension racksBTSM:0Cell 1BTS:0BS-240 base rack

CREATE BTS NAME=BTSM:0/BTS:0,CELLTYP=STDCELL,SYSID=BB900,BCCHFREQ=12;CREATE TRX NAME=BTSM:0/BTS:0/TRX:0,TRXFREQ=12;CREATE TRX NAME=BTSM:0/BTS:0/TRX:1,TRXFREQ=...;...CREATE BTS NAME=BTSM:0/BTS:1,CELLTYP=STDCELL,SYSID=BB900,BCCHFREQ=17;CREATE TRX NAME=BTSM:0/BTS:1/TRX:3,TRXFREQ=17;CREATE TRX NAME=BTSM:0/BTS:1/TRX:4,TRXFREQ=...;...CREATE BTS NAME=BTSM:0/BTS:2,CELLTYP=STDCELL,SYSID=BB900,BCCHFREQ=23;CREATE TRX NAME=BTSM:0/BTS:2/TRX:6,TRXFREQ=23;CREATE TRX NAME=BTSM:0/BTS:2/TRX:7,TRXFREQ=...;...BR Network ArchitectureClassical Single Band NetworkBTS:0TRX:0BTSM:0TRX:3TRX:6BTS:1BTS:2TRX:1TRX:4TRX:7BSCCell 1Cell 2Cell 3siteeBSCCell 1Cell 2Cell 3BS-240Cell 1Cell 2Cell 3BCCH 900BCCH 900BCCH 900BCCH carrier layerEach 900 MHz cell has its own BCCH carrierTRX:2TRX:5TRX:8defines the bandwidth of a cell, e.g. BB900 = PGSMdefines the type of a cell

CREATE BTS NAME=BTSM:1/BTS:0,CELLTYP=STDCELL,SYSID=DCS1800,BCCHFREQ=975;CREATE TRX NAME=BTSM:1/BTS:0/TRX:0,TRXFREQ=975;CREATE TRX NAME=BTSM:1/BTS:0/TRX:1,TRXFREQ=...;...CREATE BTS NAME=BTSM:1/BTS:1,CELLTYP=STDCELL,SYSID=DCS1800,BCCHFREQ=979;CREATE TRX NAME=BTSM:1/BTS:1/TRX:3,TRXFREQ=979;CREATE TRX NAME=BTSM:1/BTS:1/TRX:4,TRXFREQ=...;...CREATE BTS NAME=BTSM:1/BTS:2,CELLTYP=STDCELL,SYSID=DCS1800,BCCHFREQ=983;CREATE TRX NAME=BTSM:1/BTS:2/TRX:6,TRXFREQ=983;CREATE TRX NAME=BTSM:1/BTS:2/TRX:7,TRXFREQ=...;...BR Network ArchitectureClassical Dual Band NetworkBTS:0TRX:0BTSM:0TRX:3TRX:6BTS:1BTS:2TRX:1TRX:4TRX:7BSCCell 1Cell 2Cell 3siteBCCH carrier layerTRX:2TRX:5TRX:8BTS:0TRX:0BTSM:1TRX:3TRX:6BTS:1BTS:2TRX:1TRX:4TRX:7TRX:2TRX:5TRX:8Cell 4Cell 5Cell 6BS-240Cell 4Cell 5Cell 6eBSCCell 1Cell 2Cell 3BS-240Cell 1Cell 2Cell 3Cell 4Cell 6Cell 5BCCH 900BCCH 900BCCH 900BCCH 1800BCCH 1800BCCH 1800BCCH carrier layersiteSee the previous slide for the BTSM:0- 900 MHz- 1800 MHz

CREATE BTS NAME=BTSM:0/BTS:0,CELLTYP=DBSTDCELL,SYSID=GSMDCS,BCCHFREQ=12;CREATE TRX NAME=BTSM:0/BTS:0/TRX:0,TRXFREQ=12;CREATE TRX NAME=BTSM:0/BTS:0/TRX:1,TRXFREQ=975;...CREATE BTS NAME=BTSM:0/BTS:1,CELLTYP=DBSTDCELL,SYSID=GSMDCS,BCCHFREQ=17;CREATE TRX NAME=BTSM:0/BTS:1/TRX:3,TRXFREQ=17;CREATE TRX NAME=BTSM:0/BTS:1/TRX:4,TRXFREQ=979;...CREATE BTS NAME=BTSM:0/BTS:2,CELLTYP=DBSTDCELL,SYSID=GSMDCS,BCCHFREQ=23;CREATE TRX NAME=BTSM:0/BTS:2/TRX:6,TRXFREQ=23;CREATE TRX NAME=BTSM:0/BTS:2/TRX:7,TRXFREQ=981;...BR Network ArchitectureDual Band Standard Cell NetworkBTS:0TRX:0BTSM:0TRX:3TRX:6BTS:1BTS:2TRX:1TRX:4TRX:7BSCCell 1Cell 2Cell 3siteTRX:2TRX:5TRX:8eBSCCell 1Cell 2Cell 3BS-240 base rackCell 1Cell 2Cell 3BCCH 900BCCH 900BCCH 900BCCH carrier layerseparate feeder and combiner systems are necessary separate band specific antennas or a common dual-band antennaIn case the greater number of TRXs is required just add (an) extension rack(s) and create new TRXs- 900 MHz- 1800 MHz

Step 1: create a new BCF:ZEFC:1,P:DNAME=OMU23;=> The BCF is created and associated with the OMUSIG LAPD channelBCF (Base Control Function) is a functional entity which handles common control functions of a base transceiver station:Associated with a physical base station cabinet, e.g. with the UltraSite BTSUsually contains several BTS objects or SEG objects which represent cells (sectors)Created in the BSS database using the following syntax in the command line:

Example:BSS Network ArchitectureDefinitions and Basic Configuration Management (1/6)ZEFC:,:;*BSC3iUltra SitePCM line with OMUSIG=OMU23 BCF-1B: 2nd generationD: Talk-familyF: PrimeSiteC: MetroSiteI: InSiteP: UltraSiteE: Flexi EDGE

BTS (Base Transceiver Station) is a cell consisting of TRXs belonging to the same base transceiver station and operating on the same frequency band:In the BSS database the cell is represented by the BTS objectCreated in the BSS database using the following syntax in the command line:

Example:

Applicable to the standard single or dual band networkStep 2: create a new BTS:ZEQC:BCF=1,BTS=1:CI=11,BAND=900:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;EFC:1,D:DNAME=OMU23;=> The BTS is created in the BCFBSS Network ArchitectureDefinitions and Basic Configuration Management (2/6)ZEQC:,:,:,:,,;BSC3iCell 1Ultra SiteCell 1PCM line with OMUSIG=OMU23 BCF-1BTS-1

BSS Network ArchitectureDefinitions and Basic Configuration Management (3/6)SEG (Segment) is a cell consisting of TRXs belonging to:More than one co-located and synchronised base transceiver stations served by a common BCCH channelThe different frequency bands served by a common BCCH channelIn the BSS database the segment is represented by the SEG objectCreated in the BSS database using the following command line with the optional SEG identification:

The multi BCF control and common BCCH control use the concept of the segment:The maximum number of BTSs in a segment is 32The maximum number of TRXs in a segment is 36

ZEQC:,, :, :,:,,;

BSS Network ArchitectureDefinitions and Basic Configuration Management (4/6)The BTS object in a segment must consist of TRXs of the same frequency band => PGSM 900, EGSM 900, GSM 1800, GSM 800 or GSM 1900The BTS object in a segment must consist of TRXs of the same base station site type => Talk family, UltraSite, Flexi EDGE or MetroSite

The use the segment concept is not restricted to the multi BCF control or to the common BCCH control => e.g. multiple hopping groups in a cell can be setup by creating several BTS objects in a segment and grouping TRXs of each hopping rule in each BTS objectcommon to all TRXscommon to BTS specific TRXs

Step 3: create a new SEG and assign BTSs to the SEG:ZEQC:BCF=1,BTS=1, SEG=1:CI=11,BAND=900:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;EFC:1,D:DNAME=OMU23;ZEQC:BCF=1,BTS=2, SEG=1:CI=11,BAND=1800:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;EFC:1,D:DNAME=OMU23;=> 1 SEG object is created and associated with 1 BCF object, 2 BTS objects are assigned to the SEG objectBSS Network ArchitectureDefinitions and Basic Configuration Management (5/6)BSC3iUltra SiteCell 1PCM line with OMUSIG=OMU23 BCF-1BTS-2BTS-1SEG-1Example 1: the number of TRXs in a site requires use of one cabinet only (no multi BCF control) separate band specific antennas or a common dual-band antennaseparate feeder and combiner systems are necessary

Step 3: create a new SEG and assign BTSs to the SEG:ZEQC:BCF=1,BTS=1, SEG=1:CI=11,BAND=900:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;EFC:1,D:DNAME=OMU23;ZEQC:BCF=2,BTS=2, SEG=1:CI=11,BAND=1800:NCC=3,BCC=4:MCC=111,MNC=02,LAC=3344;EFC:1,D:DNAME=OMU23;=> 1 SEG object is created and associated with 2 BCF objects, 2 BTS objects are assigned to the SEG objectBSS Network ArchitectureDefinitions and Basic Configuration Management (6/6)Ultra SiteBSC3iUltra SiteCell 1SYNCBTS-2BTS-1SEG-1BCF-1BCF-2Example 2: the number of TRXs in a site requires use of few cabinets (multi BCF control)separate band specific antennas or a common dual-band antenna

Create BTSPLUS in FlexiBSC

Creating BTSPLUS in FlexiBSCDatabase in eBSC

CREATE BTSM:NAME=BTSM:2,,PCMCON0=PCMB_003-PORT_0,PCMCON1=PCMB_004-PORT_2,;

CREATE LPDLM:NAME=BTSM:2/LPDLM:0,ABISCH=3-31,LAPDPOOL=1;CREATE LPDLM:NAME=BTSM:2/LPDLM:1,ABISCH=4-30,LAPDPOOL=1;

CREATE BTS:NAME=BTSM:2/BTS:0,CELLGLID="460"-"00"-6378-36897,BSIC=6-5,PLMNP=100,CELLTYP=STDCELL,SYSID=BB900,BCCHFREQ=27,CALLF01=56,CALLF02=32,;

CREATE BTS:NAME=BTSM:2/BTS:1,CELLGLID="460"-"00"-6378-36898,BSIC=6-3,PLMNP=100,;

SET PWRC:NAME=BTSM:2/BTS:0/PWRC:0,;CREATE PTPPKF:NAME=BTSM:2/BTS:0/PTPPKF:0,RACODE=1,RACOL=0,;

CREATE FHSY:NAME=BTSM:2/BTS:0/FHSY:1,HSN=3,MOBALLOC=CALLF01&CALLF03&CALLF04&CALLF05&CALLF06;

CREATE TRX:NAME=BTSM:2/BTS:0/TRX:0,TRXFREQ=BCCHFREQ,, TRXMD=EDGE,;CREATE TRX:NAME=BTSM:2/BTS:0/TRX:1,TRXFREQ=CALLF01, TRXMD=GSM,;

CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:0,CHTYPE=MAINBCCH, FHSYID=FHSY_0,;CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:1,CHTYPE=SDCCH,CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:2,CHTYPE=CCCH, CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:3,CHTYPE=TCHF_HLF,CREATE CHAN:NAME=BTSM:2/BTS:0/TRX:0/CHAN:3,CHTYPE=TCHSD,

Creating BTSPLUS in FlexiBSCDatabase in eBSCCREATE TGTBTS:NAME=TGTBTS:66,CELLGLID="460"-"00"-6244-13409,BSIC=6-0,BCCHFREQ=9,SYSID=BB900,MSTXPMAXGSM=5,;

CREATE TGTPTPPKF:NAME=TGTBTS:66/TGTPTPPKF:0,RACODE=1,RACOL=0,GRXLAMI=6,GMSTXPMAC=2,;

CREATE TGTTDD:NAME=TGTTDD:52,CELLGLID="460"-"00"-43030-32817,RNCID=390,BNDWID,;

SET HAND:NAME=BTSM:3/BTS:0/HAND:0,;SET BTS:NAME=BTSM:3/BTS:0,BTSHSCSD=FALSE,;

CREATE ADJC:NAME=BTSM:2/BTS:0/ADJC:33,TGTCELL=BTSM:68/BTS:0,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0,HOMDOFF=0,;

CREATE ADJC3G:NAME=BTSM:2/BTS:0/ADJC3G:0,TGTCELL=TGTTDD:0,USRSCP=18,USECNO=23,UMECNO=19,UADJ=63,PLNC=0,;

CREATE ADJC:NAME=BTSM:3/BTS:0/ADJC:8,TGTCELL=BTSM:2/BTS:0,RXLEVMIN=20,HOM=69,HOMSOFF=0,HOMDTIME=0,HOMDOFF=0,;

Creating BTSPLUS in Flexi BSC Frequency bands Supported in GEMINI

The BTSplus supports the following frequency bands:

GSM 850 MH GSM 900 MHz (primary GSM)GSM 900 MHz extended (EGSM)GSM 1800 MHz (DCS)GSM 1900 MHz (PCS)

Note: When operating the BTSplus with the Flexi BSC product family, the GSM-R frequency band is not used.

Baseband hopping with CU and ECU in one cell still using EGPRS

in BR hopping system (FHSY) is defined per TSL and 11 FHSYs per cell are allowedIn case of baseband hopping (BB) if FHSY include ECU and CU then EDGE is not supported on that TSL where this FHSY is runningthis gives huge flexibility in hopping configuration eg. following BB hopping configuration is supported

In BR it is possible to define BB hopping with ECU only (TRX1-4) for certain timslots (TSL 0-4) serving EGPRS and for normal calls on the other TSLs (TSL 5-7) BB hopping including all CUs in the cell (TRX1 -6).

Creating BTSPLUS in Flexi BSC BB HOPPING in BR

Baseband hopping with CU and ECU in one cell still using EGPRS

in BSS one hopping system can be configured in one BTS but it is possible to have multiple BTS (up to 32) per segement (cell) (COMMON BCCH in used)

In case of mixed configuration (cells with EDGE capable and EDGE not capable TRXs) 2 BB hopping systems must be configured by means of 2 BTS objects per segement and each of them must be using only TRXs of the same type; otherwise EDGE will be not supported

ECU/FCU supports EDGE while CU/GCU does not

Creating BTSPLUS in Flexi BSC BB HOPPING in GEMINI

Creating BTSPLUS in Flexi BSCPoints in Creating BTSPLUS in Flexi BSC

BTSM refers to BCF in Flexi BSCDefine the port and PCM during creating BCFMultiplexing LAPD in Flexi BSCLAPD mapping between BSC and BTS sitePlan TRX LAPD multiplexing into different LAPD( LAPD overload protection )Max to 11 LAPD per BCFBTS refers to CELL(SEGMENT) in Flexi BSCCommon BCCH allows EGSM/PGSM used in the same cellDefine the CHW (refers to BTM NO. in eBSC database) during creating BTSPlan the TRX TCH TSL mapping into PCM-TSLMax to 32 TRX per BCF of BTSPLUS

Creating BTSPLUS in FlexiBSCCreate LAPD

Create OM LAPD( Lapd mutiplexing)

Create TRX LAPD ( Lapd mutiplexing)

ZDSE:OM001:BCSU,0:62,1:64,265-31:M,2;TRXSIG and OMUSIG channels that share the same timeslot (physical LAPD link) must be configured to the same BCSU unit and to the same signaling terminal62- OM LAPDOMU TEI=1LAPD BIT RATE=64K N ... NORMAL CHANNEL C ... COMBINED CHANNEL M ... MULTIPLEXED CHANNEL 0 ... STANDARD ABIS SETUP 1 ... SATELLITE ABIS SETUP 2 ... BTSPLUS ABIS SETUP 3 ... BTSPLUS SATELLITE ABIS SETUP 4 ... IP ABIS SETUP 1 5 ... IP ABIS SETUP 2 (FOR LONG DELAYS) 6 ... IP ABIS SETUP 3 (FOR LOW QUALITY LINES) 7 ... ENHANCED SATELLITE ABIS SETUP 8 ... STANDARD ABIS SETUPZDSE:T0011:BCSU,0:0,1:64,265-31:M,2;TRX LAPD controlled by the same BCSU as OM Lapd0- TRX LAPDZDSE:T0012:BCSU,0:0,2:64,265-31:M,2;

Creating BTSPLUS in FlexiBSCCreate BCF

Create BCF

ZEFC:4,X,M:DNAME=OM004:::::PORT0=267,PORT2=268,PORT4=269;PCM connect to BTS.PORT0/PORT2 --- the PCM interface in the BTS SiteB .... 2ND GENERATIOND .... TALK-FAMILY F .... PRIMESITE C .... METROSITE I .... INSITE P .... ULTRASITE E .... FLEXI EDGE X .... BTSPLUSBTS HW TYPE M ... MAINLINE E ... EMICRO B ... BASICBTSplus mainline: BS-240/BS-241 BS-240 II/241 II/241 II B BS-240XL BS-240XL II BS-40 II BS-40/41 BS-82 II

BTSplus eMicro: BS-82

BTSplus basic: BS-240XS BS-288

Creating BTSPLUS in FlexiBSCCreate BTS

Create Main BTS

Create other BTS in the Segment

ZEQC:BCF=4,BTS=8,NAME=GSMINGBO3:CI=49203,BAND=900, CHW=2:NCC=5,BCC=7:MNC=00,MCC=460,LAC=6378:HOP=BB,HSN1=11,HSN2=11;Cell id, BTS number in eBSC DatabaseFrom 0-2ZEQC:BCF=4,BTS=9,SEG=8,NAME=GSMINGBO3E:CHW=2,BAND=900;Cell id : same as the BTS NO. in eBSC database

Creating BTSPLUS in FlexiBSCCreate other objects :Same as creating the Flexi BTS

Create EDAP

Create TRX

ZESE:ID=268,CRCT=268-19&&-24,BCSU=0,PCU=6;ZERC:BTS=4,TRX=1:GTRX=N,DAP=N,PREF=P:FREQ=27,TSC=5,PCMTSL=267-1:DNAME=T0041:CH0=MBCCH,CH1=SDCCH,CH2=TCHD,CH3=TCHD,CH4=TCHD,CH5=TCHD,CH6=TCHD,CH7=SDCCH;ZERC:BTS=4,TRX=4:GTRX=Y,DAP=268,PREF=N:FREQ=39,TSC=5,PCMTSL=268-3:DNAME=T0044:CH0=SDCCH,TCT=TCHD;ZERC:BTS=4,TRX=1:GTRX=Y,ETRX=N,PREF=P:FREQ=27,TSC=5,PCMTSL=267-1:DNAME=T0041:CH0=MBCCH,CH1=NOUSED,CH2=LRTCH,CH3=LRTCH;ZERC:BTS=4,TRX=2:GTRX=Y,ETRX=E,PREF=N:FREQ=39,TSC=5,PCMTSL=268-3:DNAME=T0042:CH0=ERACH,CH1=SDCCH,CH2=TCHD,CH6=EGTCH,CH7=EGTCH;(Extended cells)

Creating BTSPLUS in FlexiBSCCreate other objects :Same as creating the Flexi BTS

Create Power Control parameters

Create Handover parameters

Create 2G ADJ

Create W ADJ

ZEUC:SEG=4;ZEHC:SEG=4;ZEAC:SEG=4::MCC=460,MNC=00,LAC=30027,CI=26261:NCC=4,BCC=5,FREQ=49:RAC=100;ZEAE:BTS=4::MCC=460,MNC=01,RNC=1280,CI=1472:LAC=50432,SCC=25,SAC=1472,FREQ=10713;

Review of Create BTSplus in GEMINIMultiplexing the LAPDIdentify BTS site subtypeIdentify the PCM&BPORTIdentify the CHW

Official process of BTSplus Migration in GEMINI

Official Migration Process

Official Migration Process Data export and migrationDbaemUsed in BR line to get database with a format of ASCII file.Each released BSC software load has a dedicated dbaem version.Exporter migration toolThe exporter migration tool is a new offline tool used to map BTSplus configurationdata, in the form of an eBSC/BSC1 configuration ASCII command file, to a Flexi BSC configuration file in the NetAct Configurator-compliant RAML 2.0 XML format.

exporter --bscfile --template --outfile Replace all instances of TBD with appropriate values for the mapped IDs. exporter --bscfile --ctfile

Conversion tool Control File (TBD file)

Conversion tool output (configuration script (RAML 2.0 format) suitable for importing in NetAct)

Exporter Tool Not SupprotThe exporter migration tool does not automatically migrate:eBSC/BSC1 licensing data: new Flexi BSC licenses have to be provided andinstalled according to contractGPRS configuration dataFrequency hopping system configurationExtended cell and concentric cell configurationsBTS cells with the following system indicators (SYSID):EXT900GSMDCSGSM850PCSGSM850DCSGSMR

Exporter Tool Not SupprotRequirements for additional measuresAbis loop connection between the BTSplus and the eBSC/BSC1Insufficient bandwidth on the BSS Abis interfaceAbis compression/optimization equipment is installedNon BTSplus site-specific dataExtended cellsBaseband hopping in a cell with mixed GSM/EDGE transceiver hardwareBTSplus migrated to another locationChange in BTSplus hardware configurationChange in the CGI of BTSplus cells

Process of BTSplus Migration in HLJ

Process of BTSplus Migration in HLJPreparingCheck all the related elements are available for Migration In SHMCC S14 pilot ,the Software of elements are:Check RC and LMT availableUpload eBSCs database --- eBSC The database mainly contains:BTSM HW database: BTSM type, portLAPD: LAPD PCM, LAPD TSLBTS HW basic parameters: LAC/CI/NCC/BCC/BAND/PLMN/HOPTRX FREQ&INDEX&TCH TYPEDownload the new software load to BSXXX from eBSCMonitor KPI of the Site to be rehosting

ElementSoftwareBR lineBR9029FlexiBSCS14 ??NetActOSS5.1 CDSet2 PCD

Process of BTSplus Migration in HLJ MML command generate and send to Flexi BSCCheck the new Flexi BSC is readyModify the parameters (ZEEO/ZEGO/ZOCI)Enable Features and Licenses (ZWOI/ZWOS/ZW7I)Enable the measurement report (ZTPI/ZTPM/ZTPS)Create the new SW package for BTSPLUS in Flexi BSCPrepare the MML commandPrepare the MML command according to the plan data and new PCMIntegrate the BTSPLUS in Flexi BSCCheck new configurations consistency

Process of BTSplus Migration in HLJCutoverCheck the status of eBSC and BSxxxCheck the alarms and working states of the rehosting BSxxx and the alarms of the eBSCActive the new SW load in RCAfter the GEMINI SW load active, the icon of the btsplus in RC will be out of control with grey color.Disconnect PCM from eBSC then connect to the new Flexi BSC in 20 minsThere is a timer to set automatic fallback of BSxx to BR-Abis capable software load. If the PCM cant be connected to Flexi BSC within 20 minutes, the BSxx software load will fallback to old software load that available in eBSC. Those BSxx can be afterwards managed via Radio Commander again. The timer will be disabled after BTSplus connected to Flexi BSC.Check the MSS configurationUnlock the BCF in Flexi BSCMonitor the restart phase in Flexi BSCMaybe it takes a long time to restart some BCFs, Mornitor the restart phase with ST RPHASESXUpdate the incoming ADJCheck all rehosting BTSPLUS working status, alarms, and BSC alarms

Process of BTSplus Migration in HLJ

Clean-upDelete old data in eBSC if the result of drive test is OKSafecopy in Flexi BSC

OptimizationNetwork optimization to reach measured KPIsAdapt network planning parameters to improve the KPI.

Points during cutover

The PCM should be connect to Flexi BSC within 20 mins.The LAPDs state may be down to UA-AD during the PCM cutoverMonitor the BCF restart phase, make sure all phases OK. Some sites may take more than 20 mins to finish the restart phase. Some TRX may be BL-SYS or BL-RSL or BL-RST after the BCF restart phase finish and the TRX LAPD is ok, Lock and Unlock the BTS

*****PS Traffic Handling Capacity:BSC3i 660:6 BCSUs / BSC2 PCU2-D pius / BCSU2 PCUs / PCU piu256 TCHs / PCU= 6 x 2 x 2 x 256 = 6144 @16kbit/s PS TCHs

BSC3i 2000:10 BCSUs / BSC5 PCU2-D pius / BSC2 PCUs / PCU piu256 TCHs / PCU= 10 x 5 x 2 x 256 = 25600 @16kbit/s PS TCHs

Flexi BSC (BSC3i 3000):6 BCSUs / BSC5 PCU2-E pius / BSC1 PCUs / PCU piu1024 TCHs / PCU= 6 x 5 x 1 x 1024 = 30720 @16kbit/s PS TCHs

*

Simplified cablingamount of cabling reduced standard, pre-installed internal cabling including optional unitscompact, one-cabinet configuration: no need for Intracabinet installations Configured at the factoryPre-wired and equipped with all necessary cartridges and cablesfew parts to be mounted on the site

BSC3i does not require any specific environmental conditions for operation: - no need for raised floor - no need for air conditioning

BSC3i is designed for the toughest environmentSafety: EN 60950 and UL 1950Earthquake resistance: Telcordia GR63CORE Zone 4Environmental requirements: ETSI ETS 300019-1-3, Class 3.1EEMC emission: EN 300386-2EMC immunity: FCC 15 Part 47 ETS 300119-2

Compare to AS7-B:Processor : Intel Mobile Celeron 650 MHz, 100 MHz FSB (800 MB/s) L1 Instruction cache: 16 kB L1 Write Back Data Cache: 16 kBL2 Cache: 256 kBMemory : SDRAM: 128/256 MB Capacity:Channels: 256 2M PCMs: 10***************Frequency Hopping between the bands of operation is not supported. Frequency Hopping is managed by a BTS when the segment concept is in use. In a PGSM 900 - EGSM 900 BTS, Frequency Hopping is possible on only one of the two bands. In the segment architecture the resources of different types are grouped as separate BTSs. All the resource types have the hopping parameters and the hopping groups of their own.********

flexi bsc & gemini

Documents