MobileMAN Meeting
Helsinki (8 June 2004)
Marco Conti
Computer Networks Dept., IIT CNR
Marco.conti@iit.cnr.it
http://cnd.iit.cnr.it/mobileMAN
Meeting Objectives
To Analyze the Deliverables production
To verify the status of the implementations
To plan the experiments
To define methods and tools for Interactions with users and
plan tests with users
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverables status
Deliverables list
Del.
no.
D6
D7
D8
D9
D10
D11
Deliver able name
WP
no.
Lead
participant
Estimated
personmonths
Del. type*
Security
**
MobileMAN functionalities
3 Already
CNR delivered
18
Prototype
Š a minimal set
Socio-economic research
2
SUPSI-DLS
9
Report
Already
delivered (March
2004)
methodology
4
CNR
25
MobileMAN first phase
Report
MobileMAN intermediate
1
SUPSI-DIE
6
Report
To
be
addressed
starting
from
Sept.
1st
evaluation report
2
EURECOM
8
MobileMAN architecture,
Report
protocols, and services
intermediate report
MobileMAN functionalities
Š enhanced set
3
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
HUT
40
Prototype
Deliver
y
(proj.
month)
Pub
13
Pub
18
Pub.
Pub
22
24
Pub
24
Pub
25
D8: Integration and Experimentation
•
D8 is an output of WP 4: This WP will integrate the HW/SW
developed (…) Qualitative study of the social and
anthropological consequences of the utilization of the system.
•
T4 .1 Small Area Scale Integration: Integrate part of the HW/SW developed (reduced
networking and services capabilities), and install it in each node in a small and test this
system in order to identify HW or simple networking problems and integration errors. Fix
problems/errors found verifying that the system operates correctly. (input to D8 - month
22 (July 2004) All
•
T4 .2 Small Area Scale Validation and Analysis: Validate the small scale MobileMAN from
a technical (i.e., the technical constraints and limitations of the system), and social
standpoint. The latter will be performed by measuring the acceptance -- from Virtual
Communities (VCs) of users -- of the MobileMAN system when running some simple
application(s). This will task will also monitor the social construction and human
behaviour of the VCs. (input to D8 - month 22), (D17 - month 34 ) All
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
D11: MobileMAN functionalities –
enhanced set
•
D11: HUT is responsible for this deliverable (month 25)
•
D11 is an output of WP 3:
T3.2 Implementation of Location Protocols: Develop new location and
discovery protocols based on the nearness metric. Implementation of it for the
Linux operating system. (input to D6, D11, D14)
Service discovery embeeded in the routing protocol instead of
users’ location
T3.3 Routing and forwarding: Develop routing and forwarding protocols for the
self-organised
and
co-operative
communications
of
MobileMAN.
Implementation of them for the Linux operating system, in co-operation with
the task on security (T3.4). (input to D6, D11, D14)
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
D11: MobileMAN functionalities –
enhanced set
T3.4 Security and Co-operation Model: Implementation of the collaborative
reputation mechanism (CORE) proposed to solve ad hoc node misbehaviour.
Implementation of the CORE mechanism for the Linux operating system, in
co-operation with the task dedicated to the definition and implementation of
the routing algorithm adopted by MobileMAN (T3.3). (input to D11, D14)
T3.5 P2P delivery mechanisms: Implementation of the P2P mechanisms
designed in Task T2.6. (input to D11, D14)
T3.6 Risk reduction in the system development: This task will be activated, if
required, by the self assessment procedure to tackle the risks emerging
during the implementation of the system solutions. The objective of this task is
the identification of alternative solutions for implementing the system solutions
when adopted approaches are too complex and risky. (input to D11, D12,
D14
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
D8 (and D11): Actions
Proposal: An experimental trial to be setup in Pisa
involving junior researchers from all partners
This group of people should have continuous exchanges via e-mails, chat,
etc, and meet regularly (from now to the end of the project) to verify the
status of software implementation and integration
•
Why?
i.
ii.
•
•
•
When?
•
Construct a small MobileMAN (D8) now and to work toward a larger
testbed;
To address software integration, fix problems in existing software, better
coordinate ongoing software development activities etc….. (D8 & D11)
End June - First week of July in Pisa
Who is involved ? (at least 1-2 junior researchers for each partner)
•
•
•
•
•
•
CNR (about 6 Ph.d students + possibly master students as users)
Eurecom (Pietro and Claudio ?)
Cambridge (Ziran Sun?)
HUT ( ???)
SUPSI - (Claudia Brazzola?)
NetiKos (Veronica Vanni)
Pisa Trial Coordinators: Eleonora Borgia & Franca Delmastro
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
D8 (and D11): Actions
•
Aspects to be investigated
•
Technical aspects
• Routing framework (AODV, OLSR).
• Middleware (Pastry)
• Application Layer (UDDI?)
• Cooperation (at least watchdog ????)
•
•
•
Social aspects
• Students’ involvement
A second meeting can be organized in the period September - October
depending on the project status
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10:
D5 extension/refinement
•
D10 is an output of WP 2: MobileMAN architecture, protocols, and
services intermediate report
•
Input from WP 2:
•
T2.8 Economic driven modelling: (input to D5, D10, D13)
•
T2.9 Domain model refinement and risk reduction: (input to D10,
D13)
•
Eurecom is responsible for this deliverable
•
Proposed schedule:
•
•
•
•
Now: preliminary table of contents
By end June: refined table of contents
By end July: release 1 (full draft)
By September 10: final version
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10: Table of Contents
Tentative Table of contents - Section 1
D5
1.MOBILEMAN ARCHITECTURE
7
1.1.
Interconnection to the Internet
1.2.
Design Methods and Tools 14
1.3.
References17
12
D10
1.MOBILEMAN ARCHITECTURE
(CNR)
1.1.
Legacy Architecture (All)
1.2.
Cross Layer Architecture (CNR + Cambridge)
1.2.1.
Nest
1.2.2.
Synchronous/Asynchronous interaction
1.3.
References
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10: Table of Contents
Tentative Table of contents - Section 2
D5
2. WIRELESS TECHNOLOGIES 19
2.1. IEEE 802.11 Architecture and Protocols 21
2.2. Analysis of 802.11 performance
27
2.3. IEEE 802.11b Measurements
34
2.5. Burtsy MAC definition 48
2.5.1.
Asymptotically Optimal Backoff (AOB) Mechanism
2.5.2.
AOB Performance Analysis
54
2.6. Enhanced card novel mechanisms
58
2.6.1.
State-of-the-art investigation
58
2.6.2.
Choice of an hardware medium-access platform for
MobileMAN
58
2.6.3.
The medium-access level software architecture
2.7. References 61
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
51
59
Deliverbale D10: Table of Contents
Tentative Table of contents - Section 2
D10
WIRELESS TECHNOLOGIES
2.1. Integration of AoB and IEEE 802.11 (CNR)
2.2. IEEE 802.11 & AoB Analysis with realistic channel
model (CNR)
2.3. Refinement of the AoB mechanism (CNR)
2.4. Enhanced card novel architecture & mechanisms
(SUPSI-DIE)
2.5.References
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10: Table of Contents
Table of contents D5 - Section 3
D5
3. NETWORKING
63
3.1.
Nodes’ Location
63
3.1.1. Location Services in MobileMAN 64
3.2.
Routing 66
3.2.1. Unicast Routing Protocols 67
3.2.2. A Testbed for Experimenting MANET IETF
and Novel Routing protocols 68
3.2.3. Routing in a cross layering
architecture 73
3.3.
Reliable Forwarding
74
3.4.
Transport protocol
77
3.5.
References
82
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10: Table of Contents
Tentative Table of contents - Section 3
D10
w 3. NETWORKING
w 3.1. Services Location
(HUT + CNR)
3.2.
Routing
3.2.1.
A Testbed for Experimenting MANET IETF
and Novel Routing protocols
(HUT)
3.2.2.
Routing in a cross layering
architecture: HSLS (CNR)
3.3.
Reliable Forwarding (CNR)
3.4.
References
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10: Table of Contents
Tentative Table of contents - Section 4
D5
4.SECURITY AND CO-OPERATION MODEL AND MECHANISMS85
4.1.
Secure Routing 85
4.1.1. State of the art
86
4.1.2. Secure routing in MobileMan
93
4.2.
Co-operation Mechanisms 93
4.2.1. State of the art
94
4.2.2. Co-operation in MobileMan95
4.3.
Authentication and Key Management 95
4.3.1. State of the art
96
4.4.
MANET and Data Link Layer Security 98
4.5.
References100
D10
Eurecom (see review meeting)
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10: Table of Contents
Tentative Table of contents - Section 5
D5
5. MIDDLEWARE
102
5.1.
P2P information delivery 103
5.1.1.
A Brief History
105
5.1.2.
Applications 111
5.1.3.
Properties and Issues
116
5.2.
Collaboration and Trust
117
5.2.1.
Future Directions 121
5.2.2.
Conclusion
124
5.3.
Analysis of existing middleware 125
D10
5. MIDDLEWARE
5.1.
CrossRoad: Pastry & Cross Layering (CNR + Cambridge?)
5.2.
Bamboo ??? (Cambridge)
5.3.
???????
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10: Table of Contents
Tentative Table of contents - Section 6
D5
6. APPLICATIONS
132
6.1.
Status of the Art
132
6.2.
Scenarios 132
6.3.
Content Sharing Application 133
6.3.1.
Technical Aspects
133
6.3.2.
Social and Economical Aspects
6.4.
References 134
134
D10
APPLICATIONS
6.1.
Netikos Activity on UDDI
6.2.
HUT real time audio
6.3.
Users’ evaluation of application usefulness
6.4.
References
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Deliverbale D10: Table of Contents
Tentative Table of contents - Section 7
D5
7. ECONOMIC ISSUES 135
7.1.
Introduction of Approach: Promoting
Cooperation
135
7.2.
System Description 135
7.3.
Simulations
136
7.4.
Conclusions
143
7.5.
References144
D10
7. ECONOMIC MODELS
n
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Cambridge
Other Issues
II year review meeting
Proposal to be in Lugano (Switzerland)
end September - beginning of October ?
Motivation: hardware platform demo
Other motivation: other demos
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
Milestones
M6 Month 16: Preliminary definition of the overall MobileMAN domain
model to be used as input for WP 3 and WP 4. Meeting with the
Industrial Advisory Board to present and discuss the MobileMAN
domain model.
M8 – Month 16: Preliminary version of the basic set of
MobileMAN functionalities.
First Check on the status of the
implementation of all MobileMAN components;
M10 – Month 20: Preliminary version of a small scale MobileMAN
M12 – Month 24: Analysis of the MobileMAN dissemination activities
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
II Year WPs and Tasks
The main activities are in the framework of
WP3 and WP 4:
Tasks temporal diagram
T5.3
WP 5
T5.2
T5.1
T4.6
T4.5
T4.4
WP 4
IMPLEMENTATION AND INTEGRATION AND
SOCIAL STUDY
T4.3
T4.2
WP 3 Objectives: to implement the
MobileMAN innovative components at
networking and service layer of the
architecture as defined by WP2.
T4.1
T3.6
T3.5
T3.4
T3.3
WP 3
T3.2
T3.1
T2.9
T2.8
WP 4 Objectives: This WP will integrate the
HW/SW developed (…) Qualitative study of the
social and anthropological consequences of
T2.7
T2.6
T2.5
.0 2
WP
T2.4
T2.3
T2.2
T2.1
the utilization of the system.
0.0
T1.5
T1.4
T1.3
WP 1
T1.2
T1.1
T2.7 Socio-economic modelling:
T0.4
T0.3
WP 0
T2.8 Economic driven modelling:
T0.2
T0.1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
Projet month
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
T2.9 Domain model refinement and risk reduction:
T5.1 Dissemination:
WP 3
Objectives: The aim of this WP is to implement the MobileMAN innovative
components at networking and service layer of the architecture as defined by WP2.
Description of work: The innovative elements of the networking architecture of
MobileMAN consist of the MAC, Routing and Location components. At service level
the main components is the security one. The work to be done regarding these
components includes all the phases of the HW/SW development lifecycle, from
requirements analysis to testing (verification testing).
T3.1 Bursty-responsive MAC Develop new MAC protocol and hardware supporting
bursty communication. The hardware will be based, wherever possible, on a off-theshelf 802.11 chipset whit ad-hoc programmed firmware. (input to D12) - SUPSI DIE
T3.2 Implementation of Location Protocols: Develop new location and discovery
protocols based on the nearness metric. Implementation of it for the Linux operating
system. (input to D6, D11, D14) - CNR & HUT
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
WP 3 (cont.)
T3.3 Routing and forwarding: Develop routing and forwarding protocols for the selforganised and co-operative communications of MobileMAN. Implementation of them
for the Linux operating system, in co-operation with the task on security (T3.4).
(input to D6, D11, D14) HUT & CNR
T3.4 Security and Co-operation Model: Implementation of the collaborative
reputation mechanism (CORE) proposed to solve ad hoc node misbehaviour.
Implementation of the CORE mechanism for the Linux operating system, in cooperation with the task dedicated to the definition and implementation of the routing
algorithm adopted by MobileMAN (T3.3). (input to D11, D14) Eurecom
T3.5 P2P delivery mechanisms: Implementation of the P2P mechanisms designed in
Task T2.6. (input to D11, D14) Cambridge
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
WP 4
Description of work: Given the high challenges of this WP, the main tasks to be performed in it
(integration and acceptance) will be addressed at two different area scales: campus-wide area
scale (T4 .2 and T4 .3) and large area scale (T4 .4 and T4 .5).
T4 .1 Small Area Scale Integration: Integrate part of the HW/SW developed (reduced networking
and services capabilities), and install it in each node in a small and test this system in order to
identify HW or simple networking problems and integration errors. Fix problems/errors found
verifying that the system operates correctly. (input to D8 - month 22) All
T4 .2 Small Area Scale Validation and Analysis: Validate the small scale MobileMAN from a
technical (i.e., the technical constraints and limitations of the system), and social standpoint. The
latter will be performed by measuring the acceptance -- from Virtual Communities (VCs) of users -of the MobileMAN system when running some simple application(s). This will task will also monitor
the social construction and human behaviour of the VCs. (input to D8 - month 22), (D17 - month
34 ) All
T4.3 Evaluation of MobileMAN Networking: Simulative study of the integration of MobileMAN
Networking components with other relevant elements as the connection to Internet, as well as
congestion control and error recovery mechanisms to optimise the utilization of the resources.
(input to D16 - month 34) HUT, CNR, Eurecom
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
II Year Activities
•
The objectives reported below are the detailed criteria for evaluating the
success of the second year of the project.
MobileMAN architecture implementation (CNR)
-
Implementation and validation of the MobileMAN architecture as defined during the first year
(see D5) considering both the original and the new reference model.
New applications and services (Netikos)
-
Adaptation of existing applications (or classes of applications) identified, during the first year,
as ones that can become a customer advantage, when run on top of MobileMAN, compared to
traditional technologies.
Middleware (Cambridge)
-
Adaptation of Pastry middleware for the MobileMAN environment to exploit cross layering.
-
Development of new solutions for P2P information delivery based on Pastry.
Co-operation Model (Eurecom)
-
Implementation and validation of the cooperation models and mechanisms defined during the
first year.
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
II Year Activities (cont.)
Networking services (CNR, HUT)
-
Include the cross-layering view at network/transport layer
-
Design of packet forwarding schemes suitable for MobileMAN.
-
Implementation and validation of location scheme defined during the first year.
-
Development and testing of a complete ad hoc network
Wireless Technologies (SUPSI - DIE)
-
Include the cross-layering view at datalink layer.
-
Design and implement a full datalink layer that includes the enhanced MAC protocol for ad hoc
networks as designed during the first year.
Socio-economic Model (SUPSI - DLS)
-
Apply the developed methodology for evaluating social, anthropological, and economic potential of
MobileMAN, and provide the results for improving the technical parts.
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)
II Year Success Criteria
The goals for evaluating the success of the second year of the project are:
- The software implementation of the solutions defined and studied during the first year,
except the MobileMAN enhanced NIC.
- The integration of the developed solutions in a fully functioning testbed.
- Preliminary measures of the users’ satisfaction of the ad hoc networking paradigm.
These measures will be mainly done by empirical research based on forms to be filled.
In addition, some measurements with a small group of users (on a simplified testbed)
will be also performed.
- To investigate market-based mechanisms for exploiting the self-organised paradigm.
This will take into account both the users’ satisfaction and the advantages provided by
the MobileMAN environment to some class of applications.
Agenda - MobileMAN meeting (Helsinki, 8 June, 2004)