[经济学]AGENT MONITORING AGENTS.ppt

AGENT MONITORING AGENTS MONITORING THE HISTORY OF AGENTS AND RESTRICTING USER ACCESS Mentors: Dr.Sadanand Srivastava, Dr.James Gil de Lamadrid Presented by: Marietta Gittens, Hemalatha Yellapragada Bowie State University PROJECT GOAL To design a system that covertly monitors the activities of intelligent agent processes deployed on the network. MONITOR USAGE Individuals wishing to monitor agents that they have deployed on the network. Administrators covertly monitoring the use of agents and groups of agents of their subordinates. OBJECTIVE To introduce restricted user access to the agent monitor, groups, agents, and displays. OBJECTIVE BACKGROUND Agents can communicate with each other and this is monitored by the server. An agent registers at the server and gets a port# for ping action. BACKGROUND An agent receives a “ping” from the server. If active it replies “OK”. If not there is no reply. An agent that has moved is reinitialized by an agent catcher at its new host. BACKGROUND A relocated agent always reregisters at the server. MONITORING HISTORY In logging the history of the groups of agents the following are monitored: Agent identity Operation performed - birth, death, group entry, split, merge, delete, relocation MONITORING HISTORY Group agent operated upon Timestamp of all operations Location of agent * * To monitor the history of our agents via a graphical user interface. To use the popular agent-based packages, such as Jini and Voyager, as a test bed for the Agent Monitoring System. User Interface AMA server agent1 agent2 group leader AGENT-BASED SYSTEM Fig.A THE AMA STRUCTURE agent3 FIG.B AGENT REGISTRATION server agent Agent Info. BackPort # for Ping FIG.C MONITORING AGENT COMMUNICATION agent1 agent2 User Interface server message communication detection FIG.D PING ACTIVE AGENTS agent1 agent2 User Interface server ping ping active agent list OK ping