<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Interworking with other features</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:dn03297833:4:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-15T12:08:55Z"?>
<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:dn03297833:4:en:global:publishing_online_1_0:data:data:5:*:*" date="2005-02-15T12:08:55Z"?>
</head>
<body lang="en" xml:lang="en">
<p><a name="feb2031244429" shape="rect"></a>
<a name="ned_12" 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=dn03297833&amp;edition=4&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">System impact of Adaptive Multi Rate Codec (AMR)</a></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn03297833_about&amp;edition=4&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=dn03297833_about&amp;edition=4&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>Interworking with other features</h2>

<a name="nov15215183529" shape="rect"></a>
<div class="topic">
<h3>Direct
access to desired layer/band (DADL/B)</h3>

<p>To support the 2nd generation BTSs in the AMR environment, <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=id011216#id011216" 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=id011216#id011216');return false" shape="rect" target="_blank">DADL/B</a> is used to hand over AMR calls to co-located
AMR capable cells during the call set-up phase. Both intra-BSC and inter-BSC
DADL/B handovers are possible and preferably inside one frequency band as
the failure probability is higher with DADL/B handovers between bands. Figure
2, <em>DADL/B and prioritisation</em>, shows an example of
DADL/B.</p>


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


<p>TCH assignment versus DADL/B handover start:</p>


<ul>
<li><p>If an AMR call is attempted and there
are no TCHs available in the accessed cell, then Directed Retry (DR) due to
congestion, with or without queuing, is made.</p>
</li>
<li><p>If there are TCHs available in the
accessed cell and there are adjacent cells defined as DADL/B handover target
cells with the parameter <span class="parameter-sem">AMR Target Cell of Direct Access
to Desired Layer</span>, the DADL/B handover is applied. Adjacent cells are
not verified according to the MS capabilities (single band, dual band or tri-band),
but they have to fulfill the current signal level requirements to be considered
as a target cell for DADL/B handover. The current method for sorting the target
adjacent cells is used.</p>
</li>
<li><p>If no DADL/B handover target cells
are defined, the TCH is allocated from the accessed cell and another speech
codec than AMR is chosen.</p>
</li>
</ul>
</div>


<a name="nov2731023521" shape="rect"></a>
<div class="topic">
<h3>Enhanced
TRX priorisation</h3>

<p>With the use of TRP parameter, the operator can direct
AMR calls primarily to non-BCCH TRX and non-AMR calls primarily to BCCH TRX.</p>
</div>


<a name="nov2731221332" shape="rect"></a>
<div class="topic">
<h3>Common
BCCH Control and Multi BCF Control</h3>

<p>In segment environment, if the AMR codec set of the BCCH
BTS of the cell is disabled, it must also be disabled in the other BTSs of
that cell. </p>


<p>In segment environment, if the AMR codec set of the BCCH
BTS of the cell is enabled, it must also be enabled in the other BTSs of that
cell. </p>


<p>AMR FR and AMR HR codec sets can be disabled or enabled
separately. </p>


<p>For more information, see <em>Common BCCH Control in
BSC</em> and <em>Multi BCF Control in BSC</em> in BSC/TCSM documentation.</p>
</div>


<a name="nov273122283" shape="rect"></a>
<div class="topic">
<h3>Queuing
and Pre-emption</h3>

<p><em>Queuing</em>: a new indicator, the
speech codec list from the Channel Type element relating to TCH rates that
are required, is stored in the queue. </p>


<p><em>Pre-emption</em>: the same information
as in the case of queuing is stored in the data structures 'BTS Forced Release
Data Structure' or 'BTS Forced Handover Data Structure'.</p>
</div>


<a name="nov15215213330" shape="rect"></a>
<div class="topic">
<h3>Intelligent
Frequency Hopping and Intelligent Underlay-Overlay</h3>

<p>AMR-specific good and bad C/I thresholds are specified
for the HR and AMR FR:</p>


<ul>
<li><p>super reuse good C/I threshold for
AMR HR</p>
</li>
<li><p>super reuse bad C/I threshold for AMR
HR</p>
</li>
<li><p>super reuse good C/I threshold for
AMR FR</p>
</li>
<li><p>super reuse bad C/I threshold for AMR
FR</p>
</li>
</ul>


<p>Current Nx and Px values of C/I thresholds are in use.</p>


<p>The new threshold values for the AMR HR also serve the
basic HR. The current good and bad threshold pair (super reuse good C/I threshold
and super reuse bad C/I threshold) is going to serve the basic FR.</p>


<p>With these new thresholds you can control which type of
speech calls are preferred to enter the super layers cells, for example AMR
HR calls could be packed to the super layer in order to increase the capacity
of regular layer cells (good value for AMR HR - 5 dB compared to the current
value and good value for AMR FR for example. + 5 dB).</p>
</div>


<a name="dec2331455311" shape="rect"></a>
<div class="topic">
<h3>Satellite
Abis</h3>

<p>Full Rate AMR with Satellite Abis is supported, but Half
Rate AMR not.</p>
</div>
</div>
</div>
</body>
</html>