Moby Dick Consolidated System Integration Plan

D0103v1.doc Version 1 6.7.2003
1 Introduction
This deliverable describes the first version of the architecture of the Moby Dick network infrastructure.
The goal is to provide QoS-enabled and AAA supported mobility on a heterogeneous network
infrastructure. So Moby Dick merges mechanisms of three different research areas namely QoS, AAA,
and Mobility management. This document should be regarded as baseline document throughout the whole
duration of the project. Moby Dick targets a generic architecture supporting all kind of layer 2 access
technology, however, the architectural considerations are restricted to Ethernet, Wireless LAN, and TD-
CDMA technologies. Since the integration process of QoS, Mobility, and AAA issues to provide a M-
commerce capable all-IP based wireless Internet infrastructure is quite complex it is quite supposable that
the first trial of the architecture specification does not require further iteration processes towards an open,
stable, and scalable platform for “3.5 G and beyond” based access networks.
The big challenge within the architecture is to find an ideal mixture of QoS, Mobility, and AAA elements,
mechanisms and functions which approach as far as possible to the optimised Moby Dick architecture.
The definition of the Moby Dick architecture can be regarded as an optimisation problem since each of
the three major research areas has already solutions for various problems, however, it is clear that first,
the combination of these individual mechanisms can not be achieved from a technical point of view
boundlessly and second, mechanisms and elements of one research area may have a negative impact on
the mechanisms and elements of the other research area. For this reason, the Moby Dick architecture will
be a best practice compromise between mechanisms, requirements, and solutions from the abovementioned
three research areas.
The structure of the document is as follows:
Chapter 2 starts with an overall motivation for the project Moby Dick. Here the authors would like to
summarise again the motivation for the overall project.
Since Moby Dick is targeting a “3,5 G and beyond” wireless network infrastructure assumptions and
requirements based on selected usage scenarios are required to have a realistic input to the architecture
definition. Chapter 3 describes the key architecture from a more generic and conceptual user point of
view. Chapter 4 points the detailed software architecture of the key modules and components developed
within the project. Chapter 5 describes how these detailed modules are mapped first into a functional
architecture by a detailed specification of the interaction flow between these components. In chapter 6, a
conclusion is given.
The overall structure of the project has the following nature: WP1 does define the overall Moby Dick
architecture. WP2, WP3, and WP4 are the so-called implementation workpackages. Here QoS issues
(WP2), Mobility related issues (WP3) and AAAC related issues (WP4) are specified based on the overall
architecture on a more detailed level. Since almost each component contains modules from each
implementation workpackage, this horizontal interface contains major input from all workpackages. In
the current project year all implementation workpackages officially provided an additional deliverable,
this document contains some redundant information since it is of course reported in the Deliverables of
the implementation workpackages. However, in order to increase the overall readability of this document,
this overlap intended. So the reader of this document should get a clear view of the modules and
components the project developed, specified and brought into the evaluation by means of the Moby Dick
field trial. Theoretical aspects with our close relevance to the implementation are kept outside.
D0103v1.doc 9 / 168