1 / 32

CoAX Technology Contributions

DARPA. CoAX Technology Contributions AFRL Rome, AIAI, Boeing, Dartmouth, DERA Malvern, Lockheed Martin ATL, Michigan, MIT Sloan, OBJS, USC/ISI, UWF/IHMC Support from BBN, GITI, ISX, MITRE, Schafer, Stanford Coalition Agents eXperiment (CoAX) http://www.aiai.ed.ac.uk/project/coax/.

zwi
Download Presentation

CoAX Technology Contributions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DARPA CoAX Technology Contributions AFRL Rome, AIAI, Boeing, Dartmouth, DERA Malvern, Lockheed Martin ATL, Michigan, MIT Sloan, OBJS, USC/ISI, UWF/IHMC Support from BBN, GITI, ISX, MITRE, Schafer, Stanford Coalition Agents eXperiment (CoAX) http://www.aiai.ed.ac.uk/project/coax/

  2. Object Services and Consulting, Inc. DARPA

  3. Technical Contributions • GITI - CoABS Grid Infrastructure • Boeing and UWF/IHMC- KAoS Domain Management • AIAI Process Panel - Task and Process Management • DERA Master Battle Planning • LM ATL EMAA/CAST AODB - Restricted Data Base Access • AFRL/BBN/GITI CAMPS - Air Logistics Support Tool • USC/ISI Ariadne - Open Information Access • UWF/IHMC - NOMADS safe and secure mobile agents • Stand alone demonstrations at 9 months: • MIT Robustness Services • Dartmouth Observer Agent • Michigan Coordination Planning Aid

  4. GITI/ISXThe CoABS Grid • The CoABS/Infrastructure code provides a framework for integrating diverse agent-based systems, and provides additional common services. • The Grid allows agents to find services and other agents so that agent teams can be dynamically formed to solve context-based tasks. • The Grid is built using JiniTM technology. Direct agent communication is provided using message queues built on JAVA RMI. Grid Logging Markup Language based on XML.

  5. Prototype Grid Architecture Grid Aware Services e-mail Proxi Agents Auction/Trader Agents Information Retrieval Agents Grid Ready Components OAA Proxy Agent RETSINA Proxy Agent Matchmaker Mobility EventMessaging Grid Core Services Logging Admin Instrument- ation Object Visualization Events Security AgentRep Message Queue Grid Agent Helper ServiceRep Registry Grid Service Helper Java Platform: RMI, Jini™ • Interoperability of distributed, heterogeneous objects, services, and multi-agent systems. • Registration and advertisement of capabilities. • Discovery of relevant participants, and flexible run-time communications. • Current Grid services include: Logging, Visualization, Security, Instrumentation, Communication, Registration, and Event Services.

  6. Boeing/UWF - Agent Domains DM An agent domain consists of one or more agents registered with a common Domain Manager which provides for common administration and enforcement of domain-wide, platform-specific, and agent-specific policies.

  7. Agent Domain Management in CoAX • Broadens typical distributed security concerns to include: • Communication and access management: Who can communicate with whom for what services? • Registration management: Who can join the domain under what circumstances? • Resource management: Who can have which kind and how much of a given computing resource? • Mobility management: Who can move where under what circumstances? • Conversation management: What constraints govern interaction between conversing agents? • Obligation management: Who is not meeting commitments? Initial capability shown in six-month demo Initial capability slated for nine-month demo Initial capability slated for 2001-2002 demos

  8. Policy Admin Tool Policy Management Framework Authorized user makes changes over the Web KAoS Domain Manager 1. Ensures policy consistency at all levels 2. Stores policy changes 3. Notifies guards HTTP RMI Servlet Event-driven policy changes RMI JNDI Policy Directory Other Guard Aroma VM Guard Java VM Guard Agent Native Mech Agent Agent Agent Agent Agent Native Mech 1. Abstract, mechanism- neutral representation/XML syntax (DAML collaboration) 2. Distributed networked availability 3. Secure Guard is responsible for: 1. Interpreting policy 2. Enforcing with appropriate native mechanism

  9. KAoS Policy Admin Tool

  10. AIAI I-X Process Panel • Initially maintains an overview of the current status the coalition C2 processes in accessible shared military terms. • Later adds the ability to monitor, plan and control the coalition C2 processes. • Can take on and address “issues” in the C2 process. • Links to and assists with domain management, authority, exception management and other Grid management services. • To be packaged as generic task and process management facilities that can be made available to other Grid applications.

  11. AIAI I-X Process Panel

  12. DERAMaster Battle Planner • Visual planning tool for air operations. • Map-based graphical user interface - operator builds scenario and air missions using simple dialogs and “point and click” techniques. • Analyzes plans (identifying over-tasking, GANTT charts, animated flyout facility) • Obtains data on targets and assets from other agents. • Integrates air missions (e.g. air transport) and weather forecasts from other agents into the air visualisation. • Informs AIAI’s Process Panel of current planning status.

  13. DERAMaster Battle Planner

  14. DERAMaster Battle Planner

  15. AFRL/GITI/BBNCAMPS Mission Planner • Develops schedules for aircraft to pick up and deliver cargo within specified time windows. • Takes into account a large number of constraints (aircraft & port capabilities, crew availability, work schedule rules) • Can be tasked by other agents. • Domain-aware agent obtains scheduled air transport flights and forwards them to Master Battle Planner for integration into the air visualisation.

  16. AFRL/GITI/BBNCAMPS Mission Planner

  17. USC/ISI Ariadne Weather Agent

  18. LM ATL EMAA/CAST AODB Access Agent • Provides access to AODB via XML formatted Grid messages. • Supports different kinds of queries: one shot, update, and persistent. • Will be evolving EMAA/CAST technology to create a deliverable generic Grid-aware core agent engine to other end users. This technology will be configurable and is intended to easily allow access to alternative sources.

  19. LM ATL EMAA/CAST AODB Access Agent

  20. Lm ATL EMAA/CAST AODB Access Agent

  21. USC/ISI Open Information Access • Provide real-time access to Web data sources • Tools for learning wrappers to extract data for semi-structured sources • Agents learn the structure of data to support: • Source verification automatically detect when the source no longer provides correct data (possibly because the source has changed) • Source reinduction automatically revise wrapper when site change

  22. Resource Control and Security in NOMADS • Dynamic and fine-grained resource control • NOMADS enforces security policies specified by the KAoS domain manager • Security policies include limits on CPU, disk, and network resource usage • Resource consumption monitoring • NOMADS Guard constantly monitors the resource consumption of the GAO agent • When the guard detects a potential denial of service, the guard reduces the resource limits available to the GAO agent

  23. Observers Domain KPAT Domain Manager Java VM Resource Control and Security in NOMADS Aroma VM G GAO DAO

  24. Field Observations (Dartmouth) • Team of soldiers • PDA’s • Ad-hoc wireless networking • Soldiers make observations. • Ground traffic • Air traffic • Personnel and equipment • Buildings and other structures • Observations are fed into battle-planning systems (e.g., MBP) through the CoABS Grid. • In the demo, a team of CoAX soldiers will make observations to correct Gao mis-information.

  25. D’Agents API Observation Agent Grid API Field Observations (Dartmouth) I see a tank! Query/ Response Observation Viewer (9-month demo - standalone) Registration/ Update Stream MBP (18-month demo - integrated) Observations

  26. MIT Robustness Service • The Challenge • Open systems (like coalitions) include unreliable agents (bugs, malice) and infrastructures • The MIT Robustness Service • Monitors agent ‘health’ via polling • Tracks inter-agent commitments • Controls task cancellation, result caching & task re-announcement • Maintains reliability information (failure avoidance) • Informs registry of hung agents

  27. Michigan Multilevel Coordinator Agent • Analyses the alternative plan spaces of coalition functional teams that plan independently and act asynchronously • Works top-down with plans chosen by teams to predict unintended interactions (resource contentions; friendly fire). • Identifies candidate resolutions (timing or action constraints). • Notifies process panel of possible plan conflicts and computed workarounds. • Operationalizes/enforces coordination decisions selected. • Given more time, isolates and resolves conflicts more precisely and efficiently. • Allows planning and coordination decisions to be postponed until runtime conditions become better known. • Packaged as a Grid-aware component that can be proactively executing and utilized by the AIAI Process Panel.

  28. Michigan Multilevel Coordinator Agent

  29. eGents Inside Command Post Evacuees Medevac Liaison Family Member In one eGents application, each evacuees are given a Personal Status Monitor, which measures location, vital signs, etc. The PSM contains an eGent which intermittently communicates to subscribing entities using email protocols. OBJS eGents: Agents over Email Problem CoAX Impact • Dynamic military situations are often disconnected and asynchronous. Need a scalable way to deliver agent messages to 1000’s of (wireless) platforms. • Agent systems are often closed and require a lot of specialized agent technology. Email is a common denominator in coalition situations. • By 2012 imagine free eGents attached to sensors, actuators, people, equipment, & locations as pervasive observers & actors • Anyone with email can create an agent service that anyone else can use. New eGent apps can be downloaded to the field as situations change. Approach • Thesis: Integration of agent technology with pervasive Web-ORB-Email backplanes is a route to making agent technology open, pervasive and robust. • eGents are agents which communicate over email. eGents leverages pervasive, robust email infrastructure, inherits support for disconnected operations, message queueing, mobile users, firewalls, filtering, logging, and security. eGents use FIPA or KQML Agent Communication Language (ACL) encoded in XML. No ACL parser needed. Status: Prototype, NEO demo, gridified, on wireless Palm. Spec submitted to FIPA. In progress: packaging and numerous extensions.

  30. OBJS eGents: Agents over Email Miami demo: standalone - 18 month demo: integrated w Process Panel & MBP

More Related