PATENT DOCUMENT

Publication Number: US-10691473-B2
Application Number: US-201615151191-A
Country: US
Kind Code: B2

Title: Intelligent automated assistant in a messaging environment

Abstract:
Systems and processes for operating an intelligent automated assistant in a messaging environment are provided. In one example process, a graphical user interface (GUI) having a plurality of previous messages between a user of the electronic device and the digital assistant can be displayed on a display. The plurality of previous messages can be presented in a conversational view. User input can be received and in response to receiving the user input, the user input can be displayed as a first message in the GUI. A contextual state of the electronic device corresponding to the displayed user input can be stored. The process can cause an action to be performed in accordance with a user intent derived from the user input. A response based on the action can be displayed as a second message in the GUI.

Claims:
What is claimed is: 
     
       1. A non-transitory computer-readable medium having instructions stored thereon, the instructions, when executed by one or more processors of an electronic device having a display, cause the one or more processors to:
 display, on the display, a graphical user interface (GUI) having a plurality of previous messages between a user of the electronic device and a digital assistant implemented on the electronic device, the plurality of previous messages presented in a conversational view; 
 after displaying the plurality of previous messages, detect a user selection of a first previous message of the displayed plurality of previous messages, the first previous message corresponding to a first previous user input received at a first time; 
 in response to detecting the user selection of the first previous message, retrieve a first previous contextual state of the electronic device at the first time, wherein the first previous contextual state is associated with the first previous message; 
 receive a current user input at a second time after the first time; and 
 in response to receiving the current user input:
 display a representation of the current user input as a first current message in the GUI, wherein the first current message is associated with a current contextual state of the electronic device at the second time; 
 cause a determination of a user intent based on the current user input and the retrieved first previous contextual state of the electronic device at the first time; 
 cause an action to be performed in accordance with the determined user intent, wherein results are obtained by performing the action; and 
 display a response as a second current message in the GUI, the response containing a representation of the obtained results. 
 
 
     
     
       2. The non-transitory computer-readable medium of  claim 1 , wherein each of the plurality of previous messages is associated with a respective previous contextual state of the electronic device. 
     
     
       3. The non-transitory computer-readable medium of  claim 1 , wherein the instructions further cause the one or more processors to:
 prior to the second time:
 detect a second previous user input; 
 in response to detecting the second previous user input, sample audio data containing a user utterance; 
 cause a second action to be performed in accordance with a second user intent derived from the user utterance; and 
 output a second response based on the second action, wherein a second previous message of the plurality of previous messages includes a text representation of the user utterance, and wherein a third previous message of the plurality of previous messages is based on the second response. 
 
 
     
     
       4. The non-transitory computer-readable medium of  claim 1 , wherein the instructions further cause the one or more processors to:
 prior to the second time, receive a third previous user input associated with a fourth previous message of the plurality of previous messages; 
 in response to receiving the third previous user input, store a bookmark of the fourth previous message in association with an affordance; and 
 display the affordance on the GUI, wherein selecting the affordance causes a focus of the GUI to change to the fourth previous message. 
 
     
     
       5. The non-transitory computer-readable medium of  claim 1 , wherein the instructions further cause the one or more processors to:
 in response to displaying the current user input as the first current message in the GUI of the electronic device, cause display of the first current message in a GUI of a second electronic device; and 
 in response to displaying the response as the second current message in the GUI of the electronic device, cause display of the second current message in the GUI of the second electronic device. 
 
     
     
       6. The non-transitory computer-readable medium of  claim 5 , wherein the instructions further cause the one or more processors to cause the second electronic device to:
 detect a user selection of the first current message in the GUI of the second electronic device; 
 receive a fourth user input at a third time after the second time; 
 in response to receiving the fourth user input, display the fourth user input as a third current message in the GUI of the second electronic device; 
 cause a third action to be performed in accordance with a third user intent, the third user intent derived from the fourth user input and the current contextual state of the electronic device at the second time; and 
 display a third response as a fourth current message in the GUI of the second electronic device, the third response based on the third action. 
 
     
     
       7. The non-transitory computer-readable medium of  claim 1 , wherein the instructions further cause the one or more processors to:
 identify, based on the current contextual state of the electronic device and the determined user intent, one or more words in the displayed response corresponding to an entity; 
 determine a fourth action associated with the entity; and 
 enable selection of the one or more words in the displayed response, wherein detecting a user selection of the one or more words causes the fourth action associated with the entity to be performed. 
 
     
     
       8. The non-transitory computer-readable medium of  claim 1 , wherein the GUI of the electronic device includes a text input field, and wherein the instructions further cause the one or more processors to:
 after displaying the GUI, detect a fifth user input associated with a fifth previous message of the plurality of previous messages; and 
 in response to detecting the fifth user input, display text of the fifth previous message in the text input field of the GUI. 
 
     
     
       9. The non-transitory computer-readable medium of  claim 1 , wherein the instructions further cause the one or more processors to:
 receive, via the GUI of the electronic device, a user selection of the second current message; in response to receiving the user selection of the second current message: 
 obtain, using an application of the electronic device, detailed results based on the user intent; and 
 display the detailed result in a GUI of the application. 
 
     
     
       10. The non-transitory computer-readable medium of  claim 9 , wherein displaying the response as the second current message includes displaying an indication in the second current message that a more detailed response is available in response to selecting the second current message. 
     
     
       11. The non-transitory computer-readable medium of  claim 1 , wherein the instructions further cause the one or more processors to:
 in response to receiving the current user input, display, based on the user intent, a media object in the GUI of the electronic device, the media object associated with an application of the electronic device. 
 
     
     
       12. The non-transitory computer-readable medium of  claim 11 , wherein the instructions further cause the one or more processors to:
 detect a user selection of the media object; 
 in response to detecting the user selection of the media object:
 obtain, using the application of the electronic device, expanded results corresponding to the media object; and 
 display the expanded results in a GUI of the application. 
 
 
     
     
       13. The non-transitory computer-readable medium of  claim 1 , wherein the instructions further cause the one or more processors to:
 receive a notification from an application of the electronic device; and 
 in response to receiving the notification, display the notification as a fifth current message in the GUI. 
 
     
     
       14. The non-transitory computer-readable medium of  claim 1 , wherein the GUI of the electronic device includes a user input interface, wherein the displayed response includes a request for additional information, and wherein the instructions further cause the one or more processors to:
 display two or more suggested character strings in the user input interface, each of the two or more suggested character string responsive to the request for additional information; 
 detect a user selection of a suggested character string of the two or more suggested character strings; 
 in response to detecting the user selection of the suggested character string, display the selected suggested character string as a sixth current message in the GUI of the electronic device; and 
 display a fourth response as a seventh current message in the GUI of the electronic device, the fourth response based on the selected suggested character strings. 
 
     
     
       15. The non-transitory computer-readable medium of  claim 1 , wherein:
 the current user input includes an ambiguous term; 
 the displayed response includes a displayed request for additional information related to the ambiguous term; and 
 the displayed request for additional information includes a list of possible interpretations for the ambiguous term. 
 
     
     
       16. The non-transitory computer-readable medium of  claim 15 , wherein the instructions further cause the one or more processors to:
 after the second time, receive a sixth user input indicating a selection of one of the list of possible interpretations; 
 in response to receiving the sixth user input, display a representation of the sixth user input as an eighth current message in the GUI; 
 cause a sixth action to be performed in accordance with a fourth user intent derived from the sixth user input; and 
 display a sixth response as a ninth current message in the GUI, the sixth response based on the sixth action. 
 
     
     
       17. The non-transitory computer-readable medium of  claim 1 , wherein the first previous contextual state includes the first time the first previous user input is received and data defining a location of the electronic device at the first time the user input is received. 
     
     
       18. A method for operating a digital assistant, the method comprising:
 at an electronic device with a display, a processor, and memory:
 displaying, on the display, a graphical user interface (GUI) having a plurality of previous messages between a user of the electronic device and a digital assistant implemented on the electronic device, the plurality of previous messages presented in a conversational view; 
 after displaying the plurality of previous messages, detecting a user selection of a first previous message of the displayed plurality of previous messages, the first previous message corresponding to a first previous user input received at a first time; 
 in response to detecting the user selection of the first previous message, retrieving a first previous contextual state of the electronic device at the first time, wherein the first previous contextual state is associated with the first previous message; 
 receiving a current user input at a second time after the first time; and 
 in response to receiving the current user input:
 displaying a representation of the current user input as a first current message in the GUI, wherein the first current message is associated with a current contextual state of the electronic device at the second time; 
 causing a determination of a user intent based on the current user input and the retrieved first previous contextual state of the electronic device at the first time; 
 causing an action to be performed in accordance with the determined user intent, wherein results are obtained by performing the action; and 
 displaying a response as a second current message in the GUI, the response containing a representation of the obtained results. 
 
 
 
     
     
       19. An electronic device comprising:
 a display; 
 one or more processors; and 
 memory having instructions stored thereon, the instructions, when executed by the one or more processors, cause the one or more processors to:
 display, on the display, a graphical user interface (GUI) having a plurality of previous messages between a user of the electronic device and a digital assistant implemented on the electronic device, the plurality of previous messages presented in a conversational view; 
 after displaying the plurality of previous messages, detect a user selection of a first previous message of the displayed plurality of previous messages, the first previous message corresponding to a first previous user input received at a first time; 
 in response to detecting the user selection of the first previous message, retrieve a first previous contextual state of the electronic device at the first time, wherein the first previous contextual state is associated with the first previous message; 
 receive a current user input at a second time after the first time; and 
 in response to receiving the current user input:
 display a representation of the current user input as a first current message in the GUI, wherein the first current message is associated with a current contextual state of the electronic device at the second time; 
 cause a determination of a user intent based on the current user input and the retrieved first previous contextual state of the electronic device at the first time; 
 cause an action to be performed in accordance with the determined user intent, wherein results are obtained by performing the action; and 
 display a response as a second current message in the GUI, the response containing a representation of the obtained results. 
 
 
 
     
     
       20. The non-transitory computer-readable medium of  claim 1 , wherein the previous contextual state includes contextual information other than text contained in the first previous message, and wherein the user intent is determined based on the contextual information other than the text contained in the first previous message. 
     
     
       21. The non-transitory computer-readable medium of  claim 1 , wherein the first previous user input comprises speech or text input received via a microphone or keyboard of the electronic device. 
     
     
       22. The method of  claim 18 , wherein each of the plurality of previous messages is associated with a respective previous contextual state of the electronic device. 
     
     
       23. The method of  claim 18 , further comprising:
 prior to the second time:
 detecting a second previous user input; 
 in response to detecting the second previous user input, sampling audio data containing a user utterance; 
 causing a second action to be performed in accordance with a second user intent derived from the user utterance; and 
 outputting a second response based on the second action, wherein a second previous message of the plurality of previous messages includes a text representation of the user utterance, and wherein a third previous message of the plurality of previous messages is based on the second response. 
 
 
     
     
       24. The method of  claim 18 , further comprising:
 prior to the second time, receiving a third previous user input associated with a fourth previous message of the plurality of previous messages; 
 in response to receiving the third previous user input, storing a bookmark of the fourth previous message in association with an affordance; and 
 displaying the affordance on the GUI, wherein selecting the affordance causes a focus of the GUI to change to the fourth previous message. 
 
     
     
       25. The method of  claim 18 , further comprising:
 in response to displaying the current user input as the first current message in the GUI of the electronic device, causing display of the first current message in a GUI of a second electronic device; and 
 in response to displaying the response as the second current message in the GUI of the electronic device, cause display of the second current message in the GUI of the second electronic device. 
 
     
     
       26. The method of  claim 25 , further comprising:
 at the second electronic device:
 detecting a user selection of the first current message in the GUI of the second electronic device; 
 receiving a fourth user input at a third time after the second time; 
 in response to receiving the fourth user input, display the fourth user input as a third current message in the GUI of the second electronic device; 
 causing a third action to be performed in accordance with a third user intent, the third user intent derived from the fourth user input and the current contextual state of the electronic device at the second time; and 
 displaying a third response as a fourth current message in the GUI of the second electronic device, the third response based on the third action. 
 
 
     
     
       27. The method of  claim 18 , further comprising:
 identifying, based on the current contextual state of the electronic device and the determined user intent, one or more words in the displayed response corresponding to an entity; 
 determining a fourth action associated with the entity; and 
 enabling selection of the one or more words in the displayed response, wherein detecting a user selection of the one or more words causes the fourth action associated with the entity to be performed. 
 
     
     
       28. The method of  claim 18 , wherein the GUI of the electronic device includes a text input field, and wherein the method further comprises:
 after displaying the GUI, detecting a fifth user input associated with a fifth previous message of the plurality of previous messages; and 
 in response to detecting the fifth user input, displaying text of the fifth previous message in the text input field of the GUI. 
 
     
     
       29. The method of  claim 18 , further comprising:
 receiving, via the GUI of the electronic device, a user selection of the second current message; 
 in response to receiving the user selection of the second current message:
 obtaining, using an application of the electronic device, detailed results based on the user intent; and 
 displaying the detailed result in a GUI of the application. 
 
 
     
     
       30. The method of  claim 18 , further comprising:
 in response to receiving the current user input, displaying, based on the user intent, a media object in the GUI of the electronic device, the media object associated with an application of the electronic device. 
 
     
     
       31. The method of  claim 18 , further comprising:
 receiving a notification from an application of the electronic device; and 
 in response to receiving the notification, displaying the notification as a fifth current message in the GUI. 
 
     
     
       32. The method of  claim 18 , wherein the first previous contextual state includes the first time the first previous user input is received and data defining a location of the electronic device at the first time the user input is received. 
     
     
       33. The device of  claim 19 , wherein each of the plurality of previous messages is associated with a respective previous contextual state of the electronic device. 
     
     
       34. The device of  claim 19 , wherein the instructions further cause the one or more processors to:
 prior to the second time:
 detect a second previous user input; 
 in response to detecting the second previous user input, sample audio data containing a user utterance; 
 cause a second action to be performed in accordance with a second user intent derived from the user utterance; and 
 output a second response based on the second action, wherein a second previous message of the plurality of previous messages includes a text representation of the user utterance, and wherein a third previous message of the plurality of previous messages is based on the second response. 
 
 
     
     
       35. The device of  claim 19 , wherein the instructions further cause the one or more processors to:
 prior to the second time, receive a third previous user input associated with a fourth previous message of the plurality of previous messages; 
 in response to receiving the third previous user input, store a bookmark of the fourth previous message in association with an affordance; and 
 display the affordance on the GUI, wherein selecting the affordance causes a focus of the GUI to change to the fourth previous message. 
 
     
     
       36. The device of  claim 19 , wherein the instructions further cause the one or more processors to:
 in response to displaying the current user input as the first current message in the GUI of the electronic device, cause display of the first current message in a GUI of a second electronic device; and 
 in response to displaying the response as the second current message in the GUI of the electronic device, cause display of the second current message in the GUI of the second electronic device. 
 
     
     
       37. The device of  claim 36 , wherein the instructions further cause the one or more processors to cause the second electronic device to:
 detect a user selection of the first current message in the GUI of the second electronic device; 
 receive a fourth user input at a third time after the second time; 
 in response to receiving the fourth user input, display the fourth user input as a third message in the GUI of the second electronic device; 
 cause a third action to be performed in accordance with a third user intent, the third user intent derived from the fourth user input and the current contextual state of the electronic device at the second time; and 
 display a third response as a fourth message in the GUI of the second electronic device, the third response based on the third action. 
 
     
     
       38. The device of  claim 19 , wherein the instructions further cause the one or more processors to:
 identify, based on the current contextual state of the electronic device and the determined user intent, one or more words in the displayed response corresponding to an entity; 
 determine a fourth action associated with the entity; and 
 enable selection of the one or more words in the displayed response, wherein detecting a user selection of the one or more words causes the fourth action associated with the entity to be performed. 
 
     
     
       39. The device of  claim 19 , wherein the GUI of the electronic device includes a text input field, and wherein the instructions further cause the one or more processors to:
 after displaying the GUI, detect a fifth user input associated with a fifth previous message of the plurality of previous messages; and 
 in response to detecting the fifth user input, display text of the fifth previous message in the text input field of the GUI. 
 
     
     
       40. The device of  claim 19 , wherein the instructions further cause the one or more processors to:
 receive, via the GUI of the electronic device, a user selection of the second current message; in response to receiving the user selection of the second current message: 
 obtain, using an application of the electronic device, detailed results based on the user intent; and 
 display the detailed result in a GUI of the application. 
 
     
     
       41. The device of  claim 19 , wherein the instructions further cause the one or more processors to:
 in response to receiving the current user input, display, based on the user intent, a media object in the GUI of the electronic device, the media object associated with an application of the electronic device. 
 
     
     
       42. The device of  claim 19 , wherein the instructions further cause the one or more processors to:
 receive a notification from an application of the electronic device; and 
 in response to receiving the notification, display the notification as a fifth current message in the GUI. 
 
     
     
       43. The device of  claim 19 , wherein the first previous contextual state includes the first time the first previous user input is received and data defining a location of the electronic device at the first time the user input is received.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application claims priority from U.S. Provisional Ser. No. 62/252,311, filed on Nov. 6, 2015, entitled INTELLIGENT AUTOMATED ASSISTANT IN A MESSAGING ENVIRONMENT, which is hereby incorporated by reference in its entirety for all purposes. 
    
    
     FIELD 
     This relates generally to intelligent automated assistants and, more specifically, to intelligent automated assistants in a messaging environment. 
     BACKGROUND 
     Intelligent automated assistants (or digital assistants) can provide a beneficial interface between human users and electronic devices. Such assistants can allow users to interact with devices or systems using natural language in spoken and/or text forms. For example, a user can provide a speech input containing a user request to a digital assistant operating on an electronic device. The digital assistant can interpret the user&#39;s intent from the speech input and operationalize the user&#39;s intent into tasks. The tasks can then be performed by executing one or more services of the electronic device, and a relevant output responsive to the user request can be returned to the user. 
     Typically, electronic devices implement a dedicated user interface for interacting with the digital assistant. For example, an electronic device can implement a dedicated voice interface for interacting with the digital assistant. Such dedicated user interfaces can limit the opportunities for interaction, which can limit the widespread adoption and application of digital assistants to benefit people&#39;s lives. 
     SUMMARY 
     Systems and processes for operating an intelligent automated assistant in a messaging environment are provided. In one example process, a graphical user interface (GUI) having a plurality of previous messages between a user of the electronic device and the digital assistant can be displayed on a display. The plurality of previous messages can be presented in a conversational view. User input can be received and in response to receiving the user input, the user input can be displayed as a first message in the GUI. A contextual state of the electronic device corresponding to the displayed user input can be stored. The process can cause an action to be performed in accordance with a user intent derived from the user input. A response based on the action can be displayed as a second message in the GUI. 
     In another example process, a GUI having a plurality of previous messages between a user and the digital assistant can be displayed on a display of an electronic device. The plurality of previous messages can be presented in a conversational view. A first user input including a media object can be received. In response to receiving the first user input, the media object can be displayed as a first message in the GUI. A second user input including text can be received. In response to receiving the second user input, the text can be displayed as a second message in the GUI. The process can cause a user intent corresponding to the first user input and the second user input to be determined. A determination of whether the user intent requires extracting text from the media object can be obtained. In response to obtaining a determination that the user intent requires extracting text from the media object: text from the media object can be extracted, a task in accordance with the user intent can be perform using the extracted text, and a response indicative of the user intent being satisfied can be displayed as a third message in the GUI. 
     In yet another example process, a GUI having a plurality of previous messages between a user of the electronic device and a user of a remote device can be displayed on the display of an electronic device. The plurality of previous messages can be presented in a conversational view. A first user input addressed to the digital assistant can be received from the user of the electronic device. In response to receiving the first user input, the first user input can be displayed as a first message in the GUI. The process can cause an action to be performed in accordance with a user intent derived from the first user input. A response based on the action can be displayed as a second message in the GUI. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a block diagram illustrating a system and environment for implementing a digital assistant according to various examples. 
         FIG. 2A  is a block diagram illustrating a portable multifunction device implementing the client-side portion of a digital assistant according to various examples. 
         FIG. 2B  is a block diagram illustrating exemplary components for event handling according to various examples. 
         FIG. 3  illustrates a portable multifunction device implementing the client-side portion of a digital assistant according to various examples. 
         FIG. 4  is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to various examples. 
         FIG. 5A  illustrates an exemplary user interface for a menu of applications on a portable multifunction device according to various examples. 
         FIG. 5B  illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display according to various examples. 
         FIG. 6A  illustrates a personal electronic device according to various examples. 
         FIG. 6B  is a block diagram illustrating a personal electronic device according to various examples. 
         FIG. 7A  is a block diagram illustrating a digital assistant system or a server portion thereof according to various examples. 
         FIG. 7B  illustrates the functions of the digital assistant shown in  FIG. 7A  according to various examples. 
         FIG. 7C  illustrates a portion of an ontology according to various examples. 
         FIG. 8  illustrates a process for operating a digital assistant in a messaging environment according to various examples. 
         FIGS. 9A-L  illustrate exemplary user interfaces of an electronic device for operating a digital assistant in a messaging environment according to various examples. 
         FIGS. 10A-C  illustrate user interfaces of an electronic device for operating a digital assistant in a messaging environment according to various examples. 
         FIGS. 11A-D  illustrate a process for operating a digital assistant in a messaging environment according to various examples. 
         FIGS. 12A-H  illustrate user interfaces of an electronic device for operating a digital assistant in a messaging environment according to various examples. 
         FIGS. 13A-C  illustrate a process for operating a digital assistant in a messaging environment according to various examples. 
         FIGS. 14A-I  illustrate user interfaces of an electronic device for operating a digital assistant in a messaging environment according to various examples. 
         FIG. 15  illustrates a functional block diagram of an electronic device according to various examples. 
         FIG. 16  illustrates a functional block diagram of an electronic device according to various examples. 
         FIG. 17  illustrates a functional block diagram of an electronic device according to various examples. 
     
    
    
     DETAILED DESCRIPTION 
     In the following description of examples, reference is made to the accompanying drawings in which it is shown by way of illustration specific examples that can be practiced. It is to be understood that other examples can be used and structural changes can be made without departing from the scope of the various examples. 
     It can be desirable to implement a digital assistant in a messaging environment. The messaging platform can enable multiple modes of input (e.g., text, audio, images, video, etc.) to be sent and received. A user request can thus define a request to the digital assistant using a combination of inputs (e.g., image and text). As described herein, this can increase the functionality and capabilities of the digital assistant, thereby providing a richer interactive experience between a user and a digital assistant. In addition, the messaging platform is a visual interface which permits interactions in a broader range of environments than voice/audio based platforms. A digital assistant in a message environment can thus enable greater accessibility to the digital assistant. In particular, the digital assistant can be accessible in noisy environments or in environments where audio output is not desired (e.g., the library). Further, the messaging platform can be a conversational interface where short concise communications are exchanged between two or more parties and presented in a chronological format. A digital assistant in a message environment can thus enable the digital assistant to be a participant in a multi-party conversation where the benefits associated with the digital assistant can be shared among the multiple participants. Moreover, the chronological format enables a user to conveniently review previous interactions with the digital assistant and utilize the contextual history associated with the previous interactions to define a wider range of tasks. 
     Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first input could be termed a second input, and, similarly, a second input could be termed a first input, without departing from the scope of the various described examples. The first input and the second input can both be inputs and, in some cases, can be separate and different inputs. 
     The terminology used in the description of the various described examples herein is for the purpose of describing particular examples only and is not intended to be limiting. As used in the description of the various described examples and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. 
     The term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context. 
     1. System and Environment 
       FIG. 1  illustrates a block diagram of system  100  according to various examples. In some examples, system  100  can implement a digital assistant. The terms “digital assistant,” “virtual assistant,” “intelligent automated assistant,” or “automatic digital assistant” can refer to any information processing system that interprets natural language input in spoken and/or textual form to infer user intent, and performs actions based on the inferred user intent. For example, to act on an inferred user intent, the system can perform one or more of the following: identifying a task flow with steps and parameters designed to accomplish the inferred user intent, inputting specific requirements from the inferred user intent into the task flow; executing the task flow by invoking programs, methods, services, APIs, or the like; and generating output responses to the user in an audible (e.g., speech) and/or visual form. 
     Specifically, a digital assistant can be capable of accepting a user request at least partially in the form of a natural language command, request, statement, narrative, and/or inquiry. Typically, the user request can seek either an informational answer or performance of a task by the digital assistant. A satisfactory response to the user request can be a provision of the requested informational answer, a performance of the requested task, or a combination of the two. For example, a user can ask the digital assistant a question, such as “Where am I right now?” Based on the user&#39;s current location, the digital assistant can answer, “You are in Central Park near the west gate.” The user can also request the performance of a task, for example, “Please invite my friends to my girlfriend&#39;s birthday party next week.” In response, the digital assistant can acknowledge the request by saying “Yes, right away,” and then send a suitable calendar invite on behalf of the user to each of the user&#39;s friends listed in the user&#39;s electronic address book. During performance of a requested task, the digital assistant can sometimes interact with the user in a continuous dialogue involving multiple exchanges of information over an extended period of time. There are numerous other ways of interacting with a digital assistant to request information or performance of various tasks. In addition to providing verbal responses and taking programmed actions, the digital assistant can also provide responses in other visual or audio forms, e.g., as text, alerts, music, videos, animations, etc. 
     As shown in  FIG. 1 , in some examples, a digital assistant can be implemented according to a client-server model. The digital assistant can include client-side portion  102  (hereafter “DA client  102 ”) executed on user device  104  and server-side portion  106  (hereafter “DA server  106 ”) executed on server system  108 . DA client  102  can communicate with DA server  106  through one or more networks  110 . DA client  102  can provide client-side functionalities such as user-facing input and output processing and communication with DA server  106 . DA server  106  can provide server-side functionalities for any number of DA clients  102  each residing on a respective user device  104 . 
     In some examples, DA server  106  can include client-facing I/O interface  112 , one or more processing modules  114 , data and models  116 , and I/O interface to external services  118 . The client-facing I/O interface  112  can facilitate the client-facing input and output processing for DA server  106 . One or more processing modules  114  can utilize data and models  116  to process speech input and determine the user&#39;s intent based on natural language input. Further, one or more processing modules  114  perform task execution based on inferred user intent. In some examples, DA server  106  can communicate with external services  120  through network(s)  110  for task completion or information acquisition. I/O interface to external services  118  can facilitate such communications. 
     User device  104  can be any suitable electronic device. For example, user devices can be a portable multifunctional device (e.g., device  200 , described below with reference to  FIG. 2A ), a multifunctional device (e.g., device  400 , described below with reference to  FIG. 4 ), or a personal electronic device (e.g., device  600 , described below with reference to  FIG. 6A-B .) A portable multifunctional device can be, for example, a mobile telephone that also contains other functions, such as PDA and/or music player functions. Specific examples of portable multifunction devices can include the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other examples of portable multifunction devices can include, without limitation, laptop or tablet computers. Further, in some examples, user device  104  can be a non-portable multifunctional device. In particular, user device  104  can be a desktop computer, a game console, a television, or a television set-top box. In some examples, user device  104  can include a touch-sensitive surface (e.g., touch screen displays and/or touchpads). Further, user device  104  can optionally include one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick. Various examples of electronic devices, such as multifunctional devices, are described below in greater detail. 
     Examples of communication network(s)  110  can include local area networks (LAN) and wide area networks (WAN), e.g., the Internet. Communication network(s)  110  can be implemented using any known network protocol, including various wired or wireless protocols, such as, for example, Ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol (VolP), Wi-MAX, or any other suitable communication protocol. 
     Server system  108  can be implemented on one or more standalone data processing apparatus or a distributed network of computers. In some examples, server system  108  can also employ various virtual devices and/or services of third-party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and/or infrastructure resources of server system  108 . 
     In some examples, user device  104  can communicate with DA server  106  via second user device  122 . Second user device  122  can be similar or identical to user device  104 . For example, second user device  122  can be similar to devices  200 ,  400 , or  600  described below with reference to  FIGS. 2A, 4, and 6A -B. User device  104  can be configured to communicatively couple to second user device  122  via a direct communication connection, such as Bluetooth, NFC, BTLE, or the like, or via a wired or wireless network, such as a local Wi-Fi network. In some examples, second user device  122  can be configured to act as a proxy between user device  104  and DA server  106 . For example, DA client  102  of user device  104  can be configured to transmit information (e.g., a user request received at user device  104 ) to DA server  106  via second user device  122 . DA server  106  can process the information and return relevant data (e.g., data content responsive to the user request) to user device  104  via second user device  122 . 
     In some examples, user device  104  can be configured to communicate abbreviated requests for data to second user device  122  to reduce the amount of information transmitted from user device  104 . Second user device  122  can be configured to determine supplemental information to add to the abbreviated request to generate a complete request to transmit to DA server  106 . This system architecture can advantageously allow user device  104  having limited communication capabilities and/or limited battery power (e.g., a watch or a similar compact electronic device) to access services provided by DA server  106  by using second user device  122 , having greater communication capabilities and/or battery power (e.g., a mobile phone, laptop computer, tablet computer, or the like), as a proxy to DA server  106 . While only two user devices  104  and  122  are shown in  FIG. 1 , it should be appreciated that system  100  can include any number and type of user devices configured in this proxy configuration to communicate with DA server system  106 . 
     Although the digital assistant shown in  FIG. 1  can include both a client-side portion (e.g., DA client  102 ) and a server-side portion (e.g., DA server  106 ), in some examples, the functions of a digital assistant can be implemented as a standalone application installed on a user device. In addition, the divisions of functionalities between the client and server portions of the digital assistant can vary in different implementations. For instance, in some examples, the DA client can be a thin-client that provides only user-facing input and output processing functions, and delegates all other functionalities of the digital assistant to a backend server. 
     2. Electronic Devices 
     Attention is now directed toward embodiments of electronic devices for implementing the client-side portion of a digital assistant.  FIG. 2A  is a block diagram illustrating portable multifunction device  200  with touch-sensitive display system  212  in accordance with some embodiments. Touch-sensitive display  212  is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device  200  includes memory  202  (which optionally includes one or more computer-readable storage mediums), memory controller  222 , one or more processing units (CPUs)  220 , peripherals interface  218 , RF circuitry  208 , audio circuitry  210 , speaker  211 , microphone  213 , input/output (I/O) subsystem  206 , other input control devices  216 , and external port  224 . Device  200  optionally includes one or more optical sensors  264 . Device  200  optionally includes one or more contact intensity sensors  265  for detecting intensity of contacts on device  200  (e.g., a touch-sensitive surface such as touch-sensitive display system  212  of device  200 ). Device  200  optionally includes one or more tactile output generators  267  for generating tactile outputs on device  200  (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system  212  of device  200  or touchpad  455  of device  400 ). These components optionally communicate over one or more communication buses or signal lines  203 . 
     As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least  256 ). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button). 
     As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user&#39;s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user&#39;s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user&#39;s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. 
     It should be appreciated that device  200  is only one example of a portable multifunction device, and that device  200  optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in  FIG. 2A  are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits. 
     Memory  202  may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. Memory  202  may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller  222  may control access to memory  202  by other components of device  200 . 
     In some examples, a non-transitory computer-readable storage medium of memory  202  can be used to store instructions (e.g., for performing aspects of processes described below) for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In other examples, the instructions (e.g., for performing aspects of the processes described below) can be stored on a non-transitory computer-readable storage medium (not shown) of the server system  108  or can be divided between the non-transitory computer-readable storage medium of memory  202  and the non-transitory computer-readable storage medium of server system  108 . In the context of this document, a “non-transitory computer-readable storage medium” can be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device. 
     Peripherals interface  218  can be used to couple input and output peripherals of the device to CPU  220  and memory  202 . The one or more processors  220  run or execute various software programs and/or sets of instructions stored in memory  202  to perform various functions for device  200  and to process data. In some embodiments, peripherals interface  218 , CPU  220 , and memory controller  222  may be implemented on a single chip, such as chip  204 . In some other embodiments, they may be implemented on separate chips. 
     RF (radio frequency) circuitry  208  receives and sends RF signals, also called electromagnetic signals. RF circuitry  208  converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry  208  optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry  208  optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry  208  optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VolP), Wi-MAX, a protocol for e mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. 
     Audio circuitry  210 , speaker  211 , and microphone  213  provide an audio interface between a user and device  200 . Audio circuitry  210  receives audio data from peripherals interface  218 , converts the audio data to an electrical signal, and transmits the electrical signal to speaker  211 . Speaker  211  converts the electrical signal to human-audible sound waves. Audio circuitry  210  also receives electrical signals converted by microphone  213  from sound waves. Audio circuitry  210  converts the electrical signal to audio data and transmits the audio data to peripherals interface  218  for processing. Audio data may be retrieved from and/or transmitted to memory  202  and/or RF circuitry  208  by peripherals interface  218 . In some embodiments, audio circuitry  210  also includes a headset jack (e.g.,  312 ,  FIG. 3 ). The headset jack provides an interface between audio circuitry  210  and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone). 
     I/O subsystem  206  couples input/output peripherals on device  200 , such as touch screen  212  and other input control devices  216 , to peripherals interface  218 . I/O subsystem  206  optionally includes display controller  256 , optical sensor controller  258 , intensity sensor controller  259 , haptic feedback controller  261 , and one or more input controllers  260  for other input or control devices. The one or more input controllers  260  receive/send electrical signals from/to other input control devices  216 . The other input control devices  216  optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s)  260  are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g.,  308 ,  FIG. 3 ) optionally include an up/down button for volume control of speaker  211  and/or microphone  213 . The one or more buttons optionally include a push button (e.g.,  306 ,  FIG. 3 ). 
     A quick press of the push button may disengage a lock of touch screen  212  or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g.,  306 ) may turn power to device  200  on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen  212  is used to implement virtual or soft buttons and one or more soft keyboards. 
     Touch-sensitive display  212  provides an input interface and an output interface between the device and a user. Display controller  256  receives and/or sends electrical signals from/to touch screen  212 . Touch screen  212  displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects. 
     Touch screen  212  has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen  212  and display controller  256  (along with any associated modules and/or sets of instructions in memory  202 ) detect contact (and any movement or breaking of the contact) on touch screen  212  and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen  212 . In an exemplary embodiment, a point of contact between touch screen  212  and the user corresponds to a finger of the user. 
     Touch screen  212  may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen  212  and display controller  256  may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen  212 . In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif. 
     A touch-sensitive display in some embodiments of touch screen  212  may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen  212  displays visual output from device  200 , whereas touch-sensitive touchpads do not provide visual output. 
     A touch-sensitive display in some embodiments of touch screen  212  may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety. 
     Touch screen  212  may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen  212  using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. 
     In some embodiments, in addition to the touch screen, device  200  may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen  212  or an extension of the touch-sensitive surface formed by the touch screen. 
     Device  200  also includes power system  262  for powering the various components. Power system  262  may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices. 
     Device  200  may also include one or more optical sensors  264 .  FIG. 2A  shows an optical sensor coupled to optical sensor controller  258  in I/O subsystem  206 . Optical sensor  264  may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor  264  receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module  243  (also called a camera module), optical sensor  264  may capture still images or video. In some embodiments, an optical sensor is located on the back of device  200 , opposite touch screen display  212  on the front of the device so that the touch screen display may be used as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user&#39;s image may be obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor  264  can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor  264  may be used along with the touch screen display for both video conferencing and still and/or video image acquisition. 
     Device  200  optionally also includes one or more contact intensity sensors  265 .  FIG. 2A  shows a contact intensity sensor coupled to intensity sensor controller  259  in I/O subsystem  206 . Contact intensity sensor  265  optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor  265  receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  212 ). In some embodiments, at least one contact intensity sensor is located on the back of device  200 , opposite touch screen display  212 , which is located on the front of device  200 . 
     Device  200  may also include one or more proximity sensors  266 .  FIG. 2A  shows proximity sensor  266  coupled to peripherals interface  218 . Alternately, proximity sensor  266  may be coupled to input controller  260  in I/O subsystem  206 . Proximity sensor  266  may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen  212  when the multifunction device is placed near the user&#39;s ear (e.g., when the user is making a phone call). 
     Device  200  optionally also includes one or more tactile output generators  267 .  FIG. 2A  shows a tactile output generator coupled to haptic feedback controller  261  in I/O subsystem  206 . Tactile output generator  267  optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor  265  receives tactile feedback generation instructions from haptic feedback module  233  and generates tactile outputs on device  200  that are capable of being sensed by a user of device  200 . In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system  212 ) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device  200 ) or laterally (e.g., back and forth in the same plane as a surface of device  200 ). In some embodiments, at least one tactile output generator sensor is located on the back of device  200 , opposite touch screen display  212 , which is located on the front of device  200 . 
     Device  200  may also include one or more accelerometers  268 .  FIG. 2A  shows accelerometer  268  coupled to peripherals interface  218 . Alternately, accelerometer  268  may be coupled to an input controller  260  in I/O subsystem  206 . Accelerometer  268  may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device  200  optionally includes, in addition to accelerometer(s)  268 , a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device  200 . 
     In some embodiments, the software components stored in memory  202  include operating system  226 , communication module (or set of instructions)  228 , contact/motion module (or set of instructions)  230 , graphics module (or set of instructions)  232 , text input module (or set of instructions)  234 , Global Positioning System (GPS) module (or set of instructions)  235 , Digital Assistant Client Module  229 , and applications (or sets of instructions)  236 . Further, memory  202  can store data and models, such as user data and models  231 . Furthermore, in some embodiments, memory  202  ( FIG. 2A ) or  470  ( FIG. 4 ) stores device/global internal state  257 , as shown in  FIGS. 2A and 4 . Device/global internal state  257  includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display  212 ; sensor state, including information obtained from the device&#39;s various sensors and input control devices  216 ; and location information concerning the device&#39;s location and/or attitude. 
     Operating system  226  (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components. 
     Communication module  228  facilitates communication with other devices over one or more external ports  224  and also includes various software components for handling data received by RF circuitry  208  and/or external port  224 . External port  224  (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices. 
     Contact/motion module  230  optionally detects contact with touch screen  212  (in conjunction with display controller  256 ) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module  230  includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module  230  receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module  230  and display controller  256  detect contact on a touchpad. 
     In some embodiments, contact/motion module  230  uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device  200 ). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter). 
     Contact/motion module  230  optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event. 
     Graphics module  232  includes various known software components for rendering and displaying graphics on touch screen  212  or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like. 
     In some embodiments, graphics module  232  stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module  232  receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller  256 . 
     Haptic feedback module  233  includes various software components for generating instructions used by tactile output generator(s)  267  to produce tactile outputs at one or more locations on device  200  in response to user interactions with device  200 . 
     Text input module  234 , which may be a component of graphics module  232 , provides soft keyboards for entering text in various applications (e.g., contacts  237 , e mail  240 , IM  241 , browser  247 , and any other application that needs text input). 
     GPS module  235  determines the location of the device and provides this information for use in various applications (e.g., to telephone  238  for use in location-based dialing; to camera  243  as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets). 
     Digital assistant client module  229  can include various client-side digital assistant instructions to provide the client-side functionalities of the digital assistant. For example, digital assistant client module  229  can be capable of accepting voice input (e.g., speech input), text input, touch input, and/or gestural input through various user interfaces (e.g., microphone  213 , accelerometer(s)  268 , touch-sensitive display system  212 , optical sensor(s)  264 , other input control devices  216 , etc) of portable multifunction device  200 . Digital assistant client module  229  can also be capable of providing output in audio (e.g., speech output), visual, and/or tactile forms through various output interfaces (e.g., speaker  211 , touch-sensitive display system  212 , tactile output generator(s)  267 , etc.) of portable multifunction device  200 . For example, output can be provided as voice, sound, alerts, text messages, menus, graphics, videos, animations, vibrations, and/or combinations of two or more of the above. During operation, digital assistant client module  229  can communicate with DA server  106  using RF circuitry  208 . 
     User data and models  231  can include various data associated with the user (e.g., user-specific vocabulary data, user preference data, user-specified name pronunciations, data from the user&#39;s electronic address book, to-do lists, shopping lists, etc.) to provide the client-side functionalities of the digital assistant. Further, user data and models  231  can includes various models (e.g., speech recognition models, statistical language models, natural language processing models, ontology, task flow models, service models, etc.) for processing user input and determining user intent. 
     In some examples, digital assistant client module  229  can utilize the various sensors, subsystems, and peripheral devices of portable multifunction device  200  to gather additional information from the surrounding environment of the portable multifunction device  200  to establish a context associated with a user, the current user interaction, and/or the current user input. In some examples, digital assistant client module  229  can provide the contextual information or a subset thereof with the user input to DA server  106  to help infer the user&#39;s intent. In some examples, the digital assistant can also use the contextual information to determine how to prepare and deliver outputs to the user. Contextual information can be referred to as context data. 
     In some examples, the contextual information that accompanies the user input can include sensor information, e.g., lighting, ambient noise, ambient temperature, images or videos of the surrounding environment, etc. In some examples, the contextual information can also include the physical state of the device, e.g., device orientation, device location, device temperature, power level, speed, acceleration, motion patterns, cellular signals strength, etc. In some examples, information related to the software state of DA server  106 , e.g., running processes, installed programs, past and present network activities, background services, error logs, resources usage, etc., and of portable multifunction device  200  can be provided to DA server  106  as contextual information associated with a user input. 
     In some examples, the digital assistant client module  229  can selectively provide information (e.g., user data  231 ) stored on the portable multifunction device  200  in response to requests from DA server  106 . In some examples, digital assistant client module  229  can also elicit additional input from the user via a natural language dialogue or other user interfaces upon request by DA server  106 . Digital assistant client module  229  can pass the additional input to DA server  106  to help DA server  106  in intent deduction and/or fulfillment of the user&#39;s intent expressed in the user request. 
     A more detailed description of a digital assistant is described below with reference to  FIGS. 7A-C . It should be recognized that digital assistant client module  229  can include any number of the sub-modules of digital assistant module  726  described below. 
     Applications  236  may include the following modules (or sets of instructions), or a subset or superset thereof:
         Contacts module  237  (sometimes called an address book or contact list);   Telephone module  238 ;   Video conference module  239 ;   E-mail client module  240 ;   Instant messaging (IM) module  241 ;   Workout support module  242 ;   Camera module  243  for still and/or video images;   Image management module  244 ;   Video player module;   Music player module;   Browser module  247 ;   Calendar module  248 ;   Widget modules  249 , which may include one or more of: weather widget  249 - 1 , stocks widget  249 - 2 , calculator widget  249 - 3 , alarm clock widget  249 - 4 , dictionary widget  249 - 5 , and other widgets obtained by the user, as well as user-created widgets  249 - 6 ;   Widget creator module  250  for making user-created widgets  249 - 6 ;   Search module  251 ;   Video and music player module  252 , which merges video player module and music player module;   Notes module  253 ;   Map module  254 ; and/or   Online video module  255 .       

     Examples of other applications  236  that may be stored in memory  202  include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication. 
     In conjunction with touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , and text input module  234 , contacts module  237  may be used to manage an address book or contact list (e.g., stored in application internal state  292  of contacts module  237  in memory  202  or memory  470 ), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone  238 , video conference module  239 , e-mail  240 , or IM  241 ; and so forth. 
     In conjunction with RF circuitry  208 , audio circuitry  210 , speaker  211 , microphone  213 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , and text input module  234 , telephone module  238  may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module  237 , modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols, and technologies. 
     In conjunction with RF circuitry  208 , audio circuitry  210 , speaker  211 , microphone  213 , touch screen  212 , display controller  256 , optical sensor  264 , optical sensor controller  258 , contact/motion module  230 , graphics module  232 , text input module  234 , contacts module  237 , and telephone module  238 , video conference module  239  includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions. 
     In conjunction with RF circuitry  208 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , and text input module  234 , e-mail client module  240  includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module  244 , e-mail client module  240  makes it very easy to create and send e-mails with still or video images taken with camera module  243 . 
     In conjunction with RF circuitry  208 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , and text input module  234 , the instant messaging module  241  includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). 
     In conjunction with RF circuitry  208 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , text input module  234 , GPS module  235 , map module  254 , and music player module, workout support module  242  includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data. 
     In conjunction with touch screen  212 , display controller  256 , optical sensor(s)  264 , optical sensor controller  258 , contact/motion module  230 , graphics module  232 , and image management module  244 , camera module  243  includes executable instructions to capture still images or video (including a video stream) and store them into memory  202 , modify characteristics of a still image or video, or delete a still image or video from memory  202 . 
     In conjunction with touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , text input module  234 , and camera module  243 , image management module  244  includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images. 
     In conjunction with RF circuitry  208 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , and text input module  234 , browser module  247  includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages. 
     In conjunction with RF circuitry  208 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , text input module  234 , e-mail client module  240 , and browser module  247 , calendar module  248  includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions. 
     In conjunction with RF circuitry  208 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , text input module  234 , and browser module  247 , widget modules  249  are mini-applications that may be downloaded and used by a user (e.g., weather widget  249 - 1 , stocks widget  249 - 2 , calculator widget  249 - 3 , alarm clock widget  249 - 4 , and dictionary widget  249 - 5 ) or created by the user (e.g., user-created widget  249 - 6 ). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets). 
     In conjunction with RF circuitry  208 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , text input module  234 , and browser module  247 , the widget creator module  250  may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget). 
     In conjunction with touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , and text input module  234 , search module  251  includes executable instructions to search for text, music, sound, image, video, and/or other files in memory  202  that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions. 
     In conjunction with touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , audio circuitry  210 , speaker  211 , RF circuitry  208 , and browser module  247 , video and music player module  252  includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen  212  or on an external, connected display via external port  224 ). In some embodiments, device  200  optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.). 
     In conjunction with touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , and text input module  234 , notes module  253  includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions. 
     In conjunction with RF circuitry  208 , touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , text input module  234 , GPS module  235 , and browser module  247 , map module  254  may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions. 
     In conjunction with touch screen  212 , display controller  256 , contact/motion module  230 , graphics module  232 , audio circuitry  210 , speaker  211 , RF circuitry  208 , text input module  234 , e-mail client module  240 , and browser module  247 , online video module  255  includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port  224 ), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module  241 , rather than e-mail client module  240 , is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety. 
     Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module  252 ,  FIG. 2A ). In some embodiments, memory  202  may store a subset of the modules and data structures identified above. Furthermore, memory  202  may store additional modules and data structures not described above. 
     In some embodiments, device  200  is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device  200 , the number of physical input control devices (such as push buttons, dials, and the like) on device  200  may be reduced. 
     The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device  200  to a main, home, or root menu from any user interface that is displayed on device  200 . In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad. 
       FIG. 2B  is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory  202  ( FIG. 2A ) or  470  ( FIG. 4 ) includes event sorter  270  (e.g., in operating system  226 ) and a respective application  236 - 1  (e.g., any of the aforementioned applications  237 - 251 ,  255 ,  480 - 490 ). 
     Event sorter  270  receives event information and determines the application  236 - 1  and application view  291  of application  236 - 1  to which to deliver the event information. Event sorter  270  includes event monitor  271  and event dispatcher module  274 . In some embodiments, application  236 - 1  includes application internal state  292 , which indicates the current application view(s) displayed on touch-sensitive display  212  when the application is active or executing. In some embodiments, device/global internal state  257  is used by event sorter  270  to determine which application(s) is (are) currently active, and application internal state  292  is used by event sorter  270  to determine application views  291  to which to deliver event information. 
     In some embodiments, application internal state  292  includes additional information, such as one or more of: resume information to be used when application  236 - 1  resumes execution, user interface state information that indicates information being displayed or that is ready for display by application  236 - 1 , a state queue for enabling the user to go back to a prior state or view of application  236 - 1 , and a redo/undo queue of previous actions taken by the user. 
     Event monitor  271  receives event information from peripherals interface  218 . Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display  212 , as part of a multi-touch gesture). Peripherals interface  218  transmits information it receives from I/O subsystem  206  or a sensor, such as proximity sensor  266 , accelerometer(s)  268 , and/or microphone  213  (through audio circuitry  210 ). Information that peripherals interface  218  receives from I/O subsystem  206  includes information from touch-sensitive display  212  or a touch-sensitive surface. 
     In some embodiments, event monitor  271  sends requests to the peripherals interface  218  at predetermined intervals. In response, peripherals interface  218  transmits event information. In other embodiments, peripherals interface  218  transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration). 
     In some embodiments, event sorter  270  also includes a hit view determination module  272  and/or an active event recognizer determination module  273 . 
     Hit view determination module  272  provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display  212  displays more than one view. Views are made up of controls and other elements that a user can see on the display. 
     Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 
     Hit view determination module  272  receives information related to sub events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module  272  identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module  272 , the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view. 
     Active event recognizer determination module  273  determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module  273  determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module  273  determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views. 
     Event dispatcher module  274  dispatches the event information to an event recognizer (e.g., event recognizer  280 ). In embodiments including active event recognizer determination module  273 , event dispatcher module  274  delivers the event information to an event recognizer determined by active event recognizer determination module  273 . In some embodiments, event dispatcher module  274  stores in an event queue the event information, which is retrieved by a respective event receiver  282 . 
     In some embodiments, operating system  226  includes event sorter  270 . Alternatively, application  236 - 1  includes event sorter  270 . In yet other embodiments, event sorter  270  is a stand-alone module, or a part of another module stored in memory  202 , such as contact/motion module  230 . 
     In some embodiments, application  236 - 1  includes a plurality of event handlers  290  and one or more application views  291 , each of which includes instructions for handling touch events that occur within a respective view of the application&#39;s user interface. Each application view  291  of the application  236 - 1  includes one or more event recognizers  280 . Typically, a respective application view  291  includes a plurality of event recognizers  280 . In other embodiments, one or more of event recognizers  280  are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application  236 - 1  inherits methods and other properties. In some embodiments, a respective event handler  290  includes one or more of: data updater  276 , object updater  277 , GUI updater  278 , and/or event data  279  received from event sorter  270 . Event handler  290  may utilize or call data updater  276 , object updater  277 , or GUI updater  278  to update the application internal state  292 . Alternatively, one or more of the application views  291  include one or more respective event handlers  290 . Also, in some embodiments, one or more of data updater  276 , object updater  277 , and GUI updater  278  are included in a respective application view  291 . 
     A respective event recognizer  280  receives event information (e.g., event data  279 ) from event sorter  270  and identifies an event from the event information. Event recognizer  280  includes event receiver  282  and event comparator  284 . In some embodiments, event recognizer  280  also includes at least a subset of: metadata  283 , and event delivery instructions  288  (which may include sub-event delivery instructions). 
     Event receiver  282  receives event information from event sorter  270 . The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device. 
     Event comparator  284  compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator  284  includes event definitions  286 . Event definitions  286  contain definitions of events (e.g., predefined sequences of sub-events), for example, event  1  ( 287 - 1 ), event  2  ( 287 - 2 ), and others. In some embodiments, sub-events in an event ( 287 ) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event  1  ( 287 - 1 ) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event  2  ( 287 - 2 ) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display  212 , and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers  290 . 
     In some embodiments, event definition  287  includes a definition of an event for a respective user-interface object. In some embodiments, event comparator  284  performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display  212 , when a touch is detected on touch-sensitive display  212 , event comparator  284  performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler  290 , the event comparator uses the result of the hit test to determine which event handler  290  should be activated. For example, event comparator  284  selects an event handler associated with the sub-event and the object triggering the hit test. 
     In some embodiments, the definition for a respective event ( 287 ) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer&#39;s event type. 
     When a respective event recognizer  280  determines that the series of sub-events do not match any of the events in event definitions  286 , the respective event recognizer  280  enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture. 
     In some embodiments, a respective event recognizer  280  includes metadata  283  with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata  283  includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata  283  includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy. 
     In some embodiments, a respective event recognizer  280  activates event handler  290  associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer  280  delivers event information associated with the event to event handler  290 . Activating an event handler  290  is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer  280  throws a flag associated with the recognized event, and event handler  290  associated with the flag catches the flag and performs a predefined process. 
     In some embodiments, event delivery instructions  288  include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process. 
     In some embodiments, data updater  276  creates and updates data used in application  236 - 1 . For example, data updater  276  updates the telephone number used in contacts module  237 , or stores a video file used in video player module. In some embodiments, object updater  277  creates and updates objects used in application  236 - 1 . For example, object updater  277  creates a new user-interface object or updates the position of a user-interface object. GUI updater  278  updates the GUI. For example, GUI updater  278  prepares display information and sends it to graphics module  232  for display on a touch-sensitive display. 
     In some embodiments, event handler(s)  290  includes or has access to data updater  276 , object updater  277 , and GUI updater  278 . In some embodiments, data updater  276 , object updater  277 , and GUI updater  278  are included in a single module of a respective application  236 - 1  or application view  291 . In other embodiments, they are included in two or more software modules. 
     It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices  200  with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized. 
       FIG. 3  illustrates a portable multifunction device  200  having a touch screen  212  in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI)  300 . In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers  302  (not drawn to scale in the figure) or one or more styluses  303  (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device  200 . In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap. 
     Device  200  may also include one or more physical buttons, such as “home” or menu button  304 . As described previously, menu button  304  may be used to navigate to any application  236  in a set of applications that may be executed on device  200 . Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen  212 . 
     In one embodiment, device  200  includes touch screen  212 , menu button  304 , push button  306  for powering the device on/off and locking the device, volume adjustment button(s)  308 , subscriber identity module (SIM) card slot  310 , headset jack  312 , and docking/charging external port  224 . Push button  306  is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device  200  also accepts verbal input for activation or deactivation of some functions through microphone  213 . Device  200  also, optionally, includes one or more contact intensity sensors  265  for detecting intensity of contacts on touch screen  212  and/or one or more tactile output generators  267  for generating tactile outputs for a user of device  200 . 
       FIG. 4  is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device  400  need not be portable. In some embodiments, device  400  is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child&#39;s learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device  400  typically includes one or more processing units (CPUs)  410 , one or more network or other communications interfaces  460 , memory  470 , and one or more communication buses  420  for interconnecting these components. Communication buses  420  optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device  400  includes input/output (I/O) interface  430  comprising display  440 , which is typically a touch screen display. I/O interface  430  also optionally includes a keyboard and/or mouse (or other pointing device)  450  and touchpad  455 , tactile output generator  457  for generating tactile outputs on device  400  (e.g., similar to tactile output generator(s)  267  described above with reference to  FIG. 2A ), sensors  459  (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s)  265  described above with reference to  FIG. 2A ). Memory  470  includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory  470  optionally includes one or more storage devices remotely located from CPU(s)  410 . In some embodiments, memory  470  stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory  202  of portable multifunction device  200  ( FIG. 2A ), or a subset thereof. Furthermore, memory  470  optionally stores additional programs, modules, and data structures not present in memory  202  of portable multifunction device  200 . For example, memory  470  of device  400  optionally stores drawing module  480 , presentation module  482 , word processing module  484 , website creation module  486 , disk authoring module  488 , and/or spreadsheet module  490 , while memory  202  of portable multifunction device  200  ( FIG. 2A ) optionally does not store these modules. 
     Each of the above-identified elements in  FIG. 4  may be stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory  470  may store a subset of the modules and data structures identified above. Furthermore, memory  470  may store additional modules and data structures not described above. 
     Attention is now directed towards embodiments of user interfaces that may be implemented on, for example, portable multifunction device  200 . 
       FIG. 5A  illustrates an exemplary user interface for a menu of applications on portable multifunction device  200  in accordance with some embodiments. Similar user interfaces may be implemented on device  400 . In some embodiments, user interface  500  includes the following elements, or a subset or superset thereof: 
     Signal strength indicator(s)  502  for wireless communication(s), such as cellular and Wi-Fi signals;
         Time  504 ;   Bluetooth indicator  505 ;   Battery status indicator  506 ;   Tray  508  with icons for frequently used applications, such as:
           Icon  516  for telephone module  238 , labeled “Phone,” which optionally includes an indicator  514  of the number of missed calls or voicemail messages;   Icon  518  for e-mail client module  240 , labeled “Mail,” which optionally includes an indicator  510  of the number of unread e-mails;   Icon  520  for browser module  247 , labeled “Browser;” and   Icon  522  for video and music player module  252 , also referred to as iPod (trademark of Apple Inc.) module  252 , labeled “iPod;” and   
           Icons for other applications, such as:
           Icon  524  for IM module  241 , labeled “Messages;”   Icon  526  for calendar module  248 , labeled “Calendar;”   Icon  528  for image management module  244 , labeled “Photos;”   Icon  530  for camera module  243 , labeled “Camera;”   Icon  532  for online video module  255 , labeled “Online Video;”   Icon  534  for stocks widget  249 - 2 , labeled “Stocks;”   Icon  536  for map module  254 , labeled “Maps;”   Icon  538  for weather widget  249 - 1 , labeled “Weather;”   Icon  540  for alarm clock widget  249 - 4 , labeled “Clock;”   Icon  542  for workout support module  242 , labeled “Workout Support;”   Icon  544  for notes module  253 , labeled “Notes;” and   Icon  546  for a settings application or module, labeled “Settings,” which provides access to settings for device  200  and its various applications  236 .   
               

     It should be noted that the icon labels illustrated in  FIG. 5A  are merely exemplary. For example, icon  522  for video and music player module  252  may optionally be labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon. 
       FIG. 5B  illustrates an exemplary user interface on a device (e.g., device  400 ,  FIG. 4 ) with a touch-sensitive surface  551  (e.g., a tablet or touchpad  455 ,  FIG. 4 ) that is separate from the display  550  (e.g., touch screen display  212 ). Device  400  also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors  457 ) for detecting intensity of contacts on touch-sensitive surface  551  and/or one or more tactile output generators  459  for generating tactile outputs for a user of device  400 . 
     Although some of the examples which follow will be given with reference to inputs on touch screen display  212  (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in  FIG. 5B . In some embodiments, the touch-sensitive surface (e.g.,  551  in  FIG. 5B ) has a primary axis (e.g.,  552  in  FIG. 5B ) that corresponds to a primary axis (e.g.,  553  in  FIG. 5B ) on the display (e.g.,  550 ). In accordance with these embodiments, the device detects contacts (e.g.,  560  and  562  in  FIG. 5B ) with the touch-sensitive surface  551  at locations that correspond to respective locations on the display (e.g., in  FIG. 5B, 560  corresponds to  568  and  562  corresponds to  570 ). In this way, user inputs (e.g., contacts  560  and  562 , and movements thereof) detected by the device on the touch-sensitive surface (e.g.,  551  in  FIG. 5B ) are used by the device to manipulate the user interface on the display (e.g.,  550  in  FIG. 5B ) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein. 
     Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously. 
       FIG. 6A  illustrates exemplary personal electronic device  600 . Device  600  includes body  602 . In some embodiments, device  600  can include some or all of the features described with respect to devices  200  and  400  (e.g.,  FIGS. 2A-4B ). In some embodiments, device  600  has touch-sensitive display screen  604 , hereafter touch screen  604 . Alternatively, or in addition to touch screen  604 , device  600  has a display and a touch-sensitive surface. As with devices  200  and  400 , in some embodiments, touch screen  604  (or the touch-sensitive surface) may have one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen  604  (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device  600  can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device  600 . 
     Techniques for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, each of which is hereby incorporated by reference in their entirety. 
     In some embodiments, device  600  has one or more input mechanisms  606  and  608 . Input mechanisms  606  and  608 , if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device  600  has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device  600  with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms may permit device  600  to be worn by a user. 
       FIG. 6B  depicts exemplary personal electronic device  600 . In some embodiments, device  600  can include some or all of the components described with respect to  FIGS. 2A, 2B , and  4 . Device  600  has bus  612  that operatively couples I/O section  614  with one or more computer processors  616  and memory  618 . I/O section  614  can be connected to display  604 , which can have touch-sensitive component  622  and, optionally, touch-intensity sensitive component  624 . In addition, I/O section  614  can be connected with communication unit  630  for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device  600  can include input mechanisms  606  and/or  608 . Input mechanism  606  may be a rotatable input device or a depressible and rotatable input device, for example. Input mechanism  608  may be a button, in some examples. 
     Input mechanism  608  may be a microphone, in some examples. Personal electronic device  600  can include various sensors, such as GPS sensor  632 , accelerometer  634 , directional sensor  640  (e.g., compass), gyroscope  636 , motion sensor  638 , and/or a combination thereof, all of which can be operatively connected to I/O section  614 . 
     Memory  618  of personal electronic device  600  can be a non-transitory computer-readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors  616 , for example, can cause the computer processors to perform the techniques and processes described below. The computer-executable instructions can also be stored and/or transported within any non-transitory computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For purposes of this document, a “non-transitory computer-readable storage medium” can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device  600  is not limited to the components and configuration of  FIG. 6B , but can include other or additional components in multiple configurations. 
     As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices  200 ,  400 , and/or  600  ( FIGS. 2, 4, and 6 ). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) may each constitute an affordance. 
     As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad  455  in  FIG. 4  or touch-sensitive surface  551  in  FIG. 5B ) while the cursor is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system  212  in  FIG. 2A  or touch screen  212  in  FIG. 5A ) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user&#39;s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device). 
     As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation. 
     In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity. 
     The intensity of a contact on the touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures. 
     An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero. 
     In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input). 
     In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances). 
     For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. 
     3. Digital Assistant System 
       FIG. 7A  illustrates a block diagram of digital assistant system  700  in accordance with various examples. In some examples, digital assistant system  700  can be implemented on a standalone computer system. In some examples, digital assistant system  700  can be distributed across multiple computers. In some examples, some of the modules and functions of the digital assistant can be divided into a server portion and a client portion, where the client portion resides on one or more user devices (e.g., devices  104 ,  122 ,  200 ,  400 , or  600 ) and communicates with the server portion (e.g., server system  108 ) through one or more networks, e.g., as shown in  FIG. 1 . In some examples, digital assistant system  700  can be an implementation of server system  108  (and/or DA server  106 ) shown in  FIG. 1 . It should be noted that digital assistant system  700  is only one example of a digital assistant system, and that digital assistant system  700  can have more or fewer components than shown, may combine two or more components, or may have a different configuration or arrangement of the components. The various components shown in  FIG. 7A  can be implemented in hardware, software instructions for execution by one or more processors, firmware, including one or more signal processing and/or application specific integrated circuits, or a combination thereof. 
     Digital assistant system  700  can include memory  702 , one or more processors  704 , input/output (I/O) interface  706 , and network communications interface  708 . These components can communicate with one another over one or more communication buses or signal lines  710 . 
     In some examples, memory  702  can include a non-transitory computer-readable medium, such as high-speed random access memory and/or a non-volatile computer-readable storage medium (e.g., one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices). 
     In some examples, I/O interface  706  can couple input/output devices  716  of digital assistant system  700 , such as displays, keyboards, touch screens, and microphones, to user interface module  722 . I/O interface  706 , in conjunction with user interface module  722 , can receive user inputs (e.g., voice input, keyboard inputs, touch inputs, etc.) and processes them accordingly. In some examples, e.g., when the digital assistant is implemented on a standalone user device, digital assistant system  700  can include any of the components and I/O communication interfaces described with respect to devices  200 ,  400 , or  600  in  FIGS. 2A, 4, 6A -B, respectively. In some examples, digital assistant system  700  can represent the server portion of a digital assistant implementation, and can interact with the user through a client-side portion residing on a user device (e.g., devices  104 ,  200 ,  400 , or  600 ). 
     In some examples, the network communications interface  708  can include wired communication port(s)  712  and/or wireless transmission and reception circuitry  714 . The wired communication port(s) can receive and send communication signals via one or more wired interfaces, e.g., Ethernet, Universal Serial Bus (USB), FIREWIRE, etc. The wireless circuitry  714  can receive and send RF signals and/or optical signals from/to communications networks and other communications devices. The wireless communications can use any of a plurality of communications standards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA, Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communication protocol. Network communications interface  708  can enable communication between digital assistant system  700  with networks, such as the Internet, an intranet, and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN), and/or a metropolitan area network (MAN), and other devices. 
     In some examples, memory  702 , or the computer-readable storage media of memory  702 , can store programs, modules, instructions, and data structures including all or a subset of: operating system  718 , communications module  720 , user interface module  722 , one or more applications  724 , and digital assistant module  726 . In particular, memory  702 , or the computer-readable storage media of memory  702 , can store instructions for performing the processes described below. One or more processors  704  can execute these programs, modules, and instructions, and reads/writes from/to the data structures. 
     Operating system  718  (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OS X, WINDOWS, or an embedded operating system such as VxWorks) can include various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communications between various hardware, firmware, and software components. 
     Communications module  720  can facilitate communications between digital assistant system  700  with other devices over network communications interface  708 . For example, communications module  720  can communicate with RF circuitry  208  of electronic devices such as devices  200 ,  400 , and  600  shown in  FIG. 2A, 4, 6A -B, respectively. Communications module  720  can also include various components for handling data received by wireless circuitry  714  and/or wired communications port  712 . 
     User interface module  722  can receive commands and/or inputs from a user via I/O interface  706  (e.g., from a keyboard, touch screen, pointing device, controller, and/or microphone), and generate user interface objects on a display. User interface module  722  can also prepare and deliver outputs (e.g., speech, sound, animation, text, icons, vibrations, haptic feedback, light, etc.) to the user via the I/O interface  706  (e.g., through displays, audio channels, speakers, touch-pads, etc.). 
     Applications  724  can include programs and/or modules that are configured to be executed by one or more processors  704 . For example, if the digital assistant system is implemented on a standalone user device, applications  724  can include user applications, such as games, a calendar application, a navigation application, or an email application. If digital assistant system  700  is implemented on a server, applications  724  can include resource management applications, diagnostic applications, or scheduling applications, for example. 
     Memory  702  can also store digital assistant module  726  (or the server portion of a digital assistant). In some examples, digital assistant module  726  can include the following sub-modules, or a subset or superset thereof: input/output processing module  728 , speech-to-text (STT) processing module  730 , natural language processing module  732 , dialogue flow processing module  734 , task flow processing module  736 , service processing module  738 , and speech synthesis module  740 . Each of these modules can have access to one or more of the following systems or data and models of the digital assistant module  726 , or a subset or superset thereof: ontology  760 , vocabulary index  744 , user data  748 , task flow models  754 , service models  756 , and ASR systems. 
     In some examples, using the processing modules, data, and models implemented in digital assistant module  726 , the digital assistant can perform at least some of the following: converting speech input into text; identifying a user&#39;s intent expressed in a natural language input received from the user; actively eliciting and obtaining information needed to fully infer the user&#39;s intent (e.g., by disambiguating words, games, intentions, etc.); determining the task flow for fulfilling the inferred intent; and executing the task flow to fulfill the inferred intent. 
     In some examples, as shown in  FIG. 7B , I/O processing module  728  can interact with the user through I/O devices  716  in  FIG. 7A  or with a user device (e.g., devices  104 ,  200 ,  400 , or  600 ) through network communications interface  708  in  FIG. 7A  to obtain user input (e.g., a speech input) and to provide responses (e.g., as speech outputs) to the user input. I/O processing module  728  can optionally obtain contextual information associated with the user input from the user device, along with or shortly after the receipt of the user input. The contextual information can include user-specific data, vocabulary, and/or preferences relevant to the user input. In some examples, the contextual information also includes software and hardware states of the user device at the time the user request is received, and/or information related to the surrounding environment of the user at the time that the user request was received. In some examples, I/O processing module  728  can also send follow-up questions to, and receive answers from, the user regarding the user request. When a user request is received by I/O processing module  728  and the user request can include speech input, I/O processing module  728  can forward the speech input to STT processing module  730  (or speech recognizer) for speech-to-text conversions. 
     STT processing module  730  can include one or more ASR systems. The one or more ASR systems can process the speech input that is received through I/O processing module  728  to produce a recognition result. Each ASR system can include a front-end speech pre-processor. The front-end speech pre-processor can extract representative features from the speech input. For example, the front-end speech pre-processor can perform a Fourier transform on the speech input to extract spectral features that characterize the speech input as a sequence of representative multi-dimensional vectors. Further, each ASR system can include one or more speech recognition models (e.g., acoustic models and/or language models) and can implement one or more speech recognition engines. Examples of speech recognition models can include Hidden Markov Models, Gaussian-Mixture Models, Deep Neural Network Models, n-gram language models, and other statistical models. Examples of speech recognition engines can include the dynamic time warping based engines and weighted finite-state transducers (WFST) based engines. The one or more speech recognition models and the one or more speech recognition engines can be used to process the extracted representative features of the front-end speech pre-processor to produce intermediate recognitions results (e.g., phonemes, phonemic strings, and sub-words), and ultimately, text recognition results (e.g., words, word strings, or sequence of tokens). In some examples, the speech input can be processed at least partially by a third-party service or on the user&#39;s device (e.g., device  104 ,  200 ,  400 , or  600 ) to produce the recognition result. Once STT processing module  730  produces recognition results containing a text string (e.g., words, or sequence of words, or sequence of tokens), the recognition result can be passed to natural language processing module  732  for intent deduction. 
     More details on the speech-to-text processing are described in U.S. Utility application Ser. No. 13/236,942 for “Consolidating Speech Recognition Results,” filed on Sep. 20, 2011, the entire disclosure of which is incorporated herein by reference. 
     In some examples, STT processing module  730  can include and/or access a vocabulary of recognizable words via phonetic alphabet conversion module  731 . Each vocabulary word can be associated with one or more candidate pronunciations of the word represented in a speech recognition phonetic alphabet. In particular, the vocabulary of recognizable words can include a word that is associated with a plurality of candidate pronunciations. For example, the vocabulary may include the word “tomato” that is associated with the candidate pronunciations of / /and / /. Further, vocabulary words can be associated with custom candidate pronunciations that are based on previous speech inputs from the user. Such custom candidate pronunciations can be stored in STT processing module  730  and can be associated with a particular user via the user&#39;s profile on the device. In some examples, the candidate pronunciations for words can be determined based on the spelling of the word and one or more linguistic and/or phonetic rules. In some examples, the candidate pronunciations can be manually generated, e.g., based on known canonical pronunciations. 
     In some examples, the candidate pronunciations can be ranked based on the commonness of the candidate pronunciation. For example, the candidate pronunciation / / can be ranked higher than / /, because the former is a more commonly used pronunciation (e.g., among all users, for users in a particular geographical region, or for any other appropriate subset of users). In some examples, candidate pronunciations can be ranked based on whether the candidate pronunciation is a custom candidate pronunciation associated with the user. For example, custom candidate pronunciations can be ranked higher than canonical candidate pronunciations. This can be useful for recognizing proper nouns having a unique pronunciation that deviates from canonical pronunciation. In some examples, candidate pronunciations can be associated with one or more speech characteristics, such as geographic origin, nationality, or ethnicity. For example, the candidate pronunciation / / can be associated with the United States, whereas the candidate pronunciation / / can be associated with Great Britain. Further, the rank of the candidate pronunciation can be based on one or more characteristics (e.g., geographic origin, nationality, ethnicity, etc.) of the user stored in the user&#39;s profile on the device. For example, it can be determined from the user&#39;s profile that the user is associated with the United States. Based on the user being associated with the United States, the candidate pronunciation / / (associated with the United States) can be ranked higher than the candidate pronunciation / / (associated with Great Britain). In some examples, one of the ranked candidate pronunciations can be selected as a predicted pronunciation (e.g., the most likely pronunciation). 
     When a speech input is received, STT processing module  730  can be used to determine the phonemes corresponding to the speech input (e.g., using an acoustic model), and then attempt to determine words that match the phonemes (e.g., using a language model). For example, if STT processing module  730  can first identify the sequence of phonemes / /corresponding to a portion of the speech input, it can then determine, based on vocabulary index  744 , that this sequence corresponds to the word “tomato.” 
     In some examples, STT processing module  730  can use approximate matching techniques to determine words in an utterance. Thus, for example, the STT processing module  730  can determine that the sequence of phonemes / / corresponds to the word “tomato,” even if that particular sequence of phonemes is not one of the candidate sequence of phonemes for that word. 
     Natural language processing module  732  (“natural language processor”) of the digital assistant can take the sequence of words or tokens (“token sequence”) generated by STT processing module  730 , and attempt to associate the token sequence with one or more “actionable intents” recognized by the digital assistant. An “actionable intent” can represent a task that can be performed by the digital assistant, and can have an associated task flow implemented in task flow models  754 . The associated task flow can be a series of programmed actions and steps that the digital assistant takes in order to perform the task. The scope of a digital assistant&#39;s capabilities can be dependent on the number and variety of task flows that have been implemented and stored in task flow models  754 , or in other words, on the number and variety of “actionable intents” that the digital assistant recognizes. The effectiveness of the digital assistant, however, can also be dependent on the assistant&#39;s ability to infer the correct “actionable intent(s)” from the user request expressed in natural language. 
     In some examples, in addition to the sequence of words or tokens obtained from STT processing module  730 , natural language processing module  732  can also receive contextual information associated with the user request, e.g., from I/O processing module  728 . The natural language processing module  732  can optionally use the contextual information to clarify, supplement, and/or further define the information contained in the token sequence received from STT processing module  730 . The contextual information can include, for example, user preferences, hardware, and/or software states of the user device, sensor information collected before, during, or shortly after the user request, prior interactions (e.g., dialogue) between the digital assistant and the user, and the like. As described herein, contextual information can be dynamic, and can change with time, location, content of the dialogue, and other factors. 
     In some examples, the natural language processing can be based on, e.g., ontology  760 . Ontology  760  can be a hierarchical structure containing many nodes, each node representing either an “actionable intent” or a “property” relevant to one or more of the “actionable intents” or other “properties.” As noted above, an “actionable intent” can represent a task that the digital assistant is capable of performing, i.e., it is “actionable” or can be acted on. A “property” can represent a parameter associated with an actionable intent or a sub-aspect of another property. A linkage between an actionable intent node and a property node in ontology  760  can define how a parameter represented by the property node pertains to the task represented by the actionable intent node. 
     In some examples, ontology  760  can be made up of actionable intent nodes and property nodes. Within ontology  760 , each actionable intent node can be linked to one or more property nodes either directly or through one or more intermediate property nodes. Similarly, each property node can be linked to one or more actionable intent nodes either directly or through one or more intermediate property nodes. For example, as shown in  FIG. 7C , ontology  760  can include a “restaurant reservation” node (i.e., an actionable intent node). Property nodes “restaurant,” “date/time” (for the reservation), and “party size” can each be directly linked to the actionable intent node (i.e., the “restaurant reservation” node). 
     In addition, property nodes “cuisine,” “price range,” “phone number,” and “location” can be sub-nodes of the property node “restaurant,” and can each be linked to the “restaurant reservation” node (i.e., the actionable intent node) through the intermediate property node “restaurant.” For another example, as shown in  FIG. 7C , ontology  760  can also include a “set reminder” node (i.e., another actionable intent node). Property nodes “date/time” (for setting the reminder) and “subject” (for the reminder) can each be linked to the “set reminder” node. Since the property “date/time” can be relevant to both the task of making a restaurant reservation and the task of setting a reminder, the property node “date/time” can be linked to both the “restaurant reservation” node and the “set reminder” node in ontology  760 . 
     An actionable intent node, along with its linked concept nodes, can be described as a “domain.” In the present discussion, each domain can be associated with a respective actionable intent, and refers to the group of nodes (and the relationships there between) associated with the particular actionable intent. For example, ontology  760  shown in  FIG. 7C  can include an example of restaurant reservation domain  762  and an example of reminder domain  764  within ontology  760 . The restaurant reservation domain includes the actionable intent node “restaurant reservation,” property nodes “restaurant,” “date/time,” and “party size,” and sub-property nodes “cuisine,” “price range,” “phone number,” and “location.” Reminder domain  764  can include the actionable intent node “set reminder,” and property nodes “subject” and “date/time.” In some examples, ontology  760  can be made up of many domains. Each domain can share one or more property nodes with one or more other domains. For example, the “date/time” property node can be associated with many different domains (e.g., a scheduling domain, a travel reservation domain, a movie ticket domain, etc.), in addition to restaurant reservation domain  762  and reminder domain  764 . 
     While  FIG. 7C  illustrates two example domains within ontology  760 , other domains can include, for example, “find a movie,” “initiate a phone call,” “find directions,” “schedule a meeting,” “send a message,” and “provide an answer to a question,” “read a list,” “providing navigation instructions,” “provide instructions for a task” and so on. A “send a message” domain can be associated with a “send a message” actionable intent node, and may further include property nodes such as “recipient(s),” “message type,” and “message body.” The property node “recipient” can be further defined, for example, by the sub-property nodes such as “recipient name” and “message address.” 
     In some examples, ontology  760  can include all the domains (and hence actionable intents) that the digital assistant is capable of understanding and acting upon. In some examples, ontology  760  can be modified, such as by adding or removing entire domains or nodes, or by modifying relationships between the nodes within the ontology  760 . 
     In some examples, nodes associated with multiple related actionable intents can be clustered under a “super domain” in ontology  760 . For example, a “travel” super-domain can include a cluster of property nodes and actionable intent nodes related to travel. The actionable intent nodes related to travel can include “airline reservation,” “hotel reservation,” “car rental,” “get directions,” “find points of interest,” and so on. The actionable intent nodes under the same super domain (e.g., the “travel” super domain) can have many property nodes in common. For example, the actionable intent nodes for “airline reservation,” “hotel reservation,” “car rental,” “get directions,” and “find points of interest” can share one or more of the property nodes “start location,” “destination,” “departure date/time,” “arrival date/time,” and “party size.” 
     In some examples, each node in ontology  760  can be associated with a set of words and/or phrases that are relevant to the property or actionable intent represented by the node. The respective set of words and/or phrases associated with each node can be the so-called “vocabulary” associated with the node. The respective set of words and/or phrases associated with each node can be stored in vocabulary index  744  in association with the property or actionable intent represented by the node. For example, returning to  FIG. 7B , the vocabulary associated with the node for the property of “restaurant” can include words such as “food,” “drinks,” “cuisine,” “hungry,” “eat,” “pizza,” “fast food,” “meal,” and so on. For another example, the vocabulary associated with the node for the actionable intent of “initiate a phone call” can include words and phrases such as “call,” “phone,” “dial,” “ring,” “call this number,” “make a call to,” and so on. The vocabulary index  744  can optionally include words and phrases in different languages. 
     Natural language processing module  732  can receive the token sequence (e.g., a text string) from STT processing module  730 , and determine what nodes are implicated by the words in the token sequence. In some examples, if a word or phrase in the token sequence is found to be associated with one or more nodes in ontology  760  (via vocabulary index  744 ), the word or phrase can “trigger” or “activate” those nodes. Based on the quantity and/or relative importance of the activated nodes, natural language processing module  732  can select one of the actionable intents as the task that the user intended the digital assistant to perform. In some examples, the domain that has the most “triggered” nodes can be selected. In some examples, the domain having the highest confidence value (e.g., based on the relative importance of its various triggered nodes) can be selected. In some examples, the domain can be selected based on a combination of the number and the importance of the triggered nodes. In some examples, additional factors are considered in selecting the node as well, such as whether the digital assistant has previously correctly interpreted a similar request from a user. 
     User data  748  can include user-specific information, such as user-specific vocabulary, user preferences, user address, user&#39;s default and secondary languages, user&#39;s contact list, and other short-term or long-term information for each user. In some examples, natural language processing module  732  can use the user-specific information to supplement the information contained in the user input to further define the user intent. For example, for a user request “invite my friends to my birthday party,” natural language processing module  732  can be able to access user data  748  to determine who the “friends” are and when and where the “birthday party” would be held, rather than requiring the user to provide such information explicitly in his/her request. 
     Other details of searching an ontology based on a token string is described in U.S. Utility application Ser. No. 12/341,743 for “Method and Apparatus for Searching Using An Active Ontology,” filed Dec. 22, 2008, the entire disclosure of which is incorporated herein by reference. 
     In some examples, once natural language processing module  732  identifies an actionable intent (or domain) based on the user request, natural language processing module  732  can generate a structured query to represent the identified actionable intent. In some examples, the structured query can include parameters for one or more nodes within the domain for the actionable intent, and at least some of the parameters are populated with the specific information and requirements specified in the user request. For example, the user may say “Make me a dinner reservation at a sushi place at 7.” In this case, natural language processing module  732  can be able to correctly identify the actionable intent to be “restaurant reservation” based on the user input. According to the ontology, a structured query for a “restaurant reservation” domain may include parameters such as {Cuisine}, {Time}, {Date}, {Party Size}, and the like. In some examples, based on the speech input and the text derived from the speech input using STT processing module  730 , natural language processing module  732  can generate a partial structured query for the restaurant reservation domain, where the partial structured query includes the parameters {Cuisine=“Sushi”} and {Time=“7 pm”}. However, in this example, the user&#39;s utterance contains insufficient information to complete the structured query associated with the domain. Therefore, other necessary parameters such as {Party Size} and {Date} may not be specified in the structured query based on the information currently available. In some examples, natural language processing module  732  can populate some parameters of the structured query with received contextual information. For example, in some examples, if the user requested a sushi restaurant “near me,” natural language processing module  732  can populate a {location} parameter in the structured query with GPS coordinates from the user device. 
     In some examples, natural language processing module  732  can pass the generated structured query (including any completed parameters) to task flow processing module  736  (“task flow processor”). Task flow processing module  736  can be configured to receive the structured query from natural language processing module  732 , complete the structured query, if necessary, and perform the actions required to “complete” the user&#39;s ultimate request. In some examples, the various procedures necessary to complete these tasks can be provided in task flow models  754 . In some examples, task flow models  754  can include procedures for obtaining additional information from the user and task flows for performing actions associated with the actionable intent. 
     As described above, in order to complete a structured query, task flow processing module  736  may need to initiate additional dialogue with the user in order to obtain additional information, and/or disambiguate potentially ambiguous utterances. When such interactions are necessary, task flow processing module  736  can invoke dialogue flow processing module  734  to engage in a dialogue with the user. In some examples, dialogue flow processing module  734  can determine how (and/or when) to ask the user for the additional information and receives and processes the user responses. The questions can be provided to and answers can be received from the users through I/O processing module  728 . In some examples, dialogue flow processing module  734  can present dialogue output to the user via audio and/or visual output, and receives input from the user via spoken or physical (e.g., clicking) responses. Continuing with the example above, when task flow processing module  736  invokes dialogue flow processing module  734  to determine the “party size” and “date” information for the structured query associated with the domain “restaurant reservation,” dialogue flow processing module  734  can generate questions such as “For how many people?” and “On which day?” to pass to the user. Once answers are received from the user, dialogue flow processing module  734  can then populate the structured query with the missing information, or pass the information to task flow processing module  736  to complete the missing information from the structured query. 
     Once task flow processing module  736  has completed the structured query for an actionable intent, task flow processing module  736  can proceed to perform the ultimate task associated with the actionable intent. Accordingly, task flow processing module  736  can execute the steps and instructions in the task flow model according to the specific parameters contained in the structured query. For example, the task flow model for the actionable intent of “restaurant reservation” can include steps and instructions for contacting a restaurant and actually requesting a reservation for a particular party size at a particular time. For example, using a structured query such as: {restaurant reservation, restaurant=ABC Café, date=Mar. 12, 2012, time=7 pm, party size=5}, task flow processing module  736  can perform the steps of: (1) logging onto a server of the ABC Café or a restaurant reservation system such as OPENTABLE®, (2) entering the date, time, and party size information in a form on the website, (3) submitting the form, and (4) making a calendar entry for the reservation in the user&#39;s calendar. 
     In some examples, task flow processing module  736  can employ the assistance of service processing module  738  (“service processing module”) to complete a task requested in the user input or to provide an informational answer requested in the user input. For example, service processing module  738  can act on behalf of task flow processing module  736  to make a phone call, set a calendar entry, invoke a map search, invoke or interact with other user applications installed on the user device, and invoke or interact with third-party services (e.g., a restaurant reservation portal, a social networking website, a banking portal, etc.). In some examples, the protocols and application programming interfaces (API) required by each service can be specified by a respective service model among service models  756 . Service processing module  738  can access the appropriate service model for a service and generate requests for the service in accordance with the protocols and APIs required by the service according to the service model. 
     For example, if a restaurant has enabled an online reservation service, the restaurant can submit a service model specifying the necessary parameters for making a reservation and the APIs for communicating the values of the necessary parameter to the online reservation service. When requested by task flow processing module  736 , service processing module  738  can establish a network connection with the online reservation service using the web address stored in the service model, and send the necessary parameters of the reservation (e.g., time, date, party size) to the online reservation interface in a format according to the API of the online reservation service. 
     In some examples, natural language processing module  732 , dialogue flow processing module  734 , and task flow processing module  736  can be used collectively and iteratively to infer and define the user&#39;s intent, obtain information to further clarify and refine the user intent, and finally generate a response (i.e., an output to the user, or the completion of a task) to fulfill the user&#39;s intent. The generated response can be a dialogue response to the speech input that at least partially fulfills the user&#39;s intent. Further, in some examples, the generated response can be output as a speech output. In these examples, the generated response can be sent to speech synthesis module  740  (e.g., speech synthesizer) where it can be processed to synthesize the dialogue response in speech form. In yet other examples, the generated response can be data content relevant to satisfying a user request in the speech input. 
     Speech synthesis module  740  can be configured to synthesize speech outputs for presentation to the user. Speech synthesis module  740  synthesizes speech outputs based on text provided by the digital assistant. For example, the generated dialogue response can be in the form of a text string. Speech synthesis module  740  can convert the text string to an audible speech output. Speech synthesis module  740  can use any appropriate speech synthesis technique in order to generate speech outputs from text, including, but not limited, to concatenative synthesis, unit selection synthesis, diphone synthesis, domain-specific synthesis, formant synthesis, articulatory synthesis, hidden Markov model (HMM) based synthesis, and sinewave synthesis. In some examples, speech synthesis module  740  can be configured to synthesize individual words based on phonemic strings corresponding to the words. For example, a phonemic string can be associated with a word in the generated dialogue response. The phonemic string can be stored in metadata associated with the word. Speech synthesis model  740  can be configured to directly process the phonemic string in the metadata to synthesize the word in speech form. 
     In some examples, instead of (or in addition to) using speech synthesis module  740 , speech synthesis can be performed on a remote device (e.g., the server system  108 ), and the synthesized speech can be sent to the user device for output to the user. For example, this can occur in some implementations where outputs for a digital assistant are generated at a server system. And because server systems generally have more processing power or resources than a user device, it can be possible to obtain higher quality speech outputs than would be practical with client-side synthesis. 
     Additional details on digital assistants can be found in the U.S. Utility application Ser. No. 12/987,982, entitled “Intelligent Automated Assistant,” filed Jan. 10, 2011, and U.S. Utility application Ser. No. 13/251,088, entitled “Generating and Processing Task Items That Represent Tasks to Perform,” filed Sep. 30, 2011, the entire disclosures of which are incorporated herein by reference. 
     4. Processes for Operating a Digital Assistant in a Messaging Environment 
       FIGS. 8, 11A -D, and  13 A-C illustrate processes  800 ,  1100 , and  1300  for operating a digital assistant in a messaging environment according to various examples.  FIGS. 9A-L ,  12 A-H, and  14 A-I illustrate exemplary user interfaces of an electronic device for operating a digital assistant in a messaging environment according to various examples. Processes  800 ,  1100 , and  1300  can be performed using one or more electronic devices implementing a digital assistant. In some examples, the processes can be performed at a client-server system (e.g., system  100 ) implementing a digital assistant. In some examples, the processes can be performed at an electronic device (e.g., device  104 ,  200 ,  400 , or  600 ). In processes  800 ,  1100 , and  1300 , some blocks are, optionally, combined, the order of some blocks are, optionally, changed, and some blocks are, optionally, omitted. Further, one of ordinary skill would appreciate that the blocks of one exemplary process can be implemented in another exemplary process. For example, the blocks of processes  1100  or  1300  can be implemented in process  800 . 
     Process  800  is described below with simultaneous reference to  FIGS. 8 and 9A -L. At block  802 , a graphical user interface (GUI) can be displayed on the display (e.g., touch screen  212  or display  440 ) of an electronic device. For example, as shown in  FIG. 9A , GUI  902  of electronic device  900  can be displayed. Electronic device  900  can be similar to one or more of devices  104 ,  200 ,  400 , or  600 , described above, and can implement a digital assistant. GUI  902  can be a GUI of a messaging application (e.g., messaging application implemented by instant messaging module  241 ) of the electronic device. The messaging application can be configured to send messages to and receive messages from one or more recipients. As shown, GUI  902  can include plurality of previous messages  903  that were previously exchanged between a user of electronic device  900  and the digital assistant. In particular, plurality of previous messages  903  can include previous messages from the user addressed to the digital assistant and previous messages generated by the digital assistant in response to the user&#39;s previous messages. For example, previous message  910  of plurality of previous messages  903  can be generated from user input and addressed to the digital assistant. Previous message  912  of plurality of previous messages  903  can be generated by the digital assistant in response to previous message  910  from the user. 
     As shown, plurality of previous messages  903  in GUI  902  can be presented in a conversational view. In particular, plurality of previous messages  903  can be displayed in chronological order. In the present example, plurality of previous messages  903  are displayed in chronological order from top to bottom where the oldest previous message is displayed at the top of GUI  902  and the most recent previous message is displayed at the bottom of GUI  902 . Further, messages from the user can be displayed on a side of GUI  902  opposite from that of messages from the digital assistant. In particular, previous messages from the user (e.g., previous message  910 ) can be justified on the right side of GUI  902  whereas previous messages from the digital assistant (e.g., previous message  912 ) can be justified on the left side of GUI  902 . 
     The plurality of previous messages can include one or more interactive sessions between the user and the digital assistant. Each interactive session can include two or more previous messages. In particular, an interactive session can be initiated by an initial request from a user and the messages in the interactive session can each be relevant to the initial request. For example, previous messages  910  and  912  can be part of the same interactive session. 
     The plurality of previous messages can represent a text history of all previous interactive sessions between the user and the digital assistant (e.g., since the last time the message history was cleared). The previous interactive sessions can include text-based interactions via the messaging application or voice-based interactions via a digital assistant interface separate from the messaging application. For example, as shown in  FIG. 9A , previous messages  914  and  916  can be text transcriptions of a previous voice-based interaction between the user and the digital assistant that occurred outside of the messaging application. The previous voice-based interaction may have occurred prior to receiving the user input at block  806  of process  800  and may have been initiated when a user input was previously detected at the electronic device to invoke the digital assistant. Detecting the user input can include, for example, detecting the push of a button on the electronic device or detecting the selection of an affordance on the electronic device. In response to detecting the user input, the electronic device can sampled audio containing a user utterance. In this example, the user utterance can include the request “Calories in chocolate bar.” The electronic device can cause the user utterance to be transcribed to text and the text representation of the user utterance can be included in GUI  902  as previous message  914 . The electronic device can further cause an action to be performed in accordance with a user intent derived from the user utterance. In particular, the sampled audio data can be transmitted to a digital assistant server (e.g., DA server  106 ) to determine an actionable intent based on the user utterance and generate a task flow corresponding to the actionable intent. Alternatively, the electronic device can process the sampled audio data locally to determine the actionable intent and generate the corresponding task flow. The task flow can be executed by the digital assistant server and/or the electronic device to perform the action. In this example, the performed action can be a search for the number of calories in a chocolate bar. A response based on the results obtained from the search can be outputted by the electronic device action. For example, the response can provide the number of calories in a milk chocolate bar. As shown in  FIG. 9A , a text representation of the response can be included in GUI  902  as previous message  916 . 
     Each of the plurality of previous messages can be associated with a previous contextual state of the electronic device. The previous contextual state can be similar to the contextual state stored at block  810 , described below. In particular, the previous contextual state can include information related to the state of the electronic device at the time user input associated with the previous message was received. For example, the previous contextual state can include temporal information (e.g., the time) defining when the user input was received or location information defining the location of the electronic device at the time the user input was received. Further, a pair of previous messages comprising the user input and the corresponding response to the user input from the digital assistant can be associated with the same previous contextual state. For example, previous messages  910  and  912  can be associated with the same previous contextual state. In particular, the previous contextual state of previous message  910  and  912  can be the state of the electronic device at the time user input associated with previous message  910  was received. Further, the previous contextual state associated with previous messages  910  and  912  can be different from the previous contextual state associated with previous messages  914  and  916 . 
     In some examples, the previous contextual state of the electronic device associated with a previous message can optionally be utilized during a current interactive session between the user and the digital assistant. For example, the user may wish to find a restaurant at the location associated with a specific previous message. In these examples, block  804  can be performed. 
     At block  804 , a user selection of a first previous message of the plurality of previous messages can be detected. The user selection can be any suitable user input associated with the first previous message. In particular, the user selection can be detected via GUI  902 . The first previous message can be associated with a first previous contextual state of the electronic device. In response to detecting the user selection of the first previous message, the first previous contextual state of the electronic device can be retrieved. The retrieved first previous contextual state can then be utilized to process a user input (e.g., user input of block  806 ) representing a user request. In some examples, block  804  can be performed prior to block  806 . In other examples, block  804  can be performed after block  806  and before block  808 . 
     At block  806 , user input can be received. The user input can be received via a user input interface of the electronic device. As shown in  FIG. 9B , GUI  902  can include user input interface  910 . The user input can include text and/or a media object. Text input can be received via keyboard  911  of user input interface  910 . Alternatively, text input can be received using dictation button  905 , which enables a user utterance received via the microphone (e.g., microphone  213 ) of the electronic device to be transcribed into text. The media object can be an image, an audio clip, a video clip, or the like. A media object can be received using image/video button  904  and audio button  908 . In particular, selection of image/video button  904  can enable the user to retrieve an image/video stored on the electronic device or to capture a new image/video using the camera (e.g., optical sensor  264 ) of electronic device. Selection of audio button  908  can enable the user to record an audio clip via the microphone (e.g., microphone  213 ) of the electronic device. User input received via user input interface  910  can be displayed in text input field  906  before being submitted. The user input can represent a user request to perform a task or retrieve information. The user input can be in natural language form. In the present example shown in  FIG. 9B , the user input can be text input  918  “How are the Giants doing?” 
     In some examples, the user can leverage previous messages to enable quicker entry of user input. In particular, a previous message of the plurality of previous messages can be selected to auto-populate the text input field of the user input interface. For example, with reference to  FIG. 9A , a user input associated with previous message  910  can be detected. The user input can be a user selection of previous message  910  via GUI  902 . In response to detecting the user input associated with previous message  910 , text of previous message  910  (e.g., “Tell John Smith I&#39;ll be late.”) can be displayed in text input field  906  of GUI  902 . This can be desirable to allow a user to input a request with few actions and in less time. For example, if the user wishes to input the text “Tell John White I&#39;ll be late,” the user can auto-populate the text of previous message  910  in text input field  906  and change “Smith” to “White.” 
     At block  808 , the user input of block  806  can be displayed as a first message in the GUI. For example, with reference to  FIG. 9C , text input  918  can be displayed as message  922  in GUI  902 . In particular, message  922  can be addressed to the digital assistant. Block  808  can be performed in response to receiving the user input at block  806 . 
     At block  810 , the electronic device can store a contextual state of the electronic device corresponding to the displayed user input. In particular, the contextual state can be stored in association with the first message. The contextual state being stored can include the state of the electronic device at the time the user input was received at block  806 . In some examples, the contextual state of the electronic device can include temporal information of when the user input at block  806  was received. In some examples, the contextual state of the electronic device can include information derived from a physical sensor of the electronic device at the time the user input at block  806  was received (e.g., location information defining the location of the electronic device at the time the user input was received). In some examples, the contextual state of the electronic device can include information stored on the electronic device at the time the user input at block  806  was received. The information can be related to a predetermined application of the electronic device. For example, the information can include contact information, email messages, media files, calendar appointments, search histories, fitness data, or the like. In some examples, the information can include which applications are installed and/or actively running on the electronic device at the time the user input of block  806  was received. It should be appreciated that the contextual state of the electronic device can include various other types of contextual information associated with the electronic device at the time the user input of block  806  was received. In the present example shown in  FIG. 9C , the contextual state of the electronic device can include at least the time and date at which the user input of block  806  was received at the electronic device and the location of the electronic device at the time the user input of block  806  was received. The time, date, and location information can be stored on the electronic device in association with first message  922 . Block  810  can be performed in response to receiving the user input at block  806 . 
     At block  812 , the electronic device can cause an action to be performed in accordance with a user intent derived from the user input. Block  812  can be performed automatically without additional human intervention in response to receiving the user input at block  806  (or in response to displaying the first message at block  808 ). In particular, the electronic device can cause the user intent (e.g., actionable intent) to be determined (e.g., using natural language processing module  732 ) based on the user input of block  806  and cause a task flow corresponding to the user intent to be generated (e.g., using task flow processing module  736 ). The electronic device can further cause the task flow to be executed to perform the action. In the present example shown in  FIG. 9D , the user intent can be determined to be searching for recent sports scores related to the “Giants” and thus the action can be performing a search for recent sports scores related to the “Giants.” Results that at least partially satisfy the derived user intent can be obtained by performing the action. The displayed response at block  814  can thus be based on the results obtained by performing the action. 
     In some examples, receiving the user input at block  806  (or displaying the first message at block  808 ) can cause the electronic device to determine the user intent, generate the task flow, and perform the action. Alternatively, the electronic device can transmit a representation of the user input to a digital assistant server (e.g., DA server  106 ) and cause the digital assistant server to determine the user intent, generate the task flow, and perform the action. 
     In some examples, the stored contextual state of the electronic device of block  810  can be utilized to determine the user intent and thus the response displayed at block  814  can be based on the stored contextual state. For example, location information stored in association with first message  922  can indicate that the electronic device was located in San Francisco at the time text input  918  was received. Based on this location information, it can be determined that the user is more likely referring to the San Francisco Giants (baseball team) rather than the New York Giants (football team), and the action can include searching for the most recent scores related to the San Francisco Giants to obtain results. In particular, search results indicating that the San Francisco Giants won 7 to 1 over the San Diego Padres in its most recent game can be obtained. It should be appreciated that in other examples, the previous contextual states of any number of previous messages in GUI  902  can additionally or alternatively be used to determine the user intent. 
     At block  814 , a response based on the action of block  812  can be displayed as a second message in the GUI. For example, as shown in  FIG. 9D , second message  924  can be displayed in GUI  902 . Second message  924  can include a response based on the search results obtained at block  812 . In particular, second message  924  can include the search results indicating that the San Francisco Giants won 7 to 1 over the San Diego Padres in its most recent game. The response can at least partially satisfy the user request represented by the user input of block  806 . Further, the response can be in natural language form. 
     In some examples, the second message can be displayed without providing any audio output. For example, second message  924  can be displayed in GUI  902  without outputting any spoken audio corresponding to the text response in second message  924 . This can be desirable to preserve the text based interactive environment associated with the messaging platform. In particular, a user may prefer to interact with the digital assistant using the messaging platform rather than a voice/audio interface when voice/audio based interactions are not possible, such as in a noisy environment, in a public setting with little privacy, or in a quiet setting (e.g., library). 
     Second message  924  can include only text. In particular, as shown in  FIG. 9D , second message  924  can be concise with only a limited number of text sentence (e.g., at most one, two, or three sentences) and without any media object. Such concise responses facilitate the quick exchange of information, which is desired and expected by users in the messaging environment. In some examples, in order to provide the user with the option of obtaining a more detailed response, second message  924  can be configured to provide a more detailed response in accordance with a user selection of second message  924 . This can enable the desirable concise format to be preserved while providing convenient access to additional details responsive to the user request. For example, as shown in  FIG. 9D , block  814  can include displaying indication  926  (e.g., “Tap for details”) in second message  924  that a more detailed response is available by selecting second message  926 . In the present example, indication  926  can inform the user that second message  926  is configured to provide additional details related to the Giants in response to a user selection of second message  926 . 
     In some examples, a user selection of second message  924  can be received via GUI  902  of electronic device  900 . In the present example, the user selection of second message  926  can include a touch input via GUI  902  of electronic device  900 . It should be recognized that in other examples, the user selection can include any suitable user input associated with the second message. In response to receiving the user selection of second message  924 , detailed results based on the user intent can be obtained. In particular, receiving the user selection can cause an application of the electronic device to obtain additional results that satisfy the user intent. The application can be different from the messaging application. For example, the user selection of second message  924  can cause the Internet browser application (e.g., the Internet browser application of browser module  247 ) of the electronic device to perform a search based on the user intent and to obtain detailed results related to how the Giants are doing. The detailed results can include, for example, the total number of games won or lost by the Giants in the current season, news articles reporting the recent win against the Padres, future game schedules for the Giants, or the like. The obtained detailed result can be displayed in a GUI of the Internet browser application. 
     Whether or not the second message displayed at block  814  is selectable to provide a more detailed response can be based on the user intent derived from the user input at block  812 . For example, in determining the actionable intent corresponding to the user input at block  812 , a determination can be made as to whether the actionable intent is associated with one of a plurality of predetermined domains in the ontology. In some examples, the plurality of predetermined domains can include domains where a detailed response is most likely desired by the user. In particular, the plurality of predetermined domains can include domains such as “contacts,” “restaurants,” “movies,” “sports,” or “search.” In response to a determination that the actionable intent is associated with one of a plurality of predetermined domains, the displayed second message at block  814  can be configured to provide a more detailed response in accordance with a user selection of the second message. 
     In some examples, hyperlinks can be provided in the response of the second message to provide the user with access to additional information relevant to the user request. For example, one or more words (or one or more character strings) in the second message can be highlighted to indicate that additional information related to the highlighted words is available upon user selection. In particular, process  800  can identify one or more words (or one or more character strings) in the displayed response corresponding to an entity. The entity can be a person, team, business, location, event, building, object, media item, or the like. In some examples, the one or more words corresponding to an entity can be identified based on the derived user intent at block  812 . In the present example, the user intent can be determined to be associated with the domain “sports” and thus one or more words corresponding to a sports entity can be identified. In particular, as shown in  FIG. 9D , the words “Giants,” “Padres,” and “7 to 1” can be identified. Process  800  can further include determining an action associated with the entity. In some examples, the action can include obtaining information related to the entity. The action can be performed using an application of the electronic device other than the messaging application. The electronic device can enable the selection of the one or more identified words in the displayed response (e.g., hyperlinking). In particular, detecting a user selection of the one or more identified words can cause the action associated with the entity to be performed. For example, in response to detecting the user selection of the word “Giants” in message  924 , information related to the Giants can be retrieved using the Internet browser application. For example, the Internet browser application can be instructed to load the homepage of the Giants or perform an Internet search of the Giants. Although in  FIG. 9D , the one or more words are highlighted by underlining, it should be recognized that other means of highlighting can be implemented, such as, using different fonts, colors, bolding, or the like. 
     In some examples, the one or more words corresponding to an entity can be identified based on the contextual state of the electronic device. For example, the user intent can be related to contacts (e.g., sending a message to “John White”) and the one or more words can be identified based on a name or location stored in the contacts of the electronic device at the time the user input was received (e.g., “John White”). In response to detecting the user selection of the one or more identified words, the contact corresponding to the one or more identified words can be retrieved and displayed via, for example, a GUI of the contacts application. In another example, the user intent can be related to airline flights (e.g., searching for a flights landing in San Francisco from Chicago) and the response in the second message can include a flight numbers. Based on this user intent, the character string corresponding to the airline flight can be identified in the second message and can be highlighted and hyperlinked in the second message. In response to detecting the user selection of the flight number in the second message, the flight schedule and/or flight status associated with the flight number can be obtained and displayed (e.g., via a GUI of the Internet browser application). 
     In some examples, block  814  can further include displaying a media object in the GUI of the electronic device. The media object can be based on the user intent. In particular, the media object can at least partially satisfy the user request represented by the user input at block  806 . In some examples, the media object can be displayed in the second message. In other examples, the media object can be displayed in a separate message (e.g., a third message). The media object can be an image, an audio clip, a video, or the like. In some examples, the media object can be a snippet of a GUI of an application of the electronic device (e.g., an application other than the messaging application). In an illustrative example shown in  FIGS. 9E-F , the user input “Calendar today” can be received (e.g., at block  806 ). The user input can represent a user request to retrieve appointments from the calendar application schedule for today. In response to receiving the user input, the user input can be displayed in GUI  902  as message  928  (e.g., at block  808 ). Based on the user intent derived from the user input, the appointments scheduled for today can be retrieved from the calendar application of the electronic device (e.g., at block  812 ). Further, a snippet of the GUI of the calendar application depicting the appointments scheduled for today can be obtained (e.g., at block  812 ). A text response addressing the user request can be displayed as message  930  in GUI  902  (e.g., at block  814 ). Further the snippet of the GUI of the calendar application can be displayed as message  932  in GUI  902 . The snippet can be a graphical presentation of information requested by the user in the user input. 
     Displaying a media object in response to a user request in the user input can be desirable for presenting information that may otherwise be difficult to clearly and concisely present using text alone. In some examples, whether or not a media object is displayed in response to the user request can be based on the user intent derived from the user input. For example, in determining the actionable intent corresponding to the user input at block  812 , a determination can be made as to whether the actionable intent is associated with one of a second plurality of predetermined domains in the ontology. In some examples, the second plurality of predetermined domains can include domains where information can be more clearly and concisely displayed in graphical or multimedia form. In particular, the second plurality of predetermined domains can include domains such as “calendar,” “weather,” “stocks,” “maps,” “health,” or the like. In response to a determination that the actionable intent is associated with one of a second plurality of predetermined domains, a media object based on the user intent can be displayed at block  814 . 
     The displayed media object can be selectable to provide the user with expanded results associated with the media object. In particular, in response to detecting the user selection of the media object, expanded results can be obtained and displayed. The expanded results can be obtained and displayed by an application of the electronic device other than the messaging application. For example, the user selection of media object  932  in  FIG. 9F  can cause the calendar application to display a GUI of the calendar application with the user&#39;s appointments scheduled for today. The expanded results can be larger and contain more information than the media object displayed at block  814 . 
     As discussed above, the previous contextual state of the electronic device associated with a previous message in GUI  902  can be utilized to facilitate a current interactive session between the user and the digital assistant.  FIGS. 9G-H  illustrate an example where the previous contextual state of the electronic device can be utilized to satisfy a user request represented by the user input of block  806 . In this example, the user may have been traveling in an unfamiliar part of San Jose at the time previous message  910  was sent to the digital assistant. Further, the user may have noticed an interesting Mexican restaurant in that unfamiliar part of San Jose while sending previous message  910 . The user may utilize the previous contextual state of the electronic device associated with previous message  910  in order to look up that Mexican restaurant at a later time. In the present example, the user input “Show me Mexican restaurants near here” can be received (e.g., at block  806 ) and in response to the user input, the user input can be displayed as message  934  (e.g., at block  808 ) in GUI  902 . In response to detecting a user selection of previous message  910  (e.g., at block  804 ), the previous contextual state of the electronic device associated with previous message  910  can be retrieved. In particular, the previous contextual state of the electronic device associated with previous message  910  can include location information corresponding to the unfamiliar location in San Jose. The electronic device can cause an action to be performed in accordance with a user intent derived from the user input (e.g., at block  812 ). In response to detecting the user selection of previous message  910 , the user intent can be derived based on the retrieved previous contextual state of the electronic device associated with previous message  910 . In particular, it can be determined based on the user selection of previous message  910  that “near here” refers to the location of the electronic device at the time previous message  910  was sent (e.g., the unfamiliar part of San Jose). In this example, the action performed can be a search for Mexican restaurants near the location of the electronic device at the time previous message  910  was sent. The results obtained from the search are thus based on the previous contextual state of the electronic device associated with previous message  910 . As shown in  FIG. 9H , a response based on the obtained search results can be displayed as message  936 . In particular, a list of Mexican restaurants near the unfamiliar part of San Jose can be displayed (e.g., in a separate application of the electronic device) in response to the user selection of message  936 . 
     In some examples, the user input received at block  806  can include an ambiguous term. For example, in the user input of message  938  shown in  FIG. 9I , the user input “Who&#39;s John?” can include the ambiguous term “John,” which can have two or more interpretations. In particular, based on the contextual state of the electronic device at the time the user input of message  938  was received, it can be determined that there are three contacts (e.g., John White, John Smith, and John Woo) stored on the electronic device corresponding to the name “John.” In these examples, the displayed response of message  940  (e.g., at block  814 ) can include a request for additional information related to the ambiguous term. For example, as shown in  FIG. 9I , the request for additional information can include a list of possible interpretations (e.g., “John White,” “John Smith,” and “John Woo”) for the ambiguous term “John. 
     User input interface  910  can be utilized to facilitate user response to the request for additional information related to the ambiguous term. In particular, user input interface  910  can include auto-complete interface  907 . Auto-complete interface  907  can be configured to display suggested words or character strings that are a prediction of future user input. The suggested words or character strings can be based on one or more characters that the user has already inputted and is displayed in text field  906 . Additionally or alternatively, the suggested words or character strings can be based on the displayed response from the digital assistant. As shown in  FIG. 9J , two or more suggested character strings (e.g., “John White,” “John Smith,” and “John Woo”) can be displayed in auto-complete interface  907 . Each of the two or more suggested character strings can be responsive to the request for additional information. In particular, the two or more suggested character strings can include the list of possible interpretations of the ambiguous term (e.g., “John White,” “John Smith,” and “John Woo”). 
     A user input indicating a selection of one of the list of possible interpretations can be received. In some examples, the user input can be a user selection of a suggested character string of the two or more suggested character strings. For example, a user selection of the suggested character string “John White”  942  in auto-complete interface  907  can be detected and in response, the suggested character string “John White” can be displayed as message  944  in GUI  902 . It should be appreciated that, as an alternative to auto-complete interface  907 , a response to the request for additional information related to the ambiguous term can be provided via text input. For example, text input “John White” can be received via the keyboard of user input interface  910  to select the intended interpretation of the ambiguous term “John.” Further, as shown in  FIGS. 9I and 9J , the list of possible interpretations of the ambiguous term can be numbered and thus in some examples, the text input corresponding number of the intended interpretation can be received. In particular, the text input “3” can be received to indicate selection of “John White” as the intended interpretation of the ambiguous term “John.” 
     The electronic device can cause an action to be performed based on the user intent derived from the user input “Who&#39;s John?” and the user selection of “John White” as the intended interpretation of the ambiguous term “John.” As shown in  FIG. 9K , a response based on the performed action can be displayed as message  946 . In particular, the response can be based on the selected interpretation “John White.” In the present example, the contact information of “John White” can be displayed (e.g., using the contacts application of electronic device  1400 ) in response to the user selection of message  946 . 
     Although in the above examples, auto-complete interface  907  is utilized for responding to disambiguation requests of the digital assistant, it should be recognized that auto-complete interface  907  can further be utilized to response to digital assistant requests other than disambiguation requests. For example, in response to a user request for show times for a movie at a cinema, the digital assistant can provide show time options and then ask the user whether he or she would like to purchase tickets. In this example, the displayed response at block  814  can be “Here are some available show times today: 730 pm, 1045 pm, 1200 am. Would you like to purchase tickets?” To facilitate user response to the digital assistant&#39;s question, the electronic device can display the suggested character strings “Yes” and “No” in auto-complete interface  907  for user selection. In response to the user selection of the suggested character string “Yes,” the suggested character string “Yes” can be displayed as a message in the GUI. Further, a response based on the suggested character string “Yes” can be displayed. For example, the response can be a follow-up request asking the user which show time he or she would like to reserve. Alternatively, the response can be a message which when selected, causes a movie reservation website to be displayed on a GUI of the Internet browser application of the electronic device. 
     In some examples, notifications from various applications of the electronic device can be presented via the digital assistant on the messaging platform. The notifications can be received from applications of the electronic device other than the messaging application. In the present example shown in  FIG. 9L , the notification can be a calendar alert from the calendar application for a dentist appointment. The calendar alert can be based on user input received prior to receiving the notification. For example, the user input can be input for creating a calendar entry for the dentist appointment in the calendar application. In response to receiving the notification, the notification can be displayed as a message in the GUI. For example, as shown in  FIG. 9L , the notification for the dentist appointment can be displayed as message  948  in GUI  902 . Convey notifications from other applications via the digital assistant on the message application can allow users to rely on a single application as the central platform for all communication. This can be desirable to streamline user interactions and improve user experience. In particular, receiving notifications through the messaging platform can allow all notifications to be stored and organized in a single location for easy referencing. Further, the digital assistant can be readily available to perform any tasks related to the notification. For example, upon receiving message  948  notifying the user of the dentist appointment, the user can conveniently request the digital assistant to send a message to the dentist indicating that the user will be 5 minutes late. Because the notification is associated with context information such as the contact information of the dentist, a message can readily be sent to the dentist without the user having to take additional time looking up the contact information of the dentist using one application and the switch to a separate application to compose the desired message. Other examples of notifications can include reminder notifications from the task reminder application for a task, stock price alerts from the stock application, fitness notifications from the fitness application related to reaching a fitness goal, or the like. 
     As described above, each message in GUI  902  can be associated with a contextual state of the electronic device. The message history can thus serve as a contextual history of the electronic device. In some examples, it may be desirable for the user to bookmark certain messages that are associated with important contextual states. For example, previous message  910  can be associated with a location that the user may be interested in referring to in the future. In these examples, a user input associated with previous message  910  can be received. The user input can be a predefined user input received via GUI  902  to bookmark previous message  910 . In response to receiving the user input, a bookmark of previous message  910  can be stored in association with an affordance. The affordance can be displayed, for example, on a scroll bar (not shown) of GUI  902 . The position of the affordance on the scroll bar can correspond to the position of previous message  910  among the plurality of previous messages. Selecting the affordance by the user can causes a focus of GUI  902  to change to previous message  910 . 
     In some examples, the conversation history in GUI  902  can be synchronized with a corresponding GUI of the messaging application of a second electronic device. For example,  FIGS. 10A-C  illustrates electronic device  1000  displaying GUI  1002 . GUI  1002  can be the GUI of the messaging application of second electronic device  1000 . Second electronic device  1002  can be separate and different from electronic device  900 . Second electronic device  1000  can implement a digital assistant and the user can interact with the digital assistant of second electronic device  1000  via GUI  1002 . As shown in  FIG. 10A , GUI  1002  can include plurality of previous messages  1003  that are identical to plurality of previous messages  903 . In particular, plurality of previous messages  1003  include messages exchanges at electronic device  900  between the user and the digital assistant implemented on electronic device  900 . Electronic device  900  can cause plurality of previous messages  1003  to be displayed in GUI  1002  based on plurality of previous messages  903 . Further, as shown in  FIG. 10B , in response to displaying at block  808  the user input as first message  922  in GUI  902  of electronic device  900 , electronic device  900  can cause the same first message to be displayed as message  1022  in GUI  1002  of second electronic device  1000 . Similarly, in response to displaying at block  814  the response as second message  924  in GUI  902  of electronic device  900 , electronic device  800  can cause the same second message to be displayed as message  1024  in GUI  1002  of second electronic device  1000 . Thus, the message history at electronic device  900  between the user and the digital assistant can be accessible to the user when the user switches over to electronic device  1000 . 
     Each of plurality of previous messages  1003  can be associated with a previous contextual state of electronic device  900  corresponding to a respective one of plurality of previous messages  903 . Similarly, message  1022  can be associated with the same contextual state of electronic device  900  as message  922 . These contextual states (and previous contextual states) can be stored on electronic device  1000 . In some examples, the contextual state associated with a message generated at the electronic device can be utilized to process user requests addressed to the digital assistant of the second electronic device. For example, a user selection of message  1022  in GUI  1002  can be detected. In response to detecting the user selection of message  1022 , the contextual state of electronic device  900  associated with message  1022  can be retrieved. In the present example, the contextual state associated with message  1022  can include location information of electronic device  900  at the time message  922  was generated. In particular, the location information can indicate that electronic device  900  was in San Francisco at the time message  922  was generated. With reference to  FIG. 10C , a user input can be received at second electronic device  1000 . The user input can be similar to the user input received at block  806 . In particular, the user input can be received via a user input interface (not shown) of GUI  1002  that is similar to user input interface  910 . In this example, the user input can be the text “Find me a park near here.” In response to receiving the user input, the user input can be displayed as message  1034  in GUI  1002  of second electronic device  1000 . Second electronic device  1000  can cause an action to be performed in accordance with a user intent. Causing the action to be performed can be similar to block  812  described above. The user intent can be derived from the user input “Find me a park near here” and from the contextual state of electronic device  900  at the time message  922  was generated. As described above, the contextual state can include location information associated with the city of San Francisco. Based on this contextual state of electronic device  900 , it can be determined that the user intent is to search for parks in San Francisco and the performed action can thus be a search for parks in San Francisco. A response as message  1036  can be displayed in GUI  1002  of second electronic device  1000 . Displaying the response can be similar to block  814  described above. The response can be based on the performed action. Specifically, in the present example, the response in message  1036  can provide access to results obtained from performing a search for parks in San Francisco. 
     Process  1100  is described below with simultaneous reference to  FIGS. 11A-D  and  12 A-H. At block  1102 , a graphical user interface (GUI) having a plurality of previous messages between a user and the digital assistant can be displayed on the display of an electronic device. For example, as shown in  FIG. 12A , GUI  1202  of electronic device  1200  can be displayed. GUI  1202  can be a GUI of a messaging application of electronic device  1200 . GUI  1202  includes plurality of previous message  1203  between the user of electronic device  1200  and the digital assistant implemented on electronic device  1200 . Plurality of previous messages  1203  are presented in a conversational view. Electronic device  1200  can be similar to one or more of devices  104 ,  200 ,  400 ,  600 , or  900 . Block  1102  can be similar or identical to block  802  of process  800 . 
     At block  1104 , a first user input including a media object can be received. The media object can be an image, video clip, audio clip, or the like. In some examples, the media object can be received via a user input interface of GUI  1202 . The user input interface can be similar to user input interface  910 . For example, the media object can be received using buttons similar to image/video button  904  and audio button  908 , described above. The media object can be retrieved from the memory of electronic device  1200 . Alternatively, the media object can be generated based on input received via the microphone or the camera of electronic device  1200 . In the present example shown in  FIG. 12B , media object of user input can be an image of a business card. 
     At block  1106 , the media object can be displayed as a first message in the GUI. For example, as shown in  FIG. 12B , media object can be displayed as first message  1204  in GUI  1202 . In the present example, the image of the business card in first message  1204  can depict contact information of an individual (e.g., “Joe Black”). It should be recognized that in other examples, the image can depict contact information of any entity (e.g., a person, an organization, a business, etc.) The image can be captured by the user via the camera of electronic device  1200 . Block  1106  can be performed in response to receiving the first user input at block  1104 . 
     At block  1108 , a request for additional information related to the media object can be displayed as a second message. For example as shown in  FIG. 12C , second message  1206  can be displayed in GUI  1202 . In this example, second message  1206  includes the request “What should I do with it?” It should be recognized that in other examples, the second message can include a different request related to the media object. In particular, the second message can include a request for clarification of the user&#39;s intent with respect to the media object. The request can thus prompt the user to more fully define the user&#39;s intent for providing the media object. Second message can be generated and displayed by the digital assistant in response to the media object of block  1104 . Block  1108  can be performed after displaying the media object as the first message at block  1106  and before receiving the second user input at block  1110 . In some examples, block  1108  can be optional. 
     At block  1110 , a second user input including text can be received. In some examples, the text of the second user input can be received via a keyboard of GUI  1202  (e.g., keyboard  911 .) In some examples, the text can be responsive to the request of block  1108  in the second message. In some examples, the text can represent a request to perform a task using the media object. In other examples, the text can represent a request to obtain information related to the media object. In the present example shown in  FIG. 12D , the text can be “Add to contacts.” 
     At block  1112 , the text of block  1110  can be displayed as a third message in the GUI. For example, as shown in  FIG. 12D , the text “Add to contacts” can be displayed as third message  1208  in GUI  1202 . Block  1112  can be performed in response to receiving the second user input at block  1110 . As evident in the present example, neither the media object of block  1104  nor the text of block  1110  are individually sufficient to represent a user request. Specifically, neither contains sufficient information to deduce a user intent. However, the combination of the media object of block  1104  and the text of block  1110  can represent a user request to the digital assistant. 
     At block  1114 , the electronic device can cause a user intent (e.g., an actionable intent) corresponding to the first user input of block  1104  and the second user input of block  1110  to be determined. Block  1114  can include causing a domain among a plurality of domains in an ontology (e.g., ontology  760 ) to be determined based on the first user input and the second user input. The user intent can be determined using natural language processes (e.g., with natural language processing module  732 ) based on the first user input and the second user input. In some examples, the user intent can be determined at the electronic device. Alternatively, the electronic device can transmit the media object of block  1104  and the text of block  1110  to a remote server (e.g., DA server  106 ) where the user intent is determined based on the media object of block  1104  and the text of block  1110 . In the present example, it can be determined that the “contacts” domain corresponds to the first user input and the second user input. Further, it can be determined that the user intent includes creating and storing a new contact entry in the contacts application of the electronic device based on the media object. 
     At block  1116 , a determination of whether the user intent requires extracting text from the media object can be obtained. In some examples, the determination can be based on the user intent determined at block  1114 . In particular, certain domains can be predetermined to require extracting text from the media object. For example, domains including contacts, calendar, reminders, and translation can be predetermined to require extracting text from the media object. In response to obtaining a determination that the user intent requires extracting text from the media object, block  1118  can be performed. 
     At block  1118 , text from the media object can be extracted. Various techniques can be implemented to extract text from the media object. In examples where the media object is an image, optical character recognition can be performed on the image to extract text from the image. In examples where the media object is an audio clip or a video clip, speech to text recognition can be performed (e.g., using STT processing module  730 ) on the media object to extract text. Further, in examples where metadata is embedded in the media object, the media object can be processed to extract text from the metadata. In the present example, optical character recognition can be performed on the media object of message  1204  to extract the text depicted in the image of a business card. The extracted text can thus include contact information. 
     At block  1120 , a task in accordance with the user intent can be performed using the extracted text. In particular, a task flow corresponding to the user intent of block  1114  can be determined. Block  1120  can thus include performing the tasks of the task flow to at least partially fulfill the user intent of block  1114 . In the present example, a performed task can include determining contacts fields corresponding to one or more character strings of the extracted text. For example, the character strings “Joe,” “Black,” “joeblack@email.com,” and “555.123.4567” of the extracted text can be determined to correspond to the first name contacts field, the last name contacts field, the email contacts field, and the phone number contacts field, respectively. Further, block  1120  can include populating, in accordance with the user intent, the extracted text into a text field of an application of the electronic device. Specifically, in the present example, a new contact entry can be created in the contacts application. The contact entry can be associated with the individual “Joe Black.” Further, the character strings “Joe,” “Black,” “joeblack@email.com,” and “555.123.4567” of the extracted text can be populated into the first name field, the last name field, the email field, and the phone number field of the new contact entry, respectively. In other examples, it can be determined that an existing contact in the contact application is associated with the extracted text (e.g., same name, email, phone number, or the like). In these examples, the existing contact can be edited and additional information based on the extract text can be populated into one or more text fields of the existing contact. Block  1120  can be performed automatically without additional user intervention in response to receiving the first user input of block  1104  and the second user input at block  1110 . 
     At block  1122 , a response indicative of the user intent being satisfied can be displayed as a fourth message in the GUI. For example, as shown in  FIG. 12E , the response “Joe Black has been added to your contacts” is displayed as fourth message  1209 . The response can confirm that the user request represented by the first user input and the second user input has been performed. Further, in this example, the name “Joe Black” can be highlighted (e.g., underlined) to indicate to the user that the words “Joe Black” in message  1209  are selectable. In particular, message  1209  can be configured such that the user selection of the words “Joe Back” can cause the newly created/edited contact entry of Joe Black to be displayed in the contacts application of the electronic device. 
     In some examples, the response of block  1122  can include information requested by the user. For example, the task of block  1120  can include retrieving information in accordance with the user intent, and the retrieved information can be displayed in the response of the fourth message. In some examples, the response can include a request from the digital assistant for additional information. For example, the response can include a request for information to clarify the user&#39;s intent. In particular, the request can be a request to disambiguate an ambiguous term in the text of the second user input. In some examples, the response can request confirmation from the user prior to performing the task of block  1120 . 
     Although blocks  1102 - 1122  of process  1100  are explained above with respect to using an image depicting contact information to create a new contact entry in the contacts application of the electronic device, it should be recognized that blocks  1102 - 1122  can include various other implementations. For example, a calendar entry in the calendar application of the electronic device can be created based on the first user input of block  1104  and the second user input of block  1110 . In these examples, the media object of the first user input (e.g., block  1104 ) can include information about an event (e.g., an opera, concert, festival, examination, etc.). For example, the media object can be a picture of a pamphlet advertising the event. The picture can be captured using the electronic device and can depicting event information in text form. The event information can include, for example, a date, time, venue, and title for the event. The text of the second user input (e.g., block  1110 ) can include a request to create a calendar event using the media object. For example, the text of the second user input can be “Add to calendar.” Based on the text and media object, the user intent can be determined at block  1114  to include creating a calendar entry in a calendar application of the electronic device using the media object. In examples where the media object is an image, text depicted in the image can be extracted using optical character recognition. The extracted text can be processed to identify one or more character strings associated with a text calendar field (e.g., start time, end time, title, location, event description, etc.) The task performed at block  1120  in accordance with the user intent can include creating a new calendar entry and populating one or more text fields of the calendar entry with the extracted text. 
     In some examples, a reminder event in the reminder application of the electronic device can be created based on the first user input of block  1104  and the second user input of block  1110 . In these examples, the media object of the first user input can include information regarding a reminder task. For example, the media object can be a picture of a grocery store advertisement indicating that watermelon is on sale for 29 cents a pound. The picture can be taken using the electronic device. The text of the second user input can include a request to create a task reminder using the media object. For example, the text of the second user input can be “Create a reminder” or “Add to grocery list.” Based on the media object and the text, the user intent can be determined at block  1114  to include creating a reminder entry in a reminder application of the electronic device using the media object. In examples where the media object is an image, text depicted in the image can be extracted using optical character recognition. The extracted text can be processed to identify one or more character strings associated with a respective text reminder field (e.g., task title, task description, task category, reminder trigger criterion, etc.). For example, the extracted text from the grocery store advertisement can include the character strings “whole seedless watermelon for 29 cents/lb,” which is determined to be associated with the text reminder fields “task title” or “task description.” Further, it can be determined based on the word “watermelon” that the task is associated with the predefined task category of “Grocery List,” which can be associated with the reminder trigger criterion of being located within a predetermined distance of a grocery store. The task performed at block  1120  in accordance with the user intent can include creating a new task reminder and populating one or more text fields of the reminder entry with the extracted text. For example, the new task reminder can be for buying watermelon at the grocery store where a reminder is provided when the electronic device is within a predetermine distance of a grocery store. 
     In some examples, text extracted from a media object can be translated based on the first user input of block  1104  and the second user input of block  1110 . In these examples, the media object can contain a first language in text or spoken form. For example, the media object can be a picture of a traffic sign depicting the French text “arrêt.” The text of the second user input can include a request to translate the media object into a second language. For example, the text of the second user input can be “Translate into English.” Based on the media object and the text, the user intent can be determined at block  1114  to include translating a first language in the media object to a second language. In examples where the media object is an image, text depicted in the image can be extracted using optical character recognition. During text extraction, the language of the text can be determined. For example, it can be determined in the present example that the extracted text is French. The task performed at block  1120  in accordance with the user intent can include obtaining the text of the second language corresponding to the text of the first language. For example, the extract French text “arra” can be translated into the corresponding English text “stop.” The translation can be performed on the electronic device or the French text can be transmitted to a separate device to perform the translation. The displayed response of block  1122  can include the text of the second language. For example, the displayed response can be “It says ‘stop.’” 
     Although in the examples described above, the media object is an image, it should be recognized that in other examples, the media object can be an audio/video clip. In particular, the audio/video file can include an utterance. In these examples, extracting text from the media object at block  1118  can include performing speech to text recognition on the media object to extract a text representation of the utterance. Further, it should be recognized that the examples described above of creating a contact entry, a calendar entry, a reminder entry, or performing a translation can be similarly performed using an audio/video clip instead of an image. 
     With reference back to block  1116 , in response to obtaining a determination that the user intent does not require extracting text from the media object, block  1124  shown in  FIG. 11C  can be performed. At block  1124 , a determination can be obtained as to whether the user intent requires performing image recognition on the media object. In some examples, the determination can be based on the user intent determined at block  1114  and the type of media object received at block  1104 . For example, if the domain is determined to be the “search” domain and the media object is determined to be an image, then it can be determined that the user intent requires performing image recognition on the media object. 
     In an example illustrated in  FIG. 12F , the media object displayed in message  1210  (e.g., at block  1106 ) can be an image of a retail object. In the present example, the retail object is a specific car (e.g., the 2015 Volkswagen Beetle). The text of the second user input displayed in message  1212  (e.g., at block  1112 ) can be a request to search for the price of the car depicted in the media object (e.g., “How much does this cost?”). Based on the image and the text, it can be determined at block  1114  that the user intent includes performing image recognition on the image to identify the retail object and then performing a price search of the identified retail object. In this example, a determination can be obtained at block  1124  that the user intent requires performing image recognition on the media object. In response to obtaining a determination that the user intent requires performing image recognition on the media object, block  1126  can be performed. 
     At block  1126 , the electronic device can cause image recognition to be performed on the media object. In some examples, the media object can be transmitted to a separate server to perform the image recognition. In other examples, at least a portion of the image recognition can be performed on the electronic device. Image recognition can include extracting a set of representative image characteristics from the media object and then comparing the set of representative image characteristics to a plurality of sets of reference characteristics stored in a database to determine a best match. Each set of reference characteristics can be associated with reference information. The reference information can include information identifying the reference image corresponding to the respective set of reference characteristics. The image recognition results can be based on the reference information of the best matched set of reference characteristics. For example, the set of representative image characteristics of the media object in message  1210  can be found to best match a set of reference characteristics corresponding to a reference image of the 2015 Volkswagen Beetle. In particular, the image recognition results can include the character strings “2015,” “Volkswagen,” and “Beetle” based on the reference information associated with the best matched set of reference characteristics. 
     At block  1128 , information associated with the media object can be obtained based on the image recognition. In particular, the information can be obtained in accordance with the user intent of block  1114  and using the image recognition results of block  1126 . In the present example, based on the user intent of searching for the price of the retail object depicted in the media object, a price search using the image recognition results “2015 Volkswagen Beetle” can be performed. The obtained information can include price information of the retail object. For example, the obtained information can include the manufacturer&#39;s suggested retail price (MSRP) of the 2015 Volkswagen Beetle. In other examples, the obtained information can include the image recognition results. 
     At block  1130 , a response indicative of the user intent being satisfied can be displaying as a fifth message in the GUI. The response can be based on the information associated with the media object. Block  1130  can be similar to block  1122 . In the present example shown in  FIG. 12F , the response can be displayed as message  1213  and can include MSRP information of the 2015 Volkswagen Beetle to satisfy the user intent. 
     Although blocks  1124 - 1130  of process  1100  are explained above with respect to searching for price information of a retail object depicted in the media object, it should be recognized that blocks  1124 - 1130  can include various other implementations. For example, location or entity information associated with the media object can be obtained with blocks  1124 - 1130 . For example, the media object of block  1104  can be an image depicting the characteristics of a location (e.g., a map, a landmark, a flag, etc.). Alternatively, the media object can be an image depicting characteristics of an entity (e.g., a person, organism, thing, building, business, etc.). In these examples, the text at block  1110  can represent a request for information identifying the location or entity. For example, the text can be “Where is this place?” “What insect is this?” or “Which company uses this logo?” Based on the media object and the text, the user intent can be determined at block  1114  to include performing image recognition on the media object to obtain a recognition result and obtaining the identity of the location or entity represented in the media object. Based on the image recognition performed at block  1126 , information associated with the media object can be obtained at block  1128 . In these examples, the obtained information can include the identity of the location or entity represented in the media object. Further, the fifth message displayed at block  1130  can include the identity of the location or entity represented in the media object (e.g., “This is the country Algeria,” “This is the Golden Gate Bridge,” “This is an earwig,” etc.). 
     With reference back to block  1124 , in response to obtaining a determination that the user intent does not require performing image recognition on the media object, block  1132  of  FIG. 11D  can be performed. At block  1132 , a determination can be obtained as to whether the user intent requires performing audio processing on the media object. In some examples, the determination can be based on the user intent determined at block  1114  and the type of media object received at block  1104 . For example, if the domain is determined to be the “search” domain or the “music” domain and the media object is determined to be an audio file, then it can be determined that the user intent requires performing image recognition on the media object. In response to obtaining a determination that the user intent requires performing audio processing on the media object, block  1134  can be performed. 
     In the example illustrated in  FIG. 12G , the media object displayed in message  1214  (e.g., at block  1106 ) can be an audio clip of a media item (e.g., a song, movie, soundtrack, etc.). In the present example, the audio clip can be a sung portion of the United States national anthem. The text of the second user input displayed in message  1216  (e.g., at block  1112 ) can be a request to perform a search based on the song corresponding to the audio clip (e.g., “What&#39;s this song?”, “Who sang this?”, “When was this song released?”, etc.). Based on the audio clip and the text, it can be determined at block  1114  that the user intent includes performing audio recognition on the media item to identify the song in the audio clip. In this example, a determination can be obtained at block  1132  that the user intent requires performing audio processing (e.g., audio recognition) on the media object. In response to obtaining a determination that the user intent requires performing audio processing on the media object, block  1134  can be performed. 
     At block  1134 , the electronic device can cause audio processing to be performed on the media object to be performed. In some examples, audio processing can include audio recognition (e.g., speaker recognition, music recognition, sound recognition, etc.). In some examples, the media object can be transmitted to a separate server to perform the audio recognition. In other examples, at least a portion of the audio recognition can be performed on the electronic device. Audio recognition can include extracting a sound print from the media object. The sound print can then be compared against a plurality of reference sound prints in a database to obtain a best matched reference sound print. Each reference sound print can be associated with reference information. The audio recognition results can be based on the reference information of the best matching reference sound print. In the present example, the best matched reference sound print can be associated with the United States national anthem. The audio recognition results can thus include reference information identifying the media object. For example, the reference information can include “Star Spangled Banner” or “United States national anthem.” 
     At block  1136 , information associated with the media object can be obtained based on the audio processing of block  1134 . In the present example, the obtained information can include the audio recognition results (e.g., United States national anthem). In other examples, information related to the audio recognition results can be obtained. For example, a search can be performed using the text information identifying the media object of block  1134  to obtain additional information to satisfy the user intent. In particular, additional information about the identified song, such as the artist, composer, release date, album name, album price, and the like, can be obtained. 
     At block  1138 , a response based on the information associated with the media object can be displayed as a sixth message in the GUI. The response can be indicative of the user intent being satisfied. Block  1138  can be similar to block  1122 . In the present example shown in  FIG. 12G , the response can be displayed as message  1218  and can identify the song in the media object as being “the United States national anthem.” In some examples, the sixth message (e.g., message  1218 ) can be configured to be selectable by the user such that in response to detecting a user selection of the sixth message, the electronic device can cause additional information related to the media object (e.g., retail information) to be displayed. In particular, in response to detecting a user selection of the sixth message, a music search application (e.g., iTunes application) of the electronic device can be caused to search for media items (e.g., songs, albums, movies, games, etc.) corresponding to the identified media object and to displayed these media items for the user to browse or purchase. 
     It should be recognized that in some examples, the audio processing of block  1134  can include speech-to-text recognition. For example, speech-to-text recognition can be performed on speech in the media object to obtain text corresponding to the speech. In some examples, the information obtained at block  1136  can be based on the text corresponding to the speech in the media object. For example, a search can be performed using one or more words in the text corresponding to the speech in the media object in accordance with the user intent of block  1114 . In other examples, the user may wish to store a transcription of the speech in the media object for future reference. In these examples, the text corresponding to the speech in the media object can be stored in association with an application (e.g., document manager application or a word processing application) of the electronic device in accordance with the user intent. 
     With reference back to block  1132 , in response to obtaining a determination that the user intent does not require performing audio processing on the media object, block  1140  can be performed. At block  1140 , the electronic device can cause an action to be performed in accordance with the user intent of block  1114 . At block  1142 , a response based on the action performed at block  1140  can be displayed as the seventh message in the GUI. 
     In some examples, process  1100  can be implemented to identify and store pertinent information for future retrieval. In these examples, the text of block  1110  can define an attribute related to the media object of block  1104 . The attribute may not be explicitly indicated in the media object. For example, the media object can represent an entity and the attribute defined by the text of block  1110  can be a characteristic of the entity. In some examples, the attribute defined by the text of block  1110  can describe a relationship between the user and the contents of the media object. For example, as shown in  FIG. 12H , the media object of block  1106  can be a picture of a bottle of wine (e.g., displayed as message  1220 ) and the text of block  1110  (e.g., displayed as message  1222 ) can define the user&#39;s opinion or preference for the wine (e.g., “I like this wine” or “This wine has vivid flavors of ground spice with hints of raspberry fruit and lemon zest”). In another example, the media object can be a picture of the parking space number at which the user parked his or her car and the text of block  1110  can indicate that the user parked at the location associated with the contents of the media object (e.g., “I parked here.”). In the examples described above, it can be determined that the user intent is to store data that associated the defined attribute to the media object for future retrieval. Based on this user intent, it can be determined at block  1132  that the user intent does not require performing audio processing on the media object. In response to obtaining a determination that the user intent does not require performing audio processing on the media object, the electronic device can cause an action to be performed at block  1140  in accordance with the user intent of block  1114 . 
     In these examples, the action of block  1140  can include storing data associating the attribute defined in the text of block  1110  to the media object of block  1104 . In particular, the data can indicate that the attribute is a characteristic of the media object. For instance, in the example shown in  FIG. 12H , the picture of the wine bottle in message  1220  can be stored (e.g., on the electronic device or on a remote device) in connection with a first attribute indicating that the picture is that of a bottle of wine and a second attribute indicating that the user likes the wine depicted in the picture. 
     In some examples, the data and/or the media object can be stored in association with an application of the electronic device. For example, the media object of block  1104  can be a picture of a person and the text of block  1110  can define the name of the person (e.g., “This is John Woo.”) In this example, the picture of the person can be stored in association with the contacts application of the electronic device. If an existing contact entry is associated with the defined name, the picture can be auto-populated into the existing contact entry. If no existing contact entry is associated with the defined name, a new contact entry can be created. The picture and the defined name can then be auto-populated in the new contact entry. The contact entry thus associates the defined name with the picture. 
     In the present example shown in  FIG. 12H , the response of block  1142  can be displayed as message  1224  and can confirm that the defined attribute is stored in association with the media object. Storing media items in association with user defined attributes can be desirable to help the user store and organize information deemed relevant to the user. For example, the user may ask the digital assistant to recommend a good wine in the future. The digital assistant can then refer back to the media object of message  1224  based on the stored attributes of “wine” and “like” associated with the media object and display the media object as a wine recommendation. 
     Process  1300  is described below with simultaneous reference to  FIGS. 13A-C  and  14 A-I. At block  1302 , a graphical user interface (GUI) having a plurality of previous messages between a user of the electronic device and a user of a remote device can be displayed on the display of an electronic device. For example, as shown in  FIG. 14A , GUI  1402  of electronic device  1400  can be displayed. GUI  1402  can be a GUI of a messaging application of electronic device  1400 . As shown, GUI  1402  can include plurality of previous messages  1403  between the user of electronic device  1400  and a user of a remote device (not shown). For example, previous message  1404  can be generated from user input via GUI  1402  of electronic device  1400  and addressed to the user of the remote device. Previous message  1406  can be sent from the remote device and addressed to the user of electronic device  1400  in response to previous message  1404 . Plurality of previous messages  1403  are presented in a conversational view. Electronic device  1400  can be similar to one or more of devices  104 ,  200 ,  400 ,  600 ,  900 , or  1100 . Electronic device  1400  and the remote device can be different devices. Block  1302  can be similar to block  802  of process  800 , except that the plurality of previous messages are between two users of different devices rather than between the user of the electronic device and the digital assistant implemented on the electronic device. In particular, similar to plurality of previous message  903  of block  802 , plurality of previous message  1403  of block  1302  can each be associated with a previous contextual state of electronic device  1400  at the time the respective previous message was generated. 
     At block  1304 , a first user input addressed to the digital assistant can be received. The first user input can be similar to the user input of block  806 . In particular, the first user input can be received from the user of the electronic device. The first user input can represent a user request and can include text input and/or a media object. The first user input can be received via a user input interface (e.g., user input interface  910 ) of electronic device  1400 . Text input of the first user input can be in natural language form. Further, in some examples, the first user input can include a predetermined trigger phrase associated with the digital assistant of electronic device  1400 . The predetermined trigger phrase can indicate that the first user input is addressed to the digital assistant. In the present example shown in  FIG. 14B , the first user input includes the text “Hey Siri, any Chinese restaurants nearby?” In this example, the predetermined trigger phrase can be “Hey Ski.” 
     At block  1306 , the first user input can be displayed as a first message in the GUI. For example, with reference to  FIG. 14B , the first user input can be displayed as first message  1408  in GUI  1402 . Block  1306  can be performed in response to receiving the first user input at block  1304 . In some examples, the first user input and first message  1408  can be associated with a contextual state of electronic device  1400 . The contextual state can be similar to the contextual state of block  810  and can include the state of the electronic device at the time first user input was received or at the time first message  1408  was generated. In some examples, the contextual state can be stored in association with first message  1408  in response to receiving the first user input at block  1304 . 
     At block  1308 , a determination can be made as to whether the first user input includes a predetermined trigger phrase to invoke the digital assistant. In some examples, the determination can be made by electronic device  1400 . In other examples, the determination can be obtained from a remote server (e.g., DA server  106 ). Block  1308  can include parsing the first user input of first message  1408  to identify any word or sequence of words corresponding to a predetermined trigger phrase. In response to determining that the first user input includes a predetermined trigger phrase, the digital assistant can be invoked and first message  1408  can be processed but the digital assistant. In particular, block  1310  can be performed in response to determining that the first user input includes a predetermined trigger phrase. In response to determining that the first user input does not include a predetermined trigger phrase, the digital assistant is not invoked and no further action is taken by the electronic device. 
     It should be recognized that in some examples, the digital assistant may still be invoked without a predetermined trigger phrase in the first user input. In these examples, the messages of GUI  1402  can be continuously processed by the digital assistant to determine whether a message from the user is intended to be addressed to the digital assistant or whether any action associated with a message can be taken by the digital assistant to assist the user. In particular, natural language processing can be performed on the first user input to attempt to determine an actionable intent. If an actionable intent can be determined from the first user input, then block  1310  can be performed. If an actionable intent cannot be determined from the first user input, then no action would be taken by the digital assistant. In the present example, the actionable intent of searching for a Chinese restaurant can be determined from first message  1408  and thus block  1310  can be performed. 
     At block  1310 , the electronic device can cause an action to be performed in accordance with a user intent derived from the first user input. Block  1310  can include causing the user intent (e.g., actionable intent) to be determined (e.g., using natural language processing module  732 ) based on the first user input of block  1304  and causing a task flow corresponding to the user intent to be generated (e.g., using task flow processing module  736 ). Block  1310  can further include causing the task flow to be executed to perform the action in accordance with the user input. In some examples, performing the action can at least partially satisfy the derived user intent. In particular, results that at least partially satisfy the derived user intent can be obtained by performing the action. 
     In some examples, receiving the user input at block  1304  (or displaying the first message at block  1306 ) can cause the electronic device to determine the user intent, generate the task flow, and the action. Alternatively, the electronic device can transmit a representation of the first user input to a digital assistant server (e.g., DA server  106 ) and cause the digital assistant server to determine the user intent, generate the task flow, and perform the action. 
     In some examples, the contextual state of the electronic device associated with first message  1408  can be utilized to determine the user intent and thus the response displayed at block  1312  can be based on the stored contextual state. For example, location information stored in association with first message  1408  can indicate that the electronic device was located near Union Square in San Francisco at the time the first user input was received. Based on this location information, it can be determined that “nearby” in the first user input refers to near Union Square in San Francisco. Thus, in this example, the user intent corresponding to the first user input can be determined to be a search for Chinese restaurants near Union Square in San Francisco. The action caused to be performed in accordance with this user intent can be obtaining search results for Chinese restaurants near Union Square in San Francisco. 
     At block  1312 , a response based on the action of block  1310  can be displayed as a second message in the GUI. For example, as shown in  FIG. 14C , second message  1410  can be displayed in GUI  1402 . Second message  1410  can include a response based on the search results obtained at block  1310 . In particular, second message  1410  can include or provide access to the search results of Chinese restaurants located near Union Square in San Francisco. The response can be in natural language form and can at least partially satisfy the user request represented by the first user input of block  1304 . In the present example, second message  1410  can be configured to provide additional details in accordance with the user input in response to a user selection of second message  1410 . In particular, selection of second message  1410  by the user of electronic device  1400  can cause an application of electronic device  1400  to display detailed search results of Chinese restaurants near Union Square in San Francisco. 
     In some examples, block  1312  can further include transmitting the response (or causing the response to be transmitted) to the remote device and causing display of the response in a GUI of the remote device. Thus, electronic device  1400  can cause messages  1408  and  1410  to be displayed in the GUI of the remote device. Further message  1410  displayed in the GUI of the remote device can be configured to cause detailed search results to be displayed on the remote device in response to user selection of the message. In this way, the user of the remote device can view the conversation between the user of electronic device  1400  and the digital assistant of electronic device  1400 . As described below, this will enable the user of the remote device to also participate in the conversation and thus benefit the assistance provided by the digital assistant of electronic device  1400 . Blocks  1310  and  1312  can be performed automatically without additional human intervention in response to receiving the first user input of block  1304  (or in response to displaying the first user input as message  1408  at block  1306 ). 
     At block  1314 , a second user input addressed to the digital assistant of electronic device  1400  can be received from the user of the remote device via the remote device. The second user input can include text input and/or a media object. In some examples, the second user input can be related to the first user input. In the present example shown in  FIG. 14D , the second user input can include the text “How about just the cheap ones?” 
     At block  1316 , the second user input can be displayed as a third message in the GUI. For example, as shown in  FIG. 14D , the second user input can be displayed as third message  1412  in GUI  1402 . Block  1316  can be performed in response to receiving the second user input. 
     At block  1318 , the electronic device can cause a second action to be performed in accordance with a second user intent derived from the second user input and the user intent of block  1310 . Block  1318  can be similar to block  1310  except that the second user input is derived from both the second user input and the user intent of block  1308 . In particular, the electronic device can cause the second user intent to be initially determined based on the second user input. In particular, a determination can be made as to whether the second user input is a request to refine the user intent of block  1308 . The determination can be based on one or more predetermined words in the second user input. In the present example, it can be determined based on the word “just” in the second user input that the second user input is a request to refine the user intent of block  1308 . Other predetermined words can include “only,” “filter,” “narrow,” and the like. Additionally or alternatively, the determination of whether the second user input is a request to refine the user intent of block  1308  can be based on the domain corresponding to the second user input. For example, if the domain corresponding to the second user input is the same as the domain corresponding to the first user input, then the second user input can be determined to be a request to refine the user intent of block  1308 . 
     In response to determining that the second user input is a request to refine the user intent of block  1308 , the second user intent can be determined based on the second user input and the user intent of block  1308 . In the present example, the second user intent can be determined to include obtaining search results for Chinese restaurants near Union Square that are rated the least expensive. The second action in accordance with the second user intent can thus be performing a search for Chinese restaurants that are rated the least expensive. It should be appreciated that in the present example, the first user intent and the second user intent can correspond to the same domain of an ontology (e.g., the “search restaurant” domain). Further, the second user intent can include a parameter (e.g., rated the least expensive) that is not included in the user intent of block  1310 . 
     At block  1320 , a second response based on the second action can be displayed as a fourth message in the GUI. In the present example as shown in  FIG. 14E , message  1414  is displayed in GUI  1402 . Message  1414  can include a second response based on the second action of block  1318 . Block  1320  can be similar to block  1314 . In this example, the second response can present search results of Chinese restaurants near Union Square in San Francisco that are rated least expensive. 
     In some examples, block  1320  can include transmitting the second response to the remote device and causing display of the second response in the GUI of the remote device. In this way, the results requested by the user of the remote device can be made accessible to the user of the remote device. The user of the remote device can thus become a participant of the conversation between the user of electronic device  1400  and the digital assistant of electronic device  1400 . 
     In some examples, the digital assistant of the remote device can interact with the user of electronic device  1400  and/or with the digital assistant of the electronic device  1400  in the messaging environment. Blocks  1322 - 1328  of process  1300  and  FIGS. 14F-I  illustrate examples of such interactions. In the examples described below, the digital assistant of the remote device can be utilized to send the user of electronic device  1400  a reminder. In particular, as indicated in message  1416  of  FIG. 14F , the user of the remote device can have the digital assistant of the remote device send a reminder to the user of electronic device  1400  thirty minutes prior to their 7:00 pm dinner appointment. Further, the user of the remote device can have the digital assistant of the remote device request that the user of electronic device  1400  call the user of the remote device upon arrival at the dinner location (e.g., Panda Express). 
     At block  1322 , input from the digital assistant of the remote device can be received. The input can be generated automatically (e.g., in response to the time being 6:30 pm) by the digital assistant of the remote device and can include text input and/or a media object. In the present example shown in  FIGS. 14G-H , the input can be received at 6:30 pm and can include text reminding the user of electronic device  1400  about the 7:00 pm dinner appointment at Panda Express. The input can further include text requesting the user of electronic device  1400  to call the user of the remote device upon arriving at the dinner venue (e.g., Panda Express). In response to receiving the input, block  1324  can be performed. 
     At block  1324 , a fifth message based on the input of block  1322  can be displayed in the GUI. In some examples, the input from the digital assistant of the remote device can be directly displayed as the fifth message in the GUI. For example, as shown in  FIG. 14G , fifth message  1418  displayed in GUI  1402  can include text of the input generated by the digital assistant of the remote device. Fifth message  1418  is thus directly addressed to the user of electronic device  1400  from the digital assistant of the remote device. Further, in some examples, indication  1417  that the content of fifth message  1418  was generated by the digital assistant of the remote device can be displayed. In this example, indication  1417  is text indicating that fifth message  1418  was created and sent by the digital assistant of the remote device. 
     In other examples, the input of block  1322  can be processed by the digital assistant of electronic device  1400  and a representation of the input can be generated and displayed as the fifth message in the GUI. For example, as shown in  FIG. 14H , fifth message  1420  displayed in GUI  1402  can convey the information represented by the input of block  1322 . In particular, receiving the input from the digital assistant of the remote device at block  1322  can cause the digital assistant of electronic device  1400  to generate and display fifth message  1420 . The content of fifth message  1420  can thus be generated by the digital assistant of electronic device  1400  based on the input of block  1322 . The input of block  1322  is thus conveyed indirectly to the user of electronic device  1400  through the digital assistant of electronic device  1400 . As shown in  FIG. 14H , indication  1419  that the content of the fifth message was generated by the digital assistant of electronic device  1400  can be displayed. In this example, indication  1419  is text indicating that fifth message  1420  was created and displayed by the digital assistant of electronic device  1400 . Although conveying the input of block  1322  indirectly to the user of electronic device  1400  through the digital assistant of electronic device  1400  can require additional processing by electronic device  1400 , it can improve user experience by reducing the number of participants in the conversation and thus reducing confusion. 
     In some examples, the input of block  1322  can cause the digital assistant of electronic device  1400  to perform an action. At block  1326 , in response to receiving the input of block  1322 , the electronic device can cause a third action to be performed in accordance with a third user intent derived from the input of block  1322 . Block  1326  can be similar to block  1310 . Block  1326  can include causing the third user intent corresponding to the input of block  1322  to be determined using natural language processing. More specifically, a determination can be made as to whether the input of block  1322  corresponds to an actionable intent. In the present example, the input of block  1322  can be determined to correspond to the actionable intent of creating a reminder. Specifically, the third user intent can include creating a reminder to call John Smith upon arriving at the location corresponding to Panda Express. Block  1326  can further include causing a third task flow corresponding to the third user intent to be generated and causing the task flow to be executed to perform the third action. In the present example, the third action can include creating a reminder to call John Smith upon arriving at location corresponding to Panda Express. The created reminder can be configured to cause a notification to be displayed on electronic device  1400  in response to detecting that electronic device  1400  is located within a predetermined distance of the location corresponding to Panda Express. 
     At block  1328 , a third response based on the third action can be displayed as a sixth message in the GUI. For example, as shown in  FIG. 14I , sixth message  1422  can be displayed in GUI  1402 . Sixth message  1422  can include a third responses confirming that the reminder has been created. Sixth message  1422  can be generated and displayed by the digital assistant of electronic device  1400 . In other examples, sixth message  1422  can include information obtained from performing the third action at block  1326 . 
     Although in the examples described above, the digital assistant of the electronic device is a participant in the conversation between the users of only two electronic devices, it should be recognized that in other examples, the conversation can include the users of any number of electronic devices. Further, the digital assistants of any one of the participating electronic devices can participate in the conversation. Moreover, it should be recognized that the aspects of operating a digital assistant in a messaging environment in processes  800  and  1100  can be applied during the multi-participant conversations between the users of different devices. 
     5. Electronic Devices 
       FIG. 15  shows a functional block diagram of electronic device  1500  configured in accordance with the principles of the various described examples. The functional blocks of the device can be optionally implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 15  can be optionally combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination, separation, or further definition of the functional blocks described herein. 
     As shown in  FIG. 15 , electronic device  1500  can include touch screen display unit  1502  configured to display a graphical user interface and to receive input from the user, audio input unit  1504  configured to receive audio input (e.g., speech input), and optionally, RF unit  1506  configured to transmit and receive information. Electronic device  1500  can further include processing unit  1508  coupled to touch screen display unit  1502 , audio input unit  1504 , and RF unit  1506 . In some examples, processing unit  1508  can include display enabling unit  1510 , receiving unit  1512 , storing unit  1514 , causing unit  1516 , detecting unit  1518 , sampling unit  1520 , outputting unit  1522 , identifying unit  1524 , determining unit  1526 , enabling unit  1528 , and obtaining unit  1530 . 
     In accordance with some embodiments, processing unit  1508  is configured to display (e.g., with display enabling unit  1510 ) on touch screen display unit  1502 , a graphical user interface (GUI) having a plurality of previous messages between a user of the electronic device and the digital assistant. The plurality of previous messages is presented in a conversational view. Processing unit  1508  is further configured to receive (e.g., with receiving unit  1512 ) user input via touch screen display unit  1502 . Processing unit  1508  is further configured to, in response to receiving the user input, display (e.g., with display enabling unit  1510  and on touch screen display unit  1510 ) the user input as a first message in the GUI. Processing unit  1508  is further configured to store (e.g., with storing unit  1514 ) a contextual state of the electronic device corresponding to the displayed user input. Processing unit  1508  is further configured to cause (e.g., with causing unit  1516 ) an action to be performed in accordance with a user intent derived from the user input. Processing unit  1508  is further configured to display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) a response as a second message in the GUI, the response based on the action. 
     In some examples, each of the plurality of previous messages are associated with a previous contextual state of the electronic device. 
     In some examples, processing unit  1508  is further configured to prior to displaying the user input, detect (e.g., with detecting unit  1518 ) a user selection of a first previous message of the plurality of previous messages, where the first previous message is associated with a first previous contextual state of the electronic device. Causing the action to be performed can further comprises obtaining results using the first previous contextual state of the electronic device, where the results are based on the user intent. 
     In some examples, processing unit  1508  is further configured to, prior to receiving the user input, detect (e.g., with detecting unit  1518 ) a second user input. In some examples, processing unit  1508  is further configured to, in response to detecting the second user input, sample (e.g., with sampling unit  1520 ) audio data (e.g., via audio input unit  1504 ). The audio data contains a user utterance. Processing unit  1508  is further configured to cause (e.g., with causing unit  1516 ) a second action to be performed in accordance with a second user intent derived from the user utterance. Processing unit  1508  is further configured to output (e.g., with outputting unit  1522 ) a second response based on the second action, where a second previous message of the plurality of previous messages includes a text representation of the user utterance, and where a third previous message of the plurality of previous messages is based on the second response. 
     In some examples, processing unit  1508  is further configured to receive (e.g., with receiving unit  1512  and via touch screen display unit) a third user input associated with a fourth previous message of the plurality of previous messages. Processing unit  1508  is further configured to, in response to receiving the third user input, store (e.g., with storing unit  1514 ) a bookmark of the fourth previous message in association with an affordance. Processing unit  1508  is further configured to display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) the affordance on the GUI, where selecting the affordance causes a focus of the GUI to change to the fourth previous message. 
     In some examples, processing unit  1508  is further configured to, in response to displaying the user input as a first message in the GUI of the electronic device, cause (e.g., with causing unit  1516 ) display of the first message in a GUI of a second electronic device. Processing unit  1508  is further configured to, in response to displaying the response as a second message in the GUI of the electronic device, cause (e.g., with causing unit  1516 ) display of the second message in the GUI of the second electronic device. 
     In some examples, processing unit  1508  is further configured to detect (e.g., with detecting unit  1518 ) a user selection of the first message in the GUI. The first message is generated from user input received at a separate electronic device. The first message is associated with a contextual state of the separate electronic device. Processing unit  1508  is further configured to receive (e.g., with receiving unit  1512  and via touch screen display unit  1502 ) a fourth user input. Processing unit  1508  is further configured to, in response to receiving the fourth user input, display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) the fourth user input as a third message in the GUI. Processing unit  1508  is further configured to cause (e.g., with causing unit  1516 ) a third action to be performed in accordance with a third user intent, the third user intent derived from the fourth user input and the contextual state of the separate electronic device. Processing unit  1508  is further configured to display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) a third response as a fourth message, the third response based on the third action. 
     In some examples, processing unit  1508  is further configured to identify (e.g., with identifying unit  1524 ), based on the contextual state of the electronic device and the derived user intent, one or more words in the displayed response corresponding to an entity. Processing unit  1508  is further configured to determine (e.g., with determining unit  1526 ) an action associated with the entity. Processing unit  1508  is further configured to enable (e.g., with enabling unit  1528 ) selection of one or more words in the displayed response, where detecting a user selection of the one or more words causes the action associated with the entity to be performed. 
     In some examples, the GUI of the electronic device includes a text input field. In these examples, processing unit  1508  is further configured to detect (e.g., with detecting unit  1518 ) a fifth user input associated with a first previous message of the plurality of previous messages. Processing unit  1508  is further configured to, in response to detecting the fifth user input, display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) text of the first previous message in the text input field of the GUI. 
     In some examples, processing unit  1508  is further configured to receive (e.g., with receiving unit  1512  and using touch screen display unit  1502 ), via the GUI of the electronic device, a user selection of the second message. Processing unit  1508  is further configured to, in response to receiving the user selection of the second message, obtain (e.g., with obtaining unit  1530 ), using an application of the electronic device, detailed results based on the user intent. Processing unit  1508  is further configured to display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) the detailed result in a GUI of the application. 
     In some examples, displaying the response as the second message includes displaying an indication in the second message that a more detailed response is available in response to selecting the second message. In some examples, the second message includes only text. 
     In some examples, processing unit  1508  is further configured to, display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ), based on the user intent, a media object in the GUI of the electronic device, the media object associated with an application of the electronic device. 
     In some examples, processing unit  1508  is further configured to detect (e.g., with detecting unit  1518 ) a user selection of the media object. In response to detecting the user selection of the media object, processing unit  1508  is further configured to obtain (e.g., with obtaining unit  1530 ), using an application of the electronic device, expanded results corresponding to the media object. Processing unit  1508  is further configured to display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) the expanded results in a GUI of the application. 
     In some examples, processing unit  1508  is further configured to receive (e.g., with receiving unit  1512  and via touch screen display unit  1502 ) a notification from an application of the electronic device. Processing unit  1508  is further configured to, in response to receiving the notification, display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) the notification as a fifth message in the GUI. 
     In some examples, the GUI of the electronic device includes a user input interface, where the displayed response includes a request for additional information. In these examples, processing unit  1508  is further configured to display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) two or more suggested character strings in the user input interface, each of the two or more suggested character string responsive to the request for additional information. Processing unit  1508  is further configured to detect (e.g., with detecting unit  1518 ) a user selection of a suggested character string of the two or more suggested character strings. Processing unit  1508  is further configured to, in response to detecting a user selection of a suggested character string, display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) the selected suggested character string as a sixth message in the GUI of the electronic device. Processing unit  1508  is further configured to display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) a fourth response as a seventh message in the GUI of the electronic device, the fourth response based on the selected suggested character strings. 
     In some examples, the user input includes an ambiguous term. The displayed response includes a displayed request for additional information related to the ambiguous term. The displayed request for additional information includes a list of possible interpretations for the ambiguous term. 
     In some examples, processing unit  1508  is further configured to receive (e.g., with receiving unit  1512 ) a sixth user input indicating a selection of one of the list of possible interpretations. Processing unit  1508  is further configured to, in response to receiving the sixth user input, display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) the sixth user input as an eighth message in the GUI. Processing unit  1508  is further configured to cause (e.g., with causing unit  1516 ) a sixth action to be performed in accordance with a user intent derived from the sixth user input. Processing unit  1508  is further configured to display (e.g., with display enabling unit  1510  and on touch screen display unit  1502 ) a sixth response as a ninth message in the GUI, the sixth response based on the sixth action. 
     In some examples, the contextual state includes a time the user input is received and data defining the location of the electronic device at the time the user input is received. 
     In some examples, the GUI of the electronic device is a GUI of a messaging application of the electronic device, the messaging application configured to send and receive messages from one or more recipients. In some examples, the plurality of previous messages are displayed in chronological order. In some examples, the first message and the second message are justified on opposite sides of the GUI. In some examples, the second message is displayed without providing any audio output. 
     In some examples, causing the action to be performed and displaying the response are performed automatically in response to receiving the user input and without additional human intervention. 
     In some examples, processing unit  1508  is further configured to cause (e.g., with causing unit  1516 ) the user intent to be determined based on the user input. Processing unit  1508  is further configured to cause (e.g., with causing unit  1516 ) a task flow to be determined based on the user intent. Processing unit  1508  is further configured to cause (e.g., with causing unit  1516 ) the task flow to executed to obtain results, where the displayed response is based on the obtained results. 
     The operations described above with reference to  FIG. 8  can be optionally implemented by components depicted in  FIGS. 1-4, 6A -B, and  7 A. For example, the operations of process  800  may be implemented by one or more of operating system  718 , applications module  724 , I/O processing module  728 , STT processing module  730 , natural language processing module  732 , task flow processing module  736 , service processing module  738 , or processor(s)  220 ,  410 ,  704 . It would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIGS. 1-4, 6A -B, and  7 A. 
       FIG. 16  shows a functional block diagram of electronic device  1600  configured in accordance with the principles of the various described examples. The functional blocks of the device can be optionally implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 16  can be optionally combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination, separation, or further definition of the functional blocks described herein. 
     As shown in  FIG. 16 , electronic device  1600  can include touch screen display unit  1602  configured to display a graphical user interface and to receive input from the user, audio input unit  1604  configured to receive audio input (e.g., speech input), and optionally, RF unit  1606  configured to transmit and receive information. Electronic device  1600  can further include processing unit  1608  coupled to touch screen display unit  1602 , audio input unit  1604 , and RF unit  1606 . In some examples, processing unit  1608  can include display enabling unit  1610 , receiving unit  1612 , causing unit  1614 , obtaining unit  1616 , extracting unit  1618 , performing unit  1620 , populating unit  1622 , and storing unit  1624 . 
     In accordance with some embodiments, processing unit  1608  is configured to displayed (e.g., with display enabling unit  1610 ), on the display unit  1602 , a graphical user interface (GUI) having a plurality of previous messages between a user and the digital assistant, the plurality of previous messages presented in a conversational view. Processing unit  1608  is further configured to receive (e.g., with receiving unit  1612 ) a first user input including a media object. Processing unit  1608  is further configured to, in response to receiving the first user input, display (e.g., with display enabling unit  1610  and on display unit  1602 ) the media object as a first message in the GUI. Processing unit  1608  is further configured to receive (e.g., with receiving unit  1612 ) a second user input including text. Processing unit  1608  is further configured to, in response to receiving the second user input, display (e.g., with display enabling unit  1610  and on display unit  1602 ) the text as a second message in the GUI. Processing unit  1608  is further configured to cause (e.g., with causing unit  1614 ) a user intent corresponding to the first user input and the second user input to be determined. Processing unit  1608  is further configured to obtain (e.g., with obtaining unit  1616 ) a determination of whether the user intent requires extracting text from the media object. Processing unit  1608  is further configured to, in response to obtaining a determination that the user intent requires extracting text from the media object: extract (e.g., with extracting unit  1618 ) text from the media object, perform (e.g., with performing unit  1620 ) a task in accordance with the user intent using the extracted text, and display (e.g., with display enabling unit  1610  and on display unit  1602 ), as a third message in the GUI, a response indicative of the user intent being satisfied. 
     In some examples, processing unit  1608  is further configured to, in accordance with the user intent, populate (e.g., with populating unit  1622 ) the extracted text into a text field of an application of the electronic device. 
     In some examples, the user intent comprises creating, using the media object, a contact entry in a contacts application of the electronic device. In these examples, the media object is an image depicting contact information of an entity, the extracted text includes the contact information, and performing the task in accordance with the user intent further comprises populating a text field of the contact entry with the extracted text, the contact entry associated with the entity. 
     In some examples, the user intent comprises creating, using the media object, a calendar entry in a calendar application of the electronic device. In these examples, the media object is an image depicting event information, the extracted text includes the event information, and performing the task in accordance with the user intent further comprises populating a text field of the calendar entry with the extracted text. 
     In some examples, the user intent comprises creating, using the media object, a reminder entry in a reminder application of the electronic device. In these examples, the media object is an image depicting a reminder task, the extracted text includes the reminder task, and performing the task in accordance with the user intent further comprises populating a text field of the reminder entry with the extracted text. 
     In some examples, the user intent comprises translating text of a first language in the media object to text of a second language. In these examples, the media object is an image depicting the text of the first language, the extracted text includes the text of the first language, performing the task in accordance with the user intent further comprises obtaining the text of the second language corresponding to the text of the first language, and the displayed response includes the text of the second language. 
     In some examples, processing unit  1608  is further configured to, in response to obtaining a determination that the user intent does not require extracting text from the media object, obtain (e.g., with obtaining unit  1616 ) a determination of whether the user intent requires performing image recognition on the media object. Processing unit  1608  is further configured to, in response to obtaining a determination that the user intent requires performing image recognition on the media object: cause (e.g., with causing unit  1614 ) image recognition on the media object to be performed, obtain (e.g., with obtaining unit  1616 ), based on the image recognition, information associated with the media object, and display (e.g., with display enabling unit  1610  and on display unit  1602 ), as a fourth message in the GUI, a response indicative of the user intent being satisfied. The response is based on the information associated with the media object. 
     In some examples, the media object depicts a retail object, and the information associated with the media object includes price information of the retail object. In some examples, the media object depicts a location, and the information associated with the media object includes the identity of the location. In some examples, the media object depicts an entity, and the information associated with the media object includes the identity of the entity. 
     In some examples, processing unit  1608  is further configured to in response to obtaining a determination that the user intent does not require performing image recognition on the media object, obtain (e.g., with obtaining unit  1616 ) a determination of whether the user intent requires performing audio processing on the media object. Processing unit  1608  is further configured to, in response to obtaining a determination that the user intent requires performing audio processing on the media object: cause (e.g., with causing unit  1614 ) audio processing on the media object to be performed, obtain (e.g., with obtaining unit  1616 ), based on the audio processing, information associated with the media object, and display (e.g., with displaying enabling unit  1610  and on display unit  1602 ), as a fifth message in the GUI, a response indicative of the user intent being satisfied. The response is based on the information associated with the media object. 
     In some examples, causing audio processing on the media object to be performed further comprises causing speech-to-text recognition to be performed on the media object to obtain text corresponding to speech in the media object. In some examples, the information is obtained using the text corresponding to the speech in the media object. In some examples, the text corresponding to the speech in the media object is stored in association with an application of the electronic device in accordance with the user intent. 
     In some examples, causing audio processing on the media object to be performed further comprises causing audio recognition to be performed using the media object to obtain text identifying the media object. In some examples, the information is obtained using the text identifying the media object. In some examples, processing unit  1608  is further configured to, in response to detecting a user selection of the fifth message in the GUI, cause (e.g., with causing unit  1614 ) retail information related to the media object to be displayed. 
     In some examples, the second user input defines an attribute related to the media object, the attribute not explicitly indicated in the media object. In these examples, processing unit  1608  is further configured to, in response to obtaining a determination that the user intent does not require performing audio processing on the media object, store (e.g., with storing unit  1624 ) data that associates the attribute to the media object. 
     In some examples, the attribute describes a relationship between the user and the media object. In some examples, processing unit  1608  is further configured to store (e.g., with storing unit  1624 ), based on the attribute, the media object in association with an application of the electronic device. 
     In some examples, processing unit  1608  is further configured to after displaying the media object as the first message and before receiving the second user input, display (e.g., with display enabling unit  1610  and on display unit  1602 ), as a sixth message in the GUI, a request for additional information regarding the media object. 
     In some examples, causing the user intent to be determined further comprises causing a domain among a plurality of domains of an oncology to be determined based on the first user input and the second user input. 
     The operations described above with reference to  FIGS. 11A-D  can be optionally implemented by components depicted in  FIGS. 1-4, 6A -B, and  7 A. For example, the operations of process  1100  may be implemented by one or more of operating system  718 , applications module  724 , I/O processing module  728 , STT processing module  730 , natural language processing module  732 , task flow processing module  736 , service processing module  738 , or processor(s)  220 ,  410 ,  704 . It would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIGS. 1-4, 6A -B, and  7 A. 
       FIG. 17  shows a functional block diagram of electronic device  1700  configured in accordance with the principles of the various described examples. The functional blocks of the device can be optionally implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in  FIG. 17  can be optionally combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination, separation, or further definition of the functional blocks described herein. 
     As shown in  FIG. 17 , electronic device  1700  can include touch screen display unit  1702  configured to display a graphical user interface and to receive input from the user, audio input unit  1704  configured to receive audio input (e.g., speech input), and optionally, RF unit  1706  configured to transmit and receive information. Electronic device  1700  can further include processing unit  1708  coupled to touch screen display unit  1702 , audio input unit  1704 , and RF unit  1706 . In some examples, processing unit  1708  can include display enabling unit  1710 , receiving unit  1712 , causing unit  1714 , transmitting unit  1717 , and determining unit  1718 . 
     In accordance with some embodiments, processing unit  1708  is configured to display (e.g., with display enabling unit  1710 ) on display unit  1702 , a graphical user interface (GUI) having a plurality of previous messages between a user of the electronic device and a user of a remote device. The plurality of previous messages is presented in a conversational view. Processing unit  1708  is further configured to receive (e.g., with receiving unit  1712 ), from the user of the electronic device, a first user input addressed to a digital assistant of the electronic device. Processing unit  1708  is further configured to, in response to receiving the first user input, display (e.g., with display enabling unit  1710  and on display unit  1702 ) the first user input as a first message in the GUI. Processing unit  1708  is further configured to cause (e.g., with causing unit  1714 ) an action to be performed in accordance with a user intent derived from the first user input. Processing unit  1708  is further configured to display (e.g., with display enabling unit  1710  and on display unit  1702 ) a response as a second message in the GUI, the response based on the action. 
     In some examples, processing unit  1708  is further configured to receive (e.g., with receiving unit  1712 ), from the user of the remote device, a second user input addressed to the digital assistant. Processing unit  1708  is further configured to, in response to receiving the second user input, display (e.g., with display enabling unit  1710  and on display unit  1702 ) the second user input as a third message in the GUI. Processing unit  1708  is further configured to cause (e.g., with causing unit  1714 ) a second action to be performed in accordance with a second user intent derived from the second user input and the user intent. Processing unit  1708  is further configured to display (e.g., with display enabling unit  1710  and on display unit  1702 ) a second response as a fourth message in the GUI, the second response based on the second action. 
     In some examples, the second user intent comprises refining the user intent. 
     In some examples, the user intent and the second user intent both include a same domain, and the second user intent includes a parameter that the user intent does not include. 
     In some examples, processing unit  1708  is further configured to transmit (e.g., with transmitting unit  1716  and using RF unit  1706 ) the second response to the remote device. Processing unit  1708  is further configured to cause (e.g., with causing unit) display of the second response in a GUI of the remote device. 
     In some examples, processing unit  1708  is further configured to determine (e.g., with determining unit  1718 ) whether the first user input includes a predetermined trigger phrase to invoke the digital assistant. Processing unit  1708  is further configured to cause (e.g., with causing unit  1714 ) the action to be performed and display (e.g., with display enabling unit  1710  and on display unit  1702 ) the response as the second message in response to determining that the first user input includes a predetermined trigger phrase. 
     In some examples, processing unit  1708  is further configured to receive (e.g., with receiving unit  1712 ) input from a digital assistant of the remote device. Processing unit  1708  is further configured to, in response to receiving the input, display (e.g., with display enabling unit  1710  and on display unit  1702 ) the input as a fifth message in the GUI. 
     In some examples, processing unit  1708  is further configured to display (e.g., with display enabling unit  1710  and on display unit  1702 ) an indication in the GUI that a content of the fifth message was generated by the digital assistant of the remote device. 
     In some examples, processing unit  1708  is further configured to, in response to receiving the input from the digital assistant of the remote device, cause (e.g., with causing unit  1714 ) the digital assistant of the electronic device to generate a content of the fifth message, where the content of the fifth message includes the input from the digital assistant of the remote device. Processing unit  1708  is further configured to display (e.g., with display enabling unit  1710  and on display unit  1702 ) in the GUI, an indication that the content of the fifth message was generated by the digital assistant of the electronic device. 
     In some examples, processing unit  1708  is further configured to, in response to receiving the input from the digital assistant of the remote device: cause (e.g., with causing unit  1714 ) a third action to be performed in accordance with a third user intent derived from the input from the digital assistant of the remote device, and display (e.g., with display enabling unit  1710  and on display unit  1702 ) a third response as a sixth message in the GUI, the third response based on the third action. 
     In some examples, processing unit  1708  is further configured to transmit (e.g., with transmitting unit  1716 ) the response to the remote device. Processing unit  1708  is further configured to cause (e.g., with causing unit  1714 ) display of the response in a GUI of the remote device. 
     In some examples, causing the action to be performed and displaying the response are performed automatically in response to receiving the first user input and without additional human intervention. 
     The operations described above with reference to  FIGS. 13A-C  can be optionally implemented by components depicted in  FIGS. 1-4, 6A -B, and  7 A. For example, the operations of process  1300  may be implemented by one or more of operating system  718 , applications module  724 , I/O processing module  728 , STT processing module  730 , natural language processing module  732 , task flow processing module  736 , service processing module  738 , or processor(s)  220 ,  410 ,  704 . It would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in  FIGS. 1-4, 6A -B, and  7 A. 
     In accordance with some implementations, a computer-readable storage medium (e.g., a non-transitory computer readable storage medium) is provided, the computer-readable storage medium storing one or more programs for execution by one or more processors of an electronic device, the one or more programs including instructions for performing any of the methods or processes described herein. 
     In accordance with some implementations, an electronic device (e.g., a portable electronic device) is provided that comprises means for performing any of the methods or processes described herein. 
     In accordance with some implementations, an electronic device (e.g., a portable electronic device) is provided that comprises a processing unit configured to perform any of the methods or processes described herein. 
     In accordance with some implementations, an electronic device (e.g., a portable electronic device) is provided that comprises one or more processors and memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for performing any of the methods or processes described herein. 
     The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated. 
     Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims. 
     As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information. 
     The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. 
     The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. 
     Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information. 
     Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publically available information.

Metadata:
Filing Date: 20160510
Publication Date: 20200623
Grant Date: 20200623
Priority Date: 20151106
Inventors: KARASHCHUK, Petr
VEGA GALVEZ, TOMAS A.
GRUBER, THOMAS R.
Assignee: APPLE INC
CPC Classifications: [{"code": "G06F3/167", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/12", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/046", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/02", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06Q10/109", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q10/107", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/453", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/216", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/216", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L67/52", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/453", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06F9/453", "inventive": true, "first": true, "tree": "[]"}, {"code": "H04L51/046", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q50/01", "inventive": false, "first": false, "tree": "[]"}, {"code": "G10L2015/223", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06Q10/109", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q10/107", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q50/01", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04L51/02", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q10/109", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/02", "inventive": true, "first": false, "tree": "[]"}, {"code": "G10L15/26", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04W4/12", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04105", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F2203/04105", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04L51/10", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/167", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/046", "inventive": true, "first": false, "tree": "[]"}, {"code": "G10L15/26", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04L51/10", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F40/166", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/12", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q10/107", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/167", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06Q50/01", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04L51/046", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F40/166", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/02", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F9/453", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06Q10/107", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04105", "inventive": false, "first": false, "tree": "[]"}, {"code": "G10L2015/223", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04L51/10", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06Q10/109", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04842", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04883", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04W4/12", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L51/16", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04L67/18", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0482", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/04886", "inventive": true, "first": false, "tree": "[]"}, {"code": "G10L15/26", "inventive": false, "first": false, "tree": "[]"}]
Family ID: 58662305