Professional Documents
Culture Documents
Agenda
Page 2
B9 Traffic Follow-up
Introduction Traffic Method Congestion Indicators
Agenda
Page 3
B9 Traffic Follow-up
Introduction Traffic Method Congestion Indicators
B9 Traffic Follow-up
Introduction
Page 4
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)
B9 Traffic Follow-up
Introduction
Page 5
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.
B9 Traffic Follow-up
Introduction
Page 6
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
B9 Traffic Follow-up
Introduction Traffic Method Congestion Indicators
B9 Traffic Follow-up
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
B9 Traffic Follow-up
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.
B9 Traffic Follow-up
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)
B9 Traffic Follow-up
Traffic method AIR/ABIS interface Traffic
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
B9 Traffic Follow-up
Traffic method AIR/ABIS interface Traffic
Page 12
B9 Traffic Follow-up
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
B9 Traffic Follow-up
Traffic method AIR/ABIS interface Traffic
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
xa
Total Nb Abis
y cellsy
x*
B9 Traffic Follow-up
Traffic method AIR/ABIS interface Traffic
Page 15
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
B9 Traffic Follow-up
Traffic method AIR/ABIS interface Traffic
Page 16
MCS-6
MCS-7 MCS-8
2.36
3.49 4.14
2.31
3.39 4
MCS-9
4.49
4.39
B9 Traffic Follow-up
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
B9 Traffic Follow-up
Traffic method
Examples:
And for all coding schemes (x) on all cells (y) of the BTS:
Total Nb Abis DL =
BTS
B9 Traffic Follow-up
Traffic method Example DL: AIR/ABIS interface Traffic
Page 19
B9 Traffic Follow-up
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
Then the number of Abis Nibbles for this Coding Scheme MCS9 used in B9 is:
(Total Nb Abis UL)m
B9 Traffic Follow-up
Traffic method
Examples:
And for all coding schemes (x) on all cells (y) of the BTS in B8:
Total Nb Abis UL =
BTS
And for all coding schemes (x) on all cells (y) of the BTS in B9:
Total Nb Abis UL =
BTS
B9 Traffic Follow-up
Traffic method Example UL: AIR/ABIS interface Traffic
Page 22
B9 Traffic Follow-up
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
B9 Traffic Follow-up
Traffic method Padding
refers to loss of GCH resource due to under-use.
B9 Traffic Follow-up
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.
B9 Traffic Follow-up
Traffic method AIR/ABIS interface Traffic
Page 26
B9 Traffic Follow-up
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.
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
B9 Traffic Follow-up
Traffic method T_GCH_Inactivity
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
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
B9 Traffic Follow-up
Traffic method T_GCH_Inactivity
Assumption based on B9 average values
T_GCH_Inactivity [70% - 100%] of Traffic activity Example in B9:
B9 Traffic Follow-up
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.
B9 Traffic Follow-up
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
B9 Traffic Follow-up
Traffic method
UL RLC blocks retransmitted
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
B9 Traffic Follow-up
Traffic method
DL RLC blocks retransmitted
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
B9 Traffic Follow-up / August 2005
All rights reserved 2005, Alcatel
B9 Traffic Follow-up
Traffic method
DL RLC blocks retransmitted
For Coding scheme MCS: The counter gives an aggregated value in bytes. P20e
Example for MCS9 m = ((P55m*74 + P20e*[P55m/ With, *[P55m/
m
P55x] is necessary to weight the leverage of each coding scheme on P20e, which
x e
B9 Traffic Follow-up
Traffic method
UL RLC blocks retransmitted
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
B9 Traffic Follow-up
Traffic method
UL RLC blocks retransmitted
For Coding scheme MCS: The counter gives an aggregated value in bytes. P21e
Example for MCS9 m = {((P57m*74+P21e*[P57m/ With, *[P57m/
m
P57x] is necessary to weight the leverage of each coding scheme on P21e, which
x e
B9 Traffic Follow-up
Traffic method AIR/ABIS interface Traffic
Page 37
B9 Traffic Follow-up
Traffic method AIR/ABIS interface Traffic
Page 38
m
BTS
y x
BTS
x a y cells
x a y cells
B9 Traffic Follow-up
Traffic method Example DL: AIR/ABIS interface Traffic
Page 39
B9 Traffic Follow-up
Traffic method Example UL: AIR/ABIS interface Traffic
Page 40
B9 Traffic Follow-up
Traffic method
B8 ATER traffic The Ater traffic is related to GPU(MFS) counters.
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
B9 Traffic Follow-up
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
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
B9 Traffic Follow-up
Traffic method Example Ater interface Traffic
Page 43
B9 Traffic Follow-up
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
B9 Traffic Follow-up
Traffic method B9 Gb traffic Gb interface Traffic
Page 45
Agenda
Page 46
B9 Traffic Follow-up
Introduction Traffic Method Congestion Indicators
B9 Traffic Follow-up
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
B9 Traffic Follow-up
Traffic method Congestion Indicators
Page 48
P470 Cumulative time (in seconds), per cell , during which there is a deficit of GCH resources (16k channel)
B9 Traffic Follow-up
Traffic method Congestion Indicators
Page 49
B9 Traffic Follow-up
Traffic method Congestion Indicators
Page 50
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
B9 Traffic Follow-up
Traffic method Congestion Indicators
Page 51
P204
Number of UL TBF establishment failures due to DSPs that are in CPU load / overload state
B9 Traffic Follow-up
Traffic method Congestion Indicators
Page 52
P482
B9 Traffic Follow-up
Traffic method Congestion Indicators
Page 53
B9 Traffic Follow-up
Traffic method Congestion Indicators
Page 54
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 / August 2005
All rights reserved 2005, Alcatel