Abis Mapping

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

TECHNICAL FEATURE DESCRIPTION

Abis mapping : Timeslot allocation

Is there a corresponding Marketing feature?

YES No

Ð Ð

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

1AA 00014 0004 (9007)A4

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.

Ed

Date

Distribution List

Validation

Validation

Ed

TD

03

Product Mng. Validation

Approval

TECHNICAL FEATURE DESCRIPTION Abis mapping : Timeslot allocation Released 3BK 10204 0335 DTZZA

1/25

Table of Contents


LIST OF TABLES __________________________________________________________ 3 LIST OF FIGURES _________________________________________________________ 3 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

1AA 00014 0004 (9007)A4

6 GLOSSARY _____________________________________________________________ 24

Ed

TD

03

Released 3BK 10204 0335 DTZZA

2/25

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

Table 1 : Equipment versus Abis topology _______________________________________________________8 Table 2 : Service bytes versus Equipment Generation _____________________________________________9 Table 3 : Timeslot budget versus Abis topology/TSO Option ________________________________________9 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 P 01 ED:01 P02

B. Genet

Document creation

B. Genet

B. Genet B. Genet B. Genet

Following Review 2/7/96 See meeting report reference 1

R.Dupuis

Following new proposal : Definition of the Free mapping rule

16/12/97

ED:01 P03 ED:01 Stable1 ED:01 Release ED:02 P01 Ed 02 Released Ed 03 P1

Following meeting 29/02/96 and received informations from 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. Following written remarks : - correction for the Nokia constraint only for R bits. - suppression of the BSC G1 upgraded. Following Prereview 10/5/96 See meeting report reference 1

22/12/97

Ed 03 P2

13/02/98

Ed 03 Rl

06/03/96

2/04/96 14/6/96 26/7/96

1AA 00014 0004 (9007)A4

13/06/97

Ed

TD

03

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) R.Dupuis Free mapping rule postponed in Release B5. Full Allocation still offered in B4. R.Dupuis Following comments on P1 from E.Amblard and G.DAEL (CO_F) R.Dupuis Following E_mail review TD/SAS/rdu/259.98/ED1


3/25


TYPE Linked to a Marketing Description Technical improvement Marketing impact

Feature without

X

RELATED DOCUMENTS [1] [2] [3] [4] [5] [6]

Technical feature description Abis signalling links multiplexing scheme16kbit/s static sub multiplex Technical feature description Abis signalling link statistical submultiplexing O&M aspects Transmission architecture specification (Release 4) MFD 8.1 Abis signalling multiplexing schemes Transmission Functional Specification Engineering rules and configurations of the G3 BTS

3BK 10204 0100 DRZZA 3BK 11204 0316 DRZZA

3BK 11200 0003 DTZZA 3BK 10203 0100 DRZZA 3BK 11203 0015 DSZZA 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

1AA 00014 0004 (9007)A4

We will then describe the rules offered in R3 and those offered in R4.

Ed

TD

03


4/25


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

A b is lin k

BTS

A b i s lin k

BTS BSC A b is lin k

BTS

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

A b is lin k

BTS

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

1AA 00014 0004 (9007)A4

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 with one BTS).

Ed

TD

03


5/25

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

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 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 MCB bit LCB bit

TS0 (NFAS) Bit 4 Bit 5

TS1 to TS31 Bit 5 Bit 6

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

1AA 00014 0004 (9007)A4

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) Current value

Ed

TD

03

TS1

TS16 ou 18


6/25

MCB bit

Bit 3,4

Bit 7,8

F bits are not used in R4 due to buggy implementation in NOKIA Hardware. All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization

A b is

A b is

IT N

A I S 2 M b it/s BSC

BTS RAI

A IS 6 4 k b it/s 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

1AA 00014 0004 (9007)A4

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

TD

03


7/25

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

Note : In the following , one has to consider that TS number for any timeslot exchanged 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 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.

BTS

Equipments and “originator” G1 (Nokia)

BSC

G2 (Alcatel) Micro (Alcatel) G3 (Alcatel) BSC G1 (Nokia) BSC G2 (Alcatel)

Board name

Abis topology supported Chain (only one BTS) Chain ,Ring Chain,Ring Chain,Ring Chain,Ring Chain (only one BTS) Chain ,Ring Chain,Ring

SMHW (*) DB2M,DX2M SMBI SMFG SUMP SMHW (*) DB2M,DX2M BIUA

Table 1 : Equipment versus Abis topology

1AA 00014 0004 (9007)A4

(*) Specific Hardware that limits the capacity of the chain to one single BTS.

Ed

TD

03


8/25


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

Service bits/bytes Nokia (G1) Alcatel (G2,..)

TS0 Usage Qmux R byte S Bits

Qmux

TS0 Transparency R byte S Bits

TS0

Any TS (1 to 31)

TS0

Any TS (1 to 31)

Any TS (1 to 31) ≠ Qmux TS

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

Chain Mix G1/G2 Ring (1) “Full” Alcatel Ring (2)

Number of timeslots usable for BTS channels TS0 Usage TS0 Transparency 31 30 30 28 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.

1AA 00014 0004 (9007)A4

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 constraint has not been retained)

Ed

TD

03


9/25

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 of 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 2 TRX 3 TRX 4 TRX 5 TRX 6 TRX 7 TRX 8 TRX

1 1 1 1 1 1 1 1

2 4 6 8 10 12 14 16

1 2 3 4 5 6 7 8

1 1 1 1 2 2 2 2

4 7 10 13 16 19 22 25

4 6 8 10 13 15 17 19

1AA 00014 0004 (9007)A4

Table 4 : Number of Timeslot versus RSL option

Ed

TD

03


10/25


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.

Number of TRE/sector

1 sector

2 sectors

3 sectors

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.

1AA 00014 0004 (9007)A4

Note : It has to be noted that the RSL 16 kbit/s feature is not possible with the Half rate.

Ed

TD

03


11/25

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

The following mapping rules have been defined in Release 3. 3.1 Star Mapping

TS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

TS0 Usage Q mux FU1 FU1 FU5 FU5 FU2 FU2 FU6 FU6 FU3 FU3 FU7 FU7 FU4 FU4 FU8 FU8

RSL8 RSL7 RSL6 RSL5 RSL4 RSL3 RSL2 RSL1 OML

TS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

TSO Transparency FU1 FU1 FU5 FU5 FU2 FU2 FU6 FU6 FU3 FU3 FU7 FU7 FU4 FU4 FU8 FU8

Q mux OML RSL8 RSL7 RSL6 RSL5 RSL4 RSL3 RSL2 RSL1

Figure 3 : The Star mappings

1AA 00014 0004 (9007)A4

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

Ed

TD

03


12/25


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 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 1 2 3 4 5 6 7 8

Qmux + Sbits

Qmux + Sbits

Qmux + Sbits

Qmux + Sbits

Qmux + Sbits

Qmux

FU 1

FU 1 - a

FU 1 - a

FU 1 - a

FU 1 - a

FU 5

FU 1 - b

FU 1 - b

FU 1 - b

FU 1 - b

FU 2

FU 2 - a

FU 2 - a

FU 2 - a

FU 2 - a

FU 6

FU 2 - b

FU 2 - b

FU 2 - b

FU 2 - b

9

FU 3

FU 3 - a

FU 1 - c

FU 1 - c

FU 1 - c

FU 7

FU 3 - b

FU 3 - c

FU 1 - d

FU 3 - c

FU 4

FU 4 - a

FU 2 - c

FU 2 - c

FU 2 - c

FU 8

FU 4 - b

FU 4 - a

FU 2 - d

FU 3 - b

FU 2 - b

FU 5 - a

FU 3 - a

FU 3 - a

RSL 2 - b

RSL 5 - a OML b RSL 4 - b 3 2 RSL 1 - b OML a RSL 4 - a 3 2 RSL 1 - a R bits

RSL 4 - a OML b OML c OML 1 RSL 3 - c RSL 2 - b RSL 1 - b RSL 3 - a RSL 2 - c RSL 1 - c RSL 2 - a RSL 1 - a R bits

10

OML a

FU 1 - a RSL 1 - a

FU 2 - a RSL 2 - a

FU 3 - a RSL 3 - a OML b

FU 1 - b 15 18

1AA 00014 0004 (9007)A4

20

25

RSL 8 7 6 5

30

RSL 4 3 2 1

OML

R bits

OML d OML b OML c RSL 2 - d RSL 1 - d RSL 2 - b RSL 1 - b OML a RSL 2 - c RSL 1 - c RSL 2 - a RSL 1 - a R bits

Rbits OML b OML c RSL 3 - b RSL 3 - c RSL 2 - b RSL 1 - b RSL 3 - a RSL 2 - c RSL 1 - c RSL 2 - a RSL 1 - a OML a

RSL 1 - b

FU 3 - b RSL 3 - b OML c

FU 1 - c RSL 1 - c

FU 2 - c RSL 2 - c

FU 3 - c RSL 3 - c

Figure 4 : The Closed catalogues configurations

Ed

TD

03


13/25


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 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 BTS channels are contiguous. Within a block 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 1 2 3 4 5

Q mux OML n FU 1 BTS n FU 1 BTS n RSL 1 BTS n .. FU m BTS n FU m BTS n RSL m BTS n ... OML 2 FU 1 BTS 2 FU 1 BTS 2 RSL 1 BTS 2 .. FU p BTS 2 FU p BTS 2 RSL p BTS 2 OML 1 FU 1 BTS 1 FU 1 BTS 1 RSL 1 BTS 1 .. FU k BTS 1 FU k BTS 1 RSL k BTS 1

1AA 00014 0004 (9007)A4

31

TD

BTS 2

B T S 1

0 1 2 3 4 5

Q mux OML n FU 1 BTS n FU 1 BTS n RSL 1 BTS n .. FU m BTS n FU m BTS n RSL m BTS n ... OML 2 FU 1 BTS 2 FU 1 BTS 2 RSL 1 BTS 2 .. FU p BTS 2 FU p BTS 2 RSL p BTS 2

03

A b is n

B T S 2

B T S n

Q mux OML n FU 1 BTS n FU 1 BTS n RSL 1 BTS n .. FU m BTS n FU m BTS n RSL m BTS n ...

BTS 1

31

Mapping on Abis 1

Ed

BTS n

0 1 2 3 4 5

A b is 2

A b is 1 B S C

31

Mapping on Abis 2

Mapping on Abis n


14/25

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 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 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

1...4 BTS FU 1 FU 1 FU 5 FU 5 FU 2 FU 2 FU 6 FU 6 FU 3 FU 3 FU 7 FU 7 FU 4 FU 4 FU 8 FU 8 S bits Q bits RSL 8 RSL 7 RSL 6 RSL 5 RSL 4 RSL 3 RSL 2 RSL 1 OML 4 OML 3 OML 2 OML 1 Ring Control

Ring Type 1 (FA1 or FA2)

TS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

5...7 BTS FU 1 FU 1 FU 5 FU 5 FU 2 FU 2 FU 6 FU 6 FU 3 FU 3 FU 7 FU 7 FU 4 FU 4 S bits Q bits OML 7 OML 6 OML 5 RSL 7 RSL 6 RSL 5 RSL 4 RSL 3 RSL 2 RSL 1 OML 4 OML 3 OML 2 OML 1 Ring Control

Ring Type 2 (Only FA1)

Figure 6 : The Full Allocation Configurations

1AA 00014 0004 (9007)A4

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

TD

03


15/25


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

3.3.2.1 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

BSC

A b is lin k

BTS 1

A b is lin k

A b is lin k

BTS 2

FU1

FU2

BTS 3

FU3

FU4

BTS 4

FU5

FU6

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

A b is lin k

A b is lin k

BSC

BTS 1 FU1

FU2

A b i s lin k

A b i s lin k

BTS 2 FU3

BTS 3

FU4

BTS 4

FU5 FU7 FU6

FU8

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 Config. n° 1 TCH TS RSL TS Extension TCH TS RSL TS

1AA 00014 0004 (9007)A4

TD

03

BTS 3

BTS 4

FU2

FU3

FU4

FU5

FU6

1, 2 26

5, 6 25

9, 10 24

13, 14 23

3, 4 22

7, 8 21

FU1 1, 2 26

FU1 Conf n°1 BTS1

Ed

BTS 2

FU1

FU2 5, 6 25

FU2

FU3 BTS2

FU3 9, 10 24

FU4 13, 14 23

FU4 BTS3

FU5 3, 4 22

FU5

FU6 7, 8 21

FU6 BTS4

FU7 11,12 20

FU7 Not used

FU8 15,16 19

FU8 Not used


16/25

Extens.

BTS1

BTS2

BTS3

BTS4


Table 6 : BTS allocation versus FU number with FA1 rule

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

BSC

BTS 1

A b i s l in k

BTS 2

FU1

FU3

A b is lin k

BTS 3 FU4

FU5

BTS 4

FU6

FU7

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

A b i s l in k

BSC

A b is lin k

BTS 1 FU1

A b is lin k

BTS 2

FU2

FU3

A b is lin k

BTS 3 FU4

FU5

BTS 4 FU7

FU6

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

Configuration n° 1 TCH TS RSL TS Extension TCH TS RSL TS

BTS 2

FU1 1, 2 26 FU1 1, 2 26

FU1 FU2 Conf n°1 BTS1 Reserved Extens. BTS1

FU2 5, 6 25

BTS 3

BTS 4

FU3 9, 10 24

FU4 13, 14 23

FU5 3, 4 22

FU6 7, 8 21

FU7 11,12 20

FU3 9, 10 24

FU4 13, 14 23

FU5 3, 4 22

FU6 7, 8 21

FU7 11,12 20

FU3

FU4 BTS2 BTS2

FU5

FU6 BTS3 BTS3

FU7 BTS4 BTS4

FU8 Reserved Reserved

3BK 10204 0335 DTZZA

17/25

Table 7 : BTS Allocation versus FU number with FA2 rule

1AA 00014 0004 (9007)A4

3.4 Summary of CMA R3 Mapping rules Abis topology TS0 Usage

Ed

TD

03

Mappings TS0 Transparency

Released

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

Ring

Star Mapping Star Mapping Closed catalogue Open catalogue : Decreasing or Full allocation 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 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

1AA 00014 0004 (9007)A4

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 same way the timeslot previously allocated for the fifth RSL of a BTS carries the RSL’s of the

Ed

TD

03


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)

1AA 00014 0004 (9007)A4

TS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

RSL1

RSL5

QMux OML2 FU1 BTS 2 FU1 BTS 2 RSL2 RSL3 FU2 BTS 2 FU2 BTS 2 FU3 BTS 2 FU3 BTS 2 FU4 BTS 2 FU4 BTS 2 FU5 BTS 2 FU5 BTS 2 RSL6 RSL7 FU6 BTS 2 FU6 BTS 2 FU7 BTS 2 FU7 BTS 2 FU8 BTS 2 FU8 BTS 2 OML1 FU1 BTS1 FU1 BTS1 RSL1 FU2 BTS1 FU2 BTS1 RSL2

First Example with a BTS*8 TRX RSL 16kbit/s

Ed

TD

03

RSL4

RSL1

RSL8

QMux OML2 FU1 BTS 2 FU1 BTS 2 RSL3 RSL5 FU3 BTS 2 FU3 BTS 2 FU5 BTS 2 FU5 BTS 2 OML1 FU1 BTS1 FU1 BTS1 RSL 1 FU2 BTS1 FU2 BTS1 RSL2

Second example with a SSC 3*1 TRX RSL 16kbit/s


19/25


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

BSC

A b is lin k

BTS 1 FU 1

FU3

FU2

A b i s l in k

BSC

BTS 2 FU5

BTS 1 FU3

FU2

FU6

FU7

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

A b is lin k

FU1

BTS 3

A b i s lin k

BTS 2 FU4

BTS 3 FU5

FU6

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.

H

From /To

F

Closed C (CC)

1AA 00014 0004 (9007)A4

Reshuffling Q1 TS16/18

FA

TD

Ð

Reshuffling Q1 TS0 TS16/18

CC

Ed

Full Allocation

03

ÐTS0

Decreasing A.

Ð

Reshuffling Q1 TS0 TS1 Reshuffling Q1 TS16/18 TS1

Ð

Star

Ð

Reshuffling Q1 TS0 TS0/19 Reshuffling Q1 TS16/18 TS0/19

Ð


20/25

Ð

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

Ð

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

Reshuffling Q1 TS1 TS0 Reshuffling Q1 TS0/19 TS0

DA

Ð

Ð

Reshuffling Q1 TS1 TS0/19

Ð

ÐTS1

Reshuffling Q1 TS0/19

4.5 Summary of CMA R4 Mapping Rules Abis Topology

NAME

max BTS TS

TS ALLOCATION POLICY

Q.1 TS

(internal) Chain X

Ring X

X

X

X

X

TSO Transparency Pre-configured 2 variants depending BTS number 2 sub_variants in BSCG1, depending FU/TCU ratio strict dependence on phys. BTS sequence. TSO Usage

COMMENT R+S bits

Full Allocation

28

Decreasing Alloc.

30

Closed catalog

30

Pre-configured, six 0 31 or 19 different BTS/TRE +0 combinations TSO Usage or Transparency

Star Mapping

25

Fixed mapping, PCM link with only one BTS.

18 or 16

31+17 or 31+15

1

-

0 or 19

Unused TS grouped on TS X..31.

Fits in well with external cross-con.

No chain nor loop cap.

Table 9 : CMA R4 Mapping rules

4.6 Support of new features

NAME

1AA 00014 0004 (9007)A4

(internal)

Compatible Static with 16 Kb/s RSL G1 BSC subG1 BTS multiplexing

SECTORISED SITE

Full Allocation

YES

NO

YES

Decreasing alloc.

YES

YES

YES

Ed

TD

03


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

YES NO

NO

YES

Chain

Closed catalog

NO

Table 10 : Supported features/Mapping rules

Released

YES

03 3BK 10204 0335 DTZZA

Star Mapping

Ed

TD 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

Ed

TD

03 STAR Mapping

Closed Catalogue

TSO Usage

Ring

Decreasing Allocation

TSO Usage

TSO

(Only BTS G1)

Transparency

TS0 Q+S

1*5+1*4 TS0 Q+S

1*4+1*3+1*2 TS0 Q+S

Transparency

Chain

4 *2

3 *3 TRX

TS0 Q+S

TS0 Q+S

Type 1 (1 to 4 BTS)

Type 2 (5 to 7 BTS)

3 *3 TRX TS0 Qmux

TS0 Qmux

TS0

TS0

TS0

TS0

TS1 Qmux

See section 3.2 for detail




See section 3.2 fordetail TS19 R bits



TS BTS n


TS19 Qmux

....

3BK 10204 0335 DTZZA

Released

TS BTS 1

TS31 R bits

TS31 R bits

TS17 S bits TS18 Qmux

TS15 S bits TS16 Qmux

TS31 R byte

TS31 R byte

TS BTS n -1

(SFR) TS31 R bits

TSO Transparency

Ring

TSO

Chain 1*8 TRX

Full Allocation

TS31 R bits

R4 Mapping Rules

23/25


5. IMPACTS 5.1 HW/FW/SW impacts OMC

BSC

BTS OMU

others

TSC Alcatel

TRANS equipment Alcatel

TOOLS

NCS

X (SW)

6 GLOSSARY BSC BSS BTS CMA F bits (*) FR

Base Station Controller Base Station Sub-system Base Transceiver Station Configuration Management Applications RAI bits not in TS0 Full Rate

1AA 00014 0004 (9007)A4

Half Rate HR Operation & Maintenance Link OML (*) SECTORISED SITE Optimised Sectorised Site Configuration (1 BTS for several cells). PCM (*) Q bits (*) Q mux named Q1) R bits (*) RAI (*) RSL (*) S bits (*) SMBI

Pulse Code Modulation Q mux bits Bus for the configuration/supervision of the transmission equipments Ring control bits Remote Alarm Indication Radio Signalling Link Bits to choice of the clock Synchronisation side in a ring SubMultiplexer Base Interface board.

TCH (*) TS (*) TSC

Traffic CHannel Time Slot in a 2048 kbit/s i.e. 64 kbit/s Transcoder Submultiplexer Controller

Ed

TD

03


24/25

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

For the document:

TECHNICAL FEATURE DESCRIPTION Abis mapping : Timeslot allocation 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 P. Dupuy D. Le

M.Roelandts

JF. A. JP. M. E.

M. Sabbe

Maillard Pech Poirault Tuchendler Vigne

ADDITIONAL DISTRIBUTION MCD

MCD/TD/BDC_A

MCD/TD_B

F. Cadorel

.

.

MCD/TD/BDC_C

MCD/TD_S

.

R. Kreis O. Strumberg

MCD/TD E. M. M. G. A.

Amblard Jaouen Robert Dael Wasnieswski

1AA 00014 0004 (9007)A4

END OF DOCUMENT

Ed

TD

03


25/25

Abis Mapping

Recommend Documents