05 - 2006-02-10_Digitel - Iub Design

All rights reserved © 2006, Alcatel

Digitel/Alcatel – IuB Design

2006, February 10thNathalie PEYROT

All rights reserved © 2006, AlcatelDigitel 3G Workshop / February 2006

Iub DimensioningArchitecture

Node-B

RNC

RNC

Node-B

Node-B

Iub

Iub

Iub

IurGMSCMSC

SGSN GGSN

HLR

Iu-CS

Iu-CS

Iu-PS

Iu-PS


Iub DimensioningVP/VC configuration

VCI 38-50 : NBAP-d - 42 Kbps

VCI 34 : ALCAP - 32Kbps

VCI 35 : NBAP-c - 38 Kbps

VCI 64 : Node Sync - 24 Kbps

VCI 37 : O&M - 64 Kbps

VCI 65 : User Data - 1700 Kbps

Additional(depends on Node B configuration)


1 to 4 VP per Node-B

1 VP per E1 at Node-B side

Node-B

RNCVCI 65 : User Data - 1920 Kbps

VPs


Iub DimensioningVP/VC configuration / some rules

Iub VP/VCs are defined in the ATM “xml” template files that are loaded in the RNC and Node-B

The size and number of VCs carrying the NBAP messages depend on the number of BB boards

Total available bandwidth on 1 E1: 1920 kbps 220 kbps for Control Plane VCs (1 BB) => there is 1700 kbps bandwidth left for User Data VC

No Control Plane VCs on the additional E1s => 1920 kbps left for User Data VC

VCI 38-50 : NBAP-d - 42 Kbps

VCI 34 : ALCAP - 32Kbps

VCI 35 : NBAP-c - 38 Kbps

VCI 64 : Node Sync - 24 Kbps

VCI 37 : O&M - 64 Kbps





Iub DimensioningVP/VC configuration / some rules

The User Data VC is shared between RRC traffic and user traffic

The RRC bandwidth on Iub is low. A margin of 5% is applied to take into account DCCH traffic.

The left bandwidth (depends on VP’s size) will carry user traffic (DTCH)

This User Traffic bandwidth has to be calculated from the inputs provided by the Operator


Iub DimensioningProcess

Number of E1

Iub VP/VC templates to use

Number of E1

Iub VP/VC templates to use

Iub Dimensioning processIub Dimensioning process

Iub VP/VC templates

Traffic Inputs

Number of BB boards

User Data VC required ATM Bandwidth (Kbps)

TemplateSelectionTemplateSelection

IncludesSignalling

Traffic ModelTraffic Model

OverheadcalculationOverheadcalculation


DCH FP

ATM/AAL-2

Physical layer

Node-B RNC

RLC/MAC

PDCP

Application

Iub Link

Iub DimensioningOverhead calculation

To get the ATM User Data Bandwidth

=> need to apply overheads to the peak bandwidth derived from Traffic Model

example: PS 384 kbps, TTI = 20ms

Overh

ead

s

Layer bitsPDCP = null 960RLC/MAC 1008

Iub Frame Protocol (UL) 1015AAL2/ATM (best case) 1222

Total Overhead 27.3%


Iub DimensioningFind the appropriate template

With the User Data VC bandwidth, select the Iub template to be applied.

Iub VP: 1 VP: 2 VP: 3 VP: 4Number of VCs VC Bandwidth Number of VCs VC Bandwidth Number of VCs VC Bandwidth Number of VCs VC Bandwidth

VC user plane 1 1496 1 1920 0 0 0 0VC ALCAP 1 32 0 0 0 0 0 0VC Node synchro 1 32 0 0 0 0 0 0VC NBAP-c 1 183 0 0 0 0 0 0VC NBAP-d 1 113 0 0 0 0 0 0VC Node B O&M 1 64 0 0 0 0 0 0Total Number of VCs 6 1 0 0VP 1 1920 1 1920 0 0 0 0

1st VP 2nd VP 3rd VP 4th VP

EMPTY EMPTY

2 E1s => 3245 Kbps bandwidth

for user data including overhead(without RRC)


Iub Dimensioning requires to derive a peak of traffic in a Multi-service environment

As a consequence, a Multi-service Traffic Model is used The peak of traffic is the shared resource Additional traffic such as overheads and signalling has to be considered. ATM overheads are calculated not taken as a fixed margin

Iub DimensioningConclusion


Traffic Parameters Services, service class, bit rates, traffic volumes,

GoS Allowed blocking and delay

Site Configuration Number of cells

Radio Parameters Soft Handover rate

Iub DimensioningRequired Parameters

www.alcatel.com

05 - 2006-02-10_Digitel - Iub Design

Documents

Transcript of 05 - 2006-02-10_Digitel - Iub Design