Attachment device based authentication for digital assistant requests

Abstract

This disclosure relates to attachment device based authentication for digital assistant requests. An example method includes, at an electronic device with one or more processors and memory: while the electronic device is in a locked state and in communication with an external attachment device: receiving natural language input; determining whether the natural language input corresponds to a secure task request; in accordance with a determination that the natural language input corresponds to a secure task request: determining whether one or more states of the external attachment device satisfy a set of authentication criteria; and in accordance with a determination that the one or more states of the external attachment device satisfy the set of authentication criteria: initiating, by the electronic device, a secure task corresponding to the natural language input; and providing output indicating the initiated secure task.

Description

Technical Field

[0001] This disclosure relates in general to intelligent automation assistants, and more specifically, to using an accessory device to authenticate a device for processing requests for an intelligent automation assistant running on the device. Background Technology

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

[0003] This document discloses an example method. An example method includes, at an electronic device having one or more processors and memory: while the electronic device is in a locked state and communicating with an external accessory device: receiving natural language input; determining whether the natural language input corresponds to a security task request; based on determining that the natural language input corresponds to a security task request: determining whether one or more states of the external accessory device satisfy a set of authentication criteria; and based on determining that the one or more states of the external accessory device satisfy the set of authentication criteria: initiating a security task corresponding to the natural language input by the electronic device; and providing an output indicating the initiated security task.

[0004] This document discloses an example non-transitory computer-readable medium. An example non-transitory computer-readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the following operations: when the electronic device is in a locked state and communicating with an external accessory device: receiving natural language input; determining whether the natural language input corresponds to a security task request; based on the determination that the natural language input corresponds to a security task request: determining whether one or more states of the external accessory device satisfy a set of authentication criteria; and based on the determination that the one or more states of the external accessory device satisfy the set of authentication criteria: initiating a security task corresponding to the natural language input by the electronic device; and providing an output indicating the initiated security task.

[0005] This document discloses an example electronic device. An example electronic device includes one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: when the electronic device is in a locked state and communicating with an external accessory device: receiving natural language input; determining whether the natural language input corresponds to a security task request; based on determining that the natural language input corresponds to a security task request: determining whether one or more states of the external accessory device meet a set of authentication criteria; and based on determining that the one or more states of the external accessory device meet the set of authentication criteria: initiating a security task corresponding to the natural language input by the electronic device; and providing an output indicating the initiated security task.

[0006] An example electronic device includes means for performing the following operations: when the electronic device is in a locked state and communicating with an external accessory device: receiving natural language input; determining whether the natural language input corresponds to a security task request; based on determining that the natural language input corresponds to a security task request: determining whether one or more states of the external accessory device meet a set of authentication criteria; and based on determining that the one or more states of the external accessory device meet the set of authentication criteria: initiating a security task corresponding to the natural language input by the electronic device; and providing an output indicating the initiated security task.

[0007] Initiating a security task only when predetermined conditions are met (e.g., natural language input corresponds to a security task request and one or more states of an external accessory device meet a set of authentication criteria) provides efficient and secure digital assistant operation. For example, this technology allows a device to securely perform a security task and output the result (e.g., displaying the user's personal and / or private information) even when the device is locked. In this way, the efficiency of the digital assistant is improved by enabling it to perform the desired task without requiring user input to unlock the device. Furthermore, determining whether natural language input corresponds to a security task request allows a locked device to authenticate itself only when necessary to perform a security task, for example, because the digital assistant can perform non-security tasks regardless of whether the device is locked. In this way, device computing resources and battery power are saved by not attempting to authenticate the device when unnecessary (e.g., when the requested task is insecure). Performing actions when a set of conditions have been met without requiring further user input enhances device operability and makes the user-device interface more efficient and secure (e.g., by reducing the user input required for the digital assistant to perform the desired task, by unlocking the device without physical interaction to enable the digital assistant to perform the desired task, by securely providing the user's personal and / or private information). This also reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0008] This document discloses an example method. An example method includes, at an electronic device having one or more processors and memory: when the electronic device is in a locked state and communicating with an external accessory device: receiving a request to unlock the electronic device; and, based on receiving the request to unlock the electronic device, determining whether one or more states of the external accessory device satisfy a set of authentication criteria; changing the state of the electronic device from the locked state to the unlocked state based on determining that the one or more states of the external accessory device satisfy the set of authentication criteria; after changing the state from the locked state to the unlocked state, changing the state from the unlocked state to the second locked state; while the electronic device is in the second locked state: receiving natural language input corresponding to a security task request; determining whether the one or more states of the external accessory device satisfy the set of authentication criteria based on receiving the natural language input; and, based on determining that the one or more states of the external accessory device satisfy the set of authentication criteria: initiating a security task corresponding to the natural language input by the electronic device; and providing an output indicating the initiated security task.

[0009] This document discloses an example non-transitory computer-readable medium. An example non-transitory computer-readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the following operations: when the electronic device is in a locked state and communicating with an external accessory: receiving a request to unlock the electronic device; and, based on receiving the request to unlock the electronic device, determining whether one or more states of the external accessory device satisfy a set of authentication criteria; based on determining that the one or more states of the external accessory device satisfy the set of authentication criteria, changing the state of the electronic device from the locked state to the unlocked state; after changing the state from the locked state to the unlocked state, changing the state from the unlocked state to a second locked state; when the electronic device is in the second locked state: receiving natural language input corresponding to a security task request; based on receiving the natural language input, determining whether the one or more states of the external accessory device satisfy the set of authentication criteria; and based on determining that the one or more states of the external accessory device satisfy the set of authentication criteria: initiating a security task corresponding to the natural language input by the electronic device; and providing an output indicating the initiated security task.

[0010] This document discloses an example electronic device. An example electronic device includes one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: when the electronic device is in a locked state and communicating with an external accessory device: receiving a request to unlock the electronic device; and, based on receiving the request to unlock the electronic device, determining whether one or more states of the external accessory device meet a set of authentication criteria; based on determining that the one or more states of the external accessory device meet the set of authentication criteria, changing the state of the electronic device from the locked state to the unlocked state; after changing the state from the locked state to the unlocked state, changing the state from the unlocked state to the second locked state; when the electronic device is in the second locked state: receiving natural language input corresponding to a security task request; based on receiving the natural language input, determining whether the one or more states of the external accessory device meet the set of authentication criteria; and based on determining that the one or more states of the external accessory device meet the set of authentication criteria: initiating a security task corresponding to the natural language input by the electronic device; and providing an output indicating the initiated security task.

[0011] An example electronic device includes means for performing the following operations: when the electronic device is in a locked state and communicating with an external accessory device: receiving a request to unlock the electronic device; and, based on receiving the request to unlock the electronic device, determining whether one or more states of the external accessory device meet a set of authentication criteria; and, based on determining that the one or more states of the external accessory device meet the set of authentication criteria, changing the state of the electronic device from the locked state to the unlocked state; after changing the state from the locked state to the unlocked state, changing the state from the unlocked state to the second locked state; when the electronic device is in the second locked state: receiving natural language input corresponding to a security task request; based on receiving the natural language input, determining whether the one or more states of the external accessory device meet the set of authentication criteria; and, based on determining that the one or more states of the external accessory device meet the set of authentication criteria: initiating a security task corresponding to the natural language input by the electronic device; and providing an output indicating the initiated security task.

[0012] Based on determining that one or more states of an external accessory device meet a set of authentication criteria (e.g., using the accessory device to authenticate the device), and after initiating a security task by changing the state of the electronic device from locked to unlocked using the accessory device to authenticate the device, the device provides feedback to the user that the accessory device is available to authenticate the device for security operations (e.g., unlocking the device, performing security tasks via a digital assistant) when the device is locked. For example, by first unlocking itself using the accessory device, the device can notify the user that the accessory device is available to authenticate the device. After the device is relocked, the device can notify the user that the device uses the same security mechanism (used for unlocking the device) to authenticate itself for security tasks by again using the external accessory device to authenticate itself for security tasks. Providing the user with improved feedback enhances device operability and makes the user-device interface more efficient (e.g., by helping the user provide correct input and reducing user errors when operating / interacting with the device, by notifying the user that the digital assistant can perform security tasks when the device is locked, and by reducing the user input that would otherwise be required to unlock the device for the digital assistant to perform security tasks). This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently. Attached Figure Description

[0013] Figure 1 Block diagrams are shown for systems and environments used to implement digital assistants, based on various examples.

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

[0015] Figure 2B A block diagram illustrating exemplary components for event handling, based on various examples.

[0016] Figure 3 Portable multi-functional devices are shown that implement the client-side portion of a digital assistant according to various examples.

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

[0018] Figure 5A An exemplary user interface for the menu of an application on a portable multi-functional device, based on various examples, is shown.

[0019] Figure 5B Exemplary user interfaces of multifunctional devices with touch-sensitive surfaces separate from the display are shown according to various examples.

[0020] Figure 6A The images show personal electronic devices based on various examples.

[0021] Figure 6B A block diagram illustrating a personal electronic device based on various examples is provided.

[0022] Figure 7A A block diagram illustrating a digital assistant system or its server portion, based on various examples, is provided.

[0023] Figure 7B Examples are shown in Figure 7A The digital assistant functions shown.

[0024] Figure 7C A portion of the knowledge ontology is shown based on various examples.

[0025] Figures 8A to 8G The techniques for using an accessory device to authenticate a device in order to process digital assistant requests are illustrated with various examples.

[0026] Figures 9A to 9G The techniques for digital assistant requests to unlock and authenticate a device using an accessory device are illustrated, based on various examples.

[0027] Figures 10A to 10C The process of authenticating accessory-based devices for digital assistant requests is illustrated with various examples.

[0028] Figures 11A to 11C The process of requesting a digital assistant to unlock and authenticate a device using an accessory device is illustrated, based on various examples. Detailed Implementation

[0029] The accompanying drawings will be referenced in the following description of the examples, which illustrate specific examples that can be implemented by way of example. It should be understood that other examples may be used and structural changes may be made without departing from the scope of the individual examples.

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

[0031] The terminology used in the description of the various examples herein is for the purpose of describing particular examples only and is not intended to be limiting. As used in the description of the various examples and the appended claims, the singular forms “an,” “a,” 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 covers 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” as used in this specification specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0032] Depending on the context, the term "if" can be interpreted as meaning "when" or "upon" or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" can be interpreted as meaning "when determination..." or "in response to determination..." or "when detection [the stated condition or event]" or "in response to detection [the stated condition or event]."

[0033] 1. System and Environment

[0034] Figure 1A block diagram of system 100 according to various examples is shown. In some examples, system 100 implements a digital assistant. The terms "digital assistant," "virtual assistant," "intelligent automated assistant," or "automated digital assistant" refer to any information processing system that interprets natural language input in spoken and / or textual form to infer user intent and performs actions based on the inferred user intent. For example, to act on an inferred user intent, the system performs one or more of the following steps: identifying a task flow having steps and parameters designed to achieve the inferred user intent; inputting a specific request into the task flow based on the inferred user intent; 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.

[0035] Specifically, a digital assistant can accept user requests, at least in part, in the form of natural language commands, requests, statements, narration, and / or inquiries. Typically, user requests seek an informational response or task from the digital assistant. A satisfactory response to a user request includes providing the requested informational response, performing the requested task, or a combination of both. For example, a user asks a digital assistant a question such as, “Where am I now?” Based on the user’s current location, the digital assistant answers, “You are near the west entrance of Central Park.” The user also requests a task, such as, “Please invite my friends to my girlfriend’s birthday party next week.” In response, the digital assistant confirms the request by saying “Okay, coming right away,” and then sends the appropriate calendar invitations 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 a sustained dialogue involving multiple exchanges of information over extended periods. Many other methods exist for interacting with a digital assistant to request information or perform various tasks. In addition to providing verbal responses and taking programmed actions, digital assistants also provide responses in other forms of video or audio, such as text, alerts, music, video, animation, etc.

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

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

[0038] User equipment 104 can be any suitable electronic device. In some examples, user equipment 104 is a portable multi-functional device (e.g., see reference below). Figure 2A The aforementioned device 200), multifunctional device (for example, see below for reference) Figure 4 The device 400) or personal electronic device (e.g., referred to below) Figures 6A to 6B The device 600 is described above. A portable multifunction device is, for example, a mobile phone that also includes other functions such as a PDA and / or music player. Specific examples of portable multifunction devices include Apple Inc. (Cupertino, California). iPod and Devices. Other examples of portable multifunction devices include, but are not limited to, earbuds / headphones, speakers, and laptops or tablets. Additionally, in some examples, user device 104 is a non-portable multifunction device. Specifically, user device 104 is a desktop computer, game console, speaker, television, or set-top box. In some examples, user device 104 includes a touch-sensitive surface (e.g., a touchscreen display and / or touchpad). Furthermore, user device 104 optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick. Various examples of electronic devices such as multifunction devices are described in more detail below.

[0039] Examples of one or more communication networks 110 include local area networks (LANs) and wide area networks (WANs), such as the Internet. Communication network 110 is 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.

[0040] 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 utilizes various virtual devices and / or services from third-party service providers (e.g., third-party cloud service providers) to provide potential computing and / or infrastructure resources for server system 108.

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

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

[0043] Although Figure 1 The digital assistant shown includes both a client-side component (e.g., DA client 102) and a server-side component (e.g., DA server 106), but in some examples, the digital assistant's functionality is implemented as a standalone application installed on the user's device. Furthermore, the functional division between the client and server components of the digital assistant can 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 the backend server.

[0044] 2. Electronic equipment

[0045] Now let’s turn our attention to the implementation of electronic devices for the client-side portion of a digital assistant. Figure 2AThis is a block diagram illustrating a portable multi-functional device 200 with a touch-sensitive display system 212 according to some embodiments. The touch-sensitive display 212 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” Device 200 includes a memory 202 (which optionally includes one or more computer-readable storage media), a memory controller 222, one or more processing units (CPUs) 220, a peripheral interface 218, RF circuitry 208, audio circuitry 210, a speaker 211, a microphone 213, an input / output (I / O) subsystem 206, other input control devices 216, and an external port 224. Device 200 optionally includes one or more optical sensors 264. Device 200 optionally includes one or more contact strength sensors 265 for detecting the intensity of contact on the device 200 (e.g., a touch-sensitive surface of the device 200 such as the touch-sensitive display system 212). Device 200 optionally includes one or more haptic output generators 267 for generating haptic outputs on device 200 (e.g., generating haptic outputs on a touch-sensitive surface such as the touch-sensitive display system 212 of device 200 or the touchpad 455 of device 400). These components optionally communicate via one or more communication buses or signal lines 203.

[0046] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the tactile surface are optionally used to measure the force at different points on the tactile 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 tactile surface. Alternatively, the size and / or variation of the contact area detected on the touch-sensitive surface, the capacitance and / or variation of the touch-sensitive surface near the contact, and / or the resistance and / or variation of the touch-sensitive surface near the contact may optionally be used as substitutes for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement) has been exceeded. In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure) has been exceeded. Using the intensity of the contact as an attribute of user input allows the user to access additional device functions that would otherwise be inaccessible to the user on smaller devices with limited physical space, such smaller devices being used (e.g., on a touch-sensitive display) to display power indications and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0047] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user's movement does not move. For example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific sensory perception of a user (e.g., "press click", "release click", "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or its components that will generate the sensory perception of a typical (or ordinary) user.

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

[0049] 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. Memory controller 222 controls other components of device 200 to access memory 202.

[0050] In some examples, the non-transitory computer-readable storage medium of memory 202 is used to store instructions (e.g., 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 processor-integrated system, or other system from which instructions can be fetched and executed. In other examples, instructions (e.g., aspects of the processes described below) are stored on a non-transitory computer-readable storage medium (not shown) of server system 108, or partitioned between the non-transitory computer-readable storage medium of memory 202 and the non-transitory computer-readable storage medium of server system 108.

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

[0052] RF (Radio Frequency) circuit 208 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 208 converts electrical signals into electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 208 optionally includes well-known circuitry for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, Subscriber Identity Module (SIM) cards, memory, etc. RF circuit 208 optionally communicates wirelessly with networks and other devices, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 208 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via near-field communication radio components. Wireless communication may optionally employ any of a variety of communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolution, Pure Data (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), and 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), Wi-MAX, email protocols (e.g., Internet Messaging 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 with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols that have not yet been developed as of the date of this document submission.

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

[0054] I / O subsystem 206 couples input / output peripherals on device 200, such as touchscreen 212 and other input control devices 216, to peripheral interface 218. I / O subsystem 206 optionally includes display controller 256, optical sensor controller 258, intensity sensor controller 259, haptic feedback controller 261, and one or more input controllers 260 for other input or control devices. One or more input controllers 260 receive electrical signals from / send electrical signals to other input control devices 216. Other input control devices 216 optionally include physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click wheels, etc. In some alternative embodiments, input controllers 260 are optionally coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, and pointing devices such as a mouse. One or more buttons (e.g., Figure 3 Optionally, 308) includes volume up / down buttons for volume control of speaker 211 and / or microphone 213. One or more buttons optionally include push-button buttons (e.g., Figure 3 (306 in the middle).

[0055] A rapid press of the down button disengages the touchscreen 212 from its lock or initiates the process of unlocking the device using gestures on the touchscreen, as described in U.S. Patent Application No. 7,657,849, 11 / 322,549, filed December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," the entire contents of which are incorporated herein by reference. A longer press of the down button (e.g., 306) powers the device 200 on or off. The user can customize the function of one or more buttons. The touchscreen 212 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

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

[0058] Touchscreen 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. Touchscreen 212 and display controller 256 use any of a variety of touch sensing technologies currently known or to be developed thereafter, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 212 to detect contact and any movement or interruption thereto. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that from Apple Inc. (Cupertino, California). and iPod The technology used.

[0059] In some embodiments, the touchscreen 212's touch-sensitive display is similar to the multi-touch pad 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 incorporated herein by reference in their entirety. However, the touchscreen 212 displays visual output from the device 200, while the touch-sensitive pad does not provide visual output.

[0060] In some embodiments, the touchscreen 212 has a touch-sensitive display as described in the following applications: (1) U.S. Patent Application No. 11 / 381313, filed May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. Patent Application No. 10 / 840862, filed May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. Patent Application No. 10 / 903964, filed July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. Patent Application No. 11 / 048264, filed January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; and (5) U.S. Patent Application No. 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input”. U.S. Patent Application No. 11 / 038590, entitled “Virtual Input Device Placement On A Touch Screen User Interface”, filed September 16, 2005; U.S. Patent Application No. 11 / 228758, entitled “Virtual Input Device Placement On A Touch Screen User Interface”, filed September 16, 2005; U.S. Patent Application No. 11 / 228700, entitled “Operation Of A Computer With A Touch Screen Interface”, filed September 16, 2005; U.S. Patent Application No. 11 / 228737, entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”, filed September 16, 2005; and U.S. Patent Application No. 11 / 367749, entitled “Multi-Functional Hand-Held Device”, filed March 3, 2006. The entire contents of all these applications are incorporated herein by reference.

[0061] Touchscreen 212 has a video resolution of over 100 dpi, for example. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. The user interacts with touchscreen 212 using any suitable object or accessory such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-desired actions.

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

[0063] The device 200 also includes a power system 262 for supplying power to various components. The power system 262 includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0064] The device 200 also includes one or more optical sensors 264. Figure 2A An optical sensor 264 is shown coupled to an optical sensor controller 258 in the I / O subsystem 206. The optical sensor 264 includes a charge-coupled device (CCD) or complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensor 264 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 243 (also called a camera module), the optical sensor 264 captures still images or video. In some embodiments, the optical sensor is located at the rear of the device 200, opposite to the touchscreen display 212 at the front of the device, such that the touchscreen 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 for use in video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 264 can be changed by the user (e.g., by rotating the lenses and sensors within the device housing), such that a single optical sensor 264 is used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

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

[0066] The device 200 also includes one or more proximity sensors 266. Figure 2A A proximity sensor 266 coupled to a peripheral device interface 218 is shown. Alternatively, the proximity sensor 266 is coupled to an input controller 260 in an I / O subsystem 206. The proximity sensor 266 performs as described in the following U.S. patent applications: No. 11 / 241839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", the entire contents of which are incorporated herein by reference. In some implementations, the proximity sensor is turned off and the touchscreen 212 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0067] The device 200 optionally also includes one or more tactile output generators 267. Figure 2AA haptic output generator coupled to a haptic feedback controller 261 in I / O subsystem 206 is shown. 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 polymerizers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 265 receives haptic feedback generation instructions from a haptic feedback module 233 and generates a haptic output on device 200 that can be felt by a user of device 200. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 212) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 200) or laterally (e.g., backward and forward in the same plane as the surface of device 200). In some implementations, 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.

[0068] The device 200 also includes one or more accelerometers 268. Figure 2A An accelerometer 268 coupled to a peripheral device interface 218 is shown. Alternatively, the accelerometer 268 is coupled to an input controller 260 in an I / O subsystem 206. The accelerometer 268 performs as described in the following U.S. patent publications: U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices” and U.S. Patent Publication No. 20060017692, “Methods and Apparatuses For Operating A Portable Device BasedOn An Accelerometer,” the entire contents of which are incorporated herein by reference. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. Device 200 optionally includes, in addition to one or more accelerometers 268, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for acquiring information about the position and orientation (e.g., portrait or landscape) of device 200.

[0069] In some embodiments, software components stored in memory 202 include an operating system 226, a communication module (or instruction set) 228, a contact / motion module (or instruction set) 230, a graphics module (or instruction set) 232, a text input module (or instruction set) 234, a Global Positioning System (GPS) module (or instruction set) 235, a digital assistant client module 229, and an application program (or instruction set) 236. Furthermore, memory 202 stores data and models, such as user data and models 231. Additionally, in some embodiments, memory 202 ( Figure 2A ) or 470 ( Figure 4 Storage device / global internal state 257, such as Figure 2A and Figure 4 As shown in the diagram. Device / global internal state 257 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touchscreen display 212; sensor state, including information obtained from the device's various sensors and input control devices 216; and position information about the device's position and / or orientation.

[0070] The operating system 226 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or embedded operating systems such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0071] The communication module 228 facilitates communication with other devices via one or more external ports 224 and includes various software components for processing data received by the RF circuitry 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 via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to… (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0072] The contact / motion module 230 optionally detects contact with the touchscreen 212 (in conjunction with the display controller 256) and other touch-sensitive devices (e.g., touchpads or physical click-based rotary dials). 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 intensity of contact (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 230 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is 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 implementations, the contact / motion module 230 and the display controller 256 detect contact on the touchpad.

[0073] In some implementations, the contact / motion module 230 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., determining whether the user has “clicked” an icon). In some implementations, 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 thresholds of a specific physical actuator and can be adjusted without changing the physical hardware of the device 200). For example, the mouse “click” threshold for a touchpad or touchscreen can be set to any threshold in a wide range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some implementations, the user of the device is provided with software settings for adjusting one or more intensity thresholds in a set (e.g., by adjusting the individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using a system-level click on the “intensity” parameter).

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

[0075] The graphics module 232 includes various known software components for rendering and displaying graphics on the touchscreen 212 or other displays, including components for altering 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, and non-limitingly includes text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0076] In some implementations, 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 or the like, and, if necessary, also receives coordinate data and other graphic attribute data, and then generates screen image data for output to the display controller 256.

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

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

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

[0080] The digital assistant client module 229 includes various client-side digital assistant commands to provide client-side functionality for the digital assistant. For example, the digital assistant client module 229 can accept audio input (e.g., voice input), text input, touch input, and / or gesture input through various user interfaces of the portable multifunction device 200 (e.g., microphone 213, one or more accelerometers 268, touch-sensitive display system 212, one or more optical sensors 264, other input control devices 216, etc.). The digital assistant client module 229 can also provide audio output (e.g., voice output), visual output, and / or haptic output through various output interfaces of the portable multifunction device 200 (e.g., speaker 211, touch-sensitive display system 212, one or more haptic output generators 267, etc.). For example, output can be provided as voice, sound, alarms, text messages, menus, graphics, video, animation, vibration, and / or combinations of both or more of these. During operation, the digital assistant client module 229 communicates with the DA server 106 using RF circuitry 208.

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

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

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

[0084] In some examples, the digital assistant client module 229 selectively provides information (e.g., user data 231) stored on the portable multifunction device 200 in response to a request from the DA server 106. In some examples, the digital assistant client module 229 also elicits additional input from the user via natural language dialogue 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 in realizing the user intent expressed in the user request.

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

[0086] Application 236 includes the following modules (or instruction sets) or subsets or supersets:

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

[0088] • Telephone module 238;

[0089] Video conferencing module 239;

[0090] • Email client module 240;

[0091] • Instant Messaging (IM) module 241;

[0092] Fitness support module 242;

[0093] • Camera module 243 for still images and / or video images;

[0094] • Image management module 244;

[0095] • Video player module;

[0096] Music player module;

[0097] • Browser module 247;

[0098] • Calendar module 248;

[0099] • Desktop mini-program module 249, which in some examples includes one or more of the following: weather desktop mini-program 249-1, stock desktop mini-program 249-2, calculator desktop mini-program 249-3, alarm clock desktop mini-program 249-4, dictionary desktop mini-program 249-5 and other desktop mini-programs acquired by the user and desktop mini-programs created by the user 249-6.

[0100] • Desktop app creator module 250 for creating user-created desktop apps 249-6;

[0101] • Search module 251;

[0102] • Video and music player module 252, which combines a video player module and a music player module;

[0103] Notepad module 253;

[0104] • Map module 254; and / or

[0105] • Online video module 255.

[0106] Examples of other applications 236 stored in memory 202 include other word processing applications, other image editing applications, drawing applications, rendering applications, Java-enabled applications, encryption, digital access control, voice recognition, and voice duplication.

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

[0108] Combining RF circuitry 208, audio circuitry 210, speaker 211, microphone 213, touchscreen 212, display controller 256, contact / motion module 230, graphics module 232, and text input module 234, telephone module 238 is used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 237, modify already entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication uses any of a variety of communication standards, protocols, and technologies.

[0109] Combining RF circuitry 208, audio circuitry 210, speaker 211, microphone 213, touchscreen 212, display controller 256, optical sensor 264, optical sensor controller 258, contact / motion module 230, graphics module 232, text input module 234, contact module 237, and telephone module 238, video conferencing module 239 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

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

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

[0112] Incorporating RF circuitry 208, touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, text input module 234, GPS module 235, map module 254, and music player module, fitness support module 242 includes executable instructions for: creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (exercise equipment); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness; and displaying, storing, and transmitting fitness data.

[0113] In conjunction with the touchscreen 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, camera module 243 includes executable instructions for: capturing still images or videos (including video streams) and storing them in memory 202, modifying the characteristics of still images or videos, or deleting still images or videos from memory 202.

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

[0115] Combining RF circuitry 208, touchscreen 212, display controller 256, contact / motion module 230, graphics module 232, and text input module 234, 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, as well as links to attachments and other files on web pages.

[0116] Combining RF circuitry 208, touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, text input module 234, email client module 240, and browser module 247, calendar module 248 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

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

[0118] Combining RF circuit 208, touch screen 212, display controller 256, contact / motion module 230, graphics module 232, text input module 234, and browser module 247, the desktop applet creator module 250 is used by the user to create desktop applets (e.g., to turn a user-specified portion of a webpage into a desktop applet).

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

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

[0121] Combining the touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, and text input module 234, the notepad module 253 includes executable instructions for creating and managing notes, to-do items, etc., according to user instructions.

[0122] Combining 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, map module 254 is used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0123] Incorporating touchscreen 212, display controller 256, touch / motion module 230, graphics module 232, audio circuitry 210, speaker 211, RF circuitry 208, text input module 234, email client module 240, and browser module 247, the online video module 255 includes instructions allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on a connected external display via external port 224), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats (such as H.264). In some embodiments, instant messaging module 241 is used instead of email client module 240 to send links to specific online videos. Further descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936562, filed June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968067, filed December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

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

[0125] In some implementations, device 200 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for the operation of device 200, the number of physical input control devices (such as push-buttons, dials, etc.) on device 200 is reduced.

[0126] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some implementations, the touchpad, when touched by a user, navigates device 200 from any user interface displayed on device 200 to a main menu, home menu, or root menu. In such implementations, a touchpad is used to implement a "menu button." In some other implementations, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

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

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

[0129] In some implementations, 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 ready to be displayed by the application 236-1, a state queue for enabling the user to return to the previous state or view of the application 236-1, and a repeat / undo queue for the user's previous actions.

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

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

[0132] In some implementations, the event classifier 270 also includes a hit view determination module 272 and / or an activity event recognizer determination module 273.

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

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

[0135] The hit view determination module 272 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 272 identifies the hit view as the lowest-level view in the hierarchical structure from which the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events forming an event or potential event) occurs. Once the hit view is identified by the hit view determination module 272, the hit view typically receives all sub-events related to the same touch or input source to which it was identified as the hit view.

[0136] The activity event recognizer determination module 273 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 273 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 273 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, the higher-level views in the hierarchy will still remain actively participating views.

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

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

[0139] 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 event recognizers among the event recognizers 280 are part of a separate module, which is a higher-level object such as a user interface toolkit (not shown) 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 an 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's internal state 292. Alternatively, one or more application views in application view 291 include one or more corresponding event handlers 290. Additionally, in some embodiments, one or more of data updater 276, object updater 277, and GUI updater 278 are included in the corresponding application view 291.

[0140] The corresponding event recognizer 280 receives event information (e.g., event data 279) from the event classifier 270 and identifies events 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 one subset of metadata 283 and event delivery instructions 288 (which includes sub-event delivery instructions).

[0141] Event receiver 282 receives event information from event classifier 270. The event information includes information about sub-events such as touch or 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 touch movement, 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 lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device pose).

[0142] Event comparator 284 compares event information with predefined event or sub-event definitions and, based on the comparison, determines the event or sub-event, or determines or updates the state of the event or sub-event. In some embodiments, 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 event (287) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, event 1 (287-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (287-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) on the displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 212, and lifting off the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 290.

[0143] In some implementations, event definition 287 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 284 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 212, when a touch is detected on touch-sensitive display 212, event comparator 284 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 290, the event comparator uses the result of the hit test to determine which event handler 290 should be activated. For example, event comparator 284 selects the event handler associated with the sub-event and the object that triggered the hit test.

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

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

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

[0147] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 280 activates the event handler 290 associated with the event. In some implementations, 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 delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 280 throws a tag associated with the identified event, and the event handler 290 associated with that tag retrieves the tag and executes a predefined procedure.

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

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

[0150] In some implementations, event handler 290 includes, or has access to, a data updater 276, an object updater 277, and a GUI updater 278. In some implementations, data updater 276, object updater 277, and GUI updater 278 are included in a single module of the corresponding application 236-1 or application view 291. In other implementations, they are included in two or more software modules.

[0151] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction 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 conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0152] Figure 3A portable multifunction device 200 with a touchscreen 212 is shown according to some embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 300. In this embodiment and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example, using one or more fingers 302 (not drawn to scale in the figure) or one or more styluses 303 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 200. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0154] In some embodiments, device 200 includes a touchscreen 212, a menu button 304, a push-button 306 for powering on / off the device and locking the device, one or more volume control buttons 308, a SIM card slot 310, a headset jack 312, and a docking / charging external port 224. The push-button 306 is optionally used to power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In another embodiment, device 200 also accepts verbal input via microphone 213 for activating or deactivating certain functions. Device 200 also optionally includes one or more contact strength sensors 265 for detecting the intensity of contact on the touchscreen 212, and / or one or more haptic output generators 267 for generating haptic outputs for the user of device 200.

[0155] Figure 4This is a block diagram of an exemplary multifunctional device with a display and a touch-sensitive surface according to 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 controller or industrial controller). Device 400 typically 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. Communication bus 420 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 400 includes an input / output (I / O) interface 430 with a display 440, which is typically a touchscreen display. I / O interface 430 also optionally includes a keyboard and / or mouse (or other pointing device) 450 and a touchpad 455, and a haptic output generator 457 for generating haptic output on device 400 (e.g., similar to the reference above). Figure 2A The one or more tactile output generators 267 and sensors 459 (e.g., optical sensors, accelerometers, proximity sensors, touch sensors, and / or contact intensity sensors similar to those mentioned above) Figure 2A The one or more contact strength sensors 265 mentioned above). Memory 470 includes high-speed random access memory, such as DRAM, SRAM, DDRRAM, 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 memory devices. Memory 470 optionally includes one or more storage devices located remotely from CPU 410. In some embodiments, memory 470 stores data with portable multifunction device 200 (…). Figure 2A The memory 470 stores programs, modules, and data structures similar to those in the memory 202 of the portable multifunction device 200, or subsets thereof. Additionally, the memory 470 optionally stores additional programs, modules, and data structures not present in the memory 202 of the portable multifunction device 200. For example, the memory 470 of the device 400 optionally stores a drawing module 480, a rendering 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 portable multifunction device 200 ( Figure 2A The memory 202 optionally does not store these modules.

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

[0157] Now let’s turn our attention to implementations of user interfaces that can be implemented, for example, on a portable multi-functional device 200.

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

[0159] Signal strength indicator 502 for wireless communications such as cellular signals and Wi-Fi signals;

[0160] Time 504;

[0161] Bluetooth indicator 505;

[0162] • Battery status indicator 506;

[0163] • Tray 508 with icons of commonly used applications, such as:

[0164] ○ The telephone module 238 has an icon 516 labeled "telephone", which optionally includes an indicator 514 indicating the number of missed calls or voicemails;

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

[0166] ○ The icon 520 labeled "Browser" in browser module 247; and

[0167] ○ The icon 522 labeled "iPod" for the video and music player module 252 (also known as the iPod (a trademark of Apple Inc.) module 252); and

[0168] • Icons of other applications, such as:

[0169] ○The icon 524 labeled "Message" in IM module 241;

[0170] ○ The icon 526 labeled "Calendar" in calendar module 248;

[0171] ○ The icon 528 labeled "Photo" in the image management module 244;

[0172] ○ The icon 530 of camera module 243, which is labeled "camera";

[0173] ○ The icon 532 of the online video module 255, which is marked as "Online Video";

[0174] ○ The icon labeled "Stock Market" in the Stock Market Desktop Mini Program 249-2;

[0175] ○ Map module 254's icon 536 labeled "Map";

[0176] ○ The icon labeled "Weather" in the Weather desktop mini-program 249-1 is 538;

[0177] ○ The icon labeled "Clock" in the alarm clock desktop mini-program 249-4;

[0178] ○ The icon 542 labeled "Fitness Support" in the Fitness Support module 242;

[0179] ○ The icon 544 labeled "Notepad" in Notepad module 253; and

[0180] ○ An icon 546 labeled "Settings" is used to set applications or modules, providing access to settings for device 200 and its various applications 236.

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

[0182] Figure 5B A touch-sensitive surface 551 (e.g., separate from the display 550 (e.g., touchscreen display 212)) is shown. Figure 4 Devices (e.g., tablets or touchpads 455) Figure 4An exemplary user interface on device 400. Device 400 also optionally includes one or more contact intensity sensors (e.g., one or more sensors in sensor 459) for detecting the intensity of contact on tactile surface 551 and / or one or more tactile output generators 457 for generating tactile output for the user of device 400.

[0183] While some examples of input on a reference touchscreen display 212 (which combines a touch-sensitive surface and a display) are given in the following examples, in some implementations, the device detects input on a touch-sensitive surface separate from the display, such as... Figure 5B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 5B 551) has a spindle (e.g., on the display (e.g., 550) that is aligned with the main axis on the display (e.g., Figure 5B The spindle corresponding to 553 in the figure (e.g., Figure 5B (552 in the example). According to these embodiments, the device detects the position corresponding to the corresponding position on the display (e.g., in the example). Figure 5B In the middle, 560 corresponds to 568 and 562 corresponds to 570) the contact with the touch-sensitive surface 551 at the location (e.g., Figure 5B (560 and 562 in the example). Thus, on touch-sensitive surfaces (e.g., Figure 5B 551 in the middle) and the display of a multi-functional device (e.g., Figure 5B When 550 is separated from 560, user input detected by the device on the touch-sensitive surface (e.g., contact with 560 and 562 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may be optionally used for other user interfaces described herein.

[0184] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0185] Figure 6AAn exemplary personal electronic device 600 is illustrated. Device 600 includes a body 602. In some embodiments, device 600 includes components relative to devices 200 and 400 (e.g., Figures 2A-4 Some or all of the features described herein. In some embodiments, device 600 has a touch-sensitive display 604, hereinafter referred to as touchscreen 604. As an alternative to or complement to touchscreen 604, device 600 has a display and a touch-sensitive surface. Similar to devices 200 and 400, in some embodiments, touchscreen 604 (or touch-sensitive surface) has one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). The one or more intensity sensors of touchscreen 604 (or touch-sensitive surface) provide output data representing the intensity of the touch. The user interface of device 600 responds to touches based on touch intensity, meaning that touches of different intensities may invoke different user interface operations on device 600.

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

[0187] In some embodiments, device 600 has one or more input mechanisms 606 and 608. Input mechanisms 606 and 608 (if included) are physical in form. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 600 has one or more attachment mechanisms. Such attachment mechanisms (if included) allow device 600 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 600.

[0188] Figure 6BAn exemplary personal electronic device 600 is illustrated. In some embodiments, device 600 includes information about... Figure 2A , Figure 2B and Figure 4 Some or all of the aforementioned components. Device 600 has a bus 612 that operatively couples I / O portion 614 to one or more computer processors 616 and memory 618. I / O portion 614 is connected to display 604, which may have touch-sensitive component 622 and optionally also has touch intensity-sensitive component 624. Furthermore, I / O portion 614 is connected to 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.

[0189] In some examples, the input mechanism 608 is a microphone. The 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.

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

[0191] As used herein, the term "power indication" refers, for example, in devices 200, 400, 600, 800 and / or 900 (… Figure 2A , Figure 4 , Figures 6A to 6B , Figures 8A to 8G , Figures 9A to 9G A graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each constitute a display representation.

[0192] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some specific implementations that include a cursor or other positional marker, the cursor acts as a "focus selector," such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 4 The touchpad 455 or Figure 5B When an input (e.g., a press input) is detected on the touch-sensitive surface 551 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of direct interaction with user interface elements on a touchscreen display) that enable direct interaction with user interface elements on the touchscreen display. Figure 2A The touch-sensitive display system 212 or Figure 5A In some embodiments of the touchscreen 212, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user-expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0193] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected over a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted, before or after contact begins to move, before contact ends, before or after contact intensity is detected to increase and / or before or after contact intensity decreases). The characteristic 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 when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether a user has performed an action. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abort performing the corresponding action), rather than to determine whether to perform the first or second action.

[0194] In some implementations, a portion of the gesture is identified to determine the characteristic intensity. For example, a touch-sensitive surface receives a series of swipes that transition from a starting position to an ending position, where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the ending position is based only on a portion of the series of swipes, rather than the entire swipe (e.g., the swipe contact is only the portion at the ending position). In some implementations, a smoothing algorithm is applied to the intensity of the swipe contact before determining its characteristic intensity. For example, the smoothing algorithm optionally includes one or more of the following: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0195] 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 performs an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

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

[0197] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0198] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the press input intensity threshold). Therefore, in some implementations, a 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 that contact below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some implementations, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and optionally the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and a corresponding operation is performed in response to detecting a press input (e.g., an increase or decrease in contact intensity depending on the environment).

[0199] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0200] 3. Digital Assistant System

[0201] Figure 7A Block diagrams of digital assistant systems 700 according to various examples are shown. In some examples, the digital assistant system 700 is implemented on a standalone computer system. In some examples, the digital assistant system 700 is distributed across multiple computers. In some examples, some of the modules and functions of the digital assistant are divided into server and client parts, wherein the client part resides on one or more user devices (e.g., devices 104, 122, 200, 400, 600, 800, or 900) and communicates with the server part (e.g., server system 108) via one or more networks, for example, as... Figure 1 As shown in the image. In some examples, the digital assistant system 700 is... Figure 1 The specific implementation of the server system 108 (and / or DA server 106) shown is illustrated. It should be noted that the digital assistant system 700 is merely an example of a digital assistant system, and the digital assistant system 700 may have more or fewer components than shown, combine two or more components, or have different configurations or layouts of components. Figure 7A The various components shown are implemented in hardware, software instructions for execution by one or more processors, firmware (including one or more signal processing integrated circuits and / or application-specific integrated circuits), or a combination thereof.

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

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

[0204] In some examples, I / O interface 706 couples input / output devices 716 of digital assistant system 700, such as a display, keyboard, touchscreen, and microphone, to user interface module 722. I / O interface 706, together with user interface module 722, receives user input (e.g., voice input, keyboard input, touch input, etc.) and processes this input accordingly. In some examples, such as when the digital assistant is implemented on a standalone user device, digital assistant system 700 includes information about… Figure 2A , Figure 4 , Figures 6A to 6B , Figures 8A to 8G and Figures 9A to 9G Any of the components and I / O communication interfaces described in devices 200, 400, 600, 800, or 900. In some examples, digital assistant system 700 represents the server portion of a digital assistant implementation and can interact with the user through a client-side portion located on a user device (e.g., device 104, 200, 400, 600, 800, or 900).

[0205] In some examples, the network communication interface 708 includes one or more wired communication ports 712 and / or wireless transmission and reception circuitry 714. The one or more wired communication ports receive and 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 the communication network and other communication devices, and transmits RF signals and / or optical signals to the communication network and other communication devices. Wireless communication uses any of a variety of communication standards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA, Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communication protocol. The network communication interface 708 enables the digital assistant system 700 to communicate with other devices via networks such as the Internet, intranets, and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs).

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

[0207] Operating systems 718 (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OS X, WINDOWS, or embedded operating systems such as VxWorks) include various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitate communication between various hardware, firmware, and software components.

[0208] 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 electronic devices (such as those in…) Figure 2A , Figure 4 , Figures 6A to 6B The device 200, 400, or 600 shown communicates with the RF circuit 208. The communication module 720 also includes various components for processing data received by the wireless circuit 714 and / or the wired communication port 712.

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

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

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

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

[0213] In some examples, such as Figure 7B As shown, the I / O processing module 728 can... Figure 7A The I / O device 716 in the middle interacts with the user or through Figure 7AThe network communication interface 708 interacts with user equipment (e.g., device 104, device 200, device 400, or device 600) to receive user input (e.g., voice input) and provide a response to the user input (e.g., as voice output). The I / O processing module 728 optionally obtains contextual information associated with the user input from the user equipment along with or shortly after receiving the user input. Contextual information includes user-specific data, vocabulary, and / or preferences associated with the user input. In some examples, the contextual information also includes the software and hardware states of the user equipment 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 a 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 a speech recognizer) for speech-to-text conversion.

[0214] STT processing module 730 includes one or more ASR systems 758. The one or more ASR systems 758 can process speech input received through I / O processing module 728 to produce recognition results. Each ASR system 758 includes a front-end speech preprocessor. The front-end speech preprocessor extracts representative features from the speech input. For example, the front-end speech preprocessor performs a Fourier transform on the speech input to extract spectral features characterizing the speech input as a sequence of representative multidimensional 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 grammar language models, and other statistical models. Examples of speech recognition engines include engines based on Dynamic Time Warping (VTW) and engines based on Weighted Finite State Transformers (WFST). One or more speech recognition models and one or more speech recognition engines are used to process the representative features extracted by the front-end speech preprocessor to produce intermediate recognition results (e.g., phonemes, phoneme strings, and sub-words) and ultimately produce text recognition results (e.g., words, word strings, or symbol sequences). In some examples, the speech input is processed at least in part by a third-party service or on the user's device (e.g., device 104, device 200, device 400, or device 600) to produce the recognition results. Once the STT processing module 730 produces a recognition result containing a text string (e.g., words, or sequences of words, or sequences of symbols), the recognition result is passed to the natural language processing module 732 for intent inference. In some examples, the STT processing module 730 produces 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. Alternatively, the five highest-ranked (n=5) candidate text representations are passed to the natural language processing module 732 for intent inference.

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

[0216] In some examples, the STT processing module 730 includes a vocabulary of recognizable words and / or accesses that vocabulary via the speech-to-letter conversion module 731. Each vocabulary word is associated with one or more candidate pronunciations of a word represented in the speech recognition alphabet. Specifically, the vocabulary of recognizable words includes words associated with multiple candidate pronunciations. For example, the vocabulary includes words associated with... and The candidate pronunciations are associated with the word "tomato". Additionally, vocabulary words are associated with custom candidate pronunciations based on previous speech input from the user. These custom candidate pronunciations are stored in the STT processing module 730 and associated with a specific user via a user profile on the device. In some examples, candidate pronunciations 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, for example, based on known standard pronunciations.

[0217] In some examples, candidate pronunciations are ranked based on their prevalence. For example, candidate pronunciations... The ranking is higher than This is because the former is a more commonly used pronunciation (e.g., among all users, for users in a specific geographic region, or for any other suitable subset of users). In some examples, candidate pronunciations are ranked based on whether they are custom candidate pronunciations associated with a user. For example, custom candidate pronunciations rank higher than standard candidate pronunciations. This can be used to identify proper nouns with unique pronunciations that deviate from the canonical pronunciation. In some examples, candidate pronunciations are associated with one or more phonological features such as geographic origin, country, or ethnicity. For example, candidate pronunciations... Associated with the United States, and candidate pronunciation The candidate pronunciations are associated with the United Kingdom. Furthermore, 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's association with the United States, candidate pronunciations... (US-related) Comparable candidate pronunciations (Related to the UK) It ranks higher. In some examples, one of the ranked candidate pronunciations can be selected as the predicted pronunciation (e.g., the most likely pronunciation).

[0218] Upon receiving voice input, the STT processing module 730 is used (e.g., using a sound model) to determine the phonemes corresponding to the voice input, and then attempts (e.g., using a language model) to determine the words that match those phonemes. For example, if the STT processing module 730 first identifies a sequence of phonemes corresponding to a portion of the voice input... It can then determine, based on vocabulary index 744, that the sequence corresponds to the word "tomato".

[0219] In some examples, the STT processing module 730 uses fuzzy matching techniques to determine words in a utterance. Therefore, for example, the STT processing module 730 determines phoneme sequences. This corresponds to the word "tomato," even if the specific phoneme sequence is not a candidate phoneme sequence for that word.

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

[0221] 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, contextual information associated with the user request from the I / O processing module 728. The natural language processing module 732 optionally uses the contextual information to clarify, supplement, and / or further define the information contained in the candidate text representation received from the STT processing module 730. Contextual information includes, for example, user preferences, the hardware and / or software state of the user's device, sensor information collected before, during, or shortly after the user request, previous interactions (e.g., conversations) between the digital assistant and the user, and so on. As described herein, in some examples, the contextual information is dynamic and varies with the time, location, content, and other factors of the conversation.

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

[0223] 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 via one or more intermediate attribute nodes. Similarly, each attribute node is directly connected to or connected to one or more executable intent nodes via one or more intermediate attribute nodes. For example, as... Figure 7C As shown, knowledge ontology 760 includes a "Restaurant Reservation" node (i.e., an executable intent node). The attribute nodes "Restaurant", "Date / Time" (for reservations) and "Party Attendees" are all directly connected to the executable intent node (i.e., the "Restaurant Reservation" node).

[0224] Furthermore, the attribute nodes "Cuisine," "Price Range," "Phone Number," and "Location" are child nodes of the attribute node "Restaurant," and all are connected to the "Restaurant Reservation" node (i.e., the executable intent node) through the intermediate attribute node "Restaurant." For example, ... Figure 7C As shown, knowledge ontology 760 also includes a "Set Reminder" node (i.e., another executable intent node). The attribute nodes "Date / Time" (for setting reminders) and "Topic" (for reminders) are both connected to the "Set Reminder" node. Since the attribute "Date / Time" is related to both the task of making a restaurant reservation and the task of setting a reminder, the attribute node "Date / Time" is connected to both the "Restaurant Reservation" node and the "Set Reminder" node in knowledge ontology 760.

[0225] An executable intent node, along with its linked attribute nodes, is described as a "domain." In this discussion, each domain is associated with a corresponding executable intent and refers to a set of nodes (and the relationships between these nodes) associated with a particular executable intent. For example, Figure 7CThe knowledge ontology 760 shown includes examples of a restaurant reservation domain 762 and a reminder domain 764 within the knowledge ontology 760. The restaurant reservation domain includes an actionable intent node “Restaurant Reservation”, attribute nodes “Restaurant”, “Date / Time”, and “Participant Size”, and sub-attribute nodes “Cuisine”, “Price Range”, “Phone Number”, and “Location”. The reminder domain 764 includes an actionable intent node “Set Reminder” and attribute nodes “Topic” and “Date / Time”. In some examples, the knowledge 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 associated with many different domains (e.g., itinerary domain, travel booking domain, movie ticket domain, etc.).

[0226] although Figure 7C Two exemplary fields within knowledge ontology 760 are shown, but other fields include, for example, “Find a movie,” “Initiate a phone call,” “Find directions,” “Schedule a meeting,” “Send a message,” and “Provide answers to questions,” “Reading lists,” “Provide navigation instructions,” “Provide instructions for a task,” etc. The “Send a message” field 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 “Recipients” is further defined, for example, by sub-attribute nodes such as “Recipient name” and “Message address.”

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

[0228] In some examples, nodes associated with multiple related executable intents are clustered under a “superdomain” in knowledge ontology 760. For example, the “Travel” superdomain includes clusters of travel-related attribute nodes and executable intent nodes. Travel-related executable intent nodes include “flight booking,” “hotel booking,” “car rental,” “route planning,” “finding points of interest,” and so on. Executable intent nodes under the same superdomain (e.g., the “Travel” superdomain) have multiple shared attribute nodes. For example, executable intent nodes for “flight booking,” “hotel booking,” “car rental,” “get route,” and “finding points of interest” share one or more of the attribute nodes “starting location,” “destination,” “departure date / time,” “arrival date / time,” and “party size.”

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

[0230] Natural Language Processing (NLP) module 732 receives candidate text representations (e.g., one or more text strings or one or more sequences of symbols) from STT processing module 730 and, for each candidate representation, determines which nodes the words in the candidate text representation relate to. In some examples, if a word or phrase in a candidate text representation is found to be associated with one or more nodes in knowledge ontology 760 (via lexical index 744), the word or phrase "triggers" or "activates" those nodes. Based on the number and / or relative importance of the activated nodes, NLP module 732 selects one executable intent as the task the user intends the digital assistant to perform. In some examples, the domain with the most "triggered" nodes is selected. In some examples, the domain with the highest confidence (e.g., based on the relative importance of its individual 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, such as whether the digital assistant has previously correctly interpreted similar requests from the user, are also considered in the node selection process.

[0231] User data 748 includes user-specific information such as user-specific vocabulary, user preferences, user address, user's default second language, user's contact list, and other short- 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 refine the user's intent. For example, in response to a user request "Invite my friends to my birthday party," the natural language processing module 732 can access user data 748 to determine who the "friends" are and when and where the "birthday party" will be held, without requiring the user to explicitly provide such information in their request.

[0232] It should be recognized that, in some examples, the natural language processing module 732 is implemented using one or more machine learning agencies (e.g., neural networks). Specifically, the one or more machine learning agencies are configured to receive candidate text representations and contextual information associated with the candidate text representations. Based on the candidate text representations and the associated contextual information, the one or more machine learning agencies are configured to determine an intent confidence score based on a set of candidate executable intents. The natural language processing module 732 can 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.

[0233] Further details regarding the symbol string-based search of knowledge ontology are described in U.S. Utility Model Patent Application Serial No. 12 / 341743, entitled "Method and Apparatus for Searching Using An Active Ontology," filed on December 22, 2008, the entire disclosure of which is incorporated herein by reference.

[0234] In some examples, once the natural language processing module 732 identifies an executable intent (or domain) based on a user request, it 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 these parameters are populated with specific information and requirements specified in the user request. For example, a user says, “Reserve a table at a sushi restaurant for 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}, etc. In some examples, based on voice input and text derived from the voice input using the STT processing module 730, the natural language processing module 732 generates a 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 a structured query associated with the domain. Therefore, based on the currently available information, no other necessary parameters such as {number of people at the party} and {date} are specified in the structured query. In some examples, the natural language processing module 732 uses the received context information to populate some parameters of the structured query. For example, in some examples, if a user requests a "nearby" sushi restaurant, the natural language processing module 732 uses GPS coordinates from the user's device to populate the {location} parameter in the structured query.

[0235] In some examples, the Natural Language Processing (NLP) 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 entirely) is generated for each identified candidate executable intent. The NLP 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 NLP module 732 transmits one or more of the 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., the m highest-ranked) candidate executable intents are provided to the task flow processing module 736, where m is a predetermined integer greater than zero. In some examples, one or more structured queries for the m best candidate executable intents, along with corresponding one or more candidate text representations, are provided to the task flow processing module 736.

[0236] Further details regarding the inference of user intent based on multiple candidate executable intents determined from multiple candidate text representations of speech input are described in U.S. Utility Model Patent Application Serial No. 14 / 298725, filed June 6, 2014, entitled “System and Method for Inferring UserIntent From Speech Inputs,” the entire disclosure of which is incorporated herein by reference.

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

[0238] As described above, to complete a structured query, the task flow processing module 736 needs to initiate additional dialogue with the user to obtain additional information and / or clarify potentially ambiguous statements. When such interaction is necessary, the task flow processing module 736 invokes the dialogue flow processing module 734 to participate in the dialogue with the user. In some examples, the dialogue flow processing module 734 determines how (and / or when) to request additional information from the user and receives and processes the user's response. The I / O processing module 728 presents questions to the user and receives answers from the user. In some examples, the dialogue flow processing module 734 presents dialogue output to the user via audible and / or visual output and receives input from the user via verbal or physical (e.g., click) responses. Continuing with the above example, when the task flow processing module 736 invokes the dialogue flow processing module 734 to determine the "party size" and "date" information for a structured query associated with the domain "restaurant reservation," the dialogue flow processing module 734 generates questions such as "How many people in a row?" and "Which day to book?" and presents them to the user. Once a response is received from the user, the dialogue flow processing module 734 either fills the structured query with the missing information or passes the information to the task flow processing module 736 to complete the missing information based on the structured query.

[0239] Once the task flow processing module 736 has completed a structured query for the executable intent, it begins executing the final task associated with the executable intent. Therefore, the task flow processing module 736 executes the steps and instructions in the task flow model based on the specific parameters contained in the structured query. For example, the task flow model for the executable intent "restaurant reservation" includes steps and instructions for contacting the restaurant and actually requesting a reservation for a specific number of people at a specific time for a specific party. For example, using a structured query such as: {restaurant reservation, restaurant = ABC Cafe, date = 3 / 12 / 2012, time = 7pm, number of people = 5}, the task flow processing module 736 can perform the following steps: (1) log in to ABC Cafe's server or such The restaurant reservation system, (2) inputs date, time and party number information on the website, (3) submits the form, and (4) creates a calendar entry for the reservation in the user's calendar.

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

[0241] For example, if a restaurant has enabled an online reservation service, it submits a service model that specifies the necessary parameters for making a reservation and the values ​​of those parameters to be sent to the online reservation service's API. 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 reservation parameters (e.g., time, date, number of party members) to the online reservation interface in a format appropriate to the online reservation service's API.

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

[0243] 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 a 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-ranking executable intent. In other examples, the first structured query is selected from structured queries received based on a combination of the corresponding speech recognition confidence score and the corresponding intent confidence score. In some examples, if the task flow processing module 736 encounters an error during the processing of the first structured query (e.g., due to the inability to determine necessary parameters), the task flow processing module 736 may continue to select and process a second structured query from the received structured queries that corresponds to a lower-ranking executable intent. For example, the second structured query may be selected based on the speech recognition confidence score of the corresponding candidate text representation, the intent confidence score of the corresponding candidate executable intent, missing necessary parameters in the first structured query, or any combination thereof.

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

[0245] In some examples, instead of using a speech synthesis processing module 740 (or other alternatives), speech synthesis is performed on a remote device (e.g., server system 108), and the synthesized speech is sent to a user device for output to the user. For example, this could occur in some implementations where the output of a digital assistant is generated at the server system. And since server systems typically have greater processing power or more resources than user devices, they are likely to achieve higher quality speech output than client-side synthesis would achieve.

[0246] Additional details regarding digital assistants can be found in U.S. Utility Model Patent Application No. 12 / 987982, filed January 10, 2011, entitled “Intelligent Automated Assistant,” and U.S. Utility Model Patent Application No. 13 / 251088, filed September 30, 2011, the entire disclosure of which is incorporated herein by reference.

[0247] 4. Authentication of accessory-based devices for digital assistant requests

[0248] You might not want your digital assistant (DA) running on your electronic device to handle certain requests when the device is locked. For example, you might not want the DA to handle task requests that include accessing and / or providing personal and / or private information stored on the device. As a specific example, when the device is locked, you might not want the DA to output or modify information corresponding to the user's text messages, emails, health, finances, home security, etc. Therefore, you might need the user to unlock the device so that the DA can handle such task requests.

[0249] Unlocking a device may require physical interaction between the user and the device, such as entering a password or providing biometric authentication data. However, sometimes, when physical interaction is inconvenient and / or impractical (e.g., when the device is in the user's bag, while the user is driving, or when unlocking the device requires the user to remove a mask to provide biometric data), the user may wish to issue a task request to the DA (Data Authentication Authority). Therefore, it may be desirable to authenticate the device to handle the DA request without requiring the user to unlock the device.

[0250] Figures 8A to 8G Techniques for authenticating device 800 using accessory device 900 to process DA requests are illustrated according to various examples. In some examples, device 800 is implemented as device 200, 400, or 600. In some examples, accessory device 900 is implemented as another instance of device 200, 400, or 600.

[0251] exist Figures 8A to 8GIn the examples, accessory device 900 is implemented as a wearable device (e.g., a smartwatch), and device 800 is implemented as a smartphone. However, accessory device 900 and device 800 can each be implemented as any type of electronic device, such as a smartphone, wearable device (e.g., earphones, smartwatches, head-mounted devices), laptop computer, desktop computer, tablet device, smart speaker, television, smart home appliance, etc. In some examples, accessory device 900 and device 800 are different types of electronic devices. In other examples, accessory device 900 and device 800 are the same type of electronic device.

[0252] exist Figure 8A In the device 800, the memory 802 at least partially implements the DA module 726, as per [reference to...]. Figures 7A to 7C As an example, the components and functions of DA module 726 are implemented entirely on device 800. As another example, the components and functions of DA module 726 are divided between device 800 and other devices (e.g., DA server 106 and / or accessory device 900).

[0253] The memory 802 further implements the authentication module 804. As discussed below, the authentication module 804 includes executable instructions for enabling the device 800 to authenticate itself to process DA requests (e.g., using the accessory device 900 and when the device 800 is in a locked state).

[0254] The memory 902 of the accessory device 900 implements the authentication module 904. As discussed below, the authentication module 904 includes executable instructions for enabling the accessory device 900 to authenticate the device 800 to process digital DA requests.

[0255] In some examples, to enable accessory device 900 to authenticate device 800 for DA requests, device 800 communicates with accessory device 900. For example, device 800 and accessory device 900 are coupled via a wired or wireless connection that enables data exchange. Any suitable communication protocol of any type can be used to implement the wired or wireless connection, such as Bluetooth, Wi-Fi, Ethernet, NFC, USB, cellular communication, fiber optic cable communication, etc.

[0256] In Figure 8BIn this context, while device 800 is in a locked state (locked) and before receiving natural language input including a request for DA, device 800 receives user input corresponding to the request to initiate DA. Examples of such user input include verbally triggered expressions (e.g., “Hey Siri”), user selection of buttons on device 800 or power indications displayed by device 800, and input received via an external electronic device (e.g., earphones) communicatively coupled to device 800. In response to receiving user input, device 800 initiates a DA session. For example, device 800 displays a DA user interface (e.g., including DA indicator 806) and / or puts DA into listening mode to sample natural language input.

[0257] exist Figure 8B In this scenario, while device 800 is locked and communicating with accessory device 900, device 800 receives natural language input, such as "Read my latest messages." In some examples, device 800 receives natural language input based on initiating a DA session. As discussed, it may not be desirable for DA to fulfill requests (e.g., by reading user messages) without device 800 being unlocked or otherwise authenticated.

[0258] In some examples, such as when device 800 is locked, device 800 determines whether the natural language input corresponds to a security task request. A security task request describes a task that DA would not normally be able to perform when device 800 is locked (e.g., unless device 800 is unlocked or authenticated via other means described below). For example, fulfilling a security task request includes retrieving and / or modifying a user's personal data. Example personal data includes a user's contact data, email data, message data, calendar data, reminder data, photos, videos, health information, financial information, web search history, media data (e.g., songs and audiobooks), information related to the user's home (e.g., the status of the user's home appliances and home security systems, home security system access information), and any other sensitive and / or private information that the user may not wish to expose to other users or devices. Example security task requests include "Read my latest messages," "How many calories did I burn today?", "Open my front door," "Pay $100 to Brandon," "What's next on my schedule?", "Directions home," "Show me the last photo I took," and so on.

[0259] In contrast, non-secure task requests describe task requests that the DA can perform regardless of whether device 800 is unlocked or otherwise authenticated. Therefore, whether a task request corresponds to a secure task request can depend on the type of task device 800 allows the DA to perform while device 800 is locked, and thus can vary based on the device 800's settings or implementation. For example, if device 800 allows the DA to make phone calls to user contacts while device 800 is locked, then a phone call task request corresponds to a non-secure task request. However, if device 800 prohibits the DA from making phone calls to user contacts while device 800 is locked, then a phone call task request corresponds to a secure task request. Example non-secure task requests include informational task requests such as "What's the weather like in Palo Alto?", "How old is Taylor Swift?", "What's the score of the Giants game?", "What time is it?", and requests to set alarms or timers.

[0260] In some examples, determining whether natural language input corresponds to a security task request includes basing decisions on the natural language input (e.g., regarding...). Figures 7A to 7C The task discussed here refers to determining whether the task corresponds to a secure task request or a non-secure task request. In some examples, determining that the natural language input corresponds to a secure task request includes determining that the natural language input corresponds to a personal domain, such as a domain associated with an operational intent to retrieve and / or modify personal data.

[0261] exist Figure 8B In the example, device 800 determines that the natural language input "Read my latest messages" corresponds to a security task request. For example, device 800 determines that fulfilling the task of reading the user's messages requires providing the user's personal and private data, such as messages.

[0262] In some examples, based on determining that the natural language input corresponds to a security task request, device 800, when device 800 is locked, determines (e.g., using authentication module 804) whether one or more states of accessory device 900 meet a set of authentication criteria. In some examples, meeting a set of authentication criteria requires accessory device 900 to be physically associated with a user of device 800, such as being worn by a user or within a predetermined distance of the user and / or device 800. Example states of accessory device 900 include the setting of accessory device 900, whether accessory device 900 is currently unlocked, whether accessory device 900 is protected by a password or other security mechanism (e.g., requiring biometric authentication to unlock), movement of accessory device 900, distance of accessory device 900 from device 800 (e.g., determined using sensors of device 800 and / or accessory device 900 implementing ranging technology and / or based on signals (e.g., received signal strength indication (RSSI) received from accessory device 900)), whether accessory device 900 is currently worn by a user, and whether accessory device 900 was recently (e.g., within a predetermined duration prior to the current time).

[0263] Examples of states in which accessory device 900 meets a set of authentication criteria include: accessory device 900 is configured to enable authentication of device 800 for DA requests; accessory device 900 is currently unlocked; accessory device 900 is protected by a password or other security mechanism; movement of accessory device 900 corresponds to a predetermined type of movement (e.g., movement consistent with movement worn on a user's wrist, head, or other body part); accessory device 900 is within a predetermined distance from the user or device 800; accessory device 900 is currently worn by the user; and accessory device 900 was recently unlocked. In some examples, accessory device 900 meets a set of authentication criteria if one or more of the above states meet the corresponding authentication criteria. In some examples, accessory device 900 does not meet a set of authentication criteria if one or more of the above states do not meet the corresponding authentication criteria (e.g., if accessory device 900 is locked; if accessory device 900 is not protected by a password or other security mechanism; and / or if accessory device 900 is not worn). U.S. Provisional Patent Application No. 63 / 141354, filed January 25, 2021, entitled “IMPLEMENTATION OF BIOMETRICAUTHENTICATION,” further discusses determining whether the status of an accessory device meets a set of certification criteria, and is incorporated herein by reference in its entirety.

[0264] In some examples, determining whether the state of accessory device 900 meets a set of authentication criteria includes device 800 sending an authentication request to accessory device 900. In some examples, upon receiving the authentication request, accessory device 900 determines (e.g., using authentication module 904) whether its state meets a set of authentication criteria and sends a determined indication (e.g., whether accessory device 900 authenticates device 800) to device 800. Upon receiving this indication (e.g., authenticated or unauthenticated), device 800 determines whether the state of accessory device 900 meets a set of authentication criteria.

[0265] In other examples, device 800 sends an information request to accessory device 900 corresponding to the status of accessory device 900 (e.g., a status related to the authentication of device 800). In some examples, upon receiving this information request, accessory device 900 determines the information (e.g., using authentication module 904) and sends the information to device 800. Upon receiving the information, device 800 locally determines (e.g., using authentication module 804) whether the status of accessory device 900 meets the set of authentication criteria.

[0266] In some examples, if it is determined that the natural language input does not correspond to a security task request and the device 800 is locked, the device 800 initiates a task corresponding to the natural language input without determining whether the state of the accessory device 900 meets the authentication criteria. In some examples, the device 800 further provides an output indicating the initiated task. For example, if the natural language input is “What’s the weather like in Palo Alto?” (a non-security task request), the device 800, while locked, initiates a task to retrieve weather information for Palo Alto, California, and provides that information, such as “The temperature in Palo Alto is currently 70 degrees Celsius, and it’s sunny.” Therefore, the device 800 can selectively determine whether to authenticate itself using the accessory device 900 based on whether the natural language input corresponds to a security task request. This advantageously prevents the device 800 from authenticating itself unnecessarily (e.g., for non-security task requests), thereby reducing the DA response time and processing power consumed by authentication. Furthermore, the device 800 can authenticate itself when needed, thereby improving device security.

[0267] exist Figure 8B In the example, device 800 determines that the state of accessory device 900 meets a set of authentication criteria. For example, device 800 determines that accessory device 900 is currently being worn, currently unlocked, and currently within a predetermined distance of device 800.

[0268] exist Figure 8C In the process, based on the determination that one or more states of the accessory device 900 meet a set of authentication criteria, device 800 initiates a security task corresponding to the natural language input (e.g., regarding...). Figures 7A to 7C The device 800 further provides an output 808 indicating the initiated security task. For example, when the device 800 is locked, the device initiates a security task to read the user's recent messages and outputs (e.g., display and / or speak recent messages, such as "Your husband said 'When are you coming home from get off work?'")

[0269] In some examples, such as Figure 8C As shown, the output 808 indicating the initiated security task includes security output. Unless device 800 is authenticated using other means (e.g., using accessory device 900), security output describes outputs that device 800 does not provide when device 800 is locked. Therefore, similar to a security task request, whether an output corresponds to security output can depend on the settings or implementation of device 800. In some examples, security output includes outputs indicating the user's personal data (e.g., the user's text messages, health information, financial information, etc.) on device 800.

[0270] In some examples, based on the determination that the state of the accessory device 900 meets a set of authentication criteria and when the device 800 is locked, the device 800 causes (e.g., using authentication module 804) the accessory device 900 to provide an output 906 indicating the initiation of a security task. For example, Figure 8C Accessory device 900 provides (e.g., displays) output 906, "Telephone Response Message Request". In some examples, device 800 provides output 906 simultaneously with output 808. In some examples, output 906 indicates the type of security task (e.g., messaging task, email task, calendar task, health-related task, etc.). In some examples, output 906 indicates a security task used by accessory device 900 to authenticate device 800. For example, output 906 further includes "Message Request to Authenticate Telephone Using Watch". Therefore, providing output 906 provides the user with visual feedback about the status of devices 800 and 900, such as whether device 800 is currently processing a security task request and / or authenticating a security task request using accessory device 900.

[0271] In some examples, output 906 includes a prompt 908 for the user to cancel the initiated security task. In some examples, the user selects (e.g., via touch input, voice input, or other input methods) prompt 908, and in response, the accessory device 900 sends an indication of the user selection of prompt 908 to device 800. Upon receiving the indication of the user selection of prompt 908, device 800 terminates the security task. For example, if device 800 is initiating a security task (e.g., performing a procedure to satisfy the security task) but has not yet caused the execution of the security task (e.g., no output is provided to the user, no action is taken), when the indication of the user selection of prompt 908 is received, then device 800 stops initiating the security task and abandons providing any output indicating the initiated security task, such as when device 800 is locked. As another example, if device 800 is currently providing output indicating the initiated security task (e.g., currently reading the user's latest message) when the indication of the user selection of prompt 908 is received, then device 800 stops providing output, such as when device 800 is locked. As another example, if device 800 has already performed a security task (e.g., unlocking a door, deleting a photo) when it receives the instruction from user selection prompt 908, then device 800 performs a task to undo or revert the performed task (e.g., relocking the door, restoring the photo), for example, when device 800 is locked.

[0272] In some examples, based on the determination that the state of the accessory device 900 meets a set of authentication criteria and when device 800 is locked, device 800 provides an output 810 instructing the use of the accessory device 900 to authenticate a security task of device 800. In some examples, device 800 provides output 810 simultaneously with an output 808 instructing the initiation of a security task; for example, output 810 is initially provided when output 808 begins and stops when output 810 stops. For example, in Figure 8C In the middle, while outputting the latest text message instructing the user, device 800 provides output 810 "Authenticate phone using watch".

[0273] In some examples, based on the determination that the state of accessory device 900 does not meet a set of authentication criteria and that device 800 is locked, device 800 provides output indicating that it cannot perform a security task while it is locked. For example, for Figure 8B If the user inputs "Read my latest messages" in natural language, device 800 will output "Sorry, I cannot do this while your device is locked." In some examples, the output will additionally or alternatively prompt the user to unlock device 800, such as "You need to unlock your device first."

[0274] In some examples, device 800 prevents DA from performing certain security tasks when device 800 is locked, even if device 800 can be authenticated using accessory device 900. For example, security tasks are categorized into Type I security tasks (tasks that can be performed when device 800 is locked and if device 800 is authenticated) and Type II security tasks (tasks that cannot be performed when device 800 is locked, regardless of whether device 800 is authenticated). Examples of Type II security tasks include tasks related to home security (e.g., reducing home security, such as unlocking doors, disabling alarms), tasks related to payments, and tasks related to launching applications. Examples of Type I security tasks include any other of the aforementioned security tasks that do not fall under Type II (e.g., reading messages, retrieving photos, modifying calendar information, retrieving or modifying health information). It should be understood that whether a security task is Type I or Type II can vary depending on the settings or implementation of device 800.

[0275] In some examples, determining whether natural language input corresponds to a security task request includes determining whether the security task is of type one or type two (e.g., using DA module 726). In some examples, determining whether the state of the accessory device 900 meets a set of authentication criteria is performed based on whether the security task is of type one. Therefore, before determining whether the accessory device 900 authenticates the device 800, the device 800 can first confirm that the DA is allowed to perform the requested security task if the device 800 is locked. This advantageously prevents the device 800 from consuming unnecessary processing resources to authenticate itself for security tasks that are not executable when it is locked.

[0276] In some examples, depending on whether the security task is determined to be of type II (a task that cannot be performed when device 800 is locked), device 800 provides output indicating that it cannot complete the security task while locked. For example, for the natural language input “pay Brandon $100” (corresponding to a type II security task), device 800 outputs “I cannot do this while your device is locked.” In some examples, the output additionally or alternatively prompts the user to unlock device 800, such as “You need to unlock your device first.”

[0277] In some examples, such as using accessory device 900 to authenticate device 800, device 800 may require additional security levels to initiate security tasks when device 800 is locked. Therefore, in some examples, determining whether natural language input corresponds to a security task request includes determining (e.g., using DA module 726) whether the security task is of a predetermined type (e.g., a security task requiring additional security levels). Example security tasks of predetermined types include security tasks corresponding to home security (e.g., reducing home security, such as unlocking doors and disarming alarms) and security tasks corresponding to payments.

[0278] In some examples, based on the determination that the security task is not a predetermined type, device 800 determines whether the status of the accessory device 900 meets a set of authentication criteria. If it does, device 800 initiates a security task, as discussed above.

[0279] In some examples, based on determining that the security task is a predetermined type, device 800 still determines whether the state of the accessory device 900 meets a set of authentication criteria. However, based on determining that the state of the accessory device 900 meets a set of authentication criteria, device 800 further determines (e.g., using authentication module 804) whether a set of security criteria for the security task is met. In some examples, the type of security criteria to be met depends on the type of security task. For example, for a security task corresponding to reducing the security of a user's home (e.g., unlocking a door, deactivating an alarm), device 800 determines whether it meets security criteria based on physical distance, such as whether device 800 is within a threshold distance of the user's home. For example, when natural language input corresponding to a security task request is received, if device 800 is within the threshold distance of the user's home, the set of security criteria is met; and when natural language input is received, if device 800 is not within the threshold distance of the user's home, the set of security criteria is not met. As another example, for a security task corresponding to a payment, device 800 determines whether it meets the security criteria based on the payee and / or based on the amount of the payment. For example, a payment request meets this set of security criteria if it is made to a recipient the user frequently or most recently makes payments to (e.g., most frequently made payment recipient, top n most frequently made payment recipients, most recently made payment recipients, top n most recently made payment recipients). Otherwise, it does not meet this set of security criteria. As another example, a payment request meets this set of security criteria if it is to pay an amount below a threshold (e.g., $50), and does not meet this set of security criteria if it is to pay an amount above the threshold.

[0280] In some examples, based on the determination that the set of security criteria is met (and based on the authentication of device 800 using accessory device 900), device 800 initiates a security task and provides output indicating the initiated security task when locked. For example, for the natural language input "Unlock my front door," device 800 determines that it has been authenticated using accessory device 900 and further determines that it is currently within a threshold distance of the user's home. Therefore, device 800 unlocks the user's front door and provides the output "Okay, I have unlocked your front door."

[0281] In some examples, if the set of security criteria is determined not to be met, device 800 provides output indicating that it cannot perform a security task while locked, such as "Sorry, I cannot do this while your device is locked." In some examples, the output additionally or alternatively prompts the user to unlock device 800.

[0282] Go to Figure 8D In some examples, natural language input may not correspond to a security task request, but fulfilling the requested task may require device 800 to provide secure output. For example, if natural language input requests DA to perform a non-secure task (e.g., initiating a phone call), but DA needs to provide output that elicits user input to clarify / eliminate ambiguity in the parameters of the secure task, then such output might be secure output (e.g., a list of user contacts to be called). In such examples, as described below, accessory device 900 can authenticate device 800 to provide secure output.

[0283] exist Figure 8D In this example, when device 800 is locked and communicating with accessory device 900, device 800 receives natural language input, such as "Call Mark". In this example, the natural language input does not correspond to a security task request, for example, because device 800 allows DA to initiate a telephone call while device 800 is locked.

[0284] In some examples, based on the determination that the natural language input does not correspond to a security task request and that device 800 is locked, device 800 determines (e.g., using DA module 726) whether fulfilling the requested task includes providing secure output. For example, DA module 726 determines whether the output generated by the dialogue stream processing module 734 includes personal data. In this example, fulfilling the requested task of calling “Mark” requires device 800 to provide secure output displaying multiple user contacts named “Mark” (e.g., “Mark Smith” and “Mark Zhao”). Based on the determination that fulfilling the requested task includes providing secure output, device 800 determines whether the status of the attached device 900 meets a set of authentication criteria, as discussed above.

[0285] In some examples, based on determining that the state of the accessory device 900 meets a set of authentication criteria, device 800 provides a secure output, for example, when device 800 is locked. Figure 8D In the process, after determining that satisfying the request to "call Mark" requires device 800 to provide output prompting the user to clear up ambiguity regarding which "Mark" to call, device 800 uses accessory device 900 to authenticate itself. After authenticating itself, device 800 provides security output, for example, by displaying and / or stating "Do you want to call Mark Smith or Mark Zhao?".

[0286] In some examples, based on the determination that the state of the accessory device 900 meets the set of authentication criteria, device 800 further enables (e.g., using authentication module 804) the accessory device 900 to provide an output 910 indicating the provision of a secure output. For example, in Figure 8D In some examples, accessory device 900 outputs (e.g., displays) "Telephone provides secure output". In some examples, output 910 further instructs accessory device 900 to authenticate the secure output of device 800, such as "Authenticate secure output of telephone using watch". In some examples, device 800 and accessory device 900 provide secure output simultaneously with output 910.

[0287] In some examples, after a security output is provided and while the electronic device is locked, device 800 receives user input in response to the security output. For example, in Figure 8D In this scenario, the user responds to the security output "Do you want to call MarkSmith or Mark Zhao?" by saying "Mark Zhao" (or providing other input to select "Mark Zhao"). In some examples, device 800 then initiates the requested task based on the user input, for example, initiating a call to "Mark Zhao" when device 800 is locked.

[0288] In some examples, if the status of the accessory device 900 is determined to be inconsistent with the set of authentication criteria, device 800 provides output indicating that it cannot complete the requested task. For example, device 800 outputs "You need to unlock your device and tell me which Mark to call".

[0289] In some examples, if it is determined that satisfying the requested task does not require providing a security output, device 800 initiates the task without authenticating itself using accessory device 900. For example, for a requested task to "call Mark", device 800 determines (e.g., using DA module 726) that the user has only one contact named "Mark", and therefore no security output is needed to elicit user input to dispel ambiguity for "Mark". Therefore, when locked, device 800 initiates the task to call "Mark" without authenticating itself using accessory device 900.

[0290] Go to Figure 8E In some examples, device 800 maintains authentication as long as the current DA session is active (e.g., not deactivated). In some examples, the current DA session is active when the DA user interface is displayed (e.g., including DA indicator 806), and is deactivated (disabled) when the DA user interface stops displaying, and optionally when the process and / or thread corresponding to the DA stops executing on device 800. Therefore, in some examples, device 800 does not re-authenticate itself using the attached device 900 to handle multiple security task requests while the DA user interface is displayed.

[0291] exist Figure 8E In the process, when device 800 is locked and communicating with accessory device 900, device 800, for example, according to the following... Figure 8B The discussion describes initiating a DA session to receive natural language input. Device 800 determines that the natural language input (e.g., “What’s next on my schedule?”) corresponds to a security task, and therefore determines whether the state of the accessory device 900 meets a set of authentication criteria. Based on the determination that the state of the accessory device 900 meets that set of authentication criteria (e.g., initially authenticating itself), device 800 initiates a security task and provides output indicating the initiated security task during the initiated digital assistant session, for example, when device 800 is locked. For example, in Figure 8E In the context of the DA user interface (e.g., DA indicator 806) being displayed and the device 800 being locked, the device 800 outputs "You have a meeting with your boss at 1 p.m.".

[0292] exist Figure 8EIn the process of locking device 800, during the initiated DA session, and after providing output indicating the initiated security task, device 800 receives second natural language input corresponding to a request to perform a second security task on device 800. For example, while DA indicator 806 remains displayed, device 800 receives the second natural language input "Turn on the front porch light". Based on the received second natural language input (and during the initiated DA session), device 800 initiates the second security task without needing to re-authenticate itself. During the initiated DA session, device 800 further provides output indicating the initiated second security task, such as "Okay, I have turned on the front porch light".

[0293] exist Figure 8F In this scenario, the initiated DA session is terminated when device 800 is locked and after output indicating the initiation of a second security task is provided. For example, the DA user interface, including DA indication identifier 806, stops displaying, and the process and / or thread corresponding to the DA stops executing on device 800. In some examples, the session automatically terminates for the predetermined duration after output is provided to the DA (e.g., if no further natural language input or input is received within a predetermined duration to put the DA into listening mode). In some examples, the DA session is terminated in response to device 800 receiving user input to terminate the DA session.

[0294] exist Figure 8G In the process, after the initiated DA session is terminated and while device 800 is locked, device 800 receives third natural language input corresponding to a request to perform a third security task on device 800. In some examples, device 800 receives third natural language input (e.g., “How many miles did I walk today?”) upon re-initiating the DA session. For example, the DA session in Figure 8F After the lockout, the user provides input to re-initiate the DA session when the device is locked (800), and the DA session continues... Figure 8G The process is restarted (for example, device 800 displays a DA user interface including DA indicator identifier 806).

[0295] In some examples, device 800 determines whether the third natural language input corresponds to a security task request. Based on this determination, device 800 determines whether the state of the accessory device 900 meets a set of authentication criteria (e.g., attempting to re-authenticate itself). Based on device 800's re-authentication of itself, device 800 initiates a third security task upon locking and provides an output indicating the initiated third security task. For example, in... Figure 8G In the middle, device 800 outputs "You walked 3 miles today." Therefore, as... Figures 8E to 8GAs shown, after the initial DA session is terminated, device 800 may need to re-authenticate its own security task request.

[0296] Figures 9A to 9G The techniques for DA requests to unlock and authenticate device 800 using accessory device 900 are illustrated according to various examples.

[0297] exist Figure 9A When device 800 is locked, device 800 receives a user request to unlock device 800 (including biometric data captured by device 800). For example, device 800 uses one or more sensors to capture biometric input (e.g., fingerprint data, facial recognition data, voice authentication data, retinal scan data) intended to unlock the device.

[0298] exist Figure 9B In this process, device 800 determines (e.g., using authentication module 804) that the captured biometric data does not meet a set of biometric authentication criteria. For example, the captured fingerprint data does not match the fingerprint data of an authorized user of device 800, or device 800 cannot match the captured facial recognition data with the facial recognition data of an authorized user of device 800 (e.g., because the user's face is obscured by a mask). Based on the determination that the captured biometric data does not meet the set of biometric authentication criteria, device 800 provides output instructing it to remain locked. For example, in 9B, device 800 moves (e.g., shakes) the displayed lock icon 812 to indicate that biometric authentication was unsuccessful. In some examples, device 800 additionally or alternatively provides audio and / or haptic output to instruct device 800 to remain locked. Figure 9B In the middle, device 800 further displays a user interface 814 prompting the user to unlock device 800 using other methods (e.g., via password input).

[0299] exist Figure 9C In this context, while device 800 remains locked, and within a predetermined duration (e.g., 5 seconds, 10 seconds) during which an output instructing device 800 to remain locked is provided, device 800 receives a second user request to unlock the device. For example, as... Figure 9C As shown, device 800 receives user input corresponding to an entered password, such as touch input. In other examples, receiving a second user request includes device 800 capturing biometric data (e.g., the user re-provides biometric data to attempt to unlock device 800). For example, if Figure 9B If the initial facial recognition-based authentication fails because the user cannot put on the mask, the user can remove the mask and have device 800 perform facial recognition-based authentication again.

[0300] exist Figure 9DIn this process, based on the determination (e.g., via authentication module 804) that a second user request meets the unlock criteria, device 800 changes its state from locked to unlocked (e.g., unlocked for a predetermined duration). For example, device 800 displays the main screen user interface 816 (or another user interface displayed just before device 800 is finally locked). In some examples, the unlock criteria are met if the password entered by the user matches a predetermined password. In some examples, the unlock criteria are met if the captured biometric data meets a set of biometric authentication criteria.

[0301] exist Figure 9D Upon unlocking device 800, device 800 outputs prompt 818 to enable settings for the electronic device. This setting enables accessory device 900 to authenticate device 800 (e.g., DA running on device 800) to perform security tasks when device 800 is locked.

[0302] In some examples, device 800 receives user input to enable the setting. For example, in response to receiving user input for selection prompt 818, device 800 displays a settings user interface that allows the user to enable the setting. In some examples, enabling the setting also enables accessory device 900 to unlock device 800 (e.g., based on determining that the state of accessory device 900 meets a set of authentication criteria). In other examples, a separate setting enables accessory device 900 to authenticate device 800 to perform security tasks when locked and enables accessory device 900 to unlock device 800.

[0303] although Figures 9A to 9D The diagram shows that device 800 outputs prompt 818 after an initial user request to unlock device 800 fails (and after unlocking in response to another user request to unlock device 800). However, in some examples, device 800 outputs prompt 818 after an initial request to DA fails because device 800 is locked. For example, even though device 800 is locked and the setting is not enabled, device 800 receives natural language input, such as "Read my latest messages". Based on the determination that device 800 is locked, the natural language input corresponds to a security task request (e.g., read messages), and the setting is not enabled, device 800 provides output indicating that it cannot perform the task while locked, such as "I cannot do this while your device is locked" and / or "You need to unlock your device first". In some examples, after providing this output, device 800 receives a user request to unlock the device. Based on the determination that the user request to unlock the device meets the unlock criteria, device 800 unlocks and displays prompt 818 to enable the setting, such as... Figure 9D As shown. In some examples, device 800 further displays a prompt 818 based on determining that it unlocks within a predetermined duration after providing output indicating that it cannot perform a task while locked.

[0304] exist Figure 9E In the process, after the user enables the settings of the accessory device 900 to authenticate the device 800 to perform a security task and unlock the device 800, the state of the device 800 changes to a locked state, for example, the user relocks the device 800.

[0305] exist Figure 9E In this example, when device 800 is locked and communicating with accessory device 900, device 800 receives a request to unlock the electronic device. For example, device 800 captures biometric data. Device 800 further determines whether the captured biometric data meets a set of biometric authentication criteria, as discussed above. In this example, device 800 determines that the captured biometric authentication data does not meet the set of biometric authentication criteria, for example, because the user is wearing a mask, therefore facial recognition-based authentication is unsuccessful.

[0306] In some examples, upon receiving a request to unlock device 800 (and optionally based on determining that the captured biometric data does not meet that set of biometric authentication criteria), device 800 determines whether the status of the accessory device 900 meets a set of authentication criteria, such as those regarding... Figures 8A to 8G The above is discussed. In some examples, device 800 further determines whether the state of accessory device 900 meets the set of authentication criteria based on whether settings enabling accessory device 900 to unlock device 800 are enabled. For example, in Figure 9E In the process, device 800 determines that biometric authentication to unlock device 800 is unsuccessful (e.g., because the user is wearing a mask), and therefore attempts to unlock device 800 using accessory device 900.

[0307] exist Figure 9F If the status of accessory device 900 meets the authentication criteria, device 800 is unlocked. For example, device 800 displays the main screen user interface 816.

[0308] exist Figure 9G In this context, after device 800 is unlocked, it may lock again, for example, displaying a lock screen user interface 820. While device 800 is locked, it receives natural language input corresponding to a security task request, such as "Read my latest news". In some examples, device 800 receives natural language input based on the initiation of a DA session, such as "About..." Figures 8A to 8G As stated above.

[0309] In some examples, based on received natural language input, device 800 determines whether the state of accessory device 900 meets a set of authentication criteria, for example, when device 800 is locked. In some examples, device 800 performs this determination based on whether a setting enabling accessory device 900 to authenticate device 800 to perform a security task while locked is enabled. In some examples, device 800 determines whether the natural language input corresponds to a security task request, and determines whether the state of accessory device 900 meets a set of authentication criteria, such as those related to... Figures 8A to 8G As stated above.

[0310] exist Figure 9G In this process, based on the determination that the status of the accessory device 900 meets the set of authentication criteria, device 800 initiates a security task corresponding to the natural language input and provides an output indicating the initiated security task, for example, when device 800 is locked. For example, device 800 initiates a security task to read the user's latest message and outputs "A message from your mother says 'Are you coming home for dinner?'".

[0311] 5. The process of authenticating accessory-based devices for digital assistant requests.

[0312] Figures 10A to 10C A process 1000 for authentication of a digital assistant request based on an accessory device is illustrated, according to various examples. For example, process 1000 may be performed using one or more electronic devices implementing a digital assistant. In some examples, a client-server system (e.g., system 100) is used to perform process 1000, and the boxes of process 1000 may be divided in any way between a server (e.g., DA server 106) and a client device (e.g., device 800). In other examples, the boxes of process 1000 may be divided between a server and multiple client devices (e.g., mobile phones and smartwatches). Therefore, while portions of process 1000 are described herein as being performed by a specific device of the client-server system, it should be understood that process 1000 is not limited thereto. In other examples, process 1000 may be performed using only a client device (e.g., user device 104 or device 800) or only multiple client devices. In process 1000, some boxes may be optionally combined, the order of some boxes may be optionally changed, and some boxes may be optionally omitted. In some examples, additional steps may be performed in conjunction with process 1000.

[0313] In some examples, at box 1002, a second user input (e.g., by device 800) corresponding to a request to activate a digital assistant is received before natural language input is received and while the electronic device (e.g., device 800) is locked.

[0314] In some examples, at box 1004, a digital assistant session is initiated in response to receiving a second user input (e.g., by device 800).

[0315] At box 1006, natural language input (e.g., by DA module 726) is received when the electronic device is locked and communicating with an external accessory device (e.g., accessory device 900). In some examples, natural language input is received based on initiating a digital assistant session.

[0316] At box 1008, it is determined (e.g., by DA module 726) whether the natural language input corresponds to a security task request. In some examples, determining whether the natural language input corresponds to a security task request includes determining whether the natural language input corresponds to a personal domain.

[0317] In some examples, in box 1010 ( Figure 10C At block 1012, based on the determination that the natural language input does not correspond to a security task request and when the electronic device is locked, it is determined (e.g., by DA module 726) whether satisfying the task corresponding to the natural language input includes providing a security output. In some examples, at block 1012, based on the determination that the natural language input does not correspond to a security task request (and optionally based on the determination that satisfying the task corresponding to the natural language input does not include providing a security output) and when the electronic device is locked, a second task corresponding to the natural language input is initiated (e.g., by DA module 726), without determining whether one or more states of the external accessory device satisfy a set of authentication criteria. In some examples, at block 1014, for example by device 800, a third output indicating the initiated second task is provided.

[0318] In some examples, at box 1016, based on determining that fulfilling the task includes providing a security output, it is determined (e.g., by authentication module 804 and / or authentication module 904) whether one or more states of the external accessory device meet the set of authentication criteria. In some examples, at box 1018, based on determining that one or more states of the external accessory device do not meet the set of authentication criteria, for example, device 800 provides a fourth output indicating that the electronic device cannot complete the task. In some examples, at box 1020, based on determining that one or more states of the external accessory device meet the set of authentication criteria, the electronic device provides a security output.

[0319] In some examples, at block 1022, after a security output is provided and while the electronic device is locked, for example, device 800 receives a first user input in response to the security output. At block 1024, based on the first user input, a task is initiated by the electronic device (e.g., by DA module 726).

[0320] In some examples, determining whether a natural language input corresponds to a security task request includes determining (e.g., by DA module 726) whether the security task is of type one or type two, as shown in box 1026. Figure 10A As shown in the diagram. In some examples, at box 1028, based on the determination that the security task is of the second type and the electronic device is in a locked state: a seventh output is provided indicating that the electronic device cannot complete the security task when the electronic device is in a locked state.

[0321] At box 1030, based on determining that the natural language input corresponds to a security task request, it is determined (e.g., by authentication module 804 and / or authentication module 904) whether one or more states of an external accessory device (e.g., accessory device 900) meet a set of authentication criteria. In some examples, determining whether one or more states of the external accessory device meet the set of authentication criteria is performed based on determining that the security task is of type one. In some examples, meeting the set of authentication criteria requires that the external accessory device be physically associated with the user of the electronic device.

[0322] In some examples, at box 1032, based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria and when the electronic device is in a locked state: for example, device 800 provides a second output indicating that the electronic device cannot perform a security task when the electronic device is in a locked state.

[0323] In some examples, at box 1034, based on determining that one or more states of the external accessory device meet the set of authentication criteria and when the electronic device is in a locked state, it is determined (e.g., by authentication module 804) whether the electronic device meets a set of security criteria corresponding to the security task. In some examples, at box 1036 ( Figure 10B At this point, based on the determination that the electronic device does not meet the set of security standards, for example, device 800 provides an output indicating that the electronic device cannot perform a security task when it is in a locked state.

[0324] In some examples, in box 1038 ( Figure 10B At block 1040, based on the determination that one or more states of the external accessory device meet the set of authentication criteria, an electronic device (e.g., DA module 726) initiates a security task corresponding to the natural language input. In some examples, the initiation of the security task is performed based on the determination that the electronic device meets the set of security criteria. In some examples, at block 1040, for example, device 800 provides an output indicating the initiated security task. In some examples, the output indicating the initiated security task includes a second security output.

[0325] In some examples, at box 1042, based on the determination that one or more states of the external accessory device meet the set of authentication criteria and while the electronic device is in a locked state: the external accessory device (e.g., by authentication module 804) provides a fifth output indicating the initiation of a security task. In some examples, the fifth output includes a prompt from the user to cancel the initiated security task. In some examples, at box 1044, based on the determination that one or more states of the external accessory device meet the set of authentication criteria and while the electronic device is in a locked state, the electronic device provides a sixth output indicating a security task to be performed using the external accessory device to authenticate the electronic device.

[0326] In some examples, at box 1046, device 800 receives an indication from an external accessory device that the user has selected a prompt to cancel. In some examples, at box 1048, the security task is terminated by an electronic device (e.g., DA module 726) based on the indication received that the user selected the prompt when initiating the security task.

[0327] In some examples, an output indicative of the initiated security task is provided during the initiated digital assistant session. In some examples, at block 1050, while the electronic device is locked, during the initiated digital assistant session, and after the output indicative of the initiated security task is provided, for example, device 800 receives second natural language input corresponding to a request to perform a second security task on the electronic device. In some examples, at block 1052, based on the received second natural language input, a second security task is initiated (e.g., by DA module 726) without determining (e.g., by authentication module 804 and / or authentication module 904) whether the state of one or more external accessory devices meets the set of authentication criteria. In some examples, at block 1054, for example, device 800 provides an eighth output indicative of the initiated second security task.

[0328] In some examples, at block 1056, when the electronic device is locked, after providing the eighth output, the initiated digital assistant session is terminated, for example, by device 800. In some examples, at block 1058, after terminating the initiated digital assistant session and while the electronic device is locked, for example, device 800 receives third natural language input corresponding to a request to perform a third security task on the electronic device. In some examples, based on the received third natural language input, process 1000 proceeds to block 1008, for example, determining (e.g., by DA module 726) whether the third natural language input corresponds to a security task request. In some examples, based on the received third natural language input, determining (e.g., by authentication module 804 and / or authentication module 904) whether one or more states of an external accessory device meet the set of authentication criteria.

[0329] The above text is about Figures 10A to 10C The operation is optionally performed by Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C and Figure 8A The process is implemented using the components depicted herein. For example, the operation of process 1000 can be implemented by device 800 and auxiliary device 900. Those skilled in the art will clearly understand how to implement the process based on the components depicted herein. Figures 1 to 4 , Figures 6A to 6B and Figures 7A to 7C The components described herein are used to perform other processes.

[0330] 6. The process of using an accessory device to unlock the device and authenticate the device's digital assistant request.

[0331] Figures 11A to 11C A process 1100 for requesting a digital assistant to unlock and authenticate a device using an accessory device is illustrated, according to various examples. For example, process 1100 may be performed using one or more electronic devices implementing a digital assistant. In some examples, a client-server system (e.g., system 100) is used to perform process 1100, and the boxes of process 1100 may be divided in any way between a server (e.g., DA server 106) and a client device (e.g., device 800). In other examples, the boxes of process 1100 may be divided between a server and multiple client devices (e.g., mobile phones and smartwatches). Therefore, while portions of process 1100 are described herein as being performed by a specific device of the client-server system, it should be understood that process 1100 is not limited thereto. In other examples, process 1100 may be performed using only a client device (e.g., user device 104 or device 800) or only multiple client devices. In process 1100, some boxes may be optionally combined, some boxes may be optionally changed in order, and some boxes may be optionally omitted. In some examples, process 1100 can be combined to perform additional steps.

[0332] In some examples, at box 1102, before receiving a request to unlock the electronic device (e.g., device 800) and while the electronic device is in a third locked state: a second user request to unlock the electronic device is received (e.g., by device 800), including the capture of second biometric data by the electronic device. In some examples, at box 1104, based on a determination (e.g., by authentication module 804) that the second biometric data does not meet a second set of biometric authentication criteria, for example, device 800 provides a second output instructing the electronic device to remain in the third locked state.

[0333] In some examples, at block 1106, before receiving a request to unlock the electronic device, while the electronic device is in a third locked state, and for a predetermined duration after providing the second output, for example, a third user request to unlock the electronic device is received by device 800. In some examples, at block 1108, based on determining (e.g., by authentication module 804) that the third user request meets the unlocking criteria, the state of the electronic device is changed from the third locked state to the second unlocked state. In some examples, at block 1110, based on changing the state of the electronic device from the third locked state to the second unlocked state, for example, device 800 outputs a prompt to enable a setting of the electronic device, wherein this setting enables an external accessory device (e.g., device 900) to authenticate the electronic device to perform a security task while the electronic device is in a locked state.

[0334] In some examples, before receiving a request to unlock the electronic device and while the electronic device is in a third locked state, a second natural language input is received (e.g., by device 800), and a third output indicating that the electronic device cannot perform a task corresponding to the second natural language input while in the third locked state is provided (e.g., by device 800) is provided. In some examples, before receiving a request to unlock the electronic device and while the electronic device is in a third locked state: for example, after providing the third output, a second user request to unlock the electronic device is received by device 800. In some examples, based on determining (e.g., by authentication module 804) that the second user request meets the unlocking criteria, the state of the electronic device is changed from a third locked state to a second unlocked state. In some examples, based on changing the state of the electronic device from a third locked state to a second unlocked state, (e.g., by device 800) a prompt to enable a setting of the electronic device is output, wherein this setting enables an external accessory device to authenticate the electronic device to perform a security task while the electronic device is in a locked state.

[0335] In some examples, at box 1112, a request to unlock the electronic device is received, for example, by device 800, when the electronic device is locked and communicating with an external accessory device. In some examples, receiving the request to unlock the electronic device includes the electronic device capturing biometric data. In some examples, at box 1114, it is determined (e.g., by authentication module 804) whether the captured biometric data meets a set of biometric authentication criteria.

[0336] In some examples, at box 1116, the electronic device unlocks (e.g., changes to an unlocked state) based on the determination that the captured biometric data meets the set of biometric authentication criteria.

[0337] In some examples, at box 1118, based on a received request to unlock the electronic device, it is determined (e.g., by authentication module 804) whether one or more states of the external accessory device meet a set of authentication criteria. In some examples, the determination of whether one or more states of the external accessory device meet the set of authentication criteria is performed based on the determination that the captured biometric data does not meet the set of biometric authentication criteria.

[0338] In some examples, at box 1120, based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria, for example, device 800 provides an output instructing the electronic device to remain locked.

[0339] In some examples, at box 1122, the state of the electronic device is changed from locked to unlocked based on determining that one or more states of the external accessory device meet the set of authentication criteria. In some examples, at box 1124 ( Figure 11B At point ), after changing the state from locked to unlocked, the electronic device's state is changed from unlocked to a second locked state.

[0340] In some examples, at box 1126, user input corresponding to a request to activate a digital assistant is received by device 800 before natural language input is received and while the electronic device is in a second locked state. In some examples, at box 1128, a digital assistant session is initiated by device 800 in response to receiving user input.

[0341] In some examples, at box 1130, when the electronic device is in a second locked state, natural language input corresponding to a security task request is received, for example, by the DA module 726. In some examples, natural language input is received based on initiating a digital assistant session.

[0342] In some examples, at box 1132, it is determined (e.g., by DA module 726 when the electronic device is in a second locked state) whether the security task is of the first type or the second type. In some examples, at box 1134, based on the determination that the security task is of the second type and when the electronic device is in a second locked state, the electronic device provides a fourth output indicating that the electronic device cannot complete the security task when the electronic device is in the second locked state.

[0343] In some examples, at box 1136, based on received natural language input and while the electronic device is in a second locked state, it is determined (e.g., by authentication module 804 and / or authentication module 904) whether one or more states of an external accessory device meet the set of authentication criteria. In some examples, meeting the set of authentication criteria requires the external accessory device to be physically associated with the user of the electronic device. In some examples, determining whether one or more states of the external accessory device meet the set of authentication criteria is performed based on determining that the security task is of a first type. In some examples, while the electronic device is in a second locked state, it is determined (e.g., by DA module 726) whether the natural language input corresponds to a security task request, wherein determining whether one or more states of the external accessory device meet the set of authentication criteria is performed based on determining that the natural language input corresponds to a security task request. In some examples, determining whether the natural language input corresponds to a security task request includes determining whether the natural language input corresponds to a personal domain. In some examples, determining whether the natural language input corresponds to a security task request includes determining whether the security task is of a first type or a second type.

[0344] In some examples, at box 1138, a fifth output is provided by device 800 indicating that the electronic device cannot perform a security task when the electronic device is in a second locked state, based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria and the electronic device is in a second locked state.

[0345] In some examples, at box 1140, based on the determination that one or more states of the external accessory device meet the set of authentication criteria, an electronic device (e.g., DA module 726 when device 800 is in a second locked state) initiates a security task corresponding to natural language input. In some examples, the security task is initiated based on the determination that the setting is enabled.

[0346] In some examples, at box 1142, for example, device 800 provides an output indicating the initiated security task when in a second locked state. In some examples, the output indicating the initiated security task includes security output.

[0347] In some examples, in box 1144 ( Figure 11CAt block 1146, based on the determination that one or more states of the external accessory device meet the set of authentication criteria and while the electronic device is in a second locked state: the external accessory device (e.g., by authentication module 804) provides a sixth output indicating the initiation of a security task. In some examples, the sixth output includes a prompt from the user to cancel the initiated security task. In some examples, at block 1146, based on the determination that one or more states of the external accessory device meet the set of authentication criteria and while the electronic device is in a second locked state, the electronic device provides a seventh output indicating a security task to be performed using the external accessory device to authenticate the electronic device.

[0348] In some examples, at box 1148, device 800 receives an indication of user selection from an external accessory device. In some examples, at box 1150, an electronic device (e.g., DA module 726) terminates the security task based on the indication of user selection received when initiating the security task.

[0349] The above text is about Figures 11A to 11C The operation is optionally performed by Figures 1 to 4 , Figures 6A to 6B , Figures 7A to 7C and Figure 8A The components depicted herein are used to implement this. For example, the operation of process 1100 can be implemented by device 800 and auxiliary device 900. Those skilled in the art will clearly understand how to implement this based on the components depicted herein. Figures 1 to 4 , Figures 6A to 6B and Figures 7A to 7C The components described herein are used to perform other processes.

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

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

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

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

[0354] For purposes of explanation, the foregoing description has been given by reference to specific embodiments. However, the illustrative discussion above is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible based on the teachings above. These embodiments were chosen and described in order to best explain the principles of these techniques and their practical applications. Others skilled in the art will thus be able to best utilize these techniques and the various embodiments with various modifications suitable for the particular intended use.

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

[0356] As described above, one aspect of the present invention is to collect and use data available from various sources to enhance the usefulness of digital assistants. This disclosure contemplates that, in some instances, such collected data may include personal information that uniquely identifies or can be used to contact or locate specific individuals. Such personal information may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, data or records relating to a 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.

[0357] This disclosure recognizes that the use of such personal information data in the techniques of this invention can be beneficial to users. For example, a digital assistant can use personal information data to fulfill tasks requested by a user. Furthermore, this disclosure also contemplates other uses of personal information data that are beneficial to the user. For example, health and fitness data can be used to provide insights into a user's overall health status or as positive feedback for individuals using technology to pursue health goals.

[0358] This disclosure assumes 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 generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should be conducted only after obtaining informed consent from users. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding 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 in other countries, health data 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.

[0359] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, with regard to the use of personal information for digital assistant responses, the technology of this invention can be configured to allow a user to opt-in or opt-out to participate in the collection of personal information data during or at any time during service registration. In another example, a user can choose not to allow the digital assistant access to personal information. In yet another example, a user can choose to limit the length of time the digital assistant can access personal information. In addition to providing "opt-in" and "opt-out" options, this disclosure envisions providing notifications related to access to or use of personal information. For example, a user may be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0360] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Where appropriate, deidentification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or characteristics of stored data (e.g., collecting location data at the city level rather than address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0361] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be unable to function properly due to the absence of all or part of such personal information data. For example, a digital assistant can use non-personal information data or a minimal amount of personal information (such as content requested by the user's associated device, other non-personal information available to the digital assistant, or publicly available information) to process user requests.

Claims

1. A method comprising: In electronic devices having one or more processors and memory: When the electronic device is in a locked state and communicating with an external accessory device: Receive natural language input; Determine whether the natural language input corresponds to a security task request; and Based on the determination that the natural language input corresponds to a security task request: Determine whether one or more states of the external accessory device meet a set of authentication criteria; and Based on the determination that the external accessory device meets the set of authentication criteria: The electronic device initiates a security task corresponding to the natural language input; and Provides output indicating the initiated security task.

2. The method according to claim 1, further comprising: Based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria and when the electronic device is in a locked state: Provide a second output indicating that the electronic device cannot perform the security task when the electronic device is in the locked state.

3. The method according to claim 1, further comprising: Based on the determination that the natural language input does not correspond to a security task request and when the electronic device is in a locked state: The electronic device initiates a second task corresponding to the natural language input without determining whether the state of the external accessory device meets the set of authentication criteria; and Provides a third output indicating the second task initiated.

4. The method according to claim 1, further comprising: Based on the determination that the natural language input does not correspond to a security task request and when the electronic device is in a locked state: Determine whether satisfying the second task corresponding to the natural language input includes providing a secure output; and Based on the determination that fulfilling the second task includes providing a secure output: Determine whether the one or more states of the external accessory device meet the set of authentication criteria; Based on the determination that the external accessory device meets the set of authentication criteria: The security output is provided by the electronic device; and Based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria: A fourth output is provided indicating that the electronic device cannot complete the second task.

5. The method according to claim 4, further comprising: After the security output is provided and while the electronic device is locked: Receive a first user input in response to the security output; and The second task is initiated by the electronic device based on the first user input.

6. The method according to claim 1, further comprising: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: The external accessory device is made to provide a fifth output indicating the initiation of the security task.

7. The method of claim 6, wherein the fifth output includes a prompt indicating that the user has cancelled the initiated security task, and the method further includes: Receive the user's instruction to select the prompt from the external accessory device; and The electronic device terminates the security task based on the instruction received from the user when the security task is initiated, upon the user selecting the prompt.

8. The method according to claim 1, further comprising: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: The electronic device provides a sixth output instructing the use of the external accessory device to authenticate the electronic device for the security task.

9. The method of claim 1, wherein determining whether the natural language input corresponds to a security task request comprises: Determine whether the security task is of type one or type two.

10. The method of claim 9, wherein determining whether the one or more states of the external accessory device meet the set of authentication criteria is performed based on determining that the security task has a first type, the method further comprising: Based on the determination that the security task has a second type and when the electronic device is in a locked state: The electronic device provides a seventh output indicating that the electronic device cannot complete the security task when the electronic device is in a locked state.

11. The method of claim 1, wherein the output indicating the initiated security task includes a second security output.

12. The method according to claim 1, further comprising: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: Determine whether the electronic device meets a set of security criteria corresponding to the security task, wherein the security task is initiated based on the determination that the electronic device meets the set of security criteria.

13. The method according to claim 1, further comprising: Before receiving the natural language input, a second user input corresponding to a request to activate the digital assistant is received when the electronic device is in a locked state; and In response to receiving the second user input, a digital assistant session is initiated, wherein the natural language input is received in accordance with initiating the digital assistant session.

14. The method of claim 13, wherein the output instructing the initiated security task is provided during the initiated digital assistant session, the method further comprising: When the electronic device is locked, during the initiated digital assistant session, and after the output indicating the initiated security task is provided: Receive second natural language input corresponding to a request for the electronic device to perform a second security task; and Based on the received second natural language input: Initiate the second security task without determining whether the one or more states of the external accessory device meet the set of authentication criteria; and Provides the eighth output indicating the second security mission initiated.

15. The method of claim 14, further comprising: When the electronic device is in a locked state: After providing the eighth output, terminate the initiated digital assistant session; After the initiated digital assistant session is terminated, third natural language input corresponding to a request for the electronic device to perform a third security task is received; and Based on the received third natural language input, determine whether the state of one or more external accessory devices meets the set of authentication criteria.

16. The method of claim 1, wherein the external accessory device that satisfies the set of authentication criteria is physically associated with the user of the electronic device.

17. The method of claim 1, wherein determining whether the natural language input corresponds to a security task request includes determining whether the natural language input corresponds to a personal domain.

18. An electronic device comprising: One or more processors; Memory; as well as One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: When the electronic device is in a locked state and communicating with an external accessory device: Receive natural language input; Determine whether the natural language input corresponds to a security task request; and Based on the determination that the natural language input corresponds to a security task request: Determine whether one or more states of the external accessory device meet a set of authentication criteria; and Based on the determination that the external accessory device meets the set of authentication criteria: The electronic device initiates a security task corresponding to the natural language input; and Provides output indicating the initiated security task.

19. The electronic device of claim 18, wherein the one or more programs further include instructions for performing the following operations: Based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria and when the electronic device is in a locked state: Provide a second output indicating that the electronic device cannot perform the security task when the electronic device is in a locked state.

20. The electronic device of claim 18, wherein the one or more programs further include instructions for performing the following operations: Based on the determination that the natural language input does not correspond to a security task request and when the electronic device is in a locked state: The electronic device initiates a second task corresponding to the natural language input without determining whether the state of the external accessory device meets the set of authentication criteria; and Provides a third output indicating the second task initiated.

21. The electronic device of claim 18, wherein the one or more programs further include instructions for performing the following operations: Based on the determination that the natural language input does not correspond to a security task request and when the electronic device is in a locked state: Determine whether satisfying the second task corresponding to the natural language input includes providing a secure output; and Based on the determination that fulfilling the second task includes providing a secure output: Determine whether the one or more states of the external accessory device meet the set of authentication criteria; Based on the determination that the external accessory device meets the set of authentication criteria: The security output is provided by the electronic device; and Based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria: A fourth output is provided indicating that the electronic device cannot complete the second task.

22. The electronic device of claim 21, wherein the one or more programs further include instructions for performing the following operations: After the security output is provided and while the electronic device is locked: Receive first user input in response to the security output; and The second task is initiated by the electronic device based on the first user input.

23. The electronic device of claim 18, wherein the one or more programs further include instructions for performing the following operations: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: The external accessory device is made to provide a fifth output indicating the initiation of the security task.

24. The electronic device of claim 23, wherein the fifth output includes a prompt indicating that the user has cancelled the initiated security task, and wherein the one or more programs further include instructions for: Receives an instruction from the user to select the prompt from the external accessory device; and The electronic device terminates the security task based on the instruction received from the user when the security task is initiated, upon the user selecting the prompt.

25. The electronic device of claim 18, wherein the one or more programs further include instructions for performing the following operations: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: The electronic device provides a sixth output instructing the use of the external accessory device to authenticate the electronic device for the security task.

26. The electronic device of claim 18, wherein determining whether the natural language input corresponds to a security task request comprises: Determine whether the security task is of type one or type two.

27. The electronic device of claim 26, wherein determining whether the one or more states of the external accessory device meet the set of authentication criteria is performed based on determining that the security task has a first type, and wherein the one or more procedures further include instructions for: Based on the determination that the security task has a second type and when the electronic device is in a locked state: The electronic device provides a seventh output indicating that the electronic device cannot complete the security task when the electronic device is in a locked state.

28. The electronic device of claim 18, wherein the output indicating the initiated security task includes a second security output.

29. The electronic device of claim 18, wherein the one or more programs further include instructions for performing the following operations: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: Determine whether the electronic device meets a set of security criteria corresponding to the security task, wherein the security task is initiated based on the determination that the electronic device meets the set of security criteria.

30. The electronic device of claim 18, wherein the one or more programs further include instructions for performing the following operations: Before receiving the natural language input, a second user input corresponding to a request to activate the digital assistant is received while the electronic device is in a locked state; and In response to receiving the second user input, a digital assistant session is initiated, wherein the natural language input is received in accordance with initiating the digital assistant session.

31. The electronic device of claim 30, wherein the output instructing the initiated security task is provided during the initiated digital assistant session, and wherein the one or more programs further include instructions for: When the electronic device is locked, during the initiated digital assistant session, and after the output indicating the initiated security task is provided: Receive second natural language input corresponding to a request for the electronic device to perform a second security task; and Based on the received second natural language input: Initiate the second security task without determining whether the one or more states of the external accessory device meet the set of authentication criteria; and Provides the eighth output indicating the second security mission initiated.

32. The electronic device of claim 31, wherein the one or more programs further include instructions for performing the following operations: When the electronic device is in a locked state: After providing the eighth output, terminate the initiated digital assistant session; After ending the initiated digital assistant session, third natural language input corresponding to a request for the electronic device to perform a third security task is received; and Based on the received third natural language input, determine whether the state of one or more external accessory devices meets the set of authentication criteria.

33. The electronic device of claim 18, wherein the external accessory device that satisfies the set of authentication criteria is physically associated with the user of the electronic device.

34. The electronic device of claim 18, wherein determining whether the natural language input corresponds to a security task request includes determining whether the natural language input corresponds to a personal domain.

35. A computer-readable storage medium storing one or more programs comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to: When the electronic device is in a locked state and communicating with an external accessory device: Receive natural language input; Determine whether the natural language input corresponds to a security task request; and Based on the determination that the natural language input corresponds to a security task request: Determine whether one or more states of the external accessory device meet a set of authentication criteria; and Based on the determination that the external accessory device meets the set of authentication criteria: The electronic device initiates a security task corresponding to the natural language input; and Provides output indicating the initiated security task.

36. The computer-readable storage medium of claim 35, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: Based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria and when the electronic device is in a locked state: Provide a second output indicating that the electronic device cannot perform the security task when the electronic device is in a locked state.

37. The computer-readable storage medium of claim 35, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: Based on the determination that the natural language input does not correspond to a security task request and when the electronic device is in a locked state: The electronic device initiates a second task corresponding to the natural language input without determining whether the state of the external accessory device meets the set of authentication criteria; and Provides a third output indicating the second task initiated.

38. The computer-readable storage medium of claim 35, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: Based on the determination that the natural language input does not correspond to a security task request and when the electronic device is in a locked state: Determine whether satisfying the second task corresponding to the natural language input includes providing a secure output; and Based on the determination that fulfilling the second task includes providing a secure output: Determine whether the one or more states of the external accessory device meet the set of authentication criteria; Based on the determination that the external accessory device meets the set of authentication criteria: The security output is provided by the electronic device; and Based on the determination that one or more states of the external accessory device do not meet the set of authentication criteria: A fourth output is provided indicating that the electronic device cannot complete the second task.

39. The computer-readable storage medium of claim 38, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: After the security output is provided and while the electronic device is locked: Receive first user input in response to the security output; and The second task is initiated by the electronic device based on the first user input.

40. The computer-readable storage medium of claim 35, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: The external accessory device is made to provide a fifth output indicating the initiation of the security task.

41. The computer-readable storage medium of claim 40, wherein the fifth output includes a prompt for the user to cancel the initiated security task, and wherein the one or more programs further includes instructions that, when executed by the one or more processors, cause the electronic device to: Receives an instruction from the user to select the prompt from the external accessory device; and The electronic device terminates the security task based on the instruction received from the user when the security task is initiated, upon the user selecting the prompt.

42. The computer-readable storage medium of claim 35, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: The electronic device provides a sixth output instructing the use of the external accessory device to authenticate the electronic device for the security task.

43. The computer-readable storage medium of claim 35, wherein determining whether the natural language input corresponds to a security task request comprises: Determine whether the security task is of type one or type two.

44. The computer-readable storage medium of claim 43, wherein determining whether the state of the external accessory device satisfies the set of authentication criteria is performed based on determining that the security task has a first type, and wherein the one or more programs further include instructions that, when executed by the one or more processors, cause the electronic device to: Based on the determination that the security task has a second type and when the electronic device is in a locked state: The electronic device provides a seventh output indicating that the electronic device cannot complete the security task when the electronic device is in a locked state.

45. The computer-readable storage medium of claim 35, wherein the output indicating the initiated security task includes a second security output.

46. ​​The computer-readable storage medium of claim 35, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: Based on the determination that the external accessory device meets the set of authentication criteria and when the electronic device is in a locked state: Determine whether the electronic device meets a set of security criteria corresponding to the security task, wherein the security task is initiated based on the determination that the electronic device meets the set of security criteria.

47. The computer-readable storage medium of claim 35, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: Before receiving the natural language input, a second user input corresponding to a request to activate the digital assistant is received while the electronic device is in a locked state; and In response to receiving the second user input, a digital assistant session is initiated, wherein the natural language input is received in accordance with initiating the digital assistant session.

48. The computer-readable storage medium of claim 47, wherein the output instructing the initiated security task is provided during the initiated digital assistant session, and wherein the one or more programs further include instructions that, when executed by the one or more processors, cause the electronic device to: When the electronic device is locked, during the initiated digital assistant session, and after the output indicating the initiated security task is provided: Receive second natural language input corresponding to a request for the electronic device to perform a second security task; and Based on the received second natural language input: Initiate the second security task without determining whether the one or more states of the external accessory device meet the set of authentication criteria; and Provides the eighth output indicating the second security mission initiated.

49. The computer-readable storage medium of claim 48, wherein the one or more programs further comprises instructions that, when executed by the one or more processors, cause the electronic device to: When the electronic device is in a locked state: After providing the eighth output, terminate the initiated digital assistant session; After ending the initiated digital assistant session, third natural language input corresponding to a request for the electronic device to perform a third security task is received; and Based on the received third natural language input, determine whether the state of one or more external accessory devices meets the set of authentication criteria.

50. The computer-readable storage medium of claim 35, wherein the external accessory device that satisfies the set of authentication criteria is physically associated with the user of the electronic device.

51. The computer-readable storage medium of claim 35, wherein determining whether the natural language input corresponds to a security task request includes determining whether the natural language input corresponds to a personal domain.

Images