<?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:dn04111526:1:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-28T16:14:45Z"?>
<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:dn04111526:1:en:global:publishing_online_1_0:data:data:50:*:*" date="2005-02-28T16:14:45Z"?>
</head>
<body lang="en" xml:lang="en">
<p><a name="sep2831535485" shape="rect"></a>
<a name="ned_17" 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=dn04111526&amp;edition=1&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 Nokia EDGE</a></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn04111526_about&amp;edition=1&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=dn04111526_about&amp;edition=1&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="dec1541349425" shape="rect"></a>
<div class="topic">
<h3>GPRS</h3>

<p>The implementation of GPRS causes changes to the following existing
functions of the BSC:</p>


<ul>
<li><p><em>Hardware Configuration Management</em></p>


<p>Introduction of the PCU plug-in unit. The serving PCU must be the same
for all the TRXs in the same segment.</p>
</li>
<li><p><em>Radio Network Configuration Management</em></p>


<p>Introduction of GPRS-related radio network parameters.</p>
</li>
<li><p><em>Radio channel allocation</em></p>


<p>Division of radio resources into two territories for circuit switched
and GPRS traffic.</p>
</li>
<li><p><em>Counters and performance indicators</em></p>


<p>Introduction of GPRS-specific measurements and counters.</p>
</li>
</ul>
</div>


<a name="dec154142356" shape="rect"></a>
<div class="topic">
<h3>GPRS and EGPRS</h3>

<p>GPRS and EGPRS can be multiplexed dynamically on the same timeslot.
See <em>(E)GPRS TBF multiplexing</em> for details.</p>
</div>


<a name="dec321156364" shape="rect"></a>
<div class="topic">
<h3>Extended
Cell Range</h3>

<p>Cell resources in the extended area of a cell are not used
for GPRS.</p>


<a name="nov292141717" shape="rect"></a>
<dl class="note-notification">
<dt class="note-caption">Note</dt>
<dd>Packet control channels cannot be used with Extended Cell
Range.</dd>
</dl>
</div>


<a name="dec321157375" shape="rect"></a>
<div class="topic">
<h3>Frequency
Hopping</h3>

<p>In Baseband hopping, radio time slot 0 belongs to a different
hopping group from other radio time slots of a TRX. This makes radio time
slot 0 unusable for multislot connections. If Baseband hopping is employed
in a BTS, radio time slot 0 of any TRX in the BTS is not used for GPRS.</p>


<p>Both <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</a> 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=id08852#id08852" 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=id08852#id08852');return false" shape="rect" target="_blank">Baseband
hopping</a> are supported in EGPRS.</p>
</div>


<a name="dec321158346" shape="rect"></a>
<div class="topic">
<h3>Optimisation
of the MS Power Level</h3>

<p>The BSC attempts to allocate the traffic channels within
the circuit switched territory according to the interference level recommendation
the BSC has calculated, to allow the performing of optimisation of the MS
power level. When the BSC has to allocate a traffic channel for a circuit
switched request in the GPRS territory, the interference level recommendation
is no longer the guiding factor. Now the first GPRS radio time slot beside
the territory border is taken regardless of its interference level being among
the recommended ones or not. For more information, refer to <em>GPRS
in BSC</em>, section Radio resource management in BSC/TCSM Product Documentation
Set.</p>
</div>


<a name="dec32115997" shape="rect"></a>
<div class="topic">
<h3>Intelligent
Underlay-Overlay</h3>

<p>Super-reuse frequencies are not supported for GPRS.</p>
</div>


<a name="dec321159338" shape="rect"></a>
<div class="topic">
<h3>Dynamic
Hot Spot</h3>

<p>For the Dynamic Hot Spot feature, the possible traffic
on the GPRS channels is also meaningful. The radio time slots in GPRS traffic
are regarded as busy channels in the algorithms of the Dynamic Hot Spot feature
during traffic channel allocation. On the other hand, the BSC applies the
Dynamic Hot Spot algorithm when it allocates radio time slots for GPRS use
in case the radio time slots are above and beyond the operator-defined GPRS
territory. When allocating the default GPRS territory that the operator has
defined with the parameter <em>default GPRS capacity (CDEF)</em>,
the BSC does not apply the Dynamic Hot Spot algorithm.</p>
</div>


<a name="dec3212019" shape="rect"></a>
<div class="topic">
<h3>Dynamic
SDCCH allocation</h3>

<p>The BSC selects a traffic channel time slot to be reconfigured
as a dynamic SDCCH time slot always within the circuit switched territory.</p>
</div>


<a name="dec321202910" shape="rect"></a>
<div class="topic">
<h3>TRX
prioritisation in TCH allocation</h3>

<p>The operator can set the BCCH TRX or the non-BCCH TRXs
as preferred for the GPRS territory with the parameter <em>prefer
BCCH frequency GPRS (BFG)</em> . If no preference is indicated, then no
prioritisation is used between different TRX types when forming the GPRS territory
either.</p>
</div>


<a name="dec32121111" shape="rect"></a>
<div class="topic">
<h3>Trunk
reservation</h3>

<p>In trunk reservation, the BSC defines the number of idle
traffic channels. The BSC adds together the number of idle traffic channels
in the circuit switched territory and the number of traffic channels in the
radio time slots of the GPRS territory, excluding the ones that are in the
radio time slots that the BSC has allocated permanently for GPRS.</p>
</div>


<a name="dec321212712" shape="rect"></a>
<div class="topic">
<h3>TRX
fault</h3>

<p>When a TRX carrying traffic channels becomes faulty, the
radio time slots on the TRX are blocked from use. The BSC releases the possible
ongoing calls and the call control resources. The BSC downgrades the traffic
channels belonging to the GPRS territory in the faulty TRX from GPRS use.
To replace the lost GPRS capacity the BSC determines the possibility of a
GPRS territory upgrade in another TRX. </p>


<p>If the faulty TRX functionality is reconfigured to another
TRX in the cell, the <em>GPRS-enabled</em> TRX is also transferred
to the new TRX.</p>


<p>If the faulty TRX is EDGE capable, and GPRS in enabled
in the TRX and EGPRS is enabled in the BTS, the system tries to reconfigure
its functionality to another EDGE-capable TRX in the BTS.</p>


<a name="jan84944301" shape="rect"></a>
<dl class="note-notification">
<dt class="note-caption">Note</dt>
<dd>A TRX is an EDGE-capable TRX if the TRX HW is EDGE capable
and it is added to EDAP. A TRX is a non-EDGE-capable TRX if the TRX has no
EDGE HW or it is not added to EDAP.</dd>
</dl>
</div>


<a name="dec321223713" shape="rect"></a>
<div class="topic">
<h3>Resource
indication to MSC</h3>

<p>In general the BSC’s indication on the resources concerns
traffic channels of a BTS excluding those allocated permanently to GPRS (dedicated
GPRS channels). GPRS territory resources other than the dedicated ones are
regarded as working and idle resources.</p>
</div>


<a name="dec321231314" shape="rect"></a>
<div class="topic">
<h3>Half
Rate</h3>

<p>Permanent type half rate time slots are not used for GPRS
traffic. Thus it is recommended not to configure permanent half rate time
slots in TRXs that are planned to be capable of GPRS.</p>


<p>When the BSC can select the channel rate (full rate or
half rate) to be used for a circuit switched call based on the traffic load
of the target BTS, the load limits used in the procedure are calculated using
the operator defined BSC and BTS parameters <em>lower limit
for HR TCH resources (HRL)</em> , <em>upper limit for HR
TCH resources (HRU)</em> , <em>lower limit for FR TCH resources
(FRL)</em> , and <em>upper limit for FR TCH resources (FRU)</em>
. The BSC parameter <em>CS TCH allocation calculation (CTC)</em>
defines how the GPRS territory is seen when the load limits are calculated.
Depending on the value of CTC either only CS territory or both CS and GPRS
territories (excluding the dedicated GPRS timeslots) are used to calculate
the load limits. Additionally, with the CTC parameter the user can define
whether the resources in GPRS territory are seen as idle resources or as occupied
resources.</p>
</div>


<a name="dec321235015" shape="rect"></a>
<div class="topic">
<h3>High
Speed Circuit Switched Data (HSCSD)</h3>

<p>If GPRS has been enabled in a 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=id08864#id08864" 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=id08864#id08864');return false" shape="rect" target="_blank">HSCSD</a>-related
load limits are calculated based on the existing HSCSD parameters and the
following rules:</p>


<ul>
<li><p>the number of working resources includes
all the working <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=id011227#id011227" 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=id011227#id011227');return false" shape="rect" target="_blank">TCH/F</a> resources of a BTS, excluding
the ones that have been allocated permanently to GPRS.</p>
</li>
<li><p>the number of occupied TCH/F resources
includes all the occupied TCH/Fs of the circuit switched territory, as well
as the default GPRS territory TCH/Fs, excluding the GPRS radio time slots
defined as dedicated.</p>
</li>
<li><p>HSCSD parameter<em>HSCSD cell load upper limit (HCU)</em> is replaced with the radio network
GPRS parameter <em>free TSL for CS downgrade (CSD)</em> if
the latter is more restricting; thus the one is used that limits HSCSD traffic
earlier.</p>
</li>
</ul>


<p>The parameter <em>free TSL for CS downgrade
(CSD)</em> defines a margin of radio time slots that the BSC tries to preserve
idle for circuit switched traffic by downgrading the GPRS territory when necessary.</p>


<p>If HSCSD multislot allocation is denied based on the appropriate
parameters, the BSC rejects the transparent HSCSD requests and serves the
non-transparent HSCSD requests with one time slot.</p>


<p>If the time slot share in HSCSD allocation is not restricted,
the transparent requests are served preferably in the circuit switched territory,
and only in the GPRS territory if necessary. If a transparent HSCSD call ends
up in the GPRS territory, the BSC does not try to move it elsewhere with an
intra-cell handover. Instead it tries to replace the lost GPRS capacity by
extending the GPRS territory on the circuit switched side of the territory
border.</p>


<p>When the transparent HSCSD call inside the GPRS territory
is later released, the BSC returns the released radio time slots back to GPRS
use to keep the GPRS territory continuous and undivided. For more information
refer to <em>GPRS in BSC</em> section Radio resource management
in BSC documentation.</p>


<p>The non-transparent HSCSD requests are always served in
the circuit switched territory as long as there is at least one <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=id011227#id011227" 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=id011227#id011227');return false" shape="rect" target="_blank">TCH/F</a>
available. A normal HSCSD upgrade procedure is applied later to fulfil the
need of the non-transparent request, if the call starts with less channels
than needed and allowed. In order for the non-transparent call to get the
needed number of time slots, the BSC starts an intra-cell handover for suitable
single slot calls beside the non-transparent HSCSD call. At the start of the
handover, the BSC checks that a single slot call can be moved to another radio
time slot and that HSCSD upgrade is generally allowed.</p>


<p>A non-transparent HSCSD call enters the GPRS territory
only in case of congestion of the circuit switched territory. If multislot
allocation was originally defined as allowed, it is applied also within the
GPRS territory to serve the non-transparent request. If the BTS load later
decreases, so that a GPRS territory upgrade becomes enabled, the non-transparent
HSCSD call is handed over to another location in the BTS so that the GPRS
territory can be extended.</p>


<p>When deciding whether to downgrade an HSCSD call or the
GPRS territory the BSC checks first if the margin of idle resources defined
by the parameter <em>free TSL for CS downgrade (CSD)</em>
exists. If a sufficient margin exists, the BSC acts as without GPRS; that
is, using the state information that the HSCSD parameters define for the BTS,
the BSC performs an HSCSD downgrade if necessary. If the number of idle resources
is below the parameter <em>free TSL for CS downgrade (CSD)</em>,
then the actions proceed as follows:</p>


<ul>
<li><p>if there are GPRS radio time slots
that are above and beyond the operator defined default GPRS territory then
these additional GPRS radio time slots are the first target for the GPRS territory
downgrade</p>
</li>
<li><p>if there are no additional GPRS radio
time slots, the BSC examines if there are more HSCSD traffic channels than
the parameter <em>HSCSD TCH capacity minimum (HTM)</em> requires
and if so, executes an HSCSD downgrade</p>
</li>
<li><p>if the minimum HSCSD capacity is not
in use, then a GPRS territory downgrade is made to maintain the margin defined
by the parameter <em>free TSL for CS downgrade (CSD)</em>.</p>
</li>
</ul>


<p>As a TCH/F becomes free through a channel release, the
BSC first examines the need and possibility for an HSCSD upgrade. If the BSC
starts no HSCSD upgrade, it further checks the need and possibility for a
GPRS upgrade. The GPRS territory can be upgraded although the parameter HSCSD
TCH capacity minimum (HTM) is not in use and there are pending HSCSD connections
in the cell. The parameter <em>free TSL for CS upgrade (CSU)</em>
and the margin it defines is the limiting factor for GPRS territory upgrade.</p>


<p>The parameter <em>free TSL for CS upgrade
(CSU)</em> defines the number of radio time slots that has to remain idle
in the circuit switched territory after the planned GPRS territory upgrade
has been performed.</p>


<p>For more information on GPRS territories refer to <em>GPRS in BSC</em>, section Radio resource management in BSC
documentation.</p>


<p>For more information, see <em>HSCSD and
14.4 kbit/s Data Services in BSC</em> in BSC documentation.</p>
</div>


<a name="dec32128916" shape="rect"></a>
<div class="topic">
<h3>Radio
Network Supervision</h3>

<p>Actions of the radio network supervision do not apply for
time slots that have been included in the GPRS territory. You may want to
monitor the uplink interference on time slots in GPRS use.</p>


<p>Radio Network Supervision does not apply to the packet
control channel.</p>
</div>


<a name="dec32129717" shape="rect"></a>
<div class="topic">
<h3>BTS
testing</h3>

<p>The BTS testing cannot be executed on the packet control
channel.</p>
</div>


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

<p>The Multi BCF feature introduces a new radio network object
called the Segment. Several BTS objects can belong to one Segment. Only one
BTS object of the Segment can have a BCCH. The Segment can have BTS objects
which differ in:</p>


<ul>
<li><p>frequency band (900/1800, 800/1800,
800/1900)</p>
</li>
<li><p>power levels (Talk-family and UltraSite
base stations).</p>


<p>Power control is always on segment level, therefore there
are differences in the output depending on the hardware.</p>
</li>
<li><p>regular and super-reuse frequencies</p>
</li>
<li><p>normal and extended cell radius frequencies</p>
</li>
<li><p>EDGE capability.</p>
</li>
</ul>


<p>TRXs inside a BTS object must have common capabilities.
An exception to this is that EDGE-capable and non-EDGE-capable TRXs can be
configured to the same BTS object. In this case, GPRS must be disabled in
the non-EDGE-capable TRXs. (E)GPRS territory can be defined to each BTS object
separately. GPRS and EGPRS territories cannot both be defined to a BTS object
at the same time. Super-reuse and extended cell radius frequencies are not
supported in (E)GPRS.</p>


<p>There is only one BCCH /<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=id04450#id04450" 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=id04450#id04450');return false" shape="rect" target="_blank">CCCH</a>
and one or no PBCCH/PCCCH in one Segment. 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=id08956#id08956" 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=id08956#id08956');return false" shape="rect" target="_blank">PBCCH</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=id08928#id08928" 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=id08928#id08928');return false" shape="rect" target="_blank">PCCCH</a> must be on the same BTS and TRX as the BCCH.</p>


<a name="nov2921452932" shape="rect"></a>
<dl class="note-notification">
<dt class="note-caption">Note</dt>
<dd>The operator must define GPRS territory to the BCCH frequency
band in a Common BCCH cell in which more than one frequency band is in use.
Otherwise the GPRS feature does not work properly in the cell. The reason
for this requirement is that in cases when the MS RAC of the GPRS mobile is
not known by the BSC, the TBF must be allocated on the BCCH frequency band
first. During the first TBF allocation, the GPRS mobile indicates its frequency
capability to the BSC. After that other frequency bands of the cell can be
used for the GPRS mobile accordingly.</dd>
</dl>
</div>


<a name="mar831256161" shape="rect"></a>
<dl class="note-notification">
<dt class="note-caption">Note</dt>
<dd><p>GPRS territory must be configured into BCCH BTS in the
segment with two or more BTSs on the BCCH band if PBCCH is not used and BTS(s)
containing Gp channels is (are) hopping.  </p>



<p>This because without PBCCH, hopping frequency parameters
are encoded to the Immediate Assignment on CCCH with indirect encoding. When
the allocated BTS is hopping, indirect encoding can only refer to the System
Information 13 message, which in Nokia BSS contains GPRS Mobile Allocation
only for the BCCH BTS.</p>



<p>The limitation to use only indirect encoding with hopping
frequency parameters in Immediate Assignment comes from the fact that Immediate
Assignment message segmentation is not supported in Nokia BSS. The other two
possible hopping frequency encodings, direct 1 and 2, might use a large number
of octets for the frequency hopping. Large sized frequency parameters cause
control message segmentation. Thus as Immediate Assignment segmentation is
not supported, direct 1 and 2 encoding cannot be used.</p>



<p>Therefore, in a segment where BCCH band Gp channels are
on hopping BTS(s), TBFs must initially be allocated to the BCCH BTS. Later,
the TBFs may be reallocated to other BTSs as well. Further, if frequency hopping
and EGPRS are used in a cell without PBCCH, the operator must configure EDGE
territory to BCCH BTS or to a non-hopping BTS.</p>
</dd>
</dl>


<a name="dec103126441" shape="rect"></a>
<div class="topic">
<h3>IDD
and hopping compatibility</h3>

<p>The hopping mode setup (No hopping, BB hopping, RF hopping,
Antenna  hopping) applies to all TRXs within a Sector/BTS_Object. It is not
possible to mix BB, RF or Antenna hopping within a Sector/BTS_Object.</p>


<p>Note that with BB, RF and Antenna hopping it is possible
to set up the hopping parameters so that a TRX, or timeslot(s) within a TRX,
do not hop.</p>


<p>RF hopping and Antenna hopping cannot be used in a sector
which uses the Remote Tune Combiner (RTC).</p>


<p>IDD is set up per TRX, with 2 TRX units making 1 (logical)
IDD TRX; the BSC sees the IDD TRX pair as a single (logical) TRX.</p>


<p>BB hopping, Antenna hopping and IDD all use the BB hopping
HW, but in slightly different ways. This restricts some of the combinations
within the cabinet.</p>


<ul>
<li><p>It is possible to mix BB hopping, RF
hopping, and Antenna hopping sectors within an UltraSite / C-100 cabinet.</p>
</li>
<li><p>Within a cabinet it is not possible
to have a single sector that is BB hopping and uses IDD; Sector with IDD and
BB hopping will be introduced in future releases.</p>
</li>
<li><p>It is not possible to have an IDD sector
and a BB hopping sector within a cabinet.</p>
</li>
<li><p>It is not possible to have an IDD sector
and an Antenna Hopping sector within a cabinet.</p>
</li>
</ul>


<a name="dec1031222192" shape="rect"></a>
<div>
<p>Table: Summary</p>


<table border="1">
<thead>
<tr align="left" char="" charoff="50" valign="bottom">
<th colspan="1" rowspan="1" valign="top"><p>First Sector Type</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Second Sector Type</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Third Sector Type</p>
</th>
<th colspan="1" rowspan="1" valign="top"><p>Mixed Sectors Within Cabinet</p>
</th>
</tr>
</thead>
<tbody>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BB hopping</p>
</td>
<td colspan="1" rowspan="1"><p>RF hopping</p>
</td>
<td colspan="1" rowspan="1"><p>-</p>
</td>
<td colspan="1" rowspan="1"><p>Possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BB hopping</p>
</td>
<td colspan="1" rowspan="1"><p>Antenna hopping</p>
</td>
<td colspan="1" rowspan="1"><p>-</p>
</td>
<td colspan="1" rowspan="1"><p>Possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BB hopping</p>
</td>
<td colspan="1" rowspan="1"><p>IDD</p>
</td>
<td colspan="1" rowspan="1"><p>-</p>
</td>
<td colspan="1" rowspan="1"><p>Not possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BB hopping</p>
</td>
<td colspan="1" rowspan="1"><p>RF hopping</p>
</td>
<td colspan="1" rowspan="1"><p>Antenna hopping</p>
</td>
<td colspan="1" rowspan="1"><p>Possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BB hopping</p>
</td>
<td colspan="1" rowspan="1"><p>RF hopping</p>
</td>
<td colspan="1" rowspan="1"><p>IDD</p>
</td>
<td colspan="1" rowspan="1"><p>Not possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>BB hopping</p>
</td>
<td colspan="1" rowspan="1"><p>Antenna hopping</p>
</td>
<td colspan="1" rowspan="1"><p>IDD</p>
</td>
<td colspan="1" rowspan="1"><p>Not possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>RF hopping</p>
</td>
<td colspan="1" rowspan="1"><p>Antenna hopping</p>
</td>
<td colspan="1" rowspan="1"><p>-</p>
</td>
<td colspan="1" rowspan="1"><p>Possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>RF hopping</p>
</td>
<td colspan="1" rowspan="1"><p>IDD</p>
</td>
<td colspan="1" rowspan="1"><p>-</p>
</td>
<td colspan="1" rowspan="1"><p>Possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>RF hopping</p>
</td>
<td colspan="1" rowspan="1"><p>Antenna hopping</p>
</td>
<td colspan="1" rowspan="1"><p>IDD</p>
</td>
<td colspan="1" rowspan="1"><p>Not possible</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>Antenna hopping</p>
</td>
<td colspan="1" rowspan="1"><p>IDD</p>
</td>
<td colspan="1" rowspan="1"><p>-</p>
</td>
<td colspan="1" rowspan="1"><p>Not possible</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>


<a name="dec1031240494" shape="rect"></a>
<div class="topic">
<h3>Other
feature interactions</h3>

<p>TRX loop test is not possible with Baseband or Antenna
hopping.</p>
</div>


<a name="dec1031242505" shape="rect"></a>
<div class="topic">
<h3>Rx
Antenna Supervision</h3>

<p>Rx Antenna Supervision by comparing RSSI value is possible
with RF, Baseband and Antenna hopping, but with some combinations of RF cabling
configuration and hopping type, the results need care in interpretation.</p>


<p>The RSSI values for a sector are summarised as follows:</p>


<ul>
<li><p>Each TRX calculates an average of the
RSSI difference between Main and Div Antennas.</p>
</li>
<li><p>The O&amp;M then takes the average
of the RSSI difference figures from all TRXs in the sector, and reports the
single sector-wide average figure.</p>
</li>
</ul>
</div>
</div>
</div>
</body>
</html>