Dimensioning Rules For CS and PS Traffic PDF

1AA 00014 0004 (9007)A4
All rights reserved. Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization.
Dimensioning Rules for CS and PS Traffic

with BSS Software Release B11
(TDM transport)
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
1/47

CONTENTS
1. REFERENCE DOCUMENTS ....................................................................................... 4
2. INTRODUCTION .................................................................................................. 5
3. DEFINITIONS ...................................................................................................... 5
4. AIR INTERFACE ................................................................................................... 6
5. A-BIS INTERFACE................................................................................................. 7
5.1
Number of time-slots available per A-bis Multidrop link ......................................... 7
5.2
Usage of A-bis timeslots ............................................................................... 7
5.3
Transport of Signalling on the A-bis interface ..................................................... 8
5.4
Two A-bis-links per BTS ................................................................................ 9
6. A-TER INTERFACE...............................................................................................11
6.1
Introduction .............................................................................................11
6.2
Specific A-ter timeslots ...............................................................................12
6.3
Mixed A-ter CS/PS links ...............................................................................13
6.4
Sum up of A-ter timslots configuration.............................................................13
7. GB INTERFACE ..................................................................................................15
7.1
Gb Interface over Frame Relay ......................................................................15
7.2
Gb Interface over IP ...................................................................................16
8. BSC DIMENSIONNING RULES...................................................................................18

8.1
BSC equipment overview..............................................................................18
8.2
BSC A-bis connectivity.................................................................................19
8.3
BSC A-ter connectivity ................................................................................23
8.4
BSC Evolution: STM1 connectivity ...................................................................26
8.5
CS Traffic capacity.....................................................................................27
8.6
Signaling on A interface ...............................................................................29
8.7
A signaling over IP......................................................................................30
9. TRANSCODER DIMENSIONING RULES .........................................................................32

9.1
Connection to the G2 TC..............................................................................32
9.2
Connection to the 9125 TC ...........................................................................32
9.3
Minimum number of A/A-ter links ...................................................................33
9.4
Introduction of Wide Band AMR......................................................................33
10.
MFS DIMENSIONING RULES ............................................................................34
1AA 00014 0004 (9007)A4
10.1 Common rules for 9130 and 9135 MFS ..............................................................34

10.2 9135 MFS .................................................................................................34
10.3 9130 MFS Evolution ....................................................................................35
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
2/47
1AA 00014 0004 (9007)A4

10.4 Number of GSL channels ..............................................................................39

11.
ANNEX 1: BSS STANDARD TRAFFIC MODEL..........................................................40
11.1 BSS traffic model for CS traffic: .....................................................................40

11.2 SS7 LINK DIMENSIONNING .............................................................................41
11.3 BSS traffic model for PS traffic ......................................................................42
12.
ANNEX 2: A-BIS INTERFACE CONFIGURATION ......................................................44
12.1 Number of time-slots required with the different Signaling Multiplexing schemes.........44
12.2 Configurations with 2 A-bis links ....................................................................46
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
3/47
1AA 00014 0004 (9007)A4

1. REFERENCE DOCUMENTS
[1]
3DC 21006 0003 TQZZA
Use of Moderation Factor for BSS traffic assessment
[2]
3DC 21016 0003 TQZZA
9120 Base Station Controller Product Description
[3]
3DC 21016 0005 TQZZA
9135 MFS Product Description
[4]
3DC 21034 0001 TQZZA
G2 Transcoder Product Description
[5]
3DC 21016 0007 TQZZA
9125 Compact Transcoder Product Description
[6]
3DC 21150 0348 TQZZA
GSM/GPRS/EDGE Radio Network Design Process For AlcatelLucent BSS Release B11
[7]
3DC 21019 0007 TQZZA
9130 BSC/MFS Evolution Product Description
[8]
3DC 21144 0063 TQZZA
Packet transmission feature in release B9
[9]
3DC 21144 0120 TQZZA
Functional Feature Description: Gb over IP In Release B10
[10]
3DC 20003 0029 UZZA
Network Engineering guidelines for IP transport in the BSS
[11]
3DC 21144 0122 TQZZA
Functional Feature Description: STM-1 connectivity in the

BSS
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
4/47

2. INTRODUCTION
This document first provides the rules to dimension the interfaces in the BSS: Air, A-bis, A-ter and
Gb interface.
Then it provides dimensioning rules of the 9120 (G2) BSC, 9135 MFS and 9130 BSC/MFS Evolution
equipments with the BSS release B11
When not explicitly otherwise mentioned,
- BTS refers to 9100 BTS.
- BSC refers to both 9120 BSC and 9130 BSC Evolution.
- MFS refers to both 9135 MFS and 9130 MFS Evolution.
- Within the MFS:
- The GP board is the GPRS processing board in the 9130 MFS Evolution.
- The GPU board is the GPRS processing board in the 9135 MFS.
The reader must have some knowledge of the BSS architecture to understand this document; more
details about Alcatel Lucent BSS can be found in documents ref [2], [3], [4], [5], [6], and [7].
3. DEFINITIONS
A 64 kbit/s channel on the A-bis interface is called an A-bis timeslot.
A 16 kbit/s channel on the A-bis interface is called an A-bis nibble.
A 16 kbit/s transmission channel established for carrying (E)GPRS traffic is called a GCH (GPRS
channel). One GCH uses one A-bis and one A-ter nibble.
1AA 00014 0004 (9007)A4
In this document, EDGE may be used instead of E-GPRS, for wording simplification purpose.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
5/47

4. AIR INTERFACE
General / CS traffic:
-
Maximum number of TRX per BTS: 24.
Maximum number of TRX per cell: 16.
There are one or two CCCH timeslots devoted to CCCH per cell.
When BCCH is combined, a second CCCH cannot be configured.
With one CCCH, up to 11 SDCCH timeslots can be configured per cell (88 SDCCHs). These
SDCCH timeslot can be static or dynamic.
With 2 CCCH, up to 22 SDCCH time slots can be configured (176 SDCCH).
At least one static SDCCH (SDCCH/4 or SDCCH/8) must be positioned on the BCCH TRX for
recovery purpose.
The maximum number of SDCCH timeslots per TRX is 3 (24 SDCCH).
The maximum number of signaling time slots (BCCH, 2nd CCCH, SDCCH) per TRX is 4,
except on G3 TRX (non Edge) on which it is 3.
In a multiband cell, all SDCCH are in the primary band of the cell.
In a concentric cell, all SDCCH are in the outer zone.
All TRX can be declared as Full rate or Dual Rate TRX. Mixture of DR TRX and FR TRX are
supported.
Packet traffic:
Max number of TRX supporting GPRS per cell
16
Max PDCH per TRX
Max MS in DL packet transfer mode per PDCH
10
Max MS in UL packet transfer mode per PDCH
Max MS in packet transfer mode per PDCH
16
Max TS allocated to a MS in packet transfer mode
61
- In a multiband cell, the whole packet traffic is in the primary band of the cell.
- In a concentric cell, the whole packet traffic is in the outer zone.
1AA 00014 0004 (9007)A4
- In case of cell split over two BTS, the packet traffic of a cell is supported by only one BTS.
1 The support of multi-slot class 30-33 feature in B10 has allowed to increase this figure from 5 (B9) to 6
(B10).
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
6/47

5. A-BIS INTERFACE
5.1 Number of time-slots available per A-bis Multidrop link
This number depends on:
- The type of the multidrop link: Closed Loop or Open Chain,
- Whether time-slot zero (TS0) transparency2 is used or not,
The table below indicates the number of time-slots available per PCM link according to the
possible choices:
OPEN CHAIN MULTIDROP
CLOSED LOOP MULTIDROP
31 (**)
29
31
30
WITH TS0 TRANSPARENCY

TS0 USAGE (*)
Number of Time Slots available per A-bis link

(*): TS0 usage is not possible with BSC Evolution.
(**) (Recall for history, Improvement with 9100 BTS, compared to G2 BTS): In case all BTSs of a
Multidrop are 9100 BTSs, and if TS0 transparency is used, then the time-slot used for transmission
supervision can be saved (because the OML of 9100 BTS supports also the transmission supervision
information)
5.2 Usage of A-bis timeslots

On the A-bis interface, there are basic timeslots, extra timeslots, and timeslots devoted to
signaling.
One timeslot on the air interface is mapped on one basic 16kbit/s nibble on the A-bis interface. As
a consequence, each TRX corresponds to two A-bis basic timeslots.
Additional extra timeslots can be configured for the transport of packet. This makes sense when
CS3/CS4 or EDGE has been activated. If the cell transports voice and GPRS up to CS-2 only, no
extra timeslots are needed.
The number of extra timeslots per BTS is determined by the operator. The granularity is one A-bis
1AA 00014 0004 (9007)A4
timeslot. There is a maximum of:
2 Time slot 0 transparency means the BSS cannot use TS0, which is reserved by the transmission equipment for
O&M purpose. Time Slot 0 Usage means the BSS can use TS0.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
7/47
- 717 extra timeslots with 9120 G2 BSC

- 2000 extra timeslots with 9130 BSC
5.3 Transport of Signalling on the A-bis interface

5.3.1 General
There are two types of information to be conveyed:
- RSL: Radio Signaling Link. There is one RSL per TRX
- OML: O&M link. There is one OML per BTS. The OML link is always on the first A-bis link.
When signaling multiplexing is not used, signaling links are transported in independent 64 kbit/s Abis timeslots.
This configuration is not recommended, as it is wasting bandwidth on the A-bis interface and HDLC
resources. The following section presents the various signaling multiplexing mode offered by the
Alcatel-Lucent BSS.
5.3.2 A-bis signaling multiplexing modes
Signaling multiplexing is specified by the Operator per BTS sector.
There are three types of Signaling Multiplexing:
- Static Signaling Multiplexing consists of multiplexing on one A-bis timeslot up to 4 RSLs.
Corresponding to TRX belonging to the same BTS. Each RSL is statically allocated a 16 kbits/s
bandwidth. The OML uses an additional A-bis timeslot. One HDLC is used per A-bis timeslot
carrying signaling.
Maximum one SDCCH should be configured per TRX. DR cannot be supported.
- Statistical Signaling Multiplexing 16k: the basic nibble corresponding to the radio timeslot 0 of
each TRX carries the RSL of this TRX and possibly the OML of the BTS. This feature requires that
the TS0 of each TRX of the BTS does not carry user traffic but signaling (BCCH or SDCCH) only. One
HDLC is used per TRX.
Maximum one SDCCH should be configured per TRX. DR cannot be supported.
1AA 00014 0004 (9007)A4
This multiplexing scheme is adapted to small BTS.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
8/47
- Statistical Signaling Multiplexing 64k consists of multiplexing on one A-bis time-slot 1, 2 or 4

RSLs3 of a same BTS plus its OML. The whole A-bis timeslot bandwidth is shared by all channels.
One HDLC is used per A-bis timeslot carrying signaling.
DR is supported.
The number of SDCCH channels per cell should not exceed 8 * NB_TRX + 8 NB_DR_TRX.
It is not possible to mix the RSL of Full-Rate TRX and Dual-Rate TRX in the same 64 kbit/s timeslot.
The multiplexing ratio depends on the configuration of the TRX (Dual Rate or Full Rate), and on
the signaling load parameter (normal or high) specified by the Operator, as illustrated in the table
below. The signaling load is specified per BTS sector.
Full Rate TRX
Dual rate TRX
Normal
High signaling
Normal
High signaling
signaling load
load
signaling load
load
4:1
2:1
2:1
1:1
Multiplexing ratio for Statistical Signaling Multiplexing 64k

-
Note: In most cases normal signaling should apply. High signaling load should correspond to
exceptional cases (very high paging load and very high location update or SMS rates.)
5.4 Two A-bis-links per BTS

A secondary A-bis link can be used for following purposes:
- To configure more extra A-bis timeslots.
- In case of more than 12 TRX in a BTS, taking benefit of TWIN TRX introduction. For this
purpose, it is possible to configure a secondary A-bis link with basic A-bis nibbles.
The OML of a BTS is always mapped on the first A-bis link.
The TCH and the RSL of a TRX are grouped on the same A-bis link, whether RSL multiplexing is
1AA 00014 0004 (9007)A4
used or not4.
3 3 RSL in one time slot is not possible. In this case 2 A-bis Time Slots are used.
4 So in case of multiplexing it implies that TCH of TRX of which RSL are multiplexed together are also on the
same A-bis.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
9/47
All A-bis signaling modes are supported. With Statistical signaling multiplexing 64 kbit/s, the
1AA 00014 0004 (9007)A4

multiplexing mode per sector is not supported, i.e. the multiplexing mode is valid for the whole
BTS.
See Annex 2 for more details.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
10/47

6. A-TER INTERFACE
6.1 Introduction
The A-ter interface is both the interface between the BSC and the TC for CS traffic, and between
the BSC and the MFS for PS traffic.
When an A-ter link transports CS traffic, it is called an A-ter CS link.
When it transports PS traffic, it is called an A-ter PS link.
An A-ter CS link can also carry PS traffic. It is then called a mixed A-ter CS/PS link.
On the A-ter CS interface, a 64 kbit/s timeslot transmits information for 4 CS calls, whatever they
use FR or HR codecs.
On the A-ter PS interface, a 64 kbit/s timeslot supports 4 GCHs. For an A-ter link fully dedicated
to PS, there are up to 30 64 kbit/s channels, among which one can be used for GSL.
For a mixed A-ter CS/PS link:
The MFS transparently routes the 64 kbit/s timeslots used for voice towards the transcoder.
The MFS has the possibility to split the traffic on a link towards the transcoder for CS
traffic and a link towards the SGSN for PS traffic (Gb).
It is also possible to route both CS and packet traffic towards the transcoder. The same TS
sharing between CS and PS is used on the BSC/MFS and MFS/ TC links.
A dedicated A-ter-PS link cannot be routed through the Transcoder.

For the sake of redundancy, the minimum number of A-ter links connected to a BSS is 2.
When there is enough PS traffic to fill 2 or more A-ter links, there is an advantage to dedicate
complete A-ter E1 to PS rather than mixing PS with CS traffic. Indeed, doing so avoids connecting
the MFS to the transcoder with A-ter E1 not fully devoted to circuit-switched traffic, and thus
avoids wasting transcoder resource.
It is possible to configure PS timeslots on all A-ter E1: typical application case is configurations
with only 2 A-ter E1 in order to ensure A-ter PS traffic resilience.
However it is recommended not to carry PS traffic on the first A-ter link so that it can be
connected directly to the transcoder, in order to enable MFS installation without O&M interruption
1AA 00014 0004 (9007)A4
on the BSC.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
11/47

6.2 Specific A-ter timeslots

Some A-ter timeslots are not usable for user traffic. Some others are or are not usable for user
traffic, depending on HW generation.
Unless explicitly otherwise mentioned, whether such a timeslot is usable or not for traffic is valid
for both CS and PS traffic.
- TS 0 of each link: Not usable for traffic.
- Transmission alarm octets:
- TC G2: Timeslot 15 of each A-ter link is used to convey transmission alarm bits (submultiplexing of TS0 alarms).
- MT120, MT120-xB5 boards: this timeslot is not used anymore for that purpose. From B10
MR2 onwards, this timeslot becomes usable for CS traffic. Starting with B11 MR2 this TS can
be used to carry PS traffic. These improvements are valid only for BSC Evolution.
- SS7:
- Timeslot 16 can be used for that purpose.
- Timeslots 16 not used as such were not usable for user traffic.
TS16 from B10 MR2 onwards is used for CS traffic, with B11 MR2 may be used to carry PS
traffic in case of MT120-xB TC board with 9130 BSC Evolution. This is particularly interesting
in case of HSL or A signaling over IP.
- Transport of O&M information between BSC and OMC-R

- 9120 BSC: When this connection is performed through the A-ter Interface (not using an
external X25 network), the O&M links is conveyed in the timeslot 31 of the A-ter links N1 &
2. Timeslots 31 not used for O&M can be used for CS or PS traffic.
- 9130 BSC: When this connection is performed through the A-ter Interface (IP over A-ter and
not IP over Ethernet), the O&M links is conveyed in the timeslot 31 of the A-ter 1 to N. N is
between 2 and 16, with a default value of 4 and is configurable by the Operator: the IP
bandwidth can then be configured between 128 Kbits and 1 Mbit/s with a default value of 256
1AA 00014 0004 (9007)A4
Kbit/s. Timeslots 31 not used for O&M can be used for CS or PS traffic.
5 MT120-xB stands for MT120-NB or MT120-WB boards
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
12/47

- Qmux protocol (Transmission equipment supervision).

- 9120 BSC: One 16 kbits/s sub-channel in timeslot 14 of links N 1, 2, 7, 8, 13, 14 (two
Qmux channels per cluster of 6 A-ter link) is dedicated to the Qmux protocol. The three
other sub channels are used for CS or PS traffic.
- 9130 BSC: One 16 kbits/s sub-channel in timeslot 14 of links N 1, 2, 7, 8, 13, 14, 19, 20,
25, 26, 61, 62, 67, 68, 73, 74 (two Qmux channels per cluster of 6 A-ter link) is dedicated to
the Qmux protocol. The three other sub channels are used for CS or PS traffic.
- GSL:
- On A-ter-PS, one GSL may be configured on timeslot 28 to convey packet signaling between
the BSC and the MFS. When not configured, timeslot 28 can be used for CS or PS traffic.
6.3 Mixed A-ter CS/PS links

The percentage of A-ter timeslots assigned to PS traffic is configured by the Operator at OMC-R.
6.4 Sum up of A-ter timslots configuration

The following table summarizes the place of the special timeslots usable or not usable for CS/PS
traffic and the sharing of timeslots between CS and PS in case of mixed A-ter links. In pure A-ter
CS links, the A-ter timeslots shown below as carrying PS traffic (GCH) can be used to carry CS
traffic.
Each column corresponds to a different proportion of A-ter timeslots devoted to A-ter PS in mixed
1AA 00014 0004 (9007)A4
A-ter links.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
13/47

0
1
TCH
TCH
TCH
TCH
GCH
TCH
TCH
TCH
TCH
GCH
TCH
TCH
TCH
TCH
GCH
TCH
TCH
TCH
TCH
GCH
TCH
TCH
TCH
TCH
GCH
TCH
TCH
TCH
TCH
GCH
TCH
TCH
TCH
TCH
GCH
TCH
TCH
TCH
GCH
GCH
TCH
TCH
TCH
GCH
GCH
10
TCH
TCH
TCH
GCH
GCH
11
TCH
TCH
TCH
GCH
GCH
12
TCH
TCH
TCH
GCH
GCH
13
TCH
TCH
TCH
GCH
GCH
14
15
TCH/Qmux
alarm Oct.
/ TCH
TCH/Qmux
alarm Oct.
/ TCH
TCH/Qmux
alarm Oct.
/ TCH
GCH/Qmux
alarm Oct.
/ GCH
GCH/Qmux
alarm Oct.
/ GCH
16
SS7 / TCH
SS7 / TCH
SS7/ GCH
SS7 / GCH
SS7 / GCH
17
TCH
TCH
GCH
GCH
GCH
18
TCH
TCH
GCH
GCH
GCH
19
TCH
TCH
GCH
GCH
GCH
20
TCH
TCH
GCH
GCH
GCH
21
TCH
TCH
GCH
GCH
GCH
22
TCH
TCH
GCH
GCH
GCH
23
TCH
TCH
GCH
GCH
GCH
24
TCH
GCH
GCH
GCH
GCH
25
TCH
GCH
GCH
GCH
GCH
26
TCH
GCH
GCH
GCH
GCH
27
TCH
GCH
GCH
GCH
GCH
28
GCH/GSL
GCH/GSL
GCH/GSL
GCH/GSL
GCH/GSL
29
GCH
GCH
GCH
GCH
GCH
30
GCH
GCH
GCH
GCH
GCH
31
GCH/O&M
GCH/O&M
GCH/O&M
GCH/O&M
GCH/O&M
1AA 00014 0004 (9007)A4
A-ter CS/PS configuration
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
14/47

7. GB INTERFACE
7.1 Gb Interface over Frame Relay
There are 2 ways to connect the MFS and the SGSN via the Gb interface:
- Through the Transcoder and the MSC.
- Bypassing the Transcoder and going either directly to the SGSN (through the MSC or not).
This is the recommended solution when the traffic is sufficient to justify A-ter E1s
completely devoted to GPRS traffic. However, depending on the hardware and software
versions, this is not always possible, because of the GPU synchronization issues6.
The links between the MFS and the SGSN or between the MSC and the SGSN can be direct point-topoint physical connections or an intermediate Frame Relay Network can be used.
The figure below displays the different types of links between the MFS and the SGSN.
A bis
A ter
A ter
BTS
BSC
TC
MSC
BTS
FRDN
Frame
Relay
Data
Network
BTS
MFS
SGSN
1AA 00014 0004 (9007)A4
Remarks: The links going through the MSC can benefit from the multiplexing capability of the MSC
6 For synchronisation issues, please refer to the 9135 MFS product description [3] or 9130 BSC/MFS Evolution
Product description [7].
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
15/47

in order to reduce the number of ports required to the frame relay network towards the SGSN.
The maximum number of Frame Relay bearer channels is 124 per GPU board (theoretical value). It
is however interesting to reduce the number of bearer channels to one per E1 and at least 2 on 2
different E1 (for redundancy reason), in order to take benefit from the statistical effect of using
larger bearer channels.
- The maximum number of NS-VC is 124 per BSS
- The maximum number of BVC is 265 per BSS for the 9135 MFS
- The maximum number of BVC is 501 per BSS for the 9130 MFS
With Gb over frame relay, the traffic is aggregated at GP(U) board level. The peak throughput of
the Gb interface per GP or GPU is equal to the peak LLC throughput multiplied by an overhead
factor, which takes into account the Gb interface overheads. This overhead factor depends on the
mean frame size. The Gb peak throughput allows determining the required number of E1 links for
Gb/frame relay. In case where the Gb links are not fully used, the operator may introduced submultiplexing of Gb links between the MFS and the SGSN with an external equipment. Gb over
Frame Relay supports static configuration.
For more information on the method to determine the Gb peak throughput according to the traffic
mix expected within the BSC area and the Gb interface overheads, please refer to [6].
7.2 Gb Interface over IP

With Gb over IP, Gb traffic is transmitted over UDP/IP/Ethernet.
Ater(circuit)
E1
PDH/SDH network
TC
Ater(packet)
BSC
MSC
GE
MFS
GE
Gb
Full redundant architecture,
1AA 00014 0004 (9007)A4
Seen as single gateway IP@
SGSN
Packet Switched Network
GboIP: End-to-End architecture
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
16/47
Note: the previous figure illustrates Gb over IP for a TDM BSS. It is for sure possible to have Gb
over IP together with IP transport in the BSS.

This feature is available from B10, on:
- The 9130 MFS Evolution
- The 9135 MFS DS10, provided that it is equipped with a compatible Gigabit Ethernet Switch.
The Gb transport type has to be chosen on a per BSC basis: all the GP(U)s connected to a same BSC
shall use Gb over Frame Relay or Gb over IP, but mixing is not allowed. On the other hand, the Gb
transport type can be different among the BSCs connected to a same MFS.
With Gb over Frame Relay, dimensioning is done per BSS with an E1 granularity. With Gb over IP,
the traffic flows from/to all GP(U)s between MFS and SGSN is aggregated into one single flow over
Ethernet: Gb dimensioning is done considering the LLC traffic of a whole MFS traffic plus
BSSGP/NS/UDP/IP/Ethernet overheads.
Traffic load sharing is possible: for this purpose, each GP(U) board can address up to 16 IP
endpoints of the SGSN.
Gb over IP supports static and dynamic configuration.
The BSC has the capability to retrieve synchronization from the A-ter CS TDM links, and is then
able to synchronize the MFS through the A-ter PS TDM links.
On the other hand, the 9120 BSC has not this capability. Therefore a TDM link between the TC and
the MFS must be kept to synchronize the MFS.
1AA 00014 0004 (9007)A4
For more information on Gb over IP and its dimensioning, refer to [6], and [10].
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
17/47

8. BSC DIMENSIONNING RULES

8.1 BSC equipment overview
8.1.1 9120 G2 BSC configurations
The G2 BSC range available with the BSS Software Release B11 is:
Configuration
number
1
2
3
4
5
6
BSC G2 EQUIPMENT
32 TRX-FR;
128 TRX-FR;
192 TRX-FR;
288 TRX-FR;
352 TRX-FR;
448 TRX-FR;
16A,
24A,
40A,
48A,
64A,
72A,
Number of
cabinets
1
1
2
2
3
3
6 A-bis-ITF
24 A-bis ITF
36 A-bis ITF
54 A-bis ITF
66 A-bis ITF
84 A-bis ITF
G2 BSC configurations
For more details on G2 BSC HW, please refer to the BSC product description [2].
8.1.2 9130 BSC Evolution configurations
Two main types of configuration are available, in one cabinet:
- Standard configurations: BSC Evolution with one telecom sub-rack
- Rack Sharing configurations: two BSC Evolution, with one telecom sub-rack per BSC.
For more details on BSC Evolution hardware, please refer to document ref [7]
1AA 00014 0004 (9007)A4
Configuration
Ed
MRD
Number of
equipped
telecom subracks
Number of CCP
boards (*)
Number of LIU
boards
BSC-EV-200
BSC-EV-400
BSC-EV-600
16
BSC-EV-800
16
BSC-EV-1000
16
BSC-EV-RS 400-400 (**)
16
BSC-EV-RS 600-200(**)
24
BSC-EV-RS 600-400 (**)
24
BSC-EV-RS 600-600
32
BSC-EV-RS 800-200
24
BSC-EV-RS 800-400
24
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
18/47

Configuration
Number of
equipped
telecom subracks
Number of CCP
boards (*)
Number of LIU
boards
BSC-EV-RS 800-600
32
BSC-EV-RS 800-800
10
32
BSC-EV-RS 1000-200
24
BSC-EV-RS 1000-400
24
BSC-EV-RS 1000-600
10
32
BSC-EV-RS 1000-800
11
32
BSC-EV-RS 1000-1000
12
32
BSC Evolution configurations

(*) Each CCP handles 200 TRX The figure here include spare CCP boards.
(**) These configurations are kept for historical reasons: indeed with B9, it was not
possible to have more than 600 TRX per logical BSC.
8.2 BSC A-bis connectivity

There is a set of rules to determine the maximum amount of TRX and BTSs that can be connected
to a BSC.
8.2.1 Mix of Full Rate and Dual Rate TRX
The Half-Rate Flexibility feature allows defining the number of Dual Rate TRX in each BTS sector
(cell). This feature is available from B6 onwards.
The optimized half-rate connectivity feature allows declaring all TRX of a cell, as dual-rate
capable with no loss of capacity in the BSC. This feature is available from B10 onwards, only with
BSC Evolution.
8.2.2 9120 G2 BSC
The A-bis connectivity is provided by a number of A-bis TSU.
Each A-bis TSU includes 8 TCUs (Terminal Control Unit) and six G.703 A-bis interfaces, which allow
connecting six A-bis PCM trunks.
The table below indicates the number of A-bis TSU and the TRX capacity for each G2 BSC
1AA 00014 0004 (9007)A4
configuration.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
19/47

BSC G2 EQUIPMENT
Nb. Of A-bis TSU
Configuration 1
Configuration 2
Configuration 3
Configuration 4
Configuration 5
Configuration 6
1
4
6
9
11
14
Max. nb. of FR-TRX Max. nb. of DR-TRX

32
128
192
288
352
448
14
62
92
140
170
218
TRX connectivity for G2 BSC

Note: At least one TCU in each BSC rack must be allocated in Full Rate. This is why the maximum
number of DR TRX is inferior to half of the maximum number of FR TRX.
When the maximum number of DR TRX is reached, there are still up to 4 potential FR TRX for
configurations (1) & (2), 8 FR TRX for configurations (3) & (4), and 12 FR TRX for configurations (5)
& (6).
It is not possible to mix FR TRX and DR TRX in a single TCU.
The maximum number of BTS and cells depends whether all TRX are configured in Full Rate or in
Dual Rate mode. It is detailed in the table below.
All TRX Full Rate
All TRX Dual Rate
BSC G2 EQUIPMENT
max. BTSs
max. Cells
max. BTSs
max. Cells
Configuration 1
Configuration 2
Configuration 3
Configuration 4
Configuration 5
Configuration 6
23
95
142
214
255
255
32
120
192
240
264
264
14
62
92
140
170
218
14
62
92
140
170
218
BTS and cell connectivity for G2 BSC

The following rules, relative to the A-bis TSU, must be respected:
- All TRX of all BTSs of a same A-bis multidrop are handled by a single A-bis TSU.
- Each TCU can handle 6 signaling links (LAPD), i.e. typically: (4 RSLs + 2 OMLs for 4 TRX+ 2
BTSs ) or (3 RSLs + 3 OMLs for 3 TRX+ 3 BTSs).
1AA 00014 0004 (9007)A4
- Each TCU can handle either Full Rate or Dual Rate traffic (but not both).
- Each TCU can handle 32 Traffic Channels, i.e. 4 Full-Rate TRX or 2 Half-Rate TRX.
- The traffic channels and the RSL of a given TRX are handled by the same TCU.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
20/47
- In case of Signaling Multiplexing, all RSLs of a given 64 kbit/s A-bis time-slot are handled by
the same TCU (this rule applies for both Static and Statistical Signaling Multiplexing)
- 6 A-bis open chain multidrop links can be connected to one A-bis TSU. In case of closed loop
multidrop links, both ends of an A-bis multidrop loop must be connected to the same A-bisTSU. Hence up to 3 A-bis closed loop multidrop links can be connected to 1 A-bis-TSU.
- In each cabinet, there is at least one TCU configured in Full Rate.
Remarks:
- It is possible to mix within a same TCU, RSL, which are multiplexed (static and/or
statistical) and RSL, which are not multiplexed.
Recommendations:
- It is recommended not to dimension a BSC over 90% of its maximum connectivity. Indeed,
leaving free some spare capacity in all A-bis TSUs will simplify further extensions.
8.2.3 9130 BSC Evolution
The following table provides the main information on the BSC Evolution A-bis connectivity:
1AA 00014 0004 (9007)A4
Configuration
TRX (*)
Cell
BTS
A-bis links
BSC-EV-200
200
200
150
96
BSC-EV-400
400
400
255
96
BSC-EV-600
600
500
255
176
BSC-EV-800
800
500
255
176
BSC-EV-1000
1000
500
255
176
BSC-EV-RS 400-400
800
800
510
192
BSC-EV-RS 600-200
800
700
405
272
BSC-EV-RS 600-400
1000
900
510
272
BSC-EV-RS 600-600
1200
1000
510
352
BSC-EV-RS 800-200
1000
700
405
272
BSC-EV-RS 800-400
1200
900
510
272
BSC-EV-RS 800-600
1400
1000
510
352
BSC-EV-RS 800-800
1600
1000
510
352
BSC-EV-RS 1000-200
1200
700
405
272
BSC-EV-RS 1000-400
1400
900
510
272
BSC-EV-RS 1000-600
1600
1000
510
352
BSC-EV-RS 1000-800
1800
1000
510
352
BSC-EV-RS 1000-1000
2000
1000
510
352
A-bis connectivity for BSC Evolution
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
21/47
(*): Thanks to the Optimised Half-Rate Connectivity feature, the BSC Evolution can handle 200
TRX per CCP board, whatever those TRX are FR or HR. However CCPs remain limited to 900 Erlang.
A maximum number of calls simultaneously established per CCP board is defined, so as to allow
reaching 900 Erlang, while not increasing the external blocking.
The Optimised Half-Rate Connectivity feature is optional. When it is not used, the maximum
number of DR TRX is equal to the maximum number of FR TRX divided by 2.
8.2.4 Particular case of cell splitting
This feature enables to share a cell between 2 BTSs. This allows for example to extend a site,
adding a new BTS without modifying the arrangement of the already existing BTS(s).
Remarks concerning the G2 BSC:
- The BTSs can be connected to the same or to different A-bis TSUs.
- However, in Multi-band Cells all radio signaling is concentrated on the primary band. In this
case, it is recommended to mix the 900 MHz BTSs and the 1800 MHz BTSs in each A-bis TSU,
so as to enable a better signaling load distribution at TCU level.
8.2.5 Introduction of CS-3, CS-4 and EDGE
8.2.5.1 Case of the 9120 G2 BSC
Introduction of CS-3, CS-4 and EDGE has impacts on A-bis dimensioning and on the BSC TRX
connectivity.
Extra-timeslots defined on the A-bis links are cross-connected inside the BSC and consume some
BSC connectivity.
Two A-bis extra timeslots are equivalent to one Full Rate TRX in terms of connectivity in the BSC.
In other words, configuring two extra timeslot is equivalent to reducing the number of connectable
FR TRX by one.
Note : the system maps extra-timeslots on any FR TCU of the A-bis TSU to which the A-bis link is
connected.
1AA 00014 0004 (9007)A4
8.2.5.2
Case of the 9130 BSC Evolution
The introduction of CS3, CS4 and EDGE has no impact on the BSC TRX connectivity.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
22/47

8.2.6 A-bis Signaling capacity

In the 9130 BSC Evolution, there are up to 1024 HDLC channels7 at 64 kbit/s per BSC. Among
them:
- 24 are reserved for GSL usage,
- 16 for O&M transport over A-ter interface,
- 984 are available for RSL and OML.
The number of RSL (plus possibly one OML) carried per HDLC channel depends on the use of
signaling multiplexing as explained in section 5.3.
If signaling multiplexing is not used on A-bis interface, the maximum number of TRX and BTS
indicated in sections 8.2.2 cannot be reached8. It is recommends to use statistical signaling
multiplexing on 64 kbit/s A-bis TS, so as to save A-bis time slots.
For 9120 G2 BSC, the number of HDLC channel is not a limiting factor (6 HDLC channels per TCU)
whatever the multiplexing scheme.
8.3 BSC A-ter connectivity

8.3.1 9120 G2-BSC
The maximum number of A-ter interfaces (E1 links) is given in the table below. This maximum
number of A-ter interfaces is the total available for CS and PS services. Each A-ter link can be
either fully dedicated to PS or CS, or it is also possible to split some A-ter links between CS and PS.
The detailed information on how to split an A-ter-link between CS & PS is detailed in section 6.
1AA 00014 0004 (9007)A4
7 For BSC Evolution installed prior to B10-MR2, a hardware upgrade is needed to reach 1024 HDLC channels.
The new TP-STM1 board must replace the previous TP board. The previous board has a capacity of 512 HDLC
channels, among which 441 are available for A-bis signaling (RSL+OML). With such boards, the number of DR
TRX is limited to 882 (2 DR RSL per signalling timeslot)
8 Without signalling multiplexing, the following rule applies: Number of TRX (RSL) + number of BTS (OML) < 984
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
23/47

BSC G2 configurations
Max. Nb. of A-ter itf
Configuration 1
Configuration 2
Configuration 3
Configuration 4
Configuration 5
Configuration 6
4
6
10
12
16
18
A-ter connectivity for G2 BSC

There is one A-ter CS pool and one A-ter PS pool per BSC
- A-ter links belonging to the A-ter PS pool are dedicated to PS traffic: Only A-ter PS links can
be configured.
- A-ter links belonging to the A-ter CS pool can be used to carry CS traffic only or CS and PS
traffic (Mixed A-ter links): Pure A-ter-CS and mixed A-ter-CS/PS links can be configured.
From B11 onwards, pure A-ter PS links can be also configured.
The maximum number of A-ter interfaces inside each pool is given in the table below:
1AA 00014 0004 (9007)A4
Configuration
A-ter CS pool
A-ter PS pool
BSC-EV-200
10
BSC-EV-400
20
12
BSC-EV-600
30
18
BSC-EV-800
38
26
BSC-EV-1000
46
30
BSC-EV-RS 400-400
40
24
BSC-EV-RS 600-200
40
24
BSC-EV-RS 600-400
50
30
BSC-EV-RS 600-600
60
36
BSC-EV-RS 800-200
48
32
BSC-EV-RS 800-400
58
38
BSC-EV-RS 800-600
68
44
BSC-EV-RS 800-800
76
52
BSC-EV-RS 1000-200
56
36
BSC-EV-RS 1000-400
66
42
BSC-EV-RS 1000-600
76
48
BSC-EV-RS 1000-800
84
56
BSC-EV-RS 1000-1000
92
60
A-ter connectivity for BSC Evolution
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
24/47
In the case of SS7 carried on 2 Mbit/s link (HSL) two A-ter links must be reserved for this. Both HSL
1AA 00014 0004 (9007)A4

should be connected to distinct LIU boards to ensure redundancy even in case of LIU failure.
HSL links are directly connected to the MSC, which saves TC resources.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
25/47

8.4 BSC Evolution: STM1 connectivity

STM1 connectivity is introduced in B11 release for the 9130 BSC Evolution. It is available on both
A-bis and A-ter interfaces.
The only HW pre-requisit is that the BSC is equipped with TPSTM1 or TPSTM1-IP boards.
BSC
STM-1
Gb over FR
or
Gb over IP
ADM
MFS
E1
E1
ADM
SDH Ring
ADM
STM-1
STM-1
E1
SGSN
MSC
ADM
STM-1
TC
BSC
STM1 in the BSC

Each E1 link is transported transparently in one 2 Mbit/s VC12 container. One STM-1 link can
contain up to 63 VC12 containers.
Up to 4 STM-1 links can be connected (Optical interfaces, in mono-mode/short-haul type9),
allowing for 100 % STM-1 connectivity, but mix of E1 and STM-1 connections is possible on A-Bis
and A-ter.
In case of a mixed configuration, the Operator can choose which A-bis or A-ter links should be
transported over STM-1, and which of the links should be transported over E1 links.
On any STM1 link can be mapped A-bis, A-ter, or a mix of A-bis and A-ter E1s.
1AA 00014 0004 (9007)A4
For more details please refer to [2] and [11].
9 Pluggable O/E converters, called SFP (Small Form Factor Pluggable), are used and enable other STM-1 types.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
26/47

8.5 CS Traffic capacity

The maximum CS traffic capacity is limited by the number of A-ter interface channels available for
traffic.
The BSC is also limited by its processing power available for signaling handling. This is reflected by
the maximum Busy Hour Call Attempts (BHCA), which depends on the traffic model.
The most constraining limit has to be taken into account. Then the other limit is calculated
according to the formula:
Erlang traffic load = (Busy hour call attempts * Mean call duration) /3600
8.5.1 9120 G2-BSC
These following figures are guaranteed with respect to the call mix specified in annex 1. The
Erlang figures are based on a 0.1%. blocking probability on the A-ter interface.
G2-BSC configuration
Configuration 1
Configuration 2
Configuration 3
Configuration 4
Configuration 5
Configuration 6
Maximum Traffic
(ERLANG)
160 Erlang
620 Erlang
1050 Erlang
1300 Erlang
1700 Erlang
1900 Erlang
Maximum BHCA
11 520
44 640
75 600
93 600
122 400
136 800
Erlang & BHCA for the 9120 G2 BSC

Note that a configuration 6 BSC can reach a 2000 ERLANG capacity with a less constraining traffic
model. Also in that case, the blocking rate will reach 0.24%, instead of 0.1%.
The figures below are guaranteed with respect to the call mix specified in annex 1. The Erlang
figures are based on a 0.1% blocking probability on the A-ter interface.
Maximum Traffic
(ERLANG)
Maximum BHCA
BSC-EV-200
900
64 800
BSC-EV-400
1800
129 600
1AA 00014 0004 (9007)A4
Configuration
Ed
MRD
03
BSC-EV-600
2700
194 400
BSC-EV-800
3600
259 200
BSC-EV-1000
4500
324 000
BSC-EV-RS 400-400
3600
259 200
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
27/47

BSC-EV-RS 600-200
3600
259 200
BSC-EV-RS 600-400
4500
324 000
BSC-EV-RS 600-600
5400
388 800
BSC-EV-RS 800-200
4500
324 000
BSC-EV-RS 800-400
5400
388 800
BSC-EV-RS 800-600
6300
453 600
BSC-EV-RS 800-800
7200
518 400
BSC-EV-RS 1000-200
5400
388 800
BSC-EV-RS 1000-400
6300
453 600
BSC-EV-RS 1000-600
7200
518 400
BSC-EV-RS 1000-800
8100
583 200
BSC-EV-RS 1000-1000
9000
648 000
Erlang & BHCA for the 9130 BSC Evolution

The capacity for rack-shared configuration is the sum of the capacity of each logical BSC.
8.5.3 The moderation factor
When dimensioning a network, one must check that the sum of the nominal traffic generated by
the different BTSs does not exceed the maximum traffic handling capacity of the BSC to which
they are connected.
However it has been noticed that the actual traffic encountered in a BSC is generally significantly
lower than this sum. This comes from the fact that the nominal traffic is not reached
simultaneously in each cell and that all TRX or all traffic channels are not all necessary to handle
the actual traffic.
To account for this and avoid over-estimating the number of BSC 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 encountered in the BSC at its busy hour and the theoretical
traffic figure. 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 be used. Significantly lower
values may even be used in many cases.
Using the Moderation Factor is also recommended for the assessment of the number of A-ter
1AA 00014 0004 (9007)A4
Interfaces and of transcoders.

More details on the Moderation Factor can be found in document [1].
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
28/47

8.6 Signaling on A interface

8.6.1 SS7 channels on 64 kbit/s time slots
The number of SS7 64 kbit/s channels required depends on the traffic mix.
There is a maximum of one SS7 64 kbit/s channel par A-ter link
There is a maximum of 16 SS7 signaling channels per BSC (so 32 for rack-shared configuration of
9130 BSC Evolution).
This limitation is a GSM limitation, and so cannot be extended.
SS7 links are traditionally dimensioned with 40% load (0,4 ERLANG per signaling channel), so
that in case of failure of one link, the switchover of one link onto another brings the total load of
the remaining links below 80%, thus preventing loss of capacity.
The Alcatel-Lucent BSC (9120 and 9130) always balances the load on all signaling links in the BSCto-MSC direction. So in case of switchover due to the loss of one signaling link, the load of the lost
link is evenly and immediately distributed on all remaining links. This strategy allows the BSC to
cope with SS7 signaling load up to 60% (0,6 ERLANG per signaling channel) as soon as there are a
minimum of four links configured. In the receive direction, the possibility to allow more than 0,4
ERLANG per link depends on the MSC strategy for load balancing in case of switchover. So
dimensioning SS7 links at 60% load is allowed with the Alcatel-Lucent BSS, if the MSC can also also
support it.
The SS7 load depends on the BHCA and other call mix parameters. A method for SS7 load
estimation on the A-interface, depending on capacity and call mix parameters, is provided in
Annex 1.
8.6.2 SS7 channel on 2Mbit/s links (HSL)
This option is available only with 9130 BSC Evolution. It becomes mandatory when 16 SS7
timeslots are not enough to convey the signaling traffic of the highest BSC configurations or in
case of very demanding traffic models.
See section 8.3.2 for configuration rules.
8.6.3 SS7 dimensioning for 9120 G2 BSC
1AA 00014 0004 (9007)A4
With the Alcatel-Lucent traffic model presented in Annex 1, it is recommended to configure one
SS7 link per A-ter link (with a maximum of 16 SS7 links). The SS7 load in this case is about 50%
With less constraining traffic models, it is possible:
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
29/47

Either to dimension the SS7 links at 40% load
Or to reduce the required number of SS7 links.
8.6.4 SS7 dimensioning for 9130 BSC-Evolution

The following table shows the number of links needed for SS7 dimensioning at 40% and 60% load,
with the Alcatel-Lucent traffic model. With less constraining parameters, the method showed in
Annex 1 can be followed to estimate exactly the number of links.
BSC configuration
BHCA
SS7 links @ SS7 links @

40%
60%
11
8
BSC-EV-200
64 800
BSC-EV-400
129 600
HSL
15
BSC-EV-600
194 400
HSL
HSL
BSC-EV-800
259 200
HSL
HSL
BSC-EV-1000
324 000
HSL
HSL
SS7 links for different BSC Evolution configurations and SS7 load
Notes: For rack-shared configuration, the number of links is the sum of the links required for each
BSC.
8.7 A signaling over IP

This alternative is available from B11 on the 9130 BSC Evolution.
Legacy transport of A interface signalling using SS7 principles is replaced by SIGTRAN protocols.
It is an alternative to HSL for high BSC configurations, for the Operator having already deployed a
NGN core network, which already use SIGTRAN protocols for internal purpose.
A Signalling over IP is mandatory when A Flex feature is used.
Transmission over TDM (E1 timeslots or full E1 in case of High Speed Link (HSL)) is replaced by
transmission over an IP network thanks to the Ethernet connectivity of the BSC Evolution.
Transport of A signalling over IP/MLPP/E1 on A-ter is not supported natively by the BSS. In case the
Operator wants to continue conveying A signalling over legacy E1 links, he can use an external
routing solution.
1AA 00014 0004 (9007)A4
When A Signalling over IP is used, the O&M link between the OMC-R and the BSC can only use the
Ethernet connectivity of the BSC. In case the Operator wants to continue using IP/MLPP/E1 on Ater, then like above, an external routing solution can be envisaged.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
30/47

The architecture of a BSS using A Signaling over IP is depicted in the figure below.
A Signaling over IP
The table below provides information on the A signaling over IP throughput at BSC Ethernet
connector, and depending on BSC configuration. For a given BSS SW release, they have to be
confirmed upon platform tests completion.
BSC configuration
BSC-EV-200
BSC-EV-400
BSC-EV-600
BSC-EV-800
BSC-EV-1000
UL
1,04
1,65
2,27
2,88
3,5
DL
0,93
1,5
2,06
2,62
3,18
A Signaling throughput (in Mbits/s)

Hypothesis:
- Alcatel-Lucent traffic model (by default the traffic model considered is very heavy, inducing
1AA 00014 0004 (9007)A4
high signalling load on A interface)

- Ethernet header
: 38 bytes
- IP header
: 20 bytes
- SCTP header
: 12 bytes
- M3UA header
: 36 bytes
- Chunk header
: 16 bytes
For more details refer to [6].
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
31/47

9. TRANSCODER DIMENSIONING RULES

9.1 Connection to the G2 TC
Each BSC rack must be connected to only one TC G2 rack. But one TC rack can be connected to
several BSC racks.
Please refer to the G2 TC product description [4] for more details.
9.2 Connection to the 9125 TC

9.2.1 Rules at BSC side
It is possible to connect up to 24 BSC on one 9125 TC.
It is also possible to connect one BSC to different TC racks.
9.2.2 Rules at 9125 TC side
E1 connectivity:
On A-ter interface, up to 48 E1 ports are available per TC rack (1 per MT120 board).
On A interface, up to 192 E1 ports are available per TC rack (4 per MT120 board).
STM-1 connectivity:
STM1 connectivity is available in the 9125 TC from B10 MR2 onwards. It is available for both A and
A-ter interfaces.
Each E1 link is transported transparently in one 2 Mbit/s VC12 container. One STM-1 link can
contain up to 63 VC12 containers.
Up to 4 STM-1 links can be connected (Optical interfaces, in mono-mode/short-haul type10),
allowing for 100 % STM-1 connectivity, but mix of E1 and STM-1 connections is possible on A and Ater.
In case of a mixed configuration, the Operator can choose which A or A-ter links should be
1AA 00014 0004 (9007)A4
transported over STM-1, and which of the links should be transported over E1 links.
10 Pluggable O/E converters, called SFP (Small Form Factor Pluggable), are used and enable other STM-1
types.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
32/47
The only rule is that the four A interfaces of a same MT120 board must all be of the same type. On
the other hand the A and A-ter interfaces of a same MLT120 board can be of different types.
Refer to the 9125 TC product description [5] for more details.
9.3 Minimum number of A/A-ter links

At least 2 A-ter links per BSC are required.
- If the O&M link to the OMC-R is not conveyed by the A-ter interface, each A-ter link needs to
be connected to a minimum of one A interface link (total two A links).
- If the O&M link to the OMC-R is conveyed by the A-ter interface, each A-ter link needs to be
connected to 2 A interface links (total four A links).
9.4 Introduction of Wide Band AMR

Only Codecs, which can be transported in 16Kbit/s time slots, are implemented. Hence there is no
impact on transmission dimensioning.
WB-AMR requires the MT120-WB TC board. This board can be plugged into already deployed G2
TC and 9125 TC. See ref [5] for details.
When the MSC supports TC pools, it is possible to mix MT120 and MT120-WB in the transcoder, for
1AA 00014 0004 (9007)A4
a smooth feature introduction according to AMR-WB MS penetration.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
33/47

10. MFS DIMENSIONING RULES

10.1 Common rules for 9130 and 9135 MFS
Each GP(U) board is connected to only one BSC.
But one BSC can be connected to up to 6 GP(U) board, depending on packet traffic. These GPU
boards can belong to different MFS subracks.
One MFS is connected to one single OMC-R. All the BSC connected to a given MFS must be
connected to the same OMC-R as the MFS.
One MFS can be connected to BSCs themselves connected to different MSC.
One MFS can be connected to several SGSN, but one GP(U) is connected to only one SGSN.
10.2 9135 MFS

10.2.1 9135 MFS configurations rules
The 9135 MFS (DS10) (*) can accommodate from 1 to 2 telecommunication sub-racks and house 32
GPU boards: 15 GPU boards plus 1 GPU board for redundancy per subrack.
The granularity is 1 GPU board.
One 9135 MFS can control up to 22 BSC.
One MFS can manage up to 2000 cells.
The maximum number of cells may be reached with only one sub-rack, but in this case it will not
be increased when adding a second sub-rack.
(*) MFS based AS800 is not supported from B11 onwards.
10.2.2 9135 MFS GPU capacity
One GPU board can support up to 16 external links
- up 8 A-ter links
- Up to 8 Gb links
1AA 00014 0004 (9007)A4
One GPU can be configured with a maximum 264 cells.

The maximum number of active PDCH is given below:
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
34/47

Max CS
CS1
CS2
CS3
CS4
Max PDCH
240
240
216
192
Maximum GPRS PDCH per GPU

Max EGPRS MCS
Max PDCH
MCS 1 MCS 2 MCS 3 MCS 4 MCS 5 MCS 6 MCS 7 MCS 8 MCS 9

220
208
204
192
176
164
132
112
104
Maximum EDGE PDCH per GPU

The above numbers corresponds to the number of PDCH, which can be simultaneously active in the
GPU, assuming all PDCH are using the same CS or MCS.
The GPU achievable throughput is highly dependant on the type of application. The achievable
throughput depending on the application and for a mix of traffic are provided below, on the basis
of the PS traffic model described in Annex 1.
Capacity
WEB
WAP
MMS
DL
Streaming
Mix of
traffic
DL throughput (kbit/s)
900
130
540
1 480
620
UL throughput (kbit/s)
50
20
340
130
Table 20: Achievable throughput per GPU for GPRS users
Capacity
WEB
WAP
MMS
DL
Streaming
Mix of
traffic
1 100
130
650
2 000
700
60
20
400
150
Achievable throughput per GPU for EDGE users
10.3 9130 MFS Evolution

10.3.1 9130 MFS configurations rules
The 9130 MFS Evolution can house up to 21 GP boards (plus 1 GP board for redundancy) in 1 to 2
1AA 00014 0004 (9007)A4
telecommunication sub-racks
Therefore one 9130 MFS can control up to 21 BSC.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
35/47

The 9130 MFS exist in several configurations, as illustrated by the next table
B10 MFS configurations
Stand-alone
small MFS
Number of ATCA shelves
Number of logical MFS (NE)
Maximum number of BSC
8/9
16/21
16
Maximum number of cells
4000
4000
8000
Number of LIU racks
Number of LIU boards for MFS
16
16
E1 connection available
128
256
256
Max GP (active)
8/9
16/21
16
See note 1
See note 1
16/12
16/12
GP standby
Max E1 per GP (LIU board
constraint)
Stand-alone Rack-shared
large MFS
MFS (double)
See notes 1 & 2 See notes 1 & 2
2
16
Note 2
MFS Evolution configurations

General notes:
- The rack-shared configurations were introduced in B9, as a workaround to the limit of 12 E1 per
GP for stand-alone configuration (limit removed from B10 MR2).
- In previous version of this document, the Stand-alone small with up to 8 GP / 16 E1 per GP was
known as Rack-shared (Single). As this denomination can be misleading (No real rack sharing as
there is only one MFS), the Rack-shared (Single) configuration is now presented as a variant of
the Stand-alone small MFS.
- The rack-shared double MFS configuration has a lower capacity in number of GP than a large
stand-alone MFS, but allows more flexibility for connecting each MFS to a distinct OMC-R
(Workaround to the rule that all BSC of a same MFS shall be connected to a same OMC-R)
Such configurations house two independent MFS. So each ATCA shelf contains both a duplicated
switch, OMCP and a redundant GP, contrary to the stand-alone large MFS.
1AA 00014 0004 (9007)A4
Note 1: Both maximum number of E1 and maximum number of GP for stand-alone MFS cannot be
reached simultaneously. The operator has to make the following choice at commissioning11:
11 The choice has to be done at commissioning so as to allow extension without service interruption due to re-
cabling and reloading of MFS configuration file.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
36/47

12 E1 with up to 9 GP for the first shelf and up to 21GP with two shelves.
16 E1 with up to 8 GP with one shelf and up to 16 GP with two shelves.
Note 2: Up to B10 MR1, In case of MFS in centralized clock mode, two 2 E1 ports are reserved for
clock distribution.
10.3.2 9130 MFS GP capacity
The number of available E1 connections per GP is determined according to the configuration as
shown in above table .
One GP board can support up to 16 external links:
-
up to 16 A-ter links
up to 8 Gb links
The maximum number of A-ter E1 is determined as follows:

- In case of Gb/Frame Relay, the E1 of one GP must be distributed between Gb and A-ter
interface. It is recommended to have at least two Gb links for safety reason, so there
remains a maximum of 10 or 14 E1 for A-ter interface depending on the MFS configuration.
- In case of Gb/IP, E1 are not used to carry the Gb data, so all the E1 links connected to one
GP can be used for A-ter purpose, so up to 12 or up to 16 A-ter E1 depending on MFS
configuration.
For determining the required number of Gb and A-ter E1 depending traffic, please refer to [6].
One GP can handle up to 500 cells.
The maximum number of PDCH, which can be simultaneously established, is determined per GP
board. The maximum number of PDCH is indicated both for the configuration with 16, 14 ,13, 12
or 10 A-ter links per GP. Each A-ter links carries up to 112 GCH (4 GCH per A-ter time slot, and
removing those reserved for GSL or other purposes as described in chapter 6.4.
Max CS
CS1
CS2
CS3
CS4
GP1
960
960
924
860
If up to 14 A-ter E1 per GP
960
960
924
860
960
960
924
860
960
960
924
816
960
960
896
680
1AA 00014 0004 (9007)A4
If up to 16 A-ter E1 per
1 With Gb/IP only
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
37/47

Maximum GPRS PDCH per GP

Max EGPRS MCS
MCS 1
MCS 2
MCS 3
MCS 4
MCS 5
MCS 6
MCS 7
MCS 8
MCS 9
If up to 16 A-ter
E1 per GP1
840
816
824
800
744
720
512
432
396
If up to 14 A-ter
E1 per GP
840
816
824
800
744
664
448
376
348
If up to 13 A-ter
E1 per GP
840
816
824
800
744
616
416
348
324
If up to 12 A-ter
E1 per GP
840
816
824
800
720
568
384
324
296
If up to 10 A-ter
E1 per GP
840
816
824
744
600
472
320
268
248
Maximum EDGE PDCH per GP

The above numbers corresponds to the number of PDCH, which can be simultaneously active in the
GP, assuming all PDCH are using the same CS or MCS.
The GP achievable throughput is highly dependant on the type of application. The achievable
throughput depending on the application and for a mix of traffic are provided below, on the basis
of the PS traffic model described in Annex 1.
Capacity
WEB
4 140
210
WAP
680
90
MMS
2 540
1 590
DL
streaming
6 480
15
Mix of
traffic
2 960
620
DL
streaming
8 050
15
Mix of
traffic
3 310
700
Achievable throughput per GP for GPRS users

Capacity
WEB
4 710
240
WAP
680
90
MMS
2 980
1 860
1AA 00014 0004 (9007)A4
Achievable throughput per GP for EDGE users
1 With Gb/IP only
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
38/47

10.3.3 General considerations on PS traffic model

In the Alcatel-Lucent traffic model, all packet users are considered active. In reality it is possible
to have a proportion of attached users, who are only generating signalling. Such users are taking
CPU resources, while using very little radio throughput. Hence the maximum number of PDCH or
throughput may not be reachable in such case.
For DL streaming, the achievable throughput corresponds to what is possible at board level with
maximum number of PDCH at very high CS/MCS. However in reality the bandwidth available on Gb
interface must be taken into account, as well as an expected distribution of CS/MCS. The GB/ Ater dimensioning must be adapted accordingly.
For more details on GP dimensioning depending on PS traffic, please refer to [6].
10.4 Number of GSL channels

The GSL (GPRS signaling links) transports the signaling between the BSC and the MFS for PS
services.
There can be 0 or 1 GSL per A-ter link.
Each GPU or GP board requires at least one GSL channel. For security reason, it is recommended
to have at least 2 GSL channels per GPU or GP board.
There can be up to
-
4 GSL per GPU board
8 GSL per GP board
24 GSL per BSC Evolution
18 GSL per G2 BSC (due to max 18 A-ter links)
The required number of GSL channels depends on the traffic. With the PS traffic model provided in
annex, 2 GSL links per GPU or GP board is sufficient, except for the case of A-ter-PS carried over
1AA 00014 0004 (9007)A4
satellite links, due to very long propagation delays. In this case specific dimensioning is required.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
39/47

11. ANNEX 1: BSS STANDARD TRAFFIC MODEL

11.1 BSS traffic model for CS traffic:
Mean holding time
Average
Bytes per
ratio per Call
procedure
Events
SDCCH
TCH
Attempt
MO Call
0.6
392
4s
50s
MT Call
0.4
381
4s
50s
Internal Handover
41
External Handover
199
Location Update
228
4s
IMSI Attach
0.5
228
4s
IMSI Detach
0.5
228
4s
MO SMS (PtP)
0.3
362
7s
MT SMS (PtP)
0.7
283
7s
Total bytes for
1888
one call (**)

CS traffic model
G2 BSC
BSC Evolution
70 Paging/s
120 Paging/s
CS paging on A interface (*)

(*): Values corresponding to the maximum BSC configurations (448 TRX for the G2 BSC and
1000 TRX for the Evolution BSC).
G2 BSC: machine limits BSC Evolution: results from the application of the traffic model.
(**) Total bytes for one call is computed considering the average ratio and bytes per
procedure.
- The traffic mix presented here above is considered as a worst case. The BSC can handle
different call mixes. If a Customers traffic mix is significantly different from the above
Standard Traffic Model, Alcatel-Lucent is prepared to study the possibility for the BSC to
cope with it.
- For a given BSS SW release, performance versus traffic mix can be committed only
1AA 00014 0004 (9007)A4
after BSC load test completion.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
40/47

11.2 SS7 LINK DIMENSIONNING

With the total bytes for one call attempt from previous table and given BHCA, it is possible to
estimate the SS7 required throughput and corresponding number of SS7 links needed.
Required SS7 throughput in kbit/s = BHCA /3600 x Total bytes for one call Attempt x 8 /1000
The required SS7 throughput is estimated in the MSC to BSS direction (worst case, because of
paging load).
Number of required channels at 64 kbit/s:
For 40% SS7 load: ROUNDUP (Required SS7 throughput / 64 x 0,4)
For 60% SS7 load: ROUNDUP (Required SS7 throughput / 64 x 0,6)
If the resulting number of links is above 16, then SS7 on 2 Mbit/s link (HSL) is required.
2 Mbit/s (one HSL link) satisfay the requirements for a 4500 Erl BSC with the Alcatel-Lucent traffic
model.
1AA 00014 0004 (9007)A4
Therefore two SS7 HSL are sufficient, the second HSL being used for redundancy purpose.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
41/47

11.3 BSS traffic model for PS traffic

The following traffic model is used as a reference to determine the capacity of the GP and GPU
boards.
A GPRS traffic session is defined as the sequence of packet calls (or transaction). The user
initiates the packet call when requesting information. During a packet call several packets may be
generated, which means the packet call constitutes a burst of packets.
The instans of packet arrivals
to network equipment
A transaction
t
A packet service session
First packet arrival

Last packet arrival

Typical characteristic of a packet service session

For example a WEB session consists of the period during which a user is actively doing WEB
browsing. During this session, a transaction corresponds to the download of a WEB page. There is
some times during which the user is looking at the screen, which corresponds to idle periods
between transactions.
The session is described by:
The signaling phase description,
The number of transactions per session,
The data load per session (page size),
The expected average packet size (IP-packet).
PDP context activation occurs at the beginning of each session. PDP context deactivation occurs
at the end of each session.
The attachment procedure can be triggered:
1AA 00014 0004 (9007)A4
Either at the beginning of each session,

Or the MS is attached when switched on.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
42/47
Additionally, mobility management (Routing Area update and cell update) must be taken into
account. The cell update can be neglected because it occurs during a transfer and does not trigger
additional TBF establishment. For simplification only periodic Routing area update is considered
with default value of the 3GPP timer T3312 (= 54mn).
A transaction can be seen as the period during which resources will be allocated to serve a burst
of packets. With the delayed downlink TBF release feature1, a transaction can be identified to
the time during which the downlink TBF is established.
For each type of service the transaction and session profile is specific. The combination of the
transaction and session description allows producing significant parameters at PCU level. The
Alcatel-Lucent traffic model considers the following main applications: WEB browsing, WAP, MMS,
Streaming, FTP downloads or mail application.
From the session description is characterized for each type of application as follows:
Session description (application level)
WEB
WAP
MMS-D
MMS-U
DL streaming
PS paging
Number of transactions per session
Average transaction size (Kbytes)
50
50
30
300
1000
1000
1500
1500
1500
Average packet size for control message (bytes)
40
40
40
40
40
User data load session DL (Kbytes)

User data load /session UL (Kbytes)
250
0
7
0
50
0
0
30
300
0
Average packet size for user data (bytes)
PS Session description for all profiles

With some additional hypothesis at transaction level not detailed here (number of TBF
establishment, number of UL/DL PDU, average PDU size) which vary for each application, then
adding the signaling for mobility and PDP context activation, we can describe the average user
behavior at the busy hour for each application.
Then the average traffic model can be based on proportion of each application.
Profile
Percentage of subscribers for each profile
WEB
WAP
MMS-D
MMS-U
DL streaming
5%
40%
25%
25%
5%
Alcatel mix of profile for BSS

The above data are used to determine the capacity of the GP and GPU boards, for each application
1AA 00014 0004 (9007)A4
and for the mix of all users.
1 It is assumed that the DL TBF is maintained as long as an uplink TBF is established taking into account the
addition of T_network_response_time, even if no data are sent on the downlink.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
43/47

12. ANNEX 2: A-BIS INTERFACE CONFIGURATION

12.1 Number of time-slots required with the different Signaling Multiplexing schemes
The table below gives the number of 64 kbit/s time-slots required with the different Signaling
Multiplexing schemes. The BTS is assumed to have n TRX in total all working in Full-Rate mode,
and we shall use the notation roundup (x) when a value x is to be rounded up to the next higher
integer. For G2 sectored BTS, we shall note i, j and k the number of TRX in sector 1,2 and 3.
Trafic (n TRX)
OML if 9100 BTS
OML if G2 BTS (*)
RSL if 9100 BTS
RSL if G2-BTS (*)
Without Signaling
Multiplexing
Static-Signaling
Multiplexing
2n (2 per TRX)
1 per BTS
1 per Sector
1 per TRX
2n (2 per TRX)
1 per BTS
1 per Sector
Roundup (n/4)
Roundup (i/4)+
Roundup (j/4)+
Roundup (k/4)
1 per
TRX
StatisticalSignaling
Multiplexing-64k
2n (2 per TRX)
0
Not applicable
See below
Not applicable
StatisticalSignaling
Multiplexing-16k
2n (2 per TRX)
0
Not applicable
0
Not applicable
Number of A-bis time-slots required according to the different Signaling Multiplexing schemes
(*): G2 BTS are no more supported from B11 release.
For statistical multiplexing on 64 kbit/s, a simple formula is not possible, taking into account the
fact that 3 RSL cannot be carried by one single A-bis TS (it requires 2 TS=The minimum number of
A-bis TS required for signaling with statistical multiplexing on 64 Kbit/s depending on the number
of TRX is provided in the table below (case normal signaling load). For high signaling load the
formula roundup (Number of TRX/ 2) applies.
TRX per BTS
10
11
12
A-bis TS for RSL +OML
TRX per BTS
13
14
15
16
17
18
19
20
21
22
23
24
A-bis TS for RSL +OML
1AA 00014 0004 (9007)A4
Number of A-bis TS required for statistical multiplexing 64 Kbit/s, normal signaling load.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
44/47

Typical cases where Signaling Multiplexing is very advantageous

- With Static Multiplexing, a sectored site with 3 x G2 BTS having 4 TRX requires:
3x[1+ 4x2+ roundup (4 / 4)] = 30 time-slots. Hence, it is possible to connect this site
with only one A-bis PCM (except if Closed Loop with TS0 transparency)
- With Statistical Multiplexing 64k, one 9100 BTS having 3x4 TRX requires
Normal signaling load:
3x4x2 + 3 = 27 time-slots.
High Signaling load:
- With Statistical Multiplexing 64k, one 9100 BTS having 3x2 TRX requires:
Normal signaling load:
High signaling load:
Hence, it is possible to connect 2 such sites with only one A-bis PCM.
- With Statistical Multiplexing 16k, one 9110 Micro-BTS with 2 TRX in full Rate mode requires:
2x2 = 4 time-slots.
Hence, it is possible to connect 7 of such BTSs with only one A-bis PCM.
- With Statistical Multiplexing 16k, one 9100 BTS with 3x1 TRX requires:
3x2 = 6 time-slots.
Hence, it is possible to connect 5 such sites with only one A-bis PCM (if open chain or
1AA 00014 0004 (9007)A4
closed loop with TS0 usage).
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
45/47

12.2 Configurations with 2 A-bis links

For large BTS configurations, a single E1 is already almost full with pure Circuit Switched traffic.
To support EDGE in such large BTS, extra timeslots can be configured on a second A-bis link.
A parameter MAX_EXTRA_TS_PRIMARY defines the number of extra A-bis timeslots dedicated to
packet on the primary link. This allows the Operator keeping some free timeslots on the primary
link, for example in anticipation of a further TRX extension of the BTS.
The following figure depicts examples of A-bis topology. A primary link is directly connected from
BSC to BTS. A secondary link may terminate a daisy chain.
BSC
Primary Abis
EVOLIUM
BTS
Secondary Abis
Primary Abis
EVOLIUM
BTS
Secondary Abis
BTS
BTS
Examples of A-bis topology

Note concerning the G2 BSC: There is no constraint about the position of the primary and
secondary links in the BSC. They may be connected to different A-Bis TSUs, and even different BSC
racks.
In addition, the TWIN TRX gives the opportunity to put more TRX than 12 TRX inside a single BTS
rack. For this purpose, it is also possible to configure a secondary A-bis link with basic A-bis
nibbles.
By default, the first A-bis link is filled up as much as possible, but it is possible to limit the number
of TRX in the first A-bis link.
Two parameters MAX_FR_TRE_PRIMARY and MAX_DR_TRE_PRIMARY define the maximum
1AA 00014 0004 (9007)A4
number of TRX of a BTS, which are mapped on the first A-bis link (respectively for Full Rate
and Dual Rate).
The Dual Rate TRX are mapped first, then the Full Rate TRX, then the Extra A-bis timeslots.
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
46/47

The OML of a BTS is always mapped on the first A-bis link.

The TCH and the RSL of a TRX are grouped on the same A-bis link. Furthermore, in case of RSL
multiplexing, the TCH belonging to the TRX of which the RSL are multiplexed together are mapped
on the same A-bis links, as well as the A-bis time slot, which carries the multiplexed RSL.
The following figure provides 2 examples for a BTS with 16 Full Rate TRX.
In the first case, MAX_FR_TRE_PRIMARY is set to 12 (default value), while on the second case
Second A-bis
RSL 13-16
TRX13
TRX13
TRX14
TRX14
TRX15
TRX15
TRX16
TRX16
First A-bis
OML+RSL1-4
TRX1
TRX1
TRX2
TRX2
TRX3
TRX3
TRX4
TRX4
RSL 5-8
TRX5
TRX5
TRX6
TRX6
TRX7
TRX7
TRX8
TRX8
RSL 9-12
TRX9
TRX9
TRX10
TRX10
TRX11
TRX11
TRX12
TRX12
MAX_FR_TRE_PRIMARY is limited to 8.
Second A-bis
RSL 9-12
TRX9
TRX9
TRX10
TRX10
TRX11
TRX11
TRX12
TRX12
RSL 13-16
TRX13
TRX13
TRX14
TRX14
TRX15
TRX15
TRX16
TRX16
First A-bis
OML+RSL1-4
TRX1
TRX1
TRX2
TRX2
TRX3
TRX3
TRX4
TRX4
RSL 5-8
TRX5
TRX5
TRX6
TRX6
TRX7
TRX7
TRX8
TRX8
MAX_FR_TRE_PRIMARY= 12
MAX_FR_TRE_PRIMARY= 8
This second option may be used for optimizing the filling of G2 BSC TSU.
1AA 00014 0004 (9007)A4
End of Document
Ed
MRD
03
Released
DMCPTBE3.DOC v 5
3DC 20003 0031 UZZZA
47/47

Dimensioning Rules For CS and PS Traffic PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Dimensioning Rules For CS and PS Traffic PDF

Hochgeladen von

Copyright:

Verfügbare Formate

1AA 00014 0004 (9007)A4

All rights reserved. Passing on and copying of this