Dear All,
We propose a distinction between KA_HEAR by AK_TELL command and
KA_HEAR by AK_SAY command, because the common KA_HEAR prevents agents
from better cooperation.
We think this proposal leads to new cooperation mechanisms in
RoboCupRescue.
The contents of our proposal is as follows:
(a) KA_HEAR_TELL header and KA_HEAR_SAY header are added to
RoboCupRescue protocol
(b) Agent developers can also use the present KA_HEAR header
(c) The number of message sending and message hearing is not changed
Revised rescue-0_43-unix package is here:
http://ne.cs.uec.ac.jp/~hiroki-e/rescue/rescue-0_43-unix-revised-hearing.tar.gz
[http://ne.cs.uec.ac.jp/~hiroki-e/]
This package includes:
* Revised RescueSystem.cxx
* Revised basic.hxx
* RescueSystem.cxx.org as original RescueSystem.cxx
* basic.hxx.org as original basic.hxx
* RescueSystem.cxx.diff, differences between RescueSystem.cxx.org
and RescueSystem.cxx
* basic.hxx.diff, differences between basic.hxx.org and basic.hxx
(a) KA_HEAR_TELL and KA_HEAR_SAY are added to the RoboCupRescue protocol.
Agent can know which command, AK_TELL or AK_SAY, a received message
was sent by.
KA_HEAR : Presently used
KA_HEAR_TELL: KA_HEAR sent to kernel by AK_TELL command
KA_HEAR_SAY : KA_HEAR sent to kernel by AK_SAY command
Presently, if a police force agent received a message from an
ambulance team agent, a police force agent can understand this message
was sent by AK_SAY command. But, if a police force agent received a
message from another police force agent at unrecognized position, it
is impossible for a police force agent to ecognize which command was
used.
If this proposal is adopted, receiver agents can recognize which
command, AK_TELL or AK_SAY, was used by a speaker agent. The kernel
send two packets as follows, when kernel received a communication
command (AK_TELL or AK_SAY):
* When kernel receives an AK_TELL communication command, then kernel
sends two packets, KA_HEAR and KA_HEAR_TELL, which have the same
message body.
* When kernel receives an AK_SAY communication command, then kernel
sends two packets, KA_HEAR and KA_HEAR_SAY, which have the same
message body.
(b) Agent developers can also use the present KA_HEAR header
The present agents can run without any changes, because the kernel
sends two packets as mentioned in (a) above.
Agent developers can use either or both of the present KA_HEAR header
and the headers added in this proposal, KA_HEAR_TELL and KA_HEAR_SAY.
Agent developers can choose command to receive a communication
message.
(c) The number of message sending and message hearing is not changed.
Agents should receive a message either one of KA_HEAR, KA_HEAR_TELL
and KA_HEAR_SAY, because these three commands have the same body.
Best regards,
Hiroki ENDO
-- Hiroki ENDO, YowAI Ikuo Takeuchi Laboratory, Department of Computer Science, University of Electro-Communications E-mail: hiroki-e@takopen.cs.uec.ac.jp
This archive was generated by hypermail 2.1.3 : Sun 14 Dec 2003 - 13:33:07 GMT