Improved Hierarchical Location Management Schemes To Locate Mobile Agents in Multi Agents Environment

IPASJ International Journal of Computer Science (IIJCS)
Web Site: http://www.ipasj.org/IIJCS/IIJCS.htm

Email: editoriijcs@ipasj.org
ISSN 2321-5992
A Publisher for Research Motivation ........
Volume 2, Issue 10, October 2014
Improved Hierarchical Location Management

Schemes to Locate Mobile Agents in Multi
Agents Environment
Swati Aggarwal1, Dr. Heman Pathak2
1
Research Scholar, Department of Computer Science, GKV Haridwar

2
Associate Professor, Department of Computer Science,

Kanya Gurukul campus, Dehradun
ABSTRACT
Location Management and its communication is still a current research topic. Mobile Agent is autonomous entity which moves
from one computer to another in the open network under its own control. In multi agent environment where multiple agents
are created, different MAs want to locate each other to communicate, assist and to take decisions together. It is always very
tough to get the location of MA until it comes back to origin host after completing its itinerary. To trace the Location of MAs is
a very important part of communication among different MAs. The strategy of Location Management (LM) & its effectiveness
depends on the cost of searching and updating the database. Hence For the location management of MAs and their
communication there is a need of system which improves the cost of searching and updating the databases. The paper has
proposed Hierarchical Location Management Scheme (HLMS) for two different cases of same base host and different base
host. HLMS divides the global network in regions. In each region there is a centralized component responsible to maintain the
location of all MAs presently executing in its region. It also records the address of the region where MA is migrating. Various
search and update schemes are then used to locate MA by its base host or other cooperating MAs. But these schemes are not
cost effective. Search takes less time but this is a very long process and update is a fast process but the update cost is very high.
Hence this paper combines the both search and update method. Here HLMS using the combination of both update and search.
Paper proposes substitute approaches for two different cases, first when Base Host of communicating MAs is same and second
when Base Hosts for communicating MAs are different. Paper also proposes a mailbox based techniques to provide
communication among the MAs.By dividing the network into regions and by combining both approaches Search and Update
HLMS reduces the overall cost of Location Management. Basically this HLMS works for the Multi agent environment where
different agents can communicate with each other and any Base Host or any agent launch by same Base Host or by different
Base Host can track the location of MAs. This paper proposes different algorithm for Communication among the MAs.
Communication uses mailbox technique. Every mobile agent in the system is allocated a mailbox. Incoming messages sent to
the agent are inserted into the mailbox first. There are two approaches of communication Push and Pull. In the Push (PS)
mode, the mailbox keeps the address of its owner and forwards every incoming message to it. In the Pull (PL) mode, the mobile
agent keeps the address of its mailbox and retrieves messages from the mailbox whenever needed. Theoretically the cost of
updation and searching reduces in the improved HLMS. But the verification is still under process. HLMS will simulate by CPN
Model under different parameters. So the algorithm proposed by the paper is a way to reduce the cost of location and provide a
way of communication among MAs. Here HLMS has given two different improved approaches for two different cases, first
when Base Host of communicating MAs are same and second when Base Hosts for communicating MAs are different. Paper
also using mailbox based techniques to provide communication among the MAs. Paper analyzes the limitation of HLMS and
giving some improved solutions of it.
Keywords:- Mobile Computing; Mobile Agent (MA); Mobile Agent System (MAS); Multi Agent System (MS);
Location Management (LM); Base Host (BH).
1. INTRODUCTION
A Multi Agent System is a system collected of numerous interacting intelligent agents. MA contain by the Multi Agent
System can launch by launch by same host or by different hosts or combination of MAs and software agents. Multi
Agent System is used to solve problems which are hard or unfeasible for an individual agent to solve. But for a Multi
Agent System the two main issues are Location management & communication. Lots of Mobile agent systems have
been proposed in the literature. But most existing MASs do not provide a complete, proficient or useful location
management approach. Hence, there is a need of a mechanism to locate any type of mobile agent at anytime from
Volume 2 Issue 10 October 2014
Page 16


ISSN 2321-5992
anywhere. Communication is also a necessary component of scattered systems and this is no exception for multi-agent
systems [1][3][4]. This paper proposes the improve mechanism to locate MAs for both cases mentioned earlier as well
as provide a communication mechanism between the MAs.
Fig1: Basic Architecture of HLMS
2. ANALYSIS OF HIERARCHICAL LOCATION MANAGEMENT SCHEME (HLMS)

According to Hierarchical location Management Schemes [2], internet is network of networks where networks are
connected with each other via router. Each router maintains an Agent Table which contains all the MAs currently
executing on the network and their HostId. Every Base Host maintains a Base table which contains a NetId and
AgentId. The following points give some analysis of HLMS:
When a MA moves from one host to other within the same network Agent Table is modified.
When MA moves from one network to other, receiving router launch an Update Agent to inform the Base Host about
the new network location of the MA. So in this approach Base Host always knows the current network of its MA.
To communicate with MA, Base Host sends message to the MAs router, where router locate the MA by searching the
Agent Table and deliver the message.
That approach combines both search and update schemes.
That scheme works for mobile multi agent system where instead of one Base Host; MAs launched by same or
different host locate each other before initiating the communication.
There was one extra component which works for communication its name is mailbox.
That approach used the case of FM for the migration of Mailbox of MAs.
But it has a limitation of high communication and access time association associated with it.
3. COMPONENT OF IMPROVED HIERARCHICAL LOCATION MANAGEMENT SYSTEM

The different Components [2][4] of our improved Hierarchical Location Management System for Mobile Multi Agent
are:
Table 1 Component Description of the Hierarchical Multi Agent Model
Components
Router/Network
Location Management System (LMS)
Log Manager (LM)
CPH
HostId
Message Deliver
Description
Every network has a router and it is identified by NetId.
It is a system which manages the location of the MAs.
It manages the arrival and departure time of the MAs.
It is a host which works as a centralized place holder. All MAs update
their location on this host.
A host in the global network is identified by number known as HostId.
It is responsible for the delivery of the messages to the target Mailbox
of the MA.
Page 17


Mobile Agent
Search Agent
Update Agent
Packet
Base Table
Local Message Table
Global Message Table
Agent Table
Log Table
Agreement Table
Location Table

ISSN 2321-5992
Every MA in the system is identified with unique AgentId. It carries
Parent HostId and certificate of verification SC (String, Destination
HostId) for communication and Another agent for communication.
In order to locate a MA, its base host launches a Search Agent (SA).
When a MA arrives at a network, an Update Agent (UA) is created to
inform BH about the new network location of MA. It is also used to
update the location to the Central repository.
Agents move from one part of the network to other via global network
in form of packet. A packet consists of an Agent, sender HostId,
destination HostId and type of agent MA, SA or UA.
Every Network maintains a BaseTable, which is the list of AgentId and
the current NetId of the MA.
Every Base Host maintains a MessageTable, which is the list of target
AgentId and messages for the target MA.
Every Network maintains a MessageTable, which is the list of target
AgentId and messages for the target MA.
Every network maintains an AgentTable which is the list of AgentId of
MA and HostId of the hosting Node.
For all MAs received at the router an arrival entry is logged in
LogTable similarly before leaving a network departure entry is logged
to the LogTable.
It contains the HostId of the hosts with which agreement has been
signed. It also contains the Date time and duration of agreement.
This table is maintained by the centralized place holder on a host. It
contains the actual network id and the HostId or all MAs. All MAs
update their location on CPH time to time.
4. IMPROVED METHODS TO LOCATE MOBILE AGENTS IN HLMS

4.1 Case 1- For the Same Base Host
This section proposes the improved mechanism to locate different MAs launched by same Base host. According to
HLMS every host maintains a BaseTable which stores network Ids of all the active MAs launched by it. Base Host
always knows the current network location of MAs. [1][2][5][6][7] Hence if a MA wanted to communicate with other
MA launched by same base host, it initiated six processes GetNetId(), ReturnNetId(), GetHostId(), ReturnHostId(),
SendMessage() and GetMessage(). But it has a limitation of high communication time association associated with it.
Firstly MA will get NetId of target MA then it will go to the router for getting the actual location of target MA. For this
MA will access the Agent Table. After getting the location MA will send the message to the Mailbox of target MA. Let
us suppose the time taken in getting the NetId is t1 & time taken to access the AgentTable and getting the HostId is t2.
Hence the total time to get the actual location of target MA is t1+t2. Again for further communication time taken in
sending the message to the Mailbox is t3.Hence total time to send a message to a particular location is t1+t2+t3. This
time is very high. Hence we are giving three approaches to reduce the communication and access time of location of
target MA.
4.1.1Base Host will send the message to mailbox of target MA
When a MA wants to communicate with other MA, MA knows the AgentId and also has message to send to the target
MA. In this case MA send message and target AgentId to the Base Host. Now Base host is responsible to the successful
delivery of the message and the source MA is now free to do another communication. As we know Base Host knows the
NetId of the target MA so BH will send a request to the router for asking the HostId. After getting the HostId BH
directly send the message to the Target Mailbox of the Agent. Hence if a MA wants to communicate with other MA
launched by the same base host, it initiates six processes: 1. SndMesgandAId: This process initiates by the Source MA to send the message and the target Agent Id to the Base
Host. This message is stored in the local message table of the Base Host.
2. GetAId: This process initiates a search procedure to visit the AgentId of target MA and search the Local Message
Table to get the AgentId of target MA.
3. GetNetId: This process initiates a search procedure to visit the Network Id of target MA and search the Base Table
to get the NetId of target MA.
Page 18


ISSN 2321-5992
4. GetHostId: This process initiates a search procedure to visit the Network Id of target MA and search the local
Agent Table to get the HostId of target MA.
5. ReturmHostId: This process returns the HostId of the target MA.
Figure 1 Message Sending by the Base Host

6. SendMesg: This process is initiated by the Base Host of Source MA when mailbox address of the target agent is
known; it drops the message to the mailbox of the target MA.
7. GetMessage: This process is initiated by the target MA. Here target MA wants to get the message from its
mailbox. To get the message MA use push and pull approach as shown in figure1. In the Push (PS) mode, the
mailbox keeps the address of its owner and forwards every incoming message to it. In the Pull (PL) mode, the
mobile agent keeps the address of its mailbox and retrieves messages from the mailbox whenever needed.
4.1.2 Message Deliver component on Router will send the message to mailbox of target MA
MA. Firstly MA will get NetId of target MA then it will go to the router and send message and target AgentId to the
Global message table of the router. Router has a component named Massage Deliver which is responsible for the
successful delivery of the message.
1. GetNetId: This process initiates a search procedure to visit the Network Id of target MA and search the Base Table
to get the NetId of target MA.
2. ReturnNetId: This process returns the NetId of the target MA.
3. SndMesgandAId: This process initiates by the Source MA to send the message and the target AgentId to the
Router. This message is stored in the Global Message Table.
4. GetHostId: This process initiates a search procedure to visit the NetId of target MA and search the local Agent
Table to get the HostId of target MA.
5. SendMesg: This process is initiated by the Base Host of Source MA when Mailbox address of the target agent is
known; it drops the message to the Mailbox of the target MA.
Mailbox. To get the message MA use push and pull approach as shown in figure2.
Figure 2 Message Sending by the Message Deliver Component

4.2 Case 2: - For Different Base Host
Sometimes there is a need to communicate among different MAs launched by different hosts. MAs launched by two
different hosts can communicate with each other only if both the hosts trust each other and have signed an agreement to
Page 19


ISSN 2321-5992
allow their respective MAs to locate and communicate with each other. For signing an agreement every host contains
and Agreement Table which contains the HostId of the signed Host Through agreement each MA carries with it the
Base Host of itself as well as the HostId of the Host with which agreement has been signed. According to [2] every host
maintains a Base Table which stores the AgentId and its current NetId. Hence to communicate with any MA, source
MA requires the current NetId of target MA. Since it already knows the Base Host of the target MA it will send a
request to the Base Host of target MA to get its current NetId. For the security purpose it should not be allowed for any
MA to locate and communicate with any other MA. When MA send a request for the NetId to the target Host then
target host will only allow access of NetId to the trusted MAs. So if a MA wants to communicate with other MA
launched by the different base host, there are three cases: 4.2.1 Base Host will send the message to mailbox of target MA
When a MA wants to communicate with other MA, MA knows the AgentId, Base HostId of target MA and also has
message to send to the target MA. In this case MA send message and target AgentId to the Base Host of target MA.
Now Base host of target MA is responsible to the successful delivery of the message and the source MA is now free to
do another communication. As we know target Base Host knows the NetId of the target MA so BH will send a request
to the router for asking the HostId. After getting the HostId Base Host directly sends the message to the target Mailbox
of the Agent. Hence if a MA wants to communicate with other MA launched by the different Base Host, it initiates six
processes: 1. SndMesgandAId: This process initiates by the Source MA to send the message, target MA HostId and the target
AgentId to the Base Host of target MA. After getting target Host will check verify the agreement table for the
authenticity of the agent and then it will provide the actual NetId of the target MA.
2. GetNetId: This process initiates a search procedure to visit the NetId of target MA and search the Base Table to
get the NetId of target MA.
3. GetHostId: This process initiates a search procedure to visit the NetId of target MA and search the local
AgentTable to get the HostId of target MA.
4. ReturnHostId: This process returns the HostId of the target MA.
5. SendMesg: This process is initiated by the Base Host of target MA when mailbox address of the target agent is
known; it drops the message to the mailbox of the target MA.
mailbox. To get the message MA use push and pull approach as shown in figure3.
Figure 3 Message Sending by the Base Host

4.2.2 Message Deliver component on Router will send the message to mailbox of target MA
When a MA wants to communicate with other MA, MA knows the AgentId, target HostId and also has message to
send to the target MA. Firstly MA will get NetId of target MA then it will go to the router and send message and target
AgentId to the router. Router has a component named Massage Deliver which is responsible for the successful delivery
of the message. This message is store in the Global Message Table. Hence if a MA wants to communicate with other
MA launched by the different base host, it initiates six processes: 1. GetNetId: This process initiates a search procedure to visit the NetId of target MA and search the Base Table to
get the NetId of target MA.
2. ReturnNetId: This process returns the NetId of the target MA.
3. SndMesgandAId: This process initiates by the Source MA to send the message and the target Agent Id and
HostId to the Base Host of target MA.
4. GetHostId: This process initiates a search procedure to visit the NetId of target MA and search the local Agent
Table to get the HostId of target MA.
Page 20


ISSN 2321-5992
5. SendMesg: This process is initiated by the MD on router when mailbox address of the target agent is known; it
drops the message to the mailbox of the target MA.
Figure 4 Message Sending by the Message Deliver Component

4.2.3 Centralized place holder at a host will send the message to mailbox of target MA
MA. All agents will send message and target AgentId to a centralized place holder at a Host. Now CPH will provide the
actual location of the target MA to the source MA. Hence if a MA wants to communicate with other MA launched by
the different base host, it initiates four processes: 1. GetNetIdandHostId: This process initiates a search procedure to visit the NetId of target MA and search the
location Table to get the NetId and HostId of target MA.
2. ReturmNetIdandHostId: This process returns the NetId and HostId of the target MA.
3. SendMesg: This process is initiated by the source MA when mailbox address of the target agent is known; it drops
the message to the mailbox of the target MA.
Figure 5 MA communication by CPH
5. CONCLUSION
Communication determines how much information is exchanged between agents. The amount of information available
to an individual agent will in turn influence the decision-making process. In open MAS, agents are mobile and may
leave or enter the system. This dynamicity results in two closely related agent communication problems, namely
efficient message passing and service agent discovery. For the communication, track the location of MAs are very
important. Our work is based on this approach. Here we gave two different ways of communication for MAs. Global
network is the network of networks. The different networks are connected with each other via Router. All MAs are
migrating from or entering into a local area network via router. Host can be the part of any network in the global
network. If Base host of different agent are same so there is no need to find the NetId of the MA because Base Host
already knows it but if Base Host are different, first Both the host sign an agreement between each other then the agent
can communicate. But in this case searching cost is very.
Page 21


ISSN 2321-5992
6. FUTURE WORK
Our work is based on the location of MA's and their communication in a multi agent environment. Here we have
explained the improved cases of Mobile agent communication. We will simulate it in our next paper using CPN tool.
We are working on it and trying to give a better result in terms of cost. We will also propose some solutions and
problems of these approaches.
REFERENCES
[1] Swati Aggrawal, Heman Pathak, Analysis of Location Management Mechanisms forMobile Multi Agents in
International Journal of Information and Computation Technology(IJICT), ISSN :0974-2239, Volume 3, Number
9pp: 917-926, 2013.
[2] Heman Pathak, Comparative Performance of Hierarchical Location Management Mechanisms for Mobile Agents
in Journal of Information Systems and Communication (JISC), ISSN: 0976-8742, E-ISSN: 0976-8750, Volume 3,
Issue 1, pp: 278-281, 2012.
[3] Tracker: A Universal Location Management System for Mobile Agents George Samaras, Constantinos Spyrou,
Evaggelia Pitoura+, Marios Dikaiakos Department of Computer Science, University of Cyprus CY-1678 Nicosia,
Cyprus, cssamara@cs.ucy.ac.cy + Department of Computer Science, University of Ioannina GR 45110, Ioannina,
Greece, pitoura@cs.uoi.gr
[4] Heman Pathak, Search and Update Based Solutions to Locate Mobile Agents in the Global Network in
International Journal of Mobile And AdHoc Network (IJMAN), ISSN(Online): 2231:6825 ISSN(Print): 2249
202X, Vol. 4, Issue 1, Pp: 75-79, Jan-Apr 2014.
[5] R. B. Patel, Nikos Mastorakis, GREECE K. Garg, "Mobile Agent Location Management in Global Networks ,
Department of Computer Science & Engineering M. M. Engineering College, Mullana- 133203, Haryana, India,
Dept of Computer Science, Military Inst. of University Education / Hellenic Naval Academy Terma
Hatzikyriakou 18539, Piraeus, Department of Electronics & Computer Engg, IIT Roorkee, Roorkee- 247667,
Uttaranchal, India
[6] Heman Pathak, Colored Petri Net based Modeling of Hybrid Location Management Mechanism for Mobile
Agents in Journal of Information Systems and Communication (JISC), ISSN: 0976-8742, E-ISSN: 0976-8750,
Volume 3, Issue 1, pp: 291-294, 2012.
[7] Rama Sushil, Rama Bhargava, Kumkum Garg" Location update schemes for mobile agents" 1Asst. Prof. SGRRITS
D. Dun, R/S Dept. Of Maths, I. I. T. Roorkee, India, ramasushil@yahoo.co.in,2Prof. Of Mathematics, I. I. T.
Roorkee, India, bhargava_iitr@rediffmail.com,3Prof. Of Computing, I. I. T. Roorkee, India, Sr. Member IEEE,
kgargfec@iiternet.in
Page 22

Improved Hierarchical Location Management Schemes To Locate Mobile Agents in Multi Agents Environment

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Improved Hierarchical Location Management Schemes To Locate Mobile Agents in Multi Agents Environment

Hochgeladen von

Copyright:

Verfügbare Formate

IPASJ International Journal of Computer Science (IIJCS)

Web Site: http://www.ipasj.org/IIJCS/IIJCS.htm

A Publisher for Research Motivation ........

Volume 2, Issue 10, October 2014