Dario Bottazzi
IS-MANET Meeting—Bologna
Enabling Collaborative Enabling Collaborative Applications in MANETsApplications in MANETs
21st July 2004
Bologna — 21.07.2004
OutlineOutline
Group Membership and Group Communication Requirements and Solutions in MANETs The AGAPE Framework
– Group Membership– Group Communication
Case Study and Results Evaluation Conclusions & Future Work
Bologna — 21.07.2004
New New Opportunities for Impromptu Opportunities for Impromptu Collaboration in MANETsCollaboration in MANETs
New MANET scenario– proliferation wireless-enabled portable devices– recent advances in MANET technology
User requirement– Traditional services (www, e-mail,…)– Innovative Collaborative Applications
– Emergency Response– Automotive – Games …
Bologna — 21.07.2004
Impromptu CollaborationImpromptu Collaboration
Proximity-Based: co-located group members are likely to operate more often than with the others. Location-based: the members of the group access available services and resources. Impromptu: collaboration require no prior planning Transient: interactions are short-lived
A Group is a set of co-located autonomous entities that can communicate, collaborate with each other. All members agree on group activities, tasks and goals.
Group Collaboration is:
Bologna — 21.07.2004
New Challenges in Collaborative New Challenges in Collaborative Applications Applications
Highly dynamic Nature of Ad-Hoc Groups– Device Mobility, Run-Time Join-Leave…– Impromptu Nature of Collaboration Activities– Collaboration Between Previously Unknown Partners
Highly Dynamic Nature of MANETs– Frequent Host Connections and Disconnections– Frequent Network Partitions
Heterogeneous Characteristics of Group Members– Resource scarcity
Bologna — 21.07.2004
Group Membership & Group Membership & CommunicationCommunication
Traditional Group Membership and Communication Solutions
– ISIS, Horus, Transis, JGroup, …– View-oriented
– Aim to provide members a commonly agreed perception of the composition of the group.
– Relevant computational resources– Suppose the availability of high bandwidth reliable multicast and total ordered communication channels
Bologna — 21.07.2004
Recent Research EffortsRecent Research Efforts Global Virtual Data Space-Based Systems (GVDS)
– LIME, PeerWare, Xmiddle, TOTA– GVDS aim to coordinating–Transiently shared data space that is partitioned between collaborating entities– Group membership and communication coupled to the data space
Profile-Based Collaboration Systems– Proem– At regular times each entity broadcasts its profile– Application provided with the visibility of neighbors’ profiles–Group membership relies on the implementation of the same application-level protocols
Bologna — 21.07.2004
The AGAPE FrameworkThe AGAPE FrameworkALLOCATION AND GROUP-AWARE PERVASIVE ENVIRONMENTS
Context-Aware Group Membership and Communication Middleware
– Users have direct visibility of only locally available set of group members and characteristics (Context-dependent View)
AGAPE Groups– Each group is characterized by a group unique identifier and by a group profile (commonly agreed interests, preferences, activities and goals)– The set of members that compose a group is not a-priori determined, but can dynamically change– Two entity roles: the Managed Entity (ME) and the Locality Manager Entity (LME)
Bologna — 21.07.2004
AGAPE LocalityAGAPE Locality
MANET
LME 1LME 3ME 1
ME 2
ME 3
ME 4
ME 5ME 6
ME 7ME 8
LME 2 ME 10
Locality3Locality2
Loca
lity1
ME 9
Bologna — 21.07.2004
Communication ModelCommunication Model Communication Pattern
– Context-Based Any-Cast/Multi-Cast – Profile– Binding Strategy (Early/Late Binding Strategy)– Designation Criteria (only for Context-Based Any-cast)
Message Scheduling Message Presentation
Bologna — 21.07.2004
Context-Based Any-CastContext-Based Any-Cast
ME 1
ME 2
ME 3
ME 4
ME 5
ME 9
ME 7
ME 8LME 1 ME 6
Locality1
ME1 ME2 ME3 ME4 ME6 LME1
Profile
Designation Criteria
Choice
Bologna — 21.07.2004
ArchitectureArchitecture
JVM-OS-HW-Network
PENS PS NMS
J/LMS VMS BCKS
CS BS MSS
Application
MPS
AG
AP
E
Group Mangement Layer
Group Communication Layer
NMS: Network Manager Service PS: Proximity Service PENS: Proximity Enabled Naming Service
BCKS: Backup Service VMS: View Manager Service J/MS: Join/Leave Manager Service
CS: Communication Service
BS: Binding Service MPS: Message Presentation Service MSS: Message Scheduler Service
Bologna — 21.07.2004
Case Study–Emergency ResponseCase Study–Emergency Response
The application aggregates together firemen working within the same area,
– provides firemen with the visibility of the colleagues – allows firemen to communicate instructions or images via messages exchanges.
Firemen interoperate via a IEEE 802.11b-based MANET with AODV routing protocol and statically configured IP addresses.
Bologna — 21.07.2004
Case Study–Emergency ResponseCase Study–Emergency Response Devices
– Firemen of high rank: lap-tops, Fedora Linux, J2SE 1.4 and the AGAPE release for resource rich devices. – Firemen of low rank: iPAQ PDAs, Linux Familiar, Personal Java and the AGAPE release for resource constrained devices.
CC/PP-compliant profiles– Firemen profiles firemen’s name and rank. – Device profiles – Group profiles identify the goals of the fire brigade community.
Bologna — 21.07.2004
MANET Tom, FirefighterBob, Engineer
Joe, Captain
Nick, Firefighter Sam, Firefighter
LME 1
ME 2
ME 3
ME 4
Locality1
Locality (h=2)ME 1
Case StudyCase Study
Join
Bologna — 21.07.2004
Case StudyCase Study
MANET Tom, FirefighterBob, Engineer
Joe, Captain
Nick, Firefighter Sam, Firefighter
LME 1
ME 2
ME 3
ME 4
Locality1
Locality (h=2)ME 1
Bologna — 21.07.2004
PreliminaryPreliminary ResultsResults
1 hop
LME1
ME1
ME1
ME1
ME1
MEn
Nme: 1..19 PDAs
Tb: 5, 10, 15, 20, 25 [sec]
Tv: 20, 40, 60, 80, 100 [sec]
0
2000
4000
6000
8000
10000
12000
14000
16000
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Tb=5
Tb=10
Tb=15Tb=20Tb=25
Nme A
bp
s
beacon dissemination
0
10000
20000
30000
40000
50000
60000
70000
80000
90000
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
Tv=20
Tv=40
Tv=60Tv=80
Tv=100
Nme B
bp
s
beacon dissemination
Nme PDAs
Bologna — 21.07.2004
Ordinary Operating ConditionsOrdinary Operating Conditions
0
500
1000
1500
2000
2500
3000
3500
4000
4500
1 2 3 4 5 6 7 8 9 10 11 12 13 140
5000
10000
15000
20000
25000
30000
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Tb=5
Tb=10
Tb=15Tb=20Tb=25
Tv=20
Tv=40
Tv=60Tv=80
Tv=100
N2hopsN2hops C D
bp
s
bp
s
beacon dissemination View dissemination
N2hops: 1..14
Tb: 5, 10, 15, 20, 25 [sec]
Tv: 20, 40, 60, 80, 100 [sec]LME1
ME1
ME4
ME2
ME3
ME5 ME6
ME7
ME9
ME8
ME105 PDAs
N2hops PDAs
1 hop
2 hop
Bologna — 21.07.2004
ConclusionsConclusions
The MANET scenario calls for re-thinking group membership and group communication solutions
AGAPE Group Management – Context-aware group membership management
solution suitable for MANETs. AGAPE Communication
– Context-aware group communication solution that permits to deliver messages, to tailor their format and to schedule their presentation order on the basis of context information.
Bologna — 21.07.2004
ThanksThanks
Questions?
Bologna — 21.07.2004
Group PromotionGroup Promotion
Application J/LMS BCKS PENS PS NMSVMS
Promote a Group
Request of GID/PID
Return GID/PID
Advertise Group
Setup Group View
Send Beacon
Send Beacon
Send Beacon
Generate GID/PID
Outcoming Message
Outcoming Message
Outcoming Message
Bologna — 21.07.2004
View DisseminationView DisseminationBCKS PENS NMSVMS
Request of the List of Co-Located Entities
Return the List of Co-Located Entities
Request of Permission
Return Permission
Send Group View
Receive Beacon
Receive Beacon
Receive Context-Dependent View
Incoming Message
Incoming Message
Incoming Message
Outcoming Message
Bologna — 21.07.2004
JoiningJoiningApplication J/LMS PENS PS NMSVMS
Receive Beacon
Receive Group Acknowledge
Start Sending Beacons
Receive Group View
Request to Join a Group
Incoming Message
Incoming Message
Outcoming Message
Incoming Message
Outcoming MessageSetup
Group Views
Request of the List of Co-Located LMEs
Return of the List of Co-Located LMEs
Request to Join a Group
Bologna — 21.07.2004
Any-Cast CommunicationAny-Cast CommunicationApplication CS BS VMS
Message Transcoding Request
Handler Request
View Request
HandlerReturn
Binding Entry
Request
Binding Reference
Return
Binding Setup
Send Message Find Message
Recipient
Return Message Recipient
View Return
MPMS MSS
View Request
View Return
User/Device Profile
Request
User/Device Profile Return
Possibly Message
Transcoding
Message Scheduling
Request
Possibly Message
Delay
Outcoming Message
Bologna — 21.07.2004
Receive MessageReceive MessageMSS MPMS CS Application
Incoming Message
Possibly Message
Transcoding
Message Request
Message Return
Message Transcoding
Request
VMS
User/Device Profile
Request
Possibly Message
Delay
User/Device Profile Return
Message Delivery