The goal of this effort is to define the concepts and implementation technologies for agents and commitments, so that we can build up a network of contracted agents that make up the domains of authority within the OOI distributed system. We will focus on two use cases:
- Use case 1 - negotiations between facility agents. A facility negotiates with another facility and establishes contracts between them. Facilities are one type of resource within the system.
- Use case 2 - negotiations between execution agents and the execution environment. We will refine the notion of agent at the level of a virtual machine being activated as part of an execution environment and negotiating its role within the execution environment (for example, who is allowed to do what on that machine)
- Munindar Singh, NCSU
- Kartik Tadanki, NCSU
- Emilia Farcas, UCSD
- Dorian Raymer, UCSD
- Michael Meisinger, UCSD
- Create a domain model for Agent Contract Network, including
- model for interactions specifications
- model for commitments & contracts between facilities pertaining to the interaction protocols by which the facilities interact, such as to establish suitable rights and privileges on one another
- Define the language by which the commitments needed for the contract types of the above domain model will be expressed along with a mapping to a database schema, and a serialization in XML
- Provide the interaction protocols describing specific exchanges of messages corresponding to the negotiation and enactment of contracts (a) between facilities and (b) between machine agents and an execution environment
- Develop middleware that supports commitments, enabling their use by agents who communicate using FIPA ACL, especially as layered on top of AMQP
- Enhance a general middleware service, which an agent developer may use to incorporate support for commitments into agents, and which supports limited customization through queries for the agents' commitment stores
- Evaluate the benefits of FIPA Agent Communication Language (ACL) and Interaction Protocols for OOI along with an assessment of the essential and inessential features
- Evaluate Jade as an implementation toolkit
- Domain models; relational and XML schemas for commitments
- Report documenting the architecture, technology choices, and experience from the prototype.
- Consolidated Agent Contract Network Deliverables.
- Iteration 1: Plan and Design, Meetings, Deliverables.
Focus on theory and concepts for facility, agents, contracts and interaction. Investigate the use cases of membership and resource negotiation. Implement FIPA-compliant agents using Jade
- Iteration 2: Plan and Design, Deliverables.
Focus on foundations and design of resource agents, an agent framework implementation (as part of the Magnet framework), contracts for the Messaging service use case and refinement of the contract/commitment model. Development of specific data models for the resource use scenario and the specific resource type of community.
- Iteration 3: Plan and Design, Deliverables.
Focus on extending the models to a community-to-community use case, preparing the messaging service use case and refining the rules engine based implementation.
- Iteration 4: Plan and Design, Deliverables
Focus on delivering an end-to-end story around the use case of the messaging service entities. Show the users, communities and resources in this scenarios and the policy challenges imposed. Show how the mechanisms developed by the ACN address these challenges and provide tool.
- Iteration 5: Aligned with COI Release 1, Iteration 1