<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>EGPRS with Multi BCF and Common BCCH</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:dn02257765:5:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-28T15:45:36Z"?>
<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:dn02257765:5:en:global:publishing_online_1_0:data:data:45:*:*" date="2005-02-28T15:45:36Z"?>
</head>
<body lang="en" xml:lang="en">
<p><a name="dec112753391" shape="rect"></a>
<a name="ned_3" 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=dn02257765&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">Planning EGPRS features</a></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn02257765_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=dn02257765_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>EGPRS with Multi BCF and Common BCCH</h2>

<p>The Multi BCF feature utilises a radio network object called a Segment.
Several BTS objects can belong to one segment, but only one of the BTS objects
can have a broadcast control channel (BCCH).</p>


<p>The basic idea (initially ignoring EDGE) behind the Common
BCCH is to include 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=id012008#id012008" 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=id012008#id012008');return false" shape="rect" target="_blank">GSM 900</a> (both PGSM 900 and EGSM 900)
and <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=id012006#id012006" 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=id012006#id012006');return false" shape="rect" target="_blank">GSM 1800</a> TRXs into one cell with a single BCCH allocated
from one band used in the cell. The BCCH of the neighbour cell is measured
from one band only. The Common BCCH is configured in only one of the bands
of operation when resources across all bands are co-located and synchronised.</p>


<p>The (E)GPRS territory handling parameters are kept at BTS
object level. This means that the (E)GPRS territory must be defined separately
for each BTS object.</p>


<p>There are two alternative ways to configure the TRXs belonging to a
given BTS object:</p>


<ul>
<li><p>EDGE TRXs are configured to separate BTS objects</p>
</li>
<li><p>EDGE TRXs and non-EDGE TRXs are configured to the same BTS object.</p>
</li>
</ul>


<p>The first alternative, in other words configuring the EDGE TRX to separate
BTS objects, is recommended.</p>


<p>If both EDGE and non-EDGE TRXs are configured to the same BTS object,
GPRS must be disabled in the non-EDGE capable TRXs because both GPRS and EGPRS
territories cannot be defined to the same BTS object simultaneously. The operator
can disable GPRS by setting the TRX-specific <span class="parameter-sem">GPRS enabled</span>
parameter to off state.</p>


<p>If the segment includes several BTS objects differing only
in EDGE support:  </p>


<ul>
<li><p>EGPRS TBFs can only be allocated to
EDGE-capable BTSs (or also to a GPRS-capable BTS according to the TBF allocation
rules, but in that case only GMSK modulation is possible)</p>
</li>
<li><p>Non-EDGE capable BTSs are preferred
for standard GPRS calls</p>
</li>
<li><p>EDGE-capable BTSs can also be used
for the standard GPRS data transfer if the load situation in the EDGE and
non-EDGE capable BTS objects so requires (this case introduces a degradation
when there is co-sharing between the GPRS and the EGPRS-capable MS)</p>
</li>
<li><p>If only the GPRS territory is available,
EGPRS can be converted to GPRS traffic and sent on the non-EDGE layer </p>
</li>
<li><p>If no GPRS territory is available,
an additional GPRS load can be directed to the EGPRS territory.</p>
</li>
</ul>


<p>In addition, the following restrictions must be taken into account in
a mixed configuration of EDGE and non-EDGE TRXs:</p>


<ul>
<li><p>AMR can only be used if both TRX types support AMR</p>
</li>
<li><p>BB hopping cannot be used in a mixed site configuration</p>
</li>
<li><p>The PBCCH (BCCH) can be located either on the EDGE or non-EDGE
TRX</p>


<p>If the PBCCH (BCCH) is located on an EDGE TRX:</p>


<ul>
<li><p>GPRS / EGPRS resources are decreased (1 TSL for BCCH and 1 TSL
for SDCCH usage -&gt; only 6 TSLs for PS traffic) </p>
</li>
<li><p>The BCCH TRX must be attenuated by one step (a requirement included
in the 3GPP specification 05.08) </p>
</li>
<li><p>A signal level measured by the MS at some instances in time will
be affected by the 8-PSK usage -&gt; the cell selection and HO procedures will
be sub-optimal</p>
</li>
</ul>


<p>If the PBCCH(BCCH) is located on a non-EDGE TRX:</p>


<ul>
<li><p>If the BCCH TRX becomes faulty, a recovery is made to the EDGE
TRX. In a BCCH recovery, the <span class="parameter-sem">GPRS enabled</span> parameter
is also swapped, and therefore the PS traffic capability is lost from the
cell.</p>
</li>
</ul>
</li>
<li><p>The EDGE TRX uses more capacity in case of GPRS CS-2 and two
timeslots are required</p>
</li>
<li><p>The (E)GPRS capacity decreases compared to a normal 2 TRX/cell
configuration. GPRS mobiles cannot decode 8-PSK blocks. If there is an UL
GPRS TBF on same channels, only the GMSK coding can be used for sending USF
information. The GPRS Subscriber will not be able to know / decode that UL
TSL has been scheduled for him/her as the message would be encoded in the
8-PSK. This limitation does not come from the PCU etc. This limitation does
not concern only that TSL where the UL TBF is, but all TSLs the DL EGPRS TBF
is using if even one of those has the UL GPRS TBF.</p>
</li>
</ul>


<p>The parameters for the Common BCCH and Multi BCF involved
with (E)GPRS are the following:</p>


<a name="dec112950447" shape="rect"></a>
<div>
<table border="1">
<thead>
<tr align="left" char="" charoff="50" valign="bottom">
<th colspan="1" rowspan="1" valign="top"><p>Q3 parameter name</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Range </p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>MML value</p>
</th>
</tr>
</thead>
<tbody>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p><em>pcuMaxNoDLtbfInCH</em></p>
</td>
<td colspan="1" rowspan="1"><p>0-16</p>
</td>
<td colspan="1" rowspan="1"><p>16</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p><em>pcuMaxNoULtbfInCH</em></p>
</td>
<td colspan="1" rowspan="1"><p>0-7</p>
</td>
<td colspan="1" rowspan="1"><p>7</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p><em>nonBCCHLayerOffset</em></p>
</td>
<td colspan="1" rowspan="1"><p>-40…+40 dBm</p>
</td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p><em>gprsNonBCCHRxlevUpper</em></p>
</td>
<td colspan="1" rowspan="1"><p>-110…-47 dBm</p>
</td>
<td colspan="1" rowspan="1"><p>-95</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p><em>gprsNonBCCHRxlevLower</em></p>
</td>
<td colspan="1" rowspan="1"><p>-110…-47 dBm</p>
</td>
<td colspan="1" rowspan="1"><p>-100</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p><em>directGPRSaccessBts</em></p>
</td>
<td colspan="1" rowspan="1"><p>-10…+10</p>
</td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p><em>gprsRxLevAccessMin (celllevel and ADJ
level)</em></p>
</td>
<td colspan="1" rowspan="1"><p>-110…-47 dBm</p>
</td>
<td colspan="1" rowspan="1"><p>-105</p>
</td>
</tr>
</tbody>
</table>
</div>


<a name="dec11275503" shape="rect"></a>
<div class="div">
<h3>TalkFamily/UltraSite BTS co-siting and synchronisation</h3>

<p>Multi BCF with Common BCCH can be used to synchronise a Nokia UltraSite
BTS to an existing Nokia TalkFamily BTS with a cable connection in order to
create an EDGE-capable layer on top of the existing non-EDGE layer. This allows
the operator to maximise the efficiency of large configurations, which could
otherwise be comprimised were synchronisation not possible.</p>


<p>The Nokia Talk-family and UltraSite TRXs can be configured
as a common sector. Only one BCCH transmission channel is required per sector. <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> between the sectors with the same frequency
lists can be used in synchronised BTSs, and synchronised handovers become
possible.</p>


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


<a name="dec162134572" shape="rect"></a>
<div class="topic">
<h4>Large
configurations and horizontal sectoring</h4>

<p>Once the large configurations, that is, UltraSite 8+8+8
and TALK 2+2+2, are required, horizontal expansion is a real benefit. To reduce
the number of UltraSite BTS cabinets at a particular site, UltraSite needs
to have the capability to split sectors horizontally across cabinets. </p>


<p>Figure <em>Large configurations</em> below shows an
example of an 8+8+8 UltraSite BTS configuration. Normally, this configuration
would require 3 cabinets, but by using horizontally split sectoring, the number
of cabinets can be reduced to 2.</p>


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