www.netlab.nec.de

About Us NWRD SSWRD Projects Jobs



INTERMON
Advanced architecture for INTER-domain quality of service MONitoring, modelling and visualisation
About the Project
Type of Project : European Commission "Information Society Technologies" (IST) 5th Framework

Partner : Salzburg Research, Advanced Network Center, Salzburg Austria
Telecom Italia Laboratories, Torino, Italy
University of Berne, Berne, Switzerland
University of Dortmund, Dortmund, Germany
Waterford Institute of Technology, Telecommunications, Software & Systems Group, Waterford, Ireland
Fraunhofer Institute for Open Communcation Systems - FOKUS, Berlin, Germany
Siemens Austria, Program and system Engineering PSE / IP Networks, Vienna, Austria
Deutsche Telekom, T-Systems Nova, Berlin, Germany
Telefonica, Research and development, Madrid, Spain
NEC Europe Ltd., Network Laboratories, Heidelberg, Germany
Budapest University of Technology and Economics, Budapest, Hungary
Consorzio Interuniversitaro Nazionale per l'Informatica - CINI, Torino, Italy

Duration : April 2002 until March 2004

Intermon is supported by the EC within its IST programme. The aim of is to develop a novel scalable inter-domain QoS architecture with integrated monitoring, modelling, simulations and visual data mining components that use a common distributed QoS database with policy-controlled data collection. The INTERMON architecture will offer Internet Service Providers (ISPs), access technologies manufacturers, and application users an integrated environment for a wide set of tasks like inter-domain QoS management, volume-based charging, inter-domain traffic engineering, network planning and inter-domain traffic profiling. So far, NEC major contribution to the project is the implementation of a passive flow meter compliant to the protocol.

The INTERMON project is to enhance the inter-domain QoS and traffic analysis in large-scale, multi-domain Internet infrastructures. To this purpose, the INTERMON project defines, designs and implements a scalable architecture to provide both telecom operators and corporate users with a set of services that, in an automated fashion, collect, process and present information about network status (i.e. network topology, traffic and Quality of Service) and SLA fulfilment, in both an intra-domain and an inter-domain scenario. By using visual data mining techniques, INTERMON users can easily and efficiently access the information they need. The core of the INTERMON architecture is a large, distributed information base, which collects data provided by measurement and simulation tools and by analytical models. The main components in the INTERMON architecture are the following:

 
  • The Global Controller (GC), which is unique within a given Autonomous System (AS) and is responsible for the provisioning of monitoring-related services (e.g. SLA monitoring, network planning support, visual data mining, etc.) to the INTERMON users.
  • One or more Local Controllers (LCs) associated to each GC. Within an AS each LC is responsible for a specific portion of the network. Depending on the task, it selects the proper Tool Manager and provides it with the appropriate configuration parameters.
  • Several Tool Managers (TMs), each responsible for controlling a given set of tools of a common type. In particular, Tool Managers translate a task description (provided by a Local Controller) into a tool specific input and can adapt the tool output to the INTERMON database structure.
  • A distributed database for the collection of measurement and simulation results.
  • Monitoring and simulation tools.
 

 

INTERMON architecture
INTERMON architecture
 

 

NEC's Role in INTERMON project
NEC is active in almost all project's work packages and contributed to set the general requirements and to the definition of the INTERMON architecture. The major activities are however related to traffic measurements. In particular, NEC has been active in two IETF Working Groups, namely IP Flow Information eXport (IPFIX ) and Packet Sampling (PSAMP). The former aims at standardizing the export of flow measurements from a measurement point to a collector, while the latter was established to define a standard set of capabilities for network elements to sample subsets of packets. The second major NEC's contribution to the project is the implementation of a flow meter compliant to the IETF IPFIX specification.
 

 

NEC IPFIX passive flow meter
| Top |
The has been established with the goal of standardizing the export of IP flow measurement results from a monitoring station (meter) to a collector, i.e. a recipient of the measurements results. This standardization is necessary to achieve an acceptable level of interoperability among equipment from different vendors (e.g. the meters may be embedded into the routers, and normally a collector will receive messages from more than one meter) and to support the development of generalized flow analysis tools.

Flow level data bring information that is certainly less complete than the one obtainable by packet level measurements; however, it is sufficient for a number of applications, including accounting, network planning, traffic engineering and attack detection. In particular, the last two require processing information in real time, which would be difficult to run directly on large packet traces. A further major benefit offered by flow measurements is that they generate much smaller data sets, therefore achieving a higher scalability, especially relevant in large, heavily used networks.

Within the INTERMON project, NEC developed an IPFIX compliant flow meter, which attempts to address scalability issues, both in terms of number of monitored flows and packet input rate. It consists of two main components, the "meter" itself and the "collector", with the meter sending to the collector messages, at regular configurable intervals, in the format defined in the IPFIX standard. These messages contain flow measurement results.

The IPFIX meter allows measuring the volume of traffic observed for a certain flow from the beginning of the measurements until the time of the last report. IPFIX provides a very flexible flow definition [3], allowing to perform measurements at very different levels of granularity, ranging from the total traffic flowing on a link to the single stream (for instance a single VoIP call).
 

 

IPFIX flow meter
IPFIX flow meter architecture and possible measurement scenario
 

 

Publications
| Top |

F. Raspall, S. Tartarelli, M. Molina and J. Quittek, Implementing an IETF IPFIX traffic meter, First international workshop on Inter-domain performance and simulation,(Extended Abstract), IPS 2003, 20-21 February 2003, Salzburg.

M. Molina, A Scalable and Efficient Methodology for Flow Monitoring in the Internet, Proc. of 18th International Teletraffic Conference, ITC18, 1 August- 5 September, 2003, Berlin, Germany.

M. Molina, S. Tartarelli, F. Raspall and S. Niccolini,
Implementation of an IPFIX compliant flow traffic meter: challenges and performance assessment, Proc. of 2003 IEEE Workshop on IP Operations and Management (IPOM2003), October 1-3 2003, Kansas City, Missouri.

M. Molina, IP Traffic Measurements: Technologies, Tools, and Protocols, tutorial at 2003 IEEE Workshop on IP Operations and Management (IPOM2003), October 1-3 2003, Kansas City, Missouri.

S. Niccolini, M. Molina, F. Raspall and S. Tartarelli, Design and implementation of a One Way Delay passive measurement system, Proc. of 9th IEEE/IFIP Network Operations and Management Symposium (NOMS 2004), 19-23 April 2004, Seoul, Korea.

S. Felis , J. Quittek and L. Eggert, Measurement-Based Wireless LAN Troubleshooting, Proc. of 1st workshop on Wireless Network Measurements , 3 April 2005, Riva del Garda, Trentino, Italy.

J. Quittek and B.Claise, On the Relationship between PSAMP and IPFIX, February 2003, draft-quittek-psamp-ipfix-01.txt .

J. Quittek, T. Zseby, B. Claise and S. Zander, Requirements for IP Flow Information Export (IPFIX), RFC 3917, October 2004.

 

Contact

For more information please use our .

Offical webpage.

 

Last modified 01-Sep-2010