You are on page 1of 108

B9 Parameter Workshop Part 2: Packet Switched (PS) Aspects

Presentation to T-Mobile, Bonn, 11 Oct 2005 Alcatel-PCS

All rights reserved 2005, Alcatel

Agenda
Page 2

B9 features and related parameters:


Enhanced support of E-GPRS in UL (8-PSK in UL and IR in UL) Extended UL TBF mode Enhanced Packet cell reselection Enhanced Transmission resource management

Channel allocation strategy in B9 for PS transfers :


Modification of the PDCH allocation strategy Modification of the TBF allocation/re-allocation strategy

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

Introduction
Page 3

This feature is part of EGPRS package. It is divided into two sub features:
Support of 8-PSK in Uplink
The "8-PSK in UL" feature proposes to introduce the 8-PSK modulation in UL, which permits to use the MCS-5 to MCS-9 coding schemes in the BSS (in B8 only the MCS-1 to MCS-4 are supported in UL).

Support of Incremental Redundancy in Uplink


The "Incremental Redundancy in UL" feature proposes to introduce the incremental redundancy in UL which permits to improve the decoding performances of the BTS with EGPRS. This is particularly useful when mobiles are at the border of the cells where a gain up to 15 % of throughput can be expected according to simulations.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

Content
Page 4

Support of 8-PSK in Uplink

Support of Incremental Redundancy in Uplink

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

8-PSK in Uplink feature


Page 5

The feature introduces 8-PSK modulation supported in UL.


Maximum data rate for difference coding scheme
The 8-PSK is a modulation technique that compare to GMSK allows up to 3 times more data to be transmitted over the GSM air interface. The 8PSK supports MCS-5 to MCS-9 coding schemes, which permit to achieve higher throughput when the radio conditions are good enough.
Modulation GMSK GMSK GMSK GMSK 8-PSK 8-PSK 8-PSK 8-PSK 8-PSK Coding Scheme MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9 Throughput (kbits/sec) 8.4 11.2 14.8 17.6 22.4 29.6 44.8 54.4 59.2

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

8-PSK in Uplink feature


Page 6

The MCS-5 to MCS-9 coding schemes will be used in RLC acknowledged and unacknowledged mode.
Support 8-PSK in RLC acknowledged & unacknowledged mode
The link adaptation mechanism in uplink is based on measurements (MEAN_BEP, CV_BEP) done by the BTS on the radio blocks received from the mobile. To take into account MCS-5 to MCS-9 in uplink, the BSS algorithm for link adaptation needs new link adaptation MEAN_BEP/CV_BEP tables, which are the same as the ones already used for downlink. The MCS selected by the BSS is indicated in the "EGPRS modulation and coding" IE included in the PACKET UPLINK ACK/NACK message. The TRX shall transmit the MEAN_BEP and CV_BEP of the RLC data block which is received with a correctly decoded RLC/MAC header, whether the payload is correctly decoded or not. The TRX will discard the RLC/MAC blocks when the header has not been successfully decoded.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

Content
Page 7

Support of 8-PSK in Uplink


Support of Incremental Redundancy in Uplink

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

Incremental Redundancy in Uplink feature


Page 8

The incremental redundancy (type II hybrid ARQ) is used with EGPRS data blocks sent on RLC acknowledged mode using MCS-1 to MCS-9.
Support of Incremental Redundancy in Uplink
The incremental redundancy is based on reception of RLC data blocks coded with different puncturing schemes, so that the BTS may enhance the decoding of the RLC data block with soft combining. By taking into account the erroneous RLC data blocks and combining them with the retransmitted RLC data blocks, the BTS receiver increases the probability of decoding them correctly and reduces the number of times it uses a slower coding scheme compared to the situation where incremental redundancy is not used and therefore the average throughput is increased.

Interaction with re-segmentation on UL


As for DL, incremental redundancy cannot be applied when the RLC datablocks are re-segmented with a different number of payloads.
TMD_B9_pres_PS_part / Oct 05
All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

Incremental Redundancy in Uplink feature


Page 9

MCS retransmission schemes :


GMSK
MCS1 MCS2 Family C MCS3 MCS4 MCS5 MCS6

8PSK
MCS7 MCS8 MCS9

22

22

22

Resegmentation required Incremental Redudancy not possible


28 28 28 28 28 28

Family B

28

Family A padding

34+3

34+3 34+3

34 34

34 34

37 Family A

37

37

37 37

37 37

RLC data block

28

unit of payload (in bytes)

Resegmentation not required Incremental Redudancy possible

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

Incremental Redundancy in Uplink feature


Page 10

IR is configured in the MFS by parameter EN_IR_UL.


When EN_IR_UL = Enable, the MFS shall:
Use incremental redundancy with all MSs. Give the [TFI, RTS] combinations, used by TBF, to the TRX.

Remark: The Incremental Redundancy for the uplink TBF feature is supported only on G4 BTSs.

When EN_RESEGMENTATION_UL = Enable, the MFS shall:


Set 1 (re-segmentation) to RESEGMENT bit in the PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT and PACKET TIMESLOT RECONFIGURE messages.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

ENHANCED SUPPORT of EGPRS IN UPLINK

Related parameters
Page 11

HMI name

Definition

Subsyst em MFS

Instan ce BSS

OMC-R access Change able

Type

Def value 0

Range

Unit

NEW : EN_IR_UL

Enables/Disables Incremental redundancy for the uplink TBF in the BSS. Enables/Disables the re-segmentation for the uplink TBF in the BSS Value of the uplink modulation and coding scheme when the link adaptation algorithm is disabled or initial value of the modulation and coding scheme otherwise. Supervision timer for TBF context configuration in a TRX

Flag

[0,1]

None

NEW : EN_RESEGMENTATION_ UL MODIFIED : TBF_UL_INIT_MCS

MFS

BSS

Change able

Flag

[0,1]

None

MFS

Cell

Change able

Number

[1,9]

None

NEW : T_CONFIG_TBF

MFS

MFS

None (DLS)

Timer

280

[200,4 00]

ms

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Agenda
Page 12

B9 features and related parameters:


Enhanced support of E-GPRS in UL (8-PSK in UL and IR in UL) Extended UL TBF mode Enhanced Packet cell reselection Enhanced Transmission resource management

Channel allocation strategy in B9 for PS transfers :


Modification of the PDCH allocation strategy Modification of the TBF allocation/re-allocation strategy

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

EXTENDED UPLINK TBF MODE

Introduction
Page 13

The aim of this feature is to extend the duration of the UL TBF in order:
To quickly restart data transmission in UL if higher layers in the MS deliver new data, without having to re-establish a new UL TBF, after the countdown procedure has started To maintain the UL TBF established, some time after the last block (CV=0) has been acknowledged by the network
This feature allows improving access time to the GPRS network. It also improves the throughput in some cases. The feature is described in 3GPP TS 44.060 - V4.18.0. It applies only for R4 MS

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

EXTENDED UPLINK TBF MODE

Functional description
Page 14

The BSS shall:


1. 2. Enable or disable the Extended uplink TBF mode through an O&M parameter, EN_EXTENDED_UL_TBF. And configure an inactivity period as duration of extended uplink TBF mode, T_MAX_EXTENDED_UL. Indicate to MS that the network supports the extended uplink TBF mode. The MS is aware of the BSS capability by the NW_EXT_UTBF parameter that is broadcast on either BCCH (SI13)or PBCCH (PSI1). So the MS is always aware of the BSS capability before establishing an Uplink TBF. On the contrary the BSS does not always know the MS capability when the first Uplink TBF is established at the beginning of a session. Detect whether or not a given MS supports the Extended Uplink TBF Mode. The MS radio access capability is received at downlink TBF establishment in the first downlink PDU. In case of cell reselection for an uplink transfer, some time TBF may elapse before a Downlink PDU is received. Radio Access Capability Update procedure is used to obtain the information. Apply the Normal release mode (with delayed final PUAN) if the MS does not support the Extended Uplink TBF Mode or if the BSS does not know MS capability. Switch to Extended Uplink TBF Mode when a MS is detected to support the feature, when the Radio Access Capabilities are received during the UL transfer. Maintain to USF scheduling an uplink TBF during the inactivity period, while the MS has no data to transmit, and maintain the reception of uplink RLC data block as long as the uplink TBF is in extended phase. Release the uplink TBF upon timer T_max_extended_UL expiry

3.

4.

5.
6.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

EXTENDED UPLINK TBF MODE

Acquiring MS capability
Page 15

Radio Access Capability Update


Enable or disable the Radio Access Capability update on Gb by flag, EN_RA_CAP _UPDATE. Recommend to enable this flag if EN_EXTENDED_UL_TBF is enabled and Radio Access Capability update is supported by SGSN. At UL TBF establishment, immediately after the contention resolution procedure, the radio access capability update procedure is triggered in the BSS. The BSS request an MSs current Radio Access capability and/or its IMSI by sending to an SGSN a RA_CAPABILITY_UPDATE, which includes the TLLI of the MS and a Tag. Then starts timer T5_RA_CAPABILITY_UPDATE. In case of the timer expiry, BSS shall repeat the request up to RA_CAPABILITY_UPDATE_RETRIES times (value = 3). The SGSN shall respond by sending a RA_CAPABILITY_UPDATE_ACK, which includes the TLLI of the MS, the Tag received in the corresponding RA_CAPABILITY_UPDATE. When the SGSN answers, the MS Radio Access capability is updated and the Extended UL feature can be used if the GERAN Feature Package 1 bit is set. Otherwise, the MS does not support the extended uplink feature.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

EXTENDED UPLINK TBF MODE

Scheduling USF
Page 16

Principle to design USF scheduling


USF for extended mode are scheduled only on the PDCH, which carries PACCH. IF the PDCH supports uplink TBF, which all are in extended mode, Then,
if flag EN_FAST_USF_UL_EXTENDED = enable then the throughput in radio blocks is equally shared between MS (round robin of one RLC block per MS). So USF are scheduled as follows: One MS in extended mode on PACCH: USF scheduled every 20ms Two MS in extended mode on PACCH: USF scheduled every 40ms n MS in extended mode on PACCH: USF scheduled every n x 20m ELSE (if the flag EN_FAST_USF_UL_EXTENDED is disabled or if the PDCH supports at least one MS which is in UL transfer) A polling period T_extended_UL_TBF_POL, is used for all MS in extended phase. A default value is 200ms. The remaining bandwidth is used for MS in transfer.

RRBP mechanism has priority above USF scheduling. This means the USF scheduling may be shifted if RRBP request from RLC.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

EXTENDED UPLINK TBF MODE

Interaction with concurrent DL TBF (1/2)


Page 17

UL transfer stops when DL is still in transfer


If timer T_max_extended_UL expires while the DL TBF is still in transfer, then the UL TBF is released with no impact on the downlink TBF.
DL UL T_max_extended_UL In transfer Extended mode T_max_extended_UL expires, then UL TBF is released while DL goes on

If the DL transfer stops while the uplink TBF has switched to extended state, then the timer T_Network_response time is started to supervise the maximum duration of the delayed downlink TBF.
(1) Last UL data block: the UL TBF switches to extended mode. Timer T_max_extended_UL is started
DL UL T_NW_response_time T_max_extended_UL T3192 event (1) (2) (3) In transfer delayed Extended mode T_NW_response_time expires still running T3192 expires T3192

(2) Last DL LLC PDU; DL TBF enters delayed mode. The timer T_network response time is started. The polling policy is exactly the same as for a delayed DL TBF with a concurrent UL in transfer (T_delayed_DL_TBF_poll_UL). (3) T_network_response time expires, then the release of the DL TBF is initiated and T3192 is started. The uplink TBF in extended mode is released when either T3192 expires or T_max_extended_UL expires.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

EXTENDED UPLINK TBF MODE

Interaction with concurrent DL TBF (2/2)


Page 18

DL transfer stops when UL still in transfer


(1)
(2) (3)

(4)

If the DL transfer enters delayed mode, while the uplink is still in transfer, no timer is started. the last UL block is received, while the downlink is in delayed mode. Timer T_network_response time and T_max_extended_UL are started. T_network_response time expires, then the release of the DL TBF is initiated and T3192 is started. The uplink TBF in extended mode is released when either T3192 expires or T_max_extended_UL expires
DL UL T_NW_response_time T_max_extended_UL T3192 event (1) (2) (3) T3192 expires => release extended UL In transfer delayed T3192 Extended mode T_NW_response_time expires

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

EXTENDED UPLINK TBF MODE

Related parameters
Page 19
HMI name NEW : EN_EXTENDED_UL_TBF NEW : T_MAX_EXTENDED_UL NEW : EN_FAST_USF_UL_EXT ENDED NEW : EN_RA_CAP_UPDATE Definition Flag to disable/enable the extended TBF mode feature on the uplink Maximum duration of the extended uplink TBF phase Flag to disable/enable the transmission of USF every 20ms in extended mode Flag to enable/disable the Radio Access Capability update on Gb Subsystem MFS Insta nce cell OMC-R access Changeable Type Flag Def value 0 Range [0,1] Unit None

MFS

cell

Changeable

Timer

2000

[100,40 00] [0,1]

ms

MFS

BSS

Changeable

Flag

None

MFS

BSS

Changeable

Flag

[0,1]

None

NEW : RA_CAPABILITY_UPDAT E_RETRIES


NEW : T_EXTENDED_UL_TBF_ POL NEW : T5_RA_CAP_UPDATE

Maximum number of repetition of Radio Access capability in case of no answer from SGSN at T5 expiry.
To control the USF scheduling on the uplink when a TBF is in extended TBF mode Timer to supervise the reception of the MSs current Radio Access capability from the SGSN on Gb.

MFS

MFS

None (DLS)

Number

None

MFS

MFS

None (DLS)

Timer

200

[120,50 0]

ms

MFS

MFS

None (DLS)

Timer

[1,30]

sec

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Agenda
Page 20

B9 features and related parameters:


Enhanced support of E-GPRS in UL (8-PSK in UL and IR in UL) Extended UL TBF mode Enhanced Packet cell reselection Enhanced Transmission resource management

Channel allocation strategy in B9 for PS transfers:


Modification of the PDCH allocation strategy Modification of the TBF allocation/re-allocation strategy

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Introduction
Page 21

The Enhanced Packet Cell Reselection feature includes sub-features allowing to reduce cell reselection duration and to avoid (NC2 mode) to direct MS towards high loaded cells.
Reduction of the service outage during packet cell reselection (NC0 and NC2 modes) :
Network Assisted Cell Change Procedures (NACC) : MS acquires target cell (P)SI in the serving cell. Only for R4 MS. Packet (P)SI Status procedure : access to a new cell without having previously acquired the full set of P(SI). Mainly for R4 MS.

In NC2 mode, prevention from directing MSs towards high loaded cells, where the MS can be served with non-optimum resources, or even worse, rejected due to congestion
NC2 improvement : Cell ranking with load criteria

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Content
Page 22

Network Assisted Cell Change


NACC NC0 NACC NC2

Packet (P)SI Status


Packet SI Status Packet PSI Status

NC2 improvement

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Network Assisted Cell Change (NACC)


Page 23

The NACC takes place in serving cell and consists of 2 independent procedures:
CCN mode procedure (Cell Change Notification)
Procedure in MS to notifies the network when the cell reselection is decided in Packet Transfer Mode and delays the cell reselection to let the network act on need, eventually through the Cell System Information distribution procedure.

Cell System Information distribution


Procedure to assist an MS in Packet Transfer Mode with target cell system information required for initial packet access after a cell change. This information is sent to the MS in the serving cell and before the cell change is performed. Cell A
Partial Sys Info. of Cell B

Cell B

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Network Assisted Cell Change - NC0 (1/2)


Page 24

When EN_NACC =enable, the CCN mode is ordered through System Information to all R4 MSs supporting GERAN feature package 1 in the cell. Scenario describes the NACC procedure in NC0 mode
MS Cell A Cell B

(1) T3206 monitors the sending of Ongoing data transfer the Packet Cell Change Target cell choice (1) Notification. RLC data block polling (2) At receipt of the PACKET CELL Packet Cell Change Notification (2) CHANGE NOTIFICATION Retrieval PSI instances message, the MFS checks of the chosen cell (3) whether the proposed cell Packet Neighbor Cell Data (PSI14) belongs to the same BSS as Packet Neighbor Cell Data (PSI1) the serving cell. If the proposed cell does not belong to the Packet Neighbor Cell Data (PSI2-first instances) same BSS (BSC_ID(n) (target Packet Neighbor Cell Data cell) <> BSC_ID (serving cell)), (PSI2-intermediate instances) a PACKET CELL CHANGE Packet Neighbor Cell Data (PSI2-last instances) CONTINUE (PCCC) message Packet Cell Change continue (4) is sent to the mobile station without sending any neighbor Note: The figure above covers the case where there is a PBCCH in the target cell. When there is no PBCCH channel in the target cell, the same scenario takes place with BSS sends cell system information. the SI13, SI1 and SI3 messages instead of the PSI14, PSI1 and PSI2 messages.
T3206 T3210 T3208 T3208n

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Network Assisted Cell Change - NC0 (2/2)


Page 25

(3) In the case, the neighbor cell belongs to the same BSS, RRM starts the timer T3208n (T3208 RTD) that monitors the sending of the PCCC and retrieves the SI13 / SI1 / SI3 or PSI14 / PSI1 / PSI2 instances currently broadcast in the neighbor cell and requests MAC to send the relevant (P)SI to the MS if the target cell supports a PBCCH channel, RRM encodes the PSI14, PSI1 and PSI2 instances of that cell in one or multiple instances of the PACKET NEIGHBOR CELL DATA message which are sent to the MS, followed by a PACKET CELL CHANGE CONTINUE message . if the target cell does not support a PBCCH channel, RRM encodes the SI13, SI1 and SI3 instances of that cell in one or multiple instances of the PACKET NEIGHBOR CELL DATA message. When the MS sends the Packet Cell Change Notification message, the MS activates the timer T3210 to wait for a response from the BSS, if timer expiry, the Packet Cell Change Notification is retransmitted. The MS also activates the timer T3208 to wait for PACKET CELL CHANGE CONTINUE from the BSS (at timer expiry, the MS will continue the cell reselection in NC0 mode). (4) When RLC has sent all the instances of the PACKET NEIGHBOUR CELL DATA message, the PACKET CELL CHANGE CONTINUE (PCCC) message is sent on the PACCH of the MS and the timer T3208n is stopped. It is to be noted that no PCA is requested to acknowledge the PCCC (No T_Ack_Wait timer is launched by the BSS when sending the PCCC because at the timer expiry, the mobile station has already left the CCN mode either because it has received the PCCC or because T3208 has already expired and it is not necessary to send the PCCC again). When the mobile station receives the PACKET CELL CHANGE CONTINUE message, it shall leave CCN mode and continue cell reselection in NC0 mode.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Network Assisted Cell Change - NC2 (1/2)


Page 26

NC2 cell reselection execution in NC2 mode


(1) (2) (3) An UL or DL TBF is assumed on-going. The MS sends a Packet Measurement Report message on one of the allocated UL block on PACCH Upon receipt of the Packet Measurement Report message, the BSS detects that a cell reselection must be triggered. It finds out that the target cell, belongs to the same BSS, and the MS supports the acquisition of neighbor cell (P)SI. The BSS sends the PNCDs to the MS, on all the PDCHs of the TBF, to transmit the (Packet) System Information for the target cell: SI13, SI1 and SI3 for a target cell without PBCCH or PSI14 (containing the same information as SI13), PSI1 and a consistent set of PSI2 for a target cell with a PBCCH. In case both a UL and a DL TBF exist, PNCDs are sent on the DL TBF.
MS
Ongoing UL or DL TBF (1) Packet Measurement Report / PACCH (2) (3) Packet Neighbor Cell Data / PDCHs (4) Packet Neighbor Cell Data / PDCHs Packet Cell Change Order / PACCH (5) (6) Packet Control Acknowledgement / PACCH (7) T_ACK_WAIT

(4)

BSS Serving cell

BSS Target cell

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Network Assisted Cell Change - NC2 (2/2)


Page 27

(5)

When all the PNCDs have been sent, the BSS orders the MS to reselect a new cell by sending a Packet Cell Change Order message on the PACCH of the DL or UL TBF. If both an UL and a DL TBFs are on-going, the message is preferentially addressed by a DL TFI. The Packet Cell Change Order message is sent in acknowledged mode and contains the ARFCN and the BSIC of the target cell. When sending the Packet Cell Change Order message, the BSS starts the timer T_ACK_WAIT to monitor the receipt of the Packet Control Acknowledgement message. (6)-(7) Upon receipt of the Packet Cell Change Order message, the MS aborts its on-going TBF in the serving cell and sends the Packet Control Acknowledgement message, then switches to the new cell.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Content
Page 28

Network Assisted Cell Change


NACC NC0 NACC NC2

Packet (P)SI Status


Packet SI Status Packet PSI Status

NC2 improvement

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Packet (P)SI Status


Page 29

Packet (P)SI status feature allows MS to make an access to a new cell without having previously acquired the full set of SYSTEM INFORMATION (resp. PACKET SYSTEM INFORMATION if PBCCH is present in the target cell) messages sent on the BCCH channel (resp. PBCCH) of the target cell. The Packet (P)SI Status procedure takes place in the target cell if in this cell, EN_PSI_STATUS = Enable.
Packet PSI Status procedure is a feature standardized from Release 97 onwards, optional for Release 97, Release 98 and Release 99 MS, and mandatory for Release 4 onwards MS supporting GERAN Feature Package 1. Packet SI Status procedure is a new feature standardized in Release 4, mandatory for Release 4 onwards mobile stations supporting GERAN Feature Package 1. Cell A
Partial Sys Info.

Cell B
Remaining Sys Info.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Packet SI Status (1/2)


Page 30

Scenario of the Packet SI Status procedure


(1) When reselecting a new cell without a PBCCH channel and supporting the PACKET SI STATUS procedure (EN_PSI_STATUS = enable), the MS can immediately request the establishment of an uplink TBF provided it has acquired the SI13, SI3 and SI1 message (if present) of this new cell. It can then send a cell update or restarts its on-going data transfer. (2) The MS asks BSS to provide the missing system information by sending a PACKET SI STATUS message on PACCH.
MS Cell A
RLC data block (1) Packet SI status (SI2, SI2bis, SI2ter message type missing) (2)

Cell B

Scheduling of the serving cell SI message to MS

T_PSCD_SCHE DULE_ACK (3)

Packet serving cell data (SI2 message) (4) Packet serving cell data (SI2bis message) Packet serving cell data (SI2ter message)

Completion of UL LLC PDU transfer RLC data block Packet Uplink ACK/NACK

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Packet SI Status (2/2)


Page 31

(3) When receiving the MS request, if a downlink TBF is already established, or if a downlink TBF is being established, or if a downlink TBF will soon be established (DL LLC PDU are being rerouted to the new cell), then the BSS shall wait until full establishment of the DL TBF to send requested SIs on all the downlink PDCHs allocated to the MS. Otherwise, SIs are sent on all the PDCHs of the uplink TBF. A supervision timer (T_PSCD_SCHEDULE_ACK) is started to monitor the sending of the SI messages to the mobile. (4) The SI instances are encapsulated in one or multiple instances of a PACKET SERVING CELL DATA message and sent individually to the mobile station. When the last SI is sent to the mobile, T_PSCD_SCHEDULE_ACK is stopped (RLC indicates to RRM that all the SIs have been sent).

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Packet PSI Status (1/2)


Page 32

Scenario of the Packet PSI Status procedure


(1) When reselecting a new cell with a PBCCH channel and supporting the PACKET PSI STATUS procedure (EN_PSI_STATUS = enable), the MS can immediately request the establishment of an UL TBF, provided it has acquired the PSI14, PSI1 and PSI2 messages of this new cell. It can then send a cell update or restarts its on-going data transfer. (2) The MS asks the BSS to provide the missing system information by sending a PACKET PSI STATUS message on a PACCH block.
MS Cell A
RLC data block (1) Packet PSI status (PSI3, PSI3bis missing) (2) Scheduling of the serving cell PSI messages to MS

Cell B

T_PSCD_SCHEDULE_ ACK (3)

Packet serving cell data (PSI3 message) Packet serving cell data (PSI3bis message) - first instance Packet serving cell data (PSI3bis message) - intermediate instance Packet serving cell data (PSI3bis message) - last instance Completion of UL LLC PDU transfer RLC data block Packet Uplink ACK/NACK

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Packet PSI Status (2/2)


Page 33

(3) When receiving the MS request, if a DL TBF is already established, or is being established, or will soon be established (DL LLC PDU are being rerouted to the new cell), then the BSS shall wait until full establishment of the DL TBF to send requested PSIs on all the downlink PDCHs allocated to the MS. Otherwise, PSIs are sent on all the PDCHs of the uplink TBF. A supervision timer (T_PSCD_SCHEDULE_ACK) is started to monitor the sending of the PSI messages to the mobile. (4) When the last PSI is sent to the mobile, T_PSCD_SCHEDULE_ACK is stopped.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Content
Page 34

Network Assisted Cell Change


NACC NC0 NACC NC2

Packet (P)SI Status


Packet SI Status Packet PSI Status

NC2 improvement

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

NC2 improvement (1/4)


Page 35

Cell load evaluation


NC2 load sampling
The NC2 load is sampled every T_NC2_LOAD_RANKING seconds by dividing the used bandwidth by the total bandwidth available in the cell

with:
UL_PS_used_Bandwidth => bandwidth used by PS traffic in the UL direction DL_PS_Used_Bandwidth => bandwidth used by PS traffic in the DL direction, CS_Used_Bandwidth => bandwidth used by CS traffic Total_PS_Bandwidth => total bandwidth available in the cell.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

NC2 improvement (2/4)


Page 36

UL_PS_Used_Bandwidth
nULTBF,i defines the number of UL TBFs on the allocated PDCH i. NULTBF is the maximum number of UL TBFs that can be pilled up on the PDCHs (defined by the parameter MAX_UL_TBF_SPDCH).

BUL , i

nUL TBF , i NUL TBF

The UL PS used bandwidth is then defined as the sum of the bandwidth used by the UL TBFs over all the PDCHs allocated to the MFS.

BUL
DL_PS_Used_Bandwidth

N_PDCH_ALL OCATED i 1 UL , i

In the DL direction, the DL used bandwidth is computed in a similar way as the UL direction.

CS_Used_Bandwidth
The bandwidth used by the CS traffic is defined by the difference between:
The maximum number of slave PDCHs that can be allocated in the cell (number of slave PDCHs = MAX_PDCH NB_TS_MPDCH) , The number of slave PDCHs currently allocated to the MFS in the cell

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

NC2 improvement (3/4)


Page 37

Example:
It is assumed:

Time Slot 3 2 1 BDL , i 1/3+1/3=2/3 DL TBF3 DL TBF1 1/3+1/3=2/3 1/3+1/3=2/3 1/3 1/3 DL TBF2 1/3 1/3 0 CS

The following repartition of the DL TBFs is used, The UL_PS_Used_Bandwidth is lower than the DL_PS_Used_Bandwidth. Thus, it is not computed. N_PDCH_ALLOCATED = 8; MAX_DL_TBF_SPDCH = 3 MAX_SPDCH = 8 and 7 slave PDCHs are allocated to the MFS.
0 1 2 3 4 5 6 7

In this example, the total bandwidth is equal to 8, the DL_PS_used_bandwidth is equal to 4x1/3 + 3x2/3 = 10/3. Therefore, the NC2_load is equal to [(10/3)+ 1]x100/8 = 13x100/24 = 54.16 %

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

NC2 improvement (4/4)


Page 38

NC2 load averaging


The NC2 load samples are further averaged using a sliding window. The size of the sliding window is defined by the parameter NC2_LOAD_EV_PERIOD.

Load evaluation of internal BSS cells


Every T_NC2_LOAD_RANKING, the BSS compares the computed NC2 load of the cell to the threshold THR_NC2_LOAD_RANKING:
If the NC2 load average is lower than or equal to the threshold, the cell is considered in a low load situation If the NC2 load average is higher than the threshold, the cell is considered in a high load situation.

The MFS shares the NC2 load situation information among the different cells of the BSS (or at least between the cells having a cell reselection link to the serving cell), i.e. low/high load. That exchange of information is taking place every MULTI_GPU_INFO_BROADCAST_PERIOD.

Load evaluation of external BSS cells


All external cells to the BSS will always be considered as in low load situation, because of the threshold THR_NC2_LOAD_RANKING of an external cell is unknown for the BSS.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

NC cell reselection ranking


Page 39

The NC2 cell ranking process consist of 2 cases.


Case 1: there is a PBCCH in the serving cell
The cell ranking list is built as follows:
Cells with C31NC2 > 0
NC2_Load situation [low => high PS load]; Cell PRIORITY_CLASS [high => low]; C32NC2 [high => low] C32NC2 [high => low]
high

C31NC2 NC2_load PRIORITY_CLASS C32NC2


low

priority

Cells with C31NC2 < 0

Case 2: there is no PBCCH in the serving cell


The cell ranking list is built as follows:
Cells with C31NC2 > 0
NC2_Load situation [low => high PS load]; C2NC2 [high => low] C2NC2 [high => low]
high

C31NC2 NC2_load C2NC2


low

priority

Cells with C31NC2 < 0

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Packet Cell Reselection

Related parameters
Page 40
HMI name Definition Subsystem
MFS MFS

Insta nce
cell MFS

OMC-R access
Changea ble None (DLS)

Type

Def value
0 0.8

Range

Unit

NEW : EN_NACC NEW : T3208n

Enables the Network Assisted Cell Change feature. Timer guarding on network side the sending of Packet Neighbor Cell Data messages for NACC feature. It is started at reception of Packet Cell Change Notification message, and stopped when all PNCDs have been sent to MS (as indicated by RLC layer to RRM layer). Enables the Packet SI Status feature in cells w/o PBCCH or the Packet PSI Status feature in cells with a PBCCH. Timer guarding on network side the sending of Packet Serving Cell Data or PSI messages for Packet (P)SI Status feature. It is started at reception of Packet PSI Status / Packet SI Status message, and stopped when all PSCDs / PSIs have been sent to the mobile (as indicated by RLC layer to RRM layer). Period of the cell load evaluation for the NC2 cell ranking process Number of NC2 load samples used to compute the NC2 load average Threshold above which the load of the serving cell is considered in a high load situation in the NC2 cell ranking process RRM reporting period to update the information (per cell) necessary for the Multi-GPU feature.

Flag Timer

[0,1] [0,1]

None sec

NEW : EN_PSI_STATUS NEW : T_PSCD_SCHEDULE_ ACK

MFS

cell

Changea ble None (DLS)

Flag

[0,1]

None

MFS

MFS

Timer

0.84

[0,2]

sec

NEW : T_NC2_LOAD_RANKIN G NEW : NC2_LOAD_EV_PERIO D NEW : THR_NC2_LOAD_RAN KING NEW : Multi_GPU_INFO_BRO ADCAST_PERIOD

MFS

MFS

None (DLS) None (DLS) Changea ble None (DLS)

Timer

[1,100]

sec

MFS

MFS

Numb er Thres hold Timer

[3,30]

None

MFS

cell

[0,100]

None

MFS

MFS

10

[1,255]

sec

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Agenda
Page 41

B9 features and related parameters:


Enhanced support of E-GPRS in UL (8-PSK in UL and IR in UL) Extended UL TBF mode Enhanced Packet cell reselection Enhanced Transmission resource management

Channel allocation strategy in B9 for PS transfers:


Modification of the PDCH allocation strategy Modification of the TBF allocation/re-allocation strategy

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Transmission Resource Management

Contents of the presentation


Page 42

M-EGCH Statistical Multiplexing Dynamic Abis Allocation Ater Resource Management DL Retransmission in the BTS

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing


M-EGCH link (I)
Page 43

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.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing


M-EGCH link (II)
Page 44

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


TMD_B9_pres_PS_part / Oct 05

1 to 36 GCHs

All rights reserved 2005, Alcatel

GCH

GCH

M-EGCH Statistical Multiplexing


Filling an M-EGCH link with PDUs (I)
Page 45
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

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing


Gains brought by the feature
Page 46

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.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

M-EGCH Statistical Multiplexing


Towards Dynamic Abis allocation
Page 47

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.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Dynamic Abis Allocation


Static versus Dynamic Abis allocation
Page 48

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)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

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

Dynamic Abis Allocation


Abis nibbles wasted in B8
Page 49

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

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Dynamic Abis Allocation


Abis nibbles usable for PS traffic (I)
Page 50

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

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Dynamic Abis Allocation


Abis nibbles usable for PS traffic (II)
Page 51

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.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Dynamic Abis Allocation


Level of sharing of the Abis nibbles usable for PS traffic
Page 52

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.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Dynamic Abis Allocation


Impacts on existing scenarios and new scenarios
Page 53

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

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Ater Resource Management


Principles
Page 54

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).

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Ater Resource Management


GPU Ater TS Margin
Page 55

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.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Ater Resource Management


High Ater usage handling (I)
Page 56

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.

Decision based on the comparison of the Ater nibble consumption with a threshold (Ater_Usage_Threshold O&M parameter).

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Ater Resource Management


High Ater usage handling (II)
Page 57

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.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Ater Resource Management


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 58

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

DL retransmission in the BTS


Principles
Page 59

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.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

DL retransmission in the BTS


Principles
Page 60

This mechanism is enabled / disabled at TRX/TRE level:


EN_DL_RETRANS_B TS Round_Trip_Dela y

Enabled Enabled disabled

< 500 ms 500 ms -

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

Gains:

Higher available transmission bandwidth.


M-EGCH link dimensioning is eased.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Transmission Resource Management

Related parameters
Page 61
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_AC CESS

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

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Enhanced Transmission Resource Management

Related parameters
Page 62
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_H IGH_ATER_USAGE NEW : EN_DL_RETRANS_BTS

MFS

cell

Changea ble None (DLS)

Numb er Flag

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

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Agenda
Page 63

B9 features and related parameters:


Enhanced support of E-GPRS in UL (8-PSK in UL and IR in UL) Extended UL TBF mode Enhanced Packet cell reselection Enhanced Transmission resource management

Channel allocation strategy in B9 for PS transfers :


Modification of the PDCH allocation strategy Modification of the TBF allocation/re-allocation strategy

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation


Page 64

In B8:
The BSC evaluates the number of timeslots that the MFS could use to carry PS traffic (Max_SPDCH_Dyn),
The MFS does not know which timeslots are usable for PS traffic, To serve a new TBF, the MFS needs to request new timeslots to the BSC. Event-triggered mechanism
Max_SPDCH_Dyn = 8

TS allocated to BSC
TS allocated to MFS

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation


Page 65

In B9, the following new needs have appeared:


Need to know the list of basic Abis nibbles which are currently available to establish GCHs, Need to know which basic Abis nibbles are preemptable / notpreemptable for CS traffic by the BSC. This information is useful: For the QoS feature (in order to be able to ensure a given GBR for an RT PFC). To define some priorities in the Abis nibble selection (preference is given to the non-preemptable basic Abis nibbles in order to limit the interaction of CS over PS traffic). Need to accelerate TBF establishment times (the B8 round trip delay between MFS and BSC to allocate some PDCHs can be avoided).

To meet all those needs, a process called Autonomous Packet Resource Allocation has been introduced in B9.
TMD_B9_pres_PS_part / Oct 05
All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation


Page 66

In B9:
The BSC evaluates a number of timeslots that the MFS can use to carry PS traffic (Max_SPDCH_Limit), Periodical exchange of messages between the BSC and the MFS:
BSC to MFS: list of RTS that the MFS can use, MFS to BSC: acknowledgement of allocated / de-allocated RTS.

The MFS knows which timeslots can be used to serve a new TBF. Periodical mechanism

Max_SPDCH_Limit = 8 TS allocated to BSC TS allocated to MFS

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation


Page 67

CS/PS sharing is based on the evaluation of Max_SPDCH_Limit. The Max_SPDCH_Limit value:


Corresponds to a number of timeslots allocated to the MFS, Evaluated at the BSC level, Periodically, every TCH_INFO_PERIOD * RR_ALLOC_PERIOD, Transmitted to the MFS using the RR Allocation Indication message, Comprised between Min_SPDCH and Max_SPDCH.

The evaluation of Max_SPDCH_Limit is based on:


O&M parameters (Max_PDCH, Min_PDCH, Max_PDCH_HIGH_LOAD, HIGH_TRAFFIC_LOAD_GPRS, THR_MARGIN_PRIO_PS), CS and PS load, averaged using a sliding window of size Load_EV_Period_GPRS, PS load: provided to the BSC by the RR Usage Indication message. Sharing of unused TSs between CS and PS traffic.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation


Page 68

Radio Resource Allocation Indication message:


Sent by BSC to MFS, Periodically, every TCH_INFO_PERIOD * RR_ALLOC_PERIOD, SPDCHs_Allocation bitmap: contains information whether a timeslot is allocated to the MFS or not.

Radio Resource Usage Indication message:


Sent by MFS to BSC, Periodically, every TCH_INFO_PERIOD or in response to a RR Allocation Indication, SPDCHs_Confirmation bitmap: indicates or confirms whether a timeslot is allocated or not to the MFS, SPDCHs_Usage bitmap: provides occupancy states of timeslots allocated to the MFS.

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

TRX Priority
Page 69

The way to set the priority of the PS capable TRX (TRX_PREF_MARK = 0) is slightly modified in B9 release with the introduction of a frequency band criterion:
PS_PREF_BCCH_TRX HW TRE capability (G4 HP -> G4 MP -> G3) DR TRE capability (FR TRX -> DR TRX) E-GSM TRX preference (new in B9, E-GSM TRX -> PGSM/GSM850/DCS TRX) TRX having the maximum number of consecutive SPDCHs TRX identity (low TRX id -> high TRX id)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection
Page 70

PS TS and TRX ordering:


the first step consists in ordering the PS timeslots and the PS TRX so as to obtain an ordered list of TCH/SPDCH timeslots the ordering of the timeslots is based on the following criteria:
selection of the TRX: the TRX having the lowest rank in the TRX ranking table (refer to the slide on TRX priority) is selected first selection of the TS: once the TRX has been selected, the TCH/SPDCH timeslots having the lowest timeslot index, i.e. located at the most left side of the TRX, is selected first

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection
Page 71

Different PS TS zones:
MAX_SPDCH_HIGH_LOAD zone:
this zone corresponds to the MAX_SPDCH_HIGH_LOAD consecutive PS capable TS that are preferred for PS allocation in this zone, allocated TBFs cannot be pre-empted

Non pre-emptable PS zone:


this zone is always inside the MAX_SPDCH_HIGH_LOAD zone in this latter zone, we search for the rightest TS allocated to the MFS and used. Then, all the TS located at its left define the non pre-emptable PS zone inside this zone, a TS:
remains allocated to the MFS if already allocated to the MFS is allocated to the MFS if previously allocated to the BSC and unused remains allocated to the BSC if already allocated to the BSC and used

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection
Page 72

Different PS TS zones:
MAX_SPDCH_LIMIT zone:
this zone corresponds to the MAX_SPDCH_LIMIT consecutive PS capable TS that are preferred for PS allocation inside this zone, a TS:
remains allocated to the MFS if already allocated to the MFS is allocated to the MFS if previously allocated to the BSC and unused remains allocated to the BSC if already allocated to the BSC and used

PS traffic zone:
this zone corresponds to the larger zone between the non pre-emptable PS zone and the MAX_SPDCH_LIMIT zone

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection
Page 73

Different PS TS zones:
example: MAX_SPDCH_HIGH_LOAD = 8, MAX_SPDCH_LIMIT = 10
PS traffic zone MAX_SPDCH_LIMIT zone Non pre-emptable PS zone PS 1 PS 2 CS 3 PS 4 5 TRX2 PS 6 CS 7 8 PS 9 PS 10 CS 11 CS 12 13 TRX1 14 15 CS 16

MAX_SPDCH_HIGH_LOAD zone

example: MAX_SPDCH_HIGH_LOAD = 8, MAX_SPDCH_LIMIT = 3


PS traffic zone Non pre-emptable PS zone MAX_SPDCH_LIMIT zone PS 1 PS 2 3 CS CS PS 6 CS 7 8 CS 9 CS 10 CS 11 CS 12 13 TRX1 14 15 CS 16

4 5 TRX2

MAX_SPDCH_HIGH_LOAD zone

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection
Page 74

Selection of the TCH/SPDCH TS:


the process begins with the non pre-emptable PS zone:
all the TS in this zone that can be or are allocated to the MFS are allocated to the MFS. The verification in terms of number of TS allocated to the MFS is done only when all the TS inside this zone have been handled

if at the end of the non pre-emptable PS zone, the number of selected TS for the MFS is strictly lower than MAX_SPDCH_LIMIT then the process of selection continues in the MAX_SPDCH_LIMIT zone if at the end of the MAX_SPDCH_LIMIT zone, the number of selected TS for the MFS is still lower than MAX_SPDCH_LIMIT, the process continues outside this zone until this number reaches MAX_SPDCH_LIMIT once MAX_SPDCH_LIMIT TS have been selected, all the remaining TCH/SPDCH TS are now allocated to the BSC, even if they were previously allocated to the MFS. This means that a TS with a SPDCH allocation state set to allocated has its SPDCH allocation state set to de-allocating

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection
Page 75

Pre-reservation mechanism in the PS traffic zone:


in order to increase the PS capacity and limit the occurrence of holes in the SPDCHs_Allocation bitmap, each TCH/SPDCH capable TS carrying CS traffic and located inside the PS traffic zone, has its prereservation state set to pre-reserved for PS. No new incoming CS call can be served on this TS, if it becomes unused once it is prereserved for PS. This is valid until the TS becomes not pre-reserved for PS again and of course still handled by the BSC the modification of the value of the pre-reservation state can only occur when the SPDCHs_Allocation bitmap is built, every TCH_INFO_PERIOD * RR_ALLOC_PERIOD seconds

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection
Page 76

CS calls in the Non pre-emptable PS zone:


to speed up the release of a TS carrying a CS call inside both the non preemptable PS zone and the MAX_SPDCH_LIMIT zone, it is proposed to reallocate the concerned CS call in the CS zone using an intra-cell handover if EN_RETURN_CS_ZONE_HO = enabled, each time MAX_SPDCH_LIMIT is calculated, the BSC shall check whether TCHs are allocated in both the MAX_SPDCH_LIMIT zone and the non pre-emptable PS zone. In this case, it shall send a Start HO (cause 30) message to the HO Preparation entity, to trigger an intracell handover, to move these TCHs into the CS zone if for any reason, the handover fails, the TCH will remain in the PS zone, until the next calculation of MAX_SPDCH_LIMIT, where a new HO could be triggered, if still needed the TS will be considered as unused only once the handover will have been successfully performed. As the pre-reservation state of such a TS is set to pre-reserved for PS, no new incoming CS call can be allocated on it

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection
Page 77

CS calls in the Non pre-emptable PS zone:


PS traffic zone MAX_SPDCH_LIMIT zone Non pre-emptable PS zone PS 1 PS 2 CS 3 PS 4 5 TRX2 PS 6 CS 7 8 PS 9 PS 10 CS 11 CS 12 13 TRX1 14 15 CS 16

MAX_SPDCH_HIGH_LOAD zone

PS traffic zone Non pre-emptable PS zone MAX_SPDCH_LIMIT zone PS 1 PS 2 3 CS CS PS 6 CS 7 8 CS 9 CS 10 CS 11 CS 12 13 TRX1 14 15 CS 16

4 5 TRX2

MAX_SPDCH_HIGH_LOAD zone PS used by PS CS used by CS CS used by CS, candidate for HO cause 30

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

CS PREEMPTION
Page 78

Principles:
the CS pre-emption process is triggered when a radio TS is reported by the BSC as no longer allocated to the MFS. The PDCH preemption for CS traffic only applies to SPDCHs

each time the MFS receives a RR Allocation Indication message from the BSC, it uses the SPDCHs_Allocation bitmap to determine which SPDCHs shall be given back to the BSC then, the MFS shall immediately send a RR Usage Indication message to the BSC with the SPDCHs_Confirmation bitmap, so that the impacted SPDCHs that are not used are immediately given back to the BSC (no TBF resources are allocated on these SPDCHs and their basic Abis nibbles are free)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

CS PREEMPTION
Page 79

Principles:
after sending the RR Usage Indication, the TCH_INFO_PERIOD timer is restarted. The remaining impacted SPDCHs, that is those still in use (at least one TBF is established on those SPDCHs or the basic Abis nibbles of those SPDCHs are used by a GCH channel), are marked by the CS pre-emption process: these SPDCHs enter the MFS de-allocating PDCH state the CS pre-emption process shall be completed before the TCH_INFO_PERIOD expiry, in order to confirm the deallocation of all the remaining pre-empted SPDCHs in the next RR Usage Indication message to be sent to the BSC. For that purpose, the internal T_PDCH_Preemption timer is set to TCH_INFO_PERIOD - 1s When T_PDCH_Preemption expires, the fast preemption is launched.
TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Related Parameters
Page 80

HMI name

Definition

Subsystem
BSC

Insta nce
BSC

OMC-R access
None (DLS)

Type

Def value
2

Range

Unit

NEW : RR_ALLOC_PERIOD

This parameter allows to tune the time between two sendings of the BSCGP RR Allocation Indication message

Numb er

[1,30]

None

NEW : THR_MARGIN_PRIO_P S
NEW : EN_RETURN_CS_ZON E_HO

Margin of radio timeslots reserved for PS traffic between two sendings of the BSCGP RR Allocation Indication message. The threshold is expressed in percentage of radio timeslots
Flag enabling the intracell handovers allowing to move TCH from the PS zone to the CS zone of PDCH/TCH allocation

BSC

BSC

None (DLS)

Perce ntage

10

[0,100]

BSC

cell

Changea ble

flag

[0,1]

None

Removed parameters :
T_PDCH_PREEMPTION

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Agenda
Page 81

B9 features and related parameters:


Enhanced support of E-GPRS in UL (8-PSK in UL and IR in UL) Extended UL TBF mode Enhanced Packet cell reselection Enhanced Transmission resource management

Channel allocation strategy in B9 for PS transfers :


Modification of the PDCH allocation strategy Modification of the TBF allocation/re-allocation strategy

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

PDCH state
Page 82

Following states are defined for a PDCH :


Allocated:
new definition in B9: the PDCH is a SPDCH which has been indicated as usable for PS traffic by the BSC B8 definition: radio resource allocated to the MFS, but associated transmission resources are not allocated

Active:
new definition in B9: an allocated PDCH is active if it supports at least one radio resource allocated for a TBF the B8 definition was considering the parameter N_TBF_PER_SPDCH which is removed in B9 release

Full : as in B8 release

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

PDCH state
Page 83

Following states are defined for a PDCH:


EGPRS:
an allocated PDCH is in the EGPRS state if some radio resources are allocated in the DL direction, for an EGPRS TBF. This state is only used when running the radio resource allocation/reallocation algorithm in GPRS mode and when considering the UL direction of the candidate TBF allocations

Remark:
the busy PDCH state (number of established TBF on the PDCH higher than N_TBF_PER_SPDCH) is no more used by the allocation algorithm

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

TRX List computing


Page 84

The goal of the TRX list computing step is to determine the TRX list on which the TBF or one UL block candidate allocations will be searched The conditions for a TRX to be inserted into the TRX list are:
the TRX shall be PS capable if the TRX is not already mapped to a DSP, and no DSP can be associated to the TRX, then the TRX shall not be considered

Difference with B8 release:


there are no longer some restricted EGPRS capable TRX lists (i.e. selection of the EGPRS TRX of highest class (that is which offer the highest throughput) as long as the maximum number of EGPRS TBF per PDCH on these TRX is not higher than a threshold). Indeed, all the EGPRS capable TRXs can offer the same potential throughput: they are all mapped on G4 TRE, and the B8 concept of TRX pool type has disappeared

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 85

Once all the usable PDCHs are determined, the different candidate timeslot allocations are sorted according to their respective available throughput, in order to choose the one offering the highest throughput to serve the considered request. This is a complete change compared to the previous BSS releases (B6, B7 and B8)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 86

Candidate timeslot allocation:


a candidate timeslot allocation is a double list of contiguous PDCH in a TRX (one list for the direction of the request, one list for the opposite direction), which verifies the concurrent constraints as defined by the MS multislot class

to be included in a candidate timeslot allocation in order to serve a best effort TBF, a PDCH on a given TRX must verify the following conditions:
the PDCH shall be allocated in the MFS. This condition is new in B9 release and comes from the fact that the MFS does not request PDCH to the BSC the PDCH shall not be in the Full state in the considered direction the PDCH shall not be locked due to a CS pre-emption process

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 87

Available throughput of a candidate timeslot allocation:


this is a completely new metric introduced in B9 release. In the past releases the idea was already to give the highest possible throughput to a TBF (allocating the highest number of TS, if possible not busy) but there was no explicit metric evaluating the throughput provided by a candidate TS allocation
the available throughput of a given candidate timeslot allocation (available_throughput_candidate_XL) is the overall throughput provided by its PDCHs. It depends both on the potential throughput of its PDCHs (potential_throughput_PDCH) and on the available capacity on each of its PDCHs (available_capacity_PDCH_XL)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 88

Available throughput of a candidate timeslot allocation:


Potential throughput of a given PDCH:
the potential throughput of a PDCH is calculated as follows according to O&M parameters for the Evolium BTS case:
GPRS best effort TBF: R_AVERAGE_GPRS EGPRS best effort TBF: R_AVERAGE_EGPRS

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 89

Available throughput of a candidate timeslot allocation:


Available capacity on a given PDCH:
The available capacity on a given PDCH (available_capacity_PDCH_XL) is calculated as follows for a GPRS TBF (XL corresponds to either UL or DL) :
1 / Nb_BE_TBF_SAME_PRIOR_XL Where : Nb_BE_TBF_SAME_PRIOR_XL indicates the total number of Best Effort TBFs (GPRS or EGPRS) which have some radio resources allocated on the considered PDCH in the XL direction, and whose priority (combination of THP (Traffic Handling Priority; QoS parameter used for the interactive traffic class) and of Precedence) is strictly equal to the priority of the TBF to establish / reallocate.

The available capacity on a given PDCH (available_capacity_PDCH_XL) is calculated as follows for an EGPRS TBF (XL corresponds to either UL or DL) :
1 / Nb_BE_EGPRS_ TBF_SAME_PRIOR_XL Where : Nb_BE_EGPRS_ TBF_SAME_PRIOR_XL only take into account EGPRS TBF (the best effort GPRS TBF are not taken into account)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 90

Available throughput of a candidate timeslot allocation:


Available capacity of a given candidate timeslot allocation:
for a given candidate timeslot allocation with n PDCHs (n 1), the available capacity is computed as follows, for each direction (XL corresponds to either UL or DL):
available_capacity_candidate_XL = i = 1 to n available_capacity_PDCHi_XL

Available throughput of a given candidate timeslot allocation:


finally, the available throughput of a candidate timeslot allocation is computed as follows, for each direction (XL corresponds to either UL or DL):
available_throughput_candidate_XL = potential_throughput_PDCH * available_capacity_candidate_XL

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 91

Candidate time slot allocations sorting:


the algorithm used in B9 release is completely modified compared to the one used in B8 release as the key criterion is now the provided throughput instead of the number of TS only the candidate timeslot allocations for which some PDCH capacity, TFI, TAI and USF resources can be allocated in the direction(s) in which the TBF has to be established, are valid. If such candidate timeslot allocation is not found, the best effort TBF allocation / reallocation request has failed and the process is aborted else, all the valid candidate timeslot allocations are sorted according to the following list of ordered criteria (from the highest priority to the lowest). This list of criteria is valid in all cases: for GPRS or EGPRS service (contrary to the B8 release case where two lists were used), and in a cell belonging to an Evolium BTS or to a DRFU BTS

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 92

Candidate time slot allocations sorting:


ALPHA: if the policy is ASAP, then the candidate TS allocations which are on some TRXs for which Current_Nb_GCH - Min_Nb_GCH_GBR Nb_MPDCH Nb_GCH_For_TBF_Estab are preferred A: the candidate TS allocations which have the lowest number of PDCHs in the EGPRS state are preferred B: the candidate TS allocations, which have the highest available throughput in the direction of the bias (available_throughput_candidate_XL) are preferred C: the candidate TS allocations, which have the highest available throughput in the direction opposite to the bias (available_throughput_candidate_XL) are preferred D: the candidate TS allocations, which are on the TRX with the highest priority, are preferred E: for EGPRS best effort TBF establishments only: the candidate TS allocations, which have the lowest number of GPRS TBFs in the direction of the bias, are preferred F: combination with the PDCHs that have the lowest index are preferred

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Best candidate allocation computation


Page 93

Candidate time slot allocations sorting:


Remarks:
the A criterion is only relevant for an UL GPRS TBF establishment / reallocation (i.e. when considering the UL direction of a candidate TS allocation in GPRS mode) when evaluating criterion F, the concurrent constraints imposed by the MS multislot class (if it is known) or by the default multislot class (if the MS multislot class is not known) shall be taken into account

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

PDCH capacity allocation


Page 94

Once a candidate TS allocation has been found (in the best candidate allocation computation step), the following radio resources are allocated to the MS in the directions in which a TBF has to be established:
PDCH capacity TFI PDTCH / PACCH TAI USF (only in the UL direction)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

PDCH capacity allocation


Page 95

PDCH capacity allocation:


this step is new in B9 release the PDCH capacity allocation is performed on the best candidate TS allocation so as to guarantee a minimum bandwidth for the corresponding TBF(s) (data throughput and throughput generated on PACCH channels in DL and in UL) the PDCH capacity allocation shall only be performed in Evolium BTSs (no PDCH capacity needs to be allocated in DRFU BTSs) the PDCH capacity allocation should always succeed, because the candidate TS allocations for which the PDCH capacity allocation cannot be performed have been excluded during the best candidate allocation computation step

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

PDCH capacity allocation


Page 96

PDCH capacity allocation:


PDCH capacity needed for a TBF:
in a given direction (UL or DL) and on a given PDCH, the minimum capacity (in terms of radio block scheduling in MAC layer) that is required for a best effort TBF is called needed_capacity_Best_Effort_XL (XL corresponds to either UL or DL) this capacity corresponds to a minimum bandwidth that shall be guaranteed for the best effort TBF it is computed as follows:
needed_capacity_Best_Effort_XL = 20 / T_MAX_FOR_TBF_SCHEDULING with T_MAX_FOR_TBF_SCHEDULING an O&M parameter in ms

this calculation of needed_capacity_Best_Effort_XL approximates the minimum load which can be generated by the data traffic and the signalling traffic of the TBF (signalling traffic on the PACCH in the direction of the TBF). To simplify, it is considered that needed_capacity_Best_Effort_DL = needed_capacity_Best_Effort_UL

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

PDCH capacity allocation


Page 97

PDCH capacity allocation:


algorithm to allocate the PDCH capacity needed for a TBF:
in a given direction (XL corresponds to either UL or DL) and on a given PDCH, the maximum PDCH capacity which can be allocated is equal to:
1 - USED_CAPACITY_BEST_EFFORT_XL Where : USED_CAPACITY_BEST_EFFORT_XL indicates the total PDCH capacity that has already been allocated to best effort TBFs (both GPRS and EGPRS) on the PDCH in the XL direction in order to ensure a minimum bandwidth for those best effort TBFs

in the direction(s) in which a TBF has to be established, a PDCH capacity equal to needed_capacity_Best_Effort_XL shall be allocated on each PDCH included in the best candidate TS allocation

then on each of these PDCH, the value of USED_CAPACITY_BEST_EFFORT_XL shall be increased accordingly (incrementation by needed_capacity_Best_Effort_XL)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

T3 & T4 TBF reallocation cases


Page 98

T3 TBF reallocation:
goals of the T3 reallocation (Evolium BTS):
provide a higher throughput, if it is possible, to any TBF in the cell establish a new M-EGCH link for one of the TRXs of the cell. This is possible because the T3 TBF reallocation requests are played with the Optimal allocation policy. perform a radio defragmentation process to limit the risk that the TBFs are impacted by a CS pre-emption. The goal is that the PDCHs supporting the TBFs in the cell are always the first or left-most allocated PDCHs of the cell (when considering the ordered TRXs list provided by the BSC and the RTSs from RTS 0 to RTS 7 on a given TRX)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

T3 & T4 TBF reallocation cases


Page 99

T3 TBF reallocation:
conditions for a MS to be candidate for T3 reallocation:
the BSS systematically requests a T3 reallocation for any MS which has an established TBF in the direction of the bias verifying the following conditions:
more than N_CANDIDATE_FOR_REALLOC bytes have been sent on the DL TBF or received on the UL TBF since their establishment T3192 is not running

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

T3 & T4 TBF reallocation cases


Page 100

T3 TBF reallocation:
THROUGHPUT_RATIO:
for each MS which is candidate for a T3 TBF reallocation, a throughput ratio is calculated this throughput ratio is useful to:
validate the candidate TBF allocations when playing the radio resource reallocation algorithm sort the T3 TBF reallocation requests within some lists: low value of the throughput ratio means high priority of the request

THROUGHPUT_RATIO = ALLOCATED_THROUGHPUT / OPTIMAL_THROUGHPUT


ALLOCATED_THROUGHPUT is the throughput currently allocated to the TBF in the direction of the bias and is equal to potential_throughput_PDCH * available_capacity_candidate_XL OPTIMAL_THROUGHPUT is the optimal throughput that could be potentially allocated to the TBF in the direction of the bias by considering its multislot class and is equal to potential_throughput_PDCH * n_MS_requested

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

T3 & T4 TBF reallocation cases


Page 101

T3 TBF reallocation:
best candidate allocation computation:
a candidate TBF allocation shall fulfil the following condition:
NEW_THROUGHPUT_RATIO min(1, (1+MIN_THROUGHPUT_GAIN ) * CURRENT_THROUGHPUT_RATIO) NEW_THROUGHPUT_RATIO is the throughput ratio of the candidate TBF allocation CURRENT_THROUGHPUT_RATIO is the throughput ratio of the current TBF allocation MIN_THROUGHPUT_GAIN is an O&M parameter

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

T3 & T4 TBF reallocation cases


Page 102

T3 TBF reallocation:
reallocation attempts:
T3 reallocation attempts occur at each expiry of the T_CANDIDATE_TBF_REALLOC timer up to N_MAX_PERIODIC_REALLOC_T3 T3 reallocation attempts can take place at each T_CANDIDATE_TBF_REALLOC timer expiry in case of successful T3 reallocation attempt, no new attempt takes place until the next T_CANDIDATE_TBF_REALLOC timer expiry even if less than N_MAX_PERIODIC_REALLOC_T3 attempts have occurred up to two T3 TBF reallocations can be successfully played at each T_CANDIDATE_TBF_REALLOC timer expiry

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

T3 & T4 TBF reallocation cases


Page 103

T4 TBF reallocation:
goal of the T4 reallocation:
avoid the UL GPRS - DL EGPRS TBF multiplexing situations indeed, in those multiplexing situations, some dummy DL GPRS TBF(s) may have to be managed by MAC in order to schedule the USFs of the UL GPRS TBF(s), which can induce a throughput reduction for the DL EGPRS TBFs

triggering conditions:
a GPRS MS becomes candidate for a T4 reallocation as soon as its UL GPRS TBF shares at least one PDCH with a DL EGPRS TBF the MS remains candidate for a T4 reallocation, after an UL TBF release, if a DL TBF is still ongoing. This means that a DL TBF can be T4 reallocated even if it has currently no UL concurrent TBF

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

T3 & T4 TBF reallocation cases


Page 104

T4 TBF reallocation:
best candidate allocation computation:
the candidate timeslot allocations do not require to have the same number of PDCHs than the current allocation in the UL direction, the candidate timeslot allocations cannot contain PDCHs in the EGPRS state. the radio resource allocation algorithm is run with the ASAP policy. Thanks to the allocation criterion ALPHA, the candidate TS allocations located on the TRXs having already Nb_GCH_For_TBF_Estab established GCHs are favored

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

T3 & T4 TBF reallocation cases


Page 105

T4 TBF reallocation:
reallocation attempts:
upon T_CANDIDATE_TBF_REALLOC timer expiry it shall be attempted to reallocate a maximum of N_MAX_PERIODIC_REALLOC_T4 candidate MSs queued within a list if a reallocation succeeds, the next request within the list shall be played (up to the N_MAX_PERIODIC_REALLOC_T4 limit)

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Related Parameters
Page 106
HMI name Definition Subsystem
MFS MFS

Insta nce
cell cell

OMC-R access
Changea ble Changea ble

Type

Def value
12000 30000

Range

Unit

NEW : R_AVERAGE_GPRS NEW : R_AVERAGE_EGPRS

average bitrate per PDCH for non-Edge capable terminals in this cell average bitrate per PDCH for Edge capable terminals in this cell

Throu ghput Throu ghput

[0,2000 0] [0,5900 0]

Bit/s Bit/s

NEW : T_MAX_FOR_TBF_SC HEDULING

maximum time between two scheduling of a given NRT TBF (either between two DL block requests for a NRT DL TBF, or between two UL blocks received for a given NRT UL TBF)
minimum throughput gain required to be provided to the MS when performing a T2 or T3 TBF reallocation total number of (unsuccessful) T3 radio resource reallocation attempts that are allowed to be performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer. As soon as a T3 radio resource reallocation attempt succeeds, no other attempt is performed (even if less than N_MAX_PERIODIC_REALLOC_T3 attempts have been performed so far). The UL-biased MSs and the DL-biased MSs are considered regardless of each other. As a result, in a given cell, up to 2 x N_MAX_PERIODIC_REALLOC_T3 T3 radio resource reallocation attempts will be performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer defines the total number of T4 radio resource reallocation attempts (successful or not) that are performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer

MFS

MFS

None (DLS)

Time

0.3

[0.12,0. 3]

NEW : MIN_THROUGHPUT_G AIN NEW : N_MAX_PERIODIC_RE ALLOC_T3

MFS

MFS

None (DLS) None (DLS)

Numb er Numb er

0.4

[0.1,5]

None

MFS

MFS

20

[0,500]

None

NEW : N_MAX_PERIODIC_RE ALLOC_T4

MFS

MFS

None (DLS)

Numb er

[0,500]

None

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Modification of the TBF allocation/re-allocation strategy

Related Parameters
Page 107

Following B8 parameters are removed in B9 release:


N_TBF_PER_SPDCH EN_RES_REALLOCATION N_MAX_PERIODIC_REALLOC

TMD_B9_pres_PS_part / Oct 05

All rights reserved 2005, Alcatel

Page 108

www.alcatel.com
TMD_B9_pres_PS_part / Oct 05
All rights reserved 2005, Alcatel

You might also like