ABIS Interface

GSM
Abis Interface Engineering Guide

Reference : Version : Date : Author : Documentalist : Approved by : Quality manager : Ext. ref. : Type : Product : Cat : Status : PE /IRC/APP/0079 01.08 / EN 12/04/99 T. Bachelier A.-M. Leberre M. Liem
CEV I A
Abstract / comments : This is an internal document that applies up to the V12 BSS release. This document is available at the following Netscape location: http://136.147.68.68/ned/ERGmain.html
Distribution lists :
This confidential document is the property of NORTEL MATRA CELLULAR and may not be copied or circulated without permission Ce document confidentiel est la proprit de NORTEL MATRA CELLULAR et ne peut tre reproduit ou communiqu sans autorisation
DOCUMENT AMENDMENTS VERSION DATE COMMENTS Creation - Preliminary edition Update after review Preliminary edition See report: PE/IRC/GES/0034 V1.01 New minutes have been taken into account Modification after review + rewriting See report: PE/IRC/GES/0034 V1.02 AUTHOR T. Bachelier T. Bachelier T. Bachelier T. Bachelier
01.01 / EN 03/06/98 01.02 / EN 19/06/98 01.03 / EN 15/07/98 01.04 / EN 31/07/98 01.05 / EN 16/12/98 01.06 / EN 24/12/98 01.07 / EN 25/03/98
US and China comments have been taken into ac- T. Bachelier count Modification after review See report: PE/IRC/GES/0034 V1.03 T. Bachelier
The main changes are on LAPD dimensioning: T. Bachelier Engineering rules have been completely remade, they are given for each type of BTS which allows more flexibility. Modification after review. T. Bachelier
01.08 / EN 12/04/98
Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN 12/04/99
GSM
Reference : Version : Date : PE /IRC/APP/0079 01.08 / EN 12/04/99
ABIS INTERFACE ENGINEERING GUIDE
TABLE OF CONTENTS
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.1 PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2 RELATED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.1 APPLICABLE DOCUMENTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2 REFERENCE DOCUMENTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 3 ABBREVIATIONS AND DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.1 ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 3.2 DEFINITION OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4 BTS CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1 SITES AND CELL LAY-OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.2 OFFERED TRAFFIC ASSESSMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.3 RADIO INTERFACE DIMENSIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.3.1 TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.3.2 SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.3.3 BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.4 CELL DIMENSIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.4.1 Cell types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.4.2 BTS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 4.5 LOOK-UP TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5 BTS DIMENSIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.1 SIGNALLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.1.1 LAPD channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 5.1.2 LAPD dimensioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 5.2 PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.2.1 Abis TS dimensioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.2.2 PCM configuration rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 5.3 DCC & DSC DIMENSIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.4 LOOK-UP TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 6 ABIS ARCHITECTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.1 DROP&INSERT CONFIGURATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.1.1 Possible configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 6.1.2 TEI issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Page 4
TABLE OF CONTENTS
6.1.3 6.1.4 6.1.5 6.1.6 6.2 HUBS 6.2.1 6.2.2 7 7.1 7.2 7.3 7.4 DTI/PCMI issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RadioSiteMask configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RadioSiteMask Extension strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additinal feature of TDMA/Abis mapping configuration for V11 . . . . . . . ......................................................... Cross-connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 37 40 42 43 43 44 46 47 49 49 49 50 50 51 51 53 54 56 58 59 59 59 60 60 62
TRANSMISSION MEDIUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 CLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANSMISSION QUALITY REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . CSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HDSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.2 HDSL issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.3 HDSL modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 MICROWAVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.1 Microwave design Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.2 Microwave Quality requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.3 Microwave configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.4 Microwave equipment redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC DIMENSIONING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 8.1 BSC TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 SICD/SICD8V BOARDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.1 Limitation rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2 Parenting rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.3 Look-up tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3 BSCB AND TSCB BOARDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4 DDTI BOARDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
APPENDIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Page 5
LIST OF TABLES
Table 1: BTS configuration limitations .............................................................................. Table 2: Traffic for a given number of TRXs in a standard cell ........................................ Table 3: Traffic for a given number of TRXs in an extended cell...................................... Table 4: PCM configuration for S333 (TEI 0) with 1 PCM............................................... Table 5: PCM configuration for S333 (TEI 0) with 2 PCMs ............................................. Table 7: Internal E1 to external T1 conversion .................................................................. Table 8: LAPD/DCC configuration.................................................................................... Table 9: Omnisectorial BTS ............................................................................................... Table 10: Bisectorial BTS................................................................................................... Table 11: Tri and hexasectorial BTS .................................................................................. Table 13: PCM E1 RadioSiteMask..................................................................................... Table 14: PCM T1 RadioSiteMask..................................................................................... Table 15: PCM E1 RadioSiteMask..................................................................................... Table 16: PCM T1 RadioSiteMask..................................................................................... Table 17: RadioSiteMask (first strategy)............................................................................ Table 18: RadioSiteMask (second strategy) ....................................................................... Table 19: RadioSiteMask (Third strategy) ......................................................................... Table 20: RadioSiteMask configuration with crossconnect ............................................... Table 21: Timing requirements........................................................................................... Table 22: Product range...................................................................................................... Table 23: SICD limitations ................................................................................................. Table 24: Maximum number of sites per BSC ................................................................... Table 25: PCM allocation for the BSC6000 Type5............................................................ 17 18 18 26 27 28 29 30 30 31 38 38 39 39 41 41 42 44 46 58 60 61 62
Page 6
LIST OF FIGURES
Figure 1: Star, Drop&Insert and Hub&Spoke Configurations ........................................... Figure 2: Loop Drop&Insert configuration ....................................................................... Figure 3: Hub&Spoke configuration. ................................................................................. Figure 4: PCMI configurations for drop&insert ................................................................. Figure 5: D&I in loop without board redundancy: 1G versus 2G ...................................... Figure 6: Drop & Insert example ........................................................................................ Figure 7: Hub&Spoke example .......................................................................................... Figure 8: Example............................................................................................................... Figure 9: Cross-connect configuration ............................................................................... Figure 10: Crossconnect configuration............................................................................... Figure 11: Architectuire with Switch ................................................................................. Figure 12: HDSL solution................................................................................................... Figure 13: Microwave solution........................................................................................... Figure 14: Reference communication of ITU..................................................................... Figure 15: Performance objectives: .................................................................................... Figure 16: Chain Drop&Insert with microwaves ............................................................... Figure 17: Loop Drop&Insert with microwaves................................................................. Figure 18: Hub and Spoke with microwaves...................................................................... Figure 19: Abis configuration with microwaves on BSC side ........................................... Figure 20: Typical non-protected and protected microwave equipment architecture ........ Figure 21: Dimensioning the Abis interface with LAPD concentration ............................ Figure 22: Example of complex configuration ................................................................... 33 34 34 35 36 38 39 40 43 43 44 49 51 53 53 54 54 55 55 56 61 63
Page 7
1 INTRODUCTION
1.1 PURPOSE The purpose of this document is to give Abis interface engineering guidelines for the NORTEL BSS network. This document is discusses the following subjects: v Dimensioning speech and signalling on the Abis interface, v Impact on the BTS side, v Abis architecture, v Transmission medium (HDSL, microwaves), v Impact on the BSC side. This document is intended primarily for Network Designers and Application Engineers involved in GSM network Engineering within NORTEL GSM Networks and Nortel. 1.2 SCOPE This document is internal and applies up to the V12 Release.
Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN
Page 8/64 12/04/99
2 RELATED DOCUMENTS
2.1 APPLICABLE DOCUMENTS [A01] Feature list of System Release V11 PE/SYS/DPL/0089 V01.02/EN [A02] [A03] Dimensioning the Abis interface PE/SYS/DD/0070 V6.02/EN
P. Vincent B. Couaillet
Transmission Network Recommendations PE/SYS/DD/0253 V1.03/EN B. Couaillet
2.2 REFERENCE DOCUMENTS [R01] V8 Engineering Changes PE/IRC/APP/00030 V1.06/EN [R02] [R03] [R04] [R05] [R06] [R07] [R08] [R09] [R10] [R11] [R12] V9 Engineering Changes PE/IRC/APP/00048 V1.06/EN V10 Feature Engineering Information PE/IRC/APP/00068 V1.08/EN V11 Feature Engineering Information PE/IRC/APP/00072 V1.06/EN
L. Jullien T. Bachelier S. Luong T. Bachelier
S8000 Outdoor BTS Engineering Information PE/IRC/APP/00033 V4.02/EN Y. Maurin S8000 Indoor BTS Engineering Information PE/IRC/APP/00055 V4.02/EN Y. Maurin S2000H BTS Engineering Information PE/IRC/APP/00052 V3.04/EN S2000L BTS Engineering Information PE/IRC/APP/00053 V3.04/EN BSC/TCU Engineering Information PE/IRC/APP/00015 V5.04/EN M. N. Boursin M. N. Boursin B. Vanheeghe
OMC-R Engineering Information (Vol. 1) PE/IRC/APP/00016 V5.04/EN M. Lebas BSS Parameters User Guide PE/IRC/APP/00037 V3.01/EN Defence mechanisms on PCM faults PE/SYS/DD/0242 V3.01/EN WGAl-WGSys B. Couaillet
Page 9/64 12/04/99
[R13] [R14]
UIT-T Recommendations G732 Characteristics of primary PCM multiplex equipment operating at 2048 kbit/s. UIT-T Recommendations G811 Timing requirements at the output of primary reference clocks suitable for plesiochronous operation of international digital links. UIT-T Recommendations G733 Characteristics of primary PCM multiplex equipment operating at 1544 kbit/s. UIT-T Recommendations The control of jitter and wander within digital networks which are based on the 2048 kb/s hierarchy. UIT-T Recommendations The control of jitter and wander within digital networks which are based on the 1544 kb/s hierarchy. CT5100 Specification for Backhaul Optimization PE/SPC/DD/00xx V1.01/EN A. Chevalier GSM Transmission Engineering Guide PE/IRC/APP/0086 V1.01/EN B. Pariseau Nortel BSS performances PE/BSS/DJD/0456 V1.01/EN HDSL modem layer1 qualification PE/BTS/DJD/0962 V10.01/EN A. Monts B. Corn
[R15] [R16]
[R17]
[R18] [R19] [R20] [R21] [R22]
BSCB Engg Information: Load Monitoring and Optimization PE/IRC/INF/0015 V1.01/EN B. Vanheghe
Page 10/64 12/04/99
3 ABBREVIATIONS AND DEFINITIONS

3.1 ABBREVIATIONS BCF BDA BER BPUG BSC BSS BTS CCCH CS CSU DCC DSC DCU DIU DM DRX DTI ES FEI GSM HDSL HG HLR HO H/W LA LAPD LG LOS L1M MG MS NMC NMC NSS O&M OMC OMC-R OMN Base Common Function Application Database Bit Error Rate BSS Parameters User Guide Base Station Controller Base Station SubSystem Base Transceiver Station Common Control Channel Coupling System Channel Service Unit Data Channel Concentrator (BTS 1G) Data Signalling Concentrator (BTS 2G) Dual Channel Unit Digital Interface Unit Degraded Minutes Driver + Receiver + Frame Processor Digital Trunk Interface Errored Seconds Feature Engineering Information (document) Global System for Mobile communications High bit rate Digital Subscriber Line High grade Home Location Register Handover Hardware Location Area Link Access Protocol on D channel Local Grade Line Of Sight Layer 1 Measurements Medium Grade Mobile Station Nortel Matra Cellular Network Management Center Network Sub-System Operation and Maintenance Operation and Maintenance Center Operation and Maintenance Center-Radio Operation and Maintenance Network
Page 11/64 12/04/99
PA PBGT PCH PCM PCMI PEI QOS RFU RV SES SMS-CB SPCMI TBC TBD TCH TCU TEI TMG TRX TS
Power Amplifier Power Budget Paging Channel Pulse Code Modulation PCM Interface Product Engineering Information (document) Quality of Service Radio Frequency Unit Rendez Vous Severely Errored Seconds Short Message Service - Cell Broadcast Small PCM Interface To Be Completed To Be Defined Traffic ChHannel Transcoder Unit Terminal Equipment Identifier Traffic Management Transmission-Reception subsystem of the BTS Time Slot
Page 12/64 12/04/99
3.2 DEFINITION OF TERMS C/I: Carrier-to-Interference ratio, measured in dB, gives the measure of the ratio of the usable signal over the interferences level. DRX: The DRX is a part of the "2G" BTS system architecture. The first product that supports this architecture in the Nortel catalogue is the S8000 Outdoor BTS. In the "2G" architecture, the TRX is composed of two modules, one dedicated to the signal processing (transmission and reception) called DRX, and one dedicated to the power transmission, called PA. Rendez Vous time slot: This is the time slot of the Abis interface PCM link that carries the primary LAPD of the BTS site. It has a fixed predefined position on the PCM (BTS side) because it is the time slot used by BSC and the BTS to establish their first dialogue after a scanning procedure. Soft Blocking: Procedure by which a TRX or a cell can be put out of service (i.e. blocked) without interrupting the given TRX or cell active calls.
Page 13/64 12/04/99
Page Intentionally Left Blank
Page 14/64 12/04/99
4 BTS CONFIGURATION
The site and the type of each BTS must be determined to perform the dimensioning of the Abis interface. This part is performed by the Cellular planning in conjunction with the network designer and the customer. 4.1 SITES AND CELL LAY-OUT The sites and the cell layout are fixed according to the coverage prediction. There are two different ways of working depending on the project context. vIf the customer defines the site locations, then Nortel must define the predicted coverage area. vIf the customer does not define the site locations, Nortel assumes additional activities for the site acquisition process follow-up such as along the site acquisitions iterations, provision of optimal theoretical site location, site selection rules, and coverage/quality impact of candidate site selection. 4.2 OFFERED TRAFFIC ASSESSMENT The BTS configurations depend on the traffic (in Erlangs) that each cell must carry. Traffic is assessed with two kinds of information: quality of service and subscriber behaviour. The behaviour of subscribers includes the distribution of GSM subscribers within the population, call profile, and mobility parameters. The offered traffic of each cell is worked out from this information. 4.3 RADIO INTERFACE DIMENSIONING The offered traffic is assessed. The next step is to dimension the radio interface. 4.3.1 TCH The number of required TCHs is worked out from the Erlang B-law with a fixed blocking rate applied to the assessed offered traffic. The assumption of NORTEL is a blocking rate of 2% for traffic or data on the radio interface. One TCH channel is carried by one radio TS. Note that an ErlangB calculator is available at the following URL address:
http://47.53.64.96/syseng/2S00/2S30/ErlangBCalc/EBCalc.html
Page 15/64 12/04/99
4.3.2 SDCCH The number of required SDCCH channels is difficult to assess because it depends on a large number of parameters: Mobility profile, Strategy used: For example, if most of the SDCCH requests are for call and not for Location Update, it could make sense to use TCH signalling. It will allow the decrease the call setup time. Therefore, no more SDCCH channels are needed according to this strategy (Note that the Location Update will be also supported by a TCH signalling). This strategy is only applicable to few particular cases, but it has a big impact on the dimensiong of the radio interface. geographical zone of the cell: If the cell is near an LA boundary, the number of Location updates could be quite important. So, the number of SDCCHs must be high. features used: Queueing increases the duration of the SDCCH connections, therefore the number of needed SDCCH may be studied. This is not an exhaustive list. It just gives information about some parameters which can strongly impact the SDCCH dimensioning. Nevertheless, if we take only into account the NORTEL standard traffic model, the number of required SDCCH can be easily determined. The NORTEL standard traffic model indicates that 28 Erlangs of signalling traffic is required for 100 Erlangs of speech or data traffic. After determination of the signalling traffic, the number of SDCCH channels is worked out from the Erlang B law. NORTEL assumption is a blocking rate of 0,1% for signalling on the radio interface. A radio TS can carry 8 SDCCH channels and is called SDCCH/8, but the SDCCH channels can be combined with the BCCH (refer to the following paragraph). 4.3.3 BCCH One BCCH is required per cell. The BCCH is supported by the TS0 of the beacon frequency. In the case of one TRX per cell, BCCH can combined with one SDCCH/4 (4 SDCCH channels) in order to have 7 TCH instead of 6. This configuration can be applied under certain conditions such as the LA size. Actually, if the size of the LA is too large, a great amount of paging will be generated and the PCH (which is limited in this configuration) will not be able to flow all the paging messages. If the SMS-CB is implemented with combined BCCH, there will be only 3 SDCCH channels.
Page 16/64 12/04/99
4.4 CELL DIMENSIONING 4.4.1 CELL TYPES The number of required TRXs depends on the type of cells. There are two different kinds of cell: standard and extended cell. Extended cell allows bigger propagation delay. The coverage of an extended cell could be bigger than the one of a standard cell (for further information, please refer to [R02]). TRX manages 8 TS in a standard cell and only four in an extended cell.
standard cell
TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7
extended cell
TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7
unused TS Standard cell is the default value used. 4.4.2 BTS CONFIGURATION The number of required TRXs per cell is fixed according to two types of information: the number of required radio time slots and the cell type. The BTS is determined by the cells that it must manage. For example a BTS which manages 3 cells with respectively 4, 5 and 2 TRXS is called a S452. The dimensioning constants of the site are checked at the OMC level: Table 1: BTS configuration limitations Cells per site TDMA per cell TRX per site 6 16 24
These limitations are only OMC-R checks. It does not necessary mean that the O16 configuration exists.
Page 17/64 12/04/99
4.5 LOOK-UP TABLES The following look-up tables give the offered traffic for a given number of TRXs with the NORTEL standard call profile (blocking rate of 2%). When the offered traffic is assessed, these look-up tables give a first assessment about the number of needed TRX. After this first assessment, some deeper dimensioning can be performed according to information of section 4.3.2 (SDCCH dimensioning).
Blocking rate = 2.0%
Table 2: Traffic for a given number of TRXs in a standard cell

TRX 1 2 3 4 5 6 7 8 Erlangs 2.9 8.2 14.0 21.0 27.3 34.7 42.1 48.7 E/TRX 2.9 4.1 4.7 5.3 5.4 5.8 6.0 6.1 TCH 7 14 21 29 36 44 52 59 SDCCH/8 0 1 2 2 3 3 3 4 BCCH 1* 1 1 1 1 1 1 1
* Combined BCCH (under certain conditions such as LA size)
Table 3: Traffic for a given number of TRXs in an extended cell

TRX 1 2 3 4 5 6 7 8 Erlangs 0.6 2.3 5.1 8.2 11.5 14.0 17.5 21.0 E/TRX 0.60 1.14 1.70 2.05 2.30 2.33 2.50 2.625 TCH 3 6 10 14 18 21 25 29 SDCCH/8 0 1 1 1 1 2 2 2 BCCH 1* 1 1 1 1 1 1 1
Page 18/64 12/04/99
Page 19/64 12/04/99
5 BTS DIMENSIONING
5.1 SIGNALLING Two types of signalling are carried on the Abis interface. The first one, related to the Operation and Maintenance, concerns all the component parts (BCF, TRX, Coupling system, Power Amplifier ...). The second one, related to the traffic management, is destined to the TRX module. In other words, all the modules receive O&M signalling, while the TRX receives both O&M and traffic management signallings. 5.1.1 LAPD CHANNEL These two types of signalling (O&M and radio management) are supported by the same LAPD channel. A distinction is made between the BCF signalling and the cell signalling. Primary LAPD: Secondary LAPD: The primary LAPD is the LAPD channel which handles BCF signalling with cell signalling. It is the LAPD channel associated to a cell. It comprises only cell signalling.
Page 20/64 12/04/99
5.1.2 LAPD DIMENSIONING LAPD dimensioning depends on BTS limitations, Abis transmission costs and BSC limitations. At BTS side, the hardware and software limitations are related to the BTS type. At BSC side, two main limitations can occur: connectivity (maximum number of LAPD ports) and real time processing capability. In fact two different strategies can be chosen by the operator to drive the LAPD dimensioning: The first one consists in concentrating the maximum number of LAPD channels at the BTS side in order to save some TS on the Abis interface. The purpose is to decrease the transmission costs and to save some LAPD ports at the BSC side. The drawback of this strategy is that it can create some BSC overload and lead to outage in worst case. Therefore, this strategy must be associated with a capacity analysis to ensure that the BSC can manage such configuration. The second one is highly related to the BSC load. As the BSC real time processing is a key factor in BSS design, it is of interest to split the signalling load on the different boards in order to avoid an overloab on one board. Of course, these two opposite strategies must fulfilled the BTS constraints. Each type of BTS has its own limitations due to hardware or software characteristics. This part deals with the BTS limitations and the BSC limitations in terms of real time processing. The BSC connectivity and the parenting rules at the BSC side will be seen in section 8 (BSC dimensioning). BTS Limitations The limitations depends on the BTS type. Each kind of BTS has its own limitations, therefore the engineering rules are different depending on the BTS type. The low capacity BTS such as S2000H/L or S2000P are not taken into account because they always need one single LAPD channel. In fact, four different BTS have been taken into account: S4000, S8000 BCF up to V11 (O&M software), S8000 BCF since V12 (COAM software), S8000 CBCF .
Page 21/64 12/04/99
S4000: The maximum configuration is S888. The engineering rules are: v Omnidirectional BTSs (up to O8) require only one LAPD channel. v Multi-sectorial sites having more than 8 TRXs require one LAPD channel per cell. v The signalling of multi-sectorial sites having up to 8 TRXs can be handled by a single LAPD channel. But, for the sake of the BSC boards (refer to the following section: BSC limitations in terms of real time processing), one LAPD per cell can be defined.
If a site has several LAPD channels, they must be connected on different SICD ports unless the system will not be configured correctly.
S8000 BCF up to V11: The maximum configuration is S888 and S444_444, S555_333, S666_222 for dualband site. The engineering rules are: v Omnidirectional BTSs (up to O8) require only one LAPD channel. v Multi-sectorial sites having more than 8 TRXs require one LAPD channel per cell. v The signalling of multi-sectorial sites having up to 8 TRXs can be handled by a single LAPD channel. But, for the sake of the BSC boards (refer to the following section: BSC limitations in terms of real time processing), one LAPD per cell can be defined. v For dualband configurations (hexasectorial applications) Sxyz_xyz, the rules are the following ones: if x+y+z+x'+y'+z' 8, 1 LAPD can be sufficient. if x+y+z 8 and x'+y'+z' 8 then allocate 1 LAPD for each frequency band. if x+y+z > 8 or x+y+z > 8 then use 1 LAPD for x,x, another LAPD for y,y, and a third LAPD for z,z
Page 22/64 12/04/99
S8000 BCF since V12: The maximum configurations are O16 for omnisectorial site , S888 for multisectorial site and S444_444, S555_333, S666_222 for dualband site. The engineering rules are: v The number of DRX which can be handled by one LAPD channel is limited to 8. v A site has a maximum of 3 Abis LAPD channels. v If a cell has less than 8 TRX, it has only one LAPD channel. v For dualband configurations (hexasectorial applications) Sxyz_xyz, the rules are the following ones: if x+y+z+x'+y'+z' 8, 1 LAPD can be sufficient. if x+y+z 8 and x'+y'+z' 8 then allocate 1 LAPD for each frequency band. if x+y+z > 8 or x+y+z > 8 then use 1 LAPD for x,x, another LAPD for y,y, and a third LAPD for z,z Examples: S111 can have one, two or three LAPD channels. O8 has necessarily 1 LAPD channel. S444 can have 2 or 3 LAPD channels. S333 can have 2 or 3 LAPD channels.
Page 23/64 12/04/99
S8000 CBCF The maximum configurations are O16 for omnisectorial site , S161616 for multisectorial site and S444_444, S555_333, S666_222 for dualband site. There are only two engineering rules: v The number of DRX which can be handled by one LAPD channel is limited to 8. v A site has a maximum of 3 Abis LAPD channels. Examples: S111 can have one, two or three LAPD channels. O8 can have one, two or three LAPD channel. S444 can have 2 or 3 LAPD channels. In case of 2 LAPD channels, 6 TRxs can defined on each LAPD channels in order to split the load. S333 can have 2 or 3 LAPD channels.
Page 24/64 12/04/99
BSC limitations in term of real time processing The SICD board is the LAPD interface controller that manages the signalling interface between the BSC, the TCU, and the BTS. The SICD4 board (not the SICD8V) can be the bottleneck of the BSC. Several BSC outages in the past were due to an overload on the SICD4 card. The overload was either generated by high Handovers, Paging and Location Update rates or by particulary high voice traffic demands on certain sites (e.g. heavy load sites). An overload mechanism has been introduced on the SICD board. But if this overload mechanism is triggered, it will penalize the traffic (Q.O.S.) on all sites associated with the SICD. Therefore, it is really important to split the load on the different SICDs in order to avoid overload on one SICD.
One LAPD channel must be associated to one cell in high traffic zone (urban zone) for the sake of the SICD for the BSC 6000.
A site with less than 8 TRXs can easily be handled by a single LAPD channel. However associating one LAPD channel to one cell allows a finer balancing of the load on the available SICD boards. This implies that additional DCC/DSC cards may be required on the BTS and that additional timeslots on the Abis interface are also necessary. Please refer to the concerned BTS Product Engineering Information. But it could make sense not applying these engineering rules if the forecast site traffic is low, typically in rural area. Note 1: These engineering rules are applicable in a normal non-congested cell. They cannot be applied in a congestion situation (radio blocking rate > 5%). Note 2: For the other rules (BSCB, SICD) which apply on the BSC side, please refer to section 8 (BSC dimensioning).
Page 25/64 12/04/99
5.2 PCM 5.2.1 ABIS TS DIMENSIONING On the Abis interface, two consecutive TS are used per TDMA and one TS per LAPD. example: S333 on 1 PCM: (3 + 3 + 3) * 2 = 18 Abis TS are required for traffic, 3 LAPD : 3 Abis TS are required for signalling, the total number of Abis TS is 21.
If there are several PCMs, the number of required TS will be higher (for further information, please refer to section 6.1.4). S333 on 2 PCMs: 18 TS for traffic => 10 on the PCM1 and 8 on the PCM2, but the radioSiteMask reserves 10 TS on each PCM. 3 TS for LAPD on each PCM. The total number of TS is (10 + 3)*2 = 26 Abis TS 5.2.2 PCM CONFIGURATION RULES The configuration rules of this section apply to the BTS side. E1 configuration rules The TS0 of a E1 PCM is used for synchronization. The other TS will be configured according to several rules. vThe TS number carrying the primary LAPD, called Rendez-Vous TS (RV TS), obeys the following rule: TS number = TEIBCF + 1. (with TEIBCF<16) vThe TS associated to TRX are mapped by two on two consecutive TS. The convention is to use the higher TS of a PCM first, and then continue toward the lower. vThe secondary LAPD channels will be mapped on the free TS following the Traffic TS. vWhen several PCM link the BTS to the BSC, the traffic TS are equally shared on those PCM. Table 4: PCM configuration for S333 (TEI 0) with 1 PCM
TS # 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 S333 T T T T T T T T T T T T T T T T T T SS SS SP : SS : Signalling Link TS (Primary LAPD) Signalling Link TS (Secondary LAPD) T: Traffic TS SP
Page 26/64 12/04/99
Table 5: PCM configuration for S333 (TEI 0) with 2 PCMs

TS # 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 S333 T T T T T T T T T T SS SS T T T T T T T T SP : SS : T: Signalling Link TS (Primary LAPD) Signalling Link TS (Secondary LAPD) Traffic TS SP
T1 configuration rules Rules: For T1 configuration, the TS will be configured according to several rules: vThe TS number carrying the primary LAPD, called Rendez-Vous TS (RV TS), obeys the following rule: TS number = TEIBCF + 1. (with TEIBCF<16) But all the TEIs cannot be used for T1. TEIs number 3, 7, 11 and 15 are forbidden for T1. The association between the Abis TS on the BTS side and the possible TEI number is provided by the following table. Table 6: TEI to TS association
TEI TS 0 1 2 4 5 6 8 9 10 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12
For further information, please refer to the following explanations (next page). vThe TS associated to TRX are mapped by two on two consecutive TS. The convention is to use the higher TS of a PCM first, and then continue toward the lower. vThe secondary LAPD channels will be mapped on the free TS following the Traffic TS. vWhen several PCM link the BTS to the BSC, the traffic TS are equally shared on those PCM.
Page 27/64 12/04/99
Explanations: For T1 PCM, the SPCMI/PCMI/DTI converts internal PCMs (still in E1: 32 TS) to external PCMs (T1: 24 TS). See Table 7. Table 7: Internal E1 to external T1 conversion
E1 T1 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 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
This means that there is no corresponding external TS for the internal TS4. Information on the internal TS4 never leaves the BTS. For the T1 PCM, the rule for RV TS calculation is still RV TS = TEI number + 1 but applies to internal PCM. So, if the TEI was configured to value 3, the used TS would be 4 and the BTS would still remain impossible to reach. Therefore, TEIs number 3, 7, 11, 15 cannot be used for T1. The association between the Abis TS on the BTS side and the possible TEI number is provided in the table 6.
Page 28/64 12/04/99
5.3 DCC & DSC DIMENSIONING This part is not apllicable to S8000 CBCF, S2000H/L and S2000P. It is only relevant for S4000 and S8000 BCF. DCC/DSC concentrates LAPD signalling links onto a single one from the DRX and the BCF to the BSC. It performs the inverse processing in the opposite way. The rule used for dimensioning the DCC/DSC is: vOne DCC/DSC per LAPD (redundancy not taken into account). The following table summarises the number of used DCC/DSC depending on the number of cells and depending on the number of signalling concentrated links.
Table 8: LAPD/DCC configuration

LAPD link F CELL 1 2 3 4 5 6 1 2 3
H
1+1 1+1 1+1 2+1 2+1 2+1 2+1 2+1 3+1 3+1 3+1 3+1
Note1: Certain configurations listed in the above table can only be achieved with dualband configurations. Note2: If, at a given time, the number of available DCC/DSC runs under the threshold given in the table above, the whole site may be definitively lost (until the right number of DCC/DSC becomes available again). Therefore, it is strongly recommended to have a spare DCC/DSC (the "+ 1" in the table represents the redundancy board).
Page 29/64 12/04/99
5.4 LOOK-UP TABLES These tables take only into account the hardware limitation for the LAPD dimensioning (one LAPD is enough if the total number of TRX is less than 8), because the engineering rules depend on too many parameters (rural or urban environment, SICD or SICD8V board, high mobility). These tables could be useful for a first high level assessment, but not for an accurate design of the network. Moreover, some specific cases occur. For example, the S22 configuration can be performed with the S2000H BTS. In this case the real configuration is 2 O2 BTS (not synchronnized) colocated on the same site and linked in a Drop and Insert configuration. Two LAPD channels are required to handle the 2 BCF signalling and 8 TS to handle the traffic of the four TDMA. Therefore, the number of required TS is 10 and not 9.
PCM E1 (31 TS) / PCM T1 (24 TS) Blocking factor = 2.0%
Table 9: Omnisectorial BTS

Config Standard cell Erlang TCH 2.9 8.2 14.0 21.0 27.3 34.7 42.1 48.7 7 14 21 29 36 44 52 59 Extended cell E1 PCM Erlang TCH Traffic TS LAPD required TS E1 0.6 2.3 5.1 8.2 11.5 14.0 17.5 21.0 3 6 10 14 18 21 25 29 2 4 6 8 10 12 14 16 1 1 1 1 1 1 1 1 3 5 7 9 11 13 15 17 1 1 1 1 1 1 1 1 T1 PCM required TS T1 3 5 7 9 11 13 15 17 1 1 1 1 1 1 1 1 DCC 1+1 1+1 1+1 1+1 1+1 1+1 1+1 1+1
O1 O2 O3 O4 O5 O6 O7 O8
Table 10: Bisectorial BTS

Config S11 S22 S33 S44 S55 S66 S77 S88 Standard cell Erlang TCH 5.8 14 16.4 28 28 42 42 58 54.6 72 69.4 88 84.2 104 97.4 118 Extended cell E1 PCM Erlang TCH Traffic TS LAPD required TS 1.2 6 4 1 5 4.56 12 8 1 9 10.16 20 12 1 13 16.4 28 16 1 17 23 36 20 2 22 28 42 24 2 26 35 50 28 2 30 42 58 32 2 18*2 T1 PCM E1 required TS 1 5 1 9 1 13 1 17 1 22 1 14*2 1 16*2 2 18*2 T1 1 1 1 1 1 2 2 2 DCC 1+1 1+1 1+1 1+1 2+1 2+1 2+1 2+1
Page 30/64 12/04/99
Table 11: Tri and hexasectorial BTS

Config S111 S222 S333 S444 S555 S666 S777 S888 S111111 S222222 S333333 S444444 Standard cell Erlang TCH 8.79 21 24.6 42 42.0 63 63.0 87 81.9 108 104.1 132 126.3 156 146.1 177 17.58 42 49.2 84 84.0 126 126.0 174 Extended cell Erlang TCH 1.8 9 6.8 18 15.2 30 24.6 42 34,5 54 42.0 63 52,5 75 63.0 87 3.6 18 13.7 36 30.5 60 49.2 84 Traffic TS 6 12 18 24 30 36 42 48 12 24 36 48 E1 PCM LAPD required TS 1 7 1 13 3 21 3 27 3 19*2 3 21*2 3 25*2 3 27*2 1 13 6 18*2 6 24*2 6 30*2 T1 PCM E1 required TS 1 7 1 13 1 21 1 15*2 2 19*2 2 21*2 2 17*3 2 19*3 1 13 2 18*2 2 24*2 2 22*3 T1 1 1 1 2 2 2 3 3 1 2 2 3 DCC 1+1 1+1 3+1 3+1 3+1 3+1 3+1 3+1 1+1 3+1 3+1 3+1
Page 31/64 12/04/99
Page 32/64 12/04/99
6 ABIS ARCHITECTURE
6.1 DROP&INSERT CONFIGURATIONS 6.1.1 POSSIBLE CONFIGURATIONS Different configurations are possible on the Abis interface. They are called Star, Drop&Insert, and Hub&Spoke configurations. The following figure presents these different configurations. Figure 1: Star, Drop&Insert and Hub&Spoke Configurations
Star BSC
Chain D&I BSC
Loop D&I BSC
Hub&Spoke BSC
BTS BTS BTS BTS BTS BTS
BTS BTS BTS
BTS
BTS
BTS
BTS
PCM Redundant PCM.
In case of loop, one side is considered as redundant PCM
The loop and chain Drop&Insert configurations are guaranteed for up to 6 BTSs. The theorical limitation is 10 O1 BTSs on 1 E1 and 8 O1 BTSs on 1 T1, but R&D tests and guarantees up to 6 BTSs.
Page 33/64 12/04/99
6.1.2 TEI ISSUES When a BTS is in a chained configuration, the BCH TEI numbers assigned to each BTS must be in an ascending sequence. The rule for the chain configuration is x<y<z. The values do not need to be adjacent. Figure 2: Loop Drop&Insert configuration
For the Hub&Spoke configuration the requirements are x<y<z and x<w. There is no constraint between w and the couple y,z (w and y can be equal). Note that the Hub&Spoke is not considered as a D&I configuration because of the fork. Figure 3: Hub&Spoke configuration.
Note that all the TEI can not be higher than 15.
Page 34/64 12/04/99
6.1.3 DTI/PCMI ISSUES PCM interfacing is provided by the DTI board for 1G BTS (S4000, S2000, S2000E), and by the PCMI board for 2G BTS (S8000I/O, S2000H/L). DTI board handles the interface of 1 PCM digital trunks. PCMI board handles the interface of 2 PCM digital trunks. The following table presents the mapping between PCM ports and PCMI/DTI boards. Table 12: PCM port
PCM ports 0 1 2 3 4 5 PCMI board PCMI 0 port 0 PCMI 0 port 1 PCMI 1 port 0 PCMI 1 port 1 PCMI 2 port 0 PCMI 2 port 1 DTI board DTI 0 DTI 1 DTI 2 DTI 3 DTI 4 DTI 5
The PCM links connecting the BSC to BTS must be arranged for synchronization reasons. A PCM crossing a BTS enters via an even PCM port and leaves via an odd PCM port. For the loop configuration, the opposite path can be set up. The following figure shows some different Drop&Insert configurations with or without PCMI board redundancy. Figure 4: PCMI configurations for drop&insert
D&I in chain without redundancy
BSC BTS
PCMI0 0 1
D&I in loop without board redundancy

BSC BTS
PCMI0 0 1
BTS
PCMI0 0 1
BTS
PCMI0 0 1
BTS
PCMI0 0 1
BTS
PCMI0 0 1
D&I in chain with board redundancy

BSC BTS
PCMI1 0 PCMI0 1 0 1
D&I in loop with board redundancy

BSC BTS
PCMI1 PCMI0 0 1 0 1
BTS
PCMI1 0 PCMI0 1 0 1
BTS
PCMI1 0 PCMI0 1 0 1
BTS
PCMI1 PCMI0 0 0 1 1
BTS
PCMI0 0 1 PCMI1 0 1
Page 35/64 12/04/99
For 1G BTS in loop Drop&Insert without DTI redundancy (following figure), if a DTI failure occurs, only one PCM will be lost and the opposite path will be activated. For 2G BTS in the same configuration, if a PCMI failure occurs, two PCMs will be lost. Therefore as the two ways of connection will be impossible, the site will be lost. The PCMI redundancy avoid to lost the site in case of PCMI failure. Figure 5: D&I in loop without board redundancy: 1G versus 2G
D&I in loop without board redundancy
BSC
BTS A
PCMI0 0 1
BTS B
PCMI0 0 1
BTS C
PCMI0 0 1
BSC
BTS D
DTI0 DTI1
BTS E
DTI0 DTI1
BTS F
DTI0 DTI1
Therefore, changing a S4000 by a S8000 is not as easy as it appears. There are some impacts on redundancy, and then on reliability.
Page 36/64 12/04/99
6.1.4 RADIOSITEMASK CONFIGURATION Rules For each site, a parameter called RadioSiteMask is configured in order to define which TS are reserved. vThe same mask is applied to all the PCM connecting a BTS vThe primary LAPD is not included in the mask. The TS carrying the primary LAPD has a defined position on the BTS side: TS number = TEIBCF + 1. vThe traffic TS are mapped by two on two consecutive TS. A convention is to use first the higher TS of a PCM and then continue toward the lower one. The secondary LAPD follows the same rules as the traffic TS. vWhen several PCM link the BTS to the BSC, the traffic TS are equally shared on those PCM. Some engineering rules define the value of the RadioSiteMask (total number of timeslots set to 1): For 1 PCM connected: (Nb LAPD - 1) + Nb TRX *2 For 2 PCM connected: (Nb LAPD - 1) + Ent[(Nb TRX + 1)/2] * 2 For 3 PCM connected: (Nb LAPD - 1) + Ent[(Nb TRX + 2)/3] * 2 For n PCM connected: (Nb LAPD - 1) + Ent[(Nb TRX + (n-1))/n] * 2
MIf the TEI are not adjacent, it is strongly recommended not to use the TS between
TS0 and the TS which carried the primary LAPD of the BTS with the bigger TEI.
Page 37/64 12/04/99
Example 1 This first example concerns a chain configuration. One S444 and one S222 are linked together in order to optimize the transmission link. Figure 6: Drop & Insert example
Site A Site B
PCM3
BSC
PCM1
S444
PCM2 PCM4
S222
TEI 1
TEI 0
In this example the PCM4 is a redundant PCM. Note that the TEI are in ascending sequence. The traffic of the BTS A is equally shared between the 2 PCMs. The secondary LAPD follow the TS supporting the traffic. The primary LAPD is not included in the radioSiteMask. The BSC is a BSC6000, then 3 LAPD channels are defined for the site B in order to be able to split the load on the different SICDs. Table 13: PCM E1 RadioSiteMask
TS number PCM 1 PCM 2 PCM 3 RadioSiteMask Site A RadioSiteMask Site B
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Sa Sa Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Sb Sb Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Sb Sb Pb 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 Pb Pa
Table 14: PCM T1 RadioSiteMask

TS number PCM 1 PCM 2 PCM 3 PCM 4 RadioSiteMask Site A RadioSiteMask Site B Ta Tb Sa Sb
24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Sa Sa Tb Tb Tb Tb Tb Tb Sb Sb Pb Pa Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Tb Sb Sb Pb Tb Tb Tb Tb Tb Tb 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0 0
Traffic Ts site A Traffic Ts site B Secondary LAPD site A Secondary LAPD site B
Pa Pb
Primary LAPD site A Primary LAPD site B
Page 38/64 12/04/99
Example 2 This other example concerns the Hub&Spoke configuration. Four omnisectorial BTSs are linked in order to save transmission costs. Figure 7: Hub&Spoke example
Site B
PCM3
Site A
PCM1
O3
TEI 1 Site C Site D
PCM5
BSC
PCM2
O5
TEI 0
PCM4
O4
TEI 1
O2
TEI 2
The traffic of the BTS A is equally shared between the 2 PCMs, while the traffic of the other BTSs is supported by the PCM1 or the PCM2 but not shared. Table 15: PCM E1 RadioSiteMask
TS number PCM 1 PCM 2 RadioSiteMask Site A RadioSiteMask Site B RadioSiteMask Site C RadioSiteMask Site D
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Ta Ta Ta Ta Ta Ta Tb Tb Tb Tb Tb Tb Ta Ta Ta Ta 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Tc Tc Tc Tc Tc Tc Tc Tc Td Td Td Td Pb Pa Pd Pc
Table 16: PCM T1 RadioSiteMask

TS number PCM 1 PCM 2 RadioSiteMask Site A RadioSiteMask Site B RadioSiteMask Site C RadioSiteMask Site D
24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 Ta Ta Ta Ta Ta Ta Tb Tb Tb Tb Tb Tb Ta Ta Ta Ta 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Tc Tc Tc Tc Tc Tc Tc Tc Td Td Td Td Pb Pa Pd Pc
Page 39/64 12/04/99
6.1.5 RADIOSITEMASK EXTENSION STRATEGY The future expansion of the network may be taken into account when dimensioning the RadioSiteMask. It will make the network roll-out easier. The radioSiteMask parameter is a class 2 parameter located in the btsSiteManager Q3 object. It means that this parameter can only be set when the object is locked and the parent bsc object is unlocked. Therefore, the modification of the radioSiteMask will involve interruption of service. Moreover, forecasting the future extension will avoid some complex RadioSiteMask configurations that are difficult to manage. Different configuration strategies can be applied according to the knowledge of the extension politics of the operators.
First strategy: Assumption: The number of the future additionnal DRXs in a BTS can be assessed. In this case, it will be of interest to increase the RadioSiteMask. This method allows extensions without requiring the reconfiguration of the RadioSiteMask (no interruption of service). Figure 8: Example
Site A Site B
PCM2
BSC
PCM1
S222
TEI 0
O2
TEI 1
The site A is composed of 6 DRXs in a cabinet. One cabinet can contain up to 8 DRXs. Therefore, it could make sense to foresee the introduction of the 2 other possible DRXs. It would facilitate their introduction and avoid any interruption of service for the two sites.
Page 40/64 12/04/99
Table 17: RadioSiteMask (first strategy)

TS number PCM 1 PCM 2 RadioSiteMask Site A RadioSiteMask Site B Ta Tb Sa Pa Pb
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Sa Sa Tb Tb Tb Tb Tb Tb Tb Tb Pb Pa Pb
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0
Traffic TS site A Traffic TS site B Secondary LAPD site A Primary LAPD site A Primary LAPD site B
Of course, if Site A is composed of three radio cabinets, it does not make sense to dimension the RadioSiteMask for a 3S888. Another strategy has to be considered.
Second strategy Assumptions:Nortel has no knowledge of the future number of added DRXs. Nortel is convinced that the operator will not add any other BTSs in a D&I configuration. In such case, the RadioSiteMask can be defined as indicated in Table 18. Table 18: RadioSiteMask (second strategy)
TS number PCM 1 PCM 2 RadioSiteMask Site A RadioSiteMask Site B Ta Tb Sa Pa Pb
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Sa Sa Tb Tb Tb Tb Pb Pa Tb Tb Tb Tb Pb 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0
Traffic TS site A Traffic TS site B Secondary LAPD site A Primary LAPD site A Primary LAPD site B
This configuration allows to easily increase capacity in the both site. The introduction of additional DRX in a site will not perturb the other one, only one RadioSiteMask is impacted. Moreover the two RadioSiteMask stay simple and easy to manage. The drawback is that it will be difficult to add a BTS in a D&I configuration, because the RadioSiteMask of the site B must be modified (interruption of service).
Page 41/64 12/04/99
Third strategy Assumption: Nortel has no information about the extension policy. If Nortel has any information, the two previous strategies are not recommended. The "normal" configuration with the engineering rules of page 37 may be followed. The BTS introduction in a Drop&Insert configuration will be easy. Moreover, it is also possible to introduce additional DRXs without interruption of service for the second site. Table 19: RadioSiteMask (Third strategy)
TS number PCM 1 PCM 2 RadioSiteMask Site A RadioSiteMask Site B Ta Tb Sa
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Ta Tb Tb Tb Tb Ta Ta Ta Ta Sa Sa Tb Tb Tb Tb Pb Pa Pb
1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Traffic TS site A Traffic TS site B Secondary LAPD site A
Pa Pb
Primary LAPD site A Primary LAPD site B
The drawback is that some RadioSiteMask can be quite complex and it will become more and more difficult to make them evolve. 6.1.6 ADDITINAL FEATURE OF TDMA/ABIS MAPPING CONFIGURATION FOR V11 A new V11 feature secures the Abis interface. FM844 "Traffic Channel Defense" allows to reconfigure the TDMA according to their priority in case of PCM failure for a multiPCM site, as long as one PCM is available (refer to [R04]). If the following requirements are fulfilled: the PCMs are not full, if the rentalfees are per used PCM and not per used TS, then it could make sense to increase the radioSiteMask. It will allow more TS reconfigurations and then to lose less traffic channels. Moreover it could facilitate the introduction of new DRXs. The drawback is that the evolution of the network could be more difficult (for example, adding a BTS in drop&insert). There is a trade-off between quality of service and flexibility. For further information on this feature, please refer to the V11 FEI [R04].
Page 42/64 12/04/99
6.2 HUBS 6.2.1 CROSS-CONNECT Since the V8 system release, a new feature is available: TEI decorrelation. It allows the simulation of a Drop&Insert function from the BSC point of view, without using the BTS in Drop&Insert configuration. The TEI of the BTS can be the same, then since V8, the TEI number and the "Rendez-vous TS" are decorrelated on the BSC side. The number of the "Rendezvous TS" is configurated by the pcmTimeSlotNumber parameter on the MMI interface. pcmTimeSlotNumber is located in the btsSiteManager Q3 object. Figure 9: Cross-connect configuration
For the BTS, the installation is easier because all the sites have the same configuration (Star with a TEI = 0). For the BSC, the 3 sites are in drop and insert so the drop and insert rules must be respected on the BSC side. The choice of the TS for the signalisation must be done in accordance with the crossconnect configuration. Figure 10: Crossconnect configuration
Page 43/64 12/04/99
The traffic TS must be at the same place (TS number) on the two sides of the crossconnect. This rule does not concern the primary signalling TS which has a fixed position on the BTS side (TEIBCF+1). Table 20: RadioSiteMask configuration with crossconnect
TS number PCM A PCM B PCM C PCM D RadioSiteMask Site A RadioSiteMask Site B RadioSiteMask Site C Ta Tb Tc Pa Pb Pc
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Ta Ta Ta Ta Tb Tb Tb Tb Tc Tc Tc Tc Ta Ta Ta Ta Tb Tb Tb Tb Tc Tc Tc Tc Pa Pb Pc Pc Pb Pa
1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Traffic Ts site A Traffic Ts site B Traffic Ts site C Primary LAPD site A Primary LAPD site B Primary LAPD site CSwitch
6.2.2 SWITCH Hubs can act as switch for redundancy purpose. The main advantage of this architecture is that in case of PCM1 failure, the hub1 is able to switch on the redundant PCM2 without loosing the communications. Figure 11: Architectuire with Switch
BTS
PCM1
BSC
Hub1
PCM2
Hub2
BTS
BTS
It can be implemented with digital cross-connect such as PDMX-E (Nortel product).
Page 44/64 12/04/99
Page 45/64 12/04/99
7 TRANSMISSION MEDIUM
7.1 CLOCK Timing requirements according to G811 are: Table 21: Timing requirements Time 98,89% 1% 0,1% 0,01% | f/f | | f/f | 10 11 1011 < | f/f | 2109 210 9 < | f/f | 510 7 510 7 < | f/f |
One characteristic defines the quality of the PCM clock for the BSS sub-systems and especially for the BTS. There are two requirements to consider: The requirement for a PCM: 50 ppm (see G732). The requirement for the BTS in order to generate a reference time for radio interface. The BTS uses the clock reference from the network to generate a 5*10 -8 precision timing reference for the radio interface. Long-term accuracy recommended for PCM E1 (2,048 MHz) and PCM T1 (1,544 MHz): | f/f | = 10 -9 or 0,001 ppm This characteristic assures a good transmission quality for BTS frequencies allowing the mobile connections and avoiding the disturbance of the adjacent frequencies. Note: it is not necessary that all GSM sub-systems are synchronized with the same clock, but that they respect the recommendations defined above.
Page 46/64 12/04/99
7.2 TRANSMISSION QUALITY REQUIREMENTS To maintain the PCM quality to a good level, BER shall not exceed 10E-4. To not disturb the voice quality, BER shall be maintained at or above 10E-6. PCM unavailibility also has a big impact on the BSS. The unavailibility is determined by errors detected by the DDTI board. The different types of error are: For E1 PCM links : No signal Signal Indicator Alarm error Frame alignment loss Synchronization loss Frame error Distant alarm indicator error CRC error For T1 PCM links : No signal Signal Indicator Alarm error Frame alignment loss Synchronization loss Distant alarm indicator error The time duration of the PCM unavailibility is determined by the number of Errored Seconds (ES if at least an error occurs for 1 second). For example, if the signal is lost for 3.1 seconds, the PCM unavailibility time could be 5 seconds.
SIGNAL
ES ES ES ES
SIGNAL
ES
Page 47/64 12/04/99
The time duration of the PCM unavailability impacts the BTS in different ways: PCM unavailibility < 5 seconds When the BSC-BTS link is interrupted during less than 5 seconds (5 Errored Seconds), nothing happens. The communications are disturbed, but not lost.
PCM unavailibility (BER > 10E-3) for less than 5 seconds leads to disturb the communications.
PCM unavailibility between 5 seconds and 30 minutes A timer exists that triggers a defense BSS mechanism. If the BSC-BTS link is interrupted for more than this timer, the BSC will try to find another PCM to reestablish the contact. When the contact is reestablished, the BSC will lead in the BTS to a reset of PCM boards and a BCF and TRX reconfiguration. Today this timer is set to 5 seconds, which allows fast recovery in case of a real failure, and fast alarm reporting, and however tolerates short transient link outages often encountered especially with microwaves links. This timer is therefore a tradeoff between fast recovery and tolerance to transient faults.
PCM unavailibility beween 5 seconds and 30 minutes leads to lose current communications plus a BTS reconfiguration time (BTS dependent, refer to [R20]).
PCM unavailibility > 30 minutes If the interruption lasts for more than 30 minutes, the BTS resets itself, and will be redownloaded and reconfigured when the link is up again. In case of DRX (S8000 or S2000H/L) or AMNU/DCU4, the download procedure is reduced. In fact, the software is not downloaded, but only checked.
PCM unavailibility of more than 30 minutes leads to a complete reboot of the BTS which could last several minutes depending on the configuration (refer to [R20]).
The reconfiguration and reboot time depend on the BTS configuration. This kind of information can be found in the document "Performance Tests Results Report" ([R20]) which gives a summary of performance tests performed in PIV.
Page 48/64 12/04/99
7.3 CSU The CSU equipment is designed to be inserted between the Abis link provided by the operator and the BCF subrack. Its purpose is to test and recalibrate the incoming and outgoing signal and ensure that it meets the recommendations. The equipment includes a set of alarms displayed on the CSU front panel. Any alarm condition (or power failure) releases a single pole alarm relay connected to the user alarms of the BTS. Three types of CSU equipment can be ordered: CSU T-serv II, CSU T-smart, and CSU MPATH. The MPATH CSU offers additional features (such as SNMP management) compared to other types of CSU. The CSU equipment is designed for T1 PCM and is mandatory for the US market. 7.4 HDSL 7.4.1 INTRODUCTION HDSL is a technology that allows to convey, on a few kilometers, a PCM signal over ordinary twisted pairs. This technology becomes more and more popular, as a cheap solution to provide PCM links to remote locations. This applies generally to the Abis link, including Drop&Insert configurations. Figure 12: HDSL solution
BSC
BTS
4 shielded pairs master

HDSL modem
2 twisted pairs
slave HDSL modem
4 shielded pairs
PCM
HDSL
PCM
For short distances (up to 1.5 Km), only one wires twisted pair is needed. Two wires twisted pairs are required for longer distance (up to 4 Km). The distances depend on the modems and on the quality of the twisted pair wires. Therefore the values given above are only for indication purposes and must not be communicated to customers.
Page 49/64 12/04/99
7.4.2 HDSL ISSUES HDSL modems use a very complex synchronization scheme based on a masterslave configuration. The master HDSL modem is on the BSC side and the slave one is on the BTS side. The consequence is that any short link drop or click disturbancy leads to long link unstability. Depending on the modem, 1 second interruption may translate up to 15 seconds. The timer that triggers a defense BSS mechanism is set to 5 seconds (refer to section 7.2 ). This value may no longer be the right trade-off between fast recovery and tolerance to transient fault for the HDSL link. For the network that uses HDSL, a timer value of 15 seconds seems to be a better trade-off for the sake of the link stability (but QOS impact). This specific parameter setting of the BSS defense mechanism is not mandatory. Some HDSL modems work properly with the default configuration. Note that the timer value applies to all PCM links of the BSC and not only to the HDSL links. 7.4.3 HDSL MODEMS The HDSL modems are systematically tested by R&D in order to remove modems which are suspected to lead problems on the field. The list of the recommended HDSL modems and the list of the inadvisable ones can be found in the document "HDSL modem layer1 qualification" ([R21]). For all modems considered OK, a very short disturbance on the Abis line (i.e. : 1 second cut) leads to unavailability of the link for more than 10 seconds.
Page 50/64 12/04/99
7.5 MICROWAVES 7.5.1 MICROWAVE DESIGN GUIDELINES MW link have the following advantages over leased lines: Meet superior reliability, allow total control over them, easy expansion, and rapid deployment. However, the following design guidelines must be taken into account: L.O.S (line of Sight), Distance, Parabolic antennas, Frequency dependence, Interference limitation. L.O.S. needed That means that a MW link is terrain dependant, and sometimes a link cannot be installed. Indeed the clearance has to be 60% of the first Fresnel zone, plus a security factor (5 or 6 m) for errors on terrain data. The 60% F1 is calculated for standard atmosphere (k=4/3) and the atmosphere can change, needing the link a better clearance. In this case a calculation can be done with k=2/3 and 50% F1. Distance The effects of rain and multipath limit the distance a link can cover, so that sometimes a repeater is needed to cover this distance. In order to calculate the unavailability due to rain, the rain zone where the link is going to be installed, has to be known ; this will give the rain rate that is exceeded the 0.01% of the annual time (i.e. k rain zone is 42 mm/h). Figure 13: Microwave solution
Page 51/64 12/04/99
When designing a link, the availability (unavailability) is an objective that is fixed by the operator in order to meet its quality requirements. For example, the availability due to propagation in a 1+0 (nonprotected) can be 99.99% of the annual time; for this objective, if the rain zone is k (42 mm/h), in 23 GHz up to 13 Km can be covered (0.6 m antennas at both sites and vertical polarization), and in 38 GHz up to 6 Km (0.6 m antennas at both sites and vertical polarization). Parabolic antennas Parabolic antennas must be installed. Wind loadings have to be considered on the tower, or the place where the antenna is going to be installed. The tilt and twist of the tower, that increases with the height, can affect the alignment of the antenna, reducing the receive signal level, and consequently the fade margin. Frequency dependence Sometimes it is difficult to get a channel from the local government; normally this depends on the working band (15 GHz, 23 GHz etc..). Interference limitation There is a limitation in the number of links that can converge at one point (concentrator) due to interference mechanism. In digital MW links the interference reduces the threshold, which means that the fade margin decreases and the link will be unavailable for more time than the time it was calculated for. Alternate polarization (cross polarization discrimination) and high gain antennas (more directivity) can offset these effects. For further information, please refer to the web pages of the transmissions group at the following URL address:
http://136.147.68.68/ned/ND_AE/ND/Transmission/Transmission.html
Page 52/64 12/04/99
7.5.2 MICROWAVE QUALITY REQUIREMENTS The ITU-T G.821 defines different grades of service for the microwave transmissions: high grade (HG), medium grade (MG) and local grade (LG). Figure 14: Reference communication of ITU.
1250 km
27500 km 25000 km
1250 km
Local grade
Medium grade
High grade
Medium grade
Local grade
The performance of the grade of service can be estimated by 3 parameters:
F Degraded Minutes:
DM if BER > 10-6 for 1 minute.
F Severely Errored Seconds:

SES if BER > 10-3 for 1 second.
F Errored Seconds:
ES if at least an error occurs for 1 second. The performance objectives of these 3 grades of service are: Figure 15: Performance objectives:
PERFORMANCE OBJECTIVES: MG LG Global HG Degraded < 10% < 4% < 1.5% < 1.5% Minutes Severely < 0.2% < 0.04% < 0.015% < 0.015% Errored * * Seconds Errored < 8% < 1.2% < 3.2% < 1.2% Seconds
Note*: 0.05% can be added if m/w is used. DM: Min. at 10E-6; SES: Sec. at 10E-3; ES: Sec. with errors.
Page 53/64 12/04/99
Depending on the configuration local or medium grade links are recommended for Abis interface. Medium grade quality is 50% to 100% more expensive than local grade as it requires redundant equipment. It must be proposed only if specified by customer. 7.5.3 MICROWAVE CONFIGURATIONS It is possible to combine the drop and insert functionality of the BTS product and the microwaves product in order to insure the transmission security and capacity. The following configurations are given as example. Figure 16: Chain Drop&Insert with microwaves
medium or local grade
Central Office
DMS Switch
TCU
BSC
BTS
BTS
BTS
Figure 17: Loop Drop&Insert with microwaves

local or medium grade local grade ring
Central Office BTS 1 BTS 2 BTS 3
DMS Switch
TCU
BSC
BTS 5
BTS 4
Page 54/64 12/04/99
Figure 18: Hub and Spoke with microwaves

local or medium grade local grade
Central Office BTS BTS
DMS Switch
TCU
BSC BTS
BTS S222
BTS
BTS
The minimum capacity of the microwaves equipment is 2 E1 PCM links. Therefore, from the BSC point of view, the Loop D&I implementation (fig. 17) is seen as below: Figure 19: Abis configuration with microwaves on BSC side BTS 1 BTS 2 BTS 3
BSC
BTS 4 BTS 5
Page 55/64 12/04/99
7.5.4 MICROWAVE EQUIPMENT REDUNDANCY PCM link failure can be more diverse than for a cable support. Two main events can occur: either an equipment failure, either a signal fading due to rains or multipath. In all cases, all the PCM carried between the two radio systems are brought down. A failure of only one PCM link is not possible, contrary to the LL cable solution. PCM link failure due to equipment can be minimized by redundant configuration. Figure 20: Typical non-protected and protected microwave equipment architecture
Two protected configurations can be considered: The first one with redundant DIU and RFU with a single antennae (a wave guide coupler must be used). The second one uses two antennas without wave guide coupler. It allows to avoid the PCM link failure due to antennea falling out of alignment.
Page 56/64 12/04/99
Page 57/64 12/04/99
8 BSC DIMENSIONING
8.1 BSC TYPE The following table gives the board configuration related to Abis interface for each available BSC type.
Table 22: Product range Architecture Type DDTI(**) BSCB(*) SICD SICD8 1 6 0 2 2 10 0 4 BSC 6000 3 14 0 6 4 20 5 24 1 24 2 24 BSC 12000 3 24 4 24 5 24
11+1 11+1 11+1 11+1 11+1 11+1 11+1 8 10 1 2 3 4 5
*The BSCB board is optional for the BTS LAPD concentration. If this option is not chosen, the number of BSCB boards required is zero. The number of BSCB boards shown in the table indicates the maximum number of BSCB boards for each type of BSC. The minimum number of BSCB boards is 2. The quantity of boards depends on the number of LAPD channels (or sites) to be concentrated. One board is reserved for redundancy purpose (+1). ** There is a maximum of 24 DDTI boards per BSC12000 (whatever the product version is: 1201/ 1202/1203/1204/1205). The basic configuration provides 10 DDTI boards. But, depending on the needs, it is possible to add DDTI units up to 24. For the BSC 6000 product family, there are 6/10/14/20/24 DDTI boards depending on the product version 602/604/606/608/610 respectively. These numbers are fixed.
Page 58/64 12/04/99
8.2 SICD/SICD8V BOARDS 8.2.1 LIMITATION RULES SICD limitation rules The limitation rules for the SICD board are: vOne SICD board has 4 ports (hardware design). One SICD board can manage up to 4 physical channels of LAPD (concentrated with BSCB or non concentrated). vOne LAPD equipment (SICD ports) supports up to 10 TEI. Note that one TCU corresponds to one TEI, one BCF corresponds to one TEI, and one TRX corresponds to one TEI. v16 is the maximum number of TDMA per SICD due to traffic load. vAll the LAPD equipment are reserved for the Abis interface except the fourth port (port 3) of the SICD 0 which is used for the TCU (by convention). SICD8V limitation rules The limitation rules for the SICD8V board are: vOne SICD board has 8 ports (hardware design). One SICD board can manage up to 8 physical channels of LAPD (concentrated with BSCB or non concentrated). vOne LAPD equipment (SICD ports) supports up to 15 TEI. Note that one TCU corresponds to one TEI, one BCF corresponds to one TEI, and one TRX corresponds to one TEI. v64 is the maximum number of TDMA per SICD due to traffic load. vAll the LAPD equipment are reserved for the Abis interface except the fourth port (port 3) of the SICD8V 0 which is used for the TCU (by convention). 8.2.2 PARENTING RULES To avoid overload on one SICD due to high spot traffic, use the following rules for parenting. vTwo neighbor sites must be on two different SICDs. vTwo cells of a same site must be on two different SICDs. Of course this condition can only be applied if the two cells are mapped on two different LAPD channels. A SICD8V board does the same job as a SICD, but the processor is more powerful. Furthermore, the inhomogenous load on the various SICD8V has less impact with SICD8V than with SICD because the load is only split onto 5 boards as opposed to 10 for SICD.
Page 59/64 12/04/99
8.2.3 LOOK-UP TABLES
Table 23: SICD limitations Architecture Type SICD/SICD8V board LAPD eqpt LAPD eqpt for Abis TEI per LAPD eqpt TDMA per SICD/SICD8V TDMA* 1 2 8 7 10 16 32 2 4 16 15 10 16 64 BSC 6000 3 6 24 23 10 16 96 4 8 32 31 10 16 128 5 10 40 39 10 16 160 1 1 8 7 15 64 64 2 2 16 15 15 64 128 BSC 12000 3 3 24 23 15 64 192 4 4 32 31 15 64 256 5 5 40 39 15 64 320
*This number can be worked out from nb SICD * max TDMA per SICD.
8.3 BSCB AND TSCB BOARDS Use of BSCB is optional. If this option is not chosen, the number of BSCB boards required is zero. The minimum number of BSCB boards is 2. The quantity of boards depends on the number of LAPD channels (or sites) to be concentrated. The associated parameter is a class 0 parameter (xSCBConfiguration in the bsc object). Therefore, every time a board is added, the BDA needs to be rebuilt. The BSC does not have a dedicated board used for redundancy, but manages a pool of BSCB boards. When one BSCB fails, the BSC reconfigures the whole configuration of the failed BSCB onto a free BSCB board (one without any LAPD mapped on it). When new concentrated LAPD terminals are declared and LAPD channel locations are moved from one SICD to another, it is very important to check that a BSCB remains free.
The BSCB boards can be the bottleneck of the BSC in some configurations. Therefore it is very important to follow the rules describe in the document "BSCB Engg Information: Load monitoring and optimization" ([R22]).
Page 60/64 12/04/99
Figure 21: Dimensioning the Abis interface with LAPD concentration

BTS sites
Abis Interface + BSC internal connectivity
Max. of 12 non-concentrated LapD channels used per BSCB board BSCB Max. of 3 concentrated LapD channels used per BSCB board
BSCB
BSCB
SICD8V
SICD8V
Max. of 8 LapD Equipment used per SICD8V board (4 LapD equipment per SICD board)
A BSCB board processes the concentration of 12 unconcentrated links to 3 (3 times 4 LAPD unconcentrated into 1 LAPD concentrated). The limit of 10 TEIs per SICD port (BCF+TRX) or 15 TEIs per SICD8V port is still in effect.
Table 24: Maximum number of sites per BSC Architecture Type SICD/SICD8V board LAPD eqpt LAPD eqpt for Abis BSCB max number of sites (*) 1 2 8 7 0 7 2 4 16 15 0 15 BSC 6000 3 6 24 23 0 23 4 8 32 31 5 10 40 39 1 1 8 7 2 2 16 15 BSC 12000 3 3 24 23 4 4 32 31 5 5 40 39
11+1 11+1 11+1 11+1 11+1 11+1 11+1 124 138 28 60 92 124 138
*Number of sites per BSC, depending on the number of SICD and BSCB (with BSCB redundancy).
Page 61/64 12/04/99
8.4 DDTI BOARDS Since the BSC extracts the synchronization clock from PCM 0, 2, 4, and 6, these spans are used only for the Ater interface. The others can be used indiscriminately either for the Abis or the Ater interface but must use some spread convention. Spread convention nc. 1 In order to minimize the number of remainning PCMs when a board fails, it is best to spread the spans of a BTS on different DDTIs. Spread convention nc. 2 Use the same previous rule when configuring Ater PCMs. Avoid the configuration of two Ater PCMs on a same DDTI board. Table 25: PCM allocation for the BSC6000 Type5 PCM Number 0, 2, 4, 6 1, 3, 5, 7 to 47 Allocation Ater Ater or Abis
The use of PCM 0, 2, 4, 6 for Abis interface may lead serious synchronization problems for the whole BSS. So, this configuration is forbiden.
A DDTI board handles two PCMs which are connected to port 0 and port 1. PCM_Number = 2*DDTI_Number + Port_Number
Page 62/64 12/04/99
9 APPENDIX
This configuration has been tested in a network. This interesting configuration uses cross-connect and Hub&Spoke configuration. Figure 22: Example of complex configuration
S11
Cross-connect
TEI4 TEI2 TEI1 TEI3
S111
BSC
S111
TEI0
S111 S111
TEI1
S11 S111
TEI2
S11
TEI3
S111
TEI4
Page 63/64 12/04/99
END OF DOCUMENT
Page 64/64 12/04/99

ABIS Interface

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ABIS Interface

Uploaded by

Copyright:

Available Formats

GSM

Abis Interface Engineering Guide

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN 12/04/99

ABIS INTERFACE ENGINEERING GUIDE

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 8/64 12/04/99

Transmission Network Recommendations PE/SYS/DD/0253 V1.03/EN B. Couaillet

L. Jullien T. Bachelier S. Luong T. Bachelier

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 9/64 12/04/99

[R18] [R19] [R20] [R21] [R22]

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 10/64 12/04/99

3 ABBREVIATIONS AND DEFINITIONS

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 11/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 12/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 13/64 12/04/99

Page Intentionally Left Blank

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 14/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 15/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 16/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 17/64 12/04/99

Table 2: Traffic for a given number of TRXs in a standard cell

* Combined BCCH (under certain conditions such as LA size)

Table 3: Traffic for a given number of TRXs in an extended cell

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 18/64 12/04/99

Page Intentionally Left Blank

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 19/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 20/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 21/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 22/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 23/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 24/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 25/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 26/64 12/04/99

Table 5: PCM configuration for S333 (TEI 0) with 2 PCMs

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 27/64 12/04/99

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 28/64 12/04/99

Table 8: LAPD/DCC configuration

Abis Interface Engineering Guide PE /IRC/APP/0079 01.08 / EN

Page 29/64 12/04/99