<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>GSM Trace</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:dn0446537:1:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-28T16:10:36Z"?>
<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:dn0446537:1:en:global:publishing_online_1_0:data:data:36:*:*" date="2005-02-28T16:10:36Z"?>
</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="jan18510343454" 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=dn0446537_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=dn0446537_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>GSM Trace</h1>

<p>The aim of tracing is to start a log of all or some events
happening during a certain period of time. This is particularly useful when
subscriber (IMSI) observations are needed, for example, the mobile station
is suspected to be faulty.</p>


<p>The trace facility is a useful aid in maintenance. It is
also a development tool that can be used during system testing etc. In particular,
it may be used in conjunction with test-MSs to ascertain the digital cell
‘footprint’, network integrity, and also the network QoS as perceived by the
PLMN customer.</p>


<p>The trace facility enables the NM to trace activities of
IMSIs that result in events occurring in the PLMN. This facility also enables
the tracing of all the information, that is available within, or accessible
by the PLMN, on the call path used by the associated MS, that is, the BER
of the radio uplink and downlink, the identity of originating, and terminating
equipment of the mobile or fixed subscriber, the identity of incoming and
outgoing circuits in the nodes involved.</p>


<p>The route information facility is a useful maintenance
aid. It enables network management to trace the actual hardware route of a
call. Information from trace and observation reports can be used to solve
suspected hardware problems within a BSC.</p>


<p>The trace report has additional HW information called Route
Trace Data. The information includes:</p>


<ul>
<li><p>A-if ET-PCM, ET-TSL and ET-SUB-TSL</p>
</li>
<li><p>Abis ET-PCM, ET-TSL and ET-SUB-TSL</p>
</li>
<li><p>SPC, CIC, Transcoder PCM and TSL</p>
</li>
<li><p>Group switch type and BCSU id.</p>
</li>
</ul>


<p>There are several new fields in the GSM ph2 trace invocation
message over the A interface ('MSC invoke trace') of which the following actions
will be implemented:</p>


<ul>
<li><p><em>Priority output</em>:
If the MSC orders the BSC to use priority output for trace reports, the BSC
sends tracing data as Q3 events immediately to the NetAct.</p>
</li>
<li><p><em>Normal output</em>:
tracing data goes to performance data files.</p>
</li>
<li><p>Events <em>including/excluding
radio measurements</em>: the BSC includes or excludes radio measurements
in tracing reports.</p>
</li>
</ul>
</div>
</body>
</html>