abis mapping

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

TECHNICAL FEATURE DESCRIPTIONAbis mapping : Timeslot allocation

Ed 03 Released

TD 3BK 10204 0335 DTZZA 1/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

TECHNICAL FEATURE DESCRIPTION

Abis mapping : Timeslot allocation

Is there a corresponding Marketing feature?

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

No Ð

AUTHORRegis DUPUIS

Ed 03 Released

TD 3BK 10204 0335 DTZZA 2/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

Table of Contents

LIST OF TABLES __________________________________________________________ 3

LIST OF FIGURES _________________________________________________________ 3

HISTORY _________________________________________________________________ 3

TYPE_____________________________________________________________________ 4

RELATED DOCUMENTS ___________________________________________________ 4

PREFACE_________________________________________________________________ 4

1. DEFINITIONS___________________________________________________________ 51.1 Abis Interface _____________________________________________________________________51.2 Abis Network Topology_____________________________________________________________51.3 Abis Traffic _______________________________________________________________________6

1.3.1 Qmux bus channel ______________________________________________________________61.3.2 Ring Control Channels __________________________________________________________61.3.3 BTS Channels _________________________________________________________________7

2. TECHNICAL DESCRIPTION ______________________________________________ 82.1 Reasons of Timeslot allocation rules definition ___________________________________________8

2.1.1 Equipment constraints ___________________________________________________________82.1.2 2.048 kbit/s links suppliers constraints _____________________________________________92.1.3 Installation, maintenance constraints _______________________________________________92.1.4 The current situation and relative rules ____________________________________________102.1.5 Service impact ,the System outage ________________________________________________102.1.6 R4 Features Introduction ________________________________________________________10

3 R3 RULES ______________________________________________________________ 123.1 Star Mapping ____________________________________________________________________123.2 Closed catalogue __________________________________________________________________133.3 Open catalogue ___________________________________________________________________14

3.3.1 Decreasing allocation __________________________________________________________143.3.2 Full allocation ________________________________________________________________15

3.4 Summary of CMA R3 Mapping rules__________________________________________________17

4 R4 RULES ______________________________________________________________ 184.1 Star Mapping_____________________________________________________________________184.2 Closed catalogue __________________________________________________________________184.3 Open catalogue ___________________________________________________________________18

4.3.1 Decreasing Allocation __________________________________________________________184.3.2 Full Allocation________________________________________________________________20

4.4 Transition from one rule to another ___________________________________________________204.5 Summary of CMA R4 Mapping Rules _________________________________________________214.6 Support of new features_____________________________________________________________21

5. IMPACTS ______________________________________________________________ 245.1 HW/FW/SW impacts_______________________________________________________________24

6 GLOSSARY _____________________________________________________________ 24

Ed 03 Released

TD 3BK 10204 0335 DTZZA 3/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

LIST OF TABLES

Table 1 : Equipment versus Abis topology _______________________________________________________8Table 2 : Service bytes versus Equipment Generation _____________________________________________9Table 3 : Timeslot budget versus Abis topology/TSO Option ________________________________________9Table 4 : Number of Timeslot versus RSL option_________________________________________________10Table 5 : Relation between sectors and number of FU’s. __________________________________________11Table 6 : BTS allocation versus FU number with FA1 rule_________________________________________17Table 7 : BTS Allocation versus FU number with FA2 rule ________________________________________17Table 8 : CMA R3 Mapping rules ____________________________________________________________18Table 9 : CMA R4 Mapping rules ____________________________________________________________21Table 10 : Supported features/Mapping rules ___________________________________________________22

LIST OF FIGURES

Figure 1 : Abis Network Topologies____________________________________________________________5Figure 2 : Use of Intermediate Transmission Networks ____________________________________________7Figure 3 : The Star mappings________________________________________________________________12Figure 4 : The Closed catalogues configurations ________________________________________________13Figure 5 : A example of Decreasing allocation mapping __________________________________________15Figure 6 : The Full Allocation Configurations __________________________________________________15Figure 7 : An example of R4 Decreasing Allocation mapping ______________________________________20

HISTORY

19/02/96 ED:01P 01

B. Genet Document creation

06/03/96 ED:01P02

B. Genet Following meeting 29/02/96 and received informations fromCMA/Toscana.The main changes concern : - a simplification of the generalallocation rules but reconfiguration constraints are no moresupported - Nokia multidrop equipments restrictions in TS0transparency taken in account.

2/04/96 ED:01P03

B. Genet Following written remarks : - correction for the Nokia constraintonly for R bits. - suppression of the BSC G1 upgraded.

14/6/96 ED:01Stable1

B. Genet Following Prereview 10/5/96 See meeting report reference 1

26/7/96 ED:01Release

B. Genet Following Review 2/7/96 See meeting report reference 1

ED:02P01

R.Dupuis Following new proposal : Definition of the Free mapping rule

13/06/97 Ed 02Released

R.Dupuis Following Review Meeting on Ed 2 P01 : SAS/ea/0694.97(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 stilloffered 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

Ed 03 Released

TD 3BK 10204 0335 DTZZA 4/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

TYPE

Linked to a Marketing FeatureDescriptionTechnical improvement withoutMarketing impact

X

RELATED DOCUMENTS

[1] Technical feature description Abis signalling linksmultiplexing scheme16 kbit/s static sub multiplex

3BK 10204 0100 DRZZA

[2] Technical feature description Abis signalling linkstatistical submultiplexing O&M aspects

3BK 11204 0316 DRZZA

[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 evaluatethe relevancy of such choices.

We are going first to give some definitions and recall the different aspect of the Abis interfacewe have to take into account.We will then give the list of concerned equipment and calculate the Timeslot budget in regardto 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.

Ed 03 Released

TD 3BK 10204 0335 DTZZA 5/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

1. DEFINITIONS

1.1 Abis Interface

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 256bits grouped in 32 timeslots numbered from 0 to 31.The 8 bits of each timeslot are numberedfrom 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 fornational 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 tothe BSC.

b ) R in g T o po lo g y

a ) C h a in T o p o log y

B S C

B T S

B T S

B T S

A b is link

A bis lin kA b is lin k

B S C

B T S

B T S

B T S

A b is lin k

A b is lin kA b is lin k

A b is lin k

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) : Seenext section.

Note : For historical reasons NOKIA defined also a Star topology (particular case of a chainwith one BTS).

Ed 03 Released

TD 3BK 10204 0335 DTZZA 6/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

1.3 Abis Traffic

There are three categories of channels to be mapped onto the transmission links:

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

� Ring control channels used by the transmission equipments independently from thetransmission O&M controller (TSC).

�BTS channels

1.3.1 Qmux bus channel

The Transmission part of the Network Elements are configured and supervised from aCentralised 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 eachBTS 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 synchronisationsignal. These two bits can either be conveyed in any TS (from 0 to 31).

Current value TS0 (NFAS) TS1 to TS31MCB bit Bit 4 Bit 5LCB 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 beused 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 reportingpurposes. They would have given an information to the remote end in case of failure within theITN.This would have been particularly useful in Ring configuration to be informed that one ofthe two paths is in failure. (there is no other meaning to be awarded of this situation)

Current value TS1 TS16 ou 18

Ed 03 Released

TD 3BK 10204 0335 DTZZA 7/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

MCB bit Bit 3,4 Bit 7,8F bits are not used in R4 due to buggy implementation in NOKIA Hardware.

A b i s A b i s

6 4 k b i t / s C r o s s - C o n n e c t si . e T r a n s m i c N e t w o r k

A I S 2 M b i t / s

A I S 6 4 k b i t / so n G S M T r a f fi c

I n c a s e o f f a i l u r e w i t h in th e I T N , t h e F b i t s a r e s e t t o “ 1 ” d u e to th e 6 4 k b i t / s A I S in a l l “ G S M ” t im e s lo ts .T h i s a l e r t s th e B T S o f a f a i l u r e w i th in th e I T N . R e f e r ( 3 ) a n d ( 5 ) f o r d e ta i l c o n c e r n in g r e la te d r e a c t i o n s

B S C B T S

I T N

R A I

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 in16 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.

Ed 03 Released

TD 3BK 10204 0335 DTZZA 8/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

2. TECHNICAL DESCRIPTION

Note : In the following , one has to consider that TS number for any timeslotexchanged between BTS and BSC is same for both sides.

2.1 Reasons of Timeslot allocation rules definition

We have listed in the following the different aspects to take into account and the reasonsleading 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 orgeneration.

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

Equipments and “originator”

Board name Abis topology supported

BTS G1 (Nokia) SMHW (*) Chain (only one BTS)DB2M,DX2M Chain ,Ring

G2 (Alcatel) SMBI Chain,RingMicro (Alcatel) SMFG Chain,RingG3 (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.

Ed 03 Released

TD 3BK 10204 0335 DTZZA 9/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

The second table gives the Service bits/bytes constraints (in term of location in the frame)versus the equipment originator

TS0 Usage TS0 TransparencyServicebits/bytes

Qmux R byte S Bits Qmux R byte S Bits

Nokia(G1)

TS0 Any TS(1 to 31)

TS0 Any TS(1 to 31)

Any TS (1 to 31) ≠ Qmux TS

Any TS (1 to 31)≠ Qmux TS and ≠ R byte TS

Alcatel(G2,..)

TS0 Any TS(1 to 31)

TS0 Any TS (1 to 31)

Any TS (1 to 31) ≠ Qmux TS

Any TS (1 to 31) 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 channelsTS0 Usage TS0 Transparency

Chain 31 30Mix 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 AlcatelEquipment constraints)(2) “Full Alcatel” : Supporting only Alcatel Equipments (See 2.1.1.1 Alcatel Equipmentconstraints)

2.1.1.2 External Equipment constraintsAs already mentionned Intermediate transmission networks can be used on Abis interfaceSome 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 linesService (supported on Transmic Network) offer N*64 kbit/s transportation: the N timeslotsbeing 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 incase this could not be achieved with a back up database. (Considering our tools , thisconstraint has not been retained)

Ed 03 Released

TD 3BK 10204 0335 DTZZA 10/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

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

2.1.4 The current situation and relative rules

Introduction of a new rule could have a big impact on already installed networks :i.e in case ofchange 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 tosite 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 Qmuxlocation. It is not possible in same time to modify the Qmux location and use the Qmux bus toexchange 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 selectedrule, 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 ofneeded timeslots for a same BTS traffic and then the number of public PCM links requiredover the Abis interface.The RSL is carried on 16 kbit/s channel instead of 64 kbit/s channel. Up to four RSL of a sameBTS 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 agiven configuration.

Timeslot needed for BTS channelsRSL 64 kbit/s RSL 16kbit/s

OML TCH RSL Total RSL Total1 TRX 1 2 1 4 1 42 TRX 1 4 2 7 1 63 TRX 1 6 3 10 1 84 TRX 1 8 4 13 1 105 TRX 1 10 5 16 2 136 TRX 1 12 6 19 2 157 TRX 1 14 7 22 2 178 TRX 1 16 8 25 2 19

Table 4 : Number of Timeslot versus RSL option

Ed 03 Released

TD 3BK 10204 0335 DTZZA 11/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

2.1.6.2 Sectorized Site BTS

Refering (6) :

Several configurations are offered with EVOLIUM TM BTS : up to 3 sectors with a totalnumber 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.

Ed 03 Released

TD 3BK 10204 0335 DTZZA 12/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

3 R3 RULES

The following mapping rules have been defined in Release 3.

3.1 Star Mapping

TS TS0 Usage TS TSO Transparency0 Q mux 01 FU1 1 FU12 FU1 2 FU13 FU5 3 FU54 FU5 4 FU55 FU2 5 FU26 FU2 6 FU27 FU6 7 FU68 FU6 8 FU69 FU3 9 FU310 FU3 10 FU311 FU7 11 FU712 FU7 12 FU713 FU4 13 FU414 FU4 14 FU415 FU8 15 FU816 FU8 16 FU817 1718 1819 19 Q mux20 2021 21 OML22 RSL8 22 RSL823 RSL7 23 RSL724 RSL6 24 RSL625 RSL5 25 RSL526 2627 RSL4 27 RSL428 RSL3 28 RSL329 RSL2 29 RSL230 RSL1 30 RSL131 OML 31

Figure 3 : The Star mappings

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

Ed 03 Released

TD 3BK 10204 0335 DTZZA 13/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

3.2 Closed catalogue

The Qmux channel is always conveyed on TS0.(TS0 Usage)The closed catalogue includes a list of PCM TS mapping descriptions corresponding to alimited 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 canaccomodate is defined in each case. The actual number of equipped BTS or TRE isconfigurable within these limits, but the maximum transmission capacity is always reserved inadvance.

_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 oneexception (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 relationbetween this name which determines the mapping and the physical position of the BTS on thelink.

Qmux + Sbits

FU 1

FU 5

FU 2

FU 6

FU 3

FU 7

FU 4

FU 8

RSL 8765

OMLRSL 4

321

R bits

1 BTS x 8 TRE 1x5 + 1x4 1x4 + 1x3 + 1x2 4 BTS X 2 TRE

Rbits

3 BTS x 3 TRE 3 x 3 SFR

1

5678

10

15

20

25

30

0 Qmux + Sbits Qmux + Sbits Qmux + Sbits Qmux + Sbits Qmux

234

9

FU 1 - a

FU 1 - b

FU 2 - a

FU 2 - b

FU 3 - a

FU 3 - b

FU 4 - a

FU 4 - b

FU 5 - a18

OML aRSL 4 - a

32

RSL 1 - a R bits

OML bRSL 4 - b

32

RSL 1 - b

RSL 5 - a

FU 1 - c

FU 3 - c

FU 2 - c

FU 4 - a

FU 3 - a

R bits

RSL 2 - aRSL 1 - a

RSL 2 - cRSL 1 - c

RSL 3 - a

RSL 2 - bRSL 1 - b

RSL 3 - c OML 1 OML c OML b

RSL 4 - a

FU 1 - a

FU 1 - b

FU 2 - a

FU 2 - b

FU 1 - c

FU 1 - d

FU 2 - c

FU 2 - d

R bits

RSL 2 - aRSL 1 - a

RSL 2 - cRSL 1 - c

OML a

RSL 2 - bRSL 1 - b

RSL 2 - dRSL 1 - d

OML c OML b OML d

FU 1 - a

FU 1 - b

FU 2 - a

FU 2 - b

FU 1 - c

FU 3 - c

FU 2 - c

FU 3 - b

FU 3 - a

OML a

RSL 2 - aRSL 1 - a

RSL 3 - aRSL 2 - cRSL 1 - c

RSL 2 - bRSL 1 - b

RSL 3 - cRSL 3 - b

OML c OML b

OML a

FU 1 - aRSL 1 - a

FU 2 - aRSL 2 - a

FU 3 - aRSL 3 - a

OML b

FU 1 - bRSL 1 - b

FU 2 - bRSL 2 - b

FU 3 - bRSL 3 - b

OML c

FU 1 - cRSL 1 - c

FU 2 - cRSL 2 - c

FU 3 - cRSL 3 - c

FU 1 - a

FU 1 - b

FU 2 - a

FU 2 - b

Figure 4 : The Closed catalogues configurations

Ed 03 Released

TD 3BK 10204 0335 DTZZA 14/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

3.3 Open catalogue

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

The supported multidrop link configurations in terms of BTS and TRE are not enlisted inadvance. A rule is defined (there are several different rules) to map the BTS channels onto thePCM 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 acomplete reshuffling of the mapping : disturbance on all BTS on the chain.

On all segments of the chain, the BTS channelsare grouped on a per BTS basis. The blocks ofBTS channels are contiguous. Within a blockthe OML/RSL and TRE channels arecontiguous. The first block on a PCM link(smallest TS numbers) corresponds to the lastphysical position on the multidrop link.

B S CB T S 1 B T S 2 B T S n

A b i s 1 A b i s nA b i s 2

TS0 0 01 Q mux 1 Q mux 1 Q mux2 OML n 2 OML n 2 OML n3 FU 1 BTS n 3 FU 1 BTS n 3 FU 1 BTS n4 FU 1 BTS n 4 FU 1 BTS n 4 FU 1 BTS n5 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 nFU m BTS n FU m BTS n FU m BTS nRSL m BTS n RSL m BTS n RSL m BTS n... ... ...OML 2 OML 2FU 1 BTS 2 FU 1 BTS 2FU 1 BTS 2 FU 1 BTS 2RSL 1 BTS 2 BTS 2 RSL 1 BTS 2 .. ..FU p BTS 2 FU p BTS 2FU p BTS 2 FU p BTS 2RSL p BTS 2 RSL p BTS 2OML 1FU 1 BTS 1FU 1 BTS 1RSL 1 BTS 1 BTS 1 ..FU k BTS 1FU k BTS 1RSL k BTS 1

31 31 31

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

Ed 03 Released

TD 3BK 10204 0335 DTZZA 15/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

Figure 5 : A example of Decreasing allocation mapping

3.3.2 Full allocation

Full Allocation occupies at every segment of an Abis path the same amount of TS’s but is openfor every dimensioning concerning BTS’s and FU’s.The numbering of FU’s and RSL’s is notrelated 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 or7, 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 RSLand OML links between the TS used by the Q-bits / S-bits and TS 30.

TS 1...4 BTS TS 5...7 BTS0 01 FU 1 1 FU 12 FU 1 2 FU 13 FU 5 3 FU 54 FU 5 4 FU 55 FU 2 5 FU 26 FU 2 6 FU 27 FU 6 7 FU 68 FU 6 8 FU 69 FU 3 9 FU 3

10 FU 3 10 FU 311 FU 7 11 FU 712 FU 7 12 FU 713 FU 4 13 FU 414 FU 4 14 FU 415 FU 8 15 S bits16 FU 8 16 Q bits17 S bits 17 OML 718 Q bits 18 OML 619 RSL 8 19 OML 520 RSL 7 20 RSL 721 RSL 6 21 RSL 622 RSL 5 22 RSL 523 RSL 4 23 RSL 424 RSL 3 24 RSL 325 RSL 2 25 RSL 226 RSL 1 26 RSL 127 OML 4 27 OML 428 OML 3 28 OML 329 OML 2 29 OML 230 OML 1 30 OML 131 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.With FA2 rule, the reservation is systematically made for a couple of FU’s.

Ed 03 Released

TD 3BK 10204 0335 DTZZA 16/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

: reservation of FUi and FU i+1 locations (with i=1, 3, 5 or 7).

3.3.2.1Ring Type 1 FA1 applicationThe allocated timeslots of a FU number k of BTS(j) are those corresponding to FU(m) (in FA1rule) 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)

R in g T y p e 1 F A 1

B S C B T S 1 B T S 3B T S 2

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

B T S 4

A b is link

F U 1 F U 5 F U 6F U 4F U 3F U 2


A b is link A bi s lin kA b is lin k

B T S 4

A bi s lin k

F U 1 F U 2 F U 7F U 5F U 4F U 3 F U 8

b ) E xte n s ion o f on e F U in B T S 1 an d 1 F U in B T S 3

a ) C on fig ura tio n n ° 1

F U 6

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

Thus the corresponding allocation timeslot for the 2 configurations is :

BTS 1 BTS 2 BTS 3 BTS 4FU1 FU2 FU3 FU4 FU5 FU6

Config. n° 1TCH TS 1, 2 5, 6 9, 10 13, 14 3, 4 7, 8

RSL TS 26 25 24 23 22 21

ExtensionFU1 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 FU8Conf n°1 BTS1 BTS2 BTS3 BTS4 Not

usedNotused

Ed 03 Released

TD 3BK 10204 0335 DTZZA 17/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

Extens. BTS1 BTS2 BTS3 BTS4

Table 6 : BTS allocation versus FU number with FA1 rule

3.3.2.2 Ring Type 1 FA2 applicationIn 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) (inFA2 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.

R i n g T y p e 1 F A 2


A b i s l in k A b i s l in kA b i s l i n k

B T S 4

A b i s l i n k

F U 1 F U 6 F U 7F U 5F U 4F U 3


A b i s l i n k A b i s l i n kA b i s l in k

B T S 4

A b i s l i n k

F U 1 F U 2 F U 5F U 4F U 3 F U 7

b ) E x t e n s i o n o f O N L Y o n e F U i n B T S 1

a ) C o n f i g u r a t i o n n ° 1

F U 6

In the given example, we see that thank to allocation per couple of FU, extension of one FU onthe BTS 1 does not impact the allocation of the following ones BUT in contrario it is notpossible to add a TRE to BTS3.Thus the corresponding allocation timeslot for the 2 configurations is :

BTS 1 BTS 2 BTS 3 BTS 4Configuration 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 FU8Conf n°1 BTS1 Reserved BTS2 BTS3 BTS4 ReservedExtens. 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 MappingsTS0 Usage TS0 Transparency

Ed 03 Released

TD 3BK 10204 0335 DTZZA 18/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

Chain Star MappingClosed catalogue

Star MappingOpen catalogue : Decreasing or Full allocation

Ring Closed catalogue Open catalogue : Full allocation

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 tothe fixed numbering of the TRE some configurations are not possible : i.e the 3 *4 TRX Configunderequipped to 3*2 TRX (TRX number = 1,2,5,6,9,10) cannot fit with the 1BTS*8TRXconfiguration.

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. Insame 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 19/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

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)

TS

0

1 QMux QMux

2 OML2 OML2

3 FU1 BTS 2 FU1 BTS 2


5 RSL1 RSL2 RSL3 RSL4 RSL1 RSL3 RSL5





10 FU4 BTS 2 OML111 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 witha BTS*8 TRX RSL 16kbit/s a SSC 3*1 TRX RSL 16kbit/s

Ed 03 Released

TD 3BK 10204 0335 DTZZA 20/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

Figure 7 : An example of R4 Decreasing Allocation mapping

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 FA1The FA2 configuration is not supported in BSCG2.This removal implies to change from FA2 to FA1 the configuration of PCM connected to BSCG2 when migrating from B3 to B4.

M ig r a t io n f r o m F A 2 t o F A 1

F U 2b ) C o n f ig u r a t io n n ° 1 F A 1

a ) C o n f ig u r a t io n n ° 1 F A 2


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

F U 1 F U 3 F U 6F U 5F U 4


A b is l in k A b is l in kA b is l in k

F U 1 F U 3 F U 7F U 6F U 5

F U 2

In case of odd number of FU for BTS j , the following BTS on the multidrop are impactedwhen 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) allpossible transitions are allowed.

From /To FH

Closed C (CC) Full Allocation Decreasing A. Star

CC ReshufflingQ1 TS0 ÐTS16/18

ReshufflingQ1 TS0 ÐTS1

ReshufflingQ1 TS0ÐTS0/19

FA ReshufflingQ1 TS16/18 ÐTS0

ReshufflingQ1 TS16/18 ÐTS1

ReshufflingQ1 TS16/18 ÐTS0/19

Ed 03 Released

TD 3BK 10204 0335 DTZZA 21/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

DA ReshufflingQ1 TS1 ÐTS0



Star ReshufflingQ1 TS0/19 ÐTS0

ReshufflingQ1 TS0/19 ÐTS16/18

ReshufflingQ1 TS0/19 ÐTS1

4.5 Summary of CMA R4 Mapping Rules

AbisTopology

NAME

(internal)

maxBTSTS

TS ALLOCATIONPOLICY

Q.1TS R+S

bits

COMMENT

Chain Ring TSO TransparencyX X Full Allocation 28 Pre-configured

2 variantsdepending BTS

number2 sub_variants in

BSCG1, dependingFU/TCU ratio

18 or16

31+17 or31+15

X Decreasing Alloc. 30 strict dependenceon phys. BTSsequence.

1 - Unused TS grouped onTS X..31.

TSO Usage

X X Closed catalog 30 Pre-configured, sixdifferent BTS/TREcombinations

0 31 or 19+ 0

Fits in well with external cross-con.

TSO Usage or Transparency

X Star Mapping 25 Fixed mapping,PCM link with onlyone BTS.

0 or19

-No chain nor loop cap.

Table 9 : CMA R4 Mapping rules

4.6 Support of new features

NAME

(internal)

Compatiblewith

G1 BSCG1 BTS

Static16 Kb/s RSL

sub-multiplexing

SECTORISEDSITE

Full Allocation YES NO YES

Decreasing alloc. YES YES YES

Ed

03R

eleased

TD

3BK

10204 0335 DT

ZZ

A22/25

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

not permitted without written authorization1AA 00014 0004 (9007)A4

Chain

Closed catalog

YE

SN

OY

ES

Star Mapping

YE

SN

ON

O

Tab

le 10 : Su

pp

orted

features/M

app

ing

rules

Ed

03R

eleased

TD

3BK

10204 0335 DT

ZZ

A23/25

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

not permitted without written authorization1AA 00014 0004 (9007)A4

Full Allocation TSO Transparency

Ring

TS0

TS17 S bits TS18 Qmux

TS31 R byte

TS0

TS15 S bits TS16 Qmux

TS31 R byte

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

STAR Mapping

TSO

Transparency

TS0 Qmux

See section

3.1 for detail

TS0

See section

3.1 for detail

TS19 Qmux

Decreasing Allocation

TSO

Transparency

TS0

TS1 Qmux

TS BTS n

TS BTS n -1

TS BTS 1

....

TSO Usage

(Only BTS G1)

Chain

R4 Mapping Rules

Closed Catalogue

TSO Usage

Ring

(SFR)

Chain

TS0 Q+S

TS31 R bits

See section

3.2

for detail

1*8 TRX

TS0 Q+S

TS31 R bits

See section

3.2

for detail

1*4+1*3+1*2

TS0 Q+S

TS31 R bits

See section

3.2

for detail

4 *2

TS0 Q+S

TS19 R bits

See section

3.2

fordetail

3 *3 TRX

TS0 Q+S

TS31 R bits

See section

3.2

for detail

1*5+1*4

TS0 Qmux

See section

3.2

for detail

3 *3 TRX

Ed 03 Released

TD 3BK 10204 0335 DTZZA 24/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

5. IMPACTS

5.1 HW/FW/SW impacts

OMC BSC BTS TSC TRANSequipment

TOOLS

OMU others Alcatel Alcatel NCS

X(SW)

6 GLOSSARY

BSC Base Station ControllerBSS Base Station Sub-systemBTS Base Transceiver StationCMA Configuration Management ApplicationsF bits (*) RAI bits not in TS0FR Full Rate

HR Half RateOML (*) Operation & Maintenance LinkSECTORISED SITE Optimised Sectorised Site Configuration (1 BTS for several cells).

PCM (*) Pulse Code ModulationQ bits (*) Q mux bitsQ mux named Q1) Bus for the configuration/supervision of the transmission equipmentsR bits (*) Ring control bitsRAI (*) Remote Alarm IndicationRSL (*) Radio Signalling LinkS bits (*) Bits to choice of the clock Synchronisation side in a ringSMBI SubMultiplexer Base Interface board.

TCH (*) Traffic CHannelTS (*) Time Slot in a 2048 kbit/s i.e. 64 kbit/sTSC Transcoder Submultiplexer Controller

Ed 03 Released

TD 3BK 10204 0335 DTZZA 25/25

All

right

s re

serv

ed. P

assi

ng o

n an

d co

pyin

g of

this

do

cum

ent,

use

and

com

mun

icat

ion

of it

s co

nten

ts

notp

erm

itted

with

outw

ritte

nau

thor

izat

ion

1AA

000

14 0

004

(900

7)A

4

DOCUMENT DISTRIBUTION LISTFor the document: TECHNICAL FEATURE DESCRIPTION

Abis mapping : Timeslot allocation

Reference: 3BK 10204 0335 DRZZADOC CENTRES

MCD/TD

B. Marliac

MCD/TD/BDC_A

L. Van Eyck

MCD/TD_S

I.Lentzsch

STANDARD DISTRIBUTION

MCD/TD (cont.)

R. DupuisP. DupuyD. Le

JF. MaillardA. PechJP. PoiraultM. TuchendlerE. Vigne

MCD/TD/BDC_A

M.Roelandts

M. Sabbe

ADDITIONAL DISTRIBUTION

MCD

F. Cadorel

MCD/TD

E. AmblardM. JaouenM. RobertG. DaelA. Wasnieswski

MCD/TD/BDC_A

.

MCD/TD/BDC_C

.

MCD/TD_B

.

MCD/TD_S

R. KreisO. Strumberg

END OF DOCUMENT

abis mapping

Documents