2-Claro B9 Enhanced Transmission Resource Management

Enhanced Transmission Resource Management
B9 Claro Workshop - February 14th, 2006
All rights reserved 2005, Alcatel
Agenda
Page 2
Enhanced Transmission resource management

M-EGCH Statistical Multiplexing Dynamic Abis Allocation Ater Resource Management DL Retransmission in the BTS Related parameters & counters
B9 Claro Workshop / February 14th 2006
M-EGCH Statistical Multiplexing

M-EGCH link (I)
Page 3
An M-EGCH link (Multiplexed Enhanced GPRS CHannel) is a bidirectional link established between the MFS and the BTS. An M-EGCH link is a set of 16k GCH channels. An M-EGCH link is defined per TRX. The M-EGCH link of a TRX is necessary:
To carry TBF traffic and PACCH signalling when TBFs are established on some PDCHs of the TRX,
To carry signalling messages when MPDCHs are defined on the TRX, To carry UL signalling messages after one-UL-block allocation (UL twophase access), To carry some BTS-MFS signalling.

M-EGCH link (II)
Page 4
B8: one EGCH per RTS

TRX 0
EGCH
B9: one M-EGCH link for the whole TRX

TRX 0 1 2 3 4 5 6 7
1
EGCH
2
EGCH
3
EGCH
4
EGCH
5
EGCH
6
EGCH
7
EGCH
M-EGCH link
composed of composed of
GCH
GCH
GCH
GCH
GCH
GCH
GCH
GCH
1 to 5 GCHs depending on the TRX class

1 to 36 GCHs
GCH
GCH

Filling an M-EGCH link with PDUs (I)
Page 5
RLC/MAC PDU 1 for DBN=x RLC/MAC layer RLC header MEGCH header (first segment) MEGCH layer segmentation sub-layer MEGCH header (next segments) SYNC pattern + Z bit indicator MEGCH layer framing sub-layer 320 bits
Dummy Filling
RLC/MAC PDU 2 for DBN=x
LEGEND
320 bits
320 bits
320 bits
MEGCH header (/NHP and addr byte) Dummy Filling PDU CRC + Tail bits Padding bits
320 bits DBN=x GCH1 GCH2 GCH3 GCH4 GCH5

Dummy Filling
DBN=x+1
DBN=x+2
Dummy Filling PDU
Dummy Filling
20 ms
20 ms
20 ms

Gains brought by the feature
Page 6
Reduction of the Abis and Ater consumption Resources are used in a more efficient way:
Instantaneous reaction to radio variations (MCS variations).
Example:
M- EGCH link composed of 4 GCHs
DBN m GCH 1 GCH 2 GCH 3 GCH 4 DBN m+ 1 DBN m+ 2
RB1 RB1 RB2 RB2 RB3

20 ms 320 bits per GCH
RB1 RB2 RB1 RB2 RB3

20 ms
RB1 RB1 RB2 RB2 RB3

20 ms
GCH 1
RB2 RB3
RB2
GCH 2 GCH 3 GCH 4
No more TBF maximum MCS reduction is needed. The resources not used by delayed DL TBFs, extended UL TBFs, are used by other TBFs.

Towards Dynamic Abis allocation
Page 7
In B8:
The size of an EGCH link (associated to a PDCH) can be dynamically decreased.
But the size of an EGCH link cannot be dynamically increased.
In B9:
The size of an M-EGCH link (associated to a TRX) can be dynamically decreased or increased. The algorithms to dynamically decrease or increase the size of an M-EGCH link correspond to the Dynamic Abis allocation.
Agenda
Page 8

Dynamic Abis Allocation

Static versus Dynamic Abis allocation
Page 9
B8: static Abis allocation

TRX
B9: dynamic Abis allocation

7
EGCH
0
EGCH
1
EGCH
2
EGCH
3
EGCH
4
EGCH
5
EGCH
6
EGCH
TRX
M-EGCH link
composed of
GCH Basic
GCH Extra
GCH Extra
GCH Basic
1 to 5 GCHs depending on the TRX class (and only one GCH can use a basic Abis nibble)
1 to 36 GCHs (mixture of GCHs using basic, extra and bonus Abis nibbles)
GCH Basic
Basic Abis nibbles and Extra Abis nibbles are statically mapped to a RTS. They can only be used in the EGCH of this RTS.
No more constraints in B9!
composed of
GCH Basic
GCH Extra
GCH Extra
GCH Extra
GCH Extra

Abis nibbles wasted in B8
Page 10
In B8, the following Abis nibbles were wasted:

X X B X X S M M P P T T X X X X
Extra Abis nibbles (number of nibbles per RTS = TRX class-1)
Basic Abis nibbles
TRX configuration on the air interface
Legend: B: BCCH, S: static SDCCH, M: MPDCH, P: PDCH, T: TCH, X : Abis nibble wasted in B8, in B8
: Abis nibble used

Abis nibbles usable for PS traffic (I)
Page 11
In B9, the following Abis nibbles are usable for PS traffic:

The basic Abis nibbles mapped to a RTS currently available for PS traffic (see Autonomous Packet Resource Allocation" feature to know the list of those RTSs) or mapped to a RTS used as MPDCH.
Example:
P P P P M C C C RTSs in a 2-TRX cell
The basic Abis nibbles of those RTS can be used to establish some GCHs Legend: - C: RTS currently used for CS traffic (CS call), - P: RTS currently used for PS traffic (TBF or MPDCH traffic). RTS available for PS traffic RTS reserved for CS traffic

Abis nibbles usable for PS traffic (II)
Page 12
The bonus basic Abis nibbles currently used for BCCH or static SDCCH channels:
The list of bonus Abis nibbles depends on the cell configuration.
All the extra Abis nibbles of the BTS:

A number of 64k extra Abis TSs is defined for each BTS by O&M (N_EXTRA_ABIS_TS).
The list of extra Abis TSs of a BTS is provided by the BSC to the MFS.

Level of sharing of the Abis nibbles usable for PS traffic
Page 13
The basic Abis nibbles mapped on a RTS allocated to MFS can be used in the M-EGCH link of any TRX of the CELL.
The extra Abis nibbles can be used in the M-EGCH link of any TRX of the BTS.
The bonus Abis nibbles can be used in the M-EGCH link of any TRX of the BTS.

Impacts on existing scenarios and new scenarios
Page 14
Due to Dynamic Abis allocation, new messages have to be sent to the BTS to
notify each TRE which Abis nibbles are associated..

Those messages are sent via GSL and RSL interfaces. The following scenarios are therefore modified:
GCH establishment. GCH release.
New scenario appear to distribute GCH resources :

Intra-cell GCH pre-emption : between TRXs of a cell Inter-cell GCH pre-emption : between cells of a BTS
Agenda
Page 15

Ater Resource Management

Principles
Page 16
The Ater Resource Management in a given GPU is based on two complementary mechanisms:
GPU Ater TS margin,
High Ater usage handling.
A strong requirement is to ensure GPRS access in all the cells of the GPU (no cell shall be blocked due to an Ater congestion).

GPU Ater TS Margin
Page 17
GPU 64k Ater TS margin:

Aim:
Ensures that GPRS access can never be blocked in a cell due to lack of Ater resources in the GPU. Handled in each GPU to serve some priority requests at any moment and in any cell managed by the GPU.
Priority request is the GCH establishment request for the first PS traffic in a cell (first TBF to establish in a cell).
Management:
Release of some GCHs when the remaining number of free 64k Ater TSs in the GPU becomes too low (O&M parameter N_ATER_TS_MARGIN_GPU). For a given TRX, when releasing GCHs, it is ensured that:
Established_Nb_GCH remains higher than Min_Nb_GCH.

High Ater usage handling (I)
High Ater usage handling:
Definition of the Ater usage of a GPU: Represents the consumption of Ater nibbles (by GCH channels) among the PCM links connected to the GPU, Ater usage can be either normal or high.
Page 18
Decision based on the comparison of the Ater nibble consumption with a threshold (Ater_Usage_Threshold O&M parameter).

High Ater usage handling (II)
Page 19
Behaviour if Ater usage is high: Target_Nb_GCH values associated to TRXs of the GPU supporting some PS traffic will be reduced: GCH_RED_FACTOR_HIGH_ATER_USAGE O&M parameter. The reduction factor is only applied on PDCHs newly open. newly open PDCH means that no radio resources were previously allocated on this PDCH. When evaluating Target_Nb_GCH on a given TRX: If PDCH already open, no reduction is applied, If PDCH is newly open, reduction is applied.

High Ater usage handling (III)
Example:
Max_EGPRS_MCS = MCS-9, GCH_RED_FACTOR_HIGH_ATER_USAGE = 0,5 1) Ater usage = normal 2) Establishment of an EGPRS DL TBF on RTS0-3 Target_Nb_GCH = 4 * Nb_GCH(Max_EGPRS_MCS) = 4 * 4,49 = 18 3) Ater usage = high 4) Establishment of an EGPRS DL TBF on RST4-7 Target_Nb_GCH = 4 * Nb_GCH(Max_EGPRS_MCS) + 0,5 * 4 * Nb_GCH(Max_EGPRS_MCS) = 4 * 4,49 + 4 * 0,5 * 4,49 = 27 (< 36)
Page 20
Agenda
Page 21

DL retransmission in the BTS

Principles
Page 22
Goal: Avoid consuming transmission resources (Abis + Ater) in case of DL RLC data block retransmissions. Principles: Store for a certain time, in the memory of the TRE involved in the packet transfer mode with an MS, the DL RLC data blocks received from the RLC/MAC layer for this MS. Then, the RLC/MAC layer (in the MFS) can ask the TRE (in the BTS) to retransmit some data blocks.
Data received from the MFS are stored in a buffer.
DL retransmission in the BTS

Principles
Page 23
This mechanism is enabled / disabled at TRX/TRE level: HW generation of the TRE CS-2 CS-4 CS-4+MCS-9 (DRFU) (G3 or M4M) (G4 or M5M) Disabled Disabled Enabled Disabled Disabled Disabled Disabled Disabled Disabled
EN_DL_RETRANS_B TS
Round_Trip_Dela y
Enabled Enabled disabled Gains:
< 500 ms 500 ms -
Higher available transmission bandwidth. M-EGCH link dimensioning is eased.
Agenda
Page 24

Related parameters & counters

Parameters
Page 25
HMI name Definition Subsystem
BSC MFS
Insta nce
BTS MFS
OMC-R access
Changea ble None (DLS)
Type
Def value
0 1
Range
Unit
NEW : N_EXTRA_ABIS_TS NEW : N_GCH_FAST_PS_ACC ESS
Number of extra Abis (64k) timeslots configured for a BTS. Two definitions are possible : - If EN_FAST_INITIAL_GPRS_ACCESS = enabled : number of GCHs required to be established due to the Fast Initial PS Access feature, - If EN_FAST_INITIAL_GPRS_ACCESS = "disabled : number of GCHs to keep established when there is no more (E)GPRS traffic in a cell (while the T_GCH_INACTIVITY_LAST timer is running). - For Non Evolium BTS : Timer to postpone the release of one slave PDCH, when it does not support any (E)GPRS traffic. - For Evolium BTS : Timer to postpone the release of the "unused" GCHs of the M-EGCH link of a TRX (the condition for some GCHs of the M-EGCH link of a TRX to become "unused" is that some TBFs - For Non Evolium BTS : Timer to postpone the release of the last established slave PDCH of a cell, when it does not support GPRS traffic anymore. - For Evolium BTS : Timer to postpone the release of the last N_GCH_FAST_PS_ACCESS GCHs established in a cell, when the last TBF has been released in the cell. -
Numb er Numb er
[0,60] [1,5]
None None
NEW : T_GCH_Inactivity
MFS
BSS
Changea ble
Timer
[1,100]
sec
NEW : T_GCH_Inactivity_Last
MFS
BSS
Changea ble
Timer
20
[1,200]
sec

Parameters
Page 26
HMI name
NEW : N_ATER_TS_MARGIN_ GPU
Definition
Number of free 64k Ater TSs that are kept in reserve in order to be able to serve some prioritary requests in cells managed by the GPU. The prioritary requests are the GCH establishment requests launched when the first TBF has to be established in a cell. Note : In case of non-Evolium BTS, those are PDCHs that will be established instead of GCHs. Reduction factor of the number of GCHs targeted per PDCH, when the Ater usage is high. This flag enables / disables downlink retransmission in the BTS.
Subsystem
MFS
Insta nce
BSS
OMC-R access
Changea ble
Type
Numb er
Def value
2
Range
[0,10]
Unit
none
NEW : GCH_RED_FACTOR_HI GH_ATER_USAGE NEW : EN_DL_RETRANS_BTS
MFS
cell
Changea ble None (DLS)
Numb er Flag 1
0.75
[0,1]
none
MFS
MFS
[0,1]
None
Removed parameters :
NB_EXTRA_ABIS_TS T_PDCH_Inactivity T_PDCH_Inactivity_Last MAX_PDCH_PER_TBF_High_Ater_Usage

Counters
Page 27
Counter number P100c P100d
Name CUMULATED_TIME_BUSY_GCH_CELL MAX_NB_BUSY_GCH_CELL
Definition The counter cumulates over the reporting period the time during which a GCH is busy in the cell. Maximum number of busy GCH (16k channel) in the cell.
P105 i / j
P469
NB_DL/UL_TBF_EST_FAIL_CONG_ABIS
MAX_NB_DEFICIT_GCH
Number of DL/UL TBF establishment failures due to a lack of Abis resources.

Maximum number of GCH in deficit reached in the cell.
P470
P471 P472 P474
CUMULATED_TIME_DEFICIT_GCH
CUMULATED_TIME_EXCESS_GCH CUMULATED_TIME_FREE_EXTRA_BONU S_ABIS_NIBBLES CUMULATED_TIME_FREE_ATER_NIBBLE S MIN_NB_FREE_EXTRA_BONUS_ABIS_NI BBLE MIN_NB_FREE_ATER_NIBBLE
Cumulative time (in seconds), per cell , during which there is a deficit of GCH resources (16k channel).
Cumulative time (in seconds), per cell ,during which there is a excess of GCH resources (16k channel). Cumulative time (in seconds), per BTS ,during which there are free extra and bonus Abis nibbles available. Cumulated time during which a PDCH is used by at least one DL TBF (in GPRS or EGPRS mode), cumulated over all the PDCHs of the cell. Minimum number of free extra and bonus Abis nibbles. Minimum number of free Ater nibbles.
P484 P486
Page 28
www.alcatel.com

2-Claro B9 Enhanced Transmission Resource Management

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

2-Claro B9 Enhanced Transmission Resource Management

Încărcat de

Drepturi de autor:

Formate disponibile

Enhanced Transmission Resource Management

B9 Claro Workshop - February 14th, 2006

All rights reserved 2005, Alcatel

Enhanced Transmission resource management

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing

B8: one EGCH per RTS

B9: one M-EGCH link for the whole TRX

1 to 5 GCHs depending on the TRX class

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing

RLC/MAC PDU 2 for DBN=x

320 bits DBN=x GCH1 GCH2 GCH3 GCH4 GCH5

Dummy Filling PDU

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing

RB1 RB1 RB2 RB2 RB3

RB1 RB2 RB1 RB2 RB3

RB1 RB1 RB2 RB2 RB3

GCH 2 GCH 3 GCH 4

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing

But the size of an EGCH link cannot be dynamically increased.

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

Enhanced Transmission resource management

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

Dynamic Abis Allocation

B8: static Abis allocation

B9: dynamic Abis allocation

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

No more constraints in B9!

Dynamic Abis Allocation

In B8, the following Abis nibbles were wasted:

Basic Abis nibbles

TRX configuration on the air interface

: Abis nibble used

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

Dynamic Abis Allocation

In B9, the following Abis nibbles are usable for PS traffic:

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

Dynamic Abis Allocation

All the extra Abis nibbles of the BTS:

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

Dynamic Abis Allocation

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

Dynamic Abis Allocation

notify each TRE which Abis nibbles are associated..

New scenario appear to distribute GCH resources :

B9 Claro Workshop / February 14th 2006

All rights reserved 2005, Alcatel

Enhanced Transmission resource management