Professional Documents
Culture Documents
Agenda
Page 2
TMD_B9_pres_PS_part / Oct 05
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).
TMD_B9_pres_PS_part / Oct 05
Content
Page 4
TMD_B9_pres_PS_part / Oct 05
TMD_B9_pres_PS_part / Oct 05
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
Content
Page 7
TMD_B9_pres_PS_part / Oct 05
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.
8PSK
MCS7 MCS8 MCS9
22
22
22
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
28
TMD_B9_pres_PS_part / Oct 05
Remark: The Incremental Redundancy for the uplink TBF feature is supported only on G4 BTSs.
TMD_B9_pres_PS_part / Oct 05
Related parameters
Page 11
HMI name
Definition
Subsyst em MFS
Instan ce BSS
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
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
Agenda
Page 12
TMD_B9_pres_PS_part / Oct 05
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
Functional description
Page 14
3.
4.
5.
6.
TMD_B9_pres_PS_part / Oct 05
Acquiring MS capability
Page 15
TMD_B9_pres_PS_part / Oct 05
Scheduling USF
Page 16
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
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
(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
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
ms
MFS
BSS
Changeable
Flag
None
MFS
BSS
Changeable
Flag
[0,1]
None
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
Agenda
Page 20
TMD_B9_pres_PS_part / Oct 05
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
Content
Page 22
NC2 improvement
TMD_B9_pres_PS_part / Oct 05
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 B
TMD_B9_pres_PS_part / Oct 05
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
(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
(4)
TMD_B9_pres_PS_part / Oct 05
(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
Content
Page 28
NC2 improvement
TMD_B9_pres_PS_part / Oct 05
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
Cell B
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
(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
Cell B
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
(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
Content
Page 34
NC2 improvement
TMD_B9_pres_PS_part / Oct 05
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
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
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
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
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.
TMD_B9_pres_PS_part / Oct 05
priority
priority
TMD_B9_pres_PS_part / Oct 05
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
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
MFS
cell
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
Timer
[1,100]
sec
MFS
MFS
[3,30]
None
MFS
cell
[0,100]
None
MFS
MFS
10
[1,255]
sec
TMD_B9_pres_PS_part / Oct 05
Agenda
Page 41
TMD_B9_pres_PS_part / Oct 05
M-EGCH Statistical Multiplexing Dynamic Abis Allocation Ater Resource Management DL Retransmission in the BTS
TMD_B9_pres_PS_part / Oct 05
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
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 36 GCHs
GCH
GCH
LEGEND
320 bits
320 bits
320 bits
MEGCH header (/NHP and addr byte) Dummy Filling PDU CRC + Tail bits Padding bits
DBN=x+1
DBN=x+2
Dummy Filling
20 ms
20 ms
20 ms
TMD_B9_pres_PS_part / Oct 05
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
GCH 1
RB2 RB3
RB2
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
In B8:
The size of an EGCH link (associated to a PDCH) can be dynamically decreased.
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
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
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.
composed of
GCH Basic
GCH Extra
GCH Extra
GCH Extra
GCH Extra
Legend: B: BCCH, S: static SDCCH, M: MPDCH, P: PDCH, T: TCH, X : Abis nibble wasted in B8, in B8
TMD_B9_pres_PS_part / Oct 05
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
The bonus basic Abis nibbles currently used for BCCH or static SDCCH channels:
The list of bonus Abis nibbles depends on the cell configuration.
The list of extra Abis TSs of a BTS is provided by the BSC to the MFS.
TMD_B9_pres_PS_part / Oct 05
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
TMD_B9_pres_PS_part / Oct 05
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
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
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
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
TMD_B9_pres_PS_part / Oct 05
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.
TMD_B9_pres_PS_part / Oct 05
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:
TMD_B9_pres_PS_part / Oct 05
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
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
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
MFS
cell
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
Agenda
Page 63
TMD_B9_pres_PS_part / Oct 05
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
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
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
TMD_B9_pres_PS_part / Oct 05
TMD_B9_pres_PS_part / Oct 05
TMD_B9_pres_PS_part / Oct 05
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
MAX_SPDCH_LIMIT TS selection
Page 70
TMD_B9_pres_PS_part / Oct 05
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
TMD_B9_pres_PS_part / Oct 05
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
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
4 5 TRX2
MAX_SPDCH_HIGH_LOAD zone
TMD_B9_pres_PS_part / Oct 05
MAX_SPDCH_LIMIT TS selection
Page 74
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
MAX_SPDCH_LIMIT TS selection
Page 75
TMD_B9_pres_PS_part / Oct 05
MAX_SPDCH_LIMIT TS selection
Page 76
TMD_B9_pres_PS_part / Oct 05
MAX_SPDCH_LIMIT TS selection
Page 77
MAX_SPDCH_HIGH_LOAD zone
4 5 TRX2
TMD_B9_pres_PS_part / Oct 05
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
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
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
Agenda
Page 81
TMD_B9_pres_PS_part / Oct 05
PDCH state
Page 82
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
PDCH state
Page 83
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
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
TMD_B9_pres_PS_part / Oct 05
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
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
TMD_B9_pres_PS_part / Oct 05
TMD_B9_pres_PS_part / Oct 05
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
TMD_B9_pres_PS_part / Oct 05
TMD_B9_pres_PS_part / Oct 05
TMD_B9_pres_PS_part / Oct 05
TMD_B9_pres_PS_part / Oct 05
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
TMD_B9_pres_PS_part / Oct 05
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
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
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
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
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
TMD_B9_pres_PS_part / Oct 05
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
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
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
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
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
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
average bitrate per PDCH for non-Edge capable terminals in this cell average bitrate per PDCH for Edge capable terminals in this cell
[0,2000 0] [0,5900 0]
Bit/s Bit/s
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]
MFS
MFS
Numb er Numb er
0.4
[0.1,5]
None
MFS
MFS
20
[0,500]
None
MFS
MFS
None (DLS)
Numb er
[0,500]
None
TMD_B9_pres_PS_part / Oct 05
Related Parameters
Page 107
TMD_B9_pres_PS_part / Oct 05
Page 108
www.alcatel.com
TMD_B9_pres_PS_part / Oct 05
All rights reserved 2005, Alcatel