Service Communautaire d'Information sur la Recherche et le Développement - CORDIS

FP5

MOBY DICK Résumé de rapport

Project ID: IST-2000-25394
Financé au titre de: FP5-IST

New architecture for mobile operators based on IPv6

The Moby Dick architecture successfully integrated Mobility, QoS and AAA towards an IP dominated mobile Internet platform. The key result of the project is that Mobile IPv6 with the slight extensions as proposed in Moby Dick is able to provide QoA-aware and AAA-supported seamless mobility on heterogeneous network architecture.

The Moby Dick architecture clearly showed that the Internet can become a mobile network which goes beyond the support for nomadic use only, as currently supported by WLAN/Mobile IP technologies. Inter-technology handover can be supported easily and though the profile concept of Moby Dick users can be de-coupled from end systems and user mobility concepts can be introduced into such a network without severe problems.

A further result is that seamless mobility between administrative domains is still an open issue and was not the key focus of Moby Dick for the following reason:
Moby Dick provides a network architecture, which provides technical solutions to technical problems. The inter-domain scenario is rather an economical and contractual problem than a technical problem. Here the relation and in turn the business models describing the relationship between two operators are the more critical path and so, this topic is out of the scope of Moby Dick.

Further open issues so far are, if the mobile operators really allow the Internet to become mobile and seamlessly available since the Internet lacks of a business model and so there exists no concept how to really earn money. So the Moby Dick consortium can handover this successor-problem to the economists in order to get feedback about the level of openness this infrastructure can stand in order to generate the revenue required.

A further, very important aspect is the missing concept describing the relationship between the network operator and a third party operator creating a service to be consumed by the user. This relationship could bring new requirements to the AAA part of the Moby Dick architecture which has nod been considered so far.

More information on the Moby Dick project can be found at:
http://www.ist-mobydick.org/

Reported by

UNIVERSITAET STUTTGART