Voice interaction for accessing the call function of a companion device at a host device

Abstract

The present disclosure generally relates to voice interaction for accessing a call function of a companion device at a main device. In an exemplary process, a user utterance is received. Based on the user utterance and context information, the process causes a server to determine a user intent corresponding to the user utterance. The context information is based on signals received from the companion device. A command is received according to the user intent corresponding to an executable intent to answer the incoming call. Based on the command, an instruction is provided to the companion device, and the instruction causes the companion device to answer the incoming call and provide audio data of answering the incoming call. Audio is output according to the audio data of answering the incoming call.

Description

[0001] This application is a divisional application of the patent application for invention "Voice Interaction for Accessing the Call Function of a Companion Device at a Primary Device" with the application date of March 27, 2019 and the application number 201980033273.7.

[0002] Cross - reference to Related Applications

[0003] This application claims priority to the following patent applications: U.S. Provisional Application No. 62 / 679,177, filed on June 1, 2018, entitled "Voice Interaction at a Primary Device to Access Call Functionality of a Companion Device"; U.S. Non - Provisional Application No. 16 / 113,119, filed on August 27, 2018, entitled "Voice Interaction at a Primary Device to Access Call Functionality of a Companion Device"; and Danish Patent Application No. PA201870373, filed on June 12, 2018, entitled "Voice Interaction at a Primary Device to Access Call Functionality of a Companion Device", the entire contents of which are hereby incorporated by reference for all purposes. Technical Field

[0004] The present invention generally relates to intelligent automation assistants, and more particularly, to using an intelligent automation assistant to access the call functionality of a companion device from a primary device. Background Art

[0005] Intelligent automation assistants (or digital assistants) can provide a beneficial interface between human users and electronic devices. Such assistants can allow users to interact with the device or system using natural language in voice form and / or text form. For example, a user can provide voice input containing a user request to a digital assistant running on an electronic device. The digital assistant can interpret the user's intention from the voice input and operationalize the user's intention into a task. These tasks can then be executed by performing one or more services of the electronic device, and relevant outputs in response to the user request can be returned to the user. Summary of the Invention

[0006] This document describes techniques for using voice interaction on a primary device to access call functions on a companion device. In one exemplary technique, voice interaction at the primary device is used to cause the companion device to answer an incoming call. In this technique, a signal is received from the companion device. The signal indicates that an incoming call has been detected on the companion device. User utterances are received and the server determines a user intent corresponding to the user utterance based on the user utterance and context information. The context information is based on the received signal. Based on the user intent corresponding to the executable intent of answering the incoming call, multiple operations are performed. The multiple operations include receiving a command from the server representing a task that satisfies the executable intent of answering the incoming call. Additionally, the multiple operations include providing an instruction to the companion device to answer the incoming call and relay audio data of the answered incoming call to an electronic device based on the command. According to the instruction to successfully cause the companion device to answer the incoming call, an audio output is output at the electronic device speaker based on the audio data of the answered incoming call received from the companion device. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0008] Figure 2A FIG. shows a block diagram of a portable multifunctional device implementing a client-side portion of a digital assistant according to various examples.

[0009] Figure 2B FIG. shows a block diagram of exemplary components for event processing according to various examples.

[0010] Figure 3 FIG. shows a portable multifunctional device implementing a client-side portion of a digital assistant according to various examples.

[0011] Figure 4 FIG. shows a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to various examples.

[0012] Figure 5A FIG. shows an exemplary user interface of a menu of an application on a portable multifunctional device according to various examples.

[0013] Figure 5B FIG. shows an exemplary user interface of a multifunctional device having a touch-sensitive surface separate from the display according to various examples.

[0014] Figure 6A FIG. shows a personal electronic device according to various examples.

[0015] Figure 6B FIG. shows a block diagram of a personal electronic device according to various examples.

[0016] Figure 7AA block diagram showing a digital assistant system or its server portion according to various examples.

[0017] Figure 7B Shows the functions of a digital assistant as shown in Figure 7A in accordance with various examples.

[0018] Figure 7C Shows a portion of a knowledge ontology according to various examples.

[0019] Figure 8 Shows techniques for using voice interaction at a primary device to cause a companion device to make a call according to various examples.

[0020] Figure 9 Shows techniques for using voice interaction at a primary device to cause a companion device to answer an incoming call according to various examples.

[0021] Figure 10 Shows techniques for using voice interaction at a primary device to cause a companion device to perform call-related tasks while the companion device is in a call according to various examples.

[0022] Figure 11 Shows techniques for using voice interaction at a primary device to cause a companion device to provide call-related information according to various examples.

[0023] Figures 12A to 12B Shows a process for using voice interaction to access the call function of a companion device according to various examples. Detailed Description

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

[0025] It may be necessary to use voice interaction to access the call function. For example, a user sitting in the living room of a home may wish to answer an incoming call on a smart phone left in the kitchen (e.g., ). Instead of retrieving the smart phone to answer the call, it is more convenient to use voice interaction (e.g., via a digital assistant) to answer the call. However, directly processing voice requests at the smart phone may be ineffective and unreliable. For example, the microphone and speaker of the smart phone may not be suitable for far-field voice interaction (e.g., between the kitchen and the living room). According to the techniques described herein, a primary device (e.g., a smart speaker) may be used to access the call function of a companion device (e.g., a smart phone). For example, a user can access the smart speaker in the living room (e.g., )。The smart speaker is paired with the user's smartphone, so the smart speaker can wirelessly communicate with the user's smartphone to access its call function. Therefore, it may be necessary to use voice interaction with the smart speaker to access the call function of the smartphone. Specifically, the microphone and speaker of the smart speaker can be configured to produce better sound quality for far-field voice interaction. In addition, the smart speaker can be used as a hub to control and coordinate access to the call function of the smartphone faster, more efficiently, and more intelligently. For example, the smart speaker can coordinate information among the user, the digital assistant server, and the user's smartphone to achieve the desired user experience, where the voice interaction is accurately interpreted, the response latency is shortened, and the sound quality is excellent.

[0026] In one exemplary technique for using voice interaction to access the call function of a companion device (e.g., a smartphone), a master device (e.g., a smart speaker) is used to cause the companion device to answer an incoming call. In this technique, a signal indicating an incoming call at the companion device is received at the master device. The master device receives the user's utterance and causes the server to determine the user's intent corresponding to the user's utterance based on the user's utterance and context information. The context information is based on the received signal. According to the user's intent corresponding to the executable intent of answering the incoming call, multiple operations are performed. The multiple operations include receiving, from the server, a command representing a task that satisfies the executable intent of answering the incoming call. The multiple operations also include providing, based on the command, an instruction to the companion device to answer the incoming call and relay the audio data of the answered incoming call to an electronic device. According to the instruction to successfully cause the companion device to answer the incoming call, an audio output at the speaker of the electronic device is output according to the audio data of the answered incoming call received from the companion device.

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

[0028] The terms used in the description of the various examples herein are for the purpose of describing particular examples only and are not intended to be limiting. As used in the description of the various examples and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will 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 components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0029] Depending on the context, the term “if” can be interpreted to mean “when” or “upon” or “in response to determining” or “in response to detecting.” Similarly, depending on the context, the phrases “if determined...” or “if [stated condition or event] is detected” can be interpreted to mean “when determining...” or “in response to determining...” or “when [stated condition or event] is detected” or “in response to detecting [stated condition or event].”

[0030] 1. System and Environment

[0031] Figure 1 A block diagram of a system 100 in accordance with various examples is shown. In some examples, system 100 implements a digital assistant. The terms “digital assistant,” “virtual assistant,” “intelligent automation assistant,” or “automated digital assistant” refer to any information processing system that interprets natural language input in oral form and / or text form to infer a user intention and performs an action based on the inferred user intention. For example, to act on the inferred user intention, the system performs one or more of the following steps: identifying a task flow having steps and parameters designed to implement the inferred user intention, inputting specific requirements into the task flow based on the inferred user intention; executing the task flow by invoking programs, methods, services, APIs, etc.; and generating an output response to the user in an audible (e.g., voice) and / or visual form.

[0032] Specifically, a digital assistant is capable of receiving user requests that are at least partially in the form of natural language commands, requests, statements, utterances, and / or queries. Generally, user requests seek an informative response from the digital assistant or the performance of a task. A satisfactory response to a user request includes providing the requested informative response, performing the requested task, or a combination of the two. For example, a user poses a question to the digital assistant, such as "Where am I now?". Based on the user's current location, the digital assistant responds with "You are near the west gate of Central Park." The user also requests the performance of 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 "Okay, right away" and then send appropriate calendar invitations on behalf of the user to each of the user's friends listed in the user's electronic address book. During the performance of the requested task, the digital assistant sometimes interacts with the user in an ongoing conversation involving multiple information exchanges over a long period of time. There are many other ways to interact 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, alerts, music, video, animation, etc.

[0033] As Figure 1 shown, in some examples, the digital assistant is implemented according to a client-server model. The digital assistant includes client portions (hereinafter referred to as "DA clients 102 and 124") that execute on the user device 104 and / or the second user device 122. The digital assistant also includes a server-side portion 106 (hereinafter referred to as "DA server 106") that executes on the server system 108. The DA clients 102 / 124 communicate with the DA server 106 via one or more networks 110. The DA clients 102 / 124 provide client functions, such as user-facing input and output processing, and communication with the DA server 106. The DA server 106 provides server-side functions for any number of DA clients located on respective user devices.

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

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

[0036] Examples of one or more communication networks 110 include a local area network (LAN) and a wide area network (WAN), such as the Internet. One or more communication networks 110 are implemented using any known network protocol, including various wired or wireless protocols, such as Ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Wi-Fi, Voice over Internet Protocol (VoIP), Wi-MAX, or any other suitable communication protocol.

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

[0038] In some examples, the second user device 122 functions as the primary device, and the user device 104 functions as a companion device to the second user device 122. In these examples, the user device 104 pairs with the second user device 122 and establishes a wireless communication connection with each other upon successful exchange of authentication information. In some examples, the user device 104 is a smart phone device having features similar to those of the device 200 or 400 (e.g., ) as described below with reference to Figure 2A , Figure 4 and Figures 6A to 6B . In some examples, the second user device 122 is a smart speaker device having only a subset of the features included in the device 200 or 400 (e.g., ). For example, the second user device 122 does not include a display or feature enabling an independent call function (e.g., the phone module 238 or the video conferencing module 239). Specifically, in these examples, the second user device 122 cannot make or receive calls without being communicatively coupled to the user device 104. When establishing the wireless communication connection, the second user device 122 is communicatively coupled to the user device 104 via a direct communication connection such as Bluetooth, NFC, BTLE, etc. or via a wireless network such as a local Wi-Fi network. In some examples, as described in more detail below, the second user device 122 accesses the call function of the user device 104 to perform call-related functions. For example, a user can provide voice input to the second user device 122 to make or receive calls on the user device 104.

[0039] Although Figure 1 the digital assistant shown therein includes both a client-side portion (e.g., the DA client 102) and a server-side portion (e.g., the DA server 106), in some examples, the functions of the digital assistant are implemented as a stand-alone application installed on the user device. Additionally, the functional division between the client portion and the server portion of the digital assistant may vary in different 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.

[0040] 2. Electronic Device

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

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

[0043] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of the device relative to a previous position of the device detected by a user using the user's sense of touch, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device. For example, in the case of contact between the device or a component of the device and a surface of the user sensitive to touch (e.g., a finger, palm, or other part of the user's hand), a haptic output generated by the physical displacement will be interpreted by the user as a sense of touch corresponding to a perceived change in the physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or a touchpad) may optionally be interpreted by the user as a "press click" or "release click" of a physical actuation button. In some cases, the user will sense a sense of touch, 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 interpretations of touch by the user will be limited by the user's individual sensory perception, many sensory perceptions of touch are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "press click", "release click", "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or its component that would generate the described sensory perception of a typical (or ordinary) user.

[0044] It should be understood that device 200 is only one example of a portable multifunctional device, and device 200 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has different configurations or arrangements of these components. Figure 2A The various components shown are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits.

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

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

[0047] 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. One or more processors 220 run or execute various software programs and / or instruction sets stored in the memory 202 to perform the 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 chip 204. In some other embodiments, they are implemented on separate chips.

[0048] The RF (Radio Frequency) circuit 208 receives and transmits RF signals, which are also referred to as electromagnetic signals. The RF circuit 208 converts electrical signals into electromagnetic signals / converts electromagnetic signals into electrical signals, and communicates with a communication network and other communication devices via electromagnetic signals. The RF circuit 208 optionally includes well-known circuits for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, a memory, and so on. The RF circuit 208 optionally communicates with the network and other devices via wireless communication, and these networks are such as the Internet (also known as the World Wide Web (WWW)), an intranet, and / or a wireless network (such as a cellular phone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN)). The RF circuit 208 optionally includes well-known circuits for detecting a near field communication (NFC) field, such as via a short-range communication radio component. The wireless communication optionally uses any one 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), Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), WiMAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the date of submission of this document.

[0049] The audio circuitry 210, speaker 211, and microphone 213 provide an audio interface between the user and the device 200. The audio circuitry 210 receives audio data from the peripheral interface 218, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 211. The speaker 211 converts the electrical signal into sound waves audible to humans. The audio circuitry 210 also receives the electrical signal converted from sound waves by the microphone 213. The audio circuitry 210 converts the electrical signal into audio data and transmits the audio data to the peripheral interface 218 for processing. The audio data is retrieved from and / or transmitted to the memory 202 and / or the RF circuitry 208 via the peripheral interface 218. In some embodiments, the audio circuitry 210 also includes an earphone jack (e.g., Figure 3 312 in

[0050] ). The earphone jack provides an interface between the audio circuitry 210 and a removable audio input / output peripheral device, such as an output-only headset or an earphone having both output (e.g., a mono or stereo earphone) and input (e.g., a microphone). Figure 3 308 in Figure 3 ). One or more buttons (e.g.,

[0051] Quickly pressing the depress button disengages the lock of the touch screen 212 or starts the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application No. 11 / 322,549, filed on December 23, 2005, titled "Unlocking a Device by Performing Gestures on an Unlock Image," which is incorporated herein by reference in its entirety. Pressing the depress button (e.g., 306) for a longer period turns the device 200 on or off. The user can customize the functions of one or more buttons. The touch screen 212 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

[0053] The touch screen 212 has a touch-sensitive surface, sensor, or group of sensors that accepts input from the user based on tactile and / or haptic contact. The touch screen 212 and the display controller 256 (along with any associated modules and / or instruction sets in the memory 202) detect contact (and any movement or interruption of the contact) on the touch screen 212 and convert the detected contact into an interaction with user interface objects (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.

[0054] The touch screen 212 uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, but other display technologies may be used in other embodiments. The touch screen 212 and the display controller 256 use any of a variety of touch-sensing technologies currently known or later to be 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, the variety of touch-sensing technologies 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 the technology used in and iPod used by

[0055] In some embodiments, the touch-sensitive display of the touchscreen 212 is similar to the multi-touch sensitive touchpad described in the following 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 touchscreen 212 displays visual output from the device 200, while the touch-sensitive touchpad does not provide visual output.

[0056] 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, entitled "Multipoint Touch Surface Controller", filed on May 2, 2006; (2) U.S. Patent Application No. 10 / 840,862, entitled "Multipoint Touchscreen", filed on May 6, 2004; (3) U.S. Patent Application No. 10 / 903,964, entitled "Gestures For Touch Sensitive Input Devices", filed on July 30, 2004; (4) U.S. Patent Application No. 11 / 048,264, entitled "Gestures For TouchSensitive Input Devices", filed on January 31, 2005; (5) U.S. Patent Application No. 11 / 038,590, entitled "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices", filed on January 18, 2005; (6) U.S. Patent Application No. 11 / 228,758, entitled "Virtual Input DevicePlacement On A Touch Screen User Interface", filed on September 16, 2005; (7) U.S. Patent Application No. 11 / 228,700, entitled "Operation Of A Computer With A Touch ScreenInterface", filed on September 16, 2005; (8) U.S. Patent Application No. 11 / 228,737, entitled "ActivatingVirtual Keys Of A Touch-Screen Virtual Keyboard", filed on September 16, 2005; and (9) U.S. Patent Application No. 11 / 367,749, entitled "Multi-Functional Hand-Held Device", filed on March 3, 2006. All of these applications are hereby incorporated by reference in their entirety.

[0057] 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 approximately 160 dpi. The user contacts the touch screen 212 using any suitable object or appendage such as a stylus, finger, etc. In some embodiments, the user interface is designed to work primarily through finger-based contact and gestures, which may not be as precise as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device converts the finger-based rough input into an accurate pointer / cursor position or command for performing the action desired by the user.

[0058] In some embodiments, in addition to the touch screen, the device 200 further includes a touchpad (not shown) for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of the device, which, unlike the touch screen, does not display a visual output. The touchpad is a touch-sensitive surface separate from the touch screen 212 or an extension of the touch-sensitive surface formed by the touch screen.

[0059] The device 200 also includes a power system 262 for powering various components. The power system 262 includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0060] The device 200 also includes one or more optical sensors 264. Figure 2A An optical sensor coupled to the optical sensor controller 258 in the I / O subsystem 206 is shown. The optical sensor 264 includes a charge-coupled device (CCD) or 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 combination with the imaging module 243 (also called the camera module), the optical sensor 264 captures still images or videos. In some embodiments, the optical sensor is located at the rear of the device 200, opposite the touch screen display 212 at the front of the device, such that the touch screen display is used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located at the front of the device such that an image of the user is acquired while the user views other video conference participants on the touch screen display for a video conference. 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) such that a single optical sensor 264 is used in conjunction with the touch screen display for both video conferencing and still image and / or video image acquisition.

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

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

[0063] Device 200 optionally further includes one or more haptic output generators 267. Figure 2AShows a haptic output generator coupled to a haptic feedback controller 261 in an I / O subsystem 206. The haptic output generator 267 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting an electrical signal into a haptic output on the device). The contact intensity sensor 265 receives haptic feedback generation instructions from the haptic feedback module 233 and generates a haptic output on the device 200 that can be sensed by a user of the device 200. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 212), and optionally generates a haptic output by moving the touch-sensitive surface vertically (e.g., into / out 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 haptic output generator sensor is located on the rear of the device 200, opposite to the touch screen display 212 located on the front of the device 200.

[0064] The device 200 also includes one or more accelerometers 268. Figure 2A Shows an accelerometer 268 coupled to the peripheral device interface 218. Alternatively, the accelerometer 268 is coupled to an input controller 260 in the I / O subsystem 206. The accelerometer 268 operates as described in the following U.S. Patent Publications: U.S. Patent Publication 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices” and U.S. Patent Publication 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer”, the entire disclosures of which are incorporated herein by reference. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on an 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 location and orientation (e.g., portrait or landscape) of the device 200.

[0065] In some embodiments, the software components stored in the memory 202 include an operating system 226, a communication module (or instruction set) 228, a touch / 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 application programs (or instruction sets) 236. In addition, the memory 202 stores data and models, such as user data and models 231. Further, in some embodiments, the memory 202 ( Figure 2A ) or 470 ( Figure 4 ) stores a device / global internal state 257, as Figure 2A and Figure 4 shown. The device / global internal state 257 includes one or more of the following: an active application state that indicates which applications, if any, are currently active; a display state that indicates what applications, views, or other information occupy the respective regions of the touchscreen display 212; a sensor state that includes information obtained from the various sensors and input control devices 216 of the device; and location information regarding the location and / or orientation of the device.

[0066] 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 facilitates communication between the various hardware components and software components.

[0067] 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 ports 224. The external ports 224 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled through a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is the same as or similar to and / or compatible with the 30-pin connector used on (a trademark of Apple Inc.) devices and is a multi-pin (e.g., 30-pin) connector. In some examples, the communication module 228 is configured to establish a wireless communication connection between the device 200 and a second device. Specifically, the communication module 228 coordinates the exchange of authentication information with the second device to determine whether the second device is a registered device of the device 200. When it is determined based on the exchanged authentication that the second device is a registered device of the device 200, the communication module 228 establishes (e.g., using the RF circuit 208) a wireless communication connection with the second device.

[0068] 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 a physical clickwheel). 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 intensity (e.g., the force or pressure of the contact, or a surrogate 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 ceased (e.g., detecting a finger lift event or contact break). The contact / motion module 230 receives contact data from the touch-sensitive surface. Determining the movement of 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 single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple finger contact). In some embodiments, the contact / motion module 230 and the display controller 256 detect contact on the touchpad.

[0069] 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 the user (e.g., determining whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds is determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a specific physical actuator and can be adjusted without changing the physical hardware of the device 200). For example, the mouse "click" threshold of the touchpad or touch screen can be set to any one of a wide range of predefined thresholds without changing the touchpad or touch screen display hardware. Additionally, in some implementations, software settings are provided to the user of the device for adjusting one or more of the intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using a system-level click on an "intensity" parameter).

[0070] The touch / motion module 230 optionally detects a user's gesture input. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timing, and / or intensities of the detected contact). Thus, gestures are optionally detected by detecting a particular contact pattern. 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 position (or substantially the same position) as the finger press event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift (lift-off) event.

[0071] The graphics module 232 includes various known software components for presenting and displaying graphics on the touch screen 212 or other display, including components for changing the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual characteristics). 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.

[0072] In some embodiments, the graphics module 232 stores data representing the 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, etc., and also receives coordinate data and other graphic attribute data as necessary, and then generates screen image data for output to the display controller 256.

[0073] The haptic feedback module 233 includes various software components for generating instructions that are used by one or more haptic output generators 267 to generate haptic output at one or more locations on the device 200 in response to user interaction with the device 200.

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

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

[0076] The digital assistant client module 229 includes various client - side digital assistant instructions to provide client - side functionality of the digital assistant. For example, the digital assistant client module 229 is capable of receiving voice input (e.g., speech input), text input, touch input, and / or gesture input through various user interfaces of the portable multifunctional device 200 (e.g., microphone 213, one or more accelerometers 268, touch - sensitive display system 212, one or more optical sensors 229, other input control devices 216, etc.). The digital assistant client module 229 is also capable of providing output in the form of audio (e.g., voice output), visual, and / or tactile through various output interfaces of the portable multifunctional 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, alert, text message, menu, graphics, 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.

[0077] The user data and model 231 includes 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 lists, shopping lists, etc.) to provide client - side functionality of the digital assistant. In addition, the user data and model 231 includes 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.).

[0078] In some examples, the digital assistant client module 229 utilizes various sensors, subsystems, and peripherals of the portable multifunctional device 200 to collect additional information from the surrounding environment of the portable multifunctional device 200 to establish 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 context information or a subset thereof together with the user input to the DA server 106 to assist in inferring user intent. In some examples, the digital assistant also uses the context information to determine how to prepare the output and deliver it to the user. The context information is referred to as context data.

[0079] In some examples, the context 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 context information may also include the physical state of the device, such as device orientation, device location, device temperature, power level, speed, acceleration, motion mode, 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 multifunctional device 200, installed programs, past and current network activities, background services, error logs, resource usage, etc., is provided as context information associated with the user input to the DA server 106.

[0080] In some examples, the digital assistant client module 229 selectively provides information stored on the portable multifunctional 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 solicits additional input from the user via natural language conversations or other user interfaces when requested by the DA server 106. The digital assistant client module 229 transmits this additional input to the DA server 106 to assist the DA server 106 in intent inference and / or realizing the user intent expressed in the user request.

[0081] The following is a more detailed description with reference to Figures 7A to 7C the digital assistant. It should be recognized that the digital assistant client module 229 may include any number of sub - modules of the digital assistant module 726 described below.

[0082] The application 236 includes the following modules (or instruction sets) or subsets or supersets thereof:

[0083] · Contact module 237 (sometimes referred to as an address book or contact list);

[0084] · Phone module 238;

[0085] · Video conferencing module 239;

[0086] · Email client module 240;

[0087] · Instant messaging (IM) module 241;

[0088] · Fitness support module 242;

[0089] · Camera module 243 for still images and / or video images;

[0090] · Image management module 244;

[0091] · Video player module;

[0092] · Music player module;

[0093] · Browser module 247;

[0094] · Calendar module 248;

[0095] · Desktop applet module 249, which in some examples includes one or more of the following: weather desktop applet 249-1, stock desktop applet 249-2, calculator desktop applet 249-3, alarm desktop applet 249-4, dictionary desktop applet 249-5, and other desktop applets obtained by the user and desktop applets created by the user 249-6;

[0096] · Desktop applet creator module 250 for forming the desktop applet created by the user 249-6;

[0097] · Search module 251;

[0098] · Video and music player module 252, which combines a video player module and a music player module;

[0099] · Notepad module 253;

[0100] · Map module 254; and / or

[0101] · Online video module 255.

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

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

[0104] In combination with RF circuitry 208, audio circuitry 210, speaker 211, microphone 213, touch screen 212, display controller 256, contact / motion module 230, graphics module 232, and text input module 234, the telephone module 238 is operative to input a character sequence corresponding to a telephone number, access one or more telephone numbers in the contacts module 237, modify a telephone number already input, place a call to the corresponding telephone number, conduct a session, and disconnect or hang up when the session is complete. As described above, the wireless communication uses any of a variety of communication standards, protocols, and technologies.

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

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

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

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

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

[0110] In combination with the touch screen 212, display controller 256, contact / 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, tagging, deleting, presenting (e.g., in a digital slide show or album), and storing still images and / or video images.

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

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

[0113] 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 micro application that can be downloaded and used by the user (e.g., weather desktop widget 249-1, stock market desktop widget 249-2, calculator desktop widget 249-3, alarm clock desktop widget 249-4, and dictionary desktop widget 249-5) or a micro application created by the user (e.g., 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., Yahoo! desktop widget).

[0114] 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 creator module 250 is used by the user to create desktop widgets (e.g., to turn a user-specified portion of a web page into a desktop widget).

[0115] In combination with the touch screen 212, the display controller 256, the contact / motion module 230, the graphics module 232, and the 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) according to a user instruction.

[0116] In combination with the touch screen 212, the display controller 256, the contact / motion module 230, the graphics module 232, the audio circuit 210, the speaker 211, the RF circuit 208, and the browser module 247, the video and music player module 252 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing back videos (e.g., on the touch screen 212 or on an external display connected via the external port 224). In some embodiments, the device 200 optionally includes the functionality of an MP3 player such as an iPod (a trademark of Apple Inc.).

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

[0118] In combination with the RF circuit 208, touch screen 212, display controller 256, contact / motion module 230, graphics module 232, text input module 234, GPS module 235, and browser module 247, the map module 254 is configured to receive, display, modify, and store maps and map-associated data (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.

[0119] In combination 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., via streaming and / or downloading), play back (e.g., on the touch screen or via an external port 224 on a connected external display), send an email with a link to a particular online video, and otherwise manage online videos in one or more file formats (such as, H.264). In some embodiments, the instant messaging module 241 is used instead of the email client module 240 to send a link to a particular online video. Other descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed Jun. 20, 2007, and titled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed Dec. 31, 2007, and titled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0120] Each of the above-described modules and applications corresponds to a set of executable instructions for performing one or more of the above-described functions 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., the instruction sets) need not be implemented as separate software programs, processes, or modules, and thus in various embodiments, various subsets of these modules may be combined or otherwise rearranged. For example, a video player module may be combined with a music player module into a single module (e.g., Figure 2Athe video and music player module 252). In 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.

[0121] In some embodiments, the device 200 is a device in which a predefined set of functions on the device is performed uniquely through a touchscreen and / or a touchpad. By using the touchscreen and / or the touchpad as the main 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.

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

[0123] Figure 2B is a block diagram showing exemplary components for event handling according to some embodiments. In some embodiments, the memory 202 ( Figure 2A ) or the 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 foregoing applications 237 to 251, 255, 480 to 490).

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

[0125] In some embodiments, the application internal state 292 includes additional information, such as one or more of the following: recovery 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.

[0126] The event monitor 271 receives event information from the peripheral device interface 218. The event information includes information about sub-events (e.g., a user touch on the touch-sensitive display 212 as part of a multi-touch gesture). The peripheral device interface 218 transmits information that it receives from the I / O subsystem 206 or sensors such as proximity sensor 266, one or more accelerometers 268, and / or microphone 213 (via the audio circuit 210). The information that the peripheral device interface 218 receives from the I / O subsystem 206 includes information from the touch-sensitive display 212 or a touch-sensitive surface.

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

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

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

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

[0131] The hit view determination module 272 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchical structure, the hit view determination module 272 identifies the hit view as the lowest view in the hierarchical structure that should handle the sub-events. 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 a potential event) occurs. Once the hit view is identified by the hit view determination module 272, the hit view generally receives all sub-events related to the same touch or input source for which it is identified as the hit view.

[0132] The 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, the active event recognizer determination module 273 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognizer determination module 273 determines that all views that include the physical location of the sub-event are actively participating views and, thus, 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 a particular view, higher views in the hierarchy will still remain as actively participating views.

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

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

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

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

[0137] The event receiver 282 receives event information from event classifier 270. The event information includes information about sub-events such as a touch or a touch movement. 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 (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device pose).

[0138] Event comparator 284 compares the event information with predefined event or sub - event definitions and, based on that 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 contains definitions of events (e.g., predefined sequences of sub - events), such as Event 1 (287 - 1), Event 2 (287 - 2), and other events. In some embodiments, sub - events in an 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 - tap on a displayed object. For example, a double - tap includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift - off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on the displayed object, and a second lift - off (touch end) of a predetermined duration. In another example, the definition of Event 2 (287 - 2) is a drag on a displayed object. For example, a drag includes a touch (or contact) of a predetermined duration on the displayed object, movement of the touch on the touch - sensitive display 212, and lift - off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 290.

[0139] In some embodiments, event definition 287 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 284 performs a hit test to determine which user interface object is associated with a sub - event. For example, in an application view that displays 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, event comparator uses the result of the hit test to determine which event handler 290 should be activated. For example, event comparator 284 selects the event handler associated with the sub - event and the object that triggered the hit test.

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

[0141] When the corresponding event recognizer 280 determines that the sub - event sequence does not match any event in the 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 such a case, other event recognizers (if any) that remain active for the hit view continue to track and process the ongoing sub - events of the touch - based gesture.

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

[0143] In some embodiments, when one or more specific sub - events of an event are recognized, the corresponding event recognizer 280 activates the event handler 290 associated with the event. In some embodiments, the corresponding event recognizer 280 delivers event information associated with the event to the event handler 290. Activating the event handler 290 is different from sending (and deferring to send) sub - events to the corresponding hit view. In some embodiments, the event recognizer 280 throws a token associated with the recognized event, and the event handler 290 associated with that token retrieves the token and executes a predefined process.

[0144] In some embodiments, the event delivery instruction 288 includes a sub - event delivery instruction that delivers event information about the sub - event without activating the event handler. Instead, the sub - event delivery instruction delivers the event information to the event handler associated with the sub - event sequence or to the actively participating view. The event handler associated with the sub - event sequence or with the actively participating view receives the event information and executes a predetermined process.

[0145] In some embodiments, the data updater 276 creates and updates data used in the application 236-1. For example, the data updater 276 updates the phone numbers used in the contact module 237 or stores the video files used in the video player module. In some embodiments, the object updater 277 creates and updates objects used in the application 236-1. For example, the object updater 277 creates new user interface objects or updates the positions of user interface objects. The GUI updater 278 updates the GUI. For example, the GUI updater 278 prepares the display information and sends the display information to the graphics module 232 for display on the touch-sensitive display.

[0146] In some embodiments, the event handler 290 includes or has access to the data updater 276, the object updater 277, and the GUI updater 278. In some embodiments, the data updater 276, the object updater 277, and the 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.

[0147] It should be understood that the above discussion of event handling for user touches on the touch-sensitive display also applies to other forms of user input for operating the multifunctional device 200 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in cooperation with single or multiple keyboard presses or holds; contact movement on a touchpad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal instructions; detected eye movement; biometric input; and / or any combination thereof are optionally used as inputs corresponding to sub-events that define the events to be recognized.

[0148] Figure 3FIG. 0 shows a portable multifunctional device 200 having a touch screen 212 according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 300. In this and other embodiments described below, a user can select one or more of these graphics by making gestures on the graphics using, for example, one or more fingers 302 (not drawn to scale in the figures) or one or more styli 303 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gestures optionally include one or more taps, one or more swipes (from left to right, right to left, up, and / or down), and / or rolling of a finger that has made contact with the device 200 (from right to left, left to right, up, and / or down). In some implementations or in some cases, inadvertently contacting a graphic does not select the graphic. For example, when the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

[0149] 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 of the applications 236 in a set of applications executed 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.

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

[0151] Figure 4is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface, in accordance with some embodiments. Device 400 need not be portable. In some embodiments, device 400 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home or industrial controller). Device 400 generally includes one or more processing units (CPUs) 410, one or more network or other communication interfaces 460, memory 470, and one or more communication buses 420 for interconnecting these components. The communication bus 420 optionally includes circuitry (sometimes termed a chipset) that interconnects the system components and controls the communication between the system components. Device 400 includes an input / output (I / O) interface 430 having a display 440, which is typically a touchscreen display. The I / O interface 430 also optionally includes a keyboard and / or mouse (or other pointing device) 450 and a touchpad 455, a haptic output generator 457 for generating haptic output on device 400 (e.g., similar to one or more of the haptic output generators 267 described above with reference to Figure 2A ), sensors 459 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and / or contact intensity sensors (similar to one or more of the contact intensity sensors 265 described above with reference to Figure 2A ). Memory 470 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 470 optionally includes one or more storage devices located remotely from the CPU 410. In some embodiments, memory 470 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in the memory 202 of the portable multifunctional device 200 ( Figure 2A ). Additionally, memory 470 optionally stores additional programs, modules, and data structures not present in the memory 202 of the portable multifunctional device 200. For example, the memory 470 of device 400 optionally stores a drawing module 480, a presentation module 482, a word processing module 484, a website creation module 486, a disk editing module 488, and / or a spreadsheet module 490, while the memory 202 of the portable multifunctional device 200 ( Figure 2A ) optionally does not store these modules.

[0152] Figure 4Each of the above-described components in some examples is stored in one or more of the previously mentioned memory devices. Each of the above modules corresponds to a set of instructions for performing the above functions. The above modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, so various subsets of these modules are combined or otherwise rearranged in various embodiments. In some embodiments, memory 470 stores a subset of the above modules and data structures. Additionally, memory 470 stores additional modules and data structures not described above.

[0153] Attention is now turned to embodiments of a user interface that can be implemented on, for example, a portable multifunctional device 200.

[0154] Figure 5A An exemplary user interface of an application menu on a portable multifunctional device 200 is shown according to some embodiments. A similar user interface is implemented on device 400. In some embodiments, the user interface 500 includes the following components or a subset or superset thereof:

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

[0156] · Time 504;

[0157] · Bluetooth indicator 505;

[0158] · Battery status indicator 506;

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

[0160] ο An icon 516 labeled "Phone" for the phone module 238, which optionally includes an indicator 514 of the number of missed calls or voicemails;

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

[0162] ο An icon 520 labeled "Browser" for the browser module 247; and

[0163] ο An icon 522 labeled "iPod" for the video and music player module 252 (also referred to as the iPod (trademark of Apple Inc.) module 252); and

[0164] · Icons for other applications, such as:

[0165] ο An icon 524 labeled "Messages" for the IM module 241;;

[0166] ο The icon 526 marked as "Calendar" of the calendar module 248;;

[0167] ο The icon 528 marked as "Photos" of the image management module 244;;

[0168] ο The icon 530 marked as "Camera" of the camera module 243;;

[0169] ο The icon 532 marked as "Online Video" of the online video module 255;;

[0170] ο The icon 534 marked as "Stock Market" of the stock market desktop applet 249-2;;

[0171] ο The icon 536 marked as "Map" of the map module 254;;

[0172] ο The icon 538 marked as "Weather" of the weather desktop applet 249-1;;

[0173] ο The icon 540 marked as "Clock" of the alarm clock desktop applet 249-4;;

[0174] ο The icon 542 marked as "Fitness Support" of the fitness support module 242;;

[0175] ο The icon 544 marked as "Notepad" of the notepad module 253; and

[0176] ο The icon 546 marked as "Settings" for setting up an application or module, which provides access to the settings of the device 200 and its various applications 236.

[0177] It should be noted that Figure 5A The icon labels shown are merely exemplary. For example, the icon 522 of the video and music player module 252 is optionally marked as "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 specific application icon is different from the name of the application corresponding to the specific application icon.

[0178] Figure 5B A device is shown having a touch-sensitive surface 551 (e.g., Figure 4 a tablet or touchpad 455) separate from the display 550 (e.g., Figure 4Exemplary user interface on device 400). The device 400 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 457) for detecting the intensity of contacts on the touch-sensitive surface 551 and / or one or more haptic output generators 459 for generating haptic output for a user of the device 400.

[0179] Although some of the subsequent examples will be given with reference to inputs on a touch screen display 212 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface separate from the display, as Figure 5B shown. In some embodiments, the touch-sensitive surface (e.g., Figure 5B 551 in ) has a main axis (e.g., Figure 5B 552 in ) corresponding to the main axis (e.g., Figure 5B 553 in ) on the display (e.g., 550). According to these embodiments, the device detects contacts (e.g., Figure 5B 560 and 562 in ) with the touch-sensitive surface 551 at positions corresponding to the respective positions on the display (e.g., in Figure 5B 560 corresponds to 568 and 562 corresponds to 570). Thus, when the touch-sensitive surface (e.g., Figure 5B 551 in ) is separate from the display of the multifunctional device (e.g., Figure 5B 550 in ), user inputs detected by the device on the touch-sensitive surface (e.g., contacts 560 and 562 and their movements) are used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0180] In addition, although the following examples are mainly 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 inputs 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 a contact), followed by a movement of the cursor along the path of the swipe (e.g., instead of a movement of the contact). Another example is that a tap gesture is optionally replaced by a mouse click when the cursor is above the position of the tap gesture (e.g., instead of detecting a contact, followed by stopping the detection of the 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 a finger contact are optionally used simultaneously.

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

[0182] Techniques for detecting and processing touch intensity may exist, for example, in the related applications: International Patent Application PCT / US2013 / 040061, filed on May 8, 2013, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", and International Patent Application PCT / US2013 / 069483, filed on November 11, 2013, entitled "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships", each of which is hereby incorporated by reference in its entirety.

[0183] In some embodiments, the device 600 has one or more input mechanisms 606 and 608. The input mechanisms 606 and 608, if included, are in physical form. 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, watch bands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 600.

[0184] Figure 6BAn exemplary personal electronic device 600 is shown. In some embodiments, device 600 includes some or all of the components described with respect to Figure 2A , Figure 2B and Figure 4 . Device 600 has a bus 612 that operatively couples the I / O section 614 to one or more computer processors 616 and a memory 618. The I / O section 614 is connected to a display 604 that may have a touch-sensitive component 622 and optionally also a touch-intensity sensitive component 624. Additionally, the I / O section 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 pressable input device and a rotatable input device. In some examples, input mechanism 608 is a button.

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

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

[0187] As used herein, the term "enabling representation" refers to, for example, user-interactive graphical user interface objects displayed on the display screens of devices 200, 400, and / or 600 ( Figure 2A , Figure 4 and Figures 6A - 6B ). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each constitute an enabling representation.

[0188] As used herein, the term "focus selector" refers to an input element that is used to indicate the current portion of a user interface with which a user is interacting. In some particular implementations that include a cursor or other position marker, the cursor serves as the "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., Figure 4 the touchpad 455 in Figure 5B or the touch-sensitive surface 551 in Figure 2A the touch-sensitive display system 212 in Figure 5A or the touch screen 212 in

[0189] ) above a particular user interface element (e.g., a button, a window, a slider, or other user interface element), that particular user interface element is adjusted in accordance with the detected input. In some particular implementations that include a touch screen display (e.g., Figure 2A the touch-sensitive display system 212 in Figure 5A or the touch screen 212 in

[0189] ) that enables direct interaction with user interface elements on the touch screen display, a contact detected on the touch screen serves as the "focus selector" such that when an input (e.g., a press input made by the contact) is detected at the location of a particular user interface element (e.g., a button, a window, a slider, or other user interface element) on the touch screen display, that particular user interface element is adjusted in accordance with the detected input. In some particular implementations, the focus moves from one area of the user interface to another area of the user interface without a corresponding movement of the cursor or a movement of the contact on the touch screen display (e.g., by using the tab key or arrow keys to move the focus from one button to another button); in these particular implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the particular form that the focus selector takes, the focus selector is generally a user interface element (or a contact on the touch screen display) that is controlled by the user in order to effectuate the interaction with the user interface that the user anticipates (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 touchpad or a touch screen), the position of the focus selector (e.g., the cursor, the contact, or the selection box) above the corresponding button will indicate that the user desires to activate the corresponding button (as opposed to other user interface elements shown on the device display).

[0189] As used in the specification and claims, the term "feature intensity" of a contact refers to a feature of the contact based on one or more intensities of the contact. In some embodiments, the feature intensity is based on a plurality of intensity samples. The feature intensity is optionally based on a predefined number or set of intensity samples collected during a predefined period of time (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 detecting the contact, before detecting the lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact). The feature intensity of the contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half-maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used in determining the feature intensity (e.g., when the feature intensity is the average value of the contact intensity over time). In some embodiments, the feature intensity is compared with a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds includes a first intensity threshold and a second intensity threshold. In this example, a contact with a feature intensity not exceeding the first threshold results in a first operation, a contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second operation, and a contact with a feature intensity exceeding the second threshold results in a third operation. In some embodiments, the comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to forgo performing the corresponding operation), rather than for determining whether to perform a first operation or a second operation.

[0190] In some embodiments, a portion of a gesture is identified for use in determining the feature intensity. For example, the touch-sensitive surface receives a continuous swiping contact that transitions from a starting position to an ending position at which the intensity of the contact increases. In this example, the feature intensity of the contact at the ending position is based only on a portion of the continuous swiping contact, rather than the entire swiping contact (e.g., only the portion of the swiping contact that is at the ending position). In some embodiments, a smoothing algorithm is applied to the intensity of the swiping contact before determining the feature intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted moving 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 spikes or dips in the intensity of the swiping contact for the purpose of determining the feature intensity.

[0191] 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 an operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts below the nominal contact detection intensity threshold are no longer detected), the device will move a focus selector based on 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 sets of user interface figures.

[0192] An increase in contact characteristic intensity from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact characteristic intensity from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact characteristic intensity from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. A decrease in contact characteristic intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0193] 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 contacts), wherein the corresponding press input is detected at least in part based on detecting an increase in the intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, a corresponding operation is performed in response to detecting an increase in the intensity of the corresponding contact above the press input intensity threshold (e.g., the "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below the press input intensity threshold, and a corresponding operation is performed in response to detecting a subsequent decrease in the intensity of the corresponding contact below the press input threshold (e.g., the "up stroke" of the corresponding press input).

[0194] In some embodiments, the device employs strength hysteresis to avoid unexpected inputs sometimes referred to as "jitter", where the device defines or selects a hysteresis strength threshold having a predefined relationship to a press input strength threshold (e.g., the hysteresis strength threshold is X strength units lower than the press input strength threshold, or the hysteresis strength threshold is 75%, 90%, or some reasonable proportion of the press input strength threshold). Thus, in some embodiments, a press input includes the intensity of a corresponding contact increasing above the press input strength threshold and the intensity of that contact subsequently decreasing below the hysteresis strength threshold corresponding to the press input strength threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis strength threshold (e.g., the "upstroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or lower than the hysteresis strength threshold to an intensity equal to or higher than the press input strength threshold and optionally the contact intensity subsequently decreases to an intensity equal to or lower than the hysteresis strength, and a corresponding operation is performed in response to detecting the press input (e.g., depending on the context, the contact intensity increases or the contact intensity decreases).

[0195] For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is triggered in response to detecting any one of the following various conditions: the contact intensity increasing above the press input strength threshold, the contact intensity increasing from an intensity lower than the hysteresis strength threshold to an intensity higher than the press input strength threshold, the contact intensity decreasing below the press input strength threshold, and / or the contact intensity decreasing below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in an example where an operation is described as being performed in response to detecting that the intensity of a contact decreases below the press input strength threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below the hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0196] 3. Digital Assistant System

[0197] Figure 7A A block diagram of a digital assistant system 700 is shown in accordance with various examples. 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 partitioned 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, e.g., as Figure 1 shown. In some examples, the digital assistant system 700 isFigure 1 The specific implementation of the server system 108 (and / or the 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 different configurations or layouts of components. Figure 7A The various components shown in are implemented in hardware, software instructions executed by one or more processors, firmware (including one or more signal processing integrated circuits and / or application specific integrated circuits), or combinations thereof.

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

[0199] In some examples, the 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).

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

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

[0202] 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: an operating system 718, a communication module 720, a user interface module 722, one or more application programs 724, and a 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. The one or more processors 704 execute these programs, modules, and instructions and read data from or write data to the data structures.

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

[0204] The communication module 720 facilitates communication between the digital assistant system 700 and other devices via the network communication interface 708. For example, the communication module 720 communicates with the RF circuitry 208 of an electronic device (such as the devices 200, 400, or 600 shown respectively in Figure 2A , Figure 4 , Figures 6A to 6B ). The communication module 720 also includes various components for processing data received by the wireless circuitry 714 and / or the wired communication ports 712.

[0205] The user interface module 722 receives commands and / or inputs from a 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 a display. The user interface module 722 also prepares outputs (e.g., voice, sound, animation, text, icons, vibration, haptic feedback, lighting, etc.) and transmits them to the user via the I / O interface 706 (e.g., through a display, audio channel, speaker, touchpad, etc.).

[0206] The application 724 includes 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, the application 724 includes user applications such as games, calendar applications, navigation applications, or mail applications. If the digital assistant system 700 is implemented on a server, the application 724 includes, for example, a resource management application, a diagnostic application, or a scheduling application.

[0207] 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 sub-modules or a subset or superset thereof: an input / output processing module 728, a speech-to-text (STT) processing module 730, a natural language processing module 732, a dialogue 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 lexical index 744, user data 748, a task flow model 754, a service model 756, and an ASR system 758.

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

[0209] In some examples, as Figure 7B shown, the I / O processing module 728 can interact with the user through the I / O device 716 in Figure 7A or through Figure 7AThe network communication interface 708 therein 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 a voice output). The I / O processing module 728 optionally obtains context information associated with the user input from the user device either along with or shortly after receiving the user input. The context information includes user-specific data, vocabulary, and / or preferences related to the user input. In some examples, the context information also includes the software state and hardware state of the user device at the time the user request is received, and / or information related to the user's surrounding environment at the time the user request is received. In some examples, the I / O processing module 728 also sends follow-up questions related to the user request to the user and receives answers from the user. When the user request is received by the I / O processing module 728 and the user request includes voice input, the I / O processing module 728 forwards the voice input to the STT processing module 730 (or speech recognizer) for speech-to-text conversion.

[0210] 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 through the I / O processing module 728 to generate recognition results. Each ASR system 758 includes a front-end speech pre-processor. The front-end speech pre-processor extracts representative features from the speech input. For example, the front-end speech pre-processor performs a Fourier transform on the speech input to extract spectral features characterizing the speech input as a sequence of representative multi-dimensional vectors. Additionally, 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 transducers (WFST). The one or more speech recognition models and the one or more speech recognition engines are used to process the extracted representative features of the front-end speech pre-processor to generate intermediate recognition results (e.g., phonemes, strings of phonemes, and sub-words), and ultimately generate text recognition results (e.g., words, strings of words, or sequences of symbols). In some examples, the speech input is at least partially processed by a third-party service or on the user's device (e.g., device 104, device 200, device 400, or device 600) to generate recognition results. Once the STT processing module 730 generates a recognition result that includes a text string (e.g., words, or a sequence of words, or a sequence of symbols), the recognition result is transmitted to the natural language processing module 732 for intent inference. In some examples, the STT processing module 730 generates multiple candidate text representations of the speech input. Each candidate text representation is a sequence of words or symbols corresponding to the speech input. In some examples, each candidate text representation is associated with a speech 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. As another example, the 5 highest-ranked (n = 5) candidate text representations are passed to the natural language processing module 732 for intent inference.

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

[0212] In some examples, the STT processing module 730 includes a vocabulary of recognizable words and / or accesses the vocabulary via a phonetic conversion module 731. Each vocabulary word is associated with one or more candidate pronunciations of the word represented in a speech recognition phonetic alphabet. Specifically, the vocabulary of recognizable words includes words associated with multiple candidate pronunciations. For example, the vocabulary includes the word "tomato" associated with candidate pronunciations of and . 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 are associated with a particular user via a user profile on the device. In some examples, candidate pronunciations of a word are determined based on the spelling of the word and one or more linguistic and / or phonetic rules. In some examples, candidate pronunciations are generated manually, e.g., based on known standard pronunciations.

[0213] In some examples, candidate pronunciations are ranked based on their prevalence. For example, the candidate pronunciation is ranked higher than because the former is a more commonly used pronunciation (e.g., among all users, among users in a particular geographic region, or among any other suitable subset of users). In some examples, candidate pronunciations are ranked based on whether they are custom candidate pronunciations associated with the user. For example, custom candidate pronunciations are ranked higher than standard candidate pronunciations. This can be used to identify proper names with unique pronunciations that deviate from the norm. In some examples, candidate pronunciations are associated with one or more speech characteristics such as geographic origin, country, or ethnicity. For example, the candidate pronunciation is associated with the United States, while the candidate pronunciations are associated with the United Kingdom. Additionally, the ranking of candidate pronunciations is based on one or more characteristics of the user (e.g., geographic origin, country, ethnicity, etc.) stored in the user profile on the device. For example, it can 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 pronunciation (associated with the United States) may be ranked higher than the candidate pronunciation (associated with the United Kingdom). In some examples, one of the ranked candidate pronunciations can be selected as the predicted pronunciation (e.g., the most likely pronunciation).

[0214] When a voice input is received, the STT processing module 730 is used (e.g., using a voice model) to determine the phonemes corresponding to the voice input, and then attempts to (e.g., using a language model) determine the words that match the phonemes. For example, if the STT processing module 730 first identifies a sequence of phonemes corresponding to a portion of the voice input then it may subsequently determine that the sequence corresponds to the word "tomato" based on the lexical index 744.

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

[0216] The natural language processing module 732 of the digital assistant ("natural language processor") obtains the n-best candidate text representations ("sequence of words" or "sequence of symbols") 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 performed by the digital assistant and can have an associated task flow that is implemented in the task flow model 754. The associated task flow is a series of programmed actions and steps that the digital assistant takes to perform a 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 a user request expressed in natural language.

[0217] 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, for example, context information associated with the user request 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. Context information includes, for example, user preferences, the hardware and / or software state of the user's device, sensor information collected before, during, or shortly after the user request, previous interactions (e.g., conversations) between the digital assistant and the user, and so on. As described herein, in some examples, the context information is dynamic and varies with the time, location, content, and other factors of the conversation.

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

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

[0220] In addition, the attribute nodes "cuisine", "price range", "phone number", and "location" are child nodes of the attribute node "restaurant" and are all connected to the "restaurant reservation" node (i.e., the executable intent node) through the intermediate attribute node "restaurant". Again, as Figure 7C shown, the knowledge ontology 760 also includes a "set reminder" node (i.e., another executable intent node). The attribute nodes "date / time" (for setting the reminder) and "subject" (for the reminder) are both connected to the "set reminder" node. Since the attribute "date / time" is relevant 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 the knowledge ontology 760.

[0221] An executable intent node, together with its linked attribute nodes, is described as a "domain" representing a specific concept. 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 specific executable intent. For example, Figure 7CThe ontology 760 shown includes examples of a restaurant reservation domain 762 and a reminder domain 764 within the ontology 760. The restaurant reservation domain 762 represents the concept of making a restaurant reservation. The restaurant reservation domain includes the executable intent node "restaurant reservation", the attribute nodes "restaurant", "date / time", and "party size", and the sub-attribute nodes "cuisine", "price range", "phone number", and "location". The reminder domain 762 represents the concept of setting and providing reminders. The reminder domain 764 includes the executable intent node "set reminder" and the 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 domain, travel reservation domain, movie ticket domain, etc.).

[0222] Although Figure 7C two exemplary domains within the ontology 760 are shown, other domains include, for example, "find movie", "make a call", "find directions", "schedule a meeting", "send a message", and "provide an answer to a question", "reading list", "provide navigation instructions", "provide instructions for a task", etc. The "send a message" domain is associated with the "send a message" executable intent node and further includes attribute nodes such as "one or more recipients", "message type", and "message body". The attribute node "recipient" is further defined, for example, by sub-attribute nodes such as "recipient name" and "message address".

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

[0224] In some examples, nodes associated with multiple related executable intents are clustered under a "super domain" in the ontology 760. For example, the "travel" super domain includes a cluster of attribute nodes and executable intent nodes related to travel. Executable intent nodes related to travel include "flight reservation", "hotel reservation", "car rental", "get directions", "find points of interest", etc. Executable intent nodes under the same super domain (e.g., the "travel" super domain) have multiple shared attribute nodes. For example, the executable intent nodes for "flight reservation", "hotel reservation", "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".

[0225] In some examples, each node in the 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 the so-called "lexicon" associated with the node. The corresponding set of words and / or phrases associated with each node is stored in a lexicon index 744 associated with the attribute or executable intent represented by the node. For example, returning Figure 7B , the lexicon associated with the node of the "restaurant" attribute includes words such as "food", "drinks", "cuisine", "hunger", "eat", "pizza", "fast food", "meal", etc. As another example, the lexicon associated with the node of the "initiate a phone call" executable intent includes words and phrases such as "call", "make a phone call", "dial", "talk on the phone with...", "call this number", "call...", etc. The lexicon index 744 optionally includes words and phrases in different languages.

[0226] The natural language processing module 732 receives a candidate text representation (e.g., one or more text strings or one or more sequences of symbols) from the STT processing module 730, and for each candidate representation, determines which nodes the words in the candidate text representation pertain to. In some examples, if a word or phrase in the candidate text representation is associated (via the lexicon index 744) with one or more nodes in the ontology 760, then 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 for 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 respective 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 during the process of selecting nodes, such as whether the digital assistant has previously correctly interpreted similar requests from the user.

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

[0228] It should be recognized that in some examples, one or more machine learning mechanisms (e.g., neural networks) are utilized to implement the natural language processing module 732. Specifically, one or more machine learning mechanisms are configured to receive a candidate text representation and context information associated with the candidate text representation. Based on the candidate text representation and the associated context information, 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 the set of candidate executable intents based on the determined intent confidence score. In some examples, a knowledge ontology (e.g., knowledge ontology 760) is also utilized to select one or more candidate executable intents from the set of candidate executable intents.

[0229] Other details regarding searching a knowledge ontology based on a symbol string are described in U.S. Utility Patent Application Serial No. 12 / 341,743, entitled "Method and Apparatus for Searching Using An Active Ontology", filed on Dec. 22, 2008, the entire disclosure of which is incorporated herein by reference.

[0230] 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 populated with specific information and requirements specified in the user request. For example, the user says "Help me reserve a seat at a sushi restaurant at 7 pm." 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 for the "restaurant reservation" domain includes parameters such as {cuisine}, {time}, {date}, {number of people in the party}, etc. In some examples, based on the voice input and the text derived from the voice input using the STT processing module 730, the natural language processing module 732 generates a partially structured query for the restaurant reservation domain, where the partially structured query includes the parameters {cuisine = "sushi"} and {time = "7 pm"}. However, in this example, the user's 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 people in the party} and {date} are not specified in the structured query. In some examples, the natural language processing module 732 populates some of the parameters of the structured query with the received context information. For example, in some examples, if the user requests a "nearby" sushi restaurant, the natural language processing module 732 populates the {location} parameter in the structured query with the GPS coordinates from the user's device.

[0231] In some examples, the natural language processing module 732 identifies multiple candidate executable intents for each candidate text representation received from the STT processing module 730. Additionally, in some examples, a corresponding structured query (partially or fully) is generated for each identified candidate executable intent. The natural language processing module 732 determines an intent confidence score for each candidate executable intent and ranks the candidate executable intents based on the intent confidence scores. In some examples, the natural language processing module 732 transmits one or more generated 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., m highest-ranked) candidate executable intents are provided to the task flow processing module 736, where m is a predetermined integer greater than zero. In some examples, one or more structured queries for the m best candidate executable intents are provided to the task flow processing module 736 along with the corresponding one or more candidate text representations.

[0232] Additional details of inferring user intent based on multiple candidate executable intents determined from multiple candidate text representations of a speech input are described in U.S. Utility Patent Application No. 14 / 298,725, filed on June 6, 2014, entitled "System and Method for Inferring User Intent From Speech Inputs", the entire disclosure of which is incorporated herein by reference.

[0233] 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 "fulfill" 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 processes for obtaining additional information from the user and a task flow for performing actions associated with the executable intents.

[0234] As described above, to complete the structured query, the task flow processing module 736 needs to initiate an additional conversation with the user to obtain additional information and / or clarify potentially ambiguous utterances. When such an interaction is necessary, the task flow processing module 736 invokes the dialog flow processing module 734 to participate in the conversation with the user. In some examples, the dialog flow 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 via the I / O processing module 728. In some examples, the dialog flow processing module 734 presents the dialog output to the user via audible output and / or visual output and receives input from the user via an oral or physical (e.g., click) response. Continuing the above example, when the task flow processing module 736 invokes the dialog flow processing module 734 to determine the "number of people in the party" and "date" information for the structured query associated with the domain "restaurant reservation", the dialog flow processing module 734 generates questions such as "How many people per row?" and "Which day to book?" and passes them to the user. Once the answer from the user is received, the dialog flow processing module 734 fills the structured query with the missing information or passes the information to the task flow processing module 736 to complete the missing information according to the structured query.

[0235] 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. Thus, the task flow processing module 736 executes the steps and instructions in the task flow model according to the specific parameters included in the structured query. For example, the task flow model for the executable intent "restaurant reservation" includes steps and instructions for contacting the restaurant and actually requesting a reservation for a specific number of people at a specific time. For example, using the structured query such as: {restaurant reservation, restaurant = ABC Cafe, date = 3 / 12 / 2012, time = 7 pm, number of people in the party = 5}, the task flow processing module 736 can execute the following steps: (1) log in to the server of ABC Cafe or a restaurant reservation system such as and (2) enter the date, time, and number of people in the party information in the form on the website, (3) submit the form, and (4) form a calendar entry for the reservation in the user's calendar.

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

[0237] For example, if a restaurant has enabled an online reservation service, the restaurant submits a service model that specifies the necessary parameters for making a reservation and the API for transmitting the values of the necessary parameters to 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, number of people in the party) in a format according to the API of the online reservation service to the online reservation interface.

[0238] In some examples, the natural language processing module 732, the dialog flow processing module 734, and the task flow processing module 736 are used jointly and repeatedly to infer and define the user's intent, obtain information to further clarify and refine the user's intent, and finally generate a response (i.e., output to the user or complete a task) to meet the user's intent. The generated response is a dialog response to the voice input that at least partially meets the user's intent. Additionally, in some examples, the generated response is output as a voice output. In these examples, the generated response is sent to the speech synthesis processing module 740 (e.g., a speech synthesizer), where the generated response can be processed to synthesize the dialog response in voice form. In other examples, the generated response is data content related to fulfilling the user's request in the voice input.

[0239] In an example where the task flow processing module 736 receives multiple structured queries from the natural language processing module 732, the task flow processing module 736 first processes the first structured query of the received structured queries to attempt to complete the first structured query and / or execute 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 received structured queries based on a combination of the corresponding speech recognition confidence score and the corresponding intent confidence score. In some examples, if the task flow processing module 736 encounters an error during the processing of the first structured query (e.g., due to inability to determine necessary parameters), the task flow processing module 736 may continue to select and process a second structured query corresponding to a lower-ranked executable intent among the received structured queries. The second structured query is selected, for example, based on the speech recognition confidence score corresponding to the corresponding candidate text representation, the intent confidence score corresponding to the corresponding candidate executable intent, the missing necessary parameters in the first structured query, or any combination thereof.

[0240] The speech synthesis processing module 740 is configured to synthesize a speech output for presentation to the user. The speech synthesis processing module 740 synthesizes the speech output based on the text provided by the digital assistant. For example, the generated conversation 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 suitable speech synthesis technology to generate the speech output from the text, including but not limited to: concatenative synthesis, unit selection synthesis, diphone synthesis, domain-specific synthesis, formant synthesis, articulatory synthesis, Hidden Markov Model (HMM)-based synthesis, and sine wave synthesis. In some examples, the speech synthesis processing module 740 is configured to synthesize individual words based on the phoneme strings corresponding to those words. For example, the phoneme strings are associated with the words in the generated conversation response. The phoneme strings are stored in the metadata associated with the words. The speech synthesis processing module 740 is configured to directly process the phoneme strings in the metadata to synthesize the words in speech form.

[0241] 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., the 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 embodiments where the output of the digital assistant is generated at the server system. Also, since the server system generally has more processing power or more resources than the user device, it is possible to obtain a higher-quality speech output than would be achieved by client-side synthesis.

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

[0243] As described above, the ontology 760 can include any number of domains representing any number of executable intents. For example, in some examples, the ontology 760 includes a "phone" superdomain representing concepts related to phone functionality. The "phone" superdomain includes, for example, a plurality of executable intent nodes representing corresponding executable intents. The executable intents correspond, for example, to the respective functions of a phone application (e.g., implemented by the phone module 238).

[0244] In some examples, the "phone" superdomain includes a "make call" executable intent node representing the executable intent of making a phone call. The "make call" executable intent node is linked to an attribute node representing the {phone number} parameter. The "make call" executable intent node corresponds to the task of making a phone call to the phone number specified by the {phone number} parameter. In some examples, the "phone" superdomain also includes a "make emergency call" executable intent node representing the executable intent of making an emergency call. The "make emergency call" executable intent node corresponds to the task of connecting to a device having a call function and causing the device to make a phone call to the emergency number at the current location (e.g., "911" in the United States or "112" in the United Kingdom).

[0245] In some examples, the "phone" superdomain includes an "answer call" executable intent node representing the executable intent of answering an incoming call. The "answer call" executable intent node corresponds to the task of answering an incoming call.

[0246] In some examples, the "phone" superdomain includes an "end call" executable intent node representing the executable intent of ending a call. The "end call" executable intent node corresponds to the task of ending a call on the device (e.g., hanging up the phone).

[0247] In some examples, the "Phone" superdomain includes a "Transmit Dual-Tone Multi-Frequency (DTMF) Tone" executable intent node that represents an executable intent to transmit DTMF tones during a call. In some examples, the "Transmit DTMF Tone" executable intent node is linked to an attribute node that represents a {character key} parameter. The "Transmit DTMF Tone" executable intent node corresponds to the task of generating and transmitting DTMF tones corresponding to the character keys specified by the {character key} parameter during a call.

[0248] In some examples, the "Phone" superdomain includes an "Answer Call" executable intent node that represents an executable intent to answer an incoming call. The "Answer Call" executable intent node corresponds to the task of answering an incoming call.

[0249] In some examples, the "Phone" superdomain includes an "End Call" executable intent node that represents an executable intent to end a call. The "End Call" executable intent node corresponds to the task of ending a call on the device (e.g., hanging up the phone).

[0250] In some examples, the "Phone" superdomain includes a "Hold Call" executable intent node that represents an executable intent to hold a call. The "Hold Call" executable intent node corresponds to the task of holding a call.

[0251] In some examples, the "Phone" superdomain includes a "Transfer Call" executable intent node that represents an executable intent to transfer a call. In some examples, the "Transfer Call" executable intent node is linked to an attribute node that represents a {transfer phone number} parameter. The "Transfer Call" executable intent node corresponds to the task of transferring a call to a second device based on the phone number specified by the {transfer phone number} parameter.

[0252] In some examples, the "Phone" superdomain includes a "Conference Call" executable intent node that represents an executable intent to add a second phone to an existing call. In some examples, the "Conference Call" executable intent node is linked to an attribute node that represents a {conference phone number} parameter. The "Conference Call" executable intent node corresponds to the task of establishing a second call with a second device (e.g., by answering an incoming call or dialing the phone number specified by the {conference phone number} parameter) and merging the second call with the existing call to establish a three-way call.

[0253] In some examples, the "Phone" superdomain includes a "Play Voicemail" executable intent node that represents an executable intent to play the most recent voicemails. The "Play Voicemail" executable intent node corresponds to the task of obtaining and playing the N most recent voicemails (where N is a predefined positive integer).

[0254] In some examples, the "phone" superdomain includes an "unanswered call list" executable intent node that represents an executable intent to present a list of recently unanswered calls. The "unanswered call list" executable intent node corresponds to the task of obtaining and presenting call information for the N most recent unanswered calls (where N is a predefined positive integer).

[0255] Figures 8 to 11 Various techniques are shown for using voice interaction at a primary device to access call functionality of a companion device, according to various examples. It should be recognized that, in some examples, Figures 8 to 11 the various aspects described above can be combined in any manner.

[0256] Figure 8 Techniques are shown for using voice interaction at a primary device 802 to cause a companion device 804 to make a phone call, according to various examples. The primary device 802 is similar or identical to Figure 1 device 122. The companion device 804 is similar or identical to Figure 1 device 102. For example, the primary device 802 is a smart speaker device (e.g., without a display), and the companion device 804 is a smart phone device. Some aspects of the present technology are performed using a DA server 806, which is similar or identical to Figure 1 DA server 106. It should be recognized that, in other examples, any operations performed by the DA server 806 can alternatively be performed locally at the primary device 802 and / or the companion device 804. For example, the respective DA client modules (e.g., DA client module 229) of the primary device 802 and / or the companion device 804 can perform the operations of the DA server 806.

[0257] As shown by arrow 808, a wireless communication connection is first established between the primary device 802 and the companion device 804. For example, when the companion device 804 is positioned close to the primary device 802, the primary device 802 detects a wireless signal broadcast by the companion device 804, which initiates an exchange of authentication information between the primary device 802 and the companion device 804. Based on the exchanged authentication information, the primary device 802 determines whether the companion device is a registered device of the primary device. If the primary device 802 determines that the companion device 804 is a registered device, a wireless communication connection is established between the primary device 802 and the companion device 804. In some examples, the established wireless communication connection is a single-hop, point-to-point wireless communication channel between the primary device 802 and the companion device 804. For example, the wireless communication connection is established using the communication module (e.g., communication module 228) and the RF circuit (e.g., RF circuit 208) of the primary device 802.

[0258] In some examples, based on establishing a wireless communication connection, the companion device 804 provides information to the primary device 802, such as its device characteristics (e.g., device capabilities and functions) and operating status. For example, the companion device 804 provides information indicating that it is a smartphone with telephone capabilities and that it is not currently in a call. It should be appreciated that in some examples, the primary device 802 may be communicatively coupled to a number of devices, each having different device characteristics. For example, a wireless communication connection may be established between the primary device 802 and other devices such as a smart light switch, a media player, a smart thermostat, etc. In some examples, the primary device 802 is configured to control the functions of any one of the connected devices based on the received user utterance.

[0259] As shown by arrow 810, the primary device 802 receives a user utterance (e.g., "Hey Siri, call my mom"). For example, the user utterance is received at the I / O processing module (e.g., I / O processing module 728) via a microphone (e.g., microphone 213) of the primary device 802. In this example, the user utterance is received in conjunction with invoking a digital assistant on the primary device 802. For example, when it is determined that the first part of the user utterance contains a predefined voice trigger (e.g., "Hey Siri,..."), the digital assistant is invoked. Invoking the digital assistant causes the primary device 802 to obtain audio data (e.g., via the microphone of the primary device 802) containing the second part of the user utterance (e.g., "... call my mom"), and to automatically perform speech recognition (e.g., using the STT processing module 730) and natural language processing (e.g., using the natural language processing module 732) on the second part of the user utterance. In other examples, the user utterance is received when or after the digital assistant is invoked on the primary device 802. For example, the digital assistant is invoked in response to detecting a user input corresponding to a predefined type (e.g., a button press). In this example, invoking the digital assistant causes the primary device 802 to obtain audio data containing the user utterance and to automatically perform speech recognition and natural language processing on the user utterance.

[0260] Upon receiving the user utterance, the master device 802 sends a representation of the user utterance and context information to the DA server 806 (as shown by arrow 812). The context information indicates, for example, that a wireless communication connection is established between the master device 802 and the companion device 804, and the companion device 804 is a registered device of the master device 802. In some examples, the context information specifies the operating state of the companion device 804. The operating state of the companion device 804 includes, for example, whether the companion device 804 is currently in a call. In some examples, the context information specifies the type of device corresponding to the master device 802 and / or the companion device 804. For example, the context information specifies that the master device 802 is a smart speaker device (e.g., without an independent phone function) and / or the companion device 804 is a smart phone device (e.g., with an independent phone function).

[0261] Upon receiving the representation of the user utterance and the context information, the DA server 806 determines the user intent corresponding to the user utterance. Specifically, the DA server 806 performs automatic speech recognition processing on the user utterance (e.g., using the STT processing module 730) to determine the text representation of the user utterance. Then, the DA server 806 processes the text representation using the context information (e.g., using the natural language processing module 732) to determine the user intent. For example, given the text representation of the second part of the user utterance "call my mom", the DA server 806 determines that the "phone" superdomain is most relevant to the user utterance. Within the "phone" superdomain, the DA server 806 further determines that the "make a call" executable intent node is most relevant to the user utterance. Based on this determination, the DA server 806 determines that the user intent corresponding to the user utterance is to make a call. In some examples, the DA server 806 parses one or more parameters in the selected executable intent node. For example, the DA server 806 determines the value of the {phone number} parameter in the "make a call" executable intent node by searching the user's contact information and obtaining the phone number corresponding to the contact alias "mom" specified in the user utterance.

[0262] In some examples, the DA server 806 uses the context information to disambiguate between several possible user intents. For example, based on the context information indicating that the master device 802 is a smart speaker without a display, the DA server 806 may select the "make a call" executable intent node in the "phone" superdomain (instead of the "make a video call" executable intent node in the "video call" superdomain) because it is most relevant to the user utterance. Thus, even if the user utterance is "make a video call to my mom", the DA server 806 may determine that the "make a call" executable intent node in the "phone" superdomain is most relevant to the user utterance because it recognizes, based on the context information that the master device 802 is a smart speaker, that video calls cannot be supported.

[0263] Based on the user intent corresponding to the executable intent of making a call, the DA server 806 generates a command and sends the command to the master device 802 (represented by arrow 814). This command represents a task that satisfies the executable intent of making a call. In some examples, the command specifies a domain and parameters corresponding to the determined user intent. For example, the command specifies the "make a call" executable intent node of the "phone" superdomain and the resolved value of the {phone number} parameter. In some examples, the command does not specify the device on which to execute the command, which enables the DA server 806 to generally apply to multiple devices.

[0264] The master device 802 receives and analyzes the command from the DA server 806 (e.g., using the DA client module 229), and determines which device will execute the command based on a set of rules. For example, the master device 802 is communicatively coupled to a number of devices (including the companion device 804). Based on the command, the master device 802 determines whether the command is to be executed by itself or by one of the coupled devices. For example, based on the "make a call" executable intent node and the "phone" superdomain specified in the command, the master device 802 determines that the command will be executed by a device with a phone function.

[0265] Based on determining that the companion device 804 is a smart phone with a phone function, the master device 802 sends an instruction to the companion device 804 via an established wireless communication connection (e.g., using the DA client module 229) (as shown by arrow 816). This instruction causes the companion device 804 to execute the task that satisfies the user intent. In some examples, the instruction includes the same command received by the master device 802 from the DA service 806. In these examples, the command is forwarded to the companion device 804 for execution. For example, upon receiving a command specifying the "make a call" executable intent node of the "phone" superdomain and the resolved value of the {phone number} parameter, the companion device 804 executes the task of making a call to the phone number specified in the {phone number} parameter (e.g., using the task flow processing module 736 and the service processing module 738). Specifically, the companion device 804 initiates a phone call to the specified phone number using the phone application (e.g., implemented by the phone module 238), and attempts to establish a phone connection with an external device corresponding to the specified phone number (represented by arrow 822).

[0266] In some examples, when a command is executed or an attempt is made to execute a command, the companion device 804 generates an acknowledgement signal (represented by arrow 818) and sends it to the host device 802. The acknowledgement signal indicates, for example, the result of the companion device 804's attempt to execute the command. For example, the acknowledgement signal can provide an acknowledgement that a phone call has been successfully initiated. Or, if the execution of the command is unsuccessful, the acknowledgement signal can indicate the type of error that has occurred. For example, the acknowledgement signal can include an error code that indicates that a cellular communication signal could not be satisfactorily received to initiate a cellular call, or that the companion device 804 has participated in a phone call.

[0267] In an example of successfully executing a command to make a phone call, the companion device 804 provides (e.g., using the phone module 238 and the RF circuit 208) audio data of the called phone number to the host device 802 (as shown by arrow 820). The audio data is sent to the host device 802 via a previously established wireless communication channel and includes audio signals associated with making the phone call (e.g., dial tone, dual-tone multi-frequency signaling for dialing the phone number, ringing tone, etc.). The host device 802 receives the audio data and generates an audio output based on the received audio data (e.g., at the speaker of the host device 802). Additionally, when a phone connection is established, the audio data of the established call is exchanged between the companion device 804 and the host device 802 via the previously established wireless communication channel. For example, audio data representing the voice received at the microphone of the host device 802 is sent to the companion device 804, which transmits the audio data to the called party (e.g., via the cellular network). Similarly, audio data representing the voice data received from the called party at the companion device 804 is sent to the host device 802, which generates an audio output corresponding to the audio data.

[0268] In an example where the acknowledgement signal includes an error code, the host device 802 processes the error code in conjunction with the DA server 806 and provides a response to the user. For example, the host device 802 outputs a dialogue notifying the user of the type of error encountered. In some examples, the dialogue prompts the user whether to attempt to make the phone call again.

[0269] It should be understood that Figure 8The technology may include making other types of phone calls or video calls. Specifically, in some examples, voice interaction at the primary device 802 can be used to cause the companion device 804 to make an emergency call. For example, the user utterance received at the primary device 802 is "Hey Siri, call the police" or "Hey Siri, call 911". The representation of the user utterance and the associated context information are sent to the DA server 806. Based on the user utterance and the context information, the DA server 806 determines the user intent corresponding to the user utterance. For example, the DA server 806 determines that the "Make an emergency call" executable intent node in the "Phone" superdomain is the most relevant from the second part of the user utterance (e.g., "call the police" or "call 911"). Based on this determination, the DA server 806 determines that the user intent is to make an emergency call. Then, the DA server 806 sends a command to the primary device 802. The command represents one or more tasks corresponding to the "Make an emergency call" executable intent node. In some examples, based on this command, the primary device 802 provides a voice prompt requesting confirmation that the user wishes to make an emergency call. Upon receiving confirmation that the user wishes to make an emergency call, the primary device 802 continues to process the command. Specifically, the primary device 802 determines whether a companion device having an independent phone function (e.g., the companion device 804) is currently connected to the primary device 802. When it is determined that the companion device 804 having an independent phone function is connected to the primary device 802, the primary device 802 forwards the command to the companion device 804, which causes the companion device 804 to make an emergency call. Alternatively, if the primary device 802 determines that a companion device having an independent phone function is not currently connected to the primary device 802, the primary device 802 attempts to connect to any surrounding compatible devices having a phone function. For example, the primary device 802 broadcasts a signal that causes a compatible device to establish a wireless connection with the primary device 802 when received by the surrounding compatible device having an independent phone function. The compatible device does not need to be a registered device of the primary device 802. Upon successfully establishing a wireless connection with the compatible device, the primary device 802 sends an instruction to the compatible device to cause the device to make an emergency call.

[0270] Figure 9 Illustrates techniques for using voice interaction at a primary device 902 to cause a companion device 904 to answer an incoming call according to various examples. The primary device 902 and the companion device 904 are similar or identical to the primary device 802 and the companion device 804, respectively. A DA server 906 is used to perform some aspects of this technology, which is similar or identical to the DA server 806. In some examples, any of these aspects may alternatively be performed locally at the primary device 902 and / or the companion device 904.

[0271] As shown by arrow 908, first a wireless communication connection is established between the primary device 902 and the companion device 904. In a manner similar to that described above in Figure 8Establish a wireless communication connection in a similar manner as described. In some examples, when establishing the wireless communication connection, the companion device 904 (via the established connection) provides information to the primary device 902, such as its device characteristics (e.g., device capabilities and functions) and operating status.

[0272] As shown by arrow 910, an incoming call is detected at the companion device 904 (e.g., using the telephone module 238 and the RF circuit 208). In some examples, the incoming call is a voice call received at the companion device 904 via a telephone network (e.g., a landline or a cellular network). In some examples, the incoming call is a video call. In some examples, a telecommunications application software operating on the companion device 904 (e.g., or ) is used to detect the incoming call.

[0273] Based on the detected incoming call, the companion device 904 sends a signal (represented by arrow 910) to the primary device 902. This signal indicates that an incoming call has been detected at the companion device 904. The signal may also include other context information about the companion device 904. In some examples, when the incoming call is detected, the companion device 904 outputs an indication of the incoming call. This output is used to alert the user of the incoming call. The output includes, for example, audio, visual, and / or tactile outputs. In some examples, the primary device 902 does not output an audio indication of the incoming call in response to receiving the signal from the companion device 904. In other examples, in response to receiving the signal, the primary device 902 presents audio, visual, and / or tactile outputs to alert the user of the incoming call.

[0274] In some examples, the signal (represented by arrow 910) received by the primary device 902 from the companion device 904 includes information about the caller. This information includes, for example, caller identification (ID) information. In some examples, the information includes the caller's contact alias listed in the contacts stored on the companion device 904. In some examples, the information about the caller is automatically provided via the signal according to the activation settings (e.g., accessibility settings) on the companion device 904. In response to receiving the signal, the primary device 902 outputs (e.g., via the speaker) a voice dialogue containing the information about the caller. For example, if the caller corresponds to the contact alias "Mom", the primary device 902 outputs a voice dialogue announcing "Mom is calling".

[0275] As shown by arrow 912, a user utterance (e.g., "Hey Siri, answer the call") is received at the main device 902 (e.g., via microphone 213 using I / O processing module 728). In some examples, receiving the user utterance is combined with invoking a digital assistant on the main device 902. For example, when it is determined that the first part of the user utterance contains a predefined voice trigger (e.g., "Hey Siri,..."), the digital assistant is invoked. Invoking the digital assistant causes the main device 902 to obtain audio data containing the second part of the user utterance (e.g., "... answer the call") and automatically perform speech recognition and natural language processing on the second part of the user utterance. In other examples, the user utterance can be received when or after the digital assistant is invoked on the main device 902 (e.g., when a button is pressed to invoke the digital assistant).

[0276] Upon receiving the user utterance, the main device 902 sends a representation of the user utterance and associated context information (represented by arrow 914) to the DA server 906. The context information includes, for example, information similar to that described in the examples above in Figure 8 . In some examples, the context information includes the information represented in the received signal. For example, the context information indicates that an incoming call is detected at the companion device 904.

[0277] Based on the received representation of the user utterance and the associated context information, the DA server 906 automatically determines the user intent corresponding to the user utterance (e.g., by performing automatic speech recognition and natural language processing). For example, based on the context information and the text representation "answer the call" of the second part of the user utterance, the DA server 906 determines that the "phone" superdomain is most relevant to the user utterance. Within the "phone" superdomain, the DA server 906 further determines that the "answer call" executable intent node is most relevant to the user utterance. Based on this determination, the DA server 906 determines that the user intent corresponding to the user utterance is to answer the call.

[0278] In some examples, the DA server 906 uses the context information to disambiguate between several possible user intents. For example, based on the context information indicating that an incoming call is currently detected at the companion device 904, the DA server 906 can select the "answer call" executable intent node in the "phone" superdomain (instead of the "reply email" executable intent node in the "email" superdomain) because it is most relevant to the user utterance. As another example, based on the context information indicating that an incoming call is currently detected at the main device 902, the DA server 906 can select the "answer call" executable intent node in the "phone" superdomain (instead of the "answer call" executable intent node in the "video call" superdomain) because it is most relevant to the user utterance.

[0279] Based on the user intent corresponding to the executable intent for answering an incoming call, the DA server 906 performs one or more tasks corresponding to the executable intent. The one or more tasks include, for example, generating a command and sending the command to the primary device 902 (represented by arrow 916). The command represents a task that satisfies the executable intent for answering an incoming call. In some examples, the command specifies the domain of the user intent. For example, the command specifies the "Answer Call" executable intent node of the "Phone" superdomain.

[0280] In some examples, the DA server 906 generates and sends a command after verifying that the context information indicates that the companion device 904 has detected an incoming call. If the context information does not indicate that the companion device 904 (or any other associated device) has detected an incoming call, the DA server 906 returns an error indication to the primary device 902. For example, the error indication causes the DA server 906 to output a dialogue notifying the user that there is no incoming call to answer at this time. In some examples, the error indication causes the DA server 906 to output a prompt asking the user if they want to make a call.

[0281] The primary device 902 analyzes the command from the DA server 906 and determines which of the multiple potentially connectable devices will execute the command based on a set of rules. For example, by applying the set of rules, the primary device 902 determines that the command will be executed by the companion device 904 because the "Answer Call" executable intent node is part of the "Phone" superdomain and the companion device 904 has a phone function. Additionally, in some examples, the primary device 902 determines which device will execute the command based on the operational states of the multiple potentially connectable devices. For example, based on a signal indicating that the companion device 904 has detected an incoming call, the primary device 902 determines that the operational state of the companion device 904 is most relevant to the "Answer Call" executable intent node and thus determines that the companion device 904 will execute the command.

[0282] Based on the determination that the companion device 904 will execute the command, the primary device 902 sends an instruction to the companion device 904 via the established wireless communication connection (as shown by arrow 916). The instruction causes the companion device 904 to perform the task corresponding to the user intent of answering the call. In some examples, the instruction includes the same command received by the primary device 902 from the DA service 906. In these examples, the primary device 902 forwards the command to the companion device 904 for execution.

[0283] When receiving a command for the "Answer Call" executable intent node that specifies the "Phone" super domain, the companion device 904 performs the corresponding task of answering an incoming call and establishing a phone connection with the external device of the calling party. In some examples, the corresponding task includes providing audio data of the answered incoming call to the electronic device. For example, audio data for the answered call is exchanged between the main device 902 and the companion device 904 (represented by arrow 918). In some examples, the corresponding task includes providing audio data of the answered incoming call to the electronic device.

[0284] When executing or attempting to execute a command, the companion device 904 generates an acknowledgment signal (represented by arrow 922) and sends it to the main device 902. In some examples, upon receiving the acknowledgment signal, the main device 902 sends a representation of the acknowledgment signal (represented by arrow 920) to the DA server 906. The acknowledgment signal indicates the result of the companion device 904's attempt to execute the command. For example, the acknowledgment signal provides confirmation of successfully answering the incoming call and establishing a phone connection between the companion device 904 and the calling party's device. In some examples, upon receiving an acknowledgment signal indicating that the incoming call has been successfully answered, the main device 902 outputs an indication (e.g., audio, video, and / or tactile) notifying the user that the call has been successfully answered.

[0285] In an example of successfully executing the command to answer an incoming call, the companion device 904 provides audio data of the answered incoming call to the main device 902 (represented by arrow 918). The audio data is sent to the main device 902 via a previously established wireless communication channel and includes a representation of the audio signal sent from the calling party. The main device 902 receives the audio data (e.g., using the RF circuit 208) and generates an audio output based on the received audio data (e.g., using the audio circuit 210 and the speaker 211). Additionally, audio data representing the speech received at the microphone of the main device 902 is sent to the companion device 904, which transmits the audio data to the called party (e.g., via a cellular network). In some examples, the companion device 904 does not generate an audio output corresponding to the audio data but relies on the main device 902 to generate the audio output.

[0286] In some examples, the execution of the command is unsuccessful. In these examples, the confirmation signal indicates the type of error associated with the unsuccessful command execution. For example, the confirmation signal includes a first error code that indicates that the incoming call hung up before the companion device 904 executed the command and the incoming call includes caller identification information. As another example, the confirmation signal includes a second error code that indicates that the incoming call hung up before the companion device 904 executed the command and the incoming call does not include caller identification information. When receiving a confirmation signal with an error code, the master device 902 processes the error code in conjunction with the DA server 906 and provides a corresponding response to the user (e.g., using the task flow processing module 736, the dialogue flow processing module 734, and the speech synthesis processing module 740). For example, the master device 902 sends the error code to the DA server 906 (e.g., as indicated by arrow 920). Based on the error code, the DA server 906 provides a corresponding dialogue response to the master device 902 (as indicated by arrow 924). For example, according to the first error code indicating that the incoming call hung up before the companion device 904 executed the command and the incoming call includes caller identification information, the DA server 906 sends a dialogue response to the master device 902 notifying the user of the error and prompting the user to call back based on the caller identification information (e.g., "Sorry, you missed your mom's call. Do you want to call her back?").

[0287] As another example, according to the second error code indicating that the incoming call hung up before the companion device 904 executed the command and the incoming call does not include caller identification information, the DA server 906 sends a dialogue response to the master device 902 notifying the user of the error without prompting the user to call back (e.g., "Sorry, you missed a call.").

[0288] When receiving the dialogue response from the DA server 906, the master device 902 outputs the dialogue response in voice form (e.g., via the speaker of the master device 902). In an example where the dialogue response prompts the user to call back based on the caller identification information, the master device 902 automatically detects the voice response from the user and enables the DA server 906 to determine the corresponding user intent of the voice response. According to the DA server 906 determining that the user intent of the voice response corresponds to the executable intent of making a call using the caller identification information, the DA server 906 sends a command to the master device 902 to cause the companion device 904 to initiate a call using the caller identification information.

[0289] Figure 10Illustrated are techniques for using voice interaction at a primary device 1002 to cause an accessory device 1004 to perform call-related tasks while the accessory device 1004 is in a call. The primary device 1002 and the accessory device 1004 are similar or identical to the primary device 802 and the accessory device 804, respectively. A DA server 1006 is used to perform some aspects of the techniques, which is similar or identical to the DA server 806. In some examples, any of these aspects may alternatively be performed locally at the primary device 1002 and / or the accessory device 1004.

[0290] In Figure 10 this example of Figure 8 the accessory device 1004 is in a call. For example, a voice call or a video call connection is established between the accessory device 1004 and an external device (e.g., via a telephone, cellular, or Internet network). In some examples, the call is established when the primary device 1002 successfully causes the accessory device 1004 to make a call (e.g., as described in Figure 9 ). Alternatively, the call is established, for example, when the primary device 1002 successfully causes the accessory device 1004 to answer an incoming call (e.g., as described in

[0291] As shown by arrow 1008, audio data associated with the call is exchanged between the accessory device 1004 and the primary device 1002. For example, the audio data is exchanged via a previously established wireless communication connection between the primary device 1002 and the accessory device 1004. The wireless communication connection is established in a similar manner as described above in Figure 8 . In some examples, the primary device 1002 sends audio data representing an audio signal received at the microphone of the primary device 1002 during the call to the accessory device 1004. Then, the accessory device 1004 sends the audio data from the primary device 1002 to the external device via the call connection. Similarly, the accessory device 1004 receives audio data from the external device via the call connection and provides the audio data to the primary device 1002. The primary device 1002 outputs audio corresponding to the received audio data (e.g., at the speaker of the primary device 1002). The received audio data represents an audio signal received at the microphone of the external device during the call.

[0292] As shown by arrow 1010, the primary device 1002 receives user speech during the call (e.g., via the microphone of the primary device 1002). For example, the user speech is received when the primary device 1002 outputs audio according to the received audio data associated with the call. The user speech may be natural language speech representing one of a plurality of call-related tasks that the user desires the primary device 1002 to perform with the accessory device 1004. For example, the user speech includes one of the following utterances:

[0293] "Hey Siri, hang up the call."

[0294] "Hey Siri, enter 3."

[0295] "Hey Siri, pause the call."

[0296] "Hey Siri, transfer the call to my sister."

[0297] "Hey Siri, connect to a call."

[0298] "Hey Siri, answer the call."

[0299] In some examples, the host device 1002 receives a signal containing context information before or in conjunction with receiving a user utterance. As shown by arrow 1020, the signal is received from the companion device 1004. In some examples, the signal is received from a different companion device communicatively coupled to the host device 1002. The context information includes, for example, the operating state of the companion device 1004 related to the received user utterance. For example, the signal indicates that the companion device 1004 is currently in a call. In some examples, the signal further indicates that the companion device 1004 has detected an incoming call separate from the current call. In some examples, the signal indicates that a companion device other than the companion device 1004 has detected an incoming call while the companion device 1004 is currently in a call. In some examples, based on the received signal, the host device 1002 outputs a voice dialogue notifying of the separate incoming call. For example, the voice dialogue can state: "You have another incoming call from John on the same line" or "You have an incoming call from Bob's phone". In some examples, although the voice dialogue is output from the speaker of the host device 1002, the audio data corresponding to the voice dialogue is not sent to the companion device 1004. For example, the host device 1002 performs signal cancellation on the audio input received at the microphone of the host device 1002 to cancel the portion of the audio input corresponding to the output voice dialogue. In this way, the remote party of the call will not hear the voice dialogue notifying of the separate incoming call.

[0300] In some examples, the user utterance is received in conjunction with invoking a digital assistant on the host device 1002. For example, in a manner similar to that described above in Figure 8 and Figure 9Call the digital assistant in a similar manner as described in . Depending on the manner of calling the digital assistant, the audio data corresponding to the user's utterance may or may not be sent from the main device 1002 to the companion device 1004. In some examples, if the digital assistant is called in response to detecting a user input corresponding to a first predetermined type (e.g., detecting that the first part of the user's utterance contains a predefined voice trigger such as "Hey Siri"), the main device 1002 includes a representation of the user's utterance in the audio data sent to the companion device 1004. Thus, the far-end party of the call will hear the user's utterance. Alternatively, if the digital assistant is called in response to detecting a user input corresponding to a second predetermined type (e.g., button push), the main device 1002 does not include a representation of the user's utterance in the audio data sent to the companion device 1004. For example, the main device 1002 cancels a portion of the audio data corresponding to the user's utterance. Thus, the far-end party of the call will not hear the user's utterance. This may be desirable when the user's utterance represents a request for confidentiality. For example, if the user is currently on a call with the user's mother, the user may want to find out the user's mother's birthday without the user's mother knowing. In this case, the user can privately call the digital assistant (e.g., the second predetermined type) to provide the user's utterance "When is my mother's birthday?" Additionally, for such private digital assistant requests, any voice dialogue response provided by the digital assistant will also be removed from the audio data sent to the companion device 1004. Thus, the far-end party will not hear the voice dialogue response provided by the digital assistant.

[0301] In some examples, the digital assistant implemented on the main device 1002 can be called by the utterance represented in the audio data received from the far-end party of the call. For example, the utterance from the far-end party can be "Hey Siri, find us a good Japanese restaurant". In these examples, the main device 1002 analyzes the audio data of the call received from the companion device 1004 and determines (e.g., using speaker recognition technology) whether the utterance represented in the audio data corresponds to a predefined voice trigger. If the main device 1002 determines that the first part of the utterance contains a predefined voice trigger (e.g., Hey Siri,...), the main device 1002 calls the digital assistant and automatically causes the second part of the utterance (e.g., "... find us a good Japanese restaurant") to be subjected to speech recognition and natural language processing (e.g., at the DA server 1006). The utterance from the far-end party is processed in a similar manner as the user's utterance received at the microphone of the main device 1002. Additionally, the voice dialogue response provided by the digital assistant in response to the user's utterance from the far-end party is sent to the far-end party via the companion device 1004. Thus, the far-end party will hear the voice dialogue response.

[0302] Upon receiving a user utterance (represented by arrow 1010), the master device 1002 sends a representation of the user utterance and associated context information to the DA server 1006 (represented by arrow 1012). The context information includes, for example, information described in the above examples similar to Figure 8 and Figure 9 . The context information is based on one or more signals received from the companion device 1004 and / or a different companion device. In some examples, the context information indicates that the companion device 1004 is participating in a call. In some examples, in relevant cases, the context information also indicates a separate incoming call detected at the companion device 1004 or at another companion device communicatively coupled to the master device 1002.

[0303] Based on the received representation of the user utterance and the associated context information, the DA server 1006 automatically determines the user intent corresponding to the user utterance (e.g., by performing automatic speech recognition and natural language processing). As described in the example of Figures 7A to 7C , determining the user intent includes determining the domain (or superdomain) most relevant to the user utterance.

[0304] In some examples, the DA server 1006 allows processing of user intents unrelated to the current call. In other examples, the DA server 1006 restricts the processing of user intents unrelated to the current call. Such a restriction may be needed to reduce interruptions to the call caused by unintentional invocations of the digital assistant. For example, based on the context information indicating that the companion device 1004 is in a call, the DA server 1006 determines whether the domain determined to be most relevant to the user utterance corresponds to the "phone" or "video call" superdomain (for controlling call functions). If the DA server 1006 determines that the domain most relevant to the user utterance is the "phone" or "video call" superdomain, the DA server 1006 continues to complete the natural language processing of the user utterance and performs one or more tasks that satisfy the user intent corresponding to the user utterance. Alternatively, if the DA server 1006 determines that the domain most relevant to the user utterance is a domain other than the "phone" superdomain, the DA server 1006 abandons performing one or more tasks that satisfy the user intent.

[0305] The determination of the user intention for each of the above exemplary user utterances is now described in more detail. For the user utterance "Hey Siri, hang up the call", the DA server 1006 determines that the "End Call" executable intent node in the "Phone" superdomain is most relevant to the user utterance based on the part "hang up the call" and the context information. For the user utterance "Hey Siri, enter 3", the DA server 1006 determines that the "Transmit DTMF Tone" executable intent node in the "Phone" superdomain is most relevant to the user utterance based on the part "enter 3" and the context information. For the user utterance "Hey Siri, pause the call", the DA server 1006 determines that the "Hold Call" executable intent node in the "Phone" superdomain is most relevant to the user utterance based on the part "pause the call" and the context information. For the user utterance "Hey Siri, transfer the call to my sister", the DA server 1006 determines that the "Transfer Call" executable intent node in the "Phone" superdomain is most relevant to the user utterance based on the part "transfer the call to my sister" and the context information. For the user utterance "Hey Siri, make a call", the DA server 1006 determines that the "Make a Call" executable intent node in the "Phone" superdomain is most relevant to the user utterance based on the part "make a call" and the context information. For the user utterance "Hey Siri, answer the call", the DA server 1006 determines that the "Answer Call" executable intent node in the "Phone" superdomain is most relevant to the user utterance based on the part "answer the call".

[0306] In some examples, the DA server 1006 uses context information to disambiguate between multiple executable intent nodes that may be determined to be highly relevant to the user utterance. For example, the isolated utterances "hang up the call" or "pause the call" may be ambiguous with respect to whether the user wishes to hang up a voice call (e.g., for cellular voice service) or a video call (e.g., for a telecommunications application). If the context information indicates that the companion device 1004 is currently engaged in a voice call rather than a video call, the DA server 1006 will select the "Phone" superdomain (rather than the "Video Call" domain) as it is most relevant to the user utterance.

[0307] In some examples, the DA server 1006 parses one or more parameters in the selected executable intent node. Information obtained from the user utterance and the context information is used to parse the one or more parameters. For example, based on the part "3" in the user utterance "Hey Siri, enter 3", the DA server 1006 determines that the value of the {character key} parameter in the "Transmit DTMF Tone" executable intent node is "3".

[0308] Based on the determined user intent, the DA server 1006 performs one or more tasks that satisfy the user intent (e.g., according to a corresponding task flow). The one or more tasks include, for example, generating a command and sending the command to the primary device 1002 (represented by arrow 1014). The command represents the one or more tasks that satisfy the user intent. In some examples, the command specifies a domain or an executable intent node corresponding to the user intent. When receiving the command from the DA server 1006, the primary device 1002 analyzes the command and determines, based on a set of rules, which device among a plurality of possible devices will execute the command. The determination is based on the domain or the executable intent node specified in the command. Additionally, in some examples, the determination is based on the capabilities of each possible device. In some examples, the primary device 1002 determines that the command will be executed by itself and thus proceeds to execute the command. In other examples, the primary device 1002 determines that a companion device (e.g., companion device 1004) will execute the command. In these examples, the primary device 1002 sends an instruction to the companion device (as shown by arrow 1016). When the companion device receives the instruction, the instruction causes the companion device to automatically perform one or more tasks that satisfy the user intent (e.g., without further input from the user). In some examples, the instruction includes the same command received from the DA server 1006.

[0309] The command and the resulting execution tasks for each of the above exemplary user utterances are now described in more detail. For the user utterance "Hey Siri, hang up the call", the command received at the primary device 1002 from the DA server 1006 specifies the "End Call" executable intent node of the "Phone" super domain. Based on a set of rules and the "End Call" executable intent node, the primary device 1002 determines that the command will be executed by the primary device 1002. In accordance with this determination, the primary device 1002 executes the command by performing one or more tasks corresponding to the "End Call" executable intent node. For example, the primary device 1002 stops acquiring audio data (e.g., via its microphone) and outputs audio associated with the call (e.g., via its speaker). In some examples, the primary device 1002 terminates communication with the companion device 1004 associated with the call, which causes the companion device 1004 to terminate the call with the remote party. In some examples, executing the command includes sending a signal to the companion device 1004 (e.g., via a previously established wireless communication connection) that causes the companion device 1004 to end the call. The signal is different from the command received from the DA server 1006. For example, the signal can be a lower level signal that does not specify the "End Call" executable intent node of the "Phone" super domain. It may be desirable to execute the command at the primary device 1002 rather than the companion device 1004 because this can result in a faster response from the user's perspective. Additionally, the primary device 1002 is released more quickly to handle subsequent calls with the companion device 1004 or a different companion device.

[0310] In the exemplary user utterance “Hey Siri, enter 3”, the command received at the primary device 1002 from the DA server 1006 specifies an executable intent node of “Transmit DTMF tones” in, for example, the “Phone” superdomain. The command also specifies a value “3” for the associated {character key} parameter. The primary device 1002 then determines, based on a set of rules, the “Transmit DTMF tones” executable intent node, and the phone capabilities of the companion device 1004, that the command is to be executed by the companion device 1004. Based on this determination, the primary device 1002 forwards the command received from the DA server 1006 to the companion device 1004. In response to receiving the command, the companion device 1004 executes one or more tasks corresponding to the “Transmit DTMF tones” executable intent node. Specifically, the companion device 1004 generates a DTMF tone for the character key “3” and transmits the tone of the call to the remote party.

[0311] In the exemplary user utterance “Hey Siri, pause the call”, the command received at the primary device 1002 from the DA server 1006 specifies an executable intent node of “Hold call” in, for example, the “Phone” superdomain. Based on a set of rules, the “Hold call” executable intent node, and context information indicating that the companion device 1004 is currently in a call, the primary device 1002 determines that the command is to be executed by the companion device 1004. Based on this determination, the primary device 1002 forwards the command received from the DA server 1006 to the companion device 1004. In response to receiving the command, the companion device 1004 executes one or more tasks corresponding to the “Hold call” executable intent node. Specifically, the companion device 1004 pauses the call.

[0312] In the exemplary user utterance “Hey Siri, transfer the call to my sister”, the command received at the primary device 1002 from the DA server 1006 specifies an executable intent node of “Transfer call” in the “Phone” superdomain. The command also specifies a parameter value for the associated {transfer phone number} parameter of the “Transfer call” executable intent node. For example, the parameter value specifies the phone number of the call to be transferred (e.g., the phone number corresponding to “sister”). Based on a set of rules, the “Transfer call” executable intent node, and context information indicating that the companion device 1004 is currently in a call, the primary device 1002 determines that the command is to be executed by the companion device 1004. Based on this determination, the primary device 1002 forwards the command received from the DA server 1006 to the companion device 1004. In response to receiving the command, the companion device 1004 executes one or more tasks corresponding to the “Transfer call” executable intent node. Specifically, the companion device 1004 dials a call to the party corresponding to the phone number specified in the {transfer phone number} parameter (e.g., “sister”) and transfers the current call to that party.

[0313] In the exemplary user utterance "Hey Siri, answer call", the command received at the primary device 1002 from the DA server 1006 specifies the "answer call" executable intent node of the "phone" superdomain. Based on a set of rules, the "answer call" executable intent node, and context information indicating that a second incoming call is detected at the companion device 1004 while a call is in progress, the primary device 1002 determines that the command will be executed by the companion device 1004. In accordance with this determination, the primary device 1002 forwards the command received from the DA server 1006 to the companion device 1004. In response to receiving the command, the companion device 1004 performs one or more tasks corresponding to the "answer call" executable intent node. For example, the companion device 1004 pauses the call, answers the second incoming call, and then merges the two calls to establish a three-way call.

[0314] It should be appreciated that in some examples, a three-way call can alternatively be established by calling another party and then merging that other party into the call. For example, the user utterance received at the primary device 1002 can be "Hey Siri, add Susan to the call". The DA server 1006 determines that the "answer call" executable intent node is most relevant to the user utterance. In addition to specifying the "answer call" executable intent node, the command received at the primary device 1002 from the DA server 1006 specifies the phone number associated with the contact alias "Susan". Upon receiving the command from the primary device 1002, the companion device 1004 pauses the current call, establishes a second call by dialing Susan's phone number, and then merges the two calls to establish a three-way call.

[0315] In the exemplary user utterance "Hey Siri, answer call", the command received at the primary device 1002 from the DA server 1006 specifies the "answer call" executable intent node of the "phone" superdomain. Based on the context information, the primary device 1002 determines which companion device 1004 will execute the command. For example, if the context information indicates that a second incoming call is detected at the companion device 1004 while a call is in progress at the companion device 1004, the primary device 1002 determines that the companion device 1004 will execute the command and forwards the command to the companion device 1004. Then, the companion device 1004 answers the second incoming call to establish a second call. Additionally, the companion device 1004 ends the initial call or pauses the call. Then, the audio data associated with the second call is sent to the primary device 1002 for output.

[0316] In other examples, the context information indicates that a second incoming call was detected at a second companion device while companion device 1004 was on a call. In these examples, the main device 1002 determines that the second companion device is to execute a command specifying an "answer call" executable intent node and forwards the command to the second companion device. In response to receiving the command, the second companion device answers the second incoming call to establish a telephone connection with the caller. In addition, the main device 1002 disconnects from the initial call on companion device 1004. Specifically, the main device 1002 transmits the operation of the initial call back to the companion device 1004, and stops obtaining audio input (e.g., via its microphone) or receiving audio data associated with the initial call (e.g., from the companion device 1004).

[0317] When executing the command, the companion device 1004 (or another companion device) sends a confirmation signal (indicated by arrow 1018) to the main device 1002. This confirmation signal is similar to the one described above in Figure 8 and Figure 9 For example, the confirmation signal indicates whether the command was successfully executed. Figure 8 and Figure 9 As described in, the master device 1002 can provide an indicator as to whether the command was successfully executed based on the confirmation signal.

[0318] Figure 11 Techniques for using voice interaction at a primary device 1102 to cause a companion device 1104 to provide call-related information are shown according to various examples. The primary device 1002 and the companion device 1004 are similar or identical to the primary device 802 and the companion device 804, respectively. Some aspects of the present technology are performed using a DA server 1106, which is similar or identical to the DA server 806. In some examples, any of these aspects may alternatively be performed locally at the primary device 1102 and / or the companion device 1104.

[0319] As shown by arrow 1108, a wireless communication connection is first established between the main device 1102 and the supporting device 1104. Figure 8A wireless communication connection is established in a similar manner as described in . The main device 1102 receives the user speech (as shown by arrow 1110). In this example, the user speech can represent a request for information stored on the companion device 1104. In some examples, the requested information is call-related information. For example, the speech is "Hey Siri, play my voicemail" or "Hey Siri, tell me what missed calls I have." In some examples, the user speech is received on the main device 1102 in conjunction with or when invoking the digital assistant. Invoking the digital assistant causes the main device 1102 to obtain audio data (e.g., via a microphone) containing at least a portion of the user speech, and automatically performs speech recognition and natural language processing on a second portion of the user speech.

[0320] Upon receiving the user utterance, the master device 1102 sends a representation of the user utterance and associated context information to the DA server 1106 (as indicated by arrow 1112). The context information includes, for example, Figures 8 to 10 In some examples, the context information includes information indicated in a signal received from the companion device 1104 (similar to Figures 8 to 10 )

[0321] Based on the received representation of the user utterance and the associated context information, the DA server 1106 automatically determines the user intent corresponding to the user utterance (e.g., by performing automatic speech recognition and natural language processing). In some examples, the determined user intent involves obtaining and presenting call-related information. For example, based on the context information and the text representation of the user utterance "...play my voicemail", the DA server 1106 determines that the "play voicemail" executable intent node of the "phone" superdomain is most relevant to the user utterance. Based on this determination, the DA server 1106 determines that the user intent corresponding to the user utterance is to play the most recent voicemail. For another example, based on the context information and the text representation of the user utterance "...tell me what missed calls I have", the DA server 1106 determines that the "missed call list" executable intent node of the "phone" superdomain is most relevant to the user utterance. Based on this determination, the DA server 1106 determines that the user intent corresponding to the user utterance is to present a list of recent missed calls.

[0322] Based on the determined user intent, the DA server 1106 generates a command and sends the command to the primary device 1102 (represented by arrow 1114). The command represents a task that satisfies the user intent. In some examples, the command specifies the domain of the user intent or an executable intent node. Additionally, in some examples, the command includes values of one or more parameters associated with the domain or the executable intent node. When receiving the command from the DA server 1106, the primary device 1102 analyzes the command and determines which device among a plurality of possible devices will execute the command. This determination is based on, for example, a set of rules, the executable intent node specified in the command, and context information. In the exemplary utterance “… play my voicemail”, the command specifies the “play voicemail” executable intent node. Based on a set of rules, the “play voicemail” executable intent node, and context information indicating that the companion device 1104 has telephone capabilities (including voicemail), the primary device 1102 determines that the command will be executed by the companion device 1104. Similarly, in the exemplary utterance “… tell me what my missed calls are”, the DA server 1106 determines based on a set of rules, the “missed call list” executable intent node, and context information indicating that the companion device 1104 has telephone capabilities (including recent call history), and the primary device 1102 determines that the command will be executed by the companion device 1104.

[0323] Based on determining that the command will be executed by the companion device 1104, the primary device 1102 sends an instruction to the companion device 1104 (represented by arrow 1116). The instruction causes the companion device 1104 to automatically perform one or more tasks that satisfy the user intent (e.g., without further input from the user). In some examples, the instruction includes the same command received from the DA server 1106. For example, the primary device 1102 forwards the command from the DA server to the companion device 1104 (represented by arrow 1116).

[0324] In response to receiving the command, the companion device 1104 performs one or more tasks corresponding to the user's intent. For example, if the user intent involves obtaining and presenting call-related information, the companion device 1104 retrieves the call-related information and sends the call-related information to the primary device 1102 for presentation (represented by arrow 1118). Specifically, in response to the exemplary utterance “… play my voicemails”, the companion device 1104 performs one or more tasks corresponding to the “play voicemail” executable intent node. The one or more tasks include, for example, identifying N most recent voicemail audio files stored on the companion device 1104 (where N is a predefined positive integer), and sending the voicemail audio files to the primary device 1102 for presentation. Each voicemail audio file includes call information of the voicemail (e.g., phone number, time, contact alias, etc.) and an audio recording. Similarly, for the exemplary utterance “… tell me what my missed calls are”, the companion device 1104 performs one or more tasks corresponding to the “missed call list” executable intent node. The one or more tasks include, for example, obtaining call information (e.g., phone number, time, contact alias, etc.) of N most recent missed calls stored on the companion device 1104 (where N is a predefined positive integer) and sending the call information to the primary device 1102 for presentation.

[0325] Upon receiving the call-related information from the companion device 1104, the primary device 1102 sends a representation of the information to the DA server 1106 (represented by arrow 1120), which constructs a voice conversation related to the call-related information (e.g., using the dialog flow processing module 734). The voice conversation is then sent to the primary device 1102 (represented by arrow 1122), where the voice conversation is output through the speaker of the primary device 1102.

[0326] By way of example, continuing with the exemplary utterance “… play my voicemails”, the primary device 1102 sends the caller information of the N most recent voicemail audio files to the DA server 1106. Then, the DA server 1106 constructs a voice conversation with the caller information, e.g., “Now playing your three most recent voicemail messages. The first was received from John Adams at 2:43 PM on May 8, 2018 …”, and the primary device 1102 plays the voice conversation received from the DA server 1106 and combines the playback of the voicemail audio files into the voice conversation.

[0327] Similarly, in the exemplary utterance “… tell me what my missed calls are”, the master device 1102 sends the caller information of the N most recent missed calls to the DA server 1106. The DA server 1106 then constructs a voice dialogue with the caller information, such as “You have three missed calls. The first one was from Susan White at 12:15 PM on May 2, 2018 …”, and then the master device 1102 plays the voice dialogue received from the DA server 1106. In some examples, the voice dialogue includes a prompt to call back any of the missed calls.

[0328] Although not shown in Figure 11 it should be appreciated that the companion device 1104 can send a confirmation signal similar to that described in Figures 8 to 10 to the master device 1102 to indicate whether the command has been successfully executed.

[0329] 4. Process of Accessing Call Function Using Voice Interaction

[0330] Figures 12A to 12B Process 1200 for accessing the call function of a companion device using voice interaction according to various examples is shown. For example, process 1200 is performed using one or more electronic devices implementing a digital assistant. In some examples, process 1200 is performed using a client-server system (e.g., system 100), and the blocks of process 1200 are divided in any way between the server (e.g., DA server 106) and one or more client devices (e.g., user devices 104 and 122). Thus, although parts of process 1200 are described herein as being performed by specific devices of a client-server system, it should be understood that process 1200 is not limited thereto. In other examples, process 1200 is performed using only a client device (e.g., user device 122) or multiple client devices (e.g., user devices 104 and 122). In process 1200, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in conjunction with process 1200.

[0331] Process 1200 can be implemented to enable a companion device to answer an incoming call based on a voice interaction at a primary device. As described in more detail below, process 1200 includes, for example, receiving a signal indicating an incoming call at the companion device. Based on the received user utterance and context information, process 1200 causes the server to determine a user intent corresponding to the user utterance. The context information is based on the received signal from the companion device. In accordance with the user intent corresponding to an executable intent to answer the incoming call, process 1200 performs a number of operations, including receiving, from the server, a command representing a task that satisfies the executable intent to answer the incoming call. The operation also includes providing, based on the command, instructions to the companion device to answer the incoming call and relay audio data of the answered incoming call to an electronic device. In accordance with the instruction to successfully cause the companion device to answer the incoming call, an audio output is output at an electronic device speaker based on the audio data of the answered incoming call received from the companion device.

[0332] Receiving a signal indicating an incoming call at the companion device and causing the server to determine a user intent based on context information derived from the signal enables the primary device to accurately obtain a command representing a task corresponding to the received user utterance. Additionally, the signal enables the primary device to identify that the command should be executed by the companion device, so the primary device can effectively provide instructions to the companion device to perform the task of answering the incoming call. This enables the primary device to act as an intelligent centralized hub to process voice user requests and coordinate the distribution of resulting commands. Thus, voice interaction at the primary device can be used to access the call function of the companion device, which improves user accessibility to the companion device and provides a better user experience. For example, the user does not need to be near the companion device to answer an incoming call on the companion device. Instead, the user can provide a voice request to the primary device, causing the companion device to answer the incoming call and transmit audio data from the answered call to the primary device.

[0333] Furthermore, using voice interaction at the primary device to access the call function of the companion device enables the features of each device to be utilized in a manner that results in an improved user experience. For example, the primary device is an intelligent speaker that does not have an independent call function but has a microphone and speaker that provide high-quality audio suitable for far-field voice interaction. In contrast, the companion device is a smartphone that has an independent call function. However, the microphone and speaker of the companion device do not provide audio of a suitable quality for far-field voice interaction. By using voice interaction at the primary device to access the call function of the companion device, the microphone and speaker of the primary device can be combined with the call function of the companion device to accurately and effectively process far-field voice requests to answer an incoming call on the companion device. Additionally, as a result of making a call via the primary device, the quality of the audio exchanged during the incoming call can be improved.

[0334] Now turning to Figures 12A to 12BThe operation depicted in [description], at block 1202, exchanges authentication information with a companion device (e.g., using communication module 228). The exchanged authentication information is used to verify whether the companion device is a registered device of the primary device. The primary device is, for example, similar to or the same as device 122 described above, and the companion device is, for example, similar to device 104 described above. In some examples, the companion device has an independent calling function, while the primary device does not have an independent calling function. In these examples, the primary device cannot make a call or receive an incoming call from an external device without relying on the calling function of the companion device. In some examples, block 1202 is performed before blocks 1206 and 1208.

[0335] At block 1204, based on the determination that the companion device is a registered device of the primary device according to the authentication information, a wireless communication connection is established with the companion device (e.g., as shown by arrow 908 in [reference]). For example, the wireless communication connection is established using the communication module of the primary device (e.g., communication module 228) and the RF circuit (e.g., RF circuit 208). Alternatively, based on the determination that the companion device is not a registered device of the primary device according to the authentication information, a wireless communication connection is not established with the companion device. It should be appreciated that in some examples, a wireless communication connection is required to receive the signal of block 1206 and provide the instruction of block 1218. Figure 9 At block 1206, a signal is received from the companion device (e.g., as shown by arrow 910 in [reference]). The received signal indicates, for example, an incoming call at the companion device. In some examples, the signal is received via the established wireless communication connection of block 1204. In some examples, for example, the signal is received by the I / O processing module (e.g., I / O processing module 728) of the digital assistant module (e.g., digital assistant module 726) implemented on the primary device.

[0336] In some examples, when receiving the signal, the companion device outputs an indication of the incoming call (e.g., an audio, visual, or tactile indication), while the primary device does not output an audio indication of the incoming call. Specifically, outputting an indication of the incoming call at the companion device and not outputting an audio indication of the incoming call at the primary device can enhance the user experience by not providing the user with multiple notification signals. Figure 9 At block 1208, a user utterance is received (e.g., as shown by [reference]).

[0337] In some examples, the signal includes information about the incoming call caller. In some examples, in response to receiving the signal, a voice dialogue containing information about the caller is automatically output (e.g., using the speech synthesis module 740 and via the speaker 211).

[0338] At block 1208, a user utterance is received (e.g., as shown by arrow [reference]).

[0339] At block 1208, a user utterance is received (e.g., as shown by [reference]). Figure 9as indicated by arrow 912 in). The user's speech is received at the I / O processing module (e.g., I / O processing module 728) via the microphone of the primary device (e.g., microphone 213). The user's speech includes, for example, natural language in speech that represents a request to perform a task on the device. In some examples, the user's speech regarding the device on which the user wishes to perform a task is ambiguous. In some examples, the user's speech regarding the specific task the user wishes to perform is ambiguous.

[0340] In some examples, the user's speech is received in conjunction with invoking the digital assistant of the primary device. In these examples, block 1208 includes determining whether a first portion of the user's speech contains a predefined voice trigger (block 1210). Based on the determination that the first portion of the user's speech contains the predefined voice trigger, a second portion of the user's speech that is separate from the first portion is received (block 1212). Specifically, process 1200 automatically processes the second portion of the user's speech to determine the user's intent (e.g., using the STT processing module 730 and the natural language processing module 732). Alternatively, based on the determination that the first portion of the user's speech does not contain the predefined voice trigger, process 1200 stops processing the user's speech and waits to receive a subsequent user's speech.

[0341] At block 1214, process 1200 causes the server (e.g., DA server 106) to determine the user's intent corresponding to the user's speech based on the user's speech and context information (e.g., as Figure 9 indicated by arrow 914 in). For example, a representation of the user's speech and context information is sent to the server, which causes the server to determine the text representation of the user's speech (e.g., using the STT processing module 730). Based on the text representation and context information, the user's intent is determined (e.g., using the natural language processing module 732). Based on the user's intent corresponding to the executable intent to answer an incoming call, the operations of blocks 1216 - 1220 are performed.

[0342] In some examples, the context information is based on the signal of block 1206. For example, the context information includes the operating state of the companion device. Specifically, the context information specifies that an incoming call is detected at the companion device. In some examples, the context information specifies that a wireless communication connection is established between the primary device and the companion device, and the companion device is a registered device of the electronic device. In some examples, the context information specifies the capabilities of the companion device (e.g., call function, email function, etc.).

[0343] At block 1216, a command is received from the server (e.g., as Figure 9as indicated by arrow 916). The received command represents a task that satisfies the executable intent of answering an incoming call. In some examples, the command specifies the domain of the user intent or the executable intent node. For example, the command specifies the "Answer Call" executable intent node of the "Phone" superdomain corresponding to the determined user intent.

[0344] At block 1218, based on the command, instructions are provided to the companion device (e.g., as indicated by arrow 916). For example, the instructions are provided via the established wireless communication connection of block 1204. These instructions cause the companion device to answer the incoming call. In some examples, the instructions also cause the companion device to relay the audio data of the answered incoming call to the primary device. In some examples, the instructions include the command of block 1216.

[0345] In some examples, block 1218 includes determining whether the command will be executed by the companion device. The determination is based on, for example, a set of rules, executable intents, and context information. In these examples, the instructions are provided to the companion device based on the determination that the command will be executed by the companion device.

[0346] In some examples, the incoming call at the companion device is a video call. In these examples, the provided instructions cause the companion device to answer the video call as an audio call. For example, the video data of the answered call is not exchanged between the primary device and the companion device.

[0347] At block 1220, based on the instructions that successfully cause the companion device to answer the incoming call, an audio output is generated according to the audio data of the answered incoming call. For example, the primary device receives the audio data of the answered incoming call from the companion device (e.g., as indicated by arrow 918 in Figure 9 ), and a corresponding audio output is generated from the speaker of the primary device (e.g., speaker 211). The audio data includes, for example, voice data received at the microphone of an external device that placed the call (e.g., the caller).

[0348] At block 1222, a confirmation signal is received from the companion device (e.g., as indicated by arrow 922 in Figure 9 ). The confirmation signal indicates whether the incoming call has been successfully answered. In examples where the incoming call is not successfully answered, the confirmation signal indicates an error code representing the type of error that occurred. In some examples, the representation of the confirmation signal is provided to the server. In some examples, block 1222 is executed after block 1218.

[0349] At block 1224, a voice dialogue is output that prompts the user to call back (e.g., via the speaker of the primary device). For example, the dialogue is generated by the server (e.g., DA server 106) based on the confirmation signal. Thus, the primary device receives the dialogue from the server (e.g., as indicated by Figure 9as indicated by arrow 924 in []. In some examples, block 1224 is performed based on an incoming call that ended before the companion device executed an instruction to answer the incoming call and based on an incoming call with caller identification information. In some examples, the voice conversation includes caller identification information. For example, the voice conversation prompts the user to make a call based on the caller identification information.

[0350] At block 1226, a voice conversation indicating an unanswered incoming call is output. This voice conversation does not prompt the user to call back. For example, a conversation is received from a server (e.g., as Figure 9 indicated by arrow 924 in []. For example, the server generates a voice conversation based on an acknowledgement signal. Block 1226 is performed based on an incoming call that ended before the companion device executed an instruction to answer the incoming call and based on an incoming call without caller identification information.

[0351] At block 1228, a second user utterance is received (e.g., as Figure 10 indicated by arrow 1010 in []. The second user utterance is received during an ongoing call. For example, as a result of the companion device successfully answering the call according to the provided instruction, a call is established (block 1218). In some examples, the second user utterance is received when generating an audio output based on the audio data of the incoming call being answered (e.g., at the speaker of the primary device) (block 1220).

[0352] At block 1230, process 1200 causes the server (e.g., DA server 106) to determine a second user intent corresponding to the second user utterance based on the second user utterance and second context information (e.g., as Figure 10 indicated by arrow 1012 in []. Block 1230 is similar to block 1214. In some examples, the second context information contains information similar to the context information of block 1214. In some examples, the second context information also indicates that the companion device is in an ongoing call. In some examples, when determining the second user intent, the server generates a second command representing a second task that satisfies the second user intent.

[0353] In some examples, according to the second user intent corresponding to an executable intent other than the call function for controlling the call, process 1200 abandons the execution of a task that satisfies an executable intent other than the call function for controlling the call. For example, the server abandons generating a second command to cause the primary device and / or the companion device to satisfy the second user intent.

[0354] At block 1232, a second command representing a second task that satisfies the second user intent is received from the server (e.g., as Figure 10as indicated by arrow 1014 in []. Box 1232 is similar to box 1216. In some examples, the second command specifies a domain of the second user intent or an executable intent node. For example, according to the second user intent corresponding to the executable intent of ending a call, the second command specifies the "end call" executable intent node of the "phone" superdomain. In this example, the second task includes one or more tasks that satisfy the executable intent of ending a call.

[0355] As another example, according to the second user intent corresponding to the executable intent of transmitting DTMF tones during a call, the second command specifies the "transmit DTMF tones" executable intent node of the "phone" superdomain. The second command also specifies one or more character keys, such as a phone keypad. The specified one or more character keys correspond to, for example, one or more character keys defined in the second user utterance. In this example, the second task includes one or more tasks that satisfy the executable intent of transmitting DTMF tones during a call.

[0356] At box 1232, based on the second command, process 1200 causes the companion device to perform a second task that satisfies the second user intent. For example, based on the second command, a second instruction is provided to the companion device (e.g., as Figure 10 indicated by arrow 1016 in []). In some examples, the second instruction includes the second command. When the second instruction is received and executed by the companion device, it causes the companion device to perform a second task that satisfies the second user intent.

[0357] In some examples, according to the second user intent corresponding to the executable intent of ending a call, the second instruction causes the companion device to perform the second task of ending the call. In some examples, the second command of box 1232 is executed by the primary device, which in turn causes the companion device to end the call. For example, the primary device stops receiving audio data of the call from the companion device, which causes the companion device to end the call. Alternatively, the primary device sends a signal to the companion device, which, when received by the companion device, causes the companion device to end the call. For example, the signal is different from the second command. It may be necessary to execute the second command at the primary device rather than the companion device because this can result in a faster response from the user's perspective. In addition, the primary device can be released more quickly for subsequent calls with this or a different companion device.

[0358] In other examples, according to the second user intent corresponding to the executable intent of transmitting DTMF tones during a call, the second instruction causes the companion device to perform the second task of transmitting one or more DTMF tones corresponding to the one or more character keys specified in the second command (and defined in the second user utterance) during the call.

[0359] The operations described above are optionally performed by Figures 12A to 12B and Figures 1 to 4 、Figures 6A to 6B and Figures 7A to 7C and the components depicted in Figures 7A to 7C . For example, the operations of process 1200 are implemented by communication module 228, RF circuit 208, telephone module 238, and / or video conferencing module 239. The operations of process 1200 are further implemented by digital assistant module 726 (e.g., implemented in DA server 106 and DA client module 229), which digital processing module includes I / O processing module 728, STT processing module 730, natural language processing module 732, dialogue flow processing module 734, task flow processing module 736, and service processing module 738 and / or speech synthesis processing module 738. Those of ordinary skill in the art will clearly know how to implement other processes based on the components depicted in Figures 1 to 4 , Figures 6A to 6B and Figures 7A to 7C .

[0360] According to some specific embodiments, there is provided a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) that 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 one of the methods or processes described herein.

[0361] According to some specific embodiments, there is provided an electronic device (e.g., a portable electronic device) that includes means for performing any one of the methods and processes described herein.

[0362] According to some specific embodiments, there is provided an electronic device (e.g., a portable electronic device) that includes a processing unit configured to perform any one of the methods and processes described herein.

[0363] According to some specific embodiments, there is provided an electronic device (e.g., a portable electronic device) that 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 one of the methods and processes described herein.

[0364] Certain aspects of the present technology may include collecting and using data that can be obtained from various sources to improve the accurate determination of user intent, and using voice interaction to enable effective and stable access to call functions. The present disclosure contemplates that, in some instances, the 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, telephone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0365] The present disclosure recognizes that using such personal information data in the technology of the present invention can be used to benefit users. For example, personal information data can be used to more accurately and reliably determine user intent. Therefore, using such personal information data enables users to more accurately and reliably use voice interaction to access call functions. In addition, the present disclosure also contemplates other uses of personal information data that are beneficial to 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 for individuals using technology to pursue health goals.

[0366] The present disclosure contemplates 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 readily 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 uses of the entity and should not be shared or sold outside of these legitimate uses. In addition, such collection / sharing should be done after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to safeguard and secure access to such personal information data and ensure that others with access to personal information data comply with their privacy policies and procedures. Additionally, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adjusted to account for the specific types of personal information data being collected and / or accessed and to apply applicable laws and standards that include specific considerations of the jurisdiction. For example, in the United States, the collection or acquisition 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 for different types of personal data in each country.

[0367] Regardless of the foregoing, the present disclosure also contemplates embodiments in which a user selectively blocks 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, in the case of a digital assistant, the techniques of the present invention may be configured to allow a user to select to "opt-in" or "opt-out" of participating in the collection of personal information data during the registration service or at any time thereafter. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to the access or use of personal information. For example, a user may be notified when an application is downloaded that their personal information data will be accessed, and then reminded again just before the personal information data is accessed by the application.

[0368] In addition, it is an object of the present disclosure to manage and process personal information data to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by restricting data collection and deleting the data. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. In appropriate cases, de-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or characteristics of the data stored (e.g., collecting location data at the city level rather than the address level), controlling the way the data is stored (e.g., aggregating data between users), and / or other methods.

[0369] 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 techniques of the present invention will not fail to function properly due to the lack of all or a portion of such personal information data. For example, user intent may be determined based on non-personal information data or an absolute minimum amount of personal information (such as the content requested by a device associated with the user, other non-personal information applicable to the digital assistant, or publicly available information).

[0370] For purposes of explanation, the foregoing description has been described by reference to specific embodiments. However, the above illustrative discussion is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Other technicians in the art will thereby be able to best utilize the techniques and various embodiments with various modifications suited to the particular uses contemplated.

[0371] While the present disclosure and examples have been described fully 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 present disclosure and examples as defined by the claims.

Claims

1. A method for accessing functions of a digital assistant using voice interaction, the method comprising: At a main electronic device having a processor, a memory, and a speaker: Receiving audio data of a communication session from a companion electronic device, wherein the audio data represents utterances received by the companion electronic device, wherein the audio data is sent from a remote party of an active call via a communication session connection, wherein the remote party includes an external electronic device, and wherein the main electronic device communicates with the companion electronic device; Invoking a digital assistant on the main electronic device based on the received audio data; Determining a user intent corresponding to the utterance based on the audio data; Determining one or more tasks for fulfilling the user intent; Determining a digital assistant response based on results of executing the one or more tasks; And Transmitting the digital assistant response to the companion electronic device, wherein the companion electronic device transmits the digital assistant response to the remote party of the external electronic device via the communication session connection.

2. The method according to claim 1, wherein the external electronic device has a processor, a memory, and a speaker, and Among them, Transmitting the digital assistant response to the remote party via the communication session connection causes a speaker of the remote party to output the digital assistant response as a first audio signal during the communication session.

3. The method according to claim 2, further comprising: After transmitting the digital assistant response to the remote party, outputting the digital assistant response via a speaker of the main electronic device as a second audio signal.

4. The method according to claim 3, wherein The remote party and the main electronic device simultaneously output the first audio signal and the second audio signal, respectively.

5. The method according to any one of claims 1-4, wherein Determining a user intent corresponding to the utterance based on results of performing natural language processing on the audio data.

6. The method according to claim 5, wherein, Further determining a user intent corresponding to the utterance based on context information.

7. The method according to claim 6, wherein, The context information indicates that the main electronic device is participating in the communication session.

8. The method according to any one of claims 1-7, further comprising: Determining whether the user intent corresponds to an executable intent for controlling a call function of the communication session; And According to determining that the user intent corresponds to an executable intent for controlling a communication session function of the communication session, performing determining the digital assistant response and transmitting the digital assistant response.

9. The method according to any one of claims 1-8, further comprising: In response to determining the one or more tasks for fulfilling the user intent, determining which electronic device among a plurality of electronic devices will execute the command based on the user intent, wherein the plurality of electronic devices includes the main electronic device.

10. A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of a first electronic device, the one or more programs including instructions that, when executed by the one or more processors, cause the first electronic device to execute the method according to any one of claims 1-9.

11. A first electronic device, comprising: One or more processors; A memory; And One or more programs stored in the memory, the one or more programs including instructions for performing the method according to any one of claims 1-9.

Images