You are on page 1of 25

All rights reserved.

Passing on and copying of this


document, use and communication of its contents

TECHNICAL FEATURE DESCRIPTION


not permitted without written authorization

Abis mapping : Timeslot allocation

Is there a corresponding Marketing feature?

YES Ð 8.1 Edition 01P03 27/03/95 (indirectly)

No Ð

AUTHOR
Regis DUPUIS

03rl 13/02/98

03p2 22/12/97

03p1 16/12/97

02rl 13/06/97

02p1 23/04/97

02iP 03/04/97 DDL Dev. Proj. Mng. Archit. Resp. Product Mng.
Ed Date Distribution List Validation Validation Validation Approval
1AA 00014 0004 (9007)A4

TECHNICAL FEATURE DESCRIPTION


Abis mapping : Timeslot allocation
Ed 03 Released

TD 3BK 10204 0335 DTZZA 1/25


Table of Contents

LIST OF TABLES __________________________________________________________ 3


All rights reserved. Passing on and copying of this
document, use and communication of its contents

LIST OF FIGURES _________________________________________________________ 3


not permitted without written authorization

HISTORY _________________________________________________________________ 3
TYPE_____________________________________________________________________ 4
RELATED DOCUMENTS ___________________________________________________ 4
PREFACE_________________________________________________________________ 4
1. DEFINITIONS___________________________________________________________ 5
1.1 Abis Interface _____________________________________________________________________5
1.2 Abis Network Topology_____________________________________________________________5
1.3 Abis Traffic _______________________________________________________________________6
1.3.1 Qmux bus channel ______________________________________________________________6
1.3.2 Ring Control Channels __________________________________________________________6
1.3.3 BTS Channels _________________________________________________________________7
2. TECHNICAL DESCRIPTION ______________________________________________ 8
2.1 Reasons of Timeslot allocation rules definition ___________________________________________8
2.1.1 Equipment constraints ___________________________________________________________8
2.1.2 2.048 kbit/s links suppliers constraints _____________________________________________9
2.1.3 Installation, maintenance constraints _______________________________________________9
2.1.4 The current situation and relative rules ____________________________________________10
2.1.5 Service impact ,the System outage ________________________________________________10
2.1.6 R4 Features Introduction ________________________________________________________10
3 R3 RULES ______________________________________________________________ 12
3.1 Star Mapping ____________________________________________________________________12
3.2 Closed catalogue __________________________________________________________________13
3.3 Open catalogue ___________________________________________________________________14
3.3.1 Decreasing allocation __________________________________________________________14
3.3.2 Full allocation ________________________________________________________________15
3.4 Summary of CMA R3 Mapping rules__________________________________________________17
4 R4 RULES ______________________________________________________________ 18
4.1 Star Mapping_____________________________________________________________________18
4.2 Closed catalogue __________________________________________________________________18
4.3 Open catalogue ___________________________________________________________________18
4.3.1 Decreasing Allocation __________________________________________________________18
4.3.2 Full Allocation________________________________________________________________20
4.4 Transition from one rule to another ___________________________________________________20
4.5 Summary of CMA R4 Mapping Rules _________________________________________________21
4.6 Support of new features_____________________________________________________________21
5. IMPACTS ______________________________________________________________ 24
5.1 HW/FW/SW impacts_______________________________________________________________24
6 GLOSSARY _____________________________________________________________ 24
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 2/25


LIST OF TABLES
Table 1 : Equipment versus Abis topology _______________________________________________________8
Table 2 : Service bytes versus Equipment Generation _____________________________________________9
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Table 3 : Timeslot budget versus Abis topology/TSO Option ________________________________________9


not permitted without written authorization

Table 4 : Number of Timeslot versus RSL option _________________________________________________10


Table 5 : Relation between sectors and number of FU’s. __________________________________________11
Table 6 : BTS allocation versus FU number with FA1 rule _________________________________________17
Table 7 : BTS Allocation versus FU number with FA2 rule ________________________________________17
Table 8 : CMA R3 Mapping rules ____________________________________________________________18
Table 9 : CMA R4 Mapping rules ____________________________________________________________21
Table 10 : Supported features/Mapping rules ___________________________________________________22

LIST OF FIGURES
Figure 1 : Abis Network Topologies____________________________________________________________5
Figure 2 : Use of Intermediate Transmission Networks ____________________________________________7
Figure 3 : The Star mappings________________________________________________________________12
Figure 4 : The Closed catalogues configurations ________________________________________________13
Figure 5 : A example of Decreasing allocation mapping __________________________________________15
Figure 6 : The Full Allocation Configurations __________________________________________________15
Figure 7 : An example of R4 Decreasing Allocation mapping ______________________________________20
HISTORY

19/02/96 ED:01 B. Genet Document creation


P 01
06/03/96 ED:01 B. Genet Following meeting 29/02/96 and received informations from
P02 CMA/Toscana.
The main changes concern : - a simplification of the general
allocation rules but reconfiguration constraints are no more
supported - Nokia multidrop equipments restrictions in TS0
transparency taken in account.
2/04/96 ED:01 B. Genet Following written remarks : - correction for the Nokia constraint
P03 only for R bits. - suppression of the BSC G1 upgraded.
14/6/96 ED:01 B. Genet Following Prereview 10/5/96 See meeting report reference 1
Stable1
26/7/96 ED:01 B. Genet Following Review 2/7/96 See meeting report reference 1
Release
ED:02 R.Dupuis Following new proposal : Definition of the Free mapping rule
P01
13/06/97 Ed 02 R.Dupuis Following Review Meeting on Ed 2 P01 : SAS/ea/0694.97
Released (AP’s : See memo (E_mail) TD/SAS/rdu/796.97/Ed01)
16/12/97 Ed 03 P1 R.Dupuis Free mapping rule postponed in Release B5. Full Allocation still
offered in B4.
22/12/97 Ed 03 P2 R.Dupuis Following comments on P1 from E.Amblard and G.DAEL
(CO_F)
13/02/98 Ed 03 Rl R.Dupuis Following E_mail review TD/SAS/rdu/259.98/ED1
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 3/25


All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

TYPE
Linked to a Marketing Feature
Description
Technical improvement without X
Marketing impact

RELATED DOCUMENTS

[1] Technical feature description Abis signalling links 3BK 10204 0100 DRZZA
multiplexing scheme16kbit/s static sub multiplex
[2] Technical feature description Abis signalling link 3BK 11204 0316 DRZZA
statistical submultiplexing O&M aspects
[3] Transmission architecture specification (Release 4) 3BK 11200 0003 DTZZA
[4] MFD 8.1 Abis signalling multiplexing schemes 3BK 10203 0100 DRZZA
[5] Transmission Functional Specification 3BK 11203 0015 DSZZA
[6] Engineering rules and configurations of the G3 BTS 3BK 15015 AAAA PWZZA

PREFACE
This TFD is intended to define the Abis Mapping TS allocation rules offered in Release 4.

The most complete possible view of the different parameters intervening is needed to evaluate
the relevancy of such choices.

We are going first to give some definitions and recall the different aspect of the Abis interface
we have to take into account.
We will then give the list of concerned equipment and calculate the Timeslot budget in regard
to selected options (Equipment generation, topology...)
We will described the new features offered in Release 4 which impact the Abis mapping rules

We will then describe the rules offered in R3 and those offered in R4.
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 4/25


1. DEFINITIONS
All rights reserved. Passing on and copying of this
document, use and communication of its contents

1.1 Abis Interface


not permitted without written authorization

The Abis interface is a standard ITU-T G703/G704 interface. Refer (5) for detail.
It is based on a frame structure.The frame repetition rate is 8000 Hz.The frame length is 256
bits grouped in 32 timeslots numbered from 0 to 31.The 8 bits of each timeslot are numbered
from 1 to 8.
The TS0 is used for synchronization purpose.
Part of the TS0 (bit 4 to 8, called reserved bits) not containing the frame alignment word is for
national usage. It can be used in certain condition for point to point application.

1.2 Abis Network Topology

For a functional point of view, two topologies are specified to physically connect the BTS to
the BSC.

BTS A b i s lin k
A b is lin k

BTS
BSC

A b is lin k

a ) C h a in T o p o lo g y BTS

BTS A b is lin k
A b is lin k

BTS
BSC

A b is lin k
A b is lin k BTS
b ) R in g T o p o lo g y

Figure 1 : Abis Network Topologies


a) Chain Topology : The BSC is connected with a Abis link to a BTS. This one is
connected to a 2nd BTS with a 2nd Abis link, the 2nd BTS is at its turn connected to a
third one ..and so on.
b) Ring Topology : The last BTS of a chain is connected back to the BSC.
This topology is offered for securisation purpose : traffic between any BTS and BSC
is broadcast on the two paths. (Selection is based on dedicated Service bits/bytes) : See
next section.
Note : For historical reasons NOKIA defined also a Star topology (particular case of a chain
1AA 00014 0004 (9007)A4

with one BTS).

Ed 03 Released

TD 3BK 10204 0335 DTZZA 5/25


1.3 Abis Traffic

There are three categories of channels to be mapped onto the transmission links:
All rights reserved. Passing on and copying of this
document, use and communication of its contents

è Qmux channel, used by the transmission O&M controller (TSC).


not permitted without written authorization

‚ Ring control channels used by the transmission equipments independently from the
transmission O&M controller (TSC).
ƒ BTS channels
1.3.1 Qmux bus channel
The Transmission part of the Network Elements are configured and supervised from a
Centralised Controller via a distributed Qmux bus.


This Qmux bus is conveyed on an Abis timeslot : two options are proposed :
TS0 Transparency.
Bit 1 and Bit 2 of any timeslot (from 1 to 31) can be used for this purpose.(only 16

ô
kbit/s rate)
TS0 usage.
Reserved bits of TS0 are used.
_Bit 5 to 8 (4 bits) in case of 16 kbit/s rate
_Bit 7 and 8 (2 bits) in case of 8 kbit/s rate
1.3.2 Ring Control Channels


Some Service bits/bytes are needed in case of Ring topology.
“Ring Control Byte/bits” : R byte/bits (8 or 4 bits, a complete timeslot is
used in both cases)
A byte is needed and dedicated for the supervision of the Ring continuity. It is used , at each
BTS and BSC stage, to select the direction from which the Data are extracted.
This R byte is conveyed in any of the TS from 1 to 31.

ô “Synchronization Control bits” : S bits (2 bits)


These bits are needed to select the direction from which is extracted the clock synchronisation
signal. These two bits can either be conveyed in any TS (from 0 to 31).
Current value TS0 (NFAS) TS1 to TS31
MCB bit Bit 4 Bit 5
LCB bit Bit 5 Bit 6

í “Far end Alarm” bits : F bits (2 duplicated bits)


ITN (Intermediate Transmission Network :64 kbit/s cross-connect or multiplexers..) can be
used between BSC and BTS or two BTS. These ITN could be not transparent to the TS0.
Service bits (the F bits) have been forseen for continuity checking for alarm reporting
purposes. They would have given an information to the remote end in case of failure within the
ITN.This would have been particularly useful in Ring configuration to be informed that one of
the two paths is in failure. (there is no other meaning to be awarded of this situation)
1AA 00014 0004 (9007)A4

Current value TS1 TS16 ou 18

Ed 03 Released

TD 3BK 10204 0335 DTZZA 6/25


MCB bit Bit 3,4 Bit 7,8
F bits are not used in R4 due to buggy implementation in NOKIA Hardware.
A b is A b is
IT N
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

A I S 2 M b it/s
BSC BTS
A IS 6 4 k b it/s
RAI o n G S M T r a f fi c

6 4 k b it/s C r o s s -C o n n e c ts
i .e T r a n s m ic N e tw o r k

I n c a s e o f f a ilu re w ith in th e IT N , th e F b its a re s e t to “ 1 ” d u e to


th e 6 4 k b it/s A IS in a ll “ G S M ” tim e s lo ts .T h is a le rts th e B T S o f a
f a ilu re w ith in th e IT N . R e fe r (3 ) a n d (5 ) fo r d e ta il c o n c e rn in g r e la te d
r e a c tio n s

Figure 2 : Use of Intermediate Transmission Networks

1.3.3 BTS Channels


Two types of channels are exchanged between the BTS and the BSC :

 The TCH channels which carry the end user traffic are conveyed on Abis in
16 kbit/s or 8 kbit/s channels. There are 8 (FR), 16 (HR) TCH per TRE.
Two Abis timeslots are needed per TRE.

ô The LapD channels which carry signalling information between BTS and BSC are
conveyed on Abis in 64 or 16 kbit/s channels .
_There is one LapD OML channel per BTS.
_There is one LapD RSL per TRE.
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 7/25


2. TECHNICAL DESCRIPTION
Note : In the following , one has to consider that TS number for any timeslot
All rights reserved. Passing on and copying of this
document, use and communication of its contents

exchanged between BTS and BSC is same for both sides.


not permitted without written authorization

2.1 Reasons of Timeslot allocation rules definition

We have listed in the following the different aspects to take into account and the reasons
leading to define Abis mapping TS allocations rules :

 Equipment constraints
ô 2.048 kbit/s links suppliers constraints
í Installation, maintenance objectives (minimize site intervention...)
÷ The current situation and relative rules
û Service impact , System outage
ø Introduction of new features
Note : This order is arbitrary.
2.1.1 Equipment constraints
2.1.1.1 Alcatel Equipment constraints

The following table gives the Abis topology supported versus the equipment type or
generation.

Note : mixing of equipment type or generation (except possible restriction due to specific
constraints) are authorized.

Equipments and Board name Abis topology


“originator” supported
BTS G1 (Nokia) SMHW (*) Chain (only one BTS)
DB2M,DX2M Chain ,Ring
G2 (Alcatel) SMBI Chain,Ring
Micro (Alcatel) SMFG Chain,Ring
G3 (Alcatel) SUMP Chain,Ring
BSC BSC G1 (Nokia) SMHW (*) Chain (only one BTS)
DB2M,DX2M Chain ,Ring
BSC G2 (Alcatel) BIUA Chain,Ring

Table 1 : Equipment versus Abis topology


(*) Specific Hardware that limits the capacity of the chain to one single BTS.
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 8/25


The second table gives the Service bits/bytes constraints (in term of location in the frame)
versus the equipment originator
All rights reserved. Passing on and copying of this
document, use and communication of its contents

TS0 Usage TS0 Transparency


not permitted without written authorization

Service Qmux R byte S Bits Qmux R byte S Bits


bits/bytes
Nokia TS0 Any TS TS0 Any TS Any TS (1 to 31) Any TS (1 to 31)
(G1) (1 to 31) (1 to 31) ≠ Qmux TS ≠ Qmux TS
and ≠ R byte TS
Alcatel TS0 Any TS TS0 Any TS Any TS (1 to 31) Any TS (1 to 31)
(G2,..) (1 to 31) (1 to 31) ≠ Qmux TS including with
Qmux

Table 2 : Service bytes versus Equipment Generation

The third table gives the Timeslot budget in regard to the previous elements.

Number of timeslots usable for BTS channels


TS0 Usage TS0 Transparency
Chain 31 30
Mix G1/G2 Ring (1) 30 28
“Full” Alcatel Ring (2) 30 29

Table 3 : Timeslot budget versus Abis topology/TSO Option


(1) Mix G1/G2 : Supporting both Nokia and Alcatel Equipments (See 2.1.1.1 Alcatel
Equipment constraints)
(2) “Full Alcatel” : Supporting only Alcatel Equipments (See 2.1.1.1 Alcatel Equipment
constraints)

2.1.1.2 External Equipment constraints


As already mentionned Intermediate transmission networks can be used on Abis interface
Some specific constraints can then be due to this use.
_Difficulty to reconfigure the 64 kbit/s Cross-connects
_TS0 terminated at ITN input .... (preventing TS0 usage option)

2.1.2 2.048 kbit/s links suppliers constraints


Suppliers have their proper rule to allocate timeslots to customer : i.e Transfix leased lines
Service (supported on Transmic Network) offer N*64 kbit/s transportation: the N timeslots
being consecutives, starting from TS1. Only part of the PCM line needs to be rented.

2.1.3 Installation, maintenance constraints


Have the most simple and logical rules could be required particularly .for mapping retrieval in
case this could not be achieved with a back up database. (Considering our tools , this
1AA 00014 0004 (9007)A4

constraint has not been retained)

Ed 03 Released

TD 3BK 10204 0335 DTZZA 9/25


One other main objective is to minimize the on-site intervention.

2.1.4 The current situation and relative rules


All rights reserved. Passing on and copying of this
document, use and communication of its contents

Introduction of a new rule could have a big impact on already installed networks :i.e in case of
not permitted without written authorization

change of the Qmux location, a site intervention on BTS’s and BSC can be required.

Note : For Nokia equipment the Qmux location could not be changed remotely. This leads to
site intervention each time we switch from one configuration to another.
(The reason is that two consecutives commands to the NE are needed to modify the Qmux
location. It is not possible in same time to modify the Qmux location and use the Qmux bus to
exchange the second command)

2.1.5 Service impact ,the System outage


Minimizing the System outage is also a permanent aim to consider : i.e., depending selected
rule, a extension/reduction on one BTS can impact all the BTS of a multidrop.

2.1.6 R4 Features Introduction


2.1.6.1 Abis signalling link static sub-multiplexing

This feature allows to reduce the Transmission exploitation costs by decreasing the number of
needed timeslots for a same BTS traffic and then the number of public PCM links required
over the Abis interface.
The RSL is carried on 16 kbit/s channel instead of 64 kbit/s channel. Up to four RSL of a same
BTS equipment can then be carried in one 64 kbit/s timeslot.

The following table gives the comparaison between RSL 16 kbit/s and RSL 64 kbit/s for a
given configuration.

Timeslot needed for BTS channels


RSL 64 kbit/s RSL 16kbit/s
OML TCH RSL Total RSL Total
1 TRX 1 2 1 4 1 4
2 TRX 1 4 2 7 1 6
3 TRX 1 6 3 10 1 8
4 TRX 1 8 4 13 1 10
5 TRX 1 10 5 16 2 13
6 TRX 1 12 6 19 2 15
7 TRX 1 14 7 22 2 17
8 TRX 1 16 8 25 2 19

Table 4 : Number of Timeslot versus RSL option


1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 10/25


All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

2.1.6.2 Sectorized Site BTS

Refering (6) :

Several configurations are offered with EVOLIUM TM BTS : up to 3 sectors with a total
number of up to 8 TRE.
There is a fixed relation between the sector and the FU (SBL) number.

1 sector 2 sectors 3 sectors

Number of TRE/sector 1 ...8 TRE 2*1 to 2*6 TRE 3*1 to 3*4 TRE

Table 5 : Relation between sectors and number of FU’s.


2.1.6.3 Dual Rate

There is then no impact on Abis mapping.

Note : It has to be noted that the RSL 16 kbit/s feature is not possible with the Half rate.
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 11/25


3 R3 RULES
The following mapping rules have been defined in Release 3.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

3.1 Star Mapping

TS TS0 Usage TS TSO Transparency


0 Q mux 0
1 FU1 1 FU1
2 FU1 2 FU1
3 FU5 3 FU5
4 FU5 4 FU5
5 FU2 5 FU2
6 FU2 6 FU2
7 FU6 7 FU6
8 FU6 8 FU6
9 FU3 9 FU3
10 FU3 10 FU3
11 FU7 11 FU7
12 FU7 12 FU7
13 FU4 13 FU4
14 FU4 14 FU4
15 FU8 15 FU8
16 FU8 16 FU8
17 17
18 18
19 19 Q mux
20 20
21 21 OML
22 RSL8 22 RSL8
23 RSL7 23 RSL7
24 RSL6 24 RSL6
25 RSL5 25 RSL5
26 26
27 RSL4 27 RSL4
28 RSL3 28 RSL3
29 RSL2 29 RSL2
30 RSL1 30 RSL1
31 OML 31

Figure 3 : The Star mappings

Note : This is the only mapping supported by the SMHW .


1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 12/25


3.2 Closed catalogue
All rights reserved. Passing on and copying of this
document, use and communication of its contents

The Qmux channel is always conveyed on TS0.(TS0 Usage)


not permitted without written authorization

The closed catalogue includes a list of PCM TS mapping descriptions corresponding to a


limited set of predefined multidrop link configurations in terms of BTS and TRE.

The maximum number of BTS together with the maximum number of TREs they can
accomodate is defined in each case. The actual number of equipped BTS or TRE is
configurable within these limits, but the maximum transmission capacity is always reserved in
advance.
_Any extension/reduction of capacity of one BTS has no or a minimum impact on the
traffic on the others BTS neither affected their transmission settings.
(BIUA reconfiguration is needed in case of BTS removal/addition in Ring mapping on
Ring topology)
_ Reconfiguration of any intermediate cross-connect is not needed (the maximum
configuration being programmed at the start)_
The mappings of the closed catalogue fit all both the chain and ring topologies with one
exception (chain only for 3x3 SFR, see below).
The different BTS are named a,b,c and d on the figure below. There is no fixed relation
between this name which determines the mapping and the physical position of the BTS on the
link.
1 BTS x 8 TRE 1x5 + 1x4 1x4 + 1x3 + 1x2 4 BTS X 2 TRE 3 BTS x 3 TRE 3 x 3 SFR

0 Qmux + Sbits Qmux + Sbits Qmux + Sbits Qmux + Sbits Qmux + Sbits Qmux
1 OML a
FU 1 FU 1 - a FU 1 - a FU 1 - a FU 1 - a
2 FU 1 - a
3 FU 5 FU 1 - b FU 1 - b FU 1 - b FU 1 - b
4 RSL 1 - a
5 FU 2 FU 2 - a FU 2 - a FU 2 - a FU 2 - a FU 2 - a
6
7 RSL 2 - a
8 FU 6 FU 2 - b FU 2 - b FU 2 - b FU 2 - b
FU 3 - a
9 FU 3 FU 3 - a FU 1 - c FU 1 - c FU 1 - c
10 RSL 3 - a
OML b
FU 7 FU 3 - b FU 3 - c FU 1 - d FU 3 - c
FU 1 - b
FU 4 FU 4 - a FU 2 - c FU 2 - c FU 2 - c RSL 1 - b
15 FU 8 FU 4 - b FU 4 - a FU 2 - d FU 3 - b FU 2 - b
RSL 2 - b
FU 5 - a FU 3 - a FU 3 - a
18 FU 3 - b
RSL 4 - a OML d Rbits
20 RSL 5 - a OML b OML b OML b RSL 3 - b
OML b OML c OML c OML c OML c
RSL 8 RSL 4 - b OML 1 RSL 2 - d RSL 3 - b
7 3 RSL 3 - c RSL 1 - d RSL 3 - c
FU 1 - c
6 2 RSL 2 - b RSL 2 - b RSL 2 - b RSL 1 - c
25 5 RSL 1 - b RSL 1 - b RSL 1 - b RSL 1 - b
OML OML a RSL 3 - a OML a RSL 3 - a
FU 2 - c
RSL 4 RSL 4 - a RSL 2 - c RSL 2 - c RSL 2 - c RSL 2 - c
3 3 RSL 1 - c RSL 1 - c RSL 1 - c
2 2 RSL 2 - a RSL 2 - a RSL 2 - a
FU 3 - c
30 1 RSL 1 - a RSL 1 - a RSL 1 - a RSL 1 - a RSL 3 - c
R bits R bits R bits R bits OML a
1AA 00014 0004 (9007)A4

Figure 4 : The Closed catalogues configurations

Ed 03 Released

TD 3BK 10204 0335 DTZZA 13/25


3.3 Open catalogue
All rights reserved. Passing on and copying of this
document, use and communication of its contents

The Qmux channel is never conveyed on timeslot 0.(TS0 Transparency)


not permitted without written authorization

The supported multidrop link configurations in terms of BTS and TRE are not enlisted in
advance. A rule is defined (there are several different rules) to map the BTS channels onto the
PCM TS depending on the actual number of equipped BTS and TRE.
3.3.1 Decreasing allocation
This allocation policy is only valid for chain.
This rule complies with TRANSMIC rules (See 2.1.2)
The number of “leased” timeslots on each Abis link fits the exact need.
Any extension/reduction of capacity of a BTS or addition/removal of a BTS may lead to a
complete reshuffling of the mapping : disturbance on all BTS on the chain.

On all segments of the chain, the BTS channels


are grouped on a per BTS basis. The blocks of A b is 1 A b is 2 A b is n
BTS channels are contiguous. Within a block B S C
B T S 1 B T S 2 B T S n
the OML/RSL and TRE channels are
contiguous. The first block on a PCM link
(smallest TS numbers) corresponds to the last
physical position on the multidrop link.

TS
0 0 0
1 Q mux 1 Q mux 1 Q mux
2 OML n 2 OML n 2 OML n
3 FU 1 BTS n 3 FU 1 BTS n 3 FU 1 BTS n
4 FU 1 BTS n 4 FU 1 BTS n 4 FU 1 BTS n
5 RSL 1 BTS n BTS n 5 RSL 1 BTS n 5 RSL 1 BTS n
.. .. ..
FU m BTS n FU m BTS n FU m BTS n
FU m BTS n FU m BTS n FU m BTS n
RSL m BTS n RSL m BTS n RSL m BTS n
... ... ...
OML 2 OML 2
FU 1 BTS 2 FU 1 BTS 2
FU 1 BTS 2 FU 1 BTS 2
RSL 1 BTS 2 BTS 2 RSL 1 BTS 2
.. ..
FU p BTS 2 FU p BTS 2
FU p BTS 2 FU p BTS 2
RSL p BTS 2 RSL p BTS 2
OML 1
FU 1 BTS 1
FU 1 BTS 1
RSL 1 BTS 1 BTS 1
..
FU k BTS 1
FU k BTS 1
RSL k BTS 1

31 31 31
1AA 00014 0004 (9007)A4

Mapping on Abis 1 Mapping on Abis 2 Mapping on Abis n

Ed 03 Released

TD 3BK 10204 0335 DTZZA 14/25


Figure 5 : A example of Decreasing allocation mapping

3.3.2 Full allocation


All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

Full Allocation occupies at every segment of an Abis path the same amount of TS’s but is open
for every dimensioning concerning BTS’s and FU’s.The numbering of FU’s and RSL’s is not
related to the BTS’s but it is just the sequence number on Abis.

There are two variants depending on the maximum number of BTS on the multidrop link (4 or
7, Ring Type (1) or type (2)). The Qmux and S bits location depends on which variant is used.
The TCH channels are located between TS1 and the TS used by the Q-bits / S-bits, the RSL
and OML links between the TS used by the Q-bits / S-bits and TS 30.

TS 1...4 BTS TS 5...7 BTS


0 0
1 FU 1 1 FU 1
2 FU 1 2 FU 1
3 FU 5 3 FU 5
4 FU 5 4 FU 5
5 FU 2 5 FU 2
6 FU 2 6 FU 2
7 FU 6 7 FU 6
8 FU 6 8 FU 6
9 FU 3 9 FU 3
10 FU 3 10 FU 3
11 FU 7 11 FU 7
12 FU 7 12 FU 7
13 FU 4 13 FU 4
14 FU 4 14 FU 4
15 FU 8 15 S bits
16 FU 8 16 Q bits
17 S bits 17 OML 7
18 Q bits 18 OML 6
19 RSL 8 19 OML 5
20 RSL 7 20 RSL 7
21 RSL 6 21 RSL 6
22 RSL 5 22 RSL 5
23 RSL 4 23 RSL 4
24 RSL 3 24 RSL 3
25 RSL 2 25 RSL 2
26 RSL 1 26 RSL 1
27 OML 4 27 OML 4
28 OML 3 28 OML 3
29 OML 2 29 OML 2
30 OML 1 30 OML 1
31 Ring Control 31 Ring Control
Ring Type 1 (FA1 or FA2) Ring Type 2 (Only FA1)

Figure 6 : The Full Allocation Configurations

In Ring type 1 : up to 8 FU locations are defined.


In Ring type 2 : up to 7 FU locations are defined.

Two sub_variants are defined corresponding to the TCU capacity :


FA1 in case of 1 FU/TCU and FA2 in case of 2 FU/TCU.
With FA1 rule, the FU locations are allocated to a BTS one after the other as needed.
1AA 00014 0004 (9007)A4

With FA2 rule, the reservation is systematically made for a couple of FU’s.

Ed 03 Released

TD 3BK 10204 0335 DTZZA 15/25


: reservation of FUi and FU i+1 locations (with i=1, 3, 5 or 7).
All rights reserved. Passing on and copying of this
document, use and communication of its contents

3.3.2.1
not permitted without written authorization

Ring Type 1 FA1 application


The allocated timeslots of a FU number k of BTS(j) are those corresponding to FU(m) (in FA1
rule) with m = (total number of FU of the previous BTS’s) + k
(e.g the second FU of BTS 2 uses the timeslots corresponding to FU 3 in the FA1 rule)

A b is lin k A b is lin k A b is lin k A b is lin k

BSC BTS 1 BTS 2 BTS 3 BTS 4

FU1 FU2 FU3 FU4 FU5 FU6

a ) C o n fig u r a tio n n ° 1

A b is lin k A b is lin k A b i s lin k A b i s lin k

BSC BTS 1 BTS 2 BTS 3 BTS 4

FU1 FU2 FU3 FU4 FU5 FU7 FU8


FU6
b ) E x te n s io n o f o n e F U in B T S 1 a n d 1 F U in B T S 3

R in g T y p e 1 F A 1

In case of extension of FU on intermediate BTS the allocated timeslots of all the BTS after this
modified BTS are impacted

Thus the corresponding allocation timeslot for the 2 configurations is :

BTS 1 BTS 2 BTS 3 BTS 4


FU1 FU2 FU3 FU4 FU5 FU6
Config. n° 1
TCH TS 1, 2 5, 6 9, 10 13, 14 3, 4 7, 8
RSL TS 26 25 24 23 22 21
Extension
FU1 FU2 FU3 FU4 FU5 FU6 FU7 FU8
TCH TS 1, 2 5, 6 9, 10 13, 14 3, 4 7, 8 11,12 15,16
RSL TS 26 25 24 23 22 21 20 19

FU1 FU2 FU3 FU4 FU5 FU6 FU7 FU8


Conf n°1 BTS1 BTS2 BTS3 BTS4 Not Not
1AA 00014 0004 (9007)A4

used used

Ed 03 Released

TD 3BK 10204 0335 DTZZA 16/25


Extens. BTS1 BTS2 BTS3 BTS4

Table 6 : BTS allocation versus FU number with FA1 rule


All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

3.3.2.2 Ring Type 1 FA2 application


In this case reservation is made for a couple of FU.
The allocated timeslots of a FU number k of the BTS(j) are those corresponding to FU(m) (in
FA2 rule) with m being equal to the total sum of (number of FU for each BTS (*))+ k.
(*) this number of FU per BTS being rounded to the superior even number.

A b is lin k A b i s l in k A b i s l in k A b is lin k

BSC BTS 1 BTS 2 BTS 3 BTS 4

FU1 FU3 FU4 FU5 FU6 FU7

a ) C o n fig u r a tio n n ° 1

A b i s l in k A b is lin k A b is lin k A b is lin k

BSC BTS 1 BTS 2 BTS 3 BTS 4

FU1 FU2 FU3 FU4 FU5 FU6 FU7

b ) E xte n s io n o f O N L Y o n e F U in B T S 1

R in g T y p e 1 F A 2

In the given example, we see that thank to allocation per couple of FU, extension of one FU on
the BTS 1 does not impact the allocation of the following ones BUT in contrario it is not
possible to add a TRE to BTS3.
Thus the corresponding allocation timeslot for the 2 configurations is :
BTS 1 BTS 2 BTS 3 BTS 4
Configuration n° 1 FU1 FU3 FU4 FU5 FU6 FU7
TCH TS 1, 2 9, 10 13, 14 3, 4 7, 8 11,12
RSL TS 26 24 23 22 21 20
Extension FU1 FU2 FU3 FU4 FU5 FU6 FU7
TCH TS 1, 2 5, 6 9, 10 13, 14 3, 4 7, 8 11,12
RSL TS 26 25 24 23 22 21 20

FU1 FU2 FU3 FU4 FU5 FU6 FU7 FU8


Conf n°1 BTS1 Reserved BTS2 BTS3 BTS4 Reserved
Extens. BTS1 BTS2 BTS3 BTS4 Reserved

Table 7 : BTS Allocation versus FU number with FA2 rule


3.4 Summary of CMA R3 Mapping rules

Abis topology Mappings


1AA 00014 0004 (9007)A4

TS0 Usage TS0 Transparency

Ed 03 Released

TD 3BK 10204 0335 DTZZA 17/25


Chain Star Mapping Star Mapping
Closed catalogue Open catalogue : Decreasing or Full allocation
Ring Closed catalogue Open catalogue : Full allocation
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

Table 8 : CMA R3 Mapping rules

4 R4 RULES
The following rules are introduced and/or supported in Release 4.

4.1 Star Mapping


The R3 Star mapping is still supported in R4

This can be needed in case of gradual migration : A Nokia BTS connected to a G1 BSC
_1st step : the BTS is upgraded (G1-> G2) the mapping is kept to not intervene on
BSC site.
Note : Restriction Star mapping with TS0 usage is forbidden in case of
SMBI/SMFG/SUMP
In this case either Star mapping with TS0 transparency is selected
or a change from SMHW --> DB2M/DX2M is required to allow
Open catalogue.
_2nd step : the BSC is upgraded (G1-> G2) the mapping is still kept to not intervene
on BTS site

The static submultiplexing of 16Kb/s RSLs into a single Abis PCM TS is not supported.

4.2 Closed catalogue

The R3 Closed catalogue is supported in Release 4

The static submultiplexing of 16Kb/s RSLs into a single Abis PCM TS is not supported.

The EVOLIUM TM BTS Sectorized Site configurations are supported in Closed Catalogue but due to
the fixed numbering of the TRE some configurations are not possible : i.e the 3 *4 TRX Config
underequipped to 3*2 TRX (TRX number = 1,2,5,6,9,10) cannot fit with the 1BTS*8TRX
configuration.

4.3 Open catalogue

4.3.1 Decreasing Allocation


This allocation policy , defined in Release 3, is still supported in Release 4

4.3.1.1 RSL 16 kbit/s

The Decreasing allocation rule is modified to take into account RSL 16kbit/s feature.
The timeslot previously allocated for the first RSL of a BTS carries the RSL’s of 4 TRE. In
1AA 00014 0004 (9007)A4

same way the timeslot previously allocated for the fifth RSL of a BTS carries the RSL’s of the

Ed 03 Released

TD 3BK 10204 0335 DTZZA 18/25


other 4 TRE (of course the TCH FU2/3/4 and TCH FU 6/7/8 are shifted to the top due to
“free” timeslots)
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

TS
0
1 QMux QMux
2 OML2 OML2
3 FU1 BTS 2 FU1 BTS 2
4 FU1 BTS 2 FU1 BTS 2
5 RSL1 RSL2 RSL3 RSL4 RSL1 RSL3 RSL5
6 FU2 BTS 2 FU3 BTS 2
7 FU2 BTS 2 FU3 BTS 2
8 FU3 BTS 2 FU5 BTS 2
9 FU3 BTS 2 FU5 BTS 2
10 FU4 BTS 2 OML1
11 FU4 BTS 2 FU1 BTS1
12 FU5 BTS 2 FU1 BTS1
13 FU5 BTS 2 RSL 1
14 RSL5 RSL6 RSL7 RSL8 FU2 BTS1
15 FU6 BTS 2 FU2 BTS1
16 FU6 BTS 2 RSL2
17 FU7 BTS 2
18 FU7 BTS 2
19 FU8 BTS 2
20 FU8 BTS 2
21 OML1
22 FU1 BTS1
23 FU1 BTS1
24 RSL1
25 FU2 BTS1
26 FU2 BTS1
27 RSL2
28
29
30
31
First Example with Second example with
1AA 00014 0004 (9007)A4

a BTS*8 TRX RSL 16kbit/s a SSC 3*1 TRX RSL 16kbit/s

Ed 03 Released

TD 3BK 10204 0335 DTZZA 19/25


Figure 7 : An example of R4 Decreasing Allocation mapping
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

4.3.2 Full Allocation


The Full Allocation Ring Type 1 and Ring Type 2 are still supported in Release 4.

4.3.2.1 Migration from FA2 to FA1


The FA2 configuration is not supported in BSCG2.
This removal implies to change from FA2 to FA1 the configuration of PCM connected to BSC
G2 when migrating from B3 to B4.

A b is lin k A b is lin k A b is lin k

BSC BTS 1 BTS 2 BTS 3

FU 1 FU3 FU5 FU6 FU7


FU2 a ) C o n fig u r a tio n n ° 1 F A 2

A b i s l in k A b is lin k A b i s lin k

BSC BTS 1 BTS 2 BTS 3

FU1 FU3 FU4 FU5 FU6


FU2
b ) C o n fig u r a tio n n ° 1 F A 1

M ig r a tio n fr o m F A 2 to F A 1

In case of odd number of FU for BTS j , the following BTS on the multidrop are impacted
when migrating from FA2 to FA1.
4.4 Transition from one rule to another

In order to allow operator to come back to the previous situation (operator error case) all
possible transitions are allowed.

F
H
From /To Closed C (CC) Full Allocation Decreasing A. Star

Ð Ð Ð
CC Reshuffling Reshuffling Reshuffling
Q1 TS0 TS16/18 Q1 TS0 TS1 Q1 TS0 TS0/19

ÐTS0 Ð Ð
FA Reshuffling Reshuffling Reshuffling
1AA 00014 0004 (9007)A4

Q1 TS16/18 Q1 TS16/18 TS1 Q1 TS16/18 TS0/19

Ed 03 Released

TD 3BK 10204 0335 DTZZA 20/25


Ð Ð Ð
DA Reshuffling Reshuffling Reshuffling
Q1 TS1 TS0 Q1 TS1 TS16/18 Q1 TS1 TS0/19

Ð Ð ÐTS1
Star Reshuffling Reshuffling Reshuffling
Q1 TS0/19 TS0 Q1 TS0/19 TS16/18 Q1 TS0/19
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

4.5 Summary of CMA R4 Mapping Rules

max TS ALLOCATION
Abis NAME BTS Q.1 COMMENT
Topology TS
POLICY TS R+S
(internal) bits
Chain Ring TSO Transparency
X X Full Allocation 28 Pre-configured 18 or 31+17 or
2 variants 16 31+15
depending BTS
number
2 sub_variants in
BSCG1, depending
FU/TCU ratio
X Decreasing Alloc. 30 strict dependence 1 - Unused TS grouped on
on phys. BTS TS X..31.
sequence.
TSO Usage
X X Closed catalog 30 Pre-configured, six 0 31 or 19 Fits in well with
different BTS/TRE +0 external cross-con.
combinations
TSO Usage or Transparency
X Star Mapping 25 Fixed mapping, 0 or -
PCM link with only 19 No chain nor loop cap.
one BTS.

Table 9 : CMA R4 Mapping rules

4.6 Support of new features

NAME Compatible Static


with 16 Kb/s RSL SECTORISED
(internal) G1 BSC sub- SITE
G1 BTS multiplexing

Full Allocation YES NO YES


Decreasing alloc. YES YES YES
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 21/25


All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization
1AA 00014 0004 (9007)A4
TD
Ed

Star Mapping
Closed catalog
Chain
03

Table 10 : Supported features/Mapping rules

YES
YES
Released

NO
NO
3BK 10204 0335 DTZZA

YES
NO
22/25
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization
1AA 00014 0004 (9007)A4
TD
Ed
03

Closed Catalogue STAR Mapping Decreasing Allocation TSO Transparency


Full Allocation

TSO Usage TSO Usage TSO


TSO Ring
Transparency
(Only BTS G1) Transparency

Ring Chain

Chain Type 1 (1 to 4 BTS) Type 2 (5 to 7 BTS)

1*8 TRX 1*5+1*4 1*4+1*3+1*2 4 *2 3 *3 TRX


3 *3 TRX

TS0 Q+S TS0 Q+S TS0 Q+S TS0 Q+S TS0 Q+S TS0 Qmux TS0 Qmux TS0 TS0 TS0 TS0
TS1 Qmux
See section See section
3.2 3.1 for detail TS BTS n
See section See section See section See section fordetail See section TS17 S bits TS15 S bits
See section TS18 Qmux TS16 Qmux
3.2 3.2 3.2 3.2 3.2
3.1 for detail TS BTS n -1
for detail for detail for detail for detail TS19 R bits for detail TS19 Qmux

.... TS31 R byte TS31 R byte


(SFR)
Released

TS BTS 1
TS31 R bits TS31 R bits TS31 R bits TS31 R bits
3BK 10204 0335 DTZZA

R4 Mapping Rules
23/25
5. IMPACTS
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization

5.1 HW/FW/SW impacts

OMC BSC BTS TSC TRANS TOOLS


equipment
OMU others Alcatel Alcatel NCS
X
(SW)

6 GLOSSARY
BSC Base Station Controller
BSS Base Station Sub-system
BTS Base Transceiver Station
CMA Configuration Management Applications
F bits (*) RAI bits not in TS0
FR Full Rate

HR Half Rate
OML (*) Operation & Maintenance Link
SECTORISED SITE Optimised Sectorised Site Configuration (1 BTS for several cells).

PCM (*) Pulse Code Modulation


Q bits (*) Q mux bits
Q mux named Q1) Bus for the configuration/supervision of the transmission equipments
R bits (*) Ring control bits
RAI (*) Remote Alarm Indication
RSL (*) Radio Signalling Link
S bits (*) Bits to choice of the clock Synchronisation side in a ring
SMBI SubMultiplexer Base Interface board.

TCH (*) Traffic CHannel


TS (*) Time Slot in a 2048 kbit/s i.e. 64 kbit/s
TSC Transcoder Submultiplexer Controller
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 24/25


DOCUMENT DISTRIBUTION LIST
For the document: TECHNICAL FEATURE DESCRIPTION
All rights reserved. Passing on and copying of this
document, use and communication of its contents

Abis mapping : Timeslot allocation


not permitted without written authorization

Reference: 3BK 10204 0335 DRZZA


DOC CENTRES

MCD/TD MCD/TD/BDC_A MCD/TD_S


B. Marliac L. Van Eyck I.Lentzsch
STANDARD DISTRIBUTION
MCD/TD (cont.) MCD/TD/BDC_A
R. Dupuis M.Roelandts
P. Dupuy M. Sabbe
D. Le

JF. Maillard
A. Pech
JP. Poirault
M. Tuchendler
E. Vigne
ADDITIONAL DISTRIBUTION
MCD MCD/TD/BDC_A MCD/TD_B
F. Cadorel . .

MCD/TD/BDC_C MCD/TD_S
MCD/TD
. R. Kreis
E. Amblard
O. Strumberg
M. Jaouen
M. Robert
G. Dael
A. Wasnieswski

END OF DOCUMENT
1AA 00014 0004 (9007)A4

Ed 03 Released

TD 3BK 10204 0335 DTZZA 25/25

You might also like