<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>BSC Software 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:dn0446143:1:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-21T16:15:28Z"?>
<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:dn0446143:1:en:global:publishing_online_1_0:data:data:35:*:*" date="2005-02-21T16:15:28Z"?>
</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="jan18510153023" 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=dn0446143_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=dn0446143_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>BSC Software Configuration Management</h1>

<p>By means of the BSC Software Configuration Management,
the operator can deploy a new software package in the BSC, update an existing
package, test new software before its deployment, and safe-copy the software
of the BSC. These functions make it possible to load, test, and deploy totally
new software or a specified part of it, under controlled conditions in the
BSC.</p>


<p>The BSC can maintain several software packages on its system
disk at the same time. A sufficient maximum configuration for everyday needs
is three packages. Various packages may contain common software components.
The master files of different packages may thus contain common records. It
is therefore possible to make use of the old package simply by introducing
only those software components that have changed. It is also possible to make
a safe-copy of the package in operation, compare two software packages of
different levels, and examine the change history of the packages. Safe copying
can be made for the whole package or for the data files only.</p>


<p>The biggest software change is one where all the software
components of a package are changed, and the smallest is one where only one
component is changed. Software configuration management supports both of these
cases as well as all cases there between. Conversion programs serve to retain
the semi-permanent data (file contents) even though its format may change
in the new package. Big software changes can be employed safely through a
trial configuration.</p>


<p>A trial configuration is a functional division of the BSC
into two parts, accomplished with package management commands, in which there
is a traffic-transmitting part (traffic side) and a software-testing part
(trial side). The parts are invisible to each other and can have different
software packages. The traffic side handles the traffic with old software
while the new package can be tested on the trial side without disturbing traffic.</p>


<a name="mar1141727110" shape="rect"></a>
<div class="topic">
<h2>Automatic
return to old package</h2>

<p>It is required that a BSC software package can be changed
and activated remotely from the NetAct. This feature enhances the functionality
of the remote BSC software updating.</p>


<p>To be sure that the BSC and its remote connections start
working correctly after the package deployment, this feature provides an automatic
return to the old package if the remote connection fails or if other severe
malfunction occurs in the BSC's Operation and Maintenance Unit preventing
the operator from remote operations.</p>


<p>Two different return conditions can be given to the BSC:</p>


<ul>
<li><p>A return to back-up package allowed</p>
</li>
<li><p>A return to fallback package allowed.</p>
</li>
</ul>


<p>Two modes of automatic return can be used:</p>


<ul>
<li><p>An immediate return in case of the
Operation and Maintenance Unit will not start up</p>
</li>
<li><p>A timed return to the old package if
the remote connection does not begin to work.</p>
</li>
</ul>


<p>With the enhancement 'Installing Multiple Change Deliveries'
it is possible to install more than one CD before creating a correction package.
It is particularly useful when making a BSC software upgrade or when commissioning
a BSC for the first time as in these cases we usually have to install many
CDs at the same time.</p>


<p>The enhancement 'Improved Local Back-up' introduces a one-command
safe copy. The Back-up Application takes care of the whole procedure: the
preparatory actions, copying, and the finishing actions. Command calendar
files for remote safe copying is no more needed. Another enhancement is that
an archive back-up can be taken also after change deliveries have been installed,
which was previously practically impossible.</p>
</div>
</div>
</body>
</html>