<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Standard Measurements</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:dn0448208:1:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-28T15:54:00Z"?>
<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:dn0448208:1:en:global:publishing_online_1_0:data:data:37:*:*" date="2005-02-28T15:54:00Z"?>
</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="jan1851334103" 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=dn0448208_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=dn0448208_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>Standard Measurements</h1>

<p>In order to run the network effectively, that is, to minimise
costs and maximise the service quality to the subscriber, the operator needs
to know certain characteristics about the performance and the service level
of the BSC and radio network. Such characteristics are, for example, traffic
carried by different cells, congestion on the SDCCH or TCH channels as well
as successful and failed handovers. Traffic measurements provide the required
basic information. Standard measurements also include specific counters for
some features, for example, the HSCSD.</p>


<p>By analysing the information, the operator can find out
if, for example, there are load distribution problems, that is, both heavily
and lightly loaded parts in the system. In that case the operator can make
redimensioning in order to balance the network to improve the performance.
Observing certain traffic characteristics over a period of time enables the
operator to forecast the time when new resources or extensions must be introduced
to the network. The measurements are grouped together to allow better functionality
and handling. This provides the user easier selection of certain measurements
necessary at a particular time. All measurements are independent of each other
but the same user interface is used for handling all measurements.</p>


<p>The measurements include the following:</p>


<a name="mar154171161" shape="rect"></a>
<div class="topic">
<h2>Traffic
Measurements Per Cell (Traffic)</h2>

<p>Traffic measurement includes SDCCH and TCH counters, for
example, seizure attempts, successful seizures, and success TCH seizure for
assignment complete. Also forced release, forced handover and queue counters
belong to traffic measurement. The total number of traffic measurement counters
is over hundred.</p>
</div>


<a name="mar154171462" shape="rect"></a>
<div class="topic">
<h2>Resource
Availability Measurements Per Cell (Res_Avail)</h2>

<p>The radio resource availability measurement results contain
the following information:</p>


<ul>
<li><p>The availability of TCHs and SDCCHs</p>
</li>
<li><p>The availability of TCHs per interference
band</p>
</li>
<li><p>Time congestion of TCH and SDCCH</p>
</li>
<li><p>The average and peak number of busy
TCHs (Erlang counter) or SDCCHs</p>
</li>
<li><p>Average holding times of TCH and SDCCH.</p>
</li>
</ul>
</div>


<a name="mar154173193" shape="rect"></a>
<div class="topic">
<h2>Resource
Availability Measurements Per BSC (Avail_Bsc)</h2>

<p>The counter values give average information within a measurement
period. The counters are:</p>


<ol class="type-odd">
<li type="1"><p>Average number of unavailable TRXs
due to user actions</p>


<p>The sampled counter is updated when</p>


<ul>
<li><p>TRX is unblocked</p>
</li>
<li><p>TRX is blocked.</p>
</li>
</ul>
</li>
<li type="1"><p>Average number of unavailable TRXs
due to BSS internal reasons</p>


<p>The sampled counter is updated when</p>


<ul>
<li><p>TRX is unblocked</p>
</li>
<li><p>TRX is blocked.</p>
</li>
</ul>
</li>
<li type="1"><p>Average number of unavailable TRXs
due to BSS external reasons</p>


<p>The sampled counter is updated when</p>


<ul>
<li><p>TRX is unblocked</p>
</li>
<li><p>TRX is blocked.</p>
</li>
</ul>
</li>
</ol>
</div>


<a name="mar154177304" shape="rect"></a>
<div class="topic">
<h2>Resource
Access Measurements Per CCCH (Ccch_Acc)</h2>

<p>The resource access measurement results contain the following
information:</p>


<ul>
<li><p>The number of messages per type of
message sent via Abis</p>
</li>
<li><p>The average load on control channels</p>
</li>
<li><p>The number of seizures for originated
and terminated calls</p>
</li>
<li><p>IMSI detach on SDCCH</p>
</li>
<li><p>IMSI detach on TCH in FACCH call set-up
due to SDCCH congestion.</p>
</li>
</ul>


<p>The measurement collects information on the basis of common
control channels.</p>
</div>


<a name="mar154179135" shape="rect"></a>
<div class="topic">
<h2>Handover
Measurement Per Cell (Ho)</h2>

<p>The handover measurement results contain the following
information:</p>


<ul>
<li><p>MSC/BSC-controlled incoming handovers
succeeded/failed</p>
</li>
<li><p>MSC/BSC-controlled outgoing handovers
succeeded/failed</p>
</li>
<li><p>Intracellular cell handovers succeeded/failed</p>
</li>
<li><p>Handovers according to cause.</p>
</li>
<li><p>Call dropped during external handover
after ho command received from the MSC</p>
</li>
<li><p>Call possibly dropped during external
handover after ho request ack sent to the MSC.</p>
</li>
</ul>
</div>


<a name="mar1541711126" shape="rect"></a>
<div class="topic">
<h2>Power
Control Measurement Per Cell (Power)</h2>

<p>The power control measurement results contain the following
information:</p>


<ul>
<li><p>The number of power control messages
sent to the MS and TRX</p>
</li>
<li><p>The average power of the MS and TRX</p>
</li>
<li><p>The average Rx quality of the MS and
TRX</p>
</li>
<li><p>The average Rx level of the MS and
TRX</p>
</li>
<li><p>The average uplink interference level
on idle channels.</p>
</li>
</ul>


<p>Statistics are compiled in counters reserved for each TRX
of BSS cells. </p>
</div>


<a name="mar1541712297" shape="rect"></a>
<div class="topic">
<h2>OSI/X.25
Measurements  (OSI)</h2>

<p>The OSI measurement results consist of four main parts:</p>


<ul>
<li><p>The results of OSI level 1 (physical
layer)</p>
</li>
<li><p>The results of OSI level 2 (data link
layer)</p>
</li>
<li><p>The results of OSI level 3 (network
layer)</p>
</li>
<li><p>The results of OSI level 4 (transport
layer).</p>
</li>
</ul>


<p>The measurement collects information concerning all OSI
channels belonging to the BSC.</p>
</div>


<a name="mar1541714258" shape="rect"></a>
<div class="topic">
<h2>Field
Reporting (Avail)</h2>

<p>The availability measurement results contain the following
information:</p>


<ul>
<li><p>The number of restarts of a unit</p>
</li>
<li><p>The number of software process restarts
of a unit</p>
</li>
<li><p>The number of pre-processor restarts
of a unit</p>
</li>
<li><p>The duration of disconnection of a
unit.</p>
</li>
</ul>
</div>


<a name="mar1541715379" shape="rect"></a>
<div class="topic">
<h2>Load
Measurement (Load)</h2>

<p>The load measurement results contain for example:</p>


<ul>
<li><p>The peak value of processor load rate</p>
</li>
<li><p>The average value of processor load
rate.</p>
</li>
</ul>


<p>The measurement collects information concerning all computer
units belonging to the BSC.</p>
</div>


<a name="mar15417171710" shape="rect"></a>
<div class="topic">
<h2>BSC
Clear Codes Per Call Phase Per BSC (BSC_CC)</h2>

<p>The call is divided into 15 different phases.</p>


<ul>
<li><p>Paging/initial ms (ccch and sdcch or
tch)</p>
</li>
<li><p>Mm-signalling (sdcch or tch)</p>
</li>
<li><p>Basic assignment (sdcch and tch)</p>
</li>
<li><p>Release (sdcch or tch)</p>
</li>
<li><p>Facch assignment (tch)</p>
</li>
<li><p>Sms-establishment (tch)</p>
</li>
<li><p>Gms-establishment (sdcch)</p>
</li>
<li><p>Ciphering (sdcch or tch)</p>
</li>
<li><p>External handover (sdcch or tch, source)</p>
</li>
<li><p>Internal handover intra (sdcch or tch,
source)</p>
</li>
<li><p>External handover (sdcch or tch, target)</p>
</li>
<li><p>Internal handover inter (sdcch or tch,
source)</p>
</li>
<li><p>Internal handover intra (sdcch or tch,
target)</p>
</li>
<li><p>Internal handover inter (sdcch or tch,
target)</p>
</li>
<li><p>Conversation (tch).</p>
</li>
</ul>


<p>The BSC Clear Code measurement provides all failure and
success causes that lead to a channel release in different call phases.</p>
</div>


<a name="mar15417205611" shape="rect"></a>
<div class="topic">
<h2>BSC
Clear Codes, PM Counters Per BSC (CC_PM)</h2>

<p>The BSC clear codes PM counters are divided into five different
classes:</p>


<ul>
<li><p>Failure counters	</p>
</li>
<li><p>Success counters	</p>
</li>
<li><p>BCSU counters	</p>
</li>
<li><p>Call establishment cause counters	</p>
</li>
<li><p>Handover counters</p>
</li>
</ul>


<p>These counters provide general information about different
channel reservations at BSC level.</p>


<p>Three new dx - causes are added (counters for these dx-causes
are added in the BSC clear code (PM) measurement):</p>


<ol class="type-odd">
<li type="1"><p>Attempt IMSI detach</p>


<p>This is incremented when the IMSI detach is started.</p>
</li>
<li type="1"><p>Basic IMSI detach</p>


<p>This is incremented when the IMSI detach is done successfully
on an SDCCH channel.</p>
</li>
<li type="1"><p>FACCH IMSI detach</p>


<p>This is incremented when the IMSI detach is done successfully
on a TCH channel.</p>
</li>
</ol>
</div>


<a name="mar15417235712" shape="rect"></a>
<div class="topic">
<h2>BSC
Clear Codes, Service Level Counters Per Cell (CC_SERLEV)</h2>

<p>The BSC clear codes, Service Level counters are divided
into two different classes.</p>


<p> Failure counters:</p>


<p>These counters are updated after a service level has occurred.
The counters are sum counters of different fatal failures that can cause call
clearing.</p>


<ul>
<li><p>Call set-up failure</p>
</li>
<li><p>External handover target failure</p>
</li>
<li><p>Internal inter handover target failure</p>
</li>
<li><p>Internal intra handover target failure</p>
</li>
<li><p>External handover source failure</p>
</li>
<li><p>Internal inter handover source failure</p>
</li>
<li><p>Internal intra handover source failure</p>
</li>
<li><p>Dropped call </p>
</li>
<li><p>TCH failure.</p>
</li>
</ul>


<p>Success counters:</p>


<p>The counters for successful signalling</p>


<ul>
<li><p>External handover target successful</p>
</li>
<li><p>External handover source successful</p>
</li>
<li><p>Call successful</p>
</li>
<li><p>Internal inter handover successful</p>
</li>
<li><p>Internal intra handover successful </p>
</li>
<li><p>Set-up successful</p>
</li>
<li><p>Conversation started</p>
</li>
<li><p>TCH seizures.</p>
</li>
</ul>


<p>The failure and the success counters together characterise
the quality of service in the BTS level, new call success factors are added:</p>


<ul>
<li><p>Congestion related SDCCH access probability</p>
</li>
<li><p>Activation related SDCCH access probability</p>
</li>
<li><p>SDCCH call success ratio</p>
</li>
<li><p>Congestion related TCH access probability</p>
</li>
<li><p>Activation related TCH access probability</p>
</li>
<li><p>TCH success ratio.</p>
</li>
</ul>
</div>


<a name="mar15417295713" shape="rect"></a>
<div class="topic">
<h2>Transmission
measurements</h2>

<p>The transmission measurements collect the signal quality
counters of the interfaces of the Nokia transmission equipment.</p>


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


<p>The counters are based on the G.821 or G.826 recommendation.
The BSC collects the counters either through BSCs Q1 channels, or if the equipment
is connected to the BTS’s Q1 bus, through the OMUSIG. There are three different
transmission measurements:</p>


<ul>
<li><p>TRU (Transmission Unit, TRUA and TRUB)</p>
</li>
<li><p>DN2 (n * 2Mbit/s Dynamic Node)</p>
</li>
<li><p>DMR (Digital Microwave Radios, Nokia
DMR18-38, DMR2000 and DMR7000).</p>
</li>
</ul>


<p>The signal quality counters are:</p>


<ul>
<li><p>Total time</p>
</li>
<li><p>Available time</p>
</li>
<li><p>Errored seconds</p>
</li>
<li><p>Severely errored seconds</p>
</li>
<li><p>Degraded minutes.</p>
</li>
</ul>


<p>MIN and MAX incoming RF levels are also included to the
DMR measurement.</p>


<p>In many cases, it is possible to predict the faults appearing
in the PCM interfaces days in advance, based on an increasing number of short
disturbances.</p>


<p>BSC and TCSM2 Exchange Terminal plug-in units measure the
performance of the interfaces permanently in 24-hour periods. The measurement
reports of the BSC ETs are printed out locally at midnight. Both BSC and TCSM2
ET reports can be seen with the MMI commands. The following is an example
of the BSC print out of the error counters:</p>


<a name="mar15417333814" shape="rect"></a>
<div>
<p>Table: An example of the BSC print out of the error counters</p>


<table border="1">
<tbody>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="6" rowspan="1"><p>DISTURBANCES:</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>DISTTYPE</p>
</td>
<td align="center" colspan="5" rowspan="1"><p>COUNTER LIMITS (ms)</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>10-50</p>
</td>
<td colspan="1" rowspan="1"><p>50-200</p>
</td>
<td colspan="1" rowspan="1"><p>200-1000</p>
</td>
<td align="center" colspan="2" rowspan="1"><p>1000-</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>NOINSGN</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>1</p>
</td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>2</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p>FALOST</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>0</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>AIS</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>0</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>REMOTE</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>2</p>
</td>
<td colspan="1" rowspan="1"><p>0</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></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="6" rowspan="1"><p>FRAME ALIGNMENT SIGNAL ERRORS:</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="5" rowspan="1"><p>COUNTER LIMITS (ERRORS/5 SEC)</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>1-39</p>
</td>
<td colspan="1" rowspan="1"><p>40-79</p>
</td>
<td colspan="1" rowspan="1"><p>80-159</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>160-</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>10</p>
</td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="6" rowspan="1"><p>SLIPS:</p>
</td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="2" rowspan="1"><p>POSITIVE</p>
</td>
<td colspan="2" rowspan="1"><p>NEGATIVE</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
</tr>
<tr align="left" char="" charoff="50" valign="top">
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p></p>


 </td>
<td colspan="1" rowspan="1"><p>0</p>
</td>
<td colspan="1" rowspan="1"><p></p>


 </td>
</tr>
</tbody>
</table>
</div>
</div>


<a name="mar15417422916" shape="rect"></a>
<div class="topic">
<h2>Nokia
MetroSite, UltraSite, and Nokia GSM Office Transmission Equipment Statistics</h2>

<p>Transmission Equipment Statistics offers information on
the signal quality of the Transmission system. The Nokia MetroSite Microcellular
solutions allow greater number of base stations and related transmission equipment,
and the same is done for the Nokia UltraSite EDGE BTS and Nokia GSM Office.
 In practice, this means a large set of counters, and thus the operator has
the possibility to measure the transmission equipment in two ways:</p>


<ol class="type-odd">
<li type="1"><p>First, all equipment can be measured
with a 24-hour period. This measurement gives fixed set of counters, which
are near-end G.826 signal quality counters:</p>


<ul>
<li><p>Total time</p>
</li>
<li><p>Available time</p>
</li>
<li><p>Errored seconds</p>
</li>
<li><p>Severely errored seconds</p>
</li>
<li><p>Background block errors</p>
</li>
<li><p>Errored block.</p>
</li>
</ul>
</li>
<li type="1"><p>Second, a certain set of transmission
equipment can be defined. The measurement interval can be 15, 30 minutes,
1,2,3, or 24 hours. Transmission equipment refers to either the whole equipment
or part of it (functional entity and supervision block). It is also possible
to define the counters that will be collected from the equipment. To be able
to do this operator has to know the topology of the transmission network so
that he is able to choose the measurement subject.</p>
</li>
</ol>
</div>
</div>
</body>
</html>