Generating routing table for free roaming mobile agent in distributed environment

  • Authors:
  • S. Venkatesan;C. Chellappan

  • Affiliations:
  • Department of Computer Science and Engineering, Anna University, Chennai, India;Department of Computer Science and Engineering, Anna University, Chennai, India

  • Venue:
  • Computer Standards & Interfaces
  • Year:
  • 2009

Quantified Score

Hi-index 0.00

Visualization

Abstract

Free roaming mobile agent [D. Xu, L. Harn, M. Narasimhan, J. Luo. ''An Improved Free-Roaming Mobile Agent Security Protocol against Colluded Truncation Attacks.'' In Proceedings of the 30th Annual international Computer Software and Applications Conference(COMPSAC,06), Volume 2, Page(s):309-314,Chigago, Sept. 2006, IEEE Computer Society Press.; S. Venkatesan, C. Chellappan, ''Protecting free roaming mobile agent against multiple colluded truncation attacks'', In proceedings of the 3rd International conference on Mobile Multimedia Communication (Mobimedia'07), page(s): 293-297, August 2007.] is to collect information from more number of remote host using the shortest route. The routing table available in the router is not applicable for the free roaming mobile agent to roam around the network, so each and every server must have the routing information. This paper proposes a model to generate the routing table for the free roaming mobile agent to roam around the network by calculating the link cost between the nodes. Link cost between the servers is measured by the energy consumed to reach the destination. Link cost is measured by the transmission of agent instead of sending the message because here the route is calculated for agent roaming. The cost for transferring the message and the agent differs because of the migration and transfer. In agent transmission, the whole thing will be migrated to the remote host. But in the message transmission, the particular message is transmitted. Routing table in the destination will be generated automatically by the mobile agent while it visits the destination host and the routing table of the source host will be generated after the agent returns to its home (source host).