Dimensioning rules for Abis optimiser in release B10

Dimensioning rules for Abis optimiser In Release B10

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 1

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

Dimensioning rules for Abis optimiser in release B10

Contents

3. SCOPE............................................................................................................ 4

2. REFERENCE...................................................................................................... 3 Notice of proprietary information................................................................... 4

1. GLOSSARY ....................................................................................................... 3

6. BANDWIDTH AFTER OPTIMIZATION .......................................................................... 8 6.1 6.2 Overheads ............................................................................................... 9

5. APPLICATION CASES AND END-TO-END ARCHITECTURE .................................................. 6 Bandwidth gain brought by Abis optimisation ..................................................... 8 Ultimate configuration per BTS site ................................................................ 9

4. INTRODUCTION ................................................................................................. 5

6.3

Figures

Figure 2 : Cell Site Optimiser for E1 optimisation ................................................................... 9

Figure 1 : Abis optimization : application cases ..................................................................... 7

Figure 3: E1 optimisation: site configuration example 1 ......................................................... 10 Figure 4: E1 optimisation: site configuration example 2 ......................................................... 10 Figure 5: E1 optimisation: site configuration example 3 ......................................................... 10

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 2

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

Dimensioning rules for Abis optimiser in release B10

1. GLOSSARY
Abis nibble CS DSCP GE 16K timeslot (4 nibbles per 64K TDM timeslot) Circuit Switched DiffServ Code Point Gigabit Ethernet

GboIP GPRS GSM MFS PS QoS TS

Gb interface over IP General Packet Radio Service Multi-BSS Fast packet Server

Global System for Mobile communications

Packet Switched

SGSN

Quality of Service

Time Slot (64K TDM TS)

Service GPRS Support Node

2. REFERENCE

[REF 1] 3DC 21144 0063 TQZZA: Functional Feature Description Packet Transmission features in release B9

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 3

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

Dimensioning rules for Abis optimiser in release B10

3. SCOPE
The present dimensioning guidelines gives detailed information about how to dimension the optimized bandwidth on Abis interface. These solutions are available as an option in the Alcatel-Lucent BSS B10 MR2, on top of any legacy BSS hardware.

Preliminary notice The information contained in this document is subject to change without notice.

Notice of proprietary information This document contains proprietary technical information belonging to Alcatel-Lucent. By accepting this material, the recipient agrees that this material will not be reproduced or used in whole or part except as otherwise agreed between Alcatel-Lucent and the recipient.

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 4

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

Dimensioning rules for Abis optimiser in release B10

4. INTRODUCTION
On the Abis interface, the reserved bandwidth (i.e. the number of TDM Timeslots) for the voice traffic is over-dimensioned compared to the actual BTS traffic. This results in an additional possibility for the optimization of the Abis traffic, also called compression: only the real traffic is sent over the Abis. Idle radio timeslots do not consume transmission resources, and silences are suppressed from the voice calls. Chapter 5 describes the end-to-end architecture. Chapter 6 provides bandwidth estimation on Abis with optimization over E1. Thanks to optimization, the number of TDM timeslots required to backhaul Abis traffic is reduced: thus, the maximum number of TRX supported per site to fill up 1 E1 or 2 E1s (referred here as ultimate configuration) is increased. Ultimate configurations are reported in 6.3.

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 5

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

Dimensioning rules for Abis optimiser in release B10

5. APPLICATION CASES AND END-TO-END ARCHITECTURE

Optimization in the BSS aims at reducing the transmission capacity needs for the backhauling of Mobile traffic, without any impact on legacy transport networks. It is nothing else but a transmission optimization, which is also completely transparent to the BSS. Despite Alcatel-Lucent provides optimized usage of TDM Timeslots thanks to the Dynamic Abis feature (see [REF 1]), the reserved bandwidth (i.e. the number of TDM Timeslots) for the Abis traffic is over-dimensioned compared to the actual BTS traffic: the statistical usage of the radio Timeslots (and as a consequence the one of TDM timeslots) is not achieved for the voice traffic. the voice activity factor (i.e. the periods during which there is speech activity within a call) of the voice traffic is not handled.

This results in an additional possibility for the optimization of the Abis traffic, also called compression: only the real traffic is sent over the Abis. Idle radio timeslots do not consume transmission resources, and silences are suppressed from the voice calls. The optimization depends on many factors, as detailed in Chapter 6, but an average value of 30% bandwidth savings may be retained. As a consequence, the required number of TDM timeslots required to backhaul Abis traffic is reduced, allowing for several cases of network optimization, as described in figure below.

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 6

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

Dimensioning rules for Abis optimiser in release B10

Cell site optimizer

11-Improved Improvedchaining chaining capabilities capabilities

(*) leased lines

TDM Aggregation MicroWave/LL) MicroWave/LL)

E1 BSC

Aggregation gateway
E1

22-Reduce ReduceNumber Numberof ofE1 E1at atradio radiosite site

30% 30%bandwidth bandwidthreduction reduction BTS 2E1 BTS 2E1backhauling backhaulingwith withsingle singleE1 E1

33-More Moresellable sellableservices services

nd Add AddTRx TRxwithout withoutneed needof of22ndE1 E1

Figure 1 : Abis optimization : application cases The following typical application cases are : 1. optimization shall allow to chain 3 BTS instead of 2. 2. The optimization shall allow to reduce the number of E1 at base station site, from 2 E1 to 1 E1. This provides significant transmission savings, especially in the case where chaining is not possible. 3. Optimization shall allow for a densification of the coverage (i.e. more TRx at a given radio site) without the need to reinforce the transmission capacity needs. End-to-End Architecture The overall BSS architecture remains unchanged: the Abis flow are backhauled through a TDM network, typically E1 Microwave or E1 leased lines. Whatever the application case, the architecture relies on two equipments: A Cell site optimizer, located at radio site, An aggregation gateway, located in central sites (BSC, TC, MFS).

Both perform the same functions, but are made of a different hardware since they do not address the same traffic capacity. Optimization is fully transparent to the legacy BSS.

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 7

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

Dimensioning rules for Abis optimiser in release B10

6. BANDWIDTH AFTER OPTIMIZATION

This chapter describes the principles of bandwidth dimensioning for Abis interface when optimization is activated. Section 6.1 gives the principles used to derive the optimization gains. Section 6.2 recalls the overheads that need to be taken into account in the final bandwidth estimation Section 6.3 summarizes the ultimate configurations per BTS site to come up with 1 E1.

6.1 Bandwidth gain brought by Abis optimisation

On the Abis interface, the bandwidth gain brought by the optimization is mainly accounted for by the statistical usage for voice calls of Abis timeslots and the voice activity factor. Contrary to static mapping, this approach introduces a Grade of Service on Abis for voice. This GoS corresponds to an overflow once the call is established, mirroring the capability of the vocoder to deliver a good voice quality despite the lost packets. It does not introduce blocking. The overflow probability is computed by a binomial law taking into account the maximum number of active timeslots on the air interface and the voice activity factor. A maximum value of 2% for the overflow is considered in the following. The expected compression rate is highly sensitive to: The Voice activity factor is linked to the number of simultaneous active calls at cell site. The denser the cell site activity, the lower the voice activity factor (better statistical effect). Silence rate: ratio of silences during the call. This parameter depends among others on the speech rhythm (which varies with the language of the speaker), the site environmental noise (background noise reduces the probability to have silences in the call). A value of 60%, accounting for both silence and activity factor is assumed here. Data traffic ratio: compression applies to voice traffic, not data traffic. The compression rate is all the more significant since the voice traffic ratio is high.

Note that the BTS load is supposed to be 100% in the optimization gains computed below. For lower loads, the gain is expected to be higher. The bandwidth gain is computed on the number of 64 kbps TS. It ranges from 20 to over 30% depending on the number of TRX on the site: the more TRX, the higher the optimization gain.

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 8

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

Dimensioning rules for Abis optimiser in release B10

6.2 Overheads
The overall bandwidth must take into account overheads coming from Signaling and unit management between the optimisation boxes. E1 framing after optimisation

6.3 Ultimate configuration per BTS site

In case of E1 optimisation, the interest of the solution lies in a configuration where 2 outgoing E1 are reduced to 1 (see Figure 2).

Expected compression rate = f (voice activity factor, silence ratio, % data traffic,..)
E1

E1

Input Ni 64K TS

Output No 64K TS

Figure 2 : Cell Site Optimiser for E1 optimisation Computations based on the principles explained in 6.1 and 6.2 show that No is less than 31 TS if Ni is less than 44 TS. Figures below give 3 examples of site configuration where 2 outgoing E1s are reduced to a single outgoing E1 thanks to the Abis optimizer. Thanks to the optimisation solution, one site can host up to 18TRX and consume 1 E1 bandwidth for Abis.

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 9

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

Dimensioning rules for Abis optimiser in release B10

S222, 1 HR per cell, 3 extra TS for EDGE S222, 1 HR per cell, 3 extra TS for EDGE

900MHz

E1

E1

1800MHz
Figure 3: E1 optimisation: site configuration example 1

S333, no HR, no EDGE S333, no HR, no EDGE

900MHz

E1

E1

1800MHz
Figure 4: E1 optimisation: site configuration example 2

S666, 1HR per cell, 2 extra TS

E1

E1

Figure 5: E1 optimisation: site configuration example 3

End of Document

Alcatel-Lucent

Date 07/07/2008

Edition 01

Page 10

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