Intelligent software agent system architecture

• US 20040205772A1
• Filed: 03/21/2001
• Published: 10/14/2004
• Est. Priority Date: 03/21/2001
• Status: Active Grant

• Current Assignee: Tribridge Holdings LLC (DXC Technology Company)
• Original Assignee: Bot, Inc. (DXC Technology Company)
• Inventors: Kunstman, Pawel, Uszok, Andrzej
• Granted Patent: US 7,861,252 B2
• Time in Patent Office: Days
• US Class Current: 719/317
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A software architecture supports deployment of mobile software agents over the Internet. Mobile software agents or “bots” are bifurcated into two parts, a first part executable on a user'"'"'s client platform (“mBot”), and a corresponding second part, called “sBot,” executable on a remote “bot server”. botServer implements virtual “meeting places” for visiting bots, and provides event notification, plug-ins and other services. The new system further includes a component called “botBox” executable on another server (which may be the same as the bot server), that tracks the status and locations of running bots, handles communications, and enables continuing operation while the user is off-line. Knowledge about the user, including private information, is finely controlled by custom user profiles which are defined by the user, but made available to the remote-executing sBot only through the botBox intermediary.

Claims

1. A bot system comprising:

a first software component [mBot] for execution on a local client platform; and

a second software component [sBot] associated with the first software component for execution on a first server platform remote from the client platform;

said execution of the sBot commencing in response to a launch message initiated by the first software component; and

a third [botBox] software component for execution on a second server platform remote from the client platform;

the third software component implementing data storage for use by the first and second software components.

2. A bot system according to claim 1 further comprising a bot management application program (botMaster) executable on the local client platform, wherein the botMaster includes means for creating a user model comprising knowledge about a user of the botMaster.

3. A bot system according to claim 2 wherein the user model reflects knowledge about the user in the form of a conceptual graph.

4. A bot system according to claim 2 wherein the user model stores knowledge about the user on the local client platform in accordance with a predetermined resource description framework applying metadata.

5. A bot system according to claim 2 wherein the means for creating a user model includes means for capturing data responsive to the user'"'"'s interactions with at least one application program other than botMaster executable on the local client platform.

6. A bot system according to claim 2 wherein the botMaster includes means for creating at least one user profile based on the user model, and the botBox includes means for storing a copy of the user profile on the second server platform.

7. A bot system according to claim 6 wherein the botMaster includes a user interface enabling the user to modify the user profile so as to control what information about the user is exposed in the user profile.

8. A bot system according to claim 2 wherein the botMaster allows the user to manage a plurality of different user profiles, and further enables the user to associate a selected user profile with the said mBot.

9. A bot system according to claim 2 wherein the botMaster manages a plurality of mBots and enables the user to associate any selected one of the user profiles with each of the mBots thereby allowing the user to employ multiple mBots, each mBot carrying a user profile selected by the user as appropriate to the mBot'"'"'s task.

10. A bot system comprising:

a first software component [mBot] for execution on a local client platform;

a second software component [sBot] associated with the first software component as a sibling for execution on a first server platform remote from the client platform to implement predetermined logic;

a first bot management application program (botMaster) executable on the local client platform, the botMaster program including means for creating a user model comprising knowledge about a user of the botMaster, and further including means for creating at least one user profile based on the user model; and

a third [botBox] software component for execution on a second server platform remote from the client platform;

the third software component botBox including means for storing a copy of the user profile on the second server platform for access by the sibling sBot.

11. A bot system according to claim 10 wherein the botBox includes means for receiving and storing data provided by the sBot for access by the sibling mBot.

12. A bot system according to claim 10 wherein the botBox includes means for means for storing an indication of a current status of the sBot, for reporting to the botMaster.

13. A bot system according to claim 10 wherein the botBox includes means for storing an indication of a current location of the sBot, for reporting to the botMaster;

the current location of the sBot including a uniform resource identifier of a server platform on which the sBot is located.

14. A bot system according to claim 10 wherein the botBox includes means for receiving and storing data provided by the botMaster for access by a foreign bot in a P2P exchange operation.

15. A bot system according to claim 10 and further comprising a second botMaster application program executable on a second client platform;

the second botMaster operable in a slave mode relative to the first botMaster.

16. A bot system according to claim 15 wherein the second client platform is a wireless mobile platform.

17. A bot system according to claim 10 and wherein the second software component [sBot] implements the predetermined logic in accordance with a predefined interaction protocol.

18. A bot system according to claim 10 and wherein the first software component [mBot] is downloadable from an external bot source and it includes a manifest that provides identification of the bot source and the bot runtime requirements.

19. A bot system according to claim 10 and wherein the first software component [mBot] comprises a class level software object that can be instantiated on the client platform.

20. A botServer computer program for execution on a first server platform comprising:

a botServer core software component for managing operation of the botServer;

a botExecutor component for managing execution of one or more sBots under direction of the core component; and

a communication component for managing communications between the core component and at least one external program.

21. A botServer program according to claim 20 and further comprising an event registry service available to provide event services to an executing sBot.

22. A botserver program according to claim 21 including means for directing the botExecutor component to activate a specified idle sBot in response to an occurrence of a selected event previously entered in the event registry.

23. A botserver program according to claim 21 including means for directing the botExecutor component to notify a specified executing sBot in response to an occurrence of a selected event previously entered in the event registry.

24. A botserver program according to claim 21 wherein the event registry implements a predetermined priority scheme applicable when more than one sBot registers for the same event.

25. A botserver program according to claim 20 wherein the botExecutor implements a container for safe execution of an sBot.

26. A botServer program according to claim 25 wherein the botExecutor implements an interaction controller for limiting interactions among two sBots executing in the container.

27. A botserver program according to claim 25 wherein the botExecutor implements a resource controller for controlling allocation of computing resources to an sBot executing in the container.

28. A botserver program according to claim 20 and further comprising an sBot repository for storing at least one sBot code class;

and wherein the botExecutor maintains an inventory of sBot classes stored in the repository, and the botExecutor includes means for instantiating a specified sBot from a corresponding sBot class stored in the repository responsive to a loading message from the botserver core.

29. A botserver program according to claim 28 and further comprising a bot verifier component to check the repository for the existence of executable code (sBot) corresponding to a launch request message received by the botExecutor.

30. A botserver program according to claim 20 wherein the communication component includes a botbox communication means for exchanging messages with a botBox account realized on a remote server and associated with an sBot executing on the botServer.

31. A botServer program according to claim 20 wherein the communication component includes a botMaster communication means for exchanging messages with a botMaster program that manages an mBot sibling associated with an sBot executing on the botServer.

32. A botServer program according to claim 20 wherein the communication component includes a botServer communication means for exchanging messages with a second botServer program located on a second server platform thereby enabling coordination between sBot programs executing on the first and second server platforms.

33. A botServer program according to claim 20 further comprising a plug-ins manager component for managing one or more software interfaces, each interface arranged for interacting with a resource external to the botServer;

and wherein the core includes means for passing messages between the plug-ins manager and the botExecutor so as to afford an executing sBot access to the external resource via the corresponding interface.

34. A botServer program according to claim 20 further comprising a code loader component for acquiring bot sBot code.

35. A botServer program according to claim 20 further comprising a botBox manager component for creating and managing at least one botBox account associated with a remote user.

36. A botServer program according to claim 35 wherein the botBox manager maintains at least one user profile associated with the botBox account on behalf of the remote user.

37. A botServer program according to claim 35 wherein the botBox manager includes a process for implementing migration of an sBot.

38. A botServer program according to claim 36 wherein the botBox manager maintains a plurality of predetermined user profiles associated with a given botBox account, and the botBox manager associates a designated one of the user profiles with a designated bot.

39. A botServer program according to claim 20 further comprising a plug-ins manager to provide access to external services for an sBot executing on the botServer.

40. A botServer computer program for execution on a first server platform for hosting at least one sBot comprising:

a botServer core software component for managing operation of the botServer, the core providing an event registry;

a botexecutor component for managing execution of one or more sBots under direction of the core component, the botExecutor implementing a container for safe execution of an sBot; and

the core including means for directing the botExecutor component to notify a specified executing sBot in response to an occurrence of a selected event previously entered in the event registry; and

the botServer further comprising an sBot repository for storing at least one sBot class code; and

wherein the botExecutor maintains an inventory of sBot classes stored in the repository, and the botExecutor includes means for instantiating a specified sBot from a corresponding sBot class stored in the repository responsive to a loading message from the botServer core.

41. A botServer program according to claim 40 wherein the botServer implements at least one general meeting place for execution of visiting sBots.

42. A botServer program according to claim 40 wherein the botServer implements at least one specialized meeting place for execution of visiting sBots only in accordance with a first predetermined interaction protocol.

43. A botServer program according to claim 42 wherein the botServer implements a child meeting place that inherits the interaction protocol of the said specialized meeting place.

44. A botServer program according to claim 42 wherein the botServer implements at least one virtual proctor to oversee activities of sBots executing in the said specialized meeting place.

45. A botServer program according to claim 42 wherein the specialized meeting place implements at least one local service.

46. A botServer program according to claim 45 wherein the local service comprises a publisher/subscriber service.

47. A botServer program according to claim 40 including a security registry.

48. A botServer program according to claim 47 wherein the security registry includes at least one of a trusted user list and a not trusted user list.

49. A botServer program according to claim 47 wherein the security registry includes at least one of a trusted developer list and a not trusted developer list.

50. An mBot application program for execution on a local client platform in association with a sibling sBot program executable on a first server platform remote from the local client platform, the mBot program comprising:

a graphical user interface for interacting with a user;

a core logic component for implementing a predetermined behavior, the logic block being configurable by the user via the graphical user interface;

an mBot data component for managing mBot data storage and manipulation;

a task data component for managing task data storage and manipulation; and

means for communicating with the sibling sBot.

51. An mBot according to claim 50 and further comprising a skin engine for changing an appearance of the graphical user interface.

52. An mBot according to claim 50 and further comprising a bot knowledge repository.

53. An mBot according to claim 50 and further including a component for monitoring progress of the sibling sBot program.

54. An mBot according to claim 50 and further comprising an ontology repository.

55. A [botMaster] bot management application program for use by a user on a local client platform, the program comprising:

a botMaster core component for supervising operation of the bot management application;

a botmanager component for downloading and installing an mBot executable on the local client platform; and

means for establishing a botBox account on a remote server on behalf of an mBot.

56. A bot management application program according to claim 55 wherein the botManager component implements a container for executing an mBot.

57. A bot management application program according to claim 55 wherein the botManager component includes a bot type repository for storing and accessing an mBot class source code and a bot instance repository for storing and accessing one or more individual instances of the mBot class code.

58. A bot management application program according to claim 55 and further comprising a scheduler component for launching a selected mBot at a predetermined time in the future.

59. A bot management application program according to claim 55 and further comprising a knowledge manager component for developing and storing a user model.

60. A bot management application program according to claim 59 and further comprising at least one plug-in (interface) for collecting data based on a user'"'"'s interaction with another application program to provide such data to the knowledge manager component for developing the user model.

61. A bot management application program according to claim 60 and further comprising a configuration component for managing remote botBox storage.

62. A bot management application program according to claim 61 and further comprising a configuration component for managing user setup data and local storage.

63. A bot management application program according to claim 60 and further comprising a botBox proxy.

64. A bot management application program including means for creating at least one user profile based on the user model.

65. An sBot program for execution on a server platform in association with a sibling mBot program executable on a remote client platform, the sBot comprising:

a core component implementing a predetermined functionality; and

means for communicating with a second server to interact with the sibling mBot.

66. An sBot program according to claim 65 wherein the sBot core includes a publishing component for publishing to the server platform the existence of the sBot to enable interaction with another bot.

67. An sBot program according to claim 65 wherein the sBot core includes a message handler for communications with a child sBot.

68. An sBot program according to claim 65 including a bot protocol component implementing bot-specific data.

69. An sBot program according to claim 68 wherein the bot protocol component implements a protocol specific state machine.

70. A method of implementing a software agent bot comprising the steps of:

designing a software agent to implement a desired functionality;

bifurcating the software agent functionality so as to form two parts—

a first component mBot for execution on a user'"'"'s local client machine, and a second sBot component for execution on a server platform remote from the user'"'"'s local client machine;

assigning a common identifier both to the mBot component and to the sBot component, thereby associating the mBot and sBot components as siblings; and

distributing the mBot component and the sBot component.

71. A method according to claim 70 wherein said bifurcating step includes allocating user interface functionality to the mBot component and allocating interaction with external resources to the sBot component.

72. A method according to claim 71 wherein said interaction with external resources includes accessing a database coupled to the remote server platform.

73. A method according to claim 71 wherein said interaction with external resources includes interacting with a remote Web site.

74. A method according to claim 71 wherein said interaction with external resources includes interacting with a foreign software agent.

75. A method according to claim 71 wherein said interaction with external resources includes interacting with a program executing on the remote server platform.

76. A method of deploying a software agent from a client platform comprising the steps of:

selecting a bot program to carry out a desired functionality, the bot program comprising a client side application and a corresponding server side application;

commencing execution of the client side application on the client platform;

initializing an [botBox] anchor program on a first server remote from the client platform;

sending a first message from the client platform to the anchor program to request launching the server side application;

in the first remote server, responsive to the first message, determining a location of the server side application, and sending a second message to the determined location to request launching of the server side application; and

then

commencing execution of the server side application on a second server at the determined location remote from the client platform.

77. A method according to claim 76 wherein said initializing the anchor program includes first selecting the first server for hosting the anchor program by manually inputting an identifier for locating the first server.

78. A method according to claim 76 wherein said initializing the anchor program includes first discovering a first server for hosting the anchor program by utilizing an Internet discovery service.

79. A method according to claim 76 wherein said initializing the anchor program includes locating the anchor program at a predetermined server identified in the client side program.

80. A method of migrating a software agent from a client platform comprising the steps of:

selecting a bot program to carry out a desired task, the bot program comprising a client side application mBot and a corresponding server side application, namely a first sBot;

commencing execution of the mBot on the client platform;

establishing an anchor program botBox on a first server remote from the client platform;

launching the first sBot on a second server remote from the client platform;

storing at the botBox an indication of a current location of the first sBot;

creating a second sBot associated with the first sBot;

launching the second sBot on a third server remote from the client platform;

updating the indication of a current location of the first sBot to reflect a location of the second sBot;

terminating execution of the first sBot, thereby effectively migrating the first sBot to the third server.

81. A method according to claim 80 wherein said launching the first sBot includes sending a launch request message from the client platform to the botBox;

and

responsive to the launch request message, locating a server to employ as the second server for hosting the first sBot.

82. A method according to claim 81 wherein said locating a server includes identifying a server that is authorized to host the corresponding sBot.