<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Radio Network Configuration Management</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:dn0446319:1:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-28T15:41:20Z"?>
<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:dn0446319:1:en:global:publishing_online_1_0:data:data:36:*:*" date="2005-02-28T15:41:20Z"?>
</head>
<body lang="en" xml:lang="en">
<p><a name="ned_top" shape="rect"></a>
<a name="ned_1" shape="rect"></a></p>

<a name="jan18510275440" shape="rect"></a>
<a name="p2xhtm-repid-1" shape="rect"></a>
<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%"></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn0446319_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=dn0446319_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">
<h1>Radio Network Configuration Management</h1>

<p>To run a mobile network requires managing a number of radio
network elements and parameters controlling the functions of the radio network.
As the radio network configuration is not static but changes due to an increasing
demand of coverage and capacity, fast and easy-to-use access to the configuration
data is required. In addition, changes must not cause unnecessary service
breaks.</p>


<p>The Radio Network Configuration Management in the BSC supports
managing the radio network structure and data in case of</p>


<ul>
<li><p>Building the radio network</p>
</li>
<li><p>Expanding the network</p>
</li>
<li><p>Reconfiguring the network</p>
</li>
<li><p>Changing and optimising the functioning
of the network</p>
</li>
<li><p>Deploying advanced features into the
network.</p>
</li>
</ul>


<p>Most of the changes can be done on-line. This means that
when making configuration or parameter changes concerning, for example, a
base station, other base stations are not disturbed.</p>


<p>The radio network data consists of logical radio network
objects, and their parameters are stored in the Radio Network Database of
the BSC. The managed objects are: BSC, Base Control Function (BCF), Base Station
(BTS), Transceiver (TRX), Radio Timeslot (RTSL), Handover Control Parameters
per cell (HOC), Power Control Parameters per cell (POC), Adjacent Cell definitions
(ADJC), Frequency Hopping Systems per cell (FHS), BCCH Allocation Frequency
List (BA), Mobile Allocation Frequency List (MA), and Trunk Reservation Threshold
Table (TRK_TBL).</p>


<p>The object hierarchy is shown below.</p>


<a name="apr16410385024" shape="rect"></a>
<div>
<img alt="urn:mars:dn0469853:1:en:global:tiff:data:data" border="0" src="NED?action=retrieve&amp;identifier=dn0469853&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=gif&amp;component=data&amp;item=data" /><p class="figure-caption">Figure: Object hierarchy</p>
</div>


<p>The following operations are supported:</p>


<p>Creating and removing objects (BCF, BTS, TRX, ADJC, BA,
MA, and TRK_TBL) in the database</p>


<p>Changing of parameter values. The change is distributed
and activated immediately. Changes in the following objects are possible on-line,
that is, they do not cause any break in the service: BSC level parameters,
handover and power control parameters, adjacent cell definitions, BA frequency
lists, trunk reservation tables, most of the cell parameters.</p>


<p>Managing frequency hopping (both baseband hopping and radio
frequency hopping);</p>


<p>Interrogating parameter values;</p>


<p>Changing the administrative state (LOCKED/UNLOCKED) of
the object (BCF, BTS, TRX, and RTSL);</p>


<p>Displaying the operational states of the functional entities
(BCF, BTS, TRX, and RTSL).</p>


<p>The enhancement 'Three Digit Mobile Network Code' allows
the use of 3-digit Mobile Network Codes (MNC). The maximum number of networks
is 1000 within one country within one Mobile Country Code (MCC).</p>


<p>In an enhancement 'Radio Network MML Improvement' there
are improvements for Output Radio Network Configuration and Check Adjacent
Cell Data MML commands. There is also a new command for checking that the
amount of IUO interfering cell definitions does not exceed the allowed maximum.</p>


<p>The enhancement 'Guard Channel Management' enables the
use-guarded channels by controlling the maximum TRX transmit power. The GSM1900
frequency band in the USA consists of channel numbers 512 to 810. The band
has been further divided into six sub-blocks A, B, C, D, E, F, blocks A to
C being 15 MHz bands and D to F being 5 MHz bands. The FCC, the local regulator
in the USA, has set certain emission limits for GSM1900 equipment to ensure
that an operator on a band does not interfere another operator on the adjacent
bands. The edge channel between two adjacent blocks must not be used at all.
Two more channels next to the edge channel may not be used on the maximum
transmit power. The result is that there are three channels between each two
adjacent sub-bands that cannot be used freely. Also the extreme edges of the
GSM1900 band, that is, channels 512 and 810 belong to the low power category.
The BSS has the responsibility to control the EDGE channel emission limits.</p>
</div>
</body>
</html>