<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="client.xsl" type="text/xsl"?>
<article article-type="other">
<front>
<journal-meta>
<journal-id/>
<issn/>
<banner>
<!--<href>banner.jpg</href>-->
<size width="100%"/>
</banner>
</journal-meta>
<article-meta>
<title-group>
<article-title>Periodic Real-Time Resource Allocation for Teams of Progressive Processing Agents</article-title>
</title-group>

<author><a href="mailto:gdibango@ift.ulaval.ca"><name>Gilles Steeve Dibangoye</name></a></author>
<aff>GREYC-CNRS &amp; DAMAS, Laval University, G1K7P4, Quebec, Canada</aff>

<author><a href="mailto:mouaddib@info.unicaen.fr"><name>Abdel-Illah Mouaddib</name></a></author>
<aff>GREYC-CNRS, University of Caen, France, Bd. Marechal Juin, Campus II</aff>

<author><a href="mailto:chaib@ift.ulaval.ca"><name>Brahim Chaib-Draa</name></a></author>
<aff>DAMAS Laboratory, Laval University, G1K7P4, Quebec, Canada</aff>

</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>In this paper, we focus on the problem of finding a periodic allocation strategy for teams of resource-bounded agents. We propose a real-time dynamic algorithm RTDA*, that exploits two key properties to avoid the exponential increase in the state and action spaces associated with multi-agent systems. First, resource allocation at each time period follows an earliest deadline first order (EDF) over agents. Second, the resources are <italic>undivided</italic>, i.e., the resources allocated to an agent restrict their availability to others over time. We can therefore view each incoming agent as a cyclic individual resource-bounded processing, namely "<italic>cyclic progressive reasoning unit</italic>" (C-PRU), and solve, off-line, the single agent resource allocation problem. In the on-line phase, our algorithm exploits pre-compiled policies, as heuristic metrics, to build near-optimal joint decisions at each time period.</p>
</abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>AAMAS07_0349_b324af1029f23592a1a3f1f63168518b</hpdf>
</fpdf>
</body>
</article>

