US20010023439A1 - Multi-agents cooperating method and system - Google Patents

Multi-agents cooperating method and system Download PDF

Info

Publication number
US20010023439A1
US20010023439A1 US09/866,682 US86668201A US2001023439A1 US 20010023439 A1 US20010023439 A1 US 20010023439A1 US 86668201 A US86668201 A US 86668201A US 2001023439 A1 US2001023439 A1 US 2001023439A1
Authority
US
United States
Prior art keywords
agent
user
request
agents
planning
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US09/866,682
Inventor
Kazuya Miyazaki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitsubishi Electric Corp
Original Assignee
Mitsubishi Electric Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mitsubishi Electric Corp filed Critical Mitsubishi Electric Corp
Priority to US09/866,682 priority Critical patent/US20010023439A1/en
Publication of US20010023439A1 publication Critical patent/US20010023439A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/50Indexing scheme relating to G06F9/50
    • G06F2209/501Performance criteria
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • Y10S707/99945Object-oriented database structure processing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99948Application of database or data structure, e.g. distributed, multimedia, or image

Definitions

  • the present invention relates to a multi-agents cooperating method and a system which is capable of readily describing a distributed application for providing services by cooperatively performing a plurality of applications and processes in a distributing environment composed of a plurality of computers mutually connected via a network.
  • An agent which is an entity of computing process such as a plurality of processes for performing a computing process on a distributed environment composed of a plurality of computers mutually connected via a network provides services in response to a request for service from a certain user or other agent.
  • FIG. 19 of the accompanying drawings is a block diagram of a conventional multi-agents cooperating system disclosed, for example, in Japanese Patent Laid-Open No. Hei 4-77827 and Japanese Patent Laid-Open No. Hei 4-279935.
  • FIG. 19 is a block diagram of a conventional multi-agents cooperating system disclosed, for example, in Japanese Patent Laid-Open No. Hei 4-77827 and Japanese Patent Laid-Open No. Hei 4-279935.
  • an agent providing a variety of services comprises a communicating section 102 for communicating information with an other agent, a communicating definition storing section 103 which is a data base storing definitions for determining contents of information to be communicated, procedure of communication and target of communication, communicating target determining and communicating section 104 for determining contents of information to be communicated, procedure of communication and target of communication by referring to the contents of the communicating definitions storing section 103 , a rule base storing definitions of manner of plan or planning, and contents of the services, and a planning and service executing section 106 for providing planning and service referring to the contents of the rule base 105 .
  • FIG. 20 is a flow diagram showing a total summary of the conventional system.
  • the process in the conventional system comprises a step 201 for determining if the ordered service is accepted to execute, a step 202 for determining if the order is really entrusted or not, and a step 203 for performing requested services.
  • step 201 the agent 101 estimates contents (specification) of services requested by the other agent or user and decides, if it is acceptable, to execute processing to provide the requested services. If the agent 101 desires to accept the request, it inquires conditions for the acceptance to the other agent or user. In step 202 , the other agent or user estimates the conditions to accept the request returned from the agent with its particular criterion so as to determine if it actually entrusts the execution of the services. In step 203 , the agent 101 executes services having been entrusted thereto.
  • FIG. 21 is a detailed flow diagram of step 201 for determining if it accepts requests to execute the requested services.
  • the step 201 for determining if it accepts requests to execute the requested services comprises a step 204 for receiving specification of the service requested by the other agent or user by the agent 101 , a step 205 for estimating the specification of the requested service having been received in step 204 by the agent 101 , a step 206 for determining if the agent 101 desires to accept the request on the basis of the estimated result in step 205 , and a step 207 for transmitting reply of desiring to accept the request when the agent 101 has decided to accept the request in step 206 .
  • step 204 the agent 101 receives specification of services to be executed by the communicating section 102 from the other agent or user.
  • step 205 the agent 101 estimates a variety of restricting conditions for executing the services by the transmitting target and communicating section 104 in accordance with the procedure and restrictions of communication defined in the communicating definition storing section 103 , refers to the rule base 105 in the planning and service executing section 106 , and estimates the probability of executing the service by trying to produce a plan for executing the specification of the service.
  • step 206 the agent 101 judges if it accepts the request to perform the service on the basis of the estimated result in step 205 . As a result of the judgment, if it does not accept it, the operation terminates. In the case of accepting the request, the agent 101 transmits the conditions for executing the service to the other agent or user through the communicating section 102 in step 207 .
  • FIG. 22 is a detailed flow diagram of step 203 for executing the service having been entrusted in FIG. 20.
  • Step 203 for executing the entrusted service comprises step 208 for receiving messages representing to entrust the service, step 209 for entrusting partial service after communicating with an other agent if necessary for executing the entrusted service, and step 210 for executing partial service by the agent 101 .
  • step 208 the agent 101 receives service-entrusting information from the other agent or user having decided to entrust the service in step 202 through the communicating section 102 .
  • the agent 101 for executing the plan produced in the planning and service executing section 106 for executing the service, its transmitting target determining and communicating section 104 communicates through the communicating section 102 in accordance with the procedures and restrictions which are defined in the communicating definition storing section 103 with the other agent capable of executing a part of the plan when required.
  • step 210 the service which can be processed by the agent 101 itself is executed in the planning and service executing section 106 .
  • FIG. 23 is a block diagram of a conventional multi-agent cooperating system disclosed for example in Japanese Patent Laid-Open No. Hei 3-84652.
  • the multi-agent cooperating system comprises a plurality of agents 111 for providing a variety of services, a user information administering section 112 for storing information from users, and a common memory 113 for communicating information among the user, agent 111 and the user information administering section 112 which use the multi-agent cooperating system.
  • any agent 111 estimates the request by referring to the contents of the user information administering section 112 .
  • the agent 111 judges to be able to process the request, the processed result of the service held by the agent 111 is written into the common memory 113 . If any competition arises due to a plurality of agents 111 trying to provide services, the competition would be resolved by eventually selecting a single service result among the competed services.
  • the definitions of the cooperating operations are relative to the communicating procedure and communicating target, so as to distribute the cooperating manner to a plurality of agents. As a result, the change of the agent organization and the cooperation would be more difficult.
  • the agent itself contains the definitions relative to the manner of cooperative operation to be performed with a suitable judgment of the actual situation for processing the request from the user, the amount of described contents from the agent would be enormous.
  • the present invention has been attained to overcome problems as mentioned above, and is aimed at providing a multi-agent cooperating system and method which is capable of readily defining flexible cooperative operation of a wide application range and attending to the user requests, and system change and extension.
  • a multi-agent cooperating method provides services as requested by a user by cooperation of a plurality of agents, the planning method provides separation of which is obtaining combination of functions for attaining services requested by a user, data to be transmitted and received between the functions, and plans for the order in which the data is executed from resource division, which is a problem of distributing tasks so that tasks for attaining services for elemental functions so as to maintain the balance of load state or operating state of the resource connected to the elemental function or the elemental function for attaining the service requested by the user such that the problem is solved by the divided process for each problem.
  • the definition of the specification with regard to the group of the members of the aforementioned agent and the procedure of the cooperation between the agents, the definition of the elemental function, and the definition of the plan, are defined separately from each other, and the agent executes the cooperative operation in accordance with the definition.
  • a multi-agent cooperating system for providing services in accordance with a request from user by cooperation of a plurality of agents comprises: one or more elemental function agents for providing elemental functions; one or more planning agents having definitions relating to the plan and having the ability to distribute tasks; and a field manager connected via said elemental function agents and planning agents, having definitions relating to the collection of the members of the planning agents and the elemental function agents and the procedure of cooperation between these two agents so as to administer the cooperative operation between the agents.
  • the field manager comprises: a communicating means for transmitting/receiving information to/from the agents or the user; a cooperative definition data base for storing the members of the agent to perform the cooperative operation and the definition of the procedure of the cooperative operation; and a cooperative operation performing means for transmitting a message to make the agent perform the cooperative operation with reference to the definition of said cooperative definition data base via the communicating means.
  • the planning agent comprises: a communicating means for transmitting/receiving information to/from said agent or user; a rule base for storing rules to generate a plan; a planning performing means for generating a plan with reference to the rule base; an estimating data storing means for storing basics to estimate the request contained in the message from the field manager; and an estimating means for making estimation in accordance with the data contained in said estimating data storing means.
  • the elemental function agent comprises: a communicating means for transmitting/receiving information to/from the agent or user; an functional definition storing means for storing a definition of an elemental service function or a part thereof; a service executing means for executing service or a part thereof in accordance with the contents of said elemental function definition storing means; an estimating data/profile storing means for storing estimating basics and profiles; and an estimating means for estimating in accordance with the data stored in said estimating data/profile storing means.
  • a multi-agent cooperating method for executing cooperative operation using the multi-agent cooperating system comprising the steps of: receiving a service request from a user in said field manager; transmitting the service request, with instructions related to cooperation added thereto, to the planning agent; executing estimation and planning in accordance with the service request and the instructions in the planning agent; judging if the result of the estimation in accordance with the service request and the instructions has reached a prescribed criterion and further the plan has been obtained; asking for the elemental function agent to make an estimation as to load; returning the result of the load estimation to the planning agent in the elemental function agent; making a general estimation of the estimated result from the planning agent and the elemental function agent; determining a planning agent to ask for the work to execute the service based on the result of the general estimation and informing this agent of that; and executing the process in accordance with the plan or with the elemental function agent in the entrusted planning agent.
  • a multi-agent cooperating method for executing cooperative operation using said multi-agent cooperating system comprising the steps of: transmitting the profile stored in the estimating data/profile storing means to the field manager and the planning agent in the elemental function agent to be newly installed in the multi-agent cooperating system; estimating the contents of the profile received from the elemental function agent in the field manager and the planning agent; judging if the contents of the profile should be registered; and registering the elemental function agent in the cooperative definition data base as a member.
  • the multi-agent cooperating system of this invention as estimating criterion for entrusting and accepting tasks in the agent, there are provided classes of: restrictions that must be satisfied necessarily in view of specification; basics with relatively wide allowance which are prioritized in accordance with user or user's preference; and basics related to cost of resource that can be calculated from the load state of the CPU or associated equipments.
  • a multi-agent cooperating system for providing services in accordance with the request from the user by cooperative operation of a plurality of agents, comprising: one or more planning agents having definitions as to plan and ability of distributing tasks; a means for describing the plan in the definition of the planning agent; and a describing means for defining the plan for the user.
  • the planning agent comprises a plan base for storing the plan having been described by the plan describing means, and a plan interpretation executing means for interpreting and executing the contents of the plan base.
  • a multi-agent cooperating system for providing services in reply to a request from user by cooperative operation of a plurality of agents, comprising: a user definition storing means provided for each user in order to store personal information related to each user; and a user agent provided to correspond to each user definition storing means for processing the request from the user by, for example, adding options thereto and then transmitting it to the agent.
  • the personal information contains user attribute representing objective characteristics of each user; and options to be used when requesting services.
  • a multi-agent cooperating system for providing services in reply to the request from user by cooperative operation of a plurality of agent, comprising: agents for providing services requested by the user; a field manager for administering the cooperative operation among the agents by adding cooperative information as instructive information related to the cooperative operation to the message, wherein a plurality of agents cooperate in the field being within the scope of the field manager using the messages.
  • the agent comprises a means for executing instructions contained in the instructive information corresponding to the instructive information.
  • a means for executing the services of the agent an estimating means for estimating input messages, and an attributes storing means for storing attributes of the agents.
  • a multi-agent cooperating system for providing services in reply to a request from a user by cooperative operation of a plurality of agents, comprising a means for storing a combination of a pattern requested by the user and an agent corresponding to the request among the agents available for processing the request, wherein when a request for the same pattern is input, the request is preferentially distributed to this agent.
  • a multi-agent cooperating system for providing services in reply to a request from a user by cooperative operation of a plurality of agents, comprising a means for storing the pattern of request from the user and agent which would provide an estimated value equal to or more than a predetermined estimation criterion among the agents available for processing the request, wherein when a request of the same pattern is input again, the cooperative operation is executed only between the agents.
  • a multi-agent cooperating method for executing cooperative operation using a multi-agent cooperating system for providing services in reply to a request from a user comprising agents for providing services requested by a user, field managers for managing cooperative operations among the agents, so that a plurality of agents cooperate using message in a field being a scope of management by the field manager, wherein the field manager performs functions comprising the steps of: informing the agents in the field of the request from the user; presenting the conditions to accept the requests from the agent having been judged to be able to process the request to the user collectively; and making an agent corresponding to the condition designated by the user among the presented conditions execute the request.
  • a multi-agent cooperating system for presenting services corresponding to a request from a user by cooperative operation of a plurality of agents, comprising a means for presenting conditions to accept the processing by the agent for the request from the user collectively to the user, making the user select an appropriate agent, and entrusting the execution of the process to the selected agent.
  • each user would access the multi-agent cooperating system through the user agent that uniquely manages its own information.
  • the user agent modifies options in reply to the request of services from the user and converts them into appropriate forms which could be interpreted by each agent to be transmitted.
  • the user agent can also obtain user information by almost the same communication as in the case of making communication between the agents. If a plurality of users exist, the user agent is connected to the multi-agent cooperating system in correspondence to each user.
  • the cooperative operation may be made in accordance with the contents of the cooperative information transferred from the field manager, so that the agent can easily realize complicated operations just by providing means corresponding to the contents of information included in the cooperative information.
  • the requested pattern and the agent corresponding to the request are stored, so that the stored agent can preferentially process when a request of the same pattern is input, without unnecessarily repeating the same cooperative operation for the same request each time.
  • the requested pattern, and among the agents corresponding to the request agents having values not less than the estimating criterion of the field are stored, and when a request of the same pattern is input again, the cooperative operation limited just between these agents are carried out.
  • the user inputs a request without designating any agent, then conditions of agents available for processing the request are presented. The user selects an agent to actually perform the processing.
  • FIG. 1 is a block diagram showing a general composition of a multi-agent cooperating system according to a first embodiment of this invention
  • FIG. 2 is a block diagram showing the inner composition of the field manager according to the first embodiment of this invention.
  • FIG. 3 is a block diagram of the inner composition of a planning agent according to a first embodiment of this invention.
  • FIG. 4 is a block diagram showing the inner composition of an elemental function agent according to a first embodiment of this invention.
  • FIG. 5 is a flow diagram representing the cooperative operation of the agent according to the first embodiment of this invention.
  • FIG. 6 is a flow diagram representing the operation of a new elemental function agent when started according to the first embodiment of this invention.
  • FIG. 7 is a block diagram showing a planning agent when a means for describing the plan is provided in the definition of the planning agent according to a second embodiment of this invention.
  • FIG. 8 is a block diagram of a multi-agent cooperating system according to a third embodiment of this invention.
  • FIG. 9 is a profile table showing contents of a user definition storing section according to a third embodiment of this invention.
  • FIG. 10 is a preference table showing contents of a user definition storing section according to the third embodiment of this invention.
  • FIG. 11 is a block diagram showing a multi-agent cooperating system corresponding to multi-users according to the third embodiment of this invention.
  • FIG. 12 is a block diagram showing a multi-agent cooperating system according to a fourth embodiment of this invention.
  • FIG. 13 is a flow diagram showing the function of the multi-agent cooperating system according to the fourth embodiment of this invention.
  • FIG. 14 is a block diagram showing a multi-agent cooperating system according to a fifth embodiment of this invention.
  • FIG. 15 is a flow diagram showing the operation of a multi-agent cooperating system according to the fifth embodiment of this invention.
  • FIG. 16 is a flow diagram showing the operation of a multi-agent cooperating system according to a sixth embodiment of this invention.
  • FIG. 17 is a block diagram showing a multi-agent cooperating system according to a seventh embodiment of this invention.
  • FIG. 18 is a flow diagram showing the operation of a multi-agent cooperating system according to a seventh embodiment of this invention.
  • FIG. 19 is a block diagram of a conventional multi-agent cooperating system
  • FIG. 20 is a flow diagram showing the general operation of the conventional system
  • FIG. 21 is a detailed flow diagram of conventional steps to determine whether the service request can be accepted
  • FIG. 22 is a detailed flow diagram showing steps to carry out entrusted services in a conventional multi-agent cooperating system.
  • FIG. 23 is a block diagram showing a conventional multi-agent cooperating system.
  • FIG. 1 is block diagram showing a general composition of a multi-agent cooperating system according to a first embodiment of this invention.
  • This multi-agent cooperating system comprises: a user interface 1 for communication between an end user and a multi-agent cooperating system of this embodiment; a field manager having definitions of collection of members of agents to execute cooperative operations and procedures of the cooperative operations in the multi-agent cooperating system so as to make the other agent execute cooperative operation; a planning agent having definitions as to plan; and an elemental function agent having an elemental function to perform services.
  • FIG. 2 is a block diagram showing the inner composition of the field manager 2 in FIG. 1.
  • the field manager 2 comprises: a communicating section 5 for transmitting/receiving information to/from the agent or the user; a cooperative definition data base 6 for storing definitions of procedures of member and cooperative operations of agents to perform the cooperative operation; and a cooperative operation executing section 7 for communicating message for making other agent execute cooperative operation via the communicating section 5 referring to the definition of the cooperative definition data base 6 .
  • FIG. 3 is a block diagram showing the inner composition of the planning agent 3 in FIG. 1.
  • the planning agent 3 comprises: a communicating section 8 for transmitting/receiving information to/from other agents or a user; a rule base 9 for storing rules to produce plans; a planning executing section 10 for producing plans with reference to the rule base 9 ; an estimating data storing section 11 for storing criterion to estimate the request contained in the message from the field manager 2 ; and an estimating section 12 for making estimation in accordance with the contents of the estimating data storing section 11 .
  • FIG. 4 is a block diagram showing the inner composition of the elemental function agent 4 .
  • the elemental function agent 4 comprises: a communicating section 13 for transmitting/receiving information to/from other agents or a user; a functional definition storing section 14 for storing definitions of services or elemental functions being a part thereof; a service executing section 15 for executing services or a part thereof in accordance with the contents of the functional definition storing section 14 ; an estimating data/profile storing section 16 for storing estimating criterion and profile; and an estimating section 17 for making estimation in accordance with the estimating data and profile.
  • the term planning signifies a problem to obtain combination of functions to attain services requested from a user, data to be transferred between functions, and plans being the procedures to execute them.
  • resource distribution is a problem to distribute tasks to attain the services for the elemental function so that the balance between the elemental function to attain the plan or operating state of resources coupled to the elemental function or the load state can be maintained.
  • the planning and the resource distribution are separated from each other, so that the problem can be solved by a process of two stages divided for each problem.
  • the specification as to the procedure of cooperation between the agents and the collection of the members of the agents to cooperate, the elemental function and the plan are defined separately from each other so that the agents can cooperate in accordance with the definitions.
  • FIG. 5 is a flow diagram showing the cooperative operation of the agents in this embodiment.
  • the cooperative operation of the agents includes: a step 21 for receiving a service request from the user by the field manager via the user interface 1 ; a step 22 for adding instructions relating to the cooperation to the service request and transmitting it to the planning agent 3 ; a step 23 for making estimation and planning in accordance with the service request and the instructions; a step 24 for judging if the estimated result reaches a prescribed criterion and the plan has been obtained; a step 25 in which the planning agent 3 entrusts the elemental function agent 4 to estimate the load; a step 26 in which the elemental function agent 4 estimates the load and returns the estimated result; a step 27 in which the field manager 2 generally estimates the estimated result returned from the planning agent 3 and the elemental function agent 4 ; a step 28 in which the field manager 2 determines the planning agent 3 for entrusting the task to actually attain the service from the result of
  • the field manager 2 receives the service request having been input by the user through the interface 1 via the communicating section 5 .
  • the field manager 2 transfers the instructions generated by the cooperative operation executing section 7 in accordance with the description in the cooperative definition data base 6 which is added to the service request from the user to appropriate planning agents 3 that are members to the planning agent 3 .
  • the planning agent 3 estimates the specification of the services requested by the user in the estimating section 12 in accordance with the contents of the estimating data storing section 11 , and the planning execution section 10 generates plan to execute the service requested in accordance with the contents of the rule base 9 .
  • step 24 the planning agent 3 judges if the aforementioned estimated result has reached the prescribed criterion and the plan has been obtained. If the criterion is not satisfied or no plan is obtained, the planning agent 3 terminates its operation. Otherwise, in step 25 , the planning agent 3 entrusts a necessary elemental function agent 4 via the communicating section 8 to estimate the position of the device associated with the elemental function agent 4 and the load via the communicating section 8 . At this time, necessary information for the estimation is transmitted with the entrust. In step 26 , the elemental function agent 4 receives the entrust via the communicating section 13 , and estimates the received information in accordance with the contents in the estimating data and profile storing section 16 , and returns the estimated result to the planning agent 3 via the communicating section 13 .
  • step 28 the field manager 2 determines a planning agent 3 for entrusting the task to actually attain the services on the basis of the result of the general estimation for entrusting it to execute the task.
  • step 29 the planning agent having been entrusted processes the task together with the appropriate elemental function agent 4 in accordance with the aforementioned plan.
  • estimation criterion for entrusting or accepting the task, namely the process for the planning agent or the elemental function agent 4 .
  • these are a criterion that must be necessarily satisfied in view of the specification, a criterion having a wide range of allowance and being preferentially graded by the user based on the user requirements, and a criterion as to the cost of a resource calculated from the load state such as associated equipments or CPU.
  • the estimation is made on the basis of these criterion.
  • the planning agent 3 estimates the specification of the service request from the user in the estimating section 12 , and terminates the operation at this time point if the result does not reach the prescribed criterion. Otherwise, it would be possible that the planning executing section 10 generates plan and proceeds to the step 25 if the plan is obtained.
  • the general estimation of the step 27 can also be presented to the user via the user interface 1 in an appropriate form of the total estimation result without performing in the field manager 2 to be executed by the user. Also, it is possible in the same manner that the determination of the entrusted agent in step 28 is executed by the user.
  • FIG. 6 is a flow diagram representing operations associated with the start of the new elemental function agent 4 according to this embodiment.
  • the operation associated with the start of the new elemental function agent 4 comprises: a step 31 in which the user inputs a new elemental function agent 4 to the system; a step 32 in which the elemental function agent 4 transmits the profiles of the estimating data and the profile storing section 16 to the field manager 2 and the planning agent 3 ; a step 33 in which the field manager 2 and the planning agent 3 estimates the contents of the received profile; a step 34 for judging if the field manager 2 and the planning agent 3 are to be registered; and a step 35 in which the field manager registers the elemental function agent 4 in the cooperative definition data base 6 .
  • step 31 the user install a new elemental function agent 4 into the system.
  • the elemental function agent 4 transmits the estimating data for estimating the specification and the profile in the estimating data and profile storing section 16 via the communicating section 13 to the field manager and the planning agent 3 .
  • the field manager 2 and the planning agent 3 receive the profile through the communicating section 5 and 8 .
  • the field manager and the planning agent 3 refer the contents in the profile to the contents in the cooperative definition data base 6 , estimating data storing section 11 , and the rule base 9 for estimating if the elemental function agent 4 is necessary for the field manager 2 or the planning agent 3 .
  • step 34 if it is unnecessary for the field manager 2 or the planning agent 3 to be registered, the process in the field manager 2 and the planning agent 3 terminates. If it is judged as necessary, in step 35 , the field manager 2 registers the elemental function agent 4 as a member in the cooperative definition data base 6 .
  • FIG. 7 shows an embodiment having a means for describing plan in the definition of the planning agent 3 .
  • the function of the planning agent 3 , communicating section 8 , the estimating data storing section 11 , and the estimating section 12 is almost the same as that in FIG. 3.
  • the planning agent 3 further comprises a plan describing section 18 for making the user describe the plan, a plan base 19 for storing plan described by the plan describing section 18 , and a plan interpretation executing section 20 for interpreting and executing the contents of the plan base 19 .
  • the user uses the script language presented in the plan describing section 18 to describe a combination of functions to attain a certain service, data to be transmitted/received between the functions, and plan being a procedure to execute the data.
  • the contents of the description are stored in the plan base by the plan describing section 18 so as to define a planning agent having a new plan by the user definition.
  • the plan having been stored in the plan base 19 will be interpreted and executed by the plan interpreting/executing section 20 .
  • plan describing section 18 , the plan base 19 , and the plan interpreting section 20 can also be provided together with the rule base 9 and the planning executing section 10 of the planning agent 3 shown in FIG. 3.
  • the plan base 19 is firstly tried for application in reply to the service request from the user, and then the planning executing section 10 executes the plan generation.
  • possibility of making the plan generation taking a long time be unnecessary would arise, so that the efficiency for obtaining a plan by the planning agent 3 can be improved.
  • FIG. 8 shows a third embodiment of this invention.
  • the multi-agent cooperating system comprises an agent group 41 composed of a plurality of agents for providing services to the user; a user definition storing section 42 for storing personal information of the user; a user agent 43 for referring to the contents of the user definition storing section 42 and converting a request from the user into appropriate form to be transferred to the agent group 41 .
  • FIGS. 9 and 10 show contents of the user definition storing section 42 according to this embodiment which respectively represent a profile table 44 for standing for the user attributes being user's objective characteristics such as name, section etc. and a preference table 45 representing preferences of the user for the option when service is requested.
  • FIG. 11 shows a correspondence to multi-user of a multi-agent cooperating system which is composed to be capable of coping with a plurality of users in this embodiment.
  • each of the user agents 43 is coupled to the agent group 41 in correspondence to each user.
  • the user inputs a request via the user interface presented by the user agent 43 .
  • the user agent having received the request refers to the preference table 45 and the profile table 44 of the user definition storing section 42 and carries out supplementary processing such as adding an option such as the resolution shown in FIG. 10 to the request so as thereafter to input to the agent group 41 .
  • the request input by the user is converted into an appropriate form reflecting the characteristics of the user so that the system can interpret the request input by the user to be transferred to the agent group 41 .
  • the user agent 43 returns a value of user's attributes requested by referring to the user definition storing section 42 when user characteristics are requested by the agent group 41 side.
  • the multi-agent cooperating system side need not take the form and contents of the user information into consideration which contributes to the simplification of the structure. Further, it is easily possible to cope with a plurality of users just by coupling a user agent 43 being a exclusive module for each user to the system.
  • FIG. 12 shows a fourth embodiment of this invention.
  • the multi-agent cooperating system according to this embodiment comprises a plurality of agents 46 for providing services to the user and has a field 47 for prescribing method of cooperation.
  • the field manager 48 instructs and manages the cooperative operation between the agents 46 in the field 47 .
  • a variety of information is communicated between the field manager 48 and the agents 46 via the message 49 .
  • the field manager 48 adds cooperative information 50 to the message 49 for giving instructions relating to the cooperative operation.
  • Each agent 46 includes a selector 51 for interpreting the cooperative information 50 contained in the message 49 and determining the cooperative operation, an executing section 52 for executing the service of the agent 46 , an estimating section 53 for estimating the message having input, and an attributes storing section 54 for storing attributes of the agent 46 .
  • FIG. 13 is a flow diagram showing process according to this embodiment. The process will now be described with reference to this FIG. 13.
  • the field manager 48 adds the cooperative information 50 to the message representing the request from the user (step 221 ).
  • the cooperative information 50 in this embodiment is any one of the instructive information for entrusting the execution of the service, information for requesting the present of information contained in the agent 46 , and information for designating an estimating method such as the preferential degree for the estimation.
  • the agent 46 reads the message 49 to which the cooperative information is added (step 222 ), and the selector 51 determines the process in accordance with the contents of the cooperative information 50 (step 223 ).
  • the selector 51 transfers the message 49 to the executing section 52 , which then execute the services indicated in the message 49 (step 224 ). If the contents of the cooperative information 50 is such information as to request the presentation of information, the selector 51 receives the attributes of the agent 46 indicated in the cooperative information from the attributes storing section 54 and transfers them outside (step 225 ). If the contents of the cooperative information 50 is to designate the estimating method, the selector 51 transfers the message 49 containing the cooperative information 50 to the estimating section 53 , which then makes an estimation in accordance with the cooperative information (step 226 ).
  • the field manager 48 converts the contents of the cooperative information 50 and transfers them to the agent 46 .
  • the means for executing the cooperative operation in accordance with the contents of the instructive information contained in the cooperative information 50 , namely the executing section 52 , the estimating section 53 , and the attributes storing section 54 in each agent 46 .
  • FIG. 14 shows a fifth embodiment of this invention.
  • components equivalent to those in the previous embodiment are designated by the same numerals.
  • an entrusted target memory section 55 as a means for storing a combination of request patterns from a user and the agent that actually accepted the request as a set.
  • FIG. 15 is a flow diagram showing a process of this embodiment.
  • the field manager 48 reads the request from the user (step 231 ), and judges if the request pattern corresponding to the request exists in the entrusted target memory section 55 (step 232 ). If no corresponding pattern exists, normal processing is executed in accordance with cooperating rule previously prescribed (step 233 ). Namely, the contents of the request from the user are notified to the agent 46 in the field 47 , and this agent 46 estimates the request, and if it judges to be able to process the request by itself, it inform the field manager 48 of that.
  • the field manager 48 selects one agent 46 to process the request from the user in accordance with predetermined estimating criterion as shown in the first embodiment, for example.
  • the agent 46 having finally processed the request and the request pattern are stored in the entrusted target memory section 55 as a set (step 234 ). If the request pattern corresponding to the entrusted target memory section 55 exists, the agent 46 having the entrusted target memory section 55 containing the request is preferentially and directly asked to execute the request (step 235 ).
  • the set of the request pattern and the agent 46 having finally executed the request has been stored in the entrusted target storing section 55 .
  • those having an estimated value equal to or more than a threshold value after being referred to a predetermined estimating criterion that is a threshold contained in the field manager are stored in the entrusted target storing section 55 .
  • FIG. 16 is a flow diagram showing the process according to this embodiment.
  • the field manager 48 reads the request from the user (step 241 ), and judges if the corresponding request pattern exists in the entrusted target memory section 55 (step 242 ). If no request pattern exists, normal processing is executed in accordance with a predetermined cooperating rule (step 243 ). At this time, among the agents 46 having an accepted to process the request, the group of the agent 46 having estimated value equal to or larger than a predetermined threshold of the field manager 48 together with the request pattern is stored in the entrusted target storing section 55 (step 244 ).
  • the entrusted target memory section 55 has been composed so as to be used by the field manager 48 , but alternatively it is also possible to make the entrusted target memory section 55 be used by the user agent in the third embodiment, so that the user agent is ordered to limit the agents to be entrusted to process the request depending on the request pattern.
  • FIG. 17 shows a seventh embodiment of this invention.
  • a user selecting section 56 which presents the conditions for accepting the process sent from the agent 46 collectively to the user so that the user selects an appropriate agent 46 and to entrust the agent 46 to actually process the request based on the result of the selection.
  • the other components are the same as those in fifth and sixth embodiments so as to be omitted from explanation.
  • FIG. 18 is a flow diagram showing the process according to this embodiment.
  • This embodiment is composed of the steps of: reading the request from the user by the field manager 48 (step 251 ); announcing the request to the agent 46 in the field 47 (step 252 ); sending conditions for executing the process to the agent 46 having judged to be able to process the request (step 253 ); presenting the conditions to the user using the user selecting section 56 by the field manager (step 254 ); selecting by the user an agent 46 having presented conditions that are the closest to the request of its own from the presented condition; actually entrusting the selected agent 46 by the field manager 48 to execute the process for the request (step 256 ); and processing the request by the entrusted agent 46 (step 257 ).
  • the field manager 48 reads the request presented to the field 47 from the user.
  • the contents of the read request are sent to each agent in the field 47 .
  • the noticed agent 46 estimates the request as being processable by itself, it returns conditions for accepting the request.
  • the field manager 48 presents the conditions returned from the agent 46 to the user in a form selectable by the user through the user selecting section 56 .
  • the agent 46 having presented the conditions closest to the request of its own among the presented conditions is selected.
  • the field manager 48 entrusts the agent 46 which corresponds to the conditions selected by the user to execute the process of the request.
  • the entrusted agent 46 executes the request.
  • the cooperative definition can be made separately from those of the planning, resource distribution, and elemental function. Therefore, the description of the application is simplified and eased. The cooperative definition can also be easily changed.
  • plan is opened to the user so as to be instantly suited to the needs of the user, and the planning process which is normally complicated and requires significant time to execute may be omitted. Consequently, the total process efficiency can be enhanced.
  • the user input is converted into an appropriate form reflecting the characteristics of the user within a scope that is acceptable by the system so as to be then transferred to the multi-agent cooperating system of this invention, the form or contents of the user information need not be recognized by the system side, which contributes to simplify the composition. Further, it is possible to easily cope with a plurality of users by simply coupling a module exclusive for each user to the system.
  • the cooperative operation of the agent can be changed by changing the contents of the cooperative information by the field manager, it is possible to realize a complicated function merely by mounting simple agents, and further it is possible to perform different cooperative operations when the field is changed within the same agent.

Abstract

A multi-agent cooperating system and method which is capable of being applied to a plurality of users with a simple composition and of performing efficient processing. The system comprises an agent group composed of a plurality of agents for providing services to the user, a user definition storing section for storing personal information such as user preferences for the options when requesting a service, and a user agent for converting the request from the user into an appropriate form with reference to the contents in the user definition storing section and transmitting them to the agent group, or transmitting the value of the attributes of the user with reference to the user definition storing section when user characteristics are requested from the agent group. The user agents are coupled to the agent group corresponding to each user.

Description

    BACKGROUND OF THE INVENTION
  • 1. Field of the Invention [0001]
  • The present invention relates to a multi-agents cooperating method and a system which is capable of readily describing a distributed application for providing services by cooperatively performing a plurality of applications and processes in a distributing environment composed of a plurality of computers mutually connected via a network. [0002]
  • 2. Description of a Prior Art [0003]
  • An agent which is an entity of computing process such as a plurality of processes for performing a computing process on a distributed environment composed of a plurality of computers mutually connected via a network provides services in response to a request for service from a certain user or other agent. [0004]
  • FIG. 19 of the accompanying drawings is a block diagram of a conventional multi-agents cooperating system disclosed, for example, in Japanese Patent Laid-Open No. Hei 4-77827 and Japanese Patent Laid-Open No. Hei 4-279935. In FIG. 19, an agent providing a variety of services comprises a communicating [0005] section 102 for communicating information with an other agent, a communicating definition storing section 103 which is a data base storing definitions for determining contents of information to be communicated, procedure of communication and target of communication, communicating target determining and communicating section 104 for determining contents of information to be communicated, procedure of communication and target of communication by referring to the contents of the communicating definitions storing section 103, a rule base storing definitions of manner of plan or planning, and contents of the services, and a planning and service executing section 106 for providing planning and service referring to the contents of the rule base 105.
  • An operation of the conventional system will now be described with reference to the drawings. FIG. 20 is a flow diagram showing a total summary of the conventional system. As shown in FIG. 20, the process in the conventional system comprises a [0006] step 201 for determining if the ordered service is accepted to execute, a step 202 for determining if the order is really entrusted or not, and a step 203 for performing requested services.
  • In [0007] step 201, the agent 101 estimates contents (specification) of services requested by the other agent or user and decides, if it is acceptable, to execute processing to provide the requested services. If the agent 101 desires to accept the request, it inquires conditions for the acceptance to the other agent or user. In step 202, the other agent or user estimates the conditions to accept the request returned from the agent with its particular criterion so as to determine if it actually entrusts the execution of the services. In step 203, the agent 101 executes services having been entrusted thereto.
  • FIG. 21 is a detailed flow diagram of [0008] step 201 for determining if it accepts requests to execute the requested services. The step 201 for determining if it accepts requests to execute the requested services comprises a step 204 for receiving specification of the service requested by the other agent or user by the agent 101, a step 205 for estimating the specification of the requested service having been received in step 204 by the agent 101, a step 206 for determining if the agent 101 desires to accept the request on the basis of the estimated result in step 205, and a step 207 for transmitting reply of desiring to accept the request when the agent 101 has decided to accept the request in step 206.
  • In [0009] step 204, the agent 101 receives specification of services to be executed by the communicating section 102 from the other agent or user. In step 205, the agent 101 estimates a variety of restricting conditions for executing the services by the transmitting target and communicating section 104 in accordance with the procedure and restrictions of communication defined in the communicating definition storing section 103, refers to the rule base 105 in the planning and service executing section 106, and estimates the probability of executing the service by trying to produce a plan for executing the specification of the service. In step 206, the agent 101 judges if it accepts the request to perform the service on the basis of the estimated result in step 205. As a result of the judgment, if it does not accept it, the operation terminates. In the case of accepting the request, the agent 101 transmits the conditions for executing the service to the other agent or user through the communicating section 102 in step 207.
  • FIG. 22 is a detailed flow diagram of [0010] step 203 for executing the service having been entrusted in FIG. 20. Step 203 for executing the entrusted service comprises step 208 for receiving messages representing to entrust the service, step 209 for entrusting partial service after communicating with an other agent if necessary for executing the entrusted service, and step 210 for executing partial service by the agent 101.
  • In [0011] step 208, the agent 101 receives service-entrusting information from the other agent or user having decided to entrust the service in step 202 through the communicating section 102. In step 209, the agent 101, for executing the plan produced in the planning and service executing section 106 for executing the service, its transmitting target determining and communicating section 104 communicates through the communicating section 102 in accordance with the procedures and restrictions which are defined in the communicating definition storing section 103 with the other agent capable of executing a part of the plan when required. In step 210, the service which can be processed by the agent 101 itself is executed in the planning and service executing section 106.
  • FIG. 23 is a block diagram of a conventional multi-agent cooperating system disclosed for example in Japanese Patent Laid-Open No. Hei 3-84652. In FIG. 23, the multi-agent cooperating system comprises a plurality of [0012] agents 111 for providing a variety of services, a user information administering section 112 for storing information from users, and a common memory 113 for communicating information among the user, agent 111 and the user information administering section 112 which use the multi-agent cooperating system.
  • The operation of the conventional system will now be described with reference to FIG. 23. When the user inputs a certain request to the [0013] common memory 113, any agent 111 estimates the request by referring to the contents of the user information administering section 112. When the agent 111 judges to be able to process the request, the processed result of the service held by the agent 111 is written into the common memory 113. If any competition arises due to a plurality of agents 111 trying to provide services, the competition would be resolved by eventually selecting a single service result among the competed services.
  • According to the conventional cooperating system and method shown in FIG. 19, however, definitions on the planning and resource division are mixedly stored in the same agent and are not processed by clearly distinguished steps. As a result, the definitions of the agent and the whole system would be complicated, and the coverage of the processing section would become difficult. [0014]
  • In the conventional system, it has been necessary to describe the relationship to the other agent at the portions related to the plan and communication in all of the agents. This would break the independency of the definitions of the agent, such that the extent of the system would be reduced. [0015]
  • Further, in the conventional system, the definitions of the cooperating operations are relative to the communicating procedure and communicating target, so as to distribute the cooperating manner to a plurality of agents. As a result, the change of the agent organization and the cooperation would be more difficult. [0016]
  • Since the conventional system has been composed of agents having different functions but with the same level, the definitions relating to the cooperative operations and planning in a variety of forms requested when practically applied would be complicated. [0017]
  • Further, in the conventional system, as the estimating criterion for accepting tasks by the agents, those having a certainly wide range of allowance such as cost and those having narrow range of allowance such as restrictions have been treated equally without any clear difference, it has been difficult to construct a system that can appropriately reply to a variety of situations and user requests. [0018]
  • In addition, since the conventional multi-agent cooperating system shown in FIG. 23 is composed as mentioned above, all of the agents must capture the format, contents and manner of use of the user information administering section. As a result, the composition of the whole system and the agents would become complicated. Further, it has been impossible to cope with a plurality of users. [0019]
  • Moreover, since the agent itself contains the definitions relative to the manner of cooperative operation to be performed with a suitable judgment of the actual situation for processing the request from the user, the amount of described contents from the agent would be enormous. [0020]
  • Since the same cooperative operation is repeated for the same request each time the user makes a request, approximately the same time is consumed at every request so as to cause low efficiency. [0021]
  • Further, since a single memory is used as a space for performing a cooperating process by a plurality of agents, the system description would be complicated and the processing efficiency would be lowered from a standpoint of effectively utilizing the services by the user in such a distributed environment as a number of computers are mutually coupled via a network. [0022]
  • SUMMARY OF THE INVENTION
  • The present invention has been attained to overcome problems as mentioned above, and is aimed at providing a multi-agent cooperating system and method which is capable of readily defining flexible cooperative operation of a wide application range and attending to the user requests, and system change and extension. [0023]
  • It is another object of this invention to provide a multi-agent cooperating system capable of operating in accordance with a plurality of users by a simple system composition without adding a complicated interpreting function to the agent. [0024]
  • It is further an object of this invention to provide a multi-agent cooperating system which is capable of efficiently processing the user request in a shorter time. [0025]
  • To attain such objects as aforementioned, a multi-agent cooperating method according to this invention provides services as requested by a user by cooperation of a plurality of agents, the planning method provides separation of which is obtaining combination of functions for attaining services requested by a user, data to be transmitted and received between the functions, and plans for the order in which the data is executed from resource division, which is a problem of distributing tasks so that tasks for attaining services for elemental functions so as to maintain the balance of load state or operating state of the resource connected to the elemental function or the elemental function for attaining the service requested by the user such that the problem is solved by the divided process for each problem. [0026]
  • Further, in the aforementioned multi-agent cooperating method, the definition of the specification with regard to the group of the members of the aforementioned agent and the procedure of the cooperation between the agents, the definition of the elemental function, and the definition of the plan, are defined separately from each other, and the agent executes the cooperative operation in accordance with the definition. [0027]
  • According to another embodiment of this invention, a multi-agent cooperating system for providing services in accordance with a request from user by cooperation of a plurality of agents comprises: one or more elemental function agents for providing elemental functions; one or more planning agents having definitions relating to the plan and having the ability to distribute tasks; and a field manager connected via said elemental function agents and planning agents, having definitions relating to the collection of the members of the planning agents and the elemental function agents and the procedure of cooperation between these two agents so as to administer the cooperative operation between the agents. [0028]
  • Further, in the aforementioned multi-agent cooperating system, the field manager comprises: a communicating means for transmitting/receiving information to/from the agents or the user; a cooperative definition data base for storing the members of the agent to perform the cooperative operation and the definition of the procedure of the cooperative operation; and a cooperative operation performing means for transmitting a message to make the agent perform the cooperative operation with reference to the definition of said cooperative definition data base via the communicating means. [0029]
  • Furthermore, according to the multi-agent cooperating system, the planning agent comprises: a communicating means for transmitting/receiving information to/from said agent or user; a rule base for storing rules to generate a plan; a planning performing means for generating a plan with reference to the rule base; an estimating data storing means for storing basics to estimate the request contained in the message from the field manager; and an estimating means for making estimation in accordance with the data contained in said estimating data storing means. [0030]
  • Further, according to the multi-agent cooperating system of this invention, the elemental function agent comprises: a communicating means for transmitting/receiving information to/from the agent or user; an functional definition storing means for storing a definition of an elemental service function or a part thereof; a service executing means for executing service or a part thereof in accordance with the contents of said elemental function definition storing means; an estimating data/profile storing means for storing estimating basics and profiles; and an estimating means for estimating in accordance with the data stored in said estimating data/profile storing means. [0031]
  • Further, according to the invention, there is provided a multi-agent cooperating method for executing cooperative operation using the multi-agent cooperating system, comprising the steps of: receiving a service request from a user in said field manager; transmitting the service request, with instructions related to cooperation added thereto, to the planning agent; executing estimation and planning in accordance with the service request and the instructions in the planning agent; judging if the result of the estimation in accordance with the service request and the instructions has reached a prescribed criterion and further the plan has been obtained; asking for the elemental function agent to make an estimation as to load; returning the result of the load estimation to the planning agent in the elemental function agent; making a general estimation of the estimated result from the planning agent and the elemental function agent; determining a planning agent to ask for the work to execute the service based on the result of the general estimation and informing this agent of that; and executing the process in accordance with the plan or with the elemental function agent in the entrusted planning agent. [0032]
  • Further, a multi-agent cooperating method for executing cooperative operation using said multi-agent cooperating system comprising the steps of: transmitting the profile stored in the estimating data/profile storing means to the field manager and the planning agent in the elemental function agent to be newly installed in the multi-agent cooperating system; estimating the contents of the profile received from the elemental function agent in the field manager and the planning agent; judging if the contents of the profile should be registered; and registering the elemental function agent in the cooperative definition data base as a member. [0033]
  • Further, according to the multi-agent cooperating system of this invention, as estimating criterion for entrusting and accepting tasks in the agent, there are provided classes of: restrictions that must be satisfied necessarily in view of specification; basics with relatively wide allowance which are prioritized in accordance with user or user's preference; and basics related to cost of resource that can be calculated from the load state of the CPU or associated equipments. [0034]
  • According to another embodiment of this invention, a multi-agent cooperating system for providing services in accordance with the request from the user by cooperative operation of a plurality of agents, comprising: one or more planning agents having definitions as to plan and ability of distributing tasks; a means for describing the plan in the definition of the planning agent; and a describing means for defining the plan for the user. [0035]
  • Further, in the aforementioned multi-agent cooperating system, the planning agent comprises a plan base for storing the plan having been described by the plan describing means, and a plan interpretation executing means for interpreting and executing the contents of the plan base. [0036]
  • According to another embodiment of this invention, a multi-agent cooperating system for providing services in reply to a request from user by cooperative operation of a plurality of agents, comprising: a user definition storing means provided for each user in order to store personal information related to each user; and a user agent provided to correspond to each user definition storing means for processing the request from the user by, for example, adding options thereto and then transmitting it to the agent. [0037]
  • In the aforementioned multi-agent cooperating system, the personal information contains user attribute representing objective characteristics of each user; and options to be used when requesting services. [0038]
  • According to another embodiment of this invention, a multi-agent cooperating system for providing services in reply to the request from user by cooperative operation of a plurality of agent, comprising: agents for providing services requested by the user; a field manager for administering the cooperative operation among the agents by adding cooperative information as instructive information related to the cooperative operation to the message, wherein a plurality of agents cooperate in the field being within the scope of the field manager using the messages. [0039]
  • In the aforementioned multi-agent cooperating system, the agent comprises a means for executing instructions contained in the instructive information corresponding to the instructive information. [0040]
  • In the aforementioned multi-agent cooperating system, there are provided a means for executing the services of the agent, an estimating means for estimating input messages, and an attributes storing means for storing attributes of the agents. [0041]
  • According to another embodiment of this invention, there is provided a multi-agent cooperating system for providing services in reply to a request from a user by cooperative operation of a plurality of agents, comprising a means for storing a combination of a pattern requested by the user and an agent corresponding to the request among the agents available for processing the request, wherein when a request for the same pattern is input, the request is preferentially distributed to this agent. [0042]
  • According to another embodiment of this invention, there is provided a multi-agent cooperating system for providing services in reply to a request from a user by cooperative operation of a plurality of agents, comprising a means for storing the pattern of request from the user and agent which would provide an estimated value equal to or more than a predetermined estimation criterion among the agents available for processing the request, wherein when a request of the same pattern is input again, the cooperative operation is executed only between the agents. [0043]
  • According to another embodiment of this invention, there is provided a multi-agent cooperating method for executing cooperative operation using a multi-agent cooperating system for providing services in reply to a request from a user comprising agents for providing services requested by a user, field managers for managing cooperative operations among the agents, so that a plurality of agents cooperate using message in a field being a scope of management by the field manager, wherein the field manager performs functions comprising the steps of: informing the agents in the field of the request from the user; presenting the conditions to accept the requests from the agent having been judged to be able to process the request to the user collectively; and making an agent corresponding to the condition designated by the user among the presented conditions execute the request. [0044]
  • According to another embodiment of this invention, a multi-agent cooperating system for presenting services corresponding to a request from a user by cooperative operation of a plurality of agents, comprising a means for presenting conditions to accept the processing by the agent for the request from the user collectively to the user, making the user select an appropriate agent, and entrusting the execution of the process to the selected agent. [0045]
  • In the multi-agent cooperating method of this invention, there are provided a means for defining the planning process and resource distributing process by separating them from each other, and a means for solving both process by two clearly divided processing steps. As a result, it is possible to deal with process of wide range, and the system for defining and processing the process can be simplified so that specification of the agents for planning and resource distribution and of the total system can be simplified. [0046]
  • Further, it is possible to simplify the cooperative definition and process by the means for defining the specification related to the procedure of the cooperation of the collection of the members of the agents and the agents to perform the cooperation from the definition of the elemental function and the definition of the plan and the means for executing the cooperative operation by the agents in accordance with the definition, so that the specification of the agents and the total system as to the cooperation can be simplified. [0047]
  • Further, providing the means for defining the plan for planning agent separately from the elemental function agent for providing an elemental function and the means for processing based on that would serve to clarify and simplify the total specification of the system and the specification of each agent as to the planning and the resource distribution. In addition, since the definition as to the plan is collected, the definitions for the other agents would be more highly independent from other portions of the system. [0048]
  • Since the means for collecting the processes related to the specification on the cooperative operation to the field manager is provided, the specification of each agent relating to the cooperation and the specification of the total system is clarified and simplified. Due to the collection of the definition on the cooperation, the other portion of the system related to the definition of the agents would be highly independent from the definition of other portions of the system. [0049]
  • In addition, for introducing a new elemental function agent to the system, due to the provision of a means for communicating information of the profile of an elemental function agent to be introduced into a proper region to the planning agent or field manager of the proper region, and a means for judging the utility of the newly incorporated elemental function agent by each planning agent and the field manager and registering the elemental function agent as a target to entrust the process when judging as available, when the elemental function agent is extended for the system, the system would automatically renew the necessary data due to the extension of the elemental function agent. As a result, it is totally unnecessary to manually renew the existing system, and no description other than the agent itself would be necessary so that the independency of the definition of the agent would become higher. [0050]
  • Further, three classes of criterion with different allowance range or weight are established as estimating criterion for task entrusting/accepting of the agents, and a means for defining the classes and estimating them for each class is provided. As a result, the definition of estimation and the provision of the process can be simplified so that a variety of estimation corresponding to situations can be made and the efficiency of the estimation would be improved. [0051]
  • In addition, since a means for freely defining the plan in the planning agency by the end user is provided, it is possible for the end user and the other programs to produce, as required, agents which have their own plan. As a result, the extension degree and flexibility are increased. [0052]
  • In the multi-agent cooperating system according to this invention, each user would access the multi-agent cooperating system through the user agent that uniquely manages its own information. The user agent modifies options in reply to the request of services from the user and converts them into appropriate forms which could be interpreted by each agent to be transmitted. In addition, the user agent can also obtain user information by almost the same communication as in the case of making communication between the agents. If a plurality of users exist, the user agent is connected to the multi-agent cooperating system in correspondence to each user. [0053]
  • Further, according to the multi-agent cooperating system of this invention, the cooperative operation may be made in accordance with the contents of the cooperative information transferred from the field manager, so that the agent can easily realize complicated operations just by providing means corresponding to the contents of information included in the cooperative information. [0054]
  • In the multi-agent cooperating system of this invention, the requested pattern and the agent corresponding to the request are stored, so that the stored agent can preferentially process when a request of the same pattern is input, without unnecessarily repeating the same cooperative operation for the same request each time. [0055]
  • In the multi-agent cooperating system of this invention, further, the requested pattern, and among the agents corresponding to the request agents having values not less than the estimating criterion of the field are stored, and when a request of the same pattern is input again, the cooperative operation limited just between these agents are carried out. [0056]
  • According to the multi-agent cooperating system of this invention, the user inputs a request without designating any agent, then conditions of agents available for processing the request are presented. The user selects an agent to actually perform the processing.[0057]
  • The above and other objects, features and advantages of this invention will become clear from the following description of the preferred embodiment thereof, taken in conjunction with the accompanying drawings. [0058]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram showing a general composition of a multi-agent cooperating system according to a first embodiment of this invention; [0059]
  • FIG. 2 is a block diagram showing the inner composition of the field manager according to the first embodiment of this invention; [0060]
  • FIG. 3 is a block diagram of the inner composition of a planning agent according to a first embodiment of this invention; [0061]
  • FIG. 4 is a block diagram showing the inner composition of an elemental function agent according to a first embodiment of this invention; [0062]
  • FIG. 5 is a flow diagram representing the cooperative operation of the agent according to the first embodiment of this invention; [0063]
  • FIG. 6 is a flow diagram representing the operation of a new elemental function agent when started according to the first embodiment of this invention; [0064]
  • FIG. 7 is a block diagram showing a planning agent when a means for describing the plan is provided in the definition of the planning agent according to a second embodiment of this invention; [0065]
  • FIG. 8 is a block diagram of a multi-agent cooperating system according to a third embodiment of this invention; [0066]
  • FIG. 9 is a profile table showing contents of a user definition storing section according to a third embodiment of this invention; [0067]
  • FIG. 10 is a preference table showing contents of a user definition storing section according to the third embodiment of this invention; [0068]
  • FIG. 11 is a block diagram showing a multi-agent cooperating system corresponding to multi-users according to the third embodiment of this invention; [0069]
  • FIG. 12 is a block diagram showing a multi-agent cooperating system according to a fourth embodiment of this invention; [0070]
  • FIG. 13 is a flow diagram showing the function of the multi-agent cooperating system according to the fourth embodiment of this invention; [0071]
  • FIG. 14 is a block diagram showing a multi-agent cooperating system according to a fifth embodiment of this invention; [0072]
  • FIG. 15 is a flow diagram showing the operation of a multi-agent cooperating system according to the fifth embodiment of this invention; [0073]
  • FIG. 16 is a flow diagram showing the operation of a multi-agent cooperating system according to a sixth embodiment of this invention; [0074]
  • FIG. 17 is a block diagram showing a multi-agent cooperating system according to a seventh embodiment of this invention; [0075]
  • FIG. 18 is a flow diagram showing the operation of a multi-agent cooperating system according to a seventh embodiment of this invention; [0076]
  • FIG. 19 is a block diagram of a conventional multi-agent cooperating system; [0077]
  • FIG. 20 is a flow diagram showing the general operation of the conventional system; [0078]
  • FIG. 21 is a detailed flow diagram of conventional steps to determine whether the service request can be accepted; [0079]
  • FIG. 22 is a detailed flow diagram showing steps to carry out entrusted services in a conventional multi-agent cooperating system; and [0080]
  • FIG. 23 is a block diagram showing a conventional multi-agent cooperating system.[0081]
  • DETAILED DESCRIPTION
  • First Embodiment [0082]
  • A first embodiment according to the present invention will now be described with reference to the drawings. [0083]
  • FIG. 1 is block diagram showing a general composition of a multi-agent cooperating system according to a first embodiment of this invention. This multi-agent cooperating system comprises: a user interface [0084] 1 for communication between an end user and a multi-agent cooperating system of this embodiment; a field manager having definitions of collection of members of agents to execute cooperative operations and procedures of the cooperative operations in the multi-agent cooperating system so as to make the other agent execute cooperative operation; a planning agent having definitions as to plan; and an elemental function agent having an elemental function to perform services.
  • FIG. 2 is a block diagram showing the inner composition of the [0085] field manager 2 in FIG. 1. In FIG. 2, the field manager 2 comprises: a communicating section 5 for transmitting/receiving information to/from the agent or the user; a cooperative definition data base 6 for storing definitions of procedures of member and cooperative operations of agents to perform the cooperative operation; and a cooperative operation executing section 7 for communicating message for making other agent execute cooperative operation via the communicating section 5 referring to the definition of the cooperative definition data base 6.
  • FIG. 3 is a block diagram showing the inner composition of the [0086] planning agent 3 in FIG. 1. The planning agent 3 comprises: a communicating section 8 for transmitting/receiving information to/from other agents or a user; a rule base 9 for storing rules to produce plans; a planning executing section 10 for producing plans with reference to the rule base 9; an estimating data storing section 11 for storing criterion to estimate the request contained in the message from the field manager 2; and an estimating section 12 for making estimation in accordance with the contents of the estimating data storing section 11.
  • FIG. 4 is a block diagram showing the inner composition of the [0087] elemental function agent 4. In FIG. 4, the elemental function agent 4 comprises: a communicating section 13 for transmitting/receiving information to/from other agents or a user; a functional definition storing section 14 for storing definitions of services or elemental functions being a part thereof; a service executing section 15 for executing services or a part thereof in accordance with the contents of the functional definition storing section 14; an estimating data/profile storing section 16 for storing estimating criterion and profile; and an estimating section 17 for making estimation in accordance with the estimating data and profile.
  • The term planning signifies a problem to obtain combination of functions to attain services requested from a user, data to be transferred between functions, and plans being the procedures to execute them. The term resource distribution is a problem to distribute tasks to attain the services for the elemental function so that the balance between the elemental function to attain the plan or operating state of resources coupled to the elemental function or the load state can be maintained. [0088]
  • As a significant feature of this invention, the planning and the resource distribution are separated from each other, so that the problem can be solved by a process of two stages divided for each problem. Further, the specification as to the procedure of cooperation between the agents and the collection of the members of the agents to cooperate, the elemental function and the plan are defined separately from each other so that the agents can cooperate in accordance with the definitions. As a result, it is possible to easily describe the application and change the definitions. [0089]
  • A cooperative operation according to this embodiment will now be described with reference to the drawings. FIG. 5 is a flow diagram showing the cooperative operation of the agents in this embodiment. The cooperative operation of the agents includes: a [0090] step 21 for receiving a service request from the user by the field manager via the user interface 1; a step 22 for adding instructions relating to the cooperation to the service request and transmitting it to the planning agent 3; a step 23 for making estimation and planning in accordance with the service request and the instructions; a step 24 for judging if the estimated result reaches a prescribed criterion and the plan has been obtained; a step 25 in which the planning agent 3 entrusts the elemental function agent 4 to estimate the load; a step 26 in which the elemental function agent 4 estimates the load and returns the estimated result; a step 27 in which the field manager 2 generally estimates the estimated result returned from the planning agent 3 and the elemental function agent 4; a step 28 in which the field manager 2 determines the planning agent 3 for entrusting the task to actually attain the service from the result of the general estimation and transmitting the determined result; and a step 29 in which the entrusted planning agent 3 executes the process with the elemental function agent 4 in accordance with the aforementioned plan.
  • Details of the cooperative operation will now be described with reference to FIG. 5. [0091]
  • In the [0092] step 21, the field manager 2 receives the service request having been input by the user through the interface 1 via the communicating section 5. In the step 22, the field manager 2 transfers the instructions generated by the cooperative operation executing section 7 in accordance with the description in the cooperative definition data base 6 which is added to the service request from the user to appropriate planning agents 3 that are members to the planning agent 3. In step 23, the planning agent 3 estimates the specification of the services requested by the user in the estimating section 12 in accordance with the contents of the estimating data storing section 11, and the planning execution section 10 generates plan to execute the service requested in accordance with the contents of the rule base 9. In step 24, the planning agent 3 judges if the aforementioned estimated result has reached the prescribed criterion and the plan has been obtained. If the criterion is not satisfied or no plan is obtained, the planning agent 3 terminates its operation. Otherwise, in step 25, the planning agent 3 entrusts a necessary elemental function agent 4 via the communicating section 8 to estimate the position of the device associated with the elemental function agent 4 and the load via the communicating section 8. At this time, necessary information for the estimation is transmitted with the entrust. In step 26, the elemental function agent 4 receives the entrust via the communicating section 13, and estimates the received information in accordance with the contents in the estimating data and profile storing section 16, and returns the estimated result to the planning agent 3 via the communicating section 13. In step 28, the field manager 2 determines a planning agent 3 for entrusting the task to actually attain the services on the basis of the result of the general estimation for entrusting it to execute the task. In step 29, the planning agent having been entrusted processes the task together with the appropriate elemental function agent 4 in accordance with the aforementioned plan.
  • In the aforementioned process, there are three types of estimation criterion for entrusting or accepting the task, namely the process for the planning agent or the [0093] elemental function agent 4. These are a criterion that must be necessarily satisfied in view of the specification, a criterion having a wide range of allowance and being preferentially graded by the user based on the user requirements, and a criterion as to the cost of a resource calculated from the load state such as associated equipments or CPU. The estimation is made on the basis of these criterion.
  • In the [0094] aforementioned steps 23 and 24, the planning agent 3 estimates the specification of the service request from the user in the estimating section 12, and terminates the operation at this time point if the result does not reach the prescribed criterion. Otherwise, it would be possible that the planning executing section 10 generates plan and proceeds to the step 25 if the plan is obtained.
  • Further, it is also possible to return the estimated result of the [0095] elemental function agent 4 to the field manager 2.
  • In addition, the general estimation of the [0096] step 27 can also be presented to the user via the user interface 1 in an appropriate form of the total estimation result without performing in the field manager 2 to be executed by the user. Also, it is possible in the same manner that the determination of the entrusted agent in step 28 is executed by the user.
  • An operation of this embodiment when a new [0097] elemental function agent 4 is started will be described with reference to the drawings. FIG. 6 is a flow diagram representing operations associated with the start of the new elemental function agent 4 according to this embodiment. The operation associated with the start of the new elemental function agent 4 comprises: a step 31 in which the user inputs a new elemental function agent 4 to the system; a step 32 in which the elemental function agent 4 transmits the profiles of the estimating data and the profile storing section 16 to the field manager 2 and the planning agent 3; a step 33 in which the field manager 2 and the planning agent 3 estimates the contents of the received profile; a step 34 for judging if the field manager 2 and the planning agent 3 are to be registered; and a step 35 in which the field manager registers the elemental function agent 4 in the cooperative definition data base 6.
  • Details of the cooperative operation will now be described with reference to FIG. 6. [0098]
  • In [0099] step 31, the user install a new elemental function agent 4 into the system. In step 32, the elemental function agent 4 transmits the estimating data for estimating the specification and the profile in the estimating data and profile storing section 16 via the communicating section 13 to the field manager and the planning agent 3. In step 32, the field manager 2 and the planning agent 3 receive the profile through the communicating section 5 and 8. In step 33, the field manager and the planning agent 3 refer the contents in the profile to the contents in the cooperative definition data base 6, estimating data storing section 11, and the rule base 9 for estimating if the elemental function agent 4 is necessary for the field manager 2 or the planning agent 3. In step 34, if it is unnecessary for the field manager 2 or the planning agent 3 to be registered, the process in the field manager 2 and the planning agent 3 terminates. If it is judged as necessary, in step 35, the field manager 2 registers the elemental function agent 4 as a member in the cooperative definition data base 6.
  • Second Embodiment [0100]
  • A second embodiment of this invention will now be described with reference to the drawings. [0101]
  • FIG. 7 shows an embodiment having a means for describing plan in the definition of the [0102] planning agent 3. The function of the planning agent 3, communicating section 8, the estimating data storing section 11, and the estimating section 12 is almost the same as that in FIG. 3. The planning agent 3 further comprises a plan describing section 18 for making the user describe the plan, a plan base 19 for storing plan described by the plan describing section 18, and a plan interpretation executing section 20 for interpreting and executing the contents of the plan base 19.
  • In this embodiment shown in FIG. 7, the user uses the script language presented in the [0103] plan describing section 18 to describe a combination of functions to attain a certain service, data to be transmitted/received between the functions, and plan being a procedure to execute the data. The contents of the description are stored in the plan base by the plan describing section 18 so as to define a planning agent having a new plan by the user definition. The plan having been stored in the plan base 19 will be interpreted and executed by the plan interpreting/executing section 20.
  • The [0104] plan describing section 18, the plan base 19, and the plan interpreting section 20 can also be provided together with the rule base 9 and the planning executing section 10 of the planning agent 3 shown in FIG. 3. In this case, the plan base 19 is firstly tried for application in reply to the service request from the user, and then the planning executing section 10 executes the plan generation. As a result, possibility of making the plan generation taking a long time be unnecessary would arise, so that the efficiency for obtaining a plan by the planning agent 3 can be improved.
  • Third Embodiment [0105]
  • FIG. 8 shows a third embodiment of this invention. The multi-agent cooperating system comprises an [0106] agent group 41 composed of a plurality of agents for providing services to the user; a user definition storing section 42 for storing personal information of the user; a user agent 43 for referring to the contents of the user definition storing section 42 and converting a request from the user into appropriate form to be transferred to the agent group 41. FIGS. 9 and 10 show contents of the user definition storing section 42 according to this embodiment which respectively represent a profile table 44 for standing for the user attributes being user's objective characteristics such as name, section etc. and a preference table 45 representing preferences of the user for the option when service is requested. FIG. 11 shows a correspondence to multi-user of a multi-agent cooperating system which is composed to be capable of coping with a plurality of users in this embodiment. As shown in FIG. 11, each of the user agents 43 is coupled to the agent group 41 in correspondence to each user.
  • In the multi-agent cooperating system composed as mentioned above, the user inputs a request via the user interface presented by the [0107] user agent 43. The user agent having received the request refers to the preference table 45 and the profile table 44 of the user definition storing section 42 and carries out supplementary processing such as adding an option such as the resolution shown in FIG. 10 to the request so as thereafter to input to the agent group 41. Namely, the request input by the user is converted into an appropriate form reflecting the characteristics of the user so that the system can interpret the request input by the user to be transferred to the agent group 41.
  • Further, the [0108] user agent 43 returns a value of user's attributes requested by referring to the user definition storing section 42 when user characteristics are requested by the agent group 41 side.
  • As mentioned above, the [0109] user agent 43, in reply to the request from the user, or the request from the agents forming the agent group 41, the multi-agent cooperating system side need not take the form and contents of the user information into consideration which contributes to the simplification of the structure. Further, it is easily possible to cope with a plurality of users just by coupling a user agent 43 being a exclusive module for each user to the system.
  • Fourth Embodiment [0110]
  • FIG. 12 shows a fourth embodiment of this invention. The multi-agent cooperating system according to this embodiment comprises a plurality of [0111] agents 46 for providing services to the user and has a field 47 for prescribing method of cooperation. The field manager 48 instructs and manages the cooperative operation between the agents 46 in the field 47. A variety of information is communicated between the field manager 48 and the agents 46 via the message 49. The field manager 48 adds cooperative information 50 to the message 49 for giving instructions relating to the cooperative operation. Each agent 46 includes a selector 51 for interpreting the cooperative information 50 contained in the message 49 and determining the cooperative operation, an executing section 52 for executing the service of the agent 46, an estimating section 53 for estimating the message having input, and an attributes storing section 54 for storing attributes of the agent 46.
  • FIG. 13 is a flow diagram showing process according to this embodiment. The process will now be described with reference to this FIG. 13. [0112]
  • In the multi-agent cooperating system composed as mentioned above, the [0113] field manager 48 adds the cooperative information 50 to the message representing the request from the user (step 221). The cooperative information 50 in this embodiment is any one of the instructive information for entrusting the execution of the service, information for requesting the present of information contained in the agent 46, and information for designating an estimating method such as the preferential degree for the estimation. The agent 46 reads the message 49 to which the cooperative information is added (step 222), and the selector 51 determines the process in accordance with the contents of the cooperative information 50 (step 223). If the contents of the cooperative information 50 is such information as to entrust the execution of the services, the selector 51 transfers the message 49 to the executing section 52, which then execute the services indicated in the message 49 (step 224). If the contents of the cooperative information 50 is such information as to request the presentation of information, the selector 51 receives the attributes of the agent 46 indicated in the cooperative information from the attributes storing section 54 and transfers them outside (step 225). If the contents of the cooperative information 50 is to designate the estimating method, the selector 51 transfers the message 49 containing the cooperative information 50 to the estimating section 53, which then makes an estimation in accordance with the cooperative information (step 226).
  • As mentioned above, in this embodiment, the [0114] field manager 48 converts the contents of the cooperative information 50 and transfers them to the agent 46. As a result, it is possible to readily perform complicated cooperative operations simply by previously providing the means for executing the cooperative operation in accordance with the contents of the instructive information contained in the cooperative information 50, namely the executing section 52, the estimating section 53, and the attributes storing section 54 in each agent 46.
  • Fifth Embodiment [0115]
  • FIG. 14 shows a fifth embodiment of this invention. In FIG. 14, components equivalent to those in the previous embodiment are designated by the same numerals. As a significant feature of this invention, there is provided an entrusted [0116] target memory section 55 as a means for storing a combination of request patterns from a user and the agent that actually accepted the request as a set.
  • FIG. 15 is a flow diagram showing a process of this embodiment. [0117]
  • In a multi-agent cooperating system composed as mentioned above, the [0118] field manager 48 reads the request from the user (step 231), and judges if the request pattern corresponding to the request exists in the entrusted target memory section 55 (step 232). If no corresponding pattern exists, normal processing is executed in accordance with cooperating rule previously prescribed (step 233). Namely, the contents of the request from the user are notified to the agent 46 in the field 47, and this agent 46 estimates the request, and if it judges to be able to process the request by itself, it inform the field manager 48 of that. The field manager 48 selects one agent 46 to process the request from the user in accordance with predetermined estimating criterion as shown in the first embodiment, for example. Thus, the agent 46 having finally processed the request and the request pattern are stored in the entrusted target memory section 55 as a set (step 234). If the request pattern corresponding to the entrusted target memory section 55 exists, the agent 46 having the entrusted target memory section 55 containing the request is preferentially and directly asked to execute the request (step 235).
  • As mentioned above, according to this embodiment, it is unnecessary to repeat the same cooperative operation each time so as to improve the processing efficiency since the [0119] same agent 46 stored in the entrusted target storing section 55 executes the process.
  • Sixth Embodiment [0120]
  • As a significant feature of the fifth embodiment, the set of the request pattern and the [0121] agent 46 having finally executed the request has been stored in the entrusted target storing section 55. In this embodiment, among the sets of the request and the agent having accepted the process of the request but not finally executing the process, those having an estimated value equal to or more than a threshold value after being referred to a predetermined estimating criterion that is a threshold contained in the field manager are stored in the entrusted target storing section 55.
  • FIG. 16 is a flow diagram showing the process according to this embodiment. [0122]
  • The [0123] field manager 48 reads the request from the user (step 241), and judges if the corresponding request pattern exists in the entrusted target memory section 55 (step 242). If no request pattern exists, normal processing is executed in accordance with a predetermined cooperating rule (step 243). At this time, among the agents 46 having an accepted to process the request, the group of the agent 46 having estimated value equal to or larger than a predetermined threshold of the field manager 48 together with the request pattern is stored in the entrusted target storing section 55 (step 244). When the request is input again, if the request pattern corresponding to the request exists in the entrusted target memory section 55, the request is presented only to the agent 46 stored in the entrusted target memory section 55, so that the cooperative operation is executed just between these agents 46 (step 245).
  • Incidentally, in the [0124] aforementioned embodiments 5 and 6, the entrusted target memory section 55 has been composed so as to be used by the field manager 48, but alternatively it is also possible to make the entrusted target memory section 55 be used by the user agent in the third embodiment, so that the user agent is ordered to limit the agents to be entrusted to process the request depending on the request pattern.
  • Seventh Embodiment [0125]
  • FIG. 17 shows a seventh embodiment of this invention. As a significant feature of this embodiment, there is provided a [0126] user selecting section 56 which presents the conditions for accepting the process sent from the agent 46 collectively to the user so that the user selects an appropriate agent 46 and to entrust the agent 46 to actually process the request based on the result of the selection. The other components are the same as those in fifth and sixth embodiments so as to be omitted from explanation.
  • FIG. 18 is a flow diagram showing the process according to this embodiment. [0127]
  • This embodiment is composed of the steps of: reading the request from the user by the field manager [0128] 48 (step 251); announcing the request to the agent 46 in the field 47 (step 252); sending conditions for executing the process to the agent 46 having judged to be able to process the request (step 253); presenting the conditions to the user using the user selecting section 56 by the field manager (step 254); selecting by the user an agent 46 having presented conditions that are the closest to the request of its own from the presented condition; actually entrusting the selected agent 46 by the field manager 48 to execute the process for the request (step 256); and processing the request by the entrusted agent 46 (step 257).
  • The operation of this embodiment will now be described with reference to FIG. 18. [0129]
  • In FIG. 251, the [0130] field manager 48 reads the request presented to the field 47 from the user. In step 252, the contents of the read request are sent to each agent in the field 47. In step 253, if the noticed agent 46 estimates the request as being processable by itself, it returns conditions for accepting the request. In step 254, the field manager 48 presents the conditions returned from the agent 46 to the user in a form selectable by the user through the user selecting section 56. In step 255, the agent 46 having presented the conditions closest to the request of its own among the presented conditions is selected. In step 256, the field manager 48 entrusts the agent 46 which corresponds to the conditions selected by the user to execute the process of the request. In step 257, the entrusted agent 46 executes the request.
  • As mentioned above, according to this embodiment, since detailed contents which are capable of being actually processed by the [0131] agents 46 even when the user inputs a request without designating the target agent so that the user actually selects the process and makes the agent execute the process, the utility of the user can be significantly increased.
  • Thus, by virtue of the aforementioned composition of this invention, the following advantages are obtained: [0132]
  • The planning, the resource distribution and the elemental function can be separately defined. As a result, the description of the application is simplified and eased, and also the definitions can be readily changed. Further, the total system mounting process can be made easily. [0133]
  • The cooperative definition can be made separately from those of the planning, resource distribution, and elemental function. Therefore, the description of the application is simplified and eased. The cooperative definition can also be easily changed. [0134]
  • Since the definition of the cooperation is described by the field manager, that of the plan by the planning agent, that of the elemental function by the elemental function agent, respectively, and a frame work to make them cooperatively function is provided, applications and total system can be readily obtained. [0135]
  • When an elemental function agent is introduced, the profile describing the contents relating only to the agent is automatically broadcasted and the necessary portions are automatically renewed. In consequence, it is unnecessary to make any renewal or rearrangement of the other portions of the system, which would improve the modularity between the elements. [0136]
  • Since three classes of estimating criterion are provided, and the estimation is made in the order from the hardest restriction, the estimating efficiency is improved. Also, the criterion is defined independently by each class for estimation, it is possible to provide the estimating data definition and the estimating process. [0137]
  • The definition of plan is opened to the user so as to be instantly suited to the needs of the user, and the planning process which is normally complicated and requires significant time to execute may be omitted. Consequently, the total process efficiency can be enhanced. [0138]
  • Since the user input is converted into an appropriate form reflecting the characteristics of the user within a scope that is acceptable by the system so as to be then transferred to the multi-agent cooperating system of this invention, the form or contents of the user information need not be recognized by the system side, which contributes to simplify the composition. Further, it is possible to easily cope with a plurality of users by simply coupling a module exclusive for each user to the system. [0139]
  • In addition, the cooperative operation of the agent can be changed by changing the contents of the cooperative information by the field manager, it is possible to realize a complicated function merely by mounting simple agents, and further it is possible to perform different cooperative operations when the field is changed within the same agent. [0140]
  • In addition, when the same request is repeatedly input, the process of the request is directly entrusted to the same agent as previously functioned, so it is unnecessary to repeat the same cooperative operation, which contributes to improved processing efficiency. [0141]
  • Moreover, by storing the agents which are capable of processing the request from the user and have an estimated value equal to or larger than the estimating criterion, it is possible to perform the cooperative operation just between these agents. Accordingly, the time required to execute the cooperative operation can be shortened since the range of the cooperation is shortened, and the request from the user can be replied to with high accuracy, so as to improve the processing efficiency. [0142]
  • Moreover, since the system operates at the time that the user inputs the request in a diffusion environment, even if the user does not recognize where the services are and which resources are capable of meeting its request, the agent which has the service and the resource for meeting the request can reply by itself. As a result, the utility of the services and the resources in the diffusion environment can be easily enhanced. [0143]

Claims (3)

What is claimed is:
1. A multi-agent cooperating system for providing services in reply to a request from a user by cooperative operation of a plurality of agents, said system comprising:
a means for storing a combination of a request pattern from the user and selected agent suited to execute the request among the agents available for processing the request;
means for distributing a subsequent request of the same pattern to the selected agent.
2. A multi-agent cooperating system for providing services in reply to a request from a user by cooperative operation of a plurality of agents, said system comprising:
a means for storing a request pattern from the user and a portion of said plurality of agents which provide an estimation value higher than a predetermined estimation criterion;
means for determining cooperative operation said portions of agents upon receipt of a request of the same pattern.
3. A multi-agent cooperating method for executing cooperative operation by use of a multi-agent cooperating system having agents for providing services requested from a user and a field manager for managing cooperative operation of the agents so as to provide services in reply to a request from a user by cooperative operation of a plurality of agents using messages in a field within a scope of the management by the field manager, said method comprising the steps of:
transmitting information from said field manager to the agents in the field of the request from the user;
determining agents which can process the request;
presenting conditions to said user to accept the request from the agents which can process the request; and
executing the request by an agent corresponding to conditions designated by the user.
US09/866,682 1993-04-20 2001-05-30 Multi-agents cooperating method and system Abandoned US20010023439A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/866,682 US20010023439A1 (en) 1993-04-20 2001-05-30 Multi-agents cooperating method and system

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
JP9268493 1993-04-20
JPHEI5-92684 1993-04-20
JP6034454A JPH076142A (en) 1993-04-20 1994-03-04 Multiagent coordination system and its method
US22873294A 1994-04-18 1994-04-18
US08/803,330 US6285977B1 (en) 1993-04-20 1997-02-21 Multi-agents cooperating method and system
US09/866,682 US20010023439A1 (en) 1993-04-20 2001-05-30 Multi-agents cooperating method and system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US08/803,330 Continuation US6285977B1 (en) 1993-04-20 1997-02-21 Multi-agents cooperating method and system

Publications (1)

Publication Number Publication Date
US20010023439A1 true US20010023439A1 (en) 2001-09-20

Family

ID=26373268

Family Applications (2)

Application Number Title Priority Date Filing Date
US08/803,330 Expired - Fee Related US6285977B1 (en) 1993-04-20 1997-02-21 Multi-agents cooperating method and system
US09/866,682 Abandoned US20010023439A1 (en) 1993-04-20 2001-05-30 Multi-agents cooperating method and system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US08/803,330 Expired - Fee Related US6285977B1 (en) 1993-04-20 1997-02-21 Multi-agents cooperating method and system

Country Status (2)

Country Link
US (2) US6285977B1 (en)
JP (1) JPH076142A (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040029572A1 (en) * 2000-06-14 2004-02-12 Olivier Nerot Method and system for selecting on request one or several data sources available from a communication network
US20040083261A1 (en) * 2001-03-16 2004-04-29 Thompson Simon G Multi-agent system design using role models
US7379888B1 (en) * 1997-01-21 2008-05-27 Microsoft Corporation System and method for generating a schedule based on resource assignments
US20080162566A1 (en) * 2006-12-29 2008-07-03 Sungkyunkwan University Foundation For Corporate Collaboration Quantitative estimating system for grouping of multiagent and method thereof
US20130325632A1 (en) * 2000-10-07 2013-12-05 C. Douglass Thomas Method and System for Providing Notification of Publications
US20190259373A1 (en) * 2018-02-16 2019-08-22 Fuji Xerox Co., Ltd. Information processing system and non-transitory computer readable medium storing program

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1985005315A1 (en) * 1984-05-22 1985-12-05 Toyo Boseki Kabushiki Kaisha Process for producing polyamide film
DE68925429T3 (en) * 1988-06-23 1999-12-02 Toray Industries METHOD FOR PRODUCING A POLYESTER FILM
JP3954689B2 (en) * 1997-06-12 2007-08-08 インターナショナル・ビジネス・マシーンズ・コーポレーション Message processing method, message processing apparatus, and storage medium for storing program for controlling message processing
JP3353651B2 (en) 1997-06-23 2002-12-03 松下電器産業株式会社 Agent interface device
JPH1185524A (en) 1997-09-05 1999-03-30 Toshiba Corp Device and method for processing information and recording medium recording information processing program
US6675194B1 (en) * 1998-05-05 2004-01-06 Mitel Corporation Handling different communications types by using agents to implement communication goal commands
US6163794A (en) * 1998-10-23 2000-12-19 General Magic Network system extensible by users
US6529950B1 (en) * 1999-06-17 2003-03-04 International Business Machines Corporation Policy-based multivariate application-level QoS negotiation for multimedia services
JP3944148B2 (en) 2002-10-31 2007-07-11 キヤノン株式会社 Manufacturing method of image display device
US7228187B2 (en) * 2002-12-16 2007-06-05 Rockwell Automation Technologies, Inc. System and method for interfacing multi-agent system
US7543297B2 (en) * 2003-11-24 2009-06-02 International Business Machines Corporation Collaborative planning actions and recipes
US7676539B2 (en) * 2005-06-09 2010-03-09 International Business Machines Corporation Methods, apparatus and computer programs for automated problem solving in a distributed, collaborative environment
WO2007007724A1 (en) * 2005-07-08 2007-01-18 Olympus Corporation Device, system and method for acquiring information in living body
US7224278B2 (en) * 2005-10-18 2007-05-29 Avery Dennison Corporation Label with electronic components and method of making same
JP5057361B2 (en) 2006-10-02 2012-10-24 独立行政法人 宇宙航空研究開発機構 Autonomous distributed control with resource constraints
CN102946100B (en) * 2012-10-25 2014-12-10 国网能源研究院 Agent of power consumer response system
CN102968746B (en) * 2012-10-25 2016-01-27 国网能源研究院 A kind of intelligent body of intelligent body of power consumer responding system controls and study module
EP2851760A1 (en) 2013-09-19 2015-03-25 Rigas Tehniska universitate Multi-robot system
CN110609834B (en) * 2018-05-29 2023-04-18 西安电子科技大学 Multi-source heterogeneous government affair data extraction system based on Agent
CN112714165B (en) * 2020-12-22 2023-04-04 声耕智能科技(西安)研究院有限公司 Distributed network cooperation strategy optimization method and device based on combination mechanism
CN116260882B (en) * 2023-05-15 2023-07-28 中国人民解放军国防科技大学 Multi-agent scheduling asynchronous consistency method and device with low communication flow

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4656580A (en) * 1982-06-11 1987-04-07 International Business Machines Corporation Logic simulation machine
EP0162670B1 (en) * 1984-05-19 1991-01-02 British Aerospace Public Limited Company Industrial processing and manufacturing systems
US5228137A (en) * 1985-10-29 1993-07-13 Mitem Corporation Method for controlling execution of host computer application programs through a second computer by establishing relevant parameters having variable time of occurrence and context
GB2203573A (en) * 1987-04-02 1988-10-19 Ibm Data processing network with upgrading of files
JPH0384652A (en) 1989-08-29 1991-04-10 Personal Joho Kankyo Kyokai Architecture model for human interface
US5006983A (en) * 1989-09-12 1991-04-09 Addax, Inc. Service allocation system
JPH03160526A (en) 1989-11-20 1991-07-10 Nippon Telegr & Teleph Corp <Ntt> Real time problem resolving system by agent organization
US5301270A (en) * 1989-12-18 1994-04-05 Anderson Consulting Computer-assisted software engineering system for cooperative processing environments
EP0443130A3 (en) 1990-02-22 1992-12-30 International Business Machines Corporation Processor allocation method and apparatus for multiprocessor execution of a constraint satisfaction search
JPH03246745A (en) 1990-02-26 1991-11-05 Nippon Telegr & Teleph Corp <Ntt> Distributed resource allocating system
US5295065A (en) * 1990-06-01 1994-03-15 Motorola, Inc. Resource-lot association coordinator
US5291394A (en) * 1990-06-01 1994-03-01 Motorola, Inc. Manufacturing control and capacity planning system
US5185780A (en) * 1990-10-12 1993-02-09 Tex Corporation Method for predicting agent requirements in a force management system
US5249290A (en) * 1991-02-22 1993-09-28 At&T Bell Laboratories Method of and apparatus for operating a client/server computer network
JPH05134959A (en) 1991-11-14 1993-06-01 Matsushita Electric Ind Co Ltd Remote service execution control system
US5579467A (en) * 1992-05-27 1996-11-26 Apple Computer, Inc. Method and apparatus for formatting a communication
US5440739A (en) * 1992-06-11 1995-08-08 Beck Systems, Inc. Method of maintaining updated set-up configurations in workgroups on a network

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7379888B1 (en) * 1997-01-21 2008-05-27 Microsoft Corporation System and method for generating a schedule based on resource assignments
US20040029572A1 (en) * 2000-06-14 2004-02-12 Olivier Nerot Method and system for selecting on request one or several data sources available from a communication network
US20130325632A1 (en) * 2000-10-07 2013-12-05 C. Douglass Thomas Method and System for Providing Notification of Publications
US20040083261A1 (en) * 2001-03-16 2004-04-29 Thompson Simon G Multi-agent system design using role models
US20080162566A1 (en) * 2006-12-29 2008-07-03 Sungkyunkwan University Foundation For Corporate Collaboration Quantitative estimating system for grouping of multiagent and method thereof
US7650375B2 (en) * 2006-12-29 2010-01-19 Sungkyunkwan University Foundation For Corporate Collaboration Quantitative evaluation system for multiagent grouping and method thereof
US20190259373A1 (en) * 2018-02-16 2019-08-22 Fuji Xerox Co., Ltd. Information processing system and non-transitory computer readable medium storing program
US10923108B2 (en) * 2018-02-16 2021-02-16 Fuji Xerox Co., Ltd. Information processing system and non-transitory computer readable medium storing program

Also Published As

Publication number Publication date
US6285977B1 (en) 2001-09-04
JPH076142A (en) 1995-01-10

Similar Documents

Publication Publication Date Title
US6285977B1 (en) Multi-agents cooperating method and system
CA2119085C (en) Adaptive communication system
US7062537B2 (en) Workflow services architecture
US5504837A (en) Method for resolving conflicts among distributed entities through the generation of counter proposals by transversing a goal hierarchy with acceptable, unacceptable, and indeterminate nodes
US8103760B2 (en) Dynamic provisioning of service components in a distributed system
US7240015B1 (en) Policy representations and mechanisms for the control of software
US5758078A (en) Global server for transmitting calling capability to mediator and local servers for requesting calling capability from the mediator to transmit resource capability to global server
US6401102B1 (en) Virtual geographic spatial object generating system
US20070050227A1 (en) Automated workflow composable action model
US20080281970A1 (en) Method, apparatus and computer program product for integrating heterogeneous systems
US7069260B2 (en) QOS framework system
US20060161513A1 (en) Method and a system for integrating semantic web services into an existing web service infrastructure
EP0724210A1 (en) System and method for managing operation of computer output devices
CN101164046A (en) System for application priority based on device operating mode
US8516012B2 (en) Modeling of heterogeneous multi-technology networks and services by method of translation of domain-focused user information model to common information model
US6988272B1 (en) Object collaboration apparatus
CN108667940B (en) Resource allocation method and device of cloud platform and computer readable storage medium
JPH06337729A (en) Network service system
US6754658B1 (en) Database server processing system, method, program and program storage device
JP2004362449A (en) Service providing device, service coordinator device, service providing method, service coordinating method and program, as well as computer readable recording medium having the program recorded thereon
JP2001265603A (en) Automatic division software distribution system and method therefor
JPH05134959A (en) Remote service execution control system
US6298346B1 (en) Method and apparatus for supporting cooperative activity
JPH11203228A (en) Combination system for network resources
CN115022403B (en) Information processing system for multi-channel service agent

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE