27.03.2014 Views

Evaluation, Recommendations and Final Project Report

Evaluation, Recommendations and Final Project Report

Evaluation, Recommendations and Final Project Report

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

IST-2000-25394 <strong>Project</strong> Moby Dick<br />

D0603<br />

<strong>Evaluation</strong>, <strong>Recommendations</strong> <strong>and</strong><br />

<strong>Final</strong> <strong>Project</strong> <strong>Report</strong><br />

Contractual Date of Delivery to the CEC: 31 st January 2004<br />

Actual Date of Delivery to the CEC: February 2004<br />

Author(s):<br />

Partners of the Consortium<br />

Participant(s):<br />

Partners of the Consortium<br />

Work package:<br />

WP6<br />

Security:<br />

Public<br />

Nature:<br />

<strong>Report</strong><br />

Version: 1.0<br />

Total number of pages: 44<br />

Abstract:<br />

This document gives an overview over the full duration of the project <strong>and</strong> the activities taken by the<br />

consortium.<br />

Keyword list:<br />

Moby Dick, Workpackages, Workplan, Summits, Concertation, Dissemination, Self <strong>Evaluation</strong>.


21. Near is thy forgetfulness of all things; <strong>and</strong> near the forgetfulness of thee by all.<br />

23. The universal nature out of the universal substance, as if it were wax, now moulds a horse, <strong>and</strong> when<br />

it has broken this up, it uses the material for a tree, then for a man, then for something else; <strong>and</strong> each of<br />

these things subsists for a very short time. But it is no hardship for the vessel to be broken up, just as there<br />

was none in its being fastened together.<br />

“Book Seven – The Meditations”<br />

By Marcus Aurelius<br />

Written 167 A.C.E.<br />

Translated by George Long<br />

Moby Dick WP4 2 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Authors<br />

01 T-Nova<br />

Hans J. Einsiedler Phone: +49 (0)30 – 3497 3518<br />

Fax: +49 (0)30 – 3497 3519<br />

E-mail: hans.einsiedler@t-systems.com<br />

02 NEC<br />

Amardeo Sarma Phone: +49 (0)6221 – 90511 – 44<br />

Fax: +49 (0)6221 – 90511 – 55<br />

E-mail: mobile@ccrle.nec.de<br />

03 UC3M<br />

Jose Ignacio Moreno Phone: +34-916249183<br />

Fax: +34-916248749<br />

E-mail: jmoreno@it.uc3m.es<br />

04 ETHZ<br />

Burkhard Stiller Phone: +41-1-632 7016<br />

Fax: +41-1-632 1035<br />

E-mail: stiller@tik.ee.ethz.ch<br />

05 USTUTT<br />

Jürgen Jähnert Phone: +49 (0)711-685-4273<br />

Fax: +49 (0)711-678-8363<br />

E-mail: jaehnert@rus.uni-stuttgart.de<br />

06 GMD<br />

Davinder Pal Singh Phone: +49 (0)30-3463 7175<br />

Fax: +49-(0)30-3463 8175<br />

E-mail: singh@fokus.fraunhofer.de<br />

07 PTIn<br />

Victor Marques Phone: +351 234 403654<br />

Fax: +351 234 420722<br />

E-mail: victor-m-marques@ptinovacao.pt<br />

08 CRM<br />

Hong-Yon Lach Phone: +33 (0)1 69 35 25 36<br />

Fax: +33 (0)1 69 35 25 01<br />

E-mail: hong-yon.lach@crm.mot.com<br />

09 EURECOM<br />

Michelle Wetterwald Phone: +33 493.00.26.31<br />

Fax: +33 493.00.26.27<br />

E-mail: michelle.wetterwald@eurecom.fr<br />

10 UKR<br />

Piotr Pacyna Phone: +48 12 6345582<br />

Fax: +48 12 6342372<br />

E-mail: pacyna@kt.agh.edu.pl<br />

11 FTW<br />

Peter Reichl Phone: +43-1-505 28 30-31<br />

Fax: +43-1-505 28 30-99<br />

E-mail: reichl@ftw.at<br />

Moby Dick WP6 3 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

12 ICR<br />

Parijat Mishra Phone: +65-68709353<br />

Fax: +65-67795441<br />

E-mail: parijat@i2r.a-star.edu.sg<br />

Moby Dick WP6 4 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Table of Contents<br />

1. OBJECTIVES AND WORKPLAN OF THE PROJECT ............................. 7<br />

1.1 Workpackage WP1 – Architecture <strong>and</strong> Applications..................................................................7<br />

1.2 Workpackage WP2 – Quality of Service.......................................................................................7<br />

1.3 Workpackage WP3 – Mobility.......................................................................................................7<br />

1.4 Workpackage WP4 – Authentication, Authorisation, Accounting <strong>and</strong> Charging ....................7<br />

1.5 Workpackage WP5 – Integration, Validation, <strong>Evaluation</strong>, <strong>and</strong> Trials ......................................8<br />

1.6 Workpackage WP6 – <strong>Project</strong> Management <strong>and</strong> External Liaison.............................................8<br />

2. OVERALL PLAN - DESCRIPTION OF THE WORKPACKAGES............. 8<br />

2.1 Workpackage/Workload Distribution ..........................................................................................8<br />

2.2 Planned Manpower Distribution ...................................................................................................9<br />

2.3 Overall Workpackage Description ..............................................................................................10<br />

2.4 <strong>Project</strong> Structure <strong>and</strong> Deliverable Schedule...............................................................................18<br />

2.5 Deliverable Overview....................................................................................................................20<br />

3. RELATIONSHIP WITH THE PROGRAMME........................................... 21<br />

3.1 Relationship to Other <strong>Project</strong>s <strong>and</strong> Clustering Activities .........................................................21<br />

4. MAJOR PROJECT RESULTS AND INPUT TO STANDARDISATION .. 21<br />

4.1 Major <strong>Project</strong> Result: Overall Architecture...............................................................................21<br />

4.2 Major <strong>Project</strong> Result: TD-CDMA Equipment...........................................................................22<br />

4.3 Major <strong>Project</strong> Result: QoS Architecture ....................................................................................23<br />

4.4 Major <strong>Project</strong> Result: Mobility Architecture.............................................................................23<br />

4.5 Major <strong>Project</strong> Result: A4C Architecture....................................................................................26<br />

4.6 Major <strong>Project</strong> Result: IP-Paging Architecture ..........................................................................27<br />

5. DISSEMINATION OF RESULTS............................................................. 29<br />

5.1 Publications ...................................................................................................................................29<br />

5.2 Presentations .................................................................................................................................33<br />

5.3 Journals .........................................................................................................................................35<br />

5.4 Technical <strong>Report</strong>s .........................................................................................................................36<br />

Moby Dick WP6 5 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

5.5 St<strong>and</strong>ardisation .............................................................................................................................36<br />

5.6 Thesis .............................................................................................................................................37<br />

5.7 Press, Interviews, Broadcast, <strong>and</strong> Interviews.............................................................................37<br />

5.8 Moby Dick Summits .....................................................................................................................38<br />

5.9 Moby Dick Web-Site.....................................................................................................................42<br />

6. CONCLUSION, SELF ASSESSMENT, AND LESSONS LEARNT......... 43<br />

Moby Dick WP6 6 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

1. Objectives <strong>and</strong> Workplan of the project<br />

In order to evolve 3rd Generation mobile <strong>and</strong> wireless infrastructures further towards the Internet -<br />

targeting IST 2000 IV 5.2 "Terrestrial Wireless System <strong>and</strong> Networks", the project Moby Dick will<br />

define, implement, <strong>and</strong> evaluate an IPv6-based mobility-enabled end-to-end QoS architecture starting<br />

from the current IETF's QoS models, Mobile-IPv6, <strong>and</strong> AAA framework. A representative set of<br />

interactive <strong>and</strong> distributed multimedia applications will serve to derive system requirements for the<br />

verification, validation, <strong>and</strong> demonstration of the Moby Dick architecture in a testbed comprising UMTS,<br />

802.11 Wireless LANs <strong>and</strong> Ethernet. In the event of these existing applications or the underlying<br />

architectures not providing what is required, the necessary modification will be undertaken. The final testbed<br />

scenario is to provide Erasmus students exchanged between Spain <strong>and</strong> Germany with the mobilityenabled<br />

<strong>and</strong> wireless infrastructure to be able to follow lessons on the home university while being<br />

abroad.<br />

1.1 Workpackage WP1 – Architecture <strong>and</strong> Applications<br />

The objectives of this workpackage have been:<br />

• To define <strong>and</strong> specify the IPv6-based mobility-enabled end-to-end QoS Moby Dick architecture<br />

taking into account existing IETF QoS-, Mobile-IPv6- <strong>and</strong> AAA- st<strong>and</strong>ardization work.<br />

• To define functional requirements for the inter-working of ‘AAA <strong>and</strong> Charging’, QoS <strong>and</strong> Mobility.<br />

• To co-ordinate the technical work between WP2 (QoS), WP3 (Mobility) <strong>and</strong> WP4 (AAA) to<br />

guarantee a proper inter-working between these WPs.<br />

• To define set of interactive <strong>and</strong> distributive multimedia applications which are provided to WP5 to<br />

validate <strong>and</strong> verify the system concept <strong>and</strong> the application scenario.<br />

1.2 Workpackage WP2 – Quality of Service<br />

The objectives of this workpackage have been:<br />

• To develop solution for QoS in a IPv6-based mobility-enabled network.<br />

• To provide support for QoS in a consistent way in heterogeneous wireless-wired network.<br />

• To allow QoS adaptation to wireless link <strong>and</strong> mobility.<br />

• To introduce b<strong>and</strong>width-broker concept.<br />

• To introduce schemes for admission control.<br />

• To provide guidelines for resource provisioning.<br />

• To evaluate signalling schemes for QoS.<br />

• To ensure tight inter-working with AAAC <strong>and</strong> mobility solutions.<br />

• To verify the QoS solution in a demonstrator.<br />

1.3 Workpackage WP3 – Mobility<br />

The objectives of this workpackage have been:<br />

• To enable mobile differentiated (QoS) services for IP in the context of UMTS, while being able to<br />

authorise <strong>and</strong> charge users<br />

• To provide a unified mobile network architecture with a seamless mobility management for<br />

communication networks based on arbitrary heterogeneous access technologies, <strong>and</strong> to implement for<br />

this project specifically:<br />

• TD-CDMA (UMTS-TDD 1 ),<br />

• IEEE 802.11 (Wireless LAN) <strong>and</strong><br />

• Ethernet (Wired LAN).<br />

1.4 Workpackage WP4 – Authentication, Authorisation, Accounting <strong>and</strong><br />

Charging<br />

The objectives of this workpackage have been:<br />

• To facilitate the deployment of a ubiquitous Mobile IPv6 infrastructure through a best-suited <strong>and</strong><br />

pragmatic usage of an evolutionary AAAC architecture based on the IRTF AAA proposal, <strong>and</strong><br />

• To contribute with our work to main st<strong>and</strong>ard bodies.<br />

1 In previous reports TD-CDMA was named as W-CDMA. This was a misunderst<strong>and</strong>ing. Layer 1 <strong>and</strong> Layer 2 of<br />

UMTS-TDD are called TD-CDMA!<br />

Moby Dick WP6 7 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

1.5 Workpackage WP5 – Integration, Validation, <strong>Evaluation</strong>, <strong>and</strong> Trials<br />

The objectives of this workpackage have been:<br />

• To propose <strong>and</strong> demonstrate a convergent <strong>and</strong> coherent all-IP(v6) network infrastructure able to<br />

federate heterogeneous wireless access networks.<br />

• To evaluate Moby Dick Architecture through a testbed including representative applications <strong>and</strong><br />

access networks (efficiency, usability, utility).<br />

• To asses the commercial relevance <strong>and</strong> benefits (potential <strong>and</strong> actual).<br />

• To integrate <strong>and</strong> validate software <strong>and</strong> architecture provided by other workpackages in a specific trial<br />

scenario.<br />

• To trial the system in real life environment, providing end-users (students, operators, manufactures)<br />

views on exploitation conditions for the project results.<br />

• To create <strong>and</strong> operate the framework in which the evaluation process can gather the necessary data.<br />

1.6 Workpackage WP6 – <strong>Project</strong> Management <strong>and</strong> External Liaison<br />

The objectives of this workpackage have been:<br />

• To provide scientific, technical, <strong>and</strong> overall project management <strong>and</strong> co-ordination.<br />

• To ensure the quality management <strong>and</strong> assurance.<br />

• To maintain the information flow between partners.<br />

• To provide administrative <strong>and</strong> financial control according to workplan.<br />

• To co-ordinate the dissemination <strong>and</strong> promotion activities <strong>and</strong> to present the project towards the<br />

European Commission.<br />

• To build up <strong>and</strong> keep contacts to other IST projects (e.g. BRAIN, WINE GLASS) <strong>and</strong>/or other<br />

activities, e.g. EURESCOM projects (”http://www.eurescom.de/”), <strong>and</strong> to st<strong>and</strong>ardisation bodies<br />

such as IETF, etc.<br />

• To install an IPv6 cluster or sub-cluster in the framework of the “system Beyond 3G”-cluster for<br />

IPv6 mobility issues.<br />

2. Overall Plan - Description of the Workpackages<br />

2.1 Workpackage/Workload Distribution<br />

Participant<br />

number<br />

P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11 P12<br />

Org. T-Nova NEC UC3M ETHZ USTUTT GMD PTIN CRM EUR UKR FTW ICR<br />

Status: C P P P P P P P P P P P<br />

WP1 11 12 17 17 36 28 9 24 18 6 0 12<br />

WP2 9 0 24 16 17 0 28 42 18 20 6 26<br />

WP3 18 42 12 0 17 0 13 24 18 0 0 0<br />

WP4 12 0 12 36 24 56 0 0 0 0 6 10<br />

WP5 10 18 20 16 27 18 9 18 18 6 0 4<br />

WP6 27 0 4 3 0 0 0 0 0 0 0 0<br />

total MM 87 72 91 88 121 102 59 108 72 32 12 52<br />

MM in<br />

CPF<br />

87,4 72 91 88,2 121 102 59 108 72 32 12 52<br />

Table 1: Workload distribution per partner <strong>and</strong> workpackage<br />

Remark:<br />

• WP6 covered only administrative management. This includes the overall co-ordination for the coordinator<br />

(P01) of the project <strong>and</strong> dissemination activities. Partner P03 (UC3M) was responsible for<br />

the organisation of the Erasmus students in Spain. Partner P04 (ETHZ) was not funded by the<br />

Commission because they are Swiss. Both partners have a bigger amount of administrative work, this<br />

is reflected in manpower in WP6.<br />

Moby Dick WP6 8 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

• For all partners it was m<strong>and</strong>atory to participate in WP1 – the architectural workpackage – <strong>and</strong> in<br />

WP5 – test <strong>and</strong> trials. Only partner P11 (FTW) did not have to participate in these workpackages.<br />

They were participating with 10% funding <strong>and</strong> with a relative small amount of manpower. They were<br />

focusing on specific theoretical topic within WP2 – QoS – <strong>and</strong> WP4 – AAAC.<br />

• Partner P12 joined already the project last year (2002). The Amendment was confirmed in August<br />

2003.<br />

2.2 Planned Manpower Distribution<br />

140<br />

120<br />

Manpower in Manmonth<br />

100<br />

80<br />

60<br />

40<br />

20<br />

WP1<br />

WP2<br />

WP3<br />

WP4<br />

WP5<br />

WP6<br />

0<br />

P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11 P12<br />

Partner<br />

Figure 1: Graph of the manpower distribution per partner <strong>and</strong> workpackage<br />

Moby Dick WP6 9 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

2.3 Overall Workpackage Description<br />

The following includes administrative technical information, including the deliverables.<br />

B1. Workpackage list<br />

WP<br />

No<br />

Workpackage title<br />

Lead<br />

contractor<br />

No.,<br />

Responsible<br />

person<br />

Personmonths<br />

Startmonth<br />

Endmonth<br />

Deliverable No<br />

WP1<br />

Architectural Requirements<br />

<strong>and</strong> Applications<br />

P05<br />

Jürgen<br />

Jähnert<br />

190 1 30 D0101<br />

D0102<br />

D0103<br />

WP2 Quality of Service P08<br />

Hong-Yon<br />

Lach<br />

WP3 Mobility P02<br />

Amardeo<br />

Sarma<br />

206 5 28 D0201<br />

D0202<br />

144 5 28 D0301<br />

D0302<br />

D0303<br />

WP4<br />

Authentication, Authorisation,<br />

Accounting <strong>and</strong> Charging<br />

P04<br />

Burkhard<br />

Stiller<br />

156 5 28 D0401<br />

D0402<br />

WP5<br />

Integration, Validation,<br />

<strong>Evaluation</strong> <strong>and</strong> Trials<br />

P03<br />

José Ignacio<br />

Moreno<br />

Novella<br />

166 13 36 D0501<br />

D0502<br />

D0503<br />

D0504<br />

WP6<br />

<strong>Project</strong> Management <strong>and</strong><br />

External Liaison<br />

P01<br />

Hans Joachim<br />

Einsiedler<br />

34 1 36 D0601<br />

D0602<br />

D0603<br />

TOTAL 894<br />

Moby Dick WP6 10 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

B3. Workpackage description<br />

Workpackage number : WP1<br />

Title:<br />

Architecture <strong>and</strong> Applications<br />

Start date or starting event: Month 1/ Year 1<br />

Participant number: 1 2 3 4 5 6 7 8 9 10 11 12 Sum<br />

Person-months per participant: 11 12 17 17 36 28 9 24 18 6 0 12 190<br />

Objectives<br />

• To define <strong>and</strong> specify the IPv6-based mobility-enabled end-to-end QoS Moby Dick architecture taking into<br />

account existing IETF QoS-, Mobile-IPv6- <strong>and</strong> AAA- st<strong>and</strong>ards work.<br />

• To define functional requirements for the inter-working of ‘AAA <strong>and</strong> Charging’, QoS <strong>and</strong> Mobility.<br />

• To co-ordinate the technical work between WP2 (QoS), WP3 (Mobility) <strong>and</strong> WP4 (AAA) to guarantee a<br />

proper inter-working between these WPs.<br />

• To define set of interactive <strong>and</strong> distributive multimedia applications which are provided to WP5 to<br />

validate/verify the system concept <strong>and</strong> the application scenario.<br />

Description of work<br />

A0101: Applications<br />

• Select, possibly modify/enhance applications to challenge Moby Dick's technology <strong>and</strong> architectural<br />

solutions <strong>and</strong> to validate/verify the system concept <strong>and</strong> the application scenario ('ERASMUS students') in<br />

the field trials.<br />

A0102: Requirements of QoS Support<br />

• Specify general requirements of QoS support. Specify functional requirement, components <strong>and</strong> external<br />

interfaces for QoS.<br />

A0103: Requirements of Mobility Support<br />

• Specify general requirements of mobility support. Specify functional requirements, components <strong>and</strong><br />

external interfaces for mobility support for both, the network infrastructure <strong>and</strong> the mobile node.<br />

A0104: Requirements of AAA Support<br />

• Specify general requirements for an AAA framework in control of all policies <strong>and</strong> mechanisms pertinent to<br />

Mobility <strong>and</strong> QoS. Specify functional requirement, components <strong>and</strong> external interfaces of the AAA .<br />

Deliverables<br />

D0101: Moby Dick Framework Specification<br />

D0102: Moby Dick Application Framework Specification<br />

D0103: Moby Dick Consolidated System Integration Plan<br />

Milestones <strong>and</strong> expected result<br />

M1.1: First version of D0101 at M4<br />

M1.2: D0101 final version at M10 (Appendix will include the first version of D0201, D0301, <strong>and</strong> D0401.)<br />

M1.3: First version of D0102 at M12<br />

M1.4: First version of D0103 at M16 (Internal <strong>Report</strong>)<br />

M1.5: D0102 final version at M20<br />

M1.6: Second version of D0103 at M24 (Internal <strong>Report</strong>)<br />

M1.7: D0103 final version at M30<br />

Manpower Distribution for WP 1 – Partner per Activity<br />

Activity ID P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11 P12<br />

A0101 3 2 9 3 8 5 2 4 4 2 0 4<br />

A0102 4 0 5 4 8 0 4 12 7 6 0 4<br />

A0103 2 10 2 0 8 8 3 8 7 0 0 0<br />

A0104 2 0 2 10 12 15 0 0 0 0 0 4<br />

The table specifies an estimation of the workload distribution <strong>and</strong> will be adapted during the runtime of<br />

the project.<br />

Moby Dick WP6 11 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

B3. Workpackage description<br />

Workpackage number :<br />

WP2<br />

Title:<br />

Quality of Service<br />

Start date or starting event: Month 5 / Year 1<br />

Participant number: 1 2 3 4 5 6 7 8 9 10 11 12 Sum<br />

Person-months per participant: 9 0 24 16 17 0 28 42 18 20 6 26 206<br />

Objectives<br />

This workpackage will<br />

Investigate the QoS support for the IPv6-based mobility-enabled end-to-end QoS architecture, <strong>and</strong><br />

Develop the solutions in the Moby Dick testbed’s IP infrastructure <strong>and</strong> mobile nodes.<br />

Description of work<br />

Taking the architectural requirements from WP1, this workpackage will carry out the following activities:<br />

A0201: Admission control<br />

• Introduce admission control which is necessary to control the amount of traffic which is allowed for a<br />

given QoS class, in order to preserve the already provided QoS for other packets of the same class.<br />

• Study B<strong>and</strong>width Broker to manage resources in a user domain according to its dynamic SLA, with RSVP<br />

as its signalling protocol with the mobile nodes, to support negotiation <strong>and</strong> re-negotiation of admission<br />

control in a time-critical manner.<br />

A0202: QoS provision<br />

• Investigate the use of IntServ/RSVP in the user domain to support per-flow QoS. Typically, the issues to<br />

be addressed include the QoS mapping at the IntServ/DiffServ domain boundary; definition of the optimal<br />

operation point between reservations of the IntServ model, SLAs <strong>and</strong> configuration of service classes<br />

(PHBs) of DiffServ; etc.<br />

• Investigate how to classify <strong>and</strong> mark the packets both in the user node <strong>and</strong> the edge routers.<br />

A0203: QoS adaptation to wireless link <strong>and</strong> mobility<br />

• Define a QoS API <strong>and</strong> its mapping to the underlying QoS support. Such QoS API will also be used for<br />

mobility support to allow the mobile device to switch to another network proactively.<br />

• Adapt the behaviour of the protocol stack, especially TCP, to wireless-link <strong>and</strong> mobility, to optimise its<br />

performance.<br />

• Enhance protocol operations by enhancing information exchange in the interfaces between protocol layers.<br />

A0204:Implementation <strong>and</strong> evaluation of the Moby Dick QoS components<br />

• Implement the Moby Dick QoS component according to the research results in A0201, A0202 <strong>and</strong> A0203.<br />

• Integrate the Moby Dick QoS components in the Moby Dick testbed <strong>and</strong> evaluate their performance.<br />

Deliverables<br />

D0201: Initial Design <strong>and</strong> Specification of the Moby Dick QoS Architecture<br />

D0202: Development <strong>and</strong> Implementation <strong>Report</strong> on the QoS Components for Moby Dick<br />

Milestones <strong>and</strong> expected result<br />

M2.1: First version of D0201 at M10 included in D0101 as an appendix of work in progress<br />

M2.2: D0201 final version at M16<br />

M2.3: Test <strong>and</strong> evaluation of the initial implementation of the QoS components at M20<br />

M2.4: Test <strong>and</strong> evaluation of the final implementation of the QoS components at M27<br />

M2.5: D0202 final version at M28<br />

Manpower Distribution for WP 2<br />

Activity ID P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11 P12<br />

A0201 0 0 0 9 10 0 4 11 0 0 2 0<br />

A0202 0 0 10 0 0 0 10 0 0 10 2 10<br />

A0203 9 0 0 0 0 0 0 11 10 0 2 2<br />

A0204 0 0 14 7 7 0 14 20 8 10 0 14<br />

The table specifies an estimation of the workload distribution <strong>and</strong> will be adapted during the runtime of<br />

the project.<br />

Moby Dick WP6 12 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

B3. Workpackage description<br />

Workpackage number :<br />

WP3<br />

Title:<br />

Mobility<br />

Start date or starting event: Month 5 / Year 1<br />

Participant number: 1 2 3 4 5 6 7 8 9 10 11 12 Sum<br />

Person-months per participant: 18 42 12 0 17 0 13 24 18 0 0 0 144<br />

Objectives<br />

• To enable mobile differentiated (QoS) services for IP in the context of UMTS<br />

• To provide a unified mobile network architecture with a seamless mobility management for<br />

communication networks based on<br />

o TD-CDMA (UMTS),<br />

o IEEE 802.11 (Wireless LAN) <strong>and</strong><br />

o Ethernet (Wired LAN).<br />

Description of work<br />

A0301 Specification<br />

• This activity will specify <strong>and</strong> integrate mobility architecture.<br />

A0302 Development<br />

• This activity will develop interfaces <strong>and</strong> modules for the specified mobility architecture. The specification<br />

will be adapted to real-world requirements <strong>and</strong> the capabilities within this project. It will in particular<br />

consider requirements from other workpackages to allow the provision of enhanced service qualities in a<br />

mobile environment.<br />

A0303 Implementation<br />

• This activity will implement the mobility architecture as specified in the previous activities.<br />

• The implemented prototype will provide fast <strong>and</strong> seamless mobility between different networks <strong>and</strong><br />

administrative domains. It will also implement enhancements to IP mobility support, in order to support<br />

real-time VoIP traffic.<br />

• The technical basis for this work will come from both the telecommunication/UMTS <strong>and</strong> the Internet/IETF<br />

environments. In particular, real-time voice via QoS-enhanced Mobile Ipv6 over local <strong>and</strong> wide area<br />

networks – <strong>and</strong> seamless mobility between them – will be supported.<br />

Deliverables<br />

D0301: Initial Design <strong>and</strong> Specification of a Moby Dick Mobility Architecture<br />

D0302: Mobility Architecture Implementation <strong>Report</strong><br />

D0303: Development <strong>and</strong> Implementation <strong>Report</strong> on the Mobility Components for Moby Dick<br />

Milestones <strong>and</strong> expected result<br />

M3.1: First version of D0301 at M10 included in D0101 as an appendix of work in progress<br />

M3.2: D0301 final version <strong>and</strong> implementation prototype LAN at M16<br />

M3.3: First version of D0302 at M20<br />

M3.4: D0302 final version <strong>and</strong> implementation prototype WAN at M24<br />

M3.5: First version of the overall report D0303 at M26<br />

M3.6: D0303 final version <strong>and</strong> final prototype at M28<br />

Manpower Distribution for WP 3<br />

Activity ID P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11 P12<br />

A0301 6 11 4 0 4 0 4 6 4 0 0 0<br />

A0302 6 10 4 0 5 0 5 6 5 0 0 0<br />

A0303 6 21 4 0 8 0 4 12 9 0 0 0<br />

The table specifies an estimation of the workload distribution <strong>and</strong> will be adapted during the runtime of<br />

the project.<br />

Moby Dick WP6 13 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

B3. Workpackage description<br />

Workpackage number : WP4<br />

Title:<br />

Authentication, Authorisation, Accounting <strong>and</strong> Charging<br />

Start date or starting event: Month 5 / Year 1<br />

Participant number: 1 2 3 4 5 6 7 8 9 10 11 12 Sum<br />

Person-months per participant: 12 0 12 36 24 56 0 0 0 0 6 10 154<br />

Objectives<br />

• To facilitate the deployment of an ubiquitous Mobile IPv6 infrastructure through a best-suited <strong>and</strong><br />

pragmatic usage of an evolutionary AAAC architecture based on the IRTF AAA proposal, <strong>and</strong><br />

• To contribute with our work to main st<strong>and</strong>ard bodies.<br />

Description of work<br />

The task of this work package is to specify, develop, <strong>and</strong> implement a generic <strong>and</strong> scalable AAAC architecture<br />

in support of Mobile IPv6-based Quality-of-Service (QoS) aware services over a heterogeneous network<br />

infrastructure including integrated wired/wireless access aspects, multicast services, <strong>and</strong> multi-provider<br />

scenarios.<br />

A0401: Detailed Specification of an AAAC Architecture<br />

• The IETF's <strong>and</strong> IRTF's AAA architecture serves as the basis of this work, however, based on the dedicated<br />

services considered <strong>and</strong> designed, a major enlargement <strong>and</strong> detailing of this basis is necessary. These<br />

extensions are to be specified <strong>and</strong> integrated into the overall Moby Dick architecture.<br />

A0402: Implementation of the Specified AAAC Architecture<br />

• This activity will implement an AAAC server based on the specification of ACT 0401 <strong>and</strong> on the overall<br />

Moby Dick architecture. It will provide an open source reference implementation to the public domain.<br />

A0403: Authentication, Authorisation, <strong>and</strong> Auditing<br />

• Evaluate mobility scenarios <strong>and</strong> requirements for authentication <strong>and</strong> authorisation with respect to Mobile<br />

IPv6. Based on the support for configurability for service-specific <strong>and</strong> user-specific features by allowing<br />

for policy-based functions, the scenario given above is applied to the architecture.<br />

A0404: Accounting <strong>and</strong> Charging<br />

• Tasks to be performed include the investigation <strong>and</strong> definition of the relation between accounted for<br />

information <strong>and</strong> charging based on the services provided including mobile services <strong>and</strong> users (service level<br />

agreement definitions, parameter identification, mapping definition, <strong>and</strong> pricing model design). Based on<br />

investigations on the suitability of accounting for information in use of dynamic <strong>and</strong> static pricing models<br />

applying policy management, the design of an appropriate accounting <strong>and</strong> charging model for DiffServ<br />

backbones is performed. In addition, flow-based access networks <strong>and</strong> a transition to future QoS signalling<br />

methods in the local domain for mobile users are developed. Apply the given scenario above to the<br />

architecture <strong>and</strong> set up a test case <strong>and</strong> implementation.<br />

Deliverables<br />

D0401: Design <strong>and</strong> Specification of an AAAC Architecture Draft on administrative, heterogeneous, multiprovider,<br />

<strong>and</strong> mobile IPv6 Subnets<br />

D0402: Development <strong>and</strong> Implementation <strong>Report</strong> an AAAC Components for Moby Dick<br />

Milestones <strong>and</strong> expected result<br />

M4.1: First Version of AAAC architecture at M10, included in D0101 as an appendix of work in progress<br />

M4.2: D0401 final version at M12<br />

M4.3: Test <strong>and</strong> evaluation of the components developed in this work package, at M20<br />

M4.4: Open source AAAC server implementation provided to public domain, at M24<br />

M4.5: D0402 final version at M28<br />

Manpower Distribution for WP 4<br />

Activity ID P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11 P12<br />

A0401 4 0 4 8 4 8 0 0 0 0 2 0<br />

A0402 2 0 2 18 12 28 0 0 0 0 0 10<br />

A0403 3 0 3 4 3 10 0 0 0 0 2 0<br />

A0404 3 0 3 6 5 10 0 0 0 0 2 0<br />

The table specifies an estimation of the workload distribution <strong>and</strong> will be adapted during the<br />

runtime of the project.<br />

Moby Dick WP6 14 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

B3. Workpackage description<br />

Workpackage number : WP5<br />

Title:<br />

Integration, Validation, <strong>Evaluation</strong> <strong>and</strong> Trials<br />

Start date or starting event: Month 1 / Year 1<br />

Participant number: 1 2 3 4 5 6 7 8 9 10 11 12 Sum<br />

Person-months per participant: 10 18 22 16 27 18 9 18 18 6 0 4 166<br />

Objectives<br />

• To propose <strong>and</strong> demonstrate a convergent <strong>and</strong> coherent all-IP(v6) network infrastructure able to federate<br />

heterogeneous wireless access networks.<br />

• To evaluate Moby Dick Architecture through a testbed including representative applications <strong>and</strong> access<br />

networks (efficiency, usability, utility).<br />

• To integrate <strong>and</strong> validate software <strong>and</strong> architecture provide by others workpackages in a specific trial<br />

scenario.<br />

• To trial the system in real life environment, providing end-users (students, operators, manufactures) views<br />

on exploitation conditions for the project results.<br />

• To create <strong>and</strong> operate the framework in which the evaluation process can gather the necessary data.<br />

Description of work<br />

Moby Dick will perform international trials at two different sites: Madrid/Spain <strong>and</strong> Stuttgart/Germany using<br />

real users: SOCRATES-ERASMUS students located in these cities. These trials will be deployed over the<br />

Moby Dick framework specified in WP1 <strong>and</strong> will provide a comprehensive technical-economical evaluation of<br />

it. Each trial will be based on a three stage process: define trials <strong>and</strong> experiments, perform the experiments <strong>and</strong><br />

evaluate them. Based on trials evaluation, WP5 will provide appropriate feedback to WP1-4.<br />

A0501: Definition of Moby Dick Trial Scenarios.<br />

• In this activity, a detail definition of trials will be done based on the work done in WP1-4. Trials will test<br />

two different scenarios based on synchronous (real-time) <strong>and</strong> asynchronous applications (non real time).<br />

Synchronous applications will be based on VoIP <strong>and</strong> telelearning, which will permit exchange information<br />

between ERASMUS students <strong>and</strong> their home university (faculty, co-students) <strong>and</strong> even to attend remote<br />

conferences, lectures <strong>and</strong> presentations in real time. Asynchronous applications will be based on remote<br />

access <strong>and</strong> will provide ERASMUS information, digital libraries, etc. Based on these trials, the objective of<br />

the project will be evaluated in a real scenario.<br />

A0502: First Test <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong><br />

• In this activity the first Trial will be carried out. This trial will focus on local test of Moby Dick prototype<br />

without external users <strong>and</strong> will allow to fit all the local equipment of the trials sites <strong>and</strong> will provide<br />

feedback for the WP1-4.<br />

A0503: Second Test <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong><br />

• The second trial will include unicast applications based on VoIP, telelearning <strong>and</strong> database access <strong>and</strong> will<br />

be conducted by real users, SOCRATES-ERASMUS students located in the trial sites (Madrid/Spain <strong>and</strong><br />

Stuttgart/Germany)<br />

A0504: Trial <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong><br />

• <strong>Final</strong> trials will include unicast <strong>and</strong> multicast applications. Both of them will be based on SOCRATES-<br />

ERASMUS student in a real life environment. As a conclusion of the trial, a comprehensive technicaleconomical<br />

evaluation of Moby Dick framework will be provided.<br />

Deliverables<br />

D0501: Definition of Moby Dick Trial Scenarios.<br />

D0502: First Test <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong><br />

D0503: Second Test <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong><br />

D0504: Trial <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong><br />

Milestones <strong>and</strong> expected result<br />

M5.1: D0501 final version at M14<br />

M5.2: <strong>Evaluation</strong> workshop in M15<br />

M5.3: D0502 final version at M16<br />

M5.4: <strong>Evaluation</strong> workshop in M23<br />

M5.5: D0503 final version at M24<br />

M5.6: <strong>Evaluation</strong> workshop in M35<br />

Moby Dick WP6 15 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

M5.7: D0504 final version at M36<br />

Manpower Distribution for WP 5<br />

Activity ID P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11 P12<br />

A0501 1 2 2 2 3 2 1 2 2 1 0 0<br />

A0502 1 2 4 2 3 3 1 2 2 0 0 2<br />

A0503 2 4 4 4 6 5 2 4 4 2 0 2<br />

A0504 6 10 12 8 15 8 5 10 10 3 0 0<br />

The table specifies an estimation of the workload distribution <strong>and</strong> will be adapted during the runtime of<br />

the project.<br />

Moby Dick WP6 16 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

B3. Workpackage description<br />

Workpackage number : WP6<br />

Title:<br />

<strong>Project</strong> Management <strong>and</strong> External Liaison<br />

Start date or starting event: Month 1 / Year 1<br />

Participant number: 1 2 3 4 5 6 7 8 9 10 11 12 Sum<br />

Person-months per participant: 27 0 4 3 0 0 0 0 0 0 0 0 34<br />

Objectives<br />

• To provide scientific, technical <strong>and</strong> overall project management <strong>and</strong> co-ordination.<br />

• To ensure the quality management <strong>and</strong> assurance.<br />

• To maintain the information flow between partners.<br />

• To provide administrative <strong>and</strong> financial control according to workplan.<br />

• To co-ordinate the dissemination <strong>and</strong> promotion activities <strong>and</strong> to present the project towards the European<br />

Commission.<br />

• To build up <strong>and</strong> keep contacts to other IST projects (e.g. BRAIN, WINE CLASS) <strong>and</strong>/or other activities,<br />

e.g. EURESCOM projects (”http://www.eurescom.de/”), <strong>and</strong> to st<strong>and</strong>ardisation bodies such as IETF, etc.<br />

Description of work<br />

The objectives outlined are split up into the following activities:<br />

A0601: Administrative Work <strong>and</strong> IST Activities<br />

• Supervision of workpackages according to the contract/workplan.<br />

• Financial controlling <strong>and</strong> management of resources.<br />

• Controlling of formal reporting with respect to the contract (management reports).<br />

• Preparation of IST reports (Annual <strong>Project</strong> reports).<br />

A0602: External Liaison<br />

• Participation in the concertation mechanisms, clusters, <strong>and</strong> pushing the co-operation between related<br />

projects on the regional, cross-regional <strong>and</strong> European level.<br />

• Proactive dissemination of information to the public.<br />

• Co-ordination <strong>and</strong> controlling of each partners’ results in order to allow for effective <strong>and</strong> efficient internal<br />

information delivery (e.g. deliverables).<br />

A0603: Dissemination<br />

• Analysis <strong>and</strong> verification of business opportunities, exploitation, <strong>and</strong> use plans.<br />

Deliverables<br />

D0601 Dissemination <strong>and</strong> Use Plan<br />

D0602 Exploitation Plan<br />

D0603 <strong>Evaluation</strong>, Recommendation, <strong>and</strong> <strong>Final</strong> <strong>Project</strong> <strong>Report</strong><br />

Milestones <strong>and</strong> expected result<br />

Monthly Management <strong>Report</strong>s to the Commission<br />

M6.1: Dissemination <strong>and</strong> Use Plan at M7.<br />

M6.2: Annual <strong>Project</strong> <strong>Report</strong> for the first year at M12<br />

M6.3: Annual <strong>Project</strong> <strong>Report</strong> for the second year at M24<br />

M6.4: Annual <strong>Project</strong> <strong>Report</strong> for the third year, D0601 <strong>and</strong> D602 at M37<br />

Manpower Distribution for WP 6<br />

Activity ID P01 P02 P03 P04 P05 P06 P07 P08 P09 P10 P11 P12<br />

A0601 18 0 1 1 0 0 0 0 0 0 0 0<br />

A0602 5 0 2 1 0 0 0 0 0 0 0 0<br />

A0603 9 0 1 1 0 0 0 0 0 0 0 0<br />

The table specifies an estimation of the workload distribution <strong>and</strong> will be adapted during the<br />

runtime of the project.<br />

Moby Dick WP6 17 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

2.4 <strong>Project</strong> Structure <strong>and</strong> Deliverable Schedule<br />

The results of all workpackages have been manifested in 17 deliverables.<br />

WP1<br />

WP2<br />

WP3<br />

WP4<br />

WP5<br />

WP6<br />

2001<br />

0<br />

2002 2003 2004<br />

months<br />

6 12 18 24 30 36<br />

Deliverables<br />

D0101<br />

D0102<br />

D0103<br />

D0201<br />

D0202<br />

D0301<br />

D0302<br />

D0303<br />

D0401<br />

D0402<br />

D0501<br />

D0502<br />

D0503<br />

D0504<br />

D0601<br />

D0602<br />

D0603<br />

Figure 2: Time Schedule of the Workpackages <strong>and</strong> the Deliverables<br />

The results of the implementation workpackages (WP2, WP3, <strong>and</strong> WP4) have been tested at the same<br />

time in workpackage WP5. The project has defined three steps of testing. WP5.1 has done local tests.<br />

WP5.2 has done interoperability in at least two locations connected via the European Commission<br />

Research backbone. In WP5.3, the project has successfully performed the tests, which than led to the trial.<br />

Moby Dick WP6 18 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

WP2 WP3 WP4<br />

WP1<br />

WP5.1<br />

time<br />

WP5.2<br />

WP5.3<br />

WP6<br />

Figure 3:Organisation <strong>and</strong> Functional Structure of the <strong>Project</strong><br />

Figure 3 shows the interdependence of the workpackages. WP6 covers all other workpackages. WP1<br />

accompanies the implementation workpackages (WP2, WP3, <strong>and</strong> WP4) <strong>and</strong> the first two parts of the test<br />

<strong>and</strong> trial workpackage (WP5.1 <strong>and</strong> WP5.2). WP1 closed when the trial has started. However, the full<br />

support of the trial was given within WP5.3.<br />

Moby Dick WP6 19 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

2.5 Deliverable Overview.<br />

Deliverables list<br />

Del. No. Deliverable name WP<br />

no.<br />

Del.<br />

type*<br />

Security**<br />

D0101 Moby Dick Framework Specification 2 1 R Pub.<br />

D0102 Moby Dick Application Framework Specification 1 R Pub.<br />

D0103 Moby Dick Consolidated System Integration Plan 1 R Pub.<br />

D0201<br />

D0202<br />

D0301<br />

Initial Design <strong>and</strong> Specification of the Moby Dick QoS<br />

Architecture<br />

Development <strong>and</strong> Implementation <strong>Report</strong> on the QoS<br />

Components for Moby Dick<br />

Initial Design <strong>and</strong> Specification of the Moby Dick Mobility<br />

Architecture<br />

2 R Int.<br />

2 P Pub.<br />

3 R Int.<br />

D0302 Mobility Architecture Implementation <strong>Report</strong> 3 R Pub.<br />

D0303<br />

D0401<br />

D0402<br />

Development <strong>and</strong> Implementation <strong>Report</strong> on the Mobility<br />

Components for Moby Dick<br />

Design <strong>and</strong> Specification of an AAAC Architecture Draft on<br />

administrative, heterogeneous, multi-provider, <strong>and</strong> mobile<br />

IPv6 sub-networks<br />

Development <strong>and</strong> Implementation <strong>Report</strong> on AAAC<br />

Components for Moby Dick<br />

3 P Pub.<br />

4 R Pub.<br />

4 P Pub.<br />

D0501 Definition of Moby Dick Test <strong>and</strong> Trial Methodology 5 R Pub.<br />

D0502 First Test <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong> 5 R Int.<br />

D0503 Second Test <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong> 5 R Int.<br />

D0504 Trial <strong>and</strong> <strong>Evaluation</strong> <strong>Report</strong> 5 R Pub.<br />

D0601 Dissemination <strong>and</strong> Use Plan 6 R Pub<br />

D0602 Exploitation Plan 6 R Int.<br />

D0603 <strong>Evaluation</strong>, <strong>Recommendations</strong> <strong>and</strong> <strong>Final</strong> <strong>Project</strong> <strong>Report</strong> 6 R Pub.<br />

* A short, self-evident description e.g. report, demonstration, conference, specification, prototype…<br />

** Int. Internal circulation within project (<strong>and</strong> Commission <strong>Project</strong> Officer if requested)<br />

Rest. Restricted circulation list (specify in footnote) <strong>and</strong> Commission PO only<br />

IST Circulation within IST Programme participants<br />

FP5 Circulation within Framework Programme participants<br />

Pub. Public document<br />

Table 2: Deliverable Titles<br />

2 The deliverable D0101 will include the first versions of D0201 (M2.1), D0301(M3.1) <strong>and</strong> D0401 (M4.1) as working documents in<br />

the appendix.<br />

Moby Dick WP6 20 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

3. Relationship with the Programme<br />

The number of Internet connected h<strong>and</strong>sets or mobile hosts have exceeded the number of fixed to the<br />

Internet connected hosts in 2003. At the same time, an increasing number of mobile <strong>and</strong> portable hosts<br />

will require <strong>and</strong> eventually have integrated interfaces to connect various kinds of access networks, such as<br />

cellular networks, wireless LANs, <strong>and</strong> wired LANs, to be engaged in communications with various<br />

desired QoS. In addition to horizontal h<strong>and</strong>over mechanisms (roaming in different cells) established in<br />

cellular networks, this multi-access network scenario requires vertical (connection to different types of<br />

access networks) h<strong>and</strong>over solutions. To meet these requirements, Moby Dick has developed its uniform<br />

IP-convergence architecture for ubiquitous Internet access. IPv6, MIPv6, <strong>and</strong> AAA are key ingredients of<br />

Moby Dick's approach to mobility. QoS <strong>and</strong> AAA are extremely well suited to provide the European<br />

Community an added value <strong>and</strong> to contribute to policies of the European Commission. IPv6, QoS,<br />

mobility <strong>and</strong> AAA are considered – both at the European level <strong>and</strong> within the IETF – to be the<br />

technologies necessary for ubiquitous access for the next-generation Internet. In addition, they are the<br />

technical areas where Europe has a competitive edge over the US – both with respect to influence in the<br />

relevant st<strong>and</strong>ardisation bodies <strong>and</strong> with regard to products. Within this context, Moby Dick will<br />

contribute to <strong>and</strong> promote the IST Programme Objectives in several ways:<br />

• By establishing a new, IPv6-based convergence architecture for uniform ubiquitous usage of existing<br />

<strong>and</strong> next generation of heterogeneous wired, wireless, <strong>and</strong> mobile access technologies to the Internet.<br />

• By introducing a selected user community to use the trial infrastructure <strong>and</strong> to evaluate the<br />

importance of the services enabled by this architecture – thus increasing user dem<strong>and</strong>s for the<br />

services <strong>and</strong> the capability of suppliers to meet these dem<strong>and</strong>s.<br />

• By leveraging the European success in mobile technology <strong>and</strong> the related infrastructure deployment,<br />

thereby enhancing acceptance of IPv6 <strong>and</strong> maintaining European leadership in the next generation of<br />

mobile <strong>and</strong> wireless systems, their development <strong>and</strong> deployment.<br />

3.1 Relationship to Other <strong>Project</strong>s <strong>and</strong> Clustering Activities<br />

Within the IST-Programme, the project participated in the “System Beyond 3G”-cluster<br />

(http://www.cordis.lu/ist/ka4/mobile/beyond3g.htm). It was planned in the beginning to set-up an IPv6<br />

sub-cluster in the framework of the “System beyond 3G”-cluster. The activity was not started, since the<br />

focus of the cluster went into more Internet compliant interests <strong>and</strong> so it was not necessary to double the<br />

work. In 2003 Moby Dick representative Hong-Yong Lach representing P08 (Motorola) headed the<br />

“System Beyond 3G”-cluster.<br />

The project invited other project to present their results as well the project was invited to present the<br />

results in other workshops, summits, etc. All workshops <strong>and</strong> summits are listed later in this report.<br />

4. Major <strong>Project</strong> Results <strong>and</strong> Input to St<strong>and</strong>ardisation<br />

4.1 Major <strong>Project</strong> Result: Overall Architecture<br />

The Moby Dick architecture successfully integrated Mobility, QoS <strong>and</strong> AAA towards an IP dominated<br />

mobile Internet platform. The key result of the project is that Mobile IPv6 with the slight extensions as<br />

proposed in Moby Dick is able to provide QoA-aware <strong>and</strong> AAA-supported seamless mobility on<br />

heterogeneous network architecture.<br />

The Moby Dick architecture clearly showed that the Internet can become a mobile network which goes<br />

beyond the support for nomadic use only, as currently supported by WLAN/Mobile IP technologies.<br />

Inter-technology h<strong>and</strong>over can be supported easily <strong>and</strong> though the profile concept of Moby Dick users<br />

can be de-coupled from end systems <strong>and</strong> user mobility concepts can be introduced into such a network<br />

without severe problems.<br />

A further result is that seamless mobility between administrative domains is still an open issue <strong>and</strong> was<br />

not the key focus of Moby Dick for the following reason:<br />

Moby Dick provides a network architecture which provides technical solutions to technical problems. The<br />

inter-domain scenario is rather an economical <strong>and</strong> contractual problem than a technical problem. Here the<br />

relation <strong>and</strong> in turn the business models describing the relationship between two operators are the more<br />

critical path <strong>and</strong> so, this topic is out of the scope of Moby Dick.<br />

Further open issues so far are, if the mobile operators really allow the Internet to become mobile <strong>and</strong><br />

seamlessly available since the Internet lacks of a business model <strong>and</strong> so there exists no concept how to<br />

really earn money. So the Moby Dick consortium can h<strong>and</strong>over this successor-problem to the economists<br />

Moby Dick WP6 21 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

in order to get feedback about the level of openness this infrastructure can st<strong>and</strong> in order to generate the<br />

revenue required.<br />

A further, very important aspect is the missing concept describing the relationship between the network<br />

operator <strong>and</strong> a third party operator creating a service to be consumed by the user. This relationship could<br />

bring new requirements to the AAA part of the Moby Dick architecture which has nod been considered so<br />

far.<br />

4.2 Major <strong>Project</strong> Result: TD-CDMA Equipment<br />

In the framework of the Moby Dick project, EURECOM's Radio Software Platform has been enhanced to<br />

provide the required RRC functionalities in addition to the former UMTS-TDD Layer 1 <strong>and</strong> Layer 2<br />

features. Through the http://www.wireless3g4free.com/ website, EURECOM will release its<br />

implementation of the UMTS/TDD (3GPP) Access Stratum <strong>and</strong> IPv4/v6 interconnect under a GNU GPL<br />

(i.e. for free)<br />

3.5G + WLAN<br />

Radio Access<br />

Next Generation Mobile<br />

Internet Technology (Mobile-<br />

IPv6, DiffServ)<br />

Open-Source<br />

Software (Linux,<br />

RTLinux, RTAI)<br />

Figure 1: St<strong>and</strong>ardisation Relations<br />

Technical Information:<br />

Wireless3G4Free.com’s approach is based on the convergence of three technological trends:<br />

Collaborative wireless st<strong>and</strong>ards (e.g. 3GPP, 802.11), Next Generation Internet Technology (Mobile-<br />

IPv6, DiffServ, etc.) <strong>and</strong> open-source software. The components are combined to provide innovative,<br />

cost <strong>and</strong> spectrally efficient solutions for providing high-end Internet services to mobile users.<br />

Specifically, our approach allows for:<br />

Advanced signal processing techniques for ensuring high spectral efficiency:<br />

• smart antenna processing<br />

• iterative coding<br />

• multi-user scheduling<br />

• higher layers protocols & services (direct interconnection with IPv4 <strong>and</strong> IPv6 networks <strong>and</strong> WLAN<br />

systems)<br />

• Joint radio resource, mobility <strong>and</strong> QoS management across different radio access technologies<br />

The hardware/software platforms currently run under the RT-Linux real-time operating system using<br />

public-domain IPv4 <strong>and</strong> IPv6 protocol implementations. The software portion can be built from st<strong>and</strong>ard<br />

Red Hat 7.3 <strong>and</strong> 8.0 releases of the Linux operating system <strong>and</strong> currently runs on x86-based processing<br />

systems. Low-power embedded solutions are currently under development.<br />

The provided solutions cover the following operating modes<br />

• Real time processing for wideb<strong>and</strong> signals (e.g. 3G St<strong>and</strong>ards) in the RF Spectrum (currently 1.900<br />

to 1.920GHz) or at Intermediate Frequency (70 MHz)<br />

• Recording mode for off-line post-processing (measurement campaigns)<br />

• 3GPP Radio Access Network Simulation for Linux clusters<br />

The platform currently implements the 3GPP UMTS/TDD high chip rate (3.84 Mchip/s) access stratum<br />

protocols with an IP-based interconnection with off-the-shelf 802.11 WLAN solutions.<br />

Moby Dick WP6 22 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

4.3 Major <strong>Project</strong> Result: QoS Architecture<br />

The QoS Architecture major results can be structure along three main lines:<br />

a) The definition of an operator-driven service concept with practical usage for IP networks. In<br />

an operator environment, controlling effectively the resources that are free <strong>and</strong> what is being<br />

used by each user is essential from the Quality of Service point of view. Moreover, this<br />

control is also needed from a commercial <strong>and</strong> AAAC point of view – only paying users may<br />

access the network, with the QoS allowed by their profile. Therefore, WP2 developed a<br />

service concept that simultaneously allows practical resource control, while complying with<br />

the commercial view of a service.<br />

b) The definition of an integrated QoS framework, able to support QoS-aware mobility <strong>and</strong><br />

AAAC interworking. For feasibility reasons, this framework had to be light, but with<br />

extensive flexibility, in order not to constrain the services to be provided by the operators.<br />

An IntServ-alike solution does not fit well with the scalability dem<strong>and</strong>ed by such an<br />

environment, where millions of terminals can be expected. On the other h<strong>and</strong>, a pure<br />

DiffServ approach does not have enough precision in resource control <strong>and</strong> QoS guarantees.<br />

The outcome of these considerations was the development of a scenario defining specific<br />

mobility <strong>and</strong> AAAC messages, <strong>and</strong> using distributed QoS Brokers to perform Call<br />

Admission Control (CAC) per user <strong>and</strong> per service <strong>and</strong> resource management. Some of the<br />

message flows defined can be found in the next section, <strong>and</strong> will not be repeated here. The<br />

overall control infrastructure will be easily scalable, with proper network design.<br />

c) The creation of a mobility-aware QoS-broker, with st<strong>and</strong>ard interfaces for AAAC systems,<br />

<strong>and</strong> operating on the basis of the “customer profile”. The QoS Broker developed is<br />

populated with several types of interfaces <strong>and</strong> functionalities, making it a flexible control<br />

tool, able to interoperate with different types of devices, <strong>and</strong> to support multiple resource<br />

management policy strategies:<br />

The QoS Broker developed followed distributed management IP-st<strong>and</strong>ards for communications,<br />

resorting to the COPS protocol for communication with other devices. The QoS broker is fully<br />

flexible, with a set of independent modules:<br />

• A QoS Broker engine, able to perform user <strong>and</strong> service admission control, <strong>and</strong> able to<br />

keep track of the resources under its domain <strong>and</strong> manage its QoS domain in an<br />

optimised way. The support of different management policies is done by the<br />

configuration/complexity of this entity.<br />

• A Virtual Router interface to provide to the QoS Broker engine a common interface,<br />

independent of the types of Access Router. Thus the QoS Broker can take decisions<br />

with simple generic models for the ARs. This interface is then able to map this generic<br />

model into the specifics of each AR.<br />

• A COPS interface for AR configuration <strong>and</strong> interoperation, able to h<strong>and</strong>le mobility<br />

information messages, <strong>and</strong> to adequately configure the routers according with the QoS<br />

engine decisions.<br />

• A COPS interface with the AAAC system for reception of the user profiles <strong>and</strong> service<br />

definitions<br />

• A custom interface with other QoS Brokers, both for mobility management (using<br />

context transfer) <strong>and</strong> detailed network control.<br />

• A custom interface for data collecting to have information on the real network status.<br />

This framework <strong>and</strong> the QoS Broker have been successfully integrated in the Moby Dick infrastructure,<br />

<strong>and</strong> properly tested.<br />

4.4 Major <strong>Project</strong> Result: Mobility Architecture<br />

Fast h<strong>and</strong>-over prototype: A significant result of the project was the implementation of fast h<strong>and</strong>over in<br />

the mobility <strong>and</strong> integrated prototypes towards seamless mobility. Using just MIPv6, there is quite some<br />

delay when the access point (access router) is changed, in the range of up to 10 seconds. This could be<br />

significantly reduced using Fast H<strong>and</strong>over, which uses the make-before-break approach compared to<br />

break-before-make of plain MIPv6.<br />

Before fast h<strong>and</strong>over was implemented, Fast H<strong>and</strong>over was compared to using just Mobile IPv6, <strong>and</strong> it<br />

could be shown that it we could expect significant improvements. The following ns-2 simulations done in<br />

the project demonstrates the gains we get via Fast H<strong>and</strong>over regarding latency.<br />

Moby Dick WP6 23 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Figure 2: Mobile IPv6 versus Fast H<strong>and</strong>over Mobile IPv6<br />

Further simulations showed that data loss could also almost be eliminated using Fast H<strong>and</strong>over. These<br />

simulation results led to Moby Dick using this technology for seamless h<strong>and</strong>overs.<br />

The prototype confirmed our expectations regarding seamlessness. In addition, it turned out that Fast<br />

H<strong>and</strong>over could nicely be integrated with AAA <strong>and</strong> QoS to carry context data (user identity, QoS) from<br />

the old Access Router to the new Access Router, thus supporting context transfer. Though not yet<br />

officially taken up, such results have been discussed at IETF in the Seamoby group, <strong>and</strong> it such<br />

combinations will hopefully be taken up in future.<br />

The figure below shows how the message flows integrate context transfer in our implementation of Fast<br />

H<strong>and</strong>over.<br />

MN oAR nAR oQoS.f nQoS.f AAAC.f HA<br />

2<br />

1<br />

3<br />

*<br />

A<br />

C<br />

B<br />

5<br />

6<br />

7<br />

9<br />

8<br />

* if delay is an issue, it is an<br />

option to not wait for C <strong>and</strong> “roll<br />

back” in case of failure instead.<br />

10<br />

11 12<br />

13<br />

14<br />

X<br />

15<br />

Figure 3: Moby Dick fast intra-domain h<strong>and</strong>over message flow (including AAA / QoS)<br />

Moby Dick WP6 24 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

No. Message Content / Parameters Remarks<br />

1 Router Advertisement Network prefix + x Indicates HO type - see below<br />

2 Router Solicitation for Proxy NARaddr, new CoA<br />

3 H<strong>and</strong>over Initiate SubSubProfile, key, new<br />

CoA<br />

CT info for AAA as bytestream<br />

conveyed<br />

A QoS message A NAR, oCoA Indication of nAR ID, oCoA<br />

B QoS message B HoA, nCoA, DSCP in use carry NVUP (HoA, nCoA,<br />

DSCP in use)<br />

C QoS message C Configuration data, result<br />

info (comm<strong>and</strong> <strong>and</strong> DAD<br />

check result)<br />

carries configuration data for<br />

nAR or info on ResReserv<br />

failure, indication on DAD<br />

result<br />

5 H<strong>and</strong>over Acknowledge SPI<br />

6 Proxy Router Advertisement SPI<br />

7 H<strong>and</strong>over Execute (FBU)<br />

8 Start Bicasting (& Timer)<br />

9 H<strong>and</strong>over Execute ACK<br />

10 Leaving old link<br />

11 Bicasting Timer expired (Forwarding still ‘active’<br />

some more time)<br />

12 Accounting data CoA, DSCP, Time, In/Out<br />

Byte/Packet Counter<br />

13 Neighbour Advertisement<br />

X Accounting Start CoA, DSCP, Time Accounting Start requires<br />

context <strong>and</strong> is triggered on<br />

reception of 1st PDU<br />

14 Binding Update<br />

15 Binding ACK<br />

Table 1: Fast H<strong>and</strong>over Signal Flow Explanation<br />

The results here have resulted in a major step of our underst<strong>and</strong>ing: We may use Fast H<strong>and</strong>over to<br />

achieve the kind of functions in a pure IP-based environments regarding AAA <strong>and</strong> QoS that we so far<br />

only had in traditional circuit-switched networks.<br />

Driver <strong>and</strong> Wireless-LAN-cards: They are not optimised for fast h<strong>and</strong>-over. Future wireless networks<br />

will need to use the wireless LAN (802.11b) infrastructure mode to provide the kind of services that<br />

Moby Dick has prototyped. However, the available wireless LAN cards do not allow fast discovery (in<br />

infrastructure mode) of new access points while connected. In addition, the layer-2 latency was too high.<br />

For these reasons, the ad-hoc mode was chosen for the purposes of the project. The WLAN Linux driver<br />

was modified <strong>and</strong> enhanced to simulate the infrastructure mode. This solution allows the mobile terminal<br />

to receive <strong>and</strong> send data via the access point <strong>and</strong>, in the meanwhile, to process beacons advertised by<br />

other access points. The decision for h<strong>and</strong>overs is based on the signal strength of the received router<br />

advertisement. It was the common underst<strong>and</strong>ing in the project, that the ad hoc mode is a temporary<br />

solution, <strong>and</strong> that future solutions would use the infrastructure mode provided the issues mentioned<br />

above, such as layer-2 latency, as solved by the WLAN card manufacturers. It is expected that upcoming<br />

solutions, such as offered by Moby Dick, will motivate WLAN vendors to tackle these problems, which<br />

may not be relevant for the current uses of the cards. The solution could lie both in generally improving<br />

the functionality <strong>and</strong> performance of the cards, or by providing specialised WLAN cards for such<br />

purposes.<br />

MTNM: The MTNM is a prototype of what could be implemented in future multimode terminals (phones<br />

or PDAs). It h<strong>and</strong>les user preferences <strong>and</strong> interactions as well as control access technologies, including<br />

h<strong>and</strong>over management. It is also used to synchronise other functionalities on the terminal.<br />

The user interface part, the NCP, provides a set of information elements <strong>and</strong> interactions that should be<br />

implemented in a “ready to market” device. It becomes possible for the user to register on the Network<br />

<strong>and</strong> to define preferences in terms of Access Technology to use <strong>and</strong> h<strong>and</strong>over management strategy. It<br />

also provides feedback on the networking conditions (signal levels for instance) <strong>and</strong> on the ability to<br />

trigger a h<strong>and</strong>over manually if the user wants to choose the network to use.<br />

The MTNM itself is a prototype of the kind of middleware that could be embedded in a commercial<br />

terminal. It controls the network drivers for each access technology, implements a h<strong>and</strong>over algorithm to<br />

take decisions on when to perform the h<strong>and</strong>over (based on access technology conditions, but also on user<br />

Moby Dick WP6 25 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

preferences, <strong>and</strong> Quality of Service feedbacks). It interacts with all other entities on the mobile terminal<br />

(AAA registration software, paging software, in the case of Moby Dick) to synchronize all of them.<br />

4.5 Major <strong>Project</strong> Result: A4C Architecture<br />

Metering to Accounting Adaptation: USTUTT developed an interface which enables an inter-working<br />

between the enhanced, IPv6-capable RTFM-based meter to the Diameter Attendant for the final charging<br />

purpose. This includes a metering session concept, which has been implemented based on the used meter.<br />

<strong>Final</strong>ly, extensive tests have been undertaken proving the overall concept for the message flow from the<br />

Meter to the charging database.<br />

Charging: The charging process as developed by ETH calculates the price for a given service<br />

consumption based on accounting data <strong>and</strong> the SLA with all key tariff definitions. Within Moby Dick,<br />

charging supports the post paid business case <strong>and</strong> it is session-based. Within each session a user can<br />

employ services with different QoS <strong>and</strong> DSCPs <strong>and</strong> is able to roam in various domains. The tariff can be<br />

based on QoS, volume, session duration, <strong>and</strong> the domain where the service was consumed. The charging<br />

component features a convenient web interface – one for the operators <strong>and</strong> one for each customer. Users<br />

are able to login <strong>and</strong> view their accumulated charges after the provider has performed the charging<br />

process for a pre-defined period, such as a day, a month, or a week. The charges are presented in an<br />

aggregated <strong>and</strong> session-based manner, where all other details are hidden. Upon request, customers can<br />

view all accounted for charging details of each session, e.g., the consumed volume or the delivered QoS.<br />

The web interface for operators offers a login for several administration services, which customers cannot<br />

access. These include amongst others the start of the charging process for customers <strong>and</strong> sessions as well<br />

as the view of detailed customer information <strong>and</strong> their tariff definitions. Further research on prepaid <strong>and</strong><br />

content-based charging will be addressed in the Daidalos project.<br />

Auditing: Within Moby Dick the concept of SLA (Service Level Agreement) Compliance Auditing has<br />

been developed by ETH. This concept goes beyond the proposed extension of the AAAC’s server tasks of<br />

simply logging capabilities. It allows a provider to determine whether the agreed service level guarantees<br />

are being held or violated. This approach <strong>and</strong> task will have a positive impact in the future of managing<br />

SLAs among providers as well as between providers <strong>and</strong> customers. The service level guarantees of<br />

interest, which have been defined <strong>and</strong> implemented within Moby Dick, include “Entity Availability<br />

Guarantee”, “Guarantee of Successful Registration”, <strong>and</strong> “Service Request”. In order to transfer the audit<br />

trails generated by different <strong>and</strong> remote loggers to a centralized auditing instance, mainly a provider’s or a<br />

third party’s location, a logging framework has been implemented by ETH. Further research on SLA<br />

Compliance Auditing will be further carried out by ETH <strong>and</strong> partners within the Daidalos <strong>Project</strong>.<br />

Profile Decoupling of an User from the Device: Moby Dick followed the key concept of user mobility.<br />

This means in contrary to the widely deployed terminal mobility a user <strong>and</strong> the users privileges <strong>and</strong><br />

rights, which are generally reflected in a contract between user <strong>and</strong> operator, are not directly bound to a<br />

device or a SIM card inside a device as known in the 2G area. In Moby Dick any user can use any device<br />

<strong>and</strong> via a centralised profile management each user gets his individual access rights. This rights are<br />

described in the user profile <strong>and</strong> are communicated to the appropriate policy points which need the<br />

information for the service provisioning. Such a Profile concept has been designed <strong>and</strong> implemented.<br />

The AAA/Diameter framework of Moby Dick then transfers required elements of this profile to the<br />

appropriate network nodes. This implies the exchange of information also between administrative<br />

domains. Conceptually the user rights could change from administrative domain to administrative<br />

domain, however the current implementation does assume that the profile description is valid for all<br />

administrative domains involved.<br />

DIAMETER Open Source Implementation: The upcoming st<strong>and</strong>ard DIAMETER has been used for the<br />

support of AAAC functionality in this project. The use of DIAMETER in the project consolidates<br />

DIAMETER's position as the c<strong>and</strong>idate for a future st<strong>and</strong>ard. Further, DIAMETER application for<br />

Mobile IPv6 was developed. This will be used as basis for further contributions to IETF drafts <strong>and</strong> RFC.<br />

A fully functional DAIMETER based AAA infrastructure was designed <strong>and</strong> implemented in this project.<br />

The following parts of the DIAMETER implementation will be released as open source:<br />

• Server functionality including accounting<br />

• Diameter base protocol<br />

• Diameter application for MIPv6<br />

Integration of WP4 <strong>and</strong> WP: The details of this integration were fixed. The MAQ (Mobile AAA QoS)<br />

model was respected <strong>and</strong> definitely defined. User <strong>and</strong> network level management was split between WP4<br />

(user level) <strong>and</strong> WP2 (network level) <strong>and</strong> the interactions between them refined. The NVUP part of the<br />

user profile <strong>and</strong> the exact profile transfer to the various identities, including QoSB <strong>and</strong> MN (for the<br />

purposes of MN DiffServ marking software adaptation to user profile) was fixed. Also the NetServices<br />

transfer from AAAAC.f to QoSB.f was implemented<br />

Moby Dick WP6 26 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Integration of WP4 <strong>and</strong> WP3: The AAAAC context transfer when a FHO takes place was defined <strong>and</strong><br />

implemented, along with the stopping of the diameter session in the oAR <strong>and</strong> the starting of a new<br />

diameter session in the nAR.<br />

St<strong>and</strong>ards: The upcoming st<strong>and</strong>ard DIAMETER has been used for the support of AAAC functionality in<br />

this project. The use of DIAMETER in the project consolidates DIAMETER's position as the c<strong>and</strong>idate<br />

for a future st<strong>and</strong>ard.<br />

4.6 Major <strong>Project</strong> Result: IP-Paging Architecture<br />

Within the framework of the IST Moby Dick project, a concept for IP-based paging support has been<br />

specified, implemented <strong>and</strong> tested. Based on some functional <strong>and</strong> non-functional requirements, the paging<br />

architecture components as well as protocol messages <strong>and</strong> parameters have been specified in<br />

consideration of the design goals. As a result, an IP paging concept has been specified, which integrates<br />

modularly with the Mobile-IPv6 platform without being dependent on it. The concept's framework has<br />

been discussed within the Internet Engineering Task Force (IETF) <strong>and</strong> the Internet Research Task Force<br />

(IRTF).<br />

Based on the architecture <strong>and</strong> protocol concept, protocol message parameters have been specified to allow<br />

the integration <strong>and</strong> operation with the Moby Dick platform <strong>and</strong> associated access technologies<br />

(IEEE802.3, IEEE802.11 <strong>and</strong> TD-CDMA).<br />

A prototype of the paging components has been implemented, which is based on a dedicated Paging<br />

Agent node, paging attendant modules, which are to be integrated with individual Access Routers, <strong>and</strong> a<br />

paging module for the mobile terminal, which interfaces efficiently to the MTNM-module to synchronise<br />

with other functions (e.g. registration) <strong>and</strong> to retrieve access related information.<br />

Since one of the design goals was to integrate the paging architecture modularly without the need to<br />

change existing architecture <strong>and</strong> protocol components, but to make use of existing functions for the<br />

integration, the specification included the use of the Mobile-IPv6 protocol's alternate care-of-address<br />

(alt-CoA) registration. This registration support is part of the Mobile-IPv6 protocol specification, but was<br />

not available in the protocol implementation used in the Moby Dick project (implementation of Helsinki<br />

University of Technology). Hence, some parts of the Open Source Mobile-IPv6 implementation have<br />

been extended to implement the alt-CoA registration support.<br />

One function of the concept's paging attendants is to allow mapping of the technology independent<br />

paging protocol, which is used between the Paging Agent node <strong>and</strong> individual paging attendants, to<br />

technology specific paging on the access links served by individual Access Routers. Since the focus of<br />

paging related activities in Moby Dick was on the design of the framework <strong>and</strong> the common core protocol<br />

<strong>and</strong> less on technology specific paging functions <strong>and</strong> optimisation, support for integration of the Moby<br />

Dick access technologies has been specified for support on IP layer. Mapping to optimised technology<br />

specific dormant mode <strong>and</strong> paging support on access technologies' link-layer is allowed by the concept<br />

but is future work. However, efficient mapping <strong>and</strong> addressing on IP layer has been specified <strong>and</strong><br />

implemented for IEEE802.3, IEEE802.11 <strong>and</strong> TD-CDMA. Since TD-CDMA support is integrated with a<br />

Radio Gateway, which is physically separated from the respective IP-subnet's associated Access Router,<br />

operation between the paging attendant <strong>and</strong> the Radio Gateway has been specified in a generic way<br />

without introducing proprietary protocol messages for control <strong>and</strong> management purposes. This allows<br />

smooth migration to a collocated architecture in the future, which has the Access Router <strong>and</strong> the TD-<br />

CDMA Radio Gateway functions integrated in one physical node representing a TD-CDMA Access<br />

Router.<br />

Moby Dick WP6 27 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Illustration of how the paging concept integrates with the Mobile-IPv6 platform:<br />

1. Initial user-data packet(s)<br />

2. Forwarding to the explicitely registered DMA<br />

function.<br />

3. Buffering of user-data packet(s) <strong>and</strong> polling<br />

the paging attendants<br />

4. On-link paging<br />

5. Re-establishment of interface activity <strong>and</strong><br />

routing information.<br />

Figure 4: Illustration of the IP paging architecture integrated with a Mobile IPv6 environment.<br />

Paging modules: The implementation of all paging components comes with one software package. Redefinition<br />

of some default settings in dedicated source files allows control on which functionality the<br />

compiled modules should implement. This allows compilation of a Paging Agent module, a paging<br />

attendant module or the mobile terminal's paging module. All functional modules have been implemented<br />

as kernel-modules. To allow flexible configuration of the paging related settings on individual nodes, a<br />

user-space configuration <strong>and</strong> start-up framework has been implemented, which allows convenient setting<br />

of configuration parameters in a configuration file <strong>and</strong> to run a configuration script, writing the<br />

configuration data to the dynamically loaded paging kernel-module through a dedicated device-driver<br />

interface.<br />

Alternate care-of-address registration support for the Mobile-IPv6 implementation: Following the<br />

Mobile-IPv6 protocol specification, the alternate CoA registration support has been implemented as an<br />

extension to the Open Source Mobile-IPv6 implementation of Helsinki University of Technology. This<br />

had to be done because this protocol function is specified for being used for the efficient integration of the<br />

paging concept into the Mobile-IPv6 platform, but is not yet available in official releases of the Mobile-<br />

IPv6 Open Source code. The extension for alt-CoA registration support has been made available as a<br />

patch to the officially available Mobile-IPv6 release used in Moby Dick.<br />

Integration <strong>and</strong> testing: The paging support is being integrated with the Moby Dick platform. Tests have<br />

been performed with regard to a mobile terminal entering dormant mode, moving inside the registered<br />

paging area <strong>and</strong> being paged to re-establish routing states in the network infrastructure to allow routing of<br />

data packets to the current location of the reactivated mobile terminal. Tests <strong>and</strong> enhancing the<br />

functionality with regard to the support of multiple paging areas, which allows a dormant mobile terminal<br />

to scan for current paging area information <strong>and</strong> to update the registration with its Paging Agent in case of<br />

entering a new paging area while keeping the dormant state, is ongoing <strong>and</strong> continued in future work.<br />

Input to st<strong>and</strong>ards organisations: The initial concept <strong>and</strong> framework for a paging architecture has been<br />

proposed to the IETF's Seamoby Working Group, which resulted in the group's decision to take the<br />

proposed architecture as base-line for activities in st<strong>and</strong>ardizing an IP paging protocol. Since some related<br />

work items <strong>and</strong> open issues for the specification of an IP-based paging architecture <strong>and</strong> protocol have<br />

been indicated to be solved first in the research area before being st<strong>and</strong>ardized, the work has been shifted<br />

to the Internet Research Task Force (IRTF) Micro-Mobility Routing Research Group. Here, we'll<br />

continue work by means of driving the activities to get remaining technical issues resolved <strong>and</strong> providing<br />

current <strong>and</strong> future research results as input.<br />

Moby Dick WP6 28 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

5. Dissemination of results<br />

5.1 Publications<br />

"The Moby Dick <strong>Project</strong>: A Mobile Heterogeneous ALL-IP Architecture"<br />

Hans Einsiedler (T-Nova Berkom), Rui Aguiar (Instituto de Telecomunicacoes,University of Aveiro),<br />

Jüergen Jähnert (University of Stuttgart), Karl Jonas (GMD Research Centre for Information<br />

Technologies), Marco Liebsch (NEC Network Laboratories Europe), Ralf Schmitz (NEC Network<br />

Laboratories Europe), Piotr Pacyna (AGH University of Technology), Janusz Gozdecki (AGH University<br />

of Technology), Zdzislaw Papir (AGH University of Technology), Jose Ignacio Moreno (Universidad<br />

Carlos III de Madrid), Ignacio Soto (Universidad Carlos III de Madrid)<br />

Advanced Technologies, Applications <strong>and</strong> Market Strategies for 3G ATAMS 2001, Kraków, Pol<strong>and</strong>,<br />

June 17-20, 2001, ISBN 83-88309-20-X, pp. 164-171.<br />

"Authentication, Authorization, Accounting <strong>and</strong> Charging for the Mobile Internet"<br />

Hasan (Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of Technology ETH<br />

Zürich), Jürgen Jähnert (University of Stuttgart), Sebastian Z<strong>and</strong>er (GMD Fokus), Burkhard Stiller<br />

(Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of Technology ETH Zürich)<br />

IST Mobile Communications Summit 2001, Barcelona, Spain, September 9-12, 2001, pp. 923-928.<br />

"Mobility Support for a Future Communication Architecture"<br />

Hans Einsiedler (T-Nova Berkom), Karl Jonas (GMD Research Centre for Information Technologies),<br />

Jürgen Jähnert (University of Stuttgart), Ralf Schmitz (NEC Network Laboratories Europe), Marco<br />

Liebsch (NEC Network Laboratories Europe)<br />

IST Mobile Communications Summit 2001, Barcelona, Spain, September 9-12, 2001, pp. xx-xx.<br />

"Enabling IP QoS in Mobile Environments"<br />

Victor Marques (PT Invocao), Rui Aguiar (Instituto de Telecomunicacoes,University of Aveiro),<br />

Francisco Fontes (PT Invocao), Juergen Jaehnert (University of Stuttgart), Hans Einsiedler (T-Nova<br />

Berkom)<br />

IST Mobile Communications Summit 2001, Barcelona, Spain, September 9-12, 2001, pp. 300-305.<br />

Slides<br />

"An Heterogeneous Mobile IP QoS-aware Network"<br />

Victor Marques (PT Invocao), Rui Aguiar (Instituto de Telecomunicacoes,University of Aveiro), Jürgen<br />

Jähnert (University of Stuttgart), Karl Jonas (GMD Research Centre for Information Technologies),<br />

Marco Liebsch (NEC Network Laboratories Europe), Hans Einsiedler (T-Nova Berkom), Francisco<br />

Fontes (PT Invocao)<br />

Quarta Conferencia sobre Redes de Computadores - CRC'01, Covilha, Portugal, November 29-30, 2001.<br />

Slides<br />

"The Design of an Extended AAAC Architecture"<br />

Hasan (Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of Technology ETH<br />

Zürich), Davinder Singh, Sebastian Z<strong>and</strong>er (GMD Fokus), Moritz Kulbach (T-Nova Berkom), Jürgen<br />

Jähnert (University of Stuttgart), Burkhard Stiller (Computer Engineering <strong>and</strong> Network Laboratory<br />

TIK,Swiss Federal Institute of Technology ETH Zürich)<br />

IST Mobile & Wireless Telecommunications Summit 2002, Thessaloniki, Greece, June 17-19, 2002, pp.<br />

36-40.<br />

"A MIPv6, FMIPv6 <strong>and</strong> HMIPv6 h<strong>and</strong>over latency study: analytical approach"<br />

Hannes Hartenstein (NEC Network Laboratories Europe), Marco Liebsch (NEC Network Laboratories<br />

Europe), Xavier Péréz Costa (NEC Network Laboratories Europe), Ralf Schmitz (NEC Network<br />

Laboratories Europe)<br />

IST Mobile & Wireless Telecommunications Summit 2002, Thessaloniki, Greece, June 17-19, 2002, pp.<br />

100-105.<br />

"An architecture supporting end-to-end QoS with user mobility for systems beyond 3rd<br />

generation"<br />

Moby Dick WP6 29 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Victor Marques (PT Invocao), Rui Aguiar (Instituto de Telecomunicacoes,University of Aveiro), Piotr<br />

Pacyna (AGH Technical University), Janusz Gozdecki (AGH Technical University), Christophe Beaujean<br />

(Motorola Networking <strong>and</strong> Applications Lab), Nesrine Chaher (Motorola Networking <strong>and</strong> Applications<br />

Lab), Carlos García (Universidad Carlos III de Madrid), José Ignacio Moreno (Universidad Carlos III de<br />

Madrid), Hans Einsiedler (T-Nova Berkom)<br />

IST Mobile & Wireless Telecommunications Summit 2002, Thessaloniki, Greece, June 17-19, 2002, pp.<br />

858-862.<br />

"Diffserv como solución a la provisión de QoS en Internet"<br />

Jorge Escribano (Universidad Carlos III de Madrid), Carlos García (Universidad Carlos III de Madrid) ,<br />

José Ignacio Moreno (Universidad Carlos III de Madrid), Celia Sedas (Universidad Carlos III de Madrid)<br />

II Congreso Iberoamericano de Telemática CITA'2002, Mérida, Venezuela, 11-13 September 2002, ISBN<br />

980-237-217-X<br />

"Solutions for IPv6-based mobility in the EU project Moby Dick"<br />

Marco Liebsch (NEC Network Laboratories Europe), Xavier Pérez Costa (NEC Network Laboratories<br />

Europe), Ralf Schmitz (NEC Network Laboratories Europe), Amardeo Sarma (NEC Network<br />

Laboratories Europe), Jürgen Jähnert (University of Stuttgart), Serge Tessier (T-Nova Berkom), Michelle<br />

Wetterwald (EURECOM), Ignacio Soto (Universidad Carlos III de Madrid)<br />

World Teletraffic Congress, Paris, France, September 26th, 2002.<br />

"Avoiding DAD for Improving Real-Time Communication in MIPv6 Environments"<br />

Marcelo Bagnulo (Universidad Carlos III de Madrid), Ignacio Soto (Universidad Carlos III de Madrid),<br />

Alberto García-Martinez (Universidad Carlos III de Madrid), Arturo Azcorra (Universidad Carlos III de<br />

Madrid)<br />

Joint International Workshop on Interactive Distributed Multimedia Systems/Protocols for Multimedia<br />

Systems IDMS-PROMS 2002, Coimbra, Portugal, November 26-29, 2002.<br />

"Los pilares de las redes 4G: QoS, AAA y Movilidad"<br />

Antonio Cuevas Casado (Universidad Carlos III de Madrid), Carlos García (Universidad Carlos III de<br />

Madrid), José Ignacio Moreno (Universidad Carlos III de Madrid), Ignacio Soto (Universidad Carlos III<br />

de Madrid)<br />

TelecomI+D 2002, Madrid, Spain, November 19th, 2002.<br />

"Armonización de direcciones en entornos de VoIP mediante ENUM"<br />

M. Carmen Bartolomé (Universidad Carlos III de Madrid), Raquel Panadero (Universidad Carlos III de<br />

Madrid), José Ignacio Moreno (Universidad Carlos III de Madrid), David Fernández (Universidad<br />

Politécnica de Madrid)<br />

Jornadas Telecom I+D 2002, Madrid, Spain, November 19-21, 2002.<br />

"Delay Bounds for a Network of Guaranteed Rate Servers with FIFO Aggregation"<br />

Yuming Jiang (Institute for Communications Research)<br />

Computer Networks, Elsevier Science, Vol. 40, No. 6, pp. 683-694, 2002.<br />

"Impact of FIFO Aggregation on Delay Performance of a Differentiated Services Network"<br />

Yuming Jiang (Institute for Communications Research), Qi Yao (Institute for Communications Research)<br />

The International Conference on Information Networking ICOIN 2003, Jeju Isl<strong>and</strong>, Korea, February 12-<br />

14, 2003.<br />

"A Simple QoS service provision framework for beyond 3rd generation scenarios"<br />

Victor Marques (Portugal Telecom Inovacao), Rui L. Aguiar (University of Aveiro/Instituto de<br />

Telecomunicacoes) , Antonio Cuevas Casado (Universidad Carlos III de Madrid),José Ignacio Moreno<br />

(Universidad Carlos III de Madrid), Nesrine Chaher (Motorola Labs)<br />

10th International Conference on Telecommunications ICT'2003, Papeete, French Polynesia, February<br />

23-28, 2003.<br />

"An IP QoS architecture for 4G networks"<br />

Janusz Gozdecki (AGH University of Technology), Piotr Pacyna (AGH University of Technology),<br />

Victor Marques (Portugal Telecom Inovaçao), Rui L. Aguiar (Instituto de<br />

Telecomunicacoes/Universidade de Aveiro), Carlos Garcia (Universidad Carlos III de Madrid), Jose<br />

Moby Dick WP6 30 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Ignacio Moreno (Universidad Carlos III de Madrid), Christophe Beaujean (Motorola Labs), Eric Melin<br />

(Motorola Labs), Marco Liebsch (NEC Laboratories)<br />

Architectures for Quality of Service in the Internet Art-QoS 2003 <strong>and</strong> <strong>Final</strong> Aquila IST seminar, Warsaw,<br />

Pol<strong>and</strong>, March 24-25, 2003, pp. 9-20.<br />

Proceedings also in: W.Burakowski, B.Koch <strong>and</strong> A.Beben (eds.): Architectures for Quality of Service in<br />

the Internet, Springer-Verlag, LNCS Series, volume No 2698, 2003<br />

"QoS Provisioning for VoIP Traffic by Deploying Admission Control"<br />

Hung Tuan Tran (Telecommunications Research Center, FTW), Thomas Ziegler (Telecommunications<br />

Research Center, FTW), Fabio Ricciato (University of Rome "La Sapienza")<br />

Architectures for Quality of Service in the Internet Art-QoS 2003 <strong>and</strong> <strong>Final</strong> Aquila IST seminar, Warsaw,<br />

Pol<strong>and</strong>, March 24-25, 2003.<br />

"Simulation Study of IEEE 802.11e EDCF"<br />

He Dajiang (Institute for Communications Research), Charles Shen (Institute for Communications<br />

Research)<br />

The 57th Semiannual Vehicular Technology Conference VTC 2003-Spring, Jeju, Korea, April 22-25,<br />

2003.<br />

"Design <strong>and</strong> <strong>Evaluation</strong> of a H<strong>and</strong>over Decision Strategy for 4th Generation Mobile Networks"<br />

Wenhui Zhang (University of Stuttgart), Juergen Jaehnert (University of Stuttgart), Klaus Dolzer<br />

(University of Stuttgart)<br />

The 57th Semiannual Vehicular Technology Conference VTC 2003-Spring, Jeju, Korea, April 22-25,<br />

2003.<br />

Slides<br />

"Quality of Service in IP networks"<br />

Janusz Gozdecki (AGH University of Science <strong>and</strong> Technology), Rafal Stankiewicz (AGH University of<br />

Science <strong>and</strong> Technology)<br />

Workshop on Multimedia Communications <strong>and</strong> Services MCS'03, Kielce, Pol<strong>and</strong>, 23-25 April, 2003.<br />

"A Performance study of Hierarchical Mobile IPv6 from a System Perspective"<br />

Xavier Pérez Costa (NEC), Marc Torrent-Moreno (NEC)<br />

International Conference on Communications, ICC 2003, Anchorage, AK, USA, 11-15 May, 2003.<br />

"Implementation <strong>and</strong> <strong>Evaluation</strong> of an End-to-End IP QoS Architecture for Networks Beyond 3rd<br />

Generation"<br />

Christophe Beaujean (Motorola Labs), Nesrine Chaher (Motorola Labs), Victor Marques (Portugal<br />

Telecom) , Rui L. Aguiar (Instituto de Telecomunicacoes/Universidade de Aveiro), Carlos García<br />

(Universidad Carlos III de Madrid), José Ignacio Moreno (Universidad Carlos III de Madrid), Michelle<br />

Wetterwald (Eurecom), Thomas Ziegler (Telecommunications Research Center, FTW)<br />

IST Mobile <strong>and</strong> Wireless Communications Summit, Aveiro, Portugal, 15-18 June, 2003.<br />

"Auditing Architecture for SLA Violation Detection in QoS-Supporting Mobile Internet"<br />

Hasan (Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of Technology ETH<br />

Zürich), Burkhard Stiller (Computer Engineering <strong>and</strong> Network Laboratory TIK, Swiss Federal Institute of<br />

Technology ETH Zürich <strong>and</strong> Information Systems Laboratory IIS, University of the Federal Armed<br />

Forces Munich)<br />

IST Mobile <strong>and</strong> Wireless Communications Summit, Aveiro, Portugal, 15-18 June, 2003 Vol. 1, pp. 241-<br />

245.<br />

"Modeling of WLAN Beacon Signal Strength Measured in an Indoor Environment"<br />

Wenhui Zhang (University of Stuttgart)<br />

The 2003 International Conference on Wireless Networks ICWN'03, June 23th - 26th, 2003, Las Vegas,<br />

Nevada, USA.<br />

"An Analytical RED Function Design Guaranteeing Stable System Behaviour" - pre-final version<br />

Erich Plasser (Telecommunications Research Center, FTW), Thomas Ziegler<br />

The Eighth Symposium on Computers <strong>and</strong> Communications ISCC 2003, Kemer-Antalya, Turkey, June<br />

30 - July 3, 2003.<br />

Moby Dick WP6 31 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

"Engineering Solution of a CAC Mechanism for Voice Traffic over IP Networks"<br />

H.T. Tran (FTW), T. Ziegler (FTW)<br />

6th IEEE International Conference on High Speed Networks <strong>and</strong> Multimedia Communications,<br />

HSNMC'03, Estoril, Portugal, July 23-25, 2003.<br />

"Explicit Loss Notification to improve TCP Performance over Wireless Networks"<br />

G. Buchholcz (FTW), A. Gricser (FTW), T. Ziegler (FTW), Tien V. Do (FTW)<br />

6th IEEE International Conference on High Speed Networks <strong>and</strong> Multimedia Communications,<br />

HSNMC'03, Estoril, Portugal, July 23-25, 2003.<br />

"Mechanisms for AAA <strong>and</strong> QoS Interaction"<br />

Antonio Cuevas (Universidad Carlos III de Madrid), José Ignacio Moreno (Universidad Carlos III de<br />

Madrid), Rui Aguiar (University of Aveiro), Victor Marques (Portugal Telecom), Carlos García<br />

(Universidad Carlos III de Madrid), Ignacio Soto (Universidad Carlos III de Madrid)<br />

3rd Workshop on Application <strong>and</strong> Services in Wireless Networks, Bern, Switzerl<strong>and</strong>, July 2003, ISBN: 3-<br />

9522719-0-X.<br />

"Providing Throughput Guarantees in IEEE 802.11e Wireless LANs"<br />

Xavier Pérez-Costa (NEC Network Laboratories Europe)<br />

18th International Teletraffic Congress ITC, Berlin, Germany, August 31 - September 5, 2003.<br />

"Cost-efficient Metering <strong>and</strong> Accounting in 4G Networks"<br />

Juergen Jaehnert (University of Stuttgart)<br />

ITC 2003, Berlin, 31st August - 5th September 2003.<br />

"A Simulation Study on the Performance of Mobile IPv6"<br />

Xavier Pérez-Costa (NEC Network Laboratories Europe), M. Torrent-Moreno, Hannes Hartenstein (NEC<br />

Network Laboratories Europe)<br />

18th International Teletraffic Congress ITC, Berlin, Germany, August 31 - September 5, 2003.<br />

"QoS en Redes Móviles de Cuarta Generación"<br />

Carlos García (Universidad Carlos III de Madrid), Pedro Antonio Vico (Universidad Carlos III de<br />

Madrid), Antonio Cuevas (Universidad Carlos III de Madrid), Ignacio Soto (Universidad Carlos III de<br />

Madrid), Jose Ignacio Moreno (Universidad Carlos III de Madrid)<br />

IV Jornadas de Ingenieria Telemática JITEL 2003, ISBN: 84-96131-38-6, Gran Canaria, 15-17<br />

September 2003.<br />

"Problem Statement: Metering <strong>and</strong> Accounting in the full-IP 4G environment"<br />

Juergen Jaehnert (University of Stuttgart)<br />

Third International Workshop on Internet Charging <strong>and</strong> QoS Technology ICQT 2003, Munich,<br />

September 16-19, 2003.<br />

"MobyDick FlowVis Using NeTraMet for distributed protocol analysis in a 4G network<br />

environment"<br />

Nevil Brownlee (University of Stuttgart), Paul Christ (University of Stuttgart), Juergen Jaehnert<br />

(University of Stuttgart), Yongzhen Liang (University of Stuttgart), Krishna Srinivasan (University of<br />

Stuttgart), Jie Zhou (University of Stuttgart)<br />

2003 IEEE Workshop on IP Operations <strong>and</strong> Management (IPOM 2003), Kansas City, Missouri, USA,<br />

October 1-3 2003.<br />

"Open Source Experimental B3G Networks Based on Software-Radio Technology"<br />

C. Bonnett (Institute Eurecom), H. Callewaert (Institute Eurecom), L. Gauthier (Institute Eurecom), R.<br />

Knopp (Institute Eurecom), A. Menouni (Institute Eurecom), Y. Moret (Institute Eurecom), Y. Moret<br />

(Institute Eurecom), D. Nussbaum (Institute Eurecom), I. Racunica (Institute Eurecom), M. Wetterwald<br />

(Institute Eurecom)<br />

Software Digital Radio SDR'03 conference, November 19-23, 2003, Orl<strong>and</strong>o, USA<br />

Slides<br />

Moby Dick WP6 32 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

"A Performance Study of Fast H<strong>and</strong>overs for Mobile IPv6"<br />

Marc Torrent-Moreno (NEC), Xavier Pérez Costa (NEC), Sebastian Sallent-Ribes (NEC)<br />

to appear in LCN, 2003.<br />

"Second-chance Auctions for Multimedia Session Pricing"<br />

Peter Reichl (FTW), S. Bessler (FTW), Burkhard Stiller (Computer Engineering <strong>and</strong> Network Laboratory<br />

TIK, Swiss Federal Institute of Technology ETH Zürich <strong>and</strong> Information Systems Laboratory IIS,<br />

University of the Federal Armed Forces Munich)<br />

International Workshop on Multimedia Interactive Protocols <strong>and</strong> Systems MIPS 2003, Naples, Italy, 18-<br />

21 November 2003.<br />

"Moby Dick - Mobility And differentiated Services In A Future IP Network"<br />

Hans J. Einsiedler (T-Systems), supported by P. Pacyna (AGH) <strong>and</strong> Jüergen Jähnert (University of<br />

Stuttgart)<br />

Book: who is who in mobile solutions 1.0, page 92-93, whois verlags- & vertriebsgesellschaft, ISBN 3-<br />

934013-30-9<br />

"A generic IP Paging Architecture <strong>and</strong> Protocol"<br />

Marco Liebsch (NEC Network Labs Europe), Bernd Lamparter (NEC Network Labs Europe)<br />

Accepted for publication at European Wireless Conference 2004, Barcelona, February 24 - 27, 2004.<br />

"Interworking Security in Heterogeneous Wireless IP Networks"<br />

Wenhui Zhang (University of Stuttgart)<br />

Accepted for publication at 3rd International Conference on Networking (ICN'04), February 29 - March<br />

4, 2004, Guadeloupe, French Caribbean.<br />

"H<strong>and</strong>over Decision Using Fuzzy MADM in Heterogeneous Networks"<br />

Wenhui Zhang (University of Stuttgart)<br />

Accepted for publication at IEEE Wireless Communications <strong>and</strong> Networking Conference 2004 (WCNC<br />

2004), 21-25 March 2004, Atlanta, USA.<br />

5.2 Presentations<br />

"Mobility <strong>and</strong> Differentiated Services in a Future IP Network"<br />

Hans Einsiedler (T-Nova Berkom)<br />

Presentation at Key Action Line IV Concertation meeting, Brussels, Belgium, March 13-14, 2001.<br />

"How does the Internet Will Survive the Mobility Shock"<br />

Paul Christ (University of Stuttgart), Jürgen Jähnert (University of Stuttgart)<br />

Presentation at MAIN workshop, T-Nova, Berlin, Germany, April 26th, 2001.<br />

"Authentication, Authorization, Accounting, <strong>and</strong> Charging for an IPv6-enabled Internet"<br />

Burkhard Stiller (Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of<br />

Technology ETH Zürich)<br />

Presentation at "Deploying IPv6 Networks" event, Paris, France, November 22-23, 2001.<br />

"The WCDMA platform"<br />

Institut EURECOM <strong>and</strong> Deutsche Telekom<br />

Demonstration at IST Mobile Communications Summit 2001, Düsseldorf, Germany, December 3-5,<br />

2001.<br />

"Mobility <strong>and</strong> Differentiated Services in a Future IP Network"<br />

Hans Einsiedler (T-Nova Berkom)<br />

Demonstration at WINEGLASS workshop, Turin, Italy, January 24-25, 2002.<br />

"The Moby Dick project"<br />

Hong-Yon Lach (Motorola Networking <strong>and</strong> Applications Lab)<br />

Presentation at IPv6 cluster meeting, Madrid, Spain, March 12th, 2002.<br />

"DMHA Design Issues & Framework Discussion"<br />

Marco Liebsch (NEC Network Laboratories Europe)<br />

Moby Dick WP6 33 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Presentation in IETF Seamoby WG, March xx, 2002. URL:<br />

http://www.ietf.org/proceedings/02mar/slides/seamoby-1/index.html<br />

"The Moby Dick project"<br />

Hong-Yon Lach (Motorola Networking <strong>and</strong> Applications Lab)<br />

Presentation <strong>and</strong> chairing the System beyond 3G cluster meeting, Brussels, Belgium, April 10th, 2002.<br />

"The WCDMA platform"<br />

Institut EURECOM <strong>and</strong> Deutsche Telekom<br />

Presentation during FIFA drawing event, Frankfurt, Germany, April 15th, 2002.<br />

"Mobile Access to Internet Services - Architecture <strong>and</strong> Protocols"<br />

Burkhard Stiller (Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of<br />

Technology ETH Zürich)<br />

Presentation in FTW <strong>and</strong> in Technical University of Vienna, Vienna, Austria, May 2nd, 2002<br />

"The Moby Dick project"<br />

Christian Bonnet (EURECOM)<br />

Presentation at Telecom Paris, Paris, France, May xx, 2002.<br />

"IP mobility applied to UMTS "<br />

Yan Moret (EURECOM)<br />

Presentation at Workshop on IP Mobility, France Telecom R&D, Rennes, France, June 6th, 2002.<br />

"New Architecture for 3G (<strong>and</strong> beyond) Systems"<br />

Christian Bonnet (EURECOM)<br />

Presentation at Philips-Ceram Workshop, Sophia-Antipolis, France, June xx, 2002.<br />

"New Architecture for 3G (<strong>and</strong> beyond) Systems"<br />

Christian Bonnet (EURECOM)<br />

Presentation at Lucent Workshop, Sophia-Antipolis, France, June 2002.<br />

"The Design of an Extended AAAC Architecture"<br />

Hans Einsiedler<br />

IST Mobile & Wireless Telecommunications Summit 2002, Thessaloniki, Greece, June 17-19, 2002.<br />

"A MIPv6, FMIPv6 <strong>and</strong> HMIPv6 h<strong>and</strong>over latency study: analytical approach"<br />

Xavier Perez Costa<br />

IST Mobile & Wireless Telecommunications Summit 2002, Thessaloniki, Greece, June 17-19, 2002.<br />

"An architecture supporting end-to-end QoS with user mobility for systems beyond 3rd<br />

generation"<br />

Victor Marques<br />

IST Mobile & Wireless Telecommunications Summit 2002, Thessaloniki, Greece, June 17-19, 2002.<br />

Raymond Knopp (EURECOM)<br />

Presented Moby Dick at The Second European Colloquium on Reconfigurable Radio, Athens, Greece,<br />

June 20-22, 2002.<br />

"IP Paging & RRG Related Issues"<br />

Marco Liebsch (NEC Network Laboratories Europe)<br />

Presentation in IRTF Routing Research Group, IETF #54, Japan, July xx, 2002.<br />

"The IST Moby Dick project - Overview <strong>and</strong> RRG related work"<br />

Marco Liebsch (NEC Network Laboratories Europe)<br />

Presentation in IRTF Routing Research Group, IETF #54, Japan, July 15, 2002.<br />

"Moby Dick's IETF Activities IP-Paging <strong>and</strong> R<strong>and</strong>om Generation of Address Identifiers"<br />

Hans Einsiedler (T-Nova Berkom)<br />

Presentation at Systems beyond 3G Cluster meeting, Brussels, Belgium, September 11, 2002.<br />

Moby Dick WP6 34 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

"Solutions for IPv6-based mobility in the EU project Moby Dick"<br />

Amardeo Sarma (NEC)<br />

presentation at "the 18th World Telecommunications Congress - WTC 2002" event, Paris, France, 26<br />

September 2002.<br />

"Premium IP: On the Road to Ambient Networking"<br />

Rui Aguiar (Instituto de Telecomunicacoes,University of Aveiro)<br />

Presentation at a panel discussion during the QofIS'02/ICQT'02 , the "Quality of future Internet Services"<br />

<strong>and</strong> "Internet Charging <strong>and</strong> QoS Technologies" conference, Zurich, Switzersl<strong>and</strong>, October 17th, 2002.<br />

"Mobility-enabled QoS for IPv6-based Beyond-3G networking"<br />

Christophe Beaujean (Motorola)<br />

Presentation during 6th Hitachi-Eurecom-Motorola Symposium, Nice, 28th November 2002.<br />

"Lehrstuhl für Netzwerktechnologien und multimediale Teledienste"<br />

Hans Joahim Einsiedler (T-Systems)<br />

Presentation <strong>and</strong> a lecture, University of Potsdam/Germany, 28th May 2003.<br />

"PLATON: PLATe-forme pour les Nouvelles générations de communications mobiles"<br />

Christian Bonnet (Institut Eurécom)<br />

Presentation. Institut Eurécom, Sophia-Antipolis, 2nd July, 2003, France<br />

"PLATON: PLATe-forme pour les Nouvelles generations de communications mobiles"<br />

Michelle Wetterwald (Institut Eurécom)<br />

2nd July, 2003, Eurécom, Sophia-Antipolis, France.<br />

"IST Mobile Summit"<br />

Victor Marques, Rui L. Aguiar, (Portugal Telekom / University of Aveiro)<br />

<strong>Project</strong> presentation <strong>and</strong> demonstration during IST Mobile & Wireless Telecommunications Summit,<br />

Aveiro, Portugal, 15-18 June, 2003.<br />

"Moby Dick Summit in Stuttgart"<br />

Hans Joachim Einsiedler (T-Systems, Deutsche Telekom)<br />

<strong>Project</strong> presentation during Moby Dick 2nd International <strong>Project</strong> Summit, 16.05.2003.<br />

"Moby Dick"<br />

Jürgen Jähnert (University of Stuttgart)<br />

Presentation during Moby Dick 3rd International <strong>Project</strong> Summit, 6.11.2003.<br />

"Moby Dick: Mobility <strong>and</strong> Differentiated Services in a Future IP Network"<br />

Hans Joachim Einsiedler (T-Systems, Deutsche Telekom)<br />

Presentation during The Third International IST Workshop on Terrestrial Wireless Systems <strong>and</strong> Networks<br />

December 16-17, 2003, Singapore.<br />

"Wireless 3G For Free: A UMTS Software Radio Platform"<br />

Michelle Wetterwald (Institut Eurécom)<br />

Presentation during The Third International IST Workshop on Terrestrial Wireless Systems <strong>and</strong> Networks<br />

December 16-17, 2003, Singapore.<br />

5.3 Journals<br />

"Signalling in Voice over IP Networks"<br />

José Ignacio Moreno (Universidad Carlos III de Madrid), Ignacio Soto Campos (Universidad Carlos III<br />

de Madrid), David Larrabeiti (Universidad Carlos III de Madrid)<br />

Informatik/Informatique, Magazine of the Swiss Informatics Society, Vol. 3, 2001, ISSN 1420-6579, pp.<br />

xx-xx, NOVATICA, No. 151, May/June 2001, ISSN: 0211-2124, pp. xx-xx,<br />

The European Online Magazine for the Information Technologies Professional Council of European<br />

Professional Informatics Societies, June 2001, http://www.upgrade-cepis.org<br />

Moby Dick WP6 35 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

"An All-IP software radio architecture under RT-Linux"<br />

Christian Bonnet (EURECOM), Lionel Gauthier (EURECOM), Pierre Humblet (EURECOM), Raymond<br />

Knopp (EURECOM), Aawatif Menouni-Hayar (EURECOM), Yan Moret (EURECOM), Aless<strong>and</strong>ro<br />

Nordio (EURECOM), Dominique Nussbaum (EURECOM), Michelle Wetterwald (EURECOM)<br />

Annales des Telecommunications, Vol. 57, N°7-8, July-August 2002.<br />

"A Simulation Study on the Performance of Mobile IPv6 in a WLAN-Based Cellular Network"<br />

Xavier Péréz Costa (NEC Network Laboratories Europe), Hannes Hartenstein (NEC Network<br />

Laboratories Europe)<br />

Computer Networks Special Issue on The New Internet Architecture, August 2002, pp. 191-204.<br />

"Towards a new Internet Architecture"<br />

Augusto Casca (INESC), A. Sarma (NEC Network Laboratories Europe)<br />

Editorial, Computer Networks Special Issue on The New Internet Architecture, August 2002, pp. 1-4.<br />

"An IP-based QoS architecture for 4G operator scenarios"<br />

Victor Marques (Portugal Telecom Inovacao), Rui L. Aguiar (University of Aveiro/Instituto de<br />

Telecomunicacoes), Carlos Garcia (Universidad Carlos III de Madrid), Jose Ignacio Moreno (Universidad<br />

Carlos III de Madrid), Christophe Beaujean (Motorola Labs Paris), Eric Melin (Motorola Labs Paris),<br />

Marco Liebsh (NEC Network Laboratories Europe)<br />

Special Issue of IEEE Wireless Communications magazine, xxx 2003, pp. xx-xx.<br />

5.4 Technical <strong>Report</strong>s<br />

"A Survey on AAA Mechanisms, Protocols, <strong>and</strong> Architectures <strong>and</strong> a Policy-based Approach<br />

beyond: A power x"<br />

Christoph Rensing (Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of<br />

Technology ETH Zürich), Hasan (Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal<br />

Institute of Technology ETH Zürich), Martin Karsten (Computer Engineering <strong>and</strong> Network Laboratory<br />

TIK,Swiss Federal Institute of Technology ETH Zürich), Burkhard Stiller (Computer Engineering <strong>and</strong><br />

Network Laboratory TIK,Swiss Federal Institute of Technology ETH Zürich)<br />

TIK <strong>Report</strong> Nr. 111, ETH, Zürich, Switzerl<strong>and</strong>, May 2001.<br />

"Authentication, Authorization, Accounting, <strong>and</strong> Charging for the Mobile Internet"<br />

Hasan (Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of Technology ETH<br />

Zürich), Jürgen Jähnert (University of Stuttgart), Sebastian Z<strong>and</strong>er(GMD Fokus), Burkhard Stiller<br />

(Computer Engineering <strong>and</strong> Network Laboratory TIK,Swiss Federal Institute of Technology ETH Zürich)<br />

TIK <strong>Report</strong> Nr. 114, ETH, Zürich, Switzerl<strong>and</strong>, June 2001.<br />

"IPv6 activities of the "Systems beyond 3G" cluster."<br />

Hong Yon LACH, IST Systems beyond 3G cluster, July 2002.<br />

5.5 St<strong>and</strong>ardisation<br />

"Paging Concept for IP based Networks"<br />

Marco Liebsch (NEC Network Laboratories Europe), Gerrit Renker (NEC Network Laboratories Europe),<br />

Ralf Schmitz (NEC Network Laboratories Europe)<br />

Internet draft, draft-renker-paging-ipv6-01.txt, September 2001.<br />

"R<strong>and</strong>om generation of interface identifiers"<br />

Marcelo Bagnulo (Universidad Carlos III de Madrid), Ignacio Soto (Universidad Carlos III de Madrid),<br />

Alberto García-Martínez (Universidad Carlos III de Madrid), Arturo Azcorra (Universidad Carlos III de<br />

Madrid)<br />

Internet draft, draft-soto-mobileip-r<strong>and</strong>om-iids-00.txt, January 2002.<br />

"Cell-Search List Indications for Seamless Anticipative, Resource-Mindful H<strong>and</strong>overs"<br />

R. Jayaraj (ICR, NUS)<br />

Internet draft, May 2002.<br />

"Architecture <strong>and</strong> Protocol framework for Dormant Mode Host Alerting"<br />

Marco Liebsch (NEC Network Laboratories Europe), Yoshihiro Ohba, Tao Zhang editors<br />

Internet draft, draft-liebsch-dmha-framework-00.txt, September 2002.<br />

Moby Dick WP6 36 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

"Policy-Based Accounting"<br />

T. Zseby (Fraunhofer FOKUS), Sebastian Z<strong>and</strong>er (Fraunhofer FOKUS), Georg Carle (Fraunhofer<br />

FOKUS)<br />

Internet RFC, October 2002.<br />

"Context Transfer <strong>and</strong> Fast Mobile IPv6 Interactions in a Layer-2 Source-Triggered Anticipative<br />

H<strong>and</strong>over"<br />

R.J.Jayabal (Institute for Infocomm Research I2R, A-STAR)<br />

Internet draft, March 2003.<br />

"C<strong>and</strong>idate Access Router Discovery"<br />

M. Liebsch (NEC), A. Singh (Motorola) - editors, H. Chaskar (Nokia), D. Funato (NTT DoCoMo USA),<br />

E. Shim (NEC)<br />

Internet draft, September 2003.<br />

5.6 Thesis<br />

"Simulative Performance Optimization of TCP over UMTS"<br />

Marcel Lötscher Masters Thesis at ETH Zurich, March 2003.<br />

5.7 Press, Interviews, Broadcast, <strong>and</strong> Interviews<br />

• TV interview by the project manager for the "Westdeutscher Rundfunk/Computer Club" <strong>and</strong> its<br />

broadcast,15th December 2001. Video stream.<br />

• Article in a Stuttart University newspaper, Pressmitteilung 26/2003, 9th May 2003.<br />

• Article in idw-online , 12th May 2003.<br />

• Article in Yahoo Germany News, 13th May 2003.<br />

• Moby Dick interview by University of Stuttgart, EURECOM <strong>and</strong> Deutsche Telekom regarding<br />

The Second Moby Dick Summit, German radio broadcast by Deutschl<strong>and</strong>funk, 17.05.2003<br />

afternoon.<br />

• Moby Dick interview by University of Stuttgart regarding The Second Moby Dick Summit",<br />

German radio broadcast by Bayern 5, 25th May 2003 at 13:30.<br />

• TV News from Mobile Summit 2003, June 2003.<br />

• NEC announces a successful demo, November 2003.<br />

• Internationales Presse Colloquiuum with Moby Dick demonstration, 28-29 January 2003.<br />

Moby Dick WP6 37 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

5.8 Moby Dick Summits<br />

First Moby Dick International <strong>Project</strong> Summit in Madrid 2002<br />

The second audit took place together with an summit in Madrid. People from industry <strong>and</strong> academia in<br />

the European framework visited the summit.<br />

Presentations from FP5 project were given with Moby Dick presentations.<br />

Participants from academia: circa 40<br />

Participants from industry: circa 20<br />

Number of Moby Dick presentations including mobility, QoS, AAA, TD-CDMAdemonstration:<br />

5<br />

URL:<br />

http://www.it.uc3m.es/mobydick/<br />

Moby Dick WP6 38 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Second Moby Dick International <strong>Project</strong> Summit <strong>and</strong> Trial Kick-off in Stuttgart 2003<br />

The trial kick-off event took place together with a summit in Stuttgart. People from industry <strong>and</strong><br />

academia in the European framework visited the summit.<br />

Presentations from Daimler Chrysler <strong>and</strong> the University of Stuttgart were given.<br />

Participants from academia: 35<br />

Participants from industry: 35<br />

Number of Moby Dick presentations including integrated Moby Dick <strong>and</strong> 6WinIT,<br />

TD-CDMA-demonstration: 3<br />

URL: http://www-ks.rus.uni-stuttgart.de/Events/030516_MobyDick-Summit/index.html<br />

Moby Dick WP6 39 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

Third Moby Dick International <strong>Project</strong> Summit in Stuttgart 2003<br />

The final audit took place together with a summit in Stuttgart. People from industry <strong>and</strong> academia in the<br />

European framework visited the summit.<br />

Overview: Presentation in the morning from closing FP5-project such as Moby Dick <strong>and</strong> in the afternoon<br />

from new starting Integrated <strong>Project</strong> were given.<br />

Participants from academia: 30<br />

Participants from industry: 20<br />

Number of Moby Dick presentations <strong>and</strong> the final demonstration of the Moby Dick<br />

architecture: 1<br />

URL: http://www-ks.rus.uni-stuttgart.de/Events/031106_MobyDick-Summit/index.html<br />

Moby Dick WP6 40 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

International Summit in Singapore 2003<br />

People from industry <strong>and</strong> academia in the Asian framework visited the summit. Presentations from Japan,<br />

South-Korea, <strong>and</strong> Taiwan were given.<br />

Overview: Technical presentations from Asia <strong>and</strong> from the FP5 (6WinIT, MIND, OverDrive) were given.<br />

Participants from academia: 50<br />

Participants from industry: 25<br />

Moby Dick presentation including the Stuttgart demonstration movie: 1<br />

URL:<br />

http://www.i2r.a-star.edu.sg/mobydick/<br />

Moby Dick WP6 41 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

5.9 Moby Dick Web-Site<br />

The project set-up from the beginning a Web-page with its own domain identifier (ist-mobydick.org). All<br />

public activities were updated regularly here – including the public deliverables.<br />

URL:<br />

http://www.ist-mobydick.org/<br />

Moby Dick WP6 42 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

6. Conclusion, Self Assessment, <strong>and</strong> Lessons Learnt<br />

General:<br />

Moby Dick had set itself the ambitious goal of pioneering the integration of mobility, QoS, <strong>and</strong> AAAC in<br />

the spirit of the Internet within a single framework, thereby integrating heterogeneous wired, wireless,<br />

<strong>and</strong> mobile technologies. Within this context Moby Dick considered both, inter-domain <strong>and</strong> intra-domain<br />

scenarios. The project further aimed to implement a demonstrator where this integration will be<br />

experimented with real users. The project has been progressing at an adequate rate, <strong>and</strong> has been able to<br />

draw increasingly the attention of the general research community. The increased interactions with IETF<br />

<strong>and</strong> IRTF, the proactive role inside IST – within the Systems Beyond 3G cluster.<br />

The project participated in several conferences within Europe <strong>and</strong> organised four Moby Dick summits in<br />

Madrid, Stuttgart <strong>and</strong> Singapore. Interviews in radio broadcast as well as newspaper articles visualised<br />

the project results. The partner from Singapore ensured also visibility in the Asian area.<br />

Technical Achievements:<br />

With the variety of independent activities in the mobility, QoS, <strong>and</strong> AAAC areas, as well as the different<br />

technical requirements of shared medium technologies such as 802.x <strong>and</strong> Ethernet on the one h<strong>and</strong> <strong>and</strong><br />

TD-CDMA on the other, initial efforts were directed towards resolving conceptual <strong>and</strong> technological<br />

differences. Intense discussions finally resulted in harmonising the “traditional” connection-oriented<br />

approach of TD-CDMA <strong>and</strong> the packet-based, connectionless Internet approach.<br />

The independent activities were bundled in the integration phase to an integrated solution.<br />

It successfully proved its visibility in Europe by several public presentations, public demonstrations <strong>and</strong><br />

publications. So the project has achieved a high degree of international visibility – also outside Europe.<br />

The business units of the involved partners have taken a strong interest in the results of the project.<br />

The project has been able to resolve a number of difficult issues:<br />

• A common, agreed architecture for the Mobile Terminal <strong>and</strong> the companion piece, the radio<br />

gateway, which is directly attached to the access router.<br />

• Redefinition <strong>and</strong> agreement on important scenarios, e.g. for registration, seamless h<strong>and</strong>-over for<br />

intra domain h<strong>and</strong>-over <strong>and</strong> Mobile IPv6 for inter-domain h<strong>and</strong>over because of the delay for<br />

AAA <strong>and</strong> QoS messaging.<br />

• Definition of exemplary QoS classes based on the Differentiated Services approach to<br />

demonstrate the flexibility of the architecture with respect to services which will be supported.<br />

• Implementations for registration, intra-domain h<strong>and</strong>-over based on the seamless h<strong>and</strong>-over<br />

approach, inter-domain h<strong>and</strong>-over based on Mobile IPv6 including automatic registration, QoS<br />

Broker messaging, AAAC in including Auditing messaging, control <strong>and</strong> visualisation for the<br />

user as well for the operator of the billing information, IP paging on a basic strategy (database<br />

without any intelligence for the paging area identification).<br />

• The integration of all implementations was a huge challenge since the places of development<br />

were distributed over whole Europe <strong>and</strong> Singapore. However, it was successfully solved for<br />

most components.<br />

• Establish a good visibility <strong>and</strong> accepted expertise in the area of IP paging st<strong>and</strong>ardisation via<br />

partner P02 (NEC).<br />

In contrast to the original plans of the project, a full integration of TD-CDMA could not be achieved due<br />

to delays in the implementation of related hardware <strong>and</strong> software. While IP-based connectivity <strong>and</strong><br />

mobility management were integrated, the QoS modules <strong>and</strong> the AAA functionality is not (yet) part of the<br />

TD-CDMA set-up.<br />

Security <strong>and</strong> privacy have been identified as very important open issues. These were not addressed in the<br />

project proposal <strong>and</strong> we relayed on existing open source implementations. The IP security infrastructure<br />

is not applicable for a mobile operator architecture.<br />

Time Schedule:<br />

The integration as well as the trial suffered on a huge delay since not all implementations could be<br />

finished in the time schedule. As already mentioned, the fact that the development of the modules was<br />

distributed over several locations, some delay were produced since partners had to travel for debugging to<br />

the trial sites, especially to Stuttgart/Germany. Some delay for the TD-CDMA-equipment occurred<br />

because of missing hardware components from third parties.<br />

Moby Dick WP6 43 / 44


WP6-D0603 Version 1.0 February 17, 2004<br />

However, the integration was completed successfully but delayed, with some impacts to the real user trial,<br />

which had to be shorter than expected.<br />

Lessons Learnt:<br />

The integration of different modules, although accounted for with manpower <strong>and</strong> time in the original<br />

project proposal, turned out to be a real challenge. This was taken into account in the specification of a<br />

successful follow-up project proposal (IP DAIDALOS in FP6), where integration will be considered as a<br />

major requirement from the beginning, <strong>and</strong> even more resources will be spent on this aspect.<br />

Moby Dick WP6 44 / 44

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!