<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="client.xsl" type="text/xsl"?>
<article article-type="other">
<doi>MS-04-133-cd</doi>

<front><journal-meta>
<journal-id/>
<issn/>
<banner>
<href>banner.jpg</href>
<size width="100%"/>
</banner>
</journal-meta>
<article-meta>
<title-group>
<article-title>Computing Characteristics for the Availability of Paths and its Application to a Communication Network </article-title>
</title-group>

<author>H.Sch&#228;be<sup>1</sup>, and S. Gr&#252;ter<sup>2</sup></author>

<aff><sup>1</sup>T&#220;V Rheinland InterTraffic GmbH, Cologne, Germany. </aff>

<aff><sup>2</sup>DB Netz AG, Frankfurt, Germany. </aff>

</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>Computing the availability of entire networks can be cumbersome, since in practice networks are large. The availability of the entire network does not provide much information, since mostly certain paths in the network are used. In our research, we consider a communication network. The system is modelled by an undirected graph. Each vertex can fail, it is repaired upon failure and it is characterized by its mean time between failures and its mean down time. For a path in the network, connecting two arbitrary nodes, the availability, the mean time between failures, and also the mean down time of the path can be computed. For the mean down time, an approximate formula is given. Using theoretical data, a prediction for the availability characteristics for paths can be given. In the example studied, theoretically computed characteristics for paths are compared with observed data. The research has shown, how availability of network components can be verified based on data for paths in the network, rather than using data for components. The latter is sometimes complicated since many components in a network only rarely fail and statistical data are hard to obtain and as a consequence, computed characteristics have very large confidence bound.</p><p> <italic> Keywords:</italic>availability, mean down time, network, paths. </p></abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>MS-04-133</hpdf>

</fpdf>
</body>
</article>
