DFKI Technical Memo-01-01
by Michael Schillo, Klaus Fischer, Tore Knabe
The Contract-Net with Confirmation Protokoll:
An Improved Mechanism for Task Assignment
The Contract Net Protocol was designed for distributing one task among a number of agents. However, up to now it remains an unanswered question which policy the agent should use for resource allocation, i.e. in what manner it should reserve resources for tasks it made a bid for. If the agent allocates too many resources too early, it may not get its bid accepted and therefore resources will not be available for other tasks. If it allocates too late, it may have committed to more tasks than it has resources.
The major inefficiency in the CNP is that in every execution of the protocol all participating agents need to commit themselves to do the job, although only one of them will actually get the award. In this document we present the contract net with confirmation protocol (CNCP), which precisely addresses this issue and improves the CNP procedure by drastically reducing the number of commitments made. We also present an extension of this protocol for the cascaded application of the protocol, i.e. the case where bidders in the protocol can again start an instance of the protocol to subcontract the whole or parts of the task.
The previous abstract is here.
Note: This page was written to look best with CSS stylesheet support Level 1 or higher. Since you can see this, your browser obviously doesn't support CSS, or you have turned it off. We highly recommend you use a browser that supports and uses CSS, and review this page once you do. However, don't fear, we've tried to write this page to still work and be readable without CSS.