<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>(E)GPRS TBF allocation</title>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta content="text/css" http-equiv="Content-Style-Type" />
<script src="NED?action=retrieve&amp;identifier=dn00188761&amp;edition=1&amp;language=none&amp;coverage=global&amp;encoding=javascript&amp;component=data&amp;item=data" type="text/javascript" xml:space="preserve">
</script>
<?conversion name="Pub2XHTML" version="2.0" source="urn:mars:dn02256921:5:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-21T13:12:31Z"?>
<link href="NED?action=retrieve&amp;identifier=dn01158124&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=css&amp;component=data&amp;item=data" rel="stylesheet" title="Nokia Networks default online style" type="text/css" />
<meta content="draft" name="status" />
<?conversion name="SplitHTML" version="1.9" source="urn:mars:dn02256921:5:en:global:publishing_online_1_0:data:data:42:*:*" date="2005-02-21T13:12:31Z"?>
</head>
<body lang="en" xml:lang="en">
<p><a name="dec1041517352" shape="rect"></a>
<a name="ned_9" shape="rect"></a></p>

<div class="div">
<table width="100%">
<tr>
<td align="center" colspan="1" rowspan="1" width="20%"><?NED5 annotation?>
<br clear="none" /><?NED5 printview?>
</td>
<td align="center" colspan="1" rowspan="1" width="20%"></td>
<td align="center" colspan="1" rowspan="1" width="20%"></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn02256921&amp;edition=5&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_1#ned_1" onclick="sync(this);return true" shape="rect">EGPRS capacity planning</a></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn02256921_about&amp;edition=5&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_top#ned_top" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=dn02256921_about&amp;edition=5&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_top#ned_top');return false" shape="rect" target="_blank"><img alt="Document information" border="0" class="Metainfo" src="NED?action=retrieve&amp;identifier=dn01158003&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=gif&amp;component=data&amp;item=data" /></a></td>
</tr>
</table>


<div class="div">
<h2>(E)GPRS TBF allocation</h2>

<p>Temporary Block Flow (<a href="NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id011257#id011257" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id011257#id011257');return false" shape="rect" target="_blank">TBF</a>) allocation
can be divided into:</p>


<ol class="type-odd">
<li type="1"><p>BTS selection</p>
</li>
<li type="1"><p>channel allocation in the selected BTS.</p>
</li>
</ol>


<a name="mar131357372" shape="rect"></a>
<div class="topic">
<h3>Criterias
and priorities for selecting a BTS</h3>

<p>The channel allocation process is described below. The
process includes all the following steps, in the order presented, in every
allocation and reallocation instance. After every step, the list of valid
BTSs is relayed to the next step and the BTSs that did not meet the requirements
are discarded.</p>
</div>


<a name="mar131358353" shape="rect"></a>
<div class="topic">
<h3>BTS
selection in a segment without PBCCH/PCCCH</h3>

<ol class="type-odd">
<li type="1"><p>Mobile RAC (bands)</p>


<p>With <a href="NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id08877#id08877" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id08877#id08877');return false" shape="rect" target="_blank">RF hopping</a> there has to be a packet
territory in <a href="NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id04445#id04445" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id04445#id04445');return false" shape="rect" target="_blank">BCCH</a> BTS or in a non-hopping BTS on
BCCH band.</p>
</li>
<li type="1"><p>Check maximum TBF/<a href="NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id05#id05" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id05#id05');return false" shape="rect" target="_blank">TSL</a> </p>
</li>
<li type="1"><p>Signal Level</p>


<ul>
<li><p>In case of initial allocation (DL signal
level not known), DIRE is used for ruling out some BTSs. BTS with NBL value
greater than DIRE is ruled out. </p>
</li>
<li><p>Reallocation based on signal level
is triggered by ( RX_level(BCCH)-NBL&lt;GPL )</p>
</li>
<li><p>In reallocation between different valid
BTSs, NBL is used for comparing levels and ruling out BTSs. ( RX_level(BCCH)-NBL&gt;GPU
)</p>
</li>
<li><p>In reallocation case, if no BTS fulfilling
 ( RX_level(BCCH)-NBL&gt;GPU ) is found, the old BTS is selected.  </p>
</li>
</ul>
</li>
<li type="1"><p>Mobile capability (<a href="NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id08914#id08914" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id08914#id08914');return false" shape="rect" target="_blank">GPRS</a>/<a href="NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id010416#id010416" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id010416#id010416');return false" shape="rect" target="_blank">EGPRS</a>) </p>
</li>
<li type="1"><p>Load (Penalty,QoS)</p>
</li>
</ol>
</div>


<a name="mar13144354" shape="rect"></a>
<div class="topic">
<h3>BTS
selection in a segment with PBCCH/PCCH</h3>

<ol class="type-odd">
<li type="1"><p>Mobile RAC (bands)</p>
</li>
<li type="1"><p>Check maximum TBF/TSL in BTS</p>
</li>
<li type="1"><p>Signal Level</p>


<ul>
<li><p>In case of initial allocation (DL signal
level not known), DIRE is used for ruling out some BTSs. BTS with NBL value
greater than DIRE is ruled out.</p>
</li>
<li><p>Reallocation based on signal level
is triggered by:( RX_level(BCCH)-NBL&lt;GPL )</p>
</li>
<li><p>In reallocation between different valid
BTSs, NBL is used for comparing levels and ruling out BTSs. ( RX_level(BCCH)-NBL&gt;GPU
)</p>
</li>
<li><p>In reallocation case, if no BTS fulfilling
 ( RX_level(BCCH)-NBL&gt;GPU ) is found, the old BTS is selected. </p>
</li>
</ul>
</li>
<li type="1"><p>Mobile capability (GPRS/EGPRS)</p>
</li>
<li type="1"><p>Load (Penalty,QoS)</p>
</li>
</ol>


<p>In UL reallocation, the signal level of the serving BTS
is compared to check if reallocation was triggered by a bad signal level.
If the reallocation was due to signal level, then the old serving BTS is discarded
in the very beginning.</p>
</div>


<a name="mar131410365" shape="rect"></a>
<div class="topic">
<h3>TBF
allocation in a BTS</h3>

<p>After the BTS has been selected, QoS and TBF type are compared
simultaneously. Different <a href="NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id08604#id08604" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id08604#id08604');return false" shape="rect" target="_blank">QoS</a> classes result in different penalties
for load comparing. </p>
</div>


<a name="dec841330341" shape="rect"></a>
<div class="topic">
<h3>(E)GPRS TBF multiplexing</h3>

<p>GPRS and EGPRS TBFs can be dynamically allocated on the
same timeslot. This process is called multiplexing.</p>


<p>If there are both GPRS and EGPRS TBFs allocated in the
same BTS, the <a href="NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id014238#id014238" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=general_glossary&amp;edition=13&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=id014238#id014238');return false" shape="rect" target="_blank">PCU</a> tries to avoid allocating the GPRS
and EGPRS TBFs into the same timeslots because it would dramatically decrease
the throughput of EGPRS TBFs. Among multiplexed TSLs, QoS is the selecting
criteria. Multiplexed and non-multiplexed TSLs are also prioritised by a penalty
value. When the channel allocator is searching for the best possible channel
configuration for a TBF, a penalty is assigned to those channel combinations
that would increase multiplexing.</p>


<p>When a GPRS TBF is in a multiplexed TSL, the following
checks are constantly made:</p>


<ol class="type-odd">
<li type="1"><p>is the channel multiplexed</p>
</li>
<li type="1"><p>is it the only GPRS TBF in the TSL
thus causing multiplexing</p>
</li>
<li type="1"><p>are there any multiplexed channels
available where the GPRS TBF could be reallocated.</p>
</li>
</ol>


<p>If a GPRS territory contains less channels than what could
be allocated to a mobile according to its multislot class, the PCU requests
for additional channels in order to perform a territory upgrade. These additional
channels are requested only if all GPRS default channels are already in the
GPRS territory. The maximum number of GPRS channels is limited by CMAX.</p>


<p>To ensure the best quality and speed for end-users, dimensioning
of the GPRS territory may not rely solely on territory upgrades. The use of
additional channels is less efficient compared to default channels. The additional
channels are always requested from a circuit-switched (CS) territory and there
are always delays before the channel can be moved to the GPRS territory. For
example, there can be a CS call in the timeslot that is to be moved to the
GPRS territory, and an intracell handover is therefore needed before the territory
upgrade can be completed.</p>


<p>Additional channels are taken into CS use whenever more
channels are needed on the CS side. The need for additional GPRS channels
is always checked when an existing TBF is terminated. The PCU requests the
removal of additional channels if the average TBF/TSL is less than 0.5 (average
TBF/TSL&lt;0.5). The target in the downgrade is to achieve an average TBF/TSL
to be equal to 1.</p>


<p>When there is EGPRS downlink TBF and GPRS uplink TBF in
the TSL, the MCS is limited to 1-4 (GMSK) whenever there is USF signalling
to the GPRS TBF. There is also a CS-coded downlink block every 360ms for synchronisation
purposes for GPRS MSs.</p>


<p>The figure <em>Segments and territories</em>
illustrates some of the territory issues.</p>


<p>In Segment 1, GPRS TBFs can be allocated either to the
GPRS or the (E)GPRS territory. EGPRS TBFs prefer BTS-1’. The GPRS and (E)GPRS
territories are handled by different sets of parameters since they are located
in different BTS objects.</p>


<p>In Segment 2, the GPRS traffic is denied on BTS-2 by a
TRX level parameter. Therefore, all GPRS and EGPRS TBFs exist on BTS-2’ as
there is only one territory capable of carrying the GPRS and EGPRS traffic
within the segment.</p>


<a name="dec132172149" shape="rect"></a>
<div>
<img alt="urn:mars:dn02259915:1:en:global:cgm_fixed:data:data" border="0" src="NED?action=retrieve&amp;identifier=dn02259915&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=gif&amp;component=data&amp;item=data" /><p class="figure-caption">Figure: Segments and territories</p>
</div>
</div>


<a name="mar131413146" shape="rect"></a>
<div class="topic">
<h3>Allocation
and Quality of Service (QoS)</h3>

<p>Scheduling algorithm prioritises the Temporary Block Flows
(TBF) residing on the <em>same</em> time slot so that the
TBF with the highest priority gets most air time. However, equal air time
does not provide equal data rates for the TBFs in the same time slot: it only
guarantees that the air time is divided equally within a QoS priority group
and that higher QoS class mobiles get more air time than lower ones inside
one radio time slot. The allocation process tries to ensure that better priority
TBFs do not gather into the same radio timeslot. Because priority based scheduling
works only within the same time slot, it is possible that the lower priority
mobiles get a higher throughput than higher priority mobiles if the mobiles
are using different timeslots.</p>
</div>


<p>See the following examples of situations where a lower
priority MS gets higher throughput in uplink than 2 higher priority MSs. For
an overview, see <em>Overview of Priority Class Based Quality of Service</em>.</p>


<a name="mar13141837" shape="rect"></a>
<div>
<h6>Example: Multislot MS class and GPRS territory size</h6>



<p>A lower priority MS gets higher throughput in uplink than
2 higher priority MSs because of restrictions to allocate multislot MSs due
to a limited GPRS territory size.</p>



<p>Assumptions:</p>


<ul>
<li><p>3 channels in GPRS territory</p>
</li>
<li><p>Two Gold users with MS class 4 mobiles</p>
</li>
<li><p>Bi-directional TBFs</p>
</li>
</ul>



<p>There are two uplink TBFs allocated in timeslot 6 and none
in timeslots 5 and 7. This timeslot allocation is not optimal usage of uplink
resources, but MS classes of mobiles do not allow other kind of 3+1 configurations.</p>


<a name="mar131419348" shape="rect"></a>
<pre xml:space="preserve">Gold user 1 = A
Gold user 2 = B

Allocation in Downlink	            
-----------------------------       
                        B B B       
                        A A A       
TRX Channels  0 1 2 3 4 5 6 7       
-----------------------------
      
Allocation in Uplink
-----------------------------
                          B  
                          A 
TRX Channels  0 1 2 3 4 5 6 7 
-----------------------------</pre>

<p>Next, one BestEffort user is added with One Phase Access.
The Best Effort user gets better throughput for uplink TBF. This is normal
behavior, and the situation cannot be changed without degrading the data rates
for the downlink TBFs of Gold users.</p>


<a name="mar131420359" shape="rect"></a>
<pre xml:space="preserve">BestEff user = C

Allocation in Downlink
-----------------------------       
                            C                                   
                        B B B       
                        A A A        
TRX Channels  0 1 2 3 4 5 6 7       
-----------------------------       

Allocation in Uplink
-----------------------------
                          B
                          A C
TRX Channels  0 1 2 3 4 5 6 7
-----------------------------</pre></div>


<a name="mar1314211710" shape="rect"></a>
<div>
<h6>Example: TBF Release</h6>



<p>A lower priority MS temporarily gets higher throughput
in both uplink and downlink than 2 higher priority MSs because of TBF release.
This situation is only temporary, but with default value of parameter TBF_LOAD_GUARD_TRESHOLD
it can continue for one second.</p>



<p>Assumptions:</p>


<ul>
<li><p>4 channels in GPRS territory</p>
</li>
<li><p>Three Gold users with MS class 6 mobiles
(2+2 channels).</p>
</li>
<li><p>One Best Effort user with MS class
6 mobile (2+2 channels).</p>
</li>
<li><p>Bi-directional TBFs.</p>
</li>
</ul>



<p>All four TBFs have two channels both in uplink and downlink
directions. The Gold user 2 has the best service, as it shares channels with
a Best Effort user. </p>


<a name="mar1314224611" shape="rect"></a>
<pre xml:space="preserve">Gold user 1 = A
Gold user 2 = B
Gold user 3 = C
BestEff user = D

Allocation in Downlink	    
-----------------------------  
                      D D C C    
                      B B A A   
TRX Channels  0 1 2 3 4 5 6 7   
-----------------------------

Allocation in Uplink
-----------------------------
                      D D C C
                      B B A A
TRX Channels  0 1 2 3 4 5 6 7
-----------------------------  </pre>

<p>Next the Gold user 2 completes his data transfer and the
TBF 'B' is released normally.</p>



<p>Now the Best Effort user 'D' gets better a throughput for
both uplink and downlink TBFs. This situation lasts until a reallocation check
occurs to either the Gold user 'A' or the Gold user 'C'.</p>


<a name="mar1314252714" shape="rect"></a>
<pre xml:space="preserve">Allocation in Downlink	    
-----------------------------       
                          C C       
                      D D A A       
TRX Channels  0 1 2 3 4 5 6 7       
-----------------------------

Allocation in Uplink
-----------------------------
                          C C
                      D D A A
TRX Channels  0 1 2 3 4 5 6 7
----------------------------- </pre>

<p>The situation is corrected after the reallocation check
for example as shown below.</p>


<a name="mar1314251013" shape="rect"></a>
<pre xml:space="preserve">Allocation in Downlink	    
-----------------------------   
                      C C      
                      D D A A   
TRX Channels  0 1 2 3 4 5 6 7   
-----------------------------

Allocation in Uplink
-----------------------------
                      C C
                      D D A A
TRX Channels  0 1 2 3 4 5 6 7
----------------------------- </pre></div>


<p>The tables below show the default values in BSC. In uplink,
TBF Gold class is only used for signaling, not for user data. 100 000 / scheduling
step size = weight value. The scheduler allocates resources for a TBF according
to the QoS. With these values, Gold gets twice as much time as Silver users
and four times the amount of BestEffort users.</p>


<a name="mar1314261915" shape="rect"></a>
<div>
<table border="1">
<thead>
<tr align="left" char="" charoff="50" valign="bottom">
<th colspan="1" rowspan="1" valign="top"><p>QoS class DL</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Weight value in allocation</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Scheduling Step</p>
</th>
</tr>
</thead>
<tbody>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Gold</p>
</td>
<td colspan="1" rowspan="1"><p>33333</p>
</td>
<td colspan="1" rowspan="1"><p>3</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Silver</p>
</td>
<td colspan="1" rowspan="1"><p>16666</p>
</td>
<td colspan="1" rowspan="1"><p>6</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Bronze</p>
</td>
<td colspan="1" rowspan="1"><p>8333</p>
</td>
<td colspan="1" rowspan="1"><p>12</p>
</td>
</tr>
</tbody>
</table>
</div>


<a name="p2xhtm-repid-38" shape="rect"></a>
<div>
<table border="1">
<thead>
<tr align="left" char="" charoff="50" valign="bottom">
<th colspan="1" rowspan="1" valign="top"><p>QoS class UL</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Weight value in allocation</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Scheduling Step</p>
</th>
</tr>
</thead>
<tbody>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Gold</p>
</td>
<td colspan="1" rowspan="1"><p>33333</p>
</td>
<td colspan="1" rowspan="1"><p>3</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Silver</p>
</td>
<td colspan="1" rowspan="1"><p>16666</p>
</td>
<td colspan="1" rowspan="1"><p>6</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Bronze</p>
</td>
<td colspan="1" rowspan="1"><p>11111</p>
</td>
<td colspan="1" rowspan="1"><p>9</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BestEffort</p>
</td>
<td colspan="1" rowspan="1"><p>8333</p>
</td>
<td colspan="1" rowspan="1"><p>12</p>
</td>
</tr>
</tbody>
</table>
</div>


<a name="mar1314303816" shape="rect"></a>
<div>
<p>Table: Mapping of QoS classes in DL/UL</p>


<table border="1">
<thead>
<tr align="left" char="" charoff="50" valign="bottom">
<th colspan="1" rowspan="1" valign="top"><p>DL</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>UL</p>
</th>
</tr>
</thead>
<tbody>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Gold</p>
</td>
<td colspan="1" rowspan="1"><p>Silver</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Silver</p>
</td>
<td colspan="1" rowspan="1"><p>Bronze</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BestEffort</p>
</td>
<td colspan="1" rowspan="1"><p>BestEffort</p>
</td>
</tr>
</tbody>
</table>
</div>


<a name="p2xhtm-repid-40" shape="rect"></a>
<div>
<p>Table: QoS class/allocation class mapping in HLR</p>


<table border="1">
<thead>
<tr align="left" char="" charoff="50" valign="bottom">
<th colspan="1" rowspan="1" valign="top"><p>QoS</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Allocation Class</p>
</th>
</tr>
</thead>
<tbody>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Gold</p>
</td>
<td colspan="1" rowspan="1"><p>1</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Silver</p>
</td>
<td colspan="1" rowspan="1"><p>2</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BestEffort</p>
</td>
<td colspan="1" rowspan="1"><p>3</p>
</td>
</tr>
</tbody>
</table>
</div>


<a name="mar13144713" shape="rect"></a>
<div>
<h6>Example</h6>



<p>The following example suggests a possible radio network
configuration to enable the best throughput for different phones and QoS classes
and an efficient use of the Dynamic Abis resources:</p>



<p>Desired situation:</p>


<ul>
<li><p>Dynamic Abis is only used by MCS-coded
TBFs</p>
</li>
<li><p>There are no multiplexed TSLs in the
territory</p>
</li>
<li><p>Territory size allows each phone resources
according to phones maximum capability</p>
</li>
</ul>



<p>For the two first ones the simplest solution is to make
a segment configuration. The segment would contain:</p>


<ul>
<li><p>BTS 1 EDGE1900 BCCH</p>
</li>
<li><p>BTS 2 GPRS 1900</p>
</li>
</ul>



<p>In case of a Dual Band environment we could add:</p>


<ul>
<li><p>BTS 3 EDGE 850</p>
</li>
</ul>



<p>This configuration would automatically isolate the GPRS
and EGPRS territories and, as a result, prevent the CS-coded TBFs from using
the Dynamic Abis resources.</p>



<p>Territory size and Dynamic Abis pool size would need to
be considered together. For example, a default territory of 3 TSLs is required
to allow MS class 4 the maximum of 3 TSLs. For 3 master channels, at least
3 TSLs are required from the Dynamic Abis pool in order to allocate 4 slave
channels for each master using MCS-8 or MCS-9. </p>
</div>


<a name="mar131449154" shape="rect"></a>
<div>
<h6>Example: MML examples</h6>


<ul>
<li><p>Interrogate basic BTS GPRS/EGPRS parameters.</p>


<a name="mar131449535" shape="rect"></a>
<pre xml:space="preserve">EQO:BTS=11:GPRS:;

DX 200    SONJA                     2003-01-31  13:12:58

GPRS PARAMETERS:
================

SEG-011                  
BCF-011   BTS-011                  
-------------------------------------
BTS ADMINISTRATIVE STATE ... UNLOCKED
BTS OPERATIONAL STATE ...... WO
BTS BACKGROUND DATA STATE .. NOT DEFINED


GPRS ENABLED.............................(GENA)... Y
   NETWORK SERVICE ENTITY IDENTIFIER.....(NSEI)...   299
   BSSGP VIRTUAL CONNECTION IDENTIFIER...(BVCI)... 10011
ROUTING AREA IDENTIFICATION..............(RAI)
   MOBILE COUNTRY CODE...................(MCC).... 234
   MOBILE NETWORK CODE...................(MNC).... 152
   LOCATION AREA CODE....................(LAC).... 04370
ROUTING AREA CODE........................(RAC).... 123
EGPRS ENABLED............................(EGENA).. N
DEDICATED GPRS CAPACITY..................(CDED)... 30 %
DEFAULT GPRS CAPACITY....................(CDEF)... 30 %
MAX GPRS CAPACITY........................(CMAX)... 45 %
PREFER BCCH FREQUENCY GPRS...............(BFG).... N
DL ADAPTION PROBABILITY THRESHOLD........(DLA).... 20 %
UL ADAPTION PROBABILITY THRESHOLD........(ULA).... 10 %
DL BLER CROSSPOINT CS SELECTION NO HOP...(DLB).... 90 %
UL BLER CROSSPOINT CS SELECTION NO HOP...(ULB).... 90 %
DL BLER CROSSPOINT CS SELECTION HOP......(DLBH)... 20 %
UL BLER CROSSPOINT CS SELECTION HOP......(ULBH)... 24 %
CODING SCHEME NO HOP.....................(COD).... 2
CODING SCHEME HOP........................(CODH)... 0
INITIAL MCS FOR ACKNOWLEDGED MODE........(MCA).... 7
INITIAL MCS FOR UNACKNOWLEDGED MODE......(MCU).... 7
MAXIMUM BLER IN ACKNOWLEDGED MODE........(BLA).... 90 %
MAXIMUM BLER IN UNACKNOWLEDGED MODE......(BLU).... 10
MEAN BEP OFFSET GMSK.....................(MBG).... 0
MEAN BEP OFFSET 8PSK.....................(MBP).... 0
EGPRS LINK ADAPTATION ENABLED............(ELA).... 0

COMMAND EXECUTED </pre></li>
<li><p>Interrogate DIRE of a segment:</p>


<a name="mar131450286" shape="rect"></a>
<pre xml:space="preserve">EQO:SEG=12:RAD:;

DX 200    SONJA                     2003-01-31  13:13:54

RADIO LINK CONTROL DL PARAMETERS:
=================================

SEG-012                  
BCF-011   BTS-012                  
BCF-011   BTS-015                  
-------------------------------------

CELL RESELECT HYSTERESIS.................(HYS).... 04  dB
MS TXPWR MAX CCH.........................(TXP1)... 33  dBm
MS TXPWR MAX CCH 1X00....................(TXP2)... 30  dBm
RXLEV ACCESS MIN.........................(RXP)....-105 dBm
RADIO LINK TIMEOUT.......................(RLT).... 20  SACCH FRAMES
POWER OFFSET.............................(PO)..... 00  dB
GPRS RXLEV ACCESS MIN....................(GRXP)...-105 dBm
GPRS MS TXPWR MAX CCH....................(GTXP1).. 33  dBm
GPRS MS TXPWR MAX CCH 1X00...............(GTXP2).. 30  dBm
GPRS CELL RESELECT HYSTERESIS............(GHYS)... 04  dB
DIRECT GPRS ACCESS.......................(DIRE)... 0 dBm
RA RESELECT HYSTERESIS...................(RRH).... 4 dB
C31 HYSTERESIS...........................(CHYS)... N
C32 QUAL.................................(QUAL)... N
RANDOM ACCESS RETRY......................(RAR).... Y
RESELECTION TIME.........................(RES).... 5 SECONDS
PRIORITY CLASS...........................(PRC).... 0
HCS THRESHOLD............................(HCS).... -

COMMAND EXECUTED</pre></li>
<li><p>Interrogate NBL of a BTS:</p>


<a name="mar131451257" shape="rect"></a>
<pre xml:space="preserve">EQO:BTS=12:MIS:;

DX 200    SONJA                     2003-01-31  13:14:04

MISCELLANEOUS PARAMETERS:
=========================

SEG-012                  
BCF-011   BTS-012                  
-------------------------------------
BTS ADMINISTRATIVE STATE ... UNLOCKED
BTS OPERATIONAL STATE ...... WO
BTS BACKGROUND DATA STATE .. NOT DEFINED

MS TX PWR MIN............................(PMIN)... 00  dBm
RX DIVERSITY.............................(RDIV)...  N
RADIUS EXTENSION.........................(EXT).... 00 km  (NORMAL CELL)
SOFTBLOCKING THRESHOLD ON REGULAR FREQ...(STR).... 255
SOFTBLOCKING THRESHOLD ON SUPER FREQ.....(STS).... 255
NON BCCH LAYER OFFSET....................(NBL)....  0 dBm
BTS LOAD IN SEG..........................(LSEG)...  70 %

COMMAND EXECUTED



EQO:BTS=12:RAD:;

DX 200    SONJA                     2003-01-31  13:14:10

RADIO LINK CONTROL DL PARAMETERS:
=================================

SEG-012                  
BCF-011   BTS-012                  
-------------------------------------
BTS ADMINISTRATIVE STATE ... UNLOCKED
BTS OPERATIONAL STATE ...... WO
BTS BACKGROUND DATA STATE .. NOT DEFINED

GPRS NON BCCH LAYER RXLEV UPPER LIMIT....(GPU)....-095 dBm
GPRS NON BCCH LAYER RXLEV LOWER LIMIT....(GPL)....-100 dBm

COMMAND EXECUTED</pre></li>
<li><p>Interrogate scheduling step for different
QoS classes in a BSC:</p>


<a name="mar431256312" shape="rect"></a>
<pre xml:space="preserve">EEO:QOS:;</pre>
<a name="p2xhtm-repid-41" shape="rect"></a>
<div>
<pre xml:space="preserve">DX 200    SONJA                     2003-01-31  13:17:58
BSC QUALITY OF SERVICE DATA

DL HIGH PRIORITY SSS..............................(DHP)....   3
DL NORMAL PRIORITY SSS............................(DNP)....   6
DL LOW PRIORITY SSS...............................(DLP)....  12
UL PRIORITY 1 SSS.................................(UP1)....   3
UL PRIORITY 2 SSS.................................(UP2)....   6
UL PRIORITY 3 SSS.................................(UP3)....   9
UL PRIORITY 4 SSS.................................(UP4)....  12

COMMAND EXECUTED</pre></div>
</li>
<li><p>Modify scheduling step to get equal
treatment for every QoS in DL:</p>


<a name="mar131452129" shape="rect"></a>
<pre xml:space="preserve">EEV:DHP=1,DNP=1,DLP=1,:</pre></li>
<li><p>Modify GPU and GPL of a BTS:</p>


<a name="mar1314522510" shape="rect"></a>
<pre xml:space="preserve">EQG:BTS=12:GPU=-80,GPL=-90,:</pre></li>
<li><p>Modify DIRE of a segment:</p>


<a name="mar1314523911" shape="rect"></a>
<pre xml:space="preserve">EQG:SEG=12:DIRE=-10,:</pre></li>
<li><p>Modify NBL of a segment:</p>


<a name="mar131453612" shape="rect"></a>
<pre xml:space="preserve">EQM:BTS=12:NBL=-20,:</pre></li>
</ul>
</div>
</div>
</div>
</body>
</html>