How To Leap For Ad-Hoc Networks

Abstract

This document is intended to provide an overview of the effort to enable the Lightweight
Extensible Agent Platform (LEAP) to operate in ad-hoc networks. I discuss the motivations
behind this project, the usage scenarios and finally the required modifications to LEAP. With
this document I wish to inform the members of the LEAP, JADE, and FIPA communities
about my research plans and solicit any feedback they may wish to offer.

Approach

The approach taken by this project is to integrate existing peer-to-peer (P2P), service
discovery and ad-hoc networking technologies into the LEAP platform to provide a robust
infrastructure for deploying agents within an ad-hoc network.
Ad-hoc networks are the subject of current research into future generation networks but like
most new technologies the term is often misused and misunderstood.

Requirements

• Removal of AMS, DF and Main container as mandatory requirements for hosting agents
• Discovery of fragments
• Dynamic formation of fragments into compounds and associated strategies
• Dynamic creation of directory services within fragments and associated strategies
• Leased directory entries to ensure consistency over time
• Active updates to the directory services as agents join and leave the network
• Directory subscription mechanism to enable fragments to receive notifications
• JADE API compatibility from the agent developers viewpoint

Download PDF: LEAP for Ad-hoc Networks.pdf (286.3 KB)

Happy learning!

2 Likes