Multi-modal input of voice commands

Abstract

The invention relates to multi-modal input of voice commands. Systems and processes for operating an intelligent automated assistant are provided. In one example process, a first input including activation of an affordance is received. A domain associated with the affordance is determined. A second input including user speech is received, wherein a user intent is determined based on the domain and the user speech. It is determined whether the user intent includes a command associated with the affordance. In accordance with a determination that the user intent includes a command associated with the affordance, a task to advance the command is performed.

Description

[0001] This application is a divisional application of the invention patent application with the application date of August 30, 2019, application number 201980053858.5, and invention name “Multimodal input of voice commands”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Application No. 62 / 739,020, filed on September 28, 2018, entitled “Multi-Modal Inputs for Voice Commands,” and U.S. Application No. 16 / 232,855, filed on December 26, 2018, entitled “Multi-Modal Inputs for Voice Commands,” the disclosures of each of which are hereby incorporated by reference in their entirety for all purposes. Technical Field

[0004] The present application relates generally to intelligent automated assistants, and more particularly to multimodal input of voice commands. Background Art

[0005] Intelligent automated assistants or digital assistants provide a favorable interface between human users and electronic devices. Conventional digital assistants can receive voice commands from users and process the commands to perform one or more tasks. However, conventional digital assistants have difficulties in ultimately performing the desired tasks. Certain tasks may be inherently difficult to perform based on voice input alone, such as tasks that require the specification of a set of precise parameters or keywords. In addition, natural language voice input often includes ambiguous terms, and conventional digital assistants may not be able to determine the meaning of one or more of these terms. Performing desired tasks based on non-voice input can be cumbersome and inefficient, such as using finger gestures on a display screen or interacting with physical controls. Such problems are exacerbated as the complexity of smart devices increases and taking into account the different experience levels of users. For example, digital assistants may be particularly difficult to deal with for novice users. Therefore, a system including multimodal input of voice commands is needed. Summary of the invention

[0006] The present invention provides a system and process for multimodal input including voice commands. In an exemplary process, at an electronic device, a first input including activation of an enable indication is received. A domain associated with the enable indication is determined. A second input including user voice is received. A user intent is determined based on the domain and the user voice. A determination is made as to whether the user intent includes a command associated with the enable indication. Based on a determination that the user intent includes a command associated with the enable indication, a task of advancing the command is performed. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 A block diagram is shown of a system and environment for implementing a digital assistant according to various examples.

[0008] 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.

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

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

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

[0012] Figure 5A An exemplary user interface of a menu of applications on a portable multifunction device is shown according to various examples.

[0013] Figure 5B An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is shown according to various examples.

[0014] Fig. 6A A personal electronic device according to various examples is shown.

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

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

[0017] Figure 7B According to various examples, Fig. 7A The capabilities of the digital assistant shown in .

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

[0019] FIG. 8A to FIG. 8D An exemplary process for multimodal input is shown.

[0020] Fig. 9 An exemplary process for multimodal input is shown.

[0021] Fig.10 An exemplary process for multimodal input is shown.

[0022] Fig.11 An exemplary process for multimodal input is shown.

[0023] Fig.12 An exemplary process for multimodal input is shown.

[0024] Fig.13 An exemplary process for multimodal input is shown.

[0025] FIG. 14A to FIG. 14B An exemplary process for multimodal input is shown.

[0026] FIG. 15A to FIG. 15B An exemplary process for multimodal input is shown.

[0027] Fig.16 An exemplary process for multimodal input is shown.

[0028] Fig.17 An exemplary process for multimodal input is shown.

[0029] Fig.18 An exemplary process for multimodal input is shown. DETAILED DESCRIPTION

[0030] In the following description of the examples, reference will be made to the accompanying drawings, in which specific examples that may be implemented are shown by way of illustration. 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.

[0031] Conventional devices often have difficulty performing desired tasks. Such problems are compounded when the tasks become more complex. Performing certain tasks may require many precise steps, and completing these steps through conventional means is often a challenging process. For example, a task for changing the date and time of a meeting within a calendar application may require many separate steps, such as opening the calendar application, selecting the appropriate date, finding the event, and so on. These steps can be time-consuming and confusing, especially for inexperienced users. Completing such tasks based on voice commands is equally challenging. For example, many users may not be familiar with voice interfaces, and experienced users may still face problems when digital assistants are unable to determine user intent based on ambiguous natural language input. As a result, the inability of the device to perform the desired task results in a poor user experience.

[0032] According to some systems, computer-readable media, and processes described herein, task execution is improved by providing multimodal input for voice commands. In one exemplary process, a first input is received, including activation of an affordance displayed on a device. For example, a user may activate an application on the home screen of the device via touch input. A domain associated with the affordance is determined, such as a geographic domain in the case of a map application. A second input including user speech is received, and user intent is determined based on the speech and the determined domain. The speech input may include a command associated with the affordance, such as inputting "find the nearest Italian restaurant." Based on determining that the user intent includes a command associated with the activated affordance, a task that advances the command is performed.

[0033] Although the following description uses the terms "first," "second," etc. to describe various elements, these elements should not be limited by the 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 different inputs.

[0034] The terms used in the description of the various described examples herein are for the purpose of describing specific examples only and are not intended to be limiting. As used in the description of the various described examples and in the appended claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses 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.

[0035] 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, the phrase "if it is determined that..." or "if [a stated condition or event] is detected" may be interpreted to mean "upon determining that..." or "in response to determining that..." or "upon detecting [a stated condition or event]" or "in response to detecting [a stated condition or event]," depending on the context.

[0036] 1. System and Environment

[0037] 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 "automatic 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 with steps and parameters designed to implement the inferred user intent, inputting specific requirements into the task flow according to 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.

[0038] Specifically, the digital assistant is capable of accepting user requests in the form of at least partially natural language commands, requests, statements, narrations and / or inquiries. Typically, the user requests to seek an informative answer or perform a task from the digital assistant. A satisfactory response to the user's request includes providing the requested informative answer, performing the requested task, or a combination of the two. For example, the user asks the digital assistant a question, such as "Where am I now?" Based on the user's current location, the digital assistant answers "You are near the West Gate of Central Park." The user also requests to perform a task, such as "Please invite my friends to my girlfriend's birthday party next week." In response, the digital assistant can confirm the request by saying "OK, right away", and then send a suitable calendar invitation to each of the user's friends listed in the user's electronic address book on behalf of the user. During the execution of the requested task, the digital assistant sometimes interacts with the user in a continuous dialogue involving multiple information exchanges over a long period of time. There are many other methods of interacting with the digital assistant to request information or perform various tasks. In addition to providing verbal responses and taking programmed actions, the digital assistant also provides responses in other video or audio forms, such as text, alarms, music, videos, animations, etc.

[0039] like Figure 1As 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") executed on a user device 104 and a server-side portion 106 (hereinafter referred to as "DA server 106") executed 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 user-oriented input and output processing, 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.

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

[0041] User device 104 can be any suitable electronic device. In some examples, user device 104 is a portable multi-function device (e.g., Figure 2A The device 200 described above), a multifunctional device (eg, as described below with reference to Figure 4 The device 400) or a personal electronic device (eg, as described below) FIG. 6A to FIG. 6B The portable multifunction device is, for example, a mobile phone that also includes other functions such as a PDA and / or a music player. 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 trackpad). 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.

[0042] Examples of one or more communication networks 110 include local area networks (LANs) and wide area networks (WANs), such as the Internet. One or more communication networks 110 are implemented using any known network protocols, 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.

[0043] The server system 108 is implemented on one or more stand-alone data processing devices or distributed computer networks. 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.

[0044] 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 Figure 2A , Figure 4 and FIG. 6A to FIG. 6BThe 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.

[0045] 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 (e.g., a mobile phone, laptop, tablet, etc.) with greater communication capabilities and / or battery power 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.

[0046] 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. In addition, the division of functionality between the client and server portions of the digital assistant may vary in different specific implementations. For example, in some examples, the DA client is a thin client that only provides user-facing input and output processing functions and delegates all other functions of the digital assistant to a backend server.

[0047] 2. Electronic devices

[0048] Attention now turns to embodiments of electronic devices for implementing the client-side portion of a digital assistant. Figure 2Ais a block diagram showing 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 a 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, an RF circuit 208, an audio circuit 210, a speaker 211, a microphone 213, an input / output (I / O) subsystem 206, other input control devices 216, and an external port 224. The device 200 optionally includes one or more optical sensors 264. The device 200 optionally includes one or more contact force sensors 265 for detecting the intensity of contact 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 touch pad 455 of device 400). These components optionally communicate via one or more communication buses or signal lines 203.

[0049] 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) of 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 substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute 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 the 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 functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0050] 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 the 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, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (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 corresponding 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" to 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 is physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although 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.

[0051] 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 the drawings are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0052] The memory 202 includes one or more computer-readable storage media. These computer-readable storage media are, for example, tangible and non-transitory. The memory 202 includes a high-speed random access memory and also includes a non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory controller 222 controls other components of the device 200 to access the memory 202.

[0053] 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, device, or apparatus, such as a computer-based system, a system containing a processor, or other system that can fetch instructions from an instruction execution system, device, or apparatus 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 are divided between the non-transitory computer-readable storage medium of memory 202 and the non-transitory computer-readable storage medium of server system 108.

[0054] 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.

[0055] RF (radio frequency) circuit 208 receives and sends RF signals, also known as electromagnetic signals. RF circuit 208 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 208 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memory, etc. RF circuit 208 optionally communicates with networks and other devices through 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 circuit 208 optionally includes well-known circuits for detecting near field communication (NFC) fields, such as through short-range communication radio components. 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.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 802.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 Utilizing 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.

[0056] The audio circuit 210, speaker 211, and microphone 213 provide an audio interface between a 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 circuit 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-ear headset or a dual-ear headset) and input (e.g., a microphone).

[0057] The I / O subsystem 206 couples input / output peripherals on the device 200, such as a touch screen 212 and other input control devices 216, to a 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. One or more input controllers 260 receive / send electrical signals from other input control devices 216. 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 of the following (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 in ) optionally includes an up / down button for volume control of the speaker 211 and / or the microphone 213. The one or more buttons optionally include a push button (e.g., Figure 3 306 in ).

[0058] A quick press of the push button may disengage the lock of the touch screen 212 or begin the process of using gestures on the touch screen to unlock the device, 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.

[0059] 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.

[0060] The touch screen 212 has a touch-sensitive surface, sensor, or sensor group that accepts input from a 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 (and any movement or interruption of the contact) on the touch screen 212 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.

[0061] 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, 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, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in.

[0062] 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, all of which are hereby incorporated by reference in their entirety. However, the touch screen 212 displays visual output from the device 200, whereas the touch-sensitive trackpad does not provide visual output.

[0063] 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 / 086,694, filed on January 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input and (9) U.S. patent application Ser. No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these applications are hereby incorporated by reference in their entirety.

[0064] The touch screen 212 has, for example, a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user contacts the touch screen 212 using any suitable object or appendage, such as a stylus, a finger, etc. In some embodiments, the user interface is designed to work 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 actions desired by the user.

[0065] In some embodiments, in addition to the touch screen, the device 200 also 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.

[0066] 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 circuits, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0067] The device 200 also includes one or more optical sensors 264 . Figure 2A An optical sensor coupled to an optical sensor controller 258 in the I / O subsystem 206 is shown. The optical sensor 264 includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 264 receives light projected through one or more lenses from the environment 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 a static image or video. In some embodiments, the optical sensor is located at the rear of the device 200, opposite to the touch screen display 212 at the front of the device, so that the touch screen display is used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located at the front of the device so that the user's image is obtained for video conferencing while the user views 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 (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 264 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

[0068] 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. The 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 contact on a touch-sensitive surface). The 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 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 rear of the device 200, opposite the touch screen display 212 located on the front of the device 200.

[0069] 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: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. 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 the touch screen 212 is disabled.

[0070] Device 200 optionally also includes one or more tactile output generators 267. Figure 2AA tactile output generator coupled to a tactile feedback controller 261 in the I / O subsystem 206 is shown. The tactile output generator 267 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 265 receives tactile feedback generation instructions from the tactile feedback module 233 and generates a tactile output 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 arranged in juxtaposition or proximity to a touch-sensitive surface (e.g., a touch-sensitive display system 212) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 200) or laterally (e.g., backward and forward 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.

[0071] Device 200 also includes one or more accelerometers 268 . Figure 2A An accelerometer 268 coupled to the peripheral device interface 218 is shown. Alternatively, the accelerometer 268 is coupled to the input controller 260 in the I / O subsystem 206. The accelerometer 268 performs as described in the following U.S. patent publications: 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 entirety. 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 one or more accelerometers 268 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 200.

[0072] 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, including information obtained from the device's various sensors and input control devices 216; and position information about the device's position and / or posture.

[0073] 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.

[0074] The communication module 228 facilitates communication with other devices through 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 port 224. The external port 224 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

[0075] 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 touchpad 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 press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is 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 stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 230 receives contact data from the touch-sensitive surface. Determining the movement of the 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 the contact point being 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 simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 230 and display controller 256 detect contact on the touch pad.

[0076] In some embodiments, the contact / motion module 230 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has "clicked" 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, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. In addition, in some specific implementations, 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).

[0077] The contact / motion module 230 optionally detects gesture input from a user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, 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 a 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.

[0078] 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, without limitation, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0079] 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, etc., along with coordinate data and other graphic attribute data if necessary, and then generates screen image data to be output to the display controller 256.

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

[0081] The text input module 234, which in some examples is a component of the graphics module 232, provides a soft keyboard for entering text in various applications (e.g., contacts 237, email 240, IM 241, browser 247, and any other application requiring text input).

[0082] 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 Pages widget, and the Maps / Navigation widget).

[0083] The digital assistant client module 229 includes various client-side digital assistant instructions to provide the client-side functions of the digital assistant. For example, the digital assistant client module 229 can accept sound input (e.g., voice input), text input, touch input and / or gesture input through various user interfaces of the portable multifunction device 200 (e.g., microphone 213, accelerometer 268, touch-sensitive display system 212, optical sensor 229, other input control devices 216, etc.). The digital assistant client module 229 can also provide output in the form of audio (e.g., voice output), output in the form of visual output and / or output in the form of 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 voice, 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.

[0084] 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 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.).

[0085] In some examples, the digital assistant client module 229 utilizes the various sensors, subsystems, and peripherals of the portable multifunction device 200 to collect additional information from the surrounding environment of 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, to the DA server 106 along with the user input to help infer the user's 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.

[0086] In some examples, 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 activities, background services, error logs, resource usage, etc., is provided to the DA server 106 as contextual information associated with the user input.

[0087] 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 implementing the user intent expressed in the user request.

[0088] 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 sub-modules of the digital assistant module 726 described below.

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

[0090] Contacts module 237 (sometimes referred to as address book or contact list);

[0091] Telephone module 238;

[0092] Video conferencing module 239;

[0093] Email client module 240;

[0094] Instant messaging (IM) module 241;

[0095] Fitness support module 242;

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

[0097] Image management module 244;

[0098] Video player module;

[0099] Music player module;

[0100] Browser module 247;

[0101] Calendar module 248;

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

[0103] A widget creator module 250 for forming a user-created widget 249-6;

[0104] Search module 251;

[0105] Video and music player module 252, which merges the video player module and the music player module;

[0106] Notepad module 253;

[0107] Map module 254; and / or

[0108] Online video module 255.

[0109] 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.

[0110] In combination with the touch screen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, the contact module 237 is used to manage an address book or contact list (for example, stored in the application internal state 292 of the contact 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 telephone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing telephone numbers or email addresses to initiate and / or facilitate communications via telephone 238, video conferencing module 239, email 240, or IM 241; and the like.

[0111] In conjunction with RF circuit 208, audio circuit 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 contact 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 completed. As described above, wireless communications use any of a variety of communication standards, protocols, and technologies.

[0112] 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 contact / 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.

[0113] In conjunction with RF circuit 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.

[0114] In conjunction 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 the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for telephone-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 such as those supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0115] 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, 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 (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing, and transmitting fitness data.

[0116] 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 the following operations: 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.

[0117] 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 slide show or album), and storing still images and / or video images.

[0118] 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, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0119] 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 calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0120] 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 the 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 the 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).

[0121] 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).

[0122] 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.

[0123] 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.).

[0124] 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.

[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 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.

[0126] 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 specific online video, and otherwise manage online videos in one or more file formats (such as 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 specific 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.

[0127] 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.

[0128] In some embodiments, the device 200 is a device on which the operation of a predefined set of functions is performed exclusively through a touch screen and / or a touch pad. By using a touch screen and / or a 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.

[0129] A predefined set of functions that are performed exclusively through a touch screen and / or a touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates the device 200 to a main menu, a home menu, or a root menu from any user interface displayed on the device 200. In such embodiments, a touchpad 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 touchpad.

[0130] 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).

[0131] 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 distributor module 274. In some embodiments, the application 236-1 includes an application internal state 292 that indicates one or more current application views 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) is 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.

[0132] 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 a 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.

[0133] Event monitor 271 receives event information from peripherals interface 218. 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.

[0134] 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).

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

[0136] 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.

[0137] Another aspect of the user interface associated with an application is a set of views, sometimes 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 level within a programmatic hierarchy of applications or a 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 correct input is determined at least in part based on the hit view of the initial touch that started the touch-based gesture.

[0138] The 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, the 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 the hit view determination module 272, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

[0139] 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, higher views in the hierarchy will still remain as actively participating views.

[0140] Event distributor module 274 distributes event information to event identifiers (e.g., event identifier 280). In embodiments including active event identifier determination module 273, event distributor module 274 delivers the event information to the event identifier determined by active event identifier determination module 273. In some embodiments, event distributor module 274 stores the event information in an event queue, which is retrieved by corresponding event receiver 282.

[0141] 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 is part of another module stored in memory 202, such as contact / motion module 230.

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

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

[0144] 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 orientation (e.g., from a longitudinal orientation to a transverse 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).

[0145] Event comparator 284 compares event information with predefined event or sub-event definitions, and based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 284 includes event definition 286. Event definition 286 includes the 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, 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 a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a 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.

[0146] In some embodiments, event definition 287 includes a definition of an event for a corresponding user interface object. In some embodiments, event comparator 284 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view 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 associated with a sub-event and the object that triggered the hit test.

[0147] 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.

[0148] When a corresponding event recognizer 280 determines that a sequence of sub-events does not match any event in event definition 286, the corresponding event recognizer 280 enters an event impossible, 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.

[0149] In some embodiments, the corresponding event identifier 280 includes metadata 283 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event identifiers. In some embodiments, metadata 283 includes configurable properties, flags, and / or lists that indicate how event identifiers 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.

[0150] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event identifier 280 activates the event handler 290 associated with the event. In some embodiments, the corresponding event identifier 280 delivers the 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 identifier 280 throws a tag associated with the identified event, and the event handler 290 associated with the tag obtains the tag and performs a predefined process.

[0151] 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 instruction delivers the event information to an event handler associated with a sub-event sequence or to an actively participating view. An event handler associated with a sub-event sequence or with an actively participating view receives the event information and executes a predetermined process.

[0152] 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.

[0153] 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.

[0154] It should be understood that the above discussion of event processing of user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 200, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal 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.

[0155] Figure 3A portable multifunction device 200 with a touch screen 212 according to some embodiments is shown. 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 these 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, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 200 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

[0156] 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.

[0157] 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 user identity module (SIM) card slot 310, an earphone 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 keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or 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 through a microphone 213. The device 200 also optionally includes one or more contact strength sensors 265 for detecting the strength of contact on the touch screen 212, and / or one or more tactile output generators 267 for generating tactile output for a user of the device 200.

[0158] Figure 44 is a block diagram of an exemplary multi-function device with a display and a touch-sensitive surface according to some embodiments. Device 400 does not have to be portable. In some embodiments, device 400 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). 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. Communication bus 420 optionally includes circuits (sometimes referred to as chipsets) that interconnect system components and control communications between system components. Device 400 includes an input / output (I / O) interface 430 with a display 440, which is typically a touch screen display. I / O interface 430 also optionally includes a keyboard and / or mouse (or other pointing device) 450 and a touchpad 455, a tactile output generator 457 for generating tactile output on device 400 (e.g., similar to the above reference 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 memory 470 may include one or more storage devices located away from the CPU 410. In some embodiments, the memory 470 stores information related to the 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 drawing module 480, presentation module 482, word processing module 484, website creation module 486, disk editing module 488, and / or spreadsheet module 490, while portable multifunction device 200( Figure 2A )'s memory 202 optionally does not store these modules.

[0159] 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.

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

[0161] Figure 5A An exemplary user interface of an application 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:

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

[0163] Time 504;

[0164] Bluetooth indicator 505;

[0165] Battery status indicator 506;

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

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

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

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

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

[0171] Icons for other apps, such as:

[0172] o Icon 524 labeled "Message" of IM module 241;

[0173] o An icon 526 labeled “Calendar” of the calendar module 248;

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

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

[0176] o An icon 532 labeled "Online Video" of the online video module 255;

[0177] ○ Icon 534 labeled “Stock Market” of the Stock Market Desktop Applet 249-2;

[0178] o An icon 536 labeled “Map” of the map module 254;

[0179] o Icon 538 labeled “Weather” of the Weather widget 249-1;

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

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

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

[0183] ○ 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 .

[0184] It should be pointed out that Figure 5A The icon labels shown in are exemplary only. For example, icon 522 of 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 the corresponding application icon includes the name of the application corresponding to the corresponding 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.

[0185] Figure 5B A touch-sensitive surface 551 (eg, touch screen display 212) is shown having a touch-sensitive surface 551 (eg, Figure 4 tablet or touch pad 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.

[0186] 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 principal 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 a contact with touch-sensitive surface 551 (eg, Figure 5B 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.

[0187] 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). As 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 contact, followed by ceasing to detect contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or a mouse and finger contact are optionally used simultaneously.

[0188] Fig. 6AAn exemplary personal electronic device 600 is shown. Device 600 includes a body 602. In some embodiments, device 600 includes a body 602 relative to devices 200 and 400 (e.g., Figure 2A-Figure 4 ) or some or all of the features described in the foregoing. In some embodiments, device 600 has a touch-sensitive display screen 604, referred to hereinafter as touch screen 604. As an alternative or in addition to touch screen 604, device 600 has a display and a touch-sensitive surface. As with devices 200 and 400, in some embodiments, touch screen 604 (or touch-sensitive surface) has one or more intensity sensors for detecting the intensity of contact (e.g., touch) being applied. 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 touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 600.

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

[0190] In some embodiments, the device 600 has one or more input mechanisms 606 and 608. The 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, may allow the device 600 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 600.

[0191] Figure 6BAn exemplary personal electronic device 600 is shown. In some embodiments, the device 600 includes a Figure 2A , Figure 2B and Figure 4 Some or all of the components described. 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. I / O portion 614 is connected to a display 604, which may have a touch-sensitive component 622 and, optionally, also a touch-intensity sensitive component 624. In addition, 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. Device 600 includes input mechanisms 606 and / or 608. For example, input mechanism 606 is a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 608 is a button.

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

[0193] 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, for example, cause the computer processors to perform the above-described techniques and processes. The computer-executable instructions are also stored and / or transmitted, for example, in any non-transitory computer-readable storage medium for use by or in conjunction with an instruction execution system, device, or apparatus, such as a computer-based system, a system containing a processor, or other system that can obtain instructions from an instruction execution system, device, or apparatus 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.

[0194] As used herein, the term “indicative representation” refers to, for example, a display in device 200, 400, and / or 600 ( Figure 2A , Figure 4 and Figure 6A-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.

[0195] 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. 5 , the particular user interface element is adjusted according to the detected input. In the case that a touch screen display (e.g., Figure 2A A touch sensitive display system 212 or Figure 5A In some implementations of the touch screen 212 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an 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 in accordance with 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 in accordance with 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 typically 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).

[0196] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a 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 starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). 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 when 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 give up performing the corresponding operation), rather than to determine whether to perform the first operation or the second operation.

[0197] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, a touch-sensitive surface receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the strength of the contact increases. In this example, the characteristic strength of the contact at the end position is based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., the swipe contact is only located at the portion at the end 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, a 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 depressions in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

[0198] The intensity of a contact on a 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 touchpad. 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 touchpad. In some embodiments, when a contact having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector according to 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.

[0199] 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 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 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.

[0200] 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 that the strength of the contact (or multiple contacts) increases to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting that the strength of the corresponding contact increases to above the press input strength threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and the strength of the contact subsequently decreases to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0201] 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 the 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 "upward stroke" 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).

[0202] For ease of explanation, optionally, 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 triggered in response to detecting any of the following: contact intensity increasing to 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 to below the press input intensity threshold, and / or contact intensity decreasing to 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.

[0203] 3. Digital Assistant System

[0204] Fig. 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) via one or more networks, such as Figure 1 In some examples, the digital assistant system 700 is Figure 1 Specific implementation of the server system 108 (and / or DA server 106) shown in . It should be noted that the digital assistant system 700 is only one example of a digital assistant system, and the digital assistant system 700 has more or fewer components than shown, combines two or more components, or may have a different configuration or layout of components. Fig. 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.

[0205] 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.

[0206] 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).

[0207] 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 and the user interface module 722 receive user input (e.g., voice input, keyboard input, touch input, etc.) and process the input accordingly. In some examples, for example, when the digital assistant is implemented on a stand-alone user device, the digital assistant system 700 includes components respectively corresponding to Figure 2A , Figure 4 , FIG. 6A to FIG. 6B Any of the components and I / O communication interfaces described for device 200, device 400, or device 600 in the digital assistant system 700. In some examples, the digital assistant system 700 represents a server portion of a specific implementation of a digital assistant 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).

[0208] In some examples, the network communication interface 708 includes one or more wired communication ports 712 and / or wireless transmission and reception circuits 714. 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 circuit 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 the digital assistant system 700 to communicate with other devices through 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).

[0209] 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 processes. One or more processors 704 execute these programs, modules, and instructions, and read data from or write data to data structures.

[0210] 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.

[0211] The communication module 720 facilitates communication between the digital assistant system 700 and other devices through the network communication interface 708. For example, the communication module 720 and the electronic devices (such as Figure 2A , Figure 4 , FIG. 6A to FIG. 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.

[0212] 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, icon, 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.).

[0213] 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 stand-alone user device, applications 724 include user applications such as games, calendar applications, navigation applications, or mail 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.

[0214] 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 a subset or superset 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.

[0215] 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: converting voice input into text; recognizing user intent expressed in natural language input received from a user; proactively eliciting and obtaining information needed to fully infer user intent (e.g., by disambiguating words, games, intents, etc.); determining a task flow for satisfying the inferred intent; and executing the task flow to satisfy the inferred intent.

[0216] In some examples, such as Figure 7B As shown in FIG. , the I / O processing module 728 can be Fig. 7A The I / O device 716 interacts with the user or through Fig. 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 when the user request is received, and / or information related to the user's surrounding environment when 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.

[0217] 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 produce a recognition result. 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 Fourier transform on the speech input to extract the 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 finally 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 5 highest ranked (n=5) candidate text representations are delivered to the natural language processing module 732 for intent inference.

[0218] Further 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.

[0219] In some examples, the STT processing module 730 includes a vocabulary of recognizable words and / or accesses the vocabulary via the speech-to-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 the words are associated with candidate pronunciations for the word "tomato". Additionally, vocabulary words are associated with custom candidate pronunciations based on previous speech input from the user. Such custom candidate pronunciations are stored in the STT processing module 730 and associated with a particular user via a user profile on the device. In some examples, the candidate pronunciations for the words are determined based on the spelling of the words 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.

[0220] In some examples, candidate pronunciations are ranked based on their prevalence. Ranked higher than Because the former is a 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, the candidate pronunciations are ranked based on whether the candidate pronunciation is a custom candidate pronunciation associated with the user. For example, a custom candidate pronunciation is ranked higher than a standard candidate pronunciation. This can be used to identify proper nouns with unique pronunciations that deviate from the standard pronunciation. In some examples, the candidate pronunciation is associated with one or more speech features such as geographic origin, country, or ethnicity. For example, the 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, ethnicity, 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 (eg, the most likely pronunciation).

[0221] 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 can then determine based on the lexical index 744 that the sequence corresponds to the word "tomato".

[0222] 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.

[0223] The digital assistant's natural language processing module 732 ("natural language processor") obtains 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 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 taken by the digital assistant 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.

[0224] 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 context information associated with the user request, for example, from the I / O processing module 728. The natural language processing module 732 optionally uses the context information to clarify, supplement and / or further qualify the information contained in the candidate text representation received from the STT processing module 730. The context information includes, for example, user preferences, 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 context information is dynamic and changes with the time, location, content, and other factors of the conversation.

[0225] In some examples, natural language processing is based on, for example, knowledge ontology 760. Knowledge ontology 760 is a hierarchical structure containing many nodes, each node representing an "executable intent" or an "attribute" related to one or more of the "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. "Attributes" represent parameters associated with sub-aspects of an executable intent or another attribute. The connection between executable intent nodes and attribute nodes in knowledge ontology 760 defines how the parameters represented by the attribute nodes are subordinate to the tasks represented by the executable intent nodes.

[0226] In some examples, the knowledge ontology 760 is composed of executable intent nodes and attribute nodes. In 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, 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).

[0227] 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.

[0228] Executable intent nodes, together 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 ontology 760 shown in includes an example of a restaurant reservation domain 762 and an example of a reminder domain 764 within the ontology 760. The restaurant reservation domain includes an executable intent node "restaurant reservation", attribute nodes "restaurant", "date / time" and "party size", and sub-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 ontology 760 consists 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., itinerary scheduling domain, travel booking domain, movie ticket domain, etc.).

[0229] although Figure 7C Two exemplary domains within 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," etc. 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, for example, by child attribute nodes such as "recipient name" and "message address."

[0230] In some examples, ontology 760 includes all domains (and thus executable intents) that a 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.

[0231] 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. Executable intent nodes related to travel include "ticket booking", "hotel booking", "car rental", "get directions", "find points of interest", and so on. Executable intent nodes under the same superdomain (e.g., the "travel" superdomain) have multiple shared attribute nodes. For example, the executable intent nodes for "ticket 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".

[0232] 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 a so-called "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 , the vocabulary associated with the node of the "restaurant" attribute includes words such as "food", "drinks", "cuisine", "hunger", "eat", "pizza", "fast food", "meals", etc. For another example, the vocabulary associated with the node of 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.

[0233] 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 involve. In some examples, if a word or phrase in the candidate text representation is found to be associated with one or more nodes in the knowledge ontology 760 (via the vocabulary index 744), 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 nodes, such as whether the digital assistant has previously correctly interpreted similar requests from the user.

[0234] 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 for 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 qualify the user's intent. For example, for 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.

[0235] 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.

[0236] Additional details of searching knowledge 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.

[0237] In some examples, once the natural language processing module 732 identifies an executable intent (or domain) based on a user request, the natural language processing module 732 generates a structured query to represent the identified executable intent. In some examples, the structured query includes parameters for one or more nodes within the domain of the executable intent, and at least some of the parameters are filled with specific information and requirements specified in the user request. For example, the user says "help me reserve a seat at 7pm at the sushi restaurant." 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, the structured query of the "restaurant reservation" domain includes parameters such as {cuisine}, {time}, {date}, {party number}, etc. In some examples, based on 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, wherein the partial structured query includes parameters {cuisine = "sushi type"} and {time = "7pm"}. However, in this example, the user utterance contains insufficient information to complete the structured query associated with the domain. Therefore, based on the currently available information, other necessary parameters such as {number of party members} 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.

[0238] In some examples, the natural language processing module 732 identifies multiple candidate executable intentions 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 completely) for each identified candidate executable intention. The natural language processing module 732 determines the intent confidence score for each candidate executable intention and ranks the candidate executable intention 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 intentions 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 intentions are provided to the task flow processing module 736 together with the corresponding one or more candidate text representations.

[0239] 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 model 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.

[0240] 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, and a task flow for performing actions associated with an executable intent.

[0241] As described above, in order to complete the structured query, the task flow processing module 736 needs to initiate an additional dialogue with the user in order to obtain additional information and / or clarify the utterances that may be ambiguous. When it is necessary to conduct such an interaction, the task flow processing module 736 calls the dialogue flow processing module 734 to participate in the dialogue with the user. In some examples, the dialogue flow processor module 734 determines how (and / or when) to request additional information from the user, and receives and processes the user response. The question is provided to the user and the answer is received from the user through the I / O processing module 728. In some examples, the dialogue flow processing module 734 presents the dialogue output to the user via an audible output and / or a visual output, and receives input from the user via a verbal or physical (e.g., click) response. Continuing the above example, when the task flow processing module 736 calls the dialogue flow processing module 734 to determine the "party number" and "date" information for the structured query associated with the domain "restaurant reservation", the dialogue flow processing module 734 generates questions such as "how many people in a row?" and "which day to book?" and passes them to the user. Once the answer is received from the user, the dialog flow processing module 734 fills in 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.

[0242] 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 can perform the following steps: (1) Log in to the server of ABC Cafe or such A restaurant reservation system that (2) enters date, time, and party size information into a form on the website, (3) submits the form, and (4) creates a calendar entry for the reservation in the user's calendar.

[0243] In some examples, the task flow processing module 736 completes the task requested in the user input or provides the informational answer requested in the user input with the assistance of the service processing module 738 ("service processing module"). 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., restaurant reservation portals, social networking sites, bank portals, 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 models 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 according to the protocol and API required by the service based on the service model.

[0244] For example, if the 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.

[0245] In some examples, the natural language processing module 732, the dialog 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 finally generate a response (i.e., output to the user, or complete the task) to meet the user's intention. The generated response is a dialogue response to the voice input that at least partially meets 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 a 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.

[0246] 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 query 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 query received based on the 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 the processing of the first structured query (e.g., due to the inability to determine the necessary parameters), the task flow processing module 736 may continue to select and process the second structured query corresponding to the executable intent with a lower ranking in the received structured query. For example, the second structured query is selected based on the speech recognition confidence score represented by the corresponding candidate text, the intent confidence score of the corresponding candidate executable intent, the missing necessary parameters in the first structured query, or any combination thereof.

[0247] 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 an 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: concatenation synthesis, unit selection synthesis, diphone synthesis, domain-specific synthesis, formant synthesis, pronunciation synthesis, synthesis based on hidden Markov model (HMM) 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 string is associated with the words in the generated dialogue response. The phoneme string is stored in the metadata associated with the word. The speech synthesis processing module 740 is configured to directly process the phoneme string in the metadata to synthesize the words in speech form.

[0248] In some examples, instead of (or in addition to) using the speech synthesis processing module 740, 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.

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

[0250] 4. Multimodal input of voice commands

[0251] 8 to 15 show electronic devices. Fig. 8A As shown, the electronic device 800 may be any device described herein, including but not limited to devices 104, 200, 400, and 600 ( Figure 1 , Figure 2A , Figure 4 and FIG. 6A to FIG. 6B ). Thus, while the electronic devices depicted in FIGS. 8-15 may be depicted as mobile devices, it should be understood that the electronic devices may be any type of device, such as a phone, a laptop computer, a desktop computer, a tablet computer, a wearable device (e.g., a smart watch), a set-top box, a television, a home automation device (e.g., a thermostat), or any combination or subcombination thereof. In addition, the processes described herein may be performed by a server having information delivered to and from a device, information executed on a device, or a combination thereof.

[0252] FIG. 8A to FIG. 8DAn exemplary process for multimodal input is shown. For example, user 802 may interact with electronic device 800 to perform an Internet search based on both touch input and voice input. In operation, electronic device 800 may receive a first input including activation of an affordance. For example, user 802 may contact the touch-sensitive screen of device 800 to activate affordance 804. Affordances may be associated with one or more functions of a device. For example, affordances may be associated with an application of a device or with a function corresponding to an application of a device. Applications of a device may include applications for calendaring, sending and receiving messages (e.g., emails and / or text messages), initiating and receiving phone calls, browsing the Internet, capturing and viewing photos, viewing maps, listening to music, etc. In some examples, affordances are associated with functions of applications corresponding to devices. In some examples, affordances may be predefined graphical objects on a screen. For example, affordances may include selectable elements displayed on a screen, such as selectable images (e.g., icons corresponding to applications), selectable buttons (e.g., functions within applications), selectable text (e.g., one or more displayed words). For example, an affordance can be a thumbnail of a photograph, a link or other element on a web page, a song or album within a music application, a calendar event, an email or text message, a location or area of ​​a map, a location or area of ​​a virtual or other 3D environment, an element within a game or other simulation, or a location or area associated with any application or other element on a screen.

[0253] In some examples, the affordance may correspond to a general area of ​​displayed content based on user input. For example, the affordance may be associated with one or more photos, such as a portion of a photo. For example, because a user may open a photo within a photo application and touch a specific area of ​​the displayed photo, such as a dark area in the corner of the photo. This portion of the photo may correspond to a predetermined area around the photo, such as a circle or rectangle with a predetermined area whose center is located at the location of the user input. The affordance may therefore correspond to a predetermined area of ​​the photo based on the user input.

[0254] In some examples, receiving a first input including activation of the affordance 804 may include detecting different types of inputs. For example, a user input may be associated with different pressures such that the affordance is activated by an input associated with a pressure greater than a predetermined threshold. In some examples, when a user presses the affordance with a pressure greater than a predetermined threshold, the affordance is activated. In some examples, when a user presses the affordance with a pressure less than a predetermined threshold, the affordance is not activated. The predetermined threshold may be further adjusted by the user or otherwise adjusted to optimize the detection of user input for affordance activation. In some examples, multiple user inputs may be detected to activate affordances. For example, a user may "tap" the affordance multiple times, and such taps may have different durations. In some examples, a first tap may have a shorter duration, and a second tap at the same location as the first tap may have a longer duration. In some examples, one or more other gestures on the device screen may cause activation of the affordance. For example, a user may tap on a location on the screen and perform a gesture to draw a circle or other shape around a particular portion of the screen. For example, in a map application, a user may draw a circle around a specific area of ​​a city or state displayed on the map. In a photo, a user may, for example, draw a rectangle around a specific portion of the photo. In some examples, affordances may be activated by other means, such as based on eye tracking of the user's gaze.

[0255] In some examples, the affordance may be activated via a second device. For example, the affordance may be displayed on a device such as a television via a set-top box, and activation of the affordance may include receiving input from an auxiliary device such as a remote controller or a smart phone. In some examples, a smart phone or a remote controller may communicate with a set-top box to interact with different affordances displayed on an associated television. For example, a user may interact with a smart phone to focus on different affordances displayed on the television, and the affordances displayed may be activated by any means discussed herein, such as by varying pressure levels, different taps, swipe gestures, etc. For example, one or more media items (e.g., movies or programs) may be displayed on the television, and a user may activate the media items by pressing an input on the auxiliary device while focusing on the media items displayed on the television.

[0256] In some examples, activation of an affordance may cause one or more outputs to be displayed on the screen. Figure 8B, in response to user 802 activating an affordance 804, an output 806 is displayed near the activated affordance 804. In some examples, output 806 may include a temporary enlargement of the activated affordance, a "halo" around the activated affordance, or a visual vibration of the activated affordance. In some examples, the output may be displayed at another location on the screen of the device, such as in a corner of the screen and / or at the top or bottom of the screen. In some examples, in addition to or in place of a visual output, the output may include one or more tactile outputs or auditory outputs. The output displayed in response to activation of the affordance may signal the user that the user may begin voice input associated with the activated affordance. For example, an auditory output, a visual output, and / or a tactile output that also corresponds to the voice recognition function of the device may be provided to the user so as to indicate to the user that voice recognition has begun or will soon begin.

[0257] In some examples, electronic device 800 determines a domain associated with an affordance. For example, when user 802 activates affordance 804, a domain associated with affordance 804 is determined. The domain associated with an affordance may, for example, represent a general function corresponding to the affordance. The domain associated with an affordance may be further associated with a corresponding executable intent and one or more attribute nodes, as described herein. For example, an affordance corresponding to a restaurant reservation application may be associated with an executable intent node "restaurant reservation", and may further correspond to attribute nodes "restaurant", "date / time", and "number of companions", as well as sub-attribute nodes "cuisine", "price range", "telephone number", and "location". For example, the domain associated with an affordance may also include multiple domains, or may include all domains that a digital assistant can understand or function with.

[0258] In some examples, determining the domain associated with the affordance includes determining at least one attribute associated with the activated affordance. For example, affordance 804 may correspond to a web browser application, wherein the web browser application is associated with an internet search attribute. In some examples, the attributes associated with affordance may be weighted, prioritized, or otherwise sorted based on past user interactions, device history, device location, and the like. For example, if user 802 frequently visits websites related to cooking or cuisine, the web browser application may be associated with an internet search attribute, wherein the cuisine attribute is prioritized. In some examples, at least one executable intent node corresponding to at least one determined attribute is identified. For example, in response to determining that affordance 804 is associated with an internet search attribute, an executable intent node corresponding to an internet search is identified. In some examples, the attributes associated with the activated affordance include verbs or phrases commonly used to trigger functions corresponding to the activated affordance. For example, affordance 804 corresponding to a web browser may be associated with verbs or phrases such as "find", "go to", "search", "what", wherein then such verbs or phrases are usually followed by the content that the user wishes to perform an internet search or the website that the user wishes to visit. As further discussed herein, a domain may be determined based on at least one attribute including a common verb or phrase such that user intent may be determined without requiring the user to speak such a verb or phrase when activating an affordance and providing speech to the device.

[0259] In some examples, electronic device 800 receives a second input comprising a user voice. For example, upon activating affordance 804 corresponding to a web browser, user 802 may provide voice 808 comprising the phrase "best restaurants in Cupertino" with the goal of opening a web browser to perform an Internet search for restaurants in Cupertino, California. Input comprising voice 808 may be received directly from user 802 at device 800, or may be received from an auxiliary device. For example, where the activated affordance corresponds to an affordance on a television, the user may provide voice via an auxiliary device such as a remote controller, a smart phone, a watch, a Bluetooth headset, a speaker, etc.

[0260] In some examples, the audio input is sampled in order to receive a second input including the user's voice. For example, the audio input may be sampled before the first input of the enable indication is activated, or the audio input may be sampled when the enable indication is activated. In some examples, audio data of a predetermined duration is stored continuously, such as the audio of the most recent duration. Based on receiving the first input, the received audio data of a predetermined duration is obtained, and at least a portion of the second input including the user's voice is received from the received audio data of the predetermined duration. For example, if the user begins to provide voice input 808, but has not yet activated the enable indication 804, when the user activates the enable indication 804 shortly after starting to speak, based on the stored audio of the predetermined duration, the complete voice input "Best restaurant in Cupertino" is still captured.

[0261] In some examples, the audio input is sampled based on whether the first input is maintained. For example, the user 802 can activate the enable representation 804 by pressing and holding on the enable representation 804, and the audio input can be sampled in response to detecting that the user 802 has maintained the input on the enable representation 804 for a predetermined duration or by using a predetermined amount of pressure. In some examples, the audio input is sampled in response to detection, and sampling continues until it is determined that the user 802 no longer maintains the input on the enable representation 804. In some examples, sampling continues until it is determined that the user is no longer speaking. For example, the sampling of the audio input can be triggered by one or more user inputs on the enable representation 804, and audio sampling can continue regardless of whether the user maintains contact with the enable representation. Then determine whether the audio of a predetermined duration, such as the most recent duration, includes the user's voice. Based on determining that the audio of the predetermined duration does not include the user's voice, the sampling of the audio input is terminated.

[0262] In some examples, the electronic device 800 determines the user intent based on the domain and the user voice. For example, the STT processing module 730 may generate multiple candidate text representations of the voice input, and the candidate text representations are passed to the natural language processing module 732 for intention inference based on the identified domain, as described herein. For example, based on determining that the affordance representation 804 is associated with an Internet search attribute, an executable intent node for Internet search is used as the basis for intent determination. In some examples, the candidate text interpretations may be weighted or prioritized based on the activated affordance representation 804 or at least one attribute associated with the activated affordance representation 804. For example, in the case where the user activates the contact application and the user has a contact named "Bob Mills" (as opposed to a store named "Nob Hill"), the weight of the candidate text representation of "Call Bob Mills" may be higher than the weight of the candidate text representation of "Call Nob Hill". In some examples, the activated affordance representation 804 or at least one attribute associated with the activated affordance representation 804 may invalidate the candidate text representation. In some examples, the natural language processing module 732 associates each candidate text representation in the candidate text representation with one or more executable intents associated with an executable intent node for Internet search. The executable intent node for Internet search can be linked to attribute nodes related to Internet search, such as attribute nodes related to the type of search query, location constraints, user preferences, saved websites, etc. In some examples, as discussed herein, the domain can be determined based on at least one attribute including a verb or phrase associated with an activated affordance (e.g., "find", "go to", "search" and / or "what" associated with affordance 804 including a web browser application). For example, the device 800 can determine the user's intent without the user referring to such verbs or phrases. For example, based on the domain corresponding to the web browser application and the user voice "the best restaurant in Cupertino", the device 800 can determine that the user intends to search for restaurants in Cupertino, so that the complete search query can be expressed as "find the best restaurant in Cupertino".

[0263] In some examples, in response to receiving a second input including speech, one or more outputs are provided. Figure 8C, a transcription 810 of the user's speech 808 may be provided. In some examples, the transcription 810 may be provided in response to the user providing the speech. In some examples, the transcription 810 is provided when the user is providing the speech to the device, so that different characters or words are displayed sequentially when the user speaks. For example, the transcription 810 may occupy a predetermined area of ​​the screen, such as the top, middle, or bottom of the screen. In some examples, the transcription 810 is provided by displaying the transcription near the activated affordance 804, such as above, below, to the left, to the right, or near the corner of the activated affordance 804. In some examples, a transcription output area associated with the transcription 810 is provided before receiving a second speech input (e.g., an "empty" transcription), so that the transcription output area is provided in response to receiving an input including activation of the affordance 804. For example, the user may activate the affordance 804, and in response, a transcription output area including an empty transcription is displayed to indicate that the device is sampling audio data. In response to receiving a second input including speech, an output including the transcription 810 is provided in the transcription output area. In some examples, the display of transcript 810 or the transcript output area dims and / or blurs the background content, so that the focus on the output and / or activated affordance is enhanced. In some examples, transcript 810 may occupy the entire screen and disappear after a predetermined amount of time. In some examples, transcript 810 may be associated with a predetermined opacity, and such opacity may be further dynamically adjusted based on the displayed content, user preferences, or other contextual information.

[0264] In some examples, the electronic device 800 determines whether the user intent includes a command associated with the affordance. In some examples, the command may be determined based at least in part on the user voice, the activated affordance, the displayed content, or other contextual information. For example, based on determining that the user intent corresponds to an internet search, determining the user intent includes invoking a web browser to perform an internet search based on user voice input, such as based on voice input 808 of “best restaurants in Cupertino.”

[0265] In some examples, based on determining that the user intent includes a command associated with the affordance, the electronic device 800 performs a task to advance the command. Fig.8D, based on determining that the user intent includes a command to perform an Internet search, the device 800 determines whether the Internet search corresponds to an activated affordance 804 associated with the web browser. The device 800 may determine that the web browser includes functionality for performing an Internet search, thereby determining that the user intent includes a command associated with affordance 804. In response to the determination, a task is performed, such as opening a web browser 812. The task may also include automatically populating a search field 814 that includes a transcription of the user's speech 802, such as "best restaurants in Cupertino." In some examples, relative to the command to perform an Internet search, the task may also include performing an Internet search based on the transcription of the user's speech, and displaying results 816 based on the search performed.

[0266] In some examples, as disclosed herein, affordance 804 may correspond to a web browser application, wherein activation of affordance and subsequent voice input facilitates performance of a corresponding task by invoking the application. In some examples, affordance 804 may correspond to other applications, such as applications for maps, restaurant reviews, weather, music, activity monitoring, health, video (e.g., stored video or live stream), social media, sports, navigation, online shopping, games, finance, driving services, and the like. For example, a user may activate an affordance of a map application and provide a voice input including "directions to home", causing the map application to be invoked, wherein the destination is automatically populated with the user's home based on the user profile information. For another example, a user may activate an affordance of a restaurant review application and provide a voice input including "how is John's Restaurant", causing the restaurant review application to be invoked along with a displayed review page for "John's Restaurant". For another example, a user may activate an affordance of a music application and provide a voice input including "play classic rock songs", causing the music application to be invoked and further causing songs corresponding to a "classic rock" playlist to be played through one or more speakers of the device.

[0267] Fig. 9An exemplary process for multimodal input is shown. For example, user 902 may interact with electronic device 900 to perform one or more actions within calendar application 904. In some examples, a first input including activation of an affordance is received, such as activation of affordance 904. For example, affordance 904 may be associated with a calendar entry within calendar application 904. Other affordances within the calendar application may be activated, such as affordances for searching, affordances for moving to different views, or affordances for selecting a specific date and / or time (such as a specific hour of a day, a number of days of a month, a month of a year, or a specific year). In some examples, a domain associated with affordance 904 is determined. For example, a domain associated with one or more of "events", "schedules", "meetings", "planning", etc. may be determined based on activation of a calendar entry. In some examples, a domain may be associated with an attribute node for general attributes (such as "share", "delete", "search", etc.). In some examples, a second input including user voice (such as user voice 908) is received. User speech 908 may include, for example, the phrase "Move this to tomorrow at 2pm."

[0268] In some examples, the user intent is determined based on the determined domain and the received user speech. In some examples, determining the user intent includes disambiguating the user speech based on contextual information. For example, ambiguous terms, such as the ambiguity of "this" in the user speech 908 "Move this to tomorrow at 2 pm", can be disambiguated based on information associated with the calendar application 904. In some examples, references to "this", "that", "those", "these", etc. can be disambiguated based on the currently activated enabling representation. For example, the ambiguous term "this" in the speech "Move this to tomorrow at 2 pm" can correspond to the activated enabling representation 904. For example, the activated enabling representation 904 can correspond to the calendar entry for "Meeting with John". It is then determined that the ambiguous term "this" refers to the calendar entry for "Meeting with John".

[0269] In some examples, the determined domain of "event" may be associated with attribute nodes of "event name," "date / time," "participants," "create event," "change event," and the like. For example, a node for "change event" may be activated based on the text "move" generated from user speech 908. For example, a node for "event name" may be activated based on the disambiguated text "this" (meaning "a meeting with John"). A node for "date / time" may be activated based on the text "tomorrow at 2 p.m.". Based on activating the executable intent node using the determined domain, device 900 may determine that the user intent corresponds to a command to change the timing of calendar entry 904 to 2 p.m. the next day.

[0270] In some examples, based on determining that the user intent includes a command associated with the affordance 904, a task to advance the command is performed. For example, in response to determining that the user intent corresponds to a command to change the timing of calendar entry 904, device 900 may change the timing information associated with calendar entry 904, such as changing the date of the entry to the next day and changing the time to 2 p.m. Device 900 may further display one or more interfaces, such as a visual depiction within calendar application 906, including the next day and calendar events 904 scheduled for the next day (not shown). In some examples, other commands associated with affordances within calendar application 906 may include commands for creating a new calendar entry, moving to a different date on the calendar, sending a message or reminder to a participant of a calendar event, setting a reminder for a calendar event, and the like.

[0271] Fig.10 An exemplary process for multimodal input is shown. For example, user 1002 may interact with electronic device 1000 to perform one or more actions within email application 1006. In some examples, a first input including activation of an affordance is received, such as activation of affordance 1004. Affordance 1004 may correspond to an email within a plurality of emails. In some examples, additional affordances within email application 1006 may be activated, such as affordances for creating a new email, changing a mailbox, deleting an email, archiving or changing a folder of an email, opening an email attachment, editing a plurality of emails, and the like. In some examples, a domain associated with affordance 1004 is determined. For example, a domain associated with one or more of "instant messaging" or "email" may be determined based on activation of a calendar entry. In some examples, a domain of one of "shops", "personal", etc. is determined based on a particular type of email account associated with email application 1004. In some examples, a second input including user voice (such as user voice 1008) is received. For example, user speech 1008 may include the phrase "Create a meeting with everyone on this email."

[0272] In some examples, user intent is determined based on the determined domain and the received user speech 1008. For example, to determine user intent, the user speech can be disambiguated based on contextual information. An ambiguous phrase in user speech 1008, such as "everyone on that email," can be disambiguated based on information associated with email application 1006. For example, an ambiguous phrase can be determined to correspond to an activated affordance 1004 that is associated with an email sent to one or more recipients, such as "CJ Olson." The ambiguous phrase "everyone on that email" is then determined to refer to all recipients on that email that are associated with the activated affordance 1004.

[0273] In some examples, the determined domain of "instant message" or "email" may be associated with attribute nodes for "participants," "reply," "reply all," "forward," "add recipient," "new event," "delete email," and the like. For example, a node for "new event" may be activated based on the text "create meeting" generated from user voice 1008. For example, a node for "recipients" may be activated based on the disambiguated text "everyone" (meaning the recipients of the email associated with activated affordance 1004). Based on activating the executable intent node using the determined domain, device 1000 may determine that the user intent corresponds to a command to create a new event, where the participants correspond to the email recipients associated with activated affordance 1004.

[0274] In some examples, in response to determining that the user intent includes a command associated with affordance 1004, a task to advance the command is performed. For example, in response to determining that the user intent corresponds to a command for creating a new meeting with participants corresponding to the recipient of email 1004, device 1000 may initiate one or more interfaces to create a new meeting. For example, a calendar application may be called and a new event may be created (not shown). The new event may be automatically populated with the names of the participants, including the recipient of email 1004. In some examples, if additional information is required in order to perform the task to advance the command, the user may be prompted to provide additional input. For example, user speech 1008 including "Create a meeting with everyone on this email" does not include information about the date or time of the new meeting. In response to determining that additional information is required to create a new meeting, such as the date and time of the meeting, device 1000 may output a prompt to the user, such as "What time do you want to schedule the meeting?" Upon receiving additional input from the user that satisfies the request for additional information, the task may be completed by, for example, automatically filling in a new meeting entry with the additional information provided by the user. Device 1000 may also display one or more interfaces, such as a visual depiction of a scheduled meeting including participants. In some examples, other commands associated with the enable representation within the mail application 1006 may include commands for creating a new mail, deleting or moving mail, printing mail, forwarding or replying to mail, showing unread messages, moving to a new mail folder, creating a new mail folder, and the like.

[0275] Fig.11 An exemplary process for multimodal input is shown. For example, user 1102 may interact with electronic device 1100 to perform one or more actions within map application 1106. In some examples, a first input including activation of an affordance is received, such as activation of affordance 1104. Affordance 1104 may be associated with a location of a displayed map, such as a store location, home, street, park, etc. In some examples, affordance 1104 may be associated with a general area of ​​a map. For example, user 1102 may perform one or more swipe gestures that result in the creation of a shape (e.g., a circle, rectangle, custom shape, etc.) on the displayed map. For example, the content of the displayed map included in the user-created shape may correspond to the activated affordance 1104.

[0276] In some examples, a domain associated with affordance 1104 is determined. For example, a domain associated with a geographic domain may be determined. In some examples, content within affordance 1104 may be used to determine the domain. For example, if affordance 1104 includes the city of Cupertino, California, the domains of "Cupertino" and / or "California" may be determined. In some examples, a second input including user speech, such as user speech 1108, is received. For example, user speech 1108 may include the phrase "Are there any good Italian restaurants around here?".

[0277] In some examples, the user intent is determined based on the determined domain and the received user speech 1108. In some examples, in order to determine the user intent, the user speech is disambiguated based on contextual information. For example, ambiguous terms in user speech such as "around here" can be disambiguated based on the displayed content. In some examples, the affordance type can be determined, and if the affordance type corresponds to a predetermined type, the attribute associated with the displayed content is determined. For example, the attribute is then used to determine the user intent. In some examples, the affordance 1104 can be associated with a location type. Then, the attributes associated with the displayed content within the map application 1106 are used to disambiguate the user speech. For example, the affordance 1104 may include a specific area contained within a shape drawn by the user 1102 within the map application 1106. For example, the user can draw a circle, square, rectangle, or any other free shape around a specific area within the map application 1106. The attributes associated with the location within the specific area can be used to disambiguate the user speech. For example, the text "around here" generated from user speech 1108 may be parsed to mean any location within the circle drawn by the user. As another example, affordance 1104 may correspond to a specific location, such as a store location. In this case, the text "around here" generated from user speech 1108 may be parsed to mean any location within a predetermined distance from the store location (e.g., within 5 miles of the location).

[0278] In some examples, the determined geographic domain may be associated with attribute nodes for "find location," "route planning," "traffic information," "store information," "restaurant information," and the like. For example, a node for "find location" may be activated based on the text "any" or "any good" generated from user speech 1108. A node for "restaurant information" may be activated based on the text "Italian restaurant." A sub-node for "find location" may be activated, such as for "location," for the disambiguated text "around here." Based on the activation of the executable intent node using the determined domain, device 1100 may determine that the user intent corresponds to a command to find an Italian restaurant within 5 miles of the location corresponding to the activated affordance 1104.

[0279] In some examples, based on determining that the user intent includes a command associated with affordance 1104, a task is performed to advance the command. For example, in response to determining that the user intent corresponds to finding an Italian restaurant, device 1100 may display an interface (not shown) that includes all restaurants that serve Italian food within 5 miles of the activation location. In some examples, based on determining that the user intent does not include a command associated with an affordance, at least one command associated with the affordance is provided. For example, while interacting with map application 1106, a user may activate affordance 1104 and provide a voice input that includes "send a new email to these people." Device 1000 may determine that the voice input corresponds to a command to send a new email, but may further determine that the commands associated with affordance 1104 within map application 1106 do not include a command for sending a new email. In response to the determination, at least one command associated with affordance 1104 is provided. For example, device 1100 may provide exemplary commands associated with affordance 1104, such as "You can say 'Find movie showtimes around here'" or "Try saying 'How long does it take to get to San Francisco from here'." In some examples, other commands associated with the affordances within the map application 1106 may include commands for finding alternative routes, locating businesses that are open, finding concerts or other events, searching for public transportation, and the like.

[0280] Fig.12 An exemplary process for multimodal input is shown. For example, user 1202 may interact with electronic device 1200 to perform one or more actions within media application 1206. In some examples, a first input including activation of an affordance is received, such as activation of affordance 1204. Affordances within media application 1206 may be associated with one or more media items, such as a photo, a video, or a collection of one or more photos and videos. Affordance 1204 may correspond to a photo in a plurality of photos. Other affordances within the media application may be activated, such as affordances for moving to different groups of media items (e.g., moving to media from different days, months, or years) or selecting multiple media items. In some examples, a domain associated with affordance 1204 is determined. For example, a domain associated with one or more of "media" or "photos" may be determined based on activation of a photo such as affordance 1204. In some examples, a second input including user voice such as user voice 1208 is received. For example, user voice 1208 may include the phrase "send this to John."

[0281] In some examples, user intent is determined based on the determined domain and the received user speech. In some examples, ambiguous terms, such as "this" in user speech 1208 "send this to John," can be disambiguated based on information associated with photo application 1206. In some examples, references to "this," "that," "those," "these," etc. can be disambiguated based on currently activated affordances 1204 corresponding to specific photos. The ambiguous term "this" is then determined to refer to the specific photo activated by the user input.

[0282] In some examples, the determined domain of "media" or "photos" may be associated with property nodes for media or photo related properties such as "enhance," "contrast," "brightness," "cropping," or other general properties such as "share," "delete," and the like. For example, a node for "share" may be activated based on the text "send this" generated from user speech 1208. For example, a node for "photos" may be activated based on disambiguated text that refers to a specific photo corresponding to activated affordance 1204. A sub-node for "share" corresponding to "recipient" may be activated based on the text "John." Based on activating the executable intent node using the determined domain, device 1200 may determine that the user intent corresponds to a command to send a specific photo to a contact named John in the user's address book.

[0283] In some examples, based on determining that the user intent includes a command associated with affordance 1204, a task to advance the command is performed. For example, in response to determining that the user intent corresponds to a command to send a specific photo to a contact named John in the user's address book, device 900 may display an interface such as an instant messaging interface or an email interface. The displayed interface may also be automatically populated with a recipient as the user contact "John" and with an attachment including the specific photo activated via affordance 1204. In some examples, other commands associated with affordances within photo application 1206 may include commands for editing media, rearranging media, deleting media, creating media albums, and the like.

[0284] Fig.13An exemplary process for multimodal input is shown. For example, user 1302 may interact with electronic device 1300 to perform one or more actions on a home screen of device 1300. In some examples, the home screen of device 1300 includes one or more displayed notifications 1306. In some examples, a first input including activation of an affordance is received, such as activation of affordance 1304 associated with notification 1306. Notification 1306 may correspond to an alert or other indication of an event received at the device, such notification being about a received message, a news alert, a voicemail, a missed call, an application update, a sports score, and the like. In some examples, in response to receiving the first input including activation of an affordance, a second affordance is displayed near the affordance. For example, in response to user 1302 activating affordance 1304 corresponding to notification 1306, additional affordances 1310 and 1312 may be displayed. Activation of affordance 1310 may cause one or more tasks to be performed, such as marking a notification as completed or reminding the user of the notification later. Affordance 1312 may also be displayed, and activation of affordance 1312 may cause audio input to be sampled. For example, in response to user 1302 activating affordance 1312, audio input may be sampled to receive additional user voice input. The additional voice input may be processed as described herein to execute a command associated with activated affordance 1304.

[0285] FIG. 14A to FIG. 14B An exemplary process for multimodal input is shown. For example, referring to Fig.14A , user 1402 can interact with electronic device 1400 to perform dictation. In some examples, input 1404 including activation of text input area 1406 is received. Text input area 1406 can be included in an application in which a user can enter text, such as a text input area of ​​an instant messaging application, an email application, a web browser, a social media application, a notepad application, etc. In some examples, input is received from an auxiliary device such as a remote controller or a smart phone. For example, the text input area can be associated with a media application displayed on the television, such as a search bar for searching for media items. The auxiliary device can communicate with the television via a set-top box so that the user can activate the text input area on the television from the auxiliary device.

[0286] In some examples, it is determined whether the activation of the text input area 1406 is associated with a predetermined input type. For example, the user input may be associated with different pressures or durations. In some examples, it is determined whether the input is associated with a contact of a predetermined duration. The predetermined input type may correspond to any input whose duration is greater than a threshold duration (such as three seconds). In some examples, it is determined whether the input includes a first contact of a first duration and a second contact of a different duration. For example, the predetermined input type may correspond to a long press followed by a short press, or to a short press followed by a long press. In some examples, it is determined whether the input including the activation of the text input area is associated with a pressure greater than a predetermined threshold pressure. For example, if the user only taps the text input area, the text input area is not activated. In some examples, when the activation of the text input area is not associated with a predetermined input type, the activation may be associated with other input types. For example, an input whose duration is shorter than a threshold duration and / or whose pressure is less than a predetermined threshold pressure may cause one or more functions to be executed. Such functions may include, for example, activation of a menu 1410, which includes functions for cutting, copying, pasting, etc.

[0287] In some examples, according to determining that the activation of the text input area is associated with a predetermined input type, the audio input is sampled. For example, the audio input can be sampled before the activation of the text input area 1406, or the audio input can be sampled when the text input area 1406 is activated. In some examples, the audio data of a predetermined duration is stored continuously, such as the audio of the most recent duration. According to determining that the activation of the text input area 1406 is associated with a predetermined input type, the received audio data of a predetermined duration is obtained, wherein the audio data is sampled based on the received audio of the predetermined duration. Optionally, the menu 1410 may also include an affordance for activating speech recognition. For example, when determining that the input corresponds to a predetermined input type, the affordance for activating speech recognition is displayed in the menu 1410. In some examples, when the user input activates the affordance for speech recognition, the audio input can be sampled. For example, when the user does not activate the affordance for activating speech recognition, audio sampling does not occur.

[0288] In some examples, audio input may be sampled from an auxiliary device such as a remote controller, a smart phone, a watch, or a Bluetooth headset. For example, when a text input area is associated with an application displayed on a television, a user can both activate the text input area on the television from an auxiliary device and provide audio input through the auxiliary device. In some examples, an output is provided when the text input area is activated, such as a visual output, an auditory output, or a tactile output. For example, a device held by a user, such as electronic device 1400 or an auxiliary device, may vibrate in response to sampling the audio input. The output may indicate to the user that the audio input is being sampled for speech recognition, for example, so that the user's speech is dictated into the text input area.

[0289] In some examples, audio input is sampled based on different conditions. For example, when sampling audio data, it is determined whether to maintain input including activation of text input area 1406. The user can activate text input area 1406, for example, by providing input 1404 and continuing to contact the device screen. For example, according to determining that the input including activation of text input area 1406 is maintained, continue to sample audio data. In some examples, according to determining that the input including activation of text input area 1406 is not maintained, the sampling of audio data is suspended. For example, after contacting the screen for ten seconds and providing voice input, the user can release input 1404 and then suspend the sampling of audio data. In some examples, when sampling audio data, it is determined whether the audio of a predetermined duration includes user voice, such as the audio of the most recent duration. According to determining that the audio of a predetermined duration includes user voice, continue to sample audio data. For example, as long as the user continues to provide voice input to device 1400, audio data will continue to be sampled. According to determining that the audio of a predetermined duration does not include user voice, suspend sampling of audio data. For example, once the user stops providing audio input to device 1400, the audio stops being sampled.

[0290] In some examples, the text representation is determined based on sampled audio data. For example, the text may be determined when audio data containing user speech is sampled. In some examples, the text representation is determined based on a predetermined duration of audio data, such as the most recent duration of the received audio data. For example, audio data is continuously received, and audio data of the predetermined duration is stored. Based on receiving user input 1404 including activation of text input area 1406, the stored duration of audio data is sampled, wherein at least a portion of the text representation is determined based on the sampled duration. For example, referring to Fig. 14B, if the user begins to provide voice input 1408 including "How is Italian food", although the text input area 1406 has not yet been activated, the complete voice input "How is Italian food" is still captured based on the audio of the predetermined duration when the text input area 1406 is activated shortly after the user begins speaking. At least a portion of the generated text is then based on the stored duration.

[0291] In some examples, an output including a representation is provided within the text input area. For example, a transcription 1412 may be displayed within the text input area 1406. In some examples, the text representation may be displayed as the text representation is determined based on the sampled audio data. For example, a transcription 1412 of the speech input 1408 is provided in real time as the user speaks the input 1408.

[0292] FIG. 15A to FIG. 15B An exemplary process for multimodal input is shown. For example, user 1502 may interact with electronic device 1500 to determine whether a displayed affordance is associated with one or more voice commands. Device 1500 may display one or more affordances, such as affordance 1504. In some examples, user input 1502 corresponding to one or more affordances, such as affordance 1504, is received. For example, the user input may correspond to a contact on a display of the device. In some examples, receiving input includes detecting an object near the display, such as a user's finger. For example, one or more proximity sensors may detect that a finger of user 1502 is positioned near affordance 1504, such as within a predetermined threshold distance of a display screen at a position corresponding to affordance 1504. In some examples, receiving input includes detecting a cursor positioned above affordance. For example, when the device corresponds to a personal computer such as a laptop, the user may use a mouse or a trackpad to interact with affordance to control the cursor. Receiving input may include, for example, detecting that a cursor controlled by a user is positioned above the displayed affordance. In some examples, user preferences may determine when such input is detected, such as detecting only direct input (e.g., a tap or touch) on an affordance, or allowing detection of more passive input associated with the affordance (e.g., a "mouse-over" gesture). In some examples, input is received from an auxiliary device such as a remote controller or a smart phone. For example, an affordance may be displayed on a television that is communicatively coupled to the auxiliary device via a set-top box, wherein a user provides input corresponding to the displayed affordance through the auxiliary device.

[0293] In some examples, it is determined whether the affordance representation corresponding to the input is associated with one or more voice commands. For example, one or more voice commands may be compatible with an application associated with affordance representation 1504, which may correspond to an email application. For example, the command "create a new email" may be associated with an email application. In some examples, certain commands such as default commands may be compatible with all or nearly all affordance representations. For example, a share command, a help command, a delete command, or a search command may be compatible with all or nearly all affordance representations. For example, a share command may enable an application or an element associated with an application to be shared with another user (e.g., via a text message or email). A help command may, for example, enable additional information about the affordance representation to be provided to the user. For example, a delete command may delete an application or an element associated with an affordance representation (e.g., a photo in a photo application) from a device. In some examples, a search command may initiate a search function associated with an application or element (e.g., a search within an email inbox).

[0294] In some examples, determining whether affordance 1504 is associated with one or more voice commands includes determining whether affordance 1504 is associated with one or more voice commands that are not included in a plurality of default voice commands. For example, affordances may be associated only with default voice commands and not with additional voice commands. Additional voice commands may be associated with affordances by, for example, providing an update to an application or an element associated with the application by a vendor of the application.

[0295] In some examples, based on determining that the affordance 1504 is associated with one or more voice commands, an output 1506 is provided to indicate that the affordance 1504 is associated with one or more voice commands. For example, the output 1506 may be displayed near the affordance 1504. The output 1506 may indicate to the user 1502 that the affordance 1504 may be interacted with via, for example, a voice command. In some examples, the output is displayed for a predetermined duration (e.g., three seconds). The output may include one or more indications about voice command compatibility, such as multiple points within a circle. In some examples, the output may include visual effects around the affordance, such as a halo or visual vibration. In some examples, in addition to or in place of a visual output, the output may include an auditory output and / or a tactile output. In some examples, in addition to or in place of a device that displays affordances, an output is provided at an auxiliary device. For example, a user may provide input via an auxiliary device such as a remote controller or a smart phone. An output such as a tactile output may be provided at an auxiliary device to indicate that the affordance corresponding to the user input is associated with one or more voice commands. Output may also be provided at an additional device, such as a smart watch or Bluetooth headset communicatively coupled to the device displaying the affordances and / or the auxiliary device.

[0296] In some examples, providing output 1506 includes determining whether to maintain input. For example, output 1506 can continue to be provided based on determining that the first input is maintained. For example, user 1502 can provide input by temporarily contacting or hovering a finger over affordance 1504. Output 1506 can continue to be displayed while the user provides input. Based on determining that the first input is not maintained (e.g., the user releases contact or moves the finger away from affordance 1504), displaying output 1506 is discontinued.

[0297] Fig.16A process 1600 for providing multimodal input according to various examples is shown. For example, process 1600 is performed using one or more electronic devices that implement a digital assistant. In some examples, process 1600 is performed using a client-server system (e.g., system 100), and the boxes of process 1600 are divided in any way between a server (e.g., DA server 106) and a client device. In other examples, the boxes of process 1600 are divided between a server and multiple client devices (e.g., a mobile phone and a smart watch). Therefore, although part of process 1600 is described herein as being performed by a specific device of a client-server system, it should be understood that process 1600 is not limited thereto. In other examples, process 1600 is performed using only a client device (e.g., user device 104) or only multiple client devices. In process 1600, some boxes are optionally combined, the order of some boxes is optionally changed, and some boxes are optionally omitted. In some examples, additional steps may be performed in conjunction with process 1600.

[0298] At box 1602, the electronic device receives a first input including activation of an affordance. In some examples, receiving the first input including activation of the affordance includes: determining whether the first input is associated with a pressure greater than a predetermined threshold, and determining that the first input is received based on determining that the first input is associated with a pressure greater than the predetermined threshold. In some examples, receiving the first input including activation of the affordance includes: receiving a first contact associated with a first duration at a location on a display of the electronic device, and receiving a second contact associated with a second duration at a location on the display, wherein the second duration is longer than the first duration. In some examples, receiving the first input including activation of the affordance includes: receiving a first contact at a first location on the display of the electronic device, detecting a swipe gesture on the display, detecting a release of the contact at a second location on the display, and determining the affordance based on an area associated with the first location, the swipe gesture, and the second location. These features improve digital assistants by maintaining existing functionality on the device based on a specific input type (e.g., a short press for an existing function), and extending functionality to multimodal input of voice commands based on various additional input types (e.g., pressure-based input or gesture-based input). In other words, the system maximizes different input types in order to achieve multimodal functionality without reducing usability relative to existing features.

[0299] In some examples, receiving a first input comprising activation of an affordance comprises detecting a user gaze corresponding to the affordance, wherein the gaze is associated with a predefined duration. In some examples, based on receiving the first input comprising activation of the affordance, a second affordance is displayed near the affordance, a third input comprising activation of the second affordance is received, and based on receiving the third input, an audio input is sampled to receive the second input. In some examples, the first input is received from an auxiliary device. By activating affordances based on additional inputs such as eye gaze or input from an auxiliary device, a multimodal input system is utilized on a variety of different device types using different techniques. In turn, the multimodal system can be extended to interactions involving televisions, smart watches, personal computers, virtual reality systems, home stereo systems, and the like.

[0300] At box 1604, a domain associated with the enable representation is determined. In some examples, determining the domain associated with the enable representation includes determining at least one attribute associated with the activated enable representation, identifying at least one executable intent node corresponding to the at least one attribute, and determining the user intent based on the at least one identified executable intent node. Determining the domain associated with the enable representation facilitates improving the accuracy of user intent determination. For example, by determining a specific domain associated with the enable representation, such as a geographic domain (e.g., corresponding to a map application) or a media domain (e.g., corresponding to an entertainment application), the system can narrow down the possible domains from which to determine the user intent. In other words, by performing domain determination, the system learns that the voice input will likely be associated with the domain corresponding to the activated enable representation. In turn, the system maximizes resource utilization by avoiding intent determination based on unrelated domains.

[0301] At block 1606, a second input including a user voice is received. In some examples, the second input is received from an auxiliary device. In some examples, audio data is received, wherein the received audio data of a predetermined duration is stored, and based on receiving the first input, the received audio data of a predetermined duration is obtained, wherein at least a portion of the second input including the user voice is received from the received audio data of the predetermined duration. In some examples, the audio of the predetermined duration includes the audio of the most recent duration. In some examples, based on receiving the first input, the audio input is sampled to receive the second input, and it is determined whether the first input is maintained, wherein based on determining that the first input is maintained, the audio input continues to be sampled, and based on determining that the first input is not maintained, the audio input is suspended from being sampled. In some examples, in response to receiving the first input, the audio input is sampled to receive the second input, wherein based on the sampling, it is determined whether the audio of the predetermined duration includes the user voice, and based on determining that the audio of the predetermined duration includes the user voice, the audio input continues to be sampled, and based on determining that the audio of the predetermined duration does not include the user voice, the audio input is suspended from being sampled. In some examples, the audio of the predetermined duration includes the audio of the most recent duration. By sampling the audio based on a variety of different conditions, the system provides the user with a variety of ways to provide voice commands after the enable indication is activated. For example, the user can press and hold the enable indication, and provide voice while the user continues to hold the enable indication. Alternatively, if the user does not want or cannot continue to press the enable indication, the user can provide voice, and once the user stops speaking, the audio sampling will automatically terminate. In addition, if it is more convenient, the user can provide voice via an auxiliary device. Each of these methods improves the user experience by maximizing the options available to the user.

[0302] At box 1608, the user intent is determined based on the domain and the user voice. In some examples, the affordance type is determined, wherein at least one attribute associated with the displayed content is determined based on determining that the affordance type corresponds to a predetermined type, and the user intent is further determined based on the at least one attribute. In some examples, the affordance type corresponds to at least one of a mail type, a photo type, a map type, a calendar type, or a notification type. By refining the user intent determination based on the displayed content, the system further optimizes the multimodal input system. For example, when the user intent determination is first enhanced based on the domain determination, the ambiguity of the user voice that retains ambiguity can be eliminated based on the displayed content. For example, if the device has determined the media domain associated with the displayed picture, and the user voice input includes "put this song second", the device utilizes the displayed content to satisfy the user request. That is, in the case of displaying a song playlist, the device can, for example, determine that "second" refers to the second position within the displayed playlist based on the attributes associated with the playlist. Therefore, the intention determination is further improved.

[0303] At box 1610, it is determined whether the user intent includes commands associated with the affordance. In some examples, based on determining that the user intent does not include commands associated with the affordance, at box 1612, at least one command associated with the affordance is provided. In some examples, the at least one command associated with the affordance includes at least one of a share command, a help command, a delete command, or a search command. By providing commands in this manner, the multimodal input system provides additional information to the user in the event that the user command is not associated with an activated affordance. For example, a user may routinely utilize a command to "send a message" using an instant messaging or email application. If the user attempts to utilize a command with a newly downloaded application that does not yet perform such a function, the device will notify the user of the currently available commands for the new application, such as default commands available for all applications or application-specific commands. These features further improve the user experience by providing valuable training to the user.

[0304] At box 1614, based on determining that the user intent includes a command associated with the enable representation, a task is performed to advance the command. By performing tasks based on multimodal input, the system utilizes the strength of physical "touch" input (or other non-voice input) and the strength of voice input to provide an enhanced user experience. Specifically, non-voice input such as touch or tap provides the user with the ability to accurately and accurately identify and activate different objects on the displayed screen, while avoiding requiring the user to make many different touch inputs and screen gestures to perform tasks. The system also takes advantage of the convenience that the user can provide additional instructions via voice input to complete the request, especially in cases where such instructions would be difficult to execute via touch. The determination of user intent is further enhanced based on domain determination, resulting in a system that improves conventional digital assistants and reduces associated difficulties.

[0305] References Fig.16 The described operations are optionally performed by Figures 1 to 4 , FIG. 6A to FIG. 6B and 7A to 7C For example, the operations of process 1600 may be implemented by one or more of the following: operating system 718, application module 724, I / O processing module 728, STT processing module 730, natural language processing module 732, vocabulary index 744, task flow processing module 736, service processing module 738, media service 120-1, or processor 220, 410, 704. A person skilled in the art will clearly know how to implement the process 1600 based on the above. Figures 1 to 4 , FIG. 6A to FIG. 6B and 7A to 7C The components depicted in the figure are used to implement other processes.

[0306] Fig.17 A process 1700 for providing multimodal input according to various examples is shown. For example, process 1700 is performed using one or more electronic devices that implement a digital assistant. In some examples, process 1700 is performed using a client-server system (e.g., system 100), and the boxes of process 1700 are divided in any way between a server (e.g., DA server 106) and a client device. In other examples, the boxes of process 1700 are divided between a server and multiple client devices (e.g., a mobile phone and a smart watch). Therefore, although part of process 1700 is described herein as being performed by a specific device of a client-server system, it should be understood that process 1700 is not limited thereto. In other examples, process 1700 is performed using only a client device (e.g., user device 104) or only multiple client devices. In process 1700, some boxes are optionally combined, the order of some boxes is optionally changed, and some boxes are optionally omitted. In some examples, additional steps may be performed in conjunction with process 1700.

[0307] At box 1702, the electronic device receives input including activation of a text input area. In some examples, the input is received from an auxiliary device. In some examples, the text input area corresponds to at least one of an instant message text field, an email text field, a calendar event text field, a notepad field, a social media text field, or a search text field. By activating the text input area based on input at the device or from the auxiliary device, the system provides the user with different options for activating text fields that are ubiquitous in many different applications and settings. For example, a user can activate a text input area to compose an email on a device, or alternatively activate a text input area on a television to compose an email from an auxiliary device such as a smart phone. These different inputs improve the user experience by allowing the text input area to be activated across multiple devices.

[0308] At box 1704, determine whether the activation of the text input area is associated with a predetermined input type. In some examples, determining whether the activation of the text input area is associated with a predetermined input type includes determining whether the input including the activation of the text input area is associated with a contact of a predetermined duration. In some examples, determining whether the activation of the text input area is associated with a predetermined input type includes determining whether the input including the activation of the text input area is associated with a pressure greater than a predetermined threshold pressure. In some examples, determining whether the activation of the text input area is associated with a predetermined input type includes receiving a first contact associated with a first duration within the text input area, and receiving a second contact associated with a second duration within the text input area, wherein the second duration is longer than the first duration. By determining whether the activation is associated with a predetermined input type, the system maintains existing functionality on the device, such as a quick tap for existing functionality, and expands functionality to multimodal input of voice commands based on additional input types, such as pressure-based or timing-based input. Then, the system maximizes different input types to achieve multimodal functionality without reducing the usability of existing features.

[0309] At box 1706, based on determining that activation of the text input area is associated with a predetermined input type, audio data is sampled. In some examples, based on determining that activation of the text input area is associated with a predetermined input type, audio data is received from an auxiliary device, and sampling the audio data includes sampling the audio data received from the auxiliary device. In some examples, based on determining that activation of the text input area is associated with a predetermined input type, an output is provided to indicate the initiation of speech recognition, wherein the output includes at least one of an audible output, a visual output, or a tactile output. In some examples, when sampling the audio data, it is determined whether the input including activation of the text input area is maintained, wherein the input including activation of the text input area is maintained, the audio data is continued to be sampled, and the audio data is suspended according to the determination that the input including activation of the text input area is not maintained. In some examples, it is determined whether the audio of a predetermined duration includes a user voice, wherein the audio of a predetermined duration includes a user voice, the audio data is continued to be sampled, and the audio of a predetermined duration does not include a user voice, and the audio data is suspended. In some examples, the audio of the predetermined duration includes the audio of the most recent duration. By sampling the audio based on various different conditions, the system provides the user with a variety of ways to provide input text after activating the text input area. For example, the user can press and hold the text input area, and provide voice when the user continuously holds the area. Alternatively, if the user does not want or cannot press the text input area continuously, the user can provide voice, and once the user stops speaking, the audio sampling will automatically terminate. In addition, if it is more convenient or necessary, the user can provide voice via an auxiliary device. Each of these methods improves the user experience by maximizing the options available to the user.

[0310] At box 1708, determine text representation based on sampled audio data. In some examples, receive audio data, wherein store the received audio data of predetermined duration, and according to receiving input including activation to text input area, sample the audio data of predetermined duration, wherein determine at least a part of text representation based on the audio data of predetermined duration sampled. In some examples, the received audio data of predetermined duration includes the audio of the most recent duration. By sampling the audio of the stored duration, the system ensures that any voice received before the user activates the text input area will be captured and included in the generated text representation. For example, the user can temporarily start dictating to the device before activating the text input area. Therefore, the system avoids the situation that such audio will not be included in the dictated text by considering the audio of the predetermined duration received before activating the text input area. These features improve user experience by eliminating the strict user input sequence (e.g., touch and then speak) that would be required without such features.

[0311] At box 1710, an output including a text representation is provided within the text input area. In some examples, providing an output including a text representation within the text input area includes: when the text representation is determined based on the sampled audio data, displaying text within the text input area, wherein the displayed text corresponds to a determined portion of the text representation. By providing the text representation within the text input area, and when the text representation is determined, the user is able to view the generated results while the user is speaking, thereby allowing the user to modify the spoken text when necessary. Such features improve the user experience by providing enhanced feedback and real-time dictation.

[0312] References Fig.17 The described operations are optionally performed by Figures 1 to 4 , FIG. 6A to FIG. 6B and 7A to 7C For example, the operations of process 1700 may be implemented by one or more of the following: operating system 718, application module 724, I / O processing module 728, STT processing module 730, natural language processing module 732, vocabulary index 744, task flow processing module 736, service processing module 738, media service 120-1, or processor 220, 410, 704. A person of ordinary skill in the art will clearly know how to implement the process 1700 based on the above. Figures 1 to 4 , FIG. 6A to FIG. 6B and 7A to 7C The components depicted in the figure are used to implement other processes.

[0313] Fig.18A process 1800 for providing multimodal input according to various examples is shown. For example, process 1800 is performed using one or more electronic devices that implement a digital assistant. In some examples, process 1800 is performed using a client-server system (e.g., system 100), and the boxes of process 1800 are divided in any way between a server (e.g., DA server 106) and a client device. In other examples, the boxes of process 1800 are divided between a server and multiple client devices (e.g., a mobile phone and a smart watch). Therefore, although part of process 1800 is described herein as being performed by a specific device of a client-server system, it should be understood that process 1800 is not limited thereto. In other examples, process 1800 is performed using only a client device (e.g., user device 104) or only multiple client devices. In process 1800, some boxes are optionally combined, the order of some boxes is optionally changed, and some boxes are optionally omitted. In some examples, additional steps may be performed in conjunction with process 1800.

[0314] At box 1802, one or more enable indications are displayed.

[0315] At box 1804, input is received corresponding to an enable representation in one or more enable representations. In some examples, the input includes user contact on a display of the electronic device. In some examples, receiving the input includes detecting an object near the enable representation. In some examples, receiving the input includes detecting a cursor positioned above the enable representation. In some examples, the input is received from an auxiliary device. By detecting a variety of different input types, the system takes advantage of different levels of user interaction with the device. For example, input can be detected based on direct user input such as a touch or tap on the screen, and input can be further detected through more passive input such as "mouseover" or "hovering" above the enable representation. Detecting different levels of user interaction facilitates different levels of intrusiveness to discover useful features of the device.

[0316] At box 1806, determine whether the enable representation is associated with one or more voice commands. In some examples, determining whether the enable representation is associated with one or more voice commands includes determining a plurality of default voice commands, and determining whether the enable representation is associated with one or more voice commands that are not included in the plurality of default voice commands. By distinguishing between default commands and additional commands, the device enhances discoverability by providing notifications only when the enable representation is associated with a unique command. For example, all enable representations may be associated with a set of default voice commands such that discoverability does not apply to such commands (e.g., doing so would result in output that displays all enable representations).

[0317] At box 1808, based on determining that the affordance is associated with one or more voice commands, an output is provided to indicate that the affordance is associated with one or more voice commands. In some examples, providing an output to indicate that the affordance is associated with one or more voice commands includes displaying an output for a predetermined duration. In some examples, providing an output indicating that the affordance is associated with one or more voice commands includes determining whether the input is held, wherein the output continues to be provided based on determining that the first input is held, and the output is terminated based on determining that the first input is not held. In some examples, the output is provided at an auxiliary device. In some examples, the output includes at least one of an audible output, a visual output, or a tactile output. By providing output based on different conditions or at different devices, the system enhances functional discoverability by changing the level of intrusion when providing output. For example, the output may only appear for a predetermined duration, or only when a user input is detected. By further providing a tactile output or an audible output, the device can provide a more subtle way of notifying the user that the affordance is associated with one or more voice commands. Each of these features improves the user experience by providing valuable training to the user about features that the user may not have known before. Therefore, device functionality and user productivity are maximized.

[0318] References Fig.18 The described operations are optionally performed by Figures 1 to 4 , FIG. 6A to FIG. 6B and 7A to 7C For example, the operations of process 1800 may be implemented by one or more of the following: operating system 718, application module 724, I / O processing module 728, STT processing module 730, natural language processing module 732, vocabulary index 744, task flow processing module 736, service processing module 738, media service 120-1, or processor 220, 410, 704. A person of ordinary skill in the art will clearly know how to implement the process 1800 based on the above. Figures 1 to 4 , FIG. 6A to FIG. 6B and 7A to 7C The components depicted in the figure are used to implement other processes.

[0319] According to some specific implementations, a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) is provided, which stores one or more programs for execution by one or more processors of an electronic device, the one or more programs including instructions for performing any of the methods or processes described herein.

[0320] According to some implementations, an electronic device (eg, a portable electronic device) is provided that includes means for performing any of the methods and processes described herein.

[0321] According to some implementations, an electronic device (eg, a portable electronic device) is provided that includes a processing unit configured to perform any of the methods and processes described herein.

[0322] According to some specific implementations, an electronic device (e.g., a portable electronic device) is provided, which includes one or more processors and a memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for performing any of the methods and processes described herein.

[0323] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

[0324] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of the disclosure and examples defined by the claims.

[0325] As described above, one aspect of the present technology is to collect and use data available from various sources to improve multimodal input of voice commands. The present disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or health level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0326] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to better understand user utterances, for example, for user intent determination. Therefore, the use of such personal information data can allow, for example, user intent to be determined based on user preferences. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health status, or can be used as positive feedback to individuals using technology to pursue health goals.

[0327] This disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should be performed after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to defend and secure access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0328] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, with respect to a user registration process for voice recognition, the technology of the present invention may be configured to allow a user to select an "opt-in" or "opt-out" registration process, which may utilize personal information from the user such as voice features. In another example, a user may select an "opt-in" or "opt-out" process to automatically listen for verbal triggers. In yet another example, a user may select an "opt-in" or "opt-out" process to automatically listen for verbal triggers. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then the user may be reminded again just before the personal information data is accessed by the application.

[0329] Furthermore, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. Additionally, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. Where appropriate, de-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or characteristics of stored data (e.g., collecting location data at a city level rather than an address level), controlling how data is stored (e.g., aggregating data across users), and / or other methods.

[0330] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, a multimodal input method for voice commands may be performed based on non-personal information data or an absolute minimum amount of personal information (such as content requested by a device associated with a user, other non-personal information available to an intelligent automated assistant, or publicly available information).

Claims

1. A computer-implemented method comprising: At an electronic device having a memory and one or more processors: detecting a user gaze including activation of a text input area; determining whether the activation of the text input area is associated with a predetermined input type; sampling audio data in response to determining that the activation of the text input area is associated with a predetermined input type; determining a textual representation based on the sampled audio data; as well as An output including the text representation is provided within the text input area.

2. The method according to claim 1, wherein: Determining whether the activation of the text input area is associated with a predetermined input type includes: A determination is made as to whether the user gaze, including activation of the text input area, is associated with a gaze of a predetermined duration.

3. The method according to claim 1, wherein: Detecting the user gaze comprises eye tracking.

4. The method according to claim 1, wherein: Determining whether the activation of the text input area is associated with a predetermined input type includes: In response to detecting the user gaze including activation of the text input area, displaying an affordance adjacent to the text input area; and Based on receiving user input including activation of the affordance, determining that the activation of the text input area is associated with a predetermined input type.

5. The method according to claim 1, wherein: Detecting the user gaze includes communicating with a secondary device.

6. The method according to claim 1, comprising: Based on determining that the activation of the text input area is associated with a predetermined input type, receiving audio data from an auxiliary device, wherein sampling the audio data includes sampling the audio data received from the auxiliary device.

7. The method according to claim 1, wherein: The text input area corresponds to at least one of an instant message text field, an email text field, a calendar event text field, a note field, a social media text field, or a search text field.

8. The method according to claim 1, comprising: Based on determining that the activation of the text input area is associated with a predetermined input type, providing an output to indicate initiation of speech recognition, wherein the output includes at least one of an audible output, a visual output, or a tactile output.

9. The method according to claim 1, wherein: Providing an output including the text representation within the text input area comprises: When the text representation is determined based on the sampled audio data, text is displayed within the text input area, wherein the displayed text corresponds to the determined portion of the text representation.

10. The method according to claim 1, comprising: Receive audio data; storing the received audio data for a predetermined duration; sampling audio data of the predetermined duration in response to detecting the user gaze including activation of the text input area; as well as At least a portion of the textual representation is determined based on the sampled audio data of a predetermined duration.

11. The method according to claim 10, wherein: The predetermined duration of received audio data comprises a most recent duration of audio.

12. The method according to claim 1, comprising: while sampling the audio data, determining whether detection of the user gaze including activation of the text input area is maintained; as well as continuing to sample the audio data in response to determining that the user gaze, including activation of the text input area, is maintained; as well as Based on determining that the user gaze, including activation of the text input area, is not maintained, sampling the audio data is discontinued.

13. The method according to claim 1, comprising: determining whether the audio of the predetermined duration includes user speech; In response to determining that the audio of the predetermined duration includes user speech, continuing to sample the audio data; as well as Based on determining that the audio of the predetermined duration does not include user voice, sampling the audio data is terminated.

14. The method according to claim 13, wherein: The predetermined duration of audio includes the most recent duration of audio.

15. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, the one or more programs comprising instructions for performing the method according to any one of claims 1-14.

16. An electronic device, comprising: one or more processors; and A memory storing one or more programs, the one or more programs being configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1-14.

17. An electronic device configured to communicate with one or more display generation components and one or more input devices, comprising: Apparatus for performing the method according to any one of claims 1-14.

18. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 1-14.

19. A method comprising: At an electronic device having a memory and one or more processors: receiving input including activation of a text input area; determining whether the activation of the text input area is associated with a predetermined input type; sampling audio data in response to determining that the activation of the text input area is associated with a predetermined input type; determining a textual representation based on the sampled audio data; as well as An output including the text representation is provided within the text input area.

20. The method according to claim 19, wherein: Determining whether the activation of the text input area is associated with a predetermined input type includes: A determination is made as to whether the input, including activation of the text input area, is associated with a contact of a predetermined duration.

21. The method according to claim 19, wherein: Determining whether the activation of the text input area is associated with a predetermined input type includes: A determination is made as to whether the input, including activation of the text input area, is associated with a pressure greater than a predetermined threshold pressure.

22. The method according to claim 19, wherein: Determining whether the activation of the text input area is associated with a predetermined input type includes: receiving a first contact associated with a first duration within the text input area; and A second contact associated with a second duration is received within the text input area, wherein the second duration is longer than the first duration.

23. The method according to claim 19, wherein: The input is received from an auxiliary device.

24. The method according to claim 23, further comprising: Based on determining that the activation of the text input area is associated with a predetermined input type, receiving audio data from an auxiliary device, wherein sampling the audio data includes sampling the audio data received from the auxiliary device.

25. The method of claim 19, wherein: The text input area corresponds to at least one of an instant message text field, an email text field, a calendar event text field, a note field, a social media text field, or a search text field.

26. The method of claim 19, further comprising: Based on determining that the activation of the text input area is associated with a predetermined input type, providing an output to indicate initiation of speech recognition, wherein the output includes at least one of an audible output, a visual output, or a tactile output.

27. The method of claim 19, wherein: Providing an output including the text representation within the text input area comprises: When the text representation is determined based on the sampled audio data, text is displayed within the text input area, wherein the displayed text corresponds to the determined portion of the text representation.

28. The method of claim 19, comprising: Receive audio data; storing the received audio data for a predetermined duration; sampling audio data of the predetermined duration in response to receiving the input comprising activation of the text input area; as well as At least a portion of the textual representation is determined based on the sampled audio data of a predetermined duration.

29. The method according to claim 28, wherein: The predetermined duration of received audio data comprises a most recent duration of audio.

30. The method of claim 19, comprising: while sampling the audio data, determining whether the input including activation of the text input area is maintained; as well as continuing to sample the audio data in response to determining that the input including activation of the text input area is maintained; Based on determining that the input including activation of the text input area is not maintained, sampling the audio data is discontinued.

31. The method of claim 19, comprising: determining whether the audio of the predetermined duration includes user speech; In response to determining that the audio of the predetermined duration includes user speech, continuing to sample the audio data; as well as Based on determining that the audio of the predetermined duration does not include user voice, sampling the audio data is terminated.

32. The method according to claim 31, wherein: The predetermined duration of audio includes the most recent duration of audio.

33. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component, the one or more programs comprising instructions for performing a method according to any one of claims 19-32.

34. An electronic device comprising: one or more processors; as well as A memory storing one or more programs, the one or more programs being configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 19-32.

35. An electronic device configured to communicate with one or more display generation components and one or more input devices, comprising: Apparatus for performing the method according to any one of claims 19-32.

36. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for performing the method according to any one of claims 19-32.

Images