Digital assistant interaction in a video communication session environment

Abstract

The present disclosure relates to intelligent automated assistants in a video communication session environment. An example method includes: during a video communication session between at least two user devices and at a first user device among the at least two user devices: receiving a first user input; obtaining a first digital assistant response based on the first user input; providing the first digital assistant response and context information associated with the first user input to a second user device among the at least two user devices; outputting the first digital assistant response; receiving a second digital assistant response and context information associated with the second user input, wherein the second user input is received at the second user device, and wherein the second digital assistant response is determined based on the second user input and the context information associated with the first user input; and outputting the second digital assistant response.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of the following patent applications: U.S. Provisional Application No. 62 / 975,643, entitled “DIGITAL ASSISTANT INTERACTION IN A VIDEO COMMUNICATION SESSION ENVIRONMENT,” filed on February 12, 2020; U.S. Provisional Application No. 63 / 016,083, entitled “DIGITAL ASSISTANT INTERACTION IN AVIDEO COMMUNICATION SESSION ENVIRONMENT,” filed on April 27, 2020; and U.S. Patent Application No. 17 / 158,703, entitled “DIGITAL ASSISTANT INTERACTION IN A VIDEO COMMUNICATION SESSION ENVIRONMENT,” filed on January 26, 2021, the contents of which are hereby incorporated by reference in their entirety. Technical Field

[0003] The present invention relates generally to intelligent automated assistants, and more particularly to intelligent automated assistants in the context of video communication sessions. Background Art

[0004] Intelligent automated assistants (or digital assistants) can provide a convenient interface between human users and electronic devices. Such assistants can allow users to interact with devices or systems using natural language in the form of speech and / or text. For example, a user can provide voice input containing a user request to a digital assistant running on an electronic device. The digital assistant can interpret the user's intent from the voice input and operationalize the user's intent into tasks. These tasks can then be performed by executing one or more services of the electronic device, and relevant output responsive to the user's request can be returned to the user. Summary of the Invention

[0005] In some examples, a user of an electronic device may participate in a video communication session with one or more other participants. Accordingly, it may be desirable to provide digital assistant functionality to the user and other participants during the video communication session, such that the user and / or other participants may, for example, request / command their respective digital assistants to perform certain tasks during the video communication session. Furthermore, it may be desirable for the devices participating in the video communication session to share contextual information during the video communication session, such that the digital assistant of each of the devices may, for example, be aware of digital assistant requests / responses received / provided at the other participating devices. This, in turn, creates the appearance of a single digital assistant participating in the video communication session with the user and other participants, while still allowing the digital assistant of each device participating in the video communication session to locally process requests / commands from its respective user.

[0006] An example method is disclosed herein. An example method includes, during a video communication session between at least two user devices and at a first user device of the at least two user devices: receiving a first user input; obtaining a first digital assistant response based on the first user input; providing the first digital assistant response and context information associated with the first user input to a second user device of the at least two user devices; outputting the first digital assistant response; receiving a second digital assistant response and context information associated with the second user input, wherein the second user input is received at the second user device, and wherein the second digital assistant response is determined based on the second user input and the context information associated with the first user input; and outputting the second digital assistant response.

[0007] Another example method includes: during a video communication session between at least two user devices and at a first user device among the at least two user devices: receiving a first user voice input; generating a text representation based on the first user voice input; transmitting the text representation to one or more servers; receiving a shared transcription from the one or more servers, wherein the shared transcription includes a text representation of the first user voice input and one or more additional text representations generated by a second user device among the at least two user devices, and wherein the one or more additional text representations correspond to one or more user voice inputs received at the second user device during the video communication session; and after receiving the shared transcription: determining one or more candidate tasks that can be performed by a digital assistant of the first user device based on the text representation included in the shared transcription; and presenting the one or more candidate tasks.

[0008] Another example method includes: during a video communication session between at least two user devices and at a first user device among the at least two user devices: receiving a first user voice input; determining whether the first user voice input represents a common digital assistant request; based on determining that the first user voice input represents a common digital assistant request, transmitting a request to a second user device among the at least two user devices so that the second user device provides context information associated with the first user voice input to the first user device; receiving context information associated with the first user voice input from the second user device; obtaining a first digital assistant response based on at least a portion of the context information received from the second user device and at least a portion of the context information associated with the first user voice input stored on the first user device; providing the first digital assistant response to the second user device; and outputting the first digital assistant response.

[0009] Disclosed herein is an example non-transitory computer-readable storage medium. An example non-transitory computer-readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of a first user device during a video communication session between a first user device and at least a second user device, cause the first user device to: receive a first user input; obtain a first digital assistant response based on the first user input; provide the first digital assistant response and context information associated with the first user input to a second user device; output the first digital assistant response; receive a second digital assistant response and context information associated with the second user input, wherein the second user input is received at the second user device, and wherein the second digital assistant response is determined based on the second user input and the context information associated with the first user input; and output the second digital assistant response.

[0010] Another example non-transitory computer-readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of the first user device during a video communication session between the first user device and at least a second user device, cause the first user device to: receive a first user voice input; generate a text representation based on the first user voice input; transmit the text representation to one or more servers; receive a shared transcript from the one or more servers, wherein the shared transcript includes the text representation of the first user voice input and one or more additional text representations generated by a second user device of the at least two user devices, and wherein the one or more additional text representations correspond to the one or more user voice inputs received at the second user device during the video communication session; and after receiving the shared transcript: determine one or more candidate tasks that can be performed by a digital assistant of the first user device based on the text representations included in the shared transcript; and present the one or more candidate tasks.

[0011] Another example non-transitory computer-readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of the first user device during a video communication session between the first user device and at least a second user device, cause the first user device to: receive a first user voice input; determine whether the first user voice input represents a common digital assistant request; based on determining that the first user voice input represents a common digital assistant request, transmit a request to a second user device of the at least two user devices for the second user device to provide context information associated with the first user voice input to the first user device; receive context information associated with the first user voice input from the second user device; obtain a first digital assistant response based on at least a portion of the context information received from the second user device and at least a portion of the context information associated with the first user voice input stored on the first user device; provide the first digital assistant response to the second user device; and output the first digital assistant response.

[0012] An example electronic device is disclosed herein. An example user device includes: one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations during a video communication session between the user device and at least a second user device: receiving a first user input; obtaining a first digital assistant response based on the first user input; providing the first digital assistant response and context information associated with the first user input to a second user device of the at least two user devices; outputting the first digital assistant response; receiving a second digital assistant response and context information associated with the second user input, wherein the second user input is received at the second user device, and wherein the second digital assistant response is determined based on the second user input and the context information associated with the first user input; and outputting the second digital assistant response.

[0013] Another example user device includes: one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for the following operations during a video communication session between the user device and at least a second user device: receiving a first user voice input; generating a text representation based on the first user voice input; transmitting the text representation to one or more servers; receiving a shared transcription from the one or more servers, wherein the shared transcription includes a text representation of the first user voice input and one or more additional text representations generated by a second user device of at least two user devices, and wherein the one or more additional text representations correspond to one or more user voice inputs received at the second user device during the video communication session; and after receiving the shared transcription: determining one or more candidate tasks that can be performed by a digital assistant of the first user device based on the text representation included in the shared transcription; and presenting the one or more candidate tasks.

[0014] Another example user device includes: one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for the following operations during a video communication session between the user device and at least a second user device: receiving a first user voice input; determining whether the first user voice input represents a common digital assistant request; based on determining that the first user voice input represents a common digital assistant request, transmitting a request to a second user device of at least two user devices so that the second user device provides context information associated with the first user voice input to the first user device; receiving context information associated with the first user voice input from the second user device; obtaining a first digital assistant response based on at least a portion of the context information received from the second user device and at least a portion of the context information associated with the first user voice input stored on the first user device; providing the first digital assistant response to the second user device; and outputting the first digital assistant response.

[0015] An example user device includes: a device for receiving a first user input during a video communication session between the user device and at least a second user device; a device for obtaining a first digital assistant response based on the first user input; a device for providing the first digital assistant response and contextual information associated with the first user input to a second user device of at least two user devices; a device for outputting the first digital assistant response; a device for receiving a second digital assistant response and contextual information associated with the second user input, wherein the second user input is received at the second user device, and wherein the second digital assistant response is determined based on the second user input and the contextual information associated with the first user input; and a device for outputting the second digital assistant response.

[0016] Another example user device includes: a device for receiving a first user voice input during a video communication session between the user device and at least a second user device; a device for generating a text representation based on the first user voice input; a device for transmitting the text representation to one or more servers; a device for receiving a shared transcription from the one or more servers, wherein the shared transcription includes a text representation of the first user voice input and one or more additional text representations generated by a second user device of at least two user devices, and wherein the one or more additional text representations correspond to one or more user voice inputs received at the second user device during the video communication session; and after receiving the shared transcription: a device for determining one or more candidate tasks that can be performed by a digital assistant of the first user device based on the text representation included in the shared transcription; and a device for presenting the one or more candidate tasks.

[0017] Another example user device includes: a device for receiving a first user voice input during a video communication session between the user device and at least a second user device; a device for determining whether the first user voice input represents a common digital assistant request; a device for transmitting a request to a second user device of at least two user devices so that the second user device provides context information associated with the first user voice input to the first user device based on determining that the first user voice input represents a common digital assistant request; a device for receiving context information associated with the first user voice input from the second user device; a device for obtaining a first digital assistant response based on at least a portion of the context information received from the second user device and at least a portion of the context information associated with the first user voice input stored on the first user device; a device for providing the first digital assistant response to the second user device; and a device for outputting the first digital assistant response.

[0018] In some examples, receiving a second digital assistant response and contextual information associated with the second user input at a first user device (and during a video communication session) can improve the video communication session experience involving the digital assistant, wherein the second user input is received at the second user device, and wherein the second digital assistant response is determined based on the second user input and the contextual information associated with the first user input (received at the first user device). Specifically, using the contextual information associated with the first user input to determine the second digital assistant response allows the digital assistant of the second user device to provide a digital assistant response based on and / or facilitate the first user input, even if the first user input was not provided by the user of the second user device. In this way, the user of the second user device can provide a digital assistant request in a more natural and conversational manner (e.g., provided in the second user input), and if certain aspects of the request were already introduced in the first user input, those aspects do not have to be repeated. For example, if the first user input includes a user request "Hey, Siri, what's the weather in Palo Alto?", the user of the second user device can then request weather information about New York by providing a second user input "Hey, Siri, what's the weather in New York?", rather than having to repeat the request for weather information (e.g., "Hey, Siri, what's the weather in New York?"). This, in turn, creates the appearance of a single digital assistant participating in the video communication session with the users of the first user device and the second user device, which, as described above, may ultimately improve the users' video communication session experience.

[0019] In some examples, determining one or more candidate tasks that can be performed by the digital assistant of the first user device based on the text representation included in the shared transcript allows the digital assistant of the first user to proactively determine one or more tasks that the user of the first user device may want the digital assistant to perform based on the conversation held during the video communication session. In this way, the digital assistant prevents the user from having to request such tasks separately, ensures that the user does not forget to request such tasks, and / or informs the user of tasks that the digital assistant is capable of performing (e.g., that the user was previously unaware of). This, in turn, can improve the user's experience with the video communication session and the digital assistant of the first user device.

[0020] In some examples, determining at a first user device among at least two user devices participating in a video communication session whether a first user voice input represents a common digital assistant request, and based on the determination that the first user voice input represents a common digital assistant request, transmitting a request to a second user device among the at least two user devices so that the second user device provides contextual information associated with the first user voice input to the first user device can improve the video communication session experience involving a digital assistant. Specifically, determining whether the user voice input is a common digital assistant request and subsequently transmitting a request for contextual information associated with the user voice input to the second user device (if the user voice input is a common digital assistant request) allows users of the first user device and the second user device to provide digital assistant requests in a more natural and conversational manner during the video communication session. For example, rather than each user having to individually provide the same digital assistant request during a video communication session (e.g., “Hey, Siri, when am I free today?”), the user of the first user device can provide a common digital assistant request (e.g., “Hey, Siri, find a time for us to meet.”), and as will be described in more detail below, the first user device can then obtain and provide one or more digital assistant responses that take into account contextual information from both the first user device and the second user device (e.g., “John and you are both free today at 5:30 PM.”). This, in turn, creates the appearance of a single digital assistant that is engaged with the users of the first and second user devices (as opposed to separate digital assistants for each user device) and is aware of the context of the users / user devices. This ultimately improves the video communication session experience for the users of the first and second user devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A block diagram illustrating systems and environments for implementing a digital assistant according to various examples.

[0022] Figure 2A A block diagram of a portable multifunction device that implements the client-side portion of a digital assistant according to various examples is shown.

[0023] Figure 2B is a block diagram illustrating exemplary components for event processing according to various examples.

[0024] Figure 3 A portable multifunction device implementing the client-side portion of a digital assistant according to various examples is shown.

[0025] Figure 4 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to various examples.

[0026] Figure 5AAn exemplary user interface is shown for a menu of applications on a portable multifunction device according to various examples.

[0027] Figure 5B Exemplary user interfaces for a multifunction device with a touch-sensitive surface separate from the display are shown according to various examples.

[0028] Figure 6A A personal electronic device according to various examples is shown.

[0029] Figure 6B is a block diagram illustrating a personal electronic device according to various examples.

[0030] Figure 7A A block diagram of a digital assistant system or a server portion thereof according to various examples is shown.

[0031] Figure 7B Shown in accordance with various examples Figure 7A The capabilities of the digital assistant shown in .

[0032] Figure 7C A portion of an ontology according to various examples is shown.

[0033] Figure 8 Systems and techniques for providing context-aware digital assistant responses during a video communication session are shown according to various examples.

[0034] Figure 9 Exemplary user interfaces for a video communication session are shown according to various examples.

[0035] Figure 10 Systems and techniques for determining candidate digital assistant tasks based on user voice input received at a user device participating in a video communication session are shown according to various examples.

[0036] Figure 11 An exemplary user interface for real-time transcription of a video communication session is shown according to various examples.

[0037] Figure 12 Systems and techniques for providing digital assistant responses to common digital assistant requests during a video communication session are shown according to various examples.

[0038] 13A to 13C A flowchart representing a process for providing context-aware digital assistant responses during a video communication session is shown, according to various examples.

[0039] FIG. 14A to FIG. 14BA flowchart representing a process for determining candidate digital assistant tasks based on user voice input received at a user device participating in a video communication session is shown according to various examples.

[0040] FIG. 15A to FIG. 15B A flowchart representing a process for providing digital assistant responses to common digital assistant requests during a video communication session is shown according to various examples. DETAILED DESCRIPTION

[0041] In the following description of the examples, reference is made to the accompanying drawings, which show, by way of illustration, specific examples that may be implemented. It should be understood that other examples may be used and structural changes may be made without departing from the scope of the various examples.

[0042] The present disclosure relates to intelligent automated assistants in the context of a video communication session. For example, the present disclosure describes providing a context-aware digital assistant at multiple user devices participating in a video communication session by using contextual information from a first user device to determine a digital assistant response at a second user device. In this way, a user participating in the video communication session can interact with the digital assistant during the video communication session as if the digital assistant were another participant in the video communication session. The present disclosure also describes automatically determining candidate digital assistant tasks based on a shared transcription of user voice input received at the user device participating in the video communication session. In this way, a digital assistant of a user device participating in the video communication session can proactively determine one or more tasks that a user of the user device may want the digital assistant to perform based on a conversation maintained during the video communication session.

[0043] Although the following description uses the terms "first," "second," etc. to describe various elements, these elements should not be limited by these terms. These terms are simply used to distinguish one element from another. For example, without departing from the scope of the various described examples, a first input may be referred to as a second input, and similarly, a second input may be referred to as a first input. Both the first input and the second input are inputs, and in some cases, are independent and distinct inputs.

[0044] The terms used in the description of the various examples described herein are only for the purpose of describing specific examples and are not intended to be limiting. As used in the description of the various examples described and in the appended claims, the singular forms "a", "an" and "the" are intended to also include the plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "and / or" used herein refer to and encompass any and all possible combinations of one or more of the associated listed items. It will also be 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 parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their groupings.

[0045] Depending on the context, the term "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting." Similarly, depending on the context, the phrase "if it is determined that..." or "if [stated condition or event] is detected" may be interpreted to mean "upon determining that..." or "in response to determining that..." or "upon detecting [stated condition or event]" or "in response to detecting [stated condition or event]."

[0046] 1. System and Environment

[0047] Figure 1 A block diagram of a system 100 according to various examples is shown. In some examples, the system 100 implements a digital assistant. The terms "digital assistant," "virtual assistant," "intelligent automated assistant," or "automated digital assistant" 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 performs one or more of the following steps: identifying a task flow having steps and parameters designed to implement the inferred user intent, inputting specific requirements into the task flow based on the inferred user intent; executing the task flow by calling a program, method, service, API, etc.; and generating an output response to the user in an audible (e.g., voice) and / or visual form.

[0048] Specifically, digital assistants are capable of accepting user requests that are at least partially in the form of natural language commands, requests, statements, narrations, and / or inquiries. Typically, user requests seek an informational answer from the digital assistant or the performance of a task. A satisfactory response to a user request includes providing the requested informational answer, performing the requested task, or a combination of the two. For example, a user asks the digital assistant a question such as, "Where am I now?" Based on the user's current location, the digital assistant responds, "You are near Central Park West." The user also requests a task, such as, "Please invite my friends to my girlfriend's birthday party next week." In response, the digital assistant may acknowledge the request by saying, "Okay, right away," and then send appropriate calendar invitations on behalf of the user to each of the user's friends listed in the user's electronic address book. While performing the requested task, the digital assistant sometimes interacts with the user in a continuous conversation involving multiple information exchanges over an extended period of time. There are many other ways to interact with a digital assistant to request information or perform various tasks. In addition to providing verbal responses and taking programmed actions, digital assistants also provide responses in other visual or audio forms, such as text, alerts, music, videos, animations, and the like.

[0049] like Figure 1 As shown, in some examples, the digital assistant is implemented according to a client-server model. The digital assistant includes a client-side portion 102 (hereinafter referred to as "DA client 102") executing on a user device 104 and a server-side portion 106 (hereinafter referred to as "DA server 106") executing on a server system 108. The DA client 102 communicates with the DA server 106 via one or more networks 110. The DA client 102 provides client-side functionality, such as input and output processing for the user, and communication with the DA server 106. The DA server 106 provides server-side functionality for any number of DA clients 102, each located on a corresponding user device 104.

[0050] In some examples, the DA server 106 includes a client-facing I / O interface 112, one or more processing modules 114, data and models 116, and an I / O interface to external services 118. The client-facing I / O interface 112 facilitates client-facing input and output processing of the DA server 106. The one or more processing modules 114 utilize the data and models 116 to process voice input and determine user intent based on the natural language input. In addition, the one or more processing modules 114 perform task execution based on the inferred user intent. In some examples, the DA server 106 communicates with external services 120 over one or more networks 110 to complete tasks or collect information. The I / O interface 118 to external services facilitates such communications.

[0051] User device 104 can be any suitable electronic device. In some examples, user device 104 is a portable multifunction device (e.g., Figure 2A The device 200), multifunctional device (eg, Figure 4 The device 400) or a personal electronic device (eg, Figures 6A to 6B The portable multifunction device is, for example, a mobile phone that also includes other functions (such as a PDA and / or music player functions). Specific examples of portable multifunction devices include the Apple iPod and Device. Other examples of portable multifunction devices include, but are not limited to, earbuds / headphones, speakers, and laptops or tablets. In addition, in some examples, user device 104 is a non-portable multifunction device. Specifically, user device 104 is a desktop computer, a game console, a speaker, a television, or a television set-top box. In some examples, user device 104 includes a touch-sensitive surface (e.g., a touch screen display and / or a touchpad). In addition, user device 104 optionally includes 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 multifunction devices are described in more detail below.

[0052] Examples of the one or more communication networks 110 include local area networks (LANs) and wide area networks (WANs), such as the Internet. The one or more communication networks 110 are implemented using any known network protocol, including various wired or wireless protocols such as 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 (VoIP), Wi-MAX, or any other suitable communication protocol.

[0053] The server system 108 is implemented on one or more stand-alone data processing devices or a distributed computer network. In some examples, the server system 108 also uses various virtual devices and / or services of third-party service providers (e.g., third-party cloud service providers) to provide the potential computing resources and / or infrastructure resources of the server system 108.

[0054] In some examples, the user device 104 communicates with the DA server 106 via a second user device 122. The second user device 122 is similar or identical to the user device 104. For example, the second user device 122 is similar to the user device 104 described below with reference to FIG. Figure 2A 、 Figure 4 as well as Figures 6A to 6B The device 200, 400 or 600 described. The user device 104 is configured to be communicatively coupled to the second user device 122 via a direct communication connection (such as, Bluetooth, NFC, BTLE, etc.) or via a wired or wireless network (such as, a local Wi-Fi network). In some examples, the second user device 122 is configured to act as a proxy between the user device 104 and the DA server 106. For example, the DA client 102 of the user device 104 is configured to transmit information (e.g., a user request received at the user device 104) to the DA server 106 via the second user device 122. The DA server 106 processes the information and returns relevant data (e.g., data content in response to the user request) to the user device 104 via the second user device 122.

[0055] In some examples, the user device 104 is configured to send an abbreviated request for data to a second user device 122 to reduce the amount of information transmitted from the user device 104. The second user device 122 is configured to determine supplemental information to add to the abbreviated request to generate a complete request for transmission to the DA server 106. The system architecture can advantageously allow user devices 104 with limited communication capabilities and / or limited battery power (e.g., a watch or similar compact electronic device) to access services provided by the DA server 106 by using a second user device 122 with greater communication capabilities and / or battery power (e.g., a mobile phone, laptop, tablet, etc.) as a proxy to the DA server 106. Although Figure 1 Only two user devices 104 and 122 are shown, but it should be understood that in some examples, the system 100 may include any number and type of user devices configured to communicate with the DA server system 106 in this proxy configuration.

[0056] Although Figure 1 The digital assistant shown in includes both a client-side portion (e.g., DA client 102) and a server-side portion (e.g., DA server 106), but in some examples, the functionality of the digital assistant is implemented as a stand-alone application installed on a user device. Furthermore, the division of functionality between the client and server portions of the digital assistant can vary in different implementations. For example, in some examples, the DA client is a thin client that provides only user-facing input and output processing functionality and delegates all other functionality of the digital assistant to a backend server.

[0057] 2. Electronic devices

[0058] Attention now turns to embodiments of electronic devices for implementing the client-side portion of the digital assistant. Figure 2A2 is a block diagram illustrating a portable multifunction device 200 with a touch-sensitive display system 212 according to some embodiments. The touch-sensitive display 212 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The device 200 includes memory 202 (which optionally includes one or more computer-readable storage media), a memory controller 222, one or more processing units (CPUs) 220, a peripheral device interface 218, RF circuitry 208, audio circuitry 210, a speaker 211, a microphone 213, an input / output (I / O) subsystem 206, other input control devices 216, and external ports 224. The device 200 optionally includes one or more optical sensors 264. The device 200 optionally includes one or more contact intensity sensors 265 for detecting the intensity of contacts on the device 200 (e.g., a touch-sensitive surface of the device 200 such as the touch-sensitive display system 212). Device 200 optionally includes one or more tactile output generators 267 for generating tactile output on device 200 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 212 of device 200 or trackpad 455 of device 400). These components optionally communicate via one or more communication buses or signal lines 203.

[0059] As used in this 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 surrogate (surrogate) 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 different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the surrogate measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some embodiments, the surrogate measurement of the contact force or pressure is converted into 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 the contact as an attribute of the user input allows the user to access additional device functionality that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0060] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device that will be detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical characteristic of the device or 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 "press click" or "release click" on a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click," even when the physical actuation button associated with the touch-sensitive surface that was physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when the smoothness of the touch-sensitive surface does not change, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. While such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

[0061] It should be understood 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. Figure 2A The various components shown in FIG. 5 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0062] Memory 202 includes one or more computer-readable storage media. These computer-readable storage media are, for example, tangible and non-transitory. Memory 202 includes high-speed random access memory and also includes 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 controls access to memory 202 by other components of device 200.

[0063] In some examples, the non-transitory computer-readable storage medium of memory 202 is used to store instructions (e.g., for performing various aspects of the processes described below) for use by or in conjunction with an instruction execution system, apparatus, or device, such as a computer-based system, a system containing a processor, or other system that can retrieve instructions from an instruction execution system, apparatus, or device and execute the instructions. In other examples, the instructions (e.g., for performing various aspects of the processes described below) are stored on a non-transitory computer-readable storage medium (not shown) of server system 108 or divided between the non-transitory computer-readable storage medium of memory 202 and the non-transitory computer-readable storage medium of server system 108.

[0064] The peripheral device interface 218 is used to couple the input and output peripheral devices of the device to the CPU 220 and the memory 202. The one or more processors 220 run or execute various software programs and / or instruction sets stored in the memory 202 to perform various functions of the device 200 and process data. In some embodiments, the peripheral device interface 218, the CPU 220, and the memory controller 222 are implemented on a single chip, such as the chip 204. In some other embodiments, they are implemented on separate chips.

[0065] RF (radio frequency) circuitry 208 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 208 converts electrical signals into / from electromagnetic signals and communicates with communication networks and other communication 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 the like. RF circuitry 208 optionally communicates with networks and other devices via wireless communications, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuitry 208 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via a short-range communication radio. Wireless communication optionally uses any of a variety of communication 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.11b), IEEE 802.11c, IEEE 802.11d ... 11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (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 that have not yet been developed as of the filing date of this document.

[0066] The audio circuit 210, speaker 211, and microphone 213 provide an audio interface between the user and the device 200. The audio circuit 210 receives audio data from the peripheral device interface 218, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 211. The speaker 211 converts the electrical signals into sound waves audible to humans. The audio circuit 210 also receives electrical signals converted from sound waves by the microphone 213. The audio circuit 210 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 218 for processing. The audio data is retrieved from and / or transmitted to the memory 202 and / or the RF circuit 208 via the peripheral device interface 218. In some embodiments, the audio circuit 210 also includes a headset jack (e.g., Figure 3 The headset jack provides an interface between the audio circuitry 210 and a removable audio input / output peripheral device, such as an output-only headset or a headset with both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0067] The I / O subsystem 206 couples input / output peripherals on the device 200, such as the touch screen 212 and other input control devices 216, to the peripheral device interface 218. The I / O subsystem 206 optionally includes a display controller 256, an optical sensor controller 258, an intensity sensor controller 259, a tactile 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, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller 260 is optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 3 308) optionally includes an up / down button for volume control of the speaker 211 and / or microphone 213. The one or more buttons optionally include a push button (e.g., Figure 3 306 in ).

[0068] A quick press of the push button releases the lock on the touch screen 212 or initiates the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application No. 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 306) turns the device 200 on or off. The user can customize the function of one or more buttons. The touch screen 212 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0069] The touch-sensitive display 212 provides an input interface and an output interface between the device and the user. The display controller 256 receives electrical signals from the touch screen 212 and / or sends electrical signals to the touch screen 212. The touch screen 212 displays visual output to the user. The visual output includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects.

[0070] The touch screen 212 has a touch-sensitive surface, sensor, or sensor group that accepts input from the user based on tactile and / or haptic contact. The touch screen 212 and display controller 256 (together with any associated modules and / or instruction sets in memory 202) detect contact on the touch screen 212 (and any movement or interruption of that contact) and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 212. In an exemplary embodiment, the point of contact between the touch screen 212 and the user corresponds to the user's finger.

[0071] The touch screen 212 uses 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. The touch screen 212 and display controller 256 use any of a variety 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 the touch screen 212 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® Touch Controller from Apple Inc. (Cupertino, California). and iPod The technology used in

[0072] In some embodiments, the touch-sensitive display of the touch screen 212 is similar to the multi-touch-sensitive trackpads described in U.S. Patents 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 212 displays visual output from the device 200, whereas a touch-sensitive trackpad does not provide visual output.

[0073] In some embodiments, the touch-sensitive display of the touch screen 212 is as described in the following applications: (1) U.S. patent application No. 11 / 381,313, filed on May 2, 2006, entitled "Multipoint Touch Surface Controller"; (2) U.S. patent application No. 10 / 840,862, filed on May 6, 2004, entitled "Multipoint Touchscreen"; (3) U.S. patent application No. 10 / 903,964, filed on July 30, 2004, entitled "Gestures For Touch Sensitive Input Devices"; (4) U.S. patent application No. 11 / 048,264, filed on January 31, 2005, entitled "Gestures For Touch Sensitive Input Devices"; (5) U.S. patent application No. 11 / 050,694, filed on January 18, 2005, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices”; (6) U.S. Patent Application No. 11 / 228,758, filed on September 16, 2005, entitled “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. Patent Application No. 11 / 228,700, filed on September 16, 2005, entitled “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. Patent Application No. 11 / 228,737, filed on September 16, 2005, entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”; and (9) U.S. Patent Application No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device”. All of these applications are incorporated herein by reference in their entirety.

[0074] The touch screen 212 has, for example, a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user makes contact with the touch screen 212 using any suitable object or appendage, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to operate primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of a finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the user's desired action.

[0075] In some embodiments, in addition to the touch screen, the device 200 includes a touchpad (not shown) for activating or deactivating specific 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 is a touch-sensitive surface that is separate from the touch screen 212 or an extension of the touch-sensitive surface formed by the touch screen.

[0076] Device 200 also includes a power system 262 for powering the various components. Power system 262 includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuitry, 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 a portable device.

[0077] Device 200 also includes one or more optical sensors 264 . Figure 2A An optical sensor coupled to the optical sensor controller 258 in the I / O subsystem 206 is shown. The optical sensor 264 includes a charge-coupled device (CCD) or complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 264 receives light projected from the environment through one or more lenses and converts the light into data representing an image. In conjunction with the imaging module 243 (also called a camera module), the optical sensor 264 captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 200, facing away from the touch screen display 212 on the front of the device, so that the touch screen display can be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user's image can be captured for video conferencing while viewing other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 264 can be changed by the user (for example, by rotating the lens and sensor in the device housing), so that a single optical sensor 264 can be used with the touch screen display for both video conferencing and still image and / or video image acquisition.

[0078] Device 200 optionally also includes one or more contact intensity sensors 265 . Figure 2A A contact force sensor is shown coupled to a force sensor controller 259 in the I / O subsystem 206. Contact force sensor 265 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). Contact force sensor 265 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 212). In some embodiments, at least one contact force sensor is located on the back of device 200, opposite to touch screen display 212 located on the front of device 200.

[0079] Device 200 also includes one or more proximity sensors 266 . Figure 2A A proximity sensor 266 is shown coupled to the peripherals interface 218. Alternatively, the proximity sensor 266 is coupled to the input controller 260 in the I / O subsystem 206. The proximity sensor 266 is implemented as described in the following U.S. patent applications: No. 11 / 241,839, entitled “Proximity Detector In Handheld Device”; No. 11 / 240,788, entitled “Proximity Detector In Handheld Device”; No. 11 / 620,702, entitled “Using Ambient Light Sensor To Augment Proximity Sensor Output”; No. 11 / 586,862, entitled “Automated Response To And Sensing Of User Activity In Portable Devices”; and No. 11 / 638,251, entitled “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entireties. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 212.

[0080] Device 200 optionally also includes one or more tactile output generators 267 . Figure 2AA tactile output generator is shown coupled to a tactile feedback controller 261 in the I / O subsystem 206. The tactile output generator 267 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components for converting electrical signals into tactile outputs on the device). The contact force sensor 265 receives tactile feedback generation instructions from the tactile feedback module 233 and generates tactile outputs on the device 200 that can be felt by a user of the device 200. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 212) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of the device 200) or laterally (e.g., back and forth in the same plane as the surface of the device 200). In some embodiments, at least one tactile output generator sensor is located on the back of the device 200, opposite the touch screen display 212 located on the front of the device 200.

[0081] Device 200 also includes one or more accelerometers 268 . Figure 2A An accelerometer 268 is shown coupled to the peripherals interface 218. Alternatively, the accelerometer 268 is coupled to the input controller 260 in the I / O subsystem 206. The accelerometer 268 implements as described in the following 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 herein by reference in their entireties. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from one or more accelerometers. The device 200 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the one or more accelerometers 268 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 200.

[0082] In some embodiments, the software components stored in memory 202 include an operating system 226, a communication module (or instruction set) 228, a contact / motion module (or instruction set) 230, a graphics module (or instruction set) 232, a text input module (or instruction set) 234, a global positioning system (GPS) module (or instruction set) 235, a digital assistant client module 229, and an application (or instruction set) 236. In addition, memory 202 stores data and models, such as user data and models 231. In addition, in some embodiments, memory 202 ( Figure 2A ) or 470( Figure 4 ) storage device / global internal state 257, such as Figure 2A and Figure 4 . The device / global internal state 257 includes one or more of the following: an active application state, which indicates which applications, if any, are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 212; a sensor state, which includes information obtained from the device's various sensors and input control devices 216; and position information regarding the device's position and / or posture.

[0083] The 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 facilitating communication between various hardware components and software components.

[0084] The communication module 228 facilitates communication with other devices via one or more external ports 224 and also includes various software components for processing data received by the RF circuit 208 and / or the external ports 224. The external ports 224 (e.g., Universal Serial Bus (USB), FireWire, etc.) are suitable for coupling directly to other devices or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are connected to (trademark of Apple Inc.) devices.

[0085] The contact / motion module 230 optionally detects contact with the touch screen 212 (in conjunction with the display controller 256) and other touch-sensitive devices (e.g., a trackpad or physical click wheel). The contact / motion module 230 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there has been movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has ceased (e.g., detecting a finger lift event or contact break). The contact / motion module 230 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single-finger contact) or multiple points of contact simultaneously (e.g., "multi-touch" / multiple-finger contact). In some embodiments, the contact / motion module 230 and display controller 256 detect contact on the touchpad.

[0086] In some embodiments, the contact / motion module 230 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 200). For example, a mouse "click" threshold for a touchpad or touchscreen can be set to any one of a large range of predefined thresholds without changing the touchpad or touchscreen display hardware. In addition, in some embodiments, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0087] The contact / motion module 230 optionally detects gesture input from the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Thus, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

[0088] The graphics module 232 includes various known software components for rendering and displaying graphics on the touch screen 212 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0089] In some embodiments, the graphics module 232 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 232 receives one or more codes specifying the graphics to be displayed from an application program or the like, along with coordinate data and other graphic attribute data, if necessary, and then generates screen image data for output to the display controller 256.

[0090] Haptic feedback module 233 includes various software components for generating instructions used by one or more tactile output generators 267 to produce tactile output at one or more locations on device 200 in response to user interaction with device 200 .

[0091] Text input module 234 , which in some examples is part of graphics module 232 , provides a soft keyboard for entering text in various applications (eg, contacts 237 , email 240 , IM 241 , browser 247 , and any other application requiring text input).

[0092] The GPS module 235 determines the location of the device and provides this information for use in various applications (e.g., to the phone 238 for use in location-based dialing; to the camera 243 as picture / video metadata; and to applications that provide location-based services, such as the weather widget, the local yellow pages widget, and the map / navigation widget).

[0093] The digital assistant client module 229 includes various client-side digital assistant instructions to provide client-side functionality of the digital assistant. For example, the digital assistant client module 229 is capable of accepting voice input (e.g., speech input), text input, touch input, and / or gesture input through various user interfaces of the portable multifunction device 200 (e.g., microphone 213, one or more accelerometers 268, touch-sensitive display system 212, one or more optical sensors 264, other input control devices 216, etc.). The digital assistant client module 229 is also capable of providing output in the form of audio (e.g., speech output), visual output, and / or tactile output through various output interfaces of the portable multifunction device 200 (e.g., speaker 211, touch-sensitive display system 212, one or more tactile output generators 267, etc.). For example, the output is provided as speech, sound, alarm, text message, menu, graphic, video, animation, vibration, and / or a combination of two or more of the above. During operation, the digital assistant client module 229 communicates with the DA server 106 using the RF circuit 208.

[0094] User data and models 231 include various data associated with the user (e.g., user-specific vocabulary data, user preference data, user-specified name pronunciations, data from the user's electronic address book, to-do items, shopping lists, etc.) to provide the client-side functionality of the digital assistant. In addition, user data and models 231 include various models for processing user input and determining user intent (e.g., speech recognition models, statistical language models, natural language processing models, knowledge ontologies, task flow models, service models, etc.).

[0095] In some examples, the digital assistant client module 229 utilizes the various sensors, subsystems, and peripherals of the portable multifunction device 200 to gather additional information from the environment surrounding the portable multifunction device 200 to establish a context associated with the user, the current user interaction, and / or the current user input. In some examples, the digital assistant client module 229 provides the context information, or a subset thereof, along with the user input to the DA server 106 to help infer user intent. In some examples, the digital assistant also uses the context information to determine how to prepare and transmit output to the user. The context information is referred to as context data.

[0096] In some examples, the contextual information accompanying the user input includes sensor information, such as lighting, ambient noise, ambient temperature, images or videos of the surrounding environment, etc. In some examples, the contextual information may also include the physical state of the device, such as device orientation, device location, device temperature, power level, speed, acceleration, motion pattern, cellular signal strength, etc. In some examples, information related to the software state of the DA server 106, such as the running process of the portable multifunction device 200, installed programs, past and current network activity, background services, error logs, resource usage, etc., is provided to the DA server 106 as contextual information associated with the user input.

[0097] In some examples, the digital assistant client module 229 selectively provides information stored on the portable multifunction device 200 (e.g., user data 231) in response to a request from the DA server 106. In some examples, the digital assistant client module 229 also elicits additional input from the user via a natural language dialog or other user interface upon request by the DA server 106. The digital assistant client module 229 transmits the additional input to the DA server 106 to assist the DA server 106 in inferring intent and / or fulfilling the user intent expressed in the user request.

[0098] Reference below 7A to 7C A more detailed description of the digital assistant is provided. It should be appreciated that the digital assistant client module 229 may include any number of submodules of the digital assistant module 726 described below.

[0099] The application 236 includes the following modules (or instruction sets) or a subset or superset thereof:

[0100] Contacts module 237 (sometimes called address book or contact list);

[0101] Telephone module 238;

[0102] Video conferencing module 239;

[0103] Email client module 240;

[0104] Instant messaging (IM) module 241;

[0105] Fitness support module 242;

[0106] A camera module 243 for still and / or video images;

[0107] Image management module 244;

[0108] Video player module;

[0109] Music player module;

[0110] Browser module 247;

[0111] Calendar module 248;

[0112] Widget module 249, which in some examples includes one or more of the following: weather widget 249-1, stock widget 249-2, calculator widget 249-3, alarm clock widget 249-4, dictionary widget 249-5, and other user-acquired widgets and user-created widgets 249-6;

[0113] A widget creator module 250 for forming user-created widgets 249-6;

[0114] Search module 251;

[0115] Video and music player module 252, which combines the video player module and the music player module;

[0116] Notepad module 253;

[0117] Map module 254; and / or

[0118] Online video module 255.

[0119] Examples of other applications 236 stored in memory 202 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice reproduction.

[0120] In combination with the touch screen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, the contacts module 237 is used to manage an address book or contact list (for example, stored in the application internal state 292 of the contacts module 237 in memory 202 or memory 470), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 238, video conferencing module 239, email 240 or IM 241; and so on.

[0121] 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, phone module 238 is used to enter a character sequence corresponding to a phone number, access one or more phone numbers in contacts module 237, modify an already entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communications use any of a variety of communication standards, protocols, and technologies.

[0122] In combination with the RF circuit 208, the audio circuit 210, the speaker 211, the microphone 213, the touch screen 212, the display controller 256, the optical sensor 264, the optical sensor controller 258, the touch / motion module 230, the graphics module 232, the text input module 234, the contact module 237 and the telephone module 238, the video conferencing module 239 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0123] In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact / motion module 230, graphics module 232, and text input module 234, email client module 240 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 244, email client module 240 makes it very easy to create and send emails with still images or video images captured by camera module 243.

[0124] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the contact / motion module 230, the graphics module 232, and the text input module 234, the instant messaging module 241 includes executable instructions for entering a character sequence corresponding to an instant message, modifying previously entered characters, transmitting the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages include graphics, photos, audio files, video files, and / or other attachments as supported in MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0125] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232, the text input module 234, the GPS module 235, the map module 254, and the music player module, the fitness support module 242 includes executable instructions for: creating a workout (e.g., with time, distance, and / or calorie burn goals); communicating with fitness sensors (exercise equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for a workout; and displaying, storing, and transmitting fitness data.

[0126] In combination with the touch screen 212, the display controller 256, one or more optical sensors 264, the optical sensor controller 258, the touch / motion module 230, the graphics module 232, and the image management module 244, the camera module 243 includes executable instructions for capturing still images or videos (including video streams) and storing them in the memory 202, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 202.

[0127] In conjunction with the touch screen 212, display controller 256, touch / motion module 230, graphics module 232, text input module 234, and camera module 243, the image management module 244 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0128] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232 and the text input module 234, the browser module 247 includes executable instructions for browsing the Internet in accordance with user instructions, including searching for, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0129] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232, the text input module 234, the email client module 240 and the browser module 247, the calendar module 248 includes executable instructions for creating, displaying, modifying and storing a calendar and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0130] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the contact / motion module 230, the graphics module 232, the text input module 234, and the browser module 247, the desktop widget module 249 is a mini-application that can be downloaded and used by a user (e.g., the weather desktop widget 249-1, the stock desktop widget 249-2, the calculator desktop widget 249-3, the alarm desktop widget 249-4, and the dictionary desktop widget 249-5) or a mini-application created by a user (e.g., the user-created desktop widget 249-6). In some embodiments, the desktop widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the desktop widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., the Yahoo! desktop widget).

[0131] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232, the text input module 234 and the browser module 247, the desktop widget creator module 250 is used by users to create desktop widgets (for example, to turn a user-specified portion of a web page into a desktop widget).

[0132] In combination with the touch screen 212, display controller 256, contact / motion module 230, graphics module 232 and text input module 234, the search module 251 includes executable instructions for searching the memory 202 for text, music, sound, images, videos and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

[0133] 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 a 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), as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 212 or on an external display connected 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.).

[0134] In conjunction with the touch screen 212, display controller 256, contact / motion module 230, graphics module 232 and text input module 234, the notepad module 253 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

[0135] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232, the text input module 234, the GPS module 235 and the browser module 247, the map module 254 is used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions, data related to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0136] In conjunction with the touch screen 212, display controller 256, contact / motion module 230, graphics module 232, audio circuit 210, speaker 211, RF circuit 208, text input module 234, email client module 240, and browser module 247, the online video module 255 includes instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on the touch screen or on a connected external display via external port 224), send an email with a link to a particular online video, and otherwise manage online videos in one or more file formats (e.g., H.264). In some embodiments, the instant messaging module 241 is used instead of the email client module 240 to send a link to a particular online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0137] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, a video player module may be combined with a music player module into a single module (e.g., Figure 2AIn some embodiments, the memory 202 stores a subset of the above modules and data structures. In addition, the memory 202 stores additional modules and data structures not described above.

[0138] In some embodiments, the device 200 is a device in which the operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touch pad. By using the touch screen and / or the touch pad as the primary input control device for the operation of the device 200, the number of physical input control devices (such as push buttons, dials, etc.) on the device 200 is reduced.

[0139] A predefined set of functions that are exclusively performed through the touch screen and / or trackpad optionally includes navigation between user interfaces. In some embodiments, the trackpad, when touched by the user, navigates the device 200 from any user interface displayed on the device 200 to a main menu, home menu, or root menu. In such embodiments, the trackpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a trackpad.

[0140] Figure 2B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 202 ( Figure 2A ) or memory 470( Figure 4 ) includes an event classifier 270 (e.g., in the operating system 226) and a corresponding application 236-1 (e.g., any one of the aforementioned applications 237 to 251, 255, 480 to 490).

[0141] The event classifier 270 receives event information and determines the application 236-1 and the application view 291 of the application 236-1 to which the event information is to be delivered. The event classifier 270 includes an event monitor 271 and an event dispatcher module 274. In some embodiments, the application 236-1 includes an application internal state 292 that indicates one or more current application views that are displayed on the touch-sensitive display 212 when the application is active or executing. In some embodiments, the device / global internal state 257 is used by the event classifier 270 to determine which application(s) are currently active, and the application internal state 292 is used by the event classifier 270 to determine the application view 291 to which the event information is to be delivered.

[0142] In some embodiments, the application internal state 292 includes additional information, such as one or more of the following: resumption information to be used when the application 236-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed by the application 236-1, a state queue for enabling the user to return to a previous state or view of the application 236-1, and a repeat / undo queue of previous actions taken by the user.

[0143] Event monitor 271 receives event information from peripherals interface 218. The event information includes information about sub-events (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 sensors such as proximity sensor 266, one or more accelerometers 268, and / or microphone 213 (through audio circuit 210). The information that peripherals interface 218 receives from I / O subsystem 206 includes information from touch-sensitive display 212 or a touch-sensitive surface.

[0144] In some embodiments, event monitor 271 sends requests to peripheral device interface 218 at predetermined intervals. In response, peripheral device interface 218 transmits event information. In other embodiments, peripheral device interface 218 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or receiving an input for more than a predetermined duration).

[0145] In some embodiments, the event classifier 270 also includes a hit view determination module 272 and / or an active event identifier determination module 273.

[0146] When the touch-sensitive display 212 displays more than one view, the hit view determination module 272 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.

[0147] Another aspect of the user interface associated with an application is a set of views, sometimes also referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of the respective application) in which a touch is detected correspond to a programmatic hierarchy of the application or a programmatic level within the view hierarchy. For example, the lowest-level view in which a touch is detected is called a hit view, and the set of events that are considered to be valid input is determined at least in part based on the hit view of the initial touch that started the touch-based gesture.

[0148] Hit view determination module 272 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 272 identifies the hit view as the lowest view in the hierarchy where the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by 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.

[0149] Active event recognizer determination module 273 determines which view or views within the 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 the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, views higher in the hierarchy will still remain actively participating views.

[0150] Event dispatcher module 274 dispatches event information to event recognizers (e.g., event recognizer 280). In embodiments that include active event recognizer determination module 273, event dispatcher module 274 delivers the event information to the event recognizer determined by active event recognizer determination module 273. In some embodiments, event dispatcher module 274 stores the event information in an event queue, which is retrieved by corresponding event receiver 282.

[0151] In some embodiments, operating system 226 includes event classifier 270. Alternatively, application 236-1 includes event classifier 270. In yet another embodiment, event classifier 270 is a standalone module or part of another module stored in memory 202, such as contact / motion module 230.

[0152] In some embodiments, application 236-1 includes multiple event handlers 290 and one or more application views 291, each of which includes instructions for handling touch events that occur within a corresponding view of the application's user interface. Each application view 291 of application 236-1 includes one or more event recognizers 280. Typically, the corresponding application view 291 includes multiple event recognizers 280. In other embodiments, one or more of the event recognizers 280 are part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 236-1 inherits methods and other properties. In some embodiments, the corresponding event handler 290 includes one or more of the following: a data updater 276, an object updater 277, a GUI updater 278, and / or event data 279 received from an event classifier 270. The event handler 290 utilizes or calls the data updater 276, the object updater 277, or the GUI updater 278 to update the application's internal state 292. Alternatively, one or more of the application views in the application views 291 include one or more corresponding event handlers 290. Additionally, in some embodiments, one or more of the data updater 276, object updater 277, and GUI updater 278 are included in the corresponding application view 291.

[0153] A corresponding event identifier 280 receives event information (e.g., event data 279) from event classifier 270 and identifies an event from the event information. Event identifier 280 includes an event receiver 282 and an event comparator 284. In some embodiments, event identifier 280 also includes metadata 283 and at least a subset of event delivery instructions 288 (which includes sub-event delivery instructions).

[0154] The event receiver 282 receives event information from the event classifier 270. The event information includes information about sub-events such as touches or touch movements. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (for example, from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0155] The event comparator 284 compares the event information with a predefined event or sub-event definition and, based on the comparison, determines the event or sub-event, or determines or updates the state of the event or sub-event. In some embodiments, the event comparator 284 includes an event definition 286. The event definition 286 includes a definition of an event (e.g., a predefined sequence of sub-events), such as event 1 (287-1), event 2 (287-2), and other events. In some embodiments, the sub-events in event (287) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (287-1) is a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (287-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 212, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 290.

[0156] In some embodiments, event definition 287 includes definitions of events for corresponding user interface objects. 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 displaying three user interface objects 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 corresponding 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 that is associated with the sub-event and the object that triggered the hit test.

[0157] In some embodiments, the definition of the corresponding event (287) also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

[0158] When a corresponding event recognizer 280 determines that a sub-event sequence does not match any event in event definitions 286, the corresponding event recognizer 280 enters the event not possible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0159] In some embodiments, the corresponding event recognizer 280 includes metadata 283 having configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery for actively participating event recognizers. In some embodiments, metadata 283 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 283 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0160] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 280 activates the event handler 290 associated with the event. In some embodiments, the corresponding event recognizer 280 delivers event information associated with the event to the event handler 290. Activating the event handler 290 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 280 throws a flag associated with the identified event, and the event handler 290 associated with the flag obtains the flag and performs a predefined process.

[0161] 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 the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with the actively participating view receives the event information and performs a predetermined process.

[0162] In some embodiments, data updater 276 creates and updates data used in application 236-1. For example, data updater 276 updates phone numbers used in contact module 237 or stores video files 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 new user interface objects or updates the position of user interface objects. GUI updater 278 updates the GUI. For example, GUI updater 278 prepares display information and sends the display information to graphics module 232 for display on a touch-sensitive display.

[0163] In some embodiments, event handler 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 the corresponding application 236-1 or application view 291. In other embodiments, they are included in two or more software modules.

[0164] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input utilizing input devices to operate the multifunction device 200, and not all user input is initiated on a touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a trackpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken commands; detected eye movement; biometric input; and / or any combination thereof, are optionally used as input corresponding to sub-events defining the event to be recognized.

[0165] Figure 3A portable multifunction device 200 with a touch screen 212 is shown according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 300. In this embodiment and other embodiments described below, a user can select one or more of the graphics by, for example, making gestures on the graphics using 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 the 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, from right to left, up and / or down), and / or rolling of the finger that has made contact with the device 200 (from right to left, from left to right, up and / or down). In some embodiments or in some cases, 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.

[0166] The device 200 also includes one or more physical buttons, such as a "home" or menu button 304. As previously described, the menu button 304 is used to navigate to any application 236 in a set of applications executing on the device 200. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 212.

[0167] In some embodiments, the device 200 includes a touch screen 212, a menu button 304, a push button 306 for powering the device on / off and for locking the device, one or more volume adjustment buttons 308, a subscriber identity module (SIM) card slot 310, a headset jack 312, and a docking / charging external port 224. The push button 306 is optionally used to turn the device on / off by pressing the button and holding it in the depressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In an alternative embodiment, the device 200 also accepts speech input for activating or deactivating certain functions via the microphone 213. The device 200 also optionally includes one or more contact force sensors 265 for detecting the intensity of contact on the touch screen 212, and / or one or more tactile output generators 267 for generating tactile output for the user of the device 200.

[0168] Figure 44 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 400 does not have to be portable. In some embodiments, the 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 children's learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). The device 400 typically includes one or more processing units (CPUs) 410, one or more network or other communication interfaces 460, a memory 470, and one or more communication buses 420 for interconnecting these components. The communication bus 420 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. The device 400 includes an input / output (I / O) interface 430 with a display 440, which is typically a touch screen display. The I / O interface 430 also optionally includes a keyboard and / or mouse (or other pointing device) 450 and a touchpad 455, a tactile output generator 457 for generating tactile output on the device 400 (e.g., similar to the above referenced device). Figure 2A The one or more tactile output generators 267 described above), sensors 459 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensors, and / or contact intensity sensors (similar to those described above with reference to Figure 2A The one or more contact intensity sensors 265 described herein)). 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 located remotely from CPU 410. In some embodiments, memory 470 stores data related to portable multifunction device 200 ( Figure 2A ) or a subset thereof. In addition, 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 a drawing module 480, a presentation module 482, a word processing module 484, a website creation module 486, a disk editing module 488, and / or a spreadsheet module 490, while portable multifunction device 200( Figure 2A )'s memory 202 optionally does not store these modules.

[0169] Figure 4Each of the above-mentioned elements in some examples is stored in one or more previously mentioned memory devices. Each module in the above-mentioned modules corresponds to an instruction set for performing the above-mentioned functions. The above-mentioned modules or programs (e.g., instruction sets) do not have to be implemented as independent software programs, processes or modules, so the various subsets of these modules are combined or otherwise rearranged in various embodiments. In some embodiments, memory 470 stores a subset of the above-mentioned modules and data structures. In addition, memory 470 stores additional modules and data structures not described above.

[0170] Attention is now turned to embodiments of a user interface that may be implemented on, for example, portable multifunction device 200 .

[0171] Figure 5A An exemplary user interface for an applications menu on portable multifunction device 200 is shown according to some embodiments. A similar user interface is implemented on device 400. In some embodiments, user interface 500 includes the following elements, or a subset or superset thereof:

[0172] one or more signal strength indicators 502 of one or more wireless communications such as cellular signals and Wi-Fi signals;

[0173] Time 504;

[0174] Bluetooth indicator 505;

[0175] Battery status indicator 506;

[0176] A tray 508 with icons for commonly used applications, such as:

[0177] o An icon 516 labeled "Phone" for the phone module 238, which optionally includes an indicator 514 of the number of missed calls or voice messages;

[0178] o An icon 518 labeled "Mail" of the email client module 240, which optionally includes an indicator 510 of the number of unread emails;

[0179] o An icon 520 labeled "Browser" for the browser module 247; and

[0180] o An icon 522 labeled “iPod” for the video and music player module 252 (also referred to as the iPod (trademark of Apple Inc.) module 252); and

[0181] Icons for other apps, such as:

[0182] o Icon 524 labeled "Messages" of the IM module 241;

[0183] o Icon 526 labeled "Calendar" of the calendar module 248;

[0184] o Icon 528 labeled "Photos" of the image management module 244;

[0185] o An icon 530 labeled “Camera” of the camera module 243;

[0186] ○ Icon 532 labeled “Online Video” of the online video module 255;

[0187] ○ Icon 534 labeled “Stock Market” of the Stock Market widget 249-2;

[0188] o Icon 536 labeled "Map" of the map module 254;

[0189] ○ Icon 538 labeled “Weather” of weather widget 249-1;

[0190] ○ Icon 540 labeled “Clock” of the alarm clock widget 249-4;

[0191] o An icon 542 labeled “Fitness Support” of the fitness support module 242;

[0192] o An icon 544 labeled "Notepad" of the Notepad module 253; and

[0193] o An icon 546 labeled “Settings” for a settings application or module that provides access to settings for the device 200 and its various applications 236 .

[0194] It should be pointed out that Figure 5A The icon labels shown in are merely exemplary. For example, icon 522 for video and music player module 252 is optionally labeled "Music" or "Music Player." Other labels are optionally used for various application icons. In some embodiments, the label of a respective application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0195] Figure 5B A touch-sensitive surface 551 (eg, touch screen display 212) is shown having a touch-sensitive surface 551 (eg, touch screen display 212) that is separate from a display 550 (eg, touch screen display 212). Figure 4 tablet or touchpad 455) of the device (e.g., Figure 4Device 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 output for a user of device 400.

[0196] Although some of the examples that follow will be given with reference to input on a touch screen display 212 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 5B In some embodiments, the touch-sensitive surface (e.g., Figure 5B 551) has a main axis (e.g., Figure 5B 553) corresponding to the main axis (for example, Figure 5B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 5B , 560 corresponds to 568 and 562 corresponds to 570 ) at contact with touch-sensitive surface 551 (e.g., Figure 5B 560 and 562 in ). Thus, on a touch-sensitive surface (e.g., Figure 5B 551) and a display of a multi-function device (e.g., Figure 5B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 560 and 562 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0197] In addition, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). For another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting the contact, followed by ceasing to detect the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mice and finger contacts are optionally used simultaneously.

[0198] Figure 6AAn exemplary personal electronic device 600 is shown. The device 600 includes a body 602. In some embodiments, the device 600 includes a body 602 relative to the devices 200 and 400 (e.g., Figures 2A-4 ) some or all of the features described in . In some embodiments, device 600 has a touch-sensitive display screen 604, referred to hereinafter as touch screen 604. As an alternative to or in addition to touch screen 604, device 600 has a display and a touch-sensitive surface. As is the case with devices 200 and 400, in some embodiments, touch screen 604 (or touch-sensitive surface) has one or more intensity sensors for detecting the intensity of contact (e.g., a touch) being applied. The one or more intensity sensors of touch screen 604 (or touch-sensitive surface) provide output data representing the intensity of the touch. The user interface of device 600 responds to touches based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 600.

[0199] Technology for detecting and processing touch intensity may be found, for example, in related applications: International patent application serial number PCT / US2013 / 040061, entitled “Device, Method, and Graphical User Interface for Displaying UserInterface Objects Corresponding to an Application,” filed on May 8, 2013, and International patent application serial number PCT / US2013 / 069483, entitled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed on November 11, 2013, each of which is hereby incorporated by reference in its entirety.

[0200] In some embodiments, the device 600 has one or more input mechanisms 606 and 608. Input mechanisms 606 and 608 (if included) are physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 600 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 600 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, wristbands, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 600.

[0201] Figure 6BAn exemplary personal electronic device 600 is shown. In some embodiments, the device 600 includes information about Figure 2A 、 Figure 2B and Figure 4 Some or all of the components described. The device 600 has a bus 612 that operatively couples an I / O portion 614 to one or more computer processors 616 and a memory 618. The I / O portion 614 is connected to a display 604, which may have a touch-sensitive component 622 and, optionally, a touch intensity-sensitive component 624. In addition, the I / O portion 614 is connected to a communication unit 630 for receiving application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication technologies. The device 600 includes input mechanisms 606 and / or 608. For example, the input mechanism 606 is a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 608 is a button.

[0202] In some examples, input mechanism 608 is a microphone. Personal electronic device 600 includes, for example, various sensors such as a GPS sensor 632, an accelerometer 634, an orientation sensor 640 (e.g., a compass), a gyroscope 636, a motion sensor 638, and / or combinations thereof, all of which are operatively connected to I / O portion 614.

[0203] The memory 618 of the personal electronic device 600 is a non-transitory computer-readable storage medium for storing computer-executable instructions that, when executed by one or more computer processors 616, cause the computer processors to perform the techniques and processes described above. The computer-executable instructions are also stored and / or transmitted, for example, within any non-transitory computer-readable storage medium for use by or in conjunction with an instruction execution system, apparatus, or device, such as a computer-based system, a system containing a processor, or other system that can obtain instructions from an instruction execution system, apparatus, or device and execute the instructions. The personal electronic device 600 is not limited to Figure 6B components and configurations, but may include other components or additional components in a variety of configurations.

[0204] As used herein, the term "indicator" refers to, for example, a display on device 200, 400, and / or 600 ( Figure 2A 、 Figure 4 and Figures 6A to 6B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) each constitute an affordance.

[0205] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 4 Touchpad 455 or Figure 5B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 551 in FIG, the particular user interface element is adjusted according to the detected input. In the case of a touch screen display (e.g., a touch screen display) that enables direct interaction with user interface elements on the touch screen display Figure 2A touch-sensitive display system 212 or Figure 5A In some implementations of the touch screen 212 in FIG, 20 , a contact detected on the touch screen acts as a “focus selector” such that when input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted according to the detected input. In some implementations, the focus moves from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves according to the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a trackpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0206] 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 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact begins to move, before contact ends, before or after contact is detected to increase in intensity, and / or before or after contact is detected to decrease in intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half-maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation), rather than to determine whether to perform the first operation or the second operation.

[0207] In some embodiments, a portion of a gesture is identified for use in determining the characteristic strength. For example, a touch-sensitive surface receives a continuous swipe contact that transitions from a starting position and reaches an ending position where the strength of the contact increases. In this example, the characteristic strength of the contact at the ending position is based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., the portion of the swipe contact that is located only at the ending position). In some embodiments, a smoothing algorithm is applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or dips in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

[0208] The intensity of a contact on the touch-sensitive surface is 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 an operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or 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, contacts below the nominal contact detection intensity threshold are no longer detected), the device will move the focus selector in accordance with the 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 speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface illustrations.

[0209] An increase in contact feature intensity from an intensity below a 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 in contact feature intensity from an intensity below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below a 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 a contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact lifted 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.

[0210] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting an increase in the intensity of the contact (or multiple contacts) to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in the intensity of the corresponding contact to above the press input intensity threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below the press input intensity threshold, and the corresponding operation is performed in response to detecting a subsequent decrease in the intensity of the corresponding contact to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0211] In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs, sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a 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, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and, optionally, that the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the circumstances).

[0212] For ease of explanation, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input is optionally triggered in response to detecting any of the following: contact intensity increasing above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing below the press input intensity threshold, and / or contact intensity decreasing below a 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 that the intensity of the contact decreases below the press input intensity threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0213] 3. Digital Assistant System

[0214] Figure 7A A block diagram of a digital assistant system 700 according to various examples is shown. In some examples, the digital assistant system 700 is implemented on a stand-alone computer system. In some examples, the digital assistant system 700 is distributed across multiple computers. In some examples, some of the modules and functions of the digital assistant are divided into a server portion and a client portion, where the client portion is located on one or more user devices (e.g., device 104, device 122, device 200, device 400, or device 600) and communicates with the server portion (e.g., server system 108) over one or more networks, such as Figure 1 In some examples, the digital assistant system 700 is Figure 1 It should be noted that the digital assistant system 700 is only one example of a digital assistant system, and that the digital assistant system 700 may have more or fewer components than shown, combine two or more components, or have a different configuration or arrangement of components. Figure 7A The various components shown in the drawings are implemented in hardware, software instructions for execution by one or more processors, firmware (including one or more signal processing integrated circuits and / or application specific integrated circuits), or a combination thereof.

[0215] The digital assistant system 700 includes a memory 702, an input / output (I / O) interface 706, a network communication interface 708, and one or more processors 704. These components can communicate with each other via one or more communication buses or signal lines 710.

[0216] In some examples, memory 702 includes non-transitory computer-readable media, such as high-speed random access memory and / or non-volatile computer-readable storage media (e.g., one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices).

[0217] In some examples, the I / O interface 706 couples the input / output devices 716 of the digital assistant system 700, such as a display, keyboard, touch screen, and microphone, to the user interface module 722. The I / O interface 706, together with the user interface module 722, receives user input (e.g., voice input, keyboard input, touch input, etc.) and processes the input accordingly. In some examples, such as when the digital assistant is implemented on a stand-alone user device, the digital assistant system 700 includes a plurality of interfaces with respect to the user interface module 722. Figure 2A 、 Figure 4 、 Figures 6A to 6B In some examples, digital assistant system 700 represents the server portion of a digital assistant implementation and can interact with a user through a client-side portion located on a user device (e.g., device 104, device 200, device 400, or device 600).

[0218] In some examples, the network communication interface 708 includes one or more wired communication ports 712 and / or wireless transmission and reception circuitry 714. The one or more wired communication ports receive and send communication signals via one or more wired interfaces such as Ethernet, Universal Serial Bus (USB), FIREWIRE, etc. The wireless circuitry 714 receives RF signals and / or optical signals from a communication network and other communication devices and sends RF signals and / or optical signals to a communication network and other communication devices. Wireless communication uses any of a variety of communication standards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA, Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communication protocol. The network communication interface 708 enables communication between the digital assistant system 700 and other devices over a network, 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).

[0219] In some examples, the memory 702 or the computer-readable storage medium of the memory 702 stores programs, modules, instructions, and data structures, including all or a subset of the following: operating system 718, communication module 720, user interface module 722, one or more application programs 724, and digital assistant module 726. Specifically, the memory 702 or the computer-readable storage medium of the memory 702 stores instructions for performing the above-described processes. The one or more processors 704 execute these programs, modules, and instructions and read data from or write data to the data structures.

[0220] The operating system 718 (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OS X, 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, firmware, and software components.

[0221] The communication module 720 facilitates communication between the digital assistant system 700 and other devices via the network communication interface 708. For example, the communication module 720 facilitates communication between the digital assistant system 700 and other devices (such as Figure 2A 、 Figure 4 、 Figures 6A to 6B The communication module 720 also includes various components for processing data received by the wireless circuit 714 and / or the wired communication port 712.

[0222] The user interface module 722 receives commands and / or input from the user (e.g., from a keyboard, touch screen, pointing device, controller, and / or microphone) via the I / O interface 706 and generates user interface objects on the display. The user interface module 722 also prepares output (e.g., speech, sound, animation, text, icons, vibration, tactile feedback, lighting, etc.) and transmits it to the user via the I / O interface 706 (e.g., through a display, audio channel, speaker, touchpad, etc.).

[0223] Applications 724 include programs and / or modules configured to be executed by the one or more processors 704. For example, if the digital assistant system is implemented on a standalone user device, applications 724 include user applications such as games, calendar applications, navigation applications, or email applications. If the digital assistant system 700 is implemented on a server, applications 724 include, for example, resource management applications, diagnostic applications, or scheduling applications.

[0224] The memory 702 also stores a digital assistant module 726 (or the server portion of the digital assistant). In some examples, the digital assistant module 726 includes the following submodules, or subsets or supersets thereof: an input / output processing module 728, a speech-to-text (STT) processing module 730, a natural language processing module 732, a dialog flow processing module 734, a task flow processing module 736, a service processing module 738, and a speech synthesis processing module 740. Each of these modules has access to one or more of the following systems or data and models of the digital assistant module 726, or subsets or supersets thereof: a knowledge ontology 760, a vocabulary index 744, user data 748, a task flow model 754, a service model 756, and an ASR system 758.

[0225] In some examples, using the processing modules, data, and models implemented in the digital assistant module 726, the digital assistant may perform at least some of the following: convert speech input into text; recognize user intent expressed in natural language input received from the user; proactively elicit and obtain information needed to fully infer user intent (e.g., by disambiguating words, games, intents, etc.); determine a task flow for satisfying the inferred intent; and execute the task flow to satisfy the inferred intent.

[0226] In some examples, such as Figure 7B As shown in FIG, the I / O processing module 728 can be Figure 7A The I / O devices 716 in the system interact with the user or through Figure 7AThe network communication interface 708 in interacts with a user device (e.g., device 104, device 200, device 400, or device 600) to obtain user input (e.g., voice input) and provide a response to the user input (e.g., as voice output). The I / O processing module 728 optionally obtains context information associated with the user input from the user device along with or shortly after receiving the user input. The context information includes user-specific data, vocabulary, and / or preferences related to the user input. In some examples, the context information also includes the software state and hardware state of the user device at the time the user request is received, and / or information related to the user's surrounding environment at the time the user request is received. In some examples, the I / O processing module 728 also sends follow-up questions related to the user request to the user and receives answers from the user. When the user request is received by the I / O processing module 728 and the user request includes voice input, the I / O processing module 728 forwards the voice input to the STT processing module 730 (or speech recognizer) for speech-to-text conversion.

[0227] The STT processing module 730 includes one or more ASR systems 758. The one or more ASR systems 758 can process the speech input received by the I / O processing module 728 to generate recognition results. Each ASR system 758 includes a front-end speech preprocessor. The front-end speech preprocessor extracts representative features from the speech input. For example, the front-end speech preprocessor performs a Fourier transform on the speech input to extract spectral features that characterize the speech input as a sequence of representative multidimensional vectors. In addition, each ASR system 758 includes one or more speech recognition models (e.g., acoustic models and / or language models) and implements one or more speech recognition engines. Examples of speech recognition models include hidden Markov models, Gaussian mixture models, deep neural network models, n-gram language models, and other statistical models. Examples of speech recognition engines include engines based on dynamic time warping and engines based on weighted finite state transformers (WFST). One or more speech recognition models and one or more speech recognition engines are used to process the extracted representative features of the front-end speech preprocessor to produce intermediate recognition results (e.g., phonemes, phoneme strings, and sub-words), and ultimately produce text recognition results (e.g., words, word strings, or symbol sequences). In some examples, the voice input is at least partially processed by a third-party service or processed on the user's device (e.g., device 104, device 200, device 400, or device 600) to produce recognition results. Once the STT processing module 730 generates a recognition result containing a text string (e.g., a word, or a sequence of words, or a sequence of symbols), the recognition result is transmitted to the natural language processing module 732 for intention inference. In some examples, the STT processing module 730 generates multiple candidate text representations of the voice input. Each candidate text representation is a sequence of words or symbols corresponding to the voice input. In some examples, each candidate text representation is associated with a voice recognition confidence score. Based on the speech recognition confidence score, the STT processing module 730 ranks the candidate text representations and provides the n best (e.g., the n highest ranked) candidate text representations to the natural language processing module 732 for intent inference, where n is a predetermined integer greater than zero. For example, in one example, only the highest ranked (n=1) candidate text representation is delivered to the natural language processing module 732 for intent inference. For another example, the five highest ranked (n=5) candidate text representations are delivered to the natural language processing module 732 for intent inference.

[0228] More details regarding speech-to-text processing are described in U.S. Utility Patent Application Serial No. 13 / 236,942, filed on September 20, 2011, entitled “Consolidating Speech Recognition Results,” the entire disclosure of which is incorporated herein by reference.

[0229] In some examples, the STT processing module 730 includes a vocabulary of recognizable words and / or accesses the vocabulary via the phonetic alphabet conversion module 731. Each vocabulary word is associated with one or more candidate pronunciations of the word represented in the speech recognition phonetic alphabet. Specifically, the vocabulary of recognizable words includes words associated with multiple candidate pronunciations. For example, the vocabulary includes words associated with and In some examples, the candidate pronunciations for a word are determined based on the spelling of the word and one or more linguistic and / or phonetic rules. In some examples, the candidate pronunciations are manually generated, for example, based on a known standard pronunciation.

[0230] In some examples, candidate pronunciations are ranked based on their prevalence. For example, Ranked higher than Because the former is the more common pronunciation (e.g., among all users, for users in a particular geographic region, or for any other suitable subset of users). In some examples, candidate pronunciations are ranked based on whether they are custom candidate pronunciations associated with the user. For example, custom candidate pronunciations are ranked higher than standard candidate pronunciations. This can be used to identify proper nouns that have unique pronunciations that deviate from the standard pronunciation. In some examples, candidate pronunciations are associated with one or more phonetic features such as geographic origin, country, or ethnicity. For example, a candidate pronunciation associated with the United States, while the candidate pronunciation Associated with the United Kingdom. In addition, the ranking of the candidate pronunciations is based on one or more characteristics of the user (e.g., geographic origin, country, race, etc.) in a user profile stored on the device. For example, it may be determined from the user profile that the user is associated with the United States. Based on the user being associated with the United States, the candidate pronunciations are ranked (Associated with the United States) Comparable candidate pronunciations (associated with the United Kingdom) is ranked higher. In some examples, one of the ranked candidate pronunciations may be selected as the predicted pronunciation (e.g., the most likely pronunciation).

[0231] When speech input is received, the STT processing module 730 is used to determine (e.g., using an acoustic model) a phoneme corresponding to the speech input and then attempts to determine (e.g., using a language model) a word that matches the phoneme. For example, if the STT processing module 730 first identifies a phoneme sequence corresponding to a portion of the speech input It may then determine based on the lexical index 744 that the sequence corresponds to the word "tomato".

[0232] In some examples, the STT processing module 730 uses fuzzy matching techniques to determine words in an utterance. Thus, for example, the STT processing module 730 determines the phoneme sequence corresponds to the word "tomato", even though this particular phoneme sequence is not a candidate phoneme sequence for that word.

[0233] The digital assistant's natural language processing module 732 ("natural language processor") takes the n best candidate text representations ("word sequences" or "symbol sequences") generated by the STT processing module 730 and attempts to associate each candidate text representation with one or more "executable intents" recognized by the digital assistant. An "executable intent" (or "user intent") represents a task that can be executed by the digital assistant and that can have an associated task flow implemented in the task flow model 754. The associated task flow is a series of programmed actions and steps that the digital assistant takes to perform the task. The scope of the digital assistant's capabilities depends on the number and variety of task flows that have been implemented and stored in the task flow model 754, or in other words, on the number and variety of "executable intents" recognized by the digital assistant. However, the effectiveness of the digital assistant also depends on the assistant's ability to infer the correct "one or more executable intents" from user requests expressed in natural language.

[0234] In some examples, in addition to the sequence of words or symbols obtained from the STT processing module 730, the natural language processing module 732 also receives contextual information associated with the user request, for example, from the I / O processing module 728. The natural language processing module 732 optionally uses the contextual information to clarify, supplement, and / or further qualify the information included in the candidate text representation received from the STT processing module 730. The contextual information includes, for example, user preferences, the hardware and / or software state of the user's device, sensor information collected before, during, or shortly after the user's request, previous interactions (e.g., conversations) between the digital assistant and the user, and the like. As described herein, in some examples, the contextual information is dynamic and changes with the time, location, content, and other factors of the conversation.

[0235] In some examples, natural language processing is based on, for example, a knowledge ontology 760. The knowledge ontology 760 is a hierarchical structure comprising many nodes, each node representing an "executable intent" or an "attribute" related to one or more of an "executable intent" or other "attributes". As described above, an "executable intent" represents a task that the digital assistant can perform, that is, the task is "executable" or can be performed. An "attribute" represents a parameter associated with a sub-aspect of an executable intent or another attribute. The connection between the executable intent node and the attribute node in the knowledge ontology 760 defines how the parameters represented by the attribute node are subordinate to the task represented by the executable intent node.

[0236] In some examples, the knowledge ontology 760 is composed of executable intent nodes and attribute nodes. Within the knowledge ontology 760, each executable intent node is directly connected to or connected to one or more attribute nodes through one or more intermediate attribute nodes. Similarly, each attribute node is directly connected to or connected to one or more executable intent nodes through one or more intermediate attribute nodes. For example, Figure 7C As shown, the knowledge ontology 760 includes a "restaurant reservation" node (i.e., an executable intent node). The attribute nodes "restaurant", "date / time" (for reservations), and "party size" are all directly connected to the executable intent node (i.e., the "restaurant reservation" node).

[0237] In addition, the attribute nodes "cuisine", "price range", "telephone number" and "location" are child nodes of the attribute node "restaurant", and are all connected to the "restaurant reservation" node (i.e., executable intent node) through the intermediate attribute node "restaurant". Figure 7C As shown, ontology 760 also includes a "Set Reminder" node (i.e., another executable intent node). The attribute nodes "Date / Time" (for setting reminders) and "Subject" (for reminders) are both connected to the "Set Reminder" node. Since the attribute "Date / Time" is related to both the task of making a restaurant reservation and the task of setting a reminder, the attribute node "Date / Time" is connected to both the "Restaurant Reservation" node and the "Set Reminder" node in ontology 760.

[0238] Executable intent nodes, along with their linked attribute nodes, are described as "domains". In this discussion, each domain is associated with a corresponding executable intent and refers to a set of nodes (and the relationships between these nodes) associated with a particular executable intent. For example, Figure 7CThe knowledge ontology 760 shown in includes an example of a restaurant reservation domain 762 and an example of a reminder domain 764 within the knowledge ontology 760. The restaurant reservation domain includes an executable intent node "restaurant reservation", attribute nodes "restaurant", "date / time" and "party size", and child attribute nodes "cuisine", "price range", "phone number" and "location". The reminder domain 764 includes an executable intent node "set reminder" and attribute nodes "subject" and "date / time". In some examples, the knowledge ontology 760 is composed of multiple domains. Each domain shares one or more attribute nodes with one or more other domains. For example, in addition to the restaurant reservation domain 762 and the reminder domain 764, the "date / time" attribute node is also associated with many different domains (e.g., a scheduling domain, a travel booking domain, a movie ticket domain, etc.).

[0239] although Figure 7C Two exemplary domains within the knowledge ontology 760 are shown, but other domains include, for example, "find a movie," "make a phone call," "find directions," "schedule a meeting," "send a message," and "provide answers to questions," "read a list," "provide navigation instructions," "provide instructions for a task," and the like. The "send message" domain is associated with the "send message" executable intent node and further includes attribute nodes such as "one or more recipients," "message type," and "message body." The attribute node "recipients" is further defined by, for example, child attribute nodes such as "recipient name" and "message address."

[0240] In some examples, ontology 760 includes all domains (and thus executable intents) that the digital assistant can understand and act upon. In some examples, ontology 760 is modified, such as by adding or removing entire domains or nodes, or by modifying the relationships between nodes within ontology 760.

[0241] In some examples, nodes associated with multiple related executable intents are clustered under a "superdomain" in the knowledge ontology 760. For example, the "travel" superdomain includes a cluster of attribute nodes and executable intent nodes related to travel. The executable intent nodes related to travel include "flight booking", "hotel booking", "car rental", "route planning", "find points of interest", etc. The executable intent nodes under the same superdomain (e.g., the "travel" superdomain) have multiple common attribute nodes. For example, the executable intent nodes for "flight booking", "hotel booking", "car rental", "get directions", and "find points of interest" share one or more of the attribute nodes "starting location", "destination", "departure date / time", "arrival date / time", and "party size".

[0242] In some examples, each node in the knowledge ontology 760 is associated with a set of words and / or phrases related to the attribute or executable intent represented by the node. The corresponding set of words and / or phrases associated with each node is called the "vocabulary" associated with the node. The corresponding set of words and / or phrases associated with each node is stored in the vocabulary index 744 associated with the attribute or executable intent represented by the node. For example, return Figure 7B For example, the vocabulary associated with the node for the "restaurant" attribute includes words such as "food," "drinks," "cuisine," "hunger," "eat," "pizza," "fast food," "meal," etc. For another example, the vocabulary associated with the node for the "make phone call" executable intent includes words and phrases such as "call," "make a phone call," "dial," "talk to," "call the number," "call," etc. The vocabulary index 744 optionally includes words and phrases in different languages.

[0243] The natural language processing module 732 receives candidate text representations (e.g., one or more text strings or one or more symbol sequences) from the STT processing module 730 and, for each candidate representation, determines which nodes the words in the candidate text representation refer to. In some examples, if a word or phrase in the candidate text representation is found (via the vocabulary index 744) to be associated with one or more nodes in the knowledge ontology 760, the word or phrase "triggers" or "activates" those nodes. Based on the number and / or relative importance of the activated nodes, the natural language processing module 732 selects one of the executable intents as the task that the user intends the digital assistant to perform. In some examples, the domain with the most "triggered" nodes is selected. In some examples, the domain with the highest confidence (e.g., based on the relative importance of its various triggered nodes) is selected. In some examples, the domain is selected based on a combination of the number and importance of the triggered nodes. In some examples, additional factors are also considered in the process of selecting the node, such as whether the digital assistant has previously correctly interpreted a similar request from the user.

[0244] User data 748 includes user-specific information such as user-specific vocabulary, user preferences, user address, user's default second language, user's contact list, and other short-term or long-term information about each user. In some examples, natural language processing module 732 uses user-specific information to supplement the information contained in the user input to further define the user's intent. For example, in response to a user request to "invite my friends to my birthday party," natural language processing module 732 can access user data 748 to determine who "friends" are and when and where the "birthday party" will be held, without requiring the user to explicitly provide such information in their request.

[0245] It should be recognized that in some examples, the natural language processing module 732 is implemented using one or more machine learning mechanisms (e.g., neural networks). Specifically, the one or more machine learning mechanisms are configured to receive candidate text representations and context information associated with the candidate text representations. Based on the candidate text representations and the associated context information, the one or more machine learning mechanisms are configured to determine an intent confidence score based on a set of candidate executable intents. The natural language processing module 732 may select one or more candidate executable intents from a set of candidate executable intents based on the determined intent confidence scores. In some examples, a knowledge ontology (e.g., knowledge ontology 760) is also utilized to select one or more candidate executable intents from a set of candidate executable intents.

[0246] Additional details of searching ontologies based on symbolic strings are described in U.S. Utility Patent Application Serial No. 12 / 341,743, filed on December 22, 2008, entitled “Method and Apparatus for Searching Using An Active Ontology,” the entire disclosure of which is incorporated herein by reference.

[0247] In some examples, once the natural language processing module 732 identifies an executable intent (or domain) based on the user request, the natural language processing module 732 generates a structured query representing the identified executable intent. In some examples, the structured query includes parameters for one or more nodes within the executable intent's domain, and at least some of the parameters are populated with specific information and requirements specified in the user request. For example, a user may say, "Make me a reservation at a sushi restaurant for 7 p.m." In this case, the natural language processing module 732 is able to correctly identify the executable intent as "restaurant reservation" based on the user input. According to the knowledge ontology, a structured query for the "restaurant reservation" domain includes parameters such as {cuisine}, {time}, {date}, {number of people in the party}, etc. In some examples, based on the voice input and text derived from the voice input using the STT processing module 730, the natural language processing module 732 generates a partial structured query for the restaurant reservation domain, where the partial structured query includes the parameters {cuisine = "sushi"} and {time = "7 p.m."}. However, in this example, the user utterance does not contain sufficient information to complete the structured query associated with the domain. Therefore, based on the currently available information, other necessary parameters such as {number of people in the party} and {date} are not specified in the structured query. In some examples, the natural language processing module 732 populates some parameters of the structured query with the received contextual information. For example, in some examples, if the user requests a sushi restaurant "nearby," the natural language processing module 732 populates the {location} parameter in the structured query with the GPS coordinates from the user's device.

[0248] In some examples, the natural language processing module 732 identifies multiple candidate executable intents for each candidate text representation received from the STT processing module 730. In addition, in some examples, a corresponding structured query is generated (partially or fully) for each identified candidate executable intent. The natural language processing module 732 determines an intent confidence score for each candidate executable intent and ranks the candidate executable intents based on the intent confidence score. In some examples, the natural language processing module 732 transmits the generated one or more structured queries (including any completed parameters) to the task flow processing module 736 ("task flow processor"). In some examples, one or more structured queries for the m best (e.g., the m highest ranked) candidate executable intents are provided to the task flow processing module 736, where m is a predetermined integer greater than zero. In some examples, one or more structured queries for the m best candidate executable intents are provided to the task flow processing module 736 along with the corresponding one or more candidate text representations.

[0249] Additional details for inferring user intent based on multiple candidate executable intents determined based on multiple candidate textual representations of speech input are described in U.S. utility patent application serial number 14 / 298,725, entitled “System and Method for Inferring User Intent From Speech Inputs,” filed on June 6, 2014, the entire disclosure of which is incorporated herein by reference.

[0250] The task flow processing module 736 is configured to receive one or more structured queries from the natural language processing module 732, complete the structured queries (if necessary), and perform the actions required to "complete" the user's final request. In some examples, the various processes necessary to complete these tasks are provided in the task flow model 754. In some examples, the task flow model 754 includes a process for obtaining additional information from the user, as well as a task flow for performing actions associated with the executable intent.

[0251] As described above, to complete a structured query, the task flow processing module 736 may need to initiate additional conversations with the user to obtain additional information and / or clarify potentially ambiguous utterances. When such interaction is necessary, the task flow processing module 736 invokes the dialog flow processing module 734 to participate in the conversation with the user. In some examples, the dialog flow processing module 734 determines how (and / or when) to request additional information from the user and receives and processes user responses. Questions are presented to the user and responses are received from the user via I / O processing module 728. In some examples, the dialog flow processing module 734 presents the dialog output to the user via audible and / or visual output and receives input from the user via verbal or physical (e.g., click) responses. Continuing with the above example, when the task flow processing module 736 invokes the dialog flow processing module 734 to determine the "party size" and "date" information for the structured query associated with the domain "restaurant reservation," the dialog flow processing module 734 generates questions such as "How many people are in your party?" and "What day do you want to reserve a reservation?" and transmits them to the user. Once the answer is received from the user, the dialog flow processing module 734 fills the structured query with the missing information, or passes the information to the task flow processing module 736 to complete the missing information based on the structured query.

[0252] Once the task flow processing module 736 has completed the structured query for the executable intent, the task flow processing module 736 begins to execute the final task associated with the executable intent. Therefore, the task flow processing module 736 executes 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 executable intent "restaurant reservation" includes steps and instructions for contacting a restaurant and actually requesting a reservation for a specific party size at a specific time. For example, using a structured query such as: {restaurant reservation, restaurant = ABC Cafe, date = 3 / 12 / 2012, time = 7pm, party size = 5}, the task flow processing module 736 may perform the following steps: (1) Log into the server of ABC Cafe or such A restaurant reservation system, (2) entering date, time, and party size information into a form on the website, (3) submitting the form, and (4) making a calendar entry for the reservation in the user's calendar.

[0253] In some examples, the task flow processing module 736, with the assistance of the service processing module 738 ("service processing module"), completes the task requested in the user input or provides the informational answer requested in the user input. For example, the service processing module 738 initiates a phone call, sets a calendar entry, invokes a map search, invokes or interacts with other user applications installed on the user device, and invokes or interacts with third-party services (e.g., a restaurant reservation portal, a social networking site, a bank portal, etc.) on behalf of the task flow processing module 736. In some examples, the protocols and application programming interfaces (APIs) required for each service are specified by the corresponding service model in the service model 756. The service processing module 738 accesses the appropriate service model for the service and generates a request for the service based on the protocol and API required by the service according to the service model.

[0254] For example, if a restaurant has enabled an online reservation service, the restaurant submits a service model that specifies the necessary parameters for making a reservation and transmits the values of the necessary parameters to the API of the online reservation service. When requested by the task flow processing module 736, the service processing module 738 can use the web address stored in the service model to establish a network connection with the online reservation service and send the necessary parameters for 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.

[0255] In some examples, the natural language processing module 732, the dialogue flow processing module 734, and the task flow processing module 736 are used together and repeatedly to infer and define the user's intention, obtain information to further clarify and refine the user's intention, and ultimately generate a response (i.e., output to the user, or complete the task) to satisfy the user's intention. The generated response is a dialogue response to the voice input that at least partially satisfies the user's intention. In addition, in some examples, the generated response is output as a voice output. In these examples, the generated response is sent to the speech synthesis processing module 740 (e.g., a speech synthesizer), where the generated response can be processed to synthesize the dialogue response in the form of speech. In other examples, the generated response is data content related to satisfying the user request in the voice input.

[0256] In an example where the task flow processing module 736 receives multiple structured queries from the natural language processing module 732, the task flow processing module 736 first processes the first structured query of the received structured queries in an attempt to complete the first structured query and / or perform one or more tasks or actions represented by the first structured query. In some examples, the first structured query corresponds to the highest-ranked executable intent. In other examples, the first structured query is selected from the structured queries received based on a combination of the corresponding speech recognition confidence score and the corresponding intent confidence score. In some examples, if the task flow processing module 736 encounters an error during processing of the first structured query (e.g., due to an inability to determine the necessary parameters), the task flow processing module 736 may continue to select and process a second structured query corresponding to a lower-ranked executable intent in the received structured queries. For example, the second structured query is selected based on the speech recognition confidence score of the corresponding candidate text representation, the intent confidence score of the corresponding candidate executable intent, the missing necessary parameters in the first structured query, or any combination thereof.

[0257] The speech synthesis processing module 740 is configured to synthesize speech output for presentation to the user. The speech synthesis processing module 740 synthesizes speech output based on the text provided by the digital assistant. For example, the generated dialogue response is in the form of a text string. The speech synthesis processing module 740 converts the text string into audible speech output. The speech synthesis processing module 740 uses any appropriate speech synthesis technology to generate speech output from the text, including but not limited to: concatenative synthesis, unit selection synthesis, diphone synthesis, domain-specific synthesis, formant synthesis, pronunciation synthesis, Hidden Markov Model (HMM)-based synthesis, and sine wave synthesis. In some examples, the speech synthesis processing module 740 is configured to synthesize individual words based on phoneme strings corresponding to these words. For example, the phoneme strings are associated with the words in the generated dialogue response. The phoneme strings are stored in metadata associated with the words. The speech synthesis processing module 740 is configured to directly process the phoneme strings in the metadata to synthesize the words in speech form.

[0258] In some examples, instead of using the speech synthesis processing module 740 (or in addition), speech synthesis is performed on a remote device (e.g., server system 108), and the synthesized speech is sent to the user device for output to the user. For example, this may occur in some implementations where the output of the digital assistant is generated at the server system. And because the server system typically has more processing power or more resources than the user device, it is possible to obtain higher quality speech output than client-side synthesis would achieve.

[0259] Additional details about digital assistants can be found in U.S. utility patent application No. 12 / 987,982, filed on January 10, 2011, entitled “Intelligent Automated Assistant,” and U.S. utility patent application No. 13 / 251,088, filed on September 30, 2011, entitled “Generating and Processing Task Items That Represent Tasks to Perform,” the entire disclosures of which are incorporated herein by reference.

[0260] 4. Systems and techniques for providing context-aware digital assistant responses during video communication sessions

[0261] Figure 8 Systems and techniques for providing context-aware digital assistant responses during a video communication session according to various examples are shown. System 800 includes a user device 802 and a user device 804. User device 802 and user device 804 are both client devices (e.g., user devices 104, 122, 200, 400, or 600). In some examples, system 800 includes one or more servers (e.g., DA server 106). It should be appreciated that in these examples, any operations performed by user device 802 and / or user device 804 may alternatively be performed by the one or more servers. For example, the one or more servers may perform the operations of a corresponding DA client module (e.g., DA client module 229) of user device 802 and / or user device 804.

[0262] As indicated by arrow 806, user device 802 and user device 804 initiate a video communication session (e.g., a video conference). In some examples, more than two user devices (e.g., four user devices) participate in the video communication session. In some examples, initiating a video communication session establishes one or more audio streams between each user device participating in the video communication session. For example, when initiating the video communication session, user device 802 and user device 804 establish a first audio stream between each other. For example, if a third user device were to join the video communication session, the third user device would establish a second audio stream between itself and user device 802 and a third audio stream between itself and user device 804. In some examples, the remaining steps of the technique (see below) Figure 8 ) occurs during an initiated video communication session between user device 802 and user device 804.

[0263] Figure 9 An exemplary user interface for a video communication session according to various examples is shown. Specifically, Figure 9A user device 900 (e.g., user device 104, 122, 200, or 600) is shown. User device 900 is similar or identical to user device 802 and / or user device 804. Figure 9 In the non-limiting exemplary embodiment shown in FIG, user device 900 is a smartphone. In other embodiments, user device 900 can be a different type of user device, such as a wearable device (e.g., a smartwatch or smart glasses), a tablet computer, a laptop or desktop computer, etc. As shown, user device 900 includes a display 902. In some examples, user device 900 includes one or more input devices (e.g., a touch screen of display 902, buttons 910, a microphone, etc.).

[0264] exist Figure 9 , user device 900 displays a video communication session interface 904 on display 902 (e.g., touch-sensitive display system 212). Video communication session interface 904 is an exemplary user interface for a video communication session (e.g., a video conference) between two user devices (e.g., user device 802 and user device 804). As shown, video communication session interface 904 includes representations of three participants in the video communication session. Representation 906A includes a view from a camera (e.g., optical sensor 164) of user device 900 (e.g., user device 802). Representation 906B includes a real-time video feed from a second user device (e.g., user device 804).

[0265] In some examples, a representation (e.g., representation 906B) includes a representative image of a user device that only provides audio data (e.g., because video data is unavailable). For example, the representative image may include one or more letters representing a participant (e.g., the first letters of a participant's contact name stored on user device 900) and / or the participant's full name (e.g., the full participant's contact name stored on user device 900). Furthermore, the representative image may be any two-dimensional shape (e.g., a circle, square, rectangle, triangle, etc.) or any three-dimensional shape (e.g., a sphere, cube, pyramid, etc.). In some examples, a representation (e.g., representation 906B) includes an avatar (e.g., an icon or graphic representing a particular person). For example, the avatar may represent a user of a user device that only provides audio data. In some examples, one or more movements of the avatar (e.g., movements of the avatar's lips, eyes, and / or head) are synchronized with the audio data received from the user device that only provides audio data. Thus, the avatar appears to be speaking and / or moving based on the audio output generated based on the audio data.

[0266] Representation 906C includes a representative image of the digital assistant of the user device 900. As shown, the representative image of the digital assistant includes the letter "S" and the name "Siri". However, the representative image of the digital assistant is not limited to this example and may include any other image, letter, name, number, or combination thereof. In addition, the representative image of the digital assistant may be any two-dimensional shape (e.g., a circle, square, rectangle, triangle, etc.) or any three-dimensional shape (e.g., a sphere, cube, pyramid, etc.). In some examples, the representative image of the digital assistant includes an avatar. In some examples, one or more movements of the avatar (e.g., movement of the avatar's lips, eyes, and / or head) are synchronized with the digital assistant response (i.e., the audio output for the digital assistant response). In this way, the avatar appears to be speaking and / or moving according to the digital assistant response.

[0267] Finally, the video communication session interface 904 includes an effect enable indication 908A, a mute enable indication 908B, a flip enable indication 908C, and an end enable indication 908D.

[0268] The following will refer to Figure 8 As detailed, the digital assistant of user device 900 is represented as representation 906C in video communication session interface 904 because the digital assistant is able to interact with one or more participants of the video communication session (e.g., the user of user device 900 and / or the user of a second user device). Specifically, in some examples, when the digital assistant is invoked by a participant (e.g., the user of user device 900) during the video communication session, the participant can request the digital assistant to perform a task and the digital assistant can subsequently provide a response to the participant's request. Furthermore, in some examples, each participant of the video communication session can hear the digital assistant request and the subsequent digital assistant response. This, in turn, creates the appearance of a single digital assistant actively participating in a video communication session between multiple participants.

[0269] Note that in some examples, the user interface for the video communication session is based on the number of user devices participating in the video communication session. For example, if a third user device joins Figure 9 If the video communication session shown in FIG. 9 is changed, the video communication session interface 904 will be converted to a new video communication session interface having an additional representation (e.g., representation 906D) for the third user device. In these examples, the additional representation will include a real-time video feed from the third user device or a representative image for the third user device.

[0270] In addition, in some examples, each user device participating in the video communication session has an activity level that is used to determine the layout of representations included in the video communication session user interface (e.g., the layout of representations 906A and 906B of video communication session interface 904). In some examples, the activity level of the user device is based on the audio and / or video feed received from the user device (e.g., motion or sound in the video feed). In some examples, the activity level of the participant is based on movement identified in the video feed received from the user device that meets a set of movement criteria (e.g., a certain type of movement (e.g., hand movement, head / face movement, movement that is not background movement (e.g., non-participant movement)).

[0271] In some examples, the digital assistant has a method for determining an activity level of a layout of representations of the digital assistant included in the video communication session interface (e.g., layout of representations 906C). In some examples, the activity level of the digital assistant is based on an audio feed of the digital assistant (e.g., based on audio responses provided by the digital assistant and / or output by a user device (e.g., user device 900)).

[0272] Back to Figure 8, as shown by arrow 808, user device 802 receives a first user input. In some examples, the first user input is a user voice input. In some examples, the first user input includes a digital assistant trigger word (e.g., "Hey, Siri," "Siri," etc.) that invokes the digital assistant of user device 802 (e.g., initiating a conversation session between the user of user device 802 and the digital assistant of user device 802). For example, the first user input may include a digital assistant trigger word at the beginning of the first user input (e.g., "Hey, Siri, what's the weather like in Palo Alto?"). For another example, the first user input may include a digital assistant trigger word at the end of the first user input (e.g., "What's the weather like in Palo Alto, Siri?"). In some examples, in response to determining that the first user input includes a digital assistant trigger word, user device 802 determines that the first user input represents a user request for the digital assistant of user device 802 to perform one or more tasks (and in some examples, provide one or more digital assistant responses to the user request). For example, the user input "Hey, Siri, what's the weather like in Palo Alto?" represents a user request for the digital assistant to retrieve and provide weather information for Palo Alto. In some examples, even if the first user input does not include a digital assistant trigger word, the first user input represents a user request for the digital assistant of user device 802 to perform one or more tasks (and in some examples, provide one or more digital assistant responses to the user request). In these examples, the digital assistant of user device 802 is invoked before receiving the first user input. For example, the digital assistant of user device 802 may be invoked in response to a user selecting an affordance displayed in a user interface for a video communication session. For another example, the digital assistant of user device 802 may be invoked in response to a user of user device 802 pressing (e.g., long pressing) a physical button of user device 802. In these examples, once the digital assistant of user device 802 is invoked, user device 802 may receive the first user input.

[0273] In some examples, in response to receiving the first user input, user device 802 transmits the first user input (e.g., audio data or text data representing the first user input) to user device 804. In some examples, user device 802 transmits the first user input to user device 804 as a peer-to-peer transmission (e.g., using an audio stream established between the two user devices when the video communication session is initiated). In other examples, user device 802 transmits the first user input to one or more servers (e.g., DA server 106), which then transmits the first user input (e.g., audio data representing the first user input) to user device 804. In some examples, after receiving the first user input, user device 804 outputs the first user input as an audio output (e.g., using speaker 211).

[0274] Upon receiving the first user input, the user device 802 obtains a first digital assistant response based on the first user input. In some examples, obtaining the first digital assistant response includes the user device 802 performing natural language processing of the first user input, determining one or more tasks to be performed based on the results of the natural language processing, and performing the one or more tasks to determine the first digital assistant response (e.g., performing a search, retrieving data, performing text-to-speech processing, etc.). In some examples, obtaining the first digital assistant response includes the user device 802 transmitting the first user input (e.g., audio data representing the first user input) to one or more servers (e.g., the DA server 106) and subsequently receiving the first digital assistant response from the one or more servers (e.g., after the one or more servers perform natural language processing of the first user input and perform the one or more tasks to determine the first digital assistant response). In some examples, after the user device 802 transmits the first user input to the one or more servers, the user device 802 receives one or more commands from the one or more servers to perform the one or more tasks (e.g., a command to search / retrieve the current temperature in Palo Alto based on the user input “Hey Siri, what’s the weather in Palo Alto?”). In some examples, after performing one or more tasks in response to one or more commands, the user device 802 determines a first digital assistant response based on the results of the one or more performed tasks (e.g., determining the first digital assistant response based on the current temperature information of Palo Alto obtained via a search). In other examples, after performing one or more tasks in response to one or more commands, the user device 802 transmits the results of the one or more performed tasks (e.g., data representing the results) to one or more servers. The one or more servers then determine a first digital assistant response based on the results and subsequently transmit the first digital assistant response (e.g., data representing the first digital assistant response) to the user device 802.

[0275] In some examples, the first digital assistant response includes a natural language expression corresponding to a task performed by the digital assistant of the user device 802 (and / or one or more servers) based on the first user input. For example, if the first user input is "Hey, Siri, what's the weather in Palo Alto?", the first digital assistant response may include the natural language expression "It's 90 degrees in Palo Alto right now." In this example, the natural language expression "It's 90 degrees in Palo Alto right now" corresponds to a digital assistant task of, for example, searching for, retrieving, and providing weather information / data for Palo Alto. In some examples, the first digital assistant response includes data (e.g., website hyperlinks, images, audio data, video data, navigation information, stored contact information, weather information, etc.) retrieved and / or determined by the digital assistant of the user device 802 (and / or one or more servers). For example, the first digital assistant response in the above example includes current temperature data for Palo Alto (e.g., "90 degrees").

[0276] As indicated by arrow 810, user device 802 provides the first digital assistant response and contextual information associated with the first user input (e.g., data corresponding to the first digital assistant response and the contextual information) to user device 804. Figure 8 As shown, user device 802 transmits the first digital assistant response and context information directly to user device 804 (e.g., in a peer-to-peer manner). For example, when initiating a video communication session in which user device 802 and user device 804 participate, user device 802 may transmit the first digital assistant response as audio data to device 804 via an audio stream established between the two devices. As another example, user device 802 may transmit the first digital assistant response as text data (e.g., a text representation of the first digital assistant response) directly to user device 804. In some examples, user device 802 provides user device 804 with a command to perform one or more tasks and context information associated with the first user input. In these examples, user device 804 performs the one or more tasks in response to receiving the command and then obtains the first digital assistant response based on the results of the execution of the one or more tasks.

[0277] In some examples, providing the first digital assistant response and the context information to the user device 804 includes the user device 802 transmitting the first digital assistant response and the context information (e.g., audio and / or text data representing the first digital assistant response and the context information) to one or more servers. In these examples, the one or more servers then transmit the first digital assistant response and the context information to the user device 804.

[0278] In some examples, the context information associated with the first user input includes data corresponding to the context state of user device 802 when user device 802 receives the first user input. For example, the context state of user device 802 includes the local time when user device 802 receives the first user input, the current location and / or orientation of user device 802 when user device 802 receives the first user input, the movement speed and / or direction of user device 802 when user device 802 receives the first user input, the signal strength (e.g., Wi-Fi signal strength) when user device 802 receives the first user input, etc. Note that in some examples, the context state of user device 802 "when user device 802 receives the first user input" includes the context state of user device 802 immediately before and / or after user device 802 receives the first user input. For example, the context state of user device 802 when user device 802 receives the first user input may include the context state of user device 802 5 seconds, 10 seconds, and / or 15 seconds before and / or after user device 802 receives the first user input.

[0279] In some examples, the contextual information associated with the first user input includes data associated with the first user input stored on the user device 802. For example, the data associated with the first user input stored on the user device 802 includes stored contact information, stored user-specific preferences and / or information (e.g., favorite restaurants, favorite sports teams, navigation preferences, calendar information, etc.), and / or any other information stored on the user device 802 that is used to determine a first digital assistant response based on the first user input (e.g., used to disambiguate the first user input, used to determine one or more parameters for performing a digital assistant task based on the first user input, etc.). For example, if the first user input is “Hey, Siri, how long does it take to drive to John’s house?”, the contextual information associated with the first user input may include the home address in John’s contact information stored on the user device 802 (e.g., stored in the application-internal state 292 of the contacts module 237 in memory 202 or memory 470).

[0280] In some examples, the data associated with the first user input stored on the user device 802 includes data stored (e.g., locally or remotely) by a software application on the user device 802 (e.g., a native software application or a third-party software application stored on the user device 802) (e.g., contact information, user-specific preferences and / or information, etc.). In these examples, the user device 802 requests the data from the software application. For example, the user device 802 may request user-specific calendar information (e.g., all user calendar entries or user calendar entries for one or more specific dates) from a third-party calendar software application stored on the user device 802. In response, the software application retrieves the data (e.g., retrieves the requested data from local storage (e.g., memory 202 or memory 470) and / or requests one or more servers to provide the requested data to the software application) and provides the data to the user device 802.

[0281] In some examples, contextual information associated with the first user input includes a conversation history (e.g., data representing the conversation history) between the digital assistant of user device 802 and the user of user device 802 during the video communication session. In some examples, the conversation history includes previous user inputs received by user device 802 during the video communication session (e.g., before receiving the first user input) and / or previous digital assistant responses determined and / or provided by user device 802 during the video communication session (e.g., determined and / or provided before determining and / or providing the first digital assistant response).

[0282] In some examples, the contextual information associated with the first user input includes contextual information (such as the contextual information described above) received by user device 802 from one or more other user devices participating in the video communication session during the video communication session (e.g., before user device 802 receives the first user input). For example, user device 802 may receive contextual state data (e.g., data indicating a current location) from a third user device participating in the video communication session (e.g., using a digital assistant response determined by the third user device). User device 802 may then transmit the contextual state data of the third user device associated with the first user input (e.g., using the first digital assistant response) to user device 804. For another example, user device 802 may receive a conversation history of the third user device during the video communication session, which may include user input received by the third user device during the video communication session (e.g., before user device 802 receives the first user input) and / or a previous digital assistant response determined and / or provided by the third user device during the video communication session (e.g., determined and / or provided before user device 802 determines and / or provides the first digital assistant response). The user device 802 may then transmit data of the conversation history received from the third user device associated with the first user input (eg, data representing user input received at the third user device associated with the first user input).

[0283] In this way, a device that joins the video communication session later (e.g., after a conversation between two or more devices participating in the video communication session has already occurred) can still be aware of user input and / or digital assistant responses received and / or provided by other user devices participating in the video communication session before the later user device joined the video communication session. This in turn allows the digital assistant of the later device to determine and / or provide digital assistant responses based on previous user input and / or digital assistant responses, thereby seamlessly / naturally integrating into the existing conversation.

[0284] In some examples, contextual information associated with the first user input includes any information and / or data accessible by the user device 802 (e.g., stored on the user device 802, stored on one or more servers, and / or accessible via an internet search) and used by the user device 802 (or used by one or more servers) to determine a response from the first digital assistant.

[0285] In some examples, before user device 802 provides the first digital assistant response and context information associated with the first user input to user device 804, user device 802 determines whether the context information includes private information. In some examples, the private information includes private information associated with the user of user device 802 (e.g., stored on user device 802) and / or private information associated with one or more contacts stored on user device 802 (e.g., stored in application internal state 292 of contacts module 237 in memory 202 or memory 470). For example, the private information associated with the user and / or stored contacts includes personal information of the user and / or stored contacts (e.g., race, gender, age, weight, etc.), social security number (SSN), personal and / or work email addresses, personal and / or work addresses, personal health records, etc.

[0286] If user device 802 determines that the context information associated with the first user input includes private information, user device 802 removes at least a portion of the private information from the context information. In some examples, user device 802 removes private information not explicitly requested in the first user input. For example, if the first user input represents a user request for an email address of a stored contact (e.g., “Hey, Siri, what is John's email address?”), the user device 802 removes the private information other than the email address of the stored contact from the context information before providing the context information to the user device 804 (e.g., using the first digital assistant response). In some examples, the user device 802 removes private information that is not used to determine the first digital assistant response (e.g., all private information that is not used to disambiguate the first user input, determine one or more parameters for performing a digital assistant task based on the first user input, etc.). For example, if the first user input represents a user request for navigation information about the user's home address (e.g., “Hey, Siri, how long will it take me to get home now?”), the user device 802 removes the private information other than the user's home address (and any other private information used to determine the first digital assistant response) from the context information before providing the context information to the user device 804 (e.g., using the first digital assistant response).

[0287] After the user device 802 removes at least a portion of the private information from the context information (e.g., private information not explicitly requested in the first user input and / or private information not used to determine the first digital assistant response), the user device 802 provides the first digital assistant response and the remaining context information associated with the first user input to the user device 804 (e.g., as described above with reference to arrow 810).

[0288] As indicated by arrow 812, user device 802 and user device 804 output a first digital assistant response. In some examples, user device 802 and user device 804 output the first digital assistant response simultaneously. In some examples, user device 802 and user device 804 output the first digital assistant response at different times. For example, user device 802 may output the first digital assistant response a few seconds (e.g., 1 second, 2 seconds, 5 seconds, or 10 seconds) before user device 804 outputs the first digital assistant response. In some examples, user device 802 outputs the first digital assistant response before providing the first digital assistant response (and contextual information associated with the first user input) to user device 804. Then, in some examples, user device 804 outputs the first digital assistant response after receiving the first digital assistant response.

[0289] In some examples, outputting the first digital assistant response includes the user device 802 and / or the user device 804 outputting the first digital assistant response as an audio output (e.g., using the speaker 211). As described above, in some examples, the user device 802 provides the first digital assistant response to the user device 804 as text data. In these examples, the user device 804 performs text-to-speech processing on the text data corresponding to the first digital assistant response to generate an audio output corresponding to the first digital assistant response (and then outputs the audio output). In some examples, the user device 802 and / or the user device 804 outputs the audio output corresponding to the first digital assistant response based on one or more predefined digital assistant language and / or voice settings (for each respective user device). For example, the user device 802 may have a predefined digital assistant language setting of English and a predefined digital assistant voice setting of British English (male), while the user device 804 may have a predefined digital assistant language setting of English and a predefined digital assistant voice setting of American English (female).

[0290] In some examples, outputting the first digital assistant response includes the user device 802 and / or user device 804 displaying (e.g., using the touch-sensitive display system 212) the data included in the first digital assistant response (e.g., text, images, videos, navigation information, etc. retrieved and / or determined by the digital assistant of the user device 802 based on the first user input). In some examples, during the video communication session, the user device 802 and / or user device 804 displays the data included in the first digital assistant response. For example, the user device 802 and / or user device 804 may display the image included in the first digital assistant response as a user interface (e.g., video communication session interface 904) overlaying the video communication session while outputting the first digital assistant response as an audio output. In some examples, after the video communication session ends, the user device 802 and / or user device 804 displays the data included in the first digital assistant response. For example, after the video communication session ends and the user interface for the video communication session is no longer displayed, the user device 802 and / or user device 804 may display the video included in the first digital assistant response.

[0291] In some examples, outputting the first digital assistant response includes storing (e.g., permanently or temporarily) data included in the first digital assistant response by user device 802 and / or user device 804. In some examples, a user of user device 802 and / or user device 804 accesses the stored data included in the first digital assistant response via an application stored on user device 802 and / or user device 804 (e.g., an application via applications 236). For example, if the first user input represents a request for navigation directions (e.g., “Hey, Siri, show me directions to John’s house.”), user device 802 and / or user device 804 may output the first digital assistant response as an audio output (e.g., “Directions to John’s house can be found in your Maps application.”) and store the navigation information included in the first digital assistant response so that the user of user device 802 and / or user device 804 can access the navigation information using a navigation application stored on user device 802 and / or user device 804.

[0292] As shown by arrow 814, user device 804 receives a second user input. In some examples, the second user input is a user voice input. In some examples, the second user input includes a digital assistant trigger word (e.g., "Hey, Siri," "Siri," etc.) that invokes the digital assistant of user device 804 (e.g., initiating a conversation session between the user of user device 804 and the digital assistant of user device 804). For example, the second user input may include a digital assistant trigger word (e.g., "Hey, Siri, how long does it take to drive there?") at the beginning of the second user input. As another example, the second user input may include a digital assistant trigger word (e.g., "How long does it take to drive there, Siri?") at the end of the second user input. In some examples, in response to determining that the second user input includes a digital assistant trigger word, user device 804 determines that the second user input represents a user request for the digital assistant of user device 804 to perform a task (and in some examples, provide a digital assistant response to the user request). For example, the user input "Hey, Siri, how long does it take to drive there?" represents a user request for the digital assistant to retrieve navigation information and provide it to the previously mentioned location (i.e., "there").

[0293] In some examples, in response to receiving the second user input, user device 804 transmits the second user input (e.g., audio data representing the second user input) to user device 802 (and other user devices participating in the video communication session). In some examples, user device 804 transmits the second user input to user device 802 as a peer-to-peer transmission (e.g., using an audio stream established between the two user devices when the video communication session was initiated). In other examples, user device 804 transmits the second user input to one or more servers (e.g., DA server 106), which then transmits the second user input (e.g., audio data representing the second user input) to user device 802. In some examples, after receiving the second user input, user device 802 outputs the second user input as an audio output (e.g., using speaker 211).

[0294] Upon receiving the second user input, the user device 804 obtains a second digital assistant response based on the second user input. In some examples, obtaining the second digital assistant response includes the user device 804 performing natural language processing of the second user input, determining one or more tasks to be performed based on the results of the natural language processing, and performing the one or more tasks to determine the second digital assistant response (e.g., performing a search, retrieving data, performing text-to-speech processing, etc.). In some examples, obtaining the second digital assistant response includes the user device 804 transmitting the first user input (e.g., audio data representing the second user input) to one or more servers (e.g., DA server 106) and subsequently receiving the second digital assistant response from the one or more servers (e.g., after the one or more servers perform natural language processing of the second user input and perform the one or more tasks to determine the second digital assistant response). In some examples, after the user device 804 transmits the second user input to the one or more servers, the user device 804 receives one or more commands to perform the one or more tasks from the one or more servers. In some examples, after performing the one or more tasks in response to the one or more commands, the user device 804 determines the second digital assistant response based on the results of the one or more performed tasks. In other examples, after performing one or more tasks in response to one or more commands, the user device 804 transmits the results of the one or more performed tasks (e.g., data representing the results) to the one or more servers. The one or more servers then determine a second digital assistant response based on the results and subsequently transmit the second digital assistant response (e.g., data representing the second digital assistant response) to the user device 804.

[0295] In some examples, the user device 804 further obtains the second digital assistant response based on contextual information associated with the first user input (and received with the first digital assistant response). Specifically, in some examples, the user device 804 (or one or more servers) uses the contextual information associated with the first user input to disambiguate one or more ambiguous terms or phrases in the second user input (e.g., when determining user intent based on the second user input), and then determines the second digital assistant response based on the disambiguated second user input. For example, if the first user input is “Hey, Siri, what’s the weather like in Palo Alto?” and the second user input is “Hey, Siri, how long does it take to drive there?” ”, the user device 804 (or one or more servers) may use contextual information associated with the first user input (e.g., the conversation history received from the user device 802) to disambiguate the term “there” and determine that the second user input represents a user request for navigation information (i.e., travel time) from the current location of the user device 804 to Palo Alto (e.g., because “there” refers to the location mentioned in the first user input (i.e., Palo Alto)). For another example, if the first user input is “Hey, Siri, what’s the weather like in Palo Alto?” and the second user input is “Hey, Siri, what about New York?”, the user device 804 (or one or more servers) may use contextual information associated with the first user input (e.g., the conversation history received from the user device 802) to disambiguate the term “there” and determine that the second user input represents a user request for weather information about New York (e.g., because “what about New York” refers to the task requested in the first user input).

[0296] In some examples, the user device 804 (or one or more servers) uses contextual information associated with the first user input to determine one or more parameters (e.g., one or more structured query parameters) for performing one or more tasks based on the second user input. Example parameters that the user device 804 (or one or more servers) determines based on the contextual information associated with the first user input include (but are not limited to) a location, a website hyperlink, a phone number, an email address, a home and / or work address, and the like. For example, if the first user input is "What's John's mobile number, Siri?" and the second user input is "Hey, Siri, save John's mobile number to my contacts.", the user device 804 (or one or more servers) may use the contextual information associated with the first user input and received with the first digital assistant response (e.g., John's mobile number stored on the user device 802) to determine the phone number that the user of the user device 804 wishes to save (e.g., if the user device 804 has not already saved John's mobile number before receiving the second user input). After the user device 804 (or one or more servers) performs one or more tasks based on the one or more determined parameters, the user device 804 (or one or more servers) determines a second digital assistant response based on the results of the one or more tasks performed. For example, in the previous example, the second digital assistant response can be "John's mobile number has been added to your stored contacts."

[0297] Using contextual information as described above to determine a second digital assistant response allows the digital assistant of the second user device to provide a digital assistant response that is based on and / or facilitates the user request and / or digital assistant response received / provided at the first user device. In this way, users of the first user device and the second user device can provide digital assistant requests in a more natural and conversational manner during the video communication session, and if certain aspects of the request have already been introduced in previous user requests and / or digital assistant responses during the video communication session, those aspects do not have to be repeated. For example, as described above, if the user of the first user device provides the user request “Hey, Siri, what’s the weather in Palo Alto?”, the user of the second user device can subsequently request weather information about New York by providing the user request “Hey, Siri, what’s the weather in New York?”, rather than having to repeat the request for weather information (e.g., “Hey, Siri, what’s the weather in New York?”). This, in turn, creates the appearance of a single digital assistant participating in the video communication session with the users of the first user device and the second user device, while still allowing the digital assistant of each user device to locally process requests from its respective user. This ultimately improves the video communication session experience for the users of the first user device and the second user device.

[0298] In some examples, the second digital assistant response includes a natural language expression corresponding to a task performed by the digital assistant of the user device 802 (and / or one or more servers) based on the second user input. For example, if the second user input is "Hey, Siri, how long does it take to drive there?", the second digital assistant response may include the natural language expression "Traffic is light to Palo Alto, I estimate it will take 45 minutes via I-280 North." In this example, the natural language expression "Traffic is light to Palo Alto, I estimate it will take 45 minutes via I-280 North. ” corresponds to a digital assistant task of, for example, retrieving navigation information (e.g., travel time) about the current location of the user device 804 and the previously mentioned location (in this case, Palo Alto). In some examples, the second digital assistant response includes data (e.g., website hyperlinks, images, videos, navigation information, stored contact information, weather information, etc.) retrieved and / or determined by the digital assistant of the user device 802 (and / or one or more servers). For example, the second digital assistant response in the above example includes navigation data (e.g., 45 minutes via I-280 North) determined and / or retrieved by the user device 804 (or one or more servers).

[0299] As indicated by arrow 816, user device 804 provides the second digital assistant response (e.g., data corresponding to the second digital assistant response) and contextual information associated with the second user input to user device 802. Figure 8 As shown, user device 804 transmits the second digital assistant response and context information directly to user device 802 (e.g., in a peer-to-peer manner). For example, when initiating a video communication session in which user device 802 and user device 804 participate, user device 804 may transmit the second digital assistant response as audio data to device 802 via an audio stream established between the two devices. As another example, user device 804 may transmit the second digital assistant response as text data (e.g., a text representation of the second digital assistant response) directly to user device 802. In some examples, user device 804 provides user device 802 with a command to perform one or more tasks and context information associated with the second user input. In these examples, user device 802 performs the one or more tasks in response to receiving the command and then obtains a second digital assistant response based on the results of the execution of the one or more tasks.

[0300] In some examples, providing the second digital assistant response and the context information to the user device 802 includes the user device 804 transmitting the second digital assistant response and the context information (e.g., audio and / or text data representing the second digital assistant response and the context information) to one or more servers. In these examples, the one or more servers then transmit the second digital assistant response and the context information to the user device 802.

[0301] The context information associated with the second user input may include any of the various types of context information described above with respect to the context information associated with the first user input (e.g., as described with reference to arrow 810). That is, in some examples, the context information associated with the second user input includes data corresponding to the context state of user device 804 when user device 804 receives the second user input. In some examples, the context information associated with the second user input includes data associated with the second user input stored on user device 804. In some examples, the context information associated with the second user input includes a conversation history (e.g., data representing the conversation history) between the digital assistant of user device 804 and the user of user device 804 during the video communication session. In some examples, the context information associated with the second user input includes context information (such as the context information described above) received by user device 804 from one or more other user devices participating in the video communication session during the video communication session (e.g., before user device 804 receives the first user input). In some examples, contextual information associated with the second user input includes any information and / or data accessible by the user device 804 (e.g., stored on the user device 804, stored on one or more servers, and / or accessible via an internet search) and used by the user device 804 (or used by one or more servers) to determine a second digital assistant response.

[0302] In some examples, before user device 804 provides the second digital assistant response and context information associated with the second user input to user device 802, user device 804 determines whether the context information includes privacy information (e.g., as described above with respect to user device 802 and context information associated with the first user input). If user device 804 determines that the context information associated with the second user input includes privacy information, user device 804 removes at least a portion of the privacy information from the context information (e.g., in the same manner as user device 802 removed the privacy information from the context information associated with the first user input). After user device 804 removes at least a portion of the privacy information from the context information (e.g., privacy information that was not explicitly requested in the second user input and / or privacy information that was not used to determine the second digital assistant response), user device 804 provides the second digital assistant response and the remaining context information associated with the second user input to user device 802 (e.g., as described above with reference to arrow 816). Additional details regarding the type of privacy information and removal of privacy information from the context information are described above with reference to removing privacy information from the context information associated with the first user input. These additional details also apply to removing private information from the contextual information associated with the second user input.

[0303] As indicated by arrow 818, user device 802 and user device 804 output the second digital assistant response. In some examples, user device 802 and user device 804 output the second digital assistant response simultaneously. In some examples, user device 802 and user device 804 output the second digital assistant response at different times. For example, user device 802 may output the second digital assistant response a few seconds (e.g., 1 second, 2 seconds, 5 seconds, or 10 seconds) before user device 804 outputs the second digital assistant response. In some examples, user device 804 outputs the second digital assistant response before providing the second digital assistant response (and contextual information associated with the second user input) to user device 802. Then, in some examples, user device 802 outputs the second digital assistant response after receiving the second digital assistant response.

[0304] The user device 802 and / or 804 outputs the second digital assistant response in any of the various ways described above with reference to outputting the first digital assistant response (e.g., as described above with reference to arrow 810). That is, in some examples, outputting the second digital assistant response includes the user device 802 and / or user device 804 outputting the second digital assistant response as an audio output (e.g., using speaker 211). As described above, the user device 804 may provide various forms of data corresponding to the second digital assistant response to the user device 802 (e.g., audio data, text data, commands to perform one or more tasks, etc.). In all of these examples, the user device 802 performs any processing required on the received data in order to output the second digital assistant response. For example, if the user device 804 provides the second digital assistant response to the user device 802 as text data, the user device 802 will perform text-to-speech processing on the text data corresponding to the second digital assistant response to generate an audio output corresponding to the second digital assistant response (and subsequently output the audio output).

[0305] In some examples, user device 802 and / or user device 804 output an audio output corresponding to the second digital assistant response based on one or more predefined digital assistant language and / or voice settings (for each respective user device). For example, user device 802 may have a predefined digital assistant language setting of English and a predefined digital assistant voice setting of British English (male), while user device 804 may have a predefined digital assistant language setting of English and a predefined digital assistant voice setting of American English (female).

[0306] In some examples, outputting the second digital assistant response includes the user device 802 and / or the user device 804 displaying (e.g., using the touch-sensitive display system 212) data included in the second digital assistant response (e.g., text, images, video, navigation information, etc. retrieved and / or determined by the digital assistant of the user device 804 based on the second user input). In some examples, outputting the second digital assistant response includes the user device 802 and / or the user device 804 storing (e.g., permanently or temporarily) the data included in the second digital assistant response.

[0307] In some examples, in response to receiving user input from a user (e.g., a first user input and / or a second user input) and before obtaining a digital assistant response (e.g., a first digital assistant response and / or a second digital assistant response) based on the user input, the user device 802 or the user device 804 determines whether the user input includes a digital assistant trigger word (e.g., "Hey, Siri," "Siri," etc.). In response to determining that the user input includes the digital assistant trigger word, the user device 802 or the user device 804 performs a call indication process or a call permission process (also known as a "baton" sharing process) to determine whether to continue obtaining a digital assistant response based on the user input.

[0308] In some examples, user device 802 or user device 804 performs a call indication process. Specifically, in response to determining that the user input includes a digital assistant trigger word, user device 802 or user device 804 generates an indication (e.g., a message, a signal, etc.) that the digital assistant of the user device has been invoked and transmits the indication to all other user devices participating in the video communication session. For example, if user device 802 determines that the first user input includes a digital assistant trigger word, user device 802 generates an indication that its digital assistant has been invoked and transmits the indication to user device 804 (before obtaining a response from the first digital assistant). In some examples, the indication includes data indicating the time (e.g., the time of day) at which the digital assistant of user device 802 or user device 804 was invoked.

[0309] After receiving an indication that a digital assistant of another user device has been invoked, user device 802 or user device 804 determines, based on the indication, whether the digital assistant of the user device providing the indication was invoked before receiving one or more user inputs (e.g., user inputs received before and / or after receiving the indication). For example, after receiving an indication from user device 804 that the digital assistant of user device 804 has been invoked (e.g., by a second user input), user device 802 determines (e.g., based on data indicating the time (included in the indication) when the digital assistant of user device 804 was invoked) whether a third user input was received before or after the digital assistant of user device 804 was invoked.

[0310] If the user device 802 or the user device 804 determines that the user input is received after the digital assistant of the other user device is called, the user device 802 or the user device 804 abandons obtaining a digital assistant response based on the user input. Returning to the previous example, if the user device 802 determines that the digital assistant of the user device 804 is called before the user device 802 receives a third user input, the user device 802 abandons obtaining a third digital assistant response based on the third user input. In some examples, after the user device 802 or the user device 804 determines that the user input is received after the digital assistant of the other user device is called, the user device 802 or the user device 804 will continue to abandon obtaining a digital assistant response based on the user input until the user device 802 or the user device 804 receives a digital assistant response from the other device (e.g., a digital assistant response based on the user input that called the digital assistant of the other device).

[0311] However, if user device 802 or user device 804 determines that user input was received before invoking the digital assistant of another user device, user device 802 or user device 804 obtains a digital assistant response based on the user input and / or provides the digital assistant response to the other user devices participating in the video communication session (e.g., as described above with reference to obtaining and / or providing the first digital assistant response and the second digital assistant response). Returning to the previous example, if user device 802 determines that the digital assistant of user device 804 was invoked after user device 802 received a third user input, user device 802 continues to obtain and / or provide a third digital assistant response to user device 804 (and any other user devices participating in the video communication session) based on the third user input.

[0312] In general, when implementing the call indication process, user device 802 or user device 804 will perform the following operations: (1) in response to determining that the user input includes a digital assistant trigger word, transmit an indication that its digital assistant has been invoked (transmitted to another user device participating in the video communication session); and (2) determine whether the user input is received before or after invoking the digital assistant of the other user device participating in the video communication session (based on any call indications recently received (e.g., received within the last 1 second, 5 seconds, or 10 seconds) from the other user devices participating in the video communication session).

[0313] In some examples, user device 802 or user device 804 performs a call permission process (also known as a "baton" passing process). Specifically, in response to determining that the user input includes a digital assistant trigger word, user device 802 or user device 804 determines whether it currently holds a digital assistant call permission. The digital assistant call permission (e.g., data indicating that the user device can call the user device's digital assistant) is the "baton" that the user device needs to call its digital assistant during the video communication session. Only one user device participating in the video communication session holds the call permission at a time. If user device 802 or user device 804 determines that it currently holds the call permission, user device 802 or user device 804 obtains a digital assistant response based on the user input and / or provides the digital assistant response to other user devices participating in the video communication session (e.g., as described above with reference to obtaining and / or providing a first digital assistant response and a second digital assistant response).

[0314] If user device 802 or user device 804 determines that it does not currently hold the call permission, user device 802 or user device 804 transmits a request for the call permission to the other user devices participating in the video communication session. Only the user device that currently holds the call permission can transfer the call permission to the user device that made the request. If the user device receiving the request (1) has not recently received user input indicating a digital assistant request before receiving the call permission request (e.g., 0.5 seconds, 1 second, or 2 seconds before receiving the request), and / or (2) is not in the process of obtaining and / or providing a digital assistant response based on user input when receiving the call permission request, then the user device that holds the call permission and receives the call permission request will transmit the call permission to the user device that made the request (e.g., user device 802 or user device 804). If user device 802 or user device 804 receives permission to call from another user device participating in the video communication session within a predetermined time period after transmitting the request for permission to call (e.g., 0.5 seconds, 1 second, or 2 seconds after transmitting the request), user device 802 or user device 804 obtains a digital assistant response based on the user input and / or provides the digital assistant response to the other user device participating in the video communication session. However, if user device 802 or user device 804 does not receive permission to call from another user device participating in the video communication session within a predetermined time period after transmitting the request for permission to call, user device 802 or user device 804 abandons obtaining and / or providing a digital assistant response based on the user input.

[0315] In some examples, user device 802 or user device 804 abandons obtaining and / or providing a digital assistant response based on user input in response to receiving a call permission request being denied from another user device participating in a video communication session, rather than waiting for a predetermined time period to expire. Only the user device currently holding the call permission can transmit the call permission request being denied to the user device that made the request. If the user device (1) recently received user input indicating a digital assistant request before receiving the call permission request (e.g., 0.5 seconds, 1 second, or 2 seconds before receiving the request), and / or (2) when receiving the call permission request, is in the process of obtaining and / or providing a digital assistant response based on user input, then the user device holding the call permission and receiving the call permission request will transmit the call permission request being denied. In some of these examples, user device 802 or user device 804 will continue to wait to act on the user input (but will not completely abandon obtaining and / or providing a digital assistant response based on the user input) until user device 802 or user device 804 receives the call permission or the call permission request being denied from another user device participating in the video communication session.

[0316] In some examples, after user device 802 or user device 804 abandons obtaining and / or providing a digital assistant response based on user input (e.g., because user device 802 or user device 804 never received permission to invoke and / or received permission to invoke that was denied) (e.g., immediately, 1 second later, etc.), user device 802 or user device 804 displays (e.g., on touch-sensitive display system 212 of user device 802 or user device 804) an indication that the digital assistant of user device 802 or user device 804 is currently unavailable, or an indication that the digital assistant of another user device participating in the video communication session is currently invoked. In some examples, user device 802 or user device 804 continues to display the indication (or at least a portion of the indication) until its digital assistant is available again (e.g., because the digital assistant of the other user device participating in the video communication session is no longer invoked).

[0317] Note that in the example of the above-mentioned call permission process, there is always a user equipment that currently holds the call permission and participates in the video communication. Specifically, first the call permission is assigned to the user equipment that initiates the video communication session (for example, the user equipment that issues the initial call or request for initiating the video communication session). For example, if user equipment 802 initially calls or requests user equipment 804 to initiate the video communication session, then once the video communication session is established (for example, after arrow 806), user equipment 802 will hold the call permission. In addition, if the user equipment that currently holds the call permission leaves the video communication session without transferring the call permission to another user equipment that participates in the video communication session, then the call permission automatically returns to the user equipment (for example, the user equipment 802 in the previous example) that issued the initial call or request for initiating the video communication session. If the user equipment that issues the initial call or request for initiating the video communication session no longer participates in the video communication session when the call permission holder leaves the video communication session, then the call permission automatically goes to the user equipment that has participated in the video communication session for the longest time (wherein the user equipment that recently joined the video communication session is ranked last and automatically receives the call permission).

[0318] The above-described call indication and call permission process helps prevent multiple digital assistants from being called concurrently during a video communication session. Thus, only one user device (of two or more user devices participating in the video communication session) can obtain / provide a digital assistant response based on user input during the video communication session at a time. This, in turn, maintains the appearance of a single digital assistant participating in the video communication session by, for example, preventing multiple overlapping digital assistant responses from being provided simultaneously (e.g., providing audio output of two digital assistant responses simultaneously).

[0319] In some examples, during a video communication session, user device 802 or user device 804 initiates a private digital assistant session and forgoes transmitting one or more user inputs and one or more corresponding digital assistant responses to other devices participating in the video communication session. Specifically, in some examples, user device 802 or user device 804 receives a user input and determines that the user input represents a user intent to provide a private digital assistant request. For example, after outputting a second digital assistant response (e.g., as described above with reference to arrow 818), user device 802 may receive a third user input (from the user of user device 802) and determine that the third user input represents a user intent to provide a private digital assistant request. Examples of user input representing a user intent to provide a private digital assistant request include (1) a user selection of a mute enable indication included in a displayed video communication session user interface (e.g., mute enable indication 908B) and (2) a button push and / or press (e.g., long press button 910) to invoke a digital assistant of user device 802 or user device 804.

[0320] If user device 802 or user device 804 determines that the user input indicates a user intent to provide a private digital assistant request, user device 802 or user device 804 will forgo providing (e.g., transmitting) subsequent user input (received from the user of user device 802 or user device 804, respectively) and the digital assistant response to other user devices participating in the video communication session until a predetermined condition is met (as described in detail below). User device 802 or user device 804 may then receive another user input (specifically, user voice input, such as, for example, “Hey, Siri, when is my mother’s birthday?” or “How many calories did I burn today?”), obtain a digital assistant response based on the user voice input (e.g., as described above with reference to obtaining a first digital assistant response and a second digital assistant response), forgo providing the digital assistant response to other user devices participating in the video communication session, and output the digital assistant response (e.g., as an audio output).

[0321] A private digital assistant session such as this (e.g., user voice input representing a digital assistant request and subsequent digital assistant response) allows a user of user device 802 or user device 804 to make a private digital assistant request during a video communication session and receive a subsequent digital assistant response that the user may not want users of other user devices participating in the video communication session to hear. This, in turn, prevents the user of user device 802 or user device 804 from having to wait until the video communication session ends in order to, for example, make a digital assistant request for information that the user may want or need during the video communication session. For example, if the user of user device 802 is participating in a video communication session with the user's mother (who is using user device 804), the user may want to find out the user's mother's birthday without the user's mother knowing. In this case, the user may, for example, initiate the private digital assistant session and provide a third user input, "Hey, Siri, when is my mother's birthday?", after user device 802 outputs a second digital assistant response (e.g., by selecting a silent affordance or pressing a button). User device 802 will then forgo providing the third user input and corresponding third digital assistant response (e.g., audio data representing the third user voice input and the third digital assistant response) to user device 804. Thus, the user's mother will not hear the third user input or the third digital assistant response. Furthermore, as described above, user device 802 will continue to forgo providing user input and digital assistant responses to user device 804 (and other user devices participating in the video communication session) until a predetermined condition is satisfied.

[0322] The manner in which the predetermined condition is satisfied depends on the manner in which the user of user device 802 or user device 804 initiated the private digital assistant session. In some examples, if the user of user device 802 or user device 804 initiates the private digital assistant session by selecting a mute affordance (e.g., mute affordance 906B), the predetermined condition is satisfied when user device 802 or user device 804 again receives a user selection of the mute affordance (i.e., unmuting and thereby allowing users at other devices participating in the video communication session to again hear voice input received at user device 802 or user device 804). In these examples, the second user selection of the mute affordance ends the private digital assistant session and allows user device 802 or user device 804 to again provide user input and digital assistant responses to the other user devices participating in the video communication session. In other examples, if the user of user device 802 or user device 804 initiates a private digital assistant session by depressing / pressing a physical button (e.g., long pressing button 910) that invokes the digital assistant of user device 802 or user device 804, the predetermined condition is satisfied once user device 802 or user device 804 outputs a digital assistant response in response to the private user input. Thus, unlike when the user initiates a private digital assistant session by selecting a silent affordance, in these examples, the user may only provide a single user input (e.g., “Hey, Siri, when is my mother's birthday?”) and receive a single corresponding digital assistant response before the private digital assistant session ends.

[0323] 5. For determining candidate based on user voice input received at a user device participating in a video communication session Systems and technologies for digital assistant tasks

[0324] Figure 10 Systems and techniques for determining candidate digital assistant tasks based on user voice input received at a user device participating in a video communication session are shown according to various examples. System 1000 includes a user device 1002 (e.g., user device 104, 122, 200, 400, 600), a user device 1004 (e.g., user device 104, 122, 200, 400, 600), and a server 1006 (e.g., DA server 106). In some examples, user device 1002 and user device 1004 are similar to or identical to user device 802 and user device 804, respectively. It should be appreciated that in these examples, any operations performed by user device 1002 and / or user device 1004 may alternatively be performed by server 1006, and any operations performed by server 1006 may alternatively be performed by user device 1002 and / or user device 1004. For example, server 1006 may perform operations of a corresponding DA client module (e.g., DA client module 229) of user device 1002 and / or user device 1004.

[0325] As indicated by arrow 1008, user device 1002 and user device 1004 initiate a video communication session (e.g., a video conference). In some examples, more than two user devices (e.g., four user devices) participate in the video communication session. In some examples, initiating a video communication session establishes one or more audio streams between each user device participating in the video communication session. For example, when initiating the video communication session, user device 1002 and user device 1004 establish a first audio stream between each other. For example, if a third user device were to join the video communication session, the third user device would establish a second audio stream between itself and user device 1002 and a third audio stream between itself and user device 1004. In some examples, the remaining steps of the technique (see below) Figure 10 ) occurs during an initiated video communication session between user device 1002 and user device 1004.

[0326] As shown by arrow 1010, user device 1002 receives user voice input. In some examples, the user voice input includes a digital assistant trigger word (e.g., "Hey, Siri," "Siri," etc.) that invokes the digital assistant of user device 1002 (e.g., initiating a conversation session between the user of user device 1002 and the digital assistant of user device 1002). For example, the user voice input may include a digital assistant trigger word at the beginning of the first user input (e.g., "Hey, Siri, what's the weather in Palo Alto?"). For another example, the user voice input may include a digital assistant trigger word at the end of the first user input (e.g., "What's the weather in Palo Alto, Siri?"). In some examples, in response to determining that the user voice input includes a digital assistant trigger word, user device 1002 determines that the user voice input represents a user request for the digital assistant of user device 1002 to perform one or more tasks (and in some examples, provide one or more digital assistant responses to the user request). For example, the user input "Hey, Siri, what's the weather in Palo Alto?" represents a user request for the digital assistant to retrieve and provide weather information for Palo Alto. In some examples, the user voice input does not include a digital assistant trigger word and, therefore, does not invoke the digital assistant of the user device 1002. In some examples, the user voice input does not include a digital assistant trigger word, but rather causes the digital assistant of the user device 1002 to determine and / or provide a digital assistant response (e.g., when the digital assistant is invoked via user selection of an affordance and / or a physical button press prior to the user device 1002 receiving the user voice input).

[0327] In some examples, in response to receiving the user voice input, user device 1002 transmits the user voice input (e.g., audio data representing the user voice input) to user device 1004. In some examples, user device 1002 transmits the user voice input to user device 1004 as a peer-to-peer transmission (e.g., using an audio stream established between the two user devices when the video communication session is initiated). In other examples, user device 1002 transmits the user voice input to server 1006, which then transmits the user voice input (e.g., audio data representing the user voice input) to user device 1004. In some examples, after receiving the user voice input, user device 1004 outputs the user voice input as an audio output (e.g., using speaker 211).

[0328] After receiving the user voice input, the user device 1002 generates a text representation based on the user voice input (e.g., using the STT processing module 730). Then, as indicated by arrow 1012, the user device 1002 transmits the generated text representation (e.g., data representing the text representation) to the server 1006. In some examples, the user device 1002 transmits the text representation along with contextual information associated with the user voice input to the server 1006. Examples of contextual information associated with the user voice input include (but are not limited to) the time (e.g., a timestamp) of the user device 1002 when the user voice input is received from the user, the location of the user device 1002 when the user voice input is received (e.g., determined by the GPS module 235), the orientation of the user device 1002 when the user voice input is received, etc.

[0329] As indicated by arrow 1014, server 1006 receives one or more additional text representations (e.g., data representing one or more additional text representations) from user device 1004. In some examples, the one or more additional text representations correspond to user voice input received by user device 1004 during the video communication session, and / or digital assistant responses provided by user device 1004 during the video communication session before and / or after user device 1002 receives the user voice input (as indicated by arrow 1010). Figure 10 Server 1006 is shown receiving one or more additional text representations (represented by arrow 1014) after server 1006 receives the text representation (represented by arrow 1012), but in some examples, server 1006 receives one or more additional text representations (e.g., corresponding to one or more user voice inputs and / or digital assistant responses) from user device 1004 before server 1006 receives the text representation from user device 1002 (e.g., as shown by arrow 1010).

[0330] In some examples, the user device 1004 transmits one or more additional text representations along with contextual information associated with one or more user voice inputs and / or one or more digital assistant responses corresponding to the one or more additional text representations to the server 1006. Examples of contextual information associated with the one or more user voice inputs include, but are not limited to, the time (e.g., timestamp) at which the user device 1004 received each user voice input from the user, the location (e.g., as determined by the GPS module 235) of the user device 1004 at the time each user voice input was received. Examples of contextual information associated with one or more digital assistant responses include, but are not limited to, the time (e.g., timestamp) at which the user device 1004 provided each digital assistant response (e.g., to other user devices participating in the video communication session), the location and / or orientation of the user device 1004 at the time each digital assistant response was provided by the user device 1004, and the like.

[0331] After receiving the text representation from user device 1002 and one or more additional text representations from user device 1004 (e.g., immediately after receiving each additional text representation), server 1006 adds the text representation and the additional text representation to a shared transcript. A shared transcript is a digital note, file, document, collection of text, etc. stored on server 1006 and shared among all user devices participating in the video communication session. Specifically, the shared transcript is "shared" because all user devices participating in the video communication session can transmit text representations (e.g., corresponding to user voice input and / or digital assistant responses) to server 1006 to be added to the shared transcript associated with the video communication session. In some examples, once a video communication session is established (e.g., between at least two user devices), a shared transcript associated with the video communication session is generated.

[0332] In some examples, server 1006 adds the text representation and the one or more additional text representations to the shared transcript based on the order in which server 1006 receives the text representation and the one or more additional text representations. For example, if server 1006 receives the one or more additional text representations before server 1006 receives the text representation from user device 1002, server 1006 adds the one or more additional text representations to the shared transcript (e.g., immediately after receiving the additional text representations) and subsequently adds the text representation to the shared transcript (e.g., immediately after receiving the text representation). In some examples, server 1006 uses contextual information received with the text representation and contextual information received with the one or more additional text representations to determine the order in which to add the text representation and the one or more additional text representations to the shared transcript. In this way, server 1006 accounts for any delays (e.g., network delays) in receiving the text representation and / or the one or more additional text representations from user device 1002 and / or user device 1004. Returning to the above example, if contextual information (e.g., user voice input and / or digital assistant response timestamps) received along with the text representation and one or more additional text representations indicates that user device 1002 received user voice input corresponding to the text representation before user device 1004 received and / or provided user voice input and / or digital assistant response corresponding to the one or more additional text representations, server 1006 will add the text representation to the shared transcription before adding the one or more additional text representations.

[0333] In some examples, server 1006 includes one or more indications in the shared transcript that, based on contextual information (e.g., timing information) received with the text representation and / or contextual information received with the one or more additional text representations, the two or more text representations correspond to user voice input and / or digital assistant responses received and / or provided simultaneously. For example, server 1006 may include an indication in the shared transcript that the text representation received from user device 1002 and one of the one or more additional text representations received from user device 1004 each correspond to user voice input received simultaneously by user device 1002 and user device 1004 (e.g., because their respective users spoke simultaneously during the video communication session). As will be described in more detail below, user device 1002 and / or user device 1004 may use such indications in the shared transcript to determine how to display (e.g., in a video communication session user interface) the two or more text representations corresponding to user voice input and / or digital assistant responses received and / or provided simultaneously by user device 1002 and user device 1004.

[0334] After adding the text representation and the one or more additional text representations to the shared transcript, server 1006 transmits the shared transcript to user device 1002 and user device 1004, as indicated by arrows 1016 and 1018, respectively. In some examples, server 1006 periodically transmits the shared transcript to user device 1002 and user device 1004 (and all other user devices participating in the video communication session) (e.g., every 1 second, 5 seconds, 10 seconds, etc.). In some examples, server 1006 transmits the shared transcript to user device 1002 and user device 1004 (and all other user devices participating in the video communication session) after server 1006 adds each text representation to the shared transcript. Thus, for example, server 1006 may transmit the shared transcript to user device 1002 and user device 1004 after adding the text representation (received from user device 1002) to the shared transcript but before adding the one or more additional text representations (received from user device 1004) to the shared transcript. Server 1006 may then transmit the shared transcript to user device 1002 and user device 1004 again after adding the one or more additional text representations to the shared transcript (e.g., transmitting the shared transcript after each of the one or more additional text representations is added).

[0335] In some examples, after receiving the shared transcript, user device 1002 and / or user device 1004 displays the text representation (e.g., the text representation and one or more additional text representations) included in the shared transcript (e.g., using touch-sensitive display system 212). In some examples, user device 1002 and / or user device 1004 displays the text representation as a user interface overlaying the video communication session. In some examples, one or more text representations included in the received shared transcript are already displayed as a user interface overlaying the video communication session. In these examples, displaying the text representations included in the shared transcript includes user device 1002 and / or user device 1004 displaying one or more text representations that have not yet been displayed, in addition to displaying the one or more text representations included in the shared transcript that have already been displayed. For example, user device 1002 and / or user device 1004 may display new text representations included in the shared transcript (i.e., those text transcripts that have not yet been displayed) below the text representations included in the shared transcript that have already been displayed. In this way, user device 1002 and / or user device 1004 may maintain one or more displayed text representations in a user interface and simply add new text representations to the user interface (eg, below the displayed text representations).

[0336] For example, Figure 11 An exemplary user interface for real-time transcription of a video communication session according to various examples is shown. Specifically, Figure 11User device 1100 (e.g., user device 104, 122, 200, or 600) is shown. User device 1100 is similar or identical to user device 1002, user device 1004, and / or user device 900. Figure 11 In the non-limiting exemplary embodiment shown in FIG, user device 1100 is a smartphone. In other embodiments, user device 1100 can be a different type of user device, such as a wearable device (e.g., a smartwatch or smart glasses), a tablet computer, a laptop, or a desktop computer. As shown, user device 1100 includes a display 1102. In some examples, user device 1100 includes one or more input devices (e.g., a touch screen of display 902, buttons 1110, a microphone, etc.).

[0337] exist Figure 11 , user device 1100 displays a video communication session interface 1104 on display 1102 (e.g., touch-sensitive display system 212). Video communication session interface 1104 is an exemplary user interface for a video communication session (e.g., a video conference) between two user devices (e.g., user device 1002 and user device 1004). In some examples, video communication session interface 1104 is similar to or identical to video communication session interface 904 (described above with reference to FIG. Figure 9 As shown, video communication session interface 1104 includes representations of three participants in the video communication session. Representation 1106A includes a view from a camera (e.g., optical sensor 164) of user device 1100 (e.g., user device 1002). Representation 1106B includes a real-time video feed from a second user device (e.g., user device 1004). In some examples, the representation (e.g., representation 1106B) includes a representative image of a user device that only provides audio data (e.g., because video data is not available). For example, the representative image may include one or more letters representing the participant (e.g., the first letter of the participant's contact name stored on user device 1100) and / or the participant's full name (e.g., the full participant's contact name stored on user device 1100). Representation 1106C includes a representative image of the digital assistant of user device 1100. As shown, the representative image of the digital assistant includes the letter "S" and the name "Siri." However, the representative image of the digital assistant is not limited to this example and may include any other image, letters, name, number, or combination thereof.

[0338] As shown, the video communication session interface 1104 includes a real-time transcript 1108. The real-time transcript 1108 includes multiple text representations of user voice input received by user devices participating in the video communication session and / or digital assistant responses provided by user devices participating in the video communication session. In addition, the real-time transcript 1108 includes a user name (e.g., Adam or John) corresponding to each text representation of the user voice input (e.g., to indicate the user device that received the user voice input from the user) and a digital assistant name (e.g., Siri) corresponding to each text representation of the digital assistant response. As described above, the multiple text representations included in the real-time transcript 1108 correspond to text representations included in one or more shared transcripts received by the user device 1100. The text representations included in the real-time transcript 1108 are "real-time" because they are displayed in real time in the video communication session interface 1104, or shortly (e.g., immediately, less than 1 second later, less than 2 seconds later, etc.) after the user device 1100 receives and / or provides the user voice input and / or digital assistant response corresponding to the text representation. For example, Figure 11 As shown, immediately or shortly after the real-time transcription “JOHN: Hi ADAM, what’s the weather like in Palo Alto?” is displayed on real-time transcript 1108, user device 1100 receives user voice input from John’s user device corresponding to the real-time transcription (e.g., because user device 1100 receives user voice input from John’s user device immediately or shortly after receiving the shared transcription including the text representation from one or more servers (e.g., server 1006)).

[0339] In some examples, user device 1100 displays one or more text representations (included in real-time transcript 1108) in different colors (e.g., each user device has a corresponding color) based on the user device participating in the video communication session that generated / provided the text representation. For example, the text representation in real-time transcript 1108 generated / provided by user device 1100 (i.e., the text representation beginning with "ADAM:") can be one color (e.g., white), while the text representation generated / provided by John's user device (i.e., the text representation beginning with "JOHN:") is another color (e.g., red).

[0340] In some examples, if user device 1100 determines that two or more text representations correspond to user voice input and / or digital assistant responses received and / or provided by two or more user devices (e.g., user device 1100 and John's user device) simultaneously participating in the video communication session, user device 1100 displays the two or more text representations in real-time transcript 1108 in a particular color (e.g., red, white, blue, etc.). As described above, in some examples, the shared transcript includes an indication that the two or more text representations included in the shared transcript correspond to user voice input and / or digital assistant responses received and / or provided simultaneously. Thus, in these examples, user device 1100 determines that the two or more text representations correspond to user voice input and / or digital assistant responses received and / or provided simultaneously based on the indication included in the shared transcript. Thereafter, user device 1100 displays the two or more text representations in one color (e.g., red) and displays all other text representations in real-time transcript 1108 (e.g., those that do not correspond to user voice input and / or digital assistant responses received and / or provided simultaneously) in another color (e.g., white). In this way, a user of user device 1100 (e.g., Adam) will be able to quickly determine which text representations included in real-time transcript 1108 correspond to concurrently received and / or provided user voice input and / or digital assistant responses.

[0341] In some examples, user device 1100 displays only a predetermined number of the most recent text representations (e.g., one, two, five, ten, etc.) in real-time transcript 1108 (e.g., rather than displaying all text representations included in the shared transcript). Thus, once user device 1100 displays the predetermined number of text representations in real-time transcript 1108, as user device 1100 displays new text representations in real-time transcript 1108, user device 1100 stops displaying older text representations in real-time transcript 1108. For example, if user device 1100 displays only six text representations in real-time transcript 1108 at a time (i.e., because the predetermined number of text representations is six), user device 1100 will display the next (e.g., most recent) text representation below “ADAM: OK.” and stop displaying the text representation “JOHN: Hi, ADAM, what's the weather like in Palo Alto?” In some examples, user device 1100 determines which text representations included in the shared transcript are the most recent based on the order in which server 1006 added the text representations to the shared transcript. In some examples, user device 1100 determines which text representations included in the shared transcript are most recent based on contextual information (e.g., timing information) corresponding to the text representations to which server 1006 provided the shared transcript.

[0342] return Figure 10After receiving the shared transcription, the user device 1002 determines one or more candidate tasks that can be performed by the digital assistant of the user device 1002 based on the text representation included in the shared transcription. Example candidate tasks include setting a reminder, creating a calendar event, setting an alarm, creating a new stored contact, requesting a service from a third-party application (e.g., requesting an Uber car using the Uber application), etc. For example, referring to Figure 11 , upon receiving a shared transcription that includes the text representation "Great. Please let me know your address when it changes.", the digital assistant of the user device 1100 may determine the candidate task for the reminder setting as "Tell John your address" based on the text representation. In some examples, the user device 1002 determines the one or more candidate tasks by performing natural language processing (e.g., using the natural language processing module 732) on one or more (e.g., all) text representations included in the shared transcription. In some examples, the user device 1002 performs natural language processing on the text representations included in each shared transcription that the user device 1002 receives during the video communication session. In some of these examples, the user device 1002 performs natural language processing on the one or more text representations included in the shared transcription only if the user device 1002 has not already performed natural language processing on the one or more text representations included in the shared transcription (i.e., if the one or more text representations were not included in a shared transcription that the user device 1002 previously received during the video communication session).

[0343] As indicated by arrow 1020, after user device 1002 determines one or more candidate tasks that can be performed by the digital assistant of user device 1002, user device 1002 presents the one or more candidate tasks. In some examples, presenting the one or more candidate tasks includes displaying the one or more candidate tasks on a display of user device 1002 during the video communication session and / or after the video communication session ends. In some examples, user device 1002 displays the one or more candidate tasks as text overlaying a video communication session user interface (i.e., during the video communication session). For example, user device 1002 may display the one or more candidate tasks as text included in a real-time transcript (e.g., real-time transcript 1108) in a video communication session user interface (e.g., video communication session interface 1104). In some examples, user device 1002 displays the one or more candidate tasks in a text message within a text messaging application (e.g., in a text messaging conversation between a user of user device 1002 and the digital assistant of user device 1002). In some examples, user device 1002 displays one or more candidate tasks in one or more notifications (e.g., displayed as text in a banner notification, included in a notification history interface, included in a notification in a lock screen interface, etc.). In some examples, user device 1002 displays one or more candidate tasks as one or more task suggestions (e.g., displayed in a lock screen interface, in a notification history interface, etc.).

[0344] In some examples, user device 1002 presents one or more candidate tasks in an audio output (e.g., with or without a corresponding user interface). In some examples, in response to user voice input (e.g., received during a private digital assistant session with a user of user device 1002 (during a video communication session) or after the video communication session ends) indicating a user request for one or more candidate tasks (e.g., "Hey, Siri, what do I do?"), user device 1002 presents the one or more candidate tasks in an audio output. In some examples, user device 1002 automatically presents the one or more candidate tasks in an audio output after the video communication session ends (e.g., immediately or a few seconds later). In some examples, the audio output (1) requests the user of user device 1002 to confirm or deny each of the one or more candidate tasks, (2) requests the user of user device 1002 to select at least one of the one or more candidate tasks for the digital assistant to perform, and / or (3) requests user permission to perform one of the one or more candidate tasks.

[0345] Automatically determining and presenting one or more candidate tasks based on text representations included in a shared transcript received during a video communication session (as described above) allows a digital assistant of a user device participating in a video communication session to proactively determine one or more tasks that a user of the user device may want the digital assistant to perform based on the conversation maintained during the video communication session. In this way, the digital assistant prevents the user from having to individually request such tasks, ensures that the user does not forget to request such tasks, and / or informs the user of tasks that the digital assistant is capable of performing (e.g., that the user was previously unaware of). This, in turn, improves the user's experience with the video communication session and the digital assistant of the user device.

[0346] 6. For providing digital assistant responses to common digital assistant requests received during a video communication session Systems and technologies

[0347] Figure 12 Systems and techniques for providing digital assistant responses to common digital assistant requests during a video communication session according to various examples are shown. System 1200 includes a user device 1202 (e.g., user device 104, 122, 200, 400, 600) and a user device 1204 (e.g., user device 104, 122, 200, 400, 600). In some examples, user device 1202 and user device 1204 are similar to or identical to user device 802 / 1002 and user device 804 / 1004, respectively. It should be appreciated that in these examples, any operations performed by user device 1202 and / or user device 1204 may alternatively be performed by one or more servers (e.g., DA server 106). For example, one or more servers may perform operations of corresponding DA client modules (e.g., DA client module 229) of user device 1202 and / or user device 1204.

[0348] As indicated by arrow 1206, user device 1202 and user device 1204 initiate a video communication session (e.g., a video conference, a virtual reality video conference, or an augmented reality video conference). In some examples, more than two user devices (e.g., four user devices) participate in the video communication session. In some examples, initiating a video communication session establishes one or more audio streams between each user device participating in the video communication session. For example, when initiating the video communication session, user device 1202 and user device 1204 establish a first audio stream between each other. For example, if a third user device were to join the video communication session, the third user device would establish a second audio stream between itself and user device 1002 and a third audio stream between itself and user device 1004. In some examples, the remaining steps of the technique (see below) Figure 12 ) occurs during an initiated video communication session between user device 1202 and user device 1204.

[0349] As indicated by arrow 1208, user device 1202 receives user voice input representing a public digital assistant request. A public digital assistant request is a user request for the digital assistant to perform one or more tasks based on contextual information (e.g., user device contextual state information, user-specific information and / or data, etc.) associated with at least two user devices participating in a video communication session (or in some examples, participating in a phone call). Some exemplary public digital assistant requests include “Hey, Siri, find a time for us to meet,” “Hey, Siri, play a song that John and I both like,” and “Hey, Siri, how long will it take John and I to get to Palo Alto?” As will be described in more detail below, in some examples, the digital assistant provides / outputs a single digital assistant response to the public digital assistant request. In other examples, the digital assistant provides / outputs more than one digital assistant response (e.g., two, three, or four responses) to the public digital assistant request.

[0350] After receiving the user voice input, the user device 1202 determines whether the voice input represents a public digital assistant request (rather than, for example, a request such as that described above). Figure 8 In some examples, determining whether the first user voice input represents a public digital assistant request includes user device 1202 determining whether contextual information from at least two user devices participating in the video communication session can be used to satisfy the user request included in the user voice input (e.g., to perform one or more tasks associated with the user request). For example, in response to receiving the user voice input "Hey Siri, find a time for us to meet," user device 1202 (more specifically, the digital assistant of user device 1202) may determine whether user-specific calendar information from user device 1202 and from user device 1204 (as described above with reference to Figure 8 As described above, this is one type of contextual information) that can be used to determine a time when users of the two devices can meet, and thus can be used to fulfill a user request included in the user voice input. Thus, in this example, the user device 1202 will determine that the user voice input "Hey Siri, find a time for us to meet" represents a public digital assistant request.

[0351] In some examples, determining whether the user voice input represents a public digital assistant request includes user device 1202 determining whether the user voice input refers to multiple participants of the video communication session. In some examples, user device 1202 determines that the user voice input refers to multiple participants of the video communication session based on whether the user voice input (e.g., audio data corresponding to the user voice input or a textual representation of the user voice input) includes appropriate names (e.g., stored contact names) of two or more participants of the video communication session. For example, if there are users named John and Adam who are participating in a video communication session (e.g., if John is a user of user device 1204 and Adam is a user of a third user device participating in the video communication session), user device 1202 may determine that the user voice input “Hey Siri, find a time for John, Adam, and me to meet” represents a public digital assistant request. In other words, at least because the user voice input includes the appropriate names of the two or more participants of the video communication session, user device 1202 will determine that “Hey Siri, find a time for John, Adam, and me to meet” represents a public digital assistant request.

[0352] In some examples, user device 1202 determines that the user voice input refers to multiple participants of the video communication session based on whether the user voice input includes at least one proper name and a first-person singular pronoun (e.g., "I (I or me)") of the video communication session participant. For example, if there is a user named John who is participating in the video communication session (e.g., if John is the user of user device 1204), user device 1202 may determine that the user voice input "Hey, Siri, play a song that John and I both like" represents a public digital assistant request. In other words, at least because the user voice input includes the proper name ("John") and the first-person singular pronoun ("I") of the video communication session participant, user device 1202 will determine that "Hey, Siri, play a song that John and I both like" represents a public digital assistant request.

[0353] In some examples, user device 1202 determines that the user voice input refers to multiple participants of the video communication session based on whether the user voice input includes at least one plural pronoun (e.g., "us," "they," "them," "both," "our," and / or "we"). For example, user device 1202 may determine that the user voice input "Hey Siri, find a time for us to meet" represents a public digital assistant request at least because the user voice input includes the plural pronoun ("we").

[0354] Note that in some examples, user device 1202 uses a combination of two or more of the above determinations to determine whether the received voice input represents a public digital assistant request. For example, the user device may determine that the user voice input is a public digital assistant request because contextual information from at least two user devices participating in the video communication session is available to satisfy the user request included in the user voice input and because the user voice input includes a plural pronoun.

[0355] If the user device 1202 determines that the user voice input represents a public digital assistant request, the user device 1202 then transmits the request to the user device 1204 (as described in more detail below with reference to arrow 1210). If the user device 1202 determines that the user voice input does not represent a public digital assistant request, the user device 1202 forgoes transmitting the request to the user device 1204 and, in some examples, obtains and / or outputs a digital assistant response based on the user voice input (e.g., as described above with reference to Figure 8 , arrow 808 and / or arrow 812).

[0356] In some examples, in response to receiving the user voice input and before determining whether the user voice input represents a public digital assistant request, user device 1202 transmits the user voice input (e.g., audio data or text data representing the user voice input) to user device 1204. In some examples, user device 1202 transmits the user voice input to user device 1204 as a peer-to-peer transmission (e.g., using an audio stream established between the two user devices when the video communication session is initiated). In other examples, user device 1202 transmits the user voice input to one or more servers (e.g., DA server 106), which then transmits the user voice input (e.g., audio data or text data representing the first user input) to user device 1204. In some examples, after receiving the user voice input, user device 1204 outputs the user voice input as an audio output (e.g., using speaker 211).

[0357] In some examples, in response to receiving user voice input and before determining whether the user voice input represents a public digital assistant request, the user device 1202 determines whether the user voice input (e.g., audio data corresponding to the user voice input or a textual representation of the user voice input) includes a digital assistant trigger word (e.g., "Hey, Siri," "Siri," etc.). In response to determining that the user voice input includes the digital assistant trigger word, the user device 1202 performs a call indication process or a call permission process (e.g., as described above with reference to Figure 8, as indicated by arrow 818) determines whether to (1) continue to determine whether the user voice input represents a common digital assistant request or (2) abandon determining whether the user voice input represents a common digital assistant request (and therefore abandon obtaining and / or providing a digital assistant response based on the user voice input).

[0358] In some examples, user device 1202 performs a call indication process. Specifically, in response to determining that the user input includes a digital assistant trigger word, user device 1202 (1) transmits an indication that its digital assistant has been invoked (transmitted to another user device participating in the video communication session) in response to determining that the user input includes a digital assistant trigger word; and (2) determines whether the user voice input was received before or after invoking the digital assistant of the other user device participating in the video communication session (based on any call indications recently received (e.g., received within the last 1 second, 5 seconds, or 10 seconds) from the other user devices participating in the video communication session). If user device 1202 determines that it received the user voice input after the invocation of the digital assistant of the other user device participating in the video communication session, user device 1202 abandons determining whether the user voice input represents a public digital assistant request (and therefore abandons obtaining and / or providing a digital assistant response based on the user voice input). Alternatively, if user device 1202 determines that it received the user voice input before the invocation of the digital assistant of the other user device participating in the video communication session, user device 1202 continues to determine whether the user voice input represents a public digital assistant request.

[0359] In some examples, user device 1202 performs a call permission process (also known as a "baton" passing process). Specifically, in response to determining that the user input includes a digital assistant trigger word, user device 1202 determines whether it currently holds a digital assistant call permission. If user device 1202 determines that it currently holds a call permission, user device 1202 proceeds to determine whether the user voice input represents a public digital assistant request.

[0360] If user device 1202 determines that it does not currently hold call permission, user device 1202 transmits a request for call permission to the other user devices participating in the video communication session. If user device 1202 receives call permission from another user device participating in the video communication session (e.g., user device 1204) within a predetermined time period after transmitting the request for call permission (e.g., 0.5 seconds, 1 second, or 2 seconds after transmitting the request), user device 1202 continues to determine whether the user voice input represents a public digital assistant request. However, if user device 1202 does not receive call permission from another user device participating in the video communication session within a predetermined time period after transmitting the request for call permission, user device 1202 abandons determining whether the user voice input represents a public digital assistant request (and therefore abandons obtaining and / or providing a digital assistant response based on the user voice input).

[0361] In some examples, instead of waiting for a predetermined time period to expire, user device 1202 abandons determining whether the user voice input represents a public digital assistant request in response to receiving a denied permission to invoke request from another user device participating in the video communication session. In some of these examples, user device 1202 will continue to wait to act on the user voice input (but will not completely abandon determining whether the user voice input represents a public digital assistant response) until user device 1202 receives permission to invoke or the permission to invoke request is denied from another user device participating in the video communication session.

[0362] In some examples, after user device 1202 gives up determining whether the user voice input represents a response from the public digital assistant (e.g., because user device 1202 never received permission to invoke and / or received a denial of a permission to invoke request) (e.g., immediately, 1 second later, etc.), user device 1202 displays (e.g., on touch-sensitive display system 212 of user device 1202) an indication that the digital assistant of user device 1202 is currently unavailable and / or an indication that the digital assistant of another user device participating in the video communication session is currently invoked. In some examples, user device 1202 continues to display the indication (or at least a portion of the indication) until its digital assistant is available again (e.g., because the digital assistant of another user device participating in the video communication session is no longer invoked).

[0363] As mentioned above Figure 8As illustrated by arrow 818 in FIG. 1 , the above-described call indication and call permission processes help prevent multiple digital assistants from being called concurrently during a video communication session. In this way, only one user device (of two or more user devices participating in the video communication session) can obtain / provide a digital assistant response based on user input during the video communication session at a time. This, in turn, maintains the appearance of a single digital assistant participating in the video communication session by, for example, preventing multiple overlapping digital assistant responses from being provided simultaneously (e.g., providing audio output of two digital assistant responses simultaneously). For more information on the call indication process and the call permission process, refer to the corresponding Figure 8 Description of arrow 818.

[0364] As indicated by arrow 1210, user device 1202 transmits a request to user device 1204, causing user device 1204 to provide user-specific information associated with the user voice input to user device 1202. The user-specific information includes information and / or data corresponding to the current user of the user device (e.g., the current user of user device 1204). Figure 8 Arrow 810 of FIG. 1 details an example of user-specific information and / or data. In some examples, the request for user-specific information associated with the user voice input is a request for user device 1204 to provide certain user-specific information (e.g., user-specific calendar entries for one or more specific dates, the user's favorite songs, the user's favorite restaurants, etc.). For example, if the user voice input is "Hey, Siri, find a time for John and me to meet today," user device 1202 may transmit a request to user device 1204 (in this example, John's user device) for data corresponding to John's calendar entries for today.

[0365] In some examples, a request for user-specific information associated with a user voice input is a request for user device 1204 to provide a certain type of user-specific information based on one or more domains of the user voice input (e.g., domains of ontology 760). For example, if user device 1202 determines that the user voice input "Hey, Siri, find a restaurant that John and I both like" corresponds to the "restaurant reservations" domain (e.g., based on a natural language processing result of a public digital assistant request), user device 1202 may transmit a request for user-specific restaurant information and / or preferences (e.g., recently visited restaurants, favorite restaurants, etc.) to user device 1204 (in this example, John's user device). For another example, if user device 1202 determines that the user voice input "Hey, Siri, play a song that John and I both like" corresponds to the "music playback" domain, user device 1202 may transmit a request for user-specific music information and / or preferences (e.g., recently played songs, favorite songs, etc.) to user device 1204. As another example, if user device 1202 determines that the user voice input “Hey, Siri, find a time we can meet” corresponds to the “schedule a meeting” domain, user device 1202 may transmit a request for user-specific calendar information (e.g., all user-specific calendar information rather than user-specific calendar entries for specific dates) to user device 1204.

[0366] In some examples, user device 1202 transmits a request to user device 1204 for user device 1204 to provide a predetermined set of one or more types of user-specific information to user device 1202 (rather than transmitting a request to user device 1204 for user-specific information associated with the user voice input). In other words, in these examples, user device 1202 transmits a request for a predetermined set of user-specific information types, regardless of the content of the public digital assistant request. In some examples, the predetermined set includes one or more of user-specific calendar information, user-specific restaurant information, user-specific music information, user-specific sports information, etc. Thus, for example, if the user voice input is “Hey, Siri, find a time for us to meet,” user device 1202 may transmit a request to user device 1204 for user device 1204 to provide a predetermined set of user-specific information including all user-specific calendar information and all user-specific music information.

[0367] In some examples, user device 1202 transmits a general request to user device 1204, causing user device 1204 to provide contextual information associated with the user voice input to user device 1202 (rather than transmitting a request for user-specific information associated with the user voice input to user device 1204). As described above, the contextual information associated with the user voice input includes, for example, the contextual state of the user device (e.g., the current location of the user device when the user voice input is received), contact information associated with the user voice input, user-specific information and / or data associated with the user voice input, conversation history information associated with the user voice input (and corresponding to the digital assistant conversation session during the video communication session), etc. Therefore, the general request for contextual information associated with the user voice input is a request for user-specific information associated with the user voice input as well as other types of contextual information associated with the user voice input (e.g., the contextual state of the user device, stored contact information, conversation history information, etc.). For example, if the user voice input is "Hey Siri, how long does it take John and I to get to Palo Alto," the user device 1202 may transmit a general request for contextual information such as the user's specific navigation preferences and the current location of the user device 1204. Figure 8 Arrows 810 detail various types of information and / or data, including contextual information, that one user device may provide to another user device during a video communication session.

[0368] In some examples, user device 1202 transmits the request for user-specific information and / or the general request for contextual information to one or more servers (rather than to user device 1204). In these examples, the one or more servers then relay the request for user-specific information and / or the general request for contextual information to user device 1204.

[0369] Determining whether a user voice input is a public digital assistant request and then transmitting a request for user-specific information (and / or contextual information) associated with the user voice input to another user device participating in the video communication session (if the user voice input is a public digital assistant request) allows users of the user devices participating in the video communication session to provide digital assistant requests in a more natural and conversational manner during the video communication session. For example, instead of two or more users having to individually provide the same digital assistant request during the video communication session (e.g., "Hey, Siri, when am I free today?"), a single user can provide a public digital assistant request (e.g., "Hey, Siri, find a time for us to meet."), and as will be described in more detail below, the user's user device can then obtain and provide one or more digital assistant responses that take into account the user-specific information (and / or contextual information) received from the other user devices (e.g., "John and you are both free today at 5:30 PM."). This, in turn, creates the appearance of a single digital assistant that participates with all user devices in the video communication session (as opposed to a separate digital assistant for each user device) and is aware of the context of each user / user device. This ultimately improves the video communication session experience for the users of the first user device and the second user device.

[0370] As indicated by arrow 1212, in response to receiving a request for user-specific information associated with the user voice input from user device 1202, user device 1204 retrieves the user-specific information associated with the user voice input (e.g., data representing the user-specific information) and transmits it to user device 1202. For example, user device 1204 transmits at least a portion of the requested user-specific information to user device 1202. In some examples, user device 1204 retrieves the user-specific information from a memory (e.g., memory 202 or memory 470) of user device 1204. In some examples, user device 1204 retrieves the user-specific information from one or more servers (e.g., DA server 106).

[0371] Similarly, in the above example where user device 1202 transmits a general request for context information associated with the user voice input (rather than a request for user-specific information) to user device 1204, user device 1204, in response to receiving the general request, retrieves context information associated with the user voice input (e.g., data representing the context information) and transmits it to user device 1202. In some examples, user device 1204 retrieves the context information from a memory of user device 1204. In some examples, user device 1204 retrieves the context information from one or more servers.

[0372] In some examples, the requested user-specific information is stored (e.g., locally or remotely) by a software application (e.g., a third-party software application) stored on user device 1204. In these examples, user device 1204 issues a request for the desired user-specific information to the software application, the software application retrieves the user-specific information (e.g., from a memory of user device 1204 and / or from one or more servers), and the software application then provides the requested user-specific information to user device 1204. After receiving the requested user-specific information from the software application, user device 1204 transmits the user-specific information to user device 1202. For example, if user device 1204 receives a request for user-specific calendar information (e.g., a request for user calendar entries for a specific date, a request for all user calendar entries, etc.) from user device 1202, user device 1204 may issue a request for the user-specific calendar information to a third-party calendar software application. In response to such a request, the calendar software application may retrieve the requested user-specific information from one or more third-party remote servers and then provide the retrieved user-specific information to user device 1204. User device 1204 may then transmit the user-specific calendar information to user device 1202. Other examples of user-specific information that user device 1204 may request from a software application (e.g., a third-party software application) stored on user device 1204 include, but are not limited to, user-specific music information, restaurant information, location information, sports information, messaging information, and any other type of user-specific information described above.

[0373] In some examples, user device 1204 transmits the requested user-specific information and / or contextual information to one or more servers (rather than user device 1202). In these examples, the one or more servers then relay the user-specific information and / or contextual information to user device 1202.

[0374] After receiving the user-specific information (or, in some examples, contextual information) from the user device 1204, the user device 1202 obtains a digital assistant response based on the user voice input (e.g., a natural language processi...

Claims

1. A method for video communication, comprising: During a video communication session between at least two user devices and at a first user device of the at least two user devices: receiving a first user input; obtaining a first digital assistant response based on the first user input; providing the first digital assistant response and contextual information associated with the first user input to a second user device of the at least two user devices; outputting the first digital assistant response; receiving a second digital assistant response and contextual information associated with a second user input, and outputting the second digital assistant response, wherein the second user input is received at the second user device, and Wherein the second digital assistant response is determined based on the second user input and the context information associated with the first user input.

2. The method of claim 1, wherein the contextual information associated with the first user input comprises a history of conversations between a digital assistant of the first user device and a user of the first user device during the video communication session. 3 . The method of claim 1 , wherein the context information associated with the first user input comprises data corresponding to a current location of the first user device when the first user device receives the first user input.

4. The method of any one of claims 1 to 3, wherein the first digital assistant response comprises at least one of: a natural language expression corresponding to a task performed by the digital assistant of the first user device based on the first user input; and Data retrieved by the digital assistant of the first user device based on the first user input.

5. The method of any one of claims 1 to 3, wherein obtaining the first digital assistant response comprises: performing one or more tasks based on the first user input; as well as The first digital assistant response is determined based on the results of the execution of the one or more tasks.

6. A method according to any one of claims 1 to 3, wherein providing the first digital assistant response and the context information associated with the first user input to the second user device includes transmitting the first digital assistant response and the context information associated with the first user input to the second user device.

7. The method of claim 6, wherein the first user device receives the second digital assistant response and the context information associated with the second user input from the second user device.

8. The method according to claim 6, further comprising: Prior to providing the first digital assistant response and the contextual information associated with the first user input to the second user device: The first user input is transmitted to the second user device using a first audio stream.

9. The method of claim 8, wherein the first digital assistant response is transmitted to the second user device using the first audio stream.

10. The method according to claim 6, further comprising: Before receiving the second digital assistant response: receiving the second user input; as well as The second user input is output.

11. The method of claim 10, wherein the first user device receives the second user input and the second digital assistant response using a first audio stream.

12. A method according to any one of claims 1 to 3, wherein the digital assistant of the second user device uses the context information associated with the first user input to disambiguate the second user input.

13. A method according to any one of claims 1 to 3, wherein the first digital assistant response and the second digital assistant response can also be output by the second user device.

14. The method of claim 13, wherein the second user device outputs the first digital assistant response before receiving the second user input, and Wherein, after the first user device receives the second digital assistant response, the second user device outputs the second digital assistant response.

15. The method according to any one of claims 1 to 3, further comprising: Before receiving the second digital assistant response: receiving an indication that a digital assistant of the second user device has been invoked; receiving a third user input; determining, based on the received indication, whether the digital assistant of the second user device was invoked prior to receiving the third user input; as well as Based on determining that the digital assistant of the second user device was invoked before receiving the third user input, abandoning obtaining a third digital assistant response based on the third user input.

16. The method according to any one of claims 1 to 3, further comprising: After outputting the second digital assistant response: receiving a fourth user input; According to determining that the fourth user input represents a user intention to provide a private digital assistant request: receiving a fifth user input; obtaining a fourth digital assistant response based on the fifth user input; forgoing providing the fourth digital assistant response and contextual information associated with the fifth user input to the second user device; as well as Output the fourth digital assistant response.

17. The method according to any one of claims 1 to 3, further comprising: Prior to providing the first digital assistant response and the contextual information associated with the first user input to the second user device: determining whether the context information includes private information stored on the first user device; and According to determining that the context information includes private information stored on the first user device: removing at least a portion of the private information from the contextual information; as well as The first digital assistant response and remaining contextual information associated with the first user input are provided to the second user device.

18. A first user equipment, comprising: monitor; one or more processors; Memory; and One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, wherein the one or more programs include instructions for: During a video communication session between the first user device and at least a second user device: receiving a first user input; obtaining a first digital assistant response based on the first user input; providing the first digital assistant response and contextual information associated with the first user input to the second user device; outputting the first digital assistant response; receiving a second digital assistant response and contextual information associated with a second user input, and outputting the second digital assistant response, wherein the second user input is received at the second user device, and Wherein the second digital assistant response is determined based on the second user input and the context information associated with the first user input.

19. A first user device according to claim 18, wherein the context information associated with the first user input includes a history of conversation between a digital assistant of the first user device and a user of the first user device during the video communication session.

20. The first user device of claim 18, wherein the context information associated with the first user input comprises data corresponding to a current location of the first user device when the first user input is received by the first user device.

21. The first user device of any one of claims 18 to 20, wherein the first digital assistant response comprises at least one of: a natural language expression corresponding to a task performed by the digital assistant of the first user device based on the first user input; and Data retrieved by the digital assistant of the first user device based on the first user input.

22. The first user device of any one of claims 18 to 20, wherein obtaining the first digital assistant response comprises: performing one or more tasks based on the first user input; as well as The first digital assistant response is determined based on the results of the execution of the one or more tasks.

23. A first user device according to any one of claims 18 to 20, wherein providing the first digital assistant response and the context information associated with the first user input to the second user device includes transmitting the first digital assistant response and the context information associated with the first user input to the second user device.

24. A first user device according to claim 23, wherein the first user device receives the second digital assistant response and the context information associated with the second user input from the second user device.

25. The first user device of claim 23, wherein the one or more programs further comprise instructions for: Prior to providing the first digital assistant response and the contextual information associated with the first user input to the second user device: The first user input is transmitted to the second user device using a first audio stream.

26. A first user device according to claim 25, wherein the first digital assistant response is transmitted to the second user device using the first audio stream.

27. The first user device of claim 23, wherein the one or more programs further comprise instructions for: Before receiving the second digital assistant response: receiving the second user input; and The second user input is output.

28. A first user device according to claim 27, wherein the first user device uses a first audio stream to receive the second user input and the second digital assistant response.

29. A first user device according to any one of claims 18 to 20, wherein the digital assistant of the second user device uses the context information associated with the first user input to disambiguate the second user input.

30. A first user device according to any one of claims 18 to 20, wherein the first digital assistant response and the second digital assistant response can also be output by the second user device.

31. The first user device of claim 30, wherein the second user device outputs the first digital assistant response before receiving the second user input, and Wherein, after the first user device receives the second digital assistant response, the second user device outputs the second digital assistant response.

32. The first user equipment according to any one of claims 18 to 20, wherein the one or more programs further comprise instructions for: Before receiving the second digital assistant response: receiving an indication that a digital assistant of the second user device has been invoked; receiving a third user input; determining, based on the received indication, whether the digital assistant of the second user device was invoked before receiving the third user input; and Based on determining that the digital assistant of the second user device was invoked before receiving the third user input, abandoning obtaining a third digital assistant response based on the third user input.

33. The first user equipment according to any one of claims 18 to 20, wherein the one or more programs further comprise instructions for: After outputting the second digital assistant response: receiving a fourth user input; According to determining that the fourth user input represents a user intention to provide a private digital assistant request: receiving a fifth user input; obtaining a fourth digital assistant response based on the fifth user input; forgoing providing the fourth digital assistant response and contextual information associated with the fifth user input to the second user device; as well as Output the fourth digital assistant response.

34. The first user equipment according to any one of claims 18 to 20, wherein the one or more programs further comprise instructions for: Prior to providing the first digital assistant response and the contextual information associated with the first user input to the second user device: determining whether the context information includes private information stored on the first user device; and According to determining that the context information includes private information stored on the first user device: removing at least a portion of the private information from the contextual information; and The first digital assistant response and remaining contextual information associated with the first user input are provided to the second user device.

35. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by one or more processors of a first user device having a display, cause the first user device to: During a video communication session between the first user device and at least a second user device: receiving a first user input; obtaining a first digital assistant response based on the first user input; providing the first digital assistant response and contextual information associated with the first user input to the second user device; outputting the first digital assistant response; receiving a second digital assistant response and contextual information associated with a second user input, and outputting the second digital assistant response, wherein the second user input is received at the second user device, and Wherein the second digital assistant response is determined based on the second user input and the context information associated with the first user input.

36. The computer-readable storage medium of claim 35, wherein the contextual information associated with the first user input comprises a history of conversation between a digital assistant of the first user device and a user of the first user device during the video communication session.

37. The computer-readable storage medium of claim 35, wherein the contextual information associated with the first user input comprises data corresponding to a current location of the first user device when the first user device receives the first user input.

38. The computer-readable storage medium of any one of claims 35 to 37, wherein the first digital assistant response comprises at least one of: a natural language expression corresponding to a task performed by the digital assistant of the first user device based on the first user input; and Data retrieved by the digital assistant of the first user device based on the first user input.

39. The computer-readable storage medium of any one of claims 35 to 37, wherein obtaining the first digital assistant response comprises: performing one or more tasks based on the first user input; as well as The first digital assistant response is determined based on the results of the execution of the one or more tasks.

40. A computer-readable storage medium according to any one of claims 35 to 37, wherein providing the first digital assistant response and the context information associated with the first user input to the second user device includes transmitting the first digital assistant response and the context information associated with the first user input to the second user device.

41. A computer-readable storage medium according to claim 40, wherein the first user device receives the second digital assistant response and the context information associated with the second user input from the second user device.

42. The computer-readable storage medium of claim 40, wherein the one or more programs further comprise instructions that, when executed by the one or more processors, cause the first user device to: Prior to providing the first digital assistant response and the contextual information associated with the first user input to the second user device: The first user input is transmitted to the second user device using a first audio stream.

43. The computer-readable storage medium of claim 42, wherein the first digital assistant response is transmitted to the second user device using the first audio stream.

44. The computer-readable storage medium of claim 40, wherein the one or more programs further comprise instructions that, when executed by the one or more processors, cause the first user device to: Before receiving the second digital assistant response: receiving the second user input; and The second user input is output.

45. The computer-readable storage medium of claim 44, wherein the first user device receives the second user input and the second digital assistant response using a first audio stream.

46. A computer-readable storage medium according to any one of claims 35 to 37, wherein the digital assistant of the second user device uses the context information associated with the first user input to disambiguate the second user input.

47. A computer-readable storage medium according to any one of claims 35 to 37, wherein the first digital assistant response and the second digital assistant response are also capable of being output by the second user device.

48. A computer-readable storage medium according to claim 47, wherein the second user device outputs the first digital assistant response before receiving the second user input, and wherein the second user device outputs the second digital assistant response after the first user device receives the second digital assistant response.

49. The computer-readable storage medium of any one of claims 35 to 37, wherein the one or more programs further comprise instructions that, when executed by the one or more processors, cause the first user device to: Before receiving the second digital assistant response: receiving an indication that a digital assistant of the second user device has been invoked; receiving a third user input; determining, based on the received indication, whether the digital assistant of the second user device was invoked before receiving the third user input; and Based on determining that the digital assistant of the second user device was invoked before receiving the third user input, abandoning obtaining a third digital assistant response based on the third user input.

50. The computer-readable storage medium of any one of claims 35 to 37, wherein the one or more programs further comprise instructions that, when executed by the one or more processors, cause the first user device to: After outputting the second digital assistant response: receiving a fourth user input; According to determining that the fourth user input represents a user intention to provide a private digital assistant request: receiving a fifth user input; obtaining a fourth digital assistant response based on the fifth user input; forgoing providing the fourth digital assistant response and contextual information associated with the fifth user input to the second user device; as well as Output the fourth digital assistant response.

51. The computer-readable storage medium of any one of claims 35 to 37, wherein the one or more programs further comprise instructions that, when executed by the one or more processors, cause the first user device to: Prior to providing the first digital assistant response and the contextual information associated with the first user input to the second user device: determining whether the context information includes private information stored on the first user device; and According to determining that the context information includes private information stored on the first user device: removing at least a portion of the private information from the contextual information; and The first digital assistant response and remaining contextual information associated with the first user input are provided to the second user device.

Images