B9 Traffic Follow-Up

Alcatel BSS B9 release
B9 Traffic Follow-up / August 2005
All rights reserved 2005, Alcatel
Agenda
Page 2
B9 Traffic Follow-up
Introduction Traffic Method Congestion Indicators
Agenda
Page 3
Introduction
Page 4
What is the Gain on dimensioning aspects in 2G-B9?

From B8 to B9, we introduced the following concepts:
M-EGCH Statistical Multiplexing (Pool of GCH resources for the whole TRX) Dynamic Abis Allocation (M-EGCH bandwidth allocated dynamically) Enhanced Transmission Resource Management (Abis and Ater)
Those new algorithms will improve the usage of Abis resources significantly This leads to a reduction of consumption of Abis/Ater Transmission links (e.g. use of only one E1 link on ABIS instead of 2 links)
Introduction
Page 5
How can I assess my 2G-B9 dimensioning Gain?

TC E1 MBS MSC
Abis
E1 E1
BSC
Core Network
MFS SGSN
MBS
Abis in B8
RTS
MBS
Abis in B9 In B8, Basic Abis nibbles and Extra Abis nibbles are statically mapped to a RTS. They are only used in the EGCH of this RTS. In B9, all GCH are gathered into one M-EGCH link. Basic, extra and bonus Abis nibbles are available for the whole TRX. And each M-EGCH resource (GCH) is available at BTS level.
Introduction
Page 6
How can I assess my 2G-B9 dimensioning Gain?

The best way to assess the use of Abis resources is to evaluate the number of GCH resources : 1. Start with a B8 network with EDGE already activated,
2.
3.
Find the reference traffic on B8 network (in terms of number of GCH used),
Apply the method formula (described in the following slides) to find the required dimensioning on B9 network based on the equivalent traffic found in B8,
4.
5.
Migrate to B9,
Check that the traffic on B9 is the expected one (in terms of number of GCH) (with the same amount of traffic observed before migrating to B9 (in terms of End-user traffic))
Agenda
Page 7
Traffic method
Page 8
Status of the method Dimensioning traffic method on a BSS network has to handle the following interfaces: Traffic on Air/Abis interface Traffic on Ater interface Traffic on Gb interface
Traffic method
Page 9
Status of the method (contd) The method proposed by Alcatel / PCS takes into account only the real status of the network by using the PM counters and Indicators available at OMC-R level.
The method to assess the number of GCH used is mainly based on the amount of data the MFS sends or receives (in DL & UL).
The counters used must be valid in B8 and in B9 in order to use the same comparison reference.
Traffic method AIR/ABIS interface Traffic
Page 10
The counters which give the amount of data GPRS/EDGE to handle are expressed in number of RLC blocks in DL and UL side. The following counters are available in B8 and B9: P55x (x [a .. m]) = Number of useful DL RLC blocks sent in RLC acknowledged mode on PDTCH encoded in (M)CSx (max MCS9) during the reporting period (usually 3600s), P57x ((x [a .. m]) = Number of useful UL RLC blocks received in RLC acknowledged mode on PDTCH encoded in (M)CSx (max MCS4 in UL for B8) during the reporting period (usually 3600s).
Note : in UL direction in B8, the highest coding scheme is MCS4 (P57h)
Page 11
For each Coding Scheme, the size of the RLC blocks varies
Channel Coding scheme CS-1 CS-2 CS-3 CS-4 Channel Coding scheme MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 (sent of 2 blocks) MCS-8 (sent of 2 blocks) MCS-9 (sent of 2 blocks) RLC data block total number of bytes 22 32 38 52 RLC data block total number of bytes 22 28 37 44 56 74 2*56 2*68 2*74
Page 12
Traffic Intensity definition:

The traffic intensity represents an amount of data that the network has to handle. It is expressed in erlang.
x= [RLC data blocks (bytes) (M)CS x per cell * 8/1024] / Throughput (M)CS x per RTS (kbps) With, RLC data blocks (bytes/s) (M)CS x = (Number of useful DL/UL RLC blocks)x * (RLC data block total number of bytes)x /PERIOD, with x = [1..9] And Throughput (M)CS x per RTS (kbps) is the effective throughput on radio interface RLC/MAC layer (see next slide)
Traffic method
Throughput (M)CS x per RTS (kbps)
Scheme CS-1 CS-2 CS-3 CS-4 MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9 Maximum Throughput in kbps per RTS (Radio Time Slot) on RLC/MAC layer 8 12 14.4 20 8.8 11.2 14.8 17.6 22.4 29.6 44.8 54.4 59.2
AIR/ABIS interface Traffic

Page 13
Page 14
Hence the total number of ABIS GCH used in DL or UL using the Coding scheme x for a BTS (with y cells) is: (Total Nb Abis )x =
y cells
BTS
y x * (Nb Abis_Nibbles per (M)CS)x
The Nb Abis_Nibbles per (M)CS)x varies in B8 and in B9 (see next 2 slides)

And for all coding schemes (x) BTSall cells (y) of the BTS: m on

xa
Total Nb Abis
y cellsy
x*
(Nb Abis_Nibbles per (M)CS)x
Page 15
The Nb Abis_Nibbles varies per (M)CS)x in B8

Scheme per RTS CS-1 CS-2 CS-3 CS-4 Nb_GCH required in B8 per RLC PDU 1 1 2 2
MCS-1
MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7
2
2 2 2 2 3 4
MCS-8
MCS-9
4
5
Page 16
The Nb Abis_Nibbles varies per (M)CS)x and on UL and DL in B9

MCS per RTS CS-1 CS-2 CS-3 CS-4 MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 Nb_GCH required UL per RLC PDU 0.73 1 1.25 1.64 0.89 1 1.33 1.5 1.86 Nb_GCH required DL per RLC PDU 0.73 1 1.22 1.60 0.86 1 1.28 1.47 1.81
MCS-6
MCS-7 MCS-8
2.36
3.49 4.14
2.31
3.39 4
MCS-9
4.49
4.39
Traffic method
Examples:
For MCS9, we have the traffic intensity for one cell in DL: m = ((P55m* 74 /3600)* 8/1024 )/ 59.2
In the BTS, we have 3 cells, each having as traffic intensity: 1 m ; 2 m ; 3 m Then the number of Abis Nibbles for this Coding Scheme MCS9 used in B8 is: (Total Nb Abis DL)m = (1 m + 2 m + 3 m ) * (Abis_Nibbles)m = (1 m + 2 m + 3 m ) * 5 Then the number of Abis Nibbles for this Coding Scheme MCS9 used in B9 is: (Total Nb Abis DL)m = (1 m + 2 m + 3 m ) * (Abis_Nibbles_DL)m = (1 m + 2 m + 3 m ) * 4.39

Page 17
Traffic method
Examples:

Page 18
And for all coding schemes (x) on all cells (y) of the BTS:
Total Nb Abis DL =

xa
y cells
BTS
Traffic method Example DL: AIR/ABIS interface Traffic
Page 19
Traffic method
Examples:
For MCS4 in B8, we have the traffic intensity for one cell in UL: h = ((P57h * 44 /3600) * 8/1024) / 17.6 For MCS9 in B9, we have the traffic intensity for one cell in UL: m = ((P57m * 74 /3600) * 8/1024) / 59.2 In the BTS, we have 3 cells, each having as traffic intensity: 1 h ; 2 h ; 3 h Then the number of Abis Nibbles for this Coding Scheme MCS4 used in B8 is:
(Total Nb Abis UL)h = (1 h +2 h +3 h )* (Abis_Nibbles)h = (1 h +2 h +3 h )* 2 = (1 h +2 h +3 h )* (Abis_Nibbles)h = (1 h +2 h +3 h )* 4.49

Page 20
Then the number of Abis Nibbles for this Coding Scheme MCS9 used in B9 is:
(Total Nb Abis UL)m
Traffic method
Examples:

Page 21
And for all coding schemes (x) on all cells (y) of the BTS in B8:
Total Nb Abis UL =

xa
y cells
BTS
And for all coding schemes (x) on all cells (y) of the BTS in B9:
Total Nb Abis UL =

xa
y cells
BTS
Traffic method Example UL: AIR/ABIS interface Traffic
Page 22
Traffic method Additional features to include
Some others telecom parameters have leverage on the result of number of GCH used :
Padding, multiplexing of RLC blocks which not fulfill the GCH pool available, T_GCH_Inactivity, increases the use (reservation) of GCH resources within a PDCH in order to avoid signaling traffic in case of new incoming TBF data to send, RLC blocks Retransmitted in UL and DL, due to unacknowledge of RLC blocks between MS and MFS, MPDCH and Fast Initial PS Access

Page 23
Traffic method Padding
refers to loss of GCH resource due to under-use.

Page 24
Traffic method Padding
Due to the difficulty to assess the level of padding for each GCH, we can assume a given percentage. assumption 10% Padding in B8 should be greater than Padding in B9. It is due to the efficient multiplexing in B9, where we can take benefit of some GCH resources.

Page 25
Page 26
T_GCH_Inactivity & Fast Initial PS Access

When a TBF is released and Target_Nb_GCH becomes strictly lower than Established_Nb_GCH unused GCHs:
Triggers an inactivity timer (T_GCH_Inactivity) Anticipates new TBF arrival GCH preemption At timer expiry, if Target_Nb_GCH is still strictly lower than Established_Nb_GCH, the unused GCHs are released: Choice of GCHs to release is the reverse order than the one used for GCH establishment If there is no TBF traffic in the cell and the TRX is the last established TRX of the cell: Not all the GCHs are released (keep N_GCH_Fast_PS_Access GCHs) Triggers T_GCH_Inactivity_Last timer Only valid if Fast Initial PS Access is disabled
Traffic method T_GCH_Inactivity
We have the following counters in B8:
P38 : TIME_PDCH_ESTABLISHED
Cumulated time during which the master and slave PDCHs are established for the cell. Only B8 available counter.

Page 27
P38b : CUMULATED_TIME_PDCH_USED
Cumulated time during which the slave PDCHs carry at least one UL or DL TBF (TBF established in GPRS mode or EGPRS mode)
T_GCH_INACTIVITY_B8 = (P38-P38b)/P38
We have the following counters in B9:
P414bis : CUMULATED_TIME_ALLOCATED_SPDCH
This counter integrates over time the values of the allocated SPDCH during the whole granularity period

Page 28
P38b : CUMULATED_TIME_PDCH_USED
Cumulated time during which the slave PDCHs carry at least one UL or DL TBF (TBF established in GPRS mode or EGPRS mode)
T_GCH_INACTIVITY_B9 = (P414bis-P38b)/P414bis
Assumption based on B9 average values
T_GCH_Inactivity [70% - 100%] of Traffic activity Example in B9:

Page 29
Traffic method DL RLC blocks retransmitted
In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in (M)CS retransmitted due to unacknowledgement of the MS.

Page 30
UL RLC blocks retransmitted

In acknowledged mode, number of UL RLC blocks on PDTCH encoded in (M)CS retransmitted due to unacknowledgement of the MFS.
Traffic method
DL RLC blocks retransmitted
We have the following counters:
P20a : NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS1
In acknowledged mode, number of DL RLC blocks (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in CS-1 retransmitted due to unacknowledgement of the MS

Page 31
P20b : NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS2 P20c : NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS3 P20d : NB_DL_RLC_BLOCK_PDTCH_RETRANS_CS4 P20e : NB_DL_RLC_BYTES_PDTCH_RETRANS_MCS

In acknowledged mode, number of DL RLC data bytes (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in MCS-x (with x = 1 to 9) retransmitted due to unacknowledgement of the MS
Traffic method
We have the following counters:
P21a : NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS1
In acknowledged mode, number of UL RLC blocks (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in CS-1 retransmitted due to unacknowledgement of the MFS

Page 32
P21b : NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS2 P21c : NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS3 P21d : NB_UL_RLC_BLOCK_PDTCH_RETRANS_CS4 P21e : NB_UL_RLC_BYTES_PDTCH_RETRANS_MCS

In acknowledged mode, number of UL RLC data bytes (except RLC blocks containing LLC Dummy UI Commands only) on PDTCH encoded in MCS-x (with x = 1 to 9) retransmitted due to unacknowledgement of the MFS
Traffic method
We have an additional amount of data, due to retransmision of unacknowledged RLC blocks To take into account those values, we have to insert the data for each coding scheme into a new Traffic Intensity value x :
For Coding scheme CS: The counters give a value in RLC blocks. We translate them into bytes. P20a*22 P20b*32 P20c*38 P20d*52 a = (((P55a + P20a) * 22 /3600) * 8/1024) / 8 b = (((P55b + P20b) * 32 /3600) * 8/1024) / 12 c = (((P55c + P20c) * 38 /3600) * 8/1024) / 14.4 d = (((P55d + P20d) * 52 /3600) * 8/1024) / 20

Page 33
Traffic method
For Coding scheme MCS: The counter gives an aggregated value in bytes. P20e
Example for MCS9 m = ((P55m*74 + P20e*[P55m/ With, *[P55m/
m

Page 34
P55x] )/3600) * 8/1024}/ 59.2

x e
P55x] is necessary to weight the leverage of each coding scheme on P20e, which
x e
is composed of an aggregate of all Coding Scheme,
Traffic method
For Coding scheme CS: The counters give a value in RLC blocks. We translate them into bytes. P21a*22 P21b*32 P21c*38 P21d*52
a = (((P57a + P21a) * 22 /3600) * 8/1024) / 8 b = (((P57b + P21b) * 32 /3600) * 8/1024) / 12 c = (((P57c + P21c) * 38 /3600) * 8/1024) / 14.4 d = (((P57d + P21d) * 52 /3600) * 8/1024) / 20

Page 35
Traffic method
For Coding scheme MCS: The counter gives an aggregated value in bytes. P21e
Example for MCS9 m = {((P57m*74+P21e*[P57m/ With, *[P57m/
m

Page 36
P57x] )/3600)*8/1024}/ 59.2

x e
P57x] is necessary to weight the leverage of each coding scheme on P21e, which
x e
is composed of an aggregate of all Coding Scheme,
Page 37
MPDCH and Fast Initial PS Access

For MPDCH, we can assume 1 GCH additional used per cell For Fast Initial PS Access (if enabled), we can assume 1 additional GCH used per cell
Page 38
Total Number of Abis, taking into account all parameters

Note: are not included MPDCH and Fast Initial PS Access in the formulas
Accurate Total Nb Abis DL = Padding% * [ (1+T_GCH_Inactivity) + RLC retransmit DL
m
BTS
y x
y x * (Nb Abis_Nibbles per (M)CS)x] *
BTS
x a y cells
Accurate Total Nb Abis UL = Padding% * [ (1+T_GCH_Inactivity) + RLC retransmit UL
* (Nb Abis_Nibbles per (M)CS) ] *

x
x a y cells
Traffic method Example DL: AIR/ABIS interface Traffic
Page 39
Traffic method Example UL: AIR/ABIS interface Traffic
Page 40
Traffic method
B8 ATER traffic The Ater traffic is related to GPU(MFS) counters.
Ater interface Traffic

Page 41
The following counters are available:

P100a : CUMULATED_TIME_BUSY_GCH_GPU
Cumulative time (in seconds) during which a GCH (16k channel) is busy in the GPU. The counter is integrated over all the GCH available in the GPU). Only B8 counter
P100b : MAX_NB_BUSY_GCH_GPU
Maximum number of busy GCH (16k channel) in the GPU). Only B8 counter
We obtain easily the average number of GCH used and its maximum by : Average Nb GCH busy = P100a/3600 Maximum Nb GCH busy = P100b
Traffic method
B9 ATER traffic The following counters are available: P100f : MAX_NB_GCH_BUSY_GPU
Maximum number of busy GCH (16k channel) in the GPU
Ater interface Traffic

Page 42
P101 : CUMULATED_TIME_AVAIL_GCH_GPU
Cumulative time (in seconds) during which a GCH resource (16k channel) is available in the GPU. The counter is integrated over all the GCH resources configured in the GPU
P474 : CUMULATED_TIME_FREE_ATER_NIBBLES
Cumulative time (in seconds), per GPU ,during which there are free Ater nibbles
We obtain easily the average number of GCH used and its maximum by : Average Nb GCH busy =(P101 P474)/3600 Maximum Nb GCH busy = P100f
Traffic method Example Ater interface Traffic
Page 43
Traffic method
B9 Gb traffic
The following counters are available:
P45 : NB_KBYTES_RECEIVED_FROM_SGSN P46 : NB_KBYTES_SENT_TO_SGSN
Gb interface Traffic
Page 44
DL Gb throughput (kb/s) = P45/(8*3600) UL Gb throughput (kb/s) = P46/(8*3600)
Traffic method B9 Gb traffic Gb interface Traffic
Page 45
Agenda
Page 46
Traffic method Congestion Indicators
Page 47
Some counters gives an indication on the level of congestion of the network lack of Abis resources
A lack of Abis transmission resources occurs when there is not enough Abis nibbles to serve the DL/UL TBF request The number of GCH that can be established and, or redistributed is < Nb_GCH_FOR_TBF_ESTAB and the number of free Abis nibbles is < Nb_GCH_FOR_TBF_ESTAB P105i
Number of DL TBF establishment failures due to a lack of Abis resources Number of UL TBF establishment failures due to a lack of Abis resources Both are available from MR1
P105j
Page 48
Deficit of GCH resources (MR2 only)

If the Target GCH is not reached, we have a deficit of GCH given by the following counters: P469 Maximum number of GCH in deficit reached in the cell
P470 Cumulative time (in seconds), per cell , during which there is a deficit of GCH resources (16k channel)
Page 49
Excess of GCH resources

The excess is represented as the available number of GCH Target GCH. P471
Cumulative time (in seconds), per cell ,during which there is a excess of GCH resources (16k channel)
available from MR1
Page 50
Low number of GCH (MR2 only)

A low number of GCH implies that we will have a failure to establish a TBF The following counters gives this indication:
P105k
Number of DL TBF establishment failures due to a too low number of GCH to guarantee a minimum throughput for the DL TBF. This may happen when the number of TBFs is too high compared to the number of available GCHs Number of UL TBF establishment failures due to a too low number of GCH to guarantee a minimum throughput for the UL TBF. This may happen when the number of TBFs is too high compared to the number of available GCHs
P105l
Page 51
Ater Congestion Indicators

CPU overload
DSP in the MFS can be in overload state

P203
Number of DL TBF establishment failures due to DSPs that are in CPU load / overload state
P204
Number of UL TBF establishment failures due to DSPs that are in CPU load / overload state
Page 52

Preemption Whenever a DL/UL TBF is released due to preemption of its transmission resources : 1) basic nibbles given back to the BSC for CS 2) redistribution of the GCH resources in the MFS. P481
Number of DL TBF release due to preemption in case of need of transmission resources,
Number of UL TBF release due to preemption in case of need of transmission resources
P482
Page 53

ATER nibbles free per GPU
To have the minimum reached level of free ATER, we have :

P486 : Minimum number of free Ater nibbles.
Page 54

Lack of GCH on ATER
The lack of GCH on ATER is indicated by:

P383a
Atermux congestion duration (in seconds) due to a lack of GCH transmission resources on the Atermux interface
P383b
Time (in seconds cumulated over a granularity period) during which the GPU remains in "high" Ater usage
Page 55
www.alcatel.com

B9 Traffic Follow-Up

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B9 Traffic Follow-Up

Uploaded by

Copyright:

Available Formats

Alcatel BSS B9 release

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

What is the Gain on dimensioning aspects in 2G-B9?

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

How can I assess my 2G-B9 dimensioning Gain?

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

How can I assess my 2G-B9 dimensioning Gain?

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

Traffic Intensity definition:

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

AIR/ABIS interface Traffic

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

y x * (Nb Abis_Nibbles per (M)CS)x

The Nb Abis_Nibbles per (M)CS)x varies in B8 and in B9 (see next 2 slides)

(Nb Abis_Nibbles per (M)CS)x

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

The Nb Abis_Nibbles varies per (M)CS)x in B8

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

The Nb Abis_Nibbles varies per (M)CS)x and on UL and DL in B9

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

AIR/ABIS interface Traffic

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

AIR/ABIS interface Traffic

y x * (Nb Abis_Nibbles per (M)CS)x

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

AIR/ABIS interface Traffic

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

AIR/ABIS interface Traffic

y x * (Nb Abis_Nibbles per (M)CS)x

y x * (Nb Abis_Nibbles per (M)CS)x

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

B9 Traffic Follow-up / August 2005

All rights reserved 2005, Alcatel

AIR/ABIS interface Traffic

DL Gb throughput (kb/s) = P45/(83600) UL Gb throughput (kb/s) = P46/(83600)