Context-Aware Group Management Middleware to Support Resource Sharing in MANET Environments

1. Context-Aware Group Management Middleware to Support Resource Sharing in MANET Environments MDM 2005 — Ayia Napa, Cyprus Dario Bottazzi dbottazzi@deis.unibo.it 12thMay 2005

2. Outline • Group Membership Requirements and Solutions in Mobile Ad-Hoc Scenarios • The AGAPE Framework • Group Membership Management Model • AGAPE Architecture • Case Study • Conclusions & Future Work

3. Group Collaboration Characteristics in MANETs • Proximity-Based: co-located group members are likely to operate moreoften than with the others. The members of the group can accessonly to locally available services and resources. • Impromptu: collaboration require no prior planning • Transient: interactions are short-lived

4. New Challenges in Collaborative 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

5. Recent Research Efforts • Global Virtual Data Space-Based Systems (GVDS) • LIME, PeerWare, XMiddle • 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, Konark • 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

6. The AGAPE Framework • 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 • Set of autonomous entities that can communicate, collaborate with each other. All members agree on group activities, tasks and goals. • Each group is characterized by a group unique identifier and by a group profile (commonly agreed interests, preferences, activities and goals) • Two entity roles: the Managed Entity (ME) and the Locality Manager Entity (LME)

7. AGAPE Locality Locality2 ME 2 Locality3 Locality1 ME 4 ME 7 LME 2 ME 10 ME 8 ME 1 LME 3 LME 1 ME 5 ME 6 ME 9 ME 3 MANET

8. Architecture J/MS: Join/Leave Manager Service VMS: View Manager Service VCS: View Controller Service PENS: Proximity Enabled Naming Service PS: Proximity Service NMS: Network Manager Service Application Group Management Layer J/LMS VMS VMS AGAPE Basic Service Layer PENS PS NMS JVM-OS-HW-Network

9. Case Study view view view ME 2 LME 1 Locality1 ME 1 Locality (h=2) Joe, Captain ME 3 Nick, Firefighter MANET Bob, Engineer Tom, Firefighter Nick, Firefighter

10. Case Study view view view view ME 2 LME 2 LME 1 Locality1 ME 1 Locality (h=2) Joe, Captain Joe, Captain ME 3 Nick, Firefighter Nick, Firefighter Harry, Lieutenant MANET Bob, Engineer Tom, Firefighter

11. Case Study view view view ME 2 LME 2 Locality1 ME 1 Locality (h=2) ME 3 Nick, Firefighter Nick, Firefighter Harry, Lieutenant MANET Bob, Engineer Tom, Firefighter

12. Experimental Results Energy consumption for advertisement and group view dissemination.

13. Conclusions & Future Works • Group Management • We have presented AGAPE, a context-aware group membership management solution tailored to MANET environments • AGAPE provides the full visibility of co-located group members along with user attribute and device characteristics • Future directions • Introduce a security support for AGAPE • Improve the initial group communication support we are implementing

14. Thanks Questions?