<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ep-patent-document PUBLIC "-//EPO//EP PATENT DOCUMENT 1.0//EN" "ep-patent-document-v1-0.dtd">
<ep-patent-document id="EP04255422A1" file="04255422.xml" lang="en" country="EP" doc-number="1633080" kind="A1" date-publ="20060308" status="n" dtd-version="ep-patent-document-v1-0">
<SDOBI lang="en"><B000><eptags><B001EP>ATBECHDEDKESFRGBGRITLILUNLSEMCPTIESILTLVFIROMKCYALTRBGCZEEHUPLSK..HR............</B001EP><B005EP>J</B005EP><B007EP>DIM360 (Ver 1.5  21 Nov 2005) -  1100000/0</B007EP></eptags></B000><B100><B110>1633080</B110><B120><B121>EUROPEAN PATENT APPLICATION</B121></B120><B130>A1</B130><B140><date>20060308</date></B140><B190>EP</B190></B100><B200><B210>04255422.0</B210><B220><date>20040907</date></B220><B250>en</B250><B251EP>en</B251EP><B260>en</B260></B200><B400><B405><date>20060308</date><bnum>200610</bnum></B405><B430><date>20060308</date><bnum>200610</bnum></B430></B400><B500><B510EP><classification-ipcr sequence="1"><text>H04L  12/24        20060101AFI20050207BHEP        </text></classification-ipcr></B510EP><B540><B541>de</B541><B542>Schnittstelle für ein Netzverwaltungssystem</B542><B541>en</B541><B542>An interface for a network management system</B542><B541>fr</B541><B542>Interface pour un systéme de gestion de réseau</B542></B540><B590><B598>2</B598></B590></B500><B700><B710><B711><snm>SIEMENS AKTIENGESELLSCHAFT</snm><iid>00200520</iid><irf>2004P08441EP</irf><adr><str>Wittelsbacherplatz 2</str><city>80333 München</city><ctry>DE</ctry></adr></B711></B710><B720><B721><snm>Pereira, Goncalo</snm><adr><str>Av. Alexandre Salles, 14 9E</str><city>Amadora</city><ctry>PT</ctry></adr></B721><B721><snm>Pessoa, Pedro</snm><adr><str>Av. Eng. Arantes e Oliveira, 25, 3C</str><city>Lisboa</city><ctry>PT</ctry></adr></B721></B720><B740><B741><snm>Morgan, Marc</snm><sfx>et al</sfx><iid>00074607</iid><adr><str>Siemens Shared Services, 
c/o Siemens AG, 
Postfach 22 16 34</str><city>80506 Munich</city><ctry>DE</ctry></adr></B741></B740></B700><B800><B840><ctry>AT</ctry><ctry>BE</ctry><ctry>BG</ctry><ctry>CH</ctry><ctry>CY</ctry><ctry>CZ</ctry><ctry>DE</ctry><ctry>DK</ctry><ctry>EE</ctry><ctry>ES</ctry><ctry>FI</ctry><ctry>FR</ctry><ctry>GB</ctry><ctry>GR</ctry><ctry>HU</ctry><ctry>IE</ctry><ctry>IT</ctry><ctry>LI</ctry><ctry>LU</ctry><ctry>MC</ctry><ctry>NL</ctry><ctry>PL</ctry><ctry>PT</ctry><ctry>RO</ctry><ctry>SE</ctry><ctry>SI</ctry><ctry>SK</ctry><ctry>TR</ctry></B840><B844EP><B845EP><ctry>AL</ctry></B845EP><B845EP><ctry>HR</ctry></B845EP><B845EP><ctry>LT</ctry></B845EP><B845EP><ctry>LV</ctry></B845EP><B845EP><ctry>MK</ctry></B845EP></B844EP></B800></SDOBI>
<abstract id="abst" lang="en">
<p id="pa01" num="0001">An interface (3) includes a hash function (5) for storing fields of network element alarms which cannot be processed by a network management system (4) into fields that can be processed.
<img id="iaf01" file="imgaf001.tif" wi="165" he="77" img-content="drawing" img-format="tif"/></p>
</abstract><!-- EPO <DP n="1"> -->
<description id="desc" lang="en">
<p id="p0001" num="0001">This invention relates to an interface for network management system, in a communications network.</p>
<p id="p0002" num="0002">Communications networks are built from network elements. Examples of such elements include switches, multiplexers, modems or other basic units of a network.</p>
<p id="p0003" num="0003">The elements of the network may experience faults, high loading, low loading conditions which may require an intervention in the way the network is configured. For example, if a router develops a fault or is overloaded, traffic may be re-routed to avoid that router. In order to cater for this, network elements issue alarms to a network manager system (NMS).</p>
<p id="p0004" num="0004">The NMS is a computer implemented device which receives alarms and initiates remedial action such as re-configuring the network to re-route traffic.</p>
<p id="p0005" num="0005">The NMS are designed to operate within a standard and thus can cater only for a set of alarms with limited accompanying information of fixed length.</p>
<p id="p0006" num="0006">The network elements or an intermediary system called an Element Management System can produce alarms with more information than is permitted or acceptable to the NMS.</p>
<p id="p0007" num="0007">According to the invention there is provided an interface for a network management system to provide thereto compatible network element alarms which interface comprising an input for accepting incoming alarms generated by network elements and a hashing processor for applying a hash function to the incoming alarms to produce hashed alarms output to the network management system.<!-- EPO <DP n="2"> --></p>
<p id="p0008" num="0008">A hashing function in one which take an arbitrary amount of information and reduces it to a fixed number of bits. Thus, by use of the invention alarms generated by network elements having an arbitrary amount of information are converted into alarms of a fixed bit length conforming to the requirements of the network management system.</p>
<p id="p0009" num="0009">In the preferred embodiment the hashing function is one known as MD5.</p>
<p id="p0010" num="0010">A specific embodiment of the invention will now be described, by way of example only, with reference to the drawing in which:
<ul id="ul0001" list-style="none" compact="compact">
<li>Figure 1 shows in schematic form an interface in accordance with the invention used in a communications network; and</li>
<li>Figure 2 is an explanatory diagram.</li>
</ul></p>
<p id="p0011" num="0011">With reference to figure 1, a communications system 1 comprises a network 2 including a large number of network elements 4. Alarms from the network elements 4 are coupled by an interface 3 to a network management system 4 (NMS).</p>
<p id="p0012" num="0012">The interface 3 is a suitably programmed computer including a hashing processor 5. The hashing processor 4 applies a hashing function to the incoming alarms. The hashed alarms are then output to the NMS 4.</p>
<p id="p0013" num="0013">The hashing function used is MD5.</p>
<p id="p0014" num="0014">The hashing function produces a digest from the incoming alarms of those fields of the alarm which cannot be directly processed by the NMS 4. This digest is input into a field which can be processed by the NMS 4. This is depicted in figure 2. It will be seen that the data in fields F1 to F4 is taken by the hash function and input into field F2 of the output alarm.</p>
</description><!-- EPO <DP n="3"> -->
<claims id="claims01" lang="en">
<claim id="c-en-0001" num="0001">
<claim-text>An interface for a network management system to provide compatible alarms thereto derived from alarms generated by network elements which interface comprising an input for accepting incoming alarms generated by network elements, a hashing processor for applying a hash function to the incoming alarms to produce hashed alarms and an output for coupling the hashed alarms to the network management system.</claim-text></claim>
<claim id="c-en-0002" num="0002">
<claim-text>An interface as claimed in claim 1 wherein the hashing function is an MD5 function.</claim-text></claim>
<claim id="c-en-0003" num="0003">
<claim-text>A communications system comprising a network of network elements, a network management system and an interface as claimed in claims 1 or 2.</claim-text></claim>
</claims><!-- EPO <DP n="4"> -->
<drawings id="draw" lang="en">
<figure id="f0001" num=""><img id="if0001" file="imgf0001.tif" wi="165" he="162" img-content="drawing" img-format="tif"/></figure>
</drawings>
<search-report-data id="srep" lang="en" srep-office="EP" date-produced=""><doc-page id="srep0001" file="srep0001.tif" wi="155" he="233" type="tif"/><doc-page id="srep0002" file="srep0002.tif" wi="157" he="233" type="tif"/></search-report-data>
</ep-patent-document>
