Appeal 2007-0786
Application 10/262,142
instance of the scheduling agent for each user while the other agents are
shared by a community of users since they hold common information and
data. (Cesta, p. 112, para. 40).
3. The scheduling agent can play the role of organizer or guest. Once a
meeting is announced, the agents have to reach an agreement to make the
event possible while respecting all the constraints on the meeting. The
scheduling agent for each user maintains a knowledge base about the user
containing his preferences, his interests, his availability, his agenda
(Cesta, p. 112, para. 42). The agents extract priority values from the
individual user preferences that are utilized to make a first proposal in
case of conflict. If an agreement is not possible, a negotiation phase
starts in which the organizer can ask the agents to relax some constraints
(Cesta, p. 112, para. 43).
4. The resource agent knows the cities in which the users live, the places
usually hosting meetings and the available resources. It can figure out
the distance between places to select the most convenient town and place
to organize the meeting (Cesta, p. 112, para. 45).
5. Cesta does not teach the location of the resource agent nor does it teach a
processor function or controller embedded with a resource.
6. RFC 2739 discusses calendar attributes for vCard and LDAP, but makes
no mention of resources needed for meetings nor does it teach a
processor function or controller embedded with a resource.
5
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next
Last modified: September 9, 2013