eda_bss trial_nsn_eda_01.pdf

8/11/2019 EDA_BSS Trial_NSN_EDA_01.pdf

http://slidepdf.com/reader/full/edabss-trialnsneda01pdf 1/10

Uninor Feb 05, 2014 1 of 10

UNINOR

BSS Feature Trial

NOTICE TO READERS

ALL MATERIALS INCLUDED HEREIN ARE COPYRIGHTED AND CONFIDENTIAL UNLESS OTHERWISEINDICATED. The information contained herein is intended only for the person or entity to which it is addressed andmay contain confidential and/or privileged material. Any review, retransmission, dissemination, or other use or relianceupon this information by persons or entities other than the intended recipient is prohibited. The information providedherein is subject to protection from disclosure, reproduction and use.

This document is subject to change without notice. Please verify that you are in possession of the mostrecent version of this document.

05 February 2014




Document Summary

Testing Type : Feature (Feature Or Parameter)Feature / Parameter Name : SRADocument Version : NSN_SRA_01Last Revision Date : February 6, 2014Prepared By : Piyush PantDocument Approver : Parimal Johary



BSS Feature Trial


Table of Contents

1 Introduction .................................................................................................................................... 4 1.1 Background ............................................................................................................................................. 4

1.2 Technical Description .............................................................................................................................. 4

1.2.1 Channel allocation ............................................................................................................................ 4

1.2.2 EDA scheduling ................................................................................................................................ 5

1.3 Maximum configurations ......................................................................................................................... 5

1.4 Objective ................................................................................................................................................. 7

2 Hardware / Software Dependencies .............................................................................................. 8

2.1 Hardware ................................................................................................................................................. 8

2.1.1 BSC Side .......................................................................................................................................... 8

2.2 Software .................................................................................................................................................. 8

2.2.1 Software version ............................................................................................................................... 8

2.3 End-user equipment ................................................................................................................................ 8

3 Trial Preparation ............................................................................................................................. 9

3.1 Site Preparation ...................................................................................................................................... 9

3.1.1 Trial Plan .......................................................................................................................................... 9

3.2 Service Impact ........................................................................................................................................ 9

3.3 Planned Date of Implementation............................................................................................................. 9

4 Expected Benefits ........................................................................................................................ 10



BSS Feature Trial


1 Introduction

1.1 BackgroundThe packet switched (PS) data volumes are increasing in the GSM networks due to from Smart Phone applications.Higher multi-slot class Smartphones are available in our subscriber base that can use more UL timeslots for betteruplink speed. Extended Dynamic Allocation (EDA) is an extension to the Dynamic Allocation (DA) medium accessmethod. It enables a mobile to use more uplink (UL) timeslots, and thus reach higher UL throughput by removing theneed for the mobile to detect uplink state flags (USFs) separately for each allocated UL timeslot.

The feature is controlled by a BSC level ON/OFF license key.

1.2 Technical Description

In general, PCU attempts to allocate as many timeslots for a TBF as allowed by the multislot class of the mobile, thenetwork resources and, in case of a UL TBF, the MS Multislot Power Reduction restrictions. However, the introduction

of EDA brings some modifications to this rule: more than two timeslots are allocated only if it is estimated that an EDAallocation would provide better throughput than a DA allocation. By allocating only the 'necessary' amount of timeslotsfor a UL TBF, the transmission power reduction possibly applied by the mobile is kept to a minimum, and thescheduling of TBFs is kept. Extended Dynamic Allocation exemplifies EDA by presenting a UL TBF consisting of 4timeslots (1, 2, 3, 4). The mobile receives USF in timeslot 1 and can therefore transmit on slots 1, 2, 3 and 4 during thenext block period.

1.2.1 Channel allocationIn case of a resource allocation for an EDA-capable mobile, PCU may limit the number of timeslots to be allocated fora UL TBF on the basis of a DA/EDA throughput estimate comparison. If PCU estimates that a DA (max. two timeslots)connection would provide better throughput than an EDA connection, it allocates no more than two timeslots for theTBF. The possibility that a DA connection would provide better throughput than an EDA connection is due to the EDAscheduling restrictions described in EDA scheduling. Heavy traffic load on EDA connection timeslots may limit thenumber of block periods during which the connection can be scheduled. PCU carries out the throughput estimatecomparison by first finding the best DA connection in the (E)GPRS territory according to the normal channel allocationprocedures. Then, by using the existing loads on the selected and the adjacent slots as input and by consulting alookup table based on simulation results, PCU estimates whether an EDA-connection would be likely to provide betterthroughput than the selected DA connection. The same estimation is used during reallocations.

1.2.1.1 UL/DL timeslot division

When concurrent TBFs are created for an MS, the initial timeslot division between UL and DL is in principle done byobserving the parameters CONC_UL_TBF_FAVOR_DIR and CONC_DL_TBF_FAVOR_DIR . With EDA, a greatervariety of UL configurations becomes available. This gives rise to a need to define a third value for these parameters.Therefore, the value 'shared' has been added to the existing values 'favour DL' and 'favour UL'. When allowed by themobile's multislot class, the 'shared' resource allocation produces concurrent TBFs between which the availabletimeslots are divided more evenly than in the case of either 'UL favoured' or 'DL favoured' resource allocation.However, no more than two UL timeslots are allocated for 'shared' TBFs. It must be remembered that while theparameters CONC_UL_TBF_FAVOR_DIR and CONC_DL_TBF_FAVOR_DIR define a target DL/UL configuration for aninitial concurrent TBF resource allocation, other restrictions and considerations on the number of UL timeslots may



BSS Feature Trial


affect the final configuration. Whenever fewer UL timeslots than allowed by the mobile's multislot class are allocated,'leftover' UL slots are moved to DL if this is allowed by the mobile's multislot class.

1.2.1.2 TBF reallocation

TBF reallocations for a mobile that does not have a TBF in the opposite direction are similar to initial radio resourceallocations. During TBF reallocations for a mobile with concurrent TBFs, the timeslots are divided between UL and DLaccording to the perceived traffic densities. The new 'shared' configuration option has been added to thesereallocations as well.

1.2.2 EDA scheduling

GPRS standards set certain restrictions to EDA scheduling:

The number of scheduled timeslots cannot be decreased between two consecutive block periods.

A scheduled set of timeslots always includes the highest-numbered slot at the end of the TBF radio resourceallocation.

The set of timeslots scheduled for a mobile during one block period is constituted by contiguous slots. Thecontiguousness of the scheduled slots cannot be interrupted even by timeslots scheduled through the polling

mechanism for the same mobile.Whenever it is not possible to schedule an EDA TBF observing these restrictions for the block period in question,either the TBF is left unscheduled or fewer timeslots - if this does not lead to another conflict with the restrictions - arescheduled. Otherwise, there are no differences between the scheduling of DA and EDA connections.USF4 granularity is not applied to EDA scheduling even when an EDA GPRS TBF is multiplexed with an EGPRS TBF.

1.3 Maximum configurations

Figures Maximum configurations for multislot classes 1 –12 and 19 –23 and Maximum configurations for multislotclasses 24 –45 present the maximum UL and DL configurations that are achieved with and without EDA support. Thefigures include the maximum configurations with the mobile's multislot class and the different values for the PRFILEparameters CHA_CONC_UL_TBF_FAVOR_DIR and CHA_CONC_DL_TBF_FAVOR_DIR.Note that the prevailing circumstances, such as PS territory size or UL power reduction restrictions, may lead toconfigurations other than those listed.

Type1MS DL TSLs UL TSLs Type1MS DL TSLs UL TSLs

Multislot Class 1 Multislot Class 4

Favour DL 1 1 Favour DL 3 1

Share resources 1 1 Share resources 3 1

Favour UL 1 1 Favour UL 3 1



Share resources 2 1 Share resources 2 2Favour UL 2 1 Favour UL 2 2




Favour UL (EDA) 1 2 Favour UL 2 2

Favour UL (DA) 2 1



BSS Feature Trial



Multislot Class 7 Multislot Classes 20-21



Favour UL 2 2 Favour UL (EDA) 2 3

Favour UL (DA) 3 2

Multislot Class 8

Favour DL 4 1 Multislot Classes 22-23

Share resources 4 1 Favour DL 4 1

Favour UL 4 1 Share resources 3 2

Favour UL (EDA) 1 4

Multislot Class 9 Favour UL (DA) 3 2

Favour DL 3 2

Share resources 3 2 Multislot Class 24

Favour UL 3 2 Favour DL 4 1

Share resources 3 2

Multislot Class 10 Favour UL 3 2

Favour DL 4 1

Share resources 3 2 Multislot Classes 25-26


Share resources 3 2

Multislot Class 11 Favour UL (EDA) 2 3

Favour DL 4 1 Favour UL (DA) 3 2

Share resources 3 2

Favour UL (EDA) 2 3 Multislot Classes 27-29

Favour UL (DA) 3 2 Favour DL 4 1

Share resources 3 2

Multislot Class 12 Favour UL (EDA) 1 4

Favour DL 4 1 Favour UL (DA) 3 2

Share resources 3 2

Favour UL (EDA) 1 4 Multislot Class 30

Favour UL (DA) 3 2 Favour DL 5 1

Share resources 5 1

Multislot Class 19 Favour UL 5 1

Favour DL 4 1

Share resources 3 2 Multislot Class 31


Share resources 4 2

Favour UL 4 2



BSS Feature Trial






Favour UL (EDA) 3 3 Favour UL 5 1

Favour UL (DA) 4 2

Multislot Class 41

Multislot Classes 33-34 Favour DL 5 1

Favour DL 5 1 Share resources 4 2

Share resources 4 2 Favour UL 4 2

Favour UL (EDA) 2 4

Favour UL (DA) 4 2 Multislot Class 42

Favour DL 5 1

Multislot Class 35 Share resources 4 2

Favour DL 4 1 Favour UL (EDA) 3 3

Share resources 4 1 Favour UL (DA) 4 2

Favour UL 4 1

Multislot Classes 43-45

Multislot Class 36 Favour DL 5 1

Favour DL 4 1 Share resources 4 2

Share resources 3 2 Favour UL (EDA) 2 4

Favour UL 3 2 Favour UL (DA) 4 2

Multislot Classes 37-39

Favour DL 4 1

Share resources 3 2

Favour UL (EDA) 2 3

Favour UL (DA) 3 2

1.4 Objective

Improve UL capacity by supporting multi-slot configurations that cannot be supported with Dynamic Allocation.

Make the network more Smart Phone friendly by supporting handset's multislot capability.



BSS Feature Trial


2 Hardware / Software Dependencies

2.1 Hardware

2.1.1 BSC Side

The “Extended Dynamic Allocation” feature requires the following hardware:

Network Element Required Hardware

PCU PCU2

2.2 Software

2.2.1 Software versionThe software release of the BSC must be S12 or higher.

2.3 End-user equipment

Extended Dynamic Allocation-capable mobile stations are required. Extended Dynamic

Allocation support is obligatory for multi-slot classes 22, 24, 25 and 27.



BSS Feature Trial


3 Trial Preparation

3.1 Site Preparation

Trial will be implemented in Ahmedabad-1 BSC. Pre and Post KPI will be analyzed so as to see any adverse effect.

3.1.1 Trial Plan

BSS20089 (Extended Dynamic Allocation) feature enable on BAH0101 by 6th Feb 2013

3.2 Service Impact

No service impact.

3.3 Planned Date of Implementation

Trial Plan to be implemented on 6th Feb 2014.



BSS Feature Trial


4 Expected Benefits

Extended Dynamic Allocation allows a mobile to use more than two timeslots in UL. In BSS12, the maximum number

of UL timeslots per UL TBF is four, which permits the following maximum UL bitrates: GPRS with CS-1/CS-2, up to 48 kbit/s

GPRS with CS-3/CS-4, up to 80 kbit/s

EDGE, up to 236 kbit/s

Capacity and quality EDA improves UL capacity by supporting multislot configurations that cannot be supported with Dynamic

Allocation.

With EDA, the maximum number of available UL timeslots and the achievable UL throughput are doubledin comparison with earlier BSS releases.

With EDA, the best possible UL resources are allocated, rather than the most possible UL timeslots. Inother words, lesser timeslots are allocated when it is estimated that more timeslots would not provide abetter service.

Support for new applications Higher UL bitrates are beneficial to applications such as sending email with attachments, fileuploading, MMS sending and mobile video telephony.

eda_bss trial_nsn_eda_01.pdf

Documents