<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Interoperable features with Multi BCF</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:dn03501906:2:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-28T15:46:15Z"?>
<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:dn03501906:2:en:global:publishing_online_1_0:data:data:4:*:*" date="2005-02-28T15:46:15Z"?>
</head>
<body lang="en" xml:lang="en">
<p><a name="jan841515231" shape="rect"></a>
<a name="ned_16" shape="rect"></a></p>

<div class="div">
<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=dn03501906&amp;edition=2&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_15#ned_15" onclick="sync(this);return true" shape="rect">Interworking with other features</a></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn03501906_about&amp;edition=2&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=dn03501906_about&amp;edition=2&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">
<h3>Interoperable features with Multi BCF</h3>

<a name="dec3141043241" shape="rect"></a>
<div class="topic">
<h4>Common BCCH</h4>

<p>When Multi BCF and Common BCCH are combined you are allowed to configure
both BTSs to one segment by using different frequency bands and BTSs of different
base station types.</p>
</div>


<a name="dec321859451" shape="rect"></a>
<div class="topic">
<h4>Queueing</h4>

<p>When the segment architecture is used, the queueing for
traffic channels is a segment-level procedure including related parameters.</p>


<p>In a segment with several BTSs of different properties
it is possible that a TCH request cannot be served even though all the TCH
resources in a segment are not fully utilised. However, queueing can be started
if permitted by the related parameters.</p>


<p>The maximum number of possible calls in a queue is 32 when
the segment architecure is in use.</p>


<p>For more information, see <em>Radio Resource
Pre-emption and Queuing</em> in BSC/TCSM documentation.</p>
</div>


<a name="dec32191572" shape="rect"></a>
<div class="topic">
<h4>Pre-emption</h4>

<p>When the segment architecture is used, the Pre-emption
is a segment level function. </p>


<p>In a segment with several BTSs of different properties
it is possible that a TCH request cannot be served even though all the TCH
resources in a segment are not fully utilised. However, pre-emption is possible,
if permitted by the related parameters.</p>


<p>The candidate for the forced actions is selected among
the resource types that are indicated as reasonable in the resource request
that initiates these actions. In the candidate selection the criterion of
the lowest possible priority is the most important one. When searching for
the lowest priority call the different resource types are scanned in a reverse
order than in TCH allocation.</p>


<p>The maximum number of possible calls in a pre-emption queue
is 8.</p>


<p>For more information, see <em>Radio Resource
Pre-Emption and Queuing</em> in BSC/TCSM documentation.</p>
</div>


<a name="dec32192223" shape="rect"></a>
<div class="topic">
<h4>Intelligent
Underlay-Overlay (IUO)</h4>

<p>In the segment environment the use of Intelligent Underlay-Overlay
is BTS-specific. Each BTS in a segment can have its own regular and super-reuse
layers. The super-reuse layer of a BTS can only be accessed via the regular
layer of the BTS.</p>


<p>The target for a super-reuse TCH request is always one
BTS (a few TRXs within the BTS) and not the whole segment as in resource requests
in general. The handover procedure from regular resources to super-reuse resources
in a BTS is the same regardless of whether the segment architecture is used
or not.</p>


<p>When an IUO handover from a super-reuse TRX to regular
BTS resources is performed, the information on the usability of different
resource types in the segment is decided based on the values of parameter <span class="parameter-sem">Non Bcch Layer Offset</span> in different BTSs
of the segment. As a target the BSC accepts the BTSs whose <span class="parameter-sem">Non Bcch Layer Offset</span> value is less than, or equal to the
value of the BTS where the handover was initiated. This is indicated in the
figure <em>Possible handover directions on a segment</em>
with dash line arrows from the super-reuse layer of one BTS to the regular
layer of another BTS in a segment.</p>


<p>The child cell concept is not supported in a BSC in which
the segment option is enabled.</p>


<p>Direct access to super-reuse resources is possible in segments
consisting of only one BTS, and is not supported in segments with more than
one BTS.</p>


<a name="dec221450261" shape="rect"></a>
<div>
<img alt="urn:mars:dn02250284:1:en:global:cgm_fixed:data:data" border="0" src="NED?action=retrieve&amp;identifier=dn02250284&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=gif&amp;component=data&amp;item=data" /><p class="figure-caption">Figure: Possible handover directions in a segment</p>
</div>


<p>For more information, see <em>Intelligent
Underlay-Overlay</em> in BSC/TCSM documentation.</p>
</div>


<a name="dec32193194" shape="rect"></a>
<div class="topic">
<h4>Frequency
Hopping</h4>

<p>In segment architecture the resources of different base
station types are grouped as separate BTSs. Frequency Hopping is managed by
a BTS. All the different BTSs in a segment have their own hopping parameters
and hopping groups.</p>


<p>The segment architecture enables having BTSs without 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=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> TRX. This reduces the number of hopping groups
in a BTS's regular area, because there is no need for a separate group for
the BCCH TRX in RF hopping. In BB hopping, there is no need for separating
TSL0 from the other TSLs in BTSs that do not contain a BCCH TRX. However,
the separation between TSL0 and other TSLs remain and these are regarded as
two different hopping groups. The operator gives one set of parameters for
the TSL0 group and another for the other TSLs. A similar set of parameters
can be given for both.</p>


<p>The segment model offers the opportunity to have several
hopping groups even though there are only resources for one type in a segment.
The operator can form hopping groups by gathering the needed TRXs into one
BTS and have several BTSs of the same type.</p>


<p>For more information, see <em>Frequency
Hopping</em> in BSC/TCSM documentation.</p>
</div>


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

<p>From the point of view of <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>,
the effects of the segment structure appear mainly when allocating TCHs for
HSCSD requests. The basic principles that apply for the TCH allocation in
general are also valid in HSCSD cases. This means that the HSCSD resource
allocation is made considering the radio conditions and the loads on different
resource types.</p>


<p>Among the resource types that the BSC defines as reasonable,
the TCH search is performed in a way that the HSCSD channel configuration
which best fulfills the request is selected. Within a segment the HSCSD allocation
is made in a BTS that has no restrictions based on the HSCSD load parameters
rather than in a BTS where the allocation is restricted to include only one
TCH.</p>


<p>The operator can control the HSCSD traffic load between
a segment's BTSs by using the BTS-specific HSCSD load parameters <span class="parameter-sem">Min HSCSD Capacity Cell</span>, <span class="parameter-sem">Upper
Limit Cell Load HSCSD</span>, <span class="parameter-sem">Lower Limit
Cell Load HSCSD</span> and <span class="parameter-sem">Upper Limit Regular
Load HSCSD</span>.</p>


<p>If necessary, one HSCSD downgrade per segment per received
request is made in the segment environment. When the received request leads
to TCH allocation, the need for an HSCSD downgrade is examined in the BTS
of the allocation. If a free TCH cannot be found, the candidate for the HSCSD
downgrade is selected among the segment's BTSs that are defined as appropriate
targets for the request. A round robin method is used to direct separate downgrade
attempts to different BTSs in a segment. In each BTS the downgrade decision
is based on the HSCSD parameters of the particular BTS.</p>


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


<a name="dec32193526" shape="rect"></a>
<div class="topic">
<h4>GPRS</h4>

<p>When comparing the TCH load of a segment's BTS with the
parameter <span class="parameter-sem">BTS Load In Segment</span>, the
BSC interpretes <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=id04980#id04980" 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=id04980#id04980');return false" shape="rect" target="_blank">RTSL</a>s 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=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>
territory as busy channels (excluding dedicated GPRS resources). This interpretation
prevents the GPRS territory of a single BTS from shrinking unnecessarily,
if there are other BTSs in the segment where CS calls could be transferred
to from the BTS in question.</p>


<p>The interactions between the circuit switched radio resource
management of a segment and GPRS are described in TCH allocation in Common
BCCH segment environment. For the effects of the segment concept on the radio
resource management of the packet switched services in the PCU, see <em>GPRS in BSC</em> in BSC/TCSM documentation.</p>


<p>Every GPRS BTS in a segment has to be connected to the
same PCU.</p>
</div>


<a name="dec32194377" shape="rect"></a>
<div class="topic">
<h4>Intelligent
Coverage Enhancement (ICE)</h4>

<p>Intelligent Coverage Enhancements can be used in the BCCH
BTS of the Multi BCF segment.</p>
</div>


<a name="dec32194478" shape="rect"></a>
<div class="topic">
<h4>Extended
Cell and Multi BCF Control</h4>

<p>In the segment environment only BCCH BTS can have extended
area TRXs.</p>


<p>For more information, see <em>Extended Cell</em>
in BSC/TCSM documentation.</p>
</div>


<a name="dec32194589" shape="rect"></a>
<div class="topic">
<h4>Dynamic
SDCCH allocation</h4>

<p>The dynamic reconfiguration of the SDCCH radio time slots
is possible only in those BTSs of a Multi BCF segment which have a negative
value or value zero in parameter <span class="parameter-sem">Non BCCH
Layer Offset</span> and are thus indicated to have a signal level at least
as strong as in the BCCH BTS.</p>
</div>


<a name="dec321951010" shape="rect"></a>
<div class="topic">
<h4>Directed
Retry </h4>

<p>The Directed Retry or the Intelligent Directed Retry procedure
can be triggered even if all the resources of a segment are not completely
in use. It requires that all the resources that an accessing MS could utilise
under the current conditions are unavailable.</p>


<p>For more information, see <em>Directed Retry
Procedure in BSC</em> in BSC/TCSM documentation.</p>
</div>


<a name="dec321954811" shape="rect"></a>
<div class="topic">
<h4>Direct
Access to Desired Layer/Band (DADL/B)</h4>

<p>In the segment environment, DADL/B can be used to direct
traffic between segments. Everything related to DADL/B concerns a segment
instead of a BTS. The loads are evaluated per segment, adjacency definitions
are between segments and DADL/B handovers are made between segments.</p>


<p>For more information, see <em>Direct Access
to Desired Layer/Band</em> in BSC/TCSM documentation.</p>
</div>


<a name="dec321973212" shape="rect"></a>
<div class="topic">
<h4>Trunk
Reservation</h4>

<p>The control of Trunk Reservation is removed from the BTS
level to the segment level.</p>


<p>For more information, see <em>Trunk Reservation</em>
in BSC/TCSM documentation.</p>
</div>


<a name="dec321974113" shape="rect"></a>
<div class="topic">
<h4>Advanced
Multilayer Handling (AMH)</h4>

<p>The BSC-controlled traffic reason handover is a segment
level procedure, including the related parameters.</p>
</div>


<a name="dec321975114" shape="rect"></a>
<div class="topic">
<h4>MSC
controlled traffic reason handover</h4>

<p>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=id02939#id02939" 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=id02939#id02939');return false" shape="rect" target="_blank">MSC</a>-controlled traffic reason handover
(TRHO) and the related resource indications are segment-level procedures.</p>


<p>In the spontaneous resource indication method the segment-level
parameter <span class="parameter-sem">BTS Load Threshold</span> is used
when defining the need to send the resource indication.</p>
</div>


<a name="dec32198915" shape="rect"></a>
<div class="topic">
<h4>Dynamic
Hotspot (DHS)</h4>

<p>The Dynamic Hotspot control works mainly on the BTS level,
but the adjacencies are on the segment level. This means that all the possible
BTSs of an adjacent segment are examined, if the segment has been defined
as an interfered cell. For the decision on TCH usability in the examined segment,
the defined limit parameter values of separate interfered BTSs and the numbers
of occupied TCHs in them are summed up. Based on these two results the decision
of THC allocation capability is made. The counters related to Dynamic Hotspot
are updated for one BTS per TCH request in the target segment.</p>


<p>For more information, see <em>Dynamic Hotspot</em>
in BSC/TCSM documentation.</p>
</div>


<a name="dec321982216" shape="rect"></a>
<div class="topic">
<h4>Radio
network supervision</h4>

<p>The congestion supervision for alarm <span class="alarm-sem">7746
CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD</span> is monitored on the segment
level since the target for a channel request is a segment. In a segment with
several BTSs, the channel congestion supervision is made in the BCCH BTS for
the whole segment. A possible alarm on congestion, even if it is identified
with the BCCH BTS, describes the congestion level of the whole segment.</p>


<p>For more information, see <em>Radio Network
Supervision</em> in BSC/TCSM documentation.</p>
</div>


<a name="dec321983317" shape="rect"></a>
<div class="topic">
<h4>FACCH
call setup</h4>

<p>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=id011221#id011221" 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=id011221#id011221');return false" shape="rect" target="_blank">FACCH</a> call setup, the SDCCH phase is
skipped and the call is put directly to a TCH channel. At that time, the measurement
reports from the accessing terminal are not available. Therefore the usability
of the non-BCCH layer resources based on those reports cannot be defined.</p>


<p>In Multi BCF Control the FACCH setup is possible only in those BTSs
of a Multi BCF segment which have a negative value or value zero in parameter <span class="parameter-sem">Non BCCH Layer Offset</span> and are thus indicated to have
a signal level at least as strong as in the BCCH BTS.</p>
</div>


<a name="dec321984318" shape="rect"></a>
<div class="topic">
<h4>Adaptive
Multirate (AMR)</h4>

<p>Decisions on the need for packing AMR FR (full rate) calls
to AMR HR (half rate) calls is based on the load situation of each individual
BTS also in the segment environment. AMR FR calls in a particular BTS are
packed depending on the load of that individual BTS. Furthermore, the intra
cell handovers that perform the actual packing of calls are implemented as
BTS internal events. When an intra-segment TCH handover is made in order to
decrease the load of a BTS, the number of the possible requests for AMR FR
call packing in the BTS is decreased in order to avoid unnecessary handovers.</p>
</div>


<a name="jan841610561" shape="rect"></a>
<div class="topic">
<h4>Recovery
for BSS and Site Synchronisation</h4>

<p>Recovery for BSS and Site Synchronisation offers synchronisation
recovery for Multi BCF site and a possibility to define the Multi BCF chain
configuration to BSC's Radio Network database. If Recovery for BSS and Site
Synchronisation is activated for UltraSite/MetroSite/Talk-family BTS chain,
all BCF sites in the chain are restarted automatically if need be when master
clock BCF is restarted.</p>


<p>For more information, see <em>BSS11073 Recovery
for BSS and Site Synchronisation</em> in BSC/TCSM documentation.</p>
</div>
</div>
</div>
</div>
</body>
</html>