CN110058834B

CN110058834B - Intelligent device arbitration and control

Info

Publication number: CN110058834B
Application number: CN201811605229.2A
Authority: CN
Inventors: K·W·皮索尔; R·M·奥尔; D·J·曼德尔
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2016-06-11
Filing date: 2017-05-27
Publication date: 2022-06-17
Anticipated expiration: 2037-05-27
Also published as: CN107491285A; CN110058834A; CN107491285B

Abstract

The invention provides intelligent device arbitration and control. The present disclosure relates to systems and processes for arbitrating between and/or controlling electronic devices with virtual assistants. In one exemplary process, a first electronic device samples audio input with a microphone. The first electronic device broadcasts a first set of one or more values based on the sampled audio input. Further, the first electronic device receives a second set of one or more values based on the audio input from the second electronic device. Based on the first set of one or more values and the second set of one or more values, the first electronic device determines whether a response to the audio input should be made or whether a response to the audio input should be abandoned.

Description

Intelligent device arbitration and control

Description of divisional applications

The application is a divisional application of Chinese patent application with application number 201710392871.6 and name "intelligent equipment arbitration and control", which is filed on 27.5.2017.

Technical Field

The present disclosure relates generally to multi-device systems, and more particularly to intelligent arbitration and control of devices in a multi-device system.

Background

Many modern electronic devices provide virtual assistant services to perform various tasks in response to user speech input. In some cases, multiple electronic devices with virtual assistant services may operate in parallel in a shared environment. Thus, when the user input contains a trigger phrase or command that is recognized by each of the virtual assistant services on these electronic devices, the user input may cause each of the plurality of electronic devices to respond. This, in turn, may lead to a confusing experience for the user, as multiple electronic devices may begin listening and/or prompting for additional input at the same time. In addition, multiple electronic devices may perform repeated or conflicting operations based on the same user input.

Further, the user input may identify one or more particular electronic devices to perform the task. For example, a user may issue commands to the virtual assistant service to remotely control home electronic devices by referring to the devices by location ("in my living room"), by device type ("on my television"), or by the type of task that the devices need to perform ("playing the beatles"). However, the user input itself often does not provide sufficient information for the virtual assistant service to identify, control, and/or manage the electronic device.

Disclosure of Invention

Exemplary methods are provided herein. An example method includes, at a first electronic device having a microphone: sampling an audio input with a microphone at a first electronic device; broadcasting, with a first electronic device, a first set of one or more values based on the sampled audio input; receiving, with the first electronic device, a second set of one or more values from the second electronic device, wherein the second set of one or more values is based on the audio input; and determining, with the first electronic device, whether the first electronic device should respond to the audio input based on the first set of one or more values and the second set of one or more values. In accordance with a determination that the first electronic device should respond to the audio input, the first electronic device responds to the audio input. In accordance with a determination that the first electronic device should not respond to the audio input, the first electronic device forgoes responding to the audio input.

Example non-transitory computer-readable storage media are disclosed herein. An exemplary non-transitory computer readable 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 with a microphone, cause the electronic device to: sampling an audio input with a microphone at the electronic device; broadcasting a first set of one or more values based on the sampled audio input; receiving a second set of one or more values from a second electronic device, wherein the second set of one or more values is based on the audio input; and determining whether the electronic device should respond to the audio input based on the first set of one or more values and the second set of one or more values. The instructions further cause the electronic device to: in accordance with a determination that the electronic device should respond to the audio input, responding to the audio input; in accordance with a determination that the electronic device should not respond to the audio input, forgoing responding to the audio input.

Example apparatuses are provided herein. An exemplary device includes a microphone; 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 include instructions for: sampling an audio input with the microphone at an electronic device; broadcasting a first set of one or more values based on the sampled audio input; receiving a second set of one or more values from a second electronic device, wherein the second set of one or more values is based on the audio input; and determining whether the electronic device should respond to the audio input based on the first set of one or more values and the second set of one or more values. The one or more programs further include instructions for: in accordance with a determination that the electronic device should respond to the audio input, responding to the audio input; in accordance with a determination that the electronic device should not respond to the audio input, forgoing responding to the audio input.

An exemplary electronic device includes a microphone; means for sampling audio input with the microphone at the electronic device; means for broadcasting a first set of one or more values based on the sampled audio input; means for receiving a second set of one or more values from a second electronic device, wherein the second set of one or more values is based on the audio input; means for determining whether the electronic device should respond to the audio input based on the first set of one or more values and the second set of one or more values; means for responding to the audio input in accordance with a determination that the electronic device should respond to the audio input; and in accordance with a determination that the electronic device should not respond to the audio input, forgoing responding to the audio input.

An exemplary method for controlling a user device with a virtual assistant on a first user device includes, at an electronic device: receiving, with the electronic device, data corresponding to an audio input from a first user device; obtaining, with the electronic device, an identification of a second user device based on data corresponding to an audio input; obtaining, with the electronic device, an identification of a media item based on data corresponding to an audio input; and providing, with the electronic device, a command to the first user device that includes the identification of the media item and the identification of the second user device.

An exemplary 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 receive data corresponding to audio input from a first user device; obtaining an identification of the second user device based on data corresponding to the audio input; obtaining an identification of a media item based on data corresponding to an audio input; and providing a command to the first user device including the identification of the media item and the identification of the second user device.

An exemplary 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: receiving data corresponding to an audio input from a first user device; obtaining an identification of the second user device based on data corresponding to the audio input; obtaining an identification of a media item based on data corresponding to an audio input; and providing a command to the first user device including the identification of the media item and the identification of the second user device.

An exemplary electronic device includes means for receiving data corresponding to an audio input from a first user device; means for obtaining an identification of the second user device based on data corresponding to the audio input; means for obtaining an identification of a media item based on data corresponding to an audio input; and means for providing a command to the first user device including the identification of the media item and the identification of the second user device.

Drawings

For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings in which like reference numerals indicate corresponding parts throughout the figures.

FIG. 1 is a block diagram illustrating a system and environment for implementing a digital assistant in accordance with various embodiments.

Figure 2A is a block diagram illustrating a portable multifunction device implementing a client-side portion of a digital assistant, according to some embodiments.

Fig. 2B is a block diagram illustrating exemplary components for event processing, in accordance with various embodiments.

Figure 3 illustrates a portable multifunction device implementing a client-side portion of a digital assistant, in accordance with various embodiments.

FIG. 4 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with various embodiments.

FIG. 5A illustrates an exemplary user interface of an application menu on a portable multifunction device in accordance with various embodiments.

FIG. 5B illustrates an exemplary user interface of a multifunction device with a touch-sensitive surface separate from a display in accordance with various embodiments.

FIG. 6A illustrates a personal electronic device, in accordance with various embodiments.

Fig. 6B is a block diagram illustrating a personal electronic device, in accordance with various embodiments.

Fig. 7A is a block diagram illustrating a digital assistant system or server portion thereof in accordance with various embodiments.

Fig. 7B illustrates functionality of the digital assistant of fig. 7A in accordance with various embodiments.

FIG. 7C illustrates a portion of an ontology in accordance with various embodiments.

Fig. 8A-8C illustrate a plurality of electronic devices according to various embodiments.

Fig. 9A-9C illustrate exemplary systems and environments for controlling an electronic device, in accordance with various embodiments.

Fig. 10A-10C illustrate an exemplary process for device arbitration, in accordance with various embodiments.

Fig. 11A-11E illustrate exemplary processes for device control, in accordance with various embodiments.

FIG. 12 illustrates a functional block diagram of an electronic device in accordance with various embodiments.

Fig. 13 illustrates a functional block diagram of an electronic device of a system in accordance with various embodiments.

Detailed Description

In the following description of the present disclosure and embodiments, reference is made to the accompanying drawings, in which are shown by way of illustration specific embodiments that may be practiced. It is to be understood that other embodiments and examples may be practiced and that changes may be made without departing from the scope of the present disclosure.

Techniques for intelligent device arbitration and control are desired. As described herein, the techniques improve a user's ability to interact with multiple electronic devices, thereby increasing productivity. In addition, such techniques can reduce the computational requirements and battery power that would otherwise be consumed by the electronic device due to redundant responses to user inputs.

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, a first input may be named a second input, and similarly, a second input may be named a first input, without departing from the scope of the various described embodiments. Both the first and second inputs may be outputs, and in some cases may be separate, distinct inputs.

The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

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

1. System and environment

Fig. 1 illustrates a block diagram of a system 100 in accordance with various embodiments. In some embodiments, the system 100 may implement a digital assistant. The terms "digital assistant," "virtual assistant," "intelligent automated assistant," or "automatic digital assistant" may 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 make the inferred user intent, the system may perform one or more of the following: identifying a task flow by steps and parameters designed to achieve the inferred user intent, entering into the task flow specific requirements from the inferred user intent; executing a task flow by calling a program, method, service, API, etc.; and generating an output response to the user in audible (e.g., speech) and/or visual form.

In particular, the digital assistant may be capable of accepting user requests at least partially in the form of natural language commands, requests, statements, narratives and/or inquiries. In general, a user request may seek either an informational answer or a task performed by the digital assistant. A satisfactory response to a user request may be to provide a requested informational answer, to perform a requested task, or a combination of both. For example, a user may ask a digital assistant such as "where do i am present? "and the like. Based on the user's current location, the digital assistant may answer "you are near the central park siemens. A "user may also request to perform a task, such as" please invite my friend to join my girlfriend's birthday party on the next week. In response, the digital assistant can acknowledge the request by speaking "good, now" and then send an appropriate calendar invitation on behalf of the user to each of the user's friends listed in the user's electronic address book. During the performance of requested tasks, the digital assistant can sometimes interact with the user over a long period of time in a continuous conversation involving multiple exchanges of information. There are many other ways to interact with a digital assistant to request information or perform various tasks. In addition to providing verbal responses and taking programmed actions, the digital assistant can also provide responses in other visual or audio forms (e.g., as text, alerts, music, video, animation, etc.).

As shown in fig. 1, in some embodiments, the digital assistant may be implemented according to a client-server model. The digital assistant can include a client-side portion 102 (hereinafter "DA client 102") executing on a user device 104, and a server-side portion 106 (hereinafter "DA server 106") executing on a server system 108. The DA client 102 may communicate with the DA server 106 over one or more networks 110. The DA client 102 may provide client-side functionality such as user-oriented input and output processing and communication with the DA server 106. The DA server 106 may provide server-side functionality for any number of DA clients 102, each of the number of DA clients 102 located on a respective user device 104.

In some embodiments, DA server 106 may include 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 may facilitate client-facing input and output processing of the DA server 106. The one or more processing modules 114 may utilize the data and models 116 to process speech input and determine the user's intent based on natural language input. In addition, the one or more processing modules 114 perform task execution based on the inferred user intent. In some embodiments, DA server 106 may communicate with external services 120 over network 110 to complete tasks or collect information. An I/O interface 118 to external services may facilitate such communication.

The user device 104 may be any suitable electronic device. For example, the user device may be a portable multifunction device (e.g., device 200 described below with reference to fig. 2A), a multifunction device (e.g., device 400 described below with reference to fig. 4), or a personal electronic device (e.g., device 600 described below with reference to fig. 6A-6B). The portable multifunction device may be, for example, a mobile phone that also contains other functions, such as PDA and/or music player functions.Specific examples of portable multifunction devices can include that of Apple Inc (Cupertino, California)

And

an apparatus. Other examples of portable multifunction devices may include, but are not limited to, laptops or tablets. Additionally, in some embodiments, the user device 104 may be a non-portable multifunction device. In particular, the user device 104 may be a desktop computer, a game console, a television, or a television set-top box. In some embodiments, the user device 104 may include a touch-sensitive surface (e.g., a touchscreen display and/or a touchpad). In addition, the user device 104 may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick. Various embodiments of electronic devices, such as multifunction devices, are described in detail below.

Examples of communication network 110 may include a Local Area Network (LAN) and a Wide Area Network (WAN), such as the Internet. The communication network 110 may be implemented using any known network protocol, including various wired or wireless protocols, such as, for example, Ethernet, Universal Serial Bus (USB), FIREWIRE (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.

The server system 108 may be implemented on one or more stand-alone data processing devices or a distributed network of computers. In some embodiments, the server system 108 may also employ various virtual devices and/or services of a third party service provider (e.g., a third party cloud service provider) to provide the underlying computing resources and/or infrastructure resources of the server system 108.

In some embodiments, user device 104 may communicate with DA server 106 via second user device 122. The second user device 122 may be similar to or the same as the user device 104. For example, the second user equipment 122 may be similar to the

apparatus

200, 400, or 600 described below with reference to fig. 2A, 4, and 6A-6B. The user device 104 may be configured to communicatively couple to the second user device 122 via a direct communication connection (such as bluetooth, NFC, BTLE, etc.) or via a wired or wireless network (such as a local Wi-Fi network). In some embodiments, second user device 122 may be configured to act as a proxy between user device 104 and DA server 106. For example, DA client 102 of user device 104 may be configured to transmit information (e.g., a user request received at user device 104) to DA server 106 via second user device 122. DA server 106 may process the information and return relevant data (e.g., data content in response to a user request) to user device 104 via second user device 122.

In some embodiments, the user device 104 may be configured to transmit an abbreviated data request to the second user device 122 to reduce the amount of information transmitted from the user device 104. Second user device 122 may be configured to determine supplemental information to add to the abbreviated request to generate a full request to transmit to DA server 106. This system architecture may advantageously allow a user device 104 (e.g., a watch or similar compact electronic device) with limited communication capabilities and/or limited battery power to access services provided by DA server 106 by utilizing a second user device 122 (e.g., a mobile phone, laptop, tablet, etc.) with greater communication capabilities and/or battery power as a proxy for DA server 106. Although only two

user devices

104 and 122 are shown in fig. 1, it should be understood that system 100 may include any number and type of user devices configured in such a proxy configuration to communicate with DA server system 106.

Although the digital assistant shown in fig. 1 may include both a client-side portion (e.g., DA client 102) and a server-side portion (e.g., DA server 106), in some embodiments, the functionality of the digital assistant may be implemented as a standalone application installed on a user device. Moreover, the division of functionality between the client portion and the server portion of the digital assistant may vary in different implementations. For example, in some embodiments, the DA client may be a thin client that provides only user-oriented input and output processing functions, and delegates all other functions of the digital assistant to a backend server.

2. Electronic device

Attention is now directed to implementations of electronic devices for implementing a client-side portion of a digital assistant. FIG. 2A is a block diagram illustrating a portable multifunction device 200 with a touch-sensitive display system 112 in accordance with some embodiments. The touch sensitive display 212 is sometimes referred to as a "touch screen" for convenience, and may sometimes be referred to or called a "touch sensitive display system". Device 200 includes memory 202 (which optionally includes one or more computer-readable storage media), a memory controller 222, one or more processing units (CPUs) 220, a peripheral 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. The device 200 optionally includes one or more optical sensors 264. Device 200 optionally includes one or more contact intensity sensors 265 for detecting the intensity of contacts on device 200 (e.g., a touch-sensitive surface, such as touch-sensitive display system 212 of device 200). Device 200 optionally includes one or more tactile output generators 267 for generating tactile outputs on device 200 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 212 of device 200 or touch panel 455 of device 400). These components optionally communicate over one or more communication buses or signal lines 203.

As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (surrogate) for the force or pressure of a contact on the touch-sensitive surface. The intensity of the contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of the contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure forces at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated contact force. Similarly, the pressure sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereof, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereof, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereof, are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement of contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some implementations, the surrogate measurement of contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functionality that the user may not have access to on a smaller sized device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or physical/mechanical controls, such as knobs or buttons).

As used in this specification and claims, the term "haptic output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to a center of mass of the device that is to be detected by a user with the user's sense of touch. For example, where the device or component of the device is in contact with a surface of the user that is sensitive to touch (e.g., a finger, palm, or other portion of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a haptic sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of the touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down click" or "up click" of a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click," even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement is not moving. As another example, movement of the touch sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch sensitive surface even when the smoothness of the touch sensitive surface is unchanged. While such interpretation of touch by a user will be limited by the user's individualized sensory perception, many sensory perceptions of the presence of touch are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of a user (e.g., "up click," "down click," "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or a component thereof that would generate the sensory perception of a typical (or ordinary) user.

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

Memory 202 may include one or more computer-readable storage media. The computer-readable storage medium may be tangible and non-transitory. The memory 202 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 222 may control other components of device 200 to access memory 202.

In some embodiments, a non-transitory computer-readable storage medium of memory 202 may be used to store instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions (e.g., for performing aspects of

processes

1000 and 1100, as described below). In other embodiments, the instructions (e.g., for performing aspects of

processes

1000 and 1100, as described below) may be stored on a non-transitory computer-readable storage medium of server system 108, or may be distributed between the non-transitory computer-readable storage medium of memory 202 and the non-transitory computer-readable storage medium of server system 108. In the context of this document, a "non-transitory computer-readable storage medium" can be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device.

Peripheral interface 218 may be used to couple the input and output peripherals of the device to CPU 220 and memory 202. The one or more processors 220 execute or execute various software programs and/or sets of instructions stored in the memory 202 to perform various functions of the device 200 and process data. In some embodiments, peripherals interface 218, CPU 220, and memory controller 222 may be implemented on a single chip, such as chip 204. In some other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 208 receives and transmits RF signals, also known as electromagnetic signals. The RF circuitry 208 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 208 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and so forth. RF circuitry 208 optionally communicates with networks, such as the internet, also 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), as well as other devices via wireless communications. RF circuitry 208 optionally includes well-known circuitry for detecting Near Field Communication (NFC) fields, such as by short-range communication radios. The wireless communication optionally uses any of a number of communication standards, protocols, and techniques, 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 +, 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 low energy (BTLE), wireless fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over internet protocol (VoIP), Wi-MAX, email protocol (e.g., Internet Message Access Protocol (IMAP), and/or Post Office Protocol (POP)) Instant messaging (e.g., extensible messaging and presence protocol (XMPP), session initiation protocol with extensions for instant messaging and presence (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed at the filing date of this document.

Audio circuitry 210, speaker 211, and microphone 213 provide an audio interface between a user and device 200. The audio circuit 210 receives audio data from the peripheral interface 218, converts the audio data to an electrical signal, and transmits the electrical signal to the speaker 211. The speaker 211 converts the electrical signals into human-audible sound waves. The audio circuit 210 also receives electrical signals converted by the microphone 213 from sound waves. The audio circuit 210 converts the electrical signals to audio data and transmits the audio data to the peripheral interface 218 for processing. The audio data may be retrieved from the memory 202 and/or the RF circuitry 208 and/or transmitted to the memory 202 and/or the RF circuitry 208 by the peripheral interface 218. In some embodiments, the audio circuit 210 also includes a headset jack (e.g., 312 in fig. 3). The headset jack provides an interface between the audio circuitry 210 and a removable audio input/output peripheral such as an output-only headset or a headset having both an output (e.g., a monaural or binaural headset) and an input (e.g., a microphone).

The I/O subsystem 206 couples input/output peripheral devices on the device 200, such as the touch screen 212 and other input control devices 216, to a peripheral interface 218. I/O subsystem 206 optionally includes a display controller 256, an optical sensor controller 258, an intensity sensor controller 259, a haptic feedback controller 261, and one or more input controllers 260 for other input or control devices. The one or more input controllers 260 receive/transmit electrical signals from/to the other

input control devices

216, 116. Other input control devices 216 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, input controller 260 is optionally coupled to (or not coupled to) any of: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. The one or more buttons (e.g., 308 in fig. 3) optionally include an up/down button for volume control of the speaker 211 and/or microphone 213. The one or more buttons optionally include a push button (e.g., 306 in fig. 3).

A quick press of the push button unlocks the touch screen 212 or initiates the process of Unlocking the Device using a gesture on the touch screen, as described in U.S. patent application 11/322,549 entitled "Unlocking a Device by Performance testing on an Unlock Image," filed on 23.12.2005, and U.S. patent 7,657,849, which are hereby incorporated by reference in their entirety. Pressing the push button (e.g., 306) longer may turn the device 200 on or off. The user can customize the functionality of one or more buttons. The touch screen 212 is used to implement virtual or soft buttons and one or more soft keyboards.

The touch sensitive display 212 provides an input interface and an output interface between the device and the user. Display controller 256 receives electrical signals from touch screen 212 and/or transmits electrical signals to touch screen 112. Touch screen 212 displays visual output to a user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output may correspond to a user interface object.

Touch screen 212 has a touch-sensitive surface, sensor, or group of sensors that accept input from a user based on tactile and/or haptic contact. Touch screen 212 and display controller 256 (along with any associated modules and/or sets of instructions in memory 202) detect contact (and any movement or breaking of the contact) on touch screen 212 and convert the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch screen 212. In an exemplary embodiment, the point of contact between the touch screen 212 and the user corresponds to a finger of the user.

The touch screen 212 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. The touch screen 212 and display controller 256 may detect contact and any movement or breaking thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive technologies, resistive technologies, infrared technologies, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 212. In one exemplary embodiment, projected mutual capacitance sensing technology is used, such as that in Apple Inc. (Cupertino, California)

And iPod

The technique found.

The touch sensitive display in some embodiments of the touch screen 212 may be similar to the multi-touch sensitive touchpad described in the following U.S. patents: 6,323,846(Westerman et al), 6,570,557(Westerman et al) and/or 6,677,932 (Westerman); and/or U.S. patent publication 2002/0015024a1, each of which is hereby incorporated by reference in its entirety. However, touch screen 212 displays visual output from device 200, while touch sensitive touchpads do not provide visual output.

Touch sensitive displays in some embodiments of touch screen 212 may be as described in the following patent applications: (1) U.S. patent application 11/381,313, "Multipoint Touch Surface Controller," filed on 2.5.2006; (2) U.S. patent application 10/840,862, "Multipoint Touchscreen", filed 5/6/2004; (3) U.S. patent application 10/903,964, "Gestures For Touch Sensitive Input Devices," filed on 30.7.2004; (4) U.S. patent application 11/048,264, "Gestures For Touch Sensitive Input Devices," filed on 31/1/2005; (5) U.S. patent application 11/038,590, "model-Based Graphical User Interfaces For Touch Sensitive Input Devices," filed on 18.1.2005; (6) U.S. patent application 11/228,758, "Virtual Input Device plan On A Touch Screen User Interface", filed On 16.9.2005; (7) U.S. patent application 11/228,700, "Operation Of A Computer With A Touch Screen Interface," filed on 16.9.2005; (8) U.S. patent application 11/228,737, "Activating Virtual Keys Of A Touch-Screen Virtual Keys", filed on 16.9.2005; and (9) U.S. patent application 11/367,749, "Multi-Functional Hand-Held Device," filed 3.3.2006. All of these patent applications are incorporated herein by reference in their entirety.

The touch screen 212 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user may make contact with touch screen 212 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the action desired by the user.

In some embodiments, in addition to a touch screen, device 200 may include a touch pad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike a touch screen, does not display visual output. The touchpad may be a touch-sensitive surface separate from the touch screen 212 or an extension of the touch-sensitive surface formed by the touch screen.

The device 200 also includes a power system 262 for powering the various components. Power system 262 may include a power management system, one or more power sources (e.g., battery, Alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a Light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

The device 200 may also include one or more optical sensors 264. Fig. 2A shows an optical sensor coupled to optical sensor controller 258 in I/O subsystem 206. The optical sensor 264 may include a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 264 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 243 (also referred to as a camera module), the optical sensor 264 may capture still images or video. In some embodiments, the optical sensor is located on the back of device 200 opposite touch screen display 212 on the front of the device so that the touch screen display can be used as a viewfinder for still and/or video image acquisition. In some embodiments, the optical sensor is located in the front of the device so that images of the user can be acquired for the video conference while the user views other video conference participants on the touch screen display. In some implementations, the position of the optical sensor 264 can be changed by the user (e.g., by rotating a lens and sensor in the device housing) so that a single optical sensor 264 can be used with a touch screen display for both video conferencing and still image and/or video image capture.

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

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

Device 200 optionally further comprises one or more tactile output generators 267. Fig. 2A shows a tactile output generator coupled to a tactile feedback controller 261 in I/O subsystem 206. Tactile output generator 267 optionally includes one or more electro-acoustic devices such as speakers or other audio components; and/or an electromechanical device such as a motor, solenoid, electroactive aggregator, piezoelectric actuator, electrostatic actuator, or other tactile output generating component for converting energy into linear motion (e.g., a component for converting an electrical signal into a tactile output on the device). Contact intensity sensor 265 receives haptic feedback generation instructions from haptic feedback module 233 and generates haptic output on device 200 that can be felt by a user of device 200. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 212), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., into/out of the surface of device 200) or laterally (e.g., back and forth in the same plane as the surface of device 200). In some embodiments, at least one tactile output generator sensor is located on the back of device 200 opposite touch screen display 212, which is located on the front of device 200.

Device 200 may also include one or more accelerometers 268. Fig. 2A shows accelerometer 268 coupled to peripheral interface 218. Alternatively, accelerometer 268 may be coupled to input controller 260 in I/O subsystem 206. Accelerometer 268 may be implemented as described in the following U.S. patent publications: 20050190059 entitled "Acceleration-Based Detection System For Portable Electronic Devices" And 20060017692, entitled "Methods And applications For Operating A Portable Device Based On An Accelerator", the disclosures of which are both incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from the one or more accelerometers. Device 200 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the one or more accelerometers 268 for obtaining information about the position and orientation (e.g., portrait or landscape) of device 200.

In some embodiments, the software components stored in memory 202 include an operating system 226, a communication module (or set of instructions) 228, a contact/motion module (or set of instructions) 230, a graphics module (or set of instructions) 232, a text input module (or set of instructions) 234, a Global Positioning System (GPS) module (or set of instructions) 235, a digital assistant client module 229, and an application program (or set of instructions) 236. In addition, memory 202 may store data and models, such as user data and models 231. Further, in some embodiments, memory 202 (fig. 2A) or 470 (fig. 4) stores device/global internal state 257, as shown in fig. 2A, and fig. 4. Device/global internal state 257 includes one or more of: an active application state indicating which applications (if any) are currently active; display state indicating what applications, views, or other information occupy various areas of the touch screen display 212; sensor states including information obtained from the various sensors of the device and the input control device 216; and location information regarding the device's location and/or attitude.

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.

The communication module 228 facilitates communication with other devices through one or more external ports 224 and also includes various software components for processing data received by the RF circuitry 208 and/or the external ports 224. External port 224 (e.g., Universal Serial Bus (USB), firewire, etc.) is adapted to couple directly to other devices or indirectly through a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is an external port

(trademark of Apple inc.) the 30-pin connectors used on devices are the same or similar and/or compatible multi-pin (e.g., 30-pin) connectors.

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

In some embodiments, the contact/motion module 230 uses a set of one or more intensity thresholds to determine whether an operation has been performed by the user (e.g., determine whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds are determined as a function of software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and may be adjusted without changing the physical hardware of device 200). For example, the mouse "click" threshold of the trackpad or touchscreen can be set to any one of a wide range of predefined thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more intensity thresholds of a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting multiple intensity thresholds at once with a system-level click on an "intensity" parameter).

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

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

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

Haptic feedback module 233 includes various software components for generating instructions for use by haptic output generator 267 to produce haptic outputs at one or more locations on device 200 in response to user interaction with device 200.

Text input module 234, which may be a component of graphics module 232, provides a soft keyboard for entering text in a variety of applications, such as contacts 237, email 240, instant message 241, browser 247, and any other application that requires text input.

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

The digital assistant client module 229 may include various client-side digital assistant instructions for providing client-side functionality of the digital assistant. For example, the digital assistant client module 229 may be capable of accepting voice input (e.g., speech input), text input, touch input, and/or gesture input through various user interfaces of the portable multifunction device 200 (e.g., the microphone 213, the accelerometer 268, the touch-sensitive display system 212, the optical sensor 229, the other input control device 216, and so forth). The digital assistant client module 229 may also be capable of providing output in audio (e.g., speech output), visual, and/or tactile forms through various output interfaces of the portable multifunction device 200 (e.g., speaker 211, touch-sensitive display system 212, tactile output generator 267, etc.). For example, the output may be provided as voice, sound, alarm, text message, menu, graphics, video, animation, vibration, and/or a combination of two or more of the foregoing. During operation, digital assistant client module 229 may communicate with DA server 106 using RF circuitry 208.

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

In some embodiments, the digital assistant client module 229 may utilize various sensors, subsystems, and peripherals of the portable multifunction device 200 to gather additional information from the surroundings 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 embodiments, the digital assistant client module 229 may provide 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 embodiments, the digital assistant may also use the contextual information to determine how to prepare and communicate the output to the user. The context information may be referred to as context data.

In some embodiments, the contextual information accompanying the user input may include sensor information, such as lighting, ambient noise, ambient temperature, images or video of the surrounding environment, and the like. In some embodiments, the context information may also include physical states of the device, such as device orientation, device location, device temperature, power level, velocity, acceleration, motion pattern, cellular signal strength, and the like. In some embodiments, information related to the software state of the DA server 106 (e.g., running processes, installed programs, past and current network activities, background services, error logs, resource usage, etc.) and the software state of the portable multifunction device 200 can be provided to the DA server 106 as contextual information associated with user input.

In some embodiments, the digital assistant client module 229 may selectively provide 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 embodiments, the digital assistant client module 229 may also elicit additional input from the user via a natural language dialog or other user interface upon request by the DA server 106. The digital assistant client module 229 may communicate the additional input to the DA server 106 to assist the DA server 106 in intent inference and/or to satisfy the user intent expressed in the user request.

A more detailed description of the digital assistant is described below with reference to fig. 7A-7C. It should be appreciated that the digital assistant client module 229 may include any number of sub-modules of the digital assistant module 726 described below.

The application programs 236 may include the following modules (or sets of instructions), or a subset or superset thereof:

a contacts module 237 (sometimes also referred to as a contact list or contact list);

a phone module 238;

a video conferencing module 239;

an email client module 240;

an Instant Messaging (IM) module 241;

fitness support module 242;

a camera module 243 for still and/or video images;

an image management module 244;

a video player module;

a music player module;

a browser module 247;

a calendar module 248;

desktop applet modules 249 that may include one or more of the following: a weather desktop applet 249-1, a stock market desktop applet 249-2, a calculator desktop applet 249-3, an alarm desktop applet 249-4, a dictionary desktop applet 249-5, and other desktop applets acquired by the user and a desktop applet 249-6 created by the user;

a desktop applet creator module 250 for generating a user-created desktop applet 249-6;

a search module 251;

a video and music player module 252 that incorporates a video player module and a music player module;

a notepad module 253;

a map module 254; and/or

Online video module 255.

Examples of other application programs 236 that may be stored in memory 202 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

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

In conjunction with the RF circuitry 208, the audio circuitry 210, the speaker 211, the microphone 213, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, and the text input module 234, the phone module 238 may be used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in the contacts module 237, modify the entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As described above, wireless communication may use any of a number of communication standards, protocols, and technologies.

In conjunction with the RF circuitry 208, audio circuitry 210, speaker 211, microphone 213, touch screen 212, display controller 256, optical sensor 264, optical sensor controller 258, contact/motion module 230, graphics module 232, text input module 234, contacts module 237, and phone module 238, the video conference module 239 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants according to user instructions.

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, and text input module 234, email client module 240 includes executable instructions to create, send, receive, and manage emails in response to user instructions. In conjunction with the image management module 244, the e-mail client module 240 makes it very easy to create and send an e-mail having a still image or a video image photographed by the camera module 243.

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

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, text input module 234, GPS module 235, map module 254, and music player module, fitness support module 242 includes executable instructions for: creating fitness (e.g., with time, distance, and/or calorie burning goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating a sensor for monitoring fitness; selecting body-building music and playing; and displaying, storing and transmitting fitness data.

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

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

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, and text input module 234, browser module 247 includes executable instructions for browsing the internet (including searching for, linking to, receiving, and displaying web pages or portions thereof, and attachments and other files linked to web pages) according to user instructions.

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

In conjunction with the RF circuitry 208, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, the text input module 234, and the browser module 247, the desktop applet module 249 is a mini-application (e.g., a weather desktop applet 249-1, a stock market desktop applet 249-2, a calculator desktop applet 249-3, an alarm desktop applet 249-4, and a dictionary desktop applet 249-5) or a mini-application created by a user (e.g., a user-created desktop applet 249-6) that may be downloaded and used by the user. In some embodiments, the desktop applet includes an HTML (hypertext markup language) file, a CSS (cascading style sheet) file, and a JavaScript file. In some embodiments, the desktop applet includes an XML (extensible markup language) file and a JavaScript file (e.g., Yahoo! desktop applet).

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, text input module 234, and browser module 247, the desktop applet creator module 250 may be used by a user to create a desktop applet (e.g., to turn a user-specified portion of a web page into the desktop applet).

In conjunction with touch screen 212, display controller 256, contact/motion module 230, graphics module 232, and text input module 234, search module 251 includes executable instructions for searching 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.

In conjunction with the touch screen 212, display controller 256, contact/motion module 230, graphics module 232, audio circuitry 210, speakers 211, RF circuitry 208, and browser module 247, the video and music player module 252 includes executable instructions that allow a user to download and playback 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, rendering, or otherwise playing back video (e.g., on the touch screen 212 or on an external display connected via the external port 224). In some embodiments, the device 200 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple inc.).

In conjunction with the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, and the text input module 234, the notepad module 253 includes executable instructions to create and manage notepads, backlogs, and the like according to user instructions.

In conjunction with RF circuitry 208, touch screen 212, display controller 256, contact/motion module 230, graphics module 232, text input module 234, GPS module 235, and browser module 247, map module 254 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data related to stores and other points of interest at or near a particular location, and other location-based data) according to user instructions.

In conjunction with touch screen 212, display controller 256, contact/motion module 230, graphics module 232, audio circuit 210, speaker 211, RF circuit 208, text input module 234, email client module 240, and browser module 247, online video module 255 includes instructions that allow a user to access, browse, receive (e.g., by streaming and/or downloading), play back (e.g., on the touch screen or on an external display connected via external port 224), send emails with links to particular online videos, and otherwise manage online videos in one or more file formats, such as h.264. In some embodiments, a link to a particular online video is sent using instant messaging module 241 rather than email client module 240. Additional descriptions of Online video applications may be found in U.S. provisional patent application 60/936,562 entitled "Portable Multi function Device, Method, and Graphical User Interface for Playing Online video", filed on year 2007, 20, and U.S. patent application 11/968,067 entitled "Portable Multi function Device, Method, and Graphical User Interface for Playing Online video", filed on year 2007, 31, which are both hereby incorporated by reference in their entirety.

Each of the modules and applications described above corresponds to a set of executable instructions for performing one or more of the functions described above as well as the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, a video player module may be combined with a music player module into a single module (e.g., video and music player module 252 in fig. 2A). In some embodiments, memory 202 may store a subset of the modules and data structures described above. Further, memory 202 may store additional modules and data structures not described above.

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

The predefined set of functions performed exclusively by the touchscreen and/or touchpad optionally include navigating between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 200 from any user interface displayed on device 200 to a main, home, or root menu. In such embodiments, a touchpad is used to implement a "menu button". In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

Fig. 2B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 202 (FIG. 2A) or memory 470 (FIG. 4) includes event classifier 270 (e.g., in operating system 226) and corresponding application 236-1 (e.g., any of the

aforementioned applications

237, 251, 255, 480, 490).

The event sorter 270 receives the event information and determines the application 236-1 to which the event information is to be delivered and the application view 291 of the application 236-1. The event sorter 270 includes an event monitor 271 and an event dispatcher module 274. In some embodiments, the application 236-1 includes an application internal state 292 that indicates a current application view that is displayed on the 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) are currently active, and application internal state 292 is used by event classifier 270 to determine the application view 291 to which to deliver event information.

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

The event monitor 271 receives event information from the peripheral interface 218. The event information includes information about a sub-event (e.g., a user touch on the touch-sensitive display 212 as part of a multi-touch gesture). Peripherals interface 218 transmits information it receives from I/O subsystem 206 or sensors (such as proximity sensor 266), accelerometer 268, and/or microphone 213 (through audio circuitry 210). Information received by peripheral interface 218 from I/O subsystem 206 includes information from touch-sensitive display 212 or a touch-sensitive surface.

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

In some embodiments, event classifier 270 also includes hit view determination module 272 and/or activity event recognizer determination module 273.

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

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 respective application) in which the touch is detected may correspond to a programmatic level within a programmatic or view hierarchy of applications. For example, the lowest level view in which a touch is detected may be referred to as a hit view, and the set of events identified as correct inputs may be determined based at least in part on the hit view of the initial touch that began the touch-based gesture.

Hit view determination module 272 receives information related to sub-events of the touch-based gesture. When the application has multiple views organized in a hierarchy, hit view determination module 272 identifies the hit view as the lowest view in the hierarchy that should handle the sub-event. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in the sequence of sub-events that form an event or potential event) occurs. Once the hit view is identified by hit view determination module 272, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

The activity event identifier determination module 273 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some implementations, the activity event recognizer determination module 273 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognizer determination module 273 determines that all views that include the physical location of the sub-event are actively participating views, and thus determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with one particular view, the higher views in the hierarchy will remain as actively participating views.

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

In some embodiments, the operating system 226 includes an event classifier 270. Alternatively, the application 236-1 includes an event classifier 270. In other embodiments, the event classifier 270 is a separate module or is part of another module stored in the memory 202 (such as the contact/motion module 230).

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

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

Event receiver 282 receives event information from event sorter 270. The event information includes information about a sub-event (e.g., a touch or touch movement). According to the sub-event, the event information further includes additional information, such as the location of the sub-event. When the sub-event involves motion of a touch, the event information may also include the velocity and direction of the sub-event. In some embodiments, the event comprises rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information comprises corresponding information about the current orientation of the device (also referred to as the device pose).

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

In some embodiments, the event definitions 287 include definitions of events for respective user interface objects. In some embodiments, event comparator 284 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view that displays three user interface objects on the touch-sensitive display 212, when a touch is detected on the touch-sensitive display 212, the 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 results of the hit test to determine which event handler 290 should be activated. For example, the event comparator 284 selects the event handler associated with the sub-event and the object that triggered the hit test.

In some embodiments, the definition of the respective event (287) further comprises a delay action that delays the delivery of the event information until it has been determined whether the sequence of sub-events does or does not correspond to the event type of the event recognizer.

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

In some embodiments, the respective event recognizer 280 includes metadata 283 with configurable attributes, tags, and/or lists for indicating how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 283 includes configurable attributes, flags, and/or lists that indicate how event recognizers may interact with each other or be enabled to interact with each other. In some embodiments, metadata 283 includes configurable attributes, tags, and/or lists that indicate whether a sub-event is delivered to a different level in the view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the respective event identifier 280 activates the event handler 290 associated with the event. In some embodiments, the respective event identifier 280 delivers event information associated with the event to the event handler 290. Activating the event handler 290 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, event recognizer 280 throws a marker associated with the recognized event, and event handler 290 associated with the marker retrieves the marker and performs a predefined process.

In some embodiments, the event delivery instructions 288 include sub-event delivery instructions that deliver event information about sub-events without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the sequence of sub-events or to actively participating views. Event handlers associated with the sequence of sub-events or with actively participating views receive the event information and perform a predetermined process.

In some embodiments, the data updater 276 creates and updates data used in the application 236-1. For example, the data updater 276 updates a phone number used in the contacts module 237 or stores a video file used in the video player module. In some embodiments, the object updater 277 creates and updates objects used in the application 236-1. For example, object updater 277 creates a new user interface object or updates the location of a user interface object. The GUI updater 278 updates the GUI. For example, GUI updater 278 prepares display information and sends it to graphics module 232 for display on a touch-sensitive display.

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

It should be understood that the above discussion of event processing with respect to user touches on a touch sensitive display also applies to other forms of user input utilizing an input device to operate multifunction device 200, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in combination with single or multiple keyboard presses or holds; contact movements on the touchpad, such as taps, drags, scrolls, and the like; inputting by a stylus; movement of the device; verbal instructions; the detected eye movement; inputting biological characteristics; and/or any combination thereof, is optionally used as input corresponding to a sub-event defining an event to be identified.

Fig. 3 illustrates a portable multifunction device 200 with a touch screen 212 in accordance with some embodiments. The touch screen optionally displays one or more graphics within a User Interface (UI) 300. In this embodiment, as well as other embodiments described below, a user can select one or more of these graphics by making gestures on the graphics, for example, with one or more fingers 302 (not drawn to scale in the figures) or with one or more styluses 303 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics will occur when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, up, and/or down), and/or a rolling of a finger (right to left, left to right, up, and/or down) that has made contact with device 200. In some implementations, or in some cases, inadvertent contact with a graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over the application icon optionally does not select the respective application.

Device 200 may also include one or more physical buttons, such as a "home" button or menu button 304. As previously described, the menu button 304 may be used to navigate to any application 236 in a set of applications that may be executed on the device 200. Alternatively, in some embodiments, the menu buttons are implemented as soft keys in a GUI displayed on touch screen 212.

In some embodiments, device 200 includes a touch screen 212, menu buttons 304, a push button 306 for powering the device on/off and for locking the device, one or more volume adjustment buttons 308, a Subscriber Identity Module (SIM) card slot 310, a headset jack 312, and a docking/charging external port 224. The push button 306 is optionally used to: powering on/off the device by pressing and maintaining the button in a depressed state for a predetermined time interval; locking the device by pressing the button and releasing the button before a predetermined time interval has elapsed; and/or unlocking the device or initiating an unlocking process. In an alternative embodiment, device 200 also accepts voice input through microphone 213 for activating or deactivating certain functions. Device 200 also optionally includes one or more contact intensity sensors 265 for detecting the intensity of contacts on touch screen 212, and/or one or more tactile output generators 267 for generating tactile outputs for a user of device 200.

FIG. 4 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. The device 400 need not be portable. In some embodiments, the device 400 is a laptop, desktop, tablet, multimedia player device, navigation device, educational device (such as a child 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. The communication bus 420 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 400 includes an input/output (I/O) interface 430 with a display 440, which is typically a touch screen display. The I/O interface 430 also optionally includes a keyboard and/or mouse (or other pointing device) 450 and a touchpad 455, a tactile output generator 457 (e.g., similar to one or more tactile output generators 267 described above with reference to fig. 2A), a sensor 459 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch-sensitive sensor, and/or a contact intensity sensor similar to one or more contact intensity sensors 265 described above with reference to fig. 2A) for generating tactile outputs on the device 400. Memory 470 includes high-speed random access memory such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices or other non-volatile solid state storage devices. Memory 470 optionally includes one or more storage devices located remotely from CPU 410. In some embodiments, memory 470 stores programs, modules, and data structures similar to or a subset of the programs, modules, and data structures stored in memory 202 of portable multifunction device 200 (fig. 2A). In addition, memory 470 optionally stores additional programs, modules, and data structures not present in memory 202 of portable multifunction device 200. For example, memory 470 of device 400 optionally stores drawing module 480, presentation module 482, word processing module 484, website creation module 486, disk editing module 488, and/or spreadsheet module 490, while memory 202 of portable multifunction device 200 (FIG. 2A) optionally does not store these modules.

Each of the above-described elements in fig. 4 may be stored in one or more of the aforementioned memory devices. Each of the above modules corresponds to a set of instructions for performing a function described above. The modules or programs (e.g., sets of instructions) described above need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, memory 470 may store a subset of the modules and data structures described above. In addition, memory 470 may store additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces that may be implemented on, for example, portable multifunction device 200.

Figure 5A illustrates an exemplary user interface of an application menu on portable multifunction device 100 in accordance with some embodiments. A similar user interface may be implemented on device 400. In some embodiments, the user interface 500 includes the following elements, or a subset or superset thereof:

signal strength indicators 502 for wireless communications (such as cellular signals and Wi-Fi signals);

time 504;

a bluetooth indicator 505;

a battery status indicator 506;

tray 508 with common application icons such as:

icon 516 of phone module 238 marked "phone", the icon 416 optionally including an indicator 514 of the number of missed calls or voice messages;

an icon 518 for the email client module 240 labeled "mail", the icon 518 optionally including an indicator 510 of the number of unread emails;

icon 520 of browser module 247 labeled "browser"; and

an icon 522 labeled "iPod" for the video and music player module 252 (also known as iPod (trademark of Apple inc.) module 252); and

icons for other applications, such as:

icon 524 of IM module 241 labeled "message";

icon 526 of calendar module 248 labeled "calendar";

icon 528 of image management module 244 labeled "photo";

icon 530 of camera module 243 labeled "camera";

icon 532 for online video module 255 labeled "online video";

an icon 534 labeled "stock market" for the O-stock desktop applet 249-2;

icon 536 for the map module 254 labeled "map";

icon 538 for weather desktop applet 249-1 labeled "weather";

icon 540 labeled "clock" for alarm clock desktop applet 249-4;

icon 542 labeled "fitness support" for fitness support module 242;

icon 544 labeled "notepad" for notepad module 253; and

icon 546 labeled "settings" for setting applications or modules, this icon 446 providing access to settings of device 200 and its various applications 236.

It should be noted that the icon labels shown in fig. 5A are merely exemplary. For example, icon 522 of video and music player module 252 may optionally be labeled "music" or "music player". Other tabs are optionally used for various application icons. In some embodiments, the label of the respective application icon includes a name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

Fig. 5B illustrates an exemplary user interface on a device (e.g., device 400 of fig. 4) having a touch-sensitive surface 551 (e.g., tablet or touchpad 455 of fig. 4) separate from a display 550 (e.g., touchscreen display 212). The device 400 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 457) for detecting the intensity of contacts on the touch-sensitive surface 551 and/or one or more tactile output generators 459 for generating tactile outputs for a user of the device 400.

Although some of the examples that follow will be given with reference to input on the touch screen display 212 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in fig. 5B. In some implementations, the touch-sensitive surface (e.g., 551 in fig. 5B) has a major axis (e.g., 552 in fig. 5B) that corresponds to a major axis (e.g., 553 in fig. 5B) on the display (e.g., 550). According to these embodiments, the device detects contacts (e.g., 560 and 562 in fig. 5B) with the touch-sensitive surface 551 at locations that correspond to respective locations on the display (e.g., 560 corresponds to 568 and 562 corresponds to 570 in fig. 5B). As such, when the touch-sensitive surface (e.g., 551 in fig. 5B) is separated from the display (550 in fig. 5B) of the multifunction device, user inputs (e.g.,

contacts

560 and 562 and their movements) detected by the device on the touch-sensitive surface are used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contact, single-finger tap gesture, finger swipe gesture), it should be understood that in some embodiments one or more of these finger inputs are replaced by inputs from another input device (e.g., mouse-based inputs or stylus inputs). For example, the swipe gesture is optionally replaced by a mouse click (e.g., rather than a contact) followed by movement of the cursor along the path of the swipe (e.g., rather than movement of the contact). As another example, a flick gesture is optionally replaced by a mouse click (e.g., rather than detection of a contact followed by termination of detection of the contact) while the cursor is over the location of the flick gesture. Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mouse and finger contacts are optionally used simultaneously.

Fig. 6A illustrates an exemplary personal electronic device 600. The device 600 includes a body 602. In some embodiments, device 600 may include some or all of the features described for devices 200 and 400 (e.g., fig. 2A-4). In some embodiments, device 600 has a touch-sensitive display screen 604, hereinafter referred to as touch screen 604. Instead of or in addition to the touch screen 604, the device 600 has a display and a touch-sensitive surface. As with devices 200 and 400, in some embodiments, touch screen 604 (or touch-sensitive surface) may have one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). One or more intensity sensors of touch screen 604 (or touch-sensitive surface) may provide output data representing the intensity of a touch. The user interface of device 600 may respond to the touch based on the strength of the touch, meaning that different strengths of the touch may invoke different user interface operations on device 600.

Techniques for detecting and processing touch intensity can be found, for example, in the following related patent applications: international patent Application Ser. No. PCT/US2013/040061 entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects reforming to an Application", filed on 8.5.2013, and International patent Application Ser. No. PCT/US2013/069483 entitled "Device, Method, and Graphical User Interface for translating Betwen Touch Input to Display Output references", filed 11.11.2013, each of which is hereby incorporated by reference in its entirety.

In some embodiments, device 600 has one or

more input mechanisms

606 and 608. Input mechanisms 606 and 608 (if included) may be in physical 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, may allow device 600 to be attached with, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watchband, bracelet, pants, belt, shoe, purse, backpack, and the like. These attachment mechanisms may allow the user to wear the device 600.

Fig. 6B illustrates an exemplary personal electronic device 600. In some embodiments, the apparatus 600 may include some or all of the components described with reference to fig. 2A, 2B, and 4. The device 600 has a bus 612 that operatively couples an I/O portion 614 with one or more computer processors 616 and a memory 618. I/O portion 614 may be connected to display 604, which may have touch sensitive component 622 and optionally may also have touch intensity sensitive component 624. Further, I/O portion 614 may connect with communications unit 630 for receiving applications and operating system data using Wi-Fi, bluetooth, Near Field Communication (NFC), cellular, and/or other wireless communication technologies. Device 600 may include input mechanisms 606 and/or 608. For example, input mechanism 606 may be a rotatable input device or a depressible input device as well as a rotatable input device. In some examples, input mechanism 608 may be a button.

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

The memory 618 of the personal electronic device 600 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by the one or more computer processors 616, may, for example, cause the computer processors to perform the techniques described below, including the processes 1000 and 1100 (fig. 10-11). The personal electronic device 600 is not limited to the components and configuration of fig. 6B, but may include other components or additional components in a variety of configurations.

As used herein, the term "affordance" refers to a user-interactive graphical user interface object that may be displayed on a display screen of device 200, 400, and/or 600 (FIGS. 2, 4, and 6). For example, images (e.g., icons), buttons, and text (e.g., links) can each constitute an affordance.

As used herein, the term "focus selector" refers to an input element that is used to indicate the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touch pad 455 in fig. 4 or touch-sensitive surface 551 in fig. 5B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 212 in fig. 2A or touch screen 212 in fig. 5A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a "focus selector" such that when an input (e.g., a press input by the contact) is detected at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by moving the focus from one button to another using tab or arrow keys); in these implementations, the focus selector moves according to focus movement between different regions of the user interface. Regardless of the particular form taken by the focus selector, the focus selector is typically a user interface element (or contact on a touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element with which the user of the user interface desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a touchpad or touchscreen), the location of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate that the user desires to activate the respective button (as opposed to other user interface elements shown on the device display).

As used in the specification and in the 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 a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples acquired during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detecting contact, before detecting contact lift, before or after detecting contact start movement, before or after detecting contact end, before or after detecting an increase in intensity of contact, and/or before or after detecting a decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of: maximum value of contact strength, mean value of contact strength, average value of contact strength, value at the first 10% of contact strength, half maximum value of contact strength, 90% maximum value of contact strength, and the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact whose characteristic intensity does not exceed the first threshold results in a first operation, a contact whose characteristic intensity exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact whose characteristic intensity exceeds the second threshold results in a third operation. In some embodiments, the comparison between the characteristic strength and the one or more thresholds is used to determine whether to perform the one or more operations (e.g., whether to perform the respective operation or to forgo performing the respective operation), rather than to determine whether to perform the first operation or the second operation.

In some implementations, a portion of the gesture is recognized for determining the characteristic intensity. For example, the touch-sensitive surface may receive a continuous swipe contact that transitions from a starting location and reaches an ending location where the intensity of the contact increases. In this example, the characteristic strength of the contact at the end position may be based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some implementations, a smoothing algorithm may be applied to the intensity of the swipe gesture before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: a non-weighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for the purpose of determining the feature intensity.

The intensity of a contact on the touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity that: at which intensity the device will perform the operations typically associated with clicking a button or touchpad of a physical mouse. In some embodiments, the deep press intensity threshold corresponds to an intensity that: at which intensity the device will perform a different operation than that typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected whose characteristic intensity is below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, a contact below the nominal contact detection intensity threshold is no longer detected), the device will move the focus selector in accordance with movement of the contact on the touch-sensitive surface without performing operations associated with a light press intensity threshold or a deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface drawings.

Increasing the contact characteristic intensity from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. Increasing the contact characteristic intensity from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. Increasing the contact characteristic intensity from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. The decrease in contact characteristic intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a lift of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

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

In some embodiments, the device employs intensity hysteresis to avoid accidental input sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold having a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting a subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold and optionally a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in intensity of the contact or a decrease in intensity of the contact, depending on the circumstances).

For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input is triggered in response to detection of any of the following: the contact intensity increases above the press input intensity threshold, the contact intensity increases from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, the contact intensity decreases below the press input intensity threshold, and/or the contact intensity decreases below the hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples in which operations are described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operations are optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

3. Digital assistant system

Fig. 7A illustrates a block diagram of a digital assistant system 700 according to various embodiments. In some embodiments, the digital assistant system 700 may be implemented on a stand-alone computer system. In some embodiments, the digital assistant system 700 may be distributed across multiple computers. In some embodiments, some of the modules and functionality of the digital assistant can be divided into a server portion and a client portion, where the client portion is located on one or more user devices (e.g.,

user devices

104, 122, 200, 400, or 600) and communicates with the server portion (e.g., server system 108) over one or more networks, for example as shown in fig. 1. In some embodiments, digital assistant system 700 may be a specific implementation of server system 108 (and/or DA server 106) shown in fig. 1. It should be noted that the digital assistant system 700 is only one example of a digital assistant system, and that the digital assistant system 700 may have more or fewer components than illustrated, may combine two or more components, or may have a different configuration or layout of the components. The various components shown in fig. 7A may be 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.

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

In some embodiments, the memory 702 may include a non-transitory computer-readable medium, such as high-speed random access memory and/or a non-volatile computer-readable storage medium (e.g., one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices).

In some embodiments, the I/O interface 706 may couple input/output devices 716, such as a display, a keyboard, a touch screen, and a microphone, of the digital assistant system 700 to the user interface module 722. I/O interface 706, in conjunction with user interface module 722, can receive user inputs (e.g., voice inputs, keyboard inputs, touch inputs, etc.) and process those inputs accordingly. In some embodiments, such as when the digital assistant is implemented on a standalone user device, the digital assistant system 700 may include any of the components and I/O communication interfaces described with respect to the

devices

200, 400, or 600 in fig. 2A, 4, 6A-6B, respectively. In some embodiments, the digital assistant system 700 may represent a server portion of a digital assistant implementation and may interact with a user through a client-side portion located on a user device (e.g.,

device

104, 200, 400, or 600).

In some embodiments, the network communication interface 708 may include a wired communication port 712 and/or wireless transmit and receive circuitry 714. The wired communication port may receive and transmit communication signals via one or more wired interfaces, such as ethernet, Universal Serial Bus (USB), firewire, and the like. The wireless circuitry 714 may receive and transmit RF and/or optical signals to and from communication networks and other communication devices. The wireless communication may use 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 may enable communication of the digital assistant system 700 with other devices via a network, such as the internet, an intranet, and/or a wireless network, such as a cellular telephone network, a wireless Local Area Network (LAN), and/or a Metropolitan Area Network (MAN).

In some embodiments, memory 702, or a computer-readable storage medium of memory 702, may store programs, modules, instructions, and data structures, including all or a subset of the following: an operating system 718, a communications module 720, a user interface module 722, one or more application programs 724, and a digital assistant module 726. In particular, memory 702 or the computer-readable storage medium of memory 702 may store instructions for performing

processes

1000 and 1100 described below. The one or more processors 704 may execute the programs, modules, and instructions and read/write data from/to data structures.

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

The communication module 720 may facilitate communications between the digital assistant system 700 and other devices via the network communication interface 708. For example, the communication module 720 may communicate with the RF circuitry 208 of an electronic device, such as the

devices

200, 400, and 600 shown in fig. 2A, 4, and 6A-6B, respectively. The communications module 720 may also include various components for processing data received by the wireless circuitry 714 and/or the wired communications port 712.

User interface module 722 may receive commands and/or input from a user (e.g., from a keyboard, touch screen, pointing device, controller, and/or microphone) via I/O interface 706 and generate user interface objects on the display. The user interface module 722 may also prepare and communicate output (e.g., voice, sound, animation, text, icons, vibrations, haptic feedback, lighting, etc.) to the user via the I/O interface 706 (e.g., through a display, audio channels, speakers, and touch pad, etc.).

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

The memory 702 may also store a digital assistant module 726 (or a server portion of a digital assistant). In some embodiments, digital assistant module 726 may include the following sub-modules, or a subset or superset thereof: an input/output processing module 728, a Speech To Text (STT) processing module 730, a natural language processing module 732, a conversation stream processing module 734, a task stream processing module 736, a services processing module 738, and a speech synthesis module 740. Each of these modules may have access to one or more of the following systems or data and models of digital assistant module 726, or a subset or superset thereof: ontology 760, vocabulary index 744, user data 748, task flow model 754, service model 756, and ASR system.

In some embodiments, 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 the speech input to text; identifying a user's intent expressed in a natural language input received from a user; actively elicit and obtain information needed to fully infer a user's intent (e.g., by disambiguating words, names, intentions, etc.); determining a task flow for implementing the inferred intent; and executing the task flow to achieve the inferred intent.

In some embodiments, as shown in fig. 7B, I/O processing module 728 may interact with a user through I/O device 716 in fig. 7A or with a user device (e.g.,

device

104, 200, 400, or 600) through network communication interface 708 in fig. 7A to obtain user input (e.g., voice input) and provide a response to the user input (e.g., as voice output). The I/O processing module 728 optionally may obtain contextual information associated with the user input along with or shortly after receiving the user input from the user device. The contextual information may include user-specific data, vocabulary, and/or preferences related to user input. In some embodiments, the context information also includes software and hardware states of the user device at the time the user request is received, and/or information relating to the user's surroundings at the time the user request is received. In some embodiments, the I/O processing module 728 may also send follow-up questions to the user regarding the user request and receive answers from the user. When a user request is received by the I/O processing module 728 and the user request may include speech input, the I/O processing module 728 may forward the speech input to the STT processing module 730 (or speech recognizer) for speech-to-text conversion.

STT processing module 730 may include one or more ASR systems. The one or more ASR systems may process the speech input received through the I/O processing module 728 to generate recognition results. Each ASR system may include a front-end speech preprocessor. The front-end speech preprocessor can extract representative features from the speech input. For example, a front-end speech preprocessor may perform a fourier transform on a speech input to extract spectral features that characterize the speech input as a representative sequence of multidimensional vectors. Additionally, each ASR system may include one or more speech recognition models (e.g., acoustic and/or language models), and may implement one or more speech recognition engines. Examples of speech recognition models may include hidden markov models, gaussian mixture models, deep neural network models, N-gram language models, and other statistical models. Examples of speech recognition engines may include dynamic time warping based engines and Weighted Finite State Transformer (WFST) based engines. One or more speech recognition models and one or more speech recognition engines may be used to process the representative features extracted by the front-end speech preprocessor to generate intermediate recognition results (e.g., phonemes, phoneme strings, and subwords) and, ultimately, text recognition results (e.g., words, word strings, or symbol sequences). In some embodiments, the speech input may be processed, at least in part, by a third party service or on the user's device (e.g.,

device

104, 200, 400, or 600) to generate the recognition result. Once STT processing module 730 generates a recognition result containing a text string (e.g., a word, or a sequence of words, or a sequence of symbols), the recognition result may be passed to natural language processing module 732 for intent inference.

More details regarding the processing of Speech to text are described in U.S. utility model patent application serial No. 13/236,942 entitled "Consolidating Speech recognitions Results" filed on 20/9/2011, the entire disclosure of which is incorporated herein by reference.

In some embodiments, STT processing module 730 may include and/or may access the vocabulary of recognizable words via speech alphabet conversion module 731. Each vocabulary word may be associated with one or more candidate pronunciations of the word represented in the speech recognition phonetic alphabet. In particular, the vocabulary of recognizable words may include words associated with multiple candidate pronunciations. For example, the vocabulary may include candidate pronunciations

And

the associated word "tomato". Additionally, the vocabulary words may be associated with custom candidate pronunciations based on previous speech input from the user. Such custom candidate pronunciations can be stored in STT processing module 730 and can be associated with a particular user via a user profile on the device. In some embodiments, candidate pronunciations for a word may be determined based on the spelling of the word and one or more linguistic and/or phonetic rules. In some embodiments, the candidate pronunciation may be based on, for example, knowledgeStandard pronunciation and manual generation.

In some embodiments, the candidate pronunciations may be ranked based on the prevalence of the candidate pronunciations. For example, candidate pronunciations

Ratio of rankable

High because the former is a more commonly used pronunciation (e.g., among all users, for users in a particular geographic area, or for any other suitable subset of users). In some embodiments, the candidate pronunciations may be ranked based on whether the candidate pronunciation is a custom candidate pronunciation associated with the user. For example, custom candidate pronunciations can be ranked higher than canonical candidate pronunciations. This may be useful for identifying proper nouns with a unique pronunciation different from the canonical pronunciation. In some embodiments, the candidate pronunciations may be associated with one or more speech characteristics (such as geographic origin, country, or ethnicity). For example, candidate pronunciations

Can be associated with the United states to make candidate pronunciations

May be associated with the united kingdom. Additionally, the ranking of candidate pronunciations may be associated based on one or more characteristics of the user (e.g., geographic origin, country, race, etc.) stored in the user profile on the device. For example, it may be determined from a profile of the user that the user is associated with the United states. Based on the user's association with the United states, a candidate pronunciation (associated with the United states)

Candidate pronunciations (associated with the United kingdom) may be ranked

And higher. In some embodiments, one of the ranked candidate pronunciations may be selected as a pre-candidate pronunciationMeasured pronunciation (e.g., most likely pronunciation).

When a speech input is received, STT processing module 730 may be used to determine a phoneme (e.g., using an acoustic model) corresponding to the speech input, and then attempt to determine a word matching the phoneme (e.g., using a language model). For example, if STT processing module 730 may first identify a phoneme sequence corresponding to a portion of a speech input

It may then determine that this sequence corresponds to the word "tomato" based on the vocabulary index 744.

In some embodiments, STT processing module 730 may use approximate matching techniques to determine words in the utterance. Thus, for example, STT processing module 730 may determine a phoneme sequence

Corresponding to the word "tomato", even though the particular phoneme sequence is not one of the candidate phoneme sequences for that word.

The natural language processing module 732 ("natural language processor") of the digital assistant may take the sequence of words or symbols ("symbol sequence") generated by the STT processing module 730 and attempt to associate the symbol sequence with one or more "actionable intents" identified by the digital assistant. An "actionable intent" may represent a task that may be performed by a digital assistant and that may have an associated task flow implemented in task flow model 754. The associated task stream may be a series of programmed actions and steps taken by the digital assistant to perform the task. The capability scope of the digital assistant may depend on the number and variety of task flows that have been implemented and stored in task flow model 754, or in other words, may depend on the number and variety of "actionable intents" that the digital assistant recognizes. However, the effectiveness of a digital assistant may also depend on the assistant's ability to infer the correct "actionable intent" from a user request expressed in natural language.

In some embodiments, in addition to the sequence of words or symbols obtained from STT processing module 730, natural language processing module 732 may also receive context information associated with the user request, such as from I/O processing module 728. The natural language processing module 732 may optionally use the context information to clarify, supplement, and/or further define information contained in the sequence of symbols received from the STT processing module 730. Contextual information may include, for example, user preferences, hardware and/or software states of the user device, sensor information collected before, during, or shortly after a user request, previous interactions (e.g., conversations) between the digital assistant and the user, and so forth. As described herein, contextual information may be dynamic and may vary with time, location, dialog content, and other factors.

In some embodiments, the natural language processing may be based on, for example, ontology 760. Ontology 760 may be a hierarchical structure containing a number of nodes, each node representing an "actionable intent" or "attribute" related to one or more of the "actionable intents" or other "attributes". As described above, "actionable intent" may refer to a task that a digital assistant is capable of performing, i.e., that is "executable" or can be performed. An "attribute" may represent a parameter associated with a sub-aspect of an executable intent or another attribute. The connection between the actionable intent node and the property node in ontology 760 may define how the parameters represented by the property node pertain to the task represented by the actionable intent node.

In some embodiments, ontology 760 may be composed of actionable intent nodes and attribute nodes. Within ontology 760, each actionable intent node may be connected to one or more property nodes directly or through one or more intermediate property nodes. Similarly, each property node may be connected directly to one or more actionable intent nodes or through one or more intermediate property nodes. For example, as shown in FIG. 7C, ontology 760 can include a "restaurant reservation" node (i.e., an actionable intent node). The property nodes "restaurant," "date/time" (for reservation), and "party size" may all be directly connected to the actionable intent node (i.e., "restaurant reservation" node).

Further, the property nodes "cuisine," price interval, "" phone number, "and" location "may be child nodes of the property node" restaurant, "and may each be connected to the" restaurant reservation "node (i.e., actionable intent node) through an intermediate property node" restaurant. As another example, as shown in fig. 7C, ontology 760 may also include a "set reminder" node (i.e., another actionable intent node). The property node "date/time" (for set reminders) and "subject" (for reminders) may both be connected to the "set reminders" node. Since the attribute "date/time" may be related to both the task of making a restaurant reservation and the task of setting a reminder, the attribute node "date/time" may be connected to both the "restaurant reservation" node and the "set reminder" node in ontology 760.

The actionable intent node along with the concept nodes to which it connects may be described as a "domain". In the present discussion, each domain may be associated with a respective actionable intent and refer to a set of nodes (and relationships between those nodes) associated with a particular actionable intent. For example, ontology 760 shown in fig. 7C may include an example of restaurant reservation domain 762 and an example of reminder domain 764 within ontology 760. The restaurant reservation domain includes the actionable intent node "restaurant reservation," the property nodes "restaurant," date/time, "and" party size, "and the child property nodes" cuisine, "" price interval, "" phone number, "and" location. The reminder field 764 may include the executable intent node "set reminder" and the property nodes "subject" and "date/time". In some embodiments, ontology 760 may be composed of multiple domains. Each domain may share one or more attribute nodes with one or more other domains. For example, in addition to the restaurant reservation field 762 and reminder field 764, the "date/time" property node may be associated with many different fields (e.g., a scheduling field, a travel reservation field, a movie tickets field, etc.).

Although fig. 7C shows two exemplary domains within ontology 760, other domains may include, for example, "find movie," "initiate phone call," "find direction," "arrange meeting," "send message," and "provide answer to question," "read list," "provide navigation instructions," "provide instructions for task," etc. The "send message" field may be associated with a "send message" actionable intent node and may also include attribute nodes such as "recipient", "message type", and "message body". The attribute node "recipient" may be further defined, for example, by child attribute nodes such as "recipient name" and "message address".

In some embodiments, ontology 760 may include all domains (and thus actionable intents) that a digital assistant is able to understand and act upon. In some embodiments, ontology 760 can be modified, such as by adding or removing entire domains or nodes, or by modifying relationships between nodes within ontology 760.

In some embodiments, nodes associated with multiple related executables may be clustered under a "super domain" in ontology 760. For example, a "travel" super-domain may include a cluster of attribute nodes and actionable intent nodes related to travel. Executable intent nodes related to travel may include "airline reservations," "hotel reservations," "car rentals," "route planning," "finding points of interest," and so forth. An actionable intent node under the same super-domain (e.g., a "travel" super-domain) may have multiple attribute nodes in common. For example, executable intent nodes for "airline reservations," hotel reservations, "" car rentals, "" route plans, "" find points of interest, "may share one or more of the attribute nodes" starting location, "" destination, "" departure date/time, "" arrival date/time, "and" co-workers.

In some embodiments, each node in ontology 360 may be associated with a set of words and/or phrases that are related to the property or executable intent represented by the node. The respective set of words and/or phrases associated with each node may be a so-called "vocabulary" associated with the node. The respective set of words and/or phrases associated with each node may be stored in the lexical index 744 associated with the property or actionable intent represented by the node. For example, returning to fig. 7B, the vocabulary associated with the node for the "restaurant" property may include words such as "food," "drinks," "cuisine," "hunger," "eating," "pizza," "fast food," "meal," and so forth. As another example, the words associated with the node of the actionable intent of "initiate a phone call" may include words and phrases such as "call," "make phone call," "dial," "make phone call with … …," "call the number," "call to," and so on. The vocabulary index 744 may optionally include words and phrases in different languages.

Natural language processing module 732 may receive a sequence of symbols (e.g., a text string) from STT processing module 730 and determine which nodes are involved in words in the sequence of symbols. In some embodiments, if a word or phrase in a sequence of symbols is found to be associated with one or more nodes in ontology 760 (via lexical index 744), then the word or phrase may "trigger" or "activate" those nodes. Based on the number and/or relative importance of the activated nodes, natural language processing module 732 may select one of the actionable intents as a task that the user intends for the digital assistant to perform. In some embodiments, the domain with the most "triggered" nodes may be selected. In some embodiments, the domain with the highest confidence value (e.g., based on the relative importance of its respective triggered node) may be selected. In some embodiments, the domain may be selected based on a combination of the number and importance of triggered nodes. In some embodiments, additional factors are also considered in selecting a node, such as whether the digital assistant has previously correctly interpreted a similar request from the user.

The user data 748 may include user-specific information such as user-specific vocabulary, user preferences, user addresses, the user's default and second languages, the user's contact list, and other short-term or long-term information for each user. In some embodiments, the natural language processing module 732 may use user-specific information to supplement information contained in the user input to further define the user intent. For example, for a user request "invite my friend to my birthday party," natural language processing module 732 may be able to access user data 748 to determine who the "friend" is and where and when the "birthday party" will be held without the user explicitly providing such information in their request.

Additional details of Searching for ontologies based on symbolic strings are described in U.S. utility patent application serial No. 12/341,743, entitled "Method and Apparatus for Searching Using An Active Ontology," filed on 22.12.2008, the entire disclosure of which is incorporated herein by reference.

In some embodiments, once natural language processing module 732 identifies an executable intent (or domain) based on the user request, natural language processing module 732 may generate a structured query to represent the identified executable intent. In some embodiments, the structured query may include parameters for one or more nodes within the domain that can execute the intent, and at least some of the parameters are populated with specific information and requirements specified in the user request. For example, the user may say "help me reserve a seat at 7 pm in a sushi shop. In this case, the natural language processing module 732 may be able to correctly identify the executable intent as "restaurant reservation" based on the user input. According to the ontology, the structured query for the "restaurant reservation" domain may include parameters such as { cuisine }, { time }, { date }, { party size }, and the like. In some embodiments, based on the speech input and text derived from the speech input using STT processing module 730, natural language processing module 732 may generate a partially structured query for the restaurant reservation field, where the partially structured query includes parameters { cuisine ═ sushi class "} and { time ═ 7 pm" }. However, in this embodiment, the user utterance contains insufficient information to complete the structured query associated with the domain. Thus, based on the currently available information, it is not possible to specify other necessary parameters such as { co-people } and { date } in a structured query. In some embodiments, natural language processing module 732 may populate some parameters of the structured query with the received contextual information. For example, in some embodiments, if the user requests a sushi store that is "nearby," the natural language processing module 732 may populate the { location } parameter in the structured query with the GPS coordinates from the user device.

In some embodiments, the natural language processing module 732 may pass the generated structured query (including any completed parameters) to the task flow processing module 736 ("task flow processor"). Task stream processing module 736 may be configured to receive the structured query from natural language processing module 732, to complement the structured query (if necessary), and to perform the actions required to "complete" the user's final request. In some embodiments, the various processes necessary to accomplish these tasks may be provided in task flow model 754. In some embodiments, task flow model 754 may include procedures for obtaining additional information from a user, as well as task flows for performing actions associated with an executable intent.

As described above, to complete a structured query, the task flow processing module 736 may need to initiate additional dialog with the user in order to obtain additional information and/or clarify potentially ambiguous utterances. When such interaction is necessary, the task flow processing module 736 may invoke the dialog flow processing module 734 to conduct a dialog with the user. In some embodiments, the conversation flow processing module 734 may determine how (and/or when) to request additional information from the user, and receive and process the user response. Questions may be provided to the user and answers may be received from the user via the I/O processing module 728. In some embodiments, the conversation stream processing module 734 may present conversation output to the user via audio and/or video output and receive input from the user via spoken or physical (e.g., click) responses. Continuing with the above-described embodiment, when the task flow processing module 336 invokes the conversation flow processing module 734 to determine "number of peers" and "date" information for a structured query associated with the domain "restaurant reservation," the conversation flow processing module 734 may generate a query such as "a few digits in a line? "and" which day to book? "and the like to the user. Upon receiving an answer from the user, the dialog flow processing module 734 may populate the structured query with missing information or pass information to the task flow processing module 736 to supplement the missing information of the structured query.

Once the task flow processing module 736 has completed the structured query for the executable intent, the task flow processing module 736 may continue to execute the final task associated with the executable intent. Thus, the task flow processing module 736 may perform the steps and instructions in the task flow model according to the specific parameters contained in the structured query. For example, a task flow model for the actionable intent "restaurant reservation" may include steps and instructions for contacting a restaurant and actually requesting a reservation for a particular peer at a particular time. For example, by using structured queries such as: { restaurant reservation, restaurant, ABC cafe, date 2012/3/12, time 7 pm, peer 5 }, task flow processing module 736 may perform the following steps: (1) a server or restaurant reservation system such as that logged into ABC cafe

(2) Entering date, time, and peer information in a form on a website, (3) submitting the form, and (4) making a calendar entry for the reservation in the user's calendar.

In some embodiments, the task flow processing module 736 may complete the tasks requested in the user input or provide the informational answers requested in the user input with the assistance of the service processing module 738 ("service processing module"). For example, the service processing module 738 may initiate phone calls, set calendar entries, invoke map searches, invoke or interact with other user applications installed on the user device, and invoke or interact with third-party services (e.g., restaurant reservation portals, social networking sites, bank portals, etc.) on behalf of the task flow processing module 736. In some embodiments, the protocols and Application Programming Interfaces (APIs) required for each service may be specified by respective ones of service models 756. The service handling module 738 may access the appropriate service model for a service and generate a request for the service according to the service model and the required protocols and APIs for the service.

For example, if a restaurant has enabled an online reservation service, the restaurant may submit a service model that specifies the necessary parameters to make the reservation and an API that communicates the values of the necessary parameters to the online reservation service. When requested by the task stream processing module 736, the service processing module 738 may use the web address stored in the service model to establish a network connection with the online booking service and send the necessary parameters for booking (e.g., time, date, number of peers) to the online booking interface in a format according to the API of the online booking service.

In some embodiments, the natural language processing module 732, the dialog flow processing module 734, and the task flow processing module 736 may be used jointly and iteratively to infer and define a user's intent, to obtain information to further clarify and refine the user's intent, and to ultimately generate a response (i.e., output to the user, or completion of a task) to satisfy the user's intent. The generated response may be a dialog response to the speech input that at least partially satisfies the user intent. Additionally, in some embodiments, the generated response may be output as a voice output. In these embodiments, the generated response may be sent to a speech synthesis module 740 (e.g., a speech synthesizer) where it may be processed to synthesize a conversational response in the form of speech. In further embodiments, the generated response may be data content relevant to satisfying the user request in the voice input.

The speech synthesis module 740 may be configured to synthesize speech output for presentation to a user. The speech synthesis module 740 synthesizes speech output based on text provided by the digital assistant. For example, the generated dialog response may be in the form of a text string. The speech synthesis module 740 may convert the text string into an audible speech output. The speech synthesis module 740 may use any suitable speech synthesis technique for generating speech output from text, including but not limited to concatenative synthesis, unit selection synthesis, diphone synthesis, domain specific synthesis, formant synthesis, articulatory synthesis, Hidden Markov Model (HMM) based synthesis, and sine wave synthesis. In some embodiments, speech synthesis model 740 may be configured to synthesize individual words based on the phoneme strings corresponding to the words. For example, the phoneme string may be associated with a word in the generated dialog response. The phoneme string may be stored in metadata associated with the word. Speech synthesis model 740 may be configured to directly process the phoneme string in the metadata to synthesize words in speech form.

In some embodiments, instead of (or in addition to) utilizing speech synthesis module 740, speech synthesis may be performed on a remote device (e.g., server system 108), and the synthesized speech may be sent to a user device for output to a user. This may occur, for example, in some implementations, where the output of the digital assistant is generated at the server system. And because server systems typically have more processing power or resources than user devices, it may be possible to obtain higher quality speech output than is achieved with client-side synthesis.

Additional details of the digital Assistant can be found in U.S. utility model patent application 12/987,982 entitled "Intelligent automatic Assistant" filed on 10/1/2011, U.S. utility model patent application 13/251,088 entitled "Generating and Processing Task Items then procedure Tasks to performance" filed on 30/9/2011, U.S. utility model patent application 15/144,618 entitled "Intelligent Device Identification" filed on 2/5/2016, and U.S. utility model patent application 14/503,105 entitled "Intelligent Assistant for Home Automation" filed on 30/9/2014, the entire disclosures of which are incorporated herein by reference.

4. Exemplary techniques for Intelligent device arbitration

Fig. 8A-8C illustrate example techniques for intelligent device arbitration, according to some embodiments. These drawings are also used to illustrate the processes described below, including the processes in fig. 10A to 10C.

FIG. 8A shows

electronic devices

802, 804, 806, and 808 of a user 800. In some embodiments, one or more of devices 802-808 may be any of

devices

104, 122, 200, 400, 600, and 1200 (fig. 1, fig. 2A, fig. 3, fig. 4, fig. 5A, fig. 6A-6B, and fig. 12). In some embodiments, the electronic device 802 is a wearable electronic device, such as a smart watch, and is optionally powered off when in the lowered position, as shown. In some embodiments, the electronic device 804 is a mobile device, such as a mobile phone; the electronic device 806 is an electronic device with relatively large display capabilities, such as a television; the electronic device 808 is a device with auditory output capabilities, such as a speaker docking station. Although the illustrated embodiment is described herein with reference to electronic devices 802-808, it should be understood that a fewer or greater number of devices may be used in other implementations. Additionally, the electronic devices 802 and 808 can be associated with different users (not shown).

Each of the electronic devices 802-808 is capable of sampling audio input from the user 800. For example, the electronic device 804 samples audio input through its microphone to listen for verbal instructions from the user 800. In some embodiments, one or more of the electronic devices 802-808 continuously sample the audio input. In some embodiments, one or more of the electronic devices 802-808 begin sampling audio input in response to detecting the proximate user 800. In some embodiments, one or more of the electronic devices 802-808 begin sampling audio input in response to a particular input (such as a spoken trigger) by the user 800. Fig. 8A shows that user 800 provides spoken instructions 834 "hey, Siri, find me a tv show". In one implementation, each of the electronic devices 802-808 respectively sample the audio input and detect the spoken instruction 834.

In response to detecting the spoken instruction 834, the electronic device 802 and 808 initiate an arbitration process to identify (e.g., determine) an electronic device for responding to the spoken instruction 834 from the user 800. By way of example, each of the electronic devices 802-808 broadcast a set of values based on the audio input sampled on the respective device. Each set of values may include one or more values. For example, the electronic device 804 (implemented as a mobile phone) broadcasts a first set of one or more values based on the spoken instructions 834 sampled on the electronic device 804, while the electronic device 808 (implemented as a speaker docking station) broadcasts a second set of one or more values based on the spoken instructions 834 sampled on the electronic device 808. The electronic devices 802 and 806 also broadcast respective sets of one or more values. The set of one or more values may be broadcast by the electronic device 802-808 via any one-way broadcast communication standard, protocol, and/or technique now known or in the future. In some embodiments, one or more sets of one or more values are broadcast using a bluetooth low energy (BTLE) advertisement mode. Other communication methods may be used including, but not limited to, WiFi (e.g., any 802.11 compatible communication), NFC, infrared, acoustic, and the like, or any combination thereof.

In some embodiments, the set of one or more values broadcast by the electronic device includes any number of values. One exemplary value indicates an energy level of the audio input sampled on the electronic device. The energy level of the sampled audio input may be indicative of the proximity of the electronic device to the user, for example. In some embodiments, the energy level is measured using a known measure of audio quality, such as signal-to-noise ratio, sound pressure, or a combination thereof.

Another exemplary value indicates a voiceprint of the audio input, i.e., whether the audio input is likely to be provided by a particular user. In some embodiments, the electronic device analyzes the audio input and calculates a confidence value that expresses a likelihood that the audio input originated from a particular user (e.g., a user that has registered for a virtual assistant service on the electronic device). In some embodiments, the electronic device determines whether the audio input is from an authorized user by comparing the confidence value to a predetermined threshold, and broadcasts a value based on the comparison. In this embodiment, the set of one or more values may also include a value corresponding to a confidence value.

Another exemplary value indicates a type of the electronic device. For example, as shown in FIG. 8A, the electronic device 804 is a mobile phone. It should be appreciated that the predetermined value may be used by the electronic devices 802-808 to indicate different device types including, but not limited to, speakers, televisions, smart watches, laptops, tablets, mobile devices, set-top boxes, headsets, or any combination thereof. In some embodiments, each of the electronic devices 802-808 broadcasts a "device type" only when the verbal instructions specify a task to be performed, as discussed in more detail below.

Another exemplary value indicates a status of the electronic device. In some embodiments, the value may indicate, for example, whether the electronic device has been active (e.g., has received user input) for a predetermined amount of time prior to receiving the audio input. In at least one embodiment, the value may indicate whether the electronic device is in a locked state. In some embodiments, the value may also indicate whether the user has recently activated the device or a virtual assistant service on the device. In some embodiments, the value may convey details about the most recent user input, such as a timestamp, type of input (e.g., physical touch, raising gesture), and so forth.

Another exemplary value indicates location information of the electronic device. In some embodiments, the value indicates a geographic location of the electronic device, for example, using GPS coordinates of the electronic device, or indicates a named location of the electronic device (e.g., a living room of the user).

The exemplary values described above correspond to various metrics related to implementing smart device arbitration as described herein. It should be appreciated that any number of values corresponding to these metrics may be broadcast and/or some or all of the values may be used to provide a single value using one or more functions. This single value may then be broadcast during device arbitration as described herein. It should also be understood that one or more functions may assign different weights to different values, respectively.

In some embodiments, the electronic device determines the respective value and/or broadcasts the value in response to detecting the spoken trigger. Referring to fig. 8A-8C, the spoken trigger is the phrase "hey, Siri". In response to the spoken trigger "hey, Siri," each of the electronic devices 802-808 broadcast a respective set of one or more values, as described. If the audio input does not contain a spoken trigger, the electronic device forgoes determining and/or broadcasting a set of one or more values.

Each of the electronic devices 802-808 can receive a set of values from the other devices. By way of example, the electronic device 802 may receive multiple sets of values from the electronic device 804 and 808, the electronic device 804 may receive multiple sets of values from the electronic devices 802, 806, 808, and so on. After the sets of values have been exchanged between the electronic devices 802-808, each device determines whether it should respond to the audio input by analyzing the values of the sets, as described below.

In some embodiments, each device determines whether a response to the spoken command 834 should be made based on the energy level values broadcast by the electronic devices 802-808. Each of the electronic devices 802-808 compares the respective "energy level" value to the "energy level" values broadcast by the other electronic devices. In some embodiments, if the electronic device broadcasts the highest "energy level" value, the electronic device responds to the audio input. As described above, a higher "energy level" value may indicate a closer proximity to the user. Because the device closest to the user may be associated with the highest energy level value, it may be beneficial for the electronic device that broadcast the highest "energy level" value to respond to the spoken instructions 834.

In some embodiments, each device determines whether a response to the spoken command 834 should be made based on the status values broadcast by the electronic devices 802 and 808. Each of the electronic devices 802-808 compares the respective "status" value to the "status" values broadcast by the other electronic devices. As described above, the "state" value of an electronic device may contain information about the operation of the electronic device, such as whether it is locked, whether it has been activated recently, whether it has received a particular user input recently. In some embodiments, the electronic device responds to the audio input if the user has recently provided input indicating an intent to interact with that particular electronic device. Exemplary inputs include an active gesture (e.g., on a wearable electronic device), a physical touch (e.g., on a touch-sensitive screen of the device), and so forth. In some embodiments, if the electronic device is the only device in the unlocked state based on the broadcasted "status value," the electronic device responds to the audio input.

In some embodiments, each device determines whether a response to the spoken command 834 should be made based on the voiceprint values broadcast by the electronic devices 802 and 808. Each of the electronic devices 802-808 compares the respective "voiceprint" value to the values broadcast by the other electronic devices. In some embodiments, the electronic device responds to the audio input if, based on the broadcasted value, it is the only electronic device that has identified the user providing the audio input as an authorized user. For example, if user 800 has registered for virtual assistant service only on electronic device 802 (implemented as a smart watch), then electronic device 802 responds to audio input from user 800.

In some embodiments, each of the electronic devices 802-808 determines whether a response should be made to the spoken instruction based on the device type value broadcast by the electronic devices 802-808. Each of the electronic devices 802-808 compares the respective "device type" value to the values broadcast by the other electronic devices. Device types are particularly relevant for smart device arbitration when a user's input specifies a task to be performed (such as "hey, Siri, find me a tv drama" or "hey, Siri, take me there"). In some embodiments, if, based on the broadcasted value, the electronic device is the only device of the type that is capable of handling the task specified in the audio input, the electronic device responds to the audio input.

In some embodiments, the electronic device obtains a list of acceptable device types that can handle the specified task (e.g., by locally analyzing the audio input and/or by receiving the list from one or more servers) and determines whether the electronic device should respond to the audio input based on the broadcasted "device type" value and the list of acceptable device types. In some embodiments, the one or more servers receive data representing the sampled audio input from one or more of the electronic devices 802 and 808, derive user intent based on the data, and identify a task having one or more parameters based on the user intent. In some embodiments, once the one or more servers determine the task based on the audio input, the one or more servers transmit the task, the parameters (if any), and the list of acceptable device types for processing the task to the electronic device that has sampled the audio input (e.g., electronic device 802- "808). Additional details regarding identifying tasks from natural language input can be found, for example, in U.S. utility patent application No. 15/144,618 entitled "Intelligent Device Identification," filed 5/2/2016, which is hereby incorporated by reference in its entirety.

It should be understood that the arbitration process described herein is exemplary and that some or all of the above values, alone or in combination, may be included in the determination of whether the electronic device should respond to audio input using one or more numerical and/or logical functions and algorithms. In some embodiments, each of the electronic devices 802-808 broadcasts a plurality of values (e.g., a total score and a "device type" value). Accordingly, the electronic device 802-808 may arbitrate according to one or more predetermined algorithms. In some embodiments, each of the electronic devices 802-808 broadcasts a single score that is calculated using some or all of the above values according to one or more functions. For example, a single score for a broadcast may be calculated based on a predetermined weighting of received audio quality (e.g., signal-to-noise ratio), device type, ability to perform a task, and device status. It should further be appreciated that each of the electronic devices 802-808 may use a variety of logical and/or numerical functions and algorithms. It should also be understood that adjustments to the functions and algorithms may be implemented to adjust the prioritization of the above factors.

In some embodiments, the electronic device may respond to the audio input by providing a visual output (e.g., a display notification or an LED switch), an audible output, a tactile output, or a combination thereof. For example, the electronic device 804 can respond to the audio input with a visual output (e.g., displaying transcribed text of the audio input) and an audio output (e.g., "search for a television. If the electronic device determines not to respond to the audio input, the electronic device may forgo responding to the audio input by entering an inactive mode (e.g., a sleep mode).

Referring to fig. 8A, each of electronic device 802 (implemented as a smart watch), electronic device 804 (implemented as a mobile phone), electronic device 808 (implemented as a speaker docking cradle), and electronic device 806 (implemented as a television) generates and broadcasts a set of one or more values after sampling verbal instructions 834 from user 800. In this embodiment, each set of one or more values includes a "energy level" value and a "device type" value. By comparing the broadcast "energy level" values, the electronic device 804 determines that it broadcast the highest "energy level" value among the electronic devices 802 and 808, indicating that the electronic device 804 is relatively close to the user 800.

However, the electronic device 804 also analyzes the broadcasted "device type" value in accordance with the task specified in the verbal instructions 834. As described above, the verbal instructions 834 may be processed and broken down into one or more tasks, either locally or remotely. For example, the electronic device 804 can locally break up the verbal instructions 834 into tasks, or receive tasks from one or more servers and a list of acceptable device types for processing the tasks. In this embodiment, the electronic device 804 determines that it is not an acceptable (or preferred) device type for handling tasks specified in the audio input (i.e., video playback). Thus, the electronic device 804 forgoes responding to the audio input.

In some embodiments, the electronic device 804 also determines whether any of the remaining electronic devices are capable of processing the specified task. The electronic device 804 makes this determination based on the device types broadcast by the other electronic devices and the list of acceptable device types. In some embodiments, if the electronic device 804 determines that none of the other electronic devices is of an acceptable device type for handling the task, the electronic device 804 outputs an error message to the user or prompts the user for additional input (e.g., "do you want to play back video on your iPhone.

Similarly, electronic device 806 (implemented as a television) receives sets of one or more values from electronic devices 802 (implemented as a smart watch), 808 (implemented as a speaker docking cradle), and 804 (implemented as a mobile phone), respectively. By analyzing the plurality of sets of values broadcast, the electronic device 806 determines that it has not broadcast the highest "energy level" value. However, the electronic device 806 also determines that it is a type of device that is capable of handling video playback tasks. Upon determination, the electronic device 806 makes an additional determination as to whether or not it should respond to the audio input, although the highest "energy level" value is not broadcast. For example, if the electronic device 806 determines that none of the electronic devices that broadcast the higher "energy level" value (e.g., electronic device 804) is an acceptable device type for handling the task, the electronic device 806 responds to the audio input. On the other hand, if the electronic device 806 determines that there is at least one electronic device that broadcasts a higher "energy level" value and is an acceptable device type for handling the task, the electronic device 806 foregoes responding to the audio input. In some embodiments, forgoing responding to the audio input may include entering an inactive mode.

Turning to fig. 8B, the user 800 provides audio input 812 that includes only spoken triggers ("hey, Siri") without specifying tasks. In response, each of the electronic devices 802 and 808 generates and broadcasts a set of one or more values, as described. In some embodiments, each of electronic devices 802-808 broadcast an "energy level" value to each other. In some embodiments, each of electronic devices 802-808 calculates a single value that aggregates some or all of the exemplary values described herein. In this embodiment, the electronic device 804 determines that it broadcasts the highest "energy level" value, indicating that the electronic device 804 is closer to the user 800 than the other electronic devices. Thus, the electronic device 804 responds to the audio input 812, and the remaining electronic devices forgo responding to the audio input.

In some embodiments, because the audio input 812 ("hey, Siri") does not specify a task, the electronic device used 802 and 808 may forgo broadcasting the "device type" value and rely only on the "energy level" value during arbitration. In some embodiments, the electronic device 802-808 forgoes broadcasting the "device type" value upon determining that the user did not provide another utterance within a predetermined period of time after the spoken trigger (e.g., "hey, Siri"). It should be appreciated that after the electronic device determines to respond to the audio input 812 ("hey, Siri"), the electronic device can receive an utterance specifying a task and can cause the task to be performed at a second electronic device if the electronic device is not of the type used to perform the indicated task or the second electronic device is better suited to perform the specified task.

Turning to fig. 8C, a user 800 raises an electronic device 802 (implemented as a smart watch) to a raised position and then provides audio input 814 ("hey, Siri"). In some embodiments, the set of one or more values broadcast by the electronic device 802 includes a value indicative of a gesture input by a user at the electronic device 802. The value may be a value indicating that there is a recent user input or may include detailed information about the user input such as a timestamp, input type, and the like. In view of the broadcasted "status" value of the electronic device 802, the electronic device 804 and 808 forgo responding to the audio input, and the electronic device 802 responds to the audio input. In some embodiments, an electronic device that broadcasts a value indicating a particular type of user input (e.g., an active gesture, a physical touch) at the electronic device should respond to audio input regardless of other broadcasted values. In some embodiments, when multiple electronic devices broadcast values indicative of a particular type of user input at the respective electronic devices, the electronic device broadcasting the value indicative of the most recent user input (e.g., a timestamp) should respond to the audio input regardless of the other broadcasted values.

In some embodiments, if an electronic device broadcasts a set of one or more values and does not receive any of the set of one or more values from another electronic device, the electronic device responds to the audio input regardless of the value broadcast.

5. Exemplary techniques for Smart device control

Fig. 9A-9C illustrate an exemplary technique for smart device control, according to some embodiments. These drawings are also used to illustrate the processes described below, including the processes in fig. 11A to 11E.

Fig. 9A illustrates an exemplary system and environment 900 for controlling an electronic device with a virtual assistant. In some embodiments, the first user equipment 908 and the second user equipment 910 may be any of the

devices

104, 122, 200, 400, 600, and 1330 (fig. 1, fig. 2A, fig. 3, fig. 4, fig. 5A, fig. 6A-6B, and fig. 13). In some embodiments, each of

user devices

908 and 910 may be a television, a set-top box, an audio speaker, a mobile phone, a smart watch, a laptop, a desktop computer, a tablet, or a combination thereof. Virtual assistant server 902 may be implemented using any system described herein, such as system 108 of fig. 1. Each of media identification storage 906 and device identification storage 904 may be located on virtual assistant server 902, first user device 908, second user device 910, or any other device or system in communication with virtual assistant server 902.

In operation, as shown in FIG. 9A, The first user device 908 receives user input (e.g., "play The Ramones in my living room"). In some embodiments, the user input comprises user speech, and the first user device 908 receives the user input with a microphone of the first electronic device 908. In some embodiments, the first electronic device 908 converts the user input into a representation of the audio input. The representation of the audio input may be an analog or digital representation. In some embodiments, the representation is a textual representation and the first electronic device 908 converts the user input to a textual representation using speech-to-text conversion. The user speech may be converted using any known speech-to-text conversion process.

At 920, the user input, or a representation thereof, is provided (e.g., transmitted) by first electronic device 908 to virtual assistant server 902 for processing.

Based on the user input, virtual assistant server 902 identifies one or more tasks and parameters. For example, virtual assistant server 902 interprets a textual representation of the user's input to derive intent and operationally define the intent as one or more tasks. In The illustrated embodiment, based on The user input "play The ramons in my living room," virtual assistant server 902 identifies a task as being to add one or more media items to a media play queue at The desired electronic device. Tasks may be identified in any number of ways. Techniques for identifying tasks can be found, for example, in U.S. utility patent application No. 14/503,105 entitled "Intelligent assistance for Home Automation" filed on 30.9.2014 and U.S. provisional patent application No. 62/348,015 entitled "Intelligent Automated assistance in a Home Environment" filed on 9.6.2016 (attorney docket No. 770003000100(P30331USP1)), the entire disclosures of which are incorporated herein by reference.

In addition, virtual assistant server 902 identifies relevant parameters needed to complete the task. In some embodiments, the parameters include an indication of the media item to be played, such as a song title and a media file name. In some embodiments, the parameters include an indication of the type of media item to be played, such as audio, video, and text. In some embodiments, the parameters include an indication of a location of the desired electronic device, such as a named location and configuration ("living room", "garage", "upstairs") or GPS coordinates associated with the user. In some embodiments, the parameters include an indication of the type of desired electronic device, such as a television, a speaker docking station, and a smart watch. In the illustrated embodiment, virtual assistant server 902 identifies the parameters as being "Ramones" and "living room".

At 940, virtual assistant server 902 transmits a request for the identity of one or more user devices to device identity store 904. The request includes one or more parameters identifying one or more user devices. In some embodiments, the one or more parameters may specify a named location (e.g., "living room"), a device type (e.g., "AppleTV"), and/or one or more attributes of the media item, such as a type of the media item (e.g., "audio" and "video").

Device identification storage 904 may store data and/or models for a plurality of attributes and related information associated with various electronic devices. Attributes that may be stored for the electronic device include, but are not limited to, a unique identifier, status, type, location, supported media types, and owner. For example, device identification storage 904 may store information associating the device with the type "AppleTV", the named location "living room", and the supported media types "audio" and "video". As another example, device identification storage 904 may store information associating the device with the type "speaker," named location "garage," and supported media type "audio.

Device identification storage 904 may be implemented via hardware, software, or a combination of both. In some embodiments, the device identification storage 904 may be located on one or more of the above electronic devices, including the first user device 908 and the second user device 910. Device identification storage 904 may be located on the same electronic device hosting either media identification storage 906 and virtual assistant server 902.

At device identification store 904, one or more user devices are identified based on parameters provided in the request from virtual assistant server 902. In some embodiments, device identification storage 804 determines whether any of the electronic devices having entries in the database have attributes that match the parameters. In the illustrated embodiment, user device 910 is identified by device identification store 904 based on the request received at 940. Additional details regarding the identification of electronic devices can be found, for example, in U.S. utility patent application 14/503,105 entitled "Intelligent assistance for Home Automation," filed on 30.9.2014, the entire disclosure of which is incorporated herein by reference.

In response to the request for the identification of the one or more devices, virtual assistant server 902 receives identification information of the one or more devices at 942. In the illustrated embodiment, the identification information includes a unique identifier (e.g., "uid-123456") corresponding to the identified user device 910.

At 960, virtual assistant server 902 transmits a request for identification of one or more media items to media identification store 906. The request includes one or more parameters, such as the parameter "Ramones," that allow the one or more media items to be identified. The media identification store 906 comprises a database that associates (e.g., catalogs) a set of media items by one or more attributes associated with the media items, including title, artist, genre, length, and any other relevant information. By way of example, one or more media items are identified at the media identification store 906 based on the parameter "RAMONES".

In response to the request for identification of the one or more media items, virtual assistant server 902 receives identification information of the one or more media items identified from media identification store 906 at 962. In some embodiments, the identification information includes a unique identifier corresponding to the identified one or more media items, such as "artist:// store/56989". The unique identifiers of the one or more media items can be used to identify, and subsequently access, the identified one or more media items, for example, using one or more applications that support media playback. Media identification storage 906 may be located on any local or remote electronic device, such as the same electronic device on which virtual assistant server 902 is located. It should be understood that while the operations at 940 are illustrated as occurring before the operations at 960, the operations corresponding to 960 and 940 may be performed in any temporal order or simultaneously.

At 980, the virtual assistant server 902 provides the consolidated command to the first user device 908. The command includes identification information for one or more media items and identification information for the user device 910. In the embodiment shown in fig. 9A, the unified command includes the text string "setmediaplayquerueartist:// store/56989 airplayaroute ═ 12456". In response to receiving the join command, user device 908 causes the identified one or more media items (e.g., media related to the ramons) to be played back at the identified user device (e.g., second user device 910, implemented as a television) at 982. In some embodiments, the first user device 908 transmits the relevant information derived from the joint command to the second user device 910.

Referring to fig. 9B, in some embodiments, device identification storage 904 provides (e.g., generates) and/or updates entries in its database for the electronic device by communicating with device tracking storage 912. Device tracking storage 912 provides discovery of electronic devices having particular attributes and communicates with device identification storage 904 to update the database of device identification storage 904. The device tracking storage 912 may be implemented via hardware, software, or a combination of both. Further, device tracking storage 912 may be located on any electronic device described herein, such as first user device 908 or second user device 910. Device tracking storage 912 may be located on the same electronic device that hosts media identification storage 906, virtual assistant server 902, device identification storage 904, or any device or system in communication with device identification storage 904.

In some embodiments, device identification store 904 provides and/or updates an entry for an electronic device in its database in response to user input (e.g., "play the RAMONS on My Apple TV"). As shown in fig. 9B, in response to receiving a request for identification of one or more user devices (940), device identification storage 904 communicates with device tracking storage 912 at 930 to cause discovery of all electronic devices having one or more attributes specified in or derived from the request. In some embodiments, discovery of devices is performed in response to the device identification store 904 being unable to identify devices having parameters that match those provided in the request from the virtual assistant server 902. At 932, device tracking storage 912 passes a list of newly discovered electronic devices to device identification storage 904. Based on the discovered electronic devices and corresponding attributes, the device identification store 904 updates the relevant entries in its database. In some embodiments, data corresponding to discovered electronic devices and corresponding attributes is cached, at least in part, at device tracking storage 912 or device identification storage 904 for a period of time (e.g., minutes).

In some embodiments, device identification storage 904 automatically and/or periodically provides and/or updates an entry for the electronic device in its database. For example, device tracking storage 912 may facilitate discovery of electronic devices without requests from virtual assistant server 902 and without any communication from device identification storage 904.

In some embodiments, after sending the request to device identification store 904 at 940, virtual assistant server 902 receives identification information that requires input from the user. In one embodiment, user input is required in response to device identification storage 904 having identified a plurality of user devices corresponding to the requested parameters. In this way, the user is prompted to provide a disambiguating input by selecting a device from the identified plurality of user devices in some cases. As another example, user input is required to authenticate a device discovered, for example, in response to device identification storage 904 failing to identify a device matching the request parameters.

As shown in fig. 9C, virtual assistant server 902 receives, at 942, identification information for a plurality of identified electronic devices from device identification store 904. At 944, virtual assistant server 902 provides (e.g., transmits) the identification information to user device 908 for disambiguation by the user. Accordingly, the user device 908 presents (e.g., displays) a list of the plurality of identified electronic devices to the user and prompts the user to provide input including selecting a device from the list. In some embodiments, the device list includes distinguishing attributes of the devices, such as color and model.

An indication of the selected device is transmitted from the user device 908 to the virtual assistant server 902 at 946. At 980, based on the received data, virtual assistant server 902 generates a consolidated command and provides the command to user device 908. The command includes identification information for one or more media items and identification information for a device selected by the user. For example, in FIG. 9A, the command is the text string "SetMediaPlayerQueue attribute:// store/56989AirplayRouteUid ═ 12456".

In some embodiments, virtual assistant server 902 receives identification information for one or more electronic devices that require user authentication. As described above, device identification store 904 may not be able to identify user devices whose attributes match parameters in a request provided by virtual assistant server 902, and in response, may identify the device through discovery. Virtual assistant server 902 provides (e.g., transmits) identification information for the devices identified in this manner to user device 908 for user authentication.

At the user device 908, the user is prompted to verify the candidate device and/or provide related information to be associated with the candidate device. For example, an available output (e.g., audio output) "is this speaker in your living room? "to prompt the user. In response, user device 908 receives input from the user confirming or rejecting the candidate device and transmits data corresponding to the user's input to virtual assistant server 902. If the user confirms the candidate device, virtual assistant server 902 generates a federated command accordingly and provides the command to user device 908, as described. If the user rejects the candidate device, user device 908 outputs an error message and, in some cases, communicates the user's rejection of the candidate device to virtual assistant server 902.

In some embodiments, the database of device identification store 904 is updated in response to user input at user device 908. Virtual assistant server 902 may, for example, receive a user's input and, in response, cause device identification store 904 to update a database of electronic devices. By way of example, virtual assistant server 902 receives the disambiguation response at 946 and causes an entry for the user-selected device to be created and/or updated at the database of device identification store 904 at 948. For example, the user-selected device is then associated with an existing configuration (e.g., a "living room" configuration) based on the user input. Additional details regarding the creation and management of configurations can be found, for example, in U.S. utility patent application 14/503,105 entitled "Intelligent Assistant for Home Automation," filed on 9/30/2014, the entire disclosure of which is incorporated herein by reference.

6. Process for intelligent device arbitration

Fig. 10A-10C illustrate a process 1000 for operating a digital assistant, according to various embodiments. Process 1000 is performed, for example, with one or more electronic devices (e.g.,

devices

104, 106, 200, 400, or 600) implementing a digital assistant. In some embodiments, the process is performed at a client-server system (e.g., system 100) implementing a digital assistant. The blocks of the process may be distributed in any manner between a server (e.g., DA server 106) and a client (e.g., user device 104). In process 1000, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some embodiments, only a subset of the features or blocks described below with reference to fig. 10A-10C are performed.

As described below, the method 1000 provides an efficient way to arbitrate among multiple devices for responding to user input. The method reduces the cognitive burden on the user to manage multiple devices, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling a user to accomplish task completion more efficiently conserves power and increases the time interval between battery charges.

At block 1002, a first electronic device having a microphone samples audio input. In some embodiments, the audio input may be received via a microphone (e.g., microphone 213) of the electronic device. The received audio input may be processed (e.g., using audio circuitry 210 or processor 220) and converted to a representative form, such as, for example, an electronic signal (digital or analog) or one or more audio files.

At block 1008, the first electronic device broadcasts a first set of one or more values based on the sampled audio input. In some embodiments, the values in the first set of values are based on a signal-to-noise ratio of speech of the audio input sampled by the first electronic device. In some embodiments, the values in the first set of values are based on sound pressures of audio inputs sampled by the first electronic device. In some embodiments, the first electronic device identifies a confidence value that indicates a likelihood that the audio input was provided by the particular user, and the values in the first set of values are based on the confidence value. In some embodiments, the first electronic device identifies a state of the first electronic device, and the values in the first set of values are based on the identified state of the first electronic device. In some embodiments, the state of the first electronic device is identified based on user input received by the first electronic device. In some embodiments, at least one value of the first set of one or more values is based on a type of the first electronic device.

At block 1004, the first electronic device optionally determines whether the audio input includes a spoken trigger (e.g., "hey, Siri"). In accordance with a determination that the audio input does not include a spoken trigger, the first electronic device forgoes broadcasting the first set of one or more values at block 1006.

At block 1010, the first electronic device receives a second set of one or more values from the second electronic device. The second set of one or more values is based on the audio input sampled at the second electronic device.

At block 1012, the first electronic device determines whether the first electronic device should respond to the audio input based on the first set of one or more values and the second set of one or more values. In some embodiments, the first electronic device determines whether the first electronic device should respond to the audio input by determining whether a value in the first set of one or more values is higher than a corresponding value in the second set of one or more values at block 1042.

At block 1014, in accordance with a determination that the first electronic device should respond to the audio input, the first electronic device responds to the audio input. In some embodiments, the audio input includes additional input indicative of the task. At block 1018 (fig. 10B), the first electronic device also determines whether the type of the first electronic device meets the requirements of the task. At block 1020, the first electronic device optionally receives data from a server indicating requirements for the task.

In accordance with a determination that the type of the first electronic device satisfies the requirements of the task, the first electronic device responds to the audio input at block 1022. In accordance with a determination that the type of the first electronic device does not meet the requirements of the task, the first electronic device may forgo responding to the audio input, or optionally, make additional determinations to determine whether the second device should respond to the audio input at block 1024. At block 1026, in accordance with a determination that the second device should respond to the audio input, the first electronic device overrides responding to the audio input with the first electronic device. In accordance with a determination that the second device should not respond to the audio input, the first electronic device provides an output indicating an error at block 1028.

At block 1016 (fig. 10A), in accordance with a determination that the first electronic device should not respond to the audio input, the first electronic device forgoes responding to the audio input. In some embodiments, the audio input includes additional input indicative of the task. At block 1030 (fig. 10C), the first electronic device optionally determines whether the type of the first electronic device meets the requirements of the task. At block 1032, the first electronic device optionally receives data from the server indicating a requirement of the task.

At block 1034, in accordance with a determination that the type of the first electronic device satisfies the requirements of the task, the first electronic device determines whether the first electronic device should be used to respond to the audio input based on the first set of one or more values, the second set of one or more values, and the requirements of the task. At block 1036, in accordance with the determination that the first electronic device should be used to respond to the audio input, the first electronic device responds to the audio input with the first electronic device. At block 1038, in accordance with a determination that the first electronic device should not be used to respond to the audio input, the first electronic device overrides responding to the audio input with the first electronic device.

In accordance with a determination that the type of the first electronic device does not meet the requirements of the task, the first electronic device overrides responding to the audio input with the first electronic device at block 1040. In some embodiments, forgoing responding to the audio input with the first electronic device includes entering an inactive mode, as shown in block 1044.

In some embodiments, the first set of one or more values is broadcast according to a one-way broadcast communication protocol, such as BTLE advertised mode.

In some embodiments, in accordance with a determination that the first electronic device should respond to an audio input, the first electronic device provides a visual output, an audible output, a tactile output, or a combination thereof.

7. Process for smart device control

Fig. 11A-11E illustrate a process 1100 for operating a digital assistant, in accordance with various embodiments. The process 1100 is performed, for example, with one or more electronic devices (e.g.,

devices

104, 106, 200, 400, 600, 1300, 1330, or 1360) implementing a digital assistant. In some embodiments, the process is performed at a client-server system (e.g., system 100) implementing a digital assistant. The blocks of the process may be distributed in any manner between a server (e.g., DA server 106) and a client (e.g., user device 104). In process 1100, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some embodiments, only a subset of the features or blocks described below with reference to fig. 11A-11E are performed.

As described below, the method 1100 provides an efficient way to control one of a plurality of devices for responding to user input. The method reduces the cognitive burden on the user to manage multiple devices, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling a user to accomplish task completion more efficiently conserves power and increases the time interval between battery charges.

At block 1102, the electronic device receives data corresponding to an audio input from a first user device.

At block 1104, the electronic device obtains an identification of a second user device based on data corresponding to the audio input. In some embodiments, the electronic device is a first electronic device and communicates with a second electronic device to obtain an identification of the second user device. In some embodiments, the second electronic device is the first user device (e.g., implemented with the same hardware).

Optionally, at block 1106, the first electronic device identifies tasks and parameters based on data corresponding to the audio input. At block 1108, the first electronic device transmits a request to the second electronic device, where the request includes a parameter identifying a user device for performing a task.

At block 1110, the second electronic device receives a request including a parameter. At block 1112, the second electronic device discovers one or more user devices in response to receiving the request. Optionally at block 1113, the second electronic device discovers the user device associated with the indication of the named location of the user. At block 1114, the second electronic device updates the record based on the discovered attributes of the one or more user devices. The record stores sets of attributes corresponding to a plurality of user devices, respectively. At block 1116, the second electronic device caches the discovered attributes of the one or more user devices. In some embodiments, the steps in block 1112-1116 are performed automatically and/or periodically without any request from the first electronic device. At block 1118, the second electronic device obtains data from the record. In some embodiments, the user device of the plurality of user devices is a computer, a television, a set-top box, an audio speaker, or a telephone. At block 1120 (fig. 11B), the second electronic device determines an identity of a second user device based on the parameter, wherein the second user device is a member of the plurality of user devices. In some embodiments, the second electronic device determines the identity of the second user device by determining whether at least one attribute of the second user device matches the parameter at block 1121. At block 1122, the second electronic device transmits an identification of the second user device to the first electronic device.

At block 1124, the first electronic device receives an identification of a second user device from the second electronic device. In some embodiments, the parameter includes an indication of a named location of the user. In some embodiments, the parameter comprises an indication of a type of the device. In some embodiments, the parameters include one or more attributes of one or more media items.

Optionally, at block 1126, the first electronic device identifies tasks and parameters based on data corresponding to the audio input. At block 1132, the first electronic device receives a plurality of identifications corresponding to a plurality of user devices from the second electronic device. In some embodiments, obtaining the plurality of identifications at the second electronic device is similar to the steps described with reference to block 1108 and 1122. At block 1134, the first electronic device transmits a plurality of identifications corresponding to the plurality of user devices to the first user device. At block 1136, the first user device receives a plurality of identifications corresponding to a plurality of user devices. At block 1138, the first user device presents the plurality of user devices as selectable options. At block 1140 (fig. 11C), the first user device receives an input representing a selection of a particular user device of the plurality of user devices. At block 1142, the first user device transmits data corresponding to the selection of the particular user device to the first electronic device. In some embodiments, each of the plurality of user devices has an attribute that matches the parameter.

At block 1144, the first electronic device receives data from the first user device corresponding to a selection of a particular user device of the plurality of user devices. At block 1146, the first electronic device obtains an identification of the second user device based on the received data corresponding to the selection of the particular user device of the plurality of user devices.

Optionally, at block 1148, the first electronic device identifies tasks and parameters based on data corresponding to the audio input. At block 1150, the second electronic device receives a request for identification of the user device from the first electronic device, where the request includes the parameter. At block 1152, the second electronic device obtains data from a record storing sets of attributes corresponding to a plurality of user devices, respectively. At block 1154 (fig. 11D), the second electronic device determines data corresponding to a candidate user device based on the parameters, wherein the candidate user device is not a member of the plurality of user devices stored in the record. In some embodiments, obtaining data corresponding to the candidate user device based on the parameter at block 1193 further comprises determining, with the second electronic device, that none of the plurality of user devices has an attribute that matches the parameter and discovering, with the second electronic device, the candidate user device at block 1151. At block 1153, the candidate user devices have attributes that match the parameters. At block 1156, the second electronic device transmits data corresponding to the candidate user device to the first electronic device.

At block 1158, the first electronic device receives data corresponding to the candidate user device from the second electronic device. At block 1160, the first electronic device transmits data corresponding to the candidate user device to the first user device. At block 1162, the first user device receives data corresponding to the candidate user devices. At block 1164, the first user device presents the candidate user devices as a confirmable option. At block 1166, the first user device receives an input representing a confirmation of candidate user devices. At block 1168 (fig. 11E), the first user device transmits data corresponding to the confirmation of the candidate user device to the first electronic device. In some embodiments, the first user device receives a rejection of the candidate user device at block 1171. In response, the first user device presents an output indicating an error at block 1173.

At block 1170, the first electronic device receives data from the first user device corresponding to the confirmation of the candidate user device. At block 1172, the first electronic device obtains an identification of the second user device by obtaining an identification of the candidate user device in response to receiving the data corresponding to the confirmation. In some embodiments, the second electronic device receives data corresponding to the confirmation of the candidate user device to the first electronic device at block 1171, and updates the record at block 1173 in response to receiving the data corresponding to the confirmation.

At block 1174, the electronic device obtains an identification of the media item based on the data corresponding to the audio input. Optionally, at block 1176, the first electronic device identifies tasks and parameters based on data corresponding to the audio input. Optionally, at block 1178, the first electronic device transmits a request to the database, wherein the request includes parameters identifying one or more media items. Optionally, at block 1180, the first electronic device receives an identification of one or more media items from a database. In some embodiments, the identification of the media items includes unique identifiers of one or more media items.

Fig. 12 illustrates a functional block diagram of an electronic device 1200 configured in accordance with the principles of various described embodiments (including those described with reference to fig. 8A-8C and 10A-10C), according to some embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of software and hardware to implement the principles of the various embodiments. Those skilled in the art will appreciate that the functional blocks described in fig. 12 are optionally combined or divided into sub-blocks in order to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in fig. 12, the electronic device 1200 comprises a microphone unit 1202, a processing unit 1208, and optionally further comprises an output unit 1204, the processing unit 1208 being coupled to the microphone unit 1202 and optionally to the output unit 1204. In some embodiments, the processing unit 1208 includes a broadcasting unit 1210, a receiving unit 1212, a determining unit 1214, a responding unit 1216, and optionally an identifying unit 1218 and an entering unit 1220.

In some embodiments, the processing unit 1208 is configured to: sampling (e.g., with microphone unit 1210) an audio input (e.g., block 1002 of fig. 10A); broadcasting (e.g., with the broadcasting unit 1210) a first set of one or more values based on the sampled audio input (e.g., block 1008 of fig. 10A); receiving (e.g., with receiving unit 1212) a second set of one or more values from a second electronic device, wherein the second set of one or more values is based on the audio input (e.g., block 1010 of fig. 10A); determining (e.g., with determining unit 1214) whether the electronic device should respond to the audio input based on the first set of one or more values and the second set of one or more values (e.g., block 1012 of fig. 10A); in accordance with a determination that the electronic device should respond to the audio input, responding to the audio input (e.g., with response unit 1216) (e.g., block 1014 of FIG. 10A); and in accordance with a determination that the electronic device should not respond to the audio input, forgoing responding to the audio input (e.g., with response unit 1216) (e.g., block 1016 of fig. 10A).

In some embodiments, the values in the first set of values are based on a signal-to-noise ratio of speech of the audio input sampled by the electronic device 1200.

In some embodiments, the values in the first set of values are based on the sound pressure of the audio input sampled by the electronic device 1200.

In some embodiments, the processing unit 1208 is further configured to identify (e.g., with the identification unit 1218) a confidence value that indicates a likelihood that the audio input was provided by a particular user, and the values in the first set of values are based on the confidence value.

In some embodiments, the processing unit 1208 is further configured to identify (e.g., with the identification unit 1218) a state of the electronic device 1200, and the values in the first set of values are based on the identified state of the electronic device 1200.

In some embodiments, the state of the electronic device 1200 is identified based on user input received by the electronic device 1200.

In some embodiments, at least one value of the first set of one or more values is based on a type of the electronic device 1200.

In some embodiments, sampling the audio input includes determining (e.g., with determining unit 1214) whether the audio input includes a spoken trigger (e.g., block 1004 of fig. 10A). The processing unit 1208 is further configured to: in accordance with a determination that the audio input does not include the spoken trigger, the first set of one or more values is forgone from being broadcast (e.g., with broadcast unit 1210).

In some embodiments, the audio input includes additional input indicative of a task, and responding to the audio input with the electronic device 1200 further includes: determining (e.g., with the determining unit 1214) whether the type of electronic device meets the requirements of the task (e.g., block 1018 of FIG. 10B); in accordance with a determination that the type of electronic device satisfies the requirements of the task, responding to the audio input (e.g., with response unit 1216) (e.g., block 1022 of FIG. 10B); in accordance with a determination that the type of electronic device does not meet the requirements of the task, forgo responding to the audio input (e.g., with response unit 1216) (e.g., block 1024 of FIG. 10B).

In some embodiments, the processing unit 1208 is further configured to: in accordance with a determination that the type of electronic device does not meet the requirements, determining (e.g., with determining unit 1214) whether the second device should respond to the audio input (e.g., block 1024 of fig. 10B); in accordance with a determination that the second device should respond to the audio input, forgoing responding to the audio input with the electronic device (e.g., with response unit 1216) (e.g., block 1028 of FIG. 10B); in accordance with a determination that the second device should not respond to the audio input, an output indicating an error is provided (e.g., with output unit 1204) (e.g., block 1026 of fig. 10B).

In some embodiments, the processing unit 1208 is further configured to: data indicating the requirements of the task is received (e.g., with receiving unit 1212) from the server (e.g., block 1020 of fig. 10B).

In some embodiments, the audio input comprises additional input indicative of a task, and forgoing responding to the audio input with the electronic device further comprises: determining (e.g., with the determining unit 1214) whether the type of electronic device meets the requirements of the task (e.g., block 1030 of FIG. 10C); in accordance with a determination that the type of electronic device satisfies the requirements of the task, determining (e.g., with determining unit 1214) whether the electronic device should respond to the audio input based on the first set of one or more values, the second set of one or more values, and the requirements of the task (e.g., block 1034 of FIG. 10C); in accordance with a determination that the electronic device should be responsive to the audio input, responding to the audio input with the electronic device (e.g., with response unit 1216) (e.g., at block 1036 of fig. 10C); and in accordance with a determination that the electronic device should not be used to respond to the audio input, forgoing responding to the audio input with the electronic device (e.g., with response unit 1216) (e.g., block 1038 of fig. 10C); and in accordance with a determination that the type of electronic device does not meet the requirements of the task, forgo responding to the audio input with the electronic device (e.g., with response unit 1216) (e.g., block 1040 of fig. 10C).

In some embodiments, the processing unit 1208 is further configured to: data indicating the requirements of the task is received (e.g., with receiving unit 1212) from the server (e.g., block 1032 of fig. 10C).

In some embodiments, forgoing to respond to the audio input with electronic device 1200 includes entering (e.g., with entering unit 1220) an inactive mode (e.g., block 1044 of fig. 10A).

In some embodiments, the first set of one or more values is broadcast according to a one-way broadcast communication protocol.

In some embodiments, the processing unit 1208 is further configured to: in accordance with a determination that the electronic device should respond to the audio input, a visual output, an audible output, a tactile output, or a combination thereof is provided (with output unit 1204).

In some embodiments, determining whether the electronic device should respond to the audio input comprises: it is determined (e.g., with determining unit 1214) whether a value of the first set of one or more values is higher than a corresponding value of the second set of one or more values (e.g., block 1042 of fig. 10A).

The operations described above with reference to fig. 10A-10C are optionally implemented by the components depicted in fig. 1-4, 6A-6B, 7A, and 12. For example, the sampling operation 1002, the determining operation 1004, the broadcasting operation 1006, and the receiving operation 1010 are optionally implemented by the processor 120. One of ordinary skill in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1-4, 6A-6B, 7A, and 12.

Fig. 13 illustrates a functional block diagram of a system including a first electronic device 1300, a first user device 1330, and a second electronic device 1360, at least one of which is configured in accordance with the principles of various described embodiments (including those described with reference to fig. 9A-9C and 11A-11E), according to some embodiments. The functional blocks of the device are optionally implemented by hardware, software, or a combination of software and hardware to implement the principles of the various embodiments described. Those skilled in the art will appreciate that the functional blocks described in fig. 13 are optionally combined or divided into sub-blocks in order to implement the principles of the various described embodiments. Thus, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in fig. 13, the first electronic device 1300 includes a first processing unit 1308. In some embodiments, the processing unit 1308 includes a receiving unit 1310, an obtaining unit 1312, a providing unit 1314, and optionally includes an identifying unit 1316 and a transmitting unit 1318. The first user equipment 1330 includes a second processing unit 1338 optionally coupled to an optional output unit. The second processing unit 1338 optionally includes a causing unit 1340, a receiving unit 1342, a determining unit 1344, a responding unit 1346, an identifying unit 1348 and a transmitting unit 1350. The second electronic device 1360 includes a third processing unit 1368. The third processing unit 1368 optionally comprises a receiving unit 1370, an obtaining unit 1372, a determining unit 1374, a transmitting unit 1376, a discovering unit 1378, an updating unit 1380 and a caching unit 1382.

In some embodiments, the first processing unit 1308 is configured to: receiving (e.g., with the receiving unit 1330) data from the first user device 1330 corresponding to the audio input (e.g., block 1102 of fig. 11A); obtaining (e.g., with obtaining unit 1312) an identification of the second user device based on data corresponding to the audio input (e.g., block 1104 of fig. 11A); obtaining (e.g., with obtaining unit 1312) an identification of the media item based on the data corresponding to the audio input (e.g., block 1174 of fig. 11E); a command including the identification of the media item and the identification of the second user device is provided (e.g., with the providing unit 1314) to the first user device 1330 (e.g., block 1182 of fig. 11E).

In some embodiments, the second processing unit 1338 is configured to cause playback of the media item at the second user device (e.g., block 1184 of fig. 11E).

In some embodiments, obtaining the identification of the media item comprises: identifying (e.g., with identification unit 1316) tasks and parameters based on data corresponding to the audio input (e.g., block 1176 of FIG. 11E); transmitting (e.g., with the transmitting unit 1318) a request to a database, wherein the request includes the parameters identifying one or more media items (e.g., block 1178 of FIG. 11E); and receiving (e.g., with the receiving unit 1310) an identification of the one or more media items from the database (e.g., block 1180 of fig. 11E).

In some embodiments, the identification of the media items comprises a unique identifier of the one or more media items.

In some embodiments, obtaining the identity of the second user equipment comprises: identifying (e.g., with identifying unit 1316) tasks and parameters based on data corresponding to the audio input (e.g., block 1106 of FIG. 11A); transmitting (e.g., with the transmitting unit 1318) a request to the second electronic device 1360, wherein the request includes the parameters identifying the user device for performing the task (e.g., block 1108 of FIG. 11A); and receiving (e.g., with the receiving unit 1310) an identification of the second user device from the second electronic device 1360 (e.g., block 1124 of fig. 11B).

In some embodiments, the parameter includes an indication of a named location of the user.

In some embodiments, the parameter comprises an indication of a type of device.

In some embodiments, the parameters include one or more attributes of the one or more media items.

In some embodiments, the second electronic device 1360 is the first user device 1330.

In some embodiments, the third processing unit 1368 is configured to: receiving (e.g., with receiving unit 1370) the request including the parameter (e.g., block 1110 of FIG. 11A); obtaining (e.g., with an obtaining unit 1372) data from a record, wherein the record stores sets of attributes that respectively correspond to a plurality of user devices (e.g., block 1118 of FIG. 11A); determining (e.g., with the determining unit 1374) an identity of a second user equipment based on the parameters, wherein the second user equipment is a member of the plurality of user equipments (e.g., block 1120 of fig. 11B); and transmitting (e.g., with transmission unit 1376) the identification of the second user equipment to the first electronic device 1300 (e.g., block 1122 of fig. 11B).

In some embodiments, determining the identity of the second user equipment based on the parameter comprises: it is determined (e.g., with the determining unit 1374) whether the at least one attribute of the second user equipment matches the parameter (e.g., block 1121 of fig. 11B).

In some embodiments, the user device of the plurality of user devices is a computer.

In some embodiments, the user equipment of the plurality of user equipment is a television.

In some embodiments, the user device of the plurality of user devices is a set top box.

In some embodiments, the user devices of the plurality of user devices are audio speakers.

In some embodiments, the user device of the plurality of user devices is a telephone.

In some embodiments, the third processing unit 1368 is further configured to: one or more user devices are discovered (e.g., with discovery unit 1378) and the record is updated (e.g., with update unit 1380) based on the discovered attributes of the one or more user devices. These steps are similar to those performed at blocks 1112 and 1114 (fig. 11A), but are performed automatically and/or periodically (rather than in response to receiving a user request).

In some embodiments, the third processing unit 1368 is further configured to: in response to receiving the request including the parameters, one or more user devices (e.g., block 1112 of fig. 11A) are discovered (e.g., with discovery unit 1378) and the record (e.g., block 1114 of fig. 11A) is updated (e.g., with update unit 1380) based on the discovered attributes of the one or more user devices.

In some embodiments, discovering one or more user devices includes discovering a user device associated with an indication of a named location of a user (e.g., block 1113 of fig. 11A).

In some embodiments, the third processing unit 1368 is further configured to: the discovered attributes of the one or more user devices are cached (e.g., with caching element 1382) (e.g., block 1118 of fig. 11A).

In some embodiments, obtaining the identification of the second user device based on the data corresponding to the audio input further comprises: identifying (e.g., with identifying unit 1316) tasks and parameters based on data corresponding to the audio input (e.g., block 1126 of FIG. 11B); receiving (e.g., with the receiving unit 1310) a plurality of identifications corresponding to a plurality of user devices from the second electronic device 1360 (e.g., block 1132 of FIG. 11B); transmitting (e.g., with transmitting unit 1318) the plurality of identifications corresponding to the plurality of user devices to first user device 1330 (e.g., at block 1134 of fig. 11B); receiving (e.g., with the receiving unit 1310) data from the first user device 1330 corresponding to a selection of a particular user device of the plurality of user devices (e.g., block 1144 of fig. 11C); an identification of a second user equipment is obtained (e.g., with obtaining unit 1312) based on the received data corresponding to the selection of the particular one of the plurality of user equipments (e.g., block 1146 of fig. 11C).

In some embodiments, the second processing unit 1338 is further configured to: receiving (e.g., with receiving unit 1342) the plurality of identifications corresponding to the plurality of user devices (e.g., block 1136 of fig. 11B); presenting (e.g., with output unit 1334) the plurality of user devices as selectable options (e.g., block 1138 of FIG. 11B); receiving (e.g., with the receiving unit 1342) an input representing a selection of the particular one of the plurality of user devices (e.g., block 1140 of FIG. 11C); data corresponding to the selection of the particular user device is transmitted (e.g., with transmission unit 1350) to the first electronic device 1300 (e.g., block 1142 of fig. 11C).

In some embodiments, each of the plurality of user equipment has an attribute that matches the parameter.

In some embodiments, obtaining the identification of the second user device based on the data corresponding to the audio input further comprises: identifying (e.g., with identifying unit 1316) tasks and parameters based on data corresponding to the audio input (e.g., block 1148 of FIG. 11C); receiving (e.g., with the receiving unit 1310) data corresponding to the candidate user device from the second electronic device 1360 (e.g., block 1158 of fig. 11D); transmitting (e.g., with the transmission unit 1318) data corresponding to the candidate user device to the first user device 1330 (e.g., block 1160 of fig. 11D); receiving (e.g., with the receiving unit 1310) data from the first user device 1330 corresponding to the determination of the candidate user device (e.g., block 1170 of fig. 11E); and responsive to receiving the data corresponding to the confirmation, acquiring (e.g., with acquisition unit 1312) an identification of the second user equipment by acquiring (e.g., with acquisition unit 1312) an identification of the candidate user equipment (e.g., block 1172 of fig. 11E).

In some embodiments, the second processing unit 1338 is further configured to: receiving (e.g., with the receiving unit 1342) data corresponding to the candidate user device (e.g., block 1162 of fig. 11D); presenting (e.g., with output unit 1334) the candidate user device as a confirmable option (e.g., block 1164 of FIG. 11D); receiving (e.g., with the receiving unit 1342) an input representing a confirmation of the candidate user device (e.g., block 1166 of fig. 11D); and transmitting (e.g., with transmitting unit 1350) data corresponding to the determination of the candidate user device to the first electronic device 1300 (e.g., block 1168 of fig. 11E).

In some embodiments, the second processing unit 1338 is further configured to: receiving (e.g., with receiving unit 1342) data corresponding to the candidate user devices; presenting (e.g., with output unit 1334) the candidate user devices as a confirmable option; receiving (e.g., with the receiving unit 1342) an input representing a rejection of the candidate user device (e.g., block 1171 of fig. 11D); an output indicating an error is presented (e.g., with output unit 1334) (e.g., block 1173 of fig. 11D).

In some embodiments, the third processing unit 1368 is further configured to: receiving (e.g., with the receiving unit 1370) a request for an identification of a user device from the first electronic device 1300, wherein the request includes the parameter (e.g., block 1150 of fig. 11C); obtaining (e.g., with an obtaining unit 1372) data from a record, wherein the record stores sets of attributes corresponding to a plurality of user devices, respectively (e.g., block 1152 of fig. 11C); obtaining (e.g., with an obtaining unit 1372) data corresponding to candidate user devices based on the parameters, wherein the candidate user devices are not members of the plurality of user devices stored in the record (e.g., block 1154 of fig. 11D); and transmitting (e.g., with the transmitting unit 1376) data corresponding to the candidate user device to the first electronic device 1300 (e.g., block 1156 of fig. 11D).

In some embodiments, obtaining data corresponding to the candidate user devices based on the parameters further comprises: determining (e.g., with the determining unit 1374) that none of the plurality of user devices has a parameter that matches the parameter (e.g., block 1151 of fig. 11C); and discovering (e.g., with the discovery unit 1378) a candidate user device, wherein the candidate user device has an attribute that matches the parameter (e.g., block 1153 of fig. 11C).

In some embodiments, the third processing unit 1368 is further configured to: receiving (e.g., with the receiving unit 1370) data corresponding to the confirmation of the candidate user device to the first electronic device 1300 (e.g., block 1171 of fig. 11E); in response to receiving the data corresponding to the acknowledgement, the record is updated (e.g., with update unit 1380) (e.g., block 1173 of fig. 11E).

The operations described above with reference to fig. 11A-11E are optionally implemented by the components depicted in fig. 1-4, 6A-6B, 7A, and 13. For example, the receiving operation 1102, the obtaining operation 1104, and the providing operation 1182 are optionally implemented by the processor 120. Those of ordinary skill in the art will clearly know how other processes may be implemented based on the components depicted in fig. 1-4, 6A-6B, 7A, and 13.

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

According to some implementations, an electronic device (e.g., a portable electronic device) is provided that includes means for performing any of the methods or processes described herein.

According to some implementations, an electronic device (e.g., a portable electronic device) is provided that includes a processing unit configured to perform any of the methods or processes described herein.

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

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the technology and its practical applications. Those skilled in the art are thus well able to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

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

Claims

1. A method for controlling a user device with a virtual assistant on a first user device, the method comprising:

at an electronic device:

receiving, with the electronic device, data corresponding to audio input from the first user device;

obtaining, with the electronic device, an identification of a second user device based on the data corresponding to the audio input;

obtaining, with the electronic device, an identification of a media item based on the data corresponding to the audio input; and

providing, with the electronic device, a command to the first user device that includes the identification of the media item and the identification of the second user device.

2. The method of claim 1, further comprising:

at the location of the first user equipment,

causing, with the first user device, playback of the media item at the second user device.

3. The method of claim 1, wherein obtaining the identification of the media item comprises:

identifying, with the electronic device, tasks and parameters based on the data corresponding to the audio input;

transmitting, with the electronic device, a request to a database, wherein the request includes the parameters identifying one or more media items; and

receiving, with the electronic device, the identification of the one or more media items from the database.

4. The method of claim 3, wherein the identification of the media item comprises a unique identifier of the one or more media items.

5. The method of any of claims 1-4, wherein the electronic device is a first electronic device, and wherein obtaining the identification of the second user device comprises:

identifying, with the first electronic device, tasks and parameters based on the data corresponding to the audio input;

transmitting, with the first electronic device, a request to a second electronic device, wherein the request includes the parameter identifying a user device for performing the task; and

receiving, with the first electronic device, the identification of the second user device from the second electronic device.

6. The method of claim 5, wherein the parameter comprises an indication of a named location of a user.

7. The method of claim 5, wherein the parameter comprises an indication of a type of device.

8. The method of claim 5, wherein the parameters include one or more attributes of one or more media items.

9. The method of claim 5, wherein the second electronic device is the first user equipment.

10. The method of claim 5, further comprising:

at the second electronic device:

receiving, with the second electronic device, the request including the parameter;

obtaining, with the second electronic device, data from a record, wherein the record stores sets of attributes corresponding to a plurality of user devices, respectively;

determining, with the second electronic device, the identity of the second user device based on the parameter, wherein the second user device is a member of the plurality of user devices; and

transmitting, with the second electronic device, the identification of the second user device to the first electronic device.

11. The method of claim 10, wherein determining the identity of the second user equipment based on the parameter comprises:

determining, with the second electronic device, whether at least one attribute of the second user device matches the parameter.

12. The method of claim 10, wherein a user device of the plurality of user devices is a computer, a television, a set-top box, an audio speaker, or a telephone.

13. The method of claim 10, further comprising:

at the second electronic device:

discovering one or more user devices with the second electronic device;

updating, with the second electronic device, the record based on the discovered attributes of the one or more user devices.

14. The method of claim 13, wherein discovering the one or more user devices comprises discovering, with the second electronic device, a user device associated with an indication of a named location of a user.

15. The method of claim 10, further comprising:

at the second electronic device:

in response to receiving the request including the parameters, discovering, with the second electronic device, one or more user devices;

16. The method of claim 15, wherein discovering the one or more user devices comprises discovering, with the second electronic device, a user device associated with an indication of a named location of a user.

17. The method of claim 15, further comprising: caching, with the second electronic device, the discovered attributes of the one or more user devices.

18. The method of any of claims 1-4, wherein the electronic device is a first electronic device, and wherein obtaining the identification of the second user device based on the data corresponding to the audio input further comprises:

at the first electronic device:

receiving, with the first electronic device, a plurality of identifications corresponding to a plurality of user devices from a second electronic device;

transmitting, with the first electronic device, the plurality of identities corresponding to the plurality of user devices to the first user device;

receiving, with the first electronic device, data from the first user device corresponding to a selection of a particular user device of the plurality of user devices;

obtaining, with the first electronic device, an identification of the second user device based on the received data corresponding to the selection of the particular user device of the plurality of user devices.

19. The method of claim 18, further comprising:

at the location of the first user equipment,

receiving, with the first user device, the plurality of identifications corresponding to the plurality of user devices;

presenting, with the first user device, the plurality of user devices as selectable options;

receiving, with the first user device, an input representing the selection of the particular user device of the plurality of user devices;

transmitting, with the first user device, the data corresponding to the selection of the particular user device to the first electronic device.

20. The method of claim 18, wherein each of the plurality of user devices has an attribute that matches the parameter.

21. The method of any of claims 1-4, wherein the electronic device is a first electronic device, and wherein obtaining the identification of the second user device based on the data corresponding to the audio input further comprises:

at the first electronic device:

receiving, with the first electronic device, data corresponding to a candidate user device from a second electronic device;

transmitting, with the first electronic device, the data corresponding to the candidate user device to the first user device;

receiving, with the first electronic device, data from the first user device corresponding to a confirmation of the candidate user device; and

in response to receiving the data corresponding to the confirmation, obtaining, with the first electronic device, an identification of the second user device by obtaining the identification of the candidate user device.

22. The method of claim 21, further comprising:

at the location of the first user equipment,

receiving, with the first user device, the data corresponding to the candidate user device;

presenting, with the first user device, the candidate user device as a confirmable option;

receiving, with the first user device, an input representing the confirmation of the candidate user device;

transmitting, with the first user device, data corresponding to the confirmation of the candidate user device to the first electronic device.

23. The method of claim 21, further comprising:

at the location of the first user equipment,

receiving, with the first user device, an input representing a rejection of the candidate user device;

presenting, with the first user device, an output indicating an error.

24. The method of claim 21, further comprising:

at the second electronic device:

receiving, with the second electronic device, a request from the first electronic device to identify a user device, wherein the request includes the parameter;

obtaining, with the second electronic device, data corresponding to the candidate user device based on the parameters, wherein the candidate user device is not a member of the plurality of user devices stored in the record; and

transmitting, with the second electronic device, data corresponding to the candidate user device to the first electronic device.

25. The method of claim 24, wherein obtaining the data corresponding to the candidate user device based on the parameter further comprises:

determining, with the second electronic device, that none of the plurality of user devices have an attribute that matches the parameter;

discovering, with the second electronic device, the candidate user device, wherein the candidate user device has an attribute that matches the parameter.

26. The method of claim 24, further comprising:

at the second electronic device:

receiving, with the second electronic device, the data corresponding to the acknowledgement to the candidate user device to the first electronic device;

updating the record with the second electronic device in response to receiving the data corresponding to the confirmation.

27. A computer-readable storage medium comprising one or more computer-readable storage media storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of one or more electronic devices, cause the one or more electronic devices to perform the method of any of claims 1-26.

28. A system for controlling user equipment, comprising:

one or more processors of one or more electronic devices;

one or more memories of the one or more electronic devices; and

one or more programs, wherein the one or more programs are stored in the one or more memories and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any of claims 1-26.