Intent based processing

• US 20050154783A1
• Filed: 12/22/2004
• Published: 07/14/2005
• Est. Priority Date: 02/27/2001
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hagiu, Costin, Sather, Dale A., Lisitsa, Rafael S.
• Granted Patent: US 7,349,953 B2
• Time in Patent Office: Days
• US Class Current: 709/209
• CPC Class Codes: G06F 3/023 Arrangements for converting discrete items of information into a coded form, e.g. arrangements for interpreting keyboard generated codes as alphanumeric codes, operand codes or instruction codes
• CPC Class Codes: G06F 3/038 Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry

Abstract

Presented is a system and method for determining a user'"'"'s intent. Specifically, constituents and a topology are derived from the user'"'"'s expression of intent, which can be stated broadly or stated in specific detail. The intent is expressed verbally, written, or in an XML format. The constituents and topology are resolved into a configuration based upon contexts. The contexts, which include a resource context, a user context, and an application context, includes information about the user'"'"'s preferences, location, restrictions, device and network availability, and content availability. The configuration is then implemented.

Claims

1. A method for determining a user'"'"'s intent to be implemented in a computer environment comprising:

receiving an input from the user containing the user'"'"'s intent; and

resolving the input into at least one constituent and a topology;

2. The method of claim 1 wherein the step of receiving an input from the user comprises receiving a voice indication.

3. The method of claim 1 wherein the step of step of receiving an input from the user comprises receiving a plurality of elements.

4. The method of claim 3 wherein the step of receiving a plurality of elements comprises the steps of:

receiving an object element;

receiving a node element; and

receiving a connection element, the node element and the connection element specifying a topology for the object element.

5. The method of claim 4 wherein the step of receiving a plurality of elements further comprises the steps of:

receiving an interface element; and

receiving a format element.

9. The method of claim 1 further comprising the step of resolving the constituent and topology into a configuration.

11. The method of claim 9 further comprising the step of realizing the configuration into an implementation.

6-8. -8. (canceled)

10. (canceled)

12-18. -18. (canceled)

19. A computer-readable medium having computer executable instructions for performing the steps comprising:

receiving a message having a user'"'"'s intent; and

resolving the user'"'"'s intent into a configuration.

23. The computer-readable medium of claim 19 wherein the step of resolving the user'"'"'s intent into a configuration comprises the steps of:

determining providers to implement the user'"'"'s intent; and

determining parameters required by the providers to realize the user'"'"'s intent.

24. The computer-readable medium of claim 19 having further computer executable instructions for performing the step comprising implementing the configuration.

20-22. -22. (canceled)

25. A computer-readable medium containing a data structure describing a user intent for rendering content, the data structure comprising:

an object element representing an object node elements associated with the object, the node elements representing constituents of the user intent; and

connection elements representing connections between constituents of the user intent

wherein the node elements and connection elements form a topology.

26. The computer-readable medium of claim 25 wherein the data structure is stored in an XML format.

27. The computer-readable medium of claim 25 wherein the data structure further includes an interface element that specifies an interface that clients use to control an object.

28. The computer-readable medium of claim 25 wherein the data structure further includes a format element that specifies a format for a connection or node.

29. The computer-readable medium of claim 28 wherein the format element includes attributes that identify the type of formats a connection or node supports.

30. The computer-readable medium of claim 25 wherein the object element includes an autoplay attribute that indicates whether the object should be started when created.

31. The computer-readable medium of claim 25 wherein a node element includes an identifier attribute that identifies the node in the context of a request.

32. The computer-readable medium of claim 25 wherein a collection element includes source and destination attributes that identify the nodes that are to be connected.