Interface for user/agent interaction

• US 5,877,759 A
• Filed: 03/26/1997
• Issued: 03/02/1999
• Est. Priority Date: 03/26/1997
• Status: Expired due to Term

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Netscape Communications Corporation (Apollo Global Management, Inc.)
• Inventors: Bauer, German W.
• Primary Examiner(s): Bayerl, Raymond J.
• Application Number:
  US08/825,210
• Time in Patent Office: 706 Days
• Field of Search: 345/329, 345/332, 345/963, 345/968, 345/331, 345/971, 345/336, 345/338, 345/337, 345/333, 345/335, 345/339, 395/200.32, 395/200.33, 395/200.35, 395/200.49, 395/680, 395/683, 707/10
• US Class Current: 719/317
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: Y10S 715/963 Calendar or scheduling
• CPC Class Codes: Y10S 715/968 interface for database querying and retrieval

Abstract

A user interface, for example for Internet and intranet agents, embodies the technical potential of automation and delegation into a cohesive structure. The invention also provides intelligent assistance to the client user interface and provides an interface that is centered on autonomous processing of whole tasks rather than sequences of commands, as well as the autonomous detection of contexts which require the launch of a process, especially where such context is time-based.

Claims

1. An interface for user/agent interaction, comprising:

a user interface element that offers a user intelligent choices of tasks that can be accomplished, based upon a given context and selection, wherein said tasks comprise multiple sub-tasks that are separately executed in conventional systems by calling up appropriate tools in a correct sequence;

said interface element comprising;

a funnel into which a user can type and/or drop objects, wherein said funnel provides a decision overlay that operates upon user requests for actions or resources, where the order of execution of such requests may be simultaneous or sequential, and where sequential tasks may be randomly executed or they may be hierarchically executed, and wherein said user inherits all outside capability of an enterprise; and

a pop-up menu that contains tasks and activities;

wherein said interface element allows multiple ways to communicate a user request and wherein said interface element recognizes a current selection and objects dragged onto it, as well as text typed into it; and

a meta agent that knows about the capabilities of a system and consolidates said capabilities of various plug-in agents into said interface element, wherein a funnel initiated search can be narrowed by user preferences, wherein said search may be time delimited;

wherein said search may be performed in the background and a user may be alerted when said search is completed, and wherein said user can define any task-relevant parameter at said funnel, including any of time, context, and location.

2. The interface of claim 1, wherein a user may speak into a microphone to access said funnel.

3. The interface of claim 1, further comprising:

a parser, wherein a user can specify requests in high-level terms by choosing one or more targets or parameters and, responsive thereto, said parser suggesting a requested task.

4. The interface of claim 1, wherein said funnel can recognize various instances of the same thing, wherein all of these instances are treated as equal pointers to said thing.

5. The interface of claim 1, wherein said funnel can suggest meaningful activities, constrained only by the capabilities of said system and any recognizers, once an object or a collection of objects is recognized, wherein the more details that are specified by said user through said funnel, the more the choice of activities is narrowed.

6. The interface of claim 1, further comprising:

a pop-up menu to present meaningful activities and for displaying a most probable choice as a pop-up label.

7. A user point of contact with all of the resources of an enterprise for providing said resources to said user at a single location, comprising:

a graphic user interface generated on a display, said graphic user interface comprising;

a funnel, wherein actions available at resource appear as functionality at said funnel as part of a pop-up menu, wherein said funnel adds functionality in the form of actions that are accessible to said user at said pop-up menu, to the extent that such functionality exists within a system and is available to said funnel, wherein said funnel provides a decision overlay that operates upon user requests for actions or resources, where the order of execution of such requests may be simultaneous or sequential, and where sequential tasks may be randomly executed or they may be hierarchically executed, and wherein said user inherits all outside capability of an enterprise;

at least one parser for parsing user entered information to convert said information to a common format and for parsing remote components;

a resource interface for accessing any available resource to complete a user requested task, wherein said tasks comprise multiple sub-tasks that are separately executed in conventional systems by calling up appropriate tools in a correct sequence, wherein a resource is registered with said parser when said resource makes itself known to said parser by providing information about itself to said parser, said information consisting of any of name or type of resource, what data types said resource can process, and what actions said resource can perform.

8. The user point of contact of claim 7, further comprising:

a context switch for translating user selections based upon their context.

9. The user point of contact of claim 7, further comprising:

a time management engine that establishes time parameters, alerts said user to scheduled events, and time stamps activities and completed tasks.

10. The user point of contact of claim 7, further comprising:

a Java engine for parsing and generating Java applets to enhance the functionality of a user request by including platform independent coded routines with a request, and by receiving and executing such routines as a result of a request.

11. The user point of contact of claim 7, further comprising:

a resolver for satisfying ambiguous or arcane requests; and

a database for determining whether or not a request is resolvable.

12. The user point of contact of claim 11, said database comprising:

modules that store user preferences, settings, history, and directories.