BSS Dimensioning Rules B6.2

BSS B6.
2 Configuration description
BSS B6.2 CONFIGURATION DESCRIPTION

DIMENSIONING RULES
Alcatel
File b62_jv_2000.doc
Reference 3DF 00928 0001 DSZZA
Date 03/01/2000
Edition 03
Page 1
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.
BSS B6.2 Configuration description
TABLE OF CONTENTS
1 2 3 4 HISTORY.............................................................................................................................................................6 REFERENCE DOCUMENTS............................................................................................................................7 SCOPE..................................................................................................................................................................7 AIR INTERFACE ...............................................................................................................................................8 4.1 RADIO CHANNELS CONFIGURATION ...................................................................................................................8 4.1.1 GPRS Impact ............................................................................................................................................8 4.1.2 Radio channels type .................................................................................................................................8 4.1.3 Rural Configurations................................................................................................................................9 4.1.4 Urban Configurations ............................................................................................................................10 4.1.5 Urban Dense Configuration ...................................................................................................................11 4.2 TRAFFIC AVAILABLE ........................................................................................................................................12 5 BTS CONFIGURATIONS................................................................................................................................13 5.1 EVOLIUMTM A9100 BTS RADIO SOLUTION ..................................................................................................13 5.1.1 General Product presentation ................................................................................................................13 5.1.2 Evolium BTS...........................................................................................................................................13
5.1.2.1 Functional description ................................................................................................................................... 13
The EvoliumTM A9100 BTS is made of the following components: .................................................................13 5.1.3 Evolium Evolution BTS ..........................................................................................................................14
5.1.3.1 Overall architecture ....................................................................................................................................... 15
5.1.4 5.1.5 5.1.6 5.1.7 5.1.8
High power GSM 1800...........................................................................................................................16 Single antenna ........................................................................................................................................16 Low losses ..............................................................................................................................................16 TMA and REK solutions .........................................................................................................................16 Multiband configurations .......................................................................................................................17
Multiband BTS.............................................................................................................................................. 17 Multiband cell ............................................................................................................................................... 17
5.1.8.1 5.1.8.2
5.2 G2 BTS IN B6.2...............................................................................................................................................18 5.3 G1 BTS IN B6.2...............................................................................................................................................18 5.4 BTS CONFIGURATIONS SUMMARY ...................................................................................................................18 6 ABIS LINKS ......................................................................................................................................................20 6.1 ABIS NETWORK TOPOLOGY ..............................................................................................................................21 6.2 MEDIUM OF ABIS NETWORK TRANSPORT .........................................................................................................21 6.3 ABIS TRAFFIC ...................................................................................................................................................22 6.4 SIGNALLING SUBMULTIPLEXING SCHEMES .......................................................................................................23 6.4.1 Presentation of concept ................................................................................................... .......................23 6.4.2 16K Static multiplexing ................................................................................................... .......................24
6.4.2.1 Limitations and Requirements............................................................................................ ........................... 24 Full Rate TRE........................................................................................................... ..................................... 25 Dual Rate TRE ........................................................................................................... ................................... 26 Limitations and requirements ............................................................................................ ............................ 26 Limitations and requirements ............................................................................................ ............................ 26
6.4.3
64K statistical multiplexing....................................................................................................................25
6.4.3.1 6.4.3.2 6.4.3.3
6.4.4
16K statistical multiplexing....................................................................................................................26
6.4.4.1
6.5 ABIS MAPPING RULES .......................................................................................................................................27 6.5.1 Support of external cross-connect ..........................................................................................................27 6.5.2 Mapping techniques ...............................................................................................................................28 6.5.3 B5 BSC G1 Mapping ..............................................................................................................................28
Alcatel
Date 03/01/2000
Edition 03
Page 2
6.5.3.1 6.5.3.2 6.5.3.3
Star Mapping (Appendix1)............................................................................................................................ 29 Closed Catalogue mapping (Appendix1)....................................................................................................... 29 B5 Free mapping ........................................................................................................................................... 29
6.5.4 7
B6.2 BSC G2 Free Mapping...................................................................................................................30
6.5.4.1 Free mapping rules ............................................................................................................................................... 30
G2 BSC CONFIGURATIONS .........................................................................................................................31 7.1 OVERVIEW .......................................................................................................................................................31 7.2 ABIS TSU CONNECTIVITY ................................................................................................................................32 7.2.1 Rules.......................................................................................................................................................32
7.2.1.1 7.2.1.2 7.2.1.3 7.2.1.4 7.2.1.5 Allocation of TSL link to TCUC ................................................................................................................... 32 Allocation of TRX and BTS to TCUC .......................................................................................................... 32 Allocation of TRX and BTS to TSU ............................................................................................................. 33 Maximum number of TRX ............................................................................................................................ 33 Maximum number of BTS/cells .................................................................................................................... 33
7.2.2 G2-BSC Half Rate Flexibility.................................................................................................................34 7.2.3 Recommendations...................................................................................................................................34 7.3 ATER TSU CAPACITY.......................................................................................................................................35 7.3.1 Rules.......................................................................................................................................................35
7.3.1.1 7.3.1.2 7.3.1.3 Multiplexing on Ater link.............................................................................................................................. 35 Number of channels and interfaces................................................................................................................ 35 SS7 links dimensioning................................................................................................................................. 35
7.3.2 Recommendations...................................................................................................................................35 7.4 PROCESSOR LOAD ............................................................................................................................................37 7.4.1 Rules.......................................................................................................................................................37 7.4.2 Recommendations...................................................................................................................................37 8 G1 BSC CONFIGURATIONS .........................................................................................................................38 8.1 OVERVIEW .......................................................................................................................................................38 8.2 ABIS CONNECTIVITY.........................................................................................................................................38 8.2.1 Rules.......................................................................................................................................................38
8.2.1.1 8.2.1.2 Allocation of TRX......................................................................................................................................... 38 Allocation of BTS and cells .......................................................................................................................... 39
8.3 ATER CAPACITY ...............................................................................................................................................39 8.3.1 Rules.......................................................................................................................................................39

8.3.1.1 8.3.1.2 8.3.1.3 Multiplexing on Ater link.............................................................................................................................. 39 Number of channels and interfaces................................................................................................................ 40 SS7 links dimensioning................................................................................................................................. 40
8.3.2 Recommendations...................................................................................................................................40 8.4 PROCESSORS LOAD ..........................................................................................................................................40 9 A935 MFS CONFIGURATIONS.....................................................................................................................41 9.1 OVERVIEW .......................................................................................................................................................41 9.2 CONSTRAINTS ..................................................................................................................................................42 9.2.1 Hardware support ..................................................................................................................................42 9.2.2 Rules.......................................................................................................................................................42
9.2.2.1 9.2.2.2 9.2.2.3 9.2.2.4 GPRS-MFS In BSC-TC Configurations........................................................................................................ 42 BSS/MFS Connectivity. ................................................................................................................................ 42 GPRS BTSs ................................................................................................................................................... 42 OMC-R/MFS Connection ............................................................................................................................. 43
9.3 A935 MFS ARCHITECTURE .............................................................................................................................43 9.4 A935 MFS DIMENSIONING ..............................................................................................................................43 9.4.1 GPU Dimensioning ................................................................................................................................44 9.4.2 GPU interfaces dimensioning.................................................................................................................44 9.4.3 Method for dimensioning the interface from the BSC to the A935 MFS ................................................47 10 ATERMUX LINKS ...........................................................................................................................................48
Alcatel
Date 03/01/2000
Edition 03
Page 3
10.1 G2 MULTIPLEXING .......................................................................................................................................48 10.2 3:1 MUTIPLEXING.........................................................................................................................................49 10.2.1 Characteristics ...................................................................................................................................49 10.2.2 Mapping consequences ......................................................................................................................49
General mapping............................................................................................................................................................... 50 10.2.2.2 Mapping rules................................................................................................................................................ 51 10.2.2.3 CICs number ................................................................................................................................................. 51
10.3 4:1 MULTPLIPLEXING ...................................................................................................................................51 10.3.1 Characteristics ...................................................................................................................................51 10.3.2 Mapping consequences ......................................................................................................................52
10.3.2.1 10.3.2.2 10.3.2.3 General mapping ........................................................................................................................................... 52 Mapping rules................................................................................................................................................ 53 CICs Number................................................................................................................................................. 53
10.4 10.5 11
COMPARISON 3:1 AND 4:1 WITH G2 BSC ....................................................................................................53 RULES OF ATER INTERFACE BETWEEN MFS AND BSC ................................................................................54
TC CONFIGURATIONS..................................................................................................................................55 11.1 G1 TC .........................................................................................................................................................56 11.1.1 Presentation .......................................................................................................................................56 11.1.2 Functional configuration ...................................................................................................................56 11.2 G2 TC .........................................................................................................................................................57 11.2.1 Presentation .......................................................................................................................................57 11.2.2 Functional configuration ...................................................................................................................57 11.2.3 New TC G2 granularity......................................................................................................................58 11.3 G2.5 TC ......................................................................................................................................................58 11.3.1 Topology ............................................................................................................................................58 11.3.2 Dimensionning ...................................................................................................................................58 11.3.3 Extension............................................................................................................................................59
12
OMC-R 1353 RA CONFIGURATIONS .........................................................................................................60 DIMENSIONING RULES ...............................................................................................................................................60 12.2 HW DESCRIPTIONS : 5 GENERIC CONFIGURATIONS .....................................................................................61 12.2.1 Server .................................................................................................................................................61 12.2.2 HMIS and Terminal. ..........................................................................................................................61 12.2.3 O&M Configuration...........................................................................................................................62 12.3 HW : OMC2 VERSUS OMC3 ......................................................................................................................63 12.4 OMC-R/BSC INTERCONNECTION ........................................................................................................63 12.4.1 Collocated BSCs without router (via simples adapters on HIS ports) ...............................................64 12.4.2 Collocated BSCs via X25 switch (Newbridge) ...................................................................................64 12.4.3 Remote BSCs via PSDN (via modem) ................................................................................................64 12.4.4 BSCs connection via Transcoder .......................................................................................................65
12.4.4.1 12.4.4.2 X25 extraction on G1 TC .............................................................................................................................. 65 X25 extraction on G2 .................................................................................................................................... 66
12.4.5
BSC CONNECTION VIA MSC ..........................................................................................................67
12.4.5.1 Characteristics ............................................................................................................................................... 67 12.4.5.2 Small configuration ....................................................................................................................................... 67 12.4.5.3 Large number of BSCs at MSC site .............................................................................................................. 68 12.4.5.4 Additional OMCRs for large networks........................................................................................................ 69 12.4.5.5 Remote configuration ......................................................................................................................................... 70 12.4.5.7 Mixed local and remote MSC configuration....................................................................................................... 71
12.5 OMC-R/MFS INTERCONNECTION........................................................................................................72 12.5.1 MFS and OMCR collocated (via an external Hub)..........................................................................72 12.5.2 MFS and OMCR not collocated (via PSDN ) ..................................................................................73
12.5.2.1 case of CISCO 2500 use................................................................................................................................ 73
12.5.3
12.5.3.1 12.5.3.2
Case of CISCO 4700 use....................................................................................................................74

Principle ........................................................................................................................................................ 74 Main advantages............................................................................................................................................ 74
Alcatel
Date 03/01/2000
Edition 03
Page 4
12.5.3.3 12.5.3.4
Technical description .................................................................................................................................... 75 BSC OMC-R connection............................................................................................................................ 76
13
GLOSSARY .......................................................................................................................................................79 Appendix 1 : Star and closed catalogue mapping...............................................................................................81
03 ED
03/01/20 00 DATE CHANGE NOTE
RCD/TD APPRAISAL AUTHORITY
RCD/CO/PCS/NOP ORIGINATOR
Alcatel
Date 03/01/2000
Edition 03
Page 5
HISTORY
21/08/98 25/10/99 Second Edition Update with : OMC-R 1353 RA GPRS Moderation Factor First Edition.
Ed. 01 Ed 02
Third edition Ed 03 Proposal 1 01/01/2000 Update with : TC G2.5 HR Flexibility Extended cell on G3 BTS Ed 03 Proposal 2 20/01/2000 Update according to review
Alcatel
Date 03/01/2000
Edition 03
Page 6
REFERENCE DOCUMENTS
[1] 3BK 10204 0467 DTZZA BSS Technical Feature List (Without GPRS) [2] 3BK 11203 0039 DSZZA Transmission Functional Specification [3] 3DC 20003 0012 UZZZA Dimensioning Rules for G2 BSC TC with BSS Software B6.2 [4] 3DC 20003 0013 UZZZA Dimensioning rules for GPRS with BSS software B6.2 [5] 3BK 11203 0055 DSZZA GPRS Traffic Model and Performances [6] 3BK 10204 0438 DTZZA General Packet Radio Service [7] 3BK 17025 0124 PGZZA B6.2 BSS Configurations Rules [8] 3DC 21006 0003 TQZZA Use of Moderation Factor for BSS traffic assessment [9] 3BK 17025 0119 PGZZA BSS O&M Routing Configurations in B6.2 [10] 3DC 20003 0010 UZZZA G2 BSC Dimensioning Rules with the BSS Software Release B5
SCOPE
This document describes the BSS dimensioning rules in Release 6.2 (SMG28 and SMG29). It gives general explanations about new hardware and software configurations and their impact in the various interfaces as regards dimensioning aspects. GPRS and statistical multiplexing on A-bis interface which are introduced in B6.2, are mainly impacting this document since B5 edition. TC A925 and BTS A9100 EVOLIUM BTS Evolutions should be introduced in B6.2.
Alcatel
Date 03/01/2000
Edition 03
Page 7
AIR INTERFACE
4.1
Radio Channels Configuration
4.1.1
GPRS Impact
GPRS radio time-slots (PDCH) are dynamically allocated according to the following customer defined parameters: MIN_PDCH_GROUP: Minimum number of PDCH TS per cell ( can be any from 0 to 8)
The operator can ensure that minimum resources is dedicated to GPRS even if the cell is fully loaded with non GPRS traffic. MAX_PDCH_GROUP: Maximum number of PDCH TS per cell ( can be any from 1 to 8) MAX_PDCH_HIGH_LOAD: Maximum number of PDCH TS per cell in case of Circuit Switched traffic overload cell ( can be any from 1 to 8)
The operator can choose the maximum GPRS traffic capacity.
The operator can prioritise non-GPRS traffic versus GPRS traffic. Those parameters allow the operator to prioritise Circuit-Switched (CS) traffic versus GPRS traffic in order for example to avoid QOS drop while introducing GPRS. Also Quality parameters could be used as the number of MS that can share a same PDCH. B6.2 Limitations: 1 TRX maximum per Cell is able to carry GPRS traffic (Up to 8 PDCH /cell) CS-1 (9.05 Kbps) and CS-2 (13.4 Kbps) channel coding schemes. A maximum of 32 mobiles can be in transfer simultaneously within a cell. As GPRS and CS are using the same channels for Paging (PCH) and Assignment (AGCH) flows, one should take care of GPRS contribution in order to avoid any congestion and especially for Combined signalling channels. Up to 240 active PDCH per GPU
4.1.2
Radio channels type

The different timeslot configurations for the transceivers of a BTS are the same in release B5 and release B6.2. PDCH TS are used for the GPRS(see 4.1.1)
Alcatel
Date 03/01/2000
Edition 03
Page 8
The allocation of SDCCH/ CCCH is depending the call mix and the position compared to the Location Area Border. (Example of Call mix 7.4 that has been used for the calculation in 4.1.3, 4.1.4, 4.1.5) Concerning TS content, several configurations are encountered, the most relevant are: Traffic channels : TCH Signalling channels: BCC = FCCH + SCH + BCCH + CCCH CBC = FCCH + SCH + BCCH + CCCH + SDCCH/4 + SACCH/4 SDC = SDCCH/8 + SACCH/8 Note: For cells used for SMS-CB, CBC or SDC signalling channels are replaced respectively by CBH and SDH. This reconfiguration is impacting SDCCH capacity so one should avoid the reconfiguration on cells that have SDCCH overload problem. The various radio channels configurations will be split up into the different call mixes but one has to keep in mind that there is no strict correlation between the geographical morpho-structure and the so called traffic mix. In order to define the number of SDC channels, we will generally associate: Rural configuration with low traffic and low SMS rate Urban configuration with high traffic and high SMS rate Urban dense configuration for traffic peak (many call attempts)
4.1.3
Rural Configurations
The traffic density is low, therefore we consider configurations with maximum 2 TRX. TRX 1 One TRX : 4 SDCCH, 7 TCH, 1 CCCH CBC TCH TCH TCH TCH TCH TCH TCH
Two TRX : 8 SDCCH, 14 TCH, 1 CCCH TRX 1 TRX 2 CBC TCH SDC TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH
Alcatel
Date 03/01/2000
Edition 03
Page 9
As a general rule, SDC are rather allocated in the first TRX in order not to lose SDCCH in case of radio recovery.
4.1.4
Urban Configurations
For microcells with medium load (max 2 TRX), we have the same configurations as rural configurations. For a number of TRX between 3 and 12, Alcatel proposes: Number of TRX 3 4 5 6 7 8 9 10 11 12 SDCCH 16 24 24 32 32 40 40 48 48 56 TCH 21 28 36 43 51 58 66 73 81 88
This is standard configuration for restricting traffic mix and might be optimised (i.e. replace some SDCCH by new TCH) depending on specific mixes. Time slot split between signalling and traffic channels on the different TRX is: TRX 1 TRX 2 TRX 3 TRX 4 TRX 5 TRX 6 BCC TCH TCH TCH TCH TCH SDC TCH SDC SDC TCH SDC TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH
Alcatel
Date 03/01/2000
Edition 03
Page 10
TRX 7 TRX 8 TRX 9 TRX 10 TRX 11 TRX 12
TCH TCH TCH TCH TCH TCH
TCH SDC TCH SDC TCH SDC
4.1.5
Urban Dense Configuration

If specific SDCCH congestion risk exists in the macrocell, a microcell linked to the macrocell is used. The microcell helps to face a heavy load in the macrocell on traffic hotspot area. One TRX microcell : 8 SDCCH, 6 TCH, 1 CCCH
TRX 1
CBC
SDC
TCH
TCH
TCH
TCH
TCH
TCH
Two TRX microcell in the same situation : 12 SDCCH, 14 TCH, 1 CCCH TRX 1 TRX 2 CBC TCH SDC TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH
Alcatel
Date 03/01/2000
Edition 03
Page 11
4.2
Traffic available
Thanks to the above-mentioned tables, one can compute the number of traffic channels in each configuration. Given a quality criterion (generally 2% on the air interface due to allocation failures), we can compute the traffic required as shown in the following Erlang B table:
Nb of TCH Offered traffic(Erl) Nb of TCH Offered traffic(Erl) Nb of TCH Offered traffic(Erl) Nb of TCH Offered traffic(Erl) Nb of TCH Offered traffic(Erl) Nb of TCH Offered traffic(Erl) Nb of TCH Offered traffic(Erl) Nb of TCH Offered traffic(Erl) Nb of TCH Offered traffic(Erl) 1 0.02 11 5.84 21 14.04 31 22.83 41 31.92 51 41.19 61 50.59 71 60.09 81 69.65 2 0.22 12 6.62 22 14.90 32 23.72 42 32.83 52 42.13 62 51.53 72 61.04 82 70.61 3 0.60 13 7.40 23 15.76 33 24.63 43 33.76 53 43.06 63 52.48 73 61.99 83 71.56 4 1.09 14 8.20 24 16.63 34 25.53 44 34.68 54 44.00 64 53.43 74 62.95 84 72.53 5 1.66 15 9.01 25 17.50 35 26.44 45 35.60 55 44.93 65 54.38 75 63.90 85 73.49 6 2.28 16 9.83 26 18.38 36 27.34 46 36.53 56 45.88 66 55.33 76 64.86 86 74.45 7 2.93 17 10.66 27 19.26 37 28.25 47 37.46 57 46.82 67 56.27 77 65.82 87 75.41 8 3.63 18 11.49 28 20.15 38 29.17 48 38.39 58 47.75 68 57.22 78 66.77 88 76.38 9 4.35 19 12.33 29 21.04 39 30.08 49 39.32 59 48.70 69 58.18 79 67.73 89 77.35 10 5.08 20 13.18 30 21.93 40 31.00 50 40.26 60 49.64 70 59.13 80 68.69 90 78.31
Traffic available (2% of blocking rate)

80 70 60 50 40 30 20 10 0 1 2 3 4 5 6 7 8 9 10 11 12 Nb of TRX
Erlang
Erl
Alcatel
Date 03/01/2000
Edition 03
Page 12
BTS CONFIGURATIONS
5.1
EVOLIUMTM A9100 BTS Radio Solution
5.1.1
General Product presentation

Alcatel has introduced since 1998, the EVOLIUM A9100 Base Stations. To respond to the customer demand of new services in a very integrated way, the A9100 Base stations have been evolved. For B6.2 , the major impact is the introduction of the Multi-Band Cell configurations and from B6.2 SMG29-1 each delivered BTS will be Evolium Evolution Step1. There are two types of Evolium cabinets: indoor cabinet with two sizes Mini and Medi. outdoor cabinet with two sizes Mini and Medi EVOLIUM
A9100 Base Station
1 sector 1 to 4 TRXs 1 to 4 TRXs 2 to 8 TRXs
2 sectors 1 to 2 TRXs per sector 1 to 2 TRXs per sector 1 to 6 TRXs per sector
3 sectors 1 TRX per sector 2 TRX* per sector 1 to 4 TRXs per sector
Mini Indoor Mini Outdoor Medi Indoor/Outdoor Extended cell:
* New configuration with Evolium Evolution A minimum of 4 TRX in the extended inner cell and a minimum of 4 TRX in the extended outer cell are required.
5.1.2
Evolium BTS
5.1.2.1 Functional description

The EvoliumTM A9100 BTS is made of the following components: antennas Twin RFE and Duplexer Stage modules that provide filtering and low noise amplifying functions
Alcatel
Date 03/01/2000
Edition 03
Page 13
Twin Wide Band Combiner Stage modules which is a wide band combiner on the downlink path and a splitter on the uplink path TRX modules which embrace modulating and frequency hopping functions SUM board which ensures operation and maintenance functions and provides the clock to the BTS.
This modularity allows configurations such as:

TM TM
EVOLIUM EVOLIUM TM TM EVOLIUM EVOLIUM TM EVOLIUM Duplexer
Duplexer
Combiner Duplexer Combiner
TRX TRX TRX TRX TRX TRX
Combiner
Combiner
TRX TRX TRX TRX TRX TRX TRX TRX
1 sector 2 TRX
1 sector 4 TRX INCORPORER.
1 sector 8 TRX
5.1.3
Evolium Evolution BTS
This EVOLIUM Evolution is done in a two step approach available in B6.2 SMG29-1
- EVOLIUM Evolution Step 1 contains following features: - Merging of ANx and ANy functionality in one new module, ANc; this integration providing: - a compactness which is used to build new configurations, - an easiest maintenance policy (reducing the number of spares). - Optimization of the SUM module, providing a future-proof board, which is prepared to handle a third and fourth Abis link, or to integrate a GPS receiver or similar additional equipment through baby-boards directly plugged on the SUM board.
Alcatel
Date 03/01/2000
Edition 03
Page 14
- Integration of base-band part of micro-wave (IDU) in indoor and outdoor cabinet, building a complete integrated solution; this choice simplifying the installation and maintenance process, and reducing logistics costs. - Introduction of new configurations, such as: - 3x2 TRX configuration available in an Outdoor Mini cabinet, reducing the purchasing price and optimizing the floor space of an often used configuration in rural environment, - 3x4 TRX configuration in an AC Indoor cabinet, which avoids the use of an external power supply cabinet, allowing to save floor space and to reduce acquisition, installation and maintenance costs of an often used configuration in urban environment. - EVOLIUM Evolution Step 2 contains following features: - Introduction of a new TRX module with EDGE provision (8-PSK and GMSK modulation schemes), to answer to the increasing demand for highest data flow services. - Improved baseband processing with enhanced antenna diversity algorithms to improve the Alcatel network quality of service.
5.1.3.1 Overall architecture

The BTS architecture for the EVOLIUM Evolution is identical to that of all known A9100 configurations. It is based on a three level architecture, consisting of: - Antenna coupling level - Transceiver (TRX) level - Base Station Control Function (BCF) level
The information flow between the Air interface and the Abis interface is presented in the figure below.
Alcatel
Date 03/01/2000
Edition 03
Page 15
Air interface
Antenna network stage

ANc
Antenna network stage

ANc
Antenna coupling level Combiner stage (ANy) Combiner stage (ANy)
TRX level
TRX
TRX
TRX
TRX
TRX
TRX
TRX
TRX
TRX
TRX
TRX
TRX
BCF level
Station unit module Abis interface
Abbreviations BCF Base station Control Function TRX Transceiver
5.1.4
High power GSM 1800

High power GSM 1800 consists in using a specific TRX module for GSM 1800. This high power TRX is a solution to provide enhanced coverage solutions. Duplexer and combiner modules are reused without any change.
5.1.5
Single antenna
All the single antenna configurations use the new antenna network module RFE Duplexer and Combiner Stage which is defined as half duplexer + half combiner in a single box. Its architecture is:
5.1.6
Low losses
Low loss configurations are obtained by removing a Combiner stage and adding if necessary a Duplexer stage
5.1.7
TMA and REK solutions

The Tower Mounted Amplifier (TMA) is a low-noise amplifier that allows to compensate the losses incurred by received signals. The TMA solution can be used with any A9100 BTS configurations. TMA is specially recommended for HighPower configurations with up to 2 TRX per sector.
Alcatel
Date 03/01/2000
Edition 03
Page 16
The Range Extension Kit (REK) is a two-way amplification box that allows to enhance the radio performance of the A9100 BTS configurations in terms of cell coverage (including both Booster and TMA functionality i.e Transmitted and Received signal amplification). The REK solution is available only in GSM900 frequency band. Moreover, REK can not be associated to A9100 configurations including Wideband combiners (ANy):
Configuration Standard Standard Standard Low-loss Others Number of sector 1 sector 2 sector 3 sector 1 sector Others Condition GSM900 GSM900 GSM900 GSM900 Not allowed Preequipment Yes/No No No No No Not allowed Minimum number Maximum number of TRXs per sector of TRXs per sector 1 1 1 3 Not allowed 2 2 2 4 Not allowed
5.1.8
Multiband configurations
5.1.8.1 Multiband BTS

That consists in using the GSM 900 and 1800 bands in different sectors of the BTS. Multiband BTS configurations (900/1800).
5.1.8.2 Multiband cell

Those configurations consist of having 900 and 1800 TRX in each sectors of the BTS (BCCH in GSM 900 only). The following table shows BSS generation equipment versus PLMN radio band. Yes = a G2 BSC G1 BSC G3 BTS M4M BTS M1M BTS M2M BTS G2 BTS G1 MKII.BTS GSM 900 a a a a a a a GSM1800 a a a a N.A a a N.A GSM 1900 a N.A a1 N.A N.A N.A a N.A Multiband 900/1800 BTS a a a a N.A N.A N.A N.A Cells a N.A a a N.A N.A N.A N.A
Restricted in SMG28
Alcatel
Date 03/01/2000
Edition 03
Page 17
Multi-band BTS: That consists in using the GSM 900 and 1800 bands in different sectors of the BTS. Multi-band BTS configurations (900/1800). Multi-band cell: Those configurations consist of having 900 and 1800 TRX in each sector of the BTS
5.2
G2 BTS in B6.2
G2 BTS configurations are still unchanged, except M3M which is no more supported. However, G2 BTS with FUCO are not supporting GPRS feature and G2 BTS with FUMO have a restricted GPRS usage (CS-1 channel coding only: 9.05 Kbps). G2 BTS extended cell is not more supported.
5.3
G1 BTS in B6.2
G1 BTS MK1 (HW1,HW2) have to be removed. MK2 BTS are still authorised but replacement of FUCO module by DRFU is nescessary for GPRS support. Rmk : All G1 BTS Compact have to be removed. They are not supported since B5.
5.4
BTS configurations summary

How to read this summary? choose the BTS type select the sector-TRX configuration: as regards the number of TRX, only the maximum configuration has been reported, e.g. 1x8 TRX configuration embraces all configurations from 1x1 to 1x8. choose the line corresponding to your specific options: single antenna, low losses, highpower, indoor AC feeding
NB: for each configuration, availability has to be checked with an Alcatel representative
Alcatel
Date 03/01/2000
Edition 03
Page 18
A9100 EVOLIUM BTS / A910 Micro-BTS

Type NB of sectors Nb of TRX
6LQJOH EDQG
GSM GSM 900 1800 GSM 1900 High indoor Single Low power AC antenna losses 1800 Power
Multi-band
New B6
Multiband BTS
Multiband Cell
Mini ,QG2XW 2XW ,QG2XW ,QG2XW Medi ,QG2XW 2XW

[ [ [ [
; ; ; ;
; ; ; ; ; LQGRRU RQO\
; ;

[
; ; ; ; ;
[ SUH HT ; ,QG2XW [ ,QG2XW [ ,QG [ ,QG2XW [ ,QG2XW ;; ,QG2XW ; ,QG2XW ; ,QG2XW ,QG2XW [ ,QG2XW [ ,QG2XW [ ,QG2XW [ ,QG [ ,QG2XW [ ,QG2XW [ 2XW ; ,QG2XW ,QG2XW ,QG2XW [ [ ,QG2XW [ [ ,QG2XW [ [ A910 Micro-BTS A910 2w ; A910 2w [ A910 2w ; A910 2w ; A910 2w ;
; ; ;
; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
; ; ;
; ; ; ;
; ; ; ; ;
; ; ; ; ;
; ; ; ; ;
Alcatel
Date 03/01/2000
Edition 03
Page 19
G2 BTS
Type Nb of sectors Nb of TRX GSM 900 GSM 1800 GSM 1900 Air combining Optional AC Power
0LQL ,QG2XW 2XW 6WG ,QG P ,QG P ,QG P 2XW P 2XW P ,QG P ,QG P ,QG P ,QG P ,QG P 2XW P 2XW P 0LFUR 00 00

[ [ [ [ [
; ; ; ; ; ; ; ; ; ; ; ; ;
; ;
; ; ; ;
; ;
G1 BTS
Type Characteristics Nb of sectors Nb of TRX GSM 900
MK2 MK2 MK2
Std Std+DRFU
1 1
8 8
X X
ABIS LINKS
The Abis interface is standard ITU-T G.703 / G.704 interface. It is based on a frame structure. The frame length is 256 bits grouped in 32 timeslots numbered from 0 to 31. The rate of each timeslot is 64 kbit/s. On the Abis interface, the important feature introduced available in release B.6.2 is the statistical signalling submultiplexing 16K and 64K. In B6.2, the Qmux can be suppressed and the supervision is done through OML ( 6.3) Before presenting these aspects, available topologies on Abis interface will be reviewed.
Alcatel
Date 03/01/2000
Edition 03
Page 20
6.1
Abis network topology

For a functional point of view, two topologies are specified to physically connect the BTS to the BSC. 1STAR topology: One PCM link connects only One BTS to BSC. It is maintained awaiting shifting out from the field all G1 BTS. The star topology will be migrated as a particular case of a chain with one BTS for a BSC G2. 2Open Multi-drop topology CHAIN: One PCM link connects up to 15 BTS (Statistic multiplexing) in serial order and the PCM is not looped back to BSC by the last BTS. In chain topology, the BSC is connected with Abis link to a BTS. This one is connected to a second BTS with a second Abis link, the second BTS is at its turn connected to a third one and so on.
C h a in T o p o lo g y
BTS
BTS
BTS
A b i s lin k
3- Closed Multi-drop topology RING: One PCM link connects up to 7 BTS in serial order and the PCM is looped back to BSC by the last BTS. In ring or loop topology, the last BTS of a chain is connected back to the BSC. This topology offers some security since traffic between any BTS and BSC is broadcast on the two paths, selection is based on dedicated Service bits / bytes. (e.g. please see next section).
BTS
BTS
Abis link BTS
Ring / loop Topology
6.2
Medium of Abis network Transport

There are several means to transport Abis Over Networks: 1- Terrestrial link mean called PCM 2Mbits/s link (64 Kbits * 32 Time Slots = 2048 Kbits/s). 2- Microwave link same capacity or higher. 3- Digital Cross-connect Network equipment, which concentrates 4, 16 or 64 PCM 2Mbits link. Hub Microwave equivalent to DCN
Alcatel
Date 03/01/2000
Edition 03
Page 21
6.3
Abis traffic
This table presents the three types of channels to be mapped onto the transmission links.
Channel type
Q mux(O&M transmission supervision) Ring control
Ring control R bits Synchronisation controls S bits
TS position
TS 0 (TS 0 usage) Other TS except TS 0 (TS0 transparency)
Purpose
Used by the BSC to manage Remote Transmission Network Elements. used in ring topology only
Other TS except TS0 Any TS (except if G1 generation)
Supervision of Ring continuity Direction of clock synchronisation
BTS channels
TCH OML RSL Other TS except TS0 Other TS except TS0 Other TS except TS0 End user traffic LAPD channel for BTS (1 OML per BTS) LAPD channel for TRX (1 RSL per TRX)
The Mapping is defined by: 1. TS bearing the Qmux 2. The presence or not of Ring control channel. 3. Allocation Rules of PCM TS to the BTS with Multiplexed Channel Block motifs. This table gives a quick view of timeslot budget depending on Qmux channel position: Supervision TS0 Open Chain MD Closed MD Loop 30 29 By QMux Transparency Usage 31 30 31 29 By OML Transparency Usage N.A N.A
Note 1: On transmission point of view, one must look carefully at one point :
A BTS with 3 sectors with 4 TRX in each sector is in fact: - 3 BTS of 4 TRX with G2 BTS which corresponds to 3 OML and 12 RSL. - 1 BTS of 3x4 TRX with Evolium RSL.
TM
A9100 BTS which corresponds to 1 OML and 12
Alcatel
Date 03/01/2000
Edition 03
Page 22
6.4
6.4.1
Signalling submultiplexing Schemes

Presentation of concept
The signalling submultiplexing offers improvement in terms of required PCM time slots on the Abis interface. This leads to substantial savings in terms of Abis interface trunks. In B6.2, three types of signalling submultiplexing will be offered : 16K Static multiplexing: Up to 4 RSL of a BTS are multiplexed on the same Abis timeslot. 64K Statistical multiplexing: Up to 4 RSL and optionally the OML of a BTS are multiplexed on the same Abis TS. 16K Statistical multiplexing: The RSL and optionally the OML of a BTS are multiplexed in the first 2 bit of the TS reserved for TCH handling (the first one of the two TS dedicated to handle the traffic of the TRX).
Note : See constraints in paragraph 7.2.1.2

16K Static Multiplexing Signalling TS* 1/1 1/1 1/1 1/1 2/1 2/1 2/1 2/1 3/1 3/1 3/1 3/1 Total 4 6 8 10 13 15 17 19 22 24 26 28 64K Statistical Multiplexing Signalling TS* 1/0 1/0 2/0 1/0 2/0 2/0 3/0 2/0 3/0 3/0 4/0 3/0 Total 3 5 8 9 12 14 17 18 21 23 26 27 16K Statistical Multiplexing Signalling TS* 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/0 Total 2 4 6 8 10 12 14 16 18 20 22 24
No Multiplexing Number Of FR TRX Traffic Channel per TRX Signalling TS* (RSL/OML) 1 TRX 2 TRX 3 TRX 4 TRX 5 TRX 6 TRX 7 TRX 8 TRX 9 TRX 10 TRX 11 TRX 12 TRX 2 4 6 8 10 12 14 16 18 20 22 24 1/1 2/1 3/1 4/1 5/1 6/1 7/1 8/1 9/1 10/1 11/1 12/1 4 7 10 13 16 19 22 25 28 31 -
Total
* Signalling TS are described as follow: RSL/OML
Note:. The activation of a signalling submultiplexing schemes is done by BTS. The activation by sector is only possible for 64k statistical multiplexing.
Alcatel
Date 03/01/2000
Edition 03
Page 23
Yes = a G2 BSC G1 BSC BTS G3 + M4M-S G2 with DRFU G2 without DRFU G2 MICRO G1 MKII DRFU with
RSL & OML TS 64Kbits/s a a a a a a a a
RSL 16Kbits Static Multiplex a
RSL&OML Statistical Multiplex 64 Kbits/s a 16 Kbits/s a
a a
G1 MKII without DRFU
6.4.2
16K Static multiplexing

The RSL of a FR TRX require only 16 kbit/s. It is therefore possible to pack up to four RSL into one 64 kbit/s PCM time slot on the Abis interface trunk. Therefore, a PCM time slot may be shared between the RSL of the same BTS HW equipment. That means: a BTS with 1 to 4 TRX use 1 PCM time slot for the RSL 16 kbit/s a BTS with 5 to 8 TRX use 2 PCM time slot for the RSL 16 kbit/s The OML is still carried on a full 64 kbit/s PCM time slot.
6.4.2.1 Limitations and Requirements

BTS should be connected to a G2 BSC.
TM A910 supports the static multiplexing. Also BTS In micro-BTS, only Evolium TM A9100 or G2 BTSs equipped with DRFU module support static Evolium multiplexing (The SMBI module has to be upgraded to ICS 16 for G2 BTS).
Each TRX is carrying a maximum of 8 SDCCH channels.
Not compatible with DR and HR mode.
Alcatel
Date 03/01/2000
Edition 03
Page 24
6.4.3
64K statistical multiplexing

The Abis channels for this multiplexing scheme may be seen as a group of MCB (Multiplexed Channel Block) : Three types of MCB have then been defined in accordance to the number of TRX to be handled. Name MCB 64/4 MCB 64/2 MCB 64/1 MCB 64/1 Nb of TRX Nb of Abis 64 k OML: RSL TS used 4 2 1 1 9 5 3 3 (0 or 1) :4 (0 or 1):2 (0 or 1):1 (0 or 1):1 Compatibility FR Only FR or DR FR or DR FR or DR
When several MCBs are used for a BTS, the OML is mapped on the MCB which has the lower SDCCH load.
6.4.3.1 Full Rate TRE

A BTS with N FR TRE configured with 64K statistical multiplexing requires: (N/4) MCB 64/4 one MCB 64/1 when N mod 4 = 1 (BTS with 1, 5 or 9 TREs) one MCB 64/2 when N mod 4 = 2 (BTS with 2, 6 or 10 TRES) one MCB 64/1 and one MCB 64/2 when N mod 4 = 3 (BTS with 3, 7 or 11 TREs). This configuration is used instead of MCB 64/3 to allow a better usage of TCU resources at the BSC. It consists of splitting the last 3 RSL into 2 Abis-TS. The 2 fractions can be mapped on 2 different TCUs.
Number of FR TRE per BTS 1 2 3 4 5 6 7 8 9 10 11 12 list of physical MCBs 64/1 64/2 64/2; 64/1 64/4 64/4; 64/1 64/4; 64/2 64/4; 64/2; 64/1 64/4; 64/4 64/4; 64/4; 64/1 64/4; 64/4; 64/2 64/4; 64/4; 64/2; 64/1 64/4; 64/4; 64/4 Maximum SDCCH weight per MCB 24 32 32;24 32 32; 24 32; 32 32;24;24 32; 32 32; 32; 24 32; 32; 32 32; 32; 32;24 32; 32; 32
Alcatel
Date 03/01/2000
Edition 03
Page 25
6.4.3.2 Dual Rate TRE

A BTS with N DR TRE configured with statistical multiplexing includes ((N-1)/2)+1 MCBs of which: (N/2) MCB 64/2 (N mod 2) MCB 64/1 Dual rate attribute is now introduced per TRE and not anymore per BTS. As a result, only the TRXs using the DR mode must follow the rules concerning DR TRXs in particular the possibility to connect 2 TRXs-DR per TCUC.
6.4.3.3 Limitations and requirements

G2 BSC and Evolium A9100/910 BTS.
6.4.4
16K statistical multiplexing

On the PCM link, two 64Kb/s timeslots are needed per TRE (128 Kb/s per TRE, 8 times 16Kb/s). Each RSL -which maybe statistically multiplexed with the OML- takes the place of the first 16Kb/s sub-channel reserved for the associated TRE on the PCM link. As for 64K statistical multiplexing, Abis transmission can be seen as a sequence of MCB 16/1.
MCB 16/1
TS n0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 Bit 8
N n+1
RSL FU1 + OML
FU1 TCH 2 FU1 TCH 6
FU1 TCH 3 FU1 TCH 7
FU1 TCH 4 FU1 TCH 8
FU1 TCH 5
The OML is always multiplexed with the RSL with the highest RSL number of any BTS sector.
6.4.4.1 Limitations and requirements

G2 BSC and Evolium A9100/910 BTS. Each TRX should carry a maximum of 8 SDCCH channels. Not compatible with DR mode. TS0 on Air Interface must not hold TCH channel (But a signalling channel: BCC,SDC) Recommendation: with Abis multiplexing statistical 16k, BTS downloading at busy hour should be avoided in order not to delay call set-up time
Alcatel
Date 03/01/2000
Edition 03
Page 26
6.5
Abis mapping rules

Installation of the new BSS software release 6.2 has no impact on the Abis TS mapping. The control channels (Qmux, Sbits, R bits) as well as the BTS channels (TCH, RSL, OML) are not remapped as a consequence of software upgrade. Signalling submultiplexing is compatible with all types of transmission mappings, star and closed catalogue excepted. GPRS has no impact on Abis mapping because PDCH are dynamically allocated on this interface. This part presents first some mapping techniques supported in previous software versions, star and closed catalogue mapping. Secondly, the free mapping is described. The open decreasing mapping and full allocation mapping, defined in B.4, are now part of free mapping techniques.
6.5.1
Support of external cross-connect

When cross-connects are used on Abis it is needed to have different numbers for Abis TSs used by the BTS (Qmux bus, OML, RSL and TCHs) on BTS connector and on BIUA connector. This flexibility is supported by the introduction of TS mapping table between BTS connectors and BIUA connectors. This TS mapping table is introduced by the operator via the OMC-R and applied by the BSC when a new BTS-BIE configuration is needed due to a modification of the Abis TSs allocation. In order to keep the B6 principle of auto-allocation of TREs, this TS mapping table will be introduced during the operation Create an Abis chain/ring. But to keep also a relative flexibility on the TS allocation within the TS reserved for each branch connected to the cross-connect, the operator must be able to select also the TSs usable by each BTS during the Create BTS operation. It is also important to note that the OMC-R operator must be able to change at any time the TS mapping table attached to one Abis chain/ring or to modify the TSs usable for each BTS.
Alcatel
Date 03/01/2000
Edition 03
Page 27
BTS 2 TS 2 to 6
BTS2
Branch 1 Branch 2 BSC

BTS1
Branch 3
BTS 1 TS 2 to 4 BTS 2 TS 11 to 15 BTS 3 TS 21 to 24 BTS 3 TS 2 to 5
BTS3
Constraints of cross-connect usage on Abis Cross-connect usage on Abis is supported only if the following rules are applied: Rule n 1 : One BTS uses (for itself and for the forwarded Abis link) only timeslots of a PCM, which comes from a single BIUA connector. Rule n 2: If Qmux is used, the BTS needs to be connected to the Qmux TS. The other Branch has to use OML if possible (Evolium BTS). Note: AND and BROADCAST function on the Qmux timeslot are always needed in the intermediate cross-connect in order to respect rules n 2, if this function is not possible the Qmux bus is not implemented and the downloading of the transmission settings is performed via OML (if supported (Evolium BTS)) or locally.
6.5.2
Mapping techniques
Up to now, there are 4 techniques introduced during different releases: 1- Star Mapping: introduced before B4. 2- Closed Catalogue : Introduced before B4 (Appendix1) 3- Open Catalogue: Introduced in B4 4- Free Mapping: Introduced in B5: with Q1 TS fixed at TS0, TS1, option (TS16 or TS18). 5- Free Mapping in B6.2 : the Q1 can be slotted anywhere in TS from TS0 to TS31 B5 mapping techniques are migrated but not exist anymore in B6.2, they are replaced by free mapping
6.5.3
B5 BSC G1 Mapping
After B5-B6 migration, the BSCG1 is still running in B5, thus the Abis interface stay with the following mapping.
Alcatel
Date 03/01/2000
Edition 03
Page 28
6.5.3.1 Star Mapping (Appendix1)

The star configuration is the configuration used in star topology. It is configured in two modes: TSO usage: Qmux on TS0. TS0 transparency: Qmux on TS 19. The star configuration is the only one configuration supported by G1 transmission interface equipment named BIU2M, composed of one SMHW plus one or two SMBS. Restriction: STAR mapping with TS0 Usage is forbidden with SMBI, SMFG, SUMP. The Static Sub-multiplexing RSL 16Kb/s is not supported.
6.5.3.2 Closed Catalogue mapping (Appendix1)

Closed catalogue is used for chain or Ring topology in TS0 usage. Qmux and S bits use the TS0. The allocation of TS for the BTS is fixed one for all. The advantage of this rule is that the Add or delete BTS/TRE has no impact on other BTS on the same link. RSL 16k sub-multiplexing is not compatible with closed catalogue.
6.5.3.3 B5 Free mapping

"Free mapping" means that the BTS channels can be mapped on any free PCM timeslot. The assignment of the Abis TS can be performed automatically using the free mapping rule either for new Abis links or for modifications. In Free mapping, the Time Slots of the Abis frame are allocated freely by CMA. The only restriction is that the TCH of a TRE are always on 2 consecutive TS. Five options are available:
Topology Chain Mapping option TS1 Option OD1 S bits Qmux TS 1 R bits for new links/ from existing open decreasing . Ring Mapping TS18+RS OF1 TS 17 TS 18 TS 31 for new links/ from existing Full allocation R1 TS16+RS TS1+RS TS1+R OF2 OF3 OF4 TS 15 TS 17 TS 1 TS 16 TS 1 TS 1 TS 31 TS 2 TS 2 from existing Full allocation R2 For new links (Mix BIU2M, G1, G2, G3) For new links (BIUMD, G2, G3)
Alcatel
Date 03/01/2000
Edition 03
Page 29
Note: Free mapping offers the best TS budget associated taking into account the static multiplexing with a great flexibility. The Abis Mapping is performed by CMA in order not to reconfigure the BTS already on the link. With BSC G1, in case configuration tool has to find a pair of contiguous TS to accommodate the TCH of a TRE although only isolated TS are available, it shall autonomously shift a block of BTS channels or move a timeslot to create the required physical resource. Remark: In B6.2 BSC G1 remains at B5 SW functionnality, it does not support any B6.2 feature (like GPRS for example...). Operations between BSC G1/B5 and BSC G2/B6.2 are allowed and supported (move BTS, Abis,....)
6.5.4
B6.2 BSC G2 Free Mapping

For G2 BSC the same options are offered but no more restrictions are imposed for TSC channels, only BTS equipment may bring restrictions.
6.5.4.1 Free mapping rules

Star, open and closed catalogue are migrated but not exist anymore in B6.2, after B5-B6 migration, they follow B6.2 free mapping rules. The migration left unchanged the Abis mapping. Operator reserved Abis TS per Abis (range of TS from TSi to TSj) (i and j from 0 to 31 and j>I). Operator defined per BTS the usable TS inside the range defined on the Abis. Operator defines TS per TS which one correspond to which BTS. For a given BTS only timeslots defined as usable for this BTS can be allocated by the BSC. For an Abis chain/ring, only timeslots defined as usable within this Abis chain/ring can be allocated by the BSC. For any BTS except Evolium BTS: the 2 timeslots needed to carry the traffic channels over Abis must be contiguous. For Evolium BTS: the 2 timeslots needed to carry the traffic channels over Abis need not be contiguous, but the first set of 4 traffic channels (TRX-TS 0..3) must always be on a lower Abis-TS than the second set (TRX-TS 4..7) any timeslot of an Abis chain/ring is either free or occupied, and it is either usable or unusable 1The Qmux, Rbits and Sbits can be slotted in any Time Slot from TS0 to TS31. 23BSC. The Channels OML and Q1 can be slotted anywhere by the operator. The Channels RSL, TCH are slotted in any available Time Slot by the
Alcatel
Date 03/01/2000
Edition 03
Page 30
G2 BSC CONFIGURATIONS
7.1
Overview
The G2 BSC consists in one switch and 3 main sub-units (TSU): Abis TSU which determines the connectivity with BTS Ater TSU which sets the capacity the BSC can handle common TSU
Group Switch 8 Planes 2 Stages
Abis TSU
TCUC TCUC
Ater TSU
DTCC DTCC DTCC DTCC DTCC DTCC DTCC
6x G.703 Abis I/F

BIUA
TCUC TCUC TCUC TCUC TCUC TCUC
ASMB
AS
AS
DTCC
ASMB
2x G.703 Ater muxed I/F
TSL
Q1 bus
AS
TSCA
CPRC CPRC CPRC CPRC CPRC CPRC CPRC CPRC
Broadcast bus
Common Functions TSU
Since B5 release, 6 configurations of G2 BSC are offered: Configuration 1 2 3 4 5 6 Racks 1 1 2 2 3 3 Abis TSU Ater TSU 1 4 6 9 11 14 2 3 5 6 8 9
Alcatel
Date 03/01/2000
Edition 03
Page 31
7.2
7.2.1
Abis TSU connectivity

Rules
7.2.1.1 Allocation of TSL link to TCUC

TSL is a LAPD link connecting the TCUC to the TSC (Transcoder Submultiplexer Controler). The TSC is in charge of the supervision of the transmission part of the BSS equipment. It polls the NE and collects the alarms indications. After correlation process it sent the list of the active alarms to OMC_R. The TSL/TCU mapping is fixed.
TSL links G2 BSC BIUA number (BSC-Adapt SBL nbr) TSL 1 (first rack) TSL 2 (second rack) TSL 3 (third rack) 1 6 11 1 41 81 TCU number
The TSL when present uses one of the six LapD controllers of the G2 TCU.
7.2.1.2 Allocation of TRX and BTS to TCUC

Each TCUC can handle 6 signalling links (LAPD such as RSL, OML or TSL) which allows excepting TSL which have been presented previously: 4 RSL+ 2 OML 3 RSL+ 3 OML 4 Full Rate TRXs 2 Dual Rate TRXs
Each TCUC can handle 32 Traffic channels which allows:
Each TCUC can handle either Full Rate or Dual Rate traffic. Each TCUC can handle 32 SDCCH channels. However, in case of 16K Signalling Multiplexing (Static or statistical 16kbit/s) each TRX can carry 8 SDCCH channels maximum. Each TCU can handle a maximum of 3 cells due to processing power to handle CCCH signalling In case of Signalling Multiplexing: 16K Static multiplexing: all RSLs of a given 64 kbit/s Abis time-slot must be handled by the same TCUC or by two adjacent TCU (TCU1 and 2, TCU 3 and 4..).
Statistic Multiplexing: All RSL and OML multiplexed are processed on the same TCU. Mix of the different signalling multiplexing and not multiplexed signalling on the same TCU is allowed for Full Rate. Mix of none and statistical multiplexing 64 k is now allowed for Dual Rate.
Alcatel File b62_jv_2000.doc Reference 3DF 00928 0001 DSZZA Date 03/01/2000 Edition 03 Page 32
7.2.1.3 Allocation of TRX and BTS to TSU

all TRXs of all BTSs of a same Abis multidrop must be connected to a single Abis TSU each Abis TSU can handle 6 Abis links which allows: maximum 3 ring configuration (looped multidrop) maximum 6 chain configuration (open multidrop or star configuration)
a maximum of 16 Dual Rate TRX assigned to a maximum of 16 BTS may be connected to a single Abis TSU each Abis TSU holds 8 TCUC TRXs of one BTS cannot be split between two different Abis PCM, thus in two different Abis TSU. Abis TSU may mix FR and DR cells
7.2.1.4 Maximum number of TRX

Configuration 1 2 3 4 5 6 Full Rate TRX 32 128 192 288 352 3521 Dual Rate TRX 16 64 96 144 176 224
7.2.1.5 Maximum number of BTS/cells

Full rate mode Configuration 1 2 3 4 5 6 Max nb of BTS 23 95 142 214 255 2551 Max nb of cells 32 128 192 264 264 264 Dual rate mode Max nb of BTS 16 64 96 144 176 224 Max nb of cells 16 64 96 144 176 224
1 This is a software release limitation.
Alcatel
Date 03/01/2000
Edition 03
Page 33
7.2.2
G2-BSC Half Rate Flexibility
Currently GSM network operators see the HR as a way to extend the capacity of their network without any additional hardware deployment (i.e. without any extra significant cost). The gradual HR introduction is done by allowing the operator to define each individual TRE as Full Rate or Dual Rate (provided the BTS hardware is compatible). This allows to control the HR ratio on a per cell basis. In addition a DR-preferred parameter is introduced at TRX level. The need to choose the speech coding rate per TRX comes from Telecom constraints; it allows in particular to select DR-preferred for TRXs with a good radio quality. The speech coding rate of a TRX requested by the OMC operator is a preference; it can be changed by the system if no mapping is possible ( TRE and TCU may be of the same type) it can also be changed if justified by the protection of a TRX (carrying BCCH or SDCCHs) during a recovery Nothing (or little) is changed to the TCU management : FR TREs are mapped to a FR TCU which can support four of them DR TREs are mapped to a DR TCU which can support two of them The TCUs of a TSU are allocated, by the BSC, to support FR or DR TREs according to the mapping algorithm. As TREs are to be mapped on either FR or DR TCUs, this implies that the two types of TREs need to be put in separate MCBs (i.e. their RSLs cannot be multiplexed together, which asks for at least two A-bis SIG TSs). Warning : This feature does not provide help to the operator to deal with the fact that allowing HR calls in a cell will increase the signalling load and may ask for more SDCCH channels. The operator should configure a relatively higher number of SDCCH on DR TRXs and a relatively lower on FR TRXs. Since TCUs can either handle 2 DR TRXs or 4 FR TRXs, this leads to spreading more evenly the signaling load.
7.2.3
Recommendations
When using Signalling Multiplexing, if the detailed Abis topology is not known, then one should not connect more TRXs than 85% of the maximum connectivity. When selecting among the different possible Abis TSU in order to connect a given BTS, one has advantage to leave some spare capacity in all Abis TSUs so as to allow extensions in every Abis TSU.
Alcatel
Date 03/01/2000
Edition 03
Page 34
7.3
Ater TSU capacity
This section enables to determine the traffic offered by the G2 BSC in the various configurations.
7.3.1
Rules
7.3.1.1 Multiplexing on Ater link

Since B5, 4:1 multiplexing is available on the Ater interface which impacts the capacity of the G2 BSC. For more details about multiplexing constraints, refer to 10. Thus, we will hereafter describe the characteristics of Ater capacity according to each multiplexing scheme. As regards equipment, one cannot mix G1 and G2 transcoding-submultiplexing equipment.
7.3.1.2 Number of channels and interfaces

1:3 mux Configuration A ITF Ater ITF 1 12 4 2 18 6 3 30 10 4 36 12 5 48 16 6 54 18 CICs PCM nb 356 4 536 6 894 10 1074 12 1432 16 1612 18 1:4 Mux Configuration A ITF Ater ITF 1 16 4 2 24 6 3 40 10 4 48 12 5 64 16 6 72 18 CICs PCM nb 454 4 686 6 1148 10 1380 12 1842 16 2074 18
7.3.1.3 SS7 links dimensioning

Exactly one channel is reserved for SS7 link on each Atermux link. Alcatel default dimensioning rule is to use all the SS7 links, thus leading to the following table with a call mix like 7.4.1
Configuration SS7 links 1 4 2 6 3 10 4 12 5 16 6 16
Remark: with configuration 6 Atermux trunks 17 and 18 do not convey SS7 links; however, TS 16 is left unused and does not convey any traffic channels. With a modified call mix, speech holding time superior to 80 seconds. The rule is one SS7 link for 2 PCM + 1 SS7 link. Which yields : for config 1 to 6, respectively 3, 4, 6,7, 9 and 10 SS7 links.
7.3.2
Recommendations
The default dimensioning rules to be used on the Ater interface are: 0.1% of blocking rate OR 80% of the maximum load which corresponds to 24 Erl/PCM When using those maximum Erlang values, one should take into account a moderation factor to be applied on busy hours traffic calculation.
1:4 Mux (Erlang) Configuration 1 2 3 4 5 6 0.1% blocking rate 160 627 1074 1300 1753 1800 24 Erl/PCM 160 576 960 1152 1536 1728
1:3 Mux (Erlang) 0.1% blocking rate 160 483 828 1002 1351 1527 24 Erl/PCM 160 432 720 864 1152 1296
When dimensioning a network, one must check that the maximum traffic generated by the different BTSs does not exceed the maximum traffic handling capacity of the BSC to which they are connected. When subscriber density and traffic per subscriber are known, the traffic generated by the BTSs serving those subscribers can be immediately derived; but when only the number and size of BTSs are known, the traffic must be assessed. To do so, a first traditional approach is: - to evaluate the maximum traffic generated by each cell (taking into account its number of TRXs and applying the Erlang B law ), - to sum all those traffics, - and then compare this sum to the maximum handling capacity of the BSC.
Optimized approach : use of the Moderation Factor However, it has been noticed that the actual traffic incurred by the BSC is generally significantly lower than the theoretical traffic calculated as above (this theoretical calculation does not account for the fact that the maximum traffic is not reached simultaneously in each cell, or that not all the TRXs of a BTS or all the Traffic Channels of a TRX are fully used; see [8] for more details). To account for this and avoid over-estimating the number of BSCs necessary for a given network, the notion of Moderation Factor has been introduced: the Moderation Factor is defined as the ratio between the actual traffic incurred by the BSC at its busy hour and the theoretical traffic figure obtained by summing the maximum traffic generated by each connected cell according to the Erlang B rule. The value of the Moderation Factor can vary very significantly depending on the network context; except for very dense urban areas, a maximum value of 0.8 may already be used; significantly lower values may even be used in many cases as described in document [10]. The recommended approach to check that the traffic generated by the BTSs does not exceed the capacity of the BSC is then:
Alcatel
Date 03/01/2000
Edition 03
Page 36
- to evaluate the maximum traffic generated by each cell (taking into account its number of TRXs and applying the Erlang B law ), to sum all those traffics, - to multiply this sum by the Moderation Factor - and then compare the value obtained to the maximum handling capacity of the BSC. (It must be noted that using the Moderation Factor is also recommended for the assessment of the number of A Interfaces and of Transcoders)
7.4
7.4.1
Processor load
Rules
The processor load depends on the amount of signalling events generated by the subscribers with a given traffic. Alcatel commitments rely on a traffic mix, also called virtual call mix because its BHCA (busy hour call attempt) was brought to 1 by a rule of three in order to compare different traffic mixes. Alcatel warrants that, provided that none of the characteristics of the virtual call mix applied to the G2 BSC exceed the value in the following table the BSC will function correctly. Event Mean TCH duration Paging messages LU ratio Internal HO External HO MO SMS MT SMS IMSI attach IMSI detach Unit S paging message per s LU per call attempt per call attempt per call attempt per call attempt per call attempt ratio of IMSi attach per call attempts ratio of IMSi detach per call attempts G2 BSC 50 70 3 2 1 0.1 0.4 0.5 0.5
7.4.2
Recommendations
If any of the characteristics of the required call mix exceed the above standard mix then, as long as other characteristics are relaxed it is very likely that the G2 BSC will be able to process the required traffic. However, in all such cases Alcatel must analyse the requirement to determine whether it is feasible.
Alcatel
Date 03/01/2000
Edition 03
Page 37
G1 BSC CONFIGURATIONS
8.1
Overview
With the G1 BSC, the TSUs are not taken into account in the definition of the standard configurations and the Abis submultiplexers (BIE) are individually configurable in separate transmission cabinet. Thus G1 BSC can be represented as follow:
TCU TCU DTC DTC
ABIS
S M
SWITCH
S M
ATER
TCU
CPRA
DTC
G1 BSC
There are 2 families of G1 BSC: 2A types which exist in 5 configurations 2B types which exist in 4 configurations
Racks 1 1 2 2 2 TCU 8 20 32 44 52 A ITF 6 6 9 12 15 2B Configuration 1 2 3 4 Racks 1 1 2 2 TCU 12 28 44 60 A ITF 6 8 9 15
2A Configuration 1 2 3 4 5
8.2
8.2.1
Abis connectivity
Rules
8.2.1.1 Allocation of TRX

With G1 BSC, TCU rules become: 1 TCUA can handle
Alcatel
2 TRX with 2A configurations 1 TRX with 2B configurations

File b62_jv_2000.doc Reference 3DF 00928 0001 DSZZA Date 03/01/2000 Edition 03 Page 38
1 TCUA can handle a maximum of 8 SDCCH half rate mode is not supported
2B Configuration Nb of TCUA Nb of TRX 1 2 3 4 12 28 44 60 12 28 44 60
2A Configuration Nb of TCUA Nb of TRX 1 2 3 4 5 8 20 32 44 52 16 40 60 60 60
NB: In case of 2A configurations, if one wants to connect an odd number of TRX to the BSC, one has to reserve the Abis TS corresponding to upper even number of TRX.
8.2.1.2 Allocation of BTS and cells

G1 BSC transmission constraints: each sector is considered as a BTS submultiplexing equipment must be inserted between G1 BSC and connected BTSs the maximum connectivity of the submultiplexing equipment is 24 PCMs signalling multiplexing is not supported a maximum of 40 BTSs can be connected a maximum of 40 cells can be connected
2A Configuration Nb of BTS/cell 1 2 3 4 5 8 20 32 40 40 2B Configuration Nb of BTS/cell 1 2 3 4 12 28 40 40
Maximum capacities of G1 BSC:
8.3
8.3.1
Ater capacity
Rules
8.3.1.1 Multiplexing on Ater link

With G1 BSC, one can only multiplex 3 Ater onto 1 Atermux link and multiplexing schemes are detailed in 10. However, one must not forget the following equipment rules: despite both G1 and G2 transcoding and submultiplexing equipment are available with this release, they cannot be mixed.
Alcatel
Date 03/01/2000
Edition 03
Page 39
submultiplexing is mandatory on Ater interface; however, existing sites which didnt use submultiplexing (between G1 BSC and G1 TC) are still supported.
8.3.1.2 Number of channels and interfaces

2A Configuration
1 2 3 4
5
A ITF 6 6 9 12
15
CICs 176 176 266 356

446
PCM nb 2 2 3 4
5
2B Configuration
1 2 3 4
A ITF 6 8 9 15
CICs 176 236 266 446
PCM nb 2 3 3 5
8.3.1.3 SS7 links dimensioning

On each A interface, one channel is reserved to allow SS7 link conveyance. Alcatel strongly advises the customer to set one SS7 link for 3 plugged-in DTC in the BSC configuration. This leads to the following configurations:
2A Configuration
SS7 links
2 2 3 4 5
2B Configuration
SS7 links
2 3 3 5
1 2 3 4
5
1 2 3 4
The Alcatel filling rule for those SS7 links is to set 2 SS7 links on the first Atermux link, 2 SS7 links on the second Atermux link, 1 SS7 link on the third Atermux link, and none on the 2 remaining ones.
8.3.2
Recommendations
One has to check the following points: the number of A interface is compatible with the BSC configuration (see 8.3.1.2) the load computed with a quality criterion (0.1% of blocking rate or a percentage of maximum load) remains below the reference table:
2A Configuration Traffic capacity (Erl) 2B Configuration Traffic capacity (Erl)
1 2 3 4
5
80 140 210 280

320
1 2 3 4
60 140 210 320
8.4
Processors load
The characteristics of BSC configurations have been tested with the following contractual call-mix:
Alcatel
Date 03/01/2000
Edition 03
Page 40
Event Mean TCH duration Paging messages LU ratio Internal HO External HO MO SMS MT SMS IMSI attach IMSI detach
unit s paging message per s LU per call attempt per call attempt per call attempt per call attempt per call attempt ratio of IMSi attach per call attempts ratio of IMSi detach per call attempts
G1 BSC on DTC 90 15 3 1 0.5 0.1 0.1 0.1 0.1
The above characteristics are relevant with a processor load remaining under 60% of its maximum capacity. Remark: G1 BSC can handle the call-mix described in 7.4.1 with a capacity of 120 Erlang.
A935 MFS CONFIGURATIONS
9.1
Overview
Alcatel has developed the BSS part of GPRS with all dedicated hardware in a new equipment, named A935 Multi-BSS Fast packet Server (A935 MFS). The figure below show the MFS position in the overall GSM network
OMC-R IMT SGSN
BTS
Abis Abis
MFS (PCU) BSC Ater
Gb Ater TC
Gb MSC A
Alcatel
Date 03/01/2000
Edition 03
Page 41
The A935 MFS is mainly composed of GPU (GPRS Processing Units) boards providing the Gb interface towards the data packet-dedicated network and the Packet Control function.
9.2
9.2.1
Constraints
Hardware support
Briefly, GPRS is supported with the following BSS Hardware:
BTS G1 MK2 with DRFU BTS G2 with FUMO (CS-1 only and 8 bit access burst, instead of 11) BTS BTS G2 with DRFU BTS Evolium Micro M1M, M2M, M4M BSC TC G2 BSC. TC G1 (With Gb link direct MFS-SGSN) TC G2 (With Gb link direct MFS-SGSN or Through MSC)
Refer to GPRS Technical Feature List for more details.
9.2.2
Rules
9.2.2.1 GPRS-MFS In BSC-TC Configurations

Rule 1: GPRS is possible In BSS: BSC G2 in front of G2 TC with SM 4:1 or 3:1. Rule 2: GPRS is possible In BSS: with Generic G1 TC and BSC G2 Rule 3: The Gb Interface can not be routed across G1 TC. Rule 4: The Gb interface can be routed via G2 TC to SGSN across MSC.
9.2.2.2 BSS/MFS Connectivity.

Rule 5: MFS can be connected only to one OMC-R A1353 A. Rule 6: All BSSs connected to the same MFS and this MFS are managed by the same OMC-R A1353 A . Rule 7: The BSSs connected to the same MFS can be linked to different MSC.
9.2.2.3 GPRS BTSs

Rule 8: All following BTSs: A9100 EVOLIUM BTS (G3), A9100 EVOLIUM BTS Evolutions (G4.2), A910 Micro-BTS (M4M-S), G2 and MKII with DRFU and Micro BTS support GPRS with Coding Scheme 1 and 2. Rule 10 : G2 BTS with FUMO support GPRS with restrictions: 11 bits Access burst format is not supported. Only code scheme CS-1 is supported
Alcatel
Date 03/01/2000
Edition 03
Page 42
9.2.2.4 OMC-R/MFS Connection

Rule 9 : If MFS on OMC-R site, a Hub is necessary to perform the connection the connection of 2 cables (1 from each AS800) to only 1 cable towards the OMC.( Cisco 2500 can be also used)Rule 10 : If MFS on MSC site, and CISCO 4700 router already installed, use of CISCO Rule 11 : Other situation, connection via leased lines or X25.
9.3
A935 MFS Architecture

The A935 MFS is made from 1 to 2 telecom subracks, each one handling from 2 to 12 GPU boards (Including one for redundancy). The granularity is one GPU board. Each GPU board have 16 PCM interfaces. On each PCM, the timeslots to be processed can be selected using the internal 64Kbps switch and in addition, any timeslot on one PCM can be transparently connected to any timeslot on its own or any other PCM.
G PU board GPU board G PU board
2048 kbit/s PCM30 Interfaces
GPU board GPU board
100 Mbit/s Ethernet Interfaces
Ethernet link (Redundancy) Ethernet link
Server
Server
Ethernet Hub
Ethernet External Interfaces
9.4
A935 MFS Dimensioning

All the BSS connected to a single MFS must be managed by the same OMC-R (Managing also this MFS). There can be more than one MFS in a MSC area but one MFS shouldnt be shared by several MSCs unless they are collocated.
Alcatel
Date 03/01/2000
Edition 03
Page 43
A A935 MFS can handle up to 22 BSS (22 GPU boards + 2 for redundancy) and is connected to one or more SGSN with a granularity at GPU level.
BSS with GPRS feature.

A BSS GPRS site configuration could be defined by combination: (Release / BSC / TC / MFS/ BTS): Release is B6.2. BSC is G2. TC is G2 or G1 generic. BTS are Evolium, G2, G1.
9.4.1
GPU Dimensioning
Each GPU board can handle : Up to 240 active PDCH (Packet Data Channels). A single BSS can only be handled by a single GPU. Up to 2880 Mobiles in packet transfer mode (Taking an average of 6 MS/ PDCH). Up to 264 routing areas (RA).
9.4.2
GPU interfaces dimensioning

A te r m u x A te r m u x A
Transcoder
BSC
;
<
M SC
M FS
G b
SG SN
S e r v in g G P R S S u p p o rt N o d e
X, Y, Z and Z represent the following interfaces : X : Ater-Mux links between BSC and MFS, Y : Ater-Mux Links with mixed CS and GPRS traffic between MFS and MSC through TC, Z : Direct Gb links between MFS and SGSN, Z : Number of Gb links between MFS and SGSN through MSC. Gb is the interface used to connect MFS to SGSN (directly or through TC and MSC)
Alcatel
Date 03/01/2000
Edition 03
Page 44
One X link may be: Dedicated to GPRS traffic (Full GPRS) then Z or Z options are available to connect SGSN. Mix of GPRS and non-GPRS (CS) traffic then Y option may be used to connect SGSN node.
As the switch in the MFS is a 64kbits/s switch, GPRS TS allocation on Ater interfaces shall be performed on a 3 by 3 basis (3:1 Ater submultiplexing) or 4 by 4 basis (4:1 Ater submultiplexing). Static TS allocation is used on X and Y interface. 1 GPRS TS on X require the availability of 1 Gb TS on Y, Z or Z( Nb_X 8 and Nb_Y+Z+Z 8). X interface includes: The GPRS Signaling Links (GSL) to support the GPRS signaling between the A935 MFS and the BSC (64K Channel). At least 2 GSL TS per GPU should be allocated on different Atermux for redundancy purpose (However one GSL TS is authorized but not advised). The GPRS traffic channels (GCH) to support the GPRS traffic between the A935 MFS (PCU function) and the GPRS radio traffic channels (PDCH) in the BTS.
X and Y interface granularity: Atermux TS for CS Full 7/8 Null3 Null Atermux TS for GPRS Null 1/8 Dedicated4 Full
3 4
Atermux is going through TC. No perturbation of the existing GSM architecture.
Alcatel
Date 03/01/2000
Edition 03
Page 45
G2 BSC&G2 TC AterMux Rack 1 1 2 3 4 5 6 Rack 2 7 8 9 10 11 12 Rack 3 13 14 15 16 17 18
X25 Y/N Y/N N N N N N N N N N N N N N N N N
Q1 Y Y N N N N Y Y N N N N Y Y N N N N
N7 = YES GSM GSM Mix GSM & GPRS GSM Mix GSM & GPRS
N7 = NO N.A N.A GPRS
GSM Mix GSM & GPRS GSM Mix GSM & GPRS
N.A N.A GPRS
GSM Mix GSM & GPRS GSM Mix GSM & GPRS
N.A N.A GPRS GPRS or GSM or Mixed GSM & GPRS
AterMux GPRS configuration
Restrictions:
The AterMux number 1 is always used for CS and never for GPRS channels. Dedicated GPRS links cannot be the first two Atermux of each BSC rack because Qmux is conveyed on these links. Atermux used for dedicated GPRS, does not carry Q1, X25 and N7. TS0 usage is not used with BSC G2. Only one GSL max per Atermux is supported : X+Y+Z <= 16. When The AterMux transport Mixing Traffic X=Y The GPU AterMux Connections example scenarios are: On TS28 of the Ater mux link for both 1:3 and 1:4 mappings. On TS16 of the 2d Ater tributary in 1:3 mapping On TS28 of the 2d Ater tributary in 1:4 mapping
Alcatel
Date 03/01/2000
Edition 03
Page 46
Scenario 1 2 3 4
X 8 6 8 8
Y 8 6 4 0
Z 0 4 4 8
With scenario 1, CS traffic goes to MSC through TC and PS traffic goes to SGSN through TC-MSC. With scenario 2, CS traffic goes to MSC through TC and PS traffic goes directly to SGSN. With scenario 3, CS traffic goes to MSC through TC and PS traffic goes directly to SGSN. With scenario 4, there is no CS traffic TC and PS traffic goes directly to SGSN.
9.4.3
Method for dimensioning the interface from the BSC to the A935 MFS
Each active PDCH is handled by one 16 kbit/s Ater Multiplexed channel. In order to calculate the total number of Ater- Multiplexed time-slots to reserve for GPRS traffic on the Ater interface, one should: First, assess the average number of Radio Time-slots (PDCH) that will be really used by GPRS traffic on all the cells connected to the BSC at the busy hour. This number is significantly lower than the sum for all cells of the Maximum number of time-slots configured for potential GPRS usage by the Operator. Then, apply the Erlang B law to the above number of radio time-slots which are actually used by GPRS traffic, applying a blocking probability derived from the Quality of Service (QoS) required by the Operator. Remark: Due to the sharing of PDCHs between users, the probability to reject one additionnal user is lower than this blocking probability. Further more, not allocating a PDCH does not systematically imply that the GPRS transfer will not occur. - Then, apply the Ater multiplexing ratio (1:4 in the general case, but 1:3 is also possible) , and add two 64kbit/s time-slots for the GSL links and finally apply the above granularity rule in order to determine the total number of Ater multiplexed time-slots (64kbit/s) required. Remarks: - The Ater connectivity of the BSC is sufficient in most cases to allow allocation for GPRS without reducing the non-GPRS traffic capacity of the BSC.
Alcatel
Date 03/01/2000
Edition 03
Page 47
- The Ater-mux PCMs which do not convey GPRS traffic can still be directly connected to the Transcoder equipment, bypassing the MFS. Furthermore, the first Ater-mux PCM must always be connected directly to the Transcoder equipment and never carries GPRS; this allows seamless GPRS introduction without service interruption. - One MFS can be connected to several SGSN units.
10 ATERMUX LINKS
As far as Atermux(BSC-MFS) is impacted by GPRS introduction, please refer to 9.4.3 for GPRS Atermux dimensioning.
10.1 G2 multiplexing
The second generation of BSC and transcoder had introduced a fourth DTC/TRAU module among the BSC and TC as shown below:
Since B5 release, the multiplexing of 4 Ater interfaces onto 1 Atermux interface is allowed. Thus, 4:1 multiplexing is only possible with configuration BSC-G2/TC-G2. 3:1 multiplexing is sill supported, with the same mapping as in B4.
Alcatel
Date 03/01/2000
Edition 03
Page 48
10.2 3:1 mutiplexing

10.2.1 Characteristics
can be used with any generation of equipment allows to multiplex 3 Ater PCM onto 1 Atermux PCM mapping is the same on all tributaries TS0 usage for Qmux or TS0 transparency
10.2.2 Mapping consequences

Although TS0 usage is possible if we are not using second generation equipment, we will only describe TS0 transparency. TS0 usage only difference is the possibility to reuse TS 31 (reserved for Qmux ) for one more traffic channel.
Alcatel
Date 03/01/2000
Edition 03
Page 49
10.2.2.1 General mapping

Shelf 1/Tributary 1/PCM1 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 SS7 17 18 19 20 21 22 23 24 25 26 27 28 29 30 49 50 51 52 53 54 55 56 57 58 59 60 61 62 X25 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 Shelf1/Tributary 2/PCM2 1 2 3 4 5 6 7 8 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Shelf1/Tributary 3/PCM3 1 2 3 4 5 6 7 8 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Shelf 2/Tributary 1/PCM5 1 2 3 4 5 6 7 8 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 SS7 145 146 147 148 149 150 151 152 153 154 155 156 157 158 177 178 179 180 181 182 183 184 185 186 187 188 189 190 X25 191 used for channel if no X25 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 Shelf2/Tributary 2/PCM6 1 2 3 4 5 6 7 8 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 Shelf2/Tributary 3/PCM7 1 2 3 4 5 6 7 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207
63 used for channel if no X25
: not available
1 2 1 33 65 5 37 69 9 41 73 13 45 77 17 49 81 21 53 85 25 57 89 29 61 93 Ater muxn 3 4 5 6 2 3 34 35 66 67 Alarm 1 6 7 38 39 70 71 Alarm 2 10 11 42 43 74 75 Alarm 3 14 15 46 47 78 79 X25/unused 18 19 50 51 82 83 1/SS7 22 23 54 55 86 87 2/SS7 26 27 58 59 90 91 3/SS7 30 Qmux 62 94 95 7 8 4 36 68 8 40 72 12 44 76 1 2 129 161 193 133 165 197 137 169 201 141 173 77 20 52 84 24 56 88 28 60 92 145 177 209 149 181 213 153 185 217 157 189 221 Ater muxn+1 3 4 5 6 7 130 131 162 163 194 195 Alarm 1 134 135 166 167 198 199 Alarm 2 138 139 170 171 202 203 Alarm 3 142 143 174 175 78 79 X25/unused 146 147 178 179 210 211 1/SS7 150 151 182 183 214 215 2/SS7 154 155 186 187 218 219 3/SS7 158 Qmux 190 222 223 8
132 164 196 136 168 200 140 172 204
148 180 212 152 184 216 156 188 220
31 for Qmux on Atermux1 and 2 63 used for channel if no X25
159 for Qmux on Atermux1 and 191 used for channel if no X25
Alcatel
Date 03/01/2000
Edition 03
Page 50
10.2.2.2 Mapping rules

Ater interface TS16 reserved for SS7 conveyance only TS31 used either for traffic channel or Qmux (Tributary 1) TS31 optionally used for X25 (Tributary 2) TS 4, 8, 12 reserved for alarms TS 20, 24, 28 reserved for SS7 TS 16 reserved for optional X25 information Qmux on the 2 PCM of the first Ater interface of the first rack (on the first tributary) with G1 BSC each rack (on the first tributary) with G2 BSC
Atermux interface
Connectivity
optional X25 on the 2 PCM of the first Ater interface of the first rack (on the second tributary)
10.2.2.3 CICs number

TS0 transparency: As explained above, one Ater link conveys either 30 channels either 29 channels (if it has Qmux or X25 on TS31). Thus, we can identify 3 mapping configurations: 90 CICs: multiplexing 3 Ater without X25 and without Qmux 89 CICs: multiplexing 3 Ater with Qmux on TS31 of one tributary 88 CICs: multiplexing 3 Ater with Qmux on TS31 of one tributary and X25 on TS31 of another tributary
TS0 usage: In this case, Qmux is conveyed on TS0 which frees 1 CIC per Atermux containing Qmux, which gives 2 configurations: 90 CICs: multiplexing 3 Ater without X25 89 CICs: multiplexing 3 Ater with X25
10.3 4:1 multpliplexing

10.3.1 Characteristics
allows to multiplex 4 Ater PCM onto 1 Atermux PCM usage of G2 BSC and G2 TC is mandatory TS0 transparency (TS0 usage forbidden with G2 BSC) Qmux conveyance (mandatory on determined Atermux links, and forbidden on others)
Alcatel
Date 03/01/2000
Edition 03
Page 51
Transmission of remote alarms (alarm octet) on each PCM X25 links conveyed on Atermux TS is optional transmission of up to one SS7 channel per PCM
10.3.2 Mapping consequences 10.3.2.1 General mapping

The multiplexing of 4 Ater interfaces onto 1 AterMux link including SS7, X25, remote alarms and Qmux is realised as follow (First two AterMux):
Shelf1/Tributary 1/PCM1 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13 Shelf1/Tributary 2/PCM2 1 2 3 4 5 6 7 8 33 34 35 36 37 38 39 40 41 42 43 44 45 46 SS7 17 18 19 20 21 22 23 24 25 26 27 28 29 30 49 50 51 52 53 54 55 56 57 58 59 60 61 62 X25 14 used for channel if no Qmux 31 used for channel if no X25 127 used for channel if no X25 81 82 83 84 85 86 87 88 89 90 91 92 93 94 113 114 115 116 117 118 119 120 121 122 123 124 125 126 Shelf1/Tributary 3/PCM3 1 2 3 4 5 6 7 8 65 66 67 68 69 70 71 72 73 74 75 76 77 78 Shelf1/Tributary 4/PCM4 1 2 3 4 5 6 7 8 97 98 99 100 101 102 103 104 105 106 107 108 109 110
: not available
Shelf2/Tributary 1/PCM5 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 129 130 131 132 133 134 135 136 137 138 139 140 141 Shelf2/Tributary 2/PCM6 1 2 3 4 5 6 7 8 161 162 163 164 165 166 167 168 169 170 171 172 173 174 SS7 145 146 147 148 149 150 151 152 153 154 155 156 157 158 177 178 179 180 181 182 183 184 185 186 187 188 189 190 X25 142 used for channel if no Qmux 159 used for channel if no X25 191 used for channel if no X25 223 used for channel if no X25 255 used for channel if no X25 209 210 211 212 213 214 215 216 217 218 219 220 221 222 241 242 243 244 245 246 247 248 249 250 251 252 253 254 Shelf2/Tributary 3/PCM7 1 2 3 4 5 6 7 8 193 194 195 196 197 198 199 200 201 202 203 204 205 206 Shelf2/Tributary 4/PCM8 1 2 3 4 5 6 7 8 225 226 227 228 229 230 231 232 233 234 235 236 237 238
: not available
Alcatel
Date 03/01/2000
Edition 03
Page 52
1 2 1 2 3 4 5 6 7 8 9 10 11 12 13 Qmux
Ater muxn 3 4 5 6 33 65 34 66 35 67 36 68 37 69 38 70 39 71 40 72 41 73 42 74 43 75 44 76 45 77 46 78 Alarm octet SS7 49 81 50 82 51 83 52 84 53 85 54 86 55 87 56 88 57 89 58 90 59 91 60 92 61 93 62 94 X25
1 2 129 130 131 132 133 134 135 136 137 138 139 140 141 Qmux
Ater muxn+1 3 4 5 6 7 33 65 34 66 35 67 36 68 37 69 38 70 39 71 40 72 41 73 42 74 43 75 44 76 45 77 46 78 Alarm octet SS7 177 209 178 210 179 211 180 212 181 213 182 214 183 215 184 216 185 217 186 218 187 219 188 220 189 221 190 222 X25
97 98 99 100 101 102 103 104 105 106 107 108 109 110
97 98 99 100 101 102 103 104 105 106 107 108 109 110
17 18 19 20 21 22 23 24 25 26 27 28 29 30
113 114 115 116 117 118 119 120 121 122 123 124 125 126
145 146 147 148 149 150 151 152 153 154 155 156 157 158
241 242 243 244 245 246 247 248 249 250 251 252 253 254
14 replaced by Qmux if used 31, 63, 95, 127 used for channels if no X25
142 replaced by Qmux if used 159, 191, 223, 255 used for channels if no X25
10.3.2.2 Mapping rules

one Qmux on the 2 PCM of the first Ater TSU of each rack of the BSC if X25 is used, it is implemented on the 2 PCM of the first Ater TSU of the first rack the alarm octet is meant to report technical hitches on any DTC so it must be conveyed on each PCM of each Ater TSU one SS7 channel per Atermux link
10.3.2.3 CICs Number

According to these rules, we can identify 3 mapping configurations: 111 CICs : mapping including Qmux, X25, SS7, alarm octet 115 CICs : mapping including Qmux, SS7, alarm octet 116 CICs : mapping including SS7, alarm octet
10.4 Comparison 3:1 and 4:1 with G2 BSC

If we consider G2 BSC in configuration 6, with TS0 transparency, the CICs numbering could be summarised with the following table:
Alcatel
Date 03/01/2000
Edition 03
Page 53
X25
Ater TSU 1 RACK 1 Ater TSU 2 Ater TSU 3 Ater TSU 4 RACK 2 Ater TSU 5 Ater TSU 6 Ater TSU 7 RACK 3 Ater TSU 8 Ater TSU 9
PCM 1 PCM 2 PCM 1 PCM 2 PCM 1 PCM 2 PCM 1 PCM 2 PCM 1 PCM 2 PCM 1 PCM 2 PCM 1 PCM 2 PCM 1 PCM 2 PCM 1 PCM 2
Qmux
x x
Alarm
x x x x x x x x x x x x x x x x x x
SS7
x x x x x x x x x x x x x x x x x x total CICs
CIC number 3:1 mux 4:1 mux

88 88 90 90 90 90 89 89 90 90 90 90 89 89 90 90 90 90 1612 111 111 116 116 116 116 115 115 116 116 116 116 115 115 116 116 116 116 2074
(x) (x)
x x
x x
10.5 Rules of Ater interface between MFS and BSC

The A935 MFS equipment is generally co-located with the Transcoding equipment and with the MSC (for economical reasons). The Ater interface between the MFS and the BSC multiplexes CS (Circuit Switched) traffic, GPRS traffic (proprietary protocol MFS/BTS), and GPRS signalling link (GSL using also a proprietary protocol MFS/BSC). The number of time-slots (64kbits/s) assigned to GPRS (within the Ater Multiplexed interface from the BSC to the A935 MFS) is statically allocated by the Operator. This number of time-slots can be changed from the OMC-R, and must always respect the following rules: - Granularity: The number of time-slots dedicated to GPRS can be 4, 8, 15, 22, 29 per Ater Multiplexed PCM, and even several complete PCMs, up to 8, can be assigned to GPRS. These numbers must include the time-slot(s) dedicated to the GSL (GPRS signalling link). Indeed, there is minimum 1 time-slot per BSC dedicated to the GSL, and preferably 2 for security reasons; these 2 time-slots should be placed on 2 different Ater Multiplexed PCMs. - Maximum configuration: The maximum number of Ater Multiplexed PCMs that can be connected to one GPU is 8.
Alcatel
Date 03/01/2000
Edition 03
Page 54
- Security split: For security reasons, the time-slots assigned to GPRS should be spread among different Ater Multiplexed PCMs (the data which do not concern GPRS will be ignored by the A935 MFS and transparently conveyed to the Transcoding equipment). However, when there is enough GPRS traffic to fill 2 or more PCMs, there is an advantage to dedicate complete PCMs to GPRS rather than mixing GPRS with CS traffic. Doing so avoids connecting the A935 MFS to the Transcoding equipment, with Ater Multiplexed PCMs not fully devoted to circuit-switched traffic, and thus avoids wasting transcoder resource. - Minimum configuration: It is strongly recommended for security reason to have minimum 2 Ater Multiplexed PCMs connected to the A935 MFS, each one carrying 4 time-slots minimum dedicated to GPRS (however, connection of only 1 Ater Multiplexed PCM is allowed.)
11 TC CONFIGURATIONS
Up to now, there are three generations of transcoder: 1. G1 TC installed in the field in front of G1 BSC. 2. G2 TC installed in the field in front of G2 BSC (or BSC G1). 3. G2.5 TC New Transcoder coming up to be introduced in B6.2 SMG29. The main architecture of Transcoder is Sub-Unit, which is compounded by: One SMU Sub-Multiplexing Units One or more TRCU Transcoding Unit.
The realisation of those units, are different from generation to another. Here after summary of technical data overall generation transcoder.
Alcatel
Date 03/01/2000
Edition 03
Page 55
G1 TC Rack Number Type Size mm AterMux per rack Mapping A interfaces SMU TRCU CIC Traffic 0.1 Blocking % Up to two 19 600 * 450 3 3:1 9 SMHW+LK2M DB2M+DX2M TC16 9*31 238 E S12
G2 TC Up to 3 900*520 6 3:1 or 4:1 18 or 24 ASMC ATBX DT16 18 or 24*31 682 E 19
G2.5 TC One 600*600 48 3:1 or 4:1 192 MT120 192*31 5811 E
11.1 G1 TC
11.1.1 Presentation
The Transcoding equipment G1 can be used in conjunction with G1 BSC and G2 BSC. However, the internal cabling and rack lay-out of G1 TC are different whether it is connected to a G1 BSC or a G2 BSC. Dual rate transcoder units will not be available with G1 TC but with G2 TC.
11.1.2 Functional configuration

The following table presents extension capability of G1 TC: Extension
from basic configuration from other configuration
Nb of Ater
Nb of TRCU
2 3
The following table presents available configurations for G1 TC:
Alcatel
Date 03/01/2000
Edition 03
Page 56
Configuration
TC-SM G1 4/2 TC-SM G1 6/2 TC-SM G1 9/3 TC-SM G1 12/4 TC-SM G1 15/5 TC-SM G1 18/6
Nb of rack
Nb of SM-Ater unit
Nb of TRCU
1 1 1 2 2 2
2 2 3 4 5 6
4 6 9 12 15 18
Please note that the Sub-multiplexer includes the Ater interface. Two fully equipped G1 TC racks (3 SM/9 TRCU each) match exactly the capacity of a G2 BSC rack (3:1 multiplexing scheme)
11.2 G2 TC
11.2.1 Presentation
The G2 TC can be associated with both types of BSC: G1 and G2. The G2 TC allows 24 A interfaces, so 24 TRCU (Transcoder Rate adapter Control unit). The basic TRCU, which interfaces one A interface and one Ater interface, is composed of one ATBX board and two DT16 boards. The Ater submultiplexing function is realised by the ASMC board, maximum 4 TRCU linked to 1 ASMC.
11.2.2 Functional configuration

G2 TC rack configurations match with G2 BSC rack configurations, maximum 3 racks G2 TC for 3 racks G2 BSC. The following table presents different configurations for the TC SubMultiplexer: Configuration Basic Extension step Maximum Nb of Rack 1 3 Nb of submultiplexer 2 1 18 (3*6) Nb of TRCU (3:1) 6 1 54 (3*18) Nb of TRCU (4:1) 8 1 72 (3*24)
The following table presents equipment capability for a TC rack:
Alcatel
Date 03/01/2000
Edition 03
Page 57
Configuration Minimum of 1 rack Extension Maximum

st
Nb of submultiplexer 2 1 6
Nb of TRCU (3:1) 6 1 18
Nb of TRCU (4:1) 8 1 24
11.2.3 New TC G2 granularity

The purpose of this granularity is to reduce the number of DT16 on a standard G2 TC configuration in order to match each time exactly the number of A interface facing the TC. Tributaries 1 and 2 of Atermux 1 and 2 must have their DT16 (i.e. DT16 of TRCU 1, 2, 5 and 6 must be present). Tributary 1 of every other Atermux must have their DT16. ATBX boards are not removed, and not connected to the MSC. ATBX settings are downloaded even if DT16 are not present
11.3 G2.5 TC
11.3.1 Topology
The TC G2.5 can be used for extension of TC G2 (possibility of mixing TC G2 and TC G2.5 within a BSS); for TC G1/G2 replacement and for new BSSs. For TC G1/G2 replacement, one TC G2.5 can replace several G1/G2 TC racks. The TC G2.5 can be equiped with up to 48 sub-units called MT120 boards. Each MT120 offers an Atermux connection to a BSC and up to 4 Atrunk connections to the MSC, so that the TC G2.5 offers up to 192 Atrunk connections to MSC. The TC G2.5 is shared between several BSC G2: one MT120 board in any slot of any subrack can be allocated to any Atermux of a BSC G2. These BSCs can belong to several OMCs. TC G2.5 in front of BSC G1 and mixing 3 : 1 and 4 : 1 within the same BSS is not allowed
11.3.2 Dimensionning
Each TSC (there is one TSC per G2 BSC rack) is used to manage one TC G2 rack (which contained up to 6 Atermux) : this group of 6 Atermux is called a cluster . In TC
Alcatel
Date 03/01/2000
Edition 03
Page 58
G2.5, a group of up to 6 MT120 boards are configured locally by TC terminal to constitute a cluster. Each BSC rack has to be connected to the same TC G2.5 for Qmux continuity. For redundancy purpose, a BSC G2 must be connected to a TC G2.5 via 2 Atermux at minimum.
11.3.3 Extension
A Qmux cluster is a group of up to 6 MT120 which insure the Qmux supervision of these boards with the TSC of the related BSC. These MT120 boards may not be adjacent or in a different subrack, but must be always in the same TC G2.5 rack. The notion of Qmux cluster is important during extension of Atermux in a BSC rack as described hereafter as it can induce modification of initial configuration. Different extensions are possible: Extension of Atermux in a BSC rack: In this case the Qmux cluster is increased. a recabling of all the Atermux of a cluster into a new TC G2.5 rack is necessary if there is no more free slot in the TC G2.5. TC G2 extension: Once the TC G2 rack maximum capacity (6 Ater) has been reached, BSC extension will require TC capacity. In this case TC G2.5 rack is required as TC G2 rack extension (TC G2 rack is kept). The TC G2.5 rack can be shared afterwards between different BSC extension New rack of a BSC by extension of Atermux capacity: Depending of free slot capacity in the TC G2.5, a new TC G2.5 may be required New BSC: Depending of free slot capacity in the TC G2.5, a new TC G2.5 may be required
Alcatel
Date 03/01/2000
Edition 03
Page 59
12 OMC-R 1353 RA CONFIGURATIONS

Alcatel 1353RA is the new generation of OMC-R available with B6.2.
12.1 Dimensioning rules
S ML_HOST MED IUM_HOST LRG1_HOST LRG2_HOST X LRG_HOST 0
250 cells - 750 TR X - 10 BSC EQ 500 cells - 1500 TRX - 2 0 BSCEQ 90 0 cells - 3600 TRX - 30 BSCEQ 12 00 cells - 360 0 TR X - 40 BSC EQ 35 00 ce lls - 8000 T R X - 100 BSC EQ
20
40
60
80
100
Nb of BS CE Q
BSC equivalent is defined as normalised load of the NE in terms of O&M capacity of the OMC-R. The following NE types must be considered: BSC (G2 type): 1 BSC G2 = 1 BSCEQ BSC (G1 type): 1 BSC G1 = 2/3 BSCEQ A935MFS: 1 A935 MFS = 2 BSCEQ
Alcatel
Date 03/01/2000
Edition 03
Page 60
12.2 HW descriptions : Generic Configurations

12.2.1 Server
Small host SML 120 Cells/480 TRX/6 BSC 2 Users w/o HMIS Standard host STDL 300 Cells/1200 TRX/20 BSC 5 Users w/o HMIS 11 Users with HMIS Large Host LRG 900 Cells/3600 TRX/35 BSC 10 Users w/o HMIS 11 Users with HMIS E4000 8p 167MHz 512 Mb E4500 6p 336MHz 512 Mb E4000 2p 167MHz 512 Mb E4500 2p 336MHz 512 Mb E450 1p 250MHz 256 Mb SS20 2p 75MHz 256Mb
12.2.2 HMIS and Terminal.
Workstation WS U5 1/2p 270MHz 128 Mb SS5 1p 170MHz 128 Mb SS5 1p 80-110MHz 32 Mb IPX Terminal XT Small HMIS S. HMIS Standart HMIS STD HMIS E450 1p 250MHz 256 Mb SS20 1/2p 75MHz 256 Mb U5 1/2p 270MHz 128 Mb SS5 1p 170MHz 128 Mb NCD
Alcatel
Date 03/01/2000
Edition 03
Page 61
12.2.3 O&M Configuration
Two kinds of configuration are distinguished for A1353-RA: The Host configuration that defines the type of machine that can be used to support the O&M configuration. The O&M configuration that defines the numbers of NE that can be supervised and the number of operators sessions that can be run simultaneously. The following types of Host have been defined:
Master Host It supports the Alarm manager, the Radio Network manager, Performance Measurement. It can support the BSS agent and the BSS communication 1 agent and their databases and USM only in the case of a no distributed configuration (Mono-Agent Host configuration). Agent Host It supports BSS agent and its database and the BSS communication agent, and USM5. HMI Sever It supports USM only. A server configuration and workstation are available. The following figure describes the generic O&M configuration set, for each set the type of generic Host configuration used, the maximal number of HMI.
Agent Host Number TX 1 on U5 + 1TX on SML,STD,LRG XLRG. 2 5 STD or LRG Host 5 10 or 15 15 on LRG Host, 10 on XLRG Host Number HMI 2 2 1 SML 11 5 6 SML or 2 STD 15 5 6 SML or 2 STD or 1 LRG 15 0 6 SML or 3 STD or 1 LRG 20 0 6 SML or 2 LRG Nber Users
Configuration SML_HMI STD_HMI LRG_HMI SML_HOST MEDIUM_HOST LRG1_HOST LRG2_HOST XLRG_HOST
Master
1 1 1 1 1
Some Master or Agent Host configurations may not support USM.
Alcatel
Date 03/01/2000
Edition 03
Page 62
12.3 HW : OMC2 versus OMC3

The philosophy is to reuse as much as possible the customer hardware. An OMC2 is migrated into the equivalent OMC3 generically configuration.
Table 1 A1353 Configuration Existing On Site Small Host Server SS20 E450 (250 MHz) E450 (400 MHz) Standard Host Server E4000 E4500 Large Host E4000 E4500 Small HMI U5 SS5 Standard HMI E450 SS20 Work Station U5 SS5 IPX X Terminal NCD Remarks / Reuse Extension
No
To replace by E450/400MHz/1GB Memory upgrade 1Gb
Yes
No
To replace by E450/400MHz/2GB Large Host LRG1 Upgrade memory :4Gb + Fan
Yes
Upgrade memory :256Mb Yes Upgrade memory: 512 Mb
No No They have not enough resource for Solaris 2.6 (B6.2) NCD
12.4 OMC-R/BSC INTERCONNECTION

The following type of connections between the OMCR and the BSCs available are: collocated BSCs without router ( via simples adapters on HSI ports ), collocated BSCs via X25 switch ( Newbridge ) Remote BSCs via PSDN ( via modem ), BSCs connection via Transcoder, BSCs connection via MSC ( via CISCO 4700 ).
Alcatel
Date 03/01/2000
Edition 03
Page 63
12.4.1 Collocated BSCs without router (via simples adapters on HIS ports)
The BSC is connected directly to a collocated X25 switch. The X25 extraction is done on the CPR-OSI board. The table below gives a description of this connection depending on the equipment.
BSC type G1 G2 CPR-OSI interface V28 X21 X25 throughput 9.6 kbit/s 64 kbit/s
12.4.2 Collocated BSCs via X25 switch (Newbridge)

The BSC is connected remotely to a X25 switch via a modem through a private switched data network. The X25 extraction is done on the CPR-OSI board. The table below gives a description of this connection depending on the equipment.
BSC type G1 G2 CPR-OSI interface V28 X25 throughput 9.6 kbit/s
V11
64 kbit/s
12.4.3 Remote BSCs via PSDN (via modem)

Each BSC communicates with an Agent Host via one CPRx board (Central Processor) at a time. The second board will be used only if the link to the first one is out of order when redundancy is set at BSC side. This link has a transfer capacity of 9.6 Kbits/s for the G1 BSC and up to 64 Kbits/s for the G2 BSC.
Alcatel
Date 03/01/2000
Edition 03
Page 64
12.4.4 BSCs connection via Transcoder 12.4.4.1 X25 extraction on G1 TC

The TRCU site through a RS232 V28 connector ( 64 kbits/s) and the OMCR can be directly connected via V28 interface. However, if more than a single BSS shall be served by the OMCR, a X25 Switch is necessary. Newbridge concentrator has been chosen. Newbridge concentrators cascade is possible in order to support the full range of BSCs served by one OMCR host, i.e. max eight switches can be re-quired. The maximum of BSSs connected via Ater is due to capacity of this switch. The G1 TC output follows the V35 protocol.
A ter DTC 3
1 2
X25 64Kb TS 31
A ter mux S M 2 M
1
(option)
X25 64Kb TS 16
A ter
TRCU 3
S M 2 M
1
(option)
X25 64Kb TS 31
D B 2 M
D X 2 M P2/1
TC
2 3
TC
DTC 4 C P R 3 OSI C P R 4 OSI

1
V28/V11 Converter
2
X25 64Kb TS 31
S M 2 M 2
(option)
X25 64Kb TS 16
S M 2 M 2
(option)
1 V28/V11 Converter
X25 64Kb TS 31
X25
Concentrator
ROUTER
D D B X 2 2 M M TC
X25 64Kb
OMC-R
TC
TRCU 4
BSC/TC G1 Internal routing
Alcatel
Date 03/01/2000
Edition 03
Page 65
12.4.4.2 X25 extraction on G2

The TRCU site and the OMCR can be directly connected via V11 interface. However, if more than a single BSS shall be served by the OMCR, a X25 Switch is necessary. Newbridge concentrator has been chosen. Newbridge concentrators cascade is possible in order to support the full range of BSCs served byone OMCR host, i.e. max eight switches can be required. The maximum of BSSs connected via Ater is due to capacity of this switch. The G2 TC output follows the X21 protocol.
A ter DTC 2
1 2
X25 64Kb TS 31
A ter mux A S M B 1 A S M B 2
(option)
X25 64Kb TS 16
A ter
TRCU 1b
A S M B
1
X25 64Kb TS 31
A T B X
DT16
2 3
DT16
DTC 6 C P R 3 OSI C P R 4 OSI
(option) 4
X25
Concentrator
X25 64Kb TS 16
2
X25 64Kb TS 31
3 4
A S M B 2
(option)
ROUTER
X25 64Kb TS 31 X25 64Kb
2 3 4
A T B X
DT16
OMC-R
DT16
TRCU 2b
BSC/TC G2 Internal routing
Alcatel
Date 03/01/2000
Edition 03
Page 66
12.4.5 BSC CONNECTION VIA MSC

This is an Alcatel solution based on CISCO 4700 routers to decrease the cost of OMC R/BSCs connection in comparison with connection via PSDN or to provide a solution when no reliable PSDN solution exist at customer site. It should be preferred to PSDN solution in any cases.
12.4.5.1 Characteristics
Virtual Path inside BSC from OSI-CPR to DTC 64kbit timeslot on Ater Between BSC and MSC Virtual Path inside MSC from BSC trunkgroup to router trunk PCM link(G.703/G.704,75 or 120 Ohm) between MSC and router
Standard X.21 cable connection between router and OMC (via HIS)
12.4.5.2 Small configuration

This configuration allows maximum 2 OMCRs and up to 31 BSCs (15 BSCs with redundancy at BSC site). Each time slot on the A interface carrying an X.25 link is mapped to one on the PCM link to the router. Then 31 x 64kb/s time slots are available with a channelized G703 link. The router is always located at OMCR site.
Alcatel
Date 03/01/2000
Edition 03
Page 67
12.4.5.3 Large number of BSCs at MSC site

The number of BSC handled by MSCs may be greater than 31 (15 if redundancy set at BSC site). In that case additional routers must be provided. A second router is used to provide another 31 or 62 ( one or two E1 modules equipped ) time slots. In that case, routers are interconnected via TCP/IP or routed via the LAN used as backbone.Some BSC links are directly routed to CISCO1, the other are routed to CISCO2 and then re routed to CISCO1 after compression via primary MSC1.
Alcatel
Date 03/01/2000
Edition 03
Page 68
12.4.5.4 Additional OMCRs for large networks

If more than the already provided number of serial boards are required for connections of OMCs or other X.25 equipment, a second ( or more ) router must be installed.
Alcatel
Date 03/01/2000
Edition 03
Page 69
12.4.5.5 Remote configuration

This configuration can be used if the OMCR and MSC sites are not collated, by using either serial WAN boards (4 ports available, 2 links advised for security), or G703 not channelized (2 ports, 2 links advised for security, connected using private links or connected to special lines provided by an operator)
This configuration allows maximum 2 OMCRs and 31 BSCs without redundancy at BSC site, 15 BSCs with redundancy at BSC site. The maximum number of BSCs is the maximum number of BSCs supported by the CISCO at MSC site (31 time slot maximum). 12.4.5.6 Remote terminals As shown in previous figure, remote terminal (X terminals or work stations) can be connected via the IP backbone to OMCRs. Two additional time slots must be dedicated to this connection. It must be taken into account for the maximum number of BSCs connected to an OMCR host.
Alcatel
Date 03/01/2000
Edition 03
Page 70
12.4.5.7 Mixed local and remote MSC configuration

12.4.5.7.1.Without data compression The PCM network between the local MSC and the remote MSC is used for X25 data transmission. X25 time slots from remote BSCs directly mapped to CISCO router without traffic concentration. No backbone network used. This configuration allows maximum 2 OMCRs and 31 BSCs (15 BSCs with redundancy at BSC site). It is recommended for small number of remote BSC.
Alcatel
Date 03/01/2000
Edition 03
Page 71
12.4.5.7.2.With data compression at remote MSC site The PCM network between the local MSC and the remote MSC is used for X25 data transmission. A second CISCO router is used at remote MSC site to compress the X25 data. One time slot is sufficient to carry X25 data for 10 BSCs.
12.5 OMC-R/MFS INTERCONNECTION

Two one OMCR/MFS connection type is supported. The interface between the OMCR and an MFS can be set using two kind of network, LAN ethernet or PSDN. The OMCR and the MFS can be collocated or not. In both case the only interface seen is the ethernet LAN. The router bridge is used to make it transparent by embedding the TCP/IP protocol into X25 frames to go through the WAN to all remote sites. Remark: Although MFS needs 2 Ethernet plugs then 2 Ethernet cables ( mandatory redundancy ), only one will be represented in the following figures.
12.5.1 MFS and OMCR collocated (via an external Hub)

A hub can emulate the Ethernet bus. As hubs are cheaps, this solution is used when there is no Ethernet infra structure susceptible to accept the Alcatel solution. Usually a Hub is already installed in OMC Networks.
12.5.2 MFS and OMCR not collocated (via PSDN )

An X25 WAN can be used to convey IP traffic between the OMCR and MFS site. Whatever WAN technology used, the adaptation of IP traffic to the the Wan server is the responsibility of external routers. The router type to be chosen depends on NEs interconnected.
12.5.2.1 case of CISCO 2500 use
OMCR/MFS LAN ethernet interface This connection can reuse the present OMCBSC network. The HUB can be provided for customer that have no ethernet infrastructure to connect all configurations with an ethernet interface : OMCR, MFS,servers, workstations.
Alcatel
Date 03/01/2000
Edition 03
Page 73
12.5.3 Case of CISCO 4700 use 12.5.3.1 Principle

The principle of this solution is to use the transmission capabilities of the PLMN itself for physical base of X.25 links. Hence, all BSC O&M channels (64 kbit/s each) are reserved on PCM trunk between each BSC and related MSC. This solution is made possible through the use of intelligent multi-protocol routers located at OMC-R site and MSC sites, routers that also build an IP network interconnecting the OMC-R and the BSCs in a very efficient, flexible and fault resistant way.
12.5.3.2 Main advantages

Already installed in many Alcatel networks, the Alcatel EVOLIUMTM BSS Universal Routing offers many advantages: Operation and Maintenance: Remote configuration operation: the reliable X.25 links will allow to perform most of its configuration operations remotely from the OMC-R, thus avoiding costly and timeconsuming on-site operations. Easy OSS modification: operations such as Move BSC will not need cabling efforts any longer. Simple routing changes from a terminal will be sufficient. Evolving solution: by its design and implementation, Alcatel EVOLIUMTM BSS Universal Routing configuration can be modified with a minimum operational impact.
Security : The X.25 link between each BSC and the OMC-R is secured thus allowing a continuous connection between OMC-R and BSCs.
Cost : No need to subscribe for X.25 links.
New equipment and releases introduction: Easy GPRS introduction: routers can carry O&M information of a co-located MFS (GPRS element of the BSS). B 6.2 migration preparation: the OMC2 -> OMC3 migration is made easier by the two X.25 links between BSC and OMC-R. It will minimize the supervision outage. Cell Broadcast Center easy introduction: this service can be introduced by connecting the CBC on any serial interface of a router.
Alcatel
Date 03/01/2000
Edition 03
Page 74
However, this solution may present some drawbacks: It takes time slots that could be used for traffic. But this TS number (2 per BSC) represents a tiny proportion of the total amount of TS. As each router concentrates a high number of BSC, the loss of one router can be penalizing for the Operation and Maintenance. This case never occurred on networks on which Alcatel installed this solution. Nevertheless, the network design can prevent from this problem. As the solution uses BSS and NSS, it can be more difficult to solve a problem. However, a good knowledge of the routing results in a quick solution to these problems.
12.5.3.3 Technical description

12.5.3.3.1 Router configurations An Alcatel OMC-R IP network adapted to the size of a PLMN is realized using routers at OMC-R sites and at MSC sites. Three router configurations have been identified from which the different network configurations can be built. They are called router types, they all have similar structure, they differ by the role they play and thus the type of modules they include: Router Type 1 is always located at OMC-R site. One such router is included in any network configuration and allows by itself to build networks involving 1 MSC, 2 OMCRs max. and 31 BSCs max. (or 15 BSCs max. if secured X.25 connection is used). Its boards are: An Ethernet module which allows the connection to the OMC-R LAN (for configuration purpose) A PCM module which receives X.25 information from BSCs A Serial module which sends X.25 information to OMC-R
Router Type 2 is always located at MSC site. It allows to build a BSS network of bigger size, An Ethernet module One or two PCM modules
In the MSC, the X.25 links from the BSCs are routed to the router PCM module through Semi-Permanent Connections (SPC). After compression, the corresponding TCP/IP traffic is routed from Router Type 2 to Router Type 1 via primary MSC through only few timeslots of the PCM trunks that interconnect these MSCs for telecom traffic purposes (and through Semi-Permanent Connections within each MSC). Each PCM module can compress 10 O&M TS on 1 IP TS which allows it to serve 28 BSC and 3 TS for TCP/IP backbone at maximum.
Alcatel
Date 03/01/2000
Edition 03
Page 75
The different routers linked together by the IP backbone can be configured remotely via telnet session.
12.5.3.4 BSC OMC-R connection

The different steps of the connection are described below : BSC site : The X25 information is routed from OSI-CPR through the BSC switch to 2 distinct DTCs (DTC 2 for the primary path, DTC 6 for the redundant path for G2 BSC), Each DTC inserts this information on the TS 31 of the A-ter interfaces PCM link, Each ASMB extracts this information and inserts it on the TS 31 of the A-termux interfaces PCM link.
TC site :
Each ASMB extracts this information and inserts it on the TS 31 of the A-ter interfaces PCM link, Each TRCU extracts this information and inserts it on the TS 31 of the A interfaces PCM link,
MSC site :
Each X25 TS from BSCs is directed to a PCM using Semi-Permanent Connections (SPC). Depending on the situation, this PCM is connected to:
q q
Alcatel
A co-located Type 2 router. After compression, the corresponding TCP/IP traffic is routed from Router Type 2 to Router Type 1 at OMC-R site via the primary MSC. An other MSC giving access to a router
File b62_jv_2000.doc Reference 3DF 00928 0001 DSZZA Date 03/01/2000 Edition 03 Page 76
A Type 1 router located at OMC-R site.
OMC-R site : The type 1 router extracts X25 information from the PCM link and directs it to its serial interface, The OMC-R receives two X25 links from the router on its HSI board.
The following figure describes the X25 TS path between BSC and MSC.
A ter BSC
C P R 3 OSI DTC 1 DTC 2 DTC 3 DTC 4 X25 64 kbit/s TS 31 A S M B 1
A ter mux TC
X25 64 kbit/s TS 31 A S M C 1
A ter
TRCU 1 X25 64 kbit/s TS 31 TRCU 3 TRCU 4 TRCU 2
X25 64 kbit/s TS 31
To MS site
X25 64 kbit/s TS 31
DTC 5 C P R 4 OSI DTC 6 DTC 7 DTC 8 X25 64 kbit/s TS 31 A S M B 2 X25 64 kbit/s TS 31 A S M C 2 X25 64 kbit/s TS 31
TRCU 5 TRCU 6 TRCU 7 TRCU 8
Alcatel
Date 03/01/2000
Edition 03
Page 77
The figure hereafter is a possible implementation of the Alcatel BSS Universal Routing on a network
MFS 2 Cisco 2 C i s c o 4 OMC 1
20 TS (**) MSC3 6 TS MSC4 MFS 1 6 BSC MSC2 1 TS 1 BSC 1 TS 13 BSC 1 TS TC 1 TS BSC (**): 18 TS = 3 * (*): 6 TS = 2 TS compressed BSS O & M (*): 21 TS = 4 TS GPRS O & M MFS 3 Cisco 3 6 TS (*) 8 BSC 6 TS (*) 18 TS (**) Cisco 1
OMC 2
21 TS (*) MSC6 OMC 3 C i s c o 5
21 TS (*) MSC5 15 BSC 18 TS (**)
MSC1
LAN
15 TS BSS O & M 2 TS compressed BSS O & M 4 TS GPRS O & M
14 TS BSS O & M 2 TS compressed BSS O & M (**): 20 TS = 2 TS compressed BSS O & M 4 TS GPRS O & M 4 TS GPRS O & M
Alcatel
Date 03/01/2000
Edition 03
Page 78
13 GLOSSARY
A Abis AC BCCH BIE BSC BSS BTS CCCH CIC CPRA DCN DR DRFU DTC EFR FR G703 Gb GCH GPRS GPU GSL LAPD MD MFS MS MSC NSS O&M PSTN PDCH QoS REK RSL RTC SDCCH SGSN SM SS7 SUM A interface is between BSC and MSC Abis interface is between BTS and BSC Alternative Current Broadcast Control Channel Base station Interface Equipment Base Station Controller Base Station Subsystem Base Transceiver Station Common Control Channel Channel Identity Code Common Processor A Digital Cross-connect Network Dual Rate Dual Rate Frame Unit Digital Trunk Controller Enhanced Full Rate Full Rate Physical/electrical characteristics of hierarchical digital interfaces Telecommunication interface between MFS and SGSN GPRS Channel (Ater interface) General Packet Radio Service GPRS Processing Unit GPRS Signaling Link Link Access Protocol on D channel Multi Drop Multi-BSS Fast packet Server Mobile Station Mobile Switching Centre Network Sub-System Operation and Maintenance Public Switched Telephone Network Packet Data Channel (Air and Abis Interface) Quality of Service Range Extension Kit Radio Signalling Link Remote Tunable Combiner Stand Alone Dedicated Control Channel Serving GPRS Support Node Sub Multiplexer Signalling System number 7 Station Unit Module
Alcatel
Date 03/01/2000
Edition 03
Page 79
SUMP TMA TC TCH TCUA TCUC TRAU TRCU TRX TS TSU WBC
Station Unit Module PCM Tower Mounted Amplifier TransCoder Traffic Channel Terminal Control Unit A Terminal Control Unit C Transcoder/Rate Adaptation Unit Transcoder Rate adaptationControl Unit Transmitter / Receiver (logical view) Time slot Terminal Sub Unit Wide Band Combiner
Alcatel
Date 03/01/2000
Edition 03
Page 80
Appendix 1 : Star and closed catalogue mapping
In B6.2, the star configuration and closed catalogue are still supported and left unchanged.Star mapping Star topology should be kept only with BSC G1 and G1 BTS carrying Star Hardware (BIU2M). TS0 usage is used only for G1 BTS. Technique used TS0 usage TS0 transparency
Qmux TS 0 TS 19
OML TS 31 TS 21
Restriction: STAR mapping with TS0 Usage is forbidden with SMBI, SMFG, SUMP. The Static Sub-multiplexing RSL 16Kb/s is not supported. Closed catalogue mapping For the closed catalogue, the Qmux channel is always conveyed on TS0. (TS0 usage). The following table summarises the closed catalogue mapping for different configurations. Qmux and S bits use the TS0. The allocation of TS for the BTS is fixed one for all. The advantage of this rule is that the Add or delete BTS/TRE has no impact on other BTS on the same link. RSL 16k sub-multiplexing is not compatible with closed catalogue.
Alcatel
Date 03/01/2000
Edition 03
Page 81
1BTS * 8TRX 0 1 2 3 4 5 6 7 8 9 10 FU 7 FU 3 FU 6 FU 2 FU 5
Qmux+Sbits
1*5 + 1*4
Qmux+Sbits
1*4 + 1*3 + 1*2

Qmux+Sbits
4 BTS * 2 TRX
Qmux+Sbits
3 BTS * 3 TRX
Qmux+Sbits
3*3 type 2
Qmux+Sbits
FU 1
FU 1 - A
FU 1 - A
FU 1 - A
FU 1 A
OML A FU 1 A
FU 1 - B
FU 1 - B
FU 1 - B
FU 1 B RSL 1 A
FU 2 - A
FU 2 - A
FU 2 - A
FU 2 A
FU 2 A
FU 2 - B
FU 2 - B
FU 2 - B
FU 2 B
RSL 2- A FU 3 A
FU 3 - A
FU 1 - C
FU 1 - C
FU 1 C RSL 3- A
FU 3 - B
FU 3 - C
FU 1 - D
FU 3 - C
OML B FU 1 B
FU 4
FU 4 - A
FU 2 - C
FU 2 - C
FU 2 - C RSL 1- B
15
FU 8
FU 4 - B
FU 4 - A
FU 2 - D
FU 3 - B
FU 2 B
FU 5 - A 18
FU 3 - A
FU 3 A
RSL 2 B FU 3 B
RSL 4 - A 20 RSL 5 - A OML B RSL 8 RSL 7 RSL 6 25 RSL 5 OML RSL 4 RSL 3 RSL 2 30 RSL 1 R bits RSL 4 - B RSL 3 - B RSL 2 - B RSL 1 - B OML A RSL 4 - A RSL 3 - A RSL 2 - A RSL 1 - A R bits OML B OML C OML A RSL 3 - C RSL 2 - B RSL 1 - B RSL 3 - A RSL 2 - C RSL 1 - C RSL 2 - A RSL 1 - A R bits
OML D OML B OML C RSL 2 - D RSL 1 - D RSL 2 B RSL 1 B OML A RSL 2 C RSL 1 C RSL 2 - A RSL 1 - A R bits
R bits OML B OML C RSL 3 B RSL 3 C RSL 2 B RSL 1 B RSL 3 A RSL 2 C RSL 1 C RSL 2 A RSL 1 A OML A RSL 3 C RSL 2 C FU 3 C RSL 1 C FU 2 C RSL 3 B OML C FU 1 C
Closed Catalogues configurations
Alcatel
Date 03/01/2000
Edition 03
Page 82
END OF DOCUMENT
Alcatel
Date 03/01/2000
Edition 03
Page 83

BSS Dimensioning Rules B6.2

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

BSS Dimensioning Rules B6.2

Diunggah oleh

Hak Cipta:

Format Tersedia

BSS B6.

BSS B6.2 CONFIGURATION DESCRIPTION

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

5.1.4 5.1.5 5.1.6 5.1.7 5.1.8

64K statistical multiplexing....................................................................................................................25

6.4.3.1 6.4.3.2 6.4.3.3

16K statistical multiplexing....................................................................................................................26

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

6.5.3.1 6.5.3.2 6.5.3.3

B6.2 BSC G2 Free Mapping...................................................................................................................30

6.5.4.1 Free mapping rules ............................................................................................................................................... 30

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

BSC CONNECTION VIA MSC ..........................................................................................................67

Case of CISCO 4700 use....................................................................................................................74

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

03/01/20 00 DATE CHANGE NOTE

RCD/TD APPRAISAL AUTHORITY

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

Radio Channels Configuration

The operator can choose the maximum GPRS traffic capacity.

Radio channels type

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

TRX 7 TRX 8 TRX 9 TRX 10 TRX 11 TRX 12

TCH TCH TCH TCH TCH TCH

TCH SDC TCH SDC TCH SDC

TCH TCH TCH TCH TCH TCH

TCH TCH TCH TCH TCH TCH

TCH TCH TCH TCH TCH TCH

TCH TCH TCH TCH TCH TCH

TCH TCH TCH TCH TCH TCH

TCH TCH TCH TCH TCH TCH

Urban Dense Configuration

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

Traffic available (2% of blocking rate)

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

EVOLIUMTM A9100 BTS Radio Solution

General Product presentation

1 sector 1 to 4 TRXs 1 to 4 TRXs 2 to 8 TRXs

Mini Indoor Mini Outdoor Medi Indoor/Outdoor Extended cell:

5.1.2.1 Functional description

Reference 3DF 00928 0001 DSZZA

BSS B6.2 Configuration description

This modularity allows configurations such as:

EVOLIUM EVOLIUM TM TM EVOLIUM EVOLIUM TM EVOLIUM Duplexer

Combiner Duplexer Combiner

TRX TRX TRX TRX TRX TRX

TRX TRX TRX TRX TRX TRX TRX TRX

Mini ,QG2XW 2XW ,QG2XW ,QG2XW Medi ,QG2XW 2XW

[ [ [ [

[ [ [ [ [